WO2023004619A1

WO2023004619A1 - Information transmission method, device, and storage medium

Info

Publication number: WO2023004619A1
Application number: PCT/CN2021/108881
Authority: WO
Inventors: 李海涛; 胡奕
Original assignee: Oppo广东移动通信有限公司
Priority date: 2021-07-28
Filing date: 2021-07-28
Publication date: 2023-02-02
Also published as: CN117296433A

Abstract

The present application provides an information transmission method, a device, and a storage medium. The method comprises: a terminal device sends a target preamble to a network device on a target RACH resource pool, so that the network device determines the type or capability of the terminal device according to the target RACH resource pool and/or the target preamble, so as to implement corresponding contention resolution message sending, thereby improving the transmission performance of a whole communication system.

Description

Information transmission method, device and storage medium

technical field

The embodiments of the present application relate to the field of communication technologies, and in particular, to an information transmission method, device, and storage medium.

Background technique

At present, in the new radio access technology (NR) system, the terminal device listens to the random access response message (Msg2) through the random access response time window, and responds to the contention resolution message (Msg4) after sending Msg3. The monitoring is controlled by the Random Access Contention Resolution Timer (RA-ContentionResolutionTimer). Different types or capabilities of terminal devices start RA-ContentionResolutionTimer in different ways. How the terminal device informs the network of its device type or capability so that the network makes corresponding random access feedback is one of the problems to be solved urgently.

Contents of the invention

Embodiments of the present application provide an information transmission method, device, and storage medium, so as to improve transmission performance of a communication system.

In the first aspect, the embodiment of the present application provides an information transmission method, which includes: the terminal device sends the target preamble to the network device on the time-frequency domain resource of the target random access channel RACH resource pool; the target RACH resource pool is determined from at least one RACH resource pool configured by the network device according to the device information of the terminal device, and the target preamble is at least one preamble configured from the network device according to the device information of the terminal device identified in the set.

In a second aspect, an embodiment of the present application provides an information transmission method, the method comprising: a network device receives a target preamble from a terminal device on a time-frequency domain resource of a target random access channel RACH resource pool; the target RACH resource The pool is determined from at least one RACH resource pool configured by the network device according to the device information of the terminal device, and the target preamble is determined from at least one RACH resource pool configured by the network device according to the device information of the terminal device identified in the code set.

In a third aspect, an embodiment of the present application provides a terminal device, including: a sending module, configured to send a target preamble to a network device on time-frequency domain resources of a target random access channel RACH resource pool; the target RACH resource pool is determined from at least one RACH resource pool configured by the network device according to the device information of the terminal device, and the target preamble is at least one preamble configured from the network device according to the device information of the terminal device identified in the set.

In a fourth aspect, the embodiment of the present application provides a network device, including: a receiving module, configured to receive a target preamble from a terminal device on a time-frequency domain resource of a target random access channel RACH resource pool; the target RACH resource The pool is determined from at least one RACH resource pool configured by the network device according to the device information of the terminal device, and the target preamble is determined from at least one RACH resource pool configured by the network device according to the device information of the terminal device identified in the code set.

In a fifth aspect, an embodiment of the present application provides a terminal device, including: a memory and a processor, the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the The processor executes the computer program to execute the method as described in the first aspect.

In a sixth aspect, an embodiment of the present application provides a network device, including: a memory and a processor, the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the The processor executes the computer program to execute the method according to the second aspect.

In a seventh aspect, an embodiment of the present application provides a computer storage medium for storing a computer program, and when the computer program runs on a computer, the computer executes the method described in the first aspect.

In an eighth aspect, the embodiment of the present application provides a computer storage medium for storing a computer program, and when the computer program runs on a computer, the computer executes the method as described in the second aspect.

In a ninth aspect, the embodiment of the present application provides a computer program product, which, when the computer program product is run on a computer, causes the computer to execute the method as described in the first aspect.

In a tenth aspect, an embodiment of the present application provides a computer program product, which, when the computer program product is run on a computer, causes the computer to execute the method as described in the second aspect.

An embodiment of the present application provides an information transmission method, device, and storage medium. The method includes: the terminal device sends the target preamble to the network device on the target RACH resource pool, so that the network device uses the target RACH resource pool and/or the target preamble Knowing the type or capability of the terminal equipment, so as to send a corresponding contention resolution message, can improve the transmission performance of the entire communication system.

Description of drawings

FIG. 1 is a schematic diagram of a communication system applicable to the information transmission method of the embodiment of the present application;

FIG. 2 is a schematic diagram of a contention-based random access process provided by an embodiment of the present application;

FIG. 3 is a schematic diagram of a non-contention-based random access process provided by an embodiment of the present application;

FIG. 4 is a schematic diagram 1 of an information transmission method provided by an embodiment of the present application;

FIG. 5 is a first configuration schematic diagram of the RACH resource pool provided by the embodiment of the present application;

FIG. 6 is a second configuration schematic diagram of the RACH resource pool provided by the embodiment of the present application;

FIG. 7 is a third schematic diagram of the configuration of the RACH resource pool provided by the embodiment of the present application;

FIG. 8 is a fourth schematic diagram of the configuration of the RACH resource pool provided by the embodiment of the present application;

FIG. 9 is a fifth configuration schematic diagram of the RACH resource pool provided by the embodiment of the present application;

FIG. 10 is a second schematic diagram of the information transmission method provided by the embodiment of the present application;

FIG. 11 is a schematic structural diagram of a terminal device provided in an embodiment of the present application;

FIG. 12 is a schematic structural diagram of a network device provided in an embodiment of the present application;

FIG. 13 is a schematic diagram of a hardware structure of a terminal device provided in an embodiment of the present application;

FIG. 14 is a schematic diagram of a hardware structure of a network device provided by an embodiment of the present application.

Detailed ways

The technical solution in this application will be described below with reference to the accompanying drawings.

The communication method provided by this application can be applied to various communication systems, for example: Long Term Evolution (Long Term Evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), Universal Mobile Telecommunications System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) Communication System, Fifth Generation (5th Generation, 5G) Mobile Communication System or New Wireless Access Technology (new radio access technology, NR). Wherein, the 5G mobile communication system may include non-standalone networking (non-standalone, NSA) and/or standalone networking (standalone, SA).

The communication method provided by this application can also be applied to machine type communication (machine type communication, MTC), inter-machine communication long-term evolution technology (Long Term Evolution-machine, LTE-M), device to device (device to device, D2D) network , machine to machine (machine to machine, M2M) network, Internet of things (internet of things, IoT) network or other networks. Wherein, the IoT network may include, for example, the Internet of Vehicles. Among them, the communication methods in the Internet of Vehicles system are collectively referred to as vehicle to other devices (vehicle to X, V2X, X can represent anything), for example, the V2X can include: vehicle to vehicle (vehicle to vehicle, V2V) communication, vehicle and Infrastructure (vehicle to infrastructure, V2I) communication, vehicle to pedestrian (vehicle to pedestrian, V2P) or vehicle to network (vehicle to network, V2N) communication, etc.

The communication method provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system and the like. This application is not limited to this.

In the embodiment of the present application, 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.

A terminal device may be a device that provides voice/data connectivity to users, for example, a handheld device with a wireless connection function, a vehicle-mounted device, and the like. At present, examples of some terminals can be: mobile phone (mobile phone), tablet computer (pad), computer with wireless transceiver function (such as notebook computer, palmtop computer, etc.), mobile internet device (mobile internet device, MID), virtual reality (virtual reality, VR) equipment, augmented reality (augmented reality, AR) equipment, wireless terminals in industrial control (industrial control), wireless terminals in self driving (self driving), wireless in remote medical (remote medical) Terminals, wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, cellular phones, cordless Telephones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices, or connected Other processing devices to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in the 5G network or terminal devices in the future evolution of the public land mobile network (PLMN), etc.

Among them, wearable devices can also be called wearable smart devices, which is a general term for the application of wearable technology to intelligently design daily wear and develop wearable devices, 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 devices are not only a hardware device, but also achieve powerful functions through software support, data interaction, and cloud interaction. Generalized wearable smart devices include full-featured, large-sized, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, etc., and only focus on a certain type of application functions, and need to cooperate with other devices such as smart phones Use, such as various smart bracelets and smart jewelry for physical sign monitoring.

In addition, the terminal device may also be a terminal device in an Internet of Things (Internet of things, IoT) system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, so as to realize the intelligent network of human-machine interconnection and object interconnection. IoT technology can achieve massive connections, deep coverage, and terminal power saving through, for example, narrow band (NB) technology.

In addition, terminal equipment can also include sensors such as smart printers, train detectors, and gas stations. The main functions include collecting data (partial terminal equipment), receiving control information and downlink data from network equipment, and sending electromagnetic waves to transmit uplink data to network equipment. .

In this embodiment of the present application, the network device may be any device with a wireless transceiver function. Network equipment includes but not limited to: evolved Node B (evolved Node B, eNB), radio network controller (radio network controller, RNC), Node B (Node B, NB), base station controller (base station controller, BSC) , base transceiver station (base transceiver station, BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (baseband unit, BBU), wireless fidelity (wireless fidelity, WiFi) system Access point (access point, AP), wireless relay node, wireless backhaul node, transmission point (transmission point, TP) or transmission and reception point (transmission and reception point, TRP), etc., can also be 5G, such as NR , a gNB in the system, or, a transmission point (TRP or TP), one or a group (including multiple antenna panels) antenna panels of a base station in a 5G system, or, it can also be a network node that constitutes a gNB or a transmission point, Such as a baseband unit (BBU), or a distributed unit (distributed unit, DU), etc.

In some deployments, a gNB may include a centralized unit (CU) and a DU. The gNB may also include an active antenna unit (AAU). The CU implements some functions of the gNB, and the DU implements some functions of the gNB. For example, the CU can be responsible for processing non-real-time protocols and services, for example, it can implement the radio resource control (radio resource control, RRC) layer, service data adaptive protocol (service data) Adaptation protocol (SDAP) layer and/or packet data convergence protocol (packet data convergence protocol, PDCP) layer functions. DU can be responsible for handling physical layer protocols and real-time services. For example, functions of a radio link control (radio link control, RLC) layer, a media access control (media access control, MAC) layer, and a physical (physical, PHY) layer may be implemented. A DU can be connected to only one CU or to multiple CUs, and a CU can be connected to multiple DUs, and CUs and DUs can communicate through the F1 interface. The AAU can realize some physical layer processing functions, radio frequency processing and related functions of active antennas. Because the information of the RRC layer will eventually be submitted to the PHY layer to become the information of the PHY layer, or converted from the information of the PHY layer, therefore, under this architecture, high-level signaling, such as RRC layer signaling, also It can be considered as sent by the DU, or sent by the DU+AAU.

It can be understood that the network device may be a device including one or more of a CU node, a DU node, and an AAU node. In addition, the CU can be divided into network devices in an access network (radio access network, RAN), and the CU can also be divided into network devices in a core network (core network, CN), which is not limited in this application.

The network device provides services for the cell, and the terminal device communicates with the cell through the transmission resources (for example, frequency domain resources, or spectrum resources) allocated by the network device. The cell may belong to a macro base station (for example, a macro eNB or a macro gNB, etc.) , can also belong to the base station corresponding to a small cell, where the small cell can include: a metro cell, a micro cell, a pico cell, a 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.

In order to facilitate understanding of the embodiment of the present application, a communication system applicable to the embodiment of the present application is first described with reference to FIG. 1 .

FIG. 1 is a schematic diagram of a communication system applicable to the information transmission method of the embodiment of the present application. As shown in FIG. 1 , the communication system 100 may include at least one network device and multiple terminal devices, for example, the network device 101 and the terminal devices 102 to 105 shown in FIG. 1 . The network device 101 and each terminal device 102 to 105 can communicate through wireless air interfaces respectively, and the terminal devices can communicate through D2D communication technology. For example, the terminal device 102 and the terminal device 103 shown in FIG. 1 may communicate with each other, and the terminal device 104 and the terminal device 105 may also communicate with each other.

It should be understood that FIG. 1 is only an example, showing a scenario where the terminal device 102 sends signaling and/or data to the terminal device 103, and the terminal device 104 sends signaling and/or data to the terminal device 105, but this does not apply to this Application constitutes no qualification. There may also be signaling and/or data interaction between the terminal device 102 and the terminal device 104 , and there may also be signaling and/or data interaction between the terminal device 103 and the terminal device 104 . This embodiment of the present application does not limit it.

It should also be understood that Fig. 1 is only an example, showing one network device and four terminal devices. But this should not constitute any limitation to the present application. The communication system 100 may also include more network devices, and may also include more or less terminal devices. This embodiment of the present application does not limit it.

In the communication system shown in FIG. 1 , signaling and/or data transmission can be performed between terminal devices through sidelinks. The resources used by the terminal device to communicate via the sidelink may be allocated by the network device. In other words, the network device allocates resources for sidelink transmissions. For example, terminal device 102 in FIG. 1 may send signaling and/or data to terminal device 103 through resources allocated by the network device, and terminal device 104 may send signaling and/or data to terminal device 105 through resources allocated by the network device.

Wireless communication between communication devices may include wireless communication between network devices and terminal devices, wireless communication between network devices and network devices, and wireless communication between terminal devices and terminal devices. In this embodiment of the present application, the term "wireless communication" may also be referred to as "communication" for short, and the term "communication" may also be described as "data transmission", "information transmission" or "transmission". Those skilled in the art can use the technical solutions of the embodiments of the present application for wireless communication between network devices and terminal devices, such as wireless communication between access network devices and terminal devices, and wireless communication between core network devices and terminal devices.

At present, in some communication systems, such as the 5th generation wireless system (5G), in order to meet high data rates, reduce delays, save energy, reduce costs, provide capacity and connect large-scale devices, the definition Enhanced mobile broadband (eMBB), low latency and highly reliable communications (ultra reliable low latency communications, URLLC), large-scale machine type communications (Massive machine type communications, mMTC) three application scenarios. eMBB mainly meets the service requirements for high data rates and supports new formats such as high-definition video and VR. It is widely used in sports, entertainment, education and other industries, and is also used in security monitoring and product testing. Typical applications of URLLC include industrial automation, electric power automation, telemedicine operations (surgery), traffic safety assurance, etc. Typical characteristics of mMTC include high connection density, small data volume, delay-insensitive services, low cost and long service life of modules, etc.

In the 5G network environment, in order to reduce air interface signaling, quickly restore wireless connections, and quickly restore data services, a new RRC state is defined, namely RRC_INACTIVE state. This state is different from RRC_IDLE state and RRC_ACTIVE state.

RRC_IDLE state: mobility is UE-based cell selection and reselection, paging is initiated by CN, and paging area is configured by CN. There is no UE access stratum (AS) context on the base station side. There is no RRC connection.

RRC_CONNECTED state: There is an RRC connection, and the UE AS context exists between the base station and the UE. The network side knows the location of the UE at the specific cell level. Mobility is mobility controlled by the network side. Unicast data can be transmitted between the UE and the base station.

RRC_INACTIVE state: Mobility is UE-based cell selection and reselection, there is a connection between CN and NR, UE AS context exists on a certain base station, paging is triggered by RAN, and the RAN-based paging area is managed by RAN, the network side Knowing the location of the UE is based on the paging area level of the RAN.

In order to facilitate understanding of the embodiment of the present application, the following briefly describes the random access process involved in the embodiment of the present application.

The random access process is mainly triggered by the following events:

1. The wireless connection is established when the UE initially accesses: the UE changes from the RRC_IDLE state to the RRC_CONNECTED state.

2. RRC connection re-establishment process: so that the UE can re-establish the radio connection after the radio link fails.

3. Handover: UE needs to establish uplink synchronization with the new cell.

4. In the RRC_CONNECTED state, the downlink (DL) data arrives, and the UL is in an out-of-sync state at this time.

5. In the RRC_CONNECTED state, the uplink (uplink, UL) data arrives. At this time, the UL is in an out-of-sync state or there is no PUCCH resource for sending a scheduling request (scheduling request, SR).

6. SR failed.

7. Synchronous reconfiguration request from RRC.

8. The UE transitions from the RRC_INACTIVE state to the RRC_CONNECTED state.

9. Time calibration is established during the process of adding a secondary serving cell (SCell).

10. Request other system information (OSI).

11. Beam failure recovery.

At present, in the NR system, the following two random access methods are mainly supported: a contention-based random access method and a non-contention-based random access method. The contention-based random access process includes 4 steps, and the non-contention-based random access process includes 2 steps. The delay overhead of the 4-step random access process is relatively large, and it is not suitable for low-latency and high-reliability scenarios in 5G. Compared with the 4-step random access process, the 2-step random access process can reduce the access delay.

FIG. 2 is a schematic diagram of a contention-based random access process provided by an embodiment of the present application. As shown in Figure 2, the random access process 200 may include the following steps:

Step 201, the terminal device sends Msg1 to the network device.

The terminal device sends Msg1 to the network device through the physical random access channel PRACH. Msg1 includes a random access preamble, and the random access preamble in Msg1 is selected by the terminal device from the random access preamble set configured by the network device.

Step 202, the network device sends Msg2 including a random access response (random access response, RAR) to the terminal device.

RAR is used to inform the terminal device of the physical uplink shared channel (PUSCH) resource that can be used when sending Msg3, allocate aadio network temporary identifier (RNTI) to the terminal device, and provide the terminal device with timing advance time advance command and so on.

Step 203, the terminal device sends Msg3 to the network device according to the RAR instruction.

After sending the Msg1, the terminal device opens a random access response time window ra-ResponseWindow, and monitors the physical downlink control channel (physical downlink control channel, PDCCH) scrambled by the RA-RNTI within the time window. The RA-RNTI is related to the PRACH time-frequency resource used by the terminal equipment to send Msg1.

After the terminal device successfully receives the PDCCH scrambled by the RA-RNTI, the terminal device can obtain the physical downlink shared channel (physical downlink shared channel, PDSCH) scheduled by the PDCCH, which contains the RAR, and the RAR may contain at least one of the following information:

1. The subheader of RAR contains BI, which is used to indicate the fallback time of retransmitting Msg1;

2. Random access preamble ID (RAPID) in RAR: the preamble index received by the network response;

3. The payload of RAR contains TAG, which is used to adjust the uplink timing;

4. Uplink authorization UL grant: used to schedule the uplink resource indication of Msg3;

5.Temporary C-RNTI: PDCCH (initial access) used to scramble Msg4.

The terminal device sends Msg3 on the PUSCH resource specified by the RAR, and the Msg3 is mainly used to notify the network device of what event triggers the random access process. For example, if it is an initial access random process, Msg3 will carry UE ID and establishment cause; if it is RRC reconstruction, it will carry connection state UE ID and establishment cause. The terminal starts RA-ContentionResolutionTimer after sending Msg3, and monitors PDCCH to receive Msg4 while the timer is running.

Step 204, the network device sends Msg4 to the terminal device.

Msg4 has two functions, one is to resolve contention conflicts, and the other is to transmit RRC configuration messages from network equipment to terminal equipment. There are two methods for contention conflict resolution: one is that if the terminal device carries less than RNTI (cell-RNTI, C-RNTI) in Msg3, Msg4 uses C-RNTI to scramble PDCCH scheduling. The other is that if the terminal equipment does not carry C-RNTI in Msg3, such as initial access, then Msg4 uses temporary C-RNTI (temporary C-RNTI, TC-RNTI) scrambled PDCCH scheduling. The conflict resolution is that the terminal device receives the PDSCH of Msg4, and matches the common control channel (common control channel, CCCH) service data unit (service data unit, SDU) in the PDSCH.

In other words, Msg4 includes a contention resolution message, and at the same time allocates uplink transmission resources for the terminal equipment. When the terminal receives Msg4 sent by the network device, it will check whether the specific temporary identifier of the terminal device sent by the terminal device in Msg3 is included in the contention resolution message sent by the network device. If it is included, it indicates that the random access process of the terminal device is successful. , otherwise it is considered that the random access procedure has failed, and the terminal device needs to start the random access procedure from step 201 again.

FIG. 3 is a schematic diagram of a non-contention-based random access procedure provided by an embodiment of the present application. As shown in FIG. 3, the random access process 300 may include the following steps:

Step 301, the terminal device sends MsgA to the network device.

MsgA includes Msg1 and Msg3 in the aforementioned 4-step random access process. For example, MsgA includes a preamble, an identifier of a terminal device, and a PUSCH part. Among them, the random access opportunity (RACH occasion, RO) where the preamble is located is the same as the aforementioned 4-step random access process, and can be configured through the network, and its RO can be shared with the RO of the aforementioned 4-step random access process, or can be configured separately . The time-frequency resource where the PUSCH is located is called PUSCH occasion (PO). One PO can contain multiple PUSCH resource units (PUSCH resource unit, PRU), one PRU contains PUSCH resource and demodulation reference signal (demodulation reference signal, DMRS), and DMRS contains DMRS port (DMRS port) and DMRS sequence. PO is also configured through the network, its period is the same as that of RO, and the two have an associated relationship.

Step 302, the network device sends the MsgB to the terminal device.

MsgB includes Msg2 and Msg4 in the aforementioned 4-step random access process.

MsgB includes a contention resolution message, and at the same time allocates uplink transmission resources for the terminal equipment. When the terminal device receives the MsgB sent by the network device, it will detect whether the terminal device-specific temporary identifier sent by the terminal device in MsgA is included in the contention resolution message sent by the network device. If it is included, it indicates that the random access process of the terminal device is successful. Otherwise, it is considered that the random access procedure fails, and the terminal device needs to initiate the random access procedure from step 301 again.

It can be seen from the above random access process that the main purpose of random access is to obtain uplink synchronization between the terminal equipment and the cell. In the random access process, the network device can know the time when the terminal device sends the preamble according to the RACH time-frequency resource used to receive the preamble from the terminal device, and then determine the terminal device's time according to the sending time and receiving time of the preamble. The initial timing advances (time advance, TA), and informs the terminal through the RAR.

It should be noted that the technical solutions provided by the embodiments of the present application are mainly aimed at the random access procedure shown in FIG. 2 .

The following briefly describes the random access channel (RACH) configuration in the NR system.

The RACH configuration is notified by the network to the terminal equipment through broadcasting. The RACH configuration includes RACH time-frequency resource configuration and initial preamble root sequence configuration.

RACH time-domain resource configuration: Indicated by one RACH configuration index, the RACH resource repetition period can be known through the RACH configuration index, the number of ROs included in one RACH resource repetition period, the duration of each RO, etc.

RACH frequency domain resource configuration: including 1 RACH starting frequency domain resource index and the number of RACH resources that can be frequency division multiplexed at the same time (that is, the number of continuous RACH frequency domain resources), which can be determined through RACH frequency domain resource configuration The RACH frequency domain resources are a segment of continuous frequency domain resources.

Each cell broadcasts an initial preamble root sequence, and based on the configured initial preamble root sequence, the available preamble set of the cell can be obtained through cyclic shift.

At present, for the uplink coverage enhancement in the NR system, one implementation method is to introduce repetition transmission (that is, a retransmission mechanism) for the Msg3 PUSCH transmission in the random access process, so as to achieve the purpose of enhancing the Msg3 coverage. The terminal device may request Msg3 PUSCH retransmission through Msg1 at least according to downlink coverage conditions, for example, when the reference signal received power (reference signal received power, RSRP) measurement value is lower than a pre-configured threshold. After receiving the specific Msg1, the network device can allocate enhanced Msg3 resources for retransmission to the terminal device through the UL grant in the RAR in Msg2.

During random access, the monitoring of Msg4 is controlled by RA-ContentionResolutionTimer. In the current NR system, RA-ContentionResolutionTimer is started after Msg3 transmission. After introducing Msg3 PUSCH repetition, how to start RA-ContentionResolutionTimer is a problem that needs to be solved by the standard. If it starts after all Msg3 repetitions are transmitted, it means that the terminal device expects the network to respond with Msg4 after receiving all Msg3 repetitions. This is suitable for terminal devices with half-duplex capability (such as RedCap terminal devices), because such terminal devices can start to monitor the downlink only after sending the PUSCH anyway. However, for a terminal device with full-duplex capability, it is possible to transmit and receive at the same time. If the network device successfully receives Msg3 only through part of the Msg3 repetition, it can respond to Msg4 as soon as possible, so that if the terminal device receives Msg4 while still transmitting the remaining Msg3 repetition, the terminal device can terminate the remaining Msg3 repetition, achieving saving The purpose of power consumption, while saving uplink resources and reducing uplink interference. It can be seen that for different capabilities or types of terminal equipment, it will affect the realization of the network side.

Therefore, in the process of random access, since different capabilities or types of terminal devices may start RA-ContentionResolutionTimer in different ways, how the terminal device informs the network side of its device capability or type so that the network can make corresponding feedback is an urgent problem to be solved. .

In the embodiment of this application, in view of the differences in the random access process of terminal devices of different capabilities or types, when a terminal device initiates a random access request, it can inform the network of its device capabilities by sending resources and/or sending content or type. Based on this method, the network can configure corresponding RACH resources for different capabilities or types of terminal equipment, and/or configure corresponding preamble sets based on different capabilities or types of terminal equipment, so that the terminal equipment can select the corresponding preamble set according to its own capabilities or types. A target RACH resource and a target preamble corresponding to the capability or type, and the target preamble is sent on the target RACH resource. The network can know the capability or type of the terminal equipment by receiving the above transmission from the terminal equipment, so as to send corresponding contention resolution messages, which can improve the transmission performance of the entire communication system. If the terminal device has full-duplex capability, the terminal device can terminate the retransmission of Msg3 PUSCH in advance according to the contention resolution message of successful random access sent by the network, to achieve the purpose of saving power, and at the same time shorten the random access time and save uplink resources , to reduce uplink interference.

The technical solutions provided by the embodiments of the present application will be described in detail below through specific embodiments. It should be noted that the technical solutions provided by the embodiments of this application may include part or all of the following content, the following specific embodiments may be combined with each other, and the same or similar concepts or processes may be used in some embodiments No longer.

FIG. 4 is a first schematic diagram of an information transmission method provided by an embodiment of the present application. As shown in Figure 4, the information transmission method may include the following steps:

Step 401, the terminal device sends the target preamble to the network device on the time-frequency domain resource of the target random access channel RACH resource pool.

In this embodiment, the target RACH resource may be determined by the terminal device from at least one RACH resource pool configured by the network device according to its device information.

In a possible design, the number of RACH resources configured by the network device is two, for example, the two RACH resource pools configured by the network device include a first RACH resource pool and a second RACH resource pool. The first RACH resource pool is only used by the first type of terminal equipment, and the second RACH resource pool is only used by the second type of terminal equipment.

At least one piece of information in the device information of the first type of terminal device is different from that of the second type of terminal device. Optionally, the device information of the terminal device may include at least one of the following information:

Information 1: device type.

Information 2: whether it has the capability of physical uplink shared channel PUSCH early termination (early PUSCH termination).

Information 3: Whether it has full-duplex capability.

In an optional embodiment of this embodiment, the device type includes a reduced capability (reduced capability, RedCap) type and a non-RedCap (non-RedCap) type.

In an optional embodiment of this embodiment, the device type includes a full-duplex type and a half-duplex type.

The following briefly describes the performance of the above-mentioned different types of terminal equipment.

1. The RedCap type terminal has the characteristics of reduced bandwidth, reduced processing speed, and reduced number of antennas.

2. The terminal of the full-duplex type supports sending and receiving messages, and can receive and send messages (signaling and/or data) at the same time.

3. Half-duplex terminals support sending and receiving messages, but can only receive or send messages at the same time.

4. A terminal with PUSCH early termination capability can terminate the remaining Msg3 PUSCH repetitions when the network device successfully receives Msg3 only through part of the Msg3 PUSCH repetitions, so as to save power, save uplink resources and reduce uplink interference.

Exemplarily, the first type of terminal device may be a non-RedCap type terminal device, and the second type of terminal device may be a RedCap type terminal device. Alternatively, the terminal device of the first type may be a terminal device of the RedCap type, and the terminal device of the second type may be a terminal device of the non-RedCap type.

Exemplarily, the first type of terminal device may be a terminal device with full duplex capability, and the second type of terminal device may be a terminal device without full duplex capability (for example, half duplex capability). Alternatively, the first type of terminal device may be a terminal device without full-duplex capability (for example, half-duplex capability), and the second type of terminal device may be a terminal device with full-duplex capability.

Exemplarily, the first type of terminal device may be a terminal device capable of PUSCH early termination, and the second type of terminal device may be a terminal device not capable of PUSCH early termination. Alternatively, the first type of terminal device may be a terminal device not capable of PUSCH early termination, and the second type of terminal device may be a terminal device capable of PUSCH early termination.

In the above design, terminal devices of different types or capabilities can use different RACH resource pools to initiate random access requests, and network devices can learn the identity of the terminal device that initiated the random access request by receiving random access requests on different RACH resource pools. type or capability, so as to perform contention resolution message transmission corresponding to the type or capability of the terminal device.

For example, taking the 4-step random access process as an example, the network device determines that the terminal device that initiates the request has full-duplex capability according to the RACH resource pool that receives the random access request. Msg3 (that is, part of Msg3) successfully receives Msg3, then it can directly return Msg4 to the terminal device, so that the terminal device can terminate the remaining Msg3 retransmission in advance, so as to realize the purpose of energy saving of the terminal device, save uplink resources and reduce uplink interference.

The following describes in detail the time-frequency resources of at least two RACH resource pools configured by the network. For ease of understanding, two RACH resource pools, such as the time-frequency domain configuration of the first RACH resource pool and the second RACH resource pool, are taken as an example for illustration. For more than two RACH resource pools, the time-frequency domain configurations of any two RACH resource pools may refer to the following time-frequency domain configurations of the first RACH resource pool and the second RACH resource pool.

FIG. 5 is a first schematic diagram of the configuration of the RACH resource pool provided by the embodiment of the present application. Figure 6 is a schematic diagram of the configuration of the RACH resource pool provided by the embodiment of the present application II, Figure 7 is a schematic diagram of the configuration of the RACH resource pool provided by the embodiment of the present application III, Figure 8 is a schematic diagram of the configuration of the RACH resource pool provided by the embodiment of the present application IV , FIG. 9 is a fifth schematic diagram of the configuration of the RACH resource pool provided by the embodiment of the present application.

In an optional embodiment of this embodiment, the time domain resources of the first RACH resource pool do not overlap with the time domain resources of the second RACH resource pool. This embodiment only limits the positional relationship in the time domain between the time domain resources of the first RACH resource pool and the second RACH resource pool, that is, the time domain resources of the first RACH resource pool and the second RACH resource pool are different.

In an optional embodiment of this embodiment, the frequency domain resources of the first RACH resource pool do not overlap with the frequency domain resources of the second RACH resource pool. This embodiment only limits the positional relationship of the frequency domain resources of the first RACH resource pool and the second RACH resource pool in the frequency domain, that is, the frequency domain resources of the first RACH resource pool and the second RACH resource pool are different.

In an optional embodiment of this embodiment, the time domain resources of the first RACH resource pool do not overlap with the time domain resources of the second RACH resource pool, and the frequency domain resources of the first RACH resource pool and the second RACH resource pool The frequency domain resources of all overlap. In other words, in this embodiment, the time domain resources of the first RACH resource pool and the second RACH resource pool are different, and the frequency domain resources of the first RACH resource pool and the second RACH resource pool are the same, as shown in FIG. 5 .

In an optional embodiment of this embodiment, the time domain resources of the first RACH resource pool do not overlap with the time domain resources of the second RACH resource pool, and the frequency domain resources of the first RACH resource pool and the second RACH resource pool The frequency domain resources of are partially overlapped. In other words, in this embodiment, the time domain resources of the first RACH resource pool and the second RACH resource pool are different, and the frequency domain resources of the first RACH resource pool and the second RACH resource pool are not completely the same, as shown in FIG. 6 .

In an optional embodiment of this embodiment, the frequency domain resources of the first RACH resource pool do not overlap with the frequency domain resources of the second RACH resource pool, and the time domain resources of the first RACH resource pool and the second RACH resource pool The time domain resources of all overlap. In other words, in this embodiment, the frequency domain resources of the first RACH resource pool and the second RACH resource pool are different, and the time domain resources of the first RACH resource pool and the second RACH resource pool are the same, as shown in FIG. 7 .

In an optional embodiment of this embodiment, the frequency domain resources of the first RACH resource pool do not overlap with the frequency domain resources of the second RACH resource pool, and the time domain resources of the first RACH resource pool and the second RACH resource pool The time domain resources of . In other words, in this embodiment, the frequency domain resources of the first RACH resource pool and the second RACH resource pool are different, and the time domain resources of the first RACH resource pool and the second RACH resource pool are not completely the same, as shown in FIG. 8 .

In an optional embodiment of this embodiment, the time domain resources of the first RACH resource pool do not overlap with the time domain resources of the second RACH resource pool, and the frequency domain resources of the first RACH resource pool and the second RACH resource pool There is no overlapping of frequency domain resources. In other words, in this embodiment, the time domain resources and frequency domain resources of the first RACH resource pool and the second RACH resource pool are different, as shown in FIG. 9 .

In an optional embodiment of this embodiment, the frequency domain resources in the first RACH resource pool and the frequency domain resources in the second RACH resource pool are continuous frequency domain resources with a preset length, as shown in FIG. 5 to FIG. 9 Show.

In an optional embodiment of this embodiment, the time-frequency two-dimensional resources of the first RACH resource pool do not overlap with the time-frequency two-dimensional resources of the second RACH resource pool. In this embodiment, both the first RACH resource pool and the second RACH resource pool include a plurality of resource blocks, and each resource block corresponds to a preset length of continuous time domain resources and a preset length of continuous frequency domain resources. Any resource block in the first RACH resource pool has no overlapping area with any resource block in the second RACH resource pool, as shown in FIGS. 5 to 9 .

In another possible design, the number of RACH resources configured by the network device is one, for example, the network device configures a third RACH resource pool. The third RACH resource pool can be used by terminal devices of various types or capabilities. Different terminal devices select RACH resources from the third RACH resource pool through resource competition.

In the above design, terminal devices of different types or capabilities can use different resource blocks in the same RACH resource pool to initiate random access requests, and the network device can learn the terminal device that initiated the random access request by analyzing the random access request of the terminal device type or capability of the terminal device, so as to perform contention resolution message sending corresponding to the type or capability of the terminal device. The random access request includes a target preamble selected by the terminal device, and the target preamble may indicate the type or capability of the terminal device.

In the above design, terminal devices of different types or capabilities may select the same or different RACH resource blocks from the third RACH resource pool. Exemplarily, if the terminal device of the first type and the terminal device of the second type select the same RACH resource block from the third RACH resource pool, the network device can learn that each The device type or capability of the end device.

In yet another possible design, the number of RACH resource pools configured by the network device is three or more. If the types or capabilities of terminal equipment include three or more types, each type or capability of terminal equipment corresponds to a specific RACH resource pool, and each type or capability of terminal equipment can select from its corresponding RACH resource pool The resources are selected in the random access process.

Exemplarily, taking three types of terminal devices as an example, the network device configures three RACH resource pools, namely a first RACH resource pool, a second RACH resource pool and a third RACH resource pool. Wherein, the first RACH resource pool is only used by the first type of terminal equipment, the second RACH resource pool is only used by the second type of terminal equipment, and the third RACH resource pool is only used by the third type of terminal equipment. In this embodiment, the device types may be divided according to actual application requirements, and this embodiment does not limit the division method.

Optionally, in some embodiments, the network device configures a RACH resource pool, such as the third RACH resource pool, and the terminal device first determines the target synchronization signal and a physical broadcast channel PBCH block (Synchronization Signal and PBCH block, SSB for short), Then select the target RACH resource from the random access opportunity RO resource corresponding to the target SSB (ie, the RO resource of the target SSB in the third RACH resource pool).

Optionally, in some embodiments, the network device configures two RACH resource pools, such as a first RACH resource pool and a second RACH resource pool, and the terminal device first selects from the two RACH resource pools according to its device type or capability A target RACH resource pool, and then determine the target SSB, and then select the target RACH resource from the RO resource corresponding to the target SSB (for example, the RO resource of the target SSB in the first RACH resource pool or the second RACH resource pool).

In this embodiment, the target preamble may be determined by the terminal device from at least one preamble set configured by the network device according to its device information.

In a possible design, the number of preamble sets configured by the network device is two, for example, the two preamble sets configured by the network device include a first preamble set and a second preamble set. The first preamble set is only used by the first type of terminal equipment, and the second preamble set is only used by the second type of terminal equipment.

At least one piece of information in the device information of the first type of terminal device is different from that of the second type of terminal device. For the information specifically included in the device information of the terminal device, please refer to the above, and will not go into details here.

Optionally, the first set of preambles and the second set of preambles do not overlap at all. It should be understood that both the first preamble set and the second preamble set include multiple preambles, and any preamble in the first preamble set is different from any preamble in the second preamble set.

In the above design, terminal devices of different types or capabilities can select preambles in different preamble sets to initiate random access requests, and network devices can obtain the terminal that initiated the random access request by reading the preambles in the random access request. The type or capability of the device, so as to perform contention resolution message sending corresponding to the type or capability of the terminal device.

In another possible design, the number of preamble sets configured by the network device is one, for example, the network device is configured with a third preamble set. The third set of preambles may be used by terminal devices of different types or capabilities.

In the above design, terminal devices of different types or capabilities may select the same or different target preambles from the third preamble set. Exemplarily, if the terminal device of the first type and the terminal device of the second type select the same target preamble from the third preamble set, the network device can send the target preamble RACH resource through the terminal device to know that each terminal The device type of the device, where the two types of terminal devices use the same target preamble sent by using different RACH resources.

In yet another possible design, the number of preamble sets configured by the network device is three or more. If the types or capabilities of terminal equipment include three or more types, each type or capability of terminal equipment corresponds to a specific preamble set, and each type or capability of terminal equipment can select from its corresponding preamble set Select the target preamble.

Exemplarily, taking three types of terminal devices as an example, the network device is configured with three preamble sets, namely a first preamble set, a second preamble set and a third preamble set. Wherein, the first preamble set is only used by the first type of terminal equipment, the second preamble set is only used by the second type of terminal equipment, and the third preamble set is only used by the third type of terminal equipment.

In the information transmission method shown in the above embodiments, the terminal device sends the target preamble to the network device on the target RACH resource pool, so that the network device determines the type or capability of the terminal device according to the target RACH resource pool and/or the target preamble, so as to make relevant The transmission of the corresponding contention resolution message can improve the transmission performance of the entire communication system. If the terminal device has full-duplex capability, the terminal device can terminate the retransmission of Msg3 PUSCH in advance according to the contention resolution message of successful random access sent by the network, to achieve the purpose of saving power, and at the same time shorten the random access time and save uplink resources , to reduce uplink interference.

Optionally, in some embodiments, if the terminal equipment is a terminal equipment of the first type, after the terminal equipment sends the target preamble to the network equipment on the target RACH resource pool, the following steps are included: A random access contention resolution timer (RA-ContentionResolutionTimer) is started or restarted on the first symbol (symbol) after a retransmission.

Optionally, in some embodiments, if the terminal device is a terminal device of the first type, after the terminal device sends the target preamble to the network device on the target RACH resource pool, the following steps are included: if the terminal device receives the correct contention resolution message, and the number of retransmissions of Msg3 PUSCH is less than the preset number of times, the terminal device terminates the retransmission of the remaining Msg3 PUSCH. Wherein, the preset times can be configured or preconfigured by the network.

Optionally, in some embodiments, if the network device determines that the terminal device sending the target preamble is the first type of terminal device, and the network device successfully receives Msg3 only through partial Msg3 retransmission, then there is no need to wait for the rest of the Msg3 retransmission Then, the contention resolution message can be sent to the terminal device.

In the above several embodiments, the terminal device of the first type may be a terminal device of a non-RedCap type, or a terminal device capable of full duplex, or a terminal device capable of PUSCH early termination.

Optionally, in some embodiments, if the terminal device is a second type of terminal device, after the terminal device sends the target preamble to the network device on the target RACH resource pool, the following steps are included: The random access contention resolution timer is started or restarted on the first symbol after a retransmission.

Optionally, in some embodiments, if the network device determines that the terminal device sending the target preamble is the second type of terminal device, the network device needs to receive all Msg3 retransmissions (that is, receive a preset number of Msg3 retransmissions) After that, a contention resolution message is sent to the terminal device.

In the above several embodiments, the terminal device of the second type may be a terminal device of the RedCap type, or a terminal device without full-duplex capability, or a terminal device without PUSCH early termination capability.

FIG. 10 is a second schematic diagram of the information transmission method provided by the embodiment of the present application. As shown in Figure 10, the information transmission method may include the following steps:

Step 501, the network device sends configuration information to the terminal device.

In this embodiment, the configuration information includes at least one of the following configurations:

At least one RACH resource pool; at least one preamble set.

In an optional embodiment of this embodiment, the configuration information includes configuration of at least one RACH resource pool.

In an optional embodiment of this embodiment, the configuration information includes configuration of at least one preamble set.

In an optional embodiment of this embodiment, the configuration information includes configurations of one RACH resource pool and at least two preamble sets.

In an optional embodiment of this embodiment, the configuration information includes configurations of at least two RACH resource pools and one preamble set.

In an optional embodiment of this embodiment, the configuration information includes the configuration of a RACH resource pool and a preamble set.

For at least one RACH resource configured for the network device, reference may be made to the foregoing embodiments, and details are not repeated here.

For the at least one preamble set configured for the network device, reference may be made to the foregoing embodiments, and details are not repeated here.

Step 502, the terminal device sends the target preamble to the network device on the time-frequency domain resources of the target RACH resource pool according to the configuration information. (optional)

In an optional embodiment of this embodiment, the terminal device selects a target RACH resource pool from at least one RACH resource pool according to the configuration information, and selects a target preamble from at least one preamble set according to the configuration information, so that the terminal device can select a target RACH resource pool from at least one RACH resource pool according to the configuration information. The target preamble is sent to the network device on the time-frequency domain resources of the RACH resource pool. It should be noted that this embodiment does not limit the execution sequence of selecting a target RACH resource pool and selecting a target preamble by the terminal device. In some embodiments, the terminal device may also perform the step of selecting the target RACH resource pool and the target preamble at the same time.

In the information transmission method shown in the above embodiments, the terminal device receives the configuration information of the network device, selects the target RACH resource pool and the target preamble corresponding to the type or capability of the terminal device according to the configuration information, and transmits the target RACH resource on the target RACH resource. The target preamble informs the network device of its type or capability, so that the network device can send corresponding contention resolution messages for terminal devices of different types or capabilities, which can improve the transmission performance of the entire communication system. If the terminal device has full-duplex capability, the terminal device can terminate the retransmission of Msg3 PUSCH in advance according to the contention resolution message of successful random access sent by the network, to achieve the purpose of saving power, and at the same time shorten the random access time and save uplink resources , to reduce uplink interference.

FIG. 11 is a schematic structural diagram of a terminal device provided by an embodiment of the present application. As shown in FIG. 11 , the terminal device 600 in this embodiment includes: a sending module 601 , a receiving module 602 and a processing module 603 .

The sending module 601 is configured to send the target preamble to the network device on the time-frequency domain resource of the target random access channel RACH resource pool;

The target RACH resource pool is determined from at least one RACH resource pool configured by the network device according to the device information of the terminal device, and the target preamble is determined from the network device according to the device information of the terminal device determined in at least one preamble set configured.

In an optional embodiment of the present application, if the network device is configured with two RACH resource pools, the two RACH resources include a first RACH resource pool and a second RACH resource pool;

The first RACH resource pool is only used by terminal equipment of the first type, and the second RACH resource pool is only used by terminal equipment of the second type; the terminal equipment of the first type and the terminal equipment of the second type At least one piece of information in the device information of the terminal device is different.

In an optional embodiment of the present application, the time domain resources of the first RACH resource pool do not overlap with the time domain resources of the second RACH resource pool.

In an optional embodiment of the present application, the frequency domain resources of the first RACH resource pool do not overlap with the frequency domain resources of the second RACH resource pool.

In an optional embodiment of the present application, the time domain resources of the first RACH resource pool do not overlap with the time domain resources of the second RACH resource pool, and the frequency domain resources of the first RACH resource pool and All or part of the frequency domain resources of the second RACH resource pool overlap.

In an optional embodiment of the present application, the frequency domain resources of the first RACH resource pool do not overlap with the frequency domain resources of the second RACH resource pool, and the time domain resources of the first RACH resource pool and All or part of the time domain resources of the second RACH resource pool overlap.

In an optional embodiment of the present application, the time domain resources of the first RACH resource pool do not overlap with the time domain resources of the second RACH resource pool, and the frequency domain resources of the first RACH resource pool and The frequency domain resources of the second RACH resource pool do not overlap.

In an optional embodiment of the present application, both the frequency domain resources of the first RACH resource pool and the frequency domain resources of the second RACH resource pool are continuous frequency domain resources of a preset length.

In an optional embodiment of the present application, the time-frequency two-dimensional resources of the first RACH resource pool do not overlap with the time-frequency two-dimensional resources of the second RACH resource pool.

In an optional embodiment of the present application, if the network device configures a third RACH resource pool; the sending module 601 is specifically used for:

sending the target preamble to the network device on the time-frequency domain resource of the third RACH resource pool.

In an optional embodiment of the present application, if the network device is configured with two sets of preambles, the two sets of preambles include a first set of preambles and a second set of preambles;

The first preamble set is only used by the first type of terminal equipment, and the second preamble set is only used by the second type of terminal equipment; the first type of terminal equipment and the second type of terminal equipment At least one piece of information in the device information of the terminal device is different.

In an optional embodiment of the present application, the first preamble set and the second preamble set do not overlap at all.

In an optional embodiment of the present application, the device information of the terminal device includes at least one of the following information:

Equipment type;

Whether it has the ability to terminate the early PUSCH termination of the physical uplink shared channel PUSCH in advance;

Whether it has full-duplex capability.

In an optional embodiment of the present application, the receiving module 602 is configured to:

Receive configuration information from the network device, where the configuration information includes at least one of the following configurations: the at least one RACH resource pool; the at least one preamble set.

In an optional embodiment of the present application, if the terminal device is a first type of terminal device, the processing module 603 is configured to start or Restart the random access contention resolution timer.

In an optional embodiment of the present application, if the terminal device is a first type of terminal device, if the receiving module 602 receives a correct contention resolution message, and the number of retransmissions of Msg3 PUSCH is less than the preset number of times, Then the processing module 603 is configured to terminate the retransmission of the remaining Msg3 PUSCH.

In an optional embodiment of the present application, if the terminal device is a second type of terminal device, the processing module 603 is configured to start or restart on the first symbol after the last retransmission of Msg3 PUSCH Random access contention resolution timer.

In an optional embodiment of the present application, the first type of terminal device is a terminal device with full-duplex capability, or a terminal device with PUSCH early termination capability, or a non-capability-reduced non-RedCap type Terminal Equipment.

In an optional embodiment of the present application, the second type of terminal device is a terminal device without full-duplex capability, or a terminal device without PUSCH early termination capability, or a terminal of RedCap type with reduced capability equipment.

The terminal device provided in the embodiments of the present application is used to implement the technical solution performed by the terminal device in any of the foregoing method embodiments, and its implementation principles and technical effects are similar, and details are not repeated here.

FIG. 12 is a schematic structural diagram of a network device provided by an embodiment of the present application. As shown in FIG. 12 , the network device 700 of this embodiment includes: a receiving module 701 and a sending module 702 .

The receiving module 701 is configured to receive the target preamble from the terminal device on the time-frequency domain resource of the target random access channel RACH resource pool;

In an optional embodiment of the present application, if the network device configures a third RACH resource pool; the receiving module 701 is specifically configured to:

Receive the target preamble from the terminal device on time-frequency domain resources of the third RACH resource pool.

Equipment type;

Whether it has full-duplex capability.

In an optional embodiment of the present application, the first type of terminal device is a terminal device with full-duplex capability, and the second type of terminal device is a terminal device without full-duplex capability.

In an optional embodiment of the present application, the first type of terminal device is a terminal device capable of PUSCH early termination, and the second type of terminal device is a terminal device not capable of PUSCH early termination.

In an optional embodiment of the present application, the first type of terminal device is a non-RedCap type terminal device with reduced capabilities, and the second type of terminal device is a RedCap type terminal device with reduced capabilities.

In an optional embodiment of the present application, the sending module 702 is configured to:

Send configuration information to the terminal device, where the configuration information includes at least one of the following configurations: the at least one RACH resource pool; the at least one preamble set.

The network device provided in the embodiments of the present application is used to implement the technical solution performed by the network device in any of the foregoing method embodiments, and its implementation principles and technical effects are similar, and details are not repeated here.

It should be noted that it should be understood that the above division of each module of the terminal device or network device is only a division of logical functions, and may be fully or partially integrated into one physical entity or physically separated during actual implementation. And these modules can all be implemented in the form of calling software through processing elements; they can also be implemented in the form of hardware; some modules can also be implemented in the form of calling software through processing elements, and some modules can be implemented in the form of hardware. For example, the processing module can be a separate processing element, or it can be integrated into a chip of the above-mentioned device. In addition, it can also be stored in the memory of the above-mentioned device in the form of program code, and a certain processing element of the above-mentioned device can Call and execute the functions of the modules identified above. The implementation of other modules is similar. In addition, all or part of these modules can be integrated together, and can also be implemented independently. The processing element mentioned here may be an integrated circuit with signal processing capability. In the implementation process, each step of the above method or each module above can be completed by an integrated logic circuit of hardware in the processor element or an instruction in the form of software.

For example, the above modules may be one or more integrated circuits configured to implement the above method, for example: one or more specific integrated circuits (application specific integrated circuit, ASIC), or, one or more microprocessors (digital signal processor, DSP), or, one or more field programmable gate arrays (field programmable gate array, FPGA), etc. For another example, when one of the above modules is implemented in the form of a processing element scheduling program code, the processing element may be a general-purpose processor, such as a central processing unit (central processing unit, CPU) or other processors that can call program codes. For another example, these modules can be integrated together and implemented in the form of a system-on-a-chip (SOC).

In the above embodiments, all or part of them may be implemented by software, hardware, firmware or any combination thereof. When implemented using software, it 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 the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server, or data center Transmission to another website site, computer, server, or data center by wired (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, 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 or a data center integrated with one or more available media. The available medium may be a magnetic medium (such as a floppy disk, a hard disk, or a magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (SSD)).

FIG. 13 is a schematic diagram of a hardware structure of a terminal device provided by an embodiment of the present application. As shown in FIG. 13, the terminal device 800 in this embodiment may include:

Transceiver 801, processor 802, memory 803;

The memory 803 stores computer-executable instructions;

The processor 802 executes the computer-executed instructions stored in the memory 803, so that the processor 802 executes the technical solution of the terminal device in any of the foregoing method embodiments.

Optionally, the memory 803 can be independent or integrated with the processor 802 . When the memory 803 is a device independent of the processor 802, the electronic device 800 may further include: a bus 804, configured to connect the memory 803 and the processor 802.

Optionally, the processor 802 may be a chip.

The terminal device provided in this embodiment can be used to execute the method performed by the terminal device in any of the foregoing method embodiments, and its implementation principles and technical effects are similar, and will not be repeated here.

FIG. 14 is a schematic diagram of a hardware structure of a network device provided by an embodiment of the present application. As shown in FIG. 14, the network device 900 of this embodiment may include:

Transceiver 901, processor 902, memory 903;

The memory 903 stores computer-executable instructions;

The processor 902 executes the computer-executed instructions stored in the memory 903, so that the processor 902 executes the technical solution of the network device in any of the foregoing method embodiments.

Optionally, the memory 903 can be independent or integrated with the processor 902 . When the memory 903 is a device independent of the processor 902 , the electronic device 900 may further include: a bus 904 , configured to connect the memory 903 and the processor 902 .

Optionally, the processor 902 may be a chip.

The network device provided in this embodiment can be used to implement the method performed by the network device in any of the foregoing method embodiments, and its implementation principles and technical effects are similar, and will not be repeated here.

An embodiment of the present application further provides a storage medium, where a computer program is stored in the storage medium, and when the computer program is executed by a processor, it is used to implement the technical solution of the terminal device in any of the foregoing method embodiments.

The embodiment of the present application further provides a program, which is used to implement the technical solution of the terminal device in any of the foregoing method embodiments when the program is executed by a processor.

An embodiment of the present application further provides a computer program product, including program instructions, and the program instructions are used to implement the technical solution of the terminal device in any one of the foregoing method embodiments.

The embodiment of the present application also provides a chip, including: a processing module and a communication interface, where the processing module can implement the technical solutions of the terminal device in the foregoing method embodiments. Further, the chip also includes a storage module (such as a memory), the storage module is used to store instructions, and the processing module is used to execute the instructions stored in the storage module, and the execution of the instructions stored in the storage module makes the processing module execute the instructions of the terminal device. Technical solutions.

An embodiment of the present application further provides a storage medium, where a computer program is stored in the storage medium, and when the computer program is executed by a processor, the technical solution of the network device in any of the preceding method embodiments is implemented.

The embodiment of the present application further provides a program, which is used to execute the technical solution of the network device in any one of the foregoing method embodiments when the program is executed by a processor.

An embodiment of the present application further provides a computer program product, including program instructions, and the program instructions are used to realize the technical solution of the network device in any one of the foregoing method embodiments.

The embodiment of the present application also provides a chip, including: a processing module and a communication interface, where the processing module can implement the technical solution of the network device in the foregoing method embodiment. Further, the chip also includes a storage module (such as a memory), the storage module is used to store instructions, and the processing module is used to execute the instructions stored in the storage module, and the execution of the instructions stored in the storage module makes the processing module execute the instructions of the network device. Technical solutions.

In the present application, "at least two" means two or more, and "multiple" means two or more. "And/or" describes the association relationship of associated objects, indicating that there may be three types of relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, and B exists alone, where A, B can be singular or plural. The character "/" generally indicates that the contextual objects are an "or" relationship; in the formula, the character "/" indicates that the contextual objects are a "division" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one item (piece) of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein, a, b, c can be single or multiple indivual.

It can be understood that the various numbers involved in the embodiments of the present application are only for convenience of description, and are not used to limit the scope of the embodiments of the present application.

It can be understood that, in the embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the order of execution, and the order of execution of the processes should be determined by their functions and internal logic, and should not be used in the implementation of this application. The implementation of the examples constitutes no limitation.

Claims

An information transmission method, characterized in that, comprising:

The terminal device sends the target preamble to the network device on the time-frequency domain resource of the target random access channel RACH resource pool;

The target RACH resource pool is determined from at least one RACH resource pool configured by the network device according to the device information of the terminal device, and the target preamble is determined from the network device according to the device information of the terminal device determined in at least one preamble set configured.
The method according to claim 1, wherein if the network device is configured with two RACH resource pools, the two RACH resources include a first RACH resource pool and a second RACH resource pool;

The first RACH resource pool is only used by terminal equipment of the first type, and the second RACH resource pool is only used by terminal equipment of the second type; the terminal equipment of the first type and the terminal equipment of the second type At least one piece of information in the device information of the terminal device is different.
The method according to claim 2, wherein the time domain resources of the first RACH resource pool do not overlap with the time domain resources of the second RACH resource pool.
The method according to claim 2, wherein the frequency domain resources of the first RACH resource pool do not overlap with the frequency domain resources of the second RACH resource pool.
The method according to claim 2, wherein the time domain resources of the first RACH resource pool do not overlap with the time domain resources of the second RACH resource pool, and the frequency domain resources of the first RACH resource pool The resource completely or partially overlaps with the frequency domain resources of the second RACH resource pool.
The method according to claim 2, wherein the frequency domain resources of the first RACH resource pool do not overlap with the frequency domain resources of the second RACH resource pool, and the time domain resources of the first RACH resource pool The resources completely or partially overlap with the time domain resources of the second RACH resource pool.
The method according to claim 2, wherein the time domain resources of the first RACH resource pool do not overlap with the time domain resources of the second RACH resource pool, and the frequency domain resources of the first RACH resource pool The resources do not overlap with the frequency domain resources of the second RACH resource pool.
The method according to any one of claims 2-7, wherein the frequency domain resources of the first RACH resource pool and the frequency domain resources of the second RACH resource pool are continuous with a preset length frequency domain resources.
The method according to any one of claims 2-8, wherein the time-frequency two-dimensional resources of the first RACH resource pool do not overlap with the time-frequency two-dimensional resources of the second RACH resource pool.
The method according to claim 1, wherein if the network device configures a third RACH resource pool; the target preamble code is sent to the network device on the time-frequency domain resource of the target random access channel RACH resource pool ,include:

sending the target preamble to the network device on the time-frequency domain resource of the third RACH resource pool.
The method according to any one of claims 1-10, wherein if the network device is configured with two sets of preambles, the two sets of preambles include a first set of preambles and a second set of preambles ;

The first preamble set is only used by the first type of terminal equipment, and the second preamble set is only used by the second type of terminal equipment; the first type of terminal equipment and the second type of terminal equipment At least one piece of information in the device information of the terminal device is different.
The method according to claim 11, wherein the first set of preambles and the second set of preambles do not overlap at all.
The method according to any one of claims 1-12, wherein the device information of the terminal device includes at least one of the following information:

Equipment type;

Whether it has the ability to terminate the early PUSCH termination of the physical uplink shared channel PUSCH in advance;

Whether it has full-duplex capability.
The method according to any one of claims 1-13, further comprising:

The terminal device receives configuration information from the network device, where the configuration information includes at least one of the following configurations: the at least one RACH resource pool; the at least one preamble set.
The method according to any one of claims 1-14, wherein if the terminal device is a first type of terminal device, the method further comprises:

The terminal device starts or restarts the random access contention resolution timer on the first symbol after the first retransmission of the Msg3 PUSCH.
The method according to any one of claims 1-15, wherein if the terminal device is a first type of terminal device, the method further comprises:

If the terminal device receives the correct contention resolution message, and the number of retransmissions of the Msg3 PUSCH is less than the preset number of times, the terminal device terminates the retransmission of the remaining Msg3 PUSCH.
The method according to any one of claims 1-14, wherein if the terminal device is a second type of terminal device, the method further comprises:

The terminal device starts or restarts the random access contention resolution timer on the first symbol after the last retransmission of the Msg3 PUSCH.
The method according to any one of claims 2, 11, 15, and 16, wherein the first type of terminal equipment is a terminal equipment with full-duplex capability, or a terminal with PUSCH early termination capability device, or, non-capability-reduced non-RedCap type end-device.
The method according to any one of claims 2, 11, and 17, wherein the second type of terminal equipment is a terminal equipment without full-duplex capability, or a terminal without PUSCH early termination capability equipment, or, reduced-capacity RedCap-type terminal equipment.
An information transmission method, characterized in that, comprising:

The network device receives the target preamble from the terminal device on the time-frequency domain resource of the target random access channel RACH resource pool;

The target RACH resource pool is at least one configured from the network device according to the device information of the terminal device

The target preamble is determined in the RACH resource pool, and the target preamble is determined from at least one preamble set configured by the network device according to the device information of the terminal device.
The method according to claim 20, wherein if the network device is configured with two RACH resource pools, the two RACH resources include a first RACH resource pool and a second RACH resource pool;

The first RACH resource pool is only used by terminal equipment of the first type, and the second RACH resource pool is only used by terminal equipment of the second type; the terminal equipment of the first type and the terminal equipment of the second type At least one piece of information in the device information of the terminal device is different.
The method according to claim 21, wherein the time domain resources of the first RACH resource pool do not overlap with the time domain resources of the second RACH resource pool.
The method according to claim 21, wherein the frequency domain resources of the first RACH resource pool do not overlap with the frequency domain resources of the second RACH resource pool.
The method according to claim 21, wherein the time domain resources of the first RACH resource pool do not overlap with the time domain resources of the second RACH resource pool, and the frequency domain resources of the first RACH resource pool The resource completely or partially overlaps with the frequency domain resources of the second RACH resource pool.
The method according to claim 21, wherein the frequency domain resources of the first RACH resource pool do not overlap with the frequency domain resources of the second RACH resource pool, and the time domain resources of the first RACH resource pool The resources completely or partially overlap with the time domain resources of the second RACH resource pool.
The method according to claim 21, wherein the time domain resources of the first RACH resource pool do not overlap with the time domain resources of the second RACH resource pool, and the frequency domain resources of the first RACH resource pool The resources do not overlap with the frequency domain resources of the second RACH resource pool.
The method according to any one of claims 21-26, wherein the frequency domain resources of the first RACH resource pool and the frequency domain resources of the second RACH resource pool are continuous with a preset length frequency domain resources.
The method according to any one of claims 21-27, wherein the time-frequency two-dimensional resources of the first RACH resource pool do not overlap with the time-frequency two-dimensional resources of the second RACH resource pool.
The method according to claim 20, wherein if the network device configures a third RACH resource pool; the network device receives the target random access channel RACH resource pool from the terminal device on the time-frequency domain resource preamble, including:

The network device receives the target preamble from the terminal device on time-frequency domain resources of the third RACH resource pool.
The method according to any one of claims 20-29, wherein if the network device is configured with two sets of preambles, the two sets of preambles include a first set of preambles and a second set of preambles ;

The first preamble set is only used by the first type of terminal equipment, and the second preamble set is only used by the second type of terminal equipment; the first type of terminal equipment and the second type of terminal equipment At least one piece of information in the device information of the terminal device is different.
The method according to claim 30, wherein the first set of preambles and the second set of preambles do not overlap at all.
The method according to any one of claims 20-31, wherein the device information of the terminal device includes at least one of the following information:

Equipment type;

Whether it has the ability to terminate the early PUSCH termination of the physical uplink shared channel PUSCH in advance;

Whether it has full-duplex capability.
The method according to claim 21 or 30, wherein the first type of terminal equipment is a terminal equipment with full-duplex capability, and the second type of terminal equipment is a terminal without full-duplex capability equipment.
The method according to claim 21 or 30, wherein the first type of terminal equipment is a terminal equipment with PUSCH early termination capability, and the second type of terminal equipment is a terminal without PUSCH early termination capability equipment.
The method according to claim 21 or 30, wherein the first type of terminal equipment is a non-capability-reduced non-RedCap type terminal equipment, and the second type of terminal equipment is a capability-reduced RedCap type terminal equipment.
The method according to any one of claims 20-35, further comprising:

The network device sends configuration information to the terminal device, where the configuration information includes at least one of the following configurations: the at least one RACH resource pool; the at least one preamble set.
A terminal device, characterized in that it includes:

A sending module, configured to send a target preamble to a network device on time-frequency domain resources of a target random access channel RACH resource pool;

The target RACH resource pool is determined from at least one RACH resource pool configured by the network device according to the device information of the terminal device, and the target preamble is determined from the network device according to the device information of the terminal device determined in at least one preamble set configured.
The terminal device according to claim 37, wherein if the network device is configured with two RACH resource pools, the two RACH resources include a first RACH resource pool and a second RACH resource pool;

The first RACH resource pool is only used by terminal equipment of the first type, and the second RACH resource pool is only used by terminal equipment of the second type; the terminal equipment of the first type and the terminal equipment of the second type At least one piece of information in the device information of the terminal device is different.
The terminal device according to claim 38, wherein the time domain resources of the first RACH resource pool do not overlap with the time domain resources of the second RACH resource pool.
The terminal device according to claim 38, wherein the frequency domain resources of the first RACH resource pool do not overlap with the frequency domain resources of the second RACH resource pool.
The terminal device according to claim 38, wherein the time domain resources of the first RACH resource pool do not overlap with the time domain resources of the second RACH resource pool, and the frequency domain resources of the first RACH resource pool The frequency domain resources completely or partially overlap with the frequency domain resources of the second RACH resource pool.
The terminal device according to claim 38, wherein the frequency domain resources of the first RACH resource pool do not overlap with the frequency domain resources of the second RACH resource pool, and the time domain resources of the first RACH resource pool The domain resource completely or partially overlaps with the time domain resource of the second RACH resource pool.
The terminal device according to claim 38, wherein the time domain resources of the first RACH resource pool do not overlap with the time domain resources of the second RACH resource pool, and the frequency domain resources of the first RACH resource pool The frequency domain resources do not overlap with the frequency domain resources of the second RACH resource pool.
The terminal device according to any one of claims 38-43, wherein the frequency domain resources of the first RACH resource pool and the frequency domain resources of the second RACH resource pool are continuous frequency domain resources.
The terminal device according to any one of claims 38-44, wherein the time-frequency two-dimensional resources of the first RACH resource pool and the time-frequency two-dimensional resources of the second RACH resource pool are all non-overlapping .
The terminal device according to claim 37, wherein if the network device is configured with a third RACH resource pool; the sending module is specifically used for:

sending the target preamble to the network device on the time-frequency domain resource of the third RACH resource pool.
The terminal device according to any one of claims 37-46, wherein if the network device is configured with two sets of preambles, the two sets of preambles include the first set of preambles and the second set of preambles gather;

The first preamble set is only used by the first type of terminal equipment, and the second preamble set is only used by the second type of terminal equipment; the first type of terminal equipment and the second type of terminal equipment At least one piece of information in the device information of the terminal device is different.
The terminal device according to claim 47, wherein the first set of preambles and the second set of preambles do not overlap at all.
The terminal device according to any one of claims 37-48, wherein the device information of the terminal device includes at least one of the following information:

Equipment type;

Whether it has the ability to terminate the early PUSCH termination of the physical uplink shared channel PUSCH in advance;

Whether it has full-duplex capability.
The terminal device according to any one of claims 37-49, further comprising: a receiving module;

The receiving module is configured to receive configuration information from the network device, where the configuration information includes at least one of the following configurations: the at least one RACH resource pool; the at least one preamble set.
The terminal device according to any one of claims 37-50, wherein, if the terminal device is a first type of terminal device, the terminal device further includes: a processing module;

The processing module is configured to start or restart a random access contention resolution timer on the first symbol after the first retransmission of the Msg3 PUSCH.
The terminal device according to any one of claims 37-51, wherein, if the terminal device is a first type of terminal device, the terminal device further includes: a receiving module and a processing module;

If the receiving module receives the correct contention resolution message, and the number of retransmissions of the Msg3 PUSCH is less than the preset number of times, the processing module is used to terminate the retransmission of the remaining Msg3 PUSCH.
The terminal device according to any one of claims 37-50, wherein, if the terminal device is a second type of terminal device, the terminal device further includes: a processing module;

The processing module is used to start or restart the random access contention resolution timer on the first symbol after the last retransmission of Msg3 PUSCH.
The terminal device according to any one of claims 38, 47, 51, and 52, wherein the first type of terminal device is a terminal device with full-duplex capability, or a terminal device with PUSCH early termination capability Terminal equipment, or non-capability-reduced non-RedCap type terminal equipment.
The terminal device according to any one of claims 38, 47, and 53, wherein the second type of terminal device is a terminal device without full-duplex capability, or a terminal device without PUSCH early termination capability Terminal equipment, or terminal equipment of the RedCap type with reduced capabilities.
A network device, characterized in that it includes:

A receiving module, configured to receive a target preamble from a terminal device on time-frequency domain resources of a target random access channel RACH resource pool;

The target RACH resource pool is determined from at least one RACH resource pool configured by the network device according to the device information of the terminal device, and the target preamble is determined from the network device according to the device information of the terminal device determined in at least one preamble set configured.
The network device according to claim 56, wherein if the network device is configured with two RACH resource pools, the two RACH resources include a first RACH resource pool and a second RACH resource pool;

The first RACH resource pool is only used by terminal equipment of the first type, and the second RACH resource pool is only used by terminal equipment of the second type; the terminal equipment of the first type and the terminal equipment of the second type At least one piece of information in the device information of the terminal device is different.
The network device according to claim 57, wherein the time domain resources of the first RACH resource pool do not overlap with the time domain resources of the second RACH resource pool.
The network device according to claim 57, wherein the frequency domain resources of the first RACH resource pool do not overlap with the frequency domain resources of the second RACH resource pool.
The network device according to claim 57, wherein the time domain resources of the first RACH resource pool do not overlap with the time domain resources of the second RACH resource pool, and the frequency domain resources of the first RACH resource pool The frequency domain resources completely or partially overlap with the frequency domain resources of the second RACH resource pool.
The network device according to claim 57, wherein the frequency domain resources of the first RACH resource pool do not overlap with the frequency domain resources of the second RACH resource pool, and the time domain resources of the first RACH resource pool The domain resource completely or partially overlaps with the time domain resource of the second RACH resource pool.
The network device according to claim 57, wherein the time domain resources of the first RACH resource pool do not overlap with the time domain resources of the second RACH resource pool, and the frequency domain resources of the first RACH resource pool The frequency domain resources do not overlap with the frequency domain resources of the second RACH resource pool.
The network device according to any one of claims 57-62, wherein the frequency domain resources of the first RACH resource pool and the frequency domain resources of the second RACH resource pool are continuous frequency domain resources.
The network device according to any one of claims 57-63, wherein the time-frequency two-dimensional resources of the first RACH resource pool and the time-frequency two-dimensional resources of the second RACH resource pool are all non-overlapping .
The network device according to claim 56, wherein if the network device is configured with a third RACH resource pool; the receiving module is specifically used for:

Receive the target preamble from the terminal device on time-frequency domain resources of the third RACH resource pool.
The network device according to any one of claims 56-65, wherein if the network device is configured with two sets of preambles, the two sets of preambles include the first set of preambles and the second set of preambles gather;

The first preamble set is only used by the first type of terminal equipment, and the second preamble set is only used by the second type of terminal equipment; the first type of terminal equipment and the second type of terminal equipment At least one piece of information in the device information of the terminal device is different.
The network device according to claim 66, wherein the first set of preambles and the second set of preambles do not overlap at all.
The network device according to any one of claims 56-67, wherein the device information of the terminal device includes at least one of the following information:

Equipment type;

Whether it has the ability to terminate the early PUSCH termination of the physical uplink shared channel PUSCH in advance;

Whether it has full-duplex capability.
The network device according to claim 57 or 66, wherein the terminal device of the first type is a terminal device with full-duplex capability, and the terminal device of the second type is a terminal device without full-duplex capability. Terminal Equipment.
The network device according to claim 57 or 66, wherein the first type of terminal device is a terminal device with PUSCH early termination capability, and the second type of terminal device is not capable of PUSCH early termination Terminal Equipment.
The network device according to claim 57 or 66, wherein the first type of terminal device is a non-capability-reduced non-RedCap type terminal device, and the second type of terminal device is a capability-reduced RedCap type Terminal Equipment.
The network device according to any one of claims 56-71, further comprising: a sending module;

The sending module is configured to send configuration information to the terminal device, where the configuration information includes at least one of the following configurations: the at least one RACH resource pool; the at least one preamble set.
A terminal device, characterized by comprising: a memory and a processor, the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the processor runs the Said computer program performs the method according to any one of claims 1-19.
A network device, characterized by comprising: a memory and a processor, the memory is used to store a computer program, the processor is used to call and run the computer program from the memory, so that the processor runs the Said computer program performs the method according to any one of claims 20-36.
A computer storage medium, which is characterized in that it is used to store a computer program, and when the computer program is run on the computer, the computer is made to execute the method according to any one of claims 1-19.
A computer storage medium is characterized in that it is used to store a computer program, and when the computer program is run on a computer, the computer is made to execute the method according to any one of claims 20-36.
A computer program product, characterized in that, when the computer program product is run on a computer, the computer is made to execute the method according to any one of claims 1-19.
A computer program product, characterized in that, when the computer program product is run on a computer, the computer is made to execute the method according to any one of claims 20-36.