WO2006115934A2 - An application programming interface for inviting participants in a serverless peer to peer network - Google Patents
An application programming interface for inviting participants in a serverless peer to peer network Download PDFInfo
- Publication number
- WO2006115934A2 WO2006115934A2 PCT/US2006/014742 US2006014742W WO2006115934A2 WO 2006115934 A2 WO2006115934 A2 WO 2006115934A2 US 2006014742 W US2006014742 W US 2006014742W WO 2006115934 A2 WO2006115934 A2 WO 2006115934A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- invitation
- endpoint
- application
- activity
- receiving
- Prior art date
Links
- 230000000694 effects Effects 0.000 claims abstract description 65
- 238000000034 method Methods 0.000 claims abstract description 57
- 230000000977 initiatory effect Effects 0.000 claims abstract description 10
- 230000007246 mechanism Effects 0.000 claims description 4
- 238000004891 communication Methods 0.000 description 36
- 230000006870 function Effects 0.000 description 19
- 125000001475 halogen functional group Chemical group 0.000 description 11
- 238000005516 engineering process Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 230000004044 response Effects 0.000 description 5
- 230000006855 networking Effects 0.000 description 4
- 230000002093 peripheral effect Effects 0.000 description 4
- 230000007423 decrease Effects 0.000 description 3
- 230000005055 memory storage Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 239000007787 solid Substances 0.000 description 2
- CDFKCKUONRRKJD-UHFFFAOYSA-N 1-(3-chlorophenoxy)-3-[2-[[3-(3-chlorophenoxy)-2-hydroxypropyl]amino]ethylamino]propan-2-ol;methanesulfonic acid Chemical compound CS(O)(=O)=O.CS(O)(=O)=O.C=1C=CC(Cl)=CC=1OCC(O)CNCCNCC(O)COC1=CC=CC(Cl)=C1 CDFKCKUONRRKJD-UHFFFAOYSA-N 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000001681 protective effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000007723 transport mechanism Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
- H04L12/1818—Conference organisation arrangements, e.g. handling schedules, setting up parameters needed by nodes to attend a conference, booking network resources, notifying involved parties
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/465—Distributed object oriented systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1069—Session establishment or de-establishment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
- H04L67/1061—Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
- H04L67/1068—Discovery involving direct consultation or announcement among potential requesting and potential source peers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/54—Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
Definitions
- Server based communication services such as the Messenger service provided by MSN ® communication services permit users to sign into a server-based network and then use the services of the network (e.g., e-mail, text messaging, etc.).
- a server may store a contact list for the user and the user can add and delete persons from the contact list.
- a server or servers may notify persons in the user's contact list that the user is "online.”
- the server or servers may notify the user of persons in the user's contact list that are "online.”
- the MICROSOFT ® Corporation also provides Peer-to-Peer Networking software for use with its WINDOWS ® operating systems.
- users can create a network of peer computers and can communicate with one another without having to sign into a central server.
- users can create a peer-to-peer group and then create a chat room in which all members of the group can post messages and see messages posted by others in the group.
- the system may also allow peers to invite others to participate in collaborative activities.
- the chat room is maintained using the peer computers and without the need for a central server.
- 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.
- the method may include that the first application for sending the invitation is the computing application, that the first application for sending the invitation is a messenger application, and initiating a name resolution mechanism to locate a second endpoint for the second user entity.
- the method may further include querying a presence store to locate a second endpoint for the second user entity, sending the invitation synchronously or asynchronously, canceling an asynchronous invitation at the first endpoint, and sending the invitation in a secure or unsecure manner.
- the method may include initiating, at a receiving endpoint, a first application for receiving an invitation from a sending endpoint to participate in an activity, receiving the invitation at the receiving endpoint, and launching a computing application on the receiving endpoint to execute the activity if the receiving endpoint determines the activity is capable of being executed by the computing application at the receiving endpoint.
- the method may include the first application for receiving the invitation is the computing application, the first application for receiving the invitation is a messenger application, and the receiving endpoint receives the invitation by at least one of a generic invitation listener application, a messenger application, or the computing application at the receiving endpoint.
- the method may further include registering activity capabilities of the computing application at the receiving endpoint with a presence store, receiving the invitation synchronously or asynchronously, receiving the invitation in a secure or unsecure manner, and retrieving, by the sending endpoint, status information of the invitation sent to the receiving endpoint.
- FIG. 1 is a block diagram of a computing system that may operate in accordance with the claims;
- FIG. 2 is a block diagram of an exemplary system that may facilitate peer-to-peer, serverless collaboration and/or communications;
- FIG. 3 is a flow diagram of an exemplary method related to sending an invitation to a contact that may facilitate collaborative activities.
- Fig. 4 is a flow diagram of an exemplary method related to receiving an invitation that may facilitate collaborative activities.
- FIG. 1 illustrates an example of a suitable computing system environment 100 on which a system for the steps of the claimed method and apparatus may be implemented.
- the computing system environment 100 is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of the method of apparatus of the claims. Neither should the computing environment 100 be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the exemplary operating environment 100.
- program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types.
- the methods and apparatus may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network.
- program modules may be located in both local and remote computer storage media including memory storage devices.
- an exemplary system for implementing the steps of the claimed method and apparatus includes a general purpose computing device in the form of a computer 110.
- Components of computer 110 may include, but are not limited to, a processing unit 120, a system memory 130, and a system bus 121 that couples various system components including the system memory to the processing unit 120.
- the system bus 121 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures.
- such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus also known as Mezzanine bus.
- ISA Industry Standard Architecture
- MCA Micro Channel Architecture
- EISA Enhanced ISA
- VESA Video Electronics Standards Association
- PCI Peripheral Component Interconnect
- Computer 110 typically includes a variety of computer readable media.
- Computer readable media can be any available media that can be accessed by computer 110 and includes both volatile and nonvolatile media, removable and non-removable media.
- Computer readable media may comprise computer storage media and communication media.
- Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data.
- Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by computer 110.
- Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media.
- modulated data signal means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.
- communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF 5 infrared and other wireless media. Combinations of the any of the above should also be included within the scope of computer readable media.
- the system memory 130 includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) 131 and random access memory (RAM) 132.
- ROM read only memory
- RAM random access memory
- BIOS basic input/output system
- RAM 132 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit 120.
- Fig. 1 illustrates operating system 134, application programs 135, other program modules 136, and program data 137.
- the computer 110 may also include other removable/non-removable, volatile/nonvolatile computer storage media.
- Fig. 1 illustrates a hard disk drive 140 that reads from or writes to non-removable, nonvolatile magnetic media, a magnetic disk drive 151 that reads from or writes to a removable, nonvolatile magnetic disk 152, and an optical disk drive 155 that reads from or writes to a removable, nonvolatile optical disk 156 such as a CD ROM or other optical media.
- removable/non-removable, volatile/nonvolatile computer storage media that can be used in the exemplary operating environment include, but are not limited to, magnetic tape cassettes, flash memory cards, digital versatile disks, digital video tape, solid state RAM, solid state ROM, and the like.
- the hard disk drive 141 is typically connected to the system bus 121 through a non-removable memory interface such as interface 140, and magnetic disk drive 151 and optical disk drive 155 are typically connected to the system bus 121 by a removable memory interface, such as interface 150.
- the drives and their associated computer storage media discussed above and illustrated in Fig. 1, provide storage of computer readable instructions, data structures, program modules and other data for the computer 110.
- hard disk drive 141 is illustrated as storing operating system 144, application programs 145, other program modules 146, and program data 147. Note that these components can either be the same as or different from operating system 134, application programs 135, other program modules 136, and program data 137. Operating system 144, application programs 145, other program modules 146, and program data 147 are given different numbers here to illustrate that, at a minimum, they are different copies.
- a user may enter commands and information into the computer 20 through input devices such as a keyboard 162 and pointing device 161, commonly referred to as a mouse, trackball or touch pad.
- Other input devices may include a microphone, joystick, game pad, satellite dish, scanner, or the like.
- These and other input devices are often connected to the processing unit 120 through a user input interface 160 that is coupled to the system bus, but may be connected by other interface and bus structures, such as a parallel port, game port or a universal serial bus (USB).
- a monitor 191 or other type of display device is also connected to the system bus 121 via an interface, such as a video interface 190.
- computers may also include other peripheral output devices such as speakers 197 and printer 196, which may be connected through an output peripheral interface 190.
- the computer 110 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 180.
- the remote computer 180 may be a personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 110, although only a memory storage device 181 has been illustrated in Fig. 1.
- the logical connections depicted in Fig. 1 include a local area network (LAN) 171 and a wide area network (WAN) 173, but may also include other networks.
- LAN local area network
- WAN wide area network
- Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets and the Internet.
- the computer 110 When used in a LAN networking environment, the computer 110 is connected to the LAN 171 through a network interface or adapter 170. When used in a WAN networking environment, the computer 110 typically includes a modem 172 or other means for establishing communications over the WAN 173, such as the Internet.
- the modem 172 which may be internal or external, may be connected to the system bus 121 via the user input interface 160, or other appropriate mechanism.
- program modules depicted relative to the computer 110, or portions thereof may be stored in the remote memory storage device.
- Fig. 1 illustrates remote application programs 185 as residing on memory device 181. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.
- FIG. 2 is a block diagram of an example system 200 that may be used to implement example methods described herein.
- the system 200 may facilitate peer-to-peer, serverless collaboration and/or communications via a communication network 202, and may be implemented using a computing system such as the computing system 100 of Figure 1.
- the communication network may include, but is not limited to, a LAN and/or a WAN, or a communication medium supporting socket communications, or named-pipes, for example.
- the system 200 may include a presence system 204 that monitors the presence of other entities on the communication network.
- An entity may be, for example, a particular person, a device (e.g., a printer, a copier, a computer, a scanner, etc.) a position in an organization (e.g., "manager,” "customer service representative,” etc.), an organization, etc.
- Presence on a network may generally refer to a current status of an entity with regard to their willingness or ability to communicate via the network, but may also refer to additional or alternative information regarding the entity such as a current activity of the entity. Presence on a network may be represented by presence information.
- Presence information may include, but are not limited to, one or more of an indication that an entity is "online,” an indication that an entity is “out to lunch,” an indication that an entity is “away,” an indication that an entity will “be right back,” an indication that an entity is “idle,” an indication that an entity is “busy,” an indication that an entity is “on the phone,” an indication that an entity is “watching a movie,” an indication that an entity is “playing Halo ® ,” an indication that an entity is “helping another customer,” an indication of a device status (e.g., a printer with status "busy,” “idle,” etc).
- Presence information may include one or more enumerated strings and/or rich presence (e.g., custom strings generated by a user entity). For example, a user entity could define a custom presence state as, "I am out of the office. Will return tomorrow.” Presence information obtained by the presence system 204 may be stored in a presence store 208.
- the presence system 204 may facilitate a user entity to monitor (or "subscribe") to presence information of other entities. This may include the presence system 204 polling other computing systems periodically, for example. Additionally or alternatively, other computing systems corresponding to other user entities may transmit event indications to the system 200 that notify the presence system 204 of events such as a change in presence state. For example, an event may occur when a user's presence changes from "offline” to "online,” and the presence system 204 may detect this event. The presence system 204 could then notify other applications or software modules (e.g., such as the application 280) that the event occurred.
- the presence system 204 may also monitor capabilities of other entities published on the network 202.
- Capabilities of an entity may include, for example, static capabilities such as whether a computing system of the entity is configured to execute a particular software application, whether a computing system of the entity has a particular hardware device, etc.
- Capabilities of an entity may also include, for example, dynamic capabilities such as real-time capabilities of an entity with respect to a game software application currently being executed on the entity's computing system, etc.
- An entity publishing capabilities on the network may refer to permitting other entities to be able to monitor the capabilities via the network 202.
- Capability information obtained by the presence system 204 may be stored in a capability store 212.
- the presence system 204 may also monitor objects of other entities published on the network 202.
- Objects of an entity may include, for example, data objects such as files, structures, pictures, sounds, a description such as meta-data, a name-value pair, etc.
- An entity publishing objects on the network may refer to permitting other entities to be able to monitor the objects via the network 202.
- publishing an object may permit an entity to provide other entities with information specific to an application being executed by a computing system of the entity and/or real-time info ⁇ nation.
- a published object could include information regarding a player's current score, a weapon currently in possession of the player, etc.
- Objects information obtained by the presence system 204 may be stored in an objects store 216.
- the presence system 204 may also provide (or "publish") presence information associated with a user entity (i.e., the entity associated with the system 200) to other entities on the network 202.
- the presence information associated with the user entity may be stored in the presence store 208 or some other storage.
- the presence system 204 may also provide (or "publish") information regarding capabilities of the user entity to other entities on the network 202.
- the capability information associated with the user entity may be stored in a capability store 208.
- the presence system 204 may also provide (or "publish") information regarding objects of the user entity to other entities on the network.
- the object information associated with the user entity may be stored in an object store 216, or some other storage.
- the presence system 204 may facilitate an ability for the user entity to monitor (or "subscribe-to") presence information. As such, when presence information is monitored by the user entity, subsequent changes may elicit events for which the user entity is notified. For example, if the monitored presence information changes from "away” to "playing Halo ® ,” an event may trigger thereby notifying the user entity of a change.
- the presence system 204 may interface with a contact store 240 that stores information regarding other entities.
- the contact store 240 may store information for an entity such as one or more of a secure identifier, a human readable alias, an indicator of whether presence information for this entity is to be monitored, and an indicator of whether to allow this entity to obtain presence information regarding the user entity.
- An entity as represented in the contact store 240 may be referred to as a contact.
- Each user entity may have one or more communication endpoints with which it is associated.
- different communication endpoints associated with a user entity may include different communication termination points associated with the entity, such as different computing systems.
- endpoints for a particular entity may include a desktop computer at work, a desktop computer at home, a personal digital assistant (PDA), etc.
- PDA personal digital assistant
- different communication endpoints associated with a user entity may also include different software applications being executed by a single computing system.
- Endpoint information may include a peer name, a machine name, or a device type, to name a few.
- the presence system 204 may also interface with a communication system 260, which is coupled to the communication network 202.
- the communication system 260 may establish connections between the system 200 and other peer computing systems associated with other entities. Establishing a connection may include, for example, one or more of determining an endpoint associated with an entity, resolving an address of the endpoint, authenticating communications, encrypting and decrypting communications, etc.
- the communication system 260 may include a Peer Name Resolution Protocol (PNRP), or similar.
- the PNRP may resolve a name (e.g., a peer name) for a contact to derive its IP address without reliance upon a Domain Name System (DNS), commonly used by server computers.
- DNS Domain Name System
- the communication system 260 may interface with an authentication system 270 that is itself coupled to the contact store 240. In attempting to establish a connection with another computing system, the communication system 260 may receive from the other computing system an indication of an identifier associated with an entity. The authentication system 270 may then check whether information about the entity with the security identifier presented is stored in the contact store 240. If the identifier is not found in the contact store 240, the connection may be refused.
- a connection may be secured.
- Establishing a connection and communicating over a connection may include, for example, one or more of utilizing a secure channel, utilizing secure socket layer (SSL) techniques, utilizing transport layer security (TLS) techniques, utilizing public/private key pairs, utilizing authentication techniques (e.g., X.509 certificates, encrypted signatures utilizing a pretty good privacy (PGP) program, etc.), utilizing a peer name resolution protocol (PNRP), transmission control protocol (TCP), internet protocol (IP), internet protocol version six (IPv6), etc.
- Resolving an address of an endpoint may include, for example, resolving a PNRP identifier to an IP address and a port.
- a software application 280 may communicate with the presence system 204 to obtain presence information, capabilities information, and/or objects information associated with other user entities on the communication network 202.
- the presence system 204 may provide a set of application programming interfaces (APIs) that permit software applications to request and receive information regarding presence, capabilities, and/or objects associated with other user entities.
- the presence system 204 may retrieve the requested information from the presence store 208, capabilities store 212, and/or the objects store 216. Additionally or alternatively, the presence system 204 could obtain requested information from the other user entities via the communication system 260 and the communication network 202.
- “availability" may refer to presence information, capabilities and objects. A user entity has the ability to publish all, some, or none of this information.
- An invitation API 282 may permit an application 280 used by a user entity to invite other contacts or user entities of a serverless network to participate in a collaborative activity.
- the invitation API 282 may employ the use of the Presence System 204 to determine contacts from the contact store 240. Additionally, the Presence System 204 may retrieve capability information located in the capability store 212. If a particular contact in the contact store 240 has no associated capability information, the invitation API 282 or, alternatively, the Application 280 may employ a Capabilities API 284 to determine the capabilities of another user entity's endpoint.
- a capability may be a collaborative activity including any activity which is supported by an application on multiple endpoints.
- a contact may support the activity of Halo ® game play because the contact's endpoint has the Halo ® gaming application installed.
- the invitation API may allow the contact owner to determine other contacts on a serverless network that may support the activity of Halo ® game-play.
- an invitation may be sent by the user entity (invitor) to that contact (invitee), thereby allowing the invitee to respond to the invitation.
- a response may include standard invitee options of "accept,” “reject,” or “ignore.”
- Other response options may include standard or custom text such as "busy now, please invite me later,” or “please try again after 9 pm.”
- the invitee may time-out. Upon expiration of a timeout period, the invitation may disappear from view at the invitee's endpoint, thereby minimizing clutter on the invitee's desktop.
- an invitee may configure alert settings so that, for example, invitation dialog boxes do not interrupt an invitee while giving a presentation.
- any incoming invitations may automatically receive an indication that the invitee is unavailable.
- the invitee may further customize such indications, for example, "Presentation ongoing, please try after 4 pm.”
- Figure 3 may be an illustration of a method 300 in accordance with the claims.
- the method may begin at either block 302 or block 350, depending on whether the application 280 used by the user entity is a messenger application (starting at block 302) or a computing application (starting at block 350).
- the user entity may begin the invitation process at block 302.
- the user entity may access the messenger application 280 at block 304 which may provide the user entity with a list of contacts from the contact store 240.
- the messenger application 280 may also access the presence system 204 to obtain presence information from the presence store 208 and provide the user entity with presence information for the contacts for which the user has selected.
- the user entity may select a contact and at block 308 the user entity may select a desired activity.
- the contact selected is not limited to other user entities, but may include one or more of the invitor contact's alternate points of presence.
- the user may select activities including, but not limited to, playing Halo ® , internet telephony, or a collaborative whiteboard.
- the Capabilities API 284 may allow the user entity to verify endpoint capabilities at block 310.
- the method may proceed to block 312 and terminate 395. Additionally, or alternatively, the method may send a message to the contact selected at block 306 to notify that contact of the failed invitation attempt, and possible reasons for that failure.
- the method may determine if the messenger, or some other application, sends the invitation at block 314.
- the method may include a default setting in which the messenger always performs the invitation, or the particular application supporting the activity performs the invitation.
- the method may also prompt the user entity to choose one of the aforementioned options. If the messenger performs the invitation, then, via the Invite API's, the method may launch the corresponding application which supports the activity at block 316.
- the application supporting the activity may perform the invitation by calling the Invite API 282 which may also set environment variables to the application and launch such application at block 318.
- the Invite API 282 may also permit the invitation to hold application specific data and/or pass parameters to the application.
- Environment variables may include a list of invitees, or other information pertaining to the activity, the application supporting the activity, and the contacts invited to participate in the activity. Once those variables are set at block 318 they may be read by the application 280 at block 320. The application may then use a function call from the invitation API 282 at block 322 to send the invitation. If, however, a contact has multiple points of presence, the invitation API 282 may send the invitation to all endpoints for which the invitee is associated.
- An invitation function call from the invitation API 282 may require sending parameters derived from the calling application, whether the calling application is the messenger or the application supporting the activity.
- the sending parameters may include the receiving name or names, the receiving contact endpoint (e.g., an IP address and port), activity information, and a function call handle, to name a few.
- the Communication System 260 may determine whether a particular endpoint for a contact name is known at block 324. If unknown, block 326 may use the Communication System 260 to determine a corresponding IP address and port for the contact, and then establish a connection with that endpoint at block 328.
- the Communication System 260 may employ PNRP, or similar, to resolve such endpoint credentials without a server.
- the activity information may also include a globally unique identifier (GUID) to identify an appropriate application to the invitee (recipient) that may support the desired activity.
- GUID globally unique identifier
- the activity information may also include an invitation message (e.g., "Let's talk about the TPS report now.") and other information to support various requirements of any particular activity.
- the handle may allow the function call to receive event information after the invitation is sent to an invitee. Such a handle is particularly useful for asynchronous function calls, however the function calls employed by the invitation API 282 may also be synchronous, in which case a response is promptly received, or the function call times out. Additionally, another handle may identify the invitation instance so that a cancellation function call may correctly identify a specific invitation to cancel.
- an invitation session is created having a corresponding GUID.
- This GUID may be used to identify responses received as a result of this particular invitation.
- the invitation API may serialize the invitation in XML (or other) format before sending to the invitee via the Communication System 260.
- Figure 4 may be an illustration of a method 400 in accordance with the claims.
- the exemplary method for receiving an invitation may include one of three starting blocks 402, 426, or 456.
- a starting block is determined by virtue of an invitee's endpoint status as either running an application 280 of type messenger (block 402), running an application 280 supporting the invitation activity (block 426), or not running either of these (block 456).
- the method in Figure 4 uses function calls from the invitation API 282 to receive the invitation.
- an invitee may choose to receive invitations from a specific subset of contacts, all contacts, or no contacts at all.
- the invitation API 282 determines if the endpoint supports the requested activity 406 through a query to the capability store 212.
- the Capabilities API 284 may make such a determination by checking for a matching GUID in the capabilities store 212 shown in Figure 2. If not supported (e.g., no appropriate matching GUID found), the invitation API 282 of the listener sends the calling function (invitor) a decline message at block 408.
- the invitation API 282 may permit the invitor, upon determining that the requested activity is not supported by the invitee endpoint, to provide information regarding where the invitee may obtain an application which may support that activity.
- the invitation may include a URL, or other useful information, to allow the invitee to acquire or install an appropriate application supporting the activity.
- the invitee may choose to install the appropriate application, which may further have a GUID.
- Protective measures may further guard against newer applications overwriting GUID 's of existing applications.
- the invitee may acknowledge the invitation, perhaps via a dialog box, by accepting, rejecting, or ignoring 410.
- a decline message may be sent at block 408 in which the message may further describe potential reasons for the decline (e.g., activity is not supported at this endpoint, user did not allow the activity, etc.).
- the response may also be sent automatically by the invitee through a default setting (e.g., always reject invitations from Bob to play Halo ® ).
- the invitee may accept all invitations by default, reject all invitations by default, or ignore all invitations by default.
- the invitee may have a default setting of accept, reject or ignore based on the specific identity of the inviter.
- the invitee may choose to accept all invitations by default if the inviter is a buddy, reject all invitations by default if the inviter is unknown (not in the invitee's contact store), or ignore an invitation by default if the inviter is an in-law.
- environment variables are set and the application supporting the activity is launched at block 412. The application reads the environment variables at block 414, sends back acceptance notification 416 and starts its collaborative activity at block 418.
- the Capabilities API 284 may be called at block 414 to obtain relevant information, discussed in further detail below.
- the messenger application may already have appropriate environment variables. As such, blocks 426 through 428 accomplish receipt of the invitation and initiation of the collaborative activity. Similarly, blocks 456 through 466 may execute if the invitee already happens to have the application running that supports the collaborative activity. In such a case, the method does not need to query the invitee's endpoint for the application supporting the collaborative activity because it is already running, but the invitee may still choose to accept, reject, or ignore at block 460. [0043] Returning briefly to block 310 of Figure 3 and blocks 406 and 430 of Figure 4, the Capabilities API 284 determines whether the endpoint supports a requested activity.
- the Capabilities API 284 may include functions for registration, unregistration, enumeration of capabilities, and retrieval of information regarding the capabilities.
- a peer registration function may allow a user entity to add an entry to an operating system registry containing information relating to the capabilities supported by a particular application. Additionally, this information may include a GUID to identify the application, application configuration, and a description of the capability. The peer registration function may further allow the user entity to specify which other user entities or contacts may access the registered application. Alternatively, the user entity may unregister capabilities with an unregister function which removes the capability information from the registry.
- a user entity may call, via the application 280, a capability query function to learn about application capabilities when the GUID is known. However, the user entity may first call a capability enumeration function to obtain a list of all capabilities currently registered at an endpoint, including the endpoint of the user entity. The user entity may then select one capability from the enumerated list and call the capability query function for more specific capability information supported by that particular application.
- the following exemplary scenario illustrates invitation API functionality.
- a user entity named Toby has friends named Bob and Alice in his contacts list.
- Bob and Alice have each allowed publication of their presence information, and Toby notices that Bob is online and has the game Halo ® installed.
- Toby selects Bob from his contact list and sends an invitation to Bob containing a request to play Halo ® .
- the invitation API 282 determines that no endpoint connection is currently available and, consequently, employs the Communication Module 260 which may use PNRP to resolve an endpoint from Bob's contact information in Toby's contact store.
- the Communication Module 260 may optionally authenticate a connection via the Authentication System 270 between Bob and Toby and then send the invitation.
- the Capabilities API 284 is called to verify that Halo ® is supported on Bob's computer. If it is supported, the invitation API 282 presents Toby with an option (via a pop-up user interface) to "accept,” “reject,” or “ignore” the invitation. Bob accepts, the Halo ® application is launched, and an "accept” message is returned to the invitor (Toby).
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020077023813A KR101251689B1 (en) | 2005-04-22 | 2006-04-20 | An application programming interface for inviting participants in a serverless peer to peer network |
EP06750716A EP1872499A4 (en) | 2005-04-22 | 2006-04-20 | An application programming interface for inviting participants in a serverless peer to peer network |
JP2008507839A JP2008538637A (en) | 2005-04-22 | 2006-04-20 | Application programming interface for inviting participants to a serverless peer-to-peer network |
CN200680013652.2A CN101495967B (en) | 2005-04-22 | 2006-04-20 | Application programming interface for inviting participants in a serverless peer to peer network |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/112,347 | 2005-04-22 | ||
US11/112,347 US8036140B2 (en) | 2005-04-22 | 2005-04-22 | Application programming interface for inviting participants in a serverless peer to peer network |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2006115934A2 true WO2006115934A2 (en) | 2006-11-02 |
WO2006115934A3 WO2006115934A3 (en) | 2009-04-16 |
Family
ID=37186816
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2006/014742 WO2006115934A2 (en) | 2005-04-22 | 2006-04-20 | An application programming interface for inviting participants in a serverless peer to peer network |
Country Status (6)
Country | Link |
---|---|
US (1) | US8036140B2 (en) |
EP (1) | EP1872499A4 (en) |
JP (1) | JP2008538637A (en) |
KR (1) | KR101251689B1 (en) |
CN (1) | CN101495967B (en) |
WO (1) | WO2006115934A2 (en) |
Families Citing this family (43)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7571228B2 (en) | 2005-04-22 | 2009-08-04 | Microsoft Corporation | Contact management in a serverless peer-to-peer system |
US8036140B2 (en) | 2005-04-22 | 2011-10-11 | Microsoft Corporation | Application programming interface for inviting participants in a serverless peer to peer network |
US7617281B2 (en) * | 2005-04-25 | 2009-11-10 | Microsoft Corporation | System and method for collaboration with serverless presence |
US7752253B2 (en) * | 2005-04-25 | 2010-07-06 | Microsoft Corporation | Collaborative invitation system and method |
US8015247B1 (en) * | 2006-05-24 | 2011-09-06 | Aol Inc. | Joint communication sessions |
US20080091445A1 (en) * | 2006-10-16 | 2008-04-17 | Matthew Mihic | Method and system for dynamic social networking based on similar travel itineraries |
US8856224B2 (en) * | 2007-03-05 | 2014-10-07 | Core Wireless Licensing S.A.R.L. | Implementing a multi-user communications service |
US9770655B2 (en) * | 2007-10-01 | 2017-09-26 | Disney Enterprises, Inc. | Mesh synchronization |
EP2234375A1 (en) * | 2009-03-24 | 2010-09-29 | Thomson Licensing | device and method for controlling dissemination of content data between peers in a P2P mode, by using a two-level randomized peer overlay and a dynamic unchoke mechanism |
JP5423444B2 (en) * | 2010-02-04 | 2014-02-19 | 株式会社リコー | Network system, server device, and groupware program |
EP2437457A1 (en) * | 2010-09-29 | 2012-04-04 | Research In Motion Limited | Method to exchange application specific information for outgoing calls between two mobile devices |
EP2445149B1 (en) * | 2010-10-25 | 2015-03-04 | BlackBerry Limited | System and method for enabling applications to communicate using a peer-to-peer (P2P) system |
US9449288B2 (en) | 2011-05-20 | 2016-09-20 | Deem, Inc. | Travel services search |
MY155584A (en) * | 2011-09-26 | 2015-11-03 | Mimos Berhad | A system and method for performing ad-hoc screen switching & sharing |
US9250983B2 (en) * | 2012-06-01 | 2016-02-02 | Blackberry Limited | System and method for sharing items between electronic devices |
JP6505963B2 (en) * | 2012-12-28 | 2019-04-24 | 任天堂株式会社 | INFORMATION PROCESSING APPARATUS, INFORMATION PROCESSING SYSTEM, INFORMATION PROCESSING PROGRAM, AND INFORMATION PROCESSING METHOD |
US9264289B2 (en) * | 2013-06-27 | 2016-02-16 | Microsoft Technology Licensing, Llc | Endpoint data centers of different tenancy sets |
US20160014059A1 (en) * | 2015-09-30 | 2016-01-14 | Yogesh Chunilal Rathod | Presenting one or more types of interface(s) or media to calling and/or called user while acceptance of call |
US10725809B2 (en) * | 2014-12-27 | 2020-07-28 | Huawei Technologies Co., Ltd. | Application interaction method and apparatus, and terminal |
CN107432043B (en) * | 2015-05-19 | 2021-04-09 | 华为技术有限公司 | NAN device and paging method between NAN devices |
WO2016190657A1 (en) * | 2015-05-26 | 2016-12-01 | 김태정 | Terminal and method for operating terminal |
US9734000B2 (en) * | 2015-06-18 | 2017-08-15 | Microsoft Technology Licensing, Llc | Seamless transitions between applications and devices |
US9733915B2 (en) | 2015-07-02 | 2017-08-15 | Microsoft Technology Licensing, Llc | Building of compound application chain applications |
US10261985B2 (en) | 2015-07-02 | 2019-04-16 | Microsoft Technology Licensing, Llc | Output rendering in dynamic redefining application |
US9733993B2 (en) | 2015-07-02 | 2017-08-15 | Microsoft Technology Licensing, Llc | Application sharing using endpoint interface entities |
US9785484B2 (en) | 2015-07-02 | 2017-10-10 | Microsoft Technology Licensing, Llc | Distributed application interfacing across different hardware |
US9658836B2 (en) | 2015-07-02 | 2017-05-23 | Microsoft Technology Licensing, Llc | Automated generation of transformation chain compatible class |
US9860145B2 (en) | 2015-07-02 | 2018-01-02 | Microsoft Technology Licensing, Llc | Recording of inter-application data flow |
US9712472B2 (en) | 2015-07-02 | 2017-07-18 | Microsoft Technology Licensing, Llc | Application spawning responsive to communication |
US10198252B2 (en) | 2015-07-02 | 2019-02-05 | Microsoft Technology Licensing, Llc | Transformation chain application splitting |
US10031724B2 (en) | 2015-07-08 | 2018-07-24 | Microsoft Technology Licensing, Llc | Application operation responsive to object spatial status |
US10198405B2 (en) | 2015-07-08 | 2019-02-05 | Microsoft Technology Licensing, Llc | Rule-based layout of changing information |
US10277582B2 (en) | 2015-08-27 | 2019-04-30 | Microsoft Technology Licensing, Llc | Application service architecture |
US10915584B2 (en) * | 2015-09-22 | 2021-02-09 | Dropbox, Inc. | Event-related document generation |
US11019305B2 (en) * | 2018-01-12 | 2021-05-25 | Facebook, Inc. | Coordinated effects in videos |
US11372698B2 (en) * | 2018-01-12 | 2022-06-28 | Meta Platforms, Inc. | Coordinated effects in experiences |
US11386233B2 (en) | 2019-04-30 | 2022-07-12 | JFrog, Ltd. | Data bundle generation and deployment |
US11886390B2 (en) | 2019-04-30 | 2024-01-30 | JFrog Ltd. | Data file partition and replication |
US11340894B2 (en) | 2019-04-30 | 2022-05-24 | JFrog, Ltd. | Data file partition and replication |
US10999314B2 (en) | 2019-07-19 | 2021-05-04 | JFrog Ltd. | Software release tracking and logging |
US10972289B2 (en) | 2019-07-19 | 2021-04-06 | JFrog, Ltd. | Software release verification |
US11695829B2 (en) * | 2020-01-09 | 2023-07-04 | JFrog Ltd. | Peer-to-peer (P2P) downloading |
US11860680B2 (en) | 2020-11-24 | 2024-01-02 | JFrog Ltd. | Software pipeline and release validation |
Family Cites Families (242)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4874963A (en) | 1988-02-11 | 1989-10-17 | Bell Communications Research, Inc. | Neuromorphic learning networks |
JP2517410B2 (en) | 1989-05-15 | 1996-07-24 | 三菱電機株式会社 | Integrated circuit device with learning function |
US5386542A (en) | 1991-10-31 | 1995-01-31 | International Business Machines Corporation | System for generating a time reference value in the MAC layer of an ISO/OSI communications model among a plurality of nodes |
US5369705A (en) | 1992-06-03 | 1994-11-29 | International Business Machines Corporation | Multi-party secure session/conference |
CA2098461A1 (en) * | 1992-06-17 | 1993-12-18 | Antony S. Williams | Method and system for registering data formats for objects |
AU7684094A (en) | 1993-09-24 | 1995-04-10 | Oracle Corporation | Method and apparatus for data replication |
US5689641A (en) | 1993-10-01 | 1997-11-18 | Vicor, Inc. | Multimedia collaboration system arrangement for routing compressed AV signal through a participant site without decompressing the AV signal |
US5371794A (en) | 1993-11-02 | 1994-12-06 | Sun Microsystems, Inc. | Method and apparatus for privacy and authentication in wireless networks |
US5944794A (en) | 1994-09-30 | 1999-08-31 | Kabushiki Kaisha Toshiba | User identification data management scheme for networking computer systems using wide area network |
US6658568B1 (en) | 1995-02-13 | 2003-12-02 | Intertrust Technologies Corporation | Trusted infrastructure support system, methods and techniques for secure electronic commerce transaction and rights management |
US5854898A (en) | 1995-02-24 | 1998-12-29 | Apple Computer, Inc. | System for automatically adding additional data stream to existing media connection between two end points upon exchange of notifying and confirmation messages therebetween |
US5907685A (en) | 1995-08-04 | 1999-05-25 | Microsoft Corporation | System and method for synchronizing clocks in distributed computer nodes |
US5712914A (en) | 1995-09-29 | 1998-01-27 | Intel Corporation | Digital certificates containing multimedia data extensions |
US6097811A (en) | 1995-11-02 | 2000-08-01 | Micali; Silvio | Tree-based certificate revocation system |
US5790785A (en) | 1995-12-11 | 1998-08-04 | Customer Communications Group, Inc. | World Wide Web registration information processing system |
US6148323A (en) | 1995-12-29 | 2000-11-14 | Hewlett-Packard Company | System and method for managing the execution of system management |
AU734654B2 (en) | 1996-02-09 | 2001-06-21 | Integrated Technologies Of America, Inc. | Access control/crypto system |
US5706462A (en) | 1996-02-23 | 1998-01-06 | Microsoft Corporation | Self optimizing font width cache |
US5761421A (en) | 1996-03-25 | 1998-06-02 | Sun Microsystems, Inc. | System and method for secure peer-to-peer communication between downloaded programs |
US6016505A (en) | 1996-04-30 | 2000-01-18 | International Business Machines Corporation | Program product to effect barrier synchronization in a distributed computing environment |
US6189034B1 (en) * | 1996-05-08 | 2001-02-13 | Apple Computer, Inc. | Method and apparatus for dynamic launching of a teleconferencing application upon receipt of a call |
US6085320A (en) | 1996-05-15 | 2000-07-04 | Rsa Security Inc. | Client/server protocol for proving authenticity |
US5917480A (en) | 1996-06-04 | 1999-06-29 | Microsoft Corporation | Method and system for interacting with the content of a slide presentation |
US5748736A (en) | 1996-06-14 | 1998-05-05 | Mittra; Suvo | System and method for secure group communications via multicast or broadcast |
US5901227A (en) | 1996-06-20 | 1999-05-04 | Novell, Inc. | Method and apparatus for implementing partial and complete optional key escrow |
US5832514A (en) | 1996-06-26 | 1998-11-03 | Microsoft Corporation | System and method for discovery based data recovery in a store and forward replication process |
JP3497338B2 (en) | 1997-01-08 | 2004-02-16 | 株式会社日立製作所 | Network system with distributed log batch management function |
US5922074A (en) | 1997-02-28 | 1999-07-13 | Xcert Software, Inc. | Method of and apparatus for providing secure distributed directory services and public key infrastructure |
US5982898A (en) | 1997-03-07 | 1999-11-09 | At&T Corp. | Certification process |
JP3457493B2 (en) | 1997-03-18 | 2003-10-20 | 富士通株式会社 | ARP server |
US5933849A (en) | 1997-04-10 | 1999-08-03 | At&T Corp | Scalable distributed caching system and method |
US6134658A (en) | 1997-06-09 | 2000-10-17 | Microsoft Corporation | Multi-server location-independent authentication certificate management system |
US5987376A (en) | 1997-07-16 | 1999-11-16 | Microsoft Corporation | System and method for the distribution and synchronization of data and state information between clients in a distributed processing system |
US6092201A (en) | 1997-10-24 | 2000-07-18 | Entrust Technologies | Method and apparatus for extending secure communication operations via a shared list |
US6141760A (en) | 1997-10-31 | 2000-10-31 | Compaq Computer Corporation | System and method for generating unique passwords |
US6128740A (en) | 1997-12-08 | 2000-10-03 | Entrust Technologies Limited | Computer security system and method with on demand publishing of certificate revocation lists |
US6163809A (en) | 1997-12-08 | 2000-12-19 | Microsoft Corporation | System and method for preserving delivery status notification when moving from a native network to a foreign network |
US6078948A (en) | 1998-02-03 | 2000-06-20 | Syracuse University | Platform-independent collaboration backbone and framework for forming virtual communities having virtual rooms with collaborative sessions |
US6088805A (en) | 1998-02-13 | 2000-07-11 | International Business Machines Corporation | Systems, methods and computer program products for authenticating client requests with client certificate information |
US6216110B1 (en) | 1998-02-27 | 2001-04-10 | Microsoft Corporation | System and method for publishing calendar information to a publicly accessible location |
US6108687A (en) | 1998-03-02 | 2000-08-22 | Hewlett Packard Company | System and method for providing a synchronized display to a plurality of computers over a global computer network |
US6205481B1 (en) | 1998-03-17 | 2001-03-20 | Infolibria, Inc. | Protocol for distributing fresh content among networked cache servers |
US6012096A (en) | 1998-04-23 | 2000-01-04 | Microsoft Corporation | Method and system for peer-to-peer network latency measurement |
US6532217B1 (en) | 1998-06-29 | 2003-03-11 | Ip Dynamics, Inc. | System for automatically determining a network address |
US6269099B1 (en) | 1998-07-01 | 2001-07-31 | 3Com Corporation | Protocol and method for peer network device discovery |
US6148383A (en) | 1998-07-09 | 2000-11-14 | International Business Machines Corporation | Storage system employing universal timer for peer-to-peer asynchronous maintenance of consistent mirrored storage |
US6463078B1 (en) | 1998-07-22 | 2002-10-08 | Microsoft Corporation | Method for switching protocols transparently in multi-user applications |
US6155840A (en) | 1998-09-18 | 2000-12-05 | At Home Corporation | System and method for distributed learning |
US6266420B1 (en) | 1998-10-08 | 2001-07-24 | Entrust Technologies Limited | Method and apparatus for secure group communications |
US6219706B1 (en) | 1998-10-16 | 2001-04-17 | Cisco Technology, Inc. | Access control for networks |
JP2000148012A (en) | 1998-11-12 | 2000-05-26 | Fuji Xerox Co Ltd | Device and method for authentication |
US6363352B1 (en) | 1998-11-13 | 2002-03-26 | Microsoft Corporation | Automatic scheduling and formation of a virtual meeting over a computer network |
US6044350A (en) | 1998-12-24 | 2000-03-28 | Pitney Bowes Inc. | Certificate meter with selectable indemnification provisions |
US6937597B1 (en) * | 1999-02-26 | 2005-08-30 | Lucent Technologies Inc. | Signaling method for internet telephony |
US6775782B1 (en) | 1999-03-31 | 2004-08-10 | International Business Machines Corporation | System and method for suspending and resuming digital certificates in a certificate-based user authentication application system |
US6721890B1 (en) | 1999-05-04 | 2004-04-13 | Microsoft Corporation | Application specific distributed firewall |
US6564261B1 (en) | 1999-05-10 | 2003-05-13 | Telefonaktiebolaget Lm Ericsson (Publ) | Distributed system to intelligently establish sessions between anonymous users over various networks |
US6920455B1 (en) | 1999-05-19 | 2005-07-19 | Sun Microsystems, Inc. | Mechanism and method for managing service-specified data in a profile service |
EP1183816A4 (en) | 1999-05-26 | 2005-09-14 | Ascom Hasler Mailing Sys Inc | Technique for split knowledge backup and recovery of a cryptographic key |
US6892230B1 (en) | 1999-06-11 | 2005-05-10 | Microsoft Corporation | Dynamic self-configuration for ad hoc peer networking using mark-up language formated description messages |
US6725281B1 (en) | 1999-06-11 | 2004-04-20 | Microsoft Corporation | Synchronization of controlled device state using state table and eventing in data-driven remote device control model |
US6910068B2 (en) | 1999-06-11 | 2005-06-21 | Microsoft Corporation | XML-based template language for devices and services |
US6636888B1 (en) | 1999-06-15 | 2003-10-21 | Microsoft Corporation | Scheduling presentation broadcasts in an integrated network environment |
US6529950B1 (en) | 1999-06-17 | 2003-03-04 | International Business Machines Corporation | Policy-based multivariate application-level QoS negotiation for multimedia services |
US6990514B1 (en) | 1999-09-03 | 2006-01-24 | Cisco Technology, Inc. | Unified messaging system using web based application server for management of messages using standardized servers |
US6654796B1 (en) | 1999-10-07 | 2003-11-25 | Cisco Technology, Inc. | System for managing cluster of network switches using IP address for commander switch and redirecting a managing request via forwarding an HTTP connection to an expansion switch |
US6675205B2 (en) | 1999-10-14 | 2004-01-06 | Arcessa, Inc. | Peer-to-peer automated anonymous asynchronous file sharing |
US6683865B1 (en) | 1999-10-15 | 2004-01-27 | Nokia Wireless Routers, Inc. | System for routing and switching in computer networks |
US7159022B2 (en) * | 2001-01-26 | 2007-01-02 | American Power Conversion Corporation | Method and system for a set of network appliances which can be connected to provide enhanced collaboration, scalability, and reliability |
EP1234251B1 (en) | 1999-11-03 | 2011-04-06 | Sublinks ApS | Method, system, and computer readable medium for managing resource links |
US6526411B1 (en) | 1999-11-15 | 2003-02-25 | Sean Ward | System and method for creating dynamic playlists |
EP1107512A1 (en) | 1999-12-03 | 2001-06-13 | Sony International (Europe) GmbH | Communication device and software for operating multimedia applications |
US6704293B1 (en) * | 1999-12-06 | 2004-03-09 | Telefonaktiebolaget Lm Ericsson (Publ) | Broadcast as a triggering mechanism for route discovery in ad-hoc networks |
US6581110B1 (en) | 1999-12-07 | 2003-06-17 | International Business Machines Corporation | Method and system for reading and propagating authenticated time throughout a worldwide enterprise system |
US6754829B1 (en) | 1999-12-14 | 2004-06-22 | Intel Corporation | Certificate-based authentication system for heterogeneous environments |
US6636889B1 (en) | 2000-01-04 | 2003-10-21 | International Business Machines Corporation | System and method for client replication of collaboration space |
US20010035976A1 (en) | 2000-02-15 | 2001-11-01 | Andrew Poon | Method and system for online presentations of writings and line drawings |
US6745178B1 (en) | 2000-04-28 | 2004-06-01 | International Business Machines Corporation | Internet based method for facilitating networking among persons with similar interests and for facilitating collaborative searching for information |
US7159223B1 (en) | 2000-05-12 | 2007-01-02 | Zw Company, Llc | Methods and systems for applications to interact with hardware |
JP2001326632A (en) | 2000-05-17 | 2001-11-22 | Fujitsu Ltd | Distribution group management system and method |
GB2365671A (en) | 2000-05-17 | 2002-02-20 | Ibm | Teleconferencing system and method |
CN1300677C (en) | 2000-06-22 | 2007-02-14 | 微软公司 | Distributed computing services platform |
US6968179B1 (en) | 2000-07-27 | 2005-11-22 | Microsoft Corporation | Place specific buddy list services |
US6701344B1 (en) | 2000-07-31 | 2004-03-02 | The Boeing Company | Distributed game environment |
US6714966B1 (en) | 2000-07-31 | 2004-03-30 | The Boeing Company | Information delivery service |
US6944662B2 (en) | 2000-08-04 | 2005-09-13 | Vinestone Corporation | System and methods providing automatic distributed data retrieval, analysis and reporting services |
AU2001289146A1 (en) | 2000-08-18 | 2002-03-04 | Sage Systems, Inc. | Autonomous local area distributed network |
US7194689B2 (en) | 2000-08-22 | 2007-03-20 | Microsoft Corporation | Generic user control point tool for universal plug and play (UPnP) devices |
AUPR070300A0 (en) * | 2000-10-12 | 2000-11-09 | Vale Statutory & Mining Services Pty Limited | Post cap |
US20030018725A1 (en) * | 2000-10-20 | 2003-01-23 | Tod Turner | System and method for using an instant messaging environment to establish a hosted application sharing session |
US7194649B2 (en) | 2000-10-30 | 2007-03-20 | International Business Machines Corporation | Clock synchronization for network measurements with clock resets |
GB2372846A (en) | 2000-11-15 | 2002-09-04 | Vhsoft I P Company Ltd | Selective distribution of electronic files via a common access platform |
US6490253B1 (en) | 2000-11-22 | 2002-12-03 | Seagate Technology Llc | Peer to peer interconnect diagnostics |
WO2002044892A2 (en) * | 2000-11-28 | 2002-06-06 | 4Thpass Inc. | Method and system for maintaining and distributing wireless applications |
US7171475B2 (en) | 2000-12-01 | 2007-01-30 | Microsoft Corporation | Peer networking host framework and hosting API |
US6636854B2 (en) | 2000-12-07 | 2003-10-21 | International Business Machines Corporation | Method and system for augmenting web-indexed search engine results with peer-to-peer search results |
US20020073204A1 (en) | 2000-12-07 | 2002-06-13 | Rabindranath Dutta | Method and system for exchange of node characteristics for DATA sharing in peer-to-peer DATA networks |
US20020078243A1 (en) | 2000-12-15 | 2002-06-20 | International Business Machines Corporation | Method and apparatus for time synchronization in a network data processing system |
US6675261B2 (en) | 2000-12-22 | 2004-01-06 | Oblix, Inc. | Request based caching of data store data |
US7925703B2 (en) | 2000-12-26 | 2011-04-12 | Numedeon, Inc. | Graphical interactive interface for immersive online communities |
US7127676B2 (en) | 2000-12-29 | 2006-10-24 | International Business Machines Corporation | Method and system for providing a separate browser window with information from the main window in a simpler format |
US7020686B2 (en) | 2000-12-29 | 2006-03-28 | International Business Machines Corporation | Method and system for providing synchronous communication and person awareness in a place |
US6791582B2 (en) | 2000-12-29 | 2004-09-14 | International Business Machines Corporation | Method and system for identifying and displaying information that is new or has been updated in a place |
US7275102B2 (en) | 2001-01-22 | 2007-09-25 | Sun Microsystems, Inc. | Trust mechanisms for a peer-to-peer network computing platform |
WO2002057917A2 (en) | 2001-01-22 | 2002-07-25 | Sun Microsystems, Inc. | Peer-to-peer network computing platform |
US20020116461A1 (en) | 2001-02-05 | 2002-08-22 | Athanassios Diacakis | Presence and availability management system |
US20040205243A1 (en) | 2001-03-09 | 2004-10-14 | Hans Hurvig | System and a method for managing digital identities |
US7302634B2 (en) | 2001-03-14 | 2007-11-27 | Microsoft Corporation | Schema-based services for identity-based data access |
US7478243B2 (en) | 2001-03-21 | 2009-01-13 | Microsoft Corporation | On-disk file format for serverless distributed file system with signed manifest of file modifications |
US6981043B2 (en) | 2001-03-27 | 2005-12-27 | International Business Machines Corporation | Apparatus and method for managing multiple user identities on a networked computer system |
US7065587B2 (en) | 2001-04-02 | 2006-06-20 | Microsoft Corporation | Peer-to-peer name resolution protocol (PNRP) and multilevel cache for use therewith |
US7085925B2 (en) | 2001-04-03 | 2006-08-01 | Sun Microsystems, Inc. | Trust ratings in group credentials |
US7272636B2 (en) | 2001-04-24 | 2007-09-18 | Sun Microsystems, Inc. | Peer group name server |
US7171415B2 (en) | 2001-05-04 | 2007-01-30 | Sun Microsystems, Inc. | Distributed information discovery through searching selected registered information providers |
US20040205167A1 (en) * | 2001-05-29 | 2004-10-14 | Doug Grumann | Automatic configuration of performance management tools |
GB2378268B (en) | 2001-06-04 | 2005-08-03 | Gordon Ross | A method of providing an interactive multi dimensional visual user interface to groups of users |
US6801604B2 (en) | 2001-06-25 | 2004-10-05 | International Business Machines Corporation | Universal IP-based and scalable architectures across conversational applications using web services for speech and audio processing resources |
US6842460B1 (en) * | 2001-06-27 | 2005-01-11 | Nokia Corporation | Ad hoc network discovery menu |
US6957261B2 (en) | 2001-07-17 | 2005-10-18 | Intel Corporation | Resource policy management using a centralized policy data structure |
US7346658B2 (en) | 2001-08-08 | 2008-03-18 | At&T Delaware Intellectual Property, Inc. | System and method for notifying an offline global computer network user of an online interaction |
WO2003017522A2 (en) * | 2001-08-16 | 2003-02-27 | Flarion Technologies, Inc. | Methods and apparatus for controlling ip applications during resource shortages |
US20030036941A1 (en) | 2001-08-17 | 2003-02-20 | International Business Machines Corporation | System and method for scheduling multiple meetings on an electronic calendar |
US7299351B2 (en) | 2001-09-19 | 2007-11-20 | Microsoft Corporation | Peer-to-peer name resolution protocol (PNRP) security infrastructure and method |
US7068789B2 (en) | 2001-09-19 | 2006-06-27 | Microsoft Corporation | Peer-to-peer name resolution protocol (PNRP) group security infrastructure and method |
US7493363B2 (en) | 2001-09-19 | 2009-02-17 | Microsoft Corporation | Peer-to-peer group management and method for maintaining peer-to-peer graphs |
US6982982B1 (en) * | 2001-10-23 | 2006-01-03 | Meshnetworks, Inc. | System and method for providing a congestion optimized address resolution protocol for wireless ad-hoc networks |
US6771666B2 (en) * | 2002-03-15 | 2004-08-03 | Meshnetworks, Inc. | System and method for trans-medium address resolution on an ad-hoc network with at least one highly disconnected medium having multiple access points to other media |
US7181620B1 (en) | 2001-11-09 | 2007-02-20 | Cisco Technology, Inc. | Method and apparatus providing secure initialization of network devices using a cryptographic key distribution approach |
US7337402B2 (en) | 2001-11-09 | 2008-02-26 | Microsoft Corporation | Tunable information presentation appliance using an extensible markup language |
US7962605B2 (en) | 2001-11-20 | 2011-06-14 | Microsoft Corporation | Distributed device discovery framework for a network |
US20030217096A1 (en) | 2001-12-14 | 2003-11-20 | Mckelvie Samuel J. | Agent based application using data synchronization |
JP3967589B2 (en) | 2001-12-28 | 2007-08-29 | 富士通株式会社 | Advertisement distribution method and advertisement distribution apparatus |
US20030126027A1 (en) | 2001-12-31 | 2003-07-03 | Kimberly-Clark Worldwide | Integrated web ring site and method for presenting information |
US20030140119A1 (en) | 2002-01-18 | 2003-07-24 | International Business Machines Corporation | Dynamic service discovery |
US7194002B2 (en) | 2002-02-01 | 2007-03-20 | Microsoft Corporation | Peer-to-peer based network performance measurement and analysis system and method for large scale networks |
US7055134B2 (en) * | 2002-03-14 | 2006-05-30 | Sap Ag | Service provider integration framework in object oriented programming environment |
US7233979B2 (en) | 2002-03-14 | 2007-06-19 | Microsoft Corporation | Instant messaging session invite for arranging peer-to-peer communication between applications |
JP2003271531A (en) | 2002-03-18 | 2003-09-26 | Nec Corp | Message server, message system, presence information management method and program |
US20040128350A1 (en) | 2002-03-25 | 2004-07-01 | Lou Topfl | Methods and systems for real-time virtual conferencing |
US7130999B2 (en) | 2002-03-27 | 2006-10-31 | Intel Corporation | Using authentication certificates for authorization |
AU2003222159A1 (en) * | 2002-04-02 | 2003-10-20 | Worldcom, Inc. | Messaging response system |
US20030191753A1 (en) | 2002-04-08 | 2003-10-09 | Michael Hoch | Filtering contents using a learning mechanism |
US6912622B2 (en) | 2002-04-15 | 2005-06-28 | Microsoft Corporation | Multi-level cache architecture and cache management method for peer-to-peer name resolution protocol |
US7213060B2 (en) | 2002-04-23 | 2007-05-01 | Canon Kabushiki Kaisha | Web based creation of printer instances on a workstation |
US7206862B2 (en) * | 2002-04-24 | 2007-04-17 | Microsoft Corporation | Method and apparatus for efficiently matching responses to requests previously passed by a network node |
US7051102B2 (en) | 2002-04-29 | 2006-05-23 | Microsoft Corporation | Peer-to-peer name resolution protocol (PNRP) security infrastructure and method |
US20030217073A1 (en) | 2002-05-14 | 2003-11-20 | Walther Dan E. | Increasing the level of automation when scheduling and managing meetings |
US20030217142A1 (en) | 2002-05-15 | 2003-11-20 | Microsoft Corporation | Method and system for supporting the communication of presence information regarding one or more telephony devices |
US6983400B2 (en) | 2002-05-16 | 2006-01-03 | Sun Microsystems Inc. | Distributed test harness model |
US7277404B2 (en) | 2002-05-20 | 2007-10-02 | Airdefense, Inc. | System and method for sensing wireless LAN activity |
US7346696B2 (en) | 2002-05-21 | 2008-03-18 | At&T Deleware Intellectual Property, Inc. | Group access management system |
GB2391135B (en) | 2002-06-28 | 2006-01-11 | Nokia Corp | User group creation |
US20040111423A1 (en) | 2002-07-13 | 2004-06-10 | John Irving | Method and system for secure, community profile generation and access via a communication system |
US20040019640A1 (en) | 2002-07-25 | 2004-01-29 | Bartram Linda Ruth | System and method for distributing shared storage for collaboration across multiple devices |
GB0218711D0 (en) | 2002-08-12 | 2002-09-18 | Mitel Knowledge Corp | System and method for facilitating communication using presence and communication services |
US6986258B2 (en) | 2002-08-29 | 2006-01-17 | Nanomix, Inc. | Operation of a hydrogen storage and supply system |
US7020480B2 (en) | 2002-09-19 | 2006-03-28 | Research In Motion Limited | Apparatus and method of wireless instant messaging |
US7206934B2 (en) | 2002-09-26 | 2007-04-17 | Sun Microsystems, Inc. | Distributed indexing of identity information in a peer-to-peer network |
US8204992B2 (en) | 2002-09-26 | 2012-06-19 | Oracle America, Inc. | Presence detection using distributed indexes in peer-to-peer networks |
DE60312355T2 (en) | 2002-10-11 | 2007-11-08 | Nokia Corp. | DYNAMIC PEER TUNNELING WITH PERFORMANCE OPTIMIZATION |
US20040078436A1 (en) | 2002-10-18 | 2004-04-22 | International Business Machines Corporation | Adding meeting information to a meeting notice |
US7249123B2 (en) | 2002-10-31 | 2007-07-24 | International Business Machines Corporation | System and method for building social networks based on activity around shared virtual objects |
US8037202B2 (en) | 2002-10-31 | 2011-10-11 | Oracle America, Inc. | Presence detection using mobile agents in peer-to-peer networks |
DE50211524D1 (en) | 2002-11-16 | 2008-02-21 | Minebea Co Ltd | Miniature motor with permanent magnet rotor |
US20040172456A1 (en) | 2002-11-18 | 2004-09-02 | Green Mitchell Chapin | Enhanced buddy list interface |
US20040143603A1 (en) | 2002-11-21 | 2004-07-22 | Roy Kaufmann | Method and system for synchronous and asynchronous note timing in a system for enhancing collaboration using computers and networking |
US7062681B2 (en) | 2002-12-03 | 2006-06-13 | Microsoft Corporation | Method and system for generically reporting events occurring within a computer system |
US7613812B2 (en) | 2002-12-04 | 2009-11-03 | Microsoft Corporation | Peer-to-peer identity management interfaces and methods |
US7430747B2 (en) | 2002-12-04 | 2008-09-30 | Microsoft Corporation | Peer-to peer graphing interfaces and methods |
US7099881B2 (en) | 2002-12-06 | 2006-08-29 | Stmicroelectronics, Inc. | Method for increasing average storage capacity in a bit-mapped tree-based storage engine by using remappable prefix representations and a run-length encoding scheme that defines multi-length fields to compactly store IP prefixes |
US8095409B2 (en) | 2002-12-06 | 2012-01-10 | Insors Integrated Communications | Methods and program products for organizing virtual meetings |
US20040111525A1 (en) | 2002-12-09 | 2004-06-10 | International Business Machines Corporation | Dynamic web service implementation discovery and selection apparatus and method |
US20040120344A1 (en) | 2002-12-20 | 2004-06-24 | Sony Corporation And Sony Electronics, Inc. | Device discovery application interface |
US20040122901A1 (en) | 2002-12-20 | 2004-06-24 | Nortel Networks Limited | Providing computer presence information to an integrated presence system |
US7209948B2 (en) | 2002-12-20 | 2007-04-24 | International Business Machines, Corporation | Collaborative review of distributed content |
US20040141005A1 (en) | 2003-01-22 | 2004-07-22 | International Business Machines Corporation | System and method for integrating online meeting materials in a place |
DE602004026131D1 (en) | 2003-01-22 | 2010-05-06 | Nec Corp | attendance system |
US7596625B2 (en) | 2003-01-27 | 2009-09-29 | Microsoft Corporation | Peer-to-peer grouping interfaces and methods |
US7139760B2 (en) | 2003-01-27 | 2006-11-21 | Microsoft Corporation | Peer-to-peer record structure and query language for searching and discovery thereof |
US7437440B2 (en) | 2003-01-27 | 2008-10-14 | Microsoft Corporation | Peer-to-peer networking framework application programming interfaces |
US7701882B2 (en) | 2003-02-10 | 2010-04-20 | Intercall, Inc. | Systems and methods for collaborative communication |
US7774495B2 (en) | 2003-02-13 | 2010-08-10 | Oracle America, Inc, | Infrastructure for accessing a peer-to-peer network environment |
US20040172452A1 (en) * | 2003-02-28 | 2004-09-02 | Erickson Paul R. | Service provider model for real-time services |
JP2004265174A (en) | 2003-03-03 | 2004-09-24 | Nippon Telegr & Teleph Corp <Ntt> | Communication device, service control method, agent program of communication device and recording medium having agent program recorded thereon |
US8308567B2 (en) | 2003-03-05 | 2012-11-13 | Wms Gaming Inc. | Discovery service in a service-oriented gaming network environment |
US20040184445A1 (en) | 2003-03-18 | 2004-09-23 | Burne Jeffrey K. | Computer algorithm and method for facilitating the networking of individuals |
US7603417B2 (en) | 2003-03-26 | 2009-10-13 | Aol Llc | Identifying and using identities deemed to be known to a user |
US7245622B2 (en) | 2003-03-27 | 2007-07-17 | Microsoft Corporation | Allowing IPv4 clients to communicate over an IPv6 network when behind a network address translator with reduced server workload |
US7216147B2 (en) | 2003-03-27 | 2007-05-08 | Microsoft Corporation | Controlling publication of presence information |
US20040249953A1 (en) | 2003-05-14 | 2004-12-09 | Microsoft Corporation | Peer-to-peer instant messaging |
US20040228531A1 (en) | 2003-05-14 | 2004-11-18 | Microsoft Corporation | Instant messaging user interfaces |
US7539771B2 (en) | 2003-06-06 | 2009-05-26 | Microsoft Corporation | Organizational locality in prefix-based structured peer-to-peer overlays |
US7418486B2 (en) | 2003-06-06 | 2008-08-26 | Microsoft Corporation | Automatic discovery and configuration of external network devices |
US7533184B2 (en) * | 2003-06-13 | 2009-05-12 | Microsoft Corporation | Peer-to-peer name resolution wire protocol and message format data structure for use therein |
US20040255029A1 (en) | 2003-06-16 | 2004-12-16 | Microsoft Corporation | Discovery and control protocol for intelligent displays |
US7337213B2 (en) | 2003-06-19 | 2008-02-26 | International Business Machines Corporation | Method and apparatus for managing messages in a messaging session |
US7363378B2 (en) * | 2003-07-01 | 2008-04-22 | Microsoft Corporation | Transport system for instant messaging |
US20050004968A1 (en) | 2003-07-02 | 2005-01-06 | Jari Mononen | System, apparatus, and method for a mobile information server |
KR100568229B1 (en) * | 2003-07-10 | 2006-04-07 | 삼성전자주식회사 | A Method And System for Dynamically Refreshing ARP Cash Table on Ad-hoc Network |
US20050009537A1 (en) | 2003-07-11 | 2005-01-13 | Crocker Ronald T. | Method and apparatus for facilitating wireless presence-based services |
US20050027805A1 (en) | 2003-07-15 | 2005-02-03 | Aoki Norihiro Edwin | Instant messaging and enhanced scheduling |
US8254276B2 (en) * | 2003-08-05 | 2012-08-28 | Qualcomm Incorporated | Packet data services using version and capability information |
US7512653B2 (en) | 2003-08-11 | 2009-03-31 | Sony Corporation | System and method for dynamically grouping messaging buddies in an electronic network |
US7546343B2 (en) | 2003-09-23 | 2009-06-09 | Alcatel-Lucent Usa Inc. | System and method for supporting virtual conferences |
US8688786B2 (en) | 2003-09-25 | 2014-04-01 | Oracle America, Inc. | Method and system for busy presence state detection in an instant messaging system |
US8443087B2 (en) | 2003-10-09 | 2013-05-14 | Rockstar Consortium Us Lp | System for managing sessions and connections in a network |
US20050080768A1 (en) | 2003-10-10 | 2005-04-14 | International Business Machines Corporation | Methods and apparatus for dynamic service discovery from Web services representation chain |
US7200638B2 (en) | 2003-10-14 | 2007-04-03 | International Business Machines Corporation | System and method for automatic population of instant messenger lists |
US8260857B2 (en) | 2003-10-23 | 2012-09-04 | Microsoft Corporation | One to many data projection system and method |
US7496648B2 (en) | 2003-10-23 | 2009-02-24 | Microsoft Corporation | Managed peer name resolution protocol (PNRP) interfaces for peer to peer networking |
US7949996B2 (en) | 2003-10-23 | 2011-05-24 | Microsoft Corporation | Peer-to-peer identity management managed interfaces and methods |
US7336623B2 (en) | 2003-10-30 | 2008-02-26 | Microsoft Corporation | Peer-to-peer cloud-split detection and repair methods |
KR20060107529A (en) | 2003-11-06 | 2006-10-13 | 코닌클리케 필립스 일렉트로닉스 엔.브이. | Bandwidth-saving discovery on dual-stack upnp devices |
US20050102245A1 (en) | 2003-11-07 | 2005-05-12 | International Business Machines Corporation | System, method, and service for negotiating schedules while preserving privacy through a shared representation |
US20050114487A1 (en) | 2003-11-12 | 2005-05-26 | Jin Peng | Notification framework and method of distributing notification |
US7720906B2 (en) * | 2003-11-24 | 2010-05-18 | Microsoft Corporation | Web service for remote application discovery |
US7475125B2 (en) | 2003-11-24 | 2009-01-06 | Microsoft Corporation | Seamless discovery of workstation-installed remote applications from an extranet |
US20050138119A1 (en) * | 2003-12-23 | 2005-06-23 | Nokia Corporation | User-location service for ad hoc, peer-to-peer networks |
US20050198173A1 (en) | 2004-01-02 | 2005-09-08 | Evans Alexander W. | System and method for controlling receipt of electronic messages |
US7885901B2 (en) | 2004-01-29 | 2011-02-08 | Yahoo! Inc. | Method and system for seeding online social network contacts |
US20050177715A1 (en) | 2004-02-09 | 2005-08-11 | Microsoft Corporation | Method and system for managing identities in a peer-to-peer networking environment |
US20050182967A1 (en) | 2004-02-13 | 2005-08-18 | Microsoft Corporation | Network security device and method for protecting a computing device in a networked environment |
US7933290B2 (en) | 2004-03-30 | 2011-04-26 | Nokia Corporation | System and method for comprehensive service translation |
US20050223086A1 (en) * | 2004-03-31 | 2005-10-06 | Raverdy Pierre G | Discovering nearby hosts and applications for impromptu interactions using well-known ad-hoc network configuration |
CN1926835B (en) * | 2004-04-05 | 2012-02-22 | 艾利森电话股份有限公司 | Method, communication device and system for address resolution mapping in a wireless multihop self-organizing network |
EP1587239A1 (en) | 2004-04-14 | 2005-10-19 | Siemens Mobile Communications S.p.A. | Method of and apparatus for server-side management of buddy lists |
US8316088B2 (en) * | 2004-07-06 | 2012-11-20 | Nokia Corporation | Peer-to-peer engine for object sharing in communication devices |
US7603466B2 (en) * | 2004-07-19 | 2009-10-13 | Sap (Ag) | Mobile collaborative peer-to-peer business applications |
US7451186B2 (en) | 2004-08-10 | 2008-11-11 | Microsoft Corporation | Method and system of integrating instant messaging with other computer programs |
US20060112177A1 (en) | 2004-11-24 | 2006-05-25 | Microsoft Corporation | Method and system for controlling access to presence information on a peer-to-peer basis |
US20060182113A1 (en) * | 2005-02-17 | 2006-08-17 | Lucent Technologies Inc. | Automatic discovery of pseudo-wire peer addresses in ethernet-based networks |
US20060190600A1 (en) | 2005-02-18 | 2006-08-24 | Siemens Communications, Inc. | Group based presence availability management |
US20060212583A1 (en) | 2005-03-17 | 2006-09-21 | Beadle Bruce A | Distributing messaging session logs to users entering an already ongoing messaging session |
US8547997B2 (en) | 2005-04-20 | 2013-10-01 | Jupiter Systems | Capture node for use in an audiovisual signal routing and distribution system |
US7571228B2 (en) | 2005-04-22 | 2009-08-04 | Microsoft Corporation | Contact management in a serverless peer-to-peer system |
US20060242235A1 (en) | 2005-04-22 | 2006-10-26 | Microsoft Corporation | Presence monitoring in a serverless peer-to-peer system |
US8036140B2 (en) | 2005-04-22 | 2011-10-11 | Microsoft Corporation | Application programming interface for inviting participants in a serverless peer to peer network |
US20060242236A1 (en) | 2005-04-22 | 2006-10-26 | Microsoft Corporation | System and method for extensible computer assisted collaboration |
US20060245235A1 (en) | 2005-05-02 | 2006-11-02 | Advanced Micro Devices, Inc. | Design and operation of a resistance switching memory cell with diode |
US20070239869A1 (en) | 2006-03-28 | 2007-10-11 | Microsoft Corporation | User interface for user presence aggregated across multiple endpoints |
US7945612B2 (en) | 2006-03-28 | 2011-05-17 | Microsoft Corporation | Aggregating user presence across multiple endpoints |
US20080005325A1 (en) | 2006-06-28 | 2008-01-03 | Microsoft Corporation | User communication restrictions |
-
2005
- 2005-04-22 US US11/112,347 patent/US8036140B2/en active Active
-
2006
- 2006-04-20 WO PCT/US2006/014742 patent/WO2006115934A2/en active Application Filing
- 2006-04-20 CN CN200680013652.2A patent/CN101495967B/en active Active
- 2006-04-20 KR KR1020077023813A patent/KR101251689B1/en active IP Right Grant
- 2006-04-20 EP EP06750716A patent/EP1872499A4/en not_active Withdrawn
- 2006-04-20 JP JP2008507839A patent/JP2008538637A/en active Pending
Non-Patent Citations (1)
Title |
---|
None |
Also Published As
Publication number | Publication date |
---|---|
WO2006115934A3 (en) | 2009-04-16 |
US20060239295A1 (en) | 2006-10-26 |
EP1872499A2 (en) | 2008-01-02 |
JP2008538637A (en) | 2008-10-30 |
KR20070118262A (en) | 2007-12-14 |
CN101495967A (en) | 2009-07-29 |
KR101251689B1 (en) | 2013-04-05 |
CN101495967B (en) | 2013-05-08 |
US8036140B2 (en) | 2011-10-11 |
EP1872499A4 (en) | 2009-12-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8036140B2 (en) | Application programming interface for inviting participants in a serverless peer to peer network | |
US20060239234A1 (en) | Application programming interface for discovering endpoints in a serverless peer to peer network | |
US7752253B2 (en) | Collaborative invitation system and method | |
US7814214B2 (en) | Contact management in a serverless peer-to-peer system | |
JP2013513313A (en) | System and method for combining instant messaging system and video communication system | |
US20060242237A1 (en) | System and method for collaboration with serverless presence | |
US20060242235A1 (en) | Presence monitoring in a serverless peer-to-peer system | |
US8447814B2 (en) | Remote control using instant messaging | |
US10404631B2 (en) | Creating groups in a messaging system | |
MXPA05011167A (en) | Mixed massaging mode for multiple points of presence. | |
US7593988B2 (en) | Systems and methods for multiparty session invite | |
US7962556B2 (en) | Instant messaging session initiation using a proxy session request | |
US20060242236A1 (en) | System and method for extensible computer assisted collaboration | |
JP2006244100A (en) | Presence information distribution system | |
WO2018132304A1 (en) | Creating groups in a messaging system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 200680013652.2 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2006750716 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2008507839 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020077023813 Country of ref document: KR |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
NENP | Non-entry into the national phase |
Ref country code: RU |