Communication method, apparatus and computer-readable storage medium

By collaborating between access network equipment and user equipment and utilizing the UL gap for sensing, the problem of low utilization of sensing resources in the millimeter wave band is solved, achieving high efficiency and flexibility in sensing operations.

WO2026103590A1PCT designated stage Publication Date: 2026-05-21HUAWEI TECH CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
HUAWEI TECH CO LTD
Filing Date
2025-11-05
Publication Date
2026-05-21

AI Technical Summary

Technical Problem

In existing technologies, access network equipment and user equipment in the millimeter wave band suffer from low resource utilization in terms of sensing capabilities, making it difficult to efficiently reuse uplink gaps (UL gaps) for sensing operations.

Method used

By collaborating between access network equipment and user equipment, UL gaps are utilized for sensing, including configuring and indicating sensing modes, uplink gap timing, and sensing data transmission resources, enabling flexible use of UL gaps.

Benefits of technology

It improves the utilization rate of UL gap resources, simplifies sensing operations, and enhances the efficiency and flexibility of sensing temporal resource utilization.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2025132777_21052026_PF_FP_ABST
    Figure CN2025132777_21052026_PF_FP_ABST
Patent Text Reader

Abstract

Provided in the present application are a communication method, an apparatus and a computer-readable storage medium, relating to the technical field of communications. The method comprises: receiving configuration information, the configuration information being used for configuring an uplink gap, and the uplink gap being used for transmission power management; receiving first information, the first information being used for indicating that the uplink gap is also used for sensing; and performing sensing by means of the uplink gap. In the embodiments of the present application, an uplink gap can be multiplexed to perform sensing.
Need to check novelty before this filing date? Find Prior Art

Description

Communication methods, devices and computer-readable storage media

[0001] This application claims priority to Chinese Patent Application No. 202411642100.4, filed on November 15, 2024, entitled "Communication Method, Apparatus and Computer-Readable Storage Medium", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a communication method, apparatus and computer-readable storage medium. Background Technology

[0003] With the evolution of mobile communication technology, the frequency bands used in wireless communication have also evolved to possess sensing capabilities, such as millimeter-wave bands. When access network equipment and user equipment adopt millimeter-wave bands, they will have radar-like sensing capabilities, thereby addressing sensing needs in many scenarios. These include autonomous / assisted driving, vehicle-to-everything (V2X) communication, intelligent transportation, 3D map reconstruction, smart industry, drone monitoring and management, intelligent interaction, and environmental monitoring. Summary of the Invention

[0004] This application discloses a communication method, apparatus, and computer-readable storage medium that can reuse uplink gaps (UL gaps) to perform sensing.

[0005] The first aspect discloses a communication method that can be applied to a user equipment, a module within the user equipment (e.g., a processor or chip), or a logic module or software capable of implementing all or part of the user equipment's functions. The following description, using an application to a user equipment as an example, includes: receiving configuration information for configuring an uplink gap for transmit power management; receiving first information indicating that the uplink gap is also used for sensing; and performing sensing through the uplink gap.

[0006] In this embodiment, the user equipment (UE) can receive configuration information from the access network device. This configuration information is used to configure a UL gap for the UE. The UE can also receive first information from the access network device. This first information can be used to indicate that the UL gap can be used for sensing. Accordingly, the UE can determine, based on the first information, that sensing can be performed through the UL gap, and subsequently, sensing can be performed through the UL gap. In this approach, the UL gap can be reused to perform sensing, clearly defining the temporal resources for sensing, which is simple and efficient. Furthermore, using the UL gap for sensing can also improve the utilization rate of UL gap resources.

[0007] In conjunction with the first aspect, in one possible implementation, the method further includes: receiving second information for indicating a sensing mode, the sensing mode including one or more of the following: user equipment self-transmission and self-reception, user equipment transmitting to access network equipment and receiving from user equipment A and user equipment B.

[0008] In this embodiment of the application, the user equipment can also receive second information from the access network device. The second information can be used to indicate the sensing mode adopted by the user equipment. The sensing mode can include one or more of the following: user equipment self-transmission and self-reception, user equipment transmitting to access network device and receiving, and user equipment A transmitting to user equipment B and receiving. This provides high flexibility.

[0009] In conjunction with the first aspect, in one possible implementation, the uplink gap includes a plurality of uplink gap opportunities, and the method further includes: receiving third information, the third information being used to indicate an uplink gap opportunity for sensing among the plurality of uplink gap opportunities included in the uplink gap; the sensing through the uplink gap includes: sensing through the uplink gap opportunity for sensing among the plurality of uplink gap opportunities included in the uplink gap.

[0010] In this embodiment of the application, the user equipment may also receive third information from the access network device so that the user equipment can accurately determine the UL gap timing used for sensing among the multiple UL gap timings included in the UL gap.

[0011] In conjunction with the first aspect, in one possible implementation, the third information includes a first ratio and / or the number N of uplink gap opportunities continuously used for sensing, the first ratio indicating the proportion of uplink gap opportunities used for sensing among the plurality of uplink gap opportunities included in the uplink gap; N is a positive integer.

[0012] In this embodiment of the application, the third information may include a first ratio and / or the number N of uplink gap opportunities continuously used for sensing. The UL gap resources used for sensing can be flexibly configured by the first ratio and / or the number N of uplink gap opportunities continuously used for sensing.

[0013] In conjunction with the first aspect, in one possible implementation, the method further includes: receiving fourth information, the fourth information being used to indicate a transmission resource for sensing data; and transmitting first sensing data, the first sensing data being sensed through the uplink gap, via the transmission resource for sensing data.

[0014] In this embodiment of the application, the user equipment may also receive fourth information from the access network device, so that the user equipment can subsequently send first sensing data to the access network device based on the resources indicated by the fourth information.

[0015] The second aspect discloses a communication method, which can be applied to an access network device, a module (e.g., a processor or chip) within the access network device, or a logic module or software capable of implementing all or part of the functions of the access network device. The following description, taking an application to a first network element as an example, includes: sending configuration information for configuring an uplink gap, the uplink gap being used for transmit power management; and sending first information indicating that the uplink gap is also used for sensing.

[0016] In this embodiment, the access network device can send configuration information to the user equipment (UE), which is used to configure a UL gap for the UE. The access network device can also send first information to the UE, which can be used to instruct the UL gap to be used for sensing. This approach allows the UE to be instructed to reuse the UL gap for sensing, clearly defining the temporal resources for sensing, and is simple and efficient. Furthermore, using the UL gap for sensing can improve the utilization rate of UL gap resources.

[0017] In conjunction with the second aspect, in one possible implementation, the method further includes: sending second information to indicate a sensing mode, the sensing mode including one or more of the following: user equipment self-transmission and self-reception, user equipment transmitting to access network equipment and receiving from user equipment A and user equipment B.

[0018] In this embodiment of the application, the access network device can also send second information to the user equipment. The second information can be used to indicate the sensing mode adopted by the user equipment. The sensing mode can include one or more of the following: user equipment self-transmission and self-reception, user equipment transmitting to access network device and receiving, and user equipment A transmitting to user equipment B and receiving. This provides high flexibility.

[0019] In conjunction with the second aspect, in one possible implementation, the uplink gap includes a plurality of uplink gap opportunities, and the method further includes: sending third information, the third information being used to indicate the uplink gap opportunity for sensing among the plurality of uplink gap opportunities included in the uplink gap.

[0020] In this embodiment of the application, the access network device may also send third information to the user equipment so that the user equipment can accurately determine the UL gap timing used for sensing among the multiple UL gap timings included in the UL gap based on the third information.

[0021] In conjunction with the second aspect, in one possible implementation, the third information includes a first ratio and / or the number N of uplink gap opportunities continuously used for sensing, the first ratio indicating the proportion of uplink gap opportunities used for sensing among the plurality of uplink gap opportunities included in the uplink gap; N is a positive integer.

[0022] In conjunction with the second aspect, in one possible implementation, the method further includes: sending fourth information, the fourth information being used to indicate a transmission resource for sensing data; and receiving first sensing data through the transmission resource for sensing data, the first sensing data being sensed through the uplink gap.

[0023] In this embodiment of the application, the access network device may also send fourth information to the user equipment so that the user equipment can subsequently send first sensing data to the access network device based on the resources indicated by the fourth information.

[0024] It should be noted that the technical solutions of the first aspect and the second aspect of this application correspond to each other, and the relevant beneficial effects can be referred to each other.

[0025] The third aspect discloses a communication device that has the functions of the first aspect described above. For example, the communication device includes a module or unit that performs the methods of the first aspect or any possible implementation of the first aspect. The module or unit can be implemented by software, hardware, or a combination of software and hardware.

[0026] For example, the communication device disclosed in the third aspect above may be a user equipment or a chip in a user equipment.

[0027] The fourth aspect discloses a communication device that has the functions of the second aspect described above. For example, the communication device includes a module or unit that performs the methods of the second aspect or any possible implementation of the second aspect. The module or unit can be implemented by software, hardware, or a combination of software and hardware.

[0028] For example, the communication device disclosed in the fourth aspect above may be an access network device or a chip in the access network device, etc.

[0029] The fifth aspect discloses a communication system comprising a user equipment and an access network device, the user equipment being configured to implement the methods provided in the first aspect and any possible embodiments thereof, and the access network device being configured to implement the methods provided in the second aspect and any possible embodiments thereof.

[0030] The sixth aspect discloses a communication device, including a processor and a communication interface; the communication interface is used to receive and / or transmit data; the processor invokes computer programs or computer instructions stored in a memory to implement the methods provided in the first aspect and any possible embodiments thereof, or to implement the methods provided in the second aspect and any possible embodiments thereof.

[0031] As one possible implementation, the communication device disclosed in the sixth aspect above may include one or more processors.

[0032] Optionally, the communication device disclosed in the sixth aspect above further includes one or more memories.

[0033] The seventh aspect discloses a computer-readable storage medium storing a computer program or computer instructions that, when executed, implement the methods provided in the first aspect and any possible embodiments thereof, or implement the methods provided in the second aspect and any possible embodiments thereof.

[0034] The eighth aspect discloses a chip including a processor for executing a program stored in a memory, which, when executed, causes the chip to perform the methods provided in the first aspect and any possible embodiments thereof, or to perform the methods provided in the second aspect and any possible embodiments thereof.

[0035] As one possible implementation, the memory is located outside the chip.

[0036] The ninth aspect discloses a computer program product comprising computer program code that, when executed, causes the methods provided in the first aspect and any possible implementation thereof to be performed, or causes the methods provided in the second aspect and any possible implementation thereof to be performed.

[0037] It should be understood that the implementation and beneficial effects of the above-mentioned aspects or any possible implementation methods of this application can be referred to each other. Attached Figure Description

[0038] The accompanying drawings are provided to more clearly illustrate the technical solutions of the embodiments of this application. The drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0039] Figure 1 is a schematic diagram of a sensor network architecture disclosed in an embodiment of this application;

[0040] Figure 2A is a schematic diagram of an architecture for the integrated deployment of SF and traditional core network disclosed in an embodiment of this application;

[0041] Figure 2B is a schematic diagram of an SF standalone deployment architecture disclosed in an embodiment of this application;

[0042] Figure 3 is a schematic diagram of the architecture of a communication system disclosed in an embodiment of this application;

[0043] Figure 4 is a schematic diagram of an open access network architecture disclosed in an embodiment of this application;

[0044] Figure 5 is a schematic diagram of a CU and DU protocol layer division disclosed in an embodiment of this application;

[0045] Figure 6 is a diagram showing the network element function division and protocol layer structure of an O-RAN device disclosed in an embodiment of this application;

[0046] Figure 7 is a schematic diagram of a CU-CP, CU-UP, DU protocol layer division disclosed in an embodiment of this application;

[0047] Figure 8 is a flowchart illustrating a communication method disclosed in an embodiment of this application;

[0048] Figure 9 is a schematic diagram of a sensing operation performed via a UL gap as disclosed in an embodiment of this application;

[0049] Figure 10 is a schematic diagram of the structure of a communication device disclosed in an embodiment of this application;

[0050] Figure 11 is a schematic diagram of the hardware structure of a communication device disclosed in an embodiment of this application. Detailed Implementation

[0051] This application discloses a communication method, apparatus, and computer-readable storage medium that can reuse uplink gaps (UL gaps) to perform sensing. The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0052] To better understand the embodiments of this application, the relevant content, terms or nouns involved in this application will be briefly introduced below.

[0053] I. Perception

[0054] Sensing is primarily achieved through the transmission of electromagnetic waves, enabling the perception of the electromagnetic wave propagation environment. This includes tasks such as detecting, locating, identifying, and imaging targets within that environment. For instance, access network devices or user equipment can acquire information such as signal strength, time difference, phase difference, and Doppler shift by sending and receiving wireless signals. Based on this information, they can calculate and process data to output information such as the target's distance, angle, speed, size, and shape.

[0055] With the development of communication technology, communication networks will also possess sensing capabilities. Integrated sensing and communication (ISAC) is a key technology in future wireless communication systems, aiming to integrate wireless communication and sensing functions into a single system. It utilizes the various propagation characteristics of wireless signals to achieve sensing functions such as target localization, detection, imaging, and identification, thereby acquiring information about the surrounding physical environment, improving communication performance, and enhancing user experience. In ISAC technology, user equipment and access network equipment can sense targets in the environment by sending sensing signals and receiving echo signals. The echo signal can be a signal generated by the sensing signal being reflected by targets in the environment. The time delay of the echo signal relative to the transmitted sensing signal reflects the target's distance, and the Doppler shift of the echo signal relative to the transmitted sensing signal reflects the target's velocity.

[0056] For example, the sensing capabilities of communication networks can be applied in scenarios such as autonomous / assisted driving, vehicle-to-everything (V2X) communication, intelligent transportation, 3D map reconstruction, smart industry, drone monitoring and management, intelligent interaction, environmental monitoring, and posture detection and recognition. For instance, high-precision dynamic maps can be generated based on perception to assist drones / intelligent vehicles in autonomous driving. Another example is that during the operation of intelligent vehicles / drones, dangerous events (such as the sudden appearance of people or objects) can be identified based on perception, and the intelligent vehicle / drone can be notified to perform emergency operations. Yet another example is that violations of driving rules can be identified based on perception, such as vehicles occupying emergency lanes or drones deviating from their flight paths. Yet another example is that abnormal postures can be identified based on perception and alerts can be issued, such as when a person falls. Finally, weather monitoring, pollution monitoring, and pest and disease monitoring can be performed based on perception.

[0057] II. Sensory Network Architecture

[0058] To support sensing functions, a new network architecture needs to be built. The following is an example of such a sensing network architecture. As shown in Figure 1, a sensing function (SF) network element can be added to the core network, along with interfaces between the SF network element and network elements such as the access and mobility management function (AMF), to facilitate interaction between the SF network element and the AMF. For example, the SF network element can be responsible for processing sensing services, such as providing sensing services, performing calculations based on sensing data, and sharing sensing results with third parties. The SF network element can also be called an SF functional unit / SF functional entity. In some possible implementations, sensing control signaling between the SF and the radio access network (RAN) / user equipment (UE) can be transmitted through the AMF or directly. Sensing measurement data acquired by the RAN / UE can be transmitted to the SF via the control plane or user plane. The user plane can be forwarded via the user plane function (UPF) or directly transmitted to the SF.

[0059] In some possible implementations, SF network elements can be deployed in sync with the traditional core network or independently. These two deployment methods are illustrated below with reference to Figures 2A and 2B. Please refer to Figure 2A, which is a schematic diagram of an architecture for SF network deployed in sync with the traditional core network according to an embodiment of this application. As shown in Figure 2A, in the sync architecture, the SF-control plane (SF-CP) can connect to the AMF, NEF, etc., in the traditional 5G core network, and can provide sensing services for the sensing application server, etc. Please also refer to Figure 2B, which is a schematic diagram of an architecture for SF network deployed independently according to an embodiment of this application. As shown in Figure 2B, in the independent deployment architecture, the SF-control plane (SF-CP) can be set up independently of the traditional 5G core network.

[0060] It should be noted that the architectures shown in Figures 1, 2A and 2B are merely illustrative examples and do not constitute a limitation on the embodiments of this application.

[0061] III. Perception Mode

[0062] It should be understood that an access network device or user equipment can function as both a sensing signal transmitter and a sensing signal receiver. Therefore, there are multiple combinations of transmitting and receiving sensing signals. Based on these different combinations, sensing methods (sensing modes) can be categorized into the following six types:

[0063] Access network devices are self-transmitting and self-receiving, meaning that the sensing signal is sent by the access network device, reflected by the target in the environment, and then received by the access network device itself.

[0064] Cooperation between access network devices (access network device A sends, access network device B receives), that is, the sensing signal is sent by access network device A, reflected by the target in the environment, and then received by access network device B;

[0065] Access network equipment sends signals, user equipment receives them; that is, the sensing signal is sent by the access network equipment, reflected by the target in the environment, and then received by the user equipment.

[0066] The user equipment sends signals to the access network equipment, which means that the sensing signals are sent by the user equipment, reflected by targets in the environment, and then received by the access network equipment.

[0067] User equipment self-transmission and self-reception means that the sensing signal is sent by the user equipment, reflected by the target in the environment, and then received by the user equipment.

[0068] User equipment collaboration (user equipment A sends, user equipment B receives), that is, the sensing signal is sent by user equipment A, reflected by the target in the environment, and then received by user equipment B.

[0069] IV. Sensing Signaling Interaction

[0070] Sensing signaling interaction can be divided into four modes based on the different network elements involved: signaling interaction between SF and access network equipment, signaling interaction between SF and UE, signaling interaction between access network equipment and UE, and signaling interaction between UEs. Taking the access network equipment as gNB as an example, the demand relationship between different sensing modes and the interaction between the three network elements (SF, gNB, UE) is summarized in Table 1 below:

[0071] Table 1

[0072] Among them, the gNB self-transmitting and self-receiving mode and the gNB A-transmitting and gNB B-receiving mode are both sensing operations conducted through the network side, requiring only interaction between the SF and gNB. The gNB-transmitting and UE-receiving modes require collaboration between the network side and the terminal side, necessitating interaction between the SF and gNB, the SF and UE, and the gNB and UE. For the UE self-transmitting and self-receiving modes and the UE A-transmitting and UE B-receiving modes, although the sensing process does not require the participation of the access network equipment, considering that all sensing resources are air interface resources and should be managed and allocated by the access network equipment, and that the UE needs to report its sensing capabilities, all four interaction methods can exist in these two sensing modes. It should be noted that in sensing modes involving the UE, assuming that the SF and UE interact through non-access stratum signaling, the interaction process can be transparent to the access network equipment.

[0073] The following is an exemplary description of the perception process, which generally consists of three steps: perception capability reporting → perception measurement configuration → perception measurement reporting. Perception capability reporting mainly involves the UE / gNB reporting its supported perception modes and related capabilities for perception signal processing, facilitating subsequent network perception measurement configuration. Perception measurement configuration mainly involves the SF configuring the UE / gNB for perception measurements, such as configuring the perception mode, the corresponding role under the perception mode (e.g., receive, transmit, receive & transmit), the reporting mode (e.g., periodic reporting, event reporting), and perception requirements (e.g., perception accuracy, perception resolution). Perception measurement reporting mainly involves the UE / gNB reporting perception measurement data to the SF or perception management terminal.

[0074] V. Perceiving Relevant Data

[0075] Depending on the sensing scenario and business requirements, the sensing signals received by the sensing device may need to be processed by one or more processing nodes, such as the UE, access network equipment, network data analytics function (NWDAF), SF, sensing application server, etc., to obtain the final sensing result.

[0076] The following table 2 shows a possible example of a hierarchical division of perception-related data:

[0077] Table 2

[0078] It should be noted that the division of perception-related data shown in Table 2 above is merely an illustrative example and does not constitute a limitation.

[0079] VI. Uplink gap (UL gap) mechanism

[0080] Release 17 (R17) introduced the UL gap mechanism. During the UL gap, the UE (User Equipment) does not transmit uplink (UL) signals by default, except for some special ULs specified in the standard. The initial purpose of the UL gap mechanism was to enable the UE to transmit a signal, and by detecting the reflected signal, determine whether the user equipment is near a human body. If no human body is nearby, the user equipment can increase its transmit power. Currently, the standard only describes that the UL gap can be used for transmit power management; the UL gap is essentially a UL gap used for transmit power management, and there are no specific regulations regarding the UE's behavior within the UL gap. The period, length, and offset of the UL gap can be configured by the network.

[0081] For example, the following is an exemplary description of the handling of the UL gap for transmit power management in frequency range 2 (FR2) according to the standard. During the FR2 UL gap configured in the UL-gapfr2-config specified in TS 38.331, the UE can transmit the following related ULs:

[0082] 1> The preamble for the physical random access channel (PRACH) as specified in Sections 5.1.2 and 5.1.2a of TS 38.321;

[0083] 1> The uplink shared channel (UL-SCH) or the payload of message A (MSG A) as specified in Section 5.4.2.2 of TS 38.321 used to transmit message 3 (Msg3);

[0084] 1> UL-SCH used for configuring authorization;

[0085] 1> Reporting of effective channel state information (CSI) during the activation process of the secondary cell (SCell);

[0086] 1> Report of valid layer 1 (L1) reference signal receiving power (RSRP) during SCell activation;

[0087] 1> Physical uplink control channel (PUCCH) transmission for schedule requests (SRs) and link recovery requests (LRRs) as defined in Section 8.5 of TS 38.133.

[0088] It should be noted that the above description of the UL gap is only an example; for more detailed information, please refer to the relevant description in the standard.

[0089] To better understand the embodiments of this application, the system architecture of the embodiments of this application will be described below.

[0090] Please refer to Figure 3, which is a schematic diagram of the architecture of a communication system disclosed in an embodiment of this application. As shown in Figure 3, the communication system may include a radio access network (RAN) 100 and a core network (CN) 200. RAN 100 includes at least one RAN node (RAN node 110a and RAN node 110b in Figure 3, hereinafter collectively referred to as RAN node 110) and at least one user equipment (user equipment 120a-120j in Figure 3, hereinafter collectively referred to as user equipment 120). RAN 100 may also include other RAN nodes, such as wireless relay equipment and / or wireless backhaul equipment (not shown in Figure 3). User equipment 120 can be wirelessly connected to RAN node 110. RAN node 110 can be wirelessly or wired connected to core network 200. The core network equipment in core network 200 and RAN node 110 in RAN 100 may be different physical devices, or they may be the same physical device integrating core network logical functions and radio access network logical functions.

[0091] User equipment (UE), also known as terminal equipment, terminal, mobile station (MS), mobile terminal (MT), or customer premises equipment (CPE), is a device with wireless communication capabilities that provides voice and / or data connectivity services to users. UEs can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), the Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, intelligent transportation, and smart cities.User equipment can include handheld terminals, laptops, RSUs (roadside units), subscriber units, cellular phones, smartphones, wireless data cards, personal digital assistant (PDA) computers, tablets, tags, wireless modems, other processing devices connected to wireless modems, handheld devices, laptop computers, cordless phones or wireless local loop (WLL) stations, machine-type communication (MTC) terminals, wearable devices (such as smartwatches, smart bracelets, pedometers, etc.), in-vehicle equipment (such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, smart home devices (such as refrigerators, televisions, air conditioners, electricity meters, etc.), intelligent robots, workshop equipment, wireless terminals in self-driving vehicles, and remote medical devices. Wireless terminals in various applications, including those related to surgery, smart grids, transportation safety, smart cities, smart homes, flying devices (such as intelligent robots, hot air balloons, drones, and airplanes), and other network-connected devices, are not limited to any particular form in this application. User equipment can be fixed or mobile, deployed on land (indoors or outdoors, handheld, wearable, or vehicle-mounted), on water (such as ships), or in the air (e.g., on airplanes, balloons, and satellites).

[0092] RAN node 110, also known as access network equipment, RAN entity, or access node, is a device deployed in the access network that enables wireless communication with user equipment (UE), facilitating UE wireless access. Multiple RAN nodes 110 in the communication system can be of the same type or different types. In some scenarios, the roles of RAN node 110 and UE 120 are relative. For example, network element 120i in Figure 3 can be a helicopter or drone, configured as a mobile base station. For UE 120j accessing RAN 100 via network element 120i, network element 120i is a base station; however, for base station 110a, network element 120i is a UE. RAN node 110 and UE 120 can both be referred to as communication devices. For example, network elements 110a and 110b in Figure 3 can be understood as communication devices with base station functionality, while network elements 120a-120j can be understood as communication devices with terminal functionality. Access network equipment can include radio access network (RAN) equipment. RAN equipment can include various types of base stations, such as macro base stations, micro base stations (also known as small stations), indoor stations (e.g., 110b in Figure 3), relay stations, donor nodes, access points, and balloon stations. The names of RAN equipment may differ in systems employing different radio access technologies. For example, in Long Term Evolution (LTE), there is the Evolved NodeB (eNB or eNodeB), and in 5th Generation (5G) mobile communication systems, there is the Next Generation NodeB (gNB) and the ng-eNB (4G base station accessing the 5G core network). Wireless access network equipment can also be wireless controllers in cloud radio access network (CRAN) scenarios, base station equipment in future networks, wireless access network equipment in future evolved public land mobile network (PLMN) networks, wearable devices, vehicles or in-vehicle equipment, RSUs, servers, transmission and reception points (TRPs), radio network controllers (RNCs), home base stations (e.g., home evolved NodeBs, or home Node Bs, HNBs), base band units (BBUs), access points (APs) in wireless fidelity (WiFi) systems, etc.

[0093] Core network equipment refers to the equipment in the core network (CN) that provides service support for user equipment. Core network equipment may include access and mobility management function (AMF) entities, session management function (SMF) entities, user plane function (UPF) entities, network exposure function (NEF) entities, SF entities, etc., which will not be listed here. Among them, the AMF entity is responsible for terminal access management and mobility management, the SMF entity is responsible for session management, such as user session establishment, and the UPF entity can be a user plane function entity responsible for connecting to external networks. More detailed descriptions of the relevant equipment / network elements in the core network can be found in the relevant standards, and will not be elaborated upon here.

[0094] RAN 100 can be a cellular system related to the 3rd Generation Partnership Project (3GPP), such as 4G mobile communication systems, 5G mobile communication systems, non-terrestrial network (NTN) systems, and future mobile communication systems. RAN 100 can also be an open RAN (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system, or a communication system integrating two or more of the above systems. For example, RAN 100 can be in transparent transmission mode or regenerative mode, or an earth-fixed cell or an earth-moving cell.

[0095] It should be understood that communication between access network equipment and user equipment follows a specific protocol layer structure. This protocol layer may include a control plane protocol layer and a user plane protocol layer. The control plane protocol layer may include at least one of the following: radio resource control (RRC) layer, packet data convergence protocol (PDCP) layer, radio link control (RLC) layer, media access control (MAC) layer, or physical (PHY) layer, etc. The user plane protocol layer may include at least one of the following: service data adaptation protocol (SDAP) layer, PDCP layer, RLC layer, MAC layer, or physical layer, etc.

[0096] In some deployments, such as O-RAN systems, access network equipment (e.g., gNB) may include centralized units (CUs) and distributed units (DUs). Access network equipment may also include radio units (RUs). For example, as shown in Figure 4, access network equipment can communicate with the core network (CN) via a backhaul link and with user equipment (UE) via an air interface (e.g., Uu interface). Specifically, the baseband unit (BBU) in the access network equipment can communicate with the core network via the backhaul link, and the radio unit in the access network equipment can communicate with the UE via the air interface. Furthermore, the BBU can communicate with the RU via a fronthaul link; the BBU and RU may or may not be co-located. The BBU may include at least one centralized unit (CU) and at least one distributed unit (DU), and the CU and DU can communicate via a midhaul link. The CU can implement some functions of the access network equipment (such as some protocol layer functions), and the DU can implement some functions of the access network equipment (such as some protocol layer functions). For example, as shown in Figure 5, the CU can implement the functions of the RRC and PDCP layers, and also the SDAP layer; the DU can implement the functions of the RLC and MAC layers, and also some physical layer functions (such as the higher physical, higher PHY layer) or all physical layer functions. The CU can connect to the DU through interfaces such as the F1 interface. The RU can be used to implement some physical layer functions (such as the lower physical layer) and radio frequency functions. It is understood that the above functional division is only an example and does not constitute a limitation on the CU and DU. The RU can be included in radio frequency equipment or radio frequency units, such as in a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH). For specific descriptions of the above protocol layers, please refer to the relevant technical specifications of the 3rd Generation Partnership Project (3GPP).

[0097] Please refer to Figure 6, which is a diagram showing the network element function division and protocol layer structure of an O-RAN device disclosed in an embodiment of this application. The following description is based on Figure 6.

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

[0099] In some examples, the CU can be split into a CU-control plane (CU-CP) and a CU-user plane (CU-UP). As shown in Figure 7, the CU-CP can be a logical node carrying the RRC and PDCP layer control plane (PDCP-C), used to implement the CU's control plane functions. The CU-CP can interact with network elements in the core network used to implement control plane functions. For example, the network element in the 5G core network used to implement control plane functions can be an AMF. The CU-UP can be a logical node carrying the SDAP and PDCP layer user plane (PDCP-U), used to implement the CU's user plane functions. The CU-UP can interact with network elements in the core network used to implement user plane functions. For example, the network element in the 5G core network used to implement user plane functions can be a UPF. The CU-CP and CU-UP can be connected via an E1 interface. It should be understood that the above CU and DU configurations are merely examples, and the functions of the CU and DU can be configured as needed. For example, a CU or DU can be configured to have more protocol layer functions, or it can be configured to have partial protocol layer processing functions. For instance, some functions of the RLC layer and the protocol layer functions above the RLC layer can be placed in the CU, while the remaining functions of the RLC layer and the protocol layer functions below the RLC layer can be placed in the DU. As another example, the functions of the CU or DU can be divided according to service type or other system requirements, such as by latency. Functions that need to meet low latency requirements can be placed in the DU, while functions that do not need to meet this latency requirement can be placed in the CU. In this embodiment, the CU can also be called O-CU (O-RAN CU), CU-CP can also be called O-CU-CP, and CU-UP can also be called O-CU-UP.

[0100] In some examples, a DU can be a logical node carrying the RLC layer, MAC layer, some physical layer functions (such as a higher physical (Higher PHY) layer), and other functions. In some examples, a DU can control at least one RU. The DU is connected to the RU through interfaces, which can be fronthaul interfaces. It should be understood that the higher physical layer can include parts of the physical layer processing; for example, higher physical layer functions can include one or more of the following: forward error correction (FEC) encoding / decoding, scrambling / descrambling, modulation / demodulation. In the embodiments of this application, the DU can also be referred to as an O-DU (O-RAN DU).

[0101] In some examples, the CU may not have a PDCP layer, i.e., it may only include the RRC layer. The CU-CP may not have PDCP-C. The CU-UP may not have PDCP-U, or may not have CU-UP at all. In some examples, the DU may not have an RLC layer, only MAC and higher PHY layers. Furthermore, in some examples, the access network device may not have a CU and may only include the DU.

[0102] In some examples, the RU can be a logical node carrying some physical layer functions (such as the lower physical (Lower PHY) layer) and radio frequency (RF) processing. In some examples, the RU can be a transmission reception point (TRP), a remote radio head (RRH), or other similar entities. In some examples, the lower physical layer can include parts of the physical layer processing; for example, lower physical layer functions can include one or more of the following: fast fourier transform (FFT), inverse fast fourier transform (IFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc. It should be understood that the RU can communicate with one or more UEs via a radio link (such as an air interface). In the embodiments of this application, the RU can also be referred to as an O-RU (O-RAN RU).

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

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

[0105] The O-RAN system may also include a RAN intelligent controller (RIC). RICs can be divided into near-real-time RICs (near-RT RIC / nRT RIC) and non-real-time RICs (non-RT RIC / NRT RIC).

[0106] Near real-time RIC refers to the near real-time portion, primarily used for near real-time intelligent management of the RAN. The near real-time RIC can achieve near real-time control and optimization of O-RAN modules and resources through data collection and related operations on the E2 interface. For example, the near real-time RIC can acquire information (such as network-side information, terminal-side information, etc.) from RAN nodes (e.g., CU, CU-CP, CU-UP, DU, RU, etc.), user equipment, non-real-time RICs, and other devices. It can then use this acquired information to train an artificial intelligence (AI) model, or input the acquired information into a trained AI model to obtain inference results. These inference results can be network parameters, such as RAN parameters (priority parameters, handover parameters, etc.). Optionally, the near real-time RIC can send the inference results to RAN nodes and / or user equipment. Optionally, inference results can be exchanged between CUs and DUs, and between DUs and RUs. For example, the near real-time RIC can send the inference results to the DU, and the DU can then send the inference results to the RU.

[0107] Non-real-time RIC refers to the non-real-time portion, primarily used for non-real-time intelligent management of RAN functions. Non-real-time RIC can implement AI / machine learning (ML) workflows, including model training and updates, and can guide applications / functions within the nRT RIC based on policies. For example, non-real-time RIC can acquire information (such as network-side information, terminal-side information, etc.) from RAN nodes (e.g., CU, CU-CP, CU-UP, DU, RU, etc.), user equipment, near-real-time RIC, and other devices, and then train AI models based on this information.

[0108] It is understood that in some possible implementations, the access network device may be a CU, DU, CU-CP, CU-UP, RU, etc., or may be a device including at least one of CU, DU, CU-CP, CU-UP, RU, etc.

[0109] It should be understood that the architectures shown in Figures 3, 4, and 6 are merely illustrative examples, and the architectures shown in Figures 3, 4, and 6 may also include other devices / network elements. This application embodiment does not limit this.

[0110] It is understood that the aforementioned access network equipment, user equipment, network elements, or functions can be implemented in the form of hardware, computer software (such as network management software, network control software, Layer 3 control software, Layer 2 control software, the management function part of the cloud terminal, etc.), or a combination of hardware and computer software. For example, the aforementioned access network equipment, user equipment, network elements, or functions can be implemented by a single device, by multiple devices working together, or by a functional module within a single device. This application embodiment does not specifically limit these aspects.

[0111] Furthermore, the aforementioned "network element" can also be referred to as an entity, functional entity, device, or module, etc., and this application does not limit it in this way. Moreover, for ease of description, the description "network element" can be omitted in some descriptions. For example, an AMF network element can be abbreviated as AMF. In this case, "AMF" should be understood as an AMF network element, an AMF entity, or an AMF functional entity, etc., and a similar understanding should be applied to other network elements or functions. That is to say, network element, entity, functional entity, device, or module, etc., can be equivalent; for example, SMF, SMF network element, and SMF entity can be equivalent.

[0112] It should be understood that the technical solutions provided in the embodiments of this application can be applied to various communication systems, such as fifth-generation (5G) communication systems, transitional systems between 5G and sixth-generation (6G) communication systems (which can also be called 5.5G communication systems), networks integrating multiple systems, and future communication systems.

[0113] It should be noted that the system architecture, network architecture, and business scenarios (or application scenarios) described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of communication network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0114] In this embodiment of the application, a technical solution for performing perception through a UL gap is provided, which can reuse the UL gap for UE perception. This is described below with reference to Figure 8. Please refer to Figure 8, which is a flowchart illustrating a communication method disclosed in this embodiment of the application. As shown in Figure 8, the method may include, but is not limited to, the following steps:

[0115] 801. The access network device sends configuration information to the user equipment. This configuration information is used to configure the uplink gap (UL gap), which is used for transmit power management.

[0116] For example, the configuration information can also be referred to as UL gap configuration information. The configuration information may include the UL gap period (e.g., 5ms, 20ms, etc.), the UL gap length (e.g., 0.125ms, 0.25ms, etc.), and the UL gap offset, etc., which are not limited in this embodiment. For a more detailed description of parameters such as the UL gap period, UL gap length, and UL gap offset, please refer to the relevant standards.

[0117] In some possible implementations, the UL gap may also be referred to as a UL gap for transmit power management, or a UL gap for transmit power management and sensing.

[0118] 802. The access network device sends first information to the user equipment. The first information is used to indicate the uplink gap and also for sensing.

[0119] In this embodiment, the access network device can send first information to the user equipment. Correspondingly, the user equipment can receive the first information from the access network device. The first information can be used to indicate that the uplink gap is used for sensing, that is, to indicate that the configured uplink gap is used for sensing, that is, to indicate that the user equipment uses the time-domain resources corresponding to the uplink gap for sensing, that is, to indicate that the user equipment can perform sensing based on the configured uplink gap. For example, the first information can be explicit indication information, which can explicitly indicate that the uplink gap is used for sensing; or, the first information can be implicit indication information (such as the second information described below), which can implicitly indicate that the uplink gap is used for sensing. For instance, when the access network device sends configuration information to configure the UL gap for the user equipment, it also sends second indication information indicating the corresponding sensing mode. In this case, the second indication information can implicitly indicate that the uplink gap is used for sensing.

[0120] Optionally, the access network device can also send second information to the user equipment. Accordingly, the user equipment can receive the second information from the access network device. This second information can be used to indicate a sensing mode, that is, to configure the user equipment to perform sensing within the UL gap. The sensing mode can include one or more of the following: user equipment self-transmitting and receiving, user equipment transmitting to the access network device and receiving, and user equipment A transmitting to user equipment B and receiving. For example, in some possible implementations, the second information can be used to instruct the user equipment to transmit sensing signals within the UL gap (such as sensing modes like user equipment transmitting to the access network device and user equipment A transmitting to user equipment B and receiving), or it can be used to instruct the user equipment to both transmit and receive sensing signals within the UL gap (such as a user equipment self-transmitting and receiving sensing mode).

[0121] It is understood that an uplink gap may include multiple uplink gap occasions. Optionally, the access network device may also send third information to the user equipment. Accordingly, the user equipment may receive the third information from the access network device, which may be used to indicate the uplink gap occasion used for sensing among the multiple uplink gap occasions included in the uplink gap. For example, the uplink gap occasion may also be referred to as the uplink gap period, uplink gap window, etc.

[0122] In some possible implementations, the third information may include a first ratio and / or the number N of consecutive uplink gap opportunities used for sensing. The first ratio can be used to indicate the proportion of uplink gap opportunities used for sensing out of a plurality of uplink gap opportunities, where N is a positive integer. For example, the first ratio may include multiple levels, such as 25%, 50%, 75%, etc. For instance, with 25%, in this case, the user equipment may use one uplink gap opportunity out of four (e.g., the first uplink gap opportunity out of every four) for sensing operations and three uplink gap opportunities for transmit power management. For example, taking 50% as an example, in this case, the user equipment can use one uplink gap timeout out of two uplink gap timeouts for sensing operations (e.g., the first uplink gap timeout out of every two uplink gap timeouts) and one uplink gap timeout for transmit power management. Alternatively, it can use two uplink gap timeouts out of four uplink gap timeouts for sensing operations and two uplink gap timeouts for transmit power management. It should be understood that the above example of the first proportion only divides multiple levels, offering high flexibility. In some possible implementations, it can also be specified that L uplink gap timeouts out of every M uplink gap timeouts are used for sensing. Here, M and L are positive integers, and M is greater than or equal to L.

[0123] The number N consecutive uplink gaps used for sensing can be used to indicate whether to perform a sensing operation using N consecutive uplink gaps. For example, if N is 2, the user equipment can use two consecutive uplink gaps to perform a sensing operation.

[0124] It should be noted that the above-described resource allocation for uplink gaps for sensing and transmit power management is merely illustrative and does not constitute a limitation. In other possible embodiments of this application, other allocation methods may also be used; for example, allocation may be performed for each uplink gap timing.

[0125] Optionally, the access network device can also send fourth information to the user equipment. Accordingly, the user equipment can receive the fourth information from the access network device, which can be used to indicate the transmission resources for the sensed data. For example, in some possible implementations, for scenarios where the user equipment transmits and receives data independently, the access network device can also send the fourth information to the user equipment to indicate the timing of the sensed data transmission, such as indicating that sensed data is transmitted at the Xth PUSCH after the UL gap ends, that is, indicating that sensed data is transmitted at an offset of X PUSCH, where X is a positive integer.

[0126] It should be noted that in some possible implementations, at least two of the above-mentioned configuration information, first information, second information, third information, and fourth information can be carried in the same message (such as a message for configuring the UL gap). For example, if the configuration information and the first information are carried in the same message, in this case, the access network device can indicate that the configured UL gap can be used for sensing while configuring the UL gap for the user equipment.

[0127] 803. User equipment senses through uplink gaps.

[0128] For example, after receiving first information from the access network device, the user equipment (UE) can determine that the uplink gap can be used for sensing based on the first information. Accordingly, the UE can perform sensing through the uplink gap. This sensing through the uplink gap can include the UE transmitting a sensing signal through the uplink gap, or it can include both transmitting and receiving sensing signals through the uplink gap. For example, as shown in Figure 9, assuming the uplink gap period includes uplink gap period 1 to uplink gap period 3, where the UL gap resource corresponding to uplink gap period 2 can be used for sensing, and the UL gap resources corresponding to uplink gap period 1 and uplink gap period 3 can be used for transmit power management. In this case, the UE can perform sensing operations through the UL gap resource corresponding to uplink gap period 2.

[0129] In some possible implementations, the user equipment (UE) may also receive second information from the access network device. In this case, the UE can perform sensing through uplink gaps based on the second information. For example, assuming the sensing mode indicated by the second information is UE self-transmission and self-reception, the UE can send and receive sensing signals, and subsequently report corresponding sensing data (such as sensing measurement data, sensing results, etc.). As another example, assuming the sensing mode indicated by the second information is UE-transmitting and access network-receiving, the UE can send sensing signals, and the access network device can receive sensing signals (such as reflected or scattered signals of the sensing signals sent by the UE). Subsequently, the access network device can obtain sensing data (such as sensing measurement data, sensing results, etc.).

[0130] In some possible implementations, the user equipment may also receive third information from the access network equipment. In this case, the user equipment can sense the uplink gap timing among the multiple uplink gap timings included in the uplink gap indicated by the third information.

[0131] In some possible implementations, the third information may include a first ratio and / or the number N of consecutive uplink gaps used for sensing. The user equipment can determine the uplink gaps for sensing based on the first ratio and / or the number N of consecutive uplink gaps used for sensing. For example, assuming the first ratio is 50% and N is 2, in this case, the user equipment can determine that the first two uplink gaps out of every four uplink gaps can be used for sensing, or it can determine that the middle two uplink gaps out of every four uplink gaps can be used for sensing, or it can determine that the last two uplink gaps out of every four uplink gaps can be used for sensing.

[0132] In some possible implementations, the user equipment may also receive fourth information from the access network device. After the user equipment obtains the first sensing data through uplink gaps, it can send the first sensing data to the access network device through the sensing data transmission resources indicated by the fourth information. Correspondingly, the access network device can receive the first sensing data, which is obtained through uplink gaps, through the sensing data transmission resources indicated by the fourth information.

[0133] For example, this application embodiment introduces the transmission of uplink signals for sensing (such as a channel sounding reference signal (SRS) for sensing) within the UL gap, and the optional corresponding condition is that sensing is configured, that is, the UL gap is configured for sensing. In conjunction with the description in the above related technologies, the UE can transmit the following related UL:

[0134] 1> The preamble for the physical random access channel (PRACH) as specified in Sections 5.1.2 and 5.1.2a of TS 38.321;

[0135] 1> The uplink shared channel (UL-SCH) or MSGA payload specified in Section 5.4.2.2 of TS 38.321 used to transmit message 3 (Msg3);

[0136] 1> UL-SCH used for configuring authorization;

[0137] 1> Reporting of effective channel state information (CSI) during the activation process of the secondary cell (SCell);

[0138] 1> Report of valid layer 1 (L1) reference signal receiving power (RSRP) during SCell activation;

[0139] 1> Physical uplink control channel (PUCCH) transmission for SR, and link recovery request (LRR) as defined in Section 8.5 of TS 38.133;

[0140] 1> If the user equipment is instructed to perform a sensing operation:

[0141] 2> Send uplink signals for sensing.

[0142] In some possible implementations, when the uplink sensing reference signal is the SRS, the access network device can configure the user equipment (UE) with transmission resources for the sensing SRS, such as the period of the sensing SRS. In this case, if the sensing SRS and the UL gap do not completely overlap, that is, if the transmission resources for the sensing SRS do not completely overlap with the resources corresponding to the UL gap, in one possible implementation, the UE can transmit the sensing SRS only within the UL gap, and not transmit it outside the UL gap. In this way, the portion of the transmission resources for the sensing SRS that does not overlap with the UL gap can be used to transmit other uplink / downlink signals, saving transmission resources and improving resource utilization.

[0143] It should be noted that in some possible implementations, the user equipment can simultaneously perform sensing and transmission power management based on the UL gap, and this application embodiment does not limit this. For example, when performing sensing based on the UL gap, the user equipment can detect whether it is near a human body based on the reflected signal of the received sensing signal. If there is no human body nearby, the user equipment can increase the transmission power.

[0144] In the above processing flow, the access network device can instruct the user equipment to perform sensing using the UL gap, that is, to use the UL gap as a time domain resource for sensing, and to reuse existing related UL gap mechanisms.

[0145] It is understood that the technical solutions provided in this application can be used in the architecture of an open access network. The operations performed by the access network device can be executed by one or more nodes such as CU, DU, CU-CP, CU-UP, and RIC (e.g., near-RT RIC, Non-RT RIC). Information sent by the user equipment to the access network device can be sent to nodes such as CU, DU, CU-CP, CU-UP, or RIC (e.g., near-RT RIC, Non-RT RIC), and this application does not limit this. For example, the access network device can send relevant information to the user equipment through CU, DU, CU-CP, CU-UP, or RIC, such as the aforementioned configuration information, first information, second information, third information, and fourth information.

[0146] It should be noted that the relevant information and descriptions in the different embodiments described above can be referenced from each other.

[0147] It should be understood that Figure 8 above primarily uses user equipment and access network equipment as examples of the execution entities in the interaction illustration to illustrate the above processing flow, but this application does not limit the execution entities in this interaction illustration. For example, the user equipment in Figure 8 can also be a chip, chip system, or processor that supports the user equipment in implementing the method, or it can be a logic module or software that can implement all or part of the user equipment. Similarly, the access network equipment in Figure 8 can also be a chip, chip system, or processor that supports the access network equipment in implementing the method, or it can be a logic module or software that can implement all or part of the access network equipment's functions.

[0148] The foregoing mainly describes the communication method provided in the embodiments of this application. It is understood that, in order to achieve the corresponding functions, the user equipment and access network equipment described above may include hardware structures and / or software modules corresponding to the execution of each function. Based on the units and steps of the various examples described in the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the embodiments of this application.

[0149] This application embodiment can divide user equipment and access network equipment into functional modules according to the above method examples. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0150] Figure 10 shows a possible structural diagram of the communication device 1000, where each functional module is divided according to its corresponding function. The communication device 1000 includes a communication unit 1001. Optionally, the communication unit 1001 may also be referred to as a transceiver unit, an output unit, or an interface unit, etc. In one possible implementation, the communication unit 1001 includes at least one of a transmitting unit or a receiving unit. The transmitting unit and the receiving unit may be integrated together, or they may be two independent units, etc. Optionally, the communication device 1000 may also include a processing unit 1002. In one possible design, the communication device 1000 may be the aforementioned user equipment, or it may be a component within the user equipment (e.g., a processor, chip, chip system, circuit, or functional module), or it may be a processing system within the user equipment, etc.

[0151] When the communication device 1000 is used for the functions of the user equipment in the embodiment shown in FIG8 above, for example:

[0152] The communication unit 1001 is used to receive configuration information, which is used to configure uplink gaps, and the uplink gaps are used for transmit power management.

[0153] The communication unit 1001 is also configured to receive first information, which indicates that the uplink gap is also used for sensing;

[0154] The communication unit 1001 is also used for sensing through the uplink gap.

[0155] For example, the communication unit 1001 can sense through the uplink gap by sending a sensing signal through the uplink gap.

[0156] In one possible implementation, the communication unit 1001 is further configured to receive second information, which indicates a sensing mode, including one or more of the following: user equipment self-transmission and self-reception, user equipment transmitting to access network equipment and receiving from user equipment A and user equipment B.

[0157] In one possible implementation, the uplink gap includes multiple uplink gap opportunities. The communication unit 1001 is further configured to receive third information, which indicates the uplink gap opportunity used for sensing among the multiple uplink gap opportunities included in the uplink gap. The communication unit 1001 sensing through the uplink gap includes sensing through the uplink gap opportunity used for sensing among the multiple uplink gap opportunities included in the uplink gap.

[0158] In one possible implementation, the third information includes a first proportion and / or the number N of uplink gap opportunities used for sensing consecutively, the first proportion indicating the proportion of uplink gap opportunities used for sensing among the multiple uplink gap opportunities included in the uplink gap; N is a positive integer.

[0159] In one possible implementation, the communication unit 1001 is further configured to receive fourth information, which is used to indicate the transmission resources for sensing data; the communication unit 1001 is further configured to transmit first sensing data through the transmission resources for sensing data, which is obtained by sensing through the uplink gap.

[0160] The specific operation of each unit in the above-mentioned communication device 1000 can be found in the description of the user equipment in the embodiment shown in Figure 8 above, and will not be repeated here.

[0161] In another possible design, the communication device 1000 may be the aforementioned access network equipment, or it may be a component (e.g., a processor, chip, chip system, circuit or functional module) in the access network equipment, or it may be a processing system in the access network equipment, etc.

[0162] When the communication device 1000 is used for the function of the access network device in the embodiment shown in FIG8 above, for example:

[0163] The communication unit 1001 is used to send configuration information, which is used to configure the uplink gap, and the uplink gap is used for transmit power management.

[0164] The communication unit 1001 is also used to send first information, which is used to indicate that the uplink gap is also used for sensing.

[0165] In one possible implementation, the communication unit 1001 is further configured to transmit second information, which indicates a sensing mode, including one or more of the following: user equipment self-transmission and self-reception, user equipment transmitting to access network equipment and receiving from user equipment A and user equipment B.

[0166] In one possible implementation, the uplink gap includes multiple uplink gap opportunities, and the communication unit 1001 is further configured to send third information, which is used to indicate the uplink gap opportunity used for sensing among the multiple uplink gap opportunities included in the uplink gap.

[0167] In one possible implementation, the third information includes a first proportion and / or the number N of uplink gap opportunities used for sensing consecutively, the first proportion indicating the proportion of uplink gap opportunities used for sensing among the multiple uplink gap opportunities included in the uplink gap; N is a positive integer.

[0168] In one possible implementation, the communication unit 1001 is further configured to send fourth information, which is used to indicate the transmission resources for sensing data; the communication unit 1001 is further configured to receive first sensing data through the transmission resources for sensing data, which is obtained by sensing through the uplink gap.

[0169] The specific operation of each unit in the above-mentioned communication device 1000 can be found in the description of the access network device in the embodiment shown in Figure 8 above, and will not be repeated here.

[0170] In one possible implementation, in the communication device shown in Figure 10, the processing unit can be one or more processors / logic circuits, and the communication unit can be a transceiver. Alternatively, the communication unit can also be a transmitting unit and a receiving unit, where the transmitting unit can be a transmitter and the receiving unit can be a receiver. The transmitting and receiving units are integrated into a single device, such as a transceiver. In this embodiment, the processor and transceiver can be coupled, etc., and the connection method between the processor and transceiver is not limited in this embodiment. During the execution of the above method, the process of sending information (such as sending configuration information) can be understood as the process of the processor outputting the information. When outputting the information, the processor outputs the information to the transceiver so that the transceiver can transmit it. After being output by the processor, the information may require further processing before reaching the transceiver. Similarly, the process of receiving information (such as receiving configuration information) in the above method can be understood as the process of the processor receiving the input information. When the processor receives the input information, the transceiver receives the information and inputs it into the processor. Furthermore, after the transceiver receives the aforementioned information, the information may need to undergo further processing before being input into the processor.

[0171] In another possible implementation, in the communication device shown in Figure 10, the processing unit can be one or more processors / logic circuits. The communication unit can be an input / output interface, or it can be both an input interface and an output interface. The input / output interface can also be called a communication interface, an interface circuit, or an interface, etc.

[0172] Figure 11 shows a possible hardware structure diagram of the communication device 1100 provided in an embodiment of this application. The communication device 1100 may include a communication interface 1104 and at least one processor 1102. Optionally, it may also include a bus 1103. Further optionally, it may also include at least one memory 1101, wherein the memory 1101, the processor 1102 and the communication interface 1104 can be connected through the bus 1103.

[0173] The memory 1101 provides storage space, which can store data such as the operating system and computer programs. The memory 1101 can be one or a combination of multiple types of random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM).

[0174] Processor 1102 is a module that performs arithmetic and / or logical operations. Specifically, it can be one or a combination of processing modules such as a central processing unit (CPU), graphics processing unit (GPU), microprocessor unit (MPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), complex programmable logic device (CPLD), coprocessor (assisting the CPU in completing corresponding processing and applications), and microcontroller unit (MCU). For example, processor 1102 can be used to process communication protocols and communication data.

[0175] The communication interface 1104 is used to receive and / or transmit data to external sources. Optionally, the communication interface 1104 may also include a transmitter (such as an RF transmitter, antenna, etc.) and / or a receiver coupled to the interface. For example, the communication interface 1104 may include a control circuit and an antenna. The control circuit is mainly used for converting baseband signals to RF signals and processing RF signals. The antenna is mainly used for transmitting and receiving RF signals in the form of electromagnetic waves. When data needs to be transmitted wirelessly, the processor 1102 performs baseband processing on the data to be transmitted and outputs a baseband signal to the control circuit. The control circuit then performs RF processing on the baseband signal and transmits the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the control circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor 1102. The processor 1102 converts the baseband signal back into data and processes the data.

[0176] In one possible implementation, the control circuitry and antenna can be set up independently of the processor performing baseband processing. For example, in a distributed scenario, the control circuitry and antenna can be arranged in a remote manner, independent of the communication device.

[0177] In one design, the communication device 1100 can be used to perform the functions of the user equipment in the embodiment shown in FIG8. For details, please refer to the relevant description of the user equipment in FIG8 above, which will not be repeated here.

[0178] In another design, the communication device 1100 can be used to perform the functions of the access network device in the embodiment shown in FIG8. For details, please refer to the relevant description of the access network device in FIG8 above, which will not be repeated here.

[0179] In one possible design, the memory 1101 may store instructions, which may be computer programs that run on the processor 1102 and cause the communication device 1100 to perform operations performed by the user equipment or the access network device in any of the above method embodiments. For details, please refer to the relevant description in Figure 8 above, which will not be elaborated here.

[0180] It should be noted that the communication device 1100 shown in Figure 11 is only one implementation of the embodiment of this application. In actual applications, the communication device 1100 may include more or fewer components, which is not limited here.

[0181] It should be understood that the transmission in the embodiments of this application can be direct or indirect. Direct transmission means that one device or module directly sends information / data to the corresponding device or module, while indirect transmission means that one device or module sends information / data to the corresponding device or module through other devices or modules.

[0182] Obviously, the embodiments described above are only some embodiments of this application, and not all embodiments. The term "embodiment" as used herein means that a specific feature, structure, or characteristic described in connection with an embodiment can be included in at least one embodiment of this application. The appearance of this phrase in various places in the specification does not necessarily indicate the same embodiment, nor is it an independent or alternative embodiment mutually exclusive with other embodiments. Those skilled in the art will understand, explicitly and implicitly, that the embodiments described herein can be combined with other embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without inventive effort are within the scope of protection of this application. The terms "first," "second," "third," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects and are not used to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, it may include a series of steps or units, or optionally, steps or units not listed, or optionally other steps or units inherent to these processes, methods, products, or devices. It is also understandable that, for an architecture with multiple devices or modules, if one device or module generates a piece of information and another device or module uses that information, there are multiple ways for the other device to obtain that information. For example, the device or module that generated the information may send the information directly to the device or module that used the information (equivalent to direct sending), or the device or module that generated the information may send the information to the device or module that used the information through other devices or modules (equivalent to indirect sending).

[0183] It is understood that the accompanying drawings show only the parts relevant to this application and not all of them. It should be understood that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although the flowcharts describe operations (or steps) as sequential processes, many of these operations can be performed in parallel, concurrently, or simultaneously. Furthermore, the order of the operations can be rearranged. The process can be terminated when its operation is completed, but may also have additional steps not included in the drawings. The process can correspond to a method, function, procedure, subroutine, subroutine, etc.

[0184] The terms “component,” “module,” “system,” “unit,” etc., used in this specification are used to refer to computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution. For example, a unit can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, a thread of execution, a program, and / or distributed between two or more computers. Furthermore, these units can be executed from various computer-readable media on which various data structures are stored. For example, a unit can communicate via local and / or remote processes based on signals having one or more data packets (e.g., data from a second unit interacting with another unit between a local system, a distributed system, and / or a network; for example, the Internet interacting with other systems via signals).

[0185] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of this application. It should be understood that the above description is only a specific embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solution of this application should be included within the scope of protection of this application.

Claims

1. A communication method, characterized in that, include: Receive configuration information, the configuration information being used to configure uplink gaps, the uplink gaps being used for transmit power management; Receive first information, the first information being used to indicate the uplink gap and also for sensing; Sensing is achieved through the uplink gap.

2. The method according to claim 1, characterized in that, The method further includes: Receive second information, which is used to indicate a sensing mode, the sensing mode including one or more of the following: user equipment self-transmission and self-reception, user equipment transmitting to access network equipment and receiving from user equipment A and user equipment B.

3. The method according to claim 1 or 2, characterized in that, The uplink gap includes multiple uplink gap timings, and the method further includes: Receive third information, the third information being used to indicate the uplink gap timing used for sensing among the multiple uplink gap timings included in the uplink gap; The sensing via the uplink gap includes: Sensing is performed using the uplink gap timings among the multiple uplink gap timings included in the uplink gap.

4. The method according to claim 3, characterized in that, The third information includes a first ratio and / or the number N of uplink gap opportunities used for sensing consecutively, wherein the first ratio is used to indicate the proportion of uplink gap opportunities used for sensing among the multiple uplink gap opportunities included in the uplink gap. N is a positive integer.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: Receive fourth information, which is used to indicate the resources for transmitting the sensed data; The first sensing data is transmitted through the sensing data transmission resources, and the first sensing data is obtained through the uplink gap.

6. A communication method, characterized in that, include: Send configuration information, which is used to configure uplink gaps, and the uplink gaps are used for transmit power management; Send a first message, which is used to indicate that the uplink gap is also used for sensing.

7. The method according to claim 6, characterized in that, The method further includes: Send a second message, which indicates a sensing mode, the sensing mode including one or more of the following: user equipment self-transmission and self-reception, user equipment transmitting to access network equipment and receiving from user equipment A and user equipment B.

8. The method according to claim 6 or 7, characterized in that, The uplink gap includes multiple uplink gap timings, and the method further includes: Send a third message, the third message being used to indicate the uplink gap timing used for sensing among the multiple uplink gap timings included in the uplink gap.

9. The method according to claim 8, characterized in that, The third information includes a first ratio and / or the number N of uplink gap opportunities used for sensing consecutively, wherein the first ratio is used to indicate the proportion of uplink gap opportunities used for sensing among the multiple uplink gap opportunities included in the uplink gap. N is a positive integer.

10. The method according to any one of claims 6-9, characterized in that, The method further includes: Send a fourth message, which is used to indicate the resources for sending the sensed data; The first sensing data is received through the transmission resources of the sensing data, and the first sensing data is obtained by sensing through the uplink gap.

11. A communication system, characterized in that, It includes user equipment and access network equipment, wherein the user equipment is used to implement the method according to any one of claims 1-5, and the access network equipment is used to implement the method according to any one of claims 6-10.

12. A communication device, characterized in that, Includes modules for implementing the method as described in any one of claims 1-10.

13. A communication device, characterized in that, The device includes a processor and a transceiver, the transceiver being used to send and receive information, and the processor being used to enable the communication device to implement the method as described in any one of claims 1-10.

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

15. A computer program product, characterized in that, The computer program product includes computer program code or computer instructions, which, when executed, implement the method described in any one of claims 1-10.