Random access method and device

Abstract

The present application provides a random access method and device, capable of reducing the delay of random access. A second communication device sends a first SSB on a first downlink carrier; a first communication device receives the first SSB from the second communication device on the first downlink carrier, wherein the first downlink carrier is used for carrying at least one SSB, the at least one SSB comprises the first SSB, and ROs corresponding to the at least one SSB are on at least two uplink carriers or at least two uplink BWPs; the first communication device sends a RACH preamble sequence to the second communication device on a first RO corresponding to the first SSB.

Description

Method and apparatus for random access

[0001] This application claims priority to the Chinese Patent Application No. 202411306316.3, filed on September 14, 2024, and titled “Method and apparatus for random access”, the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present application relates to the field of communication, and more particularly, to a method and apparatus for random access. BACKGROUND

[0003] In the 5th generation (5G) new radio (NR), there is an association between a synchronization signal block (SSB) and a random access channel (RACH) resource, and a network device can infer the best transmission beam according to the RACH resource used by a terminal device.

[0004] Currently, the RACH is transmitted on an uplink carrier corresponding to a downlink carrier used to transmit the SSB, and one downlink bandwidth part (BWP) of one downlink carrier is associated with one uplink BWP of one uplink carrier. It can be understood that one downlink carrier in one cell is associated with one uplink carrier. How to further improve the flexibility of RACH resource allocation needs to be studied. SUMMARY

[0005] The present application provides a method and apparatus for random access, which can reduce the latency of random access.

[0006] In a first aspect, a method for random access is provided, which can be applied to a first communication apparatus, such as being executed by a first communication apparatus, the first communication apparatus can be a terminal device or a module (such as a circuit, a chip, a chip system or a processor) in a terminal device, and can also be a logical node, a logical module or software that can realize all or part of the functions of a terminal device.

[0007] The method comprises: receiving a first synchronization signal block (SSB) on a first downlink carrier, the first downlink carrier being used to carry at least one SSB, the at least one SSB including the first SSB, and a random access channel (RACH) opportunity (RO) corresponding to the at least one SSB being on at least two uplink carriers or on at least two uplink bandwidth parts (BWPs); and transmitting a RACH preamble sequence on a first RO corresponding to the first SSB.

[0008] Based on the above technical solution, the RO corresponding to the at least one SSB is on at least two uplink carriers or at least two uplink BWP, and the at least one SSB is transmitted through one downlink carrier (first downlink carrier); compared with the solution that the RO corresponding to the at least one SSB is on one uplink carrier (one downlink carrier and one uplink carrier in one cell are associated, or one downlink BWP and one uplink BWP in one cell are associated), the solution provided by the embodiment of the application can shorten the resource period of the RO corresponding to the at least one SSB, can reduce the latency of random access, and in addition, the RACH resource on two carriers or BWP can reduce the probability of random access conflict of the communication device, thereby improving the communication performance.

[0009] With reference to the first aspect, in some implementations of the first aspect, the method further includes: receiving first configuration information, the first configuration information being used to indicate that the first downlink carrier is associated with the at least two uplink carriers or the at least two uplink BWP. Exemplarily, the first configuration information indicates the identity (index) of the first downlink carrier and the identity (index) corresponding to the at least two uplink carriers respectively.

[0010] Based on the above implementation, the association relationship between the first downlink carrier and the at least two uplink carriers or the at least two uplink BWP can be determined according to the first configuration information, the flexibility of RO allocation can be improved, and thus the communication performance can be improved.

[0011] With reference to the first aspect, in some implementations of the first aspect, the method further includes: receiving second configuration information or third configuration information, the second configuration information being used to indicate the RO corresponding to the first SSB, and the first SSB corresponding RO including the first RO, and the third configuration information being used to indicate the RO corresponding to the at least one SSB.

[0012] With reference to the first aspect, in some implementations of the first aspect, the method further includes: determining the RO corresponding to the first SSB according to the second configuration information; or determining the RO corresponding to the first SSB according to the third configuration information and a predefined rule.

[0013] Based on the above implementation, the RO corresponding to the first SSB can be determined through the third configuration information and the predefined rule, the signaling overhead of the configuration information can be reduced, the same RO resource can be determined according to the uniform rule between the communication devices, the flexibility of RO allocation can be improved, and thus the communication performance can be improved.

[0014] In some implementations of the first aspect, the at least one SSB includes the first SSB and a second SSB, the at least two uplink carriers include a first uplink carrier and a second uplink carrier, the RO corresponding to the first SSB is on the first uplink carrier, and the RO corresponding to the second SSB is on the second uplink carrier; or the at least two uplink BWPs include a first uplink BWP and a second uplink BWP, the RO corresponding to the first SSB is on the first uplink BWP, and the RO corresponding to the second SSB is on the second uplink BWP. In this implementation, the RO corresponding to one SSB is on one uplink carrier or one uplink BWP.

[0015] Based on the above implementation, the multiple SSBs transmitted on the first downlink carrier can correspond to the ROs of the multiple uplink carriers or multiple BWPs, which can improve the flexibility of RO allocation, reduce the access latency, and thus improve the communication performance.

[0016] In some implementations of the first aspect, the time domain location of the RO corresponding to the first SSB is the same as the time domain location of the RO corresponding to the second SSB.

[0017] Based on the above implementation, the resource period of the RO corresponding to at least one SSB can be shortened, which can further reduce the latency of random access.

[0018] In some implementations of the first aspect, the first RO corresponding to the first SSB is on a first uplink carrier, and the second RO corresponding to the first SSB is on a second uplink carrier, wherein the RO corresponding to the first SSB includes the first RO and the second RO, and the at least two uplink carriers include the first uplink carrier and the second uplink carrier; or the first RO corresponding to the first SSB is on a first uplink BWP, and the second RO corresponding to the first SSB is on a second uplink BWP, wherein the RO corresponding to the first SSB includes the first RO and the second RO, and the at least two uplink BWPs include the first uplink BWP and the second uplink BWP. In this implementation, the RO corresponding to one SSB is on two (or multiple) uplink carriers or two (or multiple) uplink BWPs.

[0019] Based on the above implementation, the first SSB can correspond to the ROs of multiple uplink carriers or multiple uplink BWPs, which can improve the flexibility of RO allocation, reduce the access latency, and reduce the probability of random access conflict of the communication device, and thus improve the communication performance.

[0020] In some implementations of the first aspect, the time domain location of the first RO is the same as the time domain location of the second RO.

[0021] Based on the above implementations, the resource period of the RO corresponding to the first SSB can be shortened, and the latency of random access can be further reduced.

[0022] In some implementations of the first aspect, the method further includes: receiving fourth configuration information, the fourth configuration information being used to indicate a carrier power offset corresponding to at least one of the at least two uplink carriers, the carrier power offset being used to determine the transmission power of the RACH on the at least one uplink carrier; or receiving fifth configuration information, the fifth configuration information being used to indicate a BWP power offset corresponding to at least one of the at least two uplink BWPs, the BWP power offset being used to determine the transmission power of the RACH on the at least one uplink BWP.

[0023] Based on the above implementations, the first communication device can determine the transmission power of the RACH on the first RO according to the carrier power offset indicated by the fourth configuration information or the BWP power offset indicated by the fifth configuration information, and according to the path loss determined according to the first SSB; and transmit the RACH preamble sequence on the first RO corresponding to the first SSB at the transmission power; the second communication device can avoid not receiving the RACH transmitted by the first communication device; in addition, the transmission power of the RACH can be determined according to the communication requirements of different carriers or different BWPs, flexible RACH transmission can be achieved, and communication performance can be improved.

[0024] In some implementations of the first aspect, the carrier power offsets corresponding to the first uplink carrier and the second uplink carrier of the at least two uplink carriers are different, or the BWP power offsets corresponding to the first uplink BWP and the second uplink BWP of the at least two uplink BWPs are different.

[0025] Based on the above implementations, the first communication device can determine the transmission power of the RACH according to the communication requirements of different carriers or different BWPs, flexible RACH transmission can be achieved, and communication performance can be improved.

[0026] In a second aspect, a method for random access is provided. The method can be applied to a second communication device, such as being performed by the second communication device. The second communication device can be a network device or a module (e.g., a circuit, a chip, a chip system, or a processor) in the network device, which can also be a logical node, a logical module, or software that can implement all or part of the function of the network device. Alternatively, the second communication device can be a terminal device or a module (e.g., a circuit, a chip, a chip system, or a processor) in the terminal device, which can also be a logical node, a logical module, or software that can implement all or part of the function of the terminal device.

[0027] The method includes: transmitting a first SSB on a first downlink carrier, the first downlink carrier being used to carry at least one SSB, the at least one SSB including the first SSB, the at least one SSB corresponding to an RO on at least two uplink carriers or on at least two uplink bandwidth parts (BWPs); and receiving a RACH preamble sequence on a first RO corresponding to the first SSB.

[0028] The method provided in the second aspect is a method corresponding to the first aspect, and the beneficial effects can be referred to the first aspect.

[0029] With reference to the second aspect, in some implementations of the second aspect, the method further includes: transmitting first configuration information, the first configuration information being used to indicate that the first downlink carrier is associated with the at least two uplink carriers or the at least two uplink BWPs.

[0030] With reference to the second aspect, in some implementations of the second aspect, the method further includes: transmitting second configuration information or third configuration information, the second configuration information being used to indicate the RO corresponding to the first SSB, the first SSB corresponding to the first RO, and the third configuration information being used to indicate the RO corresponding to the at least one SSB.

[0031] With reference to the second aspect, in some implementations of the second aspect, the at least one SSB includes the first SSB and a second SSB, the at least two uplink carriers include a first uplink carrier and a second uplink carrier, the first SSB corresponding to the first uplink carrier, and the second SSB corresponding to the second uplink carrier; or the at least two uplink BWPs include a first uplink BWP and a second uplink BWP, the first SSB corresponding to the first uplink BWP, and the second SSB corresponding to the second uplink BWP.

[0032] With reference to the second aspect, in some implementations of the second aspect, the time domain position of the RO corresponding to the first SSB is the same as the time domain position of the RO corresponding to the second SSB.

[0033] With reference to the second aspect, in some implementations of the second aspect, a first RO corresponding to the first SSB is on a first uplink carrier, and a second RO corresponding to the first SSB is on a second uplink carrier, wherein the RO corresponding to the first SSB includes the first RO and the second RO, and the at least two uplink carriers include the first uplink carrier and the second uplink carrier; or a first RO corresponding to the first SSB is on a first uplink BWP, and a second RO corresponding to the first SSB is on a second uplink BWP, wherein the RO corresponding to the first SSB includes the first RO and the second RO, and the at least two uplink BWPs include the first uplink BWP and the second uplink BWP.

[0034] With reference to the second aspect, in some implementations of the second aspect, a time domain location of the first RO is the same as a time domain location of the second RO.

[0035] With reference to the second aspect, in some implementations of the second aspect, the method further includes: sending fourth configuration information, the fourth configuration information being used to indicate a carrier power offset corresponding to at least one uplink carrier of the at least two uplink carriers, the carrier power offset being used to determine a transmission power of a RACH on the at least one uplink carrier; or sending fifth configuration information, the fifth configuration information being used to indicate a BWP power offset corresponding to at least one uplink BWP of the at least two uplink BWPs, the BWP power offset being used to determine a transmission power of a RACH on the at least one uplink BWP.

[0036] With reference to the second aspect, in some implementations of the second aspect, carrier power offsets corresponding to a first uplink carrier and a second uplink carrier of the at least two uplink carriers are different, or BWP power offsets corresponding to a first uplink BWP and a second uplink BWP of the at least two uplink BWPs are different.

[0037] A third aspect provides a communication apparatus, which can be the first communication apparatus of the first aspect. The communication apparatus includes a transceiver configured to receive a first synchronization signal block (SSB) on a first downlink carrier, the first downlink carrier being used to carry at least one SSB, the at least one SSB including the first SSB, and a random access channel opportunity (RO) corresponding to the at least one SSB being on at least two uplink carriers or at least two uplink BWPs; and the transceiver is further configured to transmit a random access channel (RACH) preamble sequence on a first RO corresponding to the first SSB.

[0038] With reference to the third aspect, in some implementations of the third aspect, the transceiver is further configured to receive first configuration information, the first configuration information being used to indicate that the first downlink carrier is associated with the at least two uplink carriers or the at least two uplink BWPs.

[0039] With reference to the third aspect, in some implementations of the third aspect, the transceiver is further configured to receive second configuration information or third configuration information, the second configuration information being used to indicate the RO corresponding to the first SSB, the RO corresponding to the first SSB including the first RO, the third configuration information being used to indicate the RO corresponding to the at least one SSB.

[0040] With reference to the third aspect, in some implementations of the third aspect, the communication apparatus further includes a processing module configured to determine the RO corresponding to the first SSB.

[0041] With reference to the third aspect, in some implementations of the third aspect, the processing module is specifically configured to: determine the RO corresponding to the first SSB according to the second configuration information; or determine the RO corresponding to the first SSB according to the third configuration information and a predefined rule.

[0042] With reference to the third aspect, in some implementations of the third aspect, the RO corresponding to the first SSB is on a first uplink carrier, and the RO corresponding to a second SSB is on a second uplink carrier, wherein the at least one SSB includes the first SSB and the second SSB, and the at least two uplink carriers include the first uplink carrier and the second uplink carrier; or the RO corresponding to the first SSB is on a first uplink BWP, and the RO corresponding to a second SSB is on a second uplink BWP, wherein the at least one SSB includes the first SSB and the second SSB, and the at least two uplink BWPs include the first uplink BWP and the second uplink BWP.

[0043] With reference to the third aspect, in some implementations of the third aspect, a time domain location of the RO corresponding to the first SSB is the same as a time domain location of the RO corresponding to the second SSB.

[0044] In some implementations of the third aspect, in combination with the third aspect, a first RO corresponding to the first SSB is on a first uplink carrier, and a second RO corresponding to the first SSB is on a second uplink carrier, wherein the ROs corresponding to the first SSB include the first RO and the second RO, and the at least two uplink carriers include the first uplink carrier and the second uplink carrier; or a first RO corresponding to the first SSB is on a first uplink BWP, and a second RO corresponding to the first SSB is on a second uplink BWP, wherein the ROs corresponding to the first SSB include the first RO and the second RO, and the at least two uplink BWPs include the first uplink BWP and the second uplink BWP.

[0045] In some implementations of the third aspect, in combination with the third aspect, a time domain location of the first RO is the same as a time domain location of the second RO.

[0046] In some implementations of the third aspect, in combination with the third aspect, the transceiver is further configured to receive fourth configuration information, the fourth configuration information being used to indicate a carrier power offset corresponding to at least one uplink carrier of the at least two uplink carriers, the carrier power offset being used to determine a transmission power of a RACH on the at least one uplink carrier; or receive fifth configuration information, the fifth configuration information being used to indicate a BWP power offset corresponding to at least one uplink BWP of the at least two uplink BWPs, the BWP power offset being used to determine a transmission power of a RACH on the at least one uplink BWP.

[0047] In some implementations of the third aspect, in combination with the third aspect, carrier power offsets corresponding to a first uplink carrier and a second uplink carrier of the at least two uplink carriers are different, or BWP power offsets corresponding to a first uplink BWP and a second uplink BWP of the at least two uplink BWPs are different.

[0048] In a fourth aspect, a communication apparatus is provided, which can be the second communication apparatus of the second aspect. The communication apparatus includes a transceiver configured to transmit a first SSB on a first downlink carrier, the first downlink carrier being used to carry at least one SSB, the at least one SSB including the first SSB, ROs corresponding to the at least one SSB being on at least two uplink carriers or at least two uplink BWPs; and the transceiver is further configured to receive a RACH preamble sequence on a first RO corresponding to the first SSB.

[0049] In some implementations of the fourth aspect, in conjunction with the fourth aspect, the transceiver is further configured to transmit first configuration information, the first configuration information being used to indicate that the first downlink carrier is associated with the at least two uplink carriers or the at least two uplink BWPs.

[0050] In some implementations of the fourth aspect, in conjunction with the fourth aspect, the transceiver is further configured to transmit second configuration information or third configuration information, the second configuration information being used to indicate the RO corresponding to the first SSB, the first SSB corresponding to the first RO, and the third configuration information being used to indicate the RO corresponding to the at least one SSB.

[0051] In some implementations of the fourth aspect, in conjunction with the fourth aspect, the RO corresponding to the first SSB is on a first uplink carrier, and the RO corresponding to a second SSB is on a second uplink carrier, wherein the at least one SSB includes the first SSB and the second SSB, and the at least two uplink carriers include the first uplink carrier and the second uplink carrier; or the RO corresponding to the first SSB is on a first uplink BWP, and the RO corresponding to a second SSB is on a second uplink BWP, wherein the at least one SSB includes the first SSB and the second SSB, and the at least two uplink BWPs include the first uplink BWP and the second uplink BWP.

[0052] In some implementations of the fourth aspect, in conjunction with the fourth aspect, a time domain location of the RO corresponding to the first SSB is the same as a time domain location of the RO corresponding to the second SSB.

[0053] In some implementations of the fourth aspect, in conjunction with the fourth aspect, a first RO corresponding to the first SSB is on a first uplink carrier, and a second RO corresponding to the first SSB is on a second uplink carrier, wherein the RO corresponding to the first SSB includes the first RO and the second RO, and the at least two uplink carriers include the first uplink carrier and the second uplink carrier; or a first RO corresponding to the first SSB is on a first uplink BWP, and a second RO corresponding to the first SSB is on a second uplink BWP, wherein the RO corresponding to the first SSB includes the first RO and the second RO, and the at least two uplink BWPs include the first uplink BWP and the second uplink BWP.

[0054] In some implementations of the fourth aspect, in conjunction with the fourth aspect, a time domain location of the first RO is the same as a time domain location of the second RO.

[0055] In some implementations of the fourth aspect, in combination with the fourth aspect, the transceiver is further configured to transmit fourth configuration information, the fourth configuration information being used to indicate a carrier power offset corresponding to at least one of the at least two uplink carriers, the carrier power offset being used to determine a transmission power of the RACH on the at least one uplink carrier; or transmit fifth configuration information, the fifth configuration information being used to indicate a BWP power offset corresponding to at least one of the at least two uplink BWPs, the BWP power offset being used to determine a transmission power of the RACH on the at least one uplink BWP.

[0056] In some implementations of the fourth aspect, in combination with the fourth aspect, carrier power offsets corresponding to the first uplink carrier and the second uplink carrier of the at least two uplink carriers are different, or BWP power offsets corresponding to the first uplink BWP and the second uplink BWP of the at least two uplink BWPs are different.

[0057] In the fifth aspect, a communication apparatus is provided, which comprises a processor configured to implement a method in the first aspect or any possible implementation of the first aspect. Optionally, the communication apparatus further comprises an interface circuit configured to receive a signal from another communication apparatus and transmit the signal to the processor or transmit a signal from the processor to another communication apparatus.

[0058] In the sixth aspect, a communication apparatus is provided, which comprises a processor configured to implement a method in the second aspect or any possible implementation of the second aspect. Optionally, the communication apparatus further comprises an interface circuit configured to receive a signal from another communication apparatus and transmit the signal to the processor or transmit a signal from the processor to another communication apparatus.

[0059] In the seventh aspect, a communication system is provided, which comprises a first communication apparatus configured to implement the method in the first aspect, and a second communication apparatus configured to implement the method in the second aspect.

[0060] In the eighth aspect, a computer readable storage medium is provided, which stores a computer program; when the computer program is run by a processor, the method in the first aspect and the second aspect and any possible implementation of the first aspect and the second aspect is executed.

[0061] In the ninth aspect, a computer program product is provided, which comprises a computer program, when the computer program is executed, the method in the first aspect and the second aspect and any possible implementation of the first aspect and the second aspect is executed.

[0062] The solutions provided by the third aspect to the ninth aspect are used to implement or assist in implementing the method provided by the first aspect or the second aspect, and thus can achieve the same or corresponding beneficial effects as the first aspect or the second aspect. Therefore, no further description is given here. BRIEF DESCRIPTION OF DRAWINGS

[0063] FIG. 1a is a schematic diagram of an architecture of a communication system to which embodiments of the present application are applied.

[0064] FIG. 1b is an example diagram of an open radio access network (O-RAN or ORAN) system.

[0065] FIGS. 1c and 1d are schematic diagrams of communication systems suitable for embodiments of the present application.

[0066] FIG. 1e is a schematic diagram of a satellite communication system suitable for embodiments of the present application.

[0067] FIG. 1f is a schematic diagram of an Internet of Things wireless projection suitable for embodiments of the present application.

[0068] FIG. 1g is a schematic diagram of an integrated access and backhaul (IAB) system suitable for embodiments of the present application.

[0069] FIG. 2 is a schematic diagram of a basic framework of a frame structure in 5G NR.

[0070] FIG. 3 is a schematic diagram of the relationship between a frame, a subframe, a slot, and a symbol when the sub-carrier spacing (SCS) is 30 kHz and 120 kHz, respectively.

[0071] FIG. 4 is a schematic diagram of different slot types.

[0072] FIG. 5 is a schematic diagram of non-slot based scheduling.

[0073] FIG. 6 is a schematic diagram of resource division of a resource element (RE), a resource block (RB), and a resource grid (RG).

[0074] FIG. 7 is a schematic diagram of the relationship between a resource element group (REG) and a control channel element (CCE).

[0075] FIG. 8 is a schematic diagram of a contention-based random access (RA) procedure.

[0076] FIG. 9 is a flowchart of a terminal device sending a preamble sequence.

[0077] FIG. 10 is a schematic diagram of a non-contention-based RA procedure.

[0078] FIG. 11 is a schematic diagram of a mapping relationship between an SSB and an RO.

[0079] FIG. 12 is a schematic flowchart of a random access method according to an embodiment of the present application.

[0080] FIG. 13 is a schematic diagram of a mapping relationship between an SSB and an RO according to an embodiment of the present application.

[0081] FIG. 14 is a schematic diagram of a mapping relationship between an SSB and an RO according to an embodiment of the present application.

[0082] FIG. 15 is a schematic diagram of a mapping relationship between an SSB and an RO according to an embodiment of the present application.

[0083] FIG. 16 is a schematic diagram of a mapping relationship between an SSB and an RO according to an embodiment of the present application.

[0084] FIG. 17 is a schematic diagram of a mapping relationship between an SSB and an RO according to an embodiment of the present application.

[0085] FIG. 18 is a schematic flowchart of a random access method according to an embodiment of the present application.

[0086] FIG. 19 is a schematic diagram of a mapping relationship between an SSB and an RO according to an embodiment of the present application.

[0087] FIG. 20 is a schematic diagram of a mapping relationship between an SSB and an RO according to an embodiment of the present application.

[0088] FIG. 21 is a schematic diagram of a mapping relationship between an SSB and an RO according to an embodiment of the present application.

[0089] FIG. 22 is a schematic diagram of a mapping relationship between an SSB and an RO according to an embodiment of the present application.

[0090] FIG. 23 is a schematic diagram of a mapping relationship between an SSB and an RO according to an embodiment of the present application.

[0091] FIG. 24 is a schematic block diagram of a communication apparatus according to an embodiment of the present application.

[0092] FIG. 25 is a schematic block diagram of a communication apparatus according to an embodiment of the present application.

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

[0094] The technical solutions provided by the present application will be described below with reference to the accompanying drawings.

[0095] The embodiments of the present application can be applied to various communication systems, such as a wireless local area network (WLAN) system, a narrow band-internet of things (NB-IoT) system, a global system for mobile communications (GSM), an enhanced data rate for GSM evolution (EDGE) system, a wideband code division multiple access (WCDMA) system, a code division multiple access 2000 (CDMA2000) system, a time division-synchronization code division multiple access (TD-SCDMA) system, a long term evolution (LTE) system, a new radio (NR) wireless communication system, and a future evolved wireless communication system, a universal mobile telecommunication system (UMTS), a worldwide interoperability for microwave access (WiMAX) communication system, a satellite communication system, a 5G communication system, a 6th-generation (6G) communication system, or a new communication system to be developed in the future. For example, the embodiments of the present application can be applied to an orthogonal frequency division multiplexing (OFDM) system in LTE, an OFDM system in NR, and a future OFDM system and an OFDM-like system, etc.

[0096] The terminal device involved in the embodiments of the present application can be a device with wireless transceiving function, and can specifically refer to a subscriber unit, a user equipment (UE), an access terminal, a cellular phone, a user station, a mobile station (MS), a customer-premises equipment (CPE), a remote station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent or a user apparatus. The terminal device can also be a satellite phone, a cellular phone, a smart phone, a wireless data card, a personal digital assistant (PDA) computer, a tablet computer, a wireless modulator demodulator (modem), a laptop computer, a machine type communication (MTC) device and a wireless terminal in self-driving, etc. The terminal device can also be a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a vehicle-mounted device, a wearable device, a computing device or other processing device connected to a wireless modem, a communication device carried on an airship, a drone, a robot, a smart point of sale (POS) machine, a terminal in device-to-device (D2D) communication, a terminal in vehicle to everything (V2X) communication, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in telemedicine or telehealth services, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a terminal in communication and sensing integration, a wireless terminal in smart home or a terminal device in future communication network, etc.The user equipment includes a vehicle user equipment. With the rise of the internet of things (IoT) technology, more and more devices that do not have a communication function, such as but not limited to household appliances, vehicles, tool devices, service devices, and service facilities, begin to obtain a wireless communication function by configuring a wireless communication unit, so as to access a wireless communication network and accept remote control. Such devices have a wireless communication function because of the configured wireless communication unit, and thus also belong to the category of wireless communication devices. This application is not limited.

[0097] In the embodiments of the present application, the device for implementing the function of the terminal equipment can be a terminal equipment, or a device capable of supporting the terminal equipment to implement the function, such as a chip system. The device can be installed in the terminal equipment or used in matching with the terminal equipment. In the embodiments of the present application, the chip system can be composed of a chip, or can include a chip and other discrete devices.

[0098] The network device involved in the embodiments of the present application is a device in a wireless network, for example, a radio access network (RAN) node that accesses a terminal device to a wireless network. The network device can be a node in a radio access network, which can be referred to as a base station, and can also be referred to as a RAN node (or device). The network device can be a base transceiver station (BTS) in a GSM or CDMA network, a Node B (NB) in a WCDMA network, an evolved Node B (eNB or eNodeB) in an LTE network, or a next generation Node B (gNB) in a 5G network; the network device can be a base station in a future evolved public land mobile network (PLMN) or an access device in the 3rd generation partnership project (3GPP); the network device can also be a wireless controller in a cloud radio access network (CRAN) scenario. Optionally, the network device in the embodiments of the present application can include various forms of base stations, for example: a relay station, an access point, a device that implements the function of a base station in a communication system evolved after 5G, a mobile switching center, a home base station (home evolved NodeB or home Node B, HNB), a baseband unit (BBU), a device that undertakes the function of a base station in device to device (D2D) communication, an access point (AP) in a wireless fidelity (WIFI) system, a wireless relay node, a wireless backhaul node, a transmission point (TP), or a transmission and reception point (TRP), and the like, a device that undertakes the function of a base station in vehicle-to-everything (V2X) and machine-to-machine (M2M) communication, and the like, and can also include a centralized unit (CU) and a distributed unit (DU) in a cloud radio access network (C-RAN) system, a network device in a non-terrestrial network (NTN) communication system, that is, can be deployed on a high-altitude platform or a satellite.The gNB or transmission point in the NR, one or a group (including multiple) of antenna panels of the base station in the NR, or the network node constituting the gNB or transmission point, or the network device can also be a vehicle-mounted device, a wearable device, and a network device in a 6G network, or a network device in a future evolved PLMN network, etc., or a network device deployed on a satellite, and the embodiments of the present application do not limit this. In addition, according to the size of the service coverage area provided, the base station can be divided into a macro base station for providing a macro cell, a micro base station for providing a pico cell, and a femto base station for providing a femto cell. With the continuous evolution of wireless communication technology, future base stations can also have other names.

[0099] In a possible scenario, multiple RAN nodes cooperate to assist a terminal device to implement wireless access, and different RAN nodes respectively implement part of the functions of a base station. For example, the RAN node can be a CU, a DU, a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), etc. The CU and the DU can be separately arranged, or can be included in the same network element, such as a BBU. The RU can be included in a radio frequency device or a radio unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0100] In different systems, the CU (or CU-CP and CU-UP), DU or RU can also have different names, but those skilled in the art can understand their meanings. For example, in an O-RAN or ORAN system, the CU can also be referred to as an open CU (O-CU), the DU can also be referred to as an open DU (O-DU), the CU-CP can also be referred to as an open DU (O-CU-CP), the CU-UP can also be referred to as an open CU-UP (O-CU-UP), and the RU can also be referred to as an open RU (O-RU). For the convenience of description, the CU, CU-CP, CU-UP, DU and RU are taken as examples for description in the present application. Any one of the CU (or CU-CP, CU-UP), DU and RU in the present application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0101] The communication between the access network device and the terminal device follows a certain protocol layer structure. The protocol layer can include a control plane protocol layer and a user plane protocol layer. The control plane protocol layer can include at least one of a radio resource control (RRC) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, a media access control (MAC) layer, or a physical (PHY) layer, etc. The user plane protocol layer can include at least one of a service data adaptation protocol (SDAP) layer, a PDCP layer, an RLC layer, a MAC layer, or a physical layer, etc.

[0102] For the correspondence between the network element in the ORAN system and the protocol layer function that can be implemented by the network element, refer to Table 1 below.

[0103] Table 1

[0104] The high physical layer function includes one or more of the following: forward error correction (FEC) encoding / decoding, scrambling / descrambling, or modulation / demodulation. The low physical layer function includes one or more of the following: fast Fourier transform (FFT) transform / inverse fast Fourier transform (IFFT) transform, digital beamforming, or extraction and filtering of a physical random access channel (PRACH), etc. Similar to the transmission reception point (TRP) or RRH in 3GPP, but including low physical layer functions such as FFT / IFFT or PRACH extraction.

[0105] Optionally, the RAN node can also be a macro base station, a micro base station or an indoor station, a relay node or a donor node, or a wireless controller in a CRAN scenario. The RAN node can also be a server, a wearable device, a vehicle or a vehicle-mounted device, etc. For example, the access network device in the V2X technology can be a road side unit (RSU).

[0106] The location of the network device and / or the terminal device can be fixed or mobile. The network device and / or the terminal device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on water; can also be deployed on an airplane, a balloon and a man-made satellite. Embodiments of the present application do not limit the application scenarios of the network device and / or the terminal device.

[0107] In embodiments of the present application, the apparatus for implementing the functions of the network device can be a network device; or can be an apparatus capable of supporting the network device to implement the functions, such as a chip system. The apparatus can be installed in the network device or used in combination with the network device.

[0108] In order to facilitate the understanding of the method provided by the embodiments of the present application, the system architecture of the method provided by the embodiments of the present application will be described below. It can be understood that the system architecture described in the embodiments of the present application is to more clearly illustrate the scheme of the embodiments of the present application, and does not constitute a limitation on the scheme provided by the embodiments of the present application.

[0109] FIG. 1a is a schematic diagram of the architecture of a communication system 1000 to which embodiments of the present application are applied. As shown in FIG. 1a, the communication system includes a RAN 100 and a core network 200. Optionally, the communication system 1000 can also include the Internet 300. The RAN 100 includes at least one RAN node (such as 110a and 110b in FIG. 1a, collectively referred to as 110), and can also include at least one terminal device (such as 120a-120j in FIG. 1a, collectively referred to as 120). The RAN 100 can also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in FIG. 1a). The terminal devices 120 are connected to the RAN nodes 110 in a wireless manner, and the RAN nodes 110 are connected to the core network 200 in a wireless or wired manner. 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 terminal devices and the terminal devices, and the RAN nodes and the RAN nodes can be connected to each other in a wired or wireless manner.

[0110] FIG. 1b is an example diagram of an O-RAN system, which can include other components in addition to those shown in the figure. As shown, an access network device (such as an eNB or a gNB or a next-generation access network device) communicates with a core network (CN) through a backhaul and communicates with a terminal device through an air interface.

[0111] Specifically, a BBU in an access network device communicates with a core network through a backhaul link, and a RU in the access network device communicates with at least one terminal device through an air interface. The BBU communicates with at least one RU through a fronthaul link, and the BBU and the RU can be co-located or not co-located. The BBU includes at least one control unit and at least one DU, which can communicate through at least one midhaul link.

[0112] As an example, the RAN node can be a satellite base station or a satellite, which is explained below in connection with Figures 1c-1e. Figures 1c and 1d are schematic diagrams of communication systems suitable for embodiments of the present application.

[0113] As shown in Figures 1c and 1d, a satellite base station provides communication services for terminal devices. For example, the satellite base station transmits downlink data to a terminal device, where the data is encoded using channel coding, and the channel-coded data is transmitted to the terminal device after being modulated using constellation modulation. As another example, a terminal device transmits uplink data to a satellite base station, where the uplink data can also be encoded using channel coding, and the encoded data is transmitted to the satellite base station after being modulated using constellation modulation. In addition, as shown in Figure 1d, a satellite base station can also communicate with a ground base station, which can act as a base station or as a terminal device. In the present application, a satellite can refer to a drone, a hot air balloon, a low earth orbit satellite, a medium earth orbit satellite, a high earth orbit satellite, etc. A satellite can also refer to a non-ground base station or a non-ground device, etc.

[0114] It should be understood that the present application can be applied to a scenario in which network devices communicate with each other, and the scenario shown in Figure 1d can also be considered as an example of network devices communicating with each other, where the satellite and the base station can both be considered as a network device.

[0115] As an implementation manner, the present application can be applied to a satellite inter-satellite link communication system. As shown in Figure 1d, the communication between satellite #1 and satellite #2.

[0116] Figure 1e is a schematic diagram of a satellite communication system applicable to an embodiment of this application. The inter-satellite link communication system can be divided into two main parts: an acquisition pointing and tracking (APT) subsystem (including an APT module and an APT transmitter / receiver) and a communication subsystem (including a communication module and transceiver antennas). The communication subsystem is primarily responsible for the transmission of inter-satellite information and is the main body of the inter-satellite communication system; the APT subsystem is primarily responsible for acquisition, alignment, and tracking between satellites. Specifically, determining the direction of arrival of the incident signal is acquisition, and adjusting the transmitted wave to aim at the receiving direction is alignment. Throughout the communication process, the APT continuously adjusts alignment and acquisition, which is tracking. To minimize attenuation and interference in the channel while maintaining high security and transmission rate, the APT must be adjusted in real time to continuously adapt to changes.

[0117] It should be understood that current APT subsystems are all optical systems, which have the disadvantage of being difficult to align and requiring mechanical adjustment of the pointing. Most existing communication subsystems are optical communication systems, with some microwave band systems, and most use a single high-gain antenna. Current APT and communication subsystems are independent systems. The disadvantages are that optical communication is susceptible to vibration and other factors, resulting in unstable data rates; millimeter-wave frequencies are low, communication capacity is low, and the antenna requires mechanical adjustment of its pointing.

[0118] As another implementation, this application can be applied to scenarios where terminal devices communicate with each other, such as Internet of Things (IoT) communication systems.

[0119] Figure 1f is a schematic diagram of a wireless screen projection method applicable to an embodiment of this application. A terminal device (e.g., a smartphone) establishes a network connection with a television. The smartphone transmits the content to be projected onto the television to the television. After receiving the content transmitted by the smartphone, the television displays the content on its screen.

[0120] It should be understood that the screen projection scenario shown in Figure 1f can be regarded as an example of communication between terminal devices, where both smartphones and televisions can be regarded as terminal devices.

[0121] As another implementation method, this application can be applied to the IAB system.

[0122] FIG. 1g is a schematic diagram of an IAB system applicable to the embodiments of the present application. As shown in FIG. 1g, the IAB system can include an IAB donor, an IAB node and a terminal device. The link between the IAB donor and the IAB node is a backhaul link, and the link between the terminal device and the IAB node is an access link. The execution subject of the embodiments of the present application can be the communication parties in the backhaul link, or the communication parties in the access link.

[0123] It should be understood that the above system application scenarios are only examples, and the present application can also be applicable to other scenarios, which are not listed one by one here.

[0124] It should be noted that in the embodiments of the present application, the physical downlink shared channel (PDSCH) is only an example of a downlink data channel, the physical downlink control channel (PDCCH) is only an example of a downlink control channel, the physical uplink shared channel (PUSCH) is only an example of an uplink data channel, and the physical uplink control channel (PUCCH) is only an example of an uplink control channel. 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.

[0125] Some terminology concepts related to the embodiments of the present application are explained below.

[0126] 1. Physical transmission link control channel (PTxCCH): a physical layer control channel. Generally, the standard protocol is described from the perspective of the terminal device, and the PTxCCH can be understood as the physical layer control channel transmitted by the terminal device, which is similar to the PUCCH in LTE and 5G. The PTxCCH can be a new physical layer control channel introduced in 6G. Of course, future networks such as 6G can still use PUCCH to represent the physical uplink control channel or physical transmission link control channel of the terminal device.

[0127] 2、Physical transmission link shared channel (PTxSCH): a kind of physical layer data channel, generally, the standard protocol is described from the perspective of terminal equipment, PTxSCH can be understood as the physical layer data channel sent by terminal equipment, the function is similar to PUSCH in LTE and 5G, PTxSCH can be a new physical layer data channel introduced in 6G. Of course, future networks such as 6G may still use PUSCH to represent the physical uplink data channel or physical transmission link data channel of terminal equipment.

[0128] 3、Physical reception link control channel (PRxCCH): a kind of physical layer control channel, generally, the standard protocol is described from the perspective of terminal equipment, PRxCCH can be understood as the physical layer control channel received by terminal equipment, the function is similar to PDCCH in LTE and 5G, PRxCCH can be a new physical layer control channel introduced in 6G. Of course, future networks such as 6G may still use PDCCH to represent the physical downlink control channel or physical reception link control channel of terminal equipment.

[0129] 4、Physical reception link shared channel (PRxSCH): a kind of physical layer data channel, generally, the standard protocol is described from the perspective of terminal equipment, PRxSCH can be understood as the physical layer data channel received by terminal equipment, the function is similar to PDSCH in LTE and 5G, PDxSCH can be a new physical layer data channel introduced in 6G. Of course, future networks such as 6G may still use PDSCH to represent the physical downlink data channel or physical reception link data channel of terminal equipment. Alternatively, for downlink transmission, it can be described from the perspective of terminal equipment as receiving; for uplink transmission, it can be described from the perspective of terminal equipment as sending. For terminal equipment and terminal equipment communication, downlink or uplink can also be described as sidelink.

[0130] 5、Multi-rat spectrum sharing (MRSS): refers to multi-rat spectrum sharing, multiple radio access technologies work in the same frequency band and share the same spectrum; such as LTE and NR spectrum sharing, NR and 6G spectrum sharing, 5G and 6G spectrum sharing, etc.

[0131] In order to facilitate the understanding of the embodiments of the present application, the technical solutions related to the embodiments of the present application are briefly introduced as follows.

[0132] The air interface time-frequency resource of the 5G system is similar to that of the LTE, including time domain and frequency domain. When formulating the 5G protocol, 3GPP redesigned the air interface time-frequency resource on the basis of the LTE, so that the network capability of the 5G can reach the design target of the system and better meet the quality of service (QoS) requirements of various services in the system while taking into account the smooth evolution of the LTE to the 5G.

[0133] I. Concepts related to time domain resource

[0134] 1. Numerology

[0135] The 5G NR introduces the concept of numerology, which includes SCS, as well as parameters such as symbol length and cycle prefix (CP) length corresponding to the SCS. Since there is a certain mapping relationship between the SCS and the symbol length and the CP length, the SCS is usually used instead of the numerology. The CP includes normal cycle prefix (normal CP) and extended cycle prefix (extended CP); the frequency range (FR) supported by different SCS is different. Table 2 shows the numerologies supported in the 3GPP protocol.

[0136] Table 2

[0137] In Table 2, μ represents the subcarrier spacing index, or the parameter in the numerology.

[0138] 2. Frame structure

[0139] In the NR system, the unit in the time domain includes symbol, time slot, subframe, half frame, frame, etc., wherein the time of one frame is 10 ms, one frame can be divided into 10 subframes numbered 0-9, and the subframes numbered 0-4 form one half frame, and the subframes numbered 5-9 form another half frame; the time of each subframe is 1 ms. Each subframe can include one or more time slots, and each time slot includes 14 symbols under normal cycle prefix, and one time slot includes 12 symbols under extended cycle prefix. Specifically, the number of time slots included in each subframe is related to the subcarrier spacing (SCS), and Table 3 shows the number of time slots included in each subframe under different SCS.

[0140] Table 3

[0141] Figure 2 is a schematic diagram of the basic framework of frame structure in 5G NR. Frame: fixed length of 10 ms, frame number range: 0-1023. Subframe: fixed length of 1 ms, subframe number range: 0-9. Slot: when normal CP is used, the length is 14 symbols; since the symbol length is not fixed, the slot length is also not fixed; when the SCS is 60 kHz, the extended CP can also be used, and the slot length is 12 symbols. Symbol: the length is not fixed, and is related to the SCS.

[0142] The time unit of 5G NR data scheduling is a slot, although the number of symbols in a slot is fixed, the length of a symbol is related to the SCS. Taking SCS of 30 kHz and 120 kHz as examples, Figure 3 is a schematic diagram of the relationship between frame, subframe, slot and symbol when the SCS is 30 kHz and 120 kHz, respectively.

[0143] 3. Symbol type and slot format

[0144] 3GPP TS 38.213 protocol defines three types of orthogonal frequency division multiplexing (OFDM) symbols, including downlink (DL), uplink (UL) and flexible (flexible) symbols. Downlink: represented by the letter D, used for downlink transmission; uplink: represented by the letter U, used for uplink transmission; flexible: represented by the letter F, which can be used for uplink transmission, also for downlink transmission, and can also be used as a guard period (GP) or reserved resource.

[0145] Each slot can be freely combined by these three types of symbols to form various slot formats. According to the slot format defined by the protocol, the slot type can be divided into the following four types:

[0146] Type 1: only includes “downlink” symbols, which is also commonly referred to as DL-only slot;

[0147] Type 2: only includes “uplink” symbols, which is also commonly referred to as UL-only slot;

[0148] Type 3: only includes “flexible” symbols, which is also commonly referred to as flexible-only slot;

[0149] Type 4: At least one "downlink" or "uplink" symbol in a slot, and there is also "flexible" symbol in the slot.

[0150] Figure 4 is a schematic diagram of different slot types; among which Type 4 can be further divided into several cases, including Type 4-1, Type 4-2, Type 4-3, Type 4-4, Type 4-5. It can be seen that the slot format design of 5G NR can achieve uplink and downlink data changes at the symbol level, while in LTE it can only achieve changes at the subframe level; therefore, the slot format design of 5G NR is more flexible, and at the same time makes the slot type more abundant to adapt to different types of services in different scenarios.

[0151] 4、Self-contained slot

[0152] Type 4-3, Type 4-4 and Type 4-5, also known as self-contained slot, correspond to two structures of self-contained slot respectively.

[0153] DL-dominant slot: such as Type 4-3, the slot is mainly used for transmission of downlink data, and a small amount of symbols are used for transmission of uplink control signals such as hybrid automatic repeat request (HARQ) feedback or sounding reference signal (SRS) of the downlink data through time division multiplexing, thereby shortening the HARQ feedback delay of the downlink data.

[0154] UL-dominant slot: such as Type 4-4, the slot is mainly used for transmission of uplink data, and a small amount of symbols are used for transmission of downlink control signals such as uplink scheduling indication in PDCCH through time division multiplexing, thereby shortening the uplink scheduling delay.

[0155] In the design of self-contained slot, both the base station and the terminal device need to switch between uplink and downlink transmission within a slot, and no signal is transmitted or received in the reserved protection time to ensure normal operation after switching.

[0156] 5、Mini-slot

[0157] In order to further reduce the air interface delay, 3GPP proposes the concept of mini-slot, whose time domain length is less than 14 symbols. Compared with the scheduling of slot, the division in time domain is more fine-grained, and the scheduling delay is shorter. The scheduling of mini-slot is usually also called non-slot based scheduling, and FIG. 5 is a schematic diagram of non-slot based scheduling.

[0158] II. Concepts related to frequency domain resources

[0159] 1. RE, RB and RG

[0160] RE is the smallest granularity physical layer resource in 5G NR, with 1 subcarrier in frequency domain and 1 OFDM symbol in time domain.

[0161] RB is the basic unit of channel resource allocation in frequency domain in 5G NR, and can contain 12 subcarriers in frequency domain. The subcarrier spacing in 5G NR is variable, so the actual bandwidth of RB is also variable.

[0162] RG is a set of time-frequency resources, and in 5G NR, it is defined as follows: for different numerologies on each carrier, a RG is a set of resources of all subcarriers in frequency domain and all symbols in time domain with a length of 1 subframe, and the starting point of frequency domain is in the granularity of RB. Since different numerologies correspond to different SCS, and one RB contains 12 subcarriers, for the same transmission bandwidth, the number of RBs contained in RG is different under different numerologies. RG is 1 subframe in time domain. FIG. 6 is a schematic diagram of resource division of RE, RB and RG.

[0163] 2. Common resource block (CRB), physical resource block (PRB) and resource block group (RBG)

[0164] CRB can be understood as a general term for all RBs in 5G NR, and CRB is numbered from 0. The center frequency point of the 0th subcarrier in CRB0 is also called point A.

[0165] PRB refers to the RB contained in the BWP of a certain terminal device in 5G NR, and is also numbered from 0, which is the basic unit of data channel scheduling.

[0166] RBG refers to a combination of a number of PRBs within a bandwidth part (BWP), numbered from 0, which is a basic unit of data channel scheduling; one RBG can contain {2, 4, 8, 16} PRBs, the specific number is related to the number of RBs in the BWP and the configuration options. Table 4 is an example of the number of PRBs contained in one RBG.

[0167] Table 4

[0168] 3、REG and CCE

[0169] REG is the basic unit of control channel resources; 1 REG can be 12 subcarriers in the frequency domain, so 1 REG can be the width of one PRB in the frequency domain and 1 OFDM symbol in the time domain. CCE is the basic unit of control channel resource scheduling, and 1 CCE can be composed of 6 REGs in the frequency domain. Figure 7 is a schematic diagram of the relationship between REG and CCE.

[0170] As the definition of time-frequency resources of 5G above, 6G can adopt the same definition, or can adopt different definitions. For example, 6G can define multiple subcarrier spacings, not limited to SCS in 5G; one slot can include one or more symbols, and one RB can include one or more subcarriers, etc.

[0171] Three, PRACH

[0172] PRACH is an important channel in LTE and 5G NR networks for terminal devices to initiate initial access and uplink synchronization with the base station. The design purpose of the PRACH channel is to enable terminal devices to initiate a random access procedure, thereby establishing a connection with the network or updating its connection status. In this application, PRACH can also be referred to as RACH.

[0173] The main functions of the PRACH channel include the following:

[0174] (1) Random access request: terminal devices initiate a random access procedure by sending a PRACH preamble, which is the first step for terminal devices to establish initial connection with the network;

[0175] (2) Uplink synchronization: by sending a preamble through PRACH, terminal devices can synchronize their uplink time with the base station to ensure correct reception of data;

[0176] (3) Obtain uplink authorization: the base station allocates uplink resources to the terminal device through the random access response (RAR) message, allowing the terminal device to send more complex messages, such as radio resource control (RRC) connection requests.

[0177] The key features of the PRACH channel include the following:

[0178] (1) Preamble sequence: The PRACH channel uses specific preamble sequences that are shared between the terminal device and the base station for detecting and identifying the terminal device's access request;

[0179] (2) Subframe structure: In LTE, the PRACH channel usually occupies one or more consecutive subframes. In 5G NR, the time domain structure of the PRACH channel is more flexible and can be configured on different slots and symbols;

[0180] (3) Power control: To ensure that the terminal device's preamble sequence can be correctly received by the base station, the transmission power of the PRACH channel needs to be adjusted according to the terminal device's path loss and the base station's instructions;

[0181] (4) Resource allocation: The resources (time, frequency, and preamble sequence) of the PRACH are configured by the base station through system information blocks (SIBs) or dynamic signaling, and the terminal device selects appropriate resources for access according to this information;

[0182] (5) Collision handling: When multiple terminal devices use the same preamble sequence at the same time, a collision may occur. The network handles this situation by sending a collision resolution instruction in the RAR message, requiring the terminal device to reselect a preamble sequence and reattempt access.

[0183] The PRACH channel plays a key role in mobile communication networks, ensuring that terminal devices can successfully establish a connection with the network to implement data transmission, voice calls, and other services.

[0184] When the terminal device performs random access, it needs to send a preamble on the PRACH; the base station measures the preamble to obtain the transmission delay between it and the terminal device, and sends a timing advance (TA) command to align the terminal device's transmission timing, thereby implementing the synchronization process between the base station and the terminal device.

[0185] Four, RA process

[0186] In the random access procedure, the terminal device needs to initiate access on a specific PRACH time-frequency resource. The signal transmitted by the terminal device when initiating access is a preamble. The preamble is used to inform the base station of a random access request, so that the base station can estimate the transmission delay between it and the terminal device.

[0187] RA includes two different mechanisms: contention-based RA and non-contention-based RA. In the contention-based RA procedure, the preamble is randomly selected by the terminal device within the scope of SIB1 broadcast, and these preambles are random; in this case, the preambles selected by different terminal devices may conflict, and the base station needs to resolve the access of different terminal devices through contention, and the result is random and cannot guarantee 100% success. In the non-contention-based RA procedure, the preamble is allocated to the terminal device by the base station, and these preambles are dedicated; in this case, the preambles selected by different terminal devices will not conflict, but when the dedicated preambles are insufficient, the base station will instruct the terminal device to initiate contention-based RA.

[0188] Figure 8 is a schematic diagram of the contention-based RA procedure. The specific steps are as follows.

[0189] Step 1: The terminal device sends a preamble on the PRACH, which can be understood as the terminal device sending Msg 1.

[0190] The purpose of the terminal device sending the preamble is to make the base station aware of the random access request of the terminal device, and to estimate the uplink time difference according to the reception of the preamble. The terminal device sends the preamble through Msg1, and Figure 9 is a flowchart of the terminal device sending the preamble sequence.

[0191] 1) The terminal device obtains the PRACH resource configuration from the SIB1 message;

[0192] The terminal device obtains the time-frequency domain position of the preamble it sends through the PRACH resource configuration;

[0193] 2) The terminal device randomly selects a preamble with equal probability;

[0194] Since different SSBs correspond to different preamble indexes, the terminal device will first select an SSB before selecting a preamble, and then determine the preamble according to the preamble index corresponding to the SSB. The terminal device can compare the reference signal receiving power (RSRP) of all received SSBs with a specified RSRP threshold, select an SSB greater than the RSRP threshold, and select the SSB with the best signal quality. If there is no SSB meeting the requirements, the terminal device will select an SSB.

[0195] 3) The terminal device sends a preamble.

[0196] Step 2: The base station sends a random access response (RAR), which can be understood as the base station sending Msg 2.

[0197] After the base station receives the preamble from the terminal device, it obtains the uplink TA of the terminal device according to the preamble. The base station sends an RAR on the PDSCH to indicate that it has received the preamble. The base station carries the value of the TA to the terminal device through Msg 2, which is used to adjust the transmission timing of the terminal device. In addition, the information carried by the RAR also includes the preamble index, the temporary cell-radio network temporary identifier (TC-RNTI) allocated to the terminal device, and the uplink grant (UL grant) resource allocated for Msg 3.

[0198] After the terminal device sends the preamble, it will start the RAR time window and continuously monitor the PDCCH within the RAR sliding window until it obtains the required RAR on the PDSCH. If the RAR contains a preamble index consistent with the index of the preamble sent by the terminal device, the terminal device considers that the RAR is successfully received and performs step 3. If the terminal device has not received the RAR within the RAR sliding window, or the received RAR fails verification, the terminal device considers that the last sent preamble has not been correctly received by the base station, and the RAR reception fails. At this time, if the number of random access attempts of the terminal device is less than the maximum number of attempts, the terminal device will perform a random access attempt again, otherwise the random access process fails.

[0199] Step 3: The terminal device sends Msg 3.

[0200] After step 2, the terminal device acquires uplink synchronization and can transmit Msg 3 on a predetermined PUSCH. Msg 3 carries a unique identifier of the terminal device, which is used for conflict resolution in step 4 to distinguish terminal devices that have occurred random access conflict. If the terminal device has been connected to a certain cell before, a cell-radio network temporary identifier (C-RNTI) can be used as the unique identifier of the terminal device; otherwise, an identifier from the core network is used as the unique identifier of the terminal device.

[0201] In step 4, the base station sends a contention resolution message / Msg 4 to the terminal device.

[0202] After the terminal device transmits Msg 3, a contention resolution timer is started (for example, the contention resolution timer can have a length of 64 ms), and then the terminal device listens to the PDCCH within the timer time window. The base station assists the terminal device in contention resolution by using the TC-RNTI on the PDCCH or using the contention resolution identity of the terminal device on the PDSCH:

[0203] Before the contention resolution timer expires, the terminal device always listens to the PDCCH channel, and if any of the following conditions exists, the terminal device considers that contention resolution is successful / the terminal device successfully accesses, and stops the contention resolution timer, otherwise the contention resolution timer is not stopped:

[0204] 1) The terminal device listens to the TC-RNTI of the terminal device on the PDCCH through Msg 4; at this time, the terminal device stops the contention resolution timer and discards the TC-RNTI;

[0205] 2) The terminal device listens to the TC-RNTI of the terminal device on the PDCCH through Msg 4, and the contention resolution identity contained in the media access control (MAC) protocol data unit (PDU) received by the terminal device from the PDSCH is the same as the contention resolution identity carried in Msg 3 sent by the terminal device, then the MAC PDU decoding is successful; at this time, the terminal device stops the contention resolution timer and sets the TC-RNTI to the C-RNTI.

[0206] If the contention resolution timer expires, the terminal device discards the TC-RNTI and considers the contention resolution as a failure. After the contention resolution failure, if the number of random access attempts of the terminal device is less than the maximum number of attempts, the terminal device performs a random access attempt again, otherwise, the random access procedure fails.

[0207] The main difference between the non-contention-based random access procedure and the contention-based random access procedure is that the preamble used in the non-contention-based random access procedure is allocated by the base station, which reduces the contention resolution process; other procedures are the same as the contention-based random access procedure. FIG. 10 is a schematic diagram of the non-contention-based RA procedure. The specific steps are as follows.

[0208] Step 1: The base station allocates a preamble to the terminal device, in other words, the base station sends preamble indication information to the terminal device.

[0209] In the handover scenario, the MobilityControlInfo information element transmitted by the source base station carries the preamble allocated to the terminal device for random access. When the base station allocates a preamble to the terminal device for random access, for example, the base station sends preamble indication information to the terminal device, the preamble indication information is used to indicate the preamble, and the base station can also indicate the SSB index corresponding to the preamble to the terminal device, including two indication methods of PDCCH and RRC signaling.

[0210] Step 2: The terminal device sends the preamble on the PRACH, which can be understood as the terminal device sending Msg 1.

[0211] Specifically, the terminal device obtains the PRACH resource configuration from the SIB1 message; the terminal device obtains the time-frequency domain position of the RA preamble sent by the terminal device through the PRACH resource configuration; and the terminal device sends the preamble.

[0212] Step 3: The base station sends the RAR, which can be understood as the base station sending Msg 2.

[0213] In the handover scenario, the information carried by the RAR includes TA information and UL grant. After the terminal device sends the preamble, the terminal device continuously monitors the PDCCH in the RAR sliding window until the required RAR is obtained. If the terminal device receives the RAR in the RAR sliding window, the terminal device considers that the RAR is received successfully, and performs step 4. If the terminal device has not received the RAR in the RAR sliding window, the terminal device considers that the RAR is not received successfully; at this time, if the number of random access attempts of the terminal device is less than the maximum number of attempts, the terminal device performs a random access attempt again, otherwise, the random access procedure fails.

[0214] Step 4, the terminal device sends Msg 3. Specifically, the terminal device sends Msg 3 to the base station at a determined sending time based on the TA information.

[0215] V. Relationship between RACH and SSB in initial access

[0216] In 5G NR, there is an association between SSB and RACH resource. Different SSBs can be transmitted using different beams. The terminal device compares the RSRP of all SSBs in the cell with a specified RSRP threshold, selects an SSB greater than the threshold, and selects the RACH resource corresponding to the SSB with the best signal quality. The network device can infer the best transmission beam according to the RACH resource used by the terminal device. The mapping between SSB and beam is transparent to the terminal device. RACH configuration information is broadcast in all beams in the cell for transmitting remaining system information (remaining SI) to ensure that the terminal device can receive the necessary RACH configuration information in any beam.

[0217] The association between RACH resource and SSB is configurable, and the resource of the RO corresponding to the SSB is periodic. If there are remaining ROs after an integer number of cycles of mapping within a defined period, these remaining ROs will not be mapped to any SSB. The number of SSBs associated with a RACH occasion (RO) is determined by the parameter SSB-per-rach-occasion, which can take values {1 / 8, 1 / 4, 1 / 2, 1, 2, 4, 8, 16}. If SSB-per-rach-occasion is less than 1, then one SSB will be mapped to 1 / SSB-per-rach-occasion consecutive RACH occasions.

[0218] FIG. 11 is a schematic diagram of the mapping relationship between SSB and RO. In this example, the mapping period of SSB and RO is 10 ms, SSB#0 is associated with RO#0 and RO#1, SSB#1 is associated with RO#2 and RO#3, SSB#2 is associated with RO#4 and RO#5, SSB#3 is associated with RO#6 and RO#7, SSB#4 is associated with RO#8 and RO#9, SSB#5 is associated with RO#10 and RO#11, SSB#6 is associated with RO#12 and RO#13, SSB#7 is associated with RO#14 and RO#15.

[0219] One RACH slot supports at least a certain number of ROs to meet the access requirements in different scenarios. Table 5 is an example of the number of ROs supported by one RACH slot under different preamble formats.

[0220] Table 5

[0221] In addition, NR supports multiple Msg1 transmissions before the end of the monitored RAR time window to support terminal device scanning transmission beams and improve the success rate of random access. When retransmitting RACH, the terminal device calculates the transmission power of RACH based on the latest estimated path loss and power boost, and the measurement of path loss is performed on the SSB associated with the RACH resource.

[0222] For single Msg1 RACH, the RAR time window starts from the first available control resource set (CORESET) after a fixed duration after the end of Msg1 transmission. The timing design of RACH should meet the decoding capability of the terminal device, for example, the minimum time interval between Msg2 and Msg3 should not be lower than a certain value to ensure that the terminal device has enough time to decode and respond.

[0223] Currently, RACH is transmitted on the uplink carrier corresponding to the downlink carrier used to transmit SSB, and one downlink BWP of one downlink carrier is associated with one uplink BWP of one uplink carrier, which can be understood as one downlink carrier in one cell being associated with one uplink carrier. How to further improve the flexibility of RACH resource allocation needs to be studied.

[0224] The method for random access provided in the embodiments of the present application can reduce the time delay of random access, thereby improving the communication performance. The method for random access provided in the embodiments of the present application is applied to a first communication device and a second communication device, for example, is executed by the first communication device and the second communication device. The first communication device in the present application can be a terminal device or a module (for example, a circuit, a chip, a chip system or a processor) in the terminal device, and can also be a logical node, a logical module or software capable of realizing all or part of the functions of the terminal device. The second communication device in the present application can be a network device or a module (for example, a circuit, a chip, a chip system or a processor) in the network device, and can also be a logical node, a logical module or software capable of realizing all or part of the functions of the network device; or the second communication device in the present application can be a terminal device or a module (for example, a circuit, a chip, a chip system or a processor) in the terminal device, and can also be a logical node, a logical module or software capable of realizing all or part of the functions of the terminal device. The chip can be a modem chip, also known as a baseband chip; or can be a system on chip (SoC) chip containing a modem core; or can be a system in package (SIP) chip. The network device in the embodiments of the present application can be a base station. In the present application, x is associated, and it can be understood that x is corresponding, or x has an association relationship. The number of x can be understood as the index or identifier of x, or it can be simply referred to as the number or index or identifier of x.

[0225] FIG. 12 is a schematic flow interaction diagram of a method 1200 for random access provided in the embodiments of the present application.

[0226] S1210, the second communication device sends the first SSB on the first downlink carrier.

[0227] The first downlink carrier is used to carry at least one SSB, the at least one SSB includes the first SSB, and the RO corresponding to the at least one SSB is on the at least two uplink carriers. Correspondingly, the first communication device receives the first SSB from the second communication device on the first downlink carrier. Wherein, the first downlink carrier used to carry at least one SSB can be understood as the first downlink carrier used to transmit at least one SSB.

[0228] In the first implementation, the at least one SSB includes a first SSB and a second SSB, the at least two uplink carriers include a first uplink carrier and a second uplink carrier, the RO corresponding to the first SSB is on the first uplink carrier, and the RO corresponding to the second SSB is on the second uplink carrier. In this implementation, the RO corresponding to one SSB is on one uplink carrier. Based on this implementation, the multiple SSBs transmitted on the first downlink carrier can correspond to the ROs of the multiple uplink carriers, the flexibility of RO allocation can be improved, the access latency can be reduced, and thus the communication performance can be improved.

[0229] Optionally, the time domain position of the RO corresponding to the first SSB is the same as the time domain position of the RO corresponding to the second SSB. The resource period of the RO corresponding to the at least one SSB can be shortened, and the latency of random access can be further reduced.

[0230] Optionally, the time domain position of the RO corresponding to the first SSB is different from the time domain position of the RO corresponding to the second SSB, which is not limited in the present application.

[0231] In the second implementation, the RO corresponding to the first SSB includes a first RO and a second RO, the first RO is on the first uplink carrier, and the second RO is on the second uplink carrier. In this implementation, the RO corresponding to one SSB is on two (or multiple) uplink carriers. Based on this implementation, the first SSB can correspond to the ROs of multiple uplink carriers, the flexibility of RO allocation can be improved, the access latency can be reduced, the RACH resource of the first SSB is on two carriers, the probability of random access conflict of the communication device can be reduced, and thus the communication performance can be improved.

[0232] Optionally, the time domain position of the first RO is the same as the time domain position of the second RO, the resource period of the RO corresponding to the first SSB can be shortened, and the latency of random access can be further reduced.

[0233] Optionally, the time domain position of the first RO is different from the time domain position of the second RO.

[0234] Optionally, S1211, the second communication device sends first configuration information to the first communication device, the first configuration information being used to indicate that the first downlink carrier is associated with the at least two uplink carriers; correspondingly, the first communication device receives the first configuration information from the second communication device. The first communication device can determine the association relationship between the first downlink carrier and the at least two uplink carriers according to the first configuration information, the flexibility of RO allocation can be improved, and thus the communication performance can be improved.

[0235] Optionally, the first configuration information includes the identifier (or index) of the at least two uplink carriers corresponding to the first downlink carrier.

[0236] Exemplarily, the first configuration information comprises an identifier (or index) of the first uplink carrier and an identifier (or index) of the second uplink carrier.

[0237] Exemplarily, the first configuration information comprises an identifier (or index) of the first downlink carrier and identifiers (or indexes) of the at least two uplink carriers respectively.

[0238] Optionally, the first downlink carrier is associated with the at least two uplink carriers, comprising that a first downlink BWP of the first downlink carrier is associated with the at least two uplink carriers.

[0239] The step S1211 can be executed before the step S1210, the step S1211 can be executed after the step S1210, or the step S1211 can be executed simultaneously with the step S1210. In the case that the step S1211 is executed simultaneously with the step S1210, the first configuration information and the first SSB are transmitted through different messages.

[0240] Optionally, the first communication device determines the RO corresponding to the first SSB, and the RO corresponding to the first SSB comprises a first RO.

[0241] Optionally, the second communication device sends second configuration information to the first communication device, and the second configuration information is used to indicate the RO corresponding to the first SSB; correspondingly, the first communication device receives the second configuration information from the second communication device. Exemplarily, the first communication device determines the RO corresponding to the first SSB according to the second configuration information.

[0242] Exemplarily, the second configuration information is used to indicate the ROs corresponding to the at least one SSB respectively, which can be understood as that the second configuration information is used to indicate the RO corresponding to the first SSB and the ROs corresponding to other SSBs in the at least one SSB respectively. In this example, the ROs corresponding to the at least one SSB respectively can be indicated through the same system information or RRC signaling.

[0243] Exemplarily, the second configuration information is used to indicate the RO corresponding to the first SSB only. In this example, the ROs corresponding to the at least one SSB respectively can be indicated through different system information or different RRC signaling.

[0244] Optionally, the second communication device sends third configuration information to the first communication device, the third configuration information being used to indicate the RO corresponding to the at least one SSB. Correspondingly, the first communication device receives the third configuration information from the second communication device. Illustratively, the first communication device determines the RO corresponding to the first SSB according to the third configuration information and the predefined rule. In this optional scheme, the second communication device indicates the time-frequency positions of multiple ROs to the first communication device, and the first communication device needs to further determine the time-frequency position of the RO corresponding to the first SSB. Based on this optional scheme, the first communication device determines the RO corresponding to the first SSB through the third configuration information and the predefined rule, which can reduce the signaling overhead of configuration information, realize that the communication devices determine the same RO resource according to a unified rule, can improve the flexibility of RO allocation, and thus can improve the communication performance.

[0245] Optionally, the numbering rule of the RO can include at least one of the following.

[0246] The numbering rule of the RO #a11: first time domain numbering, and then frequency domain numbering; wherein the time domain numbering can include at least one of symbol numbering, slot numbering, or subframe numbering. The frequency domain numbering can include at least one of RB numbering, RBG numbering, or carrier numbering.

[0247] Illustratively, the numbering rule of the RO is first symbol numbering, then subframe numbering, and then frequency domain numbering; or first symbol numbering, then subframe numbering, and then carrier numbering.

[0248] For example, the time domain resource includes subframe #1 and subframe #2, subframe #1 includes symbols #0-#13, subframe #2 includes symbols #14-#27, and the frequency domain resource includes carrier #1 and carrier #2; first, the ROs on the symbols #0-#13 included in the subframe #1 corresponding to the carrier #1 are numbered, then the ROs on the symbols #14-#27 included in the subframe #2 corresponding to the carrier #1 are numbered, then the ROs on the symbols #0-#13 included in the subframe #1 corresponding to the carrier #2 are numbered, and finally the ROs on the symbols #14-#27 included in the subframe #2 corresponding to the carrier #2 are numbered.

[0249] The numbering rule of the RO #a12: first frequency domain numbering, and then time domain numbering. Illustratively, the RO numbering is first carrier numbering, then time domain numbering; or first carrier numbering, then symbol numbering, and then subframe numbering.

[0250] For example, the time domain resource includes subframe #1 and subframe #2, subframe #1 includes symbols #0-#13, subframe #2 includes symbols #14-#27, and the frequency domain resource includes carrier #1 and carrier #2;

[0251] The ROs on the symbol #0 included in the subframe #1 corresponding to the carrier #1 are numbered first, and the ROs on the symbol #0 included in the subframe #1 corresponding to the carrier #2 are numbered.

[0252] The ROs on the symbol #m included in the subframe #1 corresponding to the carrier #1 are numbered again, and the ROs on the symbol #m included in the subframe #1 corresponding to the carrier #2 are numbered again.

[0253] The ROs on the symbol #13 included in the subframe #1 corresponding to the carrier #1 are numbered again, and the ROs on the symbol #13 included in the subframe #1 corresponding to the carrier #2 are numbered again, wherein m is a positive integer less than 13.

[0254] The ROs on the symbol #14 included in the subframe #2 corresponding to the carrier #1 are numbered again, and the ROs on the symbol #14 included in the subframe #2 corresponding to the carrier #2 are numbered again.

[0255] The ROs on the symbol #q included in the subframe #2 corresponding to the carrier #1 are numbered again, and the ROs on the symbol #q included in the subframe #2 corresponding to the carrier #2 are numbered again.

[0256] The ROs on the symbol #27 included in the subframe #2 corresponding to the carrier #1 are numbered again, and the ROs on the symbol #27 included in the subframe #2 corresponding to the carrier #2 are numbered again, wherein q is an integer greater than 14 and less than 27.

[0257] For another example, the time domain resource includes the subframe #1 and the subframe #2, the subframe #1 includes the symbols #0-#13, the subframe #2 includes the symbols #14-#27, the frequency domain resource includes the carrier #1 and the carrier #2; the ROs on the symbols #0-#13 included in the subframe #1 corresponding to the carrier #1 are numbered first, the ROs on the symbols #0-#13 included in the subframe #1 corresponding to the carrier #2 are numbered, the ROs on the symbols #14-#27 included in the subframe #2 corresponding to the carrier #1 are numbered again, and the ROs on the symbols #14-#27 included in the subframe #2 corresponding to the carrier #2 are numbered last.

[0258] For example, the time domain resource includes subframe #1 and subframe #2, the subframe #1 includes symbol #0~#13, the subframe #2 includes symbol #14~#27, the frequency domain resource includes carrier #1 and carrier #2; the ROs on symbol #0~#s1 included in the subframe #1 corresponding to the carrier #1 are numbered first, then the ROs on symbol #0~#s1 included in the subframe #1 corresponding to the carrier #2 are numbered, the ROs on symbol #s1~#13 included in the subframe #1 corresponding to the carrier #1 are numbered first, then the ROs on symbol #s1~#13 included in the subframe #1 corresponding to the carrier #2 are numbered, wherein s1 is an integer greater than 0 and less than 13; the ROs on symbol #14~#s2 included in the subframe #2 corresponding to the carrier #1 are numbered first, then the ROs on symbol #14~#s2 included in the subframe #2 corresponding to the carrier #2 are numbered, the ROs on symbol #s2~#27 included in the subframe #2 corresponding to the carrier #1 are numbered, and finally the ROs on symbol #s2~#27 included in the subframe #2 corresponding to the carrier #2 are numbered, wherein s2 is an integer greater than 14 and less than 27.

[0259] The numbering rule #a13 of the RO: the ROs on different frequency domains are numbered respectively; wherein the frequency domain can refer to a carrier.

[0260] For example, the ROs on the first uplink carrier are numbered as RO#0~RO#C0, and the ROs on the second uplink carrier are numbered as RO#0~RO#C1; wherein C0 and C1 are positive integers; C0 and C1 can be the same or different.

[0261] Optionally, the mapping rule of the SSB identifier corresponding to the RO can include at least one of the following. The mapping rule of the SSB identifier corresponding to the RO can be understood as mapping the identifier / SSB of different ROs corresponding to the SSB in the case that the RO has been determined.

[0262] The mapping rule #b11 of the SSB identifier corresponding to the RO: the SSB identifier is mapped first in time domain, and then in frequency domain; wherein the time domain mapping can include at least one of symbol mapping, time slot mapping, or subframe mapping. The frequency domain mapping can include at least one of RB mapping, RBG mapping, or carrier mapping.

[0263] Exemplarily, the mapping rule of the SSB identifier corresponding to the RO is: first symbol mapping, then subframe mapping, and then frequency domain mapping; or first symbol mapping, then subframe mapping, and then carrier mapping. For example, the time domain resource includes subframe #1 and subframe #2, the frequency domain resource includes carrier #1 and carrier #2, RO #0 and RO #1 are on symbol #0 included in subframe #1 corresponding to carrier #1, RO #2 and RO #3 are on symbol #1 included in subframe #1 corresponding to carrier #1, RO #4 and RO #5 are on symbol #0 included in subframe #2 corresponding to carrier #1, RO #6 and RO #7 are on symbol #1 included in subframe #2 corresponding to carrier #1, RO #8 and RO #9 are on symbol #0 included in subframe #1 corresponding to carrier #2, RO #10 and RO #11 are on symbol #1 included in subframe #1 corresponding to carrier #2, RO #12 and RO #13 are on symbol #0 included in subframe #2 corresponding to carrier #2, and RO #14 and RO #15 are on symbol #1 included in subframe #2 corresponding to carrier #2; first mapping the identifiers of the SSBs corresponding to RO #0 and RO #1, then mapping the identifiers of the SSBs corresponding to RO #2 and RO #3, then mapping the identifiers of the SSBs corresponding to RO #4 and RO #5, then mapping the identifiers of the SSBs corresponding to RO #6 and RO #7, then mapping the identifiers of the SSBs corresponding to RO #8 and RO #9, then mapping the identifiers of the SSBs corresponding to RO #10 and RO #11, then mapping the identifiers of the SSBs corresponding to RO #12 and RO #13, and finally mapping the identifiers of the SSBs corresponding to RO #14 and RO #15.

[0264] Mapping rule #b12 of the SSB identifier corresponding to the RO: first frequency domain mapping, and then time domain mapping.

[0265] Exemplarily, the mapping rule of the SSB identifier corresponding to the RO is: first carrier mapping, then time domain mapping; or, first carrier mapping, then symbol mapping, and then subframe mapping. For example, the time domain resource includes subframe #1 and subframe #2, the frequency domain resource includes carrier #1 and carrier #2, RO #0 and RO #1 are on symbol #0 included in subframe #1 corresponding to carrier #1, RO #2 and RO #3 are on symbol #1 included in subframe #1 corresponding to carrier #1, RO #4 and RO #5 are on symbol #0 included in subframe #2 corresponding to carrier #1, RO #6 and RO #7 are on symbol #1 included in subframe #2 corresponding to carrier #1, RO #8 and RO #9 are on symbol #0 included in subframe #1 corresponding to carrier #2, RO #10 and RO #11 are on symbol #1 included in subframe #1 corresponding to carrier #2, RO #12 and RO #13 are on symbol #0 included in subframe #2 corresponding to carrier #2, and RO #14 and RO #15 are on symbol #1 included in subframe #2 corresponding to carrier #2; first mapping the identifiers of the SSBs corresponding to RO #0 and RO #1, then mapping the identifiers of the SSBs corresponding to RO #8 and RO #9, then mapping the identifiers of the SSBs corresponding to RO #2 and RO #3, then mapping the identifiers of the SSBs corresponding to RO #10 and RO #11, then mapping the identifiers of the SSBs corresponding to RO #4 and RO #5, then mapping the identifiers of the SSBs corresponding to RO #12 and RO #13, then mapping the identifiers of the SSBs corresponding to RO #6 and RO #7, and finally mapping the identifiers of the SSBs corresponding to RO #14 and RO #15.

[0266] Optionally, the mapping rule of the SSB identifier corresponding to the RO can include at least one of the following. The mapping rule of the SSB identifier corresponding to the RO can be understood as mapping the RO / RO number corresponding to different SSBs in the case that the SSB has been determined.

[0267] The mapping rule #c11 of the SSB identifier corresponding to the RO is: first time domain mapping, and then frequency domain mapping; wherein the time domain mapping can include at least one of symbol mapping, time slot mapping, or subframe mapping. The frequency domain mapping can include at least one of RB mapping, RBG mapping, or carrier mapping.

[0268] Exemplarily, the mapping rule of the SSB identifier corresponding to the RO number is: first symbol mapping, then subframe mapping, and then frequency domain mapping; or, first symbol mapping, then subframe mapping, and then carrier mapping.

[0269] The mapping rule #c12 of the SSB identifier corresponding to the RO is: first frequency domain mapping, and then time domain mapping. Exemplarily, the mapping rule of the SSB identifier corresponding to the RO number is: first carrier mapping, then time domain mapping; or, first carrier mapping, then symbol mapping, and then subframe mapping.

[0270] Optionally, the scheme of mapping the RO corresponding to the SSB carried on one downlink carrier to two uplink carriers can include at least one of the following.

[0271] 1) Mapping according to RO number: in the order of the size of the RO number, the first half of the RO is mapped to the first uplink carrier, and the second half of the RO is mapped to the second uplink carrier; for example, the RO number includes RO#0-#15, RO#0-#7 (the first half of the RO) is mapped to the first uplink carrier, and RO#8-#15 (the second half of the RO) is mapped to the second uplink carrier.

[0272] 2) Mapping according to SSB number: in the order of the size of the SSB number, the RO corresponding to the first half of the SSB number is mapped to the first uplink carrier, and the RO corresponding to the second half of the SSB number is mapped to the second uplink carrier; for example, the SSB number includes SSB#0-#7, SSB#0-#3 (the first half of the SSB) is mapped to the first uplink carrier, and SSB#4-#7 (the second half of the SSB) is mapped to the second uplink carrier.

[0273] 3) Mapping according to the RO corresponding to one SSB number: in the order of the size of the RO number corresponding to one SSB number, the first half of the RO corresponding to one SSB number is mapped to the first uplink carrier, and the second half of the RO corresponding to one SSB number is mapped to the second uplink carrier. It can be understood that the first half of the RO is sorted in the order of the size of the RO number corresponding to one SSB number, and the RO in the first 1 / 2 is sorted; the second half of the RO can be understood as being sorted in the order of the size of the RO number, and the RO in the second 1 / 2 is sorted. For example, SSB#0 corresponds to RO#0-#3, RO#0 and RO#1 (the first half of the RO) are mapped to the first uplink carrier, and RO#2 and RO#3 (the second half of the RO) are mapped to the second uplink carrier.

[0274] Optionally, the numbering rule and the pre-defined rule of the RO can include at least one of the following.

[0275] RO numbering rule #d11: the numbering of the RO is first by symbol / slot number, then by subframe number, and finally by carrier number.

[0276] Exemplarily, in the order of the RO number, the RO of the first half of the RO number is in the first uplink carrier, and the RO of the second half of the RO number is in the second uplink carrier. For example, the RO number includes RO#0-#15, RO#0-#7 (the first half of the RO) is mapped to the first uplink carrier, and RO#8-#15 (the second half of the RO) is mapped to the second uplink carrier.

[0277] The mapping relationship between the SSB and the RO #e11: In the order of the size of the SSB number, the RO corresponding to the first half of the SSB identifier is mapped to the first uplink carrier, and the RO corresponding to the second half of the SSB identifier is mapped to the second uplink carrier. For example, the SSB identifier includes SSB#0~#7, SSB#0~#3 (the first half of the SSB) is mapped to the first uplink carrier, and SSB#4~#7 (the second half of the SSB) is mapped to the second uplink carrier.

[0278] Exemplarily, the RO corresponding to the SSB identifier is sequentially mapped in the order of the RO number. The RO number #0~RO number #n0-1 corresponds to SSB identifier #0, and the number of ROs of SSB identifier #0 is n0; the RO number #n0~RO number n0+n1-1 corresponds to SSB identifier #1, and the number of ROs of SSB identifier #1 is n1; …; the RO number #n N-2 -1 corresponds to SSB identifier #N-1, wherein the number of ROs of SSB identifier #N-1 is n N-1 . N-1 . N-1 , wherein N, n0, n1, …, n N-1 are positive integers.

[0279] Optionally, the RO number #x in the present application can be abbreviated as RO #x.

[0280] Optionally, the SSB identifier #y in the present application can be abbreviated as SSB #y.

[0281] Optionally, the mapping relationship between the SSB and the RO in the present application can also be understood as the mapping relationship between the SSB identifier and the RO number.

[0282] Optionally, the RO corresponding to the SSB in the present application can also be understood as the RO corresponding to the SSB identifier.

[0283] For example, the at least one SSB includes SSB#0-SSB#7, the at least one SSB corresponds to RO#0-RO#15, and the third configuration information is used to indicate that SSB#0-SSB#7 correspond to RO#0-RO#15. FIG. 13 is a schematic diagram of a mapping relationship between SSB and RO provided by an embodiment of the present application. SSB#0-SSB#3 correspond to RO#0-RO#7 on the first uplink carrier, and SSB#4-SSB#7 correspond to RO#8-RO#15 on the second uplink carrier. In this example, the numbering of the ROs is sequentially numbered in the time domain first and then in the frequency domain. Specifically, the numbering of the ROs is sequentially numbered in the symbols / time slots first, then in the subframes, and finally in the carriers. As shown in FIG. 13, the ROs are numbered in the symbols / time slots included in subframe#1 corresponding to the first uplink carrier first, then in the symbols / time slots included in subframe#4 corresponding to the first uplink carrier, then in the symbols / time slots included in subframe#1 corresponding to the second uplink carrier, and finally in the symbols / time slots included in subframe#4 corresponding to the second uplink carrier. The predefined rule defines that the SSB with a number / index of #0 corresponds to the ROs with numbers of #0 and #1, the SSB with a number of #1 corresponds to the ROs with numbers of #2 and #3, the SSB with a number of #2 corresponds to the ROs with numbers of #4 and #5, the SSB with a number of #3 corresponds to the ROs with numbers of #6 and #7, the SSB with a number of #4 corresponds to the ROs with numbers of #8 and #9, the SSB with a number of #5 corresponds to the ROs with numbers of #10 and #11, the SSB with a number of #6 corresponds to the ROs with numbers of #12 and #13, and the SSB with a number of #7 corresponds to the ROs with numbers of #14 and #15. If the first SSB is SSB#0, the first communication device determines, according to the third configuration information and the predefined rule, that the ROs corresponding to SSB#0 are RO#0 and RO#1.

[0284] Optionally, the numbering rule of the ROs and the predefined rule can include at least one of the following.

[0285] RO numbering rule #d12: the ROs are numbered by symbol / subframe first, then by carrier, and finally by subframe. For example, the time domain resource includes subframe #1 and subframe #2, subframe #1 includes symbols #0~#13, subframe #2 includes symbols #14~#27, and the frequency domain resource includes carrier #1 and carrier #2; the ROs on symbols #0~#13 included in subframe #1 corresponding to carrier #1 are numbered first, then the ROs on symbols #0~#13 included in subframe #1 corresponding to carrier #2 are numbered, then the ROs on symbols #14~#27 included in subframe #2 corresponding to carrier #1 are numbered, and finally the ROs on symbols #14~#27 included in subframe #2 corresponding to carrier #2 are numbered. Exemplarily, the ROs are mapped to the first uplink carrier and the second uplink carrier in the RO numbering order. For example, the RO numbering includes ROs #0~#15, ROs #0~#3 are mapped to the first uplink carrier, ROs #4~#7 are mapped to the second uplink carrier, ROs #8~#11 are mapped to the first uplink carrier, and ROs #12~#15 are mapped to the second uplink carrier.

[0286] Mapping relationship between SSB and RO #e12: the ROs corresponding to the SSBs are mapped to the first uplink carrier and the second uplink carrier in the RO numbering order. For example, the RO numbering includes ROs #0~#15, ROs #0~#3 are mapped to the first uplink carrier, ROs #4~#7 are mapped to the second uplink carrier, ROs #8~#11 are mapped to the first uplink carrier, and ROs #12~#15 are mapped to the second uplink carrier.

[0287] For example, the ROs corresponding to SSB identification #0 and the ROs corresponding to SSB identification #1 are in the first uplink carrier; the ROs corresponding to SSB identification #2 and the ROs corresponding to SSB identification #3 are in the second uplink carrier; the ROs corresponding to SSB identification #4 and the ROs corresponding to SSB identification #5 are in the first uplink carrier; and the ROs corresponding to SSB identification #6 and the ROs corresponding to SSB identification #7 are in the second uplink carrier.

[0288] For example, the ROs corresponding to the SSBs are mapped in the RO numbering order. RO numbering #0~RO numbering #n0-1 correspond to SSB identification #0, the number of ROs corresponding to SSB #0 is n0; RO numbering #n0~RO numbering n0+n1-1 correspond to SSB identification #1, the number of ROs corresponding to SSB #1 is n1; …; RO numbering #n N-2 ~RO numbering n N-1 +n N-1 -1 correspond to SSB identification #N-1, the number of ROs corresponding to SSB #N-1 is n N-1 , where N, n0, n1, …, n N-1 are positive integers.

[0289] For example, FIG. 14 is a schematic diagram of another mapping relationship between SSBs and ROs provided by an embodiment of the present application. SSB#0 and SSB#1 correspond to RO#0-RO#3 on subframe #1 of the first uplink carrier, SSB#2 and SSB#3 correspond to RO#4-RO#7 on subframe #1 of the second uplink carrier, SSB#4 and SSB#5 correspond to RO#8-RO#11 on subframe #4 of the first uplink carrier, and SSB#6 and SSB#7 correspond to RO#12-RO#15 on subframe #4 of the second uplink carrier. In this example, the ROs are numbered first by symbol / slot number on subframe #1 of the first uplink carrier, then by symbol / slot number on subframe #1 of the second uplink carrier, then by symbol / slot number on subframe #4 of the first uplink carrier, and finally by symbol / slot number on subframe #4 of the second uplink carrier. The predefined rule is the same as that of FIG. 13. If the first SSB is SSB#0, the first communication device determines that the ROs corresponding to SSB#0 are RO#0 and RO#1 according to the third configuration information and the predefined rule.

[0290] Optionally, the RO numbering rule and the predefined rule can include at least one of the following.

[0291] RO numbering rule #d13: the ROs are numbered first by symbol / slot number, then by subframe number, and finally by carrier number.

[0292] For example, in RO numbering order, the ROs with the first half of the RO numbers are on the first uplink carrier, and the ROs with the second half of the RO numbers are on the second carrier.

[0293] Mapping relationship #e13 between SSBs and ROs: the ROs corresponding to SSB identifications are interleaved and mapped to the first uplink carrier and the second uplink carrier.

[0294] For example, the ROs corresponding to SSB identification #0 and the ROs corresponding to SSB identification #1 are on the first uplink carrier; the ROs corresponding to SSB identification #2 and the ROs corresponding to SSB identification #3 are on the second uplink carrier; the ROs corresponding to SSB identification #4 and the ROs corresponding to SSB identification #5 are on the first uplink carrier; and the ROs corresponding to SSB identification #6 and the ROs corresponding to SSB identification #7 are on the second uplink carrier.

[0295] For example, SSBs with the same SSB index are staggered mapped according to RO index. RO index #0~RO index #n0-1 correspond to SSB index #0, the number of ROs of SSB #0 is n0; RO index #n0~RO index n0+n1-1 correspond to SSB index #1, the number of ROs of SSB #1 is n1; RO index #n1~RO index n1+n2-1 correspond to SSB index #1, the number of ROs of SSB index #x is n1; RO index #n2~RO index n2+n3-1 correspond to SSB index #1, the number of ROs of SSB #x+1 is n1; …; RO index #n N-2 ~RO index n N-1 +n N-1 -1 correspond to SSB index #N-1, the number of ROs of SSB #N-1 is n N-1 . Wherein, x, N, n0, n1, …, n N-1 are positive integers.

[0296] For example, FIG. 15 is a schematic diagram of another mapping relationship between SSBs and ROs provided by the embodiments of the present application. SSB#0 and SSB#1 correspond to RO#0-RO#3 on subframe #1 of the first uplink carrier, SSB#2 and SSB#3 correspond to RO#8-RO#11 on subframe #1 of the second uplink carrier, SSB#4 and SSB#5 correspond to RO#4-RO#7 on subframe #4 of the first uplink carrier, and SSB#6 and SSB#7 correspond to RO#12-RO#15 on subframe #4 of the second uplink carrier. In this example, the ROs are numbered sequentially in the time domain first and then in the frequency domain. Specifically, the ROs are numbered sequentially by symbol / slot first, then by subframe, and finally by carrier. As shown in FIG. 15, the ROs are numbered sequentially by ROs on the symbol / slot included in subframe #1 of the first uplink carrier first, then by ROs on the symbol / slot included in subframe #4 of the first uplink carrier, then by ROs on the symbol / slot included in subframe #1 of the second uplink carrier, and finally by ROs on the symbol / slot included in subframe #4 of the second uplink carrier. The predefined rule defines that SSB with a number / index of #0 corresponds to ROs with numbers of #0 and #1, SSB with a number of #1 corresponds to ROs with numbers of #2 and #3, SSB with a number of #2 corresponds to ROs with numbers of #8 and #9, SSB with a number of #3 corresponds to ROs with numbers of #10 and #11, SSB with a number of #4 corresponds to ROs with numbers of #4 and #5, SSB with a number of #5 corresponds to ROs with numbers of #6 and #7, SSB with a number of #6 corresponds to ROs with numbers of #12 and #13, and SSB with a number of #7 corresponds to ROs with numbers of #14 and #15. If the first SSB is SSB#0, the first communication device determines, according to the third configuration information and the predefined rule, that SSB#0 corresponds to RO#0 and RO#1.

[0297] Optionally, the RO numbering rule and the predefined rule can include at least one of the following.

[0298] RO numbering rule #d14: the ROs are numbered sequentially by carrier first and then by symbol / slot / subframe.

[0299] For example, the ROs are mapped to the first uplink carrier and the second uplink carrier in the RO numbering order. For example, the ROs are numbered as RO#0-RO#15, RO#0, RO#2, RO#4, RO#6, RO#8, RO#10, RO#12, and RO#14 are mapped to the first uplink carrier, and RO#1, RO#3, RO#5, RO#7, RO#9, RO#11, RO#13, and RO#15 are mapped to the second uplink carrier.

[0300] The mapping relationship between SSB and RO #e14: the RO corresponding to the SSB identification is sequentially mapped to the first uplink carrier, and the RO corresponding to the SSB identification is sequentially mapped to the second uplink carrier. Wherein, the RO corresponding to one SSB identification can be mapped to the first uplink carrier and the second uplink carrier.

[0301] For example, the RO of SSB identification #0, the RO of SSB identification #1, the RO of SSB identification #2, the RO of SSB identification #3, the RO of SSB identification #4, and the RO of SSB identification #5, the RO of SSB identification #6, and the RO of SSB identification #7 are in the first uplink carrier; the RO of SSB identification #0, the RO of SSB identification #1, the RO of SSB identification #2, the RO of SSB identification #3, the RO of SSB identification #4, and the RO of SSB identification #5, the RO of SSB identification #6, and the RO of SSB identification #7 are in the second uplink carrier.

[0302] For example, the RO corresponding to the SSB identification is staggered according to the RO number. RO number #0-RO number #n0-1 corresponds to SSB identification #0, the number of ROs of SSB #0 is n0; RO number #n0-RO number n0+n1-1 corresponds to SSB identification #1, the number of ROs of SSB #1 is n1; RO number #n1-RO number n1+n2-1 corresponds to SSB identification #1, the number of ROs of SSB #x is n1; RO number #n2-RO number n2+n3-1 corresponds to SSB identification #1, the number of ROs of SSB #x+1 is n1; …; RO number #n N-2 -RO number n N-1 +n N-1 -1 corresponds to SSB identification #N-1, and the number of ROs of SSB #N-1 is n N-1 . Wherein, x, N, n0, n1, …, n N-1 are positive integers.

[0303] For example, FIG. 16 is a schematic diagram of another mapping relationship between SSBs and ROs provided by an embodiment of the present application. Each SSB corresponds to two ROs, one RO on the first uplink carrier and the other RO on the second uplink carrier. In this example, the numbering of ROs is first by carrier and then by symbol / slot. As shown in FIG. 16, the first RO included in subframe #1 corresponding to the first uplink carrier is numbered first, the first RO included in subframe #1 corresponding to the second uplink carrier is numbered second, the second RO included in subframe #1 corresponding to the first uplink carrier is numbered third, the second RO included in subframe #1 corresponding to the second uplink carrier is numbered fourth, and so on. The predefined rule is the same as that of FIG. 13. If the first SSB is SSB #0, the first communication device determines, according to the third configuration information and the predefined rule, that the ROs corresponding to SSB #0 are RO #0 and RO #1.

[0304] Optionally, the RO numbering rule and the predefined rule can include at least one of the following.

[0305] RO numbering rule #d15: The numbering of ROs is first by symbol / slot / subframe and then by carrier.

[0306] For example, in the RO numbering order, the ROs numbered in the first half are on the first uplink carrier and the ROs numbered in the second half are on the second uplink carrier.

[0307] Mapping relationship #e15 between SSBs and ROs: The ROs corresponding to an SSB identifier are sequentially mapped to the first uplink carrier and the ROs corresponding to the SSB identifier are sequentially mapped to the second uplink carrier. The ROs corresponding to one SSB identifier can be mapped to the first uplink carrier and the second uplink carrier.

[0308] For example, the ROs corresponding to SSB identifier #0, the ROs corresponding to SSB identifier #1, the ROs corresponding to SSB identifier #2, the ROs corresponding to SSB identifier #3, the ROs corresponding to SSB identifier #4 and the ROs corresponding to SSB identifier #5, the ROs corresponding to SSB identifier #6 and the ROs corresponding to SSB identifier #7 are on the first uplink carrier; and the ROs corresponding to SSB identifier #0, the ROs corresponding to SSB identifier #1, the ROs corresponding to SSB identifier #2, the ROs corresponding to SSB identifier #3, the ROs corresponding to SSB identifier #4 and the ROs corresponding to SSB identifier #5, the ROs corresponding to SSB identifier #6 and the ROs corresponding to SSB identifier #7 are on the second uplink carrier.

[0309] For example, on the first uplink carrier, the ROs corresponding to an SSB identifier are sequentially mapped in the RO numbering order. On the second uplink carrier, the ROs corresponding to an SSB identifier are sequentially mapped in the RO numbering order.

[0310] The mapping on the first uplink carrier is as follows:

[0311] RO number #0~RO number #n0-1 correspond to SSB identity #0, and the number of ROs of SSB #0 is n0;

[0312] RO number #n0~RO number n0+n1-1 correspond to SSB identity #1, and the number of ROs of SSB #1 is n1;

[0313] …;

[0314] RO number #n N-2 ~RO number n N-1 +n N-1 -1 correspond to SSB identity #N-1, and the number of ROs of SSB #N-1 is n N-1 .

[0315] The mapping on the second uplink carrier is as follows:

[0316] RO number #n N-1 ~RO number #n N -1 correspond to SSB identity #0, and the number of ROs of SSB #0 is n N ;

[0317] RO number #n N -~RO number n N +n N+1 -1 correspond to SSB identity #1, and the number of ROs of SSB #1 is n N+1 ;

[0318] …;

[0319] RO number #n 2N-2 ~RO number n 2N-2 +n 2N-1 -1 correspond to SSB identity #N-1, and the number of ROs of SSB #N-1 is n 2N-1 . Wherein, N, n0, n1, …, n N-1 , …, n 2N-1 are positive integers.

[0320] For example, FIG. 17 is a schematic diagram of another mapping relationship between SSBs and ROs provided by an embodiment of the present application. Each SSB corresponds to two ROs, one RO is on the first uplink carrier, and the other RO is on the second uplink carrier. In this example, the numbering of the ROs is first the symbol / slot / subframe number, and then the carrier number. The predefined rule defines that: the SSB with the number / index #0 corresponds to the ROs with the numbers #0 and #8, the SSB with the number #1 corresponds to the ROs with the numbers #1 and #9, the SSB with the number #2 corresponds to the ROs with the numbers #2 and #10, the SSB with the number #3 corresponds to the ROs with the numbers #3 and #11, the SSB with the number #4 corresponds to the ROs with the numbers #4 and #12, the SSB with the number #5 corresponds to the ROs with the numbers #5 and #13, the SSB with the number #6 corresponds to the ROs with the numbers #6 and #14, and the SSB with the number #7 corresponds to the ROs with the numbers #7 and #15. If the first SSB is SSB #0, the first communication device determines, according to the third configuration information and the predefined rule, that the ROs corresponding to SSB #0 are RO #0 and RO #8.

[0321] It should be noted that FIGS. 13-15 are examples of the first implementation manner described above, and FIGS. 16 and 17 are examples of the second implementation manner described above. Compared with FIG. 11, the resource period of the RO corresponding to at least one SSB in FIGS. 13-16 and 17 is shortened from 10 ms to 5 ms. Therefore, in the embodiment of the present application, the RO corresponding to at least one SSB is on at least two uplink carriers, the resource period of the RO corresponding to at least one SSB can be shortened, the time delay of random access can be reduced, and thus the communication performance can be improved.

[0322] S1220, the first communication device sends a RACH preamble sequence to the second communication device on the first RO corresponding to the first SSB. Correspondingly, the second communication device receives the RACH preamble sequence from the first communication device on the first RO corresponding to the first SSB. In some embodiments of the present application, sending a RACH preamble sequence can be understood as sending a RACH / preamble / RACH preamble / random access request message / Msg1 / MsgA.

[0323] Optionally, the first communication device sends a RACH preamble sequence to the second communication device on the first RO and the second RO corresponding to the first SSB, wherein the ROs corresponding to the first SSB include the first RO and the second RO; and correspondingly, the second communication device receives the RACH preamble sequence from the first communication device on the first RO and the second RO corresponding to the first SSB.

[0324] For example, the time domain position corresponding to the first RO and the time domain position corresponding to the second RO are the same, and the frequency domain position corresponding to the first RO and the frequency domain position corresponding to the second RO are different.

[0325] Exemplarily, the time domain position corresponding to the first RO is different from the time domain position corresponding to the second RO, and the frequency domain position corresponding to the first RO is the same as the frequency domain position corresponding to the second RO.

[0326] Exemplarily, the time domain position corresponding to the first RO is different from the time domain position corresponding to the second RO, and the frequency domain position corresponding to the first RO is also different from the frequency domain position corresponding to the second RO.

[0327] Optionally, the preambles sent on the first RO and the second RO can be the same or different.

[0328] In the technical scheme provided in the embodiments of the present application, the RO corresponding to the at least one SSB is on at least two uplink carriers, and the at least one SSB is transmitted through one downlink carrier (first downlink carrier); compared with the scheme in which the RO corresponding to the at least one SSB is on one uplink carrier (one downlink carrier and one uplink carrier in one cell are associated), the scheme provided in the embodiments of the present application can shorten the resource period of the RO corresponding to the at least one SSB, can reduce the latency of random access, and in addition, the RACH resource on two carriers can reduce the probability of occurrence of random access conflict of the communication device, thereby improving the communication performance.

[0329] Optionally, the second communication device sends fourth configuration information to the first communication device, the fourth configuration information being used to indicate the carrier power offset corresponding to at least one uplink carrier in the at least two uplink carriers, and the carrier power offset being used to determine the transmission power of the RACH on the at least one uplink carrier. Correspondingly, the first communication device receives the fourth configuration information from the second communication device. In some embodiments of the present application, the transmission power of the RACH can be understood as the transmission power of the RACH preamble / Msg1 / MsgA.

[0330] Exemplarily, the at least one uplink carrier includes the uplink carrier on which the first RO is located, and the first communication device determines the transmission power of the RACH on the first RO according to the carrier power offset corresponding to the uplink carrier on which the first RO is located indicated by the fourth configuration information and the path loss determined through the first SSB, and transmits the RACH preamble on the first RO corresponding to the first SSB with the transmission power; this can avoid that the second communication device cannot receive the RACH transmitted by the first communication device; in addition, the transmission power of the RACH can be determined according to the communication demand of different carriers, flexible RACH transmission can be realized, and the communication performance can be improved. The value of the carrier power offset can be a positive number or a negative number.

[0331] Exemplarily, the fourth configuration information indicates a carrier power offset corresponding to one of the at least two uplink carriers, and carrier power offsets corresponding to other uplink carriers of the at least two uplink carriers can be 0 by default. Exemplarily, the fourth configuration information indicates a carrier power offset corresponding to each of the at least two uplink carriers. It should be noted that the fourth configuration information can also indicate that carrier power offsets corresponding to one or more of the at least two uplink carriers are 0, which is not limited in the present application.

[0332] Optionally, the second communication device can also not send the fourth configuration information, and correspondingly, the first communication device can also not receive the fourth configuration information. At this time, the carrier power offset can be 0 by default.

[0333] Optionally, the carrier power offsets corresponding to the first uplink carrier and the second uplink carrier of the at least two uplink carriers are different. Optionally, the carrier power offsets corresponding to different uplink carriers of the at least two uplink carriers are different. It should be noted that the carrier power offsets corresponding to different uplink carriers of the at least two uplink carriers can also be the same, which is not limited in the present application.

[0334] It should be noted that at least two of the first configuration information, the second configuration information / third configuration information, and the fourth configuration information in the present application can be sent to the first communication device through the same message, or can be sent to the first communication device through different messages respectively.

[0335] Optionally, the first configuration information, the second configuration information / third configuration information, or the fourth configuration information in the present application can be sent to the first communication device by the third communication device, which is not limited in the present application.

[0336] FIG. 18 is a schematic flow interaction diagram of another random access method 1800 provided by an embodiment of the present application.

[0337] S1810, the second communication device sends a first SSB on a first downlink carrier, the first downlink carrier is used to carry at least one SSB, the at least one SSB includes the first SSB, and a RO corresponding to the at least one SSB is on at least two uplink BWPs. Correspondingly, the first communication device receives the first SSB from the second communication device on the first downlink carrier.

[0338] Exemplarily, different uplink BWPs of the at least two uplink BWPs are uplink BWPs included by different uplink carriers respectively. For example, the at least two uplink BWPs include BWP1 and BWP2, BWP1 is a BWP included by an uplink carrier 1, and BWP2 is a BWP included by an uplink carrier 2.

[0339] Exemplarily, the at least two BWPs are different uplink BWPs included in a same uplink carrier. For example, the at least two uplink BWPs include a BWP1 and a BWP2, the BWP1 is a first BWP included in an uplink carrier 1, and the BWP2 is a second BWP included in the uplink carrier 1.

[0340] In a first implementation, the at least one SSB includes a first SSB and a second SSB, and the at least two uplink BWPs include a first uplink BWP and a second uplink BWP, a RO corresponding to the first SSB is on the first uplink BWP, and a RO corresponding to the second SSB is on the second uplink BWP. In this implementation, a RO corresponding to one SSB is on one uplink BWP. Based on this implementation, multiple SSBs transmitted on the first downlink carrier can correspond to ROs of multiple BWPs, which can improve the flexibility of RO allocation, reduce the access delay, and thus improve the communication performance.

[0341] Optionally, a time domain location of the RO corresponding to the first SSB is the same as a time domain location of the RO corresponding to the second SSB. The resource period of the RO corresponding to the at least one SSB can be shortened, which can further reduce the random access delay.

[0342] Optionally, the time domain location of the RO corresponding to the first SSB is different from the time domain location of the RO corresponding to the second SSB, which is not limited in the present application.

[0343] In a second implementation, the RO corresponding to the first SSB includes a first RO and a second RO, and the at least two uplink BWPs include a first uplink BWP and a second uplink BWP, the first RO corresponding to the first SSB is on the first uplink BWP, and the second RO corresponding to the first SSB is on the second uplink BWP. In this implementation, a RO corresponding to one SSB is on two (or multiple) uplink BWPs. Based on this implementation, the first SSB can correspond to ROs of multiple uplink BWPs, which can improve the flexibility of RO allocation, reduce the access delay, and further reduce the probability of random access conflict of the communication device, and thus improve the communication performance.

[0344] Optionally, the time domain location of the first RO is the same as the time domain location of the second RO; the resource period of the RO corresponding to the first SSB can be shortened, which can further reduce the random access delay.

[0345] Optionally, the time domain location of the first RO is different from the time domain location of the second RO.

[0346] Optionally, S1811, the second communication device sends first configuration information to the first communication device, the first configuration information being used to indicate that the first downlink carrier is associated with the at least two uplink BWPs; correspondingly, the first communication device receives the first configuration information from the second communication device. The first communication device can determine the association relationship between the first downlink carrier and the at least two uplink BWPs according to the first configuration information, which can improve the flexibility of RO allocation, and further improve the communication performance.

[0347] In the case that one downlink carrier includes one activated downlink BWP and one uplink carrier includes one activated uplink BWP, examples of the first configuration information used to indicate that the first downlink carrier is associated with the at least two uplink BWPs include the following.

[0348] For example, the first configuration information includes the identification (or index) of the first uplink BWP and the identification (or index) of the second uplink BWP.

[0349] For example, the first configuration information includes the identification (or index) of the first downlink carrier, the identification (or index) of the at least two uplink carriers, and the identification (or index) of the activated uplink BWPs respectively included by the at least two uplink carriers.

[0350] For example, the first configuration information includes the identification (or index) of the first downlink carrier, the identification (or index) of the activated downlink BWP included by the first downlink carrier, the identification (or index) of the at least two uplink carriers, and the identification (or index) of the activated uplink BWPs respectively included by the at least two uplink carriers.

[0351] For example, the first configuration information includes the identification (or index) of the activated downlink BWP included by the first downlink carrier, and the identification (or index) of the activated uplink BWPs respectively included by the at least two uplink carriers.

[0352] In the case that one downlink carrier includes one activated downlink BWP and one uplink carrier includes multiple activated uplink BWPs, examples of the first configuration information used to indicate that the first downlink carrier is associated with the at least two uplink BWPs include the following.

[0353] For example, the first configuration information includes the identification (or index) of the first downlink carrier, the identification (or index) of one uplink carrier, and the identification (or index) of the two activated uplink BWPs included by the uplink carrier.

[0354] Exemplarily, the first configuration information comprises an identifier (or index) of the first downlink carrier, an identifier (or index) of an activated downlink BWP comprised in the first downlink carrier, an identifier (or index) of one uplink carrier, and identifiers (or indexes) of two activated uplink BWPs comprised in the uplink carrier.

[0355] Exemplarily, the first configuration information comprises an identifier (or index) of an activated downlink BWP comprised in the first downlink carrier, and identifiers (or indexes) of two activated uplink BWPs comprised in one uplink carrier.

[0356] Optionally, the first downlink carrier is associated with the at least two uplink BWPs, and the first downlink BWP comprised in the first downlink carrier is associated with the at least two uplink BWPs.

[0357] The step S1811 can be performed before the step S1810, the step S1811 can be performed after the step S1810, or the step S1811 can be performed simultaneously with the step S1810. In the case that the step S1811 is performed simultaneously with the step S1810, the first configuration information and the first SSB are transmitted through different messages.

[0358] Optionally, in S1812, the first communication apparatus determines an RO corresponding to the first SSB, and the RO corresponding to the first SSB comprises a first RO.

[0359] Optionally, the second communication apparatus sends second configuration information to the first communication apparatus, and the second configuration information is used to indicate the RO corresponding to the first SSB; correspondingly, the first communication apparatus receives the second configuration information from the second communication apparatus. Exemplarily, the first communication apparatus determines the RO corresponding to the first SSB according to the second configuration information.

[0360] Exemplarily, the second configuration information is used to indicate the ROs corresponding to the at least one SSB respectively. It can be understood that the second configuration information is used to indicate not only the RO corresponding to the first SSB, but also the ROs corresponding to other SSBs in the at least one SSB respectively. In this example, the ROs corresponding to the at least one SSB respectively can be indicated through the same system information or RRC signaling.

[0361] Exemplarily, the second configuration information is used to indicate only the RO corresponding to the first SSB. In this example, the ROs corresponding to the at least one SSB respectively can be indicated through different system information or different RRC signaling.

[0362] Optionally, the second communication device sends third configuration information to the first communication device, the third configuration information being used to indicate the RO corresponding to the at least one SSB. Correspondingly, the first communication device receives the third configuration information from the second communication device. Illustratively, the first communication device determines the RO corresponding to the first SSB according to the third configuration information and a predefined rule. In this optional scheme, the second communication device indicates the time-frequency positions of multiple ROs to the first communication device, and the first communication device needs to further determine the time-frequency position of the RO corresponding to the first SSB. The first communication device determines the RO corresponding to the first SSB through the third configuration information and the predefined rule, which can reduce the signaling overhead of configuration information, realize the determination of the same RO resource between communication devices according to a unified rule, improve the flexibility of RO allocation, and further improve the communication performance.

[0363] Optionally, the numbering rule of the RO can include at least one of the following.

[0364] The numbering rule of the RO #a21: first time domain numbering, and then frequency domain numbering; wherein the time domain numbering can include at least one of symbol numbering, slot numbering, and subframe numbering. The frequency domain numbering can include at least one of RB numbering, RBG numbering, BWP numbering, and carrier numbering.

[0365] Illustratively, the numbering rule of the RO is first symbol numbering, then subframe numbering, and then frequency domain numbering; or first symbol numbering, then subframe numbering, then BWP numbering, and then carrier numbering. For example, the time domain resource includes subframe #1 and subframe #2, subframe #1 includes symbols #0-#13, subframe #2 includes symbols #14-#27, and the frequency domain resource includes BWP #1 and BWP #2; first, the ROs on the symbols #0-#13 included in the subframe #1 corresponding to the BWP #1 are numbered, then the ROs on the symbols #14-#27 included in the subframe #2 corresponding to the BWP #1 are numbered, then the ROs on the symbols #0-#13 included in the subframe #1 corresponding to the BWP #2 are numbered, and finally the ROs on the symbols #14-#27 included in the subframe #2 corresponding to the BWP #2 are numbered.

[0366] The numbering rule of the RO #a22: first frequency domain numbering, and then time domain numbering. Illustratively, the RO numbering is first BWP numbering, then carrier numbering, and then time domain numbering; or first BWP numbering, then carrier numbering, then symbol numbering, and then subframe numbering.

[0367] For example, the time domain resource includes subframe #1 and subframe #2, subframe #1 includes symbols #0-#13, subframe #2 includes symbols #14-#27, and the frequency domain resource includes BWP #1 and BWP #2; first, the ROs on the symbol #0 included in the subframe #1 corresponding to the BWP #1 are numbered, then the ROs on the symbol #0 included in the subframe #1 corresponding to the BWP #2 are numbered;...;

[0368] The ROs on the symbol #m included in the subframe #1 corresponding to the BWP #1 are numbered again, and the ROs on the symbol #m included in the subframe #1 corresponding to the BWP #2 are numbered again.

[0369] The ROs on the symbol #13 included in the subframe #1 corresponding to the BWP #1 are numbered again, and the ROs on the symbol #13 included in the subframe #1 corresponding to the BWP #2 are numbered again, where m is a positive integer less than 13.

[0370] The ROs on the symbol #14 included in the subframe #2 corresponding to the BWP #1 are numbered again, and the ROs on the symbol #14 included in the subframe #2 corresponding to the BWP #2 are numbered again.

[0371] The ROs on the symbol #q included in the subframe #2 corresponding to the BWP #1 are numbered again, and the ROs on the symbol #q included in the subframe #2 corresponding to the BWP #2 are numbered again.

[0372] The ROs on the symbol #27 included in the subframe #2 corresponding to the BWP #1 are numbered again, and the ROs on the symbol #27 included in the subframe #2 corresponding to the BWP #2 are numbered again, where q is an integer greater than 14 and less than 27.

[0373] For another example, the time domain resource includes the subframe #1 and the subframe #2, the subframe #1 includes the symbols #0-#13, the subframe #2 includes the symbols #14-#27, the frequency domain resource includes the BWP #1 and the BWP #2; the ROs on the symbols #0-#13 included in the subframe #1 corresponding to the BWP #1 are numbered first, the ROs on the symbols #0-#13 included in the subframe #1 corresponding to the BWP #2 are numbered again, the ROs on the symbols #14-#27 included in the subframe #2 corresponding to the BWP #1 are numbered again, and the ROs on the symbols #14-#27 included in the subframe #2 corresponding to the BWP #2 are numbered last.

[0374] For example, the time domain resource includes subframe #1 and subframe #2, the subframe #1 includes symbol #0~#13, the subframe #2 includes symbol #14~#27, the frequency domain resource includes BWP #1 and BWP #2; the ROs on the symbol #0~#s1 included in the subframe #1 corresponding to the BWP #1 are numbered first, and then the ROs on the symbol #0~#s1 included in the subframe #1 corresponding to the BWP #2 are numbered, the ROs on the symbol #s1~#13 included in the subframe #1 corresponding to the BWP #1 are numbered first, and then the ROs on the symbol #s1~#13 included in the subframe #1 corresponding to the BWP #2 are numbered, wherein s1 is an integer greater than 0 and less than 13; the ROs on the symbol #14~#s2 included in the subframe #2 corresponding to the BWP #1 are numbered first, and then the ROs on the symbol #14~#s2 included in the subframe #2 corresponding to the BWP #2 are numbered, the ROs on the symbol #s2~#27 included in the subframe #2 corresponding to the BWP #1 are numbered, and finally the ROs on the symbol #s2~#27 included in the subframe #2 corresponding to the BWP #2 are numbered, wherein s2 is an integer greater than 14 and less than 27.

[0375] The numbering rule #a23 of the RO: the ROs on different frequency domains are numbered respectively; wherein the frequency domain can refer to a carrier, or a BWP.

[0376] For example, the ROs on the first uplink carrier are numbered as RO#0~RO#C0, and the ROs on the second uplink carrier are numbered as RO#0~RO#C1. Wherein C0 and C1 are positive integers; C0 and C1 can be the same or different.

[0377] For example, the ROs on the first uplink BWP are numbered as RO#0~RO#C2, and the ROs on the second uplink BWP are numbered as RO#0~RO#C3. Wherein C2 and C3 are positive integers, and C2 and C3 can be the same or different.

[0378] Optionally, the mapping rule of the SSB identifier corresponding to the RO can include at least one of the following.

[0379] The mapping rule #b21 of the SSB identifier corresponding to the RO: the SSB identifier is first mapped in time domain, and then mapped in frequency domain; wherein the time domain mapping can include at least one of symbol mapping, time slot mapping, or subframe mapping. The frequency domain mapping can include at least one of RB mapping, RBG mapping, BWP mapping, or carrier mapping.

[0380] Exemplarily, the mapping rule of the SSB identifier corresponding to the RO is: first symbol mapping, then subframe mapping, and then frequency domain mapping; or first symbol mapping, then subframe mapping, then BWP mapping, and then carrier mapping. For example, the time domain resource includes subframe #1 and subframe #2, the frequency domain resource includes BWP #1 and BWP #2, RO #0 and RO #1 are on symbol #0 included in subframe #1 corresponding to BWP #1, RO #2 and RO #3 are on symbol #1 included in subframe #1 corresponding to BWP #1, RO #4 and RO #5 are on symbol #0 included in subframe #2 corresponding to BWP #1, RO #6 and RO #7 are on symbol #1 included in subframe #2 corresponding to BWP #1, RO #8 and RO #9 are on symbol #0 included in subframe #1 corresponding to BWP #2, RO #10 and RO #11 are on symbol #1 included in subframe #1 corresponding to BWP #2, RO #12 and RO #13 are on symbol #0 included in subframe #2 corresponding to BWP #2, and RO #14 and RO #15 are on symbol #1 included in subframe #2 corresponding to BWP #2; first, the identifiers of the SSBs corresponding to RO #0 and RO #1 are mapped, then the identifiers of the SSBs corresponding to RO #2 and RO #3 are mapped, then the identifiers of the SSBs corresponding to RO #4 and RO #5 are mapped, then the identifiers of the SSBs corresponding to RO #6 and RO #7 are mapped, then the identifiers of the SSBs corresponding to RO #8 and RO #9 are mapped, then the identifiers of the SSBs corresponding to RO #10 and RO #11 are mapped, then the identifiers of the SSBs corresponding to RO #12 and RO #13 are mapped, and finally, the identifiers of the SSBs corresponding to RO #14 and RO #15 are mapped.

[0381] Mapping rule #b22 of the SSB identifier corresponding to the RO: first frequency domain mapping, and then time domain mapping.

[0382] Exemplarily, the mapping rule of the SSB identifier corresponding to the RO is: first BWP mapping, then carrier mapping, and then time domain mapping; or, first BWP mapping, then carrier mapping, then symbol mapping, and then subframe mapping. For example, the time domain resource includes subframe #1 and subframe #2, the frequency domain resource includes BWP #1 and BWP #2, RO #0 and RO #1 are on symbol #0 included in subframe #1 corresponding to BWP #1, RO #2 and RO #3 are on symbol #1 included in subframe #1 corresponding to BWP #1, RO #4 and RO #5 are on symbol #0 included in subframe #2 corresponding to BWP #1, RO #6 and RO #7 are on symbol #1 included in subframe #2 corresponding to BWP #1, RO #8 and RO #9 are on symbol #0 included in subframe #1 corresponding to BWP #2, RO #10 and RO #11 are on symbol #1 included in subframe #1 corresponding to BWP #2, RO #12 and RO #13 are on symbol #0 included in subframe #2 corresponding to BWP #2, and RO #14 and RO #15 are on symbol #1 included in subframe #2 corresponding to BWP #2; first mapping the identifiers of the SSBs corresponding to RO #0 and RO #1, then mapping the identifiers of the SSBs corresponding to RO #8 and RO #9, then mapping the identifiers of the SSBs corresponding to RO #2 and RO #3, then mapping the identifiers of the SSBs corresponding to RO #10 and RO #11, then mapping the identifiers of the SSBs corresponding to RO #4 and RO #5, then mapping the identifiers of the SSBs corresponding to RO #12 and RO #13, then mapping the identifiers of the SSBs corresponding to RO #6 and RO #7, and finally mapping the identifiers of the SSBs corresponding to RO #14 and RO #15.

[0383] Optionally, the mapping rule of the SSB identifier corresponding to the RO can include at least one of the following.

[0384] The mapping rule #c21 of the SSB identifier corresponding to the RO is: first time domain mapping, and then frequency domain mapping; wherein the time domain mapping can include at least one of symbol mapping, slot mapping, or subframe mapping. The frequency domain mapping can include at least one of RB mapping, RBG mapping, BWP mapping, or carrier mapping.

[0385] Exemplarily, the mapping rule of the SSB identifier corresponding to the RO number is: first symbol mapping, then subframe mapping, and then frequency domain mapping; or, first symbol mapping, then subframe mapping, then BWP mapping, and then carrier mapping.

[0386] The mapping rule #c22 of the SSB identifier corresponding to the RO is: first frequency domain mapping, and then time domain mapping. Exemplarily, the mapping rule of the SSB identifier corresponding to the RO number is: first BWP mapping, then carrier mapping, and then time domain mapping; or, first BWP mapping, then carrier mapping, then symbol mapping, and then subframe mapping.

[0387] Optionally, the scheme of mapping the RO corresponding to the SSB carried on one downlink carrier to two uplink carriers or two uplink BWPs can include at least one of the following.

[0388] 1) Mapping according to RO number: in the order of the size of the RO number, the first half of the RO is mapped to the first uplink carrier or the first uplink BWP, and the second half of the RO is mapped to the second uplink carrier or the second uplink BWP; for example, the RO number includes RO#0-#15, RO#0-#7 (the first half of the RO) is mapped to the first uplink BWP, and RO#8-#15 (the second half of the RO) is mapped to the second uplink BWP.

[0389] 2) Mapping according to SSB number: in the order of the size of the SSB number, the RO corresponding to the first half of the SSB number is mapped to the first uplink carrier or the first uplink BWP, and the RO corresponding to the second half of the SSB number is mapped to the second uplink carrier or the second uplink BWP; for example, the SSB number includes SSB#0-#7, SSB#0-#3 (the first half of the SSB) is mapped to the first uplink BWP, and SSB#4-#7 (the second half of the SSB) is mapped to the second uplink BWP.

[0390] 3) Mapping according to the RO corresponding to one SSB number: in the order of the size of the RO number corresponding to one SSB number, the first half of the RO corresponding to one SSB number is mapped to the first uplink carrier or the first uplink BWP, and the second half of the RO corresponding to one SSB number is mapped to the second uplink carrier or the second uplink BWP.

[0391] Among them, the first half of the RO can be understood as being sorted in the order of the size of the RO number corresponding to one SSB number, and the RO in the first 1 / 2 is sorted; the second half of the RO can be understood as being sorted in the order of the size of the RO number, and the RO in the last 1 / 2 is sorted. For example, SSB#0 corresponds to RO#0-#3, RO#0 and RO#1 (the first half of the RO) are mapped to the first uplink BWP, and RO#2 and RO#3 (the second half of the RO) are mapped to the second uplink BWP.

[0392] Optionally, the numbering rule and the pre-defined rule of the RO can include at least one of the following.

[0393] RO numbering rule #d21: the numbering of the RO is first by symbol / slot number, then by subframe number, and finally by BWP number.

[0394] Exemplarily, in the order of RO numbers, ROs with the first half of RO numbers are in the first uplink BWP, and ROs with the second half of RO numbers are in the second uplink BWP. For example, RO numbers include RO#0-#15, RO#0-#7 (the first half of ROs) are mapped to the first uplink BWP, and RO#8-#15 (the second half of ROs) are mapped to the second uplink BWP.

[0395] The mapping relationship between SSB and RO #e21: in the order of SSB numbers, ROs corresponding to the first half of SSB identifiers are mapped to the first uplink BWP, and ROs corresponding to the second half of SSB identifiers are mapped to the second uplink BWP. For example, SSB identifiers include SSB#0-#7, SSB#0-#3 (the first half of SSBs) are mapped to the first uplink BWP, and SSB#4-#7 (the second half of SSBs) are mapped to the second uplink BWP.

[0396] Exemplarily, ROs corresponding to SSB identifiers are sequentially mapped in the order of RO numbers. RO number #0-RO number #n0-1 correspond to SSB identifier #0, the number of ROs of SSB identifier #0 is n0; RO number #n0-RO number n0+n1-1 correspond to SSB identifier #1, the number of ROs of SSB identifier #1 is n1; …; RO number #n N-2 -1 correspond to SSB identifier #N-1, wherein the number of ROs of SSB identifier #N-1 is n N-1 N-1 -1 correspond to SSB identifier #N-1, wherein the number of ROs of SSB identifier #N-1 is n N-1 . Wherein N, n0, n1, …, n N-1 are positive integers.

[0397] Optionally, RO number #x in the present application can be abbreviated as RO#x.

[0398] Optionally, SSB identifier #y in the present application can be abbreviated as SSB#y.

[0399] Optionally, the mapping relationship between SSB and RO in the present application can also be understood as the mapping relationship between SSB identifier and RO number.

[0400] Optionally, the RO corresponding to the SSB in the present application can also be understood as the RO corresponding to the SSB identifier.

[0401] ​For example, the at least one SSB includes SSB#0-SSB#7, the at least one SSB corresponds to RO#0-RO#15, and the third configuration information is used to indicate that SSB#0-SSB#7 corresponds to RO#0-RO#15. FIG. 19 is another example of mapping relationship between SSB and RO provided by an embodiment of the present application. SSB#0-SSB#3 corresponds to RO#0-RO#7 on the first uplink BWP, and SSB#4-SSB#7 corresponds to RO#8-RO#15 on the second uplink BWP. In this example, the numbering of RO is sequentially numbered in the time domain first and then in the frequency domain. Specifically, the numbering of RO is sequentially numbered in the symbol / slot first, then in the subframe, and finally in the BWP. As shown in FIG. 19, the numbering of RO is sequentially numbered on the RO in the symbol / slot included in the subframe#1 corresponding to the first uplink BWP, then sequentially numbered on the RO in the symbol / slot included in the subframe#4 corresponding to the first uplink BWP, then sequentially numbered on the RO in the symbol / slot included in the subframe#1 corresponding to the second uplink BWP, and finally sequentially numbered on the RO in the symbol / slot included in the subframe#4 corresponding to the second uplink BWP. The predefined rule defines that the SSB with the number / index #0 corresponds to the RO with the number #0 and #1, the SSB with the number #1 corresponds to the RO with the number #2 and #3, the SSB with the number #2 corresponds to the RO with the number #4 and #5, the SSB with the number #3 corresponds to the RO with the number #6 and #7, the SSB with the number #4 corresponds to the RO with the number #8 and #9, the SSB with the number #5 corresponds to the RO with the number #10 and #11, the SSB with the number #6 corresponds to the RO with the number #12 and #13, and the SSB with the number #7 corresponds to the RO with the number #14 and #15. If the first SSB is SSB#0, the first communication device determines that the RO corresponding to SSB#0 is RO#0 and RO#1 according to the third configuration information and the predefined rule.

[0402] Optionally, the RO numbering rule and the predefined rule can include at least one of the following:

[0403] RO numbering rule #d22: the numbering of RO is sequentially numbered in the symbol / slot first, then in the BWP, and finally in the subframe. For example, the time domain resource includes subframe#1 and subframe#2, the subframe#1 includes symbol#0-symbol#13, the subframe#2 includes symbol#14-symbol#27, and the frequency domain resource includes BWP#1 and BWP#2. The RO on symbol#0-symbol#13 included in the subframe#1 corresponding to BWP#1 is numbered first, then the RO on symbol#0-symbol#13 included in the subframe#1 corresponding to BWP#2 is numbered, then the RO on symbol#14-symbol#27 included in the subframe#2 corresponding to BWP#1 is numbered, and finally the RO on symbol#14-symbol#27 included in the subframe#2 corresponding to BWP#2 is numbered.

[0404] For example, ROs are interleaved and mapped to the first uplink BWP and the second uplink BWP in RO number order. For instance, RO numbers include RO#0 to #15, RO#0 to #3 are mapped to the first uplink BWP, RO#4 to #7 are mapped to the second uplink BWP, RO#8 to #11 are mapped to the first uplink BWP, and RO#12 to #15 are mapped to the second uplink BWP.

[0405] Mapping relationship between SSB and RO #e22: The RO corresponding to the SSB identifier is interleaved and mapped to the first uplink BWP and the second uplink BWP. For example, the RO numbers include RO#0 to #15. RO#0 to #3 are mapped to the first uplink BWP, RO#4 to #7 are mapped to the second uplink BWP, RO#8 to #11 are mapped to the first uplink BWP, and RO#12 to #15 are mapped to the second uplink BWP.

[0406] For example, the RO of SSB identifier #0 and the RO of SSB identifier #1 are in the first uplink BWP; the RO of SSB identifier #2 and the RO of SSB identifier #3 are in the second uplink BWP; the RO of SSB identifier #4 and the RO of SSB identifier #5 are in the first uplink BWP; and the RO of SSB identifier #6 and the RO of SSB identifier #7 are in the second uplink BWP.

[0407] For example, the ROs corresponding to the SSB identifiers are mapped sequentially according to their RO numbers. RO numbers #0 to #n0-1 correspond to SSB identifier #0, and the number of ROs for SSB#0 is n0; RO numbers #n0 to #n0+n1-1 correspond to SSB identifier #1, and the number of ROs for SSB#1 is n1; ...; RO numbers #n N-2 ~RO number n N-1 +n N-1 -1 corresponds to SSB identifier #N-1, and the number of ROs for SSB#N-1 is n. N-1 Where N, n0, n1, ..., n N-1 It is a positive integer.

[0408] For example, FIG. 20 is a schematic diagram of another mapping relationship between SSBs and ROs provided by an embodiment of the present application. SSB#0 and SSB#1 correspond to RO#0-RO#3 in subframe #1 of the first uplink BWP, SSB#2 and SSB#3 correspond to RO#4-RO#7 in subframe #1 of the second uplink BWP, SSB#4 and SSB#5 correspond to RO#8-RO#11 in subframe #4 of the first uplink BWP, and SSB#6 and SSB#7 correspond to RO#12-RO#15 in subframe #4 of the second uplink BWP. In this example, the ROs are numbered in the order of subframe #1 of the first uplink BWP, subframe #1 of the second uplink BWP, subframe #4 of the first uplink BWP, and subframe #4 of the second uplink BWP. The predefined rule is the same as that of FIG. 19. If the first SSB is SSB#0, the first communication device determines that the ROs corresponding to SSB#0 are RO#0 and RO#1 according to the third configuration information and the predefined rule.

[0409] Optionally, the RO numbering rule and the predefined rule can include at least one of the following.

[0410] RO numbering rule #d23: the ROs are numbered in the order of symbol / slot, subframe, and BWP.

[0411] For example, in the RO numbering order, the ROs with the first half of the RO numbers are in the first uplink BWP, and the ROs with the second half of the RO numbers are in the second BWP.

[0412] Mapping relationship #e23 between SSBs and ROs: the ROs corresponding to SSB identifications are alternately mapped to the first uplink BWP and the second uplink BWP.

[0413] For example, the ROs with SSB identification #0 and the ROs with SSB identification #1 are in the first uplink BWP; the ROs with SSB identification #2 and the ROs with SSB identification #3 are in the second uplink BWP; the ROs with SSB identification #4 and the ROs with SSB identification #5 are in the first uplink BWP; and the ROs with SSB identification #6 and the ROs with SSB identification #7 are in the second uplink BWP.

[0414] For example, SSBs with the same SSB index are mapped to ROs in a staggered manner. SSB#0 is mapped to RO#0~RO#n0-1, and the number of ROs for SSB#0 is n0; SSB#1 is mapped to RO#n0~RO#n0+n1-1, and the number of ROs for SSB#1 is n1; SSB#x is mapped to RO#n1~RO#n1+n2-1, and the number of ROs for SSB#x is n1; SSB#x+1 is mapped to RO#n2~RO#n2+n3-1, and the number of ROs for SSB#x+1 is n1; …; SSB#N-1 is mapped to RO#nN-1~RO#nN+nN-1-1, and the number of ROs for SSB#N-1 is nN-1. Wherein, x, N, n0, n1, …, nN-1 are positive integers. N-2 N-1 N-1 N-1 N-1

[0415] ​​​​​For example, FIG. 21 is a schematic diagram of another mapping relationship between SSBs and ROs provided by an embodiment of the present application. SSB#0 and SSB#1 correspond to RO#0-RO#3 on subframe #1 of the first uplink BWP, SSB#2 and SSB#3 correspond to RO#8-RO#11 on subframe #1 of the second uplink BWP, SSB#4 and SSB#5 correspond to RO#4-RO#7 on subframe #4 of the first uplink BWP, and SSB#6 and SSB#7 correspond to RO#12-RO#15 on subframe #4 of the second uplink BWP. In this example, the ROs are numbered sequentially in the time domain first and then in the frequency domain. Specifically, the ROs are numbered sequentially by symbol / slot first, then by subframe, and finally by BWP. As shown in FIG. 21, the ROs are numbered sequentially by ROs on the symbols / slots included in subframe #1 of the first uplink BWP first, then by ROs on the symbols / slots included in subframe #4 of the first uplink BWP, then by ROs on the symbols / slots included in subframe #1 of the second uplink BWP, and finally by ROs on the symbols / slots included in subframe #4 of the second uplink BWP. The predefined rule defines that SSB with a number / index of #0 corresponds to ROs with numbers of #0 and #1, SSB with a number of #1 corresponds to ROs with numbers of #2 and #3, SSB with a number of #2 corresponds to ROs with numbers of #8 and #9, SSB with a number of #3 corresponds to ROs with numbers of #10 and #11, SSB with a number of #4 corresponds to ROs with numbers of #4 and #5, SSB with a number of #5 corresponds to ROs with numbers of #6 and #7, SSB with a number of #6 corresponds to ROs with numbers of #12 and #13, and SSB with a number of #7 corresponds to ROs with numbers of #14 and #15. If the first SSB is SSB#0, the first communication apparatus determines, according to the third configuration information and the predefined rule, that SSB#0 corresponds to RO#0 and RO#1.

[0416] Optionally, the RO numbering rule and the predefined rule can include at least one of the following.

[0417] RO numbering rule #d24: The ROs are numbered sequentially by BWP first and then by symbol / slot / subframe.

[0418] For example, the ROs are mapped to the first uplink BWP and the second uplink BWP in the RO numbering order. For example, the ROs include RO#0-RO#15, RO#0, RO#2, RO#4, RO#6, RO#8, RO#10, RO#12, and RO#14 are mapped to the first uplink BWP, and RO#1, RO#3, RO#5, RO#7, RO#9, RO#11, RO#13, and RO#15 are mapped to the second uplink BWP.

[0419] The mapping relationship between SSB and RO #e14: the SSB identification corresponding RO order is mapped to the first uplink BWP, and the SSB identification corresponding RO order is mapped to the second uplink BWP. Wherein, one SSB identification corresponding RO can be mapped to the first uplink BWP and the second uplink BWP.

[0420] For example, the RO of SSB identification #0, the RO of SSB identification #1, the RO of SSB identification #2, the RO of SSB identification #3, the RO of SSB identification #4 and the RO of SSB identification #5, the RO of SSB identification #6 and the RO of SSB identification #7 are in the first uplink BWP; the RO of SSB identification #0, the RO of SSB identification #1, the RO of SSB identification #2, the RO of SSB identification #3, the RO of SSB identification #4 and the RO of SSB identification #5, the RO of SSB identification #6 and the RO of SSB identification #7 are in the second uplink BWP.

[0421] For example, the SSB identification corresponding RO is staggered according to the RO number. RO number #0-RO number #n0-1 corresponds to SSB identification #0, the number of ROs of SSB #0 is n0; RO number #n0-RO number n0+n1-1 corresponds to SSB identification #1, the number of ROs of SSB #1 is n1; RO number #n1-RO number n1+n2-1 corresponds to SSB identification #1, the number of ROs of SSB #x is n1; RO number #n2-RO number n2+n3-1 corresponds to SSB identification #1, the number of ROs of SSB #x+1 is n1; …; RO number #n N-2 -RO number n N-1 +n N-1 -1 corresponds to SSB identification #N-1, and the number of ROs of SSB #N-1 is n N-1 . Wherein, x, N, n0, n1, …, n N-1 are positive integers.

[0422] For example, FIG. 22 is a schematic diagram of another mapping relationship between SSBs and ROs provided by an embodiment of the present application. Each SSB corresponds to two ROs, one RO on the first uplink BWP and the other RO on the second uplink BWP. In this example, the numbering of ROs is first by BWP number and then by symbol / slot number; as shown in FIG. 22, the first RO included in subframe #1 corresponding to the first uplink BWP is numbered first, the first RO included in subframe #1 corresponding to the second uplink BWP is numbered second, the second RO included in subframe #1 corresponding to the first uplink BWP is numbered third, the second RO included in subframe #1 corresponding to the second uplink BWP is numbered fourth; …; the last RO included in subframe #2 corresponding to the first uplink BWP is numbered first, and the last RO included in subframe #2 corresponding to the second uplink BWP is numbered second. The predefined rule is the same as the predefined rule of FIG. 19. If the first SSB is SSB #0, the first communication device determines, according to the third configuration information and the predefined rule, that the ROs corresponding to SSB #0 are RO #0 and RO #1.

[0423] Optionally, the RO numbering rule and the predefined rule can include at least one of the following.

[0424] RO numbering rule #d25: the numbering of ROs is first by symbol / slot / subframe number and then by BWP number.

[0425] For example, in the RO numbering order, the ROs numbered in the first half are on the first uplink BWP, and the ROs numbered in the second half are on the second BWP.

[0426] Mapping relationship #e25 between SSBs and ROs: the ROs corresponding to an SSB identifier are sequentially mapped to the first uplink BWP, and the ROs corresponding to an SSB identifier are sequentially mapped to the second uplink BWP. One SSB identifier can correspond to ROs mapped to the first uplink BWP and the second uplink BWP.

[0427] For example, the ROs corresponding to SSB identifier #0, the ROs corresponding to SSB identifier #1, the ROs corresponding to SSB identifier #2, the ROs corresponding to SSB identifier #3, the ROs corresponding to SSB identifier #4 and the ROs corresponding to SSB identifier #5, the ROs corresponding to SSB identifier #6 and the ROs corresponding to SSB identifier #7 are on the first uplink BWP; the ROs corresponding to SSB identifier #0, the ROs corresponding to SSB identifier #1, the ROs corresponding to SSB identifier #2, the ROs corresponding to SSB identifier #3, the ROs corresponding to SSB identifier #4 and the ROs corresponding to SSB identifier #5, the ROs corresponding to SSB identifier #6 and the ROs corresponding to SSB identifier #7 are on the second uplink BWP.

[0428] For example, on the first uplink BWP, the ROs corresponding to an SSB identifier are sequentially mapped in the RO numbering order. On the second uplink BWP, the ROs corresponding to an SSB identifier are sequentially mapped in the RO numbering order.

[0429] For mapping on the first uplink BWP, the following applies:

[0430] RO number #0~RO number #n0-1 correspond to SSB identity #0, the number of ROs of SSB #0 is n0;

[0431] RO number #n0~RO number n0+n1-1 correspond to SSB identity #1, the number of ROs of SSB #1 is n1;

[0432] …;

[0433] RO number #n N-2 ~RO number n N-1 +n N-1 -1 correspond to SSB identity #N-1, the number of ROs of SSB #N-1 is n N-1 .

[0434] For mapping on the second uplink BWP, the following applies:

[0435] RO number #n N-1 ~RO number #n N -1 correspond to SSB identity #0, the number of ROs of SSB #0 is n N ;

[0436] RO number #n N -~RO number n N +n N+1 -1 correspond to SSB identity #1, the number of ROs of SSB #1 is n N+1 ;

[0437] …;

[0438] RO number #n 2N-2 ~RO number n 2N-2 +n 2N-1 -1 correspond to SSB identity #N-1, the number of ROs of SSB #N-1 is n 2N-1 . Wherein, N, n0, n1, …, n N-1 , …, n 2N-1 are positive integers.

[0439] For example, FIG. 23 is a schematic diagram of another mapping relationship between SSBs and ROs provided by the embodiments of the present application. Each SSB corresponds to two ROs, one RO is on the first uplink BWP, and the other RO is on the second uplink BWP. In this example, the numbering of the ROs is first the symbol / slot / subframe number, and then the BWP number. The predefined rule defines that: the SSB with the number / index #0 corresponds to the ROs with the numbers #0 and #8, the SSB with the number #1 corresponds to the ROs with the numbers #1 and #9, the SSB with the number #2 corresponds to the ROs with the numbers #2 and #10, the SSB with the number #3 corresponds to the ROs with the numbers #3 and #11, the SSB with the number #4 corresponds to the ROs with the numbers #4 and #12, the SSB with the number #5 corresponds to the ROs with the numbers #5 and #13, the SSB with the number #6 corresponds to the ROs with the numbers #6 and #14, and the SSB with the number #7 corresponds to the ROs with the numbers #7 and #15. If the first SSB is SSB #0, the first communication device determines that the ROs corresponding to SSB #0 are RO #0 and RO #8 according to the third configuration information and the predefined rule.

[0440] It should be noted that FIGS. 19-21 are examples of the above-mentioned first implementation, and FIGS. 22 and 23 are examples of the above-mentioned second implementation. Compared with FIG. 11, the resource period of the RO corresponding to at least one SSB in FIGS. 18-22 and 23 is shortened from 10 ms to 5 ms. Therefore, in the embodiments of the present application, the RO corresponding to at least one SSB is on at least two uplink BWP, the resource period of the RO corresponding to at least one SSB can be shortened, the latency of random access can be reduced, and thus the communication performance can be improved.

[0441] S1820, the first communication device sends a RACH preamble sequence to the second communication device on the first RO corresponding to the first SSB. Correspondingly, the second communication device receives the RACH preamble sequence from the first communication device on the first RO corresponding to the first SSB. In the present application, sending a RACH preamble sequence can be understood as sending a preamble / Msg1 / random access request message through RACH.

[0442] Optionally, the first communication device sends a RACH preamble sequence to the second communication device on the first RO and the second RO corresponding to the first SSB, wherein the ROs corresponding to the first SSB include the first RO and the second RO; correspondingly, the second communication device receives the RACH preamble sequence from the first communication device on the first RO and the second RO corresponding to the first SSB.

[0443] Exemplarily, the time domain position corresponding to the first RO and the time domain position corresponding to the second RO are the same, and the frequency domain position corresponding to the first RO and the frequency domain position corresponding to the second RO are different. Exemplarily, the time domain position corresponding to the first RO and the time domain position corresponding to the second RO are different, and the frequency domain position corresponding to the first RO and the frequency domain position corresponding to the second RO are the same. Exemplarily, the time domain position corresponding to the first RO and the time domain position corresponding to the second RO are different, and the frequency domain position corresponding to the first RO and the frequency domain position corresponding to the second RO are also different. Optionally, the preamble transmitted on the first RO and the second RO can be the same or different.

[0444] In the technical scheme provided in the embodiments of the present application, the RO corresponding to the at least one SSB is on at least two uplink BWPs, and the at least one SSB is transmitted through one downlink BWP; compared with the scheme in which the RO corresponding to the at least one SSB is on one uplink BWP (one downlink BWP and one uplink BWP in one cell are associated), the scheme provided in the embodiments of the present application can shorten the resource period of the RO corresponding to the at least one SSB, can reduce the latency of random access, and in addition, the RACH resource on two BWPs can reduce the probability of occurrence of random access conflict of the communication device, thereby improving the communication performance.

[0445] Optionally, the second communication device sends fifth configuration information to the first communication device, the fifth configuration information being used for indicating a BWP power offset corresponding to at least one uplink BWP in the at least two uplink BWPs, the BWP power offset being used for determining the transmission power of the RACH on the at least one uplink BWP. Correspondingly, the first communication device receives the fifth configuration information from the second communication device. Exemplarily, the at least one uplink BWP includes the uplink BWP where the first RO is located, and the first communication device determines the transmission power of the RACH on the first RO according to the BWP power offset corresponding to the uplink BWP where the first RO is located indicated by the fifth configuration information and the path loss determined according to the first SSB, and transmits the RACH preamble sequence on the first RO corresponding to the first SSB with the transmission power; this can avoid that the second communication device cannot receive the RACH transmitted by the first communication device; in addition, the transmission power of the RACH can be determined according to the communication demand of different BWPs, flexible RACH transmission can be realized, and the communication performance can be improved. The value of the BWP power offset can be a positive number or a negative number.

[0446] Exemplarily, the fifth configuration information indicates a BWP power offset corresponding to one of the at least two uplink BWPs, and a BWP power offset corresponding to another of the at least two uplink BWPs can be 0 by default. Exemplarily, the fifth configuration information indicates a BWP power offset corresponding to each of the at least two uplink BWPs. It should be noted that the fifth configuration information can also indicate that a BWP power offset corresponding to one or more of the at least two uplink BWPs is 0, which is not limited herein.

[0447] Optionally, the second communication device can also not send the fifth configuration information, and correspondingly, the first communication device can also not receive the fifth configuration information. At this time, the BWP power offset can be 0 by default.

[0448] Optionally, the BWP power offsets corresponding to the first uplink BWP and the second uplink BWP of the at least two uplink BWPs are different. Optionally, the BWP power offsets corresponding to different uplink BWPs of the at least two uplink BWPs are different. It should be noted that the BWP power offsets corresponding to different uplink BWPs of the at least two uplink BWPs can also be the same, which is not limited herein.

[0449] It should be noted that at least two of the first configuration information, the second configuration information / third configuration information, and the fifth configuration information in the present application can be sent to the first communication device through the same message, or can be sent to the first communication device through different messages respectively.

[0450] Optionally, the first configuration information, the second configuration information / third configuration information, or the fifth configuration information in the present application can be sent to the first communication device by the third communication device, which is not limited herein.

[0451] The above introduces the method of random access provided by the embodiments of the present application, and the following will introduce the execution subject for executing the method of random access.

[0452] FIG. 24 is a schematic block diagram of a communication device 2400 provided by an embodiment of the present application. The communication device 2400 can be the first communication device in the method embodiments of FIG. 12 or FIG. 18. The communication device 2400 includes:

[0453] The transceiver module 2410 is configured to receive a first synchronization signal block (SSB) from a second communication device on a first downlink carrier, the first downlink carrier being used to carry at least one SSB, the at least one SSB including the first SSB, and a random access channel opportunity (RO) corresponding to the at least one SSB being on at least two uplink carriers or on at least two uplink bandwidth parts (BWPs);

[0454] The transceiver module 2410 is further configured to transmit a random access channel (RACH) preamble sequence on the first RO corresponding to the first SSB.

[0455] Optionally, the transceiver module 2410 is further configured to receive first configuration information from the second communication device, the first configuration information being used to indicate that the first downlink carrier is associated with the at least two uplink carriers or the at least two uplink BWP.

[0456] Optionally, the transceiver module 2410 is further configured to receive second configuration information or third configuration information from the second communication device, the second configuration information being used to indicate the RO corresponding to the first SSB, the RO corresponding to the first SSB including the first RO, and the third configuration information being used to indicate the RO corresponding to the at least one SSB.

[0457] Optionally, the communication device further includes a processing module 2420 configured to determine the RO corresponding to the first SSB.

[0458] Optionally, the processing module 2420 is specifically configured to determine the RO corresponding to the first SSB according to the second configuration information, or determine the RO corresponding to the first SSB according to the third configuration information and a predefined rule.

[0459] Optionally, the at least one SSB includes the first SSB and a second SSB, the at least two uplink carriers include a first uplink carrier and a second uplink carrier, the RO corresponding to the first SSB is on the first uplink carrier, and the RO corresponding to the second SSB is on the second uplink carrier; or the at least two uplink BWP includes a first uplink BWP and a second uplink BWP, the RO corresponding to the first SSB is on the first uplink BWP, and the RO corresponding to the second SSB is on the second uplink BWP.

[0460] Optionally, a time domain position of the RO corresponding to the first SSB is the same as a time domain position of the RO corresponding to the second SSB.

[0461] Optionally, a first RO corresponding to the first SSB is on a first uplink carrier, and a second RO corresponding to the first SSB is on a second uplink carrier, wherein the ROs corresponding to the first SSB include the first RO and the second RO, and the at least two uplink carriers include the first uplink carrier and the second uplink carrier; or a first RO corresponding to the first SSB is on a first uplink BWP, and a second RO corresponding to the first SSB is on a second uplink BWP, wherein the ROs corresponding to the first SSB include the first RO and the second RO, and the at least two uplink BWPs include the first uplink BWP and the second uplink BWP.

[0462] Optionally, a time domain position of the first RO is the same as a time domain position of the second RO.

[0463] Optionally, the transceiver 2410 is further configured to receive fourth configuration information from the second communication device, the fourth configuration information being used to indicate a carrier power offset corresponding to at least one uplink carrier of the at least two uplink carriers, the carrier power offset being used to determine a transmission power of a RACH on the at least one uplink carrier; or receive fifth configuration information from the second communication device, the fifth configuration information being used to indicate a BWP power offset corresponding to at least one uplink BWP of the at least two uplink BWPs, the BWP power offset being used to determine a transmission power of a RACH on the at least one uplink BWP.

[0464] Optionally, carrier power offsets corresponding to a first uplink carrier and a second uplink carrier of the at least two uplink carriers are different, or BWP power offsets corresponding to a first uplink BWP and a second uplink BWP of the at least two uplink BWPs are different.

[0465] FIG. 25 is a schematic block diagram of another communication device 2500 provided by an embodiment of the present application. The communication device 2500 can be the second communication device in the method embodiments of FIG. 12 or FIG. 18. The communication device 2500 includes:

[0466] a transceiver 2510 configured to transmit a first SSB on a first downlink carrier, the first downlink carrier being used to carry at least one SSB, the at least one SSB including the first SSB, and ROs corresponding to the at least one SSB being on at least two uplink carriers or at least two uplink BWPs;

[0467] The transceiver 2510 is further configured to receive a RACH preamble sequence from a first communication device on a first RO corresponding to the first SSB.

[0468] Optionally, the transceiver is further configured to send, to the first communication device, first configuration information, where the first configuration information is used to indicate that the first downlink carrier is associated with the at least two uplink carriers or the at least two uplink BWPs.

[0469] Optionally, the transceiver 2510 is further configured to send, to the first communication device, second configuration information or third configuration information, where the second configuration information is used to indicate the RO corresponding to the first SSB, and the first SSB corresponds to the first RO, and the third configuration information is used to indicate the RO corresponding to the at least one SSB.

[0470] Optionally, the at least one SSB includes the first SSB and a second SSB, the at least two uplink carriers include a first uplink carrier and a second uplink carrier, the RO corresponding to the first SSB is on the first uplink carrier, and the RO corresponding to the second SSB is on the second uplink carrier; or, the at least two uplink BWPs include a first uplink BWP and a second uplink BWP, the RO corresponding to the first SSB is on the first uplink BWP, and the RO corresponding to the second SSB is on the second uplink BWP.

[0471] Optionally, a time domain location of the RO corresponding to the first SSB is the same as a time domain location of the RO corresponding to the second SSB.

[0472] Optionally, a first RO corresponding to the first SSB is on a first uplink carrier, and a second RO corresponding to the first SSB is on a second uplink carrier, where the RO corresponding to the first SSB includes the first RO and the second RO, and the at least two uplink carriers include the first uplink carrier and the second uplink carrier; or, a first RO corresponding to the first SSB is on a first uplink BWP, and a second RO corresponding to the first SSB is on a second uplink BWP, where the RO corresponding to the first SSB includes the first RO and the second RO, and the at least two uplink BWPs include the first uplink BWP and the second uplink BWP.

[0473] Optionally, a time domain location of the first RO is the same as a time domain location of the second RO.

[0474] Optionally, the transceiver 2510 is further configured to send fourth configuration information to the first communication device, the fourth configuration information being used to indicate a carrier power offset corresponding to at least one of the at least two uplink carriers, the carrier power offset being used to determine a transmission power of the RACH on the at least one uplink carrier; or send fifth configuration information to the first communication device, the fifth configuration information being used to indicate a BWP power offset corresponding to at least one of the at least two uplink BWPs, the BWP power offset being used to determine a transmission power of the RACH on the at least one uplink BWP.

[0475] Optionally, the carrier power offsets corresponding to the first uplink carrier and the second uplink carrier of the at least two uplink carriers are different, or the BWP power offsets corresponding to the first uplink BWP and the second uplink BWP of the at least two uplink BWPs are different.

[0476] FIG. 26 is a schematic block diagram of another communication device 2600 provided by the embodiments of the present application. The communication device 2600 can be the first communication device or the second communication device. The communication device 2600 includes a processor 2610, which is configured to implement the method of random access provided by the embodiments of the present application by means of logic circuit or code instruction execution. Optionally, the communication device 2600 can further include an interface circuit 2620. The processor 2610 and the interface circuit 2620 are coupled with each other. It can be understood that the interface circuit 2620 can be a transceiver or an input / output interface.

[0477] Optionally, the communication device 2600 can further include a memory 2630, which is configured to store instructions executed by the processor 2610 or store input data required by the processor 2610 to run instructions or store data generated by the processor 2610 after running instructions.

[0478] The processor 2610 described above can be an integrated circuit chip with a signal processing capability. In the implementation process, each step of the method embodiment described above can be completed by the integrated logic circuit of hardware in the processor or the instruction in the form of software. The processor described above can be a general processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The disclosed methods, steps and logic block diagrams in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as a hardware code processor for execution, or a combination of hardware and software modules in the code processor for execution. The software module can be located in a random access memory, a flash memory, a read only memory, a programmable read only memory or an electrically erasable programmable memory, a register, and other mature storage media in the art. The storage medium is located in the storage, and the processor reads the information in the storage, and combines the hardware to complete the steps of the above method.

[0479] The embodiments of the present application also provide a communication system, which comprises the first communication device in the method for random access provided by the embodiments of the present application, and other communication devices in communication with the first communication device, a second communication device and other communication devices in communication with the second communication device.

[0480] The embodiments of the present application also provide a computer readable storage medium, which stores a computer program for implementing the method in the method embodiments described above. When the computer program runs on the computer, the computer can implement the method in the method embodiments described above.

[0481] The embodiments of the present application also provide a computer program product, which comprises a computer program. When the computer program runs on the computer, the method in the method embodiments described above is executed.

[0482] The embodiments of the present application also provide a chip, which comprises a processor, and the processor is connected with a memory, the memory is used for storing a computer program, and the processor is used for executing the computer program stored in the memory, so that the chip executes the method in the method embodiments described above.

[0483] It should be understood that in the embodiments of the present application, for a technical feature, the technical features in the technical feature are distinguished by "first", "second", "third" and the like, and there is no order or size order between the technical features described by "first", "second" and "third".

[0484] In addition, 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 represent the following three cases: A exists alone, A and B exist together, and B exists alone. In addition, the character " / " in this paper generally represents that the front and rear associated objects are an "or" relationship; the term "at least one" in the present application can represent "one" and "two or more", for example, A, B and C can represent the following seven cases: A exists alone, B exists alone, C exists alone, A and B exist together, A and C exist together, C and B exist together, and A, B and C exist together.

[0485] "Sending" and "receiving" in the embodiments of the present application represent the direction of signal transmission. For example, "sending information to XX" can be understood as that the destination of the information is XX, which can include direct sending through the air interface, and also includes indirect sending through the air interface by other units or modules. "Receiving information from YY" can be understood as that the source of the information is YY, which can include direct receiving from YY through the air interface, and also can include indirect receiving from YY through the air interface from other units or modules. "Sending" can also be understood as "output" of a chip interface, and "receiving" can also be understood as "input" of a chip interface.

[0486] In other words, sending and receiving can be carried out between devices, for example, between network devices and terminal devices, or can be carried out within a device, for example, between components, modules, chips, software modules or hardware modules in the device through a bus, wire or interface.

[0487] It can be understood that the information between the source and the destination of the information transmission can be processed as necessary, such as encoding, modulation, etc., but the destination can understand the valid information from the source. Similar expressions in the present application can be similarly understood, and will not be repeated here.

[0488] In the embodiments of the present application, the indication can include direct indication and indirect indication, and can also include explicit indication and implicit indication. The information indicated by certain information (indication information described below) is referred to as to-be-indicated information. In the implementation process, there are many ways to indicate the to-be-indicated information, for example, but not limited to, the to-be-indicated information can be directly indicated, such as the to-be-indicated information itself or an index of the to-be-indicated information. The to-be-indicated information can also be indirectly indicated by indicating other information, where the other information and the to-be-indicated information have an association relationship. The to-be-indicated information can also be indicated only by a part of the to-be-indicated information, and the other part of the to-be-indicated information is known or agreed in advance. For example, the indication of a specific information can be achieved by means of the arrangement order of each information agreed in advance (for example, protocol predefined), thereby reducing the indication overhead to a certain extent. The specific manner of indication is not limited in the present application. It can be understood that the indication information can be used to indicate the to-be-indicated information for the sender of the indication information, and the indication information can be used to determine the to-be-indicated information for the receiver of the indication information.

[0489] In the present application, the same or similar parts between various embodiments can be mutually referred to, unless otherwise specified. In the various embodiments of the present application, and the various implementation manners / implementation methods / implementation approaches in each embodiment, the terms and / or descriptions between different embodiments, and between various implementation manners / implementation methods / implementation approaches in each embodiment are consistent and can be mutually referred to, if not specially specified and there is no logical conflict. The technical features in different embodiments, and in various implementation manners / implementation methods / implementation approaches in each embodiment can be combined to form new embodiments, implementation manners, implementation methods, or implementation approaches according to their inherent logical relationship. The implementation manners of the present application described below do not constitute a limitation on the protection scope of the present application.

[0490] Those skilled in the art can clearly understand that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be realized by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0491] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described system, device and unit can refer to the corresponding processes in the foregoing method embodiments, which will not be described here.

[0492] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other manners. For example, the described device embodiments are merely schematic. The division of the units is merely logical function division. There can be other division manners 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.

[0493] 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 purpose of the embodiment.

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

[0495] If the functions are realized in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application can be embodied in the form of a software product, and the computer software product is stored in a storage medium, and includes a number of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various program code storage media.

[0496] The above is merely specific embodiments 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 scope 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 random access, characterized by, Comprising: receiving a first synchronization signal block (SSB) on a first downlink carrier, the first downlink carrier being used to carry at least one SSB, the at least one SSB including the first SSB, random access channel opportunities (ROs) corresponding to the at least one SSB being on at least two uplink carriers or on at least two uplink bandwidth parts (BWPs); transmitting a random access channel (RACH) preamble sequence on a first RO corresponding to the first SSB.

2. The method of claim 1, wherein, Further comprising: receiving first configuration information indicating that the first downlink carrier is associated with the at least two uplink carriers or the at least two uplink BWPs.

3. The method according to claim 1 or 2, characterized in that, Further comprising: receiving second configuration information indicating ROs corresponding to the at least one SSB, or third configuration information indicating ROs corresponding to the at least one SSB.

4. The method of claim 3, wherein, Further comprising: determining the ROs corresponding to the first SSB according to the second configuration information.

5. The method of claim 3, wherein, Further comprising: determining the ROs corresponding to the first SSB according to the third configuration information and a predefined rule.

6. The method of any one of claims 1-5, wherein: the at least one SSB includes the first SSB and a second SSB, the at least two uplink carriers include a first uplink carrier and a second uplink carrier, the ROs corresponding to the first SSB are on the first uplink carrier, and the ROs corresponding to the second SSB are on the second uplink carrier; or the at least two uplink BWPs include a first uplink BWP and a second uplink BWP, the ROs corresponding to the first SSB are on the first uplink BWP, and the ROs corresponding to the second SSB are on the second uplink BWP.

7. The method of claim 6, wherein: time domain locations of the ROs corresponding to the first SSB are the same as time domain locations of the ROs corresponding to the second SSB.

8. The method of any one of claims 1-5, wherein: a first RO corresponding to the first SSB is on a first uplink carrier, a second RO corresponding to the first SSB is on a second uplink carrier, the ROs corresponding to the first SSB include the first RO and the second RO, and the at least two uplink carriers include the first uplink carrier and the second uplink carrier; or a first RO corresponding to the first SSB is on a first uplink BWP, a second RO corresponding to the first SSB is on a second uplink BWP, the ROs corresponding to the first SSB include the first RO and the second RO, and the at least two uplink BWPs include the first uplink BWP and the second uplink BWP.

9. The method of claim 8, wherein: a time domain location of the first RO is the same as a time domain location of the second RO. Further comprising:

10. The method according to any one of claims 1 to 9, characterized in that, ​ receiving fourth configuration information, the fourth configuration information being used to indicate a carrier power offset corresponding to at least one of the at least two uplink carriers, the carrier power offset being used to determine a transmission power of the RACH on the at least one uplink carrier; or, receiving fifth configuration information, the fifth configuration information being used to indicate a BWP power offset corresponding to at least one of the at least two uplink BWPs, the BWP power offset being used to determine a transmission power of the RACH on the at least one uplink BWP.

11. The method of claim 10, wherein: the carrier power offset corresponding to a first uplink carrier and a second uplink carrier of the at least two uplink carriers is different, or the BWP power offset corresponding to a first uplink BWP and a second uplink BWP of the at least two uplink BWPs is different.

12. A method of random access, characterized by, including: transmitting a first SSB on a first downlink carrier, the first downlink carrier being used to carry at least one SSB, the at least one SSB including the first SSB, the at least one SSB corresponding to a RO on at least two uplink carriers or on at least two uplink BWPs; receiving a RACH preamble sequence on a first RO corresponding to the first SSB.

13. The method of claim 12, wherein, further including: transmitting first configuration information, the first configuration information being used to indicate that the first downlink carrier is associated with the at least two uplink carriers or the at least two uplink BWPs.

14. The method according to claim 12 or 13, characterized in that, further including: transmitting second configuration information or third configuration information, the second configuration information being used to indicate a RO corresponding to the first SSB, the RO corresponding to the first SSB including the first RO, the third configuration information being used to indicate a RO corresponding to the at least one SSB.

15. The method of any one of claims 12 to 14, wherein: the at least one SSB includes a first SSB and a second SSB, the at least two uplink carriers include a first uplink carrier and a second uplink carrier, a RO corresponding to the first SSB being on the first uplink carrier, a RO corresponding to the second SSB being on the second uplink carrier; or the at least two uplink BWPs include a first uplink BWP and a second uplink BWP, a RO corresponding to the first SSB being on the first uplink BWP, a RO corresponding to the second SSB being on the second uplink BWP.

16. The method of claim 15, wherein: a time domain location of the RO corresponding to the first SSB is the same as a time domain location of the RO corresponding to the second SSB.

17. The method of any one of claims 12 to 14, wherein: a first RO corresponding to the first SSB is on a first uplink carrier, a second RO corresponding to the first SSB is on a second uplink carrier, wherein the RO corresponding to the first SSB includes the first RO and the second RO, the at least two uplink carriers include the first uplink carrier and the second uplink carrier; or ​ The first RO corresponding to the first SSB is on a first uplink BWP, and a second RO corresponding to the first SSB is on a second uplink BWP, wherein the ROs corresponding to the first SSB include the first RO and the second RO, and the at least two uplink BWPs include the first uplink BWP and the second uplink BWP.

18. The method of claim 17, wherein, a time domain location of the first RO is the same as a time domain location of the second RO.

19. The method according to any one of claims 12 to 18, characterized in that, Further comprising: sending fourth configuration information, the fourth configuration information being used to indicate a carrier power offset corresponding to at least one of the at least two uplink carriers, the carrier power offset being used to determine a transmission power of a RACH on the at least one uplink carrier; or, sending fifth configuration information, the fifth configuration information being used to indicate a BWP power offset corresponding to at least one of the at least two uplink BWPs, the BWP power offset being used to determine a transmission power of a RACH on the at least one uplink BWP.

20. The method of claim 19, wherein, a carrier power offset corresponding to a first uplink carrier and a second uplink carrier of the at least two uplink carriers is different, or a BWP power offset corresponding to a first uplink BWP and a second uplink BWP of the at least two uplink BWPs is different.

21. A communications device, characterized by A module for performing the method of any one of claims 1-11.

22. A communications device, characterized by A module for performing the method of any one of claims 12-20.

23. A communications device, characterized by A processor configured to implement a method recited in any one of claims 1-11.

24. A communications device, characterized by A processor configured to implement a method recited in any one of claims 12-20.

25. A computer-readable storage medium, characterized in that, Further comprising: The computer readable medium stores a computer program; The computer program, when executed by the processor, causes the method recited in any one of claims 1-20 to be performed.

26. A computer program product, characterised in that, A computer program that, when executed, causes the method recited in any one of claims 1-20 to be performed.

Images