Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W8/00—Network data management
  • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
  • H04W8/08—Mobility data transfer
  • H04W8/082—Mobility data transfer for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L12/00—Data switching networks
  • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W36/00—Hand-off or reselection arrangements
  • H04W36/0005—Control or signalling for completing the hand-off
  • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
  • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W76/00—Connection management
  • H04W76/10—Connection setup
  • H04W76/11—Allocation or use of connection identifiers
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W8/00—Network data management
  • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
  • H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
  • H04W88/02—Terminal devices
  • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W36/00—Hand-off or reselection arrangements
  • H04W36/0005—Control or signalling for completing the hand-off
  • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
  • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W76/00—Connection management
  • H04W76/20—Manipulation of established connections
  • H04W76/22—Manipulation of transport tunnels
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W8/00—Network data management
  • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
  • H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
• • 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
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W84/00—Network topologies
  • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
  • H04W84/04—Large scale networks; Deep hierarchical networks
  • H04W84/042—Public Land Mobile systems, e.g. cellular systems
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W84/00—Network topologies
  • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
  • H04W84/10—Small scale networks; Flat hierarchical networks
  • H04W84/12—WLAN [Wireless Local Area Networks]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
  • H04W88/16—Gateway arrangements
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W92/00—Interfaces specially adapted for wireless communication networks
  • H04W92/02—Inter-networking arrangements

Definitions

• the invention relates to network control node, a terminal and a method for controlling different types of connection sessions.
• the invention relates to multi-access and mobility.
• 3GPP is now discussing various way to implement MA (Mobile Access) mobility.
• Each mobility solution has its own gateway. Traffic should typically go through many gateway (e.g. GGSN and HA) .
• Gateway e.g. GGSN and HA
• Each mobility solution is using some kind of tunnelling. Having many tunnelling is not optimal, especially over cellular access.
• Each mobility solution has its own mechanism to select the gateway. Typically, it is difficult to select the same gateway.
• a gateway comprising a supporting unit configured to support a plurality of connection session types; a providing unit configured to provide a connection session to a terminal; and an associating unit configured to associate a parameter with the connection session to the terminal.
• a terminal comprising a supporting unit configured to support a plurality of connection session types; a providing unit configured to provide a connection session to a gateway; and a receiver configured to receive a parameter which is associated with the gateway.
• the object is solved by a method for controlling a gateway in a network, wherein the gateway is able to support a plurality of connection session types, the method comprising: providing a connection session to a terminal; and associating a parameter with the connection session to the terminal.
• the object is solved by a method for controlling a terminal, wherein the terminal is able to support a plurality of connection session types, the method comprising: providing a connection session to a gateway; and receiving a parameter which is associated with the gateway.
• a system for providing mobility to a terminal through at least two different mobility protocols is provided, wherein:
• each mobility protocol provides information to the terminal related to all other mobility protocol during a registration.
• connection session as such can be clearly identified.
• mobility and session continuity can be provided even in case different mobility solutions (different connection session types) are provided.
• the invention provides a mobility solution in which multiple mobility technology can be combined and session continuity across these multiple mobility technologies is allowed.
• Fig. 1 shows a signalling flow where the terminal using the integrated mobility session first power-on using GPRS connection session type according to a first embodiment
• Fig. 2A shows a signalling flow where the terminal using the integrated mobility session first power-on using Mobile IP as a connection session type according to the first embodiment
• Fig. 2B a layer structure in terminal and gateway
• FIG. 3 shows a signalling flow where the terminal using the integrated mobility session first power-on with GPRS as a connection session type according to a second embodiment
• Fig. 4 shows a signalling flow where the terminal using the integrated mobility session first power-on with Mobile IP as a connection session type according to the second embodiment
• Fig. 5 shows a signalling flow where the terminal using the integrated mobility session first power-on with GPRS connection session type according to a third embodiment
• Fig. 6 shows a signalling flow where the terminal using the integrated mobility session first power-on with Mobile IP as a connection session type according to the third embodiment
• Fig. 7A shows a basic configuration of a gateway according to the embodiments
• Fig. 7B shows a basic configuration of a terminal according to the embodiments .
• the preferred embodiments propose an integrated mobility solution, where one gateway (also referred to as mobility gateway or integrated mobility gateway) supports a single mobility session through more than one mobility technology, and is able to return to the Mobile Node (MN) configuration parameters or session parameter to ensure that the MN will stay connected to this same gateway if mobility technology are used.
• MN Mobile Node
• the gateway allocates the same home address to the MN when the mobility technology changes during a session, so that the change of mobility technology is invisible to the correspondent node.
• the terminal i.e., the Mobile Node (MN)
• MN Mobile Node
• the terminal i.e., the Mobile Node (MN)
• MN Mobile Node
• 3GPP mechanism Mobile IP
• Mobike Mobile IP
• the MN will receive configuration/session parameters, and use them to configure the other protocols part of this mobility session .
• ISN Intelligent Service Node
• GGSN-MIPv4 Home Agent combining GGSN-MIPv4 Home Agent
• step Al the UE (User Entity) or Mobile Station (MS) or Mobile Node (MN) sends a PDP (Packet Data Protocol) context request.
• the MS adds an indication that integrated MIPv4 mobility is supported. This is preferably added in the Protocol Configuration Option so that a SGSN transfer it transparently.
• the indication consists of a mobility session ID. A certain value e.g. 0000 indicates that no prior mobility session exists. +
• an integrated mobility session is created in the ISN (step A2).
• This integrated mobility session may be updated through GPRS or MIP as illustrated below.
• This integrated mobility session will not be terminated if the GPRS session is deactivated. But it will wait for a possible Mobile IP update.
• the ISN returns a PDP context accept containing its MIPv4 HA (Home Agent) IP address (and/or optionally logical name HA NAI Home Address Network Access Identifier, as defined in RFC3846, for example) , a temporary shared secret (valid for this session) , a SPI (Security Parameter Index) , and optionally a GGSN identity (preferably coded as an APN (Access Point Name) ) .
• a unique mobility session identifier should be included. These are preferably added in the Protocol Configuration Option so that SGSN transfer it transparently.
• the IP address returned to the MS in the PDP context activation response will be the MN address for the duration of the mobility session. So it will also be the Mobile IP home address .
• step A4 it is now assumed that the MN detects a WLAN which has higher priority than the cellular network, e.g. its Home WLAN.
• step A5 it sends a MIP Registration Request (RRQ) to the HA address received in step A3.
• the authentication field is computed using the temporary shared secret and SPI received in step A3.
• the RRQ also includes the home address allocated in step A3 by the GGSN.
• the request includes also HA NAI (as proposed in RFC 3846) and mobility session ID as a vendor extension .
• step A6 the ISN receives the request and finds the proper session context using the session ID (Note that overlapping address support is assumed, so Home address is not enough to uniquely identify the MS) .
• the ISN authenticates the MS and accept the request. That is, in step A6, the mobility session is identified through the mobility session ID, security procedures are performed to validate the request, and an update is performed in the ISN to route the session through this new access.
• step A7 a corresponding response (R Resp) is sent to the MS.
• the same mobility session identifier should be included (for protocol simplicity) in the accept message, as well as GGSN identity coded as APN.
• MIP session is established. E.g., an IP-in-IP tunnel is created and all traffic is now routed to the MS care- off address.
• ISN and the MS have a mobility session (referred by unique mobility session ID) containing GTP (GPRS Tunneling Protocol) parameters and MIP parameters. Both sessions are active.
• GTP GPRS Tunneling Protocol
• SGSN may release the PDP context based on a timer (there is no data traffic is SGSN) . So, in step A8, the PDP context is deactivated.
• ISN the parameters related to the GTP tunnel are erased.
• ISN and the MS have a mobility session (referred by unique mobility session ID) containing MIP parameters.
• the MS also contains the GGSN identity coded as APN.
• the GTP session is not active.
• step A9 it is assumed that the MS moves back to cellular coverage. As it has an active mobility session it will not use its default APN, but use the one receive in step A3 or A7 (GGSN ID) . Standard SGSN will route the request to the same ISN (as only one is associated with this APN) . The MS adds the mobility session ID. This is preferably added in the Protocol Configuration Option so that SGSN transfer it transparently.
• step AlO the ISN returns a PDP context accept containing its MIPv4 HA IP address (and optionally logical name HA NAI, as in RFC3846), temporary shared secret (possibly a new one valid for this session) , SPI (Security Parameter Index) , and GGSN identity (preferably coded as an APN) .
• temporary shared secret possibly a new one valid for this session
• SPI Security Parameter Index
• GGSN identity preferably coded as an APN
• the same mobility session identifier should be included (for protocol simplicity) . These are preferably added in the Protocol Configuration Option so that SGSN transfer it transparently.
• FIG. 2A Another example is described by referring to the signaling flow shown in Fig. 2A.
• an Intelligent Service Node ISN (combining GGSN-MIPv4 Home Agent) is assumed, and it is assumed that the MS first connects over Mobile IP (MIP) .
• MIP Mobile IP
• the MN connects through, e.g., a WLAN by sending a MIP Registration Request to a preconfigured HA address.
• the authentication field is computed using preconfigured shared secret and SPI.
• the RRQ also includes the MN NAI, in order to request a dynamic home address allocation.
• the request includes also mobility session ID set to 0000 as a vendor extension .
• step B2 the ISN receives the request, authenticates the MN, and detects it is a new session (since session ID is 000 in step Bl), allocates dynamically a home address, as well as a unique session identifier.
• the ISN returns GGSN identity coded as APN in the accept message.
• a MIP session is established. E.g., an IP-in-IP tunnel is created and all traffic is now routed to the MS care-off address.
• step B3 the MN updates its GPRS configuration with the received APN for the duration of this mobility session. This is also illustrated in Fig. 2B, in which the corresponding lay structure is illustrated. MIP, IP and WLAN is shown in bold in order to emphasize the settings.
• the layer structure is the same for the terminal and for the gateway.
• the terminal may be a single device (e.g. mobile phone) or consists of many different device.
• the common mobility layer may be on a laptop while the GPRS layer may be on a data card.
• the layer structure it is noted that on top a common mobility layer is present.
• this common mobility layer provides :
• the common mobility layer will configure one stack (e.g. GPRS) with the information received (GPRS APN; common session ID) through the other stack (e.g. MIP)
• one stack e.g. GPRS
• GPRS APN common session ID
• MIP multi-tenant IP
• the gateway is typically integrating many mobility technologies.
• the common mobility layer will provide one stack (e.g. GPRS) with the information to be sent to the terminal (MIP HA address; security parameters; HA names; common session ID) related the other stack (e.g. MIP)
• step B4 it is now assumed that the MN loses WLAN connectivity, so that it now moves to GPRS.
• step B5 the MN sends a create PDP request including the mobility session ID received in step B2 and using APN received in step B2.
• the SGSN selects the GGSN normally (e.g. with a DNS (Domain Name Server) ) .
• the network is configured so that this APN uniquely points to the ISN selected in step Bl.
• mobility session ID is preferably added in the Protocol Configuration Option so that SGSN transfer it transparently.
• step B6 the ISN returns a PDP context accept containing its MIPv4 HA IP address (and optionally logical name HA NAI, as in RFC3846), temporary shared secret, SPI (Security Parameter Index) .
• SPI Security Parameter Index
• the same mobility session identifier should be included (for protocol simplicity) . These are preferably added in the Protocol Configuration Option so that SGSN transfer it transparently.
• Step B7 and B8 on the figure shows what happens when the MS moves back to a MIP connection.
• the MN sends a MIP RRQ to the ISN, including the mobility session ID (which may be in this case 1111, for example) .
• APN "GGSN/HA7”
• HoA Address of the Home Agent
• a preferred way to implement the MS is to have a combined mobility layer between the application and the GPRS stack/MIP stack.
• the application will use a virtual interface to connect with this combined mobility layer and receive through this interface its Home address.
• the combined mobility layer will store in a context the information related to the mobility session, track the active interface (MIP or GPRS) , and configure the MIP and GPRS protocol with the appropriate parameters for the active mobility session.
• MIP or GPRS active interface
• the combined mobility layer may erase the parameters related to that mobility session.
• GPRS and MIP stack will then use pre- configured parameters the next time a connection is established.
• a mobility session ID is used as the parameter for identifying a connection session (such as a mobility session) .
• the assumption is that one MN can have many simultaneous sessions.
• Mobility Session ID is a robust way to uniquely identify the right session.
• the IP address cannot be used to uniquely identify the session, as private address may overlap .
• the MN identity could be used to uniquely identify the session, but it would limit the number of session to one by MN. It is not practical as different mobility protocols typically used different type of identity. That would not support concept like UMTS router (having many computers connected behind one UMTS modem)
• this mobility session ID (also abbreviated as session ID only) can be used that integrated mobility is supported and can be used. This can be indicated in step Al by a session ID containing only 000000.
• the MS needs to have a preconfigured shared secret, and MIP HA.
• MIP HA MIP HA.
• the MS will always first connect to GPRS.
• the MS and network store the parameters from the previous session.
• the GPRS signaling includes MIP parameters, and the MIP signaling includes GPRS parameters. That is, for example the mobility session ID is included in the PDP context accept message (step A3) .
• the GPRS signalling triggers a MIP message (Agent Advirtisements) carrying MIP parameters (including the mobility session ID) , instead of sending them inside the GPRS signaling.
• Fig. 3 a corresponding modification of the signaling flow of Fig. 1 is shown.
• the steps Cl to ClO are identical to the steps Al to AlO, except for steps C3 and ClO and the addition of steps C3bis and ClObis.
• steps C3 and ClO only the PDP context accept message is sent, without other parameters. Instead, in steps C3bis and ClObis an Agent Advertisement message including those parameters is sent.
• Fig. 4 a corresponding modification of the signaling flow of Fig. 2 is shown.
• the steps Dl to D8 are identical to the steps Bl to B8, except for step D6 and the addition of step D ⁇ bis.
• step D6 Similar as in Fig. 3, in step D6, only the PDP context accept message is sent, without other parameters. Instead, in step D ⁇ bis an Agent Advertisement message including those parameters is sent.
• HA NAI is used for identifying the ISN. This is shown in Figs. 5 and 6.
• HA NAI HA NAI
• Flexi ISN case it could uniquely identify the right service card.
• a single logical name is associated to the ISN. This name may be used either as the HA NAI (RFC3846) or as the GPRS APN (Access Point Name) .
• the benefit is that standard MIP signaling can be used (No new vendor extension to send back the APN, but just HA NAI is sent) . The client will then use the returned logical name as an APN for the GPRS signaling.
• Figs. 5 and 6 This is illustrated in Figs. 5 and 6, in which steps El to ElO and Fl to F8 are identical to steps Al to AlO and Bl to B8 of Figs. 1 and 2, respectively, except for steps E7, E9, F2, F5 and F8.
• step E7 in the R Resp message, the HA NAI is sent instead of the GGSN identity. This is used for the PDP context request in step E9.
• Fig. 7A illustrates a basic configuration of a gateway according to the present embodiments.
• the gateway 1 may comprise a supporting unit 11 configured to support a plurality of connection session types, a providing unit 12 configured to provide a connection session to a terminal, and an associating unit 13 configured to associate a parameter with the connection session to the terminal.
• Fig. 7B illustrates a basic configuration of a terminal according to the present embodiments.
• the terminal 2 may comprise: a supporting unit 21 configured to support a plurality of connection session types, a providing unit 22 configured to provide a connection session to a gateway, and a receiver 23 configured to receive a parameter which is associated with the gateway.
• the invention is not limited to the mobility protocols described above, but is also applicable to other mobility protocols.
• a combined mobility session may support connectivity through more than 2 underlying protocols .
• a particularly relevant example is combining the 3GPP LTE (Long Term Evolution ) mobility, GPRS and Mobike.
• extension to MObike will provide the MN with the identifier of the ISN (alternatively there might be 2 identifiers one for LTE and one for GPRS) and a unique mobility session identifier.
• the MS moves under the 3GPP LTE network it will sends the identifier of the ISN to be connected to the same gateway, and this gateway will uniquely identify the session through the mobility session identifier.
• the same IP address will be allocated to the MS, external correspond node will not detect any changes .
• the invention is also applicable to MlPv ⁇ .
• security parameters are slightly different in MlPv ⁇ .
• MlPv ⁇ is that the home IPv6 address is unique, and session ID parameter could be avoided in some cases.
• the invention is not limited to mobile connection sessions only. That is, also fixed network access points could be included.
• a laptop computer may have access via WLAN, but can also be connected via a network cable.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Databases & Information Systems (AREA)
• Mobile Radio Communication Systems (AREA)
• Data Exchanges In Wide-Area Networks (AREA)

Priority Applications (5)

Applications Claiming Priority (4)

Publications (1)

Family

ID=38263100

Family Applications (1)

Country Status (10)

Cited By (8)

Families Citing this family (16)

Citations (4)

Family Cites Families (17)

• 2007
  • 2007-01-09 US US11/651,013 patent/US9094947B2/en active Active
  • 2007-01-11 WO PCT/IB2007/050088 patent/WO2007080549A1/en not_active Ceased
  • 2007-01-11 KR KR1020087017226A patent/KR100979616B1/ko active Active
  • 2007-01-11 DK DK07700053.7T patent/DK1985087T3/en active
  • 2007-01-11 PL PL07700053T patent/PL1985087T3/pl unknown
  • 2007-01-11 EP EP07700053.7A patent/EP1985087B1/en active Active
  • 2007-01-11 CN CN200780006982.3A patent/CN101390370B/zh active Active
  • 2007-01-11 ES ES07700053.7T patent/ES2629605T3/es active Active
  • 2007-01-11 RU RU2008130135/09A patent/RU2409907C2/ru active
  • 2007-01-11 JP JP2008549965A patent/JP4954219B2/ja active Active
• 2012
  • 2012-01-04 JP JP2012000032A patent/JP5461591B2/ja active Active
• 2015
  • 2015-06-16 US US14/741,267 patent/US9686809B2/en active Active

Patent Citations (4)

Also Published As

Similar Documents

Legal Events