CN115004739A

CN115004739A - Data transmission method, terminal equipment and network equipment

Info

Publication number: CN115004739A
Application number: CN202080093637.3A
Authority: CN
Inventors: 林雪; 王淑坤; 石聪; 李海涛
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2020-04-10
Filing date: 2020-04-10
Publication date: 2022-09-02
Also published as: WO2021203439A1

Abstract

The embodiment of the application relates to a data transmission method, terminal equipment and communication equipment, wherein the method comprises the following steps: and under the condition that the key is effective, encrypting the data by adopting the key, and sending the encrypted data by utilizing the pre-configured resource. The method and the device can realize the transmission of the small data of the terminal equipment in the non-activated state.

Description

Data transmission method, terminal equipment and network equipment

Technical Field

The present application relates to the field of communications, and more particularly, to a data transmission method, a terminal device, and a network device.

Background

In a fifth generation 5G New air interface (NR, New Radio) system, Radio Resource Control (RRC, Radio Resource Control) states of a terminal device are divided into 3 types, which are: RRC _ IDLE (RRC IDLE state), RRC _ INACTIVE (RRC INACTIVE state), and RRC _ CONNECTED (RRC CONNECTED state). The RRC _ INACTIVE state is a new state introduced by the 5G system from the energy saving perspective, for the UE in the RRC _ INACTIVE state, radio bearers and all radio resources are released, but the UE side and the base station side retain the UE access context so as to quickly recover the RRC connection, and the network generally keeps the UE with infrequent data transmission in the RRC _ INACTIVE state. Before 5G standard Rel-16 released by the third Generation Partnership Project (3 GPP), the UE in the RRC _ INACTIVE state does not support data transmission, when uplink data arrives, the UE needs to recover the connection, and the UE is released to the RRC _ INACTIVE state after the data transmission is completed. For UEs with small data size and low transmission frequency, such transmission mechanisms may result in unnecessary power consumption and signaling overhead. Therefore, Rel-17 has conducted research on small data (small data) transmission in RRC _ INACTIVE state, where the small data may refer to data with a small amount of data and/or a low transmission frequency transmitted by the UE in RRC _ INACTIVE state. At present, there is no clear way for such data transmission.

Disclosure of Invention

The embodiment of the application provides 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 provides a data transmission method, which is applied to terminal equipment and comprises the following steps:

and under the condition that the key is effective, encrypting the data by adopting the key, and sending the encrypted data by utilizing the pre-configured resource.

The embodiment of the application provides a data transmission method, which is applied to network equipment and comprises the following steps:

and sending a pre-configured resource and/or a next hop link count (NCC) used for generating a key, wherein the pre-configured resource and the key are used for sending data by the terminal equipment.

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

and the transmission module is used for encrypting the data by adopting the key under the condition that the key is effective and sending the encrypted data by utilizing the pre-configured resource.

An embodiment of the present application provides a network device, including:

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

The embodiment of the application provides a terminal device, including: a processor and a memory for storing a computer program, said processor being adapted to invoke and execute the computer program stored in said memory to perform the method as described in any of the above data transmission methods.

An embodiment of the present application provides a network device, including: a processor and a memory for storing a computer program, said processor being adapted to invoke and execute the computer program stored in said memory to perform the method as described in any of the above data transmission methods.

The embodiment of the present application provides a chip, including: a processor for calling and running the computer program from the memory so that the device on which the chip is installed performs the method as described in any of the above data transmission methods.

An embodiment of the present application provides a computer-readable storage medium for storing a computer program, where the computer program enables a computer to execute the method described in any one of the above data transmission methods.

Embodiments of the present application propose computer program products comprising computer program instructions that cause a computer to perform the method as described in any of the above data transmission methods.

An embodiment of the present application provides a computer program, where the computer program enables a computer to execute any one of the above data transmission methods.

According to the embodiment of the application, the terminal equipment encrypts the data by adopting the key under the condition that the key is effective, and sends the encrypted data by using the pre-configured resource, so that the transmission of the small data in the non-activated state is realized.

Drawings

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

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

Fig. 3 is a flow chart of an implementation of a data transmission method 300 according to an embodiment of the present application.

Fig. 4 is a first schematic diagram of an implementation manner of the first embodiment of the present application.

Fig. 5 is a schematic diagram of a second implementation manner of the first embodiment of the present application.

Fig. 6 is a diagram of small data transmission 600 based on preconfigured resources according to an embodiment of the present application.

Fig. 7 is a schematic diagram illustrating a manner of acquiring an updated NCC according to a second embodiment of the present application.

Fig. 8 is a schematic diagram illustrating a second method for acquiring an updated NCC according to the second embodiment of the present application.

Fig. 9 is a flowchart of an implementation 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 block 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 Description

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

It should be noted that the terms "first," "second," and the like in the description and claims of the embodiments of the present application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. The objects described in the "first" and "second" may be the same or different.

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: global System for Mobile communications (GSM) System, Code Division Multiple Access (CDMA) System, Wideband Code Division Multiple Access (WCDMA) System, General Packet Radio Service (GPRS), Long Term Evolution (Long Term Evolution, LTE) System, LTE-a System, New Radio (NR) System, Evolution System of NR System, LTE-a System over unlicensed spectrum, NR (NR-b) System, UMTS (Universal Mobile telecommunications System), UMTS (UMTS) System, WLAN-b System over unlicensed spectrum, WiFi-b System, Wireless Local Area Network (WLAN) System, Wireless Local Area network (WiFi) System, GPRS (General Packet Radio Service, GPRS) System, GPRS (GPRS) System, LTE-b System, LTE-a System, NR System, LTE-b System over unlicensed spectrum, and LTE-b System over unlicensed spectrum, A next Generation communication (5th-Generation, 5G) system, other communication systems, and the like.

Generally, conventional Communication systems support a limited number of connections and are easy to implement, however, with the development of Communication technologies, mobile Communication systems will support not only conventional Communication, but also, for example, Device to Device (D2D) Communication, Machine to Machine (M2M) Communication, Machine Type Communication (MTC), and Vehicle to Vehicle (V2V) Communication, etc., and the embodiments of the present application can also be applied to these Communication systems.

Optionally, the communication system in the embodiment of the present application may be applied to a Carrier Aggregation (CA) scenario, may also be applied to a Dual Connectivity (DC) scenario, and may also be applied to an independent (SA) networking scenario.

The frequency spectrum of the application is not limited in the embodiment of the present application. For example, the embodiments of the present application may be applied to a licensed spectrum and may also be applied to an unlicensed spectrum.

The embodiments of the present application are described in conjunction with a network device and a terminal device, where: a terminal device may also be referred to as a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a User terminal, a wireless communication device, a User agent, or a User Equipment, etc. The terminal device may be a Station (ST) in a WLAN, and may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with Wireless communication function, a computing device or other processing device connected to a Wireless modem, a vehicle-mounted device, a wearable device, and a next generation communication system, for example, a terminal device in an NR Network or a terminal device in a future evolved Public Land Mobile Network (PLMN) Network, and the like.

By way of example and not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable equipment can also be called wearable intelligent equipment, is the general term of applying wearable technique to carry out intelligent design, develop the equipment that can dress to daily wearing, like glasses, gloves, wrist-watch, dress and shoes etc.. A wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction and cloud interaction. The generalized wearable smart device includes full functionality, large size, and can implement full or partial functionality without relying on a smart phone, such as: smart watches or smart glasses and the like, and only focus on a certain type of application functions, and need to be used in cooperation with other devices such as smart phones, such as various smart bracelets for physical sign monitoring, smart jewelry and the like.

The network device may be a device for communicating with a mobile device, and the network device may be an Access Point (AP) in a WLAN, a Base Station (BTS) in GSM or CDMA, a Base Station (NodeB, NB) in WCDMA, an evolved Node B (eNB, eNodeB) in LTE, a relay Station or an Access Point, or a vehicle-mounted device, a wearable device, a network device (gNB) in an NR network, or a network device in a PLMN network that is evolved in the future.

In this embodiment, a network device provides a service for a cell, and a terminal device communicates with the network device through a transmission resource (for example, a frequency domain resource or a spectrum resource) used by the cell, where the cell may be a cell corresponding to the network device (for example, a base station), and the cell may belong to a macro base station or a base station corresponding to a Small cell (Small cell), where the Small cell may include: urban cells (Metro cells), Micro cells (Micro cells), Pico cells (Pico cells), Femto cells (Femto cells), and the like, and the small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-rate data transmission services.

Fig. 1 exemplarily shows one network device 110 and two terminal devices 120, and optionally, the wireless communication system 100 may include a plurality of network devices 110, and each network device 110 may include other numbers of terminal devices 120 within the coverage area, which is not limited in this embodiment. The embodiment of the present application may be applied to one terminal device 120 and one network device 110, and may also be applied to one terminal device 120 and another terminal device 120.

Optionally, the wireless communication system 100 may further include other network entities such as a Mobility Management Entity (MME), an Access and Mobility Management Function (AMF), which is not limited in this embodiment.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter associated objects are in an "or" relationship.

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

s210: and under the condition that the key is effective, encrypting the data by adopting the key, and sending the encrypted data by utilizing the pre-configured resource.

In some embodiments, the data is small data (small data), such as data with a small amount of data and/or a low transmission frequency transmitted by the UE in the RRC _ INACTIVE state. In the following embodiments, the data transmitted by the terminal device may be small data.

The precondition for the above method comprises at least one of the following:

the current cell of the UE supports small data transmission based on pre-configured Resource (PUR);

the UE has the capability to transmit small data in RRC _ INACTIVE state.

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

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

The NCC may be carried in an RRC release message (RRCRelease) for generating a new key.

As shown in fig. 3, optionally, before step S320, the method further includes:

s310: receiving an RRC release message, the RRC release message comprising at least one of:

pre-configuring resources;

NCC；

the validity duration of the key;

the number of valid transmissions of the key.

Optionally, the terminal device sends a data transmission resource request in a CONNECTED state (RRC _ CONNECTED state), and after receiving the RRC release message, that is, after step S310, the terminal device transitions to an INACTIVE state (RRC _ INACTIVE state).

Because the key has a certain effective duration or effective transmission times, and the key is invalid, the terminal device can acquire the updated NCC, generate the updated key by using the updated NCC, and encrypt the data by using the updated key. Optionally, as shown in fig. 3, the method further includes:

s330: acquiring an updated NCC;

s340: generating an updated key based on the updated NCC;

s350: and encrypting the data by adopting the updated key, and sending the encrypted data by utilizing the pre-configured resource.

The terminal device can obtain the updated NCC under the condition that the key is invalid; or the network equipment updates the NCC through downlink feedback of certain small data transmission, and the terminal equipment acquires the updated NCC from the response aiming at the small data.

Optionally, the terminal device may obtain the updated NCC under the condition that the key is invalid, and the obtaining manner includes at least one of:

first, the terminal device triggers an RRC recovery (RRC Resume) procedure to receive the updated NCC when/after the key fails. Specifically, the terminal device may send an RRC recovery request (RRCResumeRequest) message for triggering an RRC recovery procedure; and receiving an RRC release (rrcreelease) message sent by the network device containing the updated NCC.

Second, when/after the key is invalid, the terminal device triggers an RRC recovery procedure when it needs to send data or is paged, and receives the updated NCC. Specifically, the terminal device may send an rrcresemequest message for triggering an RRC recovery procedure; and receiving a RRCRelease message containing the updated NCC sent by the network equipment.

Thirdly, when/after the key is invalid, the terminal device triggers the data transmission process based on the random access when the terminal device needs to send data and meets the data transmission requirement based on the random access, and receives the updated NCC. Optionally, the terminal device sends a Preamble (Preamble) of the random access process, and after receiving the uplink resource configured by the network side, sends an RRCResumeRequest message by using the uplink resource; and receiving a RRCRelease message containing the updated NCC sent by the network equipment.

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

The rrcreelease message may further include an updated valid duration and/or valid transmission times of the NCC-generated key, or further include a new pre-configured resource. If a new pre-configured resource is included, the terminal device may send the encrypted data using the new pre-configured resource.

Optionally, the case that the key is valid includes: the use duration of the key does not reach the effective duration and/or the use times of the key does not reach the effective transmission times.

The case of key failure includes: the use duration of the key reaches the effective duration and/or the use times of the key reach the effective transmission times.

For example, a timer is started at key generation, during which time the key generated based on the currently configured NCC remains valid. When the timer expires (e.g., the timer reaches the above-mentioned validity period), the key generated based on the currently configured NCC expires.

Or, initializing a counter to 0 when the key is generated, and adding 1 to the counter every time uplink data transmission or downlink data reception is performed; the key generated based on the currently configured NCC remains valid until the counter reaches the above-mentioned number of valid transmissions. When the counter reaches the above-mentioned number of valid transmissions, the key generated based on the currently configured NCC is invalidated.

In some embodiments, the RRC release message further includes a Timing Advance (TA) verification criterion.

Optionally, the TA verification criterion includes a TA Timer (TA Timer) and/or a Reference Signal Received Power (RSRP) transformation threshold. And on the premise that the terminal equipment verifies that the TA is valid according to the TA verification criterion and on the condition that the secret key is valid, sending the encrypted data by using the pre-configured resource.

Specifically, the above TA valid case may include at least one of:

TA timer is in operation;

the RSRP variation (increase or decrease) is less than the RSRP transition threshold described above.

In some embodiments, after transmitting uplink data, the terminal device receives a response message in a listening window, where the response message includes at least one of the following:

a first layer acknowledgement (L1ACK) message;

a Media Access Control (MAC) Control unit (CE) that indicates a TA adjustment amount;

downlink data;

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

Upon receiving one of the responses, the UE may consider the uplink data transmission to be successful.

Optionally, the L1ACK message includes a TA adjustment amount.

Optionally, the downlink data includes a TA adjustment amount.

Optionally, the RRC message for NCC update or reconfiguration of the pre-configured resource multiplexes downlink data and/or TA adjustment amount.

The present application will now be described in detail with reference to the drawings, in which specific embodiments are shown.

The first embodiment is as follows:

the present embodiment is directed to small data transmission in an NR system with a UE in an inactive state. Optionally, the precondition that the UE performs small data transmission includes:

the current cell of the UE supports small data transmission based on the pre-configured resource;

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

The embodiment comprises the following steps:

the method comprises the following steps: the UE initiates a small data transmission resource request in a connection state, and can selectively contain resource configuration auxiliary information: such as the period of data transmission, the amount of data, etc.

Step two: the UE receives an RRC release message sent by the network, and enters an inactive state, where the RRC release message at least may include:

a) a pre-configured resource for inactive small data transmission;

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

c) an NCC for generating a key;

d) based on the validity duration or number of valid transmissions of the key generated by the currently configured NCC.

Step three: the UE generates a new key based on the NCC configured in the RRC release message. If the RRC release message contains the validity duration of the key, the UE may start a timer when generating the key. During the timer run, the key generated based on the currently configured NCC remains valid. When the timer times out, the key generated based on the currently configured NCC expires. If the RRC release message contains the effective transmission times of the key, the UE initializes a counter to 0 after generating the key, and the counter is increased by 1 every time uplink data transmission or downlink data reception is carried out. Before the counter reaches the configured effective transmission times, the key generated based on the currently configured NCC is kept effective; when the counter reaches the configured number of valid transmissions, the key generated based on the currently configured NCC is invalidated. Fig. 4 and fig. 5 are schematic diagrams of two implementation manners of the first embodiment of the present application. Fig. 4 corresponds to a manner of determining whether the key is invalid by using a timer, and fig. 5 corresponds to a manner of determining whether the key is invalid by using a counter. In fig. 4 and 5, the horizontal direction represents a time axis, and each rectangle represents data transmitted by the UE using the pre-configured resource.

Step four: during the period that the key is valid, when the UE further verifies that the TA is valid by using the TA verification criterion and the configuration resource is valid, the UE transmits the user data by using the pre-configuration resource without multiplexing the RRC message.

Step five: after the UE sends the uplink user data, the UE receives a response of the network within the listening window, and when receiving one of the following four types of responses, the UE may consider that the small data transmission is successful:

a) an L1ACK, which may optionally include a TA adjustment (Time Advance Command);

b) a MAC CE indicating a TA adjustment amount;

c) downlink data, optionally including TA adjustment;

d) and the RRC message is used for updating the NCC or reconfiguring the pre-configured resource, and can multiplex downlink data and/or TA adjustment quantity.

The TA adjustment amount may be used to update a 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 preconfigured resources according to a first embodiment of the present application, including: the UE transmits Uplink data (Uplink data) to the ng-eNB on an available PUR. The method comprises The steps that a ng-eNB and core network equipment execute advanced Data Transmission (MO-EDT) Transmission flow (MO-EDT) of a Mobile terminal caller under a 5GS Cellular Internet of Things (CIot, Cellular The Internet of Things) User Plane Function optimization scheme, wherein The core network equipment comprises Access and Mobility Management functions (AMF, Access and Mobility Management Function), Session Management functions (SMF, Session Management Function)/User Plane Management functions (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 RRC message for NCC update or reconfiguration of preconfigured resources.

Example two:

the present embodiment relates to a procedure for acquiring a new NCC by a UE. When the current key fails, the UE may acquire a new NCC through the RRC connection release message again in one of the following manners:

the first method is as follows: the UE triggers the RRC Resume procedure for updating NCC. Specifically, the UE may send a RRCResumeRequest message and receive a rrcreelease message containing a new NCC sent by the network side.

The second method comprises the following steps: when uplink data arrives or the UE is paged, the UE triggers an RRC Resume procedure. The specific manner is the same as above.

The third method comprises the following steps: when the uplink data arrives and meets the decimal data transmission requirement, the UE triggers a random access-based decimal data transmission process. Specifically, the UE may send a Preamble (Preamble) in the random access process, and after receiving the uplink resource configured by the network side, send an RRCResumeRequest message using the uplink resource; and receives the RRCRelease message containing the new NCC sent by the network device.

Fig. 7 is a schematic diagram illustrating a manner of acquiring an updated NCC according to a second embodiment of the present application. Fig. 7 illustrates an example of the timer timeout, which corresponds to the first to third manners. As shown in fig. 7, a time axis is horizontally represented, each rectangle represents data sent by the UE using the pre-configured resource, and when/after the timer is over time, an RRC Resume procedure or a small data transmission procedure based on random access is triggered; then, an RRCRelease message which is sent by the network side and contains a new NCC is received, the new NCC is adopted to regenerate the secret key, and a timer is started. The RRCRelease message may also carry the valid duration or the valid transmission times of the new NCC generated key.

The method is as follows: the RRCResumeRequest message or the MAC CE indicating NCC update is multiplexed in small data transmission based on the pre-configured resource. Thereafter, the UE receives the RRCRelease message containing the new NCC sent by the network device.

Fig. 8 is a schematic diagram illustrating a second method for acquiring an updated NCC according to the second embodiment of the present application. Fig. 8 takes the timeout of the timer as an example, and corresponds to the fourth mode. As shown in fig. 8, the horizontal direction represents the time axis; each rectangle before the timer expires represents data transmitted by the UE using the pre-configured resource. Upon/after the timer expires, a RRCResumeRequest message or a MAC CE indicating NCC update is multiplexed in the small data based on the pre-configured resource. And then, the UE receives an RRCRelease message which is sent by the network side and contains a new NCC, regenerates the key by adopting the new NCC and starts a timer. The rrcreelease message may also carry the valid duration or the valid transmission times of the new NCC generated key.

The four ways correspond to the process of acquiring the updated NCC when/after the key is invalid. In the embodiment of the present application, when the key is not invalid, that is, during the operation of the timer or before the counter does not reach the configured valid transmission times, the gNB may update the NCC through downlink feedback for a certain small data transmission.

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

As can be seen from the above process, in the data transmission method provided in the embodiment of the present application, the terminal device may transmit uplink user data using the pre-configured resource without multiplexing an RRC message in the small data transmission process; and the key derived by the NCC can be reused for many times without frequently updating the NCC.

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

s910: and sending a pre-configured resource and/or a next hop link count (NCC) for generating a key, wherein the pre-configured resource and the key are used for sending data by the terminal equipment.

In some embodiments, sending the pre-configured resources and/or the NCC for generating the key comprises:

receiving a data transmission resource request; sending an RRC release message, the RRC release message comprising at least one of:

pre-configuring resources;

NCC；

the validity duration of the key;

the number of valid transmissions of the key.

Optionally, the method further includes: the updated NCC is sent.

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

Optionally, the TA verification criteria comprises a TA timer and/or an RSRP transformation threshold.

Optionally, the TA verification criterion is used for the terminal device to verify whether the TA is valid, and send the encrypted data by using the preconfigured resource under the condition that the TA is valid and the key is valid.

In some embodiments, the data includes small data transmitted by the terminal device in the unconnected state.

In some embodiments, the above method further comprises: sending a response message, the response message including at least one of:

an L1ACK message;

a MAC CE indicating a TA adjustment amount;

downlink data;

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

Optionally, the L1ACK message includes a TA adjustment amount.

Optionally, the downlink data includes a TA adjustment amount.

An embodiment of the present application further provides a terminal device, and fig. 10 is a schematic structural diagram of a terminal device 1000 according to the embodiment of the present application, including:

the transmission module 1010 is configured to encrypt the data by using the key and send the encrypted data by using the preconfigured resource when the key is valid.

In some embodiments, as shown in fig. 11, the terminal device further includes:

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

Optionally, the transmission module 1010 is further configured to: sending a data transmission resource request; receiving a radio resource control, RRC, release message, the RRC release message comprising at least one of:

the pre-configured resource;

the NCC;

the validity duration of the key;

the number of valid transmissions of the key.

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

further comprising: a state transition module 1130, configured to transition the terminal device to an inactive state after receiving the RRC release message.

Optionally, the transmission module 1010 is further configured to: acquiring an updated NCC; generating an updated key based on the updated NCC; and encrypting the data by adopting the updated key, and sending the encrypted data by utilizing a pre-configured resource.

Optionally, the transmitting module 1010 obtains the updated NCC in case that the key is invalid.

Optionally, the transmitting module 1010 obtains the updated NCC by using at least one of:

triggering an RRC recovery process when/after the key is invalid, and receiving the updated NCC;

triggering an RRC recovery process when the key is invalid or after the key is invalid and when data needs to be sent or the key is paged, and receiving the updated NCC;

when/after the key is invalid, when data needs to be sent and the data transmission requirement based on random access is met, triggering a data transmission process based on random access, and receiving the updated NCC;

and multiplexing an RRC recovery request message or an MAC CE indicating NCC update in the data transmitted by the pre-configured resource when/after the key is invalid, and receiving the updated NCC.

Optionally, the updated NCC is obtained from a response to the data.

Optionally, the case that the key is valid includes: and the use duration of the key does not reach the effective duration and/or the use times of the key does not reach the effective transmission times.

Optionally, the key failure condition includes: the use time of the key reaches the effective time and/or the use times of the key reaches the effective transmission times.

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

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

Optionally, the transmission module 1010 sends the encrypted data by using the preconfigured resource under the condition that the key is valid on the premise that the TA is valid according to the TA verification criterion.

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

Optionally, the 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:

a first layer acknowledges the L1ACK message;

a Media Access Control (MAC) control unit (CE) for indicating a TA adjustment amount;

downlink data;

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

Optionally, the L1ACK message includes a TA adjustment amount.

Optionally, the downlink data includes a TA adjustment amount.

It should be understood that the above and other operations and/or functions of the modules in the terminal device according to the embodiment of the present application are respectively for implementing the corresponding flows of the terminal device in the method 200 of fig. 2 and the method 300 of fig. 3, and are not described herein again for brevity.

An embodiment of the present application further provides a network device, and fig. 12 is a schematic structural diagram of a network device 1200 according to an embodiment of the present application, including:

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

Optionally, the configuration module 1210 is configured to: receiving a data transmission resource request; sending a radio resource control, RRC, release message, the RRC release message comprising at least one of:

the pre-configured resource;

the NCC;

the validity duration of the key;

the number of valid transmissions of the key.

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

Optionally, the TA verification criterion is used for the terminal device to verify whether the TA is valid, and send the encrypted data by using the preconfigured resource under the condition that the TA is valid and the secret key is valid.

Optionally, the 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:

a first layer acknowledges the L1ACK message;

a Media Access Control (MAC) control unit (CE) for indicating TA adjustment quantity;

downlink data;

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

Optionally, the L1ACK message includes a TA adjustment amount.

Optionally, the downlink data includes a TA adjustment amount.

Optionally, the RRC message for NCC update or reconfiguration of the preconfigured resource multiplexes downlink data and/or TA adjustment amount.

It should be understood that the above and other operations and/or functions of the modules in the network device according to the embodiment of the present application are respectively for implementing the corresponding flows of the network device in the method 900 of fig. 9, and are not described herein again for brevity.

Fig. 14 is a schematic block 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. From memory 1420, processor 1410 may invoke and execute a computer program to implement the methods of the embodiments of the present application.

The memory 1420 may be a separate device from the processor 1410, or may be integrated into 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, and in particular, may transmit information or data to or receive information or data transmitted by other devices.

The transceiver 1430 may include a transmitter and a receiver, among others. The transceiver 1430 may further include antennas, and the number of antennas may be one or more.

Optionally, the communication device 1400 may be a terminal device in the embodiment of the present application, and the communication device 1400 may implement a corresponding process implemented by the terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.

Optionally, the communication device 1400 may be a network device according to this embodiment, and the communication device 1400 may implement a corresponding procedure implemented by the network device in each method according to this embodiment, which is not described herein again for brevity.

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 a 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. From the memory 1520, the processor 1510 can call and execute a computer program to implement the method in the embodiment of the present application.

The memory 1520 may be a separate device from the processor 1510 or may be integrated into the processor 1510.

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

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

Optionally, the chip may be applied to the terminal device or the network device in the embodiment of the present application, and the chip may implement a corresponding process implemented by the terminal device or the network device in each method in the embodiment of the present application, which is not described herein again for brevity.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as 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 (DSPs), Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), or other programmable logic devices, transistor logic devices, discrete hardware components, etc. The general-purpose processor mentioned above may be a microprocessor, or any conventional processor, etc.

The above-mentioned memories may be either volatile or nonvolatile memories, or may include both volatile and nonvolatile memories. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash memory. The volatile memory may be a Random Access Memory (RAM).

It should be understood that the above memories are exemplary but not limiting illustrations, for example, the memories in the embodiments of the present application may also be Static Random Access Memory (SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (enhanced SDRAM, ESDRAM), Synchronous Link DRAM (SLDRAM), Direct Rambus RAM (DR RAM), and the like. That is, the memory in the embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions can 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 instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that includes one or more of the available media. The usable medium may be a magnetic medium (e.g., a floppy Disk, a hard Disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a Solid State Disk (SSD)), among others.

It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

The above description is only for the specific embodiments of the present application, but the protection scope of the present application is not limited thereto, and any person skilled in the art can easily think of the changes or substitutions within the technical scope of the present application, and shall cover the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A data transmission method is applied to terminal equipment and comprises the following steps:

and under the condition that the key is effective, encrypting the data by adopting the key, and sending the encrypted data by utilizing the pre-configured resource.
The method of claim 1, further comprising:

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

the pre-configured resource;

the NCC;

the validity duration of the key;

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

after receiving the RRC release message, the method further includes: and the terminal equipment is converted into an inactive state.
The method of any of claims 1 to 4, further comprising:

acquiring an updated NCC;

generating an updated key based on the updated NCC;

and encrypting the data by adopting the updated key, and sending the encrypted data by utilizing a pre-configured resource.
The method of claim 5, wherein the updated NCC is obtained in case of a failure of the key.
The method of claim 6, wherein the manner of obtaining updated NCCs comprises at least one of:

when/after the key is invalid, the terminal equipment triggers an RRC recovery process and receives the updated NCC;

when/after the key is invalid, the terminal equipment triggers an RRC recovery process when data needs to be sent or the terminal equipment is paged, and receives the updated NCC;

when/after the key is invalid, the terminal equipment triggers a data transmission process based on random access when data needs to be sent and the data transmission requirement based on random access is met, and receives the updated NCC;

and when/after the key is invalid, the terminal equipment multiplexes an RRC recovery request message or a Media Access Control (MAC) control unit (CE) indicating NCC update in the data transmitted by the pre-configured resource and receives the updated NCC.
The method of claim 5, wherein the updated NCC is obtained from a response to the data.
The method of any of claims 3 to 8, wherein the case that the key is valid comprises: and the use duration of the key does not reach the effective duration and/or the use times of the key does not reach the effective transmission times.
The method of claim 6, 7 or 9, wherein the key failure condition comprises: the use time of the key reaches the effective time and/or the use times of the key reaches the effective transmission times.
The method according to any of claims 3 to 10, wherein the RRC release message further comprises timing advance, TA, verification criteria.
The method of claim 11, wherein the TA verification criteria comprises a TA timer and/or a reference signal received power, RSRP, transition threshold.
A method according to claim 11 or 12, wherein on a condition that the terminal device verifies TA is valid according to the TA verification criterion, sending the encrypted data using the pre-configured resource if the key is valid.
The method of any of claims 1 to 13, wherein the data comprises small data transmitted by the terminal device in a non-connected state.
The method of any of claims 1 to 14, further comprising:

the terminal equipment receives a response message in a monitoring window, wherein the response message comprises at least one of the following:

a first layer acknowledgement L1ACK message;

a MAC CE indicating a TA adjustment amount;

downlink data;

RRC message for NCC update or pre-configured resource reconfiguration.
The method of claim 15, wherein the L1ACK message includes a TA adjustment.
The method of claim 15, wherein the downlink data comprises a TA adjustment amount.
The method of claim 15, wherein the RRC message for NCC update or pre-configured resource reconfiguration multiplexes downlink data and/or TA adjustment.
A data transmission method is applied to network equipment and comprises the following steps:

and sending a pre-configured resource and/or a next hop link count (NCC) for generating a key, wherein the pre-configured resource and the key are used for sending data by the terminal equipment.
The method of claim 19, wherein the sending pre-configured resources and/or next hop link count (NCC) for generating keys comprises:

receiving a data transmission resource request; sending a radio resource control, RRC, release message, the RRC release message comprising at least one of:

the pre-configured resource;

the NCC;

the validity duration of the key;

the number of valid transmissions of the key.
The method of claim 19 or 20, further comprising: the updated NCC is sent.
The method according to any of claims 19 to 21, wherein the RRC release message further comprises timing advance, TA, verification criteria.
The method of claim 22, wherein the TA verification criteria comprises a TA timer and/or a reference signal received power, RSRP, transition threshold.
A 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 if the TA is valid and the key is valid, the encrypted data is sent using the preconfigured resource.
The method according to any one of claims 19 to 24, wherein the data comprises small data transmitted by the terminal device in a non-connected state.
The method of any of claims 19 to 25, further comprising: sending a response message, the response message including at least one of:

a first layer acknowledgement L1ACK message;

a Media Access Control (MAC) control unit (CE) for indicating TA adjustment quantity;

downlink data;

RRC message for NCC update or pre-configured resource reconfiguration.
The method of claim 26, wherein the L1ACK message includes a TA adjustment.
The method of claim 26, wherein the downlink data comprises a TA adjustment amount.
The method of claim 26, wherein the RRC message for NCC update or preconfigured resource reconfiguration multiplexes downlink data and/or TA adjustments.
A terminal device, comprising:

and the transmission module is used for encrypting the data by adopting the key under the condition that the key is effective and sending the encrypted data by utilizing the pre-configured resource.
The terminal device of claim 30, further comprising:

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

the pre-configured resource;

the NCC;

the validity duration of the key;

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

further comprising: and the state conversion module is used for converting the terminal equipment into an inactive state after receiving the RRC release message.
The terminal device according to any one of claims 30 to 33, wherein the transmission module is further configured to: acquiring an updated NCC; generating an updated key based on the updated NCC; and encrypting the data by adopting the updated key, and sending the encrypted data by utilizing a pre-configured resource.
The terminal device of claim 34, wherein the transmission module obtains an updated NCC in case of a failure of the key.
The terminal device of claim 35, wherein the transmission module obtains the updated NCC using at least one of:

triggering an RRC recovery process when/after the key is invalid, and receiving the updated NCC;

triggering an RRC recovery process when the key is invalid or after the key is invalid and when data needs to be sent or the key is paged, and receiving the updated NCC;

when/after the key is invalid, when data needs to be sent and the data transmission requirement based on random access is met, triggering a data transmission process based on random access, and receiving the updated NCC;

and multiplexing an RRC recovery request message or an MAC CE indicating NCC update in the data transmitted by the pre-configured resource when/after the key is invalid, and receiving the updated NCC.
The terminal device of claim 34, wherein the updated NCC is obtained from a response to the data.
The terminal device of any of claims 32 to 37, wherein the case where the key is valid comprises: and the use duration of the key does not reach the effective duration and/or the use times of the key does not reach the effective transmission times.
The terminal device of claim 35, 36 or 38, wherein the case of key failure comprises: the use time of the key reaches the effective time and/or the use times of the key reaches the effective transmission times.
A terminal device according to any of claims 32 to 39, wherein the RRC release message further comprises timing Advance TA verification criteria.
A terminal device according to claim 40, wherein the TA verification criteria includes a TA timer and/or a reference Signal received Power, RSRP, transition threshold.
A terminal device according to claim 40 or 41, wherein the transmission module is configured to send the encrypted data using the pre-configured resource if the key is valid, on the premise that TA validation is verified according to the TA verification criterion to be valid.
A terminal device according to any one of claims 30 to 42, wherein the data comprises small data transmitted by the terminal device in a non-connected state.
The terminal device of any of claims 30 to 43, further comprising:

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

a first layer acknowledgement L1ACK message;

a Media Access Control (MAC) control unit (CE) for indicating a TA adjustment amount;

downlink data;

RRC message for NCC update or pre-configured resource reconfiguration.
The terminal device of claim 44, wherein the L1ACK message includes a TA adjustment amount.
The terminal device of claim 44, wherein the downlink data comprises a TA adjustment amount.
The terminal device of claim 44, wherein the RRC message used for NCC update or pre-configured resource reconfiguration multiplexes downlink data and/or TA adjustment amount.
A network device, comprising:

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

the pre-configured resource;

the NCC;

the validity duration of the key;

the number of valid transmissions of the key.
The network device of claim 48 or 49, further comprising: and the updating module is used for sending the updated NCC.
A network device according to any of claims 48 to 50, wherein the RRC release message further comprises timing Advance TA verification criteria.
A network device as defined in claim 51, wherein the TA verification criteria include a TA timer and/or a Reference Signal Received Power (RSRP) transition threshold.
A 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 in case the TA is valid and the secret key is valid, the encrypted data is sent using the preconfigured resource.
The network device of any one of claims 48 to 53, wherein the data comprises small data transmitted by the terminal device in the unconnected state.
The network device of any of claims 48 to 54, further comprising: a response module for sending a response message, the response message including at least one of:

a first layer acknowledgement L1ACK message;

a Media Access Control (MAC) control unit (CE) for indicating a TA adjustment amount;

downlink data;

RRC message for NCC update or pre-configured resource reconfiguration.
The network device of claim 55, wherein the L1ACK message includes a TA adjustment amount.
The network device of claim 55, wherein the downlink data comprises a TA adjustment amount.
The network device of claim 55, wherein the RRC message for NCC update or preconfigured resource reconfiguration multiplexes downlink data and/or TA adjustment.
A terminal device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 1 to 18.
A network device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 19 to 29.
A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 1 to 18.
A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 19 to 29.
A computer-readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 18.
A computer-readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 19 to 29.
A computer program product comprising computer program instructions to cause a computer to perform the method of any one of claims 1 to 18.
A computer program product comprising computer program instructions to cause a computer to perform the method of any of claims 19 to 29.
A computer program for causing a computer to perform the method of any one of claims 1 to 18.
A computer program for causing a computer to perform the method of any one of claims 19 to 29.