Terminal state management method and device

Abstract

The embodiment of the invention provides a terminal state management method and device, and the method applied to an access network device comprises the steps: managing the terminal state of a terminal, the terminal state is related to a first connection state and a second connection state, the first connection state is the connection state of an RAN device and the terminal, and the second connection state is the connection state of the RAN device and the terminal. The second connection state is a connection state between the terminal and a core network (CN). The terminal state management method provided by the embodiment of the invention can be applied to an RAN service scene, the terminal state is managed by the access network equipment, and the core network does not need to manage the connection state of the UE, so that the state of the UE is simplified, the interaction process is simplified, and the signaling interaction is reduced; and on the other hand, the problem of UE state synchronization between core networks NFs after RAN servitization is avoided.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method and device for managing terminal status. Background Art

[0002] In the existing method, the state of the user equipment (User Equipment, UE for short) is managed by the access and mobility management function (Access and Mobility Management Function, AMF).

[0003] After the Radio Access Network (RAN) is service-oriented, no solution has been proposed for the state management method of UE after the RAN is service-oriented. Summary of the invention

[0004] The embodiments of the present application provide a method and device for managing terminal status, so as to solve the problem that there is no solution for the status management method of UE after RAN service in the prior art.

[0005] In a first aspect, an embodiment of the present application provides a method for managing a terminal state, which is applied to an access network RAN ​​device, including:

[0006] A terminal state of a management terminal is related to a first connection state and a second connection state, wherein the first connection state is a connection state between the RAN device and the terminal, and the second connection state is a connection state between the terminal and a core network CN.

[0007] Optionally, the terminal state includes a connected state, an idle state, and an inactive state; or the terminal state includes a connected state and an inactive state;

[0008] Wherein, in the connected state, the RAN device saves the terminal context of the terminal, a radio resource control RRC connection between the RAN device and the terminal has been established, a connection between the terminal and the CN has been established, and a connection between the RAN device and the CN has been established;

[0009] In the idle state, the RAN device saves the terminal context other than the access layer context of the terminal, the RRC connection between the RAN device and the terminal is disconnected, and the connection between the RAN device and the CN is maintained;

[0010] In the inactive state, the RAN device saves the terminal context of the terminal, the RRC connection between the RAN device and the terminal is suspended, and the connection between the RAN device and the CN is maintained.

[0011] Optionally, the terminal status of the management terminal includes:

[0012] The terminal state migration is performed according to the change of the connection between the terminal and the RAN device.

[0013] Optionally, performing terminal state migration according to a change in a connection between the terminal and the RAN device includes at least one of the following:

[0014] When the terminal state is the connected state, after the RRC connection between the RAN device and the terminal is released, the terminal state is migrated from the connected state to the idle state; or

[0015] When the terminal state is the connected state, after the RRC connection between the RAN device and the terminal is suspended, the terminal state is migrated from the connected state to the inactive state; or

[0016] When the terminal state is the idle state, after the RRC connection between the RAN device and the terminal is established, the terminal state is migrated from the idle state to the connected state; or

[0017] When the terminal state is the inactive state, after the RRC connection between the RAN device and the terminal is restored, the terminal state is migrated from the inactive state to the connected state; or

[0018] When the terminal state is the inactive state, after the RRC connection between the RAN device and the terminal is released, the terminal state is migrated from the inactive state to the idle state.

[0019] Optionally, the method further comprises:

[0020] Manage whether the terminal is reachable in different terminal states.

[0021] Optionally, the managing whether the terminal is reachable in different terminal states includes but is not limited to at least one of the following:

[0022] When the terminal state is connected, the terminal is reachable; or

[0023] In the case where the terminal is in an idle state or an inactive state, determining whether the terminal is reachable according to whether the terminal applies a MICO mode in which only the terminal initiates a connection; or

[0024] When the terminal is in an idle state, starting a mobile reachable timer, and determining whether the terminal is reachable according to whether the mobile reachable timer times out; or

[0025] When the terminal is in an inactive state, a protection timer is started, and whether the terminal is reachable is determined according to whether the protection timer times out.

[0026] Optionally, the method further includes but is not limited to at least one of the following:

[0027] In the case where the terminal is in an idle state and the terminal does not apply the MICO mode, initiating a paging process for the UE according to a paging trigger condition; or

[0028] When the terminal is in an idle state, configuring a periodic RRC establishment timer for the terminal, where the periodic RRC establishment timer is used to indicate a first timer value, and the first timer value is used to instruct the terminal to perform an RRC establishment procedure; or

[0029] In a case where the terminal is in an inactive state and the terminal does not apply the MICO mode, initiating a paging process for the UE according to a paging trigger condition; or

[0030] When the terminal is in an inactive state, a periodic notification area update timer is configured for the terminal, and the periodic notification area update timer is used to indicate a second timer value, and the second timer value is used to instruct the terminal to execute a wireless access network notification area RNA update process.

[0031] Optionally, the mobile reachable timer is used to indicate a third timer value, the third timer value is longer than the first timer value, and when the mobile reachable timer exceeds the third timer value, a deregistration process is triggered to deregister the terminal from the CN; and / or

[0032] The protection timer is used to indicate a fourth timer value, where the fourth timer value is longer than the second timer value. When the protection timer exceeds the fourth timer value, the RRC connection with the terminal is released.

[0033] Optionally, when the terminal state is the connected state, the location information of the terminal known by the RAN device is of a first granularity;

[0034] When the terminal state is the idle state, the location information of the terminal known by the RAN device is of a second granularity;

[0035] When the terminal state is the inactive state, the location information of the terminal known by the RAN device is of the third granularity.

[0036] Optionally, the terminal status of the management terminal includes:

[0037] In a case where it is determined to migrate the terminal state from the connected state to the idle state, or to maintain the idle state, or to migrate the terminal from the inactive state to the idle state, sending an RRC release message to the terminal; or

[0038] When it is determined that the terminal state is to be transferred from the connected state to the inactive state, or when it is determined that the inactive state is to be maintained, an RRC suspend message is sent to the terminal.

[0039] Optionally, when the terminal state is the idle state, the method further includes at least one of the following:

[0040] receiving an RRC establishment message actively initiated by the terminal, and establishing an RRC connection with the terminal; or

[0041] receiving an RRC establishment message initiated by the terminal when the periodic RRC establishment timer times out, and establishing an RRC connection with the terminal; or

[0042] Receiving an RRC establishment message triggered by the terminal in response to a network-side paging, and establishing an RRC connection with the terminal;

[0043] When the terminal state is the inactive state, the method further includes at least one of the following:

[0044] receiving an RRC recovery message actively initiated by the terminal, and recovering the RRC connection with the terminal; or

[0045] receiving an RRC recovery message initiated by the terminal after the terminal moves out of the RNA, and recovering the RRC connection with the terminal; or

[0046] receiving an RRC recovery message initiated by the terminal when the periodic RNA update timer of the terminal times out, and recovering the RRC connection with the terminal; or

[0047] The RRC recovery message triggered by the terminal in response to the network side paging is received, and the RRC connection with the terminal is restored.

[0048] Optionally, in the case where the RRC connection is restored based on the RRC recovery message triggered by the terminal responding to the network side paging in the inactive state or the RRC establishment message triggered by the terminal responding to the network side paging in the idle state is restored, the method further includes:

[0049] receiving buffered data sent by an anchor access network device, where the buffered data is downlink data sent by a network side to the terminal in the inactive state or the idle state;

[0050] The buffered data is sent to the terminal.

[0051] Optionally, the receiving buffered data of the terminal includes:

[0052] Determining the anchor access network device;

[0053] In the case where an Xn interface exists with the anchor access network device, sending a data forwarding request message to the anchor access network device, wherein the data forwarding request message is used to request the buffered data of the terminal, and receiving the buffered data sent by the anchor access network device; or

[0054] When there is no Xn interface with the anchor access network device, a protocol data unit PDU session update context request is sent to the session management function SMF entity. The PDU session update context request carries the PDU session information of the target PDU session. The PDU session information is used by the SMF entity to determine the user plane function UPF entity and receive the buffered data sent by the UPF entity.

[0055] Optionally, when the terminal state is transferred from an idle state or an inactive state to a connected state, the method further includes:

[0056] Determine the anchor access network device;

[0057] When the RAN device is not the anchor access network device, sending a request message for obtaining a terminal context to the anchor access network device;

[0058] Receive the terminal context of the terminal sent by the anchor access network device.

[0059] Optionally, the determining of the anchor access network device includes:

[0060] The anchor access network device is determined according to the received wireless network temporary identifier of the terminal.

[0061] Optionally, when the RAN device is not the anchor access network device, the method further includes:

[0062] A network element registration request message is sent to the CN, where the network element registration request message is used to indicate information of a RAN device currently serving the terminal.

[0063] In a second aspect, an embodiment of the present application further provides a method for managing a terminal state, which is applied to a terminal, comprising:

[0064] Manage the terminal state of the terminal, the terminal state is related to a first connection state and a second connection state, the first connection state is the connection state between the terminal and the RAN device, and the second connection state is the connection state between the terminal and the core network CN.

[0065] Optionally, the terminal state includes a connected state, an idle state, and an inactive state; or the terminal state includes a connected state and an inactive state;

[0066] Wherein, in the connected state, the RAN device saves the terminal context of the terminal, a radio resource control RRC connection between the RAN device and the terminal has been established, a connection between the terminal and the CN has been established, and a connection between the RAN device and the CN has been established;

[0067] In the idle state, the RAN device saves the terminal context other than the access layer context of the terminal, the RRC connection between the RAN device and the terminal is disconnected, and the connection between the RAN device and the CN is maintained;

[0068] In the inactive state, the RAN device saves the terminal context of the terminal, the RRC connection between the RAN device and the terminal is suspended, and the connection between the RAN device and the CN is maintained.

[0069] Optionally, the managing the terminal state of the terminal includes:

[0070] The terminal state migration is performed according to the change of the connection between the terminal and the RAN device.

[0071] Optionally, performing terminal state migration according to a change in a connection between the terminal and the RAN device includes at least one of the following:

[0072] When the terminal state is the connected state, after the RRC connection between the RAN device and the terminal is released, the terminal is transferred from the connected state to the idle state; or

[0073] When the terminal state is the connected state, after the RRC connection between the RAN device and the terminal is suspended, the terminal state is migrated from the connected state to the inactive state; or

[0074] When the terminal state is the idle state, after the RRC connection between the RAN device and the terminal is established, the terminal state is migrated from the idle state to the connected state; or

[0075] When the terminal state is the inactive state, after the RRC connection between the RAN device and the terminal is restored, the terminal state is migrated from the inactive state to the connected state; or

[0076] When the terminal state is the inactive state, after the RRC connection between the RAN device and the terminal is released, the terminal state is migrated from the inactive state to the idle state.

[0077] Optionally, the method further comprises:

[0078] Depending on the terminal state and whether the terminal applies the MICO mode in which only the terminal initiates the connection, the downlink data reception situation is different.

[0079] Optionally, the downlink data reception situation is different according to the terminal state and whether the terminal applies the terminal-initiated connection-only MICO mode, including:

[0080] In the case that the terminal does not apply the terminal-initiated-only connection MICO mode, if the downlink data exists, receiving the downlink data;

[0081] When the terminal state is the connected state and the terminal applies the MICO mode, if the downlink data exists, the downlink data is received.

[0082] Optionally, the method further comprises:

[0083] When the terminal state is the idle state and the terminal does not apply the MICO mode, monitoring a paging message;

[0084] When the terminal state is the idle state or the inactive state and the terminal applies the MICO mode, the paging message is not monitored.

[0085] Optionally, the method further includes but is not limited to at least one of the following:

[0086] When the terminal enters the idle state, starting a periodic RRC establishment timer, the periodic RRC establishment timer is used to indicate a first timer value, and performing an RRC establishment process based on the first timer value; or

[0087] When the terminal state is the inactive state, after the terminal moves out of the radio access network notification area RNA, an RNA update process is executed; or

[0088] When the terminal enters the inactive state, a periodic notification area update timer is started, the periodic notification area update timer is used to indicate a second timer value, and an RNA update process is performed based on the second timer value.

[0089] Optionally, in the case of migrating the terminal state from the connected state to the idle state, or maintaining the idle state, or migrating the terminal state from the inactive state to the idle state, the method further includes: receiving an RRC release message sent by the RAN device, and releasing the RRC connection based on the RRC release message; or

[0090] In the case of migrating the terminal state from the connected state to the inactive state, or maintaining the inactive state, the method further includes: receiving an RRC suspend message sent by the RAN device, and suspending the RRC connection based on the RRC suspend message.

[0091] Optionally, when the terminal state is the idle state, the method further includes at least one of the following:

[0092] The terminal actively initiates an RRC establishment process to establish an RRC connection with the RAN device; or

[0093] The periodic RRC establishment timer received by the terminal times out, and the terminal initiates an RRC establishment procedure to establish an RRC connection with the RAN device; or

[0094] The terminal triggers an RRC establishment process in response to a network-side paging, and establishes an RRC connection with the RAN device;

[0095] When the terminal state is the inactive state, the method further includes at least one of the following:

[0096] The terminal actively initiates an RRC recovery procedure to restore the RRC connection with the RAN device; or

[0097] After the terminal moves out of the RNA, it initiates an RRC recovery process to restore the RRC connection with the RAN device; or

[0098] The periodic RNA update timer received by the terminal times out, and the terminal initiates an RRC recovery procedure to restore the RRC connection with the RAN device; or

[0099] The terminal triggers the RRC recovery process in response to the network side paging, and recovers the RRC connection with the RAN device.

[0100] Optionally, when the terminal state is the inactive state and the RRC connection is restored in response to network side paging, or when the terminal state is the idle state and the RRC connection is established in response to network side paging, the method further includes:

[0101] Receive buffered data sent by the RAN device, where the buffered data is downlink data sent by a network side to the terminal in the inactive state or the idle state.

[0102] In a third aspect, an embodiment of the present application further provides a method for managing terminal status, which is applied to a core network CN device, including:

[0103] Determine a registration management RM state of the terminal, and interact with the terminal through an access network RAN ​​device according to the RM state of the terminal, wherein the RM state is used to indicate whether the terminal is registered with the CN; or

[0104] After the terminal registers with the CN, the RAN device interacts with the terminal.

[0105] Optionally, the interacting with the terminal through an access network RAN ​​device according to the RM state of the terminal includes:

[0106] When the registration management RM state of the terminal is registered, the RAN device directly interacts with the terminal.

[0107] Optionally, when the CN device is a session management function SMF entity, the method further includes:

[0108] receiving a protocol data unit (PDU) session update context request sent by the RAN device, wherein the PDU session update context request carries PDU session information of a target PDU session;

[0109] Determine a user plane function UPF entity based on the PDU session information, the UPF entity being used to send buffered data to the RAN device, the buffered data being downlink data sent by the network side to the terminal in an inactive state or an idle state;

[0110] The tunnel information of the RAN device is sent to the UPF entity, where the tunnel information of the RAN device is used to establish a data transmission tunnel between the UPF entity and the RAN device, and the data transmission tunnel is used to transmit the buffered data.

[0111] Optionally, the method further comprises:

[0112] Determine the anchor RAN device;

[0113] The tunnel information of the anchor RAN device is sent to the UPF entity, where the tunnel information of the anchor RAN device is used to establish a data transmission tunnel between the UPF entity and the anchor RAN device, where the data transmission tunnel is used to transmit the buffered data.

[0114] In a fourth aspect, an embodiment of the present application further provides an access network RAN ​​device, including a memory, a transceiver, and a processor, wherein:

[0115] A memory for storing a computer program; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer program in the memory and implementing the terminal status management method as described in the first aspect above.

[0116] In a fifth aspect, an embodiment of the present application further provides a terminal, including a memory, a transceiver, and a processor, wherein:

[0117] A memory for storing a computer program; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer program in the memory and implementing the terminal status management method as described in the second aspect above.

[0118] In a sixth aspect, an embodiment of the present application further provides a core network CN device, including a memory, a transceiver, and a processor, wherein:

[0119] A memory for storing a computer program; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer program in the memory and implementing the terminal status management method as described in the third aspect above.

[0120] In a seventh aspect, an embodiment of the present application further provides a terminal status management device, which is applied to an access network RAN ​​device, including:

[0121] The first management unit is used to manage the terminal state of the terminal, where the terminal state is related to a first connection state and a second connection state, where the first connection state is the connection state between the RAN device and the terminal, and the second connection state is the connection state between the terminal and the core network CN.

[0122] In an eighth aspect, an embodiment of the present application further provides a terminal status management device, applied to a terminal, comprising:

[0123] The second management unit is used to manage the terminal state of the terminal, where the terminal state is related to a first connection state and a second connection state, where the first connection state is the connection state between the terminal and the RAN device, and the second connection state is the connection state between the terminal and the core network CN.

[0124] In a ninth aspect, an embodiment of the present application further provides a terminal status management device, which is applied to a core network CN device, including:

[0125] an interaction unit, configured to determine a registration management RM state of a terminal, and interact with the terminal through an access network RAN ​​device according to the RM state of the terminal, wherein the RM state is used to indicate whether the terminal is registered with the CN; or

[0126] Used to interact with the terminal through the RAN device after the terminal registers with the CN.

[0127] In the tenth aspect, an embodiment of the present application further provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the terminal status management method described in the first aspect as described above.

[0128] In the eleventh aspect, an embodiment of the present application further provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the terminal status management method described in the second aspect as described above.

[0129] In a twelfth aspect, an embodiment of the present application further provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the terminal status management method described in the third aspect above.

[0130] The terminal status management method and device provided in the embodiment of the present application can be applied to the RAN service-oriented scenario. After the RAN is service-oriented, the RAN and CN are deeply integrated, and the RAN can be connected to multiple NFs in the CN. Therefore, the connection status between the UE and the network side can be considered as the connection status between the UE and the RAN. In the embodiment of the present application, the access network device manages the terminal status, and the core network no longer manages the connection status of the UE. It is considered that the UE is always connected. When the core network interacts with the RAN, there is no need to obtain the UE status from the AMF, and there is no need to synchronize the UE status between the core network NFs, which simplifies the interaction process and reduces signaling interaction. On the other hand, the terminal status is related to the first connection status and the second connection status. The first connection status is the connection status between the RAN device and the terminal, and the second connection status is the connection status between the terminal and the core network CN, which simplifies the terminal status. BRIEF DESCRIPTION OF THE DRAWINGS

[0131] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, a brief introduction will be given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0132] Figure 1 It is a schematic diagram of the existing N2 interface provided by this application;

[0133] Figure 2 This is one of the RAN service-oriented architecture diagrams provided in this application;

[0134] Figure 3 This is the second schematic diagram of the RAN service-oriented architecture provided by this application;

[0135] Figure 4 This is one of the flow charts of the terminal status management method provided in the embodiment of the present application;

[0136] Figure 5 This is one of the terminal state migration diagrams in the RAN provided in an embodiment of the present application;

[0137] Figure 6 This is the second schematic diagram of terminal state migration in RAN provided in an embodiment of the present application;

[0138] Figure 7 This is the second flow chart of the terminal status management method provided in the embodiment of the present application;

[0139] Figure 8 This is one of the terminal state migration diagrams in the UE provided in the embodiment of the present application;

[0140] Fig. 9 This is the second schematic diagram of terminal state migration in the UE provided in an embodiment of the present application;

[0141] Fig.10 This is the third flow chart of the terminal status management method provided in the embodiment of the present application;

[0142] Fig.11 This is one of the state transition flow diagrams provided in the embodiments of the present application;

[0143] Fig.12 This is the second state transition flow diagram provided in the embodiment of the present application;

[0144] Fig.13 This is the third state transition flow diagram provided in the embodiment of the present application;

[0145] Fig.14 This is the fourth state transition flow diagram provided in the embodiment of the present application;

[0146] Fig.15 This is the fifth state transition flow diagram provided in the embodiment of the present application;

[0147] Fig.16 This is the sixth state transition flow diagram provided in the embodiment of the present application;

[0148] Fig.17 This is the seventh state transition flow diagram provided in the embodiment of the present application;

[0149] Fig.18 This is one of the schematic diagrams of the RNA update process provided in the embodiments of the present application;

[0150] Fig.19 This is the second schematic diagram of the RNA update process provided in the embodiment of the present application;

[0151] Fig. 20 This is the third schematic diagram of the RNA update process provided in the embodiment of the present application;

[0152] Fig.21 This is the eighth state transition flow diagram provided in the embodiment of the present application;

[0153] Fig. 22 is a flow chart of a path switching method provided in an embodiment of the present application;

[0154] Fig.23 It is a flowchart of the RAN information synchronization method provided in an embodiment of the present application;

[0155] Fig.24 It is one of the structural diagrams of the terminal status management device provided in the embodiment of the present application;

[0156] Fig.25 This is the second structural diagram of the terminal status management device provided in the embodiment of the present application;

[0157] Fig.26 This is the third structural diagram of the terminal status management device provided in the embodiment of the present application;

[0158] Fig. 27 It is a structural diagram of an access network RAN ​​device provided in an embodiment of the present application;

[0159] Fig.28 A schematic diagram of the structure of a terminal provided in an embodiment of the present application;

[0160] Fig.29 It is a structural diagram of the core network CN device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0161] In the embodiments of the present application, the term "and / or" describes the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0162] In the embodiments of the present application, the term "plurality" refers to two or more than two, and other quantifiers are similar.

[0163] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0164] The technical solution provided in the embodiment of the present application can be applicable to a variety of systems, especially 5G (5th Generation Mobile Communication Technology, fifth generation mobile communication technology) system. For example, the applicable system can be a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) general packet radio service (GPRS) system, a long term evolution (LTE) system, a LTE frequency division duplex (FDD) system, a LTE time division duplex (TDD) system, an advanced long term evolution (LTE-A) system, a universal mobile telecommunication system (UMTS), a world-wide interoperability for microwave access (WiMAX) system, a 5G new radio (NR) system, etc. These various systems include terminal equipment and network equipment. The system may also include core network parts, such as the Evolved Packet System (EPS), 5G System (5GS), etc.

[0165] The terminal device involved in the embodiment of the present application may be a device that provides voice and / or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem. In different systems, the name of the terminal device may also be different. For example, in a 5G system, the terminal device may be called a user equipment (UE). A wireless terminal device can communicate with one or more core networks (CN) via a radio access network (RAN). The wireless terminal device may be a mobile terminal device, such as a mobile phone (or a "cellular" phone) and a computer with a mobile terminal device. For example, it may be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges language and / or data with a wireless access network. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs) and other devices. The wireless terminal device may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal device, an access terminal device, a user terminal device, a user agent, and a user device, but is not limited in the embodiments of the present application.

[0166] The network device involved in the embodiment of the present application may be a base station, which may include multiple cells providing services for the terminal. Depending on the specific application scenario, the base station may also be called an access point, or may be a device in the access network that communicates with the wireless terminal device through one or more sectors on the air interface, or other names. The network device may be used to interchange received air frames with Internet Protocol (IP) packets, and serve as a router between the wireless terminal device and the rest of the access network, wherein the rest of the access network may include an Internet Protocol (IP) communication network. The network device may also coordinate the attribute management of the air interface. For example, the network device involved in the embodiments of the present application may be a network device (Base Transceiver Station, BTS) in the Global System for Mobile communications (Global System for Mobile communications, GSM) or Code Division Multiple Access (Code Division Multiple Access, CDMA), or a network device (NodeB) in Wide-band Code Division Multiple Access (WCDMA), or an evolutionary network device (evolutional Node B, eNB or e-NodeB) in the long term evolution (long term evolution, LTE) system, a 5G base station (gNB) in the 5G network architecture (next generation system), or a home evolved Node B (Home evolved Node B, HeNB), a relay node, a home base station (femto), a pico base station (pico), etc., which is not limited in the embodiments of the present application. In some network structures, the network device may include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit may also be arranged geographically separately.

[0167] Network devices and terminal devices can each use one or more antennas for multiple-input multiple-output (MIMO) transmission. MIMO transmission can be single-user MIMO (SU-MIMO) or multi-user MIMO (MU-MIMO). Depending on the form and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO or massive-MIMO, or it can be diversity transmission, precoded transmission or beamforming transmission, etc.

[0168] To facilitate understanding of the embodiments of the present application, the following describes terms or backgrounds related to the embodiments of the present application:

[0169] Figure 1 This is a schematic diagram of the existing N2 interface provided by this application, such as Figure 1 As shown, the centralized unit (CU)-control plane part (Control Plane) in the base station is connected to the access and mobility management function (Access and Mobility Management Function, AMF) through the N2 interface.

[0170] Figure 2 This is one of the RAN service architecture diagrams provided by this application. Figure 3 This is the second schematic diagram of the RAN service architecture provided by this application, such as Figure 2 and Figure 3 As shown, in the RAN service-oriented scenario, the RAN can be connected to multiple network function entities (NF) in the core network (CN).

[0171] No solution has been proposed for the state management method of UE after RAN service-oriented.

[0172] The implementation embodiment of the present application provides a terminal status management method, which can be applied to the scenario after RAN service.

[0173] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0174] Figure 4This is one of the flow charts of the terminal status management method provided in the embodiment of the present application, such as Figure 4 As shown, an embodiment of the present application provides a method for managing terminal status, which is applied to an access network RAN ​​device, including:

[0175] Step 410, managing the terminal state of the terminal, the terminal state is related to a first connection state and a second connection state, the first connection state is the connection state between the RAN device and the terminal, and the second connection state is the connection state between the terminal and the core network CN.

[0176] Specifically, the terminal status is managed by the access network RAN ​​device (hereinafter referred to as RAN). RAN can be a base station, such as a 5G base station (generation NodeB, gNB), etc.

[0177] The terminal status refers to the connection status between the terminal and the network side. The terminal status can be related to the following connection statuses:

[0178] The connection status between the RAN device and the terminal; and

[0179] The connection status between the terminal and the core network CN.

[0180] The connection state between the RAN device and the terminal may include:

[0181] The RAN device has established a connection with the terminal;

[0182] The RAN device suspends the connection with the terminal;

[0183] The RAN device is disconnected from the terminal.

[0184] The connection status between the terminal and the core network CN may include:

[0185] The terminal has established a connection with the core network;

[0186] The terminal is disconnected from the core network.

[0187] In different terminal states, the connection status between the terminal and the network side is different.

[0188] Exemplarily, the RAN device has established a connection with the terminal, and the terminal has established a connection with the core network, which is a first state;

[0189] The RAN device suspends the connection with the terminal, and the terminal has established a connection with the core network, which is the second state;

[0190] The RAN device is disconnected from the terminal, and the terminal has established a connection with the core network, which is the third state.

[0191] It should be understood that the above are examples for the convenience of understanding the embodiments of the present application. The embodiments of the present application do not limit the specific correspondence between the terminal state and the first connection state and the second connection state, and the embodiments of the present application do not limit the naming of different terminal states.

[0192] The terminal status management method provided in the embodiment of the present application can be applied to the RAN service-oriented scenario. After the RAN is service-oriented, the RAN and CN are deeply integrated, and the RAN can be connected to multiple NFs in the CN. Therefore, the connection status between the UE and the network side can be considered as the connection status between the UE and the RAN. In the embodiment of the present application, the terminal status is managed by the access network device, and the core network can no longer manage the connection status of the UE. The core network can consider that the UE is always connected. The UE status in the relevant method is managed by the AMF. After the RAN is service-oriented, if the existing UE status management method continues to be used, the UE status is still managed by the AMF. Then, the CN NF needs to obtain the UE status from the AMF every time it interacts with the RAN, which increases the signaling interaction and brings about the problem of UE status synchronization between the CN NFs. In the embodiment of the present application, when the core network interacts with the RAN, there is no need to obtain the UE status from the AMF, nor is there any need to synchronize the UE status between the core network NFs, which simplifies the interaction process and reduces the signaling interaction. On the other hand, the terminal status is related to the first connection status and the second connection status. The first connection status is the connection status between the RAN device and the terminal, and the second connection status is the connection status between the terminal and the core network CN, which simplifies the terminal status.

[0193] Optionally, the terminal state includes a connected state, an idle state, and an inactive state;

[0194] Or the terminal state includes a connected state and an inactive state;

[0195] The connected state may also be referred to as UE-CONNECTED. The embodiment of the present application does not limit the naming of this state. When the terminal state is the connected state:

[0196] The RAN device stores all the terminal contexts of the terminal. It should be understood that the terminal context in the embodiment of the present application includes the AS layer context, the NF information of the serving UE, etc., which will not be described in detail below;

[0197] A radio resource control (RRC) connection between the RAN device and the terminal has been established. For the characteristics of the RRC connection between the RAN device and the terminal being established, reference may be made to the relevant introduction of the RRC connection state (RRC-CONNECTED) and to the relevant technology, which will not be described in detail here;

[0198] The connection between the terminal and the CN has been established, which means that the terminal has established a connection with any NF in the CN. Optionally, the connection between the terminal and the CN has been established, which is a Non-Access Stratum (NAS) connection established between the terminal and any NF in the CN. It should be understood that the establishment of a NAS connection between the terminal and any NF in the CN can refer to the relevant technology. For example, after RAN serviceization, any NF in the CN can establish a NAS connection with the terminal. The role of NF is the same as that of AMF in the relevant technology, such as serving as a termination point for non-access stratum security;

[0199] The connection between the RAN device and the CN has been established, which means that the access network device has established a connection with any CN NF. Optionally, the access network device establishes an N2 connection with any CN NF, such as after the RAN is serviced, the N2 interface is extended to be the interface between the RAN (such as gNB) and the CN NF, such as the HyperText Transfer Protocol (HTTP) can be applied between any NF of the access network and the core network. The function of the extended N2 interface can refer to the relevant technology.

[0200] The idle state may also be referred to as UE-IDLE. The embodiment of the present application does not limit the naming of this state. When the terminal state is the idle state:

[0201] The RAN device stores the terminal context other than the access stratum (AS) context of the terminal, that is, the RAN stores the terminal context without the AS layer context;

[0202] The RRC connection between the RAN device and the terminal is disconnected. The characteristics of the RRC connection disconnection between the RAN device and the terminal can refer to the relevant introduction of the RRC idle state (RRC-IDLE) and the relevant technology, which will not be repeated here;

[0203] The connection between the RAN device and the CN is maintained, which means that the access network device has established a connection with any CN NF and maintains the connection state. Optionally, the access network device establishes an N2 connection with any CN NF, which is not described here again with reference to the above description.

[0204] Optionally, when the terminal state is the idle state, the method further includes:

[0205] If the N3 connection between the RAN device and the user plane function (UPF) entity is not connected, it remains disconnected.

[0206] Optionally, if an N3 connection has been established between the RAN device and the UPF entity, whether the N3 connection is disconnected is not limited in this embodiment of the application.

[0207] The inactive state may also be referred to as UE-INACTIVE. The embodiment of the present application does not limit the naming of this state. When the terminal state is the inactive state:

[0208] The RAN device stores the terminal context of the terminal. It should be understood that the terminal context stored by the RAN device includes an AS layer context;

[0209] The RRC connection between the RAN device and the terminal is suspended. The characteristics of the RRC connection suspension between the RAN device and the terminal can refer to the relevant introduction of the RRC inactive state (RRC-INACTIVE) and the relevant technology, which will not be repeated here;

[0210] The connection between the RAN device and the CN is maintained, which means that the access network device has established a connection with any CN NF and maintains the connection state. Optionally, the access network device establishes an N2 connection with any CN NF, which is not described here again with reference to the above description.

[0211] The terminal status management method provided in the embodiment of the present application defines different terminal states through a connected state, an idle state, and an inactive state, thereby simplifying the terminal state.

[0212] Optionally, the terminal status of the management terminal includes:

[0213] The terminal state migration is performed according to the change of the connection between the terminal and the RAN device.

[0214] Specifically, according to a change in the connection between the terminal and the RAN device, the terminal state is migrated from an original state to a new state according to the connection status between the terminal and the RAN device.

[0215] Optionally, performing terminal state migration according to a change in a connection between the terminal and the RAN device includes:

[0216] Terminal state migration is performed according to a change in the RRC connection between the terminal and the RAN device.

[0217] Optionally, performing terminal state migration according to a change in a connection between the terminal and the RAN device includes at least one of the following:

[0218] When the terminal state is the connected state, after the RRC connection between the RAN device and the terminal is released, the terminal state is migrated from the connected state to the idle state; or

[0219] When the terminal state is the connected state, after the RRC connection between the RAN device and the terminal is suspended, the terminal state is migrated from the connected state to the inactive state; or

[0220] When the terminal state is the idle state, after the RRC connection between the RAN device and the terminal is established, the terminal state is migrated from the idle state to the connected state; or

[0221] When the terminal state is the inactive state, after the RRC connection between the RAN device and the terminal is restored, the terminal state is migrated from the inactive state to the connected state; or

[0222] When the terminal state is the inactive state, after the RRC connection between the RAN device and the terminal is released, the terminal state is migrated from the inactive state to the idle state.

[0223] In one possible implementation, Figure 5 This is one of the terminal state migration diagrams in the RAN provided in the embodiment of the present application, such as Figure 5 As shown, when the terminal state includes a connected state, an idle state, and an inactive state, performing terminal state migration according to a change in the connection between the terminal and the RAN device includes:

[0224] When the terminal state is the connected state, after the RRC connection between the RAN device and the terminal is released, the terminal state is migrated from the connected state to the idle state;

[0225] When the terminal state is the connected state, after the RRC connection between the RAN device and the terminal is suspended, the terminal state is migrated from the connected state to the inactive state;

[0226] When the terminal state is the idle state, after the RRC connection between the RAN device and the terminal is established, the terminal state is migrated from the idle state to the connected state;

[0227] When the terminal state is the inactive state, after the RRC connection between the RAN device and the terminal is restored, the terminal state is migrated from the inactive state to the connected state;

[0228] When the terminal state is the inactive state, after the RRC connection between the RAN device and the terminal is released, the terminal state is migrated from the inactive state to the idle state.

[0229] In one possible implementation, Figure 6 This is the second schematic diagram of terminal state migration in RAN provided in an embodiment of the present application, such as Figure 6 As shown, when the terminal state includes a connected state and an inactive state, performing terminal state migration according to a change in the connection between the terminal and the RAN device includes:

[0230] When the terminal state is the connected state, after the RRC connection between the RAN device and the terminal is suspended, the terminal state is migrated from the connected state to the inactive state;

[0231] When the terminal state is the inactive state, after the RRC connection between the RAN device and the terminal is restored, the terminal state is migrated from the inactive state to the connected state.

[0232] The terminal status management method provided in the embodiment of the present application is that the RAN performs terminal status migration through the change of the connection between the terminal and the RAN device, and updates the terminal status when the connection between the terminal and the RAN device changes, thereby managing the terminal status.

[0233] Optionally, the method further comprises:

[0234] Manage whether the terminal is reachable in different terminal states.

[0235] Specifically, the RAN manages the terminal reachability, that is, detects whether the UE is reachable in different terminal states, which can be understood as whether the UE is accessible in different terminal states.

[0236] In the terminal status management method provided in the embodiment of the present application, the RAN manages the reachability of the terminal, and there is no need to distinguish the management entities of the terminal reachability according to different states, thereby streamlining the terminal reachability management process.

[0237] Optionally, the managing whether the terminal is reachable in different terminal states includes but is not limited to at least one of the following:

[0238] When the terminal state is connected, the terminal is reachable; or

[0239] When the terminal is in an idle state or an inactive state, determining whether the terminal is reachable according to whether the terminal applies a Mobile Initiated Connection Only (MICO) mode; or

[0240] When the terminal is in an idle state, starting a mobile reachable timer, and determining whether the terminal is reachable according to whether the mobile reachable timer times out; or

[0241] When the terminal is in an inactive state, a protection timer is started, and whether the terminal is reachable is determined according to whether the protection timer times out. When the terminal is in an idle state or an inactive state, whether the terminal is in an MICO mode where only the terminal initiates a connection is determined according to whether the terminal applies the MICO mode, including:

[0242] When the terminal uses the MICO mode, only uplink data (Mobile Original, MO) can be sent by the terminal, and downlink data (Mobile Terminated, MT) cannot be sent to the UE. The RAN considers the UE unreachable. At this time, the terminal can only send MO data, but no MT data.

[0243] If the terminal does not apply the MICO mode and can send downlink data to the UE (Mobile Terminated, MT), the RAN considers the UE to be reachable. At this time, the terminal can send MO data and receive MT data.

[0244] It should be understood that the embodiments of the present application do not limit how the RAN obtains information on whether the UE applies the MICO mode.

[0245] Optionally, when the terminal is in an idle state and the terminal does not apply the MICO mode, a paging process is initiated for the UE according to a paging trigger condition.

[0246] Specifically, when the terminal is in an idle state and the terminal does not apply the MICO mode, the RAN can page the UE. The paging trigger condition refers to the condition for triggering the paging, which can be triggered by the core network side or spontaneously by the RAN. The embodiment of the present application does not limit the paging trigger condition.

[0247] Optionally, when the terminal state is in an inactive state and the terminal does not apply the MICO mode, a paging process is initiated for the UE according to the paging trigger condition.

[0248] Specifically, when the terminal is in an inactive state and the terminal does not apply the MICO mode, the RAN can page the UE. The paging trigger condition refers to the condition for triggering the paging, which can be triggered by the core network side or spontaneously by the RAN. The embodiment of the present application does not limit the paging trigger condition.

[0249] When the terminal is in an idle state, starting a mobile reachable timer, and determining whether the terminal is reachable according to whether the mobile reachable timer times out, includes:

[0250] When the mobile reachable timer times out, the RAN considers that the terminal is unreachable.

[0251] Optionally, if the mobile reachable timer does not time out, the RAN considers that the terminal is reachable.

[0252] Optionally, when the terminal is in an idle state, a periodic RRC establishment timer is configured for the terminal, the periodic RRC establishment timer is used to indicate a first timer value, and the first timer value is used to instruct the terminal to execute the RRC establishment process.

[0253] Specifically, the RAN configures a periodic RRC establishment timer for the UE. The periodic RRC establishment timer is used to start the periodic RRC establishment timer when the UE enters an idle state. After the periodic RRC establishment timer times out, the UE executes the RRC establishment process.

[0254] The first timer value of the periodic RRC establishment timer may be allocated by the RAN to the UE based on local policies, information provided by the UE, etc. The embodiment of the present application does not limit the value of the first timer value and how to set it.

[0255] Optionally, the mobile reachable timer is used to indicate a third timer value, which is longer than the first timer value. When the mobile reachable timer exceeds the third timer value, a deregistration process is triggered to deregister the terminal device from the CN.

[0256] Specifically, the third timer value is longer than the first timer value. When the first timer times out, the periodic RRC establishment timer times out, the UE still has not established an RRC connection with the RAN, and when the mobile reachable timer exceeds the third timer value, the RAN considers that the UE is unreachable and triggers a deregistration process to deregister the terminal device from the CN. Exemplarily, the RAN may request the AMF to initiate an implicit deregistration process. After receiving the request, the AMF starts the implicit deregistration timer. The AMF starts the implicit deregistration timer, which can refer to the relevant technology and will not be described here.

[0257] Optionally, if the RRC connection has been established, the periodic RRC establishment timer counts, and if the RRC connection has not been established, the periodic RRC establishment timer continues to count;

[0258] If the RRC connection has been established, the mobile reachable timer will stop timing. If the RRC connection has not been established, the mobile reachable timer will continue timing.

[0259] When the terminal is in an inactive state, starting a protection timer, and determining whether the terminal is reachable according to whether the protection timer times out, includes:

[0260] When the protection timer times out, the RAN considers that the terminal is unreachable.

[0261] Optionally, the protection timer does not time out, and the RAN considers that the terminal is reachable.

[0262] Optionally, when the terminal is in an inactive state, a periodic notification area update timer is configured for the terminal, and the periodic notification area update timer is used to indicate a second timer value, and the second timer value is used to instruct the terminal to execute a wireless access network notification area RNA update process.

[0263] Specifically, the periodic notification area update timer is configured by the RAN for the UE and is started on the UE side. When the UE enters the inactive state UE-INACTIVE, the UE starts the periodic notification area update timer. When the periodic notification area update timer exceeds the second timer value, the UE executes the RAN notification area update process. The embodiment of the present application does not limit the value of the second timer value and how to set it.

[0264] Optionally, the protection timer is used to indicate a fourth timer value, where the fourth timer value is longer than the second timer value, and when the protection timer exceeds the fourth timer value, the RRC connection with the terminal is released.

[0265] Specifically, the fourth timer value is longer than the second timer value. When the second timer times out, the periodic notification area update timer times out, the UE has not yet executed the RNA update process, and the protection timer exceeds the fourth timer value, the RAN releases the RRC connection between the terminal.

[0266] Optionally, if the RNA update process has been executed, the periodic notification area update timer stops timing, and if the RNA update process has not been executed, the periodic notification area update timer continues timing;

[0267] If the RNA update process has been executed, the protection timer stops timing. If the RNA update process has not been executed, the protection timer continues timing.

[0268] Optionally, when the terminal state is the connected state, the location information of the terminal known by the RAN device is of a first granularity;

[0269] When the terminal state is the idle state, the location information of the terminal known by the RAN device is of a second granularity;

[0270] When the terminal state is the inactive state, the location information of the terminal known by the RAN device is of the third granularity.

[0271] In a possible implementation manner, when the terminal state is the connected state, the location information of the terminal known by the RAN device is at a cell level, and the first granularity is the cell;

[0272] When the terminal state is the idle state, the location information of the terminal known by the RAN device is a tracking area list (TAlist), and the second granularity is TAlist;

[0273] When the terminal state is the inactive state, the location information of the terminal known by the RAN device is at a RAN notification area (RAN Notification area, RNA) granularity, that is, the third granularity is RNA.

[0274] The terminal status management method provided in the embodiment of the present application can have different granularities of the location information of the terminal known to the RAN in different terminal states, so that the network can know the location of the UE in different UE states to provide services to the UE.

[0275] Optionally, the terminal status of the management terminal includes:

[0276] In a case where it is determined to migrate the terminal state from the connected state to the idle state, or to maintain the idle state, or to migrate the terminal from the inactive state to the idle state, an RRC release message is sent to the terminal.

[0277] Specifically, if the network side wants the UE to enter or maintain the idle state UE-IDLE state, the RAN can send an RRC Release message to the UE.

[0278] Optionally, when it is determined to migrate the terminal state from the connected state to the idle state, or to maintain the idle state, or to migrate the terminal from the inactive state to the idle state, and when it is determined to release the N3 interface, a PDU session update SM context request Nsmf_PDUSession_UpdateSMContextRequest is sent to the SMF, indicating that the UE cannot access the downlink data, the SMF UPF releases the user plane resources on the N3 side, and at the same time instructs the UPF to buffer DL data packets.

[0279] Optionally, the terminal status of the management terminal includes:

[0280] When it is determined that the terminal state is to be transferred from the connected state to the inactive state, or when it is determined that the inactive state is to be maintained, an RRC suspend message is sent to the terminal.

[0281] Specifically, if the network side wants the UE to enter or maintain the inactive state UE-INACTIVE, it will send an RRC suspend message. The RRC suspend message may carry Suspend related information in the RRC Release message, that is, RRC Release with Suspend message. The suspension information may include relevant configurations such as RNA.

[0282] Optionally, when the terminal state is the idle state, the method further includes at least one of the following:

[0283] receiving an RRC establishment message actively initiated by the terminal, and establishing an RRC connection with the terminal; or

[0284] receiving an RRC establishment message initiated by the terminal when the periodic RRC establishment timer times out, and establishing an RRC connection with the terminal; or

[0285] Receive an RRC establishment message triggered by the terminal in response to the network side paging, and establish an RRC connection with the terminal.

[0286] For receiving an RRC establishment message actively initiated by the terminal, an RRC connection is established with the terminal. After the RRC connection between the RAN device and the terminal is established, the terminal state is migrated from the idle state to the connected state.

[0287] When the periodic RRC establishment timer of the terminal times out, the RRC establishment message initiated by the terminal is received, and an RRC connection is established with the terminal. After the RRC connection between the RAN device and the terminal is established, the terminal state is migrated from the idle state to the connected state.

[0288] For receiving the RRC establishment message triggered by the terminal in response to the network side paging, an RRC connection is established with the terminal. After the RRC connection between the RAN device and the terminal is established, the terminal state is migrated from the idle state to the connected state.

[0289] Optionally, the method further comprises:

[0290] In a case where the RAN refuses to establish an RRC connection for the terminal, a first RRC reject RRCReject message is sent to the terminal.

[0291] Optionally, the first RRC rejection message carries a first waiting time, and the first waiting time is used to instruct the UE to initiate an RRC establishment request after the first waiting time.

[0292] Optionally, when the UE receives the first RRC rejection message sent by the RAN device, the terminal state remains in the idle state.

[0293] Optionally, when the terminal state is the inactive state, the method further includes at least one of the following:

[0294] receiving an RRC recovery message actively initiated by the terminal, and recovering the RRC connection with the terminal; or

[0295] receiving an RRC recovery message initiated by the terminal after the terminal moves out of the RNA, and recovering the RRC connection with the terminal; or

[0296] receiving an RRC recovery message initiated by the terminal when the periodic RNA update timer of the terminal times out, and recovering the RRC connection with the terminal; or

[0297] The RRC recovery message triggered by the terminal in response to the network side paging is received, and the RRC connection with the terminal is restored.

[0298] Receiving an RRC recovery message actively initiated by the terminal, restoring the RRC connection with the terminal, and after the RRC connection between the RAN device and the terminal is restored, migrating the terminal state from the inactive state to the connected state;

[0299] Receiving an RRC recovery message initiated by the terminal after moving out of the RNA, restoring the RRC connection with the terminal, and after the RRC connection between the RAN device and the terminal is restored, migrating the terminal state from the inactive state to the connected state;

[0300] When receiving an RRC recovery message initiated by the terminal when the periodic RNA update timer times out, the RRC connection between the RAN device and the terminal is restored, and after the RRC connection between the RAN device and the terminal is restored, the terminal state is migrated from the inactive state to the connected state;

[0301] Upon receiving an RRC recovery message triggered by the terminal in response to a network-side paging, the RRC connection with the terminal is restored, and the RRC connection between the RAN device and the terminal is restored.

[0302] Optionally, the method further comprises:

[0303] In a case where the RAN refuses to restore the RRC connection for the terminal, a second RRC reject RRCReject message is sent to the terminal.

[0304] Optionally, the second RRC rejection message carries a second waiting time, and the second waiting time is used to instruct the UE to initiate an RRC recovery request after the second waiting time.

[0305] Optionally, when the UE receives the second RRC reject message sent by the RAN device, the terminal state remains in the inactive state.

[0306] Optionally, in the case where the RRC connection is restored based on the RRC recovery message triggered by the terminal responding to the network side paging in the inactive state or the RRC establishment message triggered by the terminal responding to the network side paging in the idle state is restored, the method further includes:

[0307] receiving buffered data sent by an anchor access network device, where the buffered data is downlink data sent by a network side to the terminal in the inactive state or the idle state;

[0308] The buffered data is sent to the terminal.

[0309] Specifically, the anchor access network device may be an anchor gNB, and the downlink data (buffered data) of the terminal may be cached in the anchor access network device. The access network device currently serving the terminal may receive the buffered data directly or indirectly forwarded by the anchor access network device.

[0310] In the embodiment of the present application, lossless transmission of the downlink data (buffered data) of the terminal is achieved by receiving the buffered data sent by the anchor access network device.

[0311] Optionally, the receiving buffered data of the terminal includes:

[0312] Determining the anchor access network device;

[0313] In the case where an Xn interface exists with the anchor access network device, sending a data forwarding request message to the anchor access network device, wherein the data forwarding request message is used to request the buffered data of the terminal, and receiving the buffered data sent by the anchor access network device; or

[0314] When there is no Xn interface with the anchor access network device, a protocol data unit PDU session update context request is sent to the session management function SMF entity. The PDU session update context request carries the PDU session information of the target PDU session. The PDU session information is used by the SMF entity to determine the user plane function UPF entity and receive the buffered data sent by the UPF entity.

[0315] Specifically, the access network RAN ​​device may be the RAN device currently serving the terminal, which may be referred to as the current RAN device or the current gNB hereinafter.

[0316] In the case that an Xn interface exists between the current RAN device and the anchor access network device, the current RAN device may receive the buffered data directly forwarded by the anchor access network device.

[0317] When there is no Xn interface between the current RAN device and the anchor access network device, a protocol data unit PDU session update context request is sent to the session management function SMF entity. The PDU session update context request carries the PDU session information of the target PDU session. The SMF entity establishes a data transmission tunnel between the anchor access network device, UPF and the current RAN device based on the PDU session information. The current RAN device can receive the buffered data forwarded by the anchor access network device through the data transmission tunnel.

[0318] Optionally, when the terminal state is transferred from an idle state or an inactive state to a connected state, the method further includes:

[0319] Determine the anchor access network device;

[0320] When the RAN device is not the anchor access network device, sending a request message for obtaining a terminal context to the anchor access network device;

[0321] Receive the terminal context of the terminal sent by the anchor access network device.

[0322] Optionally, the determining of the anchor access network device includes:

[0323] The anchor access network device is determined according to the received Radio Network Temporary Identity (RNTI) of the terminal.

[0324] Specifically, the radio network temporary identifier may be between the UE and the access network device, and may be used as an identifier of different UEs. The RNTI in the embodiment of the present application may be applied to an idle state and / or an inactive state.

[0325] For idle state:

[0326] The anchor access network device can carry an RNTI identifier in the RRCRelease message. In this case, the RNTI (also called the idle state RNTI identifier) ​​is the idle state UE identifier, which is used by the network side (access network or core network) to find the access network device (such as gNB) to which the UE is connected before entering the idle state UE-IDLE, that is, to find the anchor access network device (anchor gNB). Optionally, the idle state RNTI identifier can be used by the network side to find the UE context in the idle state UE-IDLE state. The idle state RNTI identifier is used to identify the UE context in the idle state UE-IDLE state. The idle state UE context refers to the UE context stored by the anchor access network device before the UE enters the UE-IDLE state.

[0327] For the inactive state:

[0328] The anchor access network device can carry the RNTI identifier in the RRC Release with Suspend Indication message. In this case, the RNTI (also called the inactive RNTI identifier) ​​is the inactive UE identifier, which is used by the network side (access network or core network) to find the access network device (such as gNB) to which the UE was connected before entering the inactive state UE-INACTIVE, that is, to find the anchor access network device (anchor gNB). Optionally, the inactive RNTI identifier can be used by the network side to find the UE context in the inactive UE-INACTIVE state. The inactive RNTI identifier is used to identify the UE context in the inactive UE-INACTIVE state. The UE context in the inactive UE-INACTIVE state refers to the UE context stored by the anchor access network device before the UE enters the UE-INACTIVE state.

[0329] Optionally, both the UE side and the RAN side will store the RNTI identifier. The RRCSetup message initiated by the UE in the idle state and the RRCResume message initiated in the inactive state will carry the RNTI identifier. Currently, the anchor point gNB is determined based on the RNTI.

[0330] Optionally, the paging message sent by the RAN also carries the RNTI identifier of the UE (the RNTI identifier in the idle state or the RNTI identifier in the inactive state), and the UE learns that the paging object is the UE itself through the RNTI.

[0331] Optionally, when the RAN device is not the anchor access network device, the method further includes:

[0332] A network element registration request message is sent to the CN, where the network element registration request message is used to indicate information of a RAN device currently serving the terminal.

[0333] Specifically, the RAN device may be one of the RAN devices currently serving the terminal. Therefore, the RAN currently serving the UE should be synchronized with the core network.

[0334] Optionally, a network element registration request message is sent to the CN, and registration can be performed with the network element in the core network. The network element in the core network can be registered with a unified data management function (UDM), a unified data repository function (UDR), or a network repository function (NRF). When the core network NF initiates downlink signaling, it goes to the corresponding network element such as UDM, UDR or NRF to query the gNB currently serving the UE.

[0335] The terminal state changes from an idle state or an inactive state to a connected state. If the RAN currently serving the UE changes, that is, it is different from the serving gNB when the UE enters the idle state or the inactive state, and the core network side does not yet have the latest RAN information, the terminal state management method provided in the embodiment of the present application is provided by the RAN device to send a network element registration request message to the CN, and through the network element registration request message, the information of the RAN device currently serving the terminal is indicated, so that the CN can obtain the information of the RAN device currently serving the terminal, and synchronize the information of the RAN device currently serving the terminal.

[0336] Figure 7 This is a second flow chart of the terminal status management method provided in the embodiment of the present application, such as Figure 7 As shown, an embodiment of the present application provides a terminal status management method, which is applied to a terminal, including:

[0337] Step 710: Manage the terminal state of the terminal, where the terminal state is related to a first connection state and a second connection state, where the first connection state is the connection state between the terminal and a RAN device, and the second connection state is the connection state between the terminal and a core network CN.

[0338] Specifically, the terminal needs to manage its own terminal status.

[0339] The terminal status refers to the connection status between the terminal and the network side. The terminal status can be related to the following connection statuses:

[0340] The connection status between the terminal and the RAN device; and

[0341] The connection status between the terminal and the core network CN.

[0342] The connection status between the terminal and the RAN device may include:

[0343] The terminal has established a connection with the RAN device;

[0344] The terminal suspends the connection with the RAN device;

[0345] The terminal is disconnected from the RAN device.

[0346] The connection status between the terminal and the core network CN may include:

[0347] The terminal has established a connection with the core network.

[0348] In different terminal states, the connection status between the terminal and the network side is different.

[0349] Exemplarily, the RAN device has established a connection with the terminal, and the terminal has established a connection with the core network, which is a first state;

[0350] The RAN device suspends the connection with the terminal, and the terminal has established a connection with the core network, which is the second state;

[0351] The RAN device is disconnected from the terminal, and the terminal has established a connection with the core network, which is the third state.

[0352] It should be understood that the above are examples for the convenience of understanding the embodiments of the present application. The embodiments of the present application do not limit the specific correspondence between the terminal state and the first connection state and the second connection state, and the embodiments of the present application do not limit the naming of different terminal states.

[0353] The terminal status management method provided in the embodiment of the present application is that the terminal manages its own terminal status, and the terminal status is related to a first connection status and a second connection status. The first connection status is the connection status between the RAN device and the terminal, and the second connection status is the connection status between the terminal and the core network CN, which simplifies the terminal status.

[0354] Optionally, the terminal state includes a connected state, an idle state, and an inactive state;

[0355] Or the terminal state includes a connected state and an inactive state;

[0356] The connected state may also be referred to as UE-CONNECTED. The embodiment of the present application does not limit the naming of this state. When the terminal state is the connected state:

[0357] The RAN device stores all terminal contexts of the terminal;

[0358] A radio resource control (RRC) connection between the RAN device and the terminal has been established. For the characteristics of the RRC connection between the RAN device and the terminal being established, reference may be made to the relevant introduction of the RRC connection state (RRC-CONNECTED) and to the relevant technology, which will not be described in detail here;

[0359] The connection between the terminal and the CN has been established, which means that the terminal has established a connection with any NF in the CN. Optionally, the connection between the terminal and the CN has been established, which is a Non-Access Stratum (NAS) connection established between the terminal and any NF in the CN. It should be understood that the establishment of a NAS connection between the terminal and any NF in the CN can refer to the relevant technology. For example, after RAN serviceization, any NF in the CN can establish a NAS connection with the terminal. The role of NF is the same as that of AMF in the relevant technology, such as serving as a termination point for non-access stratum security;

[0360] The connection between the RAN device and the CN has been established, which means that the access network device has established a connection with any CN NF. Optionally, the access network device establishes an N2 connection with any CN NF, such as applying the HyperText Transfer Protocol (HTTP) to the function of the expanded N2 interface between any NF of the access network and the core network, which can refer to the relevant technology.

[0361] The idle state may also be referred to as UE-IDLE. The embodiment of the present application does not limit the naming of this state. When the terminal state is the idle state:

[0362] The RAN device stores the terminal context other than the access stratum (AS) context of the terminal, that is, the RAN stores the terminal context without the AS layer context;

[0363] The RRC connection between the RAN device and the terminal is disconnected. The characteristics of the RRC connection disconnection between the RAN device and the terminal can refer to the relevant introduction of the RRC idle state (RRC-IDLE) and the relevant technology, which will not be repeated here;

[0364] The connection between the RAN device and the CN is maintained, which means that the access network device has established a connection with any CN NF and maintains the connection state. Optionally, the access network device establishes an N2 connection with any CN NF, which is not described here again with reference to the above description.

[0365] Optionally, when the terminal state is the idle state, the method further includes:

[0366] If the N3 connection between the RAN device and the user plane function (UPF) entity is not connected, it remains disconnected.

[0367] Optionally, if an N3 connection has been established between the RAN device and the UPF entity, whether the N3 connection is disconnected is not limited in this embodiment of the application.

[0368] The inactive state may also be referred to as UE-INACTIVE. The embodiment of the present application does not limit the naming of this state. When the terminal state is the inactive state:

[0369] The RAN device stores the terminal context of the terminal. It should be understood that the terminal context stored by the RAN device includes an AS layer context;

[0370] The RRC connection between the RAN device and the terminal is suspended. The characteristics of the RRC connection suspension between the RAN device and the terminal can refer to the relevant introduction of the RRC inactive state (RRC-INACTIVE) and the relevant technology, which will not be repeated here;

[0371] The connection between the RAN device and the CN is maintained, which means that the access network device has established a connection with any CN NF and maintains the connection state. Optionally, the access network device establishes an N2 connection with any CN NF, which is not described here again with reference to the above description.

[0372] The terminal status management method provided in the embodiment of the present application defines different terminal states through a connected state, an idle state, and an inactive state, thereby simplifying the terminal state.

[0373] Optionally, the managing the terminal state of the terminal includes: performing terminal state migration according to a change in a connection between the terminal and the RAN device.

[0374] Specifically, according to a change in the connection between the terminal and the RAN device, the terminal state is migrated from an original state to a new state according to the connection status between the terminal and the RAN device.

[0375] Optionally, performing terminal state migration according to a change in a connection between the terminal and the RAN device includes: performing terminal state migration according to a change in an RRC connection between the terminal and the RAN device.

[0376] Optionally, performing terminal state migration according to a change in a connection between the terminal and the RAN device includes at least one of the following:

[0377] When the terminal state is the connected state, after the RRC connection between the RAN device and the terminal is released, the terminal state is migrated from the connected state to the idle state; or

[0378] When the terminal state is the connected state, after the RRC connection between the RAN device and the terminal is suspended, the terminal state is migrated from the connected state to the inactive state; or

[0379] When the terminal state is the idle state, after the RRC connection between the RAN device and the terminal is established, the terminal state is migrated from the idle state to the connected state; or

[0380] When the terminal state is the inactive state, after the RRC connection between the RAN device and the terminal is restored, the terminal state is migrated from the inactive state to the connected state; or

[0381] When the terminal state is the inactive state, after the RRC connection between the RAN device and the terminal is released, the terminal state is migrated from the inactive state to the idle state.

[0382] In one possible implementation, Figure 8 This is one of the terminal state migration diagrams in the UE provided in the embodiment of the present application, such as Figure 8 As shown, when the terminal state includes a connected state, an idle state, and an inactive state, performing terminal state migration according to a change in the connection between the terminal and the RAN device includes:

[0383] When the terminal state is the connected state, after the RRC connection between the RAN device and the terminal is released, the terminal state is migrated from the connected state to the idle state;

[0384] When the terminal state is the connected state, after the RRC connection between the RAN device and the terminal is suspended, the terminal state is migrated from the connected state to the inactive state;

[0385] When the terminal state is the idle state, after the RRC connection between the RAN device and the terminal is established, the terminal state is migrated from the idle state to the connected state;

[0386] When the terminal state is the inactive state, after the RRC connection between the RAN device and the terminal is restored, the terminal state is migrated from the inactive state to the connected state;

[0387] When the terminal state is the inactive state, after the RRC connection between the RAN device and the terminal is released, the terminal state is migrated from the inactive state to the idle state.

[0388] Optionally, when the terminal state is the inactive state, an RRC recovery request sent by the terminal to the RAN device is rejected, and the terminal state is maintained in the inactive state.

[0389] Optionally, when the terminal state is an idle state, an RRC establishment request sent by the terminal to the RAN device is rejected, and the terminal state is maintained in the idle state.

[0390] In one possible implementation, Fig. 9 This is the second schematic diagram of terminal state migration in the UE provided in the embodiment of the present application, such as Fig. 9 As shown, when the terminal state includes a connected state and an inactive state, performing terminal state migration according to a change in the connection between the terminal and the RAN device includes:

[0391] When the terminal state is the connected state, after the RRC connection between the RAN device and the terminal is suspended, the terminal state is migrated from the connected state to the inactive state;

[0392] When the terminal state is the inactive state, after the RRC connection between the RAN device and the terminal is restored, the terminal state is migrated from the inactive state to the connected state.

[0393] Optionally, when the terminal state is the inactive state, an RRC recovery request sent by the terminal to the RAN device is rejected, and the terminal state is maintained in the inactive state.

[0394] The terminal status management method provided in the embodiment of the present application enables the terminal to migrate the terminal status according to the change of the connection between the terminal and the RAN device, and updates the terminal status when the connection between the terminal and the RAN device changes, thereby managing its own terminal status.

[0395] Optionally, the method further comprises:

[0396] Depending on the terminal state and whether the terminal applies the MICO mode in which only the terminal initiates the connection, the downlink data reception situation is different.

[0397] Specifically, depending on the terminal status and whether the terminal applies the terminal-initiated connection-only MICO mode, the downlink data reception situation is also different. The downlink data reception situation may include whether there is downlink data, and when there is downlink data, receiving the downlink data.

[0398] Optionally, the downlink data reception situation is different according to the terminal state and whether the terminal applies the terminal-initiated connection-only MICO mode, including:

[0399] In the case that the terminal does not apply the terminal-initiated-only connection MICO mode, if the downlink data exists, receiving the downlink data;

[0400] When the terminal state is the connected state and the terminal applies the MICO mode, if the downlink data exists, the downlink data is received.

[0401] Specifically, in the case where the terminal does not apply the MICO mode in which only the terminal initiates the connection, if the downlink data exists, receiving the downlink data:

[0402] The terminal does not apply the MICO mode, and the RAN can send downlink data (Mobile Terminated, MT) to the UE. When there is MT data, the terminal receives the MT data. At this time, the terminal can send MO data or receive MT data.

[0403] In the case where the terminal state is the connected state and the terminal applies the MICO mode, if the downlink data exists, receiving the downlink data:

[0404] When the terminal applies the MICO mode in the connected state, the RAN can still send downlink data MT to the UE. When there is MT data, the terminal receives the MT data. At this time, the terminal can send MO data or receive MT data.

[0405] Optionally, when the terminal state is the idle state or the inactive state and the terminal applies a MICO mode, the downlink data does not exist:

[0406] The terminal applies the MICO mode in the idle state or the inactive state, and the network side does not send downlink data MT to the terminal. Therefore, there is no downlink data, and the terminal does not need to receive the downlink data.

[0407] The terminal status management method provided in the embodiment of the present application relates downlink data reception to the terminal status and whether the MICO mode is applied, thereby ensuring downlink data transmission of the terminal.

[0408] Optionally, the method further comprises:

[0409] When the terminal state is the idle state and the terminal does not apply the MICO mode, monitoring a paging message;

[0410] When the terminal state is the idle state or the inactive state and the terminal applies the MICO mode, the paging message is not monitored.

[0411] Specifically, when the terminal state is the idle state and the terminal does not apply the MICO mode, monitoring the paging message:

[0412] When the terminal is in an inactive state and the MICO mode is not applied to the terminal, the RAN may page the UE, and the UE may correspondingly monitor the paging message and execute the paging process.

[0413] When the terminal state is the idle state or the inactive state and the terminal applies the MICO mode, the paging message is not monitored:

[0414] When the terminal applies the MICO mode in the idle state or the inactive state, the network side will not initiate paging to the terminal, so the terminal does not need to monitor the paging message.

[0415] The terminal status management method provided in the embodiment of the present application monitors paging messages when the terminal status is the idle state and the terminal does not apply the MICO mode to avoid the terminal missing messages; when the terminal status is the idle state or the inactive state and the terminal applies the MICO mode, does not monitor paging messages to avoid the terminal wasting resources for monitoring.

[0416] Optionally, the method further includes but is not limited to at least one of the following:

[0417] When the terminal enters the idle state, starting a periodic RRC establishment timer, the periodic RRC establishment timer is used to indicate a first timer value, and performing an RRC establishment process based on the first timer value; or

[0418] When the terminal state is the inactive state, after the terminal moves out of the radio access network notification area RNA, an RNA update process is executed; or

[0419] When the terminal enters the inactive state, a periodic notification area update timer is started, the periodic notification area update timer is used to indicate a second timer value, and an RNA update process is performed based on the second timer value.

[0420] Specifically, for the periodic RRC establishment timer, the periodic RRC establishment timer is configured by the RAN for the UE, the UE receives the periodic RRC establishment timer sent by the RAN, and when the terminal enters the idle state, the terminal starts the periodic RRC establishment timer. When the periodic RRC establishment timer exceeds the first timer value, the terminal executes the RRC establishment process.

[0421] In the embodiment of the present application, a periodic RRC establishment timer is used to enable the terminal to regularly establish an RRC connection and maintain a connection with the RAN.

[0422] For the periodic notification area update timer, the periodic notification area update timer is configured by the RAN for the UE. The UE receives the periodic notification area update timer sent by the RAN. When the UE enters the inactive state UE-INACTIVE, the UE starts the periodic notification area update timer. When the periodic notification area update timer exceeds the second timer value, the UE executes the RAN notification area update process.

[0423] In the embodiment of the present application, a periodic notification area update timer is used to enable the terminal to regularly execute the RAN notification area update process, so that the RAN synchronizes the location information of the terminal, and the terminal state can be migrated through the RAN notification area update process, such as restoring the RRC connection, migrating from the inactive state to the connected state; when the RAN sends an RRC release message, it migrates from the inactive state to the idle state; when the RAN sends an RRC suspend message, it maintains the inactive state.

[0424] Optionally, in the case of migrating the terminal state from the connected state to the idle state, or maintaining the idle state, or migrating the terminal state from the inactive state to the idle state, the method also includes: receiving an RRC release message sent by the RAN device, and releasing the RRC connection based on the RRC release message.

[0425] Specifically, an RRC release message sent by the RAN device is received, and the RRC connection is released based on the RRC release message; if the terminal is in a connected state, after the RRC connection is released, the terminal state is migrated from the connected state to the idle state; if the terminal is in an inactive state, the terminal state is migrated from the inactive state to the idle state; if the terminal is in an idle state, the terminal state is maintained in the idle state.

[0426] Optionally, when migrating the terminal state from the connected state to the inactive state and maintaining the inactive state, the method further includes: receiving an RRC suspend message sent by the RAN device, and suspending the RRC connection based on the RRC suspend message.

[0427] Specifically, an RRC suspend message sent by the RAN device is received, and the RRC connection is suspending based on the RRC suspend message, and if the terminal is in a connected state, the terminal state is migrated from the connected state to the inactive state; if the terminal is in an inactive state, the terminal state is maintained in the inactive state.

[0428] In the embodiment of the present application, the RRC connection state is determined by the RAN side, thereby changing the terminal state of the UE, and the UE changes or maintains the terminal state according to the behavior of the RAN side.

[0429] Optionally, when the terminal state is the idle state, the method further includes at least one of the following:

[0430] The terminal actively initiates an RRC establishment process to establish an RRC connection with the RAN device; or

[0431] The periodic RRC establishment timer received by the terminal times out, and the terminal initiates an RRC establishment procedure to establish an RRC connection with the RAN device; or

[0432] The terminal triggers an RRC establishment process in response to the network side paging, and establishes an RRC connection with the RAN device.

[0433] The terminal actively initiates an RRC establishment process to establish an RRC connection with the RAN device, and after the RRC connection between the RAN device and the terminal is established, migrates the terminal state from the idle state to the connected state;

[0434] When a periodic RRC establishment timer received by the terminal times out, the terminal initiates an RRC establishment procedure to establish an RRC connection with the RAN device, and after the RRC connection between the RAN device and the terminal is established, migrates the terminal state from the idle state to the connected state;

[0435] The terminal responds to the network side paging to trigger the RRC establishment process, establishes an RRC connection with the RAN device, and after the RRC connection between the RAN device and the terminal is established, the terminal state is migrated from the idle state to the connected state.

[0436] Optionally, the method further comprises:

[0437] receiving a first RRC reject message sent by the RAN device, where the first RRC reject message is used to indicate that an RRC connection establishment failure has occurred;

[0438] The terminal state remains in the idle state.

[0439] Optionally, the first RRC rejection message carries a first waiting time, and the method further includes:

[0440] The terminal initiates an RRC establishment request after the first waiting time.

[0441] Optionally, when the terminal state is the inactive state, the method further includes at least one of the following:

[0442] The terminal actively initiates an RRC recovery procedure to restore the RRC connection with the RAN device; or

[0443] After the terminal moves out of the RNA, it initiates an RRC recovery process to restore the RRC connection with the RAN device; or

[0444] The periodic RNA update timer received by the terminal times out, and the terminal initiates an RRC recovery procedure to restore the RRC connection with the RAN device; or

[0445] The terminal triggers the RRC recovery process in response to the network side paging, and recovers the RRC connection with the RAN device.

[0446] The terminal actively initiates an RRC recovery process to restore the RRC connection with the RAN device, and after the RRC connection between the RAN device and the terminal is restored, the terminal state is migrated from the inactive state to the connected state;

[0447] After the terminal moves out of the RNA, an RRC recovery process is initiated to restore the RRC connection with the RAN device. After the RRC connection between the RAN device and the terminal is restored, the terminal state is migrated from the inactive state to the connected state;

[0448] When a periodic RNA update timer received by the terminal times out, the terminal initiates an RRC recovery procedure to restore the RRC connection with the RAN device, and after the RRC connection between the RAN device and the terminal is restored, migrates the terminal state from the inactive state to the connected state;

[0449] The terminal responds to the network side paging to trigger the RRC recovery process and restores the RRC connection with the RAN device. After the RRC connection between the RAN device and the terminal is restored, the terminal state is migrated from the inactive state to the connected state.

[0450] Optionally, the method further comprises:

[0451] receiving a second RRC reject message sent by the RAN device, where the second RRC reject message is used to indicate that the RRC connection recovery fails;

[0452] The terminal state remains in the inactive state.

[0453] Optionally, the second RRC rejection message carries a second waiting time, and the method further includes:

[0454] The terminal initiates an RRC recovery request after the second waiting time.

[0455] Optionally, when the terminal state is the inactive state and the RRC connection is restored in response to network side paging, or when the terminal state is the idle state and the RRC connection is established in response to network side paging, the method further includes:

[0456] Receive buffered data sent by the RAN device, where the buffered data is downlink data sent by a network side to the terminal in the inactive state or the idle state.

[0457] Fig.10 This is a flowchart of the terminal status management method provided in the embodiment of the present application. Fig.10 As shown, the embodiment of the present application provides a terminal status management method, which is applied to a core network CN device, including:

[0458] Step 1010, determining a registration management RM state of the terminal, and interacting with the terminal through an access network RAN ​​device according to the RM state of the terminal, wherein the RM state is used to indicate whether the terminal is registered with the CN; or

[0459] After the terminal registers with the CN, the RAN device interacts with the terminal.

[0460] Specifically, Registration Management (RM) is used to register or deregister (join or leave the network) a UE with the core network.

[0461] The registration management RM state is managed by any NF in the core network, and optionally, the RM state is managed by AMF.

[0462] Optionally, the registration management RM status may include:

[0463] Not registered in RM-DEREGISTERED state; and

[0464] Register RM-REGISTERED status.

[0465] The RM-DEREGISTERED state indicates that the UE is not registered with the network. In this state, there is no valid location or routing information for the UE in the UE context in the AMF, so the AMF cannot reach the UE. However, some information of the UE context can still be stored in the UE and AMF to avoid identity authentication during each registration process.

[0466] The RM-REGISTERED state indicates that the UE has registered with the network.

[0467] For interacting with the terminal through the RAN device after the terminal registers with the CN, the core network does not need to obtain the RM state of the terminal. As long as the CN considers the terminal reachable after the terminal is registered, it can interact with the UE through the RAN.

[0468] In the terminal status management method provided in the embodiment of the present application, the core network only needs to manage the RM status of the UE: as long as the terminal registers with the core network, after the status of the UE in the core network changes from the RM-DEREGISTRATION status to the RM-REGISTRATION status, or as long as the terminal is registered, the core network considers that the UE is in a connected state and is reachable, and the core network no longer needs to manage the connection status of the UE, thereby reducing the overhead of the core network in managing the UE status, streamlining the functions and interaction processes of the UE and the core network (no need to execute the UE-triggered Service Request process, the network-triggered Service Request process, and the AN release process), and at the same time avoiding the UE status synchronization problem between the core network NFs after RAN service-oriented.

[0469] Optionally, the interacting with the terminal through an access network RAN ​​device according to the RM state of the terminal includes:

[0470] When the registration management RM state of the terminal is registered, the RAN device directly interacts with the terminal.

[0471] The terminal status management method provided in the embodiment of the present application no longer distinguishes the terminal status. Since the terminal status is not distinguished, it can be understood that the terminal is stateless. The terminal, RAN and core network no longer need to manage the UE status. As long as the terminal registers with the network, the core network considers the terminal to be reachable, reducing the overhead of the terminal, RAN and core network in managing the UE status, and streamlining the functions and interaction processes of the UE and the core network.

[0472] Optionally, when the CN device is a session management function SMF entity, the method further includes:

[0473] receiving a protocol data unit (PDU) session update context request sent by the RAN device, wherein the PDU session update context request carries PDU session information of a target PDU session;

[0474] Determine a user plane function UPF entity based on the PDU session information, the UPF entity being used to send buffered data to the RAN device, the buffered data being downlink data sent by the network side to the terminal in an inactive state or an idle state;

[0475] The tunnel information of the RAN device is sent to the UPF entity, where the tunnel information of the RAN device is used to establish a data transmission tunnel between the UPF entity and the RAN device, and the data transmission tunnel is used to transmit the buffered data.

[0476] Specifically, the target PDU session is an affected PDU session.

[0477] For a terminal in an inactive state, refer to the above description of the inactive state, which will not be repeated here. For a terminal in an idle state, refer to the above description of the idle state, which will not be repeated here.

[0478] Optionally, when the CN device is a session management function SMF entity, the method further includes:

[0479] Determine the anchor RAN device;

[0480] The tunnel information of the anchor RAN device is sent to the UPF entity, where the tunnel information of the anchor RAN device is used to establish a data transmission tunnel between the UPF entity and the anchor RAN device, where the data transmission tunnel is used to transmit the buffered data.

[0481] In one possible implementation, the original UPF is a UPF that has established a data transmission tunnel with the anchor access network device and has served the UE. If the original UPF (which can be referred to as S-UPF) can still serve the UE, SMF can select the original UPF for data forwarding:

[0482] SMF sends an N4 Session Modification Request message to S-UPF to establish a forwarding path from S-UPF to RAN:

[0483] The SMF sends the tunnel information of the current RAN to the S-UPF to establish a data transmission tunnel between the S-UPF and the current RAN. Optionally, the SMF may send the forwarding path of the buffered data of the forwarding anchor access network device to the S-UPF.

[0484] After the data transmission tunnel is established, the anchor access network device can send buffered data to the S-UPF, and the S-UPF sends the buffered data to the current RAN, thereby realizing indirect data forwarding (Indirect data forwarding) by the anchor access network device to the current RAN through the S-UPF.

[0485] In one possible implementation, the S-UPF cannot serve the UE. If the UE has moved out of the service area of ​​the original UPF (S-UPF) connected to the anchor point, the protocol data unit session anchor (PDU Session Anchor, PSA) remains unchanged, and a new UPF is selected and inserted. The new UPF can be referred to as the target UPF (Target-UPF, abbreviated as T-UPF):

[0486] SMF sends the tunnel information of PSA and RAN to T-UPF. It establishes a data transmission tunnel between T-UPF and the current RAN, and a data transmission tunnel between T-UPF and PSA.

[0487] SMF sends an N4 Session Modification Request message to S-UPF to establish a data transmission tunnel between S-UPF and T-UPF, so that the buffered data of the anchor access network device can be forwarded to S-UPF and then to T-UPF through the anchor access network device, and finally forwarded to the current RAN through T-UPF.

[0488] The anchor access network device sends the buffered data to the S-UPF, the S-UPF sends the buffered data to the T-UPF, and the T-UPF sends the buffered data to the current RAN, thereby realizing indirect data forwarding by the anchor access network device to the current RAN through the S-UPF and T-UPF.

[0489] Optionally, the SMF sends an N4 Session Modification Request message to the PSA to establish a data transmission tunnel between the PSA and the T-UPF.

[0490] Optionally, the SMF sends the tunnel information of the T-UPF to the current RAN to establish an uplink forwarding tunnel (data transmission tunnel) from the T-UPF to the RAN.

[0491] Optionally, after the buffered data is sent, the SMF releases the S-UPF.

[0492] The SMF entity establishes a data transmission tunnel between the UPF and the anchor RAN device, thereby transmitting buffered data between the UPF and the anchor RAN device, so that the terminal can receive the buffered data and avoid missing data.

[0493] The following describes a terminal status management method provided by an embodiment of the present application in combination with multiple embodiments. The serial numbers of the following embodiments are only used to distinguish different embodiments.

[0494] Embodiment 1:

[0495] The terminal states include a connected state UE-CONNECTED, an idle state UE-IDLE and an inactive state UE-INACTIVE.

[0496] The registration management RM state is managed by any CN NF, and optionally by AMF. The state definition and transition of RM refer to the relevant technology and will not be repeated here.

[0497] (I) Terminal status definition:

[0498] For UE-CONNECTED state:

[0499] All UE contexts are stored in the RAN;

[0500] RRC connection maintenance;

[0501] NAS connection is maintained. Here, NAS connection refers to the NA connection between UE and CN NF through N1. CN NF is the NF that has direct interaction requirements with UE. The NAS connection maintenance means that UE can establish a NAS connection with any CN NF.

[0502] The N2 (broadly defined as N2, the same below) connection between AN (also referred to as access network equipment) and NF is maintained, where N2 refers to the interface for interaction between RAN and NF; N2 connection maintenance means that AN has a connection with any CN NF.

[0503] For UE-IDLE:

[0504] RAN saves UE context (excluding AS layer context), UE does not save AS layer context;

[0505] The RRC connection is disconnected;

[0506] N2 connection is maintained. The N2 connection between AN and NF is maintained. Here, N2 refers to the interface between RAN and NF. N2 connection maintenance means that AN has a connection with any CN NF.

[0507] N3 connection is disconnected;

[0508] Optionally, if the N3 connection has been established, whether the N3 connection must be disconnected is not limited in this embodiment of the present application.

[0509] For RRC-INACTIVE state:

[0510] The UE context (including AS layer context) is stored in the RAN;

[0511] The RRC connection is suspended, retaining the characteristics of the RRC-INACTIVE state;

[0512] N2 connection maintenance;

[0513] If the N3 connection has been established, the N3 connection is maintained.

[0514] Among them, NAS connection refers to the NA connection between UE and CN NF through N1, and CN NF is the NF that has direct interaction requirements with UE; the NAS connection maintenance means that UE has established a NAS connection with any CN NF; N2 refers to the interface for interaction between RAN and NF; N2 connection maintenance means that AN has a connection with any CN NF; the UE context in RAN also includes the NF information serving the UE and other contents.

[0515] (II) Terminal State Migration

[0516] The state transition in UE is as follows: Figure 8 As shown:

[0517] In UE-IDLE state, the UE shall:

[0518] When the RRC connection between the UE and the RAN has been established, the UE enters the UE-CONNECTED state from the UE-IDLE state.

[0519] When the RRC establishment request initiated by the UE is rejected, the UE remains in the UE-IDLE state.

[0520] In UE-CONNECTED state, the UE shall:

[0521] When the RRC connection between the UE and the RAN is released, the UE enters the UE-IDLE state from the UE-CONNECTED state.

[0522] When the RRC connection between the UE and the RAN is suspended, the UE enters the UE-INACTIVE state from the UE-CONNECTED state.

[0523] In UE-INACTIVE state, the UE shall:

[0524] When the RRC connection between the UE and the RAN is restored, the UE enters the UE-CONNECTED state from the UE-INACTIVE state.

[0525] When the RRC recovery request initiated by the UE is rejected, the UE remains in the UE-INACTIVE state.

[0526] After the UE receives the RRC suspension configuration from the network side, the UE remains in the UE-INACTIVE state.

[0527] When the UE receives the RRC release message from the network side, the UE enters the UE-IDLE state from the UE-INACTIVE state.

[0528] UE state transition in RAN is as follows: Figure 5 As shown:

[0529] When the UE in the RAN is in the UE-CONNECTED state, the RAN shall:

[0530] When the RRC connection between the RAN and the UE is released, the UE state in the RAN changes to the UE-IDLE state.

[0531] When RAN initiates RRC connection suspension, the UE state in RAN changes to UE-INACTIVE state.

[0532] When the UE in the RAN is in the UE-IDLE state, the RAN shall:

[0533] When the RRC connection between the RAN and the UE is established, the UE state in the RAN changes to the UE-CONNECTED state.

[0534] When the UE in the RAN is in the UE-INACTIVE state, the RAN shall:

[0535] When the RRC connection between the RAN and the UE is restored, the UE state in the RAN changes to the UE-CONNECTED state.

[0536] When the RRC connection between the RAN and the UE is released, the UE state in the RAN changes to the UE-IDLE state.

[0537] 3. Accessibility Management

[0538] Reachability management is responsible for detecting whether the UE is reachable and providing the network with the UE's location information so that the network can find the UE. The search process is completed by paging the UE and tracking the UE location. The UE location tracking includes UE registration area tracking (UE registration area update) and UE reachability tracking (UE periodic registration area update). The reachability management function is located in the RAN.

[0539] UE-CONNECTED state:

[0540] The UE location information known to the network (RAN and core network) is at the cell granularity.

[0541] The UE applies the MICO mode, in which the UE can receive MT data.

[0542] UE-IDLE state:

[0543] The UE location information known to the network (RAN and core network) is at the TAlist granularity.

[0544] In the case that the UE does not apply the MICO mode, the RAN can page the UE. In the case that the UE applies the MICO mode, the RAN cannot page the UE.

[0545] In case the UE does not apply the MICO mode, the UE may have MO and MT data.

[0546] The UE applies the MICO mode and can only send MO data. The RAN considers the UE unreachable and the UE does not need to monitor paging.

[0547] When the UE enters the UE-IDLE state, the UE starts a periodic RRC establishment timer. After the timer expires, the UE executes the RRC establishment process (the timer is received by the UE from the RAN during the registration process, and the RAN allocates the periodic RRC establishment timer value to the UE based on local policies, information provided by the UE, etc.).

[0548] When the UE enters UE-IDLE, the RAN starts a mobile reachable timer (MobileReachabletimer) for the UE. This timer is longer than the periodic RRC establishment timer. When the timer expires, the RAN considers that the UE is unreachable. The RAN may request the AMF to initiate an implicit deregistration process. After receiving the request, the AMF starts the implicit deregistration timer.

[0549] The RAN needs to obtain relevant information about the UE applying the MICO mode. The embodiment of the present application does not limit how to obtain the application of the MICO mode.

[0550] UE-INACTIVE state:

[0551] The UE location information known to the network is at RNA granularity, where RNA can be part of the cells configured in the UE registration area or all the cells configured in the UE registration area.

[0552] The UE can be paged in a cell located in the RAN notification area RNA (unless the UE applies MICO mode).

[0553] In case the UE does not apply the MICO mode, the UE may have MO and MT data.

[0554] The UE applies the MICO mode and can only send MO data. The RAN considers the UE unreachable and the UE does not need to monitor paging.

[0555] When the UE moves out of the RAN notification area, the UE needs to perform the RAN notification area update procedure.

[0556] When the UE enters the UE-INACTIVE state, the RAN configures a periodic RAN notification area update timer value for the UE, and the UE starts the timer. When the periodic RAN notification area update timer in the UE times out, the UE executes the RAN notification area update procedure.

[0557] When the UE enters the UE-INACTIVE state, a protection timer is started in the RAN, whose value is longer than the RAN notification area update timer value provided to the UE. When the timer expires, the RAN starts the RRC release procedure and the UE enters the RRC-IDLE state.

[0558] Embodiment 2:

[0559] The terminal status includes a connected state UE-CONNECTED and an inactive state UE-INACTIVE.

[0560] The registration management RM state is managed by any CN NF, and optionally by AMF. The state definition and transition of RM refer to the relevant technology and will not be repeated here.

[0561] (I) Terminal status definition:

[0562] For UE-CONNECTED state:

[0563] All UE contexts are stored in the RAN;

[0564] RRC connection maintenance;

[0565] NAS connection is maintained. Here, NAS connection refers to the NA connection between UE and CN NF through N1. CN NF is the NF that has direct interaction requirements with UE. The NAS connection maintenance means that UE can establish a NAS connection with any CN NF.

[0566] The N2 (broadly defined as N2, the same below) connection between AN (also referred to as access network equipment) and NF is maintained, where N2 refers to the interface for interaction between RAN and NF; N2 connection maintenance means that AN has a connection with any CN NF.

[0567] For RRC-INACTIVE state:

[0568] The UE context (including AS layer context) is stored in the RAN;

[0569] The RRC connection is suspended, retaining the characteristics of the RRC-INACTIVE state;

[0570] N2 connection maintenance;

[0571] If the N3 connection has been established, the N3 connection is maintained.

[0572] Among them, NAS connection refers to the NA connection between UE and CN NF through N1, and CN NF is the NF that has direct interaction requirements with UE; the NAS connection maintenance means that UE has established a NAS connection with any CN NF; N2 refers to the interface for interaction between RAN and NF; N2 connection maintenance means that AN has a connection with any CN NF; the UE context in RAN also includes the NF information serving the UE and other contents.

[0573] (II) Terminal State Migration

[0574] The state transition in UE is as follows: Fig. 9 As shown:

[0575] In UE-INACTIVE state, the UE shall:

[0576] When the RRC connection between the UE and the RAN is restored, the UE enters the UE-CONNECTED state from the UE-INACTIVE state.

[0577] When the RRC recovery request between the UE and the RAN is rejected, the UE remains in the UE-INACTIVE state.

[0578] In UE-CONNECTED state, the UE shall:

[0579] When the RRC connection between the UE and the RAN is suspended, the UE enters the UE-INACTIVE state from the UE-CONNECTED state.

[0580] UE state transition in RAN is as follows: Figure 6 As shown:

[0581] When the UE in the RAN is in the UE-CONNECTED state, the RAN shall:

[0582] When the RRC connection between the RAN and the UE is suspended, the UE state in the RAN enters the UE-INACTIVE state.

[0583] When the UE in the RAN is in the UE-INACTIVE state, the RAN shall:

[0584] When the RRC connection between the RAN and the UE is restored, the UE state in the RAN enters the UE-CONNECTED state.

[0585] 3. Accessibility Management

[0586] Reachability management is responsible for detecting whether the UE is reachable and providing the network with the UE's location information so that the network can find the UE. The search process is completed by paging the UE and tracking the UE location. The UE location tracking includes UE registration area tracking (UE registration area update) and UE reachability tracking (UE periodic registration area update). The reachability management function is located in the RAN.

[0587] UE-CONNECTED state:

[0588] The UE location information known to the network (RAN and core network) is at the cell granularity.

[0589] The UE applies the MICO mode, in which the UE can receive MT data.

[0590] UE-INACTIVE state:

[0591] The UE location information known to the network is at RNA granularity, where RNA can be part of the cells configured in the UE registration area or all the cells configured in the UE registration area.

[0592] The UE can be paged in a cell located in the RAN notification area RNA (unless the UE applies MICO mode).

[0593] In case the UE does not apply the MICO mode, the UE may have MO and MT data.

[0594] The UE applies the MICO mode and can only send MO data. The RAN considers the UE unreachable and the UE does not need to monitor paging.

[0595] When the UE moves out of the RAN notification area, the UE needs to perform the RAN notification area update procedure.

[0596] When the UE enters the UE-INACTIVE state, the RAN configures a periodic RAN notification area update timer value for the UE, and the UE starts the timer. When the periodic RAN notification area update timer in the UE times out, the UE executes the RAN notification area update procedure.

[0597] When the UE enters the UE-INACTIVE state, a protection timer is started in the RAN, whose value is longer than the RAN notification area update timer value provided to the UE. When the timer expires, the RAN starts the RRC release procedure and the UE enters the RRC-IDLE state.

[0598] Example 3: Conversion from UE-CONNECTED to UE-IDLE

[0599] When the RAN side decides to release the connected UE to enter the UE-IDLE state, the RAN notifies the UE through the RRC release RRCRelease message.

[0600] Fig.11 This is one of the state transition flow diagrams provided in the embodiment of the present application, such as Fig.11 As shown, if the network side wants the UE to enter or maintain the UE-IDLE state, the RAN sends a RRCRelease message to the UE;

[0601] After the UE receives the RRCRelease message, it enters the UE-IDLE state.

[0602] Optionally, when it is determined to migrate the terminal state from the connected state to the idle state, or to maintain the idle state, or to migrate the terminal from the inactive state to the idle state, and when it is determined to release the N3 interface, the gNB sends a PDU session update SM context request Nsmf_PDUSession_UpdateSMContextRequest message to the SMF, indicating that the UE cannot access downlink data, and the SMF sends an N4 session modification request N4 SessionModification Request message to the UPF, instructing the UPF to release the user plane resources on the N3 side, and at the same time instructing the UPF to buffer DL data packets, the UPF sends an N4 session modification response N4 Session Modification Response message to the SMF, and the SMF sends a PDU session update SM context response Nsmf_PDUSession_UpdateSMContext Response message to the gNB.

[0603] Example 4: UE-CONNECTED to UE-INACTIVE conversion

[0604] When the RAN side decides to suspend the connected UE to enter the UE-INACTIVE state, the RAN notifies the UE through an RRC suspension message.

[0605] Fig.12 This is the second state transition flow diagram provided in the embodiment of the present application. Fig.12As shown, if the network side wants the UE to enter or maintain the UE-INACTIVE state, the RAN sends a suspend message RRCRelease with Suspend message to the UE, that is, the RRCRelease message carries the suspend information, and the suspend information may include relevant configurations such as RNA.

[0606] When the UE receives the RRC Release with Suspend message, it can find the configuration information for entering the UE-ACTIVE state in the RRC release message. The UE then stores the inactive state configuration, the AS layer context, suspends the current air interface connection, and enters the UE-ACTIVE state.

[0607] Embodiment five:

[0608] (1) The UE triggers the UE-IDLE to UE-CONNECTED state transition successfully

[0609] Fig.13 This is the third state transition flow diagram provided in the embodiment of the present application, such as Fig.13 As shown in the figure, if a UE in idle state wants to initiate a call or respond to a paging, the RRC establishment process will be triggered:

[0610] Step 1: When the UE is in idle state, it sends an RRC Setup Request message to the gNB.

[0611] Step 2: gNB sends an RRCSetup message to the UE.

[0612] The UE enters the connected state.

[0613] Step 3: The UE sends an RRCSetup Complete message to the gNB. The UE and gNB complete the RRCsetup process.

[0614] Step 4: The current gNB (i.e., the gNB in ​​the figure) determines the anchor gNB, which is the gNB that last served the UE when the UE entered the idle state or inactive state. If the current serving gNB is not the same as the anchor gNB, the gNB sends a request Nran_UEContextTransfer Request message to the anchor gNB to obtain the AS context.

[0615] Step 5: The anchor gNB provides the stored UE context to the current gNB via the context response Nran_UEContextTransfer Response message.

[0616] Step 6a and step 6b: The gNB sends a SecurityModeCommand message to the UE, and the UE sends a SecurityModeComplete message to the gNB. The gNB and the UE activate the AS security mode.

[0617] Step 7a and step 7b: the gNB sends an RRC reconfiguration RRCReconfiguration message to the UE, the UE sends an RRC reconfiguration completion RRCReconfigurationComplete message to the gNB, and the gNB performs RRC reconfiguration to establish a radio signaling bearer (SRB) 2 and a radio data bearer (DRB) for the UE; optionally, the gNB performs RRC reconfiguration to establish SRB2 for the UE and DRB for IAB-MT (IAB node supports UE-related functions).

[0618] Step 8: If lossless transmission of downlink data (buffered data) cached in the anchor gNB is required, the current gNB provides the data forwarding address to the anchor gNB through the Nran_xx_AddrTransfer message. After receiving the message, the anchor gNB starts forwarding the buffered data to the gNB through direct or indirect forwarding.

[0619] Step 9: The gNB (i.e. the current gNB) sends a PDU session update SM context request Nsmf_PDUSession_UpdateSMContext Request message to the SMF.

[0620] Step 9a: The current gNB triggers path switching.

[0621] Step 10: SMF sends a PDU session update SM context response Nsmf_PDUSession_UpdateSMContext Response message to gNB.

[0622] Step 11: The current gNB sends a UE context release request Nran_UEContextReleaseRequest message to the anchor gNB. The anchor gNB releases the UE context. The anchor gNB sends a UE context release response Nran_UEContextRelease Response message to the current gNB.

[0623] (2) The UE-IDLE to UE-CONNECTED process triggered by the UE fails

[0624] Fig.14This is the fourth state transition flow diagram provided in the embodiment of the present application, such as Fig.14 As shown, if the gNB refuses to establish RRC for the UE, it replies to the UE with an RRCReject message, which may carry a first waiting time, indicating that the UE is suitable to initiate an access process. After receiving the RRCReject message, the UE remains in the UE-IDLE state.

[0625] Optionally, the method further comprises:

[0626] In a case where the RAN refuses to establish an RRC connection for the terminal, a first RRC reject RRCReject message is sent to the terminal.

[0627] Optionally, the first RRC rejection message carries a first waiting time, and the first waiting time is used to instruct the UE to initiate an RRC establishment request after the first waiting time.

[0628] Optionally, when the UE receives the first RRC rejection message sent by the RAN device, the terminal state remains in the idle state.

[0629] Example 6: UE state transition in UE-INACTIVE

[0630] (I) UE triggers UE-INACTIVE to UE-CONNECTED state transition

[0631] Fig.15 This is the fifth state transition flow diagram provided in the embodiment of the present application, such as Fig.15 As shown, if the UE in the inactive state wants to initiate a call or respond to a paging, the recovery process will be triggered:

[0632] Step 1: The inactive UE sends an RRC Resume Request message to the gNB.

[0633] Step 2: After receiving the RRC recovery request from the UE, the current gNB (the gNB currently serving the terminal, in the figure, is gNB) determines the anchor gNB, which refers to the gNB that last served the UE when the UE entered the idle state or inactive state. If the current serving gNB is not the same as the anchor gNB, the gNB sends a UE context forwarding request Nran_UEContextTransfer Request message to the anchor gNB to obtain all the contexts of the UE.

[0634] Step 3: The anchor gNB provides the current gNB (the gNB currently serving the terminal, gNB in ​​the figure) with the stored UE context, such as sending the UE context via the UE context forwarding response Nran_UEContextTransfer Response message.

[0635] Step 4: The current gNB generates the RRC configuration based on the received UE context, and then sends an RRC recovery RRCResume message to the UE.

[0636] The RRC connection is restored and the terminal state is transferred from the inactive state to the connected state.

[0637] Step 5: After the UE completes the RRC recovery message configuration, it sends an RRC recovery complete message to the current gNB.

[0638] Step 6: If lossless transmission of downlink data (buffered data) cached in the anchor gNB is required, the current gNB provides the data forwarding address to the anchor gNB. After receiving the message, the anchor gNB starts forwarding the buffered data (downlink user data) to the gNB directly or indirectly.

[0639] Steps 7-8: The current gNB sends 6.Nsmf_PDUSession_UpdateSMContext Request message to SMF, SMF performs path conversion, and SMF sends Nsmf_PDUSession_UpdateSMContext Response message to the current gNB.

[0640] Step 9: The current gNB sends a UE context release message to the anchor gNB, and the anchor gNB releases the UE context.

[0641] It should be understood that in the related technology, the gNB and the anchor gNB transfer the UE context through the Xn interface. After the RAN is serviced, any RANs can interact with each other, so the UE context transfer is no longer limited to RANs with Xn interfaces.

[0642] (II) UE context extraction fails partially or completely during UE-INACTIVE to UE-CONNECTED state transition triggered by UE

[0643] Fig.16 This is the sixth state transition flow diagram provided in the embodiment of the present application, such as Fig.16 As shown:

[0644] Step 1: The inactive UE sends an RRC Resume Request message to the gNB.

[0645] Step 2: After receiving the RRC recovery request from the UE, the current gNB (the gNB currently serving the terminal, in the figure, is gNB) determines the anchor gNB, which refers to the gNB that last served the UE when the UE entered the idle state or inactive state. If the current serving gNB is not the same as the anchor gNB, the gNB sends a request message to the anchor gNB to obtain the UE context (all).

[0646] Step 3: The anchor gNB fails to extract or verify the UE context partially or completely.

[0647] Step 4: If the anchor gNB cannot extract the AS layer context, but the UE network side context can be extracted, or the anchor gNB cannot verify the AS context data, the anchor gNB notifies the gNB of the failure to obtain the network side UE context and the AS layer, and executes steps 5 and 5a.

[0648] Step 4.1: If the anchor gNB fails to extract any UE context information or cannot verify all AS layer context data, the anchor gNB returns the result of acquisition failure to the current gNB, and provides the current gNB with a RRCRelease message to put the UE into the UE-IDLE state, and then executes step 6.

[0649] Step 5: The current gNB sends an RRCSetup message to establish a new RRC connection.

[0650] Step 5a: The new RRC establishment process is the same as that described in Example 5 (I) where the UE triggers the successful transition from UE-IDLE to UE-CONNECTED state.

[0651] Step 6: The current gNB sends a RRCRelease message to the UE, causing the UE to enter the UE-IDLE state.

[0652] (III) UE-INACTIVE to UE-CONNECTED state transition failure triggered by UE

[0653] Fig.17 This is the seventh state transition flow diagram provided in the embodiment of the present application, such as Fig.17 As shown, if the current gNB (the gNB currently serving the terminal, gNB in ​​the figure) refuses to restore the RRC connection for the UE (for example, the current gNB is congested), the gNB sends a second RRCReject message to the UE, carrying a second waiting time, instructing the UE to initiate the RRC recovery process again at an appropriate time. After receiving the message, the UE remains in the UE-INACTIVE state.

[0654] Optionally, the method further comprises:

[0655] In a case where the RAN refuses to restore the RRC connection for the terminal, a second RRC reject RRCReject message is sent to the terminal.

[0656] Optionally, the second RRC rejection message carries a second waiting time, and the second waiting time is used to instruct the UE to initiate an RRC recovery request after the second waiting time.

[0657] Optionally, when the UE receives the second RRC reject message sent by the RAN device, the terminal state remains in the inactive state.

[0658] (IV) RNA (RAN Notification Area) Update

[0659] Fig.18 This is one of the schematic diagrams of the RNA update process provided in the embodiments of the present application, such as Fig.18 As shown, when the network side releases the UE to the inactive state, it can configure a timer duration of a periodic notification area update timer for the UE, and the UE starts the periodic notification area update timer when entering the inactive state.

[0660] Due to the expiration of the periodic RNA update timer or when the UE moves out of the RNA configured on the network side, the inactive UE may trigger the RRC recovery procedure.

[0661] Step 1: The UE in the inactive state sends an RRC recovery request (RRC RNA Update) message to the gNB.

[0662] Step 2: After receiving the RRC recovery request from the UE, the current gNB (the gNB currently serving the terminal, in the figure, is gNB) determines the anchor gNB, which refers to the gNB that last served the UE when the UE entered the idle state or inactive state. If the current serving gNB is not the same as the anchor gNB, the gNB sends a request message to the anchor gNB to obtain the UE context (all).

[0663] Step 3: The anchor gNB provides the current gNB with its stored UE context.

[0664] Step 4: The current gNB generates RRC configuration based on the received UE context and decides to release the UE to the inactive state.

[0665] Step 5: If lossless transmission of buffered data in the anchor gNB is required, the current gNB provides the data forwarding address to the anchor gNB. After receiving the message, the anchor gNB starts forwarding the buffered data to the gNB directly or indirectly.

[0666] Step 6-7: The current gNB sends 6.Nsmf_PDUSession_UpdateSMContext Request message to SMF, SMF performs path conversion, and SMF sends Nsmf_PDUSession_UpdateSMContext Response message to the current gNB.

[0667] Step 8: The current gNB sends an RRC suspend RRCRelease with Suspend Indication message to the UE.

[0668] Step 9: The current gNB sends a UE context release message to the anchor gNB, and the anchor gNB releases the UE context.

[0669] Among them, in steps 4 to 9, if the UE or the network side needs to send data in addition to RNA update, the current gNB transfers the UE to the UE-CONNECTED state. If the connection does not need to be restored, the current gNB can directly release the UE to the UE inactive state after completing the path switching.

[0670] Optionally, in step 4, the UE may also be released to the UE idle state.

[0671] (V) RNA update process without anchor gNB change

[0672] When the anchor gNB knows that the UE is only performing a simple RNA update process, it may not update the RAN side node storing the UE context, but instead generate an RRCsuspend message to release the UE back to the UE-INACTIVE state.

[0673] Fig.19 This is the second schematic diagram of the RNA update process provided in the embodiment of the present application, such as Fig.19 As shown:

[0674] Step 1: The UE in the inactive state sends an RRC recovery request (RRC RNA Update) message to the gNB.

[0675] Step 2: After receiving the RRC recovery request from the UE, the current gNB (the gNB currently serving the terminal, gNB in ​​the figure) determines the anchor gNB, which refers to the gNB that last served the UE when the UE entered the idle state or the inactive state. If the current serving gNB is not the same as the anchor gNB, the gNB sends a UE context forwarding request Nran_UEContextTransfer Request message to the anchor gNB to obtain the UE context. Optionally, the UE context is the entire context of the UE.

[0676] Step 3: The anchor gNB can inform the current gNB of the failure to extract the UE context by sending a UE context transfer response Nran_UEContextTransfer Response message to the current gNB. The Nran_UEContextTransfer Response message contains an encapsulated RRC suspend message.

[0677] Step 4: The current gNB sends an RRC release RRCRelease with Suspend indication message to the UE based on the received Nran_UEContextTransfer Response message.

[0678] (VI) Entering UE-IDLE state after RNA update

[0679] Fig. 20 This is the third schematic diagram of the RNA update process provided in the embodiment of the present application, such as Fig. 20 As shown:

[0680] Step 1: The UE in the inactive state sends an RRC recovery request (RRC RNA Update) message to the gNB.

[0681] Step 2: After receiving the RRC recovery request from the UE, the current gNB (the gNB currently serving the terminal, gNB in ​​the figure) determines the anchor gNB, which refers to the gNB that last served the UE when the UE entered the idle state or the inactive state. If the current serving gNB is not the same as the anchor gNB, the gNB sends a UE context forwarding request Nran_UEContextTransfer Request message to the anchor gNB to obtain the UE context. Optionally, the UE context is the entire context of the UE.

[0682] Step 3: The anchor gNB can inform the current gNB of the failure to extract the UE context by sending a UE context transfer response Nran_UEContextTransfer Response message to the current gNB. The Nran_UEContextTransfer Response message contains an encapsulated RRC release RRCRelease message.

[0683] Step 4: After the UE receives the RRCRelease message, the RRC connection between the UE and the gNB is released, and the UE enters the UE-IDLE state from the UE-ANCTIVE state.

[0684] Embodiment seven:

[0685] The network side triggers the UE-IDLE / UE-INACTIVE to UE-CONNECTED state transition

[0686] When the network side initiates MT data, if the anchor gNB finds that the UE is in UE-IDLE state or UE-INACTIVE state at this time, the anchor gNB can trigger the paging process of the RAN to enable the UE to perform the RRC establishment / recovery process.

[0687] Fig.21 This is the eighth state transition flow diagram provided in the embodiment of the present application, such as Fig.21 As shown:

[0688] Steps 1-2: When downlink data or downlink signaling reaches the anchor gNB, the anchor gNB finds that the UE is in idle or inactive state. The anchor gNB obtains the gNB information of the service area in the TA list or RNA based on the UE's location information.

[0689] Step 3: The anchor gNB broadcasts a paging message to eligible RANs.

[0690] Step 4: Paging the UE.

[0691] Step 5: The UE responds to the paging message and triggers the RRC establishment / recovery process.

[0692] Among them, the RRC establishment process can refer to (I) described in Example 5, and the RRC recovery process can refer to (I) described in Example 6.

[0693] Optionally, the anchor gNB can obtain the gNB information of the service area in the TA list or RNA through NFs such as NRF / UDM / UDR.

[0694] Embodiment 8: Method for the current gNB to obtain the anchor gNB in ​​the idle state / inactive state For the idle state:

[0695] The anchor access network device can carry an RNTI identifier in the RRCRelease message. In this case, the RNTI (also called the idle state RNTI identifier) ​​is the idle state UE identifier, which is used by the network side (access network or core network) to find the access network device (such as gNB) to which the UE is connected before entering the idle state UE-IDLE, that is, to find the anchor access network device (anchor gNB). Optionally, the idle state RNTI identifier can be used by the network side to find the UE context in the idle state UE-IDLE state. The idle state RNTI identifier is used to identify the UE context in the idle state UE-IDLE state. The idle state UE context refers to the UE context stored by the anchor access network device before the UE enters the UE-IDLE state.

[0696] For the inactive state:

[0697] The anchor access network device can carry the RNTI identifier in the RRC Release with Suspend Indication message. In this case, the RNTI (also called the inactive RNTI identifier) ​​is the inactive UE identifier, which is used by the network side (access network or core network) to find the access network device (such as gNB) to which the UE was connected before entering the inactive state UE-INACTIVE, that is, to find the anchor access network device (anchor gNB). Optionally, the inactive RNTI identifier can be used by the network side to find the UE context in the inactive UE-INACTIVE state. The inactive RNTI identifier is used to identify the UE context in the inactive UE-INACTIVE state. The UE context in the inactive UE-INACTIVE state refers to the UE context stored by the anchor access network device before the UE enters the UE-INACTIVE state.

[0698] Both the UE side and the RAN side will store RNTI (RNTI identifier in the inactive state or RNTI identifier in the idle state). The RRCSetup message initiated by the UE in the idle state and the RRCResume message initiated in the inactive state will carry RNTI (RNTI identifier in the inactive state or RNTI identifier in the idle state). The current gNB determines the anchor gNB based on the RNTI.

[0699] The paging message sent by the RAN also carries the RNTI (RNTI identifier in an inactive state or RNTI identifier in an idle state) of the UE. The UE learns that the paging object is the UE itself through the RNTI (RNTI identifier in an inactive state or RNTI identifier in an idle state).

[0700] Optionally, RNTI is divided into two different lengths, and reference may be made to related technologies.

[0701] Embodiment 9: Path switching method

[0702] Fig. 22 is a flow chart of a path switching method provided in an embodiment of the present application, such as Fig. 22 As shown:

[0703] Step 6: The current gNB provides the data forwarding address to the anchor gNB through the Nran_xx_AddrTransfer message. After receiving the message, the anchor gNB starts forwarding the buffered data to the gNB through direct or indirect forwarding.

[0704] Step 6.1: If there is an Xn interface between the current gNB (the gNB currently serving the terminal, gNB in ​​the figure) and the anchor gNB, the direct data forwarding mode is used.

[0705] Step 7: The gNB sends a message to the SMF, which carries the affected PDU session information, i.e., the PDU session information of the target PDU session.

[0706] Step 8: SMF selects UPF based on the affected PDU Session (i.e., target PDU session).

[0707] Step 9: Case 1: If the original UPF (referred to as S-UPF) can still serve the UE, execute steps 9.1 to 6.22 in the figure:

[0708] For example:

[0709] Steps 9.1-9.2: SMF sends an N4 Session Modification Request message to S-UPF to establish a forwarding path from S-UPF to gNB.

[0710] Step 9.1: SMF sends an N4 Session Modification Request message to S-UPF, sends the tunnel information of the current gNB to S-UPF, and establishes a data transmission tunnel between S-UPF and the current gNB. If the gNB and the anchor gNB are indirect forwarding tunnels, SMF will also send the forwarding path for forwarding the buffered data of the anchor gNB to S-UPF.

[0711] Step 9.2: S-UPF sends an N4 Session Modification Response message to SMF.

[0712] Step 6.21: The anchor gNB sends the buffered data to the S-UPF.

[0713] Step 6.22: S-UPF sends buffered data to the current gNB. That is, the anchor gNB indirectly forwards the buffered data to the current gNB through S-UPF (Indirect data forwarding).

[0714] Case 2: If the UE has moved out of the service area of ​​the original UPF (S-UPF) connected to the anchor point, the PSA remains unchanged, a new UPF is selected and inserted, and the new UPF can be referred to as the target UPF (Target-UPF, abbreviated as T-UPF), and steps 9.3 to 10b in the figure are executed:

[0715] For example:

[0716] Step 9.3: SMF sends an N4 Session Establish Request message to T-UPF, and SMF sends the PDU Session Anchor (PSA) and gNB tunnel information to T-UPF. A data transmission tunnel is established between T-UPF and the current gNB, and a data transmission tunnel is established between T-UPF and PSA.

[0717] Step 9.4: T-UPF sends an N4 Session Establish Response message to SMF.

[0718] Step 9.5: SMF sends an N4 Session Modification Request message to S-UPF to establish a data transmission tunnel between S-UPF and T-UPF, so that the buffered data of the anchor gNB can be forwarded to S-UPF through the anchor gNB and then to T-UPF, and finally forwarded to the current gNB through T-UPF.

[0719] Step 9.6: S-UPF sends an N4 Session Modification Response message to SMF.

[0720] Step 6.23: The anchor gNB sends the buffered data to the S-UPF, and the S-UPF sends the buffered data to the T-UPF.

[0721] Step 6.24: T-UPF sends buffered data to the current gNB. That is, the anchor gNB indirectly forwards the buffered data to the current gNB through S-UPF and T-UPF (Indirect data forwarding).

[0722] Step 9.7: SMF sends an N4 Session Modification Request message to PSA to establish a data transmission tunnel between PSA and T-UPF.

[0723] Step 9.8: Send N4 Session Modification Response message to SMF.

[0724] Step 10: SMF sends the tunnel information of T-UPF to the current gNB and establishes an uplink forwarding tunnel (data transmission tunnel) from T-UPF to gNB.

[0725] SMF releases S-UPF:

[0726] Step 10a: SMF sends an N4 Session Release Request message to S-UPF;

[0727] Step 10b: S-UPF sends an N4 Session Release Response message to SMF.

[0728] Step 11: The current gNB sends a UE context release request Nran_UEContextReleaseRequest message to the anchor gNB. The anchor gNB releases the UE context. The anchor gNB sends a UE context release response Nran_UEContextRelease Response message to the current gNB.

[0729] Embodiment 10: Migration and synchronization of Serving gNB

[0730] When the UE changes from an idle or inactive state to a connected state, if the RAN currently serving the UE changes, that is, it is different from the serving gNB when the UE enters the idle or inactive state, the core network side does not have the latest RAN information at this time. Therefore, the RAN currently serving the UE should synchronize its information to the core network.

[0731] Fig.23 is a flow chart of the RAN information synchronization method provided in an embodiment of the present application, such as Fig.23 As shown:

[0732] Step 1: After receiving the RRCSetup / Resume Complete message from the UE, the gNB registers with the core network. Optionally, it can register with network elements in the core network, such as the Unified Data Management (UDM), the Unified Data Repository (UDR) or the Network Repository Function (NRF). When the core network NF initiates downlink signaling, it can go to the corresponding network element such as UDM, UDR or NRF to query the gNB currently serving the UE.

[0733] The embodiment of the present application solves the problem of UE state management after RAN service-oriented by defining a UE state management method after RAN service-oriented. This method integrates the UE state in the access network and the core network. The UE state is managed by the RAN, and the core network no longer needs to manage the UE connection state, which simplifies the UE state, reduces the overhead of the UE and the core network in managing the UE state, and simplifies the functions and interaction processes of the UE and the core network (no need to execute the UE-triggered Service Request process, the network-triggered Service Request process, and the AN release process), and also avoids the UE state synchronization problem between the core network NFs after RAN service-oriented.

[0734] refer to Fig.24 , Fig.24 This is one of the structural diagrams of the terminal status management device provided in the embodiment of the present application. The embodiment of the present application provides a terminal status management device, including:

[0735] The first management unit 2410 is used to manage the terminal state of the terminal, where the terminal state is related to a first connection state and a second connection state, where the first connection state is the connection state between the RAN device and the terminal, and the second connection state is the connection state between the terminal and the core network CN.

[0736] Optionally, the terminal state includes a connected state, an idle state, and an inactive state; or the terminal state includes a connected state and an inactive state;

[0737] Wherein, in the connected state, the RAN device saves the terminal context of the terminal, a radio resource control RRC connection between the RAN device and the terminal has been established, a connection between the terminal and the CN has been established, and a connection between the RAN device and the CN has been established;

[0738] In the idle state, the RAN device saves the terminal context other than the access layer context of the terminal, the RRC connection between the RAN device and the terminal is disconnected, and the connection between the RAN device and the CN is maintained;

[0739] In the inactive state, the RAN device saves the terminal context of the terminal, the RRC connection between the RAN device and the terminal is suspended, and the connection between the RAN device and the CN is maintained.

[0740] Optionally, the first management unit 2410, configured to manage the terminal status of the terminal, includes:

[0741] The first management unit 2410 is configured to perform terminal state migration according to a change in a connection between the terminal and the RAN device.

[0742] Optionally, the first management unit 2410 is configured to perform terminal state migration according to a change in a connection between the terminal and the RAN device, including at least one of the following:

[0743] When the terminal state is the connected state, after the RRC connection between the RAN device and the terminal is released, the terminal state is migrated from the connected state to the idle state; or

[0744] When the terminal state is the connected state, after the RRC connection between the RAN device and the terminal is suspended, the terminal state is migrated from the connected state to the inactive state; or

[0745] When the terminal state is the idle state, after the RRC connection between the RAN device and the terminal is established, the terminal state is migrated from the idle state to the connected state; or

[0746] When the terminal state is the inactive state, after the RRC connection between the RAN device and the terminal is restored, the terminal state is migrated from the inactive state to the connected state; or

[0747] When the terminal state is the inactive state, after the RRC connection between the RAN device and the terminal is released, the terminal state is migrated from the inactive state to the idle state.

[0748] Optionally, the first management unit 2410 is further used to manage whether the terminal is reachable in different terminal states.

[0749] Optionally, the first management unit 2410 is configured to manage whether the terminal is reachable in different terminal states, including but not limited to at least one of the following:

[0750] When the terminal state is connected, the terminal is reachable; or

[0751] In the case where the terminal is in an idle state or an inactive state, determining whether the terminal is reachable according to whether the terminal applies a MICO mode in which only the terminal initiates a connection; or

[0752] When the terminal is in an idle state, starting a mobile reachable timer, and determining whether the terminal is reachable according to whether the mobile reachable timer times out; or

[0753] When the terminal is in an inactive state, a protection timer is started, and whether the terminal is reachable is determined according to whether the protection timer times out.

[0754] Optionally, the device further includes but is not limited to at least one of the following:

[0755] A first paging unit is configured to initiate a paging process for the UE according to a paging trigger condition when the terminal is in an idle state and the terminal does not apply the MICO mode; or

[0756] A periodic RRC establishment timer configuration unit, used to configure a periodic RRC establishment timer for the terminal when the terminal state is an idle state, the periodic RRC establishment timer is used to indicate a first timer value, and the first timer value is used to instruct the terminal to perform an RRC establishment process; or

[0757] The first paging unit is further configured to initiate a paging process for the UE according to a paging trigger condition when the terminal is in an inactive state and the terminal does not apply the MICO mode; or

[0758] The periodic notification area update timer configuration unit is also used to configure a periodic notification area update timer for the terminal when the terminal state is in an inactive state, and the periodic notification area update timer is used to indicate a second timer value, and the second timer value is used to instruct the terminal to execute the wireless access network notification area RNA update process.

[0759] Optionally, the mobile reachable timer is used to indicate a third timer value, the third timer value is longer than the first timer value, and when the mobile reachable timer exceeds the third timer value, a deregistration process is triggered to deregister the terminal from the CN; and / or

[0760] The protection timer is used to indicate a fourth timer value, where the fourth timer value is longer than the second timer value. When the protection timer exceeds the fourth timer value, the RRC connection with the terminal is released.

[0761] Optionally, when the terminal state is the connected state, the location information of the terminal known by the RAN device is of a first granularity;

[0762] When the terminal state is the idle state, the location information of the terminal known by the RAN device is of a second granularity;

[0763] When the terminal state is the inactive state, the location information of the terminal known by the RAN device is of the third granularity.

[0764] Optionally, the first management unit 2410, configured to manage the terminal status of the terminal, includes:

[0765] The first management unit 2410 is configured to send an RRC release message to the terminal when it is determined to migrate the terminal state from the connected state to the idle state, or to maintain the idle state, or to migrate the terminal from the inactive state to the idle state; or

[0766] The first management unit 2410 is configured to send an RRC suspend message to the terminal when it is determined that the terminal state is to be migrated from the connected state to the inactive state, or when it is determined that the inactive state is to be maintained.

[0767] Optionally, when the terminal state is the idle state, the apparatus further includes a first receiving unit, and the first receiving unit is used for at least one of the following:

[0768] receiving an RRC establishment message actively initiated by the terminal, and establishing an RRC connection with the terminal; or

[0769] receiving an RRC establishment message initiated by the terminal when the periodic RRC establishment timer times out, and establishing an RRC connection with the terminal; or

[0770] Receiving an RRC establishment message triggered by the terminal in response to a network-side paging, and establishing an RRC connection with the terminal;

[0771] When the terminal state is the inactive state, the first receiving unit is further configured to do at least one of the following:

[0772] receiving an RRC recovery message actively initiated by the terminal, and recovering the RRC connection with the terminal; or

[0773] receiving an RRC recovery message initiated by the terminal after the terminal moves out of the RNA, and recovering the RRC connection with the terminal; or

[0774] receiving an RRC recovery message initiated by the terminal when the periodic RNA update timer of the terminal times out, and recovering the RRC connection with the terminal; or

[0775] The RRC recovery message triggered by the terminal in response to the network side paging is received, and the RRC connection with the terminal is restored.

[0776] Optionally, in the case where the RRC connection is restored based on the RRC recovery message triggered by the network side paging in the inactive state in response to the terminal or the RRC establishment message triggered by the network side paging in the idle state in response to the terminal is restored, the device further includes a buffer data unit;

[0777] The buffer data unit is used to receive buffer data sent by the anchor access network device, where the buffer data is downlink data sent by the network side to the terminal in the inactive state or the idle state;

[0778] The buffer data unit is further used to send the buffer data to the terminal.

[0779] Optionally, the buffer data unit is used to receive the buffer data of the terminal, including:

[0780] The buffer data unit is used to determine the anchor access network device;

[0781] The buffer data unit is used to send a data forwarding request message to the anchor access network device when there is an Xn interface with the anchor access network device, wherein the data forwarding request message is used to request the buffer data of the terminal and receive the buffer data sent by the anchor access network device; or

[0782] The buffered data unit is used to send a protocol data unit PDU session update context request to the session management function SMF entity when there is no Xn interface with the anchor access network device. The PDU session update context request carries the PDU session information of the target PDU session. The PDU session information is used by the SMF entity to determine the user plane function UPF entity and receive the buffered data sent by the UPF entity.

[0783] Optionally, when the terminal state is transferred from an idle state or an inactive state to a connected state, the apparatus further comprises a context receiving unit;

[0784] The context receiving unit is used to determine the anchor access network device;

[0785] The context receiving unit is configured to send a request message for obtaining a terminal context to the anchor access network device when the RAN device is not the anchor access network device;

[0786] The context receiving unit is configured to receive the terminal context of the terminal sent by the anchor access network device.

[0787] Optionally, the determining of the anchor access network device includes:

[0788] The anchor access network device is determined according to the received wireless network temporary identifier of the terminal.

[0789] Optionally, when the RAN device is not the anchor access network device, the apparatus further includes an information synchronization unit;

[0790] The information synchronization unit is used to send a network element registration request message to the CN, where the network element registration request message is used to indicate information of the RAN device currently serving the terminal.

[0791] The terminal status management method applied to the access network device and the terminal status management device applied to the access network device provided in each embodiment of the present application are based on the same application concept. Since the terminal status management method and the terminal status management device solve the problem in a similar manner and can achieve the same technical effect, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated.

[0792] refer to Fig.25 , Fig.25 This is a second structural diagram of a terminal status management device provided in an embodiment of the present application. The embodiment of the present application provides a terminal status management device, which can be applied to a terminal, including:

[0793] The second management unit 2510 is used to manage the terminal state of the terminal, where the terminal state is related to a first connection state and a second connection state, where the first connection state is the connection state between the terminal and the RAN device, and the second connection state is the connection state between the terminal and the core network CN.

[0794] Optionally, the terminal state includes a connected state, an idle state, and an inactive state; or the terminal state includes a connected state and an inactive state;

[0795] Wherein, in the connected state, the RAN device saves the terminal context of the terminal, a radio resource control RRC connection between the RAN device and the terminal has been established, a connection between the terminal and the CN has been established, and a connection between the RAN device and the CN has been established;

[0796] In the idle state, the RAN device saves the terminal context other than the access layer context of the terminal, the RRC connection between the RAN device and the terminal is disconnected, and the connection between the RAN device and the CN is maintained;

[0797] In the inactive state, the RAN device saves the terminal context of the terminal, the RRC connection between the RAN device and the terminal is suspended, and the connection between the RAN device and the CN is maintained.

[0798] Optionally, the second management unit 2510, configured to manage the terminal state of the terminal, includes:

[0799] The terminal state migration is performed according to the change of the connection between the terminal and the RAN device.

[0800] Optionally, the second management unit 2510 is configured to perform terminal state migration according to a change in a connection between the terminal and the RAN device, including at least one of the following:

[0801] When the terminal state is the connected state, after the RRC connection between the RAN device and the terminal is released, the terminal is transferred from the connected state to the idle state; or

[0802] When the terminal state is the connected state, after the RRC connection between the RAN device and the terminal is suspended, the terminal state is migrated from the connected state to the inactive state; or

[0803] When the terminal state is the idle state, after the RRC connection between the RAN device and the terminal is established, the terminal state is migrated from the idle state to the connected state; or

[0804] When the terminal state is the inactive state, after the RRC connection between the RAN device and the terminal is restored, the terminal state is migrated from the inactive state to the connected state; or

[0805] When the terminal state is the inactive state, after the RRC connection between the RAN device and the terminal is released, the terminal state is migrated from the inactive state to the idle state.

[0806] Optionally, depending on the terminal status and whether the terminal applies the terminal-initiated-connection-only MICO mode, the downlink data reception situation is different.

[0807] Optionally, the downlink data reception situation is different according to the terminal state and whether the terminal applies the terminal-initiated connection-only MICO mode, including:

[0808] In the case that the terminal does not apply the terminal-initiated-only connection MICO mode, if the downlink data exists, receiving the downlink data;

[0809] When the terminal state is the connected state and the terminal applies the MICO mode, if the downlink data exists, the downlink data is received.

[0810] Optionally, the device further comprises: a second paging unit;

[0811] The second paging unit is configured to monitor a paging message when the terminal state is the idle state and the terminal does not apply the MICO mode;

[0812] The second paging unit is configured to not monitor paging messages when the terminal is in the idle state or the inactive state and the terminal applies the MICO mode.

[0813] Optionally, the device further includes but is not limited to at least one of the following:

[0814] a periodic RRC establishment timer starting unit, configured to start a periodic RRC establishment timer when the terminal enters the idle state, wherein the periodic RRC establishment timer is used to indicate a first timer value, and to perform an RRC establishment procedure based on the first timer value; or

[0815] an updating unit, configured to, when the terminal state is the inactive state, execute an RNA updating process after the terminal moves out of a radio access network notification area RNA; or

[0816] The periodic notification area update starting unit is used to start the periodic notification area update timer when the terminal enters the inactive state, and the periodic notification area update timer is used to indicate a second timer value, and execute the RNA update process based on the second timer value.

[0817] Optionally, in the case of migrating the terminal state from the connected state to the idle state, or maintaining the idle state, or migrating the terminal state from the inactive state to the idle state, the apparatus further includes:

[0818] a second receiving unit, configured to receive an RRC release message sent by the RAN device, and release the RRC connection based on the RRC release message; or

[0819] In the case of migrating the terminal state from the connected state to the inactive state, or maintaining the inactive state, the second receiving unit is further used to receive an RRC suspend message sent by the RAN device, and suspend the RRC connection based on the RRC suspend message.

[0820] Optionally, when the terminal state is the idle state, the apparatus further includes a second processing unit, and the second processing unit is used for at least one of the following:

[0821] The terminal actively initiates an RRC establishment process to establish an RRC connection with the RAN device; or

[0822] The periodic RRC establishment timer received by the terminal times out, and the terminal initiates an RRC establishment procedure to establish an RRC connection with the RAN device; or

[0823] The terminal triggers an RRC establishment process in response to a network-side paging, and establishes an RRC connection with the RAN device;

[0824] When the terminal state is the inactive state, the method further includes at least one of the following:

[0825] The terminal actively initiates an RRC recovery procedure to restore the RRC connection with the RAN device; or

[0826] After the terminal moves out of the RNA, it initiates an RRC recovery process to restore the RRC connection with the RAN device; or

[0827] The periodic RNA update timer received by the terminal times out, and the terminal initiates an RRC recovery procedure to restore the RRC connection with the RAN device; or

[0828] The terminal triggers the RRC recovery process in response to the network side paging, and recovers the RRC connection with the RAN device.

[0829] Optionally, when the terminal state is the inactive state and the RRC connection is restored in response to the network side paging, or when the terminal state is the idle state and the RRC connection is established in response to the network side paging, the device further includes a buffered data receiving unit;

[0830] The buffered data receiving unit is configured to receive buffered data sent by the RAN device, where the buffered data is downlink data sent by the network side to the terminal in the inactive state or the idle state.

[0831] The terminal status management method applied to the terminal and the terminal status management device applied to the terminal provided in each embodiment of the present application are based on the same application concept. Since the principles of solving problems by the terminal status management method and the terminal status management device are similar and can achieve the same technical effects, the implementation of the device and the method can refer to each other and the repeated parts will not be repeated.

[0832] refer to Fig.26 , Fig.26 This is a third structural diagram of a terminal status management device provided in an embodiment of the present application. An embodiment of the present application provides a terminal status management device, which can be applied to a core network CN device, including:

[0833] An interaction unit 2610 is configured to determine a registration management RM state of a terminal, and interact with the terminal through an access network RAN ​​device according to the RM state of the terminal, wherein the RM state is used to indicate whether the terminal is registered with the CN; or

[0834] Used to interact with the terminal through the RAN device after the terminal registers with the CN.

[0835] Optionally, the interacting unit 2610 is configured to interact with the terminal through an access network RAN ​​device according to the RM state of the terminal, including:

[0836] The interaction unit 2610 is configured to interact with the terminal directly through the RAN device when the registration management RM state of the terminal is registered.

[0837] Optionally, when the CN device is a session management function SMF entity, the apparatus further includes:

[0838] A third receiving unit is configured to receive a protocol data unit PDU session update context request sent by the RAN device, wherein the PDU session update context request carries PDU session information of a target PDU session;

[0839] A third determining unit is used to determine a user plane function UPF entity based on the PDU session information, where the UPF entity is used to send buffered data to the RAN device, where the buffered data is downlink data sent by the network side to the terminal in an inactive state or an idle state;

[0840] The third sending unit is used to send the tunnel information of the RAN device to the UPF entity, where the tunnel information of the RAN device is used to establish a data transmission tunnel between the UPF entity and the RAN device, and the data transmission tunnel is used to transmit the buffered data.

[0841] Optionally, the device further comprises:

[0842] An anchor RAN determination unit, used to determine an anchor RAN device;

[0843] A tunnel establishing unit is used to send tunnel information of the anchor RAN device to the UPF entity, wherein the tunnel information of the anchor RAN device is used to establish a data transmission tunnel between the UPF entity and the anchor RAN device, and the data transmission tunnel is used to transmit the buffered data.

[0844] The terminal status management method applied to the core network CN device and the terminal status management device applied to the core network CN device provided in each embodiment of the present application are based on the same application concept. Since the terminal status management method and the terminal status management device solve the problem in a similar manner and can achieve the same technical effect, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated.

[0845] It should be noted that the division of units in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional unit in each embodiment of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0846] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.

[0847] Fig. 27 is a schematic diagram of the structure of the access network RAN ​​device provided in the embodiment of the present application, such as Fig. 27 As shown, the access network RAN ​​device includes a memory 2720, a transceiver 2700, and a processor 2710, wherein:

[0848] The memory 2720 is used to store computer programs; the transceiver 2700 is used to send and receive data under the control of the processor 2710; the processor 2710 is used to read the computer program in the memory 2720 and perform the following operations:

[0849] A terminal state of a management terminal is related to a first connection state and a second connection state, wherein the first connection state is a connection state between the RAN device and the terminal, and the second connection state is a connection state between the terminal and a core network CN.

[0850] Among them, Fig. 27In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 2710 and various circuits of memory represented by memory 2720 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. Bus interface 2730 provides an interface. Transceiver 2700 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium includes a wireless channel, a wired channel, an optical cable, and other transmission media. Processor 2710 is responsible for managing the bus architecture and general processing, and memory 2720 may store data used by processor 2710 when performing operations.

[0851] Processor 2710 can be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD), and the processor can also adopt a multi-core architecture.

[0852] Optionally, the terminal state includes a connected state, an idle state, and an inactive state; or the terminal state includes a connected state and an inactive state;

[0853] Wherein, in the connected state, the RAN device saves the terminal context of the terminal, a radio resource control RRC connection between the RAN device and the terminal has been established, a connection between the terminal and the CN has been established, and a connection between the RAN device and the CN has been established;

[0854] In the idle state, the RAN device saves the terminal context other than the access layer context of the terminal, the RRC connection between the RAN device and the terminal is disconnected, and the connection between the RAN device and the CN is maintained;

[0855] In the inactive state, the RAN device saves the terminal context of the terminal, the RRC connection between the RAN device and the terminal is suspended, and the connection between the RAN device and the CN is maintained.

[0856] Optionally, the terminal status of the management terminal includes:

[0857] The terminal state migration is performed according to the change of the connection between the terminal and the RAN device.

[0858] Optionally, performing terminal state migration according to a change in a connection between the terminal and the RAN device includes at least one of the following:

[0859] When the terminal state is the connected state, after the RRC connection between the RAN device and the terminal is released, the terminal state is migrated from the connected state to the idle state; or

[0860] When the terminal state is the connected state, after the RRC connection between the RAN device and the terminal is suspended, the terminal state is migrated from the connected state to the inactive state; or

[0861] When the terminal state is the idle state, after the RRC connection between the RAN device and the terminal is established, the terminal state is migrated from the idle state to the connected state; or

[0862] When the terminal state is the inactive state, after the RRC connection between the RAN device and the terminal is restored, the terminal state is migrated from the inactive state to the connected state; or

[0863] When the terminal state is the inactive state, after the RRC connection between the RAN device and the terminal is released, the terminal state is migrated from the inactive state to the idle state.

[0864] Optionally, the operation further includes:

[0865] Manage whether the terminal is reachable in different terminal states.

[0866] Optionally, the managing whether the terminal is reachable in different terminal states includes but is not limited to at least one of the following:

[0867] When the terminal state is connected, the terminal is reachable; or

[0868] In the case where the terminal is in an idle state or an inactive state, determining whether the terminal is reachable according to whether the terminal applies a MICO mode in which only the terminal initiates a connection; or

[0869] When the terminal is in an idle state, starting a mobile reachable timer, and determining whether the terminal is reachable according to whether the mobile reachable timer times out; or

[0870] When the terminal is in an inactive state, a protection timer is started, and whether the terminal is reachable is determined according to whether the protection timer times out.

[0871] Optionally, the operation further includes but is not limited to at least one of the following:

[0872] In the case where the terminal is in an idle state and the terminal does not apply the MICO mode, initiating a paging process for the UE according to a paging trigger condition; or

[0873] When the terminal is in an idle state, configuring a periodic RRC establishment timer for the terminal, where the periodic RRC establishment timer is used to indicate a first timer value, and the first timer value is used to instruct the terminal to perform an RRC establishment procedure; or

[0874] In a case where the terminal is in an inactive state and the terminal does not apply the MICO mode, initiating a paging process for the UE according to a paging trigger condition; or

[0875] When the terminal is in an inactive state, a periodic notification area update timer is configured for the terminal, and the periodic notification area update timer is used to indicate a second timer value, and the second timer value is used to instruct the terminal to execute a wireless access network notification area RNA update process.

[0876] Optionally, the mobile reachable timer is used to indicate a third timer value, the third timer value is longer than the first timer value, and when the mobile reachable timer exceeds the third timer value, a deregistration process is triggered to deregister the terminal from the CN; and / or

[0877] The protection timer is used to indicate a fourth timer value, where the fourth timer value is longer than the second timer value. When the protection timer exceeds the fourth timer value, the RRC connection with the terminal is released.

[0878] Optionally, when the terminal state is the connected state, the location information of the terminal known by the RAN device is of a first granularity;

[0879] When the terminal state is the idle state, the location information of the terminal known by the RAN device is of a second granularity;

[0880] When the terminal state is the inactive state, the location information of the terminal known by the RAN device is of the third granularity.

[0881] Optionally, the terminal status of the management terminal includes:

[0882] In a case where it is determined to migrate the terminal state from the connected state to the idle state, or to maintain the idle state, or to migrate the terminal from the inactive state to the idle state, sending an RRC release message to the terminal; or

[0883] When it is determined that the terminal state is to be transferred from the connected state to the inactive state, or when it is determined that the inactive state is to be maintained, an RRC suspend message is sent to the terminal.

[0884] Optionally, when the terminal state is the idle state, the operation further includes at least one of the following:

[0885] receiving an RRC establishment message actively initiated by the terminal, and establishing an RRC connection with the terminal; or

[0886] receiving an RRC establishment message initiated by the terminal when the periodic RRC establishment timer times out, and establishing an RRC connection with the terminal; or

[0887] Receiving an RRC establishment message triggered by the terminal in response to a network-side paging, and establishing an RRC connection with the terminal;

[0888] When the terminal state is the inactive state, the operation further includes at least one of the following:

[0889] receiving an RRC recovery message actively initiated by the terminal, and recovering the RRC connection with the terminal; or

[0890] receiving an RRC recovery message initiated by the terminal after the terminal moves out of the RNA, and recovering the RRC connection with the terminal; or

[0891] receiving an RRC recovery message initiated by the terminal when the periodic RNA update timer of the terminal times out, and recovering the RRC connection with the terminal; or

[0892] The RRC recovery message triggered by the terminal in response to the network side paging is received, and the RRC connection with the terminal is restored.

[0893] Optionally, in a case where the RRC connection is restored based on the terminal responding to an RRC recovery message triggered by network side paging in the inactive state or the RRC connection is restored based on the terminal responding to an RRC establishment message triggered by network side paging in the idle state, the operation further includes:

[0894] receiving buffered data sent by an anchor access network device, where the buffered data is downlink data sent by a network side to the terminal in the inactive state or the idle state;

[0895] The buffered data is sent to the terminal.

[0896] Optionally, the receiving buffered data of the terminal includes:

[0897] Determine the anchor access network device;

[0898] In the case where an Xn interface exists with the anchor access network device, sending a data forwarding request message to the anchor access network device, wherein the data forwarding request message is used to request the buffered data of the terminal, and receiving the buffered data sent by the anchor access network device; or

[0899] When there is no Xn interface with the anchor access network device, a protocol data unit PDU session update context request is sent to the session management function SMF entity. The PDU session update context request carries the PDU session information of the target PDU session. The PDU session information is used by the SMF entity to determine the user plane function UPF entity and receive the buffered data sent by the UPF entity.

[0900] Optionally, when the terminal state is transferred from an idle state or an inactive state to a connected state, the operation further includes:

[0901] Determine the anchor access network device;

[0902] When the RAN device is not the anchor access network device, sending a request message for obtaining a terminal context to the anchor access network device;

[0903] Receive the terminal context of the terminal sent by the anchor access network device.

[0904] Optionally, the determining of the anchor access network device includes:

[0905] The anchor access network device is determined according to the received wireless network temporary identifier of the terminal.

[0906] Optionally, when the RAN device is not the anchor access network device, the operation further includes:

[0907] A network element registration request message is sent to the CN, where the network element registration request message is used to indicate information of a RAN device currently serving the terminal.

[0908] It should be noted here that the above-mentioned access network RAN ​​device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned terminal status management method embodiment, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0909] Fig.28 A schematic diagram of the structure of a terminal provided in an embodiment of the present application, such as Fig.28As shown, the terminal includes a memory 2820, a transceiver 2800 and a processor 2810; wherein the processor 2810 and the memory 2820 may also be arranged physically separately.

[0910] The memory 2820 is used to store a computer program; the transceiver 2800 is used to send and receive data under the control of the processor 2810; the processor 2810 calls the computer program stored in the memory 2820 to perform operations corresponding to any of the terminal status management methods applied to the terminal provided in the embodiments of the present application according to the obtained executable instructions, for example:

[0911] Manage the terminal state of the terminal, the terminal state is related to a first connection state and a second connection state, the first connection state is the connection state between the terminal and the RAN device, and the second connection state is the connection state between the terminal and the core network CN.

[0912] Among them, Fig.28 In the embodiment, the bus interface 2840 may include any number of interconnected buses and bridges, specifically connecting various circuits of one or more processors represented by the processor 2810 and the memory represented by the memory 2820. The bus interface 2840 may also connect various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 2800 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium includes wireless channels, wired channels, optical cables, and other transmission media. For different terminals, a user interface 2830 may also be included, which may also be an interface capable of externally connecting or internally connecting required devices, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.

[0913] The processor 2810 is responsible for managing the bus architecture and general processing, and the memory 2820 can store data used by the processor 2810 when performing operations.

[0914] Optionally, processor 2810 may be a CPU (central processing unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array) or a CPLD (Complex Programmable Logic Device), and the processor may also adopt a multi-core architecture.

[0915] Optionally, the terminal state includes a connected state, an idle state, and an inactive state; or the terminal state includes a connected state and an inactive state;

[0916] Wherein, in the connected state, the RAN device saves the terminal context of the terminal, a radio resource control RRC connection between the RAN device and the terminal has been established, a connection between the terminal and the CN has been established, and a connection between the RAN device and the CN has been established;

[0917] In the idle state, the RAN device saves the terminal context other than the access layer context of the terminal, the RRC connection between the RAN device and the terminal is disconnected, and the connection between the RAN device and the CN is maintained;

[0918] In the inactive state, the RAN device saves the terminal context of the terminal, the RRC connection between the RAN device and the terminal is suspended, and the connection between the RAN device and the CN is maintained.

[0919] Optionally, the managing the terminal state of the terminal includes:

[0920] The terminal state migration is performed according to the change of the connection between the terminal and the RAN device.

[0921] Optionally, performing terminal state migration according to a change in a connection between the terminal and the RAN device includes at least one of the following:

[0922] When the terminal state is the connected state, after the RRC connection between the RAN device and the terminal is released, the terminal is transferred from the connected state to the idle state; or

[0923] When the terminal state is the connected state, after the RRC connection between the RAN device and the terminal is suspended, the terminal state is migrated from the connected state to the inactive state; or

[0924] When the terminal state is the idle state, after the RRC connection between the RAN device and the terminal is established, the terminal state is migrated from the idle state to the connected state; or

[0925] When the terminal state is the inactive state, after the RRC connection between the RAN device and the terminal is restored, the terminal state is migrated from the inactive state to the connected state; or

[0926] When the terminal state is the inactive state, after the RRC connection between the RAN device and the terminal is released, the terminal state is migrated from the inactive state to the idle state.

[0927] Optionally, the operation further includes:

[0928] Depending on the terminal state and whether the terminal applies the MICO mode in which only the terminal initiates the connection, the downlink data reception situation is different.

[0929] Optionally, the downlink data reception situation is different according to the terminal state and whether the terminal applies the terminal-initiated connection-only MICO mode, including:

[0930] In the case that the terminal does not apply the terminal-initiated-only connection MICO mode, if the downlink data exists, receiving the downlink data;

[0931] When the terminal state is the connected state and the terminal applies the MICO mode, if the downlink data exists, the downlink data is received.

[0932] Optionally, the operation further includes:

[0933] When the terminal state is the idle state and the terminal does not apply the MICO mode, monitoring a paging message;

[0934] When the terminal state is the idle state or the inactive state and the terminal applies the MICO mode, the paging message is not monitored.

[0935] Optionally, the operation further includes but is not limited to at least one of the following:

[0936] When the terminal enters the idle state, starting a periodic RRC establishment timer, the periodic RRC establishment timer is used to indicate a first timer value, and performing an RRC establishment process based on the first timer value; or

[0937] When the terminal state is the inactive state, after the terminal moves out of the radio access network notification area RNA, an RNA update process is executed; or

[0938] When the terminal enters the inactive state, a periodic notification area update timer is started, the periodic notification area update timer is used to indicate a second timer value, and an RNA update process is performed based on the second timer value.

[0939] Optionally, in the case of migrating the terminal state from the connected state to the idle state, or maintaining the idle state, or migrating the terminal state from the inactive state to the idle state, the operation further includes: receiving an RRC release message sent by the RAN device, and releasing the RRC connection based on the RRC release message; or

[0940] In the case of migrating the terminal state from the connected state to the inactive state, or maintaining the inactive state, the operation further includes: receiving an RRC suspend message sent by the RAN device, and suspending the RRC connection based on the RRC suspend message.

[0941] Optionally, when the terminal state is the idle state, the operation further includes at least one of the following:

[0942] The terminal actively initiates an RRC establishment process to establish an RRC connection with the RAN device; or

[0943] The periodic RRC establishment timer received by the terminal times out, and the terminal initiates an RRC establishment procedure to establish an RRC connection with the RAN device; or

[0944] The terminal triggers an RRC establishment process in response to a network-side paging, and establishes an RRC connection with the RAN device;

[0945] When the terminal state is the inactive state, the operation further includes at least one of the following:

[0946] The terminal actively initiates an RRC recovery procedure to restore the RRC connection with the RAN device; or

[0947] After the terminal moves out of the RNA, it initiates an RRC recovery process to restore the RRC connection with the RAN device; or

[0948] The periodic RNA update timer received by the terminal times out, and the terminal initiates an RRC recovery procedure to restore the RRC connection with the RAN device; or

[0949] The terminal triggers the RRC recovery process in response to the network side paging, and recovers the RRC connection with the RAN device.

[0950] Optionally, when the terminal state is the inactive state and the RRC connection is restored in response to network side paging, or when the terminal state is the idle state and the RRC connection is established in response to network side paging, the operation further includes:

[0951] Receive buffered data sent by the RAN device, where the buffered data is downlink data sent by a network side to the terminal in the inactive state or the idle state.

[0952] Fig.29 is a schematic diagram of the structure of the core network CN device provided in the embodiment of the present application, such as Fig.29 As shown, the core network CN device includes a memory 2920, a transceiver 2900, and a processor 2910, wherein:

[0953] The memory 2920 is used to store computer programs; the transceiver 2900 is used to send and receive data under the control of the processor 2910; the processor 2910 is used to read the computer program in the memory 2920 and perform the following operations:

[0954] Determine a registration management RM state of the terminal, and interact with the terminal through an access network RAN ​​device according to the RM state of the terminal, wherein the RM state is used to indicate whether the terminal is registered with the CN; or

[0955] After the terminal registers with the CN, the RAN device interacts with the terminal.

[0956] Among them, Fig.29 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 2910 and various circuits of memory represented by memory 2920 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface 2930 provides an interface. The transceiver 2900 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium includes a wireless channel, a wired channel, an optical cable, and other transmission media. The processor 2910 is responsible for managing the bus architecture and general processing, and the memory 2920 may store data used by the processor 2910 when performing operations.

[0957] Processor 2910 can be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD), and the processor can also adopt a multi-core architecture.

[0958] Optionally, the interacting with the terminal through an access network RAN ​​device according to the RM state of the terminal includes:

[0959] When the registration management RM state of the terminal is registered, the RAN device directly interacts with the terminal.

[0960] Optionally, when the CN device is a session management function SMF entity, the operation further includes:

[0961] receiving a protocol data unit (PDU) session update context request sent by the RAN device, wherein the PDU session update context request carries PDU session information of a target PDU session;

[0962] Determine a user plane function UPF entity based on the PDU session information, the UPF entity being used to send buffered data to the RAN device, the buffered data being downlink data sent by the network side to the terminal in an inactive state or an idle state;

[0963] The tunnel information of the RAN device is sent to the UPF entity, where the tunnel information of the RAN device is used to establish a data transmission tunnel between the UPF entity and the RAN device, and the data transmission tunnel is used to transmit the buffered data.

[0964] Optionally, the operation further includes:

[0965] Determine the anchor RAN device;

[0966] The tunnel information of the anchor RAN device is sent to the UPF entity, where the tunnel information of the anchor RAN device is used to establish a data transmission tunnel between the UPF entity and the anchor RAN device, where the data transmission tunnel is used to transmit the buffered data.

[0967] It should be noted that the above-mentioned core network CN device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned terminal status management method embodiment, and can achieve the same technical effect. The parts and beneficial effects that are the same as the method embodiment in this embodiment will not be described in detail here.

[0968] On the other hand, an embodiment of the present application further provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the method provided by each embodiment of the above-mentioned application to the access network RAN ​​device, including:

[0969] A terminal state of a management terminal is related to a first connection state and a second connection state, wherein the first connection state is a connection state between the RAN device and the terminal, and the second connection state is a connection state between the terminal and a core network CN.

[0970] On the other hand, an embodiment of the present application further provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the method provided by each embodiment of the above-mentioned application to the terminal, including:

[0971] Manage the terminal state of the terminal, the terminal state is related to a first connection state and a second connection state, the first connection state is the connection state between the terminal and the RAN device, and the second connection state is the connection state between the terminal and the core network CN.

[0972] On the other hand, an embodiment of the present application further provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the method provided by each embodiment of the above-mentioned application to the core network CN device, including:

[0973] Determine a registration management RM state of the terminal, and interact with the terminal through an access network RAN ​​device according to the RM state of the terminal, wherein the RM state is used to indicate whether the terminal is registered with the CN; or

[0974] After the terminal registers with the CN, the RAN device interacts with the terminal.

[0975] The processor-readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (such as CD, DVD, BD, HVD, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NANDFLASH), solid-state drive (SSD)), etc.

[0976] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) that contain computer-usable program code.

[0977] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer executable instructions. These computer executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0978] These processor executable instructions may also be stored in a processor readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0979] These processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0980] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A method for managing terminal status, characterized in that: Applied to access network RAN ​​equipment, including: A terminal state of a management terminal is related to a first connection state and a second connection state, wherein the first connection state is a connection state between the RAN device and the terminal, and the second connection state is a connection state between the terminal and a core network CN.

2. The terminal status management method according to claim 1, characterized in that: The terminal state includes a connected state, an idle state and an inactive state; or the terminal state includes a connected state and an inactive state; Wherein, in the connected state, the RAN device saves the terminal context of the terminal, a radio resource control RRC connection between the RAN device and the terminal has been established, a connection between the terminal and the CN has been established, and a connection between the RAN device and the CN has been established; In the idle state, the RAN device saves the terminal context other than the access layer context of the terminal, the RRC connection between the RAN device and the terminal is disconnected, and the connection between the RAN device and the CN is maintained; In the inactive state, the RAN device saves the terminal context of the terminal, the RRC connection between the RAN device and the terminal is suspended, and the connection between the RAN device and the CN is maintained.

3. The terminal status management method according to claim 2, characterized in that: The terminal status of the management terminal includes: The terminal state migration is performed according to the change of the connection between the terminal and the RAN device.

4. The terminal status management method according to claim 3, characterized in that: The performing terminal state migration according to the change of the connection between the terminal and the RAN device includes at least one of the following: When the terminal state is the connected state, after the RRC connection between the RAN device and the terminal is released, the terminal state is migrated from the connected state to the idle state; or When the terminal state is the connected state, after the RRC connection between the RAN device and the terminal is suspended, the terminal state is migrated from the connected state to the inactive state; or When the terminal state is the idle state, after the RRC connection between the RAN device and the terminal is established, the terminal state is migrated from the idle state to the connected state; or When the terminal state is the inactive state, after the RRC connection between the RAN device and the terminal is restored, the terminal state is migrated from the inactive state to the connected state; or When the terminal state is the inactive state, after the RRC connection between the RAN device and the terminal is released, the terminal state is migrated from the inactive state to the idle state.

5. The terminal status management method according to claim 2, characterized in that: The method further comprises: Manage whether the terminal is reachable in different terminal states.

6. The terminal status management method according to claim 5, characterized in that: The managing whether the terminal is reachable in different terminal states includes but is not limited to at least one of the following: When the terminal state is a connected state, the terminal is reachable; or When the terminal is in an idle state or an inactive state, determining whether the terminal is reachable according to whether the terminal applies a MICO mode in which only the terminal initiates a connection; or When the terminal is in an idle state, starting a mobile reachable timer, and determining whether the terminal is reachable according to whether the mobile reachable timer times out; or When the terminal is in an inactive state, a protection timer is started, and whether the terminal is reachable is determined according to whether the protection timer times out.

7. The terminal status management method according to claim 6, characterized in that: The method also includes but is not limited to at least one of the following: In the case where the terminal is in an idle state and the terminal does not apply the MICO mode, initiating a paging process for the UE according to a paging trigger condition; or When the terminal state is an idle state, configuring a periodic RRC establishment timer for the terminal, where the periodic RRC establishment timer is used to indicate a first timer value, and the first timer value is used to instruct the terminal to perform an RRC establishment procedure; or Initiate a paging process for the UE according to a paging trigger condition when the terminal is in an inactive state and the terminal does not apply the MICO mode; or When the terminal is in an inactive state, a periodic notification area update timer is configured for the terminal, and the periodic notification area update timer is used to indicate a second timer value, and the second timer value is used to instruct the terminal to execute a wireless access network notification area RNA update process.

8. The terminal status management method according to claim 7, characterized in that: The mobile reachable timer is used to indicate a third timer value, the third timer value is longer than the first timer value, and when the mobile reachable timer exceeds the third timer value, a deregistration process is triggered to deregister the terminal from the CN; and / or The protection timer is used to indicate a fourth timer value, where the fourth timer value is longer than the second timer value. When the protection timer exceeds the fourth timer value, the RRC connection with the terminal is released.

9. The terminal status management method according to any one of claims 5 to 7, characterized in that: When the terminal state is the connected state, the location information of the terminal known by the RAN device is of a first granularity; When the terminal state is the idle state, the location information of the terminal known by the RAN device is of a second granularity; When the terminal state is the inactive state, the location information of the terminal known by the RAN device is of the third granularity.

10. The terminal status management method according to any one of claims 2 to 8, characterized in that: The terminal status of the management terminal includes: In a case where it is determined to migrate the terminal state from the connected state to the idle state, or to maintain the idle state, or to migrate the terminal from the inactive state to the idle state, sending an RRC release message to the terminal; or When it is determined that the terminal state is to be transferred from the connected state to the inactive state, or when it is determined that the inactive state is to be maintained, an RRC suspend message is sent to the terminal.

11. The terminal status management method according to claim 7, characterized in that: When the terminal state is the idle state, the method further includes at least one of the following: receiving an RRC establishment message actively initiated by the terminal, and establishing an RRC connection with the terminal; or receiving an RRC establishment message initiated by the terminal when the periodic RRC establishment timer times out, and establishing an RRC connection with the terminal; or Receiving an RRC establishment message triggered by the terminal in response to a network-side paging, and establishing an RRC connection with the terminal; When the terminal state is the inactive state, the method further includes at least one of the following: receiving an RRC recovery message actively initiated by the terminal, and recovering the RRC connection with the terminal; or receiving an RRC recovery message initiated by the terminal after the terminal moves out of the RNA, and recovering the RRC connection with the terminal; or receiving an RRC recovery message initiated by the terminal when the periodic RNA update timer of the terminal times out, and recovering the RRC connection with the terminal; or The RRC recovery message triggered by the terminal in response to the network side paging is received, and the RRC connection with the terminal is restored.

12. The terminal status management method according to claim 11, characterized in that: In the case where the RRC connection is restored based on the RRC recovery message triggered by the terminal responding to the network side paging in the inactive state or the RRC establishment message triggered by the terminal responding to the network side paging in the idle state is restored, the method further includes: receiving buffered data sent by an anchor access network device, where the buffered data is downlink data sent by a network side to the terminal in the inactive state or the idle state; The buffered data is sent to the terminal.

13. The terminal status management method according to claim 12, characterized in that: The receiving buffered data of the terminal includes: Determining the anchor access network device; In the case where an Xn interface exists with the anchor access network device, sending a data forwarding request message to the anchor access network device, wherein the data forwarding request message is used to request the buffered data of the terminal, and receiving the buffered data sent by the anchor access network device; or When there is no Xn interface with the anchor access network device, a protocol data unit PDU session update context request is sent to the session management function SMF entity. The PDU session update context request carries the PDU session information of the target PDU session. The PDU session information is used by the SMF entity to determine the user plane function UPF entity and receive the buffered data sent by the UPF entity.

14. The terminal status management method according to claim 3, characterized in that: In the case where the terminal state is transferred from an idle state or an inactive state to a connected state, the method further includes: Determine the anchor access network device; When the RAN device is not the anchor access network device, sending a request message for obtaining a terminal context to the anchor access network device; Receive the terminal context of the terminal sent by the anchor access network device.

15. The terminal status management method according to claim 13 or 14, characterized in that: The device for determining the anchor access network includes: The anchor access network device is determined according to the received wireless network temporary identifier of the terminal.

16. The terminal status management method according to claim 14, characterized in that: In a case where the RAN device is not the anchor access network device, the method further includes: A network element registration request message is sent to the CN, where the network element registration request message is used to indicate information of a RAN device currently serving the terminal.

17. A method for managing terminal status, characterized in that: Applied to terminals, including: Manage the terminal state of the terminal, the terminal state is related to a first connection state and a second connection state, the first connection state is the connection state between the terminal and the RAN device, and the second connection state is the connection state between the terminal and the core network CN.

18. The terminal status management method according to claim 17, characterized in that: The terminal state includes a connected state, an idle state and an inactive state; or the terminal state includes a connected state and an inactive state; Wherein, in the connected state, the RAN device saves the terminal context of the terminal, a radio resource control RRC connection between the RAN device and the terminal has been established, a connection between the terminal and the CN has been established, and a connection between the RAN device and the CN has been established; In the idle state, the RAN device saves the terminal context other than the access layer context of the terminal, the RRC connection between the RAN device and the terminal is disconnected, and the connection between the RAN device and the CN is maintained; In the inactive state, the RAN device saves the terminal context of the terminal, the RRC connection between the RAN device and the terminal is suspended, and the connection between the RAN device and the CN is maintained.

19. The terminal status management method according to claim 18, characterized in that: The managing the terminal status of the terminal includes: The terminal state migration is performed according to the change of the connection between the terminal and the RAN device.

20. The terminal status management method according to claim 19, characterized in that: The performing terminal state migration according to the change of the connection between the terminal and the RAN device includes at least one of the following: When the terminal state is the connected state, after the RRC connection between the RAN device and the terminal is released, the terminal is migrated from the connected state to the idle state; or When the terminal state is the connected state, after the RRC connection between the RAN device and the terminal is suspended, the terminal state is migrated from the connected state to the inactive state; or When the terminal state is the idle state, after the RRC connection between the RAN device and the terminal is established, the terminal state is migrated from the idle state to the connected state; or When the terminal state is the inactive state, after the RRC connection between the RAN device and the terminal is restored, the terminal state is migrated from the inactive state to the connected state; or When the terminal state is the inactive state, after the RRC connection between the RAN device and the terminal is released, the terminal state is migrated from the inactive state to the idle state.

21. The terminal status management method according to any one of claims 18 to 20, characterized in that: The method further comprises: Depending on the terminal state and whether the terminal applies the MICO mode in which only the terminal initiates the connection, the downlink data reception situation is different.

22. The terminal status management method according to claim 21, characterized in that: The downlink data receiving conditions are different according to the terminal state and whether the terminal applies the terminal-initiated connection-only MICO mode, including: In the case that the terminal does not apply the terminal-initiated-only connection MICO mode, if the downlink data exists, receiving the downlink data; When the terminal state is the connected state and the terminal applies the MICO mode, if the downlink data exists, the downlink data is received.

23. The terminal status management method according to any one of claims 18 to 20, characterized in that: The method further comprises: When the terminal state is the idle state and the terminal does not apply the MICO mode, monitoring a paging message; When the terminal state is the idle state or the inactive state and the terminal applies the MICO mode, the paging message is not monitored.

24. The terminal status management method according to any one of claims 18 to 20, characterized in that: The method also includes but is not limited to at least one of the following: When the terminal enters the idle state, starting a periodic RRC establishment timer, the periodic RRC establishment timer is used to indicate a first timer value, and performing an RRC establishment process based on the first timer value; or When the terminal state is the inactive state, after the terminal moves out of the radio access network notification area RNA, an RNA update process is executed; or When the terminal enters the inactive state, a periodic notification area update timer is started, the periodic notification area update timer is used to indicate a second timer value, and an RNA update process is executed based on the second timer value.

25. The terminal status management method according to claim 20, characterized in that: In the case of migrating the terminal state from the connected state to the idle state, or maintaining the idle state, or migrating the terminal state from the inactive state to the idle state, the method further includes: receiving an RRC release message sent by the RAN device, and releasing the RRC connection based on the RRC release message; or In the case of migrating the terminal state from the connected state to the inactive state, or maintaining the inactive state, the method further includes: receiving an RRC suspend message sent by the RAN device, and suspending the RRC connection based on the RRC suspend message.

26. The terminal status management method according to claim 24, characterized in that: When the terminal state is the idle state, the method further includes at least one of the following: The terminal actively initiates an RRC establishment process to establish an RRC connection with the RAN device; or The periodic RRC establishment timer received by the terminal times out, and the terminal initiates an RRC establishment procedure to establish an RRC connection with the RAN device; or The terminal triggers an RRC establishment process in response to a network-side paging, and establishes an RRC connection with the RAN device; When the terminal state is the inactive state, the method further includes at least one of the following: The terminal actively initiates an RRC recovery procedure to restore the RRC connection with the RAN device; or After the terminal moves out of the RNA, it initiates an RRC recovery process to restore the RRC connection with the RAN device; or The periodic RNA update timer received by the terminal times out, and the terminal initiates an RRC recovery procedure to restore the RRC connection with the RAN device; or The terminal triggers the RRC recovery process in response to the network side paging, and recovers the RRC connection with the RAN device.

27. The terminal status management method according to claim 26, characterized in that: When the terminal state is the inactive state and the RRC connection is restored in response to the network side paging, or when the terminal state is the idle state and the RRC connection is established in response to the network side paging, the method further includes: Receive buffered data sent by the RAN device, where the buffered data is downlink data sent by a network side to the terminal in the inactive state or the idle state.

28. A method for managing terminal status, characterized in that: Applied to core network CN equipment, including: Determine a registration management RM state of the terminal, and interact with the terminal through an access network RAN ​​device according to the RM state of the terminal, wherein the RM state is used to indicate whether the terminal is registered with the CN; or After the terminal registers with the CN, the RAN device interacts with the terminal.

29. The terminal status management method according to claim 28, characterized in that: The interacting with the terminal through an access network RAN ​​device according to the RM state of the terminal includes: When the registration management RM state of the terminal is registered, the RAN device directly interacts with the terminal.

30. The terminal status management method according to claim 28 or 29, characterized in that: In the case where the CN device is a session management function SMF entity, the method further includes: receiving a protocol data unit (PDU) session update context request sent by the RAN device, wherein the PDU session update context request carries PDU session information of a target PDU session; Determine a user plane function UPF entity based on the PDU session information, the UPF entity being used to send buffered data to the RAN device, the buffered data being downlink data sent by the network side to the terminal in an inactive state or an idle state; The tunnel information of the RAN device is sent to the UPF entity, where the tunnel information of the RAN device is used to establish a data transmission tunnel between the UPF entity and the RAN device, and the data transmission tunnel is used to transmit the buffered data.

31. The terminal status management method according to claim 30, characterized in that: The method further comprises: Determine the anchor RAN equipment; The tunnel information of the anchor RAN device is sent to the UPF entity, where the tunnel information of the anchor RAN device is used to establish a data transmission tunnel between the UPF entity and the anchor RAN device, where the data transmission tunnel is used to transmit the buffered data.

32. An access network RAN ​​device, characterized in that: Includes memory, transceiver and processor: The memory is used to store a computer program; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations: A terminal state of a management terminal is related to a first connection state and a second connection state, wherein the first connection state is a connection state between the RAN device and the terminal, and the second connection state is a connection state between the terminal and a core network CN.

33. A terminal, characterized in that: Includes memory, transceiver and processor: The memory is used to store a computer program; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations: Manage the terminal state of the terminal, the terminal state is related to a first connection state and a second connection state, the first connection state is the connection state between the terminal and the RAN device, and the second connection state is the connection state between the terminal and the core network CN.

34. A core network CN device, characterized in that: Includes memory, transceiver and processor: The memory is used to store a computer program; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations: Determine a registration management RM state of the terminal, and interact with the terminal through an access network RAN ​​device according to the RM state of the terminal, wherein the RM state is used to indicate whether the terminal is registered with the CN; or After the terminal registers with the CN, the RAN device interacts with the terminal.

35. A terminal status management device, characterized in that: Applied to access network RAN ​​equipment, including: The first management unit is used to manage the terminal state of the terminal, where the terminal state is related to a first connection state and a second connection state, where the first connection state is the connection state between the RAN device and the terminal, and the second connection state is the connection state between the terminal and the core network CN.

36. A terminal status management device, characterized in that: Applied to terminals, including: The second management unit is used to manage the terminal state of the terminal, where the terminal state is related to a first connection state and a second connection state, where the first connection state is the connection state between the terminal and the RAN device, and the second connection state is the connection state between the terminal and the core network CN.

37. A terminal status management device, characterized in that: Applied to core network CN equipment, including: an interaction unit, configured to determine a registration management RM state of a terminal, and interact with the terminal through an access network RAN ​​device according to the RM state of the terminal, wherein the RM state is used to indicate whether the terminal is registered with the CN; or Used to interact with the terminal through the RAN device after the terminal registers with the CN.

38. A processor-readable storage medium, characterized in that: The processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the terminal status management method according to any one of claims 1 to 16.

39. A processor-readable storage medium, characterized in that: The processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the terminal status management method according to any one of claims 17 to 27.

40. A processor-readable storage medium, characterized in that: The processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the terminal status management method according to any one of claims 28 to 31.

Images