State resuming methods, device, system, storage medium and program product

Abstract

The present disclosure relates to state resuming methods and apparatuses, a device and a storage medium. A state resuming method comprises: sending a first request message to a core network device; and receiving a first response message sent by the core network device, the first response message being used for indicating context information of a terminal. In the described embodiments, a first access network device sends request information to the core network device to request the context information of the terminal from a second access network device, so that the core network device can request the context of the terminal from the first access network device, and so as to resume, on the basis of the context information of the terminal, the state of RRC connection between the terminal and the first access network device to an RRC connected state. In this way, the RRC connected state of the terminal can be resumed by means of forwarding via the core network device, thereby expanding ways for terminals to resume the RRC connected state, and improving stability of terminals resuming the RRC connected state.

Description

State recovery methods, devices, systems, storage media, and software products Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to state recovery methods, devices, systems, storage media, and program products. Background Technology

[0002] With the rapid development of communication technology, in order to reduce air interface signaling and quickly restore wireless connections, and thus quickly restore data services, a new state has been added to radio resource control (RRC) based on the existing RRC idle state (RRC_IDLE) and RRC connected state (RRC_CONNECTED), namely the RRC inactive state (RRC_INACTIVE). Summary of the Invention

[0003] This application solves the problem of how two access networks cannot communicate directly, and achieves the effect of restoring the RRC connection state between the terminal and the first access network device to the RRC connection state by using the core network device as a relay.

[0004] This disclosure provides a state recovery method, apparatus, system, storage medium, and program product.

[0005] According to a first aspect of the present disclosure, a state recovery method is provided, the method being performed by a first access network device, the method comprising:

[0006] Send a first request message to the core network device. The first request message is used to request the context information of the terminal from the second access network device. The context information is used to restore the state of the Radio Resource Control (RRC) connection between the terminal and the first access network device to the RRC connection state.

[0007] Receive the first response message sent by the core network device.

[0008] According to a second aspect of the present disclosure, a state recovery method is provided, the method being performed by a core network device, the method comprising:

[0009] The system receives a first request message sent by a first access network device. The first request message is used to request context information of the terminal from a second access network device. The context information is used to restore the state of the Radio Resource Control (RRC) connection between the terminal and the first access network device to the RRC connection state.

[0010] Receive the first response message sent by the core network device.

[0011] According to a third aspect of the present disclosure, a state recovery method is provided, the method being performed by a second access network device, the method comprising:

[0012] The terminal receives a third request message sent by the core network device. The third request message is used to request the context information of the terminal. The context information is used to restore the state of the Radio Resource Control (RRC) connection between the terminal and the first access network device to the RRC connection state.

[0013] Send a third response message to the core network device.

[0014] According to a fourth aspect of the present disclosure, a state recovery apparatus is provided, the apparatus comprising:

[0015] The transceiver module is used to send a first request message to the core network device. The first request message is used to request the context information of the terminal from the second access network device. The context information is used to restore the state of the Radio Resource Control (RRC) connection between the terminal and the first access network device to the RRC connection state.

[0016] The transceiver module is also used to receive the first response message sent by the core network device.

[0017] According to a fifth aspect of the present disclosure, a state recovery apparatus is provided, the apparatus comprising:

[0018] The transceiver module is used to receive a first request message sent by a first access network device. The first request message is used to request context information of the terminal from a second access network device. The context information is used to restore the state of the Radio Resource Control (RRC) connection between the terminal and the first access network device to the RRC connection state.

[0019] The transceiver module is also used to receive the first response message sent by the core network device.

[0020] According to a sixth aspect of the present disclosure, a state recovery apparatus is provided, the apparatus comprising:

[0021] The transceiver module is used to receive a third request message sent by the core network device. The third request message is used to request the context information of the terminal. The context information is used to restore the state of the Radio Resource Control (RRC) connection between the terminal and the first access network device to the RRC connection state.

[0022] The transceiver module is also used to send a third response message to the core network device.

[0023] According to a seventh aspect of the present disclosure, a communication device is provided for performing a state recovery method as described in the first, second, or third aspect.

[0024] According to an eighth aspect of the present disclosure, a state recovery method is proposed for a communication system, the communication system including a first access network device, a core network device, and a second access network device, wherein the first access network device is configured to implement the state recovery method as described in the first aspect, the core network device is configured to implement the state recovery method as described in the second aspect, and the second access network device is configured to implement the state recovery method as described in the third aspect.

[0025] According to a ninth aspect of the present disclosure, a communication system is provided, including at least one of a first access network device, a core network device, and a second access network device, wherein the first access network device is configured to implement the state recovery method as described in the first aspect, the core network device is configured to implement the state recovery method as described in the second aspect, and the second access network device is configured to implement the state recovery method as described in the third aspect.

[0026] According to a tenth aspect of the present disclosure, a storage medium is provided that stores instructions that, when executed on a communication device, cause the communication device to perform a state recovery method as described in the first, second, or third aspect.

[0027] According to an eleventh aspect of the present disclosure, a program product is provided, including at least one of a program and instructions, wherein when the program or instructions are executed by a communication device, they implement the state recovery method as described in the first, second, or third aspect.

[0028] In the above embodiments, the RRC connection state between the terminal and the first access network device is restored by using the core network device as a relay, thereby improving the stability of the terminal's ability to restore the RRC connection. Attached Figure Description

[0029] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

[0030] Figure 1 is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0031] Figure 2A is an interactive schematic diagram of a state recovery method according to an embodiment of the present disclosure.

[0032] Figure 2B is an interactive schematic diagram of a state recovery method according to an embodiment of the present disclosure.

[0033] Figure 2C is an interactive schematic diagram of a state recovery method according to an embodiment of the present disclosure.

[0034] Figure 2D is an interactive schematic diagram of a state recovery method according to an embodiment of the present disclosure.

[0035] Figure 3A is a flowchart illustrating a state recovery method according to an embodiment of the present disclosure.

[0036] Figure 3B is a flowchart illustrating a state recovery method according to an embodiment of the present disclosure.

[0037] Figure 3C is a flowchart illustrating a state recovery method according to an embodiment of the present disclosure.

[0038] Figure 4 is a flowchart illustrating a state recovery method according to an embodiment of the present disclosure.

[0039] Figure 5A is a schematic diagram of the structure of the first access network device proposed in an embodiment of this disclosure.

[0040] Figure 5B is a schematic diagram of the core network device proposed in an embodiment of this disclosure.

[0041] Figure 5C is a schematic diagram of the structure of the second access network device proposed in an embodiment of this disclosure.

[0042] Figure 6A is a schematic diagram of the structure of the communication device proposed in an embodiment of this disclosure.

[0043] Figure 6B is a schematic diagram of the chip structure proposed in an embodiment of this disclosure. Detailed Implementation

[0044] This disclosure provides a state recovery method, apparatus, system, storage medium, and program product.

[0045] In a first aspect, embodiments of this disclosure propose a state recovery method, which is executed by a first access network device, the method comprising:

[0046] Send a first request message to the core network device. The first request message is used to request the context information of the terminal from the second access network device. The context information is used to restore the state of the Radio Resource Control (RRC) connection between the terminal and the first access network device to the RRC connection state.

[0047] Receive the first response message sent by the core network device.

[0048] In the above embodiments, the first access network device sends a request message to the core network device to request the terminal's context information from the second access network device. Then, the core network device can request the terminal's context from the first access network device so that the RRC connection state between the terminal and the first access network device can be restored to the RRC connection state based on the terminal's context information. This realizes that the terminal's RRC connection state can be restored by forwarding through the core network device, expands the ways for the terminal to restore the RRC connection state, and improves the stability of the terminal's RRC connection state restoration.

[0049] In conjunction with some embodiments of the first aspect, in some embodiments, sending the first request message to the core network device includes:

[0050] There is no interface connection between the first access network device and the second access network device, so the first request message is sent to the core network device.

[0051] In the above embodiments, the first access network device sends a request message to the core network device to request the terminal's context information from the second access network device. Then, the core network device can return the terminal's context to the first access network device so that the RRC connection state between the terminal and the first access network device can be restored to the RRC connection state based on the terminal's context information. This breaks the limitation that the terminal can restore the RRC connection state even when there is no connection between the first access network device and the second access network device, and improves the stability of the terminal restoring the RRC connection state.

[0052] In conjunction with some embodiments of the first aspect, in some embodiments, the first request message includes the access network device identifier of the second access network device;

[0053] The first request message also includes at least one of the following:

[0054] An inactive radio network temporary identifier (I-RNTI) is used to indicate the access network device identifier of the second access network device and the terminal identifier of the terminal.

[0055] The first MAC-I is used to verify the identity of the terminal.

[0056] Reason for connection restoration;

[0057] Serving cell identifier, which is used to calculate the second MAC-I;

[0058] The first access network device has a list of first GPRS tunneling protocol tunnel endpoint identifiers (GTP TEIDs), which are used for data transmission and path switching.

[0059] The second GTP TEID list of the first access network device, the second GTP TEID list is used for data transmission;

[0060] The third GTP TEID list of the first access network device, the third GTP TEID list is used for path switching.

[0061] In the above embodiments, the first request message includes the access network device identifier of the first access network device, so that the core network device can accurately determine the second access network device that needs to obtain the terminal's context, and then subsequently request the second access network device to obtain the terminal's context. Furthermore, the first request information also includes at least one of the following: I-RNTI, first MAC-I, connection recovery reason, serving cell identifier, first GTP TEID list, second GTP TEID list, and third GTP TEID list, ensuring the comprehensiveness of the information carried by the first request information.

[0062] In conjunction with some embodiments of the first aspect, in some embodiments, the first response message includes the context information of the terminal;

[0063] The first response message also includes at least one of the following:

[0064] The first GTP TEID of the first access network device is used for data transmission and associated with a PDU session. The first GTP TEID is at least one GTP TEID in the first GTP TEID list, which is used for data transmission and path switching.

[0065] The second GTP TEID of the first access network device is used for data transmission and associated with a Protocol Data Unit (PDU) session. The second GTP TEID is at least one GTP TEID in the second GTP TEID list, which is used for data transmission.

[0066] The fourth GTP TEID of the core network device, the fourth GTP TEID is used for data transmission and associated with a PDU session, the fourth GTP TEID is at least one GTP TEID in the fourth GTP TEID list of the core network device, the fourth GTP TEID list is used for data transmission.

[0067] In the above embodiments, the first response message includes the terminal's context information, so that the RRC connection state that can be restored with the terminal can be determined based on the terminal's context information, ensuring the stability of the terminal's restored RRC connection state. Furthermore, the first response information also includes at least one of a first GTP TEID, a second GTP TEID, and a fourth GTP TEID, ensuring the comprehensiveness of the information carried by the first response information.

[0068] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0069] The receiving terminal sends a second request message, which requests that the state of the RRC connection between the terminal and the first access network device be restored to the RRC connection state.

[0070] Send a second response message to the terminal.

[0071] In the above embodiment, the first access network device determines that the terminal needs to restore the RRC connection state to the RRC connection state by requesting information. Then, it can determine the state of the RRC connection between the terminal and the first access network device to the RRC connection state by responding information, thus realizing the effect that the terminal can be restored to the RRC connection state.

[0072] In conjunction with some embodiments of the first aspect, in some embodiments, the second request message includes I-RNTI;

[0073] The second request message also includes at least one of the following:

[0074] First MAC-I;

[0075] Reason for connection restoration.

[0076] In the above embodiments, by carrying an I-RNTI in the second request message to indicate to the access network device that needs to obtain the terminal's context information, it is ensured that the subsequent core network device can request the terminal's context from the first access network device, so as to restore the RRC connection state between the terminal and the first access network device to the RRC connection state based on the terminal's context information. Furthermore, the second request message also includes at least one of a first MAC-I and a connection restoration reason, ensuring the comprehensiveness of the information carried by the first request message.

[0077] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0078] Based on the I-RNTI included in the second request message, the access network device identifier of the second access network device is determined.

[0079] In the above embodiments, since the core network device may be unable to recognize the I-RNTI, the first access network device determines the access network device identifier of the second access network device based on the I-RNTI. Subsequently, the core network device can directly determine the second access network device based on the access network device identifier of the second access network device, ensuring the accuracy of the core network device in finding the second access network device.

[0080] In conjunction with some embodiments of the first aspect, in some embodiments, restoring the state of the RRC connection between the terminal and the first access network device to the RRC connection state includes:

[0081] The state of the RRC connection between the terminal and the first access network device is restored from the RRC inactive state to the RRC connected state.

[0082] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0083] The terminal sends a fourth response message, which indicates that the state of the RRC connection has been restored to the RRC connection state.

[0084] In the above embodiment, the terminal sends a fourth response message to indicate that the state of the RRC connection has been restored to the RRC connection state, thus ensuring the stability of the restoration to the RRC connection state.

[0085] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0086] Receive a first paging message sent by the core network device, the first paging message being used to page the terminal;

[0087] The first paging message is forwarded to the terminal.

[0088] In the above embodiments, the step of restoring the RRC connection between the terminal and the first access network device to the RRC connection state is triggered by a paging message, ensuring the reliability of triggering the restoration to the RRC connection state.

[0089] In conjunction with some embodiments of the first aspect, in some embodiments, the first paging message includes at least one of the following:

[0090] I-RNTI;

[0091] Access network notification area (RAN-based notification area, RNA);

[0092] Radio access network (RAN) paging container.

[0093] Secondly, embodiments of this disclosure propose a state recovery method, which is executed by a core network device, and the method includes:

[0094] The system receives a first request message sent by a first access network device. The first request message is used to request context information of the terminal from a second access network device. The context information is used to restore the state of the Radio Resource Control (RRC) connection between the terminal and the first access network device to the RRC connection state.

[0095] Send a first response message to the first access network device.

[0096] In conjunction with some embodiments of the second aspect, in some embodiments, the first request message is sent when there is no interface connection between the first access network device and the second access network device.

[0097] In conjunction with some embodiments of the second aspect, in some embodiments, the first request message includes the access network device identifier of the second access network device;

[0098] The first request message also includes at least one of the following:

[0099] I-RNTI;

[0100] First MAC-I;

[0101] Reason for connection restoration;

[0102] Serving cell identifier, which is used to calculate the second MAC-I;

[0103] The first GTP TEID list is used for data transmission and path switching;

[0104] The second GTP TEID list is used for data transmission;

[0105] The third GTP TEID list is used for path switching.

[0106] In conjunction with some embodiments of the second aspect, in some embodiments, the first response message includes the context information of the terminal;

[0107] The first response message also includes at least one of the following:

[0108] The first GTP TEID of the first access network device is used for data transmission and associated with a PDU session. The first GTP TEID is at least one GTP TEID in the first GTP TEID list, which is used for data transmission and path switching.

[0109] The second GTP TEID of the first access network device is used for data transmission and associated with a PDU session. The second GTP TEID is at least one GTP TEID in the second GTP TEID list, which is used for data transmission.

[0110] The fourth GTP TEID of the core network device, the fourth GTP TEID is used for data transmission and associated with a PDU session, the fourth GTP TEID is at least one GTP TEID in the fourth GTP TEID list, the fourth GTP TEID list is used for data transmission.

[0111] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0112] Send a third request message to the second access network device, the third request message being used to request the context information of the terminal;

[0113] Receive the third response message sent by the second access network device.

[0114] In conjunction with some embodiments of the second aspect, in some embodiments, the third request message includes at least one of the following:

[0115] I-RNTI;

[0116] First MAC-I;

[0117] Reason for connection restoration;

[0118] The first GTP TEID list of the first access network device, the first GTP TEID list is used for data transmission and path switching;

[0119] The second GTP TEID list of the first access network device, the second GTP TEID list is used for data transmission;

[0120] The fourth GTP TEID list of the core network equipment, the fourth GTP TEID list is used for data transmission;

[0121] Service area signage.

[0122] In conjunction with some embodiments of the second aspect, in some embodiments, the third response message includes the context information of the terminal.

[0123] The third response message also includes at least one of the following:

[0124] The first GTP TEID of the first access network device is used for data transmission and associated with a PDU session. The first GTP TEID is at least one GTP TEID in the first GTP TEID list, which is used for data transmission and path switching.

[0125] The second GTP TEID of the first access network device is used for data transmission and associated with a PDU session. The second GTP TEID is at least one GTP TEID in the second GTP TEID list, which is used for data transmission.

[0126] The fourth GTP TEID of the core network device, the fourth GTP TEID is used for data transmission and associated with a PDU session, the fourth GTP TEID is at least one GTP TEID in the fourth GTP TEID list of the core network device, the fourth GTP TEID list is used for data transmission.

[0127] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0128] Receive a second paging message sent by a second access network device, the second paging message being used to page the terminal;

[0129] Send a first paging message to the first access network device.

[0130] In conjunction with some embodiments of the second aspect, in some embodiments, the second paging message includes at least one of the following:

[0131] List of access network devices for the first access network device;

[0132] RNA;

[0133] Access Network RAN ​​Paging Container;

[0134] I-RNTI.

[0135] In conjunction with some embodiments of the second aspect, in some embodiments, the first paging message includes at least one of the following:

[0136] I-RNTI;

[0137] RNA;

[0138] Access network RAN ​​paging container.

[0139] Thirdly, embodiments of this disclosure propose a state recovery method, which is executed by a second access network device, the method comprising:

[0140] The terminal receives a third request message sent by the core network device. The third request message is used to request the context information of the terminal. The context information is used to restore the state of the Radio Resource Control (RRC) connection between the terminal and the first access network device to the RRC connection state.

[0141] Send a third response message to the core network device.

[0142] In conjunction with some embodiments of the third aspect, in some embodiments, the third request message includes at least one of the following:

[0143] I-RNTI;

[0144] First MAC-I;

[0145] Reason for connection restoration;

[0146] The first GTP TEID list of the first access network device, the first GTP TEID list is used for data transmission and path switching;

[0147] The second GTP TEID list of the first access network device, the second GTP TEID list is used for data transmission;

[0148] The fourth GTP TEID list of the core network equipment, the fourth GTP TEID list is used for data transmission;

[0149] Service area signage.

[0150] In conjunction with some embodiments of the third aspect, in some embodiments, the method further includes:

[0151] The second MAC-I is determined based on the serving cell identifier;

[0152] The second MAC-I is the same as the first MAC-I, thus determining that the terminal is a compliant terminal.

[0153] In conjunction with some embodiments of the third aspect, in some embodiments, the third response message includes the context information of the terminal.

[0154] The third response message also includes at least one of the following:

[0155] The first GTP TEID of the first access network device is used for data transmission and associated with a PDU session. The first GTP TEID is at least one GTP TEID in the first GTP TEID list, which is used for data transmission and path switching.

[0156] The second GTP TEID of the first access network device is used for data transmission and associated with a PDU session. The second GTP TEID is at least one GTP TEID in the second GTP TEID list, which is used for data transmission.

[0157] The fourth GTP TEID of the core network device, the fourth GTP TEID is used for data transmission and associated with a PDU session, the fourth GTP TEID is at least one GTP TEID in the fourth GTP TEID list of the core network device, the fourth GTP TEID list is used for data transmission.

[0158] In conjunction with some embodiments of the third aspect, in some embodiments, the method further includes:

[0159] Receive downlink information;

[0160] A second paging message is sent to the core network equipment, the second paging message being used to page the terminal.

[0161] In conjunction with some embodiments of the third aspect, in some embodiments, the second paging message includes at least one of the following:

[0162] List of access network devices for the first access network device;

[0163] RNA;

[0164] Access Network RAN ​​Paging Container;

[0165] I-RNTI.

[0166] In conjunction with some embodiments of the third aspect, in some embodiments, the method further includes:

[0167] Send configuration information to the terminal, the configuration information being used to configure the terminal to enter the RRC inactive state.

[0168] In conjunction with some embodiments of the third aspect, in some embodiments, the configuration information includes at least one of the following:

[0169] Area information of at least one cell of the first access network device;

[0170] The area information of at least one cell of the second access network device.

[0171] In the above embodiments, the terminal is configured to enter the RRC inactive state by configuring the configuration information, and the regional information of the first access network device and the second access network device can also be configured for the terminal to facilitate the determination of the coverage area of ​​the first access network device and the second access network device, so as to ensure the accuracy of the terminal in determining the coverage area of ​​the first access network device and the second access network device.

[0172] Fourthly, embodiments of this disclosure provide a state recovery apparatus, the apparatus comprising:

[0173] The transceiver module is used to send a first request message to the core network device. The first request message is used to request the context information of the terminal from the second access network device. The context information is used to restore the state of the Radio Resource Control (RRC) connection between the terminal and the first access network device to the RRC connection state.

[0174] The transceiver module is also used to receive the first response message sent by the core network device.

[0175] Fifthly, embodiments of this disclosure provide a state recovery device, the device comprising:

[0176] The transceiver module is used to receive a first request message sent by a first access network device. The first request message is used to request context information of the terminal from a second access network device. The context information is used to restore the state of the Radio Resource Control (RRC) connection between the terminal and the first access network device to the RRC connection state.

[0177] The transceiver module is also used to send a first response message to the first access network device.

[0178] Sixthly, embodiments of this disclosure provide a state recovery apparatus, the apparatus comprising:

[0179] The transceiver module is used to receive a third request message sent by the core network device. The third request message is used to request the context information of the terminal. The context information is used to restore the state of the Radio Resource Control (RRC) connection between the terminal and the first access network device to the RRC connection state.

[0180] The transceiver module is also used to send a third response message to the core network device.

[0181] In a seventh aspect, embodiments of this disclosure provide a communication device for performing the state recovery method as described in the first, second, or third aspect.

[0182] Eighthly, a communication system is proposed, comprising at least one of a first access network device, a core network device, and a second access network device, wherein the first access network device is configured to implement the state recovery method as described in the first aspect, the core network device is configured to implement the state recovery method as described in the second aspect, and the second access network device is configured to implement the state recovery method as described in the third aspect.

[0183] In a ninth aspect, embodiments of this disclosure provide a state recovery method for a communication system, the communication system including a first access network device, a core network device, and a second access network device, wherein the first access network device is configured to implement the state recovery method as described in the first aspect, the core network device is configured to implement the state recovery method as described in the second aspect, and the second access network device is configured to implement the state recovery method as described in the third aspect.

[0184] In a tenth aspect, a storage medium is proposed that stores instructions that, when executed on a communication device, cause the communication device to perform a state recovery method as described in the first, second, or third aspect.

[0185] In the eleventh aspect, a program product is proposed, comprising at least one of a program and instructions, wherein when the program or instructions are executed by a communication device, they implement the state recovery method as described in the first, second, or third aspect.

[0186] It is understood that the aforementioned communication equipment, communication system, storage medium, program product, etc., are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0187] This disclosure provides embodiments of a state recovery method, apparatus, system, storage medium, and program product. In some embodiments, the terms state recovery method, recovery method, communication method, processing method, etc., may be used interchangeably.

[0188] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments. In all embodiments of this disclosure, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0189] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0190] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0191] In the embodiments disclosed herein, "multiple" refers to two or more.

[0192] In some embodiments, the terms "at least one of A or B, at least one of A and B", "one or more", "a plurality of", "multiple" and the like can be used interchangeably.

[0193] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.

[0194] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.

[0195] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0196] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0197] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.

[0198] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.

[0199] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0200] In some embodiments, devices, etc., may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. Terms such as “device,” “equipment,” “circuit,” “network element,” “network function,” “network device,” “function,” “node,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” are interchangeable.

[0201] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0202] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0203] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.

[0204] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0205] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0206] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0207] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0208] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0209] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0210] As shown in Figure 1, the communication system 100 includes a terminal 101, a first access network device 102, a core network device 103, and a second access network device 104.

[0211] In some embodiments, terminal 101 includes, for example, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home, but is not limited thereto.

[0212] In some embodiments, the first access network device 102 and the second access network device 104 are, for example, nodes or devices that connect terminals to a wireless network. The access network devices may include at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), wireless backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system, but are not limited thereto.

[0213] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0214] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0215] In some embodiments, a core network device may be a single device comprising one or more network elements, or it may be multiple devices or a group of devices, each comprising all or part of the aforementioned one or more network elements. Network elements may be virtual or physical. The core network may include, for example, at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC).

[0216] In some embodiments, the core network equipment includes an authentication management function (AMF) network element, which is responsible for user access and mobility management, and handles user equipment access requests, mobility management, and radio resource allocation.

[0217] In some embodiments, the core network device includes a session management function (SMF) network element, which is responsible for user session management, including session establishment, maintenance and release, and supports network slicing function.

[0218] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0219] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1 are illustrative. The communication system may include all or some of the main bodies in FIG1, or may include other main bodies outside of FIG1. ​​The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0220] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0221] In some embodiments of a 5G network environment, to reduce air interface signaling and quickly restore wireless connectivity and data services, a new RRC state is defined: the RRC inactive state (RRC_INACTIVE). This state is distinct from the RRC idle state (RRC_IDLE) and the RRC active state (RRC_ACTIVE).

[0222] The following is a description of each state involved in this application.

[0223] RRC_IDLE: Mobility is based on terminal-based cell selection or cell reselection. In some embodiments, if the terminal is in the RRC_IDLE state, the core network equipment needs to initiate paging of the terminal, and the paging area is configured by the core network equipment. Additionally, the access network equipment does not possess the terminal's AS context information, and there is no RRC connection between the access network equipment and the terminal.

[0224] RRC_CONNECTED: An RRC connection exists between the terminal and the access network device. The access network device and the terminal share the terminal's AS context. The access network device determines the terminal's location at the cell level. Furthermore, mobility is network-side controlled mobility. Unicast data can be transmitted between the terminal and the access network device.

[0225] RRC_INACTIVE: Mobility is based on terminal-based cell selection or cell reselection, and there is a connection between the terminal and the core network equipment. The terminal's AS context information exists on a certain access network device. In addition, terminal paging is triggered by the access network equipment, and the RAN paging area is managed by the access network equipment. The network side knows the terminal's location at the RAN paging area level.

[0226] When the terminal is in the RRC_INACTIVE state, the network side configures a RAN paging area for the terminal via dedicated signaling. This RAN paging area can be one or more cells. When the terminal moves within this RAN paging area, it does not need to notify the network side and follows the mobility behavior under idle state, i.e., cell selection or cell reselection principles. When the terminal moves out of the RAN paging area configured by the RAN, it triggers the terminal to restore the RRC connection and reacquire the RAN paging area configured by the RAN. When downlink data arrives at the terminal, the access network equipment that maintains the connection between the access network equipment and the core network equipment will trigger all cells within the RAN paging area to send paging messages to the terminal, enabling the terminal in the INACTIVE state to restore the RRC connection state and receive data.

[0227] Therefore, there are three possibilities when a terminal transitions from the RRC inactive state to the RRC connected state:

[0228] First, when downlink data arrives at the terminal, the network side initiates an initial paging process on the RAN, prompting the terminal to enter the connected state.

[0229] Second, the terminal itself initiates RAN location area updates, such as periodic RAN location updates or cross-regional location updates.

[0230] Third, the terminal has an uplink data transmission requirement, which prompts the terminal to enter the RRC connection state.

[0231] In some embodiments, the RRC connection recovery process in NR is as follows:

[0232] In some embodiments, the triggering reasons include the following: For terminals in the RRC inactive state, this process is triggered when uplink data arrives, or when the periodic RAN-based notification area update (RNAU) timer expires, or when an initial RAN paging is received.

[0233] In some embodiments, the RRC connection can be restored to the RRC active state.

[0234] First, the RRC connection restoration request: The terminal sends this message on the signaling radio bearer 0 (SRB0) via the uplink control channel (UL_CCCH), carrying the terminal's AS layer initial identification information, a short MAC-I, and the reason for restoration. This message corresponds to Message3 (Msg3) in the random access procedure. After sending this message, the terminal activates security, generates a key, and resumes SRB1 to wait for MSG4.

[0235] Secondly, RRC connection recovery: the gNB replies on SRB1 via DL_DCCH, which corresponds to Msg4 in the random access procedure. MSG4 is encrypted and protected for integrity.

[0236] Finally, the RRC connection restoration is completed: the UE sends a message on SRB1 via UL-DCCH without carrying any actual information, only serving as an RRC layer confirmation function.

[0237] In some embodiments, the RRC connection state is restored to the RRC inactive state.

[0238] If the gNB decides to release the terminal to the RRC inactive state (e.g., periodic RNAU) after receiving the RRC connection restoration request message, the base station carries an RRC release message in the MSG4 message to update the INACTIVE configuration parameters.

[0239] In some embodiments, the RRC connection state is restored to the RRC idle state.

[0240] Optionally, if the gNB decides to release the terminal to the RRC idle state after receiving the RRC connection restoration request message, the base station carries the RRC Release message in the MSG4 message.

[0241] For example, the above situation may be caused by at least one of the following reasons: RRC connection recovery failure, RRC connection recovery request timer T319 timeout, RRC connection recovery message (MSG4) integrity protection verification failure, or cell reselection occurring during T310 operation.

[0242] If the RRC connection reconstruction fails due to the above reasons, the terminal will return to the RRC idle state.

[0243] In some embodiments, if the UE's context information is not in the gNB, an RRC connection re-establishment message is replied on SRB0 via DL_CCCH. Upon receiving this message, the terminal deletes the previous context and executes the RRC connection establishment procedure.

[0244] In some embodiments, an RRC Reject message is received, for example, due to network load control reasons. At this point, the terminal returns to the initial RRC_INACTIVE state.

[0245] Figure 2A is an interactive schematic diagram of a state recovery method according to an embodiment of the present disclosure. As shown in Figure 2A, the embodiments of the present disclosure relate to a state recovery method, which includes:

[0246] Step S2101: The terminal sends a second request message to the first access network device.

[0247] In some embodiments, the first access network device receives a second request message sent by the terminal. Alternatively, the terminal sends a second request message, and the first access network device receives the second request message.

[0248] In some embodiments, the first access network device is the access network device currently providing services to the terminal, or it can be said that the first access network device is the terminal's serving access network device. For example, the first access network device is a service gNB.

[0249] In some embodiments, the second request message is used to request that the state of the RRC connection between the terminal and the first access network device be restored to the RRC connection state. In this embodiment of the present disclosure, if the terminal determines that it needs to restore the state of the RRC connection between the terminal and the first access network device to the RRC connection state, it sends a second request message to the first access network device to request that the state of the RRC connection between the terminal and the first access network device be restored to the RRC connection state.

[0250] Optionally, restoring the RRC connection between the terminal and the first access network device to the RRC connected state includes: restoring the RRC connection between the terminal and the first access network device from the RRC inactive state to the RRC connected state. For example, if the terminal is currently in the RRC inactive state, and the terminal determines that it needs to switch from the RRC inactive state to the RRC connected state, it indicates that the terminal needs to restore the RRC connection. Therefore, the terminal can send a second request message to the first access network device to instruct the terminal to restore the RRC connection between the terminal and the first access network device to the RRC connected state.

[0251] In some embodiments, the second request message includes an I-RNTI. This I-RNTI is used to indicate the access network device identifier of the second access network device and the terminal identifier of the terminal. Alternatively, the I-RNTI can be understood as including the access network device identifier of the second access network device and the terminal identifier of the terminal. Alternatively, the I-RNTI is determined based on the access network device identifier of the second access network device and the terminal identifier of the terminal. Furthermore, the I-RNTI refers to an identifier used to uniquely identify the terminal in the RRC inactive state. This I-RNTI is assigned to the terminal by the second access network device. The second access network device refers to the access network device that provides services to the terminal before the terminal enters the RRC inactive state.

[0252] In addition, the second request message may include at least one of the following: a first MAC-I, and a reason for connection recovery. Wherein:

[0253] The first MAC-I is used to verify the identity of the terminal. Optionally, the terminal can calculate the second MAC-I based on the serving cell identifier. If the calculated second MAC-I is the same as the first MAC-I, it indicates that the terminal is a legitimate terminal.

[0254] The connection restoration reason indicates why the terminal resumed the connection. For example, the connection restoration reason may include the terminal initiating a RAN location area update. This RAN location area update includes periodic RAN location updates or cross-region location updates. Another example is that the connection restoration reason may include the terminal having an uplink data transmission requirement, prompting the terminal to enter the RRC connected state. Optionally, the connection restoration reason can be represented as a resume cause. The serving cell identifier is represented as the current serving cell ID. For example, the serving cell identifier includes the first PLMN and the cell identifier.

[0255] In some embodiments, the second request message may be an RRC recovery request (RRCResumeRequest), which is used to trigger the RRC connection recovery process. For example, the RRCesumeRequest may include an I-RNTI, and may also include at least one of a first MAC-I and a recovery cause.

[0256] It should be noted that, prior to the above steps, the second access network device may also send configuration information to the terminal, instructing the terminal to enter the RRC inactive state. Optionally, the configuration information includes at least one of the following: area information of at least one cell of the first access network device; area information of at least one cell of the second access network device. In some embodiments, the area information of at least one cell of the first access network device; the area information of at least one cell of the second access network device may also be indicated by RNA, or the RNA in the configuration information includes the area information of at least one cell of the first access network device.

[0257] In step S2102, the first access network device determines the access network device identifier of the second access network device based on the second request message.

[0258] In some embodiments, the first access network device determines the access network device identifier of the second access network device based on the I-RNTI included in the second request message.

[0259] In this embodiment of the disclosure, the I-RNTI is used to indicate the access network device identifier of the second access network device, and therefore the access network device identifier of the second access network device can be determined based on the I-RNTI. Optionally, the second access network device refers to an anchor gNB. The access network device identifier of the second access network device is represented by the anchor gNB ID.

[0260] In some embodiments, the second access network device refers to an access network device that stores the context information of the terminal.

[0261] It should be noted that the core network device needs to determine the second access network device from the first request message received by the first access network device, and then send a third request message to the second access network device. Since the core network device may not be able to recognize the I-RNTI, while the first access network device can, the first access network device can determine the access network device identifier of the second access network device based on the I-RNTI and then send the access network device identifier of the second access network device to the core network device, so that the core network device can directly identify the second access network device based on the access network device identifier of the second access network device.

[0262] It should be noted that step S2102 is an optional step. In another embodiment, step S2102 may not be executed. In this case, the first request message sent by the first access network device will not include the access network device identifier of the second access network device.

[0263] Step S2103: The first access network device sends a first request message to the core network device.

[0264] In some embodiments, the core network device receives a first request message sent by a first access network device. Correspondingly, the core network device receives the first request message.

[0265] In some embodiments, the first request message is used to request context information of the terminal from the second access network device. The context information is used to restore the RRC connection state between the terminal and the first access network device to the RRC connected state. In this embodiment, the second access network device is the access network device that instructs the terminal to enter the RRC inactive state, and it is also the last second access network device to provide services before the terminal enters the RRC inactive state. Therefore, the second access network device stores the terminal's context information, and the first access network device can request the terminal's context information from the second access network device through a core network device as an intermediary.

[0266] In some embodiments, there is no interface connection between the first access network device and the second access network device, and a first request message is sent to the core network device. Optionally, the interface connection refers to a connection implemented through the Xn interface. The Xn interface is used to connect the two access network devices. For example, this interface connection can also be referred to as an Xn physical connection or an Xn logical connection. Alternatively, it can also be referred to as an Xn connection.

[0267] In this embodiment of the disclosure, since there is no interface connection between the first access network device and the second access network device, they cannot communicate directly. Therefore, the first access network device and the second access network device communicate through the core network device as a relay. Thus, the first access network device can send a first request message to the core network device, and subsequently, the core network device can send a third request message to the second access network device based on the first request message.

[0268] In some embodiments, the first request message includes an access network device identifier of the second access network device. In this embodiment, after receiving the first request message, the core network device can determine the second access network device based on the access network device identifier included in the first request message, and subsequently request the terminal's context information from the second access network device.

[0269] In addition, the first request message also includes at least one of the following:

[0270] (1) I-RNTI, I-RNTI is used to indicate the access network device identifier of the second access network device and the terminal identifier of the terminal.

[0271] (2) First MAC-I, the first MAC-I is used to verify the identity of the terminal.

[0272] (3) Reasons for connection restoration;

[0273] (4) Serving cell identifier, which is used to calculate the second MAC-I.

[0274] (5) The first GTP TEID list of the first access network device.

[0275] The first GTP TEID list is used for data transmission and path switching. In this embodiment, the first GTP TEID list is used for both data transmission and path switching; it can be understood as having two functions: data transmission and path switching. For example, data transmission is represented by data forwarding, and path switching is represented by path switching.

[0276] In some embodiments, the first GTP TEID list includes one or more GTP TEIDs, each GTP TEID being used to identify a tunnel used for data transmission and also for path switching.

[0277] In this embodiment of the disclosure, the first GTP TEID list includes one or more GTP TEIDs for selection by the second access network device. The second access network device selects a GTP TEID from the first GTP TEID list to facilitate data transmission based on the selected GTP TEID.

[0278] In some embodiments, the first GTP TEID list may also be referred to as the gNB GTP TEID list, that is, the GTP TEID list is a list corresponding to the access network devices.

[0279] For example, in this embodiment of the disclosure, the first GTP TEID list is represented by the first GTP TEID list.

[0280] (6) The second GTP TEID list of the first access network device.

[0281] The second GTP TEID list is used for data transmission. In this embodiment of the disclosure, the second GTP TEID list is used for data transmission, which can also be understood as the second GTP TEID list having a function of transmitting data.

[0282] In some embodiments, the second GTP TEID list includes one or more GTP TEIDs, each GTP TEID identifying a tunnel used for data transmission. In embodiments of this disclosure, the second GTP TEID list includes one or more GTP TEIDs for selection by a second access network device, which selects a GTP TEID from the second GTP TEID list to facilitate data transmission based on the selected GTP TEID.

[0283] In some embodiments, the second GTP TEID list may also be referred to as the gNB GTP TEID list, that is, the GTP TEID list is a list corresponding to the access network devices.

[0284] (7) The third GTP TEID list of the first access network device, which is used for path switching.

[0285] The third GTP TEID list is used for path switching. In this embodiment of the disclosure, the third GTP TEID list is used for path switching, which can also be understood as the third GTP TEID list having a function of performing path switching.

[0286] In some embodiments, the third GTP TEID list may also be referred to as a GTP TEID list including one or more GTP TEIDs, each GTP TEID being used to identify a tunnel used for path switching.

[0287] In some embodiments, the third gNB GTP TEID list, that is, the GTP TEID list, is a list corresponding to access network devices.

[0288] In some embodiments, the first request message may be a UEcontextRetrievalrequest. This UEcontextRetrievalrequest is used to request the acquisition of the terminal's context information. For example, the UEcontextRetrievalrequest includes the anchorgNB ID, I-RNTI, and may also include at least one of MAC-I, resume cause, current serving cellID, and GTP TEIDlist. The GTP TEIDlist includes a serving gNB GTP TEID list or range for data forwarding and a serving gNB GTP TEID list or range for path switching.

[0289] In step S2104, the core network device sends a third request message to the second access network device.

[0290] In some embodiments, the second access network device receives a third request message sent by the core network device. In some embodiments, the core network device sends a third request message, and the second access network device receives the third request message.

[0291] In some embodiments, the third request message is used to request context information of the terminal. In this embodiment, since the context information of the terminal is required to restore the RRC connection state between the terminal and the first access network device to the RRC connected state, the core network device sends a third request message to the second access network device to request the context information of the terminal when it determines that the first access network device needs the context information of the terminal.

[0292] In some embodiments, the third request message includes at least one of the following:

[0293] (1) I-RNTI;

[0294] (2) First MAC-I;

[0295] (3) Reasons for connection restoration;

[0296] (4) The first GTP TEID list of the first access network device, the first GTP TEID list is used for data transmission and path switching;

[0297] (5) The second GTP TEID list of the first access network device, which is used for data transmission.

[0298] (6) The fourth GTP TEID list of core network equipment.

[0299] The fourth GTP TEID list is used for data transmission. In this embodiment, the fourth GTP TEID list is used for data transmission; it can also be understood that the fourth GTP TEID list has a function of transmitting data.

[0300] In some embodiments, the fourth GTP TEID list includes one or more GTP TEIDs, each GTP TEID identifying a tunnel used for data transmission. In embodiments of this disclosure, the fourth GTP TEID list includes one or more GTP TEIDs for selection by a second access network device, which selects a GTP TEID from the fourth GTP TEID list to facilitate data transmission based on the selected GTP TEID.

[0301] In some embodiments, the fourth GTP TEID list may also be referred to as the fourth core network GTP TEID list, that is, the GTP TEID list is a list corresponding to core network devices.

[0302] (7) Service area signage.

[0303] In some embodiments, the third request message may be a UEcontextRetrievalrequest. For example, the UEcontextRetrievalrequest may include at least one of I-RNTI, MAC-I, resume cause, servinggNBGTP TEIDlist or servinggNBGTP TEIDlistfordataforwarding, AMFGTP TEIDlist fordataforwarding, and current serving cellID.

[0304] In step S2105, the second access network device determines the second MAC-I based on the third request message.

[0305] In some embodiments, the second access network device determines the second MAC-I based on the serving cell identifier in the third request message.

[0306] In this embodiment of the disclosure, after the second access network device receives the third request message, it can determine the need to provide the context information of the terminal based on the third request information. However, before feeding back the context information of the terminal, it is necessary to determine whether the terminal is compliant. The first MAC-I in the third request message is used to determine whether the terminal is legitimate.

[0307] In some embodiments, the second MAC-I is the same as the first MAC-I, determining that the terminal is a compliant terminal.

[0308] In some embodiments, the second access network device may also determine which terminal's context information needs to be obtained based on the I-RNTI included in the third request message.

[0309] It should be noted that step S2105 in this embodiment is an optional step, and in another embodiment, step S2105 may not be performed.

[0310] It should be noted that step S2105 in this embodiment is described with the second access network device as the execution subject. In another embodiment, step S2105 may be executed by the core network device instead of the second access network device.

[0311] In step S2106, the second access network device sends a third response message to the core network device.

[0312] In some embodiments, the core network device receives a third response message sent by the second access network device. In some embodiments, the second access network device sends a third response message, and correspondingly, the core network device receives the third response message.

[0313] In some embodiments, the third response message is used to indicate context information. This context information is the context information of the terminal to which the third request message was requested.

[0314] In some embodiments, the third response message includes context information about the terminal.

[0315] The third response message also includes at least one of the following:

[0316] (1) The first GTP TEID of the first access network device, the first GTP TEID is used for data transmission and associated with a PDU session, the first GTP TEID is at least one GTP TEID in the first GTP TEID list, the first GTP TEID list is used for data transmission and path switching.

[0317] (2) The second GTP TEID of the first access network device, the second GTP TEID is used for data transmission and associated with a PDU session, the second GTP TEID is at least one GTP TEID in the second GTP TEID list, the second GTP TEID list is used for data transmission.

[0318] (3) The fourth GTP TEID of the core network device. The fourth GTP TEID is used for data transmission and associated with a PDU session. The fourth GTP TEID is at least one GTP TEID in the fourth GTP TEID list of the core network device. The fourth GTP TEID list is used for data transmission.

[0319] In some embodiments, the third response message may be a UE context Retrieval response. The UE context Retrieval response is used to provide context information about the terminal. For example, the UE context Retrieval response may include at least one of the following:

[0320] At least one AMF GTP TEID is selected from the AMF GTP TEID list, and each AMF GTP TEID is associated with a PDUsessionID, wherein the selected AMF GTP TEID is used for data forwarding;

[0321] At least one serving gNB GTP TEID is selected from the Serving gNB GTP TEID list, and each serving gNB GTP TEID is associated with a PDUsessionID;

[0322] Terminal context information.

[0323] In step S2107, the core network device sends a first response message to the first access network device.

[0324] In some embodiments, the first access network device receives a first response message sent by the core network device. Correspondingly, the first access network device receives the first response message.

[0325] In some embodiments, the first response message is used to indicate the context information of the terminal. In this embodiment of the disclosure, by indicating the context information of the terminal through the first response message, the first access network device can subsequently obtain the context information of the terminal and restore the RRC connection state between the terminal and the first access network device to the RRC connection state based on the context information of the terminal.

[0326] In some embodiments, the first response message includes context information of the terminal;

[0327] In addition, the first response message includes at least one of the following:

[0328] (1) The first GTP TEID of the first access network device, the first GTP TEID is used for data transmission and associated with a PDU session, the first GTP TEID is at least one GTP TEID in the first GTP TEID list, the first GTP TEID list is used for data transmission and path switching;

[0329] (2) The second GTP TEID of the first access network device, the second GTP TEID is used for data transmission and associated with a PDU session, the second GTP TEID is at least one GTP TEID in the second GTP TEID list, the second GTP TEID list is used for data transmission;

[0330] (3) The fourth GTP TEID of the core network device. The fourth GTP TEID is used for data transmission and associated with a PDU session. The fourth GTP TEID is at least one GTP TEID in the fourth GTP TEID list. The fourth GTP TEID list is used for data transmission.

[0331] In some embodiments, the first response message is represented by UEcontextRetrievalresponse. For example, UEcontextRetrievalresponse includes at least one of the following:

[0332] At least one serving gNB GTP TEID is selected from the Serving gNB GTP TEID list, and each serving gNB GTP TEID is associated with a PDUsessionID. The selected serving gNB GTP TEID is used for data forwarding.

[0333] At least one serving gNB GTP TEID is selected from the Serving gNB GTP TEID list, and each serving gNB GTP TEID is associated with a PDUsessionID. The selected serving gNB GTP TEID is used for path switching. It should be noted that if there is only one serving gNB GTP TEID list, both data forwarding and path switching are selected from this list. If data forwarding and path switching correspond to two lists, then selection is made from their respective lists.

[0334] AMF GTP TEID list, where each AMF GTP TEID is associated with a PDUsessionID. AMF GTP TEIDs are used for path switching;

[0335] Terminal context information.

[0336] In step S2108, the first access network device sends a second response message to the terminal.

[0337] In some embodiments, the terminal receives a second response message sent by the first access network device. Correspondingly, the terminal receives the second response message.

[0338] In some embodiments, the second response message is used to instruct the state of the RRC connection between the terminal and the first access network device to be restored to the RRC connection state. In this embodiment of the disclosure, after receiving the context information of the terminal, the first access network device can restore the state of the RRC connection between the first access network device and the terminal to the RRC connection state.

[0339] In some embodiments, the second response message is represented by RRCResume.

[0340] In step S2109, the terminal sends a fourth response message to the first access network device.

[0341] In some embodiments, the first access network device receives a fourth response message sent by the terminal. In some embodiments, the terminal sends the fourth response message. Correspondingly, the first access network device receives the fourth response message.

[0342] In some embodiments, the fourth response message is used to indicate that the RRC connection has been restored to the RRC connection state.

[0343] In some embodiments, the fourth response message is represented by RRCResumeComplete.

[0344] The following section describes how the first access network device, the core network device (AMF), and the second access network device interact, as shown in Figure 2B.

[0345] Specifically, the terminal sends a second request message (RRCResumeRequest) to the first access network device, and the first access network device sends a first request message (UEcontextRetrievalrequest) to the AMF. The UEcontextRetrievalrequest includes the anchorgNB ID, I-RNTI, resume cause, current serving cell ID, and a GTP TEID list. The GTP TEID list includes a serving gNB GTP TEID list or range for data forwarding and a serving gNB GTP TEID list or range for path switching. The AMF sends a third request message (UEcontextRetrievalrequest) to the second access network device. This message includes I-RNTI, MAC-I, resume cause, serving gNBGTP TEIDlist or serving gNBGTP TEIDlistfordataforwarding, the AMF's GTP TEID list or range for data forwarding (AMFGTP TEIDlist fordataforwarding), and the current serving cellID. The second access network device then sends a third response message (UEcontextRetrievalresponse) to the AMF. This response includes selecting the AMF GTP TEID per PDU session for data forwarding and selecting the gNB GTP TEID per PDU session for data forwarding.The AMF then sends a first response message (UEcontextRetrievalresponse) to the first access network device, including Selected gNB GTP TEID per PDU session for data forwarding, Selected gNB GTP TEID per PDU session for path switching, and AMF GTP TEID per PDU session for path switching. The first access network device sends a second response message (RRCResume) to the terminal, and then the terminal returns a fourth response message (RRCResumeComplete) to the first access network device, thus completing the restoration of the RRC connection.

[0346] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0347] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transmit,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0348] In some embodiments, "acquire," "get," "obtain," "receive," "transmit," "bidirectional transmission," and "send and / or receive" can be used interchangeably and can be interpreted as receiving from other entities, acquiring from protocols, acquiring from higher layers, obtaining through self-processing, or autonomous implementation. Protocols include, for example, at least one of the 3GPP protocol, Wi-Fi protocol, and audio and / or video protocols.

[0349] In some embodiments, the terminal and the network device communicate via a communication protocol specifying at least one of a first parameter, a second parameter, or a third parameter. Therefore, both the terminal and the network device can determine the prefix length and the length of the valid information based on the first parameter, the second parameter, and the third parameter. Alternatively, the communication protocol can also be understood as specifying a particular first parameter, second parameter, or third parameter between the terminal and the network device.

[0350] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0351] In some embodiments, the terminal may also send indication information to the network device to indicate at least one of the first parameter, second parameter, or third parameter used.

[0352] In some embodiments, the network device may send indication information to the terminal to indicate at least one of the first parameter, second parameter, or third parameter used.

[0353] It should be noted that this embodiment uses a terminal as an example to illustrate the execution of steps S2101-S2103. However, in another embodiment, the execution subject of steps S2101-S2103 can also be a network device. Optionally, in this case, the network device used to execute steps S2101-S2103...

[0354] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".

[0355] In some embodiments, the terms “downlink control information (DCI),” “downlink (DL) assignment,” “DL DCI,” “uplink (UL) grant,” and “UL DCI” can be used interchangeably.

[0356] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, as can terms such as "physical uplink shared channel (PUSCH)" and "UL data".

[0357] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

[0358] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “duration,” “segment,” “time window,” “window,” and “time.”

[0359] In some embodiments, the terms "component carrier (CC)," "cell," "frequency carrier," and "carrier frequency" can be used interchangeably.

[0360] In some embodiments, the terms “resource block (RB)”, “physical resource block (PRB)”, “sub-carrier group (SCG)”, “resource element group (REG)”, “PRB pair”, “RB pair”, “resource element (RE)”, and “sub-carrier” can be used interchangeably.

[0361] In some embodiments, terms such as wireless access scheme and waveform can be used interchangeably.

[0362] In some embodiments, the terms "precoding", "precoder", "weight", "precoding weight", "quasi-co-location (QCL)", "transmission configuration indication (TCI) status", "spatial relation", "spatial domain filter", "transmission power", "phase rotation", "antenna port", "antenna port group", "layer", "the number of layers", "rank", "resource", "resource set", "resource group", "beam", "beam width", "beam angular degree", "antenna", "antenna element", and "panel" can be used interchangeably.

[0363] In some embodiments, the terms “frame”, “radio frame”, “subframe”, “slot”, “sub-slot”, “mini-slot”, “symbol”, “symbol”, and “transmission time interval (TTI)” can be used interchangeably.

[0364] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0365] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data and / or instructions received; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the receiver to respond to the sent content.

[0366] In some embodiments, if an arrow in the interaction diagram representing the sending of information, signaling, etc. from one subject to another passes through other subjects, it can be interpreted as the information being forwarded from one subject to another via other subjects, or it can be interpreted as the information being sent from one subject to another without passing through other subjects.

[0367] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2109. For example, at least one of steps S2101 to S2109 may be implemented as an independent embodiment, but is not limited thereto.

[0368] In some embodiments, at least one of steps S2101 to S2109 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0369] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0370] It should be noted that the embodiment in Figure 2A above is illustrated by taking the example of the terminal automatically triggering the restoration of the RRC connection state between itself and the first access network device. In another embodiment, the access network device can also trigger the restoration of the RRC connection state between itself and the first access network device when downlink information arrives. Figure 2C is an interactive schematic diagram of the state restoration method according to an embodiment of this disclosure. As shown in Figure 2C, the embodiment of this disclosure relates to a state restoration method, which includes:

[0371] Step S2201: The second access network device receives downlink information.

[0372] In some embodiments, the downlink information is represented as downlink data (DL data).

[0373] In step S2202, the second access network device sends a second paging message to the core network device.

[0374] In some embodiments, the second paging message is used for paging terminals.

[0375] In some embodiments, the second paging message includes at least one of the following:

[0376] (1) List of access network devices for the first access network device.

[0377] For example, the list of access network devices can be represented as TargetgNBidlist. Alternatively, the list of access network devices can be represented as gNBidlist.

[0378] (2) RNA.

[0379] (3) Access network RAN ​​paging container;

[0380] (4) I-RNTI.

[0381] It should be noted that the second paging message has two forms of expression. For example, the second paging message includes TargetgNBidlist, RNA, and the access network RAN ​​paging container. Another example is that the second paging message includes I-RNTI, gNBidlist, RNA, and other information that paging messages may include.

[0382] In step S2203, the core network device sends a first paging message to the first access network device.

[0383] In some embodiments, the first paging message includes at least one of the following:

[0384] I-RNTI;

[0385] RNA;

[0386] Access network RAN ​​paging container.

[0387] In some embodiments, the first paging message has two forms. For example, the first paging message includes I-RNTI, RNA, and the Access Network RAN ​​paging container. As another example, the second paging message includes I-RNTI, RNA, and other information that the paging message may include.

[0388] Step S2204: The first access network device forwards the first paging message to the terminal.

[0389] In some embodiments, both the first paging message and the second paging message can be represented using RANpagingtransfer.

[0390] In step S2205, the terminal sends a second request message to the first access network device.

[0391] Step S2205 is similar to step S2101 shown in Figure 2A above, and will not be described again here.

[0392] Step S2206: The first access network device determines the access network device identifier of the second access network device based on the second request message.

[0393] Step S2206 is similar to step S2102 shown in Figure 2A above, and will not be described again here.

[0394] Step S2207: The first access network device sends a first request message to the core network device.

[0395] Step S2207 is similar to step S2103 shown in Figure 2A above, and will not be described again here.

[0396] In step S2208, the core network device sends a third request message to the second access network device.

[0397] Step S2208 is similar to step S2104 shown in Figure 2A above, and will not be described again here.

[0398] In step S2209, the second access network device determines the second MAC-I based on the third request message.

[0399] Step S2209 is similar to step S2105 shown in Figure 2A above, and will not be described again here.

[0400] In step S2210, the second access network device sends a third response message to the core network device.

[0401] Step S2210 is similar to step S2106 shown in Figure 2A above, and will not be described again here.

[0402] In step S2211, the core network device sends a first response message to the first access network device.

[0403] Step S2211 is similar to step S2107 shown in Figure 2A above, and will not be described again here.

[0404] In step S2212, the first access network device sends a second response message to the terminal.

[0405] Step S2212 is similar to step S2108 shown in Figure 2A above, and will not be described again here.

[0406] In step S2213, the terminal sends a fourth response message to the first access network device.

[0407] Step S2213 is similar to step S2109 shown in Figure 2A above, and will not be described again here.

[0408] In some embodiments, the paging message transmission process is shown in Figure 2D. When downlink data arrives at the second access network device, the second access network device sends a second paging message (RANpagingtransfer) to the AMF. This RANpagingtransfer includes I-RNTI, RNA, or a target gNB id list, and a RAN paging container. Then, the AMF sends a first paging message (RANpagingtransfer) to the first access network device. This RANpagingtransfer includes I-RNTI, RNA, and a RAN paging container. The first access network device then forwards the first paging message to the terminal, and the terminal subsequently executes the process shown in Figure 2B.

[0409] The communication method involved in the embodiments of this disclosure may include at least one of steps S2201 to S2213. For example, at least one of steps S2201 to S2213 may be implemented as an independent embodiment, but is not limited thereto.

[0410] In some embodiments, at least one of steps S2201 to S2213 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0411] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0412] Figure 3A is a flowchart illustrating a state recovery method according to an embodiment of the present disclosure. As shown in Figure 3A, this disclosure relates to a state recovery method, which includes:

[0413] Step S3101: The first access network device sends a first request message to the core network device.

[0414] Step S3101 is similar to step S2103 shown in Figure 2A above, and will not be described again here.

[0415] In step S3102, the first access network device receives the first response message sent by the core network device.

[0416] Step S3102 is similar to step S2107 shown in Figure 2A above, and will not be described again here.

[0417] In some embodiments, sending the first request message to the core network device includes:

[0418] There is no interface connection between the first access network device and the second access network device, so the first request message is sent to the core network device.

[0419] In some embodiments, the first request message includes the access network device identifier of the second access network device;

[0420] The first request message also includes at least one of the following:

[0421] An inactive wireless network temporary identifier (I-RNTI) is used to indicate the access network device identifier of the second access network device and the terminal identifier of the terminal.

[0422] First identity message verification code MAC-I, the first MAC-I is used to verify the identity of the terminal;

[0423] Reason for connection restoration;

[0424] Serving cell identifier, which is used to calculate the second MAC-I;

[0425] The first GTP TEID list of the first access network device, the first GTP TEID list is used for data transmission and path switching;

[0426] The second GTP TEID list of the first access network device, the second GTP TEID list is used for data transmission;

[0427] The third GTP TEID list of the first access network device, the third GTP TEID list is used for path switching.

[0428] In some embodiments, the first response message includes context information of the terminal;

[0429] The first response message also includes at least one of the following:

[0430] The first GTP TEID of the first access network device is used for data transmission and associated with a PDU session. The first GTP TEID is at least one GTP TEID in the first GTP TEID list, which is used for data transmission and path switching.

[0431] The second GTP TEID of the first access network device is used for data transmission and associated with a PDU session. The second GTP TEID is at least one GTP TEID in the second GTP TEID list, which is used for data transmission.

[0432] The fourth GTP TEID of the core network device, the fourth GTP TEID is used for data transmission and associated with a PDU session, the fourth GTP TEID is at least one GTP TEID in the fourth GTP TEID list of the core network device, the fourth GTP TEID list is used for data transmission.

[0433] In some embodiments, the method further includes:

[0434] The receiving terminal sends a second request message, which requests that the state of the RRC connection between the terminal and the first access network device be restored to the RRC connection state.

[0435] Send a second response message to the terminal.

[0436] In some embodiments, the second request message includes I-RNTI;

[0437] The second request message also includes at least one of the following:

[0438] First MAC-I;

[0439] Reason for connection restoration.

[0440] In some embodiments, the method further includes:

[0441] Based on the I-RNTI included in the second request message, the access network device identifier of the second access network device is determined.

[0442] In some embodiments, restoring the RRC connection state between the terminal and the first access network device to the RRC connection state includes:

[0443] The state of the RRC connection between the terminal and the first access network device is restored from the RRC inactive state to the RRC connected state.

[0444] In some embodiments, the method further includes:

[0445] The terminal sends a fourth response message, which indicates that the RRC connection has been restored to the RRC connection state.

[0446] In some embodiments, the method further includes:

[0447] Receive a first paging message sent by the core network device, the first paging message being used to page the terminal;

[0448] The first paging message is forwarded to the terminal.

[0449] In some embodiments, the first paging message includes at least one of the following:

[0450] I-RNTI;

[0451] Access network notification area RNA;

[0452] Access network RAN ​​paging container.

[0453] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0454] Figure 3B is a flowchart illustrating a state recovery method according to an embodiment of the present disclosure. As shown in Figure 3B, this disclosure relates to a state recovery method, which includes:

[0455] Step S3201: The core network device receives the first request message sent by the first access network device.

[0456] In some embodiments, the first request message is used to request context information of the terminal from the second access network device, and the context information is used to restore the state of the RRC connection between the terminal and the first access network device to the RRC connection state.

[0457] Step S3201 is similar to step S2103 shown in Figure 2A above, and will not be described again here.

[0458] In step S3202, the core network device sends a first response message to the first access network device.

[0459] Step S3202 is similar to step S2107 shown in Figure 2A above, and will not be described again here.

[0460] In some embodiments, the first request message is sent when there is no interface connection between the first access network device and the second access network device.

[0461] In some embodiments, the first request message includes the access network device identifier of the second access network device;

[0462] The first request message also includes at least one of the following:

[0463] I-RNTI;

[0464] First MAC-I;

[0465] Reason for connection restoration;

[0466] Serving cell identifier, which is used to calculate the second MAC-I;

[0467] The first GTP TEID list is used for data transmission and path switching;

[0468] The second GTP TEID list is used for data transmission;

[0469] The third GTP TEID list is used for path switching.

[0470] In some embodiments, the first response message includes context information of the terminal;

[0471] The first response message also includes at least one of the following:

[0472] The first GTP TEID of the first access network device is used for data transmission and associated with a PDU session. The first GTP TEID is at least one GTP TEID in the first GTP TEID list, which is used for data transmission and path switching.

[0473] The second GTP TEID of the first access network device is used for data transmission and associated with a PDU session. The second GTP TEID is at least one GTP TEID in the second GTP TEID list, which is used for data transmission.

[0474] The fourth GTP TEID of the core network device, the fourth GTP TEID is used for data transmission and associated with a PDU session, the fourth GTP TEID is at least one GTP TEID in the fourth GTP TEID list, the fourth GTP TEID list is used for data transmission.

[0475] In some embodiments, the method further includes:

[0476] Send a third request message to the second access network device, the third request message being used to request the context information of the terminal;

[0477] Receive the third response message sent by the second access network device.

[0478] In some embodiments, the third request message includes at least one of the following:

[0479] I-RNTI;

[0480] First MAC-I;

[0481] Reason for connection restoration;

[0482] The first GTP TEID list of the first access network device, the first GTP TEID list is used for data transmission and path switching;

[0483] The second GTP TEID list of the first access network device, the second GTP TEID list is used for data transmission;

[0484] The fourth GTP TEID list of the core network equipment, the fourth GTP TEID list is used for data transmission;

[0485] Service area signage.

[0486] In some embodiments, the third response message includes context information of the terminal.

[0487] The third response message also includes at least one of the following:

[0488] The first GTP TEID of the first access network device is used for data transmission and associated with a PDU session. The first GTP TEID is at least one GTP TEID in the first GTP TEID list, which is used for data transmission and path switching.

[0489] The second GTP TEID of the first access network device is used for data transmission and associated with a PDU session. The second GTP TEID is at least one GTP TEID in the second GTP TEID list, which is used for data transmission.

[0490] The fourth GTP TEID of the core network device, the fourth GTP TEID is used for data transmission and associated with a PDU session, the fourth GTP TEID is at least one GTP TEID in the fourth GTP TEID list of the core network device, the fourth GTP TEID list is used for data transmission.

[0491] In some embodiments, the method further includes:

[0492] Receive a second paging message sent by a second access network device, the second paging message being used to page the terminal;

[0493] Send a first paging message to the first access network device.

[0494] In some embodiments, the second paging message includes at least one of the following:

[0495] List of access network devices for the first access network device;

[0496] RNA;

[0497] Access Network RAN ​​Paging Container;

[0498] I-RNTI.

[0499] In some embodiments, the first paging message includes at least one of the following:

[0500] I-RNTI;

[0501] RNA;

[0502] Access network RAN ​​paging container.

[0503] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0504] Figure 3C is a flowchart illustrating a state recovery method according to an embodiment of the present disclosure. As shown in Figure 3C, this disclosure relates to a state recovery method, which includes:

[0505] Step S3301: The second access network device receives the third request message sent by the core network device.

[0506] In some embodiments, the third request message is used to request context information of the terminal, the context information being used to restore the state of the RRC connection between the terminal and the first access network device to the RRC connection state.

[0507] Step S3301 is similar to step S2104 shown in Figure 2A above, and will not be described again here.

[0508] In step S3302, the second access network device sends a third response message to the core network device.

[0509] Step S3302 is similar to step S2106 shown in Figure 2A above, and will not be described again here.

[0510] In some embodiments, the third request message includes at least one of the following:

[0511] I-RNTI;

[0512] First MAC-I;

[0513] Reason for connection restoration;

[0514] The first GTP TEID list of the first access network device, the first GTP TEID list is used for data transmission and path switching;

[0515] The second GTP TEID list of the first access network device, the second GTP TEID list is used for data transmission;

[0516] The fourth GTP TEID list of the core network equipment, the fourth GTP TEID list is used for data transmission;

[0517] Service area signage.

[0518] In some embodiments, the method further includes:

[0519] The second MAC-I is determined based on the serving cell identifier;

[0520] The second MAC-I is the same as the first MAC-I, thus determining that the terminal is a compliant terminal.

[0521] In some embodiments, the third response message includes context information of the terminal.

[0522] The third response message also includes at least one of the following:

[0523] The first GTP TEID of the first access network device is used for data transmission and associated with a PDU session. The first GTP TEID is at least one GTP TEID in the first GTP TEID list, which is used for data transmission and path switching.

[0524] The second GTP TEID of the first access network device is used for data transmission and associated with a PDU session. The second GTP TEID is at least one GTP TEID in the second GTP TEID list, which is used for data transmission.

[0525] The fourth GTP TEID of the core network device, the fourth GTP TEID is used for data transmission and associated with a PDU session, the fourth GTP TEID is at least one GTP TEID in the fourth GTP TEID list of the core network device, the fourth GTP TEID list is used for data transmission.

[0526] In some embodiments, the method further includes:

[0527] Receive downlink information;

[0528] A second paging message is sent to the core network equipment, the second paging message being used to page the terminal.

[0529] In some embodiments, the second paging message includes at least one of the following:

[0530] List of access network devices for the first access network device;

[0531] RNA;

[0532] Access Network RAN ​​Paging Container;

[0533] I-RNTI.

[0534] In some embodiments, the method further includes:

[0535] Send configuration information to the terminal, the configuration information being used to configure the terminal to enter the RRC inactive state.

[0536] In some embodiments, the configuration information includes at least one of the following:

[0537] Area information of at least one cell of the first access network device;

[0538] The area information of at least one cell of the second access network device.

[0539] Figure 4 is a flowchart illustrating a state recovery method according to an embodiment of the present disclosure. As shown in Figure 4, this disclosure relates to a state recovery method, which includes:

[0540] In step S4101, the serving gNB and the anchor gNB communicate via AMF to forward data and restore the terminal's RRC connection.

[0541] The anchor gNB configures RRC_INACTIVE related configuration information for the UE, and the UE enters the RRC_INACTIVE state. The RRC_INACTIVE related configuration information includes an RNA area, which encompasses the coverage of at least one cell of at least two gNBs. There is no Xn physical connection and / or Xn logical connection (i.e., Xn connection) between the two gNBs. One gNB is the base station storing the UE context, and the other gNB is the base station of the target cell where the current UE initiates RRC connection recovery.

[0542] 1) The terminal sends an RRCResumeRequest message to the current serving base station, triggering the RRC connection recovery process.

[0543] 2) The current serving base station determines the gNB ID (identifier of the anchor gNB) of the base station storing the UE context based on the I-RNTI carried in the RRCResumeRequest message. It then checks if an Xn connection exists between the current base station and the anchor gNB. If not, the current serving base station initiates a UE context request message (UE context Retrieval request) to the AMF. This message carries the anchor gNB ID for the AMF to address the target base station and also includes the I-RNTI. It may also include one of the following: MAC-I, resume cause, current serving cell ID (first PLMN + cell identity), etc. Simultaneously, the current serving base station provides one GTP TEID list or two GTP TEID lists to the AMF, used for data forwarding and path switching respectively. If only one list is provided, this list is used for both data forwarding and path switching.

[0544] 3) The AMF addresses the target base station based on the anchor gNB ID and sends a UE context request message, i.e., a UE context Retrieval request message, to that base station. The context Retrieval request message carries one of the following information: I-RNTI, MAC-I, resume cause, serving gNB GTP TEID list or serving gNB GTP TEID list for data forwarding, AMF GTP TEID list for data forwarding, and current serving cell ID (first PLMN + cell identity).

[0545] Where: the current serving cell ID is used by anchorgNB to calculate MACI-I.

[0546] 4) The Anchor gNB locates the UE context based on the I-RNTI and determines whether it is a legitimate UE based on the MAC-I. If it is, the Anchor gNB forwards the UE context to the AMF, i.e., a UE context Retrieval response message, which includes at least one of the following:

[0547] At least one AMF GTP TEID is selected from the AMF GTP TEID list, and each AMF GTP TEID is associated with a PDU session ID. The selected AMF GTP TEID is used for data forwarding.

[0548] - At least one serving gNB GTP TEID is selected from the serving gNB GTP TEID list, and each serving gNB GTP TEID is associated with a PDU session ID. (Optional; AMF can do this if the anchor gNB does not). The selected serving gNB GTP TEID is used for data forwarding.

[0549] -UE context.

[0550] 5) The AMF forwards the UE context to the currently serving gNB, i.e., a UE context Retrieval response message, which includes at least one of the following:

[0551] At least one serving gNB GTP TEID is selected from the serving gNB GTP TEID list, and each serving gNB GTP TEID is associated with a PDU session ID. The selected serving gNB GTP TEID is used for data forwarding.

[0552] At least one serving gNB GTP TEID is selected from the serving gNB GTP TEID list, and each serving gNB GTP TEID is associated with a PDU session ID. The selected serving gNB GTP TEID is used for path switching. If there is only one serving gNB GTP TEID list, both data forwarding and path switching are selected from this list. If data forwarding and path switching correspond to two separate lists, then selection is made from each of those lists.

[0553] -AMF GTP TEID list, each AMF GTP TEID is associated with a PDU session ID. AMF GTP TEIDs are used for path switching.

[0554] -UE context.

[0555] 6) The current serving base station sends an RRRCResume message to the UE.

[0556] 7) The UE sends RRCResumeComplete to the serving base station, and the RRC recovery is successful.

[0557] Alternatively, an RRC connection recovery can be triggered via a paging message.

[0558] 1) When DL data arrives at the anchor base station, the anchor base station sends a RAN paging transfer message to the AMF for forwarding RAN paging. The RAN paging transfer message contains the following information:

[0559] Option 1: at least one of the following

[0560] -Target gNB id list

[0561] -RNA

[0562] -RAN paging container

[0563] Option 2: at least one of the following

[0564] -I-RNTI

[0565] -gNB id list

[0566] -RNA

[0567] - Other information in RAN paging, now in 38.423.

[0568] 2) The AMF forwards the information from step 1 to the target base station. This RAN paging transfer message is used to forward RAN paging to the gNB. The RAN paging transfer includes the following information:

[0569] Option 1: at least one of the following

[0570] -RAN paging container

[0571] -RNA

[0572] -I-RNTI

[0573] Option 2: at least one of the following

[0574] -I-RNTI

[0575] -RNA

[0576] - Other information in RAN paging, now in 38.423.

[0577] The subsequent service base station can then perform the aforementioned RRC connection restoration process.

[0578] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0579] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0580] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through a configuration file, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0581] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0582] Figure 5A is a schematic diagram of the structure of a first access network device according to an embodiment of this disclosure. The first access network device 5100 is used to perform any of the above methods. In some embodiments, as shown in Figure 5A, the first access network device 5100 may include at least one of a transceiver module 5101, a processing module 5102, etc. In some embodiments, the transceiver module 5101 is used to send a first request message to a core network device, the first request message being used to request context information of the first access network device from a second access network device, the context information being used to restore the state of the RRC connection between the first access network device and the second access network device to an RRC connection state; and to receive a first response message sent by the core network device. Optionally, the transceiver module is used to perform at least one of the communication steps such as sending and / or receiving performed by the first access network device 5101 in any of the above methods, which will not be elaborated here. Optionally, the processing module is used to perform at least one of the other steps performed by the first access network device 5100 in any of the above methods, which will not be elaborated here.

[0583] Figure 5B is a schematic diagram of the core network device proposed in an embodiment of this disclosure. The core network device 5200 is used to perform any of the above methods. In some embodiments, as shown in Figure 5B, the core network device 5200 may include at least one of a transceiver module 5201, a processing module 5202, etc. In some embodiments, the transceiver module 5201 is used to receive a first request message sent by a first access network device, the first request message being used to request context information of a terminal from a second access network device, the context information being used to restore the state of the RRC connection between the terminal and the first access network device to an RRC connection state; and to send a first response message to the first access network device. Optionally, the transceiver module is used to perform at least one of the communication steps such as sending and / or receiving performed by the core network device 5200 in any of the above methods, which will not be elaborated here. Optionally, the processing module is used to perform at least one of the other steps performed by the core network device 5200 in any of the above methods, which will not be elaborated here.

[0584] Figure 5C is a schematic diagram of the structure of the second access network device proposed in an embodiment of this disclosure. The second access network device 5300 is used to perform any of the above methods. In some embodiments, as shown in Figure 5C, the second access network device 5300 may include at least one of a transceiver module 5301, a processing module 5302, etc. In some embodiments, the transceiver module 5301 is used to receive a third request message sent by the core network device, the third request message being used to request context information of the terminal, the context information being used to restore the state of the RRC connection between the terminal and the first access network device to the RRC connection state; and to send a third response message to the core network device. Optionally, the transceiver module is used to perform at least one of the communication steps such as sending and / or receiving performed by the second access network device 5300 in any of the above methods, which will not be described in detail here. Optionally, the processing module is used to perform at least one of the other steps performed by the second access network device 5300 in any of the above methods, which will not be described in detail here.

[0585] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0586] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module.

[0587] In some embodiments, the processing module can be replaced by the processor, and the transceiver module can be replaced by the transceiver.

[0588] Figure 6A is a schematic diagram of the structure of the communication device 6100 proposed in an embodiment of this disclosure. The communication device 6100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 6100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0589] As shown in Figure 6A, the communication device 6100 is used to execute any of the above methods. In some embodiments, the communication device 6100 includes one or more processors 6101. The processor 6101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 6100 is used to execute any of the above methods. Optionally, one or more processors 6101 are used to invoke instructions to cause the communication device 6100 to execute any of the above methods.

[0590] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceiver 6102 performs at least one of the communication steps (e.g., steps S2103, S2104, but not limited thereto) in the above method, such as sending and / or receiving, and the processor 6101 performs at least one of other steps (e.g., steps S2101, S2102, S2105, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, sending unit, transmitter, sending circuit, etc., can be used interchangeably; the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0591] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data and / or instructions. Optionally, one or more processors 6101 are used to invoke instructions stored in the memory 6103 to cause the communication device 6100 to perform any of the above methods. Optionally, all or part of the memory 6103 may also be located outside the communication device 6100. In optional embodiments, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuit 6104 is connected to the memory 6102 and can be used to receive data and / or instructions from the memory 6102 or other devices, and can be used to send data and / or instructions to the memory 6102 or other devices. For example, the interface circuit 6104 can read data and / or instructions stored in the memory 6102 and send the data and / or instructions to the processor 6101.

[0592] The communication device 6100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 6100 described in this disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited by FIG. 6A. The communication device may be a standalone device or a part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0593] Figure 6B is a schematic diagram of the structure of chip 6200 according to an embodiment of this disclosure. For cases where the communication device 6100 can be a chip or a chip system, please refer to the schematic diagram of chip 6200 shown in Figure 6B, but it is not limited thereto.

[0594] Chip 6200 includes one or more processors 6201. Chip 6200 is used to perform any of the methods described above.

[0595] In some embodiments, chip 6200 further includes one or more interface circuits 6202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 6200 further includes one or more memories 6203 for storing data and / or instructions. Optionally, all or part of the memories 6203 may be located outside of chip 6200. Optionally, interface circuit 6202 is connected to memory 6203, and interface circuit 6202 can be used to receive data and / or instructions from memory 6203 or other devices, and interface circuit 6202 can be used to send data and / or instructions to memory 6203 or other devices. For example, interface circuit 6202 can read data and / or instructions stored in memory 6203 and send the data and / or instructions to processor 6201.

[0596] In some embodiments, the interface circuit 6202 performs at least one of the communication steps (e.g., steps S2103, S2104, but not limited thereto) in the above-described method, such as sending and / or receiving. For example, the interface circuit 6202 performing the communication steps (e.g., sending and / or receiving) in the above-described method means that the interface circuit 6202 performs data and / or instruction interaction between the processor 6201, the chip 6200, the memory 6203, or the transceiver device. In some embodiments, the processor 6201 performs at least one of other steps (e.g., steps S2101, S2102, but not limited thereto).

[0597] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0598] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0599] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.

[0600] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

Claims

1. A state recovery method, wherein, The method is performed by a first access network device, and the method includes: Send a first request message to the core network device. The first request message is used to request the context information of the terminal from the second access network device. The context information is used to restore the state of the Radio Resource Control (RRC) connection between the terminal and the first access network device to the RRC connection state. Receive the first response message sent by the core network device.

2. The method according to claim 1, wherein, Sending the first request message to the core network device includes: There is no interface connection between the first access network device and the second access network device, so the first request message is sent to the core network device.

3. The method according to claim 1 or 2, wherein, The first request message includes the access network device identifier of the second access network device; The first request message also includes at least one of the following: An inactive wireless network temporary identifier (I-RNTI) is used to indicate the access network device identifier of the second access network device and the terminal identifier of the terminal. First identity message verification code MAC-I, the first MAC-I is used to verify the identity of the terminal; Reason for connection restoration; Serving cell identifier, which is used to calculate the second MAC-I; The first GTP TEID list of the first access network device, the first GTP TEID list is used for data transmission and path switching; The second GTP TEID list of the first access network device, the second GTP TEID list is used for data transmission; The third GTP TEID list of the first access network device, the third GTP TEID list is used for path switching.

4. The method according to any one of claims 1 to 3, wherein, The first response message includes the context information of the terminal; The first response message also includes at least one of the following: The first GTP TEID of the first access network device is used for data transmission and associated with a PDU session. The first GTP TEID is at least one GTP TEID in the first GTP TEID list, which is used for data transmission and path switching. The second GTP TEID of the first access network device is used for data transmission and associated with a PDU session. The second GTP TEID is at least one GTP TEID in the second GTP TEID list, which is used for data transmission. The fourth GTP TEID of the core network device, the fourth GTP TEID is used for data transmission and associated with a PDU session, the fourth GTP TEID is at least one GTP TEID in the fourth GTP TEID list of the core network device, the fourth GTP TEID list is used for data transmission.

5. The method according to any one of claims 1 to 4, wherein, The method further includes: The receiving terminal sends a second request message, which requests that the state of the RRC connection between the terminal and the first access network device be restored to the RRC connection state. Send a second response message to the terminal.

6. The method according to claim 5, wherein, The second request message includes I-RNTI; The second request message also includes at least one of the following: First MAC-I; Reason for connection restoration.

7. The method according to claim 5 or 6, wherein, The method further includes: Based on the I-RNTI included in the second request message, the access network device identifier of the second access network device is determined.

8. The method according to any one of claims 1 to 7, wherein, Restoring the Radio Resource Control (RRC) connection state between the terminal and the first access network device to an RRC connection state includes: The state of the Radio Resource Control (RRC) connection between the terminal and the first access network device is restored from the RRC inactive state to the RRC connected state.

9. The method according to any one of claims 1 to 8, wherein, The method further includes: Receive a first paging message sent by the core network device, the first paging message being used to page the terminal; The first paging message is forwarded to the terminal.

10. The method according to claim 9, wherein, The first paging message includes at least one of the following: I-RNTI; Access network notification area RNA; Access network RAN ​​paging container.

11. A state recovery method, wherein, The method is executed by a core network device, and the method includes: The system receives a first request message sent by a first access network device. The first request message is used to request context information of the terminal from a second access network device. The context information is used to restore the state of the Radio Resource Control (RRC) connection between the terminal and the first access network device to the RRC connection state. Send a first response message to the first access network device.

12. The method according to claim 11, wherein, The first request message is sent when there is no interface connection between the first access network device and the second access network device.

13. The method according to claim 11 or 12, wherein, The first request message includes the access network device identifier of the second access network device; The first request message also includes at least one of the following: I-RNTI; First MAC-I; Reason for connection restoration; Serving cell identifier, which is used to calculate the second MAC-I; The first GTP TEID list is used for data transmission and path switching; The second GTP TEID list is used for data transmission; The third GTP TEID list is used for path switching.

14. The method according to any one of claims 11 to 13, wherein, The first response message includes the context information of the terminal; The first response message also includes at least one of the following: The first GTP TEID of the first access network device is used for data transmission and associated with a PDU session. The first GTP TEID is at least one GTP TEID in the first GTP TEID list, which is used for data transmission and path switching. The second GTP TEID of the first access network device is used for data transmission and associated with a PDU session. The second GTP TEID is at least one GTP TEID in the second GTP TEID list, which is used for data transmission. The fourth GTP TEID of the core network device, the fourth GTP TEID is used for data transmission and associated with a PDU session, the fourth GTP TEID is at least one GTP TEID in the fourth GTP TEID list, the fourth GTP TEID list is used for data transmission.

15. The method according to any one of claims 11 to 14, wherein, The method further includes: Send a third request message to the second access network device, the third request message being used to request the context information of the terminal; Receive the third response message sent by the second access network device.

16. The method according to claim 15, wherein, The third request message includes at least one of the following: I-RNTI; First MAC-I; Reason for connection restoration; The first GTP TEID list of the first access network device, the first GTP TEID list is used for data transmission and path switching; The second GTP TEID list of the first access network device, the second GTP TEID list is used for data transmission; The fourth GTP TEID list of the core network equipment, the fourth GTP TEID list is used for data transmission; Service area signage.

17. The method according to claim 15, wherein, The third response message includes the context information of the terminal. The third response message also includes at least one of the following: The first GTP TEID of the first access network device is used for data transmission and associated with a PDU session. The first GTP TEID is at least one GTP TEID in the first GTP TEID list, which is used for data transmission and path switching. The second GTP TEID of the first access network device is used for data transmission and associated with a PDU session. The second GTP TEID is at least one GTP TEID in the second GTP TEID list, which is used for data transmission. The fourth GTP TEID of the core network device, the fourth GTP TEID is used for data transmission and associated with a PDU session, the fourth GTP TEID is at least one GTP TEID in the fourth GTP TEID list of the core network device, the fourth GTP TEID list is used for data transmission.

18. The method according to any one of claims 11 to 17, wherein, The method further includes: Receive a second paging message sent by a second access network device, the second paging message being used to page the terminal; Send a first paging message to the first access network device.

19. The method according to claim 18, wherein, The second paging message includes at least one of the following: List of access network devices for the first access network device; RNA; Access Network RAN ​​Paging Container; I-RNTI.

20. The method according to claim 18, wherein, The first paging message includes at least one of the following: I-RNTI; RNA; Access network RAN ​​paging container.

21. A state recovery method, wherein, The method is performed by a second access network device, and the method includes: The terminal receives a third request message sent by the core network device. The third request message is used to request the context information of the terminal. The context information is used to restore the state of the Radio Resource Control (RRC) connection between the terminal and the first access network device to the RRC connection state. Send a third response message to the core network device.

22. The method according to claim 21, wherein, The third request message includes at least one of the following: I-RNTI; First MAC-I; Reason for connection restoration; The first GTP TEID list of the first access network device, the first GTP TEID list is used for data transmission and path switching; The second GTP TEID list of the first access network device, the second GTP TEID list is used for data transmission; The fourth GTP TEID list of the core network equipment, the fourth GTP TEID list is used for data transmission; Service area signage.

23. The method according to claim 22, wherein, The method further includes: The second MAC-I is determined based on the serving cell identifier; The second MAC-I is the same as the first MAC-I, thus determining that the terminal is a compliant terminal.

24. The method according to claim 21, wherein, The third response message includes the context information of the terminal. The third response message also includes at least one of the following: The first GTP TEID of the first access network device is used for data transmission and associated with a PDU session. The first GTP TEID is at least one GTP TEID in the first GTP TEID list, which is used for data transmission and path switching. The second GTP TEID of the first access network device is used for data transmission and associated with a PDU session. The second GTP TEID is at least one GTP TEID in the second GTP TEID list, which is used for data transmission. The fourth GTP TEID of the core network device, the fourth GTP TEID is used for data transmission and associated with a PDU session, the fourth GTP TEID is at least one GTP TEID in the fourth GTP TEID list of the core network device, the fourth GTP TEID list is used for data transmission.

25. The method according to any one of claims 21 to 24, wherein, The method further includes: Receive downlink information; A second paging message is sent to the core network equipment, the second paging message being used to page the terminal.

26. The method according to claim 25, wherein, The second paging message includes at least one of the following: List of access network devices for the first access network device; RNA; Access Network RAN ​​Paging Container; I-RNTI.

27. The method according to any one of claims 21 to 26, wherein, The method further includes: Send configuration information to the terminal, the configuration information being used to configure the terminal to enter the RRC inactive state.

28. The method according to claim 27, wherein, The configuration information includes at least one of the following: Area information of at least one cell of the first access network device; The area information of at least one cell of the second access network device.

29. A communication device, wherein, The communication device is used to perform the state recovery method according to any one of claims 1-10, or any one of claims 11-20, or any one of claims 21-28.

30. A state recovery method for a communication system, the communication system comprising a first access network device, a core network device, and a second access network device, wherein, The method includes: The first access network device is used to perform the state recovery method as described in any one of claims 1-10; The core network device is used to perform the state recovery method as described in any one of claims 11-20; The second access network device is used to perform the state recovery method as described in any one of claims 21-28.

31. A communication system, wherein, Includes at least one of a first access network device, a core network device, and a second access network device; The first access network device is used to perform the state recovery method as described in any one of claims 1-10; The core network device is used to perform the state recovery method as described in any one of claims 11-20; The second access network device is used to perform the state recovery method as described in any one of claims 21-28.

32. A storage medium storing instructions, wherein, When the instruction is executed on the communication device, the communication device performs the state recovery method as described in any one of claims 1-10, or any one of claims 11-20, or any one of claims 21-28.

33. A program product comprising at least one of a program and instructions, wherein, When at least one of the programs or instructions is executed by the communication device, it implements the state recovery method according to any one of claims 1-10, any one of claims 11-20, or any one of claims 21-28.

Images