[go: up one dir, main page]

WO2024250885A1 - Procédé et appareil de gestion d'état de terminal - Google Patents

Procédé et appareil de gestion d'état de terminal Download PDF

Info

Publication number
WO2024250885A1
WO2024250885A1 PCT/CN2024/090934 CN2024090934W WO2024250885A1 WO 2024250885 A1 WO2024250885 A1 WO 2024250885A1 CN 2024090934 W CN2024090934 W CN 2024090934W WO 2024250885 A1 WO2024250885 A1 WO 2024250885A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
state
ran device
rrc
connection
Prior art date
Application number
PCT/CN2024/090934
Other languages
English (en)
Chinese (zh)
Inventor
曹彩红
熊春山
徐晖
王可
Original Assignee
大唐移动通信设备有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 大唐移动通信设备有限公司 filed Critical 大唐移动通信设备有限公司
Publication of WO2024250885A1 publication Critical patent/WO2024250885A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02—Arrangements for increasing efficiency of notification or paging channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/34—Selective release of ongoing connections

Definitions

  • the present disclosure relates to the field of communication technology, and in particular to a method and device for managing terminal status.
  • the status of the user equipment (UE) is managed by the access and mobility management function (AMF).
  • AMF access and mobility management function
  • Radio Access Network (RAN) is service-oriented
  • no solution has been proposed for the UE status management method after the RAN is service-oriented.
  • the embodiments of the present disclosure 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 related art.
  • an embodiment of the present disclosure provides a method for managing a terminal state, which is applied to an access network RAN device, 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.
  • 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;
  • 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;
  • the terminal status of the management terminal includes:
  • the terminal state is the inactive state
  • the terminal state is migrated from the inactive state to the idle state.
  • the method further comprises:
  • the managing whether the terminal is reachable in different terminal states includes but is not limited to at least one of the following:
  • a protection timer is started, and whether the terminal is reachable is determined according to whether the protection timer times out.
  • the method further includes but is not limited to at least one of the following:
  • the location information of the terminal known by the RAN device is of a first granularity
  • the location information of the terminal known by the RAN device is of a second granularity
  • the terminal state is the inactive state
  • the terminal known to the RAN device The location information of the end is of the third granularity.
  • the terminal status of the management terminal includes:
  • an RRC suspend message is sent to the terminal.
  • the method further includes at least one of the following:
  • the method further includes at least one of the following:
  • 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.
  • the method further includes:
  • the buffered data is sent to the terminal.
  • the receiving buffered data sent by the anchor access network device includes:
  • 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.
  • the method further includes:
  • the RAN device When the registration management RM state of the terminal is registered, the RAN device directly interacts with the terminal.
  • an embodiment of the present disclosure further provides an access network RAN device, including a memory, a transceiver, and a processor, wherein:
  • 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;
  • 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;
  • 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.
  • 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.
  • 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:
  • 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
  • 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
  • the terminal state is the idle state
  • the terminal state is migrated from the idle state to the connected state
  • 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;
  • the terminal state is the inactive state
  • the terminal state is migrated from the inactive state to the idle state.
  • the processor is further configured to read a computer program in the memory and perform the following operations:
  • the managing whether the terminal is reachable in different terminal states includes but is not limited to at least one of the following:
  • a protection timer is started, and whether the terminal is reachable is determined according to whether the protection timer times out.
  • the processor is further configured to perform but not limited to at least one of the following operations:
  • 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.
  • 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.
  • the RAN device when the terminal state is the connected state, the RAN device knows The location information of the terminal is of a first granularity
  • the location information of the terminal known by the RAN device is of a second granularity
  • the location information of the terminal known by the RAN device is of the third granularity.
  • the terminal status of the management terminal includes:
  • an RRC suspend message is sent to the terminal.
  • the processor when the terminal state is the idle state, the processor is further configured to perform at least one of the following operations:
  • the processor is further configured to perform at least one of the following operations:
  • the determining of the anchor access network device includes:
  • the anchor access network device is determined according to the received wireless network temporary identifier of the terminal.
  • the processor is further configured to perform the following operations:
  • the network element registration request message is used to indicate the current Information of the RAN device currently serving the terminal.
  • an embodiment of the present disclosure further provides a terminal, including a memory, a transceiver, and a processor, wherein:
  • 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.
  • 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;
  • 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;
  • 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;
  • 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.
  • the managing the terminal state of the terminal includes:
  • the terminal state migration is performed according to the change of the connection between the terminal and the RAN device.
  • 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:
  • the terminal state is the connected state
  • the terminal is transferred from the connected state to the idle state
  • 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
  • the terminal state is the idle state
  • the terminal state is migrated from the idle state to the connected state
  • 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;
  • the terminal state is the inactive state
  • the terminal state is migrated from the inactive state to the idle state.
  • the processor is further configured to perform the following operations:
  • the downlink data reception situation is different.
  • 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:
  • the terminal does not apply the terminal-initiated-only connection MICO mode, if the downlink data exists, receiving the downlink data;
  • the terminal state is the connected state and the terminal applies the MICO mode, if the downlink data exists, the downlink data is received.
  • the processor is further configured to perform the following operations:
  • the terminal state is the idle state or the inactive state and the terminal applies the MICO mode, the paging message is not monitored.
  • the processor is further configured to perform but not limited to at least one of the following operations:
  • 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;
  • 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.
  • the processor is further used to perform the following operations: receiving an RRC release message sent by the RAN device, and releasing the RRC connection based on the RRC release message; or
  • the processor 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.
  • the processor when the terminal state is the idle state, the processor is further configured to perform at least one of the following operations:
  • the terminal actively initiates an RRC establishment process to establish an RRC connection with the RAN device;
  • the terminal triggers an RRC establishment process in response to a network-side paging, and establishes an RRC connection with the RAN device;
  • the processor is further configured to do at least one of the following:
  • the terminal actively initiates an RRC recovery procedure to restore the RRC connection with the RAN device;
  • 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;
  • the terminal triggers the RRC recovery process in response to the network side paging, and recovers the RRC connection with the RAN device.
  • an embodiment of the present disclosure further provides a core network CN device, including a memory, a transceiver, and a processor, wherein:
  • 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.
  • the processor is specifically configured to perform the following operations:
  • the RAN device When the registration management RM state of the terminal is registered, the RAN device directly interacts with the terminal.
  • the processor is further configured to perform the following operations:
  • PDU session update context request carries PDU session information of a target PDU session
  • UPF entity 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.
  • the processor is further configured to perform the following operations:
  • 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.
  • an embodiment of the present disclosure further provides a terminal status management device, which is applied to an access network RAN device, including:
  • the first management unit is used to manage the terminal state of the terminal, the terminal state is related to the first connection state
  • the first connection state is related to the second connection state
  • the first connection state is the connection state between the RAN device and the terminal
  • the second connection state is the connection state between the terminal and the core network CN.
  • 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;
  • 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;
  • 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;
  • 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.
  • the first management unit is specifically configured to:
  • the terminal state migration is performed according to the change of the connection between the terminal and the RAN device.
  • 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:
  • 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
  • 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
  • the terminal state is the idle state
  • the terminal state is migrated from the idle state to the connected state
  • 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;
  • the terminal state is migrated from the inactive state to the idle state.
  • the first management unit is further used for:
  • the first management unit is further specifically used for at least one of the following:
  • a protection timer is started, and whether the terminal is reachable is determined according to whether the protection timer times out.
  • the first management unit is further used for at least one of the following:
  • 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.
  • 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.
  • the location information of the terminal known by the RAN device is of a first granularity
  • the location information of the terminal known by the RAN device is of a second granularity
  • the location information of the terminal known by the RAN device is of the third granularity.
  • the first management unit is further specifically configured to:
  • an RRC suspend message is sent to the terminal.
  • the first management unit is further configured to perform at least one of the following:
  • the first management unit is further configured to do at least one of the following:
  • 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.
  • the first management unit is further used to:
  • the buffered data is sent to the terminal.
  • the first management unit is further used for:
  • 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.
  • the first management unit is further configured to:
  • the first management unit is further specifically configured to:
  • the anchor access network device is determined according to the received wireless network temporary identifier of the terminal.
  • the first management unit is further configured to:
  • the network element registration request message is used to indicate the current Information of the RAN device currently serving the terminal.
  • an embodiment of the present disclosure further provides a terminal status management device, which is applied to a terminal, 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.
  • 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;
  • 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;
  • 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;
  • 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.
  • the second management unit is specifically configured to:
  • the terminal state migration is performed according to the change of the connection between the terminal and the RAN device.
  • 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:
  • the terminal state is the connected state
  • the terminal is transferred from the connected state to the idle state
  • 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
  • the terminal state is the idle state
  • the terminal state is migrated from the idle state to the connected state
  • 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;
  • the terminal state is the inactive state
  • the terminal state is migrated from the inactive state to the idle state.
  • the second management unit is further used for:
  • the downlink data reception situation is different.
  • the second management unit is further specifically configured to:
  • the terminal does not apply the terminal-initiated-only connection MICO mode, if the downlink data exists, receiving the downlink data;
  • the terminal state is the connected state and the terminal applies the MICO mode, if the downlink data exists, the downlink data is received.
  • the second management unit is further used for:
  • the terminal state is the idle state or the inactive state and the terminal applies the MICO mode, the paging message is not monitored.
  • the second management unit is further used for at least one of the following:
  • 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;
  • 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.
  • the second management unit is further used to: receive an RRC release message sent by the RAN device, and release the RRC connection based on the RRC release message; or
  • the second management 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.
  • the second management unit is further configured to perform at least one of the following:
  • the terminal actively initiates an RRC establishment process to establish an RRC connection with the RAN device;
  • 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;
  • the terminal triggers an RRC establishment process in response to a network-side paging, and establishes an RRC connection with the RAN device;
  • the second management unit is further configured to do at least one of the following:
  • the terminal actively initiates an RRC recovery procedure to restore the RRC connection with the RAN device;
  • the terminal 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;
  • the terminal triggers the RRC recovery process in response to the network side paging, and recovers the RRC connection with the RAN device.
  • the second management unit is further used to:
  • Receive buffered data sent by the RAN device the buffered data being the network side in the Downlink data sent by the terminal in the inactive state or the idle state.
  • an embodiment of the present disclosure further provides a terminal status management device, which is applied to a core network CN device, 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;
  • the interaction unit is specifically used for:
  • the RAN device When the registration management RM state of the terminal is registered, the RAN device directly interacts with the terminal.
  • the interaction unit is further configured to:
  • PDU session update context request carries PDU session information of a target PDU session
  • UPF entity 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.
  • the interaction unit is further used for:
  • 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.
  • an embodiment of the present disclosure further provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, wherein the computer program is used to cause the processor to execute the following The terminal status management method described in the first aspect above.
  • an embodiment of the present disclosure 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.
  • an embodiment of the present disclosure 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 as described above.
  • the terminal status management method and device provided in the embodiments of the present disclosure can be applied to the RAN service-oriented scenario.
  • 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.
  • the terminal status is managed by the access network device, and the core network no longer manages the connection status of the UE. It is considered that the UE is always connected.
  • 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
  • the second connection status is the connection status between the terminal and the core network CN, which simplifies the terminal status.
  • FIG1 is a schematic diagram of an N2 interface in the related art provided by the present disclosure.
  • FIG2 is one of the schematic diagrams of the RAN service-oriented architecture provided by the present disclosure.
  • FIG3 is a second schematic diagram of the RAN service-oriented architecture provided by the present disclosure.
  • FIG4 is a flow chart of a method for managing terminal status according to an embodiment of the present disclosure.
  • FIG5 is one of the schematic diagrams of terminal state migration in the RAN provided by an embodiment of the present disclosure.
  • FIG6 is a second schematic diagram of terminal state migration in a RAN provided by an embodiment of the present disclosure.
  • FIG7 is a second flow chart of a method for managing terminal status provided in an embodiment of the present disclosure.
  • FIG8 is one of the schematic diagrams of terminal state migration in a UE provided in an embodiment of the present disclosure.
  • FIG9 is a second schematic diagram of terminal state migration in a UE provided in an embodiment of the present disclosure.
  • FIG10 is a third flow chart of a method for managing terminal status according to an embodiment of the present disclosure.
  • FIG11 is one of the state transition flow diagrams provided in an embodiment of the present disclosure.
  • FIG12 is a second schematic diagram of a state transition process provided by an embodiment of the present disclosure.
  • FIG13 is a third schematic diagram of a state transition process provided by an embodiment of the present disclosure.
  • FIG14 is a fourth schematic diagram of a state transition process provided by an embodiment of the present disclosure.
  • FIG15 is a fifth schematic diagram of a state transition process provided by an embodiment of the present disclosure.
  • FIG16 is a sixth schematic diagram of a state transition process provided by an embodiment of the present disclosure.
  • FIG17 is a seventh schematic diagram of a state transition process provided by an embodiment of the present disclosure.
  • FIG18 is one of the schematic diagrams of the RNA updating process provided by the embodiment of the present disclosure.
  • FIG19 is a second schematic diagram of the RNA update process provided by an embodiment of the present disclosure.
  • FIG20 is a third schematic diagram of the RNA update process provided by an embodiment of the present disclosure.
  • FIG21 is an eighth schematic diagram of a state transition process provided by an embodiment of the present disclosure.
  • FIG22 is a schematic diagram of a flow chart of a path switching method provided in an embodiment of the present disclosure.
  • FIG23 is a schematic diagram of a flow chart of a RAN information synchronization method provided in an embodiment of the present disclosure
  • FIG24 is a schematic diagram of a structure of a terminal status management device according to an embodiment of the present disclosure.
  • 25 is a second structural diagram of the terminal status management device provided in an embodiment of the present disclosure.
  • 26 is a third structural diagram of the terminal status management device provided in an embodiment of the present disclosure.
  • FIG27 is a schematic diagram of the structure of an access network RAN device provided in an embodiment of the present disclosure.
  • FIG28 is a schematic diagram of the structure of a terminal provided in an embodiment of the present disclosure.
  • FIG. 29 is a schematic diagram of the structure of the core network CN device provided in an embodiment of the present disclosure.
  • the term "and/or" describes the association relationship of associated objects, indicating that there may be three relationships.
  • a and/or B can 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. Tie.
  • plurality in the embodiments of the present disclosure refers to two or more than two, and other quantifiers are similar thereto.
  • 5G Fifth Generation Mobile Communication Technology
  • applicable systems may be global system of mobile communication (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) general packet radio service (GPRS) system, long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, long term evolution advanced (LTE-A) system, universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) system, 5G new radio (NR) system, etc.
  • GSM global system of mobile communication
  • CDMA code division multiple access
  • WCDMA wideband code division multiple access
  • GPRS general packet radio service
  • LTE long term evolution
  • FDD LTE frequency division duplex
  • TDD LTE time division duplex
  • LTE-A long term evolution advanced
  • UMTS universal mobile telecommunication system
  • WiMAX worldwide interoperability for microwave access
  • NR new radio
  • the terminal device involved in the embodiments of the present disclosure may be a device that provides voice and/or data connectivity to users, a handheld device with wireless connection function, or other processing devices connected to a wireless modem, etc.
  • the name of the terminal device may also be different.
  • the terminal device may be called User Equipment (UE).
  • UE User Equipment
  • the wireless terminal device can communicate with one or more core networks (CN) via a radio access network (RAN).
  • CN core networks
  • RAN radio access network
  • the wireless terminal device may be a mobile terminal device, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal device.
  • it may be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges language and/or data with a radio access network.
  • Wireless terminal equipment may also be referred to as system, subscriber unit, subscriber station, mobile station, mobile, remote station, access point, remote terminal equipment, access terminal equipment, user terminal equipment, user agent, user device, which is not limited in the embodiments of the present disclosure.
  • the network device involved in the embodiments of the present disclosure may be a base station, which may include multiple cells providing services to the terminal.
  • 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 can be used to interchange received air frames with Internet Protocol (IP) packets, acting 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.
  • IP Internet Protocol
  • the network device may also coordinate the attribute management of the air interface.
  • the network device involved in the embodiments of the present disclosure may be a network device (Base Transceiver Station, BTS) in the Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA), or a network device (NodeB) in Wide-band Code Division Multiple Access (WCDMA), or an evolved network device (evolutional Node B, eNB or e-NodeB) in the Long Term Evolution (LTE) system, a 5G base station (gNB) in the 5G network architecture (next generation system), or a Home evolved Node B (HeNB), a relay node, a home base station (femto), a pico base station (pico), etc., but is not limited in the embodiments of the present disclosure.
  • network devices may include centralized unit (CU) nodes and distributed unit (DU) nodes, and the centralized unit and the distributed unit may also be geographically separated.
  • 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. (Single User MIMO, SU-MIMO) or Multi-User MIMO (Multiple User MIMO, MU-MIMO).
  • 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.
  • FIG. 1 is a schematic diagram of the N2 interface in the related technology provided by the present disclosure.
  • 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.
  • AMF Access and Mobility Management Function
  • FIG2 is one of the schematic diagrams of the RAN service-oriented architecture provided in the present disclosure
  • FIG3 is the second schematic diagram of the RAN service-oriented architecture provided in the present disclosure.
  • the RAN can be connected to multiple network function entities (NF) in the core network (CN).
  • NF network function entities
  • CN core network
  • the embodiments of the present disclosure provide a method for managing terminal status, which can be applied to scenarios after RAN serviceization.
  • FIG. 4 is one of the flow diagrams of the terminal status management method provided in the embodiment of the present disclosure. As shown in FIG. 4 , the embodiment of the present disclosure provides a terminal status management method, which is applied to an access network RAN device, including:
  • 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.
  • RAN can be a base station, such as a 5G base station (generation NodeB, gNB), etc.
  • 5G base station generation NodeB, gNB
  • 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:
  • connection status between the RAN device and the terminal The connection status between the RAN device and the terminal.
  • connection status between the terminal and the core network CN The connection status between the terminal and the core network CN.
  • connection state between the RAN device and the terminal may include:
  • the RAN device has established a connection with the terminal
  • the RAN device suspends the connection with the terminal
  • the RAN device is disconnected from the terminal.
  • connection status between the terminal and the core network CN may include:
  • the terminal has established a connection with the core network
  • the terminal is disconnected from the core network.
  • connection status between the terminal and the network side is different.
  • 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;
  • 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;
  • the RAN device is disconnected from the terminal, and the terminal has established a connection with the core network, which is the third state.
  • the terminal status management method provided in the embodiment of the present disclosure can be applied to the RAN service-oriented scenario.
  • 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.
  • 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 status of the UE in the relevant method is managed by the AMF.
  • the UE status is still managed by AMF. Then, each time the CN NF interacts with the RAN, it needs to obtain the UE status from the AMF, which increases the signaling interaction and brings the problem of UE status synchronization between CN NFs.
  • 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.
  • the terminal state includes a connected state, an idle state, and an inactive state
  • the terminal state includes a connected state and an inactive state
  • the connected state may also be referred to as UE-CONNECTED.
  • the embodiment of the present disclosure does not limit the naming of this state.
  • the RAN device stores all terminal contexts of the terminal. It should be understood that the terminal context in the embodiment of the present disclosure includes AS layer context, NF information of the serving UE, etc., which will not be described in detail below;
  • RRC radio resource control
  • 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.
  • 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.
  • NAS Non-Access Stratum
  • the establishment of a NAS connection between the terminal and any NF in the CN can refer to related technologies.
  • 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 related technologies, such as serving as a termination point for non-access stratum security.
  • 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.
  • 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.
  • HTTP HyperText Transfer Protocol
  • the function of the extended N2 interface can refer to the relevant technology.
  • the idle state may also be referred to as UE-IDLE.
  • the present disclosure does not limit the naming of this state.
  • 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;
  • AS access stratum
  • 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;
  • 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.
  • the access network device establishes an N2 connection with any CN NF, which is not repeated here with reference to the above description.
  • the method further includes:
  • whether the N3 connection is disconnected is not limited in the embodiment of the present disclosure.
  • the inactive state may also be referred to as UE-INACTIVE.
  • the present disclosure does not limit the naming of this state.
  • 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;
  • 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;
  • 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.
  • the access network device establishes an N2 connection with any CN NF, which is not repeated here with reference to the above description.
  • the terminal status management method provided by the embodiment of the present disclosure defines different terminal statuses through a connected state, an idle state, and an inactive state, thereby simplifying the terminal status.
  • 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.
  • 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.
  • performing terminal state migration according to a change in a connection between the terminal and the RAN device includes:
  • Terminal state migration is performed according to a change in the RRC connection between the terminal and the RAN device.
  • 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:
  • the terminal state is the idle state
  • the terminal state is migrated from the idle state to the connected state
  • 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;
  • the terminal state is the inactive state
  • the terminal state is migrated from the inactive state to the idle state.
  • FIG. 5 is one of the schematic diagrams of terminal state migration in the RAN provided by an embodiment of the present disclosure.
  • 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:
  • the terminal state is the connected state
  • the RAN device and the terminal are connected. After the RRC connection is suspended, migrating the terminal state from the connected state to the inactive state;
  • 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;
  • 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;
  • the terminal state is the inactive state
  • the terminal state is migrated from the inactive state to the idle state.
  • FIG. 6 is a second schematic diagram of terminal state migration in a RAN provided in an embodiment of the present disclosure.
  • the terminal state includes a connected state and an inactive state
  • performing terminal state migration according to a change in a connection between the terminal and the RAN device includes:
  • 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;
  • the terminal state is the inactive state
  • the terminal state is migrated from the inactive state to the connected state.
  • the terminal status management method provided in the embodiment of the present disclosure 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.
  • the method further comprises:
  • 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.
  • 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.
  • the managing whether the terminal is reachable in different terminal states includes but is not limited to at least one of the following:
  • a protection timer is started, and whether the terminal is reachable is determined according to whether the protection timer times out.
  • whether 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:
  • 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.
  • the RAN If the terminal does not apply the MICO mode and can send downlink data to the UE (Mobile Terminated, MT), the RAN considers that the UE is reachable. At this time, the terminal can send MO data and receive MT data.
  • MT Mobile Terminated
  • a paging process is initiated for the UE according to a paging trigger condition.
  • 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 embodiments of the present disclosure do not limit the paging trigger condition.
  • a paging process is initiated for the UE according to a paging trigger condition.
  • 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 embodiments of the present disclosure do not limit the paging trigger condition.
  • the RAN When the mobile reachable timer times out, the RAN considers that the terminal is unreachable.
  • the RAN considers that the terminal is reachable.
  • 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.
  • 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.
  • the first timer value of the periodic RRC establishment timer may be allocated by the RAN to the UE according to local policies, information provided by the UE, etc.
  • the embodiment of the present disclosure does not limit the value of the first timer value and how to set it.
  • the mobile reachable timer is used to indicate a third timer value, which is longer than the first timer value.
  • a deregistration process is triggered to deregister the terminal device from the CN.
  • the third timer value is longer than the first timer value.
  • the RAN 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.
  • 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.
  • the periodic RRC establishment timer counts, and if the RRC connection has not been established, the periodic RRC establishment timer continues to count
  • the mobile reachable timer will stop timing. If the RRC connection has not been established, the mobile reachable timer will continue timing.
  • the RAN When the protection timer times out, the RAN considers that the terminal is unreachable.
  • the protection timer does not time out, and the RAN considers that the terminal is reachable.
  • the periodic notification area update timer is configured by the RAN for the UE and is started on the UE side.
  • the UE enters the inactive state UE-INACTIVE
  • the UE starts the periodic notification area update timer.
  • 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 disclosure does not limit the value of the second timer value and how to set it.
  • 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.
  • the fourth timer value is longer than the second timer value.
  • 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.
  • 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;
  • the protection timer stops timing. If the RNA update process has not been executed, the protection timer continues timing.
  • the location information of the terminal known by the RAN device is of a second granularity
  • the location information of the terminal known by the RAN device is of the third granularity.
  • the location information of the terminal known by the RAN device is at a cell level, and the first granularity is the cell;
  • the location information of the terminal known by the RAN device is a tracking area list (Tracking Area list, TA list), and the second granularity is the TA list;
  • the location information of the terminal known by the RAN device is the RAN notification area (RAN Notification area, RNA) granularity, that is, the third granularity is RNA.
  • RAN Notification area RNA
  • the terminal status management method provided in the embodiment of the present disclosure 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.
  • the terminal status of the management terminal includes:
  • an RRC release message is sent to the terminal.
  • the RAN can send an RRC Release message to the UE.
  • a PDU session update SM context request Nsmf_PDUSession_UpdateSMContext Request 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.
  • the terminal status of the management terminal includes:
  • an RRC suspend message is sent to the terminal.
  • the network if the network 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.
  • the method further includes at least one of the following:
  • 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.
  • 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.
  • 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.
  • a first RRC reject RRCReject message is sent to the terminal.
  • 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.
  • the terminal state remains in the idle state.
  • the method further includes at least one of the following:
  • 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.
  • the terminal state is migrated from the inactive state to the connected state;
  • the RRC connection with the terminal is restored, and the RRC connection between the RAN device and the terminal is restored.
  • the method further comprises:
  • a second RRC reject RRCReject message is sent to the terminal.
  • 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.
  • the terminal state remains in the inactive state.
  • Receive buffered data sent by the anchor access network device the buffered data being the network side in the downlink data sent by the terminal in the inactive state or the idle state;
  • the buffered data is sent to the terminal.
  • 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.
  • the current RAN device may receive the buffered data directly forwarded by 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.
  • the method further comprises:
  • the determining of the anchor access network device includes:
  • the anchor access network device is determined based on the received Radio Network Temporary Identity (RNTI) of the terminal.
  • RNTI Radio Network Temporary Identity
  • 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 disclosure may be applied to an idle state and/or an inactive state.
  • the anchor access network device can carry an RNTI identifier in the RRCRelease message.
  • the RNTI also called the idle state RNTI identifier
  • the idle state UE 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).
  • 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.
  • the anchor access network device can carry the RNTI identifier in the RRC Release with Suspend Indication message.
  • the RNTI also called the inactive RNTI identifier
  • the inactive UE 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).
  • 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.
  • 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.
  • the anchor point gNB is determined based on the RNTI.
  • 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.
  • 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.
  • 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.
  • a network element registration request message is sent to the CN, and registration can be performed with the network elements in the core network.
  • the network elements in the core network can be registered with unified data management functions (UDM), unified data repository functions (UDR) or network repository functions (NRF).
  • UDM unified data management functions
  • UDR unified data repository functions
  • NRF network repository functions
  • 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 by the embodiment of the present disclosure is that the RAN device sends a network element registration request message to the CN, and through the network element registration request message, indicates the information of the RAN device currently serving the terminal, 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.
  • FIG. 7 is a second flow chart of a method for managing terminal status provided in an embodiment of the present disclosure. As shown in FIG. 7 , an embodiment of the present disclosure provides a method for managing terminal status, which is applied to a terminal and includes:
  • 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.
  • the terminal needs to manage its own terminal status.
  • 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:
  • connection status between the terminal and the RAN device The connection status between the terminal and the RAN device.
  • connection status between the terminal and the core network CN The connection status between the terminal and the core network CN.
  • connection status between the terminal and the RAN device may include:
  • the terminal has established a connection with the RAN device
  • the terminal suspends the connection with the RAN device
  • the terminal is disconnected from the RAN device.
  • connection status between the terminal and the core network CN may include:
  • the terminal has established a connection with the core network.
  • 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;
  • 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;
  • the RAN device is disconnected from the terminal, and the terminal has established a connection with the core network, which is the third state.
  • the terminal status management method manages its own terminal status by the terminal, 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
  • the second connection status is the connection status between the terminal and the core network CN, which simplifies the terminal status.
  • the terminal state includes a connected state, an idle state, and an inactive state
  • the terminal state includes a connected state and an inactive state
  • the connected state may also be referred to as UE-CONNECTED.
  • the naming is not limited.
  • the terminal status is the connection status described above:
  • the RAN device stores all terminal contexts of the terminal
  • RRC radio resource control
  • 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.
  • 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.
  • NAS Non-Access Stratum
  • the establishment of a NAS connection between the terminal and any NF in the CN can refer to related technologies.
  • 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 related technologies, such as serving as a termination point for non-access stratum security.
  • 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.
  • 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.
  • HTTP HyperText Transfer Protocol
  • the idle state may also be referred to as UE-IDLE.
  • the present disclosure does not limit the naming of this state.
  • 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;
  • AS access stratum
  • 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;
  • 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.
  • the access network device establishes an N2 connection with any CN NF, which is not repeated here with reference to the above description.
  • the method further includes:
  • whether the N3 connection is disconnected is not limited in the embodiment of the present disclosure.
  • 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;
  • 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.
  • the access network device establishes an N2 connection with any CN NF, which is not repeated here with reference to the above description.
  • the terminal status management method provided by the embodiment of the present disclosure defines different terminal statuses through a connected state, an idle state, and an inactive state, thereby simplifying the terminal status.
  • 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.
  • 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.
  • 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.
  • 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:
  • 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
  • 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
  • the RAN device and the terminal are connected After the RRC connection is established, migrating the terminal state from the idle state to the connected state; or
  • 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;
  • the terminal state is the inactive state
  • the terminal state is migrated from the inactive state to the idle state.
  • FIG. 8 is one of the schematic diagrams of terminal state migration in the UE provided in an embodiment of the present disclosure.
  • 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:
  • 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;
  • 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;
  • 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;
  • 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;
  • the terminal state is the inactive state
  • the terminal state is migrated from the inactive state to the idle 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.
  • 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.
  • FIG. 9 is a second schematic diagram of terminal state migration in a UE provided in an embodiment of the present disclosure.
  • 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:
  • 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;
  • the terminal status management method provided in the embodiment of the present disclosure 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.
  • the downlink data reception situation is different.
  • the downlink data reception situation may include whether there is downlink data, and when there is downlink data, receiving the downlink data.
  • 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:
  • the terminal does not apply the terminal-initiated-only connection MICO mode, if the downlink data exists, receiving the downlink data;
  • the terminal state is the connected state and the terminal applies the MICO mode, if the downlink data exists, the downlink data is received.
  • 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:
  • the terminal does not apply the MICO mode.
  • RAN can send downlink data (Mobile Terminated, MT) to the UE.
  • MT Mobile Terminated
  • the terminal receives MT data.
  • the terminal can send MO data or receive MT data.
  • the RAN can still send downlink data MT to the UE.
  • the terminal receives the MT data.
  • the terminal can send MO data or receive MT data.
  • the downlink data does not exist:
  • the terminal status management method provided by the embodiment of the present disclosure relates downlink data reception to the terminal status and whether the MICO mode is applied, thereby ensuring downlink data transmission of the terminal.
  • the method further comprises:
  • the terminal state is the idle state or the inactive state and the terminal applies the MICO mode, the paging message is not monitored.
  • the RAN may page the UE, and the UE may correspondingly monitor the paging message and execute the paging process.
  • the terminal state is the idle state or the inactive state and the terminal applies the MICO mode, the paging message is not monitored:
  • the network side 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.
  • the terminal status management method 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; and does not monitor paging messages when the terminal status is the idle state or the inactive state and the terminal applies the MICO mode to avoid the terminal wasting resources for monitoring.
  • the method further includes but is not limited to at least one of the following:
  • a periodic RRC establishment timer is started.
  • the RRC establishment timer is used to indicate a first timer value, and the RRC establishment process is performed based on the first timer value; or
  • 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.
  • 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.
  • the terminal executes the RRC establishment process.
  • a periodic RRC establishment timer is used to enable the terminal to regularly establish an RRC connection and maintain a connection with the RAN.
  • 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.
  • the UE enters the inactive state UE-INACTIVE
  • the UE starts the periodic notification area update timer.
  • the periodic notification area update timer exceeds the second timer value, the UE executes the RAN notification area update process.
  • 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.
  • the method 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.
  • 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.
  • 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.
  • the method further includes at least one of the following:
  • the terminal triggers an RRC establishment process in response to the network side paging, and establishes an RRC connection with the RAN device.
  • 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;
  • the terminal 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;
  • the method further comprises:
  • the terminal state remains in the idle state.
  • the terminal initiates an RRC establishment request after the first waiting time.
  • the terminal actively initiates an RRC recovery procedure to restore the RRC connection with the RAN device;
  • the terminal triggers the RRC recovery process in response to the network side paging, and recovers the RRC connection with the RAN device.
  • 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;
  • the terminal 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;
  • 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.
  • the method further comprises:
  • the terminal state remains in the inactive state.
  • the second RRC rejection message carries a second waiting time
  • the method further includes:
  • the terminal initiates an RRC recovery request after the second waiting time.
  • 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.
  • FIG. 10 is a flow chart of a third method for managing terminal status provided in an embodiment of the present disclosure. As shown in FIG. 10 , an embodiment of the present disclosure provides a method for managing terminal status, which is applied to a core network CN device, including:
  • 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
  • the RAN device After the terminal registers with the CN, the RAN device interacts with the terminal.
  • RM Registration Management
  • the registration management RM state is managed by any NF in the core network, and optionally, the RM state is managed by AMF.
  • the registration management RM status may include:
  • 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 UE context can still be stored in UE and AMF to avoid identity authentication during each registration process.
  • the RM-REGISTERED state indicates that the UE has registered with the network.
  • the core network 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.
  • the core network only needs to manage the RM status of the UE: as long as the terminal registers with the core network and the UE status 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 connected and 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 also avoiding the UE status synchronization problem between the core network NFs after RAN service-oriented.
  • the interacting with the terminal through an access network RAN device according to the RM state of the terminal includes:
  • the RAN device When the registration management RM state of the terminal is registered, the RAN device directly interacts with the terminal.
  • the terminal status management method provided by the embodiment of the present disclosure 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, which reduces the overhead of the terminal, RAN and core network in managing the UE status and simplifies the functions and interaction processes of the UE and the core network.
  • the method further includes:
  • PDU session update context request carries PDU session information of a target PDU session
  • a user plane function UPF entity is determined based on the PDU session information, and the UPF entity is used to Sending 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;
  • 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.
  • the target PDU session is an affected PDU session.
  • the method further includes:
  • 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.
  • 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:
  • SMF sends N4 Session Modification Request message to S-UPF to establish the forwarding path from S-UPF to RAN:
  • 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.
  • the SMF may send the forwarding path of the buffered data of the forwarding anchor access network device to the S-UPF.
  • 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.
  • indirect data forwarding Indirect data forwarding
  • 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.
  • T-UPF Target-UPF, abbreviated as T-UPF:
  • 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.
  • 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.
  • 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 the indirect forwarding of the buffered data (Indirect data forwarding) by the anchor access network device to the current RAN through the S-UPF and T-UPF.
  • SMF sends an N4 Session Modification Request message to PSA to establish a data transmission tunnel between PSA and T-UPF.
  • 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.
  • the SMF releases the S-UPF.
  • 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.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • the terminal states include a connected state UE-CONNECTED, an idle state UE-IDLE and an inactive state UE-INACTIVE.
  • the registration management RM state is managed by any CN NF, and optionally by AMF.
  • the state definition and transition of RM refer to related technologies and will not be repeated 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 has established a NAS connection with any CN NF.
  • N2 (broadly defined N2, the same below) connection between AN (also called access network equipment) and NF is maintained.
  • N2 refers to the interface for interaction between RAN and NF.
  • N2 connection maintenance means that AN has a connection with any CN NF.
  • RAN saves UE context (excluding AS layer context), UE does not save AS layer context;
  • the RRC connection is disconnected
  • N2 connection is maintained.
  • the N2 connection between AN and NF is maintained.
  • N2 refers to the interface between RAN and NF.
  • N2 connection maintenance means that AN has a connection with any CN NF.
  • whether the N3 connection must be disconnected is not limited in the embodiment of the present disclosure.
  • the UE context (including AS layer context) is stored in the RAN;
  • the RRC connection is suspended, retaining the characteristics of the RRC-INACTIVE state
  • the N3 connection is maintained.
  • NAS connection refers to the NA connection between UE and CN NF through N1, and CN NF is the NF that has direct interaction needs 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 information such as the NF serving the UE.
  • the UE In UE-IDLE state, the UE shall:
  • the UE 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.
  • the UE When the RRC establishment request initiated by the UE is rejected, the UE remains in the UE-IDLE state.
  • the UE In UE-CONNECTED state, the UE shall:
  • the UE When the RRC connection between the UE and the RAN is released, the UE enters the UE-IDLE state from the UE-CONNECTED state.
  • the UE When the RRC connection between the UE and the RAN is suspended, the UE enters the UE-INACTIVE state from the UE-CONNECTED state.
  • the UE In UE-INACTIVE state, the UE shall:
  • the UE When the RRC connection between the UE and the RAN is restored, the UE enters the UE-CONNECTED state from the UE-INACTIVE state.
  • the UE When the RRC recovery request initiated by the UE is rejected, the UE remains in the UE-INACTIVE state.
  • the UE After the UE receives the RRC suspension configuration from the network side, the UE remains in the UE-INACTIVE state.
  • the UE When the UE receives the RRC release message from the network side, the UE enters the UE-IDLE state from the UE-INACTIVE state.
  • the RAN When the UE in the RAN is in the UE-CONNECTED state, the RAN shall:
  • the UE state in the RAN changes to the UE-IDLE state.
  • the UE state in RAN changes to UE-INACTIVE state.
  • the RAN shall:
  • the UE state in the RAN changes to the UE-CONNECTED state.
  • the RAN When the UE in the RAN is in the UE-INACTIVE state, the RAN shall:
  • the UE state in the RAN changes to the UE-CONNECTED state.
  • the UE state in the RAN changes to the UE-IDLE state.
  • 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.
  • the UE location information known to the network is at the cell granularity.
  • the UE applies the MICO mode, in which the UE can receive MT data.
  • the UE location information known to the network is at the TA list granularity.
  • the RAN can page the UE. In the case that the UE applies the MICO mode, the RAN cannot page the UE.
  • the UE may have MO and MT data.
  • 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.
  • the UE 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.).
  • the RAN 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.
  • the RAN needs to obtain relevant information about the UE applying the MICO mode.
  • the embodiment of the present disclosure does not limit how to obtain the application of the MICO mode.
  • RNA can be part of the cells configured in the UE registration area or all the cells configured in the UE registration area.
  • the UE can be paged in a cell located in the RAN notification area RNA (unless the UE applies MICO mode).
  • the UE may have MO and MT data.
  • 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.
  • the UE When the UE moves out of the RAN notification area, the UE needs to perform the RAN notification area update procedure.
  • the RAN configures a periodic RAN notification area update timer value for the UE, and the UE starts the timer.
  • the periodic RAN notification area update timer in the UE times out, the UE executes the RAN notification area update procedure.
  • a protection timer is started in the RAN, whose value is longer than the RAN notification area update timer value provided to the UE.
  • the RAN starts the RRC release procedure and the UE enters the RRC-IDLE state.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • the terminal status includes a connected state UE-CONNECTED and an inactive state UE-INACTIVE.
  • the registration management RM state is managed by any CN NF, and optionally by AMF.
  • the state definition and transition of RM refer to related technologies and will not be repeated 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 has established a NAS connection with any CN NF.
  • N2 (broadly defined N2, the same below) connection between AN (also called access network equipment) and NF is maintained.
  • 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 (including AS layer context) is stored in the RAN;
  • the RRC connection is suspended, retaining the characteristics of the RRC-INACTIVE state
  • the N3 connection is maintained.
  • NAS connection refers to the NA connection between UE and CN NF through N1, and CN NF is the NF that has direct interaction needs with the UE; the NAS connection maintenance means that the 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 information such as the NF serving the UE.
  • the UE In UE-INACTIVE state, the UE shall:
  • the UE When the RRC connection between the UE and the RAN is restored, the UE enters the UE-CONNECTED state from the UE-INACTIVE state.
  • the UE When the RRC recovery request between the UE and the RAN is rejected, the UE remains in the UE-INACTIVE state.
  • the UE In UE-CONNECTED state, the UE shall:
  • the UE When the RRC connection between the UE and the RAN is suspended, the UE enters the UE-INACTIVE state from the UE-CONNECTED state.
  • the RAN When the UE in the RAN is in the UE-CONNECTED state, the RAN shall:
  • the UE state in the RAN enters the UE-INACTIVE state.
  • the RAN When the UE in the RAN is in the UE-INACTIVE state, the RAN shall:
  • the UE state in the RAN enters the UE-CONNECTED state.
  • the UE location information known to the network is at the cell granularity.
  • the UE applies the MICO mode, in which the UE can receive MT data.
  • RNA can be part of the cells configured in the UE registration area or all the cells configured in the UE registration area.
  • the UE can be paged in a cell located in the RAN notification area RNA (unless the UE applies MICO mode).
  • the UE may have MO and MT data.
  • the RAN configures a periodic RAN notification area update timer value for the UE, and the UE starts the timer.
  • the periodic RAN notification area update timer in the UE times out, the UE executes the RAN notification area update procedure.
  • Embodiment 3 Conversion from UE-CONNECTED to UE-IDLE;
  • FIG. 11 is one of the state transition flow diagrams provided in an embodiment of the present disclosure. As shown in FIG. 11 , if the network side wants the UE to enter or maintain the UE-IDLE state, the RAN sends a RRCRelease message to the UE;
  • the UE After the UE receives the RRCRelease message, it enters the UE-IDLE state.
  • the gNB 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 to the SMF
  • the SMF requests the Nsmf_PDUSession_UpdateSMContext Request message, indicating that the UE cannot access the downlink data.
  • the SMF sends the N4 Session Modification Request message to the UPF, instructing the UPF to release the user plane resources on the N3 side and instructing the UPF to buffer the DL data packets.
  • the UPF sends the N4 Session Modification Response message to the SMF, and the SMF sends the PDU session update SM context response Nsmf_PDUSession_UpdateSMContext Response message to the gNB.
  • Embodiment 4 UE-CONNECTED to UE-INACTIVE conversion
  • the RAN When the RAN side decides to suspend the connected UE to enter the UE-INACTIVE state, the RAN notifies the UE through an RRC suspend message.
  • Figure 12 is the second state transition flow diagram provided by an embodiment of the present disclosure.
  • 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.
  • the UE 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 and AS layer context, suspends the current air interface connection, and enters the UE-ACTIVE state.
  • the UE triggers the transition from UE-IDLE to UE-CONNECTED state successfully;
  • FIG. 13 is a third schematic diagram of a state transition process provided by an embodiment of the present disclosure. As shown in FIG. 13 , when a UE in an idle state wishes to initiate a call or respond to a paging call, an RRC establishment process is triggered:
  • Step 1 When the UE is in idle state, it sends an RRC Setup Request message to the gNB.
  • Step 2 gNB sends an RRCSetup message to the UE.
  • the UE enters the connected state.
  • Step 3 UE sends an RRC Setup Complete message to gNB.
  • UE and gNB complete the RRC setup process.
  • 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 anchor gNB is not the same gNB, the gNB sends a request Nran_UEContextTransfer Request message to the anchor gNB to obtain the AS context.
  • Step 5 The anchor gNB provides the stored UE context to the current gNB via the context response Nran_UEContextTransfer Response message.
  • 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.
  • 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 radio signaling bearers (SRB) 2 and radio data bearers (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).
  • SRB radio signaling bearers
  • DRB radio data bearers
  • 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.
  • Step 9 gNB (i.e. current gNB) sends PDU session update SM context request Nsmf_PDUSession_UpdateSMContext Request message to SMF.
  • Step 9a The current gNB triggers path switching.
  • Step 10 SMF sends the PDU session update SM context response Nsmf_PDUSession_UpdateSMContext Response message to gNB.
  • Step 11 The current gNB sends a UE context release request Nran_UEContextRelease Request 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.
  • FIG. 14 is a fourth schematic diagram of a state transition process provided by an embodiment of the present disclosure.
  • the gNB if the gNB refuses to establish an RRC for the UE, it replies to the UE with an RRCReject message.
  • the message may carry a first waiting time, which indicates that the UE is suitable to initiate an access process.
  • the UE After receiving the RRCReject message, the UE remains in the UE-IDLE state.
  • the method further comprises:
  • a first RRC reject RRCReject message is sent to the terminal.
  • 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.
  • the terminal state remains in the idle state.
  • Embodiment 6 UE state transition in UE-INACTIVE
  • the UE triggers the UE-INACTIVE to UE-CONNECTED state transition
  • FIG. 15 is a fifth schematic diagram of a state transition process provided by an embodiment of the present disclosure. As shown in FIG. 15 , when a UE in an inactive state wishes to initiate a call or respond to a paging call, a recovery process is triggered:
  • Step 1 The inactive UE sends an RRC Resume Request message to the gNB.
  • 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.
  • the anchor gNB 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.
  • 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 through the UE context forwarding response Nran_UEContextTransfer Response message.
  • Step 4 The current gNB generates the RRC configuration based on the received UE context, and then sends an RRC Resume message to the UE.
  • the RRC connection is restored and the terminal state is transferred from the inactive state to the connected state.
  • Step 5 After the UE completes the RRC recovery message configuration, it sends an RRC recovery complete message to the current gNB.
  • 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.
  • 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.
  • Step 9 The current gNB sends a UE context release message to the anchor gNB, and the anchor gNB releases the UE context.
  • 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.
  • FIG. 16 is a sixth schematic diagram of a state transition process provided by an embodiment of the present disclosure, as shown in FIG. 16 :
  • Step 1 The inactive UE sends an RRC Resume Request message to the gNB.
  • 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).
  • the anchor gNB 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).
  • Step 3 The anchor gNB fails to extract or verify the UE context partially or completely.
  • 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.
  • 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.
  • Step 5 The current gNB sends an RRCSetup message to establish a new RRC connection.
  • 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.
  • Step 6 The current gNB sends a RRCRelease message to the UE, causing the UE to enter the UE-IDLE state.
  • FIG17 is a seventh state transition flow diagram provided by an embodiment of the present disclosure.
  • the gNB the gNB currently serving the terminal, in the figure, is gNB
  • the gNB sends a second RRCReject message to the UE, and carries a second waiting time, indicating that the UE initiates the RRC recovery process again at an appropriate time.
  • the UE remains in the UE-INACTIVE state.
  • the method further comprises:
  • a second RRC reject RRCReject message is sent to the terminal.
  • 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.
  • the terminal state remains in the inactive state.
  • RNA RAN Notification Area
  • a timer duration of a periodic notification area update timer may be configured for the UE, and the UE starts the periodic notification area update timer when entering the inactive state.
  • Step 1 The inactive UE sends an RRC recovery request (RRC RNA Update) message to the gNB.
  • RRC RNA Update RRC recovery request
  • Step 2 The current gNB (the gNB currently serving the terminal, in the figure gNB) receives the UE After the RRC recovery request is received, the anchor gNB is determined.
  • the anchor gNB 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 request message to the anchor gNB to obtain the UE context (all).
  • Step 4 The current gNB generates RRC configuration based on the received UE context and decides to release the UE to the inactive state.
  • 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.
  • Step 9 The current gNB sends a UE context release message to the anchor gNB, and the anchor gNB releases the UE context.
  • 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.
  • the anchor gNB 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.
  • FIG. 19 is a second schematic diagram of the RNA update process provided by an embodiment of the present disclosure, as shown in FIG. 19 :
  • Step 1 The inactive UE sends an RRC recovery request (RRC RNA Update) message to the gNB.
  • RRC RNA Update RRC recovery request
  • Step 2 The current gNB (the gNB currently serving the terminal, in the figure gNB) receives the UE After the RRC recovery request is received, the anchor gNB is determined.
  • the anchor gNB refers to the gNB that last served the UE when the UE enters 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.
  • the UE context is the entire context of the UE.
  • Step 3 The anchor gNB can inform the current gNB of the failure to extract the UE context by sending a UE context forwarding response Nran_UEContextTransfer Response message to the current gNB.
  • the Nran_UEContextTransfer Response message contains an encapsulated RRC suspend message.
  • 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.
  • FIG. 20 is a third schematic diagram of the RNA update process provided by an embodiment of the present disclosure, as shown in FIG. 20 :
  • Step 1 The inactive UE sends an RRC recovery request (RRC RNA Update) message to the gNB.
  • RRC RNA Update RRC recovery request
  • Step 3 The anchor gNB can inform the current gNB of the failure to extract the UE context by sending a UE context forwarding response Nran_UEContextTransfer Response message to the current gNB.
  • the Nran_UEContextTransfer Response message contains an encapsulated RRC release RRCRelease message.
  • 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.
  • the network side triggers the UE-IDLE/UE-INACTIVE to UE-CONNECTED state transition
  • the anchor gNB can trigger the paging process of the RAN to enable the UE to perform the RRC establishment/recovery process.
  • FIG. 21 is an eighth schematic diagram of a state transition process provided by an embodiment of the present disclosure, as shown in FIG. 21 :
  • 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.
  • Step 3 The anchor gNB broadcasts a paging message to eligible RANs.
  • Step 4 Paging the UE.
  • Step 5 The UE responds to the paging message and triggers the RRC establishment/recovery process.
  • the RRC establishment process can refer to (I) described in Example 5
  • the RRC recovery process can refer to (I) described in Example 6.
  • 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.
  • NFs such as NRF/UDM/UDR.
  • Embodiment 8 A method for the current gNB to obtain the anchor gNB in the idle state/inactive state
  • the anchor access network device can carry an RNTI identifier in the RRCRelease message.
  • the RNTI also called the idle state RNTI identifier
  • the idle state UE 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).
  • 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.
  • the anchor access network device can carry the RNTI identifier in the RRC Release with Suspend Indication message.
  • the RNTI also called the inactive RNTI identifier
  • the inactive UE 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) connected before the UE enters the inactive state UE-INACTIVE, that is, to find the anchor access network device.
  • 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 in the anchor access network device before the UE enters the UE-INACTIVE state.
  • Both the UE side and the RAN side will store RNTI (RNTI identifier in the inactive state or RNTI identifier in the idle state).
  • 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.
  • 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).
  • RNTI is divided into two different lengths, and reference may be made to related technologies.
  • Embodiment 9 Path switching method
  • FIG. 22 is a schematic flow chart of a path switching method provided in an embodiment of the present disclosure, as shown in FIG. 22 :
  • 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.
  • Step 6.1 If there is an Xn interface between the current gNB (currently the gNB serving the terminal, gNB in the figure) and the anchor gNB, the direct data forwarding mode is used.
  • 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.
  • Step 8 SMF selects UPF based on the affected PDU Session (i.e. target PDU session).
  • 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.
  • 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.
  • Step 9.2 S-UPF sends N4 Session Modification Response message to SMF.
  • Step 6.21 The anchor gNB sends the buffered data to the S-UPF.
  • 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).
  • 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.
  • PSA PDU Session Anchor
  • 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.
  • Step 9.4 T-UPF sends N4 Session Establish Response message to SMF.
  • 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 through the anchor gNB to S-UPF and then to T-UPF, and finally forwarded to the current gNB through T-UPF.
  • Step 9.6 S-UPF sends N4 Session Modification Response message to SMF.
  • 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.
  • Step 6.24 T-UPF sends buffered data to the current gNB. That is, the anchor gNB sends the buffered data to the current gNB through S-UPF. and T-UPF indirectly forwards buffered data to the current gNB (Indirect data forwarding).
  • Step 9.7 SMF sends an N4 Session Modification Request message to PSA to establish a data transmission tunnel between PSA and T-UPF.
  • Step 9.8 Send N4 Session Modification Response message to SMF.
  • 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.
  • Step 10a SMF sends an N4 Session Release Request message to S-UPF;
  • Step 10b S-UPF sends an N4 Session Release Response message to SMF.
  • Step 11 The current gNB sends a UE context release request Nran_UEContextRelease Request 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.
  • Embodiment 10 Migration and synchronization of Serving gNB
  • 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.
  • FIG. 23 is a flow chart of a RAN information synchronization method provided by an embodiment of the present disclosure, as shown in FIG. 23 :
  • Step 1 After receiving the RRCSetup/Resume Complete message from the UE, the gNB registers with the core network.
  • the core network 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).
  • UDM Unified Data Management
  • UDR Unified Data Repository
  • NRF Network Repository Function
  • the embodiment of the present disclosure solves the problem of RAN service-oriented UE status management by defining a UE status management method after RAN service-oriented UE status management.
  • the problem of UE status management after service-oriented This method integrates the status of UE in the access network and the core network.
  • the status of UE is managed by RAN.
  • the core network no longer needs to manage the connection status of UE, which simplifies the status of UE, reduces the overhead of UE and core network in managing UE status, and simplifies the functions and interaction processes of UE and core network (no need to execute UE-triggered Service Request process, network-triggered Service Request process, AN release process, etc.).
  • it also avoids the problem of UE status synchronization between core network NFs after RAN service-oriented.
  • FIG. 24 is one of the structural schematic diagrams of a terminal status management device provided in an embodiment of the present disclosure.
  • the present disclosure embodiment provides a terminal status management device, including:
  • 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.
  • 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;
  • 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;
  • 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.
  • the first management unit 2410 is configured to manage the terminal status of the terminal, including:
  • 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.
  • 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:
  • the RAN device and the terminal are connected. After the RRC connection is released, migrating the terminal state from the connected state to the idle state; or
  • 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
  • the terminal state is the idle state
  • the terminal state is migrated from the idle state to the connected state
  • 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;
  • the terminal state is the inactive state
  • the terminal state is migrated from the inactive state to the idle state.
  • the first management unit 2410 is further used to manage whether the terminal is reachable in different terminal states.
  • 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:
  • a protection timer is started, and whether the terminal is reachable is determined according to whether the protection timer times out.
  • the device further includes but is not limited to at least one of the following:
  • 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;
  • a periodic RRC establishment timer configuration unit configured 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;
  • the first paging unit is further configured to initiate a paging process for the UE according to a paging trigger condition when the terminal state is in an inactive state and the terminal does not apply the MICO mode; or
  • 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.
  • 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.
  • the location information of the terminal known by the RAN device is of a first granularity
  • the location information of the terminal known by the RAN device is of a second granularity
  • the location information of the terminal known by the RAN device is of the third granularity.
  • the first management unit 2410 configured to manage the terminal status of the terminal, includes:
  • 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
  • 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.
  • the apparatus 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:
  • the first receiving unit is further configured to do at least one of the following:
  • 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.
  • the device further includes a buffer data unit;
  • the buffer data unit is configured to receive buffer data sent by an 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;
  • the buffer data unit is further used to send the buffer data to the terminal.
  • the buffer data unit is used to receive buffer data sent by the anchor access network device, including:
  • the buffer data unit is used to determine the anchor access network device
  • the buffer data unit is used to send a data forwarding request message to the anchor access network device when an Xn interface exists 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. flush data; or
  • 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.
  • the apparatus 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;
  • the context receiving unit is used to determine the anchor access network device
  • 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;
  • the context receiving unit is configured to receive the terminal context of the terminal sent by the anchor access network device.
  • the determining of the anchor access network device includes:
  • the anchor access network device is determined according to the received wireless network temporary identifier of the terminal.
  • the apparatus when the RAN device is not the anchor access network device, the apparatus further includes an information synchronization unit;
  • 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.
  • 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 disclosure 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.
  • FIG. 25 is a second structural diagram of a terminal status management device provided in an embodiment of the present disclosure.
  • the present disclosure embodiment provides a terminal status management device, which can be applied to a terminal, including:
  • the second management unit 2510 is used to manage the terminal state of the terminal, the terminal state is related to the first connection state and the second connection state, the first connection state is the connection state between the terminal and the RAN device The second connection state is the connection state between the terminal and the core network CN.
  • 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;
  • 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;
  • 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;
  • 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.
  • the second management unit 2510 configured to manage the terminal state of the terminal, includes:
  • the terminal state migration is performed according to the change of the connection between the terminal and the RAN device.
  • 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:
  • the terminal state is the connected state
  • the terminal is transferred from the connected state to the idle state
  • 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
  • the terminal state is the idle state
  • the terminal state is migrated from the idle state to the connected state
  • 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;
  • the terminal state is the inactive state
  • the terminal state is migrated from the inactive state to the idle state.
  • the downlink data reception situation is different depending on the terminal status and whether the terminal applies the terminal-initiated-connection-only MICO mode.
  • 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:
  • the terminal does not apply the terminal-initiated-only connection MICO mode, if the downlink data exists, receiving the downlink data;
  • the terminal state is the connected state and the terminal applies the MICO mode, if the downlink data exists, the downlink data is received.
  • the device further comprises: a second paging unit;
  • 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;
  • 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.
  • the device further includes but is not limited to at least one of the following:
  • a periodic RRC establishment timer starting unit used to start a periodic RRC establishment timer when the terminal enters the idle state, the periodic RRC establishment timer is used to indicate a first timer value, and perform an RRC establishment process based on the first timer value;
  • 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;
  • 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.
  • the apparatus further includes:
  • 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;

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Les modes de réalisation de la présente divulgation concernent un procédé et un appareil de gestion d'un état de terminal. Le procédé, qui est appliqué à un dispositif de réseau d'accès radio (RAN), consiste à : gérer un état de terminal d'un terminal, l'état de terminal étant associé à un premier état de connexion et à un second état de connexion, le premier état de connexion étant un état de connexion entre un dispositif RAN et le terminal, et le second état de connexion étant un état de connexion entre le terminal et un réseau central (CN).
PCT/CN2024/090934 2023-06-09 2024-04-30 Procédé et appareil de gestion d'état de terminal WO2024250885A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202310686987.6 2023-06-09
CN202310686987.6A CN119110434A (zh) 2023-06-09 2023-06-09 终端状态的管理方法及装置

Publications (1)

Publication Number Publication Date
WO2024250885A1 true WO2024250885A1 (fr) 2024-12-12

Family

ID=93709321

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/090934 WO2024250885A1 (fr) 2023-06-09 2024-04-30 Procédé et appareil de gestion d'état de terminal

Country Status (2)

Country Link
CN (1) CN119110434A (fr)
WO (1) WO2024250885A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110351897A (zh) * 2018-04-02 2019-10-18 电信科学技术研究院有限公司 一种确定终端状态的方法、核心网设备及接入网设备
CN111615167A (zh) * 2019-02-26 2020-09-01 电信科学技术研究院有限公司 一种位置报告的方法、无线接入网实体及计算机存储介质
US20210136719A1 (en) * 2017-06-14 2021-05-06 Lg Electronics Inc. Method for managing session, and smf node for performing method
CN114449043A (zh) * 2021-11-30 2022-05-06 华为技术有限公司 通信方法及通信装置
CN116156618A (zh) * 2022-11-30 2023-05-23 浪潮通信技术有限公司 一种WiFi终端接入5G核心网的方法和系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210136719A1 (en) * 2017-06-14 2021-05-06 Lg Electronics Inc. Method for managing session, and smf node for performing method
CN110351897A (zh) * 2018-04-02 2019-10-18 电信科学技术研究院有限公司 一种确定终端状态的方法、核心网设备及接入网设备
CN111615167A (zh) * 2019-02-26 2020-09-01 电信科学技术研究院有限公司 一种位置报告的方法、无线接入网实体及计算机存储介质
CN114449043A (zh) * 2021-11-30 2022-05-06 华为技术有限公司 通信方法及通信装置
CN116156618A (zh) * 2022-11-30 2023-05-23 浪潮通信技术有限公司 一种WiFi终端接入5G核心网的方法和系统

Also Published As

Publication number Publication date
CN119110434A (zh) 2024-12-10

Similar Documents

Publication Publication Date Title
US11805567B2 (en) Method and apparatus for initiating user plane path re-establishment and communications system
JP7145319B2 (ja) リリースおよびリダイレクトが続く再開の要求
EP3783862B1 (fr) Procédé de gestion de session et élément de réseau ayant une fonction de gestion de session
KR20190138857A (ko) 데이터 버퍼링 방법 및 세션 관리 기능 엔티티
CN114745804A (zh) Ue能力信息处理方法、装置、设备及存储介质
WO2022082566A1 (fr) Procédés et dispositifs pour améliorer des réseaux de liaison terrestre et d'accès intégré (iab) pour une nouvelle radio
JP2020507967A (ja) 通信方法、端末及びアクセスネットワークデバイス
JP7615301B2 (ja) サビース処理方法、情報指示方法、端末及びネットワーク機器
JP7609298B2 (ja) 信号を送受信する方法、装置及び通信システム
US20230262557A1 (en) Methods and devices for enhancing integrated access backhaul networks for new radio
WO2024250885A1 (fr) Procédé et appareil de gestion d'état de terminal
WO2023185573A1 (fr) Procédé, appareil, et dispositif de traitement d'informations
WO2022116820A1 (fr) Procédé et appareil permettant de récupérer une connexion rrc d'un terminal
CN114585110A (zh) 终端进入非激活态的控制方法和装置
CN110383897B (zh) 在异构网络系统中提供服务的方法和设备
WO2024051504A1 (fr) Procédé et appareil de traitement de commutation, et dispositif de communication
WO2024082905A1 (fr) Procédé et appareil pour établir une session d'unité de données de protocole (pdu)
CN115915072B (zh) 一种端到端的pdu会话管理方法、装置及网络设备
EP4518409A1 (fr) Procédé et appareil de rétablissement de liaison, dispositif, et support de stockage
CN114258113B (zh) 数据传输控制方法、终端、网络设备、装置及存储介质
WO2024199148A1 (fr) Procédé et appareil de communication
WO2024017058A1 (fr) Procédé de traitement de liaison montante, procédé de traitement de service de liaison descendante, procédé de traitement de radiomessagerie, et dispositif de communication
WO2023231974A1 (fr) Procédé et appareil de gestion de session d'unités de données de protocole (pdu), et support de stockage
WO2024168747A1 (fr) Procédé et appareil de reconfiguration conditionnelle, dispositif, support d'enregistrement et produit-programme
WO2025020796A1 (fr) Procédé et appareil de transmission de données, et dispositif

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24818419

Country of ref document: EP

Kind code of ref document: A1