WO2010037321A1 - 移动性管理方法、相关设备及通信系统 - Google Patents
移动性管理方法、相关设备及通信系统 Download PDFInfo
- Publication number
- WO2010037321A1 WO2010037321A1 PCT/CN2009/074065 CN2009074065W WO2010037321A1 WO 2010037321 A1 WO2010037321 A1 WO 2010037321A1 CN 2009074065 W CN2009074065 W CN 2009074065W WO 2010037321 A1 WO2010037321 A1 WO 2010037321A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- terminal
- context
- mobility management
- management entity
- registered
- Prior art date
Links
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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
- H04W4/08—User group management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
-
- 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/18—Service support devices; Network management devices
- H04W88/182—Network node acting on behalf of an other network entity, e.g. proxy
Definitions
- Mobility management method related equipment and communication system
- the present invention relates to the field of communications technologies, and in particular, to a mobility management method, related device, and communication system.
- the network side allocates a wireless coverage area called a paging area.
- a paging area a wireless coverage area
- the network side if the network needs to send signaling or user plane data to the terminal, a paging message is sent to the terminal within the range of the paging area; when the terminal moves out from the current paging area, it needs The network side is notified by initiating a location update request procedure, and the network side allocates a new paging area to the terminal.
- the inventor found in the process of implementing the present invention that when a large number of terminals in the same position and moving together in a consistent direction and speed are moved out from the current paging area, a location update request message is respectively initiated in a short time.
- the network is notified, and the network side determines the current location of the terminal according to the location update request message of the terminal.
- the network side receives a lot of location update request messages in a short period of time, which increases the processing load of the network.
- Embodiments of the present invention provide a mobility management method, a related device, and a communication system, which can reduce the number of location update requests of the entire system.
- a mobility management method including: Receiving a first location update request sent by the mobile agent MA;
- a mobility management device includes:
- a location update request receiving unit configured to receive a first location update request sent by the MA, and determine a mobile location unit, configured to determine the terminal and the location according to the first location update request and a binding relationship between the MA context and the terminal context Said MA - move.
- a mobility management device includes:
- An affiliate MA context establishing unit configured to establish a secondary MA context, and associate the attached MA context with an MA context on a MA registered mobility management entity;
- a binding unit configured to bind the terminal context to the affiliate MA context.
- a terminal comprising:
- a binding indication obtaining unit configured to acquire a binding indication indicating that the terminal is successfully bound to the MA
- a control unit configured to: after obtaining the binding indication that the terminal and the MA are successfully bound, The location update request is not sent.
- a mobile agent device comprising:
- An authentication request sending unit configured to send an authentication request to the network side, where the authentication request is used to request the network side to authorize the mobile agent capability;
- An authentication result receiving unit configured to receive an authentication result fed back by the network side
- an advertisement sending unit configured to send an announcement message carrying the authentication result, for the terminal to confirm that the mobile agent device has mobile agent capability.
- a communication system comprising: a mobility management entity registered by a terminal, a mobility management entity registered by the MA, wherein
- the mobility management entity that is registered by the terminal is configured to establish a secondary MA context, associate with the MA context on the mobility management entity registered by the MA, and bind the terminal context to the secondary MA context;
- the MA-registered mobility management entity is configured to establish an MA context, associate with a secondary MA context on the mobility management entity registered by the terminal, and receive a location update request sent by the MA; and determine, according to the location update request, Corresponding to the terminal context bound by the subsidiary MA context The terminal moves with the MA.
- the network side in the embodiment of the present invention binds the MA (Mobile Agent) context to the terminal context, and after receiving the location update request sent by the MA, the terminal that is bound to the MA also moves accordingly. Therefore, the terminal that does not need to be bound to the MA separately initiates the location update request message, and can also determine the mobile location of the terminal, thereby reducing the processing load of the network.
- MA Mobile Agent
- the terminal in the embodiment of the present invention controls not to send the location update request during the movement, so that the network side does not receive and process many location update requests in a short time.
- the message reduces the processing load on the network.
- FIG. 1 is a flowchart of a mobility management method according to Embodiment 1 of the present invention.
- FIG. 2 is a signaling diagram of a mobility management method according to Embodiment 2 of the present invention.
- FIG. 3 is a signaling diagram of a mobility management method according to Embodiment 3 of the present invention.
- Embodiment 4 is a signaling diagram of a mobility management method according to Embodiment 4 of the present invention.
- FIG. 5 is a signaling diagram of a MA to notify a binding terminal to perform rebinding according to an embodiment of the present invention
- FIG. 6 is a signaling diagram of a debinding process provided by an embodiment of the present invention
- FIG. 7 is a signaling diagram of a debinding process according to an embodiment of the present invention.
- FIG. 8 is a structural diagram of a mobility management apparatus according to Embodiment 5 of the present invention.
- FIG. 9 is a structural diagram of a mobility management apparatus according to Embodiment 6 of the present invention.
- FIG. 10 is a structural diagram of a terminal provided in Embodiment 7 of the present invention.
- FIG. 11 is a structural diagram of a mobile agent apparatus according to Embodiment 8 of the present invention.
- Embodiment 1 is a diagrammatic representation of Embodiment 1:
- a first embodiment of the present invention provides a mobility management method, including:
- the network side binds the MA context to the terminal context
- the network side may be a mobility management entity.
- the mobility management entity may be an MME (Mobile Management Entity, The mobility management entity); the location update request may be a TAU (Tracking Area Update) request.
- EPS evolved packet system
- MME Mobile Management Entity
- TAU Track Area Update
- the binding of the MA context to the terminal context in the network side can be implemented in two ways.
- the single-homing mode requires that the binding terminal and the MA must be registered to the same MME.
- the MA is registered on a different MME, and the MME registered by the MA obtains the terminal context from the MME registered by the terminal, and binds the terminal context to the MA context.
- the multi-homing mode allows the binding terminal and the MA to register with different MMEs.
- the MME that is registered by the MA establishes a context association with the MME that is registered by the terminal to indirectly bind the terminal to the MA.
- the network side Before the network side binds the MA context to the terminal context, the network side includes: the network side (which may be a mobility management entity registered by the MA) receives the authentication request sent by the MA for requesting the network side authorized mobile agent capability, and the MA The authentication is performed, and the authentication result is returned to the MA.
- the MA broadcasts the message, and the notification message carries the authentication result.
- the terminal confirms that the MA obtains the network authorization to provide the mobile agent according to the authentication result.
- the specific process can be implemented in the following two ways. The first method includes the following steps:
- the MA initiates an attach request message, where the attach request message is used as an authentication request, and the attach request message carries information requesting itself as a mobile agent.
- the MME After receiving the attach request message, the MME obtains the subscription data from the HSS (Home Subscriber Server) or the AAA server (Authentication, Authorization, Accounting Server, Authentication, Authorization, and Accounting Server). , certify the MA.
- HSS Home Subscriber Server
- AAA server Authentication, Authorization, Accounting Server, Authentication, Authorization, and Accounting Server.
- the MME After the MME successfully authenticates the MA, the MME returns an attach accept message to the MA, where the attach accept message carries the authentication result, and the authentication result includes the security parameter of the network authorization, and the security parameter includes: an authentication parameter for the terminal to perform legality authentication on the MA.
- the security parameter is delivered in the attach accept message.
- the main reason is that not only the network needs to authenticate the MA, but the subsequent terminal also authenticates the MA to verify that the MA has been authorized by the network to authorize its time period at a specific time.
- the area provides mobile agent services for a specific number of terminals.
- an announcement message is sent by a wireless signal within a specific range to notify The existence of the notification message includes: the ID of the MA, the GUTI (Globally Unique Temporary Identity) assigned by the network, the TA List assigned to the ⁇ ⁇ , the TA where the MA is currently located, the security parameters, and The capacity of the MA (the number of terminals the MA has served, the number of terminals that can be served, or the percentage of load).
- GUTI Globally Unique Temporary Identity
- the sending of the advertisement message by the MA in a specific range is that the MA wants the terminal in the specific range to receive the advertisement message, that is, the specific range is a range in which the terminal can perform binding movement with the MA.
- the MA sends an advertisement message by using a specially planned frequency band and format, and may also send an advertisement message by using a frequency band of the existing broadcast message of the mobile communication system, and the format of the advertisement message may also adopt an existing broadcast message.
- the above steps are to complete the authentication process of the MA through the attach process, or complete the authentication process of the MA through other processes, such as the TAU (Tracking Area Update) process, or complete the authentication process of the MA through the new process. Affects the implementation of the invention.
- the terminal enters the signal coverage area of the MA, receives the notification message, and confirms that it has been in the signal coverage area of the MA for a certain period of time, that is, confirms that it is stuck on the MA; the terminal ⁇ f ⁇ the security parameter in the notification message
- the MA is authenticated, and it is confirmed that the current MA is authorized by the network to provide the service of the mobile agent.
- the terminal and the device may be in the process of moving, in some cases, the terminal may be in a certain signal coverage area within a short period of time, and then the signal coverage of the device is removed, for example, installation.
- the terminal just outside the bus receives the notification message of the device. Since the terminal does not need to be bound to the terminal, the terminal needs to confirm that it has been in the specific time.
- the ⁇ 's signal coverage area can determine that it is following the ⁇ movement.
- the step further includes: selecting, by the terminal, an MA to perform subsequent binding according to the predetermined policy.
- the predetermined policy may be selected according to the signal strength of the MA to implement load sharing between the MAs; or, according to the load percentage in the announcement message broadcasted by the MA, the load-weighted MA is selected; or, according to the weight value of each MA (The weight value of the MA corresponds to the number of terminals that the MA is authorized to serve, and the number of terminals is small.
- the weight value is small, the number of terminals is large, the weight value is large, and the MA with a larger weight value is selected.
- the random selection may be selected according to the length of the glue time. Specifically, for example, a terminal is in the signal coverage area of the MA1. After 2 minutes, within 4 minutes of the signal coverage area of MA2, the terminal will select MA2 for subsequent binding.
- the second method includes the following steps:
- the network side pre-configures an asymmetric key including a public key and a private key.
- the asymmetric key is characterized in that the information encrypted by the private key can be opened only by the corresponding public key, and the information encrypted by the public key has only the corresponding private key. Can be opened.
- the private key held by the network side is not disclosed, and the public key is sent to each terminal.
- the public key on the network side can be burned in the smart card in the terminal, or distributed to the terminal by the network side during terminal attachment or TAU. Or notify the terminal by using a broadcast message sent by the base station.
- ⁇ 2 pre-configure an asymmetric key including a public key and a private key; ⁇ when registering with the network side, provide the configured public key to the registered ⁇ , for example, ⁇ send an authentication request to the ⁇ registered to it, Carrying the public key configured in the authentication request, confirming that the mobile agent service can be provided, encrypting the configured public key and MA ID with the private key configured by itself, and obtaining the first encrypted segment as the authentication result and sending it to MA.
- the T3 and the MA use the private key configured by the user to encrypt the ID of the MA, the current timestamp, and the authorization of the MA to obtain the second encrypted segment, and send an advertisement message, where the notification message includes: And the second encrypted segment.
- the terminal decrypts the first encrypted segment by using the public key configured on the network side, obtains the public key and the ID of the UI, and decrypts the second encrypted segment by using the public key configured by the MA to obtain the ID of the MA and the current timestamp.
- the terminal determines whether the ID of the MA in the first encrypted segment is the same as the ID of the MA in the second encrypted segment, and if yes, determines whether the difference between the current timestamp and the timestamp in the advertisement message exceeds a threshold, if No, confirm that the MA is authorized by the network to provide mobile agent services.
- the legality authentication method is adopted to ensure that the spoofed MA cannot be authorized by the network. Only the MA that has passed the legality authentication can obtain the authorization of the network and provide services for the terminal.
- the network side in the first embodiment of the present invention binds the MA (Mobile Agent) context to the terminal context, and after receiving the location update request sent by the MA, the terminal that is bound to the MA also moves accordingly. Therefore, the terminal that does not need to be bound to the MA separately initiates a location update request message, and can also determine the mobile location of the terminal, thereby reducing the processing load of the network.
- MA Mobile Agent
- a second embodiment of the present invention provides a mobility management method, in which a terminal is connected to an MA by using a single-sink mode, and the method includes:
- the terminal sends a TAU request message
- the TAU request message is a binding request
- the terminal can initiate the binding at any time after confirming that the user is stuck in the MA.
- the terminal in the embodiment of the present invention confirms the adhesion.
- the binding is initiated in the next TAU procedure after the MA (the next TAU may be the TAU triggered when the terminal moves out of the current tracking area list, or the TAU triggered by the timer that controls the periodic triggering of the TAU request on the terminal).
- the message carries the GUTI of the terminal, the ID of the MA selected by the terminal, and the addressing information of the MME registered by the MA, and a binding indication.
- the addressing information of the MME registered by the MA may be the GUTI of the MA, which is filled in the field for the radio access network route binding request message in the TAU request message, because the routing request message is used for the radio access network.
- the field is originally filled in the addressing information of the MME registered by the terminal, and the addressing information of the MME registered by the terminal may be the GUTI of the terminal, so the GUTI of the terminal needs to be placed in a new cell in the message, so that the wireless connection
- the network access will route the message to the MME1 registered by the MA according to the MME Code in the GUTI of the MA in the TAU request message.
- MME1 Mobility Management Entity
- MME1 finds the MA context through the GUTI of the MA, and checks whether the MA is authorized by the network to provide the mobile proxy service.
- the MME1 confirms whether the terminal is currently registered on itself or on another MME through the MME Code in the GUTI of the terminal. If the terminal is registered on another MME2 (such as MME2), the MME1 acquires the terminal context from the MME2, if the terminal is currently registered.
- MME1 directly searches for the pre-stored terminal context based on the GUTI of the terminal. (The figure shows the case where MME1 acquires the terminal context from MME2)
- MME1 associates the terminal context to the MA context. Thereafter, the MME1 knows that the binding terminal will move with the MA, and the MME1 returns the indication information of the binding success to the terminal, and the indication information of the binding success may be a TAU accept message. , to indicate that the binding was successful.
- the MME1 may not return the indication information of the binding success to the terminal. After transmitting the binding request, the terminal determines whether the response message from the MME1 is received within a specific duration. If the response message from the MME1 is not received, the MME1 considers that it has been bound. Success.
- the terminal After the terminal successfully connects to the MA, the terminal will not initiate a TAU request message when it moves between TAs.
- the TAU request message is a location update request message, but the terminal can still initiate the periodic TAU process and maintain the binding relationship with the MA on the network side through the periodic TAU procedure.
- the terminal may continue to receive the advertisement message of the MA during the binding, and obtain the new TA List allocated by the MME for the MA as the current TA List from the advertisement message.
- the terminal may also request the MME to allocate a TA List for itself when unbinding.
- the above steps implement the binding between the terminal and the MA, and the subsequent steps describe the location update of the terminal bound by the M A proxy.
- MA detects the broadcast signal sent by the base station, finds that it has moved out of the TA List range allocated by the MME for itself and enters a target tracking area TA2, and the MA initiates a TAU request message (the TAU request message is the first location update request); eNodeB The TAU request message is received, and the target tracking area identifier TAI2 is added to the TAU request message and sent. Assuming that the originally registered MME1 of the MA can still serve the tracking area TA2, the eNodeB routes the TAU request message to the MME1.
- the MME1 After receiving the TAU request message, the MME1 searches for the context of the MA, allocates a new TA List to the MA, and saves the MA list.
- the new TA List includes but is not limited to: TAI2, and the MME1 returns a TAU accept message to the MA.
- the message carries the new GUTI and TA List allocated for the MA. It may also include the number of terminals that have been bound to the MA, or the percentage of the load.
- the MME1 can reduce the number of TAs when the TA List is allocated to the MA, so as to reduce the size of the paging area.
- the number of location update messages of the terminal has been greatly reduced. If the number of TAs in the TA List allocated by the MME1 for the MA is reduced, the paging is performed. When the terminal is used, the broadcast message coverage of the base station is small, and radio resources can be saved. Binding with the MA, and sending the binding success indication information to the terminal, to indicate that the terminal does not initiate the TAU request when moving between the TAs, and after receiving the location update request sent by the MA bound to the multiple terminals on the network side, The terminal that is bound to the MA is also moved accordingly. Therefore, the terminal that does not need to be bound to the MA separately initiates a location update request message, and can also determine the mobile location of the terminal, thereby reducing the processing load on the network.
- Embodiment 3 Referring to FIG. 3, a third embodiment of the present invention provides a mobility management method, where a binding between a terminal and an MA is implemented in a multi-homing manner, and the method includes:
- the terminal initiates a TAU request message, and the TAU request message is a binding request, and the terminal may initiate a binding at any time after confirming that the user is attached to the MA.
- the message carries the ID of the MA selected by the GUTL terminal allocated by the network for the terminal, and the MA. GUTI and binding instructions.
- the terminal fills in its own GUTI in the "GUTI of the terminal" field in the TAU request message, and the MA is GUTI fills in the other fields of the message.
- the radio access network determines that the terminal is currently registered in the MME2 according to the MME Code included in the GUTI in the GUTI field of the TAU request message, and routes the TAU request message to the MME2.
- MME2 searches for the context of the terminal according to the GUTI of the terminal in the TAU request message, and determines whether it is the MME currently registered by the MA according to the ID of the MA or the GUTI of the MA. If not, it continues to determine whether there is an affiliate MA context, if any Then, the affiliate MA context is directly associated with the terminal context, and the counter for recording the number of bound terminals in the attached MA context is incremented by one; if there is no affiliate MA context, the secondary MA context is established, and the secondary MA context and the terminal are established. The context is associated and the counter used to record the number of bound terminals in the attached MA context is set to 1.
- the context of the MA is determined to be on the MME1, and a context association is established with the MME1. If it is determined that the MME2 is the MME currently registered by the MA, the MA context is directly bound to the terminal context.
- the manner in which the MME2 establishes a context association with the MME1 is: MME2 sends a context association request message to the MME1 to notify the MME1 that the affiliation MA context has been established on the MME2, where the affiliation MA context includes: the address and corresponding address of the MME1 registered by the MA
- the identifier of the MA context where the address of the MME1 registered by the MA may be obtained by querying a DNS (Domain Name System) server according to the MME Code included in the GUTI of the MA, where the context association request message includes: And the identifier of the corresponding MA context; wherein the identifier of the corresponding MA context is used by the MME1 to search for the MA context, for example, the GUTI of the MA; the MME1 finds the corresponding MA context according to the identifier of the corresponding MA context, and attaches the MA to the MME2.
- DNS Domain Name System
- the context information (including the address of MME2 and the identity of the corresponding affiliate MA context) is stored in the MA context and a context association response is sent to MME2. If there is an attached MA on the MME2 For example, the MME2 has established a context association with the MME1, and the MME2 does not need to send a context association request message to the MME1 every time there is a terminal binding. However, in the case that the association relationship has been established, the MME2 may periodically send a context association update message to the MME1, where the message includes: a status of the secondary MA context (ie, indicating whether there is an affiliate MA context on the MME2) and/or an attached MA context binding.
- a status of the secondary MA context ie, indicating whether there is an affiliate MA context on the MME2
- the M3 and the MME2 return the indication information of the binding success to the terminal, and the indication information of the binding success may be a TAU accept message to indicate that the binding is successful.
- the MME2 does not need to return the indication information of the binding success to the terminal. After the binding request is sent, the terminal considers that the binding is successful if the response message of the MME1 is not received.
- the terminal After the terminal is successfully bound, the terminal will no longer initiate a TAU request message when the terminal moves between the TAs.
- the TAU request message is a location update request message, but the terminal can still initiate a periodic TAU process and pass the periodic TAU process.
- the network side maintains the binding relationship with the MA.
- the terminal continues to receive the advertisement message of the MA during the binding, and obtains the new TA List allocated by the MME for the MA as the current TA List from the advertisement message.
- the terminal can also request the MME to allocate a TA List to itself when unbinding.
- the above steps implement the binding between the terminal and the MA.
- the subsequent steps describe the location update of the terminal bound by the MA proxy.
- the M4 and the MA detect the broadcast signal sent by the base station, and find that the MME1 has moved out of the TA List range allocated by the MME1 to enter a target tracking area TA2, and the MA initiates a TAU request message; the eNodeB receives the TAU request message, and joins the TAU request message.
- the target tracking area is sent after the TAI2 is identified. It is assumed that the originally registered MME1 of the MA can still serve the tracking area TA2, and the eNodeB routes the TAU request message to the MME1.
- M5 and MME1 After receiving the TAU request message, M5 and MME1 search for the context of the MA and allocate a new one for the MA.
- the TA List is saved in the MA context, and the new TA List includes but is not limited to: TAI2.
- MME1 confirms that the context association is established with other MMEs from the MA context. If the network is configured to page the terminal directly in the TA List by the network, the address of the associated MME and the identifier of the corresponding affiliated MA context are obtained from the MA context. The associated MME (such as MME2) sends 3 trace area update notifications. The message carries the identifier of the newly allocated TA List and the corresponding affiliated MA context. After receiving the message, the MME2 searches for the attached MA context according to the corresponding affiliated MA context identifier, and saves the new TA List in the attached In the context of the MA. If the terminal is not directly logged by the network in the TA List, but is transferred by the MA, it is not necessary to notify the MME 2 in this step to update the TA List in the attached context.
- M6 and MME2 return a 3 track area update response message to MME1.
- MME1 returns a TAU accept message to the MA, where the message carries the new GUTI, TA List, and the number of terminals that have been bound to the MA.
- the MME2 that is registered by the terminal associates the terminal context with the secondary MA context, and the MME2 registered by the terminal establishes a context association with the MME1 registered by the MA, binds the terminal to the MA, and sends the binding successfully to the terminal.
- the indication information is used to indicate that the terminal does not initiate a TAU request when moving between the TAs.
- the terminal that is bound to the MA is also moved accordingly. Therefore, the terminal that is not required to be bound to the MA separately initiates a location update request message, and can also determine the mobile location of the terminal, thereby reducing the processing load of the network.
- the two MMEs establish an association relationship by directly performing message interaction.
- an intermediate network may also be used. Meta-transfer to establish this relationship, no longer detailed.
- Embodiment 4 is a diagrammatic representation of Embodiment 4:
- the function of the MA is further enhanced in the fourth embodiment of the present invention, so that the MA has the function of the mobile base station, and the terminal performs the binding by using the MA, and the binding between the terminal and the MA is implemented by using the single-homing mode, and the method includes:
- the terminal initiates a TAU request to the MA, where the TAU request is a binding request, and the message carries the GUTI of the terminal, and the message may also carry the related information of the MA.
- the related information of the MA includes: the ID of the MA, and the TA where the MA is currently located. , MA's GUTI, etc. If the information about the MA is not carried in the TAU request, the MA adds the information about the MA to the TAU request.
- the MA sends a TAU request message to the MME1 registered by the MA.
- Whether the TAU request message still passes through the radio access network depends on the backhaul scheme selected by the MA. If the MA selects the wireless link of the current mobile communication network as the backhaul, the message needs to reach the network side through the radio access network; if the MA selects Other backhaul solutions, such as satellite, WLAN (none Line LAN), Worldwide Interoperability for Microwave Access (WiMax), does not need to go through the wireless access network.
- the MA selects the wireless link of the current mobile communication network as the backhaul, the message needs to reach the network side through the radio access network; if the MA selects Other backhaul solutions, such as satellite, WLAN (none Line LAN), Worldwide Interoperability for Microwave Access (WiMax), does not need to go through the wireless access network.
- WiMax Worldwide Interoperability for Microwave Access
- N3—N6 is the same as L2—.
- the terminal sends a TAU request to the MME1 through the MA, and the MME1 associates the terminal context with the MA context to implement binding of the terminal to the MA, and sends the binding success indication information to the terminal to indicate that the terminal is in the TA.
- the mobile terminal does not initiate a TAU request.
- the terminal that is bound to the MA also moves accordingly. Therefore, it does not need to be bound to the MA.
- the terminal separately initiates the location update request message, and can also determine the mobile location of the terminal, thereby reducing the processing load of the network.
- the fourth embodiment is based on the single-homed mode, and describes the manner in which the terminal performs the binding by using the MA, and may also be based on the multi-homing mode.
- the implementation manner includes: the terminal sends a binding request, and the MA or the access aggregation gateway connects the terminal.
- the binding request is routed to the mobility management entity registered by the terminal.
- the subsequent execution steps are the same as those of M3 and M7, and are not described here.
- the following situations are: After the MA is bound to the terminal, the binding relationship between the network-side paging binding terminal, the network side and the terminal is established, and the MA notification binding terminal re-binds and goes. The binding process is described.
- the network side After the terminal is bound to the MA, the network side considers that the current location of the MA is the current location of the terminal. Therefore, when paging the terminal, the terminal can be paged in the current tracking area of the MA (that is, the TA List allocated for the MA).
- the MME currently registered by the terminal may instruct the radio access network to directly page the terminal in the TA List of the MA, because the MA list is always stored in the MA context or the attached MA context in the MME.
- the MME may indicate the radio access network except the TA in the MA.
- the paging area in the list (the paging area in the TA list of the MA is the current paging area of the MA) sends a paging message, and also sends a paging message to the neighboring cell of the TA List of the MA to avoid the MA.
- the bound terminal When located at the edge of the paging area, the bound terminal may be in a neighboring cell outside the paging area, resulting in no paging message being received and the paging failure. 2.
- the terminal is bound to the MA by using the single-homing mode in the network, the paging terminal is performed by the MA.
- the MME1 that is registered by the MA determines to initiate paging to the terminal.
- the MME1 first sends a paging message to the MA, and the MA broadcasts the paging message within the coverage range of the UE.
- the terminal may notify the MA to stop broadcasting the paging message. And responding to the paging to the MME1 through the service request message.
- the paging terminal is performed through the MA.
- P1, MME2 determines the paging terminal, finds that the terminal context is associated with an affiliation MA context, obtains the address of the MME1 registered by the MA from the affiliation MA context, and sends a paging message to the MME1, where the message carries the terminal that needs to be paged. logo.
- the MME1 After receiving the paging message, the MME1 sends a paging message to the MA.
- P3, M A broadcast a paging message in their own coverage area to page the terminal.
- the terminal may notify the M A to stop broadcasting the paging message, and send a service request message to the MME2 to answer the paging.
- the paging message of the terminal may be required to be paged before being sent to the MA.
- the MA re-establishes the wireless connection; if the MA is connected to the network side by using a fixed access, for example, the MA is placed in a movie theater, a gym, etc., the paging message to the terminal can be directly sent to the MA.
- the terminal needs to send a service request message to the MME currently registered by the terminal (such as MME2).
- the MME2 After receiving the service request message, the MME2 establishes a signaling connection with the terminal through the radio access network to answer the service request message of the terminal. And the bearer between the terminal and the radio access network can be restored according to the request of the terminal.
- the terminal When the terminal establishes a signaling connection with the network, the terminal triggers the process of switching, TAU, and the like according to the same triggering condition as when the MA is not bound to the MA.
- the binding relationship between the terminal and the MA is as follows:
- the binding relationship between the terminal and the MA is cleared on both the terminal and the MME.
- the terminal can be in the signaling connection After the release, the Idle state is re-bound to the MA, and the new MA can also be selected for binding.
- the MA registration MME1 (because the MME1 acquires the terminal context, the MME1 is also the MME currently registered by the terminal) deletes the binding relationship between the MA context and the terminal context.
- the MME2 registered by the terminal deletes the binding relationship between the attached MA context and the terminal context, and decrements the counter for recording the number of bound terminals by 1. When the counter value is 0, the MA registration is obtained from the secondary MA context.
- the MME1 sends a notification message indicating that the context association is deleted to the MME1, where the notification message indicating that the context association is deleted includes: an identifier corresponding to the MA context, such as a GUTI of the MA; MME1 deletes the address of the MME2 from the MA context. Corresponding to the identifier of the attached MA context, to delete the context association with MME2.
- the terminal and the MME continue to maintain the binding relationship. In this case, even if the terminal and the network side establish a signaling connection, when the terminal detects that it has left the coverage area of the bound MA, it needs to initiate a debinding process to notify the network side that it has left the coverage of the MA. region.
- the MA notifies the binding terminal to re-bind.
- the TAU process is no longer initiated when moving between TAs, thereby saving the number of TAU request messages.
- the MME switchover has occurred due to the large mobile range of the MA
- the MME registered by the MA since the MME registered by the MA is changed, in the single-homing scheme, the context of all the terminals currently bound to the MA needs to be migrated to the new MME.
- some or all of the bonded terminals may also need to be migrated to the new MME (not necessarily the same as the new MME to which the MA is migrated), and since the MA registered MME has changed, the MA registration is new.
- the MA context association relationship between the MME and the MME registered by the terminal needs to be re-established.
- the network side first releases the binding relationship between all the terminals and the MA, and then notifies the MA, and the MA notifies the bound terminal to initiate the binding.
- the TAU process for rebinding, see Figure 5, the process specifically includes:
- MA moves out of the tracking area in the TA List, enters another TA, and initiates a TAU request message, which is a second location update request message. Since the originally registered MME of the MA cannot serve the new TA, the radio access network selects a new MME (ie, the new MME registered for the MA, MME6), and routes the TAU request message to the MME 6. Q2. The MME 6 sends an MA Context Request to the MME (the old MME registered by the MA, MME5) that the MA originally registered.
- the MME 5 After receiving the Context Request initiated by the MME 6, the MME 5 obtains the address of the associated MME and the identifier of the corresponding affiliated MA context from the context of the MA, and sends the identifier to the associated MME.
- a notification message indicating deletion of a context association the message includes: an identifier corresponding to the attached MA context.
- the associated MME (such as the old MME registered by the terminal, MME3), after receiving the notification message indicating that the MA context association is deleted, searches for the corresponding secondary MA context, clears the binding relationship between the secondary MA context and the terminal, and deletes the secondary MA context.
- the MME5 responds.
- the MME 6 registers with the HSS that it is the MME currently registered by the MA.
- the MME6 allocates a new GUTI and TA List to the MA, and returns a TAU accept message to the MA, where the message carries a newly allocated GUTI, TA List, and rebinding indication.
- the MA After receiving the TAU accept message, the MA confirms that the terminal needs to perform rebinding according to the rebinding indication, sends a rebinding advertisement message, and notifies all terminals bound to the MA to perform rebinding in the rebinding notification message. Process.
- the terminal After receiving the re-binding notification message, the terminal initiates a TAU request message, where the message carries the terminal's own GUTI, the ID of the MA, the GUTI of the MA (the MME6 is the newly allocated GUTI of the MA), and the binding indication.
- each terminal may randomly delay the initiation of the TAU request message for a period of time.
- the radio access network routes the TAU request message to the MME (MME3) originally registered by the terminal according to the GUTI of the terminal in the message, and if the MME3 cannot serve the terminal entering the new TA, the radio The access network selects an MME capable of serving the TA (such as MME4 as the newly registered MME of the terminal), and at this time, the TAU request message is routed to the MME 4. Q9.
- MME Mobility Management Entity
- the MME4 confirms that it is not the MME currently registered by the MA according to the ID of the MA or the GUTI of the MA, and determines whether the affiliate MA context exists. If yes, the affiliate MA context is directly associated with the terminal context; if the secondary MA context does not exist, An affiliate MA context is then established and the affiliate MA context is associated with the terminal context. Then, according to the GUTI of the MA, the context of the MA is determined on the MME6, and a context association is established with the MME6, where the processing of the rebinding procedure is the same as the processing of the initial binding.
- the MME4 returns a TAU accept message to the terminal, where the message carries the new GUTI that the MME4 is the terminal.
- the MA original registration MME (MME5) is the same MME as the MME (MME3) originally registered by the terminal, and the MA newly registers the MME (MME6). ) The same MME as the newly registered MME (MME4).
- MME 5 clears the binding relationship between the MA and the terminal, that is, clears the MA context and The relationship of the terminal context.
- MME4 establishes a binding relationship between the MA context and the terminal context.
- the MA is instructed by the terminal to re-bind, and the MA can be re-bound with the terminal when the MA performs MME handover. After the MME is switched, the network can still determine the terminal bound to the MA according to the movement of the MA. Also move together.
- FIG. 6 shows a terminal-triggered debinding process, which specifically includes:
- the terminal detects that the MA signal strength is lower than a predetermined threshold, or the MA broadcast message requires the terminal to be unbound, and the terminal initiates a TAU request message, where the TAU request is a debinding request, and the message carries the GUTI of the terminal,
- the ID of the MA, the unbinding indication, and the TAU request message is routed to MME2 (the MME currently registered by the terminal).
- the MME2 currently registered by the terminal and the MME1 currently registered by the MA are one.
- the MME deletes the binding relationship between the MA context and the context of the terminal. If it is in the multi-homing mode, the terminal currently registers the MME2 to confirm that the terminal context is associated with the secondary MA context, and decrements the counter by 1. When the counter value is 0, the information of the MME1 currently registered by the MA is obtained from the secondary MA context (the address of the MME1) And sending, to the MME1, a notification message indicating deletion of the context association; after receiving the notification message, the MME1 deletes the information of the MME2 and the identifier of the corresponding secondary MA context from the MA context. (The picture shows the multi-homing method)
- the notification message indicating that the context association is deleted may not be sent to the MME1 immediately, but wait for a period of time, for example, waiting for 30 seconds, to confirm whether the MME2 has a new terminal to be bound to the MA in a short time. If yes, no notification message indicating that the context association is deleted is sent, and if not, a notification message indicating that the context association is deleted is sent.
- R3 and MME2 newly allocate a GUTI and a TA List to the terminal, and send a TAU accept message to the terminal, where the message carries the newly allocated GUTI and TA List.
- the TAU process is initiated to notify the network location change as in the prior art.
- the terminal described above detects that the terminal has moved out of the coverage area of the MA and initiates the TAU process to bind.
- the binding relationship between the MA and the terminal is removed when the terminal moves out of the MA coverage area, so that the subsequent terminal can move like the existing one.
- the technology continues to trigger the TAU process, instead of determining the movement of the terminal based on the movement of the MA, ensuring that the network side can obtain the correct mobile location of the terminal.
- the MA may decide to stop the mobile agent service, such as the bus with the MA installed to the end point, or, when the MA ⁇ capacity decreases, decide to batch bind some of the currently bound terminals.
- 7 shows the un-binding process of the MA trigger, which specifically includes:
- the MA initiates a TAU request, and the TAU request carries an indication to bind all current terminals.
- the MA currently registers with the MME1 to receive the TAU request. If the MME1 is in the single-homed mode, the binding relationship between all the bound terminal contexts and the MA context is cleared. If the MME 1 re-allocates the TA List for the MA every time, and does not refresh the TA List in the terminal context, it also includes setting the TA List in all the bound terminal contexts to the current TA List of the MA.
- the MME1 obtains the information of the associated MME (the address of the MME and the identifier of the corresponding affiliated MA context) from the MA context, and the MME1 sends a notification message indicating the deletion of the context association to the associated MME (such as MME2), the message It carries the identifier corresponding to the attached MA context. If MME1 is MA every time When the TA list is re-allocated, the MME2 is not notified, and the notification message for deleting the context association further includes the current TA List of the MA.
- the MME 2 searches for the secondary MA context according to the identifier of the secondary MA context, sets the TA List in the terminal context bound to the secondary MA context to the current TA List of the MA, and clears the binding relationship between the secondary MA context and the terminal context, and deletes the attached MA context, replies to MME1. (The picture shows the multi-homing method)
- the MA is currently registered.
- the MME1 returns to the MA.
- the TAU accept message indicates that the MA is successfully bound.
- the message includes the current TA Listo of the MA.
- the MA sends, to the terminal, a debinding advertisement message, which is used to indicate that the binding relationship has been released, and the de-binding notification message includes the current TA List of the MA.
- the terminal After receiving the de-binding notification message, the terminal saves the current TA list of the MA in the notification message as its current TA List, and releases the binding state of the MA that is saved with the MA, that is, if the TA List is moved later.
- the TAU process is initiated to notify the network location change as in the prior art.
- the terminal may be located at a certain distance from the bound MA. In some rare cases, after the bound terminal receives the unbinding notification message from the MA, it may find that it has moved out of the tracking area of the current TA List of the MA. The range, that is, the TA List in the terminal context saved on the MME2 is inaccurate. At this time, the terminal initiates the TAU process to Exactly locate its own location on the MME2 and requests to re-assign the TA Listo to itself.
- the MA is bound to all the terminals as an example.
- the MA can also bind certain terminals.
- the MA only requests to bind the binding relationship of the terminal registered on a certain MME. The manner is similar to the above description, and details are not described herein again.
- the above-mentioned MA triggers the debinding, and the binding relationship between the MA and the terminal is cleared in batches when the MA cannot be stopped or stopped as a mobile agent, and each binding terminal does not need to initiate a debinding process separately, thereby saving The number of signalings bound.
- the foregoing embodiment of the present invention is that the terminal actively initiates a binding request message to request binding with the MA, which is only an implementation manner provided by the technical solution of the present invention.
- the technical solution of the present invention is not limited thereto, and may also be a network.
- the active binding of the MA to the terminal is performed. For example, after the authentication of the MA is successful on the network (that is, the authorized MA has the mobile proxy function), the terminal that is adjacent to the MA is bound to the MA and sent to the terminal after binding. Binding indication, indicating that the terminal does not initiate the TAU process when moving between TAs. The implementation of the invention is not affected.
- Embodiment 5 is a diagrammatic representation of Embodiment 5:
- a fifth embodiment of the present invention provides a mobility management apparatus, including:
- a binding unit 801 configured to bind the MA context to the terminal context
- the binding success indication sending unit 802 is configured to: after the binding unit 801 binds the MA context to the terminal context, send the indication information of the binding success to the terminal, to indicate that the terminal does not initiate the location update when the location is updated. Request
- a location update request receiving unit 803 configured to receive a location update request sent by the MA, and determine a mobile location unit 804, configured to: after the binding unit binds the MA context to the terminal context, according to the location update request, Modifying the MA context, and determining that the terminal moves with the MA.
- the mobility management device may not include the binding success indication sending unit 802, that is, after the terminal sends the binding request and does not receive the response message within a certain length of time, the terminal considers that the binding is successful, and does not require the mobility management device.
- a binding indication indicating that the MA is successfully bound to the terminal is sent to the terminal.
- the binding unit 801 includes:
- a determining unit configured to determine, after receiving the binding request message that the requesting terminal binds to the MA, whether the terminal is registered on itself;
- a terminal context obtaining unit configured to acquire a terminal context from the mobility management apparatus when the determination result of the determining unit is yes, and currently register from the terminal when the determining result of the determining unit is negative Obtaining a terminal context on the MME;
- the device further includes: a notification rebinding unit, configured to receive the second location update request sent by the MA And obtaining the MA context and the terminal context from the old mobility management entity that is registered by the MA, and instructing the old mobility management entity that is registered by the MA to clear the binding relationship between the MA context and the terminal context, and send the bearer to the MA.
- the indicated location update accept message; the binding unit 801 is configured to bind the MA context and the terminal context acquired from the old mobility management entity registered by the MA after receiving the binding request message that the requesting terminal binds to the MA .
- the device also includes:
- a paging indication unit 805 configured to: after the binding unit binds the MA context to the terminal context, when the paging terminal is required, instruct the radio access network to page the terminal in the current paging area of the MA; or And indicating that the radio access network is in the current paging area of the MA and the neighboring cell paging terminal of the current paging area; or sending a paging message carrying the terminal identifier to the MA to instruct the MA to page the terminal.
- the first de-binding unit 806 is configured to: after the binding unit binds the MA context to the terminal context, delete the binding relationship between the MA context and all terminal contexts when receiving the unbinding indication sent by the MA;
- the second de-binding unit 807 is configured to: after the binding unit binds the MA context to the terminal context, when receiving the debinding indication sent by the terminal, or establishing a signaling connection between the terminal and the network side,
- the binding request message receiving unit is configured to receive a binding request message that the requesting terminal binds to the MA
- the binding unit 801 is configured to: after receiving the binding request message that the requesting terminal binds to the MA, The MA context is bound to the terminal context.
- the binding unit of the mobility management apparatus in the fifth embodiment of the present invention binds the MA context to the terminal context, and the binding success indication sending unit instructs the terminal not to initiate a location update request when the location is updated, so as to reduce the processing load on the network side; After receiving the location update request sent by the MA, the terminal that is bound to the MA is also moved accordingly. Therefore, the terminal that is bound to the MA does not need to separately initiate a location update request message, and can also determine the mobile location of the terminal. .
- Another embodiment of the present invention provides a mobility management apparatus, including:
- a location update request receiving unit configured to receive a first location update request sent by the MA, and determine a mobile location unit, configured to determine the terminal and the location according to the first location update request and a binding relationship between the MA context and the terminal context Said MA - move.
- the binding relationship between the MA context and the terminal context includes: binding of the terminal context to the secondary MA context on the mobility management entity registered by the terminal, and the mobility management entity of the secondary MA context and the MA registration The association of the MA context.
- a sixth embodiment of the present invention provides a mobility management apparatus, where the mobility management apparatus is an MME that is registered by a terminal in a multi-homing mode, and includes:
- An affiliate MA context establishing unit 901 configured to establish a secondary MA context, and associate the secondary MA context with an MA context on a mobility management entity registered by the MA;
- the binding unit 902 is configured to bind the terminal context to the affiliate MA context.
- the binding success indication sending unit 903 is configured to: after establishing the secondary MA context, and binding the terminal context to the secondary MA context, send the indication information of the binding success to the terminal, to indicate that the terminal does not initiate the location when the location is updated. Update request.
- the mobility management device may not include the binding success indication sending unit 903, that is, after the terminal sends the binding request and does not receive the response message within a certain length of time, the terminal considers that the binding is successful, and does not require the mobility management device.
- a binding indication indicating that the MA is successfully bound to the terminal is sent to the terminal.
- the device also includes:
- the paging area list receiving unit 904 is configured to: after the secondary MA context establishing unit associates the secondary MA context with the MA context on the mobility management entity registered by the MA, receive the carried by the mobility management entity registered by the MA a location update request for a new paging zone list;
- a first paging unit 905 configured to: when the paging terminal is needed, instruct the radio access network to page the terminal in a current paging area listed in the new paging area list; or, indicate that the radio access network is in The current paging zone listed in the new paging zone list and its neighboring cell paging terminal.
- a second paging unit configured to: after the binding unit binds the terminal context to the auxiliary MA context, when the paging terminal is required, the mobility management entity registered by the MA sends a paging message to the MA to indicate the MA Paging terminal.
- the first deleting unit 906 is configured to: after the binding unit binds the terminal context to the auxiliary MA context, after receiving the debinding indication sent by the terminal, or after establishing a signaling connection between the terminal and the network side, The binding relationship between the context of the terminal and the attached MA context is deleted.
- the counter unit 907 is configured to: after the first deleting unit deletes the binding relationship between the context of the terminal and the MA attached context, reduce the counter for recording the number of bound terminals by one;
- the deletion context association notification sending unit 908 is configured to, when the counter value is 0, send a notification message indicating deletion of the context association to the mobility management entity registered by the MA.
- a deletion context notification message receiving unit 909 configured to receive a notification message sent by the mobility management entity registered by the MA to delete the context association;
- the second deleting unit 910 is configured to delete the terminal context and the attached MA context binding after deleting the notification message indicating that the context association is deleted, and delete the secondary MA context.
- the device may further include: a binding request message receiving unit, configured to receive a binding request message that the requesting terminal binds to the MA; and the binding unit is configured to receive a binding request message that is bound to the MA by the requesting terminal. After that, the terminal context is bound to the affiliate MA context.
- a binding request message receiving unit configured to receive a binding request message that the requesting terminal binds to the MA
- the binding unit is configured to receive a binding request message that is bound to the MA by the requesting terminal. After that, the terminal context is bound to the affiliate MA context.
- the affiliate MA context establishing unit in the mobility management entity in the sixth embodiment of the present invention establishes a secondary MA context for context association with the MME registered by the MA; the context binding unit binds the terminal context to the secondary MA context to implement MA and Binding of the terminal, and instructing the terminal not to initiate a location update request when the location is updated, to reduce the processing load on the network side; and after receiving the location update request sent by the MA, the terminal that is bound to the MA is also correspondingly Mobile, therefore, the terminal that is not bound to the MA does not need to separately initiate a location update request message, and can also determine the mobile location of the terminal.
- a seventh embodiment of the present invention provides a terminal, where the terminal is a mobile terminal, and the method includes: a binding indication acquiring unit 1001, configured to acquire indication information indicating that the terminal is successfully bound to the MA; and a control unit 1002, configured to After obtaining the indication information indicating that the terminal is successfully bound to the MA, the control does not send the location update request when the idle Idle state occurs.
- the binding indication obtaining unit 1001 is configured to receive indication information that is sent by the network side and indicates that the terminal is successfully bound to the M A.
- the terminal may further include: a binding request sending unit 1003, configured to send a binding request message that the requesting terminal binds to the MA
- the mobile terminal further includes:
- the notification message receiving unit 1004 is configured to receive, by the plurality of MAs, an advertisement message indicating that the corresponding MA has the mobility agent capability, and the selecting unit, configured to: after the notification message receiving unit receives the notification message of the multiple MAs, select the The MA is bound to the terminal.
- the terminal in the seventh embodiment of the present invention controls not to send the location update request during the movement, so that the network side does not receive and process many location updates in a short time. Requesting a message reduces the processing load on the network.
- an embodiment of the present invention provides a mobile agent device, including:
- the authentication request sending unit 1101 is configured to send an authentication request to the network side, where the authentication request is used to request the network side to authorize the mobile agent capability;
- the authentication result receiving unit 1102 is configured to receive an authentication result fed back by the network side;
- the advertisement sending unit 1103 is configured to send an advertisement message carrying the authentication result, so that the terminal confirms that the mobile agent device has mobile agent capability.
- the device also includes:
- the unbinding indication sending unit is configured to send a debinding indication to the mobility management entity where the MA is located.
- a rebinding indication receiving unit configured to receive a rebinding indication sent by a new mobility management entity registered by the MA;
- a re-binding notification message sending unit is configured to send a re-binding notification message.
- the paging unit is configured to receive a paging message that carries the terminal identifier sent by the MA-registered mobility management entity, and pages the terminal according to the paging message.
- the mobile agent device provided in Embodiment 8 of the present invention, it can act as a mobile agent of the terminal and act as a proxy terminal.
- the ninth embodiment of the present invention provides a communication system, including: an MME registered by a terminal, and an MME registered by the MA, where
- a mobility management entity that is registered by the terminal, configured to establish a secondary MA context, associate with an MA context on the mobility management entity registered by the MA, and bind the terminal context to the secondary MA context;
- a MA-registered mobility management entity configured to establish an MA context, associate with a secondary MA context on a mobility management entity registered by the terminal, and receive a location update request sent by the MA; and determine, according to the location update request, The terminal corresponding to the terminal context bound to the attached MA context is moved with the MA.
- the MA context is associated with the secondary MA context
- the terminal context is bound to the secondary MA context, so as to bind the MA context to the terminal context, and after receiving the location update request sent by the MA,
- the terminal bound to the MA also moves accordingly. Therefore, the terminal that does not need to be bound to the MA separately initiates a location update request message, and can also determine the mobile location of the terminal, thereby reducing the processing load on the network.
- a person skilled in the art can understand that all or part of the steps of implementing the above embodiments can be completed by a program to instruct related hardware, and the program can be stored in a computer readable storage medium, for example, a read only memory. , disk or CD, etc.
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Description
移动性管理方法、 相关设备及通信系统
本申请要求于 2008 年 9 月 27 日提交中国专利局、 申请号为 200810161460.7、 发明名称为 "移动性管理方法、 相关设备及通信系统" 的中 国专利申请的优先权, 其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域,特别涉及一种移动性管理方法、相关设备及通 信系统。
背景技术
移动通信系统中,在终端附着到网络中后, 网络侧会给终端分配一个无线 覆盖范围, 称为寻呼区。 当终端释放与网络侧的连接时, 如果网络需要发送信 令或者用户面数据给终端, 则会在这个寻呼区的范围内向终端发送寻呼消息; 当终端从当前寻呼区移出时, 需要通过发起一个位置更新请求流程通知网络 侧, 网络侧会为终端分配新的寻呼区。
显然, 终端移动的越快, 其发起位置更新请求就越频繁, 而人自身的移动 速度和范围都是有限的,要想以较快的速度在大范围内移动,一般要借助交通 工具, 如公共汽车、 地铁、 火车和轮船等, 在交通工具上的所有终端都以一致 的方向和速度进行移动。
在某些场合下, 如游行、 示威, 也可能出现大量步行的人群一起移动的情 况。
发明人在实现本发明的过程中发现: 当大量处于同一位置, 以一致的方向 和速度一起移动的终端在从当前寻呼区移出时,会在很短的时间内分别发起位 置更新请求消息以通知网络, 网络侧根据终端的位置更新请求消息,确定终端 的当前位置, 由于网络侧在很短的时间内会收到很多位置更新请求消息,加重 了网络的处理负担。
发明内容
本发明实施例提供一种移动性管理方法、相关设备及通信系统, 能够减少 系统整体的位置更新请求数量。
有鉴于此, 本发明实施例提供:
一种移动性管理方法, 包括:
接收移动代理 MA发送的第一位置更新请求;
根据所述第一位置更新请求和 MA上下文与终端上下文的绑定关系, 确定 所述终端与所述 MA—起移动。
一种移动性管理装置, 包括:
位置更新请求接收单元, 用于接收 MA发送的第一位置更新请求; 确定移动位置单元, 用于根据所述第一位置更新请求和 MA上下文与终端 上下文的绑定关系, 确定所述终端与所述 MA—起移动。
一种移动性管理装置, 包括:
附属 MA上下文建立单元, 用于建立附属 MA上下文, 将所述附属 MA上下 文与 MA注册的移动性管理实体上的 MA上下文关联;
绑定单元, 用于将终端上下文与所述附属 MA上下文绑定。
一种终端, 包括:
绑定指示获取单元, 用于获取表示所述终端与 MA绑定成功的绑定指示; 控制单元, 用于在获取到表示所述终端与 MA绑定成功的绑定指示后, 在 移动时控制不发送位置更新请求。
一种移动代理装置, 包括:
认证请求发送单元, 用于向网络侧发送认证请求, 所述认证请求用于请求 网络侧授权移动代理能力;
认证结果接收单元, 用于接收网络侧反馈的认证结果;
通告发送单元, 用于发送携带所述认证结果的通告消息, 以供终端确认所 述移动代理装置具有移动代理能力。
一种通信系统, 包括: 终端注册的移动性管理实体, MA注册的移动性管 理实体, 其中,
所述终端注册的移动性管理实体, 用于建立附属 MA上下文, 与 MA注册 的移动性管理实体上的 MA上下文关联, 并将终端上下文与附属 MA上下文绑 定;
所述 MA注册的移动性管理实体, 用于建立 MA上下文, 与终端注册的移 动性管理实体上的附属 MA上下文关联, 接收所述 MA发送的位置更新请求; 根据所述位置更新请求, 确定与所述附属 MA上下文绑定的终端上下文所对应
的终端与所述 MA—起移动。
本发明实施例中的网络侧通过将 MA ( Mobile Agent, 移动代理)上下文 与终端上下文绑定, 在接收到 MA发送的位置更新请求后, 认为与 MA绑定的 终端也进行了相应的移动, 因此, 不需要与 MA绑定的终端分别发起位置更新 请求消息, 也能确定终端的移动位置, 减轻了网络的处理负担。
本发明实施例中的终端在获取到表示终端与 MA绑定成功的指示信息后, 在移动时控制不发送位置更新请求,以使网络侧不会在很短时间内接收并处理 很多位置更新请求消息, 减轻了网络的处理负担。
附图说明
图 1是本发明实施例一所提供的移动性管理方法流程图;
图 2是本发明实施例二所提供的移动性管理方法信令图;
图 3是本发明实施例三所提供的移动性管理方法信令图;
图 4是本发明实施例四所提供的移动性管理方法信令图
图 5是本发明实施例所提供的 MA通知绑定终端进行重新绑定的信令图; 图 6是本发明实施例所提供的去绑定流程信令图;
图 7是本发明实施例所提供的去绑定流程信令图;
图 8是本发明实施例五所提供的移动性管理装置结构图;
图 9是本发明实施例六所提供的移动性管理装置结构图;
图 10是本发明实施例七所提供的终端结构图;
图 11是本发明实施例八所提供的移动代理装置结构图。
具体实施方式
实施例一:
参阅图 1 , 本发明实施例一提供一种移动性管理方法, 包括:
网络侧将 MA上下文与终端上下文绑定;
接收所述 MA发送的位置更新请求;
根据所述位置更新请求和 MA上下文与终端上下文的绑定关系, 确定所述 终端与所述 MA—起移动。
上述网络侧可以是移动性管理实体, 在 EPS ( evolved packet system, 演进 的分组系统)中, 该移动性管理实体可以是 MME ( Mobile Management Entity,
移动性管理实体); 该位置更新请求可以是 TAU ( Tracking Area Update, 跟踪 区更新)请求。 后面实施例以 EPS系统为例描述本发明方案。
其中, 网络侧将 MA上下文与终端上下文绑定可以有两种方式实现, 单宿 方式和多宿方式,单宿方式要求绑定终端和 MA必须注册到同一个 MME上,在 绑定时如果终端和 MA注册在不同的 MME上,由 MA注册的 MME向终端注册的 MME获取终端上下文, 进行终端上下文与 MA上下文的绑定; 多宿方式则允许 绑定终端和 M A注册到不同的 MME上, 通过 M A注册的 MME与终端注册的 MME建立上下文关联以间接实现终端与 MA的绑定,后续实施例会详细描述这 两种实现方式。
其中,在网络侧将 MA上下文与终端上下文绑定之前,还包括: 网络侧(可 以是 MA注册的移动性管理实体 )接收 MA发送的用于请求网络侧授权移动代 理能力的认证请求,对 MA进行认证, 向 MA返回认证结果; MA广播通告消息, 所述通告消息中携带所述认证结果; 终端根据所述认证结果, 确认 MA得到网 络授权可以提供移动代理。其具体过程可以有如下两种方式实现, 第一种方式 包括如下步骤:
51、 MA发起附着请求消息, 该附着请求消息作为认证请求, 该附着请求 消息中携带请求自己作为移动代理的信息。
52、 MME接收到附着请求消息后, 从 HSS ( Home Subscriber Server, 归属 用户月良务器) 或者 AAA月良务器 ( Authentication , Authorization , Accounting Server, 鉴权、 授权、 计费服务器)获取签约数据, 对 MA进行认证。
53、 MME在对 MA认证成功后, 向 MA返回附着接受消息, 该附着接受消 息中携带认证结果, 认证结果包括网络授权的安全参数, 安全参数包括: 供终 端对 MA进行合法性认证的认证参数、 授权 MA提供移动代理服务的时间段、 授权 MA提供移动代理服务的区域(例如 MA可以服务的 TA ( Tracking Area, 跟踪区) 列表)、 授权 MA提供移动代理服务的终端数量。
该步骤中在附着接受消息中下发安全参数主要是考虑到不仅网络要对 MA 进行认证, 后续终端也要对 MA进行认证, 以验证 MA已经得到网络的授权, 授权其在特定时间的时间段、 区域为特定数量的终端提供移动代理服务。
54、 MA注册完成后, 在特定范围内通过无线信号发送通告消息, 以通告
自己的存在, 通告消息中包括: MA的 ID、 网络为 MA分配的 GUTI ( Globally Unique Temporary Identity , 全球唯一临时标识符 )、 ΜΜΕ为 Μ Α分配的 TA List、 MA当前所在的 TA、 安全参数和 MA的容量(MA已经服务的终端数、还可以服 务的终端数, 或者负荷百分比)。
其中, MA在特定范围内发送通告消息是 MA希望该特定范围内的终端能 够接收到通告消息, 即该特定范围是终端可以与 MA进行绑定移动的范围。
该步骤中 MA发送通告消息可以是通过专门规划的频段和格式发送通告消 息,也可以利用移动通信系统现有的广播消息的频段发送通告消息, 其通告消 息的格式也可以采用现有的广播消息的格式并在消息中增加特有的参数, 如 MA的 ID等。
上述步骤是通过附着流程完成 MA的认证过程, 也可以通过其他流程, 例 如 TAU ( Tracking Area Update, 跟踪区更新) 流程完成 MA的认证过程, 也可 以通过新增流程完成上述 MA的认证过程, 不影响本发明的实现。
S5、 终端进入 MA的信号覆盖区域, 接收到通告消息, 并确认自己特定时 长内一直处于该 MA的信号覆盖区域内, 即确认自己粘连在 MA上; 终端^ f艮据 通告消息中的安全参数对 MA进行认证, 确认当前 MA得到网络授权可以提供 移动代理的服务。
由于终端和 ΜΑ^艮可能都处于移动过程中, 在某些情况下可能是 4艮短的时 间内终端处于某个 ΜΑ的信号覆盖区域内, 然后就离开了该 ΜΑ的信号覆盖范 围, 例如安装了 ΜΑ的公共汽车行驶到一个终端附近时, 恰好位于公共汽车外 面的终端接收到该 ΜΑ的通告消息, 由于这种情况下终端不需要和 ΜΑ绑定, 所以需要终端确认自己特定时长内一直处于该 ΜΑ的信号覆盖区域内才能判断 自己在跟随该 ΜΑ移动。
在一些大型的交通工具上,为了服务于大量的终端,可能安装有多个 ΜΑ。 如果该步骤中终端在特定时长内同时接收到多个 MA的通告消息, 该步骤还包 括: 终端根据预定的策略, 选择一个 MA进行后续的绑定。 其中, 预定的策略 可以是根据 MA的信号强度进行选择, 以实现 MA之间的负荷分担; 或者, 根 据 MA广播的通告消息中的负荷百分比选择负荷轻的 MA; 或者, 根据各 MA的 权重值(MA的权重值与 MA被授权服务的终端数量相对应, 终端数量少, 则
权重值小, 终端数量多, 则权重值大)选择权重值比较大的 MA; 又或者, 随 机选择等, 也可以根据粘连时间长度进行选择, 具体的, 比如一个终端处于 MA1的信号覆盖区域内 2分钟, 处于 MA2的信号覆盖区域内 4分钟, 则该终端 会选择 MA2进行后续的绑定。
第二种方式包括如下步骤:
Tl、 网络侧预先配置包括公钥和私钥的非对称密钥, 非对称密钥的特点 是使用私钥加密的信息只有对应的公钥才能打开,使用公钥加密的信息只有对 应的私钥才能打开。 网络侧持有的私钥不公开, 将公钥发送给各终端, 可以将 网络侧的公钥烧录在终端中的智能卡中,也可以在终端附着或者 TAU过程中由 网络侧分发给终端, 或者通过基站发送的广播消息通知终端。
Τ2、 ΜΑ预先配置包括公钥和私钥的非对称密钥; ΜΑ向网络侧注册时, 将 ΜΑ所配置的公钥提供给 ΜΑ注册的 ΜΜΕ, 比如, ΜΑ向其注册的 ΜΜΕ发送 认证请求, 在认证请求中携带 ΜΑ所配置的公钥, ΜΜΕ确认 ΜΑ能够提供移动 代理服务后, 用自己配置的私钥加密 ΜΑ所配置的公钥和 MA ID, 得到第一加 密段作为认证结果并发送给 M A。
T3、 MA使用自己配置的私钥对 MA的 ID、 当前的时间戳, 网络给 MA的授 权等信息进行加密, 得到第二加密段, 并发送通告消息, 该通告消息中包括: 第一加密段和第二加密段。
T4、 终端利用网络侧配置的公钥解密第一加密段, 得到 ΜΑ所配置的公钥 和 ΜΑ的 ID, 利用 MA所配置的公钥解密第二加密段, 得到 MA的 ID和当前的时 间戳,终端判断第一加密段中的 MA的 ID与第二加密段中的 MA的 ID是否相同, 如果是, 判断所述当前时间戳和所述通告消息中的时间戳之差是否超过阈值, 如果否, 确认 MA得到网络授权, 能够提供移动代理服务。
通过如上的合法性认证方式, 确保仿冒的 MA无法得到网络的授权, 保证 只有经过合法性认证的 MA才能得到网络的授权, 为终端提供服务。
本发明实施例一中的网络侧通过将 MA ( Mobile Agent, 移动代理)上下 文与终端上下文绑定, 在接收到 MA发送的位置更新请求后, 认为与 MA绑定 的终端也进行了相应的移动, 因此, 不需要与 MA绑定的终端分别发起位置更 新请求消息, 也能确定终端的移动位置, 减轻了网络的处理负担。
实施例二:
参阅图 2, 本发明实施例二提供一种移动性管理方法, 该方法中采用单宿 方式实现终端与 MA的绑定, 该方法包括:
Ll、 终端发送 TAU请求消息, 该 TAU请求消息是绑定请求, 终端可以在确 认自己粘连在 MA后任何时机发起绑定, 作为一个较优的实施方案, 本发明实 施例的终端在确认自己粘连在 MA后的下一个 TAU流程中发起绑定(该下一个 TAU可以是终端移出当前跟踪区列表时所触发的 TAU,或者终端上控制周期性 触发 TAU请求的定时器超时所触发的 TAU )。 该消息中携带终端的 GUTI、 终端 选择的 MA的 ID和 MA注册的 MME的寻址信息以及绑定指示。 其中 MA注册的 MME的寻址信息可以是 MA的 GUTI, 其填写在 TAU请求消息中的用于无线接 入网路由绑定请求消息的字段内,由于用于无线接入网路由绑定请求消息的字 段原来是填写终端注册的 MME的寻址信息的, 其终端注册的 MME的寻址信息 可以是终端的 GUTI, 因此终端的 GUTI需要放在消息中一个新增的信元中, 这 样无线接入网会根据该 TAU请求消息中 MA的 GUTI中的 MME Code将消息路 由到 MA所注册的 MME1。
L2、 MME1 ( Mobility Management Entity, 移动性管理实体)通过 MA的 GUTI查找到 MA上下文, 检查该 MA是否得到网络的授权提供移动代理服务。 MME1通过终端的 GUTI中的 MME Code确认终端当前注册在自己上还是注册 在其他 MME上,如果终端注册在其他 ^1^^上(比如 MME2 ),则 MME1从 MME2 获取终端上下文, 如果终端当前注册在自己上面, 则 MME1直接^ f艮据终端的 GUTI查找预存的终端上下文。 (图中所示为 MME1从 MME2获取终端上下文的 情况)
L3、 MME1将终端上下文关联到 MA上下文, 此后, MME1知道后续该绑 定终端将和 MA—起移动, MME1向终端返回绑定成功的指示信息, 该绑定成 功的指示信息可以是 TAU接受消息, 以指示绑定成功。
其中, MME1也可以不用向终端返回绑定成功的指示信息, 终端在发送绑 定请求后, 判断特定时长内是否收到来自 MME1的响应消息, 如果未收到 MME1的响应消息, 就认为已绑定成功。
终端在绑定 MA成功后, 终端在 TA间移动时, 将不再发起 TAU请求消息,
该 TAU请求消息是位置更新请求消息,但此时终端可以仍然发起周期性 TAU流 程并通过周期性 TAU流程在网络侧维持与 MA的绑定关系。 并且, 终端在绑定 期间可以继续接收 MA的通告消息, 从通告消息中获得 MME为 MA分配的新的 TA List作为自己的当前的 TA List。 当然, 终端也可以在去绑定时再向 MME请 求为自己分配 TA List。
以上步骤实现了终端与 MA的绑定, 后续步骤描述 M A代理绑定的终端进 行位置更新。
L4、 MA检测基站发送的广播信号,发现自己已经移出 MME为自己分配的 TA List范围而进入一个目标跟踪区 TA2, MA发起 TAU请求消息(此时 TAU请 求消息为第一位置更新请求); eNodeB接收该 TAU请求消息, 并在该 TAU请求 消息中加入目标跟踪区标识 TAI2后发送。 假设 MA原来注册的 MME1仍然能够 为跟踪区 TA2服务, 则 eNodeB将 TAU请求消息路由到 MME1。
L5、 MME1接收到 TAU请求消息后, 查找 MA的上下文, 为 MA分配新的 TA List并保存在 M A上下文中, 该新的 TA List包括但不仅限于: TAI2, MME1 向 MA返回 TAU接受消息, 该消息中携带为 MA分配的新的 GUTI、 TA List, 还 可以包括已经绑定到 MA上的终端的数量, 或者负荷百分比等信息。
其中, 该 MME1为 MA分配 TA List时可减少 TA的数量, 以减少寻呼区的大 小。
由于 MA与多个终端绑定, 代理多个绑定终端的位置更新流程, 因此终端 的位置更新消息的数量已经大量减少, 如果 MME1为 MA分配 TA List中的 TA的 数量减少的话, 在寻呼终端时, 基站的广播消息覆盖范围小, 可以节省无线资 源。 与 MA进行绑定, 并向终端发送绑定成功的指示信息, 以指示终端在 TA间移动 时不发起 TAU请求, 并在网络侧接收到与多个终端绑定的 MA发送的位置更新 请求后, 认为与 MA绑定的终端也进行了相应的移动, 因此, 不需要与 MA绑 定的终端分别发起位置更新请求消息,也能确定终端的移动位置, 减轻了网络 的处理负担。
实施例三:
参阅图 3, 本发明实施例三提供一种移动性管理方法, 该方法中采用多宿 方式实现终端与 MA的绑定, 该方法包括:
Ml、 终端发起 TAU请求消息, 该 TAU请求消息是绑定请求, 终端可以在 确认自己粘连在 MA后任何时机发起绑定, 该消息中携带网络为终端分配的 GUTL 终端选择的 MA的 ID、 MA的 GUTI和绑定指示。
在该多宿方案中, 由于不需要无线接入网将该 TAU请求消息路由到 MA注 册的 MME1 , 所以终端在 TAU请求消息中的 "终端的 GUTI" 字段中填写自己 的 GUTI, 而将 MA的 GUTI填写到消息的其他字段中。
无线接入网根据 TAU请求消息中的 "终端的 GUTI字段" 中的 GUTI中包含 的 MME Code确定终端当前注册在 MME2, 将该 TAU请求消息路由到 MME2。
M2、 MME2根据 TAU请求消息中的终端的 GUTI寻找终端的上下文, 并根 据 MA的 ID或者 MA的 GUTI判断自己是否是 MA当前注册的 MME, 如果否, 继 续判断自己是否存在附属 MA上下文, 如果存在, 则直接将附属 MA上下文与 终端上下文建立关联, 并将附属 MA上下文中用于记录绑定终端数量的计数器 加 1 ; 如果不存在附属 MA上下文, 则建立附属 MA上下文, 将附属 MA上下文 与终端上下文建立关联, 并将附属 MA上下文中用于记录绑定终端数量的计数 器设置为 1。 然后根据 MA的 GUTI确定 MA的上下文在 MME1上, 与 MME1建立 上下文关联。 如果判断得到 MME2是 MA当前注册的 MME时, 直接将 MA上下 文与终端上下文进行绑定。
具体的, MME2与 MME1建立上下文关联的方式是: MME2向 MME1发送 上下文关联请求消息, 以通知 MME1已在 MME2上建立了附属 MA上下文, 其 中, 附属 MA上下文包括: MA注册的 MME1的地址和对应 MA上下文的标识, 其中, MA注册的 MME1的地址可以是根据 MA的 GUTI中包含的 MME Code通 过查询 DNS ( Domain Name System, 域名系统)服务器获得的, 上述上下文关 联请求消息包括: 对应 MA上下文的标识和对应附属 MA上下文的标识; 其中, 对应 MA上下文的标识用于 MME1查找 MA上下文, 例如可以是 MA的 GUTI; MME1根据对应 MA上下文的标识, 查找到对应的 MA上下文,将 MME2上附属 MA上下文的信息(包括 MME2的地址和对应附属 MA上下文的标识)存入 MA 上下文中, 并向 MME2发送上下文关联响应。 如果 MME2上存在附属 MA上下
文, 说明 MME2已经与 MME1建立了上下文关联, 则 MME2不用每次有终端绑 定时都向 MME1发送上下文关联请求消息。 但在关联关系已经建立的情况下, MME2可以定时向 MME1发送上下文关联更新消息, 该消息包括: 附属 MA上 下文的状态 (即表示 MME2上是否有附属 MA上下文)和 /或附属 MA上下文所 绑定的终端数量, 用于 MME1确定 MME2上是否有附属 MA上下文, 和 /或, 用 于 MME 1获知该 MME2上附属 M A上下文所绑定的终端数量,进而统计 M A上下 文所关联的所有附属 MA上下文上所绑定的终端的数量。
M3、 MME2向终端返回绑定成功的指示信息, 该绑定成功的指示信息可 以是 TAU接受消息, 以指示绑定成功。
其中, MME2也可以不用向终端返回绑定成功的指示信息, 终端在发送绑 定请求后, 如果未收到 MME1的响应消息, 就认为已绑定成功。
终端在绑定成功后, 终端在 TA间移动时, 将不再发起 TAU请求消息, 该 TAU请求消息是位置更新请求消息,但此时终端可以仍然发起周期性 TAU流程 并通过周期性 TAU流程在网络侧维持与 MA的绑定关系。 并且, 终端在绑定期 间继续接收 MA的通告消息, 从通告消息中获得 MME为 MA分配的新的 TA List 作为自己的当前的 TA List。 当然, 终端也可以在去绑定时再向 MME请求为自 己分配 TA List。
以上步骤实现了终端与 MA的绑定, 后续步骤描述 MA代理绑定的终端进 行位置更新。
M4、 MA检测基站发送的广播信号, 发现自己已经移出 MME1为自己分配 的 TA List范围而进入一个目标跟踪区 TA2 , MA发起 TAU请求消息; eNodeB接 收该 TAU请求消息,在该 TAU请求消息中加入目标跟踪区标识 TAI2后发送。假 设 MA原来注册的 MME1仍然能够为跟踪区 TA2服务, eNodeB将 TAU请求消息 路由到 MME1。
M5、 MME1接收到 TAU请求消息后, 查找 MA的上下文, 为 MA分配新的
TA List并保存在 M A上下文中, 该新的 TA List包括但不仅限于: TAI2。 MME1 从 MA上下文中确认与其他的 MME建立了上下文关联,如果网络配置为由网络 直接在 TA List中寻呼终端,则从 MA上下文中获取关联的 MME的地址和对应附 属 MA上下文的标识, 向该关联的 MME (比如 MME2 )发送 3艮踪区更新通知消
息, 该消息中携带 MME1为 ΜΑ新分配的 TA List和对应附属 MA上下文的标识, MME2接收到该消息后, 4艮据对应附属 MA上下文标识查找附属 MA上下文,将 新的 TA List保存在附属 MA上下文中。 如果不是由网络直接在 TA List中寻呼终 端, 而是通过 MA中转的, 则本步骤中通知 MME2更新附属上下文中的 TA List 不是必须的。
M6、 MME2向 MME1返回 3艮踪区更新响应消息。
M7、 MME1向 MA返回 TAU接受消息, 该消息中携带为 MA分配的新的 GUTI、 TA List以及已经绑定到 MA上的终端的数量。
本发明实施例三中终端注册的 MME2将终端上下文与附属 MA上下文进行 关联,且终端注册的 MME2与 MA注册的 MME1建立上下文关联,将终端与 MA 进行绑定, 并向终端发送绑定成功的指示信息, 以指示终端在 TA间移动时不 发起 TAU请求,在网络侧接收到与多个终端绑定的 MA发送的位置更新请求后, 认为与 MA绑定的终端也进行了相应的移动。 因此, 不需要与 MA绑定的终端 分别发起位置更新请求消息,也能确定终端的移动位置, 减轻了网络的处理负 担。 本实施例中两个 MME之间通过直接进行消息交互建立关联关系, 在实际 应用中, 例如 MA注册的移动管理实体和终端注册的移动管理实体是松耦合的 关系时, 也可以通过一个中间网元中转来建立这种关联关系, 不再详述。
实施例四:
参阅图 4, 本发明实施例四中对 MA的功能进一步增强, 使 MA具有移动基 站的功能, 终端通过 MA执行绑定, 采用单宿方式实现终端与 MA的绑定, 该 方法包括:
Nl、 终端向 MA发起 TAU请求, 该 TAU请求是绑定请求, 该消息中携带终 端的 GUTI,该消息还可以携带 MA的相关信息, MA的相关信息包括: MA的 ID、 MA当前所在的 TA、 MA的 GUTI等。如果该 TAU请求中不携带 MA的相关信息, 则 MA会在 TAU请求中加入 MA的相关信息。
N2、 MA向 MA注册的 MME1发送 TAU请求消息。
其中, 该 TAU请求消息是否仍然经过无线接入网取决于 MA选择的回程方 案, 如果 MA选择当前移动通信网的无线链接作为回程, 则该消息需要通过无 线接入网到达网络侧; 如果 MA选择其他的回程方案, 比如卫星、 WLAN (无
线局域网)、 敖波存取全球互通 ( Worldwide Interoperability for Microwave Access, WiMax ), 则不需要经过无线接入网。
N3— N6与 L2— 相同。
本发明实施例四中终端通过 MA发送 TAU请求到 MME1 , MME1将终端上 下文与 MA上下文进行关联, 实现终端与 MA的绑定, 并向终端发送绑定成功 的指示信息, 以指示终端在 TA间移动时不发起 TAU请求, 在网络侧接收到与 多个终端绑定的 MA发送的位置更新请求后, 认为与 MA绑定的终端也进行了 相应的移动, 因此, 不需要与 MA绑定的终端单独发起位置更新请求消息, 也 能确定终端的移动位置, 减轻了网络的处理负担。
该实施例四以单宿方式为基础, 描述了终端通过 MA执行绑定的方式, 也 可以以多宿方式为基础, 其实现方式包括: 终端发送绑定请求, MA或者接入 汇聚网关将终端的绑定请求路由到终端注册的移动性管理实体,后续的执行步 骤与 M3和 M7相同, 在此不再赘述。
如下几种情况是在 MA与终端绑定后, 对网络侧寻呼绑定终端、 网络侧与 终端之间的信令连接建立后的绑定关系、 MA通知绑定终端进行重新绑定和去 绑定流程进行描述。
一、 网络侧寻呼绑定终端
在终端与 MA绑定后, 网络侧认为 MA的当前位置就是终端的当前位置, 因此寻呼终端时可以在 MA的当前跟踪区 (即为 MA分配的 TA List ) 内寻呼终 端。
如下有三种寻呼方式:
1、 由于 MME中的 MA上下文或者附属 MA上下文中总是保存着 MA分配的 TA List, 所以终端当前注册的 MME可以指示无线接入网直接在 MA的 TA List 内寻呼终端。
其中, 为了提高寻呼成功率, MME可以指示无线接入网除了在 MA的 TA
List中的寻呼区( MA的 TA List中的寻呼区即是 MA当前寻呼区 )发送寻呼消息 夕卜, 还在 MA的 TA List的临近小区也发寻呼消息, 以避免当 MA位于寻呼区边 缘时, 绑定的终端可能处于寻呼区之外的临近小区而导致接收不到寻呼消息, 寻呼失败。
2、 在网络中采用单宿方式实现终端与 MA的绑定时, 通过 MA进行寻呼终 端。
MA注册的 MME1决定对终端发起寻呼, MME1首先将寻呼消息发送到 MA, MA在自己覆盖的范围内广播寻呼消息; 终端接收到寻呼消息后, 可以 通知 MA停止广播寻呼消息, 并通过良务请求消息向 MME1响应寻呼。
3、 在网络中采用多宿方式实现终端与 MA的绑定时, 通过 MA进行寻呼终 端。
Pl、 MME2决定寻呼终端,发现终端上下文关联到一个附属 MA上下文上, 从该附属 MA上下文中得到 MA所注册的 MME1的地址, 向 MME1发送寻呼消 息, 该消息中携带需要寻呼的终端的标识。
P2、 MME1接收到寻呼消息后, 将寻呼消息发送给 MA。
P3、 M A在自己的覆盖区域内广播寻呼消息, 以寻呼终端。
P4、 终端收到寻呼消息后, 可以通知 M A停止广播寻呼消息, 向 MME2发 送服务请求消息, 以应答寻呼。
当采用通过 MA寻呼终端的方案时, 如果 MA是采用无线接入连接到网络 侧并且与网络侧的无线连接已经释放, 则在将对终端的寻呼消息发送给 MA之 前可能需要先寻呼 MA并重新建立无线连接; 如果 MA是采用固定接入连接到 网络侧, 例如 MA放置在电影院、 体育馆等场所, 则对终端的寻呼消息可以直 接发送给 MA。
二、 网络侧与终端之间的信令连接建立后的绑定关系
如果 MA不具备中转终端和网络之间的信令和用户面数据的功能时, 如果 终端需要进行业务, 或者, 终端接收到寻呼消息后需要发送服务请求消息到终 端当前注册的 MME (比如 MME2 ), MME2接收到服务请求消息后, 通过无线 接入网建立与终端的信令连接, 以应答终端的服务请求消息。 并可以根据终端 的请求恢复终端与无线接入网之间的承载。在终端和网络建立信令连接的情况 下, 终端按照未和 MA绑定时一样的触发条件触发切换、 TAU等流程。
在终端和网络侧建立信令连接的情况下, 对于终端和 MA的绑定关系有如 下两种处理方案:
1、 终端和 MME上都清除终端和 MA的绑定关系。 终端可以在信令连接释
放后, 转为 Idle态后重新绑定到该 MA上, 也可以选择新的 MA进行绑定。
具体的, 对于单宿方式, MA注册的 MME1 (由于该 MME1获取了终端上 下文, 所以该 MME1也是终端当前注册的 MME )删除 MA上下文与终端上下文 的绑定关系。 对于多宿方式, 终端注册的 MME2删除附属 MA上下文与终端上 下文的绑定关系, 并将用于记录绑定终端数量的计数器减 1 , 当计数器值为 0 时,从附属 MA上下文中获取 MA注册的 MME1的信息, 向 MME1发送指示删除 上下文关联的通知消息, 所述指示删除上下文关联的通知消息包括: 对应 MA 上下文的标识, 如可以使用 MA的 GUTI; MME1从 MA上下文中删除 MME2的 地址和对应附属 MA上下文的标识, 以删除与 MME2的上下文关联。
如上所述在终端和网络侧建立信令连接的情况下, 清除终端和 MA的绑定 关系, 可以避免在终端检测到自己已经移出 MA的覆盖范围后所触发的去绑定 流程, 使网络处理流程筒单。
2、 终端和 MME继续保持绑定关系。 在这种情况下, 即使终端和网络侧建 立了信令连接, 当终端所检测到已经离开所绑定的 MA的覆盖区域时, 也需要 发起去绑定流程通知网络侧自己已经离开 MA的覆盖区域。
三、 MA通知绑定终端进行重新绑定
由于终端与 MA绑定后,在 TA间移动时不再发起 TAU流程从而节省了 TAU 请求消息数量。 但是, 当由于 MA的移动范围较大不得不发生 MME切换时, 由 于 MA注册的 MME发生了改变, 在单宿方案下, 所有当前与该 MA绑定的终端 的上下文都需要迁移到新的 MME上; 在多宿方案下, 部分甚至全部绑定终端 可能也需要迁移到新的 MME上(不一定与 MA迁移到的新 MME相同 ), 并且由 于 MA注册的 MME发生了改变, MA注册的新 MME和终端注册的 MME之间的 MA上下文关联关系需要重建, 在本发明的实施例中, 网络侧先释放所有终端 与 MA的绑定关系, 然后通知 MA, 并由 MA通知绑定的终端发起 TAU流程, 以 进行重新绑定, 参阅图 5, 其过程具体包括:
Ql、 MA移出 TA List中的跟踪区, 进入另一个 TA, 发起 TAU请求消息, 该 消息是第二位置更新请求消息。 由于 MA原来注册的 MME不能为新的 TA服务, 所以无线接入网选择一个新的 MME(即为 MA注册的新 MME, MME6 ),将 TAU 请求消息路由到 MME6。
Q2、 MME6向 MA原来注册的 MME ( MA注册的老 MME, MME5 )发送获 取 MA上下文请求。
Q3、 MME5接收到 MME6发起的获取上下文请求后, 如果 MA与终端以多 宿方式绑定, 则从 MA的上下文中获取关联的 MME的地址和对应附属 MA上下 文的标识, 向所有关联的 MME发送指示删除上下文关联的通知消息, 该消息 中包括: 对应附属 MA上下文的标识。 关联的 MME (比如终端注册的老 MME, MME3 )接收到指示删除 MA上下文关联的通知消息后, 查找对应的附属 MA 上下文, 清除附属 MA上下文与终端的绑定关系, 并删除附属 MA上下文, 向 MME5应答。
Q4、 在自己以及所有关联的 MME上该 MA上下文与终端上下文的绑定关 系都清除后 (即关联 MME所保存的附属 MA上下文与终端上下文绑定关系清 下文标识被清除 ) , MME5向 MME6发送 MA上下文。
Q5、 MME6向 HSS登记自己为 MA当前注册的 MME。
Q6、 MME6为 MA分配新的 GUTI和 TA List, 向 MA返回 TAU接受消息, 该 消息中携带为 MA新分配的 GUTI、 TA List和重绑定指示。
Q7、 MA收到 TAU接受消息后, 根据重绑定指示确认需要终端进行重新绑 定, 发送重绑定通告消息, 并在重绑定通告消息中通知所有与 MA绑定的终端 执行重新绑定流程。
Q8、 终端收到重绑定通告消息后, 发起 TAU请求消息, 该消息中携带终 端自己的 GUTI、 MA的 ID、 MA的 GUTI ( MME6为 MA新分配的 GUTI )和绑定 指示。
为了减少大量绑定终端在短时间内发起 TAU重绑定对网络造成的沖击,各 个终端在收到重绑定通告消息后, 可以随机延迟一段时间再发起 TAU请求消 息。
在多宿方式下, 无线接入网根据该消息中的终端的 GUTI, 将该 TAU请求 消息路由到终端原来注册的 MME ( MME3 ), 如果该 MME3不能为进入新的 TA 的终端服务, 则无线接入网选择一个能够为 TA服务的 MME (比如 MME4作为 终端新注册的 MME ), 此时, 将该 TAU请求消息路由到 MME4。
Q9、 MME4从 MME3获取终端上下文。
Q10、 MME4根据 MA的 ID或者 MA的 GUTI确认自己不是 MA当前注册的 MME, 判断自己是否存在附属 MA上下文, 如果存在, 则直接将附属 MA上下 文与终端上下文建立关联; 如果不存在附属 MA上下文, 则建立附属 MA上下 文,并将附属 MA上下文与终端上下文建立关联。然后根据 MA的 GUTI确定 MA 的上下文在 MME6上, 与 MME6建立上下文关联, 这里重绑定流程的处理与初 始绑定的处理相同。
Qll、 MME4向 HSS登记自己为终端当前注册的 MME。
Q12、 MME4向终端返回 TAU接受消息, 该消息中携带 MME4为终端分的 新 GUTI。
以上描述多宿方式下的重绑定, 如果 MA与终端以单宿方式绑定, 则 MA 原来注册 MME ( MME5 ) 与终端原来注册的 MME ( MME3 ) 为同一个 MME, MA新注册 MME ( MME6 )与终端新注册的 MME ( MME4 ) 为同一个 MME。 此时, 与以上描述不同之处在于, Q2中 MME6向 MME5发送获取上下文请求和 清除 MA和终端的绑定关系的指示, Q3中 MME5将 MA与终端的绑定关系清除, 即清除 MA上下文与终端上下文的关联关系。 Q10中 MME4建立 MA上下文与终 端上下文的绑定关系。
如上通过 MA指示终端进行重新绑定, 可以实现当 MA进行 MME切换时, MA与终端的重新绑定, 以保证进行 MME切换后, 网络侧依然能够根据 MA的 移动确定与其绑定在一起的终端也一起移动。
四、 去绑定流程
1、 当终端检测到自己已经移出 MA覆盖范围后, 发起 TAU流程去绑定。 图 6示出了终端触发的去绑定流程, 具体包括:
Rl、 终端检测到 MA信号强度低于预定的门限值, 或者 MA广播消息中要 求终端去绑定, 终端发起 TAU请求消息, 该 TAU请求是去绑定请求, 该消息中 携带终端的 GUTI、 MA的 ID、 去绑定指示, 该 TAU请求消息被路由到 MME2 (终端当前注册的 MME )。
R2、 如果是单宿方式, 由于在绑定时终端上下文被迁移到 MA当前注册的 MME1 , 所以此时终端当前注册的 MME2和 MA当前注册的 MME1是一个
MME,则删除 MA上下文和所述终端的上下文的绑定关系。如果是多宿方式下, 终端当前注册 MME2确认终端上下文关联到附属 MA上下文, 并将计数器减 1 , 当计数器数值为 0时, 从附属 MA上下文中获取 MA当前注册的 MME1的信息 ( MME1的地址), 向 MME1发送指示删除上下文关联的通知消息; MME1收 到该通知消息后,从 MA上下文中删除该 MME2的信息和对应附属 MA上下文的 标识。 (图中所示为多宿方式)
其中, 当计数器数值为 0时, 可以不马上向 MME1发送指示删除上下文关 联的通知消息, 而是等待一段时间, 比如等待 30秒, 以确认 MME2短时间内是 否有新的终端要与 MA进行绑定, 如果是, 则不发送指示删除上下文关联的通 知消息, 如果否, 发送指示删除上下文关联的通知消息。
R3、 MME2为终端新分配 GUTI和 TA List, 向终端发送 TAU接受消息, 该 消息中携带为终端新分配的 GUTI和 TA List。
在去绑定后, 终端在移动出 TA List的跟踪区而进入一个新的跟踪区时,像 现有技术一样发起 TAU流程通知网络位置改变。
以上描述的终端检测到自己已经移出 MA覆盖范围, 主动发起 TAU流程去 绑定, 保证在终端移动出 MA覆盖范围时, MA与终端的绑定关系解除, 以使 后续终端移动时能像现有技术一样继续触发 TAU流程, 而不是根据 MA的移动 确定该终端的移动, 保证网络侧能获得终端正确的移动位置。
2、 在某些情况下, MA可能决定停止移动代理服务, 比如安装了 MA的公 共汽车到了终点, 或者, 当 MA^载能力下降时, 决定批量去绑定当前已绑定 的一些终端, 图 7示出了 MA触发的去绑定流程, 具体包括:
51、 MA发起 TAU请求, 该 TAU请求携带去绑定当前所有终端的指示。
52、 MA当前注册 MME1接收到该 TAU请求, 如果是单宿方式, 则清除所 有绑定的终端上下文与 M A上下文的绑定关系。如果 MME 1每次为 M A重新分配 TA List时,对终端上下文中的 TA List都没有刷新的话, 则在之前还包括将所有 绑定的终端上下文中的 TA List设置成 MA当前的 TA List。 如果是多宿方式, MME1从 MA上下文中获取关联的 MME的信息( MME的地址和对应附属 MA上 下文的标识), MME1向关联的 MME (比如 MME2 )发送指示删除上下文关联 的通知消息,该消息中携带对应附属 MA上下文的标识。如果 MME1每次为 MA
重新分配 TA List时, 都没有通知 MME2, 则该指示删除上下文关联的通知消息 中还包括 MA当前的 TA List。 MME2根据附属 MA上下文的标识查找附属 MA上 下文, 将与附属 MA上下文有绑定关系的终端上下文中的 TA List设置成 MA当 前的 TA List, 清除附属 MA上下文与终端上下文的绑定关系, 删除附属 MA上 下文, 向 MME1应答。 (图中所示为多宿方式)
53、 MA当前注册 MME1向 MA返回 TAU接受消息指示 MA去绑定成功, 该 消息中包括 MA当前的 TA Listo
54、 MA向终端发送用于指示绑定关系已解除的去绑定通告消息, 该去绑 定通告消息中包括 MA当前的 TA List。
当终端接收到去绑定通告消息后, 将通告消息中的 MA当前 TA List作为自 己的当前 TA List保存起来, 并解除自己保存的与 MA的绑定状态, 即后续如果 在移动出 TA List的跟踪区而进入一个新的跟踪区时,像现有技术一样发起 TAU 流程通知网络位置改变。
由于终端可能离绑定的 MA有一定距离, 在某些罕见情况下, 当绑定的终 端接收到 MA的去绑定通告消息后, 可能发现自己已经移动出 MA当前的 TA List的跟踪区的范围,也即 MME2上保存的终端上下文中的 TA List是不准确的, 此时终端发起 TAU流程向 MME2上 4艮自己的准确位置并要求重新为自己分配 TA Listo
如上以 MA去绑定所有终端为例进行描述, MA也可以去绑定某些终端, 例如在多宿方案下 MA只请求去绑定注册在某一个 MME上的终端的绑定关系, 其实现方式与上述描述相似, 在此不再赘述。
上述描述的 MA触发去绑定, 可以在 MA不能或者停止作为移动代理时, 使 MA与终端的绑定关系批量清除, 而不需要每个绑定终端分别发起去绑定流 程, 从而节约了去绑定的信令数量。
上述本发明各实施例是终端主动发起绑定请求消息, 以请求与 MA进行绑 定的, 此仅为本发明技术方案提供的一种实施方式, 本发明技术方案并不限于 此, 也可由网络侧主动将 MA与终端进行绑定, 比如, 网络侧对 MA的认证成 功 (即授权 MA具有移动代理功能)后, 将与 MA位置临近的终端与 MA绑定, 并在绑定后向终端发送绑定指示, 指示终端在 TA间移动时不发起 TAU流程,
不影响本发明的实现。
实施例五:
参阅图 8, 本发明实施例五提供一种移动性管理装置, 包括:
绑定单元 801 , 用于将 MA上下文与终端上下文绑定;
绑定成功指示发送单元 802, 用于在所述绑定单元 801将 MA上下文与终端 上下文绑定之后, 向终端发送绑定成功的指示信息, 以指示所述终端在位置更 新时不发起位置更新请求;
位置更新请求接收单元 803, 用于接收所述 MA发送的位置更新请求; 确定移动位置单元 804, 用于在所述绑定单元将 MA上下文与终端上下文 绑定之后, 根据所述位置更新请求, 修改所述 MA上下文, 并确定所述终端与 所述 MA—起移动。
其中, 该移动性管理装置也可以不包括绑定成功指示发送单元 802, 即终 端在发送绑定请求后, 在特定时长内没有接收到响应消息, 则认为绑定成功, 不需要移动性管理装置向终端发送表示 MA与终端绑定成功的绑定指示。
其中, 所述绑定单元 801包括:
判断单元, 用于在接收到请求终端与 MA绑定的绑定请求消息后, 判断所 述终端是否注册在自己上;
终端上下文获取单元, 用于当所述判断单元的判断结果为是时,从所述移 动性管理装置上获取终端上下文, 当所述判断单元的判断结果为否时,从所述 终端当前所注册的 MME上获取终端上下文;
MA上下文关联。
若 MA以前注册过 MME, MA发生了 MME切换, 该移动性管理装置是 MA 注册的新 MME时, 该装置还包括: 通知重绑定单元, 用于在接收到 MA发送的 第二位置更新请求后, 从 MA注册的老移动性管理实体获取 MA上下文和终端 上下文, 并指示所述 MA注册的老移动性管理实体清除 MA上下文和终端上下 文的绑定关系, 向所述 MA发送携带重绑定指示的位置更新接受消息; 绑定单 元 801用于在接收到请求终端与 MA绑定的绑定请求消息后, 将从 MA注册的老 移动性管理实体获取的所述 MA上下文和终端上下文绑定。
所述装置还包括:
寻呼指示单元 805 , 用于在所述绑定单元将 MA上下文与终端上下文绑定 后, 当需要寻呼终端时, 指示无线接入网在 MA的当前寻呼区内寻呼终端; 或 者, 指示无线接入网在 MA的当前寻呼区及当前寻呼区的临近小区寻呼终端; 或者, 向 MA发送携带终端标识的寻呼消息, 以指示所述 MA对所述终端进行 寻呼。
第一去绑定单元 806, 用于在所述绑定单元将 MA上下文与终端上下文绑 定后, 当接收到 MA发送的去绑定指示时, 删除 MA上下文与所有终端上下文 的绑定关系;
和 /或,
第二去绑定单元 807, 用于在所述绑定单元将 MA上下文与终端上下文绑 定后, 当接收到终端发送的去绑定指示时, 或者, 终端与网络侧建立信令连接 还可以包括: 绑定请求消息接收单元, 用于接收请求终端与 MA绑定的绑 定请求消息;所述绑定单元 801 ,用于在接收到请求终端与 MA绑定的绑定请求 消息后, 将 MA上下文与终端上下文绑定。
本发明实施例五中的移动性管理装置的绑定单元将 MA上下文与终端上 下文绑定, 绑定成功指示发送单元指示终端在位置更新时不发起位置更新请 求, 以减少网络侧的处理负担; 且在接收到 MA发送的位置更新请求后, 认为 与 MA绑定的终端也进行了相应的移动, 因此, 不需要与 MA绑定的终端单独 发起位置更新请求消息, 也能确定终端的移动位置。
本发明另一实施例提供一种移动性管理装置, 其包括:
位置更新请求接收单元, 用于接收 MA发送的第一位置更新请求; 确定移动位置单元, 用于根据所述第一位置更新请求和 MA上下文与终端 上下文的绑定关系, 确定所述终端与所述 MA—起移动。 其中, 所述 MA上下 文与终端上下文的绑定关系包括:终端上下文与终端注册的移动性管理实体上 的附属 MA上下文的绑定,及所述附属 MA上下文与 MA注册的移动性管理实体 上的 MA上下文的关联。
实施例六:
参阅图 9, 本发明实施例六提供一种移动性管理装置, 该移动性管理装置 可以是多宿方式下终端注册的 MME, 包括:
附属 MA上下文建立单元 901 , 用于建立附属 MA上下文, 将所述附属 MA 上下文与 MA注册的移动性管理实体上的 MA上下文关联;
绑定单元 902, 用于将终端上下文与所述附属 MA上下文绑定。
绑定成功指示发送单元 903 , 用于在建立附属 MA上下文, 且将终端上下 文与附属 MA上下文绑定之后, 向终端发送绑定成功的指示信息, 以指示所述 终端在位置更新时不发起位置更新请求。
其中, 该移动性管理装置也可以不包括绑定成功指示发送单元 903, 即终 端在发送绑定请求后, 在特定时长内没有接收到响应消息, 则认为绑定成功, 不需要移动性管理装置向终端发送表示 MA与终端绑定成功的绑定指示。
该装置还包括:
寻呼区列表接收单元 904, 用于在所述附属 MA上下文建立单元将所述附 属 MA上下文与 MA注册的移动性管理实体上的 MA上下文关联后, 接收 MA注 册的移动性管理实体发送的携带新的寻呼区列表的位置更新请求;
第一寻呼单元 905, 用于当需要寻呼终端时, 指示无线接入网在所述新的 寻呼区列表所列的当前寻呼区内寻呼终端; 或者,指示无线接入网在所述新的 寻呼区列表所列的当前寻呼区及其临近小区内寻呼终端。
或者,
第二寻呼单元, 用于在绑定单元将终端上下文与所述附属 MA上下文绑定 后, 当需要寻呼终端时, 通过 MA注册的移动性管理实体向 MA发送寻呼消息, 以指示 M A寻呼终端。
第一删除单元 906, 用于在绑定单元将终端上下文与所述附属 MA上下文 绑定后, 在接收到终端发送的去绑定指示后, 或者, 在终端和网络侧建立信令 连接后, 删除所述终端的上下文与附属 MA上下文的绑定关系。
计数器单元 907, 用于在第一删除单元删除所述终端的上下文与 MA附属 上下文的绑定关系后, 将用于记录绑定终端数量的计数器减 1;
指示删除上下文关联通知发送单元 908 , 用于当计数器值为 0时, 向所述 MA注册的移动性管理实体发送指示删除上下文关联的通知消息。
指示删除上下文通知消息接收单元 909, 用于接收 MA注册的移动性管理 实体发送的指示删除上下文关联的通知消息;
第二删除单元 910 ,用于在接收到所述指示删除上下文关联的通知消息后, 删除终端上下文与附属 MA上下文绑定, 并删除所述附属 MA上下文。
该装置还可以包括: 绑定请求消息接收单元, 用于接收请求终端与 MA绑 定的绑定请求消息; 所述绑定单元, 用于在接收到请求终端与 MA绑定的绑定 请求消息后, 将终端上下文与所述附属 MA上下文绑定。
本发明实施例六中移动性管理实体中的附属 MA上下文建立单元建立用 于与 MA注册的 MME进行上下文关联的附属 MA上下文; 上下文绑定单元将终 端上下文与附属 MA上下文绑定, 以实现 MA与终端的绑定, 并指示终端在位 置更新时不发起位置更新请求, 以减少网络侧的处理负担; 且在接收到 MA 送的位置更新请求后, 认为与 MA绑定的终端也进行了相应的移动, 因此, 不 需要与 MA绑定的终端单独发起位置更新请求消息,也能确定终端的移动位置。
实施例七:
参阅图 10, 本发明实施例七提供一种终端, 该终端是移动终端, 其包括: 绑定指示获取单元 1001 , 用于获取表示终端与 MA绑定成功的指示信息; 控制单元 1002, 用于在获取到表示终端与 MA绑定成功的指示信息后, 在 空闲 Idle态发生移动时控制不发送位置更新请求。
具体的, 绑定指示获取单元 1001 , 用于接收网络侧发送的表示所述终端与 M A绑定成功的指示信息。
该终端还可以包括: 绑定请求发送单元 1003, 用于发送请求终端与 MA绑 定的绑定请求消息
该移动终端还包括:
通告消息接收单元 1004, 用于接收多个 MA发送的表示对应 MA具有移动 代理能力的通告消息; 选择单元, 用于在所述通告消息接收单元接收到多个 MA的通告消息后, 选择所述 MA与所述终端绑定。
本发明实施例七中的终端在获取到表示终端与 MA绑定成功的指示信息 后,在移动时控制不发送位置更新请求, 以使网络侧不会在很短时间内接收并 处理很多位置更新请求消息, 减轻了网络的处理负担。
实施例八:
参阅图 11 , 本发明实施例八提供一种移动代理装置, 包括:
认证请求发送单元 1101 , 用于向网络侧发送认证请求, 所述认证请求用于 请求网络侧授权移动代理能力;
认证结果接收单元 1102, 用于接收网络侧反馈的认证结果;
通告发送单元 1103, 用于发送携带所述认证结果的通告消息, 以供终端确 认所述移动代理装置具有移动代理能力。
该装置还包括:
去绑定指示发送单元,用于向 MA所在的移动性管理实体发送去绑定指示。 重绑定指示接收单元, 用于接收 MA注册的新移动性管理实体发送的重绑 定指示;
重绑定通告消息发送单元, 用于发送重绑定通告消息。
寻呼单元, 用于接收 MA注册的移动性管理实体发送的携带终端标识的寻 呼消息, 根据所述寻呼消息, 寻呼终端。
利用本发明实施例八所提供的移动代理装置, 可以作为终端的移动代理, 代理终端的移动。
实施例九:
本发明实施例九提供一种通信系统, 包括: 终端注册的 MME, MA注册的 MME, 其中,
终端注册的移动性管理实体, 用于建立附属 MA上下文, 与 MA注册的移 动性管理实体上的 MA上下文关联, 并将终端上下文与附属 MA上下文绑定;
MA注册的移动性管理实体, 用于建立 MA上下文, 与终端注册的移动性 管理实体上的附属 MA上下文关联, 接收所述 MA发送的位置更新请求; 根据 所述位置更新请求, 确定与所述附属 MA上下文绑定的终端上下文所对应的终 端与所述 MA—起移动。
本发明实施例九中通过将 MA上下文与附属 MA上下文关联, 并将终端上 下文与附属 MA上下文绑定, 以实现将 MA上下文与终端上下文绑定, 在接收 到 MA发送的位置更新请求后, 认为与 MA绑定的终端也进行了相应的移动, 因此, 不需要与 MA绑定的终端分别发起位置更新请求消息, 也能确定终端的 移动位置, 减轻了网络的处理负担。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分步骤 是可以通过程序来指令相关的硬件完成,所述的程序可以存储于一种计算机可 读存储介质中, 例如, 只读存储器, 磁盘或光盘等。
以上对本发明实施例所提供的移动性管理方法、相关设备及通信系统进行 以上实施例的说明只是用于帮助理解本发明的方法及其核心思想; 同时,对于 本领域的一般技术人员,依据本发明的思想,在具体实施方式及应用范围上均 会有改变之处, 综上所述, 本说明书内容不应理解为对本发明的限制。
+
Claims
1、 一种移动性管理方法, 其特征在于, 包括:
接收移动代理 MA发送的第一位置更新请求;
根据所述第一位置更新请求和 MA上下文与终端上下文的绑定关系, 确定 所述终端与所述 MA—起移动。
2、 根据权利要求 1所述的方法, 其特征在于, 在接收 MA发送的第一位置 更新请求之前, 该方法还包括:
3、 根据权利要求 2所述的方法, 其特征在于,
所述将 MA上下文与终端上下文绑定包括:
所述 MA注册的移动性管理实体接收终端发送的请求终端与 MA绑定的绑 定请求消息后,根据所述绑定请求消息中终端当前注册的移动性管理实体的寻 址信息, 判断所述终端是否注册在本地, 如果是, 从本地获取终端上下文; 如 果否, 从终端当前注册的移动性管理实体获取终端上下文;
将获取的所述终端上下文与 MA上下文绑定。
4、 根据权利要求 3所述的方法, 其特征在于,
所述 MA注册的移动性管理实体是 MA注册的新移动性管理实体; 在所述 MA注册的移动性管理实体接收终端发送的请求终端与 MA绑定的 绑定请求消息之前, 该方法还包括:
所述 MA发起第二位置更新请求;
所述 MA注册的新移动性管理实体接收到所述第二位置更新请求后, 从 MA注册的老移动性管理实体获取 MA上下文和终端上下文,并指示所述 MA注 册的老移动性管理实体清除 MA上下文和终端上下文的绑定关系, 向所述 MA 发送携带重绑定指示的位置更新接受消息;
所述 MA发送携带重绑定指示的重绑定通告消息;
所述终端根据所述重绑定通告消息中的重绑定指示发送绑定请求消息。
5、 根据权利要求 4所述的方法, 其特征在于,
所述将 MA上下文与终端上下文绑定包括:
所述 MA注册的新移动性管理实体将从 MA注册的老移动性管理实体获取
的所述 MA上下文和终端上下文绑定。
6、 根据权利要求 3所述的方法, 其特征在于,
所述 MA注册的移动性管理实体接收终端发送的请求终端与 MA绑定的绑 定请求消息包括:
所述 MA注册的移动性管理实体通过无线接入网接收终端发送的绑定请 求消息, 所述绑定请求消息中包括 MA注册的移动性管理实体的寻址信息。
7、 根据权利要求 3所述的方法, 其特征在于,
所述 MA注册的移动性管理实体接收终端发送的请求终端与 MA绑定的绑 定请求消息包括:
所述 MA注册的移动性管理实体通过所述 MA或者 MA的接入汇聚网关接 收所述终端发送的绑定请求消息。
8、 根据权利要求 2所述的方法, 其特征在于, 在将 MA上下文与终端上下 文绑定之后, 该方法还包括:
所述 MA注册的移动性管理实体指示无线接入网在 MA的当前寻呼区内寻 呼终端;
或者,
所述 MA注册的移动性管理实体指示无线接入网在 MA的当前寻呼区及当 前寻呼区的临近小区寻呼终端;
或者,
所述 MA注册的移动性管理实体向 MA发送携带终端标识的寻呼消息, 以 指示所述 MA对所述终端进行寻呼。
9、 根据权利要求 2所述的方法, 其特征在于, 在将 MA上下文与终端上下 文绑定之后, 该方法还包括:
所述 MA注册的移动性管理实体接收到 MA发送的去绑定指示后,删除 MA 上下文与所有终端上下文的绑定关系;
或者,
所述 MA注册的移动性管理实体接收到终端发送的去绑定指示后, 删除所 述终端的上下文与 MA上下文的绑定关系;
或者,
终端与网络侧建立信令连接后, 删除所述终端的上下文与 MA上下文的绑 定关系。
10、 根据权利要求 2所述的方法, 其特征在于, 在将 MA上下文与终端上 下文绑定之后, 该方法还包括:
所述 MA注册的移动性管理实体向终端发送绑定成功的指示信息, 以指示 所述终端在位置更新时不发起位置更新请求。
11、根据权利要求 1所述的方法, 其特征在于, 在接收 MA发送的第一位置 更新请求之前, 该方法还包括:
终端注册的移动性管理实体将 MA上下文与终端上下文绑定。
12、 根据权利要求 11所述的方法, 其特征在于, 终端注册的移动性管理实体建立附属 MA上下文,将附属 MA上下文与 MA 注册的移动性管理实体上的 MA上下文关联;
所述终端注册的移动性管理实体在接收到终端发送的请求终端与 MA绑 定的绑定请求消息后, 将终端上下文与附属 MA上下文绑定。
13、 根据权利要求 12所述的方法, 其特征在于,
接收终端发送的请求终端与 MA绑定的绑定请求消息包括:
所述终端注册的移动性管理实体通过所述 MA或者 MA的接入汇聚网关接 收终端的绑定请求消息。
14、 根据权利要求 12所述的方法, 其特征在于,
在接收所述 MA发送的第一位置更新请求之后, 该方法还包括:
MA注册的移动性管理实体为所述 MA分配新的寻呼区列表, 向所述终端 注册的移动性管理实体发送携带所述新的寻呼区列表的位置更新请求;
当所述终端注册的移动性管理实体需要寻呼终端时,指示无线接入网在所 述新的寻呼区列表所列的当前寻呼区内寻呼终端; 或者,指示无线接入网在所 述新的寻呼区列表所列的当前寻呼区及其临近小区内寻呼终端。
15、 根据权利要求 12所述的方法, 其特征在于, 在将终端上下文与附属 MA上下文绑定之后, 该方法还包括:
所述终端注册的移动性管理实体通过 MA注册的移动性管理实体向 MA发
送寻呼消息, 所述寻呼消息中携带终端的标识;
16、 根据权利要求 12所述的方法, 其特征在于, 在将终端上下文与附属 MA上下文绑定之后, 该方法还包括:
终端注册的移动性管理实体接收到终端发送的去绑定指示后, 或者,在终 端和网络侧建立信令连接后, 删除所述终端的上下文与附属 MA上下文的绑定 关系, 并将用于记录附属 MA上下文中绑定终端数量的计数器减 1。
17、 根据权利要求 16所述的方法, 其特征在于, 在将用于记录附属 MA上 下文中绑定终端数量的计数器减 1之后, 该方法还包括:
当计数器值为 0时, 所述终端注册的移动性管理实体向所述 MA注册的移 动性管理实体发送指示删除上下文关联的通知消息; 移动性管理实体的关联信息。
18、 根据权利要求 11所述的方法, 其特征在于, 在将终端上下文与附属 MA上下文绑定之后, 该方法还包括:
所述 MA注册的移动性管理实体接收到 MA发送的去绑定指示后, 向所述 终端注册的移动性管理实体发送指示删除上下文关联的通知消息;
所述终端注册的移动性管理实体删除附属 MA上下文与终端上下文的绑 定关系, 并删除所述附属 MA上下文。
19、根据权利要求 12所述的方法,其特征在于,在将附属 MA上下文与 MA 注册的移动性管理实体上的 MA上下文关联之后, 该方法还包括:
所述终端注册的移动性管理实体向 MA注册的移动性管理实体发送上下 文关联更新消息;
所述 MA注册的移动性管理实体根据所述上下文关联更新消息中表示是 否有附属 MA上下文的信息确定终端注册的移动性管理实体上是否有附属 MA 上下文; 和 /或, 根据所述上下文关联更新消息中的终端数量, 获知所述终端 注册的移动性管理实体上附属 MA上下文所绑定的终端数量。
20、 根据权利要求 12所述的方法, 其特征在于,
在接收终端发送的绑定请求消息之前, 该方法还包括:
MA注册的新移动性管理实体接收到 MA发起的第二位置更新请求后, 从 MA注册的老移动性管理实体获取 MA上下文,并指示 MA注册的老移动性管理 实体删除上下文关联; MA注册的老移动性管理实体向关联的移动性管理实体 发送携带对应附属 MA上下文的标识的指示删除上下文关联的通知消息; 所述 关联的移动性管理实体删除所述附属 MA上下文与终端上下文的绑定关系, 并 删除所述附属 MA上下文;
所述 MA注册的新移动性管理实体向所述 MA发送携带重绑定指示的位置 更新接受消息;
所述 MA发送携带所述重绑定指示的重绑定通告消息;
所述终端根据所述重绑定通告消息中的重绑定指示发送绑定请求消息。
21、 根据权利要求 12所述的方法, 其特征在于,
在将附属 MA上下文与 MA注册的移动性管理实体上的 MA上下文关联之 后, 该方法还包括:
所述终端注册的移动性管理实体向终端发送绑定成功的指示信息,以指示 所述终端在位置更新时不发起位置更新请求。
22、 根据权利要求 2或者 12所述的方法, 其特征在于, 在 MA注册的移动 性管理实体接收终端发送的绑定请求消息之前, 或者, 终端注册的移动性管理 实体接收到终端发送的绑定请求消息之前, 还包括:
MA注册的移动性管理实体接收 MA发送的认证请求, 所述认证请求用于 请求网络侧授权移动代理能力;
所述 MA注册的移动性管理实体对 MA进行认证, 向 MA返回认证结果; 所述 MA广播通告消息, 所述通告消息中携带所述认证结果;
所述终端根据所述认证结果, 确认所述 MA具有移动代理能力。
23、 根据权利要求 22所述的方法, 其特征在于,
所述 MA注册的移动性管理实体对 MA进行认证, 向 MA返回认证结果包 括:
MA注册的移动性管理实体获取 MA所配置的公钥,在确认 MA能够提供移 动代理良务后, 用网络侧配置的私钥加密 MA所配置的公钥和 MA的 ID, 得到 第一加密段作为认证结果发送给所述 MA;
所述通告消息包括: 所述第一加密段和第二加密段; 所述第二加密段是 MA使用自己配置的私钥对 MA的 ID和当前时间戳进行加密得到的;
所述终端确认所述 MA具有移动代理能力包括:
所述终端利用网络侧配置的公钥解密第一加密段, 得到 MA所配置的公钥 和 MA的 ID, 利用 MA所配置的公钥解密第二加密段, 得到 MA的 ID和当前的时 间戳, 判断第一加密段中的 MA的 ID与第二加密段中的 MA的 ID是否相同, 如 果是, 判断所述当前时间戳和所述通告消息中的时间戳之差是否超过阈值,如 果否, 确认所述 MA具有移动代理能力。
24、 一种移动性管理装置, 其特征在于, 包括:
位置更新请求接收单元, 用于接收 MA发送的第一位置更新请求; 确定移动位置单元, 用于根据所述第一位置更新请求和 MA上下文与终端 上下文的绑定关系, 确定所述终端与所述 MA—起移动。
25、 根据权利要求 24所述的装置, 其特征在于, 该装置还包括: 绑定单元, 用于将 MA上下文与终端上下文绑定。
26、 根据权利要求 25所述的装置, 其特征在于, 该装置还包括: 绑定请求消息接收单元, 用于接收终端发送的请求终端与 MA绑定的绑定 请求消息;
所述绑定单元包括:
判断单元, 用于在接收到终端发送的请求终端与 MA绑定的绑定请求消息 后,根据所述绑定请求消息中终端当前注册的移动性管理实体的寻址信息, 判 断所述终端是否注册在所述移动性管理装置上;
终端上下文获取单元, 用于当所述判断单元的判断结果为是时,从所述移 动性管理装置上获取终端上下文, 当所述判断单元的判断结果为否时,从所述 终端当前所注册的移动性管理实体上获取终端上下文;
M A上下文绑定。
27、 根据权利要求 25所述的装置, 其特征在于,
所述移动性管理装置是 MA注册的新移动性管理实体;
该装置还包括:
通知重绑定单元, 用于在接收到 MA发送的第二位置更新请求后, 从 MA 注册的老移动性管理实体获取 MA上下文和终端上下文, 并指示所述 MA注册 的老移动性管理实体清除 MA上下文和终端上下文的绑定关系, 向所述 MA发 送携带重绑定指示的位置更新接受消息;
所述绑定单元, 用于在接收到终端从 MA获取所述重绑定指示后所发送的 所述请求终端与 MA绑定的绑定请求消息后, 将从 MA注册的老移动性管理实 体获取的所述 M A上下文和终端上下文绑定。
28、 根据权利要求 25所述的装置, 其特征在于, 所述装置还包括: 寻呼指示单元, 用于在所述绑定单元将 MA上下文与终端上下文绑定后, 当需要寻呼终端时, 指示无线接入网在 MA的当前寻呼区内寻呼终端; 或者, 指示无线接入网在 MA的当前寻呼区及当前寻呼区的临近小区寻呼终端;或者, 向 MA发送携带终端标识的寻呼消息, 以指示所述 MA对所述终端进行寻呼。
29、 根据权利要求 25所述的装置, 其特征在于, 所述装置还包括: 第一去绑定单元, 用于在所述绑定单元将 MA上下文与终端上下文绑定 后, 当接收到 MA发送的去绑定指示时, 删除 MA上下文与所有终端上下文的 绑定关系;
和 /或,
第二去绑定单元, 用于在所述绑定单元将 MA上下文与终端上下文绑定 后, 当接收到终端发送的去绑定指示时,或者,终端与网络侧建立信令连接后,
30、 根据权利要求 25所述的装置, 其特征在于,
所述 MA上下文与终端上下文的绑定关系包括: 终端上下文与终端注册的 移动性管理实体上的附属 MA上下文的绑定,及所述附属 MA上下文与 MA注册 的移动性管理实体上的 MA上下文的关联。
31、 一种移动性管理装置, 其特征在于, 包括:
附属 MA上下文建立单元, 用于建立附属 MA上下文, 将所述附属 MA上下 文与 MA注册的移动性管理实体上的 MA上下文关联;
绑定单元, 用于将终端上下文与所述附属 MA上下文绑定。
32、 根据权利要求 31所述的装置, 其特征在于, 该装置还包括:
寻呼区列表接收单元, 用于在所述附属 MA上下文建立单元将所述附属 MA上下文与 MA注册的移动性管理实体上的 MA上下文关联后, 接收 MA注册 的移动性管理实体发送的携带新的寻呼区列表的位置更新请求;
第一寻呼单元, 用于当需要寻呼终端时,指示无线接入网在所述新的寻呼 区列表所列的当前寻呼区内寻呼终端; 或者,指示无线接入网在所述新的寻呼 区列表所列的当前寻呼区及其临近小区内寻呼终端;
或者,
第二寻呼单元, 用于在绑定单元将终端上下文与所述附属 MA上下文绑定 后, 当需要寻呼终端时, 向 MA注册的移动性管理实体发送携带终端标识的寻 呼消息, 以通过 MA注册的移动性管理实体指示 MA寻呼终端。
33、 根据权利要求 31所述的装置, 其特征在于, 该装置还包括: 第一删除单元, 用于在绑定单元将终端上下文与所述附属 MA上下文绑定 后, 在接收到终端发送的去绑定指示后, 或者, 在终端和网络侧建立信令连接 后, 删除所述终端的上下文与附属 MA上下文的绑定关系。
34、 根据权利要求 33所述的装置, 其特征在于, 该装置还包括: 计数器单元, 用于在第一删除单元删除所述终端的上下文与 MA附属上下 文的绑定关系后, 将附属 MA上下文中用于记录绑定终端数量的计数器减 1; 指示删除上下文关联通知发送单元, 用于当计数器值为 0时, 向所述 MA 注册的移动性管理实体发送指示删除上下文关联的通知消息。
35、 根据权利要求 31所述的装置, 其特征在于, 该装置还包括: 指示删除上下文通知消息接收单元, 用于在所述附属 MA上下文建立单元 将所述附属 MA上下文与 MA注册的移动性管理实体上的 MA上下文关联后,接 收 MA注册的移动性管理实体发送的指示删除上下文关联的通知消息;
第二删除单元, 用于在接收到所述指示删除上下文关联的通知消息后, 删 除终端上下文与附属 MA上下文绑定, 并删除所述附属 MA上下文。
36、 一种终端, 其特征在于, 包括:
绑定指示获取单元, 用于获取表示所述终端与 MA绑定成功的绑定指示; 控制单元, 用于在获取到表示所述终端与 MA绑定成功的绑定指示后, 在 移动时控制不发送位置更新请求。
37、 根据权利要求 36所述的终端, 其特征在于, 还包括:
绑定请求发送单元, 用于向网络侧发送请求终端与 MA绑定的绑定请求消
38、 根据权利要求 37所述的移动终端, 其特征在于,
所述绑定指示获取单元, 用于接收网络侧发送的表示所述终端与 ΜΑ绑定 成功的指示信息。
39、 根据权利要求 36所述的移动终端, 其特征在于, 还包括:
通告消息接收单元, 用于接收多个 ΜΑ发送的表示对应 ΜΑ具有移动代理 能力的通告消息;
选择单元, 用于在所述通告消息接收单元接收到多个 ΜΑ的通告消息后, 选择所述 ΜΑ与所述终端绑定。
40、 一种移动代理装置, 其特征在于, 包括:
认证请求发送单元, 用于向网络侧发送认证请求, 所述认证请求用于请求 网络侧授权移动代理能力;
认证结果接收单元, 用于接收网络侧反馈的认证结果;
通告发送单元, 用于发送携带所述认证结果的通告消息, 以供终端确认所 述移动代理装置具有移动代理能力。
41、 根据权利要求 40所述的装置, 其特征在于, 该装置还包括:
去绑定指示发送单元,用于向 ΜΑ所在的移动性管理实体发送去绑定指示。
42、 根据权利要求 40所述的装置, 其特征在于, 该装置还包括:
重绑定指示接收单元, 用于接收 ΜΑ注册的新移动性管理实体发送的重绑 定指示;
重绑定通告消息发送单元, 用于发送重绑定通告消息。
43、 根据权利要求 40所述的装置, 其特征在于, 该装置还包括:
寻呼单元, 用于接收 ΜΑ注册的移动性管理实体发送的携带终端标识的寻 呼消息, 才艮据所述寻呼消息, 寻呼终端。
44、 一种通信系统, 其特征在于, 包括: 终端注册的移动性管理实体, ΜΑ注册的移动性管理实体, 其中,
所述终端注册的移动性管理实体, 用于建立附属 ΜΑ上下文, 与 ΜΑ注册 的移动性管理实体上的 ΜΑ上下文关联, 并将终端上下文与附属 ΜΑ上下文绑
定;
所述 MA注册的移动性管理实体, 用于建立 MA上下文, 与终端注册的 移动性管理实体上的附属 MA上下文关联, 接收所述 MA发送的位置更新请 求;根据所述位置更新请求,确定与所述附属 MA上下文绑定的终端上下文所 对应的终端与所述 MA—起移动。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2011528168A JP5230813B2 (ja) | 2008-09-27 | 2009-09-21 | モビリティ管理の方法、関連装置、および通信システム |
EP09817235.6A EP2323456B1 (en) | 2008-09-27 | 2009-09-21 | Mobility management method, associated device and communication system |
US13/073,568 US8374629B2 (en) | 2008-09-27 | 2011-03-28 | Mobility management method, relevant devices, and communication system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2008101614607A CN101686455B (zh) | 2008-09-27 | 2008-09-27 | 移动性管理方法、相关设备及通信系统 |
CN200810161460.7 | 2008-09-27 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/073,568 Continuation US8374629B2 (en) | 2008-09-27 | 2011-03-28 | Mobility management method, relevant devices, and communication system |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2010037321A1 true WO2010037321A1 (zh) | 2010-04-08 |
Family
ID=42049360
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2009/074065 WO2010037321A1 (zh) | 2008-09-27 | 2009-09-21 | 移动性管理方法、相关设备及通信系统 |
Country Status (5)
Country | Link |
---|---|
US (1) | US8374629B2 (zh) |
EP (1) | EP2323456B1 (zh) |
JP (1) | JP5230813B2 (zh) |
CN (1) | CN101686455B (zh) |
WO (1) | WO2010037321A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2015510346A (ja) * | 2012-02-06 | 2015-04-02 | アルカテル−ルーセント | モバイル中継局トランシーバのための装置および方法、ならびにモバイル通信システムのための基地局 |
Families Citing this family (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2481396A (en) | 2010-06-21 | 2011-12-28 | Nec Casio Mobile Comm Ltd | Closed subscriber group (CSG) management |
CN101938695B (zh) * | 2010-09-14 | 2013-02-27 | 华为技术有限公司 | 计费方法、装置及系统 |
CN102624645A (zh) * | 2011-11-28 | 2012-08-01 | 苏州奇可思信息科技有限公司 | 面向临时邮件发送的无用户身份验证方法 |
CN105338600B (zh) * | 2011-12-21 | 2019-05-24 | 华为技术有限公司 | 一种读取系统消息的方法、设备 |
WO2014007687A1 (en) * | 2012-07-02 | 2014-01-09 | Telefonaktiebolaget L M Ericsson (Publ) | Method and radio access node for incorporating a moving cell in a wireless communication network |
US8644824B1 (en) * | 2012-07-13 | 2014-02-04 | Sprint Spectrum L.P. | Tracking registration buffer in a cellular network |
CN104885489B (zh) * | 2012-10-29 | 2019-03-08 | 英派尔科技开发有限公司 | 针对高速铁路的lte网络的移动性管理的方法和计算机可读介质 |
WO2014186969A1 (zh) | 2013-05-23 | 2014-11-27 | 华为技术有限公司 | 位置区管理方法及设备 |
EP2993930B1 (en) * | 2013-05-23 | 2020-05-06 | Huawei Technologies Co., Ltd. | Location area management method and core network controller |
KR102201616B1 (ko) * | 2014-02-23 | 2021-01-12 | 삼성전자주식회사 | 전자 장치 간의 장치 검색 방법 |
US20150347562A1 (en) * | 2014-06-02 | 2015-12-03 | Qualcomm Incorporated | Deriving user characteristics from users' log files |
EP3160211B1 (en) * | 2014-08-06 | 2019-06-19 | Huawei Technologies Co., Ltd. | Paging method |
CN106211283A (zh) * | 2015-04-29 | 2016-12-07 | 中兴通讯股份有限公司 | 一种移动网络分级架构的接入方法及系统 |
CN105007241A (zh) * | 2015-07-01 | 2015-10-28 | 杭州祥声通讯股份有限公司 | 一种高铁环境下多普勒频偏估计方法和系统 |
JP6734360B2 (ja) | 2015-07-24 | 2020-08-05 | クアルコム,インコーポレイテッド | 衛星通信の位置報告およびページング |
WO2018000163A1 (zh) * | 2016-06-28 | 2018-01-04 | 海能达通信股份有限公司 | 终端集群注册方法、装置、系统及核心网设备 |
CN110557198A (zh) * | 2018-05-30 | 2019-12-10 | 富士通株式会社 | 光通信控制方法、装置和通信系统 |
CN110650489B (zh) | 2018-06-26 | 2022-02-15 | 华为技术有限公司 | 一种管理监控事件的方法及装置 |
WO2020124230A1 (en) * | 2018-12-19 | 2020-06-25 | Conversant Intellectual Property Management Inc. | System and method for a network access service |
US12015587B2 (en) | 2020-02-28 | 2024-06-18 | New H3C Technologies Co., Ltd. | Methods for updating route, access device, and convergence device |
CN112672338B (zh) * | 2020-12-28 | 2023-09-19 | 超讯通信股份有限公司 | 防止终端脱离小基站吸附的方法及装置 |
WO2022141162A1 (zh) * | 2020-12-30 | 2022-07-07 | 北京小米移动软件有限公司 | 一种通信方法、装置、通信设备和存储介质 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1335024A (zh) * | 1998-12-11 | 2002-02-06 | 艾利森电话股份有限公司 | 当移动站位于移动车辆中时涉及为其提供无线覆盖的设备、系统和方法涉及移动通信的设备、系统和方法 |
CN1477887A (zh) * | 2002-06-24 | 2004-02-25 | 日本电气株式会社 | 移动通信系统、无线电交换方法、移动基站和移动终端 |
EP1860904A1 (en) | 2006-05-26 | 2007-11-28 | Matsushita Electric Industrial Co., Ltd. | Mobility management in communication networks |
CN101203044A (zh) * | 2006-12-13 | 2008-06-18 | 富士通株式会社 | 无线电网络控制方法和装置 |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US235165A (en) * | 1880-12-07 | Step-ladder | ||
US34212A (en) * | 1862-01-21 | merritt | ||
US146237A (en) * | 1874-01-06 | Improvement in paper-cutting machines | ||
US6026277A (en) | 1997-10-20 | 2000-02-15 | Gavrilovich; Charles D. | Mobile communication system with moving base station |
JP3964616B2 (ja) * | 2000-11-10 | 2007-08-22 | 株式会社エヌ・ティ・ティ・ドコモ | 着信要求送信装置、着信要求の送信方法および移動通信網 |
JP4249191B2 (ja) * | 2000-11-16 | 2009-04-02 | 株式会社エヌ・ティ・ティ・ドコモ | 移動通信端末の位置登録方法、移動通信端末の一括呼出方法および移動通信システム |
JP2004229078A (ja) * | 2003-01-24 | 2004-08-12 | Ntt Docomo Inc | ローカル位置情報管理装置、ホーム位置情報管理装置、移動通信システム |
WO2007001950A1 (en) * | 2005-06-21 | 2007-01-04 | Motorola, Inc. | System and method for paging and location update in a network |
-
2008
- 2008-09-27 CN CN2008101614607A patent/CN101686455B/zh active Active
-
2009
- 2009-09-21 JP JP2011528168A patent/JP5230813B2/ja active Active
- 2009-09-21 EP EP09817235.6A patent/EP2323456B1/en active Active
- 2009-09-21 WO PCT/CN2009/074065 patent/WO2010037321A1/zh active Application Filing
-
2011
- 2011-03-28 US US13/073,568 patent/US8374629B2/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1335024A (zh) * | 1998-12-11 | 2002-02-06 | 艾利森电话股份有限公司 | 当移动站位于移动车辆中时涉及为其提供无线覆盖的设备、系统和方法涉及移动通信的设备、系统和方法 |
CN1477887A (zh) * | 2002-06-24 | 2004-02-25 | 日本电气株式会社 | 移动通信系统、无线电交换方法、移动基站和移动终端 |
EP1860904A1 (en) | 2006-05-26 | 2007-11-28 | Matsushita Electric Industrial Co., Ltd. | Mobility management in communication networks |
CN101203044A (zh) * | 2006-12-13 | 2008-06-18 | 富士通株式会社 | 无线电网络控制方法和装置 |
Non-Patent Citations (1)
Title |
---|
See also references of EP2323456A4 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2015510346A (ja) * | 2012-02-06 | 2015-04-02 | アルカテル−ルーセント | モバイル中継局トランシーバのための装置および方法、ならびにモバイル通信システムのための基地局 |
US9344900B2 (en) | 2012-02-06 | 2016-05-17 | Alcatel Lucent | Apparatus and a method for a mobile relay station transceiver and a base station for a mobile communication system |
Also Published As
Publication number | Publication date |
---|---|
CN101686455B (zh) | 2012-12-12 |
EP2323456B1 (en) | 2014-06-18 |
EP2323456A1 (en) | 2011-05-18 |
CN101686455A (zh) | 2010-03-31 |
JP2012503904A (ja) | 2012-02-09 |
EP2323456A4 (en) | 2012-04-18 |
US20110171975A1 (en) | 2011-07-14 |
JP5230813B2 (ja) | 2013-07-10 |
US8374629B2 (en) | 2013-02-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2010037321A1 (zh) | 移动性管理方法、相关设备及通信系统 | |
TWI643519B (zh) | 區域網際網路協定存取(lipa)延伸以賦能區域內容分享 | |
US8462696B2 (en) | Method, radio system, mobile terminal and base station for providing local breakout service | |
JP4950335B2 (ja) | アイドルモードシグナリングリダクションのための方法およびシステム | |
WO2009097772A1 (zh) | 一种资源释放控制方法及通讯系统以及相关设备 | |
JP5357913B2 (ja) | 移動通信方法 | |
JP2012138944A (ja) | サービスノードおよび移動端末 | |
WO2009006774A1 (en) | Interior hangover method in a system | |
WO2008106891A1 (fr) | Procédé, système de communication et entité de réseau pour le transfert d'un groupe de nœuds | |
WO2007006227A1 (fr) | Procédé et système de négociation destinés à l’établissement de chemins de données d’interface | |
WO2010031353A1 (zh) | 服务请求的处理方法、装置及系统 | |
WO2008113235A1 (fr) | Procédé pour éviter la libération erronée de ressources pendant une mise à jour de zone de suivi ou un transfert intercellulaire | |
WO2007076729A1 (fr) | Procede de transfert intercellulaire pour utilisateur mobile et dispositif et systeme de communication et dispositif reseau a evolution | |
WO2010124586A1 (zh) | 一种紧急业务的实现方法及设备 | |
WO2007112690A1 (fr) | Procédé et système de mise à jour de route dans un système de communications mobiles | |
WO2018010583A1 (zh) | 网络系统 | |
WO2013086917A1 (zh) | 会话处理方法及装置 | |
CN102395120B (zh) | 移动性管理方法、相关设备及通信系统 | |
US8929280B2 (en) | Method to switch between network-controlled and mobile-controlled mobile IP functionality | |
WO2009043284A1 (fr) | Procédé, entité de réseau et terminal pour le transfert entre réseaux sans fil hétérogènes | |
KR101901109B1 (ko) | 무선자원 효율성 증진을 통한 안정적인 트래픽 전송을 제공하는 하이브리드 융합 네트워크 관리 시스템 및 방법 | |
WO2012151846A1 (zh) | 一种触发特定位置终端的方法、系统和终端 | |
WO2010075800A1 (zh) | 控制位置更新的方法和终端 | |
WO2010060339A1 (zh) | 移动性管理方法、移动性管理装置及终端设备 | |
WO2011097813A1 (zh) | 去激活isr的方法、修改承载参数的方法和网络系统 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 09817235 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2011528168 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1478/KOLNP/2011 Country of ref document: IN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2009817235 Country of ref document: EP |