Wireless communication method and device
By limiting the usage time of dedicated resources and the use of shared resources in the terminal device, the problem of resource waste during small data transmission in the RRC_INACTIVE state is solved, and the improvement of resource utilization and data transmission are achieved.
Patent Information
- Application Number
- CN202280002816.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-05-06
- Publication Date
- 2025-01-03
- Estimated Expiration
- 2042-05-06
AI Technical Summary
While the terminal device is in the RRC_INACTIVE state, how to effectively perform small data transmission to avoid resource waste and ensure data transmission, the prior art lacks clear methods.
By limiting the duration of the terminal device using dedicated resources, it only uses dedicated resources for small data transmission at some time, and uses shared resources for transmission at other times, thereby ensuring data transmission to a certain extent and avoiding resource waste. The specific implementation is that the network device sends a first information to the terminal device, indicating that the first timer is used to limit the usage time of the dedicated resource, the timer is less than the time of the second timer, and the second timer is used to instruct the terminal device to perform small data. Total duration of transmission.
It realizes the use of dedicated resources for small data transmission during the terminal equipment for part of the time, improves resource utilization, avoids resource waste, and ensures the smooth progress of data transmission.
Smart Images

Figure CN115316025B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communication technology, and more specifically, to a method and device for wireless communication. Background Art
[0002] In order to save the signaling overhead of the terminal device, the communication system allows the terminal device to perform small data transmission (SDT) in the inactive state of radio resource control (RRC). However, there is currently no clear way to ensure the data transmission of the terminal device as much as possible and avoid resource waste when the terminal device performs SDT. Summary of the invention
[0003] In view of the above problems, the present application provides a method and device for wireless communication. The following introduces various aspects involved in the embodiments of the present application.
[0004] In a first aspect, a method for wireless communication is provided, comprising: a terminal device receives first information sent by a network device, the first information is used to indicate a first timer, the first timer is used to indicate the duration of SDT using a first transmission resource, wherein the duration of the first timer is less than the duration of a second timer, and the second timer is used to indicate the duration of SDT of the terminal device.
[0005] In a second aspect, a method for wireless communication is provided, including: a network device sends first information to a terminal device, the first information is used to indicate a first timer, the first timer is used to indicate the duration of SDT using a first transmission resource, wherein the duration of the first timer is less than the duration of a second timer, and the second timer is used to indicate the duration of SDT for the terminal device.
[0006] In a third aspect, a terminal device is provided, comprising: a receiving unit, used to receive first information sent by a network device, the first information being used to indicate a first timer, the first timer being used to indicate the duration of SDT using a first transmission resource, wherein the duration of the first timer is less than the duration of a second timer, and the second timer being used to indicate the duration of SDT of the terminal device.
[0007] In a fourth aspect, a network device is provided, including: a sending unit, used to send first information to a terminal device, the first information is used to indicate a first timer, the first timer is used to indicate the duration of SDT using a first transmission resource, wherein the duration of the first timer is less than the duration of a second timer, and the second timer is used to indicate the duration of SDT for the terminal device.
[0008] In a fifth aspect, a terminal device is provided, comprising a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the terminal device executes the method described in the first aspect.
[0009] In a sixth aspect, a network device is provided, comprising a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the network device executes the method described in the second aspect.
[0010] In a seventh aspect, a device is provided, comprising a processor, configured to call a program from a memory to execute the method described in the first aspect.
[0011] In an eighth aspect, a device is provided, comprising a processor, configured to call a program from a memory to execute the method described in the second aspect.
[0012] In a ninth aspect, a chip is provided, comprising a processor for calling a program from a memory so that a device equipped with the chip executes the method described in the first aspect.
[0013] In a tenth aspect, a chip is provided, comprising a processor for calling a program from a memory so that a device equipped with the chip executes the method described in the second aspect.
[0014] According to an eleventh aspect, a computer-readable storage medium is provided, on which a program is stored, wherein the program enables a computer to execute the method described in the first aspect.
[0015] In a twelfth aspect, a computer-readable storage medium is provided, on which a program is stored, wherein the program enables a computer to execute the method described in the second aspect.
[0016] In a thirteenth aspect, a computer program product is provided, comprising a program, wherein the program enables a computer to execute the method described in the first aspect.
[0017] In a fourteenth aspect, a computer program product is provided, comprising a program, wherein the program enables a computer to execute the method described in the second aspect.
[0018] In a fifteenth aspect, a computer program is provided, wherein the computer program enables a computer to execute the method described in the first aspect.
[0019] In a sixteenth aspect, a computer program is provided, wherein the computer program enables a computer to execute the method described in the second aspect.
[0020] In an embodiment of the present application, by limiting the time period for the terminal device to use dedicated resources (such as the first transmission resource), the terminal device only uses the first transmission resource for SDT part of the time, and at other times, for example, it can use shared resources for SDT, thereby, to a certain extent, both ensuring the data transmission of the terminal device and avoiding waste of resources. BRIEF DESCRIPTION OF THE DRAWINGS
[0021] Figure 1 It is an example diagram of the system architecture of the communication system that can be applied to the embodiments of the present application.
[0022] Figure 2 It is a flowchart of the terminal device switching from the RRC_CONNECTED state to the RRC_INACTIVE state.
[0023] Figure 3 It is a schematic flow chart of performing SDT based on a two-step random access process.
[0024] Figure 4 It is a schematic flow chart of performing SDT based on a four-step random access process.
[0025] Figure 5 It is a schematic flowchart of a wireless communication method provided by an embodiment of the present application.
[0026] Figure 6 It is a schematic flowchart of a wireless communication method provided by another embodiment of the present application.
[0027] Figure 7 This is a schematic flowchart of SDT performed by a terminal device provided in an embodiment of the present application.
[0028] Figure 8 This is a schematic flowchart of SDT performed by a terminal device provided in another embodiment of the present application.
[0029] Fig. 9 It is a structural diagram of a terminal device provided in one embodiment of the present application.
[0030] Fig.10 It is a structural diagram of a network device provided in one embodiment of the present application.
[0031] Fig.11 It is a schematic diagram of the structure of a communication device provided in one embodiment of the present application. DETAILED DESCRIPTION
[0032] The technical solution in this application will be described below in conjunction with the accompanying drawings.
[0033] Figure 1The wireless communication system 100 used in the embodiment of the present application may include a network device 110 and a terminal device 120. The network device 110 may be a device that communicates with the terminal device 120. The network device 110 may provide communication coverage for a specific geographical area and may communicate with the terminal device 120 located in the coverage area.
[0034] Figure 1 One network device and two terminals are shown exemplarily. Optionally, the wireless 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.
[0035] Optionally, the wireless 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.
[0036] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: the fifth generation (5th generation, 5G) system or new radio (new radio, NR), long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), etc. The technical solutions provided by the present application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, etc.
[0037] The terminal device in the embodiment of the present application may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The terminal device in the embodiment of the present application may be a device that provides voice and / or data connectivity to a user, and may be used to connect people, objects and machines, such as a handheld device with wireless connection function, a vehicle-mounted device, etc. The terminal device in the embodiment of the present application can be a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. Optionally, the UE can be used to act as a base station. For example, the UE can act as a scheduling entity that provides sidelink signals between UEs in V2X or D2D, etc. For example, a cellular phone and a car communicate with each other using a sidelink signal. Cellular phones and smart home devices communicate with each other without relaying communication signals through a base station.
[0038] The network device in the embodiment of the present application may be a device for communicating with a terminal device, and the network device may also be referred to as an access network device or a wireless access network device, such as a base station. The network device in the embodiment of the present application may refer to a wireless access network (RAN) node (or device) that connects a terminal device to a wireless network. Base station can broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmission point (TRP), transmission point (TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, base band unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. The base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof. The base station may also refer to a communication module, modem or chip used to be set in the aforementioned device or apparatus. The base station may also be a mobile switching center and a device that performs the base station function in device-to-device D2D, vehicle-to-everything (V2X), machine-to-machine (M2M) communication, a network-side device in a 6G network, and a device that performs the base station function in a future communication system. The base station may support networks with the same or different access technologies. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network equipment.
[0039] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.
[0040] In some deployments, the network device in the embodiments of the present application may refer to a CU or a DU, or the network device includes a CU and a DU. The gNB may also include an AAU.
[0041] The network equipment and terminal equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on the water surface; they can also be deployed on aircraft, balloons and satellites in the air. The embodiments of the present application do not limit the scenarios in which the network equipment and terminal equipment are located.
[0042] It should be understood that the communication devices involved in the present application may be network devices or terminal devices. For example, the first communication device is a network device and the second communication device is a terminal device. For another example, the first communication device is a terminal device and the second communication device is a network device. For another example, the first communication device and the second communication device are both network devices or both terminal devices.
[0043] It should also be understood that all or part of the functions of the communication device in the present application may also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (eg, a cloud platform).
[0044] Currently, the protocol defines three radio resource control (RRC) states of terminal devices: RRC connected (RRC_CONNECTED) state, RRC idle (RRC_IDLE) state and RRC inactive (RRC_INACTIVE) state.
[0045] The RRC_CONNECTED state may refer to the state in which the terminal device is in after completing the random access process but before performing RRC release. An RRC connection exists between the terminal device and a network device (e.g., an access network device). In the RRC_CONNECTED state, the terminal device may perform data transmission with the network device, such as downlink data transmission and / or uplink data transmission. Alternatively, the terminal device may also perform terminal device-specific data channel and / or control channel transmission with the network device to transmit specific information or unicast information of the terminal device.
[0046] The RRC_IDLE state refers to the state of the terminal device when it resides in a cell but does not perform random access. The terminal device usually enters the RRC_IDLE state after being powered on or after RRC is released. In the RRC_IDLE state, there is no RRC connection between the terminal device and the network device (such as the resident network device), the network device does not store the context of the terminal device, and no connection is established between the network device and the core network for the terminal device. If the terminal device needs to enter the RRC_CONNECTED state from the RRC_IDLE state, it is necessary to initiate the RRC connection establishment process.
[0047] The RRC_INACTIVE state is a new state introduced from the perspective of energy saving in order to reduce air interface signaling, quickly restore wireless connections, and quickly restore data services. The RRC_INACTIVE state is a state between the connected state and the idle state. The terminal device has previously entered the RRC_CONNECTED state, and then released the RRC connection, radio bearer, and radio resources with the network device, but the network device saves the context of the terminal device in order to quickly restore the RRC connection. In addition, the connection established between the network device and the core network for the terminal device has not been released, that is, the user plane bearer and control plane bearer between the RAN and the CN are still maintained, that is, there is a CN-NR connection.
[0048] The terminal device can switch between the three RRC states mentioned above. For example, the terminal device can enter the RRC_INACTIVE state from the RRC_CONNECTED state to suspend its session when there is no data transmission for a period of time, and can enter the RRC_CONNECTED state from the RRC_INACTIVE state when there is a session transmission requirement. In addition, the terminal device can also enter the RRC_IDLE state from the RRC_INACTIVE state or the RRC_CONNECTED state.
[0049] Combine the following Figure 2 , the process of switching from the RRC_CONNECTED state to the RRC_INACTIVE state is introduced.
[0050] like Figure 2 As shown, in step S210, the gNB-CU determines that the terminal device enters the RRC_INACTIVE state.
[0051] In step S220, the gNB-CU may send an F1AP UE context release command to the gNB-DU.
[0052] In step S230, the gNB-DU sends an RRC connection release message to the UE. After receiving the RRC connection release message, the UE can release the RRC connection with the gNB and enter the RRC_INACTIVE state.
[0053] In step S240, the gNB-DU sends an F1AP UE context release completion response to the gNB-CU.
[0054] For terminal devices that do not transmit data frequently, the terminal devices can remain in the RRC_INACTIVE state to save power. Before release 16 (Rel-16), terminal devices in the RRC_INACTIVE state did not support data transmission, that is, they did not support the transmission of mobile originated (MO) data and mobile terminated (MT) data. MO data refers to data sent by the terminal device, and the message is transmitted from the terminal device to the network device. MO data can also be called uplink data. MT data refers to data sent by the network device, and the message is transmitted from the network device to the terminal device. MT data can also be called downlink data.
[0055] When MO data or MT data arrives, the terminal device needs to restore the RRC connection and enter the RRC_CONNECTED state. In the RRC_CONNECTED state, the terminal device can transmit MO data or MT data. After the MO data or MT data transmission is completed, the terminal device releases the RRC connection and returns to the RRC_INACTIVE state.
[0056] In the above process, the terminal device needs to switch from the RRC_INACTIVE state to the RRC_CONNECTED state, and then switch from the RRC_CONNECTED state to the RRC_INACTIVE state. Switching between different RRC states will increase the power consumption of the terminal device. However, in some scenarios, the terminal device in the RRC_INACTIVE state needs to transmit some data with a small amount of data and a low transmission frequency (which can be called small packet data). If the terminal device switches to the RRC_CONNECTED state and then performs data transmission, the signaling overhead required for the terminal device to switch the RRC state may even be greater than the overhead required to transmit this data, resulting in unnecessary power consumption and signaling overhead.
[0057] The small data packet in the embodiment of the present application may be, for example, an instant messaging message, a heartbeat packet, periodic data, etc. The embodiment of the present application does not specifically limit the source of the small data packet. As an example, the small data packet may be data from a terminal device application (application, APP). For example, the small data packet may be data from a communication service APP (such as whatsapp, QQ, WeChat, etc.), a heartbeat data packet from an IM, an email client or other APP, a push notification from various applications, etc. As another example, the small data packet may come from data from a non-terminal device application. For example, the small data packet may come from data from a wearable device (such as regular positioning information, etc.), sensor data (such as temperature information and pressure information sent by an industrial wireless sensor regularly or in an event-triggered manner), and regular instrument readings specified in the smart meter and smart meter network transmission protocol (such as 3GPP TS 22.891).
[0058] In order to reduce the power consumption of the terminal device, Rel-17 discusses the SDT scheme in the RRC_INACTIVE state. In this scheme, the terminal device does not need to switch from the RRC_INACTIVE state to the RRC_CONNECTED state for small data transmission, but can perform small data transmission in the RRC_INACTIVE state. The small data transmission of the embodiment of the present application may include uplink small data transmission and downlink small data transmission. The following will mainly describe the uplink small data transmission.
[0059] In the RRC_INACTIVE state, the terminal device can perform SDT according to the resources configured by the network device. There are two ways for the terminal device to perform SDT. One is SDT based on the random access process, and the other is SDT based on the configured grant (CG). The following introduces these two situations respectively.
[0060] SDT based on the random access process may mean that the terminal device may perform SDT during the random access process. The random access method may be a two-step random access process, or a four-step random access process. For the two-step random access process, the terminal device may perform SDT in message 1 (message 1, MSG1). That is, MSG1 of the two-step random access process may be used to carry data. For the four-step random access process, the terminal device may perform SDT in MSG3. That is, MSG3 of the four-step random access process may be used to carry data.
[0061] During the random access process, the resources used by the terminal device to perform SDT may be referred to as RA-SDT resources.
[0062] Combine the following Figure 3 and Figure 4 , the two-step random access process and the four-step random access process are described respectively.
[0063] Figure 3 FIG. 1 is a schematic flow chart of performing SDT in a two-step random access process.
[0064] In step S310, the terminal device sends MSG1 to the network device. The terminal device can send MSG1 on the random access channel (RACH) resource configured by the network device. MSG1 can carry data to be transmitted (or called uplink data or MO data). If MSG1 is used for SDT, the resource for transmitting MSG1 can also be called RA-SDT resource. For example, RA-SDT resource can be RACH resource.
[0065] In step S320, the network device sends MSG2 to the terminal device. The MSG2 may include a response to the data to be transmitted.
[0066] Figure 4 The figure shows a schematic flow chart of performing SDT in a four-step random access process.
[0067] In step S410, the terminal device sends MSG1 to the network device. MSG1 carries a random access preamble.
[0068] In step S420, the network device sends MSG2 to the terminal device. The MSG2 may also be called a random access response (RAR). MSG2 may also include an uplink grant (UL grant) for scheduling an uplink resource indication of MSG3.
[0069] In step S430, the terminal device may send MSG3 to the network device on the uplink grant scheduled by the network device. MSG3 carries the data to be transmitted. If MSG3 is used for SDT, the resource for transmitting MSG3 (i.e. the uplink grant scheduled by the network device) may also be referred to as RA-SDT resource.
[0070] In step S440, the network device sends MSG4 to the terminal device. The MSG4 may include a response to the data to be transmitted.
[0071] Configuration authorization may also be referred to as uplink authorization-free. Configuration authorization may refer to a network device activating an uplink authorization to a terminal device once. In the absence of a deactivation indication, the terminal device may always use the resources specified by the activated uplink authorization (i.e., CG resources) for uplink transmission. In an embodiment of the present application, the terminal device may use CG resources for SDT. The CG resources used for SDT may also be referred to as CG-SDT resources.
[0072] The network device can indicate the CG-SDT resources by sending CG-SDT resource configuration information (or CG-SDT resource configuration parameters) to the terminal device. The CG-SDT resource configuration information can be carried in the RRC connection release message. In some embodiments, the CG-SDT resource configuration information is only applicable to the current RRC connection release message. That is to say, if the state of the terminal device changes, such as the terminal device performs a cell switch or the terminal device performs an RRC reconnection (such as switching from the RRC_INACTIVE state to the RRC_CONNECTED state), the CG-SDT resource configuration information will become invalid.
[0073] The CG-SDT resource configuration information may include relevant information for performing SDT. For example, the CG-SDT resource configuration information may include one or more of the following information: one or more periodic time-frequency resources, modulation and coding scheme (MCS), transport block size (TBS), multiple physical uplink shared channel (PUSCH) repetitions, starting position, cell radio network temporary identity (C-RNTI) (e.g., CG-SDT C-RNTI), TA verification criteria, allowed CG-SDT resource hopping, whether the CG-SDT resource configuration is valid for one or more occasions, demodulation reference signal (DMRS) configuration, power control parameters, physical downlink control channel (PDCCH) search space, multiple repetitions of coverage enhancement (CE), and some other ancillary parameters.
[0074] The type of configuration grant may be, for example, CG type 1 or CG type 2. The configuration parameters of CG type 1 may be configured by RRC through high-level signaling. The high-level signaling may be, for example, IE ConfiguredGrantConfig. The parameters required for CGtype 2 are also configured by IE ConfiguredGrantConfig, but the activation and deactivation of CG type 2 resources need to be indicated by downlink control information (DCI), and only resources activated by DCI can be used.
[0075] CG type 1 and CG type 2 can be distinguished based on the rrc-ConfiguredUplinkGrant field in IE ConfiguredGrantConfig. If the rrc-ConfiguredUplinkGrant field is configured, the type of configuration authorization is CG type 1, and if the rrc-ConfiguredUplinkGrant field is not configured, the type of configuration authorization is CG type 2.
[0076] The network device may configure a time domain resource assignment (TDRA) table specific to the terminal device to the terminal device. The TDRA table may be carried in an RRC connection release message. The TDRA table may be used to schedule SDT resources or subsequent SDT resources or SDT retransmission resources. The above SDT resources may be RA-SDT resources or CG-SDT resources. The above resources may be PUSCH resources.
[0077] Taking CG-SDT resources as an example, the setting of the association period candidate value set for SSB to CG PUSCH mapping can be similar to the definition of the association N candidate value set for SSB to RO mapping. Parameter N can be configured through high-level parameters. If N < 1, one SSB is mapped to 1 / N consecutive valid CG PUSCHs. If N ≥ 1, N consecutive SSBs are associated with one CG PUSCH. If N < 1, multiple terminal devices can share the same resource, that is, the same resource can be allocated to different terminal devices. If N ≥ 1, the terminal device can obtain dedicated resources, and different terminal devices can obtain different resources.
[0078] Before the terminal device performs SDT, it needs to determine whether the terminal device meets the conditions for triggering SDT. The terminal device can perform SDT only if the conditions for triggering SDT are met. If the conditions for triggering SDT are met, the terminal device can initiate the SDT process. If the conditions for triggering SDT are not met, the terminal device can initiate the RRC resume process. For example, the terminal device can switch from the RRC_INACTIVE state to the RRC_CONNECTED state to transmit data.
[0079] The conditions for triggering SDT may include one or more of the following conditions: the data to be transmitted comes from a radio bearer that can trigger SDT; the amount of data to be transmitted is less than a preconfigured data amount threshold; the measurement result of the downlink reference signal receiving power (RSRP) is greater than a preconfigured RSRP threshold; there are valid SDT resources. The above conditions are introduced below.
[0080] In some embodiments, the condition for triggering SDT is related to the radio bearer where the data to be transmitted is located. The embodiment of the present application can determine whether the terminal device meets the condition for triggering SDT based on whether the data to be transmitted comes from a radio bearer that can trigger SDT. If the data to be transmitted comes from a radio bearer that can trigger SDT, the terminal device meets the condition for triggering SDT. If the data to be transmitted does not come from a radio bearer that can trigger SDT, the terminal device does not meet the condition for triggering SDT. The radio bearer may be, for example, a signaling radio bearer (SRB) or a data radio bearer (DRB).
[0081] In other embodiments, the condition for triggering SDT is related to the amount of data to be transmitted. If the amount of data to be transmitted is small, such as the data to be transmitted is small packet data, the terminal device meets the condition for triggering SDT. If the amount of data to be transmitted is large, the terminal device does not meet the condition for triggering SDT. The embodiment of the present application can also determine whether the terminal device meets the condition for triggering SDT by comparing the amount of data to be transmitted with the data amount threshold. If the amount of data to be transmitted is less than the data amount threshold, the terminal device meets the condition for triggering SDT. If the amount of data to be transmitted is greater than or equal to the data amount threshold, the terminal device does not meet the condition for triggering SDT. The data amount threshold can be pre-configured by the network device, or the data amount threshold can also be predefined in the protocol.
[0082] In other embodiments, the condition for triggering SDT is related to the measurement result of downlink RSRP. If the measurement result of downlink RSRP is greater than the RSRP threshold, it means that the signal quality is good, and the terminal device meets the condition for triggering SDT. If the measurement result of downlink RSRP is less than or equal to the RSRP threshold, it means that the signal quality is poor, and the terminal device does not meet the condition for triggering SDT. The RSRP threshold can be preconfigured by the network device, or it can be predefined in the protocol.
[0083] In other embodiments, the condition for triggering SDT is related to whether there are valid SDT resources. If there are valid SDT resources, the terminal device meets the condition for triggering SDT, and the terminal device can use the valid SDT resources for data transmission. If there are no valid SDT resources, the terminal device does not meet the condition for triggering SDT, and the terminal device has no available SDT resources for data transmission. The SDT resources can be the RA-SDT resources described above, and / or the CG-SDT resources.
[0084] If the terminal device is configured with RA-SDT resources and CG-SDT resources at the same time, when determining whether there are valid SDT resources, the terminal device may determine both RA-SDT resources and CG-SDT resources at the same time, or may first determine whether one of the SDT resources is valid, and then determine whether the other SDT resource is valid. For example, the terminal device may first determine whether there are valid RA-SDT resources, and then determine whether there are valid CG-SDT resources. For another example, the terminal device may first determine whether there are valid CG-SDT resources, and then determine whether there are valid RA-SDT resources. The following description is based on the example of a terminal device first determining whether there are valid CG-SDT resources, and then determining whether there are valid RA-SDT resources.
[0085] In some embodiments, whether the CG-SDT resource is valid is related to whether there is a valid timing advance (TA). TA is related to the uplink synchronization of the terminal device. If TA is valid, it means that the terminal device is in an uplink synchronization state; if TA is invalid, it means that the terminal device is in an uplink out-of-sync state. The embodiment of the present application can determine whether the CG-SDT resource is valid by judging whether there is a valid TA. If there is a valid TA, it can indicate that the CG-SDT resource is valid. If there is no valid TA, it can indicate that the CG-SDT resource is invalid.
[0086] Whether the TA is valid is related to whether the TA timer (TAT) of the SDT is in the running state. The network device can configure the TA timer for the terminal device, and the TA timer can be used by the terminal device to determine the duration of uplink synchronization. If the TA timer is in the running state, that is, the TA timer has not timed out, it means that there is a valid TA. If the TA timer is not in the running state, that is, the TA timer has timed out, it means that there is no valid TA.
[0087] The TA timer can be started after the terminal device receives an RRC connection release (release) message or the terminal device enters the RRC_INACTIVE state. The duration of the TA timer can be configured by the network device to the terminal device. For example, after the terminal device receives the RRC connection release message sent by the network device, it can enter the RRC_INACTIVE state according to the indication information in the RRC connection release message. The RRC connection release message can also include the configuration information of the SDT-TA timer, and the terminal device can start the SDT TA timer based on the configuration information of the SDT-TA timer.
[0088] There is currently no clear way to ensure data transmission of terminal devices and avoid resource waste when terminal devices are performing SDT. If terminal devices use dedicated resources for SDT, although data transmission of terminal devices can be guaranteed, it will lead to resource waste. Although resource sharing can improve resource utilization, such as unused resources of a terminal device can be used by other terminal devices, resource sharing will result in resource conflicts, that is, there will be a situation where two terminal devices compete for the same resource.
[0089] Based on this, an embodiment of the present application provides a method and apparatus for wireless communication, which limits the time period for a terminal device to use dedicated resources (such as a first transmission resource) so that the terminal device only uses the first transmission resource for SDT part of the time, and can use shared resources for SDT at other times, thereby ensuring the data transmission of the terminal device and avoiding waste of resources to a certain extent.
[0090] Combine the following Figure 5 , the wireless communication method in the embodiment of the present application is introduced.
[0091] See also Figure 5 In step S510, the network device sends first information to the terminal device. The first information is used to indicate a first timer. The first timer is used to indicate the duration of using the first transmission resource for SDT.
[0092] The first transmission resource may be a dedicated resource of the terminal device. The first transmission resource may be a network device configured to the terminal device. For example, the first transmission resource may be a CG-SDT resource, such as the first transmission resource may be a resource specified by CGtype 1.
[0093] The first timer can be used to limit the duration of the terminal device using the first transmission resource. In other words, the terminal device is not able to use the first transmission resource all the time, but can only use the first transmission resource within the validity period of the first timer. If the first timer has not timed out, the terminal device can use the first transmission resource. If the first timer has timed out, the terminal device cannot continue to use the first transmission resource. Of course, as long as the first timer has not timed out, the terminal device can use the first transmission resource for multiple SDTs.
[0094] The first timer may be indicated by the network device to the terminal device. The network device may directly indicate the first timer to the terminal device, such as the network device may directly indicate the duration of the first timer to the terminal device. In other embodiments, the first timer may be determined based on other timers. For example, the first timer may be determined based on a TA timer. The duration of the first timer may be equal to the duration of the TA timer, or the duration of the first timer may be obtained by adding or subtracting a preset duration from the duration of the TA timer. For example, the first timer = TA timer + duration 1. For another example, the first timer = TA timer - duration 2. In this case, the network device may indicate the preset duration to the terminal device, and the terminal device may determine the first timer based on the preset duration and the TA timer.
[0095] The duration of the first timer is less than the duration of the second timer. The second timer is the duration for the terminal device to perform SDT. Before performing SDT, the terminal device will determine whether it meets the conditions for performing SDT. If the terminal device meets the conditions for performing SDT, the terminal device can perform SDT. However, the terminal device cannot perform SDT all the time. The network device will configure a second timer for the terminal device to limit the duration for which the terminal device can perform SDT. The second timer can be understood as the duration for the terminal device to perform SDT within a cycle. If the second timer times out, the terminal device will not be able to perform SDT. If a small data packet arrives at the terminal device later, the terminal device needs to determine again whether the conditions for performing SDT are met. If so, the terminal device can perform SDT within the duration specified by the second timer according to the configuration of the network device.
[0096] The first information may be carried in RRC signaling, in other words, the network device may configure the first timer for the terminal device through RRC signaling. In some embodiments, the first information may be carried in CG-SDT resource configuration information, and the network device may indicate the first timer to the terminal device by multiplexing the CG-SDT resource configuration information, thereby saving signaling overhead.
[0097] The first timer and the second timer can be carried in the same message. For example, the first timer and the second timer can both be carried in the CG-SDT resource configuration information. The network device can simultaneously indicate the first timer and the second timer to the terminal device through the CG-SDT resource configuration information.
[0098] The embodiments of the present application do not specifically limit the start time of the first timer and the second timer. The start time of the first timer and the second timer may be the same or different. For example, the terminal device may start the first timer at the moment of receiving the first information. If the first information is carried in the CG-SDT resource configuration information, the terminal device may start the first timer after receiving the CG-SDT resource configuration information. Similarly, the network device may also start the first timer after sending the CG-SDT resource configuration information to the terminal device. In some embodiments, the terminal device may start the first timer after receiving the RRC connection release message. In other embodiments, the terminal device may also start the first timer when entering the RRC_INACTIVE state. In some embodiments, the terminal device may start the first timer and the second timer at the same time after receiving the CG-SDT resource configuration information.
[0099] In an embodiment of the present application, the terminal device may use the first transmission resource for SDT within the duration specified by the first timer. In order to improve resource utilization, after the first timer times out, the terminal device may use shared resources for SDT. Shared resources may also be referred to as allocatable resources in a network device. For example, a terminal device may use shared resources by monitoring. The network device may indicate configuration information of a shared resource pool to the terminal device, and the terminal device may monitor the resources in the shared resource pool. If the terminal device monitors that a certain resource is not occupied by other terminals, the terminal device may use the resource for SDT. If the terminal device monitors that a certain resource is already occupied by other terminal devices, the terminal device cannot use the resource for SDT.
[0100] In some embodiments, in order to reduce resource collisions, the network device may also dynamically allocate resources to the terminal device by scheduling. Figure 5As shown, in step S520, the terminal device may send a first request to the network device, the first request being used to request a second transmission resource. In step S530, after receiving the first request, the network device may send second information to the terminal device, the second information being used to indicate a second transmission resource.
[0101] The first request may also be used to indicate the size of the second transmission resource. When sending the first request, the terminal device may indicate the size of the required transmission resource to the network device. For example, the first request may be used to indicate the size of the second transmission resource. After receiving the first request, the network device may allocate transmission resources corresponding to the size of the second transmission resource to the terminal device. For another example, the first request may be used to indicate the size of the data to be transmitted (or the amount of data to be transmitted). The terminal device may also report the size of the data to be transmitted to the network device. The network device may determine the size of the second transmission resource required by the terminal device based on the size of the data to be transmitted, thereby allocating transmission resources matching the size of the data to be transmitted to the terminal device.
[0102] In some embodiments, the allocatable resources in the network device may not be able to meet the transmission requirements of all terminal devices. In other words, the sum of the transmission resources required by the terminal devices is greater than the allocatable resources. For example, the size of the allocatable resources in the network device is M, and there are K terminal devices that simultaneously request transmission resources from the network device, and the sum of the transmission resources requested by the K terminal devices is N. If N is greater than M, the allocatable resources cannot meet the transmission requirements of the K terminal devices at the same time. Therefore, not all terminal devices can obtain the transmission resources allocated by the network device. In this case, the network device can determine which terminal devices to allocate transmission resources to and which terminal devices not to allocate transmission resources to based on a certain allocation strategy.
[0103] In order to improve resource utilization, whether the terminal device can be allocated with transmission resources can be determined based on the second information, or the network device can determine the terminal device that can be allocated with transmission resources based on the second information. The second information includes one or more of the following information: the size of the resources that can be allocated in the network device; the resources that are less than or equal to the second transmission resource size among the transmission resources requested by other terminal devices; and the resources that are greater than or equal to the second transmission resource size among the transmission resources requested by other terminal devices.
[0104] For the convenience of description, the resources requested by other terminal devices that are less than or equal to the second transmission resource size are referred to as resource A, and the resources requested by other terminal devices that are greater than or equal to the second transmission resource size are referred to as resource B.
[0105] In some embodiments, if the cumulative sum of resource A and the sum of the second transmission resource are less than or equal to the size of the allocatable resource, the network device can allocate the second transmission resource to the terminal device, that is, the terminal device can obtain the second transmission resource. If the cumulative sum of resource A and the sum of the second transmission resource are greater than the size of the allocatable resource, the network device cannot allocate the second transmission resource to the terminal device, that is, the terminal device cannot obtain the second transmission resource.
[0106] In other embodiments, if the cumulative sum of resource B and the sum of the second transmission resource are less than or equal to the size of the allocatable resource, the network device can allocate the second transmission resource to the terminal device, that is, the terminal device can obtain the second transmission resource. If the cumulative sum of resource B and the sum of the second transmission resource are greater than the size of the allocatable resource, the network device cannot allocate the second transmission resource to the terminal device, that is, the terminal device cannot obtain the second transmission resource.
[0107] The network device may sort the transmission resources requested by multiple terminal devices, such as sorting them in order from large to small or from small to large. The network device may allocate transmission resources to the terminal devices in the sorted order. Hereinafter, the allocation strategy of allocating transmission resources in the order from large to small is referred to as the first allocation strategy, and the allocation strategy of allocating transmission resources in the order from small to large is referred to as the second allocation strategy.
[0108] Taking the order from large to small as an example, the network device may first allocate resources to the terminal device that requires the largest transmission resources, and then allocate resources to the terminal device that requires the second largest transmission resources, and so on, until the remaining resources are not enough for the transmission resources required by the terminal device.
[0109] For example, if the allocable resources in the network device are M, and K terminal devices apply for transmission resources at the same time, each terminal device (UE i ) The transmission resource requested is S i The network device can sort the K transmission resources in descending order, such as S0≥S1≥…≥S k-1 , i=0,1…,k-1. The network device can schedule transmission resources for the corresponding terminal devices in turn according to the above arrangement order.
[0110] Network equipment is divided into UE0, UE1, UE k-1The network device allocates transmission resources to the terminal devices in the order of . If the allocatable resource M is greater than or equal to S0, the network device may allocate transmission resource S0 to UE0. After allocating transmission resources to UE0, the allocatable resources become M-S0. If M-S0 is greater than or equal to S1, the network device may allocate transmission resource S1 to UE1. After allocating transmission resources to UE1, the allocatable resources become M-S0-S1. And so on, until the remaining allocatable resources cannot meet the transmission resource requirements of the next terminal device. For example, if M-S0-S1 is less than S2, that is, the remaining allocatable resources cannot meet the transmission requirements of UE2, the network device may not allocate transmission resources to UE2.
[0111] In some embodiments, if the remaining allocatable resources cannot meet the transmission requirements of the next terminal device, the network device can determine whether the remaining transmission resources can meet the transmission resource requirements of other terminal devices. For example, if the remaining transmission resources cannot meet the transmission requirements of the first terminal, the network device can determine whether the remaining transmission resources meet the transmission requirements of the second terminal, and the transmission resources required by the second terminal are less than the transmission resources of the first terminal.
[0112] For example, still taking the above K terminal devices as an example, if the remaining transmission resources cannot meet the transmission requirements of UE2, the network device can skip UE2 and continue to determine whether the remaining transmission resources can meet the transmission requirements of UE3. If the remaining transmission resources can meet the transmission requirements of UE3, that is, M-S0-S1 is greater than or equal to S2, the network device can allocate transmission resource S3 to UE3. If the remaining transmission resources cannot meet the transmission requirements of UE3, that is, M-S0-S1 is less than S2, the network device can skip UE3 and continue to determine whether the remaining transmission resources can meet the transmission requirements of UE4. And so on, until the remaining transmission resources cannot meet the transmission requirements of any terminal device.
[0113] In some embodiments, when determining the second terminal, the network device may also determine the second terminal based on the order of the required transmission resources from small to large. For example, still taking the above K terminal devices as an example, if the remaining transmission resources cannot meet the transmission requirements of UE2, the network device may determine whether the remaining transmission resources can meet the transmission requirements of UE k-1 If the remaining transmission resources can meet the UE k-1 The transmission requirements, that is, M-S0-S1 is greater than or equal to S k-1 , then the network device can be UE k-1 Allocate transmission resources for UE k-1 After allocating transmission resources, the remaining allocable transmission resources become M-S0-S1-S k-1The network device can continue to determine whether the remaining allocatable resources can satisfy S k-2 If the remaining transmission resources cannot meet the transmission requirements of the UE k-1 The transmission requirement is that M-S0-S1 is less than S k-1 , then the network device is not a UE k-1 Allocate transmission resources. Since the remaining transmission resources cannot meet the UE k-1 transmission requirements, and UE k-1 The transmission demand of the terminal device is the smallest, and the remaining transmission resources will not be able to meet the transmission demand of all remaining terminal devices. Therefore, the network device does not need to continue to determine whether the transmission demand of other terminals can be met, thereby saving the determination resources of the network device.
[0114] Taking small to large as an example, the network device can first allocate resources to the terminal device with the smallest transmission resource requirement, and then allocate resources to the terminal device with the second smallest transmission resource requirement, and so on, until the remaining resources are not enough for the transmission resources required by the terminal devices.
[0115] For example, if the allocable resources in the network device are M, and K terminal devices apply for transmission resources at the same time, each terminal device (UE i ') The transmission resource requested is S i '. The network device can sort the K transmission resources in ascending order, such as S0'≤S1'≤…≤S k-1 ', i=0,1…,k-1. The network device can schedule transmission resources for the corresponding terminal devices in turn according to the above arrangement order.
[0116] Network equipment is divided into UE0', UE1'..., UE k-1'. If the allocatable resource M is greater than or equal to S0', the network device may allocate transmission resource S0' to UE0'. After allocating transmission resources to UE0', the allocatable resources become M-S0'. If M-S0' is greater than or equal to S1', the network device may allocate transmission resource S1' to UE1'. After allocating transmission resources to UE1', the allocatable resources become M-S0'-S1'. And so on, until the remaining allocatable resources cannot meet the transmission resource requirements of the next terminal device. For example, if M-S0'-S1' is less than S2', that is, the remaining allocatable resources cannot meet the transmission requirements of UE2', the network device may not allocate transmission resources to UE2'. Since the transmission resources required by the terminal devices after UE2' are larger than the transmission resources required by UE2', if the remaining transmission resources cannot meet the transmission requirements of UE2', then the transmission requirements of the terminal devices after UE2' cannot be met. Therefore, the network device does not need to determine whether the remaining transmission resources can meet the transmission requirements of other terminal devices.
[0117] In some embodiments, the network device may compare the above-mentioned multiple allocation strategies to select the optimal allocation strategy, such as selecting the allocation strategy with the highest resource utilization rate, or selecting the allocation strategy with the largest number of terminal devices that can be allocated.
[0118] For example, the network device may compare the allocation results of the first allocation strategy and the second allocation strategy, and select the allocation strategy with the highest resource utilization from the first allocation strategy and the second allocation strategy. Resource utilization may refer to the ratio of resources allocated by the network device to the allocatable resources for the terminal device.
[0119] The network device can record the allocation results of the first allocation strategy and the second allocation strategy. For example, the network device can set an allocation coefficient for each terminal device to indicate whether the transmission resources are successfully allocated or cannot be allocated. For example, an allocation coefficient of 1 can indicate successful allocation, and an allocation coefficient of 0 indicates that it cannot be allocated. The resources finally allocated by the network device can be the cumulative sum of the allocation coefficients of each terminal multiplied by the transmission resources required by it. The network device can select the allocation strategy with the most resources finally allocated as the final allocation strategy, and complete the resource allocation according to the final allocation strategy. For example, if the resources allocated according to the first allocation strategy are greater than the resources allocated according to the second allocation strategy, the network device can allocate resources to the terminal device according to the first allocation strategy.
[0120] Combine the following Figure 6-Figure 8 , the wireless communication method of the embodiment of the present application is introduced in detail.
[0121] See also Figure 6In step S602, the UE in the RRC_INACTIVE state starts timer T1 and timer T2. It should be noted that timer T1 here may be the first timer described above, and timer T2 may be the second timer described above.
[0122] In step S604, the UE determines whether the timer T1 has timed out.
[0123] In step S606, if the timer T1 has not timed out, the UE may determine whether there is a small data packet to be sent.
[0124] In step S608, if the UE has a small data packet to send, the UE may use a dedicated PUSCH resource to send the small data packet.
[0125] In step S610, if the UE has no small data packet to send, the UE may reserve dedicated PUSCH resources.
[0126] At step S612, if the timer T1 expires, the UE may release the dedicated PUSCH resources.
[0127] In step S614, if the timer T1 times out, the UE determines whether the timer T2 times out.
[0128] In step S616, if the timer T2 times out, the UE cannot send the small data packet.
[0129] In step S618, if the timer T2 has not timed out, the UE determines whether there is a small data packet to be sent.
[0130] In step S620, if the UE has a small data packet to send, the UE may send the small data packet based on resources scheduled by the network device.
[0131] If timer T1 has not expired, the UE can use dedicated PUSCH resources to send small data packets. The process of UE using dedicated PUSCH resources to send small data packets can be as follows: Figure 7 shown.
[0132] See also Figure 7 In step S710, the UE in the RRC_CONNECTED state may receive an RRC connection release message sent by the network device. The RRC connection release message may include CG-SDT resource configuration information.
[0133] In step S720, after receiving the RRC connection release message, the UE may release the RRC connection with the network device, thereby entering the RRC_INACTIVE state. In addition, the UE may obtain the timer T1 according to the CG-SDT resource configuration information.
[0134] In step S730, within the validity period of timer T1, the UE sends a small data packet using dedicated PUSCH resources.
[0135] When timer T1 times out but timer T2 has not timed out, the UE can send a small data packet based on the resources scheduled by the network device. The process of the UE sending a small data packet based on the resources scheduled by the network device can be as follows: Figure 8 shown.
[0136] See also Figure 8 In step S810, the UE in the RRC_CONNECTED state may receive an RRC connection release message sent by the network device. The RRC connection release message may include CG-SDT resource configuration information.
[0137] In step S820, after receiving the RRC connection release message, the UE may release the RRC connection with the network device, thereby entering the RRC_INACTIVE state. In addition, the UE may obtain the timer T1 and the timer T2 according to the CG-SDT resource configuration information.
[0138] In step S830, the UE sends a scheduling request to the network device to request PUSCH resources.
[0139] In step S840, the network device determines whether to allocate PUSCH resources to the UE according to a certain scheduling strategy.
[0140] In step S850, if the network device determines to allocate PUSCH resources to the UE, the network device may send a grant to the UE to indicate the PUSCH resources.
[0141] In step S860, after the UE receives the grant, it can send a small data packet on the PUSCH resource indicated by the grant. In some embodiments, the UE can also send common control channel (CCCH) information on the PUSCH resource. The CCCH information can be used to establish an RRC connection or SRB, or the CCCH can be used in the RRC reestablishment process. For example, the CCCH can be used for the UE to switch from the RRC_INACTIVE state to the RRC_CONNECTED state.
[0142] Combination of the above Figures 1 to 8 , describes the method embodiment of the present application in detail, and the following is combined with Figures 9 to 11 , describes the device embodiment of the present application in detail. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment, so the parts not described in detail can refer to the previous method embodiment.
[0143] Fig. 9 It is a schematic structural diagram of a terminal device provided in one embodiment of the present application. Fig. 9 The terminal device shown may be any of the terminal devices described above. The terminal device 900 includes a receiving unit 910 .
[0144] The receiving unit 910 can be used to receive first information sent by a network device, where the first information is used to indicate a first timer, and the first timer is used to indicate the duration of SDT using a first transmission resource, wherein the duration of the first timer is less than the duration of a second timer, and the second timer is used to indicate the duration of SDT for the terminal device.
[0145] In some embodiments, the terminal device 900 also includes: a sending unit 920, used to send a first request to the network device when the first timer times out and the second timer has not timed out, the first request being used to request a second transmission resource; the receiving unit being used to receive second information sent by the network device, the second information being used to indicate a second transmission resource.
[0146] In some embodiments, the first request is used to indicate the size of the second transmission resource, and whether the terminal device can obtain the second transmission resource is determined based on second information, and the second information includes one or more of the following information: the size of allocatable resources in the network device; resources in the transmission resources requested by other terminal devices that are less than or equal to the size of the second transmission resources; resources in the transmission resources requested by other terminal devices that are greater than or equal to the size of the second transmission resources.
[0147] In some embodiments, the first transmission resource is a dedicated resource for the terminal device.
[0148] In some embodiments, the duration of the first timer is determined based on a TA timer.
[0149] In some embodiments, the first information is carried in CG-SDT resource configuration information.
[0150] Fig.10 It is a schematic structural diagram of a network device provided by an embodiment of the present application. Fig.10 The network device shown may be any one of the network devices described above. The network device 1000 includes a sending unit 1010 .
[0151] The sending unit 1010 can be used to send first information to a terminal device, where the first information is used to indicate a first timer, and the first timer is used to indicate the duration of SDT using a first transmission resource, wherein the duration of the first timer is less than the duration of a second timer, and the second timer is used to indicate the duration of SDT for the terminal device.
[0152] In some embodiments, the network device 1000 also includes: a receiving unit 1020, used to receive a first request sent by the terminal device when the first timer times out and the second timer has not timed out, the first request being used to request a second transmission resource; the sending unit being used to send second information to the terminal device, the second information being used to indicate a second transmission resource.
[0153] In some embodiments, the first request is used to indicate the size of the second transmission resource, and whether the terminal device can obtain the second transmission resource is determined based on second information, and the second information includes one or more of the following information: the size of allocatable resources in the network device; resources in the transmission resources requested by other terminal devices that are less than or equal to the size of the second transmission resources; resources in the transmission resources requested by other terminal devices that are greater than or equal to the size of the second transmission resources.
[0154] In some embodiments, the first transmission resource is a dedicated resource for the terminal device.
[0155] In some embodiments, the duration of the first timer is determined based on a TA timer.
[0156] In some embodiments, the first information is carried in CG-SDT resource configuration information.
[0157] Fig.11 It is a schematic structural diagram of the device of an embodiment of the present application. Fig.11 The dotted line in the figure indicates that the unit or module is optional. The device 1100 can be used to implement the method described in the above method embodiment. The device 1100 can be a chip, a terminal device or a network device.
[0158] The device 1100 may include one or more processors 1110. The processor 1110 may support the device 1100 to implement the method described in the above method embodiment. The processor 1110 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.
[0159] The apparatus 1100 may further include one or more memories 1120. The memory 1120 stores a program, which can be executed by the processor 1110, so that the processor 1110 executes the method described in the above method embodiment. The memory 1120 may be independent of the processor 1110 or integrated in the processor 1110.
[0160] The apparatus 1100 may further include a transceiver 1130. The processor 1110 may communicate with other devices or chips through the transceiver 1130. For example, the processor 1110 may transmit and receive data with other devices or chips through the transceiver 1130.
[0161] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to a terminal or network device provided in the present application, and the program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.
[0162] The embodiment of the present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the terminal or network device provided in the embodiment of the present application, and the program enables the computer to execute the method performed by the terminal or network device in each embodiment of the present application.
[0163] The embodiment of the present application also provides a computer program. The computer program can be applied to the terminal or network device provided in the embodiment of the present application, and the computer program enables a computer to execute the method executed by the terminal or network device in each embodiment of the present application.
[0164] It should be understood that in the embodiment of the present application, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean determining B only according to A, and B can also be determined according to A and / or other information.
[0165] It should be understood that the term "and / or" in this article is only a description of the association relationship of the associated objects, indicating that there can be three relationships. 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.
[0166] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
[0167] 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.
[0168] 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.
[0169] 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.
[0170] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).
[0171] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present 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 wireless communication method, characterized in that: include: The terminal device receives first information sent by the network device, where the first information is used to indicate a first timer, where the first timer is used to indicate a duration of small data transmission SDT using a first transmission resource; When the first timer times out and the second timer does not time out, the terminal device sends a first request to the network device, where the first request is used to request a second transmission resource; The terminal device receives second information sent by the network device, where the second information is used to indicate a second transmission resource; The duration of the first timer is smaller than the duration of the second timer, and the second timer is used to indicate the duration of the SDT of the terminal device.
2. The method according to claim 1, characterized in that The first request is used to indicate the size of the second transmission resource, and whether the terminal device can obtain the second transmission resource is determined based on second information, The second information includes one or more of the following information: The size of allocatable resources in the network device; Resources that are smaller than or equal to the size of the second transmission resource among the transmission resources requested by other terminal devices; The transmission resources requested by other terminal devices are greater than or equal to the size of the second transmission resources.
3. The method according to claim 1 or 2, characterized in that: The first transmission resource is a dedicated resource of the terminal device.
4. The method according to claim 1 or 2, characterized in that: The duration of the first timer is determined based on a timing advance TA timer.
5. The method according to claim 1 or 2, characterized in that: The first information is carried in the configuration authorization CG-SDT resource configuration information.
6. A wireless communication method, characterized in that: include: The network device sends first information to the terminal device, where the first information is used to indicate a first timer, where the first timer is used to indicate a duration of small data transmission SDT using a first transmission resource; When the first timer times out and the second timer does not time out, the network device receives a first request sent by the terminal device, where the first request is used to request a second transmission resource; The network device sends second information to the terminal device, where the second information is used to indicate a second transmission resource; The duration of the first timer is smaller than the duration of the second timer, and the second timer is used to indicate the duration of the SDT of the terminal device.
7. The method according to claim 6, characterized in that The first request is used to indicate the size of the second transmission resource, and whether the terminal device can obtain the second transmission resource is determined based on second information, The second information includes one or more of the following information: The size of allocatable resources in the network device; Resources that are smaller than or equal to the size of the second transmission resource among the transmission resources requested by other terminal devices; The transmission resources requested by other terminal devices are greater than or equal to the size of the second transmission resources.
8. The method according to claim 6 or 7, characterized in that: The first transmission resource is a dedicated resource of the terminal device.
9. The method according to claim 6 or 7, characterized in that: The duration of the first timer is determined based on a timing advance TA timer.
10. The method according to claim 6 or 7, characterized in that: The first information is carried in the configuration authorization CG-SDT resource configuration information.
11. A terminal device, characterized in that: include: A receiving unit, configured to receive first information sent by a network device, where the first information is used to indicate a first timer, where the first timer is used to indicate a duration of a small data transmission SDT using a first transmission resource; a sending unit, configured to send a first request to the network device when the first timer times out and the second timer does not time out, wherein the first request is used to request a second transmission resource; The receiving unit is further used to receive second information sent by the network device, where the second information is used to indicate a second transmission resource; The duration of the first timer is smaller than the duration of the second timer, and the second timer is used to indicate the duration of the SDT of the terminal device.
12. The terminal device according to claim 11, characterized in that: The first request is used to indicate the size of the second transmission resource, and whether the terminal device can obtain the second transmission resource is determined based on second information, The second information includes one or more of the following information: The size of allocatable resources in the network device; Resources that are smaller than or equal to the size of the second transmission resource among the transmission resources requested by other terminal devices; The transmission resources requested by other terminal devices are greater than or equal to the size of the second transmission resources.
13. The terminal device according to claim 11 or 12, characterized in that: The first transmission resource is a dedicated resource of the terminal device.
14. The terminal device according to claim 11 or 12, characterized in that: The duration of the first timer is determined based on a timing advance TA timer.
15. The terminal device according to claim 11 or 12, characterized in that: The first information is carried in the configuration authorization CG-SDT resource configuration information.
16. A wireless communication network device, characterized in that: include: A sending unit, configured to send first information to a terminal device, where the first information is used to indicate a first timer, where the first timer is used to indicate a duration of a small data transmission SDT using a first transmission resource; A receiving unit, configured to receive a first request sent by the terminal device when the first timer times out and the second timer does not time out, wherein the first request is used to request a second transmission resource; The sending unit is further used to send second information to the terminal device, where the second information is used to indicate a second transmission resource; The duration of the first timer is smaller than the duration of the second timer, and the second timer is used to indicate the duration of the SDT of the terminal device.
17. The network device according to claim 16, characterized in that: The first request is used to indicate the size of the second transmission resource, and whether the terminal device can obtain the second transmission resource is determined based on second information, The second information includes one or more of the following information: The size of allocatable resources in the network device; Resources that are smaller than or equal to the size of the second transmission resource among the transmission resources requested by other terminal devices; The transmission resources requested by other terminal devices are greater than or equal to the size of the second transmission resources.
18. The network device according to claim 16 or 17, characterized in that: The first transmission resource is a dedicated resource of the terminal device.
19. The network device according to claim 16 or 17, characterized in that: The duration of the first timer is determined based on a timing advance TA timer.
20. The network device according to claim 16 or 17, characterized in that: The first information is carried in the configuration authorization CG-SDT resource configuration information.
21. A terminal device, characterized in that: The method comprises a memory, a processor and a communication interface, wherein the memory is used to store programs, and the processor is used to call the programs in the memory, so that the terminal device executes the method according to any one of claims 1 to 5.
22. A network device, characterized in that: The network device comprises a memory, a processor and a communication interface, wherein the memory is used to store programs, and the processor is used to call the programs in the memory, so that the network device executes the method as claimed in any one of claims 6 to 10.
23. A device, characterized in that: The invention comprises a processor, which is used to call a program from a memory to execute the method according to any one of claims 1 to 5.
24. A device, characterized in that: The invention comprises a processor, which is used to call a program from a memory to execute the method according to any one of claims 6 to 10.
25. A chip, characterized in that: The device comprises a processor, which is used to call a program from a memory so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 5.
26. A chip, characterized in that: It comprises a processor, which is used to call a program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 6 to 10.
27. A computer-readable storage medium, characterized in that: A program is stored thereon, and the program enables a computer to execute the method according to any one of claims 1 to 5.
28. A computer-readable storage medium, characterized in that: A program is stored thereon, the program causing a computer to execute the method according to any one of claims 6 to 10.
29. A computer program product, characterized in that The method comprises a program which causes a computer to execute the method according to any one of claims 1 to 5.
30. A computer program product, characterized in that The method comprises a program which causes a computer to execute the method according to any one of claims 6 to 10.
