Communication method and device

Abstract

A communication method and apparatus, the method comprising: a network device sends first resource information, and a terminal device determines whether to use a first random access resource to perform random access based on a first event triggering random access. Wherein the first resource information is used for indicating a first random access resource, and a time domain resource of the first random access resource comprises an SBFD time unit. In the method, whether the SBFD resource can be used or not depends on a first event triggering random access. By limiting the random access triggering event capable of using the SBFD resource, selective use of the SBFD resource is realized, so that the purposes of efficiently using the SBFD resource to perform RACH and improving the random access performance are achieved.

Description

Technical Field

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

[0002] Currently, it has been proposed to perform random access channel (RACH) transmission on subband full duplex (SBFD) time units. Multiple events can trigger RACH; when one or more events occur, the terminal device can trigger RACH. The communication performance (e.g., access gain) resulting from RACH using SBFD resources varies across different application scenarios. Furthermore, SBFD resources are limited; therefore, how to utilize SBFD resources for RACH during random access is a crucial technical problem that needs to be solved. Summary of the Invention

[0003] This application provides a communication method and apparatus for using SBFD resources during random access, so as to make the most reasonable use of SBFD resources and improve random access performance.

[0004] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0005] Firstly, a communication method is provided, which can be applied to a terminal-side device (also called a terminal device). The terminal device can be a terminal equipment, or a module or unit that performs some of the functions of a terminal equipment. For example, the terminal device can be a circuit or chip / chip system (e.g., 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) or other functional module within the terminal equipment. Alternatively, the terminal device can be a logical node, logical module, or software that implements all or part of the functions of the terminal equipment. For ease of description, the following example assumes that the terminal device is a terminal equipment.

[0006] The communication method includes: a terminal device receiving first resource information and determining whether to use a first random access resource for random access based on a first event that triggers random access. The first resource information indicates the first random access resource, and the time-domain resources of the first random access resource include SBFD time units.

[0007] In this scheme, the availability of SBFD resources depends on the first event that triggers random access. Thus, by restricting the events that trigger random access and allow the use of SBFD resources, SBFD resources can be used selectively, thereby achieving the goal of rationally utilizing SBFD resources for RACH and improving random access performance. For example, by rationally configuring the events that allow the use of the first random access resource, the access success rate of certain terminal devices can be improved. For instance, the event that allows the use of the first random access resource can be configured to be the initial access event in the idle state, disallowing the use of the first random access resource when other events trigger random access. This reduces the number of terminal devices using the first random access resource, decreasing resource collisions and improving access success rate and efficiency.

[0008] In one implementation, determining whether to use the first random access resource for random access based on a first event that triggers random access includes: if the category of the first event is a first category, then determining that the random access triggered by the first event will use the first random access resource. By restricting the categories of events that trigger random access that can use SBFD resources, the purpose of selectively using SBFD resources is achieved.

[0009] In one implementation, determining whether to use the first random access resource for random access based on a first event that triggers random access includes: if the first event belongs to a first event set, then determining that the random access triggered by the first event will use the first random access resource. This scheme constrains the events that trigger random access that can use SBFD resources, achieving the goal of selectively using SBFD resources.

[0010] In one implementation, the method further includes: a terminal device receiving first information indicating information about at least one event of random access using a first random access resource.

[0011] The first piece of information can be sent by the network device, which means that the network side can configure at least one event that can use SBFD resources. Depending on different application scenarios, the network device can adjust at least one event that can use SBFD resources, making it more flexible.

[0012] In one implementation, the first information indicating at least one event for random access using the first random access resource includes: the first information indicating the category of the at least one event; or, the first information indicating a first set of events, which includes at least one event. The network device can directly configure events that can use the SBFD resource, which is relatively simple. Furthermore, one event can correspond to one or more categories. The network device can also indirectly configure events that can use the SBFD resource by restricting event categories.

[0013] In one implementation, the method further includes: a terminal device receiving second information used to determine the category of a first event. The network device can configure the category to which each event belongs; for example, the network device configures the category of the first event using the second information, so that the terminal device can clearly identify the category to which the first event belongs.

[0014] In one implementation, the category of the event that triggers random access includes at least one of the following: non-connectivity access, data transmission access, or mobility scenario access.

[0015] In one implementation, the first event includes one or more of the following: initial access to the radio resource control (RRC) idle state, an RRC connection re-establishment process, handover, a scheduling request (SR) failure, or an RRC connection recovery process from an inactive RRC state.

[0016] Secondly, a communication method is provided, which can be applied to a network-side device (also called a network device). The network device can be a network equipment or a component within a network equipment (e.g., a circuit, chip, or chip system). The network device can be a module or unit that performs some or all of the functions of the network equipment, such as a central unit (CU), a distributed unit (DU), or a radio unit (RU). Alternatively, the network device can be a logical node, logical module, or software that implements all or part of the functions of the network equipment. For ease of description, the following example uses a network equipment as the network device.

[0017] The communication method includes: a network device sending first resource information and first information, and receiving a random access message triggered by a first event using a first random access resource or a second random access resource. The first resource information indicates the first random access resource, whose time-domain resources include SBFD time units. The second random access resource's time-domain resources are non-SBFD time units.

[0018] The first information indicates information about at least one event in which random access is performed using the first random access resource.

[0019] In one implementation, the network device uses a first random access resource or a second random access resource to receive a random access message, including: when the category of the first event is a first category, the network device uses the first random access resource to receive the random access message.

[0020] In one implementation, the network device uses a first random access resource or a second random access resource to receive a random access message, including: when a first event belongs to a first event set, the network device uses the first random access resource to receive the random access message.

[0021] In one implementation, the information indicating at least one event for random access using the first random access resource includes: the first information indicating the category of at least one event; or, the first information indicating a first set of events, which includes at least one event.

[0022] In one implementation, the method further includes: the network device sending second information, the second information being used to determine the category of the first event.

[0023] In one implementation, the category of the event that triggers random access includes at least one of the following: non-connectivity access, data transmission access, or mobility scenario access.

[0024] In one implementation, the first event includes one or more of the following: initial access to the RRC idle state, switching of the RRC connection re-establishment process, SR failure, or the process of restoring the RRC connection from the RRC inactive state.

[0025] The beneficial effects of the second aspect and its various implementation methods can be referred to the beneficial effects of the first aspect and its various implementation methods mentioned above, and will not be repeated here.

[0026] Thirdly, a communication method is provided that can be applied to a terminal-side device. For details regarding the terminal-side device, please refer to the relevant description in the first aspect above. For ease of description, the terminal-side device will be exemplified below as a terminal device.

[0027] The communication method includes: a terminal device receiving first resource information; if a first condition is met, then performing random access using a first random access resource. The first resource information indicates the first random access resource, and the time-domain resource of the first random access resource includes SBFD time units. The first condition includes one or more of the following: the latency of the current random access is lower than a first threshold, or the terminal device supports a first feature.

[0028] This scheme achieves selective use of SBFD resources by restricting the conditions that must be met to use them. For example, whether SBFD resources can be used depends on whether the first condition is met. This scheme can achieve the goal of efficiently using SBFD resources for RACH and improving random access performance.

[0029] Fourthly, a communication method is provided that can be applied to a network-side device. For details regarding the network-side device, please refer to the relevant description in the second aspect above. For ease of description, the network-side device will be exemplified below as a network device.

[0030] The communication method includes: a network device sending first resource information and receiving a random access message from a terminal device on a first random access resource. The first resource information indicates the first random access resource, and the time-domain resource of the first random access resource includes SBFD time units. The random access message is triggered based on a first condition, which includes one or more of the following: the latency of the current random access is lower than a first threshold, or the terminal device supports a first feature.

[0031] The beneficial effects of the fourth aspect and its various implementation methods can be referred to the beneficial effects of the third aspect and its various implementation methods mentioned above, and will not be repeated here.

[0032] Fifthly, embodiments of this application provide a communication method that can be executed by a first communication device and a second communication device. The first communication device has the function of implementing the behavior in the method example of the first aspect described above. For example, the first communication device includes corresponding means, modules, or units for executing the method of the first aspect, which can be implemented by software and / or hardware. The first communication device can be the aforementioned terminal device, and the second communication device can be the aforementioned network device. The following example uses the first communication device as a terminal device and the second communication device as a network device.

[0033] The communication method includes: a network device sending first resource information to a terminal device, the first resource information indicating a first random access resource, the time domain resource of the first random access resource including SBFD time units; the terminal device determining whether to use the first random access resource for random access based on a first event triggering random access; and the network device receiving a random access message triggered based on the first event using either the first random access resource or a second random access resource. The time domain resource of the second random access resource is a non-SBFD time unit.

[0034] For the beneficial effects of the fifth aspect, please refer to the beneficial effects of the first aspect and its various implementation methods, which will not be elaborated here.

[0035] Sixthly, embodiments of this application provide a communication device that has the functionality to implement the behaviors described in any of the method examples of the first to fourth aspects. The beneficial effects can be found in the relevant descriptions of any of the first to fourth aspects, and will not be repeated here. For example, the communication device may be a terminal device as described in the first or third aspect, or it may be a device capable of supporting the terminal device in implementing the functions required by the methods provided in the first or third aspect; for example, the communication device may be a chip or chip system in the terminal device. As another example, the communication device may be a network device as described in the second or fourth aspect, or it may be a device capable of supporting the network device in implementing the functions required by the methods provided in the second or fourth aspect; for example, the communication device may be a chip or chip system in the network device.

[0036] In one possible design, the communication device includes a baseband device and a radio frequency device.

[0037] In one possible design, the communication device includes corresponding means, modules, or units for performing the methods of any of the first to fourth aspects. These modules, units, or means can be implemented in software, hardware, or a combination of both. For example, the communication device includes a processing unit (sometimes also called a processing module or processor) and / or a transceiver unit (sometimes also called a transceiver module or transceiver). The transceiver unit is capable of both transmitting and receiving functions. When the transceiver unit performs the transmitting function, it can be called a transmitting unit (sometimes also called a transmitting module), and when it performs the receiving function, it can be called a receiving unit (sometimes also called a receiving module). The transmitting unit and the receiving unit can be the same functional unit, referred to as the transceiver unit, which performs both transmitting and receiving functions; or, the transmitting unit and the receiving unit can be different functional units, with "transceiver unit" being a general term for these functional units. These units (modules) can perform the corresponding functions in the method examples of any of the first to fourth aspects described above, as detailed in the method examples, and will not be repeated here.

[0038] For example, the communication device is used to implement the corresponding function in the method example of the first aspect. The transceiver module is used to receive first resource information, which indicates a first random access resource. The time-domain resource of the first random access resource includes SBFD time units. The processing module is used to determine whether to use the first random access resource for random access based on a first event that triggers random access.

[0039] For example, the communication device is used to implement the corresponding function in the method example of the second aspect. The transceiver module is used to send first resource information and first information, and to receive a random access message triggered based on a first event using a first random access resource or a second random access resource. The first resource information indicates the first random access resource, whose time-domain resource includes SBFD time units. The second random access resource's time-domain resource is a non-SBFD time unit. The first information indicates information about at least one event in which random access is performed using the first random access resource.

[0040] For example, the communication device is used to implement the corresponding function in the method example of the third aspect. The transceiver module is used to receive first resource information. If a first condition is met, random access is performed using the first random access resource. The first resource information indicates the first random access resource, and the time-domain resource of the first random access resource includes SBFD time units. The first condition includes one or more of the following: the latency of the current random access is lower than a first threshold, or the terminal device supports a first feature. The processing module is used to determine whether the first condition is met.

[0041] For example, the communication device is used to implement the corresponding function in the method example of the fourth aspect, and the transceiver module is used to send first resource information and receive a random access message from the terminal device on the first random access resource. The first resource information indicates the first random access resource, and the time-domain resource of the first random access resource includes SBFD time units. The random access message is triggered based on a first condition, which includes one or more of the following: the latency of the current random access is lower than a first threshold, or the terminal device supports a first feature.

[0042] In a seventh aspect, embodiments of this application provide a communication device including a processor configured to execute methods from any of the first to fourth aspects and any implementation thereof. Optionally, the communication device further includes a communication interface. Optionally, the communication device also includes a memory for storing computer programs (also referred to as code or instructions), data, etc. The processor is coupled to the memory and the communication interface. When the processor reads the computer program, data, etc., from the memory, methods from any of the first to fourth aspects and any implementation thereof are executed.

[0043] Eighthly, embodiments of this application provide a communication device including an input / output interface and logic circuitry. The input / output interface is used for inputting and / or outputting information. The input / output interface may be an interface circuit, an output circuit, an input circuit, a pin, or related circuitry, etc. The logic circuitry is used to execute the methods described in any of the first to fourth aspects.

[0044] In the seventh and eighth aspects, the communication device may be a terminal device as described in the first or third aspect. Alternatively, the communication device may be a means capable of supporting the terminal device in implementing the functions required by the methods provided in the first or third aspect; for example, the communication device may be a chip or chip system within the terminal device. Alternatively, the communication device may be a network device as described in the second or fourth aspect. Alternatively, the communication device may be a means capable of supporting the network device in implementing the functions required by the methods provided in the second or fourth aspect; for example, the communication device may be a chip or chip system within the network device. The chip may be a baseband chip and / or a radio frequency chip, and the chip system may be composed of chips or may include chips and other discrete devices.

[0045] In one implementation of the eighth aspect, when the communication device is a terminal device, the interface circuit can be a radio frequency processing chip in the terminal device, and the processing circuit can be a baseband processing chip in the terminal device. When the communication device is a network device, the interface circuit can be a radio frequency processing chip in the network device, and the processing circuit can be a baseband processing chip in the network device.

[0046] In one implementation of the eighth aspect, when the communication device is a chip or chip system, the input circuit can be an input pin, the output circuit can be an output pin, and the logic circuit can be a transistor, gate circuit, flip-flop, or various other logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver; the signal output by the output circuit can be, for example, but not limited to, output to a transmitter and transmitted by the transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the input / output interface and the logic circuit.

[0047] Ninthly, embodiments of this application provide a communication system including a terminal device and a network device. The terminal device is used to implement the function of the method described in the first aspect, and the network device is used to implement the function of the method described in the second aspect. Alternatively, the terminal device is used to implement the function of the method described in the third aspect, and the network device is used to implement the function of the method described in the fourth aspect.

[0048] In a tenth aspect, embodiments of this application provide a computer-readable storage medium for storing a computer program or instructions that, when executed, cause the methods described in any of the first to fourth aspects and any implementation thereof to be implemented.

[0049] Eleventhly, embodiments of this application also provide a computer program product containing instructions that, when run on a computer, cause the methods described in any of the first to fourth aspects and any of their implementations to be implemented.

[0050] The beneficial effects of the sixth to eleventh aspects and their implementation methods can be referenced to the beneficial effects of the first aspect or the third aspect and any one of their implementation methods. Attached Figure Description

[0051] Figure 1 A schematic diagram of the architecture of a communication system provided in an embodiment of this application;

[0052] Figures 2A to 2C A schematic diagram of SBFD resource allocation provided in an embodiment of this application;

[0053] Figure 3A A schematic diagram illustrating the time-domain location of PRACH as provided in an embodiment of this application;

[0054] Figure 3B A schematic diagram illustrating the frequency domain location of PRACH as provided in an embodiment of this application;

[0055] Figure 4 A schematic flowchart illustrating the communication method provided in an embodiment of this application;

[0056] Figure 5 A schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0057] Figure 6 This is another schematic diagram of the communication device provided in the embodiments of this application. Detailed Implementation

[0058] The technical solutions provided in the embodiments of this application can be applied to various communication systems, such as Long Term Evolution (LTE) communication systems, 5th Generation (5G) mobile communication systems / New Radio (NR) communication systems, or future mobile communication systems, or other similar communication systems. Other similar communication systems may include Wireless Fidelity (WIFI), Vehicle-to-Everything (V2X), Internet of Things (IoT) systems, and so on.

[0059] Please see Figure 1This illustration shows a communication system applicable to embodiments of this application. The communication system includes a wireless access network 100 and a core network 200. Optionally, the communication system may further include the Internet. Figure 1 (Using this as an example).

[0060] The wireless access network 100 may include at least one network device and at least one terminal device. For example, the wireless access network 100 includes two network devices, 110a and 110b, and terminal devices, such as 120a to 120j. Figure 1 The network architecture shown is merely illustrative; the number of terminal devices and / or network devices may be fewer or more. The communication system described in the embodiments of this application is intended to more clearly illustrate the technical solutions of the embodiments of this application and does not constitute a limitation on the communication system to which the embodiments of this application apply. For example, the communication system may also include other devices, such as wireless relay devices and wireless backhaul devices, etc. Figure 1 Not shown in the diagram. Those skilled in the art will recognize that, with the evolution of network architecture, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems. When applying the technical solutions of the embodiments of this application to other communication systems, the devices, components, modules, etc., in the embodiments can be replaced with corresponding devices, components, modules in other communication systems, without limitation.

[0061] In this embodiment, network equipment refers to (radio)access network ((R)AN) equipment / RAN node. In this embodiment, (R)AN and RAN are interchangeable. RAN can be a cellular system related to the 3rd generation partnership project (3GPP), such as a 5G / NR mobile communication system or a future-oriented evolution system. RAN can also be an open RAN (O-RAN or ORAN), a cloud radio access network (CRAN), a virtualized RAN (vRAN), a non-terrestrial network (NTN), etc. RAN can also be a communication system that integrates two or more of the above systems. RAN equipment can also be called a RAN node, RAN entity, or access node, etc.

[0062] In one possible scenario, a RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), or a base station in a future mobile communication system. RAN nodes can also be macro base stations, micro base stations, indoor stations, relay nodes, donor / host nodes, or radio controllers. RAN nodes can also be servers, wearable devices, vehicles, or in-vehicle equipment. For example, in V2X technology, the RAN node can be a roadside unit (RSU).

[0063] In another possible scenario, the RAN node can be a module or unit that performs some of the functions of the base station; or multiple RAN nodes can cooperate to assist terminal equipment in achieving wireless access, with different RAN nodes performing some of the functions of the base station. For example, the RAN node can be a CU, DU, or RU. The function of the CU can be implemented by a single entity or by different entities. For example, the function of the CU can be further divided, that is, the control plane and the user plane can be separated and implemented by different entities, namely the control plane CU entity (i.e., CU-control plane (CP) entity) and the user plane CU entity (i.e., CU-user plane (UP) entity). The CU-CP entity and the CU-UP entity can be coupled with the DU to jointly complete the function of the RAN node. The CU and DU can be set up separately or included in the same network element, such as in the baseband unit (BBU). Any of the units among the CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented by software modules, hardware modules, or a combination of software modules and hardware modules.

[0064] 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, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples.

[0065] The CU and DU can be configured according to the protocol layer functions of the wireless network they implement: for example, the CU can be configured to implement the functions of the Packet Data Convergence Protocol (PDCP) layer and above (such as the Radio Resource Control (RRC) layer and / or the Service Data Adaptation Protocol (SDAP) layer); the DU can be configured to implement the functions of the protocol layers below the PDCP layer (such as the Radio Link Control (RLC) layer, the Media Access Control (MAC) layer, and / or the Physical (PHY) layer). For specific descriptions of the above protocol layers, please refer to the relevant 3GPP technical specifications or the technical specifications of other applicable communication protocols.

[0066] The above division of the processing functions of CU and DU according to protocol layers is merely an example; other division methods are also possible, and this application does not limit this. For example, in one design, CU or DU can be further divided into processing functions with protocol layers. In one design, some functions of the RLC layer and the functions of the protocol layer above the RLC layer are located in the CU, while the remaining functions of the RLC layer and the functions of the protocol layer below the RLC layer are located in the DU.

[0067] In another possible design, the DU and RU collaborate to implement the PHY layer functionality, or, more specifically, a portion of the PHY layer functionality of the DU can be moved to the RU. A DU can be connected to one or more RUs. The functions of the DU and RU can be configured in various ways depending on the design. For example, the DU may be configured to implement baseband functions, and the RU may be configured to implement mid-RF functions. Alternatively, the DU may be configured to implement higher-level functions in the PHY layer, and the RU may be configured to implement lower-level functions in the PHY layer, or both lower-level and RF functions. Higher-level functions in the physical layer may include a portion of the physical layer's functionality closer to the MAC layer, and lower-level functions may include another portion of the physical layer's functionality closer to the mid-RF side. This application does not limit the specific functions of the DU and RU. The interface between the DU and RU can be called a fronthaul interface. In one design, the CU may not have a PDCP layer; for example, the CU may only include an RRC layer. The CU-CP may not have PDCP-C. The CU-UP may not have PDCP-U, or may not have a CU-UP. In one design, the DU may not have an RLC layer; for example, the DU may only have a MAC and a higher PHY layer.

[0068] When the RAN is O-RAN, it can also have artificial intelligence (AI) capabilities. For example, O-RAN includes an intelligent controller. The intelligent controller can be a non-real-time RAN intelligent controller (RIC / non-RT RIC / NRTRIC) or a near-real-time RAN intelligent controller (RIC / nRT RIC / nRT RIC). A non-real-time RIC can be used to implement non-real-time intelligent management of RAN functions, enabling workflows including model training and updates, and guiding applications / functions in the nRT RIC based on policies. A near-real-time RIC can be used to implement near-real-time intelligent management of the RAN. Through data collection and related operations on the E2 interface, near-real-time control and optimization of O-RAN modules and resources are achieved.

[0069] In this application embodiment, anything capable of data communication with a base station can be considered a terminal device. Terminal devices are also called terminals, terminal equipment, user equipment (UE), mobile stations, or mobile terminals, etc. Terminal devices can be widely used in various scenarios. For example, terminal devices can be: mobile phones, computers, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, stations (STA), robotic arms, cameras, robots, vehicles, drones, helicopters, airplanes, ships, or smart home devices (such as televisions, air conditioners, robot vacuums, speakers, set-top boxes), relays, customer premises equipment (CPE), etc.

[0070] Furthermore, in this embodiment, the terminal device can also be a terminal device in an IoT system, such as a water meter or electricity meter. IoT is an important component of future information technology development. Its main technical characteristic is connecting objects to networks through communication technology, thereby realizing an intelligent network that enables human-machine interconnection and object-to-object interconnection.

[0071] When the terminal device is applied to V2X, it can also be called a V2X device, such as a smart car, an unmanned car, a driverless car, a pilotless car, or an automobile, or a roadside unit (RSU). All the terminal devices described above, if located on a vehicle (e.g., placed / installed inside the vehicle), can be considered in-vehicle terminal devices. In-vehicle terminal devices can be built into a vehicle's on-board module, on-board unit, on-board component, on-board chip, or on-board unit as one or more components or units. The vehicle can implement the methods of this application through the built-in on-board module, on-board unit, on-board component, on-board chip, or on-board unit. In-vehicle terminal devices can be vehicle equipment, on-board modules, vehicles, on-board units (OBU), RSUs, in-vehicle infotainment systems (or on-board transmitting units) (telematics boxes, T-boxes), chips, or SoCs, etc., and the aforementioned chips or SoCs can be installed in the vehicle, OBU, RSU, or T-box.

[0072] The communication system applicable to the embodiments of this application has been described above. To facilitate understanding of the technical solutions provided by the embodiments of this application, the relevant technical terms involved in the embodiments of this application will be explained below.

[0073] 1) SBFD

[0074] SBFD (Simplified Beginning Shift) is a mechanism proposed for Time Division Duplexing (TDD) to reduce uplink (UL) latency and improve uplink coverage. In TDD systems, downlink (DL) typically consumes more time-domain resources than uplink, resulting in coverage imbalance between the downlink and uplink. It's important to understand that uplink and downlink are relative terms. If the connection from network device to terminal device is uplink, then the connection from terminal device to network device is downlink. Conversely, if the connection from network device to terminal device is downlink, then the connection from terminal device to network device is uplink (this is used as an example in this paper).

[0075] For example, see Figure 2A This is a schematic diagram of a TDD configuration method. Figure 2A In this configuration, D represents a downlink time slot, where each symbol is a downlink symbol, and U represents an uplink time slot, where each symbol is an uplink symbol. This configuration results in limited time-domain resources for uplink transmission, lower uplink resource coverage, and increased uplink latency, failing to meet the demands of low-latency services.

[0076] To improve uplink coverage performance and reduce uplink transmission latency, technologies such as SBFD or single-frequency full-duplex (SFFD) are proposed.

[0077] In SBFD, a component carrier (CC) is divided into multiple sub-bands. The transmission directions of different sub-bands can be the same or different. Network devices can simultaneously transmit and receive signals on the same time-domain resources. This is equivalent to increasing the resources available for uplink transmission on the CC, thereby enhancing uplink coverage and reducing uplink latency.

[0078] For easier understanding, please refer to Figure 2B Two typical SBFD configurations are shown, such as SBFD(1) to SBFD(2). Figure 2B In this context, D represents downlink time-domain resources, and U represents uplink time-domain resources. From... Figure 2B It can be seen that uplink and downlink transmissions use different sub-band / frequency domain resources. Thus, on the same time domain resources, the device can simultaneously transmit and receive signals. This can be considered as increasing the resources available for uplink transmission on the CC band, thereby enhancing uplink coverage performance and reducing uplink latency.

[0079] In SFFD, uplink and downlink transmissions can be performed simultaneously on the same time-frequency resources. For example, on a single time-domain unit, the entire CC can be used for both transmission and reception.

[0080] For easier understanding, please refer to Figure 2C The diagram shows a schematic of SFFD. Figure 2C In this context, D represents downlink time-domain resources, and U represents uplink time-domain resources. From... Figure 2C As can be seen, uplink and downlink transmissions can be performed simultaneously on the same time-frequency resources, thus enhancing uplink coverage performance and reducing uplink latency.

[0081] 2) Random access procedure

[0082] Random access procedures include 4-step random access (also known as Type-1 RA) and 2-step random access (also known as Type-2 RA). Depending on whether there is a conflict in the transmission of preambles between terminal devices, random access procedures are further divided into contention-based random access (CBRA) and contention-free random access (CFRA). Compared to contention-based random access, in contention-free random access, the network device sends preamble allocation information to the terminal device. Since the preamble is allocated by the network device, the terminal device does not need to choose it independently, thus avoiding competition with other terminal devices.

[0083] The contention-based random access procedure mainly consists of four steps, also known as the 4-step random access procedure. This four-step procedure involves four types of random access messages, referred to as Random Access Message 1 through Random Access Message 4. Random Access Message 1 is the random access preamble, often simply called message 1 (Msg1). Random Access Message 2 is the response message to Random Access Message 1, also known as the RAR, and can be simply called message 2 (Msg2). Random Access Messages 3 and 4 are for contention-based access mechanisms and are used to resolve contention conflicts. Random Access Message 3 is also called Msg3, and Random Access Message 4 is also called the conflict resolution message / contention resolution message / Msg4.

[0084] In the four-step random access process, the terminal device sends a preamble (Msg1) through the physical random access channel (PRACH). Before sending Msg1, the terminal device obtains the PRACH resource configuration by reading the system broadcast information and determines the PRACH resources based on the configuration.

[0085] After sending Msg1, the terminal device initiates a random access response window, listening for the RAR (Random Access Response) from the network device (i.e., Msg2) within this window. If the terminal device successfully detects its own RAR, the random access is successful. Subsequently, the terminal device sends Msg3 to the network device according to the instructions in the RAR, used to send an RRC connection establishment request. If the terminal device does not receive its own RAR, the random access fails, and the terminal device re-initiates random access according to the fallback parameters indicated by the network device, until the maximum number of random access attempts is reached.

[0086] After sending Msg3, the terminal device listens for Msg4 from the network device. Msg4 carries a conflict resolution flag and air interface parameter configurations specific to the terminal device. If the terminal device successfully receives Msg4, random access is successful; otherwise, random access fails. If random access is successful, the terminal device can send Msg5 to the network device to send an RRC establishment completion command. If random access fails, the terminal device re-initiates random access according to the fallback parameters indicated by the network device until the maximum number of random access attempts is reached.

[0087] The two-step random access procedure involves two types of random access messages: Random Access Message A (MsgA) and Random Access Message B (MsgB). MsgA is equivalent to Random Access Message 1 and Random Access Message 3 in the four-step random access procedure; MsgB is equivalent to Random Access Message 2 and Random Access Message 4 in the four-step random access procedure. For details, please refer to the aforementioned description of the four-step random access procedure; it will not be repeated here.

[0088] 3) PRACH resources

[0089] PRACH resources include time-domain resources, frequency-domain resources, and preamble sequence resources. Network devices can configure PRACH resources, including configuring time-domain resources, frequency-domain resources, preamble sequence resources, power control information, etc. In the embodiments of this application, the preamble sequence can also be referred to as preamble, random access request, random access preamble, preamble, preamble code, PRACH bearer preamble, RACH preamble, Msg1, or MsgA, etc.

[0090] 3-1) Time-domain resources

[0091] The 3GPP protocol defines a RA configuration table, which contains multiple rows. Each row includes parameters such as the PRACH configuration index, preamble format, period, offset, subframe number, start symbol, number of PRACH slots within a subframe, number of PRACH slots within a PRACH slot, and PRACH duration. Network devices use higher-layer signaling to indicate the value of the PRACH configuration index, thus specifying which row of the table's RA configuration parameters to use, i.e., indicating the time-domain resource of the PRACH resource.

[0092] For example, see Figure 3AThis is a schematic diagram illustrating the temporal location of the PRACH according to an embodiment of this application. The terminal device can determine the PRACH period, the frame in which the PRACH resides, the subframe in which the PRACH resides, and the time slot structure of the subframe in which the PRACH resides, based on the value of the PRACH configuration index, thereby determining the temporal location of the PRACH.

[0093] 3-2) Frequency Domain Resources

[0094] The frequency domain resources of PRACH can be determined based on the higher-layer parameters msg1-FrequencyStart and msg1-FDM, or alternatively, based on higher-layer parameters msgA-RO-FrequencyStart and msgA-RO-FDM. msg1-FrequencyStart or msgA-RO-FrequencyStart indicates the frequency start position of the random access channel occasion (RO). msg1-FDM or msgA-RO-FDM indicates the number of ROs. The terminal device can determine the frequency domain resources of PRACH based on the frequency domain start position of the ROs and the number of ROs.

[0095] For example, see Figure 3B This is a schematic diagram illustrating the frequency domain location of the PRACH according to an embodiment of this application. The terminal device can determine the frequency domain start position of the RO based on msg1-FrequencyStart, and determine the number of ROs based on msg1-FDM, thereby determining the frequency domain location of the PRACH.

[0096] 3-3) Preamble sequence resources

[0097] Network devices can configure parameters such as preamble format, root sequence index, number of preambles supported per RO, cyclic shift, restricted set type, subcarrier spacing, and group A / B related information to indicate the preamble sequence resources configured for terminal devices. Additionally, network devices can configure the mapping between ROs and synchronization signals and physical broadcast channel (PBCH) blocks (SSBs) and the number of preambles per SSB on each RO through higher-layer parameters.

[0098] 4) Events that trigger RACH

[0099] RACH can be triggered by one or more events. Events that trigger RACH include one or more of the following events, or any of the following events will trigger RACH.

[0100] (4-1) Initial access from RRC_IDLE in the RRC idle state;

[0101] When a terminal device is in the RRC idle state and needs to establish an initial wireless connection, it will trigger RACH.

[0102] (4-2) RRC Connection Re-establishment procedure;

[0103] (4-3) During RRC_CONNECTED or RRC_INACTIVE, when the small data transmission (SDT) procedure (see clause 18.0) is ongoing, and the uplink (UL) synchronization status is "non-synchronized", data arrives on the downlink (DL) or UL.

[0104] (4-4) When there are no available physical uplink control channel (PUCCH) resources for SR, UL data arrives during RRC_CONNECTED or during RRC_INACTIVE while SDT procedure is ongoing.

[0105] (4-5) Handover, unless RACH-less handover (HO) is configured.

[0106] (4-6) SR failure;

[0107] (4-7) Explicit request by RRC upon synchronous reconfiguration;

[0108] (4-8) The RRC Connection Resume procedure from RRC_INACTIVE;

[0109] (4-9) To establish time alignment for a primary or secondary TAG;

[0110] (4-10) Request for Other System Information (SI) (see clause 7.3)

[0111] (4-11) Beam failure recovery;

[0112] (4-12) Consistent UL LBT failure on SpCell;

[0113] (4-13) SDT in RRC_INACTIVE (see clause 18);

[0114] (4-14) Positioning purpose during RRC_CONNECTED requiring random access procedure. For example, when timing advance is needed for UE positioning;

[0115] (4-15) Early UL synchronization with an LTM candidate cell for L1 / L2 triggered mobility (LTM) handover.

[0116] (4-16) RACH-based LTM cell switch.

[0117] 5) Time unit

[0118] A time unit generally refers to a unit of time. A time-domain unit can be a radio frame, subframe, slot, mini-slot, orthogonal frequency division multiplexing (OFDM) symbol, millisecond (ms), or fractional milliseconds (e.g., 1 / 32 ms). Alternatively, a time-domain unit can be multiple slots, multiple subframes, multiple mini-slots, multiple OFDM symbols, several milliseconds (ms), or several fractional milliseconds. A radio frame may include multiple subframes, a subframe may include one or more slots, and a slot may include at least one symbol. Alternatively, a radio frame may include multiple slots, and a slot may include at least one symbol. In the embodiments of this application, an OFDM symbol is simply referred to as a symbol; unless otherwise specified, a symbol refers to an OFDM symbol.

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

[0120] In this application embodiment, the number of nouns, unless otherwise specified, refers to "singular nouns or plural nouns," that is, "one or more." "At least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A / B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. For example, A / B means: A or B. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and / or c means the following combinations: a exists alone, b exists alone, c exists alone, a and b exist simultaneously, a and c exist simultaneously, b and c exist simultaneously, or a, b, and c exist simultaneously, where a, b, and c can be single or multiple.

[0121] In the embodiments of this application, "when," "if," and "if" all refer to the device taking corresponding actions under certain objective circumstances, and are not time-limited, nor do they require the device to perform a judgment action, nor do they imply any other limitations. Unless otherwise specified, "if" and "if" can be substituted, and "when" and "in the case of" can be substituted. "When" and "if" / "if" can be substituted.

[0122] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0123] In this application, the ordinal numbers such as "first" and "second" are used to distinguish multiple objects, and are not used to limit the size, content, order, timing, priority, or importance of the multiple objects. For example, "first random access resource" and "second random access resource" refer to two different random access resources, and do not indicate a difference in priority or importance between the two random access resources.

[0124] In the embodiments of this application, the solutions in each embodiment can be used in a reasonable combination, and the explanations or descriptions of various terms, similar operations, or steps appearing in the embodiments can be referenced or explained to each other in the embodiments, without limitation.

[0125] As mentioned earlier, current proposals suggest performing RACH on SBFD resources. Multiple events / scenarios can trigger RACH; when one or more events occur, the terminal device can initiate the RACH process. The communication performance (e.g., access gain) resulting from RACH on SBFD resources varies depending on the application scenario (e.g., different numbers and densities of access users). Furthermore, SBFD resources are limited; for example, the uplink available bandwidth within an SBFD time unit is less than the uplink available bandwidth within a non-SBFD time unit. Currently, there is no corresponding solution for efficiently utilizing SBFD resources for RACH to improve random access performance.

[0126] Therefore, this application provides a solution based on its embodiments. This application embodiment actually provides a method for using SBFD resources during random access. In this method, by setting conditions for using SBFD resources for RACH, the selective use of SBFD resources is achieved, thereby achieving the goal of rationally using SBFD resources for RACH and improving random access performance. For example, the events that trigger random access and allow the use of SBFD resources for RACH can be restricted. Whether SBFD resources can be used depends on whether the events triggering random access meet certain conditions. Only events that meet certain conditions or specific events can allow the use of the first random access resource. This limits the number of terminal devices using the first random access resource to a smaller number, reduces resource collisions, and improves access success rate and access efficiency.

[0127] This application does not limit the specific granularity of the "time unit". For example, an SBFD time unit can be an SBFD symbol or an SBFD time slot; a non-SBFD time unit can be a non-SBFD symbol or a non-SBFD time slot. Here, an SBFD symbol is a symbol configured with SBFD, and a non-SBFD symbol is a symbol without SBFD; an SBFD time slot is a time slot configured with SBFD, and a non-SBFD time slot is a time slot without SBFD. Regarding the configuration of SBFD, depending on whether a time slot simultaneously contains SBFD symbols and non-SBFD symbols, the following two possible configuration methods can be referenced:

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

[0129] (2) SBFD configuration is symbol-level, meaning that a slot contains symbols that can be configured as SBFD symbols in some parts and as non-SBFD symbols in others.

[0130] In this embodiment, within an SBFD time unit, a carrier may include at least two subbands, comprising a subband for uplink transmission (referred to as the uplink subband) and a subband for downlink transmission (referred to as the downlink subband). A guard band may or may not be provided between the uplink and downlink subbands. This embodiment does not impose restrictions on whether a guard band is provided between the uplink and downlink subbands. Furthermore, if a guard band exists between the uplink and downlink subbands, this embodiment does not impose restrictions on whether transmission occurs on that guard band. Additionally, the uplink and downlink subbands may or may not overlap. This embodiment also does not impose restrictions on whether the uplink and downlink subbands overlap.

[0131] In this embodiment, RACH resources include PRACH resources. Unless otherwise specified, "(pre)configuration" in this embodiment refers to configuration via signaling, which may be one or more of RRC signaling, downlink control information (DCI), or MAC control element (CE).

[0132] The communication method provided in the embodiments of this application is described below.

[0133] In the following description, the communication method provided in the embodiments of this application is applied to Figure 1Taking the network architecture shown as an example, the communication method provided in this application embodiment can be executed by a network device and a terminal device. The steps executed by the network device can be implemented by the RAN device itself, or by components within the RAN device (such as a baseband chip, or other processing units or processor modules), or by components that perform some or all of the functions of the RAN device (such as a CU, DU, or RU). The steps executed by the terminal device can be implemented by the terminal device itself, or by components within the terminal device (such as a baseband chip, or other processing units or processor modules). There are no restrictions on the specific form of the network device and the terminal device; for example, the network device can be a chip, and the terminal device can be a device; or both the network device and the terminal device can be chips or devices. In possible scenarios, the network device can be... Figure 1 The terminal device 120a shown, or it could be Figure 1 The chip (system) in the terminal device 120a; the terminal device can be Figure 1 The network device 110a in the middle, or it could be Figure 1 The chip (system) in network device 110a. In possible scenarios, the network device can be... Figure 1 The terminal device 120b shown, or it could be Figure 1 The chip (system) in the terminal device 120b; the terminal device can be Figure 1 The terminal device 120a, or it could be Figure 1 The chip (system) in the terminal device 120a.

[0134] Please see Figure 4 This is a flowchart illustrating the communication method provided in an embodiment of this application. Figure 4 This method is introduced from the perspective of interaction between network devices and terminal devices. It should be understood that the communication method can also be implemented by other devices, such as chips or communication devices with communication capabilities. Furthermore, the processing performed by a single execution entity can be divided into multiple execution entities, which can be logically and / or physically separated. For example, the processing performed by a network device can be divided into execution by at least one of CU, DU, RU, etc. Figure 4 As shown, the communication method includes the following steps.

[0135] S401, The network device sends the first resource information.

[0136] Accordingly, the terminal device receives first resource information. The first resource information is used to indicate a first random access resource. The time-domain resource of the first random access resource includes an SBFD time unit, or the time-domain resource of the first random access resource is an SBFD time unit. That is, in this embodiment, the network device configures a dedicated random access resource for each SBFD time unit. A SBFD time unit-specific random access resource refers to a set of one or more RACH resources located only on the SBFD time unit.

[0137] The first resource information can also be PRACH resource configuration. For example, the first resource information can be carried in the common access channel configuration (RACH-ConfigCommon) field in system information block 1 (SIB1).

[0138] S402, The network device sends the second resource information.

[0139] Accordingly, the terminal device receives second resource information. The second resource information is used to indicate a second random access resource. The time-domain resource of the second random access resource is a non-SBFD time unit. In this embodiment, the network device can also configure random access resources for non-SBFD time units. A RACH resource for a non-SBFD time unit refers to a set of one or more RACH resources located only in the non-SBFD time unit.

[0140] The second resource information can also be a PRACH resource configuration. For example, the first resource information can be carried in the RACH-ConfigCommon field of the SIB. The first and second resource information can be carried in different signaling. For example, the first resource information can be carried in SIBX and SIB1, where SIBX can be a newly defined SIB or an already defined SIB, but different from SIB1. Alternatively, the first and second resource information can be carried in the same signaling, for example, both the first and second resource information can be carried in the RACH-ConfigCommon field of SIB1. Another example is that the first resource information is carried in the first RACH-ConfigCommon field of SIB1, and the second resource information is carried in the second RACH-ConfigCommon field of SIB1.

[0141] Alternatively, the first or second resource information can also be carried in dedicated signaling, such as RRC signaling. The first and second resource information can be carried in the same dedicated signaling or in different dedicated signaling.

[0142] The execution order of S401 and S402 is not limited. For example, S402 can be executed before or after S401.

[0143] It should be noted that the network device can configure one set of random access resources for SBFD time units and another set of random access resources for non-SBFD time units using the first resource information and the second resource information. That is, it can configure dedicated random access resources for SBFD time units and non-SBFD time units respectively. Alternatively, the network device can configure a first random access resource using the first resource information, and the time domain resources corresponding to this first random access resource can include both SBFD and non-SBFD time units. In this case, S402 does not need to be executed; therefore, in Figure 4 S402 is shown as a dashed line.

[0144] When a network device configures the first random access resource and the second random access resource using the first resource information and the second resource information, the contents of the first resource information and the second resource information are also different because the first random access resource and the second random access resource are different. As mentioned above, PRACH resource configuration includes time-domain resource configuration, frequency-domain resource configuration, and preamble sequence resource configuration. Accordingly, the first resource information may include one or more of the first time-domain resource configuration, the first frequency-domain resource configuration, and the first preamble sequence resource configuration; the second resource information may include one or more of the second time-domain resource configuration, the second frequency-domain resource configuration, and the second preamble sequence resource configuration. The contents of the first resource information and the second resource information are described below in order to configure the first random access resource and the second random access resource.

[0145] 1) Temporal resource allocation

[0146] The first time-domain resource configuration includes a first PRACH configuration index, indicating the time-domain resources of the first random access resource. The terminal device can determine the time-domain resources corresponding to the first random access resource based on the first PRACH configuration index and the RA configuration table. The second time-domain resource configuration includes a second PRACH configuration index, indicating the time-domain resources of the second random access resource. The terminal device can determine the time-domain resources corresponding to the second random access resource based on the second PRACH configuration index and the RA configuration table. Through the first and second time-domain resource configurations, the network device configures independent PRACH Configuration Indexes for PRACH resources specific to the SBFD time unit and for PRACH resources not specific to the SBFD time unit. In other words, the time-domain resources, preamble format, etc., of the PRACH resources specific to the SBFD time unit are configured separately, and the time-domain resources, preamble format, etc., of the PRACH resources not specific to the SBFD time unit are also configured separately.

[0147] Alternatively, the second time-domain resource configuration includes a second PRACH configuration index, indicating the time-domain resources of the second random access resource. The first time-domain resource configuration includes a PRACH configuration index offset, which, along with the second PRACH configuration index, constitutes the first PRACH configuration index. The terminal device receives first resource information and second resource information, obtains the PRACH configuration index offset and the second PRACH configuration index, determines the first PRACH configuration index based on the PRACH configuration index offset and the second PRACH configuration index, and then determines the time-domain resources corresponding to the first random access resource based on the first PRACH configuration index and the RA configuration table.

[0148] 2) Frequency domain resource allocation

[0149] The first frequency domain resource configuration includes the starting frequency position of the lowest RO in the frequency domain of the first random access resource and / or the number of ROs in the FDM. The second frequency domain resource configuration includes the starting frequency position of the lowest RO in the frequency domain of the second random access resource and / or the number of ROs in the FDM.

[0150] Through first and second frequency domain resource configurations, the network device independently configures the frequency start position of the RO and / or the number of ROs for FDM for PRACH resources dedicated to SBFD time units and for PRACH resources not dedicated to SBFD time units. In other words, the network device separately configures the frequency start position of the RO and / or the number of ROs for FDM for PRACH resources dedicated to SBFD time units, and separately configures the frequency start position of the RO and / or the number of ROs for FDM for PRACH resources not dedicated to SBFD time units. Alternatively, the network device configures dedicated ROs for SBFD time units and dedicated ROs for non-SBFD time units.

[0151] Alternatively, the second frequency domain resource configuration includes the frequency starting position of the lowest RO in the frequency domain of the second random access resource and / or the number of ROs in the FDM. The first frequency domain resource includes a frequency offset and / or an RO number offset. Wherein, when the first frequency domain resource includes a frequency offset, the frequency starting position of the lowest RO in the frequency domain of the first random access resource is the sum of the frequency offset and the frequency starting position of the lowest RO in the frequency domain of the second random access resource. When the first frequency domain resource includes an RO number offset, the number of ROs in the first random access resource is the sum of the RO number offset and the number of ROs in the second random access resource.

[0152] 3) Preamble sequence resource configuration

[0153] The first preamble sequence resource configuration includes at least one parameter related to the first preamble sequence, which belongs to the preamble sequence corresponding to the PRACH resource associated with a non-SBFD time unit. The second preamble sequence resource configuration includes at least one parameter related to the second preamble sequence, which belongs to the preamble sequence corresponding to the PRACH resource associated with an SBFD time unit. Through the first and second preamble sequence resource configurations, the network device independently configures one or more parameters related to the preamble sequence for the PRACH resources associated with and non-SBFD time units. For details, please refer to the relevant description in "3-3) Preamble Sequence Resources" above.

[0154] It should be noted that the first resource information and the second resource information are sent independently, and there is no restriction on the order in which they are sent. Similarly, there is no restriction on the execution order of S401 and S402. For example, S402 can be executed after S401 or before S401.

[0155] It should be noted that the specific implementation of the above-mentioned first and second resource information takes the first and second random access resources as PRACH resources as an example. When the first and second random access resources are used for Msg3 or MsgA, the specific implementation of the first and second resource information is different.

[0156] S403. The network device sends the first information, and the terminal device receives the first information accordingly.

[0157] The first information indicates the conditions for using the first random access resource for random access. When the conditions indicated by the first information are met, the terminal device can use the first random access resource for random access. If the conditions indicated by the first information are not met, the terminal device cannot use the first random access resource for random access. It should be noted that the conditions for using the first random access resource for random access can be defined or agreed upon by the protocol. Therefore, S403 is an optional step, not a mandatory step. Figure 4 The image is indicated by a dashed line.

[0158] The conditions that must be met for random access using the first random access resource may include: conditions that the event triggering random access must meet, conditions that the terminal device must meet, or other possible conditions (such as random access latency requirements). The following lists the conditions that must be met for random access using the first random access resource.

[0159] (1) Triggering random access events.

[0160] The event that triggers random access can itself be considered a condition for using the first random access resource. Furthermore, the conditions for using the first random access resource for random access also include the conditions that the event that triggers random access must satisfy.

[0161] In this case, the first information may indicate information about at least one event for random access using the first random access resource. The information about at least one event may indicate the event itself, or it may indicate conditions that the event needs to meet. For example, the content indicated by the information about at least one event includes, but is not limited to, the following two types.

[0162] (1-1) Information about at least one event can indicate at least one event itself.

[0163] For example, the first information may indicate a first set of events, which includes at least one event, or the first set of events is a set consisting of at least one event. For the first set of events, random access triggered based on any event within the first set of events can use the first random access resource. For example, if the first event triggering random access satisfies the conditions indicated by the first information, then random access triggered based on the first event can use the first random access resource. The first event satisfying the conditions indicated by the first information includes the first event belonging to the first set of events, or the first event belonging to the first set of events being considered to satisfy the conditions for using the first random access resource. For the terminal device, if the first event triggering random access belongs to the first set of events, then random access triggered based on the first event determines that the first random access resource will be used.

[0164] The specific implementation of triggering random access for the first information indicating the first event set is not limited in the embodiments of this application.

[0165] For example, the first information may include the indexes of each event in the first event set.

[0166] Alternatively, if multiple events trigger random access, the events that use the first random access resource for random access can be grouped into a set (e.g., a first event set), or the events that cannot use the first random access resource for random access can not be grouped into a set (e.g., a second event set). In this case, the first information may include identification information of the first event set, such as the identifier (ID) of the first event set. Alternatively, the first information may include identification information of the second event set, such as the ID of the second event set. In this case, the terminal device, upon receiving the first information, considers the first event set to be a set of events excluding the second event set.

[0167] Alternatively, the N events that trigger random access can be sorted according to certain rules, where N is a positive integer. The first information can be a bitmap, which occupies N bits, with one bit corresponding to one or more events. The first event set can be a set of events corresponding to bit values ​​of "1" or "0".

[0168] Alternatively, multiple events triggering random access can be grouped according to protocol version, with the set of events corresponding to a single protocol version constituting the first event set. For example, protocol version 1 (e.g., R15) corresponds to event set 1, and protocol version 2 (e.g., R18) corresponds to event set 2. In this case, the first information may include an identifier of the protocol version, indicating the first event set through the protocol version. For example, if the first information includes an identifier of R15, then the first information indicates event set 1.

[0169] Optionally, the first information indicating a first event set includes indicating a second event set, which is a set of events for random access that does not use the first random access resource. The first information indicating the second event set is done in the same way as the first information indicating the first event set. For example, the first information includes the index of each event in the second event set, or the first information includes the ID of the second event set. In this case, the terminal device can determine, based on the first information, that random access triggered by events that do not belong to the second event set can use the first random access resource.

[0170] The embodiments of this application do not impose limitations on the signaling carrying the first information. Specific examples are given below to illustrate the signaling carrying the first information.

[0171] Example 1: The first piece of information is carried in a system message.

[0172] Network devices can indicate a first set of events via system messages; for example, a system message may carry first information. Any terminal device can determine the first set of events by receiving a system message. Carrying first information via system messages is applicable to all terminal devices.

[0173] Example 2: The first information is carried in the RRC reconfiguration message.

[0174] Network devices can send first information via RRC reconfiguration messages; for example, an RRC reconfiguration message may include first information. Sending first information via RRC reconfiguration messages allows a network device to indicate a first set of events to a specific terminal device. For example, a network device can use an RRC reconfiguration message to indicate the first set of events to a terminal device in a connected state. As another example, during cell handover for a terminal device, the source network device can use an RRC reconfiguration message to indicate the first set of events to the terminal device.

[0175] Example 3: The first information is carried in the RRC release message.

[0176] Network devices can send first information via an RRC release message, for example, the RRC release message includes first information. For example, for a terminal device in an RRC inactive state, the network device can indicate a first set of events when releasing the terminal device to enter the RRC inactive state.

[0177] (1-2) Information on at least one event may indicate the category of at least one event.

[0178] For example, the first information may indicate the category of at least one event. If the category of an event belongs to the category indicated by the first information, then random access triggered based on that event can use the first random access resource. For example, assuming the category indicated by the first information includes a first category, if the category of the first event that triggers random access is the first category, then random access triggered based on the first event can use the first random access resource. In other words, the condition for random access triggered based on the first event to use the first random access resource includes that the category of the first event is the first category.

[0179] There are multiple events that can trigger random access, and each event can be categorized. An event may correspond to one category or multiple categories. This application embodiment does not limit the method of categorizing multiple events. For example, they can be categorized according to the access scenario, as shown in Table 1. The first column of Table 1 represents the event category. For example, the categories of events triggering random access may include non-connectivity access, data transmission access, mobility scenario access, system message related access, beam management access, LBT failure access, or location scenario access. The second column of Table 1 shows the possible events that trigger random access. It should be noted that the events and categories in Table 1 are merely examples and may include more events or categories. Furthermore, this application embodiment does not limit the specific names of event categories, as long as the terminal device and network device have a consistent understanding of the category for the same event. For example, data transmission access and mobility scenario access in Table 1 can be merged into one category (e.g., called the service continuity category), and system message related access, beam management access, LBT failure access, and location scenario access in Table 1 can be merged into one category (e.g., called the other category). Other categories can also refer to categories other than disconnected access and service continuity.

[0180] Table 1

[0181]

[0182]

[0183] It should be noted that the category of each event can be predefined by the protocol, for example, Table 1 can be predefined. Alternatively, the category of each event can also be (pre)configured. For example, the network device can configure the category of at least one event that triggers random access to the terminal device, providing greater flexibility. Taking the first event as an example, the network device can send second information to the terminal device, which can be used to configure / determine the category of the first event. It is understood that the categories of other events besides the first event can also be configured through the second information.

[0184] Taking the first event as an example, assuming the category of the first event is Category 1, the second information may include the index of Category 1. Similar to the first information, the second information can also be carried in system messages, RRC reconfiguration messages, or RRC release messages. For the signaling carrying the second information, please refer to the relevant descriptions in Examples 1 to 3 above, which will not be repeated here.

[0185] It should be noted that the first event set can also be called the first event group, which is equivalent to dividing multiple events that trigger random access into multiple groups. At least one event belonging to the same category can be regarded as an event group or an event set.

[0186] When the first information indicates the category of at least one event, the first information may include identification information of the category to which the at least one event belongs. For example, if the at least one event is event 1, event 2, and event 3, and event 1 belongs to the first category, and events 2 and 3 both belong to the second category, then the first information may include the ID / index of the first category and the ID / index of the second category.

[0187] Optionally, the first information indicating the category of at least one event includes: the first information indicating a category other than the category of at least one event. In this case, if an event belongs to the category indicated by the first information, then random access triggered based on that event will not use the first random access resource for random access.

[0188] (2) The conditions for using the first random access resource for random access may include the first condition.

[0189] Here, the first condition can be other conditions unrelated to the event that triggered random access. For example, the first condition may include one or more of the following: the current random access latency is less than or equal to a first threshold, or the terminal device supports a first feature. When the first condition is met, the terminal device can use the first random access resource for random access. For example, if the terminal device supports the first feature, then the terminal device can use the first random access resource for random access; if the terminal device does not support the first feature, then the terminal device will not use the first random access resource for random access. As another example, if the current random access latency is less than or equal to the first threshold, then the terminal device can use the first random access resource for random access; if the current random access latency is greater than the first threshold, then the terminal device will not use the first random access resource for random access. The first condition can be (pre)configured or predefined. The first threshold can be (pre)configured or predefined.

[0190] S404. The terminal device determines whether to use the first random access resource for random access based on the first event that triggers random access.

[0191] When a terminal device performs random access, it can determine whether to use the first random access resource based on the first event that triggers the random access. For example, if the first event belongs to a first event set, the terminal device determines to use the first random access resource for random access; if the first event does not belong to the first event set, the terminal device determines not to use the first random access resource for random access. As another example, if the category indicated by the first information includes a first category, if the category of the first event is the first category, the terminal device determines to use the first random access resource for random access; if the category of the first event is not the first category, the terminal device determines not to use the first random access resource for random access.

[0192] Optionally, when the conditions for using the first random access resource for random access include the first condition, if the first condition is met, the terminal device determines to use the first random access resource for random access; if the first condition is not met, the terminal device determines not to use the first random access resource for random access. The process of not using the first random access resource for random access can be understood as the process of using the second random access resource for random access.

[0193] Optionally, when the first condition comprises multiple conditions, satisfying the first condition can mean satisfying all of these conditions or some of them. For example, if the first condition is condition 1 and condition 2, satisfying the first condition can mean satisfying both conditions 1 and 2 simultaneously, or satisfying either condition 1 or condition 2. For instance, condition 1 is that the terminal device supports a first feature, and condition 2 is that the current random access latency is less than or equal to a first threshold. When satisfying the first condition means satisfying either condition 1 or condition 2, then if the terminal device supports the first feature, the terminal device can determine to use the first random access resource for random access. When satisfying the first condition means satisfying both conditions 1 and 2, then if the terminal device supports the first feature, the terminal device can determine not to use the first random access resource for random access.

[0194] In addition, when determining whether to use the first random access resource for random access, the terminal device may consider whether the first condition is met, and whether the first event that triggered the random access meets the condition. For example, if the first condition is met, and the first event that triggered the random access belongs to the first event set or the category of the first event is the first category, then it is determined that the first random access resource will be used for random access.

[0195] If the terminal device determines to use the first random access resource for random access, then execute S405, that is, use the first random access resource for random access. If the terminal device determines not to use the first random access resource for random access, then execute S406, that is, use the second random access resource for random access.

[0196] S405. The terminal device uses the first random access resource to perform random access.

[0197] The terminal device using the first random access resource for random access can also be understood as the terminal device using the first random access resource to perform a random access procedure. For example, the terminal device uses the first random access resource to send a random access message, such as at least one of Msg1, Msg3, or Msg A.

[0198] S406. The terminal device uses the second random access resource for random access.

[0199] The terminal device using the second random access resource for random access can also be understood as the terminal device using the second random access resource to perform a random access procedure. For example, the terminal device uses the second random access resource to send a random access message, such as at least one of Msg1, Msg3, or Msg A.

[0200] If the terminal device sends Msg1 or Msg3 and does not receive a response message of Msg1 or Msg3, then the random access attempt is considered to have failed. The terminal device can increase its transmission power and re-initiate random access until the maximum number of access attempts corresponding to the second random access resource is reached. If no random access response is received after this, then the terminal device has failed to access the first random access resource. Therefore, Figure 4 S405 or S406 may be executed multiple times, with different Msg1 or Msg3 sent each time, and different transmission powers used.

[0201] Optionally, after receiving msg1 or msg3, the network device can further determine whether the first event triggering random access by the terminal device is an event that allows the use of the first random access resource. If the network device determines that the first event is an event that allows the use of the first random access resource, the network device continues to execute the RACH procedure. If the first event is not an event that allows the use of the first random access resource, the network device can reject this random access. If the network device rejects this random access, it will subsequently enter the random access failure procedure.

[0202] Optionally, if the network device rejects this random access, it may send a reason value to the terminal device for rejecting the random access. For example, the reason value may include: a first event does not allow the use of the first random access resource.

[0203] like Figure 4The communication method shown allows for the selective use of SBFD resources by appropriately configuring the conditions for triggering random access, such as events, event categories, and first conditions. This achieves the goal of rationally utilizing SBFD resources for RACH and improving random access performance. For example, if there are multiple events in Table 1, the two events corresponding to connectionless access can be configured to use the first random access resource. Random access events not triggered by connectionless access will not use the first random access resource. Consequently, the number of terminal devices using the first random access resource is relatively small, and the probability of collisions during random access on the first random access resource is correspondingly low, thus improving the access success rate of terminal devices, reducing access latency, and increasing access efficiency. Furthermore, network devices can flexibly configure the conditions for using the first random access resource according to the actual scenario to improve communication performance. For example, if the network can currently access more terminal devices, the network device can configure more events to use the first random access resource, thereby increasing network capacity.

[0204] The methods provided in the embodiments of this application above are described using terminal devices and network devices as examples. In this application, each embodiment can be implemented independently or in combination based on certain inherent connections; in each embodiment, different implementation methods can be implemented in combination or independently. To achieve the functions of the methods provided in the embodiments of this application above, the steps executed by the terminal device can be implemented by different functional entities constituting the terminal device. The steps executed by the network device can be implemented by different functional entities constituting the network device. For example, the network device can be a CU-DU architecture, where the CU can generate first resource information and the DU can send the first resource information. To achieve the functions of the methods provided in the embodiments of this application above, the terminal device and network device can include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or hardware structures plus software modules. Whether a particular function is executed in the form of hardware structures, software modules, or hardware structures plus software modules depends on the specific application and design constraints of the technical solution.

[0205] Based on the same inventive concept as the method embodiments, this application provides a communication device. The communication device used to implement the above method in the embodiments of this application is described below with reference to the accompanying drawings. The content above can be used in subsequent embodiments, and repeated content will not be repeated.

[0206] Figure 5 This is a schematic block diagram of a communication device 500 provided in an embodiment of this application. The communication device 500 can be a terminal device or a network device as described in the above embodiments. The communication device 500 can correspondingly implement the functions or steps implemented by the terminal device in the various method embodiments described above. For example, the communication device 500 can be... Figure 1 The communication device 500 can be a terminal device; or, the communication device 500 can be a chip (system) in the terminal device; or, the communication device 500 can be a software module of the terminal device. The communication device 500 can correspondingly implement the functions or steps implemented by the network device in the above method embodiments. For example, the communication device 500 can be... Figure 1 The communication device 500 can be a network device; or, the communication device 500 can be a chip (system) within the network device; or, the communication device 500 can be a software module of the network device. The communication device 500 may include a processing module 510 and a transceiver module 520. Optionally, it may also include a storage module, which can be used to store instructions (code or programs) and / or data. This storage module may be, for example, a memory. The processing module 510 and the transceiver module 520 may be coupled to the storage module. For example, the processing module 510 can read instructions (code or programs) and / or data from the storage module to implement a corresponding method. When the communication device 500 is a chip in a terminal device or network device, the storage module may be a storage module within the chip, such as a register, cache, etc. For example, the storage module may also be a storage module located outside the chip within the terminal device or network device, such as a read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions, random access memory (RAM), etc. The above-mentioned units can be set independently, or partially or completely integrated.

[0207] Processing module 510 may be a processor or controller, such as a general-purpose central processing unit (CPU), a general-purpose processor, a digital signal processing unit (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor may also be a combination that implements computing functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc. Transceiver module 520 is a transceiver, interface circuit, bus, pin, or other possible communication interface for receiving signals from other devices. For example, when the device is implemented as a chip, transceiver module 520 is an interface circuit for the chip to receive signals from other chips or devices, or an interface circuit for the chip to send signals to other chips or devices.

[0208] In one implementation, the communication device 500 can correspondingly implement the behavior and functions of the terminal device in the above method embodiments. The communication device 500 can be the terminal device, a component (e.g., a chip or circuit) applied in the terminal device, a chip or chipset in the terminal device, or a part of a chip used to perform the relevant method functions, or a software module capable of implementing the terminal device in the above methods; there are no limitations. For details, please refer to the relevant content of the foregoing method embodiments, which will not be repeated here.

[0209] For example, transceiver module 520 is used to receive first resource information, which indicates a first random access resource, the time domain resource of which includes SBFD time units. Processing module 510 is used to determine whether to use the first random access resource for random access based on a first event that triggers random access.

[0210] As an optional implementation, the processing module 510 is specifically used to: when the category of the first event is the first category, determine that the random access triggered by the first event uses the first random access resource.

[0211] As an optional implementation, the processing module 510 is specifically used to: when the first event belongs to the first event set, determine that the random access triggered by the first event uses the first random access resource.

[0212] As an optional implementation, the transceiver module 520 is used to receive first information indicating information about at least one event of random access using the first random access resource.

[0213] As an optional implementation, the information indicating at least one event for random access using the first random access resource includes: the first information indicating the category of at least one event; or, the first information indicating a first set of events, which includes at least one event.

[0214] As an optional implementation, the transceiver module 520 is used to receive second information, which is used to determine the category of the first event.

[0215] As an optional implementation method, the categories of events that trigger random access include at least one of the following: non-connectivity access, data transmission access, or mobility scenario access.

[0216] As an optional implementation, the first event includes one or more of the following: initial access in the RRC idle state, RRC connection re-establishment process, handover, SR failure, or the process of restoring the RRC connection from the RRC inactive state.

[0217] For example, the transceiver module 520 is used to receive first resource information. The processing module 510 is used to determine if a first condition is met, and then use the first random access resource for random access. The first resource information indicates the first random access resource, and the time-domain resource of the first random access resource includes SBFD time units. The first condition includes one or more of the following: the latency of the current random access is lower than a first threshold, or the terminal device supports a first feature.

[0218] In another implementation, the communication device 500 can correspondingly implement the behavior and functions of the network device in the above method embodiments. The communication device 500 can be a network device, a component (e.g., a chip or circuit) applied within a network device, a chip or chipset within a network device, or a part of a chip used to perform the relevant method functions, or a software module capable of implementing the network device in the above methods; there are no limitations. For details, please refer to the relevant content of the foregoing method embodiments, which will not be repeated here.

[0219] For example, the transceiver module 520 is used to send first resource information and first information, and to receive a random access message triggered by a first event using a first random access resource or a second random access resource. The first resource information indicates the first random access resource, whose time-domain resources include SBFD time units. The second random access resource's time-domain resources are non-SBFD time units. The first information indicates information about at least one event in which random access is performed using the first random access resource.

[0220] As an optional implementation, the transceiver module 520 is specifically used to: when the category of the first event is the first category, use the first random access resource to receive random access messages.

[0221] As an optional implementation, the transceiver module 520 is specifically used to: when the first event belongs to the first event set, use the first random access resource to receive random access messages.

[0222] As an optional implementation, the information indicating at least one event for random access using the first random access resource includes: the first information indicating the category of at least one event; or, the first information indicating a first set of events, which includes at least one event.

[0223] As an optional implementation, the transceiver module 520 is used to send second information, which is used to determine the category of the first event.

[0224] As an optional implementation method, the categories of events that trigger random access include at least one of the following: non-connectivity access, data transmission access, or mobility scenario access.

[0225] As an optional implementation, the first event includes one or more of the following: initial access to the RRC idle state, switching of the RRC connection re-establishment process, SR failure, or the process of restoring the RRC connection from the RRC inactive state.

[0226] For example, the transceiver module 520 is used to send first resource information and receive random access messages from the terminal device on the first random access resource. The first resource information indicates the first random access resource, and the time-domain resources of the first random access resource include SBFD time units. The random access message is triggered based on a first condition, which includes one or more of the following: the latency of the current random access is lower than a first threshold, or the terminal device supports a first feature.

[0227] When the communication device 500 is a chip-based device or circuit, the transceiver module can be an input / output circuit and / or a communication interface; the processing module is an integrated processor, microprocessor, or integrated circuit.

[0228] Figure 6 This is a schematic block diagram of a communication device 600 provided in an embodiment of this application. The communication device 600 can be a terminal device or a network device as described in the above embodiments. For example, the communication device 600 can be... Figure 1 The terminal device or the chip (system) within the terminal device. In the embodiments of this application, the chip system may be composed of chips or may include chips and other discrete devices. Specific functions can be found in the descriptions of the above method embodiments. For example, the communication device 600 may be... Figure 1 The network device or the chip (system) within the network device. In the embodiments of this application, the chip system may be composed of a chip, or it may include chips and other discrete devices. For specific functions, please refer to the description in the above method embodiments.

[0229] The communication device 600 includes one or more processors 601, used to implement or support the communication device 600 in implementing the functions of the terminal device or network device in the methods provided in the embodiments of this application. For details, please refer to the detailed description in the method examples, which will not be repeated here. The processor 601 can also be called a processing unit or processing module, and can implement certain control functions. The processor 601 can be a general-purpose processor or a dedicated processor, etc. For example, it includes: a baseband processor, a central processing unit, an application processor, a modem processor, a graphics processor, an image signal processor, a digital signal processor, a video codec processor, a controller, a memory, and / or a neural network processor, etc. The baseband processor can be used to process communication protocols and communication data. The central processing unit can be used to control the communication device 600 (e.g., a network device or a terminal device), execute software programs, and / or process data. Different processors can be independent devices or integrated into one or more processors, for example, integrated on one or more application-specific integrated circuits.

[0230] In one design, processor 601 may include program 603 (sometimes also referred to as code or instructions), which can be executed on processor 601 to cause communication device 600 to perform the methods described in the embodiments below. In yet another possible design, communication device 600 includes circuitry (…). Figure 6 (Not shown), the circuit is used to implement the functions of the terminal device or network device in the above embodiments.

[0231] In one design, the communication device 600 may include one or more memories 602 storing a program 604 (sometimes referred to as code or instructions), which can be run on the processor 601 to cause the communication device 600 to perform the methods described in the above method embodiments.

[0232] In one possible design, the processor 601 and / or memory 602 may also store data. The processor and memory may be configured separately or integrated together.

[0233] In one possible design, the communication device 600 may further include a transceiver 605 and / or an antenna 606. The processor 601, sometimes referred to as a processing unit, controls the communication device 600. The transceiver 605, sometimes referred to as a transceiver unit, transceiver, transceiver circuit, or transceiver, is used to implement the transmission and reception functions of the communication device 600 through the antenna 606.

[0234] In one possible design, the communication device 600 may further include one or more of the following components: a wireless communication module, an audio module, an external memory interface, internal memory, a universal serial bus (USB) interface, a power management module, an antenna, a speaker, a microphone, an input / output module, a sensor module, a motor, a camera, or a display screen, etc. It is understood that in some embodiments, the communication device 600 may include more or fewer components, or some components may be integrated, or some components may be separated. These components may be implemented in hardware, software, or a combination of software and hardware.

[0235] The communication device in the above embodiments can be a terminal device, a circuit, a chip applied in a terminal device, or other combined devices or components having the aforementioned terminal device. Alternatively, the communication device in the above embodiments can be a network device, a circuit, a chip applied in a network device, or other combined devices or components having the aforementioned network device. When the communication device is a terminal device or a network device, the transceiver module can be a transceiver, which may include an antenna and radio frequency circuits, etc., and the processing module can be a processor, such as a CPU. When the communication device is a chip system, the communication device can be an FPGA, a dedicated ASIC, a SoC, a CPU, a network processor (NP), a DSP, a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips. The processing module can be the processor of the chip system. The transceiver module or communication interface can be the input / output interface or interface circuit of the chip system. For example, the interface circuit can be a code / data read / write interface circuit. The interface circuit can be used to receive code instructions (the code instructions are stored in memory and can be read directly from memory or through other devices) and transmit them to the processor; the processor can then execute the code instructions to perform the methods described in the above method embodiments. Alternatively, the interface circuit can also be a signal transmission interface circuit between a communication processor and a transceiver.

[0236] This application also provides a communication system, which includes at least one terminal device and at least one network device. The terminal device is used to implement the functions related to the above-described communication method, and the network device is used to implement the functions related to the above-described communication method. Please refer to the relevant descriptions in the above method embodiments for details, which will not be repeated here.

[0237] This application also provides a computer-readable storage medium, including instructions that, when run on a computer, cause the computer to execute the method performed by the terminal device or network device in the above-described communication method.

[0238] This application also provides a computer program product, including computer program code, which, when executed, causes a computer to perform the method executed by the terminal device or network device in the above-described communication method.

[0239] This application provides a chip system including a processor and potentially a memory, for implementing the functions of a terminal device or network device in the aforementioned communication method. The chip system can be composed of chips or may include chips and other discrete components.

[0240] To achieve the above Figures 5-6 In addition to the functions of the communication device, this application also provides a chip, including a processor, for supporting the communication device in implementing the functions involved in the terminal device or network device in the above method embodiments. In one possible design, the chip is connected to a memory or the chip includes a memory for storing the computer programs or instructions and data necessary for the communication device.

[0241] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes 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.

[0242] Those skilled in the art will recognize that the various illustrative logical blocks and steps described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented 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 implementations should not be considered beyond the scope of this application.

[0243] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

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

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

[0246] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the essential contributing part of the technical solution of this application, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, external hard drives, ROM, RAM, magnetic disks, or optical disks.

[0247] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A communication method, characterized in that, include: Receive first resource information, which is used to indicate a first random access resource, wherein the time domain resource of the first random access resource includes a sub-band full-duplex SBFD time unit; Whether to use the first random access resource for random access is determined based on the first event that triggers random access.

2. The method as described in claim 1, characterized in that, The step of determining whether to use the first random access resource for random access based on the first event that triggers random access includes: When the category of the first event is the first category, it is determined that the random access triggered based on the first event uses the first random access resource.

3. The method as described in claim 1, characterized in that, The step of determining whether to use the first random access resource for random access based on the first event that triggers random access includes: When the first event belongs to the first event set, it is determined that the random access triggered based on the first event uses the first random access resource.

4. The method as described in claim 2 or 3, characterized in that, The method further includes: Receive first information, the first information indicating information about at least one event of random access using the first random access resource.

5. The method as described in claim 4, characterized in that, The first information indicates information about at least one event in which random access is performed using the first random access resource, including: The first information indicates the category of the at least one event; or, The first information indicates the first event set, which includes the at least one event.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: Receive second information, which is used to determine the category of the first event.

7. The method according to any one of claims 1-6, characterized in that, The categories of events that trigger random access include at least one of the following: non-connectivity access, data transmission access, or mobility scenario access.

8. The method according to any one of claims 1-7, characterized in that, The first event includes one or more of the following: Initial access in the idle state of Radio Resource Control (RRC); RRC connection re-establishment process; Switch; Scheduling request SR failure; or, The process of restoring RRC connection from the inactive state of RRC.

9. A communication method, characterized in that, include: Send first resource information, which is used to indicate a first random access resource, and the time domain resource corresponding to the first random access resource includes a sub-band full-duplex SBFD time unit. Send a first message, the first message indicating information about at least one event of random access using the first random access resource; Random access messages are received using either the first random access resource or the second random access resource, wherein the time domain resource of the second random access resource is a non-SBFD time unit.

10. The method as described in claim 9, characterized in that, Receiving random access messages using the first random access resource or the second random access resource includes: When the category of the first event is the first category, the random access message is received using the first random access resource.

11. The method as described in claim 9, characterized in that, Receiving random access messages using the first random access resource or the second random access resource includes: When the first event belongs to the first event set, the first random access resource is used to receive the random access message.

12. The method as described in claim 10 or 11, characterized in that, The first information indicates information about at least one event in which random access is performed using the first random access resource, including: The first information indicates the category of the at least one event; or, The first information indicates the first event set, which includes the at least one event.

13. The method according to any one of claims 9-12, characterized in that, The method further includes: Send a second message, which is used to determine the category of the first event.

14. The method according to any one of claims 9-13, characterized in that, The categories of events that trigger random access include at least one of the following: non-connectivity access, data transmission access, or mobility scenario access.

15. The method according to any one of claims 9-14, characterized in that, The first event includes one or more of the following: Initial access in the idle state of Radio Resource Control (RRC); RRC connection re-establishment process; Switch; Scheduling request SR failure; or, The process of restoring RRC connection from the inactive state of RRC.

16. A communication system, characterized in that, This includes network equipment and terminal equipment; The network device sends first resource information, which is used to indicate a first random access resource. The time domain resource of the first random access resource includes a sub-band full-duplex SBFD time unit. The terminal device determines whether to use the first random access resource for random access based on the first event that triggers random access. The network device uses the first random access resource or the second random access resource to receive random access triggered by the first event, wherein the time domain resource of the second random access resource is a non-SBFD time unit.

17. A communication device, characterized in that, It includes modules for performing the method as described in any one of claims 1-8, or modules for performing the method as described in any one of claims 9-15.

18. A communication device, characterized in that, The communication device includes at least one processor, the at least one processor being configured to cause the method of any one of claims 1-8 to be performed, or to cause the method of any one of claims 9-15 to be performed.

19. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program that, when run on a computer, causes the method as described in any one of claims 1-8 to be performed, or causes the method as described in any one of claims 9-15 to be performed.

20. A computer program product, characterized in that, The computer program product includes a computer program that, when run on a computer, causes the method as described in any one of claims 1-8 to be performed, or causes the method as described in any one of claims 9-15 to be performed.

21. A chip or chip system, characterized in that, The chip or chip system includes: At least one processor and an interface, the at least one processor being configured to call and execute instructions from the interface, such that when the at least one processor executes the instructions, the method as claimed in any one of claims 1-8 is executed, or the method as claimed in any one of claims 9-15 is executed.

Images