WO2018161263A1 - 一种会话迁移方法及设备 - Google Patents

一种会话迁移方法及设备 Download PDF

Info

Publication number
WO2018161263A1
WO2018161263A1 PCT/CN2017/075904 CN2017075904W WO2018161263A1 WO 2018161263 A1 WO2018161263 A1 WO 2018161263A1 CN 2017075904 W CN2017075904 W CN 2017075904W WO 2018161263 A1 WO2018161263 A1 WO 2018161263A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
terminal device
management function
function entity
mobility management
Prior art date
Application number
PCT/CN2017/075904
Other languages
English (en)
French (fr)
Inventor
朱方园
李岩
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP17899598.1A priority Critical patent/EP3579589B1/en
Priority to CN201780056409.7A priority patent/CN109691150B/zh
Priority to PCT/CN2017/075904 priority patent/WO2018161263A1/zh
Publication of WO2018161263A1 publication Critical patent/WO2018161263A1/zh
Priority to US16/563,346 priority patent/US11082893B2/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0011Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0016Hand-off preparation specially adapted for end-to-end data sessions
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0011Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/08Reselecting an access point
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/24Reselection being triggered by specific parameters
    • H04W36/32Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/12Reselecting a serving backbone network switching or routing node
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W60/00Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration

Definitions

  • the embodiments of the present invention relate to the field of communications technologies, and in particular, to a session migration method and device.
  • next-generation wireless communication systems have emerged (for example, Narrowband-Internet of Thing (NB-IOT) systems).
  • data transmitted between a terminal device and a core network device may be small data, and a service for transmitting small data is generally referred to as a packet service.
  • the requirements of the packet service for the delay and the quality of service (QoS) are relatively low. Therefore, the session between the terminal device and the core network device does not need to be continuous.
  • the terminal device located in the first tracking area (TA) and the source core network device the service area of the source core device includes the first TA
  • a session is established between the terminal device and the terminal device.
  • the source core network device releases the session with the terminal device, and indicates that the terminal device sends the target core network device to the target core network device, where the service area of the target core network device includes the second TA.
  • a session establishment request is established to establish a session between the terminal device and the target core network device, so that the terminal device can transmit the data of the terminal device through the target core network device.
  • the session between the terminal device and the target core network device Before the session between the terminal device and the target core network device is established, the session between the source core network device and the terminal device has been released. Therefore, packet loss may occur for downlink data to be sent to the terminal device. phenomenon.
  • the terminal device moves to the second TA, a session between the terminal device and the target core network device is established. If the terminal device does not transmit data in the second TA, the core network resource is wasted and not Necessary signaling transmission.
  • the present invention provides a session migration method and device, which can ensure that the downlink data has no packet loss after the TA of the terminal device changes, and the waste of the core network resources and the signaling transmission can be reduced.
  • a session migration method is provided. First, the source session management function entity determines whether to update a session of the terminal device. Then, if it is determined to update the session of the terminal device, the source session management function entity reserves the source session management function entity and the terminal. a context of the first session that has been established between the devices, and sends the indication information to the first device, where the indication information is used to indicate that the first device triggers the establishment of the second session after waiting to obtain the data of the terminal device to be sent.
  • the device is a terminal device or a target mobility management function entity, and the second session is a session between the target session management function entity and the terminal device.
  • the source session management function entity retains the context of the first session before the second session is established, even if the downlink data to be sent to the terminal device is accurately transmitted to the terminal device, the downlink data is guaranteed to be free of packet loss.
  • the second session is triggered by the terminal device or the target mobility management function entity waiting to obtain the data of the terminal device to be sent, no untransmission occurs.
  • the data is transmitted to establish a second session, which reduces the waste of core network resources and reduces unnecessary signaling transmission.
  • the source session management function entity after the source session management function entity sends the indication information to the first device, the source session management function entity further receives the first notification message from the target mobility management function entity. In this way, the source session management function entity releases the context of the first session after receiving the first notification message.
  • the first device After the source session management function entity sends the indication information to the first device, the first device triggers the establishment of the second session after waiting to obtain the data of the terminal device to be transmitted. After the second session is established, the source session management function entity further receives the first notification message from the target mobility management function entity, and releases the context of the first session according to the first notification message, thereby reducing resource waste of the source session management function entity.
  • the source session management function entity may send the first response message carrying the indication information to the source mobility management function entity.
  • the indication information is sent to the terminal device, and the indication information is used to indicate that the terminal device sends information for triggering establishment of the second session to the target mobility management function entity after waiting to obtain the data of the terminal device to be transmitted.
  • the source session management function entity may send the first information carrying the indication information to the source mobility management function entity.
  • the response message is sent to the target mobility management entity, the indication information is used to indicate that the target mobility management function entity waits until the uplink data of the terminal device to be sent is obtained, and selects the target session management function entity to trigger the second session.
  • the method that the source session management function entity sends the indication information to the first device may further receive, by the source session management function entity, the uplink data from the terminal device, and obtain the uplink data.
  • the response message is sent, and the indication information is added to the uplink data response message, and the uplink data response message carrying the indication information is sent to the first device.
  • the method in which the source session management function entity sends the indication information is different.
  • the source session management function entity further receives, from the source mobility management function entity, a second notification message that carries the identifier of the target mobility management function entity.
  • the source session management function entity determines whether to update the session of the terminal device: the source session management function entity determines whether to update the session of the terminal device according to the first condition, where the first condition includes the source mobility management function entity.
  • the identity of the target is different from the identity of the target mobility management.
  • the foregoing first condition further includes: the data volume of the uplink data received by the source session management function entity in the preset time period is greater than or equal to a preset threshold.
  • a session management function entity is provided, the session management function entity being a source session management function entity.
  • the session management function entity includes a processing unit and a sending unit.
  • the processing unit is configured to determine whether to update a session of the terminal device, and to reserve a context of the first session if it is determined to update the session of the terminal device, where the first session is a source session management function a session that has been established between the entity and the terminal device; the sending unit is configured to: if the processing unit determines to update the session of the terminal device, send the indication information to the first device, where the indication information is used to indicate that the first device is waiting to obtain the to-be-sent The data of the terminal device then triggers the establishment of the second session, wherein the first device is a terminal device or a target mobility management function entity, and the second session is a session between the target session management function entity and the terminal device.
  • the session management function entity in the embodiment of the present application further includes a receiving unit, where the receiving unit is configured to: after the sending unit sends the indication information to the first device, The mobility management function entity receives the first notification message.
  • the processing unit is further configured to release the context of the first session after the receiving unit receives the first notification message.
  • the sending unit is specifically configured to send, to the source mobility management function entity, a first response message that carries the indication information, where The indication information is sent to the terminal device, and the indication information is used to indicate that the terminal device sends information for triggering establishment of the second session to the target mobility management function entity after waiting for the data of the terminal device to be transmitted.
  • the sending unit is specifically configured to send, to the source mobility management function entity, a first response message carrying the indication information, where the indication information is sent to the target mobility management entity, and the indication information is used. After the target mobility management function entity is instructed to wait for the uplink data of the terminal device to be transmitted, the target session management function entity is selected to trigger the establishment of the second session.
  • the session management function entity in the embodiment of the present application further includes a receiving unit, where the receiving unit is configured to receive uplink data from the terminal device, and obtain an uplink data response message.
  • the processing unit is further configured to: add the indication information to the uplink data response message that is obtained by the receiving unit, where the sending unit is configured to send, to the first device, an uplink data response message that carries the indication information.
  • the session management function entity in the embodiment of the present application further includes a receiving unit, where the receiving unit is configured to receive a second notification message from the source mobility management function entity, and second The notification message carries the identity of the target mobility management function entity.
  • the processing unit is configured to determine whether to update the session of the terminal device according to the first condition, where the first condition includes the identifier of the source mobility management function entity and the target mobility management carried by the second notification message received by the receiving unit.
  • the logo is different.
  • the first condition further includes that the data amount of the uplink data received by the receiving unit in the preset time period is greater than or equal to a preset threshold.
  • a session management function entity is provided, where the session management function entity is a source session management function entity, and the session management function entity includes: a processor, a memory, and a communication interface.
  • the memory is for storing computer program code, the computer program code includes instructions, and the processor, the communication interface and the memory are connected by a bus.
  • the processor executes the memory stored instructions to cause the session management function entity to perform the session migration method as in the first aspect above and any of its possible implementations.
  • a computer storage medium having stored therein computer program code.
  • the processor of the session management function entity in the third aspect executes the computer program code
  • the session management function entity performs a session migration method as in the first aspect described above and any of its possible implementations.
  • a fifth aspect further provides a computer program product comprising instructions, when run on a session management function entity, causing a session management function entity to perform a session migration method as in the first aspect above and any possible implementation thereof .
  • the name of the above-mentioned session management function entity does not limit the device or the function module itself. In actual implementation, these devices or function modules may appear under other names. As long as the functions of the respective devices or functional modules are similar to the present application, they are within the scope of the claims and their equivalents.
  • a session migration method is provided, and a first session is established between a terminal device and a source session management function entity, where a service area of the source session management function entity includes a first tracking area TA; and the terminal device moves from the first TA to the first After the second TA, the terminal device obtains the indication information, and sends, according to the indication information, information for triggering establishment of the second session to the target mobility management function entity, where the second session is a session between the target session management function entity and the terminal device.
  • the service area of the target mobility management function entity and the service area of the target session management function entity each include a second TA.
  • the method for the terminal device to obtain the indication information may be that the terminal device sends the first request message to the target mobility management function entity, and correspondingly, the terminal device performs the target mobility management function.
  • the entity receives the second response message carrying the indication information, and may also receive, by the terminal device, the uplink data response message carrying the indication information from the target mobility management function entity.
  • the terminal device receives the second response message carrying the indication information or receives the uplink data response message carrying the indication information
  • receives the uplink data response message carrying the indication information the foregoing is used for triggering.
  • the information about the establishment of the second session is a session establishment request
  • the method for the terminal device to send the information for triggering the establishment of the second session to the target mobility management function entity according to the indication information is: the terminal device waits to obtain according to the indication information. After the data of the terminal device to be transmitted, a session establishment request is sent to the target mobility management function entity.
  • the second session is triggered after the terminal device waits to obtain the data of the terminal device to be sent. Therefore, the second session is not formed but the core network resource is reduced. Waste, also reduces unnecessary signaling transmission.
  • the method for the terminal device to obtain the indication information may further receive, by the terminal device, the downlink data that carries the indication information.
  • the information used to trigger the establishment of the second session is a session establishment request or a An uplink registration message, such that the terminal device sends the information for triggering the establishment of the second session to the target mobility management function entity according to the indication information: the terminal device receives the identifier After the information is displayed, the session establishment request or the first uplink registration message is sent to the target mobility management function entity.
  • the indication information is used to indicate that the terminal device sends the session establishment request to the target mobility management function entity immediately after acquiring the indication information. Or the first uplink registration message to trigger the establishment of the second session.
  • the terminal device in the application scenario that the terminal device receives the downlink data that carries the indication information, if the foregoing information used to trigger the establishment of the second session is a session establishment request, The terminal device further sends a second uplink registration message to the target mobility management function entity, where the second registration message is used to indicate that the target mobility management function entity notifies the application server to update the downlink transmission path, where the downlink transmission path is used for transmission to be sent to the terminal device.
  • the path to the downstream data in the application scenario that the terminal device receives the downlink data that carries the indication information, if the foregoing information used to trigger the establishment of the second session is a session establishment request.
  • a terminal device comprising a processing unit, an obtaining unit, and a sending unit.
  • the processing unit is configured to establish a first session with the source session management function entity, where the service area of the source session management function entity includes a first tracking area TA, and the acquiring unit is configured to move the terminal device from the first TA to the second After the TA, the indication information is obtained.
  • the sending unit is configured to send, according to the indication information acquired by the acquiring unit, information for triggering establishment of the second session to the target mobility management function entity, where the second session is a target session management function entity.
  • the session with the terminal device, the service area of the target mobility management function entity and the service area of the target session management function entity each include a second TA.
  • the sending unit is further configured to send a first request message to the target mobility management function entity.
  • the acquiring unit is specifically configured to use the target mobility management function.
  • the entity receives a second response message carrying the indication information.
  • the acquiring unit is specifically configured to receive, from the target mobility management function entity, an uplink data response message carrying the indication information.
  • the information used to trigger the establishment of the second session is a session establishment request
  • the sending unit is specifically configured to wait to obtain the terminal device to be sent according to the indication information. After the data, a session establishment request is sent to the target mobility management function entity.
  • the acquiring unit is specifically configured to receive downlink data that carries the indication information.
  • the acquiring unit is specifically configured to receive downlink data that carries the indication information
  • the information used to trigger establishment of the second session is a session establishment request or a
  • the sending unit is configured to: after the obtaining unit receives the indication information, send the session establishment request or the first uplink registration message to the target mobility management.
  • the sending unit is further configured to send a second uplink registration message to the target mobility management function entity, where the second registration message is used to indicate the target mobility management function entity.
  • the application server is notified to update the downlink transmission path, and the downlink transmission path is a path for transmitting downlink data to be transmitted to the terminal device.
  • a terminal device comprising: a processor, a memory, and a communication interface.
  • the memory is for storing computer program code
  • the computer program code includes instructions
  • the processor, the communication interface and the memory are connected by a bus.
  • the processor executes instructions stored in the memory to cause the terminal device to perform the session migration method as in the sixth aspect above and any possible implementation thereof.
  • a computer storage medium having stored therein computer program code.
  • the processor of the terminal device in the eighth aspect executes the computer program code, the terminal device performs the session migration method as in the sixth aspect described above and any possible implementation thereof.
  • a computer program product comprising instructions which, when run on a terminal device, cause the terminal device to perform a session migration method as in the sixth aspect above and any of its possible implementations.
  • the name of the above terminal device is not limited to the device or the function module itself. In actual implementation, these devices or function modules may appear under other names. As long as the functions of the respective devices or functional modules are similar to the present application, they are within the scope of the claims and their equivalents.
  • the eleventh aspect provides a session migration method, after the target mobility management function entity obtains the indication information, and waits until the uplink data of the terminal device to be sent is obtained according to the obtained indication information, and selects the target session management function entity.
  • the second session is a session between the target session management function entity and the terminal device.
  • the second session Since the second session is triggered by the target mobility management function entity after waiting for the uplink data of the terminal device to be sent, the second session is not formed but the core network resource is reduced. Waste, also reduces unnecessary signaling transmission.
  • the method for the target mobility management function entity to obtain the indication information may send, by the target mobility management function entity, a second request message to the source mobility management function entity, correspondingly, the target The mobility management function entity receives a third response message carrying the indication information from the source mobility management function entity.
  • the method may also receive, by the target mobility management function entity, an uplink data response message carrying the indication information from the source session management function entity.
  • the target mobility management function entity further sends a first notification message to the source session management function entity, where the source session management function entity is indicated.
  • the context of the first session is released, wherein the first session is a session established by the terminal device with the source session management function entity before the mobile device moves.
  • a mobility management function entity is provided, where the mobility management function entity is the target mobility management function entity, and the mobility management function entity includes an acquisition unit and a processing unit.
  • the acquiring unit is configured to obtain the indication information
  • the processing unit is configured to: after obtaining the uplink data of the terminal device to be sent, according to the indication information acquired by the acquiring unit, select a target session management function entity to trigger the second The establishment of the session, the second session is the target session management function The session between the body and the terminal device.
  • the mobility management function entity in the embodiment of the present application further includes a sending unit, where the sending unit is configured to send a second request message to the source mobility management function entity;
  • the acquiring unit is configured to receive, from the source mobility management function entity, a third response message carrying the indication information.
  • the acquiring unit is specifically configured to receive, from the source session management function entity, an uplink data response message carrying the indication information.
  • the mobility management function entity in the embodiment of the present application further includes a sending unit, where the target mobility management function entity is to the source after the second session is established.
  • the session management function entity sends a first notification message, where the first notification message is used to indicate that the source session management function entity releases the context of the first session, where the first session is a session established by the terminal device with the source session management function entity before the mobile device.
  • a mobility management function entity is provided, where the mobility management function entity is a target mobility management function entity, where the mobility management function entity comprises: a processor, a memory, and a communication interface.
  • the memory is for storing computer program code, the computer program code includes instructions, and the processor, the communication interface and the memory are connected by a bus.
  • the processor executes instructions stored in the memory to cause the mobility management function entity to perform the session migration method as described in the eleventh aspect above and any of its possible implementations.
  • a computer storage medium having stored therein computer program code.
  • the processor of the mobility management function entity in the thirteenth aspect executes the computer program code, the mobility management function entity performs the session migration method as described in the eleventh aspect above and any possible implementation thereof.
  • a fifteenth aspect further provides a computer program product comprising instructions, when executed on a mobility management functional entity, causing a mobility management functional entity to perform a session as in the eleventh aspect above and any one of its possible implementations Migration method.
  • the name of the above mobile management function entity does not limit the device or the function module itself. In actual implementation, these devices or function modules may appear under other names. As long as the functions of the respective devices or functional modules are similar to the present application, they are within the scope of the claims and their equivalents.
  • the beneficial effects of the twelfth aspect, the thirteenth aspect, the fourteenth aspect, the fifteenth aspect, and various implementations thereof can be referred to the analysis of the beneficial effects in the eleventh aspect and various implementations thereof, No longer.
  • FIG. 1 is a schematic structural diagram of a conventional next generation wireless communication system
  • FIG. 2 is a schematic flowchart of a session migration in the prior art
  • FIG. 3 is a schematic flowchart 1 of a session migration method according to an embodiment of the present application.
  • FIG. 4 is a second schematic flowchart of a session migration method according to an embodiment of the present disclosure.
  • FIG. 5 is a schematic flowchart 3 of a session migration method according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic flowchart 4 of a session migration method according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic flowchart 5 of a session migration method according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic flowchart 6 of a session migration method according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic flowchart diagram 7 of a session migration method according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic flowchart 8 of a session migration method according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic flowchart nin of a session migration method according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic flowchart 10 of a session migration method according to an embodiment of the present disclosure.
  • FIG. 13 is a schematic flowchart 11 of a session migration method according to an embodiment of the present disclosure.
  • FIG. 14 is a schematic flowchart 12 of a session migration method according to an embodiment of the present disclosure.
  • FIG. 15 is a schematic flowchart diagram of a session migration method according to an embodiment of the present disclosure.
  • FIG. 16 is a schematic structural diagram 1 of a session management function entity according to an embodiment of the present application.
  • FIG. 17 is a second schematic structural diagram of a session management function entity according to an embodiment of the present disclosure.
  • FIG. 18 is a schematic structural diagram 1 of a terminal device according to an embodiment of the present disclosure.
  • FIG. 19 is a schematic structural diagram 1 of a terminal device according to an embodiment of the present disclosure.
  • FIG. 20 is a schematic structural diagram 1 of a mobility management function entity according to an embodiment of the present application.
  • FIG. 21 is a schematic structural diagram 2 of a mobility management function entity according to an embodiment of the present application.
  • the words “exemplary” or “such as” are used to mean an example, illustration, or illustration. Any embodiment or design described as “exemplary” or “for example” in the embodiments of the present application should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of the words “exemplary” or “such as” is intended to present the concepts in a particular manner.
  • next generation wireless communication system Similar to a common communication system, a terminal device in a next-generation wireless communication system is connected to an application server located in an external data network through a wireless access network device and a core network device.
  • the existing next generation wireless communication system includes a terminal device 10, a radio access network device 11, a core network device 12, and an application server 13.
  • the terminal device 10 is connected to the radio access network device 11, the radio access network device 11 is also connected to the core network device 12, and the core network device 12 is connected to the application server 13.
  • the connection between the multiple devices is a wireless connection.
  • a solid line is illustrated in FIG.
  • control plane function and the user plane function of the core network device 12 described above may be set independently or integrated in the same device.
  • control plane network element 120 is used to represent the device that can implement the control plane function of the core network device 12
  • user plane network element 121 is used to represent the device that can implement the user plane function of the core network device 12.
  • control plane network element 120 and the user plane network element 121 can be independently set. It can also be integrated on the same device.
  • the application server 13 is connected to the user plane network element 121.
  • the control plane network element 120 includes a mobility management function of the terminal device, a session management function, an Internet Protocol (IP) address allocation function between the networks, and a forwarding rule function for generating a gateway user plane.
  • the control plane network element 120 may be a Mobility Management Entity (MME), a Policy and Charging Rules Function (PCRF) entity, or an integrated MME function, PCRF.
  • MME Mobility Management Entity
  • PCRF Policy and Charging Rules Function
  • the control plane network element 120 can include a mobility management (MM) functional entity 120a and a session management (SM) functional entity 120b.
  • MM mobility management
  • SM session management
  • the mobility management function entity 120a and the session management function entity 120b may be set independently or integrated on the same device.
  • the mobility management function entity 120a is responsible for attaching, mobility management, updating of the TA, assigning a temporary identity (ID) to the terminal device, authenticating and authorizing the terminal device, and the like.
  • the session management function entity 120b is responsible for selecting the user plane network element 121, the migration of the user plane network element 121, the IP address allocation, and the like for the terminal device.
  • next generation wireless communication system shown in FIG. 1 further includes a User Data Management (UDM) device 14.
  • the UDM device 14 is connected to both the mobility management function entity 120a and the session management function entity 120b.
  • the mobility management function entity 120a may acquire the mobility management subscription data of the terminal device 10 from the UDM device 14, and the session management function entity 120b may acquire the session management subscription data of the terminal device 10 from the UDM device 14.
  • next-generation wireless communication system when the data transmission service between the terminal device 10 and the core network device 12 is a packet service, the packet service requirements and the QoS requirements are relatively low.
  • the session between the terminal device 10 and the core network device 12 need not be continuously continuous.
  • the TA is used to locate the location of the terminal device.
  • the control plane network element in the network is assigned a set of registered TAs, that is, a TA list.
  • the terminal device enters a new TA (the terminal device determines that the current TA is not included in the TA LIST), or when the periodic TA update timer of the terminal device expires, the terminal device initiates a TA update procedure. If the new TA is managed by another control plane network element, the triggering terminal initiates a TA update process across the control plane network element, and the session of the terminal device needs to be migrated.
  • FIG. 2 shows a migration process of a session of a terminal device in the prior art.
  • the service area of the radio access network device 11 and the service area of the core network device 12 both include the first TA.
  • the service area of the radio access network device 11' and the service area of the core network device 12' each include a second TA.
  • the terminal device 10 has established a first session with the core network device 12, and the core network device 12 stores the context of the first session.
  • the core network device 12 releases its first session with the terminal device 10, that is, the core network device 12 deletes the session context of the first session, and instructs the terminal device 10 A session establishment request is sent to the core network device 12' such that a second session is established between the terminal device 10 and the core network device 12', and the terminal device 10 can transmit the data of the terminal device A through the core network device 12'.
  • the terminal device 10 establishes a second session between the terminal device 10 and the core network device 12' after receiving the indication sent by the core network device 12, but the core network device 12 sends the terminal device 10 to the terminal device 10.
  • the first session between the core network device 12 and the terminal device 10 is released. Therefore, for downlink data to be sent to the terminal device 10, there may be no data transmission link for transmitting the downlink. The data may cause packet loss in the downlink data.
  • the terminal device 10 does not transmit data after moving to the second TA (ie, the uplink data is not sent, and the downlink data is not received), the second session is established between the terminal device 10 and the core network device 12'. This leads to waste of core network resources and unnecessary signaling transmission.
  • the embodiment of the present application provides a session migration method.
  • the session migration method if the first session has been established between the source session management function entity and a certain terminal device, the source session management function entity retains when the source session management function entity determines to update the session of the terminal device. a context of the first session, and sending indication information to the terminal device or the target mobility management function entity, to indicate that the terminal device or the target mobility management function entity triggers to establish the second session after waiting to obtain data of the terminal device to be sent,
  • the second session is a session between the terminal device and the target session management function entity.
  • the source session management function entity retains the context of the first session before the second session is established, even if the downlink data to be sent to the terminal device is accurately transmitted to the terminal device, the downlink data is guaranteed to be lost. package.
  • the second session is triggered by the terminal device or the target mobility management function entity after waiting to obtain the data of the terminal device to be sent, in the scenario where the data of the terminal device is not transmitted, there is no need to establish a second session. It reduces the waste of core network resources and reduces unnecessary signaling transmission.
  • the session migration method provided by the embodiment of the present application is applicable to a wireless communication system in which a packet service exists.
  • the wireless communication system can be the next generation wireless communication system described above.
  • the embodiment of the present application is described by taking a wireless communication system as the next-generation wireless communication system shown in FIG. 1 as an example.
  • the terminal device 10 in the embodiment of the present application may be a device that provides voice and/or data connectivity to a user, a handheld device with a wireless connection function, or other processing device connected to a wireless modem.
  • the wireless terminal can communicate with one or more core networks via a Radio Access Network (RAN).
  • RAN Radio Access Network
  • the wireless terminal can be a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal, or can be a portable, pocket, handheld, computer built-in or in-vehicle mobile device that is connected to the wireless device.
  • Internet exchange language and/or data such as mobile phones, tablets, laptops, netbooks, personal digital assistants (PDAs).
  • the wireless access device 11 in the embodiment of the present application may be an access point (AP), or an evolved base station (English: evolved Node Base Station, eNB for short), and may also be NR gNB, NR.
  • the gNB is a base station in the network of the fifth generation communication technology (5G). The embodiment of the present application does not specifically limit this.
  • control plane network element and the user plane network element can be set independently or integrated in the same device.
  • the embodiment of the present application is mainly described by taking the independent configuration of the control plane network element and the user plane network element as an example.
  • a method for creating a session for the terminal device can be classified into the following three types:
  • the mobile management function entity in the network sends an attach request carrying the permanent identifier of the terminal device and the data network name (DNN).
  • the mobility management function entity acquires the mobility management subscription data of the terminal device from the UDM device, authenticates the terminal device, allocates the temporary identity identifier to the terminal device, and selects the session management function entity.
  • the session management function entity selected by the mobility management function entity acquires the session management subscription data of the terminal device from the UDM device, creates a session for the terminal device according to the attachment request sent by the terminal device, and the capability information of the terminal device, and stores the context of the session.
  • the context of the session includes the identifier and IP address of the user plane network element allocated by the session management function entity for the terminal device. In this way, the terminal device can perform normal packet transmission services.
  • the attachment process and the session establishment process of the terminal device are independent of each other: after the terminal device is attached to the network, the session is established again, and the uplink data is sent after the session is established.
  • the mobility management function entity acquires the mobility management subscription data of the terminal device from the UDM device, authenticates the terminal device, and allocates the temporary identity identifier to the terminal device.
  • the terminal device sends a session establishment request to the mobility management function entity in the network.
  • the mobility management function entity selects the session management function entity, and sends a session establishment request to the selected session management function entity to request the session management function entity to create a session for the terminal device, that is, request the session management function entity. Assign the user plane network element and IP address to the terminal device.
  • the session management function entity obtains the session management subscription data of the terminal device from the UDM device. After the session management function entity establishes a session for the terminal device, the terminal device can perform a normal packet transmission service.
  • the attachment process of the terminal device and the session establishment process are independent of each other: after the terminal device is attached to the network, the terminal device directly sends the uplink data to trigger the control plane network element to establish a session for the terminal device.
  • the mobility management function entity authenticates the terminal device and allocates a temporary identity identifier to the terminal device, and the mobility management function entity can obtain the mobility management subscription data of the terminal device.
  • the terminal device After being attached to the network, the terminal device directly sends the uplink data, and the uplink data is in the form of the uplink data packet. Since the terminal device has not established a session at this time, the terminal device has not been assigned an IP address.
  • the uplink data packet is a non-IP packet. After receiving the uplink data packet, the mobility management function entity determines that the session context has not been created for the terminal device according to the source address of the uplink data packet.
  • the mobility management function entity selects a session management function entity and requests the session management function entity to create a session for the terminal device.
  • the session management function entity allocates the user plane network element and the IP address to the terminal device according to the session management subscription data of the terminal device.
  • the IP address is not returned to the terminal device, but is used to encapsulate the non-IP packet into an IP packet.
  • To the communication peer create a session context.
  • the session management function entity forwards the uplink data packet sent by the mobility management function entity to the user plane network element.
  • the user plane network element encapsulates the received uplink data packet according to the session context, and sends the encapsulated uplink data packet to the external network, and then the terminal device can perform normal packet transmission service.
  • the source session management function entity in the embodiment of the present application may instruct the terminal device to send the data to the target mobility management function entity after waiting for the data of the terminal device to be sent.
  • the information triggering the establishment of the second session may also instruct the terminal device to immediately send information for triggering the establishment of the second session to the target mobility management function entity after obtaining the indication information.
  • the source session management function entity in the embodiment of the present application may instruct the target mobility management function entity to wait for the uplink data of the terminal device to be sent to obtain the target session management function. Entity to trigger the establishment of the second session.
  • the embodiment of the present application is described by taking the mobility management function entity and the session management function entity independently as an example.
  • the embodiment of the present application indicates that the source radio access network device is represented by the base station 1, the source mobility management function entity is represented by MM 1, the source session management function entity is represented by SM1, and the source user plane network element is used by the user.
  • the face network element 1 indicates that the target radio access network device is represented by the base station 2, the target mobility management function entity is represented by MM 2, the target session management function entity is represented by SM 2, and the target user plane network element is used by the user plane network. Yuan 2 indicates.
  • FIG. 3 is a schematic flowchart of a session migration method according to an embodiment of the present application.
  • the session migration method may be applied to the next generation wireless communication system shown in FIG. 1.
  • the session migration method includes:
  • a first session is established between the S300 and the terminal device and the SM 1.
  • the service area of SM 1 includes the first TA, and SM 1 stores the context of the first session.
  • a first session is established between the terminal device and the SM 1 , and the MM 1 has been authenticated and authorized by the terminal device, and the terminal device is assigned a temporary ID.
  • the temporary ID is represented by the temporary ID 1 in the embodiment of the present application. Wait.
  • the SM 1 has selected the user plane network element 1 for the terminal device, and assigned the IP address and the like to the terminal device.
  • the method for establishing the first session may be that when the terminal device is attached to the network of the first TA, the MM 1 selects the SM 1, and the SM 1 creates a first session for the terminal device according to the session management subscription data of the terminal device, and stores the first session.
  • the uplink data is sent again.
  • the terminal device After the terminal device is attached to the network of the first TA, the terminal device directly sends the uplink data to trigger the MM 1 to establish the first session between the SM 1 and the terminal device. That is to say, the method for establishing the first session herein can refer to the above method 1, method 2 or method 3 for establishing a session.
  • S301 and SM1 determine whether to update the session of the terminal device.
  • the SM 1 determines whether to update the session of the terminal device according to the first condition.
  • the first condition includes that the identifier of the MM 1 is different from the identifier of the MM 2 .
  • the method for the SM 1 to obtain the identifier of the MM 2 is that after the first session is established between the SM 1 and the terminal device, the SM 1 is connected. Receiving a second notification message sent by MM 1 carrying the identifier of MM 2.
  • the first condition further includes that the data volume of the uplink data received by the SM 1 in the preset time period is greater than or equal to a preset threshold.
  • the uplink data received by the SM 1 in the preset time period may include uplink data sent by the terminal device, and may also include uplink data sent by other terminal devices that have established a session with the SM 1 .
  • the SM1 determines to update the session of the terminal device, the SM1 reserves the context of the first session, and sends the indication information to the first device.
  • the indication information is used to indicate that the first device triggers establishment of the second session after waiting to obtain data of the terminal device to be transmitted.
  • the first device is a terminal device or MM 2
  • the second session is a session between the SM 2 and the terminal device.
  • the indication information is specifically used to indicate that the terminal device sends a session establishment request to the MM 2 after waiting to obtain the data of the terminal device to be sent, to trigger the establishment of the second session, as shown in the following figure. 4 or FIG. 5 describes a specific process of the application scenario; or the indication information is specifically used to indicate that the terminal device sends a session establishment request to the MM 2 immediately after obtaining the indication information, to trigger the establishment of the second session.
  • the specific flow of the application scenario is described in FIG. 8; or the indication information is specifically used to indicate that the terminal device sends the first uplink registration message to the MM 2 immediately after acquiring the indication information, to trigger the establishment of the second session.
  • Figure 9 describes the specific flow of this application scenario.
  • FIG. 3 is denoted by S302a.
  • the indication information is specifically used to indicate that the MM 2 waits to obtain the uplink data sent by the terminal device, and selects the SM 2 to trigger the establishment of the second session, which is described in FIG. 6 or FIG. 7 below.
  • the specific process of this application scenario is specifically used to indicate that the MM 2 waits to obtain the uplink data sent by the terminal device, and selects the SM 2 to trigger the establishment of the second session, which is described in FIG. 6 or FIG. 7 below. The specific process of this application scenario.
  • FIG. 3 is represented by S302b.
  • the first device triggers establishment of the second session after waiting to obtain data of the terminal device to be sent according to the indication information.
  • S302a then performs S303a. If the first device is MM 2, S302b is followed by S303b.
  • the MM2 After the second session is established, the MM2 sends a first notification message to the SM1.
  • the MM 2 can send a first notification message to the SM 1.
  • the SM 1 releases the context of the first session.
  • the SM 1 in the embodiment of the present application retains the context of the first session before the second session is established. Therefore, even if the downlink data to be sent to the terminal device is sent to the terminal device, the downlink data is guaranteed to be lost. package.
  • the second session since the second session is triggered by the first device waiting for the data of the terminal device to be sent, the second session is not transmitted but the second session is established, thereby reducing the waste of the core network resources. Also reduces unnecessary signaling transmission.
  • the application of the present application describes each application scenario described above.
  • the session migration method provided by the embodiment of the present application includes:
  • S400 A first session is established between the terminal device and the SM 1.
  • the service area of the SM 1 includes the first TA, and the SM 1 stores the context of the first session.
  • a first session is established between the terminal device and the SM 1 , and the MM 1 has been authenticated and authorized by the terminal device, and the terminal device is assigned a temporary ID.
  • the temporary ID is represented by the temporary ID 1 in the embodiment of the present application. Wait.
  • the SM 1 has selected the user plane network element 1 for the terminal device, and assigned the IP address and the like to the terminal device.
  • the method for establishing the first session may be that when the terminal device is attached to the network of the first TA, the MM 1 selects the SM 1, and the SM 1 creates a first session for the terminal device according to the session management subscription data of the terminal device, and stores the first session.
  • the method for establishing the first session herein can refer to the above method 1 or method 2 of establishing a session.
  • the data of the terminal device is transmitted according to the first session.
  • the uplink data of the terminal device is transmitted along the terminal device ⁇ base station 1 ⁇ MM 1 ⁇ SM 1 ⁇ user plane network element 1.
  • the downlink data to be sent to the terminal device is transmitted along the user plane network element 1 ⁇ SM 1 ⁇ MM 1 ⁇ base station 1 ⁇ terminal device.
  • the context of the first session in the embodiment of the present application includes an IP address of the terminal device in the first session, address information of the user plane network element 1, and address information of the SM1 functional entity.
  • the base station serving the terminal device is updated from the base station 1 to the base station 2.
  • the terminal device After moving to the second TA, the terminal device detects whether the second TA is in its stored TA list (the TA list is the process of attaching the terminal device to the network, and the MM 1 is sent to the terminal device). If the second TA is not in the stored TA list, the terminal device transmits a first request message carrying the identifier of the first TA, the DNN, the identifier of the MM 1 and the temporary ID 1 of the terminal device to the base station 2.
  • the DNN is used to identify a data network in which the terminal devices are connected by the base stations 1, MM 1, and SM 1.
  • the first request message in the embodiment of the present application may be a Tracking Area Update (TAU) request message.
  • TAU Tracking Area Update
  • the base station 2 forwards the first request message in S401 to the MM 2.
  • the base station 2 Since there is no interface connection between the base station 2 and the MM 1, the base station 2 cannot address the MM 1 according to the MM 1 carried in the first request message. After the terminal device moves to the second TA, the base station 2 provides a service for the terminal device. Correspondingly, the base station 2 can obtain the location information of the terminal device. In this way, the base station 2 selects the MM 2 in the second TA for the terminal device according to the location information of the terminal device, and forwards the first request message to the MM 2.
  • the MM 2 sends a second request message to the MM 1 to request to acquire a mobility management context of the terminal device.
  • the mobility management of the terminal device in the embodiment of the present application is up and down.
  • Text refers to the context associated with mobility management.
  • the mobility management context of the terminal device includes mobility management subscription data of the terminal device.
  • the MM 2 determines the MM 1 according to the identifier of the MM 1 carried in the first request message it receives, and sends a second request message to the MM 1 to request to acquire the mobility management context of the terminal device.
  • the second request message carries the identity of the MM 2 and the temporary ID 1.
  • MM 1 and MM 2 belong to different TAs, there is a communication connection between MM 1 and MM 2. Therefore, MM 2 can directly send a second request message to MM 1.
  • the MM 1 searches for the stored mobility management context list, determines that the SM corresponding to the temporary ID 1 is the SM 1, and determines the permanent identifier of the terminal device corresponding to the temporary ID 1, and sends a second notification message to the SM1.
  • the notification SM 1 updates the identity of MM 1 in the context of its stored first session to the identity of MM 2.
  • the second notification message carries the identifier of the MM 2 and the permanent identifier of the terminal device.
  • the SM1 determines, according to the identifier of the MM 2, whether to update the session of the terminal device.
  • the SM 1 determines that the identifier of the MM 2 in the second notification message is different from the identifier of the MM 1 stored therein, and thus, the SM 1 determines that the terminal device has moved. SM 1 determines that the identity of MM 1 in the context of the first session is updated to the identity of MM 2 after the terminal device moves.
  • the SM 1 determines whether the current data transmission path meets the preset condition (the preset condition may be whether the hop count of the data transmission path is greater than or equal to the preset hop count) to determine whether to update the terminal device. a session; or, the SM 1 determines whether the data amount of the uplink data received by the SM 1 in the preset time period is greater than or equal to a preset threshold, so as to determine whether to update the session of the terminal device according to the determination result, where the preset time period is It refers to any time period in which the length of time is a preset length.
  • the SM1 determines to update the session of the terminal device. Conversely, the SM 1 determines that there is no need to update the session of the terminal device for the time being.
  • the SM1 determines that the data volume of the uplink data received by the SM1 in the preset time period is greater than or equal to a preset threshold. Conversely, the SM1 determines that there is no need to update the session of the terminal device for the time being.
  • the SM1 reserves the context of the first session, and sends a first response message carrying the indication information and the identifier of the SM1 to the MM1.
  • the SM 1 determines to update the session of the terminal device. .
  • the indication information in the embodiment is used to indicate that the terminal device sends a session establishment request to the MM 2 after waiting to obtain the data of the terminal device to be transmitted, to trigger the establishment of the second session.
  • the MM 1 sends a third response message carrying the indication information, the identifier of the SM1, the mobility management context of the terminal device, and the permanent identifier of the terminal device to the MM2.
  • the MM 2 stores the identifier of the SM 1 and the mobility management context of the terminal device, and allocates a new temporary ID to the terminal device (this embodiment uses the temporary ID 2 to indicate the new temporary ID).
  • the MM 2 sends a second response message carrying the indication information, the identifiers of the temporary ID 2 and the MM 2 to the base station 2.
  • the base station 2 forwards the second response message in S409 to the terminal device.
  • the terminal device After receiving the second response message carrying the indication information, the terminal device waits until the data of the terminal device to be sent is obtained, and sends a session establishment request to the MM 2 to trigger the second session between the terminal device and the SM 2 The establishment of.
  • the downlink data can be transmitted to the terminal device, and the downlink data is guaranteed, even if the user plane network element 1 receives the downlink data to be sent to the terminal device before the second session is established. The data is not lost.
  • the user plane network element 1 Since the SM 1 is connected to the MM 1, it can also be connected to the MM 2, and the SM 1 has learned that the terminal device has moved to the service area of the MM 2, and therefore, the user plane network element 1 receives the downlink data to be sent to the terminal device.
  • the downlink data may be transmitted along the user plane network element 1 ⁇ SM 1 ⁇ MM 2 ⁇ base station 2 ⁇ terminal device, or along the user plane network element 1 ⁇ SM 1 ⁇ MM 1 ⁇ MM 2 ⁇ base station 2 ⁇ terminal Device transfer (for example, in a roaming scenario). This embodiment of the present application does not specifically limit this.
  • the terminal device After waiting to obtain the data of the terminal device to be transmitted, the terminal device sends a session establishment request carrying the DNN and the session type information to the base station 2.
  • the uplink data may be in the form of an uplink data packet, and the uplink data packet sent by the terminal device may be an IP packet or a non-IP packet.
  • the session type information in the session establishment request is used to indicate the type of the uplink data packet (that is, whether the session is an IP type session).
  • the base station 2 forwards the session establishment request in S411 to the MM 2.
  • MM 2 performs authentication and authorization on the terminal device according to the mobility management context of the terminal device, and selects the DNN and the session type information carried by the session establishment request in S412 and the subscription data of the terminal device locally stored in the MM 2 for the terminal device.
  • SM 2 the mobility management context of the terminal device
  • the MM 2 sends a session establishment request to the SM2 and a permanent identifier of the terminal device.
  • the S415 and the SM2 obtain the session management subscription data of the terminal device according to the permanent identifier of the terminal device, and select the user plane network element 2 for the terminal device according to the session management subscription data of the terminal device.
  • the SM 2 sends a subscription data request to the UDM functional entity according to the permanent identifier of the terminal device, to obtain session management subscription data of the terminal device.
  • the SM-2 needs to allocate a new IP address to the terminal device.
  • the SM 2 sends a user plane forwarding rule to the user plane network element 2, and creates a context of the second session.
  • the SM 2 sends a session establishment response to the MM 2, the MM 2 sends a session establishment response to the base station 2, and the base station 2 sends a session establishment response to the terminal device.
  • the terminal device After the terminal device receives the above session establishment response, the establishment process of the second session ends.
  • the uplink data of the terminal device is transmitted along the terminal device ⁇ base station 2 ⁇ MM 2 ⁇ SM 2 ⁇ user plane network element 2.
  • the downlink data to be sent to the terminal device along the user plane network element 2 ⁇ SM 2 ⁇ MM 2 ⁇ Base station 2 ⁇ terminal device transmission.
  • the MM 2 may also send a first notification message to the SM 1 to instruct the SM 1 to release the context of the first session, thereby reducing resource waste of the source core network device.
  • the session migration method provided by the embodiment of the present application further includes S418 and S419.
  • the MM 2 sends a first notification message to the SM 1 to instruct the SM 1 to release the context of the first session.
  • the transmission path of the first notification message may be MM 2 ⁇ SM 1, and may also be MM 2 ⁇ MM 1 ⁇ SM 1, which is not specifically limited in this embodiment.
  • the session migration method provided by the embodiment of the present application includes:
  • a first session is established between the S500 and the terminal device and the SM 1.
  • the first request message carries the identifier of the first TA, the DNN, the identifier of the MM 1, and the temporary ID 1 of the terminal device.
  • the base station 2 forwards the first request message in S401 to the MM 2.
  • the MM 2 sends a second request message to the MM 1 to request to acquire a mobility management context of the terminal device.
  • the MM 1 searches for the stored mobility management context list, determines that the SM corresponding to the temporary ID 1 is the permanent identifier of the terminal device corresponding to the temporary ID 1, and sends a second notification message to the SM 1 to notify SM 1 updates the identity of MM 1 in the context of its stored first session to the identity of MM 2.
  • the second notification message carries the identifier of the MM 2 and the permanent identifier of the terminal device.
  • S505 and SM1 determine, according to the identifier of the MM 2, whether to update the session of the terminal device.
  • the SM 1 After receiving the second notification message, the SM 1 determines that the identifier of the MM 2 in the second notification message is different from the identifier of the MM 1 stored therein, and thus, the SM 1 determines that the terminal device has moved. SM1 determines that the identity of MM 1 in the context of the first session is updated to the identity of MM 2 after the terminal device moves.
  • the SM 1 determines whether to update the session of the terminal device.
  • the method for the SM 1 to determine whether to update the session of the terminal device may refer to the description of the above S405, and details are not described herein again.
  • the SM1 determines that the session of the terminal device does not need to be updated temporarily, the SM1 reserves the context of the first session, and sends a first response message carrying the identifier of the SM1 to the MM1.
  • the MM 1 sends a third response message carrying the identifier of the SM 1 , the mobility management context of the terminal device, and the permanent identifier of the terminal device to the MM 2 .
  • the MM 2 stores the identifier of the SM 1 and the mobility management context of the terminal device, and allocates the temporary ID 2 to the terminal device.
  • the MM 2 sends a second response message carrying the identifiers of the temporary ID 2 and the MM 2 to the base station 2.
  • the base station 2 forwards the second response message in S509 to the terminal device.
  • the SM 1 since the SM 1 retains the context of the first session, even before the second session is established, even if the user plane network element 1 receives the to-be-sent Downstream data to the terminal device, the downlink data can also be transmitted to the terminal device, ensuring that downlink data is not lost.
  • the SM 1 is connected to the MM 1 and can also be connected to the MM 2, and the SM 1 has learned that the terminal device has moved to the service area of the MM 2, and therefore, for the downlink data of the user plane network element 1 to be sent to the terminal device,
  • the downlink data may be transmitted along the user plane network element 1 ⁇ SM 1 ⁇ MM 2 ⁇ base station 2 ⁇ terminal device, or may be transmitted along the user plane network element 1 ⁇ SM 1 ⁇ MM1 ⁇ MM 2 ⁇ base station 2 ⁇ terminal device
  • the embodiment of the present application does not specifically limit this.
  • the SM 1 determines again whether to update the session of the terminal device.
  • S511 and SM1 determine whether to update the session of the terminal device.
  • the SM 1 has determined that the terminal device has moved in the above S505. Therefore, the SM 1 in S511 determines whether the data amount of the uplink data received by the SM 1 in the preset time period after S506 is greater than or equal to a preset threshold.
  • the SM 1 determines to update the session of the terminal device. If the data amount of the uplink data received by the SM 1 within the preset time period after S506 is less than the preset threshold, the SM 1 still determines that the session of the terminal device is not required to be updated temporarily.
  • the terminal device may send uplink data, and correspondingly, the SM 1 receives the uplink data, and sends the uplink data that it receives to the user plane network element 1. Then, the SM 1 receives the uplink data response message sent by the user plane network element 1.
  • the uplink data response message may be a message carrying an ACK.
  • the SM1 reserves the context of the first session, adds the indication information to the received uplink data response message, and sends an uplink data response message carrying the indication information to the MM2.
  • the indication information in the embodiment is used to indicate that the terminal device sends a session establishment request to the MM 2 after waiting to obtain the data of the terminal device to be transmitted, to trigger the establishment of the second session.
  • the base station 2 forwards an uplink data response message carrying the indication information to the terminal device.
  • the terminal device After receiving the uplink data response message carrying the indication information, the terminal device waits until it obtains After the data of the terminal device to be transmitted, a session establishment request is sent to the MM 2 to trigger the establishment of the second session between the terminal device and the SM 2.
  • the terminal device After waiting to obtain the data of the terminal device to be transmitted, the terminal device sends a session establishment request carrying the DNN and the session type information to the base station 2.
  • the base station 2 forwards the session establishment request in S515 to the MM 2.
  • the MM 2 authenticates and authorizes the terminal device according to the mobility management context of the terminal device, and according to the session establishment request in S516, the DNN and the session type information carried by the terminal device and the subscription data of the terminal device locally stored by the MM 2 are the terminal device.
  • the MM 2 sends a session establishment request to the SM2 and a permanent identifier of the terminal device.
  • the S519 and the SM2 obtain the session management subscription data of the terminal device according to the permanent identifier of the terminal device, and select the user plane network element 2 for the terminal device according to the session management subscription data of the terminal device.
  • S520 and SM2 send a user plane forwarding rule to the user plane network element 2, and create a context of the second session.
  • S521, SM2 sends a session establishment response to MM2, MM2 sends a session establishment response to base station 2, and base station 2 sends a session establishment response to the terminal device.
  • the MM 2 may also send a first notification message to the SM 1 to instruct the SM 1 to release the context of the first session, thereby reducing resource waste of the source core network device.
  • the session migration method provided by the embodiment of the present application further includes S522 and S523.
  • the MM 2 sends a first notification message to the SM 1 to instruct the SM 1 to release the context of the first session.
  • S500-S505 can refer to the description of S400-S405 in FIG. 4, and S515-S523 can refer to the description of S411-S419 in FIG. 4, and details are not described herein again.
  • the SM 1 in the embodiment shown in FIG. 4 or FIG. 5 retains the context of the first session before the second session is established, even if there is downlink data to be sent to the terminal device, it can be accurately transmitted to the terminal device. To ensure that there is no packet loss in the downlink data.
  • the target MM 2 is triggered. Therefore, the second session is not formed but the core network resource is reduced. The waste also reduces unnecessary signaling transmission.
  • the first session established between the terminal device and the SM 1 adopts the foregoing method 1 or method 2 of establishing a session.
  • the session migration method provided by the embodiment shown in FIG. 6 is applicable to an application scenario in which the terminal device establishes a first session between the terminal device and the SM 1 and the terminal device moves from the first TA to the second TA.
  • the indication information is used to indicate that the MM 2 selects the SM 2 after waiting for the uplink data of the terminal device to be sent to trigger the establishment of the second session.
  • the session migration method provided by the embodiment of the present application includes:
  • a first session is established between the S600 and the terminal device and the SM 1.
  • the first session is established by the terminal after the terminal device is attached to the network of the first TA.
  • the device directly sends the uplink data to trigger the MM 1 to establish a first session between the SM 1 and the terminal device.
  • the specific process of establishing the first session may refer to the foregoing method 3 of establishing a session.
  • the data of the terminal device is transmitted according to the first session.
  • the uplink data of the terminal device is transmitted along the terminal device ⁇ base station 1 ⁇ MM1 ⁇ SM1 ⁇ user plane network element 1.
  • the downlink data to be sent to the terminal device is transmitted along the user plane network element 1 ⁇ SM 1 ⁇ MM 1 ⁇ base station 1 ⁇ terminal device.
  • the first request message carries the identifier of the first TA, the identifier of the DNN, the MM 1, and the temporary ID 1.
  • the base station 2 forwards the first request message in S601 to the MM 2.
  • the MM 2 sends a second request message carrying the identifier of the MM 2 and the temporary ID 1 to the MM 1 to request to acquire the mobility management context of the terminal device.
  • the MM 1 searches for the stored mobility management context list, determines that the SM corresponding to the temporary ID 1 is SM 1, and determines the permanent identifier of the terminal device corresponding to the temporary ID 1, and sends the identifier carrying the MM 2 to the SM 1 and A second notification message of the permanent identification of the terminal device to inform the SM 1 to update the identity of the MM 1 in the context of the stored first session to the identity of the MM 2.
  • S605 and SM1 determine, according to the identifier of the MM2, whether to update the session of the terminal device.
  • the SM1 reserves the context of the first session, and sends a first response message carrying the indication information and the identifier of the SM1 to the MM1.
  • the indication information in the embodiment is used to indicate that the MM 2 selects the SM 2 after waiting to obtain the uplink data of the terminal device to be transmitted to trigger the establishment of the second session.
  • the MM 1 sends a third response message carrying the indication information, the identifier of the SM1, the mobility management context of the terminal device, and the permanent identifier of the terminal device to the MM2.
  • the MM 2 stores the identifier of the SM 1 and the mobility management context of the terminal device, and allocates the temporary ID 2 to the terminal device.
  • the MM 2 sends a second response message carrying the identifiers of the temporary ID 2 and the MM 2 to the base station 2.
  • the base station 2 forwards the second response message in S609 to the terminal device.
  • the downlink data can be transmitted to the terminal device even if the user plane network element 1 receives the downlink data to be sent to the terminal device before the second session is established. Downstream data is not lost.
  • the user plane network element 1 Since the SM 1 is connected to the MM 1, it can also be connected to the MM 2, and the SM 1 has learned that the terminal device has moved to the service area of the MM 2, and therefore, the user plane network element 1 receives the downlink data to be sent to the terminal device.
  • the downlink data may be transmitted along the user plane network element 1 ⁇ SM 1 ⁇ MM 2 ⁇ base station 2 ⁇ terminal device, or along the user plane network element 1 ⁇ SM 1 ⁇ MM1 ⁇ MM 2 ⁇ base station 2 ⁇ terminal device The embodiment of the present application does not specifically limit this.
  • the terminal device sends, to the base station 2, an uplink data packet that carries the identifiers of the temporary ID 2 and the MM 2.
  • the base station 2 forwards the uplink data packet in S611 to the MM 2.
  • the S613 and the MM 2 After receiving the uplink data packet, the S613 and the MM 2 use the mobility management context of the terminal device to verify and authorize the terminal device according to the indication information, and according to the subscription data of the terminal device and the data type of the uplink data packet, The terminal device selects SM 2.
  • the MM 2 sends a session establishment request to the SM2 and a permanent identifier of the terminal device.
  • the S615 and the SM2 obtain the session management subscription data of the terminal device according to the permanent identifier of the terminal device, and select the user plane network element 2 for the terminal device according to the session management subscription data of the terminal device.
  • the SM 2 sends a user plane forwarding rule to the user plane network element 2, and creates a context of the second session.
  • S618 and MM 2 send the uplink data packet received by the MM 2 in S612 to the SM 2, and the SM 2 forwards the uplink data packet to the user plane network element 2.
  • the establishment process of the second session ends.
  • the uplink data of the terminal device is transmitted along the terminal device ⁇ base station 2 ⁇ MM 2 ⁇ SM 2 ⁇ user plane network element 2.
  • the downlink data to be sent to the terminal device is transmitted along the user plane network element 2 ⁇ SM 2 ⁇ MM 2 ⁇ base station 2 ⁇ terminal device.
  • the MM 2 may also send a first notification message to the SM 1 to instruct the SM 1 to release the context of the first session, thereby reducing resource waste of the source core network device.
  • the session migration method provided by the embodiment of the present application further includes S619 and S620.
  • the MM 2 sends a first notification message to the SM 1 to instruct the SM 1 to release the context of the first session.
  • the transmission path of the first notification message may be MM 2 ⁇ SM 1, and may also be MM 2 ⁇ MM 1 ⁇ SM 1, which is not specifically limited in this embodiment.
  • the SM 1 in the embodiment of the present application may perform S618 first, then perform S619, or may perform S619 first, then perform S618, and may also perform S618 and S619 at the same time, which is not specifically limited in this embodiment of the present application.
  • the S600-S608 in this embodiment is similar to the S400-S408 in the embodiment shown in FIG. 4, except that the method used in establishing the first session in S600 in this embodiment is the same as the method used in establishing the first session in S400. Different from the method, the content indicated by the indication information in this embodiment is different from the content indicated by the indication information in the embodiment shown in FIG. 4.
  • the indication information in this embodiment indicates that the MM 2 waits until the uplink data of the terminal device to be transmitted is obtained, the SM 2 is selected to trigger the establishment of the second session. Therefore, compared with the embodiment shown in FIG. 4, In this embodiment, the indication information does not need to be sent to the terminal device, and the session establishment request is initiated by the MM2, and the session establishment request in FIG. 4 is initiated by the terminal device.
  • the session migration method provided by the embodiment of the present application may also determine that the session of the terminal device does not need to be updated.
  • the flow of the application scenario is shown in FIG. 7 in the embodiment of the present application.
  • the session migration method provided by the embodiment of the present application includes:
  • a first session is established between the S700 and the terminal device and the SM 1.
  • the first request message carries the identifier of the first TA, the identifier of the DNN, the MM 1, and the temporary ID 1.
  • the base station 2 forwards the first request message in S601 to the MM 2.
  • the MM 2 sends a second request message carrying the identifier of the MM 2 and the temporary ID 1 to the MM 1 to request to acquire the mobility management context of the terminal device.
  • the MM 1 searches for the stored mobility management context list, determines that the SM corresponding to the temporary ID 1 is the SM 1, and determines the permanent identifier of the terminal device corresponding to the temporary ID 1, and sends the identifier carrying the MM 2 to the SM 1 and A second notification message of the permanent identification of the terminal device to inform the SM 1 to update the identity of the MM 1 in the context of the stored first session to the identity of the MM 2.
  • S705 and SM1 determine, according to the identifier of the MM2, whether to update the session of the terminal device.
  • the SM1 determines that the session of the terminal device does not need to be updated temporarily, the SM1 reserves the context of the first session, and sends a first response message carrying the identifier SM1 of the SM1 to the MM1.
  • MM1 sends a third response message carrying the identifier of the SM1, the mobility management context of the terminal device, and the permanent identifier of the terminal device to the MM2.
  • the MM 2 stores the identifier of the SM 1 and the mobility management context of the terminal device, and allocates the temporary ID 2 to the terminal device.
  • the MM 2 sends a second response message carrying the identifiers of the temporary ID 2 and the MM 2 to the base station 2.
  • the base station 2 forwards the second response message in S709 to the terminal device.
  • the SM 1 since the SM 1 retains the context of the first session, even before the second session is established, even if the user plane network element 1 receives the to-be-sent Downstream data to the terminal device, the downlink data can also be transmitted to the terminal device, ensuring that downlink data is not lost.
  • the SM 1 is connected to the MM 1 and can also be connected to the MM 2, and the SM 1 has learned that the terminal device has moved to the service area of the MM 2, and therefore, for the downlink data of the user plane network element 1 to be sent to the terminal device,
  • the downlink data may be transmitted along the user plane network element 1 ⁇ SM 1 ⁇ MM 2 ⁇ base station 2 ⁇ terminal device, or may be transmitted along the user plane network element 1 ⁇ SM 1 ⁇ MM1 ⁇ MM 2 ⁇ base station 2 ⁇ terminal device
  • the embodiment of the present application does not specifically limit this.
  • the SM 1 determines again whether to update the session of the terminal device.
  • S711 and SM1 determine whether to update the session of the terminal device.
  • the terminal device may send uplink data, and correspondingly, the SM 1 receives the uplink data, and sends the uplink data that it receives to the user plane network element 1. Then, the SM 1 receives the uplink data response message sent by the user plane network element 1.
  • the SM1 reserves the context of the first session, adds the indication information to the received uplink data response message, and sends an uplink data response message carrying the indication information to the MM2.
  • the indication information in the embodiment is used to indicate that the MM 2 selects the SM 2 after waiting for the uplink data of the terminal device to be transmitted to trigger the establishment of the second session.
  • S713 and MM 2 send an uplink data response message to the base station 2.
  • the base station 2 sends an uplink data response message to the terminal device.
  • the terminal device sends, to the base station 2, an uplink data packet that carries the identifiers of the temporary ID 2 and the MM 2.
  • the base station 2 forwards the uplink data packet in S715 to the MM 2.
  • the S717 and the MM 2 After receiving the uplink data packet, the S717 and the MM 2 perform verification and authorization on the terminal device by using the mobility management context of the terminal device according to the indication information carried in the uplink and downlink data response message received by the terminal device, and according to the subscription data of the terminal device. And information such as the data type of the uplink data packet, and the SM 2 is selected for the terminal device.
  • S718 and MM 2 send a session establishment request to the SM2 and a permanent identifier of the terminal device.
  • the S719 and the SM2 obtain the session management subscription data of the terminal device according to the permanent identifier of the terminal device, and select the user plane network element 2 for the terminal device according to the session management subscription data of the terminal device.
  • S720 and SM2 send a user plane forwarding rule to the user plane network element 2, and create a context of the second session.
  • S721, SM 2 send a session establishment response to MM 2.
  • S722 and MM 2 send the uplink data packet received by the MM 2 in S716 to the SM 2, and the SM 2 forwards the uplink data packet to the user plane network element 2.
  • the establishment process of the second session ends.
  • the uplink data of the terminal device is transmitted along the terminal device ⁇ base station 2 ⁇ MM 2 ⁇ SM 2 ⁇ user plane network element 2.
  • the downlink data to be sent to the terminal device is transmitted along the user plane network element 2 ⁇ SM 2 ⁇ MM 2 ⁇ base station 2 ⁇ terminal device.
  • the MM 2 may also send a first notification message to the SM 1 to instruct the SM 1 to release the context of the first session, thereby reducing resource waste of the source core network device.
  • the session migration method provided by the embodiment of the present application further includes S723 and S724.
  • the MM 2 sends a first notification message to the SM 1 to instruct the SM 1 to release the context of the first session.
  • the transmission path of the first notification message may be MM 2 ⁇ SM 1, and may also be MM 2 ⁇ MM 1 ⁇ SM 1, which is not specifically limited in this embodiment.
  • the SM 1 in the embodiment of the present application may perform S723 first, then perform S724, or may perform S724 first, then perform S723, and may also perform S723 and S724 at the same time, which is not specifically limited in this embodiment of the present application.
  • the S700-S712 in this embodiment is similar to the S500-S512 in FIG. 5, except that the indication information in this embodiment is used to indicate that the MM 2 selects the SM after waiting for the uplink data of the terminal device to be sent. 2, to trigger the establishment of the second session.
  • the indication information in the embodiment shown in FIG. 5 is used to indicate that the terminal device sends a session to the MM 2 after waiting for the data of the terminal device to be sent. A request is made to trigger the establishment of a second session.
  • S700-S705 may refer to the description of S600-S605 in FIG. 6, and S715-S724 may refer to the description of S611-S620 in FIG. 6, and details are not described herein again.
  • the SM 1 in the embodiment shown in FIG. 6 or FIG. 7 retains the context of the first session before the second session is established, even if there is downlink data to be transmitted to the terminal device, it can be accurately transmitted to the terminal device. To ensure that there is no packet loss in the downlink data.
  • the second session since the second session is triggered by the MM 2 waiting for the uplink data of the terminal device to be sent, the second session is not transmitted but the second session is not established, thereby reducing the waste of the core network resources. Also reduces unnecessary signaling transmission.
  • the terminal device does not perceive the process of session migration, and further reduces the signaling transmission of the terminal device.
  • the SM 1 determines whether to update the terminal device by determining whether the data amount of the uplink data received within the preset time period after S506 is greater than or equal to a preset threshold. Conversation.
  • the SM 1 can also determine whether to update the session of the terminal device by determining whether the data amount of the downlink data received within the preset time period after S506 is greater than or equal to a preset threshold.
  • the embodiment of the present application shows in FIG. 8 whether the SM 1 determines whether to update the terminal by determining whether the data amount of the downlink data received within the preset time period after S506 is greater than or equal to a preset threshold.
  • the process of the device session is the application scenario.
  • the session migration method provided by the embodiment of the present application includes:
  • a first session is established between the S800 and the terminal device and the SM 1.
  • the first request message carries the identifier of the first TA, the DNN, the identifier of the MM 1, and the temporary ID 1 of the terminal device.
  • the base station 2 forwards the first request message in S401 to the MM 2.
  • the MM 2 sends a second request message to the MM 1 to request to acquire a mobility management context of the terminal device.
  • MM1 searches for the stored mobility management context list, determines that the SM corresponding to the temporary ID 1 is the permanent identifier of the terminal device corresponding to the temporary ID 1, and sends a second notification message to the SM 1 to notify SM 1 updates the identity of MM 1 in the context of its stored first session to the identity of MM 2.
  • the second notification message carries the identifier of the MM 2 and the permanent identifier of the terminal device.
  • S805 and SM1 determine, according to the identifier of the MM 2, whether to update the session of the terminal device.
  • SM1 determines that the session of the terminal device is not needed to be updated temporarily, SM1 reserves the context of the first session, and sends a first response message carrying the identifier of SM1 to MM1.
  • the MM 1 sends a third response message carrying the identifier of the SM1, the mobility management context of the terminal device, and the permanent identifier of the terminal device to the MM2.
  • S808 and MM 2 store the identifier of the SM 1 and the mobility management context of the terminal device, and are the terminal The device assigns a temporary ID of 2.
  • the MM 2 sends a second response message carrying the identifiers of the temporary ID 2 and the MM 2 to the base station 2.
  • the base station 2 forwards the second response message in S809 to the terminal device.
  • the downlink data can be transmitted to the terminal device, and the downlink data is guaranteed, even if the user plane network element 1 receives the downlink data to be sent to the terminal device before the second session is established. The data is not lost.
  • the SM 1 is connected to the MM 1 and can also be connected to the MM 2, and the SM 1 has learned that the terminal device has moved to the service area of the MM 2, and therefore, for the downlink data of the user plane network element 1 to be sent to the terminal device,
  • the downlink data may be transmitted along the user plane network element 1 ⁇ SM 1 ⁇ MM 2 ⁇ base station 2 ⁇ terminal device, or may be transmitted along the user plane network element 1 ⁇ SM 1 ⁇ MM1 ⁇ MM 2 ⁇ base station 2 ⁇ terminal device
  • the embodiment of the present application does not specifically limit this.
  • the SM 1 determines again whether to update the session of the terminal device.
  • S811, SM1 determine whether to update the session of the terminal device.
  • the SM 1 has determined that the terminal device has moved in the above S805. Therefore, the SM 1 in the S811 determines whether the data amount of the downlink data received by the SM 1 in the preset time period after S806 is greater than or equal to a preset threshold.
  • the SM 1 determines to update the session of the terminal device. If the data amount of the downlink data received by the SM 1 within the preset time period after S806 is less than the preset threshold, the SM 1 still determines that the session of the terminal device is not required to be updated temporarily.
  • the SM 1 may receive downlink data to be sent to the terminal device, where the downlink data is data sent by the user plane network element 1 to the SM 1.
  • the SM1 reserves the context of the first session, adds the indication information to the received downlink data to be sent to the terminal device, and sends the downlink carrying the indication information to the MM2. data.
  • the indication information in the embodiment is used to indicate that the terminal device sends a session establishment request to the MM 2 immediately after acquiring the indication information to trigger the establishment of the second session.
  • the SM 1 in this embodiment determines that the session of the terminal device is updated under the premise that the data amount of the downlink data to be sent to the terminal device is greater than or equal to the preset threshold within a certain period of time. .
  • a second session needs to be established immediately to transmit downlink data to be sent to the terminal device according to the second session.
  • the MM 2 After receiving the downlink data carrying the indication information, the MM 2 transmits the downlink data carrying the indication information to the terminal device.
  • the terminal device since the terminal device does not send uplink data after moving to the second TA, the terminal device may be in an idle state or may be in a connected state. If the terminal device is in an idle state, after S812, S813-S814 is performed, and after S814, S815 is performed; if the terminal device is in the connected state, then after S812, S814 is performed. Since S813-S814 is optional, it is indicated by a broken line in FIG.
  • S813 and MM 2 send a paging message to the terminal device.
  • the terminal device sends a paging response to the MM 2.
  • S815 and MM 2 transmit, to the base station 2, the downlink data that is received by the indication information that is received at S812.
  • the base station 2 sends downlink data carrying the indication information to the terminal device.
  • the terminal device sends a downlink data response message to the base station 2, the base station 2 forwards the downlink data response message to the MM2, and the MM2 forwards the downlink data response message to the SM1, and the SM1 forwards the downlink data response to the user plane network element 1. Message.
  • S817 is an optional step, and is indicated by a broken line in FIG.
  • the terminal device sends a session establishment request carrying the DNN and the session type information to the base station 2 according to the indication information carried in the downlink data that is received by the S816.
  • the base station 2 forwards the session establishment request in S818 to the MM 2.
  • the S820 and the MM 2 authenticate and authorize the terminal device according to the mobility management context of the terminal device, and according to the session establishment request in S819, the DNN and the session type information carried, and the subscription data of the terminal device locally stored by the MM 2, are the terminal device.
  • MM 2 send a session establishment request to the SM 2 and a permanent identity of the terminal device.
  • S822 and SM2 obtain the session management subscription data of the terminal device according to the permanent identifier of the terminal device, and select the user plane network element 2 for the terminal device according to the session management subscription data of the terminal device.
  • S823 and SM2 send a user plane forwarding rule to the user plane network element 2, and create a context of the second session.
  • SM2 send a session establishment response to MM2
  • MM2 sends a session establishment response to base station 2
  • base station 2 sends a session establishment response to the terminal device.
  • the MM 2 may also send a first notification message to the SM 1 to instruct the SM 1 to release the context of the first session, thereby reducing resource waste of the source core network device.
  • the session migration method provided by the embodiment of the present application further includes S825 and S826.
  • the MM 2 sends a first notification message to the SM 1 to instruct the SM 1 to release the context of the first session.
  • S800-S810 can refer to the description of S500-S510 in FIG. 5, and S819-S826 can refer to the description of S516-S523 in FIG. 5, and details are not described herein again.
  • the terminal device further sends a second uplink registration message to the MM 2, and the MM 2 receives the After the second uplink registration message, the second uplink registration message is sent to the user plane network element 2 through the SM2, and after receiving the second uplink registration message, the user plane network element 2 forwards the second uplink to the application server.
  • the registration message is convenient for the application server to update the forwarding path of the downlink data to be sent to the terminal device. This process is not shown in FIG.
  • the indication information is used to indicate that the terminal device sends a session establishment request to the MM 2 immediately after acquiring the indication information, to trigger the establishment of the second session.
  • the session migration method provided by the embodiment of the present application is as shown in FIG. 8 .
  • the indication information may also be used to indicate that the terminal device sends the first uplink registration message to the MM 2 immediately after obtaining the indication information, so as to trigger the establishment of the second session.
  • Figure 9 shows the flow of this case.
  • the session migration method provided by the embodiment of the present application includes:
  • a first session is established between the S900 and the terminal device and the SM 1.
  • the first request message carries the identifier of the first TA, the identifier of the DNN, the MM 1, and the temporary ID 1.
  • the base station 2 forwards the first request message in S601 to the MM 2.
  • the MM 2 sends a second request message carrying the identifier of the MM 2 and the temporary ID 1 to the MM 1 to request to acquire the mobility management context of the terminal device.
  • the MM 1 searches for the stored mobility management context list, determines that the SM corresponding to the temporary ID 1 is SM 1, and determines the permanent identifier of the terminal device corresponding to the temporary ID 1, and sends the identifier carrying the MM 2 to the SM 1 and A second notification message of the permanent identification of the terminal device to inform the SM 1 to update the identity of the MM 1 in the context of the stored first session to the identity of the MM 2.
  • S905 and SM1 determine, according to the identifier of the MM2, whether to update the session of the terminal device.
  • the SM1 determines that the session of the terminal device does not need to be updated temporarily, the SM1 reserves the context of the first session, and sends a first response message carrying the identifier SM1 of the SM1 to the MM1.
  • the MM1 sends a third response message carrying the identifier of the SM1, the mobility management context of the terminal device, and the permanent identifier of the terminal device to the MM2.
  • MM 2 stores the identifier of the SM 1 and the mobility management context of the terminal device, and allocates the temporary ID 2 to the terminal device.
  • S909 and MM 2 send a second response message carrying the identifiers of the temporary ID 2 and the MM 2 to the base station 2.
  • the base station 2 forwards the second response message in S910 to the terminal device.
  • the downlink data can be transmitted to the terminal device, and the downlink data is guaranteed, even if the user plane network element 1 receives the downlink data to be sent to the terminal device before the second session is established. The data is not lost.
  • the SM 1 is connected to the MM 1 and can also be connected to the MM 2, and the SM 1 has learned that the terminal device has moved to the service area of the MM 2, and therefore, for the downlink data of the user plane network element 1 to be sent to the terminal device,
  • the downlink data may be transmitted along the user plane network element 1 ⁇ SM 1 ⁇ MM 2 ⁇ base station 2 ⁇ terminal device, or may be transmitted along the user plane network element 1 ⁇ SM 1 ⁇ MM1 ⁇ MM 2 ⁇ base station 2 ⁇ terminal device
  • the embodiment of the present application does not specifically limit this.
  • the SM 1 determines again whether to update the session of the terminal device.
  • S911 and SM1 determine whether to update the session of the terminal device.
  • the SM 1 has determined that the terminal device has moved in the above S905. Therefore, the SM 1 in the S911 determines whether the data amount of the downlink data received by the SM 1 in the preset time period after S906 is greater than or equal to a preset threshold.
  • the SM 1 determines to update the session of the terminal device. If the data amount of the downlink data received by the SM 1 within the preset time period after S906 is less than the preset threshold, the SM 1 still determines that the session of the terminal device is not required to be updated temporarily.
  • the SM 1 may receive downlink data to be sent to the terminal device, where the downlink data is data sent by the user plane network element 1 to the SM 1.
  • the SM1 reserves the context of the first session, adds the indication information to the received downlink data to be sent to the terminal device, and sends the downlink carrying the indication information to the MM2. data.
  • the indication information in the embodiment is used to indicate that the terminal device sends the first uplink registration message to the MM 2 immediately after acquiring the indication information, so as to trigger the establishment of the second session.
  • the MM 2 After receiving the downlink data carrying the indication information, the MM 2 transmits the downlink data carrying the indication information to the terminal device.
  • the terminal device since the terminal device does not send uplink data after moving to the second TA, the terminal device may be in an idle state or may be in a connected state. For example, if the terminal device is in an idle state, after S912, S913-S914 is performed; if the terminal device is in the connected state, then after S912, S914 is performed. Since S913-S914 is optional, it is indicated by a broken line in FIG.
  • S913 and MM 2 send a paging message to the terminal device.
  • the terminal device sends a paging response to the MM 2.
  • S915 and MM 2 send downlink data carrying the indication information to the base station 2.
  • the base station 2 sends downlink data carrying the indication information to the terminal device.
  • the terminal device sends a downlink data response message to the base station 2, the base station 2 forwards the downlink data response message to the MM2, and the MM2 forwards the downlink data response message to the SM1, and the SM1 forwards the downlink data response to the user plane network element 1. Message.
  • S917 is an optional step, and is indicated by a broken line in FIG.
  • the terminal device sends, to the base station 2, a first uplink registration message that carries the identifiers of the temporary ID 2 and the MM 2.
  • the base station 2 sends the first uplink registration message in S918 to the MM 2.
  • the S920 and the MM 2 After receiving the first uplink registration message, the S920 and the MM 2 authenticate and authorize the terminal device according to the mobility management context of the terminal device, and use the information of the subscription data of the terminal device and the data type of the first uplink registration message as the terminal.
  • the device selects SM 2.
  • S921 and MM 2 send a session establishment request to the SM2 and a permanent identifier of the terminal device.
  • the S922 and the SM 2 obtain the session management subscription data of the terminal device according to the permanent identifier of the terminal device, and select the user plane network element 2 for the terminal device according to the session management subscription data of the terminal device.
  • S923 and SM2 send a user plane forwarding rule to the user plane network element 2, and create a context of the second session.
  • S924 SM 2 sends a session establishment response to MM 2, MM 2 sends a session establishment response to base station 2, and base station 2 transmits a session establishment response to the terminal device.
  • S925 and MM 2 send the first uplink registration message received by the MM 2 in the S919 to the SM 2, and the SM 2 forwards the first uplink registration message to the user plane network element 2.
  • the MM 2 may also send a first notification message to the SM 1 to instruct the SM 1 to release the context of the first session, thereby reducing resource waste of the source core network device.
  • the session migration method provided by the embodiment of the present application further includes S926 and S927.
  • MM 2 sends a first notification message to SM1 to instruct SM1 to release the context of the first session.
  • S900-S917 may refer to the description of S800-S817 in FIG. 8
  • S921-S924 may refer to the description of S821-S824 in FIG. 8
  • S926-S927 may refer to the description of S825-S826 in FIG. 8, and details are not described herein again.
  • the application scenario to which the embodiment is applied is the same as the application scenario in the embodiment shown in FIG. 8 , except that the content indicated by the indication information in the embodiment is indicated by the indication information in the embodiment shown in FIG. 8 . The content is different.
  • the SM 1 in the embodiment shown in any of the figures retains the context of the first session before the second session is established. Therefore, even if the downlink data to be sent to the terminal device is accurately transmitted to the terminal device, the downlink data is guaranteed to have no packet loss.
  • the second session since the second session is established after waiting for the data of the terminal device to be sent, the second session is not transmitted but the second session is established, which can reduce the waste of the core network resources and reduce the Necessary signaling transmission.
  • the terminal device does not perceive the process of session migration, and further reduces the signaling transmission of the terminal device.
  • the mobility management function entity and the session management function entity can be set independently or integrated on the same device.
  • the embodiments shown in FIG. 4 to FIG. 9 are described by taking the mobility management function entity and the session management function entity as an example.
  • the mobile management function entity and the session management function entity are integrated into the same device as an example.
  • the session migration method provided by the embodiment of the present application.
  • the embodiment of the present application indicates that the source radio access network device is represented by the base station 1, and the source control plane network element is represented by the control plane network element 1, and the source user plane network element is represented by the user plane network element 1, and the target is
  • the radio access network equipment is represented by the base station 2
  • the target control plane network element is represented by the control plane network element 2
  • the target user plane network element is represented by the user plane network element 2.
  • FIG. 10 shows a session migration method corresponding to the embodiment shown in FIG.
  • the session migration method includes:
  • a first session is established between the S1000, the terminal device, and the control plane network element 1.
  • the service area of the control plane network element 1 includes a first TA, and the control plane network element 1 stores the context of the first session.
  • the first request message carries the identifier of the first TA, the DNN, the identifier of the control plane network element 1, and the terminal.
  • S1002 The base station 2 forwards the first request message in S1001 to the control plane network element 2.
  • the control plane network element 2 sends a second request message to the control plane network element 1 to request to acquire the context of the terminal device.
  • the second request message carries the identifier of the control plane network element 2 and the temporary ID 1.
  • the context of the terminal device includes the mobility management context of the terminal device and the session management context of the terminal device.
  • the control plane network element 1 determines, according to the identifier of the control plane network element 2, whether to update the session of the terminal device.
  • control plane network element 1 determines to update the session of the terminal device, the control plane network element 1 retains the context of the first session, and sends the indication information, the identifier of the control plane network element 1, and the terminal device to the control plane network element 2.
  • a third response message of the context including the mobility management context and the session management context) and the permanent identity of the terminal device.
  • the control plane network element 2 stores the identifier of the control plane network element 1 and the mobility management context of the terminal device, and allocates the temporary ID 2 to the terminal device.
  • the control plane network element 2 sends a second response message carrying the indication information, the temporary ID 2, and the identifier of the control plane network element 2 to the base station 2.
  • S1008 The base station 2 forwards the second response message in S1007 to the terminal device.
  • the terminal device sends a session establishment request carrying the DNN and the session type information to the base station 2 after waiting for the data of the terminal device to be sent, according to the indication information carried in the second response message in S1008.
  • the base station 2 forwards the session establishment request in S1009 to the control plane network element 2.
  • the control plane network element 2 performs authentication and authorization on the terminal device according to the mobility management context of the terminal device, and according to the DNN and session type information carried in the session establishment request in S1010, and the subscription of the terminal device locally stored by the control plane network element 2 The data selects the user plane network element 2 for the terminal device.
  • the control plane network element 2 sends a user plane forwarding rule to the user plane network element 2, and creates a context of the second session.
  • the control plane network element 2 sends a session establishment response to the base station 2, and the base station 2 sends a session establishment response to the terminal device.
  • the establishment process of the second session ends.
  • the session migration method provided by the embodiment of the present application further includes S1014 and S1015.
  • the control plane network element 2 sends a first notification message to the control plane network element 1 to instruct the control plane network element 1 to release the context of the first session.
  • the control plane network element 1 releases the context of the first session.
  • FIG. 11 shows a session migration method corresponding to the embodiment shown in FIG. 5.
  • the session migration method includes:
  • a first session is established between the S1100, the terminal device, and the control plane network element 1.
  • the service area of the control plane network element 1 includes a first TA, and the control plane network element 1 stores the context of the first session.
  • the first request message carries the identifier of the first TA, the DNN, the identifier of the control plane network element 1, and the temporary ID 1 of the terminal device.
  • S1102 The base station 2 forwards the first request message in S1101 to the control plane network element 2.
  • control plane network element 2 sends a second request message to the control plane network element 1 to request to acquire the context of the terminal device.
  • the second request message carries the identifier of the control plane network element 2 and the temporary ID 1.
  • the context of the terminal device includes a mobility management context and a session management context.
  • the control plane network element 1 determines whether to update the session of the terminal device according to the identifier of the control plane network element 2.
  • control plane network element 1 determines that the session of the terminal device is not required to be updated temporarily, the control plane network element 1 retains the context of the first session, and sends the identifier of the control plane network element 1 and the context of the terminal device to the control plane network element 2.
  • a third response message (including the mobility management context and the session management context) and the permanent identity of the terminal device.
  • the control plane network element 2 stores the identifier of the control plane network element 1 and the context of the terminal device, and allocates the temporary ID 2 to the terminal device.
  • the control plane network element 2 sends a second response message carrying the identifier of the temporary ID 2 and the control plane network element 2 to the base station 2.
  • the base station 2 forwards the second response message in S1107 to the terminal device.
  • control plane network element 1 determines again whether to update the session of the terminal device.
  • the control plane network element 1 determines whether to update the session of the terminal device.
  • the control plane network element 1 has determined that the terminal device has moved in the above S1104. Therefore, the control plane network element 1 in S1109 determines the amount of uplink data received by the control plane network element 1 within a preset time period after S1105. Whether it is greater than or equal to the preset threshold.
  • the control plane network element 1 determines to update the session of the terminal device. If the amount of data of the uplink data received by the control plane network element 1 in the preset time period after S1105 is less than the preset threshold, the control plane network element 1 still determines that the session of the terminal device is not needed to be updated temporarily.
  • the terminal device may send uplink data.
  • the control plane network element 1 receives the uplink data, and sends the uplink data received by the user plane network element 1. Then, the control plane network element 1 receives the uplink data response message sent by the user plane network element 1.
  • control plane network element 1 determines to update the session of the terminal device, the control plane network element 1 retains the context of the first session, adds the indication information to the received uplink data response message, and sends the carried information to the control plane network element 2 An uplink data response message with indication information.
  • the control plane network element 2 forwards the uplink data response message carrying the indication information to the base station 2.
  • S1112 The base station 2 forwards an uplink data response message carrying the indication information to the terminal device.
  • S1113 The terminal device sends a session establishment request carrying the DNN and the session type information to the base station 2 after waiting for the data of the terminal device to be sent, according to the indication information carried in the uplink data response message in S1112.
  • the base station 2 forwards the session establishment request in S1113 to the control plane network element 2.
  • the control plane network element 2 authenticates and authorizes the terminal device according to the mobility management context of the terminal device, and according to the DNN and the session type information carried in the session establishment request in S1113, and the subscription of the terminal device locally stored by the control plane network element 2 The data selects the user plane network element 2 for the terminal device.
  • the control plane network element 2 sends a user plane forwarding rule to the user plane network element 2, and creates a context of the second session.
  • the control plane network element 2 sends a session establishment response to the base station 2, and the base station 2 sends a session establishment response to the terminal device.
  • the establishment process of the second session ends.
  • the session migration method provided by the embodiment of the present application further includes S1118 and S1119.
  • the control plane network element 2 sends a first notification message to the control plane network element 1 to instruct the control plane network element 1 to release the context of the first session.
  • FIG. 12 shows a session migration method corresponding to the embodiment shown in FIG. 6.
  • the session migration method includes:
  • a first session is established between the S1200 and the terminal device and the control plane network element 1.
  • the service area of the control plane network element 1 includes a first TA, and the control plane network element 1 stores the context of the first session.
  • the first request message carries the identifier of the first TA, the DNN, the identifier of the control plane network element 1, and the temporary ID 1 of the terminal device.
  • S1202 The base station 2 forwards the first request message in S1201 to the control plane network element 2.
  • the control plane network element 2 sends a second request message to the control plane network element 1 to request to acquire the context of the terminal device.
  • the second request message carries the identifier of the control plane network element 2 and the temporary ID 1.
  • the context of the terminal device includes a mobility management context and a session management context.
  • the control plane network element 1 determines, according to the identifier of the control plane network element 2, whether to update the session of the terminal device.
  • control plane network element 1 determines to update the session of the terminal device, the control plane network element 1 retains the context of the first session, and sends the indication information, the identifier of the control plane network element 1, and the terminal device to the control plane network element 2.
  • Context including mobility management context and session management context
  • terminal devices A third response message that is permanently identified.
  • the control plane network element 2 stores the identifier of the control plane network element 1 and the context of the terminal device, and allocates the temporary ID 2 to the terminal device.
  • the control plane network element 2 sends a second response message carrying the identifier of the temporary ID 2 and the control plane network element 2 to the base station 2.
  • the base station 2 forwards the second response message in S1207 to the terminal device.
  • the terminal device sends, to the base station 2, an uplink data packet carrying the identifier of the temporary ID 2 and the control plane network element 2.
  • the base station 2 forwards the uplink data packet in the S1209 to the control plane network element 2.
  • the control plane network element 2 performs authentication and authorization on the terminal device according to the mobility management context of the terminal device according to the indication information, and selects a user plane network for the terminal device according to the subscription data of the terminal device and the data type of the uplink data packet. Yuan 2.
  • the control plane network element 2 sends a user plane forwarding rule to the user plane network element 2, and creates a context of the second session.
  • S1213 The user plane network element 2 sends a session establishment response to the control plane network element 2.
  • control plane network element 2 After the control plane network element 2 receives the session establishment response, the establishment process of the second session ends.
  • S1214 The control plane network element 2 forwards the uplink data packet received by the user plane network element 2 in S1210.
  • the session migration method provided by the embodiment of the present application further includes S1215 and S1216.
  • the control plane network element 2 sends a first notification message to the control plane network element 1 to instruct the control plane network element 1 to release the context of the first session.
  • the control plane network element 1 releases the context of the first session.
  • the control plane network element 2 in the embodiment of the present application may perform S1214 first, and then execute S1215.
  • S1215 may be executed first, then S1214 may be executed, and S1214 and S1215 may be performed at the same time, which is not specifically limited in this embodiment of the present application.
  • FIG. 13 shows a session migration method corresponding to the embodiment shown in FIG.
  • the session migration method includes:
  • a first session is established between the S1300 and the terminal device and the control plane network element 1.
  • the service area of the control plane network element 1 includes a first TA, and the control plane network element 1 stores the context of the first session.
  • the first request message carries the identifier of the first TA, the DNN, the identifier of the control plane network element 1, and the temporary ID 1 of the terminal device.
  • S1302 The base station 2 forwards the first request message in S1301 to the control plane network element 2.
  • the control plane network element 2 sends a second request message to the control plane network element 1 to request the end of the acquisition.
  • the second request carries the identifier of the control plane network element 2 and the temporary ID 1, and the context of the terminal device includes a mobility management context and a session management context.
  • the control plane network element 1 determines whether to update the session of the terminal device according to the identifier of the control plane network element 2.
  • control plane network element 1 determines that the session of the terminal device is not required to be updated temporarily, the control plane network element 1 retains the context of the first session, and sends the identifier of the control plane network element 1 and the context of the terminal device to the control plane network element 2.
  • a third response message (including the mobility management context and the session management context) and the permanent identity of the terminal device.
  • the control plane network element 2 stores the identifier of the control plane network element 1 and the context of the terminal device, and allocates the temporary ID 2 to the terminal device.
  • the control plane network element 2 sends a second response message carrying the identifier of the temporary ID 2 and the control plane network element 2 to the base station 2.
  • the base station 2 forwards the second response message in S1307 to the terminal device.
  • control plane network element 1 determines again whether to update the session of the terminal device.
  • the control plane network element 1 determines whether to update the session of the terminal device.
  • the terminal device may send uplink data.
  • the control plane network element 1 receives the uplink data, and sends the uplink data received by the user plane network element 1. Then, the control plane network element 1 receives the uplink data response message sent by the user plane network element 1.
  • control plane network element 1 determines to update the session of the terminal device, the control plane network element 1 retains the context of the first session, adds the indication information to the received uplink data response message, and sends the carried information to the control plane network element 2 An uplink data response message with indication information.
  • control plane network element 2 sends an uplink data response message to the base station 2.
  • S1312 The base station 2 forwards the uplink data response message in S1311 to the terminal device.
  • the terminal device sends, to the base station 2, an uplink data packet carrying the identifier of the temporary ID 2 and the control plane network element 2.
  • S1314 The base station 2 forwards the uplink data packet in S1313 to the control plane network element 2.
  • the control plane network element 2 performs verification and authorization on the terminal device by using the mobility management context of the terminal device according to the indication information carried in the uplink data response message received by the terminal device, and according to the subscription data of the terminal device and the uplink data packet.
  • the information such as the data type selects the user plane network element 2 for the terminal device.
  • the control plane network element 2 sends a user plane forwarding rule to the user plane network element 2, and creates a context of the second session.
  • the user plane network element 2 sends a session establishment response to the control plane network element 2.
  • control plane network element 2 sends the uplink data packet received by the control plane network element 2 in S1314.
  • control plane network element 2 After the control plane network element 2 receives the session establishment response, the establishment process of the second session ends.
  • the session migration method provided by the embodiment of the present application further includes S1319. And S1320.
  • the control plane network element 2 sends a first notification message to the control plane network element 1 to instruct the control plane network element 1 to release the context of the first session.
  • the control plane network element 2 in the embodiment of the present application may perform S1318 first, then S1319, or S1319 may be performed first, and then S1318 may be performed. S1318 and S1319 may be performed at the same time, which is not specifically limited in this embodiment of the present application.
  • FIG. 14 shows a session migration method corresponding to the embodiment shown in FIG.
  • the session migration method includes:
  • a first session is established between the S1400 and the terminal device and the control plane network element 1.
  • the service area of the control plane network element 1 includes a first TA, and the control plane network element 1 stores the context of the first session.
  • the first request message carries the identifier of the first TA, the DNN, the identifier of the control plane network element 1, and the temporary ID 1 of the terminal device.
  • S1402 The base station 2 forwards the first request message in S1401 to the control plane network element 2.
  • the control plane network element 2 sends a second request message to the control plane network element 1 to request to acquire the context of the terminal device.
  • the second request message carries the identifier of the control plane network element 2 and the temporary ID 1.
  • the context of the terminal device includes a mobility management context and a session management context.
  • the control plane network element 1 determines, according to the identifier of the control plane network element 2, whether to update the session of the terminal device.
  • control plane network element 1 determines that the session of the terminal device is not required to be updated temporarily, the control plane network element 1 retains the context of the first session, and sends the identifier of the control plane network element 1 and the context of the terminal device to the control plane network element 2.
  • a third response message (including the mobility management context and the session management context) and the permanent identity of the terminal device.
  • the control plane network element 2 stores the identifier of the control plane network element 1 and the context of the terminal device, and allocates the temporary ID 2 to the terminal device.
  • the control plane network element 2 sends a second response message carrying the identifier of the temporary ID 2 and the control plane network element 2 to the base station 2.
  • S1408 The base station 2 forwards the second response message in S1407 to the terminal device.
  • control plane network element 1 determines again whether to update the session of the terminal device.
  • the control plane network element 1 determines whether to update the session of the terminal device.
  • control plane network element 1 may receive downlink data to be sent to the terminal device, where the downlink data is data sent by the user plane network element 1 to the control plane network element 1.
  • control plane network element 1 determines to update the session of the terminal device, the control plane network element 1 retains the context of the first session, adds the indication information to the received downlink data, and sends the indication to the control plane network element 2 Downstream data for information.
  • the control plane network element 2 After receiving the downlink data carrying the indication information, the control plane network element 2 transmits the downlink data carrying the indication information to the terminal device.
  • the terminal device since the terminal device does not send uplink data after moving to the second TA, the terminal device may be in an idle state or may be in a connected state. For example, if the terminal device is in an idle state, after S1410, S1411-S1412 are executed, and after S1412, S1413 is executed; if the terminal device is in the connected state, then after S1410, S1413 is executed. Since S1411-S1412 are optional, they are indicated by dashed lines in FIG.
  • the control plane network element 2 sends a paging message to the terminal device.
  • S1412 The terminal device sends a paging response to the control plane network element 2.
  • the control plane network element 2 transmits downlink data carrying the indication information to the base station 2, and the base station 2 forwards the downlink data carrying the indication information to the terminal equipment.
  • the terminal device sends a downlink data response message to the base station 2, and the base station 2 forwards the downlink data response message to the control plane network element 2, and the control plane network element 2 forwards the downlink data response message to the control plane network element 1, and the control plane network element 1 Forwarding the downlink data response message to the user plane network element 1.
  • S1414 is an optional step, and is indicated by a broken line in FIG.
  • the terminal device sends a session establishment request carrying the DNN and the session type information to the base station 2 according to the indication information carried by the downlink data that is received in the S1413.
  • the base station 2 forwards the session establishment request in S1415 to the control plane network element 2.
  • the control plane network element 2 performs authentication and authorization on the terminal device according to the mobility management context of the terminal device, and obtains session management subscription data of the terminal device according to the permanent identifier of the terminal device, and the DNN is carried according to the session establishment request in S1416. And the session type information and the subscription data of the terminal device locally stored by the control plane network element 2, and the user plane network element 2 is selected for the terminal device.
  • the control plane network element 2 sends a user plane forwarding rule to the user plane network element 2, and creates a context of the second session.
  • the control plane network element 2 sends a session establishment response to the base station 2, and the base station 2 sends a session establishment response to the terminal device.
  • the establishment process of the second session ends.
  • the session migration method provided by the embodiment of the present application further includes S1420 and S1421.
  • the control plane network element 2 sends a first notification message to the control plane network element 1 to instruct the control plane network element 1 to release the context of the first session.
  • control plane network element 1 releases the context of the first session.
  • the terminal device further sends a second uplink registration message to the control plane network element 2, and the control plane network
  • the element 2 forwards the message to the user plane network element 2
  • the user plane network element 2 forwards the second uplink registration message to the application server, so that the application server updates the stored information to be sent to the terminal device.
  • the forwarding path of the downstream data This process is not shown in FIG.
  • FIG. 15 shows a session migration method corresponding to the embodiment shown in FIG.
  • the session migration method includes:
  • a first session is established between the S1500 and the terminal device and the control plane network element 1.
  • the service area of the control plane network element 1 includes a first TA, and the control plane network element 1 stores the context of the first session.
  • the first request message carries the identifier of the first TA, the DNN, the identifier of the control plane network element 1, and the temporary ID 1 of the terminal device.
  • S1502 The base station 2 forwards the first request message in S1501 to the control plane network element 2.
  • the control plane network element 2 sends a second request message to the control plane network element 1 to request to acquire the context of the terminal device.
  • the second request message carries the identifier of the control plane network element 2 and the temporary ID 1.
  • the context of the terminal device includes a mobility management context and a session management context.
  • the control plane network element 1 determines, according to the identifier of the control plane network element 2, whether to update the session of the terminal device.
  • control plane network element 1 determines that the session of the terminal device is not required to be updated temporarily, the control plane network element 1 retains the context of the first session, and sends the identifier of the control plane network element 1 and the context of the terminal device to the control plane network element 2.
  • a third response message (including the mobility management context and the session management context) and the permanent identity of the terminal device.
  • the control plane network element 2 stores the identifier of the control plane network element 1 and the context of the terminal device, and allocates the temporary ID 2 to the terminal device.
  • the control plane network element 2 sends a second response message carrying the identifier of the temporary ID 2 and the control plane network element 2 to the base station 2.
  • the base station 2 forwards the second response message in S1507 to the terminal device.
  • control plane network element 1 determines again whether to update the session of the terminal device.
  • the control plane network element 1 determines whether to update the session of the terminal device.
  • control plane network element 1 may continue to receive downlink data to be sent to the terminal device, where the downlink data is data sent by the user plane network element 1 to the control plane network element 1.
  • control plane network element 1 determines to update the session of the terminal device, the control plane network element 1 retains the context of the first session, adds the indication information to the received downlink data, and sends the indication to the control plane network element 2 Downstream data for information.
  • the control plane network element 2 After receiving the downlink data carrying the indication information, the control plane network element 2 transmits the downlink data carrying the indication information to the terminal device.
  • the terminal device since the terminal device does not send uplink data after moving to the second TA, the terminal device may be in an idle state or may be in a connected state. For example, if the terminal device is in an idle state, after S1510, S1511-S1512 is executed, and After S1512, S1513 is executed; if the terminal device is in the connected state, then after S1510, S1513 is executed. Since S1511-S1512 is optional, it is indicated by a broken line in Fig. 14.
  • the control plane network element 2 sends a paging message to the terminal device.
  • S1512 The terminal device sends a paging response to the control plane network element 2.
  • the control plane network element 2 transmits downlink data carrying the indication information to the base station 2, and the base station 2 forwards the downlink data carrying the indication information to the terminal equipment.
  • S1514 The terminal device sends a downlink data response message to the base station 2, and the base station 2 forwards the downlink data response message to the control plane network element 2, and the control plane network element 2 forwards the downlink data response message to the control plane network element 1, and the control plane network element 1 Forwarding the downlink data response message to the user plane network element 1.
  • S1514 is an optional step, and is indicated by a broken line in FIG.
  • S1515 The terminal device sends, to the base station 2, the first uplink registration message carrying the identifier of the temporary ID 2 and the control plane network element 2 according to the indication information carried by the downlink data received by the terminal device in S1513.
  • S1516 The base station 2 sends the first uplink registration message in S1515 to the control plane network element 2.
  • control plane network element 2 after receiving the first uplink registration message, performs verification and authorization on the terminal device according to the mobility management context of the terminal device, and according to the subscription data of the terminal device and the data type of the first uplink registration message, etc.
  • the information selects the user plane network element 2 for the terminal device.
  • the control plane network element 2 sends a user plane forwarding rule to the user plane network element 2, and creates a context of the second session.
  • control plane network element 2 After the control plane network element 2 receives the session establishment response, the establishment process of the second session ends.
  • S1520 The control plane network element 2 sends, to the user plane network element 2, the first uplink registration message received by the control plane network element 2 in S1517.
  • the session migration method provided by the embodiment of the present application further includes S1521 and S1522.
  • control plane network element 2 sends a first notification message to the control plane network element 1 to instruct the control plane network element 1 to release the context of the first session.
  • control plane network element 1 in the embodiment shown in any of the figures retains the context of the first session before the second session is established. Therefore, even if the downlink data to be sent to the terminal device is accurately transmitted to the terminal device, the downlink data is guaranteed to have no packet loss.
  • the second session since the second session is established after waiting for the data of the terminal device to be sent, the second session is not transmitted but the second session is established, which can reduce the waste of the core network resources and reduce the Necessary signaling transmission.
  • the terminal device does not perceive the process of session migration, and further reduces the signaling transmission of the terminal device.
  • the embodiment of the present application provides a session management function entity, which is used to perform the steps performed by the source session management function entity in the above session migration method.
  • the session management function entity provided by the embodiment of the present application may include a module corresponding to the corresponding step.
  • the embodiment of the present application may divide the function module of the session management function entity according to the foregoing method example.
  • each function module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the division of modules in the embodiments of the present application is schematic, and is only a logical function division, and may be further divided in actual implementation.
  • FIG. 16 shows a possible structural diagram of the session management function entity involved in the above embodiment in the case where the respective function modules are divided by corresponding functions.
  • the session management function entity 1600 includes a processing unit 160, a transmitting unit 161, and a receiving unit 162.
  • the processing unit 160 is configured to support the session management function entity 1600 to perform S301, S302, S405, S406, S419, S505, S506, S511, S523, S605, S606, S620, S705, S706, S711, S724, S705, S706, S711, S724 in the foregoing embodiment.
  • the transmitting unit 161 is configured to support the session management function entity 1600 to perform S302a in the above embodiment.
  • S302b S406, S506, S606, S706, S712, S806, S812, S906, S912, etc., and/or other processes for the techniques described herein;
  • receiving unit 162 for supporting the session management function entity 1600 to perform the above S304, S404, S418, S504, S522, S604, S619, S704, S723, S804, S825, S904, S926, etc. in the embodiments, and/or other processes for the techniques described herein.
  • the session management function entity 1600 provided by the embodiment of the present application includes, but is not limited to, the foregoing modules.
  • the session management function entity 1600 may further include a storage unit 163.
  • the storage unit 163 can be used to store the context of the first session, and can also be used to store program codes and data of the session management function entity.
  • the processing unit 160 in the embodiment of the present application may be a processor or a controller, such as a central processing unit (CPU), a digital signal processor (Digital Signal Processor, DSP). ). It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • Processing unit 160 may also be a combination of computing functions, such as one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the transmitting unit 161 and the receiving unit 162 may be implemented by being integrated in one communication unit, which may be a communication interface.
  • the storage unit 163 may be a memory.
  • the session management function entity 1600 involved in the embodiment of the present application may be the session management function entity 1700 shown in FIG. 17 when the processing unit is a processor, the storage unit is a memory, and the communication unit is a communication interface.
  • the session management function entity 1700 includes a processor 171, a memory 172, and a communication interface 173.
  • the processor 171, the memory 172, and the communication interface 173 are connected to one another via a bus 174.
  • the bus 174 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus.
  • ISA Industry Standard Architecture
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus 174 described above can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 17, but it does not mean that there is only one bus or one type of bus.
  • the session management function entity 1700 can include one or more processors 171, ie, the session management function entity 1700 can include a multi-core processor.
  • the session management function entity 1700 When the session management function entity 1700 is running, the session management function entity 1700 performs the session migration method of the embodiment shown in any of Figures 3-9.
  • the session migration method For a specific session migration method, refer to the related description in the foregoing embodiment shown in any of the figures in FIG. 3 to FIG. 9 , and details are not described herein again.
  • Another embodiment of the present application also provides a computer readable storage medium comprising one or more program codes, the one or more programs including instructions, when the processor 171 in the session management function entity 1700 When the program code is executed, the session management function entity 1700 performs the session migration method as shown in any of Figures 3-9.
  • a computer program product comprising computer executable instructions stored in a computer readable storage medium; at least one processor of the session management function entity Reading the computer execution instructions from the computer readable storage medium, the at least one processor executing the computer execution instructions such that the session management function entity implements the SM 2 in the session migration method illustrated in any of FIGS. 3-9 step.
  • An embodiment of the present application provides a terminal device, where the terminal device is configured to perform the steps performed by the terminal device in the foregoing session migration method.
  • the terminal device provided by the embodiment of the present application may include a module corresponding to the corresponding step.
  • the embodiment of the present application may perform the division of the function module on the terminal device according to the foregoing method example.
  • each function module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the division of modules in the embodiments of the present application is schematic, and is only a logical function division, and may be further divided in actual implementation.
  • FIG. 18 shows a possible structural diagram of the terminal device involved in the foregoing embodiment, in the case where the respective functional modules are divided by corresponding functions.
  • the terminal device 1800 includes a processing unit 180, an acquisition unit 181, and a transmission unit 182.
  • the processing unit 180 is configured to support the terminal device 1800 to perform S300, S400, S500, S600, S700, S800, S900, etc. in the above embodiments, and/or other processes for the techniques described herein;
  • the obtaining unit 181 is configured to Supporting the terminal device 1600 to perform S410, S510, S610, S710, S714, S810, S813, S816, S824, S910, S913, S916, etc.
  • the sending unit 182 is configured to support the terminal device 1600 to perform S401, S411, S501, S515, S601, S611, S701, S715, S801, S814, S818, S901, S914, S818, etc. in the above embodiments, and/or Other processes of the techniques described herein. All the related content of the steps involved in the foregoing method embodiments may be referred to the functional descriptions of the corresponding functional modules, and details are not described herein again.
  • the terminal device 1800 provided by the embodiment of the present application includes, but is not limited to, the foregoing module.
  • the terminal device 1800 may further include a storage unit 183.
  • the storage unit 183 can be used to store program codes and data of the terminal device.
  • the processing unit 180 in the embodiment of the present application may be a processor or a controller, such as a CPU or a DSP. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processing unit 180 can also be an implementation meter A combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the obtaining unit 181 and the transmitting unit 182 can be implemented by being integrated in one communication unit, which can be a communication interface.
  • the storage unit 183 may be a memory.
  • the terminal device 1800 When the processing unit is a processor, the storage unit is a memory, and the communication unit is a communication interface, the terminal device 1800 according to the embodiment of the present application may be the terminal device 1900 shown in FIG. As shown in FIG. 19, the terminal device 1900 includes a processor 191, a memory 192, and a communication interface 193. The processor 191, the memory 192, and the communication interface 193 are connected to one another via a bus 194.
  • the bus 194 can be a PCI bus or an EISA bus.
  • the bus 194 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 19, but it does not mean that there is only one bus or one type of bus.
  • the terminal device 1900 can include one or more processors 191, ie, the terminal device 1900 can include a multi-core processor.
  • the terminal device 1900 When the terminal device 1900 is running, the terminal device 1900 performs the session migration method of the embodiment shown in any of Figures 3-9.
  • the terminal device 1900 For a specific session migration method, refer to the related description in the foregoing embodiment shown in any of the figures in FIG. 3 to FIG. 9 , and details are not described herein again.
  • Another embodiment of the present application also provides a computer readable storage medium comprising one or more program codes, the one or more programs including instructions, when the processor 191 in the terminal device 1900 is executing In the program code, the terminal device 1900 performs the session migration method as shown in any of Figs.
  • a computer program product comprising computer executed instructions stored in a computer readable storage medium; at least one processor of the terminal device can be from the computer The readable storage medium reads the computer execution instructions, and the at least one processor executes the computer to execute the instructions such that the terminal device performs the step of performing the SM 2 in the session migration method illustrated in any of FIGS. 3-9.
  • the embodiment of the present application provides a mobility management function entity, which is used to perform the steps performed by the target mobility management function entity in the above session migration method.
  • the mobility management function entity provided by the embodiment of the present application may include a module corresponding to the corresponding step.
  • the embodiment of the present application may divide the function module of the mobility management function entity according to the foregoing method example.
  • each function module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the division of modules in the embodiments of the present application is schematic, and is only a logical function division, and may be further divided in actual implementation.
  • FIG. 20 shows a possible structural diagram of the mobility management function entity involved in the foregoing embodiment, in the case where each function module is divided by corresponding functions.
  • the mobility management function entity 2000 includes an acquisition unit 200, a processing unit 201, and a transmission unit 202.
  • the obtaining unit 200 is configured to support the mobility management function entity 2000 to perform S402, S407, S412, S417, S502, S507, S516, S521, S602, S612, S617, etc. in the above embodiments, and/or for use in the description herein.
  • the processing unit 201 is configured to support the mobility management function entity 2000 to execute S408, S413, S508, S517, S608, S613, etc.
  • the sending unit 202 is configured to support the mobility management function entity 2000 to perform S403, S409, S414, S503, S509, S513, S603, S609, S614, etc. in the foregoing embodiments, and/or Other processes of the techniques described herein. All the related content of the steps involved in the foregoing method embodiments may be referred to the functional descriptions of the corresponding functional modules, and details are not described herein again.
  • the mobility management function entity 2000 provided by the embodiment of the present application includes but is not limited to the foregoing modules.
  • the mobility management function entity 2000 may further include a storage unit 203.
  • the storage unit 203 can be used to store the mobility management context of the terminal device, and can also be used to store the program code and data of the mobility management function entity.
  • the processing unit 201 in the embodiment of the present application may be a processor or a controller, such as a CPU or a DSP. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • Processing unit 201 may also be a combination of computing functions, such as one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the obtaining unit 201 and the transmitting unit 202 can be implemented by being integrated in one communication unit, which can be a communication interface.
  • the storage unit 203 can be a memory.
  • the mobility management function entity 2000 involved in the embodiment of the present application may be the mobility management function entity 2100 shown in FIG. 21.
  • the mobility management function entity 2100 includes a processor 211, a memory 212, and a communication interface 213.
  • the processor 211, the memory 212, and the communication interface 213 are connected to each other through a bus 214.
  • the bus 214 can be a PCI bus or an EISA bus.
  • the bus 214 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in FIG. 21, but it does not mean that there is only one bus or one type of bus.
  • the mobility management functional entity 2100 can include one or more processors 211, ie, the mobility management functional entity 2100 can include a multi-core processor.
  • the mobility management function entity 2100 When the mobility management function entity 2100 is running, the mobility management function entity 2100 performs the session migration method of the embodiment shown in any of Figures 3-9.
  • the session migration method For a specific session migration method, refer to the related description in the foregoing embodiment shown in any of the figures in FIG. 3 to FIG. 9 , and details are not described herein again.
  • Another embodiment of the present application also provides a computer readable storage medium including one or more program codes, the one or more programs including instructions, when the processor 211 in the mobility management function entity 2100 When the program code is executed, the mobility management function entity 2100 performs the session migration method as shown in any of Figures 3-9.
  • a computer program product comprising computer executable instructions stored in a computer readable storage medium; at least one processor of the mobility management function entity Reading the computer execution instructions from the computer readable storage medium, the at least one processor executing the computer execution instructions such that the mobility management function entity implements MM 2 in the session migration method illustrated in any of Figures 1-3 step.
  • the disclosed system, apparatus, and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the modules or units is only a logical function division.
  • there may be another division manner for example, multiple units or components may be used. Combinations can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • a computer readable storage medium A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a flash memory, a mobile hard disk, a read only memory, a random access memory, a magnetic disk, or an optical disk, and the like, which can store program codes.

Abstract

本申请实施例提供一种会话迁移方法及设备,涉及通信技术领域,既能保证在终端设备的TA发生变化后,下行数据无丢包,又能降低核心网资源的浪费和信令的传输。该方法包括:源会话管理功能实体判断是否更新终端设备的会话;若源会话管理功能实体确定更新终端设备的会话,源会话管理功能实体保留第一会话的上下文,并向第一设备发送指示信息,指示信息用于指示第一设备在等待至获得待发送的终端设备的数据之后触发第二会话的建立;其中,第一会话为源会话管理功能实体与终端设备之间已建立的会话,第一设备为终端设备或目标移动管理功能实体,第二会话为目标会话管理功能实体与终端设备之间的会话。

Description

一种会话迁移方法及设备 技术领域
本申请实施例涉及通信技术领域,尤其涉及一种会话迁移方法及设备。
背景技术
随着通信技术的快速发展,出现了下一代无线通信系统(例如,窄带物联网(Narrowband-Internet of Thing,NB-IOT)系统)。在下一代无线通信系统中,终端设备与核心网设备之间传输的数据可以为小数据(small data),传输小数据的业务通常称为小包业务。小包业务对时延的要求和服务质量(Quality of Service,QoS)的要求均比较低,因此,终端设备与核心网设备之间的会话无需一直保持连续。
现有技术中,若位于第一跟踪区(Tracking Area,TA)内的终端设备与源核心网设备,源核心设备的服务区域包括第一TA,之间已经建立会话,在该终端设备从第一TA移动到第二TA的场景中,源核心网设备释放与该终端设备之间的会话,并指示该终端设备向目标核心网设备,该目标核心网设备的服务区域包括第二TA,发起会话建立请求,以建立该终端设备与目标核心网设备之间的会话,从而使得该终端设备可通过目标核心网设备传输该终端设备的数据。
但是,由于终端设备与目标核心网设备之间建立会话之前,源核心网设备与该终端设备之间的会话已经被释放,因此,对于待发送至该终端设备的下行数据,可能会出现丢包现象。此外,在终端设备移动到第二TA后,建立了该终端设备与目标核心网设备之间的会话,如果该终端设备在第二TA内未传输数据,则会导致核心网资源的浪费和不必要的信令传输。
发明内容
本申请提供一种会话迁移方法及设备,既能够保证在终端设备的TA发生变化后,下行数据无丢包,又能够降低核心网资源的浪费和信令的传输。
为达到上述目的,本申请采用如下技术方案:
第一方面,提供一种会话迁移方法,首先,源会话管理功能实体判断是否更新终端设备的会话;然后,若确定更新终端设备的会话,源会话管理功能实体保留该源会话管理功能实体与终端设备之间已建立的第一会话的上下文,并向第一设备发送指示信息,指示信息用于指示第一设备在等待至获得待发送的终端设备的数据之后触发第二会话的建立,第一设备为终端设备或目标移动管理功能实体,第二会话为目标会话管理功能实体与终端设备之间的会话。
由于源会话管理功能实体在第二会话建立之前,保留了第一会话的上下文,因此,即使有待发送至终端设备的下行数据,也能够准确的发送到终端设备,保证了下行数据无丢包。又由于第二会话是终端设备或目标移动管理功能实体在等待至获得待发送的终端设备的数据之后触发建立的,因此,不会出现未传 输数据却建立了第二会话的情况,降低了核心网资源的浪费,也减少了不必要的信令传输。
可选的,在本申请的一种可能的实现方式中,在源会话管理功能实体向第一设备发送指示信息之后,源会话管理功能实体还从目标移动管理功能实体接收第一通知消息。这样,源会话管理功能实体在收到第一通知消息后,释放第一会话的上下文。
源会话管理功能实体向第一设备发送指示信息之后,第一设备在等待至获得待发送的终端设备的数据之后触发了第二会话的建立。第二会话建立后,源会话管理功能实体还从目标移动管理功能实体接收第一通知消息,并根据第一通知消息释放第一会话的上下文,减少源会话管理功能实体的资源浪费。
可选的,在本申请的另一种可能的实现方式中,在第一设备为终端设备的应用场景中,源会话管理功能实体可以向源移动管理功能实体发送携带指示信息的第一响应消息,该指示信息被发送至终端设备,该指示信息用于指示终端设备在等待至获得待发送的终端设备的数据后,向目标移动管理功能实体发送用于触发第二会话的建立的信息。
可选的,在本申请的另一种可能的实现方式中,在第一设备为目标移动管理实体的应用场景中,源会话管理功能实体可以向源移动管理功能实体发送携带指示信息的第一响应消息,该指示信息被发送至目标移动管理实体,该指示信息用于指示目标移动管理功能实体等待至获得待发送的终端设备的上行数据后,选择目标会话管理功能实体,以触发第二会话的建立。
可选的,在本申请的另一种可能的实现方式中,源会话管理功能实体向第一设备发送指示信息的方法还可以为源会话管理功能实体从终端设备接收到上行数据,获取上行数据应答消息,并在上行数据应答消息中添加指示信息,向第一设备发送携带有指示信息的上行数据应答消息。
可以看出,在不同的应用场景中,源会话管理功能实体发送指示信息的方法不同。
可选的,在本申请的另一种可能的实现方式中,源会话管理功能实体还从源移动管理功能实体接收携带目标移动管理功能实体的标识的第二通知消息。在这种情况下,源会话管理功能实体判断是否更新终端设备的会话的方法为:源会话管理功能实体根据第一条件判断是否更新终端设备的会话,这里,第一条件包括源移动管理功能实体的标识与目标移动管理的标识不同。
可选的,在本申请的另一种可能的实现方式中,上述第一条件还包括:源会话管理功能实体在预设时间段内接收到的上行数据的数据量大于或等于预设阈值。
第二方面,提供一种会话管理功能实体,该会话管理功能实体为源会话管理功能实体。该会话管理功能实体包括处理单元和发送单元。
本申请提供的各个单元模块所实现的功能具体如下:
上述处理单元,用于判断是否更新终端设备的会话,以及用于若确定更新终端设备的会话,保留第一会话的上下文,其中,第一会话为源会话管理功能 实体与终端设备之间已建立的会话;上述发送单元,用于若上述处理单元确定更新终端设备的会话,向第一设备发送指示信息,指示信息用于指示第一设备在等待至获得待发送的终端设备的数据之后触发第二会话的建立,其中,第一设备为终端设备或目标移动管理功能实体,第二会话为目标会话管理功能实体与终端设备之间的会话。
进一步地,在本申请的一种可能的实现方式中,本申请实施例中的会话管理功能实体还包括接收单元,该接收单元用于在上述发送单元向第一设备发送指示信息之后,从目标移动管理功能实体接收第一通知消息。相应的,上述处理单元,还用于在该接收单元接收到第一通知消息后,释放第一会话的上下文。
进一步地,在本申请的另一种可能的实现方式中,在第一设备为终端设备的应用场景中,上述发送单元具体用于向源移动管理功能实体发送携带指示信息的第一响应消息,指示信息被发送至终端设备,指示信息用于指示终端设备在等待至获得待发送的终端设备的数据后,向目标移动管理功能实体发送用于触发第二会话的建立的信息。在第一设备为目标移动管理实体的应用场景中,上述发送单元具体用于向源移动管理功能实体发送携带指示信息的第一响应消息,指示信息被发送至目标移动管理实体,指示信息用于指示目标移动管理功能实体等待至获得待发送的终端设备的上行数据后,选择目标会话管理功能实体,以触发第二会话的建立。
进一步地,在本申请的另一种可能的实现方式中,本申请实施例中的会话管理功能实体还包括接收单元,该接收单元用于从终端设备接收到上行数据,获取上行数据应答消息。相应的,上述处理单元,还用于在该接收单元获取到的上行数据应答消息中添加指示信息;上述发送单元,具体用于向第一设备发送携带有指示信息的上行数据应答消息。
进一步地,在本申请的另一种可能的实现方式中,本申请实施例中的会话管理功能实体还包括接收单元,该接收单元用于从源移动管理功能实体接收第二通知消息,第二通知消息携带目标移动管理功能实体的标识。相应的,上述处理单元,具体用于根据第一条件判断是否更新终端设备的会话,第一条件包括源移动管理功能实体的标识与接收单元接收到的第二通知消息所携带的目标移动管理的标识不同。
进一步地,在本申请的另一种可能的实现方式中,第一条件还包括接收单元在预设时间段内接收到的上行数据的数据量大于或等于预设阈值。
第三方面,提供一种会话管理功能实体,该会话管理功能实体为上述源会话管理功能实体,该会话管理功能实体包括:处理器、存储器和通信接口。存储器用于存储计算机程序代码,计算机程序代码包括指令,处理器、通信接口与存储器通过总线连接。当会话管理功能实体运行时,处理器执行存储器存储的指令,以使会话管理功能实体执行如上述第一方面及其任一种可能的实现方式的会话迁移方法。
第四方面,提供一种计算机存储介质,该计算机存储介质中存储有计算机程序代码。当第三方面中的会话管理功能实体的处理器执行该计算机程序代码 时,会话管理功能实体执行如上述第一方面及其任一种可能的实现方式的会话迁移方法。
第五方面,还提供一种包含指令的计算机程序产品,当其在会话管理功能实体上运行时,使得会话管理功能实体执行如上述第一方面及其任一种可能的实现方式的会话迁移方法。
在本申请中,上述会话管理功能实体的名字对设备或功能模块本身不构成限定,在实际实现中,这些设备或功能模块可以以其他名称出现。只要各个设备或功能模块的功能和本申请类似,属于本申请权利要求及其等同技术的范围之内。
本申请中第二方面、第三方面、第四方面、第五方面及其各种实现方式的具体描述,可以参考第一方面及其各种实现方式中的详细描述;并且,第二方面、第三方面、第四方面、第五方面及其各种实现方式的有益效果,可以参考第一方面及其各种实现方式中的有益效果分析,此处不再赘述。
第六方面,提供一种会话迁移方法,终端设备与源会话管理功能实体之间建立第一会话,源会话管理功能实体的服务区域包括第一跟踪区域TA;终端设备从第一TA移动到第二TA后,终端设备获取指示信息,并根据指示信息,向目标移动管理功能实体发送用于触发第二会话的建立的信息,第二会话为目标会话管理功能实体与终端设备之间的会话,目标移动管理功能实体的服务区域和目标会话管理功能实体的服务区域均包括第二TA。
可选的,在本申请的一种可能的实现方式中,终端设备获取指示信息的方法可以为终端设备向目标移动管理功能实体发送第一请求消息,相应的,该终端设备从目标移动管理功能实体接收携带有指示信息的第二响应消息;也可以为终端设备从目标移动管理功能实体接收携带有指示信息的上行数据应答消息。
可选的,在本申请的另一种可能的实现方式中,在终端设备接收携带有指示信息的第二响应消息或接收携带有指示信息的上行数据应答消息的应用场景中,上述用于触发第二会话的建立的信息为会话建立请求,这样,终端设备根据指示信息,向目标移动管理功能实体发送用于触发第二会话的建立的信息的方法为:终端设备根据指示信息,等待至获得待发送的终端设备的数据后,向目标移动管理功能实体发送会话建立请求。
该应用场景中,第二会话是终端设备在等待至获得待发送的终端设备的数据之后触发建立的,因此,不会出现未传输数据却建立了第二会话的情况,降低了核心网资源的浪费,也减少了不必要的信令传输。
可选的,在本申请的另一种可能的实现方式中,终端设备获取指示信息的方法还可以为终端设备接收携带有指示信息的下行数据。
可选的,在本申请的另一种可能的实现方式中,在终端设备接收携带有指示信息的下行数据的应用场景中,上述用于触发第二会话的建立的信息为会话建立请求或第一上行注册报文,这样,终端设备根据指示信息,向目标移动管理功能实体发送用于触发第二会话的建立的信息的方法为:终端设备接收到指 示信息后,向目标移动管理功能实体发送会话建立请求或第一上行注册报文。
在终端设备接收携带有指示信息的下行数据的应用场景中,由于有下行数据需要传输,因此指示信息用于指示终端设备在获取到该指示信息后,立刻向目标移动管理功能实体发送会话建立请求或第一上行注册报文,以触发第二会话的建立。
可选的,在本申请的另一种可能的实现方式中,在终端设备接收携带有指示信息的下行数据的应用场景中,若上述用于触发第二会话的建立的信息为会话建立请求,终端设备还向目标移动管理功能实体发送第二上行注册报文,第二注册报文用于指示目标移动管理功能实体通知应用服务器更新下行传输路径,下行传输路径为用于传输待发送至终端设备的下行数据的路径。
第七方面,提供一种终端设备,该终端设备包括处理单元、获取单元和发送单元。
本申请提供的各个单元模块所实现的功能具体如下:
上述处理单元,用于与源会话管理功能实体之间建立第一会话,源会话管理功能实体的服务区域包括第一跟踪区域TA;上述获取单元,用于终端设备从第一TA移动到第二TA后,获取指示信息;上述发送单元,用于根据上述获取单元获取到的指示信息,向目标移动管理功能实体发送用于触发第二会话的建立的信息,第二会话为目标会话管理功能实体与终端设备之间的会话,目标移动管理功能实体的服务区域和目标会话管理功能实体的服务区域均包括第二TA。
进一步地,在本申请的一种可能的实现方式中,上述发送单元,还用于向目标移动管理功能实体发送第一请求消息;相对应的,上述获取单元,具体用于从目标移动管理功能实体接收携带有指示信息的第二响应消息。可选的,上述获取单元,具体用于从目标移动管理功能实体接收携带有指示信息的上行数据应答消息。
进一步地,在本申请的一种可能的实现方式中,上述用于触发第二会话的建立的信息为会话建立请求,上述发送单元具体用于根据指示信息,等待至获得待发送的终端设备的数据后,向目标移动管理功能实体发送会话建立请求。
进一步地,在本申请的另一种可能的实现方式中,上述获取单元,具体用于接收携带有指示信息的下行数据。
进一步地,在本申请的另一种可能的实现方式中,若上述获取单元具体用于接收携带有指示信息的下行数据,则上述用于触发第二会话的建立的信息为会话建立请求或第一上行注册报文,相应的,上述发送单元具体用于在获取单元接收到指示信息后,向目标移动管理发送会话建立请求或第一上行注册报文。
进一步地,在本申请的另一种可能的实现方式中,上述发送单元,还用于向目标移动管理功能实体发送第二上行注册报文,第二注册报文用于指示目标移动管理功能实体通知应用服务器更新下行传输路径,下行传输路径为用于传输待发送至终端设备的下行数据的路径。
第八方面,提供一种终端设备,该终端设备包括:处理器、存储器和通信 接口。存储器用于存储计算机程序代码,计算机程序代码包括指令,处理器、通信接口与存储器通过总线连接。当终端设备运行时,处理器执行存储器存储的指令,以使终端设备执行如上述第六方面及其任一种可能的实现方式的会话迁移方法。
第九方面,提供一种计算机存储介质,该计算机存储介质中存储有计算机程序代码。当第八方面中的终端设备的处理器执行该计算机程序代码时,终端设备执行如上述第六方面及其任一种可能的实现方式的会话迁移方法。
第十方面,还提供一种包含指令的计算机程序产品,当其在终端设备上运行时,使得终端设备执行如上述第六方面及其任一种可能的实现方式的会话迁移方法。
在本申请中,上述终端设备的名字对设备或功能模块本身不构成限定,在实际实现中,这些设备或功能模块可以以其他名称出现。只要各个设备或功能模块的功能和本申请类似,属于本申请权利要求及其等同技术的范围之内。
本申请中第七方面、第八方面、第九方面、第十方面及其各种实现方式的具体描述,可以参考第六方面及其各种实现方式中的详细描述;并且,第七方面、第八方面、第九方面、第十方面及其各种实现方式的有益效果,可以参考第六方面及其各种实现方式中的有益效果分析,此处不再赘述。
第十一方面,提供一种会话迁移方法,目标移动管理功能实体在获取到指示信息后,根据获取到的指示信息,等待至获得待发送的终端设备的上行数据后,选择目标会话管理功能实体,以触发第二会话的建立,第二会话为目标会话管理功能实体与终端设备之间的会话。
由于第二会话是目标移动管理功能实体在等待至获得待发送的终端设备的上行数据之后触发建立的,因此,不会出现未传输数据却建立了第二会话的情况,降低了核心网资源的浪费,也减少了不必要的信令传输。
可选的,在本申请的另一种可能的实现方式中,目标移动管理功能实体获取指示信息的方法可以为目标移动管理功能实体向源移动管理功能实体发送第二请求消息,相应的,目标移动管理功能实体从源移动管理功能实体接收携带有指示信息的第三响应消息;该方法也可以为目标移动管理功能实体从源会话管理功能实体接收携带有指示信息的上行数据应答消息。
可选的,在本申请的另一种可能的实现方式中,在第二会话建立后,目标移动管理功能实体还向源会话管理功能实体发送第一通知消息,用于指示源会话管理功能实体释放第一会话的上下文,其中,第一会话为终端设备在移动前与源会话管理功能实体建立的会话。
第十二方面,提供一种移动管理功能实体,该移动管理功能实体为上述目标移动管理功能实体,该移动管理功能实体包括获取单元和处理单元。
本申请提供的各个单元模块所实现的功能具体如下:
上述获取单元,用于获取指示信息;上述处理单元,用于根据上述获取单元获取到的指示信息,等待至获得待发送的终端设备的上行数据后,选择目标会话管理功能实体,以触发第二会话的建立,第二会话为目标会话管理功能实 体与终端设备之间的会话。
进一步地,在本申请的一种可能的实现方式中,本申请实施例中的移动管理功能实体还包括发送单元,该发送单元用于向源移动管理功能实体发送第二请求消息;相应的,上述获取单元,用于从源移动管理功能实体接收携带有指示信息的第三响应消息。可选的,上述获取单元,具体用于从源会话管理功能实体接收携带有指示信息的上行数据应答消息。
进一步地,在本申请的另一种可能的实现方式中,本申请实施例中的移动管理功能实体还包括发送单元,该发送单元用于在第二会话建立后,目标移动管理功能实体向源会话管理功能实体发送第一通知消息,第一通知消息用于指示源会话管理功能实体释放第一会话的上下文,其中,第一会话为终端设备在移动前与源会话管理功能实体建立的会话。
第十三方面,提供一种移动管理功能实体,该移动管理功能实体为上述目标移动管理功能实体,该移动管理功能实体包括:处理器、存储器和通信接口。存储器用于存储计算机程序代码,计算机程序代码包括指令,处理器、通信接口与存储器通过总线连接。当移动管理功能实体运行时,处理器执行存储器存储的指令,以使移动管理功能实体执行如上述第十一方面及其任一种可能的实现方式所述的会话迁移方法。
第十四方面,提供一种计算机存储介质,该计算机存储介质中存储有计算机程序代码。当第十三方面中的移动管理功能实体的处理器执行该计算机程序代码时,移动管理功能实体执行如上述第十一方面及其任一种可能的实现方式所述的会话迁移方法。
第十五方面,还提供一种包含指令的计算机程序产品,当其在移动管理功能实体上运行时,使得移动管理功能实体执行如上述第十一方面及其任一种可能的实现方式的会话迁移方法。
在本申请中,上述移动管理功能实体的名字对设备或功能模块本身不构成限定,在实际实现中,这些设备或功能模块可以以其他名称出现。只要各个设备或功能模块的功能和本申请类似,属于本申请权利要求及其等同技术的范围之内。
本申请中第十二方面、第十三方面、第十四方面、第十五方面及其各种实现方式的具体描述,可以参考第十一方面及其各种实现方式中的详细描述;并且,第十二方面、第十三方面、第十四方面、第十五方面及其各种实现方式的有益效果,可以参考第十一方面及其各种实现方式中的有益效果分析,此处不再赘述。
本申请实施例的这些方面或其他方面在以下的描述中会更加简明易懂。
附图说明
图1为现有的下一代无线通信系统的结构示意图;
图2为现有技术中会话迁移的流程示意图;
图3为本申请实施例提供的会话迁移方法的流程示意图一;
图4为本申请实施例提供的会话迁移方法的流程示意图二;
图5为本申请实施例提供的会话迁移方法的流程示意图三;
图6为本申请实施例提供的会话迁移方法的流程示意图四;
图7为本申请实施例提供的会话迁移方法的流程示意图五;
图8为本申请实施例提供的会话迁移方法的流程示意图六;
图9为本申请实施例提供的会话迁移方法的流程示意图七;
图10为本申请实施例提供的会话迁移方法的流程示意图八;
图11为本申请实施例提供的会话迁移方法的流程示意图九;
图12为本申请实施例提供的会话迁移方法的流程示意图十;
图13为本申请实施例提供的会话迁移方法的流程示意图十一;
图14为本申请实施例提供的会话迁移方法的流程示意图十二;
图15为本申请实施例提供的会话迁移方法的流程示意图十三;
图16为本申请实施例提供的会话管理功能实体的结构示意图一;
图17为本申请实施例提供的会话管理功能实体的结构示意图二;
图18为本申请实施例提供的终端设备的结构示意图一;
图19为本申请实施例提供的终端设备的结构示意图一;
图20为本申请实施例提供的移动管理功能实体的结构示意图一;
图21为本申请实施例提供的移动管理功能实体的结构示意图二。
具体实施方式
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行详细地描述。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”和“第四”等是用于区别不同对象,而不是用于限定特定顺序。
在本申请实施例中,“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言,使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
随着通信技术的发展,出现了下一代无线通信系统。与常见的通信系统类似,下一代无线通信系统中的终端设备通过无线接入网设备、核心网设备与位于外部数据网络(Data Network)的应用服务器连接。
如图1所示,现有的下一代无线通信系统包括终端设备10、无线接入网设备11、核心网设备12以及应用服务器13。终端设备10与无线接入网设备11连接、无线接入网设备11还与核心网设备12连接,核心网设备12与应用服务器13连接。在实际应用中上述多个设备之间的连接为无线连接,为了方便直观地表示各个设备之间的连接关系,图1中采用实线示意。
上述核心网设备12的控制面功能和用户面功能可以独立设置,也可以集成在同一设备。
本申请实施例采用控制面网元120表示能够实现上述核心网设备12的控制面功能的设备,采用用户面网元121表示能够实现上述核心网设备12的用户面功能的设备。相应的,控制面网元120和用户面网元121可以独立设置, 也可以集成在同一设备。在控制面网元120和用户面网元121独立设置的场景中,应用服务器13与用户面网元121连接。
控制面网元120具备终端设备的移动管理功能、会话管理功能、网络之间互连的协议(Internet Protocol,IP)地址分配功能以及生成网关用户面的转发规则功能等。该控制面网元120可以为移动管理实体(Mobility Management Entity,MME),也可以为策略与计费规则功能(Policy and Charging Rules Function,PCRF)实体,还可以为集成了MME的功能、PCRF的功能以及其他网关的功能的设备。
控制面网元120可以包括移动管理(mobility management,MM)功能实体120a和会话管理(session management,SM)功能实体120b。移动管理功能实体120a和会话管理功能实体120b可以独立设置,也可以集成在同一设备。
其中,移动管理功能实体120a负责终端设备的附着、移动性管理、TA的更新、为终端设备分配临时身份标识(Identification,ID)、对终端设备认证和授权等。会话管理功能实体120b负责为终端设备选择用户面网元121、用户面网元121的迁移、IP地址分配等。
此外,图1所示的下一代无线通信系统还包括用户数据管理(User Data Management,UDM)设备14。UDM设备14与移动管理功能实体120a和会话管理功能实体120b均连接。其中,移动管理功能实体120a可以从UDM设备14获取终端设备10的移动管理签约数据,会话管理功能实体120b可以从UDM设备14获取终端设备10的会话管理签约数据。
在图1所示的下一代无线通信系统中,当终端设备10与核心网设备12之间的数据传输业务为小包业务时,小包业务对时延的要求和QoS的要求均比较低,因此,终端设备10与核心网设备12之间的会话无需一直保持连续。
TA用于定位终端设备的位置。终端设备在附着到网络后,该网络中的控制面网元为其分配了一组注册的TA,即TA列表(TA list)。当终端设备进入新的TA(终端设备确定TA LIST中未包括其当前所处的TA),或当终端设备的周期TA更新定时器超时后,该终端设备发起TA更新流程。若终端设备移动至新的TA后,新的TA是由另一个控制面网元管理的,则触发终端发起跨控制面网元的TA更新流程,此时需要对该终端设备的会话进行迁移。
图2示出了现有技术中终端设备的会话的迁移过程。结合图1,如图2所示,若核心网设备12和核心网设备12'均与应用服务器13连接,无线接入网设备11的服务区域和核心网设备12的服务区域均包括第一TA,无线接入网设备11'的服务区域和核心网设备12'的服务区域均包括第二TA。在某一时刻,终端设备10已经与核心网设备12建立第一会话,核心网设备12存储有第一会话的上下文。在终端设备10从第一TA移动到第二TA后,核心网设备12释放其与终端设备10之间的第一会话,即核心网设备12删除第一会话的会话上下文,并指示终端设备10向核心网设备12'发送会话建立请求,这样,终端设备10与核心网设备12'之间建立第二会话,终端设备10可以通过核心网设备12'传输终端设备A的数据。
可以看出,终端设备10是在接收到核心网设备12发送的指示后,建立了该终端设备10与核心网设备12'之间的第二会话,但是,核心网设备12向终端设备10发送指示时,就释放了该核心网设备12与终端设备10之间的第一会话,因此,对于待发送至终端设备10的下行数据而言,有可能不存在数据传输链路用以传输该下行数据,导致该下行数据可能出现丢包现象。此外,若终端设备10在移动到第二TA后,并未传输数据(即未发送上行数据,且未接收下行数据),那么终端设备10与核心网设备12'之间建立第二会话,会导致核心网资源的浪费和不必要的信令传输。
针对上述问题,本申请实施例提供一种会话迁移方法。在该会话迁移方法中,若源会话管理功能实体与某一终端设备之间已经建立第一会话,则在该源会话管理功能实体确定更新该终端设备的会话时,该源会话管理功能实体保留第一会话的上下文,并向该终端设备或目标移动管理功能实体发送指示信息,用于指示终端设备或目标移动管理功能实体在等待至获得待发送的终端设备的数据之后触发建立第二会话,该第二会话为终端设备与目标会话管理功能实体之间的会话。由于在第二会话建立之前,源会话管理功能实体保留了第一会话的上下文,因此,即使有待发送至该终端设备的下行数据,也能够准确的发送至该终端设备,保证了下行数据无丢包。又由于第二会话是终端设备或目标移动管理功能实体在等待至获得待发送的终端设备的数据之后触发建立的,因此,在未传输终端设备的数据的场景中,无需建立第二会话,这样,降低了核心网资源的浪费,也减少了不必要的信令传输。
本申请实施例提供的会话迁移方法适用于存在小包业务的无线通信系统。该无线通信系统可以为上述下一代无线通信系统。为了便于描述,本申请实施例以无线通信系统为图1所示的下一代无线通信系统为例进行说明。
本申请实施例中的终端设备10可以是指向用户提供语音和/或数据连通性的设备,具有无线连接功能的手持式设备、或连接到无线调制解调器的其他处理设备。无线终端可以经无线接入网(Radio Access Network,RAN)与一个或多个核心网进行通信。无线终端可以是移动终端,如移动电话(或称为“蜂窝”电话)和具有移动终端的计算机,也可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置,它们与无线接入网交换语言和/或数据,例如,手机、平板电脑、笔记本电脑、上网本、个人数字助理(Personal Digital Assistant,PDA)。
本申请实施例中的无线接入设备11可以为无线接入点(Access Point,AP),也可以为演进式基站(英文:evolved Node Base Station,简称:eNB),还可以为NR gNB,NR gNB表示第五代通信技术(the 5Generation Mobile Communication Technology,5G)网络中的基站,本申请实施例对此不作具体限定。
从上述描述可知,控制面网元和用户面网元可以独立设置,也可以集成在同一设备。本申请实施例主要以控制面网元和用户面网元独立设置为例进行说明。
一般的,对于进行小包传输业务的终端设备而言,为该终端设备创建会话的方法可以分为以下三种:
1、终端设备的附着过程和会话建立过程同时完成。
终端设备附着到网络时,向该网络中的移动管理功能实体发送携带该终端设备的永久标识和数据网络名称(Data network name,DNN)的附着请求。移动管理功能实体在接收到附着请求后,移动管理功能实体向UDM设备获取终端设备的移动管理签约数据,对该终端设备进行鉴权,并为该终端设备分配临时身份标识以及选择会话管理功能实体。移动管理功能实体选择出的会话管理功能实体向UDM设备获取终端设备的会话管理签约数据、根据终端设备发送的附着请求以及终端设备的能力信息为该终端设备创建会话,并存储该会话的上下文,该会话的上下文包括会话管理功能实体为该终端设备分配的用户面网元的标识和IP地址等。这样,该终端设备可进行正常的小包传输业务。
2、终端设备的附着过程和会话建立过程相互独立:终端设备在附着到网络之后,再建立会话,建立会话完成后再发送上行数据。
在终端设备的附着过程中,移动管理功能实体向UDM设备获取终端设备的移动管理签约数据,对终端设备鉴权,并为终端设备分配临时身份标识。在终端设备附着到网络后,终端设备向该网络中的移动管理功能实体发送会话建立请求。移动管理功能实体在接收到会话建立请求后,选择会话管理功能实体,并向选择的会话管理功能实体发送会话建立请求,以请求会话管理功能实体为该终端设备创建会话,即请求会话管理功能实体为该终端设备分配用户面网元和IP地址等。会话管理功能实体向UDM设备获取终端设备的会话管理签约数据,在会话管理功能实体为该终端设备建立会话后,该终端设备可进行正常的小包传输业务。
3、终端设备的附着过程和会话建立过程相互独立:终端设备在附着到网络之后,直接发送上行数据,以触发控制面网元为该终端设备建立会话。
在终端设备的附着过程中,移动管理功能实体对终端设备鉴权,并为终端设备分配临时身份标识,移动管理功能实体可获取到该终端设备的移动管理签约数据。在附着到网络后,终端设备直接发送上行数据,该上行数据以上行数据报文的形式体现,由于此时还没有为该终端设备建立会话,因此,该终端设备还没有被分配到IP地址,该上行数据报文是非IP报文。移动管理功能实体在接收到上行数据报文之后,根据上行数据报文的源地址确定还未为该终端设备创建会话上下文。移动管理功能实体选择会话管理功能实体,并请求会话管理功能实体为该终端设备创建会话。会话管理功能实体根据该终端设备的会话管理签约数据,为该终端设备分配用户面网元和IP地址(该IP地址不向终端设备返回,只是用于将非IP报文封装成IP报文发送至通信对端)、创建会话上下文。该会话创建完成之后,会话管理功能实体向用户面网元转发移动管理功能实体发送的上行数据报文。用户面网元根据会话上下文封装其接收到的上行数据报文,并将封装后的上行数据报文发送至外部网络,之后该终端设备可进行正常的小包传输业务。
需要说明的是,上述方法3仅适用于终端设备发送的数据以非IP报文的形式体现的情况中。
基于上述方法2,本申请实施例中的源会话管理功能实体在确定更新终端设备的会话后,可以指示终端设备在等待至获得待发送的终端设备的数据后,向目标移动管理功能实体发送用于触发第二会话的建立的信息,也可以指示终端设备在获取到指示信息后,立即向目标移动管理功能实体发送用于触发第二会话的建立的信息。基于上述方法3,本申请实施例中的源会话管理功能实体在确定更新终端设备的会话后,可指示目标移动管理功能实体等待至获得待发送的终端设备的上行数据后,选择目标会话管理功能实体,以触发第二会话的建立。
为了方便理解本申请实施例提供的会话迁移方法,本申请实施例以移动管理功能实体和会话管理功能实体独立设置为例进行说明。
为了便于描述,本申请实施例将源无线接入网设备用基站1表示,将源移动管理功能实体用MM 1表示,将源会话管理功能实体用SM 1表示,将源用户面网元用用户面网元1表示,将目标无线接入网设备用基站2表示,将目标移动管理功能实体用MM 2表示,将目标会话管理功能实体用SM 2表示,将目标用户面网元用用户面网元2表示。
图3是本申请实施例提供的会话迁移方法的流程示意图,该会话迁移方法可以应用在图1所示的下一代无线通信系统中。
参见图3,该会话迁移方法包括:
S300、终端设备与SM 1之间建立有第一会话。
SM 1的服务区域包括第一TA,SM 1存储有第一会话的上下文。
终端设备与SM 1之间建立有第一会话,则说明MM 1已经对该终端设备认证和授权,并为该终端设备分配了临时ID(本申请实施例将该临时ID用临时ID 1表示)等。SM 1已经为该终端设备选择了用户面网元1,并为该终端设备分配了IP地址等。
这里,第一会话的建立方法可以是在终端设备附着到第一TA的网络时,MM 1选择SM 1,SM 1根据终端设备的会话管理签约数据为该终端设备创建第一会话,并存储第一会话的上下文;也可以是在终端设备附着到网络后,终端设备向MM 1发送会话建立请求,请求MM 1选择SM 1,以使得SM 1为该终端设备创建会话,建立会话完成后终端设备再发送上行数据;还可以是在终端设备附着到第一TA的网络后,终端设备直接发送上行数据,以触发MM 1建立SM 1与终端设备之间的第一会话。也就是说,这里第一会话的建立方法可以参考上述建立会话的方法1、方法2或方法3。
S301、SM 1判断是否更新终端设备的会话。
具体的,SM 1根据第一条件判断是否更新终端设备的会话。
其中,第一条件包括MM 1的标识与MM 2的标识不同。其中,SM 1获取MM 2的标识的方法为在该SM 1与终端设备建立第一会话之后,SM 1接 收MM 1发送的携带有MM 2的标识的第二通知消息。
可选的,第一条件还包括SM 1在预设时间段内接收到的上行数据的数据量大于或等于预设阈值。这里,SM 1在预设时间段内接收到的上行数据可以包括该终端设备发送的上行数据,也可以包括已经与该SM 1建立会话的其他终端设备发送的上行数据。
S302、若SM 1确定更新终端设备的会话,SM 1保留第一会话的上下文,并向第一设备发送指示信息。
该指示信息用于指示第一设备在等待至获得待发送的终端设备的数据之后触发第二会话的建立。第一设备为终端设备或MM 2,第二会话为SM 2与终端设备之间的会话。
若第一设备为终端设备,该指示信息具体用于指示该终端设备在等待至获得待发送的终端设备的数据后,向MM 2发送会话建立请求,以触发第二会话的建立,下述图4或图5描述了这一应用场景的具体流程;或者该指示信息具体用于指示该终端设备在获取到指示信息后,立刻向MM 2发送会话建立请求,以触发第二会话的建立,下述图8描述了这一应用场景的具体流程;或者该指示信息具体用于指示该终端设备在获取到指示信息后,立刻向MM 2发送第一上行注册报文,以触发第二会话的建立,下述图9描述了这一应用场景的具体流程。
对于第一设备为终端设备的情况,图3用S302a表示。
若第一设备为MM 2,该指示信息具体用于指示该MM 2在等待至获得终端设备发送的上行数据后,选择SM 2,以触发第二会话的建立,下述图6或图7描述了这一应用场景的具体流程。
对于第一设备为MM 2的情况,图3用S302b表示。
S303、第一设备根据指示信息,在等待至获得待发送的终端设备的数据之后触发第二会话的建立。
若第一设备为终端设备,S302a之后执行S303a。若第一设备为MM 2,S302b之后执行S303b。
S304、在第二会话建立后,MM 2向SM 1发送第一通知消息。
无论第一设备是终端设备还是MM 2,在第二会话建立后,MM 2均可向SM 1发送第一通知消息。
S305、SM 1释放第一会话的上下文。
本申请实施例中的SM 1在第二会话建立之前,保留了第一会话的上下文,因此,即使有待发送至终端设备的下行数据,也能够准确的发送到终端设备,保证了下行数据无丢包。又由于第二会话是第一设备在等待至获得待发送的终端设备的数据后,触发建立的,因此,不会出现未传输数据却建立了第二会话的情况,降低了核心网资源的浪费,也减少了不必要的信令传输。
为了更加清楚的理解本申请实施例提供的会话迁移方法,本申请实施例对上述每种应用场景进行描述。
参见图4,本申请实施例提供的会话迁移方法包括:
S400、终端设备与SM 1之间建立有第一会话。
这里,SM 1的服务区域包括第一TA,SM 1存储有第一会话的上下文。
终端设备与SM 1之间建立有第一会话,则说明MM 1已经对该终端设备认证和授权,并为该终端设备分配了临时ID(本申请实施例将该临时ID用临时ID 1表示)等。SM 1已经为该终端设备选择了用户面网元1,并为该终端设备分配了IP地址等。
这里,第一会话的建立方法可以是在终端设备附着到第一TA的网络时,MM 1选择SM 1,SM 1根据终端设备的会话管理签约数据为该终端设备创建第一会话,并存储第一会话的上下文;也可以是在终端设备附着到网络后,终端设备向MM 1发送会话建立请求,请求MM 1选择SM 1,以使得SM 1为该终端设备创建会话,建立会话完成后终端设备再发送上行数据。也就是说,这里第一会话的建立方法可以参考上述建立会话的方法1或方法2。
终端设备与SM 1建立第一会话后,终端设备的数据根据该第一会话进行传输。如图4所示,终端设备的上行数据沿着终端设备→基站1→MM 1→SM 1→用户面网元1传输。相应的,待发送至终端设备的下行数据沿着用户面网元1→SM 1→MM 1→基站1→终端设备传输。
本申请实施例中的第一会话的上下文包括第一会话中终端设备的IP地址、用户面网元1的地址信息以及SM 1功能实体的地址信息。
S401、终端设备从第一TA移动到第二TA后,向基站2发送第一请求消息。
终端设备从第一TA移动到第二TA后,为该终端设备提供服务的基站从基站1更新为基站2。
终端设备在移动到第二TA后,检测第二TA是否在其存储的TA列表中(该TA列表为在终端设备附着到网络的过程,MM 1发送到该终端设备的)。若第二TA未在其存储的TA列表中,则该终端设备向基站2发送携带第一TA的标识、DNN、MM 1的标识和终端设备的临时ID 1的第一请求消息。
DNN用于标识终端设备通过基站1、MM 1、以及SM 1连接的数据网络。
可选的,本申请实施例中的第一请求消息可以为跟踪区域更新(Tracking Area Update,TAU)请求消息。
S402、基站2向MM 2转发S401中的第一请求消息。
由于基站2与MM 1之间无接口连接,因此,基站2根据上述第一请求消息中携带的MM 1无法寻址到MM 1。终端设备在移动到第二TA后,基站2为该终端设备提供服务,相应的,基站2可获取到该终端设备的位置信息。这样,基站2根据该终端设备的位置信息,为该终端设备在第二TA内选择MM 2,并向MM 2转发上述第一请求消息。
S403、MM 2向MM 1发送第二请求消息,以请求获取终端设备的移动管理上下文。
与上述第一会话的上下文不同,本申请实施例中终端设备的移动管理上下 文是指与移动管理相关的上下文。例如,终端设备的移动管理上下文包括终端设备的移动管理签约数据。
MM 2根据其接收到的第一请求消息中携带的MM 1的标识确定MM 1,并向MM 1发送第二请求消息,以请求获取终端设备的移动管理上下文。该第二请求消息携带MM 2的标识和临时ID 1。
MM 1和MM 2虽然归属于不同的TA,但是,MM 1与MM 2之间存在通信连接。因此,MM 2可直接向MM 1发送第二请求消息。
S404、MM 1查找其存储的移动管理上下文列表,确定与临时ID 1对应的SM为SM 1,并确定与临时ID 1对应的终端设备的永久标识,并向SM 1发送第二通知消息,以通知SM 1将其存储的第一会话的上下文中的MM 1的标识更新为MM 2的标识。
其中,第二通知消息携带MM 2的标识和终端设备的永久标识。
S405、SM 1根据MM 2的标识,判断是否更新该终端设备的会话。
例如,SM 1接收到第二通知消息后,确定该第二通知消息中的MM 2的标识与其存储的MM 1的标识不同,如此,该SM 1确定终端设备发生了移动。SM 1确定终端设备发生移动后,将第一会话的上下文中的MM 1的标识更新为MM 2的标识。
确定终端设备发送了移动后,SM 1判断当前数据传输路径是否满足预设条件(该预设条件可以为数据传输路径的跳数是否大于或等于预设跳数),以确定是否更新终端设备的会话;或者,SM 1判断该SM 1在预设时间段内接收到的上行数据的数据量是否大于或等于预设阈值,以便于根据判断结果确定是否更新终端设备的会话,这里预设时间段是指时间长度为预设长度的任一时间段。
可选的,若SM 1确定当前数据传输路径的跳数大于或等于预设跳数,则该SM 1确定更新终端设备的会话。反之,该SM 1确定暂时无需更新终端设备的会话。
可选的,若SM 1确定该SM 1在预设时间段内接收到的上行数据的数据量大于或等于预设阈值,则该SM 1确定更新终端设备的会话。反之,该SM 1确定暂时无需更新终端设备的会话。
S406、若SM 1确定更新终端设备的会话,SM 1保留第一会话的上下文,并向MM 1发送携带指示信息以及SM 1的标识的第一响应消息。
例如,MM 2的标识与SM 1存储的MM 1的标识不同,且SM 1在预设时间段内接收到的上行数据的数据量大于或等于预设阈值,则SM 1确定更新终端设备的会话。
本实施例(图4所示的实施例)中的指示信息用于指示终端设备在等待至获得待发送的终端设备的数据后,向MM 2发送会话建立请求,以触发第二会话的建立。
S407、MM 1向MM 2发送携带指示信息、SM 1的标识、终端设备的移动管理上下文以及终端设备的永久标识的第三响应消息。
S408、MM 2存储SM 1的标识和终端设备的移动管理上下文,并为终端设备分配新的临时ID(本申请实施例用临时ID 2表示该新的临时ID)。
S409、MM 2向基站2发送携带指示信息、临时ID 2和MM 2的标识的第二响应消息。
S410、基站2向终端设备转发S409中的第二响应消息。
终端设备在接收到携带有指示信息的第二响应消息后,在等待至获得待发送的终端设备的数据后,向MM 2发送会话建立请求,以触发终端设备与SM 2之间的第二会话的建立。
由于SM 1保留第一会话的上下文,因此,在第二会话未建立之前,即使用户面网元1接收到待发送至终端设备的下行数据,该下行数据也可传输到终端设备,保证了下行数据不丢包。
由于SM 1与MM 1连接,也可与MM 2连接,且SM 1已经获知终端设备已经移动至MM 2的服务区域,因此,对于用户面网元1接收到待发送至终端设备的下行数据而言,该下行数据可以沿着用户面网元1→SM 1→MM 2→基站2→终端设备传输,也可沿着用户面网元1→SM 1→MM 1→MM 2→基站2→终端设备传输(例如在漫游场景中)。本申请实施例对此不作具体限定。
S411、在等待至获得待发送的终端设备的数据后,终端设备向基站2发送携带DNN和会话类型信息的会话建立请求。
从上面描述可知,上行数据可以用上行数据报文的形式体现,且终端设备发送的上行数据报文可以为IP报文,也可以为非IP报文。会话建立请求中的会话类型信息用于指示上行数据报文的类型(即该会话是否为IP类型的会话)。
S412、基站2向MM 2转发S411中的会话建立请求。
S413、MM 2根据终端设备的移动管理上下文对终端设备进行验证授权,并根据S412中的会话建立请求所携带的DNN和会话类型信息以及MM 2本地存储的终端设备的签约数据为该终端设备选择SM 2。
S414、MM 2向SM2发送会话建立请求以及终端设备的永久标识。
S415、SM 2根据终端设备的永久标识,获取该终端设备的会话管理签约数据,并根据该终端设备的会话管理签约数据为终端设备选择用户面网元2。
例如,SM 2根据终端设备的永久标识,向UDM功能实体发送签约数据请求,以获取该终端设备的会话管理签约数据。
若会话建立请求中的会话类型信息指示该会话传输的上行数据报文为IP报文,则SM-2还需要为终端设备分配新的IP地址。
S416、SM 2向用户面网元2发送用户面转发规则,并创建第二会话的上下文。
S417、SM 2向MM 2发送会话建立响应,MM 2向基站2发送会话建立响应,基站2向终端设备发送会话建立响应。
终端设备接收到上述会话建立响应后,第二会话的建立过程结束。这样,终端设备的上行数据沿着终端设备→基站2→MM 2→SM 2→用户面网元2传输。相应的,待发送至终端设备的下行数据沿着用户面网元2→SM 2→MM 2 →基站2→终端设备传输。
在第二会话建立结束后,MM 2还可向SM 1发送第一通知消息,用以指示SM 1释放第一会话的上下文,减少源核心网设备的资源浪费。
如图4所示,在S417之后,本申请实施例提供的会话迁移方法还包括S418和S419。
S418、MM 2向SM 1发送第一通知消息,以指示SM 1释放第一会话的上下文。
其中,第一通知消息的传输路径可以是MM 2→SM 1,也可以是MM 2→MM 1→SM 1,本申请实施例对此不作具体限定。
S419、SM 1释放第一会话的上下文。
从上面描述可知,本申请实施例还存在另一应用场景:SM 1在接收到第二通知消息之后,确定无需更新终端设备的会话。本申请实施例在图5中示出了该应用场景的流程。
参见图5,本申请实施例提供的会话迁移方法包括:
S500、终端设备与SM 1之间建立有第一会话。
S501、终端设备从第一TA移动到第二TA后,向基站2发送第一请求消息。
该第一请求消息携带第一TA的标识、DNN、MM 1的标识和终端设备的临时ID 1。
S502、基站2向MM 2转发S401中的第一请求消息。
S503、MM 2向MM 1发送第二请求消息,以请求获取终端设备的移动管理上下文。
S504、MM 1查找其存储的移动管理上下文列表,确定与临时ID 1对应的SM为SM 1,且与临时ID 1对应的终端设备的永久标识,并向SM 1发送第二通知消息,以通知SM 1将其存储的第一会话的上下文中的MM 1的标识更新为MM 2的标识。
该第二通知消息携带MM 2的标识和终端设备的永久标识。
S505、SM 1根据MM 2的标识,判断是否更新该终端设备的会话。
SM 1接收到第二通知消息后,确定该第二通知消息中的MM 2的标识与其存储的MM 1的标识不同,如此,该SM 1确定终端设备发生了移动。SM1确定终端设备发生移动后,将第一会话的上下文中的MM 1的标识更新为MM 2的标识。
确定终端设备发送了移动后,SM 1判断是否更新该终端设备的会话。这里,SM 1判断是否更新该终端设备的会话的方法可以参考上述S405的描述,此处不再进行详细赘述。
S506、若SM 1确定暂时无需更新终端设备的会话,SM 1保留第一会话的上下文,并向MM 1发送携带SM 1的标识的第一响应消息。
与上述S406相比,在S506中,虽然MM 2的标识与SM 1存储的MM 1的标识不同,但是SM 1在预设时间段内接收到的上行数据的数据量小于预设 阈值,因此,SM 1确定暂时无需更新终端设备的会话。
S507、MM 1向MM 2发送携带SM 1的标识、终端设备的移动管理上下文以及终端设备的永久标识的第三响应消息。
S508、MM 2存储SM 1的标识和终端设备的移动管理上下文,并为终端设备分配临时ID 2。
S509、MM 2向基站2发送携带临时ID 2和MM 2的标识的第二响应消息。
S510、基站2向终端设备转发S509中的第二响应消息。
与图4所示的实施例相同,在图5所示的实施例中,由于SM 1保留第一会话的上下文,因此,在第二会话未建立之前,即使用户面网元1接收到待发送至终端设备的下行数据,该下行数据也可传输到终端设备,保证了下行数据不丢包。
SM 1与MM 1连接,也可与MM 2连接,且SM 1已经获知终端设备已经移动至MM 2的服务区域,因此,对于用户面网元1接收到待发送至终端设备的下行数据而言,该下行数据可以沿着用户面网元1→SM 1→MM 2→基站2→终端设备传输,也可沿着用户面网元1→SM 1→MM1→MM 2→基站2→终端设备传输,本申请实施例对此不作具体限定。
在S506中SM 1确定暂时无需更新终端设备的会话之后的预设时间段后,SM 1再次判断是否更新终端设备的会话。
S511、SM 1判断是否更新终端设备的会话。
SM 1在上述S505中已经确定终端设备发生了移动,因此,S511中SM 1判断该SM 1在S506之后的预设时间段内接收到的上行数据的数据量是否大于或等于预设阈值。
若SM 1在S506之后的预设时间段内接收到的上行数据的数据量大于或等于预设阈值,则SM 1确定更新终端设备的会话。若SM 1在S506之后的预设时间段内接收到的上行数据的数据量小于预设阈值,则SM 1依旧确定暂时无需更新终端设备的会话。
在S511执行的过程中,终端设备可能会发送上行数据,相应的,SM 1会接收到该上行数据,并向用户面网元1发送其接收到的上行数据。随后,该SM 1会接收到用户面网元1发送的上行数据应答消息。
可选的,该上行数据应答消息可以为携带ACK的消息。
S512、若SM 1确定更新终端设备的会话,则SM 1保留第一会话的上下文,在接收到的上行数据应答消息中添加指示信息,并向MM 2发送携带有指示信息的上行数据应答消息。
本实施例(图5所示的实施例)中的指示信息用于指示终端设备在等待至获得待发送的终端设备的数据后,向MM 2发送会话建立请求,以触发第二会话的建立。
S513、MM 2向基站2转发携带有指示信息的上行数据应答消息。
S514、基站2向终端设备转发携带有指示信息的上行数据应答消息。
终端设备在接收到携带有指示信息的上行数据应答消息后,在等待至获得 待发送的终端设备的数据后,向MM 2发送会话建立请求,以触发终端设备与SM 2之间的第二会话的建立。
S515、在等待至获得待发送的终端设备的数据后,终端设备向基站2发送携带DNN和会话类型信息的会话建立请求。
S516、基站2向MM 2转发S515中的会话建立请求。
S517、MM 2根据终端设备的移动管理上下文对终端设备进行验证授权,并根据S516中的会话建立请求是携带的DNN和会话类型信息以及MM 2本地存储的终端设备的签约数据,为该终端设备选择SM 2。
S518、MM 2向SM2发送会话建立请求以及终端设备的永久标识。
S519、SM 2根据终端设备的永久标识,获取该终端设备的会话管理签约数据,并根据该终端设备的会话管理签约数据为终端设备选择用户面网元2。
S520、SM 2向用户面网元2发送用户面转发规则,并创建第二会话的上下文。
S521、SM 2向MM 2发送会话建立响应,MM 2向基站2发送会话建立响应,基站2向终端设备发送会话建立响应。
在第二会话建立结束后,MM 2还可向SM 1发送第一通知消息,用以指示SM 1释放第一会话的上下文,减少源核心网设备的资源浪费。
如图5所示,在S521之后,本申请实施例提供的会话迁移方法还包括S522和S523。
S522、MM 2向SM 1发送第一通知消息,以指示SM 1释放第一会话的上下文。
S523、SM 1释放第一会话的上下文。
S500-S505可参考图4中的S400-S405的描述,S515-S523可以参考图4中的S411-S419的描述,此处不再赘述。
由于图4或图5所示的实施例中的SM 1在第二会话建立之前,保留了第一会话的上下文,因此,即使有待发送至终端设备的下行数据,也能够准确的发送到终端设备,保证了下行数据无丢包。又由于第二会话是终端设备在等待至获得待发送的终端设备的数据后,触发目标MM 2建立的,因此,不会出现未传输数据却建立了第二会话的情况,降低了核心网资源的浪费,也减少了不必要的信令传输。
在图4或图5所示的实施例中,终端设备与SM 1之间建立第一会话采用前述建立会话的方法1或方法2。从前述描述可知,现有的建立会话的方法有三种(方法1、方法2和方法3)。图6所示的实施例提供的会话迁移方法适用于终端设备与SM 1之间采用前述方法3建立第一会话,且终端设备从第一TA移动到第二TA的应用场景。该应用场景中,指示信息用于指示MM 2在等待至获得待发送的终端设备的上行数据后,选择SM 2,以触发第二会话的建立。
如图6所示,在该应用场景中,本申请实施例提供的会话迁移方法包括:
S600、终端设备与SM 1之间建立有第一会话。
这里,第一会话的建立方法是在终端设备附着到第一TA的网络后,终端 设备直接发送上行数据,以触发MM 1建立SM 1与终端设备之间的第一会话。这里,建立第一会话的具体过程可以参考上述建立会话的方法3。
与图4或图5所示的实施例相同,在S600的终端设备与SM 1建立第一会话后,终端设备的数据根据该第一会话进行传输。如图6所示,终端设备的上行数据沿着终端设备→基站1→MM 1→SM 1→用户面网元1传输。相应的,待发送至终端设备的下行数据沿着用户面网元1→SM 1→MM 1→基站1→终端设备传输。
S601、终端设备从第一TA移动到第二TA后,向基站2发送第一请求消息。
其中,第一请求消息携带第一TA的标识、DNN、MM 1的标识和临时ID 1。
S602、基站2向MM 2转发S601中的第一请求消息。
S603、MM 2向MM 1发送携带MM 2的标识和临时ID 1的第二请求消息,以请求获取终端设备的移动管理上下文。
S604、MM 1查找其存储的移动管理上下文列表,确定与临时ID 1对应的SM为SM 1,并确定与临时ID 1对应的终端设备的永久标识,并向SM 1发送携带MM 2的标识和终端设备的永久标识的第二通知消息,以通知SM 1将其存储的第一会话的上下文中的MM 1的标识更新为MM 2的标识。
S605、SM 1根据MM2的标识,判断是否更新该终端设备的会话。
S606、若SM 1确定更新终端设备的会话,SM 1保留第一会话的上下文,并向MM 1发送携带指示信息以及SM 1的标识的第一响应消息。
本实施例(图6所示的实施例)中的指示信息用于指示MM 2在等待至获得待发送的终端设备的上行数据后,选择SM 2,以触发第二会话的建立。
S607、MM 1向MM 2发送携带指示信息、SM 1的标识、终端设备的移动管理上下文以及终端设备的永久标识的第三响应消息。
S608、MM 2存储SM 1的标识和终端设备的移动管理上下文,并为终端设备分配临时ID 2。
S609、MM 2向基站2发送携带临时ID 2和MM 2的标识的第二响应消息。
S610、基站2向终端设备转发S609中的第二响应消息。
由于SM 1保留了第一会话的上下文,因此,在第二会话未建立之前,即使用户面网元1接收到待发送至终端设备的下行数据,该下行数据也可传输到终端设备,保证了下行数据不丢包。
由于SM 1与MM 1连接,也可与MM 2连接,且SM 1已经获知终端设备已经移动至MM 2的服务区域,因此,对于用户面网元1接收到待发送至终端设备的下行数据而言,该下行数据可以沿着用户面网元1→SM 1→MM 2→基站2→终端设备传输,也可沿着用户面网元1→SM 1→MM1→MM 2→基站2→终端设备传输,本申请实施例对此不作具体限定。
S611、终端设备向基站2发送携带临时ID 2和MM 2的标识的上行数据报文。
S612、基站2向MM 2转发S611中的上行数据报文。
S613、MM 2在接收到上行数据报文后,根据指示信息,利用终端设备的移动管理上下文对终端设备进行验证授权,并根据终端设备的签约数据以及上行数据报文的数据类型等信息为该终端设备选择SM 2。
S614、MM 2向SM2发送会话建立请求以及终端设备的永久标识。
S615、SM 2根据终端设备的永久标识,获取该终端设备的会话管理签约数据,并根据该终端设备的会话管理签约数据为终端设备选择用户面网元2。
S616、SM 2向用户面网元2发送用户面转发规则,并创建第二会话的上下文。
S617、SM 2向MM 2发送会话建立响应。
S618、MM 2向SM 2发送MM 2在S612中接收到的上行数据报文,SM 2向用户面网元2转发该上行数据报文。
MM 2接收到上述会话建立响应后,第二会话的建立过程结束。这样,终端设备的上行数据沿着终端设备→基站2→MM 2→SM 2→用户面网元2传输。相应的,待发送至终端设备的下行数据沿着用户面网元2→SM 2→MM 2→基站2→终端设备传输。
在第二会话建立结束后,MM 2还可向SM 1发送第一通知消息,用以指示SM 1释放第一会话的上下文,减少源核心网设备的资源浪费。
如图6所示,在S617之后,本申请实施例提供的会话迁移方法还包括S619和S620。
S619、MM 2向SM 1发送第一通知消息,以指示SM 1释放第一会话的上下文。
其中,第一通知消息的传输路径可以是MM 2→SM 1,也可以是MM 2→MM 1→SM 1,本申请实施例对此不作具体限定。
S620、SM 1释放第一会话的上下文。
其中,本申请实施例中的SM 1可以先执行S618,后执行S619,也可以先执行S619,后执行S618,还可以同时执行S618和S619,本申请实施例对此不作具体限定。
本实施例中的S600-S608与图4所示实施例中的S400-S408类似,不同的是,本实施例中S600中建立第一会话所采用的方法与S400中建立第一会话所采用的方法不同,本实施例中的指示信息所指示的内容与图4所示实施例中的指示信息所指示的内容不同。
由于本实施例中的指示信息指示MM 2在等待至获得待发送的终端设备的上行数据后,选择SM 2,以触发第二会话的建立,因此,与图4所示的实施例相比,本实施例中指示信息无需发送至终端设备,会话建立请求是由MM2发起,而图4中会话建立请求时由终端设备发起的。
结合图6,本申请实施例提供的会话迁移方法在S605之后,SM 1也可确定无需更新终端设备的会话。本申请实施例在图7中示出了该应用场景的流程。
参见图7,本申请实施例提供的会话迁移方法包括:
S700、终端设备与SM 1之间建立有第一会话。
S701、终端设备从第一TA移动到第二TA后,向基站2发送第一请求消息。
其中,第一请求消息携带第一TA的标识、DNN、MM 1的标识和临时ID 1。
S702、基站2向MM 2转发S601中的第一请求消息。
S703、MM 2向MM 1发送携带MM 2的标识和临时ID 1的第二请求消息,以请求获取终端设备的移动管理上下文。
S704、MM 1查找其存储的移动管理上下文列表,确定与临时ID 1对应的SM为SM 1,并确定与临时ID 1对应的终端设备的永久标识,并向SM 1发送携带MM 2的标识和终端设备的永久标识的第二通知消息,以通知SM 1将其存储的第一会话的上下文中的MM 1的标识更新为MM 2的标识。
S705、SM 1根据MM2的标识,判断是否更新该终端设备的会话。
S706、若SM 1确定暂时无需更新终端设备的会话,SM 1保留第一会话的上下文,并向MM 1发送携带SM 1的标识SM 1的第一响应消息。
S707、MM 1向MM 2发送携带SM 1的标识、终端设备的移动管理上下文以及终端设备的永久标识的第三响应消息。
S708、MM 2存储SM 1的标识和终端设备的移动管理上下文,并为终端设备分配临时ID 2。
S709、MM 2向基站2发送携带临时ID 2和MM 2的标识的第二响应消息。
S710、基站2向终端设备转发S709中的第二响应消息。
与图6所示的实施例相同,在图7所示的实施例中,由于SM 1保留第一会话的上下文,因此,在第二会话未建立之前,即使用户面网元1接收到待发送至终端设备的下行数据,该下行数据也可传输到终端设备,保证了下行数据不丢包。
SM 1与MM 1连接,也可与MM 2连接,且SM 1已经获知终端设备已经移动至MM 2的服务区域,因此,对于用户面网元1接收到待发送至终端设备的下行数据而言,该下行数据可以沿着用户面网元1→SM 1→MM 2→基站2→终端设备传输,也可沿着用户面网元1→SM 1→MM1→MM 2→基站2→终端设备传输,本申请实施例对此不作具体限定。
在S706中SM 1确定暂时无需更新终端设备的会话之后的预设时间段后,SM 1再次判断是否更新终端设备的会话。
S711、SM 1判断是否更新终端设备的会话。
在S711执行的过程中,终端设备可能会发送上行数据,相应的,SM 1会接收到该上行数据,并向用户面网元1发送其接收到的上行数据。随后,该SM 1会接收到用户面网元1发送的上行数据应答消息。
S712、若SM 1确定更新终端设备的会话,则SM 1保留第一会话的上下文,在接收到的上行数据应答消息中添加指示信息,并向MM 2发送携带有指示信息的上行数据应答消息。
本实施例(图7所示的实施例)中的指示信息用于指示MM 2在等待至获得待发送的终端设备的上行数据后,选择SM 2,以触发第二会话的建立。
S713、MM 2向基站2发送上行数据应答消息。
S714、基站2向终端设备发送上行数据应答消息。
S715、终端设备向基站2发送携带临时ID 2和MM 2的标识的上行数据报文。
S716、基站2向MM 2转发S715中的上行数据报文。
S717、MM 2在接收到上行数据报文后,根据其在S712接收到的上下数据应答消息携带的指示信息,利用终端设备的移动管理上下文对终端设备进行验证授权,并根据终端设备的签约数据以及上行数据报文的数据类型等信息为该终端设备选择SM 2。
S718、MM 2向SM2发送会话建立请求以及终端设备的永久标识。
S719、SM 2根据终端设备的永久标识,获取该终端设备的会话管理签约数据,并根据该终端设备的会话管理签约数据为终端设备选择用户面网元2。
S720、SM 2向用户面网元2发送用户面转发规则,并创建第二会话的上下文。
S721、SM 2向MM 2发送会话建立响应。
S722、MM 2向SM 2发送MM 2在S716中接收到的上行数据报文,SM 2向用户面网元2转发该上行数据报文。
MM 2接收到上述会话建立响应后,第二会话的建立过程结束。这样,终端设备的上行数据沿着终端设备→基站2→MM 2→SM 2→用户面网元2传输。相应的,待发送至终端设备的下行数据沿着用户面网元2→SM 2→MM 2→基站2→终端设备传输。
在第二会话建立结束后,MM 2还可向SM 1发送第一通知消息,用以指示SM 1释放第一会话的上下文,减少源核心网设备的资源浪费。
如图7所示,在S721之后,本申请实施例提供的会话迁移方法还包括S723和S724。
S723、MM 2向SM 1发送第一通知消息,以指示SM 1释放第一会话的上下文。
其中,第一通知消息的传输路径可以是MM 2→SM 1,也可以是MM 2→MM 1→SM 1,本申请实施例对此不作具体限定。
S724、SM 1释放第一会话的上下文。
其中,本申请实施例中的SM 1可以先执行S723,后执行S724,也可以先执行S724,后执行S723,还可以同时执行S723和S724,本申请实施例对此不作具体限定。
本实施例中的S700-S712与图5中的S500-S512类似,不同的是,本实施例中的指示信息用于指示MM 2在等待至获得待发送的终端设备的上行数据后,选择SM 2,以触发第二会话的建立。而图5所示的实施例中的指示信息用于指示终端设备在等待至获得待发送的终端设备的数据后,向MM 2发送会话建 立请求,以触发第二会话的建立。
S700-S705可参考图6中的S600-S605的描述,S715-S724可以参考图6中的S611-S620的描述,此处不再赘述。
由于图6或图7所示的实施例中的SM 1在第二会话建立之前,保留了第一会话的上下文,因此,即使有待发送至终端设备的下行数据,也能够准确的发送到终端设备,保证了下行数据无丢包。又由于第二会话是MM 2在等待至获得待发送的终端设备的上行数据后,触发建立的,因此,不会出现未传输数据却建立了第二会话的情况,降低了核心网资源的浪费,也减少了不必要的信令传输。
与图4或图5所示的实施例相比,在图6或图7所示的实施例中,终端设备未感知会话迁移这一流程,进一步减少了终端设备的信令传输。
从上述描述可知,图5所示的实施例中,SM 1通过判断在S506之后的预设时间段内接收到的上行数据的数据量是否大于或等于预设阈值,以确定是否更新终端设备的会话。相对应的,SM 1也可以通过判断在S506之后的预设时间段内接收到的下行数据的数据量是否大于或等于预设阈值,以确定是否更新终端设备的会话。
结合上述图5,本申请实施例在图8中示出了SM 1通过判断在S506之后的预设时间段内接收到的下行数据的数据量是否大于或等于预设阈值,以确定是否更新终端设备的会话这一应用场景的流程。
如图8所示,本申请实施例提供的会话迁移方法包括:
S800、终端设备与SM 1之间建立有第一会话。
S801、终端设备从第一TA移动到第二TA后,向基站2发送第一请求消息。
该第一请求消息携带第一TA的标识、DNN、MM 1的标识和终端设备的临时ID 1。
S802、基站2向MM 2转发S401中的第一请求消息。
S803、MM 2向MM 1发送第二请求消息,以请求获取终端设备的移动管理上下文。
S804、MM 1查找其存储的移动管理上下文列表,确定与临时ID 1对应的SM为SM 1,且与临时ID 1对应的终端设备的永久标识,并向SM 1发送第二通知消息,以通知SM 1将其存储的第一会话的上下文中的MM 1的标识更新为MM 2的标识。
该第二通知消息携带MM 2的标识和终端设备的永久标识。
S805、SM 1根据MM 2的标识,判断是否更新该终端设备的会话。
S806、若SM 1确定暂时无需更新终端设备的会话,SM 1保留第一会话的上下文,并向MM 1发送携带SM 1的标识的第一响应消息。
S807、MM 1向MM 2发送携带SM 1的标识、终端设备的移动管理上下文以及终端设备的永久标识的第三响应消息。
S808、MM 2存储SM 1的标识和终端设备的移动管理上下文,并为终端 设备分配临时ID 2。
S809、MM 2向基站2发送携带临时ID 2和MM 2的标识的第二响应消息。
S810、基站2向终端设备转发S809中的第二响应消息。
由于SM 1保留第一会话的上下文,因此,在第二会话未建立之前,即使用户面网元1接收到待发送至终端设备的下行数据,该下行数据也可传输到终端设备,保证了下行数据不丢包。
SM 1与MM 1连接,也可与MM 2连接,且SM 1已经获知终端设备已经移动至MM 2的服务区域,因此,对于用户面网元1接收到待发送至终端设备的下行数据而言,该下行数据可以沿着用户面网元1→SM 1→MM 2→基站2→终端设备传输,也可沿着用户面网元1→SM 1→MM1→MM 2→基站2→终端设备传输,本申请实施例对此不作具体限定。
在S806中SM 1确定暂时无需更新终端设备的会话之后的预设时间段后,SM 1再次判断是否更新终端设备的会话。
S811、SM 1判断是否更新终端设备的会话。
SM 1在上述S805中已经确定终端设备发生了移动,因此,S811中SM 1判断该SM 1在S806之后的预设时间段内接收到的下行数据的数据量是否大于或等于预设阈值。
若SM 1在S806之后的预设时间段内接收到的下行数据的数据量大于或等于预设阈值,则SM 1确定更新终端设备的会话。若SM 1在S806之后的预设时间段内接收到的下行数据的数据量小于预设阈值,则SM 1依旧确定暂时无需更新终端设备的会话。
在S811执行的过程中,SM 1可能会接收到待发送至终端设备的下行数据,该下行数据为用户面网元1发送到SM 1的数据。
S812、若SM 1确定更新终端设备的会话,则SM 1保留第一会话的上下文,在接收到的待发送至终端设备的下行数据中添加指示信息,并向MM 2发送携带有指示信息的下行数据。
本实施例(图8所示的实施例)中的指示信息用于指示终端设备在获取到该指示信息后,立刻向MM 2发送会话建立请求,以触发第二会话的建立。
容易理解的是,本实施例中的SM 1是在某一时间段内,其接收到待发送至终端设备的下行数据的数据量大于或等于预设阈值的前提下,确定更新终端设备的会话。在这种场景中,需要立刻建立第二会话,用以根据第二会话传输待发送至终端设备的下行数据。
MM 2在接收到携带有指示信息的下行数据后,向终端设备发送该携带有指示信息的下行数据。可选的,由于终端设备在移动到第二TA后,未发送上行数据,因此该终端设备可能处于空闲状态,也可能处于连接状态。若该终端设备处于空闲状态,则在S812之后,执行S813-S814,并在S814之后,执行S815;若该终端设备处于连接状态,则在S812之后,执行S814。由于S813-S814是可选的,图8中用虚线表示。
S813、MM 2向终端设备发送寻呼消息。
S814、终端设备向MM 2发送寻呼响应。
S815、MM 2向基站2发送其在S812接收到的携带有指示信息的下行数据。
S816、基站2向终端设备发送携带有指示信息的下行数据。
S817、终端设备向基站2发送下行数据应答消息,基站2向MM 2转发该下行数据应答消息,MM 2向SM 1转发该下行数据应答消息,SM 1向用户面网元1转发该下行数据应答消息。
这里,S817为可选步骤,图8中用虚线表示。
S818、终端设备根据其在S816接收到的下行数据中携带的指示信息,向基站2发送携带DNN和会话类型信息的会话建立请求。
S819、基站2向MM 2转发S818中的会话建立请求。
S820、MM 2根据终端设备的移动管理上下文对终端设备进行验证授权,并根据S819中的会话建立请求是携带的DNN和会话类型信息以及MM 2本地存储的终端设备的签约数据,为该终端设备选择SM 2。
S821、MM 2向SM 2发送会话建立请求以及终端设备的永久标识。
S822、SM 2根据终端设备的永久标识,获取该终端设备的会话管理签约数据,并根据该终端设备的会话管理签约数据为终端设备选择用户面网元2。
S823、SM 2向用户面网元2发送用户面转发规则,并创建第二会话的上下文。
S824、SM 2向MM 2发送会话建立响应,MM 2向基站2发送会话建立响应,基站2向终端设备发送会话建立响应。
在第二会话建立结束后,MM 2还可向SM 1发送第一通知消息,用以指示SM 1释放第一会话的上下文,减少源核心网设备的资源浪费。
如图8所示,在S824之后,本申请实施例提供的会话迁移方法还包括S825和S826。
S825、MM 2向SM 1发送第一通知消息,以指示SM 1释放第一会话的上下文。
S826、SM 1释放第一会话的上下文。
S800-S810可参考图5中的S500-S510的描述,S819-S826可以参考图5中的S516-S523的描述,此处不再赘述。
进一步地,由于本实施例中的会话迁移过程是由下行数据引发的,因此,在本实施例中的S824之后,终端设备还向MM 2发送第二上行注册报文,MM 2在接收到该第二上行注册报文后,通过SM2向用户面网元2发送该第二上行注册报文,用户面网元2在接收到该第二上行注册报文后,向应用服务器转发该第二上行注册报文,便于应用服务器更新其存储的待发送至终端设备的下行数据的转发路径。图8中未示出这一过程。
从上述描述可知,在图8所示的实施例适用的应用场景中,指示信息用于指示终端设备在获取到该指示信息后,立刻向MM 2发送会话建立请求,以触发第二会话的建立。此外,本申请实施例提供的会话迁移方法,在图8所示的 实施例适用的应用场景中,指示信息也可以用于指示终端设备在获取到该指示信息后,立刻向MM 2发送第一上行注册报文,以触发第二会话的建立。图9示出了这种情况的流程。
如图9所示,本申请实施例提供的会话迁移方法包括:
S900、终端设备与SM 1之间建立有第一会话。
S901、终端设备从第一TA移动到第二TA后,向基站2发送第一请求消息。
其中,第一请求消息携带第一TA的标识、DNN、MM 1的标识和临时ID 1。
S902、基站2向MM 2转发S601中的第一请求消息。
S903、MM 2向MM 1发送携带MM 2的标识和临时ID 1的第二请求消息,以请求获取终端设备的移动管理上下文。
S904、MM 1查找其存储的移动管理上下文列表,确定与临时ID 1对应的SM为SM 1,并确定与临时ID 1对应的终端设备的永久标识,并向SM 1发送携带MM 2的标识和终端设备的永久标识的第二通知消息,以通知SM 1将其存储的第一会话的上下文中的MM 1的标识更新为MM 2的标识。
S905、SM 1根据MM2的标识,判断是否更新该终端设备的会话。
S906、若SM 1确定暂时无需更新终端设备的会话,SM 1保留第一会话的上下文,并向MM 1发送携带SM 1的标识SM 1的第一响应消息。
S907、MM 1向MM 2发送携带SM 1的标识、终端设备的移动管理上下文以及终端设备的永久标识的第三响应消息。
S908、MM 2存储SM 1的标识和终端设备的移动管理上下文,并为终端设备分配临时ID 2。
S909、MM 2向基站2发送携带临时ID 2和MM 2的标识的第二响应消息。
S910、基站2向终端设备转发S910中的第二响应消息。
由于SM 1保留第一会话的上下文,因此,在第二会话未建立之前,即使用户面网元1接收到待发送至终端设备的下行数据,该下行数据也可传输到终端设备,保证了下行数据不丢包。
SM 1与MM 1连接,也可与MM 2连接,且SM 1已经获知终端设备已经移动至MM 2的服务区域,因此,对于用户面网元1接收到待发送至终端设备的下行数据而言,该下行数据可以沿着用户面网元1→SM 1→MM 2→基站2→终端设备传输,也可沿着用户面网元1→SM 1→MM1→MM 2→基站2→终端设备传输,本申请实施例对此不作具体限定。
在S906中SM 1确定暂时无需更新终端设备的会话之后的预设时间段后,SM 1再次判断是否更新终端设备的会话。
S911、SM 1判断是否更新终端设备的会话。
SM 1在上述S905中已经确定终端设备发生了移动,因此,S911中SM 1判断该SM 1在S906之后的预设时间段内接收到的下行数据的数据量是否大于或等于预设阈值。
若SM 1在S906之后的预设时间段内接收到的下行数据的数据量大于或等于预设阈值,则SM 1确定更新终端设备的会话。若SM 1在S906之后的预设时间段内接收到的下行数据的数据量小于预设阈值,则SM 1依旧确定暂时无需更新终端设备的会话。
在S911执行的过程中,SM 1可能会接收到待发送至终端设备的下行数据,该下行数据为用户面网元1发送到SM 1的数据。
S912、若SM 1确定更新终端设备的会话,则SM 1保留第一会话的上下文,在接收到的待发送至终端设备的下行数据中添加指示信息,并向MM 2发送携带有指示信息的下行数据。
本实施例(图9所示的实施例)中的指示信息用于指示终端设备在在获取到该指示信息后,立刻向MM 2发送第一上行注册报文,以触发第二会话的建立。
MM 2在接收到携带有指示信息的下行数据后,向终端设备发送该携带有指示信息的下行数据。可选的,由于终端设备在移动到第二TA后,未发送上行数据,因此该终端设备可能处于空闲状态,也可能处于连接状态。例如,若该终端设备处于空闲状态,则在S912之后,执行S913-S914;若该终端设备处于连接状态,则在S912之后,执行S914。由于S913-S914是可选的,图9中用虚线表示。
S913、MM 2向终端设备发送寻呼消息。
S914、终端设备向MM 2发送寻呼响应。
S915、MM 2向基站2发送携带有指示信息的下行数据。
S916、基站2向终端设备发送携带有指示信息的下行数据。
S917、终端设备向基站2发送下行数据应答消息,基站2向MM 2转发该下行数据应答消息,MM 2向SM 1转发该下行数据应答消息,SM 1向用户面网元1转发该下行数据应答消息。
这里,S917为可选步骤,图9中用虚线表示。
S918、终端设备向基站2发送携带临时ID 2和MM 2的标识的第一上行注册报文。
S919、基站2向MM 2发送S918中的第一上行注册报文。
S920、MM 2在接收到第一上行注册报文后,根据终端设备的移动管理上下文对终端设备进行验证授权,并根据终端设备的签约数据以及第一上行注册报文的数据类型等信息为终端设备选择SM 2。
S921、MM 2向SM2发送会话建立请求以及终端设备的永久标识。
S922、SM 2根据终端设备的永久标识,获取该终端设备的会话管理签约数据,并根据该终端设备的会话管理签约数据为终端设备选择用户面网元2。
S923、SM 2向用户面网元2发送用户面转发规则,并创建第二会话的上下文。
S924、SM 2向MM 2发送会话建立响应,MM 2向基站2发送会话建立响应,基站2向终端设备发送会话建立响应。
S925、MM 2向SM 2发送MM 2在S919中接收到的第一上行注册报文,SM 2向用户面网元2转发该第一上行注册报文。
在第二会话建立结束后,MM 2还可向SM 1发送第一通知消息,用以指示SM 1释放第一会话的上下文,减少源核心网设备的资源浪费。
如图9所示,在S924之后,本申请实施例提供的会话迁移方法还包括S926和S927。
S926、MM 2向SM 1发送第一通知消息,以指示SM 1释放第一会话的上下文。
S927、SM 1释放第一会话的上下文。
S900-S917可参考图8中的S800-S817的描述,S921-S924可以参考图8中的S821-S824的描述,S926-S927可以参考图8中的S825-S826的描述,此处不再赘述。本实施例适用的应用场景与图8所示的实施例适用的应用场景相同,不同的是,本实施例中的指示信息所指示的内容与图8所示实施例中的指示信息所指示的内容不同。
上述图4-图9中,任一附图所示的实施例中的SM 1在第二会话建立之前,均保留了第一会话的上下文。因此,即使有待发送至终端设备的下行数据,也能够准确的发送到终端设备,保证了下行数据无丢包。又由于第二会话均是在等待至获得待发送的终端设备的数据之后建立的,因此,不会出现未传输数据却建立了第二会话的情况,均能降低核心网资源的浪费,减少不必要的信令传输。
除此之外,在图6或图7所示的实施例中,终端设备未感知会话迁移这一流程,进一步减少了终端设备的信令传输。
从上面描述可知,移动管理功能实体和会话管理功能实体可以独立设置,也可以集成在同一设备。上述图4-图9所示的实施例均是以移动管理功能实体和会话管理功能实体独立设置为例进行说明的,现以移动管理功能实体和会话管理功能实体集成在同一设备为例,说明本申请实施例提供的会话迁移方法。
为了便于描述,本申请实施例将源无线接入网设备用基站1表示,将源控制面网元用控制面网元1表示,将源用户面网元用用户面网元1表示,将目标无线接入网设备用基站2表示,将目标控制面网元用控制面网元2表示,将目标用户面网元用用户面网元2表示。
例如,在移动管理功能实体和会话管理功能实体集成在同一设备的场景中,图10示出了与图4所示的实施例对应的会话迁移方法。
参见图10,该会话迁移方法包括:
S1000、终端设备与控制面网元1之间建立有第一会话。
控制面网元1的服务区域包括第一TA,控制面网元1存储有第一会话的上下文。
S1001、终端设备从第一TA移动到第二TA后,向基站2发送第一请求消息。
该第一请求消息携带第一TA的标识、DNN、控制面网元1的标识和终端 设备的临时ID 1。
S1002、基站2向控制面网元2转发S1001中的第一请求消息。
S1003、控制面网元2向控制面网元1发送第二请求消息,以请求获取终端设备的上下文。
该第二请求消息携带控制面网元2的标识和临时ID 1。这里,终端设备的上下文包括终端设备的移动管理上下文和终端设备的会话管理上下文。
S1004、控制面网元1根据控制面网元2的标识,判断是否更新该终端设备的会话。
S1005、若控制面网元1确定更新终端设备的会话,控制面网元1保留第一会话的上下文,并向控制面网元2发送携带指示信息、控制面网元1的标识、终端设备的上下文(包括移动管理上下文和会话管理上下文)以及终端设备的永久标识的第三响应消息。
S1006、控制面网元2存储控制面网元1的标识和终端设备的移动管理上下文,并为终端设备分配临时ID 2。
S1007、控制面网元2向基站2发送携带指示信息、临时ID 2和控制面网元2的标识的第二响应消息。
S1008、基站2向终端设备转发S1007中的第二响应消息。
S1009、终端设备根据S1008中第二响应消息中携带的指示信息,在等待至获得待发送的终端设备的数据后,向基站2发送携带DNN和会话类型信息的会话建立请求。
S1010、基站2向控制面网元2转发S1009中的会话建立请求。
S1011、控制面网元2根据终端设备的移动管理上下文对终端设备进行验证授权,并根据S1010中的会话建立请求所携带的DNN和会话类型信息以及控制面网元2本地存储的终端设备的签约数据为终端设备选择用户面网元2。
S1012、控制面网元2向用户面网元2发送用户面转发规则,并创建第二会话的上下文。
S1013、控制面网元2向基站2发送会话建立响应,基站2向终端设备发送会话建立响应。
终端设备在接收到会话建立响应后,第二会话的建立过程结束。
在第二会话建立结束后,本申请实施例提供的会话迁移方法还包括S1014和S1015。
S1014、控制面网元2向控制面网元1发送第一通知消息,以指示控制面网元1释放第一会话的上下文。
S1015、控制面网元1释放第一会话的上下文。
图10所示的流程可以参考图4所示的流程,此处不再进行详细赘述。
在移动管理功能实体和会话管理功能实体集成在同一设备的场景中,图11示出了与图5所示的实施例对应的会话迁移方法。
参见图11,该会话迁移方法包括:
S1100、终端设备与控制面网元1之间建立有第一会话。
控制面网元1的服务区域包括第一TA,控制面网元1存储有第一会话的上下文。
S1101、终端设备从第一TA移动到第二TA后,向基站2发送第一请求消息。
该第一请求消息携带第一TA的标识、DNN、控制面网元1的标识和终端设备的临时ID 1。
S1102、基站2向控制面网元2转发S1101中的第一请求消息。
S1103、控制面网元2向控制面网元1发送第二请求消息,以请求获取终端设备的上下文。
该第二请求消息携带控制面网元2的标识和临时ID 1,终端设备的上下文包括移动管理上下文和会话管理上下文。
S1104、控制面网元1根据控制面网元2的标识,判断是否更新该终端设备的会话。
S1105、若控制面网元1确定暂时无需更新终端设备的会话,控制面网元1保留第一会话的上下文,并向控制面网元2发送携带控制面网元1的标识、终端设备的上下文(包括移动管理上下文和会话管理上下文)以及终端设备的永久标识的第三响应消息。
S1106、控制面网元2存储控制面网元1的标识和终端设备的上下文,并为终端设备分配临时ID 2。
S1107、控制面网元2向基站2发送携带临时ID 2和控制面网元2的标识的第二响应消息。
S1108、基站2向终端设备转发S1107中的第二响应消息。
在S1105中控制面网元1确定暂时无需更新终端设备的会话之后的预设时间段后,控制面网元1再次判断是否更新终端设备的会话。
S1109、控制面网元1判断是否更新终端设备的会话。
控制面网元1在上述S1104中已经确定终端设备发生了移动,因此,S1109中控制面网元1判断该控制面网元1在S1105之后的预设时间段内接收到的上行数据的数据量是否大于或等于预设阈值。
若控制面网元1在S1105之后的预设时间段内接收到的上行数据的数据量大于或等于预设阈值,则控制面网元1确定更新终端设备的会话。若控制面网元1在S1105之后的预设时间段内接收到的上行数据的数据量小于预设阈值,则控制面网元1依旧确定暂时无需更新终端设备的会话。
在S1109执行的过程中,终端设备可能会发送上行数据,相应的,控制面网元1会接收到该上行数据,并向用户面网元1发送其接收到的上行数据。随后,该控制面网元1会接收到用户面网元1发送的上行数据应答消息。
S1110、若控制面网元1确定更新终端设备的会话,则控制面网元1保留第一会话的上下文,在接收到的上行数据应答消息中添加指示信息,并向控制面网元2发送携带有指示信息的上行数据应答消息。
S1111、控制面网元2向基站2转发携带有指示信息的上行数据应答消息。
S1112、基站2向终端设备转发携带有指示信息的上行数据应答消息。
S1113、终端设备根据S1112中上行数据应答消息携带的指示信息,在等待至获得待发送的终端设备的数据后,向基站2发送携带DNN和会话类型信息的会话建立请求。
S1114、基站2向控制面网元2转发S1113中的会话建立请求。
S1115、控制面网元2根据终端设备的移动管理上下文对终端设备进行验证授权,并根据S1113中的会话建立请求所携带的DNN和会话类型信息以及控制面网元2本地存储的终端设备的签约数据为终端设备选择用户面网元2。
S1116、控制面网元2向用户面网元2发送用户面转发规则,并创建第二会话的上下文。
S1117、控制面网元2向基站2发送会话建立响应,基站2向终端设备发送会话建立响应。
终端设备在接收到会话建立响应后,第二会话的建立过程结束。
在第二会话建立结束后,本申请实施例提供的会话迁移方法还包括S1118和S1119。
S1118、控制面网元2向控制面网元1发送第一通知消息,以指示控制面网元1释放第一会话的上下文。
S1119、控制面网元1释放第一会话的上下文。
图11所示的流程可以参考图5所示的流程,此处不再进行详细赘述。
在移动管理功能实体和会话管理功能实体集成在同一设备的场景中,图12示出了与图6所示的实施例对应的会话迁移方法。
参见图12,该会话迁移方法包括:
S1200、终端设备与控制面网元1之间建立有第一会话。
控制面网元1的服务区域包括第一TA,控制面网元1存储有第一会话的上下文。
S1201、终端设备从第一TA移动到第二TA后,向基站2发送第一请求消息。
该第一请求消息携带第一TA的标识、DNN、控制面网元1的标识和终端设备的临时ID 1。
S1202、基站2向控制面网元2转发S1201中的第一请求消息。
S1203、控制面网元2向控制面网元1发送第二请求消息,以请求获取终端设备的上下文。
该第二请求消息携带控制面网元2的标识和临时ID 1,终端设备的上下文包括移动管理上下文和会话管理上下文。
S1204、控制面网元1根据控制面网元2的标识,判断是否更新该终端设备的会话。
S1205、若控制面网元1确定更新终端设备的会话,控制面网元1保留第一会话的上下文,并向控制面网元2发送携带指示信息、控制面网元1的标识、终端设备的上下文(包括移动管理上下文和会话管理上下文)以及终端设备的 永久标识的第三响应消息。
S1206、控制面网元2存储控制面网元1的标识和终端设备的上下文,并为终端设备分配临时ID 2。
S1207、控制面网元2向基站2发送携带临时ID 2和控制面网元2的标识的第二响应消息。
S1208、基站2向终端设备转发S1207中的第二响应消息。
S1209、终端设备向基站2发送携带临时ID 2和控制面网元2的标识的上行数据报文。
S1210、基站2向控制面网元2转发S1209中的上行数据报文。
S1211、控制面网元2根据指示信息,利用根据终端设备的移动管理上下文对终端设备进行验证授权,并根据终端设备的签约数据以及上行数据报文的数据类型等信息为终端设备选择用户面网元2。
S1212、控制面网元2向用户面网元2发送用户面转发规则,并创建第二会话的上下文。
S1213、用户面网元2向控制面网元2发送会话建立响应。
控制面网元2在接收到会话建立响应后,第二会话的建立过程结束。
S1214、控制面网元2向用户面网元2转发其在S1210中接收到的上行数据报文。
在第二会话建立结束后,本申请实施例提供的会话迁移方法还包括S1215和S1216。
S1215、控制面网元2向控制面网元1发送第一通知消息,以指示控制面网元1释放第一会话的上下文。
S1216、控制面网元1释放第一会话的上下文。
其中,本申请实施例中的控制面网元2可以先执行S1214,后执行S1215,也可以先执行S1215,后执行S1214,还可以同时执行S1214和S1215,本申请实施例对此不作具体限定。
图12所示的流程可以参考图6所示的流程,此处不再进行详细赘述。
在移动管理功能实体和会话管理功能实体集成在同一设备的场景中,图13示出了与图7所示的实施例对应的会话迁移方法。
参见图13,该会话迁移方法包括:
S1300、终端设备与控制面网元1之间建立有第一会话。
控制面网元1的服务区域包括第一TA,控制面网元1存储有第一会话的上下文。
S1301、终端设备从第一TA移动到第二TA后,向基站2发送第一请求消息。
该第一请求消息携带第一TA的标识、DNN、控制面网元1的标识和终端设备的临时ID 1。
S1302、基站2向控制面网元2转发S1301中的第一请求消息。
S1303、控制面网元2向控制面网元1发送第二请求消息,以请求获取终 端设备的上下文。
该第二请求携带控制面网元2的标识和临时ID 1,终端设备的上下文包括移动管理上下文和会话管理上下文。
S1304、控制面网元1根据控制面网元2的标识,判断是否更新该终端设备的会话。
S1305、若控制面网元1确定暂时无需更新终端设备的会话,控制面网元1保留第一会话的上下文,并向控制面网元2发送携带控制面网元1的标识、终端设备的上下文(包括移动管理上下文和会话管理上下文)以及终端设备的永久标识的第三响应消息。
S1306、控制面网元2存储控制面网元1的标识和终端设备的上下文,并为终端设备分配临时ID 2。
S1307、控制面网元2向基站2发送携带临时ID 2和控制面网元2的标识的第二响应消息。
S1308、基站2向终端设备转发S1307中的第二响应消息。
在S1305中控制面网元1确定暂时无需更新终端设备的会话之后的预设时间段后,控制面网元1再次判断是否更新终端设备的会话。
S1309、控制面网元1判断是否更新终端设备的会话。
在S1309执行的过程中,终端设备可能会发送上行数据,相应的,控制面网元1会接收到该上行数据,并向用户面网元1发送其接收到的上行数据。随后,该控制面网元1会接收到用户面网元1发送的上行数据应答消息。
S1310、若控制面网元1确定更新终端设备的会话,则控制面网元1保留第一会话的上下文,在接收到的上行数据应答消息中添加指示信息,并向控制面网元2发送携带有指示信息的上行数据应答消息。
S1311、控制面网元2向基站2发送上行数据应答消息。
S1312、基站2向终端设备转发S1311中的上行数据应答消息。
S1313、终端设备向基站2发送携带临时ID 2和控制面网元2的标识的上行数据报文。
S1314、基站2向控制面网元2转发S1313中的上行数据报文。
S1315、控制面网元2根据其在S1310接收到的上行数据应答消息中携带的指示信息,利用终端设备的移动管理上下文对终端设备进行验证授权,并根据终端设备的签约数据以及上行数据报文的数据类型等信息为终端设备选择用户面网元2。
S1316、控制面网元2向用户面网元2发送用户面转发规则,并创建第二会话的上下文。
S1317、用户面网元2向控制面网元2发送会话建立响应。
S1318、控制面网元2向用户面网元2发送其在S1314中接收到的上行数据报文。
控制面网元2在接收到会话建立响应后,第二会话的建立过程结束。
在第二会话建立结束后,本申请实施例提供的会话迁移方法还包括S1319 和S1320。
S1319、控制面网元2向控制面网元1发送第一通知消息,以指示控制面网元1释放第一会话的上下文。
S1320、控制面网元1释放第一会话的上下文。
其中,本申请实施例中的控制面网元2可以先执行S1318,后执行S1319,也可以先执行S1319,后执行S1318,还可以同时执行S1318和S1319,本申请实施例对此不作具体限定。
图13所示的流程可以参考图7所示的流程,此处不再进行详细赘述。
在移动管理功能实体和会话管理功能实体集成在同一设备的场景中,图14示出了与图8所示的实施例对应的会话迁移方法。
参见图14,该会话迁移方法包括:
S1400、终端设备与控制面网元1之间建立有第一会话。
控制面网元1的服务区域包括第一TA,控制面网元1存储有第一会话的上下文。
S1401、终端设备从第一TA移动到第二TA后,向基站2发送第一请求消息。
该第一请求消息携带第一TA的标识、DNN、控制面网元1的标识和终端设备的临时ID 1。
S1402、基站2向控制面网元2转发S1401中的第一请求消息。
S1403、控制面网元2向控制面网元1发送第二请求消息,以请求获取终端设备的上下文。
该第二请求消息携带控制面网元2的标识和临时ID 1,终端设备的上下文包括移动管理上下文和会话管理上下文。
S1404、控制面网元1根据控制面网元2的标识,判断是否更新该终端设备的会话。
S1405、若控制面网元1确定暂时无需更新终端设备的会话,控制面网元1保留第一会话的上下文,并向控制面网元2发送携带控制面网元1的标识、终端设备的上下文(包括移动管理上下文和会话管理上下文)以及终端设备的永久标识的第三响应消息。
S1406、控制面网元2存储控制面网元1的标识和终端设备的上下文,并为终端设备分配临时ID 2。
S1407、控制面网元2向基站2发送携带临时ID 2和控制面网元2的标识的第二响应消息。
S1408、基站2向终端设备转发S1407中的第二响应消息。
在S1405中控制面网元1确定暂时无需更新终端设备的会话之后的预设时间段后,控制面网元1再次判断是否更新终端设备的会话。
S1409、控制面网元1判断是否更新终端设备的会话。
在S1409执行的过程中,控制面网元1可能会接收到待发送至终端设备的下行数据,该下行数据为用户面网元1发送到控制面网元1的数据。
S1410、若控制面网元1确定更新终端设备的会话,则控制面网元1保留第一会话的上下文,在接收到的下行数据中添加指示信息,并向控制面网元2发送携带有指示信息的下行数据。
控制面网元2在接收到携带有指示信息的下行数据后,向终端设备发送该携带有指示信息的下行数据。可选的,由于终端设备在移动到第二TA后,未发送上行数据,因此该终端设备可能处于空闲状态,也可能处于连接状态。例如,若该终端设备处于空闲状态,则在S1410之后,执行S1411-S1412,并在S1412之后,执行S1413;若该终端设备处于连接状态,则在S1410之后,执行S1413。由于S1411-S1412是可选的,图14中用虚线表示。
S1411、控制面网元2向终端设备发送寻呼消息。
S1412、终端设备向控制面网元2发送寻呼响应。
S1413、控制面网元2向基站2发送携带有指示信息的下行数据,基站2向终端设备转发携带有指示信息的下行数据。
S1414、终端设备向基站2发送下行数据应答消息,基站2向控制面网元2转发该下行数据应答消息,控制面网元2向控制面网元1转发该下行数据应答消息,控制面网元1向用户面网元1转发该下行数据应答消息。
这里,S1414为可选步骤,图14中用虚线表示。
S1415、终端设备根据其在S1413中接收到的下行数据携带的指示信息,向基站2发送携带DNN和会话类型信息的会话建立请求。
S1416、基站2向控制面网元2转发S1415中的会话建立请求。
S1417、控制面网元2根据终端设备的移动管理上下文对终端设备进行验证授权,并根据终端设备的永久标识,获取终端设备的会话管理签约数据,并根据S1416中的会话建立请求是携带的DNN和会话类型信息以及控制面网元2本地存储的终端设备的签约数据,为终端设备选择用户面网元2。
S1418、控制面网元2向用户面网元2发送用户面转发规则,并创建第二会话的上下文。
S1419、控制面网元2向基站2发送会话建立响应,基站2向终端设备发送会话建立响应。
终端设备在接收到会话建立响应后,第二会话的建立过程结束。
例如,在第二会话建立结束后,本申请实施例提供的会话迁移方法还包括S1420和S1421。
S1420、控制面网元2向控制面网元1发送第一通知消息,以指示控制面网元1释放第一会话的上下文。
S1421、控制面网元1释放第一会话的上下文。
进一步地,由于本实施例中的会话迁移过程是由下行数据引发的,因此,在本实施例中的S1419之后,终端设备还向控制面网元2发送第二上行注册报文,控制面网元2在接收到该第二上行注册报文后转发至用户面网元2,用户面网元2向应用服务器转发该第二上行注册报文,便于应用服务器更新其存储的待发送至终端设备的下行数据的转发路径。图14中未示出这一过程。
图14所示的流程可以参考图8所示的流程,此处不再进行详细赘述。
在移动管理功能实体和会话管理功能实体集成在同一设备的场景中,图15示出了与图9所示的实施例对应的会话迁移方法。
参见图15,该会话迁移方法包括:
S1500、终端设备与控制面网元1之间建立有第一会话。
控制面网元1的服务区域包括第一TA,控制面网元1存储有第一会话的上下文。
S1501、终端设备从第一TA移动到第二TA后,向基站2发送第一请求消息。
该第一请求消息携带第一TA的标识、DNN、控制面网元1的标识和终端设备的临时ID 1。
S1502、基站2向控制面网元2转发S1501中的第一请求消息。
S1503、控制面网元2向控制面网元1发送第二请求消息,以请求获取终端设备的上下文。
该第二请求消息携带控制面网元2的标识和临时ID 1,终端设备的上下文包括移动管理上下文和会话管理上下文。
S1504、控制面网元1根据控制面网元2的标识,判断是否更新该终端设备的会话。
S1505、若控制面网元1确定暂时无需更新终端设备的会话,控制面网元1保留第一会话的上下文,并向控制面网元2发送携带控制面网元1的标识、终端设备的上下文(包括移动管理上下文和会话管理上下文)以及终端设备的永久标识的第三响应消息。
S1506、控制面网元2存储控制面网元1的标识和终端设备的上下文,并为终端设备分配临时ID 2。
S1507、控制面网元2向基站2发送携带临时ID 2和控制面网元2的标识的第二响应消息。
S1508、基站2向终端设备转发S1507中的第二响应消息。
在S1505中控制面网元1确定暂时无需更新终端设备的会话之后的预设时间段后,控制面网元1再次判断是否更新终端设备的会话。
S1509、控制面网元1判断是否更新终端设备的会话。
在S1509执行的过程中,控制面网元1可能会继续接收到待发送至终端设备的下行数据,该下行数据为用户面网元1发送到控制面网元1的数据。
S1510、若控制面网元1确定更新终端设备的会话,则控制面网元1保留第一会话的上下文,在接收到的下行数据中添加指示信息,并向控制面网元2发送携带有指示信息的下行数据。
控制面网元2在接收到携带有指示信息的下行数据后,向终端设备发送该携带有指示信息的下行数据。可选的,由于终端设备在移动到第二TA后,未发送上行数据,因此该终端设备可能处于空闲状态,也可能处于连接状态。例如,若该终端设备处于空闲状态,则在S1510之后,执行S1511-S1512,并在 S1512之后,执行S1513;若该终端设备处于连接状态,则在S1510之后,执行S1513。由于S1511-S1512是可选的,图14中用虚线表示。
S1511、控制面网元2向终端设备发送寻呼消息。
S1512、终端设备向控制面网元2发送寻呼响应。
S1513、控制面网元2向基站2发送携带有指示信息的下行数据,基站2向终端设备转发携带有指示信息的下行数据。
S1514、终端设备向基站2发送下行数据应答消息,基站2向控制面网元2转发该下行数据应答消息,控制面网元2向控制面网元1转发该下行数据应答消息,控制面网元1向用户面网元1转发该下行数据应答消息。
这里,S1514为可选步骤,图15中用虚线表示。
S1515、终端设备根据其在S1513中接收到的下行数据携带的指示信息,向基站2发送携带临时ID 2和控制面网元2的标识的第一上行注册报文。
S1516、基站2向控制面网元2发送S1515中的第一上行注册报文。
S1517、控制面网元2在接收到第一上行注册报文之后,根据终端设备的移动管理上下文对终端设备进行验证授权,并根据终端设备的签约数据以及第一上行注册报文的数据类型等信息为终端设备选择用户面网元2。
S1518、控制面网元2向用户面网元2发送用户面转发规则,并创建第二会话的上下文。
S1519、用户面网元2向控制面网元2发送会话建立响应。
控制面网元2在接收到会话建立响应后,第二会话的建立过程结束。
S1520、控制面网元2向用户面网元2发送控制面网元2在S1517中接收到的第一上行注册报文。
在第二会话建立结束后,本申请实施例提供的会话迁移方法还包括S1521和S1522。
S1521、控制面网元2向控制面网元1发送第一通知消息,以指示控制面网元1释放第一会话的上下文。
S1522、控制面网元1释放第一会话的上下文。
图15所示的流程可以参考图9所示的流程,此处不再进行详细赘述。
综上所述,上述图10-图15中,任一附图所示的实施例中的控制面网元1在第二会话建立之前,均保留了第一会话的上下文。因此,即使有待发送至终端设备的下行数据,也能够准确的发送到终端设备,保证了下行数据无丢包。又由于第二会话均是在等待至获得待发送的终端设备的数据之后建立的,因此,不会出现未传输数据却建立了第二会话的情况,均能降低核心网资源的浪费,减少不必要的信令传输。
除此之外,在图12或图13所示的实施例中,终端设备未感知会话迁移这一流程,进一步减少了终端设备的信令传输。
本申请实施例提供一种会话管理功能实体,该会话管理功能实体用于执行以上会话迁移方法中的源会话管理功能实体所执行的步骤。本申请实施例提供的会话管理功能实体可以包括相应步骤所对应的模块。
本申请实施例可以根据上述方法示例对会话管理功能实体进行功能模块的划分,例如,可以对应各个功能划分各个功能模块,也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。本申请实施例中对模块的划分是示意性的,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式。
在采用对应各个功能划分各个功能模块的情况下,图16示出了上述实施例中所涉及的会话管理功能实体的一种可能的结构示意图。如图16所示,会话管理功能实体1600包括处理单元160、发送单元161和接收单元162。处理单元160用于支持该会话管理功能实体1600执行上述实施例中的S301、S302、S405、S406、S419、S505、S506、S511、S523、S605、S606、S620、S705、S706、S711、S724、S805、S806、S811、S812、S826、S911、S912、S927等,和/或用于本文所描述的技术的其它过程;发送单元161用于支持该会话管理功能实体1600执行上述实施例中的S302a、S302b、S406、S506、S606、S706、S712、S806、S812、S906、S912等,和/或用于本文所描述的技术的其它过程;接收单元162用于支持该会话管理功能实体1600执行上述实施例中的S304、S404、S418、S504、S522、S604、S619、S704、S723、S804、S825、S904、S926等,和/或用于本文所描述的技术的其它过程。其中,上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述,在此不再赘述。当然,本申请实施例提供的会话管理功能实体1600包括但不限于上述模块,例如会话管理功能实体1600还可以包括存储单元163。存储单元163可以用于存储第一会话的上下文,也可以用于存储该会话管理功能实体的程序代码和数据。
在采用集成的单元的情况下,本申请实施例中的处理单元160可以是处理器或控制器,例如可以是中央处理器(Central Processing Unit,CPU),数字信号处理器(Digital Signal Processor,DSP)。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框,模块和电路。处理单元160也可以是实现计算功能的组合,例如包含一个或多个微处理器组合,DSP和微处理器的组合等。发送单元161和接收单元162可以集成在一个通信单元中实现,该通信单元可以是通信接口。存储单元163可以是存储器。
当上述处理单元为处理器,存储单元为存储器,通信单元为通信接口时,本申请实施例所涉及的会话管理功能实体1600可以为图17所示的会话管理功能实体1700。如图17所示,会话管理功能实体1700包括:处理器171、存储器172和通信接口173。其中,处理器171、存储器172和通信接口173通过总线174相互连接。
其中,总线174可以是工业标准体系结构(Industry Standard Architecture,ISA)总线、外部设备互连(Peripheral Component Interconnect,PCI)总线或扩展工业标准体系结构(Extended Industry Standard Architecture,EISA)总线等等。上述总线174可以分为地址总线、数据总线、控制总线等。为便于表示,图17中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。
示例性的,会话管理功能实体1700可以包括一个或多个处理器171,即会话管理功能实体1700可以包括多核处理器。
当会话管理功能实体1700运行时,该会话管理功能实体1700执行如图3-图9中任一附图所示的实施例的会话迁移方法。具体的会话迁移方法可参见上述如图3-图9中任一附图所示的实施例中的相关描述,此处不再赘述。
本申请另一实施例还提供一种计算机可读存储介质,该计算机可读存储介质包括一个或多个程序代码,该一个或多个程序包括指令,当会话管理功能实体1700中的处理器171在执行该程序代码时,该会话管理功能实体1700执行如图3-图9中任一附图所示的会话迁移方法。
在本申请的另一实施例中,还提供一种计算机程序产品,该计算机程序产品包括计算机执行指令,该计算机执行指令存储在计算机可读存储介质中;会话管理功能实体的至少一个处理器可以从计算机可读存储介质读取该计算机执行指令,至少一个处理器执行该计算机执行指令使得会话管理功能实体实施执行图3-图9中任一附图所示的会话迁移方法中的SM 2的步骤。
本申请实施例提供一种终端设备,该终端设备用于执行以上会话迁移方法中的终端设备所执行的步骤。本申请实施例提供的终端设备可以包括相应步骤所对应的模块。
本申请实施例可以根据上述方法示例对终端设备进行功能模块的划分,例如,可以对应各个功能划分各个功能模块,也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。本申请实施例中对模块的划分是示意性的,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式。
在采用对应各个功能划分各个功能模块的情况下,图18示出了上述实施例中所涉及的终端设备的一种可能的结构示意图。如图18所示,终端设备1800包括处理单元180、获取单元181和发送单元182。处理单元180用于支持该终端设备1800执行上述实施例中的S300、S400、S500、S600、S700、S800、S900等,和/或用于本文所描述的技术的其它过程;获取单元181用于支持该终端设备1600执行上述实施例中的S410、S510、S610、S710、S714、S810、S813、S816、S824、S910、S913、S916等,和/或用于本文所描述的技术的其它过程;发送单元182用于支持该终端设备1600执行上述实施例中的S401、S411、S501、S515、S601、S611、S701、S715、S801、S814、S818、S901、S914、S818等,和/或用于本文所描述的技术的其它过程。其中,上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述,在此不再赘述。当然,本申请实施例提供的终端设备1800包括但不限于上述模块,例如终端设备1800还可以包括存储单元183。存储单元183可以用于存储该终端设备的程序代码和数据。
在采用集成的单元的情况下,本申请实施例中的处理单元180可以是处理器或控制器,例如可以是CPU,DSP。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框,模块和电路。处理单元180也可以是实现计 算功能的组合,例如包含一个或多个微处理器组合,DSP和微处理器的组合等。获取单元181和发送单元182可以集成在一个通信单元中实现,该通信单元可以是通信接口。存储单元183可以是存储器。
当上述处理单元为处理器,存储单元为存储器,通信单元为通信接口时,本申请实施例所涉及的终端设备1800可以为图19所示的终端设备1900。如图19所示,终端设备1900包括:处理器191、存储器192和通信接口193。其中,处理器191、存储器192和通信接口193通过总线194相互连接。
其中,总线194可以是PCI总线或EISA总线等。上述总线194可以分为地址总线、数据总线、控制总线等。为便于表示,图19中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。
示例性的,终端设备1900可以包括一个或多个处理器191,即终端设备1900可以包括多核处理器。
当终端设备1900运行时,该终端设备1900执行如图3-图9中任一附图所示的实施例的会话迁移方法。具体的会话迁移方法可参见上述如图3-图9中任一附图所示的实施例中的相关描述,此处不再赘述。
本申请另一实施例还提供一种计算机可读存储介质,该计算机可读存储介质包括一个或多个程序代码,该一个或多个程序包括指令,当终端设备1900中的处理器191在执行该程序代码时,该终端设备1900执行如图3-图9中任一附图所示的会话迁移方法。
在本申请的另一实施例中,还提供一种计算机程序产品,该计算机程序产品包括计算机执行指令,该计算机执行指令存储在计算机可读存储介质中;终端设备的至少一个处理器可以从计算机可读存储介质读取该计算机执行指令,至少一个处理器执行该计算机执行指令使得终端设备实施执行图3-图9中任一附图所示的会话迁移方法中的SM 2的步骤。
本申请实施例提供一种移动管理功能实体,该移动管理功能实体用于执行以上会话迁移方法中的目标移动管理功能实体所执行的步骤。本申请实施例提供的移动管理功能实体可以包括相应步骤所对应的模块。
本申请实施例可以根据上述方法示例对移动管理功能实体进行功能模块的划分,例如,可以对应各个功能划分各个功能模块,也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。本申请实施例中对模块的划分是示意性的,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式。
在采用对应各个功能划分各个功能模块的情况下,图20示出了上述实施例中所涉及的移动管理功能实体的一种可能的结构示意图。如图20所示,移动管理功能实体2000包括获取单元200、处理单元201和发送单元202。获取单元200用于支持该移动管理功能实体2000执行上述实施例中的S402、S407、S412、S417、S502、S507、S516、S521、S602、S612、S617等,和/或用于本文所描述的技术的其它过程;处理单元201用于支持该移动管理功能实体2000执行上述实施例中的S408、S413、S508、S517、S608、S613等,和/或用于本 文所描述的技术的其它过程;发送单元202用于支持该移动管理功能实体2000执行上述实施例中的S403、S409、S414、S503、S509、S513、S603、S609、S614等,和/或用于本文所描述的技术的其它过程。其中,上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述,在此不再赘述。当然,本申请实施例提供的移动管理功能实体2000包括但不限于上述模块,例如移动管理功能实体2000还可以包括存储单元203。存储单元203可以用于存储终端设备的移动管理上下文,也可以用于存储该移动管理功能实体的程序代码和数据。
在采用集成的单元的情况下,本申请实施例中的处理单元201可以是处理器或控制器,例如可以是CPU,DSP。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框,模块和电路。处理单元201也可以是实现计算功能的组合,例如包含一个或多个微处理器组合,DSP和微处理器的组合等。获取单元201和发送单元202可以集成在一个通信单元中实现,该通信单元可以是通信接口。存储单元203可以是存储器。
当上述处理单元为处理器,存储单元为存储器,通信单元为通信接口时,本申请实施例所涉及的移动管理功能实体2000可以为图21所示的移动管理功能实体2100。如图21所示,移动管理功能实体2100包括:处理器211、存储器212和通信接口213。其中,处理器211、存储器212和通信接口213通过总线214相互连接。
其中,总线214可以是PCI总线或EISA总线等。上述总线214可以分为地址总线、数据总线、控制总线等。为便于表示,图21中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。
示例性的,移动管理功能实体2100可以包括一个或多个处理器211,即移动管理功能实体2100可以包括多核处理器。
当移动管理功能实体2100运行时,该移动管理功能实体2100执行如图3-图9中任一附图所示的实施例的会话迁移方法。具体的会话迁移方法可参见上述如图3-图9中任一附图所示的实施例中的相关描述,此处不再赘述。
本申请另一实施例还提供一种计算机可读存储介质,该计算机可读存储介质包括一个或多个程序代码,该一个或多个程序包括指令,当移动管理功能实体2100中的处理器211在执行该程序代码时,该移动管理功能实体2100执行如图3-图9中任一附图所示的会话迁移方法。
在本申请的另一实施例中,还提供一种计算机程序产品,该计算机程序产品包括计算机执行指令,该计算机执行指令存储在计算机可读存储介质中;移动管理功能实体的至少一个处理器可以从计算机可读存储介质读取该计算机执行指令,至少一个处理器执行该计算机执行指令使得移动管理功能实体实施执行图3-图9中任一附图所示的会话迁移方法中的MM 2的步骤。
通过以上的实施方式的描述,所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,仅以上述各功能模块的划分进行举例说明,实际应用中,可以根据需要而将上述功能分配由不同的功能模块完成,即将装置的内部结构 划分成不同的功能模块,以完成以上描述的全部或者部分功能。上述描述的系统,装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
在本申请所提供的几个实施例中,应该理解到,所揭露的系统,装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述模块或单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个系统,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本申请各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)或处理器执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括:快闪存储器、移动硬盘、只读存储器、随机存取存储器、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述,仅为本申请的具体实施方式,但本申请的保护范围并不局限于此,任何在本申请揭露的技术范围内的变化或替换,都应涵盖在本申请的保护范围之内。因此,本申请的保护范围应以所述权利要求的保护范围为准。

Claims (29)

  1. 一种会话迁移方法,其特征在于,包括:
    源会话管理功能实体判断是否更新终端设备的会话;
    若所述源会话管理功能实体确定更新所述终端设备的会话,所述源会话管理功能实体保留第一会话的上下文,并向第一设备发送指示信息,所述指示信息用于指示所述第一设备在等待至获得待发送的所述终端设备的数据之后触发第二会话的建立;
    其中,所述第一会话为所述源会话管理功能实体与所述终端设备之间已建立的会话,所述第一设备为所述终端设备或目标移动管理功能实体,所述第二会话为目标会话管理功能实体与所述终端设备之间的会话。
  2. 根据权利要求1所述的会话迁移方法,其特征在于,还包括:
    在所述源会话管理功能实体向所述第一设备发送所述指示信息之后,所述源会话管理功能实体从所述目标移动管理功能实体接收第一通知消息;
    所述源会话管理功能实体收到所述第一通知消息后,释放所述第一会话的上下文。
  3. 根据权利要求1或2所述的会话迁移方法,其特征在于,所述第一设备为所述终端设备,所述源会话管理功能实体向第一设备发送指示信息,包括:
    所述源会话管理功能实体向源移动管理功能实体发送携带所述指示信息的第一响应消息,所述指示信息被发送至所述终端设备,所述指示信息用于指示所述终端设备在等待至获得待发送的所述终端设备的数据后,向所述目标移动管理功能实体发送用于触发第二会话的建立的信息。
  4. 根据权利要求1或2所述的会话迁移方法,其特征在于,所述第一设备为所述目标移动管理实体,所述源会话管理功能实体向第一设备发送指示信息,包括:
    所述源会话管理功能实体向源移动管理功能实体发送携带所述指示信息的第一响应消息,所述指示信息被发送至所述目标移动管理实体,所述指示信息用于指示所述目标移动管理功能实体等待至获得待发送的所述终端设备的上行数据后,选择所述目标会话管理功能实体,以触发所述第二会话的建立。
  5. 根据权利要求1或2所述的会话迁移方法,其特征在于,所述源会话管理功能实体向第一设备发送指示信息,包括:
    所述源会话管理功能实体从所述终端设备接收到上行数据,获取上行数据应答消息,并在所述上行数据应答消息中添加所述指示信息,向所述第一设备发送携带有所述指示信息的上行数据应答消息。
  6. 根据权利要求1-5中任意一项所述的会话迁移方法,其特征在于,还包括:
    所述源会话管理功能实体从源移动管理功能实体接收第二通知消息,所述第二通知消息携带所述目标移动管理功能实体的标识;
    其中,所述源会话管理功能实体判断是否更新终端设备的会话,包括:
    所述源会话管理功能实体根据第一条件判断是否更新所述终端设备的会 话,所述第一条件包括所述源移动管理功能实体的标识与所述目标移动管理的标识不同。
  7. 根据权利要求6所述的会话迁移方法,其特征在于,所述第一条件还包括:
    所述源会话管理功能实体在预设时间段内接收到的上行数据的数据量大于或等于预设阈值。
  8. 一种会话迁移方法,其特征在于,包括:
    终端设备与源会话管理功能实体之间建立第一会话,所述源会话管理功能实体的服务区域包括第一跟踪区域TA;
    所述终端设备从所述第一TA移动到第二TA后,所述终端设备获取指示信息;
    所述终端设备根据所述指示信息,向目标移动管理功能实体发送用于触发第二会话的建立的信息,所述第二会话为目标会话管理功能实体与所述终端设备之间的会话,所述目标移动管理功能实体的服务区域和所述目标会话管理功能实体的服务区域均包括所述第二TA。
  9. 根据权利要求8所述的会话迁移方法,其特征在于,所述终端设备获取指示信息,包括:
    所述终端设备向所述目标移动管理功能实体发送第一请求消息;所述终端设备从所述目标移动管理功能实体接收携带有所述指示信息的第二响应消息;
    或者,
    所述终端设备从所述目标移动管理功能实体接收携带有所述指示信息的上行数据应答消息。
  10. 根据权利要求9所述的会话迁移方法,其特征在于,所述用于触发第二会话的建立的信息为会话建立请求;
    所述终端设备根据所述指示信息,向所述目标移动管理功能实体发送用于触发第二会话的建立的信息,包括:
    所述终端设备根据指示信息,等待至获得待发送的所述终端设备的数据后,向所述目标移动管理功能实体发送所述会话建立请求。
  11. 根据权利要求8所述的会话迁移方法,其特征在于,所述终端设备获取指示信息,包括:
    所述终端设备接收携带有所述指示信息的下行数据。
  12. 根据权利要求11所述的会话迁移方法,其特征在于,所述用于触发第二会话的建立的信息为会话建立请求或第一上行注册报文;
    所述终端设备根据所述指示信息,向所述目标移动管理功能实体发送用于触发第二会话的建立的信息,包括:
    所述终端设备接收到所述指示信息后,向所述目标移动管理功能实体发送所述会话建立请求或所述第一上行注册报文。
  13. 根据权利要求12所述的会话迁移方法,其特征在于,还包括:
    所述终端设备向所述目标移动管理功能实体发送第二上行注册报文,所述 第二注册报文用于指示所述目标移动管理功能实体通知应用服务器更新下行传输路径,所述下行传输路径为用于传输待发送至所述终端设备的下行数据的路径。
  14. 一种会话迁移方法,其特征在于,包括:
    目标移动管理功能实体获取指示信息;
    所述目标移动管理功能实体根据所述指示信息,等待至获得待发送的所述终端设备的上行数据后,选择目标会话管理功能实体,以触发第二会话的建立,所述第二会话为目标会话管理功能实体与所述终端设备之间的会话。
  15. 根据权利要求14所述的会话迁移方法,其特征在于,所述目标移动管理功能实体获取指示信息,包括:
    所述目标移动管理功能实体向所述源移动管理功能实体发送第二请求消息;所述目标移动管理功能实体从所述源移动管理功能实体接收携带有所述指示信息的第三响应消息;
    或者,
    所述目标移动管理功能实体从源会话管理功能实体接收携带有所述指示信息的上行数据应答消息。
  16. 根据权利要求14或15所述的会话迁移方法,其特征在于,还包括:
    在所述第二会话建立后,所述目标移动管理功能实体向所述源会话管理功能实体发送第一通知消息,所述第一通知消息用于指示所述源会话管理功能实体释放第一会话的上下文,其中,所述第一会话为所述终端设备在移动前与所述源会话管理功能实体建立的会话。
  17. 一种会话管理功能实体,其特征在于,所述会话管理功能实体为源会话管理功能实体,所述会话管理功能实体包括:
    处理单元,用于判断是否更新终端设备的会话,以及用于若确定更新所述终端设备的会话,保留第一会话的上下文,其中,所述第一会话为所述源会话管理功能实体与所述终端设备之间已建立的会话;
    发送单元,用于若所述处理单元确定更新所述终端设备的会话,向第一设备发送指示信息,所述指示信息用于指示所述第一设备在等待至获得待发送的所述终端设备的数据之后触发第二会话的建立,其中,所述第一设备为所述终端设备或目标移动管理功能实体,所述第二会话为目标会话管理功能实体与所述终端设备之间的会话。
  18. 根据权利要求17所述的会话管理功能实体,其特征在于,所述会话管理功能实体还包括接收单元,
    所述接收单元,用于在所述发送单元向所述第一设备发送所述指示信息之后,从所述目标移动管理功能实体接收第一通知消息;
    所述处理单元,还用于在所述接收单元接收到所述第一通知消息后,释放所述第一会话的上下文。
  19. 根据权利要求17或18所述的会话管理功能实体,其特征在于,
    若所述第一设备为所述终端设备,所述发送单元具体用于向源移动管理功 能实体发送携带所述指示信息的第一响应消息,所述指示信息被发送至所述终端设备,所述指示信息用于指示所述终端设备在等待至获得待发送的所述终端设备的数据后,向所述目标移动管理功能实体发送用于触发第二会话的建立的信息;
    若所述第一设备为所述目标移动管理实体,所述发送单元具体用于向源移动管理功能实体发送携带所述指示信息的第一响应消息,所述指示信息被发送至所述目标移动管理实体,所述指示信息用于指示所述目标移动管理功能实体等待至获得待发送的所述终端设备的上行数据后,选择所述目标会话管理功能实体,以触发所述第二会话的建立。
  20. 根据权利要求17或18所述的会话管理功能实体,其特征在于,所述会话管理功能实体还包括接收单元,
    所述接收单元,用于从所述终端设备接收到上行数据,获取上行数据应答消息;
    所述处理单元,还用于在所述接收单元获取到的所述上行数据应答消息中添加所述指示信息;
    所述发送单元,具体用于向所述第一设备发送携带有所述指示信息的上行数据应答消息。
  21. 根据权利要求17-20中任意一项所述的会话管理功能实体,其特征在于,所述会话管理功能实体还包括接收单元,
    所述接收单元,用于从源移动管理功能实体接收第二通知消息,所述第二通知消息携带所述目标移动管理功能实体的标识;
    所述处理单元,具体用于根据第一条件判断是否更新所述终端设备的会话,所述第一条件包括所述源移动管理功能实体的标识与所述接收单元接收到的所述第二通知消息所携带的所述目标移动管理的标识不同。
  22. 根据权利要求21所述的会话管理功能实体,其特征在于,
    所述第一条件还包括所述接收单元在预设时间段内接收到的上行数据的数据量大于或等于预设阈值。
  23. 一种终端设备,其特征在于,包括:
    处理单元,用于与源会话管理功能实体之间建立第一会话,所述源会话管理功能实体的服务区域包括第一跟踪区域TA;
    获取单元,用于所述终端设备从所述第一TA移动到第二TA后,获取指示信息;
    发送单元,用于根据所述获取单元获取到的所述指示信息,向目标移动管理功能实体发送用于触发第二会话的建立的信息,所述第二会话为目标会话管理功能实体与所述终端设备之间的会话,所述目标移动管理功能实体的服务区域和所述目标会话管理功能实体的服务区域均包括所述第二TA。
  24. 根据权利要求23所述的终端设备,其特征在于,
    所述发送单元,还用于向所述目标移动管理功能实体发送第一请求消息;所述获取单元,具体用于从所述目标移动管理功能实体接收携带有所述指示信 息的第二响应消息;
    或者,
    所述获取单元,具体用于从所述目标移动管理功能实体接收携带有所述指示信息的上行数据应答消息;
    若所述获取单元具体用于接收携带有所述指示信息的第二响应消息或具体用于接收携带有所述指示信息的上行应答消息,所述用于触发第二会话的建立的信息为会话建立请求,所述发送单元具体用于根据指示信息,等待至获得待发送的所述终端设备的数据后,向所述目标移动管理功能实体发送所述会话建立请求。
  25. 根据权利要求23所述的终端设备,其特征在于,
    所述获取单元,具体用于接收携带有所述指示信息的下行数据;
    若所述获取单元具体用于接收携带有所述指示信息的下行数据,所述用于触发第二会话的建立的信息为会话建立请求或第一上行注册报文,所述发送单元具体用于在所述获取单元接收到所述指示信息后,向所述目标移动管理功能实体发送所述会话建立请求或所述第一上行注册报文。
  26. 根据权利要求25所述的终端设备,其特征在于,
    所述发送单元,还用于向所述目标移动管理功能实体发送第二上行注册报文,所述第二注册报文用于指示所述目标移动管理功能实体通知应用服务器更新下行传输路径,所述下行传输路径为用于传输待发送至所述终端设备的下行数据的路径。
  27. 一种移动管理功能实体,其特征在于,所述移动管理功能实体为目标移动管理功能实体,所述移动管理功能实体包括:
    获取单元,用于获取指示信息;
    所述处理单元,用于根据所述获取单元获取到的所述指示信息,等待至获得待发送的所述终端设备的上行数据后,选择目标会话管理功能实体,以触发第二会话的建立,所述第二会话为目标会话管理功能实体与所述终端设备之间的会话。
  28. 根据权利要求27所述的移动管理功能实体,其特征在于,
    所述移动管理功能实体还包括发送单元,所述发送单元,用于向所述源移动管理功能实体发送第二请求消息;所述获取单元,用于从所述源移动管理功能实体接收携带有所述指示信息的第三响应消息;
    或者,
    所述获取单元,用于从源会话管理功能实体接收携带有所述指示信息的上行数据应答消息。
  29. 根据权利要求27或28所述的移动管理功能实体,其特征在于,
    所述移动管理功能实体还包括发送单元,
    所述发送单元,用于在所述第二会话建立后,所述目标移动管理功能实体向所述源会话管理功能实体发送第一通知消息,所述第一通知消息用于指示所述源会话管理功能实体释放第一会话的上下文,其中,所述第一会话为所述终 端设备在移动前与所述源会话管理功能实体建立的会话。
PCT/CN2017/075904 2017-03-07 2017-03-07 一种会话迁移方法及设备 WO2018161263A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP17899598.1A EP3579589B1 (en) 2017-03-07 2017-03-07 Session migration method and device
CN201780056409.7A CN109691150B (zh) 2017-03-07 2017-03-07 一种会话迁移方法及设备
PCT/CN2017/075904 WO2018161263A1 (zh) 2017-03-07 2017-03-07 一种会话迁移方法及设备
US16/563,346 US11082893B2 (en) 2017-03-07 2019-09-06 Session migration method and device applied to a UE tracking area update

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/075904 WO2018161263A1 (zh) 2017-03-07 2017-03-07 一种会话迁移方法及设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/563,346 Continuation US11082893B2 (en) 2017-03-07 2019-09-06 Session migration method and device applied to a UE tracking area update

Publications (1)

Publication Number Publication Date
WO2018161263A1 true WO2018161263A1 (zh) 2018-09-13

Family

ID=63447280

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/075904 WO2018161263A1 (zh) 2017-03-07 2017-03-07 一种会话迁移方法及设备

Country Status (4)

Country Link
US (1) US11082893B2 (zh)
EP (1) EP3579589B1 (zh)
CN (1) CN109691150B (zh)
WO (1) WO2018161263A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023071974A1 (zh) * 2021-10-29 2023-05-04 华为技术有限公司 通信系统、通信方法和通信装置

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4258762A3 (en) 2017-05-09 2023-12-27 Telefonaktiebolaget LM Ericsson (publ) Amf relocation with n3iwf handling
US10757611B2 (en) * 2017-09-22 2020-08-25 Ofinno, Llc SMF and AMF relocation during UE registration
CN112235840B (zh) * 2020-10-14 2022-09-13 中国联合网络通信集团有限公司 会话终端切换方法、装置、实体和系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101094096A (zh) * 2006-06-20 2007-12-26 华为技术有限公司 一种演进网络架构下的移动性管理方法
CN103428668A (zh) * 2012-05-17 2013-12-04 大唐移动通信设备有限公司 一种跟踪区更新方法及装置
CN104936237A (zh) * 2009-08-21 2015-09-23 Lg电子株式会社 负责控制面的网络实体及其执行的控制会话的方法
US20150296557A1 (en) * 2012-11-01 2015-10-15 Lg Electronics Inc. Mtc monitoring method

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1619838A1 (en) * 2004-07-21 2006-01-25 Siemens Mobile Communications S.p.A. Push to watch dedicated network element and software architecture
US8886188B2 (en) * 2007-03-20 2014-11-11 Qualcomm Incorporated Method and apparatus for transfer of session reference network controller
CN101316435B (zh) * 2007-05-31 2012-08-08 华为技术有限公司 呼叫控制的方法和ims的电路交换控制装置及终端设备
US20110039562A1 (en) * 2009-02-05 2011-02-17 Qualcomm Incorporated Session-specific signaling for multiple access networks over a single access network
CN101990174B (zh) * 2009-07-29 2016-06-15 中兴通讯股份有限公司 消息发送方法及通用无线分组业务服务支持节点
US8331938B2 (en) * 2009-11-23 2012-12-11 Telefonaktiebolaget L M Ericsson (Publ) Moving user equipment without service interruption
KR101712865B1 (ko) * 2010-09-09 2017-03-08 삼성전자주식회사 이동 통신 시스템에서 비계층 프로토콜을 이용한 통신 지원 방법 및 장치
CN102740268B (zh) 2011-04-07 2017-04-12 中兴通讯股份有限公司 分组数据网络网关及终端移动性管理的系统
US9185595B2 (en) * 2011-08-01 2015-11-10 Telefonaktiebolaget L M Ericsson (Publ) Method, apparatus and system for moving wireless terminals in mobility management serving node pool
CN103731811B (zh) * 2012-10-11 2018-08-31 中兴通讯股份有限公司 一种演进的分组核心网络实现移动性管理的方法和系统
US9826390B2 (en) * 2013-03-29 2017-11-21 Intel IP Corporation Management techniques for wireless network mobility procedures
CN104660550B (zh) * 2013-11-20 2019-03-01 北京邮电大学 一种在多服务器之间进行会话迁移的方法
CN106162705B (zh) 2015-03-31 2020-02-04 电信科学技术研究院 一种控制用户面承载建立的方法及设备
US9883385B2 (en) * 2015-09-15 2018-01-30 Qualcomm Incorporated Apparatus and method for mobility procedure involving mobility management entity relocation
CN107592331B (zh) * 2016-07-08 2021-11-02 中兴通讯股份有限公司 会话连续的实现方法、装置及系统
WO2018110939A1 (ko) * 2016-12-15 2018-06-21 엘지전자(주) 무선 통신 시스템에서의 트래킹 영역 할당 방법 및 이를 위한 장치

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101094096A (zh) * 2006-06-20 2007-12-26 华为技术有限公司 一种演进网络架构下的移动性管理方法
CN104936237A (zh) * 2009-08-21 2015-09-23 Lg电子株式会社 负责控制面的网络实体及其执行的控制会话的方法
CN103428668A (zh) * 2012-05-17 2013-12-04 大唐移动通信设备有限公司 一种跟踪区更新方法及装置
US20150296557A1 (en) * 2012-11-01 2015-10-15 Lg Electronics Inc. Mtc monitoring method

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
MEDIATEK: "Removal of ''WB-E-UTRA'' terminology", MEETING #113AH, 3GPP S2-161000, vol. SA WG2, 26 February 2016 (2016-02-26), pages 2, XP051072873 *
SAMSUNG: "Update to Solution 4.25: Local Area Data Network", SA WG2 MEETING #S2-117, 3GPP S2-165546, 21 October 2016 (2016-10-21), pages 2, XP051155134 *
See also references of EP3579589A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023071974A1 (zh) * 2021-10-29 2023-05-04 华为技术有限公司 通信系统、通信方法和通信装置

Also Published As

Publication number Publication date
CN109691150A (zh) 2019-04-26
US11082893B2 (en) 2021-08-03
EP3579589A4 (en) 2020-02-19
EP3579589B1 (en) 2021-05-12
US20190394682A1 (en) 2019-12-26
EP3579589A1 (en) 2019-12-11
CN109691150B (zh) 2021-09-14

Similar Documents

Publication Publication Date Title
EP2445159B1 (en) Policy and charging control method and system for multi-pdn connections of single apn
WO2018161263A1 (zh) 一种会话迁移方法及设备
WO2017028288A1 (zh) 无线通信接入方法、通信装置、无线终端及系统
WO2014059825A1 (zh) 发送、接收数据的方法、装置及数据的收发系统
CN107211271B (zh) 用户设备接入网络的方法、核心网实体、基站及第一ue
WO2019158040A1 (zh) 用于切换的方法和装置
WO2018145670A1 (zh) 基站的切换方法、系统和存储介质
WO2018170798A1 (zh) 一种会话迁移方法及设备
EP4090039A1 (en) Method and apparatus for transmitting multicast service
CN110831007B (zh) 用户面完整性保护方法、装置及设备
CN113543135B (zh) 授权方法、策略控制功能设备和接入和移动管理功能设备
WO2020073802A1 (zh) 一种鉴权的方法及装置
WO2021136485A1 (zh) 一种通信方法及装置
CN113411860B (zh) 一种通信路径变更方法及设备
EP4109939A1 (en) Message forwarding method and apparatus
CN107006046B (zh) 一种数据传输方法及相关设备、系统
EP3316608B1 (en) A communication network and a method for establishing non-access stratum connections in a communication network
CN116567620A (zh) 通信方法及装置
WO2023087923A1 (zh) 一种用户面网元分离的确定方法及通信装置
WO2022218099A1 (zh) 组播通信方法及通信装置
CN108141780B (zh) 数据业务处理方法、装置、终端及网络设备
WO2023213282A1 (zh) Ursp规则的验证方法、装置及网络侧设备
WO2023077948A1 (zh) 一种通信的方法和装置
CN111436086B (zh) 安全保护方法及装置
WO2021168862A1 (zh) 一种通信方法及设备

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017899598

Country of ref document: EP

Effective date: 20190905