Communication method and communication device

Abstract

Provided are a communication method and a communication device, the method comprising: receiving a first physical random access channel (PRACH) resource and a second PRACH resource configured by a network device, the first PRACH resource comprising PRACH resources located in a first flexible time domain unit and a sub-band full duplex (SBFD) time domain unit, and the second PRACH resource comprising PRACH resources located in a second flexible time domain unit; the second PRACH resource comprises PRACH resources located in a second flexible time domain unit and an uplink UL time domain unit, and the first flexible time domain unit and the second flexible time domain unit are overlapped on the time domain; and transmitting a signal according to the first PRACH resource or the second PRACH resource, in which all or part of the PRACH resources on the first flexible time domain unit are not used for transmitting the signal. According to the invention, the influence on the random access of the terminal equipment can be reduced, so that the detection performance of the terminal equipment can be prevented from being reduced, and the communication quality is improved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method and a communication device. Background Technology

[0002] Network devices can configure Physical Random Access Channel (PRACH) resources using different parameters. For example, network devices can specify PRACH resources located in flexible time slots and uplink (UL) time slots using RACH-ConfigGeneric, or they can specify PRACH resources located in flexible time slots and subband full duplex (SBFD) time slots using PRACH configuration index. The overlap of these two types of PRACH resources in flexible time slots leads to synchronization signal and PBCH block (SSB) mapping conflicts and resource allocation conflicts. To handle this conflict, network devices need to perform complex processing. Advanced network devices with better hardware performance can support the simultaneous generation of multiple beams without affecting the random access of terminal devices. However, low-level network devices with poorer hardware performance lack this capability, impacting the random access of terminal devices and consequently reducing their detection performance. Summary of the Invention

[0003] This application provides a communication method and a communication device to improve communication quality.

[0004] Firstly, this application provides a communication method that can be applied to a terminal side, such as a terminal or a communication module within a terminal, or a circuit or chip in the terminal responsible for communication functions (such as a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip or system-in-package (SIP) chip containing a modem core). Taking the application of this method to a terminal device as an example, in this method, the terminal device receives a first physical random access channel (PRACH) resource and a second PRACH resource configured by a network device. The first PRACH resource includes PRACH resources located in a first flexible time domain unit and a sub-band full-duplex (SBFD) time domain unit, and the second PRACH resource includes PRACH resources located in a second flexible time domain unit and an uplink UL time domain unit. The first and second flexible time domain units overlap in the time domain. The method also involves transmitting a signal according to the first or second PRACH resource, wherein all or part of the PRACH resources in the first flexible time domain unit are not used for transmitting signals.

[0005] In this embodiment, the terminal device transmits signals based on either the first PRACH resource or the second PRACH resource, and all or part of the PRACH resources in the first flexible time domain unit are not used for signal transmission. That is, for PRACH resources located in the first flexible time domain unit and PRACH resources located in the second flexible time domain unit, the terminal device can transmit signals based on part of the PRACH resources in the first flexible time domain unit and all of the PRACH resources in the second flexible time domain unit. Alternatively, the terminal device may not transmit signals using the PRACH resources in the first flexible time domain unit, but instead use all of the PRACH resources in the second flexible time domain unit for signal transmission. This embodiment essentially redefines the PRACH resources in the overlapping portion of the first and second PRACH resources, reducing the impact on random access of the terminal device, thereby avoiding a decrease in the detection performance of the terminal device and improving communication quality.

[0006] Furthermore, in this application embodiment, all or part of the PRACH resources on the first flexible time domain unit are not used for signal transmission, but this does not restrict the PRACH resources on the second flexible time domain unit from being used for signal transmission. It can be considered that the PRACH resources on the second flexible time domain unit can be used for signal transmission. This design can be compatible with the use of older terminal devices, thereby improving the diversity of scenarios applicable to the solution of this application.

[0007] In conjunction with the first aspect, in one possible implementation, if the SBFD symbol does not occupy the first flexible time domain unit, all resources in the PRACH resources located in the first flexible time domain unit are not used for signal transmission; or, if the SBFD symbol occupies the first flexible time domain unit, all or part of the resources in the PRACH resources located in the first flexible time domain unit are not used for signal transmission. The first PRACH resource is located in the first time-frequency resource, and the first time-frequency resource includes the SBFD symbol in the time domain.

[0008] In this embodiment, whether all or part of the PRACH resources located in the first flexible time domain unit are not used for signal transmission depends on whether the SBFD symbol occupies the first flexible time domain unit. Specifically, if the SBFD symbol does not occupy the first flexible time domain unit, all the PRACH resources located in the first flexible time domain unit are not used for signal transmission. This design is simpler and can reduce the complexity of the system. Alternatively, if the SBFD symbol occupies the first flexible time domain unit, all or part of the PRACH resources located in the first flexible time domain unit are not used for signal transmission. This design can improve the utilization rate of the PRACH resources located in the first flexible time domain unit, thereby reducing resource waste.

[0009] In conjunction with the first aspect, in one possible implementation, the SBFD symbol occupies all time domain units of the first flexible time domain unit; or, the SBFD symbol occupies a portion of the time domain units of the first flexible time domain unit.

[0010] In this embodiment, when an SBFD symbol occupies all or part of the time domain units of the first flexible time domain unit, all or part of the PRACH resources located in the first flexible time domain unit are not used for signal transmission. That is, regardless of whether the SBFD symbol occupies all the time domain units of the first flexible time domain unit, this application designs that all or part of the PRACH resources located in the first flexible time domain unit are not used for signal transmission. This design can improve the utilization rate of the PRACH resources located in the first flexible time domain unit, thereby reducing resource waste.

[0011] In conjunction with the first aspect, in one possible implementation, both the first flexible time domain unit and the second flexible time domain unit include a third flexible time domain unit, and the PRACH resources located in the third flexible time domain unit in the first PRACH resource are unavailable.

[0012] In this embodiment, both the first flexible time domain unit and the second flexible time domain unit include a third flexible time domain unit, and the PRACH resources located in the third flexible time domain unit within the first PRACH resources are unavailable. That is, for the third flexible time domain unit, the terminal device cannot perform random access based on the PRACH resources located in the third flexible time domain unit within the first PRACH resources, but the terminal device can perform random access based on the PRACH resources located in the third flexible time domain unit within the second PRACH resources. Especially when multiple terminal devices are performing random access, this avoids conflicts that occur when different terminal devices simultaneously select PRACH resources in the third flexible time domain unit for random access, thereby improving the success rate of random access for the terminal device.

[0013] In conjunction with the first aspect, in one possible implementation, the method further includes: receiving first information from a network device, the first information indicating that Y frequency division multiplexing ROs out of M1 frequency division multiplexing random access opportunities are invalid, where M1 is an integer greater than 0 and Y is an integer greater than 0 and less than or equal to M1.

[0014] In this embodiment of the application, the network device sends first information to the terminal device. The first information is used to indicate that Y frequency division multiplexing ROs among M1 frequency division multiplexing ROs are invalid. This means that these Y frequency division multiplexing ROs are not used for random access, so the frequency domains corresponding to these Y frequency division multiplexing ROs are idle. The frequency domains corresponding to these Y frequency division multiplexing ROs can be used for the transmission of other data, thereby improving the efficiency of data transmission.

[0015] In conjunction with the first aspect, in one possible implementation, the Y frequency division multiplexing ROs satisfy the following: the distance between the first PRACH resource and the physical downlink shared channel PDSCH resource is less than or equal to N frequency domain units, where N is an integer greater than 0 and less than a preset value.

[0016] This application designs an invalidation of Y frequency division multiplexing ROs in the first PRACH resource where the distance to the PDSCH resource is less than or equal to N frequency domain units. This can reduce the impact of CLI of SBFD PRACH on detection performance, thereby improving detection accuracy and communication quality.

[0017] In conjunction with the first aspect, in one possible implementation, N is indicated by signaling.

[0018] In this embodiment, N is indicated by signaling. For example, if the network device uses the newly added signaling indication N in SIB1, it can use the existing message indication N, thereby simplifying the design, reducing the number of message transmissions of the network device, and reducing the complexity of the system.

[0019] In conjunction with the first aspect, in one possible implementation, M1 bits correspond one-to-one with indicating the invalidity of M1 frequency division multiplexing (FDM) ROs; or, M1 bits indicate 2 M1 2 indexes M1 Each index corresponds to an invalid case of M1 frequency division multiplexing (RO).

[0020] In this embodiment, M1 bits can indicate the invalidity of M1 frequency division multiplexing (FDM) ROs. Specifically, each of the M1 bits corresponds to one of the invalidity of the M1 FDM ROs; or, the M1 bits indicate 2 M1 2 indexes M1 Each index corresponds to an invalid case of M1 frequency division multiplexing (FDM) ROs. The terminal device can determine the invalid cases of M1 FDM ROs based on M1 bits, so that the terminal device can avoid random access in invalid ROs, thereby improving the success rate of random access.

[0021] In conjunction with the first aspect, in one possible implementation, the method further includes: receiving second information from a network device, the second information indicating that K time-division multiplexed ROs out of M2 time-division multiplexed ROs are invalid, the K time-division multiplexed ROs including the ROs of the first time-domain unit in the first PRACH resource, M2 being an integer greater than 0, and K being an integer greater than 0 and less than or equal to M2.

[0022] In this embodiment of the application, the network device sends a second message to the terminal device. The second message is used to indicate that K of the M2 time-division multiplexed ROs are invalid, which is equivalent to these K time-division multiplexed ROs not being used for random access. As a result, the time domains corresponding to these K time-division multiplexed ROs are idle, and the time domains corresponding to these K time-division multiplexed ROs can be used for the transmission of other data, thereby improving the efficiency of data transmission.

[0023] In conjunction with the first aspect, in one possible implementation, the M2 bits correspond one-to-one with the invalid cases of the M2 time-division multiplexed ROs; or, the M2 bits indicate 2 M2 2 indexes M2 Each index corresponds to an invalid case of M2 time-division multiplexing ROs.

[0024] In this embodiment, M2 bits correspond one-to-one with indicating the invalidity of M2 time-division multiplexing ROs; or, M2 bits indicate 2 M2 2 indexes M2 Each index corresponds to an invalid case of M2 time-division multiplexing ROs. The terminal device can determine the invalid case of M2 time-division multiplexing ROs based on M2 bits, so that the terminal device can avoid random access in invalid ROs, thereby improving the success rate of random access.

[0025] Secondly, this application provides a communication device that implements the functions described in the first aspect. For example, the communication device includes modules, units, or means corresponding to the operations involved in the first aspect. These modules, units, or means can be implemented through software, hardware, or a combination of software and hardware. The beneficial effects are described in the first aspect and will not be repeated here. In one possible design, the communication device includes: a communication unit for receiving first physical random access channel (PRACH) resources and second PRACH resources configured by a network device. The first PRACH resources include PRACH resources located in a first flexible time domain unit and a sub-band full-duplex (SBFD) time domain unit, and the second PRACH resources include PRACH resources located in a second flexible time domain unit and an uplink UL time domain unit. The first and second flexible time domain units overlap in the time domain. The unit also transmits signals according to the first or second PRACH resources, wherein all or part of the PRACH resources in the first flexible time domain unit are not used for signal transmission. These units can perform the corresponding functions in the method examples of the first aspect, as described in the detailed description in the method examples and will not be repeated here.

[0026] In one implementation, the device is a communication device (such as a terminal device). When the device is a communication device, the communication unit can be a transceiver or an input / output interface; optionally, the device may further include a processing unit, which can be at least one processor. Alternatively, the device may further include a communication unit, which can be a transceiver or a transceiver circuit.

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

[0028] Thirdly, this application provides a communication device including a transceiver for executing computer programs or instructions to perform the methods in any possible implementation of the first aspect described above. Optionally, the device further includes at least one processor for processing information from the transceiver. Optionally, the device further includes a memory for storing computer programs or instructions.

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

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

[0031] Fourthly, a processor is provided for executing the method provided in the first aspect above.

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

[0033] Fifthly, this application provides a computer-readable storage medium storing computer-readable instructions, which, when read and executed by a computer, cause the computer to perform the method in any possible implementation of the first aspect described above.

[0034] In a sixth aspect, this application provides a computer program product that, when read and executed by a computer, causes the computer to perform the method in any of the possible implementations of the first aspect described above.

[0035] In a seventh aspect, a chip is provided, the chip including a processor and a communication interface, wherein the processor reads instructions from a memory through the communication interface and executes the method provided by any of the above implementations of the first aspect.

[0036] Optionally, the chip is a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip containing a modem core or a system-in-package (SIP) chip.

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

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

[0039] Ninth aspect, a communication system is provided, the communication system including means having a method for implementing any possible implementation of the first aspect, or all possible implementations of the first aspect, and various possible design functions. Attached Figure Description

[0040] Figure 1 This is a schematic diagram of a wireless communication system applicable to embodiments of this application.

[0041] Figure 2 A schematic diagram of the time-frequency division of the TDD scheme is shown.

[0042] Figure 3 A schematic diagram of the time-frequency division of the SBFD scheme is shown.

[0043] Figure 4 A schematic diagram of the time-frequency division of the SFFD scheme is shown.

[0044] Figure 5 A schematic flowchart of the four-step random access process is shown.

[0045] Figure 6 A schematic flowchart of a two-step random access process is shown.

[0046] Figure 7 A schematic diagram of PRACH configuration on a UL time slot is shown.

[0047] Figure 8 A schematic diagram of the time and frequency resources of PRACH is shown.

[0048] Figure 9 A schematic diagram illustrating the relationship between RO and SSB is shown.

[0049] Figure 10 A schematic diagram of uplink and downlink time slot configuration is shown.

[0050] Figure 11 A schematic diagram of PRACH resources with different time slot configurations is shown.

[0051] Figure 12 This is a schematic diagram of a communication method provided in an embodiment of this application.

[0052] Figure 13 This is a schematic diagram of PRACH resources corresponding to different time slots, provided as an embodiment of this application.

[0053] Figure 14 This is a schematic diagram of PRACH resources corresponding to another different time slot provided in an embodiment of this application.

[0054] Figure 15 This is a schematic diagram of another communication method provided in an embodiment of this application.

[0055] Figure 16 This is a schematic diagram of PRACH resources corresponding to different time slots, as provided in an embodiment of this application.

[0056] Figure 17 This is a schematic diagram illustrating the invalidity of frequency division multiplexing (RDBML) in an embodiment of this application.

[0057] Figure 18 This is another schematic diagram illustrating the invalidity of frequency division multiplexing (RD) RO provided in an embodiment of this application.

[0058] Figure 19 This is a schematic diagram of PRACH resources corresponding to another different time slot provided in an embodiment of this application.

[0059] Figure 20 This is a schematic diagram illustrating the ineffectiveness of time-division multiplexing RO as provided in an embodiment of this application.

[0060] Figure 21 This is another schematic diagram illustrating the ineffectiveness of time-division multiplexing RO provided in an embodiment of this application.

[0061] Figure 22 This is a schematic block diagram of a communication device provided in an embodiment of this application.

[0062] Figure 23 This is a schematic diagram of another communication device provided in an embodiment of this application.

[0063] Figure 24 This is a schematic diagram of a chip system provided in an embodiment of this application. Detailed Implementation

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

[0065] The technical solutions of this application embodiment can be applied to various communication systems, such as: Universal Mobile Telecommunications System (UMTS), Wireless Local Area Network (WLAN), Wireless Fidelity (Wi-Fi) system, 4th generation (4G) mobile communication system, such as Long Term Evolution (LTE) system, 5th generation (5G) mobile communication system, such as New Radio (NR) system, and future evolution communication systems, such as 6th generation (6G) mobile communication system, etc.

[0066] In the embodiments of this application, words such as "exemplarily" and "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design scheme described as an "example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the term "example" is intended to present concepts in a concrete manner. In the embodiments of this application, "of," "corresponding, relevant," and "corresponding" may sometimes be used interchangeably, and it should be noted that their intended meanings are consistent unless their distinction is emphasized.

[0067] The communication systems and service scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new service scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0068] Figure 1 A possible, non-limiting system schematic diagram is shown. For example... Figure 1 As shown, the communication system 10 includes a radio access network (RAN) 100 and a core network (CN) 200. RAN 100 includes at least one RAN node (e.g., ...). Figure 1 110a and 110b (collectively referred to as 110) and at least one terminal (such as Figure 1 RAN 100 (120a-120j, collectively referred to as 120) may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in the figure). Terminal 120 is wirelessly connected to RAN node 110. RAN node 110 is wirelessly or wired connected to core network 200. The core network devices in core network 200 and RAN node 110 in RAN 100 can be different physical devices, or they can be the same physical device integrating core network logical functions and wireless access network logical functions.

[0069] RAN 100 can be a cellular system related to the 3rd Generation Partnership Project (3GPP), such as 4G, 5G mobile communication systems, or future-oriented evolution systems (such as 6G mobile communication systems). RAN 100 can also be an open access network (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. RAN 100 can also be a communication system that integrates two or more of the above systems.

[0070] RAN node 110, sometimes also referred to as access network equipment, RAN entity, access node, or network equipment, constitutes part of the communication system and is used to help terminals achieve wireless access. Multiple RAN nodes 110 in communication system 10 can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal 120 are relative, for example... Figure 1 Network element 120i can be a helicopter or a drone, and it can be configured as a mobile base station. For terminals 120j that access RAN 100 through network element 120i, network element 120i is a base station; however, for base station 110a, network element 120i is a terminal. RAN node 110 and terminal 120 are sometimes referred to as communication devices, for example... Figure 1 Network elements 110a and 110b can be understood as communication devices with base station functions, while network elements 120a-120j can be understood as communication devices with terminal functions.

[0071] In one possible scenario, the RAN node can be a device or module located on the network side of the aforementioned communication system 10, possessing corresponding communication functions. The RAN node typically contains communication modules, circuits, or chips that perform the corresponding communication functions. The RAN node is also configured with program instructions for performing the corresponding communication functions, as well as the corresponding program instructions. The RAN node can be a RAN device or network element deployed within the RAN. For example, the RAN node can be a RAN device or a device capable of supporting the RAN device in achieving this function, such as a chip system or a combination device or component capable of implementing access network device functions; this device can be installed within the RAN device. RAN nodes can be access points (APs) in Wi-Fi systems, such as home gateways, routers, servers, switches, and bridges; base stations, base station controllers (BSCs), base transceiver stations (BTSs), home base stations, baseband units (BBUs); wireless relay nodes; wireless backhaul nodes; evolved Node Bs (eNBs) in 4G systems; next-generation eNBs (ng-eNBs) during the transition from 4G to 5G systems; next-generation base stations (gNBs) in 5G systems; or RAN nodes implementing (partial) gNB functions. RAN nodes can also be macro base stations (such as...) Figure 1 110a), micro base stations or indoor stations (such as Figure 1 The RAN node can be a relay node or donor node (also known as a host node), or a radio controller in a CRAN scenario. Optionally, the RAN node can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). All or part of the functions of the RAN node in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The RAN node in this application can also be a logical node, logical module, or software capable of implementing all or part of the RAN node functions.

[0072] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, with different RAN nodes each implementing a portion of the base station's functions. For example, RAN nodes can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be set up separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0073] In some examples, the CU is a logical node carrying the radio resource control (RRC) layer, service data adaptation protocol (SDAP) layer, packet data convergence protocol (PDCP) layer, and other control functions of the access network equipment. The CU connects to network nodes such as the core network through interfaces, which can be interfaces such as E2 interfaces. Optionally, the CU may have some core network functions. The CU (e.g., the PDCP layer and higher layers) connects to the DU (e.g., radio link control (RLC) and lower layers) through interfaces, which can be interfaces such as F1 interfaces. In some examples, these interfaces (e.g., the F1 interface) can provide control plane and user plane functions (e.g., interface management, system information management, user equipment (UE) context management, RRC message transmission, etc.). F1AP is the application protocol of the F1 interface, defining the F1 signaling procedures in some examples. The F1 interface supports control plane F1-C and user plane F1-U.

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

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

[0076] In some examples, the RU is a logical node carrying both lower physical layer (PHY) and radio frequency (RF) processing. In some examples, the RU can be a 3GPP transmission reception point (TRP), a remote radio head (RRH), or other similar entities. In some examples, the Low-PHY includes PHY processing functions such as Fast Fourier Transform (FFT), Inverse Fast Fourier Transform (IFFT), digital beamforming, and filtering. The RU communicates with one or more UEs via a radio link.

[0077] The DU and RU can be co-located or not. The DU and RU exchange control plane and user plane information via a fronthaul link through a lower-layer split-control, user, and synchronization (LLS-CUS) interface. LLS-CUS may include interfaces providing control plane (C-plane) and user plane (U-plane) information, respectively. In some examples, the control plane refers to real-time control between the DU and RU. The DU and RU exchange management information via a fronthaul link interface (such as a lower-layer split-management (LLS-M) interface); the user plane refers to non-real-time management operations between the DU and RU.

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

[0079] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, a radio access network may also be an open-RAN (O-RAN) architecture. In an O-RAN system, CU may also be called an open CU (open CU, O-CU), DU may also be called an open DU (open DU, O-DU), CU-CP may also be called an open CU-CP (open CU-CP, O-CU-CP), CU-UP may also be called an open CU-UP (open CU-UP, O-CU-UP), and RU may also be called an open RU (open RU, O-RU). Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application may be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.

[0080] As mentioned above, RAN nodes are sometimes also referred to as network devices. Unless otherwise specified, this application will use the term "network device" to describe them.

[0081] A terminal can be a device or module that accesses the aforementioned communication system 10 and has corresponding communication functions. A terminal can also be referred to as terminal equipment, user equipment, user device, access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal, remote station, remote terminal, mobile device, user terminal, terminal unit, terminal station, terminal device, wireless communication equipment, user agent, or user device. A terminal typically contains a communication module, circuit, or chip that performs the corresponding communication functions. The terminal may also be configured with program instructions for performing these communication functions.

[0082] Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearables, smart transportation, smart cities, etc. The terminal can be a mobile phone, a personal digital assistant (PDA) computer, a laptop computer, a tablet computer, a drone, a computer with wireless transceiver capabilities, a machine-type communication (MTC) terminal, a virtual reality (VR) terminal, an augmented reality (AR) terminal, an Internet of Things (IoT) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical care, 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 (e.g., game consoles, smart TVs, smart speakers, smart refrigerators, and fitness equipment), a transportation vehicle with wireless communication capabilities, a communication module, or a roadside unit (RSU) with terminal functionality. The embodiments of this application do not limit the device form of the terminal.

[0083] It should be understood that, in the embodiments of this application, the terminal device or access network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through processes, such as Linux, Unix, Android, iOS, or Windows. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software. Furthermore, the embodiments of this application do not particularly limit the specific structure of the execution subject of the method provided in the embodiments of this application, as long as it can communicate according to the method provided in the embodiments of this application by running a program that records the code of the method provided in the embodiments of this application. For example, the execution subject of the method provided in the embodiments of this application can be a terminal device, or a functional module in the terminal device that can call and execute a program.

[0084] Furthermore, various aspects or features of this application can be implemented as methods, apparatus, or articles of manufacture using standard programming and / or engineering techniques. The term "article of manufacture" as used in this application encompasses a computer program accessible from any computer-readable device, carrier, or medium. For example, computer-readable storage media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical discs (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROM), cards, sticks, or key drives, etc.).

[0085] Additionally, the various storage media described herein may represent one or more devices and / or other machine-readable storage media used for storing information. The term "machine-readable storage media" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0086] It should be understood that the methods, situations, categories, and classifications of embodiments in this application are for the convenience of description only and should not constitute a special limitation. Various methods, categories, situations, and features in embodiments can be combined without contradiction.

[0087] Understandable Figure 1This is a simplified diagram for ease of understanding only. The communication system may also include other possible devices, and each device may contain different functional units. Figure 1 It is not shown in the middle.

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

[0089] To facilitate understanding of the embodiments of this application, the basic concepts involved in this application will be explained first.

[0090] 1. Time Division Duplex (TDD): In a TDD system, time-domain resources are divided into uplink and downlink. For example, one possible uplink / downlink configuration in a TDD system is DDDSU, where D represents a downlink time slot, where each symbol in the downlink time slot is a downlink symbol; U represents an uplink time slot, where each symbol in the uplink time slot is an uplink symbol; and S represents a special time slot, which includes at least flexible symbols.

[0091] In widely used TDD systems, the downlink typically occupies most of the time resources, resulting in poor uplink coverage and high latency, which cannot meet the needs of emerging services (such as VR and AR).

[0092] For example, such as Figure 2 As shown, the horizontal direction represents the time domain, and the vertical direction represents the frequency domain. It includes a set of time-frequency resources for downlink (e.g., downlink data or downlink control information) transmission and a set of time-frequency resources for uplink (e.g., uplink data or uplink control information) transmission. The time domain range occupied by the time-frequency resources used for downlink transmission is called the downlink time slot (DL slot), and the time domain range occupied by the time-frequency resources used for uplink transmission is called the uplink time slot (UL slot).

[0093] 2. SBFD: To meet the needs of emerging services, the SBFD scheme was proposed. In the SBFD scheme, a carrier (e.g., a component carrier (CC)) is divided into multiple overlapping or non-overlapping subbands, and the transmission directions of different subbands can be different. For example, a carrier may include a non-overlapping first subband and a second subband, and the first and second subbands may have different transmission directions.

[0094] It should be noted that the first subband and the second subband refer to two types of subbands with different transmission directions, and do not mean that a carrier contains only two subbands. For example, a carrier may include subband #1 and subband #2, where subband #1 and subband #2 have different transmission directions. Alternatively, a carrier may include subband #1, subband #2, and subband #3, where subband #1 and subband #3 have the same transmission direction, and subband #1 and subband #2 have different transmission directions.

[0095] In this application, SBFD includes subband overlapping full duplex and subband non-overlapping full duplex.

[0096] To facilitate understanding, the following will be combined with... Figure 3 (a) and (b) briefly introduce the time-frequency division method in the SBFD scheme.

[0097] like Figure 3 As shown in (a) and (b), the horizontal direction represents the time domain, the vertical direction represents the frequency domain, DL represents downlink resources used for downlink data or control information transmission, and UL represents uplink resources used for uplink data or control information transmission. A time period consisting only of downlink resources is called a downlink time slot or downlink symbol; a time period consisting only of uplink resources is called an uplink time slot or uplink symbol; and a time period consisting of both downlink and uplink resources is called an SBFD time slot or SBFD symbol. In this application, an SBFD time slot, SBFD symbol, or time period representing both downlink and uplink resources can be referred to as an SBFD time unit.

[0098] 3. SBFD Time Unit: This includes uplink frequency resources and downlink frequency resources. The uplink frequency resources are used for uplink transmission, and the downlink frequency resources are used for downlink transmission. It can be understood that the SBFD time unit includes subbands for uplink and downlink transmission, and the base station can use these subbands to perform SBFD operations. In this embodiment, when the time unit is a symbol, the SBFD time unit is an SBFD symbol. When the time unit is a time slot, subframe, half-frame, frame, mini-subframe, mini-time slot, or transmission occasion (TO), the SBFD time unit can refer to a time unit containing an SBFD symbol.

[0099] It should be noted that the frequency domain resources on the SBFD time unit of this application may include downlink (DL) subbands and uplink (UL) subbands. To avoid cross-link interference between downlink transmissions on the DL subband and uplink transmissions on the UL subband, a guard band may be defined between the DL subband and the UL subband. This application does not limit whether a guard band exists between the DL subband and the UL subband, or whether transmission can be performed on the guard band if it exists. Furthermore, this application does not limit whether the DL subband and the UL subband can overlap (e.g., they may not overlap at all, or they may partially overlap, or they may completely overlap).

[0100] For example, regarding the configuration of SBFD, depending on whether a time slot contains both SBFD symbols and non-SBFD symbols, there are two possible configuration methods:

[0101] 1) SBFD configuration is at the time slot level, meaning that the symbols contained in a time slot are either all configured as SBFD symbols or all configured as non-SBFD symbols.

[0102] 2) SBFD configuration is symbol-level, meaning that some of the symbols contained in a time slot can be configured as SBFD symbols, while others can be configured as non-SBFD symbols.

[0103] In this context, the SBFD symbol can be considered as a symbol configured with SBFD, and the non-SBFD symbol can be considered as a symbol without SBFD. This application does not impose any limitations on the configuration of SBFD.

[0104] 4. Single Frequency Fullduplex (SFFD): This indicates that the entire Common Coordinated Access (CC) can be used simultaneously for transmission and reception within a single symbol or time slot. For example, a typical SFFD time-frequency partitioning scheme is as follows: Figure 4 As shown, the horizontal direction represents the time domain, and the vertical direction represents the frequency domain, including a set of time and frequency resources used simultaneously for downlink and uplink data or control information transmission.

[0105] 5. Subband: A portion of a frequency band within a carrier, i.e., one or more consecutive PRBs in the frequency domain. In this application, the subband used for uplink transmission is called the uplink subband, and the subband used for downlink transmission is called the downlink subband. A subband can also be understood as a frequency resource. Currently, base stations support FD (e.g., SBFD and SFFD mentioned above), meaning that in a single time slot, transmission can occur simultaneously on the uplink subband and reception on the downlink subband. Terminal equipment only supports half-duplex (HF) SBFD, meaning that in a single time slot, transmission can only occur on the uplink subband, or reception can only occur on the downlink subband.

[0106] 6. Time-frequency resources: In this embodiment, data or information can be carried by time-frequency resources. These time-frequency resources may include resources in the time domain (i.e., time-domain resources) and resources in the frequency domain (i.e., frequency-domain resources).

[0107] In the time domain, time-domain resources can include one or more time-domain units (or time units), and a time unit can include several time-domain resources. A time-domain unit is, for example, a radio frame (RF). The time-domain resources included within a time-domain unit can be, for example, a subframe, a frame, a half-subframe or half-frame, a slot, a mini-slot, a partial slot, or an OFDM symbol; alternatively, a time-domain unit may also be a collection of one or more time-domain resources, such as one or more OFDM symbols within a time slot, for example, the number of such one or more might be 6, 7, 12, or 14. One or more time units can be continuous or discrete in time. Furthermore, the duration of a time slot can be related to the sub-carrier space (SCS) interval. For example, when the subcarrier spacing is 15kHz, the duration of one time slot is 1 millisecond (ms); when the subcarrier spacing is 30kHz, the duration of one time slot is 0.5ms; and when the subcarrier spacing is 60kHz, the duration of one time slot is 0.25ms. Similarly, it can be deduced that when the subcarrier spacing is 15×2... μ At kHz, the duration of one time slot is 2. μ ms, μ = 0, 1, 2, ..., μ is a non-negative integer.

[0108] In the frequency domain, frequency domain resources can include one or more frequency domain units. A frequency domain unit can be a resource element (RE), a resource block (RB), a subchannel, a resource pool, a bandwidth, a bandwidth part (BWP), a carrier (CC), a channel, or an interlaced RB, etc.

[0109] 7. Random Access (RA): In a communication system, the terminal completes uplink time synchronization with the base station through a random access procedure and establishes an RRC connection with the base station. After the terminal and the base station establish an RRC connection, uplink and downlink service data transmission can be performed. In addition, before initiating uplink random access, the terminal must also detect and receive downlink synchronization signals sent by the base station to complete downlink time synchronization and frequency synchronization. The downlink synchronization signals generally include a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). For example, the PSS and SSS are carried in the SSB.

[0110] There are two types of random access procedures: Type-1 and Type-2. Type-1 is also known as a four-step random access procedure, and Type-2 is also known as a two-step random access procedure. Depending on whether there is a conflict in the transmission of the preamble between terminal devices, Type-1 and / or Type-2 RA procedures include contention-based random access (CBRA) and contention-free random access (CFRA) procedures. The CBRA and CFRA procedures are essentially the same. For ease of description, the following text uses CBRA as an example to introduce both Type-1 and Type-2 RA procedures.

[0111] Figure 5 A schematic flowchart of a four-step random access method is shown. Figure 5 The execution entity of the method shown can be a first communication device and a second communication device. The first communication device can be a terminal device, or a chip or circuit within the terminal device, or a functional module within the terminal device capable of calling and executing a program. The second communication device can be a network device, or a chip or circuit within the network device, or a CU or DU within the network device, or a functional module within the network device capable of calling and executing a program. Figure 5 As shown, the method includes the following steps.

[0112] S510, the first communication device sends a random access preamble to the second communication device.

[0113] Accordingly, the second communication device receives the random access preamble sent by the first communication device.

[0114] The first communication device randomly selects a random access occasion (RO) associated with the selected SSB index based on the received system message and the selected SSB index. Here, RO can be understood as the time-frequency resource used by the first communication device for random access. The second communication device pre-configures the association between RO and SSB index, and a certain RO is used to send a preamble, which is message 1 (message1, Msg1).

[0115] After determining the time-frequency resources (or ROs), the first communication device selects a Preamble sequence from the chosen ROs for transmission. It should be understood that a maximum of 64 Preambles can be transmitted simultaneously on a single RO, and the first communication device can choose one of these 64 Preamble sequences for transmission. Then, the first communication device sends the Preamble sequence to the second communication device; this Preamble sequence is carried by a PRACH.

[0116] S520, the second communication device sends a random access response (RAR) to the first communication device.

[0117] Accordingly, the first communication device receives the RAR from the second communication device.

[0118] After receiving the Preamble, the second communication device sends a Random Access Response (RAR) message to the terminal. The RAR message is message 2 (Msg2). The RAR message includes scheduling information such as allocation message 3 (Msg3), such as RAR uplink scheduling (UL grant) information.

[0119] After sending Msg1, the first communication device initiates a random access response window and listens for Msg2 sent by the network side within the window. If the first communication device successfully detects its own RAR, the random access is successful. The first communication device then continues to send Msg3 according to the instructions of the RAR. The main function of Msg3 is to send an RRC connection establishment request. If the first communication device does not receive its own RAR, the random access fails. The first communication device then re-initiates the random access process according to the fallback parameters indicated by the second communication device until the maximum number of random access attempts is reached.

[0120] S530, the first communication device sends Msg3 to the second communication device.

[0121] Accordingly, the second communication device receives Msg3 from the first communication device.

[0122] For example, the first communication device transmits Msg3 based on RAR. The main function of Msg3 is to send an RRC connection establishment request. Msg3 is transmitted on the time-frequency resources specified by Msg2 and is carried by the PUSCH channel.

[0123] S540, the second communication device sends message 4 (message4, Msg4) to the first communication device.

[0124] Accordingly, the first communication device receives Msg4 from the second communication device.

[0125] Msg4 is primarily used for conflict resolution. When multiple first communication devices connect simultaneously, it's necessary to determine which first communication device will be selected for the random access. Specifically, after sending Msg3, the first communication device listens for and receives Msg4 from the second communication device. Msg4 carries a conflict resolution flag and the air interface parameter configuration for that first communication device. If the first communication device successfully receives Msg4, the random access is successful; otherwise, it fails. If successful, the first communication device continues to send Msg5, which is mainly used to send the RRC establishment completion command. If it fails, the first communication device re-initiates the random access process according to the fallback parameters indicated by the second communication device until the maximum number of random access attempts is reached.

[0126] It should be noted that the above Figure 5 This diagram is provided merely to illustrate the four-step random access procedure and does not constitute any limitation on the scope of protection of this application. For a detailed description of the four-step random access procedure, please refer to the introduction in the relevant current technologies.

[0127] Figure 6 A schematic flowchart of a two-step random access procedure is shown. Figure 6 The execution entity of the method shown can be a first communication device and a second communication device. The first communication device can be a terminal device, or a chip or circuit within the terminal device, or a functional module within the terminal device capable of calling and executing a program. The second communication device can be a network device, or a chip or circuit within the network device, or a CU or DU within the network device, or a functional module within the network device capable of calling and executing a program. Figure 6 As shown, the method includes the following steps.

[0128] S610, the first communication device sends message A (message A, MsgA) to the second communication device.

[0129] Accordingly, the second communication device receives message A from the first communication device.

[0130] The MsgA includes a preamble portion and a physical uplink shared channel (PUSCH) portion. The preamble portion is transmitted on PRACH resources (such as RO as mentioned above), while the PUSCH resources can carry L2 or L3 information, such as BFR MAC CE or RRC connection establishment request messages.

[0131] S620, the second communication device sends message B (message B, MsgB) to the first communication device.

[0132] Accordingly, the first communication device receives message B from the second communication device.

[0133] The MsgB message can contain either a successful RAR or a fallback RAR.

[0134] For example, if the first communication device receives a fallback RAR, the first communication device needs to fall back to the four-step random access procedure and send Msg3 to the second communication device, that is, perform the above-mentioned procedure. Figure 5 Step S530.

[0135] Optionally, in addition to the fallback process from two-step random access to four-step random access described above, if the second communication device chooses to perform a two-step random access process when triggering random access, after the preamble of the two-step random access process reaches the maximum number of transmissions, the first communication device can also fallback to the four-step random access process to attempt access, thereby increasing the access success rate of the first communication device and ensuring the access performance of the first communication device.

[0136] 8. Random Access Occasion (RO): As mentioned earlier, the UE transmits a preamble sequence on the RO. An RO can be considered a time-frequency resource for transmitting the preamble. Multiple preamble sequences can be transmitted using code division multiplexing on a single RO, and an NR cell supports multiple ROs. Unlike LTE, NR introduces multi-beam operation; therefore, NR's random access process is beam-based. For example, for a UE in the initial access phase, transmission is primarily based on the SSB beam; for a UE in connected state, it can also be based on the CSI-RS beam. NR can support the base station transmitting SSBs in multiple beam directions. For example, in frequency range 1 (FR1), a maximum of 8 SSBs can be supported. The UE can select one of the SSBs and use that SSB beam to transmit the PRACH. Regarding how the UE selects the SSB to transmit PRACH, for example, if the base station does not configure a reference signal receiving power (RSRP) threshold, the UE can choose any SSB to transmit PRACH; otherwise, it can choose any SSB(s) that exceeds the RSRP threshold to transmit PRACH.

[0137] The number of contention-based (CB) preambles corresponding to each SSB is the same and is configured by the base station. For details, refer to the signaling CB-PreamblesPer SSB. For example, the number of CB preambles corresponding to each SSB is R. If there is only one SSB in a RO, the starting preamble index is 0, i.e., from 0 to R-1. If there are N SSBs in a RO, the starting preamble index corresponding to SSB index n is... That is, from arrive

[0138] For example, if a RO has two SSBs (with corresponding indices 0 and 1), the preamble index of SSB 0 starts from... The preamble index corresponding to R-1 (n=0); SSB 1 corresponds to... arrive (corresponding to n=1). Wherein, This is the total number of preambles, and the base station configuration must be a multiple of N. Assume... In RO, SSB1 corresponds to n=0, and SSB2 corresponds to n=1.

[0139] 9. PRACH Configuration: PRACH can be configured in the UL time slot through the RACH configuration of the general cell. New and old terminals can use the PRACH on the UL time slot for random access at the same time.

[0140] Figure 7 A schematic diagram of PRACH configuration on a UL time slot is shown. Figure 7 As shown, the horizontal axis represents the time domain, including SBFD and UL time slots, and the vertical axis represents the frequency domain. The dashed box in the UL time slot can represent PRACH resources. For example, the UE can use this PRACH for random access. For instance, the UE can look up the parameter prach-ConfigurationIndex carried in RACH-ConfigGeneric (e.g., Tables 6.3.3.2-2 to 6.3.3.2-4 in existing protocols (e.g., TS38211)) to obtain the period, frame number, subframe number, time slot number, and number of ROs in the time slot of the PRACH in the time domain, thus determining the time domain location of the PRACH. As another example, the UE can obtain the starting position and frequency division multiplexing (FDM) number of the PRACH in the frequency domain based on the parameters msg1-FrequencyStart and msg1-FDM carried in RACH-ConfigGeneric, thus determining the frequency domain location of the PRACH.

[0141] Figure 8 Figures (a) and (b) show schematic diagrams of the time-frequency resources of PRACH, as follows: Figure 8 As shown in (a), the top three squares in the diagram represent the radio frame containing the PRACH, and the time-domain distance between two adjacent squares is the PRACH period. The middle layer represents the 10 subframes contained in a radio frame containing a PRACH, such as subframes 0-9, where subframes 4 and 9 represent the subframe containing the PRACH. The bottom layer represents the time slot structure of subframe 4 containing the PRACH, which includes two PRACH slots (e.g., PRACH slot #1 and PRACH slot #2). Each small square represents one RO, meaning each PRACH slot contains 6 ROs. Figure 8 As shown in (b), the horizontal axis represents the time domain and the vertical axis represents the frequency domain. Each square represents one RO. The number of ROs can be 1, 2, 4 or 8. For example, ROs can be arranged starting from the frequency domain position specified by msg1-FrequencyStart.

[0142] 9. RO and SSB Association: During the Msg1 transmission process in step S510 above, the UE can select an RO to transmit the Preamble sequence based on the SSB index. Therefore, in the NR standard, in addition to specifying the PRACH location, the RO-SSB mapping relationship is also specified (one SSB index can be associated with multiple ROs, or multiple SSB indices can be associated with one RO). For example, the network device can configure the mapping relationship from N SSBs to 1 RO through the higher-layer parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB. When N is less than 1, 1 SSB is associated with 1 / N ROs; when N is greater than 1, N SSBs are associated with 1 RO (1 SSB is associated with 1 / N ROs).

[0143] Figure 9 Figures (a) to (c) illustrate the relationship between RO and SSB. Figure 9 As shown in (a), when N = 1 / 2, one SSB is associated with two ROs, as follows: Figure 9 As shown in (b), when N=2, one RO is associated with two SSBs. Therefore, when an SSB index is associated with multiple ROs, the UE can select one of the multiple ROs and choose the preamble sequence to be transmitted on that RO. Further, after determining the association between ROs and SSBs, the UE begins RO-SSB mapping, in the following order: frequency domain first, then time domain; first same slot, then same frame, and finally different frames. Figure 9 As shown in (c), where the horizontal axis represents the time domain and the vertical axis represents the frequency domain, the set of SSBs used by the base station can be {SSB}. i SSB i+1 SSB i+2 SSB i+3 When msg1-FDM = 4 and N = 1 / 4, one SSB is associated with four ROs, and the set of ROs is denoted as {RO0, RO1, RO2, RO3}. Sixteen ROs complete one complete RO-SSB mapping cycle. The mapping order of RO-SSBs can be arranged starting from the frequency domain corresponding to the time domain position of a certain RO, i.e., SSBs... i The corresponding RO0-RO3 occupy the first RO time-domain position of the first PRACH time slot of the same frame, corresponding to the four RO positions in the frequency domain, SSB i+1 The corresponding RO0-RO3 occupy the second RO time-domain position of the starting PRACH time slot, corresponding to the four RO positions in the frequency domain, SSB i+1 The corresponding RO0-RO3 occupy the second RO time-domain position in the first PRACH time slot of the same frame, corresponding to the four RO positions in the frequency domain, SSB i+2The corresponding RO0-RO3 occupy the first RO time-domain position of the second PRACH slot in the same frame, corresponding to the four RO positions in the frequency domain, SSB i+3 The corresponding RO0-RO3 occupy the second RO time domain position of the second PRACH time slot in the same frame, corresponding to the four RO positions in the frequency domain.

[0144] 10. Uplink and downlink time slot configuration

[0145] In 5G NR, the symbol direction configuration on a component carrier can be achieved in two ways: higher layer configuration (also known as RRC configuration) and downlink control information 2-0 (DCI2-0) dynamic indication (also known as slot format indicator (SFI) indication).

[0146] (1) In the high-level configuration scheme, network devices can notify terminal devices through RRC signaling to configure the symbol direction within a certain period. The high-level configuration scheme can be further divided into cell-level TDD-ConfigCommon and terminal device-level TDD-ConfigDedicated.

[0147] a. The information contained in TDD-ConfigCommon includes: the period of TDD-ConfigCommon, the number of downlink time slots in the period, the number of uplink time slots in the period, the number of downlink symbols in the period, and the number of uplink symbols in the period.

[0148] One implementation of TDD-ConfigCommon is as follows: Figure 10 As shown in (a) above. In this implementation, TDD-ConfigCommon is a single-cycle configuration. Reference Figure 10 In diagram (a), D represents downlink, F represents flexible, and U represents uplink. A time slot is 1ms long with a period of 5ms. Within the period, there are 3 downlink time slots and 1 uplink time slot. For time-frequency resources used for both uplink and downlink transmission, if there are 5 downlink symbols and 5 uplink symbols, the remaining unconfigured direction portion is flexible, consisting of 4 symbols. Based on the above configuration, the direction of all symbols within a period can be determined as downlink, flexible, or uplink.

[0149] Another implementation of TDD-ConfigCommon is as follows: Figure 10 As shown in (b) above, in this implementation, TDD-ConfigCommon is a two-cycle configuration. (See reference...) Figure 10In (b), a time slot is 1ms long. Pattern 1 has a period of 5ms, with 3 downlink time slots, 1 uplink time slot, 5 downlink symbols, and 5 uplink symbols within the period. The remaining unconfigured direction portion is flexible. Pattern 2 has a period of 5ms, with 2 downlink time slots, 2 uplink time slots, 0 downlink symbols, and 0 uplink symbols within the period. The remaining unconfigured direction portion is flexible.

[0150] b. TDD-ConfigDedicated is a terminal device-level configuration that can be configured individually for each terminal device. It can modify the direction of flexible symbols in TDD-ConfigCommon. Its main components are: the slot ID, the number of uplink symbols in that slot, and the number of downlink symbols.

[0151] (2) The SFI instruction scheme can be modified to allow for flexible symbol orientation after configuration via TDD-ConfigCommon and TDD-ConfigDedicated, as shown in the following implementation method. Figure 10 As shown in (c) in the figure.

[0152] refer to Figure 10 In (c), after TDD-ConfigCommon and TDD-ConfigDedicated are configured, time slots containing flexible symbols can be configured for each symbol direction via SFI instructions. Figure 10 In the left figure of (c), the symbol for time slot #0 is configured as downlink, and the symbols for time slots #1 to #4 are all configured as flexible time slots. Figure 10 In the right figure of (c), the symbols for slots #1 and #2 are changed to downlink, the symbol for slot #3 is changed to 10 downlink symbols, 2 flexible symbols, and 2 uplink symbols, and the symbol for slot #4 is changed to uplink.

[0153] In summary, the direction configuration of a symbol on a component carrier can be achieved through RRC configuration or SFI indication. It is worth noting that uplink and downlink slot configuration includes not only slot configuration but also symbol configuration.

[0154] The foregoing briefly introduced the application scenarios of the communication method provided in this application embodiment, and also introduced the basic concepts that may be involved in this application embodiment. Currently, network devices configure PRACH resources through the parameter PRACH configuration index. In the time domain, the PRACH period is obtained according to the PRACH configuration index, including the RO positions and formats within a period, such as which slots contain PRACH, how many PRACH slots a slot contains, how many ROs a PRACH slot contains, etc. In the frequency domain, network devices can configure at least one frequency division multiplexing RO in the frequency domain through the parameter msg1-FDM, such as configuring {1, 2, 4, 8} frequency division multiplexing ROs.

[0155] Similarly, PRACH resources can also be configured in SBFD slots or symbols based on the above method. For example, as follows: Figure 11 As shown, the horizontal direction represents the time domain, and the vertical direction represents the frequency domain. The solid box represents a PRACH resource specified by RACH-ConfigGeneric, located in both the flexible and UL time slots. The dashed box represents a PRACH resource specified by the PRACHconfiguration index, located in both the flexible and SBFD time slots. The two types of PRACH resources overlap in the flexible time slots, leading to SSB mapping conflicts and resource allocation conflicts. To handle this conflict, network devices need to perform complex processing. Advanced network devices with better hardware performance can support the simultaneous generation of multiple beams without affecting the random access of terminal devices. However, low-level network devices with poorer hardware performance do not have this capability, affecting the random access of terminal devices and consequently reducing their detection performance.

[0156] Based on this, this application provides a communication method that can reduce the impact of random access on terminal devices, thereby avoiding a decrease in the detection performance of terminal devices and improving communication quality.

[0157] It should be understood that the communication method provided in the embodiments of this application can be applied to systems that communicate using multi-antenna technology, for example, Figure 1 The communication system 100 shown may include at least one network device and at least one terminal device.

[0158] The communication between different devices involved in the embodiments of this application can refer to direct communication between different devices (i.e., without the need for relaying or forwarding by other devices), or communication between different devices through other devices (i.e., requiring relaying or forwarding by other devices), or communication between a functional unit within a device and other devices through another functional unit. In other words, "sending information to a terminal device" in this application can be understood as the destination of the information being the terminal device. This can include sending information directly or indirectly to the terminal device. "Receiving information from a network device" can be understood as the source of the information being the network device, and can include receiving information directly or indirectly from the network device. Information may undergo necessary processing between the source and destination, such as format changes, digital-to-analog conversion, amplification, filtering, etc., but the destination can understand the valid information from the source. Similar expressions in this application can be understood in a similar way, and will not be elaborated further here.

[0159] Figure 12 This is a schematic diagram of a communication method 1200 provided in an embodiment of this application. The communication method 1200 may include steps 1210-1230.

[0160] 1210. Configure a first PRACH resource and a second PRACH resource to the terminal device. The first PRACH resource includes PRACH resources located in the first flexible time domain unit and the SBFD time domain unit. The second PRACH resource includes PRACH resources located in the second flexible time domain unit and the UL time domain unit. The first flexible time domain unit and the second flexible time domain unit overlap in the time domain.

[0161] In this embodiment of the application, step 1210 can be executed by a network device, or by a module of the network device (e.g., a chip, chip system, or processor), or by a logical node, logical module, or software that can implement all or part of the functions of the network device.

[0162] It should be understood that, in the embodiments of this application, the overlap of the first flexible time domain unit and the second flexible time domain unit in the time domain can be understood as the first flexible time domain unit and the second flexible time domain unit completely overlapping in the time domain, or the first flexible time domain unit and the second flexible time domain unit partially overlapping in the time domain.

[0163] The following text combines Figure 13 This illustrates that the first and second flexible time-domain units overlap in the time domain. Taking a time-domain unit as an example, refer to... Figure 13 (a) to Figure 13 In embodiment (d), the first PRACH resource includes PRACH resources located in the first flexible time slot and the SBFD time slot, that is, the first PRACH resource is... Figure 13 (a) to Figure 13 The dashed box in (d) represents the PRACH resource. The second PRACH resource includes the PRACH resources of the second flexible time slot and the UL time slot, which is... Figure 13 (a) to Figure 13 The solid box in (d) represents the PRACH resource.

[0164] refer to Figure 13 In (a), the first flexible time slot corresponds to Figure 13 In (a) of the data, the second flexible time slot corresponds to the time period from t1 to t3. Figure 13 In (a) of the above, during the time period from t2 to t4, the first flexible time slot and the second flexible time slot overlap during the time period from t2 to t3, that is, the first flexible time slot and the second flexible time slot partially overlap in the time domain.

[0165] refer to Figure 13 In (b), the first flexible time slot corresponds to Figure 13 In (b) of the text, the second flexible time slot corresponds to the time period from t1 to t2. Figure 13 In (b) of the above, during the time period from t1 to t2, the first flexible time slot and the second flexible time slot overlap, that is, the first flexible time slot and the second flexible time slot completely overlap in the time domain.

[0166] refer to Figure 13 In (c), the first flexible time slot corresponds to Figure 13 In (c), the time intervals t1 to t2, t3 to t4, and t5 to t6 correspond to the second flexible time slot. Figure 13 In (c), during the time period from t3 to t4, the first flexible time slot and the second flexible time slot overlap, meaning that the first flexible time slot and the second flexible time slot partially overlap in the time domain.

[0167] refer to Figure 13 In (d), the first flexible time slot corresponds to Figure 13 In (d), the time intervals t1 to t2, t3 to t5, and t6 to t8 correspond to the second flexible time slot. Figure 13 In the time period from t4 to t7 in (d), the first flexible time slot and the second flexible time slot overlap in the time periods from t4 to t5 and from t6 to t7, that is, the first flexible time slot and the second flexible time slot partially overlap in the time domain.

[0168] in, Figure 13 (a) and Figure 13 The overlap in the time domain between the first and second flexible time-domain units shown in (b) can be termed continuous overlap. Figure 13 (c) and Figure 13The overlap of the first and second flexible time-domain units shown in (d) in the time domain can be called comb overlap or discrete overlap.

[0169] It should be noted that, in principle, both the first PRACH resource and the second PRACH resource can be used by the terminal device for random access. However, since the PRACH resources located in the first flexible time domain of the first PRACH resource and the PRACH resources located in the second flexible time domain of the second PRACH resource overlap in the time domain, this application redefines the resources in the overlapping part. This mainly involves redefining some or all of the PRACH resources located in the first flexible time domain. The redefined PRACH resources are not used for transmitting signals. Please refer to the following text for details.

[0170] 1220, Receive the first PRACH resource and the second PRACH resource configured by the network device.

[0171] 1230, transmit a signal according to the first PRACH resource or the second PRACH resource, wherein all or part of the PRACH resources on the first flexible time domain unit are not used for transmitting signals.

[0172] In this embodiment of the application, steps 1220 to 1230 can be executed by the terminal device, or by a module of the terminal device (e.g., a chip, chip system, or processor), or by a logic node, logic module, or software that can implement all or part of the functions of the terminal device.

[0173] For ease of description, the following text will consistently use terminal devices and network devices as examples. In the embodiments of this application, the signals sent by the terminal device according to the first PRACH resource or the second PRACH resource can be as described above. Figure 5 The preamble in the text.

[0174] In this embodiment of the application, the terminal device can send signals based on the first PRACH resource or the second PRACH resource.

[0175] 1. When the terminal device transmits a signal based on the first PRACH resource, all or part of the PRACH resources located in the first flexible time domain unit of the first PRACH resource are not used for signal transmission. When all the PRACH resources located in the first flexible time domain unit of the first PRACH resource are not used for signal transmission, the terminal device can use the PRACH resources located in the SBFD time domain unit of the first PRACH resource to transmit the signal, such as... Figure 14 (a) and Figure 14 As shown in (b) of the diagram. Taking the time-domain unit as the time slot as an example, where, Figure 14The left figure in (a) is a schematic diagram of a network device configuring a first PRACH resource that can be used to transmit signals to a terminal device. Figure 14 The right figure in (a) is a schematic diagram of the terminal device itself sending signals according to the first PRACH resource. (Compare) Figure 14 As can be seen from the left and right figures in (a) of the diagram, for the first PRACH resource, the terminal device can send signals based on the PRACH resources located in the SBFD time slot of the first PRACH resource, and not send signals for any of the PRACH resources located in the first flexible time slot of the first PRACH resource. Figure 14 (b) and Figure 14 Similar to (a) in the previous example, it will not be repeated here.

[0176] When a portion of the PRACH resources located in the first flexible time domain unit of the first PRACH resource is not used for signal transmission, the terminal device can transmit signals based on the PRACH resources located in the SBFD time domain unit and the PRACH resources located in the partial time domain unit of the first flexible time domain unit, such as... Figure 14 (c) and Figure 14 As shown in (d) in the diagram. Taking the time-domain unit as the time slot as an example, where, Figure 14 The left figure in (c) is a schematic diagram of a network device configuring the first PRACH resource that can be used to send signals to a terminal device. Figure 14 The right figure in (c) is a schematic diagram of the terminal device itself sending signals according to the first PRACH resource. (Compare) Figure 14 As can be seen from the left and right figures in (c) of the diagram, for the first PRACH resource, the terminal device can send signals based on the PRACH resource located in the SBFD time slot of the first PRACH resource. Some PRACH resources located in the first flexible time slot of the first PRACH resource do not send signals. However, for the other PRACH resources located in the first flexible time slot of the first PRACH resource, the terminal device can still send signals based on these other resources. Figure 14 (d) in Figure 14 Similar to (c) in the previous example, it will not be repeated here.

[0177] 2. When the terminal device transmits a signal according to the second PRACH resource, all resources in the second PRACH resource located on the second flexible time domain unit can be used to transmit the signal, as described above. Figure 14 (a) to Figure 14 (d) in the reference. Figure 14 In (a) of the example, taking the time domain unit as the time slot, the following is an example: Figure 14 The left figure in (a) is a schematic diagram of a network device configuring a second PRACH resource that can be used to transmit signals to a terminal device. Figure 14 The right figure in (a) is a schematic diagram of the terminal device itself sending signals according to the second PRACH resource. (Compare) Figure 14 As can be seen from the left and right figures in (a) of the second PRACH resource, the terminal device can still send signals based on the PRACH resources located in the second flexible time slot and the PRACH resources located in the UL time slot in the second PRACH resource.

[0178] It should be understood that in some possible implementations, for the second PRACH resource, all or part of the PRACH resources located on the second flexible time domain unit are not used for signal transmission. In other words, the terminal device can transmit signals based on the PRACH resources located on the UL time domain unit, or the terminal device can transmit signals based on a portion of the PRACH resources located on the second flexible time domain unit and the PRACH resources located on the UL time domain unit, without limitation.

[0179] In this embodiment, the terminal device transmits signals based on either the first PRACH resource or the second PRACH resource, and all or part of the PRACH resources in the first flexible time domain unit are not used for signal transmission. That is, for PRACH resources located in the first flexible time domain unit and PRACH resources located in the second flexible time domain unit, the terminal device can transmit signals based on part of the PRACH resources in the first flexible time domain unit and all of the PRACH resources in the second flexible time domain unit. Alternatively, the terminal device may not transmit signals using the PRACH resources in the first flexible time domain unit, but instead use all of the PRACH resources in the second flexible time domain unit for signal transmission. This embodiment essentially redefines the PRACH resources in the overlapping portion of the first and second PRACH resources, reducing the impact on random access of the terminal device, thereby avoiding a decrease in the detection performance of the terminal device and improving communication quality.

[0180] Furthermore, in this application embodiment, all or part of the PRACH resources on the first flexible time domain unit are not used for signal transmission, but this does not restrict the PRACH resources on the second flexible time domain unit from being used for signal transmission. It can be considered that the PRACH resources on the second flexible time domain unit can be used for signal transmission. This design can be compatible with the use of older terminal devices, thereby improving the diversity of scenarios applicable to the solution of this application.

[0181] Optionally, in one embodiment, if the SBFD symbol does not occupy the first flexible time domain unit, all resources in the PRACH resources located in the first flexible time domain unit are not used for signal transmission; or, if the SBFD symbol occupies the first flexible time domain unit, all or part of the resources in the PRACH resources located in the first flexible time domain unit are not used for signal transmission. The first PRACH resource is located in the first time-frequency resource, and the first time-frequency resource includes the SBFD symbol in the time domain.

[0182] It should be noted that the SBFD symbols in the embodiments of this application can be understood as time-domain resources that support SBFD operations. The SBFD symbols may include all symbols in the SBFD time-domain unit, or they may include all symbols in the SBFD time-domain unit and some or all symbols in the first flexible time-domain unit.

[0183] In this embodiment, whether all or part of the PRACH resources located in the first flexible time domain unit are not used for signal transmission is related to whether the SBFD symbol occupies the first flexible time domain unit. That is, whether all or part of the PRACH resources located in the first flexible time domain unit are not used for signal transmission is related to whether the SBFD symbol is in the first flexible time domain unit. Please refer to the following for details.

[0184] 1. The SBFD symbol does not occupy the first flexible time domain unit.

[0185] Refer to the above Figure 14 In (a) of the example, taking a time-domain unit as a time slot, the first time-domain resource includes the SBFD time slot and the first flexible time slot. The SBFD symbol occupies the SBFD time slot but not the first flexible time slot. Since the SBFD symbol does not occupy the first flexible time slot, all resources in the PRACH resource located on the first flexible time slot are not used for signal transmission, such as... Figure 14 In (a) of the figure on the right, all the dashed boxes are located in the SBFD time slot, so that the terminal device can send signals according to the PRACH resources located in the SBFD time slot in the first PRACH resource.

[0186] 2. SBFD symbols occupy the first flexible time domain unit.

[0187] Refer to the above Figure 14 In (b) of the example, taking a time-domain unit as a time slot, the first time-domain resource includes an SBFD time slot and a first flexible time slot. SBFD symbols occupy the first flexible time slot and all resources in the PRACH resources located in the first flexible time slot are not used for signal transmission, such as... Figure 14 In (b) of the diagram on the right, all the dashed boxes are located in the SBFD time slot, so that the terminal device can send signals according to the PRACH resources located in the SBFD time slot in the first PRACH resource.

[0188] Refer to the above Figure 14 (c) and Figure 14 In (d), taking a time-domain unit as a time slot as an example, the first time-domain resource includes the SBFD time slot and the first flexible time slot. SBFD symbols occupy the first flexible time slot and are used for signal transmission. Some resources within the PRACH resources located in the first flexible time slot are not used for signal transmission, such as... Figure 14 (c) or Figure 14 In (d) of the diagram on the right, part of the dashed box is located in the SBFD time slot and the other part is located in the first flexible time slot. Thus, the terminal device can send signals based on the PRACH resources of the first PRACH resource located in the SBFD time slot, or the terminal device can send signals based on a portion of the PRACH resources of the first PRACH resource located in the first flexible time slot.

[0189] In this embodiment, whether all or part of the PRACH resources located in the first flexible time domain unit are not used for signal transmission depends on whether the SBFD symbol occupies the first flexible time domain unit. Specifically, if the SBFD symbol does not occupy the first flexible time domain unit, all the PRACH resources located in the first flexible time domain unit are not used for signal transmission. This design is simpler and can reduce the complexity of the system. Alternatively, if the SBFD symbol occupies the first flexible time domain unit, all or part of the PRACH resources located in the first flexible time domain unit are not used for signal transmission. This design can improve the utilization rate of the PRACH resources located in the first flexible time domain unit, thereby reducing resource waste.

[0190] Optionally, in one embodiment, the SBFD symbol occupies all time domain units of the first flexible time domain unit; or, the SBFD symbol occupies a portion of the time domain units of the first flexible time domain unit.

[0191] In this embodiment, the time domain units occupied by the SBFD symbol in the first flexible time domain unit include all or part of the time domain units occupied by the SBFD symbol in the first flexible time domain unit. Taking a time domain unit as a time slot as an example, refer to the above. Figure 14 (b) or Figure 14 As can be seen from (c) above, the SBFD symbol occupies a portion of the first flexible time slot; refer to the above. Figure 14 As can be seen from (d) in the diagram, the SBFD symbol occupies all the time slots of the first flexible time slot.

[0192] It should be noted that, in the embodiments of this application, if the SBFD symbol occupies part of the first flexible time slot, it can be understood that the SBFD symbol occupies a flexible time slot that does not have a UL PRACH but cannot occupy a flexible time slot that has a UL PRACH. That is, this part of the time slot belongs to the first flexible time slot but does not belong to the second flexible time slot.

[0193] It should be understood that in this application, when an SBFD symbol occupies all or part of the time domain units of the first flexible time domain unit, the relationship between this and the fact that all or part of the PRACH resources on the first flexible time domain unit are not used for signal transmission is not one-to-one, but rather a one-to-many relationship. Specifically, if an SBFD symbol occupies all the time domain units of the first flexible time domain unit, then all or part of the PRACH resources on the first flexible time domain unit are not used for signal transmission; if an SBFD symbol occupies part of the time domain units of the first flexible time domain unit, then all or part of the PRACH resources on the first flexible time domain unit are not used for signal transmission.

[0194] In this embodiment, if the SBFD symbol occupies all or part of the time domain units of the first flexible time domain unit, then all or part of the PRACH resources located in the first flexible time domain unit are not used for signal transmission. That is, regardless of whether the SBFD symbol occupies all the time domain units of the first flexible time domain unit, this application designs that all or part of the PRACH resources located in the first flexible time domain unit are not used for signal transmission. This design can improve the utilization rate of the PRACH resources located in the first flexible time domain unit, thereby reducing resource waste.

[0195] Optionally, in one embodiment, both the first flexible time domain unit and the second flexible time domain unit include a third flexible time domain unit, and the PRACH resources located in the third flexible time domain unit in the first PRACH resources are unavailable.

[0196] In this embodiment, the third flexible time-domain unit can be understood as the time-domain resource of the overlapping portion in the time domain of the PRACH resources located on the first flexible time-domain unit and the PRACH resources located on the second flexible time-domain unit. Referring to the above... Figure 13 In (a), the third flexible time-domain unit corresponds to the time period t2 to t3 in the figure. Alternatively, refer to the above... Figure 13 In (b), the third flexible time-domain unit corresponds to the time period from t1 to t2 in the figure. Alternatively, refer to the above... Figure 13 In (c), the third flexible time-domain unit corresponds to the time period from t3 to t4 in the figure. Alternatively, refer to the above... Figure 13In (d), the third flexible time-domain unit corresponds to the time periods t4 to t5 and t6 to t7 in the figure. In other words, the third flexible time-domain unit is the time-domain unit that overlaps with the first and second flexible time-domain units in the time domain.

[0197] In this embodiment, both the first flexible time domain unit and the second flexible time domain unit include a third flexible time domain unit, and the PRACH resources located in the third flexible time domain unit within the first PRACH resources are unavailable. In other words, the terminal device cannot perform random access based on the PRACH resources located in the third flexible time domain unit within the first PRACH resources. The following description, in conjunction with... Figure 13 (a) to Figure 13 The (d) in the text will be explained separately.

[0198] As mentioned above, for Figure 13 In (a) of the diagram, the third flexible time domain unit corresponds to the time period from t2 to t3. Therefore, the terminal device cannot perform random access based on the PRACH resources in the first PRACH resource located in the time period from t2 to t3. In other words, the terminal device cannot perform random access based on the PRACH resources in the first PRACH resource located in the time period from t2 to t3. However, the terminal device can perform random access based on the PRACH resources in the second PRACH resource located in the time period from t2 to t3.

[0199] for Figure 13 In (b) of the diagram, the third flexible time domain unit corresponds to the time period from t1 to t2. In this case, the terminal device cannot perform random access based on the PRACH resources in the first PRACH resource located in the time period from t1 to t2. In other words, the terminal device cannot perform random access based on the PRACH resources in the first PRACH resource located in the time period from t1 to t2. However, the terminal device can perform random access based on the PRACH resources in the second PRACH resource located in the time period from t1 to t2.

[0200] for Figure 13 In (c), the third flexible time domain unit corresponds to the time period t3 to t4 in the figure. Therefore, the terminal device cannot perform random access based on the PRACH resources in the first PRACH resources located in the time period t3 to t4. In other words, the terminal device cannot perform random access based on the PRACH resources in the first PRACH resources located in the time period t3 to t4. However, the terminal device can perform random access based on the PRACH resources in the second PRACH resources located in the time period t3 to t4.

[0201] for Figure 13In (d) of the diagram, the third flexible time domain unit corresponds to the time periods t4 to t5 and t6 to t7. Therefore, the terminal device cannot perform random access based on the PRACH resources in the first PRACH resource located in the time periods t4 to t5 and t6 to t7. In other words, the terminal device cannot perform random access based on the PRACH resources in the first PRACH resource located in the time periods t4 to t5 and t6 to t7. However, the terminal device can perform random access based on the PRACH resources in the second PRACH resource located in the time periods t4 to t5 and t6 to t7.

[0202] In this embodiment, both the first flexible time domain unit and the second flexible time domain unit include a third flexible time domain unit, and the PRACH resources located in the third flexible time domain unit within the first PRACH resources are unavailable. That is, for the third flexible time domain unit, the terminal device cannot perform random access based on the PRACH resources located in the third flexible time domain unit within the first PRACH resources, but the terminal device can perform random access based on the PRACH resources located in the third flexible time domain unit within the second PRACH resources. Especially when multiple terminal devices are performing random access, this avoids conflicts that occur when different terminal devices simultaneously select PRACH resources in the third flexible time domain unit for random access, thereby improving the success rate of random access for the terminal device.

[0203] The following text combines Figure 15 The description describes how terminal devices perform random access based on the above implementation method. Figure 15 The method shown includes steps 1510 to 1530.

[0204] 1510, The network device sends an SSB signal and system message 1.

[0205] In this embodiment of the application, the network device can broadcast SSB signals and system message 1. The system message 1 may include random access information, which is used to indicate parameters such as the time-frequency position of the PRACH resource, the preamble format, the transmission power, and the retransmission configuration information.

[0206] 1520. Determine the target SSB based on the SSB signal, and determine the position and parameters of multiple SBFD PRACHs based on system message 1.

[0207] After receiving the SSB signal, the terminal device can determine the target SSB and its index from multiple SSBs. The target SSB can be an SSB whose RSRP is higher than the SSB RSRP threshold broadcast in System Message 1 (SIB1). Based on System Message 1 and the definition rules for time-domain overlapping resources in the first and second PRACH resources in method 1200 described above, the terminal device determines the locations and related parameters of multiple SBFD PRACHs.

[0208] 1530, send a preamble according to the SBFD PRACH associated with the target SSB.

[0209] The terminal device randomly selects a RO in the SBFD PRACH associated with the determined SSB index. Then, the terminal device selects a Preamble sequence from the selected RO and sends the Preamble sequence to the network device according to the transmission power in system message 1.

[0210] As mentioned above, the first PRACH resource includes PRACH resources located in the first flexible time domain unit and the SBFD time domain unit. For the first PRACH resource, the frequency division multiplexing RO or time division multiplexing RO in the resource is invalid. The following will explain the different cases.

[0211] Scenario 1:

[0212] Optionally, in some embodiments, the communication method 1200 further includes: receiving first information from a network device, the first information being used to indicate that Y frequency division multiplexing ROs out of M1 frequency division multiplexing random access timing ROs are invalid, where M1 is an integer greater than 0 and Y is an integer greater than 0 and less than or equal to M1.

[0213] refer to Figure 16 , Figure 16 The white dashed box shown represents the first PRACH resource. Assuming this first PRACH resource includes M1 frequency division multiplexing (FDM) ROs, the first information can indicate that Y FDM ROs are invalid, as shown by the black box in the figure. Therefore, the terminal device cannot perform random access on these Y FDM ROs. Even if the terminal device attempts random access on these Y FDM ROs, the random access process is considered invalid. In some possible implementations, Y can be an integer greater than 0 and less than M1.

[0214] In an NR system, a frequency division multiplexing (RFD) RO can contain 64 random access preambles. Up to eight such RFD ROs can be arranged simultaneously in the frequency domain and are continuously distributed in the frequency domain.

[0215] In this embodiment, if all M1 frequency division multiplexing (FDM) ROs are valid, the network device can send a first message to the terminal device, which indicates that 0 of the M1 FDM ROs are invalid; alternatively, the network device may not send the first message to the terminal device; this can be understood as Y being 0. Whether the network device sends the first message indicating that 0 FDM ROs are invalid, or the network device does not send the first message, the terminal device can consider that the M1 FDM ROs in the first PRACH resource are valid.

[0216] In this embodiment, M1 can be configured by the network device or specified by the protocol, and is not limited thereto. If the network device configures M1 frequency division multiplexing (RFD) ROs to the terminal device, the network device can configure it through the parameter msg 1-FDM.

[0217] In this embodiment of the application, the network device sends first information to the terminal device. The first information is used to indicate that Y frequency division multiplexing ROs among M1 frequency division multiplexing ROs are invalid. This means that these Y frequency division multiplexing ROs are not used for random access, so the frequency domains corresponding to these Y frequency division multiplexing ROs are idle. The frequency domains corresponding to these Y frequency division multiplexing ROs can be used for the transmission of other data, thereby improving the efficiency of data transmission.

[0218] Optionally, in some embodiments, the Y frequency division multiplexing ROs satisfy the following: the distance between the first PRACH resource and the PDSCH resource is less than or equal to N frequency domain units, where N is an integer greater than 0 and less than a preset value.

[0219] The frequency domain units in the embodiments of this application include RB, RE, sub-channel, bandwidth, bandwidth portion, carrier, etc.

[0220] Taking the frequency domain unit as RB as an example, the PDSCH resource is Figure 16 The time-frequency resources used for downlink transmission, for the first PRACH resource, the frequency division multiplexing RO of the PRACH resource whose distance from the PDSCH resource is less than or equal to N RBs is invalid, as shown in the black box in the figure.

[0221] The preset values ​​in the embodiments of this application can be configured by the network device or specified by the protocol, and are not limited thereto.

[0222] As mentioned above, network devices can configure {1, 2, 4, 8} frequency division multiplexing (FDM) ROs in the frequency domain using the parameter msg1-FDM. When a network device configures {1, 2, 4, 8} FDM ROs in the frequency domain, the value range of N in this embodiment can be the set {0, 1, 2, 3, 4, 5, 6, 7, 8}, or the value range of N can be a subset of the set {0, 1, 2, 3, 4, 5, 6, 7, 8}, such as subsets {1, 2, 3, 4}, {0, 4, 5, 6, 7, 8}, etc.

[0223] When the value of N is the set {0, 1, 2, 3, 4, 5, 6, 7, 8}, the preset value in this embodiment is 8; when the value of N is a subset of the set {0, 1, 2, 3, 4, 5, 6, 7, 8}, such as the subset {1, 2, 3, 4}, the preset value in this embodiment is 4.

[0224] It is understandable that for PRACH resources in the first PRACH resource whose distance from the PDSCH resource is less than or equal to N RBs, the close frequency domain distance between these resources may lead to cross-link interference (CLI) of the SBFD PRACH affecting detection performance. This application designs the invalidation of Y frequency division multiplexing ROs of PRACH resources in the first PRACH resource whose distance from the PDSCH resource is less than or equal to N frequency domain units. This can reduce the impact of CLI of the SBFD PRACH on detection performance, thereby improving detection accuracy and ultimately enhancing communication quality.

[0225] It should be noted that if Y frequency division multiplexing (FDM) ROs satisfy the condition that the distance between the second PRACH resource and the PDSCH resource is less than or equal to N frequency domain units, resulting in the unavailability of some PRACH resources in the second PRACH resource, while some older terminal devices can still perform random access on the second PRACH resource, then limiting the Y FDM ROs to PRACH resources in the second PRACH resource that satisfy the above condition would not be compatible with these older terminal devices. Therefore, this application limits the Y FDM ROs to ROs in the first PRACH resource that satisfy the above condition, which can ensure compatibility with the use of older terminal devices and thus improve the diversity of applicable scenarios for this application's solution.

[0226] Alternatively, in some embodiments, N is indicated by signaling.

[0227] In this embodiment, the network device can indicate N through the newly added signaling in SIB1. In 5G NR, SIB1 carries messages used to assess whether the terminal device is allowed to access the cell, as well as scheduling information for other system information. SIB1 also provides general radio resource configuration information for the terminal device and restriction information required by unified access control (UAC). SIB1 is transmitted through the broadcast control channel (BCCH) in transmission mode (TM).

[0228] In this embodiment, N is indicated by signaling. For example, if the network device uses the newly added signaling indication N in SIB1, it can use the existing message indication N, thereby simplifying the design, reducing the number of message transmissions of the network device, and reducing the complexity of the system.

[0229] Optionally, in some embodiments, M1 bits correspond one-to-one with indicating the invalidity of M1 frequency division multiplexing (FDM) ROs; or, M1 bits indicate 2 M1 2 indexes M1 Each index corresponds to an invalid case of M1 frequency division multiplexing (RO).

[0230] In this embodiment of the application, the invalidity of M1 frequency division multiplexing ROs can be indicated by M1 bits, specifically in two ways.

[0231] Method 1: M1 bits are used to indicate the invalidity of M1 frequency division multiplexing (FDM) ROs.

[0232] For example, a network device configures four frequency division multiplexing (FDM) ROs to a terminal device, with four bits corresponding to each of these four FDM ROs. Assuming 0 represents an invalid FDM RO and 1 represents an invalid FDM RO, if the network device sends the bit 1100 to the terminal device to indicate the four FDM ROs, it means that two of the four FDM ROs are valid and the other two are invalid.

[0233] In this embodiment, the four bits indicate the four frequency division multiplexing (FDM) ROs in descending frequency order, or in ascending frequency order. The following description uses four bits in descending frequency order to indicate the four FDM ROs. (See reference...) Figure 17If the network device sends a bit of 1100 to the terminal device to indicate the four frequency division multiplexing (FDM) ROs, it means that the two higher frequency FDM ROs are valid and the two lower frequency FDM ROs are invalid. In other words, the top two FDM ROs are valid and the bottom two FDM ROs are invalid.

[0234] For example, a network device configures eight Frequency Division Multiplexing (FDM) ROs to a terminal device, with each of the eight ROs indicated by a corresponding bit. Assuming 0 represents an invalid FDM RO and 1 represents an valid FDM RO, if the network device sends the bit 11110000 to the terminal device to indicate four FDM ROs, it means that four of the eight FDM ROs are valid, and the other four are invalid. Similarly, using eight bits in descending frequency order to indicate the eight FDM ROs, if the network device sends the bit 11110000 to the terminal device to indicate the eight FDM ROs, it means that the four higher-frequency FDM ROs are valid, and the four lower-frequency FDM ROs are invalid.

[0235] Method 2: M1 bits indicate 2 M1 indexes

[0236] M1 frequency division multiplexing RO corresponds to 2 M1 In the case of invalidity, taking M1 as 4 as an example, the 4 frequency division multiplexing ROs correspond to 2 4 = 16 cases, then these 16 cases correspond to 16 indices, which can be indicated by 4 bits. The specific correspondence is shown in Table 1.

[0237] Table 1

[0238] index Bit pattern 0000 0000 0001 0001 0010 0010 0011 0011 0100 0100 0101 0101 0110 0110 0111 0111 1000 1000 1001 1001 1010 1010 1011 1011 1100 1100 1101 1101 1110 1110 1111 1111

[0239] It should be understood that the relationship between the index and the bit pattern in Table 1 above is only for illustrative purposes and should not impose any special limitations on this application.

[0240] For example, when a network device configures four frequency division multiplexing (FDM) ROs to a terminal device, four bits indicate 16 indices, which correspond to the invalidity of these four FDM ROs. Assuming 0 represents an invalid FDM RO and 1 represents a valid FDM RO, if the network device sends the terminal device a bit of 0000 to indicate that all four FDM ROs are invalid, it means that all four FDM ROs are invalid. If the network device sends the terminal device a bit of 0111 to indicate that one of the four FDM ROs is invalid, and the other three are valid.

[0241] Similarly, these 4 bits indicate the 4 frequency division multiplexing (FDM) ROs in descending frequency order, or in ascending frequency order. The following section uses 4 bits in descending frequency order to indicate the 4 FDM ROs. (Reference) Figure 18 If the network device sends the bit 0111 to the terminal device to indicate the four frequency division multiplexing (FDM) ROs, it means that the higher frequency FDM RO is invalid and the three lower frequency FDM ROs are valid. That is, the upper FDM RO is invalid and the lower three FDM ROs are valid.

[0242] Taking M1 as an example, the two frequency division multiplexing ROs correspond to 2 2 = There are 4 cases, and these 4 cases correspond to 4 indices, which can be indicated by 4 bits. The specific correspondence is shown in Table 2.

[0243] Table 2

[0244] index Bit pattern 00 00 01 01 10 10 11 11

[0245] For example, when a network device configures two frequency division multiplexing (FDM) ROs to a terminal device, two bits indicate four indices, which correspond to the invalidity of these two FDM ROs. Assuming 0 represents an invalid FDM RO and 1 represents a valid FDM RO, if the network device sends the bit 0000 to the terminal device to indicate the two FDM ROs, it means that all FDM ROs in these two FDM ROs are invalid. If the network device sends the bit 01 to the terminal device to indicate the two FDM ROs, it means that one FDM RO is invalid and the other is valid.

[0246] Similarly, two bits are used to indicate the two frequency division multiplexing (FDM) ROs in descending order of frequency. If the network device sends a bit of 0 or 1 to the terminal device to indicate the two FDM ROs, it means that the higher-frequency FDM RO is invalid and the lower-frequency FDM RO is valid.

[0247] It should be understood that the relationship between the indices and bit patterns in Table 1 or Table 2 above is merely illustrative and should not impose any particular limitations on this application.

[0248] In some implementations, an additional 8 bits can be added to SIB1 to indicate the invalidity of at least one frequency division multiplexing (FDM) RO configured by the network device for the terminal device.

[0249] When a network device configures eight Frequency Division Multiplexing (FDM) ROs to a terminal device, these eight bits can be used to indicate the invalidity of each of the eight FDM ROs. For example, when the network device sends the bit 00110000 to the terminal device to indicate the eight FDM ROs, it means that six of the eight FDM ROs are invalid, and the other two are valid. The eight bits are used to indicate the eight FDM ROs in descending frequency order. When the network device sends the bit 00110000 to the terminal device to indicate the eight FDM ROs, it means that the two higher-frequency FDM ROs are invalid, the four lower-frequency FDM ROs are invalid, and the two middle FDM ROs are valid.

[0250] When a network device configures fewer than 8 Frequency Division Multiplexing (FDM) ROs to a terminal device, some bits in these 8 bits indicate that at least one FDM RO is invalid, while the other bits are set to 0. For example, when a network device configures 4 FDM ROs to a terminal device, the first 4 bits are used to indicate that these 4 FDM ROs are invalid, and the last 4 bits are all set to 0. If the network device sends the bit 00110000 to the terminal device to indicate the 4 FDM ROs, it means that 2 of the 4 FDM ROs are invalid, and the other 2 are valid. The 4 bits are used to indicate the 4 FDM ROs in descending frequency order. When the network device sends the bit 00110000 to the terminal device to indicate the 4 FDM ROs, it means that the 2 FDM ROs with higher frequencies are invalid, and the 2 FDM ROs with lower frequencies are valid.

[0251] In this embodiment, M1 bits can indicate the invalidity of M1 frequency division multiplexing (FDM) ROs. Specifically, each of the M1 bits corresponds to one of the invalidity of the M1 FDM ROs; or, the M1 bits indicate 2 M1 2 indexes M1 Each index corresponds to an invalid case of M1 frequency division multiplexing (FDM) ROs. The terminal device can determine the invalid cases of M1 FDM ROs based on M1 bits, so that the terminal device can avoid random access in invalid ROs, thereby improving the success rate of random access.

[0252] Scenario 2:

[0253] Optionally, in some embodiments, the communication method 1200 further includes: second information for indicating that K time-division multiplexed ROs among M2 time-division multiplexed ROs are invalid, the K time-division multiplexed ROs include ROs of the first time-domain unit in the first PRACH resource, M2 is an integer greater than 0, and K is an integer greater than 0 and less than or equal to M2.

[0254] refer to Figure 19 , Figure 19 The white dashed box shown represents the first PRACH resource. Assuming this first PRACH resource includes M² time-division multiplexed ROs, the second information can indicate that K time-division multiplexed ROs are invalid, as shown by the black box in the figure. Therefore, the terminal device cannot perform random access on these K time-division multiplexed ROs. Even if the terminal device attempts random access on these K time-division multiplexed ROs, the random access process is considered invalid. In some possible implementations, K can be an integer greater than 0 and less than M².

[0255] Among them, the K time-division multiplexed ROs can be in continuous time-domain resources, such as Figure 19 As shown in (a); or, K time-division multiplexed ROs can be used in non-contiguous time-domain resources, such as Figure 19 (b) or Figure 19 As shown in (c) in the table; no restrictions apply.

[0256] In this embodiment, M2 can be configured by the network device or specified by the protocol, and is not limited thereto. If the network device configures M2 time-division multiplexing ROs to the terminal device, the network device can configure it through the parameter msg 1-FDM.

[0257] In this embodiment, if all M2 time-division multiplexed ROs are valid, the network device can send a second message to the terminal device, whereby the first message indicates that 0 of the M2 time-division multiplexed ROs are invalid; alternatively, the network device may not send the second message to the terminal device; here, K can be understood as 0. Whether the network device sends the second message indicating that 0 time-division multiplexed ROs are invalid, or the network device does not send the second message, the terminal device can consider that the M2 time-division multiplexed ROs in the first PRACH resource are valid.

[0258] It should be noted that if the K time-division multiplexed ROs include ROs of a certain time-domain unit in the second PRACH resource, causing some PRACH resources in the second PRACH resource to become unavailable, while some older terminal devices can still perform random access on the second PRACH resource, then limiting the K time-division multiplexed ROs to include ROs of a certain time-domain unit in the second PRACH resource would not be compatible with these older terminal devices. Therefore, this application limits the K time-division multiplexed ROs to include ROs of the first time-domain unit in the first PRACH resource. This ensures compatibility with the use of older terminal devices, thereby improving the diversity of scenarios applicable to the solution of this application.

[0259] In this embodiment of the application, the network device sends a second message to the terminal device. The second message is used to indicate that K of the M2 time-division multiplexed ROs are invalid, which is equivalent to these K time-division multiplexed ROs not being used for random access. As a result, the time domains corresponding to these K time-division multiplexed ROs are idle, and the time domains corresponding to these K time-division multiplexed ROs can be used for the transmission of other data, thereby improving the efficiency of data transmission.

[0260] Optionally, in some embodiments, M2 bits correspond one-to-one with indicating the invalidity of M2 time-division multiplexed ROs; or, M2 bits indicate 2 M2 2 indexes M2 Each index corresponds to an invalid case of M2 time-division multiplexing ROs.

[0261] In this embodiment of the application, the invalidity of K time-division multiplexed ROs can be indicated by M2 bits, specifically in two ways.

[0262] Method 1: M2 bits are used to indicate the invalidity of M2 time-division multiplexing ROs.

[0263] For example, a network device configures four time-division multiplexing origins (ROs) to a terminal device, with four bits corresponding one-to-one to indicate these four ROs. Assuming 0 represents an invalid RO and 1 represents an effective RO, if the network device sends the bit 1100 to the terminal device to indicate the four ROs, it means that two of the four ROs are effective and the other two are invalid.

[0264] In this embodiment, the four bits indicate the four time-division multiplexed origins (ROs) in chronological order from earliest to latest, or in chronological order from latest to earliest. The following description uses four bits in chronological order to indicate the four time-division multiplexed ROs. (See references.) Figure 20 If a network device sends a bit of 1100 to a terminal device to indicate the four time-division multiplexed ROs, it means that the first two ROs are valid and the last two ROs are invalid.

[0265] For example, a network device configures eight time-division multiplexing (TDM) ROs to a terminal device, with each of the eight ROs indicated by a corresponding bit. Assuming 0 represents an invalid TDM RO and 1 represents an valid TDM RO, if the network device sends the bit 11110000 to the terminal device to indicate the eight TDM ROs, it means that four of the eight TDM ROs are valid, and the other four are invalid. Similarly, using eight bits in chronological order to indicate the eight TDM ROs, if the network device sends the bit 11110000 to the terminal device to indicate the eight TDM ROs, it means that the first four TDM ROs are valid, and the last four are invalid.

[0266] Method 2: M2 bits indicate 2 M2 indexes

[0267] M2 time-division multiplexed ROs correspond to 2 M2 In the case of invalidation, taking M2 as an example of 4, the 4 time-division multiplexing ROs correspond to 2 4 = 16 cases, then these 16 cases correspond to 16 indices, which can be indicated by 4 bits. The specific correspondence is shown in Table 1 above.

[0268] For example, when a network device configures four time-division multiplexing origins (ROs) to a terminal device, four bits indicate 16 indices, which correspond to the invalidity of these four ROs. Assuming 0 represents an invalid RO and 1 represents a valid RO, if the network device sends the bit 0000 to the terminal device to indicate the four ROs, it means all four ROs are invalid. If the network device sends the bit 0111 to the terminal device to indicate the four ROs, it means one RO is invalid, and the other three are valid.

[0269] Similarly, these 4 bits indicate the 4 time-division multiplexed ROs in chronological order from earliest to latest, or in chronological order from latest to earliest. The following section uses 4 bits in chronological order to indicate the 4 time-division multiplexed ROs. (Reference) Figure 21 When a network device sends a bit of 0111 to a terminal device to indicate the four time-division multiplexed ROs, it means that the first RO is invalid and the last three ROs are valid.

[0270] For example, when a network device configures two time-division multiplexing origins (ROs) for a terminal device, two bits indicate four indices, which correspond to the invalidity of these two ROs. Still assuming 0 represents an invalid RO and 1 represents a valid RO, if the network device sends the bit 0000 to the terminal device to indicate the two ROs, it means that all of the two ROs are invalid. If the network device sends the bit 01 to the terminal device to indicate the two ROs, it means that one of the two ROs is invalid, and the other is valid.

[0271] Similarly, two bits are used to indicate the two time-division multiplexed ROs in chronological order from earliest to latest. When the network device sends a bit of 0 or 1 to the terminal device to indicate the two time-division multiplexed ROs, it means that the first time-division multiplexed RO is invalid and the second time-division multiplexed RO is valid.

[0272] In some implementations, an additional 8 bits can be added to SIB1 to indicate the invalidity of at least one time-division multiplexing RO configured by the network device for the terminal device.

[0273] When a network device configures eight time-division multiplexing (TDM) ROs to a terminal device, these eight bits can be used to indicate the invalidity of each of the eight TDM ROs. For example, when the network device sends the bit 00110000 to the terminal device to indicate the eight TDM ROs, it means that six of the eight TDM ROs are invalid, and the other two are valid. The eight bits are used to indicate the eight TDM ROs in chronological order. When the network device sends the bit 00110000 to the terminal device to indicate the eight TDM ROs, it means that the two earlier TDM ROs are invalid, the four later TDM ROs are invalid, and the two in the middle are valid.

[0274] When a network device configures fewer than 8 time-division multiplexing origins (ROs) to a terminal device, some bits in these 8 bits indicate that at least one RO is invalid, while the other bits are set to 0. For example, when a network device configures 4 ROs to a terminal device, the first 4 bits are used to indicate the invalidity of these 4 ROs, and the last 4 bits are all set to 0. If the network device sends the bit 00110000 to the terminal device to indicate the 4 ROs, it means that 2 of the 4 ROs are invalid, and the other 2 are valid. Alternatively, the 4 bits can be used to indicate the 4 ROs in ascending order of time. When the network device sends the bit 00110000 to the terminal device to indicate the 4 ROs, it means that the 2 ROs with earlier timestamps are invalid, and the 2 ROs with later timestamps are valid.

[0275] In this embodiment, M2 bits correspond one-to-one with indicating the invalidity of M2 time-division multiplexing ROs; or, M2 bits indicate 2 M2 2 indexes M2 Each index corresponds to an invalid case of M2 time-division multiplexing ROs. The terminal device can determine the invalid case of M2 time-division multiplexing ROs based on M2 bits, so that the terminal device can avoid random access in invalid ROs, thereby improving the success rate of random access.

[0276] It should be noted that the values ​​shown in the above embodiments are merely illustrative examples and may be other values, and should not impose any particular limitation on this application.

[0277] The above describes the communication method provided in the embodiments of this application. The above communication method is mainly described from the perspective of the terminal device. It is understood that, in order to implement the above functions, the terminal device includes the corresponding hardware structure and / or software modules for executing each function.

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

[0279] It should be understood that in the above embodiments, the terminal device can execute some or all of the steps in each embodiment. These steps or operations are merely examples, and other operations or variations thereof can also be performed in the embodiments of this application. Furthermore, the steps can be executed in different orders as presented in the embodiments, and it is not necessary to execute all the operations in the embodiments of this application. Moreover, the sequence number of each step does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0280] The following, combined with Figures 22 to 23 This application describes the communication device provided in the embodiments. It should be understood that the description of the device embodiments corresponds to the description of the method embodiments. Therefore, for content not described in detail, please refer to the above method embodiments. For the sake of brevity, some content will not be repeated.

[0281] Figure 22 A possible exemplary block diagram of the communication device involved in an embodiment of this application is shown. For example... Figure 22 As shown, the communication device 2200 may include modules or units for implementing the methods described in the embodiments above. In one possible implementation, the communication device 2200 includes a communication unit 2210. Optionally, the communication device 2200 may further include a processing unit 2220 for processing relevant information. Optionally, the communication device 2200 may further include a storage unit 2230 for storing device program code and / or data.

[0282] The communication device 2200 can be a terminal-side device as described in the above embodiments, such as a terminal or a communication module in a terminal, or a circuit or chip in a terminal responsible for communication functions. The device 2200 can be used to perform the actions performed by the terminal device in the above method embodiments. The communication unit 2210 is used to perform information transmission-related operations on the terminal device side in the above method embodiments, and the processing unit 2220 is used to perform processing-related operations on the terminal device side in the above method embodiments.

[0283] For example, in one embodiment, the communication unit 2210 is configured to: receive a first physical random access channel (PRACH) resource and a second PRACH resource configured by the network device, wherein the first PRACH resource includes PRACH resources located in a first flexible time domain unit and a sub-band full-duplex (SBFD) time domain unit, and the second PRACH resource includes PRACH resources located in a second flexible time domain unit and an uplink UL time domain unit, wherein the first flexible time domain unit and the second flexible time domain unit overlap in the time domain; and transmit a signal according to the first PRACH resource or the second PRACH resource, wherein all or part of the PRACH resources in the first flexible time domain unit are not used for transmitting signals.

[0284] For a more detailed description of the communication unit 2210, please refer to the relevant description in the above method embodiments, which will not be repeated here.

[0285] In one possible design, when the communication device 2200 is a terminal device or a communication module within a terminal device, the functionality of the processing unit 2220 can be implemented by one or more processors. Specifically, the processor may include a modem chip, or a system-on-a-chip (SoC) chip or a SIP chip containing a modem core. The functionality of the communication unit 2210 can be implemented by transceiver circuitry.

[0286] In one possible design, when the communication device 2200 is a circuit or chip responsible for communication functions in a terminal device, such as a modem chip or a system-on-a-chip (SoC) or SIP chip containing a modem core, the function of the processing unit 2220 can be implemented by a circuit system in the aforementioned chip that includes one or more processors or processor cores. The function of the communication unit 2210 can be implemented by the interface circuitry or data transceiver circuitry on the aforementioned chip.

[0287] It is understood that the division of units in the above-described device is merely a logical functional division. Each function can correspond to a functional unit, or two or more functions can be integrated into one functional unit. In actual implementation, all or some units can be integrated into a single physical entity, or they can be distributed across different physical entities. Furthermore, the aforementioned functional units can be implemented in hardware, software, or a combination of both. Whether a function is executed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0288] In one example, the functional unit in any of the above devices may be one or more integrated circuits configured to implement the above methods, such as: one or more application-specific integrated circuits (ASICs), or one or more central processing units (CPUs), one or more microcontroller units (MCUs), one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms.

[0289] In one example, storage unit 2230 may include random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory and / or registers, etc.

[0290] See Figure 23 , Figure 23 This is a schematic diagram of another communication device 2300 provided in an embodiment of this application. The device 2300 includes a transceiver 2310, which is used for receiving and / or transmitting signals. For example, the transceiver can be used to perform steps 1210 to 1230 described above.

[0291] The device 2300 further includes a processor 2320, which controls the transceiver 2310 to receive and / or transmit signals. Optionally, the processor 2320 is coupled to a memory 2330, which stores computer programs or instructions and / or data. The processor 2320 executes the computer programs or instructions stored in the memory 2330, or reads the data stored in the memory 2330, to perform the methods in the above-described method embodiments.

[0292] Optionally, there may be one or more processors 2320.

[0293] Optionally, the memory 2330 may be one or more.

[0294] Alternatively, the memory 2330 can be integrated with the processor 2320, or it can be set separately.

[0295] As an example, transceiver 2310 may have Figure 22 The communication unit 2210 shown has the function of the processor 2320. Figure 22 The processing unit 2220 shown has the function of [function name], and the memory 2330 can be [function name]. Figure 22 The function of the storage unit 2230 shown.

[0296] As one option, the device 2300 is used to implement the operations performed by the communication device in the various method embodiments described above.

[0297] For example, processor 2320 is used to execute computer programs or instructions stored in memory 2330 to implement the relevant operations of terminal devices or network devices in the various method embodiments described above.

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

[0299] It should also be understood that the memory mentioned in the embodiments of this application can be volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

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

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

[0302] See Figure 24 , Figure 24 This application provides a schematic diagram of a chip system 1300. The chip system 1300 (or processing system) includes logic circuitry 1310 and an input / output interface 1320.

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

[0304] Optionally, the logic circuit 1310 may be implemented by one or more processors, including the one or more processors or the processing portion of the one or more processors.

[0305] Optionally, the input / output interface 1320 may include transceiver circuitry, a transceiver, input / output circuitry, or a communication interface.

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

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

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

[0309] For example, when the computer program is executed by a computer, it enables the computer to implement the methods executed by the communication device (such as a terminal device) in the various embodiments of the above methods.

[0310] This application also provides a computer program product comprising instructions which, when executed by a computer, implement the methods performed by a communication device (such as a terminal device) in the above-described method embodiments.

[0311] This application also provides a communication system, which includes the terminal devices described in the preceding embodiments. For example, the system includes... Figure 12 Terminal devices in the process.

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

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

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

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

Claims

1. A communication method, characterized in that, The method includes: The network device receives a first physical random access channel (PRACH) resource and a second PRACH resource configured. The first PRACH resource includes PRACH resources located in a first flexible time domain unit and a sub-band full-duplex (SBFD) time domain unit. The second PRACH resource includes PRACH resources located in a second flexible time domain unit and an uplink UL time domain unit. The first flexible time domain unit and the second flexible time domain unit overlap in the time domain. Signals are transmitted based on the first PRACH resource or the second PRACH resource, wherein all or part of the PRACH resources on the first flexible time domain unit are not used to transmit the signals.

2. The communication method according to claim 1, characterized in that, If the SBFD symbol does not occupy the first flexible time domain unit, all resources in the PRACH resources located in the first flexible time domain unit are not used to transmit the signal; or... If the SBFD symbol occupies the first flexible time domain unit, all or part of the PRACH resources located in the first flexible time domain unit shall not be used to transmit the signal; The first PRACH resource is located in the first time-frequency resource, which includes the SBFD symbol in the time domain.

3. The communication method according to claim 2, characterized in that, The SBFD symbol occupies all time-domain units of the first flexible time-domain unit; or... The SBFD symbol occupies a portion of the time domain unit of the first flexible time domain unit.

4. The communication method according to any one of claims 1 to 3, characterized in that, Both the first flexible time domain unit and the second flexible time domain unit include a third flexible time domain unit, and the PRACH resources located in the third flexible time domain unit in the first PRACH resources are unavailable.

5. The communication method according to any one of claims 1 to 4, characterized in that, The method further includes: Receive first information from the network device, the first information being used to indicate that Y frequency division multiplexing ROs out of M1 frequency division multiplexing random access timings are invalid, where M1 is an integer greater than 0 and Y is an integer greater than 0 and less than or equal to M1.

6. The communication method according to claim 5, characterized in that, The Y frequency division multiplexing (RFD) resources satisfy the following condition: the distance between the first PRACH resource and the physical downlink shared channel (PDSCH) resource is less than or equal to N frequency domain units, where N is an integer greater than 0 and less than a preset value.

7. The communication method according to claim 6, characterized in that, N is indicated via signaling.

8. The communication method according to any one of claims 5 to 7, characterized in that, M1 bits correspond one-to-one to indicate the invalidity of the M1 frequency division multiplexing (RO) bits; or, The M1 bits indicate 2 M1 The 2 indexes M1 Each index corresponds to an invalid case of the M1 frequency division multiplexing ROs.

9. The communication method according to any one of claims 1 to 8, characterized in that, The method further includes: Receive second information from the network device, the second information being used to indicate that K time-division multiplexed ROs out of M2 time-division multiplexed ROs are invalid, the K time-division multiplexed ROs including the ROs of the first time-domain unit in the first PRACH resource, M2 being an integer greater than 0, and K being an integer greater than 0 and less than or equal to M2.

10. The communication method according to claim 9, characterized in that, M2 bits correspond one-to-one to indicate invalid M2 time-division multiplexing ROs; or, The M2 bits indicate 2 M2 The 2 indexes M2 Each index corresponds to an invalid case of the M2 time-division multiplexing ROs.

11. A communication device, characterized in that, Includes modules or units for performing the method as described in any one of claims 1 to 10.

12. A communication device, characterized in that, Includes a transceiver for executing computer programs or instructions to cause the communication device to perform the method as described in any one of claims 1 to 10.

13. The apparatus according to claim 12, characterized in that, The device further includes a memory for storing the computer program or the instructions.

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

15. A computer program product, characterized in that, When the computer reads and executes the computer program product, it causes the computer to perform the method as described in any one of claims 1 to 10.

Images