CN116058029A - Channel resource determining method and terminal equipment - Google Patents

Channel resource determining method and terminal equipment Download PDF

Info

Publication number
CN116058029A
CN116058029A CN202080104361.4A CN202080104361A CN116058029A CN 116058029 A CN116058029 A CN 116058029A CN 202080104361 A CN202080104361 A CN 202080104361A CN 116058029 A CN116058029 A CN 116058029A
Authority
CN
China
Prior art keywords
order
pusch
indexes
resources
preamble
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202080104361.4A
Other languages
Chinese (zh)
Inventor
贺传峰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Publication of CN116058029A publication Critical patent/CN116058029A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/06Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation

Landscapes

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

Abstract

The application relates to a method for determining channel resources and terminal equipment. The method for determining the channel resources comprises the following steps: the terminal equipment determines a plurality of Physical Uplink Shared Channel (PUSCH) resources, wherein the time domain resources of the plurality of PUSCH resources are different, the plurality of PUSCH resources are used for repeated transmission of the PUSCH, and the PUSCH belongs to a message A of a type 2 random access process. According to the embodiment of the application, the plurality of PUSCH resources are mapped to different time domain resources, so that the repeated transmission of the PUSCH is facilitated.

Description

Channel resource determining method and terminal equipment Technical Field
The present invention relates to the field of communications, and in particular, to a method and a terminal device for determining channel resources.
Background
The NR (New Radio) system is designed mainly for supporting eMBB (Enhanced Mobile Broadband) services. Its main technology is to meet the needs of high rate, high spectral efficiency, large bandwidth. In fact, there are many different traffic types besides eMBB, such as sensor networks, video monitoring, wearable, etc., which have different requirements from the eMBB traffic in terms of rate, bandwidth, power consumption, cost, etc. The capabilities of terminals supporting these services are reduced compared to terminals supporting eMBB, such as reduced supported bandwidth, relaxed processing time, reduced antenna count, etc. There is a need to optimize NR systems for these services and corresponding low-capability terminals, such systems being called NR-light (light NR) systems. In LTE technology, similar systems have been designed to support large connection count, low power consumption, low cost terminals, such as MTC (Machine Type Communication), NB-IoT (Narrow Band Internet of Things ). In NR systems, it is desirable to introduce similar techniques for better supporting other traffic types than eMBB traffic using NR techniques. For such low complexity, low cost terminals, one of the optimizations that need to be made is coverage enhancement for improving the downlink and uplink coverage of such terminals.
In the Rel-15NR technology, RACH (Random Access Channel ) resources configured for access UEs (User Equipment) are defined, including 256 configurations. RACH resource configuration information used by the cell is indicated in a system message to the accessed UE. The RACH (random access) procedure in the NR system does not support repeated transmission of PRACH (Physical Random Access Channel ) nor repeated transmission of MsgA (message a) of the two-step random access (2-step RACH) procedure. In the NR-light system, it is also necessary to consider how to implement the repeated transmission of MsgA.
Disclosure of Invention
The embodiment of the application provides a method for determining channel resources and terminal equipment, which can map a plurality of PUSCH resources to different time domain resources, is favorable for realizing repeated transmission of the PUSCH and improves the transmission reliability of a message A in a random access process.
The embodiment of the application provides a method for determining channel resources, which comprises the following steps:
the terminal equipment determines a plurality of Physical Uplink Shared Channel (PUSCH) resources, wherein the time domain resources of the plurality of PUSCH resources are different, the plurality of PUSCH resources are used for repeated transmission of the PUSCH, and the PUSCH belongs to a message A of a type 2 random access process.
The embodiment of the application provides a terminal device, which comprises:
and the processing unit is used for determining a plurality of Physical Uplink Shared Channel (PUSCH) resources, wherein the time domain resources of the plurality of PUSCH resources are different, the plurality of PUSCH resources are used for repeated transmission of the PUSCH, and the PUSCH belongs to the message A of the type 2 random access process.
The embodiment of the application provides terminal equipment, which comprises a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory so as to enable the terminal equipment to execute the method for determining the channel resources.
The embodiment of the application provides a chip for realizing the method for determining channel resources. Specifically, the chip includes: and a processor for calling and running the computer program from the memory, so that the device mounted with the chip executes the above-mentioned channel resource determining method.
The embodiments of the present application provide a computer-readable storage medium storing a computer program that, when executed by a device, causes the device to perform the above-described method for determining channel resources.
Embodiments of the present application provide a computer program product including computer program instructions for causing a computer to perform the above-described method for determining channel resources.
The embodiments of the present application provide a computer program that, when executed on a computer, causes the computer to perform the above-described method for determining channel resources.
According to the method and the device, the PUSCH resources in the plurality of messages A are mapped to different time domain resources, so that repeated transmission of the PUSCH is facilitated, and the transmission reliability of the messages A in the random access process is improved.
Drawings
Fig. 1 is a schematic diagram of an application scenario according to an embodiment of the present application.
Fig. 2 is a schematic diagram of PRACH frequency domain location.
Fig. 3 is a schematic diagram of SSB and RO mapping.
Fig. 4 is a schematic diagram of a two-step RACH procedure.
Fig. 5 is a schematic diagram of the relative relationship between POs and associated ROs in time-frequency position.
Fig. 6 is a schematic diagram of a configuration of a PO.
Fig. 7 is a schematic diagram of a mapping relationship between a preamble and a PRU.
Fig. 8 is a schematic flow chart diagram of a method of determining channel resources according to an embodiment of the present application.
Fig. 9 is a schematic diagram of PUSCH resources.
Fig. 10 is a schematic diagram of the mapping relation in example 1.
Fig. 11 is a schematic diagram of PUSCH resources in example 2.
Fig. 12a to 12b are schematic diagrams of the mapping relationship in example 2.
Fig. 13 is a schematic block diagram of a terminal device according to an embodiment of the present application.
Fig. 14 is a schematic block diagram of a communication device according to an embodiment of the present application.
Fig. 15 is a schematic block diagram of a chip according to an embodiment of the present application.
Fig. 16 is a schematic block diagram of a communication system according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
The technical solution of the embodiment of the application can be applied to various communication systems, for example: global system for mobile communications (Global System of Mobile communication, GSM), code division multiple access (Code Division Multiple Access, CDMA) system, wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, general packet Radio service (General Packet Radio Service, GPRS), long term evolution (Long Term Evolution, LTE) system, advanced long term evolution (Advanced long term evolution, LTE-a) system, new Radio (NR) system, evolved system of NR system, LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum, NR-U) system on unlicensed spectrum, non-terrestrial communication network (Non-Terrestrial Networks, NTN) system, universal mobile communication system (Universal Mobile Telecommunication System, UMTS), wireless local area network (Wireless Local Area Networks, WLAN), wireless fidelity (Wireless Fidelity, wiFi), fifth Generation communication (5 th-Generation, 5G) system, or other communication system, etc.
Generally, the number of connections supported by the conventional communication system is limited and easy to implement, however, with the development of communication technology, the mobile communication system will support not only conventional communication but also, for example, device-to-Device (D2D) communication, machine-to-machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), inter-vehicle (Vehicle to Vehicle, V2V) communication, or internet of vehicles (Vehicle to everything, V2X) communication, etc., and the embodiments of the present application may also be applied to these communication systems.
Optionally, the communication system in the embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, and a Stand Alone (SA) fabric scenario.
Optionally, the communication system in the embodiments of the present application may be applied to unlicensed spectrum, where unlicensed spectrum may also be considered as shared spectrum; alternatively, the communication system in the embodiments of the present application may also be applied to licensed spectrum, where licensed spectrum may also be considered as non-shared spectrum.
Embodiments herein describe various embodiments in connection with network devices and terminal devices, where a terminal device may also be referred to as a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, a user equipment, or the like.
The terminal device may be a Station (ST) in a WLAN, may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle device, a wearable device, a terminal device in a next generation communication system such as an NR network, or a terminal device in a future evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.
In embodiments of the present application, the terminal device may be deployed on land, including indoor or outdoor, hand-held, wearable or vehicle-mounted; can also be deployed on the water surface (such as ships, etc.); but may also be deployed in the air (e.g., on aircraft, balloon, satellite, etc.).
In the embodiment of the present application, the terminal device may be a Mobile Phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an augmented Reality (Augmented Reality, AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in unmanned driving (self driving), a wireless terminal device in remote medical (remote medical), a wireless terminal device in smart grid (smart grid), a wireless terminal device in transportation security (transportation safety), a wireless terminal device in smart city (smart city), or a wireless terminal device in smart home (smart home), and the like.
By way of example, and not limitation, in embodiments of the present application, the terminal device may also be a wearable device. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wear by applying wearable technology and developing wearable devices, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.
In this embodiment of the present application, the network device may be a device for communicating with a mobile device, where the network device may be an Access Point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, a relay station or an Access Point, a vehicle device, a wearable device, and a network device (gNB) in an NR network, or a network device in a PLMN network for future evolution, or a network device in an NTN network, etc.
By way of example and not limitation, in embodiments of the present application, a network device may have a mobile nature, e.g., the network device may be a mobile device. Alternatively, the network device may be a satellite, a balloon station. For example, the satellite may be a Low Earth Orbit (LEO) satellite, a medium earth orbit (medium earth orbit, MEO) satellite, a geosynchronous orbit (geostationary earth orbit, GEO) satellite, a high elliptical orbit (High Elliptical Orbit, HEO) satellite, or the like. Alternatively, the network device may be a base station disposed on land, in a water area, or the like.
In this embodiment of the present application, a network device may provide a service for a cell, where a terminal device communicates with the network device through a transmission resource (e.g., a frequency domain resource, or a spectrum resource) used by the cell, where the cell may be a cell corresponding to a network device (e.g., a base station), and the cell may belong to a macro base station, or may belong to a base station corresponding to a Small cell (Small cell), where the Small cell may include: urban cells (Metro cells), micro cells (Micro cells), pico cells (Pico cells), femto cells (Femto cells) and the like, and the small cells have the characteristics of small coverage area and low transmitting power and are suitable for providing high-rate data transmission services.
Fig. 1 schematically illustrates a communication system 100. The communication system comprises one network device 110 and two terminal devices 120. Alternatively, the communication system 100 may include a plurality of network devices 110, and the coverage area of each network device 110 may include other numbers of terminal devices 120, which are not limited in this embodiment of the present application.
Optionally, the communication system 100 may further include other network entities such as a mobility management entity (Mobility Management Entity, MME), an access and mobility management function (Access and Mobility Management Function, AMF), and the embodiment of the present application is not limited thereto.
The network device may further include an access network device and a core network device. I.e. the wireless communication system further comprises a plurality of core networks for communicating with the access network devices. The access network device may be a long-term evolution (LTE) system, a next-generation (NR) system, or an evolved base station (evolutional node B, abbreviated as eNB or e-NodeB) macro base station, a micro base station (also called "small base station"), a pico base station, an Access Point (AP), a transmission point (transmission point, TP), a new generation base station (new generation Node B, gNodeB), or the like in an licensed assisted access long-term evolution (LAA-LTE) system.
It should be understood that a device having a communication function in a network/system in an embodiment of the present application may be referred to as a communication device. Taking the communication system shown in fig. 1 as an example, the communication device may include a network device and a terminal device with a communication function, where the network device and the terminal device may be specific devices in the embodiments of the present application, and are not described herein again; the communication device may also include other devices in the communication system, such as a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.
It should be understood that the terms "system" and "network" are used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.
It should be understood that, in the embodiments of the present application, the "indication" may be a direct indication, an indirect indication, or an indication having an association relationship. For example, a indicates B, which may mean that a indicates B directly, e.g., B may be obtained by a; it may also indicate that a indicates B indirectly, e.g. a indicates C, B may be obtained by C; it may also be indicated that there is an association between a and B.
In the description of the embodiments of the present application, the term "corresponding" may indicate that there is a direct correspondence or an indirect correspondence between the two, or may indicate that there is an association between the two, or may indicate a relationship between the two and the indicated, configured, or the like.
In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following description is given of related technologies of the embodiments of the present application, and the following related technologies may be optionally combined with the technical solutions of the embodiments of the present application as an alternative, which all belong to the protection scope of the embodiments of the present application.
Each RACH resource configuration indicated by the network to the UE may include a preamble format (preamble format), a period, a radio frame offset, a subframe number within a radio frame, a starting symbol within a subframe, a number of PRACH slots within a subframe, a number of PRACH occasions within a PRACH slot, a PRACH occasion duration, and the like. From these indicated information, time, frequency, code information of the PRACH resources may be determined. As shown in table 1 below, PRACH configuration index (Configuration Index) =86, which indicates the preamble format, and the radio frame, subframe, starting symbol, time length, etc. where the PRACH occasion is located.
TABLE 1 examples of random Access configuration
Figure PCTCN2020110152-APPB-000001
In addition to the time domain resource location of the RACH resource, the frequency domain resource location of the RACH resource may be indicated by high-level signaling such as parameters msg1-FrequencyStart (message 1 frequency start) and msg1-FDM (message 1 frequency division multiplexing) in RACH-ConfigGeneric (RACH configuration generic) signaling. Wherein msg1-FrequencyStart is used to determine an offset of a starting position of an RB (Resource Block) of a PRACH occipital 0 (wherein PRACH occipital is a PRACH occasion (physical random access channel occasion), which may be abbreviated as RO) with respect to a frequency domain starting position (i.e., BWP 0) of an uplink common BWP (Bandwidth Part), i.e., determine a frequency domain starting position of a RACH Resource. The msg1-FDM can be {1,2,4,8}, and is used for determining the number of frequency domain PRACCASION. The number of RBs occupied by the PRACH on the traffic channel may be indicated by a PRACH-root sequence index (PRACH root sequence index) indicating a preamble (preamble or referred to as preamble, random access preamble, etc.), and then the number of RBs occupied by the PUSCH is determined together according to Δfra (subcarrier spacing mapping the preamble sequence to the frequency domain), where the PRACH frequency domain location is shown in fig. 2, and msg 1-fdm=8.
For the UE, the system message may indicate RACH resource configuration, and the system message may also indicate an association relationship between SSB and PRACH resources, so that the UE may determine RACH resources that may be used by the UE according to the detected SSB and the association relationship. Each SSB may be associated with one or more PRACH occasions or with multiple contention-based preambles (Contention Based preambles). I.e. each SSB index (index) may be associated with a specific part of the resources in the RACH resource configuration indicated in the system message.
The higher layer configures N (SSB-perRACH-allocation) SSBs with parameters such as SSB-perRACH-allocation (SSB per PRACH Occasion) and CB-preablesps (contention-based preamble per SSB) associated with one PRACH Occasion (occalasion), and the number of contention-based preambles (CB-preablesps b) per SSB on each active PRACH occalasion.
If N <1, one SSB maps to 1/N consecutive active PRACH occalations. For example: n=1/4, then one SSB maps 4 PRACH occlusions, and R consecutive indexed preambles map to SSB N,0< =n-1, each valid PRACH ocction starting with a preamble index of 0.
If N>=1, r consecutively indexed preamble maps to SSB n,0<=n<=n-1, each effective PRACH occaThe version is indexed from the preamble
Figure PCTCN2020110152-APPB-000002
Starting. For example: n=2 and,
Figure PCTCN2020110152-APPB-000003
then two SSBs map 1 PRACH occalation, then n=0, 1 for both SSBs n. When n=0, the preamble index of SSB 0 starts from 0; when n=1, the preamble index at SSB 1 starts at 32. The preamble index on SSB 0 is 0-31, and the preamble index on SSB 1 is 32-configured contention preamble-1. One effective PRACH ocvision corresponds to the whole number of contention preambles, while one effective PRACH ocvision covers two SSBs, so that the two SSBs each occupy part of the preamble, and N <1 are different. Wherein the method comprises the steps of
Figure PCTCN2020110152-APPB-000004
May be configured by total numberofra-preamps (total number of random access Preambles) and is an integer multiple of N.
The relevant signaling is exemplified as follows:
ssb-perRACH-OccasionAndCB-PreamblesPerSSB CHOICE{
oneFourth ENUMERATED{n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64},
this signaling indicates that one SSB is associated with 4 PRACH occasions, n4 indicates that one SSB is associated with 4 contention-based preambles (Contention Based preambles), and so on. The total number of Contention Based preambles in one PRACH Occasion is CB-preablessperssb max (1, ssb-perRACH-allocation).
The mapping of SSB to PRACH occalation follows the following order:
first, the order of preamble indexes in a PRACH occalation is incremented;
second, the frequency resource index order of the frequency multiplexed PRACH occalation is incremented;
third, the order of the time domain resource indexes of the time domain multiplexing PRACH occalasion within the PRACH slot is incremental;
fourth, the order of PRACH slot indexes is incremental.
The mapping relationship between the two is illustrated by way of example. For example, the number of SSBs is 8 (number: 0-7), msg 1-FDM=4 (indicating the number of frequency domain PRACACversion). SSB-perRACH-Occasion=1/4, and a schematic diagram of SSB-PRACH occasing mapping is shown in fig. 3.
The delay overhead of the four-step RACH procedure is relatively large, which is unsuitable for the low-delay high-reliability scenario in 5G. In the standardized process of NR, considering the characteristics of low-delay and high-reliability related services, a two-step RACH process (also called a Type 2random access process, type-2random access procedure) is introduced into R16, and compared with a four-step RACH process, the access delay can be reduced. The two-step RACH procedure is shown in fig. 4.
In the two-step RACH procedure, simply stated, it is equivalent to combining the first and third steps of the four-step RACH procedure into the first step of the two-step RACH procedure, and the UE transmits Msg a. The second and fourth steps of the four-step RACH procedure are combined into the second step of the two-step RACH procedure, and the base station replies Msg B. For the first step of the two-step RACH, MSG a includes preamble and PUSCH (Physical Uplink Shared Channel ) parts, and MSG B includes PDCCH (Physical Downlink Control Channel ) and PDSCH (Physical Downlink Shared Channel, physical downlink shared channel). For Msg a, the UE needs to send a Preamble and a PUSCH, where the RO where the Preamble is located is the same as the four-step RACH procedure, and by configuring the network, the RO of the UE may be shared with the RO of the four-step RACH or may be configured separately. The time-frequency resource where the PUSCH is located is called PO (PUSCH timing). One PO may contain multiple PRUs (PUSCH Resource Unit, PUSCH resource elements). One PRU may contain PUSCH resources (resource) and DMRS (Demodulation Reference Signal ). The DMRS includes a DMRS Port (Port) and a DMRS sequence (sequence) (for OFDMA (Orthogonal Frequency Division Multiple Access, orthogonal frequency division multiple access)). The PO may also be configured through a network, with the same period as the RO, and associated therewith. For example, as shown in fig. 5, the relative relationship between the POs and the associated RO at the time-frequency location is network configured.
An example of a configuration parameter for a PO is as follows:
MCS (Modulation and Coding Scheme, modulation and coding strategy)/TBS (Transport Block Set, set of transport blocks);
the frequency domain origin (2 RBs in the following figure) of the PO within the activated BWP (Bandwidth Part);
the number of RBs (Resource blocks) of PUSCH (4 RBs in fig. 6);
guard period (1 symbol in fig. 6) between POs;
the start symbol of the first PO in the slot and the number of symbols each PO contains (s=2, l=3 in fig. 6);
guard band (RB) between POs (1 RB in fig. 6);
the number of frequency-divided POs (4 in FIG. 6);
the number of PUSCH slots (slots) (2 in fig. 6);
the number of POs in each PUSCH slot (3 in fig. 6).
The Preamble in one PRACH slot (slot) has a mapping relationship with the PRU in one PO slot (slot), and the mapping relationship between the Preamble and the PRU can be one-to-one or many-to-one. Illustratively, the order of mapping is as follows:
within the PRACH slot, the sequence of a set of consecutive preambles is:
first, the order of preamble indexes in a PRACH occalation is incremented;
second, the frequency resource index order of the frequency multiplexed PRACH occalation is incremented;
Third, the order of the time domain resource indexes of the time domain multiplexing PRACH occalasion within the PRACH slot is incremental;
fourth, the order of PRACH slot indexes is incremental.
Wherein every M (M > =1) consecutive PRACH preples can be mapped to a valid PRU in the following order:
first, the frequency resource index order of the frequency multiplexed POs is incremented;
secondly, the DMRS resource index sequence is increased in the PO, wherein the DMRS resource indexes are ordered according to the ascending sequence of the DMRS port indexes firstly and then according to the ascending sequence of the DMRS sequence indexes;
thirdly, the time domain resource index sequence of the time division PO is increased in an increasing way in the PUSCH slot;
fourth, the order of PUSCH slot indexes is incremental.
An example of the above-described mapping relationship is shown in fig. 7: there are 4 POs in the frequency domain, and four DMRS in each PO. The DMRS resource index order is incremented within the PO. Mapping the preamble to a first DMRS resource in the PO; the preambles 32-33 are mapped to DMRS #0 of PO #0, the preambles 34-35 are mapped to DMRS #0 of PO #1, the preambles 36-37 are mapped to DMRS #0 of PO #2, and the preambles 38-39 are mapped to DMRS #0 of PO # 3. The preamble is then mapped to the next DMRS resource within the PO: the preambles 40-41 are mapped to DMRS #1 of PO #0, the preambles 42-43 are mapped to DMRS #1 of PO #1, the preambles 44-45 are mapped to DMRS #1 of PO #2, and the preambles 46-47 are mapped to DMRS #1 of PO # 3. And by analogy, after finishing mapping the DMRS resources in the PO of the same frequency domain, if the index to be mapped is still available, mapping the preamble to the PO of different time domains.
After transmitting Msg a, the UE needs to monitor Msg B for a time window. Also, the MsgA may not be successfully received by the base station. If the UE does not receive Msg B within the time window, it will retransmit Msg a.
In one scenario, PRACH repetition transmission may be performed, for example, in an MTC (Machine-Type Communication, machine type communication) system. In the MTC system, uplink coverage enhancement is performed for the MTC terminal. Wherein the transmission of the PRACH supports repeated transmissions. The network configures up to 4 sets of RACH configuration parameters for the MTC terminal, corresponding to 4 coverage levels (coverage levels) respectively. And the MTC terminal determines the coverage grade of the MTC terminal according to the measured RSRP (Reference Signal Receiving Power, reference signal received power) and the threshold of the network configuration, and selects the RACH configuration parameter corresponding to the coverage grade. The RACH configuration parameters include PRACH frequency domain offset, number of repeated transmission of PRACH, starting subframe of repeated transmission of PRACH, frequency hopping parameters of PRACH frequency domain resources, etc.
And obtaining a subframe set where the PRACH resource is located according to the time domain resource of the RACH resource configured by the high layer. And determining a PRACH transmission starting subframe in a subframe set where PRACH resources are located according to the PRACH repeated transmission times in the RACH configuration parameters and the PRACH repeated transmission starting subframe. When the MTC terminal needs to initiate the RACH procedure, repeated transmission of the PRACH starts from the starting subframe that is closest in time.
Since the RACH procedure in the NR system does not support repeated transmission of PRACH, nor repeated transmission of MsgA for the two-step random access (2-step RACH) procedure. If uplink coverage enhancement is considered in the NR-light system, the repeated transmission of MsgA is introduced, and the mapping relation between PRACH and PUSCH is also required to be considered, so that the realization of the repeated transmission of PRACH is ensured.
The method and the device can determine that a plurality of PUSCH resources with different time domains are used for repeated transmission of the PUSCH.
Fig. 8 is a schematic flow chart diagram of a method 200 of determining channel resources according to an embodiment of the present application. The method may alternatively be applied to the system shown in fig. 1, but is not limited thereto. The method includes at least some of the following.
S210, the terminal equipment determines a plurality of Physical Uplink Shared Channel (PUSCH) resources, wherein the time domain resources of the plurality of PUSCH resources are different, the plurality of PUSCH resources are used for repeated transmission of the PUSCH, and the PUSCH belongs to a message A of a type 2 random access process.
In the embodiment of the present application, the type 2 random access procedure may also be referred to as a two-step random access procedure. Referring to fig. 4, in the type 2 random access procedure, the terminal device transmits a message a (step 1), which may include a preamble and PUSCH, to the network device. The network device may acknowledge message B (step 2), which may include PDCCH and PDSCH, to the terminal device. The terminal equipment can determine the PUSCH resources in a plurality of messages A needing to be repeatedly transmitted, the time domain resources of the plurality of PUSCH resources are different, and the plurality of PUSCH resources can be used for the repeated transmission of the PUSCH, so that the repeated transmission of the messages A is realized. In this embodiment, before detecting the response of the network device, for example, the base station, the terminal device may repeatedly transmit the message a several times, and then detect the response of the base station. Therefore, the transmission reliability of the message a can be improved.
Optionally, in the embodiment of the present application, the time domain resources of PUSCH occasions PO where the PUSCH is repeatedly transmitted are different.
Optionally, in the embodiment of the present application, the PUSCH resource and the preamble have a mapping relationship.
Optionally, in an embodiment of the present application, the method further includes: and mapping N continuous preambles to the PUSCH resources according to the sequence of the time domain resource indexes, wherein N is a positive integer, namely N is an integer greater than or equal to 1.
Illustratively, the N consecutive preambles may be preambles that the UE may select when sending message a.
Optionally, in a mode one of the embodiments of the present application, the order of the time domain resource indexes includes:
the order of the time domain resource indexes of the time division POs within the PUSCH slots is incremental.
Optionally, in a first mode of the embodiment of the present application, the mapping order further includes at least one of:
the order of PUSCH slot indexes is incremental;
the order of the frequency resource indexes of the frequency multiplexed POs is incremented;
the order of demodulation reference signal DMRS resource indexes within the PO is incremental.
In one example of the first aspect, N consecutive preambles are mapped to PUSCH resources, specifically may be mapped sequentially in the following order:
(1) The order of the time domain resource indexes of the time division POs within the PUSCH slots is incremental.
(2) The order of PUSCH slot indexes is incremental.
(3) The order of the frequency resource indexes of the frequency multiplexed POs is incremented.
(4) The order of demodulation reference signal DMRS resource indexes within the PO is incremental.
Alternatively, the order of (2) to (4) in this example may be changed. For example, the order of (2), (4), and (3), the order of (3), (2), and (4), the order of (3), (4), and (2), the order of (4), (2), and (3), or the order of (4), (3), and (2). Furthermore, if the number of indexes to be mapped is small, the mapping may be performed in the above-described previous order. For example, if the index can already be mapped according to (1), the mapping may not continue according to (2), (3) or (4). For another example, if the index can already be mapped according to (1), (2), the mapping may not be continued according to (3) or (4).
In a specific example, see fig. 9, there are two PUSCH slots, each PUSCH slot including 4 POs, where po#0 and po#1 are time-domain distinct POs, and po#2 and po#3 are time-domain distinct POs. 2 DMRSs are included in each PO. 10 consecutive preambles (e.g., preamble 1 to preamble 10) need to be mapped to PUSCH resources.
For example, it is assumed that preambles are mapped to PUSCH resources in the order of (1), (2), (3), and (4) in the above example in order. Specifically, in the first slot, preamble 1 is mapped to dmrs#0 of po#0, and in the second slot, preamble 2 is mapped to dmrs#0 of po#1; in the second slot, dmrs#0 of preamble 3 to po#0, dmrs#0 of preamble 4 to po#1. Subsequently, in the first slot, preamble 5 may be mapped to dmrs#0 of po#2, and preamble 6 may be mapped to dmrs#0 of po#3; in the second slot, preamble 7 may be mapped to dmrs#0 of po#2 and preamble 8 may be mapped to dmrs#0 of po#3. Then, in the first slot, preamble 9 is mapped to dmrs#1 of po#0, and preamble 10 is mapped to dmrs#1 of po#1.
For another example, it is assumed that preambles are mapped to PUSCH resources in the order of (1), (2), (4), and (3) in the above example in order. Specifically, in the first slot, preamble 1 is mapped to dmrs#0 of po#0, and preamble 2 is mapped to dmrs#0 of po#1; in the second slot, dmrs#0 of preamble 3 to po#0, dmrs#0 of preamble 4 to po#1. Subsequently, in the first slot, preamble 5 may be mapped to dmrs#1 of po#0, and preamble 6 may be mapped to dmrs#1 of po#1; in the second slot, preamble 7 may be mapped to DMRS #1 of PO #0 and preamble 8 may be mapped to DMRS #1 of PO #1. Then, in the first slot, preamble 9 is mapped to dmrs#0 of po#2, and preamble 10 is mapped to dmrs#0 of po#3.
For another example, it is assumed that preambles are mapped to PUSCH resources in the order of (1), (3), (2), and (4) in the above example in order. Specifically, in the first slot, preamble 1 is mapped to dmrs#0 of po#0, and preamble 2 is mapped to dmrs#0 of po#1; dmrs#0 of preamble 3 to po#2, dmrs#0 of preamble 4 to po#3. Subsequently, in the second slot, preamble 5 may be mapped to dmrs#0 of po#0, preamble 6 may be mapped to dmrs#0 of po#1, preamble 7 may be mapped to dmrs#0 of po#2, and preamble 8 may be mapped to dmrs#0 of po#3. Then, in the first slot, preamble 9 is mapped to dmrs#1 of po#0, and preamble 10 is mapped to dmrs#1 of po#1.
For another example, it is assumed that preambles are mapped to PUSCH resources in the order of (1), (3), (4), and (2) in the above example in order. Specifically, in the first slot, preamble 1 is mapped to dmrs#0 of po#0, and preamble 2 is mapped to dmrs#0 of po#1; dmrs#0 of preamble 3 to po#2, dmrs#0 of preamble 4 to po#3. Subsequently, in the first slot, preamble 5 may be mapped to dmrs#1 of po#0, preamble 6 may be mapped to dmrs#1 of po#1, preamble 7 may be mapped to dmrs#1 of po#2, and preamble 8 may be mapped to dmrs#1 of po#3. Then, in the second slot, preamble 9 is mapped to dmrs#0 of po#0 and preamble 10 is mapped to dmrs#0 of po#1.
Optionally, in the second mode of the embodiment of the present application, the sequence of the time domain resource indexes includes:
the order of PUSCH slot indexes is incremental.
Optionally, in a second mode of the embodiment of the present application, the mapping order further includes at least one of the following:
the order of the time domain resource indexes of the time division POs is incremental in the PUSCH time slot;
the order of the frequency resource indexes of the frequency multiplexed POs is incremented;
the order of DMRS resource indexes within the PO is incremental.
In one example of the second mode, N consecutive preambles are mapped to PUSCH resources, specifically, may be mapped sequentially in the following order:
(1) The order of PUSCH slot indexes is incremental.
(2) The order of the time domain resource indexes of the time division POs within the PUSCH slots is incremental.
(3) The order of the frequency resource indexes of the frequency multiplexed POs is incremented.
(4) The order of demodulation reference signal DMRS resource indexes within the PO is incremental.
Alternatively, the order of (2) to (4) in this example may be changed. For example, the order of (2), (4), and (3), the order of (3), (2), and (4), the order of (3), (4), and (2), the order of (4), (2), and (3), or the order of (4), (3), and (2). Furthermore, if the number of indexes to be mapped is small, the mapping may be performed in the above-described previous order. For example, if the index can already be mapped according to (1), the mapping may not continue according to (2), (3) or (4). For another example, if the index can already be mapped according to (1), (2), the mapping may not be continued according to (3) or (4).
In a specific example, see fig. 9, there are two PUSCH slots, each PUSCH slot including 4 POs, where po#0 and po#1 are time-domain distinct POs, and po#2 and po#3 are time-domain distinct POs. 2 DMRSs are included in each PO. 10 consecutive preambles (e.g., preamble 1 to preamble 10) need to be mapped to PUSCH resources.
For example, it is assumed that preambles are mapped to PUSCH resources in the order of (1), (2), (3), and (4) in the above example in order. Specifically, in the first slot, preamble 1 is mapped to dmrs#0 of po#0; in the second slot, preamble 2 is mapped to DMRS #0 of PO #0. Next, in the first slot, dmrs#0 of preamble 3 to po#1; in the second slot, preamble 4 is mapped to DMRS #0 of PO #1. Subsequently, in the first slot, preamble 5 is mapped to dmrs#0 of po#2; in the second slot, preamble 6 is mapped to DMRS #0 of PO # 2. Then, in the first slot, preamble 7 is mapped to dmrs#0 of po#3; in the second slot, preamble 8 is mapped to DMRS #0 of PO # 3. Then, in the first slot, preamble 9 is mapped to DMRS #1 of PO #0; in the second slot, preamble 10 is mapped to DMRS #1 of PO #0.
For another example, it is assumed that preambles are mapped to PUSCH resources in the order of (1), (3), (2), and (4) in the above example in order. Specifically, in the first slot, preamble 1 is mapped to dmrs#0 of po#0; in the second slot, preamble 2 is mapped to DMRS #0 of PO #0. Next, in the first slot, dmrs#0 of preamble 3 to po#2; in the second slot, preamble 4 is mapped to DMRS #0 of PO # 2. Subsequently, in the first slot, preamble 5 is mapped to dmrs#0 of po#1; in the second slot, preamble 6 is mapped to DMRS #0 of PO #1. Then, in the first slot, preamble 7 is mapped to dmrs#0 of po#3; in the second slot, preamble 8 is mapped to DMRS #0 of PO # 3. Then, in the first slot, preamble 9 is mapped to DMRS #1 of PO #0; in the second slot, preamble 10 is mapped to DMRS #1 of PO #0.
For another example, it is assumed that preambles are mapped to PUSCH resources in the order of (1), (4), (2), and (3) in the above example in order. Specifically, in the first slot, preamble 1 is mapped to dmrs#0 of po#0; in the second slot, preamble 2 is mapped to DMRS #0 of PO #0. Next, in the first slot, dmrs#1 of preamble 3 to po#0; in the second slot, preamble 4 is mapped to DMRS #1 of PO #0. Subsequently, in the first slot, preamble 5 is mapped to dmrs#0 of po#1; in the second slot, preamble 6 is mapped to DMRS #0 of PO #1. Then, in the first slot, preamble 7 is mapped to DMRS #1 of PO #1; in the second slot, preamble 8 is mapped to DMRS #1 of PO #1. Then, in the first slot, preamble 9 is mapped to dmrs#0 of po#2; in the second slot, preamble 10 is mapped to DMRS #0 of PO # 2.
Optionally, in the embodiment of the present application, the order of the DMRS resource indexes of the demodulation reference signals in the POs is incremental, where the DMRS resource indexes are ordered according to an ascending order of the DMRS port indexes and then according to an ascending order of the DMRS sequence indexes. For example, DMRS resource index with Port index of Port0 and Sequence index of Sequence0 is dmrs#0; the DMRS resource index with Port1 as the Port index and Sequence0 as the Sequence index is DMRS#2; the Port index is Port0 and the DMRS resource index with the Sequence index of Sequence1 is DMRS#3; the DMRS resource index with Port0 and Sequence2 is DMRS #4.
Alternatively, in the embodiment of the present application, the random access channel RACH resources configured by the NR terminal and the lightweight NR terminal are different.
Optionally, in an embodiment of the present application, the RACH resource difference includes at least one of:
the preamble sequence sets are different;
the frequency domain positions of RACH resources are different;
the time domain locations of RACH resources are different.
For example, the RACH resources configured by NR terminals include preamble sequences 0-24 and the RACH resources configured by reduced capability terminals (Reduced capability UE), e.g., light weight NR terminals, include preamble sequences 30-50. For another example, the time domains differ: the ROs corresponding to RACH resources are in different PRACH slots, or different symbol sets in the same PRACH slot. For another example, the frequency domains are different, and the frequency domains where ROs corresponding to RACH resources are located are different.
Optionally, in an embodiment of the present application, the method further includes: the N consecutive preambles are determined based on at least one of the following parameters:
the number SSB-perRACH-Occasion of the synchronization signal blocks SSB mapped on each random access channel PRACH Occasion RO;
the number of frequency domains RO msg1-FDM;
number of SSBs.
For example: if SSB-perRACH-allocation=2, r consecutive indexed preambles map to SSB n,0< =n < =1; assuming that the total number of preambles is 64, two SSBs map 1 PRACH occalation. Then n=0, 1 can be taken for both SSBs n. When n=0, the preamble index of SSB 0 is 0-31; when n=1, the preamble index at SSB 1 is 32-63.
Optionally, in an embodiment of the present application, the method further includes:
and mapping the RO of the preamble associated with the PUSCH repeated transmission to different time domains.
Optionally, in the embodiment of the present application, mapping ROs where the preamble used for the PUSCH retransmission is located to a different time domain includes: and mapping N continuous preambles according to the sequence of time division RO, wherein N is a positive integer.
Optionally, in an embodiment of the present application, the sequence of time division ROs includes:
the order of the time domain resource indexes of the time division ROs within the PRACH slot is incremented.
Optionally, in an embodiment of the present application, the mapping order further includes at least one of:
the order of PRACH slot indexes is incremental;
the order of the preamble indexes in one RO is incremental;
the order of the frequency resource indexes of the frequency multiplexing ROs is incremental.
In one example, N consecutive preambles are mapped in the order of time division RO, specifically, the following order may be sequentially mapped:
(1) The order of the time domain resource indexes of the time division ROs within the PRACH slot is incremented.
(2) The order of PRACH slot indexes is incremented.
(3) The order of the preamble indexes in one RO is incremental.
(4) The order of the frequency resource indexes of the frequency multiplexing ROs is incremental.
Alternatively, the order of (2) to (4) in this example may be changed. For example, the order of (2), (4), and (3), the order of (3), (2), and (4), the order of (3), (4), and (2), the order of (4), (2), and (3), or the order of (4), (3), and (2).
Furthermore, if the number of indexes to be mapped is small, the mapping may be performed in the above-described previous order. For example, if the index can already be mapped according to (1), the mapping may not continue according to (2), (3) or (4). For another example, if the index can already be mapped according to (1), (2), the mapping may not be continued according to (3) or (4).
Optionally, in an embodiment of the present application, the sequence of time division ROs includes:
the order of PRACH slot indexes is incremented.
Optionally, in an embodiment of the present application, the mapping order further includes at least one of:
the order of the time domain resource indexes of the time division ROs within the PRACH slot is incremented;
the order of the preamble indexes in one RO is incremental;
the order of the frequency resource indexes of the frequency multiplexing ROs is incremental.
In one example, N consecutive preambles are mapped in the order of time division RO, specifically, the following order may be sequentially mapped:
(1) The order of PRACH slot indexes is incremented.
(2) The order of the time domain resource indexes of the time division ROs within the PRACH slot is incremented.
(3) The order of the preamble indexes in one RO is incremental.
(4) The order of the frequency resource indexes of the frequency multiplexing ROs is incremental.
Alternatively, the order of (2) to (4) in this example may be changed. For example, the order of (2), (4), and (3), the order of (3), (2), and (4), the order of (3), (4), and (2), the order of (4), (2), and (3), or the order of (4), (3), and (2).
Furthermore, if the number of indexes to be mapped is small, the mapping may be performed in the above-described previous order. For example, if the index can already be mapped according to (1), the mapping may not continue according to (2), (3) or (4). For another example, if the index can already be mapped according to (1), (2), the mapping may not be continued according to (3) or (4).
In a specific application scenario, by adopting the method for determining the channel resources in the embodiment of the application, the repeated transmission of the MsgA can be well supported in an NR system by a new mapping mode between the preamble and the PRU, and the transmission delay is short.
Example 1: repeated transmissions of MsgA correspond to different time-domain PUSCH Occasin (PO).
The network may configure mapping parameters between SSBs and ROs, where the parameter CB-precursors-per-SSBs represents the number of Contention Based preambles associated with one SSB. It can be seen that an SSB can associate several preambles in a RO that are consecutive in index. Since the preamble-to-PRU mapping is a sequential mapping of M preambles to one PRU, for one SSB-associated preamble, the order of the PRU mapped would be if mapped in order of frequency-first domain then time-domain. For repeated transmission of MsgA in a two-step RACH, different transmissions need to be time-divided from each other and cannot be transmitted on RO and PO that are frequency-divided from each other but time-domain identical. For a UE, if an SSB is selected by measurement, the PRACH is transmitted according to the network configured active PRACH ocvision (RO) and the preamble associated with the SSB. If the PRACH is repeatedly transmitted, it needs to satisfy time division between transmissions, but according to a mapping relationship between a preamble and a PRU obtained by mapping in a first frequency domain and then in a time domain, it is not necessarily guaranteed that the preamble mapping used between retransmissions is time division between PRUs.
In this example, repeated PUSCH transmission in MsgA requires selection of a different time domain PUSCH occalation when determining PUSCH occalation. As shown in fig. 6, if the UE selects one of the preambles corresponding to SSB 0 to transmit the PRACH, the UE cannot select the preamble corresponding to the PRU with the same time domain for retransmission during retransmission, and if the condition is not satisfied in one PRACH slot, the UE retransmits the PRACH in MsgA in the next PRACH slot. Correspondingly, the PUSCH in MsgA is also mapped to the next PUSCH slot, thereby satisfying that the PUSCH between retransmissions is time-division. As shown in fig. 10, the time domains of po#0 and po#1 are the same, and the time domains of po#2 and po#3 are the same, if the preamble index range used for the first transmission of MsgA is 0-7, the corresponding PRU is dmrs#0 in po#0. In the second transmission, if the RO transmitted for the second time is in the same PRACH slot, the preamble index range corresponding to the SSB 0 can only be selected to be 8-15, so that the time domains of the POs where PRUs corresponding to the preambles transmitted for the second time are located are ensured to be different. Here, it is assumed that the preamble index ranges 0 to 7 and the preamble index ranges 8 to 15 corresponding to SSB 0 respectively belong to ROs of the synchronization time domain.
By adopting the scheme of the example, the repeated transmission of the MsgA is ensured by selecting different time domain PUSCH occasins.
Example 2: the mapping relation between the Preamble and the PRU is mapped according to the sequence of the PO of the prior time domain.
In this embodiment, every M (M > =1) consecutive PRACH preples are mapped to valid PRUs in the following order:
(1) The time domain resource index sequence of the time division PO is incremental in the PUSCH slot;
(2) The order of PUSCH slot indexes is incremental;
(3) The frequency resource index order of the frequency multiplexed POs is incremented;
(4) The DMRS resource index order is incremental in the PO, where the DMRS resource indexes are ordered in ascending order of the DMRS port index first and then in ascending order of the DMRS sequence index.
In the case of mapping preferentially according to the time domain resource index sequence, compared with example 1, it can be relatively easy to ensure that PUSCH repeated transmission in MsgA is performed on different time domain PUSCH occalations, especially when the preamble associated with SSB is relatively small. The above-described mapping step is a specific example in which the order of (1) and (2) described above may be exchanged, and the order of (3) and (4) may be exchanged.
Illustratively, as shown in fig. 11, taking two PUSCH slots as an example, the first PUSCH slot is PUSCH slot 0, and the second PUSCH slot is PUSCH slot 1. The PUSCH slot 0 comprises po#0 to po#3, po#0 and po#1 having the same time domain but different frequency domains, po#2 and po#3 having the same time domain but different frequency domains, po#0 and po#2 having the different time domains but the same frequency domain, and po#1 and po#3 having the different time domains but the same frequency domain. Similarly, PUSCH slot 1 also includes po#0 to po#3. Each PO comprises two DMSRs, and indexes of the DMSR#0 and the DMSR#1 are ordered according to ascending order of indexes of DMRS ports first and then ascending order of indexes of DMRS sequences.
Illustratively, as shown in fig. 12a, SSB 0 associates 16 preambles, which consecutive 16 Preamble0 to Preamble15 are mapped in order of the prior time domain resource index, e.g., sequentially mapped to PRUs in order of (1), (2), (3) and (4) above. Specifically, preamble0 maps to dmrs#0 of po#0 in slot0, and Preamble1 maps to dmrs#0 of po#2 in slot 0; preamble2 maps to dmrs#0 of po#0 in slot1, and Preamble3 maps to dmrs#0 of po#2 in slot 1. The Preamble4 is mapped to dmrs#0 of po#1 in slot0, and the Preamble5 is mapped to dmrs#0 of po#3 in slot 0; preamble6 maps to dmrs#0 of po#1 in slot1 and Preamble7 maps to dmrs#0 of po#3 in slot 1. Preamble8 maps to dmrs#1 of po#0 in slot0, and Preamble9 maps to dmrs#1 of po#2 in slot 0; preamble10 maps to dmrs#1 of po#0 in slot1 and Preamble11 maps to dmrs#1 of po#2 in slot 1. Preamble12 maps to dmrs#1 of po#1 in slot0 and Preamble13 maps to dmrs#1 of po#3 in slot 0; preamble14 maps to dmrs#1 of po#1 in slot1 and Preamble15 maps to dmrs#1 of po#3 in slot 1.
For retransmission of MsgA, preamble0 is used in the first transmission, and preambles 1-3 may be selected in the second transmission because their corresponding POs are time-divided.
As shown in fig. 12b, illustratively, SSB 0 associates 16 preambles, and the consecutive 16 preambles 0 to 15 are mapped in the order of the previous time-domain resource index, for example, sequentially mapped to PRUs in the order of (2), (1), (3), and (4) described above, as shown in fig. 12 a. Specifically, preamble0 maps to dmrs#0 of po#0 in slot0, and Preamble1 maps to dmrs#0 of po#0 in slot 1; preamble2 maps to dmrs#0 of po#2 in slot0 and Preamble3 maps to dmrs#0 of po#2 in slot 1. The Preamble4 is mapped to dmrs#0 of po#1 in slot0, and the Preamble5 is mapped to dmrs#0 of po#1 in slot 1; preamble6 maps to dmrs#0 of po#3 in slot0 and Preamble7 maps to dmrs#0 of po#3 in slot 1. Preamble8 maps to dmrs#1 of po#0 in slot0, and Preamble9 maps to dmrs#1 of po#0 in slot 1; preamble10 maps to dmrs#1 of po#2 in slot0 and Preamble11 maps to dmrs#1 of po#2 in slot 1. Preamble12 maps to dmrs#1 of po#1 in slot0 and Preamble13 maps to dmrs#1 of po#1 in slot 1; preamble14 maps to dmrs#1 of po#3 in slot0 and Preamble15 maps to dmrs#1 of po#3 in slot 1.
According to the scheme of the example, the situation that retransmission of the MsgA cannot be completed when the preamble associated with one SSB in one PRACH slot is mapped to the PO of the frequency division can be avoided.
Further, in order to avoid collision of the use of PRACH resources between two mapping modes corresponding to NR and NR-light, different RACH resources may be configured for NR and NR-light, respectively. For example, the different RACH resource configurations may include: the preamble sequence sets are different; the frequency domain positions of RACH resources are different; time domain location of RACH resources is different, etc.
By adopting the scheme of the example, the mapping mode between the preamble and the PRU is mapped according to the sequence of the time domain before the frequency domain, so that a plurality of time domains PO can be obtained more quickly for the repeated transmission of the MsgA. Compared with the original mapping mode of the first frequency domain and the second time domain, the time delay of MsgA repeated transmission can be reduced.
Example 3: based on example 2, the mapping relationship between the preamble and the PRU may be determined according to at least one of the number parameters of SSB-perRACH-allocation, msg1-FDM, and SSB.
Examples 1-2 are mainly the mapping between preamble to PRU, the mapping order of PRU is time domain first mapping, ensuring that the PRUs of one SSB-associated preamble map are time-division with each other. In order to make the RO where the preamble of the MsgA repeated transmission is located also satisfy the time division, the mapping sequence of the preamble may also satisfy the mapping of the previous time division.
Within the PRACH slot, the sequence of a set of consecutive preambles is:
(1) The order of the time domain resource indexes of the time domain multiplexing PRACCA within the PRACH time slot is incremental;
(2) The order of PRACH slot indexes is incremental;
(3) The order of preamble indexes in a PRACH occision is incremented
(4) The frequency resource index order of the frequency multiplexing PRACH occalation is incremented;
similar to example 2, the above-described mapping step is a specific example in which the order of (1) and (2) described above may be exchanged, and the order of (3) and (4) may be exchanged.
In connection with example 2, the mapping relationship between the preamble and the PRU may be seen in fig. 12a or fig. 12b.
According to the scheme of the embodiment, the mapping mode of the preamble in the PRACH slot and the mapping mode of the preamble and the PRU are mapped according to the time domain sequence, so that the repeated transmission of the MsgA can be met, and the retransmission transmission delay is short.
Fig. 13 is a schematic block diagram of a terminal device 400 according to an embodiment of the present application. The terminal device 400 may include:
the processing unit 410 is configured to determine a plurality of physical uplink shared channel PUSCH resources, where time domain resources of the plurality of PUSCH resources are different, the plurality of PUSCH resources are used for repeated transmission of PUSCH, and the PUSCH belongs to a message a of a type 2 random access procedure.
Optionally, in the embodiment of the present application, the time domain resource of the PO where the PUSCH is repeatedly transmitted is different.
Optionally, in the embodiment of the present application, the PUSCH resource and the preamble have a mapping relationship.
Optionally, in the embodiment of the present application, the processing unit is further configured to map N consecutive preambles to PUSCH resources in order of time domain resource indexes, where N is a positive integer.
Optionally, in a mode one of the embodiments of the present application, the order of the time domain resource indexes includes: the order of the time domain resource indexes of the time division POs within the PUSCH slots is incremental.
Optionally, in a first mode of the embodiment of the present application, the mapping order further includes at least one of:
the order of PUSCH slot indexes is incremental;
the order of the frequency resource indexes of the frequency multiplexed POs is incremented;
the order of demodulation reference signal DMRS resource indexes within the PO is incremental.
Optionally, in the second mode of the embodiment of the present application, the sequence of the time domain resource indexes includes: the order of PUSCH slot index is increasing.
Optionally, in a second mode of the embodiment of the present application, the mapping order further includes at least one of the following:
the order of the time domain resource indexes of the time division POs is incremental in the PUSCH time slot;
The order of the frequency resource indexes of the frequency multiplexed POs is incremented;
the order of DMRS resource indexes within the PO is incremental.
Optionally, in the embodiment of the present application, the DMRS resource indexes are ordered according to an ascending order of the DMRS port indexes and then according to an ascending order of the DMRS sequence indexes.
Alternatively, in the embodiment of the present application, the random access channel RACH resources configured by the NR terminal and the lightweight NR terminal are different.
Optionally, in an embodiment of the present application, the RACH resource difference includes at least one of:
the preamble sequence sets are different;
the frequency domain positions of RACH resources are different;
the time domain locations of RACH resources are different.
Optionally, in an embodiment of the present application, the processing unit is further configured to determine the N consecutive preambles based on at least one of the following parameters:
the number SSB-perRACH-Occasion of the synchronization signal blocks SSB mapped on each random access channel PRACH Occasion RO;
the number of frequency domains RO msg1-FDM;
number of SSBs.
Optionally, in the embodiment of the present application, the processing unit is further configured to map ROs where the preamble associated with the PUSCH retransmission is located to different time domains.
Optionally, in the embodiment of the present application, the processing unit is further configured to map N consecutive preambles in order of time division RO, where N is a positive integer.
Optionally, in an embodiment of the present application, the sequence of time division ROs includes: the order of the time domain resource indexes of the time division ROs within the PRACH slot is incremented.
Optionally, in an embodiment of the present application, the mapping order further includes at least one of:
the order of PRACH slot indexes is incremental;
the order of the preamble indexes in one RO is incremental;
the order of the frequency resource indexes of the frequency multiplexing ROs is incremental.
Optionally, in an embodiment of the present application, the sequence of time division ROs includes: the order of PRACH slot indexes is incremented.
Optionally, in an embodiment of the present application, the mapping order further includes at least one of:
the order of the time domain resource indexes of the time division ROs within the PRACH slot is incremented;
the order of the preamble indexes in one RO is incremental;
the order of the frequency resource indexes of the frequency multiplexing ROs is incremental.
The terminal device 400 of the embodiment of the present application can implement the corresponding function of the terminal device in the foregoing method embodiment. The flow, function, implementation and beneficial effects corresponding to each module (sub-module, unit or assembly, etc.) in the terminal device 400 can be referred to the corresponding description in the above method embodiments, and will not be repeated here. It should be noted that, the functions described in the respective modules (sub-modules, units, or components, etc.) in the terminal device 400 of the application embodiment may be implemented by different modules (sub-modules, units, or components, etc.), or may be implemented by the same module (sub-module, unit, component, etc.).
Fig. 14 is a schematic structural diagram of a communication device 600 according to an embodiment of the present application. The communication device 600 comprises a processor 610, which processor 610 may call and run a computer program from a memory to cause the communication device 600 to implement the methods in embodiments of the present application.
Optionally, as shown in fig. 14, the communication device 600 may further comprise a memory 620. Wherein the processor 610 may invoke and run a computer program from the memory 620 to cause the communication device 600 to implement the method in the embodiments of the present application.
The memory 620 may be a separate device from the processor 610 or may be integrated into the processor 610.
Optionally, as shown in fig. 14, the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, and in particular, may send information or data to other devices, or receive information or data sent by other devices.
The transceiver 630 may include a transmitter and a receiver, among others. Transceiver 630 may further include antennas, the number of which may be one or more.
Optionally, the communication device 600 may be a network device in the embodiment of the present application, and the communication device 600 may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.
Optionally, the communication device 600 may be a terminal device in the embodiment of the present application, and the communication device 600 may implement a corresponding flow implemented by the terminal device in each method in the embodiment of the present application, which is not described herein for brevity.
Fig. 15 is a schematic structural diagram of a chip 700 according to an embodiment of the present application. The chip 700 includes a processor 710, and the processor 710 may call and run a computer program from a memory to implement the methods of the embodiments of the present application.
Optionally, as shown in fig. 15, chip 700 may also include memory 720. The processor 710 may invoke and run a computer program from the memory 720 to implement the method performed by the terminal device or the network device in the embodiments of the present application.
Wherein the memory 720 may be a separate device from the processor 710 or may be integrated into the processor 710.
Optionally, the chip 700 may also include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and in particular, may obtain information or data sent by other devices or chips.
Optionally, the chip 700 may further include an output interface 740. The processor 710 may control the output interface 740 to communicate with other devices or chips, and in particular, may output information or data to other devices or chips.
Optionally, the chip may be applied to a network device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.
Optionally, the chip may be applied to a terminal device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the terminal device in each method in the embodiment of the present application, which is not described herein for brevity.
The chips applied to the network device and the terminal device may be the same chip or different chips.
It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.
The processors mentioned above may be general purpose processors, digital signal processors (digital signal processor, DSP), off-the-shelf programmable gate arrays (field programmable gate array, FPGA), application specific integrated circuits (application specific integrated circuit, ASIC) or other programmable logic devices, transistor logic devices, discrete hardware components, etc. The general-purpose processor mentioned above may be a microprocessor or any conventional processor.
The memory mentioned above may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM).
It should be understood that the above memory is exemplary but not limiting, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct Rambus RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.
Fig. 16 is a schematic block diagram of a communication system 800 according to an embodiment of the present application. The communication system 800 includes a terminal device 810 and a network device 820.
The terminal device 810 is configured to determine a plurality of physical uplink shared channel PUSCH resources, where time domain resources of the plurality of PUSCH resources are different, where the plurality of PUSCH resources are used for repeated transmission of PUSCH, and the PUSCH belongs to a message a of a type 2 random access procedure.
Network device 820 is configured to reply to terminal device B after receiving message a repeatedly transmitted from terminal device 810 during type 2 random access.
Wherein the terminal device 810 may be used to implement the corresponding functions implemented by the terminal device in the above-described method, and the network device 820 may be used to implement the corresponding functions implemented by the network device in the above-described method. For brevity, the description is omitted here. In this embodiment, before detecting the response of the network device, for example, the base station, the terminal device may repeatedly transmit the message a several times, and then detect the response of the network device, for example, the base station. Therefore, the transmission reliability of the message a can be improved.
In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions in accordance with embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD)), or the like.
It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.
The foregoing is merely a specific embodiment of the present application, but the protection scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions should be covered in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (41)

  1. A method of determining channel resources, comprising:
    the method comprises the steps that terminal equipment determines a plurality of Physical Uplink Shared Channel (PUSCH) resources, wherein time domain resources of the plurality of PUSCH resources are different, the plurality of PUSCH resources are used for repeated transmission of a PUSCH, and the PUSCH belongs to a message A of a type 2 random access process.
  2. The method of claim 1, wherein time domain resources of PUSCH occasions PO where the PUSCH transmissions are repeated are different.
  3. The method of claim 1 or 2, wherein the PUSCH resources and the preamble have a mapping relationship.
  4. A method according to claim 3, wherein the method further comprises:
    and mapping N continuous preambles to the PUSCH resources according to the sequence of the time domain resource indexes, wherein N is a positive integer.
  5. The method of claim 4, wherein the order of the time domain resource indexes comprises:
    the order of the time domain resource indexes of the time division POs within the PUSCH slots is incremental.
  6. The method of claim 4 or 5, wherein the mapping order further comprises at least one of:
    the order of PUSCH slot indexes is incremental;
    the order of the frequency resource indexes of the frequency multiplexed POs is incremented;
    the order of demodulation reference signal DMRS resource indexes within the PO is incremental.
  7. The method of claim 4, wherein the order of the time domain resource indexes comprises:
    the order of PUSCH slot indexes is incremental.
  8. The method of claim 4 or 7, wherein the mapping order further comprises at least one of:
    The order of the time domain resource indexes of the time division POs is incremental in the PUSCH time slot;
    the order of the frequency resource indexes of the frequency multiplexed POs is incremented;
    the order of DMRS resource indexes within the PO is incremental.
  9. The method of claim 6 or 8, wherein the DMRS resource indexes are ordered first in ascending order of DMRS port indexes and then in ascending order of DMRS sequence indexes.
  10. The method according to any of claims 1 to 9, wherein the random access channel, RACH, resources configured by the NR terminal and the lightweight NR terminal are different.
  11. The method of claim 10, wherein RACH resource variation comprises at least one of:
    the preamble sequence sets are different;
    the frequency domain positions of RACH resources are different;
    the time domain locations of RACH resources are different.
  12. The method of any of claims 4 to 9, wherein the method further comprises:
    determining the N consecutive preambles based on at least one of the following parameters:
    the number SSB-perRACH-Occasion of the synchronization signal blocks SSB mapped on each random access channel PRACH Occasion RO;
    the number of frequency domains RO msg1-FDM;
    number of SSBs.
  13. The method of any one of claims 1 to 12, wherein the method further comprises:
    And mapping the RO of the preamble associated with the PUSCH repeated transmission to different time domains.
  14. The method of claim 13, wherein mapping ROs in which the preamble used for PUSCH retransmission is located to different time domains comprises:
    and mapping N continuous preambles according to the sequence of time division RO, wherein N is a positive integer.
  15. The method of claim 14, wherein the sequence of time-division ROs comprises:
    the order of the time domain resource indexes of the time division ROs within the PRACH slot is incremented.
  16. The method of claim 14 or 15, wherein the mapping order further comprises at least one of:
    the order of PRACH slot indexes is incremental;
    the order of the preamble indexes in one RO is incremental;
    the order of the frequency resource indexes of the frequency multiplexing ROs is incremental.
  17. The method of claim 14, wherein the sequence of time-division ROs comprises:
    the order of PRACH slot indexes is incremented.
  18. The method of claim 14 or 17, wherein the mapping order further comprises at least one of:
    the order of the time domain resource indexes of the time division ROs within the PRACH slot is incremented;
    the order of the preamble indexes in one RO is incremental;
    The order of the frequency resource indexes of the frequency multiplexing ROs is incremental.
  19. A terminal device, comprising:
    the processing unit is configured to determine a plurality of physical uplink shared channel PUSCH resources, where time domain resources of the plurality of PUSCH resources are different, the plurality of PUSCH resources are used for repeated transmission of PUSCH, and the PUSCH belongs to a message a of a type 2 random access procedure.
  20. The terminal device of claim 19, wherein time domain resources of PUSCH occasions PO where the PUSCH transmissions are repeated are different.
  21. The terminal device of claim 19 or 20, wherein the PUSCH resources and the preamble have a mapping relation.
  22. The terminal device of claim 21, wherein the processing unit is further configured to map N consecutive preambles to PUSCH resources in order of time domain resource indexes, where N is a positive integer.
  23. The terminal device of claim 22, wherein the order of the time domain resource indexes comprises:
    the order of the time domain resource indexes of the time division POs within the PUSCH slots is incremental.
  24. The terminal device of claim 22 or 23, wherein the mapping order further comprises at least one of:
    the order of PUSCH slot indexes is incremental;
    The order of the frequency resource indexes of the frequency multiplexed POs is incremented;
    the order of demodulation reference signal DMRS resource indexes within the PO is incremental.
  25. The terminal device of claim 22, wherein the order of the time domain resource indexes comprises:
    the order of PUSCH slot indexes is incremental.
  26. The terminal device of claim 22 or 25, wherein the mapping order further comprises at least one of:
    the order of the time domain resource indexes of the time division POs is incremental in the PUSCH time slot;
    the order of the frequency resource indexes of the frequency multiplexed POs is incremented;
    the order of DMRS resource indexes within the PO is incremental.
  27. The terminal device of claim 24 or 26, wherein the DMRS resource indexes are ordered first in ascending order of DMRS port indexes and then in ascending order of DMRS sequence indexes.
  28. The terminal device of any of claims 19 to 27, wherein the random access channel RACH resources configured by the NR terminal and the lightweight NR terminal are different.
  29. The terminal device of claim 28, wherein RACH resources are different including at least one of:
    the preamble sequence sets are different;
    the frequency domain positions of RACH resources are different;
    the time domain locations of RACH resources are different.
  30. The terminal device of any of claims 22 to 27, wherein the processing unit is further configured to determine the N consecutive preambles based on at least one of the following parameters:
    the number SSB-perRACH-Occasion of the synchronization signal blocks SSB mapped on each random access channel PRACH Occasion RO;
    the number of frequency domains RO msg1-FDM;
    number of SSBs.
  31. The terminal device of any of claims 19 to 30, wherein the processing unit is further configured to map ROs in which the preamble associated with PUSCH retransmission is located to different time domains.
  32. The terminal device of claim 31, wherein the processing unit is further configured to map N consecutive preambles in order of time division RO, where N is a positive integer.
  33. The terminal device of claim 32, wherein the sequence of time-division ROs comprises:
    the order of the time domain resource indexes of the time division ROs within the PRACH slot is incremented.
  34. The terminal device of claim 32 or 33, wherein the mapping order further comprises at least one of:
    the order of PRACH slot indexes is incremental;
    the order of the preamble indexes in one RO is incremental;
    the order of the frequency resource indexes of the frequency multiplexing ROs is incremental.
  35. The terminal device of claim 32, wherein the sequence of time-division ROs comprises:
    the order of PRACH slot indexes is incremented.
  36. The terminal device of claim 32 or 35, wherein the mapping order further comprises at least one of:
    the order of the time domain resource indexes of the time division ROs within the PRACH slot is incremented;
    the order of the preamble indexes in one RO is incremental;
    the order of the frequency resource indexes of the frequency multiplexing ROs is incremental.
  37. A terminal device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory to cause the terminal device to perform the method of any of claims 1 to 18.
  38. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any one of claims 1 to 18.
  39. A computer readable storage medium storing a computer program which, when executed by a device, causes the device to perform the method of any one of claims 1 to 18.
  40. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 18.
  41. A computer program which causes a computer to perform the method of any one of claims 1 to 18.
CN202080104361.4A 2020-08-20 2020-08-20 Channel resource determining method and terminal equipment Pending CN116058029A (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/110152 WO2022036617A1 (en) 2020-08-20 2020-08-20 Channel resource determination method and terminal device

Publications (1)

Publication Number Publication Date
CN116058029A true CN116058029A (en) 2023-05-02

Family

ID=80322435

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202080104361.4A Pending CN116058029A (en) 2020-08-20 2020-08-20 Channel resource determining method and terminal equipment

Country Status (2)

Country Link
CN (1) CN116058029A (en)
WO (1) WO2022036617A1 (en)

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10660133B2 (en) * 2015-12-03 2020-05-19 Seoul National University R&Db Foundation Method and system for random access and uplink data transmission for low latency communication
CN107872899B (en) * 2016-09-23 2022-12-06 中兴通讯股份有限公司 Random access method, device and equipment
CN111447644A (en) * 2019-01-17 2020-07-24 北京三星通信技术研究有限公司 User equipment and uplink data transmission method
CN111278157B (en) * 2019-01-25 2022-03-25 维沃移动通信有限公司 Method for selecting random access resource and terminal
WO2020154992A1 (en) * 2019-01-30 2020-08-06 Qualcomm Incorporated Random access procedure based on two-step random access channel procedure and four-step random access channel procedure

Also Published As

Publication number Publication date
WO2022036617A1 (en) 2022-02-24

Similar Documents

Publication Publication Date Title
US20230069882A1 (en) Method for configuring sidelink feedback resource, terminal device, and network device
US11546861B2 (en) Techniques in inter-band and intra-band dynamic power sharing in dual connectivity communications
CN116711439A (en) Wireless communication method, terminal equipment and network equipment
EP4096323A1 (en) Wireless communication method and device
CN116762311A (en) Wireless communication method, terminal equipment and network equipment
CN116548039A (en) Wireless communication method and terminal equipment
CN116058029A (en) Channel resource determining method and terminal equipment
CN115413045B (en) Information transmission method, terminal equipment and network equipment
WO2022110072A1 (en) Wireless communication method, and terminal device and network device
WO2022077346A1 (en) Channel transmission method, terminal device and network device
WO2022151111A1 (en) Signal configuration method, terminal device, network device, chip and storage medium
WO2023197154A1 (en) Wireless communication method, terminal device, and network device
US20230217433A1 (en) Resource scheduling method, terminal device, and network device
CN118044304A (en) Wireless communication method and terminal equipment
CN116058028A (en) Resource set transmission method and terminal
CN118176806A (en) Wireless communication method, terminal equipment and network equipment
CN116783922A (en) Information indicating method, terminal device, network device, chip and storage medium
CN116803180A (en) Half-duplex data transmission method, terminal equipment and network equipment
CN117063564A (en) Wireless communication method, terminal device and network device
CN118120306A (en) Sidestream communication method and equipment
CN117730596A (en) Wireless communication method, terminal equipment and network equipment
CN118044291A (en) Communication method, terminal device and network device
CN117751532A (en) Wireless communication method, terminal equipment and network equipment
CN117652117A (en) Wireless communication method, terminal equipment and network equipment
CN116803182A (en) Wireless communication method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination