Communication method and related product
By sending PUSCH resource information instructions through the network device, the terminal device can determine the resources that match it, which solves the problem of the terminal having difficulty in determining the response and improves communication efficiency and reliability.
Patent Information
- Application Number
- PCT/CN2026/093753
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2026-04-29
- Publication Date
- 2026-11-12
AI Technical Summary
In existing technologies, when the network side sends information responses to multiple PUSCH resources, it is difficult for the terminal to determine whether the response corresponds to itself, which leads to a decrease in communication efficiency and reliability.
By sending PUSCH resource information instructions, the network device can determine the resources that match its own based on the information, thereby improving communication efficiency and reliability.
By using a single PUSCH resource information indication, the communication efficiency and reliability between the network device and multiple terminal devices are ensured, and the terminal devices can quickly determine retransmission information and reduce resource consumption.
Smart Images

Figure CN2026093753_12112026_PF_FP_ABST
Abstract
Description
Communication methods and related products
[0001] This application claims priority to Chinese Patent Application No. 202510600045.0, filed on May 9, 2025, entitled "Communication Method and Related Products", the entire contents of which are incorporated herein by reference. Technical Field
[0002] This application relates to the field of wireless communication technology, and in particular to a communication method and related products. Background Technology
[0003] The current discussion focuses on two-step EDT or contention-based msg3 for early data transmission (CB-msg3-EDT), where a single data transmission only includes msg3 and msg4. To improve the efficiency of msg3 contention resolution, a slotted ALOHA (SA) mechanism is introduced to support the transmission of a single msg3, and a diversity slotted ALOHA (DSA) mechanism is introduced to support the transmission of multiple msg3 replicas (i.e., two or more msg3s). Taking the contention-based msg3 EDT process using the DSA mechanism as an example, the network side configures a msg3 transmission window. Within the selected msg3 transmission window, the terminal randomly selects N uplink physical shared channel (PUSCH) resources (or PUSCH occasions) in the time domain to send N msg3s (also known as msg3 replicas). The terminal then starts a msg4 monitoring window to receive msg4. msg4 can include feedback information (response information) for multiple terminals, that is, multiple terminals share a single msg4 message. A msg4 can contain a backoff message and a contention resolution success response for at least one terminal.
[0004] The technical problem with existing technologies is that when the network side responds to information sent by one or more terminals on multiple PUSCH resources, how can the terminal determine that the response corresponds to itself? Summary of the Invention
[0005] This application provides a communication method and related products. A network device indicates the PUSCH resource information used to send the first information, so that a terminal device can determine a match with the indication based on the PUSCH resource information, thereby realizing communication between the network device and the terminal device. This process ensures the efficiency and reliability of communication between the terminal device and the network device.
[0006] In a first aspect, this application provides a communication method applied to a terminal device. The method includes: receiving configuration information; wherein the configuration information is used to indicate M PUSCH resources, where M is a positive integer; sending N first messages; wherein the first messages are used to send user data based on a contention-based resolution method, and the N uplink resources used to transmit the N first messages are selected from the M PUSCH resources, where N is a positive integer less than or equal to M; receiving second information, the second information including at least one indication, wherein the first indication in the at least one indication includes i-th PUSCH resource information, and the i-th PUSCH resource information is used to send one of the N first messages.
[0007] The above method can be applied to terminal devices, which can be terminal equipment, modules within terminal equipment (such as chip systems), or logical nodes, logical modules, or software capable of implementing all or part of the functions of the terminal equipment. There are no limitations on this.
[0008] From a technical perspective, the network device sends a second message to indicate the PUSCH resource information used for the transmission of the first message. After receiving the second message, the terminal device determines itself as the terminal device matched by the indication based on the PUSCH resource information, and then executes subsequent steps. This process enables the network device to communicate with one or more terminal devices corresponding to the PUSCH resource information through a single PUSCH resource information indication, improving communication efficiency and ensuring communication reliability.
[0009] In one feasible implementation, each of the at least one indication is used to indicate the retransmission of the first information, and the first indication is used to indicate at least one terminal device that sent the first information using the i-th PUSCH resource information to retransmit the first information.
[0010] This method involves the network device sending a second message indicating the PUSCH resource information used in the transmission of first information that was not correctly received (or successfully decoded), and instructing the matching terminal device to retransmit the first information. The terminal device determines that it matches the indication based on the PUSCH resource information, and thus determines the first information it needs to retransmit. This process enables the terminal device to quickly determine the first information it needs to retransmit, improving the processing efficiency and accuracy of the terminal equipment.
[0011] In one feasible implementation, the second information is sent via at least one Media Access Control Layer Sub-Protocol Data Unit (MAC subPDU) or via Downlink Control Information (DCI), with at least one MAC subPDU used to determine the contention resolution status.
[0012] In one feasible implementation, each of the at least one indications is a MAC subPDU corresponding to the fallback response, and the i-th PUSCH resource information is included in the fallback response or the MAC subheader of the fallback response.
[0013] At least one indication in the second information is located in the MACsubPDU of the fallback response, which can reduce the complexity of data unit modification and reduce the time cost of the network device sending the second information.
[0014] In one feasible implementation, the second information further includes at least one contention resolution response indication, wherein the first contention resolution response indication of the at least one contention resolution response indication is one or more corresponding responses of N first information, and the method further includes: ignoring the first indication or canceling the retransmission of the first information; or processing at least one contention resolution response indication, and stopping the processing of other MAC subPDUs after processing the first contention resolution response indication.
[0015] This process means that when the terminal device receives a contention resolution response indication by receiving the second information, it may choose not to retransmit the first information, or it may process the contention resolution response indication first and then determine whether to retransmit the first information. This avoids unnecessary retransmission operations and reduces resource consumption during communication.
[0016] In one feasible implementation, the second indication of at least one indication is used to indicate at least one of the following: retransmitting the first information in a manner based on orthogonal coverage code (OCC); retransmitting the first information in a manner based on non-OCC; or sending user data in a manner based on random access.
[0017] In this embodiment, the network device sends second information to indicate the PUSCH resource information used in the incorrectly received first information transmission and to instruct the matching terminal device on how to retransmit the first information. Upon receiving the second information, the terminal device determines that it matches the instruction based on the PUSCH resource information and then determines its own method for retransmitting the first information. This process ensures the accuracy of the instruction information obtained by the terminal device from the network device and guarantees that the terminal device retransmits the first information according to the retransmission method indicated by the network device, thereby improving the efficiency and reliability of the communication process.
[0018] In one feasible implementation, the second instruction includes j-th PUSCH resource information, which is used to send one of the N first messages.
[0019] In one feasible implementation, the fallback response or the MAC subheader of the fallback response includes 1 bit of information to indicate whether the first information is retransmitted using an OCC-based method or a non-OCC-based method; the fallback response does not include uplink grant information to indicate whether user data is sent using a random access method.
[0020] By setting 1 bit in the existing fallback response MAC header to indicate whether the retransmission of the first information is OCC or non-OCC, the complexity of modifying data units is reduced. Furthermore, determining whether to use the RA-based method to send user data by checking for the presence of uplink grant information further reduces the complexity of the network device sending indication information, thereby reducing communication time costs.
[0021] Secondly, this application provides a communication method applied to a network device. The method includes: sending configuration information; wherein the configuration information indicates M PUSCH resources, where M is a positive integer; receiving first information; wherein the first information is user data sent based on a contention-based resolution method, and the N uplink resources used to transmit the first information are selected from the M PUSCH resources, where N is a positive integer less than or equal to M; and sending second information, the second information including at least one indication, wherein the first indication in the at least one indication includes information about an i-th PUSCH resource, and the i-th PUSCH resource information is used to send one of the N pieces of first information.
[0022] The above method can be applied to network devices, which can be network equipment, modules within network equipment (such as chip systems), or logical nodes, logical modules, or software that can implement all or part of the functions of a network device. There are no limitations on this.
[0023] In one feasible implementation, each of the at least one indication is used to indicate the retransmission of the first information, and the first indication is used to indicate at least one terminal device that sent the first information using the i-th PUSCH resource information to retransmit the first information.
[0024] In one feasible implementation, the second information is sent via at least one Media Access Control Layer Sub-Protocol Data Unit (MAC subPDU) or via Downlink Control Information (DCI), with at least one MAC subPDU used to determine the contention resolution status.
[0025] In one feasible implementation, each of the at least one indications is a MAC subPDU corresponding to the fallback response, and the i-th PUSCH resource information is included in the fallback response or the MAC subheader of the fallback response.
[0026] In one feasible implementation, the second information further includes at least one contention resolution response indication, wherein the first contention resolution response indication of the at least one contention resolution response indication is one or more corresponding responses of the N first information.
[0027] In one feasible implementation, the second indication of at least one indication is used to indicate at least one of the following: retransmitting the first information in a manner based on orthogonal coverage code (OCC); retransmitting the first information in a manner based on non-OCC; or sending user data in a manner based on random access.
[0028] In one feasible implementation, the second instruction includes j-th PUSCH resource information, which is used to send one of the N first messages.
[0029] In one feasible implementation, the fallback response or the media access control layer subheader of the fallback response includes 1 bit of information to indicate whether the first information is retransmitted using an OCC-based method or a non-OCC-based method; the fallback response does not include uplink authorization information to indicate whether user data is sent using a random access method.
[0030] Thirdly, a communication device is provided, which includes units or modules for performing the possible methods in either the first or second aspect described above.
[0031] Fourthly, embodiments of this application provide a communication device, the communication device including at least one processor coupled to a memory; wherein the at least one processor is configured to execute a computer program or instructions stored in the memory, such that the methods that may be implemented in either the first or second aspect described above are executed.
[0032] Fifthly, embodiments of this application provide a communication system, which includes a terminal device and a network device, wherein the terminal device is used to perform the method described in any one of the first aspects, and the network device is used to perform the method described in any one of the second aspects.
[0033] Sixthly, embodiments of this application provide a computer-readable storage medium storing computer instructions that, when executed, cause the computer to perform the method described in any of the above methods.
[0034] In a seventh aspect, embodiments of this application provide a computer program product, the computer program product comprising: computer program code, which, when executed by a computer, causes the computer to perform the method described in any of the above methods.
[0035] Eighthly, embodiments of this application provide a chip coupled to a memory for reading and executing program instructions in the memory, so that the device in which the chip is located implements the method described in any of the above methods. Attached Figure Description
[0036] The accompanying drawings used in the embodiments of this application are described below.
[0037] Figure 1A is a schematic diagram of the architecture of the communication system used in the embodiments of this application.
[0038] Figure 1B is a schematic diagram of the protocol stack of a RAN node provided in an embodiment of this application.
[0039] Figure 1C is an ORAN architecture diagram provided in an embodiment of this application.
[0040] Figures 1D to 1G are schematic diagrams of the NTN-based RAN architecture provided in the embodiments of this application.
[0041] Figure 2A is a flowchart of a competition-based four-step RA provided in an embodiment of this application.
[0042] Figure 2B is a flowchart of a two-step RA based on competition provided in an embodiment of this application.
[0043] Figure 2C is a flowchart of another competition-based two-step RA provided in the embodiments of this application.
[0044] Figure 2D is a schematic diagram of the components of a MAC PDU provided in an embodiment of this application.
[0045] Figure 2E is a schematic diagram of a fallback response MAC subheader provided in an embodiment of this application.
[0046] Figure 2F is a schematic diagram of a fallback response MAC sub-PDU provided in an embodiment of this application.
[0047] Figure 3A is a schematic diagram of a transmission process based on the SA protocol provided in an embodiment of this application.
[0048] Figure 3B is a schematic diagram of a transmission process based on the DAS protocol provided in an embodiment of this application.
[0049] Figure 3C is a flowchart of a CB-msg3-EDT using the DSA mechanism provided in an embodiment of this application.
[0050] Figure 4 is a flowchart of a communication method provided in an embodiment of this application.
[0051] Figure 5A is a flowchart of another communication method provided in an embodiment of this application.
[0052] Figure 5B is a schematic diagram illustrating the indication of PUSCH resource information provided in an embodiment of this application.
[0053] Figure 6A is a flowchart of another communication method provided in an embodiment of this application.
[0054] Figure 6B is a schematic diagram of the method for instructing the retransmission of the first information provided in an embodiment of this application.
[0055] Figure 7 is a schematic diagram of the structure of a communication device provided in an embodiment of this application.
[0056] Figure 8 is a simplified structural diagram of a network device provided in an embodiment of this application.
[0057] Figure 9 is a schematic diagram of a RAN chip structure provided in an embodiment of this application.
[0058] Figure 10 is a simplified structural diagram of a UE provided in an embodiment of this application. Detailed Implementation
[0059] The technical solutions in the embodiments of this application will be described below with reference to the accompanying drawings. The terms "system" and "network" in the embodiments of this application are used interchangeably. Unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship; for example, A / B can represent A or B. "And / or" in this application merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more... "At least one of the following" or similar expressions refer to any combination of these items, including any combination of a single item or a plurality of items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be one or more. Furthermore, to facilitate a clear description of the technical solutions of the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish between network elements and identical or similar items with substantially the same function. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and that "first" and "second" are not necessarily different.
[0060] References to "one embodiment" or "some embodiments" in the embodiments described in this application mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.
[0061] Furthermore, in the embodiments of this application, the words "exemplary," "for example," etc., are used to indicate that they are examples, illustrations, or descriptions. Any embodiment or design scheme described as "exemplary" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the term "exemplary" is intended to present the concept in a concrete manner.
[0062] In the embodiments of this application, the terms "information," "signal," "message," "channel," and "singaling" may sometimes be used interchangeably. It should be noted that, without emphasizing their distinction, their intended meanings are consistent. Similarly, "of," "corresponding (relevant)," and "corresponding" may sometimes be used interchangeably. It should be noted that, without emphasizing their distinction, their intended meanings are consistent. Furthermore, the " / " mentioned in this application can be used to indicate an "or" relationship.
[0063] The following detailed embodiments further illustrate the objectives, technical solutions, and beneficial effects of this application. It should be understood that the following are merely specific embodiments of this application and are not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made based on the technical solutions of this application should be included within the scope of protection of this application.
[0064] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.
[0065] The system architecture involved in the embodiments of this application is described below.
[0066] Figure 1A is a schematic diagram of the architecture of the communication system applied in the embodiments of this application. As shown in Figure 1A, the communication system 1000 includes a radio access network (RAN) 100 and a core network (CN) 200, or may also include an Internet 300. RAN 100 includes at least one RAN node (110a and 110b in Figure 1A, collectively referred to as 110) and at least one terminal (120a-120j in Figure 1A, collectively referred to as 120). RAN may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 1A). Terminal 120 is wirelessly connected to RAN node 110. RAN node 110 is wirelessly or wired connected to core network 200. The core network device in core network 200 and RAN node 110 in RAN 100 may be different physical devices, or they may be the same physical device integrating core network logical functions and radio access network logical functions.
[0067] RAN 100 can be a cellular system related to the 3rd Generation Partnership Project (3GPP), such as 4G, 5G mobile communication systems, non-terrestrial network (NTN) systems, or future-oriented evolution systems (such as 6G mobile communication systems). RAN 100 can also be an open access network (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system, or a communication system that integrates two or more of the above systems.
[0068] The terminal involved in the embodiments of this application may also be referred to as a terminal device, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. A terminal device can be a user-side entity used to receive or transmit signals, such as a mobile phone. Terminal devices can be used to connect people, objects, and machines. Terminal devices can communicate with one or more core networks through network devices. Terminal devices include handheld devices with wireless connectivity, other processing devices connected to a wireless modem, or vehicle-mounted devices. Terminal devices can be portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile devices. Terminal devices can be widely used in various scenarios, such as cellular communication, D2D, V2X, point-to-point (P2P), machine-to-machine (M2M), machine-type communication (MTC), Internet of Things (IoT), virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearables, smart transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, autonomous delivery and mobility, etc.Examples of terminal devices include: 3GPP standard user equipment (UE), fixed equipment, mobile equipment, handheld devices, wearable devices, cellular phones, smartphones, session initiated protocol (SIP) phones, laptops, personal computers, smart books, vehicles, satellites, global positioning system (GPS) devices, drones, helicopters, aircraft, ships, remote control devices, smart home devices, industrial equipment, personal communication service (PCS) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), wireless network cameras, tablets, handheld computers, mobile internet devices (MIDs), wearable devices such as smartwatches, VR devices, AR devices, wireless terminals in industrial control, terminals in vehicle-to-everything (V2X) systems, wireless terminals in self-driving vehicles, wireless terminals in smart grids, wireless terminals in transportation safety, and smart city applications. Wireless terminals in cities include smart gas pumps, high-speed rail devices, and smart homes such as smart speakers, smart coffee machines, and smart printers. Terminal devices in 5G networks or future public land mobile networks (PLMNs) also include devices in Zigbee networks, LoRa networks, Bluetooth (BT) slaves, BLE slaves, and Wi-Fi stations (STAs). Terminal devices can also be part of IoT systems, also known as IoT nodes. IoT is a crucial component of future information technology development. Its main technical characteristic is connecting objects to networks via communication technologies, thereby achieving intelligent networks that enable human-machine and machine-to-machine interconnection. Connections can be made using broadband or narrowband technologies. IoT technology, for example, can achieve massive connectivity, deep coverage, and low power consumption through narrowband (NB) technology. IoT technologies include reflective communication, spread spectrum, and ultra-wideband (UWB), which will not be elaborated further.
[0069] The terminal can be a wireless device in the various scenarios described above, or a device for setting up a wireless device, such as a communication module, modem, or chip in the aforementioned devices. The terminal device can also be a terminal device in a future wireless communication system. The terminal device can be used in dedicated network equipment or general-purpose equipment. The embodiments of this application do not limit the specific technology or device form adopted by the terminal device.
[0070] RAN node 110, sometimes also referred to as access network equipment, RAN entity, or access node, constitutes part of the communication system and is used to help terminals achieve wireless access. Multiple RAN nodes 110 in communication system 1000 can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal 120 are relative. For example, network element 120i in Figure 1A can be a helicopter or drone, which can be configured as a mobile base station. For terminals 120j accessing RAN 100 through network element 120i, network element 120i is a base station; but for base station 110a, network element 120i is a terminal. RAN node 110 and terminal 120 are sometimes both referred to as communication devices. For example, network elements 110a and 110b in Figure 1A can be understood as communication devices with base station functions, and network elements 120a-120j can be understood as communication devices with terminal functions.
[0071] In one possible scenario, a RAN node can be a base station (BS), an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB or gNodeB), a next-generation base station in a 6th-generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system. A RAN node can be a macro base station (as shown in Figure 1A, 110a), a micro base station or indoor station (as shown in Figure 1A, 110b), a relay node or donor node, or a radio controller in a CRAN scenario. Optionally, a RAN node can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU).
[0072] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, with different RAN nodes implementing some of the base station's functions. For example, a RAN node can be a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), etc. The CU and DU can be set up separately, or they can be included in the same network element, such as a baseband unit (BBU). Referring to Figure 1B, which is a schematic diagram of a protocol stack for a RAN node according to an embodiment of this application, the CU and DU nodes separate the gNB's protocol layers. Some protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU, which is centrally controlled by the CU. As one implementation, the CU deploys the Radio Resource Control (RRC) layer, PDCP layer, and Service Data Adaptation Protocol (SDAP) layer in the protocol stack; the DU deploys the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and Physical Layer (PHY) in the protocol stack. Thus, the CU has the processing capabilities for RRC, PDCP, and SDAP. The DU has the processing capabilities for RLC, MAC, and PHY. It is understood that the above functional division is merely an example and does not constitute a limitation on the CU and DU. The RU can be included in radio frequency equipment or radio frequency units, such as in a remote radio unit (RRU), active antenna unit (AAU), or remote radio head (RRH).
[0073] In some deployments, the RAN device can be an open radio access network (ORAN) architecture, etc. For example, when the RAN device is an ORAN architecture, the RAN device in this application embodiment can be an access network element in the ORAN, or a module of an access network element, etc. In the ORAN system, CU can also be called open (O)-CU, DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU.
[0074] Core network equipment refers to the equipment in the core network (CN) that provides service support to terminals. Examples of core network equipment include: access and mobility management function (AMF) entities, session management function (SMF) entities, user plane function (UPF) entities, etc., which will not be listed here. The AMF entity is responsible for terminal access management and mobility management; the SMF entity is responsible for session management, such as user session establishment; and the UPF entity can be a user plane function entity, primarily responsible for connecting to external networks. It should be noted that in this application, entities can also be referred to as network elements or functional entities. For example, an AMF entity can also be called an AMF network element or an AMF functional entity, and similarly, an SMF entity can also be called an SMF network element or an SMF functional entity.
[0075] Communication between access network devices and terminals, between access network devices, and between terminals can be conducted using licensed spectrum, unlicensed spectrum, or both simultaneously. Communication can be conducted using spectrum below 6 GHz, spectrum above 6 GHz, or both simultaneously. The embodiments of this application do not limit the spectrum resources used for wireless communication.
[0076] The aforementioned ORAN aims to achieve an intelligent and open access network. A key feature of the ORAN architecture is the separation of hardware and software, achieving network function virtualization and hardware standardization. Furthermore, ORAN incorporates artificial intelligence (AI). Referring to Figure 1C, which illustrates an ORAN architecture according to an embodiment of this application, in the ORAN system, CU can also be called O-CU (Open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.
[0077] The network elements of the ORAN system in Figure 1C are described below:
[0078] Service Management and Orchestration Framework (SMO): Its function is similar to that of a network management system.
[0079] Non-real-time (Non-RT) RAN intelligent controller (RIC): Used for non-real-time intelligent management of RAN functions. It enables artificial intelligence (AI) / machine learning (ML) workflows, including model training and updates, and guides applications / functions within the near-real-time (Near-RT) RAN intelligent controller (RIC) based on policies. The Non-RT RIC is located within the SMO module.
[0080] Near-RT RIC: Used to achieve near real-time intelligent management of the RAN. Through data collection and related operations on the E2 interface, it enables near real-time control and optimization of ORAN modules and resources.
[0081] O-RAN central unit (O-CU): Used to implement the RRC layer, packet data convergence protocol (PDCP) layer, service data adaptation protocol (SDAP) layer, and other control functions in the 3rd generation partnership project (3GPP) standard.
[0082] O-RAN Central Unit Control Plane (O-CU-CP): Similar to the CU-CP in the NR system, it is used to implement the functions of the RRC layer and the control plane functions of the PDCP layer. It is part of the O-CU.
[0083] O-RAN Central Unit User Plane (O-CU-UP): Similar to the CU-UP in the NR system, it is used to implement the functions of the SDAP layer and the user plane functions of the PDCP layer. It is part of the O-CU.
[0084] O-RAN distributed unit (O-DU): Based on low-layer function segmentation, it is used to implement the radio link control (RLC) layer, media access control (MAC) layer, and higher physical layer (Higher PHY) layer in the 3GPP standard. The higher physical layer functions include one or more of the following: forward error correction (FEC) encoding / decoding, scrambling / descrambling, or modulation / demodulation.
[0085] The O-RAN radio unit (O-RU) is based on low-layer function partitioning and is used to implement lower physical layer (PHY) functions and radio frequency (RF) functions in the 3GPP standard. These PHY functions include one or more of the following: Fast Fourier Transform (FFT) / Inverse Fast Fourier Transform (iFFT), digital beamforming, or extraction and filtering of the Physical Random Access Channel (PRACH). It is similar to the Transmission Reception Point (TRP) or Remote Radio Head (RRH) in 3GPP, but includes PHY functions such as FFT / iFFT or PRACH extraction.
[0086] O-RAN Cloud (O-Cloud): As a cloud computing platform, it includes physical infrastructure nodes for hosting O-RAN functions such as RIC and O-DU; it supports software components (such as operating systems, virtual machine monitoring, container runtimes), management and orchestration functions.
[0087] The interfaces included in Figure 1C are described as follows:
[0088] A1 Interface: The interface between Non-RT RIC and Near-RT RIC, used for intelligent and dynamic control of radio resources within the O-RAN. Non-RT RIC provides policies, rich information, and ML model updates to Near-RT RIC through the A1 interface, while Near-RT RIC provides policy feedback to Non-RT RIC through the A1 interface.
[0089] E2 Interface: The E2 interface is an open interface between two endpoints used to connect the Near-RT RIC and the RAN node. RAN nodes include, for example, CU and DU in 5G, O-RAN compatible eNB in 4G, O-CU (O-CU-CP and / or O-CU-UP) in O-RAN, and / or O-DU, etc. The RIC can obtain data collection and feedback from the RAN node through the E2 node, and the RAN node can obtain control feedback from the Near-RT RIC through the E2 node.
[0090] O1 Interface: The interface between the management entity in the SMO and the O-RAN module, used for operation management. FCAPS management, software management, and file management are achieved through this interface.
[0091] O2 Interface: The interface between the SMO and the infrastructure management framework that supports O-RAN virtual network functionality.
[0092] The O-FH CUS plane (Open Fronthaul CUS-Plane) interface includes the control plane (C-Plane), user plane (U-Plane), and synchronization plane (S-Plane) interfaces. The control plane is used for real-time control between the O-DU and O-RU, such as transmitting beamforming weights from the O-DU to the O-RU or performing power control from the O-DU to the O-RU. The user plane is used to transmit communication data between the DU and RU for access network devices and terminals. The synchronization plane is used by the O-DU to provide clock synchronization for the O-RU.
[0093] In the embodiments of this application, the functions of the access network device can be executed by modules (such as chips) within the access network device, or by a control subsystem that includes access network device functions. This control subsystem, including access network device functions, can be a control center in the aforementioned application scenarios such as smart grids, industrial control, intelligent transportation, and smart cities. Similarly, the functions of the terminal can be executed by modules (such as chips or modems) within the terminal, or by a device that includes terminal functions.
[0094] It should be understood that the number and type of each device in the communication system shown in Figure 1A are for illustrative purposes only, and this application is not limited thereto. In actual applications, the communication system may include more terminal devices, more access network devices, and other network elements, such as network elements used to implement artificial intelligence functions.
[0095] It is understandable that all or part of the functions implemented by terminal devices and access network devices can be virtualized, that is, implemented through one or more dedicated processors or general-purpose processors and corresponding software modules. Since terminal devices and access network devices involve air interface transmission, the transmit and receive functions of this interface can be implemented in hardware. Optionally, one or more functions of the virtualized terminal devices, access network devices, or network elements used to implement artificial intelligence functions can be implemented by cloud devices, such as cloud devices in over-the-top (OTT) systems.
[0096] The prior art of the embodiments of this application is described below.
[0097] 1. Non-terrestrial network (NTN)
[0098] Because traditional terrestrial networks (TN) cannot provide seamless coverage for UEs, especially in areas where base stations cannot be deployed, such as oceans, deserts, and the air, NTN has been introduced into the Internet of Things (IoT) and 5G systems, as well as subsequent system architectures such as 6G. It provides seamless coverage for UEs and improves system reliability by deploying base stations or part of their functions on non-terrestrial network devices such as high-altitude platforms or satellites. This application uses satellites as an example. According to their operating modes, satellites are generally divided into two main categories: The first is transparent relay, where the satellite relays the radio frequency signals of base stations located on the ground. The satellite's role is to filter, convert, and amplify radio frequencies, regenerating physical layer signals. The second is regenerative relay, where the satellite has all or part of the functions of a base station, meaning the base station or part of its functions are deployed on the satellite. According to satellite altitude, i.e., satellite orbital altitude, satellite systems can be divided into the following two categories:
[0099] High Earth orbit (GEO) satellites, also known as geostationary satellites, move at the same speed as the Earth's rotation system. Therefore, the satellite remains stationary relative to the ground, and correspondingly, the cell of a GEO satellite is also stationary. GEO satellite cells have relatively large coverage areas, typically with a cell diameter of 500 km.
[0100] Medium and low Earth orbit satellites: Satellites move relatively fast relative to the ground, so the service coverage area provided by medium and low Earth orbit satellites also moves accordingly.
[0101] Therefore, for low and medium Earth orbit satellites, the coverage areas provided by the satellites can be divided into two types:
[0102] Quasi-earth-fixed cell: A moving satellite forms a cell by adjusting its beam, and the cell remains stationary on the ground for a certain period of time.
[0103] Earth-moving cell: The satellite does not dynamically adjust its beam direction; the cell covered by the satellite's beam moves as the satellite moves.
[0104] TR38.821 defines four NTN-based NG-RAN architectures:
[0105] Architecture 1 (see Figure 1D): Transparent satellite architecture.
[0106] In a transparent satellite architecture scenario, the satellite's role is to perform radio frequency filtering, frequency conversion, and amplification. In other words, the satellite primarily acts as a Layer 1 relay, regenerating physical layer signals, and does not involve any higher protocol layers.
[0107] Architecture 2 (see Figure 1E): Regenerative satellite without inter-satellite link (ISL), but with base station processing capabilities (gNB processed payload).
[0108] In this architecture, satellites act as base stations.
[0109] Architecture 3 (see Figure 1F): Regenerative satellite with inter-satellite links and base station processing capabilities (regenerative satellite with ISL, gNB processed payload).
[0110] In this scenario, the satellite also functions as a base station. The difference from the previous scenario is that an ISL (Independent Stationary Link) exists in this one.
[0111] Architecture 4 (see Figure 1G): NG-RAN with a regenerative satellite based on gNB-DU.
[0112] In this scenario, the satellite is represented by DU.
[0113] 2. Random Access (RA)
[0114] 2.1 Competition-Based Four-Step RA
[0115] Referring to Figure 2A, a flowchart of a competition-based four-step RA (Rapid Algorithm) provided in an embodiment of this application is shown, which includes the following four steps:
[0116] Step 1. The UE sends the RA preamble, i.e., msg1. Specifically, the UE obtains the PRACH configuration from system information block (SIB) 1, randomly selects an RA preamble, and sends the RA preamble;
[0117] Step 2. The UE sends the RAR, i.e., msg2. The RAR includes the uplink timing advance (TA), RA preamble identifier, uplink (UL) grant, and temporary cell radio network temporary identifier (C-RNTI). After the UE sends the RA preamble, it starts the RA response window and continuously monitors the PDCCH channel within the RA sliding window until it obtains the required RA response on the PDSCH channel.
[0118] 1) If the RA response contains an RA-preamble identifier that is consistent with the RA preamble, the UE considers the RA response successful and proceeds to step 3.
[0119] 2) If the UE does not receive a response message during the RA sliding window, or if the received response verification fails, the UE assumes that the previous transmission was not correctly received by the gNB, and the RA response fails. In this case, if the UE's RA attempt count is less than the maximum attempt count, it will attempt the RA again; otherwise, the RA process fails.
[0120] Step 3. The UE sends msg3;
[0121] After step 2 is completed, the UE achieves uplink synchronization and can transmit messages (msg3) on the scheduled PUSCH. msg3 carries the UE's unique identifier (UE ID) (or UE contention resolution identity), which is used for conflict resolution in step 4 to distinguish UEs that send conflicting messages.
[0122] If the UE has previously connected to a cell, it uses the cell's C-RNTI or the cell-assigned resume ID / (or) inactive radio network temporary identifier (I-RNTI) as its identifier. This identifier is unique within the specific cell. Otherwise, the UE uses an identifier from the core network (Serving Temporary Mobile Subscriber Identity (S-TMSI) or a random number). The Resume ID / I-RNTI is a unique identifier assigned by the cell for RRC connection recovery.
[0123] Step 4. The gNB sends a contention resolution response, i.e., msg4, to the UE.
[0124] After the UE sends msg3, it starts a contention resolution timer and then monitors the PDCCH within the timer window. Specifically, for TN networks, the UE starts or restarts the contention resolution timer within the first symbol after the end of msg3 transmission. For NTN networks, the UE starts or restarts the contention resolution timer within the first symbol after the end of msg3 transmission and the round trip time (RTT) between the UE and gNB. The RTT between the UE and gNB is the sum of the UE's timing advance and Kmac (an offset configured on the network side, approximating the round trip delay between the uplink time synchronization reference point and the RAN). The gNB assists the UE in contention resolution by scrambling msg4 on the PDCCH with C-RNTI or TC-RNTI, or by using the UE contention resolution identity on the PDSCH.
[0125] a) Before the contention resolution timer expires, the UE continuously monitors the PDCCH channel. If any of the following conditions exist, the UE obtains a matching contention resolution response indication, considers the contention resolution successful (i.e., the UE successfully accesses the network), and stops the contention resolution timer; otherwise, the timer is not stopped.
[0126] i. The UE detects msg4 scrambled with C-RNTI / Resume ID / I-RNTI on the PDCCH. At this time, the UE will stop the contention resolution timer and discard the Temporary C-RNTI.
[0127] ii. The UE detects msg4 scrambled with Temporary C-RNTI on the PDCCH, and the UE contention resolution identity contained in the medium access control protocol data unit (MAC PDU) received by the UE from the PDSCH is the same as the UE contention resolution identity carried in msg3 sent by the UE (i.e., MAC PDU decoding is successful). At this time, the UE will stop the contention resolution timer and set the temporary C-RNTI to C-RNTI.
[0128] b) If the contention resolution timer expires, the UE will discard the temporary C-RNTI and consider the contention resolution to have failed.
[0129] If the RA attempt fails after the contention resolution fails, and the number of RA attempts by the UE is less than the maximum number of attempts, the RA attempt will be repeated; otherwise, the RA process will fail.
[0130] Here, gNB (gNodeB) is just one form of RAN; it can also be other forms of network devices such as eNB. The same applies to the eNB in this embodiment.
[0131] 2.2 Two-Step RA Based on Competition
[0132] Referring to Figure 2B, a flowchart of a contention-based two-step RA provided in this embodiment of the application is shown. The two-step RA includes two parts: msgA transmission and msgB reception. The UE transmits msgA, which includes the RA preamble on PRACH and the payload on PUSCH. After msgA transmission, the UE starts a contention resolution timer to monitor msgB. msgB is the response to msgA. One msgB can include responses to msgA transmitted by multiple UEs. msgB can include one or more of the following: contention resolution response (successRAR), fallback response (fallbackRAR), and backoff indicator. Figure 2B shows the contention resolution case. For the case where a fallback indicator is received, referring to Figure 2C, another flowchart of a contention-based two-step RA provided in this embodiment of the application is shown. The UE falls back to transmit a message (msg3) on a predetermined PUSCH and then receives the contention resolution message (msg4) sent by the gNB.
[0133] The MAC PDU of msgB can be composed of one or more MAC subPDUs. Referring to Figure 2D, which is a schematic diagram of the components of a MAC PDU provided in an embodiment of this application, each MAC subPDU can be one of the following:
[0134] (1). MAC sub-PDU with backoff indication, including MAC subheader with backoff indication (not shown in the figure).
[0135] (2). The MAC sub-PDU of the fallback indication (also known as the MAC sub-PDU of the fallback response) includes the MAC sub-header and the fallback response (as shown in (a) and (b) in Figure 2D).
[0136] (3). The MAC sub-PDU of the race resolution response, including the MAC sub-header and the race resolution response (as shown in (a) and (b) in Figure 2D).
[0137] (4). The MAC sub-PDU of the data payload includes the MAC sub-header and the MAC service data unit (SDU) (as shown in Figure 2D(a)).
[0138] (5). The MAC sub-PDU is filled with MAC sub-header and padding (as shown in Figure 2D(a)).
[0139] Referring to Figure 2E, which is a schematic diagram of the MAC sub-header (also known as the MAC sub-header of the fallback indication) of a fallback response (fallbackRAR) provided in an embodiment of this application, the MAC sub-header includes a preamble ID (RAPID), meaning that each fallback response (fallbackRAR) is associated with a preamble ID. Figure 2F is a schematic diagram of the MAC sub-PDU of a fallback response provided in an embodiment of this application, which includes a UL grant (uplink grant). The uplink grant refers to uplink resource allocation information, specifically one or more of the following: resource location, resource size, modulation and coding scheme (MCS), and transmission power. In other words, it instructs the UE transmitting the preamble ID associated with the fallback response to use the UL grant included in the fallback response to perform msg3 transmission.
[0140] MAC sub-PDUs that include backoff instructions and MAC sub-PDUs that include race resolution responses do not need to be associated with a preamble ID.
[0141] 3. EDT
[0142] EDT can be divided into Mobile Originated Early Data Transmission (MO-EDT) and Mobile Terminated Early Data Transmission (MT-EDT). A key characteristic of EDT is that the UE does not need to transition to RRC connected state for data transmission. MO-EDT is used for a single uplink data transmission and an optional single downlink data transmission during the RA procedure. MO-EDT is triggered when the following conditions are met: 1) the upper layer or higher layer has requested the establishment or restoration of an RRC connection for mobile-initiated data transmission; 2) the uplink data size is less than or equal to the TB size indicated in the system message. MT-EDT is used for a single downlink data transmission during the random access procedure. If both the UE and the network support MT-EDT, and the UE has a single downlink data transmission, then MT-EDT is initiated by the core network (Mobile Management Entity (MME) or AMF).
[0143] EDT is divided into control plane EDT and user plane EDT. The common process for both is as follows: When a UE initiates an EDT, it first sends msg1, which includes the random access preamble for the EDT. It then receives msg2 from the network side, which includes the RAR (Random Access Registry). Based on the RAR, the UE sends msg3, which includes user data and the UE ID. If no further data is available, the network side sends msg4 to indicate that the UE is in RRC (Remote Access Control) idle state.
[0144] 4. SA mechanism and DSA mechanism
[0145] The ALOHA protocol is a classic protocol. Its core idea is that data can be sent as long as it's available, regardless of the receiver's state; however, this makes it highly prone to collisions. The SA protocol divides time into equal-length time slices called slots, stipulating that a terminal must wait until the start of a slot before sending data. If a data packet collides during transmission (i.e., two or more data packets are received simultaneously), the terminal randomly backs off for a period before retransmitting. By restricting the transmission time of data packets, the ALOHA protocol's arbitrary data transmission is altered, reducing the probability of data packet collisions. Referring to Figure 3A, which illustrates a transmission process based on the SA protocol according to an embodiment of this application, as shown in Figure 3A, data packets from terminal 1 and terminal 2 collide in slot 3, and both need to retransmit after a certain period.
[0146] Subsequently, DSA was proposed. Under this mechanism, the terminal randomly selects multiple time slots to send multiple copies of its own data packets. Compared with the SA mechanism, this mechanism introduces diversity, that is, each terminal can send multiple copies of its data packets. If any copy of the data packets is located in a time slot without interference from other data packets, the terminal considers the data packet to have been successfully transmitted. Refer to Figure 3B, which is a schematic diagram of a transmission process based on the DAS protocol provided by an embodiment of this application. As shown in Figure 3B, each of the three terminals (terminal 1, terminal 2, and terminal M) sends two copies (A and B) of its own data packets. Data packet copy A of terminal 1 and terminal 2 collide in time slot 3, but data packet copy B of terminal 1 and terminal 2 can be successfully decoded in their respective time slots. Therefore, the data packets of terminal 1 and terminal 2 are considered to have been successfully transmitted.
[0147] The current discussion on enhanced EDT, also known as two-step EDT or contention-based msg3 for early data transmission (CB-msg3-EDT), involves only msg3 and msg4 being transmitted in a single data transfer. To improve the efficiency of msg3 contention resolution, an SA mechanism is introduced to support the transmission of a single msg3, and a DSA mechanism is introduced to support the transmission of multiple msg3 replicas (i.e., two or more msg3s). Referring to Figure 3C, which is a flowchart of a CB-msg3-EDT using the DSA mechanism provided in an embodiment of this application, the network side configures a msg3 transmission window. Within the selected msg3 transmission window, the UE randomly selects N PUSCH resources (PUSCH occasions) in the time domain to send N copies of msg3. The UE starts a msg4 monitoring window to receive msg4. The RNTI used for scrambling msg4 transmission (also known as the RNTI used for monitoring msg4) can be derived based on the transmission resources of the Msg3 transmission window, or it can be the resume ID / I-RNTI / C-RNTI; this scheme does not impose any restrictions. The principle of the msg4 monitoring window is the same as the contention resolution timer of the four-step RA based on contention. The principle of determining the contention resolution upon receiving msg4 is the same as the contention resolution of the four-step RA based on contention. If the UE does not receive a msg4 containing a matching contention resolution ID before the msg4 monitoring window times out, then the contention resolution fails. If contention resolution fails, and the UE's msg3 attempt count is less than the maximum, a new msg3 attempt (also known as msg3 retransmission) is made. Otherwise, the CB-msg3-EDT procedure fails (CB-msg3-EDT contention resolution fails), and the UE initiates an EDT procedure based on 4-step random access to send data. An attempt to transmit at least one msg3 within a single msg3 transmission window is simply referred to as a single msg3 attempt. msg4 can include feedback information (response information) to multiple UEs; that is, multiple UEs share a single msg4 message. A single msg4 can contain a backoff message and at least one contention resolution success response for each UE. The contention resolution success response can include the UE's contention resolution ID and C-RNTI.
[0148] The network side sends CB-msg3-EDT configuration information to the UE via system messages. The CB-msg3-EDT configuration information is associated with the coverage enhancement (CE) level. Multiple coverage enhancement levels are equivalent to multiple reference signal received power (RSRP) segment intervals. This means that the network sends the UE the following information for each coverage level: [number of msg3 transmission windows, number of PUSCH time and frequency resources, msg4 monitoring window, and number of msg3 attempts].
[0149] In summary, in the existing technology, a UE attempting msg3 for the same msg3 transmission window can respond to multiple UEs in a single msg4. When the network side responds to information sent by one or more UEs on multiple PUSCH resources, how can the UE determine that the response is the response corresponding to itself?
[0150] Based on this, this application provides a communication method. Referring to Figure 4, which is a flowchart of a communication method provided by this application, the method includes the following steps:
[0151] 201. The network device sends configuration information, wherein the configuration information indicates M PUSCH resources, where M is a positive integer. Correspondingly, the terminal device receives the configuration information.
[0152] The network device in this application embodiment can be a network device, or a module within a network device (such as a chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of a network device. The terminal device can be a terminal device, or a module within a terminal device, or a logical node, logical module, or software capable of implementing all or part of the functions of a terminal device. There are no limitations on this.
[0153] In the following description, network device refers to network device and terminal device refers to terminal device.
[0154] The network device sends configuration information to configure M PUSCH resource information for the terminal device. This configuration information can be CB-msg3-EDT configuration information. Furthermore, the time-domain resources of a PUSCH resource can be identified by its time-domain resource number, and the frequency-domain resources can be identified by their frequency-domain resource number. In other words, each PUSCH resource information can also include both its time-domain resource number and its frequency-domain resource number.
[0155] 202. The terminal device sends N first messages; wherein, the first messages are used to send user data based on a contention-based resolution method, and the N uplink resources used to transmit the N first messages are selected from M PUSCH resources, where N is a positive integer less than or equal to M; correspondingly, the network device receives the first messages.
[0156] The terminal device selects N PUSCH resources from the M PUSCH resources configured in the network device to send N first messages. The first messages are used to send user data based on a contention-based resolution method. This contention-based resolution method can be either the terminal device detecting a msg4 scrambled with C-RNTI / Resume ID / I-RNTI on the PDCCH, or detecting a msg4 scrambled with this RNTI based on the RNTI derived from the transmission resources of the Msg3 transmission window. msg4 includes the terminal device's contention-based resolution identifier; this scheme does not impose any restrictions. When the configuration information is CB-msg3-EDT, this step can also be called initiating CB-msg3-EDT. During this process, the terminal device determines the number of msg3 messages N, selects the msg3 transmission window, selects N PUSCH resources for sending N msg3 messages, and starts the msg4 monitoring window.
[0157] The first message is sent on N PUSCH resources, i.e., N msg3s are sent. Then the terminal device monitors msg4 in the msg4 monitoring window.
[0158] 203. The network device sends second information, the second information including at least one indication, wherein the first indication of the at least one indication includes i-th PUSCH resource information, and the i-th PUSCH resource information is used to send one of the N first information messages. Correspondingly, the terminal device receives the second information.
[0159] A network device can receive a first message sent by one or more terminal devices. Each terminal device can select from M PUSCH resources to send its first message. After receiving the first message, the network device can send a second message as a response to the first message. That is, the second message is msg4. If the network device receives the first message and decodes msg3, it can send a contention resolution response as msg4.
[0160] After receiving the second information, the terminal device can determine whether it is a terminal device matched by at least one indication. If the terminal device sent the first information on the i-th PUSCH resource, then the terminal device is a terminal device matched by the first indication in at least one indication.
[0161] As can be seen in this embodiment, the network device sends second information to indicate the PUSCH resource information used for the transmission of the first information. After receiving the second information, the terminal device determines itself as the terminal device matching the indication based on the PUSCH resource information, and then executes subsequent steps. This process enables the network device to communicate with one or more terminal devices corresponding to the PUSCH resource information through a single indication of PUSCH resource information, improving communication efficiency and ensuring communication reliability.
[0162] In some cases, since multiple terminal devices can send the first information on M PUSCH resources, if different terminal devices send the first information on the same PUSCH resource, a collision (conflict) occurs on the network device side, and the network device cannot decode msg3 on that PUSCH resource. The network device can then send a second message, which includes at least one indication. Each of the at least one indication includes PUSCH resource information to indicate the PUSCH resource information where the collision occurred. The PUSCH resource information can be the time-domain resource number and the frequency-domain resource number of the PUSCH resource. For example, if the network device detects a collision on T different PUSCH resources, the at least one indication in the second message includes T indications, each of which indicates each of the T PUSCH resource information where the collision occurred. Further, the time-domain resource number and the frequency-domain resource number of the T PUSCH resources can be indicated. T is an integer less than or equal to N and greater than 0.
[0163] For example, if both terminal 1 and terminal 2 send the first information on the i-th PUSCH resource, then the first instruction in at least one instruction includes the i-th PUSCH resource information.
[0164] In one possible implementation, each of the at least one indication is used to instruct the terminal device to retransmit the first information. In this case, each of the at least one indication is used to instruct the retransmission of the first information. The first indication in the at least one indication is used to instruct at least one terminal device that sent the first message on the i-th PUSCH resource to retransmit the first message. For example, the at least one indication of the second information also includes a second indication, which is used to instruct the k-th PUSCH resource information where the collision occurred. For example, the at least one indication of the second information also includes a third indication, which is used to instruct the m-th PUSCH resource information where the collision occurred. Where the i-th PUSCH resource, the k-th PUSCH resource, and the m-th PUSCH resource are one of the M PUSCH resources. The at least one indication used to instruct the retransmission of the first information includes the following two methods: (1) Instructing only the PUSCH resource information where the collision occurred. If the terminal device matches the indication, it is determined that the first information needs to be retransmitted. That is, implicit indication. (2) Instructing the PUSCH resource information where the collision occurred. And instructing "retransmit". That is, explicit indication. (3) Sending at least one indication to the terminal device using the MAC subPDU or DCI of the retransmission indication. For example, since the MAC subPDU or DCI for this retransmission indication is dedicated to retransmission, it implicitly indicates retransmission. This is similar to the principle that the MAC subPDU for backoff indication is used to indicate backoff, the MAC subPDU for fallback indication is used to indicate fallback, and the MAC subPDU for contention resolution response is used to indicate contention resolution response. This scheme does not limit the specific examples of the MAC subPDU or DCI for retransmission indication.
[0165] In other words, in this embodiment, the network device sends a second message indicating the PUSCH resource information used by the first information transmission that was not correctly received (successfully decoded), and instructs the matching terminal device to retransmit the first information. The terminal device determines that it matches the instruction based on the PUSCH resource information, and thus determines the first information it needs to retransmit. This process enables the terminal device to quickly determine the first information it needs to retransmit, improving the processing efficiency and accuracy of the terminal device.
[0166] The current standard discusses a PUSCH transmission scheme using orthogonal cover codes (OCC). Multiple (e.g., 2 or 4) terminal devices transmit their uplink data using different OCCs on the same frequency and time domain resources. OCC improves the distinguishability of data from different UEs, thereby increasing network uplink capacity. This leads to a discussion of the possibility of supporting OCC-based CB-msg3-EDT, where msg3 transmission uses OCC to send data to the network device. The network device needs to know whether the terminal device is using OCC to determine whether to use the OCC mechanism to parse msg3. Since some terminal devices may not support OCC, the network device configures separate CB-msg3-EDT configuration information for OCC-based and non-OCC-based CB-msg3-EDT, allowing terminal devices that support and do not support OCC to initiate the CB-msg3-EDT process. When a network device configures resources for CB-msg3-EDT based on OCC and non-OCC via system messages, when instructing the UE to retransmit msg3, if it supports backoff between CB-msg3-EDT based on OCC / non-OCC and EDT based on four-step RA, or backoff between non-OCC and OCC, the backoff method can be divided into two types:
[0167] a) Terminal device-triggered rollback, i.e., the terminal device automatically rolls back after trying the configured number of times;
[0168] b) The network device instructs the terminal device to fall back via fallback RAR (fallback MAC CE).
[0169] Based on the above description, if the network device fails to decode the first message (msg3) sent by the terminal device, in addition to indicating the PUSCH resource information corresponding to the first message, it can also indicate the method of retransmitting the first message.
[0170] In one possible implementation, each of the at least one indication sent by the network device is used to indicate at least one of the following:
[0171] The first information is retransmitted using an orthogonal coverage code (OCC) method.
[0172] Retransmit the first information using a non-OCC-based method; or
[0173] User data is sent using a random access method.
[0174] In this case, each of the at least one indication is used to indicate the retransmission method of the first information. For example, the first indication in the at least one indication is used to instruct at least one terminal device that sent the first message on the i-th PUSCH resource to retransmit the first information using OCC (Optical Code Correction), and the second indication in the at least one indication is used to instruct at least one terminal device that sent the first message on the j-th PUSCH resource to retransmit the first information using a non-OCC method, or to send user data using random access. If the terminal device sent the first information on the j-th PUSCH resource, then the terminal device is the terminal device matched by the second indication in the at least one indication. The j-th PUSCH resource is one of M PUSCH resources, and j can be the same as or different from i / k / m mentioned above.
[0175] Furthermore, the terminal device can obtain a contention resolution response indication through the second information. In one possible implementation, if a matching contention resolution response indication can be obtained (the determination method for a matching contention resolution response indication is as described above), at least one indication can be ignored, or the retransmission of the first message can be cancelled, or data transmission based on random access can be cancelled. If a matching contention resolution response indication cannot be obtained, then the retransmission of the first message or the transmission of user data based on random access is performed based on the first indication and / or the second indication. In another possible implementation, the terminal device first processes the MAC PDU for contention resolution. If it finds one that matches the terminal device, it no longer processes the MAC PDU corresponding to the at least one indication. The MAC PDU corresponding to the at least one indication can be a MAC PDU including a fallback response, a MAC PDU for retransmission of the first information, or a MAC PDU for the retransmission method of the first information.
[0176] As can be seen, in this embodiment, the network device sends second information to indicate the PUSCH resource information used by the incorrectly received first information transmission and to instruct the matching terminal device on how to retransmit the first information. After receiving the second information, the terminal device determines that it matches the indication based on the PUSCH resource information, and then determines its own method for retransmitting the first information. This process ensures the accuracy of the indication information obtained by the terminal device from the network device, and also ensures that the terminal device retransmits the first information according to the retransmission method indicated by the network device, thus improving the efficiency and reliability of the communication process.
[0177] Furthermore, if the terminal device receives a contention resolution response indication by receiving the second information, it may not need to retransmit the first information, or it may process the contention resolution response indication first and then determine whether to retransmit the first information. This avoids unnecessary retransmission operations and reduces resource consumption during communication.
[0178] For details, please refer to Figure 5A, which is a flowchart of another communication method provided by an embodiment of this application. As shown in Figure 5A, the method includes the following steps:
[0179] 301. The network device sends configuration information, wherein the configuration information indicates M PUSCH resources, where M is a positive integer. Correspondingly, the terminal device receives the configuration information.
[0180] 302. The terminal device sends N first messages; wherein the first messages are used to send user data based on a contention-based resolution method, and the N uplink resources used to transmit the N first messages are selected from M PUSCH resources, where N is a positive integer less than or equal to M; correspondingly, the network device receives the first messages.
[0181] The descriptions of steps 301 and 302 can be found in the descriptions of steps 201 and 202 above, and will not be repeated here.
[0182] 303. The network device sends second information, the second information including at least one retransmission instruction, wherein the first instruction in the at least one retransmission instruction includes i-th PUSCH resource information, used to instruct at least one terminal device to retransmit the first information using the i-th PUSCH resource, and the i-th PUSCH resource information is used to send one of N pieces of first information. Correspondingly, the terminal device receives the second information.
[0183] In this embodiment, after receiving first information from one or more terminal devices, the network device determines that it cannot decode msg3 on the T PUSCH resources. The network device can then send second information, which includes at least one retransmission instruction to instruct the terminal devices that sent the first information using the T PUSCH resources to retransmit their own first information. For example, the first instruction in the at least one retransmission instruction is used to instruct at least one terminal device that sent the first information using the i-th PUSCH resource to retransmit the first information.
[0184] After receiving the second information, the terminal device can determine whether it sent the first information on the i-th PUSCH resource. If so, it determines that the first information sent on the i-th PUSCH resource was not correctly received by the network device and needs to be retransmitted.
[0185] Optionally, the second information is sent via at least one Media Access Control Layer Sub-Protocol Data Unit (MAC subPDU) or via Downlink Control Information (DCI), with at least one MAC subPDU used to determine the contention resolution status.
[0186] For example, suppose the second information includes T retransmission indications, used to instruct the terminal device that sent the first information on T PUSCH resources to retransmit the first message. These T retransmission indications are respectively carried in T MAC subPDUs of the MAC PDU. These MAC subPDUs can be newly added MAC subPDUs, such as a MAC subPDU called a retransmission response. Alternatively, existing fallback response MAC subPDUs can be reused. Referring to Figure 5B, which is a schematic diagram of the indication of PUSCH resource information provided in this embodiment, as shown in Figure 5B(a), the PUSCH resource information (such as the PUSCH ID) can specifically be located in the MAC subheader of the MAC subPDU of the retransmission response. Or, as shown in Figure 5B(b), it can be located in the MAC subheader of the MAC subPDU of the fallback response, replacing the original RAPID.
[0187] Alternatively, the second information can also be sent via DCI. The terminal device monitors the RNTI of the DCI by referring to the RNTI description of msg4, that is, it monitors the DCI scrambled with C-RNTI / Resume ID / I-RNTI, identifies it as its own DCI, obtains the information therein, and then obtains at least one retransmission indication corresponding to the second information.
[0188] Optionally, the second information also includes at least one contention resolution response indication, wherein the first contention resolution response indication of the at least one contention resolution response indication is one or more corresponding responses of the N first information, and the method further includes: ignoring the first indication or canceling the retransmission of the first information; or processing at least one contention resolution response indication, and stopping the processing of other MAC subPDUs after processing the first contention resolution response indication.
[0189] For example, since the terminal device sends N copies of msg3 on N PUSCH resources, some of these msg3 copies may be decoded by the network device. Therefore, the second information received by the terminal device may include at least one contention resolution response indication, where the first contention resolution response indication is one or more corresponding responses to the N first messages. For instance, receiving NT contention resolution response indications represents responses corresponding to the first messages on NT PUSCHs.
[0190] After receiving at least one contention resolution response indication, the terminal device knows that some of the N msg3 copies it sent have been successfully received by the network device. It can then ignore at least one indication in the second message, or (if the first message has already been retransmitted based on at least one indication) cancel the retransmission of the first message. Alternatively, the terminal device first processes the received at least one contention resolution response indication and determines that it includes the contention resolution ID and C-RNTI corresponding to the terminal device. If this is confirmed, the terminal device has successfully matched the contention resolution response, and the terminal device can then stop processing other MAC sub-PDUs.
[0191] As can be seen, in this embodiment, the network device sends second information to indicate the PUSCH resource information used in the incorrectly received first information transmission, and instructs the matching terminal device to retransmit the first information. The terminal device determines that it matches the indication based on the PUSCH resource information, and thus determines that it needs to retransmit the first information. This process enables the terminal device to quickly determine whether it needs to retransmit the first information, improving the processing efficiency and accuracy of the terminal device.
[0192] This method also provides a way to send the second information. By combining the existing MAC PDU structure to send the second information, it can help ensure the efficiency of network devices in sending the second information and reduce time overhead.
[0193] Furthermore, if the terminal device receives a contention resolution response indication by receiving the second information, it may not need to retransmit the first information, or it may process the contention resolution response indication first and then determine whether to retransmit the first information. This avoids unnecessary retransmission operations and reduces resource consumption during communication. Referring to Figure 6A, which is a flowchart of another communication method provided in an embodiment of this application, the method includes the following steps:
[0194] 401. The network device sends configuration information, wherein the configuration information indicates M PUSCH resources, where M is a positive integer. Correspondingly, the terminal device receives the configuration information.
[0195] The configuration information sent by the network device can be CB-msg3-EDT configuration information. The PUSCH resource type configured in the CB-msg3-EDT configuration information can be an OCC-based PUSCH resource, a non-OCC-based PUSCH resource, or it can configure both OCC-based and non-OCC-based PUSCH resources for the terminal device. The configuration information sent by the network device can also include RA-based EDT configuration information.
[0196] 402. The terminal device sends N first messages; wherein, the first messages are used to send user data based on a contention-based resolution method, and the N uplink resources used to transmit the N first messages are selected from M PUSCH resources, where N is a positive integer less than or equal to M; correspondingly, the network device receives the first messages.
[0197] For a detailed description of this step, please refer to step 202 above, which will not be repeated here.
[0198] 403. The network device sends second information, the second information including at least one indication, each indication of the at least one indication being used to indicate a method for retransmitting the first information, wherein the method for retransmitting the first information is at least one of the following: retransmitting the first information using an orthogonal coverage code (OCC) method; retransmitting the first information using a non-OCC method; or sending user data using a random access method.
[0199] After a terminal device sends the first message, the network device may receive it. Alternatively, if multiple terminal devices send the first message on the same PUSCH resource, the network device may fail to receive it. Therefore, the network device instructs the terminal devices to retransmit the first message by sending a second message, specifying the method for retransmitting the first message.
[0200] The methods for retransmitting the first information include one or more of the following:
[0201] (1) The first information is retransmitted using an OCC-based method.
[0202] For example, at least one of the instructions is used to instruct the first information to be retransmitted in an OCC-based manner, that is, the terminal device retransmits the first information using an OCC-based manner. Further, the uplink authorization included in the first instruction is used to retransmit the first information in an OCC-based manner.
[0203] (2) Retransmit the first information using a non-OCC-based method.
[0204] For example, at least one of the instructions is used to instruct the first information to be retransmitted in a non-OCC-based manner, that is, the terminal device retransmits the first information in a non-OCC-based manner. Further, the uplink authorization included in the second instruction is used to retransmit the first information in a non-OCC-based manner.
[0205] (3) User data is sent using a random access method.
[0206] In other cases, if the network device cannot correctly receive the first message sent by the terminal device, it can instruct the terminal device to send user data using a RA-based method. That is, the terminal device will not retransmit the first message and will fall back from a two-step EDT (2-step EDT / contention-based msg3 EDT) to a four-step RA-based EDT to send user data. The four-step RA-based EDT can also be extended to a four-step random access method to enter the RRC connection state; this scheme does not impose such limitations.
[0207] After receiving the second information, the terminal device can retransmit the first information in the corresponding OCC / non-OCC manner, or send user data in the RA manner.
[0208] As can be seen, in this embodiment of the application, the network device sends a second message to instruct the terminal device to retransmit the first message. This enables the terminal device that receives the second message to retransmit the first message in the corresponding manner when it needs to retransmit the first message. This process can avoid the situation where the first message sent by the terminal device cannot be correctly received by the network device due to the mismatch of the retransmission method, thereby improving the efficiency and reliability of the communication process.
[0209] Optionally, at least one indication in the second information may also be used to indicate at least one PUSCH resource information.
[0210] For example, the second information includes T indications for T PUSCH resource information. The terminal device determines whether it matches the indications (see the description of the foregoing embodiments for the specific matching method). If it matches, the terminal device determines that the first information it sent on that PUSCH resource needs to be retransmitted. At least one of the indications includes the j-th PUSCH resource information, indicating that the first information transmitted on the j-th PUSCH resource information was not correctly received by the network device and needs to be retransmitted. The second indication also indicates that the first information should be retransmitted using an OCC-based method, so the terminal device retransmits the first information sent on the j-th PUSCH resource using an OCC-based method.
[0211] The retransmission methods corresponding to the first information transmitted on the T PUSCH resource information indicated by the T instructions can be the same or different, and there is no limitation on this.
[0212] As can be seen, in this embodiment, the network device sends a second message indicating the PUSCH resource information used in the transmission of the first message that was not correctly received (successfully decoded), and simultaneously instructs the matching terminal device on the method for retransmitting the first message. The terminal device determines its match with the second message based on the PUSCH resource information, and then determines its corresponding retransmission method. This process enables the terminal device to know that the first message it sent using the corresponding PUSCH resource was not correctly received, thus requiring retransmission, and further, to know the appropriate retransmission method. This process ensures the accuracy of the instruction information obtained by the terminal device from the network device, and avoids situations where the first message sent by the terminal device cannot be decoded by the network device due to a mismatch in retransmission methods, thereby improving the efficiency and reliability of the communication process.
[0213] Optionally, at least one indication includes the Media Access Control Layer Subprotocol Data Unit (MAC subPDU) corresponding to the fallback response.
[0214] Optionally, the fallback response or the MAC subheader of the fallback response includes 1 bit of information to indicate whether the first information is retransmitted using an OCC-based method or a non-OCC-based method; the fallback response does not include uplink grant information to indicate whether user data is sent using a random access method.
[0215] The method of retransmitting the first information indicated by the network device can be included in the MAC sub-PDU corresponding to the fallback response. Specifically, refer to Figure 6B, which is a schematic diagram of the method of indicating the retransmission of the first information provided in the embodiment of this application. As shown in Figure 6B(a), the MAC sub-PDU corresponding to the fallback response includes a type identifier (TI) or reserved (R) field. This field can include 1 bit of information to indicate whether the method of retransmitting the first information is OCC or non-OCC, as shown in Figure 6B(a).
[0216] In addition, the MAC subPDU corresponding to the fallback response also includes a UL grant, which is used by the terminal device to select the first retransmission information. The network device can set the UL grant of the MAC subPDU corresponding to the fallback response to be missing, which is used to indicate that user data is sent using the RA-based method. That is, this response field is an empty field, as shown in Figure 6B(b).
[0217] Alternatively, the network device may send the second information (including the method of indicating the retransmission of the first information) in other MAC sub-PDUs or DCIs, which is not limited in this embodiment.
[0218] This embodiment sets 1 bit in the MAC subheader of the existing fallback response to indicate whether the retransmission of the first information is OCC or non-OCC, reducing the complexity of modifying data units. Furthermore, determining whether to use the RA-based method to send user data by checking for the presence of uplink grant information further reduces the complexity of the network device sending indication information, thereby reducing communication time costs.
[0219] Please refer to Figure 7, which is a schematic diagram of a communication device provided in an embodiment of this application. This communication device can be used to execute any of the methods in the foregoing embodiments.
[0220] As shown in Figure 7, the communication device includes a processing module 901 and a transceiver module 902. The processing module 901 may be one or more processors, and the transceiver module 902 may be a transceiver or a communication interface. This communication device can be used to implement the functions of devices such as the first communication device and the second communication device involved in any of the above method embodiments. These devices may be hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (e.g., a cloud platform). Optionally, the communication device may also include a storage module 903 for storing the program code and data of the communication device.
[0221] In a first example, the communication device can function as a terminal device in the embodiments of Figures 4 to 6B, and execute the steps performed by the terminal device in the above method embodiments. The transceiver module 902 supports communication with the network device. The processing module 901 can be used to support the execution of actions performed by the terminal device in the above method embodiments, excluding sending and receiving.
[0222] Specifically, the transceiver module 902 receives configuration information; wherein the configuration information is used to indicate M PUSCH resources, where M is a positive integer; the transceiver module 902 is also used to send N first messages; wherein the first messages are used to send user data based on a contention-based resolution method, and the N uplink resources used to transmit the N first messages are selected from the M PUSCH resources, where N is a positive integer less than or equal to M; the transceiver module 902 is also used to receive second information, the second information including at least one indication, wherein the first indication in the at least one indication includes information about the i-th PUSCH resource, and the i-th PUSCH resource information is used to send one of the N first messages.
[0223] In one feasible implementation, each of the at least one indication is used to indicate the retransmission of the first information, and the first indication is used to indicate at least one terminal device that sent the first information using the i-th PUSCH resource information to retransmit the first information.
[0224] In one feasible implementation, the second information is sent via at least one Media Access Control Layer Sub-Protocol Data Unit (MAC subPDU) or via Downlink Control Information (DCI), with at least one MAC subPDU used to determine the contention resolution status.
[0225] In one feasible implementation, each of the at least one indications is a MAC subPDU corresponding to the fallback response, and the i-th PUSCH resource information is included in the fallback response or the MAC subheader of the fallback response.
[0226] In one feasible implementation, the second information further includes at least one contention resolution response indication, wherein the first contention resolution response indication of the at least one contention resolution response indication is one or more corresponding responses of the N first information, and the processing module 901 is used to: ignore the first indication or cancel the retransmission of the first information; or process at least one contention resolution response indication, and stop processing other MAC subPDUs after processing the first contention resolution response indication.
[0227] In one feasible implementation, the second instruction in at least one instruction is used to indicate at least one of the following: retransmitting the first information in a manner based on orthogonal coverage code (OCC); retransmitting the first information in a manner based on non-OCC; or sending user data in a manner based on random access.
[0228] In one feasible implementation, the second instruction includes j-th PUSCH resource information, which is used to send one of the N first messages.
[0229] In one feasible implementation, the fallback response or the MAC subheader of the fallback response includes 1 bit of information to indicate whether the first information is retransmitted using an OCC-based method or a non-OCC-based method; the fallback response does not include uplink grant information to indicate whether user data is sent using a random access method.
[0230] In a second example, the communication device can function as a network device in the embodiments of Figures 4 to 6B, and execute the steps performed by the network device in the above method embodiments. The transceiver module 902 supports communication with the terminal device. The processing module 901 can be used to support the execution of actions other than sending and receiving performed by the network device in the above method embodiments.
[0231] Specifically, the transceiver module 902 is used to send configuration information; wherein the configuration information is used to indicate M PUSCH resources, where M is a positive integer; the transceiver module 902 is also used to receive first information; wherein the first information is user data sent based on a contention-based resolution method, and the N uplink resources used to transmit the first information are selected from the M PUSCH resources, where N is a positive integer less than or equal to M; the transceiver module 902 is also used to send second information, the second information including at least one indication, wherein the first indication in the at least one indication includes information about the i-th PUSCH resource, and the i-th PUSCH resource information is used to send one of the N pieces of first information.
[0232] In one feasible implementation, each of the at least one indication is used to indicate the retransmission of the first information, and the first indication is used to indicate at least one terminal device that sent the first information using the i-th PUSCH resource information to retransmit the first information.
[0233] In one feasible implementation, the second information is sent via at least one Media Access Control Layer Sub-Protocol Data Unit (MAC subPDU) or via Downlink Control Information (DCI), with at least one MAC subPDU used to determine the contention resolution status.
[0234] In one feasible implementation, each of the at least one indications is a MAC subPDU corresponding to the fallback response, and the i-th PUSCH resource information is included in the fallback response or the MAC subheader of the fallback response.
[0235] In one feasible implementation, the second information further includes at least one contention resolution response indication, wherein the first contention resolution response indication of the at least one contention resolution response indication is one or more corresponding responses of the N first information.
[0236] In one feasible implementation, the second indication of at least one indication is also used to indicate at least one of the following: retransmitting the first information in a manner based on orthogonal coverage code (OCC); retransmitting the first information in a manner based on non-OCC; or sending user data in a manner based on random access.
[0237] In one feasible implementation, the second instruction includes j-th PUSCH resource information, which is used to send one of the N first messages.
[0238] In one feasible implementation, the fallback response or the MAC subheader of the fallback response includes 1 bit of information to indicate whether the first information is retransmitted using an OCC-based method or a non-OCC-based method; the fallback response does not include uplink grant information to indicate whether user data is sent using a random access method.
[0239] Please refer to Figure 8, which is a simplified structural diagram of a network device provided in an embodiment of this application, and can be used as an implementation of the network device of this application.
[0240] The network device includes a radio frequency (RF) signal transceiver and conversion section and a baseband section 42. The RF signal transceiver and conversion section further includes a receiving module 41 and a transmitting module 43 (which can also be collectively referred to as transceiver modules). The RF signal transceiver and conversion section is mainly used for transmitting and receiving RF signals and converting RF signals to baseband signals. The baseband section 42 is mainly used for baseband processing and controlling the network device. The receiving module 41 can also be called a receiver, receiver circuit, etc., and the transmitting module 43 can also be called a transmitter, transmitter, transmitter circuit, etc. The baseband section 42 is usually the control center of the network device, and can also be called a processing module, used to execute the steps performed by the network device in any of the above methods. See the description of the relevant sections above for details. The transmitting module 43 may include an antenna and RF circuitry. The RF circuitry is mainly used for converting baseband signals to RF signals and processing RF signals. The antenna is mainly used for transmitting and receiving RF signals in the form of electromagnetic waves.
[0241] The baseband section 42 may include one or more boards, each board may include one or more processors and one or more memories. The processors are used to read and execute programs in the memories to implement baseband processing functions and control network devices. If multiple boards exist, they can be interconnected to increase processing power. As an optional implementation, multiple boards may share one or more processors, multiple boards may share one or more memories, or multiple boards may simultaneously share one or more processors.
[0242] Please refer to Figure 9, which is a schematic diagram of a RAN chip structure provided in an embodiment of this application, and can be used as another implementation of the network device of this application.
[0243] The chip 1000 includes an interface circuit 1001 and a processor 1002. The interface circuit 1001 and the processor 1002 are coupled to each other. The interface circuit can be a transceiver, an input / output interface, or a transceiver circuit, etc. Optionally, the chip 1000 may also include a memory 1003 for storing instructions executed by the processor 1002, or storing input data required for the processor to run instructions, or storing data generated after the processor runs instructions.
[0244] Please refer to Figure 10, which is a simplified structural diagram of a UE provided in an embodiment of this application, as an implementation of the terminal device in this application.
[0245] For ease of understanding and illustration, Figure 10 uses a mobile phone as an example of a UE. As shown in Figure 10, the UE includes at least one processor, and may also include radio frequency (RF) circuitry, an antenna, and input / output devices. The processor can be used to process communication protocols and communication data, as well as to control the UE, execute software programs, and process data from those programs. The UE may also include a memory, primarily used to store software programs and data. These programs can be loaded into the memory at the time of manufacture or added later when needed. The RF circuitry is mainly used for converting baseband signals to RF signals and processing RF signals. The antenna is mainly used for transmitting and receiving RF signals in the form of electromagnetic waves. Input / output devices, such as touchscreens, displays, and keyboards, are mainly used to receive user input data and output data to the user. It should be noted that some types of UEs may not have input / output devices.
[0246] When a signal needs to be transmitted, the processor performs baseband processing on the data to be transmitted and outputs the baseband signal to the radio frequency (RF) circuit. The RF circuit then processes the baseband signal and transmits it outward as an electromagnetic wave through the antenna. When data is sent to the UE, the RF circuit receives the RF signal through the antenna, converts it into a baseband signal, and outputs it to the processor. The processor converts the baseband signal back into data and processes it. For ease of explanation, only one memory and processor are shown in Figure 10. In actual UE products, there may be one or more processors and one or more memories. Memory can also be called storage medium or storage device, etc. Memory can be set up independently of the processor or integrated with the processor; this embodiment does not limit this.
[0247] In this embodiment, the antenna and radio frequency circuit with transceiver functions can be regarded as the receiving unit and transmitting unit of the UE (or collectively referred to as the transceiver unit), and the processor with processing functions can be regarded as the processing unit of the UE. As shown in Figure 10, the UE includes a receiving module 31, a processing module 32, and a transmitting module 33. The receiving module 31 can also be referred to as a receiver, receiver circuit, etc., and the transmitting module 33 can also be referred to as a transmitter, transmitter, transmitter circuit, etc. The processing module 32 can also be referred to as a processor, processing board, processing device, etc.
[0248] It is understood that the processor in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor can be a microprocessor or any conventional processor.
[0249] Optionally, the memory may also store data. The processor and memory may be configured separately or integrated together. The memory may be non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or it may be volatile memory, such as random-access memory (RAM). In the embodiments of this application, the processor may also be flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art.
[0250] Optionally, the UE may include instructions (sometimes referred to as code or program) that can be executed on the processor.
[0251] Optionally, the UE may also include a transceiver and an antenna. The transceiver may be referred to as a transceiver unit, transceiver module, transceiver, transceiver circuit, transceiver, input / output interface, etc., and is used to realize the UE's transmission and reception functions through the antenna.
[0252] This application provides a communication system, which includes the aforementioned terminal device and network device.
[0253] This application provides a computer-readable storage medium storing computer instructions that, when executed, cause the computer to perform the method described in any of the above methods.
[0254] This application provides a computer program product, which includes computer program code. When the computer program code is run, it causes the computer to perform the method described in any of the above methods.
[0255] This application provides a chip coupled to a memory for reading and executing program instructions in the memory, so that the device containing the chip implements the method described in any of the above methods.
[0256] In the above embodiments, the descriptions of each embodiment have their own emphasis. Parts not described in detail in a particular embodiment can be found in the relevant descriptions of other embodiments. It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.
[0257] In the several embodiments provided in this application, it should be understood that the disclosed apparatus can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of the units described above is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical or other forms.
[0258] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0259] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.
Claims
1. A communication method characterized by comprising: The method is applied to a terminal device and comprises: receiving configuration information, wherein the configuration information is used to indicate M PUSCH resources, M being a positive integer; sending N first information, wherein the first information is used to send user data based on a contention resolution manner, N being a positive integer less than or equal to M, and N uplink resources used for transmitting the N first information being selected from the M PUSCH resources; receiving second information, wherein the second information comprises at least one indication, a first indication in the at least one indication comprises i-th PUSCH resource information, and the i-th PUSCH resource information is used to send one of the N first information.
2. The method of claim 1, wherein, Each indication in the at least one indication is used to indicate retransmission of the first information, and the first indication is used to indicate retransmission of the first information by at least one terminal device that sends the first information using the i-th PUSCH resource information.
3. The method according to claim 1 or 2, characterized in that, The second information is sent through at least one MAC subPDU or downlink control information (DCI), wherein the at least one MAC subPDU is used to determine a contention resolution condition.
4. The method according to claim 2 or 3, characterized in that, Each indication in the at least one indication is a MAC subPDU corresponding to a fallback response, and the i-th PUSCH resource information is included in the fallback response or a MAC subheader of the fallback response.
5. The method according to any one of claims 1 to 4, characterized in that, The second information further comprises at least one contention resolution response indication, a first contention resolution response indication in the at least one contention resolution response indication is a corresponding response of one or more of the N first information, and the method further comprises: ignoring the first indication or canceling retransmission of the first information; or processing the at least one contention resolution response indication, and stopping processing of other MAC subPDUs after processing the first contention resolution response indication.
6. The method according to any one of claims 1 to 5, characterized in that, A second indication in the at least one indication is used to indicate at least one of the following: retransmitting the first information in an OCC-based manner; retransmitting the first information in a non-OCC-based manner; or sending user data in a random access-based manner.
7. The method of claim 6, wherein, The second indication comprises j-th PUSCH resource information, and the j-th PUSCH resource information is used to send one of the N first information.
8. The method according to claim 6 or 7, characterized in that, The fallback response or the MAC subheader of the fallback response comprises 1-bit information, which is used to indicate retransmission of the first information in an OCC-based manner or retransmission of the first information in a non-OCC-based manner, and the fallback response does not comprise uplink grant information, which is used to indicate sending user data in a random access-based manner.
9. A communication method characterized by comprising: The method is applied to a network device and comprises: sending configuration information, wherein the configuration information is used to indicate M PUSCH resources, M being apositive integer; receiving first information, wherein the first information is user data sent based on a contention resolution manner, N being a positive integer less than or equal to M, N uplink resources used for transmitting the first information being selected from the M PUSCH resources, and the first information being used to send user data based on a contention resolution manner; and transmitting second information, the second information comprising at least one indication, a first indication of the at least one indication comprising i-th PUSCH resource information, the i-th PUSCH resource information being used for transmitting one of the N first information.
10. The method of claim 9, wherein, Each indication of the at least one indication is used for indicating retransmission of the first information, the first indication being used for indicating retransmission of the first information by at least one terminal device that transmits the first information using the i-th PUSCH resource information.
11. The method according to claim 9 or 10, characterized in that, The second information is transmitted by at least one MAC subPDU or by DCI, the at least one MAC subPDU being used for determining contention resolution.
12. The method according to claim 10 or 11, characterized in that, Each indication of the at least one indication is a MAC subPDU corresponding to a fallback response, the i-th PUSCH resource information being comprised in the fallback response or a MAC subheader of the fallback response.
13. The method according to any one of claims 9-12, characterized in that, The second information further comprises at least one contention resolution response indication, a first contention resolution response indication of the at least one contention resolution response indication being a corresponding response of one or more of the N first information.
14. The method according to any one of claims 9 to 13, characterized in that, A second indication of the at least one indication is used for indicating at least one of: retransmitting the first information in an OCC-based manner; retransmitting the first information in a non-OCC-based manner; or transmitting user data in a random access-based manner.
15. The method of claim 14, wherein, The second indication comprises j-th PUSCH resource information, the j-th PUSCH resource information being used for transmitting one of the N first information.
16. The method according to claim 14 or 15, characterized in that The fallback response or the MAC subheader of the fallback response comprises 1-bit information, the 1-bit information being used for indicating retransmitting the first information in an OCC-based manner or retransmitting the first information in a non-OCC-based manner, the fallback response not comprising uplink grant information, the uplink grant information being used for indicating transmitting user data in a random access-based manner.
17. A communications device, characterized by The apparatus comprises means or units for implementing the method of any one of claims 1 to 8, or the apparatus comprises means or units for implementing the method of any one of claims 9 to 16. 18.A communication apparatus, comprising: at least one processor coupled with a memory; wherein the at least one processor is configured to execute computer programs or instructions stored in the memory, so that the method of any one of claims 1 to 8 is implemented, or so that the method of any one of claims 9 to 16 is implemented.
19. The communication apparatus according to claim 17, wherein The memory stores computer programs or instructions.
20. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a computer program, which, when executed, causes the method of any one of claims 1 to 8 to be implemented, or causes the method of any one of claims 9 to 16 to be implemented.
21. A computer program, characterized in that, The computer program, when executed, causes the method of any one of claims 1 to 8 to be performed, or causes the method of any one of claims 9 to 16 to be performed.
