A communication method and apparatus

CN116634426BActive Publication Date: 2026-11-17HUAWEI TECH CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202210130403.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-02-11
Publication Date
2026-11-17
Estimated Expiration
2042-02-11

AI Technical Summary

Technical Problem

[0004]但是,如果终端设备第二次发送RRC恢复请求消息时,接入网设备已经缓存了一些下行数据,这些下行数据可能会使用第一次RRC连接恢复过程中推演出的第一密钥进行安全性保护

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116634426B_ABST
    Figure CN116634426B_ABST
Patent Text Reader

Abstract

This application relates to the field of wireless communication technology, providing a communication method and apparatus to avoid security verification errors. When a terminal device in an inactive state determines that first type of data has arrived, it determines a first key; the first key is used by the terminal device to transmit the first type of data in the inactive state. When a second type of data has arrived, it determines a second key and sends an RRC request message to the access network device; the second key is used by the terminal device to transmit the second type of data in the connected state. Before receiving an RRC response message from the access network device, the terminal device receives the first type of data from the access network device and uses the first key to perform security verification on the first type of data. Since if downlink first type of data is received before receiving the response message to the second RRC request message, and the first key is still used to perform security verification on the downlink data, no security verification error will occur.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to fields such as wireless communication, and in particular to a communication method and apparatus. Background Technology

[0002] When a terminal device in an inactive state needs to transmit uplink data, it initiates a radio resource control (RRC) recovery process. Upon receiving the RRC recovery message, the terminal device restores the RRC connection, transitions from the inactive state to the connected state, and begins transmitting uplink data. This process results in low service data transmission efficiency. Based on this, the standard further discusses that when performing small data transmission (SDT) in the inactive state, it is not necessary to transition from the inactive state to the connected state; however, for non-SDT data, the terminal device still needs to transition from the inactive state to the connected state to transmit data.

[0003] When a terminal device in the inactive state needs to send SDT data, it triggers the first RRC connection recovery process. During this first RRC connection recovery process, the terminal device and the base station deduce a first key to protect the uplink and downlink data. If the terminal device needs to send non-SDT data before receiving an RRC release message, it can trigger a second RRC connection recovery process. During this second RRC connection recovery process, the terminal device and the base station deduce a new second key to protect the uplink and downlink data.

[0004] However, if the access network device has already cached some downlink data when the terminal device sends the RRC recovery request message for the second time, this downlink data may be protected with the first key derived during the first RRC connection recovery process. Upon receiving this downlink data, the terminal device will use the second key newly generated during the second RRC connection recovery process for security verification, which will trigger a security verification error. Summary of the Invention

[0005] This application provides a communication method and apparatus to avoid security verification errors.

[0006] Firstly, a communication method is provided. The execution subject of this method can be a terminal device or a component applied in the terminal device, such as a chip or processor. The following description uses a terminal device as the execution subject. First, when the terminal device in an inactive state determines that a first type of data has arrived, it determines a first key; wherein, the first key is used by the terminal device to transmit the first type of data in the inactive state. Then, when the terminal device determines that a second type of data has arrived, it determines a second key and sends an RRC request message to the access network device; wherein, the second key is used by the terminal device to transmit the second type of data in the connected state; the RRC request message is used to request the restoration of the RRC connection. Next, before receiving an RRC response message from the access network device, the terminal device receives the first type of data from the access network device and uses the first key to perform security verification on the first type of data; wherein, the RRC response message is used to respond to the RRC request message.

[0007] After the terminal device sends the second RRC request message, if it receives downlink first-type data before receiving the response message (such as RRC recovery or RRC release message) of the second RRC request message, it will still use the first key to perform security verification on the downlink first-type data, so that no security verification error will occur, and thus it can avoid delivering erroneous data to the upper layer.

[0008] Secondly, a communication method is provided. The execution subject of this method can be a terminal device or a component applied in the terminal device, such as a chip or processor. The following description uses a terminal device as the execution subject. First, when the terminal device in an inactive state determines that a first type of data has arrived, it determines a first key; wherein, the first key is used by the terminal device to transmit the first type of data in the inactive state. Then, when the terminal device determines that a second type of data has arrived, it determines a second key and sends an RRC request message to the access network device; wherein, the second key is used by the terminal device to transmit the second type of data in the connected state; the RRC request message is used to request the restoration of the RRC connection. Finally, before receiving the RRC response message from the access network device, the terminal device receives the first type of data from the access network device and discards the first type of data; wherein, the RRC response message is used to respond to the RRC request message.

[0009] If the terminal device receives downlink data after sending the second RRC request message but before receiving the response message for the second RRC request message, and discards the downlink data directly, a security verification error will not occur, thus avoiding the delivery of erroneous data to the upper layer.

[0010] Thirdly, a communication method is provided. The execution subject of this method can be a centralized unit (CU) or a component applied in the centralized unit CU, such as a chip or processor. The following description uses the centralized unit CU as the execution subject. First, upon receiving a first RRC request message from a DU, the centralized unit CU determines a first key; wherein the first RRC request message originates from a deactivated terminal device, is used to request the restoration of the RRC connection, and the first key is used to transmit a first type of data with the deactivated terminal device. Then, the centralized unit CU receives a second RRC request message from the DU and determines a second key; wherein the second RRC request message originates from the deactivated terminal device, is used to request the restoration of the RRC connection, and the second key is used to transmit a second type of data with the connected terminal device. Next, after sending first indication information to the DU, the centralized unit CU sends an RRC response message of the second RRC request message to the DU; wherein the first indication information instructs the DU to clear the first type of data.

[0011] In existing technology, if the DU (Distribution Unit) has cached downlink data, it will continue to send it to the inactive terminal device. However, because this cached downlink data is protected by a first key, and the UE has already determined the second key before sending the second RRC request message, continuing to send this cached downlink data to the UE will lead to a security verification error on the UE side. In this example, after receiving the second RRC request message, the CU (Distribution Unit) instructs the DU to delete the cached downlink data, avoiding wasting transmission resources and preventing UE security verification errors.

[0012] In one possible implementation, the CU includes a control plane CU and a user plane CU; sending first indication information to the DU includes: the user plane CU sending first indication information to the DU; or, the control plane CU sending first indication information to the DU.

[0013] In one possible implementation, the user plane CU sends first indication information to the DU, including: the user plane CU sending a downlink user data message to the DU, the downlink user data message including the first indication information.

[0014] In one possible implementation, the control plane CU sends first indication information to the DU, including: the control plane CU sending a UE context establishment request message to the DU, the UE context establishment request message including the first indication information.

[0015] Fourthly, a communication method is provided. The execution subject of this method can be a new service access network device or a component applied in the new service access network device, such as a chip or processor. The following description uses the example of the new service access network device as the execution subject. First, the new service access network device receives a first Radio Resource Control (RRC) request message from a terminal device in an inactive state. The first RRC request message is used to request the restoration of the RRC connection. Then, the new service access network device receives a second RRC request message from the terminal device in an inactive state. The second RRC request message is used to request the restoration of the RRC connection, and it is sent by the inactive terminal device when there is a second type of data to be transmitted during a first type of data transmission process, which is triggered by the first RRC request message. Next, the new service access network device sends a request message to the anchor access network device, which is used to request the acquisition of the context of the terminal device. Finally, the new service access network device receives a response message from the anchor access network device in response to the request message. Next, before the new service access network device sends the response message of the second RRC recovery request message to the terminal device, it clears the cached first type of data.

[0016] In existing technology, if a new serving access network device has cached downlink data, it will continue to send it to the UE. However, because this cached downlink data is protected by a first key, and the UE has already determined the second key before sending the second RRC request message, continuing to send downlink data protected by the first key to the UE will lead to a security verification error on the UE side. In this example, after the anchor access network device learns through I-RNTI that this is the second RRC recovery process initiated by the same UE, it instructs the new serving access network device to delete the cached downlink data to avoid wasting transmission resources and prevent the UE from experiencing a security verification error.

[0017] In one possible implementation, the response message includes second indication information; wherein: the second indication information is used to instruct the new service access network device to clear all cached downlink data, the cached downlink data being the first type of data; or, the second indication information is used to indicate the identification information of the downlink data to be cleared, the downlink data to be cleared being data in the downlink data cached by the new service access network device, the cached downlink data being the first type of data.

[0018] In one possible implementation, the response message is a UE context acquisition failure message; or, the response message is a downlink user data message.

[0019] Fifthly, a communication method is provided. The executing entity of this method can be a new service access network device or a component applied in the new service access network device, such as a chip or processor. The following description uses the example of the new service access network device as the executing entity. First, the new service access network device receives a first Radio Resource Control (RRC) request message from a terminal device in an inactive state. The first RRC request message is used to request the restoration of the RRC connection. Then, the new service access network device receives a second RRC request message from the terminal device in an inactive state. The second RRC request message is used to request the restoration of the RRC connection. The second RRC request message is sent by the inactive terminal device when there is a second type of data to be transmitted during a first type of data transmission process, which is triggered based on the first RRC request message. The second RRC request message includes a first identifier, which is used to determine the context of the terminal device. The first identifier can be an I-RNTI. Next, the new service access network device determines the context of the terminal device based on the first identifier. The context of the terminal device is the context of the terminal device received by the new service access network device from the anchor access network device during the first type of data transmission. The new service access network device determines a second key based on the information in the context of the terminal device. The second key is used to transmit the second type of data with the terminal device in the connected state.

[0020] This scheme can be applied to anchor point relocation scenarios. After receiving the first RRC request message from the terminal device, the new service access network device can also receive a terminal device context response message from the anchor access network device before receiving the second RRC request message from the terminal device. The terminal device context response message includes the entire context of the terminal device.

[0021] The new service access network device replaces the anchor access network device in determining the second key, thus eliminating the need for the anchor access network device to determine the second key. This avoids security issues caused by the same key being used in different access network devices and also saves storage resources on the anchor access network device.

[0022] In one possible implementation, after receiving the first RRC request message from the terminal device and before receiving the second RRC request message from the terminal device, the new serving access network device may also receive the first identifier from the anchor access network device and associate the first identifier with the context of the terminal device. For example, when the new serving access network device receives the first identifier from the anchor access network device, it may receive a RETRIEVE UE CONTEXT RESPONSE message from the anchor access network device, which includes the first identifier. Alternatively, the first identifier may be sent to the new serving access network device in a new message.

[0023] In one possible implementation, after determining the second key, the new service access network device can also send an RRC recovery message to the UE.

[0024] In one possible implementation, the first RRC request message includes the first identifier (e.g., I-RNTI). After receiving the first RRC request message from the terminal device and before receiving the second RRC request message from the terminal device, the new serving access network device may also receive a RETRIEVE UE CONTEXT RESPONSE message from the anchor access network device, triggering the association of the first identifier with the context of the terminal device. For example, the RETRIEVE UE CONTEXT RESPONSE message includes third indication information, which may be used to indicate authentication of the terminal device, to indicate saving the first identifier from the first RRC request message, or to indicate associating the first identifier with the context of the terminal device.

[0025] Sixthly, a communication method is provided. The executing entity of this method can be a new service access network device or a component applied in the new service access network device, such as a chip or processor. The following description uses the example of the new service access network device as the executing entity. First, the new service access network device receives a first Radio Resource Control (RRC) request message from a terminal device in an inactive state. The first RRC request message is used to request the restoration of the RRC connection. The first RRC request message includes a first identifier, which is used to determine the context of the terminal device. The first identifier can be an I-RNTI. Then, the new service access network device sends a second identifier to the terminal device. The second identifier is used to determine the context of the terminal device. The second identifier can be a new I-RNTI. This new I-RNTI can be carried in an RRCReconfiguration message or in a new RRC message. Next, the new service access network device receives a second RRC request message from a terminal device in an inactive state. This second RRC request message requests the restoration of the RRC connection and is sent by the inactive terminal device when a second type of data needs to be transmitted during a first type of data transmission process, triggered by the first RRC request message. The second RRC request message includes the second identifier. Next, the new service access network device determines the context of the terminal device based on the second identifier. The context of the terminal device is the one sent by the anchor access network device during the small data transmission process. Next, the new service access network device determines a second key based on the information in the context of the terminal device. This second key is used to transmit the second type of data with the terminal device in a connected state.

[0026] The new service access network device replaces the anchor access network device in determining the second key, thus eliminating the need for the anchor access network device to determine the second key. This avoids security issues caused by the same key being used in different access network devices and also saves storage resources on the anchor access network device.

[0027] After determining the second key, the new service access network device can also send an RRC recovery message to the UE.

[0028] In one possible implementation, when the new service access network device sends the second identifier to the terminal device, it may also send the next-hop chain count (NCC) value to the terminal device.

[0029] In a seventh aspect, a communication device is provided, the device having functions that implement any of the above aspects and any possible implementations of any of the above aspects. These functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more functional modules corresponding to the above functions.

[0030] When the device has the function of implementing the first aspect described above, the device includes: A processing module is configured to determine a first key when the device, in an inactive state, determines that a first type of data has arrived; wherein the first key is used by the device to transmit the first type of data in the inactive state; and to determine a second key when a second type of data has arrived; a sending module is configured to send an RRC request message to an access network device; wherein the second key is used by the device to transmit the second type of data in a connected state; the RRC request message is used to request the restoration of the RRC connection; a receiving module is configured to receive the first type of data from the access network device before receiving an RRC response message from the access network device; the processing module is further configured to perform security verification on the first type of data using the first key; wherein the RRC response message is used to respond to the RRC request message.

[0031] When the device has the function of implementing the second aspect described above, the device includes: A processing module is configured to determine a first key when the device, in an inactive state, determines that a first type of data has arrived; wherein the first key is used by the device to transmit the first type of data in the inactive state; and to determine a second key when a second type of data has arrived; a sending module is configured to send an RRC request message to an access network device; wherein the second key is used by the device to transmit the second type of data in a connected state; the RRC request message is used to request the restoration of the RRC connection; a receiving module is configured to receive the first type of data from the access network device before receiving an RRC response message from the access network device; wherein the RRC response message is used to respond to the RRC request message; the processing module is further configured to discard the first type of data.

[0032] When the device has the functions of implementing the third aspect and any possible implementation of the third aspect, the device includes: A processing module is configured to determine a first key upon receiving a first RRC request message from a DU; wherein the first RRC request message originates from a terminal device in an inactive state, the first RRC request message is used to request the restoration of an RRC connection, and the first key is used to transmit a first type of data with the terminal device in the inactive state; a receiving module is configured to receive a second RRC request message from the DU; wherein the second RRC request message originates from the terminal device in the inactive state, and the second RRC request message is used to request the restoration of an RRC connection; the processing module is further configured to determine a second key, the second key being used to transmit a second type of data with the terminal device in a connected state; a sending module is configured to send an RRC response message of the second RRC request message to the DU after sending first indication information; wherein the first indication information is used to instruct the DU to clear the first type of data.

[0033] For example, the device includes a control plane CU and a user plane CU.

[0034] When the apparatus has the functions of implementing the fourth aspect and any possible implementation of the fourth aspect, the apparatus includes: A receiving module is configured to receive a first Radio Resource Control (RRC) request message from a terminal device in an inactive state, the first RRC request message being used to request the restoration of an RRC connection; and to receive a second RRC request message from the terminal device in an inactive state; wherein the second RRC request message is used to request the restoration of an RRC connection, and the second RRC request message is sent by the terminal device in the inactive state when there is a second type of data to be transmitted during a first type of data transmission process, the first type of data transmission process being triggered based on the first RRC request message; a sending module is configured to send a request message to an anchor access network device, the request message being used to request the acquisition of the context of the terminal device; the receiving module is further configured to receive a response message from the anchor access network device in response to the request message; and a processing module is configured to clear the cached first type of data before sending the response message of the second RRC restoration request message to the terminal device.

[0035] For example, the response message includes second indication information; wherein: the second indication information is used to instruct the new service access network device to clear all cached downlink data, the cached downlink data being the first type of data; or, the second indication information is used to indicate the identification information of the downlink data that needs to be cleared, the downlink data that needs to be cleared being data in the downlink data cached by the new service access network device, the cached downlink data being the first type of data.

[0036] For example, the response message may be a UE context acquisition failure message; or, the response message may be a downlink user data message.

[0037] Eighthly, a communication device is provided, including a processor, and optionally, a memory; the processor and the memory are coupled; the memory is used to store computer programs or instructions; the processor is used to execute part or all of the computer programs or instructions in the memory, and when the part or all of the computer programs or instructions are executed, to implement the functions of any of the above aspects and any possible implementations of the methods.

[0038] In one possible implementation, the apparatus may further include a transceiver for transmitting signals processed by the processor or receiving signals input to the processor. The transceiver may perform either the transmitting or receiving action in any aspect and in any possible implementation of any aspect.

[0039] Ninthly, this application provides a chip system including one or more processors (also referred to as processing circuits), the processors being electrically coupled to a memory (also referred to as a storage medium); the memory may or may not be located in the chip system; the memory is used to store computer programs or instructions; the processor is used to execute part or all of the computer programs or instructions in the memory, and when the part or all of the computer programs or instructions are executed, to implement the functions of any of the above aspects and any possible implementations of the methods.

[0040] In one possible implementation, the chip system may further include an input / output interface (also referred to as a communication interface) for outputting signals processed by the processor or receiving signals input to the processor. The input / output interface can perform either a sending or receiving action in any aspect and any possible implementation of that aspect. Specifically, the output interface performs a sending action, and the input interface performs a receiving action.

[0041] In one possible implementation, the chip system may consist of chips or include chips and other discrete devices.

[0042] In a tenth aspect, a computer-readable storage medium is provided for storing a computer program, the computer program including instructions for implementing functions in any aspect and any possible implementation of any aspect.

[0043] Alternatively, a computer-readable storage medium for storing a computer program, which, when executed by a computer, causes the computer to perform any of the above-described methods and any possible implementation thereof.

[0044] Eleventhly, a computer program product is provided, the computer program product comprising: computer program code, which, when run on a computer, causes the computer to perform the methods of any of the above aspects and any possible implementations of any of the above aspects.

[0045] The technical effects of aspects seven through eleven above can be referred to the descriptions in aspects one through six, and the repeated parts will not be repeated. Attached Figure Description

[0046] Figure 1 This is a communication system architecture diagram provided in the embodiments of this application; Figure 2a This is a communication system architecture diagram provided in the embodiments of this application; Figure 2b This is a communication system architecture diagram provided in the embodiments of this application; Figure 3 , Figure 4 , Figure 5 , Figure 6 , Figure 7 , Figure 8 , Figure 9 , Figure 10 , Figure 11 , Figure 12 , Figure 13 These are schematic diagrams of a communication process provided in the embodiments of this application; Figure 14 , Figure 15 These are structural diagrams of a communication device provided in the embodiments of this application. Detailed Implementation

[0047] The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0048] To facilitate understanding of the technical solutions in the embodiments of this application, the system architecture of the methods provided in the embodiments of this application will be briefly described below. It is understood that the system architecture described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions in the embodiments of this application and does not constitute a limitation on the technical solutions provided in the embodiments of this application.

[0049] The technical solutions of this application embodiment can be applied to various communication systems, such as satellite communication systems and traditional mobile communication systems. The satellite communication system can be integrated with traditional mobile communication systems (i.e., terrestrial communication systems). Examples of communication systems include: wireless local area network (WLAN) communication systems, wireless fidelity (WiFi) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, 5th generation (5G) systems or new radio (NR) systems, 6th generation (6G) systems, and other future communication systems. It also supports communication systems that integrate multiple wireless technologies. For example, it can also be applied to systems that integrate non-terrestrial networks (NTN) with terrestrial mobile communication networks, such as drones, satellite communication systems, and high altitude platform station (HAPS) communication.

[0050] To facilitate understanding of the embodiments of this application, the application scenarios of this application will be introduced below. The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. As those skilled in the art will know, with the emergence of new business scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.

[0051] like Figure 1 The communication system shown allows terminal devices (e.g., terminal device 1301 or terminal device 1302) to access a wireless network to obtain services from an external network (e.g., a data network (DN)) or to communicate with other devices, such as other terminal devices. This wireless network includes a radio access network (RAN) and a core network (CN). The RAN, also known as the access network (AN), is used to connect terminal devices to the wireless network, while the CN manages the terminal devices and provides a gateway for communication with the DN.

[0052] The RAN may include one or more access network devices, such as access network device 1101 and access network device 1102. The CN may include one or more core network elements, such as core network element 120.

[0053] Furthermore, the technical solutions described in this application are applicable to communication systems between UEs and access network devices, as well as UE-UE communication systems.

[0054] To facilitate understanding of the embodiments of this application, some terms or related technologies used in the embodiments of this application will be explained below, so that those skilled in the art can understand them.

[0055] 1) Terminal equipment.

[0056] Terminal equipment, also known as user equipment (UE), includes devices that provide voice and / or data connectivity to users. Examples include handheld devices with wireless connectivity or processing devices connected to a wireless modem. This terminal equipment can communicate with the core network via a radio access network (RAN) and exchange voice and / or data with the RAN. Terminal equipment can include wireless terminal equipment, mobile terminal equipment, device-to-device (D2D) terminal equipment, vehicle-to-everything (V2X) terminal equipment, machine-to-machine / machine-type communications (M2M / MTC) terminal equipment, Internet of Things (IoT) terminal equipment, subscriber units, subscriber stations, mobile stations, remote stations, access points (APs), remote terminals, access terminals, user terminals, user agents, or user equipment. For example, it can include mobile phones (or "cellular" phones), computers with mobile terminal devices, portable, pocket-sized, handheld, or computer-embedded mobile devices, etc. Examples include personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, and personal digital assistants (PDAs). It can also include limited devices, such as those with low power consumption, limited storage capacity, or limited computing power. Examples include information sensing devices such as barcode scanners, radio frequency identification (RFID), sensors, global positioning systems (GPS), and laser scanners.

[0057] In this application embodiment, the device for implementing the functions of the terminal device can be the terminal device itself, or it can be any device capable of supporting the terminal device in implementing those functions, such as a chip system or a combination of devices or components capable of implementing the functions of the terminal device. This device can be installed in the terminal device. In this application embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices. In the technical solutions provided in this application embodiment, the terminal device is used as an example to describe the technical solutions provided in this application embodiment.

[0058] 2) Access network equipment

[0059] Access network equipment refers to nodes or devices that connect terminal devices to a wireless network. Access network equipment can also be called a base station. Examples of access network equipment include, but are not limited to: next-generation Node B (gNB), evolved Node B (eNB), radio network controller (RNC), node B (NB), base station controller (BSC), base transceiver station (BTS), home evolved node B (HeNB) or home node B (HNB) in 5G communication systems, baseband unit (BBU), transmitting and receiving point (TRP), transmitting point (TP), or mobile switching center, etc.

[0060] In this application embodiment, the device for implementing the function of the access network device can be the access network device itself, or it can be a device that supports the access network device in implementing the function, such as a chip system or a combination device or component that can implement the function of the access network device. This device can be installed in the access network device. In the technical solutions provided in this application embodiment, the use of an access network device as an example to describe the technical solutions provided in this application embodiment.

[0061] The interface between the access network device and the terminal device can be a Uu interface (or air interface). Of course, in future communications, the names of these interfaces may remain unchanged or may be replaced by other names; this application does not limit this. For example, the communication between the access network device and the terminal device follows a certain protocol layer structure. For instance, the control plane protocol layer structure may include a radio resource control (RRC) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, a media access control (MAC) layer, and a physical layer; the user plane protocol layer structure may include a PDCP layer, an RLC layer, a MAC layer, and a physical layer. In one possible implementation, a service data adaptation protocol (SDAP) layer may also be included above the PDCP layer.

[0062] Access network equipment can have a single node implementing protocol layer functions such as RRC, PDCP, RLC, and MAC, or multiple nodes can implement these protocol layer functions. For example, in an evolutionary architecture, access network equipment may include one or more centralized units (CUs) and one or more distributed units (DUs), with multiple DUs centrally controlled by a single CU. As an example, the interface between the CU and DU can be called an F1 interface, where the control plane (CP) interface can be F1-C, and the user plane (UP) interface can be F1-U. CUs and DUs can be distinguished according to the protocol layers of the wireless network: for example... Figure 2a As shown, the functional settings of the PDCP layer and above are configured in the CU, while the functional settings of the protocol layers below the PDCP layer (such as the RLC layer and MAC layer) are configured in the DU.

[0063] Understandably, the above division of CU and DU processing functions according to protocol layers is merely an example; other divisions are also possible. For instance, functions of protocol layers above the RLC layer can be placed in the CU, while functions of protocol layers at and below the RLC layer can be placed in the DU. Alternatively, the CU or DU can be divided into functions with more protocol layers, or it can be divided into partial processing functions with protocol layers. In one design, some functions of the RLC layer and functions of protocol layers above the RLC layer are placed in the CU, while the remaining functions of the RLC layer and functions of protocol layers below the RLC layer are placed in the DU. In another design, the functions of the CU or DU can be divided according to service type or other system requirements, such as by latency. Functions whose processing time needs to meet latency requirements are placed in the DU, while functions that do not need to meet this latency requirement are placed in the CU. In yet another design, the CU can also have one or more core network functions. For example, the CU can be located on the network side for convenient centralized management; the DU can have multiple radio frequency functions, or the radio frequency functions can be remotely located. This application does not limit this aspect.

[0064] For example, the functionality of a CU can be implemented by a single entity, or it can be implemented by different entities. For instance, such as... Figure 2b As shown, the functions of the CU can be further divided, that is, the control plane and user plane can be separated and implemented through different entities, namely the control plane CU entity (i.e., the CU-CP entity) and the user plane CU entity (i.e., the CU-UP entity). The CU-CP entity and the CU-UP entity can be coupled with the DU to jointly complete the functions of the access network equipment. The interface between the CU-CP entity and the CU-UP entity can be an E1 interface, the interface between the CU-CP entity and the DU can be an F1-C interface, and the interface between the CU-UP entity and the DU can be an F1-U interface. A DU and a CU-UP can be connected to one CU-CP. Under the control of the same CU-CP, a DU can be connected to multiple CU-UPs, and a CU-UP can be connected to multiple DUs.

[0065] It should be noted that: in the above Figure 2a and Figure 2bIn the illustrated architecture, signaling generated by the CU can be sent to the terminal device via the DU, or signaling generated by the terminal device can be sent to the CU via the DU. The DU can directly encapsulate the signaling through the protocol layer and transmit it to the terminal device or CU without parsing it. In the following embodiments, if such signaling transmission between the DU and the terminal device is involved, the DU's sending or receiving of signaling includes this scenario. For example, signaling at the RRC or PDCP layer will eventually be processed into physical layer data and sent to the terminal device, or it may be transformed from received physical layer data. In this architecture, the RRC or PDCP layer signaling can also be considered as being sent by the DU, or by the DU and the radio frequency device.

[0066] 3) Core network elements

[0067] Taking a 5G communication system as an example, the core network elements in a CN may include access and mobility management function (AMF) network elements, session management function (SMF) network elements, user plane function (UPF) network elements, policy control function (PCF) network elements, etc., without any specific limitations.

[0068] Access and mobility management function (AMF) network elements are control plane network elements provided by the operator's network, responsible for access control and mobility management of terminal equipment accessing the operator's network. These functions include mobility state management, allocation of temporary user identities, authentication, and user management. In future communication systems, access management network elements may still be AMF network elements, or they may have other names; this application does not limit this.

[0069] The Session Management Function (SMF) network element is primarily responsible for session management in mobile networks, such as session establishment, modification, and release. Specific functions include assigning IP addresses to users and selecting user plane network elements that provide packet forwarding capabilities. In future communication systems, the Session Management Network element may still be an SMF network element, or it may have other names; this application does not impose any limitations on this.

[0070] The user plane function (UPF) network element is responsible for forwarding and receiving user data in the terminal equipment. It can receive user data from the data network and transmit it to the terminal equipment through the access network equipment; the UPF network element can also receive user data from the terminal equipment through the access network equipment and forward it to the data network. The transmission resources and scheduling functions providing services to the terminal equipment in the UPF network element are managed and controlled by the SMF network element. In future communication systems, the user plane network element may still be a UPF network element, or it may have other names; this application does not limit this.

[0071] 4) The three states of the terminal: RRC Idle, RRC Inactive, and RRC Connected.

[0072] The 3rd Generation Partnership Project (3GPP) defines three terminal states in the 5G communication standard: RRC Idle, RRC Inactive, and RRC Connected. RRC Connected can also be called RRC Active.

[0073] In RRC Connected mode, there is a dedicated RRC connection between the terminal device and the access network device.

[0074] In RRC Idle mode, there is no dedicated RRC connection between the terminal device and the access network device.

[0075] In RRC Inactive state, the terminal device moves within the Radio Access Network (RNA) without leaving the configured RNA range and can remain unaware of the access network device. The terminal device maintains its own context, and the Last Serving gNB maintains the terminal device's context, as well as the NG connections between the Last Serving gNB and the AMF and UPF. The dedicated RRC connection between the terminal device and the access network device is suspended but can be resumed later.

[0076] Similar to RRC Idle, RRC Inactive state receives content from the common search space (e.g., paging, broadcasts) and can also perform cell reselection. The principle of cell reselection in RRC Inactive state is the same as that in RRC Idle state. RRC Inactive state saves terminal device power because the UE in RRC Inactive state suspends data processing. If the UE moves within the same RNA, it does not need to interact with access network equipment, thus achieving a power consumption level similar to RRC Idle state. However, if the UE moves out of the RNA range, an RNA update process needs to be initiated. UEs in RRC Inactive state can quickly transition to RRC Connected state through the RRC Resume procedure, resulting in lower recovery latency when resuming data transmission.

[0077] The process of these three states transitioning between each other is as follows: Figure 3 As shown: RRC Idle can be transitioned to RRC Connected through the RRC recovery process, and RRC Connected can be transitioned to RRC Idle through the RRC release process. RRC Inactive can be transitioned to RRC Connected through the RRC recovery process, and RRC Connected can be transitioned to RRC Inactive through the RRC release process. RRC Recovery can also be performed in the RRC Inactive state, and RRC Inactive can be transitioned to RRC Idle through the RRC release process. For ease of description, RRC Idle, RRC Inactive, and RRC Connected will be simplified to Idle, Inactive, and Connected respectively in the following text.

[0078] 5) Small Data: If the total amount of data to be transmitted by a radio bearer that is allowed to transmit data in a power-saving state (e.g., inactive or idle state containing part of the access layer context of the connection state), is less than a pre-configured threshold, then the data of that radio bearer can be considered small data. For example, the configured threshold is 30 bytes, 50 bits, etc. Radio bearers that allow small data transmission in a power-saving state include data radio bearers (DRBs) and signaling radio bearers (SRBs). The following uses DRBs for small data transmission as an example.

[0079] 6) In this application A request can also be called Request messages, for example, an RRC request can be called an RRC request message, and an RRC recovery request can be called an RRC recovery request message. Similarly, The response can also be called Response message.

[0080] The 0, 1, 2, and 3 in the key subscripts mentioned in this application are for distinguishing keys and should not limit the key name or function. For example, K NG-RAN _1 Base station key K gNB1 RRC integrity protection key K RRCint1 RRC encryption key K RRCenc1 User plane integrity protection key K UPint1 The encryption key K for the user face UPenc1 The subscript 1 should not restrict the key name or function.

[0081] When a UE in RRC inactive state needs to transmit uplink data radio bearer (DRB) service data, it initiates an RRC recovery request message. Upon receiving the RRC recovery message, the UE restores the RRC connection, transitions from inactive to connected state, and transmits uplink DRB service data. This method results in low service data transmission efficiency. Based on this, the standard further discusses allowing data transmission on a designated DRB in inactive state without entering connected state. A designated DRB can be called a small data transmission (SDT) DRB (hereinafter referred to as SDT), which allows data transmission directly in inactive state when the total amount of data to be transmitted across all designated DRBs is below a pre-configured threshold. For this type of DRB, the UE is also allowed to perform multiple transmissions in inactive state. Otherwise, the UE needs to restore the RRC connection before data transmission can occur. A non-designated DRB can be called a non-SDT DRB (hereinafter referred to as non-SDT), which does not allow direct data transmission in inactive state; the UE needs to restore the RRC connection before data transmission can occur. Small data transmission can be either configured grant-based SDT (CG-SDT) or random access-based SDT (RA-SDT). For small data transmission based on random access, anchor base station migration or no anchor base station migration is supported.

[0082] like Figure 4 The diagram illustrates the small data transfer process, which includes at least the following steps: Step 401: The base station (gNB) sends an RRC Release message to the UE, instructing the UE to enter the Inactive state.

[0083] The RRC release message carries a suspend Config field, which may include an inactive radio network temporary identifier (I-RNTI) and CG configuration. The I-RNTI is used to uniquely identify the access stratum (AS) context within a base station.

[0084] Step 402: After receiving the RRC release message, the UE transitions from the Connected state to the Inactive state.

[0085] Optionally, the UE can also save the current base station key K. gNB0 The current RRC integrity protection key K RRCint0 Information such as this is sent to the Inactive AS context.

[0086] Step 403: When SDT data arrives, the UE triggers the first RRC connection recovery process.

[0087] For example, the UE is based on the RRC integrity protection key K RRCint0 Deducing the new K NG-RAN _1 , will K NG-RAN _1 As the existing base station key K gNB1 Furthermore, new RRC keys, new UP keys, etc., can be derived.

[0088] For example, UE is based on K gNB1 Deducing the RRC integrity protection key K RRCint1 RRC encryption key K RRCenc1 User plane integrity protection key K UPint1 The encryption key K for the user face UPenc1 User plane integrity protection key K UPint1 The encryption key K for the user face UPenc1 These are used respectively for integrity protection and encryption of user plane data; RRC integrity protection key K RRCint1 RRC encryption key K RRCenc1 They are used for integrity protection and encryption of RRC signaling, respectively.

[0089] This application will use the RRC integrity protection key K stored locally by the UE when SDT is triggered. RRCint0 RRC encryption key K RRCenc0 User plane integrity protection key K Upint0 The encryption key K for the user face Upenc0 The resulting key set is denoted as K_0; the new RRC integrity protection key K is derived from the UE. RRCint1 RRC encryption key K RRCenc1 User plane integrity protection key K UPint1 The encryption key K for the user face UPenc1 The resulting key set is denoted as K_1.

[0090] The UE can also use the RRC integrity protection key K RRCint0 Derive the message authentication code used for authentication: shortResumeMAC-I (message authentication code for Integrity, MAC-I), or resumeMAC-I.

[0091] Step 404: The UE sends a first RRC Resume Request message to the base station (gNB) and uses K... UPenc1 Encrypted uplink data. The first RRC recovery request contains I-RNTI and the resumeMAC-I or shortResumeMAC-I generated above.

[0092] The UE can send the first RRC recovery request via message 3 (Msg3) in the 4-step random access procedure, or message A (MsgA) in the 2-step random access procedure, or by configuring authorization and using K. UPenc1 Encrypted uplink data. For example, the UE checks whether the conditions for CG-SDT are met; if so, the UE triggers CG-SDT, and the UE uses the CG resources allocated in the CG configuration to send an RRC recovery request message and uses K... UPenc1 Encrypted uplink data. For example, the UE checks whether the conditions for random access RA-SDT are met; if so, the UE triggers RA-SDT, and the UE sends an RRC Resume Request message and uses K in message 3 of the 4-step random access procedure or message A of the 2-step random access procedure. UPenc1 Encrypted upstream data.

[0093] In random access scenarios, after the UE sends a first RRC recovery request on the resources provided by the 4-step random access response or the Message A resource of the 2-step random access, it starts a first timer. During the execution of the first timer, it listens for the response message of the first RRC recovery request. If the response message contains contention resolution information, it compares the received contention resolution information with the first 48 bits or all bits of the first RRC recovery request. If the two are the same or match, it indicates that contention resolution is successful, and the transmission is considered successful. If no matching contention resolution information is received before the timer expires, it indicates that contention resolution has failed, and the transmission is considered to have failed. Besides this method of contention resolution, there are other methods. For example, if downlink scheduling information from a UE-dedicated RNTI-scrambled physical downlink control channel (PDCCH) is received, it indicates that contention resolution is successful, and the transmission is considered successful. If no UE-dedicated RNTI-scrambled physical downlink control channel is received before the timer expires, it indicates that contention resolution has failed, and the transmission is considered to have failed.

[0094] In the configuration-authorized transmission scenario, after the UE sends the first RRC recovery request on the configured-authorized resource, it starts a second timer. During the second timer's operation, it listens for the response message of the first RRC recovery request. If the response message contains PDCCH information scrambled with the UE's dedicated RNTI, the transmission is considered successful. If the UE's dedicated RNTI-scrambled PDCCH is not received before the timer expires, the transmission is considered to have failed.

[0095] Step 405: After receiving the first RRC Resume Request message, the gNB uses the RRC integrity protection key K... RRCint0 The gNB derives ResumeMAC-I or shortResumeMAC-I and performs UE authentication based on either ResumeMAC-I or shortResumeMAC-I.

[0096] For example, the gNB obtains the UE's context (e.g., Inactive AS context) based on the I-RNTI and uses the same method as the UE, based on the base station key K in the context. gNB0 Derive ResumeMAC-I or shortResumeMAC-I.

[0097] If the verification is successful, the gNB uses the same method as the UE, based on the base station key K. gNB0 Deducing the new K NG-RAN _1 , will K NG-RAN _1As the existing base station key K gNB1 Furthermore, it can also deduce the keys in the key set K_1.

[0098] All uplink and downlink data transmitted in the SDT process can use the user plane integrity protection key K in K_1. UPint1 and / or the user-side encryption key K UPenc1 Perform integrity protection and / or encryption.

[0099] Step 406: The UE completes the initial transmission of SDT.

[0100] For example, during small data transmission based on configuration authorization, the gNB replies to the UE with a configuration authorization (CG) response, and the UE completes the initial transmission of CG-SDT after receiving the response.

[0101] For example, in small data transmission based on random access, the UE completes the initial transmission of RA-SDT when the random access procedure is successfully completed. Optionally, the gNB dynamically configures uplink transmission resources for subsequent transmissions for the UE through downlink control information (DCI).

[0102] Step 407: After the UE completes the initial transmission of SDT, the UE and gNB can perform subsequent transmissions of SDT.

[0103] Step 408: After the subsequent transmission of SDT is completed, gNB sends an RRC Release message to UE to terminate the SDT process.

[0104] Figure 4 The example described applies to scenarios where the gNB that sends the RRRCRelease message to switch the UE from the Connected state to the Inactive state is the same as the service gNB when the UE initiates SDT.

[0105] In another scenario, when the UE moves, the gNB that sends the RRC Resume Request message to transition the UE from Connected to Inactive state and the serving gNB when the UE initiates SDT may not be the same gNB. This application refers to the gNB that sends the RRC Resume Request message to transition the UE from Connected to Inactive state as the Last serving gNB (which can be called the anchor base station, the old serving base station, or the previous serving base station), and the serving gNB when the UE initiates SDT as the New serving base station. When the anchor base station and the New serving base station are not the same gNB, the UE can only trigger RA-SDT, not CG-SDT. After the New serving base station receives the RRC Resume Request message from the UE, it requests the UE context from the anchor base station. The anchor base station then decides whether to perform anchor relocation. If anchor relocation is performed, the anchor base station sends the entire UE context to the New serving base station, the New serving base station establishes a path with the core network, and the New serving base station becomes the new anchor base station. If anchor relocation is not performed, the New serving base station is responsible for forwarding data between the UE and the anchor base station.

[0106] like Figure 5 As shown, the process of RA-SDT without anchor point relocation is described.

[0107] Step 501: The anchor base station (Last serving gNB) sends an RRC Release message to the UE, instructing the UE to enter the Inactive state.

[0108] The RRC release message carries a suspend Config field, which includes: the inactive wireless network temporary identifier I-RNTI, and may also include CG configuration.

[0109] Step 502: After receiving the RRC release message, the UE transitions from the Connected state to the Inactive state.

[0110] Optionally, the UE can also save the current base station key K. gNB0 The current RRC integrity protection key K RRCint0 Information such as this is sent to the Inactive AS context.

[0111] Step 503: When SDT data arrives, the UE triggers the first RRC connection recovery process.

[0112] For example, the UE is based on the base station key K gNB0 Deducing the new K NG-RAN _1 , will KNG-RAN _1 As the existing base station key K gNB1 Furthermore, new RRC keys and new UP keys can be derived.

[0113] For example, based on K gNB1 Deducing the RRC integrity protection key K RRCint1 RRC encryption key K RRCenc1 User plane integrity protection key K UPint1 The encryption key K for the user face UPenc1 User plane integrity protection key K UPint1 The encryption key K for the user face UPenc1 These are used respectively for integrity protection and encryption of user plane data; RRC integrity protection key K RRCint1 RRC encryption key K RRCenc1 They are used for integrity protection and encryption of RRC signaling, respectively.

[0114] This application will store the RRC integrity protection key K locally by the UE when SDT is triggered. RRCint0 RRC encryption key K RRCenc0 User plane integrity protection key K Upint0 The encryption key K for the user face Upenc0 The resulting key set is denoted as K_0; the new RRC integrity protection key K is derived from the UE. RRCint1 RRC encryption key K RRCenc1 User plane integrity protection key K UPint1 The encryption key K for the user face UPenc1 The resulting key set is denoted as K_1.

[0115] The UE can also use the RRC integrity protection key K RRCint0 Derive the message authentication code used for authentication, such as shortResumeMAC-I or resumeMAC-I.

[0116] Step 504: The UE sends the first RRC recovery request and uses K to the new serving base station (new gNB). UPenc1 Encrypted upstream data.

[0117] The first RRC recovery request includes I-RNTI and the shortResumeMAC-I or resumeMAC-I generated above, and may also include resume Id and reason value.

[0118] The UE can send the first RRC recovery request and use K through message 3 in the 4-step random access procedure or message A in the 2-step random access procedure.UPenc1 Encrypted upstream data.

[0119] Step 505: The new serving gNB determines the last serving gNB based on the I-RNTI and sends a first request message to the last serving gNB. Correspondingly, the last serving gNB receives the first request message from the new serving gNB. The first request message is used to obtain the terminal's context or to request the last serving gNB to perform data or small data transmission.

[0120] The first request message includes I-RNTI, ResumeMAC-I or shortResumeMAC-I for verifying the UE's identity.

[0121] Optionally, the first request message may also include a Small Data Transfer Indication (SDT indication).

[0122] The first request message can be a RETRIEVE UE CONTEXT REQUEST message.

[0123] Step 506: The anchor base station (Last Serving gNB) obtains the UE context based on the I-RNTI and uses the same method as the UE, based on the RRC integrity protection key K. RRCint0 The gNB derives either ResumeMAC-I or Short ResumeMAC-I and then authenticates the UE based on either ResumeMAC-I or Short ResumeMAC-I.

[0124] If the verification is successful, the anchor base station uses the same method as the UE, based on the base station key K. gNB0 Deducing the new K NG-RAN _1 , will K NG-RAN _1 As the existing base station key K gNB1 Furthermore, new RRC keys and new UP keys (such as keys in key set K_1) can be derived. All uplink and downlink data transmitted in the SDT process can use the user plane integrity protection key K in K_1. UPint0 and / or the user-side encryption key K UPenc0 Perform integrity protection and / or encryption.

[0125] Step 507: The last serving gNB decides not to perform anchor relocation.

[0126] Step 508: The anchor base station (Last Serving gNB) sends a response message to the new serving base station (new gNB) for the first request message. Correspondingly, the new serving base station receives the response message from the anchor base station.

[0127] Optionally, the response message may include a partial context of the UE. For example, this response message could be a Retrieve UE CONTEXT RESPONSE message.

[0128] Optionally, in step 509: the new serving gNB sends an address indication (Xn-U) to the last serving gNB, which is used to notify the last serving gNB of the tunnel address for forwarding downlink data.

[0129] This prevents downlink data packets cached at the anchor base station from being lost.

[0130] If the anchor base station has the UE's downlink data, it can send the downlink data to the new serving base station, which then sends it to the UE. Of course, the new serving base station may also choose not to notify the anchor base station of the tunnel address for forwarding downlink data.

[0131] A data forwarding channel is established between the new serving base station and the anchor base station through steps 508 and 509. Then, the new serving base station sends the cached user data to the anchor base station, the anchor base station sends the user data to the core network, and the anchor base station sends the downlink data received from the core network to the UE through the new serving base station.

[0132] Step 510: After receiving the response message from step 508, the new serving gNB can send the K-type response received in step 504 to the anchor gNB. UPenc1 Encrypted upstream data.

[0133] Anchor base stations can also send decrypted uplink data to User Plane Function (UPF) network elements. For example, when an anchor base station receives data using K... UPenc1 After encrypting the uplink data, K derived in step 506 can be used. UPenc1 Decrypt the uplink data and send it to the UPF.

[0134] Optionally, in step 511: the anchor base station (Last Serving gNB) can also receive downlink data from the UPF, for example, the anchor base station sends data to the new serving base station using K... UPenc1 Encrypted downlink data.

[0135] Of course, it's also possible that there is currently no downlink data to send to the UE.

[0136] Step 512: The new serving base station (new gNB) sends a response message for the first RRC recovery request to the UE, and the terminal receives the response message from the new serving base station.

[0137] The new serving base station sends a response message for the first RRC recovery request via message 4 in the 4-step random access process or message B in the 2-step random access process. The response message may contain contention resolution information. If the core network element sends downlink data to the anchor base station, the response message may also contain downlink data.

[0138] In the RA-SDT process without anchor point relocation, the UE derives a key set K_1 before sending the first RRC Resume Request and uses the keys in key set K_1 to perform integrity protection and / or encryption of uplink data. The anchor base station also derives a key set K_1 after authenticating the UE, and in subsequent transmissions, uses the keys in key set K_1 to perform integrity protection and / or encryption of downlink data before sending it to the new serving base station.

[0139] like Figure 6 As shown, the process of performing RA-SDT for anchor point relocation is introduced.

[0140] Steps 601 to 605 and Figure 5 Steps 501 to 505 are the same and will not be repeated.

[0141] The difference between step 606 and step 506 includes: in step 606, the anchor base station will not use the derived new K. NG-RAN _1 As the existing base station key K gNB1 The rest are the same and will not be repeated.

[0142] Step 607: The anchor base station (Last Serving gNB) decides to perform anchor relocation.

[0143] Step 608: The anchor base station (Last Serving gNB) sends a response message to the new serving base station (new gNB) for the first request message. Correspondingly, the new serving base station receives the response message from the anchor base station.

[0144] Optionally, the response message includes the entire context of the UE, which may include the new K derived in step 606. NG-RAN _1 This response message is, for example, the RETRIEVE UE CONTEXTRESPONSE message.

[0145] Step 608a: The new serving base station (new gNB) uses the same method as the UE, based on K... NG-RAN _1 The keys in the key set K_1 are derived, and K is then used to derive the keys. NG-RAN _1 As the existing base station key K gNB1 .

[0146] Optionally, step 609 (same as step 509): The new serving gNB sends an address indication (Xn-U) to the last serving gNB, which is used to notify the last serving gNB of the tunnel address for forwarding downlink data.

[0147] This prevents the loss of downlink data packets cached at the anchor base station. If the anchor base station has the UE's downlink data, it can send the downlink data to the new serving base station, which then forwards it to the UE. Of course, the new serving base station may also choose not to notify the anchor base station of the tunnel address for forwarding downlink data.

[0148] Step 610: The new serving base station sends a path switch request to the core network element (e.g., AMF or SMF) to establish a path between the new serving base station and the core network.

[0149] Step 611: The new serving base station receives a path switch request acknowledge message from a core network element (e.g., AMF or SMF).

[0150] Step 612a: The new serving base station sends a UE context release message to the anchor base station (Last Serving gNB), triggering the anchor base station to release the UE context.

[0151] Step 612b: The new serving base station (new gNB) sends a response message for the first RRC recovery request to the UE, and the terminal receives the response message from the new serving base station.

[0152] The order of steps 612a and 612b is not restricted.

[0153] The new serving base station sends a response message for the first RRC recovery request via message 4 in the 4-step random access procedure or message B in the 2-step random access procedure. The response message may contain contention resolution information. If the core network element sends downlink data to the new serving base station, the response message may also contain downlink data.

[0154] The UE and the new serving base station (gNB) can perform subsequent data transmission. The new serving base station can directly transmit uplink data sent by the UE to the core network, or transmit downlink data sent by the core network to the UE.

[0155] In the RA-SDT for anchor point relocation, the UE derives the base station key K before sending the first RRC Resume Request. gNB1 A key set K_1 is used to perform integrity protection and / or encryption of uplink data. The anchor base station derives K after completing user authentication for the UE. NG-RAN 1 and key set K_1, then the anchor base station will derive a new K in step 608. NG-RAN _1 Send to the new serving base station, which then sends the new K based on the received new K. NG-RAN _1 Derive the keys in the key set K_1, and then use the keys in the key set K_1 to perform integrity protection and / or encryption on the downlink data.

[0156] When a UE in RRC Inactive state needs to send service data on a designated DRB, the UE triggers the RRC connection restoration process and sends an RRC restoration request message for the first time (i.e., the first RRC restoration request message mentioned above). If the UE needs to send service data on a non-designated DRB (i.e., non-SDT) before receiving an RRC release message, the UE triggers the RRC connection restoration process again and sends a second RRC restoration request message (hereinafter referred to as the second RRC restoration request message).

[0157] like Figure 7 As shown, a communication flow diagram is provided, illustrating that the UE triggers the RRC connection recovery process again when the first RRC connection recovery process (also known as the data or small data transmission process) in the Inactive state has not ended. Figure 7 and Figure 4 Steps 401 to 406, and may also include step 407 (excluding step 408), can be viewed as a general communication flow. For ease of diagramming, it is divided into two parts for description. Specifically, it includes the following steps: The UE determines that non-SDT data has arrived, meaning that uplink data that cannot be transmitted in the RRC inactive state has arrived.

[0158] Step 409: The UE starts the second RRC recovery process.

[0159] For example, the UE can use the base station key K gNB1 RRC Integrity Protection Key K RRCint1 The information is then updated in the Inactive AS context.

[0160] For example, the UE can be based on the base station key K gNB1 Deducing the new K NG-RAN _2 , will K NG-RAN _2 As the existing base station key K gNB2 Furthermore, new RRC keys, new UP keys, etc., can be derived. For example, the UE is based on K. gNB2 Deducing the RRC integrity protection key K RRCint2 RRC encryption key K RRCenc2 User plane integrity protection key K Upint2 The encryption key K for the user face Upenc2 This application derives a new RRC integrity protection key K from the UE. RRCint2 RRC encryption key K RRCenc2 User plane integrity protection key K Upint2 The encryption key K for the user face Upenc2 The resulting key set is denoted as K_2.

[0161] For example, the UE can also use the RRC integrity protection key K RRCint1 Derive the message authentication code resumeMAC-I or shortResumeMAC-I used for authentication.

[0162] Step 410: The UE sends a second RRC recovery request message to the base station gNB.

[0163] The second RRC recovery request includes I-RNTI and the shortResumeMAC-I or resumeMAC-I generated above.

[0164] Step 411: After receiving the second RRC Resume Request message, the base station gNB obtains the UE context based on the I-RNTI and uses the same method as the UE, based on the RRC integrity protection key K. RRCint1 The gNB derives ResumeMAC-I or shortResumeMAC-I and performs UE authentication based on either ResumeMAC-I or shortResumeMAC-I.

[0165] For example, the gNB obtains the UE context (e.g., the Inactive AS context) based on the I-RNTI and uses the same method as the UE, based on the base station key K in the context. gNB1 Derive ResumeMAC-I or shortResumeMAC-I.

[0166] If the verification is successful, the gNB uses the same method as the UE, based on the base station key K. gNB1 Deducing the new K NG-RAN _2 , will K NG-RAN _2 As the existing base station key K gNB2 Furthermore, it is also possible to deduce the keys in the key set K_2.

[0167] Optionally, step 412: The base station gNB sends a K-type... _ Downlink data that is securely protected by the key in 1.

[0168] Optionally, the downlink data may be cached data of the base station gNB before it receives the second RRC Resume Request message.

[0169] Optionally, in step 413: After receiving downlink data from the base station gNB, the UE uses the keys in the newly generated key set K_2 to perform security verification on the downlink data.

[0170] When the UE sends the second RRCResumeRequest message, the gNB may have already generated some downlink data, which is protected by security measures (e.g., encryption) using K_1. After receiving this downlink data, the UE will use the newly generated K_2 for security verification (e.g., decryption), which will trigger a security verification (e.g., decryption) error.

[0171] Step 414: The base station gNB sends a response message to the UE for the second RRC recovery request message.

[0172] The response message can be either an RRC Resume message or an RRC Release message. If the UE receives an RRC Resume message from the gNB, it switches from the inactive state to the connected state and begins transmitting non-SDT data. If the UE receives an RRC Release message from the gNB, it terminates the current SDT process, triggers the RRC connection recovery process, switches to the connected state, and then transmits non-SDT data.

[0173] Optionally, the response message is protected with security based on keys in the key set K_2.

[0174] like Figure 8 As shown, a communication flow diagram is provided, illustrating that the UE triggers the RRC connection recovery process again when the first RRC connection recovery process (also known as the data or small data transmission process) in the Inactive state has not ended. Figure 8 and Figure 5 The process (i.e., RA-SDT without anchor point relocation) can be viewed as a general communication process, which is divided into two parts for easier diagramming. Specifically, it includes the following steps: The UE determines that non-SDT data has arrived, meaning that uplink data that cannot be transmitted in the RRC inactive state has arrived.

[0175] Step 513: The UE starts the second RRC recovery process.

[0176] For example, the UE can use the base station key K gNB1 RRC Integrity Protection Key K RRCint1 The information is then updated in the Inactive AS context.

[0177] For example, the UE can be based on the base station key K gNB1 Deducing the new K NG-RAN _2 , will K NG-RAN _2 As the existing base station key K gNB2 Furthermore, new RRC keys, new UP keys, etc., can be derived. For example, the UE is based on K. gNB2 Deducing the RRC integrity protection key K RRCint2 RRC encryption key K RRCenc2 User plane integrity protection key K Upint2 The encryption key K for the user face Upenc2 This application derives a new RRC integrity protection key K from the UE. RRCint2 RRC encryption key K RRCenc2User plane integrity protection key K Upint2 The encryption key K for the user face Upenc2 The resulting key set is denoted as K_2.

[0178] For example, the UE can also use the RRC integrity protection key K RRCint1 Derive the message authentication code used for authentication, such as resumeMAC-I or shortResumeMAC-I.

[0179] Step 514: The UE sends a second RRC recovery request message to the new serving base station (new gNB).

[0180] The second RRC recovery request includes I-RNTI and the shortResumeMAC-I or resumeMAC-I generated above.

[0181] Step 515: The new serving gNB determines the last serving gNB based on the I-RNTI and sends a second request message to the last serving gNB. Correspondingly, the last serving gNB receives the second request message from the new serving gNB. The second request message is used to obtain the terminal's context or to request the last serving gNB to perform data or small data transmission.

[0182] The second request message includes I-RNTI, ResumeMAC-I or shortResumeMAC-I for verifying the UE's identity.

[0183] The second request message can be a RETRIEVE UE CONTEXT REQUEST message.

[0184] Step 516: The anchor base station (Last Serving gNB) obtains the UE context based on the I-RNTI and uses the same method as the UE, based on the RRC integrity protection key K. RRCint1 The gNB derives either ResumeMAC-I or Short ResumeMAC-I and then authenticates the UE based on either ResumeMAC-I or Short ResumeMAC-I.

[0185] For example, the anchor base station obtains the UE context (e.g., Inactive AS context) based on the I-RNTI and uses the same method as the UE, based on the RRC integrity protection key K in the context. RRCint1 Derive ResumeMAC-I or shortResumeMAC-I.

[0186] If the verification is successful, the anchor base station uses the same method as the UE, based on the base station key K. gNB1 Deducing the new K NG-RAN _2 , will K NG-RAN _2 As the existing base station key K gNB2 Furthermore, it can also deduce new RRC keys and new UP keys (such as keys in key set K_2).

[0187] Step 517: The anchor base station (Last Serving gNB) sends a response message to the new serving base station (new gNB) for the second request message. Correspondingly, the new serving base station receives the response message from the anchor base station.

[0188] Optionally, the response message may be, for example, a RETRIEVE UE CONTEXT FAILURE message.

[0189] The response message includes an RRC Release message.

[0190] Step 518: The new serving base station (new gNB) sends a response message for the second RRC recovery request to the UE, and the terminal receives the response message from the new serving base station. This response message is, for example, an RRC release message.

[0191] Optionally, step 519: The anchor base station (Last Serving gNB) sends downlink data to the new serving base station (new gNB) with security protection using the key in K_1.

[0192] Optionally, step 520: The new serving base station (new gNB) caches downlink data that is securely protected using the key in K_1.

[0193] Steps 519 and 520 are performed before step 514.

[0194] Optionally, in step 521: the new serving base station (new gNB) sends downlink data to the UE using the key in K_1 for security protection.

[0195] Optionally, in step 522: After receiving downlink data from the new serving base station (new gNB), the UE uses the key in the newly generated key set K_2 to perform security verification (e.g., decryption) on the downlink data, which will trigger a security verification (e.g., decryption) error.

[0196] Steps 521 and 522 are performed before step 518.

[0197] It can be seen that if, when the UE sends the second RRC Resume Request message, the new serving base station has already cached the downlink data from the anchor base station, and this downlink data is protected by security (e.g., encrypted) using the key in K_1, the new serving base station sends this security-protected (e.g., encrypted) downlink data to the UE. If the UE uses the key in set K_2 to perform security verification on the downlink data after receiving it, a security verification (e.g., decryption) error will occur.

[0198] like Figure 9 As shown, a communication flow diagram is provided, illustrating that the UE triggers the RRC connection recovery process again when the first RRC connection recovery process (also known as the data or small data transmission process) in the Inactive state has not ended. Figure 9 and Figure 6 The process of (i.e., RA-SDT for anchor point relocation) can be viewed as a general communication process, which is divided into two parts for easier diagramming. Specifically, it includes the following steps: The UE determines that non-SDT data has arrived, meaning that uplink data that cannot be transmitted in the RRC inactive state has arrived.

[0199] Steps 613 to 615 and Figure 5 Steps 513 to 515 are the same and will not be repeated.

[0200] The difference between step 616 and step 516 includes: in step 616, the anchor base station will not transmit the newly derived K. NG-RAN _2 As the existing base station key K gNB2 The rest are the same and will not be repeated.

[0201] Step 617: The anchor base station (Last Serving gNB) sends a response message to the new serving base station (new gNB) for the second request message. Correspondingly, the new serving base station receives the response message from the anchor base station.

[0202] Optionally, the response message includes the entire context of the UE, which may include the new K derived in step 616. NG-RAN 2. This response message is, for example, the RETRIEVE UE CONTEXTRESPONSE message.

[0203] Step 618a: The new serving base station (new gNB) can also be based on K NG-RAN _2 The keys in the key set K_2 are derived, and K is then used to derive the keys. NG-RAN _2 As the existing base station key K gNB2 .

[0204] Step 618b: The new serving base station (new gNB) sends a response message for the second RRC recovery request to the UE, and the terminal device receives the response message from the new serving base station. This response message is, for example, an RRC recovery message.

[0205] Optionally, in step 618c: the new serving gNB sends a UE context release message to the last serving gNB, triggering the last serving gNB to release the UE context.

[0206] Optionally, step 619: The new serving base station (new gNB) receives downlink data from the user plane function UPF network element.

[0207] Optionally, in step 620: the new serving base station (new gNB) uses the key in K_1 to secure the downlink data and caches the secure downlink data.

[0208] Steps 619 and 620 are performed before step 614.

[0209] Optionally, step 621: The new serving base station (new gNB) sends the downlink data, which is protected by the key in K_1, to the UE.

[0210] Optionally, in step 622: After receiving downlink data from the new serving base station (new gNB), the UE uses the key in the newly generated key set K_2 to perform security verification (e.g., decryption) on the downlink data, which will trigger a security verification (e.g., decryption) error.

[0211] The order of steps 621 and 618 is not restricted, nor is the order of steps 622 and 618.

[0212] It can be seen that if the new serving base station has already cached downlink data protected by the key in K_1 when the UE sends the second RRC Resume Request message, and sends this protected (e.g., encrypted) downlink data to the UE, a security verification (e.g., decryption) error will occur if the UE uses the key in K_2 to perform security verification on the downlink data after receiving it.

[0213] In summary, it can be seen that in various scenarios, when non-SDT data arrives during the SDT process, the terminal device will encounter downlink data security verification errors. Based on this, this application proposes several technical solutions to avoid downlink data security verification errors by the terminal device.

[0214] The following examples, in conjunction with the accompanying drawings, illustrate several examples. The features or contents marked with dashed lines in the drawings can be understood as optional operations or optional structures in the embodiments of this application.

[0215] It is understood that this application presents multiple examples, and the explanations and functions of the same words in the examples can be referenced from each other.

[0216] The new service access network equipment and anchor access network equipment are similar to the new service base station and anchor base station introduced above. The base station is a specific example of access network equipment.

[0217] like Figure 10 The diagram illustrates a communication process, including the following steps: Step 1001: When the terminal device in the inactive state determines that the first type of data has arrived, it determines the first key.

[0218] The first key is used by the terminal device to transmit the first type of data in an inactive state, or it can be used to provide security protection for the first type of data transmitted between the access network device and the terminal device in an inactive state. Security protection may include encryption protection and / or integrity protection.

[0219] The first type of data can be data transmitted on a specified DRB, data transmitted on an SDT DRB, SDT data, or small data, etc.

[0220] The first key may include, but is limited to, one or more of the following keys: K NG-RAN _1 Base station key K gNB1 RRC integrity protection key K RRCint1 RRC encryption key K RRCenc1 User plane integrity protection key K UPint1 The encryption key K for the user face UPenc1 .

[0221] Optionally, before step 1001, the terminal device may also receive an RRC release message from the access network device, and the terminal device may transition from the connected state to the inactive state.

[0222] In one example, the Figure 10 Examples can be applied Figure 4 and Figure 7 In the application scenario, steps 1001 and 403 can be the same; before step 1001, the processes described in steps 401 and 402 can also be executed.

[0223] In one example, the Figure 10 Examples can be applied Figure 6 and Figure 9 In the application scenario, steps 1001 and 603 can be the same; before step 1001, the processes described in steps 601 and 602 can also be executed. Figure 10 The access network device in the example is Figure 6 and Figure 9 The example shows a new service base station.

[0224] Step 1002: The terminal device (still in an inactive state) can send an RRC request message to the access network device, and the access network device receives the RRC request message from the terminal device.

[0225] An RRC request message is used to request the restoration of an RRC connection. An RRC request message can be an RRC restoration request message. This particular RRC request message can be referred to as the first RRC request message.

[0226] In one example, the Figure 10 Examples can be applied Figure 4 and Figure 7 In the application scenario, steps 1002 and 404 can be the same; after step 1002, the process described in step 406 can also be executed, and further, the process described in step 407 can also be executed.

[0227] In one example, the Figure 10 Examples can be applied Figure 6 and Figure 9 In application scenarios, Figure 10 The access network equipment in the middle is Figure 6 and Figure 9 In the example of the new serving base station, steps 1002 and 604 can be the same; after step 1002, the process described in step 612b can also be performed.

[0228] Step 1003: Upon receiving a first RRC request message from a terminal device in an inactive state, the access network device determines the first key.

[0229] Access network equipment uses the same method as terminal equipment to determine the first key.

[0230] In one example, the Figure 10 Examples can be applied Figure 4 and Figure 7In the application scenario, steps 1003 and 405 can be the same.

[0231] In one example, the Figure 10 Examples can be applied Figure 6 and Figure 9 In the application scenario, steps 1003 and 608a can be the same.

[0232] Step 1004: The terminal device (still in an inactive state) determines the second key upon confirming the arrival of the second type of data.

[0233] The second key is used by the terminal device to transmit the second type of data in a connected state, or it can be used to provide security protection for the second type of data transmitted between the access network device and the terminal device in a connected state. Security protection may include encryption protection and / or integrity protection.

[0234] The second type of data can be data transmitted on a non-designated DRB, or data transmitted on a non-SDT DRB, or non-SDT data, or non-small data, etc. Here, the second type of data refers to uplink second type data.

[0235] The second key may include, but is limited to, one or more of the following keys: K NG-RAN _2 Base station key K gNB2 RRC integrity protection key K RRCint2 RRC encryption key K RRCenc2 User plane integrity protection key K Upint2 The encryption key K for the user face Upenc2 .

[0236] In one example, the Figure 10 Examples can be applied Figure 4 and Figure 7 In the application scenario, steps 1004 and 409 can be the same; before step 1004, the process described in step 406 and step 407 can also be executed. It should be noted that before executing step 1004, the terminal device does not receive an RRC Release message from the access network device, which can also be understood as not executing the process described in step 408.

[0237] In one example, the Figure 10 Examples can be applied Figure 6 and Figure 9In this application scenario, steps 1004 and 613 can be the same. Before step 1004, the process described in step 612b can also be executed. It should be noted that the terminal device has not received an RRC Release message from the access network device before executing step 1004.

[0238] Step 1005: The terminal device (still in an inactive state) sends an RRC request message to the access network device, and the corresponding access network device receives the RRC request message from the terminal device.

[0239] The RRC request message is used to request the restoration of the RRC connection. This RRC restoration request message can be referred to as the second RRC restoration request message.

[0240] In one example, the Figure 10 Examples can be applied Figure 4 and Figure 7 In the application scenario, steps 1005 and 410 can be the same.

[0241] In one example, the Figure 10 Examples can be applied Figure 6 and Figure 9 In the application scenario, steps 1005 and 614 can be the same.

[0242] Step 1006: Upon receiving a second RRC request message from a terminal device in an inactive state, the access network device determines the second key.

[0243] The access network equipment uses the same method as the terminal equipment to determine the second key.

[0244] In one example, the Figure 10 Examples can be applied Figure 4 and Figure 7 In the application scenario, steps 1006 and 411 can be the same.

[0245] In one example, the Figure 10 Examples can be applied Figure 6 and Figure 9 In the application scenario, steps 1006 and 618a can be the same.

[0246] Step 1007: Before receiving the RRC response message from the access network device, the terminal device (still in an inactive state) receives the first type of data from the access network device. Correspondingly, before sending the RRC response message to the terminal device, the access network device sends the first type of data to the terminal device.

[0247] This first type of data is downlink first type of data. It is the first type of data received by the UE after sending the RRC request message and before receiving the RRC response message. This first type of data can be protected by the first key.

[0248] RRC response messages are used to respond to the RRC request messages, such as RRC recovery messages or RRC release messages.

[0249] In one example, before sending an RRC response message to the terminal device, the access network device uses the first key to protect the first type of data and then sends the first type of data to the terminal device (which is still in an inactive state).

[0250] The first type of data can be used for security protection by the access network device before or after receiving a second RRC request message from a terminal device that is in an inactive state.

[0251] If the first type of data is protected for security before the access network device receives the second RRC request message from the inactive terminal device, it is typically protected using a first key. If the first type of data is protected for security after the access network device receives the second RRC request message from the inactive terminal device, it is typically protected using a second key. In an optional example of this application, it may also be specified that the access network device uses the first key to protect the first type of data for security after receiving the second RRC request message from the inactive terminal device.

[0252] You may choose to perform either step 1008a or step 1008b.

[0253] In one optional implementation, step 1008a is performed: the terminal device (still in an inactive state) uses the first key to perform security verification on the first type of data.

[0254] like Figure 7In the example described, after the UE sends the second RRC request message (or determines the second key), when it receives downlink Type 1 data, it typically uses the newly generated second key to perform security verification (e.g., decryption) on the downlink Type 1 data. However, if the downlink Type 1 data is protected using the first key, this will cause a security verification (e.g., decryption) error. In this application, after the terminal device sends the second RRC request message but before receiving the response message (e.g., RRC recovery or RRC release message), if it receives downlink Type 1 data, it still uses the first key to perform security verification (e.g., decryption) on the downlink Type 1 data. This avoids security verification errors and prevents erroneous data from being delivered to the upper layer.

[0255] In one optional implementation, step 1008b is performed: the terminal device (still in an inactive state) discards the first type of data.

[0256] If the terminal device receives downlink data after sending the second RRC request message, it can discard the downlink data directly to avoid security verification errors and thus prevent erroneous data from being delivered to the upper layer.

[0257] Step 1009: The access network device sends an RRC response message to the terminal device, and the terminal device can receive the RRC response message from the access network device.

[0258] RRC response messages are used to respond to the RRC request messages, such as RRC recovery messages or RRC release messages.

[0259] The RRC response message can be protected with the second key.

[0260] In one example, the Figure 10 Examples can be applied Figure 4 and Figure 7 In the application scenario, steps 1009 and 414 can be the same.

[0261] In one example, the Figure 10 Examples can be applied Figure 4 and Figure 7 In the application scenario, steps 1009 and 618a can be the same.

[0262] like Figure 11As shown in another example, a communication flow suitable for a CU and DU separated architecture is introduced. This example can be applied to scenarios where the gNB sending the RRC Request message to transition the UE from Connected to Inactive state is the same as the serving gNB when the UE initiates an SDT. For explanations and functions of the names and functions of the first key, second key, first type of data, second type of data, first RRC request message, and second RRC request message, please refer to [reference needed]. Figure 10 The examples provided will not be repeated here.

[0263] Step 1101: The distributed unit (DU) (which may be referred to as gNB-DU) sends a first RRC request message to the centralized unit (CU) (e.g., the control plane CU, which may be referred to as gNB-CU-CP). Correspondingly, the centralized unit (CU) receives the first RRC request message from the DU. The first RRC request message originates from a terminal device in an inactive state and is used to request the restoration of the RRC connection.

[0264] Step 1102: Upon receiving a first RRC request message from the DU, the centralized unit (CU) determines a first key. This first key is used to transmit a first type of data with the inactive terminal device.

[0265] Step 1103: The DU sends a second RRC request (e.g., RRC recovery request) message to the CU (e.g., the control plane CU). Correspondingly, the CU receives the second RRC request message from the DU. The second RRC recovery request message originates from the inactive terminal device and is used to request the restoration of the RRC connection.

[0266] After receiving the second RRC request message sent by the UE, the DU sends the second RRC request message to the CU (e.g., the control plane CP) through the Initial ULRRC Message Transmission (INITIAL ULRRC MESSAGE TRANSFER) message.

[0267] Step 1104: The centralized unit (CU) (e.g., control plane CU) determines a second key. The second key is used to transmit a second type of data with the terminal device in the connected state.

[0268] Optionally, the CU can first authenticate the terminal device based on the information in the second RRC request message, and then determine the second key after successful authentication. This process can be referenced... Figure 7 The process of the base station authenticating the UE will not be described in detail.

[0269] Step 1105: The CU (e.g., the control plane CU or the user plane CU (which may be referred to as gNB-CU-UP)) sends a first instruction message to the DU, the first instruction message being used to instruct the DU to clear the first type of data.

[0270] Step 1106: DU responds to the first instruction information and clears (or discards, deletes, etc.) the first type of data.

[0271] In an optional example, when the CU sends the first indication information to the DU, it can be that the user plane CU sends the first indication information to the DU. For example, when the user plane CU sends the first indication information to the DU, it sends a downlink user data (DL USER DATA) message to the DU, and the downlink user data message includes the first indication information. The first indication information sent by the user plane CU to the DU can be used to instruct the DU to clear downlink data. The first indication information includes identification information (e.g., an index, which can also be understood as the label of a PDCP protocol data unit (PDU)) of the downlink data to be cleared. The downlink data to be cleared is data in the cached downlink data, and the cached downlink data is first-type data. The control plane CU derives a new second key and then sends a bearer context modification request (BEAR CONTEXT MODIFICATION REQUEST) message to the user plane CU, which carries an indication to restore the non-SDT radio bearer (RB). Upon receiving the message, the User Plane (CU) triggers the sending of a Downlink User Data (DL USER DATA) message to the DU. This DL USER DATA message carries first indication information, specifying the downlink data to be deleted. Upon receiving the DL USER DATA message, the DU deletes the downlink data indicated in the DL USER DATA message.

[0272] In one optional example, when the CU sends the first indication information to the DU, it can be that the control plane CU sends the first indication information to the DU. For example, when the control plane CU sends the first indication information to the DU, it sends a UE context setup request (UE CONTEXT SETUP REQUEST) message to the DU, and the UE context setup request message includes the first indication information. The first indication information sent by the CU to the DU can be used to instruct the DU to clear all cached downlink data, which is first-type data. Alternatively, the control plane CU can also send the first indication information to the DU separately, informing the DU to clear all cached downlink data, which is first-type data.

[0273] Step 1107: After the CU sends the first instruction information to the DU, the CU (e.g., the control plane CU) sends the RRC response message of the second RRC request message to the DU.

[0274] In existing technology, if the DU (Distribution Unit) has cached downlink data, it will continue to send it to the inactive terminal device. However, because this cached downlink data is protected by a first key, and the UE has already determined the second key before sending the second RRC request message, continuing to send this cached downlink data to the UE will lead to UE-side security verification (e.g., decryption) errors. In this example, after receiving the second RRC request message, the CU (Distribution Unit) instructs the DU to delete the cached downlink data, avoiding wasting transmission resources and preventing UE security verification errors.

[0275] like Figure 12 The diagram illustrates a communication flow, applicable to scenarios where the gNB sending the RRRCRelease message transitions the UE from Connected to Inactive state and the serving gNB is the same when the UE initiates SDT. Figure 12 exist Figure 11 A detailed description was provided based on that.

[0276] Includes the following steps: Step 1201: The control plane CU sends an RRC release message to the terminal device, and the terminal device receives the RRC release message from the control plane CU accordingly.

[0277] The RRC release message can be found in step 401, and will not be repeated here.

[0278] Step 1202 (same as step 402): The terminal device transitions from the connected state to the inactive state.

[0279] Step 1203 (and step): When the first type of data (e.g., SDT data) arrives, the UE initiates the first RRC connection recovery process.

[0280] For example, the terminal device determines a first key, which includes, but is not limited to, one or more of the following: K NG-RAN _1, Base station key K gNB1 RRC integrity protection key K RRCint1 RRC encryption key K RRCenc1 User plane integrity protection key K UPint1 The encryption key K for the user face UPenc1 .

[0281] The process of step 1203 can be referred to the process of step 403, and the repeated parts will not be described again.

[0282] Step 1204: The UE sends a first RRC request message (e.g., an RRC Resume Request) to the DU. Correspondingly, the DU receives the first RRC Resume Request message from the UE.

[0283] The process of step 1204 can be referred to the process of step 404, and the repeated parts will not be described again.

[0284] Step 1205: DU caches the uplink data (buffer UL data).

[0285] Step 1206: The DU sends a first RRC recovery request to the control plane CU. This first RRC recovery request may be carried in the initial uplink RRC message transfer (INITIAL UL RRC MESSAGE TRANSFER) message.

[0286] Step 1207: The control plane CU determines the first key.

[0287] The process of step 1207 can be referred to the process of step 405, and the repeated parts will not be described again.

[0288] Step 1208: The control plane CU sends a UE context setup request to the DU, and the DU receives the UE context setup request from the control plane CU.

[0289] Step 1209: The DU sends a UE CONTEXT SETUP RESPONSE to the control plane CU, and correspondingly, the control plane CU sends a UE context setup response to the DU.

[0290] Step 1210: The control plane CU sends a bearer context modification request to the user plane CU. In response, the user plane CU receives the bearer context modification request from the control plane CU.

[0291] Step 1211: The user plane CU sends a bearer context modification response (BEAR CONTEXTMODIFICATION RESPONSE) to the control plane CU. In response, the control plane CU receives the BEAR CONTEXT MODIFICATION RESPONSE from the user plane CU.

[0292] Step 1212: After the DU sends a UE context establishment response to the control plane CU, the DU can send uplink data to the user plane CU.

[0293] Step 1213: The UE determines that non-SDT data has arrived, i.e., uplink data that cannot be transmitted in the RRC inactive state has arrived. The UE initiates the second RRC recovery process.

[0294] For example, the terminal device determines a second key, which includes, but is not limited to, one or more of the following: K NG-RAN _2, Base station key K gNB2 RRC integrity protection key K RRCint2 RRC encryption key K RRCenc2 User plane integrity protection key K UPint2 The encryption key K for the user face UPenc2 .

[0295] Step 1214: The UE sends a second RRC Resume Request message to the DU. Correspondingly, the DU receives the second RRC Resume Request message from the UE.

[0296] The process of step 1214 can be referred to the process of step 410, and the repeated parts will not be described again.

[0297] Before the DU receives the second RRC recovery request from the UE, the DU performs steps 1215 and 1216.

[0298] Step 1215: DU receives the first type of data (downlink data) sent from the user plane CP, which is protected by the first key.

[0299] Step 1216: The DU caches the first type of data that is protected by the first key.

[0300] Step 1217: After receiving the second RRC recovery request, the DU sends the second RRC recovery request to the control plane CU. The second RRC recovery request may carry the initial uplink RRC message transmission (INITIAL UL RRC MESSAGE TRANSFER) message.

[0301] Step 1218: The control plane CU determines the second key.

[0302] The process of step 1218 can be referred to the process of step 411, and the repeated parts will not be described again.

[0303] In one alternative example, step 1219a is performed after step 1218.

[0304] Step 1219a: The control plane CU sends a recovery instruction to the user plane CU. The recovery instruction is carried in the bearer context modification request.

[0305] After receiving the recovery instruction information, the user plane CU triggers the transfer of DL USER DATA message.

[0306] The user plane CU sends a downlink user data (DL USER DATA) message to the DU, the downlink user data message including the first indication information. The first indication information sent by the user plane CU to the DU can be used to instruct the DU to clear downlink data. The first indication information includes the identification information of the downlink data to be cleared (e.g., an index, which can also be understood as the label of the PDCP PDU). The downlink data to be cleared is data in the cached downlink data, and the cached downlink data is the first type of data.

[0307] In one alternative example, step 1219b is performed after step 1218.

[0308] Step 1219b: The control plane CU sends a UE context setup request message to the DU, the UE context setup request message including the first indication information. The first indication information sent by the CU to the DU can be used to indicate that all cached downlink data, the cached downlink data being of the first type, be cleared.

[0309] In one alternative example, step 1219c is performed after step 1218.

[0310] Step 1219c: The control plane CU sends a first indication message to the DU. The first indication message can be used to instruct the DU to clear downlink data. The first indication message includes the identification information of the downlink data to be cleared (e.g., index, which can also be understood as the label of the PDCP PDU). The downlink data to be cleared is the data in the cached downlink data, and the cached downlink data is the first type of data.

[0311] Step 1220: DU responds to the first indication information and clears the corresponding first type of data.

[0312] The first type of data can be the first type of data in steps 1215 and 1216.

[0313] In another example, the serving gNB that sends the RRRCRelease message to transition the UE from Connected to Inactive state is different from the serving gNB when the UE initiates SDT, and RA-SDT does not perform anchor point relocation (e.g.) Figure 5 and Figure 8 In the scenario described in the example, after receiving the second RRC recovery request message, the anchor access network device (such as the anchor base station mentioned above) can instruct the new base station to delete the cached downlink data.

[0314] The new service access network device receives a first Radio Resource Control (RRC) request message from a terminal device that is in an inactive state. The first RRC request message is used to request the restoration of the RRC connection (refer to the process in step 504). The new service access network device receives a second RRC request message from a terminal device in an inactive state (refer to step 514); wherein, the second RRC request message is used to request the restoration of the RRC connection, and the second RRC request message is sent by the terminal device in the inactive state when there is a second type of data to be transmitted during the first type of data transmission process, and the first type of data transmission process is triggered based on the first RRC request message; The new service access network device sends a request message to the anchor access network device. The request message is used to request the context of the terminal device (refer to the process in step 515). The new service access network device receives a response message from the anchor access network device in response to the request message; Before the new service access network device sends a response message to the terminal device for the second RRC recovery request message, it clears the cached first type of data.

[0315] In one example, the response message is a RETRIEVE UE CONTEXTFAILURE message, optionally including an RRC release. Based on this response message, the new serving base station deletes all cached downlink data, which is type 1 data.

[0316] In one example, the response message includes second indication information, which instructs the new service access network device to clear all cached downlink data, wherein the cached downlink data is the first type of data; optionally, the response message is a RETRIEVE UE CONTEXT FAILURE message, which includes RRC release.

[0317] In one example, the second indication information is used to indicate the identification information (e.g., index, or PDCP PDU number) of the downlink data that needs to be cleared. The downlink data that needs to be cleared is the data in the downlink data cached by the new service access network device. The cached downlink data is the first type of data. Optionally, the response message is a downlink user data (DL USER DATA) message.

[0318] After receiving the second RRC Resume Request message from the terminal device, the new serving access network device sends a RETRIEVE UE CONTEXT REQUEST message to the anchor serving access network device. The anchor serving access network device, based on the I-RNTI in the RRC Resume Request message, knows that this is the second RRC connection recovery process initiated by the same UE. Next: In one example, the anchor serving access network replies to the new serving access network device with a RETRIEVE UE CONTEXT FAILURE message, which carries an RRRCRelease message. Upon receiving the RETRIEVE UE CONTEXT FAILURE message, the new base station can automatically delete all cached downlink data. Optionally, when replying to the new serving access network device with the RETRIEVE UE CONTEXT FAILURE message, the anchor access network device includes a second indication message in the message, instructing the new serving access network device to clear all cached downlink data. Upon receiving the indication, the new serving access network device deletes all cached downlink data.

[0319] In another example, the anchor access network device sends a DL USER DATA message to the new serving access network device, which carries information about the downlink data to be deleted (e.g., an index, which can also be understood as the label of a PDCP PDU). After receiving the DL USER DATA message, the new serving access network device deletes the downlink data specified in the message.

[0320] In existing technology, if a new serving access network device has cached downlink data, it will continue to send it to the UE. However, because this cached downlink data is protected by a first key, and the UE has already determined the second key before sending the second RRC Resume Request message, continuing to send downlink data protected by the first key to the UE will lead to a security verification error on the UE side. In this example, after the anchor access network device learns through I-RNTI that this is the second RRC recovery process initiated by the same UE, it instructs the new serving access network device to delete the cached downlink data to avoid wasting transmission resources and prevent the UE from experiencing a security verification error.

[0321] As mentioned earlier, the serving gNB that sends the RRRCRelease message to transition the UE from Connected to Inactive state is different from the serving gNB when the UE initiates SDT, and the RA-SDT that performs anchor point relocation is performed (e.g.) Figure 6 and Figure 9 In the example scenario described: On the one hand, when the UE initiates the first RRC connection recovery process, in step 606, the anchor base station deduces K. NG-RAN _1 and the keys in the key set K_1; in step 608, the anchor base station will use K NG-RAN _1 Send to the new serving base station; in step 608a, when the new serving base station receives K NG-RAN _1 Subsequently, the keys in key set K_1 will be deduced, and K_1 will be used in subsequent SDT processes to protect downlink data. Then, when the UE initiates the second RRC connection recovery process, in step 616, the anchor base station needs to authenticate the UE using the keys in key set K_1 (e.g., through the RRC integrity protection key K). RRCint1 Derivation of ResumeMAC-I or shortResumeMAC-I means that the key in the key set K_1 is used in both the anchor base station and the new serving base station, which can cause security problems.

[0322] On the other hand, although the new serving base station has already obtained the UE context through steps 605 and 608 in the SDT process, since the I-RNTI still identifies the UE and the anchor base station, when non-SDT data arrives and the UE sends the second RRCresumRequest message (e.g., step 614), the new serving base station still needs to send a RETRIEVE UE CONTEXT REQUEST message to the anchor base station (e.g., step 615), and the anchor base station will perform UE authentication (e.g., step 616). After completing the authentication, the anchor base station will reply with a RETRIEVE UE CONTEXT RESPONSE message to the new serving base station again (e.g., step 617). This will result in a large signaling overhead.

[0323] On the other hand, the anchor base station needs to keep the UE context until the non-SDT data transmission ends, which will consume the anchor base station's storage resources.

[0324] In one example, RA-SDT (e.g., for anchor point relocation) can be used to perform anchor point relocation. Figure 6 and Figure 9In the scenario described in the example, after the new serving access network device receives a pathswitch request acknowledge message from a core network element (e.g., AMF or SMF) (e.g., step 611), it can send an RRRCRelease message to the UE (still in an inactive state) (e.g., step 1312 below). Optionally, the RRRCRelease message carries an indication message that instructs the UE to initiate a new SDT process. Furthermore, the new serving access network device sends a UE CONTEXT RELEASE message to the anchor access network device (e.g., step 1313 below).

[0325] like Figure 13 As shown, a communication process is introduced, including the following steps: Step 1301: The anchor access network device (Last serving gNB) sends an RRC Release message to the UE, instructing the UE to enter the Inactive state.

[0326] Step 1301 can refer to the process of step 601, and will not be described in detail again.

[0327] Step 1302: After receiving the RRC release message, the UE transitions from the Connected state to the Inactive state.

[0328] Step 1302 can refer to the process of step 602, and will not be described in detail again.

[0329] Step 1303: When SDT data arrives, the UE triggers the first RRC connection recovery process.

[0330] For example, the first key is determined. The first key can be referred to in the above introduction and will not be repeated here.

[0331] Step 1303 can refer to the process of step 603, and will not be described in detail again.

[0332] Step 1304: The UE sends the first RRC request to the new serving access network device (new gNB).

[0333] The first RRC request message can be the first RRC recovery request message. Step 1304 can refer to the process of step 604, and will not be repeated here.

[0334] Step 1305: The new serving access network device (e.g., the new gNB) determines the anchor access network device (e.g., the last serving gNB) based on the I-RNTI and sends a first request message to the anchor access network device. Correspondingly, the anchor access network device receives the first request message from the new serving access network device. The first request message is used to obtain the terminal's context or to request the anchor access network device to perform data or small data transmission.

[0335] The first request message includes I-RNTI, ResumeMAC-I or shortResumeMAC-I for verifying the UE's identity. The first request message may be a RETRIEVE UE CONTEXT REQUEST message.

[0336] Step 1305 can be referred to the process of step 605, and will not be repeated here.

[0337] Step 1306: The anchor access network device (Last Serving gNB) determines the first key.

[0338] Step 1306 can be referred to the process of step 606, and will not be repeated here.

[0339] Step 1307 (same as step 607): The Last Serving gNB decides to perform anchor point relocation.

[0340] Step 1308: The anchor access network device (Last Serving gNB) sends a response message to the new serving access network device (new gNB) for the first request message. Correspondingly, the new serving access network device receives the response message from the anchor access network device.

[0341] Step 1308 can refer to the process of step 608, and will not be repeated here.

[0342] Step 1308a: The new service access network device determines the first key.

[0343] Step 1308a can refer to the process of step 608a, and will not be repeated here.

[0344] Optionally, step 1309 (same as step 609): The new serving gNB sends an address indication (Xn-U address indication) to the last serving gNB, which is used to notify the last serving gNB of the tunnel address for forwarding downlink data.

[0345] Step 1310 (same as step 610): The new service access network device sends a path switch request to the core network element (e.g., AMF or SMF) to establish a path between the new service access network device and the core network.

[0346] Step 1311 (same as step 611): The new service access network device receives a path switch request acknowledge message from a core network element (e.g., AMF or SMF).

[0347] Step 1312: The new service access network device sends an RRCRelease message to the UE (still in an inactive state). Optionally, the RRCRelease message carries an indication message that instructs the UE to initiate a new first-type data transmission process, such as an SDT process.

[0348] Typically, the RRC RELEASE message includes a new I-RNTI that identifies the UE and the new access network device. Downlink data is also sent during this step.

[0349] Using K RRC-int 1 and K gNB1 Updates UE Inactive AS context with K RRCint 1 and K gNB- 1 ).

[0350] Step 1313: The new serving access network device sends a UE context release message to the anchor access network device (Last Serving gNB), triggering the anchor access network device to release the UE context.

[0351] Step 1314: The UE (still in an inactive state) initiates a second RRC recovery process, for example, the second RRC recovery process is used to transmit the first type of data that was not completely sent during the first RRC recovery process.

[0352] For example, the UE determines the second key. The principle is the same as that in step 1303.

[0353] For example, the UE can use the base station key K gNB1 RRC Integrity Protection Key K RRCint1 The information is then updated in the Inactive AS context.

[0354] For example, the UE can be based on the base station key K gNB1 Deducing the new KNG-RAN _2 , will K NG-RAN _2 As the existing base station key K gNB2 Furthermore, new RRC keys, new UP keys, etc., can be derived. For example, the UE is based on K. gNB2 Deducing the RRC integrity protection key K RRCint2 RRC encryption key K RRCenc2 User plane integrity protection key K Upint2 The encryption key K for the user face Upenc2 This application derives a new RRC integrity protection key K from the UE. RRCint2 RRC encryption key K RRCenc2 User plane integrity protection key K Upint2 The encryption key K for the user face Upenc2 The resulting key set is denoted as K_2.

[0355] For example, the UE can also use the RRC integrity protection key K RRCint1 Derive the message authentication code resumeMAC-I or shortResumeMAC-I used for authentication.

[0356] Step 1315: The UE sends a second RRC request to the new serving access network device (new gNB).

[0357] The second RRC request can be a second RRC recovery request message. The second RRC recovery request includes the new I-RNTI determined in step 1312 and the shortResumeMAC-I or resumeMAC-I generated in step 1314.

[0358] K can also be sent in this step. UPenc2 Encrypted upstream data.

[0359] Step 1316: The new service access network device determines the second key. This principle is the same as that in step 1308a.

[0360] For example, the new access network device obtains the UE context based on the I-RNTI and uses the same method as the UE, based on the RRC integrity protection key K. RRCint1 The ResumeMAC-I or shortResumeMAC-I is derived, and the new service access network device authenticates the UE based on the resumeMAC-I or shortResumeMAC-I.

[0361] For example, the gNB obtains the UE context (e.g., the Inactive AS context) based on the I-RNTI and uses the same method as the UE, based on the base station key K in the context. gNB1 Derive ResumeMAC-I or shortResumeMAC-I.

[0362] If the verification is successful, the gNB uses the same method as the UE, based on the base station key K. gNB1 Deducing the new K NG-RAN _2 , will K NG-RAN _2 As the existing base station key K gNB2 Furthermore, it is also possible to deduce the keys in the key set K_2.

[0363] Step 1317 (same as step 612b): The new serving access network device (new gNB) sends a response message for the second RRC request to the UE, and the terminal receives the response message from the new serving access network device.

[0364] For example, the response message could be message B or message 4, and the new service access network device could also send downlink data to the UE.

[0365] This response message marks the end of the initial transmission of RA-SDT.

[0366] Optionally, the UE can also perform subsequent transmission of SDT data.

[0367] Step 1318: The UE determines that non-SDT data has arrived, i.e., uplink data that cannot be transmitted in the RRC inactive state has arrived. The UE initiates the third RRC recovery process.

[0368] The UE determines a third key, which includes, but is not limited to, one or more of the following keys: K NG-RAN _3 Access network device key K gNB3 RRC integrity protection key K RRCint3 RRC encryption key K RRCenc3 User plane integrity protection key K Upint3 The encryption key K for the user face Upenc3 .

[0369] Step 1318 can refer to the process of step 613, except that the name of the key changes from the original index 1 to index 2, and from the original index 2 to index 3. The principle is the same, and the specific process will not be described in detail.

[0370] Step 1319: The UE sends a third RRC recovery request message to the new serving access network device (new gNB).

[0371] The process in step 1319 can be referred to in step 614, and will not be repeated here. The third RRC recovery request message includes the new I-RNTI determined in step 1312.

[0372] Step 1320: The new serving base station determines the third key.

[0373] For example, the new service access network device can determine that the third RRC Request and the second RRC Request come from the same UE based on I-RNT1, and can do so based on the RRC integrity protection key K. RRCint2 The ResumeMAC-I or shortResumeMAC-I is derived, and the new service access network device authenticates the UE based on the resumeMAC-I or shortResumeMAC-I.

[0374] For example, the new serving base station obtains the UE context (e.g., Inactive AS context) based on the I-RNTI and uses the same method as the UE, based on the base station key K in the context. gNB2 Derive ResumeMAC-I or shortResumeMAC-I.

[0375] If the verification is successful, the gNB uses the same method as the UE, based on the base station key K. gNB2 Deducing the new K NG-RAN _3 , will K NG-RAN _3 As the existing base station key K gNB3 Furthermore, it is also possible to deduce the keys in the key set K_3.

[0376] Step 1321: The new service access network device sends an RRC recovery message to the UE.

[0377] In the existing technology 2, the previous serving base station and the new base station may use the KRRCint_1 key simultaneously, posing a security risk. Furthermore, the new base station needs to repeatedly request the UE context from the previous serving base station, resulting in significant signaling overhead. In this example, after completing the path handover, the new base station sends an RCRelease message to the UE and assigns a new I-RNTI to the UE. This I-RNTI identifies both the UE and the new base station. Therefore, when non-SDT data arrives during subsequent SDT processes, the new base station, upon receiving the RCResumeRequest message carrying this I-RNTI, can directly authenticate the UE, avoiding the repeated sending of UE CONTEXT REQUEST messages to the previous serving base station and preventing security issues caused by the same key being used on different base stations. Additionally, after completing the path handover, the new base station can inform the previous serving base station to clear the UE's context, saving the previous serving base station's storage resources.

[0378] In another example, RA-SDT (e.g., for anchor point relocation) can be used to perform anchor point relocation. Figure 6 and Figure 9 In the scenario described in the example, when the last serving access network device decides to perform anchor point relocation after receiving the RETRIEVE UE CONTEXT REQUEST message, it carries the I-RNTI in the RETRIEVE UE CONTEXT RESPONSE message replied to the new access network device.

[0379] The new service access network device receives a first Radio Resource Control (RRC) request message from a terminal device that is in an inactive state (refer to the process in step 604). The first RRC request message is used to request the restoration of the RRC connection. The new service access network device receives a second RRC request message from a terminal device in an inactive state (refer to step 614); wherein, the second RRC request message is used to request the restoration of the RRC connection, and the second RRC request message is sent by the terminal device in the inactive state when there is a second type of data to be transmitted during the first type of data transmission process, and the first type of data transmission process is triggered based on the first RRC request message; the second RRC request message includes a first identifier, which is used to determine the context of the terminal device; the first identifier may be an I-RNTI, which may come from the I-RNTI carried in the first RRC request message in step 604, or from the I-RNTI carried in the terminal device context response message in step 608.

[0380] The new service access network device determines the context of the terminal device based on the first identifier. The context of the terminal device is the context of the terminal device received by the new service access network device from the anchor access network device during the first type of data transmission (refer to the process in step 608). The new service access network device determines a second key based on the information in the context of the terminal device. The second key is used to transmit the second type of data with the terminal device in the connected state.

[0381] This scheme can be applied to anchor point relocation scenarios. After receiving the first RRC request message from the terminal device, and before receiving the second RRC request message from the terminal device, the new service access network device can also receive a terminal device context acquisition response message from the anchor access network device. This terminal device context acquisition response message includes the complete context of the terminal device. This process can be referred to in step 608 and will not be repeated here.

[0382] In one optional example, after receiving the first RRC request message from the terminal device and before receiving the second RRC request message from the terminal device, the new serving access network device may also receive the first identifier from the anchor access network device and associate the first identifier with the context of the terminal device. For example, when the new serving access network device receives the first identifier from the anchor access network device, it may receive a RETRIEVE UE CONTEXT RESPONSE message from the anchor access network device, which includes the first identifier. For example, the first identifier may be carried in step 608, such as an I-RNTI. As another example, the anchor access network device may send the first identifier to the new serving access network device separately or in a new message.

[0383] The new serving access network device (NSN) determines the second key instead of the anchor access network device (which is no longer required to determine the second key, thus eliminating the need for steps 615-618a). This avoids security issues arising from the use of the same key in different access network devices. The process by which the new NSN determines the second key can be referenced from the process performed by the anchor base station in step 616, and will not be described in detail here. After determining the second key, the new NSN can also send an RRC recovery message to the UE.

[0384] In an optional example, the first RRC request message includes the first identifier (e.g., the first identifier is included in step 604, such as I-RNTI); after receiving the first RRC request message from the terminal device and before receiving the second RRC request message from the terminal device, the new serving access network device may also receive a RETRIEVE UE CONTEXT RESPONSE message from the anchor access network device (e.g., step 608), triggering the association of the first identifier with the context of the terminal device. For example, the RETRIEVE UE CONTEXT RESPONSE message includes third indication information, which is used to indicate that the terminal device is authenticated, or to indicate that the new serving access network device authenticates the terminal device during the second RRC recovery process, or to indicate that the new serving base station saves the first identifier from the first RRC request message, or to indicate that the new serving access network device associates the first identifier with the context of the terminal device.

[0385] After receiving a third indication message or a terminal device context response (RETRIEVE UECONTEXT RESPONSE) message, the new service access network device can save the first identifier, such as I-RNTI.

[0386] Figure 6 and Figure 9 The examples show that both the anchor base station and the new serving base station use the first key (e.g., K). RRCint_1 In the case of using a different key, there are security issues. Furthermore, the new serving base station needs to repeatedly request the UE context from the anchor base station, which leads to significant signaling overhead. In this example, the new serving base station sends the I-RNTI to itself in the RETRIEVE UECONTEXT RESPONSE message, or it receives the I-RNTI from the UE. Subsequently, when second-type data (e.g., non-SDT data) arrives, the new serving base station, upon receiving a second RRCResumeRequest message containing the new I-RNTI, can directly authenticate the UE. This avoids the new serving base station repeatedly requesting the UE context from the anchor base station and also prevents security issues caused by the same key being used on different base stations.

[0387] In another example, RA-SDT (e.g., when performing anchor point relocation) can be used. Figure 6 and Figure 9 In the scenario described in the example, after the new access network device completes the path handover, it allocates a new I-RNTI to the UE. This new I-RNTI can be carried in the RRCReconfiguration message or in a new RRC message.

[0388] The new service access network device receives a first Radio Resource Control (RRC) request message from a terminal device in an inactive state. The first RRC request message is used to request the restoration of the RRC connection. The first RRC request message includes a first identifier, which is used to determine the context of the terminal device (refer to the process in step 604). The first identifier may be an I-RNTI. The new service access network device sends a second identifier to the terminal device, which is used to determine the context of the terminal device; the second identifier may be a new I-RNTI. This new I-RNTI may be carried in an RRCReconfiguration message or in a new RRC message.

[0389] The new service access network device receives a second RRC request message from a terminal device in an inactive state (refer to step 614); wherein, the second RRC request message is used to request the restoration of the RRC connection, and the second RRC request message is sent by the terminal device in the inactive state when there is a second type of data to be transmitted during the first type of data transmission process, and the first type of data transmission process is triggered based on the first RRC request message; the second RRC request message includes the second identifier (it should be noted that in step 614, the second RRC restoration request message still carries the first identifier (e.g., I-RNTI), while in this example it carries the second identifier (e.g., a new I-RNTI) assigned to the UE by the new service access network device); The new service access network device determines the context of the terminal device based on the second identifier, wherein the context of the terminal device is the one that receives the data sent by the anchor access network device during the small data transmission process; The new service access network device determines a second key based on information in the context of the terminal device. The second key is used to transmit a second type of data with the terminal device in the connected state.

[0390] Optionally, when the new service access network device sends the second identifier to the terminal device, it may also send the next-hop link count (NCC) value to the terminal device.

[0391] The new serving access network device (NSN) determines the second key instead of the anchor access network device (which is no longer required to determine the second key, thus eliminating the need for steps 615-618a). This avoids security issues caused by the same key being used in different access network devices and also saves storage resources on the anchor access network device. The process by which the new NSN determines the second key can be referenced from the process performed by the anchor base station in step 616, and will not be described in detail here. After determining the second key, the new NSN can also send an RRC recovery message to the UE.

[0392] Figure 6 and Figure 9 In the previous example, the anchor base station and the new serving base station might both use the first key (e.g., the KRRCint_1 key), which poses a security risk. Furthermore, the new serving base station would need to repeatedly request the UE context from the anchor base station, leading to significant signaling overhead. In this example, after completing the path handover, the new serving base station assigns a new I-RNTI to the UE. Subsequently, when second-type data (e.g., non-SDT data) arrives, the new serving base station, upon receiving a second RRCResumeRequest message containing the new I-RNTI, can directly authenticate the UE. This avoids the new serving base station repeatedly requesting the UE context from the anchor base station and also prevents the security issues caused by the same key being used on different base stations.

[0393] The methods of the embodiments of this application have been introduced above. The apparatus of the embodiments of this application will be described below. The methods and apparatus are based on the same technical concept. Since the principles of solving the problem by the methods and apparatus are similar, the implementation of the apparatus and methods can refer to each other, and the repeated parts will not be described again.

[0394] Based on the above method examples, the embodiments of this application can divide the device into functional modules. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one module. These modules can be implemented in hardware or as software functional modules. It should be noted that the module division in the embodiments of this application is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0395] Based on the same technical concept as the method described above, see [link to relevant documentation]. Figure 14A schematic diagram of a communication device 1400 is provided. The device 1400 may include a processing module 1410, and optionally, a receiving module 1420a, a transmitting module 1420b, and a storage module 1430. The processing module 1410 may be connected to the storage module 1430, the receiving module 1420a, and the transmitting module 1420b, respectively. The storage module 1430 may also be connected to the receiving module 1420a and the transmitting module 1420b.

[0396] In one example, the receiving module 1420a and the transmitting module 1420b described above can also be integrated together and defined as a transceiver module.

[0397] In one example, the device 1400 can be a terminal device, or a chip or functional unit applied in a terminal device. The device 1400 has any of the functions of the terminal device described above; for example, the device 1400 can perform the aforementioned... Figure 10 , Figure 11 , Figure 12 , Figure 13 The various steps performed by the terminal device in the method.

[0398] The receiving module 1420a can perform the receiving actions performed by the terminal device in the above method embodiment.

[0399] The sending module 1420b can perform the sending action executed by the terminal device in the above method embodiment.

[0400] The processing module 1410 can execute other actions besides sending and receiving actions performed by the terminal device in the above method embodiments.

[0401] In one example, the processing module 1410 is configured to determine a first key when the device, in an inactive state, determines that a first type of data has arrived; wherein the first key is used by the device to transmit the first type of data in the inactive state; and to determine a second key when a second type of data has arrived. The sending module 1420b is configured to send an RRC request message to the access network device; wherein the second key is used by the device to transmit the second type of data in a connected state; the RRC request message is used to request the restoration of the RRC connection. The receiving module 1420a is configured to receive the first type of data from the access network device before receiving an RRC response message from the access network device. The processing module 1410 is further configured to perform security verification on the first type of data using the first key; wherein the RRC response message is used to respond to the RRC request message.

[0402] In one example, the processing module 1410 is configured to determine a first key when the device, in an inactive state, determines that a first type of data has arrived; wherein the first key is used by the device to transmit the first type of data in the inactive state; and to determine a second key when a second type of data has arrived. The sending module 1420b is configured to send an RRC request message to the access network device; wherein the second key is used by the device to transmit the second type of data in a connected state; the RRC request message is used to request the restoration of the RRC connection. The receiving module 1420a is configured to receive the first type of data from the access network device before receiving an RRC response message from the access network device; wherein the RRC response message is used to respond to the RRC request message. The processing module 1410 is further configured to discard the first type of data.

[0403] For example, a storage module may include one or more memories, which can be devices in one or more devices or circuits used to store programs or data. The storage module can be a register, cache, or RAM, and can be integrated with the processing module. The storage module can also be ROM or other types of static storage devices capable of storing static information and instructions, and can be independent of the processing module.

[0404] The transceiver module can be an input or output interface, pins, or circuits, etc.

[0405] In one example, the device 1400 can be a centralized unit CU, or a chip or functional unit applied in the centralized unit CU. The device 1400 has any function of the centralized unit CU in the above method; for example, the device 1400 can perform the above-described... Figure 10 , Figure 11 , Figure 12 , Figure 13 The methods are implemented by the centralized unit (CU) for each step.

[0406] The receiving module 1420a can perform the receiving action performed by the centralized unit CU in the above method embodiment.

[0407] The transmitting module 1420b can perform the transmitting action executed by the centralized unit CU in the above method embodiment.

[0408] The processing module 1410 can execute other actions besides the sending and receiving actions performed by the centralized unit CU in the above method embodiment.

[0409] In one example, the processing module 1410 is configured to determine a first key upon receiving a first RRC request message from a DU; wherein the first RRC request message originates from a terminal device in an inactive state, the first RRC request message is used to request the restoration of an RRC connection, and the first key is used to transmit a first type of data with the terminal device in the inactive state. The receiving module 1420a is configured to receive a second RRC request message from the DU; wherein the second RRC restoration request message originates from the terminal device in the inactive state, and the second RRC request message is used to request the restoration of an RRC connection. The processing module 1410 is further configured to determine a second key, the second key being used to transmit a second type of data with the terminal device in a connected state. The sending module 1420b is configured to send an RRC response message of the second RRC request message to the DU after sending first indication information; wherein the first indication information is used to instruct the DU to clear the first type of data.

[0410] In one example, the device includes a control plane CU and a user plane CU.

[0411] In one example, the user plane CU sends first indication information to the DU, including: the user plane CU sending a downlink user data message to the DU, the downlink user data message including the first indication information.

[0412] In one example, the control plane CU sends first indication information to the DU, including: the control plane CU sending a UE context establishment request message to the DU, the UE context establishment request message including the first indication information.

[0413] For example, a storage module may include one or more memories, which can be devices in one or more devices or circuits used to store programs or data. The storage module can be a register, cache, or RAM, and can be integrated with the processing module. The storage module can also be ROM or other types of static storage devices capable of storing static information and instructions, and can be independent of the processing module.

[0414] The transceiver module can be an input or output interface, pins, or circuits, etc.

[0415] In one example, the device 1400 can be a new service access network device, or it can be a chip or functional unit applied in a new service access network device. The device 1400 has any of the functions of the new service access network device in the above method; for example, the device 1400 can perform the above-described... Figure 10 , Figure 11 , Figure 12 , Figure 13The method involves the various steps performed by the new service access network device.

[0416] The receiving module 1420a can perform the receiving action performed by the new service access network device in the above method embodiment.

[0417] The sending module 1420b can perform the sending action performed by the new service access network device in the above method embodiment.

[0418] The processing module 1410 can execute other actions besides sending and receiving actions among the actions performed by the new service access network device in the above method embodiments.

[0419] In one example, the receiving module 1420a is configured to receive a first Radio Resource Control (RRC) request message from a terminal device in an inactive state, the first RRC request message being used to request the restoration of an RRC connection; and to receive a second RRC request message from the terminal device in an inactive state; wherein the second RRC request message is used to request the restoration of an RRC connection, and the second RRC request message is sent by the terminal device in the inactive state when there is a second type of data to be transmitted during a first type of data transmission process, the first type of data transmission process being triggered based on the first RRC request message. The sending module 1420b is configured to send a request message to the anchor access network device, the request message being used to request the acquisition of the context of the terminal device. The receiving module 1420a is further configured to receive a response message from the anchor access network device in response to the request message. The processing module 1410 is configured to clear the cached first type of data before sending the response message of the second RRC restoration request message to the terminal device.

[0420] In one example, the response message includes second indication information; wherein: the second indication information is used to instruct the new service access network device to clear all cached downlink data, the cached downlink data being the first type of data; or, the second indication information is used to indicate the identification information of the downlink data to be cleared, the downlink data to be cleared being data in the downlink data cached by the new service access network device, the cached downlink data being the first type of data.

[0421] In one example, the response message is a UE context acquisition failure message; or, the response message is a downlink user data message.

[0422] For example, a storage module may include one or more memories, which can be devices in one or more devices or circuits used to store programs or data. The storage module can be a register, cache, or RAM, and can be integrated with the processing module. The storage module can also be ROM or other types of static storage devices capable of storing static information and instructions, and can be independent of the processing module.

[0423] The transceiver module can be an input or output interface, pins, or circuits, etc.

[0424] As a possible product form, the device can be implemented using a general bus architecture.

[0425] like Figure 15 As shown, a schematic block diagram of a communication device 1500 is provided.

[0426] The device 1500 may include a processor 1510, and optionally, a transceiver 1520 and a memory 1530. The transceiver 1520 may be used to receive programs or instructions and transmit them to the processor 1510, or the transceiver 1520 may be used for communication interaction between the device 1500 and other communication devices, such as exchanging control signaling and / or service data. The transceiver 1520 may be a code and / or data read / write transceiver, or it may be a signal transmission transceiver between the processor and a transceiver. The processor 1510 and the memory 1530 are electrically coupled.

[0427] In one example, the device 1500 can be a terminal device or a chip applied in a terminal device. It should be understood that the device has any of the functions of the terminal device described above; for example, the device 1500 can perform the aforementioned... Figure 10 , Figure 11 , Figure 12 , Figure 13 The method comprises the various steps executed by the terminal device. For example, the memory 1530 is used to store computer programs; the processor 1510 can be used to call the computer programs or instructions stored in the memory 1530 to execute the method executed by the terminal device in the above example, or to execute the method executed by the terminal device in the above example via the transceiver 1520.

[0428] In one example, the device 1500 can be a centralized unit (CU) or a chip applied within the centralized unit (CU). It should be understood that the device has any of the functions of the centralized unit (CU) in the above method; for example, the device 1500 can perform the aforementioned... Figure 10 , Figure 11 , Figure 12 , Figure 13The methods described herein are executed by a centralized unit (CU) in various steps. For example, the memory 1530 is used to store a computer program; the processor 1510 can be used to call the computer program or instructions stored in the memory 1530 to execute the method executed by the centralized unit (CU) in the above example, or to execute the method executed by the centralized unit (CU) in the above example via the transceiver 1520.

[0429] Figure 14 The processing module 1410 can be implemented by the processor 1510.

[0430] Figure 14 The receiving module 1420a and the transmitting module 1420b can be implemented using the transceiver 1520. Alternatively, the transceiver 1520 can be divided into a receiver and a transmitter, with the receiver performing the function of the receiving module and the transmitter performing the function of the transmitting module.

[0431] Figure 14 The storage module 1430 can be implemented through the memory 1530.

[0432] In one example, the device 1500 can be a new service access network device or a chip applied in a new service access network device. It should be understood that the device has any of the functions of the new service access network device in the above method; for example, the device 1500 can perform the above-described... Figure 10 , Figure 11 , Figure 12 , Figure 13 The method comprises the various steps executed by the new service access network device. For example, the memory 1530 is used to store computer programs; the processor 1510 can be used to call the computer programs or instructions stored in the memory 1530 to execute the method executed by the new service access network device in the above example, or to execute the method executed by the new service access network device in the above example via the transceiver 1520.

[0433] Figure 14 The processing module 1410 can be implemented by the processor 1510.

[0434] Figure 14 The receiving module 1420a and the transmitting module 1420b can be implemented using the transceiver 1520. Alternatively, the transceiver 1520 can be divided into a receiver and a transmitter, with the receiver performing the function of the receiving module and the transmitter performing the function of the transmitting module.

[0435] Figure 14 The storage module 1430 can be implemented through the memory 1530.

[0436] As one possible product form, the device can be implemented using a general-purpose processor (which can also be called a chip or chip system).

[0437] In one possible implementation, the general-purpose processor implementing the device for a terminal device or a centralized unit CU includes: a processing circuit (which may also be called a processor); optionally, it further includes: an input / output interface internally connected and communicating with the processing circuit, and a storage medium (which may also be called a memory), the storage medium being used to store instructions executed by the processing circuit to execute the method executed by the terminal device or centralized unit CU in the above example.

[0438] Figure 14 The processing module 1410 can be implemented through a processing circuit.

[0439] Figure 14 The receiving module 1420a and the transmitting module 1420b can be implemented through input / output interfaces. Alternatively, the input / output interface can be divided into an input interface and an output interface, with the input interface performing the function of the receiving module and the output interface performing the function of the transmitting module.

[0440] Figure 14 The storage module 1430 can be implemented using a storage medium.

[0441] As one possible product form, the apparatus of this application embodiment can also be implemented using one or more FPGAs (Field Programmable Gate Arrays), PLDs (Programmable Logic Devices), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits capable of performing the various functions described throughout this application.

[0442] This application also provides a computer-readable storage medium storing a computer program that, when executed by a computer, enables the computer to perform the aforementioned communication method. Alternatively, the computer program includes instructions for implementing the aforementioned communication method.

[0443] This application also provides a computer program product, including: computer program code, which, when run on a computer, enables the computer to execute the communication method provided above.

[0444] Furthermore, the processor mentioned in the embodiments of this application can be a central processing unit (CPU), a baseband processor, and the baseband processor and CPU can be integrated together or separate. It can also be a network processor (NP) or a combination of CPU and NP. The processor may further include hardware chips or other general-purpose processors. The aforementioned hardware chip can be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The aforementioned PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), and other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., or any combination thereof. The general-purpose processor can be a microprocessor or any conventional processor.

[0445] The memory mentioned in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memories described in this application are intended to include, but are not limited to, these and any other suitable types of memory.

[0446] The transceiver mentioned in the embodiments of this application may include a separate transmitter and / or a separate receiver, or the transmitter and receiver may be integrated into one unit. The transceiver can operate under the instruction of a corresponding processor. Optionally, the transmitter may correspond to a transmitter in a physical device, and the receiver may correspond to a receiver in a physical device.

[0447] Those skilled in the art will recognize that the method steps and units described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the steps and components of each embodiment have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0448] In the embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the couplings or direct couplings or communication connections shown or discussed may be indirect couplings or communication connections through some interfaces, apparatuses, or units, or they may be electrical, mechanical, or other forms of connection.

[0449] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of the embodiments of this application, depending on actual needs.

[0450] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0451] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0452] In this application, "and / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "Multiple" in this application refers to two or more. Furthermore, it should be understood that in the description of this application, terms such as "first" and "second" are used only for descriptive purposes and should not be construed as indicating or implying relative importance or order.

[0453] Although preferred embodiments of this application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this application.

[0454] Obviously, those skilled in the art can make various modifications and variations to the embodiments of this application without departing from the spirit and scope of the embodiments of this application. Therefore, if these modifications and variations to the embodiments of this application fall within the scope of the claims of this application and their equivalents, this application also intends to include these modifications and variations.

Claims

1. A method of communication, comprising: The method includes: Upon receiving a first RRC request message from a DU, the centralized unit (CU) determines a first key; wherein the first RRC request message originates from a terminal device in an inactive state, the first RRC request message is used to request the restoration of the RRC connection, and the first key is used to transmit a first type of data with the terminal device in the inactive state. The centralized unit (CU) receives a second RRC request message from the DU and determines a second key; wherein the second RRC request message comes from the terminal device in the inactive state, the second RRC request message is used to request the restoration of the RRC connection, and the second key is used to transmit a second type of data with the terminal device in the connected state; After the centralized unit (CU) sends the first indication information to the DU, it sends an RRC response message of the second RRC request message to the DU; wherein, the first indication information is used to instruct the DU to clear the first type of data.

2. The method as described in claim 1, characterized in that, The CU includes a control plane CU and a user plane CU; Sending first indication information to the DU includes: The user plane CU sends a first instruction message to the DU; or... The control plane CU sends a first instruction message to the DU.

3. The method as described in claim 2, characterized in that, The user plane CU sends a first indication message to the DU, including: The user plane CU sends a downlink user data message to the DU, and the downlink user data message includes the first indication information.

4. The method as described in claim 2, characterized in that, The control plane CU sends first instruction information to the DU, including: The control plane CU sends a UE context establishment request message to the DU, and the UE context establishment request message includes the first indication information.

5. A communication device, characterized in that, include: Implement the functional modules described in any one of claims 1-4.

6. A communication device, characterized in that, Includes a processor, which is coupled to a memory; The memory is used to store computer programs or instructions; The processor is configured to execute some or all of the computer programs or instructions in the memory, and when the some or all of the computer programs or instructions are executed, to implement the method as described in any one of claims 1-4.

7. A communication device, characterized in that, Including processor and memory; The memory is used to store computer programs or instructions; The processor is configured to execute some or all of the computer programs or instructions in the memory, and when the some or all of the computer programs or instructions are executed, to implement the method as described in any one of claims 1-4.

8. A chip system, characterized in that, The chip system includes: a processing circuit; the processing circuit is coupled to a storage medium; The processing circuit is configured to execute part or all of the computer program or instructions in the storage medium, and when the part or all of the computer program or instructions are executed, to implement the method as described in any one of claims 1-4.

9. A computer-readable storage medium, characterized in that, Used to store a computer program, the computer program including instructions for implementing the method of any one of claims 1-4.

10. A computer program product, characterized in that, The computer program product includes: computer program code, which, when run on a computer, causes the computer to perform the method as described in any one of claims 1-4.

Citation Information

Patent Citations

  • Method, base station, equipment and system for recovering connection of inactive terminal

    CN109699050A

  • Security verification when resuming an RRC connection

    CN111886885A