Wireless communication method and communication apparatus

Abstract

Provided in the present application are a wireless communication method and a communication apparatus, which facilitate reducing the signaling overhead of uplink data transmission. The method comprises: receiving first configuration information sent by a first network device, wherein the first configuration information is used for configuring a preconfigured uplink resource, and the preconfigured uplink resource is shared by a plurality of terminal devices within the coverage range of a plurality of network devices; and on the basis of the preconfigured uplink resource, sending to the first network device a message 3 in a random access procedure.

Description

Wireless communication method and communication apparatus

[0001] The present application claims priority to the Chinese Patent Application No. 202410729598.1, filed on June 5, 2024, and entitled "Wireless communication method and communication apparatus", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present application relates to the field of communication technology, and in particular, to a wireless communication method and a communication apparatus. BACKGROUND

[0003] With the development of communication technology, some new technical requirements are proposed, for example, how to directly transmit message 3 without transmitting message 1 and message 2 in the random access process, so as to reduce the signaling overhead of uplink data transmission. However, for some communication systems with large coverage range and frequent cell changes (such as non-terrestrial network (NTN) communication systems), how to implement the above technical requirements does not have a clear technical solution at present. SUMMARY

[0004] The present application provides a wireless communication method and a communication apparatus, which are beneficial to reduce the signaling overhead of uplink data transmission.

[0005] In a first aspect, a wireless communication method is provided, and the method is applied to a first terminal device. The method comprises: receiving first configuration information sent by a first network device, wherein the first configuration information is used to configure a preconfigured uplink resource, and the preconfigured uplink resource is shared by a plurality of terminal devices within the coverage range of a plurality of network devices; and sending message 3 in a random access process to the first network device based on the preconfigured uplink resource.

[0006] Based on the above technical solution, a network device (such as a first network device) can configure a preconfigured uplink resource shared by a plurality of terminal devices within the coverage range of a plurality of network devices for a terminal device (such as a first terminal device), that is, the preconfigured uplink resource can be shared by a plurality of terminal devices and multiplexed by a plurality of network devices. Since the preconfigured uplink resource is multiplexed by a plurality of network devices, even if the cell changes frequently, the terminal device can use the preconfigured uplink resource to send message 3 to the current cell, so as to meet the demand of frequent cell changes. In addition, since the preconfigured uplink resource is shared by a plurality of terminal devices, it is not necessary to configure a dedicated preconfigured uplink resource for each terminal device, which can reduce the demand for preconfigured uplink resources and is beneficial to improve the resource utilization rate. Therefore, the scheme of the present application embodiment can meet the demand of the communication system with large coverage range and frequent cell changes.

[0007] With reference to the first aspect, in some embodiments of the first aspect, the sending, based on the preconfigured uplink resource, the message 3 in the random access procedure to the first network device comprises: selecting a first uplink resource from the preconfigured uplink resource; and sending the message 3 on the first uplink resource using a first orthogonal code corresponding to the first uplink resource.

[0008] The terminal device in the embodiments of the present application can send the message 3 on the selected first uplink resource using the orthogonal code. By sending the message 3 using the orthogonal code, multiple terminal devices can share the same uplink resource in a code division multiplexing manner, which is conducive to improving the utilization rate of the uplink resource, thereby facilitating a reduction in the number of preconfigured uplink resources.

[0009] With reference to the first aspect, in some embodiments of the first aspect, the first configuration information is further used for configuring a plurality of orthogonal codes corresponding to the preconfigured uplink resource, and the first orthogonal code belongs to the plurality of orthogonal codes.

[0010] The orthogonal code used by the terminal device in the embodiments of the present application can be configured by the network device. By configuring the available orthogonal code for the terminal device by the network device, the complexity of the terminal device in determining the orthogonal code can be reduced, thereby reducing the complexity of the terminal device in sending the message 3.

[0011] With reference to the first aspect, in some embodiments of the first aspect, the first orthogonal code is an orthogonal cover code (OCC).

[0012] With reference to the first aspect, in some embodiments of the first aspect, the method further comprises: receiving downlink control information sent by the first network device, the downlink control information being scrambled using a first radio network temporary identifier (RNTI), and the first RNTI being used to indicate whether a contention conflict in the random access procedure of the first terminal device is resolved.

[0013] The terminal device in the embodiments of the present application can directly determine whether the contention conflict in the random access procedure is resolved through the downlink control information, thereby omitting the transmission of the message 4, simplifying the process of the random access procedure, and being conducive to reducing the signaling overhead of the uplink data transmission. In addition, since the downlink control information itself is scrambled using the RNTI, indicating whether the contention conflict is resolved through the first RNTI scrambling the downlink control information will not cause additional signaling overhead and calculation overhead.

[0014] With reference to the first aspect, in some embodiments of the first aspect, if the first RNTI is generated based on an identifier (ID) of the first terminal device and the first orthogonal code used by the message 3, the first RNTI is used to indicate that the contention conflict in the random access procedure of the first terminal device is resolved.

[0015] The RNTI can be generated by the ID of the first terminal device and a first orthogonal code used in the message 3, so as to improve the security of the RNTI and ensure the uniqueness of the RNTI.

[0016] With reference to the first aspect, in some embodiments of the first aspect, the ID of the first terminal device is carried in the message 3.

[0017] With reference to the first aspect, in some embodiments of the first aspect, the timing advance TA for the first terminal device is included in the downlink control information.

[0018] The TA is indicated by the downlink control information, so that the uplink synchronization of the terminal device and the network device can be ensured without additional signaling overhead.

[0019] With reference to the first aspect, in some embodiments of the first aspect, the first configuration information is carried in a broadcast message.

[0020] The first configuration information is sent by the broadcast message, so that the sending process of the first configuration information can be simplified, and the purpose of sharing the preconfigured uplink resource by multiple terminal devices can be easily achieved.

[0021] With reference to the first aspect, in some embodiments of the first aspect, the first terminal device is a terminal device in a non-terrestrial network communication system.

[0022] In a second aspect, a wireless communication method is provided, which is applied to a first network device and includes: sending first configuration information to a first terminal device, the first configuration information being used for configuring a preconfigured uplink resource, the preconfigured uplink resource being shared by multiple terminal devices within a coverage range of multiple network devices; and receiving a message 3 in a random access process, the message 3 being sent by the first terminal device based on the preconfigured uplink resource.

[0023] With reference to the second aspect, in some embodiments of the second aspect, the message 3 is sent by using a first orthogonal code, the first orthogonal code corresponding to a first uplink resource, the first uplink resource being selected by the first terminal device from the preconfigured uplink resource.

[0024] With reference to the second aspect, in some embodiments of the second aspect, the first configuration information is further used for configuring multiple orthogonal codes corresponding to the preconfigured uplink resource, and the first orthogonal code belongs to the multiple orthogonal codes.

[0025] With reference to the second aspect, in some embodiments of the second aspect, the first orthogonal code is an orthogonal cover code OCC.

[0026] In some embodiments of the second aspect, the method further comprises: sending, to the first terminal device, downlink control information scrambled by a first radio network temporary identifier (RNTI), the first RNTI being used to indicate whether a contention conflict in the random access procedure of the first terminal device is resolved.

[0027] In some embodiments of the second aspect, if the first RNTI is generated based on an identifier (ID) of the first terminal device and a first orthogonal code used in the message 3, the first RNTI is used to indicate that the contention conflict in the random access procedure of the first terminal device is resolved.

[0028] In some embodiments of the second aspect, the ID of the first terminal device is carried in the message 3.

[0029] In some embodiments of the second aspect, timing advance (TA) for the first terminal device is included in the downlink control information.

[0030] In some embodiments of the second aspect, the first configuration information is carried in a broadcast message.

[0031] In some embodiments of the second aspect, the first terminal device is a terminal device in a non-terrestrial network communication system.

[0032] In a third aspect, a communication apparatus is provided, which is configured to execute the method in any possible implementation of the first aspect. Specifically, the apparatus includes modules for performing the method in any possible implementation of the first aspect.

[0033] In a fourth aspect, another communication apparatus is provided, which is configured to execute the method in any possible implementation of the second aspect. Specifically, the apparatus includes modules for performing the method in any possible implementation of the second aspect.

[0034] In a fifth aspect, a further communication apparatus is provided, which includes a processor coupled with a memory, and configured to execute instructions in the memory to implement the method in any possible implementation of the first aspect or the second aspect. Optionally, the apparatus further includes the memory. Optionally, the apparatus further includes a communication interface, and the processor is coupled with the communication interface.

[0035] In an implementation, the apparatus is a terminal device (or a network device). When the apparatus is a terminal device (or a network device), the above communication interface can be a transceiver, or an input / output interface.

[0036] In another implementation, the apparatus is a chip configured in a terminal device (or a network device). When the apparatus is a chip configured in a terminal device (or a network device), the communication interface can be an input / output interface.

[0037] In a sixth aspect, a processor is provided, including an input circuit, an output circuit and a processing circuit. The processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor performs the method in any possible implementation of the first aspect or the second aspect.

[0038] In a specific implementation process, the processor can be a chip, the input circuit can be an input pin, the output circuit can be an output pin, and the processing circuit can be a transistor, a gate circuit, a flip-flop and various logic circuits, etc. The input signal received by the input circuit can be received and input by, for example but not limited to, a receiver, the signal output by the output circuit can be output to and transmitted by, for example but not limited to, a transmitter, and the input circuit and the output circuit can be the same circuit which is used as the input circuit and the output circuit at different times. The embodiments of the present application do not limit the specific implementation of the processor and various circuits.

[0039] In a seventh aspect, a processing apparatus is provided, including a processor and a memory. The processor is configured to read instructions stored in the memory, and can receive a signal through a receiver and transmit a signal through a transmitter to perform the method in any possible implementation of the first aspect or the second aspect.

[0040] Optionally, the processor is one or more, and the memory is one or more.

[0041] Optionally, the memory can be integrated with the processor, or the memory and the processor can be separately arranged.

[0042] In a specific implementation process, the memory can be a non-transitory memory, for example, a read only memory (ROM), which can be integrated with the processor on the same chip, or can be separately arranged on different chips. The type of the memory and the arrangement of the memory and the processor are not limited in the present application.

[0043] It should be understood that the related data interaction process, for example, the process of transmitting the indication information can be the process of outputting the indication information from the processor, and the process of receiving the capability information can be the process of receiving the input capability information by the processor. Specifically, the processed output data can be output to a transmitter, and the input data received by the processor can come from a receiver. The transmitter and the receiver can be collectively referred to as a transceiver.

[0044] The processing device in the seventh aspect can be a chip. The processor can be implemented by hardware or software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc. When implemented by software, the processor can be a general-purpose processor, which is implemented by reading software codes stored in a memory. The memory can be integrated in the processor or exist independently of the processor.

[0045] In an eighth aspect, a computer program product is provided, which includes a computer program (also referred to as code or instructions), which, when executed, causes a computer to perform the method in any possible implementation of the first aspect or the second aspect.

[0046] In a ninth aspect, a computer-readable storage medium is provided, which stores a computer program (also referred to as code or instructions), which, when executed on a computer, causes the computer to perform the method in any possible implementation of the first aspect or the second aspect. BRIEF DESCRIPTION OF DRAWINGS

[0047] FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present application;

[0048] FIG. 2 is a schematic flowchart of a contention-based random access method;

[0049] FIG. 3 shows a change of a cell where a terminal device is located in an NTN communication scenario;

[0050] FIG. 4 is a schematic flowchart of a wireless communication method according to an embodiment of the present application;

[0051] FIG. 5 is a schematic flowchart of another wireless communication method according to an embodiment of the present application;

[0052] FIG. 6 is a schematic block diagram of a communication apparatus according to an embodiment of the present application;

[0053] FIG. 7 is a schematic block diagram of another communication apparatus according to an embodiment of the present application;

[0054] FIG. 8 is a schematic block diagram of yet another communication apparatus according to an embodiment of the present application. DETAILED DESCRIPTION

[0055] FIG. 1 is a schematic diagram of an architecture of a communication system 1000 to which embodiments of the present application are applied. As shown in FIG. 1, the communication system includes a radio access network (RAN) 100, wherein the RAN 100 includes at least one RAN node (e.g., 110a and 110b in FIG. 1, collectively referred to as 110), and can further include at least one terminal device (e.g., 120a-120j in FIG. 1, collectively referred to as 120). The RAN 100 can further include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in FIG. 1). The terminal devices 120 are wirelessly connected to the RAN nodes 110. The terminal devices and the terminal devices, and the RAN nodes and the RAN nodes can be connected to each other by wireline or wirelessly. The communication system 1000 can further include a core network 200. The RAN nodes 110 are connected to the core network 200 wirelessly or by wire. The core network devices in the core network 200 and the RAN nodes 110 in the RAN 100 can be independent and different physical devices, or can be the same physical device integrated with the logical functions of the core network devices and the logical functions of the RAN nodes. The communication system 1000 can further include an Internet 300.

[0056] The RAN 100 can be an evolved universal terrestrial radio access (E-UTRA) system, a new radio (NR) system, and a future wireless access system defined in the 3rd generation partnership project (3GPP). The RAN 100 can also include two or more different wireless access systems described above. The RAN 100 can also be an open RAN (O-RAN).

[0057] A RAN node, also referred to as a radio access network device, a RAN entity, or an access node, is configured to help a terminal device access a communication system through wireless means. In one application scenario, the RAN node can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in a 5th generation (5G) mobile communication system, a next generation NodeB in a 6th generation (6G) mobile communication system, or a base station in a future mobile communication system. The RAN node can be a macro base station (e.g., 110a in FIG. 1), a micro base station or an indoor station (e.g., 110b in FIG. 1), or a relay node or a donor node.

[0058] In another application scenario, a terminal device can access a communication system through wireless means by cooperation of multiple RAN nodes, and different RAN nodes implement part of functions of a base station. For example, the RAN node can be a central unit (CU), a distributed unit (DU), or a radio unit (RU). Here, the CU implements functions of a radio resource control protocol and a packet data convergence protocol (PDCP) of a base station, and can also implement a function of a service data adaptation protocol (SDAP). The DU implements functions of a radio link control layer and a medium access control (MAC) layer of a base station, and can also implement part of functions of a physical layer or all functions of a physical layer. For details of the protocol layers, refer to relevant technical specifications of 3GPP. The RU can be configured to implement functions of transceiving a radio frequency signal. The CU and the DU can be two independent RAN nodes, or can be integrated in the same RAN node, e.g., integrated in a baseband unit (BBU). The RU can be included in a radio frequency device, e.g., included in a remote radio unit (RRU) or an active antenna unit (AAU). The CU can be further divided into two types of RAN nodes, i.e., a CU-control plane and a CU-user plane.

[0059] The RAN node can have different names in different systems, for example, in an O-RAN system, the CU can be referred to as an open CU (O-CU), the DU can be referred to as an open DU (O-DU), and the RU can be referred to as an open RU (O-RU). The RAN node in the embodiments of the present application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module. For example, the RAN node can be a server loaded with a corresponding software module. The embodiments of the present application do not limit the specific technology and specific device form of the RAN node. For ease of description, a base station is described as an example of the RAN node in the following.

[0060] The terminal device is a device with wireless transceiving function, which can send signals to the base station or receive signals from the base station. The terminal device can also be referred to as a terminal, user equipment (UE), mobile station, mobile terminal, etc. The terminal device can be widely applied in various scenarios, such as device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-type communication (MTC), internet of things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, remote medical treatment, smart power grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc. The terminal device can be a mobile phone, tablet computer, computer with wireless transceiving function, wearable device, vehicle, airplane, ship, robot, mechanical arm, smart home device, etc. The embodiments of the present application do not limit the specific technology and specific device form of the terminal device.

[0061] The base station and the terminal device can be fixed in position or movable. The base station and the terminal device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on water surface; can also be deployed on airplanes, balloons and artificial satellites. The embodiments of the present application do not limit the application scenarios of the base station and the terminal device.

[0062] The roles of the base station and the terminal device can be relative. For example, the helicopter or the drone 120i in FIG. 1 can be configured as a mobile base station, and for the terminal device 120j that accesses the wireless access network 100 through 120i, 120i is a base station; but for the base station 110a, 120i is a terminal device, that is, 110a communicates with 120i through a wireless air interface protocol. Of course, 110a and 120i can also communicate through a base station-to-base station interface protocol, and in this case, 120i is also a base station relative to 110a. Therefore, the base station and the terminal device can be collectively referred to as a communication device, and 110a and 110b in FIG. 1 can be referred to as a communication device with a base station function, and 120a-120j in FIG. 1 can be referred to as a communication device with a terminal function.

[0063] The base station and the terminal device, the base station and the base station, and the terminal device and the terminal device can communicate through a licensed frequency spectrum, an unlicensed frequency spectrum, or both. They can communicate through a frequency spectrum below 6 gigahertz (GHz), a frequency spectrum above 6 GHz, or both. The embodiments of the present application do not limit the frequency spectrum resources used for wireless communication.

[0064] In the embodiments of the present application, the functions of the base station can also be performed by a module (such as a chip) in the base station or a control subsystem containing base station functions. The control subsystem containing base station functions herein can be a control center in the above-mentioned application scenarios such as smart grids, industrial control, intelligent transportation, and smart cities. The functions of the terminal device can also be performed by a module (such as a chip or a modem) in the terminal device or a device containing terminal device functions.

[0065] In the present application, the base station sends a downlink signal or downlink information to the terminal device, and the downlink information is carried on a downlink channel; the terminal device sends an uplink signal or uplink information to the base station, and the uplink information is carried on an uplink channel. In order to communicate with the base station, the terminal device needs to establish a wireless connection with a cell controlled by the base station. The cell that establishes a wireless connection with the terminal device is called a service cell of the terminal device. When the terminal device communicates with the service cell, it will also be interfered by signals from neighboring cells.

[0066] It can be understood that, in the embodiments of the present application, the physical downlink shared channel (PDSCH), the physical downlink control channel (PDCCH) and the physical uplink shared channel (PUSCH) are only examples of a downlink data channel, a downlink control channel and an uplink data channel, respectively. In different systems and different scenarios, data channels and control channels can have different names, and the embodiments of the present application do not limit this.

[0067] Currently, three RRC states of terminal devices are defined in the protocol: an RRC connected (RRC_CONNECTED) state, an RRC idle (RRC-IDLE) state and an RRC inactive (RRC-INACTIVE) state.

[0068] The RRC connected state can refer to a state of a terminal device after completing a random access process and before performing RRC release. An RRC connection exists between the terminal device and a network device (for example, an access network device). In the RRC connected state, the terminal device can perform data transmission with the network device, such as downlink data transmission and / or uplink data transmission. Alternatively, the terminal device can also perform transmission of a terminal device-specific data channel and / or control channel with the network device to transmit specific information or unicast information of the terminal device.

[0069] The RRC idle state refers to a state of a terminal device when the terminal device camps in a cell but does not perform random access. The terminal device usually enters the RRC idle state after being powered on or after RRC release. In the RRC idle state, there is no RRC connection between the terminal device and a network device (for example, a camping network device), and the network device does not store a context of the terminal device. The network device does not establish a connection for the terminal device with a core network. If the terminal device needs to enter the RRC connected state from the RRC idle state, an RRC connection establishment process needs to be initiated.

[0070] The RRC inactive state is a state defined to reduce air interface signaling, quickly recover a wireless connection and quickly recover data services. The RRC inactive state is a state between the connected state and the idle state. The terminal device has previously entered the RRC connected state and then released the RRC connection with the network device, but the network device saves the context of the terminal device. In addition, the connection for the terminal device established by the network device with the core network is not released, that is, the user plane bearer and the control plane bearer between the RAN and the CN are still maintained, that is, the CN-NR connection exists.

[0071] The terminal device in the RRC idle state and the RRC inactive state can initiate random access to the network device. There are two ways of random access, one is contention-based random access, and the other is non-contention-based random access. The embodiments of the present application mainly relate to contention-based random access. The contention-based random access process will be introduced below in combination with FIG. 2.

[0072] Referring to FIG. 2, in step S210, the terminal device sends message 1 (Msg1) in the random access process to the network device. The Msg1 can include a preamble.

[0073] The terminal device can select a random access channel (RACH) resource and a preamble, and send the selected preamble on the selected resource. The RACH resource can also be referred to as a physical random access channel (PRACH) resource.

[0074] The network device can send the configuration information of the RACH to the terminal device in the form of broadcast. The configuration information of the RACH can include the configuration information of the time-frequency resource of the RACH and the configuration information of the starting preamble root sequence. The configuration information of the RACH can be carried in the system message. The terminal device can determine the RACH resource and the preamble based on the configuration information of the RACH.

[0075] In step S220, the network device sends the Msg2 to the terminal device. The Msg2 can also be referred to as a random access response (RAR). The Msg2 can be carried by the PDCCH.

[0076] After the terminal device sends the Msg1, a random access response time window can be started, and the terminal device monitors the PDCCH scrambled by the random access-radio network temporary identifier (RA-RNTI) in the time window.

[0077] The preamble sent by the terminal device can also be included in the Msg2. If the terminal device receives the PDCCH scrambled by the RA-RNTI, and the Msg2 contains the preamble sent by the terminal device, the terminal device can consider that the random access response is successfully received.

[0078] After the terminal device successfully receives the PDCCH, the terminal device can obtain a PDSCH scheduled by the PDCCH, and the PDSCH contains the RAR. The RAR can contain multiple information. For example, a backoff indicator (BI) can be contained in a subheader of the RAR, and the BI can be used to indicate a backoff time for retransmitting the Msg1; a random access preamble identification (RAPID) in the RAR indicates a preamble index received by the network device; a timing advance group (TAG) can be contained in a payload of the RAR, and the TAG can be used to adjust an uplink timing; an uplink grant (UL grant) can also be contained in the RAR, and the UL grant can be used to schedule an uplink resource indication of the Msg3; and a temporary cell-radio network temporary identifier (C-RNTI) can also be contained in the RAR, and the terminal device can use the temporary C-RNTI to decode a PDCCH of the Msg4 for initial access of the terminal device.

[0079] In step S230, the terminal device sends the Msg3 to the network device. The terminal device can send the Msg3 on the UL grant scheduled by the network device. The Msg3 can also be referred to as a Radio Resource Control (RRC) connection establishment request message.

[0080] In step S240, the network device sends the Msg4 to the terminal device.

[0081] The Msg4 has two functions, one is for contention resolution, and the other is to send an RRC configuration message to the terminal device. If the terminal device carries a C-RNTI in Msg3, Msg4 adopts PDCCH scheduling scrambled by the C-RNTI, and accordingly, the terminal device can use the C-RNTI in Msg3 to decode the PDCCH to obtain Msg4. If the terminal device does not carry a C-RNTI in Msg3, such as initial access, Msg4 can adopt PDCCH scheduling scrambled by a temporary C-RNTI, and accordingly, the terminal device can use the temporary C-RNTI in Msg2 to decode the PDCCH to obtain Msg4. After the terminal device successfully decodes the PDCCH, the terminal device obtains the PDSCH carrying Msg4. The terminal device can compare the common control channel (CCCH) service data unit (SDU) in the PDSCH with the CCCH SDU in Msg3, and if they are the same, it indicates that the contention resolution is successful.

[0082] In some communication systems, a terminal device in an RRC idle state and an RRC inactive state needs to enter an RRC connected state through a random access process before it can send uplink data and / or receive downlink data. However, for small data packets, if the data packets are still transmitted in the above manner, the signaling overhead required for random access will be much larger than the signaling overhead required for transmitting the data packets, that is, this data transmission mechanism will result in large RRC signaling overhead and large energy consumption of the terminal device. To solve the above problem, an early data transmission (EDT) mechanism is introduced in some systems (such as IoT systems or narrowband systems). For a terminal device in an RRC idle state and an RRC inactive state, the terminal device can directly transmit data with a network device without entering an RRC connected state.

[0083] In some implementations, the network device can configure a dedicated preconfigured uplink resource (PUR) for the terminal device through dedicated signaling. The terminal device can directly send uplink data to the network device using the PUR without initiating random access. The PUR can be a periodic PUR, or a semi-static PUR or an aperiodic PUR. This mechanism is also referred to as an IoT PUR mechanism.

[0084] In some implementations, the network device can further configure a PUR search space window (PUR SS window) to the terminal device. The terminal device can detect a downlink message transmitted by the network device within the PUR SS window. The downlink message may, for example, include one or more of an acknowledgement (ACK), a fall back indication, and retransmission scheduling information.

[0085] With the development of technology, new communication systems, such as NTN communication systems, are introduced. The NTN communication system is described below.

[0086] The NTN communication system provides communication services to users in a non-terrestrial manner. The non-terrestrial manner may, for example, include a satellite or an unmanned aircraft system (UAS) platform.

[0087] For terrestrial network communication, scenarios such as oceans, mountains, deserts, and the like cannot be covered by land communication. Or, considering the cost of building and operating communication equipment, land communication usually does not cover sparsely populated areas. Compared with terrestrial network (TN) communication, NTN has many advantages. First, NTN communication can be free of user geographical restrictions. For NTN communication networks, there are no geographical restrictions. In theory, a satellite can orbit the earth, so every corner of the earth can be covered by satellite communication. And the area covered by NTN communication equipment is much larger than that covered by terrestrial communication equipment. For example, in satellite communication, a satellite can cover a large area of land. Second, NTN communication has great social value. NTN communication can achieve coverage at a low cost, for example, satellite communication can cover remote mountainous areas or poor countries or regions at a low cost. This can enable people in these areas to enjoy advanced voice communication and mobile Internet technology, which is conducive to narrowing the digital gap with developed areas and promoting the development of these areas. Third, NTN communication has a long communication distance and does not significantly increase the cost of communication. In addition, NTN communication has high stability. For example, NTN communication is not limited by natural conditions, and can be used even in the event of natural disasters.

[0088] According to the difference of the orbit height, the communication satellite can be divided into low-earth orbit (LEO) satellite, medium-earth orbit (MEO) satellite, geostationary earth orbit (GEO) satellite, high elliptical orbit (HEO) satellite, etc.

[0089] In order to ensure the coverage of the satellite and improve the system capacity of the whole satellite communication system, the satellite can adopt multi-beam coverage of the ground, that is, a plurality of beam footprints can constitute the field of view of the satellite. For example, a satellite can form dozens or even hundreds of beams to cover the ground. Among them, a satellite beam can cover a ground area with a diameter of dozens to hundreds of kilometers.

[0090] With the development of technology, people's demand for the uplink capacity of the IoT NTN communication system is getting higher and higher, therefore, it is necessary to enhance the uplink capacity of the IoT NTN communication system. Especially for the transmission enhancement of small data packets, people hope to further reduce the uplink and downlink signaling overhead on the basis of the existing EDT mechanism. The enhancement mode can include the following two modes:

[0091] 1. Direct transmission of Msg3 without transmission of Msg1 and Msg2;

[0092] 2. More efficient transmission of Msg4 or RRC EarlyDataComplete message.

[0093] The current IoT PUR mechanism is more in line with the above requirements. That is, the uplink PUSCH resource can be reserved for the terminal device through UE-specific signaling, so as to realize the requirement that the terminal device directly transmits data without transmitting Msg1 and Msg2 in the idle state and the inactive state.

[0094] However, if the above IoT PUR mechanism is applied in the IoT NTN scenario, there will be some problems.

[0095] For example, in the current IoT PUR mechanism, the PUR is configured by dedicated signaling in the connected state, and the PUR is only valid for the current cell. That is, if the terminal device receives the PUR configured by cell 1, the PUR can only be used for the terminal device to send uplink data to cell 1, and cannot be used for the terminal device to send uplink data to other cells. However, for the IoT NTN communication system, the network device (such as the most common MEO satellite and LEO satellite) has a high moving speed, and the coverage time of one NTN cell is generally only a few minutes, so the frequent change of the serving cell is inevitable. However, the current PUR configuration is only valid for the current cell, which cannot meet the needs of frequent changes of the cell in the NTN communication system.

[0096] For example, in the current IoT PUR mechanism, the PUR is configured by dedicated signaling in the connected state, and the PUR is only valid for the current cell. That is, if the terminal device receives the PUR configured by cell 1, the PUR can only be used for the terminal device to send uplink data to cell 1, and cannot be used for the terminal device to send uplink data to other cells. However, for the IoT NTN communication system, the network device (such as the most common MEO satellite and LEO satellite) has a high moving speed, and the coverage time of one NTN cell is generally only a few minutes, so the frequent change of the serving cell is inevitable. However, the current PUR configuration is only valid for the current cell, which cannot meet the needs of frequent changes of the cell in the NTN communication system.

[0097] For example, in the current IoT PUR mechanism, the PUR is configured by dedicated signaling in the connected state, and the PUR is only valid for the current cell. That is, if the terminal device receives the PUR configured by cell 1, the PUR can only be used for the terminal device to send uplink data to cell 1, and cannot be used for the terminal device to send uplink data to other cells. However, for the IoT NTN communication system, the network device (such as the most common MEO satellite and LEO satellite) has a high moving speed, and the coverage time of one NTN cell is generally only a few minutes, so the frequent change of the serving cell is inevitable. However, the current PUR configuration is only valid for the current cell, which cannot meet the needs of frequent changes of the cell in the NTN communication system.

[0098] As can be seen from the above, there is currently no mechanism that can meet the needs of enhancing uplink capacity in the IoT NTN communication system. It should be noted that the above is only an example of the IoT NTN communication system, and the scheme of the embodiments of the present application can also be applied to other communication scenarios as long as the communication scenario has the above technical needs.

[0099] To solve the above problems, the application proposes that the network device can configure a PUR shared by multiple terminal devices in the coverage range of multiple network devices for the terminal device, that is, the PUR can be shared by multiple terminal devices and multiplexed by multiple network devices. Since the PUR is multiplexed by multiple network devices, even if the NTN cell changes quickly, the terminal device can use the PUR to send Msg3 to the current NTN cell, thereby meeting the demand for frequent changes of NTN cells. In addition, since the shared PUR is shared by multiple terminal devices, a dedicated PUR does not need to be configured for each terminal device, which can reduce the demand for PUR resources and improve resource utilization. Therefore, the scheme of the embodiments of the application can meet the demand for enhancing uplink capacity in the IoT NTN communication system.

[0100] The wireless communication method provided by the embodiments of the application will be described in detail below in combination with FIG. 4. The method shown in FIG. 4 is described from the perspective of device interaction. The specific form and quantity of each device shown are only examples and should not constitute any limitation on the implementation of the method provided by the application. The communication method of the embodiments of the application will be described in detail below with the network device and the terminal device as the execution subject.

[0101] It should be understood that the terminal device in the embodiments of the application can be the terminal device itself, or a chip, chip system or processor supporting the terminal device to implement the communication method, or a logic module or software capable of implementing all or part of the terminal device. The network device in the embodiments of the application can be the network device itself, or a chip, chip system or processor supporting the network device to implement the communication method, or a logic module or software capable of implementing all or part of the network device.

[0102] Referring to FIG. 4, in step S410, the first network device sends first configuration information to the first terminal device.

[0103] The first network device can be any of the network devices described above, and the first network device can be an access network device. The first network device can be any of the multiple network devices described above. Taking the NTN communication system as an example, the first network device can be a network device in the NTN communication system.

[0104] The first terminal device can be any of the terminal devices described above. The first terminal device can be any of the multiple terminal devices described above. Taking the NTN communication system as an example, the first terminal device can be a terminal device in the NTN communication system.

[0105] The first configuration information can be used to configure a preconfigured uplink resource, i.e., a PUR. The PUR can include one or more uplink resources. In some implementations, the PUR can be a resource set, which can include one or more uplink resources. In other implementations, the PUR can be a resource list, which can include one or more uplink resources.

[0106] In some implementations, the PUR can be an uplink resource for transmitting a Msg3. The PUR can include a time domain resource and / or a frequency domain resource. Through the time domain resource and / or the frequency domain resource, the terminal device can transmit the Msg3 to the network device. The PUR can be a PUSCH resource. The terminal device transmitting the Msg3 to the network device can also be understood as the terminal device transmitting uplink data to the network device.

[0107] In some implementations, the PUR can be replaced by a preconfigured resource, a reserved resource, a reserved uplink resource, a pre-prepared resource, a pre-prepared uplink resource, etc.

[0108] In some implementations, the PUR can be shared or shared by multiple terminal devices within the coverage of multiple network devices. That is, multiple terminal devices within the coverage of multiple network devices can use the PUR, or the PUR is applicable to multiple terminal devices within the coverage of multiple network devices. Taking an NTN communication system as an example, the multiple network devices can be all network devices (such as all satellites) in the NTN communication system, or the multiple network devices can be part of the network devices (such as part of the satellites) in the NTN communication system. The multiple terminal devices can be all terminal devices within the coverage of the multiple network devices, or part of the terminal devices within the coverage of the multiple network devices. For example, a group of PURs can be configured for part of the terminal devices within the coverage of the multiple network devices, and another group of PURs can be configured for another part of the terminal devices within the coverage of the multiple network devices. The terminal devices within the coverage of the network devices can be understood as the terminal devices within the coverage of a cell (such as an NTN cell).

[0109] For example, assuming that the plurality of network devices include network device 1, network device 2, and network device 3, the coverage range of network device 1 includes terminal device a and terminal device b, the coverage range of network device 2 includes terminal device c and terminal device d, and the coverage range of network device 3 includes terminal device e and terminal device f, if the terminal devices a-f are configured with PUR, the terminal devices a-f can all use the PUR. Taking terminal device a as an example, when terminal device a is in the coverage range of network device 1, terminal device a can use the PUR to send Msg3 to network device 1. As the terminal device and / or network device moves, when terminal device a is in the coverage range of network device 2, terminal device a can still use the PUR to send Msg3 to network device 2. Similarly, when terminal device a is in the coverage range of network device 3, terminal device a can use the PUR to send Msg3 to network device 3. The above is only an example of terminal device a, and other terminal devices are similar, that is, terminal devices b-f can use the PUR to send Msg3 to network devices 1-3.

[0110] In step S420, the first terminal device sends Msg3 in the random access process to the first network device based on the preconfigured uplink resource.

[0111] In some implementations, the first terminal device can select a first uplink resource from the PUR and send Msg3 on the first uplink resource. The first uplink resource can be randomly selected by the first terminal device from the plurality of PURs, or the first uplink resource can be selected by the first terminal device from the plurality of PURs according to a first rule, which can be indicated by the network device to the first terminal device or predefined by a protocol. It should be noted that the first uplink resource can also be referred to as the first PUR. The first uplink resource can be a time domain resource and / or a frequency domain resource. In some implementations, the first uplink resource can be a PUSCH resource.

[0112] In some implementations, the number of the plurality of terminal devices can be greater than or equal to 2. The number of PURs configured by the first configuration information can be less than the number of the plurality of terminal devices, that is, the plurality of terminal devices can use the same PUR to send Msg3, in this way, the number of preconfigured resources required can be reduced, so that it is not necessary to configure dedicated resources for each terminal device, which is conducive to meeting the needs of NTN cells with large coverage radius and limited bandwidth.

[0113] In some implementations, the number of the plurality of network devices can be greater than or equal to 2. That is, 2 or more network devices can multiplex the PUR, and the terminal device can use the PUR to send the Msg3 to the current network device regardless of which network device of the plurality of network devices the terminal device is in the coverage of. In this way, even if the NTN cell changes frequently, the terminal device can not need to reacquire the PUR, but can continue to use the previous PUR to send the Msg3 to the network device, thereby meeting the demand of frequent changes of the IoT NTN cell.

[0114] In some implementations, the PUR can be determined by negotiation for the plurality of network devices, such that the PUR determined by negotiation can be used for the plurality of network devices, that is, the plurality of network devices can receive the Msg3 on the PUR.

[0115] In some implementations, the sending manner of the first configuration information can be broadcasting, or the first configuration information is carried in a broadcast message. Through the broadcast message, the first network device can send the first configuration information to the plurality of terminal devices, thereby simplifying the sending process of the first configuration information, and more easily achieving the purpose of sharing the PUR by the plurality of terminal devices. The above-mentioned broadcast message can be a master information block (MIB) message or a system information block (SIB) message, and the SIB message can be, for example, a SIB1 message, a SIB2 message, etc., which are not limited in the embodiments of the present application. The first network device sends the first configuration information through broadcasting, which can enable the first terminal device to receive the first configuration information in the RRC idle state and / or the RRC inactive state, thereby reducing the power consumption of receiving the first configuration information.

[0116] In some implementations, one PUR is used for one terminal device to send the Msg3, in which case the terminal device can directly use the selected uplink resource to send the Msg3. In another implementation, in order to further improve the utilization of resources and improve the uplink capacity, a plurality of terminal devices can use the same PUR to send the Msg3. In order to avoid interference between signals, the terminal device can use an orthogonal code to send the Msg3, and different terminal devices can use different orthogonal codes to send the Msg3 on the same uplink resource. For example, the first terminal device can use a first orthogonal code to send the Msg3 on a first uplink resource, and the second terminal device can use a second orthogonal code to send the Msg3 on a second uplink resource.

[0117] The Msg3 is sent through an orthogonal code, so that multiple terminal devices can share the same PUR through code division multiplexing, thereby facilitating reduction in the number of preconfigured uplink resources. Even in the case of a large cell coverage range, i.e., a large number of terminal devices in the cell coverage range, fewer PURs can be configured to meet the uplink transmission requirements of the terminal devices.

[0118] In some implementations, sending the Msg3 using the orthogonal code can be understood as encoding the Msg3 using the orthogonal code and then sending the encoded Msg3. Multiple terminal devices can use different orthogonal codes to encode their respective Msg3s, so that the encoded multiple Msg3s are orthogonal to each other. The network device can decode the Msg3 based on the mutually orthogonal Msg3s to separate the Msg3s of different terminal devices.

[0119] In some implementations, the first terminal device can use the first orthogonal code to send the Msg3, or in other words, the first terminal device can use the first orthogonal code to send the Msg3 on the first uplink resource. The first orthogonal code can be determined by the first terminal device itself, for example, the first terminal device can calculate the first orthogonal code in a certain manner (such as a manner agreed with the network device), or the first orthogonal code can be indicated to the first terminal device by the network device. By indicating the orthogonal code to the terminal device by the network device, the complexity of the terminal device in determining the orthogonal code can be reduced, thereby reducing the complexity of the terminal device in sending the Msg3.

[0120] In some implementations, the first orthogonal code can be configured to the first terminal device by the first network device. For example, the first configuration information is further used to configure multiple orthogonal codes, or in other words, the first configuration information further includes multiple orthogonal codes, and the first orthogonal code belongs to the multiple orthogonal codes, i.e., the first orthogonal code is one of the multiple orthogonal codes. In some embodiments, each PUR has a corresponding orthogonal code, i.e., one PUR corresponds to one orthogonal code configuration. The orthogonal codes corresponding to different PURs can be the same, different, or partially the same and partially different. In other words, the first configuration information can be used to configure multiple orthogonal codes corresponding to the PUR. The first terminal device can select the first orthogonal code from the orthogonal codes corresponding to the selected uplink resource. For example, if the first terminal device selects the first uplink resource from the PUR, the first terminal device can select the first orthogonal code from the orthogonal codes corresponding to the first uplink resource (i.e., the first orthogonal code corresponds to the first uplink resource), and use the first orthogonal code to send the Msg3.

[0121] In some implementations, the first configuration information can further include the number of available orthogonal codes. By configuring the number of available orthogonal codes, the terminal device can explicitly determine the number of orthogonal codes that can be used, which facilitates the selection of orthogonal codes by the terminal device.

[0122] In some implementations, the first terminal device can select the first uplink resource from the PUR. After selecting the first uplink resource, the first terminal device can transmit the Msg3 on the first uplink resource using the first orthogonal code corresponding to the first uplink resource. The first uplink resource can correspond to a plurality of orthogonal codes, and the first terminal device can select one orthogonal code from the plurality of orthogonal codes, and the selected orthogonal code is the first orthogonal code.

[0123] The orthogonal code in the embodiments of the present application can also be replaced by other terms, such as an orthogonal sequence, which is not specifically limited in the embodiments of the present application. The orthogonal code in the embodiments of the present application can be an orthogonal cover code (OCC), or other types of orthogonal codes. The OCC can also be replaced by an OCC sequence, an OCC code, etc. One orthogonal sequence can include one or more elements, and each element can be referred to as a code element. Taking the orthogonal code [+1, -1] as an example, +1 is a code element, and -1 is also a code element. The length of the orthogonal code refers to the number of code elements included in the orthogonal code. Taking the orthogonal code [+1, -1] as an example, the number of code elements is 2, and the length of the orthogonal code is also 2.

[0124] The embodiments of the present application do not specifically limit the number of code elements included in the orthogonal code, and the number of code elements included in the orthogonal code can be an integer greater than or equal to 2, for example, the number of code elements included in the orthogonal code can be 2, 3, 4, 5, 6, etc. Table 1 shows the case where the orthogonal code includes 4 code elements. It should be noted that Table 1 is only an example for easy understanding and does not limit the present application.

[0125] Table 1

[0126] In some implementations, after the first network device receives the Msg3 sent by the first terminal device, the first network device can send a PDCCH to the first terminal device, and the terminal device can obtain a PDSCH carrying a Msg4 after successfully decoding the PDCCH. The terminal device can determine whether the contention conflict is resolved according to the Msg4.

[0127] In some implementations, in order to simplify the process of random access, or in other words, in order to improve the efficiency of Msg4 transmission, the network device can indicate whether the contention conflict of the random access process is resolved to the terminal device through downlink control information (DCI), so that the transmission of the Msg4 can be omitted, and the process of random access can be simplified. The above-mentioned DCI can also be replaced by PDCCH DCI or PDCCH or downlink information or downlink message, etc.

[0128] The embodiments of the present application do not make specific limitations on the manner of indicating whether the contention conflict is resolved through the DCI. For example, the first network device can indicate whether the contention conflict is resolved to the first terminal device through a first RNTI, where the first RNTI is used to scramble the DCI, and the first terminal device can determine whether the contention conflict is resolved based on the first RNTI. Since the downlink control information itself will be scrambled by the RNTI, indicating whether the contention conflict is resolved through the RNTI will not cause additional signaling overhead and calculation overhead. For another example, the first network device can indicate whether the contention conflict is resolved to the first terminal device through a first key, where the first key is used to encrypt the DCI, and the first terminal device can determine whether the contention conflict is resolved based on the first key.

[0129] The manner of indicating whether the contention conflict is resolved to the first terminal device through the first RNTI scrambling the DCI is introduced as follows. If the first network device determines that the first terminal device succeeds in the contention, the first network device can calculate the first RNTI based on the relevant information of the first terminal device, then scramble the DCI using the first RNTI, and send the scrambled DCI to the first terminal device. That is, if the first RNTI is generated based on the relevant information of the first terminal device, the first RNTI can be used to indicate that the contention conflict of the first terminal device in the random access process is resolved. After receiving the DCI, the first terminal device can obtain the second RNTI using the same calculation manner as the first network device based on the relevant information of the first terminal device. If the first terminal device can correctly descramble the DCI using the second RNTI, the first terminal device can determine that the contention conflict is resolved. If the first terminal device cannot correctly descramble the DCI using the second RNTI, the first terminal device can determine that the contention conflict is not resolved.

[0130] The relevant information of the first terminal device can include an identity (ID) of the first terminal device and / or an orthogonal code used by the first terminal device to send the Msg3. In some implementation manners, the RNTI (such as the first RNTI and / or the second RNTI) can be generated based on the ID of the terminal device. Since the ID of each terminal device is unique, the RNTI generated based on the ID of the terminal device is also unique, thereby uniquely indicating that the contention conflict of a certain terminal device is resolved. In some implementation manners, the RNTI can be generated based on the ID of the terminal device and the orthogonal code used by the terminal device to send the Msg3. By generating the RNTI based on the ID of the terminal device and the orthogonal code, the security of the RNTI can be improved and the uniqueness of the RNTI can be ensured.

[0131] In some implementations, the first terminal device can generate a second RNTI based on the ID of the first terminal device and an orthogonal code used in the message 3. The first terminal device can decode downlink control information sent by the network device based on the second RNTI, and if the downlink control information is successfully decoded, the first terminal device can determine the contention conflict resolution in the random access process. In other words, if the first RNTI is generated based on the ID of the first terminal device and the orthogonal code used by the first terminal device to send the message 3, the first RNTI is used to indicate the contention conflict resolution of the first terminal device in the random access process.

[0132] Generating the RNTI based on the ID of the terminal device and the orthogonal code can refer to generating the RNTI based on the ID of the terminal device and related information of the orthogonal code. The related information of the orthogonal code can include one or more of the following: an index of the orthogonal code, a number of symbols included in the orthogonal code, and a length of the orthogonal code.

[0133] The generation process of the RNTI is described below taking the index of the orthogonal code as an example.

[0134] The orthogonal code selected by the first terminal device is a first orthogonal code, and the index of the first orthogonal code can be indicated to the first terminal device by the first network device. For example, the first network device can configure the information of the orthogonal code and the corresponding index for the first terminal device as shown in Table 1. Alternatively, the first orthogonal code can be determined by the first terminal device and the first network device, and the first terminal device and the first network device can determine the index of the orthogonal code according to the order of the orthogonal code. For example, the index of the first orthogonal code is 0, the index of the second orthogonal code is 1, and so on.

[0135] The RNTI can be generated based on the ID of the terminal device and the index of the orthogonal code. The first terminal device and the first network device can use the same calculation method to obtain the RNTI. The calculation method can be agreed by the first terminal device and the first network device.

[0136] The ID of the terminal device can be carried in the message 3, so that the network device can generate the RNTI based on the ID of the terminal device. The ID of the terminal device carried in the message 3 can refer to the ID of the terminal device carried in the payload of the message 3 or the common control channel (CCCH) payload of the message 3.

[0137] The RNTI in the embodiments of the present application can also be referred to as a PUR RNTI. Taking the orthogonal code as an example, the RNTI generated based on the OCC can also be referred to as an OCC based PUR RNTI.

[0138] It should be noted that whether the contention conflict is resolved in the embodiments of the present application can be replaced by whether the contention conflict is successful, or whether the contention is successful, or whether the contention is resolved, or whether the conflict is resolved, etc. The contention conflict resolution in the embodiments of the present application can be replaced by contention resolution, or conflict resolution, or contention success, etc. The contention conflict not being resolved in the embodiments of the present application can be replaced by contention not being successful, or conflict not being resolved, etc.

[0139] In some implementations, the first network device can also indicate a time window for detecting the DCI to the first terminal device. If the first terminal device does not detect the DCI, or does not correctly decode the DCI, within the time window, the first terminal device can determine that the contention conflict is not resolved. If the first terminal device correctly decodes the DCI within the time window, it means that the Msg3 transmission of the first terminal device is successful, and the first terminal device can determine that the contention conflict is resolved. In some implementations, if the first terminal device does not correctly decode the DCI, the first terminal device can continue to monitor the PDCCH until the time window expires.

[0140] The time window described above can be a period of time after the Msg3 transmission time. The duration of the time window can be indicated by the network device, or predefined by the protocol. The time window described above can be a PUR SS window. In some implementations, the time window described above can also be replaced by a timer, a first time duration, etc.

[0141] In some implementations, in order to avoid waste of PUR, the first network device can also send indication information to the first terminal device to end the PUR process. For example, the first network device can use the layer 1 (L1) ACK to end the PUR process. After the first terminal device receives the L1 ACK sent by the first network device, the first terminal device can end the PUR process.

[0142] In some implementations, the first network device can send the timing advance (TA) for the first terminal device to the first terminal device through the downlink control information. In some cases, the TA of the first terminal device can change, and the first network device can indicate the adjusted TA to the first terminal device. For example, the first network device can use the L2 ACK to indicate the adjusted TA to the first terminal device, so as to ensure the uplink synchronization between the first terminal device and the first network device. In addition, by indicating the TA through the downlink control information, the uplink synchronization between the first terminal device and the first network device can be ensured without additional signaling overhead.

[0143] In some implementations, the first configuration information can comprise PUR information. The PUR information can comprise one or more of the following information: time domain resource, frequency domain resource, modulation and coding scheme (MCS), transport block size (TBS), demodulation reference signal (DMRS) configuration, PDCCH search space, and PDCCH configuration, etc.

[0144] MCS defines the number of useful bits that can be carried within one symbol. One symbol is defined as one resource element (RE), and MCS defines the bits in each RE that can be used for transmitting data. MCS depends on the signal quality in the wireless link, the better the signal quality, the more bits in one symbol can be used for transmitting data, and the worse the signal quality, the fewer bits in one symbol can be used for transmitting data.

[0145] Each PUR has a corresponding TBS. The size of the uplink data transmitted by the terminal device through the PUR cannot exceed the TBS corresponding to the PUR. Therefore, the terminal device can select according to the size of the data to be transmitted and the TBS corresponding to the PUR, so that the selected uplink resource can meet the transmission requirement.

[0146] DMRS is a reference signal for channel demodulation by the terminal device. DMRS can include DMRS on the physical broadcast channel (PBCH), PDCCH and PDSCH.

[0147] The PDCCH search space can include a common search space and a UE-specific search space. The common search space is mainly used by the terminal device when accessing the cell and / or when the cell is switched, while the UE-specific search space is used after the terminal device accesses the cell.

[0148] The PDCCH configuration can include the time domain position and / or the frequency domain position of the PDCCH. The terminal device can receive the PDCCH based on the PDCCH configuration. For example, the terminal device can receive the PDCCH DCI described above based on the PDCCH configuration.

[0149] The method of the embodiments of the present application will be described in detail below in combination with FIG. 5 and in combination with specific examples.

[0150] Referring to FIG. 5, in step S510, the network device sends a broadcast message to the terminal device, and the broadcast message comprises shared PUR configuration. The broadcast message may, for example, be a SIB message.

[0151] The PUR configuration can comprise shared PUR information and OCC configuration corresponding to the PUR. The shared PUR information can comprise one or more of the following information: time domain resource, frequency domain resource, MCS, TBS, DMRS configuration, PDCCH search space, PDCCH configuration, etc.

[0152] The OCC configuration corresponding to the PUR can comprise code word related information and number of available OCCs. The code word related information can comprise OCC information. The number of available OCCs can be understood as the number of OCCs included in the OCC configuration.

[0153] The terminal device receives a system broadcast message and obtains the PUR configuration and the OCC configuration corresponding to the PUR configuration from the broadcast message.

[0154] Before transmitting the Msg3, the terminal device can select a first PUR from the shared PUR and select a first OCC from the OCC configuration corresponding to the first PUR.

[0155] At step S520, the terminal device transmits the Msg3 using the first OCC at the PUSCH resource location corresponding to the first PUR. In addition, the terminal device can carry the UE ID in the Msg3 CCCH payload for subsequent contention resolution.

[0156] The terminal device and the network device can use an agreed algorithm to calculate the OCC based PUR RNTI according to the UE ID in the Msg3 and the information of the first OCC. The information of the first OCC can be the index of the first OCC. The index of the first OCC can be the index of the first OCC configured in the broadcast message, or the index of the first OCC can be determined based on the position of the first OCC in the OCC configuration. For example, the index of the first OCC is 0, the index of the second OCC is 1, and so on.

[0157] At step S530, the network device can use the calculated OCC based PUR RNTI to scramble the PDCCH DCI and transmit the scrambled PDCCH DCI to the terminal device.

[0158] At step S540, the terminal device decodes the PDCCH DCI using the calculated OCC based PUR RNTI within the PUR SS window.

[0159] If the terminal device successfully decodes the PDCCH with the calculated OCC based PUR RNTI within the PUR SS window, it means that the terminal device succeeds in sending the Msg3. Otherwise, the terminal device continues to monitor the PDCCH until the PUR SS window expires.

[0160] Optionally, in some implementations, the method shown in FIG. 5 can further include step S550, the network device can further send the Msg4 to the terminal device. For example, the network device can schedule the PDSCH through the PDCCH, and the PDSCH can carry the Msg4. The terminal device can determine whether the contention conflict is resolved based on the Msg4.

[0161] In addition, the network device can end the PUR procedure using the L1 ACK, or the network device can use the L2 ACK to adjust the TA of the terminal device.

[0162] The method embodiments of the present application are described in detail above in combination with FIGS. 1-5, and the device embodiments of the present application are described below in combination with FIGS. 6-8. It should be understood that the description of the method embodiments and the description of the device embodiments correspond to each other, and therefore, the parts not described in detail can be referred to the foregoing method embodiments.

[0163] FIG. 6 is a schematic block diagram of a communication device according to an embodiment of the present application. As shown in FIG. 6, the communication device 600 includes a receiving module 610 and a sending module 620.

[0164] In a possible implementation, the device 600 can be used to implement the steps corresponding to the terminal device in the method shown in FIG. 4 and / or FIG. 5.

[0165] The receiving module 610 is configured to receive first configuration information sent by a first network device, the first configuration information being used for configuring a preconfigured uplink resource, and the preconfigured uplink resource being shared by a plurality of terminal devices within a coverage range of a plurality of network devices.

[0166] The sending module 620 is configured to send a message 3 in a random access procedure to the first network device based on the preconfigured uplink resource.

[0167] In some possible implementations, the communication device 600 further includes a selecting module configured to select a first uplink resource from the preconfigured uplink resource, and the sending module 620 is configured to send the message 3 on the first uplink resource using a first orthogonal code corresponding to the first uplink resource.

[0168] In some possible implementations, the first orthogonal code is an orthogonal cover code (OCC).

[0169] In a possible implementation, the receiving module 610 is further configured to receive downlink control information sent by the first network device, wherein the downlink control information is scrambled by a first radio network temporary identifier (RNTI), and the first RNTI is used to determine whether a contention conflict in the random access procedure is resolved.

[0170] In a possible implementation, if the first RNTI is generated based on an identifier (ID) of the first terminal device and a first orthogonal code used in the message 3, the first RNTI is used to indicate that the contention conflict in the random access procedure of the first terminal device is resolved.

[0171] In a possible implementation, the ID of the first terminal device is carried in the message 3.

[0172] In a possible implementation, the downlink control information includes a timing advance (TA) for the first terminal device.

[0173] In a possible implementation, the first configuration information is carried in a broadcast message.

[0174] In a possible implementation, the first terminal device is a terminal device in a non-terrestrial network communication system.

[0175] FIG. 7 is a schematic block diagram of a communication apparatus provided by an embodiment of the present application. As shown in FIG. 7, the communication apparatus 700 includes a sending module 710 and a receiving module 720.

[0176] In a possible implementation, the apparatus 700 can be used to implement the steps corresponding to the network device in the methods shown in FIG. 4 and / or FIG. 5.

[0177] The sending module 710 is configured to send first configuration information to a first terminal device, wherein the first configuration information is used to configure a preconfigured uplink resource, and the preconfigured uplink resource is shared by a plurality of terminal devices within coverage ranges of a plurality of network devices.

[0178] The receiving module 720 is configured to receive a message 3 in a random access procedure, wherein the message 3 is sent by the first terminal device based on the preconfigured uplink resource.

[0179] In a possible implementation, the message 3 is sent using a first orthogonal code, wherein the first orthogonal code corresponds to a first uplink resource, and the first uplink resource is selected by the first terminal device from the preconfigured uplink resource.

[0180] In a possible implementation, the first configuration information is further used to configure a plurality of orthogonal codes corresponding to the preconfigured uplink resource, and the first orthogonal code belongs to the plurality of orthogonal codes.

[0181] In some possible implementation, the first orthogonal code is an orthogonal cover code (OCC).

[0182] In some possible implementation, the sending module 710 is further configured to send, to the first terminal device, downlink control information scrambled by a first radio network temporary identifier (RNTI), the first RNTI being used by the first terminal device to determine whether a contention conflict in the random access procedure is resolved.

[0183] In some possible implementation, if the first RNTI is generated based on an identifier (ID) of the first terminal device and the first orthogonal code used in the message 3, the first RNTI is used to indicate that the contention conflict in the random access procedure is resolved.

[0184] In some possible implementation, the ID of the first terminal device is carried in the message 3.

[0185] In some possible implementation, the downlink control information includes a timing advance (TA) for the first terminal device.

[0186] In some possible implementation, the first configuration information is carried in a broadcast message.

[0187] In some possible implementation, the first terminal device is a terminal device in a non-terrestrial network communication system.

[0188] It should be understood that the apparatus 600 and the apparatus 700 are embodied in the form of functional modules herein. The term “module” herein can refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (shared, dedicated or group) and memory that execute one or more software or firmware programs, a combinational logic circuit, and / or other suitable components that provide the described functionality. In one optional example, those skilled in the art can understand that the apparatus 700 can be embodied as the terminal device in the above-described embodiments, and the apparatus 700 can be used to execute each flow and / or step corresponding to the terminal device in the above-described method embodiments. The apparatus 700 can be embodied as the network device in the above-described embodiments, and the apparatus 700 can be used to execute each flow and / or step corresponding to the network device in the above-described method embodiments. To avoid repetition, details are not described herein.

[0189] The apparatus 600 has functions of implementing the corresponding steps performed by the terminal device in the above method, and the apparatus 700 has functions of implementing the corresponding steps performed by the network device in the above method. The above functions can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0190] In embodiments of the present application, the apparatus 600 and the apparatus 700 can also be chips, such as system on chip (SOC) or Modem, etc. Correspondingly, the receiving module and the sending module can be transceiver circuits of the chip, which are not limited herein.

[0191] FIG. 8 is a schematic structural diagram of a communication apparatus according to an embodiment of the present application. The dashed line in FIG. 8 indicates that the unit or module is optional. The apparatus 800 can be used to implement the method described in the above method embodiments. The apparatus 800 can be a chip, a terminal device or a network device.

[0192] The apparatus 800 can include one or more processors 810. The processor 810 can support the apparatus 800 to implement the method described in the above method embodiments. The processor 810 can be a general purpose processor or a dedicated processor. For example, the processor can be a central processing unit (CPU). Alternatively, the processor can also be other general purpose processors, digital signal processors (DSPs), ASICs, field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gates or transistor logic components, discrete hardware components, etc. The general purpose processor can be a microprocessor or the processor can also be any conventional processor.

[0193] The apparatus 800 can also include one or more memories 820. The memory 820 stores programs, which can be executed by the processor 810, so that the processor 810 performs the method described in the above method embodiments. The memory 820 can be independent of the processor 810 or integrated in the processor 810.

[0194] The apparatus 800 can also include a transceiver 830. The processor 810 can communicate with other devices or chips through the transceiver 830. For example, the processor 810 can perform data transceiving with other devices or chips through the transceiver 830.

[0195] The embodiment of the present application further provides a computer readable storage medium for storing a program. The computer readable storage medium can be applied to the terminal device or the network device provided by the embodiment of the present application, and the program causes the computer to execute the method performed by the terminal device or the network device in each embodiment of the present application.

[0196] The embodiment of the present application further provides a computer program product. The computer program product includes a program. The computer program product can be applied to the terminal device or the network device provided by the embodiment of the present application, and the program causes the computer to execute the method performed by the terminal device or the network device in each embodiment of the present application.

[0197] The embodiment of the present application further provides a computer program. The computer program can be applied to the terminal device or the network device provided by the embodiment of the present application, and the computer program causes the computer to execute the method performed by the terminal device or the network device in each embodiment of the present application.

[0198] It should be understood that, in the embodiments of the present application, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that the determination of B according to A does not mean that B is determined only according to A, but B can also be determined according to A and / or other information.

[0199] It should be understood that the term "and / or" in the present application is only to describe the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can mean that A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in the present application generally represents that the front and rear associated objects are in an "or" relationship.

[0200] It should be understood that, in various embodiments of the present application, the size of the sequence number of the above processes does not mean the order of execution, and the execution order of the processes should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0201] In the present application, the sending of information from entity A to entity B can be directly from A to B, or indirectly from A to B via other entities. Similarly, the receiving of information from entity A by entity B can be directly from A by B, or indirectly from A by B via other entities. The entities A and B can be RAN nodes or terminals, or modules within RAN nodes or terminals. The sending and receiving of information can be the exchange of information between RAN nodes and terminals, e.g. between base stations and terminals; the sending and receiving of information can also be the exchange of information between two RAN nodes, e.g. between a CU and a DU; the sending and receiving of information can also be the exchange of information between different modules within one apparatus, e.g. between a terminal chip and other modules of the terminal, or between a base station chip and other modules of the base station.

[0202] In several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method can be implemented in other manners. For example, the apparatus embodiments described above are merely schematic, and the division of units is merely a logical function division, and there can be another division manner in actual implementation. For example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections can be indirect couplings or communication connections through some interfaces, devices or units, and can be in electrical, mechanical or other forms.

[0203] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, i.e. can be located in one place, or can be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purposes of the embodiments.

[0204] In addition, each functional unit in the embodiments of the present application can be integrated in one processing unit, or each unit can exist physically as a separate unit, or two or more units can be integrated in one unit.

[0205] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments can be implemented 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 the present application are generated. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode. The computer readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server, data center and the like integrated with one or more available media sets. The available media can be magnetic media (for example, floppy disk, hard disk, magnetic tape), optical media (for example, digital video disc (DVD)) or semiconductor media (for example, solid state disk (SSD)) and the like.

[0206] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical range disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method of wireless communication, the method comprising: The method is applied to a first terminal device, and comprises: receiving first configuration information sent by a first network device, the first configuration information being used for configuring a pre-configured uplink resource, the pre-configured uplink resource being shared by a plurality of terminal devices within a coverage range of a plurality of network devices; based on the pre-configured uplink resource, sending a message 3 in a random access procedure to the first network device.

2. The method of claim 1, wherein, The method further comprises: receiving downlink control information sent by the first network device, the downlink control information being scrambled by a first radio network temporary identifier (RNTI), the first RNTI being used for indicating whether a contention conflict in a random access procedure of the first terminal device is resolved. If the first RNTI is generated based on an identifier (ID) of the first terminal device and a first orthogonal code used by the message 3, the first RNTI is used for indicating that the contention conflict in the random access procedure of the first terminal device is resolved.

3. The method of claim 2, wherein, The ID of the first terminal device is carried in the message 3.

4. The method according to claim 2 or 3, characterized in that, Timing advance (TA) for the first terminal device is included in the downlink control information.

5. The method according to any one of claims 1-4, characterized in that, The first configuration information is carried in a broadcast message. The first terminal device is a terminal device in a non-terrestrial network communication system.

6. The method of claim 5, wherein, The method is applied to a first network device, and comprises:

7. The method of claim 6, wherein, sending first configuration information to a first terminal device, the first configuration information being used for configuring a pre-configured uplink resource, the pre-configured uplink resource being shared by a plurality of terminal devices within a coverage range of a plurality of network devices; 8. The method according to any one of claims 5-7, characterized in that, receiving a message 3 in a random access procedure, the message 3 being sent by the first terminal device based on the pre-configured uplink resource.

9. The method according to any one of claims 1-8, characterized in that, The message 3 is sent using a first orthogonal code, the first orthogonal code corresponding to a first uplink resource, the first uplink resource being selected by the first terminal device from the pre-configured uplink resource.

10. The method according to any one of claims 1-9, characterized in that, The first configuration information is further used for configuring a plurality of orthogonal codes corresponding to the pre-configured uplink resource, the first orthogonal code belonging to the plurality of orthogonal codes.

11. A method of wireless communication, the method comprising: The first orthogonal code is an orthogonal cover code (OCC). The method further comprises: sending downlink control information to the first terminal device, the downlink control information being scrambled by a first radio network temporary identifier (RNTI), the first RNTI being used for indicating whether a contention conflict in a random access procedure of the first terminal device is resolved.

12. The method of claim 11, wherein, If the first RNTI is generated based on an identifier (ID) of the first terminal device and a first orthogonal code used by the message 3, the first RNTI is used for indicating that the contention conflict in the random access procedure of the first terminal device is resolved.

13. The method of claim 12, wherein, ​ 14. The method according to claim 12 or 13, characterized in that, ​ 15. The method according to any one of claims 11-14, characterized in that, ​ ​ 16. The method of claim 15, wherein, ​ 17. The method of claim 16, wherein, The ID of the first terminal device is carried in the message 3.

18. The method according to any one of claims 15-17, characterized by, Timing advance TA for the first terminal device is included in the downlink control information.

19. The method according to any one of claims 11-18, characterized in that, The first configuration information is carried in a broadcast message.

20. The method of any one of claims 11-19, wherein, The first terminal device is a terminal device in a non-terrestrial network communication system.

21. A communications device, characterized by Comprise: A processor coupled with a memory for storing a computer program, which, when invoked by the processor, causes the communication apparatus to perform the method of any one of claims 1-10 or any one of claims 11-20.

Images