Wireless communication method and device

Abstract

The present application provides a method and apparatus for wireless communication, which provides a clear solution for network devices to handle resource conflicts. The method includes: the network device determines one or more of the following events based on first information: whether the first transmission opportunity for the first terminal to send a small data packet is valid; whether the second transmission opportunity for the second terminal to send message A in the two-step random access process is valid; wherein the resources of the second transmission opportunity at least partially overlap with the resources of the first transmission opportunity; the first information includes one or more of the following information: the service type of the small data packet; the triggering condition for triggering the two-step random access; the number of retransmissions of the small data packet.

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, the communication system allows the terminal to send small data packets to the network device in the radio resource control (RRC) inactive state. However, the resources for a terminal to send a small data packet may overlap with the resources for another terminal to perform random access, that is, the resources conflict.

[0003] If resource conflicts occur, there are currently no clear regulations on how network devices should handle such resource conflicts. Summary of the invention

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

[0005] In a first aspect, a method for wireless communication is provided, comprising: a network device determines one or more of the following events based on first information: whether a first transmission opportunity for a first terminal to send a small data packet is valid; whether a second transmission opportunity for a second terminal to send a message A in a two-step random access process is valid; wherein resources of the second transmission opportunity at least partially overlap with resources of the first transmission opportunity; the first information comprises one or more of the following information: a service type of the small data packet; a trigger condition for triggering two-step random access; and the number of retransmissions of the small data packet.

[0006] According to a second aspect, a method for wireless communication is provided, comprising: a first terminal sends a small data packet to a network device on a first transmission opportunity, resources of the first transmission opportunity at least partially overlap with resources of a second transmission opportunity, the second transmission opportunity is used by the second terminal to send a message A in a two-step random access process to the network device, and whether the first transmission opportunity or the second transmission opportunity is valid is determined based on first information, the first information comprising one or more of the following information: a service type of the small data packet; a trigger condition for triggering two-step random access; and the number of retransmissions of the small data packet.

[0007] According to a third aspect, a method for wireless communication is provided, comprising: a second terminal sends a message A in a two-step random access process to a network device on a second transmission opportunity, resources of the second transmission opportunity at least partially overlap with resources of a first transmission opportunity, the first transmission opportunity is used by the first terminal to send a small data packet to the network device, and whether the first transmission opportunity or the second transmission opportunity is valid is determined based on first information, the first information comprising one or more of the following information: a service type of the small data packet; a trigger condition for triggering two-step random access; and the number of retransmissions of the small data packet.

[0008] In a fourth aspect, a wireless communication device is provided, which is a network device, and includes: a determination unit, used to determine one or more of the following events based on first information: whether a first transmission opportunity for a first terminal to send a small data packet is valid; whether a second transmission opportunity for a second terminal to send a message A in a two-step random access process is valid; wherein the resources of the second transmission opportunity at least partially overlap with the resources of the first transmission opportunity; the first information includes one or more of the following information: the service type of the small data packet; the triggering condition for triggering the two-step random access; the number of retransmissions of the small data packet.

[0009] In a fifth aspect, a wireless communication device is provided, which is a first terminal, and the device includes: a sending unit, used to send a small data packet to a network device on a first transmission opportunity, the resources of the first transmission opportunity at least partially overlap with the resources of the second transmission opportunity, the second transmission opportunity is used by the second terminal to send a message A in a two-step random access process to the network device, and whether the first transmission opportunity or the second transmission opportunity is valid is determined based on first information, and the first information includes one or more of the following information: the service type of the small data packet; the triggering condition for triggering the two-step random access; the number of retransmissions of the small data packet.

[0010] In a sixth aspect, a wireless communication device is provided, which is a second terminal, and the device includes: a sending unit, used to send message A in a two-step random access process to a network device on a second transmission opportunity, the resources of the second transmission opportunity at least partially overlap with the resources of the first transmission opportunity, the first transmission opportunity is used by the first terminal to send a small data packet to the network device, and whether the first transmission opportunity or the second transmission opportunity is valid is determined based on first information, and the first information includes one or more of the following information: the service type of the small data packet; the triggering condition for triggering the two-step random access; the number of retransmissions of the small data packet.

[0011] In the seventh aspect, a wireless communication apparatus 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 programs in the memory so that the terminal device executes the method described in any one of the first to third aspects.

[0012] 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 any one of the first to third aspects.

[0013] 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 any one of the first to third aspects.

[0014] In a tenth 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 any one of the first to third aspects.

[0015] In an eleventh aspect, a computer program product is provided, comprising a program, wherein the program enables a computer to execute the method described in any one of the first to third aspects.

[0016] In a twelfth aspect, a computer program is provided, wherein the computer program enables a computer to execute the method described in any one of the first to third aspects.

[0017] In the embodiment of the present application, when the resources of the first transmission opportunity and the resources of the second transmission opportunity overlap, the network device can determine whether the first transmission opportunity is valid or whether the second transmission opportunity is valid based on the first information. By introducing the first information, a clear solution is provided for the network device to handle resource conflicts. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0019] Figure 2 is a schematic flow chart of the four-step random access process.

[0020] Figure 3 is a schematic flow chart of a two-step random access process.

[0021] Figure 4 It is a schematic flowchart of a wireless communication method provided by an embodiment of the present application.

[0022] Figure 5 It is a schematic diagram of determining whether a transmission opportunity is valid provided by an embodiment of the present application.

[0023] Figure 6It is a schematic diagram of determining whether a transmission opportunity is valid provided by another embodiment of the present application.

[0024] Figure 7 It is a schematic diagram of the correspondence between service types, resource pools, and timers provided in an embodiment of the present application.

[0025] Figure 8 This is a schematic flowchart of SDT performed by a terminal device provided in an embodiment of the present application.

[0026] Fig. 9 This is a schematic flowchart of timer-based transmission of small data packets provided in one embodiment of the present application.

[0027] Fig.10 It is a schematic flowchart of timer-based transmission of small data packets provided by another embodiment of the present application.

[0028] Fig.11 It is a structural diagram of a network device provided in one embodiment of the present application.

[0029] Fig.12 It is a structural diagram of a first terminal provided in another embodiment of the present application.

[0030] Fig.13 It is a structural diagram of a second terminal provided in another embodiment of the present application.

[0031] Fig.14 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 1 The wireless communication system 100 used in the embodiment of the present application may include a network device 110 and a terminal 120. The network device 110 may be a device that communicates with the terminal 120. The network device 110 may provide communication coverage for a specific geographical area and may communicate with the terminal 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 terminals 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, and so on.

[0037] The terminal 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 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 in the embodiment of the present application can be a mobile phone, a tablet computer, a laptop, 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 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, 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 to a wireless network. The 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 to device D2D, vehicle-to-everything (V2X), machine-to-machine (M2M) communication device that performs the base station function, 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 terminals 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 terminals are located.

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

[0043] With people's pursuit of speed, latency, high-speed mobility, energy efficiency, and the diversity and complexity of services in future life, the 3rd Generation Partnership Project (3GPP) international standards organization began to develop 5G. The main application scenarios of 5G may include: enhanced mobile broadband (eMBB), ultra reliable low latency communications (URLLC) and massive machine type communication (mMTC). The solution of the embodiment of the present application can be applied to any of the above scenarios.

[0044] The main features of eMBB services are large amounts of data transmitted and high transmission rates. When transmitting eMBB service data, a longer time scheduling unit is generally used to transmit data to improve data transmission efficiency. Typical eMBB services may include: ultra-high-definition video, augmented reality (AR), virtual reality (VR), etc.

[0045] The main features of URLLC services are that they require ultra-high reliability and ultra-low latency, with a small amount of transmitted data and burstiness. For example, without considering reliability, the transmission delay requirement of URLLC services is generally within 0.5 milliseconds. Under the premise that the reliability requirement reaches 99.999%, the transmission delay requirement of URLLC services is within 1ms. Due to the burstiness and randomness of URLLC services, URLLC services may not generate data packets for a long time, or may generate multiple data packets in a very short time. These data packets are small packets in most cases (for example, data packets with a size of 50 bytes). Typical URLLC services may include: wireless control in industrial manufacturing or production processes, motion control of driverless cars or drones, and tactile interaction applications such as remote repair and remote surgery.

[0046] Typical features of mMTC include: high connection density, small data volume, latency-insensitive services, low cost and long service life of modules, etc. This scenario is mainly for IoT services, which places extremely high demands on the access capabilities of the network.

[0047] Currently, three RRC states of the terminal are defined in the protocol: RRC connected (RRC_CONNECTED) state, RRC idle (RRC_IDLE) state and RRC inactive (RRC_INACTIVE) state.

[0048] The RRC_CONNECTED state may refer to the state in which the terminal is in after completing the random access process and before performing RRC release. An RRC connection exists between the terminal and a network device (e.g., an access network device). In the RRC_CONNECTED state, the terminal may perform data transmission with the network device, such as downlink data transmission and / or uplink data transmission. Alternatively, the terminal may also perform terminal-specific data channel and / or control channel transmission with the network device to transmit specific information or unicast information of the terminal.

[0049] The RRC_IDLE state refers to the state of the terminal when the terminal resides in the cell but does not perform random access. The terminal usually enters the RRC_IDLE state after powering on or after RRC is released. In the RRC_IDLE state, there is no RRC connection between the terminal and the network device (such as the resident network device), the network device does not store the context of the terminal, and no connection is established between the network device and the core network for the terminal. If the terminal needs to enter the RRC_CONNECTED state from the RRC_IDLE state, it is necessary to initiate the RRC connection establishment process.

[0050] 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 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 in order to quickly restore the RRC connection. In addition, the connection established between the network device and the core network for the terminal is not 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.

[0051] The terminal can switch between the above three RRC states. For example, the terminal 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 can also enter the RRC_IDLE state from the RRC_INACTIVE state or the RRC_CONNECTED state.

[0052] A terminal in the RRC_IDLE state or the RRC_INACTIVE state can enter the RRC_CONNECTED state by random access. There are two random access methods: four-step random access and two-step random access. Four-step random access can also be called contention-based random access. Two-step random access can also be called non-contention-based random access. Figure 2 and Figure 3 , the four-step random access process and the two-step random access process are introduced.

[0053] See also Figure 2 In step S210, the terminal may send message 1 (message 1, Msg1) in the random access process to the network device. The Msg1 includes a preamble.

[0054] The terminal can select a random access channel (RACH) resource and a preamble, and send the selected preamble on the selected resource. The RACH resource may also be referred to as a physical random access channel (PRACH) resource.

[0055] The network device may send the RACH configuration information to the terminal in the form of broadcast. The RACH configuration information may include the configuration information of the RACH time-frequency resources and the configuration information of the initial preamble root sequence.

[0056] The configuration information of the time domain resources of RACH can be indicated by a RACH configuration index. The RACH configuration index may include one or more of the repetition period of the RACH resources, the number of RACH opportunities (RACHoccasion, RO) contained in a RACH resource repetition period, and the duration of each RO. The configuration information of the frequency domain resources of RACH may include a RACH starting frequency domain resource index and the number of RACH resources that can be frequency-division multiplexed at the same time (i.e., the number of continuous RACH frequency domain resources). A continuous frequency domain resource can be determined by the configuration information of the RACH frequency domain resources. The starting preamble root sequence can be broadcast through the cell, and each cell can broadcast a preamble root sequence. Based on the configured starting preamble root sequence, the preamble set available in this cell can be obtained by cyclic shift.

[0057] In step S220, the network device sends Msg2 to the terminal, and the Msg2 may also be called a random access response (RAR). The Msg2 may be carried by a physical downlink control channel (PDCCH).

[0058] After sending Msg1, the terminal may open a random access response time window and monitor the PDCCH scrambled by the random access-radio network temporary identifier (RA-RNTI) within the time window.

[0059] Msg2 may also include a preamble sent by the terminal. If the terminal receives a PDCCH scrambled with RA-RNTI and Msg2 includes the preamble sent by itself, the terminal may consider that the random access response has been successfully received.

[0060] After the terminal successfully receives the PDCCH, the terminal can obtain the physical downlink shared channel (PDSCH) scheduled by the PDCCH, wherein the PDSCH includes the RAR. The RAR may include an uplink grant (UL grant) for scheduling the uplink resource indication of Msg3.

[0061] In step S230, the terminal sends Msg3 to the network device. The terminal may send Msg3 on the uplink grant scheduled by the network device. The Msg3 may also be called a radio resource control (RRC) connection establishment request message.

[0062] Step S240: The network device sends Msg4 to the terminal.

[0063] The Msg4 has two functions, one is for contention conflict resolution, and the other is to send an RRC configuration message to the terminal. If the terminal carries C-RNTI in Msg3, Msg4 is scheduled using the PDCCH scrambled by the C-RNTI. Accordingly, the terminal can use the C-RNTI in Msg3 to decode the PDCCH to obtain Msg4. If the terminal does not carry C-RNTI in Msg3, such as initial access, Msg4 can be scheduled using the PDCCH scrambled by the temporary C-RNTI. Accordingly, the terminal can use the temporary C-RNTI in Msg2 to decode the PDCCH to obtain Msg4. After successfully decoding the PDCCH, the terminal obtains the PDSCH carrying Msg4. The terminal can compare the common control channel (CCCH) service data unit (SDU) in the PDSCH with the CCCH SDU in Msg3. If the two are the same, it means that the contention resolution is successful.

[0064] Figure 3 This is a flow chart of a two-step random access process provided by an embodiment of the present application. The method includes steps S310 to S330.

[0065] In step S310, the network device sends preamble configuration information to the terminal, where the configuration information includes the preamble and RACH resources required in the random access process.

[0066] In step S320, the terminal can send MsgA to the network device according to the preamble configuration information, that is, the terminal can send the preamble to the network device on the RACH resource. The MsgA can also be called MsgA physical uplink shared channel (PUSCH).

[0067] In some embodiments, MsgA in the two-step random access procedure is equivalent to Msg1 and Msg3 in the four-step random access procedure.

[0068] In step S330, the network device sends MsgB to the terminal, and the MsgB may include RAR. After the terminal receives the RAR, it indicates that the random access process is finished.

[0069] In some embodiments, MsgB in the two-step random access procedure is equivalent to Msg2 and Msg4 in the four-step random access procedure.

[0070] After the two-step random access technology is introduced, the terminal can work in a mode where only four-step random access (4-stepRACH) is configured, or in a mode where only two-step random access (2-step RACH) is configured, or in a mode where both 4-step RACH and 2-step RACH are configured.

[0071] The terminal is only configured with 4-step RACH, which means that the terminal can only initiate random access based on the 4-step RACH configuration. The terminal is only configured with 2-step RACH, which means that the terminal can only initiate random access based on the 2-step RACH configuration.

[0072] For a terminal configured with both 4-step RACH and 2-step RACH, the terminal can initiate random access based on the 4-step RACH configuration, or can initiate random access based on the 2-step RACH configuration. In addition, since the terminal only supports maintaining one random access process at the same time, the terminal needs to select a random access process from 4-step RACH and 2-step RACH for access. In some embodiments, if the reference signal receiving power (RSRP) measured by the terminal is higher than the set threshold in the contention-based random access process, or for random access triggered by RRC reconfiguration, if the terminal configures a dedicated non-contention random access resource based on 2-step RACH, the terminal can select 2-step RACH. For other situations, the terminal can select 4-step RACH.

[0073] In a wireless communication system, a network device may broadcast synchronization signals in multiple directional beams, such as one or more of a primary synchronization signal (PSS), a secondary synchronization signal (SSS), an extended synchronization signal (ESS), a beam reference signal (BRS), and system information. In addition, the network device may also send other reference signals, such as a channel state information reference signal (CSI-RS), through a beam, so that the terminal can measure the channel between the network device and the terminal. The terminal may perform initial cell selection by listening to the broadcast, and perform signal measurement based on one or more of the synchronization signal, BRS, and other signals. The terminal may determine the signal strength based on the received signal, and select a cell and a beam within the cell based on the signal strength to perform random access. When performing random access, the terminal may start the random access process by sending a random access preamble using the same subarray and beam direction as the selected beam.

[0074] For terminals with infrequent data transmission, the terminal can remain in the RRC_INACTIVE state to save power. Before release 16 (Rel-16), terminals in the RRC_INACTIVE state do not support data transmission, that is, they do not support the transmission of mobile originated (MO) data and mobile terminated (MT) data. MO data means that the sender of the data is the terminal, and the message transmission direction is from the terminal to the network device. MO data can also be called uplink data. MT data means that the sender of the data is the network device, and the message transmission direction is from the network device to the terminal. MT data can also be called downlink data.

[0075] When MO data or MT data arrives, the terminal needs to restore the RRC connection and enter the RRC_CONNECTED state. In the RRC_CONNECTED state, the terminal can transmit MO data or MT data. After the MO data or MT data transmission is completed, the terminal releases the RRC connection and returns to the RRC_INACTIVE state.

[0076] In the above process, the terminal 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. However, in some scenarios, the terminal 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 switches to the RRC_CONNECTED state and then performs data transmission, the signaling overhead required for the terminal to switch the RRC state may even be greater than the overhead required to transmit these data, resulting in unnecessary power consumption and signaling overhead.

[0077] The small data packet in the embodiment of the present application can 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 can be data from a terminal application (application, APP). For example, the small data packet can 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 can be data from a non-terminal application. For example, the small data packet can 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).

[0078] In order to reduce the power consumption of the terminal, Rel-17 discusses a small data transmission (SDT) scheme in the RRC_INACTIVE state. In this scheme, the terminal 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.

[0079] In the RRC_INACTIVE state, the terminal can perform SDT according to the resources configured by the network device, that is, the terminal can send an SDT PUSCH to the network device in the RRC_INACTIVE state. There are many ways for the terminal to perform SDT, and the embodiments of the present application do not specifically limit this. For example, the terminal can perform SDT during the random access process. For another example, the terminal can perform SDT based on configured grant (CG) resources. For another example, the terminal can perform SDT based on pre-allocated uplink resource (PUR). These situations are introduced below.

[0080] Taking the random access process as an example, in the random access process, the resources for the terminal to perform SDT can be called RA-SDT resources. For the two-step random access process, the terminal can perform SDT in MsgA. Figure 3 For example, the terminal can carry a small data packet in MsgA. For the four-step random access process, the terminal can perform SDT in Msg3. Figure 2 For example, the terminal can carry a small data packet in Msg3.

[0081] 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 once. In the absence of a deactivation indication, the terminal 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 may use CG resources for SDT. CG resources used for SDT may also be referred to as CG-SDT resources.

[0082] 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 resources of CG type 2 require downlink control information (DCI) to indicate the activation and deactivation of the resources, and only the resources activated by DCI can be used.

[0083] 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 grant is CGtype 1, and if the rrc-ConfiguredUplinkGrant field is not configured, the type of configuration grant is CGtype 2.

[0084] In some embodiments, the terminal may also use PUR resources for SDT. PUR resources are preconfigured resources for the terminal to send uplink data in a non-connected state. The PUR resources may be periodic resources. PUR resources may be preconfigured based on a first type of uplink grant (granttype 1). In the RRC_INACTIVE state, the terminal may use the reserved PUR resources to directly transmit data.

[0085] Before performing SDT, the terminal needs to determine whether the terminal meets the conditions for triggering SDT. Only when the conditions for triggering SDT are met can the terminal perform SDT. If the conditions for triggering SDT are met, the terminal can initiate the SDT process. If the conditions for triggering SDT are not met, the terminal can initiate the RRC resume process. For example, the terminal can switch from the RRC_INACTIVE state to the RRC_CONNECTED state to transmit data.

[0086] The conditions for triggering SDT may include one or more of the following conditions: the data to be transmitted comes from a wireless bearer that can trigger SDT; the amount of data to be transmitted is less than a preconfigured data amount threshold (hereinafter also referred to as the third preset threshold); the measurement result of the downlink reference signal receiving power (reference signal receiving power, RSRP) is greater than the preconfigured RSRP threshold; there are valid SDT resources.

[0087] In some cases, the resources used by the first terminal for SDT may conflict with the resources used by the second terminal for random access. For example, taking the two-step random access process as an example, the first terminal sends the first small data packet on the first transmission opportunity, and the second terminal sends MsgA in the two-step random access process on the second transmission opportunity. If the resources of the first transmission opportunity and the resources of the second transmission opportunity at least partially overlap, that is, the resources of the first transmission opportunity and the resources of the second transmission opportunity conflict, then how the network device should handle this resource conflict has not yet been clearly specified.

[0088] If a resource conflict occurs, both the SDT PUSCH and the MsgA PUSCH may not be decoded correctly, which will result in reduced spectrum and energy efficiency. Taking CG-SDT resources as an example, CG-SDT PUSCH resources are usually configured for terminals through dedicated signaling. Therefore, other terminals performing random access cannot identify the CG-SDT PUSCH resources and thus cannot know that the MsgA PUSCH resources conflict with the CG-SDT PUSCH resources. Therefore, it is necessary to provide a processing rule for the conflict between the MsgA PUSCH resources and the CG-SDTPUSCH resources.

[0089] Based on this, the embodiments of the present application provide a method and apparatus for wireless communication, which provides a clear solution for network devices to handle resource conflicts. Figure 4 , the solution of the embodiment of the present application is introduced in detail.

[0090] like Figure 4 As shown, in step S410, the first terminal sends a small data packet to the network device in the first transmission opportunity. In other words, the first terminal sends a SDTPUSCH to the network device in the first transmission opportunity.

[0091] In some embodiments, the first terminal may send a small data packet to the network device under the condition of triggering SDT. The condition of triggering SDT can refer to the above description and will not be repeated here.

[0092] There may be multiple service types for small data packets, which are not specifically limited in the embodiments of the present application. For example, the service type for small data packets may include one or more of the following services: URLLC service, mMTC service, and eMBB service.

[0093] The first transmission opportunity can be understood as a transmission resource. The first transmission opportunity may include time domain resources and / or frequency domain resources. The resources of the first transmission opportunity may also be referred to as SDT resources. The resources of the first transmission opportunity may be, for example, CG-SDT resources, or PUR resources or RA-SDT resources. The resources of the first transmission opportunity may be configured by a network device to the first terminal, and the configuration method of the resources of the first transmission opportunity will be described in detail below.

[0094] It should be noted that the resource of the first transmission opportunity may also be referred to as an SDT PUSCH resource, or a first resource. The terms "resource of the first transmission opportunity", "SDT PUSCH resource", and "first resource" may be used interchangeably depending on the specific context. In some embodiments, the first resource may be a CG-SDT PUSCH.

[0095] It should be noted that, in the embodiment of the present application, the first terminal sends a small data packet to the network device, which only means that the first terminal sends a small data packet to the network device, and does not mean that the network device successfully receives the small data packet, or that the network device receives the small data packet. In some embodiments, the network device can determine whether to receive the small data packet based on whether the first transmission opportunity is valid. The method for determining whether the first transmission opportunity is valid will be described in detail below.

[0096] In step S420, the second terminal sends MsgA in the two-step random access process to the network device in the second transmission opportunity. In other words, the second terminal can send MsgA PUSCH to the network device in the second transmission opportunity. The second terminal and the first terminal can be two different terminals.

[0097] MsgA may include a random access preamble and uplink data. MsgA may also be referred to as MsgAPUSCH. The second transmission opportunity may be a PRACH opportunity (PRAChoccasion, PO). The second transmission opportunity may include time domain resources and / or frequency domain resources. The resources of the second transmission opportunity may be configured by the network device to the terminal. The resources of the second transmission opportunity may be dedicated resources for the second terminal. The resources of the second transmission opportunity may be configured to the second terminal by configuring authorization. In some embodiments, the network device may configure the resources of the second transmission opportunity to the second terminal through RRC signaling.

[0098] It should be noted that the resources of the second transmission opportunity may also be referred to as MsgA PUSCH resources or second resources. The terms “resources of the second transmission opportunity”, “MsgA PUSCH resources”, and “second resources” may be used interchangeably depending on the specific context.

[0099] Under the triggering of different random access events, the size of the data packet transmitted by the second terminal through MsgA PUSCH may also be different. Therefore, the second terminal can select the matching MsgA PUSCH resource according to the size of the data packet to be transmitted. At present, the communication system can support 2 different PUSCH configurations. The time-frequency resource position and size of PUSCH under different PUSCH configurations can be different, corresponding to different PUSCH transmission packet size requirements, so as to support the terminal to select a configuration that meets its needs to initiate random access.

[0100] It should be noted that the second terminal in the embodiment of the present application sends MsgA to the network device, which only means that the second terminal sends MsgA to the network device, and does not mean that the network device successfully receives MsgA or that the network device receives MsgA. In some embodiments, the network device can determine whether to receive MsgA based on whether the second transmission opportunity is valid. The method for determining whether the second transmission opportunity is valid will be described in detail below.

[0101] The resources of the first transmission opportunity and the resources of the second transmission opportunity at least partially overlap. For the convenience of description, the resources of the first transmission opportunity are referred to as first resources, and the resources of the second transmission opportunity are referred to as second resources. The at least partial overlap of the first resource and the second resource may refer to that part of the first resource overlaps part or all of the second resource, or part of the second resource overlaps part or all of the first resource. Resource overlap in the embodiments of the present application may refer to time domain resource overlap and / or frequency domain resource overlap.

[0102] In step S430, the network device determines one or more of the following events based on the first information: whether the first transmission opportunity is valid; whether the second transmission opportunity is valid.

[0103] The validity of the first transmission opportunity can be understood as the first terminal can use the first transmission opportunity to successfully send a small data packet, or the network device can receive the small data packet sent by the first terminal on the first transmission opportunity, or the network device first receives the small data packet sent by the first terminal on the first transmission opportunity, and after the transmission of the small data packet is completed, the network device receives MsgA sent by the second terminal on the second transmission opportunity.

[0104] The invalidity of the first transmission opportunity can be understood as the first terminal failing to successfully send the small data packet using the first transmission opportunity, or the network device abandons receiving the small data packet sent by the first terminal on the first transmission opportunity, or the network device first receives MsgA sent by the second terminal on the second transmission opportunity, and after the transmission of MsgA is completed, the network device receives the small data packet sent by the first terminal on the first transmission opportunity.

[0105] The validity of the second transmission opportunity can be understood as the second terminal can use the second transmission opportunity to successfully send MsgA, or the network device can receive MsgA sent by the second terminal on the second transmission opportunity, or the network device first receives MsgA sent by the second terminal on the second transmission opportunity, and after the transmission of MsgA is completed, the network device receives the small data packet sent by the first terminal on the first transmission opportunity.

[0106] The invalidity of the second transmission opportunity can be understood as the second terminal cannot successfully send MsgA using the second transmission opportunity, or the network device gives up receiving MsgA sent by the second terminal on the second transmission opportunity, or the network device first receives MsgA sent by the second terminal on the second transmission opportunity, and after the transmission of MsgA is completed, the network device receives the small data packet sent by the first terminal on the first transmission opportunity.

[0107] In some embodiments, the network device may determine whether the first transmission opportunity is valid based on the first information. If the first transmission opportunity is valid, the network device may directly determine that the second transmission opportunity is invalid. If the first transmission opportunity is invalid, the network device may directly determine that the second transmission opportunity is valid.

[0108] In some embodiments, the network device may determine whether the second transmission opportunity is valid based on the first information. If the second transmission opportunity is valid, the network device may directly determine that the first transmission opportunity is invalid. If the second transmission opportunity is invalid, the network device may directly determine that the first transmission opportunity is valid.

[0109] Of course, the network device may also determine whether the first transmission opportunity is valid and whether the second transmission opportunity is valid based on the first information.

[0110] If the first transmission opportunity is valid and the second transmission opportunity is invalid, the network device can only receive the first small data packet and give up receiving Msg A. If the first transmission opportunity is invalid and the second transmission opportunity is valid, the network device can only receive Msg A and give up receiving the first small data packet.

[0111] The first information may include one or more of the following information: the service type of the small data packet; the triggering condition for triggering the two-step random access; and the number of retransmissions of the small data packet.

[0112] The service type of the small data packet may include, for example, one or more of URLLC service, mMTC service, and eMBB service.

[0113] In the embodiment of the present application, a service type with a higher priority than MsgA and / or a service type with a lower priority than MsgA can be set, so that whether the first transmission opportunity or the second transmission opportunity is valid can be determined according to the service type.

[0114] As an example, the priority of the mMTC service can be higher than the priority of MsgA. If the service type of the small data packet is the mMTC service, the network device can determine that the first transmission opportunity is valid and / or the second transmission opportunity is invalid. Since the mMTC service is mainly used in the Internet of Things scenario, there are many small data packets in the mMTC service. Setting the priority of the mMTC service higher than the priority of MsgA can enable the mMTC service data to be transmitted in a timely manner, reduce the number of data retransmissions, and improve the user experience.

[0115] As another example, the priority of the eMBB service may be lower than the priority of MsgA. If the service type of the first small data packet is the eMBB service, the network device may determine that the first transmission opportunity is invalid, and / or that the second transmission opportunity is valid, such as Figure 5 As shown. Since the eMBB service is mainly aimed at high-traffic mobile broadband services, the number of its data packets is generally small or the importance is relatively low. Therefore, the priority of the eMBB service can be set lower than the priority of MsgA, so that the second terminal can successfully access randomly as soon as possible.

[0116] As another example, the priority of the URLLC service may be higher than the priority of MsgA. If the service type of the small data packet is the URLLC service, the network device may determine that the first transmission opportunity is valid, and / or that the second transmission opportunity is invalid, such as Figure 6 As shown. Since URLLC services are generally low-latency services, first transmitting data packets of URLLC services is beneficial to ensuring the latency requirements of data packets. Of course, in some embodiments, the priority of URLLC services may also be lower than the priority of MsgA. If the service type of the small data packet is URLLC service, the network device may determine that the first transmission opportunity is invalid, and / or that the second transmission opportunity is valid.

[0117] The first information may include a triggering condition for triggering two-step random access. The triggering condition for triggering two-step random access may include multiple conditions, for example, the triggering condition may include one or more of the following: initial access; RRC reconstruction; cell switching; when the uplink (UL) synchronization state is "out of synchronization", downlink (DL) or UL data in RRC_CONNECTED arrives; access from RRC_INACTIVE; secondary node (SN) establishment; request for other system information (SI); beam failure recovery; scheduling request (SR) failure. Other SI may, for example, include system information other than the master information block (MIB) and system information block 1 (SIB1) in the system information.

[0118] In some embodiments, a first trigger condition may be set, and when the trigger condition of the two-step random access is the first trigger condition, it may be determined that the first transmission opportunity is invalid, and / or that the second transmission opportunity is valid. The first trigger condition may include one or more of the following: requesting other SI access; beam failure recovery; SR failure.

[0119] Of course, in some embodiments, a second trigger condition may also be set. When the trigger condition of the two-step random access is the second trigger condition, it may be determined that the first transmission opportunity is valid and / or the second transmission opportunity is invalid. The second trigger condition may include one or more of the following: initial access; RRC reestablishment; cell switching; when the UL synchronization state is "out of sync", DL or UL data in RRC_CONNECTED arrives; access from RRC_INACTIVE; SN establishment.

[0120] The first information may include the number of retransmissions of the small data packet. If the number of retransmissions of the small data packet is higher than a preset threshold, the network device may determine that the first transmission opportunity is invalid, or that the second transmission opportunity is valid. When the number of retransmissions of the small data packet is higher than a preset threshold, the network device may abandon receiving the small data packet and receive MsgA, thereby avoiding the problem that the small data packet is retransmitted indefinitely, resulting in the second terminal being unable to successfully perform random access.

[0121] The above-mentioned first information can be implemented separately or in combination with the embodiments, and the embodiments of the present application do not make any specific limitations on this.

[0122] In some embodiments, if the first information satisfies the first condition, the first transmission opportunity is valid, or the second transmission opportunity is invalid. The first condition includes one or more of the following: the service type of the small data packet is URLLC service; the service type of the small data packet is mMTC service; the triggering condition for triggering two-step random access does not include beam failure recovery; the triggering condition for triggering two-step random access does not include SR failure; the triggering condition for triggering two-step random access does not include requesting SI.

[0123] In some embodiments, if the first information satisfies the second condition, the first transmission opportunity is invalid, or the first transmission opportunity is valid. The second condition includes one or more of the following: the service type of the small data packet is an eMBB service; the service type of the small data packet is a URLLC service; the triggering condition for triggering two-step random access includes beam failure recovery; the triggering condition for triggering two-step random access includes SR failure; the triggering condition for triggering two-step random access includes requesting other SI; the number of retransmissions of the small data packet is higher than a preset threshold.

[0124] As an example, if the service type of the small data packet is a URLLC service, it is possible to determine whether the first transmission opportunity is valid or the second transmission opportunity is valid based on the triggering condition for the second terminal to perform two-step random access. If the triggering condition for triggering the two-step random access includes the above-mentioned first triggering condition, the first transmission opportunity is invalid, or the second transmission opportunity is valid. The network device may abandon the transmission of the small data packet and perform the transmission of the MsgA PUSCH. If the triggering condition for triggering the two-step random access does not include the above-mentioned first triggering condition, the first transmission opportunity is valid, or the second transmission opportunity is invalid. The network device may transmit the small data packet and abandon the transmission of the MsgA PUSCH.

[0125] As another example, if the service type of the small data packet is an mMTC service, the network device may first transmit the small data packet and wait for MsgA PUSCH. However, when the number of retransmissions of the small data packet is greater than a preset threshold, the network device may abandon the transmission of the small data packet and transmit MsgA PUSCH.

[0126] The service type of the small data packet may be determined based on the first resource. In the embodiment of the present application, different resource pools may be configured for different services, and the network device may determine the service type of the small data packet based on the resource pool to which the first resource belongs.

[0127] For example, the service type of the small data packet may include multiple service types, and the multiple service types correspond to multiple resource pools respectively. Each resource pool in the multiple resource pools is used to transmit the small data packet of the service type corresponding thereto. The first terminal may select resources from the resource pool matching the service type of the small data packet to be sent to send the small data packet.

[0128] For example, the service types of small data packets may include eMBB services, URLLC services, and mMTC services. Figure 7 As shown, the resource pool corresponding to the eMBB service is R1, the resource pool corresponding to the URLLC service is R2, and the resource pool corresponding to the mMTC service is R3. If the small data packet to be sent in the first terminal belongs to the eMBB service, the first terminal can select resources from the resource pool R1 to send the small data packet. If the small data packet to be sent in the first terminal belongs to the URLLC service, the first terminal can select resources from the resource pool R2 to send the small data packet. If the small data packet to be sent in the first terminal belongs to the mMTC service, the first terminal can select resources from the resource pool R3 to send the small data packet.

[0129] In some embodiments, the sizes of resource pools corresponding to different services may be equal or unequal, and the embodiments of the present application do not specifically limit this. For example, the embodiments of the present application may differentiate resource pools according to the number of data packets of different service types, so that the transmission of data packets of different services can be balanced and resources can be reasonably configured.

[0130] For example, the resource pool size corresponding to the URLLC service is larger than the resource pool size corresponding to the mMTC service; the resource pool size corresponding to the mMTC service is larger than the resource pool size corresponding to the eMBB service; the resource pool size corresponding to the URLLC service is larger than the resource pool size corresponding to the eMBB service. Since the URLLC service has a low latency requirement, configuring more resources for the URLLC service can enable the URLLC service to be transmitted in a timely manner, which is conducive to meeting the service latency requirements.

[0131] The above-mentioned multiple resource pools may be configured by the network device for the first terminal, or may be predefined. In some embodiments, the network device may configure multiple resource pools to the terminal via an RRC connection release message.

[0132] by Figure 8 For example, in step S810, the network device may send an RRC connection release message to the first terminal. The RRC connection release message may include configuration information of three resource pools.

[0133] In step S820, after receiving the RRC connection release message, the first terminal enters the RRC_INACTIVE state.

[0134] In step S830, when the first terminal has a small data packet to send, the first terminal may select a corresponding resource pool according to the service type of the small data packet to be sent, and send the small data packet to the network device through the resources in the resource pool.

[0135] The above-mentioned multiple resource pools can correspond to multiple timers, that is, the embodiment of the present application can configure multiple timers for multiple resource pools respectively. Multiple timers are respectively used to limit the duration of the resources in the multiple resource pools for transmitting small data packets of corresponding business types. In other words, the multiple resource pools include a first resource pool, and the timer corresponding to the first resource pool is used to limit the duration of the resources of the first resource pool for transmitting small data packets of the business type corresponding to the first resource pool. The first terminal can use the resources in the first resource pool to transmit small data packets within the duration of the timer corresponding to the first resource pool.

[0136] Taking the first resource as a CG-SDT resource as an example, the parameters of the multiple timers can be indicated by the CG-SDT resource configuration information.

[0137] 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), timing advance (TA) verification criteria, allowed CG-SDT resource hopping, whether the CG-SDT resource configuration is valid for one or more opportunities, demodulation reference signal (DMRS) configuration, power control parameters, physical downlink control channel (PDCCH) search space, multiple repetitions of coverage enhancement (CE) and other ancillary parameters, and related parameters of multiple timers.

[0138] like Figure 7As shown, the timer corresponding to the resource pool of the eMBB service is T1, the timer corresponding to the resource pool of the URLLC service is T2, and the timer corresponding to the resource pool of the mMTC service is T3. Timer T1 is used to limit the duration of resource pool R1 used to transmit eMBB services. Timer T2 is used to limit the duration of resource pool R2 used to transmit URLLC services. Timer T3 is used to limit the duration of resource pool R3 used to transmit mMTC services.

[0139] During the validity period of timer T1, resources in resource pool R1 can be used to transmit small data packets of eMBB services. After timer T1 times out, resources in resource pool R1 cannot be used to transmit small data packets of eMBB services. In other words, after timer T1 times out, the first terminal cannot transmit small data packets of eMBB services.

[0140] During the validity period of timer T2, the resources in resource pool R2 can be used to transmit small data packets of URLLC services. After timer T2 times out, the resources in resource pool R2 cannot be used to transmit small data packets of URLLC services. In other words, after timer T2 times out, the first terminal cannot transmit small data packets of URLLC services.

[0141] During the validity period of timer T3, resources in resource pool R3 can be used to transmit small data packets of mMTC services. After timer T3 times out, resources in resource pool R3 cannot be used to transmit small data packets of mMTC services. In other words, after timer T3 times out, the first terminal cannot transmit small data packets of mMTC services.

[0142] The durations of the multiple timers corresponding to the above-mentioned multiple resource pools may be equal or unequal, and the embodiments of the present application do not specifically limit this. In some embodiments, the duration of the timer corresponding to the resource pool of the URLLC service is greater than the duration of the timer corresponding to the resource pool of the mMTC service; the duration of the timer corresponding to the resource pool of the mMTC service is greater than the duration of the timer corresponding to the resource pool of the eMBB service; the duration of the timer corresponding to the resource pool of the URLLC service is greater than the duration of the timer corresponding to the resource pool of the eMBB service.

[0143] In some embodiments, the duration of the timer may be determined according to the distribution of different services. For example, a longer timer may be set for a service type with a larger number of data packets, and a smaller timer may be set for a service type with a smaller number of data packets.

[0144] For example, assuming that the multiple service types include a first service and a second service, the first service corresponds to a first resource pool, the second service corresponds to a second resource pool, the first resource pool corresponds to a first timer, and the second resource pool corresponds to a second timer. If the number of data packets of the second service is greater than the number of data packets of the first service, the duration of the second timer may be greater than the duration of the first timer, so that more data packets of the second service can be transmitted.

[0145] In some embodiments, if the timer corresponding to a resource pool times out, the resources in the resource pool can be used for data transmission of other service types. Still taking the first service and the second service as an example, if the duration of the first timer is less than the duration of the second timer, after the first timer times out, the resources in the first resource pool can be used for the transmission of data packets of the second service.

[0146] For example, taking the above timers T1, T2 and T3 as an example, assuming that T2>T3>T1, after timer T1 times out, the resources in resource pool R1 can be shared with mMTC services and URLLC services. That is, after timer T1 times out, the first terminal can use the resources in resource pool R1 to transmit small data packets of mMTC services and URLLC services.

[0147] The following takes eMBB service, URLLC service, and mMTC service as examples. Figure 7 and Figure 8 The transmission process of data packets of different services is explained.

[0148] Fig. 9 The figure shows the case where the durations of the three timers are equal. Fig. 9 In step S910, the first terminal is in the RRC_INACTIVE state, and the first terminal can start timers T1, T2 and T3.

[0149] In step S920, the first terminal determines whether the timer T1, T2 or T3 has timed out.

[0150] In step S930, within the validity period of the timer T1, T2 or T3, the first terminal determines whether it needs to send a small data packet.

[0151] In step S940, if the first terminal needs to send a small data packet, the first terminal selects a resource in a resource pool corresponding to the small data packet to be sent, and sends the small data packet on the resource.

[0152] If the timer T1 or T2 or T3 times out, the first terminal releases the resources in the resource pool, and the first terminal cannot transmit the small data packet.

[0153] Fig.10The figure shows the case where the durations of the three timers are not equal. Fig.10 In step S1010, the first terminal is in the RRC_INACTIVE state, and the first terminal can use the resources in the resource pool to send a service data packet corresponding to the resource pool.

[0154] In step S1020, the first terminal starts the timers corresponding to the resource pools, and the first terminal starts the timers T1, T2 and T3.

[0155] In step S1030, the first terminal determines whether the timer T1 has timed out. If the timer T1 has not timed out, the first terminal may use the resources in the resource pool R1 to transmit the small data packet of the eMBB service.

[0156] In step S1040, if timer T1 times out, the first terminal may release resources in resource pool R1. In some embodiments, the first terminal may release resources in resource pool R1 to a shared resource pool so that resources in resource pool R1 can be used to transmit small data packets of URLLC services and mMTC services.

[0157] In step S1050, the first terminal determines whether the timer T3 has timed out. If the timer T3 has not timed out, the first terminal may use the resources in the resource pool R3 to transmit the small data packet of the mMTC service.

[0158] In step S1060, if timer T3 times out, the first terminal may release resources in resource pool R3. In some embodiments, the first terminal may release resources in resource pool R3 to a shared resource pool so that resources in resource pool R3 may be used to transmit small data packets of URLLC services.

[0159] In step S1070, the first terminal determines whether the timer T2 has timed out. If the timer T2 has not timed out, the first terminal can use the resources in the resource pool R2 to transmit small data packets of the URLLC service.

[0160] In step S1080, if the timer T2 times out, the first terminal can release the resources in the resource pool R2. In addition, the first terminal will not be able to transmit small data packets, that is, the first terminal will not be able to transmit small data packets of any service type.

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

[0162] Fig.11This is a schematic structural diagram of a wireless communication device provided by an embodiment of the present application. The device may be a network device. Fig.11 The network device shown may be any one of the network devices described above. The network device 1100 includes a determining unit 1110 .

[0163] The determination unit 1110 may be configured to determine, based on the first information, one or more of the following events: whether a first transmission opportunity for a first terminal to send a small data packet is valid; whether a second transmission opportunity for a second terminal to send a message A in a two-step random access process is valid, wherein resources of the second transmission opportunity at least partially overlap with resources of the first transmission opportunity.

[0164] The first information includes one or more of the following information: the service type of the small data packet; the triggering condition for triggering two-step random access; and the number of retransmissions of the small data packet.

[0165] In some embodiments, if the first information satisfies a first condition, the first transmission opportunity is valid, or the second transmission opportunity is invalid, and the first condition includes one or more of the following: the service type of the small data packet is URLLC service; the service type of the small data packet is mMTC service; the triggering condition for triggering two-step random access does not include beam failure recovery; the triggering condition for triggering two-step random access does not include SR failure; the triggering condition for triggering two-step random access does not include requesting other SI.

[0166] In some embodiments, if the first information satisfies a second condition, the first transmission opportunity is invalid, or the second transmission opportunity is valid, and the second condition includes one or more of the following: the service type of the small data packet is eMBB service; the service type of the small data packet is URLLC service; the triggering condition for triggering two-step random access includes beam failure recovery; the triggering condition for triggering two-step random access includes SR failure; the triggering condition for triggering two-step random access includes requesting other SI; the number of retransmissions of the small data packet is higher than a preset threshold.

[0167] In some embodiments, the service type of the small data packet is determined based on resources of the first transmission opportunity.

[0168] In some embodiments, the service type of the small data packet includes multiple service types, the multiple service types correspond to multiple resource pools respectively, and the resources in each resource pool of the multiple resource pools are used to transmit the small data packet of the corresponding service type.

[0169] In some embodiments, the resource pool size corresponding to the URLLC service is larger than the resource pool size corresponding to the mMTC service; the resource pool size corresponding to the mMTC service is larger than the resource pool size corresponding to the eMBB service; the resource pool size corresponding to the URLLC service is larger than the resource pool size corresponding to the eMBB service.

[0170] In some embodiments, the multiple resource pools correspond to multiple timers respectively, and the multiple timers are respectively used to limit the duration of time that the resources in the multiple resource pools are used to transmit small data packets of corresponding service types.

[0171] In some embodiments, the durations of the multiple timers are equal.

[0172] In some embodiments, the durations of the multiple timers are not equal.

[0173] In some embodiments, the multiple service types include a first service and a second service, the first service corresponds to a first resource pool, the second service corresponds to a second resource pool, the first resource pool corresponds to a first timer, and the second resource pool corresponds to a second timer. If the duration of the first timer is less than the duration of the second timer, then after the first timer times out, the resources in the first resource pool are used for the transmission of small data packets of the second service.

[0174] In some embodiments, the timer duration corresponding to the resource pool of the URLLC service is greater than the timer duration corresponding to the resource pool of the mMTC service; the timer duration corresponding to the resource pool of the mMTC service is greater than the timer duration corresponding to the resource pool of the eMBB service; the timer duration corresponding to the resource pool of the URLLC service is greater than the timer duration corresponding to the resource pool of the eMBB service.

[0175] In some embodiments, the resource of the first transmission opportunity is a CG-SDT resource.

[0176] Fig.12 1 is a schematic structural diagram of a wireless communication device provided by an embodiment of the present application. The device may be a first terminal. Fig.12 The first terminal shown may be any of the first terminals described above. The first terminal 1200 includes a sending unit 1210 .

[0177] The sending unit 1210 can be used to send a small data packet to a network device on a first transmission opportunity, where resources of the first transmission opportunity at least partially overlap with resources of a second transmission opportunity, and the second transmission opportunity is used by a second terminal to send message A in a two-step random access process to the network device.

[0178] Whether the first transmission opportunity or the second transmission opportunity is valid is determined based on first information. The first information includes one or more of the following information: the service type of the small data packet; the triggering condition for triggering two-step random access; and the number of retransmissions of the small data packet.

[0179] In some embodiments, if the first information satisfies a first condition, the first transmission opportunity is valid, or the second transmission opportunity is invalid, and the first condition includes one or more of the following: the service type of the small data packet is URLLC service; the service type of the small data packet is mMTC service; the triggering condition for triggering two-step random access does not include beam failure recovery; the triggering condition for triggering two-step random access does not include SR failure; the triggering condition for triggering two-step random access does not include requesting other SI.

[0180] In some embodiments, if the first information satisfies a second condition, the first transmission opportunity is invalid, or the second transmission opportunity is valid, and the second condition includes one or more of the following: the service type of the small data packet is eMBB service; the service type of the small data packet is URLLC service; the triggering condition for triggering two-step random access includes beam failure recovery; the triggering condition for triggering two-step random access includes SR failure; the triggering condition for triggering two-step random access includes requesting other SI; the number of retransmissions of the small data packet is higher than a preset threshold.

[0181] In some embodiments, the service type of the small data packet is determined based on resources of the first transmission opportunity.

[0182] In some embodiments, the service type of the small data packet includes multiple service types, the multiple service types correspond to multiple resource pools respectively, and the resources in each resource pool of the multiple resource pools are used to transmit the small data packet of the corresponding service type.

[0183] In some embodiments, the resource pool size corresponding to the URLLC service is larger than the resource pool size corresponding to the mMTC service; the resource pool size corresponding to the mMTC service is larger than the resource pool size corresponding to the eMBB service; the resource pool size corresponding to the URLLC service is larger than the resource pool size corresponding to the eMBB service.

[0184] In some embodiments, the multiple resource pools correspond to multiple timers respectively, and the multiple timers are respectively used to limit the duration of time that the resources in the multiple resource pools are used to transmit small data packets of corresponding service types.

[0185] In some embodiments, the durations of the multiple timers are equal.

[0186] In some embodiments, the durations of the multiple timers are not equal.

[0187] In some embodiments, the multiple service types include a first service and a second service, the first service corresponds to a first resource pool, the second service corresponds to a second resource pool, the first resource pool corresponds to a first timer, and the second resource pool corresponds to a second timer. If the duration of the first timer is less than the duration of the second timer, then after the first timer times out, the resources in the first resource pool are used for the transmission of small data packets of the second service.

[0188] In some embodiments, the timer duration corresponding to the resource pool of the URLLC service is greater than the timer duration corresponding to the resource pool of the mMTC service; the timer duration corresponding to the resource pool of the mMTC service is greater than the timer duration corresponding to the resource pool of the eMBB service; the timer duration corresponding to the resource pool of the URLLC service is greater than the timer duration corresponding to the resource pool of the eMBB service.

[0189] In some embodiments, the resource of the first transmission opportunity is a CG-SDT resource.

[0190] Fig.13 1 is a schematic structural diagram of a wireless communication device provided by an embodiment of the present application. The device may be a second terminal. Fig.13 The second terminal shown may be any second terminal described above. The second terminal 1300 includes a sending unit 1310 .

[0191] The sending unit 1310 can be used to send message A in the two-step random access process to the network device on the second transmission opportunity, the resources of the second transmission opportunity at least partially overlap with the resources of the first transmission opportunity, and the first transmission opportunity is used by the first terminal to send a small data packet to the network device.

[0192] Whether the first transmission opportunity or the second transmission opportunity is valid is determined based on first information. The first information includes one or more of the following information: the service type of the small data packet; the triggering condition for triggering two-step random access; and the number of retransmissions of the small data packet.

[0193] In some embodiments, if the first information satisfies a first condition, the first transmission opportunity is valid, or the second transmission opportunity is invalid, and the first condition includes one or more of the following: the service type of the small data packet is URLLC service; the service type of the small data packet is mMTC service; the triggering condition for triggering two-step random access does not include beam failure recovery; the triggering condition for triggering two-step random access does not include SR failure; the triggering condition for triggering two-step random access does not include requesting other SI.

[0194] In some embodiments, if the first information satisfies a second condition, the first transmission opportunity is invalid, or the second transmission opportunity is valid, and the second condition includes one or more of the following: the service type of the small data packet is eMBB service; the service type of the small data packet is URLLC service; the triggering condition for triggering two-step random access includes beam failure recovery; the triggering condition for triggering two-step random access includes SR failure; the triggering condition for triggering two-step random access includes requesting other SI; the number of retransmissions of the small data packet is higher than a preset threshold.

[0195] In some embodiments, the service type of the small data packet is determined based on resources of the first transmission opportunity.

[0196] In some embodiments, the service type of the small data packet includes multiple service types, the multiple service types correspond to multiple resource pools respectively, and the resources in each resource pool of the multiple resource pools are used to transmit the small data packet of the corresponding service type.

[0197] In some embodiments, the resource pool size corresponding to the URLLC service is larger than the resource pool size corresponding to the mMTC service; the resource pool size corresponding to the mMTC service is larger than the resource pool size corresponding to the eMBB service; the resource pool size corresponding to the URLLC service is larger than the resource pool size corresponding to the eMBB service.

[0198] In some embodiments, the multiple resource pools correspond to multiple timers respectively, and the multiple timers are respectively used to limit the duration of time that the resources in the multiple resource pools are used to transmit small data packets of corresponding service types.

[0199] In some embodiments, the durations of the multiple timers are equal.

[0200] In some embodiments, the durations of the multiple timers are not equal.

[0201] In some embodiments, the multiple service types include a first service and a second service, the first service corresponds to a first resource pool, the second service corresponds to a second resource pool, the first resource pool corresponds to a first timer, and the second resource pool corresponds to a second timer. If the duration of the first timer is less than the duration of the second timer, then after the first timer times out, the resources in the first resource pool are used for the transmission of small data packets of the second service.

[0202] In some embodiments, the timer duration corresponding to the resource pool of the URLLC service is greater than the timer duration corresponding to the resource pool of the mMTC service; the timer duration corresponding to the resource pool of the mMTC service is greater than the timer duration corresponding to the resource pool of the eMBB service; the timer duration corresponding to the resource pool of the URLLC service is greater than the timer duration corresponding to the resource pool of the eMBB service.

[0203] In some embodiments, the resource of the first transmission opportunity is a CG-SDT resource.

[0204] Fig.14 It is a schematic structural diagram of the device of an embodiment of the present application. Fig.14 The dotted line in the figure indicates that the unit or module is optional. The device 1400 can be used to implement the method described in the above method embodiment. The device 1400 can be one or more of a chip, a first terminal, a second terminal, and a network device.

[0205] The device 1400 may include one or more processors 1410. The processor 1410 may support the device 1400 to implement the method described in the above method embodiment. The processor 1410 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.

[0206] The apparatus 1400 may further include one or more memories 1420. The memory 1420 stores a program, which can be executed by the processor 1410, so that the processor 1410 executes the method described in the above method embodiment. The memory 1420 may be independent of the processor 1410 or integrated in the processor 1410.

[0207] The apparatus 1400 may further include a transceiver 1430. The processor 1410 may communicate with other devices or chips through the transceiver 1430. For example, the processor 1410 may transmit and receive data with other devices or chips through the transceiver 1430.

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

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

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

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

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

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

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

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

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

[0217] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using 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 (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)).

[0218] 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 network device determines one or more of the following events based on the first information: Whether a first transmission opportunity for the first terminal to send a small data packet is valid; Whether a second transmission opportunity for the second terminal to send message A in the two-step random access process is valid; The resources of the second transmission opportunity at least partially overlap with the resources of the first transmission opportunity; the service type of the small data packet is determined based on the resources of the first transmission opportunity; the service type of the small data packet includes multiple service types, the multiple service types correspond to multiple resource pools respectively, and the resources in each resource pool of the multiple resource pools are used to transmit the small data packet of the service type corresponding to it; The first information includes one or more of the following information: The service type of the small data packet; The number of retransmissions of the small data packet.

2. The method according to claim 1, characterized in that The first information also includes a triggering condition for triggering two-step random access. If the first information satisfies the first condition, the first transmission opportunity is valid, or the second transmission opportunity is invalid. The first condition includes one or more of the following: The service type of the small data packet is a high reliability and low latency URLLC service; The service type of the small data packet is a massive machine type communication (mMTC) service; The triggering conditions for triggering two-step random access do not include beam failure recovery; The triggering condition for triggering two-step random access does not include the failure of the scheduling request SR; The triggering condition for triggering two-step random access does not include requesting other system information SI.

3. The method according to claim 1, characterized in that The first information further includes a triggering condition for triggering two-step random access. If the first information satisfies a second condition, the first transmission opportunity is invalid, or the second transmission opportunity is valid. The second condition includes one or more of the following: The service type of the small data packet is an enhanced mobile broadband eMBB service; The service type of the small data packet is URLLC service; The triggering conditions for triggering two-step random access include beam failure recovery; The triggering conditions for triggering two-step random access include SR failure; The triggering conditions for triggering two-step random access include requesting other SI; The number of retransmissions of the small data packet is higher than a preset threshold.

4. The method according to any one of claims 1 to 3, characterized in that The resource pool size corresponding to the URLLC service is larger than the resource pool size corresponding to the mMTC service; The size of the resource pool corresponding to the mMTC service is larger than the size of the resource pool corresponding to the eMBB service; The resource pool size corresponding to the URLLC service is larger than the resource pool size corresponding to the eMBB service.

5. The method according to any one of claims 1 to 3, characterized in that: The multiple resource pools correspond to multiple timers respectively, and the multiple timers are respectively used to limit the duration of time that the resources in the multiple resource pools are used to transmit small data packets of corresponding service types.

6. The method according to claim 5, characterized in that The durations of the multiple timers are equal.

7. The method according to claim 5, characterized in that The durations of the multiple timers are not equal.

8. The method according to claim 7, characterized in that The multiple service types include a first service and a second service, the first service corresponds to a first resource pool, the second service corresponds to a second resource pool, the first resource pool corresponds to a first timer, and the second resource pool corresponds to a second timer, If the duration of the first timer is shorter than the duration of the second timer, then after the first timer times out, the resources in the first resource pool are used for transmission of small data packets of the second service.

9. The method according to claim 5, characterized in that The timer duration corresponding to the resource pool of the URLLC service is greater than the timer duration corresponding to the resource pool of the mMTC service; The timer duration corresponding to the resource pool of the mMTC service is greater than the timer duration corresponding to the resource pool of the eMBB service; The timer duration corresponding to the resource pool of the URLLC service is greater than the timer duration corresponding to the resource pool of the eMBB service.

10. The method according to any one of claims 1 to 3, characterized in that: The resource of the first transmission opportunity is a CG-SDT resource configured to authorize small data transmission.

11. A wireless communication method, characterized in that: include: A first terminal sends a small data packet to a network device on a first transmission opportunity, resources of the first transmission opportunity at least partially overlap with resources of a second transmission opportunity, the second transmission opportunity is used by the second terminal to send a message A in a two-step random access process to the network device, whether the first transmission opportunity or the second transmission opportunity is valid is determined based on first information, and a service type of the small data packet is determined based on resources of the first transmission opportunity; the service type of the small data packet includes multiple service types, the multiple service types correspond to multiple resource pools respectively, and resources in each of the multiple resource pools are used to transmit a small data packet of a service type corresponding to it; The first information includes one or more of the following information: The service type of the small data packet; The number of retransmissions of the small data packet.

12. The method according to claim 11, characterized in that The first information also includes a triggering condition for triggering two-step random access. If the first information satisfies the first condition, the first transmission opportunity is valid, or the second transmission opportunity is invalid. The first condition includes one or more of the following: The service type of the small data packet is a high reliability and low latency URLLC service; The service type of the small data packet is a massive machine type communication (mMTC) service; The triggering conditions for triggering two-step random access do not include beam failure recovery; The triggering condition for triggering two-step random access does not include the failure of the scheduling request SR; The triggering condition for triggering two-step random access does not include requesting other system information SI.

13. The method according to claim 11, characterized in that The first information further includes a triggering condition for triggering two-step random access. If the first information satisfies a second condition, the first transmission opportunity is invalid, or the second transmission opportunity is valid. The second condition includes one or more of the following: The service type of the small data packet is an enhanced mobile broadband eMBB service; The service type of the small data packet is URLLC service; The triggering conditions for triggering two-step random access include beam failure recovery; The triggering conditions for triggering two-step random access include SR failure; The triggering conditions for triggering two-step random access include requesting other SI; The number of retransmissions of the small data packet is higher than a preset threshold.

14. The method according to any one of claims 11 to 13, characterized in that The resource pool size corresponding to the URLLC service is larger than the resource pool size corresponding to the mMTC service; The size of the resource pool corresponding to the mMTC service is larger than the size of the resource pool corresponding to the eMBB service; The resource pool size corresponding to the URLLC service is larger than the resource pool size corresponding to the eMBB service.

15. The method according to any one of claims 11 to 13, characterized in that The multiple resource pools correspond to multiple timers respectively, and the multiple timers are respectively used to limit the duration of time that the resources in the multiple resource pools are used to transmit small data packets of corresponding service types.

16. The method according to claim 15, characterized in that The durations of the multiple timers are equal.

17. The method according to claim 15, characterized in that The durations of the multiple timers are not equal.

18. The method according to claim 17, characterized in that The multiple service types include a first service and a second service, the first service corresponds to a first resource pool, the second service corresponds to a second resource pool, the first resource pool corresponds to a first timer, and the second resource pool corresponds to a second timer, If the duration of the first timer is shorter than the duration of the second timer, then after the first timer times out, the resources in the first resource pool are used for transmission of small data packets of the second service.

19. The method according to claim 15, characterized in that The timer duration corresponding to the resource pool of the URLLC service is greater than the timer duration corresponding to the resource pool of the mMTC service; The timer duration corresponding to the resource pool of the mMTC service is greater than the timer duration corresponding to the resource pool of the eMBB service; The timer duration corresponding to the resource pool of the URLLC service is greater than the timer duration corresponding to the resource pool of the eMBB service.

20. The method according to any one of claims 11 to 13, characterized in that The resource of the first transmission opportunity is a CG-SDT resource configured to authorize small data transmission.

21. A wireless communication method, characterized in that: include: The second terminal sends a message A in a two-step random access process to the network device on a second transmission opportunity, the resources of the second transmission opportunity at least partially overlap with the resources of the first transmission opportunity, the first transmission opportunity is used by the first terminal to send a small data packet to the network device, whether the first transmission opportunity or the second transmission opportunity is valid is determined based on the first information, and the service type of the small data packet is determined based on the resources of the first transmission opportunity; the service type of the small data packet includes multiple service types, the multiple service types correspond to multiple resource pools respectively, and the resources in each of the multiple resource pools are used to transmit a small data packet of a service type corresponding to it; The first information includes one or more of the following information: The service type of the small data packet; The number of retransmissions of the small data packet.

22. The method according to claim 21, characterized in that The first information also includes a triggering condition for triggering two-step random access. If the first information satisfies the first condition, the first transmission opportunity is valid, or the second transmission opportunity is invalid. The first condition includes one or more of the following: The service type of the small data packet is a high reliability and low latency URLLC service; The service type of the small data packet is a massive machine type communication (mMTC) service; The triggering conditions for triggering two-step random access do not include beam failure recovery; The triggering condition for triggering two-step random access does not include the failure of the scheduling request SR; The triggering condition for triggering two-step random access does not include requesting other system information SI.

23. The method according to claim 21, characterized in that The first information further includes a triggering condition for triggering two-step random access. If the first information satisfies a second condition, the first transmission opportunity is invalid, or the second transmission opportunity is valid. The second condition includes one or more of the following: The service type of the small data packet is an enhanced mobile broadband eMBB service; The service type of the small data packet is URLLC service; The triggering conditions for triggering two-step random access include beam failure recovery; The triggering conditions for triggering two-step random access include SR failure; The triggering conditions for triggering two-step random access include requesting other SI; The number of retransmissions of the small data packet is higher than a preset threshold.

24. The method according to any one of claims 21 to 23, characterized in that The resource pool size corresponding to the URLLC service is larger than the resource pool size corresponding to the mMTC service; The size of the resource pool corresponding to the mMTC service is larger than the size of the resource pool corresponding to the eMBB service; The resource pool size corresponding to the URLLC service is larger than the resource pool size corresponding to the eMBB service.

25. The method according to any one of claims 21 to 23, characterized in that The multiple resource pools correspond to multiple timers respectively, and the multiple timers are respectively used to limit the duration of time that the resources in the multiple resource pools are used to transmit small data packets of corresponding service types.

26. The method according to claim 25, characterized in that The durations of the multiple timers are equal.

27. The method according to claim 25, characterized in that The durations of the multiple timers are not equal.

28. The method according to claim 27, characterized in that The multiple service types include a first service and a second service, the first service corresponds to a first resource pool, the second service corresponds to a second resource pool, the first resource pool corresponds to a first timer, and the second resource pool corresponds to a second timer, If the duration of the first timer is shorter than the duration of the second timer, then after the first timer times out, the resources in the first resource pool are used for transmission of small data packets of the second service.

29. The method according to claim 25, characterized in that The timer duration corresponding to the resource pool of the URLLC service is greater than the timer duration corresponding to the resource pool of the mMTC service; The timer duration corresponding to the resource pool of the mMTC service is greater than the timer duration corresponding to the resource pool of the eMBB service; The timer duration corresponding to the resource pool of the URLLC service is greater than the timer duration corresponding to the resource pool of the eMBB service.

30. The method according to any one of claims 21 to 23, characterized in that The resource of the first transmission opportunity is a CG-SDT resource configured to authorize small data transmission.

31. A wireless communication device, characterized in that: The device is a network device, and the device includes: A determining unit, configured to determine one or more of the following events based on the first information: Whether a first transmission opportunity for the first terminal to send a small data packet is valid; Whether a second transmission opportunity for the second terminal to send message A in the two-step random access process is valid; The resources of the second transmission opportunity at least partially overlap with the resources of the first transmission opportunity; the service type of the small data packet is determined based on the resources of the first transmission opportunity; the service type of the small data packet includes multiple service types, the multiple service types correspond to multiple resource pools respectively, and the resources in each resource pool of the multiple resource pools are used to transmit the small data packet of the service type corresponding to it; The first information includes one or more of the following information: The service type of the small data packet; The number of retransmissions of the small data packet.

32. The device according to claim 31, characterized in that The first information also includes a triggering condition for triggering two-step random access. If the first information satisfies the first condition, the first transmission opportunity is valid, or the second transmission opportunity is invalid. The first condition includes one or more of the following: The service type of the small data packet is a high reliability and low latency URLLC service; The service type of the small data packet is a massive machine type communication (mMTC) service; The triggering conditions for triggering two-step random access do not include beam failure recovery; The triggering condition for triggering two-step random access does not include the failure of the scheduling request SR; The triggering condition for triggering two-step random access does not include requesting other system information SI.

33. The device according to claim 31, characterized in that The first information further includes a triggering condition for triggering two-step random access. If the first information satisfies a second condition, the first transmission opportunity is invalid, or the second transmission opportunity is valid. The second condition includes one or more of the following: The service type of the small data packet is an enhanced mobile broadband eMBB service; The service type of the small data packet is URLLC service; The triggering conditions for triggering two-step random access include beam failure recovery; The triggering conditions for triggering two-step random access include SR failure; The triggering conditions for triggering two-step random access include requesting other SI; The number of retransmissions of the small data packet is higher than a preset threshold.

34. The device according to any one of claims 31 to 33, characterized in that The resource pool size corresponding to the URLLC service is larger than the resource pool size corresponding to the mMTC service; The size of the resource pool corresponding to the mMTC service is larger than the size of the resource pool corresponding to the eMBB service; The resource pool size corresponding to the URLLC service is larger than the resource pool size corresponding to the eMBB service.

35. The device according to any one of claims 31 to 33, characterized in that The multiple resource pools correspond to multiple timers respectively, and the multiple timers are respectively used to limit the duration of time that the resources in the multiple resource pools are used to transmit small data packets of corresponding service types.

36. The device according to claim 35, characterized in that The durations of the multiple timers are equal.

37. The device according to claim 35, characterized in that The durations of the multiple timers are not equal.

38. The device according to claim 37, characterized in that The multiple service types include a first service and a second service, the first service corresponds to a first resource pool, the second service corresponds to a second resource pool, the first resource pool corresponds to a first timer, and the second resource pool corresponds to a second timer, If the duration of the first timer is shorter than the duration of the second timer, then after the first timer times out, the resources in the first resource pool are used for transmission of small data packets of the second service.

39. The device according to claim 35, characterized in that The timer duration corresponding to the resource pool of the URLLC service is greater than the timer duration corresponding to the resource pool of the mMTC service; The timer duration corresponding to the resource pool of the mMTC service is greater than the timer duration corresponding to the resource pool of the eMBB service; The timer duration corresponding to the resource pool of the URLLC service is greater than the timer duration corresponding to the resource pool of the eMBB service.

40. The device according to any one of claims 31 to 33, characterized in that The resource of the first transmission opportunity is a CG-SDT resource configured to authorize small data transmission.

41. A wireless communication device, characterized in that: The device is a first terminal, and the device includes: A sending unit, configured to send a small data packet to a network device on a first transmission opportunity, wherein resources of the first transmission opportunity at least partially overlap with resources of a second transmission opportunity, wherein the second transmission opportunity is used by a second terminal to send a message A in a two-step random access process to the network device, wherein whether the first transmission opportunity or the second transmission opportunity is valid is determined based on first information, and a service type of the small data packet is determined based on resources of the first transmission opportunity; the service type of the small data packet includes multiple service types, wherein the multiple service types correspond to multiple resource pools respectively, and resources in each of the multiple resource pools are used to transmit a small data packet of a service type corresponding thereto; The first information includes one or more of the following information: The service type of the small data packet; The number of retransmissions of the small data packet.

42. The device according to claim 41, characterized in that The first information also includes a triggering condition for triggering two-step random access. If the first information satisfies the first condition, the first transmission opportunity is valid, or the second transmission opportunity is invalid. The first condition includes one or more of the following: The service type of the small data packet is a high reliability and low latency URLLC service; The service type of the small data packet is a massive machine type communication (mMTC) service; The triggering conditions for triggering two-step random access do not include beam failure recovery; The triggering condition for triggering two-step random access does not include the failure of the scheduling request SR; The triggering condition for triggering two-step random access does not include requesting other system information SI.

43. The device according to claim 41, characterized in that The first information further includes a triggering condition for triggering two-step random access. If the first information satisfies a second condition, the first transmission opportunity is invalid, or the second transmission opportunity is valid. The second condition includes one or more of the following: The service type of the small data packet is an enhanced mobile broadband eMBB service; The service type of the small data packet is URLLC service; The triggering conditions for triggering two-step random access include beam failure recovery; The triggering conditions for triggering two-step random access include SR failure; The triggering conditions for triggering two-step random access include requesting other SI; The number of retransmissions of the small data packet is higher than a preset threshold.

44. The device according to any one of claims 41 to 43, characterized in that The resource pool size corresponding to the URLLC service is larger than the resource pool size corresponding to the mMTC service; The size of the resource pool corresponding to the mMTC service is larger than the size of the resource pool corresponding to the eMBB service; The resource pool size corresponding to the URLLC service is larger than the resource pool size corresponding to the eMBB service.

45. The device according to any one of claims 41 to 43, characterized in that The multiple resource pools correspond to multiple timers respectively, and the multiple timers are respectively used to limit the duration of time that the resources in the multiple resource pools are used to transmit small data packets of corresponding service types.

46. ​​The device according to claim 45, characterized in that The durations of the multiple timers are equal.

47. The device according to claim 45, characterized in that The durations of the multiple timers are not equal.

48. The device according to claim 47, characterized in that The multiple service types include a first service and a second service, the first service corresponds to a first resource pool, the second service corresponds to a second resource pool, the first resource pool corresponds to a first timer, and the second resource pool corresponds to a second timer, If the duration of the first timer is shorter than the duration of the second timer, then after the first timer times out, the resources in the first resource pool are used for transmission of small data packets of the second service.

49. The device according to claim 45, characterized in that The timer duration corresponding to the resource pool of the URLLC service is greater than the timer duration corresponding to the resource pool of the mMTC service; The timer duration corresponding to the resource pool of the mMTC service is greater than the timer duration corresponding to the resource pool of the eMBB service; The timer duration corresponding to the resource pool of the URLLC service is greater than the timer duration corresponding to the resource pool of the eMBB service.

50. The device according to any one of claims 41 to 43, characterized in that The resource of the first transmission opportunity is a CG-SDT resource configured to authorize small data transmission.

51. A wireless communication device, characterized in that: The device is a second terminal, and the device includes: A sending unit, configured to send a message A in a two-step random access process to a network device on a second transmission opportunity, wherein resources of the second transmission opportunity at least partially overlap with resources of a first transmission opportunity, wherein the first transmission opportunity is used by a first terminal to send a small data packet to the network device, and whether the first transmission opportunity or the second transmission opportunity is valid is determined based on first information, and a service type of the small data packet is determined based on resources of the first transmission opportunity; the service type of the small data packet includes multiple service types, wherein the multiple service types correspond to multiple resource pools respectively, and resources in each of the multiple resource pools are used to transmit a small data packet of a service type corresponding to the small data packet; The first information includes one or more of the following information: The service type of the small data packet; The number of retransmissions of the small data packet.

52. The device according to claim 51, characterized in that The first information also includes a triggering condition for triggering two-step random access. If the first information satisfies the first condition, the first transmission opportunity is valid, or the second transmission opportunity is invalid. The first condition includes one or more of the following: The service type of the small data packet is a high reliability and low latency URLLC service; The service type of the small data packet is a massive machine type communication (mMTC) service; The triggering conditions for triggering two-step random access do not include beam failure recovery; The triggering condition for triggering two-step random access does not include the failure of the scheduling request SR; The triggering condition for triggering two-step random access does not include requesting other system information SI.

53. The device according to claim 51, characterized in that The first information further includes a triggering condition for triggering two-step random access. If the first information satisfies a second condition, the first transmission opportunity is invalid, or the second transmission opportunity is valid. The second condition includes one or more of the following: The service type of the small data packet is an enhanced mobile broadband eMBB service; The service type of the small data packet is URLLC service; The triggering conditions for triggering two-step random access include beam failure recovery; The triggering conditions for triggering two-step random access include SR failure; The triggering conditions for triggering two-step random access include requesting other SI; The number of retransmissions of the small data packet is higher than a preset threshold.

54. The device according to any one of claims 51 to 53, characterized in that The resource pool size corresponding to the URLLC service is larger than the resource pool size corresponding to the mMTC service; The size of the resource pool corresponding to the mMTC service is larger than the size of the resource pool corresponding to the eMBB service; The resource pool size corresponding to the URLLC service is larger than the resource pool size corresponding to the eMBB service.

55. The device according to any one of claims 51 to 53, characterized in that The multiple resource pools correspond to multiple timers respectively, and the multiple timers are respectively used to limit the duration of time that the resources in the multiple resource pools are used to transmit small data packets of corresponding service types.

56. The device according to claim 55, characterized in that The durations of the multiple timers are equal.

57. The device according to claim 55, characterized in that The durations of the multiple timers are not equal.

58. The device according to claim 57, characterized in that The multiple service types include a first service and a second service, the first service corresponds to a first resource pool, the second service corresponds to a second resource pool, the first resource pool corresponds to a first timer, and the second resource pool corresponds to a second timer, If the duration of the first timer is shorter than the duration of the second timer, then after the first timer times out, the resources in the first resource pool are used for transmission of small data packets of the second service.

59. The device according to claim 55, characterized in that The timer duration corresponding to the resource pool of the URLLC service is greater than the timer duration corresponding to the resource pool of the mMTC service; The timer duration corresponding to the resource pool of the mMTC service is greater than the timer duration corresponding to the resource pool of the eMBB service; The timer duration corresponding to the resource pool of the URLLC service is greater than the timer duration corresponding to the resource pool of the eMBB service.

60. The device according to any one of claims 51 to 53, characterized in that The resource of the first transmission opportunity is a CG-SDT resource configured to authorize small data transmission.

61. A wireless communication device, characterized in that: The device comprises a memory, a processor and a communication interface, wherein the memory is used to store a program, and the processor is used to call the program in the memory, so that the device executes the method according to any one of claims 1 to 30.

62. 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 30.

63. 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 30.

64. 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 30.

65. 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 30.

Images