Communication method and communication apparatus
The terminal device determines the DMRS sequence based on the preamble identification and model, and realizes the mapping of sending different DMRS sequences on the same DMRS resource, solving the problem of limiting the number of DMRS ports and improving the detection performance of multi-terminal access.
Patent Information
- Application Number
- PCT/CN2024/125465
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2024-01-29
- Filing Date
- 2024-10-17
- Publication Date
- 2025-08-07
AI Technical Summary
In the prior art, due to the limited number of DMRS ports, detection performance deteriorates when multiple terminal devices request random access at the same time.
The terminal device determines the DMRS sequence based on the identification and model of the preamble, and sends different DMRS sequences through the same DMRS resources, and combines PUSCH resource mapping to reduce mutual interference and improve detection success rate.
Support more terminal devices to request random access at the same time, which improves the success rate of detection of PUSCH data by network devices and reduces mutual interference.
Smart Images

Figure CN2024125465_07082025_PF_FP_ABST
Abstract
Description
Communication method and communication device
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of the People's Republic of China on January 29, 2024, with application number 202410128380.0 and invention name "A Communication Method and Communication Device", the entire contents of which are incorporated by reference into this application. Technical Field
[0003] The present application relates to the field of wireless communication technology, and in particular to a communication method and a communication device. Background Art
[0004] In the two-step random access process, the terminal device sends message A, which specifically includes sending a preamble carried on a random access channel (RACH) resource, and sending a demodulation reference signal (DMRS) sequence and PUSCH data carried on a physical uplink shared channel (PUSCH) resource corresponding to the RACH resource. The PUSCH data includes a random access request, and the DMRS sequence is sent through the DMRS port corresponding to the RACH resource.
[0005] However, since the number of DMRS ports is currently limited, for example, a maximum of 12 DMRS ports are currently supported. Therefore, to ensure that the network equipment's detection performance of PUSCH data is not affected, a maximum of 12 users (i.e., terminal devices) are supported to simultaneously transmit DMRS sequences on different DMRS ports. If more than 12 users transmit DMRS sequences simultaneously, some users will transmit DMRS sequences on the same DMRS port, which will degrade detection performance.
[0006] How to support more terminal devices to request random access at the same time remains to be solved.
[0007] Summary of the Invention
[0008] The embodiments of the present application provide a communication method and a communication device to support more terminal devices to request random access simultaneously.
[0009] In a first aspect, an embodiment of the present application provides a communication method that can be performed by a terminal device or a module (such as a chip) in the terminal device. The method includes: receiving information of a first model; determining a demodulation reference signal (DMRS) sequence based on an identifier of a preamble and the first model; and transmitting the preamble carried on a random access channel (RACH) resource, and the DMRS sequence and PUSCH data carried on a physical uplink shared channel (PUSCH) resource corresponding to the RACH resource.
[0010] In the above solution, the terminal device determines the DMRS sequence according to the identifier of the preamble code and the first model, and different DMRS sequences are sent on the same DMRS resource, which is no longer limited to the DMRS port, thereby supporting more terminal devices to request random access at the same time.
[0011] In one possible implementation method, determining the DMRS sequence based on the identifier of the preamble code and the first model includes: determining the DMRS port number based on the identifier of the preamble code; and inputting the DMRS port number into the first model to obtain the DMRS sequence; or, inputting the identifier of the preamble code into the first model to obtain the DMRS sequence.
[0012] In a possible implementation method, the method further includes: receiving indication information, where the indication information indicates a correspondence between the RACH resources and the PUSCH resources.
[0013] In a possible implementation method, the information of the first model and the indication information are included in the same system information, or are respectively included in different system information.
[0014] In a possible implementation method, the method further includes: receiving information of a second model; and determining the PUSCH resource according to an identifier of the preamble code and the second model.
[0015] The above scheme, combined with the information of the second model to determine the PUSCH resources, helps to map the DMRS sequences sent by different terminal devices to different PUSCH resources to minimize mutual interference, thereby improving the success rate of network equipment in detecting PUSCH data.
[0016] In a possible implementation method, the information of the first model and the information of the second model are included in the same system information, or are respectively included in different system information.
[0017] In one possible implementation method, the information of the first model includes at least one of the identification of the first model, the network structure information of the first model, or the weight of the first model; the information of the second model includes at least one of the identification of the second model, the network structure information of the second model, or the weight of the second model.
[0018] In a possible implementation method, the determining of the PUSCH resource based on the identifier of the preamble code and the second model includes: determining the PUSCH resource based on the identifier of the preamble code, first information and the second model, wherein the first information includes at least one of the following: the priority of the service of the terminal device, the quality of the synchronization signal block (SSB) measured by the terminal device, or the index of the SSB measured by the terminal device.
[0019] The above solution, combined with the first information to determine the PUSCH resource, can map the DMRS sequences sent by different terminal devices to different PUSCH resources to avoid mutual interference as much as possible, thereby improving the success rate of network equipment in detecting PUSCH data.
[0020] In a possible implementation method, the method further includes: determining at least one of the transmission power of the preamble code, the transmission power of the DMRS sequence, or the transmission power of the PUSCH data based on the identifier of the preamble code, the first information, and the second model.
[0021] The above solution helps to reduce the mutual interference when different terminal devices send preamble codes, DMRS sequences and PUSCH data, thereby improving the success rate of sending preamble codes, DMRS sequences and PUSCH data, and improving the detection performance of network equipment.
[0022] In a second aspect, embodiments of the present application provide a communication method that can be performed by a terminal device or a module (such as a chip) in the terminal device. The method includes: receiving first indication information, where the first indication information indicates a DMRS sequence corresponding to a preamble; and transmitting, based on the first indication information, the preamble carried on a RACH resource, and the DMRS sequence and PUSCH data carried on a PUSCH resource corresponding to the RACH resource.
[0023] In the above solution, the terminal device determines the DMRS sequence according to the first indication information, and different DMRS sequences are sent on the same DMRS resource, which is no longer limited to the DMRS port, thereby supporting more terminal devices to request random access at the same time.
[0024] In a possible implementation method, the first indication information includes a correspondence between the preamble code and the DMRS sequence.
[0025] In one possible implementation method, the first indication information includes the identifier of the DMRS sequence and the DMRS sequence; the method also includes: determining the DMRS sequence based on the first indication information and the correspondence between the identifier of the DMRS sequence and the identifier of the preamble code.
[0026] In a possible implementation method, the method further includes: receiving second indication information, where the second indication information indicates a correspondence between the RACH resources and the PUSCH resources.
[0027] In a possible implementation method, the first indication information and the second indication information are included in the same system information, or are respectively included in different system information.
[0028] In a possible implementation method, the method further includes: receiving information of a second model; and determining the PUSCH resource according to an identifier of the preamble code and the second model.
[0029] The above scheme, combined with the information of the second model to determine the PUSCH resources, helps to map the DMRS sequences sent by different terminal devices to different PUSCH resources to minimize mutual interference, thereby improving the success rate of network equipment in detecting PUSCH data.
[0030] In a possible implementation method, the first indication information and the information of the second model are included in the same system information, or are respectively included in different system information.
[0031] In a possible implementation method, the information of the second model includes at least one of an identifier of the second model, network structure information of the second model, or a weight of the second model.
[0032] In a possible implementation method, the PUSCH resource is determined based on the identifier of the preamble code and the second model, including: determining the PUSCH resource based on the identifier of the preamble code, first information and the second model, the first information including at least one of the following: the priority of the service of the terminal device, the quality of the SSB measured by the terminal device, or the index of the SSB measured by the terminal device.
[0033] The above solution, combined with the first information to determine the PUSCH resource, can map the DMRS sequences sent by different terminal devices to different PUSCH resources to avoid mutual interference as much as possible, thereby improving the success rate of network equipment in detecting PUSCH data.
[0034] In a possible implementation method, the method further includes: determining at least one of the transmission power of the preamble code, the transmission power of the DMRS sequence, or the transmission power of the PUSCH data based on the identifier of the preamble code, the first information, and the second model.
[0035] The above solution helps to reduce the mutual interference when different terminal devices send preamble codes, DMRS sequences and PUSCH data, thereby improving the success rate of sending preamble codes, DMRS sequences and PUSCH data, and improving the detection performance of network equipment.
[0036] In a third aspect, embodiments of the present application provide a communication method that can be performed by a network device or a module (such as a chip) in the network device. The method includes: receiving a preamble carried on a RACH resource; determining a DMRS sequence based on an identifier of the preamble; and determining PUSCH data carried on the PUSCH resource based on the DMRS sequence, a received signal on a PUSCH resource corresponding to the RACH resource, and a third model.
[0037] In this solution, network devices determine the DMRS sequence based on the preamble identifier. Different DMRS sequences are transmitted on the same DMRS resource, freeing them from DMRS port constraints. This allows more devices to simultaneously request random access. Furthermore, network devices do not need to perform channel estimation; instead, they simply input the received signal on the PUSCH resource into a third model to obtain PUSCH data. This results in a simpler and more accurate detection method.
[0038] In a possible implementation method, determining the DMRS sequence according to the identifier of the preamble includes: determining the DMRS sequence according to the identifier of the preamble and a first model.
[0039] In one possible implementation method, determining the DMRS sequence based on the identifier of the preamble code and the first model includes: determining the DMRS port number based on the identifier of the preamble code; and inputting the DMRS port number into the first model to obtain the DMRS sequence; or, inputting the identifier of the preamble code into the first model to obtain the DMRS sequence.
[0040] In a possible implementation method, the method further includes: sending information of the first model.
[0041] In a possible implementation method, the information of the first model includes at least one of an identifier of the first model, network structure information of the first model, or a weight of the first model.
[0042] In a possible implementation method, the method further includes: determining the PUSCH resource according to the identifier of the preamble code and the second model.
[0043] The above scheme, combined with the information of the second model to determine the PUSCH resources, helps to map the DMRS sequences sent by different terminal devices to different PUSCH resources to minimize mutual interference, thereby improving the success rate of network equipment in detecting PUSCH data.
[0044] In a possible implementation method, the method further includes: sending information of the second model.
[0045] In a possible implementation method, the information of the second model includes at least one of an identifier of the second model, network structure information of the second model, or a weight of the second model.
[0046] In a possible implementation method, the method further includes: acquiring the third model according to the number of terminal devices that send DMRS sequences on the PUSCH resources.
[0047] The above solution determines the corresponding third model based on the number of terminal devices sending DMRS sequences on the same PUSCH resource, which helps to select a third model with appropriate performance for parsing PUSCH data and improves the success rate of data parsing.
[0048] In a fourth aspect, an embodiment of the present application provides a communication device, which may be a terminal device or a module (such as a chip) in the terminal device. The device has the function of implementing any of the implementation methods of the first to second aspects above. The function can be implemented by hardware or by hardware executing corresponding software implementations. The hardware or software includes one or more modules corresponding to the above functions.
[0049] In a fifth aspect, an embodiment of the present application provides a communication device, which may be a network device or a module (such as a chip) in a network device. The device has the function of implementing any implementation method of the third aspect described above. The function can be implemented by hardware or by hardware executing corresponding software implementations. The hardware or software includes one or more modules corresponding to the above functions.
[0050] In a sixth aspect, an embodiment of the present application provides a communication device, comprising a unit or means for executing each step of any implementation method in the above-mentioned first to third aspects.
[0051] In a seventh aspect, an embodiment of the present application provides a communication device, comprising a processor and an interface circuit, wherein the processor is configured to communicate with other devices via the interface circuit and execute any of the implementation methods described in the first to third aspects above. The processor comprises one or more.
[0052] Optionally, the communication device may further include a memory for storing computer instructions, the memory being coupled to a processor, and the processor executing the computer instructions stored in the memory so that the device executes any implementation method in the above-mentioned first to third aspects.
[0053] In an eighth aspect, an embodiment of the present application further provides a computer program product, which includes a computer program or instructions. When the computer program or instructions are run by a communication device, any implementation method in the above-mentioned first to third aspects is executed.
[0054] In the ninth aspect, an embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores instructions, which, when run on a communication device, enables any implementation method in the above-mentioned first to third aspects to be executed.
[0055] In the tenth aspect, the present application provides a chip (or chip system), which includes a processor, the processor is coupled to a memory, and the memory stores a computer program; the processor is used to call part or all of the computer program in the memory, so that any implementation method of the above-mentioned first to third aspects is executed. BRIEF DESCRIPTION OF THE DRAWINGS
[0056] FIG1( a ) is a schematic diagram of the architecture of a communication system used in an embodiment of the present application;
[0057] Figure 1(b) shows a schematic diagram of a network device;
[0058] FIG2 is a schematic diagram of a four-step random access process;
[0059] FIG3 is a schematic diagram of a two-step random access process;
[0060] FIG4( a ) is a diagram illustrating an example of a time-frequency resource configuration pattern of a DMRS;
[0061] Figure 4(b) shows an example of resource configuration for a single-symbol Type 1 DMRS corresponding to PUSCH Type A and Type B mapping;
[0062] FIG5 is a flow chart of a communication method provided in an embodiment of the present application;
[0063] FIG6 is a diagram showing an example of DMRS resource configuration;
[0064] FIG7 is a flow chart of a communication method provided in an embodiment of the present application;
[0065] FIG8 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application;
[0066] FIG9 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0067] Figure 1(a) is a schematic diagram of the architecture of a communication system used in an embodiment of the present application. The communication system shown in Figure 1(a) includes a wireless access network 100 and a core network 200. Optionally, the communication system also includes the Internet 300. The wireless access network 100 may include at least one network device (such as 110a and 110b in Figure 1(a)) and may also include at least one terminal device (such as 120a-120j in Figure 1(a)). The terminal device is connected to the network device wirelessly, and the network device is connected to the core network wirelessly or by wire. The core network device and the network device may be independent and distinct physical devices, or the functions of the core network device and the logical functions of the network device may be integrated into the same physical device, or a physical device may integrate some of the functions of the core network device and some of the functions of the network device. Terminal devices and network devices may be connected to each other via wired or wireless connections. Figure 1(a) is merely a schematic diagram. The communication system may also include other network devices, such as wireless relay devices and wireless backhaul devices, which are not shown in Figure 1(a).
[0068] A network device is an access device that a terminal device uses to access a communication system via a wired or wireless method. A network device may be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in a fifth generation (5G) mobile communication system, a next generation base station in a sixth generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system; it may also be a module or unit that performs some of the functions of a base station, for example, a centralized unit (CU), a distributed unit (DU), or a radio unit (RU). A network device may be a macro base station (such as 110a in FIG1(a)), a micro base station or an indoor station (such as 110b in FIG1(a)), a relay node or a donor node, etc. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network device.
[0069] A terminal device is a device with wireless transceiver capabilities that can send signals to or receive signals from a network device. Terminal devices include but are not limited to terminal devices, terminals, user equipment (UE), mobile stations, mobile terminals, etc. Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, etc. The terminal device can specifically be a mobile phone, tablet computer, computer with wireless transceiver capabilities, wearable device, vehicle, aircraft, ship, robot, robotic arm, smart home device, etc. The embodiments of this application do not limit the specific technology and specific device form adopted by the terminal device.
[0070] Network devices and terminal devices can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed on aircraft, balloons, and artificial satellites. The embodiments of this application do not limit the application scenarios of network devices and terminal devices.
[0071] The roles of network devices and terminal devices can be relative. For example, the helicopter or drone 120i in Figure 1(a) can be configured as a mobile network device. For terminal devices 120j that access the wireless access network 100 via 120i, terminal device 120i is a network device. However, for network device 110a, 120i is a terminal device, meaning that communication between 110a and 120i occurs via a wireless air interface protocol. Of course, communication between 110a and 120i can also occur via an interface protocol between network devices. In this case, relative to 110a, 120i is also a network device. Therefore, both network devices and terminal devices can be collectively referred to as communication devices. 110a and 110b in Figure 1(a) can be referred to as communication devices with network device functionality, and 120a-120j in Figure 1(a) can be referred to as communication devices with terminal device functionality.
[0072] Network devices and terminal devices, network devices and network devices, and terminal devices and terminal devices can communicate through authorized spectrum, unauthorized spectrum, or both; can communicate through spectrum below 6 gigahertz (GHz), spectrum above 6 GHz, or spectrum below 6 GHz and spectrum above 6 GHz simultaneously. The embodiments of the present application do not limit the spectrum resources used for wireless communications.
[0073] In the embodiments of the present application, the functions of the network device may also be performed by a module (such as a chip) in the network device, or by a control subsystem that includes the network device functions. The control subsystem that includes the network device functions here may be a control center in the above-mentioned application scenarios such as smart grid, industrial control, smart transportation, and smart city. The functions of the terminal device may also be performed by a module (such as a chip or a modem) in the terminal device, or by a device that includes the terminal device functions.
[0074] In this application, a network device sends downlink signals or downlink information to a terminal device, and the downlink information is carried on a downlink channel. A terminal device sends uplink signals or uplink information to a network device, and the uplink information is carried on an uplink channel. To communicate with a network device, a terminal device needs to establish a wireless connection with a cell controlled by the network device. The cell with which a terminal device has established a wireless connection is called the serving cell of the terminal device.
[0075] Figure 1(b) shows a schematic diagram of a network device. As shown in Figure 1(b), the network device includes one or more CUs, one or more DUs, and one or more RUs. For clarity, Figure 1(b) shows only one CU, DU, and RU. The CU is connected to the core network and one or more DUs. Optionally, the CU may have some of the core network's functionality. The CU may include a CU-control plane (CP) and a CU-user plane (UP).
[0076] The CU and DU can be configured according to the protocol layer functions of the wireless network they implement: for example, the CU is configured to implement the functions of the packet data convergence protocol (PDCP) layer and the protocol layers above it (such as the radio resource control (RRC) layer and / or the service data adaptation protocol (SDAP) layer, etc.); the DU is configured to implement the functions of the protocol layers below the PDCP layer (such as the radio link control (RLC) layer, the medium access control (MAC) layer, and / or the physical (PHY) layer, etc.). For another example, the CU is configured to implement the functions of the protocol layers above the PDCP layer (such as the RRC layer and / or the SDAP layer), and the DU is configured to implement the functions of the PDCP layer and the protocol layers below it (such as the RLC layer, the MAC layer, and / or the PHY layer, etc.).
[0077] The above configuration of CU and DU is only an example, and the functions of CU and DU can also be configured as needed. For example, the CU or DU can be configured to have the functions of more protocol layers, or the CU or DU can be configured to have partial processing functions of the protocol layer. For example, some functions of the RLC layer and the functions of the protocol layers above the RLC layer are set in the CU, and the remaining functions of the RLC layer and the functions of the protocol layers below the RLC layer are set in the DU. For another example, the functions of the CU or DU can be divided according to the service type or other system requirements, such as by delay, and the functions whose processing time needs to meet the smaller delay requirement are set in the DU, and the functions that do not need to meet the delay requirement are set in the CU.
[0078] The DU and RU can work together to implement the functions of the PHY layer. A DU can be connected to one or more RUs. The functions of the DU and RU can be configured in various ways according to the design. For example, the DU is configured to implement the baseband function, and the RU is configured to implement the mid-RF function. For another example, the DU is configured to implement the high-layer functions in the PHY layer, and the RU is configured to implement the low-layer functions in the PHY layer or to implement the low-layer functions and the RF functions. The high-layer functions in the physical layer may include a part of the functions of the physical layer, which is closer to the MAC layer, and the low-layer functions in the physical layer may include another part of the functions of the physical layer, which is closer to the mid-RF side.
[0079] The CU and DU may be set separately, or may be included in the same network element, such as a baseband unit (BBU). The RU may be included in a radio frequency device or a radio frequency unit, such as a remote radio unit (RRU), an active antenna unit 610 (AAU) or a remote radio head (RRH). In different systems, CU, DU or RU may have different names, but those skilled in the art can understand their meanings. For example, in an open radio access network (ORAN) system, CU may also be referred to as O-CU (open CU), DU may also be referred to as O-DU, and RU may also be referred to as O-RU. Any of the CU (or CU-CP, CU-UP), DU and RU in this application may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.
[0080] To facilitate understanding of the present invention, the nouns or terms involved in the present invention are introduced and explained below.
[0081] 1. Four-step random access process
[0082] The terminal device accesses the network device through the random access process. Currently, the random access process is divided into a four-step random access process and a two-step random access process.
[0083] FIG2 is a schematic diagram of a four-step random access process, which includes the following steps:
[0084] In step 201, the terminal device sends a message 1 (Msg1) to the network device. Correspondingly, the network device receives the message 1.
[0085] The terminal device selects and sends a random access preamble (random access preamble) according to system information 1 (SIB1) broadcast by the cell. The random access preamble is carried in message 1.
[0086] This message 1 is also called a random access request message.
[0087] In this application, the random access preamble may also be referred to as a random access channel (RACH) preamble or preamble. For ease of explanation, it is referred to as the preamble in the following. It is described uniformly here and will not be repeated later.
[0088] In step 202, the network device sends message 2 (Msg2) to the terminal device. Correspondingly, the terminal device receives message 2.
[0089] After the network device detects the preamble sent by the terminal device, it sends message 2 to the terminal device, which includes the identifier of the detected preamble, the timing advance (TA) command, the cell radio network temporary identifier (Cell-Radio Network Temporary Identifier, C-RNTI) and the uplink grant scheduling (UL grant) for physical uplink shared channel (PUSCH) transmission.
[0090] This message 2 is also called a random access response message.
[0091] In step 203, the terminal device sends message 3 (Msg3) to the network device. Correspondingly, the network device receives message 3.
[0092] After receiving message 2, the terminal device sends message 3 to the network device on the resources indicated by the UL grant, that is, transmits message 3 on the PUSCH, and the message 3 includes a contention resolution identifier.
[0093] The message 3 is also called a radio resource control setup request (RRCSetupRequest) message.
[0094] Step 204: The network device sends message 4 (Msg4) to the terminal device. Correspondingly, the terminal device receives message 4.
[0095] After receiving message 3, the network device sends message 4 to the terminal device, where message 4 includes a contention resolution identifier.
[0096] After receiving Message 4, the terminal device determines whether the contention resolution identifier in Message 4 is the same as the contention resolution identifier sent by the terminal device in Message 3. If they are the same, the terminal device considers the contention resolved and access successful; if they are different, the terminal device considers the contention failed and can re-initiate the random access process.
[0097] The message 4 is also called a radio resource control setup (RRCSetup) message.
[0098] The above describes a four-step random access process. The following describes a two-step random access process.
[0099] 2. Two-step random access process
[0100] FIG3 is a schematic diagram of a two-step random access process, which includes the following steps:
[0101] Step 301: The terminal device sends message A (MsgA) to the network device. Correspondingly, the network device receives message A.
[0102] This step combines message 1 and message 3 in the four-step random access process into one message, message A, and sends it. Therefore, message A contains the information in message 1 and the information in message 3, such as the preamble and the contention resolution identifier.
[0103] Wherein, before step 301, the terminal device receives system information broadcast by the network device, and the system information includes the correspondence between the random access channel occasion (RACH Occasion, RO) and the physical uplink shared channel occasion (PUSCH Occasion, PO). Wherein, RO indicates the RACH resource, and PO indicates the PUSCH data resource for sending PUSCH data, the demodulation reference signal (demodulation reference signal, DMRS) resource for sending the DMRS sequence, and the DMRS port. Wherein, DMRS resources and PUSCH data resources can be collectively referred to as PUSCH resources. Wherein, PUSCH data resources and DMRS resources are collectively referred to as PUSCH resources. Therefore, in this step 301, the terminal device selects the RACH resource to send the preamble code according to the RO in the system information, and adopts the corresponding DMRS port to perform PUSCH transmission on the corresponding PUSCH data resource, such as sending a contention resolution identifier.
[0104] Among them, RO and PO can be a one-to-one correspondence or a many-to-one relationship.
[0105] Exemplarily, the mapping between RO and PO indicated by the system information includes the following information 1 to information 5:
[0106] Information 1 includes a mapping relationship between RACH resource 1, PUSCH resource 1, and DMRS port 0, wherein PUSCH resource 1 includes PUSCH data resource 1 and DMRS resource 1;
[0107] Information 2 includes a mapping relationship between RACH resource 2, PUSCH resource 1, and DMRS port 1, where PUSCH resource 1 includes PUSCH data resource 1 and DMRS resource 1;
[0108] Information 3 includes a mapping relationship between RACH resource 3, PUSCH resource 2, and DMRS port 0, where PUSCH resource 2 includes PUSCH data resource 2 and DMRS resource 2;
[0109] Information 4 includes a mapping relationship between RACH resource 4, PUSCH resource 2, and DMRS port 1, wherein PUSCH resource 2 includes PUSCH data resource 2 and DMRS resource 2;
[0110] Information 5 includes a mapping relationship between RACH resource 5, PUSCH resource 3, and DMRS port 0, wherein PUSCH resource 3 includes PUSCH data resource 3 and DMRS resource 3.
[0111] Step 302: The network device sends message B (message A, MsgB) to the terminal device. Correspondingly, the terminal device receives message B.
[0112] The network device receives message A, detects the preamble, parses the preamble, and demodulates the PUSCH at the corresponding PO. The network device then sends message B to the terminal device. Message B is a combination of message 2 and message 4 in the four-step random access process. Therefore, message B contains the information in message 2 and message 4.
[0113] After receiving message B, the terminal device determines whether the contention resolution identifier in message B is the same as the contention resolution identifier sent by the terminal device in message A. If they are the same, the terminal device considers the contention resolved and access successful; if they are different, the terminal device considers the contention failed and can re-initiate the random access process.
[0114] The above describes a two-step random access procedure, which can reduce delay and control signaling overhead compared to a four-step random access procedure.
[0115] 3. Channel Estimation and Demodulation Reference Signal (DMRS)
[0116] In order to reduce the physical layer air interface delay, an effective way is to reduce the delay of the physical downlink shared channel (PDSCH) or PUSCH hybrid automatic repeat request (HARQ) processing. The processing flow of the physical layer data signal at the receiving end is decomposed. First, the receiving end performs a Fourier transform (FFT) on the received time domain sampling signal to obtain frequency domain data. Furthermore, in order to restore the original signal, it is necessary to perform channel estimation based on the reference signal, and then compensate for the distortion of the input signal caused by the non-ideal channel through channel equalization, thereby eliminating or reducing the interference problem caused by multipath delay in broadband communication. Finally, the receiving end performs data demodulation and decoding on the equalized signal. For channel estimation, network equipment reduces delay by configuring DMRS. DMRS is used for channel estimation during PDSCH / PUSCH demodulation. Each cell independently configures a set of DMRS generation parameters for the terminal device.
[0117] Based on the different DMRS port divisions, the protocol defines two DMRS configuration types: Type 1 and Type 2. In the time domain, DMRS supports single-symbol and dual-symbol mapping. Type 1 DMRS supports 4 ports (i.e., 4 DMRS ports) when using a single symbol, and 8 ports (i.e., 8 DMRS ports) when using a dual symbol. Type 2 DMRS supports 6 ports (i.e., 6 DMRS ports) when using a single symbol, and 12 ports (i.e., 12 DMRS ports) when using a dual symbol. In the frequency domain, different DMRS ports are divided into different code division multiplexing (CDM) groups. DMRS ports within the same group are spread in the time-frequency domain using orthogonal cover codes (OCC), ensuring orthogonality across different ports. This improves the accuracy of channel estimation. Figure 4(a) shows an example of a DMRS time-frequency resource configuration pattern, where P0, P1, ..., P11 represent DMRS port indices. It can be seen that for DMRS configuration Type 1, when DMRS adopts single symbol mapping, it supports up to 4 DMRS ports, namely P0~P3; for DMRS configuration Type 1, when DMRS adopts dual symbol mapping, it supports up to 8 DMRS ports, namely P0~P7; for DMRS configuration Type 2, when DMRS adopts single symbol mapping, it supports up to 6 DMRS ports, namely P0~P5; for DMRS configuration Type 2, when DMRS adopts dual symbol mapping, it supports up to 12 DMRS ports, namely P0~P11.
[0118] For the configuration of DMRS resources, key parameters include the resource mapping type of PUSCH / PDSCH (i.e. TypeA or TypeB), the DMRS configuration type (i.e. Type1 or Type2), and the number of DMRS symbols (i.e. single symbol or double symbol). Taking the DMRS configuration of PUSCH as an example, the DMRS configuration type is configured by the high-level parameter dmrs-Type; the number of DMRS symbols is determined by the high-level parameter maxLength and the Antenna port field in the downlink control information (DCI). If the maxLength value is 1, it means that the DMRS is a single symbol. When the value is 2, the DCI jointly determines whether it is a single symbol or a double symbol. Figure 4(b) is an example diagram of the resource configuration of the corresponding single-symbol Type1 DMRS under PUSCH TypeA and TypeB mapping. For PUSCH TypeA mapping, PUSCH data is mapped starting from symbol 0, and PUSCH DMRS is mapped starting from symbol 2. For PUSCH Type B mapping, the DMRS is located at the first symbol of the PUSCH. That is, the index of the starting symbol indicated by the start and length indicator value (SLIV) parameter of the PUSCH is 2, and the DMRS is mapped starting from symbol 2. Among them, the PUSCH resources include DMRS resources and PUSCH data resources. The DMRS resources carry different DMRS sequences through different DMRS ports, and the PUSCH data resources are used to carry PUSCH data.
[0119] According to the description of the above two-step random access process, the terminal device sends message A, which specifically includes sending a preamble code carried on the RACH resource, and sending a DMRS sequence and PUSCH data carried on the PUSCH resource corresponding to the RACH resource. The PUSCH data includes a random access request, and the DMRS sequence is sent through the DMRS port corresponding to the RACH resource.
[0120] However, since the number of DMRS ports is currently limited, for example, in the example of Figure 4(a), a maximum of 12 DMRS ports are supported. Therefore, to ensure that the network device's detection performance of PUSCH data is not affected, a maximum of 12 users (i.e., terminal devices) are supported to simultaneously transmit DMRS sequences on different DMRS ports. If more than 12 users transmit DMRS sequences simultaneously, some users will transmit DMRS sequences on the same DMRS port, which will reduce detection performance.
[0121] To solve this problem, this application provides corresponding embodiments, which are described in detail below.
[0122] Figure 5 is a flow chart of a communication method provided in an embodiment of the present application. The method is executed by a network device or a module (such as a chip) of a network device, and a terminal device or a module (such as a chip) of a terminal device. The following description uses the network device and the terminal device as an example to illustrate the method.
[0123] The method comprises the following steps:
[0124] Step 501: The network device sends information of a first model to the terminal device. Correspondingly, the terminal device receives the information of the first model.
[0125] In the embodiment of the present application, the model may also be referred to as a codebook, a dictionary, etc., which are uniformly described here and will not be repeated later.
[0126] The information of the first model includes at least one of an identifier of the first model, network structure information of the first model, or a weight of the first model. The network structure information of the first model is used to indicate information about each node in the first model and the relationships between the nodes. The weight of the first model is used to indicate coefficients or weights between different nodes in the first model.
[0127] For example, the information of the first model includes the identifier of the first model, the network structure information of the first model and the weight of the first model, or includes the network structure information of the first model and the weight of the first model. The terminal device can determine the first model based on the information of the first model.
[0128] For another example, if the terminal device pre-stores an identifier of a first model and network structure information of the first model, the information of the first model sent by the network device in step 501 may include the identifier of the first model and the weight of the first model. The terminal device determines the first model based on the information of the first model received from the network device and the identifier of the first model and network structure information of the first model stored locally. The identifier of the first model and network structure information of the first model pre-stored on the terminal device may be defined by a protocol or standard, or may be pre-configured for the terminal device by the network device.
[0129] For another example, if the terminal device pre-stores an identifier of a first model and a weight of the first model, the information about the first model sent by the network device in step 501 may include the identifier of the first model and the network structure information of the first model. The terminal device determines the first model based on the information about the first model received from the network device and the identifier of the first model and the weight of the first model stored locally. The identifier of the first model and the weight of the first model pre-stored on the terminal device may be defined by a protocol or standard, or may be pre-configured for the terminal device by the network device.
[0130] For another example, if the terminal device pre-stores an identifier of a first model, network structure information of the first model, and a weight of the first model, the information of the first model sent by the network device in step 501 may include the identifier of the first model, and the terminal device determines the first model based on the information of the first model received from the network device and the identifier of the first model, network structure information of the first model, and weight of the first model stored locally. The identifier of the first model, network structure information of the first model, and weight of the first model pre-stored on the terminal device may be defined by a protocol or standard, or may be pre-configured for the terminal device by the network device.
[0131] In one implementation method, the information of the first model may be carried in a system information (SI) and sent. For example, the system information may be SIB1 or other SIBs.
[0132] Step 502: The terminal device determines a DMRS sequence according to the identifier of the preamble code and the first model.
[0133] The preamble code may be randomly selected by the terminal device from a plurality of predefined preamble codes.
[0134] In one implementation method, the terminal device determines the DMRS port number based on the identifier of the preamble code, and then the terminal device inputs the DMRS port number into the first model to obtain a DMRS sequence. That is, the input parameter of the first model is the DMRS port number, and the output parameter is the DMRS sequence. The relationship between the identifier of the preamble code and the DMRS port number can be indicated by the network device. For example, before step 502, the terminal device receives indication information from the network device, and the indication information indicates the correspondence between the RACH resource and the PUSCH resource and the DMRS port. After the terminal device determines the RACH resource for sending the preamble code, it can determine the PUSCH resource and DMRS port number corresponding to the RACH resource. Exemplarily, the indication information can be sent in the same system information as the information of the aforementioned first model, or sent in different system information.
[0135] In another implementation method, the terminal device inputs the identifier of the preamble into the first model to obtain the DMRS sequence. That is, the input parameter of the first model is the identifier of the preamble, and the output parameter is the DMRS sequence.
[0136] Step 503: The terminal device sends a preamble carried on the RACH resource, and a DMRS sequence and PUSCH data carried on the PUSCH resource corresponding to the RACH resource to the network device.
[0137] Step 503 can also be understood as: the terminal device sends MsgA to the network device, where the MsgA includes a preamble carried on the RACH resource, and a DMRS sequence and PUSCH data carried on the PUSCH resource corresponding to the RACH resource, where the PUSCH data includes a random access request.
[0138] It should be noted that if the terminal device determines the DMRS port based on the identifier of the preamble code, and then determines the DMRS sequence based on the DMRS port and the first model, then there is a corresponding relationship between the DMRS sequence and the DMRS port. And in an embodiment of the present application, although the DMRS sequences sent by different terminal devices correspond to different DMRS ports, they can all be mapped to the same DMRS resource, that is, different DMRS ports in the embodiment of the present application correspond to the same DMRS resource. Refer to Figure 6, which is an example diagram of DMRS resource configuration. Different DMRS ports correspond to the same DMRS resource, that is, they all correspond to a whole block of DMRS resources. Therefore, different DMRS sequences are mapped to the same DMRS resource. In addition, the number of DMRS ports is no longer limited. For example, for the example shown in Figure 4 (a), the embodiment of the present application does not need to limit the maximum number of DMRS ports to 4, 6, 8 or 12.
[0139] The terminal device may determine the PUSCH resource corresponding to the RACH resource in any of the following ways:
[0140] Method 1: Before step 503, the terminal device receives indication information from the network device, which indicates the correspondence between RACH resources and PUSCH resources, so that after determining the RACH resource for sending the preamble code, the terminal device can determine the PUSCH resource corresponding to the RACH resource.
[0141] Optionally, the indication information further indicates a correspondence between RACH resources and DMRS ports.
[0142] Method 2: Before step 503, the terminal device receives information of the second model from the network device, and determines the PUSCH resource based on the identifier of the preamble and the second model. That is, the terminal device inputs the identifier of the preamble into the second model to obtain the PUSCH resource.
[0143] Since the preamble is carried on the RACH resource for transmission, and the PUSCH resource is related to the identifier of the preamble, the PUSCH resource and the RACH resource are also associated.
[0144] Optionally, the terminal device may also input the identifier of the preamble code and the first information into the second model to obtain PUSCH resources. The first information includes at least one of the following: the number of times MsgA has been retransmitted, the priority of the terminal device's service, the quality of the synchronization signal block (SSB) measured by the terminal device, or the index of the SSB measured by the terminal device. This method determines the PUSCH resources in combination with the first information, and can map the DMRS sequences sent by different terminal devices to different PUSCH resources to avoid mutual interference as much as possible, thereby improving the success rate of network equipment in detecting PUSCH data.
[0145] Optionally, the terminal device inputs the identifier of the preamble code and the first information into the second model, and can output not only the PUSCH resource, but also at least one of the transmission power of the preamble code, the transmission power of the DMRS sequence, or the transmission power of the PUSCH data. Furthermore, in the above step 503, the terminal device can send the preamble code according to the transmission power of the preamble code, send the DMRS sequence according to the transmission power of the DMRS sequence, and send the PUSCH data according to the transmission power of the PUSCH data. This method helps to reduce the mutual interference when different terminal devices send preamble codes, DMRS sequences, and PUSCH data, thereby improving the success rate of sending preamble codes, DMRS sequences, and PUSCH data, and improving the detection performance of network equipment.
[0146] The information of the second model includes at least one of an identifier of the second model, network structure information of the second model, or a weight of the second model. The network structure information of the second model is used to indicate information about each node in the second model and the relationship between the nodes. The weight of the second model is used to indicate the coefficients or weights between different nodes in the second model.
[0147] For example, the information of the second model includes the identifier of the second model, the network structure information of the second model and the weight of the second model, or includes the network structure information of the second model and the weight of the second model. The terminal device can determine the second model based on the information of the second model.
[0148] For another example, if the terminal device pre-stores the identifier of the second model and the network structure information of the second model, the information about the second model sent by the network device may include the identifier of the second model and the weight of the second model. The terminal device determines the second model based on the information about the second model received from the network device and the identifier of the second model and the network structure information of the second model stored locally. The identifier of the second model and the network structure information of the second model pre-stored on the terminal device may be defined by a protocol or standard, or may be pre-configured for the terminal device by the network device.
[0149] For another example, if the terminal device pre-stores the identifier of the second model and the weight of the second model, the information about the second model sent by the network device may include the identifier of the second model and the network structure information of the second model. The terminal device determines the second model based on the information about the second model received from the network device and the identifier of the second model and the weight of the second model stored locally. The identifier of the second model and the weight of the second model pre-stored on the terminal device may be defined by a protocol or standard, or may be pre-configured for the terminal device by the network device.
[0150] For another example, if the terminal device pre-stores the identifier of the second model, the network structure information of the second model, and the weight of the second model, the information about the second model sent by the network device may include the identifier of the second model, and the terminal device determines the second model based on the information about the second model received from the network device and the identifier of the second model, the network structure information of the second model, and the weight of the second model stored locally. The identifier of the second model, the network structure information of the second model, and the weight of the second model pre-stored on the terminal device may be defined by a protocol or standard, or may be pre-configured for the terminal device by the network device.
[0151] In one implementation method, the information of the second model and the information of the first model can be carried in the same system information and sent, or can be carried in different system information and sent respectively.
[0152] Based on the above steps 501 to 503, the terminal device determines the DMRS sequence according to the identifier of the preamble code and the first model. Different DMRS sequences are sent on the same DMRS resource and are no longer limited to the DMRS port, thereby supporting more terminal devices to request random access at the same time.
[0153] Step 504: The network device receives a preamble carried on the RACH resource.
[0154] That is, the network device performs detection on the RACH resource, detects the preamble, and determines the identifier of the detected preamble.
[0155] Step 505: The network device determines a DMRS sequence according to the identifier of the preamble and the first model.
[0156] The method for the network device to determine the DMRS sequence is the same as the method for the terminal device to determine the DMRS sequence. For a detailed description, please refer to the aforementioned step 502.
[0157] Step 506: The network device determines PUSCH data carried on the PUSCH resource according to the DMRS sequence, the received signal on the PUSCH resource corresponding to the RACH resource, and the third model.
[0158] The network device may determine the PUSCH resource corresponding to the RACH resource in any of the following ways:
[0159] Method A: The network device predetermines the correspondence between RACH resources and PUSCH resources, and notifies the terminal device of the correspondence. The terminal device determines the PUSCH resource corresponding to the RACH resource based on the correspondence, and sends the DMRS sequence and PUSCH data on the PUSCH resource (see the description of the aforementioned step 503 for details). After detecting the preamble code on the RACH resource, the network device also determines the PUSCH resource corresponding to the RACH resource based on the correspondence.
[0160] Method B: The network device determines the PUSCH resource based on the identifier of the preamble and the second model. For example, the network device inputs the identifier of the preamble into the second model to obtain the PUSCH resource, or inputs the identifier of the preamble and the first information into the second model to obtain the PUSCH resource. The first information includes at least one of the following: the number of times MsgA has been retransmitted, the priority of the service of the terminal device, the quality of the SSB measured by the terminal device, or the index of the SSB measured by the terminal device. The second model here is the same model as the second model used by the terminal device in the aforementioned step 503.
[0161] If the terminal device uses method 1 described in step 503 to determine the PUSCH resource, the network device uses method A herein to determine the PUSCH resource; if the terminal device uses method 2 described in step 503 to determine the PUSCH resource, the network device uses method B herein to determine the PUSCH resource. In other words, the terminal device and the network device use the same method to determine the PUSCH resource.
[0162] The received signal on the PUSCH resource includes all contents mapped on the PUSCH resource, such as the DMRS sequence and PUSCH data. The network device inputs the DMRS sequence and the received signal on the PUSCH resource into the third model to obtain the PUSCH data carried on the PUSCH resource.
[0163] In one implementation method, a plurality of third models may be stored on a network device, and different third models may have different performances. For example, the network device may obtain the corresponding third model based on the number of terminal devices that send DMRS sequences on PUSCH resources, that is, the third model used by the network device is related to the number of terminal devices that send DMRS sequences on PUSCH resources. For example, when multiple terminal devices request random requests at the same time, the multiple terminal devices simultaneously send DMRS sequences and random access requests on the same PUSCH resources. If the number of terminal devices is 1 to 10, the first third model is used; if the number of terminal devices is 11 to 20, the second third model is used, and so on. Among them, the performance of the second third model is better than that of the first third model. Based on this method, the corresponding third model is determined based on the number of terminal devices that send DMRS sequences on the same PUSCH resource, which helps to select a third model with appropriate performance for parsing PUSCH data, thereby improving the success rate of data parsing.
[0164] Based on steps 504 to 506 above, the network device determines the DMRS sequence based on the preamble identifier and the first model. Different DMRS sequences are transmitted on the same DMRS resource, freeing the user from the DMRS port. This allows more terminal devices to simultaneously request random access. Furthermore, the network device does not need to perform channel estimation; instead, it inputs the received signal on the PUSCH resource into the third model to obtain PUSCH data. This results in a simpler and more accurate detection method.
[0165] Figure 7 is a flow chart of a communication method provided in an embodiment of the present application. The method is executed by a network device or a module (such as a chip) of the network device, and a terminal device or a module (such as a chip) of the terminal device. The following description uses the network device and the terminal device as an example to illustrate the method.
[0166] The method comprises the following steps:
[0167] Step 701: The network device sends first indication information to the terminal device. Correspondingly, the terminal device receives the first indication information.
[0168] The first indication information indicates the DMRS sequence corresponding to the preamble code. That is, the terminal device can determine the mapping relationship between the preamble code and the DMRS sequence according to the first indication information.
[0169] In one implementation method, the first indication information includes the correspondence between the preamble and the DMRS sequence. Therefore, after selecting the preamble, the terminal device can determine the corresponding DMRS sequence based on the correspondence between the preamble and the DMRS sequence indicated by the first indication information. For example, the first indication information includes (preamble ID#1, DMRS sequence#1), (preamble ID#2, DMRS sequence#2) and (preamble ID#3, DMRS sequence#3). Among them, preamble ID#1 indicates preamble#1, and preamble#1 corresponds to DMRS sequence 1. Preamble ID#2 indicates preamble#2, and preamble#2 corresponds to DMRS sequence 2. Preamble ID#3 indicates preamble#3, and preamble#3 corresponds to DMRS sequence 3. If the preamble selected by the terminal device is preamble#1, the determined DMRS sequence is DMRS sequence#1.
[0170] In another implementation method, the first indication information includes an identifier of a DMRS sequence and a DMRS sequence. The terminal device pre-stores a correspondence between the identifier of the DMRS sequence and the identifier of the preamble. Therefore, after selecting the preamble, the terminal device can determine the DMRS sequence based on the first indication information and the correspondence between the identifier of the DMRS sequence and the identifier of the preamble stored on the terminal device. For example, (preamble ID#1, DMRS sequence ID#1), (preamble ID#2, DMRS sequence ID#2) and (preamble ID#3, DMRS sequence ID#3) are pre-stored on the terminal device. The first indication information includes (DMRS sequence ID#1, DMRS sequence#1), (DMRS sequence ID#2, DMRS sequence#2) and (DMRS sequence ID#3, DMRS sequence#3). If the preamble selected by the terminal device is preamble#1, which is indicated by preamble ID#1, the determined DMRS sequence is DMRS sequence#1.
[0171] Step 702: The terminal device sends a preamble carried on a RACH resource, and a DMRS sequence and PUSCH data carried on a PUSCH resource corresponding to the RACH resource to the network device according to the first indication information.
[0172] Step 702 can also be understood as: the terminal device sends MsgA to the network device, where the MsgA includes a preamble carried on the RACH resource, and a DMRS sequence and PUSCH data carried on the PUSCH resource corresponding to the RACH resource, where the PUSCH data includes a random access request.
[0173] The terminal device may determine the PUSCH resource corresponding to the RACH resource in any of the following ways:
[0174] Method 1: Before step 702, the terminal device receives second indication information from the network device, where the second indication information indicates the correspondence between RACH resources and PUSCH resources, so that after the terminal device determines the RACH resource used to send the preamble code, it can determine the PUSCH resource corresponding to the RACH resource according to the second indication information.
[0175] Optionally, the second indication information further indicates a correspondence between RACH resources and DMRS ports.
[0176] Optionally, the second indication information and the aforementioned first indication information are included in the same system information, or are respectively included in different system information.
[0177] Method 2: Before step 702, the terminal device receives information of the second model from the network device, and determines the PUSCH resource based on the identifier of the preamble and the second model. That is, the terminal device inputs the identifier of the preamble into the second model to obtain the PUSCH resource.
[0178] Since the preamble is carried on the RACH resource for transmission, and the PUSCH resource is related to the identifier of the preamble, the PUSCH resource and the RACH resource are also associated.
[0179] Optionally, the terminal device may also input the identifier of the preamble code and the first information into the second model to obtain PUSCH resources. The first information includes at least one of the following: the number of times MsgA has been retransmitted, the priority of the terminal device's service, the quality of the SSB measured by the terminal device, or the index of the SSB measured by the terminal device. This method determines the PUSCH resources in combination with the first information, and can map the DMRS sequences sent by different terminal devices to different PUSCH resources to avoid mutual interference as much as possible, thereby improving the success rate of network equipment in detecting PUSCH data.
[0180] Optionally, the terminal device inputs the identifier of the preamble code and the first information into the second model, and can output not only the PUSCH resource, but also at least one of the transmit power of the preamble code, the transmit power of the DMRS sequence, or the transmit power of the PUSCH data. Furthermore, in the above step 702, the terminal device can send the preamble code according to the transmit power of the preamble code, send the DMRS sequence according to the transmit power of the DMRS sequence, and send the PUSCH data according to the transmit power of the PUSCH data. This method helps to reduce the mutual interference when different terminal devices send preamble codes, DMRS sequences, and PUSCH data, thereby improving the success rate of sending preamble codes, DMRS sequences, and PUSCH data, and improving the detection performance of network equipment.
[0181] The information of the second model includes at least one of an identifier of the second model, network structure information of the second model, or a weight of the second model. The network structure information of the second model is used to indicate information about each node in the second model and the relationship between the nodes. The weight of the second model is used to indicate the coefficients or weights between different nodes in the second model.
[0182] For example, the information of the second model includes the identifier of the second model, the network structure information of the second model and the weight of the second model, or includes the network structure information of the second model and the weight of the second model. The terminal device can determine the second model based on the information of the second model.
[0183] For another example, if the terminal device pre-stores the identifier of the second model and the network structure information of the second model, the information about the second model sent by the network device may include the identifier of the second model and the weight of the second model. The terminal device determines the second model based on the information about the second model received from the network device and the identifier of the second model and the network structure information of the second model stored locally. The identifier of the second model and the network structure information of the second model pre-stored on the terminal device may be defined by a protocol or standard, or may be pre-configured for the terminal device by the network device.
[0184] For another example, if the terminal device pre-stores the identifier of the second model and the weight of the second model, the information about the second model sent by the network device may include the identifier of the second model and the network structure information of the second model. The terminal device determines the second model based on the information about the second model received from the network device and the identifier of the second model and the weight of the second model stored locally. The identifier of the second model and the weight of the second model pre-stored on the terminal device may be defined by a protocol or standard, or may be pre-configured for the terminal device by the network device.
[0185] For another example, if the terminal device pre-stores the identifier of the second model, the network structure information of the second model, and the weight of the second model, the information about the second model sent by the network device may include the identifier of the second model, and the terminal device determines the second model based on the information about the second model received from the network device and the identifier of the second model, the network structure information of the second model, and the weight of the second model stored locally. The identifier of the second model, the network structure information of the second model, and the weight of the second model pre-stored on the terminal device may be defined by a protocol or standard, or may be pre-configured for the terminal device by the network device.
[0186] In one implementation method, the information of the second model can be carried in the same system information as the aforementioned first indication information and sent, or can be carried in different system information and sent respectively.
[0187] Based on the above steps 701 to 702, the terminal device determines the DMRS sequence according to the first indication information, and different DMRS sequences are sent on the same DMRS resource, which is no longer limited to the DMRS port, thereby supporting more terminal devices to request random access at the same time.
[0188] Step 703: The network device receives a preamble carried on a RACH resource.
[0189] That is, the network device performs detection on the RACH resource, detects the preamble, and determines the identifier of the detected preamble.
[0190] Step 704: The network device determines a DMRS sequence according to the identifier of the preamble.
[0191] The method for the network device to determine the DMRS sequence is the same as the method for the terminal device to determine the DMRS sequence. For a specific description, please refer to the aforementioned step 702.
[0192] Step 705: The network device determines PUSCH data carried on the PUSCH resource according to the DMRS sequence, a received signal on the PUSCH resource corresponding to the RACH resource, and the third model.
[0193] The network device may determine the PUSCH resource corresponding to the RACH resource in any of the following ways:
[0194] Method A: The network device predetermines the correspondence between RACH resources and PUSCH resources and notifies the terminal device of the correspondence. The terminal device determines the PUSCH resource corresponding to the RACH resource based on the correspondence and sends the DMRS sequence and PUSCH data on the PUSCH resource (see the description of the aforementioned step 702 for details). After detecting the preamble code on the RACH resource, the network device also determines the PUSCH resource corresponding to the RACH resource based on the correspondence.
[0195] Method B: The network device determines the PUSCH resource based on the identifier of the preamble and the second model. For example, the network device inputs the identifier of the preamble into the second model to obtain the PUSCH resource, or inputs the identifier of the preamble and the first information into the second model to obtain the PUSCH resource. The first information includes at least one of the following: the number of times MsgA has been retransmitted, the priority of the service of the terminal device, the quality of the SSB measured by the terminal device, or the index of the SSB measured by the terminal device. The second model here is the same model as the second model used by the terminal device in the aforementioned step 702.
[0196] If the terminal device determines the PUSCH resource using method 1 described in step 702 above, the network device determines the PUSCH resource using method A here; if the terminal device determines the PUSCH resource using method 2 described in step 702 above, the network device determines the PUSCH resource using method B here. That is, the terminal device and the network device use the same method to determine the PUSCH resource.
[0197] The received signal on the PUSCH resource includes all contents mapped on the PUSCH resource, such as the DMRS sequence and PUSCH data. The network device inputs the DMRS sequence and the received signal on the PUSCH resource into the third model to obtain the PUSCH data carried on the PUSCH resource.
[0198] In one implementation method, a plurality of third models may be stored on a network device, and different third models may have different performances. For example, the network device may obtain the corresponding third model based on the number of terminal devices that send DMRS sequences on PUSCH resources, that is, the third model used by the network device is related to the number of terminal devices that send DMRS sequences on PUSCH resources. For example, when multiple terminal devices simultaneously request a random request, the multiple terminal devices simultaneously send a DMRS sequence and a random access request on the same PUSCH resource. If the number of terminal devices is 1 to 10, the first third model is used; if the number of terminal devices is 11 to 20, the second third model is used, and so on. Among them, the performance of the second third model is better than that of the first third model.
[0199] Based on steps 703 to 705 above, the network device determines the DMRS sequence based on the identifier of the preamble. Different DMRS sequences are transmitted on the same DMRS resource, freeing the device from being restricted by DMRS ports. This allows more terminal devices to simultaneously request random access. Furthermore, the network device does not need to perform channel estimation; instead, it inputs the received signal on the PUSCH resource into the third model to obtain PUSCH data. This results in a simpler and more accurate detection method.
[0200] It is understood that in order to implement the functions in the above embodiments, the terminal device or network device includes hardware structures and / or software modules corresponding to the execution of each function. It should be readily apparent to those skilled in the art that, in combination with the units and method steps of each example described in the embodiments disclosed in this application, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in hardware or in a manner driven by computer software depends on the specific application scenario and design constraints of the technical solution.
[0201] Figures 8 and 9 are schematic diagrams of the structures of possible communication devices provided in embodiments of the present application. These communication devices can be used to implement the functions of the terminal device or network device in the above method embodiments, thereby also achieving the beneficial effects of the above method embodiments. In the embodiments of the present application, the communication device can be a terminal device or a network device, or a module (such as a chip) applied to the terminal device or the network device.
[0202] The communication device 800 shown in Figure 8 includes a processing unit 810 and a transceiver unit 820. The communication device 800 is used to implement the functions of the terminal device or network device in the above method embodiment.
[0203] When the communication device 800 is used to implement the functions of the terminal device in the above method embodiment, the transceiver unit 820 is used to receive information of the first model; the processing unit 810 is used to determine the DMRS sequence based on the identifier of the preamble code and the first model; the transceiver unit 820 is further used to send the preamble code carried on the RACH resource, and the DMRS sequence and PUSCH data carried on the PUSCH resource corresponding to the RACH resource.
[0204] In one possible implementation method, the processing unit 810 is used to determine the DMRS sequence based on the identifier of the preamble code and the first model, specifically including: determining the DMRS port number based on the identifier of the preamble code; and inputting the DMRS port number into the first model to obtain the DMRS sequence; or, inputting the identifier of the preamble code into the first model to obtain the DMRS sequence.
[0205] In a possible implementation method, the transceiver unit 820 is further configured to receive indication information, where the indication information indicates a correspondence between the RACH resources and the PUSCH resources.
[0206] In a possible implementation method, the information of the first model and the indication information are included in the same system information, or are respectively included in different system information.
[0207] In a possible implementation method, the transceiver unit 820 is further configured to receive information of a second model; and determine the PUSCH resource according to the identifier of the preamble code and the second model.
[0208] In a possible implementation method, the information of the first model and the information of the second model are included in the same system information, or are respectively included in different system information.
[0209] In one possible implementation method, the information of the first model includes at least one of the identification of the first model, the network structure information of the first model, or the weight of the first model; the information of the second model includes at least one of the identification of the second model, the network structure information of the second model, or the weight of the second model.
[0210] In one possible implementation method, the processing unit 810 is used to determine the PUSCH resource based on the identifier of the preamble code and the second model, specifically including: determining the PUSCH resource based on the identifier of the preamble code, first information and the second model, the first information including at least one of the following: the priority of the service of the terminal device, the quality of the SSB measured by the terminal device, or the index of the SSB measured by the terminal device.
[0211] In one possible implementation method, the processing unit 810 is further used to determine at least one of the transmission power of the preamble code, the transmission power of the DMRS sequence, or the transmission power of the PUSCH data based on the identifier of the preamble code, the first information, and the second model.
[0212] When the communication device 800 is used to implement the function of the terminal device in the above method embodiment, the transceiver unit 820 is used to receive first indication information, where the first indication information indicates a DMRS sequence corresponding to the preamble code; the processing unit 810 is used to send the preamble code carried on the RACH resource and the DMRS sequence and PUSCH data carried on the PUSCH resource corresponding to the RACH resource through the transceiver unit 820 according to the first indication information.
[0213] In a possible implementation method, the first indication information includes a correspondence between the preamble code and the DMRS sequence.
[0214] In one possible implementation method, the first indication information includes the identifier of the DMRS sequence and the DMRS sequence; the processing unit 810 is also used to determine the DMRS sequence based on the first indication information and the correspondence between the identifier of the DMRS sequence and the identifier of the preamble code.
[0215] In a possible implementation method, the transceiver unit 820 is further configured to receive second indication information, where the second indication information indicates a correspondence between the RACH resources and the PUSCH resources.
[0216] In a possible implementation method, the first indication information and the second indication information are included in the same system information, or are respectively included in different system information.
[0217] In a possible implementation method, the transceiver unit 820 is further configured to receive information of a second model; and determine the PUSCH resource according to the identifier of the preamble code and the second model.
[0218] In a possible implementation method, the first indication information and the information of the second model are included in the same system information, or are respectively included in different system information.
[0219] In a possible implementation method, the information of the second model includes at least one of an identifier of the second model, network structure information of the second model, or a weight of the second model.
[0220] In one possible implementation method, the processing unit 810 is used to determine the PUSCH resource based on the identifier of the preamble code and the second model, specifically including: determining the PUSCH resource based on the identifier of the preamble code, first information and the second model, the first information including at least one of the following: the priority of the service of the terminal device, the quality of the SSB measured by the terminal device, or the index of the SSB measured by the terminal device.
[0221] In one possible implementation method, the processing unit 810 is further used to determine at least one of the transmission power of the preamble code, the transmission power of the DMRS sequence, or the transmission power of the PUSCH data based on the identifier of the preamble code, the first information, and the second model.
[0222] When the communication device 800 is used to implement the functions of the network device in the above method embodiment, the transceiver unit 820 is used to receive a preamble code carried on the RACH resource; the processing unit 810 is used to determine the DMRS sequence according to the identifier of the preamble code; and determine the PUSCH data carried on the PUSCH resource based on the DMRS sequence, the received signal on the PUSCH resource corresponding to the RACH resource, and the third model.
[0223] In a possible implementation method, the processing unit 810 is configured to determine the DMRS sequence according to the identifier of the preamble code, specifically including: determining the DMRS sequence according to the identifier of the preamble code and a first model.
[0224] In one possible implementation method, the processing unit 810 is used to determine the DMRS sequence based on the identifier of the preamble code and the first model, specifically including: determining the DMRS port number based on the identifier of the preamble code; and inputting the DMRS port number into the first model to obtain the DMRS sequence; or, inputting the identifier of the preamble code into the first model to obtain the DMRS sequence.
[0225] In a possible implementation method, the transceiver unit 820 is further configured to send information of the first model.
[0226] In a possible implementation method, the information of the first model includes at least one of an identifier of the first model, network structure information of the first model, or a weight of the first model.
[0227] In a possible implementation method, the processing unit 810 is further configured to determine the PUSCH resource according to the identifier of the preamble code and the second model.
[0228] In a possible implementation method, the transceiver unit 820 is further configured to send information of the second model.
[0229] In a possible implementation method, the information of the second model includes at least one of an identifier of the second model, network structure information of the second model, or a weight of the second model.
[0230] In a possible implementation method, the processing unit 810 is further configured to obtain the third model according to the number of terminal devices that send DMRS sequences on the PUSCH resources.
[0231] For a more detailed description of the processing unit 810 and the transceiver unit 820, reference can be made to the relevant description in the above method embodiment, which will not be repeated here.
[0232] The communication device 900 shown in Figure 9 includes a processor 910 and an interface circuit 920. The processor 910 and the interface circuit 920 are coupled to each other. It is understood that the interface circuit 920 can be a transceiver or an input / output interface. Optionally, the communication device 900 may also include a memory 930 for storing instructions executed by the processor 910, or storing input data required by the processor 910 to execute instructions, or storing data generated after the processor 910 executes instructions.
[0233] When the communication device 900 is used to implement the above method embodiment, the processor 910 is used to implement the functions of the above processing unit 810 , and the interface circuit 920 is used to implement the functions of the above transceiver unit 820 .
[0234] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.
[0235] An embodiment of the present application also provides a chip (or chip system), which includes a processor, the processor is coupled to a memory, and the memory stores a computer program; the processor is used to call part or all of the computer program in the memory, so that any implementation method of the above-mentioned first to third aspects is executed.
[0236] The method steps in the embodiments of the present application can be implemented by hardware or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, mobile hard disks, compact disc read-only memory (CD-ROM) or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and storage medium can be located in an ASIC. In addition, the ASIC can be located in a terminal device or a network device. Of course, the processor and storage medium can also exist as discrete components in an access network device or a terminal.
[0237] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. A computer program refers to a set of instructions that instruct an electronic computer or other device with message processing capabilities to perform each step of the action, usually written in a certain programming language and running on a certain target architecture. When the computer program or instruction is loaded and executed on a computer, the process or function described in the embodiment of the present application is executed in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable device. The computer program or instruction can 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 program or instruction can be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired or wireless means. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; an optical medium, such as a digital video disk; or a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both volatile and non-volatile types of storage media.
[0238] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.
[0239] In this application, "at least one" means one or more, and "more" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. In the text description of this application, the character " / " generally indicates that the previous and next related objects are in an "or" relationship; in the formulas of this application, the character " / " indicates that the previous and next related objects are in a "division" relationship.
[0240] It is understood that the various numbers used in the embodiments of this application are merely for ease of description and are not intended to limit the scope of the embodiments of this application. The order of the sequence numbers of the above-mentioned processes does not necessarily imply a specific order of execution; the order of execution of the processes should be determined by their functions and inherent logic.
Claims
1. A communication method, characterized in that: The method comprises: receiving information of a first model; Determine a demodulation reference signal (DMRS) sequence according to the identifier of the preamble and the first model; The preamble carried on a random access channel RACH resource and the DMRS sequence and PUSCH data carried on a physical uplink shared channel PUSCH resource corresponding to the RACH resource are sent.
2. The method according to claim 1, wherein The determining, according to the identifier of the preamble and the first model, a DMRS sequence includes: Determine a DMRS port number according to the identifier of the preamble; and input the DMRS port number into the first model to obtain the DMRS sequence; or, The identifier of the preamble code is input into the first model to obtain the DMRS sequence.
3. The method according to claim 1 or 2, wherein: The method further comprises: Indication information is received, where the indication information indicates a correspondence between the RACH resource and the PUSCH resource.
4. The method according to claim 3, wherein The information of the first model and the indication information are included in the same system information, or are respectively included in different system information.
5. The method according to claim 1 or 2, wherein: The method further comprises: receiving information of the second model; The PUSCH resource is determined according to the identifier of the preamble code and the second model.
6. The method according to claim 5, wherein The information of the first model and the information of the second model are included in the same system information, or are respectively included in different system information.
7. The method according to claim 5 or 6, wherein: The information of the first model includes at least one of an identifier of the first model, network structure information of the first model, or a weight of the first model; The information of the second model includes at least one of an identifier of the second model, network structure information of the second model, or a weight of the second model.
8. The method according to any one of claims 5 to 7, characterized in that The determining the PUSCH resource according to the identifier of the preamble and the second model includes: The PUSCH resource is determined based on the identifier of the preamble code, the first information and the second model, where the first information includes at least one of the following: the priority of the service of the terminal device, the quality of the synchronization signal block SSB measured by the terminal device, or the index of the SSB measured by the terminal device.
9. The method according to claim 8, wherein The method further comprises: At least one of the transmission power of the preamble, the transmission power of the DMRS sequence, or the transmission power of the PUSCH data is determined according to the identifier of the preamble, the first information, and the second model.
10. A communication method, characterized in that: The method comprises: receiving first indication information, where the first indication information indicates a demodulation reference signal (DMRS) sequence corresponding to a preamble; According to the first indication information, the preamble carried on a random access channel RACH resource and the DMRS sequence and PUSCH data carried on a physical uplink shared channel PUSCH resource corresponding to the RACH resource are sent.
11. The method according to claim 10, wherein The first indication information includes a correspondence between the preamble code and the DMRS sequence.
12. The method according to claim 10, wherein The first indication information includes an identifier of the DMRS sequence and the DMRS sequence; the method further includes: The DMRS sequence is determined according to the first indication information and the correspondence between the identifier of the DMRS sequence and the identifier of the preamble code.
13. The method according to any one of claims 10 to 12, characterized in that The method further comprises: Second indication information is received, where the second indication information indicates a correspondence between the RACH resource and the PUSCH resource.
14. The method according to claim 13, wherein The first indication information and the second indication information are included in the same system information, or are respectively included in different system information.
15. The method according to any one of claims 10 to 12, characterized in that The method further comprises: receiving information of the second model; The PUSCH resource is determined according to the identifier of the preamble code and the second model.
16. The method according to claim 15, wherein The first indication information and the information of the second model are included in the same system information, or are respectively included in different system information.
17. The method according to claim 15 or 16, wherein: The information of the second model includes at least one of an identifier of the second model, network structure information of the second model, or a weight of the second model.
18. The method according to any one of claims 15 to 17, characterized in that The determining the PUSCH resource according to the identifier of the preamble and the second model includes: The PUSCH resource is determined based on the identifier of the preamble code, the first information and the second model, where the first information includes at least one of the following: the priority of the service of the terminal device, the quality of the synchronization signal block SSB measured by the terminal device, or the index of the SSB measured by the terminal device.
19. The method according to claim 18, wherein The method further comprises: At least one of the transmission power of the preamble, the transmission power of the DMRS sequence, or the transmission power of the PUSCH data is determined according to the identifier of the preamble, the first information, and the second model.
20. A communication method, characterized in that: The method comprises: Receive a preamble carried on a random access channel RACH resource; Determining a demodulation reference signal (DMRS) sequence according to an identifier of the preamble; PUSCH data carried on the PUSCH resource is determined according to the DMRS sequence, a received signal on a physical uplink shared channel PUSCH resource corresponding to the RACH resource, and a third model.
21. The method according to claim 20, wherein The determining, according to the identifier of the preamble, a DMRS sequence includes: The DMRS sequence is determined according to the identifier of the preamble code and the first model.
22. The method according to claim 21, wherein The determining, according to the identifier of the preamble and the first model, a DMRS sequence includes: Determine a DMRS port number according to the identifier of the preamble; and input the DMRS port number into the first model to obtain the DMRS sequence; or, The identifier of the preamble code is input into the first model to obtain the DMRS sequence.
23. The method according to claim 21 or 22, wherein: The method further comprises: The information of the first model is sent.
24. The method according to any one of claims 21 to 23, characterized in that The information of the first model includes at least one of an identifier of the first model, network structure information of the first model, or a weight of the first model.
25. The method according to any one of claims 20 to 24, characterized in that The method further comprises: The PUSCH resource is determined according to the identifier of the preamble code and the second model.
26. The method of claim 25, wherein: The method further comprises: Send the second model information.
27. The method according to claim 25 or 26, wherein The information of the second model includes at least one of an identifier of the second model, network structure information of the second model, or a weight of the second model.
28. The method according to any one of claims 20 to 27, characterized in that The method further comprises: The third model is obtained according to the number of terminal devices that send DMRS sequences on the PUSCH resources.
29. A communication device, characterized in that: The invention comprises a processor and an interface circuit, wherein the processor is used to communicate with other devices through the interface circuit and execute the method described in any one of claims 1 to 9, or execute the method described in any one of claims 10 to 19, or execute the method described in any one of claims 20 to 28.
30. A chip, characterized in that: The chip includes a processor, which is coupled to a memory, and the memory stores a computer program; the processor is used to call part or all of the computer program in the memory, so that the method described in any one of claims 1 to 9, or the method described in any one of claims 10 to 19, or the method described in any one of claims 20 to 28 is executed.
31. A computer program product, characterized in that The computer program product comprises instructions, which, when executed on a processor, cause the method of any one of claims 1 to 9, or the method of any one of claims 10 to 19, or the method of any one of claims 20 to 28 to be performed.
32. A computer-readable storage medium, characterized in that The storage medium stores a computer program or instruction. When the computer program or instruction is executed by the communication device, it implements the method described in any one of claims 1 to 9, or implements the method described in any one of claims 10 to 19, or implements the method described in any one of claims 20 to 28.
Citation Information
Patent Citations
Random access method and device, terminal and network side equipment
CN114599111A
Random access method, communication device and communication equipment
CN116528385A
Methods and apparatus for msg-a transmission in two-step rach
US20220086915A1
Random access method, communication apparatus and communication device
WO2023138606A1