Data transmission method, terminal device and network device
By encrypting and integrity protection of NAS messages on the terminal device and wirelessly carrying SRB transmission through signaling, the problem of NAS messages transmission in the RRC is solved, and the security and complete data transmission are achieved.
Patent Information
- Application Number
- CN202080105901.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-12-21
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2040-12-21
AI Technical Summary
The prior art is difficult to realize NAS message transmission in the RRC inactive state, especially in small data transmission scenarios, signaling wireless bearers do not support the transmission of NAS messages, resulting in transmission difficulties.
By encrypting and integrity protection processing of the NAS messages to be transmitted on the terminal device, the target NAS messages are generated and encapsulated in the RRC message, and wirelessly carrying SRB transmission is realized through signaling, NAS messages transmission in RRC inactivated state is realized.
NAS message transmission in RRC inactive state is realized, solving the problem of transmission difficulties and ensuring the security and integrity of the data.
Smart Images

Figure CN116326179B_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present application relate to the field of communications, and specifically to a data transmission method, a terminal device, and a network device. Background Art
[0002] Small data transmission (SDT) is a data transmission mode of a terminal device in an RRC inactive state (RRC_INACTIVE). SDT may include SDT based on a random access process, or SDT based on a preconfigured uplink resource (PUR).
[0003] SDT is usually transmitted through Data Radio Bearers (DRB) configured by network equipment. Signaling Radio Bearers (SRB) do not support small data transmission, while positioning measurement reports need to be carried in Non-Access Stratum (NAS) messages and transmitted over the air interface through SRB. Therefore, how to realize the transmission of NAS messages in the RRC non-activated state is an urgent problem to be solved. Summary of the invention
[0004] The present application provides a data transmission method, a terminal device and a network device, which can realize the transmission of NAS messages in the RRC inactive state.
[0005] In a first aspect, a data transmission method is provided, comprising: a terminal device in a radio resource control (RRC) inactive state sends first information to a network device when there is data to be transmitted and an inactive state data transmission condition is met; wherein the first information includes a first RRC message, the first RRC message is transmitted via a first signaling radio bearer (SRB), the first RRC message includes a target non-access layer (NAS) message, the target NAS message is obtained by the terminal device by encrypting and integrity processing the first NAS message, and the data to be transmitted includes the first NAS message.
[0006] In a second aspect, a data transmission method is provided, including: a network device receiving first information sent by a terminal device in a radio resource control RRC inactive state when data is to be transmitted and a condition for data transmission in an inactive state is met;
[0007] Among them, 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 layer NAS message, the target NAS message is obtained by the terminal device encrypting and integrity processing the first NAS message, and the data to be transmitted includes the first NAS message.
[0008] In a third aspect, a terminal device is provided for executing the method in the first aspect or its various implementations.
[0009] Specifically, the terminal device includes a functional module for executing the method in the above-mentioned first aspect or its various implementation modes.
[0010] In a fourth aspect, a network device is provided for executing the method in the second aspect or its respective implementation manners.
[0011] Specifically, the network device includes a functional module for executing the method in the above-mentioned second aspect or its various implementation modes.
[0012] In a fifth aspect, a terminal device is provided, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the first aspect or its implementation manners.
[0013] In a sixth aspect, a network device is provided, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the second aspect or its implementation manners.
[0014] In a seventh aspect, a chip is provided for implementing the method in any one of the first to second aspects or in each of their implementations.
[0015] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the device executes a method as described in any one of the first to second aspects or their respective implementations.
[0016] In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, wherein the computer program enables a computer to execute the method of any one of the first to second aspects or any of their implementations.
[0017] In a ninth aspect, a computer program product is provided, comprising computer program instructions, wherein the computer program instructions enable a computer to execute the method in any one of the first to second aspects above or in each of their implementations.
[0018] In a tenth aspect, a computer program is provided, which, when executed on a computer, enables the computer to execute the method in any one of the first to second aspects or in each of their implementations.
[0019] Through the above technical solution, when there is data to be transmitted and the inactive data transmission conditions are met, the terminal device can encrypt and integrity protect the first NAS message in the data to be transmitted to obtain a target NAS message, further encapsulate the target NAS message in a first RRC message, and transmit the first RRC message through the first SRB, thereby realizing the transmission of NAS messages of terminal devices in the RRC inactive state. BRIEF DESCRIPTION OF THE DRAWINGS
[0020] Figure 1 It is a schematic diagram of an application scenario provided by an embodiment of the present application.
[0021] Figure 2 It is a schematic flow chart of UE requesting PUR.
[0022] Figure 3 It is a schematic diagram of data transmission using PUR.
[0023] Figure 4 It is a schematic diagram of data transmission using random access resources.
[0024] Figure 5 It is a schematic diagram of a data transmission method provided in an embodiment of the present application.
[0025] Figure 6 It is a schematic diagram of another data transmission method provided in an embodiment of the present application.
[0026] Figure 7 It is a schematic diagram of another data transmission method provided in an embodiment of the present application.
[0027] Figure 8 It is a schematic block diagram of a terminal device provided in an embodiment of the present application.
[0028] Fig. 9 It is a schematic block diagram of another terminal device provided in an embodiment of the present application.
[0029] Fig.10 It is a schematic block diagram of a communication device provided in another embodiment of the present application.
[0030] Fig.11 It is a schematic block diagram of a chip provided in an embodiment of the present application.
[0031] Fig.12 It is a schematic block diagram of a communication system provided in an embodiment of the present application. DETAILED DESCRIPTION
[0032] The following will describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. For the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0033] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity) system. Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.
[0034] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device to device (Device to Device, D2D) communication, machine to machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), vehicle to vehicle (V2V) communication, or vehicle to everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.
[0035] Optionally, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) networking scenario.
[0036] Optionally, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, wherein the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, wherein the authorized spectrum can also be considered as an unshared spectrum.
[0037] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
[0038] The terminal device can be a station (STATION, ST) in a WLAN, 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, 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 (PLMN) network, etc.
[0039] In the embodiments of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (for example, on airplanes, balloons and satellites, etc.).
[0040] In the embodiment of the present application, the terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.
[0041] As an example but not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and fully or partially independent of smartphones, such as smart watches or smart glasses, as well as devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.
[0042] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (EvolutionalNode B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network, or a network device in a future evolved PLMN network, or a network device in an NTN network, etc.
[0043] As an example but not limitation, in an embodiment of the present application, the network device may have a mobile characteristic, for example, the network device may be a mobile device. Optionally, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water.
[0044] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station), and the cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.
[0045] For example, the communication system 100 used in the embodiment of the present application is as follows: Figure 1 The communication system 100 may include a network device 110, which may be a device that communicates with a terminal device 120 (or a communication terminal or terminal). The network device 110 may provide communication coverage for a specific geographical area and may communicate with terminal devices located in the coverage area.
[0046] Figure 1One network device and two terminal devices are shown exemplarily. Optionally, the communication system 100 may include multiple network devices and each network device may include another number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.
[0047] Optionally, the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiments of the present application.
[0048] It should be understood that the device with communication function in the network / system in the embodiment of the present application can be referred to as a communication device. Figure 1 Taking the communication system 100 shown as an example, the communication equipment may include a network device 110 and a terminal device 120 with communication functions. The network device 110 and the terminal device 120 may be the specific devices described above and will not be repeated here. The communication equipment may also include other devices in the communication system 100, such as a network controller, a mobile management entity and other network entities, which is not limited in the embodiments of the present application.
[0049] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.
[0050] It should be understood that the "indication" mentioned in the embodiments of the present application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B.
[0051] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between two items, or an association relationship between the two items, or a relationship between indication and being indicated, configuration and being configured, and the like.
[0052] In the embodiments of the present application, "pre-definition" can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including a terminal device and a network device), and the present application does not limit the specific implementation method. For example, pre-definition can refer to what is defined in the protocol.
[0053] In the embodiments of the present application, the "protocol" may refer to a standard protocol in the communication field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.
[0054] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The following related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all belong to the protection scope of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.
[0055] It should be understood that in the embodiment of the present application, NR can also be deployed independently. In order to reduce air interface signaling and quickly restore wireless connections and data services in the 5G network environment, a new radio resource control (RRC) state is defined, namely, the RRC_INACTIVE (inactive) state. This state is different from the RRC_IDLE (idle) and RRC_CONNECTED (connected) states.
[0056] In the RRC_IDLE state: mobility is based on the cell selection reselection of the terminal device, paging is initiated by the core network (CN), and the paging area is configured by the CN. There is no terminal device access stratum (AS) context on the base station side, and there is no RRC connection.
[0057] In the RRC_CONNECTED state: an RRC connection exists, and a terminal device AS context exists between the base station and the terminal device. The network device knows the location of the terminal device at the specific cell level. Mobility is mobility controlled by the network device. Unicast data can be transmitted between the terminal device and the base station.
[0058] RRC_INACTIVE: Mobility is based on cell selection reselection of the terminal device. There is a connection between CN and NR. The AS context of the terminal device exists on a certain base station. Paging is triggered by the Radio Access Network (RAN). The RAN-based paging area is managed by the RAN. The network equipment knows the location of the terminal device based on the RAN paging area level.
[0059] It should be noted that in the embodiments of the present application, the non-activated state may also be referred to as the deactivated state, and the present application does not limit this.
[0060] The network device can control the state transition of the terminal device. For example, a terminal device in the RRC_CONNECTED state can enter the RRC_IDLE state by releasing the RRC connection; a terminal device in the RRC_IDLE state can enter the RRC_CONNECTED state by establishing an RRC connection; a UE in the RRC_CONNECTED state can enter the RRC_INACTIVE state by suspending (Release with Suspend) the RRC connection; a UE in the RRC_INACTIVE state can enter the RRC_CONNECTED state by resuming (Resume) the RRC connection, and can also enter the RRC_IDLE state by releasing the RRC connection.
[0061] In LTE Release 16, a method of using preconfigured uplink resources (PUR) for data transmission in the IDLE state was introduced for the Narrow Band Internet of Things (NB-IoT) and enhanced machine type of communication (eMTC) scenarios. Figure 2 Specifically, if the cell where the UE is located supports uplink transmission based on PUR and the UE is in a connected state, then 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), to request the network device to configure PUR.
[0062] Optionally, the PURConfigurationRequest may include at least one of the following: requested PUR period, TBS, number of PURs. The network device sends the PUR configuration to the UE via a Radio Resource Control (RRC) message. For example, the RRC message may be an RRC Connection Release (RRCConnectinRelease) message. The network device configures the PUR for the UE by including a PUR configuration (PUR-Config) field in the RRC message, and releases the UE to the IDLE state. Optionally, the PUR configuration may be determined by the network device, or may be determined based on at least one of the UE's request, UE registration information, and local policy.
[0063] It should be noted that the PUR is only valid in the UE's serving cell or the cell where it is currently residing. When the UE detects a cell change and initiates random access in a new cell, the UE needs to release the PUR configured in the original cell.
[0064] Before a UE in the IDLE state wants to use PUR for data transmission, the following prerequisites must be met:
[0065] 1. To be effective, TA must meet the following two conditions at the same time:
[0066] a. Timing Advance (TA) timer: After receiving the instruction from the higher layer, the Media Access Control (MAC) layer starts the TA timer. When judging the validity of the TA, the higher layer can confirm with the MAC layer whether the TA timer is in operation. When the TA timer times out, the MAC layer needs to feedback to the higher layer. When the TA timer is running, the TA is considered valid, otherwise the TA is invalid.
[0067] b. Reference Signal Receiving Power (RSRP) change: When the change (increase or decrease) of RSRP is greater than the set threshold, that is, the RSRP change is too large, in this case, the TA is considered to be invalid, otherwise the TA is considered to be valid.
[0068] 2. The UE is configured with a Next Hop Chaining Count (NCC), which is used to derive new keys.
[0069] Optionally, the NCC may be configured through an RRC message, for example, the RRC message may be an RRCConnectionRelease message.
[0070] 3. Valid PUR: The cell where the UE resides supports PUR and is configured with PUR.
[0071] 4. There is a need to establish or restore an RRC connection, such as uplink data arriving;
[0072] Combination Figure 3 , describing the process of a UE in IDLE state using PUR for data transmission.
[0073] When the aforementioned prerequisites are met, the UE in the idle state can use the PUR for data transmission.
[0074] S41, the UE sends an RRC message, such as an RRC connection resumption request (RRCConnectionResumeRequest) message, to a network device, such as an eNB / ng-eNB.
[0075] Optionally, the RRC message may include: a resume ID (Resume ID) or an information RNTI (InformationRNTI, I-RNTI), an establishment cause (establishment cause), and shortResumeMAC-I / ResumeMAC-I.
[0076] Among them, Resume ID / I-RNTI is used by the network device to identify the context of the UE in the suspended state, and shortResumeMAC-I / ResumeMAC-I is used for the identity authentication of the UE.
[0077] Furthermore, the UE resumes all signaling radio bearers (SRB) and data radio bearers (DRB). It uses the NCC contained in the RRCConnectionRelease message of the last connection to derive new keys, encrypts and transmits the user data to be sent on the dedicated transmission channel (DTCH), and multiplexes it with the RRCConnectionResumeRequest on the common control channel (CCCH).
[0078] S42, data transmission is performed between the access network device and the core network device.
[0079] The network equipment may include access network equipment, such as eNB, ng-eNB and core network equipment, such as mobility management entity (MME) and serving gateway (S-GW).
[0080] After the access network device delivers the user data to the core network device, the eNB / ng-eNB further keeps the UE in the IDLE state through the RRCConnectionRelease message. The RRCConnectionRelease message may include the following information, for example:
[0081] a) The release cause (releaseCause) is set to RRC-Suspend;
[0082] b) resume ID / I-RNTI;
[0083] c) NCC;
[0084] d)DRB continuous reliable header compression (Robust Header Compression, ROHC), namely drb-ContinueROHC.
[0085] If there is downlink data to be sent on the network side, it is encrypted and transmitted through DTCH and multiplexed with the RRCConnectionRelease message on DCCH.
[0086] In the LTE system, early data transmission (EDT) is introduced. During the EDT process, the terminal device may always remain in an idle state, a suspended state, or an inactive state to complete the transmission of uplink and / or downlink small data packets. For example, Figure 4 As shown, the user plane data transmission solution can be specifically implemented by the process described in the following S31 to S38.
[0087] S31. The UE sends an RRC connection resumption request (Resume Request) to the eNB, and the RRC connection resumption request includes a resumption ID (Resume ID) or information RNTI (Information RNTI, I-RNTI), an establishment cause (establishmentcause), and shortResumeMAC-I. It also includes the uplink data sent by the UE (i.e., small data transmission);
[0088] S32. The eNB sends a UE CONTEXT RESUME REQUEST to the Mobility Management Entity (MME);
[0089] S33. Modify the bearer between MME and Serving Gateway (SGW);
[0090] S34.MME sends a UE CONTEXT RESUME RESPONSE to the eNB;
[0091] S35. The eNB sends the uplink data sent by the UE to the SGW (ie, small data transmission);
[0092] S36. The SGW receives the downlink data sent by the eNB (optionally);
[0093] S37 suspends the process between eNB and SGW, and modifies the bearer between MME and SGW;
[0094] S38. The eNB sends an RRC connection release message to the UE. Optionally, the RRC connection release message includes downlink data.
[0095] It should be noted that for small data transmission, the UE actually completes the transmission of small data packets without entering the connected state. This type of transmission is different from entering the connected state to transmit mobile broadband (MBB) services.
[0096] In summary, small data transmission (SDT) may include SDT based on a random access procedure, or may also be SDT based on a PUR.
[0097] SDT is usually transmitted through DRB configured by network equipment. SRB does not support small data transmission, while positioning measurement reports need to be carried in NAS messages and transmitted over the air interface through SRB. Therefore, how to realize the transmission of NAS messages in the RRC inactive state is an urgent problem to be solved.
[0098] Figure 5 A schematic flow chart of a data transmission method 200 provided in an embodiment of the present application. The method 200 may be Figure 1 The terminal device in the communication system shown executes, as shown in Figure 5 As shown, the method 200 may include at least part of the following:
[0099] S220, the terminal device in the RRC inactive state sends first information to the network device when there is data to be transmitted and the inactive state data transmission condition is met;
[0100] Among them, 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 layer NAS message, the target NAS message is obtained by the terminal device encrypting and integrity processing the first NAS message, and the data to be transmitted includes the first NAS message.
[0101] That is to say, when there is data to be transmitted and the data to be transmitted includes a first NAS message, the terminal device can encrypt and integrity protect the first NAS message to obtain a target NAS message, further encapsulate the target NAS message in a first RRC message, and transmit the first RRC message through the first SRB, thereby enabling the transmission of NAS messages of terminal devices in an RRC inactive state.
[0102] Optionally, in some embodiments, the first NAS message includes a positioning measurement report.
[0103] Optionally, in some embodiments, the data to be transmitted may also include user data.
[0104] Optionally, in some embodiments, the first information also includes information for requesting restoration of the RRC connection.
[0105] Optionally, in some embodiments, the information for requesting to restore the RRC connection may include at least one of the following:
[0106] Resume ID / I-RNTI;
[0107] ResumeMAC-I;
[0108] Resume cause.
[0109] Among them, Resume ID / I-RNTI is used by the network device to identify the context of the terminal device in the suspended state, and ResumeMAC-I is used for the identity authentication of the terminal device.
[0110] Optionally, in some embodiments, the information for requesting restoration of the RRC connection may be encapsulated in a first RRC message. In other embodiments, the information for requesting restoration of the RRC connection may also be encapsulated independently, for example, in a second RRC message. This application does not limit this.
[0111] Optionally, in some embodiments, upon receiving first indication information from the NAS layer of the terminal device, the AS layer of the terminal device determines that there is data to be transmitted.
[0112] Optionally, in some embodiments, the method 200 may further include:
[0113] S210, the AS layer of the terminal device determines whether the inactive state data transmission condition is met when receiving the first indication information. For example, if the condition is met, the inactive state data transmission is performed, otherwise, the inactive state data transmission is not performed.
[0114] Optionally, the inactive state data transmission condition may include any trigger condition for a terminal device in an RRC inactive state to perform data transmission, for example, may include a first trigger condition and / or a second trigger condition.
[0115] Optionally, the first trigger condition includes at least one of the following:
[0116] The timing advance TA of the terminal equipment is valid;
[0117] The terminal device is equipped with a downlink chain counter NCC;
[0118] The pre-configured uplink resource PUR of the terminal device is valid;
[0119] There is a need to establish or restore an RRC connection, for example, when uplink data arrives.
[0120] The method for determining whether the TA is effective may refer to the related description above.
[0121] In some embodiments, the terminal device may select to perform inactive data transmission based on pre-configured uplink resources when the first trigger condition is met. That is, the terminal device may perform SDT based on random access when the first trigger condition is met.
[0122] Optionally, in some embodiments, the first trigger condition may also include that the terminal device supports PUR-based small data transmission, the network device supports PUR-based small data transmission, etc., but the present application is not limited thereto.
[0123] Optionally, the second trigger condition includes: the data volume of the uplink data is less than the maximum data volume allowed to be transmitted configured by the network device.
[0124] Optionally, the maximum data amount may be a maximum transport block (TB) size configured by the network device through a system information block (System Information Block, SIB), such as SIB2.
[0125] In some embodiments, the terminal device may select to perform inactive data transmission based on pre-configured uplink resources when the second trigger condition is met. That is, the terminal device may perform SDT based on PUR when the second trigger condition is met.
[0126] It should be understood that the above inactive data transmission conditions are only examples, but the present application is not limited thereto.
[0127] 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 a target NAS message.
[0128] Further, the NAS layer of the terminal device delivers the target NAS message to the AS layer, ie, the RRC layer, of the terminal device. The AS layer of the terminal device generates a first RRC message according to the target NAS message, and further transmits the first RRC message through the first SRB.
[0129] Optionally, in some 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 a target NAS message.
[0130] Furthermore, the NAS layer of the terminal device delivers the target NAS message to the AS layer, i.e., the RRC layer, of the terminal device. The AS layer of the terminal device performs encryption and integrity protection on the RRC message carrying the target NAS message, generates a first RRC message, and further transmits the first RRC message through the first SRB.
[0131] The following describes a method for transmitting the first information in conjunction with a specific implementation of the first SRB.
[0132] Embodiment 1: The first SRB is SRB0.
[0133] In this embodiment 1, the NAS layer of the terminal device can encrypt and integrity protect the first NAS message to obtain the target NAS message.
[0134] Optionally, in some embodiments, the AS layer of the terminal device generates the first RRC message based on the target NAS message and the information used by the terminal device to request restoration of the RRC connection.
[0135] For example, the AS layer of the terminal device may encapsulate the target NAS message and the information for requesting to resume the RRC connection in a first RRC message.
[0136] In this embodiment 1, the first RRC message transmitted via SRB0 may not be encrypted and integrity protected by the AS layer of the terminal device.
[0137] Embodiment 2: The first SRB includes SRB1 and / or SRB2.
[0138] In this embodiment 2, the NAS layer of the terminal device can encrypt and integrity protect the first NAS message to obtain the target NAS message.
[0139] Furthermore, the AS layer of the terminal device may perform encryption and integrity protection processing on the RRC message carrying the target NAS message to generate the first RRC message. That is, the first RRC message transmitted via SRB1 and / or SRB2 is encrypted and integrity protected by the NAS layer and AS layer of the terminal device.
[0140] Optionally, in this embodiment 2, the method 200 further includes:
[0141] The terminal device activates the AS layer security key and restores SRB1 and / or SRB2.
[0142] Optionally, in some embodiments, the AS layer of the terminal device may also generate a second RRC message according to the information for requesting to restore the RRC connection. For example, the AS layer of the terminal device may encapsulate the information for requesting to restore the RRC connection in the second RRC message.
[0143] Optionally, the second RRC message may be transmitted via SRB0, that is, the second RRC message does not undergo encryption and integrity protection processing at the AS layer of the terminal device.
[0144] In summary of the above-mentioned Embodiment 1 and Embodiment 2, the first NAS message may be transmitted via SRB0, wherein the first NAS message is encrypted and integrity protected by the NAS layer of the terminal device. Alternatively, the first NAS message may be transmitted via SRB1 and / or SRB2, wherein the first NAS message is encrypted and integrity protected by the NAS layer and the AS layer of the terminal device.
[0145] Optionally, in some embodiments, if the data to be transmitted also includes user data, the AS layer of the terminal device may further perform encryption and integrity protection processing on the user data to obtain target user data. The target user data may be transmitted via the DRB.
[0146] Optionally, in some embodiments, if the data to be transmitted also includes user data, the method 200 further includes: the terminal device restoring the DRB.
[0147] Optionally, in some embodiments, the first information may also include other data, such as MAC CE and / or padding bit, etc.
[0148] In some embodiments, the multiplexing of the first RRC message, the second RRC message, the target user data, the MAC CE, and the padding bits may follow a Logical Channel Prioritization (LCP) process.
[0149] Optionally, in some embodiments, Figure 5 As shown, the method 200 further includes:
[0150] S230: The terminal device receives second information sent by the network device, wherein the second information includes at least one of the following:
[0151] a third RRC message, wherein the third RRC message is transmitted through the second SRB;
[0152] Subsequent downlink scheduling;
[0153] Subsequent uplink scheduling.
[0154] It should be noted that the subsequent uplink scheduling and subsequent downlink scheduling here may be relative to the first SDT. For example, the subsequent uplink scheduling may refer to the uplink scheduling after the first SDT, and the subsequent downlink scheduling may refer to the downlink scheduling after the first SDT.
[0155] Optionally, in some embodiments, the third RRC message includes at least one of the following:
[0156] Configuration information for releasing the RRC connection;
[0157] Configuration information for restoring the RRC connection;
[0158] Configuration information for establishing an RRC connection;
[0159] Downlink NAS message.
[0160] That is to say, the downlink NAS message to be sent by the network device can be multiplexed with the configuration information for releasing / restoring / establishing the RRC connection and sent to the terminal device. Alternatively, the downlink NAS message to be sent by the network device may not be multiplexed with the configuration information for releasing / restoring / establishing the RRC connection, that is, not transmitted through the second SRB.
[0161] Optionally, the subsequent downlink scheduling includes an RRC message carrying a NAS message; and / or
[0162] The subsequent uplink scheduling includes an RRC message carrying a NAS message.
[0163] That is, the downlink NAS message to be sent by the network device may be carried in the RRC message, and further included in the transmission in the subsequent downlink scheduling and / or the subsequent uplink scheduling.
[0164] Optionally, in some embodiments, the second SRB includes SRB1.
[0165] Optionally, in some embodiments, the uplink resource used to transmit the first information is an uplink resource used for random access, or a pre-configured uplink resource, or a subsequent uplink scheduling resource.
[0166] As an example, if carried on SRB0, the first information needs to be sent during the first uplink small data transmission process, because the RRC message carried on SRB0 needs to include information for requesting to restore the RRC connection in addition to the NAS message. In this case, the first information can be sent through resources used for random access, such as resources for transmitting MSGA or Msg3, or it can also be sent through pre-configured uplink resources, such as CG resources.
[0167] As another example, if carried on SRB1 / SRB2, the first information can be sent during the first uplink small data transmission process, or it can be sent through uplink resources further scheduled by the network device after the first uplink small data transmission process, that is, through subsequent uplink scheduling resources.
[0168] In summary, the first information can be sent based on random access small data transmission, or can be sent based on PUR small data transmission, or can be sent in uplink scheduling after small data transmission. This application does not limit the sending timing of the first information.
[0169] The following, combined Figure 6 and Figure 7 , describing the specific process of the data transmission method according to an embodiment of the present application.
[0170] exist Figure 6 In the example, NAS messages are transmitted via SRB0. Figure 6 As shown, at least some of the following steps may be included:
[0171] S201, when there is data to be transmitted, the NAS layer of the terminal device sends first indication information to the AS layer of the terminal device, indicating that there is data to be transmitted, wherein the data to be transmitted includes a first NAS message.
[0172] S202, the AS layer of the terminal device determines whether a non-active data transmission condition is met, and executes non-active data transmission if the non-active data transmission condition is met.
[0173] S203, the NAS layer of the terminal device encrypts and performs integrity protection processing on the first NAS message to obtain a target NAS message.
[0174] S204, the NAS layer of the terminal device delivers the target NAS message to the AS layer of the terminal device.
[0175] S205, the AS layer of the terminal device encapsulates the target NAS message and the following information in the first RRC message:
[0176] Resume ID;
[0177] ResumeMAC-I;
[0178] resume cause.
[0179] Optionally, if the data to be transmitted also includes user data, the terminal device may also activate the AS layer security key and restore the DRB for transmitting the user data.
[0180] Optionally, the AS layer of the terminal device may also perform encryption and integrity protection processing on the user data to obtain target user data.
[0181] S206, the AS layer of the terminal device sends first information to the network device.
[0182] The first information includes a first RRC message, and the first RRC message is transmitted via SRB0. The first RRC message is not encrypted and integrity protected at the AS layer.
[0183] If the data to be transmitted also includes user data, the first information may also include target user data, which is transmitted via the DRB.
[0184] Optionally, the first information may also include MAC CE and / or padding bits, etc.
[0185] In some embodiments, multiplexing of the first RRC message, the target user data, the MAC CE, and padding bits may follow an LCP procedure.
[0186] Furthermore, the AS layer of the terminal device can receive the second information of the AS layer of the network device. For specific implementation, please refer to the relevant description in the previous text and will not be repeated here.
[0187] exist Figure 7 In the example, NAS messages are transmitted via SRB1 and / or SRB2. Figure 7 As shown, at least some of the following steps may be included:
[0188] S301, when there is data to be transmitted, the NAS layer of the terminal device sends first indication information to the AS layer of the terminal device, indicating that there is data to be transmitted, wherein the data to be transmitted includes a first NAS message.
[0189] S302, the AS layer of the terminal device determines whether a non-active data transmission condition is met, and executes non-active data transmission if the non-active data transmission condition is met.
[0190] S303: The NAS layer of the terminal device encrypts and performs integrity protection processing on the first NAS message to obtain a target NAS message.
[0191] S304, the NAS layer of the terminal device delivers the target NAS message to the AS layer of the terminal device.
[0192] S305, the AS layer of the terminal device encapsulates the target NAS message in the RRC message.
[0193] In S305, the terminal device may also activate the AS layer security key and restore SRB1 and / or SRB2.
[0194] The AS layer of the terminal device encrypts and integrity protects the RRC message carrying the target NAS message to obtain a first RRC message.
[0195] Optionally, the AS layer of the terminal device may also encapsulate the following information in the second RRC message:
[0196] Resume ID;
[0197] ResumeMAC-I;
[0198] resume cause.
[0199] Optionally, the second RRC message may be transmitted via SRB0. The second RRC message is not encrypted and integrity protected at the AS layer.
[0200] Optionally, if the data to be transmitted also includes user data, the terminal device may also restore the DRB for transmitting the user data.
[0201] Optionally, the AS layer of the terminal device may also perform encryption and integrity protection processing on the user data to obtain target user data.
[0202] S306, the AS layer of the terminal device sends first information to the network device.
[0203] The first information includes a first RRC message, and the first RRC message is transmitted via SRB1 and / or SRB2. The first RRC message is encrypted and integrity protected by the NAS layer and the AS layer of the terminal device.
[0204] If the data to be transmitted also includes user data, the first information may also include target user data, which is transmitted via the DRB and is encrypted and integrity protected at the AS layer of the terminal device.
[0205] Optionally, the first information may also include a second RRC message, transmitted via SRB0.
[0206] Optionally, the first information may also include MAC CE and / or padding bits, etc.
[0207] In some embodiments, multiplexing of the first RRC message, the target user data, the MAC CE, and padding bits may follow an LCP procedure.
[0208] Furthermore, the AS layer of the terminal device can receive the second information of the AS layer of the network device. For specific implementation, please refer to the relevant description in the previous text and will not be repeated here.
[0209] In summary, when there is a NAS message to be transmitted and the inactive data transmission conditions are met, the terminal device can encrypt and integrity protect the NAS message to be transmitted (for example, the NAS layer of the terminal device can encrypt and integrity protect the NAS message, or the NAS layer and AS layer of the terminal device both encrypt and integrity protect the NAS message). Furthermore, the encrypted and integrity protected NAS message can be transmitted through SRB, thereby enabling the transmission of NAS messages of inactive terminal devices.
[0210] Combination of the above Figures 5 to 7 , describes in detail the method embodiment of the present application, and the following is combined with Figures 8 to 12 , the device embodiments of the present application are described in detail. It should be understood that the device embodiments and the method embodiments correspond to each other, and similar descriptions can refer to the method embodiments.
[0211] Figure 8 FIG. 4 shows a schematic block diagram of a terminal device 400 according to an embodiment of the present application. Figure 8 As shown, the terminal device 400 includes:
[0212] The communication unit 410 sends first information to the network device when there is data to be transmitted and the inactive data transmission condition is met;
[0213] In which, the terminal device is in a radio resource control (RRC) inactive state, 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 layer NAS message, the target NAS message is the first NAS message obtained by encryption and integrity processing by the terminal device, and the data to be transmitted includes the first NAS message.
[0214] Optionally, in some embodiments, the first SRB is SRB0.
[0215] Optionally, in some embodiments, the terminal device 400 further includes:
[0216] a processing unit, configured to perform encryption and integrity protection processing on the first NAS message at a NAS layer to obtain the target NAS message;
[0217] Delivering the target NAS message to the AS layer of the terminal device at the NAS layer;
[0218] The first RRC message is generated at the AS layer according to the target NAS message and at least one of the following: a recovery identifier, a recovery media access control identifier, and a recovery reason.
[0219] Optionally, in some embodiments, the first SRB includes SRB1 and / or SRB2.
[0220] Optionally, in some embodiments, the terminal device 400 further includes:
[0221] a processing unit, configured to perform encryption and integrity protection processing on the first NAS message at a NAS layer to obtain the target NAS message;
[0222] Delivering the target NAS message to the AS layer of the terminal device at the NAS layer;
[0223] The RRC message carrying the target NAS message is encrypted and integrity protected at the AS layer to generate the first RRC message.
[0224] Optionally, in some embodiments, the processing unit is further configured to:
[0225] Generate a second RRC message at the AS layer according to at least one of the following:
[0226] Recovery ID, recovery media access control ID, recovery reason.
[0227] Optionally, in some embodiments, the first information also includes the second RRC message, wherein the second RRC message is transmitted via SRB0.
[0228] Optionally, in some embodiments, the terminal device 400 further includes:
[0229] A processing unit is used to activate the AS layer security key and restore the first SRB.
[0230] Optionally, in some embodiments, if the data to be transmitted also includes user data, the terminal device 400 further includes: a processing unit, configured to perform encryption and integrity protection processing on the user data at the AS layer to obtain target user data.
[0231] Optionally, in some embodiments, the first information also includes: the target user data, and the target user data is transmitted via a data radio bearer DRB.
[0232] Optionally, in some embodiments, the first information further includes:
[0233] Transmitting medium access control MAC control element CE and / or padding bits.
[0234] Optionally, in some embodiments, the communication unit 410 is further configured to: receive second information sent by a network device, wherein the second information includes at least one of the following:
[0235] A third RRC message, wherein the third RRC message is transmitted through the second SRB;
[0236] Subsequent downlink scheduling;
[0237] Subsequent uplink scheduling.
[0238] Optionally, in some embodiments, the third RRC message includes at least one of the following:
[0239] Configuration information for releasing the RRC connection;
[0240] Configuration information for restoring the RRC connection;
[0241] Configuration information for establishing an RRC connection;
[0242] Downlink NAS message.
[0243] Optionally, in some embodiments, the subsequent downlink scheduling includes an RRC message carrying a NAS message; and / or, the subsequent uplink scheduling includes an RRC message carrying a NAS message.
[0244] Optionally, in some embodiments, the second SRB includes SRB1.
[0245] Optionally, in some embodiments, the first NAS message includes a positioning measurement report.
[0246] Optionally, in some embodiments, the uplink resource used to transmit the first information is an uplink resource used for random access, or a pre-configured uplink resource, or a subsequent uplink scheduling resource.
[0247] Optionally, in some embodiments, the terminal device 400 further includes: a processing unit, configured to send first indication information to the AS layer of the terminal device at the NAS layer, wherein the first indication information is used to indicate that data is to be transmitted;
[0248] Determine at the AS layer whether the inactive data transmission conditions are met.
[0249] Optionally, in some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.
[0250] 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 method embodiment of the present application, and the above and other operations and / or functions of each unit in the terminal device 400 are respectively to implement 5 to Figure 7 For the sake of brevity, the corresponding process of the terminal device in the illustrated method embodiment will not be repeated here.
[0251] Fig. 9 It is a schematic block diagram of a network device according to an embodiment of the present application. Fig. 9 The network device 500 includes:
[0252] A communication unit, configured to receive first information sent by a terminal device in a radio resource control (RRC) inactive state when data is to be transmitted and a condition for data transmission in an inactive state is met;
[0253] Among them, 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 layer NAS message, the target NAS message is obtained by the terminal device encrypting and integrity processing the first NAS message, and the data to be transmitted includes the first NAS message.
[0254] Optionally, in some embodiments, the first SRB is SRB0.
[0255] Optionally, in some embodiments, the first RRC message further includes at least one of the following: a recovery flag, a recovery media access control flag, and a recovery reason.
[0256] Optionally, in some embodiments, the first SRB includes SRB1 and / or SRB2.
[0257] Optionally, in some embodiments, the first information also includes a second RRC message, wherein the second RRC message is transmitted via SRB0, and the second RRC message includes at least one of the following: a recovery identifier, a recovery media access control identifier, and a recovery reason.
[0258] Optionally, in some embodiments, the data to be transmitted also includes user data, the first information also includes the target user data, and the target user data transmitted via the data wireless bearer DRB is the user data encrypted and integrity protected by the AS layer of the terminal device.
[0259] Optionally, in some embodiments, the first information also includes: a media access control MAC control element CE and / or padding bits.
[0260] Optionally, in some embodiments, the communication unit 510 is further configured to:
[0261] Sending second information to the terminal device, wherein 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;
[0262] Subsequent downlink scheduling;
[0263] Subsequent uplink scheduling.
[0264] Optionally, in some embodiments, the third RRC message includes at least one of the following:
[0265] Configuration information for releasing the RRC connection;
[0266] Configuration information for restoring the RRC connection;
[0267] Configuration information for establishing an RRC connection;
[0268] Downlink NAS message.
[0269] Optionally, in some embodiments, the subsequent downlink scheduling includes an RRC message carrying a NAS message; and / or, the subsequent uplink scheduling includes an RRC message carrying a NAS message.
[0270] Optionally, in some embodiments, the second SRB includes SRB1.
[0271] Optionally, in some embodiments, the first NAS message includes a positioning measurement report.
[0272] Optionally, in some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.
[0273] 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 method embodiment of the present application, and the above and other operations and / or functions of each unit in the network device 500 are respectively to implement Figures 5 to 7 For the sake of brevity, the corresponding processes of the network device in the illustrated method embodiment are not described in detail here.
[0274] Fig.10 It is a schematic structural diagram of a communication device 600 provided in an embodiment of the present application. Fig.10 The communication device 600 shown includes a processor 610, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.
[0275] Alternatively, if Fig.10 As shown, the communication device 600 may further include a memory 620. The processor 610 may call and run a computer program from the memory 620 to implement the method in the embodiment of the present application.
[0276] The memory 620 may be a separate device independent of the processor 610 , or may be integrated into the processor 610 .
[0277] Alternatively, if Fig.10 As shown, the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.
[0278] The transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include an antenna, and the number of the antennas may be one or more.
[0279] Optionally, the communication device 600 may specifically be a network device of an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.
[0280] Optionally, the communication device 600 may specifically be a mobile terminal / terminal device of an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the mobile terminal / terminal device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.
[0281] Fig.11It is a schematic structural diagram of the chip of an embodiment of the present application. Fig.11 The chip 700 shown includes a processor 710, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.
[0282] Alternatively, if Fig.11 As shown, the chip 700 may further include a memory 720. The processor 710 may call and run a computer program from the memory 720 to implement the method in the embodiment of the present application.
[0283] The memory 720 may be a separate device independent of the processor 710 , or may be integrated into the processor 710 .
[0284] Optionally, the chip 700 may further include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.
[0285] 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 specifically, may output information or data to other devices or chips.
[0286] Optionally, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
[0287] Optionally, the chip can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
[0288] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
[0289] Fig.12 is a schematic block diagram of a communication system 900 provided in an embodiment of the present application. Fig.12 As shown, the communication system 900 includes a terminal device 910 and a network device 920 .
[0290] Among them, the terminal device 910 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 920 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they are not repeated here.
[0291] It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and performed. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, and other mature storage media in the art. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
[0292] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0293] It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.
[0294] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.
[0295] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.
[0296] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.
[0297] An embodiment of the present application also provides a computer program product, including computer program instructions.
[0298] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.
[0299] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.
[0300] The embodiment of the present application also provides a computer program.
[0301] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods in the embodiments of the present application. For the sake of brevity, they are not described here.
[0302] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of the present application. When the computer program is run on a computer, the computer executes the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.
[0303] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0304] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0305] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0306] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple 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.
[0307] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0308] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0309] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
Claims
1. A data transmission method, characterized in that: include: The terminal device in the radio resource control RRC inactive state sends the first information to the network device when there is data to be transmitted and the inactive state data transmission condition is 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 layer NAS message, the target NAS message is obtained by the terminal device encrypting and integrity processing the first NAS message, and the data to be transmitted includes the first NAS message; Wherein, the first SRB includes SRB1 and / or SRB2; The method further comprises: The NAS layer of the terminal device encrypts and performs integrity protection processing on the first NAS message to obtain the target NAS message; The NAS layer of the terminal device delivers the target NAS message to the AS layer of the terminal device; The AS layer of the terminal device encrypts and integrity protects the RRC message carrying the target NAS message to generate the first RRC message.
2. The method according to claim 1, characterized in that The method further comprises: The AS layer of the terminal device generates a second RRC message according to at least one of the following: Recovery ID, recovery media access control ID, recovery reason.
3. The method according to claim 2, characterized in that The first information also includes the second RRC message, wherein the second RRC message is transmitted via SRB0.
4. The method according to any one of claims 1 to 3, characterized in that The method further comprises: The terminal device activates the AS layer security key and restores the first SRB.
5. The method according to any one of claims 1 to 3, characterized in that: If the data to be transmitted also includes user data, the method further includes: The AS layer of the terminal device encrypts and performs integrity protection processing on the user data to obtain target user data.
6. The method according to claim 5, characterized in that The first information also includes: the target user data, and the target user data is transmitted via a data radio bearer DRB.
7. The method according to any one of claims 1 to 3, characterized in that The first information also includes: Transmitting medium access control MAC control element CE and / or padding bits.
8. The method according to any one of claims 1 to 3, characterized in that The method further comprises: The terminal device receives second information sent by the network device, wherein the second information includes at least one of the following: A third RRC message, wherein the third RRC message is transmitted through the second SRB; Subsequent downlink scheduling; Subsequent uplink scheduling.
9. The method according to claim 8, characterized in that The third RRC message includes at least one of the following: Configuration information for releasing the RRC connection; Configuration information for restoring the RRC connection; Configuration information for establishing an RRC connection; Downlink NAS message.
10. The method according to claim 8, characterized in that The subsequent downlink scheduling includes an RRC message carrying a NAS message; and / or The subsequent uplink scheduling includes an RRC message carrying a NAS message.
11. The method according to claim 8, characterized in that The second SRB includes SRB1.
12. The method according to any one of claims 1 to 3, characterized in that The first NAS message includes a positioning measurement report.
13. The method according to any one of claims 1 to 3, characterized in that: The uplink resource used to transmit the first information is an uplink resource used for random access, or a pre-configured uplink resource, or a subsequent uplink scheduling resource.
14. The method according to any one of claims 1 to 3, characterized in that The method further comprises: The NAS layer of the terminal device sends first indication information to the AS layer of the terminal device, where the first indication information is used to indicate that data is to be transmitted; The AS layer of the terminal device determines whether the inactive data transmission condition is met.
15. A terminal device, characterized in that: include: The communication unit sends first information to the network device when there is data to be transmitted and the inactive data transmission condition is met; The terminal device is in a radio resource control (RRC) inactive state, 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 layer (NAS) message, the target NAS message is obtained by the terminal device by encrypting and integrity processing the first NAS message, and the data to be transmitted includes the first NAS message; The first SRB includes SRB1 and / or SRB2; wherein the terminal device further includes: a processing unit, configured to perform encryption and integrity protection processing on the first NAS message at a NAS layer to obtain the target NAS message; Delivering the target NAS message to the AS layer of the terminal device at the NAS layer; The RRC message carrying the target NAS message is encrypted and integrity protected at the AS layer to generate the first RRC message.
16. The terminal device according to claim 15, characterized in that: The processing unit is also used for: Generate a second RRC message at the AS layer according to at least one of the following: Recovery ID, recovery media access control ID, recovery reason.
17. The terminal device according to claim 16, characterized in that: The first information also includes the second RRC message, wherein the second RRC message is transmitted via SRB0.
18. The terminal device according to any one of claims 15 to 17, characterized in that: The terminal device further includes: A processing unit is used to activate the AS layer security key and restore the first SRB.
19. The terminal device according to any one of claims 15 to 17, characterized in that: If the data to be transmitted also includes user data, the terminal device further includes: The processing unit is used to encrypt and integrity protect the user data at the AS layer to obtain target user data.
20. The terminal device according to claim 19, characterized in that: The first information also includes: the target user data, and the target user data is transmitted via a data radio bearer DRB.
21. The terminal device according to any one of claims 15 to 17, characterized in that: The first information also includes: Transmitting medium access control MAC control element CE and / or padding bits.
22. The terminal device according to any one of claims 15 to 17, characterized in that: The communication unit is further configured to: receive second information sent by the network device, wherein the second information includes at least one of the following: A third RRC message, wherein the third RRC message is transmitted through the second SRB; Subsequent downlink scheduling; Subsequent uplink scheduling.
23. The terminal device according to claim 22, characterized in that: The third RRC message includes at least one of the following: Configuration information for releasing the RRC connection; Configuration information for restoring the RRC connection; Configuration information for establishing an RRC connection; Downlink NAS message.
24. The terminal device according to claim 23, characterized in that: The subsequent downlink scheduling includes an RRC message carrying a NAS message; and / or The subsequent uplink scheduling includes an RRC message carrying a NAS message.
25. The terminal device according to claim 22, characterized in that: The second SRB includes SRB1.
26. The terminal device according to any one of claims 15 to 17, characterized in that: The first NAS message includes a positioning measurement report.
27. The terminal device according to any one of claims 15 to 17, characterized in that: The uplink resource used to transmit the first information is an uplink resource used for random access, or a pre-configured uplink resource, or a subsequent uplink scheduling resource.
28. The terminal device according to any one of claims 15 to 17, characterized in that: The terminal device further includes: a processing unit, configured to send first indication information to the AS layer of the terminal device at the NAS layer, wherein the first indication information is used to indicate that data is to be transmitted; Determine at the AS layer whether the inactive data transmission conditions are met.
29. A terminal device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 14.
30. A chip, characterized in that: include: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 14.
31. A computer-readable storage medium, characterized in that: Used to store a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 14.
32. A computer program product, characterized in that The method comprises computer program instructions which cause a computer to execute the method as claimed in any one of claims 1 to 14.
