US20080212536A1 - Policy based mechanisms for selecting access routers and mobile context - Google Patents
Policy based mechanisms for selecting access routers and mobile context Download PDFInfo
- Publication number
- US20080212536A1 US20080212536A1 US12/149,790 US14979008A US2008212536A1 US 20080212536 A1 US20080212536 A1 US 20080212536A1 US 14979008 A US14979008 A US 14979008A US 2008212536 A1 US2008212536 A1 US 2008212536A1
- Authority
- US
- United States
- Prior art keywords
- context
- policy server
- access router
- mobile node
- identifier
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 230000007246 mechanism Effects 0.000 title description 6
- 238000012546 transfer Methods 0.000 claims description 29
- 238000000034 method Methods 0.000 claims description 22
- 230000003068 static effect Effects 0.000 claims description 21
- 238000004590 computer program Methods 0.000 claims 4
- 230000008859 change Effects 0.000 abstract description 4
- 230000000694 effects Effects 0.000 abstract description 4
- 230000008569 process Effects 0.000 description 12
- 238000013475 authorization Methods 0.000 description 4
- 239000000284 extract Substances 0.000 description 4
- 238000013459 approach Methods 0.000 description 2
- 230000001010 compromised effect Effects 0.000 description 2
- 238000003379 elimination reaction Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000001228 spectrum Methods 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 230000000903 blocking effect Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000013439 planning Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
- H04L67/303—Terminal profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
- H04W12/062—Pre-authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/12—Reselecting a serving backbone network switching or routing node
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
- H04W8/24—Transfer of terminal data
-
- 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/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
- H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
-
- 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
-
- 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
- H04W36/0038—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information of security context information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/08—Reselecting an access point
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
- H04W40/34—Modification of an existing route
- H04W40/36—Modification of an existing route due to handover
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
-
- 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
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/16—Interfaces between hierarchically similar devices
- H04W92/20—Interfaces between hierarchically similar devices between access points
Definitions
- each access router must discover candidate access routers for possible handover, select the target access router for actual handover based on the capabilities of the mobile node, authenticate the target access router and finally perform the context transfer. Specifically, each access router performs the following functions:
- routers can authenticate each other. They may relay on public key based mechanism but it's a along way to go as the public key mechanism may take time into effect.
- the router selection rules or algorithms are installed on all access routers or Mobile Nodes. This may increase the cost of both access routers and mobile nodes and impact router performance. In addition, a simple change of the selection rules requires updating on all routers or mobile nodes.
- the proposals in this invention comprise two aspects. First, we propose a policy based mechanism to select a possible target (new) access router for context transfer. Second, we describe two context transfer sequences for intra/inter domain handovers.
- FIG. 1 is a reference system for transferring context of a mobile node between autonomous systems
- FIG. 2 shows a context transfer message flow, according to an embodiment
- FIG. 3 shows a proactive handover embodiment
- An embodiment of the invention may perform policy based target router selection and context transfer. Embodiments may provide the following benefits:
- Routers do not need to expose and discover the capabilities of other routers because this information is readily available at policy servers. This effectively reduces the amount of messages exchanged over the network, saving valuable bandwidth.
- Access routers are freed from target router selection process and most of context transfer process. Hence they can focus on performing their main duty, i.e., route internet protocol packets.
- Access routers need not execute proxy application if their neighbors are running different technology.
- the critical resource is radio spectrum.
- radio resources are allocated to the MN prior to authorization. If the MN failed the authentication and authorization process, then such radio resources have to be revoked. This could have repercussions such as the blocking of a legitimate user that could be handed over to this network otherwise.
- Receiver driven approach for target selection helps in reducing denial of service attacks.
- a possible disadvantage is that the policy server may become a single point of failure. But proper network planning and incorporating Rservpool architecture for policy server can strengthen the availability and reliability of the policy server.
- FIG. 1 shows the reference architecture for the context transfer framework and the target access router selection process.
- Access routers e.g. source access router (AR) 101 and destination access router 123 are policy targets.
- the access routers may report their capabilities (QoS, Security etc) to a policy server 105 .
- the policy server (PS 1 ) 105 then downloads the corresponding policy to the AR 101 according to the reported capabilities. Therefore the policy server 105 has all the information about an AR 101 capabilities in the administrative domain 110 .
- the policy server 105 can retrieve information relating to the base station 107 from the database of network management systems. The information includes, for example, which access router a base station 107 is connected to.
- Mobile Node (MN) 151 is currently in Autonomous System AS 1 110 and is communicating with a server in a core network 140 .
- the static capabilities of the MN 151 are stored in a AAA server, e.g. AAA1 server 109 .
- the policy server can retrieve this information from the AAA server of the MN home network.
- the MN 151 when the MN 151 is in the AS 1 110 , the static capabilities of the MN 115 are retrieved by PS 1 105 from AAA1 server 109 and dynamic capabilities (or negotiated profiles) are kept with the access router AR 1 107 that is currently serving the MN 151 .
- the MN 151 moves toward Autonomous System (AS 2 ) 120 , it receives identification information on a broadcast channel which may contain link layer information of a second base station (BS 2 ) 127 or IP address of AR 2 120 or Autonomous System number associating some link local address or any combination information. MN 151 forwards the information to AR 1 101 .
- AS 2 Autonomous System
- An embodiment includes steps.
- the first step is the access router selection process where policy servers compute a list of possible access routers that may serve the MN 151 and the MN 151 is informed of this list by the policy server in its own domain.
- the second step involves the actual context transfer. Details of the two steps are described in the following subsections.
- the policy server in the same domain as the candidate access routers computes the selection process.
- the MN When the MN receives new identifiers from more than one base station through the broadcast channel, the MN forwards the information to the AR currently serving it, e.g. AR 1 101 .
- the access router forwards it to the policy server, e.g. PS 1 105 .
- the minimal information which the policy server 105 expects is either the link layer identifier or Autonomous System (AS) number and link layer identifier.
- AS Autonomous System
- PS 1 105 If PS 1 105 receives only link layer identifier, it checks first with the policy database to see whether that is simply an intra domain handover. If it is not an intra domain handover, PS 1 105 checks with the neighboring AS defined in the policy database and forwards to their neighboring policy server.
- the policy server e.g. AR 1 101 , forwards the information to the respective policy server, e.g. PS 2 126 , along with the MN static capabilities (which it retrieved from AAA1 server 109 ).
- the PS 2 125 determines whether AS 2 120 can potentially serve the MN 151 . If yes, PS 2 125 further computes the candidate access routers that will be able to serve the MN 151 . PS 2 129 then returns the computed access routers to PS 1 105 (this is totally dependent on the topology of the AS). An algorithm for selecting the access routers is described in the next subsection. If the access router cannot serve the MN, PS 2 125 simply sends a negative acknowledgement to PS 1 105 .
- MN 151 has forwarded more than one access system identifiers to the AR 1 101 , the PS 1 105 performs the above steps for each access system. Finally PS 1 105 sends a message to MN 151 informing all the possible (or authorized) ARs that may server the MN 151 .
- An embodiment of an AR selection algorithm may be used by a policy server. It is based on a sequence of elimination processes.
- the order of the rules may be changed on the policy server.
- a rule that is able to eliminate more routers should be evaluated before those that eliminate fewer routers. Some times it may be difficult to predict which rule will eliminate more routers. The insight can be gained with experience and a careful analysis of log data on policy servers.
- PS can pre-authorize MN.
- the initiating PS after receiving the list of possible AR's has to periodically inform the MN's presence in their network.
- the second step in the above selection algorithm requires the policy server to have the knowledge of traffic load on the access routers.
- a policy server may obtain the current load of access routers:
- the policy server also performs admission controls, it knows the load on those routers naturally. If there is an admission control server, for example a bandwidth broker, the policy server can do a simple query of the server to get the load situation on those routers.
- an admission control server for example a bandwidth broker
- Some networks may have no centralized admission control.
- a network may operate on constrained routing where unused network resources are advertised globally within an administrative domain and each router makes admission control decision based on the advertised information.
- the policy server simply listens to the advertisement to know the unused resources on those routers. It then uses that information as an input to the above router selection algorithm.
- a MN When a MN is roaming in a network, it may receive signals from adjacent base stations.
- the MN can perform two types of handovers namely reactive and proactive.
- the MN informs the new access router to pickup its context from the old access router.
- the MN forwards the new access router's identities to the old access router and informs the old access router to push the context to the new access router.
- MN is initially in AS 2 and is moving towards AS 1 . MN picks up more than one base station signals. With the target access router selection process described above, the MN is aware of the possible access routers who can satisfy its capabilities.
- FIG. 2 shows a context transfer message flow
- MN 251 that was roaming in the AS 2 220 moves towards AS 1 210 and starts receiving the base station signal.
- MN 251 forwards the AS 2 :AR 2 identity to the AR 1 , as a identity packet 261 .
- AR 1 201 requests 262 PS 1 205 to prepare the context transfer request.
- PS 1 205 forwards the MN context request to the AS 2 220 in a forwarded packet 263 .
- AR 2 223 sends the context related to the MN in a message 264 to PS 2 225 .
- PS 2 225 adds to the context received from AS 2 the static context about MN that is available at PS 2 225 .
- PS 2 225 may collect other dynamic context from other network elements.
- MN 251 may have a security context associated with a gateway in AS 2 220 .
- PS 2 225 sends all these static and dynamic contexts to AR 1 201 in a first cross-network message 265 .
- AR 1 201 extracts the context relevant to AR 1 201 and forwards the rest of the context 266 to PS 1 .
- PS 1 205 extracts the static context and forwards the rest of the context 167 to related network elements, e.g., a security gateway that will reconstruct the security context. PS 1 205 sends a context transfer complete message to AR 2 223 in a second cross-network message 267 .
- AR 2 223 forwards the context transfer complete message 268 to PS 2 225 and finally context may be removed from AS 2 223 .
- the policy server may be totally kept in private address space due to security reasons and may not be accessible or visible from outside the autonomous system.
- FIG. 3 shows a proactive handover embodiment
- MN 351 is initially in the AS 1 310 and is moving towards AS 2 320 . MN 351 picks up more than one base station signals. With the target access router selection process described above, the MN 351 is aware of the possible access routers who can satisfy its capabilities.
- each possible AS domain has pre-authorized the MN 351 .
- context transfer is just a simple relocation of state information.
- MN 351 that is currently roaming in AS 1 310 decides to move to AS 2 320 because the signal from AS 2 320 is stronger than that from AS 1 310 . Under this situation MN 351 forwards 361 the AS 2 :AR 2 identity to the AR 1 301 and requests it to start the context transfer.
- AR 1 301 forwards the context to PS 1 305 and informs PS 1 305 to forward 362 the context to AR 2 323 .
- PS 1 305 adds to the context received from AR 1 301 the static context about MN 351 that is available at PS 1 305 .
- PS 1 305 may collect other dynamic context from other network elements.
- MN 351 may have a security context associated with a gateway.
- PS 1 305 sends 363 all these static and dynamic contexts to AR 2 323 .
- AR 2 323 extracts the context relevant to AR 2 323 and forwards 364 the rest of the context to PS 2 329 .
- PS 2 329 extracts the static context and forwards the rest of the context to related network elements, e.g., a security gateway that will reconstruct the security context.
- PS 2 329 sends 365 a context transfer complete message to AR 1 301 .
- AR 1 301 forwards 366 the context transfer complete message to PS 1 305 and finally context is removed from AS 1 310 .
Abstract
In mobile IP networks, when a mobile node (MN) moves from one cell to another, handover occurs. The result of the handover is that the MN connects to the network through a new access router (AR). The handover may occur between access routers of the same or different administrative domains. In all cases, the information related to the mobile node has to be transferred from the old AR to the new AR in order to minimize the effect of the change of access routers.
Description
- This is a Divisional of application Ser. No. 10/309,366, filed Dec. 2, 2002, which claims priority of Provisional Patent Application No. 60/336,937, filed Dec. 3, 2001, the contents of which are incorporated herein.
- In mobile IP networks, when a mobile node (MN) moves from one cell to another, handover occurs. The result of the handover is that the MN connects to the network through a new access router (AR). The handover may occur between access routers of the same or different administrative domains. In all cases, the information related to the mobile node has to be transferred from the old AR to the new AR in order to minimize the effect of the change of access routers. This is the so-called context transfer (see H. Syed et al, “General Requirements for a Context Transfer Framework,” draft-ietf-seamoby-ct-reqs-alpha05.txt, IETF Internet Draft, May 2001). We propose a policy-based approach that is efficient, secure and does not require significant additional functionalities being built into access routers.
- Current or proposed solutions are based on moving the complete intelligence to the network elements, i.e., access routers. Each access router must discover candidate access routers for possible handover, select the target access router for actual handover based on the capabilities of the mobile node, authenticate the target access router and finally perform the context transfer. Specifically, each access router performs the following functions:
- 1. Contacting the respective Home agent server
- 2. Contacting the Home AAA server
- 3. Interpreting the static subscription profile of the mobile node
- 4. Authenticating and authorizing the neighboring access routers
- 5. Interpreting the static capability of the neighboring access routers (and/or)
- 6. Moving the static capacity of the mobile node to the access routers (and/or)
- 7. Performing some pre-context activities before the actual context transfer
- 8. Finally transferring the context to the new access router
- These functions are in addition to the main responsibilities of an access router, i.e., to route IP packets based on subscriber information and to perform metering and monitoring for charging and management purposes. Hence, the above functions may require a radical change in the current Internet infrastructure. The following are the potential shortcomings:
- 1. Currently there is no common mechanism for two access routers to exchange information across two autonomous systems (AS).
- 2. For security reasons, network operators do not want to expose the capabilities or capacity of their access routers. If one of the router is compromised the whole system is likely to get compromised. Yet current solutions require routers to expose their capabilities to other routers in same or different domains
- 3. Moving the intelligence to the access router is a security issue. Control and update distributed information is always a potential problem. In strictly protected networks such as Telecom networks, this may be less important. But IP networks are not as easy to protect as Telecom networks.
- 4. There are no automatic schemes where routers can authenticate each other. They may relay on public key based mechanism but it's a along way to go as the public key mechanism may take time into effect.
- 5. The router selection rules or algorithms are installed on all access routers or Mobile Nodes. This may increase the cost of both access routers and mobile nodes and impact router performance. In addition, a simple change of the selection rules requires updating on all routers or mobile nodes.
- The above-mentioned references are exemplary only and are not meant to be limiting in respect to the resources and/or technologies available to those skilled in the art.
- The proposals in this invention comprise two aspects. First, we propose a policy based mechanism to select a possible target (new) access router for context transfer. Second, we describe two context transfer sequences for intra/inter domain handovers.
- The disclosed inventions will be described with reference to the accompanying drawings, which show important sample embodiments of the invention, wherein:
-
FIG. 1 is a reference system for transferring context of a mobile node between autonomous systems; -
FIG. 2 shows a context transfer message flow, according to an embodiment; and -
FIG. 3 shows a proactive handover embodiment. - An embodiment of the invention may perform policy based target router selection and context transfer. Embodiments may provide the following benefits:
- 1. Balance the functionalities between policy servers and access routers.
- 2. Centralize the critical information for admission control and operation of the network in the policy server. This makes updating and protecting the policy rules easier.
- 3. Routers do not need to expose and discover the capabilities of other routers because this information is readily available at policy servers. This effectively reduces the amount of messages exchanged over the network, saving valuable bandwidth.
- 4. Access routers are freed from target router selection process and most of context transfer process. Hence they can focus on performing their main duty, i.e., route internet protocol packets.
- 5. Access routers need not execute proxy application if their neighbors are running different technology.
- 6. In most wireless networks, the critical resource is radio spectrum. In the traditional mechanism where handover occurs prior to authorization, radio resources are allocated to the MN prior to authorization. If the MN failed the authentication and authorization process, then such radio resources have to be revoked. This could have repercussions such as the blocking of a legitimate user that could be handed over to this network otherwise. By performing an authorization prior to handover, we avoid this problem of blind radio resource allocation, thereby conserving use of the radio spectrum and associated radio resources.
- 7. Receiver driven approach for target selection helps in reducing denial of service attacks.
- A possible disadvantage is that the policy server may become a single point of failure. But proper network planning and incorporating Rservpool architecture for policy server can strengthen the availability and reliability of the policy server.
-
FIG. 1 shows the reference architecture for the context transfer framework and the target access router selection process. Access routers, e.g. source access router (AR) 101 anddestination access router 123 are policy targets. On boot up, the access routers may report their capabilities (QoS, Security etc) to apolicy server 105. The policy server (PS1) 105 then downloads the corresponding policy to theAR 101 according to the reported capabilities. Therefore thepolicy server 105 has all the information about anAR 101 capabilities in theadministrative domain 110. In addition thepolicy server 105 can retrieve information relating to thebase station 107 from the database of network management systems. The information includes, for example, which access router abase station 107 is connected to. - In
FIG. 1 , Mobile Node (MN) 151 is currently inAutonomous System AS1 110 and is communicating with a server in acore network 140. The static capabilities of theMN 151 are stored in a AAA server,e.g. AAA1 server 109. The policy server can retrieve this information from the AAA server of the MN home network. In the following, we describe the problem of inter domain handover which is more complicated than intra domain handovers. - For example, when the
MN 151 is in theAS1 110, the static capabilities of the MN 115 are retrieved byPS1 105 fromAAA1 server 109 and dynamic capabilities (or negotiated profiles) are kept with theaccess router AR1 107 that is currently serving theMN 151. When theMN 151 moves toward Autonomous System (AS2) 120, it receives identification information on a broadcast channel which may contain link layer information of a second base station (BS2) 127 or IP address ofAR2 120 or Autonomous System number associating some link local address or any combination information.MN 151 forwards the information toAR1 101. - An embodiment includes steps. The first step is the access router selection process where policy servers compute a list of possible access routers that may serve the
MN 151 and theMN 151 is informed of this list by the policy server in its own domain. The second step involves the actual context transfer. Details of the two steps are described in the following subsections. - 7.1 Selection of Access Routers Prior to Handover
- In this selection process, the policy server in the same domain as the candidate access routers computes the selection process.
- When the MN receives new identifiers from more than one base station through the broadcast channel, the MN forwards the information to the AR currently serving it,
e.g. AR1 101. The access router forwards it to the policy server,e.g. PS1 105. The minimal information which thepolicy server 105 expects is either the link layer identifier or Autonomous System (AS) number and link layer identifier. - 1. If
PS1 105 receives only link layer identifier, it checks first with the policy database to see whether that is simply an intra domain handover. If it is not an intra domain handover,PS1 105 checks with the neighboring AS defined in the policy database and forwards to their neighboring policy server. - 2. (or) It would be faster if the AS number is also sent in the broadcast channel by each base station this eliminates lots of processing. If AS number is sent then the policy server,
e.g. AR1 101, forwards the information to the respective policy server, e.g. PS2 126, along with the MN static capabilities (which it retrieved from AAA1 server 109). - 3. After receiving the information, the
PS2 125 determines whetherAS2 120 can potentially serve theMN 151. If yes,PS2 125 further computes the candidate access routers that will be able to serve theMN 151.PS2 129 then returns the computed access routers to PS1 105 (this is totally dependent on the topology of the AS). An algorithm for selecting the access routers is described in the next subsection. If the access router cannot serve the MN,PS2 125 simply sends a negative acknowledgement toPS1 105. - If
MN 151 has forwarded more than one access system identifiers to theAR1 101, thePS1 105 performs the above steps for each access system. FinallyPS1 105 sends a message toMN 151 informing all the possible (or authorized) ARs that may server theMN 151. - 7.1.1 An Algorithm for AR Selection within an AS
- An embodiment of an AR selection algorithm may be used by a policy server. It is based on a sequence of elimination processes.
- Given the set of reachable access routers for the mobile node
- 1. Eliminate those routers that cannot meet the mobile node's static capabilities.
- 2. Eliminate those routers whose traffic load is above a given threshold;
- 3. Use other operator defined rules to eliminate more routers.
- 4. Finally, when all rules are executed and if several routers survived the elimination processes forward all of them to the initiating PS.
- The order of the rules may be changed on the policy server. In general, a rule that is able to eliminate more routers should be evaluated before those that eliminate fewer routers. Some times it may be difficult to predict which rule will eliminate more routers. The insight can be gained with experience and a careful analysis of log data on policy servers.
- There is no need to reserve any resource at AR's during this process. PS can pre-authorize MN. The initiating PS after receiving the list of possible AR's has to periodically inform the MN's presence in their network.
- The second step in the above selection algorithm requires the policy server to have the knowledge of traffic load on the access routers. There are two possible ways a policy server may obtain the current load of access routers:
- If the policy server also performs admission controls, it knows the load on those routers naturally. If there is an admission control server, for example a bandwidth broker, the policy server can do a simple query of the server to get the load situation on those routers.
- Some networks may have no centralized admission control. For example, a network may operate on constrained routing where unused network resources are advertised globally within an administrative domain and each router makes admission control decision based on the advertised information. In this case, the policy server simply listens to the advertisement to know the unused resources on those routers. It then uses that information as an input to the above router selection algorithm.
- 7.2 Context Transfer Protocol
- When a MN is roaming in a network, it may receive signals from adjacent base stations. The MN can perform two types of handovers namely reactive and proactive. In the reactive case, the MN informs the new access router to pickup its context from the old access router. In the proactive case, the MN forwards the new access router's identities to the old access router and informs the old access router to push the context to the new access router.
- Preconditions
- 1. MN is initially in AS2 and is moving towards AS1. MN picks up more than one base station signals. With the target access router selection process described above, the MN is aware of the possible access routers who can satisfy its capabilities.
- 2. During the target access router selection process, each possible AS domain has pre-authorized the MN. Hence, context transfer is just a simple relocation of state information
-
FIG. 2 shows a context transfer message flow. - 1.
MN 251 that was roaming in theAS2 220 moves towardsAS1 210 and starts receiving the base station signal.MN 251 forwards the AS2:AR2 identity to the AR1, as aidentity packet 261. - 2.
AR1 201requests 262PS1 205 to prepare the context transfer request. - 3.
PS1 205 forwards the MN context request to theAS2 220 in a forwardedpacket 263. - 4.
AR2 223 sends the context related to the MN in amessage 264 toPS2 225. - 5.
PS2 225 adds to the context received from AS2 the static context about MN that is available atPS2 225. In addition,PS2 225 may collect other dynamic context from other network elements. For example,MN 251 may have a security context associated with a gateway inAS2 220.PS2 225 sends all these static and dynamic contexts toAR1 201 in a firstcross-network message 265. - 6.
AR1 201 extracts the context relevant toAR1 201 and forwards the rest of thecontext 266 to PS1. - 7.
PS1 205 extracts the static context and forwards the rest of the context 167 to related network elements, e.g., a security gateway that will reconstruct the security context.PS1 205 sends a context transfer complete message toAR2 223 in a secondcross-network message 267. - 8.
AR2 223 forwards the context transfercomplete message 268 toPS2 225 and finally context may be removed fromAS2 223. - The policy server may be totally kept in private address space due to security reasons and may not be accessible or visible from outside the autonomous system.
-
FIG. 3 shows a proactive handover embodiment. - Preconditions:
- 1.
MN 351 is initially in theAS1 310 and is moving towardsAS2 320.MN 351 picks up more than one base station signals. With the target access router selection process described above, theMN 351 is aware of the possible access routers who can satisfy its capabilities. - 2. During the target access router selection process, each possible AS domain has pre-authorized the
MN 351. Hence, context transfer is just a simple relocation of state information. - Context Transfer Message Flow:
- 1.
MN 351 that is currently roaming inAS1 310 decides to move toAS2 320 because the signal fromAS2 320 is stronger than that fromAS1 310. Under thissituation MN 351forwards 361 the AS2:AR2 identity to theAR1 301 and requests it to start the context transfer. - 2.
AR1 301 forwards the context toPS1 305 and informsPS1 305 to forward 362 the context toAR2 323. - 3.
PS1 305 adds to the context received fromAR1 301 the static context aboutMN 351 that is available atPS1 305. In addition,PS1 305 may collect other dynamic context from other network elements. For example,MN 351 may have a security context associated with a gateway.PS1 305 sends 363 all these static and dynamic contexts toAR2 323. - 4.
AR2 323 extracts the context relevant toAR2 323 andforwards 364 the rest of the context toPS2 329. - 5.
PS2 329 extracts the static context and forwards the rest of the context to related network elements, e.g., a security gateway that will reconstruct the security context.PS2 329 sends 365 a context transfer complete message toAR1 301. - 6.
AR1 301forwards 366 the context transfer complete message toPS1 305 and finally context is removed fromAS1 310. - Although described in the context of particular embodiments, it will be apparent to those skilled in the art that a number of modifications and various changes to these teachings may occur. Thus, while the invention has been particularly shown and described with respect to one or more preferred embodiments thereof, it will be understood by those skilled in the art that certain modifications or changes, in form and shape, may be made therein without departing from the scope and spirit of the invention as set forth above and claimed hereafter.
Claims (20)
1. A method comprising:
receiving all contexts from a first policy server, wherein said all contexts comprise a context added with a second context;
extracting a relevant context from said all contexts;
forwarding a rest of context to a second policy server to extract a static context; and
wherein the static context is forwarded to at least one network element, and wherein a context transfer complete message is transmitted to a first access router and forwarded to the first policy server.
2. The method of claim 1 , wherein the first policy server is a component of a first autonomous system, and the second policy server is a component of a second autonomous system.
3. The method of forwarding a context of claim 1 , further comprising forwarding a context transfer request from the first policy server to a second autonomous system wherein the first policy server is a component of a first autonomous system.
4. The method of forwarding a context of claim 3 , further comprising requesting the first policy server to send a context transfer request.
5. The method of forwarding a context of claim 4 , further comprising receiving an identity packet at the first access router.
6. A method comprising:
identifying, to a mobile node currently served by a first autonomous system, a list of at least one capable access router, wherein the identifying comprises
getting an identifier;
forwarding the identifier to a neighboring policy server; and
sending a message to the mobile node, said message having the list of at least one capable access router.
7. The method of claim 6 , further comprising:
determining if a second autonomous system can serve the mobile node; and
calculating the list of at least one access router that can serve the mobile node.
8. The method of claim 6 , wherein the getting of the identifier comprises getting a link layer identifier.
9. The method of claim 6 , wherein the getting of the identifier comprises getting an autonomous system number.
10. The method of claim 9 , further comprising:
determining if a second autonomous system can serve the mobile node; and
calculating the list of at least one access router that can serve the mobile node.
11. An apparatus comprising:
a receiver configured to receive all contexts from a first policy server, wherein said all contexts comprise a context added with a second context;
an extractor configured to extract a relevant context from said all contexts; and
a transmitter configured to forward a rest of context to a second policy server to extract a static context,
wherein the static context is forwarded to at least one network element, and wherein a context transfer complete message is transmitted to a first access router and forwarded to the first policy server.
12. The apparatus of claim 11 , further comprising a requester configured to request the first policy server to send a context transfer request.
13. An apparatus comprising:
an identifying unit configured to identify, to a mobile node currently served by a first autonomous system, a list of at least one capable access router, wherein the identifying unit comprises
a retrieving unit configured to retrieve an identifier;
an identifier transmitter configured to forward the identifier to a neighboring policy server; and
a message transmitter configured to send a message to the mobile node, said message having the list of at least one capable access router.
14. The apparatus of claim 13 , further comprising:
a determiner configured to determine if a second autonomous system can serve the mobile node; and
a calculator configured to calculate the list of at least one access router that can serve the mobile node.
15. The apparatus of claim 13 , wherein the retrieving unit is configured to retrieve a link layer identifier.
16. The apparatus of claim 13 , wherein the retrieving unit is configured to retrieve an autonomous system number.
17. A computer program, embodied on a computer readable medium, the computer program configured to perform the following:
receiving all contexts from a first policy server, wherein said all contexts comprise a context added with a second context;
extracting a relevant context from said all contexts; and
forwarding a rest of context to a second policy server to extract a static context,
wherein the static context is forwarded to at least one network element, and wherein a context transfer complete message is transmitted to a first access router and forwarded to the first policy server.
18. A computer program, embodied on a computer readable medium, the computer program configured to perform the following:
identifying, to a mobile node currently served by a first autonomous system, a list of at least one capable access router, wherein the identifying comprises
getting an identifier;
forwarding the identifier to a neighboring policy server; and
sending a message to the mobile node, said message having the list of at least one capable access router.
19. An apparatus comprising:
receiving means for receiving all contexts from a first policy server, wherein said all contexts comprise a context added with a second context;
extracting means for extracting a relevant context from said all contexts; and
transmitting means for forwarding a rest of context to a second policy server to extract a static context,
wherein the static context is forwarded to at least one network element, and wherein a context transfer complete message is transmitted to a first access router and forwarded to the first policy server.
20. An apparatus comprising:
identifying means for identifying, to a mobile node currently served by a first autonomous system, a list of at least one capable access router, wherein the identifying means comprises
retrieving means for retrieving an identifier;
identifier transmitting means for forwarding the identifier to a neighboring policy server; and
message transmitting means for sending a message to the mobile node, said message having the list of at least one capable access router.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/149,790 US20080212536A1 (en) | 2001-12-03 | 2008-05-08 | Policy based mechanisms for selecting access routers and mobile context |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US33693701P | 2001-12-03 | 2001-12-03 | |
US10/309,366 US7443835B2 (en) | 2001-12-03 | 2002-12-02 | Policy based mechanisms for selecting access routers and mobile context |
US12/149,790 US20080212536A1 (en) | 2001-12-03 | 2008-05-08 | Policy based mechanisms for selecting access routers and mobile context |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/309,366 Division US7443835B2 (en) | 2001-12-03 | 2002-12-02 | Policy based mechanisms for selecting access routers and mobile context |
Publications (1)
Publication Number | Publication Date |
---|---|
US20080212536A1 true US20080212536A1 (en) | 2008-09-04 |
Family
ID=23318373
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/309,366 Active 2025-10-21 US7443835B2 (en) | 2001-12-03 | 2002-12-02 | Policy based mechanisms for selecting access routers and mobile context |
US12/149,790 Abandoned US20080212536A1 (en) | 2001-12-03 | 2008-05-08 | Policy based mechanisms for selecting access routers and mobile context |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/309,366 Active 2025-10-21 US7443835B2 (en) | 2001-12-03 | 2002-12-02 | Policy based mechanisms for selecting access routers and mobile context |
Country Status (6)
Country | Link |
---|---|
US (2) | US7443835B2 (en) |
EP (1) | EP1451974B1 (en) |
AT (1) | ATE438978T1 (en) |
AU (1) | AU2002353270A1 (en) |
DE (1) | DE60233255D1 (en) |
WO (1) | WO2003049377A1 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090318155A1 (en) * | 2008-06-19 | 2009-12-24 | Fujitsu Limited | Base station apparatus, mobile station and wireless communication controlling method |
US20170034739A1 (en) * | 2013-12-19 | 2017-02-02 | Zte Corporation | Method and device for processing to share network resources, and method, device and system for sharing network resources |
CN107979572A (en) * | 2016-10-25 | 2018-05-01 | 鄂尔多斯市赛博购商贸有限公司 | The method of augmented reality service is provided and uses end |
Families Citing this family (99)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6360100B1 (en) | 1998-09-22 | 2002-03-19 | Qualcomm Incorporated | Method for robust handoff in wireless communication system |
US7295509B2 (en) | 2000-09-13 | 2007-11-13 | Qualcomm, Incorporated | Signaling method in an OFDM multiple access system |
US9130810B2 (en) | 2000-09-13 | 2015-09-08 | Qualcomm Incorporated | OFDM communications methods and apparatus |
US7974294B2 (en) * | 2001-12-14 | 2011-07-05 | Interdigital Technology Corporation | System for context transfer for wireless internet devices |
US8619718B2 (en) | 2002-04-05 | 2013-12-31 | Interdigital Technology Corporation | Method and apparatus for coordinating a radio network controller and node B resource management for high speed downlink packet data service |
US6862446B2 (en) * | 2003-01-31 | 2005-03-01 | Flarion Technologies, Inc. | Methods and apparatus for the utilization of core based nodes for state transfer |
US7668541B2 (en) | 2003-01-31 | 2010-02-23 | Qualcomm Incorporated | Enhanced techniques for using core based nodes for state transfer |
JP4217544B2 (en) * | 2003-06-05 | 2009-02-04 | 株式会社エヌ・ティ・ティ・ドコモ | Mobile communication system, control apparatus, and communication method |
US7493393B2 (en) | 2003-06-23 | 2009-02-17 | Nokia Corporation | Apparatus and method for security management in wireless IP networks |
DE602004009596T2 (en) * | 2003-09-12 | 2008-07-24 | Ntt Docomo Inc. | SAFE HANDOVER WITHIN A TERRITORY AND TERRITORY |
AU2003273866A1 (en) * | 2003-09-12 | 2005-04-06 | Docomo Communications Laboratories Europe Gmbh | Context transfer for seamless handover |
US7548525B2 (en) | 2003-10-18 | 2009-06-16 | Samsung Electronics Co., Ltd | System and method for providing handover of a mobile IP terminal in a wireless network |
EP1531645A1 (en) | 2003-11-12 | 2005-05-18 | Matsushita Electric Industrial Co., Ltd. | Context transfer in a communication network comprising plural heterogeneous access networks |
US7706325B2 (en) * | 2003-12-30 | 2010-04-27 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and system for handling context of data packet flows |
EP1703680A1 (en) * | 2004-01-07 | 2006-09-20 | Matsushita Electric Industrial Co., Ltd. | Communication system, mobile terminal and access router |
BRPI0506734A (en) * | 2004-01-07 | 2007-05-15 | Matsushita Electric Ind Co Ltd | communication system, mobile terminal, and access router |
US9137822B2 (en) | 2004-07-21 | 2015-09-15 | Qualcomm Incorporated | Efficient signaling over access channel |
US9148256B2 (en) | 2004-07-21 | 2015-09-29 | Qualcomm Incorporated | Performance based rank prediction for MIMO design |
WO2006011730A1 (en) * | 2004-07-28 | 2006-02-02 | Samsung Electronics Co., Ltd. | Handoff system and method between mobile communication network and wireless lan |
DE602004018848D1 (en) * | 2004-08-17 | 2009-02-12 | Nokia Corp | HANDOVER OF A MOBILE STATION |
EP1646189A1 (en) | 2004-10-06 | 2006-04-12 | Matsushita Electric Industrial Co., Ltd. | WLAN radio access network to UMTS radio access network handover with network requested packet data protocol context activation |
CN1898972B (en) * | 2004-12-17 | 2010-05-05 | 华为技术有限公司 | Method and system for maintaining conversation continuity |
CN101112059A (en) * | 2005-02-02 | 2008-01-23 | 松下电器产业株式会社 | Packet transfer method in communication network system and packet processing method in communication device constituting the system |
US9246560B2 (en) | 2005-03-10 | 2016-01-26 | Qualcomm Incorporated | Systems and methods for beamforming and rate control in a multi-input multi-output communication systems |
US9154211B2 (en) | 2005-03-11 | 2015-10-06 | Qualcomm Incorporated | Systems and methods for beamforming feedback in multi antenna communication systems |
US8446892B2 (en) | 2005-03-16 | 2013-05-21 | Qualcomm Incorporated | Channel structures for a quasi-orthogonal multiple-access communication system |
US9461859B2 (en) | 2005-03-17 | 2016-10-04 | Qualcomm Incorporated | Pilot signal transmission for an orthogonal frequency division wireless communication system |
US9520972B2 (en) | 2005-03-17 | 2016-12-13 | Qualcomm Incorporated | Pilot signal transmission for an orthogonal frequency division wireless communication system |
US9143305B2 (en) | 2005-03-17 | 2015-09-22 | Qualcomm Incorporated | Pilot signal transmission for an orthogonal frequency division wireless communication system |
EP1708423A1 (en) * | 2005-03-29 | 2006-10-04 | Matsushita Electric Industrial Co., Ltd. | Inter-domain context transfer using context tranfer managers |
US9184870B2 (en) | 2005-04-01 | 2015-11-10 | Qualcomm Incorporated | Systems and methods for control channel signaling |
US7920519B2 (en) * | 2005-04-13 | 2011-04-05 | Cisco Technology, Inc. | Transferring context information to facilitate node mobility |
US9036538B2 (en) | 2005-04-19 | 2015-05-19 | Qualcomm Incorporated | Frequency hopping design for single carrier FDMA systems |
US9408220B2 (en) | 2005-04-19 | 2016-08-02 | Qualcomm Incorporated | Channel quality reporting for adaptive sectorization |
US8879511B2 (en) | 2005-10-27 | 2014-11-04 | Qualcomm Incorporated | Assignment acknowledgement for a wireless communication system |
US8565194B2 (en) | 2005-10-27 | 2013-10-22 | Qualcomm Incorporated | Puncturing signaling channel for a wireless communication system |
US8611284B2 (en) | 2005-05-31 | 2013-12-17 | Qualcomm Incorporated | Use of supplemental assignments to decrement resources |
US8462859B2 (en) | 2005-06-01 | 2013-06-11 | Qualcomm Incorporated | Sphere decoding apparatus |
US8548487B2 (en) * | 2005-06-07 | 2013-10-01 | Nokia Corporation | Signaling for administrative domain change during location tracking |
US8599945B2 (en) | 2005-06-16 | 2013-12-03 | Qualcomm Incorporated | Robust rank prediction for a MIMO system |
US9179319B2 (en) | 2005-06-16 | 2015-11-03 | Qualcomm Incorporated | Adaptive sectorization in cellular systems |
GB2440100B (en) | 2005-06-21 | 2009-09-30 | Motorola Inc | Method and apparatus for reducing latency during wireless connectivity changes |
US9357586B2 (en) | 2005-06-21 | 2016-05-31 | Google Technology Holdings LLC | Method and apparatus to facilitate mobile station communications using internet protocol-based communications |
GB2440884B (en) | 2005-06-21 | 2010-01-06 | Motorola Inc | Method apparatus and system for establishing a direct route between agents of a sender node and a receiver node |
DE112006001656T5 (en) | 2005-06-21 | 2008-05-08 | Motorola, Inc., Schaumburg | System and method for providing a distributed virtual mobility agent |
DE112006001657B4 (en) | 2005-06-21 | 2017-05-24 | Motorola Mobility, Inc. ( N.D. Ges. D. Staates Delaware ) | Method and devices for device call and location update in a network |
CN101204099B (en) | 2005-06-21 | 2011-09-07 | 摩托罗拉移动公司 | Address resolution protocol based wireless access point |
CN101199219B (en) | 2005-06-21 | 2013-06-05 | 摩托罗拉移动公司 | Method and apparatus to facilitate communications using surrogate and care-of internet protocol addresses |
CN100450291C (en) * | 2005-07-11 | 2009-01-07 | 华为技术有限公司 | Method of establishing interface link |
US8885628B2 (en) | 2005-08-08 | 2014-11-11 | Qualcomm Incorporated | Code division multiplexing in a single-carrier frequency division multiple access system |
US20070041457A1 (en) | 2005-08-22 | 2007-02-22 | Tamer Kadous | Method and apparatus for providing antenna diversity in a wireless communication system |
US9209956B2 (en) | 2005-08-22 | 2015-12-08 | Qualcomm Incorporated | Segment sensitive scheduling |
US8644292B2 (en) | 2005-08-24 | 2014-02-04 | Qualcomm Incorporated | Varied transmission time intervals for wireless communication system |
US9136974B2 (en) | 2005-08-30 | 2015-09-15 | Qualcomm Incorporated | Precoding and SDMA support |
US9066344B2 (en) | 2005-09-19 | 2015-06-23 | Qualcomm Incorporated | State synchronization of access routers |
US9078084B2 (en) | 2005-12-22 | 2015-07-07 | Qualcomm Incorporated | Method and apparatus for end node assisted neighbor discovery |
US8509799B2 (en) | 2005-09-19 | 2013-08-13 | Qualcomm Incorporated | Provision of QoS treatment based upon multiple requests |
US8983468B2 (en) | 2005-12-22 | 2015-03-17 | Qualcomm Incorporated | Communications methods and apparatus using physical attachment point identifiers |
US20070064948A1 (en) * | 2005-09-19 | 2007-03-22 | George Tsirtsis | Methods and apparatus for the utilization of mobile nodes for state transfer |
US9736752B2 (en) | 2005-12-22 | 2017-08-15 | Qualcomm Incorporated | Communications methods and apparatus using physical attachment point identifiers which support dual communications links |
US8982835B2 (en) | 2005-09-19 | 2015-03-17 | Qualcomm Incorporated | Provision of a move indication to a resource requester |
US8982778B2 (en) | 2005-09-19 | 2015-03-17 | Qualcomm Incorporated | Packet routing in a wireless communications environment |
US9144060B2 (en) | 2005-10-27 | 2015-09-22 | Qualcomm Incorporated | Resource allocation for shared signaling channels |
US9210651B2 (en) | 2005-10-27 | 2015-12-08 | Qualcomm Incorporated | Method and apparatus for bootstraping information in a communication system |
US9225416B2 (en) | 2005-10-27 | 2015-12-29 | Qualcomm Incorporated | Varied signaling channels for a reverse link in a wireless communication system |
US8045512B2 (en) | 2005-10-27 | 2011-10-25 | Qualcomm Incorporated | Scalable frequency band operation in wireless communication systems |
US9225488B2 (en) | 2005-10-27 | 2015-12-29 | Qualcomm Incorporated | Shared signaling channel |
US8477684B2 (en) | 2005-10-27 | 2013-07-02 | Qualcomm Incorporated | Acknowledgement of control messages in a wireless communication system |
US9088384B2 (en) | 2005-10-27 | 2015-07-21 | Qualcomm Incorporated | Pilot symbol transmission in wireless communication systems |
US8693405B2 (en) | 2005-10-27 | 2014-04-08 | Qualcomm Incorporated | SDMA resource management |
US9172453B2 (en) | 2005-10-27 | 2015-10-27 | Qualcomm Incorporated | Method and apparatus for pre-coding frequency division duplexing system |
US8582509B2 (en) | 2005-10-27 | 2013-11-12 | Qualcomm Incorporated | Scalable frequency band operation in wireless communication systems |
US8582548B2 (en) | 2005-11-18 | 2013-11-12 | Qualcomm Incorporated | Frequency division multiple access schemes for wireless communication |
US8831607B2 (en) | 2006-01-05 | 2014-09-09 | Qualcomm Incorporated | Reverse link other sector communication |
US9083355B2 (en) | 2006-02-24 | 2015-07-14 | Qualcomm Incorporated | Method and apparatus for end node assisted neighbor discovery |
US8489096B2 (en) * | 2006-06-01 | 2013-07-16 | Nokia Corporation | Inter-access handover with access specific policy control functions |
WO2007147438A1 (en) * | 2006-06-21 | 2007-12-27 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and arrangements in a mobile ip network |
CN101523842A (en) * | 2006-08-09 | 2009-09-02 | 艾利森电话股份有限公司 | VRM selection |
US9155008B2 (en) | 2007-03-26 | 2015-10-06 | Qualcomm Incorporated | Apparatus and method of performing a handoff in a communication network |
US8634423B1 (en) * | 2007-04-13 | 2014-01-21 | Clearwire Ip Holdings Llc | Determining a quality-of-service prior to registering a wireless device |
US8090369B2 (en) * | 2007-05-01 | 2012-01-03 | Qualcomm Incorporated | User equipment capability handling in long-term evolution systems |
US8125954B2 (en) * | 2007-05-04 | 2012-02-28 | Futurewei Technologies, Inc. | System for FA relocation with context transfer in wireless networks |
US8830818B2 (en) | 2007-06-07 | 2014-09-09 | Qualcomm Incorporated | Forward handover under radio link failure |
US9094173B2 (en) | 2007-06-25 | 2015-07-28 | Qualcomm Incorporated | Recovery from handoff error due to false detection of handoff completion signal at access terminal |
US20090073943A1 (en) * | 2007-08-17 | 2009-03-19 | Qualcomm Incorporated | Heterogeneous wireless ad hoc network |
US9392445B2 (en) | 2007-08-17 | 2016-07-12 | Qualcomm Incorporated | Handoff at an ad-hoc mobile service provider |
US9398453B2 (en) | 2007-08-17 | 2016-07-19 | Qualcomm Incorporated | Ad hoc service provider's ability to provide service for a wireless network |
US8780856B2 (en) | 2007-09-18 | 2014-07-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Inter-system handoffs in multi-access environments |
GB2453525B (en) * | 2007-09-26 | 2011-11-02 | Motorola Inc | Radio resource management |
JP2010028675A (en) * | 2008-07-23 | 2010-02-04 | Fujitsu Ltd | Communicating system, base station, mobile terminal, and data transfer method |
JP5340397B2 (en) * | 2008-10-20 | 2013-11-13 | テレフオンアクチーボラゲット エル エム エリクソン(パブル) | Using cell ID and mask to find home node B gateway address |
US9179367B2 (en) | 2009-05-26 | 2015-11-03 | Qualcomm Incorporated | Maximizing service provider utility in a heterogeneous wireless ad-hoc network |
ES2807608T3 (en) * | 2009-10-29 | 2021-02-23 | Nokia Solutions & Networks Oy | Device and method with server that includes data replicated from the mobile device |
US8615241B2 (en) | 2010-04-09 | 2013-12-24 | Qualcomm Incorporated | Methods and apparatus for facilitating robust forward handover in long term evolution (LTE) communication systems |
US9801102B2 (en) | 2010-04-28 | 2017-10-24 | Samsung Electronics Co., Ltd. | Method and apparatus for handover using X2 interface based on closed subscriber group in mobile communication system |
CN102238656A (en) * | 2010-04-28 | 2011-11-09 | 北京三星通信技术研究有限公司 | Switching method for mobile communication system |
US8755385B2 (en) | 2012-05-03 | 2014-06-17 | Itron, Inc. | Authentication using DHCP services in mesh networks |
US9591525B2 (en) * | 2012-05-03 | 2017-03-07 | Itron Global Sarl | Efficient device handover/migration in mesh networks |
CN110636561B (en) * | 2018-06-21 | 2022-11-08 | 中兴通讯股份有限公司 | Information transmission method and device, storage medium and electronic device |
Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5442633A (en) * | 1992-07-08 | 1995-08-15 | International Business Machines Corporation | Shortcut network layer routing for mobile hosts |
US6091953A (en) * | 1997-08-06 | 2000-07-18 | Nortel Networks Limited | Distributed signaling message routing in a scalable wireless communication system |
US6151319A (en) * | 1996-11-15 | 2000-11-21 | Lucent Technologies Inc. | Connectionless message service using ATM routers |
US6272129B1 (en) * | 1999-01-19 | 2001-08-07 | 3Com Corporation | Dynamic allocation of wireless mobile nodes over an internet protocol (IP) network |
US6501741B1 (en) * | 1998-01-28 | 2002-12-31 | Nokia Mobile Phones Ltd. | Method supporting the quality of service of data transmission |
US6854014B1 (en) * | 2000-11-07 | 2005-02-08 | Nortel Networks Limited | System and method for accounting management in an IP centric distributed network |
US20050105491A1 (en) * | 2001-06-28 | 2005-05-19 | Nokia, Inc. | Protocol to determine optimal target access routers for seamless IP-level handover |
US7123598B1 (en) * | 2001-06-29 | 2006-10-17 | Nokia Inc. | Efficient QoS signaling for mobile IP using RSVP framework |
US7545754B2 (en) * | 2001-11-02 | 2009-06-09 | Ntt Docomo, Inc. | Geographically adjacent access router discovery and caching for mobile nodes |
US7848753B1 (en) * | 2001-04-04 | 2010-12-07 | Nortel Networks Limited | Context transfer systems and methods in support of mobility |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
AU6497698A (en) * | 1998-02-16 | 1999-08-30 | Nokia Telecommunications Oy | Method and system for performing handover in a mobile communication system |
AU6861100A (en) * | 1999-09-29 | 2001-04-30 | Nortel Networks Limited | Apparatus and method for routing aaa messages between domains of a network |
US6587680B1 (en) * | 1999-11-23 | 2003-07-01 | Nokia Corporation | Transfer of security association during a mobile terminal handover |
AU7236800A (en) * | 1999-12-21 | 2001-06-28 | Nortel Networks Limited | Utilizing internet protocol mobility messages and authentication, authorization and accounting messages in communication system |
CA2405044C (en) * | 2000-05-02 | 2007-01-23 | At&T Corp. | System and method for inter-domain mobility management |
CN1201534C (en) | 2000-05-22 | 2005-05-11 | 艾利森电话股份有限公司 | Application of controlling policy |
-
2002
- 2002-12-02 AU AU2002353270A patent/AU2002353270A1/en not_active Abandoned
- 2002-12-02 US US10/309,366 patent/US7443835B2/en active Active
- 2002-12-02 WO PCT/IB2002/005071 patent/WO2003049377A1/en not_active Application Discontinuation
- 2002-12-02 DE DE60233255T patent/DE60233255D1/en not_active Expired - Lifetime
- 2002-12-02 AT AT02788291T patent/ATE438978T1/en not_active IP Right Cessation
- 2002-12-02 EP EP02788291A patent/EP1451974B1/en not_active Expired - Lifetime
-
2008
- 2008-05-08 US US12/149,790 patent/US20080212536A1/en not_active Abandoned
Patent Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5442633A (en) * | 1992-07-08 | 1995-08-15 | International Business Machines Corporation | Shortcut network layer routing for mobile hosts |
US6151319A (en) * | 1996-11-15 | 2000-11-21 | Lucent Technologies Inc. | Connectionless message service using ATM routers |
US6091953A (en) * | 1997-08-06 | 2000-07-18 | Nortel Networks Limited | Distributed signaling message routing in a scalable wireless communication system |
US6501741B1 (en) * | 1998-01-28 | 2002-12-31 | Nokia Mobile Phones Ltd. | Method supporting the quality of service of data transmission |
US6272129B1 (en) * | 1999-01-19 | 2001-08-07 | 3Com Corporation | Dynamic allocation of wireless mobile nodes over an internet protocol (IP) network |
US6854014B1 (en) * | 2000-11-07 | 2005-02-08 | Nortel Networks Limited | System and method for accounting management in an IP centric distributed network |
US7848753B1 (en) * | 2001-04-04 | 2010-12-07 | Nortel Networks Limited | Context transfer systems and methods in support of mobility |
US20050105491A1 (en) * | 2001-06-28 | 2005-05-19 | Nokia, Inc. | Protocol to determine optimal target access routers for seamless IP-level handover |
US7123598B1 (en) * | 2001-06-29 | 2006-10-17 | Nokia Inc. | Efficient QoS signaling for mobile IP using RSVP framework |
US7545754B2 (en) * | 2001-11-02 | 2009-06-09 | Ntt Docomo, Inc. | Geographically adjacent access router discovery and caching for mobile nodes |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090318155A1 (en) * | 2008-06-19 | 2009-12-24 | Fujitsu Limited | Base station apparatus, mobile station and wireless communication controlling method |
US8359035B2 (en) * | 2008-06-19 | 2013-01-22 | Fujitsu Limited | Base station apparatus, mobile station and wireless communication controlling method |
US20170034739A1 (en) * | 2013-12-19 | 2017-02-02 | Zte Corporation | Method and device for processing to share network resources, and method, device and system for sharing network resources |
US9900804B2 (en) * | 2013-12-19 | 2018-02-20 | Zte Corporation | Method and device for processing to share network resources, and method, device and system for sharing network resources |
CN107979572A (en) * | 2016-10-25 | 2018-05-01 | 鄂尔多斯市赛博购商贸有限公司 | The method of augmented reality service is provided and uses end |
Also Published As
Publication number | Publication date |
---|---|
EP1451974B1 (en) | 2009-08-05 |
AU2002353270A1 (en) | 2003-06-17 |
US20030103496A1 (en) | 2003-06-05 |
EP1451974A4 (en) | 2007-05-02 |
ATE438978T1 (en) | 2009-08-15 |
EP1451974A1 (en) | 2004-09-01 |
US7443835B2 (en) | 2008-10-28 |
DE60233255D1 (en) | 2009-09-17 |
WO2003049377A1 (en) | 2003-06-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7443835B2 (en) | Policy based mechanisms for selecting access routers and mobile context | |
US20200287818A1 (en) | Optimization of packet transmission paths | |
US8719453B2 (en) | Inter-domain context transfer using context transfer managers | |
CA2554546C (en) | Methods and apparatus for the utilization of core based nodes for state transfer | |
US7127249B2 (en) | System and method for selecting a wireless serving mode | |
CN1224231C (en) | Candidate access router discovery | |
EP1124396B1 (en) | Mobility support for a correspondent node in a Mobile IP network | |
KR101097635B1 (en) | Context transfer in a communication network comprising plural heterogeneous access networks | |
US7460504B2 (en) | Base station methods and apparatus for establishing connections | |
KR20050103240A (en) | Method and system for improved handoff of a mobile device between wireless subnetworks | |
Ram Gopal et al. | Policy Based Access Router Selections and Context Transfers in Mobile IP Network | |
AU2002360554B2 (en) | System and method for selecting a wireless serving node |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |