Communication method and communication apparatus

Abstract

The present application provides a communication method and a communication apparatus. In the method, when a terminal device starts a first timer, the terminal device makes all subsequently sent second messages carry information used for determining a first RNTI, and extends the running duration of the first timer, so that contention resolution messages corresponding to the subsequent second messages can all be monitored by means of the first timer, thereby improving the efficiency of receiving contention resolution messages.

Description

Communication methods and communication devices

[0001] This application claims priority to Chinese Patent Application No. 202411600808.3, filed on November 8, 2024, entitled "Communication Method and Communication Device", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more specifically, to a communication method and a communication device. Background Technology

[0003] During the random access process of the terminal device, the terminal device sends a random access preamble, i.e., message 1 (Msg1), to the network device; then, the network device sends a random access response, i.e., message 2 (Msg2), to the terminal device; then, based on RAR scheduling, the terminal device transmits a message, i.e., message 3 (Msg3), on the predetermined physical uplink shared channel (PUSCH). Msg3 carries an identifier for contention resolution (e.g., the terminal device's identity (ID) or a contention resolution identifier); after receiving Msg3, the network device sends a contention resolution message, i.e., message 4 (Msg4), to the terminal device.

[0004] In this process, the network device scrambles Msg4 with a radio network temporary identifier (RNTI) on the physical downlink control channel (PDCCH). This RNTI is derived based on the PUSCH occasion used for Msg3 transmission. After the terminal device sends Msg3, it starts a contention resolution timer and then monitors the PDCCH within the time window. If Msg4 scrambled with this RNTI is detected on the PDCCH, the contention resolution is considered successful (i.e., the terminal device has successfully accessed the network).

[0005] The aforementioned Msg3 can be transmitted through the diversity slotted ALOHA (DSA) mechanism. Under this mechanism, the terminal device can send multiple copies of the data packet. If any copy is located in a time slot without interference from other data packets, the terminal device considers the data packet to have been successfully transmitted.

[0006] However, when transmitting multiple copies of Msg3, the terminal device will start multiple contention resolution timers to monitor Msg4. Each contention resolution timer corresponds to an RNTI for Msg4 descrambling / scrambling. If the time windows of two or more contention resolution timers overlap, the overlapping time window corresponds to two or more RNTIs. The terminal device cannot determine which RNTI the received Msg4 corresponds to during the overlapping window period. Summary of the Invention

[0007] This application provides a communication method and a communication device that enables the determination of the RNTI used to monitor the contention resolution message when the time windows of multiple contention resolution timers overlap.

[0008] Firstly, a communication method is provided, which can be executed by a terminal device or by a component of the terminal device (such as a chip, circuit, or chip system). For ease of understanding, the following description uses execution by a terminal device as an example.

[0009] The method includes: sending a first message, the first message including first data and first information for contention resolution; starting a first timer, the first timer being used to monitor contention resolution messages scrambled by a first Radio Network Temporary Identifier (RNTI), the first RNTI being determined based on the timing of sending the first message using the Physical Uplink Shared Channel (PUSCH), the first timer expiring after its runtime reaches a first duration; sending N second messages, the second messages including the first data and second information for contention resolution, the second information being determined based on the timing of sending the first message using the PUSCH; and, at the i-th transmission of the second message, determining that the first timer expiring after its runtime reaches a second duration, the second duration being greater than the first duration, the difference between the second duration and the first duration being equal to the duration of the time interval between the i-th transmission of the second message and the transmission of the first message, where i is an integer, i∈[1,N].

[0010] Optionally, the first and second messages are copies of msg3 sent in different time slots.

[0011] Optionally, the race resolution message is msg4.

[0012] Based on the above scheme, after the first timer is started, all subsequent second messages sent carry information for determining the first RNTI, and the runtime of the first timer is extended. Thus, the contention resolution messages corresponding to the subsequent second messages can be monitored through the first timer, which improves the efficiency of receiving contention resolution messages.

[0013] In some implementations, the method further includes: when the second message is sent for the (N+1)th time, determining that the first timer expires after the runtime of the first timer reaches a third duration, wherein the third duration is longer than the second duration, and the difference between the third duration and the second duration is equal to the duration of the time interval between the i-th and N+1-th transmissions of the second message.

[0014] Based on the above scheme, the runtime of the first timer is extended each time a new second message is sent, so that the contention resolution message corresponding to the second message can be monitored through the first timer, thereby improving the efficiency of receiving contention resolution messages.

[0015] In some implementations, the first information includes the identifier of the terminal device, or a parameter indicating the timing of the PUSCH used to send the first message, or the first RNTI.

[0016] Based on the above scheme, the network device can determine the first RNTI that scrambles the contention resolution message through the first information sent by the terminal device, so that the contention resolution message corresponding to the first message can be monitored by the first timer.

[0017] In some implementations, the second information includes parameters of the timing of the PUSCH used to send the first message, or it includes the first RNTI.

[0018] Based on the above scheme, the network device can determine the first RNTI that scrambles the contention resolution message through the second information sent by the terminal device, so that the contention resolution message corresponding to the second message can be monitored by the first timer.

[0019] In some implementations, before sending the first message, the method further includes: sending M third messages, the third messages including the first data and third information for contention resolution; when sending the third message for the jth time, starting a j-th timer, the j-th timer being used to monitor contention resolution messages scrambled by a j-th RNTI, the j-th RNTI being determined based on the timing of the PUSCH used when sending the j-th third message; when sending the (j+1)-th timer, starting a (j+1)-th timer, the (j+1)-th timer being used to monitor contention resolution messages scrambled by a (j+1)-th RNTI, the (j+1)-th RNTI being determined based on the timing of the PUSCH used when sending the (j+1)-th third message, where j is an integer, j∈[1, M-1].

[0020] Optionally, the third message is a copy of msg3.

[0021] Based on the above scheme, before sending the first message, the terminal device has sent multiple copies of msg3 and started the corresponding contention resolution timer for each.

[0022] In some implementations, when a contention resolution message is received, if both the j-th timer and the (j+1)-th timer are running, the method further includes: monitoring the contention resolution message using the (j+1)-th RNTI; or, if monitoring the contention resolution message using the (j+1)-th RNTI fails, then monitoring the contention resolution message using the (j+1)-th RNTI.

[0023] Based on the above scheme, when a contention resolution message is received, the terminal device can use the RNTI corresponding to the timer to monitor msg4 in order from early to late according to the timer's start time.

[0024] In some implementations, before sending the first message, the method further includes: sending a third message, the third message including the first data and third information for contention resolution; and starting a second timer for monitoring contention resolution messages scrambled by a second RNTI, the second RNTI being determined based on the timing of the PUSCH used to send the third message.

[0025] In some implementations, when a contention resolution message is received, if both the first timer and the second timer are running, the method further includes: monitoring the contention resolution message using the second RNTI; or, if monitoring the contention resolution message using the second RNTI fails, monitoring the contention resolution message using the first RNTI.

[0026] In some implementations, the third information includes the identifier of the terminal device, or includes parameters of the timing of the PUSCH used to send the third message, or includes RNTI determined based on the parameters of the timing of the PUSCH used to send the third message.

[0027] Based on the above scheme, network devices can determine the RNTI that scrambles the contention resolution message through the third information sent by the terminal device, so that the contention resolution message corresponding to the third message can be monitored by the corresponding timer.

[0028] In some implementations, before the i-th transmission of the second message, the method further includes: determining the second message based on the number of currently running timers.

[0029] In some implementations, determining the second message based on the number of currently running timers includes: if the number of currently running timers is equal to the maximum number supported by the terminal device, then the second message includes the second information.

[0030] Based on the above scheme, when sending a copy of msg3, the terminal device determines the content of the msg3 copy based on whether the number of currently running timers is equal to the maximum number supported by the terminal device.

[0031] In some implementations, the method further includes: receiving first indication information, the first indication information being used to indicate a maximum number of time slots, wherein time slots within the maximum number of time slots can be randomly selected by the terminal device for sending a message including the first data, or the random number of time slots within the maximum number of time slots can be selected by the terminal device as the time interval between two consecutively sent messages including the first data, wherein the message including the first data includes the first message and the second message.

[0032] Secondly, a communication method is provided, which can be executed by a network device or by a component of the network device (such as a chip, circuit, or chip system). For ease of understanding, the following description uses execution by a terminal device as an example.

[0033] The method includes: receiving at least one of a first message and N second messages from a terminal device, the first message including first data and first information for contention resolution, the second message including first data and second information for contention resolution, the second information being determined based on the timing of sending the first message using the Physical Uplink Shared Channel (PUSCH); and sending a contention resolution message scrambled with a first Radio Network Temporary Identifier (RNTI), the first RNTI being determined based on the timing of sending the first message using the PUSCH.

[0034] In some implementations, the method further includes: the first information includes the identifier of the terminal device, or includes a parameter of the timing of the PUSCH used in sending the first message, or includes a second RNTI, the second RNTI being determined based on the timing of the Physical Uplink Shared Channel (PUSCH) used in sending the first message.

[0035] In some implementations, the method further includes: the second information includes parameters of the timing of the PUSCH used in the most recent transmission of the first message, or includes the first RNTI.

[0036] In some implementations, the method further includes: sending first indication information, the first indication information being used to indicate a maximum number of time slots, wherein time slots within the maximum number of time slots can be randomly selected by the terminal device for sending a message including the first data, or the random number of time slots within the maximum number of time slots can be selected by the terminal device as the time interval between two consecutively sent messages including the first data, wherein the message including the first data includes the first message and the second message.

[0037] Thirdly, a communication device is provided, which has the function of implementing the method in the first aspect or any possible implementation of the first aspect. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above-described function.

[0038] Fourthly, a communication device is provided, which has the function of implementing the method in the second aspect or any possible implementation of the second aspect. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above-described function.

[0039] Fifthly, a communication device is provided, comprising at least one processor configured to cause the communication device to execute the method of the first aspect or any possible implementation thereof; or to execute the method of the second aspect or any possible implementation thereof. Optionally, the at least one processor is coupled to at least one memory for storing computer programs or instructions, and the at least one processor is configured to call and run the computer program or instructions from the at least one memory, causing the communication device to execute the method of the first aspect or any possible implementation thereof; or to execute the method of the second aspect or any possible implementation thereof. Optionally, the at least one processor may be included in the communication device or may be configured outside the communication device. Optionally, the communication device further includes the at least one memory. Furthermore, the communication device may optionally include a communication interface coupled to the at least one processor, which can be used to input information and / or data to the at least one processor, or to output information and / or data from the at least one processor. As an example, the communication interface may include an input interface and / or an output interface, or an interface circuit, etc.

[0040] Sixthly, a communication device is provided, comprising a communication interface and a circuit. The communication interface is configured to receive a signal to be processed and transmit the signal to the circuit. The circuit is configured to process the signal to perform a method as described in the first aspect or any possible implementation thereof; or to perform a method as described in the second aspect or any possible implementation thereof. Optionally, the communication interface is further configured to output the signal processed by the circuit. As an example, the communication interface may be a transceiver, hardware circuit, bus, module, pin, or other type of communication interface. The signal includes information and / or data. Optionally, the communication device may be a chip.

[0041] A seventh aspect provides a computer-readable storage medium storing computer program code or instructions that, when executed on a computer, cause the method as described in the first aspect or any possible implementation thereof to be implemented; or, the method as described in the second aspect or any possible implementation thereof to be implemented.

[0042] Eighthly, a computer program product is provided, the computer program product comprising computer program code or instructions, which, when executed on a computer, cause the method in the first aspect or any possible implementation thereof to be implemented; or, as in the second aspect or any possible implementation thereof, the method to be implemented.

[0043] A ninth aspect provides a wireless communication system, including a communication device as described in the third aspect and a communication device as described in the fourth aspect. Attached Figure Description

[0044] Figure 1 is a schematic diagram of a network architecture applicable to an embodiment of this application.

[0045] Figure 2 is a schematic diagram of the functions implemented by the central unit (CU) and the distributed unit (DU).

[0046] Figure 3 is a schematic diagram of an ORAN system applicable to an embodiment of this application.

[0047] Figure 4 is a schematic diagram of several satellite communication architectures.

[0048] Figure 5 is a schematic flowchart of random access for a terminal device.

[0049] Figures 6 to 8 are schematic flowcharts of the communication method provided in this application.

[0050] Figure 9 is a schematic structural diagram of a communication device provided in this application.

[0051] Figure 10 is a schematic structural diagram of another communication device provided in this application.

[0052] Figure 11 is a schematic structural diagram of the chip provided in this application. Detailed Implementation

[0053] To facilitate understanding of the embodiments of this application, the following points are provided.

[0054] First, in this application, "for indicating" can include both direct and indirect indication. When describing an indication information as indicating A, it can include whether the indication information directly indicates A or indirectly indicates A, but does not necessarily mean that the indication information includes A.

[0055] The information indicated by the instruction information is called the instruction-to-be-instructed information. In the specific implementation, there are many ways to instruct the instruction-to-be-instructed information. The instruction-to-be-instructed information can be sent as a whole, or it can be divided into multiple sub-information messages and sent separately. Furthermore, the sending period and / or timing of these sub-information messages can be the same or different. This application does not limit the specific sending method. The sending period and / or timing of these sub-information messages can be predefined, for example, according to a protocol, or configured by the transmitting device by sending configuration information to the receiving device.

[0056] Second, in this application, the words "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the words "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0057] Third, in the embodiments of this application, "under the circumstances", "when", and "if" can sometimes be used interchangeably. It should be noted that when the distinction is not emphasized, their intended meanings are consistent.

[0058] Fourth, the term "and / or" in the embodiments of this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. In addition, the character " / " in this document generally indicates that the related objects before and after it have an "or" relationship.

[0059] Fifth, the various message names or device names involved in the embodiments of this application are merely examples and do not constitute any limitation on the scope of protection of this application. For example, messages may have different names, as long as they can achieve the corresponding functions.

[0060] Sixth, the terms "message", "information", or "information element (IE)" can be used interchangeably in this article. There are no restrictions on the names of messages or information, as long as they can achieve the corresponding functions.

[0061] In this application, "send" and "receive" refer to the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, and "send information" can include direct transmission or indirect transmission through other units or modules. "Receive information from YY" can be understood as the source of the information being YY, and "receive information" can include direct reception from YY or indirect reception from YY through other units or modules. Besides air interface transmission or reception signals implemented at the system level, such as network devices or terminal devices, "send" can also be understood as the "output" of a chip interface, and "receive" can also be understood as the "input" of a chip interface. For example, a modem or system-on-a-chip (SoC) chip or system-in-package (SIP) chip transmits or receives signals. "Send" or "receive" can also be performed through device components, for example, by using buses, traces, or interfaces to transmit or receive signals through several parts, modules, or chips of a device.

[0062] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0063] The technical solutions of this application can be applied to satellite communication systems, high altitude platform station (HAPS) communication, and non-terrestrial network (NTN) systems such as unmanned aerial vehicles (UAVs), including integrated communication and navigation (ICAN) systems, GNSS, and ultra-dense low-Earth orbit satellite communication systems. Satellite communication systems can be integrated with traditional mobile communication systems. For example, the mobile communication system can be a fourth-generation (4G) communication system (e.g., Long Term Evolution (LTE) system), a worldwide interoperability for microwave access (WiMAX) communication system, a fifth-generation (5G) communication system (e.g., new radio (NR) system), and future mobile communication systems.

[0064] Figure 1 is a schematic diagram of a communication system applicable to this application. As shown in Figure 1, the communication system 100 includes at least one network device, such as network device 111, network device 112, and network device 113 shown in Figure 1. The wireless communication system may also include at least one terminal device, such as terminal device 121, terminal device 122, terminal device 123, terminal device 124, terminal device 125, terminal device 126, and terminal device 127 shown in Figure 1.

[0065] For example, network devices and terminal devices can communicate with each other, including but not limited to: multi-site transmission, enhanced mobile broadband (eMBB) transmission, etc., wherein network devices 112 and 113 as shown in FIG1 can transmit with terminal device 124 through multi-site transmission, and network device 112 as shown in FIG1 can transmit with terminal devices 121, 122 and 123 through eMBB transmission.

[0066] For example, network devices can also communicate with each other, including but not limited to: backhaul. As shown in FIG1, network device 111 and network device 112 can communicate through backhaul, and network device 111 and network device 113 can also communicate through backhaul. In this case, network device 112 and network device 113 can act as relay nodes in the system.

[0067] For example, terminal devices can also communicate with each other, including but not limited to device-to-device (D2D) transmission. For example, terminal device 122 and terminal device 125 can communicate with each other via D2D transmission as shown in FIG1.

[0068] A network device is a network-side device with wireless transceiver capabilities. A network device can be a device in a radio access network (RAN) that provides wireless communication capabilities to terminal devices. Network devices can be cellular systems related to the 3rd Generation Partnership Project (3GPP), such as 5G mobile communication systems, or future-oriented evolution systems. Network devices can also be open radio access networks (O-RAN or ORAN), cloud radio access networks (CRAN), or wireless fidelity (WiFi) systems. For example, the network device can be a base station, an evolved NodeB (eNodeB), a next-generation NodeB (gNB) in a 5G mobile communication system, a 3GPP subsequent evolution base station, a transmission reception point (TRP), an access node, a wireless relay node, or a wireless backhaul node in a WiFi system. In communication systems employing different radio access technologies (RATs), the names of devices with base station capabilities may differ. For example, in an LTE system, it may be called an eNB or eNodeB, and in a 5G or NR system, it may be called a gNB. This application does not limit the specific name of the base station. The network equipment may include one or more co-located or non-co-located transmitting and receiving points. Furthermore, the network equipment may include at least one of the following: one or more central units (CUs), one or more distributed units (DUs), and one or more radio units (RUs).

[0069] 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. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU (open 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. 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. Exemplarily, the function of CU can be implemented by one entity or different entities. For example, the function of CU can be further divided, that is, the control plane and user plane can be separated and implemented through different entities, namely the control plane CU entity (i.e., the CU-CP entity) and the user plane CU entity (i.e., the CU-UP entity). The CU-CP entity and the CU-UP entity can be coupled with the DU to jointly complete the function of the access network device. For example, the CU (Complex Unit) is responsible for handling non-real-time protocols and services, implementing the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers. The DU (Digital Unit) is responsible for handling physical layer protocols and real-time services, implementing the functions of the radio link control (RLC), medium / media access control (MAC), and physical (PHY) layers. This allows multiple network function entities to implement some of the functions of a radio access network device. These network function entities can be network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). Network devices can also include active antenna units (AAUs). The AAU implements some physical layer processing functions, radio frequency processing, and related functions of the active antenna. Since RRC layer information ultimately becomes PHY layer information, or is derived from PHY layer information, in this architecture, higher-layer signaling, such as RRC layer signaling, can also be considered as being sent by the DU, or by the DU+AAU. It is understood that network devices can be one or more of the following: CU nodes, DU nodes, and AAU nodes. Furthermore, a CU can be classified as a network device in the RAN, or it can be classified as a network device in the core network (CN); this application does not limit this classification.For example, in vehicle-to-everything (V2X) technology, the access network equipment can be a roadside unit (RSU). Multiple access network devices in the communication system can be base stations of the same type or different types. Base stations can communicate with terminal devices, or they can communicate with terminal devices through relay stations. In this embodiment, the device used to implement the network device function can be the network device itself, or a device that supports the network device in implementing that function, such as a chip system or a combination of devices or components that can implement the access network device function. This device can be installed in the network device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices.

[0070] A terminal device is a user-side device with wireless transceiver capabilities. It can be a fixed device, mobile device, handheld device (e.g., mobile phone), wearable device, in-vehicle device, or a wireless device (e.g., communication module, modem, or chip system) built into the aforementioned devices. Terminal devices are used to connect people, objects, and machines, and can be widely used in various scenarios, such as: cellular communication, D2D communication, V2X communication, machine-to-machine / machine-type communications (M2M / MTC), the Internet of Things (IoT), virtual reality (VR), augmented reality (AR), industrial control, self-driving, remote medical care, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, drones, robots, etc. For example, a terminal device can be a handheld terminal in cellular communication, a communication device in D2D, an IoT device in MTC, a surveillance camera in smart transportation and smart cities, or a communication device on a drone. Terminal equipment is sometimes referred to as user equipment (UE), user terminal, user device, user unit, user station, terminal, access terminal, access station, UE station, remote station, mobile device, or wireless communication device, etc. Terminal equipment can also be a terminal device in an IoT system. IoT is an important component of future information technology development. Its main technical characteristic is connecting objects to networks through communication technology, thereby realizing an intelligent network of human-machine interconnection and machine-to-machine interconnection. In the embodiments of this application, IoT technology can achieve massive connectivity, deep coverage, and terminal power saving through technologies such as narrowband (NB). In the embodiments of this application, the device used to implement the functions of the terminal equipment can be the terminal equipment itself, or it can be a device that supports the terminal equipment in implementing the functions, such as a chip system or a combination of devices or components that can implement the functions of the terminal equipment. This device can be installed in the terminal equipment. The terminal typically contains a communication module, circuit, or chip (such as a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip) that performs the corresponding communication functions. The terminal can also be configured with program instructions for performing corresponding communication functions.

[0071] Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located.

[0072] For example, the communication system 100 may further include an application function (AF) network element, which is a control plane network function provided by the operator's network for providing application layer information; the communication system 100 may also include a session management function (SMF) network element, which is a control plane network function provided by the operator's network. In this embodiment, when the communication system 100 includes both AF and SMF network elements, the AF can send service-related information to the network device through the SMF.

[0073] The satellite mentioned in this application can also be a satellite base station or a network-side device mounted on a satellite. The satellite in this application can also be a central unit (CU), a distributed unit (DU), a radio unit (RU), or an open radio access network (O-RAN) node mounted on a satellite. The CU and DU can be two independent satellite nodes or integrated into the same satellite node, for example, integrated into a baseband unit (BBU). The RU can be included in radio frequency equipment, such as a remote radio unit (RRU) or an active antenna unit (AAU). The CU can be further divided into two types of nodes: CU-control plane (CU-CP) and CU-user plane (CU-UP).

[0074] Figure 2 is a schematic diagram of the functions implemented by CU and DU.

[0075] As shown in Figure 2(a), the CU can implement the functions of the radio resource control (RRC) layer, packet data convergence protocol (PDCP) layer, and service data adaptation protocol (SDAP) layer in the 3rd generation partnership project (3GPP) standard. The DU can implement the functions of the radio link control (RLC) layer and medium access control (MAC) layer in the 3GPP standard, and can also complete some or all of the physical layer (PHY) functions. For specific descriptions of the above protocol layers, please refer to the relevant 3GPP technical specifications. The RU can be used to implement the radio frequency signal transmission and reception functions.

[0076] As shown in Figure 2(b), when the CU is divided into CU-CP and CU-UP, CU-CP is used to implement the functions of the RRC layer and the control plane (PDCP-C) function of the PDCP layer. CU-UP is used to implement the functions of the SDAP layer and the user plane (PDCP-U) function of the PDCP layer.

[0077] In Figure 2, E1 is the interface between CU-CP and CU-UP, F1 is the interface between CU and DU, F1-C is the interface between CU-CP and DU, and F1-U is the interface between CU-UP and DU.

[0078] In different systems, CU (or CU-CP and CU-UP), DU, or RU can also have different names. For example, in an O-RAN system, CU can also be called an open CU (O-CU), DU can also be called an open DU (O-DU), and RU can be called an open RU (O-RU). CU-CP can also be called an open CU-CP (O-CU-CP), and CU-UP can also be called an open CU-UP (O-CU-UP). It should be understood that the O-RAN system aims to achieve an intelligent and open access network. The main feature of the O-RAN system is the separation of hardware and software, realizing the virtualization of network functions and the standardization of hardware. In addition, the O-RAN system can also introduce artificial intelligence (AI) or machine learning (ML).

[0079] For example, Figure 3 is a schematic diagram of an ORAN system, which may include one or more O-CUs, O-DUs, O-RUs, etc. Specific protocol layer functions can be found in Table 1.

[0080] Table 1. Correspondence between RAN nodes and their achievable protocol layer functions in the RAN system.

[0081] Any of the CU (or CU-CP, CU-UP), DU, and RU units in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules. In the ORAN system, any of the O-CU (or O-CU-CP, O-CU-UP), O-DU, and O-RU units in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0082] It is understood that the segmentation of the protocol layer functions of the RAN nodes shown in Table 1 is only an example and does not constitute a limitation on CU, DU, and RU.

[0083] As communication requirements continue to rise, traditional terrestrial networks (TN) cannot provide seamless coverage for terminal devices, especially in areas where base stations cannot be deployed, such as oceans, deserts, and the air. Introducing non-terrestrial networks (NTN), by deploying base stations or some base station functions on non-terrestrial network equipment such as satellites, can provide seamless coverage for terminal devices and improve communication reliability.

[0084] Based on satellite altitude, or orbital altitude, satellite systems can be divided into high-Earth orbit (GEO) satellites and medium-Earth orbit (LEO) satellites. GEO satellites, also known as geostationary orbit (GEO) satellites, move at the same speed as the Earth's rotation, thus remaining stationary relative to the ground. Correspondingly, the cells of GEO satellites are also stationary. GEO satellite cells have relatively large coverage areas, typically with a cell diameter of 500 km. LEO satellites include medium Earth orbit (MEO) satellites and low Earth orbit (LEO) satellites. MEO and LEO satellites move faster relative to the ground, therefore their service coverage areas also shift. Thus, for LEO satellites, the cells they provide coverage for can be divided into two types:

[0085] (1) 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.

[0086] (2) 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.

[0087] Based on their operating modes, satellites are generally divided into two main categories: the first is transparent satellites, which relay radio frequency signals from ground-based base stations. The second is regenerative satellites, which possess all or part of the functions of a base station; that is, the base station or some of its functions are deployed on the satellite. The following explanation is based on Figure 4, where (a) corresponds to a transparent satellite, and (b) to (d) correspond to regenerative satellites.

[0088] Figure 4 is a schematic diagram of several satellite communication architectures. The architectures shown in Figure 4(a) to (d) can be collectively referred to as NTN-based NG-RAN architectures.

[0089] Figure 4(a) shows a transparent satellite RAN architecture. As shown in Figure 4(a), in this architecture, the satellite forwards the radio frequency signals from the ground-based base station. The satellite's role is to perform radio frequency filtering, frequency conversion, and amplification. That is, the satellite primarily acts as a Layer 1 relay, regenerating physical layer signals, and does not involve any higher protocol layers. Therefore, the satellite replicates the NR Uu radio interface signal from the feeder link (between the NTN gateway and the satellite) to the service link (between the satellite and the UE), and vice versa. The satellite radio interface (SRI) on the feeder link transmits the NR Uu interface signal; that is, the satellite does not terminate the NR Uu interface signal but rather replicates it. The NTN gateway supports all necessary functions for forwarding the NR Uu interface signal. Different transmission satellites can connect to the same terrestrial base station (such as a next-generation NodeB (gNB) or an evolved NodeB (eNB) in a 5G system). The SRI interface is a transmission link between the NTN gateway and the satellite. In this architecture, the satellite and the NTN gateway can be considered as a single remote radio unit.

[0090] Figure 4(b) shows a regenerative satellite without ISL architecture. In this architecture, the satellite acts as a base station, regenerating signals received from the ground. Specifically, NR Uu radio interface signals are transmitted on the service link between the UE and the satellite, and SRI signals are transmitted on the feeder link between the NTN gateway and the satellite. NG interface signals are transmitted to the NTN gateway via the SRI interface, and then forwarded by the NTN gateway to the ground core network equipment. The process of transmitting NG interface signals from the ground core network equipment to the satellite base station is similar and will not be described further here.

[0091] Figure 4(c) shows a regenerative satellite with ISL architecture. In this architecture, the satellite also acts as a base station. The difference from the architecture shown in Figure 4(b) is that this scenario includes an ISL. An ISL is an inter-satellite transmission link. As shown in Figure 4(b), a UE served by an on-board base station can access the 5G core network via the ISL. Base stations on different satellites can connect to the same terrestrial 5G core network.

[0092] Figure 4(d) shows the architecture of NG-RAN with a regenerative satellite based on gNB-DU. In this architecture, the CU and DU of the base station are separated. The satellite, as the DU of the base station, is on-board. The satellite realizes the regeneration of signals received from the ground, that is, it transmits NR Uu radio interface signals on the service link between the UE and the satellite, and transmits SRI signals on the feed link between the NTN gateway and the satellite. SRI is a transport link capable of transmitting the 3GPP standard logical interface F1 signal. F1 protocol signals are transmitted on the SRI. The satellite can provide inter-satellite links (ISL). The NTN gateway is a transport network layer node and supports all necessary transport protocols. DUs on different satellites can be connected to the same ground CU.

[0093] The above RAN architecture is only an example. The embodiments of this application may also be used in other NTN architectures, or in 4G, 5G, and future wireless network architectures.

[0094] To facilitate understanding, some concepts or terms involved in this application will be explained first.

[0095] 1. UE status

[0096] The UE's RRC states include RRC connected state and RRC idle state. Within the RRC idle state, there is a special state called RRC suspended state. Specifically,

[0097] (1) When the UE is in RRC connected state, the UE and the base station establish an RRC connection. After the access stratum (AS) security is activated, the RRC connected state UE will initiate an RRC (connection) reconstruction process after detecting radio link failure, handover failure, integrity verification failure or RRC reconfiguration failure.

[0098] (2) When the UE is in the RRC idle state, the UE and the base station do not establish an RRC connection.

[0099] (3) When the UE is in the RRC suspend state, the UE suspends the RRC connection, including all signal radio bearers (SRBs) and data radio bearers (DRBs), and the UE suspends data processing, but the base station still maintains the UE's AS context. The AS context may include one or more of the UE's current RRC configuration, current security context, source cell C-RNTI, source cell cell identifier, and PCI. As an example, when the UE supports user plane (UP)-based reserved uplink resource (PUR) data transmission or early data transmission (EDT), the base station can indicate a resume identity and RRC suspension in the RRC connection release message, allowing the UE to leave the RRC connected state and enter the RRC suspend state. The resume identity is used to identify the suspended UE context, which is used by the UE to resume the RRC connection. When a UE resumes a suspended RRC connection, for example, when the UE needs to initiate a user plane-based PUR or EDT transmission, or when the UE is a narrow band internet of things (NB-IoT) UE, the UE initiates an RRC (connection) recovery request.

[0100] 2. Contention-based random access (RA)

[0101] Figure 5 is a schematic flowchart of a terminal device performing random access, including the following steps 1 to 4:

[0102] Step 1:

[0103] The terminal device sends the RA preamble, namely Msg1. Specifically, the terminal device obtains the physical random access channel (PRACH) configuration from the system information block (SIB) 1 message, randomly selects an RA preamble, and sends that RA preamble.

[0104] Step 2:

[0105] The network device sends a random access response (RAR), also known as Msg2. The RAR includes the uplink timing advance (TA), the RA preamble identifier, the uplink grant (UL grant), and the temporary cell radio network temporary identifier (T-CRNTI).

[0106] After the terminal device sends the RA preamble, it will start the RA response window and continuously monitor the physical downlink control channel (PDCCH) within the RA sliding window until it obtains the required RA response on the physical uplink shared channel (PDSCH).

[0107] In one implementation, if the RAR contains an RA preamble identifier that is consistent with the RA preamble, the terminal device considers the RA response to be successful and proceeds to step 3.

[0108] In another implementation, if the terminal device does not receive an RA response during the RA sliding window, or if the received RA response fails to be verified, the terminal device assumes that the RA preamble was not correctly received by the network device, and the RA response fails. In this case, if the terminal device's RA attempt count is less than the maximum attempt count, it will retry the RA (i.e., resend the RA preamble); otherwise, the RA process fails.

[0109] Step 3:

[0110] The terminal device sends Msg3.

[0111] After step 2 is completed, the terminal device achieves uplink synchronization and can transmit message Msg3 on the predetermined physical uplink shared channel (PUSCH). Msg3 carries an identifier for contention resolution, such as the terminal device's identifier or a contention resolution identity. This identifier is used in the contention resolution process in step 4 to distinguish the terminal devices that are sending conflicting messages.

[0112] If the terminal device has previously connected to a cell, the cell radio network temporary identifier (C-RNTI) is used as the identifier for contention resolution. This identifier is unique to the terminal device within a specific cell. Otherwise, the terminal device uses an identifier from the core network (such as the Serving Temporary Mobile Subscriber Identity (S-TMSI) or a random number).

[0113] Step 4:

[0114] The network device sends a contention resolution message, namely Msg4, to the terminal device.

[0115] After the terminal device sends Msg3, it starts a contention resolution timer and then monitors the PDCCH within the timer window.

[0116] Specifically, for TN networks, the terminal device starts or restarts the contention resolution timer within the first symbol after the Msg3 transmission ends.

[0117] For NTN networks, the terminal device starts or restarts the contention resolution timer within the first symbol after the round-trip time between the terminal device and the network device following the completion of Msg3 transmission. The network device assists the terminal device in contention resolution by scrambling Msg4 with C-RNTI or TC-RNTI on the PDCCH, or by using the terminal device's Contention Resolution Identity on the PDSCH.

[0118] In one implementation, before the contention resolution timer expires, the terminal device continuously monitors the PDCCH channel. If any of the following conditions exist, the terminal device considers the contention resolution successful (i.e., the terminal device has successfully accessed the network) and stops the contention resolution timer; otherwise, the timer is not stopped.

[0119] i. The terminal device detects Msg4 scrambled with C-RNTI in the PDCCH. At this time, the terminal device will stop the contention resolution timer and discard the T-CRNTI.

[0120] ii. The terminal device detects Msg4 scrambled with T-CRNTI on the PDCCH, and the terminal device's Contention Resolution Identity contained in the MAC protocol data unit (MAC PDU) received by the terminal device from the PDSCH is the same as the terminal device's Contention Resolution Identity carried in Msg3 sent by the terminal device (i.e., the MAC PDU is successfully decoded). At this time, the terminal device will stop the contention resolution timer and set T-CRNTI to C-RNTI.

[0121] In another implementation, if the contention resolution timer times out, the terminal device discards the T-CRNTI and considers the contention resolution to have failed.

[0122] If the RA attempt fails after the contention resolution fails, and the terminal device has fewer RA attempts than the maximum number of attempts, it will attempt RA again (e.g., resend Msg3); otherwise, the RA process will fail.

[0123] It should be understood that the above process is merely an example of a random access procedure, and this application does not limit it.

[0124] 3. Early Data Transmission (EDT)

[0125] EDT can be divided into mobile-originating early data transmission (MO-EDT) and mobile-terminated early data transmission (MT-EDT). The characteristic of EDT is that the UE does not need to switch to RRC connected state for data transmission.

[0126] 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 (MME or AMF).

[0127] 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 keep the UE in RRC (Remote Access Control) idle state.

[0128] The current discussion of EDT enhancement, also known as two-step EDT or contention-based EDT for resolving msg3, involves only msg3 and msg4 in a single data transmission. The RNTI used for scrambling msg4 is derived from the PUSCH occasion used for Msg3 transmission. The PUSCH occasion includes both PUSCH frequency resources and PUSCH time domain resources.

[0129] For example, the RNTI is derived based on the PUSCH occasion used for Msg3 transmission as follows: RNTI = 1 + s_id + 14 × t_id + 14 × 80 × f_id + 14 × 80 × 8 × ul_carrier_id + 14 × 80 × 8 × 2, where s_id is the index of the first OFDM symbol of the PUSCH occasion (0 ≤ s_id < 14), t_id is the index of the first slot of the PUSCH occasion in the system frame (0 ≤ t_id < 80), t_id is the index of the slot in the system frame containing the PUSCH occasion (0 ≤ t_id < 80), and f_id is the index of the PUSCH occasion in the frequency domain (0 ≤ f_id < 8). ul_carrier_id is the UL carrier used for PUSCH transmission (0 represents NUL carrier, 1 represents SUL carrier).

[0130] 4. DSA mechanism

[0131] The ALOHA protocol is a classic protocol. Its core idea is that data can be sent as long as there is data to be sent, without considering the state of the receiving end. However, data collisions are very likely to occur.

[0132] The SA (Slotted ALOHA) protocol divides time into several equal-length time slices called time slots. It stipulates that a terminal must wait until the beginning of a time slot before sending data. If a data packet encounters a collision during transmission (i.e., receiving two or more data packets simultaneously), the terminal randomly backs off for a period before retransmitting. By restricting the transmission time of data packets, the ALOHA protocol changes the randomness of data transmission by the terminal, reducing the probability of data packet collisions.

[0133] Subsequently, DSA (diversity slotted ALOHA) 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 data packets. If any copy is in a time slot where there is no interference from other data packets, the terminal considers the data packet to have been successfully transmitted.

[0134] The diagram below illustrates the access mechanism of the DSA protocol. There are three terminals in the diagram, each of which sends two copies (A and B) of its own data packets. The data packet copies A of terminal 1 and terminal 2 collide in time slot 3, but the data packet copies B of terminal 1 and terminal 2 can be successfully decoded in their respective time slots. Therefore, it is considered that the data packet transmission of terminal 1 and terminal 2 was successful.

[0135] The current discussion is based on the DSA mechanism to send multiple msg3 copies. The introduction of the DSA (diversity slotted ALOHA) mechanism supports the transmission of multiple msg3 copies (i.e., two or more msg3 copies) to improve the efficiency of msg3 contention resolution.

[0136] As described in the background section, the RNTI used for scrambling msg4 transmission is derived based on the PUSCH occasion used for Msg3 transmission. When transmitting multiple copies of msg3, the UE starts multiple contention resolution timer windows to monitor msg4. Each contention resolution timer window corresponds to the RNTI for mgs4 descrambling (msg4 scrambling). However, there is overlap between two or more contention resolution timer windows, and there are also two or more RNTIs. The UE cannot determine which RNTI corresponds to the msg4 received during the overlapping window period.

[0137] Additionally, if the number of msg3 copies transmitted by the UE exceeds the number of contention resolution timers that the UE can enable or run, the UE may not be able to open a new contention resolution timer window to receive Msg4 when it transmits another msg3 copy.

[0138] To address the aforementioned issues, this application provides a communication method that enables the determination of the RNTI used to monitor the contention resolution message when the time windows of multiple contention resolution timers overlap.

[0139] It is understood that in the various embodiments of this application, "monitoring" can be used interchangeably with "receiving", "detecting", or "reading".

[0140] It should be understood that the embodiments shown below use terminal devices and network devices as examples of execution subjects in the interaction illustration to illustrate the method. However, this application does not limit the execution subject of the interaction illustration. As long as a program can run the code of the method provided in the embodiments of this application to communicate according to the method provided in the embodiments of this application. The execution subject of the method provided in the embodiments of this application can be a terminal device and a network device, or a functional module in the terminal device and network device that can call and execute a program. For example, the network device in FIG5 can also be a chip, chip system, or processor that supports the method that the network device can implement, or it can also be a logic module or software that can implement all or part of the network device functions; the terminal device in FIG6 can also be a chip, chip system, or processor that supports the method that the terminal device can implement, or it can also be a logic module or software that can implement all or part of the terminal device functions.

[0141] Figure 6 is a schematic flowchart of a communication method 600 provided in this application. As shown in Figure 6, the method 600 includes the following steps.

[0142] S610, the terminal device sends a first message, the first message including first data and first information for contention resolution.

[0143] The first message is a copy of msg3 during the random access process of the terminal device.

[0144] Optionally, the first message can be the first copy of msg3 sent by the terminal device.

[0145] Optionally, the first message can be the Lth copy of msg3 sent by the terminal device, where L is an integer greater than 1.

[0146] It should be understood that this first data refers to the data that the terminal device needs to transmit after random access is completed, without using 2-step EDT. Optionally, this data may be user data. Based on 2-step EDT, this first data can be transmitted via msg3.

[0147] The first information used for contention resolution may include the identifier of the terminal device, or parameters regarding the timing of the PUSCH used to send the first message, or a first RNTI. The first RNTI is determined based on the timing of the Physical Uplink Shared Channel (PUSCH) used to send the first message and is used by the network device to scramble msg4.

[0148] S620, the terminal device starts a first timer. The first timer is used to monitor contention resolution messages scrambled by the first wireless network temporary identifier RNTI. The first timer expires after its runtime reaches a first duration.

[0149] It should be understood that the terminal device starts the first timer after sending the first message.

[0150] For example, in a satellite communication scenario, after the terminal device sends the first message, it starts the first timer after a certain period of time. Optionally, this period of time is the round-trip time between the terminal device and the network device, such as UE-gNB RTT.

[0151] It should be understood that the first timer expires after its runtime reaches the first duration, which can be interpreted as: the duration of the first timer's time window is the first duration, or the first timer is closed after its runtime reaches the first duration.

[0152] S630, the terminal device sends N second messages, the second message including the first data and second information for contention resolution, the second information being determined based on the timing of the Physical Uplink Shared Channel (PUSCH) used to send the first message.

[0153] The second information used for contention resolution may include parameters of the timing of sending the first message using the PUSCH, or may include the first RNTI.

[0154] Similar to the first message, the second message is a copy of msg3 during the random access process of the terminal device.

[0155] It should be understood that the terminal device sends the second message N times, that is, the terminal device sends the second message N times in different time slots, that is, sends N copies of msg3.

[0156] S640, when the second message is sent for the i-th time in N times, it is determined that the first timer expires after the runtime reaches the second duration. The second duration is longer than the first duration. The difference between the second duration and the first duration is equal to the duration of the time interval between the i-th time of sending the second message and sending the first message, where i is an integer, i∈[1,N].

[0157] It should be understood that when a terminal device sends N copies of msg3, each copy of msg3 may be received by the network device and a msg4 may be returned, and each msg4 corresponds to an RNTI for scrambling / descrambling. In this application, the msg4 corresponding to the N copies of msg3 are scrambled using the same RNTI, and all are monitored and received through a first timer.

[0158] Optionally, during the i-th transmission of the second message in N transmissions, the duration of the first timer is extended to the second duration.

[0159] For example, the terminal device sends a first message in the first time slot and again in the third time slot, with the first timer lasting for 5 time slots (an example of a first duration). Then, the terminal device sends a second message in the fifth time slot, extending the duration of the first timer to 9 time slots (an example of a second duration). The difference between the second duration and the first duration is 4 time slots, which is equal to the duration of the time interval between sending the first message and sending the second message.

[0160] In addition, if the terminal device still does not receive msg4 after sending the second message N times, it can continue to send the second message and extend the first timer.

[0161] For example, when the terminal device sends the second message for the N+1th time, it can be determined that the first timer expires after the runtime reaches the third duration, the third duration is longer than the second duration, and the difference between the third duration and the second duration is equal to the duration of the time interval between the i-th time of sending the second message and the N+1-th time of sending the second message.

[0162] In the first implementation, the terminal device starts only one timer, namely the first timer. The first message is the first copy of msg3 sent by the terminal device, and the N second messages are the N copies of msg3 sent after the first message.

[0163] It should be understood that the msg4 corresponding to the first message and N second messages are all scrambled / descrambled through the first RNTI and monitored / received through the first timer.

[0164] In the second implementation, the terminal device can start multiple timers, and the maximum number of timers that the terminal device supports running simultaneously is M+1.

[0165] Here, the first message is the Lth copy of msg3 sent by the terminal device, and the Nth second message is the Nth copy of msg3 sent after the first message. Furthermore, after sending the first message and starting the first timer, the number of timers running on the terminal device reaches the maximum supported number. That is, the first timer is the timer with the latest start time currently running. For ease of description, the timer with the earliest start time currently running is referred to as timer a.

[0166] It should be understood that after the terminal device sends the second message for the first time, if the earliest timer currently in operation has not been closed or expired, the terminal device will not start a new timer, but will extend the first timer and carry the second information in the second message.

[0167] It should be understood that in the above N second messages, when the terminal device sends the second message at any time, the number of timers running reaches the maximum supported number, and timer a is the timer with the latest start time. Therefore, when the second message is sent at any time, the terminal device will not start a new timer, but will extend the first timer, and carry the second information in the second message.

[0168] It should be understood that before sending the first message, the terminal device has sent at least one copy of the message and started at least one timer.

[0169] For example, before sending the first message, the terminal device sends M third messages, each including the first data and third information for contention resolution. After each third message is sent, the terminal device starts the corresponding contention resolution timer, thereby monitoring msg4 through the RNTI corresponding to that third message. These M third messages are M copies of msg3 sent before the first message, and the number of timers running on the terminal device has not yet reached the maximum supported number when the third messages are sent.

[0170] For example, when the terminal device sends the third message for the jth time, it starts the jth timer, which is used to monitor the contention resolution message scrambled by the jth RNTI. The jth RNTI is determined according to the timing of the PUSCH used when sending the third message for the jth time. When the third message is sent for the (j+1)th time, it starts the (j+1)th timer, which is used to monitor the contention resolution message scrambled by the (j+1)th RNTI. The (j+1)th RNTI is determined according to the timing of the PUSCH used when sending the third message for the (j+1)th time, where j is an integer and j∈[1, M-1].

[0171] Optionally, the third information includes the identifier of the terminal device, or includes parameters of the timing of the PUSCH used to send the third message, or includes RNTI determined based on the parameters of the timing of the PUSCH used to send the third message.

[0172] For example, the third information included in the j-th third message may include the identifier of the terminal device, or may include parameters of the timing of the PUSCH used to send the j-th third message, or may include RNTI determined based on the parameters of the timing of the PUSCH used to send the j-th third message.

[0173] Optionally, before sending the first message, the terminal device also sends other copies of msg3 besides the aforementioned M third messages.

[0174] Assuming the terminal device receives msg4, it determines the second message based on the number of currently running timers.

[0175] Specifically, if multiple timers are running simultaneously when the terminal device receives msg4, the terminal device can use the corresponding RNTI of the timer in order from earliest to latest to monitor msg4.

[0176] For example, when the terminal device receives msg4, in addition to the first timer, the j-th timer and the (j+1)-th timer are also running. The terminal device first monitors / descrambles msg4 through the j-th RNTI. If monitoring / descrambling msg4 through the j-th RNTI fails, it then monitors / descrambles the contention resolution message through the (j+1)-th RNTI. If monitoring / descrambling msg4 through the (j+1)-th RNTI fails, it then monitors / descrambles the contention resolution message through the first RNTI.

[0177] It should be understood that when a terminal device sends a second message, it needs to first determine the number of timers currently running, and then determine the information carried by the second message.

[0178] For example, before the terminal device sends the second message for the i-th time, it determines the second message based on the number of currently running timers.

[0179] If the number of currently running timers equals the maximum number supported by the terminal device, then the second message is determined to include the second information. In other words, the first timer can continue to be used for monitoring msg4.

[0180] Alternatively, if the number of currently running timers is less than the maximum number supported by the terminal device, then the second message is determined to not include the aforementioned second message, but instead includes fifth information for contention resolution. This fifth information includes the identifier of the terminal device, or parameters regarding the timing of the PUSCH used to send the second message, or a third RNTI determined based on the PUSCH timing used to send the second message. In other words, a new timer can be started for monitoring msg4 via the third RNTI.

[0181] It should be understood that in steps S610 to S640 above, any copy of msg3 sent by the terminal device may be received by the network device.

[0182] Optionally, when a network device receives a first message carrying first information, the network device can distinguish between conflicting terminal devices, or scramble msg4 using a first RNTI and send the scrambled msg4.

[0183] Optionally, when the network device receives a second message carrying second information, the first RNTI can be determined through the second message. Then, the network device can scramble msg4 using the first RNTI and send the scrambled msg4 using the first RNTI.

[0184] Optionally, before step S610, method 600 further includes:

[0185] S650, the network device sends a first indication information to the terminal device, the first indication information being used to indicate the maximum number of time slots or the minimum number of time slots.

[0186] Optionally, the time slots within the maximum number of time slots can be randomly selected by the terminal device to send a message including the first data, or the random number of time slots within the maximum number of time slots can be selected by the terminal as the time interval between two consecutive transmissions of a message including the first data.

[0187] Optionally, the terminal device selects a time interval between two consecutive transmissions of a message including the first data that is greater than or equal to the minimum number of time slots.

[0188] For example, within the maximum number of time slots starting from a specific time slot, the terminal device may randomly select a time slot to send a message including first data, wherein the message including the first data may also be referred to as a contention resolution message. The contention resolution message or the message including the first data includes the aforementioned first message and second message. This specific time slot may be derived by the terminal device or indicated to the terminal device by the network device; there is no limitation on this.

[0189] For example, if the terminal device receives the maximum number of time slots in the first time slot, assuming the maximum number of time slots is 10, then the terminal device randomly selects a time slot from the second to the eleventh time slots to send a message containing the first data. Alternatively, the terminal device randomly selects a time slot from 1 to 10 time slots; for example, if the selected time slot is 6, then for the two transmissions of the message containing the first data, the first transmission occurs in the i-th time slot, and the second transmission occurs in the (i+6)-th time slot.

[0190] Alternatively, a time slot within a maximum number of time slots starting from the current time slot, the next time slot, or a derived starting time slot may be randomly selected by the terminal device to send a message including the first data; or, a time slot within the maximum number of time slots starting from the current time slot, the next time slot, or a derived starting time slot may be randomly selected by the terminal device to send a message for contention resolution.

[0191] Optionally, the maximum number of time slots can be greater than the maximum number of msg3 replicas.

[0192] Optionally, the duration of the maximum number of time slots can be less than the duration of the contention resolution timer.

[0193] Optionally, the duration of the minimum number of time slots can be greater than the duration of the contention resolution timer.

[0194] Optionally, the communication method steps provided in the embodiments of this application may be appropriately adjusted, for example, by adjusting the order of the steps, adding or removing steps, etc. For example, step S650 may be omitted. Any variations that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the protection scope of this application.

[0195] Figure 7 is a schematic flowchart of a communication method 700 provided in this application. Method 700 describes a method for monitoring msg4 using only one timer. It should be understood that method 700 is a specific implementation of method 600, and the concepts or terms in method 700 can be referred to the description in method 600. As shown in Figure 7, method 700 includes the following steps.

[0196] S710 (optional step): The network device sends a maximum number of time slots or a minimum number of time slots (i.e., an example of the first indication information) to the terminal device. The terminal device randomly selects a time slot within the maximum number of time slots to send a copy of msg3, or the terminal device sends two copies of msg3 consecutively at an interval equal to a random number of time slots within the maximum number of time slots, or the terminal device sends two copies of msg3 consecutively at an interval greater than or equal to the minimum number of time slots.

[0197] S720, the terminal device sends the first copy of msg3 (i.e., an example of the first message).

[0198] The first msg3 copy includes first data and first information for race resolution, wherein the description of the first data can be referred to method 600.

[0199] The first information may include the identifier of the terminal device, or a parameter indicating the timing of the PUSCH used to send the first copy of msg3, or a first RNTI. The first RNTI is determined based on the timing of the PUSCH used to send the first copy of msg3 and is used by the network device to scramble msg4.

[0200] S730, the terminal device starts timer 1 (i.e., an example of the first timer).

[0201] The timer 1 is used to monitor msg4 through the first RNTI. The runtime of the timer 1 is a first duration, that is, the timer 1 expires after the runtime reaches the first duration.

[0202] S740, the terminal device sends a second copy of msg3 (i.e., an example of sending the second message for the first time).

[0203] Optionally, the second msg3 copy includes first data and second information for contention resolution, the second information including parameters for the timing of the PUSCH used to send the first msg3 copy, or including the first RNTI.

[0204] It should be understood that the msg4 corresponding to the second msg3 copy is also scrambled through the first RNTI and monitored through timer 1.

[0205] S750, the terminal device extends the duration of timer 1 to a second duration, the second duration being longer than the first duration, and the difference between the second duration and the first duration being equal to the duration of the time interval between sending the first copy of msg3 and sending the second copy of msg3.

[0206] S760 (optional step): The terminal device sends a third copy of msg3 (i.e., an example of sending the second message for the second time).

[0207] Optionally, the third msg3 copy includes the first data and the second information for race resolution.

[0208] It should be understood that the msg4 corresponding to the third msg3 copy is also scrambled through the first RNTI and monitored through timer 1.

[0209] Optionally, the terminal device extends the duration of timer 1 to a third duration, the third duration being longer than the second duration, and the difference between the third duration and the second duration being equal to the duration of the time interval between sending the second msg3 copy and sending the third msg3 copy.

[0210] Optionally, the terminal device may continue to send a copy of msg3, extend the duration of timer 1, and monitor msg4 through timer 1.

[0211] Optionally, upon receiving msg4, the terminal device may stop sending copies of msg3 and stop monitoring msg4.

[0212] It should be understood that when the network device receives a copy of msg3, if the received copy of msg3 is the first copy of msg3 sent by the aforementioned terminal device, the network device determines the first RNTI based on the parameters of the PUSCH timing used to send the first copy of msg3, and scrambles msg4 using the first RNTI before sending it to the terminal device.

[0213] Alternatively, if the msg3 copy received by the network device is the second msg3 copy or a subsequent msg3 copy sent by the terminal device, the network device determines the first RNTI by the second information carried in the received msg3 copy, and scrambles msg4 with the first RNTI before sending it to the terminal device.

[0214] Figure 8 is a schematic flowchart of a communication method 800 provided in this application. Method 800 describes a method for monitoring msg4 using multiple timers. It should be understood that method 800 is a specific implementation of method 600, and the concepts or terms in method 800 can be referred to the description in method 600. As shown in Figure 8, method 800 includes the following steps.

[0215] S810 (optional step): The network device sends a maximum number of time slots (i.e., an example of the first indication information) to the terminal device, which randomly selects time slots within the maximum number of time slots to send a copy of msg3.

[0216] In S820, the terminal device sends multiple copies of msg3 and starts the corresponding timer for each.

[0217] For example, the terminal device sends the Lth copy of msg3 and starts the corresponding timer L0 to monitor msg4. This timer L0 is used to monitor msg4 by the RNTI corresponding to the PUSCH timing parameter used to send the Lth copy of msg3. The runtime of this timer L0 is a first duration, that is, timer L0 expires after the runtime reaches the first duration.

[0218] Assuming that after the terminal device starts timer L0, the number of timers running reaches the maximum number M supported by the terminal device (for ease of understanding and description, M = 3 is assumed in the following text), then the Lth copy of msg3 is an example of the first message of this application.

[0219] The Lth msg3 copy includes first data and first information for contention resolution, wherein the description of the first data can be referred to method 600. The first information may include an identifier of the terminal device, or a parameter indicating the timing of the PUSCH used to send the Lth msg3 copy, or a first RNTI. The first RNTI is determined based on the timing of the PUSCH used to send the Lth msg3 copy and is used by the network device to scramble msg4.

[0220] In addition, before the terminal device sends the Lth msg3 copy, it also sends the (L-1)th msg3 copy and the (L-2)th msg3 copy (i.e., an example of the M third messages, where M=2). The (L-1)th msg3 copy corresponds to timer L1, and the (L-2)th msg3 copy corresponds to timer L2. It should be understood that after the terminal device sends the Lth msg3 copy, the number of timers in the terminal device's line reaches the maximum number supported by the terminal device.

[0221] It should be understood that the terminal device may have sent the (L-3)th msg3 copy before sending the (L-2)th msg3 copy, and the timer corresponding to the (L-3)th msg3 copy has expired.

[0222] It should be understood that timer L0 is used to monitor msg4 by the RNTI corresponding to the parameters of the PUSCH timing used when sending the Lth msg3 copy, timer L1 is used to monitor msg4 by the RNTI corresponding to the parameters of the PUSCH timing used when sending the (L-1)th msg3 copy, and timer L2 is used to monitor msg4 by the RNTI corresponding to the parameters of the PUSCH timing used when sending the (L-2)th msg3 copy.

[0223] Optionally, if a msg4 is received while timers L0, L1, and L2 are all running, the msg4 can be monitored in ascending order according to the timers' start times. For example, monitoring can be performed first using the RNTI corresponding to timer L2; if that fails, monitoring can then be performed using the RNTI corresponding to timer L1; if that still fails, monitoring can then be performed using the RNTI corresponding to timer L0.

[0224] S830, the terminal device sends the L+1th copy of msg3 (i.e., an example of sending the second message for the first time).

[0225] When the terminal device sends the (L+1)th copy of msg3, since the number of currently running timers has reached the maximum number supported by the terminal device, the terminal device will not start the timer again after sending the (L+1)th copy, but will extend the duration of timer L0.

[0226] Optionally, the (L+1)th msg3 copy includes first data and second information for contention resolution, the second information including parameters for the timing of the PUSCH used to send the Lth msg3 copy, or including the first RNTI.

[0227] It should be understood that the msg4 corresponding to the L+1th msg3 copy is also scrambled through the first RNTI and monitored through timer L0.

[0228] S840, the terminal device extends the duration of timer L0 to a second duration, the second duration being longer than the first duration, and the difference between the second duration and the first duration being equal to the duration of the time interval between sending the Lth msg3 copy and sending the L+1th msg3 copy.

[0229] S850 (optional step): The terminal device sends the L+2th copy of msg3 (i.e., an example of sending the second message for the second time).

[0230] Optionally, the L+2th msg3 copy includes the first data and the second information for race resolution.

[0231] It should be understood that the msg4 corresponding to the L+2th msg3 copy is also scrambled through the first RNTI and monitored through timer L0.

[0232] Optionally, the terminal device extends the duration of timer L0 to a third duration, the third duration being longer than the second duration, and the difference between the third duration and the second duration being equal to the duration of the time interval between sending the (L+2)th msg3 copy and sending the (L+1)th msg3 copy.

[0233] Optionally, the terminal device can continue to send a copy of msg3, extend the duration of timer L0, and monitor msg4 through timer L0.

[0234] Optionally, upon receiving msg4, the terminal device may stop sending copies of msg3 and stop monitoring msg4.

[0235] It should be understood that when the network device receives a copy of msg3, if the received copy of msg3 is the Lth copy of msg3 sent by the aforementioned terminal device, the network device determines the first RNTI based on the parameters of the PUSCH timing used to send the Lth copy of msg3, and scrambles msg4 using the first RNTI before sending it to the terminal device.

[0236] Alternatively, if the msg3 copy received by the network device is the L+1th msg3 copy sent by the terminal device or a subsequent msg3 copy, the network device determines the first RNTI by the second information carried in the received msg3 copy, and scrambles msg4 with the first RNTI before sending it to the terminal device.

[0237] It should be understood that the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0238] It should also be understood that, in the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0239] The above is a detailed description of the communication method provided in this application. The following describes the communication device provided in this application.

[0240] In order to realize the functions of the communication device (e.g., terminal device or network device) in the embodiments of this application, the communication device can implement the corresponding functions in the form of hardware and / or software.

[0241] Figure 9 is a schematic structural diagram of a communication device provided in this application. As shown in Figure 9, the communication device 1000 includes a processing module 1001 and a communication module 1002. The communication device 1000 can be a communication device, or a device applied to a communication device and capable of realizing the corresponding functions of the communication device, such as a chip, processor, or circuit. Exemplarily, the communication device can be a terminal device or a network device, as in the method embodiment.

[0242] The communication module can also be a transceiver module, transceiver, transceiver device, or transceiver unit. The processing module can also be a processor, processing board, processing unit, or processing device. Optionally, the communication module is used to execute the sending or receiving operations of the terminal device or network device in any of the method embodiments. The device in the communication module that implements the receiving function can be considered a receiving unit, and the device in the communication module that implements the sending function can be considered a sending unit; that is, the communication module includes a receiving unit and a sending unit. The processing module is used to execute the internal implementation-related operations / processing of the terminal device or network device in any of the method embodiments. The specific operations of each module can be found in the descriptions in the method embodiments and will not be repeated here.

[0243] Alternatively, the communication module and / or processing module can be implemented as virtual modules. For example, the processing module can be implemented as a software functional unit or a virtual device, and the communication module can be implemented as a software function or a virtual device. Alternatively, the processing module or communication module can also be implemented as a physical device. For example, the communication device can be a chip, such as a system-on-chip (SoC), hardware circuitry, etc. The communication module can be an input / output circuit and / or a communication interface, performing input operations (corresponding to the aforementioned receiving operation) and output operations (corresponding to the aforementioned sending operation); the processing module can be an integrated circuit or logic circuit, etc.

[0244] The module division in this application is illustrative and represents only one logical functional division. In actual implementation, other division methods are possible. Furthermore, the functional modules in the various examples of this application can be integrated into one module, exist as separate physical entities, or be integrated into one module. The integrated modules described above can be implemented in hardware, as software functional modules, or as a combination of hardware and software functional modules; no limitation is imposed.

[0245] Figure 10 is a schematic structural diagram of another communication device provided in this application. The communication device 1100 can be used to implement the functions of any communication device (e.g., a terminal device or a network device) in the communication system described in the foregoing examples. Optionally, the communication device 1100 can be a chip or a chip system. Optionally, in this application, the chip system can be composed of chips or may include chips and other discrete devices. The communication device 1100 may include at least one processor 1110. Optionally, the processor 1110 (or processing device) is coupled to a memory, which may be located within the communication device, or the memory may be integrated with the processor, or the memory may be located outside the communication device. For example, the communication device 1100 may also include at least one memory 1120. The memory 1120 stores computer programs / instructions or data necessary for implementing any of the above method embodiments; the processor 1110 may execute the computer programs / instructions or data stored in the memory 1120 to complete the corresponding functions of the terminal device or mobility management network element in any of the above embodiments.

[0246] Optionally, the communication device 1100 may further include a communication interface 1130, through which the communication device 1100 can interact with other devices. For example, the communication interface 1130 may be a transceiver, circuit, bus, module, pin, or other type of communication interface. When the communication device 1100 is a chip-type device or circuit, the communication interface 1130 in the device 1100 may also be an input / output circuit, capable of inputting information (or receiving information) and / or outputting information (or sending information). The processor may be an integrated circuit or logic circuit, etc., and the processor can determine the output information based on the input information.

[0247] The coupling in this application refers to indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, used for information exchange between devices, units, or modules. The processor 1110 may operate in conjunction with the memory 1120 and the communication interface 1130. This application does not limit the connection medium between the processor 1110, the memory 1120, and the communication interface 1130.

[0248] Optionally, as shown in FIG10, the processor 1110, the memory 1120, and the communication interface 1130 are interconnected via a bus 1140. The bus 1140 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one line is used to represent the bus 1140 in FIG10, but this does not indicate that there is only one bus or one type of bus.

[0249] Figure 11 is a schematic structural diagram of the chip provided in this application. The chip 30 includes a circuit 31 and a communication interface 32. The circuit 31 can be a logic circuit, integrated circuit, etc., and the communication interface 32 can also be called an input / output circuit, input / output interface, interface circuit, etc., which can input information (or receive information) or output information (or send information). The chip 30 can execute the methods executed by the terminal device or network device in the various embodiments of this application.

[0250] In addition, this application also provides a computer-readable storage medium storing computer instructions, which, when executed on a computer, cause operations and / or processes performed by a terminal device or network device in the various method embodiments of this application to be executed.

[0251] This application also provides a computer program product, which includes computer program code or instructions. When the computer program code or instructions are run on a computer, the operations and / or processes performed by a terminal device or network device in the various method embodiments of this application are executed.

[0252] Furthermore, this application also provides a chip including a processor. A memory for storing a computer program is provided independently of the chip, and the processor is used to execute the computer program stored in the memory, so that operations and / or processes performed by a terminal device or network device in any method embodiment are executed. Further, the chip may also include a communication interface. The communication interface may be an input / output interface or an interface circuit, etc. Further, the chip may also include the memory.

[0253] This application provides a communication system, including the terminal device and network device in the above method embodiments.

[0254] The processor in this application embodiment has signal processing capabilities and can be a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., capable of implementing or executing the methods, steps, and logic block diagrams disclosed in this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in this application can be directly manifested as being executed by the hardware processor, or executed by a combination of hardware and software modules within the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory; the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above methods.

[0255] In the embodiments of this application, the memory can be volatile memory or non-volatile memory, or it can include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0256] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0257] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0258] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units 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 apparatuses or units may be electrical, mechanical, or other forms.

[0259] The units described 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.

[0260] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0261] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0262] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, Applied to terminal devices, including: Send a first message, the first message including first data and first information for resolving the contention; Start a first timer, which is used to monitor contention resolution messages scrambled by the first radio network temporary identifier (RNTI). The first RNTI is determined based on the timing of sending the first message using the physical uplink shared channel (PUSCH). The first timer expires after its runtime reaches a first duration. Send N second messages, the second message including the first data and second information for contention resolution, the second information being determined based on the timing of the Physical Uplink Shared Channel (PUSCH) used to send the first message; When the second message is sent for the i-th time, it is determined that the first timer expires after the runtime reaches the second duration. The second duration is longer than the first duration. The difference between the second duration and the first duration is equal to the duration of the time interval between the i-th time of sending the second message and sending the first message, where i is an integer, i∈[1,N].

2. The method according to claim 1, characterized in that, The method further includes: When the second message is sent for the (N+1)th time, it is determined that the first timer expires after the runtime reaches the third duration, the third duration is longer than the second duration, and the difference between the third duration and the second duration is equal to the duration of the time interval between the i-th and N+1-th times the second message is sent.

3. The method according to claim 1 or 2, characterized in that, The first information includes the identifier of the terminal device, or, includes parameters of the timing of the PUSCH used to send the first message, or includes the first RNTI.

4. The method according to any one of claims 1 to 3, characterized in that, The second information includes parameters regarding the timing of the PUSCH used to send the first message, or it includes the first RNTI.

5. The method according to any one of claims 1 to 4, characterized in that, Before sending the first message, the method further includes: Send M third messages, each third message including the first data and third information for contention resolution; When the third message is sent for the jth time, the jth timer is started. The jth timer is used to monitor the contention resolution message scrambled by the jth RNTI. The jth RNTI is determined based on the timing of the PUSCH used when the third message is sent for the jth time. When the third message is sent for the (j+1)th time, the (j+1)th timer is started. The (j+1)th timer is used to monitor the contention resolution message scrambled by the (j+1)th RNTI. The (j+1)th RNTI is determined according to the timing of the PUSCH used to send the third message for the (j+1)th time, where j is an integer and j∈[1, M-1].

6. The method according to claim 5, characterized in that, When a race-resolved message is received, if both the j-th timer and the (j+1)-th timer are running, then The method further includes: The contention resolution message is monitored via the j-th RNTI; or... If monitoring the contention resolution message using the j-th RNTI fails, then monitoring the contention resolution message using the (j+1)-th RNTI is performed.

7. The method according to any one of claims 1 to 4, characterized in that, Before sending the first message, the method further includes: Send a third message, the third message including the first data and third information for contention resolution; A second timer is started to monitor contention resolution messages scrambled by a second RNTI, which is determined based on the timing of the PUSCH used to send the third message.

8. The method according to claim 7, characterized in that, When a race-resolved message is received, if both the first timer and the second timer are running, then The method further includes: The contention resolution message is monitored via the second RNTI; or... If monitoring the contention resolution message using the second RNTI fails, then monitoring the contention resolution message using the first RNTI is performed.

9. The method according to any one of claims 5 to 8, characterized in that, The third information includes the identifier of the terminal device, or includes parameters of the timing of the PUSCH used to send the third message, or includes the RNTI determined based on the parameters of the timing of the PUSCH used to send the third message.

10. The method according to any one of claims 1 to 9, characterized in that, Before the i-th transmission of the second message, the method further includes: The second message is determined based on the number of timers currently running.

11. The method according to claim 10, characterized in that, Determining the second message based on the number of currently running timers includes: If the number of currently running timers is equal to the maximum number supported by the terminal device, then the second message is determined to include the second information.

12. The method according to any one of claims 1 to 11, characterized in that, The method further includes: The terminal device receives a first indication message, which indicates a maximum number of time slots. The time slots within the maximum number of time slots can be randomly selected by the terminal device to send a message including the first data, or the random number of time slots within the maximum number of time slots can be selected by the terminal device as the time interval between two consecutive messages including the first data. The message including the first data includes the first message and the second message.

13. A communication method, characterized in that, Applied to network devices, including: Receive at least one of a first message and N second messages from a terminal device, wherein the first message includes first data and first information for contention resolution, and the second message includes first data and second information for contention resolution, wherein the second information is determined based on the timing of the Physical Uplink Shared Channel (PUSCH) used to send the first message; Send a contention resolution message scrambled with a first Radio Network Temporary Identifier (RNTI), the first RNTI being determined based on the timing of sending the first message using the Physical Uplink Shared Channel (PUSCH).

14. The method according to claim 13, characterized in that, The first information includes the identifier of the terminal device, or, includes parameters of the timing of the PUSCH used to send the first message, or includes the first RNTI.

15. The method according to claim 13 or 14, characterized in that, The second information includes parameters regarding the timing of the PUSCH used to send the first message, or it includes the first RNTI.

16. The method according to any one of claims 13 to 15, characterized in that, The method further includes: Send a first indication message, which indicates the maximum number of time slots. The time slots within the maximum number of time slots can be randomly selected by the terminal device to send a message including the first data, or the random number of time slots within the maximum number of time slots can be selected by the terminal device as the time interval between two consecutive messages including the first data. The message including the first data includes the first message and the second message.

17. A communication device, characterized in that, The device includes one or more processors, which are configured to execute a computer program or instructions stored in a memory, causing the device to perform the method of any one of claims 1 to 12, or to perform the method of any one of claims 13 to 16.

18. A chip or chip system, characterized in that, The device includes a processor coupled to a memory for storing a computer program, and the processor for executing the computer program stored in the memory to implement the method as described in any one of claims 1 to 16.

19. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions, which, when executed by a communication device, implement the method as described in any one of claims 1 to 16.

20. A computer program product, characterized in that, Includes a computer program that, when run, implements the method as described in any one of claims 1 to 16.

Images