WO2011139926A2 - Communication protocol preferences - Google Patents
Communication protocol preferences Download PDFInfo
- Publication number
- WO2011139926A2 WO2011139926A2 PCT/US2011/034694 US2011034694W WO2011139926A2 WO 2011139926 A2 WO2011139926 A2 WO 2011139926A2 US 2011034694 W US2011034694 W US 2011034694W WO 2011139926 A2 WO2011139926 A2 WO 2011139926A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- communication
- computer
- protocol
- implemented method
- recited
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/167—Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/24—Negotiation of communication capabilities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/08—Mobility data transfer
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5007—Internet protocol [IP] addresses
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
- H04W80/045—Network layer protocols, e.g. mobile IP [Internet Protocol] involving different protocol versions, e.g. MIPv4 and MIPv6
Definitions
- computing devices and communication networks facilitate the collection and exchange of information.
- a computing device can engage in data communications with a wide variety of computing devices.
- a computing device can interact with specific computing devices by specifying data packets intended for specific network-based addresses.
- the external computing devices Prior to initiating connectivity to the communication network, however, the external computing devices must have some type of agreement with the computing devices associated with communication networks, often referred to as gateway computing devices, as to the communication protocols that will be utilized to facilitate communication.
- telecommunications-based devices such as mobile terminals, establish communications with gateway computing devices via a wireless communication network.
- the gateway computing devices provide data communication to data networks, such as the local area network or wide area networks (e.g., the Internet).
- data networks such as the local area network or wide area networks (e.g., the Internet).
- a service provider maintains the wireless access communication network and gateway computing device for telecommunications-based devices that are associated with subscribers/customers of the service provider, often referred to as a home network.
- multiple service providers have business relationships that allow telecommunications-based devices that are not associated with subscribers/customer of the particular service provider to use a foreign/visitor radio access network to access other data networks.
- the non-subscribers telecommunications-based devices are often referred to as roaming telecommunications-based devices from the perspective of the service provider and the wireless communication network are often referred to as visiting networks/foreign networks from the perspective of the non-subscriber telecommunications-based device.
- Subscriber telecommunications-based devices are often configured with software applications, configurations, or other settings that specify the type of communication protocols that will be utilized to establish communications with the home network gateway computing devices.
- a home network service provider can provision subscriber telecommunications-based device with the specification of the specific type of addressing protocol that will be utilized to transmit data via the home network.
- visiting network service providers typically have not ability to configure roaming telecommunications-based devices prior to the roaming telecommunications-based devices attempting to establish communications with the visiting network.
- these non-subscriber telecommunications-based devices may be configured in accordance with their respective home network configurations that may be incompatible or non-optimal with the corresponding configurations for the visiting network.
- FIGURE 1 is a block diagram illustrative of a telecommunication environment including a number of telecommunication devices and gateway computing devices;
- FIGURE 2 is a block diagram illustrative of components of a telecommunication device for use the generation, management and display of group-based information
- FIGURES 3A and 3B are block diagrams of the telecommunication environment of FIGURE 1 illustrating an embodiment for the specification of communication protocols between a mobile telecommunications-based device and a gateway computing device;
- FIGURES 4A and 4B are block diagrams of the telecommunication environment of FIGURE 1 illustrating another embodiment for the specification of communication protocols between a mobile telecommunications-based device and a gateway computing device;
- FIGURE 5 is a flow diagram illustrative of a communication request processing routine implemented by a gateway computing device in a telecommunication environment
- FIGURE 6 is a flow diagram illustrative of a communication requesting routing implemented by a mobile telecommunications-based device in a telecommunication environment
- FIGURE 7 is a flow diagram illustrative of a communication protocol selection sub-routine implemented by a telecommunications-based device in a telecommunication environment.
- gateway computing devices corresponding to a radio communication network can specify an ordered preference of one or more communication protocols that will be used telecommunications-based devices accessing the wireless communication network. Additionally, by integrating the specification of the ordered preference of the one more communication protocols into a response to initial access request, the requesting telecommunications-based device can mitigate the need for repeating access requests.
- the present disclosure will be discussed with regard to the specification of an ordered preference for various addressing protocols utilized in conjunction with data packet delivery via the wireless communication networks including the Internet Protocol version 4 ("IPv4") and the Internet Protocol version 6 (“IPv6”) addressing protocols.
- Such communication paths can include wireless communication paths (via infra-red, RF, optical, terrestrial, or satellite communication media) and wired communication paths.
- a telecommunications-based device may also be referred to as a wireless computing device, a mobile communication device, a mobile terminal, or a computing device. Examples of telecommunication devices are described below with regard to FIGURE 1. Accordingly, reference to a telecommunication device should not be interpreted as including any particular functionality or operation not described in the present disclosure.
- the telecommunication device communication environment 100 can include a number of telecommunications-based device 102 associated with a user.
- the telecommunications-based device 102 can correspond to a wide variety of devices or components that are capable of initiating, receiving or facilitating communications over a radio communication network 104 including, but not limited to, personal computing devices, electronic book readers (e.g., e-book readers), hand held computing devices, integrated components for inclusion in computing devices, home electronics, appliances, vehicles, machinery, landline telephones, network-based telephones (e.g., voice over BP ("VoIP”), cordless telephones, cellular telephones, smart phones, modems, personal digital assistants, laptop computers, gaming devices, media devices, and the like.
- VoIP voice over BP
- the telecommunications-based device 102 include a wide variety of software and hardware components for establishing communications over one or more communication networks, including wireless communication network 104 or a wired communication network (not shown). Illustrative components of a telecommunications-based device 102 will be described in greater detail with regard to FIGURE 2.
- the gateway computing devices can include a mobility management anchor computing device 106 for obtaining requests for connectivity to communication networks from telecommunications-based devices 102 via the wireless communication network 104.
- the mobility management anchor computing device 106 may correspond to a Mobility Management Entity ("MME") key control node as specified for the Long Term Evolution (“LTE”) air interface protocol.
- MME Mobility Management Entity
- LTE Long Term Evolution
- the mobility management anchor computing device 106 may correspond to the Serving GPRS Support Node ("SGSN") node in according the General Packet Radio Service (“GPRS”) and Universal Mobile Telecommunications System (“UMTS”) air interface protocols.
- SGSN Serving GPRS Support Node
- GPRS General Packet Radio Service
- UMTS Universal Mobile Telecommunications System
- the mobility management anchor computing device 106 is not limited to any specific structure or component of any one air interface protocol.
- the mobility management anchor computing device 106 can maintain data, such as in the form of data tables, that facilitate the selection of an ordered preference of communication protocols to be utilized by telecommunications-based device 102.
- the mobility management anchor computing device 106 can maintain one or more communication protocol data stores 108 for maintaining the data for determining the ordered preference of communication protocols.
- the communication protocol data stores 108 may correspond to a single data store or a set of data stores, maintain either locally or in a distributed manner. Still further, at least some portion of the communication protocol data stores 108 may correspond to service provider home networks. Additionally, at least some portion of the communication protocol data stores 108 may correspond to service provider visited networks.
- the telecommunication device communication environment 100 can further include one or more access gateway computing devices 110 that facilitate, or otherwise provider, data connectivity to the communication network 112.
- the telecommunication device communication environment 100 can include a number of additional components, systems and/or subsystems for facilitating communications with the telecommunications-based devices 102 and/or the mobility management anchor computing device 106, or other devices.
- the additional components can facilitate wireless communication network 104, such as a cellular radio access network, a wireless network based on the family of IEEE 802.11 technical standards ("WiFi"), a wireless network based on IEEE 802.16 standards (“WiMax”), a converged wireless telecommunication network such as Unlicensed Mobile Access (“UMA”), or General Access Network (“GAN”), and other wireless networks.
- WiFi wireless network based on the family of IEEE 802.11 technical standards
- WiMax wireless network based on IEEE 802.16 standards
- UMA Unlicensed Mobile Access
- GAN General Access Network
- the operation of mobile communication networks, such as wireless communication network 104 are well known and will not be described in greater detail.
- the wireless communication network 104 is illustrated as a single communication network, one skilled in the relevant art will
- the telecommunications-based device 102 may include one or more processing units 202, such as one or more CPUs.
- the telecommunications-based device 102 may also include system memory 204, which may correspond to any combination of volatile and/or non- volatile storage mechanisms.
- the system memory 204 may store information which provides an operating system component 206, various program components 208, program data 210, and other components.
- the above-enumerated list of components is representative and is not exhaustive of the types of functions performed, or components implemented, by the telecommunications-based device 102.
- the telecommunications-based device 102 performs functions by using the processing unit(s) 202 to execute instructions provided by the system memory 204.
- the telecommunications-based device 102 may also include one or more input devices 212 (keyboard, mouse device, specialized selection keys, etc.) and one or more output devices 214 (displays, printers, audio output mechanisms, etc.).
- the telecommunications-based device 102 may also include one or more types of removable storage 216 and one or more types of non-removable storage 218. Still further, the telecommunications-based device 102 can include communication components 220 for facilitating communication via wired and wireless communication networks, such as the wireless communication network 104 and data network 118 (FIGURE 1).
- Examples of various communication protocols include, but are not limited to, Bluetooth, the family of IEEE 802.11 technical standards (“WiFi”), the IEEE 802.16 standards (“WiMax), short message service (“SMS”), voice over IP (“VoIP”) as well as various generation cellular air interface protocols (including, but not limited to, air interface protocols based on CDMA, TDMA, GSM, WCDMA, CDMA2000, TD-SCDMA, WTDMA, LTE, OFDMA, and similar technologies).
- WiFi the family of IEEE 802.11 technical standards
- WiMax the IEEE 802.16 standards
- SMS short message service
- VoIP voice over IP
- various generation cellular air interface protocols including, but not limited to, air interface protocols based on CDMA, TDMA, GSM, WCDMA, CDMA2000, TD-SCDMA, WTDMA, LTE, OFDMA, and similar technologies.
- a telecommunications-based device 102 transmits a request to establish communications via the wireless communication network 104.
- the request from the telecommunications-based device 102 includes a specification of the addressing protocols to be utilized by the telecommunications-based device 102 in data communications.
- the telecommunications-based device 102 request included a specification, by the telecommunications-based device 102, of the IPv6 addressing protocol. If the receiving mobility management anchor computing device 106 does not support IPv6 addressing, or otherwise does not wish the requesting telecommunications- based device 102 to utilize the IPv6 addressing protocol, the mobility management anchor computing device 106 would process and reject the request submitted by the telecommunications- based device 102.
- the telecommunications-based device 102 upon receipt of the rejection to the IPv6-based request, the telecommunications-based device 102 would have to transmit a new communication request.
- the telecommunications-based device 102 would specify a different addressing protocol, illustrative IPv4. Assuming the mobility management anchor computing device 106 supports IPv4 addressing for the requesting telecommunications-based device 102, the mobility management anchor computing device 106 would process and accept the request.
- this traditional approach can be inefficient in requiring at least two or more requests from the telecommunications-based device 102.
- FIGURES 3A and 3B may be especially predominant in situations in which the telecommunications-based device 102 is roaming and the mobility management anchor computing device 106 corresponding to a visited network.
- FIGURES 4A and 4B an illustrative example of another embodiment for the specification of communication protocols between a mobile telecommunications-based device 102 and a gateway computing devices, such as the mobility management anchor computing device 106, will be described.
- a telecommunications-based device 102 transmits a request to establish communications via the wireless communication network 104.
- the request from the telecommunications-based device 102 does include a specification of the addressing protocols to be utilized by the telecommunications-based device 102 in data communications.
- the request does not include any specification of the addressing protocol to be utilized.
- the request can include preferences for addressing protocols, or a specification of an addressing protocol can be treated as a preference for an addressing protocol.
- the mobility management anchor computing device 106 processes the initial communication request and transmits and acknowledgement/notification to the telecommunications-based device 102. Included in the acknowledgement/notification is an ordered set of addressing protocols the mobility management anchor computing device 106 is specifying for the requesting telecommunications-based device 102.
- the ordered set of addressing protocols is determined, at least in part, on attributes of the telecommunications-based device 102 and can include the specification of a single specified addressing protocol.
- the telecommunications-based device 102 upon receipt of the acknowledgment/notification, processes the ordered set of addressing protocols to select an addressing protocol. The telecommunications-based device 102 then utilizes the selected addressing protocol to establish data communications via the mobility management anchor computing device 106. Additionally, in the event that more than one addressing protocol is specified in the ordered set of addressing protocols, the telecommunications-based device 102 may attempt to establish data connection multiple times in the order of the ordered set of preferences until it can achieve data communications via the mobility management anchor computing device 106.
- FIGURE 5 a flow diagram illustrative of a communication request processing routine 500 implemented by a gateway computing device in telecommunication environment 100, such as the mobility management anchor computing device 106, will be described.
- the mobility management anchor computing device 106 obtains a request to establish data communications from a computing device, such as telecommunications-based device 102 via the wireless communication network 104.
- the request to establish data communications can correspond to an attach request transmitted from the telecommunications-based device 102.
- the request from the telecommunications-based device 102 can include one or more attributes of the telecommunications-based device 102 (or user of the telecommunications-based device 102) that will be utilized by the mobility management anchor computing device 106 as described below.
- the attributes of the telecommunications-based device 102 may specifically be included in the request, such as via an application programming interface ("API") or inferred from the communication request.
- API application programming interface
- the mobility management anchor computing device 106 processes the request to determine the ordered set of communication protocols to be utilized in data communications with the requesting telecommunications-based device 102.
- the ordered set of set communication protocols includes an ordered set of addressing protocols, which can include the specification of a single addressing protocol. Still further, the ordered set can be specified such that the first specified addressing protocol is considered a primary addressing protocol and any additional specified addressing protocols are considered secondary addressing protocols.
- the determination of the ordered set of communication protocols can be facilitated through data tables maintained by the mobility management anchor computing device 106 in the communication protocol data stores 108.
- the data tables correspond to static tables that define the ordered set of addressing protocols (or other communication protocols) in accordance with one or more attributes associated with the telecommunications-based device 102.
- the attributes utilized in the selection of the ordered set can include telecommunications-based device 102 device type, roaming status (e.g., in home network vs.
- the attributes can correspond to information that can assist in the optimization of the performance of the telecommunications-based device 102 or in the level of service being provided to the user of the telecommunications-based device 102.
- the mobility management anchor computing device 106 can dynamically determine the ordered set of communication protocols in accordance with the above-referenced attributes. Additionally, the mobility management anchor computing device 106 can dynamically modify a static specification of the ordered set of communication protocols.
- the mobility management anchor computing device 106 transmits an acceptance of the communication request, such as an attach accept, or other acknowledgement/notification to the requesting telecommunications-based device 102.
- the transmitted acceptance includes the specification (either directly or indirectly) of the ordered set of communication protocols.
- the processing of the ordered set of communication protocols will be described with regard to FIGURES 6 and 7.
- the mobility management anchor computing device 106 obtains an initiation of communications from the requesting telecommunications-based device 102, such as a receive attach acknowledgement, with a selected communication protocol from the ordered set of communication protocols.
- the routine 500 ends.
- the telecommunications-based device 102 transmits a communication request to the mobility management anchor computing device 106 via the wireless communication network 104.
- the communication request can correspond to an attach request.
- the communication request can include attribute information utilized by the mobility management anchor computing device 106 to process the request and specify an ordered set of communication protocols in reply.
- the attribute information may be specifically provided as part of the communication request. Alternatively, the attribute information may be included indirectly provided, such as embedded in addressing information.
- the telecommunications-based device 102 obtains a reply from the mobility management anchor computing device 106.
- the reply from the mobility management anchor computing device 106 corresponds to an acceptance of the communication request or other notification/acknowledgement.
- the reply includes the specification of an ordered set of communication protocols the telecommunications-based device 102 may utilize in data communications.
- the telecommunications-based device 102 processes the ordered set of communication protocol to select a communication protocol, such as to select an addressing protocol. An example of the processing of the ordered set of communication protocols will be described with regard to sub-routine 700 (FIGURE 7).
- the telecommunications-based device 102 initiates communications with the selected communication protocol.
- the routine 600 terminates.
- the telecommunications-based device 102 obtains the ordered set of communication protocols, such as addressing protocols.
- the ordered set of protocols can include a specification of a single communication protocol.
- the ordered set of protocols can designate primary and secondary communication protocols.
- a test is conducted to determine whether a single communication protocol has been specified in the ordered set of communication protocols. If so, at block 706, the specified communication protocol is selected and the sub-routine 700 terminates such that the telecommunications-based device 102 will attempt to establish communications in accordance with the selected communication protocol.
- the telecommunications-based device 102 selects the primary designated communication protocol and then attempts to establish communications in accordance with the selected communication protocol.
- a test is conducted to determine whether the telecommunications-based device 102 was able to establish communications in accordance with the selected communication protocol. If so, the sub-routine 700 terminates at block 712. Alternatively, if the telecommunications-based device 102 was not able to establish communications in accordance with the selected communication protocol, at block 714, the telecommunications-based device 102 selects the secondary communication protocol and then attempts to establish communications in accordance with the selected communication protocol.
- a test is conducted to determine whether the telecommunications-based device 102 was able to establish communications in accordance with the selected communication protocol. If so, the sub-routine 700 terminates at block 718. Alternatively, the sub-routine 700 terminates in an error at block 720 (or repeats decision block 716 for additional secondary designated communication protocols.
- All of the processes described herein may be embodied in, and fully automated via, software code modules executed by one or more general purpose computers or processors.
- the code modules may be stored in any type of computer-readable medium or other computer storage device. Some or all the methods may alternatively be embodied in specialized computer hardware.
- the components referred to herein may be implemented in hardware, software, firmware or a combination thereof. As such, reference in the disclosure to actions performed by a module or component relates to the execution of executable instructions by a processing device, or devices, to cause the referenced action to be performed.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Systems and methods for the management of communications related to telecommunications-based devices are provided. Telecommunications-based devices initiate requests to gateway computing devices corresponding to a radio communication network to establish data communications. The gateway computing device accepts the communication request and specifies an ordered preference of one or more communication protocols that will be used telecommunications-based devices accessing the wireless communication network. The telecommunications-based device processes the acceptance and selects a communication protocol from the ordered preference provided by the gateway computing device.
Description
COMMUNICATION PROTOCOL PREFERENCES
BACKGROUND
[0001] Generally described, computing devices and communication networks facilitate the collection and exchange of information. Utilizing a communication network and relevant communication protocols, a computing device can engage in data communications with a wide variety of computing devices. For example, in accordance with an addressing protocol, a computing device can interact with specific computing devices by specifying data packets intended for specific network-based addresses. Prior to initiating connectivity to the communication network, however, the external computing devices must have some type of agreement with the computing devices associated with communication networks, often referred to as gateway computing devices, as to the communication protocols that will be utilized to facilitate communication.
[0002] In accordance with a telecommunications-based environment, telecommunications-based devices, such as mobile terminals, establish communications with gateway computing devices via a wireless communication network. The gateway computing devices provide data communication to data networks, such as the local area network or wide area networks (e.g., the Internet). Typically, a service provider maintains the wireless access communication network and gateway computing device for telecommunications-based devices that are associated with subscribers/customers of the service provider, often referred to as a home network. Additionally, multiple service providers have business relationships that allow telecommunications-based devices that are not associated with subscribers/customer of the particular service provider to use a foreign/visitor radio access network to access other data networks. The non-subscribers telecommunications-based devices are often referred to as roaming telecommunications-based devices from the perspective of the service provider and the wireless communication network are often referred to as visiting networks/foreign networks from the perspective of the non-subscriber telecommunications-based device.
[0003] Subscriber telecommunications-based devices are often configured with software applications, configurations, or other settings that specify the type of communication protocols that will be utilized to establish communications with the home network gateway
computing devices. For example, a home network service provider can provision subscriber telecommunications-based device with the specification of the specific type of addressing protocol that will be utilized to transmit data via the home network. In contrast, visiting network service providers typically have not ability to configure roaming telecommunications-based devices prior to the roaming telecommunications-based devices attempting to establish communications with the visiting network. Moreover, these non-subscriber telecommunications-based devices (e.g., roaming telecommunications-based devices) may be configured in accordance with their respective home network configurations that may be incompatible or non-optimal with the corresponding configurations for the visiting network.
BRIEF DESCRIPTION OF THE DRAWINGS
[0004] The foregoing aspects and many of the attendant advantages of the present disclosure will become more readily appreciated as the same become better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:
[0005] FIGURE 1 is a block diagram illustrative of a telecommunication environment including a number of telecommunication devices and gateway computing devices;
[0006] FIGURE 2 is a block diagram illustrative of components of a telecommunication device for use the generation, management and display of group-based information;
[0007] FIGURES 3A and 3B are block diagrams of the telecommunication environment of FIGURE 1 illustrating an embodiment for the specification of communication protocols between a mobile telecommunications-based device and a gateway computing device;
[0008] FIGURES 4A and 4B are block diagrams of the telecommunication environment of FIGURE 1 illustrating another embodiment for the specification of communication protocols between a mobile telecommunications-based device and a gateway computing device;
[0009] FIGURE 5 is a flow diagram illustrative of a communication request processing routine implemented by a gateway computing device in a telecommunication environment;
[0010] FIGURE 6 is a flow diagram illustrative of a communication requesting routing implemented by a mobile telecommunications-based device in a telecommunication environment; and
[0011] FIGURE 7 is a flow diagram illustrative of a communication protocol selection sub-routine implemented by a telecommunications-based device in a telecommunication environment.
DETAILED DESCRIPTION
[0012] Generally described, aspects of the present disclosure relate to the management of communications related to telecommunications-based devices. In an illustrative embodiment, gateway computing devices corresponding to a radio communication network can specify an ordered preference of one or more communication protocols that will be used telecommunications-based devices accessing the wireless communication network. Additionally, by integrating the specification of the ordered preference of the one more communication protocols into a response to initial access request, the requesting telecommunications-based device can mitigate the need for repeating access requests. Illustratively, the present disclosure will be discussed with regard to the specification of an ordered preference for various addressing protocols utilized in conjunction with data packet delivery via the wireless communication networks including the Internet Protocol version 4 ("IPv4") and the Internet Protocol version 6 ("IPv6") addressing protocols.
[0013] Although aspects of the present disclosure will be described with regard to an illustrative telecommunication environment and component interactions, communication protocols and flow diagrams, one skilled in the relevant art will appreciate that the disclosed embodiments are illustrative in nature and should not be construed as limiting. Specifically, although the present disclosure will be described with regard to the two above-referenced addressing protocols, the systems and methods in the present disclosure may utilized in conjunction with various communication protocols, including additional or different addressing protocols. Additionally, although the term telecommunication device is used in this document, the term represents any type of device having a component for communicating with one or more other devices via one or more communication paths. Such communication paths can include wireless communication paths (via infra-red, RF, optical, terrestrial, or satellite communication media) and
wired communication paths. Still further, although the present disclosure references a telecommunications-based device, one skilled in the relevant art will appreciate that a telecommunications-based device may also be referred to as a wireless computing device, a mobile communication device, a mobile terminal, or a computing device. Examples of telecommunication devices are described below with regard to FIGURE 1. Accordingly, reference to a telecommunication device should not be interpreted as including any particular functionality or operation not described in the present disclosure.
[0014] With reference now to FIGURE 1, a block diagram illustrative of a telecommunication environment 100 will be described. The telecommunication device communication environment 100 can include a number of telecommunications-based device 102 associated with a user. The telecommunications-based device 102 can correspond to a wide variety of devices or components that are capable of initiating, receiving or facilitating communications over a radio communication network 104 including, but not limited to, personal computing devices, electronic book readers (e.g., e-book readers), hand held computing devices, integrated components for inclusion in computing devices, home electronics, appliances, vehicles, machinery, landline telephones, network-based telephones (e.g., voice over BP ("VoIP"), cordless telephones, cellular telephones, smart phones, modems, personal digital assistants, laptop computers, gaming devices, media devices, and the like. In an illustrative embodiment, the telecommunications-based device 102 include a wide variety of software and hardware components for establishing communications over one or more communication networks, including wireless communication network 104 or a wired communication network (not shown). Illustrative components of a telecommunications-based device 102 will be described in greater detail with regard to FIGURE 2.
[0015] With continued reference to FIGURE 1, in communication with the telecommunications-based devices 102 are a number of computing devices, generally referred to as gateway computing devices. Specifically, as illustrated in FIGURE 1, the gateway computing devices can include a mobility management anchor computing device 106 for obtaining requests for connectivity to communication networks from telecommunications-based devices 102 via the wireless communication network 104. Illustratively, the mobility management anchor computing device 106 may correspond to a Mobility Management Entity ("MME") key control node as
specified for the Long Term Evolution ("LTE") air interface protocol. In another example, the mobility management anchor computing device 106 may correspond to the Serving GPRS Support Node ("SGSN") node in according the General Packet Radio Service ("GPRS") and Universal Mobile Telecommunications System ("UMTS") air interface protocols. One skilled in the relevant art will appreciate that the mobility management anchor computing device 106 is not limited to any specific structure or component of any one air interface protocol.
[0016] As will be discussed in greater detail below, the mobility management anchor computing device 106 can maintain data, such as in the form of data tables, that facilitate the selection of an ordered preference of communication protocols to be utilized by telecommunications-based device 102. Specifically, the mobility management anchor computing device 106 can maintain one or more communication protocol data stores 108 for maintaining the data for determining the ordered preference of communication protocols. The communication protocol data stores 108 may correspond to a single data store or a set of data stores, maintain either locally or in a distributed manner. Still further, at least some portion of the communication protocol data stores 108 may correspond to service provider home networks. Additionally, at least some portion of the communication protocol data stores 108 may correspond to service provider visited networks. The telecommunication device communication environment 100 can further include one or more access gateway computing devices 110 that facilitate, or otherwise provider, data connectivity to the communication network 112.
[0017] In an illustrative embodiment, the telecommunication device communication environment 100 can include a number of additional components, systems and/or subsystems for facilitating communications with the telecommunications-based devices 102 and/or the mobility management anchor computing device 106, or other devices. The additional components can facilitate wireless communication network 104, such as a cellular radio access network, a wireless network based on the family of IEEE 802.11 technical standards ("WiFi"), a wireless network based on IEEE 802.16 standards ("WiMax"), a converged wireless telecommunication network such as Unlicensed Mobile Access ("UMA"), or General Access Network ("GAN"), and other wireless networks. The operation of mobile communication networks, such as wireless communication network 104 are well known and will not be described in greater detail. Additionally, although the wireless communication network 104 is illustrated as a single
communication network, one skilled in the relevant art will appreciate that the communication network can be made up of any number of public or private communication networks and/or network connections.
[0018] With reference now to FIGURE 2, illustrative components of a telecommunication device, such as telecommunications-based device 102, for use in the creation and display of group-based information displays will be described. The telecommunications-based device 102 may include one or more processing units 202, such as one or more CPUs. The telecommunications-based device 102 may also include system memory 204, which may correspond to any combination of volatile and/or non- volatile storage mechanisms. The system memory 204 may store information which provides an operating system component 206, various program components 208, program data 210, and other components. The above-enumerated list of components is representative and is not exhaustive of the types of functions performed, or components implemented, by the telecommunications-based device 102. One skilled in the relevant art will appreciate that additional or alternative components may also be included in the telecommunications-based device 102 to carry out other intended functions such as a mobile telephone functions. The telecommunications-based device 102 performs functions by using the processing unit(s) 202 to execute instructions provided by the system memory 204. The telecommunications-based device 102may also include one or more input devices 212 (keyboard, mouse device, specialized selection keys, etc.) and one or more output devices 214 (displays, printers, audio output mechanisms, etc.).
[0019] With continued reference to FIGURE 2, the telecommunications-based device 102 may also include one or more types of removable storage 216 and one or more types of non-removable storage 218. Still further, the telecommunications-based device 102 can include communication components 220 for facilitating communication via wired and wireless communication networks, such as the wireless communication network 104 and data network 118 (FIGURE 1). Examples of various communication protocols include, but are not limited to, Bluetooth, the family of IEEE 802.11 technical standards ("WiFi"), the IEEE 802.16 standards ("WiMax), short message service ("SMS"), voice over IP ("VoIP") as well as various generation cellular air interface protocols (including, but not limited to, air interface protocols based on
CDMA, TDMA, GSM, WCDMA, CDMA2000, TD-SCDMA, WTDMA, LTE, OFDMA, and similar technologies).
[0020] With reference now to FIGURES 3 A and 3B, an illustrative example of an embodiment for the specification of communication protocols between a mobile telecommunications-based device 102 and a gateway computing devices, such as the mobility management anchor computing device 106, will be described. With reference to FIGURE 3 A, in a traditional embodiment, a telecommunications-based device 102 transmits a request to establish communications via the wireless communication network 104. In this traditional embodiment, the request from the telecommunications-based device 102 includes a specification of the addressing protocols to be utilized by the telecommunications-based device 102 in data communications.
[0021] For purposes of illustration, assume that the telecommunications-based device 102 request included a specification, by the telecommunications-based device 102, of the IPv6 addressing protocol. If the receiving mobility management anchor computing device 106 does not support IPv6 addressing, or otherwise does not wish the requesting telecommunications- based device 102 to utilize the IPv6 addressing protocol, the mobility management anchor computing device 106 would process and reject the request submitted by the telecommunications- based device 102.
[0022] With reference now to FIGURE 3B, in the same traditional embodiment, upon receipt of the rejection to the IPv6-based request, the telecommunications-based device 102 would have to transmit a new communication request. In this second request, the telecommunications-based device 102 would specify a different addressing protocol, illustrative IPv4. Assuming the mobility management anchor computing device 106 supports IPv4 addressing for the requesting telecommunications-based device 102, the mobility management anchor computing device 106 would process and accept the request. However, as illustrated in FIGURES 3A and 3B, this traditional approach can be inefficient in requiring at least two or more requests from the telecommunications-based device 102. The embodiment illustrated in FIGURES 3A and 3B may be especially predominant in situations in which the telecommunications-based device 102 is roaming and the mobility management anchor computing device 106 corresponding to a visited network.
[0023] With reference now to FIGURES 4A and 4B, an illustrative example of another embodiment for the specification of communication protocols between a mobile telecommunications-based device 102 and a gateway computing devices, such as the mobility management anchor computing device 106, will be described. With reference to FIGURE 4A, in an illustrative embodiment, a telecommunications-based device 102 transmits a request to establish communications via the wireless communication network 104. In this illustrative embodiment, however, the request from the telecommunications-based device 102 does include a specification of the addressing protocols to be utilized by the telecommunications-based device 102 in data communications. In one embodiment, the request does not include any specification of the addressing protocol to be utilized. In another embodiment, the request can include preferences for addressing protocols, or a specification of an addressing protocol can be treated as a preference for an addressing protocol.
[0024] In contrast to the embodiment of FIGURES 3A and 3B, the mobility management anchor computing device 106 processes the initial communication request and transmits and acknowledgement/notification to the telecommunications-based device 102. Included in the acknowledgement/notification is an ordered set of addressing protocols the mobility management anchor computing device 106 is specifying for the requesting telecommunications-based device 102. The ordered set of addressing protocols is determined, at least in part, on attributes of the telecommunications-based device 102 and can include the specification of a single specified addressing protocol.
[0025] With reference now to FIGURE 4B, in this illustrative embodiment, upon receipt of the acknowledgment/notification, the telecommunications-based device 102 processes the ordered set of addressing protocols to select an addressing protocol. The telecommunications-based device 102 then utilizes the selected addressing protocol to establish data communications via the mobility management anchor computing device 106. Additionally, in the event that more than one addressing protocol is specified in the ordered set of addressing protocols, the telecommunications-based device 102 may attempt to establish data connection multiple times in the order of the ordered set of preferences until it can achieve data communications via the mobility management anchor computing device 106.
[0026] Turning now to FIGURE 5, a flow diagram illustrative of a communication request processing routine 500 implemented by a gateway computing device in telecommunication environment 100, such as the mobility management anchor computing device 106, will be described. At block 502, the mobility management anchor computing device 106 obtains a request to establish data communications from a computing device, such as telecommunications-based device 102 via the wireless communication network 104. For example, the request to establish data communications can correspond to an attach request transmitted from the telecommunications-based device 102. In an illustrative embodiment, the request from the telecommunications-based device 102 can include one or more attributes of the telecommunications-based device 102 (or user of the telecommunications-based device 102) that will be utilized by the mobility management anchor computing device 106 as described below. The attributes of the telecommunications-based device 102 may specifically be included in the request, such as via an application programming interface ("API") or inferred from the communication request.
[0027] At block 504, the mobility management anchor computing device 106 processes the request to determine the ordered set of communication protocols to be utilized in data communications with the requesting telecommunications-based device 102. In an illustrative embodiment, the ordered set of set communication protocols includes an ordered set of addressing protocols, which can include the specification of a single addressing protocol. Still further, the ordered set can be specified such that the first specified addressing protocol is considered a primary addressing protocol and any additional specified addressing protocols are considered secondary addressing protocols.
[0028] In an illustrative embodiment, the determination of the ordered set of communication protocols can be facilitated through data tables maintained by the mobility management anchor computing device 106 in the communication protocol data stores 108. Specifically, in an illustrative embodiment, the data tables correspond to static tables that define the ordered set of addressing protocols (or other communication protocols) in accordance with one or more attributes associated with the telecommunications-based device 102. Illustratively, the attributes utilized in the selection of the ordered set can include telecommunications-based device 102 device type, roaming status (e.g., in home network vs. in visiting network), roaming
plan (e.g., what is the home network and country associated with the telecommunications-based device 102), supported operating system, user descriptors (e.g., type of use or amount of data used), supported applications or applications being executed by the telecommunications-based device 102, and the like. The attributes can correspond to information that can assist in the optimization of the performance of the telecommunications-based device 102 or in the level of service being provided to the user of the telecommunications-based device 102. In an alternative embodiment, the mobility management anchor computing device 106 can dynamically determine the ordered set of communication protocols in accordance with the above-referenced attributes. Additionally, the mobility management anchor computing device 106 can dynamically modify a static specification of the ordered set of communication protocols.
[0029] At block 506, the mobility management anchor computing device 106 transmits an acceptance of the communication request, such as an attach accept, or other acknowledgement/notification to the requesting telecommunications-based device 102. The transmitted acceptance includes the specification (either directly or indirectly) of the ordered set of communication protocols. The processing of the ordered set of communication protocols will be described with regard to FIGURES 6 and 7. Thereafter, at block 508, the mobility management anchor computing device 106 obtains an initiation of communications from the requesting telecommunications-based device 102, such as a receive attach acknowledgement, with a selected communication protocol from the ordered set of communication protocols. At block 510, the routine 500 ends.
[0030] Turning now to FIGURE 6, a flow diagram illustrative of a communication requesting routing 600 implemented by a telecommunications-based device 102 will be described. At block 602, the telecommunications-based device 102 transmits a communication request to the mobility management anchor computing device 106 via the wireless communication network 104. Illustratively, the communication request can correspond to an attach request. As previously discussed, the communication request can include attribute information utilized by the mobility management anchor computing device 106 to process the request and specify an ordered set of communication protocols in reply. The attribute information may be specifically provided as part of the communication request. Alternatively, the attribute information may be included indirectly provided, such as embedded in addressing information.
[0031] At block 604, the telecommunications-based device 102 obtains a reply from the mobility management anchor computing device 106. In an illustrative embodiment, the reply from the mobility management anchor computing device 106 corresponds to an acceptance of the communication request or other notification/acknowledgement. As previously discussed, the reply includes the specification of an ordered set of communication protocols the telecommunications-based device 102 may utilize in data communications. At block 606, the telecommunications-based device 102 processes the ordered set of communication protocol to select a communication protocol, such as to select an addressing protocol. An example of the processing of the ordered set of communication protocols will be described with regard to sub-routine 700 (FIGURE 7). At block 608, the telecommunications-based device 102 initiates communications with the selected communication protocol. At block 610, the routine 600 terminates.
[0032] Referring now to FIGURE 7, a flow diagram illustrative of a communication protocol selection sub-routine 700 implemented by the telecommunications-based device 102 will be described. At block 702, the telecommunications-based device 102 obtains the ordered set of communication protocols, such as addressing protocols. As previously discussed, the ordered set of protocols can include a specification of a single communication protocol. Additionally, the ordered set of protocols can designate primary and secondary communication protocols. Accordingly, at decision block 704, a test is conducted to determine whether a single communication protocol has been specified in the ordered set of communication protocols. If so, at block 706, the specified communication protocol is selected and the sub-routine 700 terminates such that the telecommunications-based device 102 will attempt to establish communications in accordance with the selected communication protocol.
[0033] With continued reference to FIGURE 7, if at decision block 704, multiple communication protocols are specified, at block 708, the telecommunications-based device 102 selects the primary designated communication protocol and then attempts to establish communications in accordance with the selected communication protocol. At decision block 710, a test is conducted to determine whether the telecommunications-based device 102 was able to establish communications in accordance with the selected communication protocol. If so, the sub-routine 700 terminates at block 712. Alternatively, if the telecommunications-based
device 102 was not able to establish communications in accordance with the selected communication protocol, at block 714, the telecommunications-based device 102 selects the secondary communication protocol and then attempts to establish communications in accordance with the selected communication protocol. At decision block 716, a test is conducted to determine whether the telecommunications-based device 102 was able to establish communications in accordance with the selected communication protocol. If so, the sub-routine 700 terminates at block 718. Alternatively, the sub-routine 700 terminates in an error at block 720 (or repeats decision block 716 for additional secondary designated communication protocols.
[0034] All of the processes described herein may be embodied in, and fully automated via, software code modules executed by one or more general purpose computers or processors. The code modules may be stored in any type of computer-readable medium or other computer storage device. Some or all the methods may alternatively be embodied in specialized computer hardware. In addition, the components referred to herein may be implemented in hardware, software, firmware or a combination thereof. As such, reference in the disclosure to actions performed by a module or component relates to the execution of executable instructions by a processing device, or devices, to cause the referenced action to be performed.
[0035] Conditional language such as, among others, "can," "could," "might" or "may," unless specifically stated otherwise, are otherwise understood within the context as used in general to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.
[0036] Any process descriptions, elements or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or elements in the process. Alternate implementations are included within the scope of the embodiments described herein in which elements or functions
may be deleted, executed out of order from that shown, or discussed, including substantially concurrently or in reverse order, depending on the functionality involved as would be understood by those skilled in the art.
[0037] It should be emphasized that many variations and modifications may be made to the above-described embodiments, the elements of which are to be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure and protected by the following claims.
Claims
1. A computer-implemented method for managing communication in a radio network, comprising:
obtaining a communication request from a mobile device via the radio network; determining addressing protocol preferences for data communications with the mobile device, the addressing protocol preferences selected from at least two possible addressing protocols; and
transmitting an acceptance of the response to the communication request, the acceptance of the response including the addressing protocol preferences.
2. The computer-implemented method as recited in Claim 1, wherein the communication request includes identification information corresponding to at least one of the mobile device and a user of the mobile device.
3. The computer-implemented method as recited in Claim 1, wherein determining addressing protocol preferences includes:
maintaining a table defining various addressing protocol preferences mapped to one or more mobile device attributes;
determining at least one mobile device attribute associated with the communication request; and
selecting addressing protocol preferences from the table based on the at least one mobile device attribute.
4. The computer-implemented method as recited in Claim 3, wherein the one or more mobile device attributes includes mobile device type information.
5. The computer-implemented method as recited in Claim 3, wherein the one or more mobile device attributes includes mobile device roaming status.
6. The computer-implemented method as recited in Claim 3, wherein the one or more mobile device attributes include mobile device roaming plan.
7. The computer-implemented method as recited in Claim 3, wherein the one or more mobile device attributes include supported operating system.
8. The computer-implemented method as recited in Claim 3, wherein the one or more mobile device attributes includes software application information.
9. The computer-implemented method as recited in Claim 3, wherein the one or more mobile device attributes includes use description.
10. The computer-implemented method as recited in Claim 1, wherein determining addressing protocol preferences includes:
determining at least one mobile device attribute associated with the communication request; and
dynamically determining addressing protocol preferences from the table based on the at least one mobile device attribute.
11. The computer-implemented method as recited in Claim 1, wherein transmitting the acceptance of the response to the communication request includes transmitting addressing protocol preferences including at least two addressing protocols.
12. The computer-implemented method as recited in Claim 11, wherein the addressing protocol preferences include at least one primary addressing protocol and at least one secondary addressing protocol.
13. The computer-implemented method as recited in Claim 1, wherein at least one of the addressing protocols includes the Internet Protocol version four addressing protocol.
14. The computer-implemented method as recited in Claim 1, wherein at least one of the addressing protocols includes the Internet Protocol version six addressing protocol.
15. A computer-implemented method for managing communication in a communication network, comprising:
transmitting a request to establish communications via the communication network, wherein communications via the communication network can utilize two or more available communication protocols and wherein the request to establish communications does not include a specification of a communication protocol from the two or more available communication protocols;
obtaining an acceptance of the communication request, the acceptance of the communication request including an ordered preference of at least one communication protocol selected from the two or more available communication protocols;
processing the ordered preference of the at least one communication protocol to select a communication protocol; causing communications via the communication network in accordance with the selected communication protocol.
16. The computer-implemented method as recited in Claim 15, wherein transmitting the request to establish communications includes transmitting one or more device attributes utilized, at least in part, to select the ordered preference of at least one communication protocol.
17. The computer-implemented method as recited in Claim 15, wherein the communication network corresponds to a visited network and wherein transmitting the request to establish communications includes transmitting the request to establish communication to the visited network.
18. The computer-implemented method as recited in Claim 15, wherein the ordered preference includes the specification of at least two communication protocols.
19. The computer-implemented method as recited in Claim 18, wherein the ordered preference includes a designation of a primary communication protocol and a designation of a secondary communication protocol.
20. The computer-implemented method as recited in Claim 15, wherein processing the ordered preference of the at least one communication protocol to select a communication protocol includes if a single communication protocol is specified in the ordered preference, selecting the single specified single communication protocol.
21. The computer-implemented method as recited in Claim 20, wherein processing the ordered preference of the at least one communication protocol to select a communication protocol includes if two or more communication protocols are specified in the ordered preference, selecting a first communication protocol specified in the ordered preference; and causing communications via the communication network in accordance with the selected first communication protocol.
22. The computer-implemented method as recited in Claim 21, wherein processing the ordered preference of the at least one communication protocol to select a communication protocol includes if two or more communication protocols are specified in the ordered preference, selecting a second communication protocol specified in the ordered preference if communication is not achieved via the first communication protocol specified in the ordered preference; and causing communications via the communication network in accordance with the selected second communication protocol.
23. The computer-implemented method as recited in Claim 15, wherein the communications protocol is an addressing protocol.
24. The computer-implemented method as recited in Claim 23, wherein at least one of the addressing protocols includes the Internet Protocol version four addressing protocol.
25. The computer-implemented method as recited in Claim 23, wherein at least one of the addressing protocols includes the Internet Protocol version six addressing protocol.
26. A computer-implemented method for managing communications via a communications network, comprising:
obtaining, at a gateway computing device, a request to establish communications via the communication network, wherein the request does not include a specification of a communication protocol utilized in communications via the communication network; determining, by the gateway computing device, an ordered preference of communication protocols selected from at least two applicable communication protocols, wherein determining the ordered preference of communication protocols include determining the ordered preference based, at least in part, on attributes associated with the request; and
transmitting, by the gateway computing device, a confirmation of the communication request, the confirmation including the ordered preference of communication protocols.
27. The computer-implemented method as recited in Claim 26, wherein the request to establish communications via the communication network includes identification information corresponding to at least one of a mobile device or a user of the mobile device.
28. The computer-implemented method as recited in Claim 26, wherein determining the preference of communication protocols includes:
maintaining a table defining various addressing protocol preferences mapped to one or more mobile device attributes;
determining at least one mobile device attribute associated with the communication request; and selecting the ordered preference of communication protocols from the table based on the at least one mobile device attribute.
29. The computer-implemented method as recited in Claim 28, wherein the one or more mobile device attributes includes mobile device type information.
30. The computer-implemented method as recited in Claim 28, wherein the one or more mobile device attributes includes mobile device roaming status.
31. The computer-implemented method as recited in Claim 28, wherein the one or more mobile device attributes include mobile device roaming plan.
32. The computer-implemented method as recited in Claim 28, wherein the one or more mobile device attributes include supported operating system.
33. The computer-implemented method as recited in Claim 28, wherein the one or more mobile device attributes includes software application information.
34. The computer-implemented method as recited in Claim 28, wherein the one or more mobile device attributes includes use description.
35. The computer-implemented method as recited in Claim 26, wherein determining the preference of communication protocols includes:
determining at least one mobile device attribute associated with the communication request; and
dynamically selecting the ordered preference of communication protocols from the table based on the at least one mobile device attribute.
36. The computer-implemented method as recited in Claim 26, wherein transmitting the confirmation of the communication request includes transmitting an ordered preference of communication protocols including the specification of two or more communication protocols.
37. The computer-implemented method as recited in Claim 36, wherein the specification of the two or more protocols includes the specification of at least one primary and at least one secondary communication protocol.
38. The computer-implemented method as recited in Claim 26, wherein the communications protocol is an addressing protocol.
39. The computer-implemented method as recited in Claim 38, wherein at least one of the addressing protocols includes the Internet Protocol version four addressing protocol.
40. The computer-implemented method as recited in Claim 39, wherein at least one the addressing protocols includes the Internet Protocol version six addressing protocol.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP11778079.1A EP2564657B1 (en) | 2010-04-29 | 2011-04-29 | Communication protocol preferences |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/770,632 | 2010-04-29 | ||
US12/770,632 US8538405B2 (en) | 2010-04-29 | 2010-04-29 | Communication protocol preferences |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2011139926A2 true WO2011139926A2 (en) | 2011-11-10 |
WO2011139926A3 WO2011139926A3 (en) | 2012-02-02 |
Family
ID=44904412
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2011/034694 WO2011139926A2 (en) | 2010-04-29 | 2011-04-29 | Communication protocol preferences |
Country Status (3)
Country | Link |
---|---|
US (3) | US8538405B2 (en) |
EP (1) | EP2564657B1 (en) |
WO (1) | WO2011139926A2 (en) |
Families Citing this family (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE102011079402A1 (en) * | 2011-07-19 | 2013-01-24 | Bayerische Motoren Werke Aktiengesellschaft | Control device for a motor vehicle, programming device and programming system |
US9406181B2 (en) * | 2012-10-23 | 2016-08-02 | Kwikset Corporation | Electronic lock having software based automatic multi-wireless profile detection and setting |
WO2014066391A1 (en) * | 2012-10-23 | 2014-05-01 | Kwikset Corporation | Electronic lock having hardware based multi-wireless profile detection and setting |
JP6478915B2 (en) | 2012-10-26 | 2019-03-06 | スペクトラム ブランズ インコーポレイテッド | Electronic lock with mobile device user interface |
WO2014093436A1 (en) | 2012-12-12 | 2014-06-19 | Kwikset Corporation | Electronic lock system having proximity mobile device |
US10028083B2 (en) * | 2014-11-05 | 2018-07-17 | At&T Intellectual Property I, L.P. | Mobility management |
US10783731B2 (en) | 2018-04-27 | 2020-09-22 | Spectrum Brands, Inc. | Wireless tag-based lock actuation systems and methods |
US11019157B2 (en) | 2019-03-06 | 2021-05-25 | At&T Intellectual Property I, L.P. | Connectionless service and other services for devices using microservices in 5G or other next generation communication systems |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2003084185A1 (en) * | 2002-03-27 | 2003-10-09 | British Telecommunications Public Limited Company | System for selecting a connectivity mechanism |
US20060028998A1 (en) * | 2004-08-06 | 2006-02-09 | Marcello Lioy | Wireless network supporting failover between network protocols |
KR20060022937A (en) * | 2004-09-08 | 2006-03-13 | 삼성전자주식회사 | Method and apparatus for ip address autoconfiguration in mobile ad-hoc networks |
US20090037595A1 (en) * | 2007-07-31 | 2009-02-05 | Sprint Communications Company L.P. | Selecting and applying a communication version |
Family Cites Families (67)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6067452A (en) | 1996-05-28 | 2000-05-23 | Comsat Corporation | Technique for least cost routing for mobile satellite systems employing a GSM network infrastructure |
US6058115A (en) * | 1997-08-04 | 2000-05-02 | Motorola, Inc. | Communication method and apparatus utilizing protocol options |
US6600738B1 (en) | 1999-10-02 | 2003-07-29 | Ericsson, Inc. | Routing in an IP network based on codec availability and subscriber preference |
WO2001031861A1 (en) | 1999-10-22 | 2001-05-03 | Nomadix, Inc. | Systems and methods for dynamic bandwidth management on a per subscriber basis in a communications network |
US6563919B1 (en) | 1999-12-17 | 2003-05-13 | Nortel Networks Limited | System and method for unifying the implementation and processing of mobile communications and a unified mobility manager for providing such communications |
US6785726B1 (en) | 2000-05-08 | 2004-08-31 | Citrix Systems, Inc. | Method and apparatus for delivering local and remote server events in a similar fashion |
EP1310129B1 (en) | 2000-08-10 | 2005-10-19 | Nokia Corporation | Roaming support method and system in UMTS |
US7979571B2 (en) | 2002-01-15 | 2011-07-12 | Hughes Network Systems, Llc | Method and system for providing load sensitive throttling |
WO2003075537A1 (en) * | 2002-03-05 | 2003-09-12 | Fujitsu Limited | Communication apparatus |
US6788676B2 (en) | 2002-10-30 | 2004-09-07 | Nokia Corporation | User equipment device enabled for SIP signalling to provide multimedia services with QoS |
US20040187021A1 (en) | 2003-02-10 | 2004-09-23 | Rasanen Juha A. | Mobile network having IP multimedia subsystem (IMS) entities and solutions for providing simplification of operations and compatibility between different IMS entities |
US8321584B2 (en) | 2003-04-04 | 2012-11-27 | Ellacoya Networks, Inc. | Method and apparatus for offering preferred transport within a broadband subscriber network |
US20050007967A1 (en) * | 2003-07-09 | 2005-01-13 | Keskar Dhananjay V. | Co-operative protocol for wireless device interaction with intelligent environments |
US7142537B2 (en) * | 2003-12-18 | 2006-11-28 | Motorola, Inc. | Interface call signaling protocol |
US7840217B2 (en) | 2004-07-23 | 2010-11-23 | Cisco Technology, Inc. | Methods and apparatus for achieving route optimization and location privacy in an IPV6 network |
US7076237B2 (en) | 2004-08-05 | 2006-07-11 | International Business Machines Corporation | Traffic shaping of cellular service consumption through delaying of service completion according to geographical-based pricing advantages |
US7702346B2 (en) | 2004-09-09 | 2010-04-20 | Nextel Communications Inc. | System and method for facilitating roaming of push to talk subscribers across disparate dispatch networks |
US7551926B2 (en) | 2004-10-08 | 2009-06-23 | Telefonaktiebolaget Lm Ericsson (Publ) | Terminal-assisted selection of intermediary network for a roaming mobile terminal |
US7292592B2 (en) | 2004-10-08 | 2007-11-06 | Telefonaktiebolaget Lm Ericsson (Publ) | Home network-assisted selection of intermediary network for a roaming mobile terminal |
US8196199B2 (en) | 2004-10-19 | 2012-06-05 | Airdefense, Inc. | Personal wireless monitoring agent |
US20080263632A1 (en) | 2004-10-20 | 2008-10-23 | Neil Keon | System and Method for Managing Use and Access of a Communication Network |
US8238326B2 (en) | 2004-11-18 | 2012-08-07 | Ruckus Wireless, Inc. | Maintaining consistent network connections while moving through wireless networks |
US20060117020A1 (en) | 2004-12-01 | 2006-06-01 | John Toebes | Arrangement for selecting a server to provide distributed services from among multiple servers based on a location of a client device |
FI20041652A0 (en) | 2004-12-22 | 2004-12-22 | Nokia Corp | Default subscriber profile of the visited terminal in a packet data based mobile network |
US8867575B2 (en) | 2005-04-29 | 2014-10-21 | Jasper Technologies, Inc. | Method for enabling a wireless device for geographically preferential services |
US9226151B2 (en) | 2006-04-04 | 2015-12-29 | Jasper Wireless, Inc. | System and method for enabling a wireless device with customer-specific services |
US7516478B2 (en) | 2005-06-03 | 2009-04-07 | Microsoft Corporation | Remote management of mobile devices |
US8626128B2 (en) | 2011-04-07 | 2014-01-07 | Microsoft Corporation | Enforcing device settings for mobile devices |
US8010997B2 (en) | 2005-06-30 | 2011-08-30 | Microsoft Corporation | Enforcing device settings for mobile devices |
US8832792B2 (en) | 2005-08-03 | 2014-09-09 | At&T Mobility Ii Llc | Limiting services based on location |
US20070060100A1 (en) | 2005-09-14 | 2007-03-15 | Telemac Corporation | Systems and methods for mobile station service control |
GB2431822A (en) | 2005-10-27 | 2007-05-02 | Agilent Technologies Inc | Determing an IP address of a node |
DE102005052262B4 (en) | 2005-11-02 | 2007-10-25 | Siemens Ag | A method of selecting an S-CSCF entity within an IMS based service communication system |
US20070115934A1 (en) | 2005-11-22 | 2007-05-24 | Samsung Electronics Co., Ltd. | Method and system for locating subscriber data in an IP multimedia subsystem |
CN101005488A (en) * | 2006-01-18 | 2007-07-25 | 华为技术有限公司 | Method and system for consulting and determining use of IP protocol version |
US7673077B2 (en) * | 2006-03-09 | 2010-03-02 | Sun Microsystems, Inc. | Multi-protocol iSCSI device discovery for on demand device enumeration |
US20070254628A1 (en) | 2006-04-27 | 2007-11-01 | Research In Motion Limited | Method, apparatus and system for monitoring and controlling wireless resource usage |
EP2455881B1 (en) | 2006-05-18 | 2018-01-17 | BlackBerry Limited | Automatic security action invocation for mobile communications device |
TW200744396A (en) * | 2006-05-26 | 2007-12-01 | Hon Hai Prec Ind Co Ltd | Mobile node and roaming method therefor, home agent and packet processing method therefor, and network communication system |
GB0610635D0 (en) | 2006-05-30 | 2006-07-05 | Nokia Corp | Allocation of a call state control function to a subscriber |
US8195196B2 (en) | 2006-12-29 | 2012-06-05 | United States Cellular Corporation | Mobility based service in wireless environment |
JP5276012B2 (en) | 2007-01-10 | 2013-08-28 | マッシュ・エス・アー・エール・エル | Data service roaming between networks that do not fully support Mobile Internet Protocol (MIP) |
US8781491B2 (en) | 2007-03-02 | 2014-07-15 | Aegis Mobility, Inc. | Management of mobile device communication sessions to reduce user distraction |
US9294401B2 (en) | 2007-06-28 | 2016-03-22 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for data transfer in a peer-to-peer network |
US8265281B2 (en) * | 2007-07-09 | 2012-09-11 | Qualcomm Incorporated | IP service authorization in wireless communications networks |
US20100208671A1 (en) | 2007-07-27 | 2010-08-19 | Nec Corporation | Communication system, user equipment registration method, switching device and user equipment registration system |
US9043451B2 (en) | 2007-07-31 | 2015-05-26 | Tekelec, Inc. | Methods, systems, and computer readable media for managing the flow of signaling traffic entering a signaling system 7 (SS7) based network |
US20090047947A1 (en) | 2007-08-02 | 2009-02-19 | Qualcomm Incorporated | Dynamic gateway selection based on data service and roaming protocol |
GB2453315A (en) | 2007-08-15 | 2009-04-08 | Nec Corp | Connection Identifier in a telecommunications network |
AU2007359104B2 (en) | 2007-09-20 | 2013-07-11 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for roaming between communications networks |
US8064382B2 (en) | 2007-09-28 | 2011-11-22 | Wireless Technology Solutions Llc | Apparatus and method for scheduling in a wireless communication system |
US20090161575A1 (en) | 2007-12-19 | 2009-06-25 | Research In Motion Limited | Long Term Evolution User Equipment Multi-Packet Data Network Connectivity Control |
CN101483635B (en) * | 2008-01-10 | 2012-06-27 | 华为技术有限公司 | Method and apparatus for IP address selection |
RU2450485C2 (en) | 2008-01-17 | 2012-05-10 | Нокиа Корпорейшн | Control of bit speed of adaptive multispeed codec in wireless communications system |
WO2009155031A2 (en) | 2008-05-28 | 2009-12-23 | Camiant, Inc. | Fair use management method and system |
US8041346B2 (en) | 2008-05-29 | 2011-10-18 | Research In Motion Limited | Method and system for establishing a service relationship between a mobile communication device and a mobile data server for connecting to a wireless network |
US8355337B2 (en) | 2009-01-28 | 2013-01-15 | Headwater Partners I Llc | Network based service profile management with user preference, adaptive policy, network neutrality, and user privacy |
US8589541B2 (en) | 2009-01-28 | 2013-11-19 | Headwater Partners I Llc | Device-assisted services for protecting network capacity |
US8965338B2 (en) | 2008-06-09 | 2015-02-24 | Apple Inc | Network access control methods and apparatus |
US8358602B2 (en) | 2008-06-27 | 2013-01-22 | Cisco Technology, Inc. | Method and system for supporting packet data network communications |
US20100002700A1 (en) | 2008-07-02 | 2010-01-07 | Cellnet Innovations, Inc. | Methods and Systems for Network Packet Routing Using Embedded Geographic Routing Information |
US8763020B2 (en) | 2008-10-14 | 2014-06-24 | Cisco Technology, Inc. | Determining user attention level during video presentation by monitoring user inputs at user premises |
US8750863B2 (en) | 2009-02-13 | 2014-06-10 | T-Mobile Usa, Inc. | Selection of roaming gateway |
EP2399412B1 (en) | 2009-02-19 | 2015-09-16 | Telefonaktiebolaget L M Ericsson (publ) | Traffic control for roaming subscribers |
US8326302B2 (en) | 2009-03-11 | 2012-12-04 | Futurewei Technologies, Inc. | System and method for initial gateway selection |
US8321565B2 (en) | 2009-11-02 | 2012-11-27 | Verizon Patent And Licensing Inc. | Network usage throttling systems and methods |
US20120198046A1 (en) | 2010-04-29 | 2012-08-02 | Mehul Jayant Shah | Mobile device bandwidth throttling |
-
2010
- 2010-04-29 US US12/770,632 patent/US8538405B2/en active Active
-
2011
- 2011-04-29 EP EP11778079.1A patent/EP2564657B1/en active Active
- 2011-04-29 WO PCT/US2011/034694 patent/WO2011139926A2/en active Application Filing
-
2013
- 2013-09-16 US US14/028,317 patent/US9226131B2/en active Active
-
2015
- 2015-12-17 US US14/973,374 patent/US10251162B2/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2003084185A1 (en) * | 2002-03-27 | 2003-10-09 | British Telecommunications Public Limited Company | System for selecting a connectivity mechanism |
US20060028998A1 (en) * | 2004-08-06 | 2006-02-09 | Marcello Lioy | Wireless network supporting failover between network protocols |
KR20060022937A (en) * | 2004-09-08 | 2006-03-13 | 삼성전자주식회사 | Method and apparatus for ip address autoconfiguration in mobile ad-hoc networks |
US20090037595A1 (en) * | 2007-07-31 | 2009-02-05 | Sprint Communications Company L.P. | Selecting and applying a communication version |
Also Published As
Publication number | Publication date |
---|---|
WO2011139926A3 (en) | 2012-02-02 |
US20140233455A1 (en) | 2014-08-21 |
US8538405B2 (en) | 2013-09-17 |
US9226131B2 (en) | 2015-12-29 |
EP2564657B1 (en) | 2019-07-03 |
EP2564657A4 (en) | 2017-01-25 |
EP2564657A2 (en) | 2013-03-06 |
US20160105916A1 (en) | 2016-04-14 |
US20120196588A1 (en) | 2012-08-02 |
US10251162B2 (en) | 2019-04-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10251162B2 (en) | Communication protocol preferences | |
AU2021277736B2 (en) | Pdu type setting method, ue policy setting method, and related entity | |
US9769743B2 (en) | Method and apparatus for determining access point service capabilities | |
US7280832B2 (en) | Method and apparatus for automatically selecting a bearer for a wireless connection | |
JP7043631B2 (en) | Methods and devices for determining SSC mode | |
KR102419113B1 (en) | Service quality monitoring method and system, and device | |
WO2022171051A1 (en) | Communication method and device | |
CN105052179A (en) | Communication between machine-to-machine service layers and transport network | |
WO2021223637A1 (en) | Application migration method and device | |
EP2564555B1 (en) | Managing access gateways | |
KR20110031234A (en) | A method and apparatus for a subscriber database | |
US8036222B1 (en) | Method for obtaining a mobile internet protocol address | |
CN114338603A (en) | Discovery method, device, block chain system and medium for edge application server | |
US8856204B2 (en) | Managing service provider messaging | |
US9204483B1 (en) | Methods for obtaining a mobile internet protocol address | |
TW200836542A (en) | A method of providing a mobility service | |
EP3001729B1 (en) | Method and apparatus for selecting an ip type during roaming | |
WO2022222081A1 (en) | Communication method and apparatus, and device and storage medium | |
WO2021037136A1 (en) | Service indication method and device | |
US20120100841A1 (en) | Method, system and apparatus for configuring a mobile electronic device | |
WO2024001563A1 (en) | Message routing method and apparatus, and system | |
CN114557045A (en) | Communication method and related device | |
KR20090032474A (en) | In-bound roaming system in mobile communication and method using the same |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 11778079 Country of ref document: EP Kind code of ref document: A2 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2011778079 Country of ref document: EP |