Communication method and communication apparatus

Abstract

The present application provides a communication method and a communication apparatus. The communication method comprises: on the basis of a mapping relationship between a synchronization signal and PBCH block (SSB) and a PRACH occasion (RO), sending a random access request message. The mapping relationship between the SSB and the RO comprises a mapping relationship between the SSB and a first type RO and / or a mapping relationship between the SSB and a second type RO; the time unit occupied by the first type RO in the time domain is an SBFD time unit, and the frequency domain resource occupied by the first type RO in the frequency domain is an uplink subband corresponding to the SBFD time unit; and the time unit occupied by the second type RO in the time domain is a non-SBFD time unit, and the frequency domain resource occupied by the second type RO in the frequency domain is a frequency domain resource corresponding to the non-SBFD time unit and used for uplink transmission. By means of the present application, a mapping relationship between an SSB and an RO after the introduction of SBFD is provided, thereby supporting the transmission of a random access request message in an SBFD system.

Description

Communication method and communication device

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on February 6, 2024, with application number 202410172100.6 and application name “Communication Method and Communication Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a communication method and a communication device. Background Art

[0003] In traditional time division duplex (TDD) systems, uplink and downlink communications share the same frequency domain resources, but the time domain resources occupied by uplink and downlink communications are different. For example, for a base station, the base station sends downlink data in the downlink time slot and cannot receive uplink data in the downlink time slot. For another example, for a base station, the base station receives uplink data in the uplink time slot and cannot send downlink data in the uplink time slot. However, since the downlink time slot accounts for a large proportion in traditional TDD systems, uplink resources are insufficient, resulting in an increase in uplink service scheduling delay. Therefore, subband full duplex (SBFD) is introduced. Specifically, a new type of time slot is introduced in the TDD system, namely the SBFD time slot. For a base station, an uplink subband and a downlink subband can be configured in the SBFD time slot. Therefore, in the SBFD time slot, the base station can receive uplink data through the uplink subband and send downlink data through the downlink subband. However, after the introduction of the SBFD time slot, the traditional mapping relationship between the synchronization signal block (Synchronization Signal and PBCH block, SSB) used to send the random access request message and the physical random access channel occasion (PRACH occasion, RO) is no longer applicable. Summary of the Invention

[0004] The embodiments of the present application provide a communication method and a communication device, which provide a mapping relationship between SSB and RO after the introduction of SBFD, thereby supporting the transmission of random access request messages in the SBFD system.

[0005] In a first aspect, an embodiment of the present application provides a communication method, the method comprising:

[0006] Send a random access request message according to the mapping relationship between the synchronization signal block SSB and the random access opportunity RO;

[0007] The mapping relationship between the SSB and the RO includes a mapping relationship between the SSB and the first type RO and / or a mapping relationship between the SSB and the second type RO; the time unit occupied by the first type RO in the time domain is an SBFD time unit, and the time unit occupied by the second type RO in the time domain is a non-SBFD time unit.

[0008] The method of implementing the first aspect includes, after the introduction of SBFD, two types of ROs in the mapping relationship between SSB and RO, namely, the first type of RO that occupies the SBFD time unit in the time domain, and the second type of RO that occupies the non-SBFD time unit in the time domain. The mapping relationship between SSB and RO after the introduction of SBFD includes a mapping relationship between two types of RO and SSB, thereby supporting the transmission of random access request messages in the SBFD system.

[0009] In one possible implementation, the frequency domain resources occupied by the first type RO in the frequency domain are the uplink subband corresponding to the SBFD time unit, and the frequency domain resources occupied by the second type RO in the frequency domain are the frequency domain resources corresponding to the non-SBFD time unit, and the frequency domain resources corresponding to the non-SBFD time unit are used for uplink transmission.

[0010] By implementing this approach, the frequency domain resources occupied by the two types of ROs are further limited, thereby facilitating accurate determination of the frequency domain resource locations of the two types of ROs.

[0011] In a possible implementation, at least one RO group for PRACH transmission of preamble code repetition in the mapping relationship between SSB and RO includes a first RO group, and the ROs in the first RO group include the first type RO and the second type RO.

[0012] By implementing this method, when performing RO grouping, the same RO group may include two types of ROs, that is, the types of ROs may not be distinguished when performing RO grouping, thereby improving the efficiency of RO grouping and thus increasing the preamble code repetition transmission density.

[0013] In a possible implementation, the at least one RO group for PRACH transmission of preamble repetition in the mapping relationship between the SSB and the RO includes the second RO group and / or the third RO group;

[0014] The ROs in the second RO group are the first type ROs, and the ROs in the third RO group are the second type ROs; or,

[0015] The ROs in the second RO group are of the second type, and the ROs in the third RO group are of the first type.

[0016] By implementing this approach, ROs in the same RO group are of the same type, thereby facilitating scheduling of the same type of ROs to repeatedly transmit preambles.

[0017] In a possible implementation, the at least one RO group for PRACH transmission of preamble repetition in the mapping relationship between the SSB and the RO further includes a fourth RO group; the ROs in the fourth RO group and the ROs in the second RO group are located in the same time period;

[0018] The types of the ROs in the fourth RO group are the same as those in the second RO group, the SSBs mapped to the ROs in the fourth RO group are the same as those in the second RO group, and the frequency domain resource indexes of the ROs in the fourth RO group and the ROs in the second RO group are the same;

[0019] The first RO in the fourth RO group is an RO determined by shifting the first RO in the second RO group backward by X ROs in the time domain. SSBs mapped to the X ROs are the same as SSBs mapped to the ROs in the second RO group. Frequency domain resource indexes of the X ROs are the same as frequency domain resource indexes of the ROs in the second RO group. Types of the X ROs are the same as types of the ROs in the second RO group.

[0020] By implementing this method, the RO grouping density of two adjacent ROs of the same type used to map the same SSB can be controlled by the offset X.

[0021] In one possible implementation, the mapping relationship between the SSB and the RO includes an RO group corresponding to each number of repetitions of each SSB within a time period for PRACH transmission of the preamble code repetition, the RO group includes the first type RO and / or the second type RO, the SSB is the SSB configured by the network, and the number of repetitions is the number of repetitions of the preamble code configured by the network.

[0022] By implementing this method, after the introduction of SBFD, the RO group corresponding to each repetition number of each SSB can be determined within the time period without distinguishing whether the RO group includes ROs of the same type, which facilitates the determination of the time period and reduces the modification of the definition of the time period in the existing standard protocol.

[0023] In one possible implementation, the time period of PRACH transmission for preamble code repetition in the mapping relationship between SSB and RO includes: a first type RO group corresponding to each repetition number of each SSB, and / or a second type RO group corresponding to each repetition number of each SSB, the RO in the first type RO group is the first type RO, the RO in the second type RO group is the second type RO, the SSB is the SSB configured by the network device, and the repetition number is the repetition number of the preamble code configured by the network.

[0024] To implement this method, after the introduction of SBFD, a first type RO group corresponding to each repetition number of each SSB and a second type RO group corresponding to each repetition number of each SSB need to be included in the time period, that is, two different RO groups can be found for each SSB and each repetition number, thereby increasing the possibility of scheduling the transmission of random access request messages.

[0025] In a possible implementation, within an association period in the mapping relationship between the SSB and the RO, N SSBs are mapped to the RO M times, and the RO used to map the N SSBs includes the first type RO and / or the second type RO, and N and M are positive integers.

[0026] In this manner, ROs used for mapping the SSB within an association period may include first-type ROs or second-type ROs, providing an association period in the SBFD system.

[0027] In a possible implementation, the RO used to map the N SSBs includes the first type RO and the second type RO, including:

[0028] The N SSBs are mapped to the first type RO R times, and the N SSBs are mapped to the second type RO MR times, where R is a positive integer and the value of MR is a positive integer.

[0029] By implementing this method, N SSBs need to be mapped to the first type RO for at least one round in one association cycle, and N SSBs need to be mapped to the second type RO for at least one round, so that various types of ROs mapped to various SSBs can be found in one association cycle.

[0030] In a second aspect, an embodiment of the present application provides a communication method, the method comprising:

[0031] receiving a random access request message according to a mapping relationship between a synchronization signal block SSB and a random access opportunity RO;

[0032] The mapping relationship between the SSB and the RO includes a mapping relationship between the first type RO and the SSB and / or a mapping relationship between the second type RO and the SSB; the time unit occupied by the first type RO in the time domain is an SBFD time unit, and the time unit occupied by the second type RO in the time domain is a non-SBFD time unit.

[0033] In a possible implementation, the frequency domain resources occupied by the first type RO in the frequency domain are the uplink subband corresponding to the SBFD time unit, and the frequency domain resources occupied by the second type RO in the frequency domain are the frequency domain resources corresponding to the non-SBFD time unit, and the frequency domain resources corresponding to the non-SBFD time unit are used for uplink transmission.

[0034] In a possible implementation, at least one RO group for PRACH transmission of preamble code repetition in the mapping relationship between SSB and RO includes a first RO group, and the ROs in the first RO group include the first type RO and the second type RO.

[0035] In a possible implementation manner, at least one RO group for PRACH transmission of preamble code repetition in the mapping relationship between SSB and RO includes the second RO group and / or the third RO group;

[0036] The ROs in the second RO group are the first type ROs, and the ROs in the third RO group are the second type ROs; or,

[0037] The ROs in the second RO group are of the second type, and the ROs in the third RO group are of the first type.

[0038] In a possible implementation, the at least one RO group for PRACH transmission with preamble repetition in the mapping relationship between the SSB and the RO further includes a fourth RO group; the ROs in the fourth RO group and the ROs in the second RO group are located in the same time period;

[0039] The types of the ROs in the fourth RO group are the same as those in the second RO group, the SSBs mapped to the ROs in the fourth RO group are the same as those in the second RO group, and the frequency domain resource indexes of the ROs in the fourth RO group and the ROs in the second RO group are the same;

[0040] The first RO in the fourth RO group is an RO determined by shifting the first RO in the second RO group backward by X ROs in the time domain. SSBs mapped to the X ROs are the same as SSBs mapped to the ROs in the second RO group. Frequency domain resource indexes of the X ROs are the same as frequency domain resource indexes of the ROs in the second RO group. Types of the X ROs are the same as types of the ROs in the second RO group.

[0041] In one possible implementation, the time period of PRACH transmission for preamble code repetition in the mapping relationship between SSB and RO includes an RO group corresponding to each repetition number of each SSB, the RO group includes the first type RO and / or the second type RO, the SSB is the SSB configured by the network, and the repetition number is the repetition number of the preamble code configured by the network.

[0042] In one possible implementation, the time period of PRACH transmission for preamble code repetition in the mapping relationship between SSB and RO includes: a first type RO group corresponding to each repetition number of each SSB, and / or a second type RO group corresponding to each repetition number of each SSB, the RO in the first type RO group is the first type RO, the RO in the second type RO group is the second type RO, the SSB is the SSB configured by the network device, and the repetition number is the repetition number of the preamble code configured by the network.

[0043] In a possible implementation, within an association period in the mapping relationship between the SSB and the RO, N SSBs are mapped to the RO M times, and the RO used to map the N SSBs includes the first type RO and / or the second type RO, and N and M are positive integers.

[0044] In a possible implementation, the RO used to map the N SSBs includes the first-type RO and the second-type RO, including:

[0045] The N SSBs are mapped to the first type RO R times, and the N SSBs are mapped to the second type RO MR times, where R is a positive integer and the value of MR is a positive integer.

[0046] In a third aspect, an embodiment of the present application provides a communication method, the method comprising:

[0047] Send a random access request message according to the mapping relationship between the random access opportunity RO and the synchronization signal block SSB;

[0048] The mapping relationship between the RO and the SSB includes a mapping relationship between a first type RO and the SSB and / or a mapping relationship between a second type RO and the SSB.

[0049] In one possible implementation, the time unit occupied by the first type RO in the time domain is an SBFD time unit, and the frequency domain resources occupied by the first type RO in the frequency domain are the uplink subband corresponding to the SBFD time unit. The time unit occupied by the second type RO in the time domain is a non-SBFD time unit, and the frequency domain resources occupied by the second type RO in the frequency domain are the frequency domain resources corresponding to the non-SBFD time unit. The frequency domain resources corresponding to the non-SBFD time unit are used for uplink transmission.

[0050] For other possible implementations of the third aspect, reference may be made to the various possible implementations of the first aspect, which will not be repeated here.

[0051] In a fourth aspect, an embodiment of the present application provides a communication method, the method comprising:

[0052] receiving a random access request message according to a mapping relationship between a random access opportunity RO and a synchronization signal block SSB;

[0053] The mapping relationship between the RO and the SSB includes a mapping relationship between a first type RO and the SSB and / or a mapping relationship between a second type RO and the SSB.

[0054] In one possible implementation, the time unit occupied by the first type RO in the time domain is an SBFD time unit, and the frequency domain resources occupied by the first type RO in the frequency domain are the uplink subband corresponding to the SBFD time unit. The time unit occupied by the second type RO in the time domain is a non-SBFD time unit, and the frequency domain resources occupied by the second type RO in the frequency domain are the frequency domain resources corresponding to the non-SBFD time unit. The frequency domain resources corresponding to the non-SBFD time unit are used for uplink transmission.

[0055] For other possible implementations of the fourth aspect, reference may be made to the various possible implementations of the second aspect, which will not be repeated here.

[0056] In a fifth aspect, an embodiment of the present application provides a communication device, the communication device comprising:

[0057] A sending unit, configured to send a random access request message according to a mapping relationship between a synchronization signal block SSB and a random access opportunity RO;

[0058] The mapping relationship between the SSB and the RO includes a mapping relationship between the first type RO and the SSB and / or a mapping relationship between the second type RO and the SSB; the time unit occupied by the first type RO in the time domain is an SBFD time unit, and the time unit occupied by the second type RO in the time domain is a non-SBFD time unit.

[0059] In a sixth aspect, an embodiment of the present application provides a communication device, the communication device comprising:

[0060] A receiving unit, configured to receive a random access request message according to a mapping relationship between a synchronization signal block SSB and a random access opportunity RO;

[0061] The mapping relationship between the SSB and the RO includes a mapping relationship between the first type RO and the SSB and / or a mapping relationship between the second type RO and the SSB; the time unit occupied by the first type RO in the time domain is an SBFD time unit, and the time unit occupied by the second type RO in the time domain is a non-SBFD time unit.

[0062] In the seventh aspect, an embodiment of the present application provides a communication device, which includes a processor and a memory, the processor and the memory are connected to each other, the memory is used to store a computer program, and the processor is configured to execute the computer program to execute the method as described in the first aspect or any optional embodiment of the first aspect, or to execute the method as described in the second aspect or any optional embodiment of the second aspect, or to implement the method as described in the third aspect or any optional embodiment of the third aspect, or to implement the method as described in the fourth aspect or any optional embodiment of the fourth aspect.

[0063] In an eighth aspect, an embodiment of the present application provides a chip, comprising a processor and an interface, wherein the processor and the interface are coupled; the interface is used to receive and / or output signals, and the processor is used to execute code instructions to execute the method as described in the first aspect or any optional embodiment of the first aspect, or to execute the method as described in the second aspect or any optional embodiment of the second aspect, or to execute the method as described in the third aspect or any optional embodiment of the third aspect, or to execute the method as described in the fourth aspect or any optional embodiment of the fourth aspect.

[0064] In the ninth aspect, an embodiment of the present application provides a module device, which includes a communication module, a power module, a storage module and a chip module, wherein: the power module is used to provide power to the module device; the storage module is used to store data and / or instructions; the communication module communicates with an external device; the chip module is used to call the data and / or instructions stored in the storage module, and execute the method as described in the first aspect or any optional embodiment of the first aspect, or, execute the method as described in the second aspect or any optional embodiment of the second aspect, or, execute the method as described in the third aspect or any optional embodiment of the third aspect, or, execute the method as described in the fourth aspect or any optional embodiment of the fourth aspect.

[0065] In the tenth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program, and the computer program includes program instructions. When the computer executes the program instructions, it implements the method as described in the first aspect or any optional embodiment of the first aspect, or implements the method as described in the second aspect or any optional embodiment of the second aspect, or implements the method as described in the third aspect or any optional embodiment of the third aspect, or implements the method as described in the fourth aspect or any optional embodiment of the fourth aspect.

[0066] In the eleventh aspect, an embodiment of the present application provides a computer program product, which includes a computer program or computer code, which, when running on a computer, is used to implement the method described in the first aspect or any optional embodiment of the first aspect, or to implement the method described in the second aspect or any optional embodiment of the second aspect, or to implement the method described in the third aspect or any optional embodiment of the third aspect, or to implement the method described in the fourth aspect or any optional embodiment of the fourth aspect.

[0067] In a twelfth aspect, an embodiment of the present application provides a communication system, which includes a terminal device and a network device.

[0068] The beneficial effects of the technical solutions provided in aspects 2 to 12 of the embodiments of this application can refer to the beneficial effects of the technical solution provided in aspect 1, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0069] FIG1 is a schematic structural diagram of a communication system provided in an embodiment of the present application;

[0070] FIG2 is a schematic diagram of a random access process provided in an embodiment of the present application;

[0071] FIG3 is a schematic diagram of an RO provided in an embodiment of the present application;

[0072] Figure 4a is a schematic diagram of a mapping relationship between SSB and RO provided in an embodiment of the present application

[0073] FIG4b is a schematic diagram of another mapping relationship between SSB and RO provided in an embodiment of the present application

[0074] FIG5 is a schematic diagram of resources after the introduction of SBFD according to an embodiment of the present application;

[0075] FIG6 is a schematic diagram of a first type RO and a second type RO provided in an embodiment of the present application;

[0076] FIG7 is a flow chart of a communication method provided in an embodiment of the present application;

[0077] Figures 8a to 8d are schematic diagrams of RO grouping scenarios provided by embodiments of the present application;

[0078] FIG8e is a schematic diagram of a time offset provided in an embodiment of the present application;

[0079] 9a to 9c are schematic diagrams of association periods and association mode periods provided in embodiments of the present application;

[0080] Figures 10a to 10b are schematic diagrams of time periods provided in embodiments of the present application;

[0081] FIG11 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0082] FIG12 is a schematic structural diagram of another communication device provided in an embodiment of the present application;

[0083] FIG13 is a schematic structural diagram of another communication device provided in an embodiment of the present application;

[0084] FIG14 is a schematic structural diagram of a module device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0085] In the embodiments of this application, unless otherwise specified, the character " / " indicates that the associated objects are in an "or" relationship. For example, A / B can represent A or B. "And / or" describes the relationship between the associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exists simultaneously, or B exists alone.

[0086] It should be pointed out that the words "first", "second", etc. involved in the embodiments of this application are only used for distinguishing description purposes, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated, nor can they be understood as indicating or implying order.

[0087] In the embodiments of the present application, "at least one" refers to one or more, and "plurality" refers to two or more. In addition, "at least one of the following" or similar expressions refers to any combination of these items, which may include any combination of single items or plural items. For example, at least one of A, B, or C can represent: A, B, C, A and B, A and C, B and C, or A, B and C. Among them, each of A, B, and C can be an element itself, or a set containing one or more elements.

[0088] In the embodiments of this application, the terms "exemplary," "in some embodiments," and "in another embodiment" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" in this application should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of the word "exemplary" is intended to present concepts in a concrete manner.

[0089] In the embodiments of this application, the terms "of," "corresponding," and "relevant" may sometimes be used interchangeably. It should be noted that, when the distinction between them is not emphasized, the meanings they convey are the same. In the embodiments of this application, the terms "communication" and "transmission" may sometimes be used interchangeably. It should be noted that, when the distinction between them is not emphasized, the meanings they convey are the same. For example, "transmission" may include "sending" and / or "receiving," and may be either a noun or a verb.

[0090] In the embodiments of the present application, "equal to" can be used in conjunction with "greater than" or "less than", but not with both "greater than" and "less than". It should be noted that when "equal to" is used in conjunction with "greater than", the technical solution adopted by "greater than" is applicable; when "equal to" is used in conjunction with "less than", the technical solution adopted by "less than" is applicable.

[0091] Please refer to Figure 1, which is a schematic diagram of the structure of a communication system provided in an embodiment of the present application. The communication system may include, but is not limited to, one or more network devices and one or more terminal devices. For example, Figure 1 takes a network device and a terminal device as an example, wherein the network device in Figure 1 is a base station as an example, and the terminal device is a mobile phone as an example, and the terminal device can establish a wireless link with the network device for communication. The communication system shown in Figure 1 includes, but is not limited to, network devices and terminal devices, and may also include other communication devices. The number and form of the devices shown in Figure 1 are for example only and do not constitute a limitation on the embodiments of the present application.

[0092] In the embodiments of the present application, a terminal device is a device with wireless transceiver functions, which can be referred to as a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, vehicle-mounted terminal, industrial control terminal, UE unit, UE station, mobile station, remote station, remote terminal, mobile device, wireless communication device, UE agent or UE device, etc. The terminal device can be fixed or mobile. It should be noted that the terminal device can support at least one wireless communication technology, such as long term evolution (LTE), new radio (NR), etc. For example, the terminal device can be a mobile phone, a tablet computer, a desktop computer, a laptop computer, an all-in-one computer, an in-vehicle terminal, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a cellular phone, 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 computing device or other processing device connected to a wireless modem, a wearable device, a terminal in a future mobile communication network, or a terminal in a future evolved public mobile land network (PLMN), etc. In some embodiments of the present application, the terminal may also be a device with transceiver functions, such as a chip system, wherein the chip system may include a chip and may also include other discrete devices.

[0093] In the embodiment of the present application, a network device is a device that provides wireless communication functions for a terminal device, and may also be referred to as an access network device, a radio access network (RAN) device, etc. The network device may support at least one wireless communication technology, such as LTE, NR, etc. For example, the network device includes, but is not limited to: a next-generation base station (gNB) in a fifth-generation mobile communication system (5G), a base station in a sixth-generation mobile communication system (6G), an evolved node B (eNB), a radio network controller (RNC), a node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., home evolved node B, or home node B, HNB), a baseband unit (BBU), a transmitting and receiving point (TRP), a transmitting point (TP), a mobile switching center, etc. The network device may also be a wireless controller, a centralized unit (CU), and / or a distributed unit (DU) in a cloud radio access network (CRAN) scenario, or the network device may be a relay station, an access point, an on-board device, a terminal device, a wearable device, a network device in future mobile communications, or a network device in a future evolved PLMN. In some embodiments, the network device may also be a device that provides wireless communication functions for a terminal device, such as a chip system. For example, the chip system may include a chip and may also include other discrete devices.

[0094] Before introducing the specific solutions of the embodiments of the present application, the technical background involved in the embodiments of the present application is first introduced:

[0095] 1. Random Access preamble (RA preamble)

[0096] A random access preamble is a sequence sent by a terminal device to request network access. It includes, but is not limited to, a gold sequence, an m-sequence, and a ZC (Zadoff-Chu) sequence. The random access preamble is often referred to as a preamble. The terminal device transmits the RA preamble during a random access opportunity (PRACH occasion, RO). The RA preamble is carried (or transmitted) by the RO.

[0097] 2. Random access process

[0098] Random access refers to the process by which a terminal device sends a preamble to a network device, establishes a wireless link with the network device, and acquires or restores uplink synchronization. Random access is a key step in mobile communication systems, enabling the terminal device and network device to establish a communication connection. This allows the terminal device to exchange information with the network device and also achieve uplink synchronization.

[0099] As shown in FIG2 , the entire random access process includes four steps: transmission of Msg1, transmission of message 2 (Msg2), transmission of message 3 (Msg3), and transmission of message 4 (Msg4).

[0100] The transmission of Msg1, that is, the terminal device sends a physical random access channel (PRACH) to the network device. Msg1 can also be called a random access request message.

[0101] Specifically, Msg1 includes a preamble, which is used to request access from the network device, enabling the network device to estimate the transmission delay between the network device and the terminal device based on the preamble and calibrate the uplink timing, and then indicate this to the terminal device through Msg2.

[0102] The transmission of Msg2, that is, the network device transmits a Random Access Response (RAR) to the terminal device. The network device receives Msg1 and sends Msg2 to the terminal device.

[0103] Specifically, the network device sends Msg2 to the terminal device on the physical downlink shared channel (PDSCH) payload.

[0104] Msg2 may include the time adjustment amount required for specifying uplink synchronization, the uplink resources required for the terminal device to send Msg3, the temporary cell-radio network temporary identifier (TC-RNTI), etc.

[0105] The first two steps of the random access process, Msg1 and Msg2, mainly complete the uplink time synchronization, while the main purpose of Msg3 and Msg4 is to assign a unique and legal identity to the terminal device for subsequent data transmission.

[0106] Regarding the transmission of Msg3, the terminal device receives Msg2 and sends Msg3 to the network device. For example, the terminal device sends Msg3 to the network device on the Physical Uplink Share Channel (PUSCH). Furthermore, in some embodiments, Msg3 includes a unique identifier of the terminal device.

[0107] Transmission of Msg4: The network device receives Msg3 and sends Msg4 to the terminal device.

[0108] In the conflict resolution mechanism, the network device carries the flag for uniquely identifying the terminal device in Msg4 to indicate the winning terminal device, and the terminal device that does not win in the conflict resolution will re-initiate random access.

[0109] 3. Number of preamble repetitions

[0110] In PRACH transmissions with preamble repetitions, the preamble repetition count indicates the number of times the preamble is transmitted multiple times (or repeatedly) during a random access procedure. For example, a preamble repetition count of 4 indicates four repetitions of the preamble. The preamble repetition count is configured by the base station and can be set to {2, 4, 8}.

[0111] It should be noted that the number of preamble repetitions can also be called PRACH repetitions, random access request repetitions, PRACH repetitions, PRACH transmissions, etc. In the four-step random access process, the number of preamble repetitions can also be called Msg1 repetitions or Msg1 repetitions.

[0112] When the terminal device repeatedly transmits the preamble code Y times, the terminal device can support sending the preamble code once on Y ROs with different time domain positions in one random access attempt.

[0113] 4. RO / RO group

[0114] RO refers to the time-frequency resources used for preamble / PRACH / random access request message transmission. RO can include time domain resources and frequency domain resources. Specifically, time domain resources can be indicated by a time domain resource index, and frequency domain resources can be indicated by a frequency domain resource index. For the time domain resources corresponding to a time domain resource index, the number of ROs in the frequency domain can be {1, 2, 4, 8}, configured by the high-level parameter "msg1-FDM".

[0115] For example, Figure 3 is a schematic diagram of RO, where the horizontal axis is time domain resources and the vertical axis is frequency domain resources. ROjk refers to RO with a time domain resource index of j (j is an integer greater than or equal to 0) and a frequency domain resource index of k (k is an integer greater than or equal to 0).

[0116] The PRACH period, the number of ROs in the time domain within a PRACH period, and the number of ROs multiplexed in frequency (msg1-FDM) are all configured by the network equipment.

[0117] In PRACH transmission with preamble repetition, an RO group refers to a set of one or more ROs, the SSBs mapped within the ROs in an RO group are the same, the frequency domain resource indexes of the ROs in an RO group are the same, and the number of ROs with different time domain positions in an RO group is equal to the number of preamble repetitions.

[0118] 5. Mapping (association / correspondence) relationship between SSB and RO

[0119] The mapping rules between SSB and RO are as follows:

[0120] First, within a single RO, the order of the preamble index is ascending; second, the order of the frequency domain resource index of a frequency-division multiplexed RO is ascending; third, the order of the time domain resource index of a time-division multiplexed RO within a PRACH slot is ascending; and fourth, the order of the PRACH slot index is ascending. In other words, the SSB-RO mapping rule follows: 1. Increase the preamble index; 2. Increase the RO's frequency domain resource index; 3. Increase the RO's time domain resource index; 4. Increase the PRACH slot.

[0121] The mapping relationship between SSB and RO can be indicated by the high-level parameter "ssb-perRACH-Occasion (N)". For example, the value of N can be {1 / 8, 1 / 4, 1 / 2, 1, 2, 4, 8, 16}.

[0122] If N<1, it means that one SSB can be mapped to 1 / N ROs. For example, if N=1 / 4, one SSB is associated with 4 ROs; if N=1 / 8, one SSB is associated with 8 ROs.

[0123] If N=1, it means that 1 SSB is mapped to 1 RO;

[0124] If N>1, it means that N SSBs can be mapped into one RO.

[0125] The following takes the case where 8 SSBs are configured in a cell, the indexes of the 8 SSBs are 0 to 7, and the parameter msg1-FDM=4 as an example, and combines Figures 4a and 4b to illustrate the mapping relationship between SSBs and ROs.

[0126] For example, see Figure 4a, which is a schematic diagram of a mapping relationship between SSBs and ROs provided in an embodiment of the present application. As shown in Figure 4a, when N = 1 / 2 in SSB-perRACH-Occasion, Figure 4a includes eight SSBs, namely SSB0 to SSB7. Since N = 1 / 2, one SSB is associated with two ROs.

[0127] For another example, see Figure 4b, which is a schematic diagram of another SSB-RO mapping relationship provided in an embodiment of the present application. As shown in Figure 4b, when N = 2 in SSB-perRACH-Occasion, Figure 4b includes 8 SSBs, namely SSB0 to SSB7. Since N = 2, 2 SSBs can be mapped into 1 RO.

[0128] Optionally, after triggering the random access process, the terminal device can measure the reference signal receiving power (RSRP) of the SSB sent by the network device and determine the SSB that meets the RSRP condition. If there are multiple SSBs that meet the RSRP condition, one SSB is selected from them, and one or more ROs associated with the SSB are determined based on the mapping relationship between the SSB and the RO, and a random access request message is sent on the selected RO. In other words, the terminal device can determine the RO resource for transmitting the random access request message based on the mapping relationship between the SSB and the RO. In this way, after receiving the random access request message, the network device can identify the SSB selected by the terminal device, and thereby use the beam corresponding to the SSB selected by the terminal device to send a random access response.

[0129] The following explains some of the terms involved in the embodiments of the present application to facilitate understanding by those skilled in the art.

[0130] 1. Time unit

[0131] A time unit is a time-domain unit used for signal transmission and can be a radio frame, subframe, slot, mini-slot, or Orthogonal Frequency Division Multiplexing (OFDM) symbol. An OFDM symbol can also be simply called a symbol.

[0132] 2. SBFD time unit, non-SBFD time unit, uplink subband, and downlink subband

[0133] SBFD refers to configuring a frequency domain resource for uplink transmission in the frequency domain of a downlink time unit or a flexible time unit. In the embodiment of the present application, the downlink time unit or the flexible time unit is referred to as an SBFD time unit. As shown in (A) in Figure 5, there is a schematic diagram of the SBFD time unit. The frequency domain resources configured for the SBFD time unit include frequency domain resources for uplink transmission (marked with "U" in (A) in Figure 5) and frequency domain resources for downlink transmission (marked with "D" in (A) in Figure 5).

[0134] In the embodiment of the present application, an uplink time unit or flexible time unit that is not configured with frequency domain resources for downlink transmission in the frequency domain is referred to as a non-SBFD time unit, and all frequency domain resources configured for the non-SBFD time unit are frequency domain resources for uplink transmission.

[0135] As shown in Figure 5 (B), time unit 5 is a non-SBFD time unit, and the frequency domain resources configured for the non-SBFD time unit are all used for uplink transmission. As shown in Figure 5 (B), time units 2, 3, and 4 are all SBFD time units.

[0136] For example, taking a symbol as the time unit, an SBFD time unit can be referred to as an SBFD symbol, and a non-SBFD time unit can be referred to as a non-SBFD symbol. For example, taking a time slot as the time unit, an SBFD time unit can be referred to as an SBFD time slot, and a non-SBFD time unit can be referred to as a non-SBFD time slot.

[0137] In this embodiment of the present application, a segment of frequency domain resources configured for uplink transmission in an SBFD time unit is referred to as an uplink subband. A segment of frequency domain resources configured in the frequency domain of an SBFD time unit for downlink transmission is referred to as a downlink subband. One or more downlink subbands can be configured in an SBFD time unit. As shown in Figure 5 (A), there is one downlink subband, and as shown in Figure 5 (B), time units 2, 3, and 4, there are two downlink subbands. The names of the uplink and downlink subbands are not limited and may be other names.

[0138] In the embodiments of the present application, a guard band may be a frequency domain resource segment between adjacent uplink and downlink subbands to reduce transmission interference between the uplink and downlink subbands. For details, see the guard band identifiers shown in Figures 5(A) and 5(B). The guard band is not limited to a specific name and may be other names, such as guard band.

[0139] Using uplink and downlink subbands, the base station can simultaneously perform uplink and downlink transmissions within a single time unit, achieving full-duplex operation. Compared to TDD, SBFD offers increased uplink resources, improving uplink coverage. For terminal devices, the base station can configure resources in either the uplink or downlink subband, maintaining half-duplex operation for the terminal.

[0140] 3. Type 1 RO and Type 2 RO

[0141] In the embodiment of the present application, the time unit occupied by the first type RO in the time domain is the SBFD time unit, and the frequency domain resource occupied by the first type RO in the frequency domain is the uplink subband corresponding to the SBFD time unit. As shown in FIG6 , the RO located in the uplink subband is the first type RO, for example, the RO in FIG6 00 , RO 01 , RO 10 , RO 11 , RO 20 , RO 21 It is the first type RO.

[0142] In the embodiment of the present application, the time unit occupied by the second type RO in the time domain is a non-SBFD time unit, and the frequency domain resources occupied by the second type RO in the frequency domain are the frequency domain resources corresponding to the non-SBFD time unit. The frequency domain resources corresponding to the non-SBFD time unit are used for uplink transmission, that is, all frequency domain resources of the non-SBFD time unit are used for uplink transmission. For example, as shown in Figure 6, the non-SBFD time unit is an uplink time unit, that is, time unit 5, and the RO configured on the frequency domain resources of the time unit 5 30 , RO 31 It is the second type RO.

[0143] It should be noted that the various technical solutions (or embodiments) of this application can be implemented independently or in combination based on certain internal connections. This application is not limited thereto. Furthermore, the various terms and definitions between the various embodiments can be referenced to each other. In each embodiment of this application, different implementations can also be implemented in combination or independently.

[0144] Please refer to FIG7 , which is a flow chart of a communication method provided in an embodiment of the present application. As shown in FIG7 , the communication method of this embodiment includes but is not limited to the following steps:

[0145] 701. The terminal device determines the mapping relationship between SSB and RO.

[0146] Exemplarily, step 701 may be an optional step.

[0147] 702. The terminal device sends a random access request message according to the mapping relationship between the SSB and the RO. Correspondingly, the network device receives the random access request message according to the mapping relationship between the SSB and the RO.

[0148] As an example, the mapping relationship between SSB and RO includes the mapping relationship between SSB and the first type RO and the mapping relationship between SSB and the second type RO. For the description of the first type RO and the second type RO, please refer to the term explanation. For example, in Figure 6, if the mapping relationship between SSB and RO includes the mapping relationship between SSB and the first type RO and the mapping relationship between SSB and the second type RO, then the mapping relationship between SSB and RO may include RO 00 , RO 01 , RO 10 , RO 11 , RO 20 , RO 21 , RO 30 , RO 31 , SSB is mapped on each RO.

[0149] As another example, the mapping relationship between SSB and RO may include only the mapping relationship between SSB and the first type RO, but not the mapping relationship between SSB and the second type RO. For example, in FIG6 , if the mapping relationship between SSB and RO only includes the mapping relationship between SSB and the first type RO, then the mapping relationship between SSB and RO may include RO 00 , RO 01 , RO 10 , RO 11 , RO 20 , RO 21 , excluding RO 30 , RO 31 .

[0150] As another example, the mapping relationship between SSB and RO may include only the mapping relationship between SSB and the second type RO, but not the mapping relationship between SSB and the first type RO. For example, in FIG6 , if the mapping relationship between SSB and RO only includes the mapping relationship between SSB and the second type RO, then the mapping relationship between SSB and RO may include RO 30 , RO 31 , excluding RO00 , RO 01 , RO 10 , RO 11 , RO 20 , RO 21 .

[0151] After triggering the random access process, the terminal device can measure the RSRP of the SSB sent by the network device and determine the SSB that meets the RSRP condition. If there are multiple SSBs that meet the RSRP condition, one SSB is selected from them, and one or more ROs associated with the SSB are determined based on the mapping relationship between the SSB and the RO, and a random access request message is sent on the selected RO. After receiving the random access request message, the network device can determine the RO where the random access request message is located, and based on the mapping relationship between the SSB and the RO, determine the SSB corresponding to the RO where the random access request message is located. The SSB is the SSB selected by the terminal device, and the network device uses the beam corresponding to the SSB selected by the terminal device to send a random access response.

[0152] For ease of description, in the following embodiments, the mapping relationship between SSB and RO includes the mapping relationship between SSB and the first type RO and the mapping relationship between SSB and the second type RO as examples.

[0153] For example, in the mapping relationship between SSB and RO, the resource configurations of the mapping relationship between SSB and the first type RO and the mapping relationship between SSB and the second type RO may be the same or different, and this application does not limit this. Wherein the resource configurations of the mapping relationship between SSB and the first type RO and the mapping relationship between SSB and the second type RO are the same, it can be understood that the mapping relationship between the first type RO and the mapping relationship between SSB and the second type RO share the same set of resource configurations.

[0154] The resource configuration may include the time domain resource configuration and / or frequency domain resource configuration of the RO. Further optionally, the resource configuration may also include the number of SSBs associated with each RO, that is, the value of the SSB-perRACH-Occasion configuration. For example, the resource configuration may include at least one of the following: the size of the PRACH cycle, the number of ROs in the time domain within a PRACH cycle, the number of ROs multiplexed on the frequency (that is, the value of msg1-FDM), the number of SSBs associated with each RO (that is, the value of the SSB-perRACH-Occasion configuration), etc. The different resource configurations may be at least one of the size of the PRACH cycle, the number of ROs in the time domain within a PRACH cycle, the number of ROs multiplexed on the frequency, and the number of SSBs associated with each RO.

[0155] As an example, when SSB is mapped to RO, it is mapped to each RO in order from small to large according to the index value of the SSB, without distinguishing the type of RO. In this way, the index values ​​of SSB mapped to different types of RO are also continuous. For the convenience of description, the subsequent embodiments will refer to this mapping method as "uniform mapping of SSB to different types of RO". In the embodiments of the present application, the continuous index value of SSB can be understood as mapping in order from small to large according to the index value of SSB for one round, and then mapping in order from small to large according to the index value of SSB. For example, if the network device is configured with 4 SSBs and one RO maps one SSB, then SSB0, SSB1, SSB2, SSB3, SSB0, SSB1, SSB2, SSB3 can be understood as continuous index values.

[0156] As another example, when SSBs are mapped to ROs, they are mapped to ROs of the same type in ascending order of SSB index values. In this approach, only the index values ​​of SSBs mapped to ROs of the same type are continuous. For example, in the mapping relationship between SSBs and ROs, the index values ​​of SSBs mapped to all ROs of the first RO type are continuous, and the index values ​​of SSBs mapped to all ROs of the second RO type are continuous. For ease of description, subsequent embodiments will refer to this mapping approach as "different types of ROs are mapped to different SSBs."

[0157] Regardless of whether the mapping relationship between different types of ROs and SSBs shares the same resource configuration, and whether the SSBs are mapped uniformly, there are two possible implementations of the RO group for PRACH transmission of preamble repetition. PRACH transmission for preamble repetition can be understood as the repeated transmission of the preamble in the PRACH transmission of the random access process, and repeated transmission of the preamble can also be understood as repeated transmission of the random access request message. The network device can configure one or more repetition times for the terminal device, and the terminal device can select one repetition time to transmit the preamble during actual transmission.

[0158] In a first possible implementation, ROs in the same RO group may include ROs of different types. For example, in the mapping relationship between SSBs and ROs, at least one RO group used for PRACH transmission with preamble repetition includes a first RO group, and the ROs in the first RO group include first-type ROs and second-type ROs. In this first possible implementation, RO types may not be distinguished when determining the RO group.

[0159] In a second possible implementation, ROs in the same RO group can only be of the same type. For example, in the SSB-RO mapping relationship, at least one RO group used for PRACH transmission with preamble repetition includes a second RO group and / or a third RO group; the ROs in the second RO group are of the first type, and the ROs in the third RO group are of the second type; or, the ROs in the second RO group are of the second type, and the ROs in the third RO group are of the first type. In this second possible implementation, ROs of different types cannot be in the same RO group. Therefore, it is necessary to distinguish RO types when determining RO groups.

[0160] For example, the network device may configure whether the same RO group includes different types of ROs through high-layer signaling.

[0161] In the above two possible implementations, the index values ​​of the SSBs mapped by the ROs in the same RO group are the same, and the frequency domain resource indexes of the ROs in the same RO group are the same. The number of ROs at different time domain positions included in the RO group is equal to the number of repetitions corresponding to the RO group.

[0162] The following examples illustrate RO group determination methods in four cases with reference to FIG8a to FIG8d . In the following examples, the time unit is a time slot.

[0163] In case 1, the mapping relationship between SSB and the first type RO and the mapping relationship between SSB and the second type RO share the same resource configuration, and different types of ROs are uniformly mapped to SSB.

[0164] As shown in Figure 8a, uplink subbands are configured on the frequency domain resources of time slots n+1, n+2, and n+3, making them SBFD time units. The frequency domain resources of time slot n+4 are frequency domain resources used for uplink transmission, making them non-SBFD time units. The time slots after time slot n+4 are repetitions of time slots n to n+4. In Figure 8a, 801 is a schematic diagram of resource distribution, where U identifies the frequency domain resources used for uplink transmission and D identifies the frequency domain resources used for downlink transmission. ROs corresponding to SBFD time units in the time domain are type I ROs, while ROs corresponding to non-SBFD time units in the time domain are type II ROs. In Figure 8a, 802 identifies grouping method one for RO groups, and 803 identifies grouping method two for RO groups. For details, please refer to the subsequent embodiments. The ROs identified by 802 and 803 are located in the resource identified by 801. For the sake of comparison, the RO located in the resource identified by "U" in 801 is placed in the positions identified by 802 and 803 for description.

[0165] In Figure 8a, the mapping relationship between SSB and the first type of RO and the mapping relationship between SSB and the second type of RO share the same resource configuration. Take the network device configured with 4 SSBs, SSB-perRACH-Occasion = 1 / 2, msg1-FDM = 4 as an example. Different types of ROs are uniformly mapped to SSBs, that is, the RO type is not distinguished when mapping SSBs, and the index values ​​of the SSBs mapped to different types of ROs that are adjacent in the time domain are continuous. As shown in Figure 8a, the 4 ROs in time slot n+3 are first type ROs, and the 4 ROs in time slot n+4 are second type ROs. The index values ​​of the SSBs mapped to the 4 ROs in time slot n+3 and the 4 ROs in time slot n+4 are continuous, that is, SSB0, SSB0, SSB1, SSB1, SSB2, SSB2, SSB3, SSB3.

[0166] In one implementation, the same RO group can include different types of ROs, that is, the symbol type is not distinguished when dividing RO groups. As shown in FIG8a , 802 indicates that different types of ROs can be grouped into the same RO group. For example, the gray-filled ROs used to map SSB2 are grouped into one RO group. Although the RO type corresponding to time slot n+4 is different from the RO type corresponding to time slot n+2, they can still be in the same RO group.

[0167] In another implementation, the same RO group can only include ROs of the same type. That is, RO grouping requires distinguishing RO types. As shown in FIG8a , ROs of the same type can only be grouped into the same RO group as indicated by 803. For example, the gray-filled first-type ROs mapped to SSB2 are grouped into one RO group. The hatched second-type ROs mapped to SSB2 are grouped into another RO group.

[0168] In case 2, the mapping relationship between SSB and the first type RO and the mapping relationship between SSB and the second type RO share the same resource configuration, and different types of ROs are mapped to SSBs respectively.

[0169] As shown in FIG8b , the mapping relationship between SSB and the first type RO and the mapping relationship between SSB and the second type RO share the same resource configuration. 901 indicates the resource distribution. For details, see the description of FIG8a of Case 1, which will not be repeated here.

[0170] In Figure 8b, different types of ROs are mapped to SSBs separately, that is, the index values ​​of the SSBs are mapped to the same type of RO in ascending order. For example, in Figure 8b, the ROs of time slots n+1 to time slots n+3 and time slots n+6 to time slots n+8 are first-type ROs. Therefore, the index values ​​of the SSBs are mapped in ascending order, and the index values ​​of the SSBs mapped to the ROs of time slots n+1 to time slots n+3 and time slots n+6 to time slots n+8 are continuous. The ROs of time slots n+4 and time slots n+9 are second-type ROs. Therefore, the index values ​​of the SSBs are mapped in ascending order, and the index values ​​of the SSBs mapped to the ROs of time slots n+4 and time slots n+9 are continuous.

[0171] In one implementation, the same RO group can include ROs of different types, that is, the symbol type is not distinguished when dividing RO groups. As shown in 902 in Figure 8b, ROs of different symbol types can be grouped into the same RO group. For example, the gray-filled ROs used to map SSB0 can be grouped into one RO group. For example, although the RO type of time slot n+4 is different from that of time slots n+1 and n+3, they can still be in the same RO group.

[0172] In another implementation, the same RO group can only include ROs of the same type. That is, RO grouping requires distinguishing RO types. As shown in FIG8b , ROs of the same type can only be grouped into the same RO group as indicated by 903. For example, the gray-filled first-type ROs mapped to SSB0 are grouped into one RO group, while the diagonally filled second-type ROs mapped to SSB0 are grouped into another RO group.

[0173] In case 3, the mapping relationship between SSB and the first type RO and the mapping relationship between SSB and the second type RO have different resource configurations, and different types of ROs are uniformly mapped to SSB.

[0174] In FIG8c, reference numeral 1001 is a schematic diagram of resource distribution, and for details, please refer to the description of Case 1 in FIG8a.

[0175] In Figure 8c, the mapping relationship between the SSB and the first type of RO and the mapping relationship between the SSB and the second type of RO has different resource configurations. For example, in the mapping relationship between the SSB and the first type of RO, msg1-FDM = 2, and in the mapping relationship between the SSB and the second type of RO, msg1-FDM = 4. Different types of ROs are uniformly mapped to SSBs, that is, the symbol type is not distinguished when mapping SSBs. The index values ​​of the SSBs mapped to different types of ROs are continuous.

[0176] In one implementation, the same RO group can include different types of ROs, i.e., the symbol type is not distinguished when dividing RO groups. As shown in FIG8c , 1002 indicates that different types of ROs can be grouped into the same RO group. For example, different types of ROs filled in gray for mapping SSB3 can be grouped into one RO group.

[0177] In another implementation, the same RO group can only include ROs of the same type. That is, RO grouping requires distinguishing RO types. As shown in FIG8c , ROs of the same type can only be grouped into the same RO group as indicated by 1003. For example, the gray-filled first-type ROs mapped to SSB3 are grouped into one RO group, while the diagonally filled second-type ROs mapped to SSB3 are grouped into another RO group.

[0178] In case 4, the mapping relationship between SSB and the first type RO and the mapping relationship between SSB and the second type RO have different resource configurations, and different types of ROs are mapped to SSBs respectively.

[0179] In FIG8 d , the reference numeral 2001 is a schematic diagram of resource distribution, and for details, please refer to the description of Case 1 in FIG8 a .

[0180] In Figure 8d, the mapping relationship between SSB and the first type RO and the mapping relationship between SSB and the second type RO have different resource configurations. Take the mapping relationship between SSB and the first type RO as an example, msg1-FDM=2, and the mapping relationship between SSB and the second type RO as an example, msg1-FDM=4.

[0181] Different types of ROs are mapped to SSBs respectively, that is, the index values ​​of SSBs are mapped to the same type of RO in ascending order. For example, in Figure 8d, the index values ​​of SSBs mapped to all first type ROs are continuous, and the index values ​​of SSBs mapped to all second type ROs are continuous.

[0182] In one implementation, the same RO group can include different types of ROs, i.e., the symbol type is not distinguished when dividing RO groups. As shown in FIG8d , ROs of different symbol types can be grouped into the same RO group, as indicated by 2002. For example, different types of ROs filled in gray for mapping SSB2 can be grouped into one RO group.

[0183] In another implementation, the same RO group can only include ROs of the same type. That is, RO grouping requires distinguishing RO types. As shown in FIG8d , ROs of the same type can only be grouped into the same RO group as indicated by 2003. For example, the gray-filled first-type ROs mapped to SSB2 are grouped into one RO group, while the diagonally filled second-type ROs mapped to SSB2 are grouped into another RO group.

[0184] The following example illustrates the time offset (time offset or TimeOffsetBetweenStartingRO) in the mapping relationship between SSB and RO after the introduction of SBFD.

[0185] The time offset may refer to the number of ROs that the first RO of the second RO group of two RO groups is offset from the first RO of the first RO group of the first RO group of the two RO groups within a time period. For example, the number of ROs offset is X. The ROs in the two RO groups are mapped to the same SSB, and the frequency domain resource indexes of the ROs in the two RO groups are the same. The frequency domain resource indexes of the offset X ROs are also the same as the frequency domain resource indexes of the ROs in the two RO groups.

[0186] In one implementation, the ROs in the two RO groups are of the same type. For example, the ROs in the two RO groups are all Type 1 ROs or Type 2 ROs, and the types of the X offset ROs are also the same as those in the two RO groups. The two RO groups are adjacent RO groups. These adjacent RO groups are defined as two adjacent RO groups when multiple RO groups containing ROs of the same type are arranged in the time domain according to the ROs within the RO groups.

[0187] For example, if the first of two adjacent RO groups is the second RO group and the second RO group is the fourth RO group, the ROs in the fourth RO group and the ROs in the second RO group are located in the same time period. The types of the ROs in the fourth RO group are the same as those in the second RO group, for example, all are type 1 ROs or all are type 2 ROs. The SSBs mapped to the ROs in the fourth RO group are the same as those in the second RO group, and the frequency domain resource indexes of the ROs in the fourth RO group and the ROs in the second RO group are the same. The first RO in the fourth RO group is the RO determined by shifting the first RO in the second RO group back by X ROs in the time domain. The SSBs mapped to the X ROs are the same as those mapped to the ROs in the second and fourth RO groups, the frequency domain resource indexes of the X ROs are the same as those in the second and fourth RO groups, and the types of the X ROs are the same as those in the second and fourth RO groups.

[0188] The time offset is illustrated below with reference to FIG8e. For example, if the number of repetitions is 2 and the time offset is 4, in FIG8e, the first type RO mapped to SSB2 indicated by A is the first RO of an RO group (which can be understood as the second RO group). Since the number of repetitions is 2, the first type RO mapped to SSB2 indicated by B is the second RO of the RO group. Since the time offset is 4 ROs, it is necessary to offset 4 first type ROs mapped to SSB2 from the first type RO mapped to SSB2 indicated by A, and the frequency domain resource indexes of the 4 first type ROs mapped to SSB2 are the same. In FIG8e, the RO indicated by A is the first RO of the offset, the RO indicated by B is the second RO of the offset, the RO indicated by C is the third RO of the offset, and the RO indicated by D is the fourth RO of the offset. Therefore, the RO indicated by E is the first RO in the next RO group (which can be understood as the fourth RO group).

[0189] In another implementation, the types of the X offset ROs may include different types of ROs, i.e., the SSBs mapped to the X offset ROs are the same as those mapped to the ROs in the two RO groups, and the frequency domain resource indexes of the X offset ROs are the same as those of the ROs in the two RO groups, without limiting the types of the X ROs. Optionally, an RO group may also include ROs of different types.

[0190] The first RO in the RO group described above may also be referred to as the starting RO of the RO group. The first RO in an RO group may be understood as the first RO when the ROs in the RO group are arranged in ascending order according to the time domain resource index.

[0191] The following example illustrates the association period and association pattern period in the mapping relationship between SSB and RO after the introduction of SBFD.

[0192] An association period is the duration of one or more PRACH periods. The PRACH period may also be referred to as a PRACH configuration period. The PRACH period may be obtained according to the configuration of the network device.

[0193] During an association cycle, the N SSBs configured by the network device are mapped M times, where M and N are positive integers. Mapping N SSBs M times can be understood as mapping N SSBs M times, and one round of mapping can include all sequential mappings of the N SSBs. The ROs used to map these M rounds of SSBs can include first-type ROs and / or second-type ROs. For ease of understanding, the following description replaces the description of "SSB mapping at least once" with "SSB mapping at least one round." The following examples illustrate various situations for determining the association cycle:

[0194] Case 1: The RO type is not considered when determining the association period. One association period is the duration of mapping at least one round of SSB. The RO used to map at least one round of SSB may include a first type RO and a second type RO.

[0195] In case 1, as long as N SSBs are mapped for at least one round (e.g., M rounds), the association period can be determined. The SSBs mapped for the M rounds may include first-type ROs and / or second-type ROs. This is illustrated below with reference to Figures 9a and 9b. In Figure 9a, within one association period, N SSBs are mapped for two rounds, and the ROs used to map the two rounds of SSBs are all first-type ROs, i.e., the first-type ROs map the two rounds of SSBs first, so the SSBs mapped for the M rounds include first-type ROs. In Figure 9b, within one association period, N SSBs are mapped for one round, and the ROs used to map the SSBs for that round include first-type ROs and second-type ROs. In this scenario, the SSBs mapped for M rounds include first-type ROs and second-type ROs. In some embodiments, if the second-type RO maps at least one round of SSBs first, but the first-type RO has not yet completed one round of mapping, the ROs included in one association period are second-type ROs, and in this scenario, the SSBs mapped for M rounds include second-type ROs.

[0196] Case 2: When determining the association period, it is necessary to distinguish RO types. One association period is the duration of mapping at least one round of SSB. The ROs used to map at least one round (eg, M rounds) of SSB are of the same type.

[0197] In Case 2, an association cycle is determined when N SSBs complete at least one round (e.g., M rounds) of mapping to ROs of the same RO type. In other words, in Case 2, the ROs mapping these M rounds of SSBs are either Type 1 ROs or Type 2 ROs. For example, in Case 2, only ROs of one RO type may complete at least one round of mapping to SSBs within an association cycle. ROs of the other RO type may not be included within the association cycle, or ROs of the other RO type may not have completed a full round of mapping within the association cycle. As shown in Figure 9a, Type 2 ROs are not included within an association cycle.

[0198] In case 2, the association period can be understood as the smaller value of the first association period and the second association period. The first association period can be the duration for N SSBs to be mapped in at least one round in the first type RO, and the second association period can be the duration for N SSBs to be mapped in at least one round in the second type RO. The first association period is one or more PRACH cycles, and the second association period is one or more PRACH cycles.

[0199] Case 3: When determining the association period, it is necessary to distinguish the RO type. One association period includes at least one round of SSB mapping for a first-type RO and at least one round of SSB mapping for a second-type RO.

[0200] In case 2, the association period can only be determined after N SSBs have been mapped for at least one round in the first type RO and at least one round in the second type RO. For example, N SSBs are mapped for R rounds in the first type RO and MR rounds in the second type RO. R and MR are both positive integers, and the SSBs are mapped for a total of M rounds in one association period.

[0201] The following example is illustrated in conjunction with Figure 9c. When N SSBs are mapped in the first type RO for 3 rounds and in the second type RO for 1 round, the association period can be determined. The association period includes N SSBs being mapped in the first type RO for 3 rounds and in the second type RO for 1 round. One association period is the duration of 2 PRACH cycles.

[0202] In case 3, the association period can be understood as the larger value of the first association period and the second association period. The first association period can be the duration for N SSBs to be mapped in at least one round in the first type RO, and the second association period can be the duration for N SSBs to be mapped in at least one round in the second type RO. The first association period is one or more PRACH cycles, and the second association period is one or more PRACH cycles.

[0203] In the embodiment of the present application, the association mode period may include one or more association periods. For example, the mapping relationship between SSB and RO in the embodiment of the present application includes a first association mode period and a second association mode period. The mapping relationship between SSB and RO in the first association mode period is the same as the mapping relationship between SSB and RO in the second association mode period. The first association mode period and the second association mode period may be any two association mode periods among the multiple association mode periods of the mapping relationship between SSB and RO. Among them, the mapping relationship between SSB and RO is the same, which can be understood as that the mapping relationship between SSB and RO in the second association period is a copy of the mapping relationship between SSB and RO in the first association period, that is, the position of each RO in the second association period and the mapped SSB are the same as the position of each RO in the first association period and the mapped SSB. For details, see the schematic diagrams of the association mode period in Figures 9a to 9c.

[0204] The following examples illustrate the time period in the mapping relationship between SSB and RO after the introduction of SBFD. A time period can include one or more association mode periods. The following two examples illustrate the method of determining the time period:

[0205] Case 1: within a time period, an RO group corresponding to each repetition number of each SSB is included, and an RO group corresponding to one repetition number of an SSB may include a first type RO and a second type RO.

[0206] The RO groups in Case 1 can be understood as grouping ROs without distinguishing between RO types; different types of ROs can be placed in the same RO group. A single time period may include RO groups corresponding to each repetition count for each SSB configured by the network device. The SSB and repetition count can be configured by the network device. For example, the network device can configure eight SSBs and repetition counts {2, 4, 8} through high-layer signaling, and a single time period includes RO groups corresponding to each repetition count for each of these eight SSBs. In a specific implementation, if a single time period includes an RO group corresponding to the maximum repetition count for each SSB, then the time period can be determined to include RO groups corresponding to each repetition count for each SSB. It is understood that in Case 1, RO groups corresponding to the repetition count of an SSB may also include either the first type of RO or the second type of RO.

[0207] The following uses FIG10a as an example to illustrate the time period. A network device can configure eight SSBs and repetition times {2, 4, 8} through high-layer signaling. Since the maximum repetition time is 8, it is necessary to determine an RO group with a repetition time of 8 for each SSB. In FIG10a, since the same RO group may include first-type ROs and second-type ROs, the time period can be the duration of four association mode periods. Specifically, the duration indicated by the time period in FIG10a can be seen. The time period includes RO groups corresponding to each repetition time for each SSB. For example, the RO group corresponding to repetition time 1 of SSB0 includes only first-type ROs, and the RO group corresponding to repetition time 2 of SSB0 includes both first-type ROs and second-type ROs.

[0208] Case 2: a time period includes: a first type RO group corresponding to each number of repetitions of each SSB, and / or a second type RO group corresponding to each number of repetitions of each SSB, the ROs in the first type RO group are all first type ROs, and the ROs in the second type RO group are all second type ROs.

[0209] The RO groups in this case 2 can be understood as the need to distinguish RO types when dividing RO groups, and ROs in the same RO group are of the same RO type.

[0210] In one possible implementation, a time period may include a first type RO group corresponding to each repetition number of each SSB, or a second type RO group corresponding to each repetition number of each SSB. That is, a time period may include only one type of RO group corresponding to each repetition number of each SSB. For example, if the time period is the smaller of time period 1 and time period 2, time period 1 may include a first type RO group corresponding to each repetition number of each SSB, and time period 2 may include a second type RO group corresponding to each repetition number of each SSB. If time period 1 is smaller than time period 2, then the time period is time period 1, and a first type RO group corresponding to each repetition number of each SSB may be included in the time period. It will be understood that in this scenario, time period 1 includes one or more association mode periods.

[0211] In another possible implementation, a time period may include a first type of RO group corresponding to each repetition number of each SSB and a second type of RO group corresponding to each repetition number of each SSB, that is, a time period may include two types of RO groups corresponding to each repetition number of each SSB.

[0212] The time period is illustrated below with reference to FIG10b. The network device can configure 8 SSBs and repetition times {2, 4, 8} through high-level signaling. Since the maximum repetition time is 8, it is necessary to determine the first type RO group and the second type RO group corresponding to the repetition time of 8 for each SSB. In FIG10b, the time period may include the first type RO group corresponding to each repetition time of each SSB and the second type RO group corresponding to each repetition time of each SSB. Therefore, the time period in FIG10b may be 8 association mode periods.

[0213] Please refer to Figure 11, which is a schematic diagram of the structure of a communication device provided in an embodiment of the present application, and the communication device is applied to a terminal device. Exemplarily, the communication device can be a terminal device, or a device in a terminal device, for example, a chip or chip module in the terminal device, or a device that can be used in conjunction with the terminal device. The communication device 100 shown in Figure 11 may include a sending unit 110, wherein:

[0214] The sending unit 110 is configured to send a random access request message according to a mapping relationship between a synchronization signal block SSB and a random access opportunity RO;

[0215] The mapping relationship between the SSB and the RO includes a mapping relationship between the SSB and the first type RO and / or a mapping relationship between the SSB and the second type RO; the time unit occupied by the first type RO in the time domain is an SBFD time unit, and the time unit occupied by the second type RO in the time domain is a non-SBFD time unit.

[0216] In a possible implementation, the frequency domain resources occupied by the first type RO in the frequency domain are the uplink subband corresponding to the SBFD time unit, and the frequency domain resources occupied by the second type RO in the frequency domain are the frequency domain resources corresponding to the non-SBFD time unit, and the frequency domain resources corresponding to the non-SBFD time unit are used for uplink transmission.

[0217] In a possible implementation, at least one RO group for PRACH transmission of preamble code repetition in the mapping relationship between SSB and RO includes a first RO group, and the ROs in the first RO group include the first type RO and the second type RO.

[0218] In a possible implementation manner, at least one RO group for PRACH transmission of preamble code repetition in the mapping relationship between SSB and RO includes the second RO group and / or the third RO group;

[0219] The ROs in the second RO group are the first type ROs, and the ROs in the third RO group are the second type ROs; or,

[0220] The ROs in the second RO group are of the second type, and the ROs in the third RO group are of the first type.

[0221] In a possible implementation, the at least one RO group for PRACH transmission with preamble repetition in the mapping relationship between the SSB and the RO further includes a fourth RO group; the ROs in the fourth RO group and the ROs in the second RO group are located in the same time period;

[0222] The types of the ROs in the fourth RO group are the same as those in the second RO group, the SSBs mapped to the ROs in the fourth RO group are the same as those in the second RO group, and the frequency domain resource indexes of the ROs in the fourth RO group and the ROs in the second RO group are the same;

[0223] The first RO in the fourth RO group is an RO determined by shifting the first RO in the second RO group backward by X ROs in the time domain. SSBs mapped to the X ROs are the same as SSBs mapped to the ROs in the second RO group. Frequency domain resource indexes of the X ROs are the same as frequency domain resource indexes of the ROs in the second RO group. Types of the X ROs are the same as types of the ROs in the second RO group.

[0224] In one possible implementation, the time period of PRACH transmission for preamble code repetition in the mapping relationship between SSB and RO includes an RO group corresponding to each repetition number of each SSB, the RO group includes the first type RO and / or the second type RO, the SSB is the SSB configured by the network, and the repetition number is the repetition number of the preamble code configured by the network.

[0225] In one possible implementation, the time period of PRACH transmission for preamble code repetition in the mapping relationship between SSB and RO includes: a first type RO group corresponding to each repetition number of each SSB, and / or a second type RO group corresponding to each repetition number of each SSB, the RO in the first type RO group is the first type RO, the RO in the second type RO group is the second type RO, the SSB is the SSB configured by the network device, and the repetition number is the repetition number of the preamble code configured by the network.

[0226] In a possible implementation, within an association period in the mapping relationship between the SSB and the RO, N SSBs are mapped M times, and the RO used to map the N SSBs includes the first type RO and / or the second type RO, and N and M are positive integers.

[0227] In a possible implementation, the N SSBs are mapped to the first type RO R times, and the N SSBs are mapped to the second type RO MR times, where R is a positive integer and the value of MR is a positive integer.

[0228] For the description of the specific embodiment of FIG11 , reference can be made to the description of the aforementioned method embodiment, which will not be repeated here.

[0229] Please refer to Figure 12, which is a schematic diagram of the structure of another communication device provided in an embodiment of the present application. The communication device is applied to a network device. For example, the communication device can be a network device or a device in a network device, for example, a chip or chip module in the network device, or a device that can be used in conjunction with the network device. The communication device 200 shown in Figure 12 may include a receiving unit 210, wherein:

[0230] The receiving unit 210 is configured to receive a random access request message according to a mapping relationship between a synchronization signal block SSB and a random access opportunity RO;

[0231] The mapping relationship between the SSB and the RO includes a mapping relationship between the SSB and the first type RO and / or a mapping relationship between the SSB and the second type RO; the time unit occupied by the first type RO in the time domain is an SBFD time unit, and the time unit occupied by the second type RO in the time domain is a non-SBFD time unit.

[0232] In a possible implementation, the frequency domain resources occupied by the first type RO in the frequency domain are the uplink subband corresponding to the SBFD time unit, and the frequency domain resources occupied by the second type RO in the frequency domain are the frequency domain resources corresponding to the non-SBFD time unit, and the frequency domain resources corresponding to the non-SBFD time unit are used for uplink transmission.

[0233] In a possible implementation, at least one RO group for PRACH transmission of preamble code repetition in the mapping relationship between SSB and RO includes a first RO group, and the ROs in the first RO group include the first type RO and the second type RO.

[0234] In a possible implementation manner, at least one RO group for PRACH transmission of preamble code repetition in the mapping relationship between SSB and RO includes the second RO group and / or the third RO group;

[0235] The ROs in the second RO group are the first type ROs, and the ROs in the third RO group are the second type ROs; or,

[0236] The ROs in the second RO group are of the second type, and the ROs in the third RO group are of the first type.

[0237] In a possible implementation, the at least one RO group for PRACH transmission with preamble repetition in the mapping relationship between the SSB and the RO further includes a fourth RO group; the ROs in the fourth RO group and the ROs in the second RO group are located in the same time period;

[0238] The types of the ROs in the fourth RO group are the same as those in the second RO group, the SSBs mapped to the ROs in the fourth RO group are the same as those in the second RO group, and the frequency domain resource indexes of the ROs in the fourth RO group and the ROs in the second RO group are the same;

[0239] The first RO in the fourth RO group is an RO determined by shifting the first RO in the second RO group backward by X ROs in the time domain. SSBs mapped to the X ROs are the same as SSBs mapped to the ROs in the second RO group. Frequency domain resource indexes of the X ROs are the same as frequency domain resource indexes of the ROs in the second RO group. Types of the X ROs are the same as types of the ROs in the second RO group.

[0240] In one possible implementation, the time period of PRACH transmission for preamble code repetition in the mapping relationship between SSB and RO includes an RO group corresponding to each repetition number of each SSB, the RO group includes the first type RO and / or the second type RO, the SSB is the SSB configured by the network, and the repetition number is the repetition number of the preamble code configured by the network.

[0241] In one possible implementation, the time period of PRACH transmission for preamble code repetition in the mapping relationship between SSB and RO includes: a first type RO group corresponding to each repetition number of each SSB, and / or a second type RO group corresponding to each repetition number of each SSB, the RO in the first type RO group is the first type RO, the RO in the second type RO group is the second type RO, the SSB is the SSB configured by the network device, and the repetition number is the repetition number of the preamble code configured by the network.

[0242] In a possible implementation, within an association period in the mapping relationship between the SSB and the RO, the N SSBs are mapped at least M times, and the RO used to map the N SSBs includes the first type RO and / or the second type RO, and N and M are positive integers.

[0243] In one possible implementation, the RO used to map the N SSBs includes the first type RO and the second type RO, the N SSBs are mapped to the first type RO R times, and the N SSBs are mapped to the second type RO MR times, where R is a positive integer and the value of MR is a positive integer.

[0244] For the description of the specific embodiment of FIG12 , reference can be made to the description of the aforementioned method embodiment, which will not be repeated here.

[0245] Please refer to Figure 13, which is a schematic diagram of the structure of a communication device provided in an embodiment of the present application, which is used to implement the functions of the terminal device in the above method embodiment, or to implement the functions of the network device in the above method embodiment. The communication device 300 can be a terminal device or a device for a terminal device. The device for a terminal device can be a chip system or chip within the terminal device. The communication device can also be a network device or a device for a network device. The device for a network device can be a chip system or chip within the network device. Among them, the chip system can be composed of chips, or it can include chips and other discrete devices.

[0246] The communication device 300 includes at least one processor 320 for implementing the data processing function of the terminal device or network device in the method provided in the embodiment of the present application. The communication device 300 may also include a communication interface 310 for implementing the transceiver operation of the terminal device or network device in the method provided in the embodiment of the present application. In the embodiment of the present application, the processor 320 may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. In the embodiment of the present application, the communication interface 310 may be a transceiver, circuit, bus, module or other type of communication interface for communicating with other devices via a transmission medium. For example, the communication interface 310 is used for the communication device 300 to communicate with other devices. The processor 320 uses the communication interface 310 to send and receive data and is used to implement the method described in the above method embodiment.

[0247] The communication device 300 may also include at least one memory 330 for storing program instructions and / or data. The memory 330 is coupled to the processor 320. The coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, which may be electrical, mechanical, or other forms, and is used for information exchange between the devices, units, or modules. The processor 320 may operate in conjunction with the memory 330. The processor 320 may execute program instructions stored in the memory 330. At least one of the at least one memory may be included in the processor.

[0248] When the communication device 300 is turned on, the processor 320 can read the software program in the memory 330, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be sent wirelessly, the processor 320 performs baseband processing on the data to be sent and outputs the baseband signal to the radio frequency circuit (not shown in Figure 13). The radio frequency circuit performs radio frequency processing on the baseband signal and then transmits the radio frequency signal to the outside in the form of electromagnetic waves through the antenna. When data is sent to the communication device 300, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor 320. The processor 320 converts the baseband signal into data and processes the data.

[0249] In another implementation, the RF circuit and antenna may be provided independently of the processor 320 that performs baseband processing. For example, in a distributed scenario, the RF circuit and antenna may be remotely located independent of the device.

[0250] The specific connection medium between the communication interface 310, processor 320, and memory 330 is not limited in the embodiments of the present application. In Figure 13, the embodiment of the present application shows that the memory 330, processor 320, and communication interface 310 are connected via a bus 340. The bus is represented by a bold line in Figure 13. The connection method between other components is only for schematic illustration and is not limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one bold line is used in Figure 13, but this does not mean that there is only one bus or one type of bus.

[0251] When the communication device 300 is specifically used in a terminal device, for example, when the communication device 300 is specifically a chip or a chip system, the communication interface 310 may output or receive a baseband signal. When the communication device 300 is specifically a terminal device, the communication interface 310 may output or receive a radio frequency signal.

[0252] It should be noted that the device can execute the relevant steps of the terminal device or network device in the above method embodiment. For details, please refer to the implementation methods provided in the above steps, which will not be repeated here.

[0253] For each device or product applied to or integrated in the device, each module contained therein can be implemented by hardware such as circuits, and different modules can be located in the same component (for example, a chip, circuit module, etc.) or different components within the terminal device, or at least some of the modules can be implemented by a software program that runs on a processor integrated within the terminal device, and the remaining (if any) modules can be implemented by hardware such as circuits.

[0254] The memory may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0255] An embodiment of the present application provides a chip. The chip includes a processor and, optionally, a memory. The processor may be one or more, and the memory may be one or more. The processor reads instructions and data stored in the memory to execute the method described in the above method embodiment and the steps performed in related implementation methods.

[0256] As shown in Figure 14, which is a schematic diagram of the structure of a module device provided in an embodiment of the present application, the module device 400 can execute the steps related to the terminal device in the aforementioned method embodiment, or the module device 400 can execute the steps related to the network device in the aforementioned method embodiment.

[0257] The module device 400 includes a communication module 410, a power module 420, a storage module 430, and a chip module 440. The power module 420 is used to provide power to the module device; the storage module 430 is used to store data and / or instructions; the communication module 410 is used to communicate with external devices; and the chip module 440 is used to access the data and / or instructions stored in the storage module 430. In combination with the communication module 410, the method described in the above method embodiment and the steps performed in the related implementation methods can be executed.

[0258] The present application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, which includes program instructions. When an electronic device executes the program instructions, the electronic device implements the steps performed by the terminal device in the method shown in the above method embodiment, or implements the steps performed by the network device in the method shown in the above method embodiment.

[0259] The computer-readable storage medium may be an internal storage unit of the terminal device or network device described in any of the aforementioned embodiments, such as a hard disk or memory of the device. The computer-readable storage medium may also be an external storage device of the terminal device or network device, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the device. Furthermore, the computer-readable storage medium may include both an internal storage unit of the terminal device or network device and an external storage device. The computer-readable storage medium is used to store the computer program and other programs and data required by the terminal device or network device. The computer-readable storage medium may also be used to temporarily store data that has been output or is to be output. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that contains a collection of one or more available media. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, or a magnetic tape), an optical medium (e.g., a high-density digital video disc (DVD)), or a semiconductor medium. The semiconductor medium may be a solid-state drive.

[0260] Regarding the various modules / units contained in the various devices and products described in the above embodiments, they can be software modules / units, hardware modules / units, or partly software modules / units and partly hardware modules / units. For example, for various devices and products applied to or integrated in a chip, the various modules / units contained therein can all be implemented in the form of hardware such as circuits, or at least part of the modules / units can be implemented in the form of software programs, which run on the processor integrated inside the chip, and the remaining (if any) modules / units can be implemented in the form of hardware such as circuits; for various devices and products applied to or integrated in a chip module, the various modules / units contained therein can all be implemented in the form of hardware such as circuits, and different modules / units can be located in the same component of the chip module (such as a chip, circuit module, etc.) or in different components, or at least part of the modules / units can be implemented in the form of software programs. It can be implemented in the form of a software program that runs on a processor integrated inside the chip module, and the remaining (if any) modules / units can be implemented in the form of hardware such as circuits; for various devices and products applied to or integrated in the data acquisition node, the various modules / units contained therein can be implemented in the form of hardware such as circuits, and different modules / units can be located in the same component (for example, chip, circuit module, etc.) or different components in the terminal device, or at least some modules / units can be implemented in the form of a software program that runs on a processor integrated inside the data acquisition node, and the remaining (if any) modules / units can be implemented in the form of hardware such as circuits.

[0261] The above embodiments can be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented using software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer program are loaded or executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired or wireless means.

[0262] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0263] In the several embodiments provided in this application, it should be understood that the disclosed methods, devices, and systems can be implemented in other ways. For example, the device embodiments described above are merely schematic; for example, the division of the units is merely a logical function division, and there may be other division methods in actual implementation; for example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, indirect coupling or communication connection of devices or units, which may be electrical, mechanical, or other forms.

[0264] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0265] In addition, the functional units in various embodiments of the present invention may be integrated into a single processing unit, each unit may be physically included separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or hardware plus software functional units.

[0266] The above-mentioned integrated unit implemented in the form of a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit stored in a storage medium includes a number of instructions for causing a computer device (which can be a personal computer, server, or gateway node, etc.) to perform some steps of the method described in various embodiments of the present invention.

[0267] Those skilled in the art will appreciate that all or part of the processes in the above-described method embodiments can be implemented by instructing related hardware through a computer program. The program can be stored in a computer-readable storage medium, and when executed, the program can include the processes in the above-described method embodiments. The storage medium can be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

[0268] The above disclosure is only a preferred embodiment of the present application, and certainly cannot be used to limit the scope of rights of the present application. Ordinary technicians in this field can understand that all or part of the processes of the above embodiment and equivalent changes made in accordance with the claims of this application are still within the scope covered by the application.

Claims

1. A communication method, characterized in that: include: Send a random access request message according to the mapping relationship between the synchronization signal block SSB and the random access opportunity RO; The mapping relationship between SSB and RO includes a mapping relationship between SSB and a first type of RO and / or a mapping relationship between SSB and a second type of RO; the time unit occupied by the first type of RO in the time domain is a sub-band full-duplex SBFD time unit, and the time unit occupied by the second type of RO in the time domain is a non-SBFD time unit.

2. The method according to claim 1, wherein The frequency domain resources occupied by the first type RO in the frequency domain are the uplink subband corresponding to the SBFD time unit, and the frequency domain resources occupied by the second type RO in the frequency domain are the frequency domain resources corresponding to the non-SBFD time unit, and the frequency domain resources corresponding to the non-SBFD time unit are used for uplink transmission.

3. The method according to claim 1 or 2, wherein: At least one RO group for PRACH transmission of preamble code repetition in the mapping relationship between SSB and RO includes a first RO group, and the ROs in the first RO group include the first type RO and the second type RO.

4. The method according to claim 1 or 2, wherein: The at least one RO group for PRACH transmission of preamble code repetition in the mapping relationship between SSB and RO includes the second RO group and / or the third RO group; The ROs in the second RO group are the first type ROs, and the ROs in the third RO group are the second type ROs; or, The ROs in the second RO group are of the second type, and the ROs in the third RO group are of the first type.

5. The method according to claim 4, wherein The at least one RO group for PRACH transmission of preamble code repetition in the mapping relationship between SSB and RO also includes a fourth RO group; the ROs in the fourth RO group and the ROs in the second RO group are located in the same time period; The types of the ROs in the fourth RO group are the same as those in the second RO group, the SSBs mapped to the ROs in the fourth RO group are the same as those in the second RO group, and the frequency domain resource indexes of the ROs in the fourth RO group and the ROs in the second RO group are the same; The first RO in the fourth RO group is an RO determined by shifting the first RO in the second RO group backward by X ROs in the time domain. SSBs mapped to the X ROs are the same as SSBs mapped to the ROs in the second RO group. Frequency domain resource indexes of the X ROs are the same as frequency domain resource indexes of the ROs in the second RO group. Types of the X ROs are the same as types of the ROs in the second RO group.

6. The method according to claim 3, wherein The time period of PRACH transmission for preamble code repetition in the mapping relationship between SSB and RO includes an RO group corresponding to each repetition number of each SSB, the RO group includes the first type RO and / or the second type RO, the SSB is the SSB configured by the network, and the repetition number is the repetition number of the preamble code configured by the network.

7. The method according to claim 4 or 5, characterized in that The time period of PRACH transmission for preamble code repetition in the mapping relationship between SSB and RO includes: a first type RO group corresponding to each repetition number of each SSB, and / or a second type RO group corresponding to each repetition number of each SSB, the RO in the first type RO group is the first type RO, the RO in the second type RO group is the second type RO, the SSB is the SSB configured by the network device, and the repetition number is the repetition number of the preamble code configured by the network.

8. The method according to any one of claims 1 to 7, wherein: In an association cycle of the mapping relationship between the SSB and the RO, N SSBs are mapped M times, and the ROs used to map the N SSBs include the first type RO and / or the second type RO, and N and M are positive integers.

9. The method according to claim 8, wherein The RO used to map the N SSBs includes the first type RO and the second type RO, the N SSBs are mapped to the first type RO R times, and the N SSBs are mapped to the second type RO MR times, where R is a positive integer and the value of MR is a positive integer.

10. A communication method, characterized in that: include: receiving a random access request message according to a mapping relationship between a synchronization signal block SSB and a random access opportunity RO; The mapping relationship between the SSB and the RO includes a mapping relationship between the SSB and the first type RO and / or a mapping relationship between the SSB and the second type RO; the time unit occupied by the first type RO in the time domain is an SBFD time unit, and the time unit occupied by the second type RO in the time domain is a non-SBFD time unit.

11. The method according to claim 10, wherein The frequency domain resources occupied by the first type RO in the frequency domain are the uplink subband corresponding to the SBFD time unit, and the frequency domain resources occupied by the second type RO in the frequency domain are the frequency domain resources corresponding to the non-SBFD time unit, and the frequency domain resources corresponding to the non-SBFD time unit are used for uplink transmission.

12. The method according to claim 10 or 11, wherein: At least one RO group for PRACH transmission of preamble code repetition in the mapping relationship between SSB and RO includes a first RO group, and the ROs in the first RO group include the first type RO and the second type RO.

13. The method according to claim 10 or 11, characterized in that The at least one RO group for PRACH transmission of preamble code repetition in the mapping relationship between SSB and RO includes the second RO group and / or the third RO group; The ROs in the second RO group are the first type ROs, and the ROs in the third RO group are the second type ROs; or, The ROs in the second RO group are of the second type, and the ROs in the third RO group are of the first type.

14. The method according to claim 13, wherein The at least one RO group for PRACH transmission of preamble code repetition in the mapping relationship between SSB and RO also includes a fourth RO group; the ROs in the fourth RO group and the ROs in the second RO group are located in the same time period; The types of the ROs in the fourth RO group are the same as those in the second RO group, the SSBs mapped to the ROs in the fourth RO group are the same as those in the second RO group, and the frequency domain resource indexes of the ROs in the fourth RO group and the ROs in the second RO group are the same; The first RO in the fourth RO group is an RO determined by shifting the first RO in the second RO group backward by X ROs in the time domain. SSBs mapped to the X ROs are the same as SSBs mapped to the ROs in the second RO group. Frequency domain resource indexes of the X ROs are the same as frequency domain resource indexes of the ROs in the second RO group. Types of the X ROs are the same as types of the ROs in the second RO group.

15. The method according to claim 12, wherein The time period of PRACH transmission for preamble code repetition in the mapping relationship between SSB and RO includes an RO group corresponding to each repetition number of each SSB, the RO group includes the first type RO and / or the second type RO, the SSB is the SSB configured by the network, and the repetition number is the repetition number of the preamble code configured by the network.

16. The method according to claim 13 or 14, wherein: The time period of PRACH transmission for preamble code repetition in the mapping relationship between SSB and RO includes: a first type RO group corresponding to each repetition number of each SSB, and / or a second type RO group corresponding to each repetition number of each SSB, the RO in the first type RO group is the first type RO, the RO in the second type RO group is the second type RO, the SSB is the SSB configured by the network device, and the repetition number is the repetition number of the preamble code configured by the network.

17. The method according to any one of claims 10 to 16, wherein: In an association cycle of the mapping relationship between the SSB and the RO, the N SSBs are mapped at least M times, and the ROs used to map the N SSBs include the first type RO and / or the second type RO, and N and M are positive integers.

18. The method according to claim 17, wherein The RO used to map the N SSBs includes the first type RO and the second type RO, the N SSBs are mapped to the first type RO R times, and the N SSBs are mapped to the second type RO MR times, where R is a positive integer and the value of MR is a positive integer.

19. A communication device, characterized in that: include: A sending unit, configured to send a random access request message according to a mapping relationship between a synchronization signal block SSB and a random access opportunity RO; The mapping relationship between the SSB and the RO includes a mapping relationship between the SSB and the first type RO and / or a mapping relationship between the SSB and the second type RO; the time unit occupied by the first type RO in the time domain is an SBFD time unit, and the time unit occupied by the second type RO in the time domain is a non-SBFD time unit.

20. A communication device, characterized in that: include: A receiving unit, configured to receive a random access request message according to a mapping relationship between a synchronization signal block SSB and a random access opportunity RO; The mapping relationship between the SSB and the RO includes a mapping relationship between the SSB and the first type RO and / or a mapping relationship between the SSB and the second type RO; the time unit occupied by the first type RO in the time domain is an SBFD time unit, and the time unit occupied by the second type RO in the time domain is a non-SBFD time unit.

21. A communication device, characterized in that: The communication device includes a processor and a memory, and the processor and the memory are connected to each other, wherein the memory is used to store a computer program, and the computer program includes program instructions. The processor calls the program instructions to execute the method according to any one of claims 1 to 9, or executes the method according to any one of claims 10 to 18.

22. A chip, characterized in that: The chip includes a processor and an interface, and the processor and the interface are coupled; the interface is used to receive or output signals, and the processor is used to execute code instructions, execute the method according to any one of claims 1 to 9, or execute the method according to any one of claims 10 to 18.

23. A module device, characterized in that: The module device includes a communication module, a power module, a storage module and a chip module, wherein: The power supply module is used to provide electrical energy to the module device; The storage module is used to store data and / or instructions; The communication module is used to communicate with external devices; The chip module is used to call the data and / or instructions stored in the storage module, and in combination with the communication module, execute the method according to any one of claims 1 to 9, or execute the method according to any one of claims 10 to 18.

24. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, which includes program instructions. When a computer executes the program instructions, the method according to any one of claims 1 to 9 is implemented, or the method according to any one of claims 10 to 18 is implemented.

Images