CN117296433A

CN117296433A - Information transmission method, device and storage medium

Info

Publication number: CN117296433A
Application number: CN202180098075.6A
Authority: CN
Inventors: 李海涛; 胡奕
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2021-07-28
Filing date: 2021-07-28
Publication date: 2023-12-26
Also published as: WO2023004619A1

Abstract

The application provides an information transmission method, equipment and a storage medium, wherein the method comprises the following steps: the terminal equipment sends the target preamble to the network equipment on the target RACH resource pool, so that the network equipment determines the type or the capacity of the terminal equipment according to the target RACH resource pool and/or the target preamble, and accordingly, corresponding competition solving information sending is carried out, and the transmission performance of the whole communication system can be improved.

Description

Information transmission method, device and storage medium

Technical Field

The embodiment of the application relates to the technical field of communication, in particular to an information transmission method, information transmission equipment and a storage medium.

Background

At present, in a new radio access technology (new radio access technology, NR) system, a terminal device monitors a random access response message (Msg 2) through a random access response time window, and monitors a contention resolution message (Msg 4) after Msg3 is sent, under the control of a random access contention resolution timer (RA-contentionresolution). The mode of starting the RA-ContentionResolTimer is different for different types or capabilities of terminal equipment, and how the terminal equipment informs the network of the equipment type or capability of the terminal equipment, so that the network makes corresponding random access feedback is one of the problems to be solved in the present day.

Disclosure of Invention

The embodiment of the application provides an information transmission method, information transmission equipment and a storage medium, and improves the transmission performance of a communication system.

In a first aspect, an embodiment of the present application provides an information transmission method, including: the terminal equipment sends a target preamble to the network equipment 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 based on the device information of the terminal device, and the target preamble is determined from at least one preamble set configured by the network device based on the device information of the terminal device.

In a second aspect, an embodiment of the present application provides an information transmission method, including: the network equipment receives a target preamble from the terminal equipment 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 based on the device information of the terminal device, and the target preamble is determined from at least one preamble set configured by the network device based on the device information of the terminal device.

In a third aspect, an embodiment of the present application provides a terminal device, including: a transmitting module, configured to transmit a target preamble to a network device on a time-frequency domain resource 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 based on the device information of the terminal device, and the target preamble is determined from at least one preamble set configured by the network device based on the device information of the terminal device.

In a fourth aspect, embodiments of the present application provide 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 pool is determined from at least one RACH resource pool configured by the network device based on the device information of the terminal device, and the target preamble is determined from at least one preamble set configured by the network device based on the device information of the terminal device.

In a fifth aspect, an embodiment of the present application provides a terminal device, including: a memory for storing a computer program and a processor for calling and running the computer program from the memory, such that the processor runs the computer program to perform the method according to the first aspect.

In a sixth aspect, embodiments of the present application provide a network device, including: a memory for storing a computer program and a processor for calling and running the computer program from the memory, such that the processor runs the computer program to perform the method according to the second aspect.

In a seventh aspect, embodiments of the present application provide a computer storage medium storing a computer program which, when run on a computer, causes the computer to perform the method according to the first aspect.

In an eighth aspect, embodiments of the present application provide a computer storage medium storing a computer program, which when run on a computer causes the computer to perform the method according to the second aspect.

In a ninth aspect, embodiments of the present application provide a computer program product which, when run on a computer, causes the computer to perform the method according to the first aspect.

In a tenth aspect, embodiments of the present application provide a computer program product which, when run on a computer, causes the computer to perform the method according to the second aspect.

The embodiment of the application provides an information transmission method, equipment and a storage medium, wherein the method comprises the following steps: the terminal equipment sends the target preamble to the network equipment on the target RACH resource pool, so that the network equipment knows the type or the capacity of the terminal equipment according to the target RACH resource pool and/or the target preamble, and accordingly, corresponding competition solving information sending is carried out, and the transmission performance of the whole communication system can be improved.

Drawings

Fig. 1 is a schematic diagram of a communication system suitable for an information transmission method according to an embodiment of the present application;

fig. 2 is a schematic diagram of a contention-based random access procedure according to an embodiment of the present application;

fig. 3 is a schematic diagram of a non-contention based random access procedure according to an embodiment of the present application;

fig. 4 is a schematic diagram of an information transmission method according to an embodiment of the present application;

fig. 5 is a schematic diagram of a configuration of a RACH resource pool according to an embodiment of the present disclosure;

fig. 6 is a second schematic configuration diagram of a RACH resource pool provided in an embodiment of the present disclosure;

fig. 7 is a schematic diagram III of a configuration of a RACH resource pool according to an embodiment of the present disclosure;

fig. 8 is a schematic diagram of a configuration of a RACH resource pool according to an embodiment of the present disclosure;

fig. 9 is a schematic diagram of a configuration of a RACH resource pool according to an embodiment of the present disclosure;

Fig. 10 is a schematic diagram two of an information transmission method according to an 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 according to an embodiment of the present application;

fig. 13 is a schematic hardware structure of a terminal device according to an embodiment of the present application;

fig. 14 is a schematic hardware structure of a network device according to an embodiment of the present application.

Detailed Description

The technical solutions in the present application will be described below with reference to the accompanying drawings.

The communication method provided by the application can be applied to various communication systems, such as: 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 (universal mobile telecommunication system, UMTS), worldwide interoperability for microwave access (worldwide interoperability for microwave access, wiMAX) telecommunications system, fifth generation (5th Generation,5G) mobile telecommunications system, or new radio access technology (new radio access technology, NR). The 5G mobile communication system may include a non-independent Networking (NSA) and/or an independent networking (SA), among others.

The communication method provided by the 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 (D2D) network, machine-to-machine (machine to machine, M2M) network, internet of things (internet of things, ioT) network or other networks. The IoT network may include, for example, an internet of vehicles. The communication modes in the internet of vehicles system are generally called as vehicle to other devices (V2X, X may represent anything), for example, the V2X may include: vehicle-to-vehicle (vehicle to vehicle, V2V) communication, vehicle-to-infrastructure (vehicle to infrastructure, V2I) communication, vehicle-to-pedestrian communication (vehicle to pedestrian, V2P) or vehicle-to-network (vehicle to network, V2N) communication, etc.

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

In the embodiment of the present application, the terminal device may also be referred to as a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user equipment.

The terminal device may be a device providing voice/data connectivity to a user, e.g., a handheld device with wireless connectivity, an in-vehicle device, etc. Currently, some examples of terminals may be: a mobile phone (mobile phone), a tablet (pad), a computer with wireless transceiver function (e.g., a notebook, a palm, etc.), a mobile internet device (mobile internet device, MID), a Virtual Reality (VR) device, an augmented reality (augmented reality, AR) device, a wireless terminal in an industrial control (industrial control), a wireless terminal in an unmanned (self-drive), a wireless terminal in a telemedicine (remote medical), a wireless terminal in a smart grid (smart grid), a wireless terminal in a transportation security (transportation safety), a wireless terminal in a smart city (smart city), a wireless terminal in a smart home (smart home), a cellular phone, a cordless phone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (wireless local loop, WLL) station, a personal digital assistant (personal digital assistant, PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a wireless terminal in a wearable device, a land-based device, a future-mobile terminal in a smart city (smart city), a public network (35G) or a future mobile communication device, etc.

The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wearing and developing wearable devices by applying a wearable technology, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

Furthermore, the terminal device may also be a terminal device in an internet of things (Internet of things, ioT) system. IoT is an important component of future information technology development, and its main technical feature is to connect an item with a network through a communication technology, so as to implement man-machine interconnection and an intelligent network for object interconnection. IoT technology may enable massive connectivity, deep coverage, and terminal power saving through, for example, narrowband (NB) technology.

In addition, the terminal device may further include sensors such as an intelligent printer, a train detector, and a gas station, and the main functions include collecting data (part of the terminal device), receiving control information and downlink data of the network device, and transmitting electromagnetic waves to transmit uplink data to the network device.

In this embodiment of the present application, the network device may be any device having a wireless transceiver function. Network devices include, but are not limited to: an evolved Node B (eNB), a radio network controller (radio network controller, RNC), a Node B (Node B, NB), a base station controller (base station controller, BSC), a base transceiver station (base transceiver station, BTS), a home base station (home evolved NodeB, or a home Node B, HNB, for example), a Base Band Unit (BBU), an Access Point (AP) in a wireless fidelity (wireless fidelity, wiFi) system, a wireless relay Node, a wireless backhaul Node, a transmission point (transmission point, TP), or a transmission reception point (transmission and reception point, TRP), etc., may also be 5G, e.g., NR, a gNB in a system, or a transmission point (TRP or TP), one or a group of base stations (including multiple antenna panels) in a 5G system, or may also be a network Node constituting a gNB or a transmission point, such as a baseband unit (BBU), or a Distributed Unit (DU), etc.

In some deployments, the gNB may include a Centralized Unit (CU) and DUs. The gNB may also include an active antenna unit (active antenna unit, AAU). The CUs implement part of the functionality of the gNB, the DUs implement part of the functionality of the gNB, e.g., the CUs may be responsible for handling non-real time protocols and services, e.g., may implement the functionality of a radio resource control (radio resource control, RRC) layer, a traffic data adaptation protocol (service data adaptation protocol, SDAP) layer, and/or a packet data convergence layer protocol (packet data convergence protocol, PDCP) layer. The DU may be responsible for handling physical layer protocols and real-time services. For example, functions of a radio link control (radio link control, RLC), medium access control (media access control, MAC) and Physical (PHY) layers may be implemented. One DU may be connected to only one CU or to a plurality of CUs, and one CU may be connected to a plurality of DUs, between which communication may be performed through an F1 interface. The AAU may implement part of the physical layer processing functions, radio frequency processing, and active antenna related functions. Under this architecture, higher layer signaling, such as RRC layer signaling, may also be considered to be transmitted by DUs or by dus+aaus, since the information of the RRC layer is eventually submitted to the PHY layer to become information of the PHY layer, or is converted from information of the PHY layer.

It is understood that the network device may be a device comprising one or more of a CU node, a DU node, an AAU node. In addition, the CU may be divided into network devices in an access network (radio access network, RAN), or may be divided into network devices in a 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 transmission resources (e.g., frequency domain resources, or spectrum resources) allocated by the network device, where the cell may belong to a macro base station (e.g., macro eNB or macro gNB, etc.), or may belong to a base station corresponding to a small cell (small cell), where the small cell may include: urban cells (metro cells), micro cells (micro cells), pico cells (pico cells), femto cells (femto cells) and the like, and the small cells have the characteristics of small coverage area, low transmitting power and the like and are suitable for providing high-rate data transmission services.

To facilitate an understanding of the embodiments of the present application, a communication system suitable for use in the embodiments of the present application will be described first with reference to fig. 1.

Fig. 1 is a schematic diagram of a communication system suitable for an information transmission method according to an embodiment of the present application. As shown in fig. 1, the communication system 100 may include at least one network device and a plurality of terminal devices, such as network device 101, terminal devices 102-105 shown in fig. 1. Wherein the network device 101 and the terminal devices 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, and illustrates a scenario in which the terminal device 102 transmits signaling and/or data to the terminal device 103, and the terminal device 104 transmits signaling and/or data to the terminal device 105, which should not constitute any limitation to the present application. There may also be signaling and/or data interactions between terminal device 102 and terminal device 104, and signaling and/or data interactions between terminal device 103 and terminal device 104 may also be performed. The embodiments of the present application are not limited in this regard.

It should also be understood that fig. 1 shows one network device and four terminal devices by way of example only. But this should not constitute any limitation to the present application. The communication system 100 may also include more network devices, as well as more or fewer terminal devices. The embodiments of the present application are not limited in this regard.

In the communication system shown in fig. 1, signaling and/or data transmission between terminal devices may be performed via a side-link. The resources used by the terminal device through the side-uplink communication may be allocated by the network device. In other words, the network device allocates resources for the sidelink transmission. For example, terminal device 102 in fig. 1 may send signaling and/or data to terminal device 103 via network device allocated resources, and terminal device 104 may send signaling and/or data to terminal device 105 via network device allocated resources.

The wireless communication between the communication devices may include wireless communication between a network device and a terminal device, wireless communication between a network device and a network device, and wireless communication between a terminal device and a terminal device. In the embodiments of the present application, the term "wireless communication" may also be simply referred to as "communication", and the term "communication" may also be described as "data transmission", "information transmission" or "transmission". Those skilled in the art may use the technical solutions of the embodiments of the present application to perform wireless communication between a network device and a terminal device, for example, wireless communication between an access network device and a terminal device, and wireless communication between a core network device and a terminal device.

Currently, in some communication systems, such as the fifth generation mobile communication system (5th generation wireless system,5G), three application scenarios of enhanced mobile ultra wideband (enhanced mobile broadband, eMBB), low latency high reliability communication (ultra reliable low latency communications, URLLC), and large-scale machine type communication (Massive machine type communications, mctc) are defined for satisfying high data rates, reducing delay, saving energy, reducing cost, and improving capacity and large-scale device connection. The eMBB is mainly used for meeting the service requirement of high data rate, supporting new business states such as high-definition video and VR, and is widely applied to industries such as cultural relics, entertainment, education and the like, and is also used for security monitoring, product detection and the like. Typical applications of URLLC include industrial automation, electric automation, telemedicine operations (surgery), traffic safety assurance, etc. Typical characteristics of mctc include high connection density, small data volume, delay insensitive traffic, low cost and long life of the module, etc.

In a 5G network environment, for the purpose of reducing air interface signaling, quickly recovering a radio connection, and quickly recovering a data service, a new RRC state, namely, rrc_inactive state is defined. This state is different from the rrc_idle state and the rrc_active state.

Rrc_idle state: mobility is based on cell selection reselection of the UE, paging is initiated by the CN and paging areas are configured by the CN. The base station side does not have a UE Access Stratum (AS) context. There is no RRC connection.

Rrc_connected state: there is an RRC connection and the base station and UE have a UE AS context. The network side knows that the location of the UE is cell specific. Mobility is network-side controlled mobility. Unicast data may be transmitted between the UE and the base station.

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

In order to facilitate understanding of the embodiments of the present application, a brief description of a random access procedure involved in the embodiments of the present application is provided below.

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

1, establishing wireless connection when UE initially accesses: the UE goes from rrc_idle state to rrc_connected state.

Rrc connection reestablishment procedure: so that the UE reestablishes the radio connection after the radio link failure.

3. And (3) switching: the UE needs to establish uplink synchronization with the new cell.

In the rrc_connected state, downlink (DL) data arrives, and the UL is in an out-of-sync state.

In the rrc_connected state, uplink (UL) data arrives, when the UL is in an out-of-sync state or there is no PUCCH resource for transmitting a scheduling request (scheduling request, SR).

Sr failed.

7. A synchronous reconfiguration request from RRC.

The ue transitions from the rrc_inactive state to the rrc_connected state.

9. Time alignment is established during secondary cell (SCell) addition.

10. Request other system messages (other system information, OSI).

11. Beam failure recovery.

At present, in an NR system, the following two random access modes are mainly supported: a contention-based random access scheme and a non-contention-based random access scheme. Wherein the contention-based random access procedure includes 4 steps and the non-contention-based random access procedure includes 2 steps. The time delay cost of the 4-step random access process is relatively large, and the method is not applicable to a low-time delay high-reliability scene in 5G. Compared with the 4-step random access process, the 2-step random access process can reduce access delay.

Fig. 2 is a schematic diagram of a contention-based random access procedure according to an embodiment of the present application. As shown in fig. 2, the random access procedure 200 may include the steps of:

in step 201, the terminal device sends Msg1 to the network device.

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

In step 202, the network device sends Msg2 comprising a random access response (random access response, RAR) to the terminal device.

The RAR is used to inform the terminal device that the Msg3 can use the physical uplink shared channel (physical uplink shared channel, PUSCH) resource, allocate a radio network temporary identifier (aadio network temporary identifier, RNTI) to the terminal device, provide timing advance time advance command for the terminal device, and so on.

In step 203, the terminal device sends Msg3 to the network device according to the RAR indication.

After the terminal device sends Msg1, a random access response time window RA-response window is opened, and a physical downlink control channel (physical downlink control channel, PDCCH) scrambled by the RA-RNTI is monitored in the time window. Wherein the RA-RNTI relates to PRACH time-frequency resources used by the terminal device to transmit Msg1.

After the terminal equipment successfully receives the PDCCH scrambled by the RA-RNTI, the terminal equipment can obtain a physical downlink shared channel (physical downlink shared channel, PDSCH) scheduled by the PDCCH, wherein the physical downlink shared channel comprises an RAR, and the RAR can comprise at least one of the following information:

the sub header of the RAR contains BI, which is used for indicating the back-off time of retransmission Msg 1;

random access preamble sequence identification (random access preamble ID, RAPID) in rar: the network responds to the received preamble index;

TAG is contained in the payload of the rar, and is used for adjusting uplink timing;

4. uplink grant UL grant: uplink resource indication for scheduling Msg 3;

temporary C-RNTI: PDCCH (initial access) for scrambling Msg4.

The terminal device sends Msg3 on PUSCH resources specified by the RAR, where Msg3 is mainly used to inform the network device what event the random access procedure is triggered by. For example, if it is an initial access random procedure, UE ID and establishment cause are carried in Msg 3; in the case of RRC reestablishment, the UE ID and establishment cause in the connected state are carried. After the Msg3 is sent, the terminal starts the RA-ContentionResolTimer, and monitors the PDCCH to receive the Msg4 during the running period of the timer.

In step 204, the network device sends Msg4 to the terminal device.

Msg4 has two roles, one is for contention conflict resolution, and the other is for the network device to transmit RRC configuration messages to the terminal device. The contention resolution is achieved in two ways: one is PDCCH scheduling with C-RNTI scrambling for Msg4 if the terminal device carries less than RNTI (cell-RNTI, C-RNTI) in Msg 3. Another is PDCCH scheduling, which is scrambled with a temporary C-RNTI (TC-RNTI) by the Msg4 if the terminal device does not carry a C-RNTI in the Msg3, such as an initial access. The conflict is resolved by the terminal device receiving PDSCH of Msg4 by matching the common control channel (common control channel, CCCH) traffic data units (service data unit, SDU) in the PDSCH.

In other words, msg4 includes a contention resolution message while allocating uplink transmission resources to the terminal device. When the terminal receives the Msg4 sent by the network device, it will detect whether the specific temporary identifier of the terminal device sent by the Msg3 by the terminal device is included in the contention resolution message sent by the network device, if so, it indicates that the random access procedure of the terminal device is successful, otherwise, the random access procedure is considered to be failed, and the terminal device needs to initiate the random access procedure from step 201 again.

Fig. 3 is a schematic diagram of a non-contention based random access procedure according to an embodiment of the present application. As shown in fig. 3, the random access procedure 300 may include the steps of:

in step 301, the terminal device sends MsgA to the network device.

MsgA includes Msg1 and Msg3 in the aforementioned 4-step random access procedure. For example, the MsgA includes a preamble, an identification of the terminal device, and a PUSCH portion. The random access time (RACH occision) of the preamble is the same as the 4-step random access procedure, and may be configured through a network, where the RO may be shared with the RO of the 4-step random access procedure, or may be configured separately. The time-frequency resource where the PUSCH is located is called PUSCH Occalasion (PO). One PO may contain multiple PUSCH resource elements (PUSCH resource unit, PRU), one PRU contains PUSCH resource and demodulation reference signals (demodulation reference signal, DMRS), DMRS contains DMRS ports (DMRS ports) and DMRS sequences. The PO is also configured through the network, the period of the PO is the same as that of the RO, and the PO and the RO have an association relationship.

In step 302, the network device sends MsgB to the terminal device.

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

The MsgB includes a contention resolution message while allocating uplink transmission resources to the terminal device. 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 MsgA by the terminal device is included in the contention resolution message sent by the network device, if so, it indicates that the random access procedure of the terminal device is successful, otherwise, the random access procedure is considered to be failed, and the terminal device needs to initiate the random access procedure from step 301 again.

From the above random access procedure, it can be seen that the main purpose of random access is for the terminal device to acquire uplink synchronization with the cell. In the random access process, the network device can know the time of the terminal device sending the preamble according to the RACH time-frequency resource used by the preamble received from the terminal device, so as to determine the initial Timing Advance (TA) of the terminal device according to the sending time and the receiving time of the preamble, and inform the terminal device through the RAR.

It should be noted that, the technical solution provided in the embodiment of the present application is mainly directed to the random access procedure shown in fig. 2.

The random access channel (random access channel, RACH) configuration in the NR system is briefly described below.

The RACH configuration is informed to the terminal device by the network in a broadcast form. The RACH configuration includes a RACH time-frequency resource configuration and a starting preamble root sequence configuration.

RACH time domain resource configuration: the RACH resource repetition period can be known through 1 RACH configuration index indication, and one RACH resource repetition period contains the number of ROs, the duration of each RO, and the like.

RACH frequency domain resource configuration: the method comprises 1 RACH initial frequency domain resource index and the number of RACH resources which can be frequency division multiplexed at the same time (namely the number of continuous RACH frequency domain resources), and the RACH frequency domain resources can be determined to be a section of continuous frequency domain resources through RACH frequency domain resource allocation.

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

At present, for uplink coverage enhancement in an NR system, one implementation manner is to introduce repetition transmission (i.e. retransmission mechanism) for Msg3 PUSCH transmission in a random access procedure, so as to achieve the purpose of enhancing Msg3 coverage. The terminal device may request Msg3 PUSCH retransmission by Msg1 at least according to the downlink coverage situation, for example when the reference signal received power (reference signal received power, RSRP) measurement is below a pre-configured threshold. After receiving the specific Msg1, the network device may allocate enhanced Msg3 resources for retransmission to the terminal device through UL grant in RAR in Msg 2.

In the random access process, the monitoring of Msg4 is controlled by RA-ContentionResolutionTimer. In the current NR system, RA-ContentionResolTimer is started after Msg3 transmission. After the Msg3 PUSCH repetition is introduced, how to start RA-contentioresolutiontimer is a problem that the standard needs to solve. If started after all Msg3 repetition transmissions are completed, the representative terminal device expects the network to respond to Msg4 after receiving all Msg3 repetitions. This is suitable for half duplex capable terminals, such as a RedCap terminal, since such terminals can only start listening to the downlink after PUSCH transmission is completed anyway. However, for a terminal device with full duplex capability, both transmit and receive may be used. If the network device receives the Msg3 successfully only through part of the Msg3 repetition, the Msg4 can be responded as early as possible, so that if the terminal device still receives the Msg4 while transmitting the rest of the Msg3 repetition, the terminal device can terminate the rest of the Msg3 repetition, thereby achieving the purpose of saving electricity, saving uplink resources and reducing uplink interference. It can be seen that the implementation on the network side is affected for different capabilities or types of terminal devices.

Therefore, in the random access process, since the mode of starting the RA-contentioresolutiontimer by the terminal devices with different capabilities or types may be different, how the terminal device informs the network of the device capability or type, so that the network makes corresponding feedback is a problem to be solved urgently at present.

In the embodiment of the application, aiming at the difference of the terminal equipment with different capabilities or types in the random access process, when the terminal equipment initiates a random access request, the equipment capability or type of the network can be informed through the transmission resource and/or the transmission content. Based on this approach, the network may configure corresponding RACH resources for terminal devices of different capabilities or types, and/or configure corresponding preamble sets based on terminal devices of different capabilities or types, so that the terminal device selects, according to its own capabilities or types, a target RACH resource corresponding to its capabilities or types and a target preamble, and sends the target preamble on the target RACH resource. The network can acquire the equipment capacity or type through the above transmission of the receiving terminal equipment, so that corresponding competition resolving information transmission is made, and the transmission performance of the whole communication system can be improved. If the terminal equipment has full duplex capability, the terminal equipment can terminate retransmission of the Msg3 PUSCH in advance according to the contention resolution message of successful random access sent by the network, thereby achieving the purpose of saving power, shortening the random access time, saving uplink resources and reducing uplink interference.

The technical scheme provided by the embodiment of the application is described in detail through specific embodiments. It should be noted that, the technical solution provided in the embodiments of the present application may include some or all of the following, and the following specific embodiments may be combined with each other, and the same or similar concepts or processes may not be described in some embodiments.

Fig. 4 is a schematic diagram of an information transmission method according to an embodiment of the present application. As shown in fig. 4, the information transmission method may include the steps of:

in step 401, the terminal device sends a 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 one possible design, the number of RACH resources configured by the network device is two, e.g., 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 used only for terminal devices of the first type and the second RACH resource pool is used only for terminal devices of the second type.

At least one item of information in the device information of the first type of terminal device and the second type of terminal device is different. Alternatively, the device information of the terminal device may include at least one of the following information:

information 1: device type.

Information 2: whether there is a capability of physical uplink shared channel PUSCH early termination (early PUSCH termination).

Information 3: whether full duplex capability.

In an alternative embodiment of the present embodiment, the device types include a capability reduction (reduced capability, redCap) type and a non-RedCap (non-RedCap) type.

In an alternative embodiment of the present embodiment, the device types include a full duplex type and a half duplex type.

The performance of the above-described different types of terminal devices is briefly described below.

The RedCAP type terminal has the characteristics of reduced bandwidth, reduced processing speed, reduced antenna number and the like.

2. Terminals of the full duplex type support sending and receiving messages, which can be received and sent at the same time (signaling and/or data).

3. A half duplex type terminal supports transmitting and receiving messages, but can only receive or transmit messages at the same time.

4. The terminal with the PUSCH early termination capability can terminate the rest of the Msg3 PUSCH repetition under the condition that the network equipment successfully receives the Msg3 only through part of the Msg3 PUSCH repetition, so as to achieve the purpose of saving electricity, save uplink resources and reduce uplink interference.

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

By way of example, the first type of terminal device may be a full duplex capable terminal device and the second type of terminal device may be a terminal device that does not have full duplex capability (e.g., half duplex capability). Alternatively, the first type of terminal device may be a terminal device that does not have full duplex capability (e.g., half duplex capability), and the second type of terminal device may be a terminal device that has full duplex capability.

For example, the first type of terminal device may be a terminal device having PUSCH early termination capability, and the second type of terminal device may be a terminal device not having PUSCH early termination capability. Alternatively, the first type of terminal device may be a terminal device without PUSCH early termination capability, and the second type of terminal device may be a terminal device with PUSCH early termination capability.

In the above design, terminal devices of different types or capabilities may initiate a random access request using different RACH resource pools, and the network device may learn the type or capability of the terminal device initiating the random access request by receiving the random access request on the different RACH resource pools, thereby performing contention resolution message transmission corresponding to the type or capability of the terminal device.

For example, taking a 4-step random access procedure as an example, the network device determines that the terminal device initiating the request has full duplex capability according to the RACH resource pool for receiving the random access request, if the network device only successfully receives the Msg3 through the Msg3 (i.e., part of the Msg 3) less than the preset retransmission times, the network device can directly return the Msg4 to the terminal device, so that the terminal device terminates the remaining Msg3 retransmission in advance, thereby achieving the purpose of terminal device energy saving, saving uplink resources and reducing uplink interference.

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

Fig. 5 is a schematic diagram of a configuration of a RACH resource pool according to an embodiment of the present disclosure. Fig. 6 is a schematic diagram of a second configuration of a RACH resource pool provided in an embodiment of the present application, fig. 7 is a schematic diagram of a third configuration of a RACH resource pool provided in an embodiment of the present application, fig. 8 is a schematic diagram of a fourth configuration of a RACH resource pool provided in an embodiment of the present application, and fig. 9 is a schematic diagram of a fifth configuration of a RACH resource pool provided in an embodiment of the present application.

In an alternative embodiment of the present 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 defines the positional relationship of the time domain resources of the first RACH resource pool and the second RACH resource pool in the time domain, i.e. the time domain resources of the first RACH resource pool and the second RACH resource pool are different.

In an alternative embodiment of the present 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 defines the positional relationship of the frequency domain resources of the first RACH resource pool and the second RACH resource pool on the frequency domain, i.e. the frequency domain resources of the first RACH resource pool and the second RACH resource pool are different.

In an alternative embodiment of the present embodiment, the time domain resources of the first RACH resource pool and the time domain resources of the second RACH resource pool do not overlap, and the frequency domain resources of the first RACH resource pool and the frequency domain resources of the second RACH resource pool 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 alternative embodiment of the present embodiment, the time domain resources of the first RACH resource pool and the time domain resources of the second RACH resource pool do not overlap, and the frequency domain resources of the first RACH resource pool and the frequency domain resources of the second RACH resource pool partially 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 not exactly the same, as shown in fig. 6.

In an alternative embodiment of the present embodiment, the frequency domain resources of the first RACH resource pool and the frequency domain resources of the second RACH resource pool do not overlap, and the time domain resources of the first RACH resource pool and the time domain resources of the second RACH resource pool 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 alternative embodiment of the present embodiment, the frequency domain resources of the first RACH resource pool and the frequency domain resources of the second RACH resource pool do not overlap, and the time domain resources of the first RACH resource pool and the time domain resources of the second RACH resource pool partially 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 not exactly the same, as shown in fig. 8.

In an alternative embodiment of the present embodiment, the time domain resources of the first RACH resource pool and the time domain resources of the second RACH resource pool do not overlap, 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 other words, in this embodiment, the time domain resources and the frequency domain resources of the first RACH resource pool and the second RACH resource pool are different, as shown in fig. 9.

In an alternative embodiment of the present embodiment, the frequency domain resources of the first RACH resource pool and the frequency domain resources of the second RACH resource pool are each consecutive frequency domain resources of a preset length, as shown in fig. 5 to 9.

In an alternative embodiment of the present embodiment, 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. In this embodiment, the first RACH resource pool and the second RACH resource pool each include a plurality of resource blocks, each of which corresponds to a predetermined length of contiguous time-domain resources and a predetermined length of contiguous frequency-domain resources. Any one of the resource blocks in the first RACH resource pool and any one of the resource blocks in the second RACH resource pool have no overlapping region, as shown in fig. 5 to 9.

In another possible design, the number of RACH resources configured by the network device is one, e.g., the network device is configured with a third RACH resource pool. The third RACH resource pool may be used for multiple types or capabilities of terminal device usage. And selecting RACH resources from the third RACH resource pool by different terminal equipment in a resource competition mode.

In the above design, terminal devices of different types or capabilities may initiate a random access request by using different resource blocks in the same RACH resource pool, and the network device may learn the type or capability of the terminal device initiating the random access request by analyzing the random access request of the terminal device, thereby performing contention resolution message transmission corresponding to the type or capability of the terminal device. Wherein the random access request includes a target preamble selected by the terminal device, and the target preamble may indicate a 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. For example, 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 may learn the device type or capability of each terminal device through different target preambles sent by the terminal devices.

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

For example, 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 used only for terminal devices of a first type, the second RACH resource pool is used only for terminal devices of a second type, and the third RACH resource pool is used only for terminal devices of a third type. In this embodiment, the device types may be divided according to actual application requirements, and the dividing manner is not limited in this embodiment.

Optionally, in some embodiments, the network device configures a RACH resource pool, for example, a third RACH resource pool, and the terminal device first determines a target synchronization signal and a physical broadcast channel PBCH block (Synchronization Signal and PBCH block, abbreviated SSB), and then selects a target RACH resource from the random access occasion RO resources corresponding to the target SSB (i.e., RO resources of the target SSB in the third RACH resource pool).

Optionally, in some embodiments, the network device configures two RACH resource pools, for example, a first RACH resource pool and a second RACH resource pool, and the terminal device first selects one target RACH resource pool from the two RACH resource pools according to its device type or capability, then determines the target SSB, and then selects the target RACH resource from RO resources corresponding to the target SSB (for example, RO resources 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 one possible design, the number of preamble sets configured by the network device is two, e.g., two preamble sets configured by the network device include a first preamble set and a second preamble set. The first preamble set is used only for terminal devices of the first type and the second preamble set is used only for terminal devices of the second type.

At least one item of information in the device information of the first type of terminal device and the second type of terminal device is different. The device information of the terminal device specifically includes which information can be referred to above, and will not be described herein.

Optionally, the first set of preambles and the second set of preambles do not overlap at all. It should be appreciated that the first set of preambles and the second set of preambles each include a plurality of preambles, any one of the first set of preambles being different from any one of the second set of preambles.

In the above design, terminal devices of different types or capabilities may select preambles in different preamble sets to initiate a random access request, and the network device may obtain the type or capability of the terminal device initiating the random access request by reading the preambles in the random access request, so as to perform contention resolution message transmission 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, e.g., the network device is configured with a third preamble set. The third set of preambles may be used for different types or capabilities of terminal devices.

In the above design, terminal devices of different types or capabilities may select the same or different target preambles from the third preamble set. For example, if the first type of terminal device and the second type of terminal device select the same target preamble from the third preamble set, the network device may send the target preamble RACH resource through the terminal device, and learn the device type of each terminal device, where the two types of terminal devices are 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 the terminal device include three or more types, each type or capability of the terminal device corresponds to a specific preamble set, and each type or capability of the terminal device can select a target preamble from the corresponding preamble sets.

For example, taking three types of terminal devices as an example, the network device configures three preamble sets, namely a first preamble set, a second preamble set and a third preamble set. Wherein the first preamble set is used only for the first type of terminal device, the second preamble set is used only for the second type of terminal device, and the third preamble set is used only for the third type of terminal device.

According to the information transmission method shown in the above embodiment, 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, and accordingly sends the corresponding contention resolution message, and the transmission performance of the whole communication system can be improved. If the terminal equipment has full duplex capability, the terminal equipment can terminate retransmission of the Msg3 PUSCH in advance according to the contention resolution message of successful random access sent by the network, thereby achieving the purpose of saving power, shortening the random access time, saving uplink resources and reducing uplink interference.

Optionally, in some embodiments, if the terminal device is a first type of terminal device, after the terminal device sends the target preamble to the network device on the target RACH resource pool, the method includes the steps of: the terminal device starts or restarts a random access contention resolution timer (RA-contentdimer) on the first symbol (symbol) after the first retransmission of the Msg3 PUSCH.

Optionally, in some embodiments, if the terminal device is a first type of terminal device, after the terminal device sends the target preamble to the network device on the target RACH resource pool, the method includes the steps of: if the terminal equipment receives the correct contention resolution message and the retransmission times of the Msg3 PUSCH are smaller than the preset times, the terminal equipment 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 that sends the target preamble is the first type of terminal device, the network device receives Msg3 successfully only by partial Msg3 retransmission, and may send the contention resolution message to the terminal device without waiting for receiving the remaining Msg3 retransmission.

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

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 method includes the steps of: the terminal device starts or restarts the random access contention resolution timer on the first symbol after the last retransmission of the Msg3 PUSCH.

Optionally, in some embodiments, if the network device determines that the terminal device that sends the target preamble is the second type of terminal device, the network device needs to send the contention resolution message to the terminal device after receiving all Msg3 retransmissions (i.e. receiving the Msg3 retransmissions for a preset number of times).

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

Fig. 10 is a schematic diagram two of an information transmission method according to an embodiment of the present application. As shown in fig. 10, the information transmission method may include the steps of:

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 alternative embodiment of the present embodiment, the configuration information includes a configuration of at least one RACH resource pool.

In an alternative embodiment of the present embodiment, the configuration information comprises a configuration of at least one preamble set.

In an alternative embodiment of the present embodiment, the configuration information includes a configuration of one RACH resource pool and at least two preamble sets.

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

In an alternative embodiment of the present embodiment, the configuration information includes a configuration of one RACH resource pool and one preamble set.

The at least one RACH resource configured for the network device may be referred to the above embodiments, and will not be described here again.

The at least one preamble set configured for the network device may be referred to the above embodiments, and will not be described herein.

Step 502, the terminal device sends a target preamble to the network device on the time-frequency domain resource 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 the at least one RACH resource pool according to the configuration information, and selects a target preamble from the at least one preamble set according to the configuration information, so as to implement that the terminal device sends the target preamble to the network device on a time-frequency domain resource of the target RACH resource pool. In this embodiment, the execution order of the terminal device selecting the target RACH resource pool and the target preamble is not limited. In some embodiments, the terminal device may also perform the step of selecting the target RACH resource pool and the target preamble simultaneously.

According to the information transmission method shown in the above embodiment, 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 informs the network device of the type or capability of the terminal device by sending the target preamble on the target RACH resource, so that the network device can make corresponding contention resolution message sending for the terminal devices with different types or capabilities, and the transmission performance of the whole communication system can be improved. If the terminal equipment has full duplex capability, the terminal equipment can terminate retransmission of the Msg3 PUSCH in advance according to the contention resolution message of successful random access sent by the network, thereby achieving the purpose of saving power, shortening the random access time, saving uplink resources and reducing uplink interference.

Fig. 11 is a schematic structural diagram of a terminal device according to an embodiment of the present application. As shown in fig. 11, the terminal device 600 of the present embodiment includes: a transmitting module 601, a receiving module 602 and a processing module 603.

A transmitting module 601, configured to transmit a target preamble to a network device on a time-frequency domain resource 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 based on the device information of the terminal device, and the target preamble is determined from at least one preamble set configured by the network device based on the device information of the terminal device.

In an optional embodiment of the present application, if the network device configures 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 a first type, and the second RACH resource pool is only used by terminal equipment of a second type; at least one item of information in the device information of the first type of terminal device and the second type of terminal device is different.

In an alternative 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 alternative 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 and the time domain resources of the second RACH resource pool do not overlap, and the frequency domain resources of the first RACH resource pool and the frequency domain resources of the second RACH resource pool overlap in whole or in part.

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

In an optional embodiment of the present application, the time domain resources of the first RACH resource pool and the time domain resources of the second RACH resource pool do not overlap, 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, the frequency domain resource of the first RACH resource pool and the frequency domain resource 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 and the time-frequency two-dimensional resources of the second RACH resource pool are all non-overlapping.

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

and transmitting the target preamble to the network equipment on the time-frequency domain resource of the third RACH resource pool.

In an optional embodiment of the present application, if the network device configures two preamble sets, the two preamble sets include a first preamble set and a second preamble set;

the first preamble set is used only for terminal equipment of a first type, and the second preamble set is used only for terminal equipment of a second type; at least one item of information in the device information of the first type of terminal device and the second type of terminal device is different.

In an alternative embodiment of the present application, the first set of preambles and the second set of preambles 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:

a device type;

whether there is a capability of the physical uplink shared channel PUSCH to terminate early PUSCH termination in advance;

whether full duplex capability.

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

receiving configuration information from the network device, the configuration information including 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 a random access contention resolution timer on a first symbol after the first retransmission of the Msg3 PUSCH.

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 retransmission times of the Msg3 PUSCH is less than a preset number of times, the processing module 603 is configured to terminate 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 a random access contention resolution timer on a first symbol after a last retransmission of the Msg3 PUSCH.

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 terminal device with non-capability reduction non-RedCap type.

In an optional embodiment of the present application, the second type of terminal device is a terminal device that does not have full duplex capability, or a terminal device that does not have PUSCH early termination capability, or a terminal device of capability reduction RedCap type.

The terminal device provided in the embodiment of the present application is configured to execute the technical scheme executed by the terminal device in any of the foregoing method embodiments, and its implementation principle and technical effect are similar, and are not described herein again.

Fig. 12 is a schematic structural diagram of a network device according to an embodiment of the present application. As shown in fig. 12, the network device 700 of the present embodiment includes: a receiving module 701 and a transmitting module 702.

A receiving module 701, 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;

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:

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

a device type;

whether full duplex capability.

In an alternative 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 with PUSCH early termination capability, and the second type of terminal device is a terminal device without PUSCH early termination capability.

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

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

transmitting configuration information to the terminal equipment, wherein the configuration information comprises 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 embodiment of the present application is configured to execute the technical scheme executed by the network device in any of the foregoing method embodiments, and its implementation principle and technical effect are similar, and are not described herein again.

It should be noted that, the above division of the modules of the terminal device or the network device is merely a division of a logic function, and may be fully or partially integrated into a physical entity or may be physically separated. And these modules may all be implemented in software in the form of calls by the processing element; or can be realized in hardware; the method can also be realized in a form of calling software by a processing element, and the method can be realized in a form of hardware by a part of modules. For example, the processing module may be a processing element that is set up separately, may be implemented in a chip of the above apparatus, or may be stored in a memory of the above apparatus in the form of program code, and may be called by a processing element of the above apparatus to execute the functions of the above determination module. The implementation of the other modules is similar. In addition, all or part of the modules can be integrated together or can be independently implemented. The processing element described herein may be an integrated circuit having signal processing capabilities. In implementation, each step of the above method or each module above may be implemented by an integrated logic circuit of hardware in a processor element or an instruction in a software form.

For example, the modules above may be one or more integrated circuits configured to implement the methods above, such as: 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), or the like. For another example, when a module above is implemented in the form of a processing element scheduler code, the processing element may be a general purpose processor, such as a central processing unit (central processing unit, CPU) or other processor that may invoke the program code. For another example, the modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD)), etc.

Fig. 13 is a schematic hardware structure of a terminal device according to an embodiment of the present application. As shown in fig. 13, the terminal device 800 of the present embodiment may include:

a transceiver 801, a processor 802, a memory 803;

the memory 803 stores computer-executable instructions;

the processor 802 executes the computer-executable 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.

Alternatively, the memory 803 may be separate or integrated with the processor 802. When the memory 803 is separate from the processor 802, the electronic device 800 may further include: a bus 804 for connecting the memory 803 and the processor 802.

Alternatively, the processor 802 may be a chip.

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

Fig. 14 is a schematic hardware structure of a network device according to an embodiment of the present application. As shown in fig. 14, the network device 900 of the present embodiment may include:

a transceiver 901, a processor 902, a memory 903;

The memory 903 stores computer-executable instructions;

the processor 902 executes the computer-executable 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.

Alternatively, the memory 903 may be separate or integrated with the processor 902. When the memory 903 is a device separate from the processor 902, the electronic device 900 may further include: a bus 904 for connecting the memory 903 and the processor 902.

Alternatively, the processor 902 may be a chip.

The network device provided in this embodiment may be used to execute the method executed by the network device in any of the foregoing method embodiments, and its implementation principle and technical effects are similar, and are not repeated here.

The embodiment of the application also provides a storage medium, in which a computer program is stored, and when the computer program is executed by a processor, the technical solution of the terminal device in any of the foregoing method embodiments is implemented.

The embodiment of the application also provides a program, when the program is executed by a processor, for executing the technical scheme of the terminal device in any of the foregoing method embodiments.

The embodiment of the application also provides a computer program product, which comprises program instructions for implementing the technical scheme of the terminal device in any of the foregoing method embodiments.

The embodiment of the application also provides a chip, which comprises: the processing module and the communication interface, the processing module can execute the technical scheme of the terminal equipment in the foregoing method embodiment. Further, the chip also comprises a storage module (such as a memory), the storage module is used for storing instructions, the processing module is used for executing the instructions stored in the storage module, and execution of the instructions stored in the storage module enables the processing module to execute the technical scheme of the terminal equipment.

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

The embodiment of the application also provides a program, when the program is executed by a processor, for executing the technical scheme of the network device in any of the foregoing method embodiments.

The embodiment of the application also provides a computer program product, which comprises program instructions for implementing the technical scheme of the network device in any of the foregoing method embodiments.

The embodiment of the application also provides a chip, which comprises: the processing module and the communication interface, the processing module can execute the technical scheme of the network equipment in the foregoing method embodiment. Further, the chip further includes a storage module (e.g., a memory), the storage module is configured to store the instructions, the processing module is configured to execute the instructions stored in the storage module, and execution of the instructions stored in the storage module causes the processing module to execute the technical scheme of the network device.

In the present application, "at least two" means two or more, and "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a alone, a and B together, and B alone, wherein a, B may be singular or plural. The character "/" generally indicates that the front and rear associated objects are an "or" relationship; in the formula, the character "/" indicates that the front and rear associated objects are a "division" relationship. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b, or c may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or plural.

It will be appreciated that the various numerical numbers referred to in the embodiments of the present application are merely for ease of description and are not intended to limit the scope of the embodiments of the present application.

It should be understood that, in the embodiments of the present application, the sequence number of each process described above does not mean that the execution sequence of each process should be determined by the function and the internal logic of each process, and should not constitute any limitation on the implementation process of the embodiments of the present application.

Claims

An information transmission method, comprising:

the terminal equipment sends a target preamble to the network equipment 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 based on the device information of the terminal device, and the target preamble is determined from at least one preamble set configured by the network device based on the device information of the terminal device.
The method of claim 1, wherein if the network device configures 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 a first type, and the second RACH resource pool is only used by terminal equipment of a second type; at least one item of information in the device information of the first type of terminal device and the second type of terminal device is different.
The method of claim 2, wherein the time domain resources of the first RACH resource pool are non-overlapping with the time domain resources of the second RACH resource pool.
The method of claim 2, wherein frequency domain resources of the first RACH resource pool are non-overlapping with frequency domain resources of the second RACH resource pool.
The method of claim 2, wherein the time domain resources of the first RACH resource pool and the time domain resources of the second RACH resource pool do not overlap, and wherein the frequency domain resources of the first RACH resource pool and the frequency domain resources of the second RACH resource pool overlap in whole or in part.
The method of claim 2, wherein the frequency domain resources of the first RACH resource pool and the frequency domain resources of the second RACH resource pool do not overlap, and wherein the time domain resources of the first RACH resource pool and the time domain resources of the second RACH resource pool overlap in whole or in part.
The method of claim 2, wherein the time domain resources of the first RACH resource pool and the time domain resources of the second RACH resource pool do not overlap, and wherein the frequency domain resources of the first RACH resource pool and the frequency domain resources of the second RACH resource pool do not overlap.
The method according to any 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 each consecutive frequency domain resources of a preset length.
The method according to any of claims 2-8, wherein the time-frequency two-dimensional resources of the first RACH resource pool are all non-overlapping 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 sending the target preamble code to the network device on the time-frequency domain resource of the target random access channel RACH resource pool includes:

and transmitting the target preamble to the network equipment on the time-frequency domain resource of the third RACH resource pool.
The method according to any of claims 1-10, wherein if the network device configures two preamble sets, the two preamble sets comprise a first preamble set and a second preamble set;

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

a device type;

whether there is a capability of the physical uplink shared channel PUSCH to terminate early PUSCH termination in advance;

whether 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, the configuration information including 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 of claims 1-14, wherein if the terminal device is a first type of terminal device, the method further comprises:

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

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

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

the network equipment receives a target preamble from the terminal equipment on time-frequency domain resources of a target Random Access Channel (RACH) resource pool;

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

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 of claim 20, wherein if the network device configures 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 a first type, and the second RACH resource pool is only used by terminal equipment of a second type; at least one item of information in the device information of the first type of terminal device and the second type of terminal device is different.
The method of claim 21, wherein the time domain resources of the first RACH resource pool are non-overlapping with the time domain resources of the second RACH resource pool.
The method of claim 21, wherein the frequency domain resources of the first RACH resource pool are non-overlapping with the frequency domain resources of the second RACH resource pool.
The method of 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 wherein the frequency domain resources of the first RACH resource pool overlap with the frequency domain resources of the second RACH resource pool in whole or in part.
The method of claim 21, wherein the frequency domain resources of the first RACH resource pool and the frequency domain resources of the second RACH resource pool do not overlap, and wherein the time domain resources of the first RACH resource pool and the time domain resources of the second RACH resource pool overlap in whole or in part.
The method of claim 21, wherein the time domain resources of the first RACH resource pool and the time domain resources of the second RACH resource pool do not overlap 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.
The method according to any 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 each consecutive frequency domain resources of a preset length.
The method according to any of claims 21-27, wherein the time-frequency two-dimensional resources of the first RACH resource pool are all non-overlapping 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 receiving a target preamble from a terminal device on time-frequency domain resources of a target random access channel RACH resource pool, comprising:

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 of claims 20-29, wherein if the network device configures two preamble sets, the two preamble sets comprise a first preamble set and a second preamble set;

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

a device type;

whether there is a capability of the physical uplink shared channel PUSCH to terminate early PUSCH termination in advance;

whether full duplex capability.
The method according to claim 21 or 30, wherein the first type of terminal device is a full duplex capable terminal device and the second type of terminal device is a terminal device not having full duplex capability.
The method according to claim 21 or 30, wherein the first type of terminal device is a PUSCH early termination capable terminal device and the second type of terminal device is a terminal device without PUSCH early termination capability.
The method according to claim 21 or 30, wherein the first type of terminal device is a non-capability reduction non-RedCap type of terminal device and the second type of terminal device is a capability reduction RedCap type of terminal device.
The method according to any one of claims 20-35, further comprising:

The network device sends configuration information to the terminal device, wherein the configuration information comprises at least one of the following configurations: the at least one RACH resource pool; the at least one preamble set.
A terminal device, comprising:

a transmitting module, configured to transmit a target preamble to a network device on a time-frequency domain resource 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 based on the device information of the terminal device, and the target preamble is determined from at least one preamble set configured by the network device based on the device information of the terminal device.
The terminal device of claim 37, wherein if the network device configures 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 a first type, and the second RACH resource pool is only used by terminal equipment of a second type; at least one item of information in the device information of the first type of terminal device and the second type of terminal device is different.
The terminal device of 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 of claim 38, wherein the frequency domain resources of the first RACH resource pool are non-overlapping with the frequency domain resources of the second RACH resource pool.
The terminal device of 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 wherein the frequency domain resources of the first RACH resource pool overlap with the frequency domain resources of the second RACH resource pool in whole or in part.
The terminal device of claim 38, wherein the frequency domain resources of the first RACH resource pool and the frequency domain resources of the second RACH resource pool do not overlap, and wherein the time domain resources of the first RACH resource pool and the time domain resources of the second RACH resource pool overlap in whole or in part.
The terminal device of claim 38, wherein the time domain resources of the first RACH resource pool and the time domain resources of the second RACH resource pool do not overlap, and wherein the frequency domain resources of the first RACH resource pool and the frequency domain resources of the second RACH resource pool do not overlap.
The terminal device of any 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 each contiguous frequency domain resources of a preset length.
The terminal device of any of claims 38-44, wherein the time-frequency two-dimensional resources of the first RACH resource pool are all non-overlapping with the time-frequency two-dimensional resources of the second RACH resource pool.
The terminal device of claim 37, wherein if the network device configures a third RACH resource pool; the sending module is specifically configured to:

and transmitting the target preamble to the network equipment on the time-frequency domain resource of the third RACH resource pool.
The terminal device of any of claims 37-46, wherein if the network device configures two preamble sets, the two preamble sets include a first preamble set and a second preamble set;

the first preamble set is used only for terminal equipment of a first type, and the second preamble set is used only for terminal equipment of a second type; at least one item of information in the device information of the first type of terminal device and the second type of terminal device is different.
The terminal device of 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 of the claims 37-48, characterized in that the device information of the terminal device comprises at least one of the following information:

a device type;

whether there is a capability of the physical uplink shared channel PUSCH to terminate early PUSCH termination in advance;

whether full duplex capability.
The terminal device according to any of the claims 37-49, characterized in that the terminal device further comprises: 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 of the claims 37-50, characterized in that if the terminal device is a terminal device of a first type, the terminal device further comprises: a processing module;

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

and if the receiving module receives the correct contention resolution message and the retransmission times of the Msg3 PUSCH are smaller than the preset times, the processing module is used for terminating the retransmission of the residual Msg3 PUSCH.
The terminal device according to any of the claims 37-50, characterized in that if the terminal device is a terminal device of a second type, the terminal device further comprises: a processing module;

the processing module is configured to start or restart a random access contention resolution timer on a first symbol after a last retransmission of the Msg3 PUSCH.
The terminal device according to any of claims 38, 47, 51, 52, wherein the terminal device of the first type is a terminal device with full duplex capability, or a terminal device with PUSCH early termination capability, or a terminal device of the non-capability downscaling non-RedCap type.
The terminal device of any of claims 38, 47, 53, wherein the second type of terminal device is a terminal device that is not full duplex capable, or is a terminal device that is not PUSCH early termination capable, or is a reduced capability RedCap type of terminal device.
A network device, comprising:

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 pool is determined from at least one RACH resource pool configured by the network device based on the device information of the terminal device, and the target preamble is determined from at least one preamble set configured by the network device based on the device information of the terminal device.
The network device of claim 56, wherein if the network device configures 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 a first type, and the second RACH resource pool is only used by terminal equipment of a second type; at least one item of information in the device information of the first type of terminal device and the second type of terminal device is different.
The network device of claim 57, wherein the time domain resources of the first pool of RACH resources do not overlap with the time domain resources of the second pool of RACH resources.
The network device of claim 57, wherein the frequency domain resources of the first pool of RACH resources do not overlap with the frequency domain resources of the second pool of RACH resources.
The network device of claim 57, wherein the time domain resources of the first RACH resource pool and the time domain resources of the second RACH resource pool do not overlap, and the frequency domain resources of the first RACH resource pool and the frequency domain resources of the second RACH resource pool overlap in whole or in part.
The network device of claim 57, wherein the frequency domain resources of the first RACH resource pool and the frequency domain resources of the second RACH resource pool do not overlap, and the time domain resources of the first RACH resource pool and the time domain resources of the second RACH resource pool overlap in whole or in part.
The network device of claim 57, wherein the time domain resources of the first RACH resource pool and the time domain resources of the second RACH resource pool do not overlap, 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.
The network device of any 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 each contiguous frequency domain resources of a preset length.
The network device of any of claims 57-63, wherein the time-frequency two-dimensional resources of the first RACH resource pool are all non-overlapping with the time-frequency two-dimensional resources of the second RACH resource pool.
The network device of claim 56, wherein if the network device configures a third RACH resource pool; the receiving module is specifically configured to:

the target preamble from the terminal device is received on time-frequency domain resources of the third RACH resource pool.
The network device of any one of claims 56-65, wherein if the network device configures two preamble sets, the two preamble sets include a first preamble set and a second preamble set;

the first preamble set is used only for terminal equipment of a first type, and the second preamble set is used only for terminal equipment of a second type; at least one item of information in the device information of the first type of terminal device and the second type of terminal device is different.
The network device of claim 66, wherein the first set of preambles and the second set of preambles do not overlap at all.
The network device of any one of claims 56-67, wherein the device information of the terminal device comprises at least one of:

a device type;

whether there is a capability of the physical uplink shared channel PUSCH to terminate early PUSCH termination in advance;

whether full duplex capability.
The network device of claim 57 or 66, wherein the first type of terminal device is a full duplex capable terminal device and the second type of terminal device is a terminal device that is not full duplex capable.
The network device of claim 57 or 66, wherein the first type of terminal device is a PUSCH early termination capable terminal device and the second type of terminal device is a terminal device without PUSCH early termination capability.
The network device of claim 57 or 66, wherein the first type of terminal device is a non-capability reduction non-RedCap type of terminal device and the second type of terminal device is a capability reduction RedCap type of terminal device.
The network device of any one of claims 56-71, wherein the network device further comprises: a transmitting 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, comprising: a memory for storing a computer program and a processor for calling and running the computer program from the memory, such that the processor runs the computer program to perform the method of any of claims 1-19.
A network device, comprising: a memory for storing a computer program and a processor for calling and running the computer program from the memory, such that the processor runs the computer program to perform the method of any of claims 20-36.
A computer storage medium storing a computer program which, when run on a computer, causes the computer to perform the method of any one of claims 1-19.
A computer storage medium storing a computer program which, when run on a computer, causes the computer to perform the method of any one of claims 20-36.
A computer program product, characterized in that the computer program product, when run on a computer, causes the computer to perform the method according to any of claims 1-19.
A computer program product, characterized in that the computer program product, when run on a computer, causes the computer to perform the method according to any of claims 20-36.