WO2017024843A1

WO2017024843A1 - Context transfer method and apparatus

Info

Publication number: WO2017024843A1
Application number: PCT/CN2016/082526
Authority: WO
Inventors: 强宇红; 郑芳庭; 吴瑟
Original assignee: 中兴通讯股份有限公司
Priority date: 2015-08-10
Filing date: 2016-05-18
Publication date: 2017-02-16
Also published as: CN106454962A

Abstract

Disclosed are a context transfer method and apparatus. The method comprises: acquiring user information and/or receiving configured mobile data, the user information comprising all or some of historical location information of a user, the mobile data comprising geographic locations of the user at a series of successive time points; determining, on the basis of the user information and/or the mobile data, one or more candidate subsequent locations for migration of the user; and instructing a current serving node of the user or a network function entity that stores a context of the user to send context information of the user to a network node corresponding to the candidate subsequent location.

Description

Method and device for conveying context

Technical field

The present application relates to, but is not limited to, the field of user context information interaction between communication control functions in a mobile communication system.

Background technique

The 3GPP (3rd Generation Partnership Project) project for the next generation of mobile wireless networks is called System Architecture Evolution (SAE). The architecture of the SAE is shown in Figure 1, which includes the following network elements:

E-RAN (Evolved RAN): An evolved radio access network that can provide higher uplink and downlink rates, lower transmission delays, and more reliable wireless transmission. The network element included in the E-RAN is an eNodeB (Evolved Node B, eNB for short), which provides radio resources for terminal access.

HSS (Home Subscriber Server): A home subscriber server that permanently stores user subscription data.

MME (Mobility Management Entity): A control plane function entity that temporarily stores user data. It is responsible for managing and storing the User Equipment (UE) context (such as UE/user ID, mobility management status, and user). Security parameter, etc.), assigning a temporary identifier to the user, when the UE is camped in the tracking area or the network is responsible for authenticating the user; processing all non-access stratum messages between the MME and the UE; triggering paging in the SAE .

SGW (Serving Gateway): A service gateway. The gateway is a user plane entity responsible for user plane data routing processing and terminating downlink data of UEs in idle state. Manage and store the SAE bearer context of the UE, such as IP bearer service parameters and network internal routing information. It is the anchor point of the internal user plane of the 3GPP system. A user can only have one Serving GW at a time;

PGW (Packet Data Network Gateway): A packet data network gateway, which is responsible for the UE accessing the PDN gateway, assigning a user IP address, and is a mobility anchor of 3GPP and non-3GPP access systems. Users can access multiple PDN GWs at the same time.

Policy and Charging Rule Functionality (PCRF): A functional entity that controls the transmission of user data based on the service information and user subscription information and the configuration information of the operator. And billing rules. The functional entity can also control the establishment and release of bearers in the access network.

From the 2G era to the 4G mobile network, there are some geographically distributed nodes, such as MME, SGW, and eNodeB. These nodes provide wireless and wired network access functions for terminals in a certain geographical range. For the current service node. After the terminal moves out of the scope of the current service node, the terminal accesses the new wireless and wired control node, and the new node is called the destination service node. In order to achieve the purpose of correctly identifying and serving users, that is, providing services to users reasonably and qualitatively according to the service service level requested by the user, the service node needs to store at least two types of information, including user authentication, user category and service subscription obtained from the HSS. Such information, as well as other user-related temporary information generated during the business process, is collectively referred to as the user's context information. When the terminal moves, the destination service node needs to obtain the context information of the user from the current serving node or the HSS before providing the UE with the service service. The implementation of the related art is that after the UE autonomously searches and accesses the new destination service node, the destination service node searches for the context in which the local UE is not stored, and thus searches for the HSS or the previous serving node, and initiates a request for acquiring the UE context. . Only when the UE roams to the destination MME and sends an access request to the destination MME, the destination MME obtains the context and subscription information of the UE from the original serving MME and the S6 interface to the HSS through the S10 interface. The implementation of the related art often causes the destination service node to provide services after a period of time, and may reduce the service capability of the communication network in a service with high mobile low latency requirements.

At present, many organizations in the world have begun research on next-generation mobile networks. User end-to-end delay is a very important evaluation index. How to provide low-latency connection services when users frequently move at high speed is an important issue. .

Summary of the invention

The following is an overview of the topics detailed in this document. This Summary is not intended to limit the scope of the claims.

This document provides a method and apparatus for delivering a context. The current serving node actively and early pushes the UE context to provide a consistent low latency service for the mobile terminal to move at high speed.

A method of passing contexts, including:

Acquiring user information and/or receiving configured mobile data, the user information including all or part of historical location information of the user, the mobile data including a geographical location where the user is located at a continuous time point;

Determining one or more candidate subsequent locations of the user migration based on the user information and/or the movement data;

Notifying the service node where the user is currently located or the network function entity storing the user context sends the context information of the user to the network node corresponding to the candidate subsequent location.

Optionally, the sending, by the network function entity that the user is currently located, or the network function entity that stores the user context, the context information of the user to the network node corresponding to the candidate subsequent location includes:

Obtaining, according to network configuration data of the candidate subsequent location, a network node corresponding to the candidate subsequent location;

Sending the network node identifier corresponding to the candidate subsequent location to the service node where the user is currently located or the network function entity storing the user context, so that the service node where the user is currently located or the network function for storing the user context The entity sends the context information of the user to the network node corresponding to the candidate subsequent location according to the network node identifier.

Optionally, after determining the candidate subsequent locations of the one or more of the user migrations, the method further includes:

Sending, to the network node corresponding to the candidate subsequent location, a notification for acquiring the context information of the user, so that the network node corresponding to the candidate subsequent location is to the serving node where the user is currently located or the network function for storing the user context The entity obtains context information of the user.

The notification of acquiring the context information of the user includes an identifier of the service node where the user is currently located or a network function entity that stores the user context.

The user information further includes one or more of the following: a user type, a user terminal type, user subscription service information, service information used by the user, and user subscription information.

The context information of the user further includes one or more of the following: a user type, User terminal type, user subscription service information, mobility management context information, and user authentication information.

A device that conveys context, including:

An obtaining module, configured to: obtain user information and/or receive configured mobile data, where the user information includes all or part of historical location information of the user, and the mobile data includes the user at a continuous time point Geographic location

An analysis module, configured to: determine one or more candidate subsequent locations of the user migration based on the user information and/or the movement data;

The push module is configured to: notify the service node where the user is currently located or the network function entity that stores the user context to send the context information of the user to the network node corresponding to the candidate subsequent location.

Optionally, the acquiring module includes a receiving unit and a manual interaction unit, and the receiving unit is configured to: acquire user information, where the manual interaction unit is configured to: receive configured mobile data.

Optionally, the analysis module includes a configuration unit and a calculation unit, and the calculation unit is configured to: determine one or more candidate subsequent positions of the user migration based on the user information and/or the movement data; The configuration unit is configured to: obtain, according to network configuration data of the candidate subsequent location, a network node corresponding to the candidate subsequent location;

The push module includes a sending unit, and the sending unit is configured to: send a network node identifier corresponding to the candidate subsequent location to a service node where the user is currently located or a network function entity that stores the user context, so that the The network function entity in which the user is currently located or the network function entity storing the user context sends the context information of the user to the network node corresponding to the candidate subsequent location according to the network node identifier.

Optionally, the pushing module further includes a notification unit, where the notification unit is configured to: send a notification for acquiring the context information of the user to the network node corresponding to the candidate subsequent location, so that the candidate subsequent location corresponds to The network node acquires context information of the user to a service node where the user is currently located or a network function entity that stores the user context.

A computer readable storage medium storing computer executable instructions for performing the method of any of the above.

The method and device for transmitting context provided by the embodiment of the present invention acquires historical information of all or part of the UE (including but not limited to location information and speed, direction, etc.), and further analyzes, infers, and knows the movement of the UE, and infers Possible one or more candidate subsequent locations of the UE. According to the configuration data of the network, the network node corresponding to the candidate subsequent location can be obtained as the candidate destination service node, and the candidate destination service node ID list information is sent to the service node. The service node thus actively sends the key context of the UE (including but not limited to user authentication information) to the candidate service node, which can provide a better service experience for the mobile user.

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

BRIEF abstract

1 is a 4G architecture diagram in the related art;

2 is a flow chart of a method for delivering a context according to an embodiment of the present invention;

3 is a schematic structural diagram of an apparatus for transmitting a context according to an embodiment of the present invention;

4 is a diagram showing an example of a 4G network architecture according to Embodiment 1 of the present invention;

5 is a diagram showing an example of a 4G network architecture according to Embodiment 2 of the present invention;

6 is a diagram showing an example of a 4G network architecture according to Embodiment 3 of the present invention;

7 is a diagram showing an example of an abstract architecture of Embodiment 4 of the present invention;

8 is a diagram showing an example of an abstract architecture of Embodiment 5 of the present invention;

Figure 9 is a diagram showing an example of the flow of Embodiment 6 of the present invention;

Figure 10 is a diagram showing an example of the flow of Embodiment 7 of the present invention;

Figure 11 is a diagram showing an example of the flow of Embodiment 8 of the present invention.

Embodiments of the invention

The embodiments of the present invention will be described below with reference to the accompanying drawings. It should be noted that the features in the embodiments and the embodiments in the present application can be arbitrarily combined with each other without conflict.

As shown in FIG. 2, an embodiment of the present invention provides a method for delivering a context, including:

S1. Acquiring user information and/or receiving configured mobile data, the user information including all or part of historical location information of the user, the mobile data including a continuous time point The geographic location where the user is located;

S2. Determine, according to the user information and/or the mobile data, one or more candidate subsequent locations of the user migration;

S3. Notifying the service node where the user is currently located or the network function entity storing the user context sends the context information of the user to the network node corresponding to the candidate subsequent location.

Wherein, the step of storing the user information and/or the mobile data may be included after step S1.

Step S2 includes:

Wherein, step S3 includes one or two of function one and function two:

The function of the network node corresponding to the candidate subsequent location is sent to the service node where the user is currently located or the network function entity storing the user context, so that the service node where the user is currently located or the user context is stored. The network function entity sends the context information of the user to the network node corresponding to the candidate subsequent location according to the network node identifier.

The second function is to send a notification for acquiring the context information of the user to the network node corresponding to the candidate subsequent location, so that the network node corresponding to the candidate subsequent location is to the service node where the user is currently located or the user context is stored. The network function entity acquires context information of the user.

The user information may further include one or more of the following: a user type, a user terminal type, user subscription service information, service information used by the user, and user subscription information. The context information of the user may further include one or more of the following: a user type, a user terminal type, user subscription service information, mobility management context information, and user authentication information, and the notification of acquiring the context information of the user includes: The service node where the user is currently located or the identifier of the network function entity storing the user context.

The embodiment of the present invention further provides a computer readable storage medium storing computer executable instructions for executing the above method for delivering a context.

As shown in FIG. 3, an embodiment of the present invention provides a device for transmitting a context, which is set on an AAF (Behavior Analysis Function), and the AAF runs on an entity of the network and can be operated separately. It can also be used as part of other functional entities, including:

The obtaining module 11 is configured to: acquire user information and/or receive configured mobile data, where the user information includes all or part of historical location information of the user, and the mobile data includes the user at a continuous time point Geographic location

The analyzing module 12 is configured to: determine one or more candidate subsequent locations of the user migration based on the user information and/or the mobile data;

The push module 13 is configured to: notify the service node where the user is currently located or the network function entity that stores the user context to send the context information of the user to the network node corresponding to the candidate subsequent location.

The obtaining module 11 includes:

The receiving unit 111 is configured to: acquire user information;

The human interaction unit 112 is arranged to receive the configured mobile data.

The analysis module 12 includes:

The calculating unit 121 is configured to: determine one or more candidate subsequent positions of the user migration based on the user information and/or the movement data;

The configuration unit 122 is configured to: obtain the network node corresponding to the candidate subsequent location according to the network configuration data of the candidate subsequent location;

The push module optionally includes one of the following units, and may also include two units at the same time:

The sending unit 131 is configured to: send the network node identifier corresponding to the candidate subsequent location to the service node where the user is currently located or the network function entity that stores the user context, so that the service node or the storage where the user is currently located The network function entity of the user context sends the context information of the user to the network node corresponding to the candidate subsequent location according to the network node identifier.

The notification unit 132 is configured to: send a notification for acquiring the context information of the user to the network node corresponding to the candidate subsequent location, so that the network node corresponding to the candidate subsequent location is to the service node or the storage device where the user is currently located. The network function entity of the user context acquires context information of the user.

Example 1

FIG. 4 shows a network architecture embodiment 1 of the present invention in a 4G mobile network.

A function is added to the network, and the function is operated on an entity of the network, which is called AAF (behavior analysis function) in the embodiment of the present invention. AAF collects user information from the network and analyzes a large amount of user information to form a certain decision to guide the network to better serve users. The information obtained by the AAF from the network includes the user type, user terminal type, user subscription service information, user historical location information, service information used by the user, and subscription information. The AAF can obtain historical information of the user from network functions including the following network elements, such as MME (through the A1 interface), HSS (through the B1 interface), PCRF (through the C1 interface), and the like. The AAF can maintain and analyze the obtained large amount of user information, and determine that the UE may roam from one MME to another destination MME (or multiple MME lists) in the following time period, thereby triggering the current serving MME to key UE context ( For example, the UE mobility management context information, the authentication information, the subscription service information, the user type, the terminal type, and the like are forwarded to the destination MME (or multiple MME lists) in advance through the D1 interface. In this sentence, “triggering” means that the AAF sends a message to the current serving MME and/or the destination MME, so that the current serving MME sends a request to the destination MME, or causes the destination MME to send a request to the current serving MME, requesting that the UE context be from the current serving MME. Send to the destination MME.

Example 2

FIG. 5 shows a network architecture embodiment 2 of the present invention in a 4G mobile network.

In this example, the AAF function is also added. Compared with FIG. 2, the AAF not only obtains user information from the network element of the core network, but also obtains user information from the eNodeB of the access network (through the A2 interface). The AAF further analyzes the obtained information, and determines that the UE may roam from one eNodeB to another destination eNodeB (or multiple eNodeB lists) in the following time period, thereby triggering the current serving eNodeB to pass the key UE context. The D1 interface is forwarded to the destination eNodeB (or multiple eNodeB lists) in advance. In this sentence, “triggering” means that the AAF sends a message to the current serving eNodeB and/or the destination eNodeB, such that the current serving eNodeB sends a request to the destination eNodeB, or causes the destination eNodeB to send a request to the current serving eNodeB, requesting that the UE context be from the current serving eNodeB. Send to the destination eNodeB.

Example 3

FIG. 6 shows a network architecture embodiment 3 of the present invention in a 4G mobile network.

With respect to FIG. 5, the AAF function may not acquire user information from the HSS or the PCRF, but acquire user information from any other one or more network elements on the network to make a judgment of the UE roaming path. Shown in this example figure is that the AAF obtains UE information from the MME and the eNodeB.

Example 4

Figure 7 shows an abstract architecture embodiment 4 of the present invention in a mobile network.

The AAF function obtains user information from one or several functional entities NF11, NF12, and NF21 on the network. The NF11, NF12, and NF21 may be virtual network functions or traditional network elements on the virtual architecture, and are collectively referred to as network functions. NF11, NF12, and NF13 are the same type of network function, and NF21 is another network function. The AAF determines that the UE will move from the coverage of the NF11 to the coverage of the NF12 (NF12 or NF13) according to the obtained user history information. Therefore, the NF11 is triggered to transmit the key UE context to the NF12 in advance through the D1 interface, so as to improve the processing speed of the NF12. . "Trigger" means that the AAF sends a message to the current serving network function and/or the destination network function, so that the current serving network function actively sends a request to the destination network function, transmits the UE context to it, or causes the destination network service function to actively send a request to the current service. Network function to get the UE context from it. It is also possible for the AAF to determine that the UE will move from NF11 coverage to coverage of multiple network function lists (eg, NF12 or NF13), thus triggering NF11 to pass critical UE contexts to multiple network functions in advance through the D1 interface. In the abstract architecture embodiment of the present invention, the AAF can acquire information of the UE from more network functions, and is not limited to the description in the figure.

Example 5

Figure 8 shows an abstract architecture embodiment 5 of the present invention in a mobile network.

Different from FIG. 7 , a network function UCDB (user context database) for centrally storing UE context is added to the network, and NF11, NF12, and NF13 send the UE context to the UCDB for storage. When the AAF function determines that the UE will move from the NF11 coverage to the NF12 coverage, the UCDB is triggered to advance the key UE context to the NF12 in advance through the E1 interface. "Trigger" means that the AAF sends a message to the UCDB and/or the destination network function, so that the UCDB actively sends a request to the destination network function, transmits the UE context to it, or causes the destination network service function to actively send a request to the UCDB to acquire the UE context. Abstract architecture of the present invention In an embodiment, the AAF can acquire information of the UE from more network functions, and is not limited to the description in the figure.

Example 6

Figure 9 illustrates an embodiment of UE context transfer under the architecture embodiment of Figure 7.

In step 101, UE A moves to NF11 coverage, and NF11 provides service for UE A. The NF11 records the activity information of the UE in the network function and transmits the related information to the AAF function. Step 101 represents a request and response message sent by one or more pieces of information. Step 101 can occur at some point in time when UE A is within or outside of NF11 coverage.

In step 102, UE A moves to NF12 coverage, and NF12 provides service for UE A. The NF12 records the activity information of the UE in the network function and transmits the related information to the AAF function. Step 102 represents a request and response message sent by one or more pieces of information. Step 102 can occur at some point in time when UE A is within or outside of NF 12 coverage.

In step 103, the NF21 passes the information recorded by the UE in the network function to the AAF function. Step 103 represents a request and response message sent by either UE A information. Step 103 can occur at some point in time when UE A is within or outside the coverage of NF21.

In step 104, the user inputs some information related to the personal service through the service interface provided by the AAF, such as the starting point, destination, and the like of the day driving. The service interface includes, when not limited to, a web page.

In this embodiment, at least one of the steps 101, 102, 103, and 104 may be included, and multiple pieces may be included.

Step 105: The AAF uses the UE history information and the current information acquired in steps 101, 102, 103, and 104 to determine that the UE is likely to move from the NF12 coverage to the NF11 coverage.

In step 106, the AAF notifies the NF 12 to transfer the key context information of the UEA to the NF11.

In step 107, the AAF notifies the NF11 to acquire the key context information of the UEA from the NF12.

In this embodiment, at least one of the messages in steps 106, 107 may also be included.

In step 108, the NF 12 passes the key context information of the UE A to the NF11. Step 108 represents a request and response message sent by one or more contexts.

Example 7

Figure 10 illustrates an embodiment of UE context transfer under the architecture embodiment of Figure 8.

Step 201: After UE A moves to the coverage of NF11, NF11 provides service for UE A, and NF11 sends the context of the UE to the UCDB for backup. Step 201 represents a request and response message sent by one or more UE A contexts.

In step 202, the NF11 records the activity information of the UE in the network function, and transmits the related information to the AAF function. Step 202 represents a request and response message sent by one or more pieces of information. Step 202 can occur at some point in time when UE A is within or outside of NF11 coverage.

In step 203, UE A moves to NF12 coverage, and NF12 provides service for UE A. NF12 sends the context of the UE to the UCDB for backup. Step 203 represents a request and response message sent by one or more pieces of information.

Step 204: The NF12 records the activity information of the UE in the network function, and transmits the related information to the AAF function. Step 204 represents a request and response message sent by one or more pieces of information. Step 204 can occur at some point in time when UE A is within or outside of NF 12 coverage.

In step 205, the NF21 transmits the information recorded by the UE in the network function to the AAF function. Step 205 represents a request and response message sent by one or more pieces of information. Step 205 can occur at some point in time when UE A is within or outside of NF 21 coverage.

Step 206: The user inputs some information related to the personal service through the service interface provided by the AAF, such as the starting point, destination, and the like of the day driving. The service interface includes, but is not limited to, a web page.

In this embodiment, at least one of the steps 202, 204, 205, and 206 may be included, and multiple pieces may be included.

Step 207: The AAF uses the UE history information and the current information acquired in steps 202, 204, 205, and 206 to determine that the UE is likely to move from the NF12 coverage to the NF11 coverage.

In step 208, the AAF notifies the NF 12 to transmit the key context information of the UEA to the NF11.

In step 209, the AAF notifies the NF11 to acquire the key context information of the UEA from the NF12.

At least one of the messages in steps 208, 209 may be included in this embodiment.

In step 210, the NF 12 passes the key context information of the UE A to the NF11. Step 210 represents a request and response message sent by one or more contexts.

Example 8

Figure 11 shows an embodiment of UE context transfer under the architecture embodiment of Figure 8.

The difference from FIG. 10 is that in step 307, the AAF determines that UE A may move to one of a plurality of network functions.

Step 301: After UE A moves to the coverage of NF11, NF11 provides service for UE A, and NF11 sends the context of the UE to the UCDB for backup. Step 301 represents a request and response message sent by one or more UE A contexts.

Step 302: The NF11 records the activity information of the UE in the network function, and transmits the related information to the AAF function. Step 302 represents a request and response message sent by one or more pieces of information. Step 302 can occur at some point in time when UE A is within or outside of NF11 coverage.

In step 303, UE A moves to NF12 coverage, and NF12 provides service for UE A. NF12 sends the context of the UE to the UCDB for backup. Step 303 represents a request and response message sent by one or more pieces of information.

In step 304, the NF 12 records the activity information of the UE in the network function, and transmits the related information to the AAF function. Step 304 represents a request and response message sent by one or more pieces of information. Step 304 can occur at some point in time when UE A is within or outside of NF 12 coverage.

Step 305, the NF21 transmits the information recorded by the UE in the network function to the AAF function. Step 305 represents a request and response message sent by one or more pieces of information. Step 305 can occur at some point in time when UE A is within or outside of NF 21 coverage.

In step 306, the user inputs some information related to the personal service through the service interface provided by the AAF, such as the starting point, destination, and the like of the day driving. The service interface includes, when not limited to, a web page.

In this embodiment, at least one of the steps 302, 304, 305, and 306 is included, and multiple pieces may be included.

Step 307, the AAF uses the UE history information and current information acquired in steps 302, 304, 305, 306 to determine that the UE is likely to move from the NF12 coverage to the NF11 or NF13. Coverage.

In step 308, the AAF notifies the UCDB to transfer the key context information of the UEA to the NF11 and the NF13.

In step 309, the AAF notifies the NF11 to acquire the key context information of the UEA from the UCDB.

In step 310, the AAF notifies the NF 13 to acquire key context information of the UEA from the UCDB.

In this embodiment, at least one or a group of messages in the step 308, 309/310 step group may be included, and all messages may also be included.

In step 311, the UCDB delivers the key context information of the UE A to the NF11. Step 311 represents a request and response message sent by one or more contexts.

In step 312, the UCDB delivers the key context information of UE A to NF13. Step 312 represents a request and response message sent by one or more contexts.

One of ordinary skill in the art will appreciate that all or a portion of the steps of the above-described embodiments can be implemented using a computer program flow, which can be stored in a computer readable storage medium, such as on a corresponding hardware platform (eg, The system, device, device, device, etc. are executed, and when executed, include one or a combination of the steps of the method embodiments.

Alternatively, all or part of the steps of the above embodiments may also be implemented by using an integrated circuit. These steps may be separately fabricated into individual integrated circuit modules, or multiple modules or steps may be fabricated into a single integrated circuit module. achieve.

The devices/function modules/functional units in the above embodiments may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.

When the device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium. The above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.

The embodiments disclosed in the present invention are as described above, but the contents thereof are only for the purpose of facilitating understanding of the technical solutions of the present invention, and are not intended to limit the present invention. Any person skilled in the art to which the invention pertains may, without departing from the core technical solutions disclosed by the present invention, In the form and details of the invention, it is intended that the scope of the invention be defined by the scope of the appended claims.

Industrial applicability

Claims

A method of passing contexts, including:

Acquiring user information and/or receiving configured mobile data, the user information including all or part of historical location information of the user, the mobile data including a geographical location where the user is located at a continuous time point;

Determining one or more candidate subsequent locations of the user migration based on the user information and/or the movement data;

Notifying the service node where the user is currently located or the network function entity storing the user context sends the context information of the user to the network node corresponding to the candidate subsequent location.
The method of claim 1, wherein: notifying the service node currently located by the user or the network function entity storing the user context to send the context information of the user to the network node corresponding to the candidate subsequent location comprises:

Obtaining, according to network configuration data of the candidate subsequent location, a network node corresponding to the candidate subsequent location;

Sending the network node identifier corresponding to the candidate subsequent location to the service node where the user is currently located or the network function entity storing the user context, so that the service node where the user is currently located or the network function for storing the user context The entity sends the context information of the user to the network node corresponding to the candidate subsequent location according to the network node identifier.
The method of claim 1 wherein: determining one or more candidate subsequent locations for said user migration further comprises:

Sending, to the network node corresponding to the candidate subsequent location, a notification for acquiring the context information of the user, so that the network node corresponding to the candidate subsequent location is to the serving node where the user is currently located or the network function for storing the user context The entity obtains context information of the user.
The method of claim 3, wherein the obtaining the notification of the context information of the user comprises an identifier of the service node in which the user is currently located or a network function entity storing the user context.
The method of claim 1, wherein the user information further comprises one or more of the following: a user type, a user terminal type, user subscription service information, and a service letter used by the user. Information, user signing information.
The method of claim 1, wherein: the context information of the user further comprises one or more of the following: a user type, a user terminal type, user subscription service information, mobility management context information, and user authentication information.
A device that conveys context, including:

An obtaining module, configured to: obtain user information and/or receive configured mobile data, where the user information includes all or part of historical location information of the user, and the mobile data includes the user at a continuous time point Geographic location

An analysis module, configured to: determine one or more candidate subsequent locations of the user migration based on the user information and/or the movement data;

The push module is configured to: notify the service node where the user is currently located or the network function entity that stores the user context to send the context information of the user to the network node corresponding to the candidate subsequent location.
The apparatus according to claim 7, wherein: said obtaining module comprises a receiving unit and a human interaction unit, said receiving unit being configured to: acquire user information, said human interaction unit being arranged to receive the configured mobile data.
The apparatus of claim 7, wherein: said analysis module comprises a configuration unit and a computing unit, said computing unit configured to: determine one or more of said users based on said user information and/or said movement data a candidate subsequent location of the migration; the configuration unit is configured to: obtain, according to network configuration data of the candidate subsequent location, a network node corresponding to the candidate subsequent location;

The push module includes a sending unit, and the sending unit is configured to: send a network node identifier corresponding to the candidate subsequent location to a service node where the user is currently located or a network function entity that stores the user context, so that the The network function entity in which the user is currently located or the network function entity storing the user context sends the context information of the user to the network node corresponding to the candidate subsequent location according to the network node identifier.
The device of claim 7, wherein the push module further comprises a notification unit, the notification unit configured to: send a notification to acquire a context information of the user to a network node corresponding to the candidate subsequent location, so that a network node corresponding to the candidate subsequent location to the user The serving node currently located or the network function entity storing the user context acquires context information of the user.