WO2023231005A1 - 无线通信的方法及装置 - Google Patents

无线通信的方法及装置 Download PDF

Info

Publication number
WO2023231005A1
WO2023231005A1 PCT/CN2022/096908 CN2022096908W WO2023231005A1 WO 2023231005 A1 WO2023231005 A1 WO 2023231005A1 CN 2022096908 W CN2022096908 W CN 2022096908W WO 2023231005 A1 WO2023231005 A1 WO 2023231005A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
resource pool
small data
transmission opportunity
data packet
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2022/096908
Other languages
English (en)
French (fr)
Inventor
吕玲
赵铮
杨中志
钱鹏鹤
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Quectel Wireless Solutions Co Ltd
Original Assignee
Quectel Wireless Solutions Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Quectel Wireless Solutions Co Ltd filed Critical Quectel Wireless Solutions Co Ltd
Priority to PCT/CN2022/096908 priority Critical patent/WO2023231005A1/zh
Priority to EP22944334.6A priority patent/EP4535893A4/en
Priority to CN202280002813.7A priority patent/CN115316024B/zh
Publication of WO2023231005A1 publication Critical patent/WO2023231005A1/zh
Priority to US18/955,867 priority patent/US20250089102A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/51—Allocation or scheduling criteria for wireless resources based on terminal or device properties
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/006—Transmission of channel access control information in the downlink, i.e. towards the terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H04W74/0836—Random access procedures, e.g. with 4-step access with 2-step access

Definitions

  • the present application relates to the field of communication technology, and more specifically, to a wireless communication method and device.
  • the communication system allows the terminal to send small data packets to the network device in the radio resource control (RRC) inactive (INACTIVE) state.
  • RRC radio resource control
  • the resources used by one terminal to send small data packets may overlap with the resources used by another terminal for random access, that is, resource conflicts occur.
  • this application provides a wireless communication method and device.
  • Various aspects involved in the embodiments of this application are introduced below.
  • a first aspect provides a wireless communication method, including: a network device determining 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 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 second transmission opportunity
  • One 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.
  • a wireless communication method including: a first terminal sending 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 the second transmission opportunity. , the second transmission opportunity is used by the second terminal to send message A in the 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 the first information,
  • the first information includes one or more of the following information: the service type of the small data packet; a triggering condition for triggering two-step random access; and the number of retransmissions of the small data packet.
  • a wireless communication method including: a second terminal sending a message A in a two-step random access process to a network device on a second transmission opportunity, where the resources of the second transmission opportunity are the same as those of the first transmission opportunity.
  • Resources of transmission opportunities at least partially overlap, the first transmission opportunity is used by the first terminal to send small data packets to the network device, and whether the first transmission opportunity or the second transmission opportunity is valid is determined based on the first information,
  • the first information includes one or more of the following information: the service type of the small data packet; a triggering condition for triggering two-step random access; and the number of retransmissions of the small data packet.
  • a wireless communication device where 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: for the first Whether the first transmission opportunity for the terminal to send small data packets 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 are the same as the The resources of the first transmission opportunity at least partially overlap; 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; the small data packet The number of retransmissions.
  • a wireless communication device is provided.
  • the device is a first terminal.
  • the device includes: a sending unit configured to send a small data packet to a network device on a first transmission opportunity.
  • the first transmission opportunity The resources of the opportunity at least partially overlap with the resources of the second transmission opportunity.
  • the second transmission opportunity is used for the second terminal to send the message A in the two-step random access process to the network device.
  • the first transmission opportunity or the Whether 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 two-step random access; The number of retransmissions of small data packets.
  • a wireless communication device where the device is a second terminal, and the device includes: a sending unit configured to send a message 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 for the first terminal to send small data packets to the network device.
  • the first transmission opportunity or the Whether 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 two-step random access; The number of retransmissions of small data packets.
  • a seventh aspect provides a wireless communication device, including a processor, a memory, and a communication interface.
  • the memory is used to store one or more computer programs.
  • the processor is used to call the computer program in the memory so that the The terminal device performs the method described in any one of the first to third aspects.
  • An eighth aspect provides a device, including a processor, for calling a program from a memory to execute the method described in any one of the first to third aspects.
  • a chip including a processor for calling a program from a memory, so that a device installed with the chip executes the method described in any one of the first to third aspects.
  • a computer-readable storage medium is provided with a program stored thereon, and the program causes a computer to execute the method described in any one of the first to third aspects.
  • a computer program product including a program that causes a computer to execute the method described in any one of the first to third aspects.
  • a computer program is provided, the computer program causing a computer to execute the method described in any one of the first to third aspects.
  • the network device 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.
  • the network device can introduce the first information, a clear solution is provided for network devices to handle resource conflicts.
  • FIG. 1 is an example system architecture diagram of a communication system applicable to embodiments of the present application.
  • Figure 2 is a schematic flow chart of a four-step random access process.
  • Figure 3 is a schematic flow chart of a two-step random access process.
  • Figure 4 is a schematic flow chart of a wireless communication method provided by an embodiment of the present application.
  • Figure 5 is a schematic diagram of determining whether a transmission opportunity is valid according to an embodiment of the present application.
  • Figure 6 is a schematic diagram of determining whether a transmission opportunity is valid according to another embodiment of the present application.
  • Figure 7 is a schematic diagram of the correspondence between service types, resource pools, and timers provided by an embodiment of the present application.
  • Figure 8 is a schematic flow chart of SDT performed by a terminal device provided by an embodiment of the present application.
  • Figure 9 is a schematic flowchart of timer-based transmission of small data packets provided by an embodiment of the present application.
  • Figure 10 is a schematic flow chart of transmitting small data packets based on a timer provided by another embodiment of the present application.
  • Figure 11 is a schematic structural diagram of a network device provided by an embodiment of the present application.
  • Figure 12 is a schematic structural diagram of a first terminal provided by another embodiment of the present application.
  • Figure 13 is a schematic structural diagram of a second terminal provided by another embodiment of the present application.
  • Figure 14 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 1 is a wireless communication system 100 applied in the embodiment of the present application.
  • the wireless communication system 100 may include a network device 110 and a terminal 120.
  • Network device 110 may be a device that communicates with terminal 120.
  • Network device 110 may provide communications coverage for a specific geographic area and may communicate with terminals 120 located within the coverage area.
  • Figure 1 exemplarily shows one network device and two terminals.
  • the wireless communication system 100 may include multiple network devices and other numbers of terminals may be included within the coverage of each network device. This application implements This example does not limit this.
  • the wireless communication system 100 may also include other network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.
  • network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.
  • the terminal in the embodiment of this application may also be called user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (mobile Terminal, MT) , remote station, remote terminal, mobile device, user terminal, terminal, wireless communications device, user agent or user device.
  • UE user equipment
  • MS mobile station
  • MT mobile terminal
  • remote station remote terminal
  • mobile device user terminal
  • terminal wireless communications device
  • user agent or user 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 users, and may be used to connect people, things, and machines, such as handheld devices and vehicle-mounted devices with wireless connection functions.
  • the terminal in the embodiment of the present application may be a mobile phone (mobile phone), a tablet computer (Pad), a notebook computer, a handheld computer, a mobile internet device (mobile internet device, MID), a wearable device, or a virtual reality (VR) ) equipment, augmented reality (AR) equipment, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, smart grids Wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, etc.
  • the UE may be used to act as a base station.
  • a UE may act as a scheduling entity that provides sidelink signals between UEs in V2X or D2D, etc.
  • cell phones and cars use sidelink signals to communicate with each other.
  • Cell phones and smart home devices communicate between each other without having to relay communication signals through base stations.
  • the network device in the embodiment of the present application may be a device used to communicate with a terminal.
  • the network device may also be called an access network device or a wireless access network device.
  • the network device may be a base station.
  • the network device in the embodiment of this application may refer to a radio access network (radio access network, RAN) node (or device) that connects the terminal to the wireless network.
  • radio access network radio access network, RAN
  • the base station can broadly cover various names as follows, or be replaced with the following names, such as: Node B (NodeB), evolved base station (evolved NodeB, eNB), next generation base station (next generation NodeB, gNB), relay station, Access point, transmission point (transmitting and receiving point, TRP), transmitting point (TP), main station MeNB, secondary station SeNB, multi-standard wireless (MSR) node, home base station, network controller, access node , wireless node, access point (AP), transmission node, transceiver node, base band unit (BBU), radio remote unit (Remote Radio Unit, RRU), active antenna unit (active antenna unit) , AAU), radio head (remote radio head, RRH), central unit (central unit, CU), distributed unit (distributed unit, DU), positioning node, etc.
  • NodeB Node B
  • eNB evolved base station
  • next generation NodeB next generation NodeB, gNB
  • relay station Access point
  • the base station may be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof.
  • a base station may also refer to a communication module, modem or chip used in the aforementioned equipment or devices.
  • the base station can also be a mobile switching center and a device that undertakes base station functions in device-to-device D2D, vehicle-to-everything (V2X), machine-to-machine (M2M) communications, and in 6G networks.
  • Base stations can support networks with the same or different access technologies. The embodiments of this application do not limit the specific technology and specific equipment form used by the network equipment.
  • Base stations can be fixed or mobile.
  • a helicopter or drone may be configured to act as a mobile base station, and one or more cells may move based on the mobile base station's location.
  • a helicopter or drone may be configured to serve as a device that communicates with another base station.
  • the network device in the embodiment of this application may refer to a CU or a DU, or the network device includes a CU and a DU.
  • gNB can also include AAU.
  • Network equipment and terminals can be deployed on land, indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed on aircraft, balloons and satellites in the sky. In the embodiments of this application, the scenarios in which network devices and terminals are located are not limited.
  • the 3rd generation mobile communications partnership project (3GPP) international standards organization began to develop 5G.
  • the main application scenarios of 5G can include: enhanced mobile ultra-broadband (eMBB), ultra-reliable low latency communications (URLLC) and massive machine type communication (mMTC).
  • eMBB enhanced mobile ultra-broadband
  • URLLC ultra-reliable low latency communications
  • mMTC massive machine type communication
  • Typical eMBB services can include: ultra-high-definition video, augmented reality (AR), virtual reality (VR), etc.
  • the main characteristics of the URLLC service are that it requires ultra-high reliability and ultra-low latency, and the amount of data transmitted is small and bursty.
  • the transmission delay requirement of URLLC services is generally within 0.5 milliseconds.
  • the transmission delay of the URLLC service is required to be within 1ms. Since the URLLC service is bursty and random, the URLLC service may not generate data packets for a long period of time, or may generate multiple data packets in a short period of time. In most cases, these data packets are Small packets (e.g., packets of size 50 bytes).
  • Typical URLLC services can include: wireless control in industrial manufacturing or production processes, motion control of driverless cars or drones, and tactile interactive applications such as remote repair and remote surgery.
  • Typical features of mMTC can include: high connection density, small data volume, delay-insensitive services, low cost and long service life of the module, etc. This scenario is mainly oriented to the Internet of Things business, which places extremely high requirements on network access capabilities.
  • RRC_CONNECTED RRC connected
  • RRC_IDLE RRC idle
  • RRC_INACTIVE RRC inactive
  • the RRC_CONNECTED state may refer to the state in which the terminal is in after completing the random access process but without performing RRC release. There is an RRC connection between the terminal and network equipment (such as access network equipment). In the RRC_CONNECTED state, the terminal can perform data transmission with network equipment, such as downlink data transmission and/or uplink data transmission. Alternatively, the terminal may also transmit terminal-specific data channels and/or control channels with the network device to transmit terminal-specific information or unicast information.
  • the RRC_IDLE state refers to the state of the terminal when it is camped 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.
  • 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 for the terminal is established between the network device and the core network. If the terminal needs to enter the RRC_CONNECTED state from the RRC_IDLE state, it needs to initiate the RRC connection establishment process.
  • the RRC_INACTIVE state is a newly introduced state 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 entered the RRC_CONNECTED state before 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 to quickly restore the RRC connection.
  • the connection for the terminal established between the network equipment and the core network has not been released. That is to say, 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.
  • 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 need for session transmission. In addition, the terminal can also enter the RRC_IDLE state from the RRC_INACTIVE state or the RRC_CONNECTED state.
  • Terminals in the RRC_IDLE state and RRC_INACTIVE state can enter the RRC_CONNECTED state through 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.
  • the four-step random access process and the two-step random access process are introduced below with reference to Figure 2 and Figure 3.
  • the terminal can send message 1 (Msg1) in the random access process to the network device.
  • the Msg1 includes the preamble.
  • the terminal can select random access channel (RACH) resources and preambles, and send the selected preambles on the selected resources.
  • RACH resource may also be called a physical random access channel (physical random access channel, PRACH) resource.
  • the network device can send RACH configuration information to the terminal in the form of broadcast.
  • the RACH configuration information may include RACH time-frequency resource configuration information and starting preamble root sequence configuration information.
  • the configuration information of RACH time domain resources can be indicated by a RACH configuration index.
  • the RACH configuration index may include one or more of the repetition period of the RACH resource, the number of RACH opportunities (RACH occasions, RO) included in one RACH resource repetition period, and the duration of each RO.
  • the configuration information of RACH frequency domain resources 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 (that is, the number of consecutive RACH frequency domain resources).
  • a continuous frequency domain resource can be determined through the configuration information of RACH frequency domain resources.
  • the initial preamble root sequence can be broadcast through the cell, and each cell can broadcast one preamble root sequence. Based on the configured starting preamble root sequence, the preamble set available in this cell can be obtained through cyclic shifting.
  • step S220 the network device sends Msg2 to the terminal.
  • the Msg2 may also be called a random access response (RAR).
  • RAR random access response
  • the Msg2 can be carried through the physical downlink control channel (PDCCH).
  • PDCH physical downlink control channel
  • the terminal After the terminal sends Msg1, it can 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.
  • RA-RNTI random access-radio network temporary identifier
  • Msg2 can also include the preamble sent by the terminal. If the terminal receives the PDCCH scrambled with RA-RNTI and Msg2 contains the preamble sent by itself, the terminal can consider that it has successfully received the random access response.
  • the terminal can obtain the physical downlink shared channel (PDSCH) scheduled by the PDCCH, where the PDSCH contains the RAR.
  • the RAR may include an uplink grant (UL grant), which is used to schedule the uplink resource indication of Msg3.
  • step S230 the terminal sends Msg3 to the network device.
  • the terminal can send Msg3 on the uplink authorization scheduled by the network device.
  • the Msg3 may also be called a radio resource control (RRC) connection establishment request message.
  • RRC radio resource control
  • Step S240 The network device sends Msg4 to the terminal.
  • 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 uses the PDCCH scrambled by the C-RNTI. Correspondingly, 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 use temporary C-RNTI scrambled PDCCH scheduling. Correspondingly, the terminal can use the temporary C-RNTI in Msg2 to decode the PDCCH to obtain Msg4 .
  • the terminal After the terminal successfully decodes the PDCCH, it 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.
  • CCCH common control channel
  • SDU service data unit
  • Figure 3 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.
  • step S310 the network device sends preamble configuration information to the terminal.
  • the configuration information includes the preamble and RACH resources required in the random access process.
  • the terminal can send MsgA to the network device according to the preamble configuration information. That is to say, the terminal can send the preamble to the network device on the RACH resource.
  • the MsgA may also be called MsgA physical uplink shared channel (PUSCH).
  • MsgA in the two-step random access process is equivalent to Msg1 and Msg3 in the four-step random access process.
  • step S330 the network device sends a MsgB to the terminal, and the MsgB may include RAR. After the terminal receives the RAR, it indicates that the random access process is completed.
  • MsgB in the two-step random access process is equivalent to Msg2 and Msg4 in the four-step random access process.
  • the terminal can work in a mode configured with only four-step random access (4-step RACH) or in a mode configured with only two-step random access (2-step RACH). mode, or can also work in a mode configured with both 4-step RACH and 2-step RACH.
  • 4-step RACH four-step random access
  • 2-step RACH two-step random access
  • the terminal is only configured with 4-step RACH, and the terminal can only initiate random access based on the 4-step RACH configuration. If the terminal is only configured with 2-step RACH, it means that the terminal device can only initiate random access based on the 2-step RACH configuration.
  • the terminal can initiate random access based on the 4-step RACH configuration or initiate random access based on the 2-step RACH configuration.
  • the terminal since the terminal only supports maintaining one random access process at the same time, the terminal needs to select a random access process between 4-step RACH and 2-step RACH for access.
  • the reference signal receiving power (RSRP) measured by the terminal is higher than the set threshold, or for random access triggered by RRC reconfiguration, if If the terminal is configured with dedicated non-contention random access resources based on 2-step RACH, the terminal can choose 2-step RACH. For other cases, the terminal can choose 4-step RACH.
  • network equipment can broadcast synchronization signals in multiple directional beams, such as primary synchronization signal (PSS), secondary synchronization signal (SSS), extended synchronization signal (extended synchronization signal, One or more of ESS), beam reference signal (BRS) and system information.
  • the network device can also send other reference signals through beams, such as channel state information reference signal (CSI-RS), so that the terminal can measure the channel between the network device and the terminal.
  • CSI-RS channel state information reference signal
  • the terminal may perform initial cell selection by listening to broadcasts and perform signal measurements based on one or more of synchronization signals, 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 to perform random access based on the signal strength.
  • the terminal can start the random access process by sending a random access preamble using the same sub-array and beam direction as the selected beam.
  • the terminal can remain in the RRC_INACTIVE state to save power.
  • the terminal in the RRC_INACTIVE state did not support data transmission, that is, it did not support the transmission of mobile origin (MO) data and mobile terminated (MT) data.
  • MO data means that the sending end 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 sending end 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.
  • the terminal 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.
  • 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 cause the terminal power consumption to increase. However, in some scenarios, the terminal in the RRC_INACTIVE state needs to transmit some data with a small amount of data and low transmission frequency (which can be called small packet data). If the terminal switches to the RRC_CONNECTED state and then transmits data, the signaling overhead required when the terminal switches the RRC state is even greater than the overhead required to transmit the data, resulting in unnecessary power consumption and signaling overhead.
  • the small data packets in the embodiment of the present application may be, for example, instant messaging messages, heartbeat packets, periodic data, etc.
  • the embodiment of this application does not specifically limit the source of the small data packet.
  • the small data packet may be data from a terminal application (APP).
  • APP terminal application
  • small data packets can be data from communication service APPs (such as WhatsApp, QQ, WeChat, etc.), heartbeat data packets from IM, email clients or other APPs, push notifications from various applications, etc.
  • small packets can come from data from non-terminal applications.
  • small data packets can come from data from wearable devices (such as regular positioning information, etc.), sensor data (such as temperature information and pressure information sent by industrial wireless sensors regularly or in an event-triggered manner), smart meters and smart meter network transmission protocols.
  • wearable devices such as regular positioning information, etc.
  • sensor data such as temperature information and pressure information sent by industrial wireless sensors regularly or in an event-triggered manner
  • smart meters and smart meter network transmission protocols.
  • the small data transmission (SDT) scheme in the RRC_INACTIVE state is discussed in Rel-17.
  • 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 in this embodiment of the present application may include uplink small data transmission and downlink small data transmission. The following will mainly describe uplink small data transmission.
  • the terminal can perform SDT according to the resources configured by the network device, that is, the terminal can send SDT PUSCH to the network device in the RRC_INACTIVE state.
  • the terminal can perform SDT during random access.
  • the terminal can perform SDT based on configured grant (CG) resources.
  • the terminal can perform SDT based on the pre-allocated uplink resource (PUR). These situations are introduced below.
  • the resources used by the terminal to perform SDT can be called RA-SDT resources.
  • the terminal can perform SDT in MsgA.
  • the terminal can carry small data packets in MsgA.
  • the terminal can perform SDT in Msg3.
  • the terminal can carry small data packets in Msg3.
  • Configuration authorization can also be called upstream authorization-free.
  • Configuring authorization can mean that the network device activates an uplink authorization to the terminal. If no deactivation instruction is received, the terminal can always use the resources specified by the activated uplink authorization (i.e., CG resources) for uplink transmission. In this embodiment of the present application, the terminal can use CG resources to perform SDT. CG resources used for SDT can also be called CG-SDT resources.
  • the type of configuration authorization can be, for example, CG type (type) 1 or CG type 2.
  • the configuration parameters of CG type 1 can be configured by RRC through high-level signaling.
  • the high-level signaling may be IE ConfiguredGrantConfig, for example.
  • the parameters required for CG type 2 are also configured by IE ConfiguredGrantConfig, but the resources of CG type 2 need to be activated and deactivated by downlink control information (DCI) to indicate resource activation and deactivation. Only resources activated by DCI can be used.
  • DCI downlink control information
  • CG type 1 and CG type 2 can be distinguished according to the field rrc-ConfiguredUplinkGrant in IE ConfiguredGrantConfig. If the field rrc-ConfiguredUplinkGrant is configured, the type of configuration authorization is CG type 1. If the field rrc-ConfiguredUplinkGrant is not configured, the type of configuration authorization is CG type 2.
  • the terminal may also use PUR resources for SDT.
  • PUR resources are preconfigured resources for terminals to send uplink data in a non-connected state.
  • the PUR resource can be a periodic resource.
  • PUR resources can be pre-configured based on grant type 1. In the RRC_INACTIVE state, the terminal can use the reserved PUR resources to directly transmit data.
  • the terminal Before performing SDT, the terminal needs to first determine whether the terminal meets the conditions for triggering SDT. Only when the conditions for triggering SDT are met, the terminal can 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 an RRC recovery (resume) process. For example, the terminal can switch from the RRC_INACTIVE state to the RRC_CONNECTED state to transmit data.
  • 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 the preconfigured data amount threshold (hereinafter also referred to as the third preset threshold) ; The measurement result of downlink reference signal receiving power (RSRP) is greater than the preconfigured RSRP threshold; there are valid SDT resources.
  • the preconfigured data amount threshold hereinafter also referred to as the third preset threshold
  • RSRP downlink reference signal receiving power
  • the resources for the first terminal to perform SDT and the resources for the second terminal to perform random access may conflict.
  • the first terminal sends the first small data packet on the first transmission opportunity
  • the second terminal sends the MsgA in the two-step random access process on the second transmission opportunity. If the 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 conflict with the resources of the second transmission opportunity. There is currently no clear regulation on how the network device should handle this resource conflict. .
  • both SDT PUSCH and MsgA PUSCH may not be decoded correctly, which results in reduced spectrum and energy efficiency.
  • 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 the MsgA PUSCH resources conflict with CG-SDT PUSCH resources. Therefore, it is necessary to provide a handling rule for conflicts between MsgA PUSCH resources and CG-SDT PUSCH resources.
  • embodiments of the present application provide a wireless communication method and device, which provide a clear solution for network devices to handle resource conflicts.
  • the solution of the embodiment of the present application will be introduced in detail below with reference to Figure 4 .
  • step S410 the first terminal sends a small data packet to the network device on the first transmission opportunity.
  • the first terminal sends SDT PUSCH to the network device on the first transmission opportunity.
  • the first terminal may send a small data packet to the network device when conditions for triggering SDT are met.
  • the conditions for triggering SDT can be found in the description above and will not be repeated here.
  • the service type of the small data packet may include one or more of the following services: URLLC service, mMTC service, and eMBB service.
  • the first transmission opportunity can be understood as transmission resources.
  • the first transmission opportunity may include time domain resources and/or frequency domain resources.
  • the resources of the first transmission opportunity may also be called SDT resources.
  • the resources of the first transmission opportunity may be, for example, CG-SDT resources, PUR resources or RA-SDT resources.
  • the resources of the first transmission opportunity may be configured by the network device to the first terminal. The configuration method of the resources of the first transmission opportunity will be described in detail below.
  • the resource of the first transmission opportunity may also be called SDT PUSCH resource, or the first resource.
  • the terms "resource of first transmission opportunity”, “SDT PUSCH resource”, “first resource” may be used interchangeably depending on the specific context.
  • the first resource may be CG-SDT PUSCH.
  • the first terminal sends a small data packet to the network device. This only means that the first terminal sent the small data packet to the network device. It does not mean that the network device successfully received the small data packet, or that the network device successfully received the small data packet. Small packets were received.
  • the network device may 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.
  • step S420 the second terminal sends the MsgA in the two-step random access process to the network device on the second transmission opportunity.
  • the second terminal can send MsgA PUSCH to the network device on the second transmission opportunity.
  • the second terminal and the first terminal may be two different terminals.
  • MsgA may include random access preamble and uplink data. MsgA can also be called MsgA PUSCH.
  • the second transmission opportunity may be a PRACH opportunity (PRACH occasion, 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 of the second terminal.
  • the resources of the second transmission opportunity can be configured to the second terminal through configuration authorization.
  • the network device may configure the resources of the second transmission opportunity to the second terminal through RRC signaling.
  • resources of the second transmission opportunity may also be called MsgA PUSCH resources, or second resources.
  • the terms "resource of the second transmission opportunity”, “MsgA PUSCH resource”, and “second resource” may be used interchangeably depending on the specific context.
  • the size of the data packet transmitted by the second terminal through MsgA PUSCH may also be different. Therefore, the second terminal can select matching MsgA PUSCH resources according to the size of the data packet to be transmitted.
  • the communication system can support two different PUSCH configurations. The time-frequency resource location and size of PUSCH under different PUSCH configurations can be different, corresponding to different PUSCH transmission packet size requirements, to support terminals to choose a configuration that meets their needs to initiate Random access.
  • the second terminal sends MsgA to the network device, which only means that the second terminal sent MsgA to the network device. It does not mean that the network device successfully received MsgA, or that the network device received MsgA. .
  • the network device may determine whether to receive the 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.
  • Resources of the first transmission opportunity and resources of the second transmission opportunity at least partially overlap.
  • the resources of the first transmission opportunity are called first resources and the resources of the second transmission opportunity are called second resources below.
  • At least partial overlap of the first resource and the second resource may mean 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 embodiment of the present application may refer to time domain resource overlap and/or frequency domain resource overlap.
  • 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.
  • the validity of the first transmission opportunity can be understood as the first terminal can successfully send the small data packet using the first transmission opportunity, or the network device can receive the small data packet sent by the first terminal on the first transmission opportunity, or the network device receives it first After the small data packet is transmitted by the first terminal on the first transmission opportunity, the network device receives the MsgA sent by the second terminal on the second transmission opportunity.
  • the invalid first transmission opportunity can be understood as the first terminal cannot successfully send the small data packet using the first transmission opportunity, or the network device gives up receiving the small data packet sent by the first terminal on the first transmission opportunity, or the network device receives the small data packet first MsgA sent by the second terminal on the second transmission opportunity. 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.
  • the validity of the second transmission opportunity can be understood as the second terminal can successfully send MsgA using the second transmission opportunity, or the network device can receive the MsgA sent by the second terminal on the second transmission opportunity, or the network device first receives the MsgA sent by the second terminal. MsgA is sent on the second transmission opportunity. After the MsgA transmission is completed, the network device then receives the small data packet sent by the first terminal on the first transmission opportunity.
  • the invalidity of the second transmission opportunity can be understood as the second terminal cannot successfully send the MsgA using the second transmission opportunity, or the network device gives up receiving the MsgA sent by the second terminal on the second transmission opportunity, or the network device receives the MsgA from the second terminal first. MsgA is sent on the second transmission opportunity. After the MsgA transmission is completed, the network device then receives the small data packet sent by the first terminal on the first transmission opportunity.
  • 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.
  • 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.
  • the network device can also determine whether the first transmission opportunity is valid and whether the second transmission opportunity is valid based on the first information.
  • the network device may only receive the first small data packet and give up receiving the MsgA. If the first transmission opportunity is invalid and the second transmission opportunity is valid, the network device may only receive MsgA and give up receiving the first small data packet.
  • 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 two-step random access; and the number of retransmissions of the small data packet.
  • the service type of the small data packet may include, for example, one or more of URLLC service, mMTC service, and eMBB service.
  • the embodiment of the present application can set a service type with a priority higher than MsgA, and/or a service type with a priority lower than MsgA, so that it can be determined whether the first transmission opportunity or the second transmission opportunity is valid according to the service type.
  • the priority of the mMTC service may be higher than the priority of MsgA. If the service type of the small data packet is the mMTC service, the network device may determine that the first transmission opportunity is valid, and/or the second transmission opportunity is invalid. Since the mMTC service is mainly used in IoT scenarios, there are many small data packets in the mMTC service. Setting the priority of the mMTC service to a higher priority than MsgA can enable the mMTC service data to be transmitted in a timely manner and reduce the duplication of data. upload times to improve user experience.
  • 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 the second transmission opportunity is valid, as shown in FIG. 5 . Since the eMBB service is mainly aimed at high-traffic mobile broadband services, the number of 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 Random access is successful as soon as possible.
  • 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 the second transmission opportunity is invalid, as shown in Figure 6 . Since the URLLC service is generally a low-latency service, transmitting the data packets of the URLLC service first will help ensure the delay requirements of the data packets. Of course, in some embodiments, the priority of the URLLC service may also be lower 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 invalid, and/or the second transmission opportunity is valid.
  • the first information may include a trigger condition that triggers two-step random access.
  • the triggering conditions that trigger two-step random access may include multiple types.
  • the triggering conditions may include one or more of the following: initial access; RRC reestablishment; cell handover; when uplink (UL) synchronization When the status is "out of sync", downlink (DL) or UL data in RRC_CONNECTED arrives; access from RRC_INACTIVE; secondary node (SN) is established; request other system information (SI); Beam failure recovery; scheduling request (SR) failed.
  • SI may, for example, include system information other than the master information block (MIB) and the system information block 1 (SIB1) in the system information.
  • MIB master information block
  • SIB1 system information block 1
  • 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 the second transmission opportunity is valid.
  • the first triggering condition may include one or more of the following: requesting other SI access; beam failure recovery; SR failure.
  • a second trigger condition may also be set.
  • the trigger condition for 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 reconstruction; cell switching; when the UL synchronization state is "out of sync", DL or UL data in RRC_CONNECTED arrives; access from RRC_INACTIVE; SN is established.
  • 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 the 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 small data packets is higher than the preset threshold, the network device can give up receiving small data packets and receive MsgA. This can avoid unlimited retransmission of small data packets, causing the second terminal to fail. Random access problem.
  • 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 the URLLC service; the service type of the small data packet is the mMTC service; the triggering condition for triggering two-step random access does not include beam failure recovery; triggering two-step random access The triggering condition for one-step random access does not include SR failure; the triggering condition for two-step random access does not include request for SI.
  • 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 the eMBB service; the service type of the small data packet is the URLLC service; the triggering condition for triggering the two-step random access includes beam failure recovery; triggering the two-step random access
  • the triggering conditions for random access include SR failure; the triggering conditions for two-step random access include requesting other SIs; the number of retransmissions of small data packets is higher than the preset threshold.
  • the service type of the small data packet is the URLLC service
  • Network equipment can give up the transmission of small data packets and transmit MsgA PUSCH. If the trigger condition that triggers the two-step random access does not include the above-mentioned first trigger condition, the first transmission opportunity is valid, or the second transmission opportunity is invalid.
  • the network device can transmit small data packets and give up the transmission of MsgA PUSCH
  • the network device can transmit the small data packet first and MsgA PUSCH waits. However, when the number of retransmissions of small data packets is greater than the preset threshold, the network device can give up the transmission of small data packets and transmit MsgA PUSCH.
  • the service type of the small data packet can be determined based on the first resource.
  • Embodiments of the present application can configure different resource pools for different services, and the network device can determine the service type of the small data packet based on the resource pool to which the first resource belongs.
  • the service type of the small data packet may include multiple service types, and the multiple service types respectively correspond to multiple resource pools.
  • Each of the multiple resource pools is used to transmit small data packets of its corresponding service type.
  • the first terminal may select resources from a resource pool that matches the service type of the small data packet to be sent to send the small data packet.
  • the service types of small data packets may include eMBB service, URLLC service, and mMTC service.
  • the resource pool corresponding to the eMBB service is R1
  • the resource pool corresponding to the URLLC service is R2
  • the resource pool corresponding to the mMTC service is R3.
  • the sizes of resource pools corresponding to different services may be equal or unequal, which is not specifically limited in the embodiments of this application.
  • this embodiment of the present application can differentiate the resource pool according to the number of data packets of different service types, which can balance the transmission of data packets of different services and enable rational allocation of resources.
  • 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; and 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 low latency requirements, configuring more resources for the URLLC service can enable the URLLC service to be transmitted in a timely manner, which is beneficial to meeting the business latency requirements.
  • the multiple resource pools mentioned above may be configured by the network device for the first terminal, or may be predefined.
  • the network device may configure multiple resource pools to the terminal through RRC connection release messages.
  • 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.
  • step S820 after receiving the RRC connection release message, the first terminal enters the RRC_INACTIVE state.
  • step S830 when the first terminal has a small data packet to send, the first terminal can 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.
  • the above-mentioned multiple resource pools may correspond to multiple timers, that is, the embodiment of the present application may configure multiple timers for multiple resource pools respectively. Multiple timers are respectively used to limit the length of time that resources in multiple resource pools are used to transmit small data packets of corresponding service types.
  • the plurality of resource pools include a first resource pool, and the timer corresponding to the first resource pool is used to limit the length of time that the resources of the first resource pool are used to transmit small data packets of the service type corresponding to the first resource pool.
  • the first terminal may use resources in the first resource pool to transmit small data packets within the duration of the timer corresponding to the first resource pool.
  • the parameters of the multiple timers may be indicated by CG-SDT resource configuration information.
  • CG-SDT resource configuration information may include information related to SDT.
  • 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 (transport block size, TBS), multiple physical uplink shared channel (PUSCH) duplication, starting location, wireless network temporary identifier (cell radio network temporary identity, C-RNTI) (such as CG-SDT C-RNTI) , timing advance (TA) verification criteria, allowed CG-SDT resource jumps, whether the CG-SDT resource configuration is suitable for one or more opportunities (occasion), demodulation reference signal (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, related parameters of multiple timers.
  • MCS modulation and coding scheme
  • TBS transport block size
  • PUSCH physical uplink shared channel
  • TA timing advance
  • timer T1 is used to limit the length of time that resource pool R1 is used to transmit eMBB services.
  • Timer T2 is used to limit the length of time that resource pool R2 is used to transmit URLLC services.
  • Timer T3 is used to limit the length of time that resource pool R3 is used to transmit the mMTC service.
  • the resources in resource pool R1 can be used to transmit small data packets of the eMBB service. After timer T1 times out, the resources in resource pool R1 cannot be used to transmit small data packets of the eMBB service. In other words, after the timer T1 times out, the first terminal cannot transmit the small data packet of the eMBB service.
  • the resources in resource pool R2 can be used to transmit small data packets of the URLLC service. After timer T2 expires, the resources in resource pool R2 cannot be used to transmit small data packets of the URLLC service. In other words, after the timer T2 times out, the first terminal cannot transmit the small data packet of the URLLC service.
  • the resources in resource pool R3 can be used to transmit small data packets of the mMTC service. After timer T3 times out, the resources in resource pool R3 cannot be used to transmit small data packets of the mMTC service. In other words, after the timer T3 times out, the first terminal cannot transmit the small data packet of the mMTC service.
  • the durations of the multiple timers corresponding to the multiple resource pools may be equal or unequal, and this is not specifically limited in this embodiment of the present application.
  • the timer duration corresponding to the resource pool of the URLLC service is longer 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 longer 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 longer than the timer duration corresponding to the resource pool of the eMBB service.
  • the duration of the timer may be determined according to the distribution of different services. For example, a larger timer can be set for a service type with a larger number of data packets, and a smaller timer can be set for a service type with a smaller number of data packets.
  • 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
  • the second resource pool corresponds to 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 the data packets of the second service can receive more transmission.
  • the resources in the resource pool can be used for data transmission of other service types.
  • first service and second service 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 second service. Transmission of data packets.
  • the resources in the resource pool R1 can be shared with the mMTC service and the URLLC service. That is to say, after the timer T1 times out, the first terminal can use the resources in the resource pool R1 to transmit small data packets of the mMTC service and the URLLC service.
  • FIG 9 shows the situation where the durations of the three timers are equal.
  • the first terminal in step S910, the first terminal is in the RRC_INACTIVE state, and the first terminal can start timers T1, T2 and T3.
  • step S920 the first terminal determines whether the timer T1 or T2 or T3 times out.
  • step S930 within the validity period of timer T1 or T2 or T3, the first terminal determines whether it needs to send a small data packet.
  • step S940 if the first terminal needs to send a small data packet, the first terminal selects a resource in the resource pool corresponding to the small data packet to be sent, and sends the small data packet on the resource.
  • the first terminal releases the resources in the resource pool, and the first terminal cannot transmit small data packets.
  • Figure 10 shows the situation where the durations of the three timers are not equal.
  • the first terminal in step S1010, the first terminal is in the RRC_INACTIVE state, and the first terminal can use resources in the resource pool to send service data packets corresponding to the resource pool.
  • step S1020 the first terminal starts the timers corresponding to each resource pool, and the first terminal starts timers T1, T2, and T3.
  • step S1030 the first terminal determines whether the timer T1 times out. If the timer T1 has not expired, the first terminal may use the resources in the resource pool R1 to transmit small data packets of the eMBB service.
  • the first terminal may release the resources in the resource pool R1.
  • the first terminal can release the resources in the resource pool R1 to the shared resource pool, so that the resources in the resource pool R1 can be used to transmit small data packets of the URLLC service and the mMTC service.
  • step S1050 the first terminal determines whether the timer T3 times out. If the timer T3 has not expired, the first terminal can use the resources in the resource pool R3 to transmit the small data packet of the mMTC service.
  • the first terminal may release the resources in the resource pool R3.
  • the first terminal may release the resources in the resource pool R3 to the shared resource pool, so that the resources in the resource pool R3 can be used to transmit small data packets of the URLLC service.
  • step S1070 the first terminal determines whether timer T2 times out. If the timer T2 has not expired, the first terminal can use the resources in the resource pool R2 to transmit the small data packet of the URLLC service.
  • step S1080 if the timer T2 times out, the first terminal may 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.
  • Figure 11 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.
  • the network device shown in Figure 11 can be any of the network devices described above.
  • the network device 1100 includes a determining unit 1110.
  • the determining unit 1110 may be configured to determine one or more of the following events based on the first information: whether the first transmission opportunity for the first terminal to send the small data packet is valid; for the second terminal to send the two-step random access Whether the second transmission opportunity of message A in the 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; a triggering condition for triggering two-step random access; and the number of retransmissions of the small data packet.
  • 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 failed; the triggering condition for two-step random access does not include requesting other SI.
  • 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 the eMBB service;
  • the service type of the small data packet is the 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 conditions for triggering two-step random access include requesting other SIs; the number of retransmissions of the small data packet is higher than the preset threshold.
  • 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 respectively correspond to multiple resource pools, and the resources in each resource pool in the multiple resource pools are used for transmission.
  • 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; and the resource pool size corresponding to the URLLC service is larger than the resource pool size corresponding to the eMBB service.
  • Resource pool size 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; and the resource pool size corresponding to the URLLC service is larger than the resource pool size corresponding to the eMBB service.
  • the multiple resource pools respectively correspond to multiple timers, and the multiple timers are respectively used to limit the length of time that the resources in the multiple resource pools are used to transmit small data packets of corresponding service types. .
  • the time lengths of the multiple timers are equal.
  • the time lengths of the multiple timers are not equal.
  • the plurality of 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 The first timer
  • the second resource pool corresponds to the second timer, if the duration of the first timer is less than the duration of the second timer, after the first timer times out, the third timer Resources in a resource pool are used for transmission of small data packets of the second service.
  • the timer duration corresponding to the resource pool of the URLLC service is longer 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 longer 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 longer than the timer duration corresponding to the resource pool of the eMBB service.
  • the resource of the first transmission opportunity is a CG-SDT resource.
  • Figure 12 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.
  • the first terminal shown in Figure 12 may be any first terminal described above.
  • the first terminal 1200 includes a sending unit 1210.
  • the sending unit 1210 may be configured to send a small data packet to the 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, and the second transmission opportunity is used for the second terminal. Send message A in the two-step random access process to the network device.
  • the first information includes one or more of the following information: the service type of the small data packet; a triggering condition for triggering two-step random access; and the number of retransmissions of the small data packet.
  • 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 failed; the triggering condition for two-step random access does not include requesting other SI.
  • 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 the eMBB service;
  • the service type of the small data packet is the 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 conditions for triggering two-step random access include requesting other SIs; the number of retransmissions of the small data packet is higher than the preset threshold.
  • 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 respectively correspond to multiple resource pools, and the resources in each resource pool in the multiple resource pools are used for transmission.
  • 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; and the resource pool size corresponding to the URLLC service is larger than the resource pool size corresponding to the eMBB service.
  • Resource pool size 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; and the resource pool size corresponding to the URLLC service is larger than the resource pool size corresponding to the eMBB service.
  • the multiple resource pools respectively correspond to multiple timers, and the multiple timers are respectively used to limit the length of time that the resources in the multiple resource pools are used to transmit small data packets of corresponding service types. .
  • the time lengths of the multiple timers are equal.
  • the time lengths of the multiple timers are not equal.
  • the plurality of 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 The first timer
  • the second resource pool corresponds to the second timer, if the duration of the first timer is less than the duration of the second timer, after the first timer times out, the third timer Resources in a resource pool are used for transmission of small data packets of the second service.
  • the timer duration corresponding to the resource pool of the URLLC service is longer 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 longer 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 longer than the timer duration corresponding to the resource pool of the eMBB service.
  • the resource of the first transmission opportunity is a CG-SDT resource.
  • Figure 13 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.
  • the second terminal shown in Figure 13 may be any second terminal described above.
  • the second terminal 1300 includes a sending unit 1310.
  • the sending unit 1310 may be configured to send the 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.
  • the first transmission opportunity The transmission opportunity is used by the first terminal to send small data packets to the network device.
  • the first information includes one or more of the following information: the service type of the small data packet; a triggering condition for triggering two-step random access; and the number of retransmissions of the small data packet.
  • 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 failed; the triggering condition for two-step random access does not include requesting other SI.
  • 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 the eMBB service;
  • the service type of the small data packet is the 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 conditions for triggering two-step random access include requesting other SIs; the number of retransmissions of the small data packet is higher than the preset threshold.
  • 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 respectively correspond to multiple resource pools, and the resources in each resource pool in the multiple resource pools are used for transmission.
  • 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; and the resource pool size corresponding to the URLLC service is larger than the resource pool size corresponding to the eMBB service.
  • Resource pool size 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; and the resource pool size corresponding to the URLLC service is larger than the resource pool size corresponding to the eMBB service.
  • the multiple resource pools respectively correspond to multiple timers, and the multiple timers are respectively used to limit the length of time that the resources in the multiple resource pools are used to transmit small data packets of corresponding service types. .
  • the time lengths of the multiple timers are equal.
  • the time lengths of the multiple timers are not equal.
  • the plurality of 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 The first timer
  • the second resource pool corresponds to the second timer, if the duration of the first timer is less than the duration of the second timer, after the first timer times out, the third timer Resources in a resource pool are used for transmission of small data packets of the second service.
  • the timer duration corresponding to the resource pool of the URLLC service is longer 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 longer 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 longer than the timer duration corresponding to the resource pool of the eMBB service.
  • the resource of the first transmission opportunity is a CG-SDT resource.
  • Figure 14 is a schematic structural diagram of the device according to the embodiment of the present application.
  • the dashed line in Figure 14 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 may be one or more of a chip, a first terminal, a second terminal, and a network device.
  • Apparatus 1400 may include one or more processors 1410.
  • the processor 1410 can support the device 1400 to implement the method described in the foregoing method embodiments.
  • the processor 1410 may be a general-purpose processor or a special-purpose processor.
  • the processor may be a central processing unit (CPU).
  • the processor can also be another general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), or an off-the-shelf programmable gate array (FPGA) Or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA off-the-shelf programmable gate array
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
  • Apparatus 1400 may also 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 foregoing method embodiment.
  • the memory 1420 may be independent of the processor 1410 or integrated in the processor 1410.
  • Apparatus 1400 may also include a transceiver 1430.
  • Processor 1410 may communicate with other devices or chips through transceiver 1430.
  • the processor 1410 can transmit and receive data with other devices or chips through the transceiver 1430.
  • An embodiment of the present application also provides a computer-readable storage medium for storing a program.
  • the computer-readable storage medium can be applied in the terminal or network device provided by the embodiments of the present application, and the program causes the computer to execute the methods performed by the terminal or network device in various embodiments of the present application.
  • An 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 in the terminal or network device provided by the embodiments of the present application, and the program causes the computer to execute the methods performed by the terminal or network device in various embodiments of the present application.
  • An embodiment of the present application also provides a computer program.
  • the computer program can be applied to the terminal or network device provided by the embodiments of the present application, and the computer program causes the computer to execute the methods performed by the terminal or network device in various embodiments of the present application.
  • B corresponding to A means that B is associated with A, and B can be determined based on A.
  • determining B based on A does not mean determining B only based on A.
  • B can also be determined based on A and/or other information.
  • the size of the sequence numbers of the above-mentioned processes does not mean the order of execution.
  • the execution order of each process should be determined by its functions and internal logic, and should not be used in the embodiments of the present application.
  • the implementation process constitutes any limitation.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.
  • 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 they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.
  • the computer program product includes one or more computer instructions.
  • 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 or transmitted from one computer-readable storage medium to another, e.g., the computer instructions may be transferred from a website, computer, server, or data center Transmission to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means.
  • 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 integrated with one or more available media.
  • the available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs (DVD)) or semiconductor media (e.g., solid state disks (SSD) )wait.
  • magnetic media e.g., floppy disks, hard disks, magnetic tapes
  • optical media e.g., digital video discs (DVD)
  • semiconductor media e.g., solid state disks (SSD)

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供了一种无线通信的方法及装置，为网络设备处理资源冲突提供了一种明确的方案。该方法包括：网络设备基于第一信息，确定以下事件中的一种或多种：用于第一终端发送小数据包的第一传输机会是否有效（S410）；用于第二终端发送两步随机接入过程中的消息A的第二传输机会是否有效（S420）；其中，该第二传输机会的资源与该第一传输机会的资源至少部分重叠；该第一信息包括以下信息中的一种或多种：该小数据包的业务类型；触发两步随机接入的触发条件；该小数据包的重传次数。

Description

无线通信的方法及装置 技术领域
本申请涉及通信技术领域，并且更为具体地，涉及一种无线通信的方法及装置。
背景技术
为了节省终端的信令开销，通信系统中允许终端在无线资源控制非激活(radio resource control，RRC)非激活(INACTIVE)态下向网络设备发送小数据包。但是，一个终端发送小数据包的资源可能会和另一个终端进行随机接入的资源发生重叠，即资源发生冲突。
如果资源发生冲突，网络设备该如何处理这种资源冲突，目前还没有明确的规定。
发明内容
针对上述问题，本申请提供一种无线通信的方法及装置。下面对本申请实施例涉及的各个方面进行介绍。
第一方面，提供了一种无线通信的方法，包括：网络设备基于第一信息，确定以下事件中的一种或多种：用于第一终端发送小数据包的第一传输机会是否有效；用于第二终端发送两步随机接入过程中的消息A的第二传输机会是否有效；其中，所述第二传输机会的资源与所述第一传输机会的资源至少部分重叠；所述第一信息包括以下信息中的一种或多种：所述小数据包的业务类型；触发两步随机接入的触发条件；所述小数据包的重传次数。
第二方面，提供了一种无线通信的方法，包括：第一终端在第一传输机会上向网络设备发送小数据包，所述第一传输机会的资源与第二传输机会的资源至少部分重叠，所述第二传输机会用于第二终端向所述网络设备发送两步随机接入过程中的消息A，所述第一传输机会或所述第二传输机会是否有效基于第一信息确定，所述第一信息包括以下信息中的一种或多种：所述小数据包的业务类型；触发两步随机接入的触发条件；所述小数据包的重传次数。
第三方面，提供了一种无线通信的方法，包括：第二终端在第二传输机会上向网络设备发送两步随机接入过程中的消息A，所述第二传输机会的资源与第一传输机会的资源至少部分重叠，所述第一传输机会用于第一终端向所述网络设备发送小数据包，所述第一传输机会或所述第二传输机会是否有效基于第一信息确定，所述第一信息包括以下信息中的一种或多种：所述小数据包的业务类型；触发两步随机接入的触发条件；所述小数据包的重传次数。
第四方面，提供了一种无线通信的装置，所述装置为网络设备，所述装置包括：确定单元，用于基于第一信息，确定以下事件中的一种或多种：用于第一终端发送小数据包的第一传输机会是否有效；用于第二终端发送两步随机接入过程中的消息A的第二传输机会是否有效；其中，所述第二传输机会的资源与所述第一传输机会的资源至少部分重叠；所述第一信息包括以下信息中的一种或多种：所述小数据包的业务类型；触发两步随机接入的触发条件；所述小数据包的重传次数。
第五方面，提供了一种无线通信的装置，所述装置为第一终端，所述装置包括：发送单元，用于在第一传输机会上向网络设备发送小数据包，所述第一传输机会的资源与第二传输机会的资源至少部分重叠，所述第二传输机会用于第二终端向所述网络设备发送两步随机接入过程中的消息A，所述第一传输机会或所述第二传输机会是否有效基于第一信息确定，所述第一信息包括以下信息中的一种或多种：所述小数据包的业务类型；触发两步随机接入的触发条件；所述小数据包的重传次数。
第六方面，提供了一种无线通信的装置，所述装置为第二终端，所述装置包括：发送单元，用于在第二传输机会上向网络设备发送两步随机接入过程中的消息A，所述第二传输机会的资源与第一传输机会的资源至少部分重叠，所述第一传输机会用于第一终端向所述网络设备发送小数据包，所述第一传输机会或所述第二传输机会是否有效基于第一信息确定，所述第一信息包括以下信息中的一种或多种：所述小数据包的业务类型；触发两步随机接入的触发条件；所述小数据包的重传次数。
第七方面，提供一种无线通信的装置，包括处理器、存储器、通信接口，所述存储器用于存储一个或多个计算机程序，所述处理器用于调用所述存储器中的计算机程序使得所述终端设备执行第一方面至第三方面中任一方面所述的方法。
第八方面，提供一种装置，包括处理器，用于从存储器中调用程序，以执行第一方面至第三方面中任一方面所述的方法。
第九方面，提供一种芯片，包括处理器，用于从存储器调用程序，使得安装有所述芯片的设备执行第一方面至第三方面中任一方面所述的方法。
第十方面，提供一种计算机可读存储介质，其上存储有程序，所述程序使得计算机执行第一方面 至第三方面中任一方面所述的方法。
第十一方面，提供一种计算机程序产品，包括程序，所述程序使得计算机执行第一方面至第三方面中任一方面所述的方法。
第十二方面，提供一种计算机程序，所述计算机程序使得计算机执行第一方面至第三方面中任一方面所述的方法。
本申请实施例中，在第一传输机会的资源和第二传输机会的资源发生重叠时，网络设备可以基于第一信息，确定第一传输机会是否有效，或第二传输机会是否有效。通过引入第一信息，为网络设备处理资源冲突提供了一种明确的方案。
附图说明
图1是可应用于本申请实施例的通信系统的系统架构示例图。
图2是四步随机接入过程的示意性流程图。
图3是两步随机接入过程的示意性流程图。
图4是本申请一实施例提供的无线通信方法的示意性流程图。
图5是本申请一实施例提供的确定传输机会是否有效的示意图。
图6是本申请另一实施例提供的确定传输机会是否有效的示意图。
图7是本申请一实施例提供的业务类型、资源池、定时器之间的对应关系的示意图。
图8是本申请一实施例提供的终端设备进行SDT的示意性流程图。
图9是本申请一实施例提供的基于定时器进行小数据包的传输的示意性流程图。
图10是本申请另一实施例提供的基于定时器进行小数据包的传输的示意性流程图。
图11是本申请一实施例提供的网络设备的结构示意图。
图12是本申请另一实施例提供的第一终端的结构示意图。
图13是本申请另一实施例提供的第二终端的结构示意图。
图14是本申请一实施例提供的通信装置的结构示意图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
图1是本申请实施例应用的无线通信系统100。该无线通信系统100可以包括网络设备110和终端120。网络设备110可以是与终端120通信的设备。网络设备110可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的终端120进行通信。
图1示例性地示出了一个网络设备和两个终端，可选地，该无线通信系统100可以包括多个网络设备并且每个网络设备的覆盖范围内可以包括其它数量的终端，本申请实施例对此不做限定。
可选地，该无线通信系统100还可以包括网络控制器、移动管理实体等其他网络实体，本申请实施例对此不作限定。
应理解，本申请实施例的技术方案可以应用于各种通信系统，例如：第五代(5th generation，5G)系统或新无线(new radio，NR)、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)等。本申请提供的技术方案还可以应用于未来的通信系统，如第六代移动通信系统，又如卫星通信系统，等等。
本申请实施例中的终端也可以称为用户设备(user equipment，UE)、接入终端、用户单元、用户站、移动站、移动台(mobile station，MS)、移动终端(mobile Terminal，MT)、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。本申请实施例中的终端可以是指向用户提供语音和/或数据连通性的设备，可以用于连接人、物和机，例如具有无线连接功能的手持式设备、车载设备等。本申请的实施例中的终端可以是手机(mobile phone)、平板电脑(Pad)、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备，虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。可选地，UE可以用于充当基站。例如，UE可以充当调度实体，其在V2X或D2D等中的UE之间提供侧行链路信号。比如，蜂窝电话和汽车利用侧行链路信号彼此通信。蜂窝电话和智能家居设备之间通信，而无需通过基站中继通信信号。
本申请实施例中的网络设备可以是用于与终端通信的设备，该网络设备也可以称为接入网设备或无线接入网设备，如网络设备可以是基站。本申请实施例中的网络设备可以是指将终端接入到无线网络的无线接入网(radio access network，RAN)节点(或设备)。基站可以广义的覆盖如下中的各种名 称，或与如下名称进行替换，比如：节点B(NodeB)、演进型基站(evolved NodeB，eNB)、下一代基站(next generation NodeB，gNB)、中继站、接入点、传输点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、主站MeNB、辅站SeNB、多制式无线(MSR)节点、家庭基站、网络控制器、接入节点、无线节点、接入点(access piont，AP)、传输节点、收发节点、基带单元(base band unit，BBU)、射频拉远单元(Remote Radio Unit，RRU)、有源天线单元(active antenna unit，AAU)、射频头(remote radio head，RRH)、中心单元(central unit，CU)、分布式单元(distributed unit，DU)、定位节点等。基站可以是宏基站、微基站、中继节点、施主节点或类似物，或其组合。基站还可以指用于设置于前述设备或装置内的通信模块、调制解调器或芯片。基站还可以是移动交换中心以及设备到设备D2D、车辆外联(vehicle-to-everything，V2X)、机器到机器(machine-to-machine，M2M)通信中承担基站功能的设备、6G网络中的网络侧设备、未来的通信系统中承担基站功能的设备等。基站可以支持相同或不同接入技术的网络。本申请的实施例对网络设备所采用的具体技术和具体设备形态不做限定。
基站可以是固定的，也可以是移动的。例如，直升机或无人机可以被配置成充当移动基站，一个或多个小区可以根据该移动基站的位置移动。在其他示例中，直升机或无人机可以被配置成用作与另一基站通信的设备。
在一些部署中，本申请实施例中的网络设备可以是指CU或者DU，或者，网络设备包括CU和DU。gNB还可以包括AAU。
网络设备和终端可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上；还可以部署在空中的飞机、气球和卫星上。本申请实施例中对网络设备和终端所处的场景不做限定。
应理解，本申请中的通信设备的全部或部分功能也可以通过在硬件上运行的软件功能来实现，或者通过平台(例如云平台)上实例化的虚拟化功能来实现。
随着人们对速率、延迟、高速移动性、能效的追求以及未来生活中业务的多样性和复杂性，第三代移动通信合作伙伴计划(3rd generation partnership project，3GPP)国际标准组织开始研发5G。5G的主要应用场景可以包括：增强移动超宽带(enhance mobile broadband，eMBB)、低时延高可靠通信(ultra reliable low latency communications，URLLC)和大规模机器类通信(massive machine type communication，mMTC)。本申请实施例的方案可适用于上述任意一种场景。
eMBB业务的主要特点是传输的数据量大，传输速率高。在传输eMBB业务的数据时，一般采用较长时间的时间调度单元来进行数据的传输以提高数据传输效率。典型的eMBB业务可以包括：超高清视频、增强现实(augmented reality，AR)、虚拟现实(virtual reality，VR)等。
URLLC业务的主要特点是要求超高的可靠性和超低的延时，传输的数据量较少并且具有突发性。例如，在不考虑可靠性的情况下，URLLC业务的传输时延要求一般在0.5毫秒以内。在可靠性要求达到99.999％的前提下，URLLC业务的传输时延要求在1ms以内。由于URLLC业务具有突发性和随机性，因此，URLLC业务可能在很长一段时间内都不会产生数据包，也可能在很短时间内产生多个数据包，这些数据包在多数情况下为小包(例如，大小为50个字节的数据包)。典型的URLLC业务可以包括：工业制造或生产流程中的无线控制，无人驾驶汽车或无人驾驶飞机的运动控制以及远程修理，远程手术等触觉交互类应用。
mMTC的典型特点可以包括：高连接密度，小数据量，时延不敏感业务，模块的低成本和长使用寿命等。该场景主要面向物联网业务，它对网络的接入能力提出了极高的要求。
目前，协议中定义了终端的三种RRC状态：RRC连接(RRC_CONNECTED)态、RRC空闲(RRC_IDLE)态和RRC非激活(RRC_INACTIVE)态。
RRC_CONNECTED态可以指终端完成随机接入过程之后，未进行RRC释放时所处的状态。终端和网络设备(例如接入网络设备)之间存在RRC连接。在RRC_CONNECTED态下，终端可以和网络设备进行数据传输，如进行下行数据传输和/或上行数据传输。或者，终端也可以和网络设备进行终端特定的数据信道和/或控制信道的传输，以传输该终端的特定信息或单播信息。
RRC_IDLE态是指终端在小区中驻留，但是未进行随机接入时终端所处的状态。终端通常在开机之后，或者在RRC释放之后进入RRC_IDLE态。在RRC_IDLE态下，终端和网络设备(例如驻留网络设备)之间没有RRC连接，网络设备没有存储终端的上下文，网络设备与核心网之间没有建立针对该终端的连接。如果终端需要从RRC_IDLE态进入RRC_CONNECTED态，则需要发起RRC连接建立过程。
RRC_INACTIVE态是为了降低空口信令、快速恢复无线连接和快速恢复数据业务，从节能的角度新引入的状态。RRC_INACTIVE态是处于连接态和空闲态之间的一个状态。终端之前已经进入了RRC_CONNECTED态，然后释放了与网络设备的RRC连接、无线承载和无线资源，但是网络设备保 存了该终端的上下文，以便快速恢复RRC连接。另外，网络设备与核心网建立的针对该终端的连接没有被释放，也就是说，RAN与CN之间的用户面承载和控制面承载仍被维护，即存在CN-NR的连接。
终端可以在上述三种RRC状态之间进行切换。例如，终端可以在持续一段时间内没有数据传输的情况下，从RRC_CONNECTED态进入RRC_INACTIVE态来暂停其会话，并且可以在有会话传输需求时，从RRC_INACTIVE态进入RRC_CONNECTED态。另外，终端也可以从RRC_INACTIVE态或RRC_CONNECTED态进入RRC_IDLE态。
处于RRC_IDLE态和RRC_INACTIVE态的终端，可以通过随机接入的方式，进入RRC_CONNECTED态。随机接入的方式有两种，一种是四步随机接入方式，一种是两步随机接入方式。四步随机接入也可以称为基于竞争的随机接入。两步随机接入也可以称为基于非竞争的随机接入。下面结合图2和图3，对四步随机接入过程和两步随机接入过程进行介绍。
参见图2，在步骤S210、终端可以向网络设备发送随机接入过程中的消息1(message 1，Msg1)。该Msg1中包括前导码。
终端可以选择随机接入信道(random access channel，RACH)资源和前导码，并在选择的资源上发送选择的前导码。该RACH资源也可以称为物理随机接入信道(physical random access channel，PRACH)资源。
网络设备可以通过广播的形式向终端发送RACH的配置信息。RACH的配置信息可以包括RACH的时频资源的配置信息以及起始的前导码根序列的配置信息。
RACH的时域资源的配置信息可以通过1个RACH配置索引进行指示。该RACH配置索引中可以包括RACH资源的重复周期、一个RACH资源重复周期内包含的RACH时机(RACH occasion，RO)个数、每个RO的持续时间中的一种或多种。RACH的频域资源的配置信息可以包括1个RACH起始频域资源索引和同一个时刻可以频分复用的RACH资源个数(即连续的RACH频域资源个数)。通过RACH频域资源的配置信息可以确定一段连续的频域资源。起始的前导码根序列可以通过小区广播，每个小区可以广播一个前导码根序列。基于配置的该起始前导码根序列，通过循环移位可以得到本小区可用的前导码集合。
在步骤S220中、网络设备向终端发送Msg2，该Msg2也可以称为随机接入响应(random access response，RAR)。该Msg2可以通过物理下行控制信道(physical downlink control channel，PDCCH)承载。
终端发送Msg1后，可以开启一个随机接入响应时间窗，并在该时间窗内监测随机接入无线网络临时标识(random access-radio network temporary identifier，RA-RNTI)加扰的PDCCH。
Msg2中还可以包括终端发送的前导码，如果终端接收到用RA-RNTI加扰的PDCCH，并且Msg2中包含自己发送的前导码，则终端可以认为成功接收到随机接入响应。
终端成功接收到PDCCH后，终端能够获得该PDCCH调度的物理下行共享信道(physical downlink shared channel，PDSCH)，其中，该PDSCH中包含了RAR。该RAR中可以包括上行授权(UL grant)，用于调度Msg3的上行资源指示。
在步骤S230、终端向网络设备发送Msg3。终端可以在网络设备调度的上行授权上发送Msg3。该Msg3也可以称为无线资源控制(radio resource control，RRC)连接建立请求消息。
步骤S240、网络设备向终端发送Msg4。
该Msg4具有两个作用，一个是用于竞争冲突解决，另一个是向终端发送RRC配置消息。如果终端在Msg3中携带了C-RNTI，则Msg4采用该C-RNTI加扰的PDCCH调度，相应地，终端可以使用Msg3中的C-RNTI对PDCCH进行解码，得到Msg4。如果终端在Msg3中没有携带C-RNTI，如初始接入，则Msg4可以采用临时C-RNTI加扰的PDCCH调度，相应地，终端可以使用Msg2中的临时C-RNTI对PDCCH进行解码，得到Msg4。终端在解码PDCCH成功后，得到承载Msg4的PDSCH。终端可以将该PDSCH中的公共控制信道(common control channel，CCCH)服务数据单元(service data unit，SDU)与Msg3中的CCCH SDU进行比较，如果两者相同，则表示竞争解决成功。
图3是本申请实施例提供的一种两步随机接入过程的流程图。该方法包括步骤S310～S330。
在步骤S310中，网络设备向终端发送前导码配置信息，该配置信息中包括随机接入过程中需要的前导码和RACH资源。
在步骤S320中，终端可以根据该前导码配置信息，向网络设备发送MsgA，也就是说，终端可以在该RACH资源上向网络设备发送该前导码。该MsgA也可以称为MsgA物理上行共享信道(physical uplink shared channel，PUSCH)。
在一些实施例中，两步随机接入过程中的MsgA相当于四步随机接入过程中的Msg1和Msg3。
在步骤S330中，网络设备向终端发送MsgB，该MsgB中可以包括RAR。终端接收到该RAR后， 表示该随机接入过程结束。
在一些实施例中，两步随机接入过程中的MsgB相当于四步随机接入过程中的Msg2和Msg4。
在引入两步随机接入技术后，终端可以工作在仅配置了四步随机接入(4-step RACH)的模式，也可以工作在仅配置了两步随机接入(2-step RACH)的模式，或者也可以工作在同时配置了4-step RACH和2-step RACH的模式。
终端仅配置了4-step RACH可以表示，终端只能基于4-step RACH配置发起随机接入。终端仅配置了2-step RACH可以表示，终端设备只能基于2-step RACH配置发起随机接入。
对于同时配置了4-step RACH和2-step RACH的终端来说，终端可以基于4-step RACH配置发起随机接入，也可以基于2-step RACH配置发起随机接入。另外，由于终端在同一时刻仅支持维护一个随机接入过程，因此，终端需要在4-step RACH和2-step RACH中选择一个随机接入过程进行接入。在一些实施例中，如果在基于竞争的随机接入过程中，终端测量的参考信号接收功率(reference signal receiving power，RSRP)高于设定阈值，或者对于RRC重配触发的随机接入，如果终端基于2-step RACH配置了专用的非竞争随机接入资源，则终端可以选择2-step RACH。对于其他情况，终端可以选择4-step RACH。
在无线通信系统中，网络设备可以在多个定向波束中广播同步信号，例如主同步信号(primary synchronization signal，PSS)、辅同步信号(secondary synchronization signal，SSS)、扩展同步信号(extended synchronization signal，ESS)、波束参考信号(beam reference signal，BRS)和系统信息中的一种或多种。另外，网络设备还可以通过波束发送其他参考信号，例如，信道状态信息参考信号(channel state information reference signal，CSI-RS)，以使终端能够测量网络设备和终端之间的信道。终端可以通过收听广播来执行初始小区的选择，并基于同步信号、BRS和其他信号中的一种或多种，进行信号测量。终端可以基于接收到的信号确定信号强度，并基于信号强度选择小区和小区内的波束以执行随机接入。终端在进行随机接入时，可以使用与所选择的波束相同的子阵列和波束方向发送随机接入前导码来启动随机接入过程。
对于数据传输不频繁的终端，终端可以保持在RRC_INACTIVE态，以节省电量。在第16版本(release 16，Rel-16)之前，处于RRC_INACTIVE态的终端不支持数据传输，即不支持移动发起(mobile original，MO)数据和移动终止(mobile terminated，MT)数据的传输。MO数据指数据的发送端为终端，消息的传递方向是终端到网络设备。MO数据也可以称为上行数据。MT数据指数据的发送端为网络设备，消息的传递方向是网络设备到终端。MT数据也可以称为下行数据。
当MO数据或MT数据到达时，终端需要恢复RRC连接，从而进入RRC_CONNECTED态。在RRC_CONNECTED态，终端可以进行MO数据或MT数据的传输。待MO数据或MT数据传输完成后，终端再释放RRC连接，回到RRC_INACTIVE态。
在上述过程中，终端需要从RRC_INACTIVE态切换到RRC_CONNECTED态，然后再从RRC_CONNECTED态切换到RRC_INACTIVE态。不同RRC状态之间的切换会导致终端功耗增加。但在一些场景下，处于RRC_INACTIVE态的终端需要传输一些数据量小且传输频率低的数据(可称为小包数据)。如果终端切换到RRC_CONNECTED态再进行数据传输，终端进行RRC状态切换时所需要的信令开销甚至会大于传输这些数据所需要的开销，从而导致不必要的功耗和信令开销。
本申请实施例中的小数据包例如可以为即时通讯消息、心跳包、周期性数据等。本申请实施例对小数据包的来源不做具体限定。作为一个示例，小数据包可以是来自终端应用程序(application，APP)的数据。例如，小数据包可以是来自通讯服务APP(如whatsapp、QQ、微信等)的数据、来自IM、电子邮件客户端或其他APP的心跳数据包、来自各种应用程序的推送通知等。作为另一个示例，小数据包可以来自非终端应用程序的数据。例如，小数据包可以来自可穿戴设备的数据(如定期定位信息等)、传感器数据(如工业无线传感器定期或以事件触发方式发送的温度信息、压力信息)、智能仪表和智能仪表网络发送协议中(如3GPP TS 22.891)规定的定期仪表读数等。
为了降低终端的功耗，Rel-17中讨论了RRC_INACTIVE态下进行小数据传输(small data transmission，SDT)方案。在该方案中，终端不需要从RRC_INACTIVE态切换至RRC_CONNECTED态进行小数据传输，而是在RRC_INACTIVE态下即可进行小数据传输。本申请实施例的小数据传输可以包括上行小数据传输和下行小数据传输。下文将主要针对上行小数据传输进行描述。
在RRC_INACTIVE态下，终端可以根据网络设备配置的资源进行SDT，即终端可以在RRC_INACTIVE态下，向网络设备发送SDT PUSCH。终端进行SDT的方式有多种，本申请实施例对此不作具体限定。例如，终端可以在随机接入的过程中进行SDT。又例如，终端可以基于配置授权(configured grant，CG)资源进行SDT。再例如，终端可以基于上行预配置资源(pre-allocated uplink resource，PUR)进行SDT。下面分别对这几种情况进行介绍。
以随机接入过程为例，在随机接入过程中，终端进行SDT的资源可以称为RA-SDT资源。对于两步随机接入过程，终端可以在MsgA中进行SDT。以图3为例，终端可以在MsgA中携带小数据包。对于四步随机接入过程，终端可以在Msg3中进行SDT。以图2为例，终端可以在Msg3中携带小数据包。
配置授权也可以称为上行免授权。配置授权可以指网络设备通过激活一次上行授权给终端，在没有接收到去激活指示的情况下，终端可以一直使用激活的上行授权所指定的资源(即CG资源)进行上行传输。在本申请实施例中，终端可以使用CG资源进行SDT。用于进行SDT的CG资源也可以称为CG-SDT资源。
配置授权的类型例如可以为CG类型(type)1或CG type 2。CG type 1的配置参数可以由RRC通过高层信令进行配置。该高层信令例如可以为IE ConfiguredGrantConfig。CG type 2需要的参数也是由IE ConfiguredGrantConfig进行配置，但是CG type 2的资源需要由下行控制信息(downlink control information，DCI)指示资源的激活和去激活，只有经过DCI激活的资源才能被使用。
CG type 1和CG type 2可以根据IE ConfiguredGrantConfig中的字段rrc-ConfiguredUplinkGrant进行区别。如果配置了字段rrc-ConfiguredUplinkGrant，则配置授权的类型为CG type 1，如果未配置字段rrc-ConfiguredUplinkGrant，则配置授权的类型为CG type 2。
在一些实施例中，终端也可以使用PUR资源进行SDT。PUR资源是用于终端在非连接状态下进行上行数据的发送而预配置的资源。该PUR资源可以为周期性资源。PUR资源可以基于第一类上行授权(grant type 1)预配置。在RRC_INACTIVE态下，终端可以利用预留好的PUR资源直接进行数据传输。
终端在进行SDT之前，需要先判断终端是否满足触发SDT的条件。只有满足触发SDT的条件，终端才可以进行SDT。如果满足触发SDT的条件，则终端可以发起SDT流程。如果不满足触发SDT的条件，则终端可以发起RRC恢复(resume)流程。例如，终端可以从RRC_INACTIVE态切换到RRC_CONNECTED态，从而进行数据的传输。
触发SDT的条件可以包括以下条件中的一种或多种：待传输数据来自可以触发SDT的无线承载；待传输数据的数据量小于预配置的数据量门限(下文也称第三预设阈值)；下行参考信号接收功率(reference signal receiving power，RSRP)的测量结果大于预配置的RSRP门限；存在有效的SDT资源。
在一些情况下，第一终端进行SDT的资源与第二终端进行随机接入的资源会发生冲突。例如，以两步随机接入过程为例，第一终端在第一传输机会上发送第一小数据包，第二终端在第二传输机会上发送两步随机接入过程中的MsgA，如果第一传输机会的资源和第二传输机会的资源至少部分重叠，即第一传输机会的资源和第二传输机会的资源发生冲突，那么网络设备该如何处理这种资源冲突，目前还没有明确的规定。
如果发生资源冲突，则SDT PUSCH和MsgA PUSCH可能都无法正确解码，这会导致频谱和能量效率降低。以CG-SDT资源为例，CG-SDT PUSCH资源通常是通过专用信令为终端配置的，因此，进行随机接入的其他终端是无法识别该CG-SDT PUSCH资源资源的，从而无法得知MsgA PUSCH资源与CG-SDT PUSCH资源冲突。因此，需要为MsgA PUSCH资源与CG-SDT PUSCH资源之间的冲突提供一种处理规则。
基于此，本申请实施例提供一种无线通信的方法及装置，为网络设备处理资源冲突提供了一种明确的方案。下面结合图4，对本申请实施例的方案进行详细介绍。
如图4所示，在步骤S410、第一终端在第一传输机会上向网络设备发送小数据包。或者说，第一终端在第一传输机会上向网络设备发送SDT PUSCH。
在一些实施例中，第一终端可以在满足触发SDT的条件下，向网络设备发送小数据包。触发SDT的条件可以参见上文的描述，此处不再赘述。
小数据包的业务类型可以有多种，本申请实施例对此不做具体限定。例如，小数据包的业务类型可以包括以下业务中的一种或多种：URLLC业务、mMTC业务、eMBB业务。
第一传输机会可以理解为传输资源。第一传输机会可以包括时域资源和/或频域资源。第一传输机会的资源也可以称为SDT资源。第一传输机会的资源例如可以为CG-SDT资源，也可以为PUR资源或RA-SDT资源。第一传输机会的资源可以是网络设备配置给第一终端的，第一传输机会的资源的配置方式将在下文进行详细描述。
需要说明的是，第一传输机会的资源也可以称为SDT PUSCH资源，或者第一资源。术语“第一传输机会的资源”、“SDT PUSCH资源”、“第一资源”根据特定上下文可以被互换地使用。在一些实施例中，第一资源可以为CG-SDT PUSCH。
需要说明的是，本申请实施例中第一终端向网络设备发送小数据包，仅表示第一终端向网络设备发送了小数据包，并不表示网络设备成功接收到小数据包，或者网络设备对小数据包进行了接收。在一些实施例中，网络设备可以根据第一传输机会是否有效，确定是否对小数据包进行接收。下文将会对第一传输机会是否有效的确定方式进行详细描述。
在步骤S420、第二终端在第二传输机会上向网络设备发送两步随机接入过程中的MsgA。或者说，第二终端可以在第二传输机会上向网络设备发送MsgA PUSCH。第二终端和第一终端可以为两个不同的终端。
MsgA中可以包括随机接入前导码以及上行数据。MsgA也可以称为MsgA PUSCH。第二传输机会可以为PRACH机会(PRACH occasion，PO)。第二传输机会可以包括时域资源和/或频域资源。第二传输机会的资源可以是网络设备配置给终端的。第二传输机会的资源可以为第二终端的专用资源。第二传输机会的资源可以通过配置授权的方式配置给第二终端。在一些实施例中，网络设备可以通过RRC信令向第二终端配置第二传输机会的资源。
需要说明的是，第二传输机会的资源也可以称为MsgA PUSCH资源，或者第二资源。术语“第二传输机会的资源”、“MsgA PUSCH资源”、“第二资源”根据特定上下文可以被互换地使用。
在不同的随机接入事件的触发下，第二终端通过MsgA PUSCH传输的数据包的大小也可能不同。因此，第二终端可以根据待传输的数据包的大小，选择相匹配的MsgA PUSCH资源。目前，通信系统可以支持2种不同的PUSCH配置，不同PUSCH配置下PUSCH的时频资源位置和大小可以不同，对应了不同的PUSCH传输包大小需求，以支持终端选择一种满足其需求的配置发起随机接入。
需要说明的是，本申请实施例中的第二终端向网络设备发送MsgA，仅表示第二终端向网络设备发送了MsgA，并不表示网络设备成功接收到MsgA，或者网络设备对MsgA进行了接收。在一些实施例中，网络设备可以根据第二传输机会是否有效，确定是否对MsgA进行接收。下文将会对第二传输机会是否有效的确定方式进行详细描述。
第一传输机会的资源和第二传输机会的资源至少部分重叠。为方便描述，下文将第一传输机会的资源称为第一资源，将第二传输机会的资源称为第二资源。第一资源和第二资源至少部分重叠可以指，第一资源的部分与第二资源的部分或全部重叠，或者，第二资源的部分与第一资源的部分或全部重叠。本申请实施例中的资源重叠可以指时域资源重叠和/或频域资源重叠。
在步骤S430、网络设备基于第一信息，确定以下事件中的一种或多种：第一传输机会是否有效；第二传输机会是否有效。
第一传输机会有效可以理解为第一终端可以使用第一传输机会成功发送小数据包，或者，网络设备可以在第一传输机会上接收第一终端发送的小数据包，或者，网络设备先接收第一终端在第一传输机会上发送的小数据包，待小数据包传输完成后，网络设备再接收第二终端在第二传输机会上发送的MsgA。
第一传输机会无效可以理解为第一终端使用第一传输机会不能成功发送小数据包，或者，网络设备放弃在第一传输机会上接收第一终端发送的小数据包，或者，网络设备先接收第二终端在第二传输机会上发送的MsgA，待MsgA传输完成后，网络设备再接收第一终端在第一传输机会上发送的小数据包。
第二传输机会有效可以理解为第二终端可以使用第二传输机会成功发送MsgA，或者，网络设备可以在第二传输机会上接收第二终端发送的MsgA，或者，网络设备先接收第二终端在第二传输机会上发送的MsgA，待MsgA传输完成后，网络设备再接收第一终端在第一传输机会上发送的小数据包。
第二传输机会无效可以理解为，第二终端使用第二传输机会不能成功发送MsgA，或者，网络设备放弃在第二传输机会上接收第二终端发送的MsgA，或者，网络设备先接收第二终端在第二传输机会上发送的MsgA，待MsgA传输完成后，网络设备再接收第一终端在第一传输机会上发送的小数据包。
在一些实施例中，网络设备可以根据第一信息确定第一传输机会是否有效。如果第一传输机会有效，则网络设备可以直接确定第二传输机会无效。如果第一传输机会无效，则网络设备可直接确定第二传输机会有效。
在一些实施例中，网络设备可以根据第一信息确定第二传输机会是否有效。如果第二传输机会有效，则网络设备可以直接确定第一传输机会无效。如果第二传输机会无效，则网络设备可直接确定第一传输机会有效。
当然，网络设备也可以基于第一信息，确定第一传输机会是否有效和第二传输机会是否有效。
如果第一传输机会有效，而第二传输机会无效，则网络设备可以仅对第一小数据包进行接收，而放弃对MsgA的接收。如果第一传输机会无效，而第二传输机会有效，则网络设备可以仅对MsgA进行接收，而放弃对第一小数据包的接收。
第一信息可以包括以下信息中的一种或多种：小数据包的业务类型；触发两步随机接入的触发条件；小数据包的重传次数。
小数据包的业务类型例如可以包括URLLC业务、mMTC业务、eMBB业务中的一种或多种。
本申请实施例可以设置优先级高于MsgA的业务类型，和/或优先级低于MsgA的业务类型，从而可以根据业务类型，确定第一传输机会或第二传输机会是否有效。
作为一个示例，mMTC业务的优先级可以高于MsgA的优先级。如果小数据包的业务类型为mMTC业务，则网络设备可以确定第一传输机会有效，和/或，第二传输机会无效。由于mMTC业务主要应用在物联网场景中，mMTC业务中的小数据包较多，将mMTC业务的优先级设置为高于MsgA的优先级，可以使得mMTC业务数据能够得到及时传输，减少数据的重传次数，提高用户体验。
作为另一个示例，eMBB业务的优先级可以低于MsgA的优先级。如果第一小数据包的业务类型为eMBB业务，则网络设备可以确定第一传输机会无效，和/或，第二传输机会有效，如图5所示。由于eMBB业务主要针对的是大流量移动宽带业务，其数据包的数量一般较少或重要性比较低，因此，可以将eMBB业务的优先级设置为低于MsgA的优先级，使得第二终端能够尽快随机接入成功。
作为又一示例，URLLC业务的优先级可以高于MsgA的优先级。如果小数据包的业务类型为URLLC业务，则网络设备可以确定第一传输机会有效，和/或，第二传输机会无效，如图6所示。由于URLLC业务一般为低时延业务，因此，先进行URLLC业务的数据包的传输，有利于保证数据包的时延要求。当然，在一些实施例中，URLLC业务的优先级也可以低于MsgA的优先级。如果小数据包的业务类型为URLLC业务，则网络设备可以确定第一传输机会无效，和/或，第二传输机会有效。
第一信息可以包括触发两步随机接入的触发条件。触发两步随机接入的触发条件可以包括多种，例如，该触发条件可以包括以下中的一种或多种：初始接入；RRC重建；小区切换；当上行链路(uplink，UL)同步状态为“失步”时，RRC_CONNECTED中的下行链路(downlink，DL)或UL数据到达；从RRC_INACTIVE接入；辅节点(secondary node，SN)建立；请求其他系统信息(system information，SI)；波束失败恢复；调度请求(scheduling request，SR)失败。其他SI可以例如包括系统信息中除主信息块(master information block，MIB)和系统信息块1(system information block1，SIB1)之外的系统信息。
在一些实施例中，可以设置第一触发条件，当两步随机接入的触发条件为该第一触发条件时，可以确定第一传输机会无效，和/或，第二传输机会有效。第一触发条件可以包括以下中的一种或多种：请求其他SI接入；波束失败恢复；SR失败。
当然，在一些实施例中，也可以设置第二触发条件，当两步随机接入的触发条件为该第二触发条件时，可以确定第一传输机会有效，和/或，第二传输机会无效。第二触发条件可以包括以下中的一种或多种：初始接入；RRC重建；小区切换；当UL同步状态为“失步”时，RRC_CONNECTED中的DL或UL数据到达；从RRC_INACTIVE接入；SN建立。
第一信息可以包括小数据包的重传次数。如果小数据包的重传次数高于预设阈值，则网络设备可以确定第一传输机会无效，或，第二传输机会有效。在小数据包的重传次数高于预设阈值时，网络设备可以放弃对小数据包的接收，而进行MsgA的接收，这样可以避免小数据包无限制地重传，导致第二终端无法成功随机接入的问题。
上述第一信息可以单独实施，也可以相互结合实施例，本申请实施例对此不做具体限定。
在一些实施例中，如果第一信息满足第一条件，则第一传输机会有效，或，第二传输机会无效。第一条件包括以下中的一种或多种：小数据包的业务类型为URLLC业务；小数据包的业务类型为mMTC业务；触发两步随机接入的触发条件不包括波束失败恢复；触发两步随机接入的触发条件不包括SR失败；触发两步随机接入的触发条件不包括请求SI。
在一些实施例中，如果第一信息满足第二条件，则第一传输机会无效，或，第一传输机会有效。第二条件包括以下中的一种或多种：小数据包的业务类型为eMBB业务；小数据包的业务类型为URLLC业务；触发两步随机接入的触发条件包括波束失败恢复；触发两步随机接入的触发条件包括SR失败；触发两步随机接入的触发条件包括请求其他SI；小数据包的重传次数高于预设门限。
作为一个示例，如果小数据包的业务类型为URLLC业务，则可以根据第二终端进行两步随机接入的触发条件，确定第一传输机会是否有效或第二传输机会是否有效。如果触发两步随机接入的触发条件包括上述第一触发条件，则第一传输机会无效，或第二传输机会有效。网络设备可以放弃小数据包的传输，而进行MsgA PUSCH的传输。如果触发两步随机接入的触发条件不包括上述第一触发条件，则第一传输机会有效，或，第二传输机会无效。网络设备可以进行小数据包的传输，而放弃对 MsgA PUSCH的传输
作为另一个示例，如果小数据包的业务类型为mMTC业务，则网络设备可以先进行小数据包的传输，MsgA PUSCH等待。但是，当小数据包的重传次数大于预设阈值时，则网络设备可以放弃小数据包的传输，而进行MsgA PUSCH的传输。
小数据包的业务类型可以基于第一资源确定。本申请实施例可以为不同的业务配置不同的资源池，网络设备可以基于第一资源所属的资源池，确定小数据包的业务类型。
例如，小数据包的业务类型可以包括多种业务类型，该多种业务类型分别对应多个资源池。多个资源池中的每个资源池用于传输与其对应的业务类型的小数据包。第一终端可以从与待发送的小数据包的业务类型匹配的资源池中选择资源，来进行小数据包的发送。
举例说明，小数据包的业务类型可以包括eMBB业务、URLLC业务、mMTC业务。如图7所示，eMBB业务对应的资源池为R1，URLLC业务对应的资源池为R2，mMTC业务对应的资源池为R3。如果第一终端中待发送的小数据包属于eMBB业务，则第一终端可以从资源池R1中选择资源来发送小数据包。如果第一终端中待发送的小数据包属于URLLC业务，则第一终端可以从资源池R2中选择资源来发送小数据包。如果第一终端中待发送的小数据包属于mMTC业务，则第一终端可以从资源池R3中选择资源来发送小数据包。
在一些实施例中，不同业务对应的资源池的大小可以相等，也可以不相等，本申请实施例对此不做具体限定。例如，本申请实施例可以根据不同业务类型的数据包的数量，来对资源池进行差异化设置，这样可以平衡不同业务的数据包的传输，以及使得资源能够合理化地配置。
例如，URLLC业务对应的资源池大小大于mMTC业务对应的资源池大小；mMTC业务对应的资源池大小大于eMBB业务对应的资源池大小；URLLC业务对应的资源池大小大于eMBB业务对应的资源池大小。由于URLLC业务具有低时延的要求，为URLLC业务配置较多的资源，可以使得URLLC业务能够及时传输，有利于满足业务时延要求。
上述多个资源池可以是网络设备配置给第一终端的，也可以是预定义的。在一些实施例中，网络设备可以通过RRC连接释放消息向终端配置多个资源池。
以图8为例，在步骤S810中，网络设备可以向第一终端发送RRC连接释放消息。该RRC连接释放消息中可以包括三个资源池的配置信息。
在步骤S820，第一终端接收到RRC连接释放消息后，进入RRC_INACTIVE状态。
在步骤S830，当第一终端有小数据包需要发送时，第一终端可以根据待发送小数据包的业务类型，选择对应的资源池，通过资源池中的资源向网络设备发送小数据包。
上述多个资源池可以对应多个定时器，即本申请实施例可以为多个资源池分别配置多个定时器。多个定时器分别用于限定多个资源池中的资源用于传输对应业务类型的小数据包的时长。换句话说，该多个资源池包括第一资源池，该第一资源池对应的定时器用于限定第一资源池的资源用于传输与第一资源池对应的业务类型的小数据包的时长。第一终端可以在第一资源池对应的定时器的时长内，使用第一资源池中的资源进行小数据包的传输。
以第一资源为CG-SDT资源为例，该多个定时器的参数可以通过CG-SDT资源配置信息来指示。
CG-SDT资源配置信息可以包括进行SDT的相关信息。例如，CG-SDT资源配置信息中可以包括以下信息中的一种或多种：一个或多个周期性时频资源、调制和编码方案(modulation and coding scheme，MCS)、传输块大小(transport block size，TBS)、多个物理上行共享信道(physical uplink shared channel，PUSCH)重复、起始位置、无线网络临时标识符(cell radio network temporary identity，C-RNTI)(例如CG-SDT C-RNTI)、时间提前量(timing advance，TA)验证准则、允许的CG-SDT资源跳跃、CG-SDT资源配置是否对一个或多个机会(occasion)、解调参考信号(demodulation reference signal，DMRS)配置、功率控制参数、物理下行控制信道(physical downlink control channel，PDCCH)搜索空间、覆盖增强(coverage enhancement，CE)的多次重复有效以及其他一些附属参数，多个定时器的相关参数。
如图7所示，eMBB业务的资源池对应的定时器为T1，URLLC业务的资源池对应的定时器为T2，mMTC业务的资源池对应的定时器为T3。定时器T1用于限定资源池R1用于传输eMBB业务的时长。定时器T2用于限定资源池R2用于传输URLLC业务的时长。定时器T3用于限定资源池R3用于传输mMTC业务的时长。
在定时器T1的有效期内，资源池R1中的资源可用于传输eMBB业务的小数据包。在定时器T1超时后，资源池R1中的资源不能用于传输eMBB业务的小数据包。或者说，在定时器T1超时后，第一终端不能传输eMBB业务的小数据包。
在定时器T2的有效期内，资源池R2中的资源可用于传输URLLC业务的小数据包。在定时器 T2超时后，资源池R2中的资源不能用于传输URLLC业务的小数据包。或者说，在定时器T2超时后，第一终端不能传输URLLC业务的小数据包。
在定时器T3的有效期内，资源池R3中的资源可用于传输mMTC业务的小数据包。在定时器T3超时后，资源池R3中的资源不能用于传输mMTC业务的小数据包。或者说，在定时器T3超时后，第一终端不能传输mMTC业务的小数据包。
上述多个资源池对应的多个定时器的时长可以相等，也可以不相等，本申请实施例对此不做具体限定。在一些实施例中，URLLC业务的资源池对应的定时器时长大于mMTC业务的资源池对应的定时器时长；mMTC业务的资源池对应的定时器时长大于eMBB业务的资源池对应的定时器时长；URLLC业务的资源池对应的定时器时长大于eMBB业务的资源池对应的定时器时长。
在一些实施例中，可以根据不同业务的分布情况，确定定时器的时长。例如，可以为数据包的数量较多的业务类型设置较大的定时器，而为数据包的数量较少的业务类型设置较小的定时器。
举例说明，假设多种业务类型包括第一业务和第二业务，第一业务对应第一资源池，第二业务对应第二资源池，第一资源池对应第一定时器，第二资源池对应第二定时器。如果第二业务的数据包的数量多于第一业务的数据包的数量，则第二定时器的时长可以大于第一定时器的时长，这样可以使得第二业务的数据包能够得到更多的传输。
在一些实施例中，如果某个资源池对应的定时器超时，则该资源池中的资源可以用于其他业务类型的数据传输。仍以上述第一业务和第二业务为例，如果第一定时器的时长小于第二定时器的时长，则在第一定时器超时后，第一资源池在的资源可用于第二业务的数据包的传输。
举例说明，以上述定时器T1、T2和T3为例，假设T2＞T3＞T1，则在定时器T1超时后，资源池R1中的资源可共享给mMTC业务和URLLC业务。也就是说，在定时器T1超时后，第一终端可以使用资源池R1中的资源传输mMTC业务和URLLC业务的小数据包。
下面以eMBB业务、URLLC业务、mMTC业务为例，结合图7和图8对不同业务的数据包的传输过程进行说明。
图9示出的是三个定时器的时长相等的情况。参见图9，在步骤S910、第一终端处于RRC_INACTIVE状态，第一终端可以开启定时器T1、T2和T3。
在步骤S920、第一终端确定定时器T1或T2或T3是否超时。
在步骤S930、在定时器T1或T2或T3的有效期内，第一终端确定是否需要发送小数据包。
在步骤S940、如果第一终端需要发送小数据包，则第一终端在待发送的小数据包对应的资源池中选择资源，并在该资源上发送小数据包。
如果定时器T1或T2或T3超时，则第一终端释放资源池中的资源，第一终端不能进行小数据包的传输。
图10示出的是三个定时器的时长不相等的情况。参见图10，在步骤S1010、第一终端处于RRC_INACTIVE状态，第一终端可以使用资源池中的资源发送与该资源池对应的业务数据包。
在步骤S1020、第一终端开启各个资源池对应的定时器，第一终端开启定时器T1、T2和T3。
在步骤S1030、第一终端确定定时器T1是否超时。如果定时器T1未超时，则第一终端可以使用资源池R1中的资源传输eMBB业务的小数据包。
在步骤S1040、如果定时器T1超时，则第一终端可以释放资源池R1中的资源。在一些实施例中，第一终端可以将资源池R1中的资源释放到共享资源池中，使得该资源池R1中的资源可用于传输URLLC业务、mMTC业务的小数据包。
在步骤S1050、第一终端确定定时器T3是否超时。如果定时器T3未超时，则第一终端可以使用资源池R3中的资源传输mMTC业务的小数据包。
在步骤S1060、如果定时器T3超时，则第一终端可以释放资源池R3中的资源。在一些实施例中，第一终端可以将资源池R3中的资源释放到共享资源池中，使得该资源池R3中的资源可用于传输URLLC业务的小数据包。
在步骤S1070、第一终端确定定时器T2时是否超时。如果定时器T2未超时，则第一终端可以使用资源池R2中的资源传输URLLC业务的小数据包。
在步骤S1080、如果定时器T2超时，则第一终端可以释放资源池R2中的资源。另外，第一终端将无法进行小数据包的传输，即第一终端将不能传输任何业务类型的小数据包。
上文结合图1至图10，详细描述了本申请的方法实施例，下面结合图11至图14，详细描述本申请的装置实施例。应理解，方法实施例的描述与装置实施例的描述相互对应，因此，未详细描述的部分可以参见前面方法实施例。
图11是本申请一个实施例提供的无线通信的装置的示意性结构图。该装置可以为网络设备。图11 所示的网络设备可以为上文描述的任意一种网络设备。所述网络设备1100包括确定单元1110。
确定单元1110，可用于基于第一信息，确定以下事件中的一种或多种：用于第一终端发送小数据包的第一传输机会是否有效；用于第二终端发送两步随机接入过程中的消息A的第二传输机会是否有效。其中，所述第二传输机会的资源与所述第一传输机会的资源至少部分重叠。
所述第一信息包括以下信息中的一种或多种：所述小数据包的业务类型；触发两步随机接入的触发条件；所述小数据包的重传次数。
在一些实施例中，如果所述第一信息满足第一条件，则所述第一传输机会有效，或所述第二传输机会无效，所述第一条件包括以下中的一种或多种：所述小数据包的业务类型为URLLC业务；所述小数据包的业务类型为mMTC业务；触发两步随机接入的触发条件不包括波束失败恢复；触发两步随机接入的触发条件不包括SR失败；触发两步随机接入的触发条件不包括请求其他SI。
在一些实施例中，如果所述第一信息满足第二条件，则所述第一传输机会无效，或所述第二传输机会有效，所述第二条件包括以下中的一种或多种：所述小数据包的业务类型为eMBB业务；所述小数据包的业务类型为URLLC业务；触发两步随机接入的触发条件包括波束失败恢复；触发两步随机接入的触发条件包括SR失败；触发两步随机接入的触发条件包括请求其他SI；所述小数据包的重传次数高于预设门限。
在一些实施例中，所述小数据包的业务类型基于所述第一传输机会的资源确定。
在一些实施例中，所述小数据包的业务类型包括多种业务类型，所述多种业务类型分别对应多个资源池，所述多个资源池中每个资源池中的资源用于传输与其对应的业务类型的小数据包。
在一些实施例中，URLLC业务对应的资源池大小大于mMTC业务对应的资源池大小；mMTC业务对应的资源池大小大于eMBB业务对应的资源池大小；URLLC业务对应的资源池大小大于eMBB业务对应的资源池大小。
在一些实施例中，所述多个资源池分别对应多个定时器，所述多个定时器分别用于限定所述多个资源池中的资源用于传输对应业务类型的小数据包的时长。
在一些实施例中，所述多个定时器的时长相等。
在一些实施例中，所述多个定时器的时长不相等。
在一些实施例中，所述多种业务类型包括第一业务和第二业务，所述第一业务对应第一资源池，所述第二业务对应第二资源池，所述第一资源池对应第一定时器，所述第二资源池对应第二定时器，如果所述第一定时器的时长小于所述第二定时器的时长，则在所述第一定时器超时后，所述第一资源池中的资源用于所述第二业务的小数据包的传输。
在一些实施例中，URLLC业务的资源池对应的定时器时长大于mMTC业务的资源池对应的定时器时长；mMTC业务的资源池对应的定时器时长大于eMBB业务的资源池对应的定时器时长；URLLC业务的资源池对应的定时器时长大于eMBB业务的资源池对应的定时器时长。
在一些实施例中，所述第一传输机会的资源为CG-SDT资源。
图12是本申请一个实施例提供的无线通信的装置的示意性结构图。该装置可以为第一终端。图12所示的第一终端可以为上文描述的任意一种第一终端。所述第一终端1200包括发送单元1210。
发送单元1210，可用于在第一传输机会上向网络设备发送小数据包，所述第一传输机会的资源与第二传输机会的资源至少部分重叠，所述第二传输机会用于第二终端向所述网络设备发送两步随机接入过程中的消息A。
所述第一传输机会或所述第二传输机会是否有效基于第一信息确定。所述第一信息包括以下信息中的一种或多种：所述小数据包的业务类型；触发两步随机接入的触发条件；所述小数据包的重传次数。
在一些实施例中，如果所述第一信息满足第一条件，则所述第一传输机会有效，或所述第二传输机会无效，所述第一条件包括以下中的一种或多种：所述小数据包的业务类型为URLLC业务；所述小数据包的业务类型为mMTC业务；触发两步随机接入的触发条件不包括波束失败恢复；触发两步随机接入的触发条件不包括SR失败；触发两步随机接入的触发条件不包括请求其他SI。
在一些实施例中，如果所述第一信息满足第二条件，则所述第一传输机会无效，或所述第二传输机会有效，所述第二条件包括以下中的一种或多种：所述小数据包的业务类型为eMBB业务；所述小数据包的业务类型为URLLC业务；触发两步随机接入的触发条件包括波束失败恢复；触发两步随机接入的触发条件包括SR失败；触发两步随机接入的触发条件包括请求其他SI；所述小数据包的重传次数高于预设门限。
在一些实施例中，所述小数据包的业务类型基于所述第一传输机会的资源确定。
在一些实施例中，所述小数据包的业务类型包括多种业务类型，所述多种业务类型分别对应多个 资源池，所述多个资源池中每个资源池中的资源用于传输与其对应的业务类型的小数据包。
在一些实施例中，URLLC业务对应的资源池大小大于mMTC业务对应的资源池大小；mMTC业务对应的资源池大小大于eMBB业务对应的资源池大小；URLLC业务对应的资源池大小大于eMBB业务对应的资源池大小。
在一些实施例中，所述多个资源池分别对应多个定时器，所述多个定时器分别用于限定所述多个资源池中的资源用于传输对应业务类型的小数据包的时长。
在一些实施例中，所述多个定时器的时长相等。
在一些实施例中，所述多个定时器的时长不相等。
在一些实施例中，所述多种业务类型包括第一业务和第二业务，所述第一业务对应第一资源池，所述第二业务对应第二资源池，所述第一资源池对应第一定时器，所述第二资源池对应第二定时器，如果所述第一定时器的时长小于所述第二定时器的时长，则在所述第一定时器超时后，所述第一资源池中的资源用于所述第二业务的小数据包的传输。
在一些实施例中，URLLC业务的资源池对应的定时器时长大于mMTC业务的资源池对应的定时器时长；mMTC业务的资源池对应的定时器时长大于eMBB业务的资源池对应的定时器时长；URLLC业务的资源池对应的定时器时长大于eMBB业务的资源池对应的定时器时长。
在一些实施例中，所述第一传输机会的资源为CG-SDT资源。
图13是本申请一个实施例提供的无线通信的装置的示意性结构图。该装置可以为第二终端。图13所示的第二终端可以为上文描述的任意一种第二终端。所述第二终端1300包括发送单元1310。
发送单元1310，可用于在第二传输机会上向网络设备发送两步随机接入过程中的消息A，所述第二传输机会的资源与第一传输机会的资源至少部分重叠，所述第一传输机会用于第一终端向所述网络设备发送小数据包。
所述第一传输机会或所述第二传输机会是否有效基于第一信息确定。所述第一信息包括以下信息中的一种或多种：所述小数据包的业务类型；触发两步随机接入的触发条件；所述小数据包的重传次数。
在一些实施例中，如果所述第一信息满足第一条件，则所述第一传输机会有效，或所述第二传输机会无效，所述第一条件包括以下中的一种或多种：所述小数据包的业务类型为URLLC业务；所述小数据包的业务类型为mMTC业务；触发两步随机接入的触发条件不包括波束失败恢复；触发两步随机接入的触发条件不包括SR失败；触发两步随机接入的触发条件不包括请求其他SI。
在一些实施例中，如果所述第一信息满足第二条件，则所述第一传输机会无效，或所述第二传输机会有效，所述第二条件包括以下中的一种或多种：所述小数据包的业务类型为eMBB业务；所述小数据包的业务类型为URLLC业务；触发两步随机接入的触发条件包括波束失败恢复；触发两步随机接入的触发条件包括SR失败；触发两步随机接入的触发条件包括请求其他SI；所述小数据包的重传次数高于预设门限。
在一些实施例中，所述小数据包的业务类型基于所述第一传输机会的资源确定。
在一些实施例中，所述小数据包的业务类型包括多种业务类型，所述多种业务类型分别对应多个资源池，所述多个资源池中每个资源池中的资源用于传输与其对应的业务类型的小数据包。
在一些实施例中，URLLC业务对应的资源池大小大于mMTC业务对应的资源池大小；mMTC业务对应的资源池大小大于eMBB业务对应的资源池大小；URLLC业务对应的资源池大小大于eMBB业务对应的资源池大小。
在一些实施例中，所述多个资源池分别对应多个定时器，所述多个定时器分别用于限定所述多个资源池中的资源用于传输对应业务类型的小数据包的时长。
在一些实施例中，所述多个定时器的时长相等。
在一些实施例中，所述多个定时器的时长不相等。
在一些实施例中，所述多种业务类型包括第一业务和第二业务，所述第一业务对应第一资源池，所述第二业务对应第二资源池，所述第一资源池对应第一定时器，所述第二资源池对应第二定时器，如果所述第一定时器的时长小于所述第二定时器的时长，则在所述第一定时器超时后，所述第一资源池中的资源用于所述第二业务的小数据包的传输。
在一些实施例中，URLLC业务的资源池对应的定时器时长大于mMTC业务的资源池对应的定时器时长；mMTC业务的资源池对应的定时器时长大于eMBB业务的资源池对应的定时器时长；URLLC业务的资源池对应的定时器时长大于eMBB业务的资源池对应的定时器时长。
在一些实施例中，所述第一传输机会的资源为CG-SDT资源。
图14是本申请实施例的装置的示意性结构图。图14中的虚线表示该单元或模块为可选的。该装 置1400可用于实现上述方法实施例中描述的方法。装置1400可以是芯片、第一终端、第二终端、网络设备中的一种或多种。
装置1400可以包括一个或多个处理器1410。该处理器1410可支持装置1400实现前文方法实施例所描述的方法。该处理器1410可以是通用处理器或者专用处理器。例如，该处理器可以为中央处理单元(central processing unit，CPU)。或者，该处理器还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
装置1400还可以包括一个或多个存储器1420。存储器1420上存储有程序，该程序可以被处理器1410执行，使得处理器1410执行前文方法实施例所描述的方法。存储器1420可以独立于处理器1410也可以集成在处理器1410中。
装置1400还可以包括收发器1430。处理器1410可以通过收发器1430与其他设备或芯片进行通信。例如，处理器1410可以通过收发器1430与其他设备或芯片进行数据收发。
本申请实施例还提供一种计算机可读存储介质，用于存储程序。该计算机可读存储介质可应用于本申请实施例提供的终端或网络设备中，并且该程序使得计算机执行本申请各个实施例中的由终端或网络设备执行的方法。
本申请实施例还提供一种计算机程序产品。该计算机程序产品包括程序。该计算机程序产品可应用于本申请实施例提供的终端或网络设备中，并且该程序使得计算机执行本申请各个实施例中的由终端或网络设备执行的方法。
本申请实施例还提供一种计算机程序。该计算机程序可应用于本申请实施例提供的终端或网络设备中，并且该计算机程序使得计算机执行本申请各个实施例中的由终端或网络设备执行的方法。
应理解，在本申请实施例中，“与A相应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够读取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，数字通用光盘(digital video disc，DVD))或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (78)

  1. 一种无线通信的方法，其特征在于，包括：
    网络设备基于第一信息，确定以下事件中的一种或多种：
    用于第一终端发送小数据包的第一传输机会是否有效；
    用于第二终端发送两步随机接入过程中的消息A的第二传输机会是否有效；
    其中，所述第二传输机会的资源与所述第一传输机会的资源至少部分重叠；
    所述第一信息包括以下信息中的一种或多种：
    所述小数据包的业务类型；
    触发两步随机接入的触发条件；
    所述小数据包的重传次数。
  2. 根据权利要求1所述的方法，其特征在于，如果所述第一信息满足第一条件，则所述第一传输机会有效，或所述第二传输机会无效，所述第一条件包括以下中的一种或多种：
    所述小数据包的业务类型为高可靠低时延URLLC业务；
    所述小数据包的业务类型为大规模机器通信mMTC业务；
    触发两步随机接入的触发条件不包括波束失败恢复；
    触发两步随机接入的触发条件不包括调度请求SR失败；
    触发两步随机接入的触发条件不包括请求其他系统信息SI。
  3. 根据权利要求1所述的方法，其特征在于，如果所述第一信息满足第二条件，则所述第一传输机会无效，或所述第二传输机会有效，所述第二条件包括以下中的一种或多种：
    所述小数据包的业务类型为增强移动宽带eMBB业务；
    所述小数据包的业务类型为URLLC业务；
    触发两步随机接入的触发条件包括波束失败恢复；
    触发两步随机接入的触发条件包括SR失败；
    触发两步随机接入的触发条件包括请求其他SI；
    所述小数据包的重传次数高于预设门限。
  4. 根据权利要求1-3中任一项所述的方法，其特征在于，所述小数据包的业务类型基于所述第一传输机会的资源确定。
  5. 根据权利要求4所述的方法，其特征在于，所述小数据包的业务类型包括多种业务类型，所述多种业务类型分别对应多个资源池，所述多个资源池中每个资源池中的资源用于传输与其对应的业务类型的小数据包。
  6. 根据权利要求5所述的方法，其特征在于，
    URLLC业务对应的资源池大小大于mMTC业务对应的资源池大小；
    mMTC业务对应的资源池大小大于eMBB业务对应的资源池大小；
    URLLC业务对应的资源池大小大于eMBB业务对应的资源池大小。
  7. 根据权利要求5或6所述的方法，其特征在于，
    所述多个资源池分别对应多个定时器，所述多个定时器分别用于限定所述多个资源池中的资源用于传输对应业务类型的小数据包的时长。
  8. 根据权利要求7所述的方法，其特征在于，所述多个定时器的时长相等。
  9. 根据权利要求7所述的方法，其特征在于，所述多个定时器的时长不相等。
  10. 根据权利要求9所述的方法，其特征在于，所述多种业务类型包括第一业务和第二业务，所述第一业务对应第一资源池，所述第二业务对应第二资源池，所述第一资源池对应第一定时器，所述第二资源池对应第二定时器，
    如果所述第一定时器的时长小于所述第二定时器的时长，则在所述第一定时器超时后，所述第一资源池中的资源用于所述第二业务的小数据包的传输。
  11. 根据权利要求7-10中任一项所述的方法，其特征在于，
    URLLC业务的资源池对应的定时器时长大于mMTC业务的资源池对应的定时器时长；
    mMTC业务的资源池对应的定时器时长大于eMBB业务的资源池对应的定时器时长；
    URLLC业务的资源池对应的定时器时长大于eMBB业务的资源池对应的定时器时长。
  12. 根据权利要求1-11中任一项所述的方法，其特征在于，所述第一传输机会的资源为配置授权小数据传输CG-SDT资源。
  13. 一种无线通信的方法，其特征在于，包括：
    第一终端在第一传输机会上向网络设备发送小数据包，所述第一传输机会的资源与第二传输机会 的资源至少部分重叠，所述第二传输机会用于第二终端向所述网络设备发送两步随机接入过程中的消息A，所述第一传输机会或所述第二传输机会是否有效基于第一信息确定，
    所述第一信息包括以下信息中的一种或多种：
    所述小数据包的业务类型；
    触发两步随机接入的触发条件；
    所述小数据包的重传次数。
  14. 根据权利要求13所述的方法，其特征在于，如果所述第一信息满足第一条件，则所述第一传输机会有效，或所述第二传输机会无效，所述第一条件包括以下中的一种或多种：
    所述小数据包的业务类型为高可靠低时延URLLC业务；
    所述小数据包的业务类型为大规模机器通信mMTC业务；
    触发两步随机接入的触发条件不包括波束失败恢复；
    触发两步随机接入的触发条件不包括调度请求SR失败；
    触发两步随机接入的触发条件不包括请求其他系统信息SI。
  15. 根据权利要求13所述的方法，其特征在于，如果所述第一信息满足第二条件，则所述第一传输机会无效，或所述第二传输机会有效，所述第二条件包括以下中的一种或多种：
    所述小数据包的业务类型为增强移动宽带eMBB业务；
    所述小数据包的业务类型为URLLC业务；
    触发两步随机接入的触发条件包括波束失败恢复；
    触发两步随机接入的触发条件包括SR失败；
    触发两步随机接入的触发条件包括请求其他SI；
    所述小数据包的重传次数高于预设门限。
  16. 根据权利要求13-15中任一项所述的方法，其特征在于，所述小数据包的业务类型基于所述第一传输机会的资源确定。
  17. 根据权利要求16所述的方法，其特征在于，所述小数据包的业务类型包括多种业务类型，所述多种业务类型分别对应多个资源池，所述多个资源池中每个资源池中的资源用于传输与其对应的业务类型的小数据包。
  18. 根据权利要求17所述的方法，其特征在于，
    URLLC业务对应的资源池大小大于mMTC业务对应的资源池大小；
    mMTC业务对应的资源池大小大于eMBB业务对应的资源池大小；
    URLLC业务对应的资源池大小大于eMBB业务对应的资源池大小。
  19. 根据权利要求17或18所述的方法，其特征在于，
    所述多个资源池分别对应多个定时器，所述多个定时器分别用于限定所述多个资源池中的资源用于传输对应业务类型的小数据包的时长。
  20. 根据权利要求19所述的方法，其特征在于，所述多个定时器的时长相等。
  21. 根据权利要求19所述的方法，其特征在于，所述多个定时器的时长不相等。
  22. 根据权利要求21所述的方法，其特征在于，所述多种业务类型包括第一业务和第二业务，所述第一业务对应第一资源池，所述第二业务对应第二资源池，所述第一资源池对应第一定时器，所述第二资源池对应第二定时器，
    如果所述第一定时器的时长小于所述第二定时器的时长，则在所述第一定时器超时后，所述第一资源池中的资源用于所述第二业务的小数据包的传输。
  23. 根据权利要求19-22中任一项所述的方法，其特征在于，
    URLLC业务的资源池对应的定时器时长大于mMTC业务的资源池对应的定时器时长；
    mMTC业务的资源池对应的定时器时长大于eMBB业务的资源池对应的定时器时长；
    URLLC业务的资源池对应的定时器时长大于eMBB业务的资源池对应的定时器时长。
  24. 根据权利要求13-23中任一项所述的方法，其特征在于，所述第一传输机会的资源为配置授权小数据传输CG-SDT资源。
  25. 一种无线通信的方法，其特征在于，包括：
    第二终端在第二传输机会上向网络设备发送两步随机接入过程中的消息A，所述第二传输机会的资源与第一传输机会的资源至少部分重叠，所述第一传输机会用于第一终端向所述网络设备发送小数据包，所述第一传输机会或所述第二传输机会是否有效基于第一信息确定，
    所述第一信息包括以下信息中的一种或多种：
    所述小数据包的业务类型；
    触发两步随机接入的触发条件；
    所述小数据包的重传次数。
  26. 根据权利要求25所述的方法，其特征在于，如果所述第一信息满足第一条件，则所述第一传输机会有效，或所述第二传输机会无效，所述第一条件包括以下中的一种或多种：
    所述小数据包的业务类型为高可靠低时延URLLC业务；
    所述小数据包的业务类型为大规模机器通信mMTC业务；
    触发两步随机接入的触发条件不包括波束失败恢复；
    触发两步随机接入的触发条件不包括调度请求SR失败；
    触发两步随机接入的触发条件不包括请求其他系统信息SI。
  27. 根据权利要求25所述的方法，其特征在于，如果所述第一信息满足第二条件，则所述第一传输机会无效，或所述第二传输机会有效，所述第二条件包括以下中的一种或多种：
    所述小数据包的业务类型为增强移动宽带eMBB业务；
    所述小数据包的业务类型为URLLC业务；
    触发两步随机接入的触发条件包括波束失败恢复；
    触发两步随机接入的触发条件包括SR失败；
    触发两步随机接入的触发条件包括请求其他SI；
    所述小数据包的重传次数高于预设门限。
  28. 根据权利要求25-27中任一项所述的方法，其特征在于，所述小数据包的业务类型基于所述第一传输机会的资源确定。
  29. 根据权利要求28所述的方法，其特征在于，所述小数据包的业务类型包括多种业务类型，所述多种业务类型分别对应多个资源池，所述多个资源池中每个资源池中的资源用于传输与其对应的业务类型的小数据包。
  30. 根据权利要求29所述的方法，其特征在于，
    URLLC业务对应的资源池大小大于mMTC业务对应的资源池大小；
    mMTC业务对应的资源池大小大于eMBB业务对应的资源池大小；
    URLLC业务对应的资源池大小大于eMBB业务对应的资源池大小。
  31. 根据权利要求29或30所述的方法，其特征在于，
    所述多个资源池分别对应多个定时器，所述多个定时器分别用于限定所述多个资源池中的资源用于传输对应业务类型的小数据包的时长。
  32. 根据权利要求31所述的方法，其特征在于，所述多个定时器的时长相等。
  33. 根据权利要求31所述的方法，其特征在于，所述多个定时器的时长不相等。
  34. 根据权利要求33所述的方法，其特征在于，所述多种业务类型包括第一业务和第二业务，所述第一业务对应第一资源池，所述第二业务对应第二资源池，所述第一资源池对应第一定时器，所述第二资源池对应第二定时器，
    如果所述第一定时器的时长小于所述第二定时器的时长，则在所述第一定时器超时后，所述第一资源池中的资源用于所述第二业务的小数据包的传输。
  35. 根据权利要求31-34中任一项所述的方法，其特征在于，
    URLLC业务的资源池对应的定时器时长大于mMTC业务的资源池对应的定时器时长；
    mMTC业务的资源池对应的定时器时长大于eMBB业务的资源池对应的定时器时长；
    URLLC业务的资源池对应的定时器时长大于eMBB业务的资源池对应的定时器时长。
  36. 根据权利要求25-35中任一项所述的方法，其特征在于，所述第一传输机会的资源为配置授权小数据传输CG-SDT资源。
  37. 一种无线通信的装置，其特征在于，所述装置为网络设备，所述装置包括：
    确定单元，用于基于第一信息，确定以下事件中的一种或多种：
    用于第一终端发送小数据包的第一传输机会是否有效；
    用于第二终端发送两步随机接入过程中的消息A的第二传输机会是否有效；
    其中，所述第二传输机会的资源与所述第一传输机会的资源至少部分重叠；
    所述第一信息包括以下信息中的一种或多种：
    所述小数据包的业务类型；
    触发两步随机接入的触发条件；
    所述小数据包的重传次数。
  38. 根据权利要求37所述的装置，其特征在于，如果所述第一信息满足第一条件，则所述第一 传输机会有效，或所述第二传输机会无效，所述第一条件包括以下中的一种或多种：
    所述小数据包的业务类型为高可靠低时延URLLC业务；
    所述小数据包的业务类型为大规模机器通信mMTC业务；
    触发两步随机接入的触发条件不包括波束失败恢复；
    触发两步随机接入的触发条件不包括调度请求SR失败；
    触发两步随机接入的触发条件不包括请求其他系统信息SI。
  39. 根据权利要求37所述的装置，其特征在于，如果所述第一信息满足第二条件，则所述第一传输机会无效，或所述第二传输机会有效，所述第二条件包括以下中的一种或多种：
    所述小数据包的业务类型为增强移动宽带eMBB业务；
    所述小数据包的业务类型为URLLC业务；
    触发两步随机接入的触发条件包括波束失败恢复；
    触发两步随机接入的触发条件包括SR失败；
    触发两步随机接入的触发条件包括请求其他SI；
    所述小数据包的重传次数高于预设门限。
  40. 根据权利要求37-39中任一项所述的装置，其特征在于，所述小数据包的业务类型基于所述第一传输机会的资源确定。
  41. 根据权利要求40所述的装置，其特征在于，所述小数据包的业务类型包括多种业务类型，所述多种业务类型分别对应多个资源池，所述多个资源池中每个资源池中的资源用于传输与其对应的业务类型的小数据包。
  42. 根据权利要求41所述的装置，其特征在于，
    URLLC业务对应的资源池大小大于mMTC业务对应的资源池大小；
    mMTC业务对应的资源池大小大于eMBB业务对应的资源池大小；
    URLLC业务对应的资源池大小大于eMBB业务对应的资源池大小。
  43. 根据权利要求41或42所述的装置，其特征在于，
    所述多个资源池分别对应多个定时器，所述多个定时器分别用于限定所述多个资源池中的资源用于传输对应业务类型的小数据包的时长。
  44. 根据权利要求43所述的装置，其特征在于，所述多个定时器的时长相等。
  45. 根据权利要求43所述的装置，其特征在于，所述多个定时器的时长不相等。
  46. 根据权利要求45所述的装置，其特征在于，所述多种业务类型包括第一业务和第二业务，所述第一业务对应第一资源池，所述第二业务对应第二资源池，所述第一资源池对应第一定时器，所述第二资源池对应第二定时器，
    如果所述第一定时器的时长小于所述第二定时器的时长，则在所述第一定时器超时后，所述第一资源池中的资源用于所述第二业务的小数据包的传输。
  47. 根据权利要求43-46中任一项所述的装置，其特征在于，
    URLLC业务的资源池对应的定时器时长大于mMTC业务的资源池对应的定时器时长；
    mMTC业务的资源池对应的定时器时长大于eMBB业务的资源池对应的定时器时长；
    URLLC业务的资源池对应的定时器时长大于eMBB业务的资源池对应的定时器时长。
  48. 根据权利要求37-47中任一项所述的装置，其特征在于，所述第一传输机会的资源为配置授权小数据传输CG-SDT资源。
  49. 一种无线通信的装置，其特征在于，所述装置为第一终端，所述装置包括：
    发送单元，用于在第一传输机会上向网络设备发送小数据包，所述第一传输机会的资源与第二传输机会的资源至少部分重叠，所述第二传输机会用于第二终端向所述网络设备发送两步随机接入过程中的消息A，所述第一传输机会或所述第二传输机会是否有效基于第一信息确定，
    所述第一信息包括以下信息中的一种或多种：
    所述小数据包的业务类型；
    触发两步随机接入的触发条件；
    所述小数据包的重传次数。
  50. 根据权利要求49所述的装置，其特征在于，如果所述第一信息满足第一条件，则所述第一传输机会有效，或所述第二传输机会无效，所述第一条件包括以下中的一种或多种：
    所述小数据包的业务类型为高可靠低时延URLLC业务；
    所述小数据包的业务类型为大规模机器通信mMTC业务；
    触发两步随机接入的触发条件不包括波束失败恢复；
    触发两步随机接入的触发条件不包括调度请求SR失败；
    触发两步随机接入的触发条件不包括请求其他系统信息SI。
  51. 根据权利要求49所述的装置，其特征在于，如果所述第一信息满足第二条件，则所述第一传输机会无效，或所述第二传输机会有效，所述第二条件包括以下中的一种或多种：
    所述小数据包的业务类型为增强移动宽带eMBB业务；
    所述小数据包的业务类型为URLLC业务；
    触发两步随机接入的触发条件包括波束失败恢复；
    触发两步随机接入的触发条件包括SR失败；
    触发两步随机接入的触发条件包括请求其他SI；
    所述小数据包的重传次数高于预设门限。
  52. 根据权利要求49-51中任一项所述的装置，其特征在于，所述小数据包的业务类型基于所述第一传输机会的资源确定。
  53. 根据权利要求52所述的装置，其特征在于，所述小数据包的业务类型包括多种业务类型，所述多种业务类型分别对应多个资源池，所述多个资源池中每个资源池中的资源用于传输与其对应的业务类型的小数据包。
  54. 根据权利要求53所述的装置，其特征在于，
    URLLC业务对应的资源池大小大于mMTC业务对应的资源池大小；
    mMTC业务对应的资源池大小大于eMBB业务对应的资源池大小；
    URLLC业务对应的资源池大小大于eMBB业务对应的资源池大小。
  55. 根据权利要求53或54所述的装置，其特征在于，
    所述多个资源池分别对应多个定时器，所述多个定时器分别用于限定所述多个资源池中的资源用于传输对应业务类型的小数据包的时长。
  56. 根据权利要求55所述的装置，其特征在于，所述多个定时器的时长相等。
  57. 根据权利要求55所述的装置，其特征在于，所述多个定时器的时长不相等。
  58. 根据权利要求57所述的装置，其特征在于，所述多种业务类型包括第一业务和第二业务，所述第一业务对应第一资源池，所述第二业务对应第二资源池，所述第一资源池对应第一定时器，所述第二资源池对应第二定时器，
    如果所述第一定时器的时长小于所述第二定时器的时长，则在所述第一定时器超时后，所述第一资源池中的资源用于所述第二业务的小数据包的传输。
  59. 根据权利要求55-58中任一项所述的装置，其特征在于，
    URLLC业务的资源池对应的定时器时长大于mMTC业务的资源池对应的定时器时长；
    mMTC业务的资源池对应的定时器时长大于eMBB业务的资源池对应的定时器时长；
    URLLC业务的资源池对应的定时器时长大于eMBB业务的资源池对应的定时器时长。
  60. 根据权利要求49-59中任一项所述的装置，其特征在于，所述第一传输机会的资源为配置授权小数据传输CG-SDT资源。
  61. 一种无线通信的装置，其特征在于，所述装置为第二终端，所述装置包括：
    发送单元，用于在第二传输机会上向网络设备发送两步随机接入过程中的消息A，所述第二传输机会的资源与第一传输机会的资源至少部分重叠，所述第一传输机会用于第一终端向所述网络设备发送小数据包，所述第一传输机会或所述第二传输机会是否有效基于第一信息确定，
    所述第一信息包括以下信息中的一种或多种：
    所述小数据包的业务类型；
    触发两步随机接入的触发条件；
    所述小数据包的重传次数。
  62. 根据权利要求61所述的装置，其特征在于，如果所述第一信息满足第一条件，则所述第一传输机会有效，或所述第二传输机会无效，所述第一条件包括以下中的一种或多种：
    所述小数据包的业务类型为高可靠低时延URLLC业务；
    所述小数据包的业务类型为大规模机器通信mMTC业务；
    触发两步随机接入的触发条件不包括波束失败恢复；
    触发两步随机接入的触发条件不包括调度请求SR失败；
    触发两步随机接入的触发条件不包括请求其他系统信息SI。
  63. 根据权利要求61所述的装置，其特征在于，如果所述第一信息满足第二条件，则所述第一传输机会无效，或所述第二传输机会有效，所述第二条件包括以下中的一种或多种：
    所述小数据包的业务类型为增强移动宽带eMBB业务；
    所述小数据包的业务类型为URLLC业务；
    触发两步随机接入的触发条件包括波束失败恢复；
    触发两步随机接入的触发条件包括SR失败；
    触发两步随机接入的触发条件包括请求其他SI；
    所述小数据包的重传次数高于预设门限。
  64. 根据权利要求61-63中任一项所述的装置，其特征在于，所述小数据包的业务类型基于所述第一传输机会的资源确定。
  65. 根据权利要求64所述的装置，其特征在于，所述小数据包的业务类型包括多种业务类型，所述多种业务类型分别对应多个资源池，所述多个资源池中每个资源池中的资源用于传输与其对应的业务类型的小数据包。
  66. 根据权利要求65所述的装置，其特征在于，
    URLLC业务对应的资源池大小大于mMTC业务对应的资源池大小；
    mMTC业务对应的资源池大小大于eMBB业务对应的资源池大小；
    URLLC业务对应的资源池大小大于eMBB业务对应的资源池大小。
  67. 根据权利要求65或66所述的装置，其特征在于，
    所述多个资源池分别对应多个定时器，所述多个定时器分别用于限定所述多个资源池中的资源用于传输对应业务类型的小数据包的时长。
  68. 根据权利要求67所述的装置，其特征在于，所述多个定时器的时长相等。
  69. 根据权利要求67所述的装置，其特征在于，所述多个定时器的时长不相等。
  70. 根据权利要求69所述的装置，其特征在于，所述多种业务类型包括第一业务和第二业务，所述第一业务对应第一资源池，所述第二业务对应第二资源池，所述第一资源池对应第一定时器，所述第二资源池对应第二定时器，
    如果所述第一定时器的时长小于所述第二定时器的时长，则在所述第一定时器超时后，所述第一资源池中的资源用于所述第二业务的小数据包的传输。
  71. 根据权利要求67-70中任一项所述的装置，其特征在于，
    URLLC业务的资源池对应的定时器时长大于mMTC业务的资源池对应的定时器时长；
    mMTC业务的资源池对应的定时器时长大于eMBB业务的资源池对应的定时器时长；
    URLLC业务的资源池对应的定时器时长大于eMBB业务的资源池对应的定时器时长。
  72. 根据权利要求61-71中任一项所述的装置，其特征在于，所述第一传输机会的资源为配置授权小数据传输CG-SDT资源。
  73. 一种无线通信的装置，其特征在于，包括存储器、处理器和通信接口，所述存储器用于存储程序，所述处理器用于调用所述存储器中的程序，使得所述终端设备执行如权利要求1-36中任一项所述的方法。
  74. 一种装置，其特征在于，包括处理器，用于从存储器中调用程序，以执行如权利要求1-36中任一项所述的方法。
  75. 一种芯片，其特征在于，包括处理器，用于从存储器调用程序，使得安装有所述芯片的设备执行如权利要求1-36中任一项所述的方法。
  76. 一种计算机可读存储介质，其特征在于，其上存储有程序，所述程序使得计算机执行如权利要求1-36中任一项所述的方法。
  77. 一种计算机程序产品，其特征在于，包括程序，所述程序使得计算机执行如权利要求1-36中任一项所述的方法。
  78. 一种计算机程序，其特征在于，所述计算机程序使得计算机执行如权利要求1-36中任一项所述的方法。
PCT/CN2022/096908 2022-06-02 2022-06-02 无线通信的方法及装置 Ceased WO2023231005A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/CN2022/096908 WO2023231005A1 (zh) 2022-06-02 2022-06-02 无线通信的方法及装置
EP22944334.6A EP4535893A4 (en) 2022-06-02 2022-06-02 METHOD AND APPARATUS FOR WIRELESS COMMUNICATION
CN202280002813.7A CN115316024B (zh) 2022-06-02 2022-06-02 无线通信的方法及装置
US18/955,867 US20250089102A1 (en) 2022-06-02 2024-11-21 Method and apparatus for wireless communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/096908 WO2023231005A1 (zh) 2022-06-02 2022-06-02 无线通信的方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/955,867 Continuation US20250089102A1 (en) 2022-06-02 2024-11-21 Method and apparatus for wireless communication

Publications (1)

Publication Number Publication Date
WO2023231005A1 true WO2023231005A1 (zh) 2023-12-07

Family

ID=83867642

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/096908 Ceased WO2023231005A1 (zh) 2022-06-02 2022-06-02 无线通信的方法及装置

Country Status (4)

Country Link
US (1) US20250089102A1 (zh)
EP (1) EP4535893A4 (zh)
CN (1) CN115316024B (zh)
WO (1) WO2023231005A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118843192A (zh) * 2023-04-23 2024-10-25 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置
CN117796121B (zh) * 2023-11-02 2025-10-10 北京小米移动软件有限公司 信令有效性和信令指示方式的确定方法、装置及存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110536472A (zh) * 2019-08-08 2019-12-03 中兴通讯股份有限公司 一种数据传输方法、装置及计算机可读存储介质
WO2021139620A1 (zh) * 2020-01-06 2021-07-15 夏普株式会社 由用户设备执行的方法及用户设备
WO2021164928A1 (en) * 2020-02-21 2021-08-26 Panasonic Intellectual Property Corporation Of America Communication apparatus and network node for small data transmission during random access applying a transport block size restriction
US20210307073A1 (en) * 2020-03-31 2021-09-30 Asustek Computer Inc. Method and apparatus for random access preamble partition for small data transmission in a wireless communication system
CN113518453A (zh) * 2020-04-10 2021-10-19 夏普株式会社 数据传输方法以及用户设备
CN114071479A (zh) * 2020-08-06 2022-02-18 维沃移动通信有限公司 数据传输类型的设定方法和终端

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11483810B2 (en) * 2017-04-03 2022-10-25 Huawei Technologies Co., Ltd. Methods and systems for resource configuration of wireless communication systems
GB2561918A (en) * 2017-04-28 2018-10-31 Canon Kk Multi-user random access in a wireless network
PL3905831T3 (pl) * 2019-01-04 2023-05-22 Beijing Xiaomi Mobile Software Co., Ltd. Dwuetapowa procedura dostępu swobodnego w pasmach nielicencjonowanych
EP3911102B1 (en) * 2019-01-16 2024-08-07 Beijing Xiaomi Mobile Software Co., Ltd. Method and apparatus regarding random access
CN111757403B (zh) * 2019-03-29 2022-09-02 华为技术有限公司 一种资源配置方法及通信装置
CN113938905B (zh) * 2020-06-29 2024-06-28 华为技术有限公司 数据传输方法及装置
WO2022041002A1 (zh) * 2020-08-26 2022-03-03 Oppo广东移动通信有限公司 传输方法和终端设备

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110536472A (zh) * 2019-08-08 2019-12-03 中兴通讯股份有限公司 一种数据传输方法、装置及计算机可读存储介质
WO2021139620A1 (zh) * 2020-01-06 2021-07-15 夏普株式会社 由用户设备执行的方法及用户设备
WO2021164928A1 (en) * 2020-02-21 2021-08-26 Panasonic Intellectual Property Corporation Of America Communication apparatus and network node for small data transmission during random access applying a transport block size restriction
US20210307073A1 (en) * 2020-03-31 2021-09-30 Asustek Computer Inc. Method and apparatus for random access preamble partition for small data transmission in a wireless communication system
CN113518453A (zh) * 2020-04-10 2021-10-19 夏普株式会社 数据传输方法以及用户设备
CN114071479A (zh) * 2020-08-06 2022-02-18 维沃移动通信有限公司 数据传输类型的设定方法和终端

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
See also references of EP4535893A4 *
SPREADTRUM COMMUNICATIONS: "Discussion on physical layer aspects of small data transmission", 3GPP TSG RAN WG1 #106BIS-E R1-2108894, 1 October 2021 (2021-10-01), XP052057906 *
XIAOMI: "Discussion on physical layer aspects of small data transmission", 3GPP TSG RAN WG1 #107-E R1-2111539, 6 November 2021 (2021-11-06), XP052074954 *

Also Published As

Publication number Publication date
EP4535893A1 (en) 2025-04-09
CN115316024B (zh) 2025-02-18
EP4535893A4 (en) 2025-06-25
US20250089102A1 (en) 2025-03-13
CN115316024A (zh) 2022-11-08

Similar Documents

Publication Publication Date Title
US11997720B2 (en) Radio terminal, radio access network node, and method therefor
US12402167B2 (en) Communication method and system, and device
JP7655401B2 (ja) ユーザ装置およびユーザ装置の方法
WO2022152003A1 (zh) 非激活态下数据传输方法及装置
CN108462998A (zh) 用于随机接入的基站、用户设备和方法
US20250089102A1 (en) Method and apparatus for wireless communication
CN115299080B (zh) 无线通信的方法和通信装置
WO2023004619A1 (zh) 信息传输方法、设备及存储介质
TW201836334A (zh) 系統訊息的獲取方法、裝置及系統
WO2020221279A1 (zh) 随机接入方法和装置
WO2022067614A1 (zh) 无线通信方法、终端设备和网络设备
WO2022116093A1 (zh) 无线通信方法和设备
CN115316002B (zh) 无线通信的方法及装置
CN116471657A (zh) 无线通信方法、终端设备和网络设备
US20230077110A1 (en) Communication Method, Apparatus, and System
WO2024032800A1 (zh) 数据传输方法、装置、设备、存储介质及程序产品
WO2024026849A1 (zh) 无线通信的方法及装置
WO2023108416A1 (zh) 无线通信的方法、终端设备及网络设备
CN115316025B (zh) 无线通信的方法及装置
WO2021062837A1 (zh) 通信方法及装置
WO2024093246A1 (en) Terminal device, network device and methods for communications
WO2024148452A1 (zh) 无线通信方法及终端设备
WO2024046236A1 (zh) 一种数据传输方法及装置
WO2025199875A1 (zh) 无线通信的方法、终端设备及网络设备
WO2025175638A1 (zh) 无线通信方法和通信设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22944334

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022944334

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2022944334

Country of ref document: EP

Effective date: 20250102

WWG Wipo information: grant in national office

Ref document number: 202280002813.7

Country of ref document: CN

WWP Wipo information: published in national office

Ref document number: 2022944334

Country of ref document: EP