Communication method and communication apparatus

Abstract

Provided in the embodiments of the present application are a communication method and a communication apparatus. According to the present application, after sending an uplink message by means of an uplink resource indicated by first uplink resource configuration information, a terminal device can determine whether the uplink message has failed to be sent. Furthermore, if the terminal device determines that the uplink message has failed to be sent, the terminal device retransmits the uplink message after a first backoff time is delayed, thereby facilitating the retransmission success of the terminal device after an uplink transmission failure.

Description

Communication methods and communication devices

[0001] This application claims priority to Chinese Patent Application No. 202410571981.9, filed on May 9, 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] One possible uplink transmission method is as follows: User equipment (UE) performs uplink transmission based on common uplink resources. For example, when the UE performs mobile terminated early data transmission (MO-EDT) without physical random access (PRACH), the UE transmits uplink data based on common uplink resources; PRACH-free MO-EDT can also be called PRACH-free EDT. Another example is that the UE uses contention-based preconfigured uplink resources (PUR) for uplink transmission; contention-based PUR can also be called contention-based PUR.

[0004] However, when a UE performs uplink transmission based on public uplink resources or using contention-based PUR resources, uplink conflicts are likely to occur, leading to uplink transmission failure. Summary of the Invention

[0005] This application provides a communication method and a communication device that enables a terminal device to back off when it determines that the uplink transmission has failed, thereby facilitating successful retransmission after the uplink transmission fails.

[0006] Firstly, a communication method is provided. This method can be applied to the terminal side; that is, it can be executed by the terminal device or by components of the terminal device (such as a chip, chip system, circuit, or communication module). This application does not limit the scope of the method. The following description mainly uses a terminal device as an example.

[0007] The method includes: receiving first uplink resource configuration information; sending an uplink message through the uplink resource indicated by the first uplink resource configuration information; determining that the uplink message transmission failed; and retransmitting the uplink message after a first backoff time.

[0008] Based on the above technical solution, during uplink transmission using shared resources (such as public uplink resources or contention-based PUR resources), the terminal device can determine uplink transmission failure and retransmit after backoff, thereby improving the retransmission success rate. For example, when terminal device #1 and terminal device #2 send uplink messages through uplink resource #1, uplink transmission failure occurs due to uplink conflict (i.e., the uplink messages sent by terminal device #1 and terminal device #2 interfere with each other). Then, after backoff, terminal device #1 retransmits the uplink message on uplink resource #2, and terminal device #2 retransmits the uplink message on uplink resource #3. Since uplink resource #2 and uplink resource #3 are different, both terminal device #1 and terminal device #2 can successfully retransmit.

[0009] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: starting a window or timer after sending an uplink message; determining that the uplink message transmission failed, including: determining that the uplink message transmission failed in the event of at least one of the following events: event 1, the window or timer expires and no downlink message is received; or, event 2, the window or timer expires and a downlink message is received before the window or timer expires, the downlink message is not scrambled with a first radio network temporary identifier (RNTI), the first RNTI is determined according to the uplink resource indicated by the first uplink resource configuration information, or the first RNTI is a common RNTI; or, event 3, the window or timer expires and a downlink message is received before the window or timer expires, the identifier of the terminal device included in the downlink message does not match the identifier of the terminal device included in the uplink message; or, event 4, downlink control information (DCI) is received before the window or timer expires, the DCI being used to indicate that the uplink message transmission failed.

[0010] Optionally, the DCI is scrambled using the first RNTI, and the DCI includes third uplink resource configuration information.

[0011] Based on the above technical solution, if the terminal device determines that the uplink message transmission has failed based on any of events 1 to 3, the terminal device can still determine that the uplink message transmission has failed even if the network device does not indicate uplink transmission failure or retransmission to the terminal device, thereby facilitating the triggering of uplink message retransmission. Furthermore, since it is not necessary for the network device to indicate uplink transmission failure or retransmission to the terminal device, the downlink signaling overhead of the network device can be reduced.

[0012] It should also be understood that, compared to the scheme of determining uplink message transmission failure based on the occurrence of any of events 1 to 3, if the terminal device determines uplink message transmission failure based on the occurrence of event 4, the terminal device can determine uplink message transmission failure before the window or timer expires. This is conducive to triggering uplink message retransmission as soon as possible, reducing retransmission latency, and saving power consumption of the terminal device.

[0013] In conjunction with the first aspect, in some implementations of the first aspect, retransmitting uplink messages includes: retransmitting uplink messages via uplink resources indicated by the first uplink resource configuration information.

[0014] It should be noted that if, in the event of event 4, the terminal device determines that the uplink message transmission has failed, and the DCI includes third uplink resource configuration information, then after the first backoff time, the terminal device will still use the uplink resources indicated by the first uplink resource configuration information to retransmit the uplink message. In other words, the terminal device ignores the third uplink resource configuration information included in the DCI. It can be understood that by using the uplink resources indicated by the first uplink resource configuration information to retransmit the uplink message after backoff, instead of using the uplink resources indicated by the third uplink resource configuration information, the terminal device can avoid retransmission failure caused by multiple terminal devices simultaneously using the uplink resources indicated by the third uplink resource configuration information to retransmit the uplink message.

[0015] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: receiving second uplink resource configuration information; retransmitting uplink messages, including: retransmitting uplink messages through uplink resources indicated by the second uplink resource configuration information.

[0016] It should be noted that if, in the event of event 4, the terminal device determines that the uplink message transmission has failed, and the DCI includes third uplink resource configuration information, then after the first backoff time, the terminal device will still use the uplink resources indicated by the second uplink resource configuration information to retransmit the uplink message. In other words, the terminal device ignores the third uplink resource configuration information included in the DCI. It can be understood that by using the uplink resources indicated by the first uplink resource configuration information to retransmit the uplink message after backoff, instead of using the uplink resources indicated by the third uplink resource configuration information, the terminal device can avoid retransmission failure caused by multiple terminal devices simultaneously using the uplink resources indicated by the third uplink resource configuration information to retransmit the uplink message.

[0017] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: receiving backoff time parameter information, the backoff time parameter information being used to determine a first backoff time, the backoff time parameter information including one or more of the following: a second backoff time, an index of the second backoff time; and randomly selecting a first backoff time between 0 and the second backoff time.

[0018] Based on the above technical solution, the terminal device can determine the first backoff time based on the received backoff time parameter information. Furthermore, the terminal device randomly selects the first backoff time between 0 and the second backoff time, which facilitates different terminal devices randomly selecting different first backoff times. When different terminal devices randomly select different first backoff times, they will retransmit on different uplink resources, thus increasing the chances of successful retransmission.

[0019] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: receiving indication information, the indication information being used to indicate backoff in the event of uplink transmission failure.

[0020] Based on the above technical solution, the terminal device can determine whether to back off in the event of uplink transmission failure before retransmitting uplink, thereby avoiding retransmission failure when retransmitting uplink immediately after uplink transmission failure.

[0021] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: receiving a public RNTI.

[0022] Based on the above technical solution, the terminal device can monitor the physical downlink control channel (PDCCH) based on the common RNTI, and thus determine whether an uplink transmission failure has occurred based on whether the PDCCH scrambled by the common RNTI is detected.

[0023] Secondly, a communication method is provided. This method can be applied to the network side; that is, it can be executed by a network device or by a component of the network device (such as a chip, chip system, circuit, or communication module). This application does not limit the scope of the method. The following description mainly uses a network device as an example.

[0024] The method includes: sending first uplink resource configuration information; receiving uplink messages through uplink resources indicated by the first uplink resource configuration information; and sending downlink messages and / or DCI, wherein the downlink messages or DCI are used to determine that the uplink message transmission failed.

[0025] For the beneficial effects and possible designs of the second aspect, please refer to the relevant description in the first aspect, which will not be repeated here.

[0026] In conjunction with the second aspect, in some implementations of the second aspect, the downlink message is not scrambled with the first RNTI. The first RNTI is determined based on the uplink resources indicated by the first uplink resource configuration information, or the first RNTI is a common RNTI, or the identifier of the terminal device included in the downlink message does not match the identifier of the terminal device included in the uplink message. The DCI is used to indicate uplink message transmission failure.

[0027] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: sending backoff time parameter information, the backoff time parameter information being used to determine a first backoff time, the backoff time parameter information including one or more of the following: a second backoff time, an index of the second backoff time; the first backoff time being between 0 and the second backoff time.

[0028] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: sending indication information, which is used to indicate backoff in the event of uplink transmission failure.

[0029] In conjunction with the second aspect, in some implementations of the second aspect, the DCI is scrambled by a first RNTI, which is determined based on the uplink resources indicated by the first uplink resource configuration information, or the first RNTI is a common RNTI, and the DCI contains the third uplink resource allocation information.

[0030] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: sending a public RNTI.

[0031] Thirdly, a communication apparatus is provided for performing the method in any of the possible implementations of the first to second aspects described above. Specifically, the apparatus may include units and / or modules for performing the method in any of the possible implementations of the first to second aspects, such as processing units and / or communication units.

[0032] In one implementation, the device is a communication device (such as a terminal device or a network device). When the device is a communication device, the communication unit can be a transceiver or an input / output interface; the processing unit can be at least one processor. Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0033] In another implementation, the device is a chip, chip system, circuit, or communication module for communication equipment (such as terminal equipment or network equipment). When the device is a chip, chip system, or circuit for communication equipment, the communication unit can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; the processing unit can be at least one processor, processing circuit, or logic circuit.

[0034] Fourthly, a communication device is provided, comprising: at least one processor for executing a computer program or instructions to perform the method in any of the possible implementations of the first to second aspects described above. Optionally, the device further comprises a memory for storing the computer program or instructions. Optionally, the device further comprises a communication interface coupled to the processor, which can be used to input the computer program or instructions to the processor or to output information from the processor.

[0035] In one implementation, the device is a communication device (such as a terminal device or a network device).

[0036] In another implementation, the device is a chip, chip system, circuit, or communication module for communication equipment (such as terminal equipment or network equipment).

[0037] Fifthly, a processor is provided for performing the method provided in any one of the first to second aspects described above.

[0038] Unless otherwise specified, or if it does not contradict its actual function or internal logic in the relevant description, the transmission and acquisition / reception operations involved in the processor can be understood as processor output and reception, input and other operations, or as transmission and reception operations performed by radio frequency circuits and antennas. This application does not limit them in this regard.

[0039] Optionally, the device further includes: a memory for storing a program; correspondingly, at least one processor for executing the computer program or instructions in the memory.

[0040] Optionally, the device also includes a communication interface. The communication interface is coupled to the processor and can be used to input information to the processor or output information from the processor.

[0041] A sixth aspect provides a computer-readable storage medium storing program code for execution by a device, the program code including methods for performing any of the possible implementations of the first to second aspects described above.

[0042] In a seventh aspect, a computer program product containing instructions is provided, which, when run on a computer, causes the computer to perform the method in any of the possible implementations of the first to second aspects described above.

[0043] Eighthly, a chip is provided, the chip including a processor and a communication interface, the processor reading instructions from a memory through the communication interface and executing the method provided by any of the above implementations of the first to second aspects.

[0044] Optionally, the chip is 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.

[0045] Optionally, as one implementation, the chip further includes a memory storing computer programs or instructions, and a processor for executing the computer programs or instructions in the memory. When the computer programs or instructions are executed, the processor is used to perform the method provided by any of the above implementations of the first to second aspects.

[0046] Ninth aspect, a computer program product containing instructions is provided, which, when run on a computer, causes the computer to perform the method provided by any of the above implementations of the first to second aspects.

[0047] In a tenth aspect, a communication system is provided, including the aforementioned terminal equipment and network equipment. Attached Figure Description

[0048] Figure 1 shows a schematic diagram of a network architecture applicable to embodiments of this application.

[0049] Figure 2 shows a schematic diagram of an architecture of a communication system applicable to embodiments of this application.

[0050] Figure 3 shows a schematic diagram of a quasi-fixed cell.

[0051] Figure 4 shows a schematic diagram of a mobile cell.

[0052] Figure 5 illustrates the interaction between the UE and the access network equipment during the MO-EDT process initiated by the UE.

[0053] Figure 6 illustrates the interaction between the UE and the access network device during a UE-based PUR transmission.

[0054] Figure 7 shows a schematic flowchart of the communication method provided in an embodiment of this application.

[0055] Figure 8 shows a schematic flowchart of the communication method provided in an embodiment of this application.

[0056] Figure 9 is a schematic diagram of a communication device 1200 provided in an embodiment of this application.

[0057] Figure 10 is a schematic diagram of another communication device 1300 provided in an embodiment of this application.

[0058] Figure 11 is a schematic diagram of a chip system 1400 provided in an embodiment of this application. Detailed Implementation

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

[0060] The technical solutions provided in this application can be applied to various communication systems, such as: 5th generation (5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, wireless local area network (WLAN) systems, satellite communication systems, future communication systems, or integrated systems of multiple systems. The technical solutions provided in this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems.

[0061] The technical solutions provided in this application can also be applied to non-terrestrial network (NTN) systems such as inter-satellite communication and satellite communication. As an example, a satellite communication system includes a satellite base station and terminal equipment. The satellite base station provides communication services to the terminal equipment. The satellite base station can also communicate with other base stations. A satellite can act as a base station or as a terminal device. Here, "satellite" can refer to unmanned aerial vehicles (UAVs), hot air balloons, low-Earth orbit (LEO) satellites, medium-Earth orbit (MEO) satellites, high-Earth orbit (HEO) satellites, etc. "Satellite" can also refer to non-terrestrial base stations or non-terrestrial equipment, etc.

[0062] In a communication system, a device can send signals to or receive signals from another device. These signals can include information, signaling, or data. The term "device" can be replaced by an entity, network entity, communication device, mobile device, network element, communication module, node, communication node, communication apparatus, etc. This disclosure uses a device as an example. For instance, a communication system can include at least one terminal device and at least one network device. The network device can send downlink signals to the terminal device, and / or the terminal device can send uplink signals to the network device. It is understood that the terminal device in this disclosure can be replaced by a first communication device, and the network device can be replaced by a second communication device, both performing the corresponding communication methods described in this disclosure. Alternatively, the corresponding communication methods in this disclosure can be applied between network devices or between terminal devices, without limitation herein.

[0063] The terminal device in this application embodiment can be a device or module that accesses the aforementioned communication system and has corresponding communication functions. The terminal device can include various devices with wireless communication capabilities, which can be used to connect people, objects, machines, etc. The terminal device can be widely applied in various scenarios, such as: cellular communication, D2D, V2X, peer-to-peer, M2M, MTC, IoT, virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery, etc. The terminal device can be a terminal in any of the above scenarios, such as an MTC terminal, an IoT terminal, etc. Terminal equipment can be user equipment, terminals, fixed equipment, mobile station equipment or mobile devices, subscriber units, handheld devices, vehicle-mounted equipment, wearable devices, cellular phones, smartphones, session initiation protocol (SIP) phones, wireless data cards, personal digital assistants (PDAs), computers, tablets, laptops, wireless modems, handsets, laptop computers, computers with wireless transceiver capabilities, smart books, vehicles, satellites, global positioning system (GPS) devices, target tracking devices, aircraft (e.g., drones, helicopters, multiple helicopters, four helicopters, or airplanes), ships, remote control devices, smart home devices, industrial equipment, transportation vehicles with wireless communication capabilities, communication modules, and roadside units with terminal functions, all conforming to the 3GPP standard. The terminal device (RSU) can be a unit or a device built into the aforementioned equipment (e.g., a communication module, modem, or chip in the aforementioned equipment), or other processing devices connected to a wireless modem. For ease of description, the terminal device will be described below as a terminal or UE.

[0064] It should be understood that in certain scenarios, a UE can also be used as a base station. For example, a UE can act as a scheduling entity, providing sidelink signaling between UEs in scenarios such as V2X, D2D, or end-to-end.

[0065] In this embodiment, the device for implementing the functions of the terminal device can be the terminal device itself, or it can be any device capable of supporting the terminal device in implementing those functions, such as a chip system. This device can be installed in or used in conjunction with the terminal device. In this embodiment, the chip system can be composed of chips or may include chips and other discrete components. This embodiment only uses the terminal device as an example to illustrate the device for implementing the functions of the terminal device, and does not constitute a limitation on the solution of this embodiment.

[0066] The network device in this application embodiment can be a device or module with corresponding communication functions. The network device can be a device used to communicate with terminal devices; it can also be called an access network device or a wireless access network device, such as a base station. In this application embodiment, the network device can refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitter point, master station, auxiliary station, motor slide retainer (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or a combination thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, a device that performs base station functions in D2D, V2X, and M2M communications, or a device that performs base station functions in future communication systems. A base station can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

[0067] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0068] In some deployments, the network devices mentioned in the embodiments of this application may be devices including CU, DU, or CU and DU, or devices with control plane CU nodes (central unit-control plane (CU-CP)) and user plane CU nodes (central unit-user plane (CU-UP)) and DU nodes. For example, the network devices may include gNB-CU-CP, gNB-CU-UP, and gNB-DU.

[0069] In some deployments, multiple RAN nodes collaborate to assist terminals in achieving wireless access, with different RAN nodes each implementing some of the base station's functions. For example, RAN nodes can be CUs, DUs, CU-CPs, CU-UPs, or radio units (RUs). CUs and DUs can be configured separately or included in the same network element, such as a BBU. RUs can be included in radio equipment or radio units, such as RRUs, AAUs, or RRHs.

[0070] In some deployments, the CU (Core Unit) is a logical node that carries the Radio Resource Control (RRC) layer, Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, and other control functions of the access network equipment. The CU connects to network nodes such as the core network through interfaces, which may be E2 interfaces, etc. Optionally, the CU possesses some core network functions. The CU (e.g., the PDCP layer and higher layers) connects to the DU (e.g., the Radio Link Control (RLC) layer and lower layers) through interfaces, which may be F1 interfaces, etc. In some examples, these interfaces (e.g., the F1 interface) can provide control plane (C-Plane) and user plane (U-Plane) functions (e.g., interface management, system information management, UE context management, RRC message transmission, etc.). The F1 application protocol (F1AP) is the application protocol for the F1 interface, and in some examples, it defines the F1 signaling procedures. The F1 interface supports both the control plane (F1-C) and the user plane (F1-U).

[0071] In some deployments, the CU can be split into CU-CP and CU-UP. CU-CP is a logical node carrying the RRC layer and the control plane part of PDCP (PDCP-C) layer, used to implement the CU's control plane functions. CU-CP can interact with network elements in the core network used to implement control plane functions. These network elements in the core network can be access and mobility function network elements. CU-UP is a logical node carrying the SDAP layer and the user plane part of PDCP (PDCP-U) layer, used to implement the CU's user plane functions. CU-UP can interact with network elements in the core network used to implement user plane functions. The above CU and DU configurations are merely examples; the functions of CU and DU can be configured as needed. For example, CU or DU can be configured to have more protocol layer functions, or CU or DU can be configured to have only partial protocol layer processing functions. For example, some functions of the RLC layer and the functions of the protocol layer above the RLC layer can be placed in the CU, while the remaining functions of the RLC layer and the functions of the protocol layer below the RLC layer can be placed in the DU. Another example is that the functions of the CU or DU can be divided according to service type or other system requirements. For instance, based on latency, functions that need to meet low latency requirements can be placed in the DU, while functions that do not need to meet such latency requirements can be placed in the CU.

[0072] In some deployments, the DU (Distributed Unit) is a logical node that carries the RLC (Real-Time Control) layer, the medium access control (MAC) layer, the higher physical layer (Higher PHY) layer, and other functions. In some examples, the DU can control at least one RU (Remote Root). The DU connects to the RU through interfaces, which can be fronthaul interfaces. In some examples, the Higher PHY layer includes the PHY layer processing, such as forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation.

[0073] In some deployments, the RU is a logical node that carries both lower physical layer (PHY) and radio frequency (RF) processing. In some examples, the RU can be a TRP, RRH, or other similar entity. In some examples, the Lower PHY includes PHY processing functions such as Fast Fourier Transform (FFT), Inverse Fast Fourier Transform (IFFT), digital beamforming, and filtering. The RU communicates with one or more UEs via a radio link.

[0074] DU and RU can cooperate to implement the functions of the PHY layer. A DU can be connected to one or more RUs. The functions of DU and RU can be configured in various ways depending on the design. For example, a DU can be configured to implement baseband functions, and an RU can be configured to implement mid-RF functions. Another example is that a DU can be configured to implement higher-level functions in the PHY layer, and an RU can be configured to implement lower-level functions in the PHY layer, or to implement both lower-level and RF functions. Higher-level functions in the physical layer can include a portion of the physical layer's functions that are closer to the MAC layer, while lower-level functions in the physical layer can include another portion of the physical layer's functions that are closer to the mid-RF side.

[0075] In one possible design, the processing unit in the BBU used to implement baseband functions is called the baseband high (BBH) unit, and the processing unit in the RRU / AAU / RRH used to implement baseband functions is called the baseband low (BBL) unit.

[0076] 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, a radio access network can also be an open radio access network (O-RAN) architecture. In an O-RAN system, CU can also be called an open CU (open CU, O-CU), DU can also be called an open DU (open DU, O-DU), CU-CP can also be called an open CU-CP (O-CU-CP), CU-UP can also be called an open CU-UP (O-CU-UP), and RU can also be called an open RU (open RU, 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 modules and hardware modules.

[0077] In this embodiment, the device for implementing the functions of a network device can be a network device itself, or a device capable of supporting the network device in implementing those functions, such as a chip system, chip, circuit, or communication module (i.e., a communication module that performs communication functions). This device can be installed within the network device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices. Furthermore, the device can be configured with program instructions for performing corresponding communication functions. This embodiment only uses a network device as an example to illustrate the device for implementing the functions of a network device, and does not limit the solution of this embodiment.

[0078] 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. Furthermore, terminal devices and network devices can be hardware devices, software functions running on dedicated hardware, or software functions running on general-purpose hardware, such as virtualization functions instantiated on a platform (e.g., a cloud platform), or entities that include dedicated or general-purpose hardware devices and software functions. This application does not limit the specific form of the terminal devices and network devices.

[0079] In practical network deployments, terrestrial networks cannot cover all areas, especially sparsely populated regions such as deserts, oceans, and the Arctic and Antarctic. Non-terrestrial network (NTN) networks offer wide coverage and are more likely to provide coverage in sparsely populated areas, making them suitable for deployment in such locations. This application's embodiments apply to NTN network communication, where an NTN network refers to a network or network segment that uses radio frequency on a satellite (unmanned aircraft system, UAS platform). The following section uses a satellite communication system as an example, and details the network architecture applicable to this application's embodiments with reference to Figure 1. In a satellite communication system, network equipment may include satellites.

[0080] Figure 1 is a schematic diagram of the network architecture applicable to an embodiment of this application. The terrestrial mobile terminal (UE) accesses the network through a 5G New Radio interface. The 5G access network equipment is deployed on satellites and connected to the terrestrial core network via a wireless link. Simultaneously, wireless links exist between satellites to complete signaling interaction and user data transmission between access network equipment. The various network elements in Figure 1 and their interfaces are described below:

[0081] Terminal devices: Mobile devices that support 5G New Radio, such as mobile phones and tablets. They can access satellite networks and initiate calls, internet access, and other services via the air interface.

[0082] 5G access network equipment: mainly provides wireless access services, allocates wireless resources to access terminals, and provides reliable wireless transmission protocols and data encryption protocols, such as base stations.

[0083] 5G Core Network: This includes services such as user access control, mobility management, session management, user security authentication, and billing. It consists of multiple functional units, which can be divided into control plane and data plane functional entities. The Access and Mobile Management Function (AMF) is responsible for user access management, security authentication, and mobility management. The User Plane Function (UPF) is responsible for managing user plane data transmission and traffic statistics. The Session Management Function (SMF) is primarily responsible for session management in the mobile network, such as session establishment, modification, and release.

[0084] Ground station: Responsible for forwarding signaling and service data between satellite access network equipment and 5G core network.

[0085] 5G New Radio: The wireless link between a terminal and access network equipment.

[0086] Xn interface: The interface between 5G access network devices and other access network devices, mainly used for signaling interactions such as handover.

[0087] NG interface: The interface between 5G access network equipment and 5G core network, mainly for exchanging non-access stratum (NAS) signaling of the core network and user service data.

[0088] It should be understood that the network architecture in Figure 1 is illustrated using the example of a UE accessing the network via a 5G New Radio interface. This application does not limit the network accessed by the UE. For example, the UE can access the network via 4G.

[0089] Figure 2 is a schematic diagram of an architecture of a communication system applicable to an embodiment of this application. As shown in Figure 2, the communication system may include at least one network device, such as the satellite device shown in Figure 1; the communication system may also include at least one terminal device, such as the terminal device shown in Figure 1. The network device and the terminal device can communicate via a wireless link.

[0090] It should be understood that the network equipment in this wireless communication system can be any device with wireless transceiver capabilities. This equipment includes, but is not limited to, base station controllers (BSCs), base transceiver stations (BTSs), etc., and can also be one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or even a satellite.

[0091] It should be understood that Figure 2 shows only one network device and one terminal device as an example. This communication system is not limited to including more terminal devices. For example, in a satellite communication network, a satellite can cover multiple terminal devices for communication. Each terminal device is also not limited to communicating with only one network device. For example, if a satellite moves, the terminal device may need to reselect a satellite for access communication.

[0092] It is understood that Figure 2 is merely an example and does not constitute any limitation on the scope of protection of this application. The communication method provided in the embodiments of this application may also involve network elements or devices not shown in Figure 2, and of course, the communication method provided in the embodiments of this application may also include only some of the network elements shown in Figure 2.

[0093] It should be understood that the network architecture shown above is merely an illustrative example, and the network architecture applicable to the embodiments of this application is not limited thereto. Any network architecture capable of realizing the functions of the above-described network elements is applicable to the embodiments of this application.

[0094] It should also be understood that the aforementioned network elements or functions can be divided into one or more services, and furthermore, services that exist independently of network functions may also exist. In this application, instances of the aforementioned functions, instances of services included in the aforementioned functions, or instances of services that exist independently of network functions can all be referred to as service instances.

[0095] It should also be understood that the above naming is defined only for the convenience of distinguishing different functions and should not constitute any limitation on this application. This application does not preclude the possibility of using other names in other networks in the future.

[0096] It should also be understood that the interface names between the network elements in Figures 1 and 2 are merely examples, and the interface names in actual implementations may be different; this application does not impose any specific limitations on them. Furthermore, the names of the messages (or signaling) transmitted between the aforementioned network elements are also merely examples and do not constitute any limitation on the function of the messages themselves.

[0097] The following explanations or introductions of some technical terms or concepts used in this application are provided for ease of reading.

[0098] 1. NTN:

[0099] NTN refers to networks or network segments that utilize onboard radio frequencies (RF) from satellites (UAS). Satellite communication offers advantages such as wide coverage, long communication distance, high reliability, high flexibility, and high throughput. Introducing satellites into 5G can provide communication services to areas difficult to cover with terrestrial networks, such as oceans and forests. It can enhance the reliability of 5G communication, providing more stable and higher-quality communication services for users on trains, airplanes, and other modes of transportation. It can also provide more data transmission resources and support a larger number of connections.

[0100] 2. Quasi-Earth Fixed Cell:

[0101] A quasi-fixed cell, also known simply as a quasi-fixed cell, is a type of satellite whose beam covers one geographic area for a limited time and a different geographic area for another time (e.g., the case of a non-geosynchronous orbit (NGSO) satellite generating a steerable beam). Specifically, as shown in Figure 3, the steerable beam generated by satellite 1 covers geographic area 1 at times t1, t2, and t3; therefore, geographic area 1 can be called a quasi-fixed cell.

[0102] 3. Earth Moving Cell:

[0103] A moving cell, also known simply as a mobile cell, is a cell whose coverage area shifts across the Earth's surface as the satellite moves (e.g., when an NGSO satellite generates a fixed or non-steerable beam). Specifically, as shown in Figure 4, the geographical areas covered by the fixed or non-steerable beam generated by satellite 1 at times t1, t2, and t3 are geographical area 1, geographical area 2, and geographical area 3, respectively. Therefore, geographical area 1, geographical area 2, and geographical area 3 can all be referred to as moving cells.

[0104] 4. NTN-based NG-RAN architectures:

[0105] RAN architectures based on NTN include transparent satellite architecture, regenerative satellite without ISL and with gNB processed payload, regenerative satellite with ISL and gNB processed payload, regenerative satellite with a regenerative satellite based on gNB-DU and with base station DU processing capabilities, and base stations with integrated access and backhaul (IAB) capabilities (gNB processed payload based on relay-like architectures).

[0106] It should be noted that the specific description of the above-mentioned NTN-based RAN architecture can be found in the descriptions of existing protocols or standards. To avoid redundancy, this application will not elaborate further.

[0107] It should be noted that the above-mentioned NTN-based RAN architectures are merely examples, and NTN-based RAN architectures may include other architectures with the same or similar characteristics, which this application does not limit.

[0108] 5. Mobile-Initiated Early Data Transmission (MO-EDT):

[0109] MO-EDT is triggered when the following conditions are met: 1) The upper 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 transport block (TB) size indicated in the system message.

[0110] Figure 5 illustrates the interaction between the UE and the access network device during the UE-initiated MO-EDT procedure. As shown in Figure 5, the interaction between the UE and the access network device may include the following steps.

[0111] S501, the UE sends a random access preamble to the access network equipment.

[0112] Accordingly, the access network equipment receives a random access preamble from the UE.

[0113] When a UE requests a connection to establish mobile-originating data transmission, the UE initiates the MO-EDT procedure and selects the random access preamble configured for early data transmission (EDT) to send to the access network equipment. The mobile-originating data originates from an upper layer or a higher layer.

[0114] S502, the access network device sends a random access response to the UE.

[0115] Accordingly, the UE receives a random access response from the access network device.

[0116] The random access response can instruct the access network equipment to allocate uplink resources for the UE to send message #1.

[0117] S503, the UE sends message #1 to the access network device.

[0118] Accordingly, the access network device receives message #1 from the UE.

[0119] It should be understood that the UE uses the uplink resources allocated to the UE as indicated in the random access response to send message #1.

[0120] In one possible implementation, if the UE initiates a control plane MO-EDT in a 4G communication system, message #1 can be an RRC Early Data Request (RRCE) message. For example, message #1 may include at least one of the following parameters: system architecture evolution temporary mobile subscriber identity (S-TMSI), establishment cause value, or dedicated info for NAS.

[0121] In one possible implementation, if the UE initiates a control plane MO-EDT in a 5G communication system, message #1 can be an RRCEarlyDataRequest message. For example, message #1 may include at least one of the following parameters: 5G-S-TMSI, establishment cause, or dedicated info for NAS.

[0122] In one possible implementation, if the UE initiates a User Plane MO-EDT in a 4G communication system, message #1 can be an RRC Connection Resume Request message. For example, message #1 may include at least one of the following parameters: resume ID, resume cause value, short resume message authentication code-integrity (short resume MAC-I), or uplink data.

[0123] In one possible implementation, if the UE initiates a user plane MO-EDT in a 5G communication system, message #1 can be an RRCConnectionResumeRequest message. For example, message #1 may include at least one of the following parameters: inactive radio network temporary identifier (I-RNTI), resume cause, short resume MAC-I, uplink data, or access stratum (AS) route area identifier (RAI).

[0124] After receiving message #1, the access network device interacts with the core network elements. The process of interaction between the access network device and the core network elements can refer to existing protocols or standards, and will not be described in detail in this application.

[0125] S504, the access network device sends message #2 to the UE.

[0126] Accordingly, the UE receives message #2 from the access network device.

[0127] In one possible implementation, if the UE initiates a control plane MO-EDT in a 4G or 5G communication system, message #2 can be an RRC Early Data Complete (RRCEarlyDataComplete) message. For example, message #2 may include dedicated info for NAS.

[0128] For example, an access network device can send an RRCEarlyDataComplete message on the common control channel (CCCH) to keep the UE in the RRC_IDLE state. If the access network device receives downlink data from a core network element, the RRCEarlyDataComplete message contains the downlink data.

[0129] In one possible implementation, if the UE initiates a user plane MO-EDT in a 4G or 5G communication system, message #2 can be an RRC Connection Release message. For example, if the UE initiates a user plane MO-EDT in a 4G communication system, message #2 can include at least one of the following parameters: release cause, resumeID, next hop chaining count (NCC), or downlink data. Here, the release cause can be RRC-Suspend, revoverID, NCC, and data radio bearer robust header compression (ROHC) (drb-ContinueROHC). If the UE initiates a user plane MO-EDT in a 5G communication system, message #2 can include at least one of the following parameters: release cause, I-RNTI, NCC, or downlink data. Here, the release cause can be RRC-Suspend, I-RNTI, NCC, and drb-ContinueROHC. If an access network device receives downlink data from a core network element, it encrypts and transmits the RRCEarlyDataComplete message on a dedicated transmission channel (DTCH). The RRCConnectionRelease message contains the downlink data. The DTCH message is multiplexed with the RRCConnectionRelease message on the dedicated control channel (DTCH).

[0130] 6. Preconfigured uplink resource (PUR):

[0131] The UE can request a PUR and obtain the PUR configuration in the previous RRC connection. The UE will maintain the PUR configuration when in RRC_IDLE state.

[0132] Transmissions using a PUR allow for a single uplink transmission from RRC_IDLE using pre-configured uplink resources without performing a random access procedure. A transmission using a PUR is triggered when an upper layer requests the establishment or restoration of an RRC connection, and the UE has a valid PUR for transmission, and the TA (Timing Advance) verification standard is met.

[0133] Figure 6 illustrates the interaction between the UE and the access network device during a UE-Used PUR transmission. As shown in Figure 6, the interaction between the UE and the access network device may include the following steps.

[0134] S601, the UE sends message #3 to the access network device.

[0135] Accordingly, the access network device receives message #3 from the UE.

[0136] It should be understood that if the UE has determined that it can use PUR resources, then when the UE needs to send mobile originating data, it can trigger the transmission using PUR.

[0137] It should be noted that the difference between S601 and S501 is that the UE transmits message #3 on the PUR resource, rather than on the resource allocated in the random access response.

[0138] In one possible implementation, if the UE initiates a control plane PUR in a 4G or 5G communication system, message #3 can be an RRCEarlyDataRequest message. For example, message #3 may include at least one of the following parameters: 5G-S-TMSI, establishment cause, or dedicated info for NAS.

[0139] In one possible implementation, if the UE initiates a user plane PUR in a 4G communication system, message #3 can be an RRCConnectionResumeRequest message. For example, message #3 may include at least one of the following parameters: resumeID, establishment cause, short resume MAC-I, or uplink data.

[0140] In one possible implementation, if the UE initiates a user plane PUR in a 5G communication system, message #3 can be an RRCConnectionResumeRequest message. For example, message #3 may include at least one of the following parameters: I-RNTI, establishment cause, short resume MAC-I, or uplink data.

[0141] After receiving message #3, the access network device interacts with the core network elements. The process of interaction between the access network device and the core network elements can refer to existing protocols or standards, and will not be described in detail in this application.

[0142] S602, the access network device sends message #4 to the UE.

[0143] Accordingly, the UE receives message #4 from the access network device.

[0144] In one possible implementation, if the UE initiates a control plane PUR in a 4G or 5G communication system, message #4 can be an RRCEarlyDataComplete message, a layer 1 acknowledgment (layer 1 Ack), or a MAC control element (CE).

[0145] For example, an access network device can send an RRCEarlyDataComplete message on the common control channel (CCCH) to keep the UE in the RRC_IDLE state. The RRCEarlyDataComplete message may include dedicated info for NAS, and if the access network device receives downlink data from a core network element, the RRCEarlyDataComplete message contains the downlink data.

[0146] For example, if the access network device determines that there is no downlink data or signaling to be processed, the access network device can send a Layer 1 confirmation to the UE. The Layer 1 confirmation may include a time advance adjustment to update the TA and terminate the transmission process.

[0147] For example, if the access network device determines that there is no further data or signaling, the access network device can send a MAC CE to the UE. The MAC CE may include a time adjustment command to update the TA and terminate the transmission process.

[0148] In one possible implementation, if the UE initiates a user plane PUR in a 4G or 5G communication system, message #4 can be an RRCConnectionRelease message. For example, if the UE initiates a user plane PUR in a 4G communication system, message #4 may include at least one of the following parameters: release cause, resumeID, NCC, downlink data, or time advance command. If the UE initiates a user plane PUR in a 5G communication system, message #4 may include at least one of the following parameters: release cause, I-RNTI, NCC, downlink data, or time advance command.

[0149] To enhance uplink capacity, MO-EDT can omit S501 and S502 as shown in Figure 5. MO-EDT omitting S501 and S502 can be called PRACH-free MO-EDT, or PRACH-free EDT. Alternatively, to enhance uplink capacity, the UE can perform contention-based PUR transmissions, also known as contention-based PUR.

[0150] It is understandable that if MO-EDT omits S501 and S502 shown in Figure 5, it is equivalent to omitting the step of the access network device allocating resources for the UE to transmit message #1. In this case, the UE will use shared resources to send message #1. The shared resources are resources configured by the access network device for multiple UEs and can be used by multiple UEs; these shared resources can also be called public resources. In contention-based PUR transmission, the access network device does not use unicast to configure dedicated PUR resources for the UE, but rather configures shared PUR resources for multiple UEs. In other words, multiple UEs can use the same PUR resources to send message #3. However, when UEs use shared resources to send uplink messages, if multiple UEs simultaneously use the same resources to send uplink messages, there will be mutual interference between the uplink messages sent by the multiple UEs, or in other words, uplink conflicts will occur between the uplink messages sent by the multiple UEs, leading to uplink transmission failure.

[0151] In view of this, this application provides a communication method that enables a terminal device to back off when it determines that the uplink transmission has failed, thereby facilitating successful retransmission after the uplink transmission fails.

[0152] Before introducing the scheme of this application, the following points should be noted.

[0153] (1) In this application, “instruction” may include direct instruction, indirect instruction, explicit instruction, and implicit instruction. When describing a certain instruction information for the purpose of instructing A, it can be understood that the instruction information carries A, directly instructs A, or indirectly instructs A.

[0154] In this application, the information indicated by the instruction information is called the information to be instructed. In specific implementations, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly indicate the information to be instructed by indicating other information, where there is a relationship between the other information and the information to be instructed. It can also indicate only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent. Furthermore, the information to be instructed can be sent as a whole or divided into multiple sub-information pieces, and the sending period and / or timing of these sub-information pieces can be the same or different.

[0155] (2) In this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, which may include direct transmission via the air interface or indirect transmission via the air interface by other units or modules. "Receive information from YY" can be understood as the source of the information being YY, which may include direct reception from YY via the air interface or indirect reception from YY via the air interface by other units or modules. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface. In other words, sending and receiving can occur between devices, such as between network devices and terminal devices, or within a device, such as between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface.

[0156] (3) In the various embodiments of this application, unless otherwise specified or logically conflicting, the terms and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0157] (4) In this application, "first" and "second" are used for descriptive convenience only to distinguish objects and are not intended to limit the scope of the embodiments of this application. They are not used to describe the order or sequence of features. It should be understood that the objects described in this way can be interchanged where appropriate so as to describe solutions other than those in the embodiments of this application.

[0158] (5) In this application, “predefined” may mean a standard protocol predefined, or it may mean that the devices have agreed or negotiated in advance.

[0159] (6) In this application, the words “exemplary,” “for example,” etc., are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as an “example” in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the word “example” is intended to present the concept in a concrete manner. In the embodiments of this application, “of,” “corresponding, relevant,” and “corresponding” may sometimes be used interchangeably, and it should be noted that their intended meanings are consistent unless their distinction is emphasized.

[0160] The method provided by the embodiments of this application will be described in detail below with reference to the accompanying drawings. The embodiments provided by this application can be applied to the communication system shown in FIG1 above, and are not limited thereto.

[0161] In the following embodiments, terminal devices and network devices are used as examples for illustrative purposes. The term "terminal device" can be replaced by a component of a terminal device (e.g., a chip, chip system, circuit, or communication module), and the term "network device" can be replaced by a component of a network device (e.g., a chip, chip system, circuit, or communication module).

[0162] Figure 7 shows a schematic flowchart of the communication method provided in an embodiment of this application. As shown in Figure 7, method 700 may include the following steps.

[0163] S710, the network device sends the first uplink resource configuration information.

[0164] Accordingly, the terminal device receives the first uplink resource configuration information from the network device.

[0165] The first uplink resource configuration information is used to indicate uplink resources. It can be understood that the uplink resources indicated by the first uplink resource configuration information are the uplink resources configured by the network device for the terminal device. For example, the first uplink resource configuration information may include one or more of the following: location information of the uplink resource in the time domain, location information of the uplink resource in the frequency domain, or the period of the uplink resource.

[0166] The location information of the uplink resource's time domain resources may include one or more of the following: the time resource indicator value (TRIV) corresponding to the uplink resource, the index of the time domain unit included in the uplink resource, the time domain unit offset information of the time domain unit included in the uplink resource relative to the time domain unit where the first uplink resource configuration information is located, the starting time domain unit index included in the uplink resource, or the number of time domain units included in the uplink resource. The time domain unit may be a slot, mini-slot, symbol, frame, subframe, etc.

[0167] The location information of the uplink resource's frequency domain resources may include one or more of the following: the frequency resource indicator value (FRIV) corresponding to the uplink resource, the index of the frequency domain cells included in the uplink resource, the index of the starting frequency domain cells included in the uplink resource, or the number of frequency domain cells included in the uplink resource. Here, a frequency domain cell may be a subchannel, subband, physical resource block (PRB), resource element (RE), subcarrier, carrier, bandwidth part (BWP), etc.

[0168] For example, in S710, the network device sends the first uplink resource configuration information via multicast or broadcast.

[0169] For example, in S710, the network device sends the first uplink resource configuration information via unicast. It should be noted that if the network device sends the first uplink resource configuration information via unicast, then the network device sends the same first uplink resource configuration information to multiple terminal devices respectively via unicast. For example, the network device sends the first uplink resource configuration information to UE#1 via unicast, and also sends the first uplink resource configuration information to UE#2 via unicast.

[0170] It is understandable that since multiple terminal devices can receive the first uplink resource configuration information from the network device, the uplink resource indicated by the first uplink resource configuration information is a public or shared resource. In other words, multiple terminal devices that receive the first uplink resource configuration information can use the uplink resource indicated by the first uplink resource configuration information to perform uplink transmission.

[0171] Optionally, method 700 also includes S711.

[0172] S711, network devices send backoff time parameter information.

[0173] Correspondingly, the terminal device receives backoff time parameter information from the network device.

[0174] The backoff time parameter information is used to determine the first backoff time or the first backoff resource quantity. The first backoff time is the duration of the delay when the terminal device performs the backoff. The first backoff resource quantity is the amount of time-domain resources delayed when the terminal device performs the backoff.

[0175] Optionally, when the terminal device receives the backoff time parameter information, method 700 further includes: the terminal device determining a second backoff time based on the backoff time parameter information; and the terminal device randomly selecting a first backoff time between 0 and the second backoff time. Alternatively, method 700 further includes: the terminal device determining a second backoff resource quantity based on the backoff time parameter information; and the terminal device randomly selecting a first backoff resource quantity between 0 and the second backoff resource quantity.

[0176] For example, the backoff time parameter information includes one or more of the following: second backoff time, index of the second backoff time, or, number of second backoff resources.

[0177] For example, if the terminal device and network device have predefined or preconfigured a backoff time parameter table, which includes at least one backoff time and an index to at least one backoff time, then the backoff time parameter information may include an index to a second backoff time. Accordingly, the terminal device can determine the second backoff time based on the index of the second backoff time and the backoff time parameter table.

[0178] The time unit for the aforementioned backoff time can be seconds (s), milliseconds (ms), time slots, micro-time slots, symbols, frames, subframes, etc.

[0179] For example, in S711, network devices send backoff time parameter information via multicast or broadcast.

[0180] For example, in S711, the network device sends backoff time parameter information via unicast. It should be noted that if the network device sends backoff time parameter information via unicast, it sends the same backoff time parameter information to multiple terminal devices separately. For instance, the network device sends backoff time parameter information to UE#1 via unicast, and also sends backoff time parameter information to UE#2 via unicast.

[0181] It should be noted that if the terminal device and network device have pre-configured or pre-defined the second backoff time and / or the number of second backoff resources, then method 700 may not need to execute S711. Alternatively, if the network device sends backoff time parameter information to the terminal device before executing method 700, then method 700 may not need to execute S711.

[0182] Optionally, method 700 also includes S712.

[0183] S712, network devices send instruction information.

[0184] Correspondingly, the terminal device receives instruction information from the network device.

[0185] The indication information is used to indicate whether to backoff in the event of an uplink transmission failure.

[0186] This application does not limit the specific form of the instruction information.

[0187] For example, the indication information may include 1 bit. If the value of the indication information is "0", the indication information is used to indicate that no backoff will be performed in the event of uplink transmission failure. If the value of the indication information is "1", the indication information is used to indicate that backoff will be performed in the event of uplink transmission failure.

[0188] For example, in S712, network devices send instruction information via multicast or broadcast.

[0189] For example, in S712, the network device sends indication information via unicast. It should be noted that if the network device sends indication information via unicast, it sends the same indication information to multiple terminal devices. For instance, the indication information sent by the network device to UE#1 via unicast indicates backoff in the event of uplink transmission failure, and the indication information sent by the network device to UE#2 via unicast also indicates backoff in the event of uplink transmission failure.

[0190] It should be noted that if the terminal device defaults to or predefines backoff in the event of uplink transmission failure, or defaults to or predefines not backoff in the event of uplink transmission failure, then method 700 may not execute S712. Alternatively, if the network device sends indication information to the terminal device before executing method 700, then method 700 may not execute S712. Alternatively, if the network device sends backoff time parameter information to the terminal device, it implicitly indicates backoff in the event of uplink transmission failure, and method 700 may not execute S712. Alternatively, if the network device does not send backoff time parameter information to the terminal device, it implicitly indicates not backoff in the event of uplink transmission failure, and method 700 may not execute S712.

[0191] Optionally, method 700 also includes S713.

[0192] S713, network devices send public RNTI.

[0193] Accordingly, the terminal device receives the public RNTI from the network device.

[0194] The public RNTI is used to scramble downlink messages.

[0195] It should be noted that if the network device sends a common RNTI to the terminal device before executing method 700, then method 700 may not need to execute S713. Alternatively, if the network device scrambles the downlink message using an RNTI determined by the uplink resources indicated by the first uplink resource configuration information, then method 700 may not need to execute S713.

[0196] It should also be noted that the execution order of S710 to S713 is not limited in the embodiments of this application. For example, S710 can be executed before or after S711 to S713, or S710 can be executed simultaneously with S711 to S713. For example, when S710 and S711 to S713 are executed simultaneously, the first uplink resource configuration information, backoff time parameter information, indication information, and common RNTI can be included in the same message.

[0197] S720: The terminal device sends an uplink message to the network device.

[0198] The terminal device sends uplink messages through the uplink resources indicated by the first uplink resource configuration information.

[0199] The uplink message may include the identifier of the terminal device. For example, if the terminal device is already connected to a cell (e.g., cell #1), the identifier of the terminal device may be the cell-radio network temporary identifier (C-RNTI) of the terminal device in cell #1. Another example is that the identifier of the terminal device is the S-TMSI assigned to the terminal device by the core network element, or the identifier of the terminal device is a random number.

[0200] It is understandable that since the uplink resource indicated by the first uplink resource configuration information is a public or shared resource, multiple terminal devices may simultaneously send uplink messages through the uplink resource indicated by the first uplink resource configuration information, which may cause the terminal devices to fail to send uplink messages.

[0201] It is also understandable that if the terminal device fails to send an uplink message, the network device may not be able to receive the uplink message from the terminal device, or, if it does receive the uplink message from the terminal device, it may be unable to parse the uplink message.

[0202] After sending an uplink message, the terminal device can start or restart a window or timer. For example, the terminal device can start or restart the window or timer one round-trip time (RTT) after the end time unit of the uplink message, or the terminal device can start or restart the window or timer after the end time unit of the physical uplink shared channel (PUSCH) transmission corresponding to the uplink message plus the time unit after the UE-eNB / gNB RTT.

[0203] It should be noted that if the terminal device sends uplink messages repeatedly, the terminal device will start or restart the window or timer after the last uplink message is sent.

[0204] Optionally, method 700 also includes S721.

[0205] S721, network devices send downlink messages, downlink control information (DCI), or MAC messages.

[0206] Correspondingly, the terminal device receives downlink messages, DCI messages, or MAC messages.

[0207] In one possible implementation, after receiving an uplink message from a terminal device, if the network device determines that it cannot parse the uplink message, it can send a DCI or MAC message to the terminal device.

[0208] The DCI (Distributed Information Configuration) is used to indicate uplink message transmission failure; it can also be referred to as a downlink layer 1 (L1) message. For example, the DCI is scrambled using a first RNTI (Reference Resource Interchange) and includes third uplink resource configuration information. This DCI can reuse the legacy PUR (Programmed Receiver Retransmission) message format N0. The third uplink resource configuration information is carried in resource allocation-related fields within the DCI, such as resource assignment and scheduling delay fields.

[0209] MAC messages include indication information #1, which is used to indicate uplink message transmission failure, or to indicate retransmission, or to indicate retransmission after backoff. MAC messages can be called downlink layer 2 (L2) messages.

[0210] In one possible implementation, the downlink message sent by the network device is a downlink message sent to other terminal devices. In other words, the downlink message is not scrambled with the first RNTI, or the identifier of the terminal device included in the downlink message does not match the identifier of the terminal device included in the uplink message, or the identifier of the terminal device included in the downlink message does not match the identifier cached by the terminal device.

[0211] Here, the first RNTI is either a common RNTI or an RNTI determined based on the uplink resources indicated by the first uplink resource configuration information. For example, the RNTI determined based on the uplink resources indicated by the first uplink resource configuration information can be denoted as X-RNTI. For instance, X-RNTI = 1 + t_id + 10 * f_id, where t_id and f_id are the indexes of the time-domain resource and frequency resource of the uplink resources indicated by the first uplink resource configuration information, respectively. Another example is X-RNTI = 1 + resource_id, where resource_id is the index of the uplink resource indicated by the first uplink resource configuration information.

[0212] A mismatch between the terminal device identifier included in the downlink message and the terminal device identifier included in the uplink message means that the terminal device identifiers included in the downlink message and the uplink message are used to identify different terminal devices. For example, the terminal device identifier included in the downlink message is used to identify terminal device #1, while the terminal device identifier included in the uplink message is used to identify terminal device #2.

[0213] A mismatch between the terminal device identifier included in the downlink message and the identifier cached in the terminal device cache means that the terminal device identifier included in the downlink message and the identifier cached in the terminal device cache are used to identify different terminal devices. For example, the terminal device identifier included in the downlink message is used to identify terminal device #1, while the identifier cached in the terminal device #2 is used to identify terminal device #2. The identifier cached in the terminal device cache can be S-TMSI or C-RNTI.

[0214] It is understandable that because the downlink messages sent by the network device are sent during the window or timer operation, the terminal device can receive the downlink messages from the network device.

[0215] S730, the terminal device has determined that the uplink message transmission failed.

[0216] After starting or restarting a window or timer, the terminal device monitors the PDCCH and / or receives downlink messages from the network device within the window or during the timer's operation. Then, it determines that uplink message transmission has failed if at least one of the following events occurs: Event 1, the window or timer expires and the terminal device does not receive a downlink message from the network device; Event 2, the window or timer expires and the terminal device receives a downlink message from the network device before the window or timer expires, and the downlink message is not scrambled with the first RNTI; Event 3, the window or timer expires and the terminal device receives a downlink message from the network device before the window or timer expires, and the identifier of the terminal device included in the downlink message does not match the identifier of the terminal device included in the uplink message; Event 4, the terminal device receives a DCI from the network device before the window or timer expires, and the DCI indicates uplink message transmission failure; Event 5, the terminal device receives a MAC message from the network device before the window or timer expires, and the MAC message includes indication information #1.

[0217] Regarding Event 1, "the terminal device did not receive downlink messages from the network device" means that the terminal device did not receive any downlink messages from the network device during the window or timer's execution.

[0218] Regarding Event 2, the downlink message received by the terminal device is the downlink message received by the terminal device through the PDCCH.

[0219] Regarding event 3, the downlink message received by the terminal device may be a MAC protocol data unit (PDU) or an RRC message. This downlink message is a downlink message received by the terminal device through the physical downlink shared channel (PDSCH). This PDSCH corresponds to the PDCCH scrambled with the first RNTI that the terminal device monitors during the window or timer operation.

[0220] Regarding event 4, if the terminal device receives a DCI from the network device before the window or timer expires, the terminal device can stop the window or timer.

[0221] Regarding event 5, if the terminal device receives a MAC message from the network device before the window or timer expires, the terminal device can stop the window or timer.

[0222] It is understandable that when a terminal device stops the window or timer, it is equivalent to the terminal device stopping monitoring the PDCCH and / or receiving downlink messages from network devices.

[0223] It should be understood that if the terminal device determines that the uplink message transmission has failed based on any of events 1 to 3, the terminal device can still determine that the uplink message transmission has failed even if the network device does not indicate uplink transmission failure or retransmission to the terminal device, thus facilitating timely triggering of uplink message retransmission. Furthermore, since it is not necessary for the network device to indicate uplink transmission failure or retransmission to the terminal device, downlink signaling overhead can be reduced.

[0224] It should also be understood that, compared to a scheme that determines uplink message transmission failure based on any of events 1 through 3, if the terminal device determines uplink message transmission failure based on event 4 or 5, the terminal device can determine the failure before the window or timer expires. This facilitates triggering uplink message retransmission more quickly and reduces retransmission latency. Furthermore, in the event of event 4 or 5, the terminal device can stop the window or timer, or in other words, stop monitoring the PDCCH and / or receiving downlink messages from network devices, thereby saving power consumption.

[0225] S740, the terminal device retransmits the uplink message.

[0226] If the terminal device determines that the uplink message transmission has failed, it retransmits the uplink message. For example, the uplink message sent by the terminal device in S710 may be the same message as the uplink message retransmitted in S740, or the uplink message sent by the terminal device in S710 may be different from the uplink message retransmitted in S740. For instance, if the terminal device adjusts the modulation and coding scheme (MCS) during retransmission, the uplink message sent by the terminal device in S710 may be different from the uplink message retransmitted in S740.

[0227] In one possible implementation, after a first backoff time delay, the terminal device retransmits the uplink message using the uplink resources indicated by the first uplink resource configuration information. The first backoff time is randomly selected by the terminal device between 0 and a second backoff time. It should be noted that the terminal device has an equal probability of selecting any backoff time from 0 to the second backoff time; in other words, the terminal device randomly selects the first backoff time evenly distributed between 0 and the second backoff time, or alternative backoff times that can serve as the first backoff time are evenly distributed between 0 and the second backoff time. The unit of the first backoff time is the same as the unit of the second backoff time, or the duration corresponding to the unit of the first backoff time is less than the duration corresponding to the unit of the second backoff time. For example, the second backoff time is x subframes, and the first backoff time is y subframes, where x is an integer greater than or equal to 1, and y = 1, 2, ..., x, meaning the units of the first and second backoff times are the same. For example, the second backoff time is x seconds, and the first backoff time is y milliseconds, where x is an integer greater than or equal to 1, and y = 1, 2, ..., x * 1000. That is, the duration corresponding to the unit of the first backoff time is less than the duration corresponding to the unit of the second backoff time.

[0228] In one possible implementation, the terminal device retransmits the uplink message through the uplink resource indicated by the first uplink resource configuration information after a delay of at least the number of uplink resources indicated by the first backoff resource configuration information. For example, in S710, the terminal device sends an uplink message through the r-th uplink resource indicated by the first uplink resource configuration information; then in S740, the terminal device retransmits the uplink message through the (r+m+s)-th uplink resource indicated by the first uplink resource configuration information, where m is the number of first backoff resources, and r, s, and m are integers greater than or equal to 0. The number of first backoff resources is randomly selected by the terminal device from 0 to the number of second backoff resources. It should be noted that the terminal device has an equal probability of selecting any number of backoff resources from 0 to the number of second backoff resources; in other words, the terminal device randomly selects the number of first backoff resources uniformly from 0 to the number of second backoff resources, or, in other words, the number of alternative backoff resources that can be used as the number of first backoff resources is uniformly distributed from 0 to the number of second backoff resources.

[0229] It should be noted that if the terminal device determines that the uplink message transmission failed in the event 4, and the DCI includes the third uplink resource configuration information, the terminal device will still use the uplink resources indicated by the first uplink resource configuration information to retransmit the uplink message after delaying the first backoff time or delaying at least the number of uplink resources indicated by the first backoff resource configuration information. In other words, the terminal device ignores the third uplink resource configuration information included in the DCI.

[0230] It should also be noted that if method 700 executes S712 and the indication information is used to indicate backoff in the event of uplink transmission failure, the terminal device will backoff after determining that the uplink message transmission has failed, and then retransmit the uplink message.

[0231] In one possible implementation, after the terminal device determines that the uplink message transmission has failed, it retransmits the uplink message without backing up.

[0232] It should be noted that if the terminal device determines that the uplink message transmission failed in the event 4, and the DCI includes the third uplink resource configuration information, the uplink message can be retransmitted using the uplink resources indicated by the first uplink resource configuration information, or the uplink message can be retransmitted using the uplink resources indicated by the third uplink resource configuration information.

[0233] It should also be noted that if method 700 does not execute S712, or if method 700 executes S712 and the indication information is used to indicate that no backoff will be performed in the event of uplink transmission failure, then after the terminal device determines that the uplink message transmission has failed, it will retransmit the uplink message without backoff.

[0234] In the embodiments of this application, during uplink transmission using shared resources (e.g., public uplink resources or contention-based PUR resources), the terminal device can determine that the uplink transmission has failed and back off before retransmitting, thereby improving the success rate of retransmission. For example, when terminal device #1 and terminal device #2 send uplink messages through uplink resource #1, uplink transmission fails due to uplink conflict (i.e., the uplink messages sent by terminal device #1 and terminal device #2 interfere with each other). Then, after backing off, terminal device #1 retransmits the uplink message on uplink resource #2, and terminal device #2 retransmits the uplink message on uplink resource #3. Since uplink resource #2 and uplink resource #3 are different, both terminal device #1 and terminal device #2 can successfully retransmit.

[0235] Figure 8 shows a schematic flowchart of the communication method provided in an embodiment of this application. As shown in Figure 8, method 800 may include the following steps.

[0236] S810, the network device sends the first uplink resource configuration information.

[0237] Accordingly, the terminal device receives the first uplink resource configuration information from the network device.

[0238] For a more detailed description of S810, please refer to S710 in Method 700 above.

[0239] Optionally, method 800 also includes S811.

[0240] S811, the network device sends backoff time parameter information.

[0241] Correspondingly, the terminal device receives backoff time parameter information from the network device.

[0242] For a more detailed description of S811, please refer to S711 in Method 700 above.

[0243] Optionally, method 800 also includes S812.

[0244] S812, network devices send instruction information.

[0245] Correspondingly, the terminal device receives instruction information from the network device.

[0246] For a more detailed description of S812, please refer to S712 in Method 700 above.

[0247] Optionally, method 800 also includes S813.

[0248] S813, network devices send public RNTI.

[0249] Accordingly, the terminal device receives the public RNTI from the network device.

[0250] For a more detailed description of S813, please refer to S713 in Method 700 above.

[0251] Method 800 also includes S814.

[0252] S814, the network device sends the second uplink resource configuration information.

[0253] Correspondingly, the terminal device receives the second uplink resource configuration information from the network device.

[0254] The second uplink resource configuration information is used to indicate uplink resources. It can be understood that the uplink resources indicated by the second uplink resource configuration information are the uplink resources configured by the network device for the terminal device. For example, the second line of resource configuration information may include one or more of the following: location information of the uplink resource in the time domain, location information of the uplink resource in the frequency domain, or the period of the uplink resource.

[0255] For more details on the second uplink resource configuration information, please refer to the description of the first uplink resource configuration information in Method 700 above.

[0256] For example, in S814, the network device sends the second uplink resource configuration information via multicast or broadcast.

[0257] For example, in S814, the network device sends the second uplink resource configuration information via unicast. It should be noted that if the network device sends the second uplink resource configuration information via unicast, then the network device sends the same second uplink resource configuration information to multiple terminal devices respectively via unicast. For example, the network device sends the second uplink resource configuration information to UE#1 via unicast, and also sends the second uplink resource configuration information to UE#2 via unicast.

[0258] It is understandable that since multiple terminal devices can receive the second uplink resource configuration information from the network device, the uplink resource indicated by the second uplink resource configuration information is a public or shared resource. In other words, multiple terminal devices that receive the second uplink resource configuration information can use the uplink resource indicated by the second uplink resource configuration information to perform uplink transmission.

[0259] It should be noted that the execution order of S810 to S814 is not limited in this application embodiment. For example, S810 can be executed before or after S811 to S814, or S810 can be executed simultaneously with S811 to S814. For example, when S810 and S811 to S814 are executed simultaneously, the first uplink resource configuration information, backoff time parameter information, indication information, common RNTI, and second resource configuration information can be included in the same message.

[0260] S820: The terminal device sends an uplink message to the network device.

[0261] The terminal device sends uplink messages through the uplink resources indicated by the first uplink resource configuration information.

[0262] For more details on S820, please refer to S720 in Method 700 above.

[0263] Optionally, method 800 also includes S821.

[0264] S821, network devices send downlink messages or DCI or MAC messages.

[0265] Correspondingly, the terminal device receives downlink messages, DCI messages, or MAC messages.

[0266] For a more detailed description of S821, please refer to S721 in Method 700 above.

[0267] S830, the terminal device has determined that the uplink message transmission failed.

[0268] For a more detailed description of S830, please refer to S730 in Method 700 above.

[0269] S840, the terminal device retransmits the uplink message.

[0270] If the terminal device determines that the uplink message transmission has failed, it retransmits the uplink message. For example, the uplink message sent by the terminal device in S810 may be the same message as the uplink message retransmitted in S840, or the uplink message sent by the terminal device in S810 may be different from the uplink message retransmitted in S840. For instance, if the terminal device adjusts the MCS during retransmission, the uplink message sent by the terminal device in S810 may be different from the uplink message retransmitted in S840.

[0271] In one possible implementation, after a first backoff time delay, the terminal device retransmits the uplink message using uplink resources indicated by the second uplink resource configuration information. The description of the first backoff time can be found in S740 of method 700 above.

[0272] In one possible implementation, the terminal device retransmits the uplink message using the uplink resources indicated by the second uplink resource configuration information after a delay of at least the number of first backoff resources. A description of the number of first backoff resources can be found in S740 of method 700 above.

[0273] It should be noted that if the terminal device determines that the uplink message transmission failed in the event 4, and the DCI includes the third uplink resource configuration information, the terminal device will still use the uplink resources indicated by the second uplink resource configuration information to retransmit the uplink message after delaying the first backoff time or delaying at least the number of uplink resources indicated by the first backoff resources. In other words, the terminal device ignores the third uplink resource configuration information included in the DCI.

[0274] It should also be noted that if method 800 executes S812 and the indication information is used to indicate backoff in the event of uplink transmission failure, the terminal device will backoff after determining that the uplink message transmission has failed, and then retransmit the uplink message.

[0275] In one possible implementation, after the terminal device determines that the uplink message transmission has failed, it retransmits the uplink message without backing up.

[0276] The terminal device may retransmit uplink messages using uplink resources indicated by the first uplink resource configuration information, or by using uplink resources indicated by the second uplink resource configuration information.

[0277] It should be noted that if the terminal device determines that the uplink message transmission failed in the event 4, and the DCI includes the third uplink resource configuration information, it can retransmit the uplink message using the uplink resources indicated by the first uplink resource configuration information, or retransmit the uplink message using the uplink resources indicated by the third uplink resource configuration information, or retransmit the uplink message using the uplink resources indicated by the second uplink resource configuration information.

[0278] It should also be noted that if method 800 does not execute S812, or if method 800 executes S812 and the indication information is used to indicate that no backoff will be performed in the event of uplink transmission failure, then after the terminal device determines that the uplink message transmission has failed, it will retransmit the uplink message without backoff.

[0279] In the embodiments of this application, during the uplink transmission process of the terminal device through shared resources (such as public uplink resources or contention-based PUR resources), the terminal device can determine that the uplink transmission has failed, and then back off before retransmitting, thereby improving the success rate of retransmission.

[0280] It is understood that some optional features in the various embodiments of this application may not depend on other features in some scenarios, or may be combined with other features in some scenarios, without limitation.

[0281] It is also understood that the sending of information is mentioned multiple times in some of the above embodiments. Taking A sending information to B as an example, A sending information to B can include A sending information directly to B, or it can include A sending information to B through other devices or network elements, and there is no limitation on this.

[0282] It is also understood that the solutions in the various embodiments of this application can be used in reasonable combinations, and the explanations or descriptions of the various terms appearing in the embodiments can be referenced or explained to each other in the various embodiments, without limitation.

[0283] It can also be understood that the methods and operations implemented by the network element in the above-described method embodiments can also be implemented by components of the device (such as chips or circuits), without limitation.

[0284] The methods provided by the embodiments of this application have been described in detail above with reference to Figures 7 and 8. The apparatus provided by the embodiments of this application will be described in detail below with reference to Figures 9 and 10. It should be understood that the descriptions of the apparatus embodiments correspond to the descriptions of the method embodiments; therefore, any content not described in detail can be referred to the method embodiments above, and for the sake of brevity, will not be repeated here.

[0285] Figure 9 is a schematic diagram of a communication device 900 provided in an embodiment of this application. The device 900 includes a transceiver unit 910 and a processing unit 920. The transceiver unit 910 can be used to implement corresponding communication functions. The transceiver unit 910 can also be referred to as a communication interface or communication unit. The processing unit 920 can be used to perform processing. Optionally, the transceiver unit 910 may include a receiving unit and a sending unit, whereby the receiving unit implements the function of receiving and the sending unit implements the function of sending.

[0286] Optionally, the device 900 may further include a storage unit for storing instructions and / or data, and the processing unit 920 may read the instructions and / or data from the storage unit to enable the device to implement the aforementioned method embodiments.

[0287] As a design, the device 900 is used to execute the steps or processes executed by the device in the above method embodiment, the transceiver unit 910 is used to execute the transceiver-related operations on the device side in the above method embodiment, and the processing unit 920 is used to execute the processing-related operations on the device side in the above method embodiment.

[0288] In one possible implementation, the device 900 is used to execute the steps or processes executed by the terminal device in the embodiments shown in Figures 7 and 8. Optionally, the transceiver unit 910 is used to receive first uplink resource configuration information; the transceiver unit 910 is also used to send an uplink message through the uplink resources indicated by the first uplink resource configuration information; the processing unit 920 is used to determine that the uplink message transmission failed; the transceiver unit 910 is also used to retransmit the uplink message after a first backoff time.

[0289] In another possible implementation, the device 900 is used to perform the steps or processes executed by the network device in the embodiments shown in Figures 7 and 8. Optionally, the transceiver unit 910 is used to send first uplink resource configuration information; the transceiver unit 910 is also used to receive uplink messages through the uplink resources indicated by the first uplink resource configuration information; the transceiver unit 910 is also used to send downlink messages and / or DCI, the downlink messages or DCI being used to determine that the uplink message transmission failed.

[0290] It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0291] It should also be understood that the device 900 here is embodied in the form of a functional unit. The term "unit" here can refer to an application-specific integrated circuit (ASIC), electronic circuitry, a processor (e.g., a shared processor, a proprietary processor, or a group processor, etc.) and memory for executing one or more software or firmware programs, integrated logic circuitry, and / or other suitable components supporting the described functions. In an alternative example, those skilled in the art will understand that the device 900 can be specifically a device (such as a terminal device or a network device) in the above embodiments, and can be used to execute the various processes and / or steps corresponding to the device in the above method embodiments; to avoid repetition, these will not be described further here.

[0292] The apparatus 900 of each of the above-described schemes has the function of implementing the corresponding steps performed by the devices (such as terminal devices, network devices, etc.) in the above-described methods. The functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver unit can be replaced by a transceiver (e.g., the sending unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as processing units, can be replaced by processors, each executing the transceiver operations and related processing operations in the respective method embodiments.

[0293] In addition, the transceiver unit 910 described above can also be a transceiver circuit (for example, it may include a receiving circuit and a transmitting circuit), and the processing unit can be a processing circuit.

[0294] It should be noted that the device in Figure 9 can be the equipment in the foregoing embodiments, or it can be a chip or a chip system, such as a system on a chip (SoC). The transceiver unit can be an input / output circuit or a communication interface; the processing unit is a processor, microprocessor, or integrated circuit integrated on the chip. No limitations are imposed here.

[0295] Figure 10 is a schematic diagram of another communication device 1000 provided in an embodiment of this application. The device 1000 includes a processor 1010, which is coupled to a memory 1020. The memory 1020 is used to store computer programs or instructions and / or data. The processor 1010 is used to execute the computer programs or instructions stored in the memory 1020, or to read the data stored in the memory 1020, in order to execute the methods in the above method embodiments.

[0296] Optionally, there may be one or more processors 1010.

[0297] Optionally, the memory 1020 may be one or more.

[0298] Alternatively, the memory 1020 can be integrated with the processor 1010, or it can be set separately.

[0299] Optionally, as shown in FIG10, the device 1000 further includes a transceiver 1030, which is used for receiving and / or transmitting signals. For example, the processor 1010 is used to control the transceiver 1030 to receive and / or transmit signals. Optionally, the transceiver 1030 may include a receiver for receiving signals and a transmitter for transmitting signals.

[0300] As an example, processor 1010 may have the functions of processing unit 920 shown in FIG9, memory 1020 may have the functions of storage unit, and transceiver 1030 may have the functions of transceiver unit 910 shown in FIG9.

[0301] As one approach, the device 1000 is used to implement the operations performed by the device (such as a terminal device, or a network device, etc.) in the various method embodiments described above.

[0302] For example, processor 1010 is used to execute computer programs or instructions stored in memory 1020 to implement the relevant operations of the devices (such as terminal devices, or network devices, etc.) in the various method embodiments described above.

[0303] It should be understood that the processor mentioned in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0304] It should also be understood that the memory mentioned in the embodiments of this application can be volatile memory and / or non-volatile memory. 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. Volatile memory can be random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes the following forms: 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).

[0305] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) can be integrated into the processor.

[0306] The device in Figure 10 can be the equipment described in the foregoing embodiments, or it can be a chip or a chip system, such as a system on a chip (SoC). The transceiver can be an input / output circuit or a communication interface; the processor can be a processor, microprocessor, or integrated circuit integrated on the chip. No limitations are imposed here.

[0307] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0308] Figure 11 is a schematic diagram of a chip system 1100 provided in an embodiment of this application. The chip system 1100 (or may also be called a processing system) includes logic circuits 1110 and input / output interface 1120.

[0309] The logic circuit 1110 can be a processing circuit in the chip system 1100. The logic circuit 1110 can be coupled to a memory unit, calling instructions from the memory unit, enabling the chip system 1100 to implement the methods and functions of the embodiments of this application. The input / output interface 1120 can be an input / output circuit in the chip system 1100, outputting processed information from the chip system 1100, or inputting data or signaling information to be processed into the chip system 1100 for processing.

[0310] Specifically, for example, if the terminal device is equipped with the chip system 1100, the logic circuit 1110 is coupled to the input / output interface 1120, and the input / output interface 1120 can input uplink resource configuration information to the logic circuit 1110 for processing. Similarly, if the network device is equipped with the chip system 1100, the logic circuit 1110 is coupled to the input / output interface 1120, and the input / output interface 1120 can output uplink resource configuration information to the terminal device.

[0311] As one approach, the chip system 1100 is used to implement operations performed by devices (such as terminal devices, or network devices, etc.) in the various method embodiments described above.

[0312] For example, logic circuit 1110 is used to implement processing-related operations performed by a device (such as a terminal device or a network device) in the above method embodiments; input / output interface 1120 is used to implement sending and / or receiving-related operations performed by a device (such as a terminal device or a network device) in the above method embodiments.

[0313] This application also provides a computer-readable storage medium storing computer instructions for implementing the methods executed by a device (such as a terminal device or a network device) in the above-described method embodiments.

[0314] For example, when the computer program is executed by a computer, it enables the computer to implement the methods described in the embodiments of the above methods, which are executed by a device (such as a terminal device or a network device).

[0315] This application also provides a computer program product comprising instructions which, when executed by a computer, implement the methods described above as being executed by a device (such as a terminal device or a network device).

[0316] This application also provides a communication system that includes the terminal devices and / or network devices described in the embodiments above. For example, the communication system includes the terminal devices and / or network devices shown in the embodiments of FIG8 to FIG9.

[0317] The explanations and beneficial effects of the relevant contents in any of the devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0318] In the several embodiments provided in this application, it should be understood that the disclosed apparatus 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 mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of apparatus or units may be electrical, mechanical, or other forms.

[0319] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. For example, the computer can be a personal computer, a server, or a network device, etc. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks, SSDs). For example, the aforementioned available media include, but are not limited to, USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks, and other media capable of storing program code.

[0320] 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 technical scope 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, include: Receive the first uplink resource configuration information; Uplink messages are sent using the uplink resources indicated by the first uplink resource configuration information; It has been determined that the uplink message transmission failed. After the first backoff time is delayed, the uplink message is retransmitted.

2. The method according to claim 1, characterized in that, The method further includes: Start a window or timer after sending the uplink message; Determining that the uplink message transmission failed includes: The uplink message transmission is determined to have failed if at least one of the following events occurs: The window or the timer expires and no downlink message is received; or, If the window or timer expires, and a downlink message is received before the window or timer expires, the downlink message is not scrambled with a first Radio Network Temporary Identifier (RNTI), the first RNTI is determined based on uplink resources indicated by the first uplink resource configuration information, or the first RNTI is a public RNTI; or... If the window or the timer expires, and a downlink message is received before the window or the timer expires, the identifier of the terminal device included in the downlink message does not match the identifier of the terminal device included in the uplink message; or, A downlink control information (DCI) is received before the window or timer expires, the DCI indicating that the uplink message transmission has failed.

3. The method according to claim 1 or 2, characterized in that, Retransmit the uplink message, including: The uplink message is retransmitted using the uplink resources indicated by the first uplink resource configuration information.

4. The method according to claim 1 or 2, characterized in that, The method further includes: Receive the second uplink resource configuration information; Retransmit the uplink message, including: The uplink message is retransmitted via the uplink resources indicated by the second uplink resource configuration information.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: Receive backoff time parameter information, the backoff time parameter information being used to determine the first backoff time, the backoff time parameter information including one or more of the following: a second backoff time, an index of the second backoff time; The first backoff time is randomly selected between 0 and the second backoff time.

6. The method according to any one of claims 1 to 5, characterized in that, The method further includes: Receive indication information, which is used to indicate backoff in the event of uplink transmission failure.

7. The method according to claim 2, characterized in that, The method further includes: Receive the public RNTI.

8. The method according to claim 2 or 7, characterized in that, The DCI is scrambled using the first RNTI, and the DCI contains third uplink resource configuration information.

9. A communication method, characterized in that, include: Send the first uplink resource configuration information; Receive uplink messages through the uplink resources indicated by the first uplink resource configuration information; Send a downlink message and / or downlink control information (DCI), wherein the downlink message or the DCI is used to determine that the uplink message transmission failed.

10. The method according to claim 9, characterized in that, The downlink message is not scrambled with the first Radio Network Temporary Identifier (RNTI). The first RNTI is determined based on the uplink resources indicated by the first uplink resource configuration information, or the first RNTI is a public RNTI. Alternatively, the identifier of the terminal device included in the downlink message does not match the identifier of the terminal device included in the uplink message. The DCI is used to indicate that the uplink message transmission failed.

11. The method according to claim 9 or 10, characterized in that, The method further includes: Send backoff time parameter information, which is used to determine a first backoff time. The backoff time parameter information includes one or more of the following: a second backoff time, an index of the second backoff time; the first backoff time is between 0 and the second backoff time.

12. The method according to any one of claims 9 to 11, characterized in that, The method further includes: Send an instruction message, which is used to indicate backoff in the event of uplink transmission failure.

13. The method according to any one of claims 9 to 12, characterized in that, The DCI is scrambled using a first RNTI, which is determined based on the uplink resources indicated by the first uplink resource configuration information, or the first RNTI is a common RNTI, and the DCI includes third uplink resource allocation information.

14. The method according to claim 10 or 13, characterized in that, The method further includes: Send the public RNTI.

15. A communication device, characterized in that, Includes modules or units for performing the method according to any one of claims 1 to 8.

16. A communication device, characterized in that, Includes modules or units for performing the method according to any one of claims 9 to 14.

17. A communication device, characterized in that, The device includes at least one processor, which is configured to execute a computer program or instructions to cause the device to perform the method of any one of claims 1 to 8, or to cause the device to perform the method of any one of claims 9 to 14.

18. The apparatus according to claim 17, characterized in that, The device further includes a memory for storing the computer program or instructions; and / or, The device further includes a communication interface coupled to the at least one processor, the communication interface being used for inputting and / or outputting information.

19. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed on a communication device or computer, cause the communication device to perform the method as described in any one of claims 1 to 8, or cause the communication device to perform the method as described in any one of claims 9 to 14.

20. A computer program product, characterized in that, The computer program product includes a computer program or instructions for performing the method as described in any one of claims 1 to 8, or the computer program product includes a computer program or instructions for performing the method as described in any one of claims 9 to 14.

Images