Data transmission method and terminal equipment

Abstract

The application of the invention is a divisional application of 202080104861.8. A data transmission method and a terminal device, capable of implementing inactive state data transmission based on a pre-configured uplink resource or a random access resource, the method comprising: if the terminal device selects to perform inactive state data transmission based on a random access resource, the terminal device sends uplink information to a network device, the uplink information at least comprises uplink data to be sent by the terminal equipment and identification information of the terminal equipment.

Description

[0001] This application is a divisional application of the invention patent application with the application date of August 7, 2020, application number 202080104861.8, and invention name “Data transmission method and terminal device”. Technical Field

[0002] The embodiments of the present application relate to the field of communications, and specifically to a data transmission method and terminal equipment. Background Art

[0003] In the New Radio (NR) system, in order to reduce air interface signaling and quickly restore wireless connections and data services, 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. For UEs in the RRC_INACTIVE state, the radio bearer and all radio resources will be released, but the terminal side and the base station side retain the access context of the terminal device in order to quickly restore the RRC connection. The network usually keeps terminals with infrequent data transmission in the RRC_INACTIVE state.

[0004] For RRC_INACTIVE terminal devices, when the mobile originated (Mobile Originated, MO) or mobile received (Mobile Terminated, MT) data arrives, the terminal device needs to restore the connection and release it to the INACTIVE state after the data transmission is completed. Among them, MO data and MT data are both for terminal devices. MO data can refer to the uplink transmission initiated by the mobile terminal, and MT data can refer to the downlink transmission received by the mobile terminal. For UEs with small data volumes and low transmission frequencies, such a transmission mechanism will lead to unnecessary power consumption and signaling overhead. Therefore, how to perform small data transmission to reduce signaling overhead is an urgent problem to be solved. Summary of the invention

[0005] The embodiments of the present application provide a data transmission method and a terminal device, which can perform non-activated data transmission based on pre-configured uplink resources or random access resources, thereby reducing signaling overhead.

[0006] In a first aspect, a data transmission method is provided, comprising: if a terminal device chooses to perform non-activated data transmission based on pre-configured uplink resources, the terminal device sends uplink information to a network device, the uplink information at least including the uplink data to be sent by the terminal device, or the uplink information at least including the uplink data to be sent by the terminal device and identification information of the terminal device.

[0007] In a second aspect, a data transmission method is provided, comprising: if a terminal device chooses to perform non-activated data transmission based on random access resources, the terminal device sends uplink information to a network device, and the uplink information includes at least uplink data to be sent by the terminal device and identification information of the terminal device.

[0008] In a third aspect, a terminal device is provided, which is used to execute the method in the first aspect or any possible implementation of the first aspect. Specifically, the terminal device includes a unit for executing the method in the first aspect or any possible implementation of the first aspect.

[0009] In a fourth aspect, a terminal device is provided, which is used to execute the method in the second aspect or any possible implementation of the second aspect. Specifically, the network device includes a unit for executing the method in the second aspect or any possible implementation of the second aspect.

[0010] In a fifth aspect, a terminal device is provided, the terminal device comprising: a processor and a memory. 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.

[0011] In a sixth aspect, a terminal device is provided, the terminal device comprising: a processor and a memory. 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 manner.

[0012] 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.

[0013] Specifically, the chip includes: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes a method as described in any one of the first to second aspects or in each of their implementations.

[0014] 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.

[0015] In a ninth aspect, a computer program product is provided, comprising computer program instructions, which enable a computer to execute the method in any one of the first to second aspects or their respective implementations.

[0016] 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.

[0017] Based on the above technical solution, when the terminal device performs non-activated data transmission based on the pre-configured uplink resources, since the network side can save the correspondence between the pre-configured uplink resources and the identification information of the terminal device, or may not save the correspondence, the uplink information sent by the terminal device may carry the identification information of the terminal device in addition to the uplink data to be transmitted, or may not carry the identification information of the terminal device. As long as the network device can identify the UE, non-activated data transmission based on the pre-configured uplink resources can be achieved.

[0018] On the other hand, when the terminal device performs non-activated data transmission based on random access resources, since the random access resources are cell shared resources, the network device cannot identify the terminal device through the random access resources. In this case, the uplink information sent by the terminal device needs to carry the identification information of the terminal device in addition to the uplink data to be transmitted, which is beneficial to ensure that the network device can identify the UE, thereby realizing non-activated data transmission based on random access resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 It is a schematic diagram of an application scenario provided by an embodiment of the present application.

[0020] Figure 2 It is a schematic flow chart of UE requesting PUR.

[0021] Figure 3 It is a schematic diagram of data transmission using PUR.

[0022] Figure 4 It is a schematic diagram of data transmission using random access resources.

[0023] Figure 5 It is a schematic diagram of a data transmission method provided in an embodiment of the present application.

[0024] Figure 6 It is a schematic diagram of another data transmission method provided in an embodiment of the present application.

[0025] Figure 7 It is a schematic block diagram of a terminal device provided in an embodiment of the present application.

[0026] Figure 8 It is a schematic block diagram of another terminal device provided in an embodiment of the present application.

[0027] Fig. 9It is a schematic block diagram of a communication device provided in another embodiment of the present application.

[0028] Fig.10 It is a schematic block diagram of a chip provided in an embodiment of the present application. DETAILED DESCRIPTION

[0029] 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.

[0030] 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.

[0031] 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.

[0032] 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.

[0033] 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.

[0034] 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.

[0035] 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.

[0036] 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.).

[0037] 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.

[0038] 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.

[0039] 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.

[0040] 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.

[0041] 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.

[0042] 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.

[0043] 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.

[0044] 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.

[0045] 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.

[0046] 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.

[0047] 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.

[0048] 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.

[0049] 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.

[0050] 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.

[0051] 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.

[0052] 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.

[0053] 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.

[0054] 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.

[0055] 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.

[0056] 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.

[0057] 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.

[0058] Before a UE in the IDLE state wants to use PUR for data transmission, the following prerequisites must be met:

[0059] 1. To be effective, TA must meet the following two conditions at the same time:

[0060] 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.

[0061] 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.

[0062] 2. The UE is configured with a Next Hop Chaining Count (NCC), which is used to derive new keys.

[0063] Optionally, the NCC may be configured through an RRC message, for example, the RRC message may be an RRCConnectionRelease message.

[0064] 3. Valid PUR: The cell where the UE resides supports PUR and is configured with PUR.

[0065] 4. There is a need to establish or restore an RRC connection, such as uplink data arriving;

[0066] Combination Figure 3 , describing the process of a UE in IDLE state using PUR for data transmission.

[0067] When the aforementioned prerequisites are met, the UE in the idle state can use the PUR for data transmission.

[0068] 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.

[0069] 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.

[0070] 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 is used for the identity authentication of the UE.

[0071] 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).

[0072] S42, data transmission is performed between the access network device and the core network device.

[0073] 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).

[0074] 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:

[0075] a) The release cause (releaseCause) is set to RRC-Suspend;

[0076] b) resume ID / I-RNTI;

[0077] c) NCC;

[0078] d)DRB continuous reliable header compression (Robust Header Compression, ROHC), namely drb-ContinueROHC.

[0079] 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.

[0080] 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.

[0081] 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);

[0082] S32. The eNB sends a UE CONTEXT RESUME REQUEST to the Mobility Management Entity (MME);

[0083] S33. Modify the bearer between MME and Serving Gateway (SGW);

[0084] S34.MME sends a UE CONTEXT RESUME RESPONSE to the eNB;

[0085] S35. The eNB sends the uplink data sent by the UE to the SGW (ie, small data transmission);

[0086] S36. The SGW receives the downlink data sent by the eNB (optionally);

[0087] S37 suspends the process between eNB and SGW, and modifies the bearer between MME and SGW;

[0088] S38. The eNB sends an RRC connection release message to the UE. Optionally, the RRC connection release message includes downlink data.

[0089] 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.

[0090] Random access resources are shared resources among cells, while PUR resources are only valid in the currently configured cell. In this case, for an inactive UE, how to perform data transmission is an urgent problem to be solved.

[0091] 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 5As shown, the method 200 may include at least part of the following:

[0092] S210, if the terminal device chooses to perform non-activated data transmission based on pre-configured uplink resources, the terminal device sends uplink information to the network device, and the uplink information at least includes the uplink data to be sent by the terminal device, or the uplink information at least includes the uplink data to be sent by the terminal device and the identification information of the terminal device.

[0093] Optionally, the pre-configured uplink resource PUR may be configured by a network device. The network device may configure the PUR by itself, or may configure the PUR based on a request of a terminal device, registration information or a local policy.

[0094] Optionally, in some embodiments, the uplink data may be EDT.

[0095] In some embodiments, the terminal device may choose to perform inactive data transmission based on pre-configured uplink resources when a first trigger condition is met.

[0096] Optionally, the first trigger condition includes at least one of the following:

[0097] The timing advance TA of the terminal equipment is valid;

[0098] The terminal device is equipped with a downlink chain counter NCC;

[0099] The pre-configured uplink resources of the terminal device are valid;

[0100] There is a need to establish or restore an RRC connection, for example, when uplink data arrives.

[0101] The method for determining whether the TA is effective may refer to the related description above.

[0102] 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.

[0103] When the terminal device chooses to perform non-activated data transmission based on PUR, the terminal device sends the uplink information to the network device. The specific content of the uplink information is described below.

[0104] Embodiment 1: The uplink information at least includes uplink data to be sent.

[0105] In this case, the PUR used by the terminal device to send the uplink information has a corresponding relationship with the identification information of the terminal device. For example, the PUR may be configured per UE, and the network device can identify the terminal device based on the PUR of the uplink information received. Therefore, the terminal device does not need to send the identification information of the terminal device. In this case, the network side needs to store the corresponding relationship between the PUR and the UE identification.

[0106] Embodiment 2: The uplink information at least includes uplink data to be sent and identification information (ID) of the terminal device.

[0107] In this embodiment, the PUR used by the terminal device to send the uplink information and the identification information of the terminal device may not have a corresponding relationship, that is, the network device cannot identify the terminal device based on the PUR received for the uplink information, so the terminal device may need to send the identification information of the terminal device. In this case, the network side does not need to store the corresponding relationship between the PUR and the UE's identification.

[0108] It should be understood that in the second embodiment, the identification information of the terminal device can be carried in any uplink message or signaling and sent to the network device together with the uplink data.

[0109] As an example, the uplink information includes a radio resource control RRC message, and the identification information of the terminal device is included in the RRC message.

[0110] Optionally, the RRC message is an RRC recovery request message, namely, RRCResumeRequest.

[0111] In a specific implementation, the uplink information is a media access control MAC protocol data unit (Protocol Data Unit, PDU), the MAC PDU includes multiple MAC sub-PDUs, the uplink data and the RRC message are respectively contained in different MAC sub-PDUs in the MAC PDU, wherein the uplink data can occupy one or more MAC sub PDUs in the MAC PDU, and the RRC message can occupy one or more MAC sub PDUs in the MAC PDU.

[0112] In this way, when sending the MAC PDU, the RRC message and the uplink data can be initiated to the network device together, thereby realizing inactive data transmission using PUR.

[0113] As another example, the uplink information includes a Media Access Control Control Element (MAC CE), and the identification information of the terminal device is included in the MAC CE.

[0114] In some embodiments of the present application, the terminal device may directly adopt embodiment 1 or embodiment 2 to perform inactive data transmission based on PUR, or may adopt a specific method to perform inactive data transmission based on PUR based on the instruction of the network device.

[0115] For example, the terminal device determines the content of the uplink information according to the first indication information sent by the network device. The first indication information is used to indicate the information content carried by the terminal device for inactive transmission based on PUR, or whether the identification information of the terminal device needs to be carried.

[0116] As an example, the first indication information is used to indicate that the uplink information at least includes uplink data; or,

[0117] The first indication information is used to indicate that the uplink information at least includes uplink data and identification information of the terminal device.

[0118] As another example, the first indication information is used to indicate whether the PUR-based inactive data transmission carries identification information of the terminal device.

[0119] Furthermore, the first indication information may also indicate a carrying method of the identification information of the terminal device, that is, through what message or signaling the identification information of the terminal device is carried.

[0120] As an example, the first indication information is used to indicate that the identification information of the terminal device is carried in an RRC message or MAC CE.

[0121] Optionally, in some embodiments of the present application, the first indication information is included in a first message, and the first message is used to configure the preconfigured uplink resource. That is, when configuring the PUR, the network device can also configure the information content sent when using the PUR for inactive data transmission.

[0122] Combination of the above Figure 5 , describes a data transmission method according to an embodiment of the present application, and the following is combined with Figure 6 , describes a data transmission method according to another embodiment of the present application.

[0123] Figure 6 is a schematic flow chart of a data transmission method 300 according to another embodiment of the present application. The method 300 may be Figure 1 The terminal device in the communication system shown executes, as shown in Figure 5 As shown, the method 300 includes the following contents:

[0124] S310, if the terminal device chooses to perform non-activated data transmission based on random access resources, the terminal device sends uplink information to the network device, and the uplink information at least includes uplink data to be sent by the terminal device and identification information of the terminal device.

[0125] In this embodiment, the random access resources can be shared by the cell. For example, the network device can notify the UE in the cell of the resources used for random access by broadcasting. In this case, the network device cannot identify the UE based on the random access resources for receiving uplink information. Therefore, when performing non-activated data transmission based on the random access resources, the terminal device needs to carry the identification information of the terminal device so that the network device can identify the UE.

[0126] In some embodiments, the terminal device may choose to perform inactive data transmission based on pre-configured uplink resources when a second trigger condition is met.

[0127] 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.

[0128] 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.

[0129] If the amount of uplink data is less than the maximum TB size broadcasted, the terminal device may initiate EDT transmission through random access resources, otherwise, the terminal device uses the normal connection establishment process to enter the connected state to transmit data.

[0130] Optionally, in an embodiment of the present application, the identification information of the terminal device can be carried in any downlink message or signaling and sent to the network device together with the uplink data.

[0131] As an example, the uplink information includes an RRC message, and the identification information of the terminal device is included in the RRC message. Optionally, the RRC message is an RRC recovery request message, namely, RRCResumeRequest.

[0132] In a specific implementation, the uplink information is a MAC PDU, the MAC PDU includes multiple MAC sub PDUs, the uplink data and the RRC message are respectively contained in different MAC sub-PDUs in the MAC PDU, wherein the uplink data can occupy one or more MAC sub PDUs in the MAC PDU, and the RRC message can occupy one or more MAC sub PDUs in the MAC PDU.

[0133] In this way, when sending the MAC PDU, the RRC message and the uplink data can be initiated to the network device together, thereby realizing inactive data transmission using random access resources.

[0134] Combination of the above Figures 5 and 6 , describes in detail the method embodiment of the present application, and the following is combined with Figures 7 to 10 , 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.

[0135] Figure 7 FIG. 4 shows a schematic block diagram of a terminal device 400 according to an embodiment of the present application. Figure 7 As shown, the terminal device 400 includes:

[0136] The communication unit 410 is used to send uplink information to the network device if the terminal device chooses to perform non-activated data transmission based on pre-configured uplink resources. The uplink information at least includes the uplink data to be sent by the terminal device, or the uplink information at least includes the uplink data to be sent by the terminal device and the identification information of the terminal device.

[0137] Optionally, in some embodiments, the uplink information includes a radio resource control RRC message, and the identification information of the terminal device is included in the RRC message.

[0138] Optionally, in some embodiments, the RRC message is an RRC recovery request message.

[0139] Optionally, in some embodiments, the uplink information is a media access control MAC protocol data unit PDU, and the uplink data and the RRC message are respectively contained in different MAC sub-PDUs in the MAC PDU.

[0140] Optionally, in some embodiments, the uplink information includes a media access control MAC control element CE, and the identification information of the terminal device is included in the MAC CE.

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

[0142] The processing unit is used to determine the content included in the uplink information according to the first indication information of the network device.

[0143] Optionally, in some embodiments, the first indication information is used to indicate that the uplink information at least includes uplink data; or,

[0144] The first indication information is used to indicate that the uplink information at least includes uplink data and identification information of the terminal device.

[0145] Optionally, in some embodiments, the first indication information is also used to indicate a method for carrying the identification information of the terminal device.

[0146] Optionally, in some embodiments, the first indication information is used to indicate that the identification information of the terminal device is carried in an RRC message or MAC CE.

[0147] Optionally, in some embodiments, the first indication information is included in a first message, and the first message is used to configure the pre-configured uplink resources.

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

[0149] The processing unit is used to select inactive data transmission based on pre-configured uplink resources when a first trigger condition is met.

[0150] Optionally, in some embodiments, the first trigger condition includes at least one of the following:

[0151] The timing advance TA of the terminal equipment is valid;

[0152] The terminal device is equipped with a downlink chain counter NCC;

[0153] The pre-configured uplink resources of the terminal device are valid;

[0154] There is a need to establish or restore an RRC connection.

[0155] 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.

[0156] 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 Figure 5For the sake of brevity, the corresponding process of the terminal device in the method 200 is not repeated here.

[0157] Figure 8 It is a schematic block diagram of a terminal device according to an embodiment of the present application. Figure 8 The terminal device 500 includes:

[0158] The communication unit 510 is used to send uplink information to the network device if the terminal device chooses to perform non-active data transmission based on random access resources. The uplink information at least includes the uplink data to be sent by the terminal device and the identification information of the terminal device.

[0159] Optionally, in some embodiments, the uplink information includes a radio resource control RRC message, and the identification information of the terminal device is included in the RRC message.

[0160] Optionally, in some embodiments, the RRC message is an RRC recovery request message.

[0161] Optionally, in some embodiments, the uplink information is a media access control MAC protocol data unit PDU, and the uplink data and the RRC message are respectively contained in different MAC sub-PDUs in the MAC PDU.

[0162] Optionally, in some embodiments, the terminal device 500 further includes:

[0163] The processing unit is used to select the random access resource to perform inactive data transmission when the second trigger condition is met.

[0164] Optionally, in some embodiments, the second trigger condition includes:

[0165] The amount of the uplink data is less than the maximum amount of data allowed to be transmitted configured by the network device.

[0166] 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.

[0167] It should be understood that the terminal 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 above and other operations and / or functions of each unit in the terminal device 500 are respectively to implement Figure 6 For the sake of brevity, the corresponding process of the terminal device in the method 300 is not repeated here.

[0168] Fig. 9 It is a schematic structural diagram of a communication device 600 provided in an embodiment of the present application. Fig. 9 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.

[0169] Alternatively, if Fig. 9 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.

[0170] The memory 620 may be a separate device independent of the processor 610 , or may be integrated into the processor 610 .

[0171] Alternatively, if Fig. 9 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.

[0172] 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.

[0173] 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.

[0174] 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.

[0175] Fig.10 It is a schematic structural diagram of the chip of an embodiment of the present application. Fig.10 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.

[0176] Alternatively, if Fig.10 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.

[0177] The memory 720 may be a separate device independent of the processor 710 , or may be integrated into the processor 710 .

[0178] 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.

[0179] 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.

[0180] 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.

[0181] 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.

[0182] 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.

[0183] 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.

[0184] 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.

[0185] 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.

[0186] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0187] 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.

[0188] 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.

[0189] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0190] 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.

[0191] 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.

[0192] The embodiment of the present application also provides a computer program.

[0193] 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.

[0194] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of the present application. When the computer program runs on the 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.

[0195] 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.

[0196] 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.

[0197] 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.

[0198] 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.

[0199] 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.

[0200] 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.

[0201] 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: If the terminal device chooses to perform non-activated data transmission based on pre-configured uplink resources, the terminal device sends uplink information to the network device, and the uplink information at least includes the uplink data to be sent by the terminal device, or the uplink information at least includes the uplink data to be sent by the terminal device and the identification information of the terminal device.

2. The method according to claim 1, characterized in that The uplink information includes a radio resource control RRC message, and the identification information of the terminal device is included in the RRC message.

3. The method according to claim 2, characterized in that The RRC message is an RRC recovery request message.

4. The method according to claim 2 or 3, characterized in that: The uplink information is a media access control MAC protocol data unit PDU, and the uplink data and the RRC message are respectively contained in different MAC sub-PDUs in the MAC PDU.

5. The method according to claim 1, characterized in that The uplink information includes a media access control MAC control element CE, and the identification information of the terminal device is included in the MAC CE.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: The terminal device determines the content included in the uplink information according to the first indication information of the network device.

7. The method according to claim 6, characterized in that The first indication information is used to indicate that the uplink information at least includes uplink data; or, The first indication information is used to indicate that the uplink information at least includes uplink data and identification information of the terminal device.

8. The method according to claim 7, characterized in that The first indication information is also used to indicate a method for carrying the identification information of the terminal device.

9. The method according to claim 8, characterized in that The first indication information is used to indicate that the identification information of the terminal device is carried in an RRC message or MAC CE.

10. The method according to any one of claims 6 to 9, characterized in that: The first indication information is included in a first message, and the first message is used to configure the pre-configured uplink resource.

11. The method according to any one of claims 1 to 10, characterized in that The method further comprises: When the first trigger condition is met, the terminal device selects to perform inactive data transmission based on pre-configured uplink resources.

12. The method according to claim 11, characterized in that The first trigger condition includes at least one of the following: The timing advance TA of the terminal equipment is valid; The terminal device is equipped with a downlink chain counter NCC; The pre-configured uplink resources of the terminal device are valid; There is a need to establish or restore an RRC connection.

13. A terminal device, characterized in that: include: A communication unit, used to send uplink information to a network device if the terminal device chooses to perform non-activated data transmission based on pre-configured uplink resources, wherein the uplink information at least includes the uplink data to be sent by the terminal device, or the uplink information at least includes the uplink data to be sent by the terminal device and the identification information of the terminal device.

14. The terminal device according to claim 13, characterized in that: The uplink information includes a radio resource control RRC message, and the identification information of the terminal device is included in the RRC message.

15. The terminal device according to claim 14, characterized in that: The RRC message is an RRC recovery request message.

16. 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 12.

Images