Abstract:
A method for creating, discovering, and joining meetings over a peer-to-peer network involves creation of a graph of meetings on a local subnet. When a meeting is created a meeting record is added to the graph where it may be discovered by other potential meeting attendees. A user may select from a list of meetings displayed in a meeting management window and send requested showing the selected meaning. Credentials, such as a password, may be supplied with the request. When the request is validated, information is sent to the requester for use in joining the meeting. When an ad hoc wireless session is used to hold a meeting the discovery process may further include analyzing data traffic to determine which wireless sessions are meetings.
Abstract:
Users on a peer-to-peer network, particularly a local subnet or ad hoc wireless network, may publish first contact information to a graph or data store on the network. The first contact information may include a certificate with a public-key and a user identification, such as a peer name. Other users may discover the first contact information and use the first contact information to request additional information from the user. Data in the first contact information may also be "promoted" by adding the information to a trusted contacts database, allowing the user additional privileges. The user publishing the first contact information may be given the opportunity to approve or deny the request for additional information.
Abstract:
A mobile computing device that supports cost-aware application components for operation over a metered network. A current basis for computing usage charges over one or more networks may be made available to the cost-aware application components through an application programming interface supported by an operating system service. That service may receive a policy for charging for data usage over a network and may also obtain information defining data usage for the mobile computing device. Based on this information, the service may determine a current basis for charging for data usage. With this information, the application component can determine a manner for executing network operations that involve data transmission over the network, such as deferring the operation or selecting an alternative network.
Abstract:
Methods and computer readable mediums are described that facilitate inviting user entities on a network. The method may include initiating a first application for sending an invitation by a first user entity on a first endpoint, selecting a second user entity to receive the invitation, and selecting an activity. The method may also include sending from the first endpoint to the second user entity the invitation to participate in the activity if the first endpoint determines the activity is supported by a computing application on the first endpoint.
Abstract:
A context dependent computing device. The computing device configures itself for operations based on its context. The computing device may determine its context by reading a value from a tag using low power transmissions such that receiving a value from the tag provides an indication of proximity to a location where the tag is affixed. The value read provides an indication of a desired operation. In response to reading a value of a tag, the computing device may identify an application to launch, identify devices with which to pair or take other actions that configure the computing device for its context.
Abstract:
Methods are described that facilitate presence publication which may include authorizing publication of presence at a first endpoint, if the publication is authorized, assembling a presence data structure, and broadcasting the presence data structure from the first endpoint. The method may also include the presence structure including a friendly name, contact information, and endpoint information. The method further including contact information in at least one of XML format, vCard format, and the endpoint information obtained from a peer name resolution protocol. The method may additionally include the presence data structure encoded as at least one of a generic discovery protocol message, a simple service discovery protocol message, and associating a globally unique identifier with the discovery protocol messages. The method may include a user entity authorizing presence publication, the user entity setting at least one of a default parameter authorizing publication of all presence, some presence, or no presence.