[go: up one dir, main page]

MXPA06013973A - Switch-in of centralised infrastructure for management for wireless communications - Google Patents

Switch-in of centralised infrastructure for management for wireless communications

Info

Publication number
MXPA06013973A
MXPA06013973A MXPA/A/2006/013973A MXPA06013973A MXPA06013973A MX PA06013973 A MXPA06013973 A MX PA06013973A MX PA06013973 A MXPA06013973 A MX PA06013973A MX PA06013973 A MXPA06013973 A MX PA06013973A
Authority
MX
Mexico
Prior art keywords
information
wireless
server
database
wireless carrier
Prior art date
Application number
MXPA/A/2006/013973A
Other languages
Spanish (es)
Inventor
N Owen Russell
Original Assignee
Research In Motion Limited
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
Application filed by Research In Motion Limited filed Critical Research In Motion Limited
Publication of MXPA06013973A publication Critical patent/MXPA06013973A/en

Links

Abstract

After a wireless device registers with a wireless carrier, a registration process isinitiated with a provisioning server. The provisioning server, based on at leastone of a device identifier for the wireless device and an identifier of the wirelesscarrier, retrieves database information from a database. This information maybe used by the provisioning server to decide whether to return (i) address informationfor a relay server which provides centralized management services or (ii) addressinformation for an enterprise network.

Description

CONNECTION OF CENTRALIZED INFRASTRUCTURE FOR THE ADMINISTRATION OF WIRELESS COMMUNICATIONS.
BACKGROUND OF THE INVENTION. A company with a computer network may wish to provide its employees with access to the enterprise network using remote wireless devices. There is a variety of wireless network carriers that serve different geographical areas. Historically, to provide access to the business network through wireless devices, a company could first determine the geographic coverage required. Next, the company could identify one or more wireless carriers that together would provide the required geographic coverage. The company could then approach each of the identified carriers and arrange a private line of communication between the business network and the wireless carrier (often referred to as a leased line). After this, wireless devices within the geographic range of the wireless network of one of these wireless carriers could access the enterprise network using the wireless network and the communication line established between the wireless network and the enterprise network. An obvious drawback with this procedure is that the company that wants to allow wireless communication with the business network across a broad geographical area must make and maintain arrangements with many different wireless carriers. In addition, a proposed message for a wireless device that was disconnected (e.g., turned off, or was not in any of the coverage areas) would need to be retained by the business network. This is due to the fact that it would not be known which wireless carrier the wireless device would be registered with (subsequent to the entry, or switching on, the coverage area of the wireless carrier.) As a business network can not be configured to drive or to operate Efficiently undeliverable messages until they can be sent, this could prove problematic.Also, any given wireless device will normally be assigned to a different address (typically IP) when it enters each of the different wireless networks. to keep a framing in the current direction of each of the wireless devices.To address these and other difficulties, a centralized infrastructure was designed to provide centralized management services for wireless communications.The connections were negotiated between the centralized infrastructure and many d different wireless carriers in order to provide coverage geographical area. In addition, for a company that subscribes to centralized management services, the centralized infrastructure will receive messages from the corporate network destined for a wireless device, whether or not the wireless device is currently connected. Where a given wireless device is disconnected, the centralized infrastructure will store the message and transmit it to the given wireless device as long as it subsequently registers with one of the included wireless carriers. Additionally, the centralized infrastructure, by maintaining the appropriate framing tables, allows the enterprise network to communicate with each authorized wireless device regardless of which address can assign a given wireless carrier to the wireless device. Furthermore, historically, wireless carriers employ network finder technology. As such, a message addressed to a wireless device registered with a given wireless carrier is stored by the wireless carrier and must be actively recovered from the wireless carrier by the wireless device. In contrast, using the technology described in US 6,701,378 issued March 2, 2004 to Gilhuly et al. , whose contents are incorporated into the present by reference, the centralized infrastructure can - - configure to send the message on a wireless device. With the arrival of virtual private networks (VPNs) on the public Internet, the need for a leased line between a company and a wireless carrier has disappeared in many cases. This, together with the inter-carrier agreements, can make it less difficult to ensure a broad geographical coverage even when deciding a service agreement with only one carrier. In addition, the latest wireless carriers can employ pulse technology, can handle disconnections by storing and transmitting messages, and can download the wireless device solving business network problems. With such high capacity of wireless carriers and inter-carrier agreements, the centralized infrastructure described above could become an unwanted aggregate expense. This invention seeks to improve this potential problem. SUMMARY OF THE INVENTION. After a wireless device registers with a wireless carrier, a registration process is initiated with a provisioning server. The provisioning server, based on at least one of a device identifier for the wireless device and an identifier of the wireless carrier, retrieves the information from the database from a database. This information can be used by the provisioning server to decide if it returns (i) the address information by a relay server that provides centralized management services or (ii) the address information by a corporate network. According to the present invention, there is a method of handling communications, comprising: receiving from a wireless carrier network at least one of a wireless device identifier and a wireless carrier network identifier; based on at least one of said device identifier and said wireless carrier network identifier, retrieving the information from the database from a database, based at least in part on said database information, returning one of (i) address information for a server that provides centralized management services and (ii) address information for a corporate network. A computer-readable medium is also provided, which contains instructions executable by computer, whose instructions when executed by a processor of a provisioning server cause the provisioning server to implement the described method.
In a further aspect, a provisioning server is provided comprising: a database; an operable processor for: receiving from a wireless carrier network at least one of a wireless device identifier and an identifier of the wireless carrier network, based on at least one of said device identifier and said carrier network identifier wireless, retrieve information from the database from said database, based at least in part on said database information, return one of (i) address information for a server that provides centralized management services and (ii) address information for a business network. Other features and advantages of the invention will become apparent from the following description in conjunction with the drawings. BRIEF DESCRIPTION OF THE DRAWINGS. In the figures illustrating the exemplary embodiments of the invention, Figure 1 is a schematic view of a known network configuration, Figure 2 is a schematic view of a network configuration embodying the teachings of the subject invention. Figure 3 is a schematic view of a portion of the network of FIG 2, and Figure 4 is a sequence diagram showing the operation of the system of Figure 2. DETAILED DESCRIPTION. Going back to Figure 1, a company 10 has a business center network and radial link 12 with a number of communication devices 14 (such as personal computers, properly configured PCs) connected to the company's central server 16. The company server 16 is connected to the public Internet 22. A number of wireless carrier networks 24a, 24c operated by wireless carriers are also connected to the public Internet as a relay server does 26. Additional wireless carrier networks, such as as the wireless carrier network 24b are accessed by a leased line, such as line 25. The wireless communication devices 30 can be connected to one or other of the wireless carrier networks. Each of the wireless devices 30 may be associated with the business 10. A wireless device may be associated with the business 10 by directly connecting the wireless device to the PC 14 of the business network 12 while running an association process on the PC. The result is to load a device identifier for the wireless device into the enterprise network and load an identifier from the company from network 12 to the wireless device. The device identifier, which can be referred to as a PIN, is a feature of each wireless device (i.e., a PIN is burned in each wireless device). The identifier of the company which can be referred to as a user ID, or UID, does not usually change either. Another feature of each wireless device is an initial address. To provide wireless centralized management services, the relay server 26 has a communication path established with a number of wireless carrier networks. Specifically, the relay server 26 may have a communication path established with each of the wireless carrier networks 24a, 24c that connects to the public Internet 22 through a VPN. In addition, each wireless carrier network accessible only over a private line will have a private line to the relay server 26. Thus, for example, the wireless carrier network 24b has a communication path established with the relay server 26 over a leased line. The company 10 can take advantage of the centralized management services for wireless communications by installing a wireless communication management server 20 with a connection between the company server 16 and public Internet 22. Management server 20, provides the company identifier (UID) and the current company address to the relay server 26. A database on the relay server is populated with the device identifiers together with the identifier of the company and the current address of the company (called, the address for the wireless communication server 20 of the network 12 of the company 10). With the described setup, the wireless communication management server 20 with the relay server 26 can provide centralized management of wireless communications as follows. When a wireless device 30 is registered (in conventional manner) with one of the wireless carrier networks 24a, 24b, 24c with which the relay server 26 has an established communications path, the device 30 will be provided with the address of carrier wireless network (typically IP). The device will send a registration message to your initial address with your device identifier (PIN) and the company identifier (UID). The initial address may indicate to the relay server or, more typically to a registration server, that it redirects the message to the relay server. This message that is received by the relay server 26 will include an indicator of the wireless bearer network. He The identifier of the wireless carrier network may be implicit in the address of origin of the message, (i.e. the address of the wireless carrier network) or it may be explicitly contained in the message. Upon receiving this message, the relay server associates the carrier's address of the wireless network with the PIN, and returns a message to the wireless device with its own address. Any subsequent message sent by the wireless device 30 is directed to the relay server. These subsequent messages may include a UID. Using the UID (received in the Message, or associated with the PIN in the relay server), the relay server searches for the appropriate address of the company and transmits the message to the network 12 through the wireless communication server 20. A message from the business network 12 destined for a given wireless device 30 is routed through the network 12 to the relay and includes the device identifier (PIN) of the wireless device. The message is transmitted to the relay server through the wireless communication management server 20. If the relay server maintains an association of the device identifier with a given wireless carrier network address, the message is transmitted to that address of the wireless carrier network. On the other hand, if there is no association, this indicates that the wireless device of the The intended recipient is not currently connected to (i.e registered with) any of the included wireless carrier networks. In such circumstances, the relay server simply stores the message until an association of the recipient's wireless device with one of the included wireless carrier networks is realized. From the above, it will be apparent that the relay server allows the enterprise network to simply direct messages to all wireless devices in the relay, relay. In addition, the relay server allows messages to be stored for disconnected wireless devices until they are reconnected to one of the wireless carrier networks (i.e. storage and transmission services). Additionally, the relay server allows the connection through a number of wireless carrier networks, and therefore a wide geographic coverage, while the company 10 only needs to administer a single agreement with the centralized service. However, it may be that the wireless carrier network 24c is improved, in order to be able to provide one or more of the services provided by the centralized service. For example, you can connect to the Public Internet and configure yourself to do one or more of the following: store and transmit messages, use PINs AND UIDs when directing messages between wireless devices and a company, interacting with one or more other wireless carrier networks to communicate messages between a company and wireless devices associated with the company, and send messages to wireless devices. To provide a more economical service to the client, the configuration of the network of Figure 1 can be modified as illustrated in Figure 2. Returning to Figure 1, where similar parts have been given similar reference numerals, it is connected a provisioning server 50 to the public Internet 22 such as the relay server 26. To provide the option of centralized management services, the provisioning server 50 (rather than relay 26) has a communication path established with a variety of wireless carrier networks. Specifically, the provisioning server 50 may have a communication path established with each of the wireless carrier networks 24a, 24c on the public Internet 22 through a VPN. In addition, each wireless carrier network, accessible only on a private Line will have a private line to the provisioning server 50. Thus, for example, the wireless carrier network 24b may have a communication path established with the provisioning server 50 over a leased line 25. The relay server 26 has a communication path established with provisioning server 50, such as on public Internet 22 through a VPN. In addition, where the initial address of each wireless device points to a registration server, the registration server will be configured to redirect it to the provisioning server. Alternatively, the registration server itself can act as the provisioning server. Where the initial address points directly to the relay server, the provisioning server is replaced by the relay server, so that the initial address now points to the provisioning server. With this facility, and a wireless communications management server 20 installed in company 10, the company may be able to take advantage of centralized management services by providing its business identifier, the current business address and device identifiers. of the wireless devices currently associated with the company. As illustrated in Figure 3, the company identifier (UID) and the current addresses for the business network 12 and specifically, for the wireless communications management server 20 of the business network - they set up a database 28 in the server relay 26 and a database 48 in the provisioning server. Each device identifier populates the database 48 in the provisioning server 50. Additionally, a quality of service indicator (QOS) is associated with each device identifier and stored in the database 48 of the provisioning server 50. QOS indicators are provided by an administrator of the centralized management services and each QOS indicator indicates the level of service for which each wireless device is authorized (under the service plan to which it is subscribed). In addition, the database 48 on the provisioning server is also populated with capacity information for each wireless carrier network with which it has an established connection. For each wireless carrier network, this capacity information includes an indication of (i) whether the wireless carrier network may or may not store and transfer messages, (ii) whether the wireless carrier network may or may not use PINs and UIDs in addressing of messages between a company and a wireless device, (iii) whether the wireless carrier network inter-operates with one or some other wireless carrier networks to communicate messages between a company and the wireless devices associated with the company, and ( iv) if the wireless carrier network drives or no messages to wireless devices. During the operation, the relay server 26 periodically sends loading information to the provisioning server 50, which indicates the degree to which the capacity of the relay server is currently used. This loading information is stored by the provisioning server in the database 48. The provisioning server 50 may comprise a processor operating under a control program. The program and information for the database 48 may be loaded from computer readable media 52, which means may be, for example, a computer-readable diskette, an integrated memory chip, or a file loaded onto a VPN on the Internet. public. As before, r a wireless device 30 registers with one of the wireless carrier networks 24a, 24b, 2c with which the provisioning server 50 has an established communication path, the device 30 sends a registration message with its device identifier to its initial address. However, now, this message is received by the provisioning provider 50. Consequently, with reference to Figure 4, a registration (establishment) message 110 that originates from the device 30, which includes an identifier of the wireless carrier network , it is sent to provisioning server 50. As is typical with a registration message, the message includes not only the identifier of the device, but also information about the capabilities of the wireless device 30 itself. The provisioning server 50 will then make a decision as to whether the wireless device 30 should use the centralized management services provided by the relay 26 in communication with the enterprise network (via the wireless communication management server 20) or communicate directly with the the business network 12 (via the wireless communication management server 20), This decision is based on one or more of the following criteria: (i) the capabilities of the wireless carrier network with which the wireless device 30 has been registered (as revealed by the information on the capabilities of the wireless carrier network of the database 48), (ii) the current load on the relay server (based on the latest information received in this regard from the server of the relay, and stored in the database 48). (iii) the capabilities of the wireless device (as indicated in message 110), and (iv) the QOS to which the wireless device is authorized (as stored in the database 48). As an example, a decision algorithm can provide a series of thresholds to be loaded in the relay server and, associated with each major threshold loaded, a higher QOS service level that must be subscribed in order to be able to use relay 26. For communications authorized to use the relay, can provide a secondary operation of the decision algorithm, as long as the capacity information of the wireless carrier network indicates that the wireless carrier network was able to provide services that emulate those of the relay server 26, and that the wireless device was able to interconnect with the network of wireless carriers to obtain such services, the wireless device being not authorized to use the relay. If as a result of the decision algorithm, the wireless device 30 is authorized to use the relay server 26, the provisioning server directs a message 112 to the wireless device including an address for the relay server 26 and a time interval of wait. Assuming that the message 112 includes an address for the relay server, the wireless device 30 will then direct future messages, such as message 114, to the relay server and the relay server will be associated with the PIN for the device with the current one. address of the carrier of the device's wireless network and handle communications between the wireless device and the business network 12 in the manner described above. The timeout interval prompts the wireless device to activate a timer. When the timer finishes the interval, the wireless device is prompted to register again with the provisioning server by sending a message 116 to its initial address. The manner of configuring a wireless device to operate in this manner will be understood by those of skill in the art and will therefore not be further described herein. The provisioning server therefore again decides whether the wireless device 30 should use the centralized management services provided by the relay 26 in communication with the wireless communication management server 20 of the enterprise network 12 or should communicate directly with the enterprise network 12 (via wireless communication management server). It may be that as a result of modified circumstances, such as an increased load on the relay server, the decision algorithm indicates that the wireless device is not authorized to use the relay server. The provisioning server then returns a message 118 to the wireless device including an address for the wireless communication management server 20. Accordingly, the wireless device is prompted to direct future messages, such as message 120, directly to the corporate network 12 (through the wireless communication management server 20). Thus, future communications between the wireless communication management server 20 and the wireless device 30 is made directly without the intervention of the relay 26. The message 118 will also include a timeout interval so that the wireless device is driven back to the wireless network. register (through, for example, message 112), after a time interval. The address of each provisioning server 50, the relay server 26, and the enterprise network 12 (ie, the wireless communication management server 20) may be network addresses, such as supplier.central.com, rele.central .com, and company.central.com. In such a case, a message sent to that network address is translated by a directory name server (DNS) on the public Internet to an Internet Protocol (IP) address (eg 123.456.789) Alternatively, these addresses can be IP addresses. However, in such a case, these addresses may need to be updated occasionally. In this case in where, for example, the IP address of the wireless communication management server 20 changed, this would need to be communicated from the wireless communication management server 20 to the provisioning server 50. This can be carried out by the network 12, passing its current address to relay 26, which, in turn, passes this address to the provisioning server. The provisioning server would then be responsible for sending an updated message to any of the wireless devices that are currently in direct communication with the wireless communication management server 20. The provisioning server and the relay server can be found co-located , or both can be implemented on a single server with appropriate software control. In addition, although the exemplary mode has been described in conjunction with a single provisioning server and a single relay server, each can actually be a server farm. Other modifications will be apparent to those skilled in the art and, therefore, the invention is defined in the claims.

Claims (11)

  1. CLAIMS 1. A method for handling communications comprising: receiving from a wireless carrier network a wireless device identifier and a wireless carrier network identifier; based on said received device identifier and / or wireless carrier network identifier retrieving the information from the database from a database; and based at least in part on said database information, return one of (i) address information for a server that provides centralized management services and (ii) address information for a corporate network. The method of claim 1 wherein said database information comprises capacity information for said wireless carrier network. The method of claim 2 wherein said capacity information comprises any or a combination of an indication of whether the wireless carrier network may or may not store and transfer messages; an indication of whether or not the wireless carrier network uses characteristic identifiers for wireless devices and businesses when directing messages; an indication of whether the wireless carrier network inter-operates with one or more other wireless carrier networks to communicate messages between a company and the wireless devices associated with the carrier; or an indication of whether or not the wireless carrier network sends messages to wireless devices. The method of any of claims 1 to 3, further comprising: receiving load information, indicating the load on said server that provides centralized administration services, and storing said load information as database information on said basis of data. The method of any one of claims 1 to 4 which further comprises receiving the capacity information of the device with said device identifier and wherein said step of returning the address information is based in part on said device capacity information. The method of any of claims 1 to 5 wherein said database information comprises quality of service information associated with said device identifier. 7. The method of any of the claims 1 to 6 wherein said step of receiving an identifier comprises receiving a registration message from said device. The method of any of claims 1 to 7 wherein said step of returning the address information comprises returning said information in a response message addressed to a device associated with said device identifier. The method of claim 8 wherein said response message comprises an indicator for driving a future establishment message from said device. The method of claim 9 wherein said indicator indicates a waiting interval. The method of any of claims 1 to 10 wherein said return is returned to said wireless carrier network. 12. A provisioning server comprising: a database an operable processor for: receiving from a wireless carrier network a wireless device identifier and a wireless carrier network identifier; based on said device identifier and / or received wireless carrier network identifier, retrieve information from the database from said database; and based at least in part on said database information, return one of (i) address information for a server that provides centralized management services and (ii) address information for a corporate network. The server of claim 12 wherein said database information comprises capacity information for said wireless carrier network. The server of claim 12 or claim 13 wherein said processor is further operable to: receive load information indicating the load on a server that provides centralized management services; and storing said loading information as information from the database in said database. 15. The server of any of claims 12 to 14 wherein said database information further comprises information on the capacity of the device. 16. The server of any of claims 12 to 15 wherein said information of the The database further comprises information on the quality of service associated with said device identifier. The server of any of claims 12 to 16 wherein said processor is also operable to return a timeout interval. 18. A computer readable medium containing computer instructions executable by a processor of the provisioning server of any of claims 12 to 17 for causing said provisioning server to operate in accordance with the method of any of claims 1 to 11. 19. A computer program code contained in a machine readable medium, said computer program code being executable by a processor of the provisioning server of any of claims 12 to 17 to cause said provisioning server to operate in accordance with the method of any of claims 1 to 11.
MXPA/A/2006/013973A 2004-09-15 2006-11-30 Switch-in of centralised infrastructure for management for wireless communications MXPA06013973A (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP04104473 2004-09-15

Publications (1)

Publication Number Publication Date
MXPA06013973A true MXPA06013973A (en) 2008-09-26

Family

ID=

Similar Documents

Publication Publication Date Title
US6754321B1 (en) Naming convention for different types of device, and apparatus and methods using the naming convention
US7844745B1 (en) Alternate home subscriber server (HSS) node to receive a request if a first HSS node cannot handle said request
US6785256B2 (en) Method for extending mobile IP and AAA to enable integrated support for local access and roaming access connectivity
US6538996B1 (en) Remote computer communication
EP2521402A1 (en) System with a dual mode WLAN/GSM terminal in which calls are established over WLAN or GSM network
US8054805B2 (en) Method, apparatus and system for obtaining MIH service information
US7359352B2 (en) Apparatus and method for processing data call in private wireless high-speed data system
KR20030034751A (en) Method for transferring data form a server of virtual private network to mobile node
EP1793538B1 (en) Seamless mobility in layer 2 radio access networks
CN100521812C (en) Dynamic selection of a packet data serving node
US7701898B2 (en) Switch-in of centralised infrastructure for management for wireless communications
JP2011045107A (en) Switch-in of centralized infrastructure for management for wireless communications
MXPA06013973A (en) Switch-in of centralised infrastructure for management for wireless communications
US7647379B2 (en) System and method for re-routing messaging traffic to external resources
US7215953B2 (en) Private wireless high-speed data system and data service method
WO2024001563A1 (en) Message routing method and apparatus, and system
CN114727278B (en) Address changing method and device for single NRF network element
US20250310740A1 (en) Federated eas discovery
HK1087275B (en) Centralised infrastructure for management of wireless communications
US11856547B2 (en) Method of registering a service in a telecommunication network having a service based architecture, SBA, as well as a corresponding collection controller
WO2025017686A1 (en) Method and system for provisioning slice information in a communication network
JP2003209557A (en) Communication network and method for setting service information used in the same