WO2008118388A1 - Selection de mecanisme de mobilite ip pour terminaux multimodes a connectivite ip directe - Google Patents

Selection de mecanisme de mobilite ip pour terminaux multimodes a connectivite ip directe Download PDF

Info

Publication number
WO2008118388A1
WO2008118388A1 PCT/US2008/003805 US2008003805W WO2008118388A1 WO 2008118388 A1 WO2008118388 A1 WO 2008118388A1 US 2008003805 W US2008003805 W US 2008003805W WO 2008118388 A1 WO2008118388 A1 WO 2008118388A1
Authority
WO
WIPO (PCT)
Prior art keywords
mobility
network
mobility protocol
network device
protocol
Prior art date
Application number
PCT/US2008/003805
Other languages
English (en)
Inventor
Stefano Faccin
Original Assignee
Marvell World Trade Ltd.
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 Marvell World Trade Ltd. filed Critical Marvell World Trade Ltd.
Priority to EP08727101A priority Critical patent/EP2135419A1/fr
Priority to JP2009554593A priority patent/JP2010522483A/ja
Publication of WO2008118388A1 publication Critical patent/WO2008118388A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • 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
    • 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
    • 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

  • the present disclosure relates to communication systems, and more particularly to selecting protocols for managing connectivity and mobility of network devices relative to remote networks.
  • FIG. 1 an exemplary network system 10 illustrating 3 rd Generation Partnership Project (3GPPTM) access from a 3GPPTM network is shown.
  • 3GPPTM 3 rd Generation Partnership Project
  • the network system 10 includes a service request device (SRD) 12 (e.g., a mobile network device) that may communicate with one or more remote networks, such as a visited public land mobile network (VPLMN) and a home public land mobile network (HPLMN) of a 3GPPTM system 14.
  • SRD 12 establishes Internet protocol (IP) connectivity with a packet data network (PDN) gateway 16 of the HPLMN to receive services, such as operator IP services.
  • IP Internet protocol
  • PDN packet data network gateway 16 of the HPLMN to receive services, such as operator IP services.
  • the services may include real-time and non-real-time services, such as Web browsing, voice over Internet phone (VoIP), electronic mail (email), and real-time IP multimedia, as well as conversational and streaming services.
  • VoIP voice over Internet phone
  • email electronic mail
  • real-time IP multimedia as well as conversational and streaming services.
  • the VPLMN includes a radio access network (RAN) 18, a serving gateway 20, a mobility management entity (MME) 22, and a servicing general packet radio service support node (SGSN) 24.
  • the serving gateway 20 may be a system architecture evolution (SAE) gateway or a wireless access gateway (WAG).
  • SAE system architecture evolution
  • WAG wireless access gateway
  • the MME 22 is in communication with each of the RAN 18, the serving gateway 20, and the SGSN 24.
  • the MME 22 performs SRD tracking and security functions.
  • the serving gateway 20 is in communication with the RAN 18 the PDN gateway 16, and the SGSN 24.
  • the SGSN 24 may perform MME selection and/or serving gateway selection.
  • the HPLMN includes a home subscriber server (HSS) 26 that is in communication with a 3GPPTM authentication, authorization and accounting (AAA) server 28.
  • the HPLMN also includes the PDN gateway 16, which is in communication with a home policy and changing rules function (hPCRF) device 30 and a PDN.
  • the PDN provides operator IP services, which may include IP multimedia subsystem (IMS) services, packet switched service sequence (PSS) services, etc, identified as 32.
  • IMS IP multimedia subsystem
  • PSS packet switched service sequence
  • the HSS 26 may have authentication and subscription data required for a subscriber, such as a subscriber associated with the SRD 12, to access the PDN.
  • the HSS 26 may also store an IP address of the 3GPPTM AAA server 28 to which the SRD 12 is registered.
  • the HSS 26 may perform PDN gateway selection.
  • the hPCRF device 30 may be used to terminate reference points between network devices, such as reference points associated with the serving gateway 20 and the hPCRF 30.
  • the 3GPPTM AAA server 28 provides AAA information and subscriber profile information. This information may be obtained from the HSS 26. For example only, the 3GPPTM AAA server 28 may authenticate the subscriber with the HSS 26 after an invoked tunnel establishment request by the SRD 12.
  • the SRD 12 when accessing the PDN gateway 16 generates an access authentication signal, which is transmitted to the MME 22 via the RAN 18.
  • the MME 22 generates an AAA request signal that is transmitted to the HSS 26 and/or the 3GPPTM AAA server 28.
  • the HSS 26 and/or the 3GPPTM AAA server 28 authenticate the SRD 12 and select a PDN gateway.
  • IP connectivity may be established between the MME 22 and the PDN gateway 16. Following establishment of IP connectivity, an attachment procedure between the SRD 12 and the MME 22 is completed.
  • the SRD 12 may register with a home agent of the PDN gateway 16. The SRD 12 then receives services from the PDN via the PDN gateway 16.
  • the network system 50 includes a SRD 52 that is located in a non-3GPPTM network, such as a wireless local area network (WLAN).
  • the 3GPPTM access is identified as 54.
  • the SRD 52 may communicate with one or more remote networks, such as a VPLMN and a HPLMN.
  • the SRD 52 establishes IP connectivity with a PDN gateway 56 of the HPLMN to receive services, such as operator IP services.
  • the VPLMN includes a RAN 58, a serving gateway 60, a MME 62, and a SGSN 64.
  • the MME 62 is in communication with each of the RAN 58, the serving gateway 60, and the SGSN 64.
  • the MME 62 performs SRD tracking and security functions.
  • the serving gateway 60 is in communication with the non-3GPPTM network, the PDN gateway 56, the RAN 58 and the SGSN 64.
  • the SGSN 64 may perform MME selection and/or serving gateway selection.
  • the HPLMN includes a HSS 68 that is in communication with a 3GPPTM AAA server 70.
  • the HPLMN also includes the PDN gateway 56, which is in communication with a hPCRF device 72 and a PDN.
  • the PDN provides operator IP services identified as 74.
  • the HSS 68 may have authentication and subscription data required for a subscriber, such as a subscriber associated with the SRD 52, to access the PDN.
  • the HSS 68 may also store an IP address of the 3GPPTM AAA server 70 to which the SRD 52 is registered.
  • the HSS 68 may perform PDN gateway selection.
  • the hPCRF device 72 may be used to terminate reference points between network devices, such as reference points associated with the serving gateway 60 and the hPCRF 72.
  • the 3GPPTM AAA server 70 provides AAA information and subscriber profile information. This information may be obtained from the HSS 68. For example only, the 3GPPTM AAA server 70 may authenticate the subscriber with the HSS 68 after an invoked tunnel establishment request by the SRD 52.
  • the SRD 52 when accessing the PDN gateway 56 generates an access authentication signal, which is transmitted to the MME 62 via the non- 3GPPTM network and the serving gateway 60.
  • the MME 62 generates an AAA request signal that is transmitted to the HSS 68 and/or the 3GPPTM AAA server 70.
  • the HSS 68 and/or the 3GPPTM AAA server 70 authenticates the SRD 52 and selects a PDN gateway.
  • IP connectivity is established between the MME 62 and the PDN gateway 56. Following establishment of IP connectivity, an attachment procedure between the SRD 52 and the MME 62 is completed.
  • the SRD 52 may register with a home agent of the PDN gateway 56.
  • the SRD 52 then receives services from the packet data network via the PDN gateway 56.
  • the network system 100 includes a SRD 102 that is located in a non-3GPPTM network, such as a Worldwide Interoperability for Microwave Access (WiMAX) network.
  • the non-3GPPTM access is identified as 103.
  • the SRD 102 may communicate with one or more remote networks, such as a VPLMN and a HPLMN.
  • the SRD 102 establishes IP connectivity with a PDN gateway 104 of the HPLMN to receive services, such as operator IP services.
  • the VPLMN includes a RAN 106, a serving gateway 108, a MME 110, and a SGSN 112.
  • the MME 110 is in communication with each of the RAN 106, the serving gateway 108, and the SGSN 112.
  • the MME 110 performs SRD tracking and security functions.
  • the serving gateway 108 is in communication with the non-3GPPTM network, the PDN gateway 104, the RAN 106 and the SGSN 112.
  • the SGSN 112 may perform MME selection and/or serving gateway selection.
  • the VPLMN may also include a 3GPPTM AAA proxy server 116 that provides AAA information and subscriber profile information to the serving gateway 104 and/or the non-3GPPTM network.
  • the HPLMN includes a HSS 118 that is in communication with a 3GPPTM AAA server 120.
  • the HPLMN also includes the PDN gateway 104, which is in communication with a hPCRF device 122 and a PDN.
  • the PDN provides operator IP services identified as 124.
  • the HSS 118 may have authentication and subscription data required for a subscriber, such as a subscriber associated with the SRD 102, to access the PDN.
  • the HSS 118 may also store an IP address of the 3GPPTM AAA server 120 to which the SRD 102 is registered.
  • the HSS 118 may perform PDN gateway selection.
  • the hPCRF device 122 may be used to terminate reference points between network devices, such as reference points associated with the serving gateway 108 and the hPCRF 122.
  • the 3GPPTM AAA server 120 provides AAA information and subscriber profile information. This information may be obtained from the HSS 118. For example only, the 3GPPTM AAA server 120 may authenticate the subscriber with the HSS 118 after an invoked tunnel establishment request by the SRD 102.
  • the SRD 102 when accessing the PDN gateway 104 generates an access authentication signal that is transmitted to the non-3GPPTM network.
  • the non-3GPPTM network generates an AAA request signal, which is transmitted to the HSS 118 and/or the 3GPPTM AAA server 120 via the serving gateway 108 and the MME 110.
  • the HSS 118 and/or the 3GPPTM AAA server 120 authenticates the SRD 102 and may select a PDN gateway 104.
  • an attachment procedure between the SRD 102 and the non-3GPPTM network is completed.
  • the SRD 102 may register with a home agent of the PDN gateway 104.
  • the SRD 102 receives services from the PDN via the PDN gateway 104.
  • a network device includes a transmit module that transmits an access point name signal including protocol information that indicates a mobility protocol supported by the network device.
  • a receive module receives a packet data network (PDN) gateway address signal including an address of a PDN gateway that supports the mobility protocol.
  • a control module establishes a tunnel for communication with the PDN gateway based on the address of the PDN gateway.
  • PDN packet data network
  • the address is selected by a network.
  • the receive module further receives a mobility protocol selection signal that indicates a selected mobility protocol.
  • the control module determines whether access to a network is permitted based on reception of at least one of the PDN gateway address signal and the mobility protocol selection signal.
  • control module determines that Internet protocol connectivity is not permitted between the network device and the PDN gateway when at least one of the PDN gateway address signal and the mobility protocol selection signal is not received within a predetermined time period.
  • control module determines whether access to a network is permitted based on content of the PDN gateway address signal and the mobility protocol selection signal. In other features, the control module determines whether handoff to an access network is permitted for the network device based on the mobility protocol selection signal. In other features, the handoff includes a change in access networks by the network device using a selected handoff mobility protocol.
  • control module determines that Internet protocol mobility is not permitted when the selected mobility protocol indicated by the mobility protocol selection signal is different than the mobility protocol supported by the network device. In other features, the control module performs an attachment procedure corresponding to an access network based on the selected mobility protocol indicated by the mobility protocol selection signal. [0024] In other features, the control module operates in a non-mobility mode and establishes Internet protocol connectivity when the selected mobility protocol indicated by the mobility protocol selection signal is different than the mobility protocol supported by the network device.
  • the access point name signal includes a mobility management descriptor.
  • the mobility management descriptor includes at least one of a mobility protocol support identifier, a mobility protocol preference identifier, and a handoff mobility protocol identifier.
  • the mobility management descriptor includes dummy bits corresponding to at least one of a PDN identifier and a domain name identifier when the network device is not identifying a PDN.
  • the transmit module generates an access authentication signal that includes the access point name signal.
  • the received module receives an authentication response signal based on the initial access signal.
  • the transmit module generates an access authentication signal.
  • the receive module receives an authentication response signal based on the access authentication signal.
  • the transmit module generates a parameter signal that includes the access point name signal based on the authentication response signal.
  • the receive module receives the PDN gateway address signal and the mobility protocol selection signal based on the parameter signal.
  • a network system is provided that includes the network device and further includes the PDN gateway.
  • control module generates a binding update and transmits the binding update to the PDN gateway via the transmit module.
  • access point name signal includes a connectivity protocol.
  • control module communicates with a home network via a mobility management device to determine a selected mobility protocol. The control module performs an attachment procedure and communicates with the PDN gateway via a serving gateway based on the selected mobility protocol.
  • a network system is provided that includes the network device and further includes another network device that generates the PDN gateway address signal and the mobility protocol selection signal.
  • a network device includes a receive module that receives an access point name signal including protocol information that indicates a mobility protocol supported by a service request device.
  • the control module detects when mobility support is requested based on the protocol information, selectively generates a PDN gateway address signal including an address of a PDN gateway that supports the mobility protocol, and selectively generates a mobility protocol selection signal indicating a selected mobility protocol.
  • a transmit module selectively transmits the PDN gateway address signal and the mobility protocol selection signal to the service request device.
  • control module selects the PDN gateway. In other features, the control module selects the PDN gateway based on at least one of a roaming agreement, an access network, a user profile, and mobility protocol support of the service request device. [0033] In other features, the control module selects the selected mobility protocol. In other features, the control module selects the selected mobility protocol based on at least one of a roaming agreement, an access network, a user profile, and mobility protocol support of the service request device. [0034] In other features, the transmit module transmits the PDN gateway address signal and the mobility protocol selection signal from a home public land mobile network.
  • control module does not generate the PDN gateway address signal and the mobility protocol selection signal when at least one of a visited public land mobile network and a home public land mobile network does not permit communication via the mobility protocol supported by the service request device.
  • control module permits handoff to an access network for the service request device when mobility protocol supported by the service request device is supported by a serving gateway of a visited public land mobile network.
  • handoff includes a change in access networks by the network device using a handoff mobility protocol selected by the control module.
  • control module determines that Internet protocol mobility is not permitted when the selected mobility protocol is different than the mobility protocol supported by the network device. [0038] In other features, the control module permits establishment of Internet protocol connectivity with the service request device when the selected mobility protocol is different than the mobility protocol supported by the network device. In other features, the control module permits establishment of Internet protocol connectivity and a mobility protocol tunnel when the selected mobility protocol is the same as the mobility protocol supported by the network device.
  • the access point name signal includes a mobility management descriptor.
  • the mobility management descriptor includes at least one of a mobility protocol support identifier, a mobility protocol preference identifier, and a handoff mobility protocol identifier.
  • the mobility management descriptor includes dummy bits that correspond to at least one of a PDN identifier and a domain name identifier when the service request device does not identify a PDN.
  • the receive module receives an access authentication signal that includes the access point name signal, the transmit module transmits an authentication response signal based on the initial access signal.
  • the access point name signal includes a connectivity protocol.
  • control module performs an attachment procedure with the service request device corresponds to an access network based on the selected mobility protocol.
  • control module operates in a non-mobility mode and establishes Internet protocol connectivity when the selected mobility protocol is different than the mobility protocol supported by the service request device.
  • receive module receives a binding update from the service request device based on the PDN gateway address signal and the mobility protocol selection signal.
  • the transmit module transmits a binding acknowledgement based on the binding update to the service request device.
  • a home public land mobile network that includes the network device and the PDN gateway.
  • a visited public land mobile network that includes the network device and a serving gateway that is in communication with the PDN gateway.
  • a method of operating a network device includes transmitting an access point name signal including protocol information that indicates a mobility protocol supported by the network device.
  • a PDN gateway address signal is received that includes an address of a PDN gateway that supports the mobility protocol.
  • a tunnel for communication with the PDN gateway is established based on the address of the PDN gateway.
  • the address is selected by a network.
  • the method further includes receiving a mobility protocol selection signal that indicates a selected mobility protocol. Permitted access to a network is determined based on reception of at least one of the PDN gateway address signal and the mobility protocol selection signal.
  • the method further includes determining that Internet protocol connectivity is not permitted between the network device and the PDN gateway when at least one of the PDN gateway address signal and the mobility protocol selection signal is not received within a predetermined time period. In other features, the method further includes determining whether access to a network is permitted based on content of the PDN gateway address signal and the mobility protocol selection signal. In other features, the method further includes determining whether handoff to an access network is permitted for the network device based on the mobility protocol selection signal. In other features, the handoff includes a change in access networks by the network device using a selected handoff mobility protocol.
  • the method further includes determining that Internet protocol mobility is not permitted when the selected mobility protocol indicated by the mobility protocol selection signal is different than the mobility protocol supported by the network device. In other features, the method further includes performing an attachment procedure corresponding to an access network based on the selected mobility protocol indicated by the mobility protocol selection signal. [0047] In other features, the method further includes operating in a non-mobility mode and establishing Internet protocol connectivity when the selected mobility protocol indicated by the mobility protocol selection signal is different than the mobility protocol supported by the network device. [0048] In other features, the access point name signal includes a mobility management descriptor. The mobility management descriptor includes at least one of a mobility protocol support identifier, a mobility protocol preference identifier, and a handoff mobility protocol identifier. In other features, the mobility management descriptor includes dummy bits corresponding to at least one of a PDN identifier and a domain name identifier when the network device is not identifying a PDN.
  • the method further includes generating an access authentication signal that includes the access point name signal. An authentication response signal is received based on the initial access signal. [0050] In other features, the method further includes generating an access authentication signal. An authentication response signal is received based on the access authentication signal. A parameter signal that includes the access point name signal is generated based on the authentication response signal. The PDN gateway address signal and the mobility protocol selection signal received based on the parameter signal.
  • the method further includes generating a binding update and transmitting the binding update to the PDN gateway via the transmit means.
  • the access point name signal includes a connectivity protocol.
  • the method further includes communicating with a home network via a mobility management device to determine a selected mobility protocol. An attachment procedure is performed. Communication with the PDN gateway via a serving gateway is enabled based on the selected mobility protocol.
  • the method further includes generating the PDN gateway address signal and the mobility protocol selection signal via another network device.
  • a method of operating a network device includes receiving an access point name signal including protocol information that indicates a mobility protocol supported by a service request device.
  • the method further includes detecting when mobility support is requested based on the protocol information.
  • a PDN gateway address signal including an address of a PDN gateway that supports the mobility protocol is selectively generated.
  • a mobility protocol selection signal indicating a selected mobility protocol selectively generated. The PDN gateway address signal and the mobility protocol selection signal are selectively transmitted to the service request device.
  • the method further includes selecting the PDN gateway. In other features, the method further includes selecting the PDN gateway based on at least one of a roaming agreement, an access network, a user profile, and mobility protocol support of the service request device. [0055] In other features, the method further includes selecting the selected mobility protocol. In other features, the method further includes selecting the selected mobility protocol based on at least one of a roaming agreement, an access network, a user profile, and mobility protocol support of the service request device. [0056] In other features, the method further includes transmitting the
  • PDN gateway address signal and the mobility protocol selection signal from a home public land mobile network.
  • the method further includes refraining from generating the PDN gateway address signal and the mobility protocol selection signal when at least one of a visited public land mobile network and a home public land mobile network does not permit communication via the mobility protocol supported by the service request device.
  • the method further includes permitting handoff to an access network for the service request device when mobility protocol supported by the service request device is supported by a serving gateway of a visited public land mobile network.
  • the handoff includes a change in access networks by the network device using a handoff mobility protocol selected by the control means.
  • the method further includes determining that
  • Internet protocol mobility is not permitted when the selected mobility protocol is different than the mobility protocol supported by the network device.
  • the method further includes permitting establishment of Internet protocol connectivity with the service request device when the selected mobility protocol is different than the mobility protocol supported by the network device. [0061] In other features, the method further includes permitting establishment of Internet protocol connectivity and a mobility protocol tunnel when the selected mobility protocol is the same as the mobility protocol supported by the network device.
  • the access point name signal includes a mobility management descriptor.
  • the mobility management descriptor includes at least one of a mobility protocol support identifier, a mobility protocol preference identifier, and a handoff mobility protocol identifier.
  • the mobility management descriptor includes dummy bits corresponding to at least one of a PDN identifier and a domain name identifier when the service request device does not identify a PDN.
  • the method further includes receiving an access authentication signal that includes the access point name signal.
  • An authentication response signal is transmitted based on the initial access signal.
  • the access point name signal includes a connectivity protocol.
  • the method further includes performing an attachment procedure with the service request device that corresponds to an access network based on the selected mobility protocol.
  • the method further includes operating in a non-mobility mode and establishing Internet protocol connectivity when the selected mobility protocol is different than the mobility protocol supported by the service request device.
  • the method further includes receiving a binding update from the service request device based on the PDN gateway address signal and the mobility protocol selection signal. A binding acknowledgement is transmitted based on the binding update to the service request device.
  • a network device includes transmitting means for transmitting an access point name signal including protocol information that indicates a mobility protocol supported by the network device.
  • Receiving means receives a PDN gateway address signal that includes an address of a PDN gateway that supports the mobility protocol.
  • Control means establishes a tunnel for communication with the PDN gateway based on the address of the PDN gateway.
  • the address is selected by a network.
  • the receiving means further receives a mobility protocol selection signal that indicates a selected mobility protocol.
  • the control means determines whether access to a network is permitted based on reception of at least one of the PDN gateway address signal and the mobility protocol selection signal.
  • control means determines that Internet protocol connectivity is not permitted between the network device and the PDN gateway when at least one of the PDN gateway address signal and the mobility protocol selection signal is not received within a predetermined time period.
  • control means determines whether access to a network is permitted based on content of the PDN gateway address signal and the mobility protocol selection signal.
  • control means determines whether handoff to an access network is permitted for the network device based on the mobility protocol selection signal.
  • the handoff includes a change in access networks by the network device using a selected handoff mobility protocol.
  • control means determines that Internet protocol mobility is not permitted when the selected mobility protocol indicated by the mobility protocol selection signal is different than the mobility protocol supported by the network device. In other features, the control means performs an attachment procedure that corresponds to an access network based on the selected mobility protocol indicated by the mobility protocol selection signal. [0074] In other features, the control means operates in a non-mobility mode and establishes Internet protocol connectivity when the selected mobility protocol indicated by the mobility protocol selection signal is different than the mobility protocol supported by the network device.
  • the access point name signal includes a mobility management descriptor.
  • the mobility management descriptor includes at least one of a mobility protocol support identifier, a mobility protocol preference identifier, and a handoff mobility protocol identifier.
  • the mobility management descriptor includes dummy bits that correspond to at least one of a PDN identifier and a domain name identifier when the network device is not identifying a PDN.
  • the transmitting means generates an access authentication signal that includes the access point name signal.
  • the receiving means receives an authentication response signal based on the initial access signal.
  • the transmitting means generates an access authentication signal.
  • the receiving means receives an authentication response signal based on the access authentication signal.
  • the transmitting means generates a parameter signal that includes the access point name signal based on the authentication response signal.
  • the receiving means receives the PDN gateway address signal and the mobility protocol selection signal based on the parameter signal.
  • a network system includes the network device and further includes the PDN gateway.
  • the control means generates a binding update and transmits the binding update to the PDN gateway via the transmit means.
  • the access point name signal includes a connectivity protocol.
  • the control means communicates with a home network via a mobility management device to determine a selected mobility protocol. The control means performs an attachment procedure and communicates with the PDN gateway via a serving gateway based on the selected mobility protocol.
  • a network system includes the network device and further includes network means for generating the PDN gateway address signal and the mobility protocol selection signal.
  • a network device includes receiving means for receiving a access point name signal including protocol information that indicates a mobility protocol supported by a service request device.
  • Control means detects when mobility support is requested based on the protocol information.
  • a PDN gateway address signal including an address of a PDN gateway that supports the mobility protocol is selectively generated.
  • a mobility protocol selection signal indicating a selected mobility protocols selectively generated.
  • Transmitting means selectively transmits the PDN gateway address signal and the mobility protocol selection signal to the service request device.
  • control means selects the PDN gateway. In other features, the control means selects the PDN gateway based on at least one of a roaming agreement, an access network, a user profile, and mobility protocol support of the service request device.
  • control means selects the selected mobility protocol. In other features, the control means selects the selected mobility protocol based on at least one of a roaming agreement, an access network, a user profile, and mobility protocol support of the service request device. In other features, the transmit means transmits the PDN gateway address signal and the mobility protocol selection signal from a home public land mobile network.
  • control means does not generate the PDN gateway address signal and the mobility protocol selection signal when at least one of a visited public land mobile network and a home public land mobile network does not permit communication via the mobility protocol supported by the service request device.
  • control means permits handoff to an access network for the service request device when mobility protocol supported by the service request device is supported by a serving gateway of a visited public land mobile network.
  • the handoff includes a change in access networks by the network device using a handoff mobility protocol selected by the control means.
  • control means determines that Internet protocol mobility is not permitted when the selected mobility protocol is different than the mobility protocol supported by the network device.
  • control means permits establishment of
  • control means permits establishment of Internet protocol connectivity and a mobility protocol tunnel when the selected mobility protocol is the same as the mobility protocol supported by the network device.
  • the access point name signal includes a mobility management descriptor.
  • the mobility management descriptor includes at least one of a mobility protocol support identifier, a mobility protocol preference identifier, and a handoff mobility protocol identifier.
  • the mobility management descriptor includes dummy bits corresponding to at least one of a PDN identifier and a domain name identifier when the service request device does not identify a PDN.
  • the receiving means receives an access authentication signal that includes the access point name signal.
  • the transmit means transmits an authentication response signal based on the initial access signal.
  • the access point name signal includes a connectivity protocol.
  • the control means performs an attachment procedure with the service request device that corresponds to an access network based on the selected mobility protocol.
  • the control means operates in a non-mobility mode and establishes Internet protocol connectivity when the selected mobility protocol is different than the mobility protocol supported by the service request device.
  • the receiving means receives a binding update from the service request device based on the PDN gateway address signal and the mobility protocol selection signal.
  • the transmit means transmits a binding acknowledgement based on the binding update to the service request device.
  • a home public land mobile network that includes the network device and the PDN gateway.
  • a visited public land mobile network that includes the network device and a serving gateway that is in communication with the PDN gateway.
  • the systems and methods described above may be implemented by a computer program executed by one or more processors.
  • the computer program can reside on a computer readable medium such as but not limited to memory, non-volatile data storage and/or other suitable tangible storage mediums.
  • FIG. 1 is a functional block diagram of an exemplary network system illustrating roaming 3GPPTM access via a radio access network according to the prior art
  • FIG. 2 is a functional block diagram of an exemplary network system illustrating roaming 3GPPTM access via a non-3GPPTM network according to the prior art
  • FIG. 3 is a functional block diagram of an exemplary network system illustrating trusted roaming non-3GPPTM access via a non-3GPPTM network according to the prior art
  • FIG. 4 is a functional block diagram of an exemplary network system in accordance with an embodiment of the present disclosure.
  • FIG. 5 is a functional block diagram of an exemplary network system illustrating roaming access via a radio access network in accordance with an embodiment of the present disclosure
  • FIG. 6 is a functional block diagram of an exemplary network system illustrating roaming access via a non-3GPP network in accordance with an embodiment of the present disclosure
  • FIG. 7 is a functional block diagram of another exemplary network system in accordance with an embodiment of the present disclosure.
  • FIG. 8 is a logic flow diagram illustrating a method of providing mobility management in accordance with an embodiment of the present disclosure
  • FIG. 9 is a message flow diagram illustrating the mobility management of the method of FIG. 8;
  • FIG. 10A is a block diagram of an access point name when a service request device identifies a packet data network in accordance with an embodiment of the present disclosure
  • FIG. 10B is a block diagram of an access point name when a service request device does not identify a packet data network in accordance with an embodiment of the present disclosure
  • FIG. 11 is a functional block diagram of an exemplary network system illustrating roaming access via a trusted non-3GPP network in accordance with an embodiment of the present disclosure
  • FIG. 12 is a functional block diagram of another exemplary network system in accordance with an embodiment of the present disclosure.
  • FIG 13 is a logic flow diagram illustrating a method of providing mobility management in accordance with an embodiment of the present disclosure;
  • FIG 14 is a message flow diagram illustrating the mobility management of the method of FIG. 13;
  • FIG 15 is a logic flow diagram illustrating a method of providing mobility management in accordance with another embodiment of the present disclosure.
  • FIG. 16 is a message flow diagram illustrating the mobility management of the method of FIG. 15;
  • FIG. 17 is a functional block diagram of an exemplary network system illustrating non-roaming access in accordance with an embodiment of the present disclosure
  • FIG. 18 is a functional block diagram of an exemplary network system illustrating non-roaming access in accordance with another embodiment of the present disclosure
  • FIG. 19 is a logic flow diagram illustrating a method of providing mobility management in accordance with another embodiment of the present disclosure.
  • FIG. 20 is a message flow diagram illustrating the mobility management of the method of FIG. 19;
  • FIG. 21 is a logic flow diagram illustrating a method of providing mobility management in accordance with another embodiment of the present disclosure.
  • FIG. 22 is a message flow diagram illustrating the mobility management of the method of FIG. 21 ;
  • FIG. 23A is a functional block diagram of a high definition television in accordance with an embodiment of the present disclosure.
  • FIG. 23B is a functional block diagram of a vehicle in accordance with an embodiment of the present disclosure.
  • FIG. 23C is a functional block diagram of a cellular phone in accordance with an embodiment of the present disclosure.
  • FIG. 23D is a functional block diagram of a set top box in accordance with an embodiment of the present disclosure; and [0123]
  • FIG. 23E is a functional block diagram of a mobile device in accordance with an embodiment of the present disclosure.
  • One or more steps within a method may be executed in different order without altering the principles of the present disclosure.
  • module refers to an Application
  • ASIC Specific Integrated Circuit
  • ASIC an electronic circuit
  • processor shared, dedicated, or group
  • memory that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that provide the described functionality.
  • a service request device may refer to user equipment (UE) and/or a mobile node.
  • UE user equipment
  • a SRD may include equipment of an end user, such as a processor, a radio interface adaptor, etc.
  • An SRD may include a mobile network device, a personal data assistant (PDA), a computer, etc.
  • PDA personal data assistant
  • the term mobility protocol may include a local mobility protocol and/or a global mobility protocol.
  • a local mobility protocol may refer to a communication protocol used for mobility by a SRD between access points of a network, e.g., a public land mobile network (PLMN). The access points are in communication with different access routers.
  • a global mobility protocol refers to a communication protocol used for mobility by a SRD between access points of different networks. The different networks may be different PLMNs.
  • a mobility protocol may include a mobile Internet protocol (MIP), which may refer to a host-based Internet protocol (IP) or a network-based MIP protocol (MIP), which may refer to a host-based Internet protocol (IP) or a network-based MIP protocol (MIP), which may refer to a host-based Internet protocol (IP) or a network-based MIP protocol (MIP), which may refer to a host-based Internet protocol (IP) or a network-based
  • a host-based IP may include a client mobile IP (CMIP), such as CMIPv4-and CMIPv ⁇ , or a dual stack mobile IP (DSMIP).
  • CMIP client mobile IP
  • DSMIP dual stack mobile IP
  • a host-based IP is used when mobility management is handled by a SRD.
  • a network-based IP may include a proxy MIP (PMIP), such as PMIPv4 and PMIPv6.
  • PMIP proxy MIP
  • a network-based IP may be used, for example, when mobility management is handled by a mobility management entity (MME) or other network device on behalf of a SRD.
  • MME mobility management entity
  • each network device is disclosed. Although a particular number of each network device is shown, any number of each network device may be included. For example, in a home network and or a visited network any number of wireless access gateways (WAGs), home subscriber servers (HSSs), authentication authorization and accounting (AAA) servers, etc. may be included. Selection of one of each of the devices may be performed during communication with a SRD.
  • WAGs wireless access gateways
  • HSSs home subscriber servers
  • AAA authentication authorization and accounting
  • the network system 150 includes a SRD 152 that may communicate with the Internet 154 and/or one or more remote networks 156.
  • the SRD 152 may communicate with a radio access network (RAN) 158 of the remote networks 156 as indicated by signal line 160 or may communicate with the remote networks 156 via an access network.
  • RAN radio access network
  • Some examples of an access network are a wireless local area network (WLAN) 162, a Worldwide Interoperability for Microwave Access (WiMAX) network 164, and a cellular network 166.
  • the network system 150 provides mobility management that allows the SRD 152 to move between local and/or global networks. The mobility is provided through establishment of Internet protocol (IP) connectivity between the SRD 152 and the remote networks 156 using mobility management as described herein.
  • IP Internet protocol
  • the SRD 152 includes a service request mobility control module 170 that provides mobility protocol information to the remote networks 156.
  • the service request mobility control module 170 may also identify a packet data network (PDN) gateway, such as one of the PDN gateways 170, of the remote networks 156 to provide requested services.
  • the mobility protocol information may include the mobility protocol(s) supported by the SRD 152.
  • the SRD 152 accesses packet switched domain services via the selected PDN gateway.
  • the PDN gateway may be located in a home PLMN (HPLMN).
  • the SRD 152 may request various real-time and non-real-time services, such as Web browsing, voice over Internet phone (VoIP), electronic mail (email), and real-time IP multimedia, as well as conversational and streaming services.
  • VoIP voice over Internet phone
  • email electronic mail
  • real-time IP multimedia as well as conversational and streaming services.
  • the remote networks 156 may include 3 rd Generation Partnership Project (3GPPTM) system networks, a VPLMN, a HPLMN, etc.
  • the remote networks 156 may comply with Technical Specification (TS) 23.402 "3GPPTM Architecture enhancements for non-3GPP accesses", Technical Specification (TS) 23.234 "3GPPTM system to Wireless Local Area Network (WLAN) interworking", TS 33.234 "Wireless Local Area Network (WLAN) interworking security", which are incorporated herein by reference in their entirety.
  • the remote networks 156 may include the RAN 158, the PDN gateways 170, a MME 172, serving gateways 174, and remote servers 176, such as home subscriber servers (HSSs).
  • the MME 172 may include a MME mobility control module 180 that supports mobility of the SRD 102.
  • the serving gateways 174 may include system architecture evolution (SAE) gateways.
  • the remote servers 1176 may include PDN records 182, DNS records 184, and SRD records 186.
  • the PDN records 182 include information regarding the services, connectivity protocols, and mobility protocols supported by the PDN gateways 170.
  • the DNS records 184 include information regarding the services and connectivity protocols supported by packet data gateways (PDGs).
  • the DNS records 184 may also include mobility protocols supported by the PDGs.
  • the SRD records 186 include information regarding the subscriber and account associated with the SRD 152.
  • Each of the PDN gateways 170 may have a physical address (effective address) and/or one or more logical addresses, which are referred to as remote IP addresses.
  • Each remote IP address may have an associated service and connectivity and mobility protocol and be assigned to the SRD 152.
  • a remote IP address may be associated with home-based IP CMIPv6 and be used to provide VoIP service to the SRD 152.
  • the SRD 152 initially accesses the network system 150, the MME 172, the PDN gateways 170, and the serving gateways 174 are unaware of the mobility protocols supported by the SRD 152.
  • the MME 172, the PDN gateways 170, and the serving gateways 174 may support multiple mobility protocols that may not be the same as the mobility protocols supported by the SRD 152. Thus, a mobility protocol mismatch could occur between a SRD 152 and the devices of the network system 150.
  • a SRD 152 may support CMIP
  • one or more of the MME 172, the PDN gateways 170, and the serving gateways 174 may support PMIP. Since PMIP operation begins before a secure tunnel is setup, the SRD 152 is unable to inform the network system 150 that the SRD 152 is CMIP compatible and not PMIP compatible.
  • a serving gateway such as one of the serving gateways 170, may support multiple protocols. In supporting multiple protocols, the serving gateway may not be able to determine whether to function as a foreign agent, an access router, or a proxy mobile agent (PMA).
  • PMA proxy mobile agent
  • one or more embodiments disclosed herein assure that a mobility protocol mismatch does not occur and that a selected PDN gateway, a MME, and/or a serving gateway support the correct mobility protocol(s).
  • the WLAN 162 includes a WLAN access point (AP) 190 with an AP mobility control module 192.
  • the WLAN AP 190 may be a base station.
  • the WLAN 190 may also include one or more home agents 194, such as routers.
  • the AP mobility control module 192 facilitates authentication of the SRD 152 and the transfer of connectivity and mobility protocol information, and PDN gateway information between the SRD 152 and network devices of the remote networks.
  • the WLAN 162 may comply with one or more IEEE standards - e.g., 802.11 , 802.11a, 802.11b, 802.11g, 802.11h, 802.11n, 802.16, and 802.20, which are incorporated herein by reference in their entirety.
  • the cellular network 166 and the WiMAX network 164 may include a cellular network AP 196 and a WiMAX network AP 198 with respective AP mobility control modules 200, 202, as shown.
  • the AP mobility control modules 196, 198 may also facilitate authentication of the SRD 152 and the transfer of connectivity and mobility protocol information, and PDN gateway information between the SRD 152 and network devices of the remote networks 156.
  • the SRD 152 may move or roam between the networks 162, 164, 166 without losing connection to one or more of the remote networks 156.
  • IP traffic flows between the RAN 158 and the serving gateways 174.
  • the WiMAX network 164 or the cellular network 166 (in one embodiment) IP traffic flows between the networks 162, 164, 166 and the serving gateways 174.
  • the SRD 152 accesses the remote networks 156 while roaming between the networks 162, 164, 166, connectivity and mobility tunnels, may be used to manage and maintain connectivity and mobility of the SRD 152.
  • a host-based system or a network-based system may be used to establish a connectivity tunnel and/or a mobility tunnel.
  • the connectivity tunnel may be a secured IP tunnel.
  • the host-based system may utilize CMIP or DSMIP protocols.
  • CMIP versions 4 and 6 are described in IP mobility request for support memos RFC 3344 and in RFC 3775, which are incorporated herein by reference in their entirety.
  • DSMIPv ⁇ is described in "Mobile IPv6 support for dual stack, Hosts, and Routers (DSMIPv ⁇ )" of an Internet draft by IPv6 working group of IETF, which is incorporated herein by reference in its entirety.
  • the network-based system may utilize PMIP protocols.
  • PMIP version 4 is described in an Internet- Draft titled "Mobility Management using Proxy Mobile IPv4" by Leung et al. and
  • IPv6 by Gundavelli, which are incorporated herein by reference in their entirety.
  • a serving gateway may function as a foreign agent (FA) and provide routing services to the SRD 152. This may occur when the SRD 152 is registered with the PDN gateway.
  • the PDN gateway performs as a home agent.
  • the SRD 152 may receive IP configuration information contained in an agent advertisement message through CMIPv4 or link layer protocols.
  • a serving gateway may function as an access router and provide routing services to the SRD 152.
  • the PDN gateway performs as a home agent.
  • the SRD 152 may receive IP configuration information contained in a CMIPv ⁇ router advertisement message through CMIPv ⁇ or link layer protocols.
  • a serving gateway may function as a PMIP client (i.e., a PMIP agent (PMA)).
  • PMA PMIP agent
  • the PDN gateway performs as a PMIP home agent.
  • a PMIP client allocates a SRD IP address and provides the SRD IP address to the SRD 152.
  • the PMIP client performs PMIP mobility procedures.
  • the network system 220 includes a SRD 224 that may communicate with one or more remote networks, such as a VPLMN and a HPLMN of a 3GPPTM system.
  • the SRD 224 includes a SRD mobility control module 226 and establishes IP connectivity with a PDN gateway 228 of the HPLMN to receive services, such as operator IP services.
  • the SRD 224 also establishes mobility protocol connectivity with the network system.
  • the SRD 224 obtains access to the network system 220 via the RAN 222.
  • the VPLMN includes the RAN 222, a serving gateway 229, a MME 230, and a SGSN 232.
  • the RAN 222, the serving gateway 229, and the MME 230 respectively include a RAN mobility control module 233, a serving gateway mobility control module 234, and a MME mobility control module 236.
  • the RAN 222, the serving gateway 229, and the MME 230 transfer mobility protocol information and PDN gateway selection information between the SRD 224 and the HPLMN.
  • the serving gateway 229 may be a SAE gateway or a WAG.
  • the MME 230 is in communication with each of the RAN 233, the SGSN 232, and the serving gateway 229.
  • the MME 230 performs SRD tracking and security functions.
  • the serving gateway 229 is in communication with the PDN gateway 228, the RAN 222 and the SGSN 232.
  • the SGSN 232 may perform MME selection and/or serving gateway selection.
  • the HPLMN includes a home subscriber server (HSS) 240 that is in communication with an authentication, authorization and accounting (AAA) server 242.
  • the HSS 240 and the AAA server 242 have respectively a HSS mobility control module 244 and an AAA server mobility control module 246.
  • the HPLMN including the HSS 240 and/or the AAA server 242 may select a mobility protocol and a PDN gateway in association with network access by the SRD 224.
  • the HPLMN including the HSS 240 and/or the AAA server 242 may provide the selected mobility protocol and selected PDN gateway information to the SRD 224.
  • the HPLMN also includes the PDN gateway, which is in communication with a home policy and changing rules function (hPCRF) device 247 and a PDN 248.
  • the PDN 248 provides operator IP services, which may include IP multimedia subsystem (IMS) services, packet switched service sequence (PSS) services, etc, identified as 250.
  • IMS IP multimedia subsystem
  • PSS packet switched service sequence
  • the HSS 240 may have authentication and subscription data required for a subscriber, such as a subscriber associated with the SRD 224, to access the PDN 248.
  • the subscriber information may be stored in SRD records.
  • the HSS 240 may also store an IP address of the AAA server 242 to which the SRD 224 is registered.
  • the HSS 240 may perform PDN gateway selection.
  • the hPCRF device 247 may be used to terminate reference points between network devices, such as reference points associated with the serving gateway 229, a visited PCRF (vPCRF) (not shown), and the hPCRF 247.
  • the AAA server 242 provides AAA information and subscriber profile information. This information may be obtained from the HSS 240. For example only, the AAA server 242 may authenticate the subscriber with the HSS 240 after an invoked tunnel establishment and/or attachment request by the SRD 224.
  • the network system 270 includes a SRD 272 that may communicate with one or more remote networks, such as a VPLMN and a HPLMN of a 3GPPTM system.
  • the SRD 272 includes a SRD mobility control module 274 and establishes IP connectivity with a PDN gateway 276 of the HPLMN to receive services, such as operator IP services.
  • the SRD 272 also establishes mobility protocol connectivity with the network system 270.
  • the SRD 272 obtains access, such as 3GPP IP access identified as 277, to the network system 270 via an access network 278.
  • the access network 278 may be a non-3GPPTM network, such as a WLAN, a WIMAX network, a cellular network, etc.
  • the access network 278 may include an access network mobility control module 279.
  • the access network 278 is in communication with a serving gateway 280 of the VPLMN.
  • the VPLMN includes the serving gateway 280, a RAN 282, a MME 284, and a SGSN 286.
  • the serving gateway 280, the RAN 282, and the MME 284 respectively include a serving gateway mobility control module 290, a RAN mobility control module 292, and a MME mobility control module 294.
  • the serving gateway 280, the RAN 282, and the MME 284 transfer mobility protocol information and PDN gateway selection information between the SRD 272 and the HPLMN.
  • the MME 284 is in communication with each of the serving gateway 280, the RAN 282, and the SGSN 286.
  • the MME 284 performs SRD tracking and security functions.
  • the serving gateway 280 is in communication with the PDN gateway 276, the access network 278, the RAN 282 and the SGSN 286.
  • the SGSN 286 may perform MME selection and/or serving gateway selection.
  • the HPLMN includes a HSS 300 that is in communication with an AAA server 302.
  • the HSS 200 and the AAA server 302 have respectively a HSS mobility control module 304 and an AAA server mobility control module 306.
  • the HPLMN including the HSS 300 and/or the AAA server 302 may select a mobility protocol and a PDN gateway 276 in association with network access by the SRD 272.
  • the HPLMN including the HSS 300 and/or the AAA server 302 may provide the selected mobility protocol and selected PDN gateway information to the SRD 272.
  • the HPLMN also includes the PDN gateway 276, which is in communication with a hPCRF device 308 and a PDN 310.
  • the PDN 310 provides IP services 312.
  • the HSS 300 may have authentication and subscription data required for a subscriber, such as a subscriber associated with the SRD 272, to access the PDN 310.
  • the subscriber information may be stored in SRD records.
  • the HSS 300 may also store an IP address of the AAA server 302 to which the SRD 272 is registered.
  • the HSS 300 may perform PDN gateway selection.
  • the hPCRF device 308 may be used to terminate reference points between network devices, such as reference points associated with the serving gateway 280, a vPCRF, and the hPCRF 308.
  • the AAA server 302 provides AAA information and subscriber profile information. This information may be obtained from the HSS 300. For example only, (in one embodiment) the AAA server 302 may authenticate the subscriber with the HSS 300 after an invoked tunnel establishment and/or attachment request by the SRD 272.
  • the network system 320 includes a SRD 322, an AP 324, a MME 326, and HPLMN server(s) 328.
  • the AP 324 may include a RAN, a WLAN, a WiMAX network, a cellular network, etc.
  • the HPLMN server(s) may include a HSS, an AAA server, a remote server, etc.
  • the SRD 322 may provide the AP 324 with service request information, IP connectivity protocol information, mobility protocol information, and/or PDN gateway information.
  • the SRD 322 may communicate with the HPLMN server(s) 328 via the AP 324 and/or a serving gateway 330 to setup connectivity and mobility tunnel(s), for communication between the SRD 322 and the a PDN gateway.
  • a serving gateway An example of a serving gateway is shown in FIG. 12.
  • the tunnel(s) may include a connectivity tunnel and/or a mobility tunnel.
  • the SRD 322 may include an antenna 340, an SR analog front- end module 342, a SR transmit module 344, a SR receive module 346, and a SR control module 348.
  • the SR analog front-end module 342 may transmit signals generated by the SR transmit module 344 via the antenna 340 and may output signals received from the antenna 340 to the SR receive module 346.
  • the SRD 322 may also include an access point name generator 350 for the generation of APNs, as described herein.
  • the AP 324 may include an antenna 360, an AP analog front- end module 362, an AP transmit module 364, an AP receive module 366, and an AP control module 367.
  • the AP analog front-end module 362 may transmit signals generated by the AP transmit module 364 via the antenna 360 and may output signals received from the antenna 360 to the AP receive module 366.
  • the MME 326 may include an antenna 370, a MME analog front-end module 372, a MME transmit module 374, a MME receive module 376, and a MME control module 378.
  • the MME analog front-end module 376 may transmit signals generated by the MME transmit module 374 via the antenna 370 and may output signals received from the antenna 370 to the MME receive module 376.
  • the HPLMN server(s) 328 may include an antenna 380, a HPLMN server(s) analog front-end module 382, a HPLMN server(s) transmit module 384, a HPLMN server(s) receive module 386, and a HPLMN server(s) control module 388.
  • the HPLMN server(s) analog front-end module 386 may transmit signals generated by the HPLMN server(s) transmit module 384 via the antenna 380 and may output signals received from the antenna 380 to the HPLMN server(s) receive module 386.
  • the HPLMN server(s) 328 may include PDN records 390 and SRD records 392. [0161] The SRD 322 initiates an information exchange between the
  • the SR control module 348 may generate an access point name (APN).
  • the APN may identify a packet data network (PDN).
  • the APN may be generated by the APN generator 350.
  • the SRD 322 performs an attachment request and receives a selected mobility protocol and a selected PDN gateway through which requested services may be provided.
  • the SRD 322 may select one or more mobility protocols (e.g., CMIP and/or PMIP) that the SRD 322 supports and/or prefers to use for connectivity and mobility.
  • the SRD 322 may select CMIP or PMIP for both connectivity and mobility (i.e., for network handover).
  • the SRD 322 may select a different mobility protocol for connectivity than for mobility.
  • the SRD 322 may select PMIP for connectivity and CMIP for mobility.
  • An SRD when attaching to a network system may use a default
  • IP access service to enable IP connectivity.
  • the SRD does not need to perform any explicit activation procedure to transfer data. For example and with respect to a general packet radio service (GPRS), a packet data protocol context activation procedure is performed along with a GPRS attachment procedure.
  • GPRS general packet radio service
  • the SRD may instead of or in addition to using a default IP access service may provide and receive mobility protocol and PDN gateway information.
  • the mobility mode refers to the ability of a SRD to roam between local and/or global networks.
  • the mobility mode is setup based on SRD and network system mobility capabilities, mobility preferences, and SRD profiles.
  • the mobility mode may refer to selected mobility protocols for IP connectivity and handoff, as well as a selected PDN gateway.
  • the decision to operate in a mobility mode may be made by a home network, such as a HPLMN, and may change based on updated SRD parameters and/or network system parameters.
  • the identification, selection and informing of a mobility protocol for handoff allows a SRD and a network system to determine and/or to predict whether the SRD is to perform a handoff to another access network. This allows a host-based mobility protocol client to be engaged in a protocol stack early on in a connectivity setup. When connectivity is setup, a host-based mobility protocol may be active or inactive on a user plane depending on whether the SRD is considered "at home" in terms of IP mobility.
  • a SRD may perform as a virtual interface to support inter- technology handovers between access networks when a network-based mobility protocol is selected. This accounts for when the same IP address is temporarily assigned to two physical interfaces, referred to as port bonding in LinuxTM. This functionality of the SRD is activated early on in the setup of IP connectivity.
  • some embodiments described herein include identification of mobility protocols that are supported by a SRD, selection of mobility protocols and PDN gateways, and informing of a SRD of the selected mobility protocols and selected PDN gateways.
  • the identification, selection, and informing may be performed using transport-level protocols.
  • FIGs. 8, 9, 13-16 and 19-22 illustrate exemplary methods, which include the stated identification, selection, and informing. Such methods prevent mobility protocol conflicts and enable handoff.
  • the methods and SRD attachments described in FIGs. 8, 9, 13-16 and 19-22 may occur when a SRD initially accesses a network and/or during a handoff between networks.
  • An SRD may provide a preferred mobility protocol and discover the mobility protocol supported by a network using extended layer 3 messages for acquiring an IP address.
  • An access network may reply to the layer 3 message with requested information including the mobility protocol supported and accepted by the access network. This may also be provided using layer 3 messages for acquiring an IP address.
  • Stateful firewalls maintain context about active sessions, and use that "state information" to speed up packet processing.
  • An existing network connection may be described by several properties, including source and destination IP address, user datagram protocol (UDP) or transmission control protocol (TCP) ports, and the current stage of the connection's lifetime (including session initiation, handshaking, data transfer, or completion connection).
  • UDP user datagram protocol
  • TCP transmission control protocol
  • the packet is evaluated according to a ruleset for new connections.
  • the packet matches an existing connection based on comparison with a firewall's state table, the packet is allowed to pass without further processing.
  • a stateless packet filter can distinguish between and control certain types of traffic, such as web browsing, remote printing, email transmission, and file transfer, unless the machines on each side of the packet filter are both using the same non-standard ports.
  • network-based mobility protocols may be used as a default. The network-based mobility protocols may be used, for example, when accesses that do not provide full local IP connectivity at the access network, such as for certain trusted non-3GPP accesses. For trusted non-3GPP accesses that support full IP connectivity at the local access network, the establishment of connectivity to a PDN gateway using a network-based mobility protocol may not be the default.
  • FIGs. 8 and 9 a logic flow diagram illustrating a method of providing mobility management and a message flow diagram illustrating the mobility management are shown.
  • the method may apply to 3GPP IP access by a SRD.
  • the method may begin at step 300.
  • the SRD when accessing a PDN gateway generates an access authentication signal, which is transmitted to a MME via an access point and/or a serving gateway.
  • the access authentication signal is generated and transmitted to initiate an attachment procedure and an access authentication procedure.
  • a user plane is setup with a serving gateway. This may include 3GPP long-term evolution (LTE) signaling.
  • the SRD in generating the access authentication signal may generate an APN signal that includes mobility protocol(s) supported by the SRD, a mobility protocol preference of the SRD 1 a mobility protocol for handoff, and/or may identify a PDN. This provides a mobility management capability and preference for the SRD that may be used by a mobility management mechanism to establish connectivity and to perform handoff between access networks.
  • the mobility management mechanism may refer to mobility management protocols and decisions used and performed within a VPLMN and/or a HPLMN. Mobility management decisions may be performed by the MME, the serving gateway, a HSS and/or an AAA server. In one embodiment, as described below, HPLMN server(s) determine a mobility protocol to use for establishing connectivity and handoff.
  • the mobility management mechanism may provide IP address allocation for the SRD.
  • the SRD may provide an indication of mobility management capability and preference by providing an APN.
  • the APN may include a specific PDN, as well as a mobility management descriptor.
  • An example of an APN 340 that may be used when a SRD identifies a PDN 1 is shown in FIG. 1OA.
  • the APN 340 may be referred to as an enhanced APN, as identified by step 301A.
  • the APN 340 includes a mobility management descriptor 342, which may include a mobility protocol support identifier 344, a mobility protocol preference identifier 346, and a mobility protocol handoff identifier 348.
  • the APN 340 may also include a PDN 350, a domain name 352, and a 3GPPTM identifier 354.
  • the domain name 352 may identify an operator, such as AT&TTM or T-mobileTM.
  • the 3GPPTM identifier 354 may indicate relationship of the APN 340 with a 3GPPTM system. Each of the stated identifiers may be one or more bits in length.
  • the SRD may provide a mobility management selection (MMS) APN defined for mobility management selection, as identified by step 301 B.
  • MMS mobility management selection
  • An example of a MMS APN 360 is shown in FIG. 10B and may be used when a SRD does not identify a PDN.
  • the MMS APN 360 may include a mobility management descriptor 362 with a mobility protocol support identifier 364, a mobility protocol preference identifier 366, and a mobility protocol handoff identifier 368.
  • the MMS APN may also include a first set of dummy bits 370, a second set of dummy bits 372, and a 3GPPTM identifier 374.
  • the first and second sets of dummy bits 372, 374 serve as place holders and replace the PDN bits and the domain name bits.
  • the length of the MMS APN 360 may be the same as the length of the enhanced APN.
  • the mobility management descriptor may identify a host- based protocol and a network-based protocol.
  • a host-based protocol may be identified to establish connectivity and to perform handoff.
  • a network-based protocol may be identified to establish connectivity and to perform handoff.
  • a mobility management descriptor may include one of a host-based protocol and a network-based protocol to establish connectivity and may include one of a host-based protocol and a network-based protocol to establish connectivity for handoff.
  • the access point and/or MME generates an access authentication request based on the access authentication signal.
  • the access authentication request is transmitted from the MME to the HPLMN server(s).
  • the access authentication request may include an AAA request signal that is transmitted to a HSS and/or an AAA server of a HPLMN.
  • step 303 the HPLMN server(s) select a mobility protocol for connectivity.
  • step 304 the HPLMN server(s) select a mobility protocol for handoff.
  • step 305 the HPLMN server(s) select a PDN gateway based on the access authentication request. As part of an authentication procedure the HSS and/or the AAA server authenticates the SRD and selects a PDN gateway. The stated selections of steps 303-305 may also be based on a roaming agreement with the VPLMN, an access network, a user profile, etc.
  • the HPLMN server(s) select the PDN gateway that supports a connectivity protocol and a mobility protocol of the SRD, as well as support services requested by the SRD.
  • a connectivity protocol may refer to a network layer protocol for packet-switched internetworks.
  • Example connectivity protocols are Internet protocols IPv4 and IPv6.
  • Example mobility protocols are host-based and network-based protocols, such as CMIP, DSMIP, and PMIP.
  • a network device may support and/or use a different version and/or connectivity protocol then that of a supported mobility protocol
  • the connectivity and mobility protocols are of the same type and version.
  • the connectivity protocol may be IPv6 and the mobility protocol may be MIPv6.
  • the following steps in FIG. 8 and subsequent Figures are primarily described as though the same connectivity protocol and mobility protocol versions and types are used.
  • the HPLMN server(s) generate an access authentication response signal.
  • the access authentication response signal includes a mobility protocol selection signal and a PDN gateway address signal and indicates a completion of SRD authentication by the HPLMN server(s).
  • the access authentication response signal may also include subscriber information.
  • the HPLMN server(s) may select the appropriate mobility protocols for connectivity and handoff and a PDN gateway.
  • the MME and/or the serving gateway may select the mobility protocols and/or PDN gateway, as generally indicated by box 307.
  • the mobility protocol selection signal indicates the selected mobility protocols for connectivity and handoff.
  • the PDN gateway address signal indicates an address of a PDN gateway that supports the mobility protocols selected.
  • the selected mobility protocol information for connectivity and handoff and the selected PDN gateway information are provided to the MME and/or the RAN and the serving gateway.
  • step 308 when a host-based mobility protocol is selected, step 310 may be performed, otherwise step 312 may be performed.
  • IP connectivity is setup between the MME and the selected PDN gateway.
  • IP mobile connectivity may be setup including setup of a network-based tunnel between the MME and the selected PDN gateway. IP mobile connectivity refers to the ability to perform handoff.
  • Network-based connectivity setup is identified by numerical designator 309.
  • GTP GPRS tunneling protocol
  • the IP connectivity between the MME and the PDN gateway may be performed using the GTP instead of the network-based mobility protocol.
  • the network-based tunnel may extend to the access point that is accessed by the SRD.
  • the SRD when in a MIPv4 foreign agent (FA) mode, may receive IP configuration information that is traditionally contained in a MIPv4 agent advertisement message through MIPv4 or link layer protocols.
  • the SRD when in a MlPv ⁇ mode, may receive IP configuration information that is traditionally contained in a MIPv6 router advertisement message either through M IPv4 or link layer protocols.
  • the MME When a host-based mobility protocol is selected for IP mobile connectivity and/or for handoff, the MME provides the selected PDN gateway information to the SRD.
  • the PDN gateway information may be provided when the SRD is connected to a home link in terms of host-based mobility protocol operations.
  • the MME or other network device may determine that the SRD is connected to a home link based on host-based mobility protocol procedures and configuration options, and based on the specifications of the host-based mobility protocol selected (e.g. CMIPv6, DSMIPv ⁇ , CMIPv4).
  • the PDN gateway information may also be provided when the SRD is not considered at home and a host-based binding update is to be sent from the SRD to the selected PDN gateway.
  • the MME generates a SRD access authentication response signal.
  • the SRD access authentication response signal may include the selected mobility protocol for IP mobile connectivity, the selected mobility protocol for handoff, and the selected PDN gateway.
  • the access authentication response signal may be transmitted to the SRD via the RAN or the serving gateway and access point. The SRD is then able to determine which mobility protocol to use in communicating with the network system and which mobility protocol to use when performing a handoff.
  • the SRD may not be provided with the selected PDN gateway information. Also, the SRD may not perform IP mobility procedures, such as those used for handoff, as this is performed by the network system.
  • the SRD is permitted to perform handoff to other access networks when the SRD and the network system (e.g. MME, serving gateway, and PDN gateway) support the same mobility protocol for handoff.
  • the SRD supports a network-based mobility protocol for handoff and the network system supports a host-based protocol for handoff, then the SRD can gain IP connectivity, but cannot perform handoff to other network accesses.
  • the SRD supports a host-based mobility protocol for handoff and the network system supports a network-based mobility protocol for handoff
  • the SRD can gain IP connectivity, but cannot perform handoff to other network accesses.
  • step 314 when a host-based mobility protocol is selected, step 316 may be performed, otherwise step 320 may be performed.
  • step 316 the attachment procedure is completed between the SRD and the MME based on the selected host-based mobility protocol.
  • step 318 the SRD generates a registration request signal.
  • the registration request signal is transmitted to the selected PDN gateway.
  • the SRD may register with a home agent of the PDN gateway.
  • step 319 the PDN gateway generates a registration response signal to complete registration of the SRD.
  • the registration response signal is transmitted to the SRD.
  • IP connectivity is setup between the SRD and the selected PDN gateway.
  • IP mobile connectivity may be setup including setup of a host-based tunnel between the SRD and a home agent of the selected PDN gateway.
  • GTP GPRS tunneling protocol
  • the IP connectivity between the MME and the PDN gateway may be performed using the GTP instead of a host-based mobility protocol.
  • step 320 the attachment procedure is completed between the SRD and the MME based on the network-based mobility protocol.
  • the SRD may not be informed of the selected PDN gateway and the SRD may not perform IP mobility procedures.
  • the address of the PDN gateway is not received by the SRD 1 since the SRD does not provide a binding update with the PDN gateway.
  • the SRD receives services from the PDN via the selected PDN gateway.
  • FIG. 11 an exemplary network system 400 illustrating roaming access via a trusted non-3GPP network is shown.
  • the network system 400 includes a SRD 402 that may communicate with one or more remote networks, such as a VPLMN and a HPLMN of a 3GPPTM system.
  • the SRD 402 includes a SRD mobility control module 404 and establishes IP connectivity with a PDN gateway 406 of the HPLMN to receive services, such as operator IP services.
  • the SRD 402 also establishes mobility protocol connectivity with the network system 400.
  • the SRD 402 obtains access, such as trusted non-3GPP IP access identified as 407, to the network system 400 via an access network 408.
  • the access network 408 may be a trusted non-3GPP IP access network, such as a WiMAX network.
  • the access network 408 may include an access network mobility control module 410 and/or a border router 412.
  • the access network 408 is in communication with a serving gateway 414 of the VPLMN.
  • the VPLMN includes a RAN 416, the serving gateway 418, a MME 420, and a SGSN 422.
  • the RAN 416, the serving gateway 418, and the MME 420 respectively include a RAN mobility control module 424, a serving gateway mobility control module 426, and a MME mobility control module 428.
  • the RAN 416, the serving gateway 414, and the MME 420 transfer mobility protocol information and PDN gateway selection information between the SRD 402 and the HPLMN.
  • the serving gateway 414 may be a SAE gateway or a WAG.
  • the MME 420 is in communication with each of the RAN 416, the SGSN 422, and the serving gateway 414.
  • the MME 420 performs SRD tracking and security functions.
  • the serving gateway 414 is in communication with the access network 408, the PDN gateway 406, the RAN 416, and the SGSN 422.
  • the SGSN 422 may perform MME selection and/or serving gateway selection.
  • the VPLMN may also include an AAA proxy server 430 that provides AAA information and subscriber profile information to the serving gateway 414 and/or the access network 408.
  • the HPLMN includes a HSS 432 that is in communication with an AAA server 434.
  • the HSS 432 and the AAA server 434 have respectively a HSS mobility control module 436 and an AAA server mobility control module 438.
  • the HPLMN including the HSS 432 and/or the AAA server 434 may select a mobility protocol and a PDN gateway in association with network access by the SRD 402.
  • the HPLMN including the HSS 432 and/or the AAA server 434 may provide the selected mobility protocol and selected PDN gateway information to the SRD 402.
  • the HPLMN also includes the PDN gateway 406, which is in communication with a hPCRF device 438 and a PDN 440 that provides IP services identified as 442.
  • the HSS 432 may have authentication and subscription data required for a subscriber, such as a subscriber associated with the SRD 402, to access the PDN 440.
  • the subscriber information may be stored in SRD records.
  • the HSS 432 may also store an IP address of the AAA server 434 to which the SRD is registered.
  • the HSS 432 may perform PDN gateway selection.
  • the hPCRF device 438 may be used to terminate reference points between network devices, such as reference points associated with the serving gateway 414, a vPCRF (not shown), and the hPCRF 438.
  • the AAA server 434 provides AAA information and subscriber profile information. This information may be obtained from the HSS 432. For example only, the AAA server 434 may authenticate the subscriber with the HSS 432 after an invoked tunnel establishment and/or attachment request by the SRD 402.
  • FIG. 12 another exemplary network system 450 is shown and includes a SRD 452, an AP 454, a serving gateway 456, and a MME 458.
  • the AP 454 may include a RAN, a WLAN 1 a WiMAX network, a cellular network, etc.
  • the SRD 452 may provide the AP 454 with service request information, IP connectivity protocol information, mobility protocol information, and/or PDN gateway information.
  • the SRD 452 may communicate with a HPLMN 460 via the AP 454, the serving gateway 456 and the MME 458 to setup connectivity and mobility tunnel(s), for communication between the SRD 452 and the PDN gateway.
  • the tunnel(s) may include a connectivity tunnel and/or a mobility tunnel.
  • the SRD 452 may include an antenna 470, an SR analog front- end module 472, a SR transmit module 474, a SR receive module 476, and a SR control module 478.
  • the SR analog front-end module 472 may transmit signals generated by the SR transmit module 474 via the antenna 470 and may output signals received from the antenna 470 to the SR receive module 476.
  • the SRD 452 may include an APN generator 479.
  • the AP 454 may include an antenna 480, an AP analog front- end module 482, an AP transmit module 484, an AP receive module 486, and an AP control module 487.
  • the AP analog front-end module 482 may transmit signals generated by the AP transmit module 484 via the antenna 480 and may output signals received from the antenna 480 to the AP receive module 486.
  • the serving gateway 456 may include an antenna 490, a serving gateway analog front-end module 492, a serving gateway transmit module 494, a serving gateway receive module 496, and a serving gateway control module 498.
  • the serving gateway analog front-end module 496 may transmit signals generated by the serving gateway transmit module 494 via the antenna 490 and may output signals received from the antenna 490 to the serving gateway receive module 496.
  • the MME 458 may include an antenna 500, a MME analog front-end module 502, a MME transmit module 504, a MME receive module 506, and a MME control module 508.
  • the MME analog front-end module 506 may transmit signals generated by the MME transmit module 504 via the antenna 500 and may output signals received from the antenna 500 to the MME receive module 506.
  • the MME 458 may be in communication with the HPLMN 460.
  • the HPLMN 460 may include a HSS 510 and an AAA server 512.
  • Example communications between the network devices FIGs. 11-12 and elements thereof are provided by the embodiments of FIGs. 13-16.
  • FIGs. 13 and 14 a logic flow diagram illustrating a method of providing mobility management and a message flow diagram illustrating the mobility management of the method are shown.
  • the method may apply to trusted non-3GPP IP access by a SRD.
  • the method may begin at step 550.
  • a connection between the AP and a serving gateway is used for the method of FIG. 13.
  • the SRD obtains IP connectivity to a network, such as a SAE network, without the need for SAE specific mechanisms for nodes at a border of a network of the AP.
  • the SRD also obtains IP connectivity without the need for additional security mechanisms to assure that IP traffic of the SRD is securely transported to and from the network.
  • the connection may be used when the access network is a trusted WLAN (e.g. not a public hotspot, but a network that is securely connected to the network).
  • a border router may perform as a default access router for this example.
  • the connection may be used when the access network is a WiMAX network, where the SRD is securely authenticated and connected to a core, due to WiMAX embedded security mechanisms.
  • the border router may perform as a WiMAX ASN GW.
  • the border router may perform as a PMIP client, as an access router (e.g. CMIPv ⁇ ), or as a foreign agent (e.g. CMIPv4).
  • the SRD generates an access authentication signal when accessing a PDN gateway.
  • the access and authentication signal is transmitted to an AP to initiate an attachment procedure and an access authentication procedure.
  • the access authentication procedure may include use of an extensible authentication protocol (EAP), an EAP method for global system for mobile communications (GSM) subscriber identity (EAP-SIM), or an EAP method for authentication universal mobile telecommunications system (UMTS) authentication and key agreement (EAP-AKA).
  • EAP extensible authentication protocol
  • GSM global system for mobile communications
  • EAP-SIM subscriber identity
  • UMTS universal mobile telecommunications system
  • EAP-AKA EAP method for authentication universal mobile telecommunications system
  • the SRD in generating the access authentication signal may generate an APN signal that includes mobility protocol(s) supported by the SRD, a mobility protocol preference of the SRD, a mobility protocol for handoff, and/or a PDN. This provides a mobility management capability and preference for the SRD that may be used by a mobility management mechanism to establish connectivity and to perform handoff between access networks.
  • the mobility management mechanism may refer to mobility management decisions performed within a VPLMN and/or a HPLMN. Mobility management decisions may be performed by the MME 1 the serving gateway, a HSS and/or an AAA server. In one embodiment as described below HPLMN server(s) determine a mobility protocol to use for establishing connectivity and handoff. The mobility management mechanism may provide IP address allocation for the SRD.
  • the SRD may provide an indication of mobility management capability and preference by providing an APN, as indicated by step 551A.
  • the APN may include a specific PDN, as well as a mobility management descriptor.
  • the APN may also include a PDN, a domain name, and a 3GPPTM identifier.
  • the domain name may identify an operator, such as AT&TTM or T-mobileTM.
  • the SRD may provide a MMS APN defined for mobility management selection, as indicated by step 551 B.
  • the MMS APN may include a mobility management descriptor, a first set of dummy bits, a second set of dummy bits, and a 3GPPTM identifier.
  • the access point generates an access authentication request based on the access authentication signal.
  • the access authentication request is transmitted from the AP to the HPLMN server(s).
  • the access authentication request may include an AAA request signal that is transmitted to a HSS and/or an AAA server of a HPLMN.
  • the HPLMN server(s) select a mobility protocol for connectivity.
  • the HPLMN server(s) select a mobility protocol for handoff.
  • the HPLMN server(s) may select a PDN gateway based on the access authentication request.
  • the HSS and/or the AAA server authenticates the SRD and may select a PDN gateway.
  • the stated selections may also be based on a roaming agreement with the VPLMN, an access network, a user profile, etc.
  • the HPLMN server(s) generate an access authentication response signal.
  • the access authentication response signal includes a mobility protocol selection signal and may include a PDN gateway address signal and indicates a completion of SRD authentication by the HPLMN server(s).
  • the HPLMN server(s) may select the appropriate mobility protocols for connectivity and handoff and a PDN gateway.
  • the selected mobility protocol information for connectivity and handoff and the selected PDN gateway information may be provided to the AP and the serving gateway.
  • the access authentication response signal may also include subscriber information.
  • the AP and/or the serving gateway may select the mobility protocols and/or PDN gateway, as generally indicated by box 557.
  • the AP generates a SRD access authentication response signal.
  • the SRD access authentication response signal is transmitted to the SRD and may include the selected mobility protocol for IP mobile connectivity, the selected mobility protocol for handoff, and the selected PDN gateway.
  • the SRD is then able to determine which mobility protocol to use in communicating with the network system and which mobility protocol to use when performing a handoff.
  • step 560 when a host-based mobility protocol is selected for IP mobile connectivity and/or for handoff, step 562 may be performed, otherwise step 570 may be performed.
  • step 562 the AP provides the selected PDN gateway information to the SRD.
  • step 564 the attachment procedure is completed between the SRD and the AP based on the selected hostbased mobility protocol.
  • step 566 the SRD generates a registration request signal.
  • the registration request signal is transmitted to the selected PDN gateway.
  • the SRD may register with a home agent of the PDN gateway.
  • the SRD may send a host-based binding update to the selected PDN gateway.
  • the PDN gateway generates a registration response signal to complete registration of the SRD.
  • the registration response signal is transmitted to the SRD.
  • IP connectivity is setup between the SRD and the selected PDN gateway.
  • IP mobile connectivity may be setup including setup of a host-based tunnel between the SRD and a home agent of the selected PDN gateway.
  • GTP GPRS tunneling protocol
  • the IP connectivity between the AP and the PDN gateway may be performed using the GTP instead of a host-based mobility protocol.
  • step 578 is performed.
  • a border router of the AP may allocate a SRD IP address and provide it to the SRD.
  • the border router may perform network-based mobility procedures.
  • the SRD may not be provided with the selected PDN gateway information and the attachment procedure may be completed between the SRD and the AP based on the network-based mobility protocol.
  • the SRD may not perform IP mobility procedures, such as those used for handoff, as this is performed by the network system.
  • the AP is provided with the address of the PDN gateway selected.
  • the AP establishes IP connectivity with the serving gateway and the selected PDN gateway using the selected mobility protocol.
  • IP connectivity is setup between the AP and the selected PDN gateway.
  • IP mobile connectivity may be setup including setup of a network-based tunnel between the AP and the selected PDN gateway.
  • Network- based connectivity setup is identified by numerical designator 577.
  • the SRD receives services from the PDN via the selected PDN gateway.
  • FIGs. 15 and 16 a logic flow diagram illustrating a method of providing mobility management and a message flow diagram illustrating the mobility management of the method are shown.
  • the method may apply to trusted non-3GPP IP access by a SRD.
  • the method may begin at step 600.
  • step 601 the SRD when accessing a PDN gateway generates an access authentication signal, which is transmitted to an AP to initiate an attachment procedure and an access authentication procedure.
  • the access authentication procedure may include use of an EAP, an EAP-SIM 1 or an
  • Mobility management decisions may be performed by a serving gateway, a MME, a HSS and/or an AAA server.
  • HPLMN server(s) determine mobility protocol(s) to use for establishing connectivity and handoff.
  • the MME and/or the serving gateway may be involved in the determination and/or may determine the mobility protocols.
  • the access point In step 602, the access point generates an access authentication request based on the access authentication signal.
  • the access authentication request is transmitted from the AP to the HPLMN server(s).
  • the access authentication request may include an AAA request signal that is transmitted to a HSS and/or an AAA server of a HPLMN.
  • the HPLMN server(s) generate an access authentication completion signal.
  • the access authentication response signal and may include subscriber information.
  • the access authentication response signal is transmitted to the AP.
  • the SRD generates a configuration request signal, which is transmitted to the AP.
  • the configuration request signal is generated to facilitate configuration procedures, which may include for example the use of a dynamic host configuration protocol (DHCP).
  • DHCP dynamic host configuration protocol
  • the transmission of the configuration request signal initiates a retrieval of SRD network parameters, as identified by box 609.
  • the configuration request signal may include mobility protocol(s) supported by the SRD, a mobility protocol preference of the SRD, a mobility protocol for handoff, and/or a PDN.
  • the SRD may provide an indication of mobility management capability and preference by providing an APN.
  • the APN may include a specific PDN, as well as a mobility management descriptor.
  • the APN may also include a PDN, a domain name, and a 3GPPTM identifier.
  • the domain name may identify an operator, such as AT&TTM or T-mobileTM.
  • the SRD may provide a MMS APN defined for mobility management selection, as indicated by step 608B.
  • An example of a MMS APN is shown in FIG. 10B for when a SRD does not identify a PDN.
  • the MMS APN may include a mobility management descriptor, a first set of dummy bits, a second set of dummy bits, and a 3GPPTM identifier.
  • the AP, the serving gateway, the MME 1 and/or the HPLMN server(s) select a mobility protocol for connectivity.
  • the AP 1 the serving gateway, the MME, and/or the HPLMN server(s) select a mobility protocol for handoff.
  • the AP, the serving gateway, the MME, and/or the HPLMN server(s) may select a PDN gateway based on the access authentication request.
  • the HSS and/or the AAA server authenticates the SRD and may select a PDN gateway.
  • the stated selections may also be based on a roaming agreement with the VPLMN, an access network, a user profile, etc.
  • the stated selections may be provided to the AP:
  • step 616 when a host-based mobility protocol is selected for IP mobile connectivity and/or for handoff, step 618 is performed, otherwise step 630 is performed.
  • the AP generates a configuration response signal, which is transmitted to the SRD.
  • the configuration response signal includes a mobility protocol selection signal and may include a PDN gateway address signal.
  • the SRD is then able to determine which mobility protocol to use in communicating with the network system and which mobility protocol to use when performing a handoff.
  • the configuration response signal may also include SRD network parameters, which may include an SRD IP address.
  • the attachment procedure is completed between the SRD and the AP based on the selected network-based mobility protocol.
  • the SRD generates a registration request signal.
  • the registration request signal is transmitted to the selected PDN gateway.
  • the SRD may register with a home agent of the PDN gateway.
  • the SRD may send a host-based binding update to the selected PDN gateway.
  • the PDN gateway generates a registration response signal to complete registration of the SRD.
  • the registration response signal is transmitted to the SRD.
  • IP connectivity is setup between the SRD and the selected PDN gateway.
  • IP mobile connectivity may be setup including setup of a host-based tunnel between the SRD and the selected PDN gateway.
  • GTP GPRS tunneling protocol
  • the IP connectivity between the AP and the PDN gateway may be performed using the GTP instead of a host-based mobility protocol.
  • step 640 is performed.
  • the AP establishes IP connectivity with the serving gateway and the selected PDN gateway using the selected mobility protocol.
  • IP connectivity is setup between the AP and the selected PDN gateway.
  • IP mobile connectivity may be setup including setup of a network-based tunnel between the AP and the selected PDN gateway.
  • Network-based connectivity setup is identified by numerical designator 631.
  • the SRD may not be provided with the selected PDN gateway information and the attachment procedure is completed between the SRD and the AAP based on the host-based mobility protocol.
  • the SRD may not perform IP mobility procedures, such as for handoff, as this is performed by the network system.
  • the AP generates a configuration response signal, which is transmitted to the SRD.
  • the configuration response signal includes a mobility protocol selection signal and may include a PDN gateway address signal.
  • the configuration response signal may include network configuration parameters including a SRD IP address.
  • the SRD is then able to determine which mobility protocol to use in communicating with the network system and which mobility protocol to use when performing a handoff.
  • the SRD receives services from the PDN via the selected PDN gateway.
  • the network system 650 includes a SRD 652 that may communicate with a HPLMN of a 3GPPTM system.
  • the SRD 652 includes a SRD mobility control module 654 and establishes IP connectivity with a PDN gateway 656 of the HPLMN to receive services, such as IP services identified as 657.
  • the SRD 652 also establishes mobility protocol connectivity with the network system 650.
  • the SRD 652 obtains access, such as 3GPP IP access identified as 658, to the network system 650 via an access network 660.
  • the access network 660 may be a non-3GPPTM network, such as a WLAN, a WIMAX network, a cellular network, etc.
  • the access network 660 may include an access network mobility control module 662.
  • the access network 660 is in communication with the PDN gateway 656 and a HSS 664.
  • the HSS 664 is in communication with an AAA server 666.
  • the HSS 664 and the AAA server 666 have respectively a HSS mobility control module 668 and an AAA server mobility control module 670.
  • the HSS 664 and/or the AAA server 666 may select a mobility protocol and the PDN gateway 656 in association with network access by the SRD 652.
  • the HSS 664 and/or the AAA server 666 may provide the selected mobility protocol and selected PDN gateway information to the SRD 652.
  • the PDN gateway 656 is in communication with a hPCRF device 672 and a PDN 674.
  • the HSS 664 may have authentication and subscription data required for a subscriber, such as a subscriber associated with the SRD 652, to access the PDN 674.
  • the subscriber information may be stored in SRD records.
  • the HSS 664 may also store an IP address of the AAA server 666 to which the SRD 652 is registered.
  • the HSS 664 may perform PDN gateway selection.
  • the hPCRF device 672 may be used to terminate reference points between network devices.
  • the AAA server 670 provides AAA information and subscriber profile information. This information may be obtained from the HSS 664. For example only, the AAA server 670 may authenticate the subscriber with the HSS
  • the network system 700 includes a SRD 702 that may communicate with a HPLMN of a 3GPPTM system.
  • the SRD 702 includes a SRD mobility control module 704 and establishes IP connectivity with a PDN gateway 706 of the HPLMN to receive services, such as IP services identified as 708.
  • the SRD 702 also establishes mobility protocol connectivity with the network system 700.
  • the SRD 702 obtains access, such as trusted non-3GPP IP access identified as 710, to the network system 700 via an access network 712.
  • the access network 712 may be a non-3GPPTM network, such as a WLAN, a WIMAX network, a cellular network, etc.
  • the access network 712 may include an access network mobility control module 713.
  • the access network 712 is in communication with the PDN gateway 706 and a HSS 714 and.
  • the HSS 714 is in communication with an AAA server 716.
  • the HSS 714 and the AAA server 716 have respectively a HSS mobility control module 718 and an AAA server mobility control module 720.
  • the HSS 714 and/or the AAA server 716 may select a mobility protocol and the PDN gateway 706 in association with network access by the SRD 702.
  • the HSS 714 and/or the AAA server 716 may provide the selected mobility protocol and selected PDN gateway information to the SRD 702.
  • the PDN gateway 706 is in communication with a hPCRF device 718 and a PDN 720.
  • the HSS 714 may have authentication and subscription data required for a subscriber, such as a subscriber associated with the SRD 702, to access the PDN 720.
  • the subscriber information may be stored in SRD records.
  • the HSS 714 may also store an IP address of the AAA server 716 to which the SRD 702 is registered.
  • the HSS 714 may perform PDN gateway selection.
  • the hPCRF device 718 may be used to terminate reference points between network devices.
  • the AAA server 716 provides AAA information and subscriber profile information. This information may be obtained from the HSS 714. For example only, the AAA server 716 may authenticate the subscriber with the HSS
  • FIGs. 19 and 20 a logic flow diagram illustrating a method of providing mobility management and a message flow diagram illustrating the mobility management are shown.
  • a stateful IP address configuration is used though similar extensions are possible for stateless IP address configurations.
  • the method may apply to when a SRD supports a network-based mobility protocol and/or has a preference of using a network-based mobility protocol. This method may also apply to when a SRD accesses a network system using a trusted non-3GPP access network.
  • the method may begin at step 750.
  • initial non-3GPP access specific layer 2 procedures may be performed.
  • Layer 2 procedures refer to procedures that may be performed by a data link layer of an Open Systems Interconnection Basic Reference Model (OSI) model.
  • OSI Open Systems Interconnection Basic Reference Model
  • the SRD may determine that the local access network requires stateful IP address configuration. The SRD may receive a router advertisement message indicating this.
  • step 754 the SRD generates and sends a DHCP request message to request an IP address and also to indicate a mobility protocol preference.
  • An FJAP authentication procedure may be initiated and performed involving the SRD, the access network, and an AAA server. Unlike in the roaming case where multiple AAA proxies may be involved, an AAA proxy may not be involved.
  • the SRD may provide an explicit indication of a preferred mobility protocol for the establishment of IP connectivity.
  • the SRD may also provide an indication of a desired mobility protocol for handoff.
  • a network-based mobility protocol may be used as a default.
  • the network such as a HPLMN including a HSS and/or the AAA server, selects a PDN gateway.
  • the AAA server may select the PDN gateway.
  • the AAA server may select the PDN gateway. This may include an additional name resolution step and the issuance of a request to a domain name system (DNS) server.
  • DNS domain name system
  • the SRD may be informed of the selected PDN gateway.
  • the PDN gateway information may be provided to a mobile access gateway or other network device of the access network.
  • step 760 when the network supports a network-based mobility protocol and authorizes the use of the network-based mobility protocol, step 778 is performed, otherwise step 770 is performed.
  • the network may refer to the access network or the HPLMN including the PDN Gateway.
  • the network may indicate that the network does not support the network-based mobility protocol by either sending a DHCP reply message or by not responding to the SRD.
  • step 772 when the SRD does not receive a reply before a timer expires, step 754 may be repeated and the DHCP request signal may be resent.
  • steps 774 and 776 may be performed.
  • the SRD may choose another mobility protocol and return to step 754.
  • step 776 the SRD may elect not to access the network.
  • step 760 may be repeated.
  • a layer 3 procedure may refer to a procedure that is performed by a network layer of an OSI model.
  • the layer 3 attachment procedure may be based off of DHCP or Neighbor Discovery protocols and/or stateless IP address configurations.
  • CMIPv ⁇ nodes on the same link use a Neighbor Discovery protocol to discover each other's presence, to determine each other's link-layer addresses, to find routers, and to maintain contact information about the paths to active neighbors.
  • Nodes hosts and routers
  • Nodes use the Neighbor Discovery protocol to determine the link-layer addresses for neighbors known to reside on attached links and to quickly purge cached values that become invalid.
  • Hosts also use the Neighbor Discovery protocol to find neighboring routers that are willing to forward packets on their behalf.
  • nodes use the Neighbor Discovery protocol to actively keep track of which neighbors are reachable and which are not, and to detect changed link-layer addresses. When a router or the path to a router fails, a host actively searches for functioning alternates.
  • RFC 4861 which is incorporated herein by reference in its entirety.
  • an access network or a mobility access gateway may send a proxy binding update message to the selected PDN gateway.
  • the MAG may be part of the trusted access network.
  • the selected PDN gateway may inform the AAA server, such as a 3GPP AAA server, of the address of the selected PDN gateway.
  • the PDN gateway processes the proxy binding update and generates a binding cache entry for the SRD.
  • the PDN gateway allocates an IP address(es) (e.g. remote IP address(es)) for the SRD.
  • the PDN gateway then sends a proxy binding acknowledgement to the MAG including the IP address(es) allocated to the SRD.
  • IP address(es) e.g. remote IP address(es)
  • the PDN gateway then sends a proxy binding acknowledgement to the MAG including the IP address(es) allocated to the SRD.
  • the SRD requests both an IPv4 and an IPv6 address, multiple IP addresses are allocated.
  • the SRD requests an IPv4 address or an IPv6 address, then a single IP address may be allocated.
  • the network establishes a network-based mobility protocol tunnel, such as a PMIP tunnel.
  • a PMIPv ⁇ tunnel may be setup between the access network and the selected PDN gateway.
  • the PDN gateway may return the selected PDN gateway address to the access network.
  • the MAG or access network may return the allocated IP address to the SRD.
  • the MAG returns the selected PDN gateway address for the user plane when: the PDN gateway address is received from the PDN gateway; a host-based mobility protocol is supported by the PDN gateway; and when the SRD indicates a host-based mobility protocol preference for handoff to other access networks.
  • the layer 3 attachment procedure is completed. IP connectivity between the SRD and the PDN gateway is set for uplink and downlink communication.
  • a MIPv4 FA mode may be enabled.
  • the SRD may generate an agent solicitation message to indicate the SRD mobility protocol preferences.
  • the agent solicitation message is provided to an access network.
  • the access network supports the M IPv4 FA mode, the access network responds with a MIPv4 agent advertisement message.
  • the SRD operates in the M IPv4 FA mode based on reception and/or content of the agent solicitation message.
  • the SRD may provide an indication of mobility protocol preferences.
  • the SRD may establish full local connectivity through the access network without indicating mobility protocol preferences of the SRD.
  • the SRD may establish connectivity by indicating mobility protocol preferences to the access network.
  • FIGs. 21 and 22 provide an example of when the SRD does indicate mobility protocol preferences. Stateful IP address configuration is used for the example of FIGs. 21 and 22, though similar extensions may be used for stateless IP address configuration.
  • FIGs. 21 and 22 a logic flow diagram illustrating a method of providing mobility management and a message flow diagram illustrating the mobility management are shown. The method may begin at step 800.
  • step 801 initial non-3GPP access specific layer 2 procedures may be performed.
  • a SRD may determine that the local access network requires stateful IP address configuration.
  • the SRD may receive a router advertisement message indicating this.
  • step 804 the SRD sends a DHCP request message to request an IP address, which may initiate a layer 3 attachment procedure.
  • the DHCP request message may indicate the mobility protocol preferences of the SRD, such as a preference to use CMIP.
  • the mobility protocol preferences may be provided after step 820.
  • An EAP authentication procedure may be initiated and performed involving the SRD, the access network, and a 3GPP AAA server.
  • step 806 when the network, such as a HPLMN, supports CMIP, step 808 is performed, otherwise step 818 is performed.
  • step 808 when the network permits the SRD to use CMIP step 810 is performed, otherwise step 818 is performed.
  • the PDN gateway address may be selected.
  • the network may indicate authorization by sending a DHCP reply message to the SRD.
  • the DHCP reply message may include a local IP address for the SRD.
  • the PDN gateway address may be provided as part of the DHCP reply message.
  • the DHCP reply message may be provided to the MAG.
  • step 820 when the SRD does not receive a reply message within a predetermined amount of time, step 804 may be repeated. Alternatively, one of steps 824 and 826 may be performed, otherwise step 828 may be performed. In step 824, the SRD may select another mobility protocol preference and return to step 804. In step 826, the SRD may stop attempting to gain access. [0269] In step 828, after successful authentication and authorization, a layer 3 attachment procedure may be initiated. The SRD may generate a mobility protocol preference signal that includes the mobility protocols supported and preferred for IP connectivity and/or for handoff when previously not indicated. [0270] In step 830, the SRD configures a local IP address from the access network based on the configuration of the access link (e.g.
  • the SRD begins the MIPv6 bootstrapping procedure.
  • the SRD establishes a security association with the selected PDN gateway and configures the SRD's home address.
  • the SRD sends a binding update message to the selected PDN gateway.
  • the selected PDN gateway generates and transmits a binding acknowledgement message to the SRD.
  • a host-based mobility protocol tunnel may be setup between the SRD and the selected PDN gateway.
  • the layer 3 attachment procedure is completed. IP connectivity between the SRD and the PDN gateway is set for uplink and downlink communications.
  • the embodiments disclosed herein provide system architectures that support both host-based IP mobility management (CMIP) and network-based mobility management (PMIP).
  • CMIP host-based IP mobility management
  • PMIP network-based mobility management
  • the system architectures support CMIP-capable SRDs, PMIP-capable SRDs, and CIMP/PMIP-capable SRDs.
  • system architectures apply to networks that support PMIP and/or CMIP based handovers.
  • FIGs. 23A-23E various exemplary implementations incorporating the teachings of the present disclosure are shown.
  • the teachings of the disclosure can be implemented in a network interface 843 of a high definition television (HDTV) 837.
  • the HDTV 837 includes an HDTV control module 838, a display 839, a power supply 840, memory 841 , a storage device 842, the network interface 843, and an external interface 845.
  • the network interface 843 includes a wireless local area network interface, an antenna (not shown) may be included.
  • the HDTV 837 can receive input signals from the network interface 843 and/or the external interface 845, which can send and receive data via cable, broadband Internet, and/or satellite.
  • the HDTV control module 838 may process the input signals, including encoding, decoding, filtering, and/or formatting, and generate output signals.
  • the output signals may be communicated to one or more of the display 839, memory 841 , the storage device 842, the network interface 843, and the external interface 845.
  • Memory 841 may include random access memory (RAM) and/or nonvolatile memory.
  • Nonvolatile memory may include any suitable type of semiconductor or solid-state memory, such as flash memory (including NAND and NOR flash memory), phase change memory, magnetic RAM, and multi-state memory, in which each memory cell has more than two states.
  • the storage device 842 may include an optical storage drive, such as a digital versatile disc (DVD) drive, and/or a hard disk drive (HDD).
  • the HDTV control module 838 communicates externally via the network interface 843 and/or the external interface 845.
  • the power supply 840 provides power to the components of the HDTV 837.
  • the teachings of the disclosure may be implemented in a in a network interface 852 of a vehicle 846.
  • the vehicle 846 may include a vehicle control system 847, a power supply 848, memory 849, a storage device 850, and the network interface 852. If the network interface 852 includes a wireless local area network interface, an antenna (not shown) may be included.
  • the vehicle control system 847 may be a powertrain control system, a body control system, an entertainment control system, an anti-lock braking system (ABS), a navigation system, a telematics system, a lane departure system, an adaptive cruise control system, etc.
  • the vehicle control system 847 may communicate with one or more sensors 854 and generate one or more output signals 856.
  • the sensors 854 may include temperature sensors, acceleration sensors, pressure sensors, rotational sensors, airflow sensors, etc.
  • the output signals 856 may control engine operating parameters, transmission operating parameters, suspension parameters, braking parameters, etc.
  • the power supply 848 provides power to the components of the vehicle 846.
  • the vehicle control system 847 may store data in memory 849 and/or the storage device 850.
  • Memory 849 may include random access memory (RAM) and/or nonvolatile memory.
  • Nonvolatile memory may include any suitable type of semiconductor or solid-state memory, such as flash memory (including NAND and NOR flash memory), phase change memory, magnetic RAM, and multi-state memory, in which each memory cell has more than two states.
  • the storage device 850 may include an optical storage drive, such as a DVD drive, and/or a hard disk drive (HDD).
  • the vehicle control system 847 may communicate externally using the network interface 852.
  • the teachings of the disclosure can be implemented in a in a network interface 868 of a cellular phone 858.
  • the cellular phone 858 includes a phone control module 860, a power supply 862, memory 864, a storage device 866, and a cellular network interface 867.
  • the cellular phone 858 may include the network interface 868, a microphone 870, an audio output 872 such as a speaker and/or output jack, a display 874, and a user input device 876 such as a keypad and/or pointing device.
  • the network interface 868 includes a wireless local area network interface, an antenna (not shown) may be included.
  • the phone control module 860 may receive input signals from the cellular network interface 867, the network interface 868, the microphone 870, and/or the user input device 876.
  • the phone control module 860 may process signals, including encoding, decoding, filtering, and/or formatting, and generate output signals.
  • the output signals may be communicated to one or more of memory 864, the storage device 866, the cellular network interface 867, the network interface 868, and the audio output 872.
  • Memory 864 may include random access memory (RAM) and/or nonvolatile memory.
  • Nonvolatile memory may include any suitable type of semiconductor or solid-state memory, such as flash memory (including NAND and NOR flash memory), phase change memory, magnetic RAM, and multi-state memory, in which each memory cell has more than two states.
  • the storage device 866 may include an optical storage drive, such as a DVD drive, and/or a hard disk drive (HDD).
  • the power supply 862 provides power to the components of the cellular phone 858.
  • FIG. 23D the teachings of the disclosure can be implemented in a in a network interface 885 of a set top box 878.
  • the set top box 878 includes a set top control module 880, a display 881, a power supply 882, memory 883, a storage device 884, and the network interface 885. If the network interface 885 includes a wireless local area network interface, an antenna (not shown) may be included.
  • the set top control module 880 may receive input signals from the network interface 885 and an external interface 887, which can send and receive data via cable, broadband Internet, and/or satellite.
  • the set top control module 880 may process signals, including encoding, decoding, filtering, and/or formatting, and generate output signals.
  • the output signals may include audio and/or video signals in standard and/or high definition formats.
  • the output signals may be communicated to the network interface 885 and/or to the display 881.
  • the display 881 may include a television, a projector, and/or a monitor.
  • the power supply 882 provides power to the components of the set top box 878.
  • Memory 883 may include random access memory (RAM) and/or nonvolatile memory.
  • Nonvolatile memory may include any suitable type of semiconductor or solid-state memory, such as flash memory (including NAND and NOR flash memory), phase change memory, magnetic RAM, and multi-state memory, in which each memory cell has more than two states.
  • the storage device 884 may include an optical storage drive, such as a DVD drive, and/or a hard disk drive (HDD).
  • HDD hard disk drive
  • the mobile device 889 may include a mobile device control module 890, a power supply 891 , memory 892, a storage device 893, the network interface 894, and an external interface 899. If the network interface 894 includes a wireless local area network interface, an antenna (not shown) may be included.
  • the mobile device control module 890 may receive input signals from the network interface 894 and/or the external interface 899.
  • the external interface 899 may include USB, infrared, and/or Ethernet.
  • the input signals may include compressed audio and/or video, and may be compliant with the MP3 format.
  • the mobile device control module 890 may receive input from a user input 896 such as a keypad, touchpad, or individual buttons.
  • the mobile device control module 890 may process input signals, including encoding, decoding, filtering, and/or formatting, and generate output signals.
  • the mobile device control module 890 may output audio signals to an audio output 897 and video signals to a display 898.
  • the audio output 897 may include a speaker and/or an output jack.
  • the display 898 may present a graphical user interface, which may include menus, icons, etc.
  • the power supply 891 provides power to the components of the mobile device 889.
  • Memory 892 may include random access memory (RAM) and/or nonvolatile memory.
  • RAM random access memory
  • Nonvolatile memory may include any suitable type of semiconductor or solid-state memory, such as flash memory (including NAND and NOR flash memory), phase change memory, magnetic RAM, and multi-state memory, in which each memory cell has more than two states.
  • the storage device 893 may include an optical storage drive, such as a DVD drive, and/or a hard disk drive (HDD).
  • the mobile device may include a personal digital assistant, a media player, a laptop computer, a gaming console, or other mobile computing device.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un dispositif de réseau comprenant un module d'émission destiné à émettre un signal de nom de point d'accès contenant des informations de protocole indiquant un protocole de mobilité soutenu par le dispositif de réseau. Un module de réception reçoit un signal d'adresse de passerelle de réseau à commutation de paquets contenant l'adresse d'une passerelle de réseau à commutation de paquets qui soutient le protocole de mobilité. Un module de commande établit un tunnel de communication avec la passerelle de réseau à commutation de paquets en fonction de l'adresse de la passerelle.
PCT/US2008/003805 2007-03-23 2008-03-21 Selection de mecanisme de mobilite ip pour terminaux multimodes a connectivite ip directe WO2008118388A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP08727101A EP2135419A1 (fr) 2007-03-23 2008-03-21 Selection de mecanisme de mobilite ip pour terminaux multimodes a connectivite ip directe
JP2009554593A JP2010522483A (ja) 2007-03-23 2008-03-21 ダイレクトｉｐコネクティビティを有するマルチモード端末のためのｉｐモビリティメカニズムの選択

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
US89660607P 2007-03-23 2007-03-23
US60/896,606 2007-03-23
US94935107P 2007-07-12 2007-07-12
US60/949,351 2007-07-12
US95757907P 2007-08-23 2007-08-23
US60/957,579 2007-08-23

Publications (1)

Publication Number Publication Date
WO2008118388A1 true WO2008118388A1 (fr) 2008-10-02

Family

ID=39615825

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2008/003805 WO2008118388A1 (fr) 2007-03-23 2008-03-21 Selection de mecanisme de mobilite ip pour terminaux multimodes a connectivite ip directe

Country Status (4)

Country Link
EP (1) EP2135419A1 (fr)
JP (1) JP2010522483A (fr)
TW (1) TW200904099A (fr)
WO (1) WO2008118388A1 (fr)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009018533A2 (fr) * 2007-08-02 2009-02-05 Qualcomm Incorporated Sélection de passerelle dynamique basée sur le service de données et le protocole d'itinérance
WO2010009635A1 (fr) * 2008-07-23 2010-01-28 华为技术有限公司 Procédé et appareil destinés à sélectionner un réseau à commutation de paquets
WO2010079984A2 (fr) * 2009-01-08 2010-07-15 Samsung Electronics Co., Ltd. Procédé d'accès à un pdn local dans un système de communication sans fil
WO2010099741A1 (fr) * 2009-03-04 2010-09-10 华为技术有限公司 Procédé de sélection de réseau, dispositif et terminal
CN102550083A (zh) * 2009-04-30 2012-07-04 三星电子株式会社 无线通信系统的毫微微蜂窝中支持本地互联网协议接入的方法和装置
JP2013507077A (ja) * 2009-10-06 2013-02-28 モサイド・テクノロジーズ・インコーポレーテッド セルラーシステムと他の無線システムとの間に相互運用性を実現するシステムおよび方法
JP2013514022A (ja) * 2009-12-15 2013-04-22 ノキア シーメンス ネットワークス オサケユキチュア ハンドオーバのシグナリング方式を決定するための方法、装置、関連するコンピュータプログラム製品及びデータ構造
WO2015039278A1 (fr) * 2013-09-17 2015-03-26 华为技术有限公司 Procédé, dispositif et système d'établissement de réseau public de données

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2017152754A (ja) * 2014-07-09 2017-08-31 シャープ株式会社 端末装置、ｍｍｅ、ｐｇｗ、通信システムおよび通信制御方法

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050128956A1 (en) * 2003-08-05 2005-06-16 Hsu Raymond T. Packet data services using version and capability Information

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050128956A1 (en) * 2003-08-05 2005-06-16 Hsu Raymond T. Packet data services using version and capability Information

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
ALEXANDER SILICON GRAPHICS S ET AL: "DHCP Options and BOOTP Vendor Extensions; rfc2132.txt", IETF STANDARD, INTERNET ENGINEERING TASK FORCE, IETF, CH, 1 March 1997 (1997-03-01), XP015007916, ISSN: 0000-0003 *
DAMIC D PREMEC B PATIL M SAHASRABUDHE NOKIA SIEMENS NETWORKS S KRISHNAN ERICSSON D: "Proxy Mobile IPv6 indication and discovery; draft-damic-netlmm-pmip6- ind-discover-03.txt", IETF STANDARD-WORKING-DRAFT, INTERNET ENGINEERING TASK FORCE, IETF, CH, no. 3, 25 February 2008 (2008-02-25), XP015052749, ISSN: 0000-0004 *
KRISHNAN ERICSSON S: "Client Initiated Selection of Proxy Mobility; draft-krishnan-netlmm-pmip-sel-00.txt", IETF STANDARD-WORKING-DRAFT, INTERNET ENGINEERING TASK FORCE, IETF, CH, 7 June 2007 (2007-06-07), XP015051890, ISSN: 0000-0004 *
YUANKUI ZHAO SHANGHAI HUAWEI TECHNOLOGY: "DHCP option for MIP type Decision; draft-zhao-dhc-miptype-00.txt", IETF STANDARD-WORKING-DRAFT, INTERNET ENGINEERING TASK FORCE, IETF, CH, 25 February 2006 (2006-02-25), XP015050627, ISSN: 0000-0004 *
YUANKUI ZHAO SHANGHAI HUAWEI TECHNOLOGY: "MIP type decision in netlmm workgroup; draft-zhao-netlmm-miptype-00.txt", IETF STANDARD-WORKING-DRAFT, INTERNET ENGINEERING TASK FORCE, IETF, CH, 25 February 2006 (2006-02-25), XP015050629, ISSN: 0000-0004 *

Cited By (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009018533A2 (fr) * 2007-08-02 2009-02-05 Qualcomm Incorporated Sélection de passerelle dynamique basée sur le service de données et le protocole d'itinérance
WO2009018533A3 (fr) * 2007-08-02 2009-03-26 Qualcomm Inc Sélection de passerelle dynamique basée sur le service de données et le protocole d'itinérance
JP2010535456A (ja) * 2007-08-02 2010-11-18 クゥアルコム・インコーポレイテッド データサービスおよびローミングプロトコルに基づく動的なゲートウェイ選択
WO2010009635A1 (fr) * 2008-07-23 2010-01-28 华为技术有限公司 Procédé et appareil destinés à sélectionner un réseau à commutation de paquets
WO2010079984A2 (fr) * 2009-01-08 2010-07-15 Samsung Electronics Co., Ltd. Procédé d'accès à un pdn local dans un système de communication sans fil
WO2010079984A3 (fr) * 2009-01-08 2010-10-21 Samsung Electronics Co., Ltd. Procédé d'accès à un pdn local dans un système de communication sans fil
WO2010099741A1 (fr) * 2009-03-04 2010-09-10 华为技术有限公司 Procédé de sélection de réseau, dispositif et terminal
EP3468254A1 (fr) * 2009-04-30 2019-04-10 Samsung Electronics Co., Ltd. Procédé et appareil pour supporter un accès ip local dans une cellule femto d'un système de communication sans fil
EP2425659A4 (fr) * 2009-04-30 2015-07-01 Samsung Electronics Co Ltd Procédé et appareil destinés à assister un accès à un protocole internet (ip) local dans une femtocellule d'un système de communication sans fil
US10893556B2 (en) 2009-04-30 2021-01-12 Samsung Electronics Co., Ltd Method and apparatus for supporting local IP access in a femto cell of a wireless communication system
CN102550083A (zh) * 2009-04-30 2012-07-04 三星电子株式会社 无线通信系统的毫微微蜂窝中支持本地互联网协议接入的方法和装置
US11006276B2 (en) 2009-10-06 2021-05-11 Conversant Intellectual Property Management Inc. System and method providing interoperability between cellular and other wireless systems
JP2013507077A (ja) * 2009-10-06 2013-02-28 モサイド・テクノロジーズ・インコーポレーテッド セルラーシステムと他の無線システムとの間に相互運用性を実現するシステムおよび方法
US9049623B2 (en) 2009-12-15 2015-06-02 Wireless Future Technologies Inc. Methods, apparatuses, related computer program product and data structure for deciding on a signaling scheme for handover
US9072012B2 (en) 2009-12-15 2015-06-30 Wireless Future Technologies Inc. Methods, apparatuses, related computer program product and data structure for deciding on a signaling scheme for handover
US9055489B2 (en) 2009-12-15 2015-06-09 Wireless Future Technologies Inc. Methods, apparatuses, related computer program product and data structure for deciding on a signaling scheme for handover
US9609554B2 (en) 2009-12-15 2017-03-28 Wireless Future Technologies Inc. Methods, apparatuses, related computer program product and data structure for deciding on a signaling scheme for handover
US9936424B2 (en) 2009-12-15 2018-04-03 Wireless Future Technologies Inc. Methods, apparatuses, related computer program product and data structure for deciding on a signaling scheme for handover
US10595235B2 (en) 2009-12-15 2020-03-17 Wireless Future Technologies Inc. Methods, apparatuses, related computer program product and data structure for deciding on a signaling scheme for handover
US8665830B2 (en) 2009-12-15 2014-03-04 Nokia Siemens Networks Oy Methods, apparatuses, related computer program product and data structure for deciding on a signaling scheme for handover
JP2013514022A (ja) * 2009-12-15 2013-04-22 ノキア シーメンス ネットワークス オサケユキチュア ハンドオーバのシグナリング方式を決定するための方法、装置、関連するコンピュータプログラム製品及びデータ構造
US11109282B2 (en) 2009-12-15 2021-08-31 Wireless Future Technologies Inc. Methods, apparatuses, related computer program product and data structure for deciding on a signaling scheme for handover
US11711730B2 (en) 2009-12-15 2023-07-25 Wireless Future Technologies Inc. Methods, apparatuses, related computer program product and data structure for deciding on a signaling scheme for handover
WO2015039278A1 (fr) * 2013-09-17 2015-03-26 华为技术有限公司 Procédé, dispositif et système d'établissement de réseau public de données

Also Published As

Publication number Publication date
JP2010522483A (ja) 2010-07-01
EP2135419A1 (fr) 2009-12-23
TW200904099A (en) 2009-01-16

Similar Documents

Publication Publication Date Title
US20080254768A1 (en) Packet data network connectivity domain selection and bearer setup
US9042308B2 (en) System and method for connecting a wireless terminal to a network via a gateway
EP2165496B1 (fr) Méthodes et appareils pour detecter si un équipement utilisateur se trouve dans un réseau d'accès fiable ou un réseau d'accès non fiable
EP2353271B1 (fr) Établissement sécurisé d'un tunnel lors de l' attachement ou passage à un réseau d'accès
US20180198672A1 (en) Methods For IP Mobility Management
US20080320149A1 (en) Service request device wireless access detach and bearer deactivation methods withou loss of internet protocol connectivity
US9277579B1 (en) Method and apparatus for supporting multiple connections in 3GPP systems
US8780800B2 (en) Optimized home link detection
EP2135419A1 (fr) Selection de mecanisme de mobilite ip pour terminaux multimodes a connectivite ip directe
US20080219218A1 (en) Gtp for Integration of Multiple Access
US20060294363A1 (en) System and method for tunnel management over a 3G-WLAN interworking system
US8879504B2 (en) Redirection method, redirection system, mobile node, home agent, and proxy node
EP2923280A1 (fr) Systèmes et méthodes d'accès à un réseau
WO2008119296A1 (fr) Procédé et dispositif permettant de réaliser la négociation du protocole de gestion de la mobilité
WO2009089762A1 (fr) Procédé et dispositif pour qu'une passerelle d'accès non 3gpp acquière un mode interactif avec une entité de décision politique
Eisl et al. Management of Multiple Mobility Protocols and Tools in Dynamically Configurable Networks
WO2009003578A1 (fr) Procédé, système et point d'accès pour le support de mobilité de réseau

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: 08727101

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2009554593

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 2008727101

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE