US20120209930A1 - Mobile server with multiple service connections - Google Patents
Mobile server with multiple service connections Download PDFInfo
- Publication number
- US20120209930A1 US20120209930A1 US13/454,456 US201213454456A US2012209930A1 US 20120209930 A1 US20120209930 A1 US 20120209930A1 US 201213454456 A US201213454456 A US 201213454456A US 2012209930 A1 US2012209930 A1 US 2012209930A1
- Authority
- US
- United States
- Prior art keywords
- mobile
- service
- session
- communications
- server
- 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.)
- Abandoned
Links
- 238000010295 mobile communication Methods 0.000 claims abstract description 87
- 238000004891 communication Methods 0.000 claims abstract description 84
- 238000000034 method Methods 0.000 claims abstract description 16
- 230000006870 function Effects 0.000 description 4
- 230000000977 initiatory effect Effects 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000004913 activation Effects 0.000 description 1
- 239000000969 carrier Substances 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- MGMXGCZJYUCMGY-UHFFFAOYSA-N tris(4-nonylphenyl) phosphite Chemical compound C1=CC(CCCCCCCCC)=CC=C1OP(OC=1C=CC(CCCCCCCCC)=CC=1)OC1=CC=C(CCCCCCCCC)C=C1 MGMXGCZJYUCMGY-UHFFFAOYSA-N 0.000 description 1
Images
Classifications
-
- 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
-
- 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/56—Provisioning of proxy services
- H04L67/565—Conversion or adaptation of application format or content
-
- 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/52—Network services specially adapted for the location of the user terminal
-
- 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
Definitions
- the present application relates to mobile communication devices and, more particularly, to methods and apparatus for connecting such devices to multiple services.
- a mobile communications device may exchange data with a number of different services, including for example an email service, peer-to-peer messaging services, and other content delivery services.
- a mobile communications device may have to maintain simultaneous connections to receive data from a plurality of services, which can tie up the computing and memory resources of the device, as well as wear down the battery of the device.
- a remote relay outside of an enterprise's firewall may be used to connect to the multiple services, with the device only maintaining a single connection to the relay.
- conditions can exist that make use of such an external relay impractical or inefficient.
- FIG. 1 illustrates a communication network including an enterprise with a wireless connection to a mobile data communication device
- FIG. 2 illustrates components of an example of a mobile data communication device for use in the communication network of FIG. 1 ;
- FIG. 3 illustrates components of a mobile server for use in the communications network of FIG. 1 .
- the method includes establishing, through a firewall and a wireless network, a first communications session between the mobile communications device and a mobile server located in an enterprise network with which the mobile communications device is associated; and establishing, concurrent with the first communications session at least one further communications session between the mobile server and a service, the at least one further communications session being established by the mobile server as a session proxy for the mobile communications device.
- a mobile server for coupling an enterprise network to a wireless communications network that is in wireless communication with a mobile communications device associated with the enterprise network, the mobile server including a service manager for establishing, through a firewall and the wireless communications network, a first communications session between the mobile communications device and the mobile server, and for establishing concurrent with the first communications session at least one further communications session between the mobile server and a service in which the mobile server functions as a session proxy for the mobile communications device.
- an enterprise 100 includes a local area network (LAN) 118 with a number of network nodes 120 (such as suitably configured personal computers—PCs 120 A, 1208 , 120 C) connected to one or more enterprise servers 102 via the LAN 118 .
- the network nodes connected to LAN 118 may also include access points to one or more local wireless networks, and gateways to further LAN's operated within enterprise 100 .
- the enterprise servers 102 may include for example one or more enterprise messaging servers (perhaps employing MicrosoftTM Exchange Server and providing e-mail, calendar events and contact details), and one or more enterprise application servers and enterprise web servers, each enterprise server 102 being connected to a wide area network (WAN, such as the public Internet) 108 via a firewall 106 .
- WAN wide area network
- wireless carrier networks 110 X, 110 Y, 110 Z (collectively or individually 110 ) operated by wireless carriers also connect to the WAN 108 .
- Mobile communications devices such as mobile communications devices 112 A, 112 B (collectively or individually 112 ), may be connected to one or other of the wireless carrier networks 110 .
- the enterprise 100 includes a mobile server 104 with a connection via the firewall 106 to the WAN 108 .
- the mobile server 104 which may be implemented on one or more suitably configured servers, couples the exchanger servers 102 to the wireless networks 110 by adapting communications between the enterprise servers 102 and the wireless networks 110 .
- FIG. 2 illustrates an example configuration of the handheld mobile communication device 112 including a housing, an input device (a keyboard 224 ), an output device (a display 226 ) and a processing device (a microprocessor 228 ), which is shown schematically in FIG. 2 as coupled between the keyboard 224 and the display 226 .
- the microprocessor 228 controls the operation of the display 226 , as well as the overall operation of the mobile device 112 , in response to actuation of keys on the keyboard 224 by a user.
- the device 112 also includes, as shown schematically in FIG.
- the mobile device 112 is a two-way radio frequency (RF) communication device having data communication capabilities and, in at least some cases, voice communication capabilities.
- the mobile device 112 preferably has the capability to communicate with other computer systems via the Internet.
- RF radio frequency
- Operating system software executed by the microprocessor 228 is preferably stored in a computer readable medium, such as the flash memory 216 , but may be stored in other types of memory devices, such as a read only memory (ROM) or similar storage element.
- system software, specific device applications, or parts thereof may be temporarily loaded into a volatile store, such as the RAM 218 .
- Communication signals received by the mobile device may also be stored to the RAM 218 .
- the microprocessor 228 in addition to its operating system functions, enables execution of software applications on the mobile device 112 .
- a predetermined set of software applications that control basic device operations such as a voice communications module 230 A and a data communications module 230 B, may be installed on the mobile device 112 during or after manufacture.
- additional software modules illustrated as other software module 230 N, which may be, for instance, a personal information manager (PIM) application, may be installed during or after manufacture.
- the PIM application is preferably capable of organizing and managing data items, such as e-mail messages, calendar events, voice mail messages, appointments, and task items.
- the PIM application is also preferably capable of sending and receiving data items via the wireless carrier network 110 .
- the data items managed by the PIM application are seamlessly integrated, synchronized and updated via the wireless carrier network 110 with the device user's corresponding data items stored or associated with a host computer system.
- Communication functions are performed through the communication subsystem 200 , and possibly through the short-range communications subsystem 202 .
- the communication subsystem 200 is configured to exchange wireless signals with network 110 , and will typically include one or more antennas, RF receivers and RF transmitters, and a digital signal processor for processing outgoing communications signals being sent from the microprocessor 228 and incoming communications signals destined to the microprocessor 228 .
- the specific design and implementation of the communication subsystem 200 is dependent upon the communication network in which the mobile device 112 is intended to operate.
- the communication subsystem 200 of the mobile device 112 may be designed to operate with the MobitexTM, DataTACTM or General Packet Radio Service (GPRS) mobile data communication networks and also designed to operate with any of a variety of voice/data communication networks, such as Advanced Mobile Phone Service (AMPS), Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), Personal Communications Service (PCS), Global System for Mobile Communications (GSM), etc.
- AMPS Advanced Mobile Phone Service
- TDMA Time Division Multiple Access
- CDMA Code Division Multiple Access
- PCS Personal Communications Service
- GSM Global System for Mobile Communications
- Other types of data and voice networks, both separate and integrated, may also be utilized with the mobile device 112 .
- the mobile device 10 is configured to also communicate in wireless local area networks (WLAN), and communications subsystem 200 may be configured to also exchange signals in such networks.
- WLAN wireless local area networks
- Network access requirements vary depending upon the type of communication system.
- an identifier is associated with each mobile device that uniquely identifies the mobile device or subscriber to which the mobile device has been assigned.
- the identifier is unique within a specific network or network technology.
- MobitexTM networks mobile devices are registered on the network using a Mobitex Access Number (MAN) associated with each device and in DataTACTM networks, mobile devices are registered on the network using a Logical Link Identifier (LLI) associated with each device.
- MAN Mobitex Access Number
- LLI Logical Link Identifier
- SIM Subscriber Identity Module
- a GPRS device therefore requires a subscriber identity module, commonly referred to as a Subscriber Identity Module (SIM) card, in order to operate on a GPRS network.
- SIM Subscriber Identity Module
- the mobile device 112 may send and receive communication signals over the wireless carrier network 110 .
- the short-range communications subsystem 202 enables communication between the mobile device 112 and other proximate systems or devices, which need not necessarily be similar devices.
- the short-range communications subsystem may include an infrared device and associated circuits and components, or a BluetoothTM communication module to provide for communication with similarly-enabled systems and devices.
- FIG. 3 schematically illustrates the mobile server 104 in greater detail.
- the mobile server 104 includes local service agents or modules 304 A, 304 B (collectively or individually 304 ) for providing services to mobile communication devices 112 , including, for example, a messaging service module 304 A and a mobile data service module 304 B.
- the mobile server 104 can also be connected to external services 306 A, 306 B (collectively or individually 306 ) that are accessible to the mobile communications devices 112 , including for example an instant messaging (“IM”) service or a peer-to-peer (“P2P”) messaging service 306 A, and other external services (represented generically in FIG. 3 as “Other Service” 306 B).
- External services refer to services that are not implemented directly by the wireless server 104 .
- another external services could include a Telelocator Network Paging Protocol (“TNPP”) service.
- TNPP Telelocator Network Paging Protocol
- email service module 304 A couples a traditional messaging server 102 A to a wireless network 110 by adapting email messages from the messaging server 102 A for transport over the wireless network to a receiving mobile communication device 112 , and adapting email messages received from a sending mobile communications device to a format suitable for the messaging server 102 A.
- Mobile data service module 304 b couples a traditional application/Web server 102 B (which may be separate servers) to the wireless network 110 by adapting applications/Web pages and other content received from or through the application/Web server 1028 for transport over the wireless network to a receiving mobile communication device 112 .
- Services 304 A and/or 304 B could in some embodiments be external services.
- P2P service 306 A such service allows mobile communications devices 112 within wireless network 110 to communicate with each other, for example through text messages.
- Mobile Communication Device 112 B can send a message to mobile communications device 112 A and vice versa, without going through the messaging server 102 A.
- the P2P service 306 A which may be located within the enterprise 100 or may be external to enterprise network 100 , routes the P2P message and manages the P2P connection.
- the mobile server 104 includes a service manager module 302 which, as will be explained in greater detail below, functions as a service or session proxy between individual mobile communications devices 112 and at least some of the various services 304 , 306 .
- the mobile server 104 and its service manager 302 are configured to allow a mobile communications device 112 to maintain a single connection with the service manager 302 , which in turn maintains connections on behalf of the mobile communications device 112 with the individual services required by the mobile communications device 112 .
- the mobile device 112 A may become associated with the enterprise 100 through a connection between the mobile device 112 A and the PC 120 C (for example through a wired link between of the serial port 208 of device 112 A and the PC 120 C, or through a link through short range communications systems 202 , or through a link through a WLAN) while an association process is executed at the PC 120 C.
- the result of the association process may be the uploading of a unique device identifier of the mobile device 112 to the PC 120 C and the downloading of a Unique Identifier (UID) of the mobile server 104 from the PC 120 C to the mobile device 112 .
- the device identifier may be considered a characteristic of the mobile device 112 (e.g., a device identifier may be burned into the mobile device 112 ).
- the UID of the mobile server 104 normally does not change.
- the mobile server 104 establishes a communication path with the multiple wireless carrier networks 110 .
- the mobile server 104 may have an established communication path with each of the wireless carrier networks 110 Y, 110 Z that is connected to the WAN 108 through a virtual private network (VPN).
- the mobile server 104 also establishes communication paths with any external services 306 that are required by the active mobile communications devices 112 .
- the mobile server 104 may provide centralized management of wireless communications, as follows. After the mobile device 112 registers (in conventional fashion) with one of the wireless carrier networks 110 with which the mobile server 104 has an established communications path, the mobile device 112 sends a registration packet with its device identifier and the UID of the mobile server 104 with which the mobile device 112 is associated. This registration packet is received by the wireless carrier network 110 X and directed to the mobile server 104 with an identity of the wireless carrier network 110 X. On receiving this registration packet, the mobile server 104 associates the wireless carrier network 110 X with the device identifier, and the mobile communications device 112 is registered for an active session with the mobile server 104 . Note that the term “packet” is used herein for an addressed unit of data that may also be called a “message”, a “frame” or, more generically, a “protocol data unit”.
- the mobile communications device is configured to send a service registration packet or series of such packets to the mobile server 104 advising the mobile server 104 of the services that are required by the mobile communications device 112 .
- services that are available to the mobile communications device will also each have a unique service identifier associated with them.
- P2P service 306 A and Other Service 306 B will each have a unique service identifier, which may for example be a unique IP address among other things.
- Email service 304 A and mobile data service 304 A are integrated into the mobile server 104 their unique service identifier may be the same as the UID of the mobile server.
- the unique service identifiers for each of the services required by a mobile communication device are included in the service registration packets sent by the mobile communication device 112 and received by the mobile server 104 .
- the mobile server 104 may associate service identification information received from the mobile communication device with a unique service identifier or service address by referring to look-up tables or similar correlating information maintained in a configuration database 308 .
- a pre-configured set of default services for each of the mobile communications devices 112 associated with the enterprise 100 are stored in configuration database 308 such that there is no need for a mobile communications device 112 to advise the mobile server 104 of its required services through service registration packets upon setting up of an active session between the mobile communications device 112 and the mobile server 104 .
- a mobile communications device 112 may provide periodic updates to the mobile server 104 during an active session advising of any changes in the services that it requires during the session (for example, addition of new services, or dropping of services that are no longer required.)
- the mobile server 102 when an active session is established between a mobile server 104 of enterprise 100 and a mobile communication device 112 , the mobile server 102 has access to information about the services required by the mobile communication device 112 .
- required service information may come from service registration packets sent by the device 112 , from configuration information associated with the mobile device 112 and stored on the configuration database 308 of mobile server 104 , or from both of these potential sources.
- the service manager 302 of the mobile server 104 uses this required service information to set up and maintain sessions on behalf of the mobile communications device 112 with each of the identified services, such that the mobile communications device 112 only needs to maintain a single session with the mobile server 104 rather than multiple sessions.
- the service manager 302 upon establishment of an active session with a mobile communication device 112 and upon receipt of the required service information will send a session initiation request packet to the required services such as P2P service 306 A and Other Service 306 B, for example (with respect to services internally managed in the mobile server 104 such as email service 304 A and mobile data service 304 B initiation of a separate session may not be required in some embodiments).
- the request will include an address of the device (which may be the unique device identifier, but could also be a different address that is mapped to the unique device identifier by the service manager 302 ).
- the request will also include the UID (or other unique address) of the mobile server 104 .
- packets sent from each of the services destined to the mobile communication device 112 will be received at the mobile server 104 on behalf of the mobile communications device, and then forwarded by the mobile server 104 to the mobile communication device 112 .
- the data provided from an external service 306 is encrypted at the external service such that the mobile server 104 that receives the data from the external service on behalf of a mobile device is unable to read or modify the data.
- the mobile communications device in order to maintain an active session with a service the mobile communications device has to periodically send out a “ping” or notification message advising the service that the mobile communications is still active.
- the mobile server 104 when the mobile server 104 receives such a ping or status notification from the mobile communications device 112 , it sends a ping or notification on behalf of the mobile communications device 112 to all of the services that the mobile server 104 is maintaining sessions with for the mobile communications device 112 .
- a single notification message from the mobile communications device 112 can be used to maintain a number of active sessions with a number of services.
- using the mobile server 104 as a session proxy to a plurality of required services has the result that only a single session needs to be maintained through the wireless communications network to the mobile communications device, thereby in some cases reducing over the air traffic in the wireless network and reducing operating demands on the mobile communications device 112 , which in turn can reduce the drain on the battery of the device. Furthermore, the mobile server 104 takes on at least some of the overhead of negotiating and maintaining sessions to the plurality of services, reducing the burden that would otherwise be placed on the mobile device if it had to negotiate the sessions directly.
- the mobile server 104 is itself a “service” from the perspective of the mobile communications device 112 , which maintains sessions to other services on behalf of the mobile communications device 112 .
- the functionality of the service manager 302 could be implemented on servers other than the mobile server 104 in other locations, for example at Other Service 306 B, such that a primary session could be maintained, through a firewall, between the Other Service 306 B and the mobile communications device 112 , and the serve manager 302 implemented at the Other Service then used to maintain proxy sessions on behalf of the mobile communications device 112 with a number of other services, including the mobile server 104 .
- a mobile communication device 112 may maintain sessions with a plurality of mobile servers 104 , in which case one of the mobile servers 104 has to take ownership of the proxy sessions and advise the respective services accordingly.
- the mobile device 112 has a prioritized list of which mobile servers 104 to try and establish a direct session with, and once the mobile device 112 is successful in establishing a session with a particular mobile server 104 , that device connected mobile server 104 than establishes proxy sessions on behalf of the mobile device 112 with the other mobile servers 104 and other services as required, in the manner described above.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
A method of communicating between a mobile communications device and a plurality of services that are used by the mobile communications device. The method includes establishing, through a firewall and a wireless network, a first communications session between the mobile communications device and a mobile server located in an enterprise network with which the mobile communications device is associated; and establishing, concurrent with the first communications session at least one further communications session between the mobile server and a service, the at least one further communications session being established by the mobile server as a session proxy for the mobile communications device.
Description
- The present application is a continuation of U.S. patent application Ser. No. 12/836,707, filed Jul. 15, 2010. U.S. patent application Ser. No. 12/836,707 is a continuation of U.S. patent application Ser. No. 11/876,872 filed Oct. 23, 2007. The content of the referenced, previously filed applications are hereby expressly incorporated by reference into the detailed description hereof.
- The present application relates to mobile communication devices and, more particularly, to methods and apparatus for connecting such devices to multiple services.
- A mobile communications device may exchange data with a number of different services, including for example an email service, peer-to-peer messaging services, and other content delivery services. In some cases, a mobile communications device may have to maintain simultaneous connections to receive data from a plurality of services, which can tie up the computing and memory resources of the device, as well as wear down the battery of the device. In some cases, a remote relay outside of an enterprise's firewall may be used to connect to the multiple services, with the device only maintaining a single connection to the relay. However, conditions can exist that make use of such an external relay impractical or inefficient.
- Accordingly, an improved method and apparatus for facilitating connections between a mobile communications device and multiple services is desirable
- In the figures which illustrate example embodiments:
-
FIG. 1 illustrates a communication network including an enterprise with a wireless connection to a mobile data communication device; -
FIG. 2 illustrates components of an example of a mobile data communication device for use in the communication network ofFIG. 1 ; and -
FIG. 3 illustrates components of a mobile server for use in the communications network ofFIG. 1 . - According to one example embodiment is a method of communicating between a mobile communications device and a plurality of services that are used by the mobile communications device. The method includes establishing, through a firewall and a wireless network, a first communications session between the mobile communications device and a mobile server located in an enterprise network with which the mobile communications device is associated; and establishing, concurrent with the first communications session at least one further communications session between the mobile server and a service, the at least one further communications session being established by the mobile server as a session proxy for the mobile communications device.
- According to another embodiment is a mobile server for coupling an enterprise network to a wireless communications network that is in wireless communication with a mobile communications device associated with the enterprise network, the mobile server including a service manager for establishing, through a firewall and the wireless communications network, a first communications session between the mobile communications device and the mobile server, and for establishing concurrent with the first communications session at least one further communications session between the mobile server and a service in which the mobile server functions as a session proxy for the mobile communications device.
- As illustrated in
FIG. 1 , anenterprise 100 includes a local area network (LAN) 118 with a number of network nodes 120 (such as suitably configured personal computers—PCs 120A, 1208, 120C) connected to one ormore enterprise servers 102 via theLAN 118. Among other things, the network nodes connected toLAN 118 may also include access points to one or more local wireless networks, and gateways to further LAN's operated withinenterprise 100. Theenterprise servers 102 may include for example one or more enterprise messaging servers (perhaps employing Microsoft™ Exchange Server and providing e-mail, calendar events and contact details), and one or more enterprise application servers and enterprise web servers, eachenterprise server 102 being connected to a wide area network (WAN, such as the public Internet) 108 via afirewall 106. Multiplewireless carrier networks mobile communications devices wireless carrier networks 110. - The
enterprise 100 includes amobile server 104 with a connection via thefirewall 106 to the WAN 108. Among other things, themobile server 104, which may be implemented on one or more suitably configured servers, couples theexchanger servers 102 to thewireless networks 110 by adapting communications between theenterprise servers 102 and thewireless networks 110. -
FIG. 2 illustrates an example configuration of the handheldmobile communication device 112 including a housing, an input device (a keyboard 224), an output device (a display 226) and a processing device (a microprocessor 228), which is shown schematically inFIG. 2 as coupled between thekeyboard 224 and thedisplay 226. Themicroprocessor 228 controls the operation of thedisplay 226, as well as the overall operation of themobile device 112, in response to actuation of keys on thekeyboard 224 by a user. Thedevice 112 also includes, as shown schematically inFIG. 2 : acommunications subsystem 200; a short-range communications subsystem 202; input/output devices in addition to the keyboard and display including a set of auxiliary I/O devices 206, aserial port 208, aspeaker 210 and amicrophone 212; as well as memory devices including aflash memory 216 and a Random Access Memory (RAM) 218; and variousother device subsystems 220. In at least one example embodiment themobile device 112 is a two-way radio frequency (RF) communication device having data communication capabilities and, in at least some cases, voice communication capabilities. In addition, themobile device 112 preferably has the capability to communicate with other computer systems via the Internet. - Operating system software executed by the
microprocessor 228 is preferably stored in a computer readable medium, such as theflash memory 216, but may be stored in other types of memory devices, such as a read only memory (ROM) or similar storage element. In addition, system software, specific device applications, or parts thereof, may be temporarily loaded into a volatile store, such as theRAM 218. Communication signals received by the mobile device may also be stored to theRAM 218. - The
microprocessor 228, in addition to its operating system functions, enables execution of software applications on themobile device 112. A predetermined set of software applications that control basic device operations, such as a voice communications module 230A and adata communications module 230B, may be installed on themobile device 112 during or after manufacture. As well, additional software modules, illustrated asother software module 230N, which may be, for instance, a personal information manager (PIM) application, may be installed during or after manufacture. The PIM application is preferably capable of organizing and managing data items, such as e-mail messages, calendar events, voice mail messages, appointments, and task items. The PIM application is also preferably capable of sending and receiving data items via thewireless carrier network 110. In some embodiments, the data items managed by the PIM application are seamlessly integrated, synchronized and updated via thewireless carrier network 110 with the device user's corresponding data items stored or associated with a host computer system. - Communication functions, including data and voice communications, are performed through the
communication subsystem 200, and possibly through the short-range communications subsystem 202. Thecommunication subsystem 200 is configured to exchange wireless signals withnetwork 110, and will typically include one or more antennas, RF receivers and RF transmitters, and a digital signal processor for processing outgoing communications signals being sent from themicroprocessor 228 and incoming communications signals destined to themicroprocessor 228. The specific design and implementation of thecommunication subsystem 200 is dependent upon the communication network in which themobile device 112 is intended to operate. For example, thecommunication subsystem 200 of themobile device 112 may be designed to operate with the Mobitex™, DataTAC™ or General Packet Radio Service (GPRS) mobile data communication networks and also designed to operate with any of a variety of voice/data communication networks, such as Advanced Mobile Phone Service (AMPS), Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), Personal Communications Service (PCS), Global System for Mobile Communications (GSM), etc. Other types of data and voice networks, both separate and integrated, may also be utilized with themobile device 112. In some embodiments, the mobile device 10 is configured to also communicate in wireless local area networks (WLAN), andcommunications subsystem 200 may be configured to also exchange signals in such networks. - Network access requirements vary depending upon the type of communication system. Typically, an identifier is associated with each mobile device that uniquely identifies the mobile device or subscriber to which the mobile device has been assigned. The identifier is unique within a specific network or network technology. For example, in Mobitex™ networks, mobile devices are registered on the network using a Mobitex Access Number (MAN) associated with each device and in DataTAC™ networks, mobile devices are registered on the network using a Logical Link Identifier (LLI) associated with each device. In GPRS networks, however, network access is associated with a subscriber or user of a device. A GPRS device therefore requires a subscriber identity module, commonly referred to as a Subscriber Identity Module (SIM) card, in order to operate on a GPRS network. Despite identifying a subscriber by SIM, mobile devices within GSM/GPRS networks are uniquely identified using an International Mobile Subscriber Identify (IMSI) number.
- When required network registration or activation procedures have been completed, the
mobile device 112 may send and receive communication signals over thewireless carrier network 110. - The short-
range communications subsystem 202 enables communication between themobile device 112 and other proximate systems or devices, which need not necessarily be similar devices. For example, the short-range communications subsystem may include an infrared device and associated circuits and components, or a Bluetooth™ communication module to provide for communication with similarly-enabled systems and devices. -
FIG. 3 schematically illustrates themobile server 104 in greater detail. In an example embodiment, themobile server 104 includes local service agents ormodules mobile communication devices 112, including, for example, amessaging service module 304A and a mobiledata service module 304B. Themobile server 104 can also be connected toexternal services 306A, 306B (collectively or individually 306) that are accessible to themobile communications devices 112, including for example an instant messaging (“IM”) service or a peer-to-peer (“P2P”)messaging service 306A, and other external services (represented generically inFIG. 3 as “Other Service” 306B). External services refer to services that are not implemented directly by thewireless server 104. For example, another external services could include a Telelocator Network Paging Protocol (“TNPP”) service. - The actual services 304, 306 available through the
mobile server 104 can vary, however to facilitate an understanding of the system described herein, example services with be briefly described. In an example embodiment,email service module 304A couples atraditional messaging server 102A to awireless network 110 by adapting email messages from themessaging server 102A for transport over the wireless network to a receivingmobile communication device 112, and adapting email messages received from a sending mobile communications device to a format suitable for themessaging server 102A. Mobile data service module 304 b couples a traditional application/Web server 102B (which may be separate servers) to thewireless network 110 by adapting applications/Web pages and other content received from or through the application/Web server 1028 for transport over the wireless network to a receivingmobile communication device 112.Services 304A and/or 304B could in some embodiments be external services. - With respect to
P2P service 306A, such service allowsmobile communications devices 112 withinwireless network 110 to communicate with each other, for example through text messages. With reference toFIG. 1 , for example, through P2P communications,Mobile Communication Device 112B can send a message tomobile communications device 112A and vice versa, without going through themessaging server 102A. In an example embodiment, theP2P service 306A, which may be located within theenterprise 100 or may be external toenterprise network 100, routes the P2P message and manages the P2P connection. - The
mobile server 104 includes aservice manager module 302 which, as will be explained in greater detail below, functions as a service or session proxy between individualmobile communications devices 112 and at least some of the various services 304, 306. Themobile server 104 and itsservice manager 302 are configured to allow amobile communications device 112 to maintain a single connection with theservice manager 302, which in turn maintains connections on behalf of themobile communications device 112 with the individual services required by themobile communications device 112. - In
FIG. 1 , themobile device 112A may become associated with theenterprise 100 through a connection between themobile device 112A and thePC 120C (for example through a wired link between of theserial port 208 ofdevice 112A and thePC 120C, or through a link through shortrange communications systems 202, or through a link through a WLAN) while an association process is executed at thePC 120C. The result of the association process may be the uploading of a unique device identifier of themobile device 112 to thePC 120C and the downloading of a Unique Identifier (UID) of themobile server 104 from thePC 120C to themobile device 112. The device identifier may be considered a characteristic of the mobile device 112 (e.g., a device identifier may be burned into the mobile device 112). The UID of themobile server 104 normally does not change. - In an example embodiment, to provide centralized wireless management services, the
mobile server 104 establishes a communication path with the multiple wireless carrier networks 110. Specifically, themobile server 104 may have an established communication path with each of thewireless carrier networks WAN 108 through a virtual private network (VPN). Themobile server 104 also establishes communication paths with any external services 306 that are required by the activemobile communications devices 112. - With the described set-up, the
mobile server 104 may provide centralized management of wireless communications, as follows. After themobile device 112 registers (in conventional fashion) with one of thewireless carrier networks 110 with which themobile server 104 has an established communications path, themobile device 112 sends a registration packet with its device identifier and the UID of themobile server 104 with which themobile device 112 is associated. This registration packet is received by thewireless carrier network 110X and directed to themobile server 104 with an identity of thewireless carrier network 110X. On receiving this registration packet, themobile server 104 associates thewireless carrier network 110X with the device identifier, and themobile communications device 112 is registered for an active session with themobile server 104. Note that the term “packet” is used herein for an addressed unit of data that may also be called a “message”, a “frame” or, more generically, a “protocol data unit”. - In an example embodiment, once an active session is opened between a
mobile communication device 112 and amobile server 104, the mobile communications device is configured to send a service registration packet or series of such packets to themobile server 104 advising themobile server 104 of the services that are required by themobile communications device 112. In at last one example embodiment, services that are available to the mobile communications device will also each have a unique service identifier associated with them. For example,P2P service 306A and Other Service 306B will each have a unique service identifier, which may for example be a unique IP address among other things. In the illustrated example asEmail service 304A andmobile data service 304A are integrated into themobile server 104 their unique service identifier may be the same as the UID of the mobile server. - In an example embodiment, the unique service identifiers for each of the services required by a mobile communication device are included in the service registration packets sent by the
mobile communication device 112 and received by themobile server 104. In some embodiments, themobile server 104 may associate service identification information received from the mobile communication device with a unique service identifier or service address by referring to look-up tables or similar correlating information maintained in aconfiguration database 308. In some embodiments, a pre-configured set of default services for each of themobile communications devices 112 associated with theenterprise 100 are stored inconfiguration database 308 such that there is no need for amobile communications device 112 to advise themobile server 104 of its required services through service registration packets upon setting up of an active session between themobile communications device 112 and themobile server 104. In some embodiments, amobile communications device 112 may provide periodic updates to themobile server 104 during an active session advising of any changes in the services that it requires during the session (for example, addition of new services, or dropping of services that are no longer required.) - Thus, it will be appreciated that when an active session is established between a
mobile server 104 ofenterprise 100 and amobile communication device 112, themobile server 102 has access to information about the services required by themobile communication device 112. Among other possible sources, such required service information may come from service registration packets sent by thedevice 112, from configuration information associated with themobile device 112 and stored on theconfiguration database 308 ofmobile server 104, or from both of these potential sources. Theservice manager 302 of themobile server 104 uses this required service information to set up and maintain sessions on behalf of themobile communications device 112 with each of the identified services, such that themobile communications device 112 only needs to maintain a single session with themobile server 104 rather than multiple sessions. - In one example embodiment, the
service manager 302, upon establishment of an active session with amobile communication device 112 and upon receipt of the required service information will send a session initiation request packet to the required services such asP2P service 306A and Other Service 306B, for example (with respect to services internally managed in themobile server 104 such asemail service 304A andmobile data service 304B initiation of a separate session may not be required in some embodiments). The request will include an address of the device (which may be the unique device identifier, but could also be a different address that is mapped to the unique device identifier by the service manager 302). The request will also include the UID (or other unique address) of themobile server 104. Thereafter, packets sent from each of the services destined to themobile communication device 112 will be received at themobile server 104 on behalf of the mobile communications device, and then forwarded by themobile server 104 to themobile communication device 112. In some example embodiments, the data provided from an external service 306 is encrypted at the external service such that themobile server 104 that receives the data from the external service on behalf of a mobile device is unable to read or modify the data. - In some communications systems, in order to maintain an active session with a service the mobile communications device has to periodically send out a “ping” or notification message advising the service that the mobile communications is still active. In at least some example embodiments, when the
mobile server 104 receives such a ping or status notification from themobile communications device 112, it sends a ping or notification on behalf of themobile communications device 112 to all of the services that themobile server 104 is maintaining sessions with for themobile communications device 112. Thus, a single notification message from themobile communications device 112 can be used to maintain a number of active sessions with a number of services. - In some embodiments, using the
mobile server 104 as a session proxy to a plurality of required services, has the result that only a single session needs to be maintained through the wireless communications network to the mobile communications device, thereby in some cases reducing over the air traffic in the wireless network and reducing operating demands on themobile communications device 112, which in turn can reduce the drain on the battery of the device. Furthermore, themobile server 104 takes on at least some of the overhead of negotiating and maintaining sessions to the plurality of services, reducing the burden that would otherwise be placed on the mobile device if it had to negotiate the sessions directly. - The
mobile server 104 is itself a “service” from the perspective of themobile communications device 112, which maintains sessions to other services on behalf of themobile communications device 112. In this regard, in at least some example embodiments, the functionality of theservice manager 302 could be implemented on servers other than themobile server 104 in other locations, for example at Other Service 306B, such that a primary session could be maintained, through a firewall, between the Other Service 306B and themobile communications device 112, and theserve manager 302 implemented at the Other Service then used to maintain proxy sessions on behalf of themobile communications device 112 with a number of other services, including themobile server 104. - In some embodiments, a
mobile communication device 112 may maintain sessions with a plurality ofmobile servers 104, in which case one of themobile servers 104 has to take ownership of the proxy sessions and advise the respective services accordingly. In some embodiments, themobile device 112 has a prioritized list of whichmobile servers 104 to try and establish a direct session with, and once themobile device 112 is successful in establishing a session with a particularmobile server 104, that device connectedmobile server 104 than establishes proxy sessions on behalf of themobile device 112 with the othermobile servers 104 and other services as required, in the manner described above. - Other modifications will be apparent to those skilled in the art.
Claims (14)
1. At a mobile server located in an enterprise network with which a mobile communications device is associated, a method of facilitating communication between the mobile communications device and a plurality of services, the method comprising:
establishing a first communications session with the mobile communications device; and
establishing, concurrent with the first communications session, a further communications session with a service external to the mobile server, the further communications session being established by the mobile server as a session proxy for the mobile communications device.
2. The method of claim 1 further comprising:
retrieving, from a configuration database at the mobile server, service identification information associated with the mobile communications device;
selecting, based on the service identification information, the service for the establishing of the further communications session.
3. The method of claim 1 further comprising:
receiving, at the mobile server from the mobile communications device over the first communications session, a status notification message;
responsive to the receiving, transmitting, from the mobile server to the service over the further communications session, the status notification message on behalf of the mobile communications device.
4. The method of claim 1 wherein the mobile server includes an email service for forwarding email messages to the mobile communications device and the service includes a peer to peer communications service for communications between mobile communications devices.
5. The method of claim 1 wherein the service is associated with a further mobile server located behind a further firewall.
6. The method of claim 1 wherein establishing the first communication session further comprises establishing the first communication session through a firewall and a wireless network.
7. A mobile server adapted to couple an enterprise network to a wireless communications network that is in wireless communication with a mobile communications device associated with the enterprise network, the mobile server comprising:
a service manager adapted to:
establish a first communications session with the mobile communications device; and
establish, concurrent with the first communications session, a further communications session with a service external to the mobile server, the further communications session being established by the mobile server as a session proxy for the mobile communications device.
8. The mobile server of claim 7 further comprising a configuration database storing service identification information associated with the mobile communications device.
9. The mobile server of claim 8 wherein the service manager is configured to:
retrieve the service identification information from the configuration database; and
select, based on the service identification information, the service for the establishing of the further communications session.
10. The mobile server of claim 7 wherein the service manager is configured to:
receive, from the mobile communications device over the first communications session, a status notification message; and
transmit, from the mobile server to the service over the further communications session, the status notification message on behalf of the mobile communications devices.
11. The mobile server of claim 7 further comprising a messaging service module for forwarding email messages to the mobile communications device.
12. The mobile server of claim 7 comprising a mobile data service module for adapting content for sending to the mobile communications device.
13. The mobile server of claim 7 wherein the service manager is further adapted to establish the first communication session through a firewall and a wireless network.
14. A computer-readable medium having stored thereon computer-executable instructions which, when executed by a processor of a mobile server located in an enterprise network with which a mobile communications device is associated, configure the processor to:
establish a first communications session with the mobile communications device; and
establish, concurrent with the first communications session, a further communications session with a service external to the mobile server, the further communications session being established by the mobile server as a session proxy for the mobile communications device.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/454,456 US20120209930A1 (en) | 2007-10-23 | 2012-04-24 | Mobile server with multiple service connections |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/876,872 US7818434B2 (en) | 2007-10-23 | 2007-10-23 | Mobile server with multiple service connections |
US12/836,707 US8209423B2 (en) | 2007-10-23 | 2010-07-15 | Mobile server with multiple service connections |
US13/454,456 US20120209930A1 (en) | 2007-10-23 | 2012-04-24 | Mobile server with multiple service connections |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/836,707 Continuation US8209423B2 (en) | 2007-10-23 | 2010-07-15 | Mobile server with multiple service connections |
Publications (1)
Publication Number | Publication Date |
---|---|
US20120209930A1 true US20120209930A1 (en) | 2012-08-16 |
Family
ID=40564609
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/876,872 Active 2028-01-05 US7818434B2 (en) | 2007-10-23 | 2007-10-23 | Mobile server with multiple service connections |
US12/836,707 Active 2028-03-11 US8209423B2 (en) | 2007-10-23 | 2010-07-15 | Mobile server with multiple service connections |
US13/454,456 Abandoned US20120209930A1 (en) | 2007-10-23 | 2012-04-24 | Mobile server with multiple service connections |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/876,872 Active 2028-01-05 US7818434B2 (en) | 2007-10-23 | 2007-10-23 | Mobile server with multiple service connections |
US12/836,707 Active 2028-03-11 US8209423B2 (en) | 2007-10-23 | 2010-07-15 | Mobile server with multiple service connections |
Country Status (1)
Country | Link |
---|---|
US (3) | US7818434B2 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120306622A1 (en) * | 2011-06-06 | 2012-12-06 | Mitel Networks Corporation | Proximity session mobility |
US10277641B2 (en) | 2011-06-06 | 2019-04-30 | Mitel Networks Corporation | Proximity session mobility extension |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8780925B2 (en) * | 2006-08-17 | 2014-07-15 | Fonality, Inc. | Mobile use of a PBX system |
US8098810B2 (en) | 2007-03-09 | 2012-01-17 | Fonality, Inc. | Intelligent presence management in a communication routing system |
US8693659B2 (en) | 2007-03-09 | 2014-04-08 | Fonality, Inc. | System and method for centralized presence management of local and remote users |
US8379832B1 (en) | 2007-05-03 | 2013-02-19 | Fonality, Inc. | Universal queuing for inbound communications |
US10097695B2 (en) | 2007-08-10 | 2018-10-09 | Fonality, Inc. | System and method for providing carrier-independent VoIP communication |
US8719386B2 (en) * | 2009-01-08 | 2014-05-06 | Fonality, Inc. | System and method for providing configuration synchronicity |
US10318922B2 (en) * | 2009-03-16 | 2019-06-11 | Fonality, Inc. | System and method for automatic insertion of call intelligence in an information system |
US9443244B2 (en) | 2009-03-16 | 2016-09-13 | Fonality, Inc. | System and method for utilizing customer data in a communication system |
US8370918B1 (en) | 2011-09-30 | 2013-02-05 | Kaspersky Lab Zao | Portable security device and methods for providing network security |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080250149A1 (en) * | 2007-04-09 | 2008-10-09 | Morris Robert P | Methods And System For Providing Concurrent Access To A Resource In A Communication Session |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7327703B2 (en) | 2000-03-15 | 2008-02-05 | Samsung Electronics Co., Ltd | Method for providing concurrent service in a mobile communication system |
US20030054810A1 (en) | 2000-11-15 | 2003-03-20 | Chen Yih-Farn Robin | Enterprise mobile server platform |
US8285880B2 (en) | 2001-11-30 | 2012-10-09 | Oracle International Corporation | Servicing requests that are issued in a protocol other than the protocol expected by the service |
JP4199670B2 (en) | 2002-01-15 | 2008-12-17 | アバイア テクノロジー コーポレーション | Communication application server for converged communication services |
US7523491B2 (en) * | 2005-01-03 | 2009-04-21 | Nokia Corporation | System, apparatus, and method for accessing mobile servers |
US20060223504A1 (en) * | 2005-04-01 | 2006-10-05 | Ixi Mobile (R&D) Ltd. | Efficient server polling system and method |
US8751680B2 (en) | 2005-12-09 | 2014-06-10 | Telefonaktiebolaget L M Ericsson (Publ) | Apparatus, method and computer program for seamless session transfer |
US20070156909A1 (en) | 2005-12-29 | 2007-07-05 | Osborn William R | Proxy for extending IMS services to mobile terminals with SMS capabilities |
US7512408B2 (en) | 2006-02-16 | 2009-03-31 | Softwired Ag | Scalable wireless messaging system |
-
2007
- 2007-10-23 US US11/876,872 patent/US7818434B2/en active Active
-
2010
- 2010-07-15 US US12/836,707 patent/US8209423B2/en active Active
-
2012
- 2012-04-24 US US13/454,456 patent/US20120209930A1/en not_active Abandoned
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080250149A1 (en) * | 2007-04-09 | 2008-10-09 | Morris Robert P | Methods And System For Providing Concurrent Access To A Resource In A Communication Session |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120306622A1 (en) * | 2011-06-06 | 2012-12-06 | Mitel Networks Corporation | Proximity session mobility |
US10225354B2 (en) * | 2011-06-06 | 2019-03-05 | Mitel Networks Corporation | Proximity session mobility |
US10277641B2 (en) | 2011-06-06 | 2019-04-30 | Mitel Networks Corporation | Proximity session mobility extension |
US11153393B2 (en) * | 2011-06-06 | 2021-10-19 | Mitel Networks Corporation | System capable of interacting with devices on a network |
US11258864B2 (en) * | 2011-06-06 | 2022-02-22 | Mitel Networks Corporation | Communication device capable of interacting with devices on a network |
Also Published As
Publication number | Publication date |
---|---|
US7818434B2 (en) | 2010-10-19 |
US8209423B2 (en) | 2012-06-26 |
US20090106427A1 (en) | 2009-04-23 |
US20100281531A1 (en) | 2010-11-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8209423B2 (en) | Mobile server with multiple service connections | |
JP4629338B2 (en) | System and method for automatically transferring communication messages | |
EP1542409B1 (en) | Protocol for multi-hop ad-hoc networks | |
US7587462B2 (en) | Method and apparatus for distributing notification among cooperating devices and device channels | |
US8065419B2 (en) | Method and apparatus for a keep alive probe service | |
US7890662B2 (en) | System and method for providing unified IP presence | |
EP0959600A1 (en) | Method and apparatus for providing network access over different wireless networks | |
US20060146821A1 (en) | Virtual multicast routing for a cluster having state synchronization | |
US20120178460A1 (en) | Bypass routing to a mobile device | |
CA2557378C (en) | Communications system with interface for enabling communication of alerts to mobile wireless communications devices | |
JP2009525632A (en) | Selective service update method for communication network | |
US11968275B2 (en) | Push notifications for multiple user devices | |
JP4954328B2 (en) | Method and system for data management in a communication network | |
US20120290673A1 (en) | Implementing a web server on a mobile station | |
US7400897B2 (en) | Implementing a web server on a mobile station | |
CN110012107B (en) | Data communication method, equipment, device, system and storage medium | |
US7933291B2 (en) | Protocol neutral channel-based application communication | |
US7543030B2 (en) | Peer-to-peer communication for instant messaging between different instant message application types | |
CA2641669C (en) | Mobile server with multiple service connections | |
JP2003115795A (en) | Communication system, server for use therein, agent control method, agent control program | |
JP5601992B2 (en) | Communication system and packet processing node | |
EP1971109A1 (en) | Method and device for event signaling and communication system comprising such device | |
US8571022B1 (en) | Packet filtering by session setup association in a wireless communication system | |
JP2000148646A (en) | Push-type function server, information monitor device, push-type control method, and recording medium thereof | |
CN101416470A (en) | Interprocessor communication protocol with high level service composition |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: RESEARCH IN MOTION LIMITED, CANADA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:PLUMB, MARC;REEL/FRAME:028097/0194 Effective date: 20071015 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: MALIKIE INNOVATIONS LIMITED, IRELAND Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BLACKBERRY LIMITED;REEL/FRAME:064104/0103 Effective date: 20230511 |