Method, apparatus, user equipment, and storage medium for sending data

Abstract

Embodiments of the present disclosure provide a method, apparatus, user equipment, and storage medium for sending data. Among them, when applied to a terminal, the method includes: determining the uplink synchronization state of the terminal and the state of the physical uplink shared channel (PUSCH) resources pre-configured by the base station for the terminal; in response to the terminal being in the uplink synchronization state and the physical uplink shared channel (PUSCH) resources being valid, sending data to the base station on the physical uplink shared channel (PUSCH) resources, where the data is the data of the terminal in the radio resource control (RRC) inactive state.

Description

Technical Field

[0001] The present disclosure relates to the field of wireless communication technologies, but is not limited to wireless technologies, and in particular, relates to a method, apparatus, user equipment, and storage medium for sending data. Background Art

[0002] In the related technologies of the fifth-generation mobile communication (5G), the states of radio resource control (RRC) include RRC connected state, RRC idle state, and RRC inactive state. When a terminal switches from the RRC idle state or the RRC inactive state to the RRC connected state, a large amount of signaling overhead is generated.

[0003] During the wireless communication process of a terminal, when the terminal is in the RRC inactive state, there is a need to send small data to a base station. In the related technologies, the method of sending the small data after switching from the RRC inactive state to the RRC connected state is adopted. However, this will bring a large amount of signaling overhead, and the generated signaling overhead is even greater than the data volume of the small data. And frequently making the terminal work in the RRC connected state results in large latency and high power consumption. Summary of the Invention

[0004] An embodiment of the present disclosure discloses a method for sending data, which is applied to a terminal, and the method includes:

[0005] Determine the uplink synchronization state of the terminal and the state of the physical uplink shared channel (PUSCH) resources pre-configured by the base station for the terminal;

[0006] In response to the terminal being in the uplink synchronization state and the PUSCH resources being valid, send data to the base station on the PUSCH resources, where the data is the data of the terminal in the RRC inactive state.

[0007] In one embodiment, the method further includes:

[0008] In response to the terminal being in the uplink synchronization state and the PUSCH resources being invalid, send the data to the base station through a random access channel.

[0009] In one embodiment, the sending the data to the base station through a random access channel includes:

[0010] Send the data to the base station via a two-step random access access channel or a four-step random access access channel according to the random access configuration of the terminal.

[0011] In one embodiment, the sending the data to the base station via a two-step random access access channel or a four-step random access access channel according to the random access configuration of the terminal includes:

[0012] In response to determining that the terminal supports two-step random access according to the random access configuration, send the data to the base station via the two-step random access access channel.

[0013] In one embodiment, the sending the data to the base station via a two-step random access access channel or a four-step random access access channel according to the random access configuration of the terminal further includes:

[0014] In response to determining that the terminal does not support two-step random access according to the random access configuration, send the data to the base station via the four-step random access access channel.

[0015] In one embodiment, the determining the uplink synchronization state of the terminal and the state of the physical uplink shared channel (PUSCH) resources pre-configured by the base station for the terminal includes:

[0016] In response to the time alignment timer maintained by the terminal being valid, determine that the terminal is in the uplink synchronization state;

[0017] Or,

[0018] In response to the time alignment timer maintained by the terminal being invalid, determine that the terminal is in the non-uplink synchronization state.

[0019] In one embodiment, the determining the uplink synchronization state of the terminal and the state of the physical uplink shared channel (PUSCH) resources pre-configured by the base station for the terminal includes:

[0020] In response to the configured grant timer being valid, determine that the physical uplink shared channel (PUSCH) resources are valid;

[0021] Or,

[0022] In response to the configured grant timer being invalid, determine that the physical uplink shared channel (PUSCH) resources are invalid.

[0023] In one embodiment, the sending data to the base station on the physical uplink shared channel (PUSCH) resources includes:

[0024] Transmit data and the terminal identifier of the terminal to a base station on the physical uplink shared channel (PUSCH) resource.

[0025] In one embodiment, the terminal identifier includes: the inactivated state radio network temporary identifier (I-RNTI) of the terminal.

[0026] According to a second aspect of an embodiment of the present disclosure, there is provided a device for transmitting data, which is applied to a terminal. The device includes a determination module and a transmission module; wherein,

[0027] The determination module is configured to determine the uplink synchronization state of the terminal and the state of the physical uplink shared channel (PUSCH) resource pre-configured by the base station for the terminal;

[0028] The transmission module is configured to, in response to the terminal being in an uplink synchronization state and the physical uplink shared channel (PUSCH) resource being valid, transmit data to the base station on the physical uplink shared channel (PUSCH) resource, where the data includes: data of the terminal in the radio resource control (RRC) inactivated state.

[0029] In one embodiment, the transmission module is further configured to:

[0030] In response to the terminal being in an uplink synchronization state and the physical uplink shared channel (PUSCH) resource being invalid, transmit the data to the base station through a random access channel.

[0031] In one embodiment, the transmission module is further configured to:

[0032] Transmit the data to the base station through a two-step random access access channel or a four-step random access access channel according to the random access configuration of the terminal.

[0033] In one embodiment, the transmission module is further configured to:

[0034] In response to determining that the terminal supports two-step random access according to the random access configuration, transmit the data to the base station through the two-step random access access channel.

[0035] In one embodiment, the transmission module is further configured to:

[0036] In response to determining that the terminal does not support two-step random access according to the random access configuration, transmit the data to the base station through the four-step random access access channel.

[0037] In one embodiment, the determination module is further configured to:

[0038] Determine that the terminal is in an uplink synchronization state in response to the Time Alignment Timer maintained by the terminal being valid;

[0039] Or,

[0040] Determine that the terminal is in a non - uplink synchronization state in response to the Time Alignment Timer maintained by the terminal being invalid.

[0041] In one embodiment, the determining module is further configured to:

[0042] Determine that the Physical Uplink Shared Channel (PUSCH) resource is valid in response to the configured Grant Timer being valid;

[0043] Or,

[0044] Determine that the Physical Uplink Shared Channel (PUSCH) resource is invalid in response to the configured Grant Timer being invalid.

[0045] In one embodiment, the sending module is further configured to send data and the terminal identifier of the terminal to the base station on the Physical Uplink Shared Channel (PUSCH) resource.

[0046] In one embodiment, the sending module is further configured to: The terminal identifier includes: the Inactive Radio Network Temporary Identifier (I - RNTI) of the terminal.

[0047] According to a third aspect of the embodiments of the present disclosure, there is provided a communication device, including:

[0048] A processor;

[0049] A memory for storing executable instructions of the processor;

[0050] Wherein, the processor is configured to: when running the executable instructions, implement the method described in any embodiment of the present disclosure.

[0051] According to a fourth aspect of the embodiments of the present disclosure, there is provided a computer storage medium storing a computer - executable program, and when the executable program is executed by a processor, the method described in any embodiment of the present disclosure is implemented.

[0052] In an embodiment of the present disclosure, the terminal in the Radio Resource Control (RRC) inactive state determines whether it can send the data to the base station on the Physical Uplink Shared Channel (PUSCH) resource according to the uplink synchronization state of the terminal and the state of the PUSCH resource pre-set by the base station for the terminal. When it is determined that the terminal is in the uplink synchronization state and the PUSCH resource is valid, in the RRC inactive state, the data can be sent to the base station on the PUSCH resource. Compared with the method in which the terminal needs to switch from the RRC inactive state to the RRC connected state before it can send the data to the base station, the signaling overhead is small, the delay is short, and the power consumption is low. Description of the Drawings

[0053] Figure 1 It is a schematic structural diagram of a wireless communication system.

[0054] Figure 2 It is a flowchart of a method for sending data according to an exemplary embodiment.

[0055] Figure 3 It is a flowchart of a method for sending data according to an exemplary embodiment.

[0056] Figure 4 It is a flowchart of a method for sending data according to an exemplary embodiment.

[0057] Figure 5 It is a flowchart of a method for sending data according to an exemplary embodiment.

[0058] Figure 6 It is a flowchart of a method for sending data according to an exemplary embodiment.

[0059] Figure 7 It is a flowchart of a method for sending data according to an exemplary embodiment.

[0060] Figure 8 It is a flowchart of a method for sending data according to an exemplary embodiment.

[0061] Figure 9 It is a block diagram of a device for sending data according to an exemplary embodiment.

[0062] Figure 10 It is a block diagram of a user equipment according to an exemplary embodiment.

[0063] Figure 11 It is a block diagram of a base station according to an exemplary embodiment. Detailed implementation manners

[0064] Here, exemplary embodiments will be described in detail, and examples thereof are shown in the drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementation manners described in the following exemplary embodiments do not represent all implementation manners consistent with the embodiments of the present disclosure. On the contrary, they are merely examples of devices and methods consistent with some aspects of the embodiments of the present disclosure as detailed in the appended claims.

[0065] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments, and are not intended to limit the embodiments of the present disclosure. The singular forms "a" and "the" used in the embodiments of the present disclosure and the appended claims are also intended to include the plural forms, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" as used herein refers to and includes any or all possible combinations of one or more of the associated listed items.

[0066] It should be understood that although the terms first, second, third, etc. may be used in the embodiments of the present disclosure to describe various information, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of the embodiments of the present disclosure, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "when" or "while" or "in response to determining".

[0067] Please refer to Figure 1 , which shows a schematic structural diagram of a wireless communication system provided by the embodiments of the present disclosure. As Figure 1 shown, the wireless communication system is a communication system based on cellular mobile communication technology, and the wireless communication system may include: a plurality of user equipments 110 and a plurality of base stations 120.

[0068] Among them, the user equipment 110 can be a device that provides voice and / or data connectivity to the user. The user equipment 110 can communicate with one or more core networks via a Radio Access Network (RAN). The user equipment 110 can be an Internet of Things (IoT) user equipment, such as a sensor device, a mobile phone (or "cellular" phone), and a computer with an IoT user equipment. For example, it can be a fixed, portable, pocket-sized, handheld, computer-integrated, or vehicle-mounted device. For example, a Station (STA), subscriber unit, subscriber station, mobile station, mobile, remote station, access point, remote terminal, access terminal, user terminal, user agent, user device, or user equipment. Or, the user equipment 110 can also be a device of an unmanned aerial vehicle. Or, the user equipment 110 can also be a vehicle-mounted device, such as a vehicle computer with wireless communication function, or a wireless user equipment external to the vehicle computer. Or, the user equipment 110 can also be a roadside device, such as a street lamp, signal lamp, or other roadside device with wireless communication function, etc.

[0069] The base station 120 can be a network-side device in a wireless communication system. Among them, the wireless communication system can be a 4th generation mobile communication (4G) system, also known as the Long Term Evolution (LTE) system; or, the wireless communication system can also be a 5G system, also known as the New Radio system or 5G NR system. Or, the wireless communication system can also be the next-generation system of the 5G system. Among them, the access network in the 5G system can be called the NG-RAN (New Generation - Radio Access Network).

[0070] Among them, the base station 120 may be an evolved Node B (eNB) adopted in a 4G system. Alternatively, the base station 120 may also be a gNode B (gNB) with a centralized distributed architecture adopted in a 5G system. When the base station 120 adopts a centralized distributed architecture, it generally includes a central unit (CU) and at least two distributed units (DUs). A protocol stack of the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Media Access Control (MAC) layer is provided in the central unit; a Physical (PHY) layer protocol stack is provided in the distributed unit. The specific implementation manner of the base station 120 is not limited in the embodiments of the present disclosure.

[0071] A wireless connection can be established between the base station 120 and the user equipment 110 through a wireless air interface. In different embodiments, the wireless air interface is a wireless air interface based on the fourth-generation mobile communication network technology (4G) standard; alternatively, the wireless air interface is a wireless air interface based on the fifth-generation mobile communication network technology (5G) standard, such as the new air interface; or the wireless air interface may also be a wireless air interface based on the next-generation mobile communication network technology standard of 5G.

[0072] In some embodiments, an E2E (End to End) connection can also be established between user equipments 110. For example, in vehicle-to-everything (V2X) communication, scenarios such as vehicle-to-vehicle (V2V) communication, vehicle-to-Infrastructure (V2I) communication, and vehicle-to-pedestrian (V2P) communication.

[0073] Here, the above user equipment can be regarded as the terminal equipment in the following embodiments.

[0074] In some embodiments, the above wireless communication system may further include a network management device 130.

[0075] A plurality of base stations 120 are respectively connected to a network management device 130. Among them, the network management device 130 may be a core network device in a wireless communication system. For example, the network management device 130 may be a Mobility Management Entity (MME) in an Evolved Packet Core (EPC). Alternatively, the network management device may also be other core network devices, such as a Serving GateWay (SGW), a Public Data Network GateWay (PGW), a Policy and Charging Rules Function (PCRF), or a Home Subscriber Server (HSS), etc. The implementation form of the network management device 130 is not limited in the embodiments of the present disclosure.

[0076] To facilitate the understanding of any embodiment of the present disclosure, first, a method for transmitting data will be described through an embodiment.

[0077] When the terminal is in the Radio Resource Control (RRC) inactive state, it can transmit small data to the base station. In one embodiment, the terminal can transmit uplink small data on a 4-step access Random Access Channel (RACH) or a 2-step access Random Access Channel (RACH).

[0078] In one embodiment, when the terminal is in the Radio Resource Control (RRC) connected state, maintaining uplink synchronization is mainly achieved by maintaining a Time Alignment Timer. The timing time of the Time Alignment Timer can be 0.1s, 0.75s, 1.28s, 1.92s, 2.5s, 5.1s, 10.2s, etc.

[0079] In one embodiment, when the Time Alignment Timer is running (or valid), the terminal confirms that the uplink transmission is synchronous, and the terminal can transmit data to the base station. When the Time Alignment Timer stops running (or becomes invalid), the terminal confirms that the uplink transmission is out of sync. At this time, in order to reduce wireless communication conflicts, the terminal cannot transmit data to the base station. The terminal can only transmit a preamble random access to the terminal and then transmit data.

[0080] In one embodiment, when the terminal is in the Radio Resource Control (RRC) connected state, the base station realizes uplink authorization for the terminal by sending activation information once. In the case that the terminal does not receive deactivation information, it will always use the radio resources indicated by the first uplink authorization for uplink transmission. The process of uplink authorization includes configuring resources in the Configured Uplink Grant field of the Information Element (IE).

[0081] In one embodiment, configuring the uplink grant includes configuring grant type 1. When configured as grant type 1, the configuration of the Configured Uplink Grant field includes parameters related to radio resources such as time-domain resources, frequency-domain resources, modulation and coding schemes, antenna ports, and demodulation reference signals. Here, the valid time of the configured resources can be achieved by maintaining the configuredGrantTimer.

[0082] When a terminal in the Radio Resource Control (RRC) inactive state needs to transmit small data and the Timing Advance (TA) is valid, it can select the configured radio resources to send the small data.

[0083] Here, it should be noted that small data can be data with the number of occupied bits or bytes less than the set threshold. For example, small data is data with the number of occupied bits less than 25 bits. Here, small data can be a heartbeat data packet or an authentication data packet.

[0084] As Figure 2 shown, a method for sending data is provided in this embodiment. Among them, when applied to a terminal, the method includes:

[0085] Step 21, determine the uplink synchronization state of the terminal and the state of the Physical Uplink Shared Channel (PUSCH) resources pre-configured by the base station for the terminal.

[0086] Here, the terminal can be, but is not limited to, a mobile phone, a wearable device, a vehicle-mounted terminal, a RoadSide Unit (RSU), a smart home terminal, an industrial sensing device, and / or a medical device, etc.

[0087] In one embodiment, the uplink synchronization state of the terminal includes being in the uplink synchronization state and being in the non-uplink synchronization state.

[0088] In one embodiment, the base station may configure a first timer for each terminal through Radio Resource Control (RRC) signaling, and the terminal determines whether it is in the uplink synchronization state or the non-uplink synchronization state according to the timing status of the first timer.

[0089] In one embodiment, when the first timer is running and has not timed out, the terminal is in the uplink synchronization state. When the first timer times out, the uplink synchronization state of the terminal becomes invalid. Before the first timer is restarted, the terminal is in the non-uplink synchronization state.

[0090] In one embodiment, the first timer starts timing when the terminal is in the Radio Resource Control (RRC) connected state, and continues to accumulate time until it times out after the terminal switches to the Radio Resource Control (RRC) inactive state.

[0091] In another embodiment, the first timer starts timing after the terminal switches to the Radio Resource Control (RRC) inactive state.

[0092] In one embodiment, the terminal periodically receives a Time Advance (TA) command sent by the base station, and each Time Advance (TA) corresponds to a valid duration. After the terminal receives the Time Advance (TA) command sent by the base station each time, it resets the first timer to zero and sets the duration to the valid duration of the Time Advance (TA). After the first timer times out, the uplink synchronization state of the terminal becomes invalid. If the terminal fails to receive any Time Advance (TA) commands, then the terminal determines that it is in the non-uplink synchronization state. At this time, the terminal can no longer perform uplink data transmission, but needs to go through a random access process to make the terminal in the uplink synchronization state and then perform data transmission.

[0093] In one embodiment, the base station may pre-configure Physical Uplink Shared Channel (PUSCH) resources for the terminal through Radio Resource Control (RRC) signaling. Here, the Physical Uplink Shared Channel (PUSCH) resources include time domain resources and frequency domain resources.

[0094] In one embodiment, the base station may pre-allocate and inform the terminal of multiple grant-free Physical Uplink Shared Channel (PUSCH) resources. In one embodiment, when the terminal has an uplink data transmission requirement, it can select at least one grant-free Physical Uplink Shared Channel (PUSCH) resource from the multiple grant-free Physical Uplink Shared Channel (PUSCH) resources pre-allocated by the base station to send uplink data.

[0095] In one embodiment, the state of the Physical Uplink Shared Channel (PUSCH) resources includes the state where the Physical Uplink Shared Channel (PUSCH) resources are valid and the state where the Physical Uplink Shared Channel (PUSCH) resources are invalid.

[0096] In one embodiment, the base station may configure a second timer for each terminal through Radio Resource Control (RRC) signaling, and the terminal determines whether the Physical Uplink Shared Channel (PUSCH) resource is in a valid state or an invalid state according to the timing status of the second timer.

[0097] In one embodiment, when the second timer is running and has not timed out, the Physical Uplink Shared Channel (PUSCH) resource is in a valid state. When the second timer times out, the Physical Uplink Shared Channel (PUSCH) resource is in an invalid state.

[0098] In one embodiment, the second timer starts timing when the terminal is in the Radio Resource Control (RRC) connected state, and continues to accumulate time until it times out after the terminal switches to the Radio Resource Control (RRC) inactive state.

[0099] In another embodiment, the second timer starts timing after the terminal switches to the Radio Resource Control (RRC) inactive state.

[0100] Step 22: In response to the terminal being in the uplink synchronization state and the Physical Uplink Shared Channel (PUSCH) resource being valid, send data to the base station on the Physical Uplink Shared Channel (PUSCH) resource, where the data is the data of the terminal in the Radio Resource Control (RRC) inactive state.

[0101] In one embodiment, the terminal is a terminal in the Radio Resource Control (RRC) inactive state.

[0102] In one embodiment, the terminal determines the state of the Physical Uplink Shared Channel (PUSCH) resource based on the running condition of the second timer. Here, when the second timer is running and has not timed out, it is determined that the Physical Uplink Shared Channel (PUSCH) resource is in a valid state.

[0103] In one embodiment, when the terminal in the Radio Resource Control (RRC) inactive state is in the uplink synchronization state, the Physical Uplink Shared Channel (PUSCH) resource is valid, and when the terminal needs to send small data to the base station, it sends data to the base station on the Physical Uplink Shared Channel (PUSCH) resource in the Radio Resource Control (RRC) inactive state.

[0104] In one embodiment, small data is data whose number of bits occupied is less than a set threshold. In one embodiment, the set threshold may be 25 bits. For example, the small data may be a heartbeat data packet or an authentication data packet.

[0105] In one embodiment, sending data to the base station on a Physical Uplink Shared Channel (PUSCH) resource means that the terminal sends data to the base station when it is in the Radio Resource Control (RRC) Inactive state.

[0106] In the embodiments of the present disclosure, a terminal in the Radio Resource Control (RRC) Inactive state determines whether it can send data to the base station on a Physical Uplink Shared Channel (PUSCH) resource according to the terminal's uplink synchronization state and the state of the Physical Uplink Shared Channel (PUSCH) resource pre-set by the base station for the terminal. When it is determined that the terminal is in the uplink synchronization state and the Physical Uplink Shared Channel (PUSCH) resource is valid, in the Radio Resource Control (RRC) Inactive state, data can be sent to the base station on the Physical Uplink Shared Channel (PUSCH) resource. Compared with the method where the terminal needs to switch from the Radio Resource Control (RRC) Inactive state to the Radio Resource (RRC) Connected state before it can send data to the base station, the signaling overhead is small, the latency is short, and the power consumption is low.

[0107] As Figure 3 shown, in this embodiment, a method for sending data is further provided, where the method further includes:

[0108] Step 31, in response to the terminal being in the uplink synchronization state and the Physical Uplink Shared Channel (PUSCH) resource being invalid, send data to the base station through the Random Access Channel.

[0109] In one embodiment, the terminal is a terminal in the Radio Resource Control (RRC) Inactive state.

[0110] In one embodiment, the terminal determines the state of the Physical Uplink Shared Channel (PUSCH) resource based on the running condition of a second timer. Here, when the second timer runs and times out, it is determined that the (PUSCH) resource is in an invalid state. The Random Access Channel includes a two-step Random Access Channel and a four-step Random Access Channel. The access latency of the two-step Random Access is less than that of the four-step Random Access. That is, the access rate of the two-step Random Access is greater than that of the four-step Random Access.

[0111] Here, when the terminal is in the uplink synchronization state and the Physical Uplink Shared Channel (PUSCH) resource is invalid, data can also be sent to the base station through the Random Access Channel. Multiple ways for a terminal in the Radio Resource Control (RRC) Inactive state to send data to the base station are provided. In this way, the situation where data cannot be sent to the base station due to the single way of sending data when the Physical Uplink Shared Channel (PUSCH) resource is invalid is reduced.

[0112] In one embodiment, when the terminal's service is a low-latency and / or high-rate service, data is sent to the base station through the two-step Random Access Channel.

[0113] In one embodiment, the low-latency and / or high-rate services may be services such as ultra-high-definition video, video conferencing, 3D games, etc. in the enhanced mobile broadband scenario.

[0114] In another embodiment, the low-latency and / or high-rate services may also be services such as vehicle-to-everything (V2X), industrial control, remote medical treatment, etc. in the low-latency and high-reliability scenario.

[0115] As Figure 4 shown, in this embodiment, a method for sending data is further provided. Among them, in step 31, sending data to the base station through the random access channel includes:

[0116] Step 41: Send data to the base station through a two-step random access channel or a four-step random access channel according to the random access configuration of the terminal.

[0117] In one embodiment, the random access configuration may configure the terminal to support two-step random access and / or configure the terminal to support four-step random access.

[0118] In one embodiment, the terminal may receive a system message carrying random access configuration information sent by the base station, and determine the random access configuration information according to the system message.

[0119] As Figure 5 shown, in this embodiment, a method for sending data is further provided. Among them, in step 41, sending data to the base station through a two-step random access channel or a four-step random access channel according to the random access configuration of the terminal includes:

[0120] Step 51: In response to determining that the terminal supports two-step random access according to the random access configuration, send data to the base station through the two-step random access channel.

[0121] Here, since the latency of transmitting data through the two-step random access channel is shorter and the rate is faster than that of transmitting data through the four-step random access channel, the efficiency of transmitting data can be improved.

[0122] In one embodiment, sending data to the base station through a two-step random access channel or a four-step random access channel according to the random access configuration of the terminal further includes:

[0123] In response to determining that the terminal does not support two-step random access according to the random access configuration, send data to the base station through the four-step random access channel.

[0124] Here, when the terminal is in the uplink synchronization state, the physical uplink shared channel (PUSCH) resource fails, and the terminal does not support two-step random access, data can also be sent to the base station through a four-step random access channel. This provides multiple ways for a terminal in the radio resource control (RRC) inactive state to send data to the base station. In this way, the situation where data cannot be sent to the base station due to the failure of the physical uplink shared channel (PUSCH) resource and the single way of sending data is reduced.

[0125] As Figure 6 shown, this embodiment also provides a method for sending data. Among them, in step 22, determining the uplink synchronization state of the terminal and the state of the physical uplink shared channel (PUSCH) resource pre-configured by the base station for the terminal includes:

[0126] Step 61, in response to the time alignment timer (TimeAlignmentTimer) maintained by the terminal being valid, determining that the terminal is in the uplink synchronization state;

[0127] Or,

[0128] In response to the time alignment timer maintained by the terminal failing, determining that the terminal is not in the uplink synchronization state.

[0129] In one embodiment, the base station can configure a time alignment timer for each terminal through radio resource control (RRC) signaling, and the terminal determines whether the terminal is in the uplink synchronization state or not in the uplink synchronization state according to the timing state of the time alignment timer.

[0130] In one embodiment, when the time alignment timer is running and has not timed out, the terminal is in the uplink synchronization state. When the time alignment timer times out, the uplink synchronization state of the terminal fails. When the time alignment timer has not been started, the terminal is not in the uplink synchronization state.

[0131] In one embodiment, the time alignment timer starts timing when the terminal is in the radio resource control (RRC) connected state, and continues to accumulate timing until it times out after the terminal switches to the radio resource control (RRC) inactive state.

[0132] In another embodiment, the time alignment timer starts timing after the terminal switches to the radio resource control (RRC) inactive state.

[0133] In one embodiment, the terminal periodically receives a Time Advance (TA) command sent by the base station, and each Time Advance (TA) corresponds to a valid duration. After the terminal receives the TA command sent by the base station each time, it resets the time correction timer to zero and sets the duration to the valid duration of the TA. After the time correction timer times out, if the terminal fails to receive any TA command, then the terminal determines that it is in a non-uplink synchronization state. At this time, the terminal cannot perform uplink data transmission anymore, but needs to go through a random access process to make the terminal in an uplink synchronization state and then perform data transmission.

[0134] As Figure 7 shown, in this embodiment, a method for sending data is further provided. Among them, in step 21, determining the uplink synchronization state of the terminal and the state of the Physical Uplink Shared Channel (PUSCH) resources pre-configured by the base station for the terminal includes:

[0135] Step 71, in response to the configuredGrantTimer being valid, determining that the Physical Uplink Shared Channel (PUSCH) resources are valid;

[0136] Or,

[0137] In response to the configuredGrantTimer expiring, determining that the Physical Uplink Shared Channel (PUSCH) resources are invalid.

[0138] In one embodiment, the base station can configure a configuredGrantTimer for each terminal through Radio Resource Control (RRC) signaling, and the terminal determines whether the (PUSCH) resources are in a valid state or an invalid state according to the timing status of the configuredGrantTimer.

[0139] In one embodiment, when the configuredGrantTimer is running and has not timed out, the Physical Uplink Shared Channel (PUSCH) resources are in a valid state. When the configuredGrantTimer times out, the Physical Uplink Shared Channel (PUSCH) resources are in an invalid state.

[0140] In one embodiment, the configuredGrantTimer starts timing when the terminal is in the Radio Resource Control (RRC) connected state, and continues to accumulate timing until it times out after the terminal switches to the Radio Resource Control (RRC) inactive state.

[0141] In another embodiment, the configuredGrantTimer starts timing after the terminal switches to the Radio Resource Control (RRC) inactive state.

[0142] In one embodiment, the timing duration configuration of the configured grant timer may be implemented in the Information Element (IE) configured uplink grant field.

[0143] As Figure 8 shown, this embodiment also provides a method for sending data. In step 22, sending data to the base station on the Physical Uplink Shared Channel (PUSCH) resource includes:

[0144] Step 81, sending data and the terminal identifier of the terminal to the base station on the Physical Uplink Shared Channel (PUSCH) resource.

[0145] In one embodiment, the terminal identifier is an identifier for differentiating terminal identities. Different terminals have different terminal identifiers.

[0146] In one embodiment, after receiving the data, the base station can confirm the terminal that sent the data according to the terminal identifier.

[0147] In one embodiment, the terminal identifier includes: the Inactive Radio Network Temporary Identifier (I-RNTI) of the terminal.

[0148] In one embodiment, the Inactive Radio Network Temporary Identifier occupies 24 or 40 bits.

[0149] As Figure 9 shown, this embodiment of the present disclosure provides a device for sending data. Applied to a terminal, the device includes a determination module 91 and a sending module 92; where

[0150] The determination module 91 is configured to determine the uplink synchronization state of the terminal and the state of the Physical Uplink Shared Channel (PUSCH) resource pre-configured by the base station for the terminal;

[0151] The sending module 92 is configured to, in response to the terminal being in the uplink synchronization state and the Physical Uplink Shared Channel (PUSCH) resource being valid, send data to the base station on the Physical Uplink Shared Channel (PUSCH) resource, where the data includes: data of the terminal in the Radio Resource Control (RRC) inactive state.

[0152] In one embodiment, the sending module 92 is further configured to:

[0153] In response to the terminal being in the uplink synchronization state and the Physical Uplink Shared Channel (PUSCH) resource being invalid, send data to the base station through the random access channel.

[0154] In one embodiment, the sending module 92 is further configured to:

[0155] Send data to the base station through a two-step random access access channel or a four-step random access access channel according to the random access configuration of the terminal.

[0156] In one embodiment, the sending module 92 is further configured to:

[0157] In response to determining that the terminal supports two-step random access according to the random access configuration, send data to the base station through a two-step random access access channel.

[0158] In one embodiment, the sending module 92 is further configured to:

[0159] In response to determining that the terminal does not support two-step random access according to the random access configuration, send data to the base station through a four-step random access access channel.

[0160] In one embodiment, the determining module 91 is further configured to:

[0161] In response to the time alignment timer (TimeAlignmentTimer) maintained by the terminal being valid, determine that the terminal is in the uplink synchronization state;

[0162] Or,

[0163] In response to the time alignment timer maintained by the terminal being invalid, determine that the terminal is in the non-uplink synchronization state.

[0164] In one embodiment, the determining module 91 is further configured to:

[0165] In response to the configured grant timer being valid, determine that the physical uplink shared channel (PUSCH) resource is valid;

[0166] Or,

[0167] In response to the configured grant timer being invalid, determine that the physical uplink shared channel (PUSCH) resource is invalid.

[0168] In one embodiment, the sending module 92 is further configured to send data and the terminal identifier of the terminal to the base station on the physical uplink shared channel (PUSCH) resource.

[0169] In one embodiment, the sending module 92 is further configured to: The terminal identifier includes: the inactive state radio network temporary identifier (I-RNTI) of the terminal.

[0170] Regarding the device in the above embodiments, the specific manners in which each module performs operations have been described in detail in the embodiments related to the method, and will not be elaborated herein.

[0171] Embodiments of the present disclosure provide a communication device, which includes:

[0172] A processor;

[0173] A memory for storing executable instructions of the processor;

[0174] Wherein, the processor is configured to: when running the executable instructions, implement the method applied to any embodiment of the present disclosure.

[0175] Wherein, the processor may include various types of storage media, and the storage media is a non-temporary computer storage media, which can continue to memorize and store the information thereon after the communication device loses power.

[0176] The processor may be connected to the memory through a bus or the like for reading the executable program stored on the memory.

[0177] Embodiments of the present disclosure further provide a computer storage medium, wherein the computer storage medium stores a computer executable program, and when the executable program is executed by a processor, the method applied to any embodiment of the present disclosure is implemented..

[0178] Regarding the device in the above embodiments, the specific manners in which each module performs operations have been described in detail in the embodiments related to the method, and will not be elaborated herein.

[0179] Figure 10 FIG. is a block diagram of a user equipment (UE) 800 shown according to an exemplary embodiment. For example, the user equipment 800 may be a mobile phone, a computer, a digital broadcast user equipment, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0180] Referring to Figure 10 , the user equipment 800 may include one or more of the following components: a processing component 802, a memory 804, a power component 806, a multimedia component 808, an audio component 810, an input / output (I / O) interface 812, a sensor component 814, and a communication component 816.

[0181] The processing component 802 generally controls the overall operation of the user device 800, such as operations associated with display, telephone calls, data communication, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the above methods. In addition, the processing component 802 may include one or more modules to facilitate the interaction between the processing component 802 and other components. For example, the processing component 802 may include a multimedia module to facilitate the interaction between the multimedia component 808 and the processing component 802.

[0182] The memory 804 is configured to store various types of data to support the operation of the user device 800. Examples of such data include instructions for any application or method operating on the user device 800, contact data, phone book data, messages, pictures, videos, etc. The memory 804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disks, or optical disks.

[0183] The power component 806 provides power to various components of the user device 800. The power component 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the user device 800.

[0184] The multimedia component 808 includes a screen that provides an output interface between the user device 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors can not only sense the boundaries of touch or swipe actions, but also detect the duration and pressure associated with the touch or swipe operation. In some embodiments, the multimedia component 808 includes a front camera and / or a rear camera. When the user device 800 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera can receive external multimedia data. Each of the front camera and the rear camera can be a fixed optical lens system or have a focal length and optical zoom capabilities.

[0185] The audio component 810 is configured to output and / or input audio signals. For example, the audio component 810 includes a microphone (MIC), which is configured to receive external audio signals when the user device 800 is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals can be further stored in the memory 804 or transmitted via the communication component 816. In some embodiments, the audio component 810 further includes a speaker for outputting audio signals.

[0186] The I / O interface 812 provides an interface between the processing component 802 and a peripheral interface module, and the peripheral interface module can be a keyboard, a click wheel, buttons, etc. These buttons can include but are not limited to: a home button, a volume button, a start button, and a lock button.

[0187] The sensor component 814 includes one or more sensors for providing status assessments of various aspects of the user device 800. For example, the sensor component 814 can detect the on / off state of the user device 800, the relative positioning of components, such as the display and keypad of the user device 800. The sensor component 814 can also detect a change in the position of the user device 800 or a component of the user device 800, the presence or absence of contact between the user and the user device 800, the orientation or acceleration / deceleration of the user device 800, and the temperature change of the user device 800. The sensor component 814 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor component 814 can also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor component 814 can further include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0188] The communication component 816 is configured to facilitate communication between the user device 800 and other devices in a wired or wireless manner. The user device 800 can access a wireless network based on a communication standard, such as WiFi, 2G, or 3G, or a combination thereof. In an exemplary embodiment, the communication component 816 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 816 further includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0189] In an exemplary embodiment, the user equipment 800 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components for performing the above method.

[0190] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 804 including instructions, and the above instructions can be executed by a processor 820 of the user equipment 800 to complete the above method. For example, the non-transitory computer-readable storage medium may be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device, etc.

[0191] As Figure 11 shown, an embodiment of the present disclosure shows a structure of a base station. For example, the base station 900 may be provided as a network-side device. Referring to Figure 11 FIG. [FIGURE NUMBER NOT PROVIDED], the base station 900 includes a processing component 922, which further includes one or more processors, and memory resources represented by a memory 932 for storing instructions executable by the processing component 922, such as application programs. The application programs stored in the memory 932 may include one or more modules each corresponding to a set of instructions. In addition, the processing component 922 is configured to execute instructions to perform any of the above methods for the foregoing application in the base station, for example, the method shown in Figures 2 - 8 FIG. [FIGURE NUMBER NOT PROVIDED].

[0192] The base station 900 may further include a power component 926 configured to perform power management of the base station 900, a wired or wireless network interface 950 configured to connect the base station 900 to a network, and an input / output (I / O) interface 958. The base station 900 may operate based on an operating system stored in the memory 932, such as Windows Server TM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, or the like.

[0193] Those skilled in the art will readily conceive of other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses, or adaptations of the present invention, which follow the general principles of the present invention and include known common knowledge or conventional technical means in the technical field not disclosed in the present disclosure. The specification and embodiments are only to be considered as exemplary, and the true scope and spirit of the present invention are pointed out by the following claims.

[0194] It should be understood that the present invention is not limited to the exact structures described above and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present invention is only limited by the appended claims.

Claims

1. A method for sending data, wherein, Applied to a terminal, the method includes: Determine the uplink synchronization state of the terminal and the state of the grant-free physical uplink shared channel (PUSCH) resources pre-configured by the base station for the terminal, where the terminal is a terminal in the radio resource control (RRC) inactive state; In response to the terminal being in the uplink synchronization state and the grant-free PUSCH resources being valid, send data to the base station on the grant-free PUSCH resources, where the data is data with the number of occupied bit positions less than a set threshold; In response to the terminal being in the uplink synchronization state and the grant-free PUSCH resources being invalid, send the data to the base station through the random access channel; The determining the state of the grant-free PUSCH resources pre-configured by the base station for the terminal includes: Determine whether the grant-free PUSCH resources are valid or invalid based on the timing state of a second timer; where the second timer starts timing when the terminal is in the RRC connected state, and accumulates timing after the terminal switches to the RRC inactive state until the timing times out.

2. The method according to claim 1, wherein The sending the data to the base station through the random access channel includes: According to the random access configuration of the terminal, send the data to the base station through a two-step random access channel or a four-step random access channel.

3. The method according to claim 2, wherein, The sending the data to the base station through a two-step random access channel or a four-step random access channel according to the random access configuration of the terminal includes: In response to determining that the terminal supports two-step random access according to the random access configuration, send the data to the base station through the two-step random access channel.

4. The method according to claim 3, wherein The sending the data to the base station through a two-step random access channel or a four-step random access channel according to the random access configuration of the terminal further includes: In response to determining that the terminal does not support two-step random access according to the random access configuration, send the data to the base station through the four-step random access channel.

5. The method according to claim 1, wherein The determining the uplink synchronization state of the terminal includes: In response to the time alignment timer (TimeAlignmentTimer) maintained by the terminal being valid, determine that the terminal is in the uplink synchronization state; Or, In response to the time alignment timer maintained by the terminal being invalid, determine that the terminal is in the non-uplink synchronization state.

6. The method according to claim 1, wherein, The determining the state of the grant-free PUSCH resources pre-configured by the base station for the terminal includes: In response to the configured grant timer (configuredGrantTimer) being valid, determine that the grant-free PUSCH resources are valid; Or, In response to the configured grant timer being invalid, determine that the grant-free PUSCH resources are invalid.

7. The method according to claim 1, wherein, The sending data to the base station on the grant-free PUSCH resources includes: Send data and the terminal identifier of the terminal to the base station on the grant-free PUSCH resources.

8. The method according to claim 7, wherein, The terminal identifier includes: the inactive state radio network temporary identifier (I-RNTI) of the terminal.

9. A device for sending data, wherein, Applied to a terminal, the device includes a determination module and a sending module; where The determining module is configured to determine the uplink synchronization state of the terminal and the state of the grant-free physical uplink shared channel (PUSCH) resources pre-configured by the base station for the terminal, where the terminal is a terminal in the radio resource control (RRC) inactive state; The sending module is configured to, in response to the terminal being in the uplink synchronization state and the grant-free PUSCH resources being valid, send data to the base station on the grant-free PUSCH resources, where the data is data with the number of occupied bit positions less than a set threshold; in response to the terminal being in the uplink synchronization state and the grant-free PUSCH resources being invalid, send the data to the base station through a random access channel; The determining module is further configured to: determine whether the grant-free PUSCH resources are valid or invalid based on the timing state of a second timer; where the second timer starts timing when the terminal is in the RRC connected state, and accumulates timing until the timing expires after the terminal switches to the RRC inactive state.

10. The apparatus according to claim 9, wherein, The sending module is further configured to: Send the data to the base station through a two-step random access access channel or a four-step random access access channel according to the random access configuration of the terminal.

11. The apparatus according to claim 10, wherein, The sending module is further configured to: In response to determining according to the random access configuration that the terminal supports two-step random access, send the data to the base station through the two-step random access access channel.

12. The device according to claim 11, wherein, The sending module is further configured to: In response to determining according to the random access configuration that the terminal does not support two-step random access, send the data to the base station through the four-step random access access channel.

13. The apparatus according to claim 9, wherein The determining module is further configured to: In response to the time alignment timer (TimeAlignmentTimer) maintained by the terminal being valid, determine that the terminal is in the uplink synchronization state; Or, In response to the time alignment timer maintained by the terminal being invalid, determine that the terminal is in a non-uplink synchronization state.

14. The apparatus according to claim 9, wherein The determining module is further configured to: In response to the configured grant timer (configuredGrantTimer) being valid, determine that the grant-free PUSCH resources are valid; Or, In response to the configured grant timer being invalid, determine that the grant-free PUSCH resources are invalid.

15. The apparatus according to claim 9, wherein, The sending module is further configured to send data and the terminal identifier of the terminal to the base station on the grant-free PUSCH resources.

16. The apparatus according to claim 15, wherein, The sending module is further configured to: The terminal identifier includes: the inactive state radio network temporary identifier (I-RNTI) of the terminal.

17. A communication device, wherein, Including: An antenna; A memory; A processor, connected to the antenna and the memory respectively, and configured to control the transceiver of the antenna by executing computer-executable instructions stored on the memory, and be able to implement the method provided in any one of claims 1 to 8.

18. A computer storage medium storing computer-executable instructions, which can implement the method provided in any one of claims 1 to 8 after being executed by a processor.

Images