CN116326179B

CN116326179B - Data transmission method, terminal device and network device

Info

Publication number: CN116326179B
Application number: CN202080105901.0A
Authority: CN
Inventors: 林雪; 卢前溪
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2020-12-21
Filing date: 2020-12-21
Publication date: 2024-11-22
Anticipated expiration: 2040-12-21
Also published as: WO2022133682A1; CN116326179A

Abstract

A data transmission method, terminal equipment and network equipment, the method comprising: a terminal equipment in a radio resource control (RRC) inactive state sends first information to a network equipment when there is data to be transmitted and a condition for data transmission in an inactive state is met; wherein the first information comprises a first RRC message, the first RRC message is transmitted via a first signaling radio bearer (SRB), the first RRC message comprises a target non-access layer (NAS) message, the target NAS message is obtained by the terminal equipment performing encryption and integrity processing on the first NAS message, and the data to be transmitted comprises the first NAS message.

Description

Data transmission method, terminal equipment and network equipment

Technical Field

The embodiment of the application relates to the field of communication, in particular to a data transmission method, terminal equipment and network equipment.

Background

The small data transmission (SMALL DATA transmission, SDT) is a data transmission mode of the terminal device in the RRC INACTIVE state (rrc_inactive), and the SDT may include an SDT based on a random access procedure or may be an SDT based on a preconfigured uplink resource (Preconfigured Uplink Resource, PUR).

SDT is typically transmitted via data radio bearers (Data Radio Bearers, DRB) configured by the network device, signaling radio bearers (SIGNALING RADIO BEARERS, SRB) do not support small data transmission, and positioning measurement reports need to be carried in Non-Access Stratum (NAS) messages and air interface transmission is implemented via SRB, so how to implement transmission of NAS messages in RRC inactive state is an urgent problem to be solved.

Disclosure of Invention

The application provides a data transmission method, terminal equipment and network equipment, which can realize the transmission of NAS information in an RRC inactive state.

In a first aspect, a data transmission method is provided, including: the method comprises the steps that a terminal device in a Radio Resource Control (RRC) inactive state sends first information to a network device under the condition that data to be transmitted are needed and inactive state data transmission conditions are met; the first information includes a first RRC message, the first RRC message is transmitted through a first signaling radio bearer SRB, the first RRC message includes a target non-access stratum NAS message, the target NAS message is obtained by encrypting and integrity processing the first NAS message by the terminal device, and the data to be transmitted includes the first NAS message.

In a second aspect, a data transmission method is provided, including: the network equipment receives first information sent by the Radio Resource Control (RRC) inactive state terminal equipment under the condition that data to be transmitted are required to be transmitted and inactive state data transmission conditions are met;

The first information includes a first RRC message, the first RRC message is transmitted through a first signaling radio bearer SRB, the first RRC message includes a target non-access stratum NAS message, the target NAS message is obtained by encrypting and integrity processing the first NAS message by the terminal device, and the data to be transmitted includes the first NAS message.

In a third aspect, a terminal device is provided for performing the method in the first aspect or each implementation manner thereof.

Specifically, the terminal device comprises functional modules for performing the method of the first aspect or its implementation manner.

In a fourth aspect, a network device is provided for performing the method of the second aspect or implementations thereof.

In particular, the network device comprises functional modules for performing the method of the second aspect or implementations thereof described above.

In a fifth aspect, a terminal device is provided comprising a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory and executing the method in the first aspect or various implementation manners thereof.

In a sixth aspect, a network device is provided that includes a processor and a memory. The memory is for storing a computer program and the processor is for calling and running the computer program stored in the memory for performing the method of the second aspect or implementations thereof described above.

A seventh aspect provides a chip for implementing the method of any one of the first to second aspects or each implementation thereof.

Specifically, the chip includes: a processor for calling and running a computer program from a memory, causing a device in which the apparatus is installed to perform the method as in any one of the first to second aspects or implementations thereof described above.

In an eighth aspect, a computer-readable storage medium is provided for storing a computer program that causes a computer to perform the method of any one of the above-described first to second aspects or implementations thereof.

A ninth aspect provides a computer program product comprising computer program instructions for causing a computer to perform the method of any one of the first to second aspects or implementations thereof.

In a tenth aspect, there is provided a computer program which, when run on a computer, causes the computer to perform the method of any one of the first to second aspects or implementations thereof.

By means of the technical scheme, under the condition that data to be transmitted are needed and the inactive state data transmission condition is met, the terminal equipment can encrypt and protect the integrity of the first NAS message in the data to be transmitted to obtain the target NAS message, the target NAS message is further packaged in the first RRC message, the first RRC message is transmitted through the first SRB, and therefore the NAS message of the terminal equipment in the RRC inactive state can be transmitted.

Drawings

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

Fig. 2 is a schematic flow chart of a UE requesting PUR.

Fig. 3 is a schematic diagram of data transmission using PUR.

Fig. 4 is a schematic diagram of data transmission using random access resources.

Fig. 5 is a schematic diagram of a data transmission method according to an embodiment of the present application.

Fig. 6 is a schematic diagram of another data transmission method according to an embodiment of the present application.

Fig. 7 is a schematic diagram of still another data transmission method according to an embodiment of the present application.

Fig. 8 is a schematic block diagram of a terminal device according to an embodiment of the present application.

Fig. 9 is a schematic block diagram of another terminal device provided in an embodiment of the present application.

Fig. 10 is a schematic block diagram of a communication device provided in another embodiment of the present application.

Fig. 11 is a schematic block diagram of a chip provided in an embodiment of the present application.

Fig. 12 is a schematic block diagram of a communication system provided in an embodiment of the present application.

Detailed Description

The following description of the technical solutions according to the embodiments of the present application will be given with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art to which the application pertains without inventive faculty, are intended to fall within the scope of the application.

The technical scheme of the embodiment of the application can be applied to various communication systems, such as: global system for mobile communications (Global System of Mobile communication, GSM), code division multiple access (Code Division Multiple Access, CDMA) system, wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, general packet Radio Service (GENERAL PACKET Radio Service, GPRS), long term evolution (Long Term Evolution, LTE) system, long term evolution advanced (Advanced long term evolution, LTE-a) system, new Radio (NR) system, evolution system of NR system, LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum, NR-U) system on unlicensed spectrum, non-terrestrial communication network (Non-TERRESTRIAL NETWORKS, NTN) system, universal mobile communication system (Universal Mobile Telecommunication System, UMTS), wireless local area network (Wireless Local Area Networks, WLAN), wireless fidelity (WIRELESS FIDELITY, WIFI), fifth Generation communication (5 th-Generation, 5G) system, or other communication system, etc.

Generally, the number of connections supported by the conventional Communication system is limited and easy to implement, however, with the development of Communication technology, the mobile Communication system will support not only conventional Communication but also, for example, device-to-Device (D2D) Communication, machine-to-machine (Machine to Machine, M2M) Communication, machine type Communication (MACHINE TYPE Communication, MTC), inter-vehicle (Vehicle to Vehicle, V2V) Communication, or internet of vehicles (Vehicle to everything, V2X) 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 (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, or an independent (Standalone, SA) networking scenario.

Optionally, the communication system in the embodiment of the present application may be applied to unlicensed spectrum, where unlicensed spectrum may also be considered as shared spectrum; or the communication system in the embodiment of the present application may also be applied to licensed spectrum, where licensed spectrum may also be considered as non-shared spectrum.

Embodiments of the present application are described in connection with a network device and a terminal device, where the 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, a User Equipment, or the like.

The terminal device may be a STATION (ST) in a WLAN, may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) STATION, a Personal digital assistant (Personal DIGITAL ASSISTANT, PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a next generation communication system such as an NR network, or a terminal device in a future evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.

In the embodiment of the application, the terminal equipment can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; can also be deployed on the water surface (such as ships, etc.); but may also be deployed in the air (e.g., on aircraft, balloon, satellite, etc.).

In the embodiment of the present application, the terminal device may be a Mobile Phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an augmented Reality (Augmented Reality, AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in unmanned (SELF DRIVING), a wireless terminal device in remote medical (remote medical), a wireless terminal device in smart grid (SMART GRID), a wireless terminal device in transportation security (transportation safety), a wireless terminal device in smart city (SMART CITY), or a wireless terminal device in smart home (smart home), or the like.

By way of example, and not limitation, in embodiments of the present application, the terminal device may also be a wearable device. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wear by applying wearable technology and developing wearable devices, such as glasses, gloves, watches, clothes, shoes and the like. The 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 can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

In the embodiment of the present application, the network device may be a device for communicating with a mobile device, where the network device may be an Access Point (AP) in a WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, a relay station or an Access Point, a vehicle device, a wearable device, a network device (gNB) in an NR network, a network device in a PLMN network for future evolution, or a network device in an NTN network, etc.

By way of example, and not limitation, in embodiments of the present application, a network device may have a mobile nature, e.g., the network device may be a mobile device. Alternatively, the network device may be a satellite, a balloon station. For example, the satellite may be a Low Earth Orbit (LEO) satellite, a medium earth Orbit (medium earth Orbit, MEO) satellite, a geosynchronous Orbit (geostationary earth Orbit, GEO) satellite, a high elliptical Orbit (HIGH ELLIPTICAL Orbit, HEO) satellite, or the like. Alternatively, the network device may be a base station disposed on land, in a water area, or the like.

In the embodiment of the present application, a network device may provide services for a cell, where a terminal device communicates with the network device through a transmission resource (e.g., a frequency domain resource, or a spectrum resource) used by the cell, where the cell may be a cell corresponding to the network device (e.g., a base station), and the cell may belong to a macro base station, or may belong to 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 transmitting power and are suitable for providing high-rate data transmission services.

An exemplary communication system 100 to which embodiments of the present application may be applied is shown in fig. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within the coverage area.

Fig. 1 illustrates one network device and two terminal devices by way of example, and the communication system 100 may alternatively include multiple network devices and may include other numbers of terminal devices within the coverage area of each network device, as embodiments of the application are not limited in this regard.

Optionally, the communication system 100 may further include a network controller, a mobility management entity, and other network entities, which are not limited by the embodiment of the present application.

It should be understood that a device having a communication function in a network/system according to an embodiment of the present application may be referred to as a communication device. Taking the communication system 100 shown in fig. 1 as an example, the communication device may include a network device 110 and a terminal device 120 with communication functions, where the network device 110 and the terminal device 120 may be specific devices described above, and are not described herein again; the communication device may also include other devices in the communication system 100, such as a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

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

It should be understood that the "indication" mentioned in the embodiments of the present application may be a direct indication, an indirect indication, or an indication having an association relationship. For example, a indicates B, which may mean that a indicates B directly, e.g., B may be obtained by a; it may also indicate that a indicates B indirectly, e.g. a indicates C, B may be obtained by C; it may also be indicated that there is an association between a and B.

In the description of the embodiments of the present application, the term "corresponding" may indicate that there is a direct correspondence or an indirect correspondence between the two, or may indicate that there is an association between the two, or may indicate a relationship between the two and the indicated, configured, etc.

In the embodiment of the present application, the "predefining" may be implemented by pre-storing corresponding codes, tables or other manners that may be used to indicate relevant information in devices (including, for example, terminal devices and network devices), and the present application is not limited to the specific implementation manner thereof. Such as predefined may refer to what is defined in the protocol.

In the embodiment of the present application, the "protocol" may refer to a standard protocol in the communication field, for example, may include an LTE protocol, an NR protocol, and related protocols applied in a future communication system, which is not limited in the present application.

In order to facilitate understanding of the technical solution of the embodiments of the present application, the technical solution of the present application is described in detail below through specific embodiments. The following related technologies may be optionally combined with the technical solutions of the embodiments of the present application, which all belong to the protection scope of the embodiments of the present application. Embodiments of the present application include at least some of the following.

It should be understood that in the embodiment of the present application, NR may be deployed independently, and a new radio resource control (Radio Resource Control, RRC) state, i.e., rrc_inactive state, is defined in the 5G network environment for the purposes of reducing air interface signaling and quickly recovering radio connection and quickly recovering data traffic. This state is different from the rrc_idle and rrc_connected states.

In the rrc_idle state: mobility is cell selection reselection based on terminal equipment, paging is initiated by a Core Network (CN), and paging areas are configured by the CN. The base station side does not have an Access Stratum (AS) context of the terminal equipment, and does not have RRC connection.

In the rrc_connected state: there is an RRC connection and the base station and the terminal device have a terminal device AS context. The network device knows that the location of the terminal device is cell specific. Mobility is mobility controlled by the network device. Unicast data may be transmitted between the terminal device and the base station.

Rrc_inactive: mobility is cell selection reselection based on terminal equipment, there is a connection between CN-NRs, terminal equipment AS context is present on a certain base station, paging is triggered by the radio access network (Radio Access Network, RAN), the RAN-based paging area is managed by the RAN, the network equipment knows that the location of the terminal equipment is based on the RAN paging area level.

In the embodiment of the present application, the inactive state may also be referred to as a deactivated state, which is not limited in this regard.

The network device may control state transitions of the terminal device, e.g., the terminal device in rrc_connected state may enter rrc_idle state by releasing RRC connection; the terminal device in the rrc_idle state may enter the rrc_connected state by establishing an RRC connection; the UE in the rrc_connected state may enter the rrc_inactive state through a suspension release (RELEASE WITH Suspend) RRC connection; the UE in the rrc_inactive state may enter the rrc_connected state through a Resume (Resume) RRC connection, and may also enter the rrc_idle state through release of the RRC connection.

In LTE Release16 (Release 16), methods for data transmission using preconfigured uplink resources (Preconfigured Uplink Resource, PUR) in IDLE (IDLE) state are introduced for narrowband internet of things (Narrow Band Internet of Things, NB-IoT) and enhanced machine type communication (ENHANCED MACHINE TYPE of communication, eMTC) scenarios. Fig. 2 shows a configuration procedure of PUR. Specifically, the cell in which the UE is located supports uplink transmission based on PUR, and the UE is in a connected state, in S21, the UE may send a PUR configuration request (PURConfigurationRequest) to a network device, such as an eNB or a next generation eNB (ng-eNB), for requesting the network device to configure PUR.

Optionally, at least one of the following may be included in PURConfigurationRequest: requested PUR period, TBS, number of PURs. The network device sends the PUR configuration to the UE via a radio resource control (Radio Resource Control, RRC) message, which may be, for example, an RRC connection release (RRCConnectinRelease) message, and the network device configures PUR for the UE by including a PUR configuration (PUR-Config) field in the RRC message, while releasing the UE to the IDLE state. Alternatively, the PUR configuration may be determined by the network device, or may be determined based on at least one of a request of the UE, UE registration information, and a local policy.

It should be noted that PUR is only valid in the serving cell or the currently camping cell of the UE, and when the UE detects a cell change and initiates random access in a new cell, the UE needs to release the PUR of the original cell configuration.

Before a UE in IDLE state wants to use PUR for data transmission, the following preconditions need to be satisfied:

1. an effective TA needs to satisfy two conditions at the same time:

a. timing advance (TIMING ADVANCE, TA) timer (timer): after receiving the high-layer instruction, the media access Control (MEDIA ACCESS Control, MAC) layer starts the TA timer, when the high-layer determines the TA validity, it can confirm whether the TA timer is in the running period to the MAC layer, when the TA timer times out, the MAC layer needs to feed back to the high-layer, when the TA timer runs, the TA is considered valid, otherwise the TA is invalid.

B. Reference signal received Power (REFERENCE SIGNAL RECEIVING Power, RSRP) change: when the change (increase or decrease) of RSRP is greater than the set threshold, i.e., the RSRP is changed too much, the TA is considered to be invalid, otherwise the TA is considered to be valid.

2. The UE is configured with a downlink counter (Next Hop Chaining Count, NCC) that is used for the derivation of the new key.

Alternatively, the NCC may be configured by an RRC message, for example, the RRC message may be an RRCConnectionRelease message.

3. An effective PUR. I.e. the cell in which the UE resides, supports PUR and is configured with PUR.

4. There is an RRC connection setup or recovery requirement, if uplink data arrives;

With reference to fig. 3, a flow of data transmission by the UE in the IDLE state using PUR will be described.

In case of satisfying the foregoing preconditions, the idle UE may perform data transmission using PUR.

S41, the UE sends an RRC message, such as an RRC connection resume request (RRCConnectionResumeRequest) message, to the network device, such as an eNB/ng-eNB.

Optionally, the RRC message may include: resume ID (Resume ID) or Information RNTI (I-RNTI), establishment cause (establishment cause), shortResumeMAC-I/ResumeMAC-I.

Wherein the Resume ID/I-RNTI is used for the network device to identify the context of the UE in a suspended (suspend) state, and shortResumeMAC-I/ResumeMAC-I is used for the authentication of the UE.

Further, the UE recovers all signaling radio bearers (SIGNALING RADIO BEARERS, SRB) and data radio bearers (Data Radio Bearer, DRB). The new key is derived using the NCC contained in the RRCConnectionRelease message of the last connection, the user data to be transmitted is encrypted and transmitted on a dedicated transport channel (DEDICATED TRANSMISSION CHANNEL, DTCH) and multiplexed with RRCConnectionResumeRequest on a common control channel (common control channel, CCCH).

S42, data transmission is carried out between the access network equipment and the core network equipment.

The network devices may include access network devices, such as enbs, ng-enbs and core network devices, such as Mobility management entities (Mobility MANAGEMENT ENTITY, MME) and serving gateways (SERVING GATEWAY, S-GW).

After the access network device submits the user data to the core network device, the eNB/ng-eNB further maintains the UE in an IDLE state through an RRCConnection Release message. The RRCConnectionRelease message may contain, for example, the following information:

a) The release reason (releaseCause) is set as RRC suspension (RRC-Suspend);

b)resume ID/I-RNTI；

c)NCC；

d) The DRB continues reliable header compression (Robust Header Compression, ROHC), DRB-ContinueROHC.

If there is downlink data transmission on the network side, the downlink data is encrypted and transmitted through the DTCH, and multiplexed with the RRCConnectionRelease message on the DCCH.

In the LTE system, small data transmission (EARLY DATA transmission, EDT) is introduced, and in the EDT process, the terminal device may always remain in an idle (idle) state, a suspended (suspended) state, or an inactive (inactive) state, so as to complete transmission of uplink and/or downlink small data packets. For example, as shown in fig. 4, the user plane data transmission scheme may be specifically implemented as the following flows in S31 to S38.

S31, the UE sends an RRC connection Resume Request (Resume Request) to the eNB, wherein the RRC connection Resume Request comprises Resume ID (Resume ID) or Information RNTI (Information RNTI, I-RNTI), and a reason (establishment cause) is established, namely shortResumeMAC-I. Meanwhile, the method also comprises uplink data (namely small data transmission) sent by the UE;

S32, the eNB sends a UE context recovery request (UE CONTEXT RESUME REQUEST) to a Mobility management entity (Mobility MANAGEMENT ENTITY, MME);

S33, modifying the bearing between the MME and the service gateway (SERVING GATEWAY, SGW);

s34, the MME sends a UE context recovery response (UE CONTEXT RESUME RESPONSE) to the eNB;

S35, the eNB sends uplink data (namely small data transmission) sent by the UE to the SGW;

s36, the SGW receives downlink data (optionally) sent by the eNB;

S37, suspending the flow between the eNB and the SGW and modifying the bearing between the MME and the SGW;

s38, the eNB sends an RRC connection release message to the UE, wherein the RRC connection release message optionally comprises downlink data.

It should be noted that, for small data transmission, the UE completes the transmission of the small data packet without entering the connection state, and such transmission is different from the Mobile Broadband (MBB) service entering the connection state.

In summary, the small data transmission (SMALL DATA transmission, SDT) may include a random access procedure based SDT or may be a PUR based SDT.

SDT is usually transmitted through DRB configured by network equipment, SRB does not support small data transmission, and positioning measurement report needs to be carried in NAS message, and air interface transmission is implemented through SRB, so how to implement transmission of NAS message in RRC inactive state is an urgent problem to be solved.

Fig. 5 is a schematic flowchart of a data transmission method 200 according to an embodiment of the present application. The method 200 may be performed by a terminal device in the communication system shown in fig. 1, and as shown in fig. 5, the method 200 may include at least part of the following:

S220, the terminal equipment in the RRC inactive state sends first information to the network equipment under the condition that data to be transmitted are available and the inactive state data transmission condition is met;

That is, in the case where data is to be transmitted and the data to be transmitted includes the first NAS message, the terminal device may encrypt and perform integrity protection processing on the first NAS message to obtain a target NAS message, and further encapsulate the target NAS message in the first RRC message, and transmit the first RRC message through the first SRB, so that transmission of the NAS message of the terminal device in the RRC inactive state can be achieved.

Optionally, in some embodiments, the first NAS message includes a positioning measurement report.

Optionally, in some embodiments, the data to be transmitted may further include user data (user data).

Optionally, in some embodiments, the first information further includes information for requesting recovery of the RRC connection.

Optionally, in some embodiments, the information for requesting recovery of RRC connection may include at least one of:

Resume ID/I-RNTI；

ResumeMAC-I；

restoration cause (resume cause).

Wherein the Resume ID/I-RNTI is used for the network device to identify the context of the terminal device in the suspended (suspend) state and ResumeMAC-I is used for authentication of the terminal device.

Alternatively, in some embodiments, the information for requesting to restore the RRC connection may be encapsulated in a first RRC message, and in other embodiments, the information for requesting to restore the RRC connection may be encapsulated separately, for example, in a second RRC message, which is not limited by the present application.

Optionally, in some embodiments, the AS layer of the terminal device determines that data is to be transmitted when receiving the first indication information of the NAS layer of the terminal device.

Optionally, in some embodiments, the method 200 may further include:

S210, the AS layer of the terminal equipment determines whether the inactive state data transmission condition is met under the condition that the first indication information is received. For example, if satisfied, the inactive state data transmission is performed, otherwise, the inactive state data transmission is not performed.

Alternatively, the inactive state data transmission condition may include any trigger condition that the terminal device in the RRC inactive state performs data transmission, for example, may include the first trigger condition and/or the second trigger condition.

Optionally, the first trigger condition includes at least one of:

the timing advance TA of the terminal device is valid;

The terminal equipment is configured with a down-link counter NCC;

The preconfigured uplink resource PUR of the terminal equipment is effective;

there is a need for RRC connection establishment or recovery, such as uplink data arrival.

The TA is determined in a valid manner by referring to the related description.

In some embodiments, the terminal device may select to perform inactive state data transmission based on the preconfigured uplink resource when the first trigger condition is satisfied. I.e. the terminal device may perform a random access based SDT in case the first trigger condition is fulfilled.

Optionally, in some embodiments, the first trigger condition may further include that the terminal device supports PUR-based small data transmission, the network device supports PUR-based small data transmission, and the application is not limited thereto.

Optionally, the second triggering condition includes: the data volume of the uplink data is smaller than the maximum data volume allowed to be transmitted configured by the network equipment.

Alternatively, the maximum data amount may be a maximum Transport Block (TB) size (size) configured by the network device through a system information block (System Information Block, SIB), such as SIB 2.

In some embodiments, the terminal device may select to perform inactive state data transmission based on the preconfigured uplink resource when the second trigger condition is satisfied. I.e. the terminal device may execute the PUR-based SDT in case the second trigger condition is fulfilled.

It should be understood that the above inactive state data transmission conditions are merely examples, and the present application is not limited thereto.

Optionally, in some embodiments of the present application, the NAS layer of the terminal device may perform encryption and integrity protection processing on the first NAS message to be transmitted, to obtain the target NAS message.

Further, the NAS layer of the terminal device submits the target NAS message to an AS layer, i.e. an RRC layer, of the terminal device. And the AS layer of the terminal equipment generates a first RRC message according to the target NAS message, and further transmits the first RRC message through the first SRB.

Optionally, in other embodiments of the present application, the NAS layer of the terminal device may perform encryption and integrity protection processing on the first NAS message to be transmitted, to obtain the target NAS message.

Further, the NAS layer of the terminal device submits the target NAS message to an AS layer, i.e. an RRC layer, of the terminal device. And the AS layer of the terminal equipment encrypts and protects the RRC message bearing the target NAS message, generates a first RRC message and further transmits the first RRC message through the first SRB.

The transmission manner of the first information is described below in conjunction with a specific implementation of the first SRB.

Example 1: the first SRB is SRB0.

In this embodiment 1, the NAS layer of the terminal device may encrypt and integrity protect the first NAS message to obtain the target NAS message.

Optionally, in some embodiments, the AS layer of the terminal device generates the first RRC message according to the target NAS message and information that the terminal device uses to request to restore an RRC connection.

For example, the AS layer of the terminal device may encapsulate the target NAS message and the information for requesting to restore the RRC connection in a first RRC message.

In this embodiment 1, the first RRC message transmitted through SRB0 may not undergo encryption and integrity protection processing by the AS layer of the terminal device.

Example 2: the first SRB includes SRB1 and/or SRB2.

In this embodiment 2, the NAS layer of the terminal device may encrypt and integrity protect the first NAS message to obtain the target NAS message.

Further, the AS layer of the terminal device may encrypt and perform integrity protection processing on the RRC message carrying the target NAS message, to generate the first RRC message. I.e. the first RRC message transmitted over SRB1 and/or SRB2 is handled through encryption and integrity protection of the NAS layer and AS layer of the terminal device.

Optionally, in this embodiment 2, the method 200 further includes:

The terminal device activates the AS layer security key and recovers SRB1 and/or SRB2.

Optionally, in some embodiments, the AS layer of the terminal device may further generate a second RRC message according to information for requesting recovery of the RRC connection. For example, the AS layer of the terminal device may encapsulate the information for requesting restoration of the RRC connection in a second RRC message.

Alternatively, the second RRC message may be transmitted through SRB 0. I.e. the second RRC message does not go through encryption and integrity protection processing of the AS layer of the terminal device.

In combination with the foregoing embodiment 1 and embodiment 2, the first NAS message may be transmitted through SRB0, where the first NAS message is processed through encryption and integrity protection of a NAS layer of the terminal device. Or the first NAS message may be transmitted through SRB1 and/or SRB2, where the first NAS message is processed through NAS layer of the terminal device and encryption and integrity protection of the AS layer.

Optionally, in some embodiments, if the data to be transmitted further includes user data, the AS layer of the terminal device may further encrypt and integrity protect the user data to obtain target user data. The target user data may be transmitted through the DRB.

Optionally, in some embodiments, if the data to be transmitted further includes user data, the method 200 further includes: and the terminal equipment recovers the DRB.

Optionally, in some embodiments, the first information may further include other data, for example, MAC CE and/or Padding bits (Padding bits), etc.

In some embodiments, multiplexing of the first RRC message, the second RRC message, the target user data, the MAC CE, and the fill bits may follow a logical channel priority (Logical Channel Prioritization, LCP) flow.

Optionally, in some embodiments, as shown in fig. 5, the method 200 further includes:

S230, the terminal device receives second information sent by the network device, where the second information includes at least one of the following:

a third RRC message, wherein the third RRC message is transmitted through a second SRB;

Subsequent downlink scheduling;

And subsequent uplink scheduling.

It should be noted that, here, the subsequent uplink schedule and the subsequent downlink schedule may be relative to the first SDT, for example, the subsequent uplink schedule may refer to an uplink schedule after the first SDT, and the subsequent downlink schedule may refer to a downlink schedule after the first SDT.

Optionally, in some embodiments, the third RRC message includes at least one of:

configuration information for releasing the RRC connection;

configuration information for recovering the RRC connection;

configuration information for establishing an RRC connection;

Downlink NAS messages.

That is, the downlink NAS message to be transmitted by the network device may be multiplexed with configuration information for releasing/recovering/establishing the RRC connection and transmitted to the terminal device. Or the downlink NAS message to be sent by the network device may also not be multiplexed with the configuration information for releasing/recovering/establishing the RRC connection, i.e. not transmitted through the second SRB.

Optionally, the subsequent downlink schedule includes an RRC message carrying a NAS message; and/or

The subsequent uplink schedule includes an RRC message carrying a NAS message.

That is, the downlink NAS message to be sent by the network device may be carried in an RRC message, and further include transmission in a subsequent downlink schedule and/or a subsequent uplink schedule.

Optionally, in some embodiments, the second SRB comprises SRB1.

Optionally, in some embodiments, the uplink resource used for transmitting the first information is an uplink resource used for random access, or an uplink resource is preconfigured, or a subsequent uplink scheduling resource.

As an example, if the first information is carried on SRB0, it needs to be sent during the first small uplink data transmission, because the RRC message carried on SRB0 needs to include information for requesting to recover the RRC connection in addition to the NAS message, in which case the first information may be sent through resources for random access, such as resources for transmission MSGA or Msg3, or may also be sent through preconfigured uplink resources, such as CG resources.

As another example, if carried on SRB1/SRB2, the first information may be sent during the first small uplink data transmission, or may also be sent after the first small uplink data transmission, through uplink resources further scheduled by the network device, i.e. through subsequent uplink scheduling resources.

In summary, the first information may be sent based on small data transmission of random access, or may also be sent based on small data transmission of PUR, or may also be sent in uplink scheduling after small data transmission, and the present application does not limit the sending timing of the first information.

Hereinafter, a specific flow of a data transmission method according to an embodiment of the present application will be described with reference to fig. 6 and 7.

In the example of fig. 6, the NAS message is transmitted over SRB 0. As shown in fig. 6, the method may include at least some of the following steps:

S201, when data to be transmitted is needed, the NAS layer of the terminal equipment sends first indication information to the AS layer of the terminal equipment, and the first indication information indicates the data to be transmitted. Wherein the data to be transmitted comprises a first NAS message.

S202, the AS layer of the terminal equipment determines whether the inactive state data transmission condition is satisfied, and executes inactive state data transmission under the condition that the inactive state data transmission condition is satisfied.

S203, the NAS layer of the terminal equipment encrypts and protects the integrity of the first NAS message to obtain a target NAS message.

S204, the NAS layer of the terminal equipment submits the target NAS message to the AS layer of the terminal equipment.

S205, the AS layer of the terminal device encapsulates the target NAS message and the following information in the first RRC message:

Resume ID；

ResumeMAC-I；

resume cause。

Optionally, if the data to be transmitted further includes user data, the terminal device may further activate an AS layer security key and recover a DRB for transmitting the user data.

Optionally, the AS layer of the terminal device may further perform encryption and integrity protection processing on the user data to obtain target user data.

S206, the AS layer of the terminal device sends the first information to the network device.

Wherein the first information includes a first RRC message, and the first RRC message is transmitted through SRB 0. Wherein the first RRC message is not subjected to AS layer encryption and integrity protection processing.

If the data to be transmitted further includes user data, the first information may further include target user data, and the target user data is transmitted through DRB.

Optionally, the first information may further include MAC CEs and/or padding bits, etc.

In some embodiments, multiplexing of the first RRC message, the target user data, the MAC CE, and the fill bits may follow LCP flow.

Further, the AS layer of the terminal device may receive the second information of the AS layer of the network device, and the detailed description refers to the related description above, which is not repeated here.

In the example of fig. 7, the NAS message is transmitted over SRB1 and/or SRB 2. As shown in fig. 7, the method may include at least some of the following steps:

S301, when data to be transmitted is needed, the NAS layer of the terminal equipment sends first indication information to the AS layer of the terminal equipment, and the first indication information indicates the data to be transmitted. Wherein the data to be transmitted comprises a first NAS message.

S302, the AS layer of the terminal equipment determines whether the inactive state data transmission condition is satisfied, and executes inactive state data transmission under the condition that the inactive state data transmission condition is satisfied.

S303, the NAS layer of the terminal equipment encrypts and protects the integrity of the first NAS message to obtain a target NAS message.

S304, the NAS layer of the terminal equipment submits the target NAS message to the AS layer of the terminal equipment.

S305, the AS layer of the terminal device encapsulates the target NAS message in the RRC message.

In this S305, the terminal device may also activate an AS layer security key, recovering SRB1 and/or SRB2.

And the AS layer of the terminal equipment encrypts and protects the RRC message bearing the target NAS message to obtain a first RRC message.

Optionally, the AS layer of the terminal device may further encapsulate the following information in a second RRC message:

Resume ID；

ResumeMAC-I；

resume cause。

Alternatively, the second RRC message may be transmitted through SRB 0. Wherein the second RRC message is not subjected to AS layer encryption and integrity protection processing.

Optionally, if the data to be transmitted further includes user data, the terminal device may further recover DRB for transmitting the user data.

Optionally, the AS layer of the terminal device may further encrypt and perform integrity protection processing on the user data to obtain target user data.

S306, the AS layer of the terminal device sends first information to the network device.

Wherein the first information includes a first RRC message, and the first RRC message is transmitted through SRB1 and/or SRB 2. The first RRC message is encrypted and integrity protected by the NAS layer and the AS layer of the terminal equipment.

If the data to be transmitted further includes user data, the first information may further include target user data, and the target user data is transmitted through DRB and is encrypted and integrity protected by the AS layer of the terminal device.

Optionally, the first information may further include a second RRC message transmitted through SRB 0.

In summary, when there is a NAS message to be transmitted and the inactive state data transmission condition is satisfied, the terminal device may perform encryption and integrity protection processing on the NAS message to be transmitted (for example, the NAS layer of the terminal device may perform encryption and integrity protection processing on the NAS message, or both the NAS layer and the AS layer of the terminal device may perform encryption and integrity protection processing on the NAS message), and further, the NAS message after encryption and integrity protection processing may be transmitted through the SRB, so that transmission of the NAS message of the terminal device in the inactive state can be implemented.

The method embodiments of the present application are described in detail above with reference to fig. 5 to 7, and the apparatus embodiments of the present application are described in detail below with reference to fig. 8 to 12, it being understood that the apparatus embodiments and the method embodiments correspond to each other, and similar descriptions may refer to the method embodiments.

Fig. 8 shows a schematic block diagram of a terminal device 400 according to an embodiment of the application. As shown in fig. 8, the terminal apparatus 400 includes:

a communication unit 410 that transmits first information to the network device in a case where data is to be transmitted and an inactive state data transmission condition is satisfied;

The terminal equipment is in a Radio Resource Control (RRC) inactive state, the first information comprises a first RRC message, the first RRC message is transmitted through a first Signaling Radio Bearer (SRB), the first RRC message comprises a target non-access stratum (NAS) message, the target NAS message is obtained by encrypting and integrity processing of the first NAS message through the terminal equipment, and the data to be transmitted comprises the first NAS message.

Optionally, in some embodiments, the first SRB is SRB0.

Optionally, in some embodiments, the terminal device 400 further includes:

The processing unit is used for encrypting and protecting the integrity of the first NAS message at the NAS layer to obtain the target NAS message;

Delivering the target NAS message to an AS layer of the terminal equipment at an NAS layer;

Generating, at an AS layer, the first RRC message according to the target NAS message and at least one of: and recovering the identifier, recovering the media access control identifier and recovering the reason.

Optionally, in some embodiments, the first SRB comprises SRB1 and/or SRB2.

Optionally, in some embodiments, the terminal device 400 further includes:

and encrypting and protecting the RRC message bearing the target NAS message at an AS layer, and generating the first RRC message.

Optionally, in some embodiments, the processing unit is further configured to:

generating, at the AS layer, a second RRC message according to at least one of:

And recovering the identifier, recovering the media access control identifier and recovering the reason.

Optionally, in some embodiments, the first information further includes the second RRC message, wherein the second RRC message is transmitted through SRB 0.

Optionally, in some embodiments, the terminal device 400 further includes:

And the processing unit is used for activating the AS layer security key and recovering the first SRB.

Optionally, in some embodiments, if the data to be transmitted further includes user data, the terminal device 400 further includes: and the processing unit is used for encrypting and protecting the integrity of the user data at the AS layer to obtain target user data.

Optionally, in some embodiments, the first information further includes: and the target user data is transmitted through a Data Radio Bearer (DRB).

Optionally, in some embodiments, the first information further includes:

the transmission medium access control MAC control element CE and/or padding bits.

Optionally, in some embodiments, the communication unit 410 is further configured to: receiving second information sent by the network device, wherein the second information comprises at least one of the following:

Subsequent downlink scheduling;

And subsequent uplink scheduling.

configuration information for releasing the RRC connection;

configuration information for recovering the RRC connection;

configuration information for establishing an RRC connection;

Downlink NAS messages.

Optionally, in some embodiments, the subsequent downlink schedule includes an RRC message carrying a NAS message; and/or, the subsequent uplink schedule includes an RRC message carrying the NAS message.

Optionally, in some embodiments, the second SRB comprises SRB1.

Optionally, in some embodiments, the terminal device 400 further includes: the processing unit is used for sending first indication information to an AS layer of the terminal equipment at the NAS layer, wherein the first indication information is used for indicating data transmission to be performed;

It is determined at the AS layer whether the inactive state data transfer condition is satisfied.

Alternatively, in some embodiments, the communication unit may be a communication interface or transceiver, or an input/output interface of a communication chip or a system on a chip. The processing unit may be one or more processors.

It should be understood that the terminal device 400 according to the embodiment of the present application may correspond to the terminal device in the embodiment of the method of the present application, and the foregoing and other operations and/or functions of each unit in the terminal device 400 are respectively for implementing the corresponding flows of the terminal device in the embodiment of the method shown in fig. 5 to 7, which are not repeated herein for brevity.

Fig. 9 is a schematic block diagram of a network device according to an embodiment of the present application. The network device 500 of fig. 9 includes:

a communication unit, configured to receive first information sent by a radio resource control RRC inactive state terminal device under a data to be transmitted and an inactive state data transmission condition is satisfied;

Optionally, in some embodiments, the first SRB is SRB0.

Optionally, in some embodiments, the first RRC message further includes at least one of: and recovering the identifier, recovering the media access control identifier and recovering the reason.

Optionally, in some embodiments, the first SRB comprises SRB1 and/or SRB2.

Optionally, in some embodiments, the first information further includes a second RRC message, wherein the second RRC message is transmitted through SRB0, the second RRC message including at least one of: and recovering the identifier, recovering the media access control identifier and recovering the reason.

Optionally, in some embodiments, the data to be transmitted further includes user data, the first information further includes the target user data, and the target user data transmitted by the target user data through a data radio bearer DRB is obtained by encrypting and integrity protecting the user data through an AS layer of the terminal device.

Optionally, in some embodiments, the first information further includes: the medium access control MAC control element CE and/or padding bits.

Optionally, in some embodiments, the communication unit 510 is further configured to:

Transmitting second information to the terminal device, wherein the second information comprises at least one of the following: a third RRC message, wherein the third RRC message is transmitted through a second SRB;

Subsequent downlink scheduling;

And subsequent uplink scheduling.

configuration information for releasing the RRC connection;

configuration information for recovering the RRC connection;

configuration information for establishing an RRC connection;

Downlink NAS messages.

Optionally, in some embodiments, the second SRB comprises SRB1.

It should be understood that the network device 500 according to the embodiment of the present application may correspond to the network device in the embodiment of the method of the present application, and the foregoing and other operations and/or functions of each unit in the network device 500 are respectively for implementing the corresponding flows of the network device in the embodiment of the method shown in fig. 5 to fig. 7, and are not repeated herein for brevity.

Fig. 10 is a schematic block diagram of a communication device 600 according to an embodiment of the present application. The communication device 600 shown in fig. 10 comprises a processor 610, from which the processor 610 may call and run a computer program to implement the method in an embodiment of the application.

Optionally, as shown in fig. 10, the communication device 600 may further comprise a memory 620. Wherein the processor 610 may call and run a computer program from the memory 620 to implement the method in an embodiment of the application.

The memory 620 may be a separate device from the processor 610 or may be integrated into the processor 610.

Optionally, as shown in fig. 10, the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, and in particular, may send information or data to other devices, or receive information or data sent by other devices.

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

Optionally, the communication device 600 may be specifically a network device according to the embodiment of the present application, and the communication device 600 may implement a corresponding flow implemented by the network device in each method according to the embodiment of the present application, which is not described herein for brevity.

Optionally, the communication device 600 may be specifically a mobile terminal/terminal device according to an embodiment of the present application, and the communication device 600 may implement corresponding processes implemented by the mobile terminal/terminal device in each method according to the embodiment of the present application, which are not described herein for brevity.

Fig. 11 is a schematic structural view of a chip of an embodiment of the present application. The chip 700 shown in fig. 11 includes a processor 710, and the processor 710 may 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. 11, chip 700 may also include memory 720. Wherein the processor 710 may call and run a computer program from the memory 720 to implement the method in an embodiment of the application.

Wherein the memory 720 may be a separate device from the processor 710 or may be integrated into the processor 710.

Optionally, the chip 700 may also include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and in particular, may obtain information or data sent by other devices or chips.

Optionally, the chip 700 may further include an output interface 740. The processor 710 may control the output interface 740 to communicate with other devices or chips, and in particular, may output information or data to other devices or chips.

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

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

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

Fig. 12 is a schematic block diagram of a communication system 900 provided by an embodiment of the present application. As shown in fig. 12, the communication system 900 includes a terminal device 910 and a network device 920.

The terminal device 910 may be configured to implement the corresponding functions implemented by the terminal device in the above method, and the network device 920 may be configured to implement the corresponding functions implemented by the network device in the above method, which are not described herein for brevity.

It should be appreciated that the processor of an embodiment of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The Processor may be a general purpose Processor, a digital signal Processor (DIGITAL SIGNAL Processor, DSP), an Application SPECIFIC INTEGRATED Circuit (ASIC), an off-the-shelf programmable gate array (Field Programmable GATE ARRAY, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in embodiments of the application may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available, such as static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (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 link dynamic random access memory (SYNCHLINK DRAM, SLDRAM), and Direct memory bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be appreciated that the above memory is exemplary and not limiting, and for example, the memory in the embodiments of the present application may be static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (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), direct Rambus RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

The embodiment of the application also provides a computer readable storage medium for storing a computer program.

Optionally, the computer readable storage medium may be applied to a network device in the embodiment of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the computer readable storage medium may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the computer program causes a computer to execute a corresponding procedure implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, which is not described herein for brevity.

The embodiment of the application also provides a computer program product comprising computer program instructions.

Optionally, the computer program product may be applied to a network device in the embodiment of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the network device in each method in the embodiment of the present application, which are not described herein for brevity.

Optionally, the computer program product may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, which are not described herein for brevity.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to a network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the computer program may be applied to a mobile terminal/terminal device in the embodiment of the present application, and when the computer program runs on a computer, the computer is caused to execute corresponding processes implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

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

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A data transmission method, comprising:

the method comprises the steps that a terminal device in a Radio Resource Control (RRC) inactive state sends first information to a network device under the condition that data to be transmitted are needed and inactive state data transmission conditions are met;

the first information comprises a first RRC message, the first RRC message is transmitted through a first Signaling Radio Bearer (SRB), the first RRC message comprises a target non-access stratum (NAS) message, the target NAS message is obtained by encrypting and integrity processing the first NAS message by the terminal equipment, and the data to be transmitted comprises the first NAS message;

wherein the first SRB comprises SRB1 and/or SRB2;

the method further comprises the steps of:

The NAS layer of the terminal equipment encrypts and protects the first NAS message to obtain the target NAS message;

the NAS layer of the terminal equipment submits the target NAS message to the AS layer of the terminal equipment;

And the AS layer of the terminal equipment encrypts and protects the RRC message bearing the target NAS message, and generates the first RRC message.

2. The method according to claim 1, wherein the method further comprises:

the AS layer of the terminal device generates a second RRC message according to at least one of the following:

3. The method of claim 2, wherein the first information further comprises the second RRC message, wherein the second RRC message is transmitted over SRB 0.

4. A method according to any one of claims 1-3, characterized in that the method further comprises:

and the terminal equipment activates an AS layer security key and recovers the first SRB.

5. A method according to any of claims 1-3, wherein if the data to be transmitted further comprises user data, the method further comprises:

And the AS layer of the terminal equipment encrypts and protects the user data to obtain target user data.

6. The method of claim 5, wherein the first information further comprises: and the target user data is transmitted through a Data Radio Bearer (DRB).

7. A method according to any one of claims 1-3, wherein the first information further comprises:

8. A method according to any one of claims 1-3, characterized in that the method further comprises:

the terminal device receives second information sent by the network device, wherein the second information comprises at least one of the following:

Subsequent downlink scheduling;

And subsequent uplink scheduling.

9. The method of claim 8, wherein the third RRC message includes at least one of:

configuration information for releasing the RRC connection;

configuration information for recovering the RRC connection;

configuration information for establishing an RRC connection;

Downlink NAS messages.

10. The method of claim 8, wherein the subsequent downlink schedule comprises an RRC message carrying a NAS message; and/or

The subsequent uplink schedule includes an RRC message carrying a NAS message.

11. The method of claim 8, wherein the second SRB comprises SRB1.

12. A method according to any of claims 1-3, wherein the first NAS message comprises a positioning measurement report.

13. A method according to any of claims 1-3, characterized in that the uplink resources used for transmitting the first information are uplink resources for random access, or pre-configured uplink resources, or subsequent uplink scheduling resources.

14. A method according to any one of claims 1-3, characterized in that the method further comprises:

The NAS layer of the terminal equipment sends first indication information to the AS layer of the terminal equipment, wherein the first indication information is used for indicating data transmission to be performed;

the AS layer of the terminal device determines whether an inactive state data transmission condition is satisfied.

15. A terminal device, comprising:

a communication unit that transmits first information to the network device in a case where data to be transmitted is to be transmitted and an inactive state data transmission condition is satisfied;

The terminal equipment is in a Radio Resource Control (RRC) inactive state, the first information comprises a first RRC message, the first RRC message is transmitted through a first Signaling Radio Bearer (SRB), the first RRC message comprises a target non-access stratum (NAS) message, the target NAS message is obtained by encrypting and integrity processing the first NAS message by the terminal equipment, and the data to be transmitted comprises the first NAS message;

Wherein the first SRB comprises SRB1 and/or SRB2; wherein, the terminal equipment still includes:

16. The terminal device of claim 15, wherein the processing unit is further configured to:

generating, at the AS layer, a second RRC message according to at least one of:

17. The terminal device of claim 16, wherein the first information further comprises the second RRC message, wherein the second RRC message is transmitted over SRB 0.

18. The terminal device according to any of the claims 15-17, characterized in that the terminal device further comprises:

19. The terminal device according to any of the claims 15-17, characterized in that if the data to be transmitted further comprises user data, the terminal device further comprises:

and the processing unit is used for encrypting and protecting the integrity of the user data at the AS layer to obtain target user data.

20. The terminal device of claim 19, wherein the first information further comprises: and the target user data is transmitted through a Data Radio Bearer (DRB).

21. The terminal device according to any of the claims 15-17, wherein the first information further comprises:

22. The terminal device according to any of the claims 15-17, wherein the communication unit is further adapted to: receiving second information sent by the network device, wherein the second information comprises at least one of the following:

Subsequent downlink scheduling;

And subsequent uplink scheduling.

23. The terminal device of claim 22, wherein the third RRC message includes at least one of:

configuration information for releasing the RRC connection;

configuration information for recovering the RRC connection;

configuration information for establishing an RRC connection;

Downlink NAS messages.

24. The terminal device of claim 23, wherein the subsequent downlink schedule comprises an RRC message carrying a NAS message; and/or

The subsequent uplink schedule includes an RRC message carrying a NAS message.

25. The terminal device of claim 22, wherein the second SRB comprises SRB1.

26. The terminal device according to any of the claims 15-17, wherein the first NAS message comprises a positioning measurement report.

27. The terminal device according to any of the claims 15-17, characterized in that the uplink resources used for transmitting the first information are uplink resources for random access, or pre-configured uplink resources, or subsequent uplink scheduling resources.

28. The terminal device according to any of the claims 15-17, characterized in that the terminal device further comprises: the processing unit is used for sending first indication information to an AS layer of the terminal equipment at the NAS layer, wherein the first indication information is used for indicating data transmission to be performed;

29. A terminal device, comprising: a processor and a memory for storing a computer program, the processor being for invoking and running the computer program stored in the memory, performing the method of any of claims 1 to 14.

30. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any one of claims 1 to 14.

31. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 14.

32. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 14.