WO2022183406A1 - 传输数据信道的方法、终端设备和网络设备 - Google Patents

传输数据信道的方法、终端设备和网络设备 Download PDF

Info

Publication number
WO2022183406A1
WO2022183406A1 PCT/CN2021/078883 CN2021078883W WO2022183406A1 WO 2022183406 A1 WO2022183406 A1 WO 2022183406A1 CN 2021078883 W CN2021078883 W CN 2021078883W WO 2022183406 A1 WO2022183406 A1 WO 2022183406A1
Authority
WO
WIPO (PCT)
Prior art keywords
pusch
resource allocation
information
domain resource
repeated transmission
Prior art date
Application number
PCT/CN2021/078883
Other languages
English (en)
French (fr)
Inventor
贺传峰
徐伟杰
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to CN202180080880.6A priority Critical patent/CN116569642A/zh
Priority to EP21928495.7A priority patent/EP4271108A4/en
Priority to PCT/CN2021/078883 priority patent/WO2022183406A1/zh
Publication of WO2022183406A1 publication Critical patent/WO2022183406A1/zh
Priority to US18/361,765 priority patent/US20240023095A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1864—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1887—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1893—Physical mapping arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0002—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission rate
    • H04L1/0003—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission rate by switching between different modulation schemes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0009—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the channel coding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H04L1/1819—Hybrid protocols; Hybrid automatic repeat request [HARQ] with retransmission of additional or different redundancy
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • 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

Definitions

  • the embodiments of the present application relate to the field of communications, and in particular, to a method, terminal device, and network device for transmitting a data channel.
  • NR New Radio
  • URLLC ultra-reliable and low latency communication
  • a four-step random access process is supported, which specifically includes the sending process of message 1 (Msg1)-message 4 (Msg4).
  • the message 3 (Msg3) is carried through the Physical Uplink Shared Channel (PUSCH), and how to realize the repeated transmission of the PUSCH carrying the Msg3 to improve the transmission reliability of the Msg3 is an urgent problem to be solved.
  • PUSCH Physical Uplink Shared Channel
  • the present application provides a method, terminal device and network device for transmitting a data channel, which can realize repeated transmission of the PUSCH carrying the Msg3, thereby improving the transmission reliability of the Msg3.
  • a method for transmitting a data channel comprising: a terminal device determining information on the number of repeated transmissions of a PUSCH according to a physical uplink shared channel PUSCH common configuration information or a time domain resource allocation list, where the PUSCH is used to carry The third message in the random access procedure.
  • a method for transmitting a data channel including: .
  • a terminal device for executing the method in the above-mentioned first aspect or each implementation manner thereof.
  • the terminal device includes a functional module for executing the method in the above-mentioned first aspect or each implementation manner thereof.
  • a network device for executing the method in the second aspect or each of its implementations.
  • the network device includes functional modules for executing the methods in the second aspect or the respective implementation manners thereof.
  • a terminal device including a processor and a memory.
  • the memory is used for storing a computer program
  • the processor is used for calling and running the computer program stored in the memory to execute the method in the above-mentioned first aspect or each implementation manner thereof.
  • a network device including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the method in the second aspect or each of its implementations.
  • a chip is provided for implementing any one of the above-mentioned first aspect to the second aspect or the method in each implementation manner thereof.
  • the chip includes: a processor for invoking and running a computer program from a memory, so that a device in which the device is installed executes any one of the above-mentioned first to second aspects or each of its implementations method.
  • a computer-readable storage medium for storing a computer program, the computer program causing a computer to execute the method in any one of the above-mentioned first aspect to the second aspect or each of its implementations.
  • a computer program product comprising computer program instructions, the computer program instructions causing a computer to execute the method in any one of the above-mentioned first to second aspects or the implementations thereof.
  • a computer program which, when run on a computer, causes the computer to perform the method in any one of the above-mentioned first to second aspects or the respective implementations thereof.
  • the terminal device can determine the number of repeated transmissions of the PUSCH carrying the Msg3 according to the PUSCH public configuration information or the time domain resource allocation list, so as to realize the repeated transmission of the PUSCH carrying the Msg3, thereby improving the transmission reliability of the Msg3 .
  • FIG. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application.
  • Figure 2 is a schematic diagram of a four-step random access procedure.
  • FIG. 3 is a schematic interaction diagram of a method for transmitting a data channel according to an embodiment of the present application.
  • FIG. 4 is a schematic block diagram of a terminal device provided according to an embodiment of the present application.
  • FIG. 5 is a schematic block diagram of a network device provided according to an embodiment of the present application.
  • FIG. 6 is a schematic block diagram of a communication device provided according to an embodiment of the present application.
  • FIG. 7 is a schematic block diagram of a chip provided according to an embodiment of the present application.
  • FIG. 8 is a schematic block diagram of a communication system provided according to an embodiment of the present application.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • CDMA Wideband Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • LTE-A Advanced Long Term Evolution
  • NR New Radio
  • NTN Non-Terrestrial Networks
  • UMTS Universal Mobile Telecommunication System
  • WLAN Wireless Local Area Networks
  • Wireless Fidelity Wireless Fidelity
  • WiFi fifth-generation communication
  • D2D Device to Device
  • M2M Machine to Machine
  • MTC Machine Type Communication
  • V2V Vehicle to Vehicle
  • V2X Vehicle to everything
  • the communication system in this embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, or a standalone (Standalone, SA) distribution. web scene.
  • Carrier Aggregation, CA Carrier Aggregation, CA
  • DC Dual Connectivity
  • SA standalone
  • the communication system in the embodiment of the present application may be applied to an unlicensed spectrum, where the unlicensed spectrum may also be considered as a shared spectrum; or, the communication system in the embodiment of the present application may also be applied to a licensed spectrum, where, Licensed spectrum can also be considered unshared spectrum.
  • the embodiments of the present application describe various embodiments in conjunction with network equipment and terminal equipment, where the terminal equipment may also be referred to as user equipment (User Equipment, UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
  • user equipment User Equipment, UE
  • access terminal subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
  • the terminal device may be a station (STATION, ST) in the WLAN, and may be a cellular phone, a cordless phone, a Session Initiation Protocol (Session Initiation Protocol, SIP) phone, a Wireless Local Loop (WLL) station, a personal digital assistant (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, next-generation communication systems such as end devices in NR networks, or future Terminal equipment in the evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.
  • PLMN Public Land Mobile Network
  • the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable, or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites) superior).
  • the terminal device may be a mobile phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (Virtual Reality, VR) terminal device, and an augmented reality (Augmented Reality, AR) terminal Equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city or wireless terminal equipment in smart home, etc.
  • a mobile phone Mobile Phone
  • a tablet computer Pad
  • a computer with a wireless transceiver function a virtual reality (Virtual Reality, VR) terminal device
  • augmented reality (Augmented Reality, AR) terminal Equipment wireless terminal equipment in industrial control, wireless terminal equipment in self driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city or wireless terminal equipment in smart home, etc.
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices, which are the general term for the intelligent design of daily wear and the development of wearable devices using wearable technology, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-scale, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, which needs to cooperate with other devices such as smart phones.
  • the network device may be a device for communicating with a mobile device, and the network device may be an access point (Access Point, AP) in WLAN, or a base station (Base Transceiver Station, BTS) in GSM or CDMA , it can also be a base station (NodeB, NB) in WCDMA, it can also be an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or in-vehicle equipment, wearable devices and NR networks
  • the network device may have a mobile feature, for example, the network device may be a mobile device.
  • the network device may be a satellite or a balloon station.
  • the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a High Elliptical Orbit (HEO) ) satellite etc.
  • the network device may also be a base station set in a location such as land or water.
  • a network device may provide services for a cell, and a terminal device communicates with the network device through transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell, and the cell may be a network device (
  • the cell can belong to the macro base station, or it can belong to the base station corresponding to the small cell (Small cell).
  • Pico cell Femto cell (Femto cell), etc.
  • These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.
  • the communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, a terminal).
  • the network device 110 may provide communication coverage for a particular geographic area, and may communicate with terminal devices located within the coverage area.
  • FIG. 1 exemplarily shows one network device and two terminal devices.
  • the communication system 100 may include multiple network devices and the coverage of each network device may include other numbers of terminal devices. This application The embodiment does not limit this.
  • the communication system 100 may further 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.
  • a device having a communication function in the network/system may be referred to as a communication device.
  • the communication device may include a network device 110 and a terminal device 120 with a communication function, and the network device 110 and the terminal device 120 may be the specific devices described above, which will not be repeated here.
  • the communication device may also include other devices in the communication system 100, such as other network entities such as a network controller, a mobility management entity, etc., which are not limited in this embodiment of the present application.
  • the "instruction" mentioned in the embodiments of the present application may be a direct instruction, an indirect instruction, or an associated relationship.
  • a indicates B it can indicate that A directly indicates B, for example, B can be obtained through A; it can also indicate that A indicates B indirectly, such as A indicates C, and B can be obtained through C; it can also indicate that there is an association between A and B relation.
  • corresponding may indicate that there is a direct or indirect corresponding relationship between the two, or may indicate that there is an associated relationship between the two, or indicate and be instructed, configure and be instructed configuration, etc.
  • predefinition may be implemented by pre-saving corresponding codes, forms, or other means that can be used to indicate relevant information in devices (for example, including terminal devices and network devices).
  • the implementation method is not limited.
  • predefined may refer to the definition in the protocol.
  • the "protocol” may refer to a standard protocol in the communication field, for example, may include the LTE protocol, the NR protocol, and related protocols applied in future communication systems, which are not limited in this application.
  • the network device sends an uplink grant (UL grant), the UL grant is carried in the downlink control information (Downlink Control Information, DCI), the DCI is DCI (format) format 0_0, or DCI format 0_1, scheduling physical uplink Shared channel (Physical Uplink Shared Channel, PUSCH) transmission.
  • DCI Downlink Control Information
  • the network device When the network device schedules uplink data transmission through the DCI carrying the UL grant, it will carry a Time Domain Resource Allocation (TDRA) field in the DCI.
  • the TDRA field is 4 bits and can indicate 16 different time domain resource allocation tables. Each row contains different resource allocation combinations, such as the starting position S of the PUSCH, the length L, k2, and different mapping types (types). Wherein, k2 represents the number of slots offset between the time slot (slot) where the DCI is located and the slot where the PUSCH is located.
  • the types of time domain resource allocation for PUSCH include Type A (Type A) and Type B (Type B). The difference between Type A and Type B is that the corresponding S and L candidate values have different value ranges.
  • Type A is mainly for slot-based services, S is relatively high, and L is relatively long.
  • Type B is mainly for Ultra-Reliable and Low Latency Communication (URLLC) services, and has higher requirements for latency, so the location of S is more flexible to transmit URLLC services that can arrive at any time. Reduce transmission delay.
  • URLLC Ultra-Reliable and Low Latency Communication
  • the DCI carrying the UL grant also includes frequency domain resource information, modulation and coding scheme (Modulation and Coding Scheme, MCS), power control command (Transmission Power Control, TPC), frequency hopping information, The redundant version, Hybrid Automatic Repeat reQuest (HARQ) process number, etc., will not be repeated here.
  • MCS Modulation and Coding Scheme
  • TPC Transmission Power Control
  • HARQ Hybrid Automatic Repeat reQuest
  • a four-step random access process is supported, which specifically includes the sending process of message 1 (Msg1)-message 4 (Msg4).
  • the four-step random access procedure includes the following steps:
  • Step 1 the terminal device sends a random access preamble (Preamble, namely Msg 1) to the network device.
  • Preamble namely Msg 1
  • the random access preamble may also be referred to as a preamble, a random access preamble sequence, a preamble sequence, or the like.
  • the terminal device may select physical random access channel (Physical Random Access Channel, PRACH) resources, and the PRACH resources may include time domain resources, frequency domain resources and code domain resources.
  • the network device sends random access related parameters to the terminal device by broadcasting a System Information Block (SIB) 1, wherein the random access common configuration information element (RACH-ConfigCommon IE) is for the synchronization signal block (Synchronization Signal Block, The Reference Signal Receiving Power (RSRP) threshold value (rsrp-ThresholdSSB) of the SSB) is used for the terminal device to select the SSB.
  • SIB System Information Block
  • RACH-ConfigCommon IE random access common configuration information element
  • RSRP Reference Signal Receiving Power
  • the terminal device compares the RSRP measurement result under each SSB with the rsrp-ThresholdSSB, and selects The SSB whose measured value is higher than the configured threshold value is used for access, and if there is no SSB that meets the configured threshold value, one is randomly selected from all SSBs for access.
  • Each SSB corresponds to a set of random access preamble (Preamble) resources and random access opportunity (RACH Occasion, RO) resources, and the terminal device randomly selects from the contention-based random access resources in the selected SSB, Set the Preamble index (PREAMBLE_INDEX) to the selected random access preamble.
  • Preamble random access preamble
  • RACH Occasion, RO random access opportunity
  • the network device can estimate the transmission delay between it and the terminal device according to the Preamble, and calibrate the uplink timing accordingly, and can roughly determine the resource size required by the terminal device to transmit Msg 3.
  • the Preamble is divided into Preamble group (group) A and Preamble group B. If there is Preamble group B in the random access resource, The terminal device can select the Preamble group according to the size of Msg 3 and pathloss.
  • Step 2 the network device sends a random access response (Random Access Response, RAR, namely Msg 2) to the terminal device
  • the terminal device After the terminal device sends the Preamble to the network device, it can open a random access response window (ra-ResponseWindow), and in the ra-ResponseWindow, detect according to the random access wireless network temporary identifier (Random Access Radio Network Temporary Identifier, RA-RNTI). Corresponding physical downlink control channel (Physical Downlink Control Channel, PDCCH). If the terminal device detects the PDCCH scrambled by the RA-RNTI, it can obtain the Physical Downlink Shared Channel (PDSCH) scheduled by the PDCCH. Wherein, the PDSCH includes the RAR corresponding to the Preamble.
  • ra-ResponseWindow a random access response window
  • RA-RNTI Random Access Radio Network Temporary Identifier
  • PDCCH Physical Downlink Control Channel
  • the terminal device detects the PDCCH scrambled by the RA-RNTI, it can obtain the Physical Downlink Shared Channel (PDSCH) scheduled by
  • the RA-RNTI is calculated according to the time-frequency position of the PRACH that sends the Preamble. Therefore, if multiple terminal devices send the Preamble on the same RO, the corresponding RARs are multiplexed in the same RAR media access control protocol data unit (Media Access Control Protocol). Protocol Data Unit, MAC PDU).
  • Media Access Control Protocol Media Access Control Protocol
  • Protocol Data Unit MAC PDU
  • the terminal successfully receives the PDCCH scrambled by the RA-RNTI corresponding to the RO resource sending the Preamble, and the RAR contains a random access sequence identifier (Random Access Preamble Identifier, RAPID) carried by a MAC sub-PDU (subPDU) and the above
  • RAPID Random Access Preamble Identifier
  • the RAR reception is successful, and the terminal can decode to obtain the Timing Advance Command (TAC), the uplink grant resource (UL Grant) and the Temporary Cell Radio Network Temporary Identity, TC- RNTI), Msg 3 was performed.
  • TAC Timing Advance Command
  • UL Grant uplink grant resource
  • TC- RNTI Temporary Cell Radio Network Temporary Identity
  • the terminal device needs to retransmit Msg 1. If the transmission times of Preamble exceeds the network configuration The maximum number of transmissions (preambleTransMax), the terminal device reports the random access problem to the upper layer.
  • Step 3 the terminal device sends Msg 3.
  • the terminal device After receiving the RAR message, the terminal device determines whether the RAR belongs to its own RAR message. For example, the terminal device can use the preamble index to check, and after determining that it belongs to its own RAR message, it can generate Msg 3 at the RRC layer, and Send Msg 3 to the network device, which needs to carry the identification information of the terminal device, etc.
  • Msg 3 is mainly used to notify the network device of the trigger event of the random access.
  • the Msg 3 sent by the terminal device in step 3 may include different contents.
  • Msg 3 may include an RRC connection request message (RRC Setup Request) generated by the RRC layer.
  • RRC Setup Request RRC connection request message
  • Msg 3 may also carry, for example, a 5G-serving temporary mobile subscriber identity (Serving-Temporary Mobile Subscriber Identity, S-TMSI) or a random number of the terminal device.
  • S-TMSI Serving-Temporary Mobile Subscriber Identity
  • Msg 3 may include an RRC connection reestablishment request message (RRC Reestabilshment Request) generated by the RRC layer.
  • RRC Reestabilshment Request RRC connection reestablishment request message
  • the Msg 3 may also carry, for example, a Cell Radio Network Temporary Identifier (C-RNTI) and the like.
  • C-RNTI Cell Radio Network Temporary Identifier
  • Msg 3 may include an RRC handover confirmation message (RRC Handover Confirm) generated by the RRC layer, which carries the C-RNTI of the terminal device.
  • RRC Handover Confirm RRC handover confirmation message
  • Msg 3 may also carry information such as a buffer status report (Buffer Status Report, BSR).
  • BSR Buffer Status Report
  • Msg 3 may include at least the C-RNTI of the terminal device.
  • Step 4 the network device sends a conflict resolution message (contention resolution), namely Msg 4, to the terminal device.
  • a conflict resolution message contention resolution
  • the network device sends Msg 4 to the terminal device, and the terminal device correctly receives the Msg 4 to complete the contention resolution (Contention Resolution).
  • the Msg 4 may carry the RRC connection establishment message.
  • the message 3 (Msg3) is carried by the Physical Uplink Shared Channel (PUSCH)
  • the RAR in the Msg2 carries the UL grant of the PUSCH used for the initial transmission of the Msg3
  • the UL grant carried in the RAR is called the RAR UL grant .
  • the information carried by the RAR UL grant information may include time domain and frequency domain resource allocation information of PUSCH, power control command TPC, frequency hopping, and MCS, etc.
  • the network device If the network device does not receive the Msg3 correctly, it will indicate the retransmission scheduling information of the Msg3 through the DCI, such as the DCI format 0_0 bearer scrambled by the Temporary Cell Radio Network Temporary Identity (TC-RNTI), In addition to the content contained in the RAR UL grant, it also includes New Data Indicator (NDI), redundancy version, and HARQ process number.
  • DCI such as the DCI format 0_0 bearer scrambled by the Temporary Cell Radio Network Temporary Identity (TC-RNTI)
  • TC-RNTI Temporary Cell Radio Network Temporary Identity
  • NDI New Data Indicator
  • redundancy version HARQ process number
  • the repeated transmission of uplink data is used to improve the transmission reliability. Therefore, how to realize the repeated transmission of the PUSCH carrying Msg3 to Improving the transmission reliability of Msg3 is an urgent problem to be solved.
  • FIG. 3 is a schematic interaction diagram of a method 300 for transmitting a data channel according to an embodiment of the present application. As shown in FIG. 3 , the method 300 includes at least some of the following contents:
  • the terminal device determines the repeated transmission times information of the PUSCH according to the public configuration information of the physical uplink shared channel PUSCH or the time domain resource allocation list, wherein the PUSCH is used to carry the third message in the random access process (ie Msg3) .
  • the PUSCH used to carry the Msg3 may also be referred to as the Msg3 PUSCH.
  • the method 300 may further include:
  • the terminal device receives the PUSCH common configuration information (pusch-ConfigCommon) sent by the network device.
  • the PUSCH common configuration information is used to carry the repeated transmission times information of the PUSCH.
  • the PUSCH public configuration information is sent through a system message.
  • the repeated transmission times information of the Msg3 PUSCH may include the repeated transmission times information for the initial transmission of the Msg3 PUSCH, and/or the repeated transmission times information for the retransmission of the Msg3 PUSCH.
  • the repeated transmission times information for the initial transmission of the Msg3 PUSCH and the repeated transmission times information for the retransmission of the Msg3 PUSCH may be the same, or may also be different.
  • the PUSCH common configuration information includes a first repeated transmission times information group, and the first repeated transmission times information group may include at least one repeated transmission times information for Msg3 PUSCH transmission.
  • the first repeated transmission times information group can be used for initial transmission and retransmission of Msg3 PUSCH.
  • the network device may indicate to the terminal device the target repeated transmission times information in the first repeated transmission times information group, for example
  • the target repeated transmission times information is indicated in a bitmap manner, and the specific indication manner is described in detail below.
  • the PUSCH common configuration information includes a second repeated transmission times information group and a third repeated transmission times information group, where the second repeated transmission times group includes at least one repeated transmission times information for the initial transmission of the Msg3 PUSCH , the third repeated transmission times information group includes at least one repeated transmission times information for Msg3 PUSCH retransmission.
  • the network device may indicate to the terminal device the target repeated transmission times in the second repeated transmission times group.
  • the number of times information indicates the repeat transmission times information of the target by means of a bitmap, and the specific indication method is described in detail below.
  • the network device may indicate to the terminal device the target repeated transmission in the third repeated transmission times group.
  • the number of times information indicates the repeat transmission times information of the target by means of a bitmap, and the specific indication method is described in detail below.
  • the embodiments of the present application are also applicable to determining the number of repeated transmissions of the PUSCH used to carry other messages.
  • the number of repeated transmissions of the PUSCH used to carry the MsgA, where the MsgA is the first message of the two-step contention-based random access in this case, the PUSCH may be called the MsgA PUSCH, and the repeated transmission of the MsgA PUSCH
  • the number of times information can be configured through the MsgA public configuration information.
  • the specific configuration method refer to the related implementation of configuring the repeated transmission times information of the Msg3 PUSCH through the PUSCH public configuration information.
  • the PUSCH common configuration information includes a PUSCH time domain resource allocation list information element (Information Element, IE), and the Msg3 PUSCH repeated transmission times information is included in the PUSCH time domain resource allocation list IE.
  • Information Element Information Element
  • the PUSCH time-domain resource allocation list IE includes multiple time-domain resource allocation configurations, and each time-domain resource allocation configuration includes a set of time-domain resource allocation information and repeat transmission times information of the PUSCH.
  • each group of time domain resource allocation information may include at least one of the following information:
  • k2 the mapping type, start symbol, and length of the PUSCH, where k2 represents the number of offset slots between the time slot (slot) where the signaling for scheduling the PUSCH is located and the slot where the PUSCH is located.
  • each time-domain resource allocation configuration includes information on the number of repeated transmissions, and the set of information on the number of repeated transmissions is used for initial transmission and retransmission of the PUSCH.
  • each time-domain resource allocation configuration includes two pieces of information on the number of repeated transmissions, and the two pieces of information on the number of repeated transmissions are respectively used for initial transmission and retransmission of the PUSCH.
  • the PUSCH Time Domain Resource Allocation List IE may reuse an existing IE, eg, PUSCH-TimeDomainResourceAllocationList-r16, or may also be a newly defined IE, eg, PUSCH-TimeDomainResourceAllocationList-r17.
  • the PUSCH-TimeDomainResourceAllocationList-r16 may include information such as k2, the mapping type of the PUSCH, the start symbol, the length, and the number of repeated transmissions.
  • PUSCH-TimeDomainResourceAllocationList-r16 is defined as follows:
  • mappingType-r16 ENUMERATED ⁇ typeA,typeB ⁇ OPTIONAL,--Cond NotFormat01-02-Or-TypeA
  • numberOfRepetitions-r16 is used to indicate the number of repeated transmissions K of the PUSCH
  • startSymbolAndLength is used to indicate the start symbol S and length L of the PUSCH.
  • the terminal device determines the time domain resource for PUSCH retransmission according to the above information and the PUSCH repetition Type determined through high-layer signaling.
  • the terminal device For example, for PUSCH repetition Type A, the terminal device repeatedly transmits the same transport block in consecutive K slots.
  • the allocation of symbols in each slot is the same, that is, the allocation of symbols in the slot indicated by startSymbolAndLength.
  • n 0,...,numberOfRepetitions-1:
  • K s is the time slot where the starting position of PUSCH repeated transmission is located, The number of symbols contained in each slot.
  • K transmissions of PUSCH start at symbol S of time slot K s and are transmitted over consecutive K*L symbols, each transmission containing L symbols.
  • the PUSCH-TimeDomainResourceAllocationList-r17 may also include the information exemplified in PUSCH-TimeDomainResourceAllocationList-r16.
  • the method 300 further includes:
  • the terminal device receives the uplink grant sent by the network device.
  • the uplink grant is an uplink grant in the random access response RAR, and the uplink grant is used to schedule retransmission of the PUSCH.
  • the uplink grant is an uplink grant in the downlink control information DCI, and the DCI is used to schedule retransmission of the PUSCH.
  • S310 may include:
  • the terminal device determines, according to the PUSCH public configuration information and the uplink grant sent by the network device, information on the number of times of repeated transmission of the PUSCH.
  • the uplink grant includes first indication information, where the first indication information is used to indicate the target repeated transmission times information in the PUSCH common configuration information.
  • the network device may indicate the information of the number of times of repeated transmissions in the multiple times of repetition information through the first indication information, for example, by using bits Graphical instructions.
  • the network device may indicate the multiple time-domain resource allocation configurations through the first indication information.
  • the target time-domain resource allocation configuration in the resource allocation configuration is indicated by, for example, a bitmap.
  • the time-domain resource allocation information and the information on the number of times of repeated transmission of the PUSCH may be associated.
  • the time domain resource allocation information and the number of times of repeated transmission of the associated PUSCH are a time domain resource allocation configuration, corresponding to a time domain resource allocation configuration index.
  • an indication information (for example, a time domain resource allocation configuration index can be used ) indicates target time domain resource allocation information for PUSCH transmission and information on the number of repeated transmissions.
  • the time-domain resource allocation information and the PUSCH repeated transmission times information are independent.
  • the time-domain resource allocation information for Msg3 PUSCH transmission and Msg3 Repeat transmission times information of PUSCH transmission are independent.
  • the PUSCH common configuration information may include the first repeated transmission times information group. If the number of repeated transmission times included in the first repeated transmission times information group is multiple, the first indication information may include A first bit map, where the first bit map can be used to indicate the target repeated transmission times information in the first repeated transmission times information group.
  • the PUSCH public configuration information includes the second repeated transmission times information group. If the second repeated transmission times information group includes a plurality of repeated transmission times, in the PUSCH initial transmission scenario,
  • the first indication information may include a second bitmap, and the second bitmap may be used to indicate the target repeated transmission times information in the second repeated transmission times information group.
  • the PUSCH common configuration information includes a third repeated transmission times information group, if the third repeated transmission times information group includes a plurality of repeated transmission times, in the PUSCH retransmission scenario,
  • the first indication information may include a third bitmap, and the third bitmap may be used to indicate the target repeated transmission times information in the third repeated transmission times information group.
  • the IE of the PUSCH common configuration information includes information on the number of times of repeated transmission of the PUSCH.
  • the repeated transmission times information of the PUSCH may be the repeated transmission times information for all terminal devices in the cell, that is, the repeated transmission times information of the PUSCH is the repeated transmission times information of the Msg3 PUSCH at the cell level.
  • an IE may be added in pusch-ConfigCommon to indicate the number of times of repeated transmission of the Msg3 PUSCH at the cell level.
  • the PUSCH-ConfigCommon information element format is as follows:
  • the Msg3-numberOfRepetitions-r17 may be used to indicate the number of repeated transmissions of the Msg3 PUSCH at the cell level.
  • the repeated transmission times information of the Msg3 PUSCH at the cell level may include a fourth repeated transmission times information group, and the fourth repeated transmission times information group may include at least one repeated transmission times information for Msg3 PUSCH transmission.
  • the fourth group of repeated transmission times can be used for initial transmission and retransmission of the Msg3 PUSCH.
  • the network device may indicate the target repeated transmission times information in the fourth repeated transmission times group to the terminal device.
  • the network device may send an uplink grant to the terminal device, where the uplink grant includes third indication information, where the third indication information is used to indicate the target repeated transmission times information in the fourth repeated transmission times group.
  • the number of times of repeated transmission information of the Msg3 PUSCH at the cell level may include a fifth information group of times of repeated transmission and a sixth information group of times of repeated transmission, where the fifth group of times of repeated transmission includes the information for the initial transmission of the Msg3 PUSCH. At least one repeated transmission times information, the sixth repeated transmission times information group includes at least one repeated transmission times information for Msg3 PUSCH retransmission.
  • the repeated transmission times information for the initial transmission of the Msg3 PUSCH and the repeated transmission times information for the retransmission of the Msg3 PUSCH may be the same, or may also be different.
  • the network device may indicate to the terminal device the target repeated transmission times information in the fifth repeated transmission times group.
  • the network device may send an uplink grant to the terminal device, where the uplink grant includes fourth indication information, and the fourth indication information is used to indicate the target repeated transmission in the fifth repeated transmission times group times information.
  • the network device may indicate to the terminal device the target repeated transmission times information in the sixth repeated transmission times group.
  • the network device may send an uplink grant to the terminal device, where the uplink grant includes fifth indication information, and the fifth indication information is used to indicate the target repeated transmission in the sixth repeated transmission times group times information.
  • the terminal device may determine the repeated transmission times information of the Msg3 PUSCH according to the time domain resource allocation list. For example, when the PUSCH common configuration information does not include the PUSCH time-domain resource allocation list IE, the terminal device may determine the information on the number of times of repeated transmission of the Msg3 PUSCH according to the time-domain resource allocation list.
  • the time domain resource allocation list is a default (default) PUSCH time domain resource allocation list (time domain resource allocation), and the default PUSCH time domain resource allocation list (default PUSCH time domain resource allocation) allocation) includes a plurality of time-domain resource allocation configurations, and each time-domain resource allocation configuration includes a set of time-domain resource allocation information and repeat transmission times information of the PUSCH.
  • each group of time domain resource allocation information may include at least one of the following information:
  • k2 the mapping type, start symbol, and length of the PUSCH, where k2 represents the number of offset slots between the time slot (slot) where the signaling for scheduling the PUSCH is located and the slot where the PUSCH is located.
  • each time-domain resource allocation configuration includes information on the number of times of repeated transmission, and the information on the number of times of repeated transmission is used for initial transmission and retransmission of the Msg3 PUSCH.
  • each time-domain resource allocation configuration includes two pieces of repeated transmission times information, and the two pieces of repeated transmission times information are respectively used for initial transmission and retransmission of the Msg3 PUSCH.
  • the number of times of repeated transmission of the PUSCH corresponding to each time-domain resource allocation configuration is predefined or configured by a network device.
  • the number of times of repeated transmission of the PUSCH included in each time-domain resource allocation configuration is configured through radio resource control RRC signaling or a system message. For example, configured via pusch-ConfigCommon.
  • the time-domain resource allocation list is used for all terminal devices; or,
  • the time domain resource allocation list is a dedicated list for terminal equipment supporting repeated transmission of the PUSCH.
  • the network device may send second indication information to the terminal device, where the second indication information is used to indicate a target time-domain resource allocation configuration in the multiple time-domain resource allocation configurations.
  • the second indication information is included in the uplink grant.
  • each time-domain resource allocation configuration corresponds to a time-domain resource allocation configuration index
  • the second indication information may be used to indicate an index corresponding to the target time-domain resource allocation configuration
  • the default PUSCH time domain resource allocation is shown in Table 2.
  • each row has one time domain resource allocation configuration, and one time domain resource allocation configuration corresponds to a row number, and the second indication information may be used to indicate the row number corresponding to the target time domain resource allocation configuration.
  • the time domain resource allocation information and the PUSCH repeated transmission times information may be carried by a table.
  • the time domain resource allocation information and the PUSCH repeated transmission times information may have an associated relationship
  • the time domain resource allocation information and the number of times of repeated transmission of the associated PUSCH can be considered as a time domain resource allocation configuration, corresponding to a time domain resource allocation configuration index. ) indicates target time domain resource allocation information for PUSCH transmission and information on the number of repeated transmissions.
  • the time-domain resource allocation information and the PUSCH repeated transmission times information may be carried through corresponding tables, respectively.
  • the time-domain resource allocation information and the PUSCH repeated transmission times information may be related. , or it can be independent.
  • the time-domain resource allocation configuration corresponds to the default PUSCH time-domain resource allocation list
  • the PUSCH repeated transmission times information corresponds to the PUSCH repeated transmission times list
  • the PUSCH repeated transmission times list may include at least one repeated transmission times information.
  • the indication information indicates the target time domain resource allocation information for PUSCH transmission and the target repeated transmission times information.
  • the PUSCH repeated transmission times list may include multiple sets of PUSCH repeated transmission times configurations, and each group of PUSCH repeated transmission times configurations includes repeated transmission times information corresponding to each group of time domain resource allocation information.
  • the network device may activate a set of PUSCH repeated transmission times configurations in the multiple sets of PUSCH repeated transmission times configurations through signaling (for example, RRC signaling or DCI).
  • the network device indicates the target time domain resource allocation information in the default PUSCH time domain resource allocation list, with respect to the repeated transmission times information corresponding to the target time domain resource allocation information in the set of PUSCH repeated transmission times configuration indicating the activation as the target Repeat transmission count information.
  • the PUSCH repeated transmission times list may include M groups of PUSCH repeated transmission times configurations, and each group of PUSCH repeated transmission times configurations includes 16 PUSCH repeated transmission times information, the 16 PUSCH repeated transmission times information and the 16 rows in Table 2.
  • the time domain resource allocation information is in one-to-one correspondence, and the information on the number of times of repeated transmission of each PUSCH can be used for the initial transmission and retransmission of the PUSCH.
  • each row of time domain resource allocation information may also correspond to two PUSCH repeated transmission times information, which are respectively used for initial transmission and retransmission of the PUSCH, and the present application is not limited to this.
  • the network device may indicate the activated PUSCH repeated transmission times configuration in the M groups of PUSCH repeated transmission times configurations, for example, activate the first group of PUSCH repeated transmission times configurations.
  • the terminal device may determine the target number of repeated transmissions of the PUSCH according to the configuration of the number of repeated transmissions of the first group of PUSCHs.
  • the network device may send an uplink grant to the terminal device, and the uplink grant may include sixth indication information, which is used to indicate the target PUSCH repeated transmission times in the configuration of the first group of PUSCH repeated transmission times, for example, by means of a bitmap.
  • the sixth indication information is used to indicate the target time domain resource allocation information in the default PUSCH time domain resource allocation list, in this case, the terminal device can repeat the transmission of the target time domain resource allocation information on this group of PUSCH The corresponding repeated transmission times in the times configuration is determined as the target repeated transmission times information.
  • the terminal device can determine the number of repeated transmissions of the PUSCH used to carry Msg3 according to the PUSCH public configuration information or the time domain resource allocation list, or, more specifically, in the initial transmission scenario of the Msg3 PUSCH, determine the number of times the PUSCH is used for the Msg3 transmission.
  • Retransmission times information of the initial transmission of PUSCH in the retransmission scenario of Msg3 PUSCH, determine the repeated transmission times information for the retransmission of Msg3 PUSCH, so as to realize the repeated transmission of PUSCH carrying Msg3, thereby improving the transmission reliability of Msg3 sex.
  • FIG. 4 shows a schematic block diagram of a terminal device 400 according to an embodiment of the present application.
  • the terminal device 400 includes:
  • the processing unit 410 is configured to determine, according to the physical uplink shared channel PUSCH common configuration information or the time domain resource allocation list, information on the number of repeated transmissions of the PUSCH, where the PUSCH is used to carry the third message in the random access process.
  • the PUSCH common configuration information includes a PUSCH time-domain resource allocation list information element IE, and the PUSCH time-domain resource allocation list IE includes repeat transmission times information of the PUSCH.
  • the PUSCH time-domain resource allocation list IE includes multiple time-domain resource allocation configurations, and each time-domain resource allocation configuration includes a set of time-domain resource allocation information and repeat transmission times information of the PUSCH.
  • each time-domain resource allocation configuration includes information on the number of repeated transmissions, and the information on the number of repeated transmissions is used for initial transmission and retransmission of the PUSCH;
  • Each time-domain resource allocation configuration includes two pieces of repeated transmission times information, and the two pieces of repeated transmission times information are respectively used for initial transmission and retransmission of the PUSCH.
  • the processing unit 410 is further configured to:
  • the uplink grant includes first indication information
  • the first indication information is used to indicate the multiple The target time domain resource allocation configuration in the time domain resource allocation configuration.
  • the IE of the PUSCH common configuration information includes information on the number of times of repeated transmission of the PUSCH.
  • the IE of the PUSCH common configuration information includes a set of repeated transmission times information, and the set of repeated transmission times information is used for initial transmission and retransmission of the PUSCH;
  • the IE of the PUSCH common configuration information includes two sets of repeated transmission times information, and the two sets of repeated transmission times information are respectively used for initial transmission and retransmission of the PUSCH.
  • the time domain resource allocation list is a default PUSCH time domain resource allocation list
  • the default PUSCH time domain resource allocation list includes multiple time domain resource allocation configurations, each time domain resource allocation
  • the configuration includes a set of time-domain resource allocation information and information on the number of repeated transmissions of the PUSCH.
  • each time-domain resource allocation configuration includes information on the number of repeated transmissions, and the information on the number of repeated transmissions is used for initial transmission and retransmission of the PUSCH;
  • Each time-domain resource allocation configuration includes two pieces of repeated transmission times information, and the two pieces of repeated transmission times information are respectively used for initial transmission and retransmission of the PUSCH.
  • the number of times of repeated transmission of the PUSCH included in each time-domain resource allocation configuration is predefined or configured by a network device.
  • the number of repeated transmissions of the PUSCH included in each time-domain resource allocation configuration is configured through radio resource control RRC signaling or system messages.
  • the time-domain resource allocation list is used for all terminal devices; or,
  • the time domain resource allocation list is a dedicated list for terminal equipment supporting repeated transmission of the PUSCH.
  • the processing unit 410 is further configured to:
  • the network device determine the repeated transmission times information of the PUSCH, wherein the uplink grant includes second indication information, and the second indication information is used to indicate the multiple transmission times.
  • the uplink grant is an uplink grant in a random access response RAR, or the uplink grant is an uplink grant in downlink control information DCI, and the DCI is used to schedule retransmission of the PUSCH .
  • the above-mentioned communication unit may be a communication interface or a transceiver, or an input/output interface of a communication chip or a system-on-chip.
  • the aforementioned processing unit may be one or more processors.
  • terminal device 400 may correspond to the terminal device in the method embodiment of the present application, and the above-mentioned and other operations and/or functions of each unit in the terminal device 400 are respectively for realizing the method shown in FIG. 3 .
  • the corresponding process of the terminal device in 300 is not repeated here for brevity.
  • FIG. 5 is a schematic block diagram of a network device according to an embodiment of the present application.
  • the network device 500 of FIG. 5 includes:
  • the processing unit 510 is configured to configure the repeated transmission times information of the PUSCH for the terminal device through the physical uplink shared channel PUSCH public configuration information or the time domain resource allocation list, wherein the PUSCH is used to carry the third item in the random access process. information.
  • the PUSCH common configuration information includes a PUSCH time-domain resource allocation list information element IE, and the PUSCH time-domain resource allocation list IE includes repeat transmission times information of the PUSCH.
  • the PUSCH time-domain resource allocation list IE includes multiple time-domain resource allocation configurations, and each time-domain resource allocation configuration includes a set of time-domain resource allocation information and repeat transmission times information of the PUSCH.
  • each time-domain resource allocation configuration includes information on the number of repeated transmissions, and the information on the number of repeated transmissions is used for initial transmission and retransmission of the PUSCH;
  • Each time-domain resource allocation configuration includes two pieces of repeated transmission times information, and the two pieces of repeated transmission times information are respectively used for initial transmission and retransmission of the PUSCH.
  • the network device 500 further includes:
  • a communication unit configured to send an uplink grant to the terminal device, wherein the uplink grant includes first indication information, where the first indication information is used to indicate target time domain resources in the multiple time domain resource allocation configurations Assign configuration.
  • the IE of the PUSCH common configuration information includes information on the number of times of repeated transmission of the PUSCH.
  • the IE of the PUSCH common configuration information includes a set of repeated transmission times information, and the set of repeated transmission times information is used for initial transmission and retransmission of the PUSCH;
  • the IE of the PUSCH common configuration information includes two sets of repeated transmission times information, and the two sets of repeated transmission times information are respectively used for initial transmission and retransmission of the PUSCH.
  • the time domain resource allocation list is a default PUSCH time domain resource allocation list
  • the default PUSCH time domain resource allocation list includes multiple time domain resource allocation configurations, each time domain resource allocation
  • the configuration includes a set of time-domain resource allocation information and information on the number of repeated transmissions of the PUSCH.
  • each time-domain resource allocation configuration includes information on the number of repeated transmissions, and the information on the number of repeated transmissions is used for initial transmission and retransmission of the PUSCH;
  • Each time-domain resource allocation configuration includes two pieces of repeated transmission times information, and the two pieces of repeated transmission times information are respectively used for initial transmission and retransmission of the PUSCH.
  • the number of times of repeated transmission of the PUSCH included in each time-domain resource allocation configuration is predefined or configured by the network device.
  • the number of repeated transmissions of the PUSCH included in each time-domain resource allocation configuration is configured through radio resource control RRC signaling or system messages.
  • the time-domain resource allocation list is used for all terminal devices; or,
  • the time domain resource allocation list is a dedicated list for terminal equipment supporting repeated transmission of the PUSCH.
  • the network device further includes:
  • a communication unit configured to send an uplink grant to the terminal device, where the uplink grant includes second indication information, where the second indication information is used to indicate a target time-domain resource allocation configuration in the multiple time-domain resource allocation configurations .
  • the uplink grant is an uplink grant in a random access response RAR, or the uplink grant is an uplink grant in downlink control information DCI, and the DCI is used to schedule retransmission of the PUSCH .
  • the above-mentioned communication unit may be a communication interface or a transceiver, or an input/output interface of a communication chip or a system-on-chip.
  • the aforementioned processing unit may be one or more processors.
  • the network device 500 may correspond to the network device in the method embodiment of the present application, and the above-mentioned and other operations and/or functions of each unit in the network device 500 are for realizing the method shown in FIG. 3 respectively.
  • the corresponding process of the network device in 300 is not repeated here for brevity.
  • FIG. 6 is a schematic structural diagram of a communication device 600 provided by an embodiment of the present application.
  • the communication device 600 shown in FIG. 6 includes a processor 610, and the processor 610 can call and run a computer program from a memory, so as to implement the method in the embodiment of the present application.
  • the communication device 600 may further include a memory 620 .
  • the processor 610 may call and run a computer program from the memory 620 to implement the methods in the embodiments of the present application.
  • the memory 620 may be a separate device independent of the processor 610 , or may be integrated in the processor 610 .
  • the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, specifically, may send information or data to other devices, or receive other devices Information or data sent by a device.
  • the transceiver 630 may include a transmitter and a receiver.
  • the transceiver 630 may further include antennas, and the number of the antennas may be one or more.
  • the communication device 600 may specifically be the network device in this embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the network device in each method in the embodiment of the present application. For the sake of brevity, details are not repeated here. .
  • the communication device 600 may specifically be the mobile terminal/terminal device of the embodiments of the present application, and the communication device 600 may implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, for the sake of brevity. , and will not be repeated here.
  • FIG. 7 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • the chip 700 shown in FIG. 7 includes a processor 710, and the processor 710 can call and run a computer program from a memory, so as to implement the method in this embodiment of the present application.
  • the chip 700 may further include a memory 720 .
  • the processor 710 may call and run a computer program from the memory 720 to implement the methods in the embodiments of the present application.
  • the memory 720 may be a separate device independent of the processor 710 , or may be integrated in the processor 710 .
  • the chip 700 may further include an input interface 730 .
  • the processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may acquire information or data sent by other devices or chips.
  • the chip 700 may further include an output interface 740 .
  • the processor 710 can control the output interface 740 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.
  • the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which is not repeated here for brevity.
  • the chip can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application.
  • the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application.
  • the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application.
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-a-chip, or the like.
  • FIG. 8 is a schematic block diagram of a communication system 900 provided by an embodiment of the present application. As shown in FIG. 8 , the communication system 900 includes a terminal device 910 and a network device 920 .
  • the terminal device 910 can be used to implement the corresponding functions implemented by the terminal device in the above method
  • the network device 920 can be used to implement the corresponding functions implemented by the network device in the above method. For brevity, details are not repeated here. .
  • the processor in this embodiment of the present application may be an integrated circuit chip, which has a signal processing capability.
  • each step of the above method embodiments may be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software.
  • the above-mentioned processor can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other available Programming logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the methods disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software module may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.
  • the memory in this embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically programmable read-only memory (Erasable PROM, EPROM). Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be Random Access Memory (RAM), which acts as an external cache.
  • RAM Static RAM
  • DRAM Dynamic RAM
  • SDRAM Synchronous DRAM
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM DDR SDRAM
  • enhanced SDRAM ESDRAM
  • synchronous link dynamic random access memory Synchlink DRAM, SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.
  • Embodiments of the present application further provide a computer-readable storage medium for storing a computer program.
  • the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application.
  • the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application.
  • the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application. , and are not repeated here for brevity.
  • Embodiments of the present application also provide a computer program product, including computer program instructions.
  • the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the network device in each method of the embodiments of the present application. Repeat.
  • the computer program product can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, For brevity, details are not repeated here.
  • the embodiments of the present application also provide a computer program.
  • the computer program can be applied to the network device in the embodiments of the present application.
  • the computer program When the computer program is run on the computer, it causes the computer to execute the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity. , and will not be repeated here.
  • the computer program may be applied to the mobile terminal/terminal device in the embodiments of the present application, and when the computer program is run on the computer, the mobile terminal/terminal device implements the various methods of the computer program in the embodiments of the present application.
  • the corresponding process for the sake of brevity, will not be repeated here.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus 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 shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium.
  • the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program codes .

Landscapes

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

Abstract

一种传输数据信道的方法、终端设备和网络设备，该方法包括：终端设备根据物理上行共享信道PUSCH公共配置信息或时域资源分配列表，确定PUSCH的重复传输次数信息，其中，所述PUSCH用于承载随机接入过程中的第三条消息，从而能够实现承载Msg3的PUSCH的重复传输，进而提升Msg3的传输可靠性。

Description

传输数据信道的方法、终端设备和网络设备 技术领域
本申请实施例涉及通信领域，具体涉及一种传输数据信道的方法、终端设备和网络设备。
背景技术
在新无线(New Radio，NR)系统中，为了支持高可靠低时延(ultra-reliable and low latency communication，URLLC)业务，采用了上行数据的重复传输来提高传输可靠性。
在NR系统中，支持四步随机接入过程，具体包括消息1(Msg1)-消息4(Msg4)的发送过程。其中，消息3(Msg3)通过物理上行共享信道(Physical Uplink Shared Channel，PUSCH)承载，如何实现承载Msg3的PUSCH的重复传输以提升Msg3的传输可靠性是一项急需解决的问题。
发明内容
本申请提供了一种传输数据信道的方法、终端设备和网络设备，能够实现承载Msg3的PUSCH的重复传输，从而提升Msg3的传输可靠性。
第一方面，提供了一种传输数据信道的方法，包括：终端设备根据物理上行共享信道PUSCH公共配置信息或时域资源分配列表，确定PUSCH的重复传输次数信息，其中，所述PUSCH用于承载随机接入过程中的第三条消息。
第二方面，提供了一种传输数据信道的方法，包括：。
第三方面，提供了一种终端设备，用于执行上述第一方面或其各实现方式中的方法。
具体地，该终端设备包括用于执行上述第一方面或其各实现方式中的方法的功能模块。
第四方面，提供了一种网络设备，用于执行上述第二方面或其各实现方式中的方法。
具体地，该网络设备包括用于执行上述第二方面或其各实现方式中的方法的功能模块。
第五方面，提供了一种终端设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述第一方面或其各实现方式中的方法。
第六方面，提供了一种网络设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述第二方面或其各实现方式中的方法。
第七方面，提供了一种芯片，用于实现上述第一方面至第二方面中的任一方面或其各实现方式中的方法。
具体地，该芯片包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有该装置的设备执行如上述第一方面至第二方面中的任一方面或其各实现方式中的方法。
第八方面，提供了一种计算机可读存储介质，用于存储计算机程序，该计算机程序使得计算机执行上述第一方面至第二方面中的任一方面或其各实现方式中的方法。
第九方面，提供了一种计算机程序产品，包括计算机程序指令，所述计算机程序指令使得计算机执行上述第一方面至第二方面中的任一方面或其各实现方式中的方法。
第十方面，提供了一种计算机程序，当其在计算机上运行时，使得计算机执行上述第一方面至第二方面中的任一方面或其各实现方式中的方法。
通过上述技术方案，终端设备可以根据PUSCH公共配置信息或时域资源分配列表确定用于承载Msg3的PUSCH的重复传输次数信息，从而能够实现承载Msg3的PUSCH 的重复传输，进而提升Msg3的传输可靠性。
附图说明
图1是本申请实施例提供的一种通信系统架构的示意性图。
图2是四步随机接入过程的示意图。
图3是根据本申请实施例提供的一种传输数据信道的方法的示意性交互图。
图4是根据本申请实施例提供的一种终端设备的示意性框图。
图5是根据本申请实施例提供的一种网络设备的示意性框图。
图6是根据本申请实施例提供的一种通信设备的示意性框图。
图7是根据本申请实施例提供的一种芯片的示意性框图。
图8是根据本申请实施例提供的一种通信系统的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。针对本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、先进的长期演进(Advanced long term evolution，LTE-A)系统、新无线(New Radio，NR)系统、NR系统的演进系统、非授权频谱上的LTE(LTE-based access to unlicensed spectrum，LTE-U)系统、非授权频谱上的NR(NR-based access to unlicensed spectrum，NR-U)系统、非地面通信网络(Non-Terrestrial Networks，NTN)系统、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、无线局域网(Wireless Local Area Networks，WLAN)、无线保真(Wireless Fidelity，WiFi)、第五代通信(5th-Generation，5G)系统或其他通信系统等。
通常来说，传统的通信系统支持的连接数有限，也易于实现，然而，随着通信技术的发展，移动通信系统将不仅支持传统的通信，还将支持例如，设备到设备(Device to Device，D2D)通信，机器到机器(Machine to Machine，M2M)通信，机器类型通信(Machine Type Communication，MTC)，车辆间(Vehicle to Vehicle，V2V)通信，或车联网(Vehicle to everything，V2X)通信等，本申请实施例也可以应用于这些通信系统。
可选地，本申请实施例中的通信系统可以应用于载波聚合(Carrier Aggregation，CA)场景，也可以应用于双连接(Dual Connectivity，DC)场景，还可以应用于独立(Standalone，SA)布网场景。
可选地，本申请实施例中的通信系统可以应用于非授权频谱，其中，非授权频谱也可以认为是共享频谱；或者，本申请实施例中的通信系统也可以应用于授权频谱，其中，授权频谱也可以认为是非共享频谱。
本申请实施例结合网络设备和终端设备描述了各个实施例，其中，终端设备也可以称为用户设备(User Equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置等。
终端设备可以是WLAN中的站点(STATION，ST)，可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字助理(Personal Digital Assistant，PDA)设备、具有无线通信功能的 手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、下一代通信系统例如NR网络中的终端设备，或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)网络中的终端设备等。
在本申请实施例中，终端设备可以部署在陆地上，包括室内或室外、手持、穿戴或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。
在本申请实施例中，终端设备可以是手机(Mobile Phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(Virtual Reality，VR)终端设备、增强现实(Augmented Reality，AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶(self driving)中的无线终端设备、远程医疗(remote medical)中的无线终端设备、智能电网(smart grid)中的无线终端设备、运输安全(transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备或智慧家庭(smart home)中的无线终端设备等。
作为示例而非限定，在本申请实施例中，该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
在本申请实施例中，网络设备可以是用于与移动设备通信的设备，网络设备可以是WLAN中的接入点(Access Point，AP)，GSM或CDMA中的基站(Base Transceiver Station，BTS)，也可以是WCDMA中的基站(NodeB，NB)，还可以是LTE中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者中继站或接入点，或者车载设备、可穿戴设备以及NR网络中的网络设备(gNB)或者未来演进的PLMN网络中的网络设备或者NTN网络中的网络设备等。
作为示例而非限定，在本申请实施例中，网络设备可以具有移动特性，例如网络设备可以为移动的设备。可选地，网络设备可以为卫星、气球站。例如，卫星可以为低地球轨道(low earth orbit，LEO)卫星、中地球轨道(medium earth orbit，MEO)卫星、地球同步轨道(geostationary earth orbit，GEO)卫星、高椭圆轨道(High Elliptical Orbit，HEO)卫星等。可选地，网络设备还可以为设置在陆地、水域等位置的基站。
在本申请实施例中，网络设备可以为小区提供服务，终端设备通过该小区使用的传输资源(例如，频域资源，或者说，频谱资源)与网络设备进行通信，该小区可以是网络设备(例如基站)对应的小区，小区可以属于宏基站，也可以属于小小区(Small cell)对应的基站，这里的小小区可以包括：城市小区(Metro cell)、微小区(Micro cell)、微微小区(Pico cell)、毫微微小区(Femto cell)等，这些小小区具有覆盖范围小、发射功率低的特点，适用于提供高速率的数据传输服务。
示例性的，本申请实施例应用的通信系统100如图1所示。该通信系统100可以包括网络设备110，网络设备110可以是与终端设备120(或称为通信终端、终端)通信的设备。网络设备110可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的终端设备进行通信。
图1示例性地示出了一个网络设备和两个终端设备，可选地，该通信系统100可以包括多个网络设备并且每个网络设备的覆盖范围内可以包括其它数量的终端设备，本申请实施例对此不做限定。
可选地，该通信系统100还可以包括网络控制器、移动管理实体等其他网络实体，本申请实施例对此不作限定。
应理解，本申请实施例中网络/系统中具有通信功能的设备可称为通信设备。以图1示出的通信系统100为例，通信设备可包括具有通信功能的网络设备110和终端设备120，网络设备110和终端设备120可以为上文所述的具体设备，此处不再赘述；通信设备还可包括通信系统100中的其他设备，例如网络控制器、移动管理实体等其他网络实体，本申请实施例中对此不做限定。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请的实施例中提到的“指示”可以是直接指示，也可以是间接指示，还可以是表示具有关联关系。举例说明，A指示B，可以表示A直接指示B，例如B可以通过A获取；也可以表示A间接指示B，例如A指示C，B可以通过C获取；还可以表示A和B之间具有关联关系。
在本申请实施例的描述中，术语“对应”可表示两者之间具有直接对应或间接对应的关系，也可以表示两者之间具有关联关系，也可以是指示与被指示、配置与被配置等关系。
本申请实施例中，"预定义"可以通过在设备(例如，包括终端设备和网络设备)中预先保存相应的代码、表格或其他可用于指示相关信息的方式来实现，本申请对于其具体的实现方式不做限定。比如预定义可以是指协议中定义的。
本申请实施例中，所述"协议"可以指通信领域的标准协议，例如可以包括LTE协议、NR协议以及应用于未来的通信系统中的相关协议，本申请对此不做限定。
为便于理解本申请实施例的技术方案，以下通过具体实施例详述本申请的技术方案。以下相关技术作为可选方案与本申请实施例的技术方案可以进行任意结合，其均属于本申请实施例的保护范围。本申请实施例包括以下内容中的至少部分内容。
在NR系统中，网络设备发送上行授权(UL grant)，该UL grant承载在下行控制信息(Downlink Control Information，DCI)中，该DCI为DCI(格式)format 0_0，或DCI format 0_1，调度物理上行共享信道(Physical Uplink Shared Channel，PUSCH)传输。
网络设备通过承载UL grant的DCI调度上行数据传输时，会在DCI中携带一个时域资源分配(TimeDomainResourceAllocation，TDRA)域，该TDRA域为4bit，可以指示一个时域资源分配表格中的16个不同的行，每一行包含不同的资源分配组合，比如PUSCH的起始位置S，长度L，k2，以及不同的映射类型(type)等。其中，k2表示DCI所在的时隙(slot)和PUSCH所在的slot之间偏移的slot的个数。PUSCH的时域资源分配的type包括类型A(Type A)和类型B(Type B)。Type A和Type B的区别在于对应的S和L候选值的取值范围不同。其中，Type A主要面向基于时隙(slot-based)业务，S比较靠前，L比较长。而Type B主要面向高可靠低时延通信(Ultra-Reliable and Low Latency Communication，URLLC)业务，对时延要求较高，所以S的位置比较灵活以便传输随时到达的URLLC业务，L较短，可降低传输时延。S和L可选的取值范围如下表1所示。
表1
Figure PCTCN2021078883-appb-000001
Figure PCTCN2021078883-appb-000002
承载UL grant的DCI中除了上述时域资源分配信息之外，还包括频域资源信息，调制编码方案(Modulation and Coding Scheme，MCS)，功率控制命令(Transmission Power Control，TPC)，跳频信息，冗余版本，混合自动请求重传(Hybrid Automatic Repeat reQuest，HARQ)进程号等，这里不再赘述。
在NR系统中，支持四步随机接入过程，具体包括消息1(Msg1)-消息4(Msg4)的发送过程。作为一个示例，如图2所示，四步随机接入过程包括如下步骤：
步骤1，终端设备向网络设备发送随机接入前导码(Preamble，也即Msg 1)。
其中，随机接入前导码也可以称为前导码、随机接入前导码序列、前导码序列等。
具体而言，终端设备可以选择物理随机接入信道(Physical Random Access Channel，PRACH)资源，PRACH资源可以包括时域资源、频域资源和码域资源。网络设备通过广播系统信息块(System Information Block，SIB)1向终端设备发送随机接入相关参数，其中随机接入公共配置信息元素(RACH-ConfigCommon IE)中的针对同步信号块(Synchronization Signal Block，SSB)的参考信号接收功率(Reference Signal Receiving Power，RSRP)门限值(rsrp-ThresholdSSB)用于终端设备进行SSB选择，终端设备将每个SSB下的RSRP测量结果与rsrp-ThresholdSSB进行对比，选择测量值高于所配置门限值的SSB进行接入，若没有满足配置门限值的SSB，则从全部SSB中随机选择一个进行接入。每个SSB对应一组随机接入前导码(Preamble)资源和随机接入时机(RACH Occasion，RO)资源，终端设备从选定的SSB中用于基于竞争的随机接入资源中进行随机选择，将Preamble索引(PREAMBLE_INDEX)设置为选定的随机接入Preamble。网络设备可以根据Preamble估计其与终端设备之间的传输时延并以此校准上行定时(timing)，以及可以大体确定终端设备传输Msg 3所需要的资源大小。为了让网络设备可以更准确的了解到待传输的Msg 3的大小以分配合适的上行资源，将Preamble分为Preamble组(group)A和Preamble group B，若随机接入资源中存在Preamble group B，终端设备可以根据Msg 3的大小以及路损(pathloss)对Preamble group进行选择。
步骤2，网络设备向终端设备发送随机接入响应(Random Access Response，RAR，也即Msg 2)
终端设备向网络设备发送Preamble后，可以开启一个随机接入响应窗口(ra-ResponseWindow)，在该ra-ResponseWindow内根据随机访问无线网络临时标识符(Random Access Radio Network Temporary Identifier，RA-RNTI)检测对应的物理下行控制信道(Physical Downlink Control Channel，PDCCH)。若终端设备检测到RA-RNTI加扰的PDCCH后，可以获得该PDCCH调度的物理下行共享信道(Physical Downlink Shared Channel，PDSCH)。其中，该PDSCH中包括Preamble对应的RAR。
RA-RNTI根据发送Preamble的PRACH的时频位置计算得到，因此如果多个终端设备在同一个RO上发送Preamble，则对应的RAR复用在同一个RAR媒体接入控制协议数据单元(Media Access Control Protocol Data Unit，MAC PDU)中。若终端成功接收到与发送Preamble的RO资源对应的RA-RNTI加扰的PDCCH，并且RAR中包含一个MAC子PDU(subPDU)所携带的随机访问序列标识符(Random Access Preamble Identifier，RAPID)与上述Msg 1中选择的PREAMBLE_INDEX相对应，则RAR接收成功，终端可解码得到定时提前命令(Timing Advance Command，TAC)，上行授权资源(UL Grant)和临时小区RNTI(Temporary Cell Radio Network Temporary Identity，TC-RNTI)，进行Msg 3。
若在ra-ResponseWindow运行期间没有接收到与发送Preamble的RO资源对应的RA-RNTI加扰的PDCCH，或接收到了RA-RNTI加扰的PDCCH，但RAR中不包含与PREAMBLE_INDEX对应的MAC subPDU，上述两种情况出现时则认为RAR接收失败， 此时，若Preamble的传输次数没有超过网络配置的最大传输次数(preambleTransMax)，终端设备需要对Msg 1进行重传，若Preamble的传输次数超过了网络配置的最大传输次数(preambleTransMax)，终端设备向上层上报随机接入问题。
步骤3，终端设备发送Msg 3。
终端设备在收到RAR消息后，判断该RAR是否为属于自己的RAR消息，例如终端设备可以利用前导码索引进行核对，在确定是属于自己的RAR消息后，可以在RRC层产生Msg 3，并向网络设备发送Msg 3，其中需要携带终端设备的标识信息等。
其中，Msg 3主要用于通知网络设备该随机接入的触发事件。针对不同的随机接入触发事件，终端设备在步骤3中发送的Msg 3可以包括不同的内容。
例如，对于初始接入的场景，Msg 3可以包括RRC层生成的RRC连接请求消息(RRC Setup Request)。此外，Msg 3还可以携带例如终端设备的5G-服务临时移动用户标识(Serving-Temporary Mobile Subscriber Identity，S-TMSI)或随机数等。
又例如，对于RRC连接重建场景，Msg 3可以包括RRC层生成的RRC连接重建请求消息(RRC Reestabilshment Request)。此外，Msg 3还可以携带例如小区无线网络临时标识(Cell Radio Network Temporary Identifier，C-RNTI)等。
又例如，对于切换场景，Msg 3可以包括RRC层生成的RRC切换确认消息(RRC Handover Confirm)，其携带终端设备的C-RNTI。此外，Msg 3还可携带例如缓冲状态报告(Buffer Status Report，BSR)等信息。对于其它触发事件例如上/下行数据到达的场景，Msg 3至少可以包括终端设备的C-RNTI。
步骤4，网络设备向终端设备发送冲突解决消息(contention resolution)，即Msg 4。
网络设备向终端设备发送Msg 4，终端设备正确接收Msg 4完成竞争解决(Contention Resolution)。例如在RRC连接建立过程中，Msg 4中可以携带RRC连接建立消息。
其中，消息3(Msg3)通过物理上行共享信道(Physical Uplink Shared Channel，PUSCH)承载，Msg2中的RAR承载用于Msg3的初次传输的PUSCH的UL grant，RAR中承载的UL grant称为RAR UL grant。RAR UL grant信息承载的信息可以包括PUSCH的时域和频域资源分配信息，功率控制命令TPC，跳频，和MCS等。
如果网络设备没有正确收到Msg3，会通过DCI指示Msg3的重传的调度信息，例如通过临时小区无线网络临时标识符(Temporary Cell Radio Network Temporary Identity，TC-RNTI)加扰的DCI format 0_0承载，除了RAR UL grant包含的内容之外，还包括新数据指示(New Data Indicator，NDI)，冗余版本，HARQ进程号。
在NR系统中，为了支持高可靠低时延(ultra-reliable and low latency communication，URLLC)业务，采用了上行数据的重复传输来提高传输可靠性，因此，如何实现承载Msg3的PUSCH的重复传输以提升Msg3的传输可靠性是一项急需解决的问题。
图3是根据本申请实施例的传输数据信道的方法300的示意性交互图，如图3所示，该方法300包括如下至少部分内容：
S310，终端设备根据物理上行共享信道PUSCH公共配置信息或时域资源分配列表，确定PUSCH的重复传输次数信息，其中，所述PUSCH用于承载随机接入过程中的第三条消息(即Msg3)。
在本申请实施例中，用于承载Msg3的PUSCH也可以称为Msg3 PUSCH。
在一些实施例中，该方法300还可以包括：
S301，终端设备接收网络设备发送的PUSCH公共配置信息(pusch-ConfigCommon)。
在本申请一些实施例中，该PUSCH公共配置信息用于承载PUSCH的重复传输次数信息。
在本申请实施例中，该PUSCH公共配置信息通过系统消息发送。
在一些实施例中，该Msg3 PUSCH的重复传输次数信息可以包括用于该Msg3 PUSCH的初传的重复传输次数信息，和/或，用于该Msg3 PUSCH的重传的重复传输次 数信息。
可选地，用于该Msg3 PUSCH的初传的重复传输次数信息和用于该Msg3 PUSCH的重传的重复传输次数信息可以相同，或者也可以不同。
在一些实施例中，该PUSCH公共配置信息包括第一重复传输次数信息组，该第一重复传输次数组可以包括用于Msg3 PUSCH传输的至少一个重复传输次数信息。
可选地，该第一重复传输次数信息组可以用于Msg3 PUSCH的初传和重传。
在一些实施例中，若该第一重复传输次数信息组包括的重复传输次数的数量为多个，网络设备可以向终端设备指示该第一重复传输次数信息组中的目标重复传输次数信息，例如通过比特位图方式指示该目标重复传输次数信息，具体指示方式在下文中详细阐述。
在另一些实施例中，该PUSCH公共配置信息包括第二重复传输次数信息组和第三重复传输次数信息组，该第二重复传输次数组包括用于Msg3 PUSCH初传的至少一个重复传输次数信息，该第三重复传输次数信息组包括用于Msg3 PUSCH重传的至少一个重复传输次数信息。
可选地，若该第二重复传输次数组包括的重复传输次数的数量为多个，在PUSCH的初传场景中，网络设备可以向终端设备指示该第二重复传输次数组中的目标重复传输次数信息，例如通过比特位图方式指示该目标重复传输次数信息，具体指示方式在下文中详细阐述。
可选地，若该第三重复传输次数组包括的重复传输次数的数量为多个，在PUSCH的重传场景中，网络设备可以向终端设备指示该第三重复传输次数组中的目标重复传输次数信息，例如通过比特位图方式指示该目标重复传输次数信息，具体指示方式在下文中详细阐述。
应理解，本申请实施例也同样适用于确定用于承载其他消息的PUSCH的重复传输次数。例如，用于承载MsgA的PUSCH的重复传输次数，其中，该MsgA为基于竞争的两步随机接入的第一条消息，此情况下，该PUSCH可以称为MsgA PUSCH，该MsgA PUSCH的重复传输次数信息可以通过MsgA公共配置信息配置，具体的配置方式参考通过PUSCH公共配置信息配置Msg3 PUSCH的重复传输次数信息的相关实现。
在本申请一些实施例中，该PUSCH公共配置信息包括PUSCH时域资源分配列表信息元素(Information Element，IE)，该Msg3 PUSCH的重复传输次数信息包括在PUSCH时域资源分配列表IE中。
在一些实施例中，所述PUSCH时域资源分配列表IE包括多个时域资源分配配置，每个时域资源分配配置包括一组时域资源分配信息和PUSCH的重复传输次数信息。
可选地，每组时域资源分配信息可以包括如下信息中的至少一项：
k2、PUSCH的映射类型、起始符号、长度，其中，k2表示调度PUSCH的信令所在的时隙(slot)和PUSCH所在的slot之间偏移的slot的个数。
在一些实施例中，每个时域资源分配配置包括一个重复传输次数信息，所述一组重复传输次数信息用于所述PUSCH的初传和重传。
在另一些实施例中，每个时域资源分配配置包括两个重复传输次数信息，所述两个重复传输次数信息分别用于所述PUSCH的初传和重传。
在一些实施例中，该PUSCH时域资源分配列表IE可以复用现有的IE，例如，PUSCH-TimeDomainResourceAllocationList-r16，或者也可以为新定义的IE，例如PUSCH-TimeDomainResourceAllocationList-r17。
例如，PUSCH-TimeDomainResourceAllocationList-r16可以包括k2，PUSCH的映射类型，起始符号，长度和重复传输次数等信息。
作为示例，PUSCH-TimeDomainResourceAllocationList-r16定义如下：
PUSCH-TimeDomainResourceAllocationList-r16::＝SEQUENCE
(SIZE(1..maxNrofUL-Allocations-r16))OF  PUSCH-TimeDomainResourceAllocation-r16
PUSCH-TimeDomainResourceAllocation-r16::＝SEQUENCE{
k2-r16INTEGER(0..32)OPTIONAL,--Need S
puschAllocationList-r16SEQUENCE(SIZE(1..maxNrofMultiplePUSCHs-r16))OF PUSCH-Allocation-r16,
...
}
PUSCH-Allocation-r16::＝SEQUENCE{
mappingType-r16 ENUMERATED{typeA,typeB}OPTIONAL,--Cond NotFormat01-02-Or-TypeA
startSymbolAndLength-r16 INTEGER(0..127)OPTIONAL,--Cond NotFormat01-02-Or-TypeA
startSymbol-r16 INTEGER(0..13)OPTIONAL,--Cond RepTypeB
length-r16 INTEGER(1..14)OPTIONAL,--Cond RepTypeB
numberOfRepetitions-r16 ENUMERATED{n1,n2,n3,n4,n7,n8,n12,n16}OPTIONAL,--Cond Format01-02
...
}
其中，numberOfRepetitions-r16用于指示PUSCH的重复传输次数K，startSymbolAndLength用于指示PUSCH的起始符号S和长度L。
在一些实施例中，终端设备根据上述信息以及通过高层信令确定的PUSCH repetition Type，确定用于PUSCH的重传的时域资源。
例如，对于PUSCH repetition Type A，终端设备在连续的K个时隙重复传输相同的传输块。每个时隙内的符号分配相同，即startSymbolAndLength所指示的时隙内的符号分配。
又例如，对于PUSCH repetition Type B，对于第n次PUSCH传输，n＝0,…,numberOfRepetitions-1：
PUSCH传输起始位置所在的时隙为
Figure PCTCN2021078883-appb-000003
相对于该时隙起始位置的PUSCH起始符号为
Figure PCTCN2021078883-appb-000004
PUSCH传输结束位置所在的时隙为
Figure PCTCN2021078883-appb-000005
相对于该时隙起始位置的PUSCH结束符号为
Figure PCTCN2021078883-appb-000006
其中，K s为PUSCH重复传输的开始位置所在的时隙，
Figure PCTCN2021078883-appb-000007
为每个时隙包含的符号个数。
也就是说，对于PUSCH repetition Type B，PUSCH的K次传输在时隙K s的符号S开始，在连续的K*L个符号上传输，每次传输包含L个符号。
在一些实施例中，该PUSCH-TimeDomainResourceAllocationList-r17也可以包括PUSCH-TimeDomainResourceAllocationList-r16中所示例的信息。
可选地，在本申请一些实施例中，该方法300还包括：
S302，终端设备接收网络设备发送的上行授权。
在一些实施例中，所述上行授权为随机接入响应RAR中的上行授权，该上行授权用于调度该PUSCH的重传。
在另一些实施例中，所述上行授权为下行控制信息DCI中的上行授权，所述DCI用于调度所述PUSCH的重传。
在本申请一些实施例中，S310可以包括：
所述终端设备根据所述PUSCH公共配置信息和网络设备发送的所述上行授权，确定所述PUSCH的重复传输次数信息。
在一些实施例中，所述上行授权包括第一指示信息，所述第一指示信息用于指示所述PUSCH公共配置信息中的目标重复传输次数信息。
例如，若该PUSCH公共配置信息中包括多个用于Msg3 PUSCH的重复传输次数信息，该网络设备可以通过第一指示信息指示该多个重复次数信息中的目标重复传输次数信息，例如通过比特位图方式指示。
又例如，若该PUSCH公共配置信息中包括多个时域资源分配配置，每个时域资源分配配置对应相应的PUSCH的重复次数信息，该网络设备可以通过第一指示信息指示该多个时域资源分配配置中的目标时域资源分配配置，例如通过比特位图方式指示。
在一些实施例中，时域资源分配信息和PUSCH的重复传输次数信息可以是具有关联关系的。例如，时域资源分配信息和关联的PUSCH的重复传输次数为一个时域资源分配配置，对应一个时域资源分配配置索引，此情况下，可以通过一个指示信息(例如，时域资源分配配置索引)指示用于PUSCH传输的目标时域资源分配信息以及重复传输次数信息。
在另一些实施例中，时域资源分配信息和PUSCH的重复传输次数信息是独立的，此情况下，可以通过分别对应的指示信息指示用于Msg3 PUSCH传输的时域资源分配信息，以及用于Msg3 PUSCH传输的重复传输次数信息。
例如，在前述实施例中，该PUSCH公共配置信息可以包括第一重复传输次数信息组，若该第一重复传输次数信息组包括的重复传输次数的数量为多个，该第一指示信息可以包括第一比特位图，该第一比特位图可以用于指示该第一重复传输次数信息组中的目标重复传输次数信息。
又例如，在前述实施例中，该PUSCH公共配置信息包括第二重复传输次数信息组，若该第二重复传输次数信息组包括的重复传输次数的数量为多个，在PUSCH初传场景下，该第一指示信息可以包括第二比特位图，该第二比特位图可以用于指示该第二重复传输次数信息组中的目标重复传输次数信息。
又例如，在前述实施例中，该PUSCH公共配置信息包括第三重复传输次数信息组，若该第三重复传输次数信息组包括的重复传输次数的数量为多个，在PUSCH重传场景下，该第一指示信息可以包括第三比特位图，该第三比特位图可以用于指示该第三重复传输次数信息组中的目标重复传输次数信息。
在本申请另一些实施例中，所述PUSCH公共配置信息的IE中包括所述PUSCH的重复传输次数信息。此情况下，该PUSCH的重复传输次数信息可以为用于小区内的所有终端设备的重复传输次数信息，即该PUSCH的重复传输次数信息为小区级的Msg3 PUSCH的重复传输次数信息。
在一些实施例中，可以在pusch-ConfigCommon中新增IE，用于指示小区级的Msg3 PUSCH的重复传输次数信息。
作为示例，PUSCH-ConfigCommon information element格式如下：
--ASN1START
--TAG-PUSCH-CONFIGCOMMON-START
PUSCH-ConfigCommon::＝SEQUENCE{
groupHoppingEnabledTransformPrecoding ENUMERATED{enabled}OPTIONAL,--Need R
pusch-TimeDomainAllocationList PUSCH-TimeDomainResourceAllocationList OPTIONAL,--Need R
OPTIONAL,--Need R
msg3-DeltaPreamble INTEGER(-1..6)OPTIONAL,--Need R
p0-NominalWithGrant INTEGER(-202..24)OPTIONAL,--Need R
Msg3-numberOfRepetitions-r17 ENUMERATED{n1,n2,n3,n4,n7,n8,n12,n16}OPTIONAL,--Cond
...
}
其中，该Msg3-numberOfRepetitions-r17可以用于指示小区级的Msg3 PUSCH的重复传输次数。
在一些实施例中，小区级的Msg3 PUSCH的重复传输次数信息可以包括第四重复传输次数信息组，该第四重复传输次数组可以包括用于Msg3 PUSCH传输的至少一个重复传输次数信息。
可选地，该第四重复传输次数组可以用于Msg3 PUSCH的初传和重传。
可选地，若该第四重复传输次数组包括的重复传输次数信息的数量为多个，网络设备可以向终端设备指示该第四重复传输次数组中的目标重复传输次数信息。
例如，网络设备可以向终端设备发送上行授权，该上行授权中包括第三指示信息，该第三指示信息用于指示该第四重复传输次数组中的目标重复传输次数信息。
在另一些实施例中，小区级的Msg3 PUSCH的重复传输次数信息可以包括第五重复传输次数信息组和第六重复传输次数信息组，该第五重复传输次数组包括用于Msg3 PUSCH初传的至少一个重复传输次数信息，该第六重复传输次数信息组包括用于Msg3 PUSCH重传的至少一个重复传输次数信息。
可选地，所述用于Msg3 PUSCH的初传的重复传输次数信息和用于Msg3 PUSCH的重传的重复传输次数信息可以相同，或者也可以不同。
可选地，若第五重复传输次数组包括的重复传输次数信息的数量为多个，网络设备可以向终端设备指示该第五重复传输次数组中的目标重复传输次数信息。
例如，在Msg3 PUSCH初传场景中，网络设备可以向终端设备发送上行授权，该上行授权中包括第四指示信息，该第四指示信息用于指示该第五重复传输次数组中的目标重复传输次数信息。
可选地，若第六重复传输次数组包括的重复传输次数信息的数量为多个，网络设备可以向终端设备指示该第六重复传输次数组中的目标重复传输次数信息。
例如，在Msg3 PUSCH重传场景中，网络设备可以向终端设备发送上行授权，该上行授权中包括第五指示信息，该第五指示信息用于指示该第六重复传输次数组中的目标重复传输次数信息。
在本申请一些实施例中，在PUSCH公共配置信息不包括PUSCH的重复传输次数信息的情况下，所述终端设备可以根据时域资源分配列表确定Msg3 PUSCH的重复传输次数信息。例如，所述终端设备可以在PUSCH公共配置信息不包括PUSCH时域资源分配列表IE的情况下，根据时域资源分配列表确定Msg3 PUSCH的重复传输次数信息。
在本申请一些实施例中，所述时域资源分配列表为缺省(default)PUSCH时域资源分配列表(time domain resource allocation)，所述缺省PUSCH时域资源分配列表(default PUSCH time domain resource allocation)包括多个时域资源分配配置，每个时域资源分配配置包括一组时域资源分配信息和PUSCH的重复传输次数信息。
可选地，每组时域资源分配信息可以包括如下信息中的至少一项：
k2、PUSCH的映射类型、起始符号、长度，其中，k2表示调度PUSCH的信令所在的时隙(slot)和PUSCH所在的slot之间偏移的slot的个数。
在一些实施例中，每个时域资源分配配置包括一个重复传输次数信息，所述一个重复传输次数信息用于所述Msg3 PUSCH的初传和重传。
在另一些实施例中，所述每个时域资源分配配置包括两个重复传输次数信息，所述两个重复传输次数信息分别用于所述Msg3 PUSCH的初传和重传。
在一些实施例中，所述每个时域资源分配配置对应的PUSCH的重复传输次数是预定 义的，或者是由网络设备配置的。
作为示例，所述每个时域资源分配配置包括的PUSCH的重复传输次数通过无线资源控制RRC信令或系统消息配置。例如，通过pusch-ConfigCommon配置。
在一些实施例中，所述时域资源分配列表用于所有的终端设备；或者，
所述时域资源分配列表为用于支持重复传输所述PUSCH的终端设备的专用列表。
在一些实施例中，网络设备可以向终端设备发送第二指示信息，所述第二指示信息用于指示所述多个时域资源分配配置中的目标时域资源分配配置。
可选地，该第二指示信息包括在上行授权中。
在一些实施例中，每个时域资源分配配置对应一个时域资源分配配置索引，该第二指示信息可以用于指示该目标时域资源分配配置对应的索引。
作为示例，default PUSCH time domain resource allocation如表2所示。
表2
Figure PCTCN2021078883-appb-000008
在表2的示例中，每行为一个时域资源分配配置，一个时域资源分配配置对应一个行号，该第二指示信息可以用于指示目标时域资源分配配置对应的行号。
在本申请一些实施例中，时域资源分配信息和PUSCH的重复传输次数信息可以通过一个表格承载，此情况下，该时域资源分配信息和PUSCH的重复传输次数信息可以是具有关联关系的，时域资源分配信息和关联的PUSCH的重复传输次数可以认为是一个时域资源分配配置，对应一个时域资源分配配置索引，此情况下，可以通过一个指示信息(例如，时域资源分配配置索引)指示用于PUSCH传输的目标时域资源分配信息以及重复传输次数信息。
在本申请另一些实施例中，时域资源分配信息和PUSCH的重复传输次数信息可以分别通过对应的表格承载，此情况下，时域资源分配信息和PUSCH的重复传输次数信息可以是具有关联关系的，或者也可以是独立的。
例如，时域资源分配配置对应缺省PUSCH时域资源分配列表，PUSCH的重复传输次数信息对应PUSCH重复传输次数列表，PUSCH重复传输次数列表可以包括至少一个重复传输次数信息，网络设备可以通过分别对应的指示信息指示用于PUSCH传输的目标时域资源分配信息以及目标重复传输次数信息。
又例如，PUSCH重复传输次数列表可以包括多组PUSCH重复传输次数配置，每组PUSCH重复传输次数配置包括每组时域资源分配信息分别对应的重复传输次数信息。网 络设备可以通过信令(例如RRC信令或DCI)激活该多组PUSCH重复传输次数配置中的一组PUSCH重复传输次数配置。该网络设备指示缺省PUSCH时域资源分配列表中的目标时域资源分配信息，相对于指示该激活的一组PUSCH重复传输次数配置中该目标时域资源分配信息对应的重复传输次数信息为目标重复传输次数信息。
举例说明，该PUSCH重复传输次数列表可以包括M组PUSCH重复传输次数配置，每组PUSCH重复传输次数配置包括16个PUSCH重复传输次数信息，该16个PUSCH重复传输次数信息和表2中的16行时域资源分配信息一一对应，每个PUSCH重复传输次数信息可以用于PUSCH的初传和重传。或者，每行时域资源分配信息也可以对应两个PUSCH重复传输次数信息，分别用于PUSCH的初传和重传，本申请并不限于此。
网络设备可以指示该M组PUSCH重复传输次数配置中的激活的PUSCH重复传输次数配置，例如，激活第一组PUSCH重复传输次数配置。此情况下，终端设备可以根据该第一组PUSCH重复传输次数配置确定PUSCH的目标重复传输次数。例如，网络设备可以向终端设备发送上行授权，该上行授权中可以包括第六指示信息，用于指示该第一组PUSCH重复传输次数配置中的目标PUSCH重复传输次数，例如通过比特位图方式指示；或者，该第六指示信息用于指示缺省PUSCH时域资源分配列表中的目标时域资源分配信息，此情况下，该终端设备可以将目标时域资源分配信息在该一组PUSCH重复传输次数配置中对应的重复传输次数确定为目标重复传输次数信息。
综上，终端设备可以根据PUSCH公共配置信息或时域资源分配列表确定用于承载Msg3的PUSCH的重复传输次数信息，或者，更具体地，可以在Msg3 PUSCH的初传场景中，确定用于Msg3 PUSCH的初传的重复传输次数信息，在Msg3 PUSCH的重传场景中，确定用于Msg3 PUSCH的重传的重复传输次数信息，从而能够实现承载Msg3的PUSCH的重复传输，进而提升Msg3的传输可靠性。
上文结合图3，详细描述了本申请的方法实施例，下文结合图4至图7，详细描述本申请的装置实施例，应理解，装置实施例与方法实施例相互对应，类似的描述可以参照方法实施例。
图4示出了根据本申请实施例的终端设备400的示意性框图。如图4所示，该终端设备400包括：
处理单元410，用于根据物理上行共享信道PUSCH公共配置信息或时域资源分配列表，确定PUSCH的重复传输次数信息，其中，所述PUSCH用于承载随机接入过程中的第三条消息。
在本申请一些实施例中，所述PUSCH公共配置信息包括PUSCH时域资源分配列表信息元素IE，所述PUSCH时域资源分配列表IE包括所述PUSCH的重复传输次数信息。
在本申请一些实施例中，所述PUSCH时域资源分配列表IE包括多个时域资源分配配置，每个时域资源分配配置包括一组时域资源分配信息和PUSCH的重复传输次数信息。
在本申请一些实施例中，所述每个时域资源分配配置包括一个重复传输次数信息，所述一个重复传输次数信息用于所述PUSCH的初传和重传；或者
所述每个时域资源分配配置包括两个重复传输次数信息，所述两个重复传输次数信息分别用于所述PUSCH的初传和重传。
在本申请一些实施例中，所述处理单元410还用于：
根据所述PUSCH公共配置信息和网络设备发送的上行授权，确定所述PUSCH的重复传输次数信息，其中，所述上行授权包括第一指示信息，所述第一指示信息用于指示所述多个时域资源分配配置中的目标时域资源分配配置。
在本申请一些实施例中，所述PUSCH公共配置信息的IE中包括所述PUSCH的重复传输次数信息。
在本申请一些实施例中，所述PUSCH公共配置信息的IE中包括一组重复传输次数 信息，所述一组重复传输次数信息用于所述PUSCH的初传和重传；或者
所述PUSCH公共配置信息的IE中包括两组重复传输次数信息，所述两组重复传输次数信息分别用于所述PUSCH的初传和重传。
在本申请一些实施例中，所述时域资源分配列表为缺省PUSCH时域资源分配列表，所述缺省PUSCH时域资源分配列表包括多个时域资源分配配置，每个时域资源分配配置包括一组时域资源分配信息和PUSCH的重复传输次数信息。
在本申请一些实施例中，所述每个时域资源分配配置包括一个重复传输次数信息，所述一个重复传输次数信息用于所述PUSCH的初传和重传；或者
所述每个时域资源分配配置包括两个重复传输次数信息，所述两个重复传输次数信息分别用于所述PUSCH的初传和重传。
在本申请一些实施例中，所述每个时域资源分配配置包括的PUSCH的重复传输次数是预定义的，或者是由网络设备配置的。
在本申请一些实施例中，所述每个时域资源分配配置包括的PUSCH的重复传输次数通过无线资源控制RRC信令或系统消息配置。
在本申请一些实施例中，所述时域资源分配列表用于所有的终端设备；或者，
所述时域资源分配列表为用于支持重复传输所述PUSCH的终端设备的专用列表。
在本申请一些实施例中，所述处理单元410还用于：
根据所述时域资源分配列表和网络设备发送的上行授权，确定所述PUSCH的重复传输次数信息，其中，所述上行授权包括第二指示信息，所述第二指示信息用于指示所述多个时域资源分配配置中的目标时域资源分配配置。
在本申请一些实施例中，所述上行授权为随机接入响应RAR中的上行授权，或者所述上行授权为下行控制信息DCI中的上行授权，所述DCI用于调度所述PUSCH的重传。
可选地，在一些实施例中，上述通信单元可以是通信接口或收发器，或者是通信芯片或者片上系统的输入输出接口。上述处理单元可以是一个或多个处理器。
应理解，根据本申请实施例的终端设备400可对应于本申请方法实施例中的终端设备，并且终端设备400中的各个单元的上述和其它操作和/或功能分别为了实现图3所示方法300中终端设备的相应流程，为了简洁，在此不再赘述。
图5是根据本申请实施例的网络设备的示意性框图。图5的网络设备500包括：
处理单元510，用于通过物理上行共享信道PUSCH公共配置信息或时域资源分配列表，为终端设备配置PUSCH的重复传输次数信息，其中，所述PUSCH用于承载随机接入过程中的第三条消息。
在本申请一些实施例中，所述PUSCH公共配置信息包括PUSCH时域资源分配列表信息元素IE，所述PUSCH时域资源分配列表IE包括所述PUSCH的重复传输次数信息。
在本申请一些实施例中，所述PUSCH时域资源分配列表IE包括多个时域资源分配配置，每个时域资源分配配置包括一组时域资源分配信息和PUSCH的重复传输次数信息。
在本申请一些实施例中，所述每个时域资源分配配置包括一个重复传输次数信息，所述一个重复传输次数信息用于所述PUSCH的初传和重传；或者
所述每个时域资源分配配置包括两个重复传输次数信息，所述两个重复传输次数信息分别用于所述PUSCH的初传和重传。
在本申请一些实施例中，所述网络设备500还包括：
通信单元，用于向所述终端设备发送上行授权，其中，所述上行授权包括第一指示信息，所述第一指示信息用于指示所述多个时域资源分配配置中的目标时域资源分配配置。
在本申请一些实施例中，所述PUSCH公共配置信息的IE中包括所述PUSCH的重复传输次数信息。
在本申请一些实施例中，所述PUSCH公共配置信息的IE中包括一组重复传输次数信息，所述一组重复传输次数信息用于所述PUSCH的初传和重传；或者
所述PUSCH公共配置信息的IE中包括两组重复传输次数信息，所述两组重复传输次数信息分别用于所述PUSCH的初传和重传。
在本申请一些实施例中，所述时域资源分配列表为缺省PUSCH时域资源分配列表，所述缺省PUSCH时域资源分配列表包括多个时域资源分配配置，每个时域资源分配配置包括一组时域资源分配信息和PUSCH的重复传输次数信息。
在本申请一些实施例中，所述每个时域资源分配配置包括一个重复传输次数信息，所述一个重复传输次数信息用于所述PUSCH的初传和重传；或者
所述每个时域资源分配配置包括两个重复传输次数信息，所述两个重复传输次数信息分别用于所述PUSCH的初传和重传。
在本申请一些实施例中，所述每个时域资源分配配置包括的PUSCH的重复传输次数是预定义的，或者是由所述网络设备配置的。
在本申请一些实施例中，所述每个时域资源分配配置包括的PUSCH的重复传输次数通过无线资源控制RRC信令或系统消息配置。
在本申请一些实施例中，所述时域资源分配列表用于所有的终端设备；或者，
所述时域资源分配列表为用于支持重复传输所述PUSCH的终端设备的专用列表。
在本申请一些实施例中，所述网络设备还包括：
通信单元，用于向所述终端设备发送上行授权，所述上行授权包括第二指示信息，所述第二指示信息用于指示所述多个时域资源分配配置中的目标时域资源分配配置。
在本申请一些实施例中，所述上行授权为随机接入响应RAR中的上行授权，或者所述上行授权为下行控制信息DCI中的上行授权，所述DCI用于调度所述PUSCH的重传。
可选地，在一些实施例中，上述通信单元可以是通信接口或收发器，或者是通信芯片或者片上系统的输入输出接口。上述处理单元可以是一个或多个处理器。
应理解，根据本申请实施例的网络设备500可对应于本申请方法实施例中的网络设备，并且网络设备500中的各个单元的上述和其它操作和/或功能分别为了实现图3所示方法300中网络设备的相应流程，为了简洁，在此不再赘述。
图6是本申请实施例提供的一种通信设备600示意性结构图。图6所示的通信设备600包括处理器610，处理器610可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图6所示，通信设备600还可以包括存储器620。其中，处理器610可以从存储器620中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器620可以是独立于处理器610的一个单独的器件，也可以集成在处理器610中。
可选地，如图6所示，通信设备600还可以包括收发器630，处理器610可以控制该收发器630与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器630可以包括发射机和接收机。收发器630还可以进一步包括天线，天线的数量可以为一个或多个。
可选地，该通信设备600具体可为本申请实施例的网络设备，并且该通信设备600可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该通信设备600具体可为本申请实施例的移动终端/终端设备，并且该通信设备600可以实现本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
图7是本申请实施例的芯片的示意性结构图。图7所示的芯片700包括处理器710， 处理器710可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图7所示，芯片700还可以包括存储器720。其中，处理器710可以从存储器720中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器720可以是独立于处理器710的一个单独的器件，也可以集成在处理器710中。
可选地，该芯片700还可以包括输入接口730。其中，处理器710可以控制该输入接口730与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或数据。
可选地，该芯片700还可以包括输出接口740。其中，处理器710可以控制该输出接口740与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
可选地，该芯片可应用于本申请实施例中的网络设备，并且该芯片可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该芯片可应用于本申请实施例中的移动终端/终端设备，并且该芯片可以实现本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
图8是本申请实施例提供的一种通信系统900的示意性框图。如图8所示，该通信系统900包括终端设备910和网络设备920。
其中，该终端设备910可以用于实现上述方法中由终端设备实现的相应的功能，以及该网络设备920可以用于实现上述方法中由网络设备实现的相应的功能为了简洁，在此不再赘述。
应理解，本申请实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于 这些和任意其它适合类型的存储器。
应理解，上述存储器为示例性但不是限制性说明，例如，本申请实施例中的存储器还可以是静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)等等。也就是说，本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供了一种计算机可读存储介质，用于存储计算机程序。
可选的，该计算机可读存储介质可应用于本申请实施例中的网络设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机可读存储介质可应用于本申请实施例中的移动终端/终端设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序产品，包括计算机程序指令。
可选的，该计算机程序产品可应用于本申请实施例中的网络设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序产品可应用于本申请实施例中的移动终端/终端设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序。
可选的，该计算机程序可应用于本申请实施例中的网络设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序可应用于本申请实施例中的移动终端/终端设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的 目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (66)

  1. 一种传输数据信道的方法，其特征在于，包括：
    终端设备根据物理上行共享信道PUSCH公共配置信息或时域资源分配列表，确定PUSCH的重复传输次数信息，其中，所述PUSCH用于承载随机接入过程中的第三条消息。
  2. 根据权利要求1所述的方法，其特征在于，所述PUSCH公共配置信息包括PUSCH时域资源分配列表信息元素IE，所述PUSCH时域资源分配列表IE包括所述PUSCH的重复传输次数信息。
  3. 根据权利要求2所述的方法，其特征在于，所述PUSCH时域资源分配列表IE包括多个时域资源分配配置，每个时域资源分配配置包括一组时域资源分配信息和PUSCH的重复传输次数信息。
  4. 根据权利要求3所述的方法，其特征在于，所述每个时域资源分配配置包括一个重复传输次数信息，所述一个重复传输次数信息用于所述PUSCH的初传和重传；或者
    所述每个时域资源分配配置包括两个重复传输次数信息，所述两个重复传输次数信息分别用于所述PUSCH的初传和重传。
  5. 根据权利要求3或4所述的方法，其特征在于，所述终端设备根据物理上行共享信道PUSCH公共配置信息或时域资源分配列表，确定PUSCH的重复传输次数信息，包括：
    所述终端设备根据所述PUSCH公共配置信息和网络设备发送的上行授权，确定所述PUSCH的重复传输次数信息，其中，所述上行授权包括第一指示信息，所述第一指示信息用于指示所述多个时域资源分配配置中的目标时域资源分配配置。
  6. 根据权利要求1所述的方法，其特征在于，所述PUSCH公共配置信息的IE中包括所述PUSCH的重复传输次数信息。
  7. 根据权利要求6所述的方法，其特征在于，所述PUSCH公共配置信息的IE中包括一组重复传输次数信息，所述一组重复传输次数信息用于所述PUSCH的初传和重传；或者
    所述PUSCH公共配置信息的IE中包括两组重复传输次数信息，所述两组重复传输次数信息分别用于所述PUSCH的初传和重传。
  8. 根据权利要求1所述的方法，其特征在于，所述时域资源分配列表为缺省PUSCH时域资源分配列表，所述缺省PUSCH时域资源分配列表包括多个时域资源分配配置，每个时域资源分配配置包括一组时域资源分配信息和PUSCH的重复传输次数信息。
  9. 根据权利要求8所述的方法，其特征在于，所述每个时域资源分配配置包括一个重复传输次数信息，所述一个重复传输次数信息用于所述PUSCH的初传和重传；或者
    所述每个时域资源分配配置包括两个重复传输次数信息，所述两个重复传输次数信息分别用于所述PUSCH的初传和重传。
  10. 根据权利要求8或9所述的方法，其特征在于，所述每个时域资源分配配置包括的PUSCH的重复传输次数是预定义的，或者是由网络设备配置的。
  11. 根据权利要求10所述的方法，其特征在于，所述每个时域资源分配配置包括的PUSCH的重复传输次数通过无线资源控制RRC信令或系统消息配置。
  12. 根据权利要求8-11中任一项所述的方法，其特征在于，所述时域资源分配列表用于所有的终端设备；或者，
    所述时域资源分配列表为用于支持重复传输所述PUSCH的终端设备的专用列表。
  13. 根据权利要求8-12中任一项所述的方法，其特征在于，所述终端设备根据物理上行共享信道PUSCH公共配置信息或时域资源分配列表，确定PUSCH的重复传输次数信息，包括：
    所述终端设备根据所述时域资源分配列表和网络设备发送的上行授权，确定所述 PUSCH的重复传输次数信息，其中，所述上行授权包括第二指示信息，所述第二指示信息用于指示所述多个时域资源分配配置中的目标时域资源分配配置。
  14. 根据权利要求5或13所述的方法，其特征在于，所述上行授权为随机接入响应RAR中的上行授权，或者所述上行授权为下行控制信息DCI中的上行授权，所述DCI用于调度所述PUSCH的重传。
  15. 一种传输数据信道的方法，其特征在于，包括：
    网络设备通过物理上行共享信道PUSCH公共配置信息或时域资源分配列表，为终端设备配置PUSCH的重复传输次数信息，其中，所述PUSCH用于承载随机接入过程中的第三条消息。
  16. 根据权利要求15所述的方法，其特征在于，所述PUSCH公共配置信息包括PUSCH时域资源分配列表信息元素IE，所述PUSCH时域资源分配列表IE包括所述PUSCH的重复传输次数信息。
  17. 根据权利要求16所述的方法，其特征在于，所述PUSCH时域资源分配列表IE包括多个时域资源分配配置，每个时域资源分配配置包括一组时域资源分配信息和PUSCH的重复传输次数信息。
  18. 根据权利要求17所述的方法，其特征在于，所述每个时域资源分配配置包括一个重复传输次数信息，所述一个重复传输次数信息用于所述PUSCH的初传和重传；或者
    所述每个时域资源分配配置包括两个重复传输次数信息，所述两个重复传输次数信息分别用于所述PUSCH的初传和重传。
  19. 根据权利要求17或18所述的方法，其特征在于，所述方法还包括：
    所述网络设备向所述终端设备发送上行授权，其中，所述上行授权包括第一指示信息，所述第一指示信息用于指示所述多个时域资源分配配置中的目标时域资源分配配置。
  20. 根据权利要求15所述的方法，其特征在于，所述PUSCH公共配置信息的IE中包括所述PUSCH的重复传输次数信息。
  21. 根据权利要求20所述的方法，其特征在于，所述PUSCH公共配置信息的IE中包括一组重复传输次数信息，所述一组重复传输次数信息用于所述PUSCH的初传和重传；或者
    所述PUSCH公共配置信息的IE中包括两组重复传输次数信息，所述两组重复传输次数信息分别用于所述PUSCH的初传和重传。
  22. 根据权利要求15所述的方法，其特征在于，所述时域资源分配列表为缺省PUSCH时域资源分配列表，所述缺省PUSCH时域资源分配列表包括多个时域资源分配配置，每个时域资源分配配置包括一组时域资源分配信息和PUSCH的重复传输次数信息。
  23. 根据权利要求22所述的方法，其特征在于，所述每个时域资源分配配置包括一个重复传输次数信息，所述一个重复传输次数信息用于所述PUSCH的初传和重传；或者
    所述每个时域资源分配配置包括两个重复传输次数信息，所述两个重复传输次数信息分别用于所述PUSCH的初传和重传。
  24. 根据权利要求22或23所述的方法，其特征在于，所述每个时域资源分配配置包括的PUSCH的重复传输次数是预定义的，或者是由所述网络设备配置的。
  25. 根据权利要求24所述的方法，其特征在于，所述每个时域资源分配配置包括的PUSCH的重复传输次数通过无线资源控制RRC信令或系统消息配置。
  26. 根据权利要求22-25中任一项所述的方法，其特征在于，所述时域资源分配列表用于所有的终端设备；或者，
    所述时域资源分配列表为用于支持重复传输所述PUSCH的终端设备的专用列表。
  27. 根据权利要求22-26中任一项所述的方法，其特征在于，所述方法还包括：
    所述网络设备向所述终端设备发送上行授权，所述上行授权包括第二指示信息，所述第二指示信息用于指示所述多个时域资源分配配置中的目标时域资源分配配置。
  28. 根据权利要求19或27所述的方法，其特征在于，所述上行授权为随机接入响应RAR中的上行授权，或者所述上行授权为下行控制信息DCI中的上行授权，所述DCI用于调度所述PUSCH的重传。
  29. 一种终端设备，其特征在于，包括：
    处理单元，用于根据物理上行共享信道PUSCH公共配置信息或时域资源分配列表，确定PUSCH的重复传输次数信息，其中，所述PUSCH用于承载随机接入过程中的第三条消息。
  30. 根据权利要求29所述的终端设备，其特征在于，所述PUSCH公共配置信息包括PUSCH时域资源分配列表信息元素IE，所述PUSCH时域资源分配列表IE包括所述PUSCH的重复传输次数信息。
  31. 根据权利要求30所述的终端设备，其特征在于，所述PUSCH时域资源分配列表IE包括多个时域资源分配配置，每个时域资源分配配置包括一组时域资源分配信息和PUSCH的重复传输次数信息。
  32. 根据权利要求31所述的终端设备，其特征在于，所述每个时域资源分配配置包括一个重复传输次数信息，所述一个重复传输次数信息用于所述PUSCH的初传和重传；或者
    所述每个时域资源分配配置包括两个重复传输次数信息，所述两个重复传输次数信息分别用于所述PUSCH的初传和重传。
  33. 根据权利要求31或32所述的终端设备，其特征在于，所述处理单元还用于：
    根据所述PUSCH公共配置信息和网络设备发送的上行授权，确定所述PUSCH的重复传输次数信息，其中，所述上行授权包括第一指示信息，所述第一指示信息用于指示所述多个时域资源分配配置中的目标时域资源分配配置。
  34. 根据权利要求29所述的终端设备，其特征在于，所述PUSCH公共配置信息的IE中包括所述PUSCH的重复传输次数信息。
  35. 根据权利要求34所述的终端设备，其特征在于，所述PUSCH公共配置信息的IE中包括一组重复传输次数信息，所述一组重复传输次数信息用于所述PUSCH的初传和重传；或者
    所述PUSCH公共配置信息的IE中包括两组重复传输次数信息，所述两组重复传输次数信息分别用于所述PUSCH的初传和重传。
  36. 根据权利要求29所述的终端设备，其特征在于，所述时域资源分配列表为缺省PUSCH时域资源分配列表，所述缺省PUSCH时域资源分配列表包括多个时域资源分配配置，每个时域资源分配配置包括一组时域资源分配信息和PUSCH的重复传输次数信息。
  37. 根据权利要求36所述的终端设备，其特征在于，所述每个时域资源分配配置包括一个重复传输次数信息，所述一个重复传输次数信息用于所述PUSCH的初传和重传；或者
    所述每个时域资源分配配置包括两个重复传输次数信息，所述两个重复传输次数信息分别用于所述PUSCH的初传和重传。
  38. 根据权利要求36或37所述的终端设备，其特征在于，所述每个时域资源分配配置包括的PUSCH的重复传输次数是预定义的，或者是由网络设备配置的。
  39. 根据权利要求38所述的终端设备，其特征在于，所述每个时域资源分配配置包括的PUSCH的重复传输次数通过无线资源控制RRC信令或系统消息配置。
  40. 根据权利要求36-39中任一项所述的终端设备，其特征在于，所述时域资源分配列表用于所有的终端设备；或者，
    所述时域资源分配列表为用于支持重复传输所述PUSCH的终端设备的专用列表。
  41. 根据权利要求36-40中任一项所述的终端设备，其特征在于，所述处理单元还 用于：
    根据所述时域资源分配列表和网络设备发送的上行授权，确定所述PUSCH的重复传输次数信息，其中，所述上行授权包括第二指示信息，所述第二指示信息用于指示所述多个时域资源分配配置中的目标时域资源分配配置。
  42. 根据权利要求33或41所述的终端设备，其特征在于，所述上行授权为随机接入响应RAR中的上行授权，或者所述上行授权为下行控制信息DCI中的上行授权，所述DCI用于调度所述PUSCH的重传。
  43. 一种网络设备，其特征在于，包括：
    处理单元，用于通过物理上行共享信道PUSCH公共配置信息或时域资源分配列表，为终端设备配置PUSCH的重复传输次数信息，其中，所述PUSCH用于承载随机接入过程中的第三条消息。
  44. 根据权利要求43所述的网络设备，其特征在于，所述PUSCH公共配置信息包括PUSCH时域资源分配列表信息元素IE，所述PUSCH时域资源分配列表IE包括所述PUSCH的重复传输次数信息。
  45. 根据权利要求44所述的网络设备，其特征在于，所述PUSCH时域资源分配列表IE包括多个时域资源分配配置，每个时域资源分配配置包括一组时域资源分配信息和PUSCH的重复传输次数信息。
  46. 根据权利要求45所述的网络设备，其特征在于，所述每个时域资源分配配置包括一个重复传输次数信息，所述一个重复传输次数信息用于所述PUSCH的初传和重传；或者
    所述每个时域资源分配配置包括两个重复传输次数信息，所述两个重复传输次数信息分别用于所述PUSCH的初传和重传。
  47. 根据权利要求45或46所述的网络设备，其特征在于，所述网络设备还包括：
    通信单元，用于向所述终端设备发送上行授权，其中，所述上行授权包括第一指示信息，所述第一指示信息用于指示所述多个时域资源分配配置中的目标时域资源分配配置。
  48. 根据权利要求47所述的网络设备，其特征在于，所述PUSCH公共配置信息的IE中包括所述PUSCH的重复传输次数信息。
  49. 根据权利要求48所述的网络设备，其特征在于，所述PUSCH公共配置信息的IE中包括一组重复传输次数信息，所述一组重复传输次数信息用于所述PUSCH的初传和重传；或者
    所述PUSCH公共配置信息的IE中包括两组重复传输次数信息，所述两组重复传输次数信息分别用于所述PUSCH的初传和重传。
  50. 根据权利要求43所述的网络设备，其特征在于，所述时域资源分配列表为缺省PUSCH时域资源分配列表，所述缺省PUSCH时域资源分配列表包括多个时域资源分配配置，每个时域资源分配配置包括一组时域资源分配信息和PUSCH的重复传输次数信息。
  51. 根据权利要求50所述的网络设备，其特征在于，所述每个时域资源分配配置包括一个重复传输次数信息，所述一个重复传输次数信息用于所述PUSCH的初传和重传；或者
    所述每个时域资源分配配置包括两个重复传输次数信息，所述两个重复传输次数信息分别用于所述PUSCH的初传和重传。
  52. 根据权利要求50或51所述的网络设备，其特征在于，所述每个时域资源分配配置包括的PUSCH的重复传输次数是预定义的，或者是由所述网络设备配置的。
  53. 根据权利要求52所述的网络设备，其特征在于，所述每个时域资源分配配置包括的PUSCH的重复传输次数通过无线资源控制RRC信令或系统消息配置。
  54. 根据权利要求50-53中任一项所述的网络设备，其特征在于，所述时域资源分配列表用于所有的终端设备；或者，
    所述时域资源分配列表为用于支持重复传输所述PUSCH的终端设备的专用列表。
  55. 根据权利要求50-54中任一项所述的网络设备，其特征在于，所述网络设备还包括：
    通信单元，用于向所述终端设备发送上行授权，所述上行授权包括第二指示信息，所述第二指示信息用于指示所述多个时域资源分配配置中的目标时域资源分配配置。
  56. 根据权利要求47或55所述的网络设备，其特征在于，所述上行授权为随机接入响应RAR中的上行授权，或者所述上行授权为下行控制信息DCI中的上行授权，所述DCI用于调度所述PUSCH的重传。
  57. 一种终端设备，其特征在于，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求1至14中任一项所述的方法。
  58. 一种网络设备，其特征在于，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求15至28中任一项所述的方法。
  59. 一种芯片，其特征在于，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1至14中任一项所述的方法。
  60. 一种芯片，其特征在于，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求15至28中任一项所述的方法。
  61. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求1至14中任一项所述的方法。
  62. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求15至28中任一项所述的方法。
  63. 一种计算机程序产品，其特征在于，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求1至14中任一项所述的方法。
  64. 一种计算机程序产品，其特征在于，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求15至28中任一项所述的方法。
  65. 一种计算机程序，其特征在于，所述计算机程序使得计算机执行如权利要求1至14中任一项所述的方法。
  66. 一种计算机程序，其特征在于，所述计算机程序使得计算机执行如权利要求14至28中任一项所述的方法。
PCT/CN2021/078883 2021-03-03 2021-03-03 传输数据信道的方法、终端设备和网络设备 WO2022183406A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CN202180080880.6A CN116569642A (zh) 2021-03-03 2021-03-03 传输数据信道的方法、终端设备和网络设备
EP21928495.7A EP4271108A4 (en) 2021-03-03 2021-03-03 METHOD FOR TRANSMITTING A DATA CHANNEL, TERMINAL DEVICE AND NETWORK DEVICE
PCT/CN2021/078883 WO2022183406A1 (zh) 2021-03-03 2021-03-03 传输数据信道的方法、终端设备和网络设备
US18/361,765 US20240023095A1 (en) 2021-03-03 2023-07-28 Method for transmitting data channel, terminal device and network device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/078883 WO2022183406A1 (zh) 2021-03-03 2021-03-03 传输数据信道的方法、终端设备和网络设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/361,765 Continuation US20240023095A1 (en) 2021-03-03 2023-07-28 Method for transmitting data channel, terminal device and network device

Publications (1)

Publication Number Publication Date
WO2022183406A1 true WO2022183406A1 (zh) 2022-09-09

Family

ID=83153899

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/078883 WO2022183406A1 (zh) 2021-03-03 2021-03-03 传输数据信道的方法、终端设备和网络设备

Country Status (4)

Country Link
US (1) US20240023095A1 (zh)
EP (1) EP4271108A4 (zh)
CN (1) CN116569642A (zh)
WO (1) WO2022183406A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024060976A1 (zh) * 2022-09-23 2024-03-28 华为技术有限公司 卫星通信方法及装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112040558A (zh) * 2020-08-07 2020-12-04 中国信息通信研究院 一种随机接入过程中的上行数据传输方法和设备
EP3780871A1 (en) * 2019-08-16 2021-02-17 Comcast Cable Communications LLC Random access procedures using repetition

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AR114402A1 (es) * 2018-03-02 2020-09-02 Ericsson Telefon Ab L M Asignación de recursos del dominio de tiempo para la transmisión por el canal físico compartido de enlace ascendente

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3780871A1 (en) * 2019-08-16 2021-02-17 Comcast Cable Communications LLC Random access procedures using repetition
CN112040558A (zh) * 2020-08-07 2020-12-04 中国信息通信研究院 一种随机接入过程中的上行数据传输方法和设备

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ETRI: "PUSCH coverage enhancement", 3GPP DRAFT; R1-2101082, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20210125 - 20210205, 19 January 2021 (2021-01-19), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051971351 *
See also references of EP4271108A4 *
XIAOMI: "Discussion on Type A PUSCH repetition for Msg3", 3GPP DRAFT; R1-2101130, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20210125 - 20210205, 18 January 2021 (2021-01-18), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051970684 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024060976A1 (zh) * 2022-09-23 2024-03-28 华为技术有限公司 卫星通信方法及装置

Also Published As

Publication number Publication date
EP4271108A1 (en) 2023-11-01
US20240023095A1 (en) 2024-01-18
EP4271108A4 (en) 2024-02-28
CN116569642A (zh) 2023-08-08

Similar Documents

Publication Publication Date Title
WO2020063828A1 (zh) 一种随机接入的方法和通信装置
WO2021168661A1 (zh) 信息传输方法、终端设备和网络设备
WO2020248259A1 (zh) 随机接入方法、终端设备和网络设备
US20240040627A1 (en) Wireless comminication method, and electronic device
US20240334359A1 (en) Method for timing advance maintenance in uplink synchronization, terminal device, and chip
US20240023095A1 (en) Method for transmitting data channel, terminal device and network device
WO2022067519A1 (zh) 随机接入方法和终端设备
WO2020020352A1 (zh) 随机接入方法、终端设备和网络设备
WO2022246588A1 (zh) 无线通信的方法、终端设备和网络设备
JP7456551B2 (ja) 信号の送受信方法、装置及び通信システム
WO2022067614A1 (zh) 无线通信方法、终端设备和网络设备
WO2020206658A1 (zh) 无线通信方法、终端设备和网络设备
WO2023130473A1 (zh) 无线通信的方法、终端设备和网络设备
WO2024011396A1 (zh) 无线通信的方法、终端设备和网络设备
US20240080817A1 (en) Wireless communication method, terminal device, and network device
US20230422240A1 (en) Wireless communication method, terminal device, and network device
WO2022150991A1 (zh) 无线通信的方法和设备
WO2024040598A1 (zh) 无线通信的方法和终端设备
US11395350B2 (en) Random access method, terminal device, and network device
WO2022233033A1 (zh) 无线通信的方法及设备
WO2022036696A1 (zh) 无线通信方法、终端设备和网络设备
US20240365401A1 (en) Wireless communication method and terminal device
WO2023130467A1 (zh) 无线通信的方法、终端设备和网络设备
WO2022027669A1 (zh) 传输反馈信息的方法、终端设备和网络设备
WO2022110178A1 (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: 21928495

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202180080880.6

Country of ref document: CN

ENP Entry into the national phase

Ref document number: 2021928495

Country of ref document: EP

Effective date: 20230725

NENP Non-entry into the national phase

Ref country code: DE