WO2021203439A1

WO2021203439A1 - Data transmission method, terminal device and network device

Info

Publication number: WO2021203439A1
Application number: PCT/CN2020/084308
Authority: WO
Inventors: 林雪; 王淑坤; 石聪; 李海涛
Original assignee: Oppo广东移动通信有限公司
Priority date: 2020-04-10
Filing date: 2020-04-10
Publication date: 2021-10-14
Also published as: CN115004739A

Abstract

The embodiments of the present application relate to a data transmission method, a terminal device, and a communication device. The method comprises: when a key is valid, encrypting data by using the key, and sending the encrypted data by using a pre-configured resource. According to the embodiments of the present application, small data transmission of a terminal device in an inactive state can be realized.

Description

Data transmission method, terminal equipment and network equipment

Technical field

This application relates to the field of communications, and more specifically, to data transmission methods, terminal devices, and network devices.

Background technique

In the fifth-generation 5G New Radio (NR, New Radio) system, the radio resource control (RRC, Radio Resource Control) state of terminal equipment is divided into three types, namely: RRC_IDLE (RRC idle state), RRC_INACTIVE (RRC inactive state) State), RRC_CONNECTED (RRC connected state). Among them, the RRC_INACTIVE state is a new state introduced by the 5G system from the perspective of energy saving. For the UE in the RRC_INACTIVE state, the radio bearer and all radio resources will be released, but the UE side and the base station side retain the UE access context to quickly restore the RRC connection. Generally, the UE with infrequent data transmission is kept in the RRC_INACTIVE state. Before the 5G standard Rel-16 released by the 3rd Generation Partnership Project (3GPP, 3rd Generation Partnership Project), the UE in the RRC_INACTIVE state did not support data transmission. When the uplink data arrives, the UE needs to restore the connection and wait for the data transmission to be completed. Then release to RRC_INACTIVE state. For UEs with small data volume and low transmission frequency, such a transmission mechanism will cause unnecessary power consumption and signaling overhead. Therefore, Rel-17 initiated a project to carry out research on small data transmission under RRC_INACTIVE. Small data can refer to data with a small amount of data sent by the UE in the RRC_INACTIVE state and/or data with low transmission frequency. Currently, there is no clear method for the transmission of this type of data.

Summary of the invention

The embodiments of the present application provide a data transmission method, a terminal device, and a communication device, which can realize the transmission of small data in an inactive state by the terminal device.

The embodiment of the application proposes a data transmission method, which is applied to a terminal device, and includes:

When the key is valid, the key is used to encrypt the data, and the pre-configured resource is used to send the encrypted data.

The embodiment of the application proposes a data transmission method, which is applied to a network device, and includes:

Sending a pre-configured resource and/or a next hop link count NCC used to generate a key, where the configured pre-configured resource and key are used for the terminal device to send data.

An embodiment of the present application proposes a terminal device, including:

The transmission module is used to encrypt data with the key when the key is valid, and use pre-configured resources to send the encrypted data.

An embodiment of the application proposes a network device, including:

The configuration module is used to send a pre-configured resource and/or a next hop link count NCC for generating a key, where the pre-configured resource and the key are used for the terminal device to send data.

The embodiment of the present application proposes a terminal device, including: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute any of the above-mentioned data transmission methods. The method described.

The embodiment of the application proposes a network device, including: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute any of the above data transmission methods. The method described.

An embodiment of the present application proposes a chip, including a processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the method described in any of the above data transmission methods.

The embodiment of the present application proposes a computer-readable storage medium for storing a computer program, and the computer program enables a computer to execute the method described in any of the above-mentioned data transmission methods.

The embodiment of the present application proposes a computer program product, including computer program instructions, which cause a computer to execute the method described in any of the above data transmission methods.

An embodiment of the present application proposes a computer program that enables a computer to execute the method described in any of the above data transmission methods.

In the embodiment of the present application, when the key is valid, the terminal device uses the key to encrypt data, and uses the pre-configured resource to send the encrypted data, so as to realize the transmission of small data in the inactive state.

Description of the drawings

Fig. 1 is a schematic diagram of an application scenario of an embodiment of the present application.

Fig. 2 is an implementation flowchart of a data transmission method 200 according to an embodiment of the present application.

FIG. 3 is an implementation flowchart of a data transmission method 300 according to an embodiment of the present application.

FIG. 4 is a schematic diagram 1 of an implementation manner of Embodiment 1 of the present application.

FIG. 5 is a schematic diagram of a second implementation manner of Embodiment 1 of the present application.

FIG. 6 is a schematic diagram of small data transmission 600 based on pre-configured resources according to Embodiment 1 of the present application.

FIG. 7 is a schematic diagram 1 of a manner of obtaining an updated NCC in Embodiment 2 of the present application.

FIG. 8 is a schematic diagram of the second embodiment of the second embodiment of the present application for obtaining an updated NCC.

FIG. 9 is an implementation flowchart of a data transmission method 900 according to an embodiment of the present application.

FIG. 10 is a schematic structural diagram of a terminal device 1000 according to an embodiment of the present application.

FIG. 11 is a schematic structural diagram of a terminal device 1100 according to an embodiment of the present application.

Fig. 12 is a schematic structural diagram of a network device 1200 according to an embodiment of the present application.

FIG. 13 is a schematic structural diagram of a network device 1300 according to an embodiment of the present application.

FIG. 14 is a schematic structural diagram of a communication device 1400 according to an embodiment of the present application;

FIG. 15 is a schematic structural diagram of a chip 1500 according to an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

It should be noted that the terms "first" and "second" in the description and claims of the embodiments of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific sequence or sequence. order. The objects described by "first" and "second" described at the same time may be the same or different.

The technical solutions of the embodiments of this application can be applied to various communication systems, such as: Global System of Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, and Wideband Code Division Multiple Access (Wideband Code Division Multiple Access, WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system , New Radio (NR) system, NR system evolution system, LTE (LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum) unlicensed spectrum, NR-U) system, universal mobile telecommunication system (UMTS), wireless local area network (Wireless Local Area Networks, WLAN), wireless fidelity (Wireless Fidelity, WiFi), next-generation communications (5th-Generation) , 5G) system or other communication systems, etc.

Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication, but also support, for example, Device to Device (Device to Device, D2D) communication, machine to machine (Machine to Machine, M2M) communication, machine type communication (MTC), and vehicle to vehicle (V2V) communication, etc. The embodiments of this application can also be applied to these communications system.

Optionally, the communication system in the embodiments of the present application can be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, can also be applied to a dual connectivity (DC) scenario, and can also be applied to a standalone (SA) deployment. Network scene.

The embodiment of the application does not limit the applied frequency spectrum. For example, the embodiments of this application can be applied to licensed spectrum or unlicensed spectrum.

The embodiments of this application describe various embodiments in combination with network equipment and terminal equipment. The terminal equipment may also be referred to as User Equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, and remote. Station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc. The terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, and personal digital processing (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, and next-generation communication systems, such as terminal devices in the NR network or Terminal equipment in the public land mobile network (PLMN) network that will evolve in the future.

As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices can also be called wearable smart devices. It is a general term for using wearable technology to intelligently design everyday wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes. A wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. Wearable devices are not only a kind of hardware device, but also realize powerful functions through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include full-featured, large-sized, complete or partial functions that can be achieved without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, and need to cooperate with other devices such as smart phones. Use, such as all kinds of smart bracelets and smart jewelry for physical sign monitoring.

A network device can be a device used to communicate with mobile devices. The network device can be an access point (AP) in WLAN, a base station (BTS) in GSM or CDMA, or a device in WCDMA. A base station (NodeB, NB), can also be an Evolutional Node B (eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in the NR network Or network equipment in the PLMN network that will evolve in the future.

In the embodiment of the present application, the network equipment provides services for the cell, and the terminal equipment communicates with the network equipment through the transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell, and the cell may be a network equipment (for example, The cell corresponding to the base station. The cell can belong to a macro base station or a base station corresponding to a small cell. The small cell here can include: Metro cell, Micro cell, Pico Cells, Femto cells, etc. These small cells have the characteristics of small coverage and low transmit power, and are suitable for providing high-rate data transmission services.

Figure 1 exemplarily shows one network device 110 and two terminal devices 120. Optionally, the wireless communication system 100 may include multiple network devices 110, and the coverage of each network device 110 may include other numbers. The terminal device 120 is not limited in this embodiment of the application. The embodiments of the present application can be applied to one terminal device 120 and one network device 110, and can also be applied to one terminal device 120 and another terminal device 120.

Optionally, the wireless communication system 100 may also include other network entities such as mobility management entities (Mobility Management Entity, MME), access and mobility management functions (Access and Mobility Management Function, AMF), etc. This is not limited.

It should be understood that the terms "system" and "network" in this article are often used interchangeably in this article. The term "and/or" in this article is only an association relationship describing the associated objects, which means that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, exist alone B these three situations. In addition, the character "/" in this text generally means that the associated objects before and after are in an "or" relationship.

The embodiment of the present application proposes a data transmission method, which can be applied to a terminal device. FIG. 2 is an implementation flowchart of a data transmission method 200 according to an embodiment of the present application, including the following steps:

S210: When the key is valid, the key is used to encrypt the data, and the pre-configured resource is used to send the encrypted data.

In some embodiments, the aforementioned data is small data, such as data with a small amount of data sent by the UE in the RRC_INACTIVE state and/or data with a low transmission frequency. In the following embodiments, the data sent by the terminal device may be small data.

The prerequisites of the above method include at least one of the following:

The cell where the UE is currently located supports small data transmission based on preconfigured resources (PUR, Preconfigured Uplink Resource);

The UE has the ability to transmit small data in the RRC_INACTIVE state.

As shown in FIG. 3, in some embodiments, the step S210 further includes:

S320: The terminal device generates the key based on the next hop link count (NCC, NextHopChainingCount).

The NCC can be carried in an RRC release message (RRCRelease) to generate a new key.

As shown in FIG. 3, optionally, before step S320 of the foregoing method, the method further includes:

S310: Receive an RRC release message, where the RRC release message includes at least one of the following:

Pre-configured resources;

NCC;

The valid duration of the key;

The number of valid transmissions of the key.

Optionally, the terminal device sends a data transmission resource request in the connected state (RRC_CONNECTED state), and after receiving the RRC release message, that is, after the above step S310, the terminal device switches to the inactive state (RRC_INACTIVE state).

Since the key has a certain validity period or number of valid transmissions, and the key is invalid, the terminal device can obtain the updated NCC, use the updated NCC to generate the updated key, and then use the updated key pair The data is encrypted. Optionally, as shown in Figure 3, the above method further includes:

S330: Obtain the updated NCC;

S340: Generate an updated key based on the updated NCC;

S350: Use the updated key to encrypt the data, and use the pre-configured resource to send the encrypted data.

Among them, the terminal device can obtain the updated NCC when the key is invalid; or the network device updates the NCC through the downlink feedback of a certain small data transmission, and the terminal device obtains the updated NCC from the response to the small data.

Optionally, the terminal device may obtain the updated NCC when the key is invalid, and the obtaining method includes at least one of the following:

In the first type, the terminal device triggers an RRC Resume (RRC Resume) process when/after the key becomes invalid, and receives the updated NCC. Specifically, the terminal device may send an RRC recovery request (RRCResumeRequest) message to trigger the RRC recovery process; and receive an RRC release (RRCRelease) message containing the updated NCC sent by the network device.

In the second type, when/after the key becomes invalid, when the terminal device needs to send data or is paged, it triggers the RRC recovery process and receives the updated NCC. Specifically, the terminal device may send an RRCResumeRequest message to trigger the RRC recovery process; and receive the RRCelease message containing the updated NCC sent by the network device.

In the third type, when/after the key becomes invalid, when the terminal device needs to send data and meets the data transmission requirements based on random access, it triggers the data transmission process based on random access and receives the updated NCC. Optionally, the terminal device sends the preamble of the random access procedure, and after receiving the uplink resource configured on the network side, uses the uplink resource to send the RRCResumeRequest message; and receives the RRCRelease containing the updated NCC sent by the network device information.

Fourth, when/after the key becomes invalid, the terminal device multiplexes the RRC recovery request message or the MAC CE indicating the update of the NCC in the data transmitted by the pre-configured resource, and receives the updated NCC. Optionally, the terminal device multiplexes the RRCResumeRequest message in the small data transmission of the pre-configured resource; and receives the RRCRelease message containing the updated NCC sent by the network device.

The aforementioned RRCRelease message may further include the effective duration and/or the number of effective transmissions of the key generated by the updated NCC, or further include new pre-configured resources. If a new pre-configured resource is included, the terminal device can use the new pre-configured resource to send encrypted data.

Optionally, the above-mentioned key valid condition includes: the use duration of the key does not reach the valid duration and/or the number of uses of the key does not reach the number of valid transmissions.

The key invalidation conditions include: the use time of the key reaches the effective time length and/or the use times of the key reach the effective transmission times.

For example, a timer is started when the key is generated, and during the running of the timer, the key generated based on the currently configured NCC remains valid. When the timer expires (for example, the timer reaches the above valid duration), the key generated based on the currently configured NCC becomes invalid.

Alternatively, the counter is initialized to 0 when the key is generated, and the counter is incremented by 1 for each uplink data transmission or downlink data reception; the key generated based on the currently configured NCC remains valid before the counter reaches the number of valid transmissions. When the counter reaches the number of valid transmissions mentioned above, the key generated based on the currently configured NCC becomes invalid.

In some embodiments, the foregoing RRC release message further includes a time advance (TA, Time Advance) verification criterion.

Optionally, the foregoing TA verification criterion includes a TA timer (TA Timer) and/or a reference signal received power (RSRP, Reference Signal Received Power) conversion threshold. On the premise that the terminal device verifies that the TA is valid according to the TA verification criterion, and when the key is valid, the encrypted data is sent by using the pre-configured resource.

Specifically, the above-mentioned effective TA may include at least one of the following:

TA timer is in operation;

The RSRP change (increase or decrease) is smaller than the aforementioned RSRP conversion threshold.

In some implementation manners, after sending uplink data, the terminal device receives a response message in the listening window, and the response message includes at least one of the following:

The first layer acknowledgement (L1ACK) message;

Media Access Control (MAC, Media Access Control) control element (CE, Control Element) indicating the TA adjustment amount;

Downlink data;

RRC message used for NCC update or pre-configured resource reconfiguration.

When one of the foregoing responses is received, the UE may consider that the uplink data transmission is successful.

Optionally, the foregoing L1ACK message includes the TA adjustment amount.

Optionally, the aforementioned downlink data includes a TA adjustment amount.

Optionally, the foregoing RRC message used for NCC update or pre-configured resource reconfiguration is multiplexed with downlink data and/or TA adjustment amount.

The application will be described in detail below with reference to the drawings and specific embodiments.

Example one:

This embodiment is directed to the small data transmission of the UE in the inactive state in the NR system. Optionally, the preconditions for the UE to perform small data transmission include:

The cell where the UE is currently located supports small data transmission based on pre-configured resources;

The UE has the function of transmitting small data in the inactive state.

This embodiment includes the following steps:

Step 1: The UE initiates a small data transmission resource request in the connected state, which can optionally include resource configuration auxiliary information: such as the period of data transmission, the amount of data, and so on.

Step 2: The UE receives the RRC release message sent by the network and enters the inactive state, where the RRC release message may at least contain:

a) Pre-configured resources for inactive small data transmission;

b) TA verification criteria (including TA timer, RSRP change threshold, etc.);

c) NCC used to generate the key;

d) Based on the valid length of the key generated by the currently configured NCC or the number of valid transmissions.

Step 3: The UE generates a new key based on the NCC configured in the RRC release message. If the RRC release message contains the valid duration of the key, the UE can start a timer when generating the key. During the running of the timer, the key generated based on the currently configured NCC remains valid. When the timer expires, the key generated based on the currently configured NCC becomes invalid. If the RRC release message contains the number of valid transmissions of the key, the UE initializes the counter to 0 after generating the key, and the counter is incremented by 1 for each uplink data transmission or downlink data reception. Before the counter reaches the configured number of valid transmissions, the key generated based on the currently configured NCC remains valid; when the counter reaches the configured number of valid transmissions, the key generated based on the currently configured NCC becomes invalid. 4 and 5 are schematic diagrams of two implementation manners of Embodiment 1 of the present application. Among them, Fig. 4 corresponds to the method of judging whether the key is invalid by using a timer, and Fig. 5 corresponds to the method of judging whether the key is invalid by using a counter. In FIG. 4 and FIG. 5, the horizontal direction represents the time axis, and each rectangle represents the data sent by the UE using the pre-configured resources.

Step 4: During the key validity period, when the UE further uses the TA verification criterion to verify that the TA is valid and the configured resources are valid, the UE uses the pre-configured resources to transmit user data without multiplexing RRC messages.

Step 5: After the UE sends the uplink user data, it receives the response from the network in the listening window. When one of the following four types of responses is received, the UE can consider that the small data transmission is successful:

a) L1ACK, optionally including TA adjustment amount (Time Advance Command);

b) MAC CE indicating the amount of TA adjustment;

c) Downlink data can optionally include TA adjustment;

d) An RRC message used for NCC update or pre-configured resource reconfiguration. The RRC message can be multiplexed with downlink data and/or TA adjustment.

The above TA adjustment can be used to update the TA value maintained by the UE and restart the TA timer.

Fig. 6 is a schematic diagram of a small data transmission 600 based on pre-configured resources in the first embodiment of the present application, including: the UE sends uplink data (Uplink data) to the ng-eNB on the available PUR. The ng-eNB and the core network equipment implement the 5GS Cellular Internet of Things (CIot, Cellular The Internet of Things) user plane function optimization solution for the mobile terminal caller's early data transmission (MO-EDT, Mobile-Originating Early Data Transmission) transmission process (MO-EDT procedure for user plane CIoT 5GS optimisations), where the aforementioned core network equipment includes access and mobility management functions (AMF, Access and Mobility Management Function), session management functions (SMF, Session Management Function)/user plane management Function (UPF, User Plane Function). The ng-eNB sends feedback for uplink data to the UE, such as downlink data (optionally including TA adjustment), MAC CE indicating the TA adjustment, L1ACK (optionally including TA adjustment), or for NCC update or pre-processing. Configure the RRC message for resource reconfiguration.

Embodiment two:

This embodiment relates to a procedure for the UE to acquire a new NCC. When the current key becomes invalid, the UE can use one of the following methods to obtain a new NCC through the RRC connection release message again:

Method 1: The UE updates the NCC and triggers the RRC Resume process. Specifically, the UE may send an RRCResumeRequest message, and receive an RRCRelease message containing a new NCC sent by the network side.

Method 2: When uplink data arrives or the UE is paged, the UE triggers the RRC Resume process. The specific method is the same as above.

Manner 3: When the uplink data arrives and meets the decimal transmission requirement, the UE triggers the small data transmission process based on random access. Specifically, the UE may send a preamble in the random access process, and after receiving the uplink resource configured on the network side, use the uplink resource to send the RRCResumeRequest message; and receive the RRCRelease message containing the new NCC sent by the network device .

FIG. 7 is a schematic diagram 1 of a manner of obtaining an updated NCC in Embodiment 2 of the present application. Figure 7 takes the timer timeout as an example, corresponding to the above-mentioned mode one to the mode three. As shown in Figure 7, the horizontal represents the time axis, and each rectangle represents the data sent by the UE using pre-configured resources. When the timer expires/after the timer expires, the RRC Resume process or the small data transmission process based on random access is triggered; then the receiving network The RRCRelease message containing the new NCC sent by the side uses the new NCC to regenerate the key and starts the timer. The RRCRelease message may also carry the effective length of the new NCC generated key or the number of effective transmissions.

Manner 4: Multiplexing the RRCResumeRequest message or MAC CE indicating the NCC update in the small data transmission based on pre-configured resources. After that, the UE receives the RRCRelease message containing the new NCC sent by the network device.

FIG. 8 is a schematic diagram of a second embodiment of the second embodiment of the present application for obtaining an updated NCC. Figure 8 takes the timer timeout as an example, which corresponds to the fourth mode above. As shown in Figure 8, the horizontal direction represents the time axis; each rectangle before the timer expires represents the data sent by the UE using the pre-configured resources. When/after the timer expires, the RRCResumeRequest message or the MAC CE indicating the update of the NCC is multiplexed in the small data based on the pre-configured resource. After that, the UE receives the RRCRelease message containing the new NCC sent by the network side, uses the new NCC to regenerate the key, and starts the timer. The RRCRelease message may also carry the effective length of the new NCC generated key or the number of effective transmissions.

The above four methods correspond to the process of obtaining the updated NCC when/after the key becomes invalid. In the embodiment of the present application, when the key is not invalidated, that is, during the operation of the timer or before the counter reaches the configured number of valid transmissions, the gNB may update the NCC through the downlink feedback of a certain small data transmission.

After acquiring a new NCC, the UE generates a key based on the updated NCC and restarts the timer or initializes the counter to 0.

It can be seen from the above process that in the data transmission method proposed in the embodiment of this application, the terminal device can use pre-configured resources to transmit uplink user data without multiplexing RRC messages in the small data transmission process; and the key derived from NCC can be reused No need to update NCC frequently.

The embodiment of the present application also proposes another data transmission method, which can be applied to network equipment. FIG. 9 is an implementation flowchart of a data transmission method 900 according to an embodiment of the present application, including:

S910: Send a pre-configured resource and/or a next hop link count NCC used to generate a key, where the pre-configured resource and key are used for the terminal device to send data.

In some embodiments, sending the pre-configured resource and/or the NCC used to generate the key includes:

Receive a data transmission resource request; send an RRC release message, the RRC release message contains at least one of the following:

Pre-configured resources;

NCC;

The valid duration of the key;

The number of valid transmissions of the key.

Optionally, the above method further includes: sending the updated NCC.

In some embodiments, the RRC release message also includes TA verification criteria.

Optionally, the TA verification criterion includes a TA timer and/or RSRP conversion threshold.

Optionally, the TA verification criterion is used for the terminal device to verify whether the TA is valid, and when the TA is valid and the key is valid, use pre-configured resources to send encrypted data.

In some embodiments, the above-mentioned data includes small data transmitted by the terminal device in a disconnected state.

In some implementation manners, the foregoing method further includes: sending a response message, the response message including at least one of the following:

L1ACK message;

MAC CE indicating the amount of TA adjustment;

Downlink data;

RRC message used for NCC update or pre-configured resource reconfiguration.

Optionally, the foregoing L1ACK message includes the TA adjustment amount.

Optionally, the aforementioned downlink data includes a TA adjustment amount.

An embodiment of the present application also proposes a terminal device. FIG. 10 is a schematic structural diagram of a terminal device 1000 according to an embodiment of the present application, including:

The transmission module 1010 is configured to use the key to encrypt data when the key is valid, and use pre-configured resources to send the encrypted data.

In some embodiments, as shown in FIG. 11, the above-mentioned terminal device further includes:

The key generation module 1120 is configured to generate the key based on the next hop link count NCC.

Optionally, the aforementioned transmission module 1010 is further configured to: send a data transmission resource request; receive a radio resource control RRC release message, where the RRC release message includes at least one of the following:

The pre-configured resource;

The NCC;

The valid duration of the key;

The number of valid transmissions of the key.

Optionally, the above-mentioned transmission module 1010 sends the data transmission resource request when the terminal device is in the connected state;

It also includes: a state conversion module 1130, configured to convert the terminal device into an inactive state after receiving the RRC release message.

Optionally, the above-mentioned transmission module 1010 is further configured to: obtain an updated NCC; generate an updated key based on the updated NCC; use the updated key to encrypt data, and send it using pre-configured resources Encrypted data.

Optionally, the above-mentioned transmission module 1010 obtains the updated NCC when the key is invalid.

Optionally, the aforementioned transmission module 1010 uses at least one of the following to obtain the updated NCC:

When/after the key becomes invalid, trigger an RRC recovery process, and receive the updated NCC;

When/after the key becomes invalid, when data needs to be sent or paged, the RRC recovery process is triggered, and the updated NCC is received;

When/after the key is invalid, when data needs to be sent and the data transmission requirements based on random access are met, a random access-based data transmission process is triggered, and the updated NCC is received;

When/after the key becomes invalid, multiplex the RRC recovery request message or the MAC CE indicating the update of the NCC in the data transmitted by the pre-configured resource, and receive the updated NCC.

Optionally, obtain the updated NCC from the response to the data.

Optionally, the foregoing case where the key is valid includes: the use duration of the key does not reach the valid duration and/or the number of uses of the key does not reach the number of valid transmissions.

Optionally, the foregoing key invalidation situation includes: the use duration of the key reaches the valid duration and/or the number of uses of the key reaches the number of valid transmissions.

Optionally, the foregoing RRC release message further includes a timing advance TA verification criterion.

Optionally, the above TA verification criterion includes a TA timer and/or a reference signal received power RSRP conversion threshold.

Optionally, the above-mentioned transmission module 1010 uses a pre-configured resource to send encrypted data on the premise that the TA is validated according to the TA verification criterion and when the key is valid.

Optionally, the aforementioned data includes small data transmitted by the terminal device in a non-connected state.

Optionally, the aforementioned terminal device further includes: a response receiving module 1140, configured to receive a response message in the listening window, where the response message includes at least one of the following:

The first layer acknowledges the L1ACK message;

The media access control MAC control unit CE indicating the TA adjustment amount;

Downlink data;

RRC message used for NCC update or pre-configured resource reconfiguration.

Optionally, the foregoing L1ACK message includes the TA adjustment amount.

Optionally, the aforementioned downlink data includes a TA adjustment amount.

It should be understood that the above-mentioned and other operations and/or functions of the modules in the terminal device according to the embodiment of the present application are used to implement the corresponding procedures of the terminal device in the method 200 of FIG. 2 and the method 300 of FIG. 3, respectively. For the sake of brevity, No longer.

An embodiment of the present application also proposes a network device. FIG. 12 is a schematic structural diagram of a network device 1200 according to an embodiment of the present application, including:

The configuration module 1210 is configured to send a pre-configured resource and/or a next hop link count NCC used to generate a key, where the pre-configured resource and key are used for the terminal device to send data.

Optionally, the above configuration module 1210 is configured to: receive a data transmission resource request; and send a radio resource control RRC release message, where the RRC release message includes at least one of the following:

The pre-configured resource;

The NCC;

The valid duration of the key;

The number of valid transmissions of the key.

In some embodiments, as shown in FIG. 13, the above-mentioned network device further includes: an update module 1320, configured to send an updated NCC.

Optionally, the above TA verification criterion is used for the terminal device to verify whether the TA is valid, and when the TA is valid and the key is valid, the encrypted data is sent using pre-configured resources.

Optionally, the aforementioned network device further includes: a response module 1330, configured to send a response message, where the response message includes at least one of the following:

The first layer acknowledges the L1ACK message;

Downlink data;

RRC message used for NCC update or pre-configured resource reconfiguration.

Optionally, the foregoing L1ACK message includes the TA adjustment amount.

Optionally, the aforementioned downlink data includes a TA adjustment amount.

It should be understood that the above-mentioned and other operations and/or functions of the modules in the network device according to the embodiment of the present application are used to implement the corresponding process of the network device in the method 900 of FIG.

FIG. 14 is a schematic structural diagram of a communication device 1400 according to an embodiment of the present application. The communication device 1400 shown in FIG. 14 includes a processor 1410, and the processor 1410 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 14, the communication device 1400 may further include a memory 1420. The processor 1410 may call and run a computer program from the memory 1420 to implement the method in the embodiment of the present application.

The memory 1420 may be a separate device independent of the processor 1410, or may be integrated in the processor 1410.

Optionally, as shown in FIG. 14, the communication device 1400 may further include a transceiver 1430, and the processor 1410 may control the transceiver 1430 to communicate with other devices. Specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.

Among them, the transceiver 1430 may include a transmitter and a receiver. The transceiver 1430 may further include an antenna, and the number of antennas may be one or more.

Optionally, the communication device 1400 may be a terminal device of an embodiment of the present application, and the communication device 1400 may implement corresponding procedures implemented by the terminal device in each method of the embodiments of the present application. For brevity, details are not described herein again.

Optionally, the communication device 1400 may be a network device of an embodiment of the present application, and the communication device 1400 may implement corresponding processes implemented by the network device in each method of the embodiments of the present application. For brevity, details are not described herein again.

FIG. 15 is a schematic structural diagram of a chip 1500 according to an embodiment of the present application. The chip 1500 shown in FIG. 15 includes a processor 1510, and the processor 1510 can call and run a computer program from the memory to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 15, the chip 1500 may further include a memory 1520. The processor 1510 can call and run a computer program from the memory 1520 to implement the method in the embodiment of the present application.

The memory 1520 may be a separate device independent of the processor 1510, or may be integrated in the processor 1510.

Optionally, the chip 1500 may further include an input interface 1530. The processor 1510 can control the input interface 1530 to communicate with other devices or chips, and specifically, can obtain information or data sent by other devices or chips.

Optionally, the chip 1500 may further include an output interface 1540. The processor 1510 can control the output interface 1540 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.

Optionally, the chip can be applied to the terminal device or the network device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the terminal device or the network device in the various methods of the embodiment of the present application. For the sake of brevity, here No longer.

It should be understood that the chip mentioned in the embodiment of the present application may also be referred to as a system-level chip, a system-on-chip, a system-on-chip, or a system-on-chip, etc.

The aforementioned processors may be general-purpose processors, digital signal processors (digital signal processors, DSP), ready-made programmable gate arrays (field programmable gate arrays, FPGAs), application specific integrated circuits (ASICs), or Other programmable logic devices, transistor logic devices, discrete hardware components, etc. Among them, the aforementioned general-purpose processor may be a microprocessor or any conventional processor.

The above-mentioned memory may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electrically available Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory. The volatile memory may be random access memory (RAM).

It should be understood that the foregoing memory is exemplary but not restrictive. For example, the memory in the embodiment of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is to say, the memory in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memory.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented by software, it can be implemented in the form of a computer program product in whole or in part. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instruction may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instruction may be transmitted from a website, computer, server, or data center through a cable (Such as coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center integrated with one or more available media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

It should be understood that in the various embodiments of the present application, the size of the sequence number of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not correspond to the embodiments of the present application. The implementation process constitutes any limitation.

Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working process of the system, device and unit described above can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

The above are only specific implementations of this application, but the protection scope of this application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application. Covered in the scope of protection of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims.

Claims

A data transmission method applied to terminal equipment, including:

When the key is valid, the key is used to encrypt the data, and the pre-configured resource is used to send the encrypted data.
The method according to claim 1, further comprising:

The terminal device generates the key based on the next hop link count NCC.
The method according to claim 2, further comprising: a terminal device sending a data transmission resource request; receiving a radio resource control RRC release message, the RRC release message including at least one of the following:

The pre-configured resource;

The NCC;

The valid duration of the key;

The number of valid transmissions of the key.
The method according to claim 3, wherein the terminal device sends the data transmission resource request in a connected state;

After receiving the RRC release message, it further includes: the terminal device is converted to an inactive state.
The method according to any one of claims 1 to 4, further comprising:

Get the updated NCC;

Generating an updated key based on the updated NCC;

The updated key is used to encrypt the data, and the pre-configured resource is used to send the encrypted data.
The method according to claim 5, wherein the updated NCC is obtained when the key is invalid.
The method according to claim 6, wherein the manner of obtaining the updated NCC includes at least one of the following:

When/after the key becomes invalid, the terminal device triggers the RRC recovery process, and receives the updated NCC;

When/after the key becomes invalid, when the terminal device needs to send data or is paged, trigger the RRC recovery process to receive the updated NCC;

When/after the key becomes invalid, when the terminal device needs to send data and meets the data transmission requirements based on random access, triggers a data transmission process based on random access, and receives the updated NCC;

When/after the key becomes invalid, the terminal device multiplexes the RRC recovery request message or the media access control MAC control unit CE indicating the update of the NCC in the data transmitted by the pre-configured resource, and receives the updated NCC.
The method according to claim 5, wherein the updated NCC is obtained from the response to the data.
The method according to any one of claims 3 to 8, wherein the condition that the key is valid includes: the use time of the key does not reach the valid time and/or the number of times the key is used does not reach the valid Number of transfers.
The method according to claim 6, 7 or 9, wherein the condition that the key is invalid includes: the use time of the key reaches the valid time and/or the number of times the key is used reaches the valid Number of transfers.
The method according to any one of claims 3 to 10, wherein the RRC release message further includes a timing advance TA verification criterion.
The method according to claim 11, wherein the TA verification criterion comprises a TA timer and/or a reference signal received power RSRP conversion threshold.
The method according to claim 11 or 12, wherein, on the premise that the terminal device verifies that the TA is valid according to the TA verification criterion, and when the key is valid, the encrypted data is sent using a pre-configured resource .
The method according to any one of claims 1 to 13, wherein the data includes small data transmitted by the terminal device in a disconnected state.
The method according to any one of claims 1 to 14, further comprising:

The terminal device receives a response message in the listening window, and the response message includes at least one of the following:

The first layer acknowledges the L1 ACK message;

MAC CE indicating the amount of TA adjustment;

Downlink data;

RRC message used for NCC update or pre-configured resource reconfiguration.
The method according to claim 15, wherein the L1 ACK message includes a TA adjustment amount.
The method according to claim 15, wherein the downlink data includes a TA adjustment amount.
The method according to claim 15, wherein the RRC message used for NCC update or pre-configured resource reconfiguration is multiplexed with downlink data and/or TA adjustment.
A data transmission method applied to network equipment, including:

Sending the pre-configured resource and/or the next hop link count NCC used to generate the key, the pre-configured resource and the key being used for the terminal device to send data.
The method according to claim 19, wherein said sending the pre-configured resource and/or the next hop link count NCC used to generate the key comprises:

Receive a data transmission resource request; send a radio resource control RRC release message, where the RRC release message includes at least one of the following:

The pre-configured resource;

The NCC;

The valid duration of the key;

The number of valid transmissions of the key.
The method according to claim 19 or 20, further comprising: sending the updated NCC.
The method according to any one of claims 19 to 21, wherein the RRC release message further includes a timing advance TA verification criterion.
The method according to claim 22, wherein the TA verification criterion comprises a TA timer and/or a reference signal received power RSRP conversion threshold.
The method according to claim 22 or 23, wherein the TA verification criterion is used for the terminal device to verify whether the TA is valid, and when the TA is valid and the key is valid, the encrypted data is sent using pre-configured resources .
The method according to any one of claims 19 to 24, wherein the data includes small data transmitted by the terminal device in a disconnected state.
The method according to any one of claims 19 to 25, further comprising: sending a response message, the response message including at least one of the following:

The first layer acknowledges the L1 ACK message;

The media access control MAC control unit CE indicating the TA adjustment amount;

Downlink data;

RRC message used for NCC update or pre-configured resource reconfiguration.
The method according to claim 26, wherein the L1 ACK message includes a TA adjustment amount.
The method according to claim 26, wherein the downlink data includes a TA adjustment amount.
The method according to claim 26, wherein the RRC message used for NCC update or pre-configured resource reconfiguration is multiplexed with downlink data and/or TA adjustment.
A terminal device, including:

The transmission module is used to encrypt data with the key when the key is valid, and use pre-configured resources to send the encrypted data.
The terminal device according to claim 30, further comprising:

The key generation module is configured to generate the key based on the next hop link count NCC.
The terminal device according to claim 31, wherein the transmission module is further configured to: send a data transmission resource request; receive a radio resource control RRC release message, the RRC release message including at least one of the following:

The pre-configured resource;

The NCC;

The valid duration of the key;

The number of valid transmissions of the key.
The terminal device according to claim 32, wherein the transmission module sends the data transmission resource request when the terminal device is in a connected state;

It also includes a state conversion module, which is used to convert the terminal device to an inactive state after receiving the RRC release message.
According to the terminal device of any one of claims 30 to 33, the transmission module is further configured to: obtain an updated NCC; generate an updated key based on the updated NCC; and use the updated key Encrypt the data and send the encrypted data using pre-configured resources.
The terminal device according to claim 34, wherein the transmission module obtains the updated NCC when the key is invalid.
The terminal device according to claim 35, wherein the transmission module uses at least one of the following to obtain the updated NCC:

When/after the key becomes invalid, trigger an RRC recovery process, and receive the updated NCC;

When/after the key becomes invalid, when data needs to be sent or paged, the RRC recovery process is triggered, and the updated NCC is received;

When/after the key is invalid, when data needs to be sent and the data transmission requirements based on random access are met, a random access-based data transmission process is triggered, and the updated NCC is received;

When/after the key becomes invalid, multiplex the RRC recovery request message or the MAC CE indicating the update of the NCC in the data transmitted by the pre-configured resource, and receive the updated NCC.
The terminal device according to claim 34, wherein the updated NCC is obtained from the response to the data.
The terminal device according to any one of claims 32 to 37, wherein the condition that the key is valid includes: the use time of the key does not reach the valid time and/or the number of times the key is used does not reach the Number of valid transfers.
The terminal device according to claim 35, 36, or 38, wherein the condition that the key is invalid includes: the use time of the key reaches the valid time and/or the number of times the key is used reaches the Number of valid transfers.
The terminal device according to any one of claims 32 to 39, wherein the RRC release message further includes a timing advance TA verification criterion.
The terminal device according to claim 40, wherein the TA verification criterion includes a TA timer and/or a reference signal received power RSRP conversion threshold.
The terminal device according to claim 40 or 41, wherein the transmission module uses a pre-configured resource to send the encrypted data on the premise that the TA is validated according to the TA verification criterion and when the key is valid. data.
The terminal device according to any one of claims 30 to 42, wherein the data includes small data transmitted by the terminal device in a disconnected state.
The terminal device according to any one of claims 30 to 43, further comprising:

The response receiving module is configured to receive a response message in the listening window, and the response message includes at least one of the following:

The first layer acknowledges the L1 ACK message;

The media access control MAC control unit CE indicating the TA adjustment amount;

Downlink data;

RRC message used for NCC update or pre-configured resource reconfiguration.
The terminal device according to claim 44, wherein the L1 ACK message includes a TA adjustment amount.
The terminal device according to claim 44, wherein the downlink data includes a TA adjustment amount.
The terminal device according to claim 44, wherein the RRC message used for NCC update or pre-configured resource reconfiguration is multiplexed with downlink data and/or TA adjustment amount.
A network device including:

The configuration module is used to send a pre-configured resource and/or a next hop link count NCC for generating a key, where the pre-configured resource and the key are used for the terminal device to send data.
The network device according to claim 48, wherein the configuration module is configured to: receive a data transmission resource request; send a radio resource control RRC release message, the RRC release message containing at least one of the following:

The pre-configured resource;

The NCC;

The valid duration of the key;

The number of valid transmissions of the key.
The network device according to claim 48 or 49, further comprising: an update module, configured to send the updated NCC.
The network device according to any one of claims 48 to 50, wherein the RRC release message further includes a timing advance TA verification criterion.
The network device according to claim 51, wherein the TA verification criterion comprises a TA timer and/or a reference signal received power RSRP conversion threshold.
The network device according to claim 51 or 52, wherein the TA verification criterion is used for the terminal device to verify whether the TA is valid, and when the TA is valid and the key is valid, use pre-configured resources to send the encrypted data.
The network device according to any one of claims 48 to 53, wherein the data includes small data transmitted by the terminal device in a disconnected state.
The network device according to any one of claims 48 to 54, further comprising: a response module, configured to send a response message, the response message comprising at least one of the following:

The first layer acknowledges the L1 ACK message;

The media access control MAC control unit CE indicating the TA adjustment amount;

Downlink data;

RRC message used for NCC update or pre-configured resource reconfiguration.
The network device according to claim 55, wherein the L1 ACK message includes a TA adjustment amount.
The network device according to claim 55, wherein the downlink data includes a TA adjustment amount.
The network device according to claim 55, wherein the RRC message used for NCC update or pre-configured resource reconfiguration is multiplexed with downlink data and/or TA adjustment amount.
A terminal device, comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute any one of claims 1 to 18 Methods.
A network device, comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute any one of claims 19 to 29 Methods.
A chip comprising: a processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 1 to 18.
A chip comprising: a processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 19 to 29.
A computer-readable storage medium for storing a computer program that enables a computer to execute the method according to any one of claims 1 to 18.
A computer-readable storage medium for storing a computer program that enables a computer to execute the method according to any one of claims 19 to 29.
A computer program product comprising computer program instructions that cause a computer to execute the method according to any one of claims 1 to 18.
A computer program product comprising computer program instructions that cause a computer to execute the method according to any one of claims 19 to 29.
A computer program that causes a computer to execute the method according to any one of claims 1 to 18.
A computer program that causes a computer to execute the method according to any one of claims 19 to 29.