EP2533493B1 - Mobility Extension von Näherungssitzungen - Google Patents

Mobility Extension von Näherungssitzungen Download PDF

Info

Publication number
EP2533493B1
EP2533493B1 EP12169860.9A EP12169860A EP2533493B1 EP 2533493 B1 EP2533493 B1 EP 2533493B1 EP 12169860 A EP12169860 A EP 12169860A EP 2533493 B1 EP2533493 B1 EP 2533493B1
Authority
EP
European Patent Office
Prior art keywords
conference
whiteboard
devices
contact
processor
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP12169860.9A
Other languages
English (en)
French (fr)
Other versions
EP2533493A1 (de
Inventor
Trung Trinh
Alain Michaud
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Mitel Networks Corp
Original Assignee
Mitel Networks Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US13/134,396 external-priority patent/US10225354B2/en
Application filed by Mitel Networks Corp filed Critical Mitel Networks Corp
Publication of EP2533493A1 publication Critical patent/EP2533493A1/de
Application granted granted Critical
Publication of EP2533493B1 publication Critical patent/EP2533493B1/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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/40—Support for services or applications
    • H04L65/401—Support for services or applications wherein the services involve a main real-time session and one or more additional parallel real-time or time sensitive sessions, e.g. white board sharing or spawning of a subconference
    • H04L65/4015—Support for services or applications wherein the services involve a main real-time session and one or more additional parallel real-time or time sensitive sessions, e.g. white board sharing or spawning of a subconference where at least one of the additional parallel sessions is real time or time sensitive, e.g. white board sharing, collaboration or spawning of a subconference
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G06F21/33—User authentication using certificates
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4594—Address books, i.e. directories containing contact information about correspondents
    • 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/1083—In-session procedures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/023—Services making use of location information using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
    • H04W4/21—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel for social networking applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/12—WLAN [Wireless Local Area Networks]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/69—Identity-dependent
    • H04W12/77—Graphical identity

Definitions

  • the present invention generally relates to communications, and more particularly, but not exclusively, to an extended system and method for seamlessly exchanging and interacting with multimedia content between devices in proximity on a network.
  • FTP File Transfer Protocol
  • HTTP Hypertext Transfer Protocol
  • HTTP Hypertext Transfer Protocol
  • VPN Virtual Private Network
  • RDP Remote Desktop Protocol
  • EP 1708528 discloses a system for authenticating a device based on tokens received from other devices in a local network.
  • the present invention relates to communications. More specifically, but not exclusively, this invention relates to proximity session mobility.
  • a system and method for seamless exchange and interaction of multimedia content between communication devices in a network is provided.
  • the method can include the discovery and identification of devices within proximity of a sending device.
  • the found devices can be authenticated through unique identifiers established during registration. Connection requirements can be determined based on the identifiers associated with the found devices and the sending device.
  • the sender can establish a connection with the found devices using the connection requirements.
  • the exchanged content can be, but is not limited to, multimedia based information, applications, contacts, virtual desktop sessions, remote desktop sessions or virtual mobile sessions.
  • the sending device can share or serve as a remote control to redirect and navigate the content, with a simple action or a gesture command, to the found device.
  • the shared multimedia content can either reside on the sender's mobile device or on a remote server within a connected network.
  • the multimedia sharing supports one-to-one and one-to-many topologies.
  • telephony applications can be tied in with session mobility.
  • whiteboards on each of the devices can be integrated seamlessly.
  • the mobile phone can also act as a remote control to bring contacts into the conference call thereby leveraging the mobile phone's native interface without the need to know the destination number of the conference device. Participants being brought into the conference can be provided with the proper context of the current interaction/presentation. Context information can be shown visually or presented audibly.
  • the conferencing appliance can turn into a temporary wireless (also referred to herein as WiFi®) access point or end point for conveniently connecting the user's mobile device to a corporate network in a restricted and secured way.
  • WiFi® temporary wireless
  • Figures 1 , 5 and 7 Exemplary systems for exchanging content will be described in Figures 1 , 5 and 7 .
  • Figures 2 through 4 will provide exemplary procedures for establishing a communication channel between devices.
  • Figure 6 discloses procedures for establishing a streaming session between devices while
  • Figure 8 provides procedures for a reverse lookup for proper identification of a receiver.
  • Figure 9 discloses procedures for seamlessly enabling a WiFi® communication between devices and
  • Figure 10 provides procedures for white boarding from a mobile device to share information to the participants on the call.
  • Devices can be referred to in this disclosure as communication devices that can be mobile or not. These devices can include tablets, mobile phones, smartphones, personal digital assistants, handheld computers, standalone computers, conference devices or the like.
  • the communication devices can also be referred to as sending devices and receiving or found devices.
  • the system 100 can include an identity server module 104 operating on a server 102 that can be wirelessly connected to a plurality of communication devices 106 and 110 having exchange agent modules 108 and 112. Communications between them can be facilitated through a wireless interface 114 distributed within proximity of the devices 106 and 110. Fewer or more components can be represented within the system 100 and are not limited to those shown. For example, while two devices 106 and 110 have been provided, many more can be shown each interconnected with one another through communication channels defined by the identity server module 104.
  • Proximity session mobility can be applied to any devices 106 and 110. It is desirable or often necessary for applications to share data between these services.
  • the modules 108 and 112, or at least components thereon, can be used as add-ons to existing applications or devices 106 and 110.
  • the exchange agent modules 108 and 112 running thereon can be downloaded onto existing mobile phones and or added to conference phones.
  • the wireless interface 114 in association with the identity server module 104 on the server 102, can connect components within the system 100. Communications between the devices 106 and 110 and to the server 102 can be facilitated through the interface 114.
  • the interface 114 can connect with the server 102 wirelessly or through a wireline connection.
  • the identity server module 104 can operate on a traditional server 102.
  • the server 102 can include an operating system and software instructions, memory, at least one processor and a network interface.
  • the server can process requests and typically handle high volumes of transactions and large amount of queries for communication and data processing.
  • the identity server module 104 can provide information such as a device's name, number, Internet Protocol (IP) address and potentially, location.
  • IP Internet Protocol
  • the module 104 can also provide a mechanism by which the devices 106 and 110 can establish a communication channel.
  • the location of the devices 106 and 110 can be determined by observing one device paired with a static device such as a conference phone.
  • the location information can be used to enhance the session experience by leveraging what the area has to offer, for example, local printers. This information can be used to populate presence information.
  • the exchange agent modules 108 and 112 on the communication devices 106 and 110 can be responsible for identifying devices in proximity and managing the sharing protocol. Operationally, each of the devices 106 and 110 can maintain a wireless interface for communication with one another and the identity server module 104 on the server 102. Referring to Figure 2 , a flow chart depicting illustrative procedures for setting up these devices 106 and 110 in accordance with one or more embodiments of the present invention is provided. The procedures can begin at block 200.
  • the exchange agent modules 108 and 112 can be downloaded or pre-installed on each of the devices 106 and 110.
  • the communication devices 106 and 110 can register with the identity server module 104 which assigns the device a unique device address or identifier. These identifiers can be referred to as tokens with usages for these tokens becoming apparent from the disclosure provided below.
  • the devices 106 and 110 can be registered with the module 104 using a number of different techniques.
  • the exchange agent module 108 on the sending device 106 can scan for devices 110 at block 202.
  • the exchange agent module 108 on the sending device 106 can scan for nearby devices to identify available receiving devices 110 within proximity.
  • Numerous types of scanning techniques can be used by the sending device 106.
  • the scanning techniques can include near field communications (NFC), BluetoothTM, graphical tag recognition, facial recognition and global positioning system (GPS) signaling or wireless networks, depending on the options and the state (on/off) of protocols available on the receiving devices 110.
  • NFC near field communications
  • BluetoothTM graphical tag recognition
  • GPS global positioning system
  • Information about receiving devices 110 can be reported back to the sending device 106. These found devices 110 can be displayed on a graphical display of the sending device 106 along with any other information about the receiving devices 110 in proximity with proper user identity which is stored in the identity server 102. For example, the sending device 106 can locate a number of different devices in proximity, but only those that have registered with the identity server module 104 are shown on the display of the sending device 106. After scanning is completed, the exchange agent module 108 on the sending device 106 now has a unique token for found devices 110. At block 204, these tokens are retrieved. These unique tokens as described earlier can be the information that was provided by the identity server module 104 when the devices 110 were registered. These tokens can then be sent to the identity server module 104 at block 206. The identity server module 104 can pull up information or communicate with all devices 106 and 110 given that the identifiers for them are known. The procedures can end at block 208.
  • the identity server module 104 can send or push updates to known devices 106 and 110 so that they can communicate with each other. This can include auto pairing the BluetoothTM radios on the devices 106 and 110 using the identity server module 104 as a mediator. Uniform resource links or IP addresses for the communication devices 106 and 110 can be sent to another device.
  • FIG. 3 is a flow chart depicting illustrative procedures for establishing a communication channel between the devices 106 and 110 in accordance with one or more embodiments of the present invention. The procedures can begin at block 300.
  • the exchange agent module 108 on the sending device 106 can use the previously identified information to validate the receiving device 110 with the identity server module 104 and collect more information for connection requirements.
  • the sending device 106 can determine whether the receiving device 110 within the previous scan was registered properly.
  • the receiving device 110 should have been registered, as guest or known account, with the identity server module 104 on the server 102 prior to communicating with the sending device 106.
  • the identity server module 104 on the server 102 prior to communicating with the sending device 106.
  • MAC Media Access Control
  • the identity server module 104 can also provide a temporary tag which acts as an identifier for the device 110 at block 306.
  • the assigned tag can be used by other devices, for example, via a camera scanning method.
  • the tag can contain an address or a Uniform Resource Identifier (URI) referencing the other device. It can also be used to derive the address or URI via a reverse lookup.
  • URI Uniform Resource Identifier
  • the temporary guest account can also be established for the sending device 106 and can be setup through similar methods.
  • the identity server module 104 can receive identification of a sending device 106 from an incoming query.
  • the identity server module 104 can know the identification of both parties through the query.
  • the first identification can be obtained from the incoming query which contains the identification such as the token, IP address, MAC address etc. of the sending device 106.
  • the identification of the receiving device 110 can be obtained from the message payload which contains the identifier for the receiving device 110 at block 310.
  • the identity server module 104 can initiate a background operation to link both devices via a communication channel at block 312.
  • the exchange agent module 108 on the sending device can then establish the sharing connection with the exchange agent module 112 on the receiving device 110.
  • the procedures can end at block 314.
  • the channel established between the sending device 106 and the receiving device 110 can either be peer-to-peer or client-server based.
  • the communication channel between the devices 106 and 110 is accomplished via a Transmission Control Protocol (TCP)/User Datagram Protocol (UDP) connection or Short Message Service (SMS) messaging.
  • TCP Transmission Control Protocol
  • UDP User Datagram Protocol
  • SMS Short Message Service
  • the connection can be terminated either by the sending device 106 or by a proximity detection mechanism or remotely via an administrative interface on the server 102 having the identity server module 104.
  • activity on the sending device 106 can be monitored by the receiving device 110 or identity server module 104 such that after a period of inactivity the session can be closed. Alternatively, the sending device 106 can disconnect itself after the period of inactivity.
  • FIG. 4 is a flow chart depicting illustrative procedures for sharing information on a user interface provided by an exchange agent module 108 in accordance with one or more embodiments of the present invention. The procedures can begin at block 400. With a connection established, a graphical display can show depictions of the identified or receiving device 110 so that a user of the sending device 106 can either drag the application or media to be shared to the receiving devices 110 or drag the receiving devices 110 to the application or media to be shared at block 402. Instructions can be provided on the display of the sending device 106.
  • the sending device 106 can determine whether the user has dragged the device 110 to the application or the application to the device 110.
  • the display can provide graphical representations of both.
  • the sending device 106 provides read only content to the receiving device 110.
  • the sending device 106 provides content which can be presented as read and write enabled to the receiving device 110.
  • Other techniques can be implemented for content sharing. For example, a menu or button click can replace the dragging technique.
  • the procedures can end at block 410.
  • the receiving devices 110 can view and discard the provided information from the sending device 106. In one embodiment, the receiving devices 110 can save the content if the sending device 106 allows it prior to starting the shared session. For dynamic content, the receiving device 110 can edit, discard or push back the content to the sender or vice versa.
  • the proximity session mobility feature can be disabled remotely from the server 102 having the identity server module 104 in case of a lost or stolen device.
  • the exchange agent modules 108 and 112 on the communication devices 106 and 110, or at least a portion thereof, can be implemented as a background service.
  • the background service can wait for input from either the identity server module 104 or associated/paired devices. This can allow the exchange agent modules 108 and 112 to be passive and do much if not all of the work with minimal user interaction.
  • an exemplary receiving device 110 in the form of a conference phone, and a sending device 106, in the form of a mobile phone, is presented.
  • the conference phone 110 can display a graphical representation of the mobile phone 106 in proximity as an identified device that can be shared.
  • the user can push a button on the conference phone 110 to confirm and their virtual remote desktop can show up on the conference phone 110.
  • the user of the mobile phone 106 can either use the conference phone keyboard to navigate the multimedia session or use the exchange agent module 108 to control the navigation.
  • the mobile phone user can either initiate a disconnect action from the exchange agent module 108 on the mobile phone 106, or just allow out-of-range proximity detection to be activated by walking away from the conference room with the device.
  • a sending device 106 and a receiving device 110 in the form of a conference appliance, not only can the user of the sending device 106 control the presentation on the receiving device 110, but they can also initiate a request to bring in their own contacts.
  • the sending device 106 from their mobile device's native interface or from a cloud network access application such as Google Mail®/contact feed, can import in data or contacts that can be connected into the conference call without actually making a phone call from the sending device 106 to a new user.
  • the sending device 106 typically does not need to know the conference call number.
  • the newly invited user can receive the call alert.
  • the user can receive the context in which the conference call takes place. For example, caller information (i.e. the name of mobile device owner instead of the caller id of the conference device), meeting participants, meeting topic/subject and the current discussion point such as a snap shot of the current presentation, can be provided to the newly invited party. Participant information can be presented in a number of forms. This information can be pulled off a centralized server and provided to the user.
  • caller information i.e. the name of mobile device owner instead of the caller id of the conference device
  • meeting participants meeting topic/subject and the current discussion point such as a snap shot of the current presentation
  • Participant information can be presented in a number of forms. This information can be pulled off a centralized server and provided to the user.
  • Telephony applications can be tied in with session mobility by using the mobile phone 106 as a remote control to bring contacts to the conference call leveraging the mobile phone's native interface without the need to know the destination number of the conference device 110. Participants being brought into the conference can be provided with a proper context of the current interaction/presentation. Context information can be shown visually or presented audibly. The mobile user should be able to bring in more participants to the conference using their native mobile phone contacts without requiring the mobile telephony channel since the mobile phone 106 is acting as a remote control.
  • the identity server module 104 can prevent some devices 106 from acting like remote controls and instead limit the scope of these devices, for example, a device can be delegated to a speaker such that those participants further away from the receiving device 110 would be able to hear the conversation for the conference.
  • the device can be prevented from enacting white boarding techniques. Other designations can be used to distinguish devices 106 connected with the receiving device 110 to limit their interactions with it.
  • the exchange agent module 108 on the sending device 106 can intercept the dialing process and collect the contact information for that number.
  • the contact can be automatically added into the conference, after being authorized by the user of the device 106.
  • the user after selecting a contact from their native contact application, the user can have the option to add a chosen contact directly into the conference without dialing their number, since the exchange agent module 108 on the sending device 106 can extend the native contact application.
  • the user can choose a contact from an aggregate list displayed in the user interface of the exchange agent module 108. This aggregate list can be a combination of local mobile device contacts, cloud-based contacts and enterprise contacts. This information can then be proxied to the receiving device 110 via the identity server module 104.
  • the receiving device 110 can then request a proxy dialing via consultation call.
  • the exchange agent module 112 on the receiving device 110 can have the necessary information about the current call, participants, context, etc. that can be passed to the newly invited contact via a data channel or text-to-speech (TTS) audio.
  • TTS text-to-speech
  • the system 500 can include an identity server module 104 operating on a server 102 that can be wirelessly connected to a plurality of communication devices 106 and 110 having exchange agent modules 108 and 112. Communications between them can be facilitated through a wireless interface 114 distributed within proximity of the devices 106 and 110.
  • the system 500 is the same as above with the addition of the streaming server 502 and streaming proxy 506. Fewer or more components can be represented within the system 100 and are not limited to those shown.
  • the previous system 100 can be altered for other applications such as video streaming redirection using the sending device 106 as a remote control.
  • the user of the sending device 106 can simply beam itself through its exchange agent module 108 to a receiving device 110, which can be in the form of a video conferencing unit.
  • the conferencing unit 110 can be connected to a monitor or projector that displays the sending device's desktop session for presentation to the rest of the participants.
  • the streaming server 502 can operate on a traditional server.
  • the server can include an operating system and software instructions, memory, at least one processor and a network interface.
  • the server can process requests and typically handle high volumes of transactions and large amount of queries for communication and data processing.
  • the streaming server 502 can be managed through the streaming proxy 506.
  • the streaming proxy 506 described herein can be implemented as logical operations and/or modules attached to the server 502 or can be implemented on a separate physical component itself.
  • the sending device 106 can be the user's link to their workspace or session. As the user moves, they retain the ability to project, forward and recall their session to and from other receiving devices 110.
  • a multimedia session can be a remote desktop session such as VMware ViewTM.
  • the streaming server 502 can be responsible for serving the multimedia data to a remote location.
  • the streaming server 502 can use a Remote Desktop Protocol (RDP), Personal Computer over Internet Protocol (PCoIP), Virtual Network Computing (VNC), etc.
  • RDP Remote Desktop Protocol
  • PCoIP Personal Computer over Internet Protocol
  • VNC Virtual Network Computing
  • the streaming proxy 506 can be responsible for redirecting and multicasting the traffic to a newer location identified by the exchange agent module 108.
  • the streaming proxy 506 can instruct the streaming server 502 to stop the current streaming and start a new one to a new end point destination address.
  • the streaming proxy 506 can redirect the streaming data between the streaming server 502 and the new end point devices.
  • FIG. 6 a flow chart depicting illustrative procedures for providing a streaming session in accordance with one or more embodiments of the present invention is provided.
  • the procedures can begin at block 600.
  • the procedures described herein can be interchanged and are not limited to the disclosed embodiments.
  • the streaming server 502 can be serving content to the remote desktop session on the PC 504 as depicted in Figure 5 .
  • the receiving device 110 can register with the identity server module 104, which assigns the device 110 to a unique address.
  • the exchange agent module 108 on the sending device 106 can scan for nearby devices to identify available receiving devices 110 within proximity.
  • the exchange agent module 108 on the sending device 106 can use the identified information to validate with the identity server module 104 operating on the server 102.
  • the identity server module 104 can collect more information for the reconnection requirements.
  • a sender operating the sending device 106 can press a share button which activates the request to the streaming proxy 506.
  • the streaming proxy 506 can receive the activation request.
  • the streaming proxy 506 can provide the request to the streaming server 502 for redirection with provided destination information at block 604.
  • the streaming server 502 can disconnect the connection to the PC 504 at block 606 and start streaming the remote session to the receiving device 110 at block 608.
  • the procedures can end at block 610.
  • a PC 504 can initially display a virtual or physical desktop session running from their work station.
  • the user can point their mobile device 106 to the conferencing device 110 with the installed exchange agent module 108.
  • the exchange agent module 108 on the mobile device 106 can display a graphical representation of the conferencing device 110 in proximity as an identified device that can be shared.
  • the user can direct the exchange agent module 108 on the mobile device 106 to initiate a sharing session.
  • the user's virtual or physical remote desktop can start projecting on the conference device's screen.
  • the user can then either use the conference device's keyboard to navigate the presentation or use their same mobile phone application to control the navigation.
  • the multimedia session can be recorded on a server and or transcoded in real-time. This can allow other participants without the required clients to view the multimedia content in a read only mode.
  • the video can be broadcasted to an authenticated or anonymous web server. The video can then be rendered via an HTML5 video tag and displayed natively in any HTML5 browser without the need for plugins or the like.
  • the sending device 106 can provide additional input to the session in the form a remote pointer.
  • PBX private branch exchange
  • SIP session initiation protocol
  • the extension can be used to do a reverse look up for the device's address.
  • the extension can be programmed in a user sending device's contact list.
  • the mobile application on the sending device 106 then can be extended to allow a sharing action in addition to the normal list of actions such as dial, chat, etc. This sharing action can provide seamless sharing session activation.
  • FIG. 7 is an exemplary system 700 for providing a reverse lookup to establish a communication channel in accordance with one or more embodiments of the present invention.
  • the system 700 can include an identity server module 104 operating on a server 102 that can be wirelessly connected to a plurality of communication devices 106 and 110 having exchange agent modules 108 and 112. Communications between them can be facilitated through a wireless interface 114 distributed within proximity of the devices 106 and 110. Fewer or more components can be represented within the system 100 and are not limited to those shown.
  • QR code 702 can be a matrix barcode readable by a dedicated reader provided on the sending device 106.
  • the code 702 can consist of black modules arranged in a square pattern on a white background.
  • Other methods known to those skilled in the relevant art can be used to identify a user of the receiving device 110.
  • the receiver can be detected through facial recognition using a photo 704 provided on the device 110 or through a picture taken by the sending device 106.
  • Figure 8 is a flow chart depicting illustrative procedures for setting up the communication channel using reverse lookup in accordance with one or more embodiments of the present invention.
  • the procedures can begin at block 800.
  • the sending device 106 can scan for receiving devices 110.
  • the sending device 106 can scan for the QR code 702 associated with the receiving device 110.
  • the sender can take a picture of the user's face or use the photo 704 provided on the receiving device 110.
  • a request can be built for the identity server module 104 that includes the receiving device's 110 tokens or other identification. The request can then be provided to the identity server module 104 at block 804.
  • the identity server module 104 can receive the request and perform a reverse lookup based on the token or identification in the request.
  • the identity server module 104 operating on the server 102 would data mine a picture database using various facial recognition algorithms known to those skilled in the relevant art.
  • a list of top candidates can be sent back to the sending device 106 along with their thumbnails.
  • the exchange agent module 108 can then provide a mechanism for the user to pick the correct candidate via a click, gestures etc.
  • the identity server module 104 can return a corresponding failure to the sending device 106 and the receiver is left untouched.
  • the code 702 can be sent to the identity server module 104 to be evaluated after retrieved by the sending device 106.
  • the exchange agent module 108 operating on the sending device 106 can be used to identify the receiving device 110. If the identity cannot be determined, a failure indicator is provided back to the sending device 106.
  • a combination of techniques for reverse lookup can be used.
  • the sending device 106 can determine whether the identity server module 104 has successfully identified the receiving device 110. This is generally provided by a successful indicator given by the identity server module 104. When the identity server module 104 cannot determine the user of the receiving device 110, the sending device 106 can provide a failure indicator to the sender at block 808. Upon successful identification, however, the identity server module 104 would know how to communicate with both devices 106 and 110 since their network addresses would be stored in its database. The identity server module 104 can act as a broker between both devices 106 and 110 in order to establish a communication channel at block 810.
  • the channel can forward initializations commands to each exchange agent module 108 and 112. These commands can include listening and allowing connections from the verified peer addresses.
  • the identity server module 104 can automate the pairing such that user input is minimized.
  • the commands sent from the server 102 to the devices 106 and 110 can involve, but are not limited to, enabling auto-discovery on the devices 106 and 110, obtaining information about perimeter devices from each exchange agent module 108 and 112, filtering out devices which are not part of the transaction, i.e. that are not the sending device 106 or the receiving device 110 and automatically pairing the devices 106 and 110.
  • Both exchange agent modules 108 and 112 can now communicate over an established data channel. The procedures can end at block 812.
  • the system 100 can contain at least three main modules, namely exchange agent modules 108 and 112 and the identity server module 104.
  • the exchange agent module 108 on the mobile device 106 can be responsible for identifying devices in proximity and manage the sharing protocol.
  • the sending device 106 can be the user mobile device while the receiving device 110 can be a conferencing appliance which can act as a SIP conferencing end point to a switch.
  • the identity server module 104 can provide information to connected devices 106 and 110 such as a device name, number, IP address presence, contact information and potential location. As described above, the identity server module 104 can also provide mechanisms by which the devices 106 and 110 can establish a communication channel. The identity server module 104 can also provide a temporary tag which acts as an identifier for the device. The tag can contain an address or URI referencing the other device. It could also be used to derive the address or URI via a reverse lookup. When queries are received, the identity server module 104 knows the identification of both parties. The first identification can be obtained from the incoming query which contains the identification of the sending device 106 such as a token, IP/MAC address, etc. The second identification can be obtained from the message payload and can contain the identification for the second device 110. With both identifications known, the identity server module 104 can initiate background operations to link both devices 106 and 110 via a communication channel.
  • Figure 7 also depicted a process to establish a WiFi® data channel between two mobile devices 106 and 110.
  • the sending device 106 can scan the QR code 702 from the remote device 110 or takes a picture of the user's face and build a request for the identity server module 104.
  • the identity server module 104 can receive the request and perform a reverse lookup based on the token or identification in the request.
  • the identity server module 104 can communicate with both devices 106 and 110 since their network addresses can be stored in its database.
  • the identity server module 104 can act as a broker between both devices 106 and 110 in order to setup a communication channel.
  • the receiving device 110 which can be a conferencing appliance, can be turned into an access point and the exchange agent module 108 on the sending device 106 can receive initialization commands. These commands can include listening and allowing connections from the verified peer address.
  • both exchange agent modules 108 and 112 can communicate over an established data channel.
  • Telephony and data applications can be further integrated within a mobility session to provide enhanced values and a seamless experience to the end users using or interacting with multimedia appliances.
  • a mobility session has been established between a device 106 and a conferencing appliance 110
  • contacts from the device 106 can be imported into the conference.
  • a user can initiate a request to bring in their own contacts into the conference call facilitated by the appliance 110 without actually making a phone call from the device 106 to the imported contact or needing to know the conferencing appliance's phone number.
  • the imported contact can receive the call alert with a context of the conference.
  • the context can include caller information, meeting participants, meeting topic/subject and the current discussion point such as a snap shot of the current presentation.
  • Operations on the guest's mobile/tablet device 106 can provide automation and seamless access application features that can be used to enhance productivity and interaction efficiency while containing data transfer cost.
  • the systems can be altered for other applications between the mobile and tablet devices 106.
  • a guest mobile user does not download an enterprise specific mobile application in order to use session mobility.
  • the conferencing appliance 110 in the case of an established session mobility, can be programmed to enable an access point from which guest mobile devices can have a temporary direct WiFi® access in a controlled method such that data security to an enterprise is not compromised.
  • the extended system and method provides the ability to tie in telephony applications with session mobility by using the mobile device 106 as a remote control to bring contacts to a conference call leveraging a mobile phone's native interface and without the need to know the destination number such as the conferencing appliance 110. Participants being brought into the conference can be provided with a proper context of the current interaction/presentation. Context information can be shown visually or presented audibly.
  • the conferencing appliance 110 can be an access point from which guest mobile users can have WiFi® connectivity without the need of temporary access identifications or manual registration.
  • This conferencing appliance 110 access point can proxy temporary data traffic between the mobile device 106 and the identity server module 104 thus containing the risk of unwanted data access to the rest of the enterprise.
  • WiFi® access enablement for the guest mobile device 106 can also be accomplished automatically as part of session mobility interaction. Once session mobility is established, the guest user can initiate a request to transfer data file from the mobile/tablet device 106 or from the cloud onto the virtual desktop session of the conferencing appliance 110 leveraging either WiFi® connectivity or a backend server connection to the cloud, thus incurring no mobile data cost.
  • the sending exchange agent module 108 can continue to use the carrier network to communicate to the identity server module 104 since it resides on the network edge. When that user enters the enterprise, they are able to use functions of the system. This can alleviate many of the security concerns with regards to untrusted/unknown clients on private networks. Since the identity server module 104 can act like a broker/proxy, remote sending clients can be unaware that receiving clients reside on the private network. This can provide a mechanism to access private networks in a secure fashion while remaining simple and intuitive to the user, for example, uploading a file to a view instance. When using thin clients, this can also provide a way to access a private network without the need to install native thick clients, for example, scanning the barcode on the device, entering the URL or indirectly accessing the network from the browser.
  • FIG. 9 is a sequence diagram depicting illustrative procedures for seamlessly enabling WiFi® communications between a stationary multimedia phone device 110 and a mobile phone 106 in accordance with one or more embodiments of the present invention. It is not trivial to allow seamless enterprise WiFi® access to an unknown/untrusted mobile device 106. However, the conferencing appliance 110, in the case of an established session mobility, can be programmed to enable an access point from which guest mobile devices 106 can have a temporary direct WiFi® access in a controlled method such that data security to an enterprise is not compromised.
  • the processes for providing a WiFi® connection can begin when the sender exchange agent module 108 enables WiFi® access at process 902.
  • the guest device 106 having the exchange agent module 108 can automatically make a request to the identity server module 104, after the establishment of a mobility session, to switch from 3/4G connectivity to WiFi® access seamlessly.
  • Other carrier services can be used to enable the WiFi® access.
  • the identity server module 104 can forward the request to the receiving exchange agent module 112 on the conferencing appliance 110.
  • the request can be proxied to the receiver exchange agent module 112.
  • the receiving exchange agent module 112 can enable a WiFi® mechanism for connecting with devices 106 at process 906.
  • the exchange agent module 112 can generate a random service set identifier (SSID).
  • the receiver exchange agent module 112 can report the status of the WiFi® connection to the identity server module 104. If the module 112 failed to establish a WiFi® connection, the module 112 can indicate to the sender exchange agent module 108 to continue to use its 3/4G connection. Otherwise, the exchange agent module 112 can report the successful connection by sending the randomly generated SSID and connection parameters to the identity server module 104.
  • the connection parameters can include an encryption algorithm for securing the communications between the sending device 106 and the conferencing appliance 110.
  • the SSID can be sent to the exchange agent module 108 of the sending device 106 by the identity server module 104 at process 910 along with the success indicator.
  • a WiFi® reachable address for the identity server module 104 can be provided to the sending exchange agent module 108 with the connection parameters including encryption algorithms.
  • the exchange agent module 108 on the sending device 106, at process 912, can enable the WiFi® connection through the given connection parameters and the SSID.
  • the 3/4G connection can be dropped in favor of a new re-established WiFi® connection with the identity server module 104 via the new address. This can remove costs associated with the 3/4G connection.
  • the signal strength from the conferencing appliance 110 having the receiver exchange agent module 112 can be controlled and fine tuned to an appropriate power level range which can confine the WiFi® access zone.
  • the mobile phone 106 can serve as, or be replaced by, a touchpad device that can also be used as a white boarding tool to project hand drawings to the conference participants without the need of additional software tools. Remote users can also view the whiteboard and interact with it.
  • the exchange agent module 108 can turn the screen on the sending device 106 to a touch pad for controlling the navigation of the content on the receiving device 110. This touch pad can also act as a whiteboard where hand drawings can be rendered into recognizable images and projected, by a push of a button, to the receiving device 110 via a web interface without the need of launching other external whiteboard applications.
  • Exchange agent modules 108 on multiple devices 106 can be native, thin or a combination of both.
  • the sender exchange agent module 108 can turn the screen of the sending device 106 to a touch pad for controlling the navigation of the content on the receiving device 110.
  • the device 106 is not given full control of the content. Instead, the content can be managed by an administrator, for example, a party that can but does not necessarily have to be near the conferencing appliance 110.
  • White boarding activities can begin at process 1002 where a request to start activity can be provided to the identity server module 104 from the sender exchange agent module 108.
  • the identity server module 104 can broadcast the request to exchange agent modules on connected devices 106 as well as that of the conferencing appliance 110 at process 1004.
  • the exchange agent module 112 on the conferencing appliance 110 can determine whether to connect with the device 106 sending the request.
  • a message can be provided to the device 106 through the identity server module 104 indicating reasons why its request was denied. For example, the appliance 110 can indicate that too many users are connected with the appliance 110. The appliance 110 can also indicate that the user of the device 106 does not have proper permissions or settings to whiteboard with the collaboration appliance 110. If successful, however, the collaboration appliance 110 can report the success by providing a message to the identity server module 104 at process 1006. The identity server module 104 can then forward the successful indicator through proxy to the sender exchange agent module 108 at process 1008.
  • the touch pad on the sending device 106 can allow hand drawings that can be rendered into recognizable images and projected, by a push of a button, to the receiving device 110 via a web interface without the need of launching other external whiteboard applications.
  • the sender exchange agent module 108 can be native, thin or a combination of both.
  • traffic can be minimized by not sending every point detected in a gesture or motion event. For example, instead of sending a series of points for a drawn circle, the type of circle can be sent along with its center coordinates and radius. This can yield clear visuals while providing a mechanism to export this data into an offline document for further manipulation, instead of a simple PNG/PDF, etc.
  • the exchange agent module 108 on the sending device 106 can send the hand drawings or recognized constructs to the identity service module 104.
  • the identity service module 104 can then provide those interactions on the whiteboard to peers of the device 106, for example, other connected devices 106 to the conferencing appliance 110. As shown in Figure 10 , changes can be sent to the conferencing appliance 110 where it can then be distributed to other connected devices 106.
  • the identity server module 104 can provide the hand drawings or constructs to the receiver exchange agent module 112 at process 1014.
  • the exchange agent module 112 can display in real-time received constructs or hand motions on the whiteboard of its display at process 1016.
  • the exchange agent module 108 on the sending device 106 can be enhanced to allow interaction with the native mobile applications in order to allow file synchronization when the user wants to project a file/presentation from their device to the receiving device 110 or when they wish to add a contact to the conference.
  • interactions on the whiteboard of the sending device 106 were sent to the conference appliance 112 through the identity service module 104.
  • the interactions were then displayed on the whiteboard of the conferencing appliance 112.
  • those interactions received from the sender device 106 can be propagated to other devices.
  • Those devices can be connected to the conferencing appliance 112 wirelessly through the identity service module 104 or through a network interface.
  • the network interface in turn, can be connected to outside devices not directly linked with the conferencing appliance 110, but through an outside network.
  • interactions can be provided directly on the whiteboard of the conferencing appliance 112. These interactions can then be distributed to devices 106 that also have whiteboards through the identity service module 104. In addition, the interactions can be provided to outside devices, as described above. The motions or gestures can be captured to form constructs. The constructs can then be provided to those devices.
  • the identity service module 104 can continuously update the devices.
  • the exchange agent modules 108 and 112 on the devices 106 and 110 can indicate whether an update to their whiteboard is available. The user can simply disregard any changes that they have made to their whiteboard in lieu of an update. Indicators showing which party making the update to the whiteboard can be provided to the devices. In one embodiment, changes can also be visible in real-time. Users do not have to commit their changes in order for them to appear on another user's whiteboard. A complete history of whiteboard activities in sequential and time-stamped order can be stored on the identity server module 104 to provide change history functionality with synchronized voice playback (if voice recording is enabled). This can provide rewind/fast forward functionalities and turn whiteboard sessions into instant webcasts for internal use.
  • the mobile device 106 can be used as a remote control to bring personal contacts to a conference.
  • other contacts can be added.
  • the exchange agent module 108 on the sender device 106 can be used to intercept the dialing process and collect the contact information for that number.
  • the contact number can be provided to the receiver exchange agent module 112 on the conferencing appliance 110 where the contact can be added into the conference. More than one contact can be added at a time.
  • a list of contacts can be provided on a native contact application on the device 106 instead of a call being made to the contact.
  • the user can have the option to add the chosen contact directly to the conference, since the exchange agent module 108 can extend the native contact application.
  • the user can choose a contact from an aggregate list displayed in the user interface of the exchange agent module 108. This aggregate list can be a combination of local mobile device contacts in addition to cloud based contacts and enterprise contacts.
  • This information can then be proxied to the receiving device 110 via the identity server module 104.
  • the conferencing appliance 110 can then request a proxy dialing via consultation call.
  • the exchange agent module 112 on the receiving device 110 can have the necessary information about the current call, the participants, the context, etc. that can be passed to the newly invited contact via data channel or TTS audio.
  • the technology described herein can be implemented as logical operations and/or modules.
  • the logical operations can be implemented as a sequence of processor-implemented steps executing in one or more computer systems and as interconnected machine or circuit modules within one or more computer systems.
  • the descriptions of various component modules can be provided in terms of operations executed or effected by the modules.
  • the resulting implementation is a matter of choice, dependent on the performance requirements of the underlying environment in which the described invention is implemented.
  • the logical operations making up the embodiments of the invention described herein are referred to variously as operations, steps, objects, or modules. It should be understood that logical operations can be performed in any order, unless explicitly claimed otherwise or a specific order is inherently necessitated by the claim language.
  • Various embodiments of the present invention can be programmed using an object-oriented programming language, such as SmallTalk, Java, C++, Ada, or C#. Other object-oriented programming languages can also be used. Alternatively, functional, scripting, and/or logical programming languages can be used.
  • object-oriented programming languages can also be used.
  • functional, scripting, and/or logical programming languages can be used.
  • Various aspects of this invention can be implemented in a non-programmed environment, for example, documents created in HTML, XML, or other format that, when viewed in a window of a browser program, render aspects of a GUI or perform other functions.
  • Various aspects of the invention can be implemented as programmed or non-programmed elements, or any combination thereof.
  • computer software and/or data is stored on a machine readable medium as part of a computer program product, and is loaded into a computer system or other device or machine via a removable storage drive, hard drive, or communications interface.
  • Computer programs also called computer control logic or computer readable program code, are stored in a main and/or secondary memory, and executed by one or more processors, controllers, or the like to cause the one or more processors to perform the functions of the invention as described herein.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Multimedia (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Computer Hardware Design (AREA)
  • Information Transfer Between Computers (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)

Claims (15)

  1. Gerät (106), das Folgendes beinhaltet:
    eine Anzeige;
    eine drahtlose Schnittstelle;
    mindestens einen Prozessor; und
    einen Speicher, der betriebsmäßig mit dem Prozessor gekoppelt ist, wobei der Speicher Programmanweisungen speichert, die, wenn vom Prozessor ausgeführt, verursachen, dass der Prozessor:
    auf der Anzeige ein Whiteboard bereitstellt;
    einen Kommunikationskanal durch die drahtlose Schnittstelle mit mindestens einem weiteren Gerät (110) in der Nähe über ein Identitätsmodul (104) aufbaut, um eine Konferenz aufzubauen;
    Informationen in der Konferenz auf dem Whiteboard mit dem mindestens einen weiteren Gerät durch den Kommunikationskanal austauscht; dadurch gekennzeichnet, dass
    Informationen in Bezug auf den Kontext der Konferenz für mindestens einen Kontakt des Geräts bereitgestellt werden, um den mindestens einen Kontakt der aufgebauten Konferenz hinzuzufügen;
    wobei die Kontextinformationen über das Identitätsmodul bereitgestellt werden.
  2. Gerät gemäß Anspruch 1, wobei das Austauschen der Informationen auf dem Whiteboard das Empfangen von Interaktionen von einem Whiteboard des mindestens einen weiteren Geräts (110) und das Anzeigen der Interaktionen auf dem Whiteboard der Anzeige beinhaltet, und wobei der Speicher, der Programmanweisungen speichert, wenn vom Prozessor ausgeführt, verursacht, dass der Prozessor die Interaktionen auf dem Whiteboard der Anzeige für andere Geräte bereitstellt.
  3. Gerät gemäß Anspruch 2, wobei der Speicher, der Programmanweisungen speichert, wenn vom Prozessor ausgeführt, verursacht, dass der Prozessor Konstrukte empfängt, die aus erfassten Bewegungen auf dem Whiteboard des mindestens einen weiteren Geräts (110) gebildet sind, und die Konstrukte auf dem Whiteboard der Anzeige anzeigt.
  4. Gerät gemäß Anspruch 1, wobei das Austauschen der Informationen auf dem Whiteboard das Bereitstellen von Interaktionen auf dem Whiteboard der Anzeige für ein Whiteboard auf dem mindestens einen weiteren Gerät beinhaltet und wobei der Speicher, der Programmanweisungen speichert, wenn vom Prozessor ausgeführt, verursacht, dass der Prozessor Bewegungen auf dem Whiteboard der Anzeige erfasst, aus den Bewegungen Konstrukte bildet und die Konstrukte für das Whiteboard auf dem mindestens einen Gerät bereitstellt.
  5. Gerät gemäß Anspruch 4, wobei der Speicher, der Programmanweisungen speichert, wenn vom Prozessor ausgeführt, verursacht, dass der Prozessor Informationen mit Kontakten auf einem äußeren Netzwerk austauscht.
  6. Verfahren zum Bringen von mindestens einem Kontakt in eine Konferenz durch ein Identitätsmodul, wobei das Verfahren Folgendes beinhaltet:
    Verlinken eines ersten Geräts (106) mit einem zweiten Gerät (110) in der Nähe zum ersten Gerät durch ein Identitätsmodul (104) durch einen Kommunikationskanal, um eine Konferenz aufzubauen; gekennzeichnet durch
    Bereitstellen von Informationen in Bezug auf den Kontext der Konferenz für mindestens einen Kontakt des ersten Geräts, wobei die Kontextinformationen durch das Identitätsmodul bereitgestellt werden;
    Hinzufügen des mindestens einen Kontakts zur aufgebauten Konferenz; und
    Austauschen von Informationen in der Konferenz auf einem Whiteboard, angezeigt auf dem ersten Gerät und des Kontakts des ersten Geräts.
  7. Verfahren gemäß Anspruch 6, das das Abfangen eines Anwählprozesses für den mindestens einen Kontakt und das Bestimmen, ob der mindestens eine Kontakt der Konferenz hinzugefügt werden soll, beinhaltet.
  8. Verfahren gemäß Anspruch 6, das das Anzeigen einer Vielzahl von Kontakten, die der Konferenz hinzuzufügen sind, und das Empfangen einer Benutzerauswahl für den mindestens einen Kontakt beinhaltet, wobei das Anzeigen der Vielzahl von Kontakten das Präsentieren von mindestens einem von lokalen Kontakten, Cloud-basierten Kontakten, Unternehmenskontakten und einer Kombination davon beinhaltet.
  9. Verfahren gemäß einem der Ansprüche 6 bis 8, wobei das Hinzufügen des mindestens einen Kontakts zur Konferenz das Stellvertretungsanwählen des mindestens einen Kontakts mit den Informationen beinhaltet.
  10. Verfahren gemäß einem der Ansprüche 6 bis 9, wobei das Verlinken mit dem Gerät durch das Identitätsmodul das Bereitstellen einer Abfrage für das Identitätsmodul mit einem Identifizierer des Geräts beinhaltet.
  11. Verfahren gemäß Anspruch 10, das das Initiieren einer Hintergrundoperation beinhaltet, durch die das Gerät durch einen Kommunikationskanal verlinkt wird.
  12. Verfahren gemäß einem der Ansprüche 6 bis 12, das das Synchronisieren von mindestens einer Datei mit dem Gerät beinhaltet.
  13. System, das Folgendes beinhaltet:
    ein Gerät (106) gemäß einem der Ansprüche 1 bis 5, das mit dem weiteren Gerät (110) verbunden wird;
    wobei das Gerät angeordnet ist, um eine drahtlose Verbindung von dem weiteren Gerät durch das Identitätsmodul (104) anzufordern, wobei das weitere Gerät einen Identifizierer für das Gerät erzeugt, um das Gerät mit dem weiteren Gerät durch die drahtlose Verbindung zu verbinden.
  14. System gemäß Anspruch 13, wobei das Gerät (106) angeordnet ist, um die drahtlose Verbindung von dem weiteren Gerät (110) durch das Identitätsmodul durch einen Trägerdienst anzufordern und sich vom Trägerdienst zu trennen, wenn die drahtlose Verbindung aufgebaut ist.
  15. System gemäß Anspruch 13, wobei eine Signalstärke des weiteren Geräts innerhalb einer Zone beschränkt ist, um die drahtlose Verbindung bereitzustellen, und wobei die drahtlose Verbindung das Gerät mit einem Firmennetzwerk durch das weitere Gerät verbinden kann.
EP12169860.9A 2011-06-06 2012-05-29 Mobility Extension von Näherungssitzungen Active EP2533493B1 (de)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US13/134,396 US10225354B2 (en) 2011-06-06 2011-06-06 Proximity session mobility
US13/356,125 US20120311038A1 (en) 2011-06-06 2012-01-23 Proximity Session Mobility Extension

Publications (2)

Publication Number Publication Date
EP2533493A1 EP2533493A1 (de) 2012-12-12
EP2533493B1 true EP2533493B1 (de) 2015-07-08

Family

ID=46147367

Family Applications (1)

Application Number Title Priority Date Filing Date
EP12169860.9A Active EP2533493B1 (de) 2011-06-06 2012-05-29 Mobility Extension von Näherungssitzungen

Country Status (2)

Country Link
US (2) US20120311038A1 (de)
EP (1) EP2533493B1 (de)

Families Citing this family (41)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8126899B2 (en) 2008-08-27 2012-02-28 Cambridgesoft Corporation Information management system
US20100315483A1 (en) * 2009-03-20 2010-12-16 King Keith C Automatic Conferencing Based on Participant Presence
US8842153B2 (en) 2010-04-27 2014-09-23 Lifesize Communications, Inc. Automatically customizing a conferencing system based on proximity of a participant
EP2567338B1 (de) 2010-05-03 2020-04-08 Perkinelmer Informatics, Inc. Verfahren und vorrichtung zur verarbeitung von dokumenten zur identifikation chemischer strukturen
US10225354B2 (en) * 2011-06-06 2019-03-05 Mitel Networks Corporation Proximity session mobility
US8887214B1 (en) 2011-07-07 2014-11-11 Cisco Technology, Inc. System and method for unified metadata brokering and policy-based content resolution in a video architecture
US8717400B2 (en) * 2011-07-29 2014-05-06 Lifesize Communications, Inc. Automatically moving a conferencing based on proximity of a participant
TWI528766B (zh) * 2012-02-05 2016-04-01 財團法人資訊工業策進會 直接通訊系統及其探索互動方法
US9977876B2 (en) 2012-02-24 2018-05-22 Perkinelmer Informatics, Inc. Systems, methods, and apparatus for drawing chemical structures using touch and gestures
US9009262B2 (en) * 2012-07-03 2015-04-14 Aventura Hq, Inc. Device collaboration in a virtual session
FR2996912B1 (fr) * 2012-10-17 2014-12-26 Airbus Operations Sas Dispositif et procede d'interaction a distance avec un systeme d'affichage
US9535583B2 (en) 2012-12-13 2017-01-03 Perkinelmer Informatics, Inc. Draw-ahead feature for chemical structure drawing applications
US10412131B2 (en) 2013-03-13 2019-09-10 Perkinelmer Informatics, Inc. Systems and methods for gesture-based sharing of data between separate electronic devices
US8854361B1 (en) 2013-03-13 2014-10-07 Cambridgesoft Corporation Visually augmenting a graphical rendering of a chemical structure representation or biological sequence representation with multi-dimensional information
CN103259785B (zh) * 2013-04-11 2015-11-18 深圳市深信服电子科技有限公司 虚拟令牌的认证方法及系统
US9430127B2 (en) 2013-05-08 2016-08-30 Cambridgesoft Corporation Systems and methods for providing feedback cues for touch screen interface interaction with chemical and biological structure drawing applications
US9751294B2 (en) 2013-05-09 2017-09-05 Perkinelmer Informatics, Inc. Systems and methods for translating three dimensional graphic molecular models to computer aided design format
US8966548B2 (en) * 2013-05-20 2015-02-24 Verizon Patent And Licensing Inc. Alternative media presentation device recommendation
WO2015072763A1 (ko) * 2013-11-13 2015-05-21 엘지전자(주) 네트워크로 연결된 방송 수신 장치와 다른 디바이스 간 연결을 관리하는 방법 및 장치
US20150161360A1 (en) * 2013-12-06 2015-06-11 Microsoft Corporation Mobile Device Generated Sharing of Cloud Media Collections
US9733808B2 (en) * 2014-05-15 2017-08-15 The Button Corporation Oy Trigger event based response execution
US9094730B1 (en) * 2014-06-19 2015-07-28 Google Inc. Providing timely media recommendations
US9560143B2 (en) * 2014-06-27 2017-01-31 Intel Corporation System and method for automatic session data transfer between computing devices based on zone transition detection
US20160192436A1 (en) * 2014-12-24 2016-06-30 Intel Corporation Apparatus, system and method of disconnecting a wireless link
US20160261648A1 (en) * 2015-03-04 2016-09-08 Unify Gmbh & Co. Kg Communication system and method of using the same
US10542056B2 (en) 2015-03-04 2020-01-21 Unify Gmbh & Co. Kg Communication system and method of using the same
US10235129B1 (en) 2015-06-29 2019-03-19 Amazon Technologies, Inc. Joining users to communications via voice commands
US10341423B2 (en) * 2015-07-31 2019-07-02 Motorola Mobility Llc Method and apparatus for distributing content using a mobile device
EP3173943A1 (de) * 2015-11-25 2017-05-31 Kubity System, verfahren und computerprogrammprodukt zur übertragung dreidimensionaler modelle
US10327121B2 (en) * 2015-12-22 2019-06-18 Ricoh Company, Ltd. Instrument and system
US11176238B2 (en) * 2016-07-12 2021-11-16 Hewlett-Packard Development Company, L.P. Credential for a service
CN106211359B (zh) * 2016-07-18 2020-01-03 上海小蚁科技有限公司 使装置获得服务的方法以及装置
CA3055172C (en) 2017-03-03 2022-03-01 Perkinelmer Informatics, Inc. Systems and methods for searching and indexing documents comprising chemical information
US11558467B2 (en) * 2017-12-07 2023-01-17 International Business Machines Corporation Virtual personal agent leveraging natural language processing and machine learning
US11057442B2 (en) * 2018-01-27 2021-07-06 Vmware, Inc. System and method for workspace sharing
US11627137B2 (en) 2018-01-31 2023-04-11 T-Mobile Usa, Inc. Virtual profile instantiations via an access privilege control system
US10861453B1 (en) * 2018-05-01 2020-12-08 Amazon Technologies, Inc. Resource scheduling with voice controlled devices
US11044090B2 (en) * 2018-07-24 2021-06-22 ZenDesk, Inc. Facilitating request authentication at a network edge device
CN110572310A (zh) * 2019-07-10 2019-12-13 上海易点时空网络有限公司 基于通讯录的驾考路线分享方法及终端、存储介质
US11615254B2 (en) 2019-11-19 2023-03-28 International Business Machines Corporation Content sharing using address generation
US11611877B2 (en) * 2020-07-08 2023-03-21 T-Mobile Usa, Inc. User authentication

Family Cites Families (68)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6845388B1 (en) 1998-09-11 2005-01-18 L. V. Partners, L.P. Web site access manual of a character string into a software interface
US6574239B1 (en) 1998-10-07 2003-06-03 Eric Morgan Dowling Virtual connection of a remote unit to a server
JP4428844B2 (ja) * 1999-10-01 2010-03-10 キヤノン株式会社 情報処理装置、データ処理方法及び記録媒体
US20020021307A1 (en) 2000-04-24 2002-02-21 Steve Glenn Method and apparatus for utilizing online presence information
KR20020026745A (ko) 2000-10-02 2002-04-12 윤종용 인터넷을 기반으로 한 네트워크 시스템 및 그 통신방법
US7024479B2 (en) 2001-01-22 2006-04-04 Intel Corporation Filtering calls in system area networks
KR100708467B1 (ko) 2001-02-03 2007-04-18 삼성전자주식회사 홈네트워크내의 기기에 서비스를 제공하는 시스템 및 그방법
CN1407780A (zh) 2001-08-13 2003-04-02 国际商业机器公司 在多种终端设备访问服务内容时保持过程持续性的方法和设备
DE10161115A1 (de) 2001-12-12 2003-07-03 Siemens Ag Transformation von Objektbäumen, insbesondere in MES-Systemen
KR100485801B1 (ko) 2002-03-07 2005-04-28 삼성전자주식회사 서로 다른 사설망에 존재하는 네트워크장치들 간의직접접속을 제공하는 망접속장치 및 방법
JP3445986B1 (ja) 2002-09-27 2003-09-16 松下電器産業株式会社 インターネットに接続するサーバ、機器および通信システム
GB2397466B (en) 2003-01-16 2006-08-09 Hewlett Packard Co Wireless LAN
US7895338B2 (en) 2003-03-18 2011-02-22 Siemens Corporation Meta-search web service-based architecture for peer-to-peer collaboration and voice-over-IP
FR2853187B1 (fr) 2003-03-28 2006-01-13 At & T Corp Systeme permettant a toute application reseau de fonctionner de facon transparente a travers un dispositif de traduction d'adresse de reseau
US8924464B2 (en) 2003-09-19 2014-12-30 Polycom, Inc. Method and system for improving establishing of a multimedia session
US8121057B1 (en) * 2003-10-31 2012-02-21 Twisted Pair Solutions, Inc. Wide area voice environment multi-channel communications system and method
US7673062B2 (en) 2003-11-18 2010-03-02 Yahoo! Inc. Method and apparatus for assisting with playback of remotely stored media files
US20050138421A1 (en) 2003-12-23 2005-06-23 Fedronic Dominique L.J. Server mediated security token access
US7669206B2 (en) 2004-04-20 2010-02-23 Microsoft Corporation Dynamic redirection of streaming media between computing devices
EP1665744A2 (de) * 2004-05-21 2006-06-07 Combots Product GmbH & Co.KG Sichere kommunikation zwischen kommunikationspartnern und anzeige von nachrichten
US20060031559A1 (en) 2004-05-25 2006-02-09 Gennady Sorokopud Real Time Streaming Protocol (RTSP) proxy system and method for its use
US8010984B2 (en) 2004-08-25 2011-08-30 Microsoft Corporation Redirection of streaming content
DE102005008590B3 (de) 2005-02-24 2006-03-23 Siemens Ag Verfahren zum Aufnehmen einer VoIP-Kommunikation mittels einer Peer-to-Peer-Datenbank
US7774505B2 (en) 2005-03-05 2010-08-10 Samsung Electronics Co., Ltd Method for transmitting image data in real-time
JP4665568B2 (ja) 2005-03-16 2011-04-06 パナソニック株式会社 情報処理装置、ポート検出装置、情報処理方法、及びポート検出方法
ATE436127T1 (de) 2005-03-29 2009-07-15 Research In Motion Ltd Verfahren und vorrichtungen zur verwendung bei der herstellung von sitzungseinleitungsprotokoll- übermittlungen für virtuelle private vernetzung
EP1708528A1 (de) * 2005-03-31 2006-10-04 BRITISH TELECOMMUNICATIONS public limited company Ortsabhängige Authentifizierung
US20060239190A1 (en) 2005-04-25 2006-10-26 Matsushita Electric Industrial Co., Ltd. Policy-based device/service discovery and dissemination of device profile and capability information for P2P networking
US20060293028A1 (en) 2005-06-27 2006-12-28 Gadamsetty Uma M Techniques to manage network authentication
US20070027367A1 (en) 2005-08-01 2007-02-01 Microsoft Corporation Mobile, personal, and non-intrusive health monitoring and analysis system
US7630714B2 (en) 2005-11-08 2009-12-08 Research In Motion Limited System and methods for data communications in a wireless communication system
US7639792B2 (en) 2005-11-23 2009-12-29 Att Knowledge Ventures, L.P. System and method for location management and emergency support for a voice over internet protocol device
US8972494B2 (en) * 2006-01-19 2015-03-03 International Business Machines Corporation Scheduling calendar entries via an instant messaging interface
US20070219817A1 (en) 2006-03-16 2007-09-20 Jianqing Wu Universal Negotiation Forum
JP4561671B2 (ja) 2006-03-30 2010-10-13 株式会社日立製作所 データ通信方法およびシステム
US20070286100A1 (en) 2006-06-09 2007-12-13 Mika Juhani Saaranen Local discovery of mobile network services
JP4953736B2 (ja) 2006-09-06 2012-06-13 パナソニック株式会社 無線通信システム
US8265004B2 (en) 2006-11-11 2012-09-11 Microsoft Corporation Transferring data using ad hoc networks
GB2449510A (en) 2007-05-24 2008-11-26 Asim Bucuk A method and system for the creation, management and authentication of links between people, entities, objects and devices
US8844002B2 (en) * 2007-06-29 2014-09-23 Ebay Inc. Method and system for notification and request processing
AU2008201643B1 (en) 2007-07-24 2008-08-28 Rambrandt Messaging Technologies, LP Messaging service in a wireless communications network
US7818434B2 (en) 2007-10-23 2010-10-19 Research In Motion Limited Mobile server with multiple service connections
US20090124284A1 (en) 2007-11-14 2009-05-14 Shimon Scherzer System and method for providing seamless broadband internet access to web applications
CN101453483B (zh) * 2007-11-29 2012-05-02 华为技术有限公司 会话历史记录的存储处理和查询方法、系统和装置
KR20090066137A (ko) 2007-12-18 2009-06-23 주식회사 케이티프리텔 이종 망에서 이동 단말기의 핸드오버 방법
DE102007062734B3 (de) * 2007-12-27 2009-05-07 Siemens Ag Verfahren und Vorrichtung zum Betreiben einer Audio- und/oder Videokonferenz mit zumindest zwei Teilnehmern
US9201527B2 (en) * 2008-04-04 2015-12-01 Microsoft Technology Licensing, Llc Techniques to remotely manage a multimedia conference event
US20100015976A1 (en) * 2008-07-17 2010-01-21 Domingo Enterprises, Llc System and method for sharing rights-enabled mobile profiles
EP2304954A4 (de) 2008-07-25 2012-07-18 Ericsson Telefon Ab L M Verfahren und system zur personalisierung und umlenkung von inhaltsobjekten
US9001989B2 (en) * 2008-08-04 2015-04-07 Centurylink Intellectual Property Llc System and method for a smart dialer
US20100081419A1 (en) * 2008-09-26 2010-04-01 Htc Corporation Communication method and communication device thereof
US8352575B2 (en) 2008-10-14 2013-01-08 Samaha Tareq A System and method for a server-based files and tasks brokerage
US9320067B2 (en) 2008-11-24 2016-04-19 Qualcomm Incorporated Configuration of user equipment for peer-to-peer communication
US20100128701A1 (en) 2008-11-24 2010-05-27 Qualcomm Incorporated Beacon transmission for participation in peer-to-peer formation and discovery
JP4784667B2 (ja) 2009-03-06 2011-10-05 ブラザー工業株式会社 端末装置とコンピュータプログラム
US9307393B2 (en) 2009-05-15 2016-04-05 Telcordia Technologies, Inc. Peer-to-peer mobility management in heterogeneous IPV4 networks
JP5275908B2 (ja) 2009-06-03 2013-08-28 株式会社日立製作所 通信システム、セッション制御管理サーバ及びセッション制御方法
US20110087775A1 (en) 2009-10-12 2011-04-14 Electronics And Telecommunications Research Peer-to-peer control device and transmission overlay management method
EP2534789B1 (de) 2010-02-11 2015-10-28 Nokia Solutions and Networks Oy Geräteverwaltung
US8606306B2 (en) 2010-04-07 2013-12-10 Apple Inc. Multiple client computing device invitations for online communication sessions
US9106794B2 (en) * 2010-04-30 2015-08-11 American Teleconferencing Services, Ltd Record and playback in a conference
US20110270922A1 (en) * 2010-04-30 2011-11-03 American Teleconferencing Services Ltd. Managing participants in a conference via a conference user interface
US20110276669A1 (en) 2010-05-10 2011-11-10 Chi-Ching Wei Method and System for Peer-to-Peer Stream
US8880663B2 (en) 2010-09-27 2014-11-04 Nokia Corporation Method and apparatus for sharing user information
US9237305B2 (en) * 2010-10-18 2016-01-12 Apple Inc. Overlay for a video conferencing application
KR101723453B1 (ko) 2011-02-21 2017-04-05 삼성전자주식회사 휴대용 단말기에서 와이파이 다이렉트 연결 기반 유니버설 플러그 앤 플레이 서비스를 제공하기 위한 장치 및 방법
US8537753B2 (en) 2011-03-21 2013-09-17 Broadcom Corporation In-house location based services
US10225354B2 (en) 2011-06-06 2019-03-05 Mitel Networks Corporation Proximity session mobility

Also Published As

Publication number Publication date
US10277641B2 (en) 2019-04-30
US20160261654A1 (en) 2016-09-08
US20120311038A1 (en) 2012-12-06
EP2533493A1 (de) 2012-12-12

Similar Documents

Publication Publication Date Title
US10277641B2 (en) Proximity session mobility extension
US11153393B2 (en) System capable of interacting with devices on a network
EP3266192B1 (de) Kommunikationssystem und verfahren zur verwendung davon
EP2798779B1 (de) Übertragung eines kommunikationsereignisses
CN110166488B (zh) 具有升级前参与确认的无缝呼叫转换
US11558437B2 (en) Communication system and method of using the same
US9722986B2 (en) Electronic tool and methods for meetings
WO2013085570A2 (en) Seamless collaboration and communication
KR20160044506A (ko) 에스컬레이션 인식 통지를 이용한 심리스 통화 전환
KR20100027288A (ko) 모바일 커뮤니티 서비스를 위한 시스템, 방법 및 장치
US11503426B2 (en) Methods and systems for managing conferencing features using a distributed communication controller
US11503440B2 (en) Methods and systems for providing enterprise services to wearable and mobile devices
CA3065726C (en) System and method for network-based transferring communication sessions between endpoints
US20150365133A1 (en) Touch and Talk Auto-Configuring of Video Conferences Using Near Field Communication (NFC)
CA2791830C (en) Proximity session mobility extension

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

17P Request for examination filed

Effective date: 20130129

17Q First examination report despatched

Effective date: 20140207

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

RIC1 Information provided on ipc code assigned before grant

Ipc: G06F 21/33 20130101ALI20150227BHEP

Ipc: H04W 4/02 20090101ALI20150227BHEP

Ipc: H04W 4/20 20090101ALI20150227BHEP

Ipc: H04L 29/06 20060101AFI20150227BHEP

Ipc: H04W 12/06 20090101ALI20150227BHEP

INTG Intention to grant announced

Effective date: 20150325

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 736141

Country of ref document: AT

Kind code of ref document: T

Effective date: 20150715

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602012008540

Country of ref document: DE

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 736141

Country of ref document: AT

Kind code of ref document: T

Effective date: 20150708

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20150708

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150708

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150708

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150708

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151008

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151009

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150708

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151108

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150708

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150708

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151109

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150708

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150708

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150708

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602012008540

Country of ref document: DE

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 5

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150708

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150708

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150708

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150708

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150708

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150708

26N No opposition filed

Effective date: 20160411

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150708

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20160531

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20160529

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150708

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20160531

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20160531

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 6

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20160529

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150708

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 7

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20120529

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150708

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150708

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150708

Ref country code: MT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20160531

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150708

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150708

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150708

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150708

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602012008540

Country of ref document: DE

Representative=s name: VENNER SHIPLEY GERMANY LLP, DE

Ref country code: DE

Ref legal event code: R082

Ref document number: 602012008540

Country of ref document: DE

Representative=s name: VENNER SHIPLEY LLP, DE

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602012008540

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0029060000

Ipc: H04L0065000000

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 12

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20240328

Year of fee payment: 13

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20240402

Year of fee payment: 13

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20240328

Year of fee payment: 13