WO2019033817A1 - 通信方法、装置和系统 - Google Patents

通信方法、装置和系统 Download PDF

Info

Publication number
WO2019033817A1
WO2019033817A1 PCT/CN2018/088280 CN2018088280W WO2019033817A1 WO 2019033817 A1 WO2019033817 A1 WO 2019033817A1 CN 2018088280 W CN2018088280 W CN 2018088280W WO 2019033817 A1 WO2019033817 A1 WO 2019033817A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
ran node
amf
message
user equipment
Prior art date
Application number
PCT/CN2018/088280
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 EP18845793.1A priority Critical patent/EP3661315A4/en
Priority to BR112020003079-1A priority patent/BR112020003079A2/pt
Publication of WO2019033817A1 publication Critical patent/WO2019033817A1/zh
Priority to US16/791,962 priority patent/US20200187144A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H04W48/04—Access restriction performed under specific conditions based on user or terminal location or mobility data, e.g. moving direction, speed
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/20—Selecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

  • the present application relates to the field of communications, and in particular, to a communication method, apparatus, and system.
  • the 5th Generation (5G) specification defines a Radio Resource Control (RRC) RRC-inactive state, which is an RRC state of a terminal device.
  • RRC Radio Resource Control
  • RAN Radio Access Network
  • CN Core Network
  • TA Tracking Area
  • TAL Tracking Area List
  • LTE Long Term Evolution
  • the TA is used to indicate the location of the area where the terminal device is located, and each TA can be represented by a Tracking Area Identity (TAI).
  • TAI Tracking Area Identity
  • the TAL is used to indicate the registration area of the terminal device, and the TAL contains the TAI of one or more TAs.
  • TAU Tracking Area Update
  • TAU Tracking Area Update
  • the ping-pong effect causes the TA to be updated frequently.
  • the terminal device in the idle state and the connected state can update the TAL by using a periodic TAU or a mobile triggered TAU, where the mobile triggered TAU refers to the terminal device when moving out of the area corresponding to the TAL,
  • the TAI of the location does not belong to the TAU caused by the TAL that the terminal device has allocated.
  • the 5G specification does not give an explanation for the TAU in which the terminal device in the RRC inactive state performs the mobile trigger, and how the RAN node and the CN node specifically perform the procedure.
  • An embodiment of the present application provides a communication method, apparatus, and system for implementing a mobile triggered TAU in a terminal device in an RRC inactive state.
  • the embodiment of the present application provides a communication method, where the method includes: when a TAI in a location where a terminal device of a radio resource control RRC inactive state is not belonging to a tracking area list TAL of a terminal device, the terminal device converts Managing the CM idle state for the connection; the terminal device sends a registration request message to the access and mobility management function AMF through the target radio access network RAN node, the registration request message is used to request to allocate the TAL for the terminal device; the terminal device receives the target RAN node A registration acceptance message sent by the AMF, the registration acceptance message including the assigned TAL.
  • the communication method provided by the embodiment of the present application when the TAI of the terminal device in the RRC inactive state does not belong to the TAL of the terminal device, indicating that the terminal device has moved to the area defined by the TAL of the terminal device, At this time, the terminal device converts to the CM idle state, and the terminal device sends a registration request message to the AMF to request to allocate a TAL to the terminal device at the current location, and the AMF sends an N2 user equipment context release command message to the source RAN node to release the source RAN node storage.
  • the context of the terminal device after receiving the response message of the source RAN node release context, the AMF sends a registration accept message to the terminal device through the target RAN node, where the registration accept message includes the TAL allocated for the terminal device.
  • the foregoing embodiment implements a TAU in which a terminal device in an RRC inactive state performs a mobile trigger.
  • the area corresponding to the TAI where the terminal device is located is the disallowed area
  • the area corresponding to the tracking area list TAL is the allowed area. This embodiment shows that the terminal device moves from the allowed area to the disallowed area.
  • the embodiment of the present application provides a terminal device, where the terminal device includes: a converting unit, configured to: when a TSI in a location where a terminal device of a RRC inactive state is in a radio resource control state does not belong to a tracking area list of the terminal device TAL, the terminal device is converted into a connection management CM idle state; the sending unit is configured to send a registration request message to the access and mobility management function AMF through the target radio access network RAN node, where the registration request message is used to request the terminal device And a receiving unit, configured to receive, by the target RAN node, a registration accept message sent by the AMF, where the registration accept message includes the allocated TAL.
  • a converting unit configured to: when a TSI in a location where a terminal device of a RRC inactive state is in a radio resource control state does not belong to a tracking area list of the terminal device TAL, the terminal device is converted into a connection management CM idle state; the sending unit is configured to send a
  • the principle and the beneficial effects of the terminal device can be referred to the foregoing first aspect and the possible method embodiments of the first aspect and the beneficial effects thereof. Therefore, the implementation of the terminal device can be referred to the above. The implementation of the first aspect and the various possible methods of the first aspect will not be repeated here.
  • an embodiment of the present application provides a communication method, where the method includes: an access and mobility management function AMF receives a registration request message from a target radio access network RAN node, where the registration request message is used to request allocation for a terminal device.
  • the tracking area list TAL the terminal device is in the radio resource control RRC inactive state;
  • the AMF sends an N2 user equipment context release command message to the source RAN node;
  • the AMF receives the N2 user equipment context release complete message sent by the source RAN node;
  • the AMF passes the target RAN
  • the node sends a registration accept message to the terminal device, and the registration accept message includes a TAL.
  • the communication method provided by the embodiment of the present application when the TAI of the terminal device in the RRC inactive state does not belong to the TAL of the terminal device, indicating that the terminal device has moved to the area defined by the TAL of the terminal device, At this time, the terminal device converts to the CM idle state, and the terminal device sends a registration request message to the AMF to request to allocate a TAL to the terminal device at the current location, and the AMF sends an N2 user equipment context release command message to the source RAN node to release the source RAN node storage.
  • the context of the terminal device after receiving the response message of the source RAN node release context, the AMF sends a registration accept message to the terminal device through the target RAN node, where the registration accept message includes the TAL allocated for the terminal device.
  • the foregoing embodiment implements a TAU in which a terminal device in an RRC inactive state performs a mobile trigger.
  • the method further includes: receiving, by the AMF, the location information of the terminal device from the target RAN node; the AMF determining, according to the location information of the terminal device and the disallowed area in the context of the terminal device, that the terminal device is located in the disallowed area; The AMF sets the terminal device to the connection management CM idle state.
  • This embodiment provides a specific implementation manner in which the AMF performs CM state transition on the terminal device, so that the CM state of the terminal device is the CM idle state.
  • the method further includes: the AMF sending a packet data unit PDU session deactivation request message to the session management function SMF, where the PDU session deactivation request message is used to request the SMF to deactivate the PDU session of the terminal device; or, AMF The indication information is sent to the SMF, wherein the indication information is used to indicate that the terminal device is located in the disallowed area.
  • This embodiment provides a specific implementation manner in which the AMF and the SMF perform PDU session state transition on the terminal device, so that the PDU session of the terminal device is in a deactivated state or an idle state.
  • the N2 user equipment context release command message includes a release reason, and the release reason is used to indicate that the terminal device is located in the disallowed area.
  • This embodiment provides a possible implementation of the cause of the release.
  • an embodiment of the present application provides an access and mobility management function AMF, where the AMF includes: a receiving unit, configured to receive a registration request message from a target radio access network RAN node, where the registration request message is used to request
  • the terminal device allocates a tracking area list TAL, the terminal device is in a radio resource control RRC inactive state, the sending unit is configured to send an N2 user equipment context release command message to the source RAN node, and the receiving unit is configured to receive the N2 sent by the source RAN node.
  • a user equipment context release completion message the sending unit is further configured to send a registration accept message to the terminal device by using the target RAN node, where the registration accept message includes a TAL.
  • the embodiment of the present application provides a communication method, where the method includes: the session management function SMF receives indication information from the access and mobility management function AMF, where the indication information is used to indicate that the terminal device is located in the disallowed area; The local session management SM policy and the indication information trigger a PDU session release process or a PDU session deactivation process of the terminal device.
  • This embodiment provides a specific implementation manner in which the AMF and the SMF perform PDU session state transition on the terminal device, so that the PDU session of the terminal device is in a deactivated state or an idle state.
  • the embodiment of the present application provides a session management function SMF, where the SMF includes: a receiving unit, configured to receive indication information from the access and mobility management function AMF, where the indication information is used to indicate that the terminal device is located in the disallowed area.
  • the sending unit is configured to trigger the PDU session release process or the PDU session deactivation process of the terminal device according to the local session management SM policy and the indication information.
  • the embodiment of the present application provides a communication method, where the method includes: when a TAI in a location where a terminal device of a radio resource control RRC inactive state is not belonging to a tracking area list TAL of a terminal device, the terminal device The target radio access network RAN node sends a radio resource control RRC connection recovery request message, the terminal device is in an RRC inactive state; the terminal device receives an RRC connection recovery reject message from the target RAN node; the terminal device recovers the reject message according to the RRC connection, from the connection management The CM connected state is converted to the CM idle state.
  • a communication method provided by the real-time example of the present application when the TAI of the location where the terminal device in the RRC inactive state is located does not belong to the TAL of the terminal device, indicating that the device has moved to the area defined by the TAL, and the terminal device attempts to restore the RRC first.
  • the connection the source RAN node may reject or accept the request.
  • the source RAN node informs the terminal device through the target RAN node that it refuses to resume the RRC connection, and on the other hand, the target RAN node initiates the N2 release procedure through the AMF.
  • the target RAN node When accepted, the target RAN node notifies the terminal device to accept its request, and then the terminal device initiates a registration request to acquire the TAL of the terminal device from the AMF.
  • the TAU in which the terminal device in the RRC inactive state performs mobile triggering is implemented.
  • the target RAN node is located in an unallowed area.
  • This embodiment provides the area in which the target RAN node may be located.
  • the embodiment of the present application provides a terminal device, where the terminal device includes: a sending unit, configured to: when a TSI in a location where a terminal device of a radio resource control RRC inactive state is located does not belong to a tracking area list of the terminal device TAL, sending a radio resource control RRC connection recovery request message to the target radio access network RAN node, the terminal device is in an RRC inactive state; the receiving unit is configured to receive an RRC connection recovery reject message from the target RAN node; According to the RRC connection recovery reject message, the connection management CM connection state is switched to the CM idle state.
  • a sending unit configured to: when a TSI in a location where a terminal device of a radio resource control RRC inactive state is located does not belong to a tracking area list of the terminal device TAL, sending a radio resource control RRC connection recovery request message to the target radio access network RAN node, the terminal device is in an RRC inactive state
  • the receiving unit is configured to receive an RRC connection recovery
  • the principle and the beneficial effects of the terminal device can be solved by referring to the foregoing possible method embodiments of the seventh and seventh aspects, and the beneficial effects brought about by the terminal device.
  • Embodiments of the seventh aspect and the possible methods of the seventh aspect are not repeated herein.
  • the embodiment of the present application provides a communication method, where the method includes: a target radio access network RAN node receives a radio resource control RRC connection recovery request message from a terminal device, the terminal device is in an RRC inactive state; and the target RAN node Sending a user equipment context request message to the source RAN node, and acquiring a user equipment context request message for acquiring context information of the terminal device; when the target RAN node receives the context information of the terminal device from the source RAN node, the target RAN node is to the terminal
  • the device sends an RRC connection recovery message, sends a path switch request message to the access and mobility management function AMF, receives a path switch response message from the AMF, and sends a user equipment context release message to the source RAN node; or, when the target RAN node receives When the user equipment context reject message is obtained from the source RAN node, or when the target RAN node receives the Get User Equipment Context Response message from the source RAN node
  • the target RAN node is connected to a terminal device sends an RRC reject message recovery.
  • a communication method provided by the real-time example of the present application when the TAI of the location where the terminal device in the RRC inactive state is located does not belong to the TAL of the terminal device, indicating that the device has moved to the area defined by the TAL, and the terminal device attempts to restore the RRC first.
  • the connection the source RAN node may reject or accept the request.
  • the source RAN node informs the terminal device through the target RAN node that it refuses to resume the RRC connection, and on the other hand, the target RAN node initiates the N2 release procedure through the AMF.
  • the target RAN node When accepted, the target RAN node notifies the terminal device to accept its request, and then the terminal device initiates a registration request to acquire the TAL of the terminal device from the AMF.
  • the TAU in which the terminal device in the RRC inactive state performs mobile triggering is implemented.
  • the path switch response message includes a tracking area list TAL that is re-allocated for the terminal device.
  • the method further includes: the target RAN node generates a RAN notification area RNA according to the TAL; and the target RAN node sends the RNA to the terminal device.
  • This embodiment provides a specific implementation of how the target RAN node generates RNA for the terminal device such that the terminal device can acquire updated RNA.
  • the target RAN node is located in the disallowed area, and after the target RAN node receives the context information of the terminal device from the source RAN node, the method further includes: the target RAN node triggers the access network AN node user equipment context The release process; the target RAN node deletes the context information of the terminal device. This embodiment causes the target RAN node to delete the context of the terminal device.
  • the embodiment of the present application provides a target radio access network RAN node, where the target RAN node includes: a receiving unit, configured to receive a radio resource control RRC connection recovery request message from a terminal device, where the terminal device is in RRC inactive.
  • a sending unit configured to send a user equipment context request message to the source RAN node, and obtain a user equipment context request message for acquiring context information of the terminal device; and when the target RAN node receives the context information of the terminal device from the source RAN node
  • the sending unit is further configured to send an RRC connection recovery message to the terminal device, and send a path switch request message to the access and mobility management function AMF, where the receiving unit is further configured to receive a path switch response message from the AMF, and send the unit, For transmitting a user equipment context release message to the source RAN node; or when the target RAN node receives the acquire user equipment context reject message from the source RAN node, or when the target RAN node receives the acquire user equipment from the source RAN node Context response message and get on user device
  • the sending unit is further configured to send an RRC connection recovery reject message to the terminal device.
  • the principle and benefit of the problem solved by the target RAN node can be seen in the possible method implementations of the foregoing ninth and ninth aspects and the beneficial effects, so that the implementation of the target RAN node can be implemented.
  • the repetitive points will not be described again.
  • an embodiment of the present application provides a communication method, where the method includes: an access and mobility management function AMF receiving a path switch request message from a target radio access network RAN node, where the path switch request message carries a terminal device
  • the location information of the terminal device determines that the TAI of the location of the terminal device does not belong to the tracking area list TAL of the terminal device; the AMF re-allocates the TAL for the terminal device and sends the re-allocated TAL to the target RAN node.
  • a communication method provided by the real-time example of the present application when the TAI of the location where the terminal device in the RRC inactive state is located does not belong to the TAL of the terminal device, indicating that the device has moved to the area defined by the TAL, and the terminal device attempts to restore the RRC first.
  • the connection the source RAN node may reject or accept the request.
  • the source RAN node informs the terminal device through the target RAN node that it refuses to resume the RRC connection, and on the other hand, the target RAN node initiates the N2 release procedure through the AMF.
  • the target RAN node When accepted, the target RAN node notifies the terminal device to accept its request, and then the terminal device initiates a registration request to acquire the TAL of the terminal device from the AMF.
  • the TAU in which the terminal device in the RRC inactive state performs mobile triggering is implemented.
  • the reassigned TAL is sent to the target RAN node, including: the AMF sends a path switch response message to the target RAN node, where the path switch response message includes the reassigned TAL.
  • This embodiment provides a possible implementation of the message that the AMF uses to send the reassigned TAL to the target RAN node.
  • the method further includes: when the target RAN node is located in the disallowed area, the AMF sends the indication information to the session management function SMF, where the indication information is used to indicate that the terminal device is located in the disallowed area; or, the AMF triggers the access.
  • Network AN node user equipment context release process when the TAI where the terminal device is located does not belong to the TAL of the terminal device, the target RAN releases the context of the UE.
  • the embodiment of the present application provides an access and mobility management function AMF, where the AMF includes: a receiving unit, configured to receive a path switch request message from a target radio access network RAN node, in a path switch request message. And a determining unit, configured to determine, according to the location information of the terminal device, that the TAI where the terminal device is located does not belong to the tracking area list TAL of the terminal device; and the sending unit is configured to re-allocate the TAL for the terminal device, and A reassigned TAL is sent to the target RAN node.
  • the AMF includes: a receiving unit, configured to receive a path switch request message from a target radio access network RAN node, in a path switch request message. And a determining unit, configured to determine, according to the location information of the terminal device, that the TAI where the terminal device is located does not belong to the tracking area list TAL of the terminal device; and the sending unit is configured to re-allocate the TAL for the terminal device, and A reas
  • the embodiment of the present application provides a communication method, where the method includes: a source radio access network RAN node receives a user equipment context request message from a target RAN node, and acquires a user equipment context request message for acquiring a terminal device.
  • the terminal device is in a radio resource control RRC inactive state; when the target RAN node is in the disallowed area, the source RAN node sends a Get User Equipment Context Reject message to the target RAN node; or, when the target RAN node is in the disallowed area
  • the source RAN node sends a user equipment context response message to the target RAN node, and the user equipment context response message carries the failure indication information, where the failure indication information is used to indicate the failure reason of acquiring the context information of the terminal device;
  • the ingress and mobility management function AMF sends an N2 User Equipment Context Release Request message.
  • a communication method provided by the real-time example of the present application when the TAI of the location where the terminal device in the RRC inactive state is located does not belong to the TAL of the terminal device, indicating that the device has moved to the area defined by the TAL, and the terminal device attempts to restore the RRC first.
  • the connection the source RAN node may reject or accept the request.
  • the source RAN node informs the terminal device through the target RAN node that it refuses to resume the RRC connection, and on the other hand, the target RAN node initiates the N2 release procedure through the AMF.
  • the target RAN node When accepted, the target RAN node notifies the terminal device to accept its request, and then the terminal device initiates a registration request to acquire the TAL of the terminal device from the AMF.
  • the TAU in which the terminal device in the RRC inactive state performs mobile triggering is implemented.
  • the obtaining user equipment context reject message carries the reason for the rejection, and the reason for the rejection is that the terminal device is located in the disallowed area;
  • the N2 user equipment context release request message carries the request release reason, and the request release reason is that the terminal device is located.
  • the area is not allowed; or the failure indication information is used to indicate that the terminal device is located in the disallowed area;
  • the N2 user equipment context release request message carries the request release reason, and the request release reason is that the terminal device is located in the disallowed area.
  • the embodiment of the present application provides a source radio access network RAN node, where the source RAN node includes: a receiving unit, configured to receive a user equipment context request message from the target RAN node, and obtain a user equipment context request message.
  • the terminal device For obtaining the context information of the terminal device, the terminal device is in the RRC inactive state of the radio resource control, and the sending unit is configured to: when the target RAN node is located in the disallowed area, send the user equipment context reject message to the target RAN node; or When the target RAN node is located in the disallowed area, the user equipment context response message is sent to the target RAN node, and the user equipment context response message carries the failure indication information, where the failure indication information is used to indicate the failure reason of acquiring the context information of the terminal device;
  • the unit is further configured to send an N2 user equipment context release request message to the access and mobility management function AMF.
  • the embodiment of the present application provides a terminal device, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, and the processor is connected to the memory through the bus, when the terminal When the device is in operation, the processor executes the computer-executable instructions stored in the memory to cause the terminal device to perform the method of any one of the preceding aspects or the seventh aspect.
  • the embodiment of the present application provides a computer storage medium, comprising instructions, when executed on a computer, causing the computer to perform the method of any one of the first aspect or the seventh aspect method.
  • the embodiment of the present application provides a computer program product comprising instructions, when executed on a computer, causing the computer to perform any one of the first aspect or the seventh aspect Methods.
  • an embodiment of the present application provides an access and mobility management function AMF, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, and the processor and the memory pass the A bus connection, the processor executing the computer-executed instructions stored in the memory to cause the AMF to perform the method of any one of the preceding aspects or the eleventh aspect.
  • the embodiment of the present application provides a computer storage medium, including instructions, when executed on a computer, causing the computer to perform any one of the third aspect or the eleventh aspect Methods.
  • the embodiment of the present application provides a computer program product comprising instructions, when executed on a computer, causing the computer to perform any one of the third aspect or the eleventh aspect The method described.
  • the embodiment of the present application provides a session management function SMF, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, and the processor is connected to the memory through the bus.
  • SMF session management function
  • the processor executes the computer-executed instructions stored in the memory to cause the SMF to perform the method of any of the above fifth aspects.
  • the embodiment of the present application provides a computer storage medium, comprising instructions, when executed on a computer, causing the computer to perform the method of any one of the fifth aspects.
  • the embodiment of the present application provides a computer program product comprising instructions, when executed on a computer, causing the computer to perform the method of any one of the fifth aspects.
  • the embodiment of the present application provides a radio access network RAN node, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, and the processor and the memory pass the bus And, when the RAN node is in operation, the processor executes the computer-executed instructions stored in the memory to cause the RAN node to perform the method of any one of the preceding ninth or thirteenth aspect.
  • the embodiment of the present application provides a computer storage medium, including instructions, when executed on a computer, causing the computer to perform any one of the ninth aspect or the thirteenth aspect The method described.
  • the embodiment of the present application provides a computer program product comprising instructions, when executed on a computer, causing the computer to perform any one of the ninth aspect or the thirteenth aspect Said method.
  • FIG. 1 is a schematic structural diagram of a communication system according to an embodiment of the present application.
  • FIG. 2 is a schematic structural diagram of hardware of each device in a system according to an embodiment of the present application.
  • FIG. 3 is a schematic flowchart 1 of a communication method provided by an embodiment of the present application.
  • FIG. 4 is a schematic flowchart 2 of a communication method according to an embodiment of the present application.
  • FIG. 5 is a schematic flowchart 3 of a communication method according to an embodiment of the present application.
  • FIG. 6 is a schematic flowchart 4 of a communication method according to an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of a SMF triggering PDU session release process according to an embodiment of the present application.
  • FIG. 8 is a schematic flowchart of a SMF-triggered PDU session deactivation process according to an embodiment of the present application.
  • FIG. 9 is a schematic flowchart 5 of a communication method according to an embodiment of the present application.
  • FIG. 10 is a schematic flowchart 6 of a communication method according to an embodiment of the present application.
  • FIG. 11 is a schematic flowchart of a target RAN node triggering an AN node UE context release process according to an embodiment of the present disclosure
  • FIG. 12 is a schematic flowchart diagram of a communication method according to an embodiment of the present application.
  • FIG. 13 is a schematic flowchart diagram of a communication method according to an embodiment of the present application.
  • FIG. 14 is a schematic flowchart of an AMF triggering AN node UE context release process according to an embodiment of the present application
  • 15 is a schematic flowchart nin of a communication method according to an embodiment of the present application.
  • 16 is a schematic flowchart 10 of a communication method according to an embodiment of the present application.
  • 17 is a schematic flowchart 11 of a communication method according to an embodiment of the present application.
  • FIG. 18 is a schematic flowchart diagram of a communication method according to an embodiment of the present application.
  • FIG. 19 is a schematic structural diagram 1 of a terminal device according to an embodiment of the present application.
  • FIG. 20 is a second schematic structural diagram of a terminal device according to an embodiment of the present application.
  • FIG. 21 is a schematic structural diagram 1 of a RAN node according to an embodiment of the present application.
  • FIG. 22 is a schematic structural diagram 2 of a RAN node according to an embodiment of the present disclosure.
  • FIG. 23 is a schematic structural diagram 1 of an AMF according to an embodiment of the present application.
  • FIG. 24 is a second schematic structural diagram of an AMF according to an embodiment of the present application.
  • 25 is a schematic structural diagram 1 of an SMF according to an embodiment of the present application.
  • FIG. 26 is a schematic structural diagram 2 of an SMF according to an embodiment of the present application.
  • the network architecture and the service scenario described in the embodiments of the present application are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute a limitation of the technical solutions provided by the embodiments of the present application.
  • the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems. It should be noted that the solution in the embodiment of the present application can also be applied to other wireless communication networks, and the corresponding names can also be replaced by the names of corresponding functions in other wireless communication networks.
  • a schematic diagram of a network architecture of a communication system includes: a terminal device 101, a radio access network (RAN) node 102, and an access and mobility management function (Access). And Mobility Management Function (AMF) 103, User Plane Function (UPF) 104, Session Management Function (SMF) 105, Policy Control Function (PCF) 106, Unified Data Management (Unified) Data Management, UDM) 107. among them:
  • the terminal device 101 may include a communication device such as a User Equipment (UE), a Tablet (Pad), and a Personal Computer (PC).
  • UE User Equipment
  • Pad Tablet
  • PC Personal Computer
  • the RAN node 102 can be a 5G side base station through which the terminal device can access the 5G communication system.
  • the AMF103 is a 5G core network device, which is used to authenticate and authorize users and manage user mobility.
  • the UPF 104 is a user plane device of the 5G core network, and provides a user plane service for a packet data unit (PDU) session of the terminal device; it is an interface gateway between the carrier network and the external network.
  • PDU packet data unit
  • the SMF 105 is a control plane device of the 5G core network, and provides a control plane service for the PDU session of the terminal device; manages the 5G PDU session, manages the 5G quality of service (QoS), and is responsible for allocating IP for the terminal device. Address, responsible for selecting UPF for the terminal device.
  • QoS quality of service
  • the PCF 106 is a 5G core network device and is responsible for generating a policy for the user to establish a QoS flow.
  • the UDM107 is a 5G core network device and is used to store user subscription data.
  • FIG. 2 it is a hardware structure diagram of each device provided by an embodiment of the present application.
  • the terminal device 100 includes at least one processor 1001, at least one memory 1002, and at least one transceiver 1003. Optionally, the terminal device 100 may further include an output device 1004 and an input device 1005. The terminal device 100 is configured to perform the functions of the terminal device described in the following method embodiments.
  • the processor 1001, the memory 1002, and the transceiver 1003 are connected by a bus.
  • the processor 1001 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or a field-programmable gate array (FPGA). , Complex Programmable Logic Device (CPLD), or one or more integrated circuits for controlling the execution of the program of the present application.
  • the processor 1001 may also be a plurality of processors, each of which may be a single-CPU processor or a multi-core processor.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • the memory 1002 may be a Read-Only Memory (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM), or other types that can store information and instructions.
  • the dynamic storage device can also be an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this.
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • CD-ROM Compact Disc Read-Only Memory
  • CD-ROM Compact Disc Read-Only Memory
  • disc storage device including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.
  • the memory 1002 may be independent and connected to the processor 1001 via a bus.
  • the memory 1002 can also be integrated with the processor 1001.
  • the memory 1002 is configured to store application code for executing the solution of the present application, and is controlled by the processor 4001 for execution.
  • the processor 4001 is configured to execute computer program code stored in the memory 4003 to implement the method described in the embodiments of the present application.
  • the transceiver 1003 can use devices such as any transceiver for communicating with other devices or communication networks, such as Ethernet, RAN nodes, Wireless Local Area Networks (WLAN), and the like.
  • the transceiver 1003 includes a transmitter Tx and a receiver Rx.
  • Output device 1004 is in communication with processor 4001 and can display information in a variety of ways.
  • the output device 104 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. Wait.
  • Input device 1005 is in communication with processor 1001 and can accept user input in a variety of ways.
  • the input device 1005 can be a mouse, a keyboard, a touch screen device, or a sensing device, and the like.
  • the RAN node 200 (RAN 102) comprises: at least one processor 2001, at least one memory 2002, at least one transceiver 2003 and at least one network interface 2004, at least one processor 2001, at least one memory 2002, at least one transceiver 2003 and at least A network interface 2004 is connected by a bus.
  • the network interface 2004 is for connecting to the network interface 3004 of the core network device 300 via a link (e.g., an S1 interface), or to a network interface 2004 of other RAN nodes via a wired or wireless link (e.g., an X2 interface).
  • the transceiver 2003 is for communication with the terminal device 100.
  • the functions of the remaining devices of the RAN node 200 are described with reference to the functions of the devices of the terminal device 100, and details are not described herein.
  • the RAN node 200 is operative to perform the functions of the target RAN node or the source RAN node described in the various method embodiments below.
  • the core network device 300 can provide further network connections, such as a telephone network and/or a data communication network (e.g., the Internet).
  • the core network device 300 includes at least one processor 3001, at least one memory 3002, and at least one network interface 3004. At least one processor 3001, at least one memory 3002, and at least one network interface 3004 are connected by a bus.
  • the network interface 3004 is for connecting to the network interface 2004 of the RAN node 200 via a link (e.g., an S1 interface) or between the core network devices via a wired or wireless link.
  • the functions of the devices in the core network device 300 are described with reference to the functions of the devices in the terminal device 100, and details are not described herein.
  • the core network device 300 is for performing the functions of the AMF, SMF or UPF described in the various method embodiments described below.
  • the service area referred to in various embodiments of the present application may include an allowed area and a non-allowed area according to the functional area division.
  • the terminal device is allowed to perform service communication, for example, according to the subscription information of the terminal device and the operator, the terminal device may be allowed to initiate any normal service communication; in the disallowed area, the terminal device is not allowed to perform normal service with the network side.
  • the communication for example, does not allow the terminal device and the network side to transmit a Service Request or Session Management signaling, but allows the terminal device or the network side to initiate a Registration Management process.
  • the TAL may be used to indicate a registration area of the terminal device, and the tracking area in the registration area may all belong to the disallowed area, or all belong to the allowed area. That is, the registration area of the terminal device may include one or more tracking areas belonging to the disallowed area, but does not include the tracking area of the allowed area; or the registration area of the terminal device may include one or more tracking areas belonging to the allowed area, but Does not include a tracking area that does not allow areas. Then, when the terminal device moves from the allowed area to the disallowed area, or from the disallowed area to the allowed area, it means that the terminal device moves out of the current registration area, and the terminal device initiates a registration management process.
  • the RAN node when the terminal device is in the RRC inactive state, the RAN node generates a RAN Notification Area (RNA) according to the TAL of the terminal device and sends it to the terminal device, when the terminal device moves away from the RNA at the location, The terminal device initiates an RRC Connection Resume request to the RAN node, and the RAN node allocates new RNA to the terminal device.
  • RNA RAN Notification Area
  • the RNA must be part of the TAL allocated by the core network, wherein the TAL allocated by the core network is sent by the AMF node to the RAN node.
  • the source RAN node mentioned in the embodiments of the present application refers to a RAN node that provides a service for the terminal device before the terminal device leaves the first area, and correspondingly, the target RAN node refers to provide a service for the terminal device when the terminal device moves to the second area.
  • RAN node refers to a RAN node that provides a service for the terminal device before the terminal device leaves the first area, and correspondingly, the target RAN node refers to provide a service for the terminal device when the terminal device moves to the second area.
  • the first area and the second area mentioned in the embodiments of the present application refer to areas respectively belonging to different TAL definitions, for example, the first area may be an allowable area as described above, and the second area is an unallowable area,
  • the application examples are not limited.
  • the conversion of the terminal device to the connection management (CM) idle state mentioned in the embodiments of the present application may be replaced by: changing the terminal device from being in the CM connected state and being in the RRC inactive state to the CM idle state, or will be in
  • the terminal device of any CM state is set to the CM idle state, and may be other conversion or setting process.
  • the embodiment of the present application is not limited, as long as the final state is the CM idle state.
  • An embodiment of the present application provides a communication method, where the method can be applied to a terminal device in an RRC inactive state to move from a first area to a second area, where the first area belongs to a registration area of the terminal device, and the second area does not belong to the terminal.
  • the first area and the second area may both be TAs or cells, and are not limited.
  • the registration area of the terminal device refers to an area defined by the TAL currently stored by the terminal device or a corresponding area.
  • the first area may be an allowable area
  • the second area may be an allowable area.
  • the method includes:
  • the TAL may be obtained from the AMF by using a registration accept message or a UE configuration update command message when the terminal device is located in the first area.
  • the terminal device can detect the TAI of the location by listening to the system information block (SIB) of the air interface. Further, the terminal device determines whether the terminal device moves out of the registration area of the terminal device by determining whether the TAI of the location thereof belongs to the currently stored TAL.
  • SIB system information block
  • the TAI of the location where the terminal device is located refers to the TAI corresponding to the TA to which the terminal device is currently located, or the TAI corresponding to the current location of the terminal device.
  • the TAI of the location where the terminal device is located does not belong to the TAL of the terminal device, it indicates that the terminal device has moved outside the area defined by the TAL, and at this time, the terminal device can perform TAU.
  • the terminal device may store the TAI of the allowed area or the TAI of the allowed area, and therefore, the terminal device may match the TAI of the location where it is located with the TAI of the allowed area, or the terminal device may locate the location thereof.
  • the TAI matches the TAI of the disallowed area to determine whether the end device is in the allowed or disallowed area. This embodiment provides an implementation in which the terminal device determines to be in an allowed or disallowed region.
  • the area corresponding to the TAI where the terminal device is located is an unallowable area
  • the area corresponding to the TAL is an allowed area. This embodiment shows that the terminal device moves from the allowed area to the disallowed area.
  • the terminal device sends a registration request message to the AMF through the target RAN node.
  • the registration request message may be used to request to allocate a TAL for the terminal device or to request to update the TAL for the terminal device.
  • the registration request message may be a registration request message of a mobility update type.
  • the mobile update type refers to an update triggered when the terminal device moves out of the TAL defined area of the terminal device, that is, the terminal device moves out of the area defined by the stored TAL.
  • the AMF receives a registration request message from the target RAN node.
  • the AMF sends an N2 UE context release command (N2 UE context release command) message to the source RAN node.
  • N2 UE context release command N2 UE context release command
  • the source RAN node may also be referred to as an anchor RAN node.
  • the N2 user equipment context release command message is used to request the source RAN node to release the context of the terminal device.
  • the N2 user equipment context release command message includes a release reason, and the release reason may be used to indicate that the terminal device is located in a non-allowed area.
  • This embodiment provides a possible implementation of the cause of the release.
  • the AMF may determine that the terminal device is located in the disallowed area according to the unpermitted area in the context of the terminal device and the TAI of the current location of the terminal device. For example, when the TAI of the location where the terminal device is located belongs to the TAI of the disallowed area, it may be determined that the terminal device is located in the disallowed area.
  • the source RAN node receives an N2 UE context release command message sent by the AMF.
  • the source RAN node deletes the context of the terminal device according to the N2 user equipment context release command message.
  • the source RAN node sends an N2 UE context release complete message to the AMF.
  • the AMF receives the N2 user equipment context release complete message sent by the source RAN node.
  • the AMF sends a registration accept message to the terminal device by using the target RAN node, where the registration accept message includes a TAL allocated for the terminal device.
  • the terminal device receives, by the target RAN node, a registration accept message sent by the AMF.
  • the communication method provided by the embodiment of the present application when the TAI of the terminal device in the RRC inactive state does not belong to the TAL of the terminal device, indicating that the terminal device has moved to the area defined by the TAL of the terminal device, At this time, the terminal device converts to the CM idle state, and the terminal device sends a registration request message to the AMF to request to allocate a TAL to the terminal device at the current location, and the AMF sends an N2 user equipment context release command message to the source RAN node to release the source RAN node storage.
  • the context of the terminal device after receiving the response message of the source RAN node release context, the AMF sends a registration accept message to the terminal device through the target RAN node, where the registration accept message includes the TAL allocated for the terminal device.
  • the foregoing embodiment implements a TAU in which a terminal device in an RRC inactive state performs a mobile trigger.
  • the method further includes steps S121-S123:
  • the AMF receives location information of the terminal device from the target RAN node.
  • the location information of the terminal device may include at least one of the following information: a TAI of the terminal device, a RAN node Cell Global Identifier (CGI) of the terminal device, or identifier information of the target RAN node.
  • a TAI of the terminal device a RAN node Cell Global Identifier (CGI) of the terminal device, or identifier information of the target RAN node.
  • CGI Cell Global Identifier
  • the TAI of the terminal device refers to the TAI corresponding to the TA where the terminal device is located.
  • the location information of the terminal device may be sent to the AMF through a message with the registration request message RAN node in step S102.
  • the target RAN node sends an initial message to the AMF.
  • An initial UE message including the location information of the terminal device and the registration request message in step S102 in the initial user equipment message.
  • the RAN node may separately send the message to the AMF by using two messages. Not limited.
  • the AMF determines that the terminal device is located in the disallowed area according to the location information of the terminal device and the disallowed area in the context of the terminal device.
  • the AMF may match the TAI of the terminal device according to the TAI of the allowed area in the context of the terminal device to determine that the terminal device is located in the allowed area or the disallowed area. Or, the AMF can match the TAI of the terminal device according to the TAI of the disallowed area in the context of the terminal device.
  • the AMF sets the terminal device to the CM idle state.
  • the AMF After the AMF sends the registration accept message to the terminal device, the AMF initiates an access network (AN) node UE context release in the AN. After the process ends, the AMF and the terminal device will connect from the CM. Switch to CM idle state.
  • AN access network
  • the AMF may convert the terminal device in the CM connection state to the CM idle state, or the AMF may convert the terminal device in the RRC inactive state to the CM idle state, which is not limited in this embodiment of the present application.
  • the embodiment described in the steps S121-S123 provides a specific implementation manner in which the AMF performs CM state transition on the terminal device, so that the CM state of the terminal device is the CM idle state.
  • step S122 the method further includes step S131:
  • the AMF sends a PDU session deactivation request message to the SMF, where the PDU session deactivation request message is used to request the SMF to deactivate the PDU session of the terminal device.
  • This embodiment provides a specific implementation manner in which the AMF performs PDU session state transition on the terminal device, so that the PDU session of the terminal device is in a deactivated state.
  • step S122 the method further includes steps S132-S134:
  • the AMF sends the indication information to the SMF.
  • the indication information is used to indicate that the terminal device is located in the disallowed area.
  • the indication information is a non-allowed area indication (e.g., non-allowed area indication).
  • the SMF receives the indication information from the AMF.
  • the SMF triggers a PDU session release process or a PDU session deactivation process of the terminal device according to the local session management (SM) policy and the foregoing indication information.
  • SM local session management
  • the foregoing SM policy may be: specifying that a PDU session corresponding to some NSSAI/DNN is deactivated, or specifying a PDU session release corresponding to some NSSAI/DNN.
  • the embodiments described in the steps S132-S134 provide a specific implementation manner in which the AMF and the SMF perform PDU session state transition on the terminal device, so that the PDU session of the terminal device is in a deactivated state or an idle state.
  • a schematic diagram of a SMF triggering PDU session release procedure includes the steps S201-S205:
  • the SMF sends an N4 Session Release Request message to the UPF, where the message includes the N4 Session ID requested to be released.
  • the UPF sends an N4 Session Release Response message to the SMF to confirm the N4 session release request message, where the N4 session identifier is included in the N4 session release response message.
  • the SMF sends a PDU Session Release Command message to the AMF.
  • the AMF sends a PDU session update session management context (Nsmf_PDUSession_UpdateSMContext) message to the SMF, where the message includes a PDU Session Release Ack message.
  • Nsmf_PDUSession_UpdateSMContext PDU Session Release Ack
  • the SMF sends a PDU session update session management context response (Nsmf_PDUSession_UpdateSMContext response) message to the AMF, so that the AMF releases the context information related to the PDU session.
  • Nsmf_PDUSession_UpdateSMContext response PDU session update session management context response
  • a schematic diagram of a SMF triggering PDU session deactivation process includes the steps S301-S307:
  • the SMF sends an N4 Session Modification Request (N4 Session Modification Request) message to the UPF, where the message is used to release the RAN node tunnel information of the N3 tunnel corresponding to the PDU session.
  • N4 Session Modification Request N4 Session Modification Request
  • the UPF sends an N4 Session Modification Response (N4 Session Modification Response) message to the SMF.
  • N4 Session Modification Response N4 Session Modification Response
  • the SMF sends an N11 message to the AMF.
  • the N11 message includes an N2 session release request message, where the N2 session release request message is used to request release of the RAN node resource related to the PDU session.
  • the AMF sends an N2 PDU Session Request message to the source RAN node, where the message includes an N2 session release request message.
  • the source RAN node and the terminal device perform an AN-specific resource release procedure to release the RAN node resource related to the PDU session.
  • the source RAN node sends an N2 PDU Session Response (N2 PDU Session Response) message to the AMF.
  • N2 PDU Session Response N2 PDU Session Response
  • the AMF sends an N11 message to the SMF, where the message is used to confirm the message in step S303.
  • An embodiment of the present application provides another communication method, which may be applied to a terminal device in an RRC inactive state to move from a first area to a second area, where related descriptions of the first area and the second area may be referred to 3 shown embodiment.
  • the method includes:
  • the terminal device sends an RRC connection resume request message to the target RAN node.
  • the TAI of the location where the terminal device is located, the TAL of the terminal device, and the TAL of the terminal device, and the TAI of the terminal device are not described in the description of the step S101, and details are not described herein.
  • the terminal device can maintain the RRC inactive state.
  • the target RAN node may be located in an unallowed area.
  • the target RAN node receives an RRC connection recovery request message from the terminal device.
  • the target RAN node sends a retrieve UE context request message to the source RAN node.
  • the acquiring user equipment context request message is used to obtain context information of the terminal device.
  • the source RAN node receives the acquire user equipment context request message from the target RAN node.
  • steps S405-S413 are performed when the target RAN node is located in the disallowed area, or steps S414-S422 are performed.
  • the manner of determining whether the target RAN node is located in the disallowed area may include: determining, by the source RAN node, whether the target RAN node is located in the disallowed area according to the information of the locally reserved disallowed area and the location information of the target RAN node.
  • the location information of the target RAN node may include TAI, CGI of the terminal device or identification information of the target RAN node.
  • the foregoing location information may be configured in advance by Operation Management and Maintenance (OAM), or when an X2 interface is established between the RAN nodes, or carried in a user equipment context request.
  • OAM Operation Management and Maintenance
  • the source RAN node sends a retrieve UE context reject message to the target RAN node; or, when the target RAN node is in the disallowed area, the source RAN node goes to the target.
  • the RAN node sends a retrieve UE context response message.
  • the acquiring the user equipment context response message may carry the failure indication information, where the failure indication information may be used to indicate the failure reason of acquiring the context information of the terminal device.
  • the obtaining the user equipment context reject message may carry the reason for the rejection, and the reason for the rejection may be that the terminal device is located in a non-allowed area indication (for example, a non-allowed area indication). At this point, the terminal device is in the local area data network.
  • This embodiment provides one possible specific implementation of the reason for rejection.
  • the source RAN node sends an N2 UE context release request message to the AMF.
  • the N2 user equipment context release request message may be used to trigger the UE context release in the AN.
  • the N2 user equipment context release request message may carry the request release reason, and the request release reason may be that the terminal device is located in the disallowed area, for example, the non-allowed area indication carried in the message is set to 1. This embodiment provides a possible specific implementation of the reason for rejection, the reason for requesting release.
  • steps S405 and S406 have no sequential execution order.
  • the target RAN node When the target RAN node receives the acquire user equipment context reject message from the source RAN node, or when the target RAN node receives the get user equipment context response message from the source RAN node, and obtains the user equipment context response message carrying useful Upon indicating the failure indication information that the context information fails to be obtained, the target RAN node sends an RRC connection resume reject message to the terminal device.
  • the terminal device receives an RRC connection recovery reject message from the target RAN node.
  • the terminal device converts the CM connection state to the CM idle state according to the RRC connection recovery reject message.
  • the terminal device receives the message that the RRC connection cannot be restored, so the terminal device can directly switch from the CM connection state to the CM idle state.
  • steps S407-S409 and S410-S413 have no sequential execution order.
  • the AMF receives an N2 user equipment context release request message from the source RAN node.
  • the AMF sends a PDU session deactivation request message to the SMF, where the PDU session deactivation request message is used to request the SMF to deactivate the PDU session of the terminal device.
  • the AMF sends an N2 UE context release command (N2 UE context release command) message to the source RAN node.
  • steps S411 and S412 have no sequential execution order.
  • the source RAN node receives an N2 UE context release command message from the AMF, and the source RAN node sends an N2 UE context release complete message to the AMF.
  • steps S405-S413 are processes in which the source RAN node refuses to resume the RRC connection
  • steps S414-S422 are processes in which the source RAN node receives the restored RRC connection.
  • the source RAN node sends a Get User Equipment Context Response message to the target RAN node, where the user equipment context response message includes the context information of the terminal device.
  • the target RAN node When the target RAN node receives the context information of the terminal device from the source RAN node, the target RAN node sends an RRC connection recovery message to the terminal device.
  • the RRC connection recovery message may be used to indicate that the RRC connection recovery is successful.
  • the target RAN node when the target RAN node receives the user equipment context response message from the source RAN node, the target RAN node sends an RRC connection recovery message to the terminal device.
  • the target RAN node sends a path switch request message to the AMF, where the path switch request message carries the location information of the terminal device.
  • This message is used to establish an N2 signaling connection between the target RAN node and the AMF.
  • the AMF receives a path switch request message from the target RAN node.
  • the AMF determines, according to the location information of the terminal device, that the TAI where the terminal device is located does not belong to the TAL of the terminal device, and the AMF re-allocates the TAL for the terminal device, and sends the re-allocated TAL to the target RAN node.
  • the AMF may send a path switch response message to the target RAN node, where the path switch response message includes the reassigned TAL.
  • This embodiment provides a possible implementation of the message that the AMF uses to send the reassigned TAL to the target RAN node.
  • the AMF reallocating the TAL for the terminal device may be before the AMF receives the registration request message from the terminal device.
  • the target RAN node receives a path switch response message from the AMF.
  • the target RAN node sends a UE context release message to the source RAN node, where the user equipment context release message is used to indicate that the source RAN node releases the context information of the terminal device.
  • the terminal device sends a registration request message to the AMF.
  • the AMF sends a registration accept message to the terminal device.
  • the registration accept message carries a TAL that is reassigned to the terminal device.
  • a communication method provided by the real-time example of the present application when the TAI of the location where the terminal device in the RRC inactive state is located does not belong to the TAL of the terminal device, indicating that the device has moved to the area defined by the TAL, and the terminal device attempts to restore the RRC first.
  • the connection the source RAN node may reject or accept the request.
  • the source RAN node informs the terminal device through the target RAN node that it refuses to resume the RRC connection, and on the other hand, the target RAN node initiates the N2 release procedure through the AMF.
  • the target RAN node When accepted, the target RAN node notifies the terminal device to accept its request, and then the terminal device initiates a registration request to acquire the TAL of the terminal device from the AMF.
  • the TAU in which the terminal device in the RRC inactive state performs mobile triggering is implemented.
  • the method may further include steps S431 and S432:
  • the target RAN node generates an RNA according to the TAL reallocated for the terminal device.
  • the TAL of the terminal device may be sent by the AMF to the target RAN node.
  • the target RAN node may generate RNA based on the TAL received from the AMF.
  • RNA may be generated by selecting a part or all of the TA in the TAL.
  • the target RAN node sends the RNA to the terminal device.
  • the target RAN node may send the RNA to the terminal device through an RRC message.
  • the RRC message may be an RRC connection release message.
  • steps S431 and S432 provide a specific implementation of how the target RAN node generates RNA for the terminal device such that the terminal device can acquire updated RNA.
  • step S415 when the target RAN node is located in the disallowed area, after the target RAN node according to step S415 receives the context information of the terminal device from the source RAN node, that is, receives at the target RAN node.
  • the method further includes step S433:
  • the target RAN node triggers the UE context release in the AN. After completing the process, the target RAN node deletes the context information of the terminal device.
  • the target RAN node may determine to convert the terminal device to the CM idle state according to the policy, and then trigger the target RAN node to trigger the UE context release in the AN.
  • the foregoing policy may be: when the terminal device is located in the disallowed area, the state of the terminal device cannot be set to the RRC inactive state.
  • This embodiment causes the target RAN node to delete the context of the terminal device.
  • the target RAN node triggering the AN context UE release process may include:
  • S4331 The target RAN node sends an N2 Context Release Request message to the AMF.
  • S4332 The AMF sends an N11 PDU session deactivation Request message to the SMF.
  • S4333 The SMF sends an N4 Session Modification Request message to the UPF.
  • the UPF sends an N4 Session Modification Response (N4 Session Modification Response) message to the SMF.
  • N4 Session Modification Response N4 Session Modification Response
  • S4335 The SMF sends an N11 PDU session deactivation Response message to the AMF.
  • the AMF sends an N2 UE Context Release Request message to the target RAN node.
  • the target RAN node releases the context of the terminal device, and the target RAN node sends an N2 UE Context Release Complete message to the AMF.
  • the method further includes the step S434-S436:
  • the AMF sends indication information (for example, a non-allowed area indication) to the SMF, where the indication information is used to indicate that the terminal device is located in the disallowed area.
  • indication information for example, a non-allowed area indication
  • the indication information may be sent to the SMF through an event exposure service (Namf_EventExposure) provided by the AMF.
  • Namf_EventExposure an event exposure service
  • the SMF receives the indication information from the AMF.
  • the SMF triggers the PDU session release process or the PDU session deactivation process of the terminal device according to the local SM policy and the foregoing indication information.
  • steps S434-S436 correspond to steps S132-S134.
  • steps S434-S436 provide a specific implementation manner in which the AMF and the SMF perform PDU session state transition on the terminal device, so that the PDU session of the terminal device is in a deactivated state or an idle state when the target RAN node is in the disallowed area. .
  • the method further includes Step S437:
  • the AMF triggers the UE context release in the AN.
  • the target RAN releases the context of the UE.
  • the AMF triggering the AN context UE release process may include:
  • AMF sends an N11 PDU session deactivation Request message to the SMF.
  • S4372 The SMF sends an N4 Session Modification Request message to the UPF.
  • N4 Session Modification Response N4 Session Modification Response
  • S4374 The SMF sends an N11 PDU session deactivation Response message to the AMF.
  • the AMF sends an N2 UE Context Release Request message to the target RAN node.
  • S4376 The target RAN node releases the context of the terminal device, and the target RAN node sends an N2 UE Context Release Complete message to the AMF.
  • An embodiment of the present application provides a communication method, where the method can be applied to a terminal device that is in an RRC inactive state from a permitted area to a disallowed area, and when the TAI acquired from the network side does not belong to the TAL of the terminal device, the terminal device Perform TAU.
  • the method includes:
  • the terminal device converts to the CM idle state according to the local policy.
  • the terminal device transitions to the CM idle state because normal service cannot be performed.
  • the local policy may be obtained in the terminal device or obtained by the terminal device from the PCF through the AMF, for example, by using a registration accept message or a UE configuration update command message.
  • step S101 The manner in which the terminal device determines to move to the disallowed area according to the TAI of the location is referred to the description in step S101.
  • the terminal device sends a registration request message of a mobile update type to the AMF by using the target RAN node, where the registration request message is used to request to allocate a TAL for the terminal device.
  • step S102 For details of this step, refer to S102.
  • step S101 For a description of the type of mobile update, refer to the description in step S101, and details are not described herein again.
  • the AMF receives an initial UE message from the target RAN node, where the initial user equipment message includes a registration request message and location information of the terminal device.
  • This step is a combination of the steps S103 and S121.
  • the AMF determines, according to the location information of the terminal device, that the terminal device is located in the disallowed area, and the AMF sets the terminal device to the CM idle state.
  • one of the two implementation manners of performing S505 or performing S506-S508 may be selected.
  • the AMF sends a PDU session deactivation request message to the SMF, where the PDU session deactivation request message is used to request the SMF to deactivate the PDU session of the terminal device.
  • step S131 for a detailed description of this step.
  • This embodiment provides a specific implementation manner in which the AMF performs PDU session state transition on the terminal device, so that the PDU session of the terminal device is in a deactivated state.
  • the AMF sends the indication information to the SMF, where the indication information is used to indicate that the terminal device is located in a non-allowed area indication (eg, a non-allowed area indication).
  • a non-allowed area indication eg, a non-allowed area indication
  • step S132 See step S132 for a detailed description of this step.
  • the SMF receives the indication information from the AMF.
  • step S133 See step S133 for a detailed description of this step.
  • the SMF triggers a PDU session release process or a PDU session deactivation process of the terminal device according to the local session management (SM) policy and the foregoing indication information.
  • SM local session management
  • the embodiments described in the steps S506-S508 provide a specific implementation manner in which the AMF and the SMF perform PDU session state transition on the terminal device, so that the PDU session of the terminal device is in a deactivated state or an idle state.
  • the AMF sends an N2 UE context release command (N2 UE context release command) message to the source RAN node, where the message includes a release reason, and the release reason is that the terminal device is located in a non-allowed area.
  • N2 UE context release command N2 UE context release command
  • the source RAN node receives the N2 user equipment context release command message sent by the AMF, and deletes the context of the terminal device according to the N2 user equipment context release command message.
  • This step is a combination of steps S105 and S106, and details are not described herein again.
  • the source RAN node sends an N2 UE context release complete message to the AMF.
  • step S107 See step S107 for a detailed description of this step.
  • the AMF receives the N2 user equipment context release complete message sent by the source RAN node, and sends a registration accept to the terminal device by using the target RAN node, where the registration accept message includes the reassigned TAL.
  • This step is a combination of steps S108 and S109, and details are not described herein again.
  • the terminal device receives the registration accept message sent by the AMF through the target RAN node.
  • step S110 for a detailed description of this step.
  • the CM status between the terminal device and the network side device is CM idle state through steps S501 and S504, and the PDU session state between the terminal device and the network side device is inactive state through step S508.
  • the communication method provided by the embodiment of the present application when the TAI of the location where the terminal device in the RRC inactive state is located does not belong to the TAL, indicating that the TAI has been moved outside the TAL boundary, and thus the TAU is performed, and the terminal device is converted to the CM idle state.
  • the terminal device sends a registration request message to the AMF to request the TAL of the location, and the AMF sends an N2 User Equipment Context Release Command message to the source RAN node to release the context of the terminal device at the source RAN node, and receive the response of the source RAN node to release the context.
  • the AMF sends a registration accept message to the terminal device, which includes a TAL that is reallocated for the terminal device.
  • the TAU of the mobile device triggered by the terminal device in the RRC inactive state is implemented.
  • the CM state between the terminal device and the network device is CM idle state
  • the PDU session state between the terminal device and the network device is inactive.
  • An embodiment of the present application provides a communication method, where the method can be applied to a terminal device that is in an RRC inactive state and moves from an allowed area to a disallowed area, and the TAI of the location where the terminal device is located does not belong to the TAL of the terminal device, and the terminal The device performs TAU.
  • the method includes:
  • the terminal device sends an RRC connection resume request message to the target RAN node.
  • the target RAN node receives an RRC connection recovery request message from the terminal device, and sends a retrieving UE context request message to the source RAN node, where the acquiring user equipment context request message is used to obtain context information of the terminal device.
  • the step is the combination of the steps S402 and S403, and details are not described herein again.
  • the source RAN node receives the user equipment context request message from the target RAN node, and sends a user equipment context response message to the target RAN node, where the user equipment context response message includes context information of the terminal device.
  • This step is a combination of steps S404 and S414, and details are not described herein again.
  • the target RAN node When the target RAN node receives the context information of the terminal device from the source RAN node, the target RAN node sends an RRC connection recovery message to the terminal device to indicate that the RRC connection recovery is successful.
  • the target RAN node sends a path switch request message to the AMF, where the path switch request message carries the location information of the terminal device.
  • the AMF receives a path switch request message from the target RAN node, and determines, according to the location information of the terminal device in the path switch request message, that the TAI of the location where the terminal device is located does not belong to the TAL of the terminal device, and the AMF re-allocates the TAL for the terminal device, and Sending a path switch response message to the target RAN node, where the path switch response message includes the reassigned TAL.
  • This step is a combination of steps S417 and S418, and details are not described herein again.
  • the target RAN node receives a path switch response message from the AMF, and sends a UE context release message to the source RAN node, where the user equipment context release message indicates that the source RAN node releases the context information of the terminal device.
  • This step is a combination of steps S419 and S420, and details are not described herein again.
  • the AMF sends a UE mobility notification message to the SMF, where the message includes indication information, where the indication information is used to indicate that the terminal device is located in the disallowed area (for example, Non-allowed area indication).
  • the SMF receives the indication information from the AMF, and triggers the PDU session release process or the PDU session deactivation process of the terminal device according to the local SM policy and the foregoing indication information.
  • This step is a combination of steps S435 and S436, and details are not described herein again.
  • the PDU session state between the terminal device and the SMF is in an inactive state by step S609.
  • the terminal device sends a registration request message to the AMF.
  • the AMF sends a registration accept message to the terminal device.
  • the registration accept message carries a TAL that is reassigned to the terminal device.
  • the terminal device when the TAI of the location where the terminal device in the RRC inactive state is located does not belong to the TAL of the terminal device, the terminal device initiates a RAN-level registration update to the target RAN node (RAN-level-registration). -update) process.
  • the target RAN node successfully acquires the context of the user equipment from the source RAN node, and restores the RRC connection state.
  • the target RAN node initiates a path switching procedure to the AMF, and sends the re-allocated TAL to the terminal device through the process.
  • a TAU in which the terminal device in the RRC inactive state performs mobile triggering is implemented.
  • the AMF learned that the terminal device entered the disallowed area.
  • An implementation manner may be adopted, that is, the AMF keeps the CM state of the terminal device in the CM connection state, and notifies the SMF of the event that the terminal device enters the disallowed area, and the SMF decides to release/disrelease the PDU session or deactivate the PDU session.
  • the RAN node maintains the terminal equipment in an RRC inactive state.
  • another implementation manner may be adopted, that is, the AMF keeps the CM state of the terminal device in the CM connection state, and notifies the SMF of the event that the terminal device enters the disallowed area, and the SMF decides to release/disrelease the PDU session or deactivate the PDU session.
  • the target RAN node initiates an N2 release procedure according to the policy or the AMF according to the policy, and converts the terminal device into a CM idle state.
  • step S621 after the AMF described in step S606 sends a TAL to the target RAN node, the method may further include step S621:
  • the target RAN node generates an RRC connection release message according to the TAL generated from the AMF, and sends an RRC connection release message to the terminal device, where the RRC connection release message includes an RNA.
  • This step is a combination of S431 and S432, and details are not described herein again.
  • the CM state between the terminal device and the AMF is maintained in the CM connection state in step S621, and the RRC state between the terminal device and the target RAN node is RRC inactive state through step S621.
  • This embodiment provides a possible implementation of the message that the target RAN uses to transmit the RAN to the terminal device.
  • the method may further include step S622:
  • the target RAN node determines to convert the terminal device to the CM idle state according to the policy, and the target RAN node triggers the UE context release in the AN.
  • step S433 For details of this step, refer to S433.
  • the process of triggering the N2 context release is described with reference to step S433, and details are not described herein.
  • the CM state between the terminal device and the target RAN node is CM connected state through step S622.
  • This embodiment causes the target RAN node to delete the context of the terminal device.
  • the method may further include step S612:
  • the AMF determines to convert the terminal device to the CM idle state according to the policy, and triggers the UE context release in the AN.
  • the CM state between the terminal device and the AMF is made CM idle state by S623.
  • the target RAN releases the context of the UE.
  • An embodiment of the present application provides a communication method, where the method can be applied to a terminal device that is in an RRC inactive state and moves from an allowed area to a disallowed area, and the TAI of the terminal device does not belong to the TAL of the terminal device, and the terminal device performs TAU.
  • the method includes:
  • the terminal device sends an RRC connection resume request message to the target RAN node.
  • step S601 This step is the same as step S601, and details are not described herein again.
  • the target RAN node receives an RRC connection recovery request message from the terminal device, and sends a retrieving UE context request message to the source RAN node, where the acquiring user equipment context request message is used to obtain context information of the terminal device.
  • the source RAN node receives the acquiring user equipment context request message from the target RAN node, and determines that the target RAN node is located in the disallowed area according to the locally saved information of the disallowed area and the location information of the target RAN node, and then determines the rejection request.
  • step S404 See step S404 for a detailed description of this step.
  • the source RAN node sends a retrieve UE context reject message to the target RAN node, where the retrieving user equipment context reject message carries a reject reason, and the reject reason is that the terminal device is located in the disallowed area (for example, non- Allowed area indication).
  • N2 UE context release request N2 UE context release request
  • AMF Access Management Function
  • N2 UE context release request message to the AMF to initiate an N2 release process, where the message carries a request release reason, and the request release reason is that the terminal device is located in the disallowed area (for example, , non-allowed area indication).
  • the target RAN node When the target RAN node receives the acquire user equipment context reject message from the source RAN node, the target RAN node sends an RRC connection resume reiect message to the terminal device.
  • the terminal device receives an RRC connection recovery reject message from the target RAN node, and converts from the CM connection state to the CM idle state according to the RRC connection recovery reject message.
  • This step is a combination of steps S408 and S409, and details are not described herein again.
  • the AMF receives an N2 user equipment context release request message from the source RAN node, and sends a PDU session deactivation request message to the SMF, where the PDU session deactivation request message is used to request the SMF to deactivate the PDU session of the terminal device.
  • This step is a combination of steps S410 and S411.
  • the AMF sends an N2 UE context release command (N2 UE context release command) message to the source RAN node.
  • N2 UE context release command N2 UE context release command
  • step S412 See step S412 for a detailed description of this step.
  • the source RAN node receives an N2 UE context release command message from the AMF, and the source RAN node sends an N2 UE context release complete message to the AMF.
  • step S413 See step S413 for a detailed description of this step.
  • the terminal device when the TAI of the location where the terminal device in the RRC inactive state is located does not belong to the TAL of the terminal device, the terminal device initiates a registration update of the RAN node level to the target RAN node (RAN node-level -registration-update) process.
  • the target RAN node requests to acquire the context of the user equipment from the source RAN node, and the source RAN node discovers that the terminal device enters the disallowed area, and rejects the request of the target RAN node.
  • An implementation may be adopted in which the source RAN node denies the terminal device access to the network, thereby causing the terminal device to enter the CM idle state, and the PDU session of the terminal device is in an inactive state.
  • the source RAN node initiates an N2 release procedure to release the N2 and N3 connections between the source RAN node and the AMF/UPF, convert the terminal device to the CM idle state, and the PDU session of the terminal device. Inactive state.
  • the embodiment of the present application provides a terminal device for performing the foregoing communication method.
  • 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. It should be noted that the division of the module in the embodiment of the present application is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 19 is a schematic diagram showing a possible structure of a terminal device involved in the foregoing embodiment.
  • the terminal device 100 includes: a receiving unit 1011, a converting unit 1012, and a sending unit. 1013.
  • the receiving unit 1011 is configured to support the terminal device 100 to perform the process S110 in FIG. 3, the process S110 in FIG. 4, the process S110 in FIG. 5, the process S110 in FIG. 6, the process S305 in FIG. 8, and the process in FIG. S408, the process S408 in FIG. 10, the process S408 in FIG. 12, the process S408 in FIG. 13, the process S513 in FIG. 15, the conversion unit 1012 is configured to support the terminal device 100 to execute the process S101 in FIG. Process S101, process S101 in FIG.
  • the transmitting unit 1013 is configured to support the terminal device 100 to perform the process S102 in FIG. 3, the process S102 in FIG. 4, the process S102 in FIG. 5, the process S102 in FIG. 6, FIG. Process S305, process S401, S413 and S421 in Fig. 9, processes S401, S413 and S421 in Fig. 10, processes S401, S413 and S421 in Fig. 12, processes S401, S413 and S421 in Fig. 13, Process S502 in FIG. 15, processes S601 and S610 in FIG.
  • Fig. 20 shows a possible structural diagram of the terminal device involved in the above embodiment.
  • the terminal device 100 includes a processing module 1022 and a communication module 1023.
  • the processing module 1022 is configured to perform control management on the action of the terminal device 100.
  • the processing module 1022 is configured to support the terminal device 100 to perform the process S101 in FIG. 3, the process S101 in FIG. 4, and the process S101 in FIG.
  • Communication module 1023 is used to support communication of the terminal device with other entities, such as with the functional modules or network entities shown in FIG.
  • the terminal device 100 may further include a storage module 1021 for storing program codes and data of the terminal device.
  • the processing module 1022 can be a processor or a controller, and can be, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (Application-Specific). Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be 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 communication module 1023 may be a transceiver, a transceiver circuit, a communication interface, or the like.
  • the storage module 1021 can be a memory.
  • the processing module 1022 can be the processor 1001 in FIG. 2
  • the communication module 1023 can be the transceiver 1003 in FIG. 2
  • the storage module 1021 can be the memory 1002 in FIG.
  • the embodiment of the present application provides a RAN node, which is used to perform the foregoing communication method.
  • the embodiment of the present application may perform the division of the function module on the RAN node 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. It should be noted that the division of the module in the embodiment of the present application is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 21 is a schematic diagram showing a possible structure of a RAN node involved in the foregoing embodiment, where the RAN node 200 includes: a receiving unit 2011, a generating unit 2012, and a deleting unit. 2013, release unit 2014, and transmission unit 2015.
  • the receiving unit 2011 is configured to support the RAN node 200 to perform the process S105 in FIG. 3, the process S105 in FIG. 4, the process S105 in FIG. 5, the process S105 in FIG. 6, the process S305 in FIG. 8, and the process in FIG. S402, S404, S419, processes S402, S404, S419 in FIG. 10, processes S402, S404, S419 in FIG. 12, processes S402, S404, S419 in FIG. 13, process S513 in FIG.
  • the supporting RAN node 200 performs the process S431 in FIG. 10, the process S621 in FIG. 17; the deleting unit 2013 is for supporting the RAN node 200 to perform the process S106 in FIG. 3, the process S106 in FIG. 4, the process S106 in FIG. Process S106 in FIG. 6, process S510 in FIG. 15; release unit 2014 is used to support RAN node 200 to perform process S4337 in FIG. 11, process S4376 in FIG. 14; and transmitting unit 2013 is configured to support RAN node 200 to execute map Process S107 in 3, process S107 in FIG. 4, process S107 in FIG. 5, process S107 in FIG. 6, processes S305 and S306 in FIG. 8, processes S403, S406, S407, S414, S415 in FIG.
  • FIG. 22 shows a possible structural diagram of the RAN node involved in the above embodiment.
  • the RAN node 200 includes a processing module 2022 and a communication module 2023.
  • the processing module 2022 is configured to perform control management on the action of the RAN node 200.
  • the processing module 2022 is configured to support the RAN node 200 to perform the process S431 in FIG. 10, the process S621 in FIG. 17, and the process S106 in FIG.
  • Communication module 1023 is for supporting communication between the RAN node and other entities, such as with the functional modules or network entities shown in FIG.
  • the RAN node 200 can also include a storage module 2021 for storing program code and data of the RAN node.
  • the processing module 2022 may be a processor or a controller, and may be, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (Application-Specific). Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be 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 communication module 2023 may be a transceiver, a transceiver circuit, a communication interface, or the like.
  • the storage module 2021 can be a memory.
  • the processing module 2022 may be the processor 2001 in FIG. 2
  • the communication module 2023 may be the transceiver 2003 or the network interface 2004 in FIG. 2
  • the storage module 2021 may be the memory 2002 in FIG.
  • the embodiment of the present application provides an AMF for performing the foregoing communication method.
  • the embodiment of the present application may divide the function module into the AMF 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. It should be noted that the division of the module in the embodiment of the present application is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 23 is a schematic diagram showing a possible structure of the AMF involved in the foregoing embodiment.
  • the AMF 400 includes: a receiving unit 4011, a determining unit 4012, and a setting unit 4013. Transmitting unit 4014.
  • the receiving unit 4011 is configured to support the AMF 400 to perform the processes S103 and S108 in FIG. 3, the processes S103, S121 and S108 in FIG. 4, the processes S103, S121 and S108 in FIG. 5, and the processes S103, S121 and S108 in FIG. Processes S410 and S417 in FIG. 9, processes S410 and S417 in FIG. 10, processes S410 and S417 in FIG. 12, processes S410 and S417 in FIG. 13, processes S503 and S512 in FIG.
  • the process S122 in FIG. 4 is performed in support of the AMF 400, the process S122 in FIG. 5, the process S122 in FIG. 6, the process S418 in FIG. 9, the process S504 in FIG. 15, the process S606 in FIG. 16, and FIG. Process S606; the setting unit 4013 is configured to support the AMF 400 to perform the process S123 in FIG. 4, the process S123 in FIG. 5, the process S123 in FIG. 6, and the transmitting unit 4013 is configured to support the AMF 400 to execute the process S104 in FIG. Process S104 in FIG. 4, processes S104 and S131 in FIG. 5, processes S104 and S132 in FIG. 6, process S204 in FIG. 7, processes S304 and S307 in FIG.
  • Fig. 24 shows a possible structural diagram of the AMF involved in the above embodiment.
  • the AMF 400 includes a processing module 4022 and a communication module 4023.
  • the processing module 4022 is configured to control and manage the actions of the AMF 400.
  • the processing module 4022 is configured to support the AMF 400 to perform the process S122 in FIG. 4, the process S122 in FIG. 5, the process S122 in FIG. 6, and the process in FIG. Process S418, process S504 in Fig. 15, process S606 in Fig. 16, process S606 in Fig. 17, process S123 in Fig. 4, process S123 in Fig. 5, and process S123 in Fig. 6.
  • Communication module 1023 is used to support communication of AMFs with other entities, such as with the functional modules or network entities shown in FIG.
  • the AMF 400 may also include a storage module 4021 for storing program codes and data of the AMF.
  • the processing module 4022 can be a processor or a controller, and can be, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (Application-Specific). Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be 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 communication module 4023 may be a transceiver circuit or a communication interface or the like.
  • the storage module 4021 can be a memory.
  • the processing module 4022 can be the processor 3001 in FIG. 2
  • the communication module 4023 can be the network interface 3003 in FIG. 2
  • the storage module 4021 can be the memory 3002 in FIG.
  • An embodiment of the present application provides an SMF for performing the foregoing communication method.
  • the embodiment of the present application may perform the division of the function module on the SMF 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. It should be noted that the division of the module in the embodiment of the present application is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 25 shows a possible structural diagram of the SMF involved in the foregoing embodiment
  • the SMF 500 includes a receiving unit 5011 and a transmitting unit 5012.
  • the receiving unit 5011 is configured to support the SMF 500 to perform the process S133 in FIG. 6, the process S435 in FIG. 12, the process S507 in FIG. 15, and the transmitting unit 5012 is configured to support the SMF 500 to execute the process S134 in FIG. 6, in FIG. Processes S201, S203, S205, processes S301, S303 in FIG. 8, process S436 in FIG. 12, processes S4372, S4374 in FIG. 14, process S508 in FIG. 15, process S609 in FIG. 16, and FIG. Process S609. 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.
  • Fig. 26 shows a possible structural diagram of the SMF involved in the above embodiment.
  • the SMF 500 includes a processing module 5022 and a communication module 5023.
  • the processing module 5022 is configured to control and manage the actions of the SMF 500.
  • Communication module 1023 is used to support communication of the SMF with other entities, such as with the functional modules or network entities shown in FIG.
  • the SMF 500 can also include a storage module 5021 for storing program code and data of the SMF.
  • the processing module 5022 may be a processor or a controller, such as a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (Application-Specific). Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be 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 communication module 5023 may be a transceiver circuit or a communication interface or the like.
  • the storage module 5021 can be a memory.
  • the processing module 5022 can be the processor 3001 in FIG. 2
  • the communication module 5023 can be the network interface 3003 in FIG. 2
  • the storage module 5021 can be the memory 3002 in FIG.
  • the size of the sequence numbers of the foregoing processes does not mean the order of execution sequence, and the order of execution of each process should be determined by its function and internal logic, and should not be applied to the embodiment of the present application.
  • the implementation process constitutes any limitation.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or 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 electrical, mechanical or otherwise.
  • 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 embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • a software program it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device that includes one or more servers, data centers, etc. that can be integrated with the media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a Solid State Disk (SSD)) or the like.
  • a magnetic medium eg, a floppy disk, a hard disk, a magnetic tape
  • an optical medium eg, a DVD
  • a semiconductor medium such as a Solid State Disk (SSD)

Abstract

本申请公开了一种通信方法、装置和系统，涉及通信领域，用于实现处于RRC非激活态的终端设备进行移动触发的TAU。该方法包括：当处于无线资源控制RRC非激活态的终端设备所处位置的TAI不属于终端设备的跟踪区列表TAL时，终端设备转换为连接管理CM空闲态；终端设备通过目标无线接入网络RAN节点向接入和移动性管理功能AMF发送注册请求消息，注册请求消息用于请求为终端设备分配TAL；终端设备通过目标RAN节点接收由AMF发送的注册接受消息，注册接受消息中包括分配的TAL。本申请实施例应用于终端设备在注册区之间移动。

Description

通信方法、装置和系统
本申请要求于2017年8月15日提交中国专利局、申请号为201710699045.6、申请名称为“通信方法、装置和系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种通信方法、装置和系统。
背景技术
5代(5th Generation，5G)规范定义了无线资源控制(Radio Resource Control，RRC)非激活态(RRC-inactive state)，该状态是终端设备的一种RRC状态(state)。在RRC-inactive state状态下：终端设备与无线接入网络(Radio Access Network，RAN)节点之间的RRC连接已经被释放，但RAN节点与核心网(Core Network，CN)节点之间保持连接。
为了便于进行位置管理，在长期演进(Long Term Evolution，LTE)中引入跟踪区(Tracking Area，TA)和跟踪区列表(Tracking Area List，TAL)的概念。TA用于指示终端设备所处区域的位置，每个TA可以用跟踪区标识(Tracking Area Identity，TAI)来表示。TAL用于指示终端设备的注册区，TAL中包含了一个或多个TA的TAI。终端设备在同一TAL所限定的区域中进行移动时，不必进行跟踪区更新(Tracking Area Update，TAU)，仅当移动至TAL所限定区域之外时才进行TAU，因此可以避免在TA边界处由于乒乓效应导致频繁更新TA。
现有5G规范中，处于空闲态和连接态的终端设备可以通过周期性TAU或移动触发的TAU来更新TAL，其中，移动触发的TAU指终端设备在移出TAL对应的区域之外时，由于所处位置的TAI不属于终端设备已分配的TAL而导致的TAU。但是对于处于RRC非激活态的终端设备如何进行移动触发的TAU，以及RAN节点和CN节点具体如何进行该流程，5G规范并没有给出说明。
发明内容
本申请的实施例提供一种通信方法、装置和系统，用于实现处于RRC非激活态的终端设备进行移动触发的TAU。
为达到上述目的，本申请的实施例采用如下技术方案：
第一方面，本申请实施例提供了一种通信方法，该方法包括：当处于无线资源控制RRC非激活态的终端设备所处位置的TAI不属于终端设备的跟踪区列表TAL时，终端设备转换为连接管理CM空闲态；终端设备通过目标无线接入网络RAN节点向接入和移动性管理功能AMF发送注册请求消息，注册请求消息用于请求为终端设备分配TAL；终端设备通过目标RAN节点接收由AMF发送的注册接受消息，注册接受消息中包括分配的TAL。本申请实施例提供的通信方法，当处于RRC非激活态的终端设备所处位置的TAI不属于该终端设备的TAL时，表明该终端设备已经移动至该终端设备的TAL所限定的区域外，此时终端设备转换为CM空闲态，终端设备向AMF发 送注册请求消息以请求为处于当前位置的终端设备分配TAL，AMF向源RAN节点发送N2用户设备上下文释放命令消息以释放源RAN节点存储的终端设备的上下文，接收到源RAN节点释放上下文的响应消息之后，AMF通过目标RAN节点向终端设备发送注册接受消息，该注册接受消息中包括为终端设备分配的TAL。上述实施例实现了处于RRC非激活态的终端设备进行移动触发的TAU。
在一种实施场景下，终端设备所处位置的TAI对应的区域为不允许区域，跟踪区列表TAL对应的区域为允许区域。该实施方式表明终端设备从允许区域移动至不允许区域。
第二方面，本申请实施例提供了一种终端设备，该终端设备包括：转换单元，用于当处于无线资源控制RRC非激活态的终端设备所处位置的TAI不属于终端设备的跟踪区列表TAL时，将终端设备转换为连接管理CM空闲态；发送单元，用于通过目标无线接入网络RAN节点向接入和移动性管理功能AMF发送注册请求消息，注册请求消息用于请求为终端设备分配TAL；接收单元，用于通过目标RAN节点接收由AMF发送的注册接受消息，注册接受消息中包括分配的TAL。基于同一发明构思，由于该终端设备解决问题的原理以及有益效果可以参见上述第一方面和第一方面的各可能的方法实施方式以及所带来的有益效果，因此该终端设备的实施可以参见上述第一方面和第一方面的各可能的方法的实施方式，重复之处不再赘述。
第三方面，本申请实施例提供了一种通信方法，该方法包括：接入和移动性管理功能AMF从目标无线接入网络RAN节点接收注册请求消息，注册请求消息用于请求为终端设备分配跟踪区列表TAL，终端设备处于无线资源控制RRC非激活态；AMF向源RAN节点发送N2用户设备上下文释放命令消息；AMF接收由源RAN节点发送的N2用户设备上下文释放完成消息；AMF通过目标RAN节点向终端设备发送注册接受消息，注册接受消息中包括TAL。本申请实施例提供的通信方法，当处于RRC非激活态的终端设备所处位置的TAI不属于该终端设备的TAL时，表明该终端设备已经移动至该终端设备的TAL所限定的区域外，此时终端设备转换为CM空闲态，终端设备向AMF发送注册请求消息以请求为处于当前位置的终端设备分配TAL，AMF向源RAN节点发送N2用户设备上下文释放命令消息以释放源RAN节点存储的终端设备的上下文，接收到源RAN节点释放上下文的响应消息之后，AMF通过目标RAN节点向终端设备发送注册接受消息，该注册接受消息中包括为终端设备分配的TAL。上述实施例实现了处于RRC非激活态的终端设备进行移动触发的TAU。
在一种实施场景下，该方法还包括：AMF从目标RAN节点接收终端设备的位置信息；AMF根据终端设备的位置信息以及终端设备的上下文中的不允许区域，确定终端设备位于不允许区域；AMF将终端设备设置为连接管理CM空闲态。该实施方式，提供了AMF对终端设备进行CM状态转换的一种具体实现方式，使得终端设备的CM状态为CM空闲态。
在一种实施场景下，该方法还包括：AMF向会话管理功能SMF发送分组数据单元PDU会话去激活请求消息，PDU会话去激活请求消息用于请求SMF去激活终端设备的PDU会话；或者，AMF向SMF发送指示信息，其中，指示信息用于指示终端设备位于不允许区域。该实施方式提供了AMF和SMF对终端设备进行PDU会话状态转 换的一种具体实现方式，使得终端设备的PDU会话处于去激活态或空闲态。
在一种实施场景下，N2用户设备上下文释放命令消息中包括释放原因，释放原因用于指示终端设备位于不允许区域。该实施方式提供了释放原因的一种可能的实现形式。
第四方面，本申请实施例提供了一种接入和移动性管理功能AMF，该AMF包括：接收单元，用于从目标无线接入网络RAN节点接收注册请求消息，注册请求消息用于请求为终端设备分配跟踪区列表TAL，终端设备处于无线资源控制RRC非激活态；发送单元，用于向源RAN节点发送N2用户设备上下文释放命令消息；接收单元，用于接收由源RAN节点发送的N2用户设备上下文释放完成消息；发送单元，还用于通过目标RAN节点向终端设备发送注册接受消息，注册接受消息中包括TAL。基于同一发明构思，由于该AMF解决问题的原理以及有益效果可以参见上述第三方面和第三方面的各可能的方法实施方式以及所带来的有益效果，因此该AMF的实施可以参见上述第三方面和第三方面的各可能的方法的实施方式，重复之处不再赘述。
第五方面，本申请实施例提供了一种通信方法，该方法包括：会话管理功能SMF从接入和移动性管理功能AMF接收指示信息，指示信息用于指示终端设备位于不允许区域；SMF根据本地会话管理SM策略以及指示信息，触发终端设备的PDU会话释放流程或PDU会话去激活流程。该实施方式提供了AMF和SMF对终端设备进行PDU会话状态转换的一种具体实现方式，使得终端设备的PDU会话处于去激活态或空闲态。
第六方面，本申请实施例提供了一种会话管理功能SMF，该SMF包括：接收单元，用于从接入和移动性管理功能AMF接收指示信息，指示信息用于指示终端设备位于不允许区域；发送单元，用于根据本地会话管理SM策略以及指示信息，触发终端设备的PDU会话释放流程或PDU会话去激活流程。基于同一发明构思，由于该SMF解决问题的原理以及有益效果可以参见上述第五方面和第五方面的各可能的方法实施方式以及所带来的有益效果，因此该SMF的实施可以参见上述第五方面和第五方面的各可能的方法的实施方式，重复之处不再赘述。
第七方面，本申请实施例提供了一种通信方法，该方法包括：当处于无线资源控制RRC非激活态的终端设备所处位置的TAI不属于终端设备的跟踪区列表TAL时，终端设备向目标无线接入网络RAN节点发送无线资源控制RRC连接恢复请求消息，终端设备处于RRC非激活态；终端设备从目标RAN节点接收RRC连接恢复拒绝消息；终端设备根据RRC连接恢复拒绝消息，从连接管理CM连接态转换为CM空闲态。本申请实话例提供的一种通信方法，当处于RRC非激活态的终端设备所处位置的TAI不属于终端设备的TAL时，表明已经移动至TAL所限定的区域外，终端设备先尝试恢复RRC连接，源RAN节点可能拒绝或接受该请求。当拒绝时，一方面，源RAN节点通过目标RAN节点通知终端设备拒绝其恢复RRC连接，另一方面，目标RAN节点通过AMF发起N2释放流程。当接受时，目标RAN节点通知终端设备接受其请求，然后由终端设备发起注册请求从AMF获取该终端设备的TAL。以上处理方式，实现了处于RRC非激活态的终端设备进行移动触发的TAU。
在一种实施场景下，目标RAN节点位于不允许区域。该实施方式提供了目标RAN 节点可能所在的区域。
第八方面，本申请实施例提供了一种终端设备，该终端设备包括：发送单元，用于当处于无线资源控制RRC非激活态的终端设备所处位置的TAI不属于终端设备的跟踪区列表TAL时，向目标无线接入网络RAN节点发送无线资源控制RRC连接恢复请求消息，终端设备处于RRC非激活态；接收单元，用于从目标RAN节点接收RRC连接恢复拒绝消息；转换单元，用于根据RRC连接恢复拒绝消息，从连接管理CM连接态转换为CM空闲态。基于同一发明构思，由于该终端设备解决问题的原理以及有益效果可以参见上述第七方面和第七方面的各可能的方法实施方式以及所带来的有益效果，因此该终端设备的实施可以参见上述第七方面和第七方面的各可能的方法的实施方式，重复之处不再赘述。
第九方面，本申请实施例提供了一种通信方法，该方法包括：目标无线接入网络RAN节点从终端设备接收无线资源控制RRC连接恢复请求消息，终端设备处于RRC非激活态；目标RAN节点向源RAN节点发送获取用户设备上下文请求消息，获取用户设备上下文请求消息用于获取终端设备的上下文信息；当目标RAN节点接收到来自源RAN节点的终端设备的上下文信息时，目标RAN节点向终端设备发送RRC连接恢复消息，向接入和移动性管理功能AMF发送路径切换请求消息，从AMF接收路径切换响应消息，并向源RAN节点发送用户设备上下文释放消息；或者，当目标RAN节点接收到来自源RAN节点的获取用户设备上下文拒绝消息时，或者，当目标RAN节点接收到来自源RAN节点的获取用户设备上下文响应消息，并且获取用户设备上下文响应消息携带有用于指示获取上下文信息失败的失败指示信息时，目标RAN节点向终端设备发送RRC连接恢复拒绝消息。本申请实话例提供的一种通信方法，当处于RRC非激活态的终端设备所处位置的TAI不属于终端设备的TAL时，表明已经移动至TAL所限定的区域外，终端设备先尝试恢复RRC连接，源RAN节点可能拒绝或接受该请求。当拒绝时，一方面，源RAN节点通过目标RAN节点通知终端设备拒绝其恢复RRC连接，另一方面，目标RAN节点通过AMF发起N2释放流程。当接受时，目标RAN节点通知终端设备接受其请求，然后由终端设备发起注册请求从AMF获取该终端设备的TAL。以上处理方式，实现了处于RRC非激活态的终端设备进行移动触发的TAU。
在一种实施场景下，路径切换响应消息中包括为终端设备重新分配的跟踪区列表TAL，该方法还包括：目标RAN节点根据TAL生成RAN通知区域RNA；目标RAN节点向终端设备发送RNA。该实施方式提供了目标RAN节点如何为终端设备生成RNA的一种具体实现方式，使得终端设备可以获取更新的RNA。
在一种实施场景下，目标RAN节点位于不允许区域，在目标RAN节点接收到来自源RAN节点的终端设备的上下文信息之后，该方法还包括：目标RAN节点触发接入网络AN节点用户设备上下文释放流程；目标RAN节点删除终端设备的上下文信息。该实施方式使得目标RAN节点删除终端设备的上下文。
第十方面，本申请实施例提供了一种目标无线接入网络RAN节点，该目标RAN节点包括：接收单元，用于从终端设备接收无线资源控制RRC连接恢复请求消息，终端设备处于RRC非激活态；发送单元，用于向源RAN节点发送获取用户设备上下文 请求消息，获取用户设备上下文请求消息用于获取终端设备的上下文信息；当目标RAN节点接收到来自源RAN节点的终端设备的上下文信息时，发送单元，还用于向终端设备发送RRC连接恢复消息，向接入和移动性管理功能AMF发送路径切换请求消息，接收单元，还用于从AMF接收路径切换响应消息，发送单元，还用于向源RAN节点发送用户设备上下文释放消息；或者，当目标RAN节点接收到来自源RAN节点的获取用户设备上下文拒绝消息时，或者，当目标RAN节点接收到来自源RAN节点的获取用户设备上下文响应消息，并且获取用户设备上下文响应消息携带有用于指示获取上下文信息失败的失败指示信息时，发送单元，还用于向终端设备发送RRC连接恢复拒绝消息。基于同一发明构思，由于该目标RAN节点解决问题的原理以及有益效果可以参见上述第九方面和第九方面的各可能的方法实施方式以及所带来的有益效果，因此该目标RAN节点的实施可以参见上述第九方面和第九方面的各可能的方法的实施方式，重复之处不再赘述。
第十一方面，本申请实施例提供了一种通信方法，该方法包括：接入和移动性管理功能AMF从目标无线接入网络RAN节点接收路径切换请求消息，路径切换请求消息中携带终端设备的位置信息；AMF根据终端设备的位置信息，确定终端设备所处位置的TAI不属于终端设备的跟踪区列表TAL；AMF为终端设备重新分配TAL，并向目标RAN节点发送重新分配的TAL。本申请实话例提供的一种通信方法，当处于RRC非激活态的终端设备所处位置的TAI不属于终端设备的TAL时，表明已经移动至TAL所限定的区域外，终端设备先尝试恢复RRC连接，源RAN节点可能拒绝或接受该请求。当拒绝时，一方面，源RAN节点通过目标RAN节点通知终端设备拒绝其恢复RRC连接，另一方面，目标RAN节点通过AMF发起N2释放流程。当接受时，目标RAN节点通知终端设备接受其请求，然后由终端设备发起注册请求从AMF获取该终端设备的TAL。以上处理方式，实现了处于RRC非激活态的终端设备进行移动触发的TAU。
在一种实施场景下，向目标RAN节点发送重新分配的TAL，包括：AMF向目标RAN节点发送路径切换响应消息，路径切换响应消息中包括重新分配的TAL。该实施方式提供了AMF向目标RAN节点发送重新分配的TAL所采用的消息的一种可能的实现方式。
在一种实施场景下，该方法还包括：当目标RAN节点位于不允许区域时，AMF向会话管理功能SMF发送指示信息，指示信息用于指示终端设备位于不允许区域；或者，AMF触发接入网络AN节点用户设备上下文释放流程。该实施方式使得终端设备所处位置的TAI不属于终端设备的TAL时，目标RAN释放UE的上下文。
第十二方面，本申请实施例提供了一种接入和移动性管理功能AMF，该AMF包括：接收单元，用于从目标无线接入网络RAN节点接收路径切换请求消息，路径切换请求消息中携带终端设备的位置信息；确定单元，用于根据终端设备的位置信息，确定终端设备所处位置的TAI不属于终端设备的跟踪区列表TAL；发送单元，用于为终端设备重新分配TAL，并向目标RAN节点发送重新分配的TAL。基于同一发明构思，由于该AMF解决问题的原理以及有益效果可以参见上述第十一方面和第十一方面的各可能的方法实施方式以及所带来的有益效果，因此该AMF的实施可以参见上述第十一方面和第十一方面的各可能的方法的实施方式，重复之处不再赘述。
第十三方面，本申请实施例提供了一种通信方法，该方法包括：源无线接入网络RAN节点从目标RAN节点接收获取用户设备上下文请求消息，获取用户设备上下文请求消息用于获取终端设备的上下文信息，终端设备处于无线资源控制RRC非激活态；当目标RAN节点位于不允许区域时，源RAN节点向目标RAN节点发送获取用户设备上下文拒绝消息；或者，当目标RAN节点位于不允许区域时，源RAN节点向目标RAN节点发送获取用户设备上下文响应消息，获取用户设备上下文响应消息中携带失败指示信息，失败指示信息用于指示获取终端设备的上下文信息的失败原因；源RAN节点向接入和移动性管理功能AMF发送N2用户设备上下文释放请求消息。本申请实话例提供的一种通信方法，当处于RRC非激活态的终端设备所处位置的TAI不属于终端设备的TAL时，表明已经移动至TAL所限定的区域外，终端设备先尝试恢复RRC连接，源RAN节点可能拒绝或接受该请求。当拒绝时，一方面，源RAN节点通过目标RAN节点通知终端设备拒绝其恢复RRC连接，另一方面，目标RAN节点通过AMF发起N2释放流程。当接受时，目标RAN节点通知终端设备接受其请求，然后由终端设备发起注册请求从AMF获取该终端设备的TAL。以上处理方式，实现了处于RRC非激活态的终端设备进行移动触发的TAU。
在一种实施场景下，获取用户设备上下文拒绝消息中携带有拒绝原因，拒绝原因为终端设备位于不允许区域；N2用户设备上下文释放请求消息中携带有请求释放原因，请求释放原因为终端设备位于不允许区域；或者，失败指示信息用于指示终端设备位于不允许区域；N2用户设备上下文释放请求消息中携带有请求释放原因，请求释放原因为终端设备位于不允许区域。该实施方式提供了拒绝原因、请求释放原因的一种可能的具体实现方式。
第十四方面，本申请实施例提供了一种源无线接入网络RAN节点，该源RAN节点包括：接收单元，用于从目标RAN节点接收获取用户设备上下文请求消息，获取用户设备上下文请求消息用于获取终端设备的上下文信息，终端设备处于无线资源控制RRC非激活态；发送单元，用于当目标RAN节点位于不允许区域时，向目标RAN节点发送获取用户设备上下文拒绝消息；或者，当目标RAN节点位于不允许区域时，向目标RAN节点发送获取用户设备上下文响应消息，获取用户设备上下文响应消息中携带失败指示信息，失败指示信息用于指示获取终端设备的上下文信息的失败原因；发送单元，还用于向接入和移动性管理功能AMF发送N2用户设备上下文释放请求消息。基于同一发明构思，由于该源RAN节点解决问题的原理以及有益效果可以参见上述第十三方面和第十三方面的各可能的方法实施方式以及所带来的有益效果，因此该源RAN节点的实施可以参见上述第十三方面和第十三方面的各可能的方法的实施方式，重复之处不再赘述。
第十五方面，本申请实施例提供一种终端设备，包括：处理器、存储器、总线和通信接口；该存储器用于存储计算机执行指令，该处理器与该存储器通过该总线连接，当该终端设备运行时，该处理器执行该存储器存储的该计算机执行指令，以使终端设备执行上述第一方面中任意一项或第七方面中任意一项所述的方法。
第十六方面，本申请实施例提供了一种计算机存储介质，包括指令，当其在计算机上运行时，使得计算机执行如第一方面中任意一项或第七方面中任意一项所述的方 法。
第十七方面，本申请实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得该计算机执行如第一方面中任意一项或第七方面中任意一项所述的方法。
另外，第十五方面至第十七方面中所带来的技术效果可参见第一方面中任意一项或第七方面中任意一项中不同设计方式所带来的技术效果，此处不再赘述。
第十八方面，本申请实施例提供一种接入和移动性管理功能AMF，包括：处理器、存储器、总线和通信接口；该存储器用于存储计算机执行指令，该处理器与该存储器通过该总线连接，当该AMF运行时，该处理器执行该存储器存储的该计算机执行指令，以使AMF执行上述第三方面中任意一项或第十一方面中任意一项所述的方法。
第十九方面，本申请实施例提供了一种计算机存储介质，包括指令，当其在计算机上运行时，使得计算机执行如第三方面中任意一项或第十一方面中任意一项所述的方法。
第二十方面，本申请实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得该计算机执行如第三方面中任意一项或第十一方面中任意一项所述的方法。
另外，第十八方面至第二十方面中所带来的技术效果可参见第三方面中任意一项或第十一方面中任意一项中不同设计方式所带来的技术效果，此处不再赘述。
第二十一方面，本申请实施例提供一种会话管理功能SMF，包括：处理器、存储器、总线和通信接口；该存储器用于存储计算机执行指令，该处理器与该存储器通过该总线连接，当该SMF运行时，该处理器执行该存储器存储的该计算机执行指令，以使SMF执行上述第五方面中任意一项所述的方法。
第二十二方面，本申请实施例提供了一种计算机存储介质，包括指令，当其在计算机上运行时，使得计算机执行如第五方面中任意一项所述的方法。
第二十三方面，本申请实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得该计算机执行如第五方面中任意一项所述的方法。
另外，第二十一方面至第二十三方面中所带来的技术效果可参见第五方面中任意一项中不同设计方式所带来的技术效果，此处不再赘述。
第二十四方面，本申请实施例提供一种无线接入网络RAN节点，包括：处理器、存储器、总线和通信接口；该存储器用于存储计算机执行指令，该处理器与该存储器通过该总线连接，当该RAN节点运行时，该处理器执行该存储器存储的该计算机执行指令，以使RAN节点执行上述第九方面中任意一项或第十三方面中任意一项所述的方法。
第二十五方面，本申请实施例提供了一种计算机存储介质，包括指令，当其在计算机上运行时，使得计算机执行如第九方面中任意一项或第十三方面中任意一项所述的方法。
第二十六方面，本申请实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得该计算机执行如第九方面中任意一项或第十三方面中任意一项所述的方法。
另外，第二十四方面至第二十六方面中所带来的技术效果可参见第九方面中任意一项或第十三方面中任意一项中不同设计方式所带来的技术效果，此处不再赘述。
附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍。
图1为本申请的实施例提供的通信系统的架构示意图；
图2为本申请的实施例提供的系统中各设备的硬件结构示意图；
图3为本申请的实施例提供的通信方法的流程示意图一；
图4为本申请的实施例提供的通信方法的流程示意图二；
图5为本申请的实施例提供的通信方法的流程示意图三；
图6为本申请的实施例提供的通信方法的流程示意图四；
图7为本申请的实施例提供的SMF触发PDU会话释放流程的流程示意图；
图8为本申请的实施例提供的SMF触发PDU会话去激活流程的流程示意图；
图9为本申请的实施例提供的通信方法的流程示意图五；
图10为本申请的实施例提供的通信方法的流程示意图六；
图11为本申请的实施例提供的目标RAN节点触发AN节点UE上下文释放流程的流程示意图；
图12为本申请的实施例提供的通信方法的流程示意图七；
图13为本申请的实施例提供的通信方法的流程示意图八；
图14为本申请的实施例提供的AMF触发AN节点UE上下文释放流程的流程示意图；
图15为本申请的实施例提供的通信方法的流程示意图九；
图16为本申请的实施例提供的通信方法的流程示意图十；
图17为本申请的实施例提供的通信方法的流程示意图十一；
图18为本申请的实施例提供的通信方法的流程示意图十二；
图19为本申请的实施例提供的终端设备的结构示意图一；
图20为本申请的实施例提供的终端设备的结构示意图二；
图21为本申请的实施例提供的RAN节点的结构示意图一；
图22为本申请的实施例提供的RAN节点的结构示意图二；
图23为本申请的实施例提供的AMF的结构示意图一；
图24为本申请的实施例提供的AMF的结构示意图二；
图25为本申请的实施例提供的SMF的结构示意图一；
图26为本申请的实施例提供的SMF的结构示意图二。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对 于类似的技术问题，同样适用。应当指出的是，本申请实施例中的方案还可以应用于其他无线通信网络中，相应的名称也可以用其他无线通信网络中的对应功能的名称进行替代。
参照图1中所示，为本申请实施例提供的通信系统的网络架构示意图，包括：终端设备101、无线接入网络(Radio Access Network，RAN)节点102、接入与移动性管理功能(Access and Mobility management Function，AMF)103、用户面功能(User Plane Function，UPF)104、会话管理功能(Session Management Function，SMF)105、策略控制功能(Policy Control Function，PCF)106、统一数据管理(Unified Data Management，UDM)107。其中：
终端设备101可以包括用户设备(User Equipment，UE)、平板电脑(Pad)、个人计算机(Personal Computer，PC)等通信设备。
RAN节点102可以为5G侧基站，终端设备通过该基站可以接入5G通信系统。
AMF103为5G核心网设备，用于对用户进行鉴权、授权，对用户的移动性进行管理。
UPF104是5G核心网的用户面设备，为终端设备的分组数据单元(Packet Data Unit，PDU)会话提供用户面服务；是运营商网络与外部网络间的接口网关。
SMF105是5G核心网的控制面设备，为终端设备的PDU会话提供控制面服务；对5G的PDU会话进行管理，对5G的服务质量(Quality of Service，QoS)进行管理，负责为终端设备分配IP地址，负责为终端设备选择UPF。
PCF106为5G核心网设备，负责产生用户建立QoS数据流(QoS flow)的策略。
UDM107为5G核心网设备，用于保存用户的签约数据。
参照图2中所示，为本申请实施例提供的各设备的硬件结构图。
终端设备100包括至少一个处理器1001、至少一个存储器1002、至少一个收发器1003。可选的，终端设备100还可以包括输出设备1004和输入设备1005。终端设备100用于执行下述各方法实施例中所述的终端设备的功能。
处理器1001、存储器1002、收发器1003通过总线相连接。处理器1001可以是一个通用中央处理器(Central Processing Unit，CPU)、微处理器、特定应用集成电路(Application-Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)、复杂可编程逻辑器件(Complex Programmable Logic Device，CPLD)，或者一个或多个用于控制本申请方案程序执行的集成电路。处理器1001也可以是多个处理器，每一个处理器可以是一个单核(single-CPU)处理器或多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路和/或用于处理数据(例如计算机程序指令)的处理核。
存储器1002可以是只读存储器(Read-Only Memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备、随机存取存储器(Random Access Memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、只读光盘(Compact Disc Read-Only Memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存 储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器1002可以是独立存在，通过总线与处理器1001相连接。存储器1002也可以和处理器1001集成在一起。其中，存储器1002用于存储执行本申请方案的应用程序代码，并由处理器4001来控制执行。处理器4001用于执行存储器4003中存储的计算机程序代码，从而实现本申请实施例中所述的方法。
收发器1003可以使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网、RAN节点、无线局域网(Wireless Local Area Networks，WLAN)等。收发器1003包括发射机Tx和接收机Rx。
输出设备1004和处理器4001通信，可以以多种方式来显示信息。例如，输出设备104可以是液晶显示器(Liquid Crystal Display，LCD)，发光二级管(Light Emitting Diode，LED)显示设备，阴极射线管(Cathode Ray Tube，CRT)显示设备，或投影仪(projector)等。输入设备1005和处理器1001通信，可以以多种方式接受用户的输入。例如，输入设备1005可以是鼠标、键盘、触摸屏设备或传感设备等。
RAN节点200(RAN 102)包括：至少一个处理器2001、至少一个存储器2002、至少一个收发器2003和至少一个网络接口2004，至少一个处理器2001、至少一个存储器2002、至少一个收发器2003和至少一个网络接口2004通过总线相连。网络接口2004用于通过链路(例如S1接口)与核心网设备300的网络接口3004连接，或者通过有线或无线链路(例如X2接口)与其它RAN节点的网络接口2004进行连接。收发器2003用于与终端设备100的通信。RAN节点200其余各器件的功能参照对终端设备100各器件的功能描述，具体不再赘述。RAN节点200用于执行下述各方法实施例中所述的目标RAN节点或源RAN节点的功能。
核心网设备300可以提供进一步网络连接，例如电话网络和/或数据通信网络(例如Internet)。核心网设备300包括：至少一个处理器3001、至少一个存储器3002和至少一个网络接口3004，至少一个处理器3001、至少一个存储器3002和至少一个网络接口3004通过一个总线相连。网络接口3004用于通过链路(例如S1接口)与RAN节点200的网络接口2004连接，或者通过有线或无线链路在各核心网设备之间连接。核心网设备300内部各器件的功能参照对终端设备100内部各器件的功能描述，具体不再赘述。核心网设备300用于执行下述各方法实施例中所述的AMF、SMF或UPF的功能。
本申请各实施例提及的服务区域(service area)按照功能区域划分可以包括允许区域(allowed area)和不允许区域(non-allowed area)。在允许区域中，允许终端设备进行业务通信，例如，根据终端设备与运营商的签约信息，可以允许终端设备发起任何正常业务通信；在不允许区域中，不允许终端设备与网络侧进行正常业务通信，例如，不允许终端设备和网络侧发送业务请求(Service Request)或者会话管理(Session Management)信令，但是允许终端设备或网络侧发起注册管理(Registration Management)流程。
在本申请各实施例中，如前所述，TAL可以用于指示终端设备的注册区，注册区内跟踪区可以全部属于不允许区域，或全部属于允许区域。即终端设备的注册区可以 包括一个或多个属于不允许区域的跟踪区，但不包含允许区域的跟踪区；或者，终端设备的注册区可以包括一个或多个属于允许区域的跟踪区，但不包含不允许区域的跟踪区。那么，当终端设备从允许区域移动到不允许区域时，或者从不允许区域移动到允许区域时，意味着终端设备移出了当前的注册区，终端设备将发起注册管理流程。
同时，当终端设备处于RRC非激活态时，RAN节点根据终端设备的TAL生成RAN通知区域(RAN Notification Area，RNA)并将其发给终端设备，当终端设备移动离开所处位置的RNA时，终端设备向RAN节点发起RRC连接恢复请求(RRC Connection Resume request)，RAN节点为终端设备分配新的RNA。需要说明的是，RNA必须是核心网分配的TAL的一部分，其中，核心网分配的TAL是由AMF节点发给RAN节点的。
本申请各实施例提及的源RAN节点指终端设备离开第一区域前，为终端设备提供服务的RAN节点，相应地，目标RAN节点指终端设备移动至第二区域时，为终端设备提供服务的RAN节点。
本申请各实施例提及的第一区域和第二区域指的是分别属于不同TAL限定的区域，例如，第一区域可以是如前文所述的允许区域，第二区域为不允许区域，本申请实施例不作限定。
本申请各实施例提及的将终端设备转换为连接管理(Connection Management，CM)空闲态可以替换为：将终端设备从处于CM连接态且处于RRC非激活态转换为CM空闲态，或者将处于任意CM状态的终端设备设置为CM空闲态，还可以是其他转换或设置过程，本申请实施例不作限定，只要保证最终状态为CM空闲态即可。
本申请实施例提供了一种通信方法，该方法可以应用于处于RRC非激活态的终端设备从第一区域移动至第二区域，第一区域属于终端设备的注册区，第二区域不属于终端设备的注册区。其中，第一区域和第二区域均可以是TA或小区，不予限定。此外，终端设备的注册区指的是终端设备当前存储的TAL所限定的区域或对应的区域。进一步的，第一区域可以为允许区域，第二区域可以为不允许区域。
参照图3中所示，该方法包括：
S101、当处于RRC非激活态的终端设备所处位置的TAI不属于终端设备的TAL时，终端设备转换为CM空闲态。
其中，上述TAL可以是在终端设备位于第一区域时，通过注册接受(registration accept)消息或用户设备配置更新命令(UE configuration update command)消息等从AMF获取的。
示例性地，终端设备在移动至第二区域之后，终端设备可以通过侦听空口的系统信息块(System Information Block，SIB)来检测其所处位置的TAI。进而，终端设备通过判断其所处位置的TAI是否属于当前存储的TAL，以确定该终端设备是否移出该终端设备的注册区。
其中，终端设备所处位置的TAI指的是终端设备当前所处位置所属TA对应的TAI，或者，终端设备当前所处位置对应的TAI。当终端设备所处位置的TAI不属于终端设备的TAL时，表明终端设备已经移动至该TAL所限定的区域外，此时，终端设备可以进行TAU。
可选的，终端设备可以存储允许区域的TAI或不允许区域的TAI，因此，终端设备可以将其所处位置的TAI与允许区域的TAI进行匹配，或者，终端设备可以将其所处位置的TAI与不允许区域的TAI进行匹配，以确定该终端设备位于允许区域或不允许区域。该实施方式提供了终端设备确定位于允许区域或不允许区域的一种实现方式。
可选的，终端设备所处位置的TAI对应的区域为不允许区域，TAL对应的区域为允许区域。该实施方式表明终端设备从允许区域移动至不允许区域。
S102、终端设备通过目标RAN节点向AMF发送注册请求(registration request)消息。
其中，该注册请求消息可以用于请求为该终端设备分配TAL或者用于请求为该终端设备更新TAL。该注册请求消息可以是移动更新(mobility update)类型的注册请求消息。其中，移动更新类型指终端设备在移出终端设备的TAL所限定区域时所触发的更新，即终端设备移出其存储的TAL所限定的区域。
S103、AMF从目标RAN节点接收注册请求消息。
S104、AMF向源RAN节点发送N2用户设备上下文释放命令(N2 UE context release command)消息。
其中，源RAN节点也可以称为锚(anchor)RAN节点。
其中，该N2用户设备上下文释放命令消息用于请求源RAN节点释放终端设备的上下文。
可选的，N2用户设备上下文释放命令消息中包括释放原因，该释放原因可以用于指示终端设备位于不允许区域(non-allowed area)。该实施方式提供了释放原因的一种可能的实现形式。
进一步可选地，AMF可以根据其保存的该终端设备的上下文(context)中的不允许区域和该终端设备当前所处位置的TAI，确定该终端设备位于不允许区域。例如，当终端设备所处位置的TAI属于不允许区域的TAI时，可以确定该终端设备位于不允许区域。
S105、源RAN节点接收由AMF发送的N2用户设备上下文释放命令(N2 UE context release command)消息。
S106、源RAN节点根据N2用户设备上下文释放命令消息删除终端设备的上下文。
S107、源RAN节点向AMF发送N2用户设备上下文释放完成(N2 UE context release complete)消息。
S108、AMF接收由源RAN节点发送的N2用户设备上下文释放完成消息。
S109、AMF通过目标RAN节点向终端设备发送注册接受(registration accept)消息，注册接受消息中包括为终端设备分配的TAL。
S110、终端设备通过目标RAN节点接收由AMF发送的注册接受消息。
本申请实施例提供的通信方法，当处于RRC非激活态的终端设备所处位置的TAI不属于该终端设备的TAL时，表明该终端设备已经移动至该终端设备的TAL所限定的区域外，此时终端设备转换为CM空闲态，终端设备向AMF发送注册请求消息以请求为处于当前位置的终端设备分配TAL，AMF向源RAN节点发送N2用户设备上下文释放命令消息以释放源RAN节点存储的终端设备的上下文，接收到源RAN节点 释放上下文的响应消息之后，AMF通过目标RAN节点向终端设备发送注册接受消息，该注册接受消息中包括为终端设备分配的TAL。上述实施例实现了处于RRC非激活态的终端设备进行移动触发的TAU。
可选的，参照图4中所示，在上述实施例的一种实施场景下，上述方法还包括步骤S121-S123：
S121、AMF从目标RAN节点接收终端设备的位置信息。
其中，终端设备的位置信息可以包括以下信息中的至少一个：终端设备的TAI、终端设备的RAN节点小区全局标识符(RAN节点Cell Global Identifier，CGI)或目标RAN节点的标识信息。
其中，终端设备的TAI指的是终端设备所处TA对应的TAI。
需要说明的是，终端设备的位置信息可以与步骤S102中的注册请求消息RAN节点通过一条消息发送给AMF，示例性的，在目标RAN节点接收到注册请求消息之后，目标RAN节点向AMF发送初始用户设备消息(initial UE message)，在该初始用户设备消息中包括终端设备的位置信息以及步骤S102中的注册请求消息；显然，也可以RAN节点通过两条消息分别发送给AMF，本申请实施例不作限定。
S122、AMF根据终端设备的位置信息以及终端设备的上下文中的不允许区域，确定终端设备位于不允许区域。
示例性的，当终端设备的位置信息为终端设备的TAI时，AMF可以根据终端设备的TAI与该终端设备的上下文中允许区域的TAI进行匹配，以确定该终端设备位于允许区域或不允许区域；或者，AMF可以根据终端设备的TAI与该终端设备的上下文中不允许区域的TAI进行匹配。
S123、AMF将终端设备设置为CM空闲态。
在AMF向终端设备发送注册接受消息之后，AMF发起接入网络(Access Network，AN)节点UE上下文释放流程(UE context release in the AN)，该流程结束后，AMF和终端设备会从CM连接态转换到CM空闲态。
示例性的，AMF可以将处于CM连接态的终端设备转换为CM空闲态，或者AMF将处于RRC非激活态的终端设备转换为CM空闲态，本申请实施例不作限定。
步骤S121-S123所述的实施方式，提供了AMF对终端设备进行CM状态转换的一种具体实现方式，使得终端设备的CM状态为CM空闲态。
可选的，在上述实施例的另一种实施场景下，参照图5中所示，在步骤S122之后，该方法还包括步骤S131：
S131、AMF向SMF发送PDU会话去激活请求消息，PDU会话去激活请求消息用于请求SMF去激活终端设备的PDU会话。
该实施方式提供了AMF对终端设备进行PDU会话状态转换的一种具体实现方式，使得终端设备的PDU会话处于去激活态。
可选的，在上述实施例的另一种实施场景下，参照图6中所示，在步骤S122之后，该方法还包括步骤S132-S134：
S132、AMF向SMF发送指示信息。
其中，该指示信息用于指示终端设备位于不允许区域。例如，该指示信息为不允 许区域指示(例如，non-allowed area indication)。
S133、SMF从AMF接收指示信息。
S134、SMF根据本地会话管理(Session Management，SM)策略以及上述指示信息，触发终端设备的PDU会话释放(PDU session release)流程或PDU会话去激活(PDU session deactivation)流程。
例如，上述SM策略可以为：指定某些NSSAI/DNN对应的PDU会话去激活，或者指定某些NSSAI/DNN对应的PDU会话释放。
步骤S132-S134所述的实施方式提供了AMF和SMF对终端设备进行PDU会话状态转换的一种具体实现方式，使得终端设备的PDU会话处于去激活态或空闲态。
参照图7中所示，为SMF触发PDU会话释放流程的示意图，该方法包括步骤S201-S205：
S201、SMF向UPF发送N4会话释放请求(N4 Session Release Request)消息，该消息中包括请求释放的N4会话标识(N4 Session ID)。
S202、UPF向SMF发送N4会话释放响应(N4 Session Release Response)消息，以确认N4会话释放请求消息，在N4会话释放响应消息中包括上述N4会话标识。
S203、SMF向AMF发送PDU会话释放命令(PDU Session Release Command)消息。
S204、AMF向SMF发送PDU会话更新会话管理上下文(Nsmf_PDUSession_UpdateSMContext)消息，该消息中包括PDU会话释放确认(PDU Session Release Ack)消息。
S205、SMF向AMF发送PDU会话更新会话管理上下文响应(Nsmf_PDUSession_UpdateSMContext response)消息，以使得AMF释放该PDU会话相关的上下文信息。
参照图8中所示，为SMF触发PDU会话去激活流程的示意图，该方法包括步骤S301-S307：
S301、SMF向UPF发送N4会话修改请求(N4 Session Modification Request)消息，该消息用于指示释放对应PDU会话的N3隧道的RAN节点隧道信息。
S302、UPF向SMF发送N4会话修改响应(N4 Session Modification Response)消息。
S303、SMF向AMF发送N11消息，N11消息中包括N2会话释放请求消息，N2会话释放请求消息用于请求释放与PDU会话相关的RAN节点资源。
S304、AMF向源RAN节点发送N2 PDU会话请求(N2 PDU Session Request)消息，该消息中包括N2会话释放请求消息。
S305、源RAN节点与终端设备进行AN特定资源释放流程，以释放与PDU会话相关的RAN节点资源。
S306、源RAN节点向AMF发送N2 PDU会话响应(N2 PDU Session Response)消息。
S307、AMF向SMF发送N11消息，该消息用于对步骤S303中的消息进行确认。
本申请实施例提供了另一种通信方法，该方法可以应用于处于RRC非激活态的终 端设备从第一区域移动至第二区域，其中，第一区域和第二区域的相关描述可以参见图3所示实施例。参见图9，该方法包括：
S401、当处于RRC非激活态的终端设备所处位置的TAI不属于该终端设备的TAL时，终端设备向目标RAN节点发送RRC连接恢复请求(RRC connection resume request)消息。
其中，终端设备所处位置的TAI，终端设备的TAL，以及如何确定终端设备所处位置的TAI不属于该终端设备的TAL等，均可以参见步骤S101的描述，具体不再赘述。
此时，终端设备可以保持RRC非激活态。
其中，目标RAN节点可以位于不允许区域。
S402、目标RAN节点从终端设备接收RRC连接恢复请求消息。
S403、目标RAN节点向源RAN节点发送获取用户设备上下文请求(retrieve UE context request)消息。
其中，该获取用户设备上下文请求消息用于获取终端设备的上下文信息。
S404、源RAN节点从目标RAN节点接收获取用户设备上下文请求消息。
可选地，当目标RAN节点位于不允许区域时执行步骤S405-S413，或者执行步骤S414-S422。
其中，确定目标RAN节点是否位于不允许区域的方式可以包括：源RAN节点根据本地保存的不允许区域的信息以及目标RAN节点的位置信息确定目标RAN节点是否位于不允许区域。
其中，目标RAN节点的位置信息可以包括终端设备的TAI、CGI或目标RAN节点的标识信息。并且上述位置信息可以事先通过操作管理和维护(Operation Administration and Maintenance，OAM，)配置，或者RAN节点之间建立X2接口连接时获取，或者在获取用户设备上下文请求中携带。
S405、当目标RAN节点位于不允许区域时，源RAN节点向目标RAN节点发送获取用户设备上下文拒绝(retrieve UE context reject)消息；或者，当目标RAN节点位于不允许区域时，源RAN节点向目标RAN节点发送获取用户设备上下文响应(retrieve UE context response)消息。
其中，该获取用户设备上下文响应消息中可以携带失败指示信息，该失败指示信息可以用于指示获取终端设备的上下文信息的失败原因。
其中，获取用户设备上下文拒绝消息中可以携带有拒绝原因，拒绝原因可以为终端设备位于不允许区域(例如，non-allowed area indication)。此时终端设备处于本地数据网络(local area data network)。该实施方式提供了拒绝原因的一种可能的具体实现方式。
S406、源RAN节点向AMF发送N2用户设备上下文释放请求(N2 UE context release request)消息。
其中，N2用户设备上下文释放请求消息可以用于触发AN节点UE上下文释放流程(UE context release in the AN)。此外，N2用户设备上下文释放请求消息中可以携带有请求释放原因，请求释放原因可以为终端设备位于不允许区域，例如，该消息中 携带的non-allowed area indication设置为1。该实施方式提供了拒绝原因、请求释放原因的一种可能的具体实现方式。
需要说明的是，步骤S405与S406没有先后执行顺序。
S407、当目标RAN节点接收到来自源RAN节点的获取用户设备上下文拒绝消息时，或者，当目标RAN节点接收到来自源RAN节点的获取用户设备上下文响应消息，并且获取用户设备上下文响应消息携带有用于指示获取上下文信息失败的失败指示信息时，目标RAN节点向终端设备发送RRC连接恢复拒绝(RRC connection resume reject)消息。
S408、终端设备从目标RAN节点接收RRC连接恢复拒绝消息。
S409、终端设备根据RRC连接恢复拒绝消息，从CM连接态转换为CM空闲态。
其中，终端设备接收到该消息表明无法恢复RRC连接，因此终端设备可以直接从CM连接态转换为CM空闲态。
需要说明的是，步骤S407-S409与S410-S413没有先后执行顺序。
S410、AMF从源RAN节点接收N2用户设备上下文释放请求消息。
S411、AMF向SMF发送PDU会话去激活请求消息，PDU会话去激活请求消息用于请求SMF去激活终端设备的PDU会话。
S412、AMF向源RAN节点发送N2用户设备上下文释放命令(N2 UE context release command)消息。
需要说明的是，步骤S411与S412没有先后执行顺序。
S413、源RAN节点从AMF接收N2用户设备上下文释放命令(N2 UE context release command)消息，源RAN节点向AMF发送N2用户设备上下文释放完成(N2 UE context release complete)消息。
以上步骤S405-S413是源RAN节点拒绝恢复RRC连接的流程，步骤S414-S422是源RAN节点接收恢复RRC连接的流程。
S414、源RAN节点向目标RAN节点发送获取用户设备上下文响应消息，获取用户设备上下文响应消息中包括终端设备的上下文信息。
S415、当目标RAN节点接收到来自源RAN节点的终端设备的上下文信息时，目标RAN节点向终端设备发送RRC连接恢复消息。
其中，RRC连接恢复消息可以用于指示RRC连接恢复成功。
具体的，当目标RAN节点接收到来自源RAN节点的用户设备上下文响应消息时，目标RAN节点向终端设备发送RRC连接恢复消息。
S416、目标RAN节点向AMF发送路径切换请求(path switch request)消息，路径切换请求消息中携带终端设备的位置信息。
该消息用于建立目标RAN节点与AMF之间的N2信令连接。
S417、AMF从目标RAN节点接收路径切换请求消息。
S418、AMF根据终端设备的位置信息，确定终端设备所处位置的TAI不属于终端设备的TAL，则AMF为终端设备重新分配TAL，并向目标RAN节点发送重新分配的TAL。
具体的，AMF可以向目标RAN节点发送路径切换响应(path switch response)消 息，该路径切换响应消息中包括重新分配的TAL。该实施方式提供了AMF向目标RAN节点发送重新分配的TAL所采用的消息的一种可能的实现方式。
其中，AMF为终端设备重新分配TAL可以是在AMF接收到来自终端设备的注册请求消息之前。
S419、目标RAN节点从AMF接收路径切换响应消息。
S420、目标RAN节点向源RAN节点发送用户设备上下文释放(UE context release)消息，用户设备上下文释放消息用于指示源RAN节点释放终端设备的上下文信息。
S421、终端设备向AMF发送注册请求消息。
S422、AMF向终端设备发送注册接受消息。
其中，该注册接受消息携带为终端设备重新分配的TAL。
本申请实话例提供的一种通信方法，当处于RRC非激活态的终端设备所处位置的TAI不属于终端设备的TAL时，表明已经移动至TAL所限定的区域外，终端设备先尝试恢复RRC连接，源RAN节点可能拒绝或接受该请求。当拒绝时，一方面，源RAN节点通过目标RAN节点通知终端设备拒绝其恢复RRC连接，另一方面，目标RAN节点通过AMF发起N2释放流程。当接受时，目标RAN节点通知终端设备接受其请求，然后由终端设备发起注册请求从AMF获取该终端设备的TAL。以上处理方式，实现了处于RRC非激活态的终端设备进行移动触发的TAU。
可选的，参照图10中所示，当路径切换响应消息中包括为终端设备重新分配的TAL时，在步骤S419之后，该方法还可以包括步骤S431和S432：
S431、目标RAN节点根据为终端设备重新分配的TAL生成RNA。
其中，终端设备的TAL可以由AMF发送给该目标RAN节点。
示例性地，目标RAN节点可以根据从AMF接收的TAL生成RNA。
进一步的，可以选择TAL中的TA的一部分或全部生成RNA。
S432、目标RAN节点向终端设备发送RNA。
具体的，目标RAN节点可以通过一条RRC消息向终端设备发送RNA。该RRC消息可以是RRC连接释放(RRC connection release)消息。
步骤S431和S432所述的实施方式提供了目标RAN节点如何为终端设备生成RNA的一种具体实现方式，使得终端设备可以获取更新的RNA。
可选的，参照图10中所示，当目标RAN节点位于不允许区域时，在步骤S415所述的目标RAN节点接收到来自源RAN节点的终端设备的上下文信息之后，即在目标RAN节点接收到来自源RAN节点的用户设备上下文响应消息之后，该方法还包括步骤S433：
S433、目标RAN节点触发AN节点UE上下文释放流程(UE context release in the AN)，完成该流程之后目标RAN节点删除终端设备的上下文信息。
具体的，目标RAN节点可以根据策略确定将终端设备转换为CM空闲态，然后触发目标RAN节点触发AN节点UE上下文释放流程(UE context release in the AN)。例如，上述策略可以为：当终端设备位于不允许区域时，终端设备的状态不能设置为RRC非激活状态。
该实施方式使得目标RAN节点删除终端设备的上下文。
具体的，参照图11中所示，目标RAN节点触发AN节点UE上下文释放流程(UE context release in the AN)可以包括：
S4331、目标RAN节点向AMF发送N2上下文释放请求(N2 UE Context Release Request消息。
S4332、AMF向SMF发送N11 PDU会话去激活请求(N11 PDU session deactivation Request)消息。
S4333、SMF向UPF发送N4会话修改请求(N4 Session Modification Request)消息。
S4334、UPF向SMF发送N4会话修改响应(N4 Session Modification Response)消息。
S4335、SMF向AMF发送N11 PDU会话去激活响应(N11 PDU session deactivation Response)消息。
S4336、AMF向目标RAN节点发送N2用户设备上下文释放请求(N2 UE Context Release Request)消息。
S4337、目标RAN节点释放终端设备的上下文，目标RAN节点向AMF发送N2用户设备上下文释放完成(N2 UE Context Release Complete)消息。
可选的，在上述实施例的一种实施场景下，参照图12中所示，在步骤S418所述的AMF确定终端设备所处位置的TAI不属于终端设备的TAL之后，该方法还包括步骤S434-S436：
S434、当目标RAN节点位于不允许区域时，AMF向SMF发送指示信息(例如，non-allowed area indication)，该指示信息用于指示终端设备位于不允许区域。
具体的，该指示信息可以通过AMF提供的事件暴露服务(Namf_EventExposure)发送给SMF。
S435、SMF从AMF接收指示信息。
S436、SMF根据本地SM策略以及上述指示信息，触发终端设备的PDU会话释放流程或PDU会话去激活流程。
具体可以参照图7和图8中描述，具体不再赘述。
需要说明的是步骤S434-S436对应于步骤S132-S134。
步骤S434-S436所述的实施方式提供了AMF和SMF对终端设备进行PDU会话状态转换的一种具体实现方式，使得目标RAN节点位于不允许区域时终端设备的PDU会话处于去激活态或空闲态。
可选的，在上述实施例的另一种实施场景下，参照图13中所示，在步骤S418所述的AMF确定终端设备所处位置的TAI不属于终端设备的TAL之后，该方法还包括步骤S437：
S437、AMF触发AN节点UE上下文释放流程(UE context release in the AN)。
该实施方式使得终端设备所处位置的TAI不属于终端设备的TAL时，目标RAN释放UE的上下文。
具体的，参照图14中所示，AMF触发AN节点UE上下文释放流程(UE context release in the AN)可以包括：
S4371、AMF向SMF发送N11 PDU会话去激活请求(N11 PDU session deactivation Request)消息。
S4372、SMF向UPF发送N4会话修改请求(N4 Session Modification Request)消息。
S4373、UPF向SMF发送N4会话修改响应(N4 Session Modification Response)消息。
S4374、SMF向AMF发送N11 PDU会话去激活响应(N11 PDU session deactivation Response)消息。
S4375、AMF向目标RAN节点发送N2用户设备上下文释放请求(N2 UE Context Release Request)消息。
S4376、目标RAN节点释放终端设备的上下文，目标RAN节点向AMF发送N2用户设备上下文释放完成(N2 UE Context Release Complete)消息。
下面以具体示例对上述通信方法进行描述。
本申请实施例提供了一种通信方法，该方法可以应用于处于RRC非激活态的终端设备从允许区域移动至不允许区域，并且从网络侧获取的TAI不属于终端设备的TAL时，终端设备进行TAU。参照图15中所示，该方法包括：
S501、当处于RRC非激活态的终端设备所处位置的TAI不属于终端设备的TAL，并且终端设备根据所处位置的TAI确定移动到不允许区域时，终端设备根据本地策略转换为CM空闲态。
具体地，当终端设备进入到不允许区域时，由于无法进行正常的业务，因此终端设备转换为CM空闲态。
其中，本地策略可以固化在终端设备中，或者由终端设备通过AMF从PCF获取，例如通过注册接受(registration accept)消息或用户设备配置更新命令(UE configuration update command)消息等获取。
该步骤详细描述参见S101，终端设备根据所处位置的TAI确定移动到不允许区域的方式参照步骤S101中描述。
S502、终端设备通过目标RAN节点向AMF发送移动更新类型的注册请求消息，该注册请求消息用于请求为该终端设备分配TAL。
该步骤详细描述参见S102，关于移动更新类型的描述参照步骤S101中描述，具体不再赘述。
S503、AMF从目标RAN节点接收初始用户设备消息(initial UE message)，初始用户设备消息中包括注册请求消息以及终端设备的位置信息。
该步骤为步骤S103和S121的结合，关于初始用户设备消息和终端设备的位置信息的描述参照步骤S121，具体不再赘述。
S504、AMF根据终端设备的位置信息确定终端设备位于不允许区域，AMF将终端设备设置为CM空闲态。
该步骤为步骤S122和S123结合，具体不再赘述。
可选的，在执行完S504后可以选择执行S505或执行S506-S508这两种实施方式中的一种。
S505、AMF向SMF发送PDU会话去激活请求消息，PDU会话去激活请求消息用于请求SMF去激活终端设备的PDU会话。
该步骤详细描述参见S131。
该实施方式提供了AMF对终端设备进行PDU会话状态转换的一种具体实现方式，使得终端设备的PDU会话处于去激活态。
S506、AMF向SMF发送指示信息，其中，该指示信息用于指示终端设备位于不允许区域(例如，non-allowed area indication)。
该步骤详细描述参见S132。
S507、SMF从AMF接收指示信息。
该步骤详细描述参见S133。
S508、SMF根据本地会话管理(Session Management，SM)策略以及上述指示信息，触发终端设备的PDU会话释放(PDU session release)流程或PDU会话去激活(PDU session deactivation)流程。
该步骤详细描述参见S134，具体不再赘述。
步骤S506-S508所述的实施方式提供了AMF和SMF对终端设备进行PDU会话状态转换的一种具体实现方式，使得终端设备的PDU会话处于去激活态或空闲态。
S509、AMF向源RAN节点发送N2用户设备上下文释放命令(N2 UE context release command)消息，该消息中包括释放原因，释放原因为终端设备位于不允许区域(non-allowed area)。
该步骤详细描述参见S104，具体不再赘述。
S510、源RAN节点接收由AMF发送的N2用户设备上下文释放命令消息，根据N2用户设备上下文释放命令消息删除终端设备的上下文(context)。
该步骤为步骤S105和S106的结合，具体不再赘述。
S511、源RAN节点向AMF发送N2用户设备上下文释放完成(N2 UE context release complete)消息。
该步骤详细描述参见S107。
S512、AMF接收由源RAN节点发送的N2用户设备上下文释放完成消息，通过目标RAN节点向终端设备发送注册接受，注册接受消息中包括重新分配的TAL。
该步骤为步骤S108和S109的结合，具体不再赘述。
S513、终端设备通过目标RAN节点接收由AMF发送的注册接受消息。
该步骤详细描述参见S110。
通过步骤S501和S504使得终端设备和网络侧设备之间CM状态均为CM空闲态，并且通过步骤S508使得终端设备和网络侧设备之间PDU会话状态均为未激活态。
本申请实施例提供的通信方法，当处于RRC非激活态的终端设备所处位置的TAI不属于TAL时，表明已经移动至TAL边界外，因此进行TAU，此时终端设备转换为CM空闲态，终端设备向AMF发送注册请求消息以请求所处位置的TAL，AMF向源RAN节点发送N2用户设备上下文释放命令消息以释放源RAN节点处的终端设备的上下文，接收到源RAN节点释放上下文的响应消息之后，AMF通过向终端设备发送注册接受消息，该注册接受消息中包括为终端设备重新分配的TAL。实现了处于RRC 非激活态的终端设备进行移动触发的TAU。另外，实现了终端设备和网络侧设备之间CM状态均为CM空闲态，终端设备和网络侧设备之间PDU会话状态均为未激活态。
本申请实施例提供了一种通信方法，该方法可以应用于处于RRC非激活态的终端设备从允许区域移动至不允许区域，并且终端设备所处位置的TAI不属于终端设备的TAL时，终端设备进行TAU。参照图16中所示，该方法包括：
S601、当处于RRC非激活态的终端设备所处位置的TAI不属于终端设备的TAL时，终端设备向目标RAN节点发送RRC连接恢复请求(RRC connection resume request)消息。
该步骤详细描述参见S401，具体不再赘述。
S602、目标RAN节点从终端设备接收RRC连接恢复请求消息，向源RAN节点发送获取用户设备上下文请求(retrieve UE context request)消息，该获取用户设备上下文请求消息用于获取终端设备的上下文信息。
其中，该步骤为步骤S402和S403的结合，具体不再赘述。
S603、源RAN节点从目标RAN节点接收获取用户设备上下文请求消息，向目标RAN节点发送获取用户设备上下文响应消息，获取用户设备上下文响应消息中包括终端设备的上下文信息。
该步骤为步骤S404和S414的结合，具体不再赘述。
S604、当目标RAN节点接收到来自源RAN节点的终端设备的上下文信息时，目标RAN节点向终端设备发送RRC连接恢复消息，以指示RRC连接恢复成功。
该步骤详细描述参见S415，具体不再赘述。
S605、目标RAN节点向AMF发送路径切换请求(path switch request)消息，路径切换请求消息中携带终端设备的位置信息。
该步骤详细描述参见S416，具体不再赘述。
S606、AMF从目标RAN节点接收路径切换请求消息，根据路径切换请求消息中终端设备的位置信息，确定终端设备所处位置的TAI不属于终端设备的TAL，则AMF为终端设备重新分配TAL，并向目标RAN节点发送路径切换响应(path switch response)消息，路径切换响应消息中包括重新分配的TAL。
该步骤为步骤S417和S418的结合，具体不再赘述。
S607、目标RAN节点从AMF接收路径切换响应消息，向源RAN节点发送用户设备上下文释放(UE context release)消息，用户设备上下文释放消息指示源RAN节点释放终端设备的上下文信息。
该步骤为步骤S419和S420的结合，具体不再赘述。
S608、当目标RAN节点位于不允许区域时，AMF向SMF发送用户设备移动性能通知(UE mobility notification)消息，该消息中包括指示信息，该指示信息用于指示终端设备位于不允许区域(例如，non-allowed area indication)。
该步骤详细描述参见S434，具体不再赘述。
S609、SMF从AMF接收指示信息，根据本地SM策略以及上述指示信息，触发终端设备的PDU会话释放流程或PDU会话去激活流程。
该步骤为步骤S435和S436的结合，具体不再赘述。
通过步骤S609使得终端设备和SMF之间PDU会话状态均为未激活态。
S610、终端设备向AMF发送注册请求消息。
该步骤详细描述参见S412，具体不再赘述。
S611、AMF向终端设备发送注册接受消息。
其中，该注册接受消息携带为终端设备重新分配的TAL。
该步骤详细描述参见S413，具体不再赘述。
本申请实施例提供的通信方法，当处于RRC非激活态的终端设备所处位置的TAI不属于终端设备的TAL时，终端设备向目标RAN节点发起RAN节点级别的注册更新(RAN-level-registration-update)流程。目标RAN节点成功从源RAN节点获取用户设备的上下文，并恢复RRC连接态，目标RAN节点向AMF发起路径切换流程，并通过该流程将重新分配的TAL发送给终端设备。实现了处于RRC非激活态的终端设备进行移动触发的TAU。AMF获知终端设备进入了不允许区域。可以采用一种实现方式，即AMF将终端设备的CM状态保持CM连接态，并且将终端设备进入不允许区域的事件通知给SMF，由SMF决定释放/不释放PDU会话或者去激活PDU会话，目标RAN节点将终端设备维持在RRC未激活态。或者可以采用另一种实现方式，即AMF将终端设备的CM状态保持CM连接态，并且将终端设备进入不允许区域的事件通知给SMF，由SMF决定释放/不释放PDU会话或者去激活PDU会话，目标RAN节点根据策略或者AMF根据策略发起N2释放流程，将终端设备转换为CM空闲态。
可选的，参照图17中所示，在步骤S606所述的AMF向目标RAN节点发送TAL之后，该方法还可以包括步骤S621：
S621、目标RAN节点根据从AMF接收的TAL生成RNA，向终端设备发送RRC连接释放(RRC connection release)消息，RRC连接释放消息中包括RNA。
该步骤为S431和S432的结合，具体不再赘述。
通过步骤S621使得终端设备和AMF之间CM状态维持为CM连接态，通过步骤S621使得终端设备和目标RAN节点之间RRC状态均为RRC未激活态。
该实施方式提供了目标RAN向终端设备发送RAN所采用的消息的一种可能的实现方式。
可选的，参照图17中所示，在步骤S604所述的目标RAN节点接收到来自源RAN节点的用户设备上下文响应消息之后，该方法还可以包括步骤S622：
S622、目标RAN节点根据策略确定将终端设备转换为CM空闲态，目标RAN节点触发AN节点UE上下文释放流程(UE context release in the AN)。
该步骤详细描述参见S433，触发N2上下文释放流程参照步骤S433描述，具体不再赘述。
通过步骤S622使得终端设备和目标RAN节点之间CM状态均为CM连接态。
该实施方式使得目标RAN节点删除终端设备的上下文。
可选的，参照图17中所示，在步骤S606所述的AMF根据终端设备的位置信息确定终端设备当前所处位置的TAI不属于当前跟踪区列表TAL之后，该方法还可以包括步骤S612：
S623、AMF根据策略确定将终端设备转换为CM空闲态，触发AN节点UE上下 文释放流程(UE context release in the AN)。
该步骤详细描述参见S437，触发AN节点UE上下文释放流程(UE context release in the AN)参照步骤S437描述，具体不再赘述。
通过S623使得终端设备和AMF之间的CM状态均为CM空闲态。
该实施方式使得终端设备所处位置的TAI不属于终端设备的TAL时，目标RAN释放UE的上下文。
本申请实施例提供了一种通信方法，该方法可以应用于处于RRC非激活态的终端设备从允许区域移动至不允许区域，并且终端设备的TAI不属于终端设备的TAL时，终端设备进行TAU。参照图18中所示，该方法包括：
S701、当处于RRC非激活态的终端设备所处位置的TAI不属于终端设备的TAL时，终端设备向目标RAN节点发送RRC连接恢复请求(RRC connection resume request)消息。
该步骤与步骤S601相同，具体不再赘述。
S702、目标RAN节点从终端设备接收RRC连接恢复请求消息，向源RAN节点发送获取用户设备上下文请求(retrieve UE context request)消息，该获取用户设备上下文请求消息用于获取终端设备的上下文信息。
该步骤与S602相同，具体不再赘述。
S703、源RAN节点从目标RAN节点接收获取用户设备上下文请求消息，根据本地保存的不允许区域的信息以及目标RAN节点的位置信息确定目标RAN节点位于不允许区域，则决定拒绝请求。
该步骤详细描述参见S404。
S704、源RAN节点向目标RAN节点发送获取用户设备上下文拒绝(retrieve UE context reject)消息，该获取用户设备上下文拒绝消息中携带有拒绝原因，拒绝原因为终端设备位于不允许区域(例如，non-allowed area indication)。
该步骤详细描述参见S405，具体不再赘述。
S705、源RAN节点向AMF发送N2用户设备上下文释放请求(N2 UE context release request)消息，以发起N2释放流程，该消息中携带有请求释放原因，请求释放原因为终端设备位于不允许区域(例如，non-allowed area indication)。
该步骤详细描述参见S406，具体不再赘述。
S706、当目标RAN节点接收到来自源RAN节点的获取用户设备上下文拒绝消息时，目标RAN节点向终端设备发送RRC连接恢复拒绝(RRC connection resume reiect)消息。
该步骤详细描述参见S407。
S707、终端设备从目标RAN节点接收RRC连接恢复拒绝消息，根据RRC连接恢复拒绝消息，从CM连接态转换为CM空闲态。
该步骤为步骤S408和S409的结合，具体不再赘述。
S708、AMF从源RAN节点接收N2用户设备上下文释放请求消息，向SMF发送PDU会话去激活请求消息，PDU会话去激活请求消息用于请求SMF去激活终端设备的PDU会话。
该步骤为步骤S410和S411的结合。
S709、AMF向源RAN节点发送N2用户设备上下文释放命令(N2 UE context release command)消息。
该步骤详细描述参见S412。
S710、源RAN节点从AMF接收N2用户设备上下文释放命令(N2 UE context release command)消息，源RAN节点向AMF发送N2用户设备上下文释放完成(N2 UE context release complete)消息。
该步骤详细描述参见S413。
本申请实施例提供的通信方法，当处于RRC非激活态的终端设备所处位置的TAI不属于该终端设备的TAL时，终端设备向目标RAN节点发起RAN节点级别的注册更新(RAN节点-level-registration-update)流程。目标RAN节点请求从源RAN节点获取用户设备的上下文，源RAN节点发现终端设备进入不允许区域，则拒绝目标RAN节点的请求。可以采用一种实现方式，即源RAN节点拒绝终端设备接入网络，从而使得终端设备进入CM空闲态，并且终端设备的PDU会话处于未激活态。或者可以采用另一种实现方式，即源RAN节点发起N2释放流程，以释放源RAN节点与AMF/UPF之间的N2和N3连接，将终端设备转换为CM空闲态，并且终端设备的PDU会话处于未激活态。
本申请实施例提供一种终端设备，用于执行上述通信方法。本申请实施例可以根据上述方法示例对终端设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用对应各个功能划分各个功能模块的情况下，图19示出了上述实施例中所涉及的终端设备的一种可能的结构示意图，终端设备100包括：接收单元1011、转换单元1012、发送单元1013。接收单元1011用于支持终端设备100执行图3中的过程S110，图4中的过程S110，图5中的过程S110，图6中的过程S110，图8中的过程S305，图9中的过程S408，图10中的过程S408，图12中的过程S408，图13中的过程S408，图15中的过程S513；转换单元1012用于支持终端设备100执行图3中的过程S101，图4中的过程S101，图5中的过程S101，图6中的过程S101，图9中的过程S409，图10中的过程S409，图12中的过程S409，图13中的过程S409，图15中的过程S501，图18中的过程S707；发送单元1013用于支持终端设备100执行图3中的过程S102，图4中的过程S102，图5中的过程S102，图6中的过程S102，图8中的过程S305，图9中的过程S401、S413和S421，图10中的过程S401、S413和S421，图12中的过程S401、S413和S421，图13中的过程S401、S413和S421，图15中的过程S502，图16中的过程S601和S610，图17中的过程S601和S610，图18中的过程S701和S710。其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在采用集成的单元的情况下，图20示出了上述实施例中所涉及的终端设备的一种 可能的结构示意图。终端设备100包括：处理模块1022和通信模块1023。处理模块1022用于对终端设备100的动作进行控制管理，例如，处理模块1022用于支持终端设备100执行图3中的过程S101，图4中的过程S101，图5中的过程S101，图6中的过程S101，图9中的过程S409，图10中的过程S409，图12中的过程S409，图13中的过程S409，图15中的过程S501，图18中的过程S707。通信模块1023用于支持终端设备与其他实体的通信，例如与图1中示出的功能模块或网络实体之间的通信。终端设备100还可以包括存储模块1021，用于存储终端设备的程序代码和数据。
其中，处理模块1022可以是处理器或控制器，例如可以是中央处理器(Central processing unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块1023可以是收发器、收发电路或通信接口等。存储模块1021可以是存储器。
具体的，处理模块1022可以为图2中的处理器1001，通信模块1023可以为图2中的收发器1003，存储模块1021可以为图2中的存储器1002。
本申请实施例提供一种RAN节点，用于执行上述通信方法。本申请实施例可以根据上述方法示例对RAN节点进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用对应各个功能划分各个功能模块的情况下，图21示出了上述实施例中所涉及的RAN节点的一种可能的结构示意图，RAN节点200包括：接收单元2011、生成单元2012、删除单元2013、释放单元2014、发送单元2015。接收单元2011用于支持RAN节点200执行图3中的过程S105、图4中的过程S105，图5中的过程S105，图6中的过程S105，图8中的过程S305，图9中的过程S402、S404、S419，图10中的过程S402、S404、S419，图12中的过程S402、S404、S419，图13中的过程S402、S404、S419，图15中的过程S513；生成单元2012用于支持RAN节点200执行图10中的过程S431，图17中的过程S621；删除单元2013用于支持RAN节点200执行图3中的过程S106，图4中的过程S106，图5中的过程S106，图6中的过程S106，图15中的过程S510；释放单元2014用于支持RAN节点200执行图11中的过程S4337，图14中的过程S4376；发送单元2013用于支持RAN节点200执行图3中的过程S107，图4中的过程S107，图5中的过程S107，图6中的过程S107，图8中的过程S305和S306，图9中的过程S403、S406、S407、S414、S415和S420，图10中的过程S403、S406、S407、S414、S432、S433、S415和S420，图11中的过程S4331和S4337，图12中的过程S403、S406、S407、S414、S415和S420，图13中的过程S403、S406、S407、S414、S415和S420，图14中的过程S4376，图15中的过程S511，图16中的 过程S602、S603、S604、S605、S607，图17中的过程S602、S603、S604、S622、S605、S621，图18中的过程S702、S704、S705、S706。其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在采用集成的单元的情况下，图22示出了上述实施例中所涉及的RAN节点的一种可能的结构示意图。RAN节点200包括：处理模块2022和通信模块2023。处理模块2022用于对RAN节点200的动作进行控制管理，例如，处理模块2022用于支持RAN节点200执行图10中的过程S431，图17中的过程S621，图3中的过程S106，图4中的过程S106，图5中的过程S106，图6中的过程S106，图15中的过程S510，图11中的过程S4337，图14中的过程S4376。通信模块1023用于支持RAN节点与其他实体的通信，例如与图1中示出的功能模块或网络实体之间的通信。RAN节点200还可以包括存储模块2021，用于存储RAN节点的程序代码和数据。
其中，处理模块2022可以是处理器或控制器，例如可以是中央处理器(Central processing unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块2023可以是收发器、收发电路或通信接口等。存储模块2021可以是存储器。
具体的，处理模块2022可以为图2中的处理器2001，通信模块2023可以为图2中的收发器2003或网络接口2004，存储模块2021可以为图2中的存储器2002。
本申请实施例提供一种AMF，用于执行上述通信方法。本申请实施例可以根据上述方法示例对AMF进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用对应各个功能划分各个功能模块的情况下，图23示出了上述实施例中所涉及的AMF的一种可能的结构示意图，AMF 400包括：接收单元4011、确定单元4012、设置单元4013、发送单元4014。接收单元4011用于支持AMF 400执行图3中的过程S103和S108，图4中的过程S103、S121和S108，图5中的过程S103、S121和S108，图6中的过程S103、S121和S108，图9中的过程S410和S417，图10中的过程S410和S417，图12中的过程S410和S417，图13中的过程S410和S417，图15中的过程S503和S512；确定单元4012用于支持AMF 400执行图4中的过程S122，图5中的过程S122，图6中的过程S122，图9中的过程S418，图15中的过程S504，图16中的过程S606，图17中的过程S606；设置单元4013用于支持AMF 400执行图4中的过程S123，图5中的过程S123，图6中的过程S123；发送单元4013用于支持AMF 400执行图3中的过程S104，图4中的过程S104，图5中的过程S104和S131，图6中的过程S104和S132，图7中的过程S204，图8中的过程S304和S307，图9中的过程 S411、S412、S418、S422，图10中的过程S411、S412、S418、S422，图10中的过程S4332、S4336，图12中的过程S411、S412、S418、S422、S434，图13中的过程S411、S412、S418、S422、S437，图14中的过程S4371、S4375，图15中的过程S505、S506、S505、S509、S512，图16中的过程S606、S608、S611，图17中的过程S606、S608、S611、S623，图18中的过程S708和S709。其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在采用集成的单元的情况下，图24示出了上述实施例中所涉及的AMF的一种可能的结构示意图。AMF 400包括：处理模块4022和通信模块4023。处理模块4022用于对AMF 400的动作进行控制管理，例如，处理模块4022用于支持AMF 400执行图4中的过程S122，图5中的过程S122，图6中的过程S122，图9中的过程S418，图15中的过程S504，图16中的过程S606，图17中的过程S606，图4中的过程S123，图5中的过程S123，图6中的过程S123。通信模块1023用于支持AMF与其他实体的通信，例如与图1中示出的功能模块或网络实体之间的通信。AMF 400还可以包括存储模块4021，用于存储AMF的程序代码和数据。
其中，处理模块4022可以是处理器或控制器，例如可以是中央处理器(Central processing unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块4023可以是收发电路或通信接口等。存储模块4021可以是存储器。
具体的，处理模块4022可以为图2中的处理器3001，通信模块4023可以为图2中的网络接口3003，存储模块4021可以为图2中的存储器3002。
本申请实施例提供一种SMF，用于执行上述通信方法。本申请实施例可以根据上述方法示例对SMF进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用对应各个功能划分各个功能模块的情况下，图25示出了上述实施例中所涉及的SMF的一种可能的结构示意图，SMF 500包括：接收单元5011、发送单元5012。接收单元5011用于支持SMF 500执行图6中的过程S133，图12中的过程S435，图15中的过程S507；发送单元5012用于支持SMF 500执行图6中的过程S134，图7中的过程S201、S203、S205，图8中的过程S301、S303，图12中的过程S436，图14中的过程S4372、S4374，图15中的过程S508，图16中的过程S609，图17中的过程S609。其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在采用集成的单元的情况下，图26示出了上述实施例中所涉及的SMF的一种可 能的结构示意图。SMF 500包括：处理模块5022和通信模块5023。处理模块5022用于对SMF 500的动作进行控制管理。通信模块1023用于支持SMF与其他实体的通信，例如与图1中示出的功能模块或网络实体之间的通信。SMF 500还可以包括存储模块5021，用于存储SMF的程序代码和数据。
其中，处理模块5022可以是处理器或控制器，例如可以是中央处理器(Central processing unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块5023可以是收发电路或通信接口等。存储模块5021可以是存储器。
具体的，处理模块5022可以为图2中的处理器3001，通信模块5023可以为图2中的网络接口3003，存储模块5021可以为图2中的存储器3002。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，具体不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、设备和方法，可以通过其它的方式实现。例如，以上所描述的设备实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，设备或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令 时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(Solid State Disk，SSD))等。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (34)

  1. 一种通信方法，其特征在于，所述方法包括：
    当处于无线资源控制RRC非激活态的终端设备所处位置的TAI不属于所述终端设备的跟踪区列表TAL时，所述终端设备转换为连接管理CM空闲态；
    所述终端设备通过目标无线接入网络RAN节点向接入和移动性管理功能AMF发送注册请求消息，所述注册请求消息用于请求为所述终端设备分配TAL；
    所述终端设备通过所述目标RAN节点接收由所述AMF发送的注册接受消息，所述注册接受消息中包括所述分配的TAL。
  2. 根据权利要求1所述的方法，其特征在于，所述终端设备所处位置的TAI对应的区域为不允许区域，所述跟踪区列表TAL对应的区域为允许区域。
  3. 一种通信方法，其特征在于，所述方法包括：
    接入和移动性管理功能AMF从目标无线接入网络RAN节点接收注册请求消息，所述注册请求消息用于请求为终端设备分配跟踪区列表TAL，所述终端设备处于无线资源控制RRC非激活态；
    所述AMF向源RAN节点发送N2用户设备上下文释放命令消息；
    所述AMF接收由所述源RAN节点发送的N2用户设备上下文释放完成消息；
    所述AMF通过所述目标RAN节点向所述终端设备发送注册接受消息，所述注册接受消息中包括所述TAL。
  4. 根据权利要求3所述的方法，其特征在于，所述方法还包括：
    所述AMF从所述目标RAN节点接收所述终端设备的位置信息；
    所述AMF根据所述终端设备的位置信息以及所述终端设备的上下文中的不允许区域，确定所述终端设备位于不允许区域；
    所述AMF将所述终端设备设置为连接管理CM空闲态。
  5. 根据权利要求4所述的方法，其特征在于，所述方法还包括：
    所述AMF向会话管理功能SMF发送分组数据单元PDU会话去激活请求消息，所述PDU会话去激活请求消息用于请求所述SMF去激活所述终端设备的PDU会话；或者，
    所述AMF向所述SMF发送指示信息，其中，所述指示信息用于指示所述终端设备位于不允许区域。
  6. 根据权利要求3-5任一项所述的方法，其特征在于，所述N2用户设备上下文释放命令消息中包括释放原因，所述释放原因用于指示所述终端设备位于不允许区域。
  7. 一种通信方法，其特征在于，包括：
    会话管理功能SMF从接入和移动性管理功能AMF接收指示信息，所述指示信息用于指示终端设备位于不允许区域；
    所述SMF根据本地会话管理SM策略以及所述指示信息，触发所述终端设备的PDU会话释放流程或PDU会话去激活流程。
  8. 一种通信方法，其特征在于，所述方法包括：
    当处于无线资源控制RRC非激活态的终端设备所处位置的TAI不属于所述终端设备的跟踪区列表TAL时，所述终端设备向目标无线接入网络RAN节点发送无线资 源控制RRC连接恢复请求消息，所述终端设备处于RRC非激活态；
    所述终端设备从所述目标RAN节点接收RRC连接恢复拒绝消息；
    所述终端设备根据所述RRC连接恢复拒绝消息，从连接管理CM连接态转换为CM空闲态。
  9. 根据权利要求8所述的方法，其特征在于，所述目标RAN节点位于不允许区域。
  10. 一种通信方法，其特征在于，所述方法包括：
    目标无线接入网络RAN节点从终端设备接收无线资源控制RRC连接恢复请求消息，所述终端设备处于RRC非激活态；
    所述目标RAN节点向源RAN节点发送获取用户设备上下文请求消息，所述获取用户设备上下文请求消息用于获取所述终端设备的上下文信息；
    当所述目标RAN节点接收到来自所述源RAN节点的所述终端设备的上下文信息时，所述目标RAN节点向所述终端设备发送RRC连接恢复消息，向接入和移动性管理功能AMF发送路径切换请求消息，从所述AMF接收路径切换响应消息，并向所述源RAN节点发送用户设备上下文释放消息；或者，
    当所述目标RAN节点接收到来自所述源RAN节点的获取用户设备上下文拒绝消息时，或者，当所述目标RAN节点接收到来自所述源RAN节点的获取用户设备上下文响应消息，并且所述获取用户设备上下文响应消息携带有用于指示获取上下文信息失败的失败指示信息时，所述目标RAN节点向所述终端设备发送RRC连接恢复拒绝消息。
  11. 根据权利要求10所述的方法，其特征在于，所述路径切换响应消息中包括为所述终端设备重新分配的跟踪区列表TAL，所述方法还包括：
    所述目标RAN节点根据所述TAL生成RAN通知区域RNA；
    所述目标RAN节点向所述终端设备发送所述RNA。
  12. 根据权利要求10或11所述的方法，其特征在于，所述目标RAN节点位于不允许区域，在所述目标RAN节点接收到来自所述源RAN节点的所述终端设备的上下文信息之后，所述方法还包括：
    所述目标RAN节点触发接入网络AN节点用户设备上下文释放流程；
    所述目标RAN节点删除所述终端设备的上下文信息。
  13. 一种通信方法，其特征在于，所述方法包括：
    接入和移动性管理功能AMF从目标无线接入网络RAN节点接收路径切换请求消息，所述路径切换请求消息中携带终端设备的位置信息；
    所述AMF根据所述终端设备的位置信息，确定所述终端设备所处位置的TAI不属于所述终端设备的跟踪区列表TAL；
    所述AMF为所述终端设备重新分配TAL，并向所述目标RAN节点发送所述重新分配的TAL。
  14. 根据权利要求13所述的方法，其特征在于，所述向所述目标RAN节点发送所述重新分配的TAL，包括：
    所述AMF向所述目标RAN节点发送路径切换响应消息，所述路径切换响应消息 中包括所述重新分配的TAL。
  15. 根据权利要求13或14所述的方法，其特征在于，所述方法还包括：
    当所述目标RAN节点位于不允许区域时，所述AMF向会话管理功能SMF发送指示信息，所述指示信息用于指示所述终端设备位于不允许区域；或者，
    所述AMF触发接入网络AN节点用户设备上下文释放流程。
  16. 一种通信方法，其特征在于，所述方法包括：
    源无线接入网络RAN节点从目标RAN节点接收获取用户设备上下文请求消息，所述获取用户设备上下文请求消息用于获取终端设备的上下文信息，所述终端设备处于无线资源控制RRC非激活态；
    当所述目标RAN节点位于不允许区域时，所述源RAN节点向所述目标RAN节点发送获取用户设备上下文拒绝消息；或者，当所述目标RAN节点位于不允许区域时，所述源RAN节点向所述目标RAN节点发送获取用户设备上下文响应消息，所述获取用户设备上下文响应消息中携带失败指示信息，所述失败指示信息用于指示获取所述终端设备的上下文信息的失败原因；
    所述源RAN节点向接入和移动性管理功能AMF发送N2用户设备上下文释放请求消息。
  17. 根据权利要求16所述的方法，其特征在于，所述获取用户设备上下文拒绝消息中携带有拒绝原因，所述拒绝原因为所述终端设备位于不允许区域；所述N2用户设备上下文释放请求消息中携带有请求释放原因，所述请求释放原因为所述终端设备位于不允许区域；或者，
    所述失败指示信息用于指示所述终端设备位于不允许区域；所述N2用户设备上下文释放请求消息中携带有请求释放原因，所述请求释放原因为所述终端设备位于不允许区域。
  18. 一种终端设备，其特征在于，包括：
    转换单元，用于当处于无线资源控制RRC非激活态的终端设备所处位置的TAI不属于所述终端设备的跟踪区列表TAL时，将所述终端设备转换为连接管理CM空闲态；
    发送单元，用于通过目标无线接入网络RAN节点向接入和移动性管理功能AMF发送注册请求消息，所述注册请求消息用于请求为所述终端设备分配TAL；
    接收单元，用于通过所述目标RAN节点接收由所述AMF发送的注册接受消息，所述注册接受消息中包括所述分配的TAL。
  19. 根据权利要求18所述的终端设备，其特征在于，所述终端设备所处位置的TAI对应的区域为不允许区域，所述跟踪区列表TAL对应的区域为允许区域。
  20. 一种接入和移动性管理功能AMF，其特征在于，包括：
    接收单元，用于从目标无线接入网络RAN节点接收注册请求消息，所述注册请求消息用于请求为终端设备分配跟踪区列表TAL，所述终端设备处于无线资源控制RRC非激活态；
    发送单元，用于向源RAN节点发送N2用户设备上下文释放命令消息；
    接收单元，用于接收由所述源RAN节点发送的N2用户设备上下文释放完成消息；
    所述发送单元，还用于通过所述目标RAN节点向所述终端设备发送注册接受消息，所述注册接受消息中包括所述TAL。
  21. 根据权利要求20所述的AMF，其特征在于，所述AMF还包括确定单元和设置单元，
    所述接收单元，还用于从所述目标RAN节点接收所述终端设备的位置信息；
    所述确定单元，还用于根据所述终端设备的位置信息以及终端设备的上下文中的不允许区域，确定所述终端设备位于不允许区域；
    所述设置单元，还用于将所述终端设备设置为连接管理CM空闲态。
  22. 根据权利要求21所述的AMF，其特征在于，所述发送单元，还用于：
    向会话管理功能SMF发送分组数据单元PDU会话去激活请求消息，所述PDU会话去激活请求消息用于请求所述SMF去激活所述终端设备的PDU会话；或者，
    向所述SMF发送指示信息，其中，所述指示信息用于指示所述终端设备位于不允许区域。
  23. 根据权利要求20-22任一项所述的AMF，其特征在于，所述N2用户设备上下文释放命令消息中包括释放原因，所述释放原因用于指示所述终端设备位于不允许区域。
  24. 一种会话管理功能SMF，其特征在于，包括：
    接收单元，用于从接入和移动性管理功能AMF接收指示信息，所述指示信息用于指示终端设备位于不允许区域；
    发送单元，用于根据本地会话管理SM策略以及所述指示信息，触发所述终端设备的PDU会话释放流程或PDU会话去激活流程。
  25. 一种终端设备，其特征在于，包括：
    发送单元，用于当处于无线资源控制RRC非激活态的终端设备所处位置的TAI不属于所述终端设备的跟踪区列表TAL时，向目标无线接入网络RAN节点发送无线资源控制RRC连接恢复请求消息，所述终端设备处于RRC非激活态；
    接收单元，用于从所述目标RAN节点接收RRC连接恢复拒绝消息；
    转换单元，用于根据所述RRC连接恢复拒绝消息，从连接管理CM连接态转换为CM空闲态。
  26. 根据权利要求25所述的终端设备，其特征在于，所述目标RAN节点位于不允许区域。
  27. 一种目标无线接入网络RAN节点，其特征在于，包括：
    接收单元，用于从终端设备接收无线资源控制RRC连接恢复请求消息，所述终端设备处于RRC非激活态；
    发送单元，用于向源RAN节点发送获取用户设备上下文请求消息，所述获取用户设备上下文请求消息用于获取所述终端设备的上下文信息；
    当所述目标RAN节点接收到来自所述源RAN节点的所述终端设备的上下文信息时，所述发送单元，还用于向所述终端设备发送RRC连接恢复消息，向接入和移动性管理功能AMF发送路径切换请求消息，所述接收单元，还用于从所述AMF接收路径切换响应消息，所述发送单元，还用于向所述源RAN节点发送用户设备上下文释放消 息；或者，
    当所述目标RAN节点接收到来自所述源RAN节点的获取用户设备上下文拒绝消息时，或者，当所述目标RAN节点接收到来自所述源RAN节点的获取用户设备上下文响应消息，并且所述获取用户设备上下文响应消息携带有用于指示获取上下文信息失败的失败指示信息时，所述发送单元，还用于向所述终端设备发送RRC连接恢复拒绝消息。
  28. 根据权利要求27所述的目标RAN节点，其特征在于，所述目标RAN节点还包括生成单元，所述路径切换响应消息中包括为所述终端设备重新分配的跟踪区列表TAL，
    所述生成单元，还用于根据所述TAL生成RAN通知区域RNA；
    所述发送单元，还用于向所述终端设备发送所述RNA。
  29. 根据权利要求27或28所述的目标RAN节点，其特征在于，所述目标RAN节点位于不允许区域，所述目标RAN节点还包括删除单元，在所述目标RAN节点接收到来自所述源RAN节点的所述终端设备的上下文信息之后，
    所述发送单元，还用于触发接入网络AN节点用户设备上下文释放流程；
    所述删除单元用于删除所述终端设备的上下文信息。
  30. 一种接入和移动性管理功能AMF，其特征在于，包括：
    接收单元，用于从目标无线接入网络RAN节点接收路径切换请求消息，所述路径切换请求消息中携带终端设备的位置信息；
    确定单元，用于根据所述终端设备的位置信息，确定所述终端设备所处位置的TAI不属于所述终端设备的跟踪区列表TAL；
    发送单元，用于为所述终端设备重新分配TAL，并向所述目标RAN节点发送所述重新分配的TAL。
  31. 根据权利要求30所述的AMF，其特征在于，所述发送单元，具体用于：
    向所述目标RAN节点发送路径切换响应消息，所述路径切换响应消息中包括所述重新分配的TAL。
  32. 根据权利要求30或31所述的AMF，其特征在于，所述发送单元还用于：
    当所述目标RAN节点位于不允许区域时，向会话管理功能SMF发送指示信息，所述指示信息用于指示所述终端设备位于不允许区域；或者，
    触发接入网络AN节点用户设备上下文释放流程。
  33. 一种源无线接入网络RAN节点，其特征在于，包括：
    接收单元，用于从目标RAN节点接收获取用户设备上下文请求消息，所述获取用户设备上下文请求消息用于获取终端设备的上下文信息，所述终端设备处于无线资源控制RRC非激活态；
    发送单元，用于当所述目标RAN节点位于不允许区域时，向所述目标RAN节点发送获取用户设备上下文拒绝消息；或者，当所述目标RAN节点位于不允许区域时，向所述目标RAN节点发送获取用户设备上下文响应消息，所述获取用户设备上下文响应消息中携带失败指示信息，所述失败指示信息用于指示获取所述终端设备的上下文信息的失败原因；
    所述发送单元，还用于向接入和移动性管理功能AMF发送N2用户设备上下文释放请求消息。
  34. 根据权利要求33所述的源RAN节点，其特征在于，所述获取用户设备上下文拒绝消息中携带有拒绝原因，所述拒绝原因为所述终端设备位于不允许区域；所述N2用户设备上下文释放请求消息中携带有请求释放原因，所述请求释放原因为所述终端设备位于不允许区域；或者，
    所述失败指示信息用于指示所述终端设备位于不允许区域；所述N2用户设备上下文释放请求消息中携带有请求释放原因，所述请求释放原因为所述终端设备位于不允许区域。
PCT/CN2018/088280 2017-08-15 2018-05-24 通信方法、装置和系统 WO2019033817A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP18845793.1A EP3661315A4 (en) 2017-08-15 2018-05-24 COMMUNICATION METHOD, DEVICE AND SYSTEM
BR112020003079-1A BR112020003079A2 (pt) 2017-08-15 2018-05-24 método, dispositivo, e sistema de comunicação
US16/791,962 US20200187144A1 (en) 2017-08-15 2020-02-14 Communication method, apparatus, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710699045.6 2017-08-15
CN201710699045.6A CN109548099B (zh) 2017-08-15 2017-08-15 通信方法、装置和系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/791,962 Continuation US20200187144A1 (en) 2017-08-15 2020-02-14 Communication method, apparatus, and system

Publications (1)

Publication Number Publication Date
WO2019033817A1 true WO2019033817A1 (zh) 2019-02-21

Family

ID=65361702

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/088280 WO2019033817A1 (zh) 2017-08-15 2018-05-24 通信方法、装置和系统

Country Status (5)

Country Link
US (1) US20200187144A1 (zh)
EP (1) EP3661315A4 (zh)
CN (1) CN109548099B (zh)
BR (1) BR112020003079A2 (zh)
WO (1) WO2019033817A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10999702B2 (en) * 2016-07-29 2021-05-04 China Academy Of Telecommunications Technology Method for managing wireless system area, terminal and base station
EP4044683A4 (en) * 2019-10-10 2022-10-26 Huawei Technologies Co., Ltd. METHOD, DEVICE AND SYSTEM FOR SERVICE PROCESSING

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109547932B (zh) * 2017-08-15 2023-05-16 华为技术有限公司 一种通信方法及装置
WO2019056271A1 (zh) * 2017-09-21 2019-03-28 北京小米移动软件有限公司 网络连接方法及装置
CN112399507B (zh) * 2019-08-16 2022-08-19 华为技术有限公司 用于传输数据的方法、终端设备和网络设备
US11824881B2 (en) 2020-04-15 2023-11-21 T-Mobile Usa, Inc. On-demand security layer for a 5G wireless network
US11799878B2 (en) 2020-04-15 2023-10-24 T-Mobile Usa, Inc. On-demand software-defined security service orchestration for a 5G wireless network
US11444980B2 (en) 2020-04-15 2022-09-13 T-Mobile Usa, Inc. On-demand wireless device centric security for a 5G wireless network
US11070982B1 (en) 2020-04-15 2021-07-20 T-Mobile Usa, Inc. Self-cleaning function for a network access node of a network
US11057774B1 (en) 2020-05-14 2021-07-06 T-Mobile Usa, Inc. Intelligent GNODEB cybersecurity protection system
US11115824B1 (en) 2020-05-14 2021-09-07 T-Mobile Usa, Inc. 5G cybersecurity protection system
US11206542B2 (en) 2020-05-14 2021-12-21 T-Mobile Usa, Inc. 5G cybersecurity protection system using personalized signatures
CN113825186B (zh) * 2020-06-19 2023-08-01 维沃移动通信有限公司 离开网络的控制方法、装置和通信设备
EP4195801A4 (en) * 2020-08-05 2023-10-04 Guangdong Oppo Mobile Telecommunications Corp., Ltd. CELL ACCESS SELECTION METHOD, TERMINAL DEVICE AND NETWORK DEVICE
CN114126090B (zh) * 2020-08-26 2024-01-12 大唐移动通信设备有限公司 上行数据处理方法、装置、网络设备、终端设备及介质
KR20230074708A (ko) * 2020-09-28 2023-05-31 광동 오포 모바일 텔레커뮤니케이션즈 코포레이션 리미티드 네트워크 선택 방법, 전자 기기 및 저장 매체
CN116134839A (zh) * 2020-10-14 2023-05-16 Oppo广东移动通信有限公司 一种通信方法及相关设备
US20230337323A1 (en) * 2021-03-02 2023-10-19 Samsung Electronics Co., Ltd. Method and system for releasing pdu session
KR20240015618A (ko) * 2021-06-05 2024-02-05 광동 오포 모바일 텔레커뮤니케이션즈 코포레이션 리미티드 단말 기기가 위치한 추적 영역을 지시하는 방법 및 네트워크 기기
GB2609487B (en) * 2021-08-05 2023-11-22 Vodafone Group Services Ltd Registration request handling in a cellular network

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106658758A (zh) * 2017-02-10 2017-05-10 北京小米移动软件有限公司 状态转换方法、状态保持方法、装置及用户设备

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102572783B (zh) * 2007-05-11 2014-12-10 华为技术有限公司 一种注册处理方法、系统及装置
CN101489209A (zh) * 2008-01-17 2009-07-22 华为技术有限公司 一种注册区的更新方法和设备
JP4690429B2 (ja) * 2008-02-05 2011-06-01 株式会社エヌ・ティ・ティ・ドコモ 位置登録方法、移動通信システム及び無線基地局
EP2326110A1 (en) * 2009-11-19 2011-05-25 Thomson Licensing, Inc. BM-SC for broadcasting services through a wireless communication network and/or a digital broadcasting network extension, and associated method
KR101090602B1 (ko) * 2010-01-29 2011-12-08 주식회사 팬택 페이징 영역 관리 방법 및 장치

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106658758A (zh) * 2017-02-10 2017-05-10 北京小米移动软件有限公司 状态转换方法、状态保持方法、装置及用户设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ANONYMOUS: "3GPP Standard; 3GPP TR 23.799", 3RD GENERATION PARTNERSHIP PROJECT; TECHNICAL SPECIFICATION GROUP SERVICES AND SYSTEM ASPECTS; STUDY ON ARCHITECTURE FOR NEXT GENERATION SYSTEM (RELEASE 14), vol. SA WG2, no. V14.0.0, 16 December 2016 (2016-12-16), pages 1 - 522, XP051230010 *
See also references of EP3661315A4

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10999702B2 (en) * 2016-07-29 2021-05-04 China Academy Of Telecommunications Technology Method for managing wireless system area, terminal and base station
EP4044683A4 (en) * 2019-10-10 2022-10-26 Huawei Technologies Co., Ltd. METHOD, DEVICE AND SYSTEM FOR SERVICE PROCESSING

Also Published As

Publication number Publication date
CN109548099A (zh) 2019-03-29
EP3661315A1 (en) 2020-06-03
BR112020003079A2 (pt) 2020-08-25
US20200187144A1 (en) 2020-06-11
CN109548099B (zh) 2021-02-05
EP3661315A4 (en) 2020-08-05

Similar Documents

Publication Publication Date Title
WO2019033817A1 (zh) 通信方法、装置和系统
EP3709707B1 (en) Slice information update method and apparatus
US11432366B2 (en) Session management method, device, and system
JP6701446B2 (ja) セッション管理機能エンティティ選択方法、機器、及びシステム
US20200015131A1 (en) Communication method and communications device
JP7097894B2 (ja) 負荷再配置方法、装置、およびシステム
WO2018171107A1 (zh) 一种通信系统间移动方法、设备和系统
US20220346190A1 (en) Session Management Method, Device, and System
WO2019137553A1 (zh) 一种配置ue的策略的方法、装置和系统
WO2019158010A1 (zh) 资源管理的方法、设备及系统
WO2019062830A1 (zh) 实例业务拓扑的生成方法及装置
EP3700252A1 (en) Communication method and device
WO2019184723A1 (zh) 策略和计费控制规则获取方法、装置及系统
US20220377653A1 (en) Slice information update method and apparatus
WO2019223702A1 (zh) 管理pdu会话的方法、装置和系统
WO2018000202A1 (zh) 一种负载迁移方法、装置及系统
WO2019096306A1 (zh) 一种处理请求的方法以及相应实体
US20220248290A1 (en) Communication Method and Communications Apparatus
CN114270944B (zh) 业务处理方法、设备及系统
JP7145197B2 (ja) ハンドオーバ方法、デバイス及びシステム
CN108924959A (zh) 无线通信的方法、amf和ran
CN110913415B (zh) 测量配置信息、测量报告信息的发送方法及装置
WO2019210779A1 (zh) 切换方法、设备及系统
CN116887349A (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: 18845793

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112020003079

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 2018845793

Country of ref document: EP

Effective date: 20200226

ENP Entry into the national phase

Ref document number: 112020003079

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20200213