Sensing method and apparatus

By determining whether a sensing request meets the reuse conditions, sensing tasks can be reused or updated appropriately, thus solving the efficiency and latency problems of sensing request processing in communication systems and achieving efficient processing of sensing tasks.

WO2026092268A1PCT designated stage Publication Date: 2026-05-07HUAWEI TECH CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

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

AI Technical Summary

Technical Problem

How to effectively handle sensing requests, especially how to reasonably reuse the sensing results of existing sensing tasks in communication systems to reduce redundant measurement overhead and latency.

Method used

The system determines whether a sensing request meets the conditions for reusing an existing sensing task. If it does, the existing sensing result is reused; otherwise, further processing is performed, including creating a new sensing task or updating an existing task, based on resource consumption and QoS requirements.

Benefits of technology

It enables flexible handling of sensing requests in communication systems, reduces redundant measurement overhead and latency, and improves the efficiency and adaptability of sensing tasks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2025129333_07052026_PF_FP_ABST
    Figure CN2025129333_07052026_PF_FP_ABST
Patent Text Reader

Abstract

A sensing method and apparatus, which relate to the technical field of communications. The method comprises: when a first sensing request meets a first condition, sending first information to an AF, wherein the first information is used for indicating a second sensing result; and when the first sensing request does not meet the first condition, processing the first sensing request, wherein the first condition is a condition for reusing the second sensing result, and the second sensing result is a sensing result of a second sensing task. When an existing sensing task is being executed, an SCF can flexibly perform different processing for different sensing requests, for example, if a sensing request #1 can meet the first condition, a sensing result of the existing sensing task can be reused, thereby avoiding the overhead and latency of performing sensing measurement again, and for another example, if a sensing request #2 does not meet the first condition, the sensing request #2 may be further processed.
Need to check novelty before this filing date? Find Prior Art

Description

Sensing methods and devices

[0001] This application claims priority to Chinese patent application filed on October 31, 2024, with application number 202411554155.X and entitled "Sensing Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and more specifically, to a sensing method and apparatus. Background Technology

[0003] With the development and advancement of communication technology, in future cellular networks, communication devices (e.g., base stations) will not only be able to achieve the Internet of Things, but also possess sensing capabilities. Enabling technologies that enable the coexistence, mutual assistance, or mutual benefit of communication and sensing functions can be termed integrated sensing and communication (ISAC). As research on ISAC deepens in academia and industry, using radio frequency signals from communication systems for sensing is becoming an increasingly popular research direction.

[0004] For example, application function network elements can send sensing requests to request sensing services. However, how to effectively process sensing requests is an urgent problem to be solved. Summary of the Invention

[0005] This application provides a sensing method and apparatus. By determining whether a new sensing request meets certain conditions, it determines whether to reuse the sensing results of an existing sensing task, thereby effectively processing the sensing request.

[0006] Firstly, a sensing method is provided. The method provided in the first aspect is applied to a first sensing network element. Unless otherwise specified, the first sensing network element in this application can be a core network device, a component within the core network device (e.g., a processor, apparatus, circuit, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the core network device. For ease of description, the following description uses a first sensing network element as an example.

[0007] For example, the first sensing network element can be responsible for sensing control. For instance, the first sensing network element can serve as a control plane network element for sensing. The first sensing network element can be called a sensing control function (SCF). In future communication systems, the first sensing network element may have other names, which are not limited in this application.

[0008] The method includes: receiving a first sensing request from an application function network element, the first sensing request being used to request a first sensing result; if the first sensing request satisfies a first condition, sending first information to the application function network element, the first information being used to indicate a second sensing result; or, if the first sensing request does not satisfy the first condition, processing the first sensing request; wherein the first condition is a condition for reusing the second sensing result, and the second sensing result is a sensing result of a second sensing task.

[0009] Specifically, the first sensing network element receives the first sensing request from the application function network element. This can be done directly from the application function network element or indirectly through other network elements. For example, the first sensing network element can receive the first sensing request from the application function network element through the network exposure function (NEF); that is, the NEF can receive the first sensing request from the application function network element and can also send the first sensing request to the first sensing network element.

[0010] Based on the above scheme, SCF can flexibly handle different sensing requests in different ways when an existing sensing task is being executed. For example, if sensing request #1 meets the first condition, the sensing results of the existing sensing task can be reused, thereby avoiding the overhead and latency of sensing and measuring again. Conversely, if sensing request #2 does not meet the first condition, it can be further processed.

[0011] In some implementations, the first information includes the second sensing result; or, the first information includes first indication information, which is used to indicate the reuse of the second sensing result.

[0012] Based on the above scheme, the first information can directly indicate the second sensing result, thereby realizing the transmission of the second sensing result. The first information can also indicate the reuse of the second sensing result. AF can determine the second sensing result from the pre-obtained sensing results, thereby reducing the transmission overhead of the second sensing result.

[0013] In some implementations, the first sensing request is used to indicate at least one of a first service type, a first quality of service (QoS) requirement, or a first sensing area; wherein the first condition includes at least one of the following: the first service type is the same as the second service type, the second service type is the service type of the second sensing task; the second sensing task satisfies the first QoS requirement; or, the first sensing area belongs to the second sensing area, the second sensing area is the sensing area of ​​the second sensing task.

[0014] Based on the above scheme, the first condition can reasonably determine whether the second perception result can be reused.

[0015] In some implementations, if the first perception request does not meet the first condition, the first perception request is processed, including: if the first business type is different from the second business type, the first perception request is processed according to the relationship between the resource consumption corresponding to the first business type and the resource consumption corresponding to the second business type.

[0016] Based on the above scheme, SCF can further process the first sensing request based on the resource consumption relationship when the business type is different, thereby effectively handling the first sensing request. For example, if the resource consumption corresponding to the business type of the first sensing request is greater, SCF can create a new sensing task or update the existing sensing task. Conversely, if the resource consumption corresponding to the business type of the first sensing request is smaller, SCF can reuse the existing sensing task.

[0017] In some implementations, processing the first sensing request based on the relationship between the resource consumption corresponding to the first service type and the resource consumption corresponding to the second service type includes: if the resource consumption corresponding to the first service type is greater than or equal to the resource consumption corresponding to the second service type, sending second information to the second sensing network element according to the first sensing request; or, if the resource consumption corresponding to the first service type is less than or equal to the resource consumption corresponding to the second service type, sending second information to the second sensing network element according to the first sensing request; or, sending indication information of the first sensing result to the application function network element according to the first sensing request, wherein the first sensing result is determined based on the second sensing result; wherein the second information is used to establish a first sensing task, and the service type of the first sensing task is the first service type.

[0018] Based on the above scheme, SCF can establish a perception task for the first perception request based on the relationship between resource consumption, or determine the perception result corresponding to the first perception request based on the previous perception results, thereby effectively processing the first perception request.

[0019] In some implementations, when the first sensing request does not meet the first condition, processing the first sensing request includes: when the second sensing task does not meet the first QoS requirement, sending second information to the second sensing network element according to the first sensing request, the second information being used to establish the first sensing task, wherein the first sensing task meets the first QoS requirement.

[0020] Based on the above scheme, if the existing sensing task does not meet the QoS requirements indicated by the new sensing request, SCF can establish a sensing task that meets the first QoS requirement, thereby realizing sensing.

[0021] In some implementations, if the first sensing request does not meet the first condition, processing the first sensing request includes: if part or all of the area in the first sensing region does not belong to the second sensing region, sending second information to the second sensing network element according to the first sensing request, the second information being used to establish a first sensing task, the sensing area of ​​the first sensing task including the first sensing region.

[0022] Based on the above scheme, when the sensing area indicated by the new sensing request exceeds the sensing area of ​​the existing sensing task, the SCF can establish a first sensing task, thereby enabling sensing in the new sensing area.

[0023] In some implementations, the method further includes: sending third information to a first access network element, the third information indicating first sensing parameters, wherein the first access network element is used to perform the first sensing task according to the first sensing parameters; and / or sending fourth information to a second access network element, the fourth information indicating second sensing parameters, wherein the second access network element is used to perform the first sensing task within a third sensing area according to the second sensing parameters, wherein the third sensing area belongs to the first sensing area and does not belong to the second sensing area.

[0024] In some implementations, the second information includes at least one of the following: identification information of the first sensing task; identification information of the second access network element; location information of the second access network element; or, information of the third sensing area.

[0025] In some implementations, the first information includes a first identifier associated with the first perception request.

[0026] Based on the above scheme, the application function network element can determine, according to the first identifier, that the second sensing request indicated by the first information is a response to the first sensing request.

[0027] Secondly, a sensing method is provided. The method provided in this second aspect is applied to the network exposure function (NEF). Unless otherwise specified, the NEF in this application can be a core network device, a component within the core network device (e.g., a processor, device, circuit, chip, or chip system), or a logic module or software capable of implementing all or part of the core network device's functions. In future communication systems, the NEF may have other names, which are not limited in this application. For ease of description, the following description uses NEF as an example.

[0028] The method includes: receiving a first sensing request from an application function network element, the first sensing request being used to request a first sensing result; if the first sensing request satisfies a first condition, sending first information to the application function network element, the first information being used to indicate a second sensing result; or, if the first sensing request does not satisfy the first condition, sending the first sensing request to a first sensing network element; wherein the first condition is a condition for reusing the second sensing result, the second sensing result being a sensing result of a second sensing task, and the first sensing network element being used to process the first sensing request.

[0029] Based on the above scheme, NEF can flexibly handle different sensing requests in different ways when existing sensing tasks are being executed. For example, if sensing request #1 meets the first condition, the sensing results of the existing sensing task can be reused, thereby avoiding the overhead and latency of sensing and measuring again. As another example, if sensing request #2 does not meet the first condition, it can be sent to the first sensing network element (e.g., SCF) for further processing.

[0030] In some implementations, the first sensing request is used to indicate at least one of a first service type, a first QoS requirement, or a first sensing area; wherein the first condition includes at least one of the following: the first service type is the same as the second service type, the second service type is the service type of the second sensing task; the second sensing task satisfies the first QoS requirement; or, the first sensing area belongs to the second sensing area, the second sensing area is the sensing area of ​​the second sensing task.

[0031] Thirdly, a communication device is provided, including processing circuitry (or a processor) and an input / output interface (also referred to as an interface circuit), the input / output interface being used for inputting and / or outputting signals, the processing circuitry being used to perform the first aspect and any possible method of the first aspect, or the processing circuitry being used to perform the second aspect and any possible method of the second aspect.

[0032] In some implementations, the processing circuitry is used to communicate with other devices via an interface circuitry and to perform the first aspect and any possible method of the first aspect, or to perform the second aspect and any possible method of the second aspect.

[0033] Fourthly, a communication device is provided. This communication device may include units or modules for performing the functions of the communication device.

[0034] In some implementations, the communication device may include modules, units, or means for performing the methods / operations / steps / actions described in the first aspect and any possible implementation of the first aspect. These modules, units, or means may be hardware circuits, software, or a combination of hardware circuits and software.

[0035] For example, the device includes a transceiver unit and a processing unit. The transceiver unit is configured to receive a first sensing request from an application function network element, the first sensing request requesting a first sensing result; if the first sensing request meets a first condition, the transceiver unit is further configured to send first information to the application function network element, the first information indicating a second sensing result; or, if the first sensing request does not meet the first condition, the processing unit is configured to process the first sensing request; wherein the first condition is a condition for reusing the second sensing result, and the second sensing result is the sensing result of a second sensing task.

[0036] In some implementations, the first information includes the second sensing result; or, the first information includes first indication information, which is used to indicate the reuse of the second sensing result.

[0037] In some implementations, the first sensing request is used to indicate at least one of a first service type, a first QoS requirement, or a first sensing area; wherein the first condition includes at least one of the following: the first service type is the same as the second service type, the second service type is the service type of the second sensing task; the second sensing task satisfies the first QoS requirement; or, the first sensing area belongs to the second sensing area, the second sensing area is the sensing area of ​​the second sensing task.

[0038] In some implementations, when the first business type is different from the second business type, the processing unit is specifically used to process the first perception request based on the relationship between the resource consumption corresponding to the first business type and the resource consumption corresponding to the second business type.

[0039] In some implementations, when the resource consumption corresponding to the first service type is greater than or equal to the resource consumption corresponding to the second service type, the transceiver unit is further configured to send second information to the second sensing network element according to the first sensing request; or, when the resource consumption corresponding to the first service type is less than or equal to the resource consumption corresponding to the second service type, the transceiver unit is further configured to send second information to the second sensing network element according to the first sensing request; or, the transceiver unit is further configured to send indication information of the first sensing result to the application function network element according to the first sensing request, wherein the first sensing result is determined based on the second sensing result; wherein the second information is used to establish a first sensing task, and the service type of the first sensing task is the first service type.

[0040] In some implementations, if the second sensing task does not meet the first QoS requirement, the transceiver unit is further configured to send second information to the second sensing network element according to the first sensing request. The second information is used to establish the first sensing task, wherein the first sensing task meets the first QoS requirement.

[0041] In some implementations, if some or all of the areas in the first sensing area do not belong to the second sensing area, the transceiver unit is further configured to send second information to the second sensing network element according to the first sensing request. The second information is used to establish a first sensing task, and the sensing area of ​​the first sensing task includes the first sensing area.

[0042] In some implementations, the transceiver unit is further configured to send third information to a first access network element, the third information being used to indicate first sensing parameters, wherein the first access network element is used to perform the first sensing task according to the first sensing parameters; and / or, the transceiver unit is further configured to send fourth information to a second access network element, the fourth information being used to indicate second sensing parameters, wherein the second access network element is used to perform the first sensing task within a third sensing area according to the second sensing parameters, wherein the third sensing area belongs to the first sensing area and does not belong to the second sensing area.

[0043] In some implementations, the second information includes at least one of the following: identification information of the first sensing task; identification information of the second access network element; location information of the second access network element; or, information of the third sensing area.

[0044] In some implementations, the first information includes a first identifier associated with the first perception request.

[0045] In some implementations, the communication device may include modules, units, or means for performing the methods / operations / steps / actions described in the second aspect and any possible implementation of the second aspect. These modules, units, or means may be hardware circuits, software, or a combination of hardware circuits and software.

[0046] For example, the device includes a processing unit and a transceiver unit. The transceiver unit is configured to: receive a first sensing request from an application function network element, the first sensing request requesting a first sensing result; if the first sensing request meets a first condition, the transceiver unit is further configured to send first information to the application function network element, the first information indicating a second sensing result; or, if the first sensing request does not meet the first condition, the transceiver unit is further configured to send the first sensing request to a first sensing network element; wherein the first condition is a condition for reusing the second sensing result, the second sensing result is the sensing result of a second sensing task, and the first sensing network element processes the first sensing request.

[0047] In some implementations, the first sensing request is used to indicate at least one of a first service type, a first QoS requirement, or a first sensing area; wherein the first condition includes at least one of the following: the first service type is the same as the second service type, the second service type is the service type of the second sensing task; the second sensing task satisfies the first QoS requirement; or, the first sensing area belongs to the second sensing area, the second sensing area is the sensing area of ​​the second sensing task.

[0048] Fifthly, a computer-readable storage medium is provided that stores a computer program or instructions that, when executed, cause the first aspect and any possible method of the first aspect to be performed (or implemented), or cause the second aspect and any possible method of the second aspect to be performed (or implemented).

[0049] In a sixth aspect, a computer program product is provided, comprising a computer program or instructions that, when executed, cause the first aspect and any possible method of the first aspect to be performed (or implemented), or cause the second aspect and any possible method of the second aspect to be performed (or implemented).

[0050] A seventh aspect provides a communication device, including a processor for executing (or implementing) any of the possible methods of the first aspect above, or for executing (or implementing) any of the possible methods of the second aspect above, by executing a computer program (or computer-executable instructions) stored in a memory, and / or by logic circuitry.

[0051] In one possible implementation, the device also includes a memory. In another possible implementation, the processor and memory are integrated together. In yet another possible implementation, the memory is located outside the communication device. The processor can be one or more.

[0052] In one possible implementation, the communication device further includes a communication interface for communicating with other devices, such as transmitting or receiving data and / or signals. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.

[0053] In one implementation, the communication device of the third, fourth, or seventh aspect mentioned above can be a chip or a chip system.

[0054] Eighthly, a chip is provided, including a processor for calling a computer program or computer instructions in memory to cause any of the implementations of the first aspect to be executed (or implemented), or to cause any of the implementations of the second aspect to be executed (or implemented).

[0055] In some implementations, the processor is coupled to the memory via an interface.

[0056] Ninth aspect, a communication system is provided, including a first sensing network element and a NEF, wherein the first sensing network element is used to perform the first aspect and any possible implementation thereof, and the NEF is used to perform the second aspect and any possible implementation thereof.

[0057] In a tenth aspect, a sensing method is provided, comprising: a first sensing network element performing the first aspect and any possible implementation thereof, and a NEF performing the second aspect and any possible implementation thereof.

[0058] For example, the NEF receives a first sensing request from an application function network element, which requests a first sensing result. If the first sensing request meets a first condition, the NEF sends first information to the application function network element, which indicates a second sensing result. Alternatively, if the first sensing request does not meet the first condition, the NEF sends the first sensing request to a first sensing network element. The first condition is a condition for reusing the second sensing result, which is the sensing result of a second sensing task. The first sensing network element processes the first sensing request. Correspondingly, the first sensing network element receives the first sensing request from the NEF and processes it.

[0059] The description of the beneficial effects of any one of the second to tenth aspects can be made with reference to the description of the beneficial effects of the first aspect. The aforementioned communication device may also be called a sensing device or other names, and this application is not limited thereto. The aforementioned communication system may also be called a sensing system or other names, and this application is not limited thereto. Attached Figure Description

[0060] Figure 1 is a schematic diagram of a communication system.

[0061] Figure 2 is a schematic diagram of another communication system.

[0062] Figure 3 is a schematic flowchart of a sensing method provided in an embodiment of this application.

[0063] Figure 4 is a schematic flowchart of processing the first perception request provided in an embodiment of this application.

[0064] Figure 5 is a schematic flowchart of another sensing method provided in an embodiment of this application.

[0065] Figure 6 is a schematic block diagram of a communication device provided in an embodiment of this application.

[0066] Figure 7 is a schematic diagram of another communication device provided in an embodiment of this application.

[0067] Figure 8 is a schematic diagram of a chip system provided in an embodiment of this application.

[0068] Figure 9 is a schematic diagram of another chip system provided in an embodiment of this application. Detailed Implementation

[0069] In this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0070] I. In this application, "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 and B can be singular or plural. In the textual description of this application, the character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "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 c can mean: a, or, b, or, c, or, a and b, or, a and c, or, b and c, or, a, b, and c. Here, a, b, and c can each be single or multiple.

[0071] II. In this application, the terms "first," "second," and various numerical designations (e.g., #1, #2, etc.) indicate distinctions made for ease of description and are not intended to limit the scope of the embodiments of this application. For example, they may distinguish different messages, rather than describing a specific order or sequence. It should be understood that such descriptions can be interchanged where appropriate to describe solutions other than those in the embodiments of this application.

[0072] Third, in this application, descriptions such as "when," "under the circumstances," and "if" all refer to the device making corresponding processing under certain objective circumstances, and are not time-limited, nor do they require the device to make a judgment action when implementing it, nor do they imply any other limitations.

[0073] IV. In this application, "instruction" or "for instruction" can include both direct (or explicit) and indirect (or implicit) instruction. When describing instruction information as indicating A, it can include whether the instruction information directly or indirectly indicates A, but does not necessarily mean that the instruction information carries A. For example, in the case of indirect (or implicit) instruction, the receiving end of the instruction information can obtain A based on the parameters indicated by the instruction information, combined with other rules or parameters, or through deduction.

[0074] V. The indication methods involved in the embodiments of this application should be understood to cover various methods that enable the party to be indicated to obtain the information to be indicated. The information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately. Moreover, the sending period and / or sending time of these sub-information can be the same or different. This application does not limit the sending method, for example.

[0075] VI. In this application, "protocol" can refer to standard protocols in the field of communications, such as 5G protocols, new radio (NR) protocols, and related protocols applied to future communication systems; this application does not limit this term. "Predefined" can include predefined terms, such as protocol definitions. "Preconfiguration" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device; this application does not limit the implementation method.

[0076] VII. In this application, "communication" can also be described as "data transmission," "information transmission," "data processing," etc. "Transmission" includes "sending" and / or "receiving." For example, transmission can be uplink transmission, such as a terminal device sending a signal to a network device; transmission can also be downlink transmission, such as a network device sending a signal to a terminal device; transmission can also be sidelink transmission, such as a terminal device sending a signal to another terminal device. For example, "transmission" can be air interface level transmission, or it can be signal transmission from a chip input (I) / output (O) port, rather than air interface level transmission.

[0077] 8. In this application, terms such as “message”, “information”, “signal” or “information element (IE)” can be used interchangeably. There are no restrictions on the name of the message or information, as long as it can achieve the corresponding function.

[0078] 9. "Sending information to XX (device)" can be understood as the destination of the information being that device. This can include sending information directly or indirectly to that device. "Receiving information from XX (device), or receiving information from XX (device)" can be understood as the source of the information being that device. This can include receiving information directly or indirectly from that device. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be understood in a similar way, and will not be repeated here. Furthermore, "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" or "receiving" can occur between devices, for example, between network devices and terminal devices via an air interface. "Sending" or "receiving" can also occur within a device, for example, between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface.

[0079] 10. In this application, terms such as "exemplarily" and "for example" are used to indicate examples, illustrations, or descriptions to present concepts in a specific manner. Any embodiment or design described as an "example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. In the embodiments of this application, the terms "of," "corresponding (relevant)," "corresponding," and "associated" may sometimes be used interchangeably, and it should be noted that their intended meanings are consistent unless their distinctions are emphasized.

[0080] XI. In this application, configuration can be signaling configuration or can be described as configuring signaling. For example, signaling configuration includes configuration using signaling sent by network devices, which can be radio resource control (RRC) messages, downlink control information (DCI) messages, or system information blocks (SIBs). Another example is signaling configuration between network devices. These network devices can include access network devices, core network devices, or management plane devices, etc. Optionally, signaling configuration can also be configured to terminal devices or network devices using pre-configured signaling, or configured to terminal devices or network devices through pre-configuration. Here, pre-configuration means defining or configuring the values ​​of corresponding parameters in advance using a protocol, and storing them in the terminal device or network device during communication. Pre-configured messages can be modified or updated when the terminal device or network device is connected to the network.

[0081] 12. This application will present various aspects, embodiments, or features relating to systems that may include multiple devices, components, modules, etc. Each system may include devices, components, modules, etc., other than those illustrated, and / or may not include all and all of the devices, components, modules, etc. discussed in conjunction with the accompanying drawings.

[0082] Thirteen, the business 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 emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0083] XIV. In the various embodiments of this application, the sequence number of each process 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. The terms "comprising," "including," "having," and their variations all mean "including but not limited to," unless otherwise specifically emphasized.

[0084] The technical solutions of this application embodiment can be applied to various communication systems, including but not limited to: Long Term Evolution (LTE) systems, NR systems, and other fifth-generation (5G) communication systems. thThis includes various mobile communication systems such as 5G, narrowband Internet of Things (NB-IoT), enhanced machine-type communication (eMTC), enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), satellite communication systems, LTE-machine-to-machine (LTE-M) systems, and other systems that evolve after 5G, such as future mobile communication systems.

[0085] Figure 1 is a schematic diagram of a communication system 100. As shown in Figure 1, the communication system 100 includes a wireless access network 110 and a core network 120. Optionally, the communication system 100 may also include an Internet 130. The wireless access network 110 may include at least one access network device (111a and 111b in Figure 1) and at least one terminal device (112a-112j in Figure 1). The terminal device is connected to the access network device wirelessly. The access network device is connected to the core network 120 wirelessly or via a wired connection. The core network 120 may include one or more core network devices. The core network device and the access network device may be independent physical devices, or the functions of the core network device and the logical functions of the access network device may be integrated on the same physical device, or a single physical device may integrate some of the functions of the core network device and some of the functions of the access network device. Terminal devices and access network devices may be interconnected via wired or wireless connections. Wireless communication can occur between terminal devices, between access network devices, and between terminal devices and access network devices via air interface resources. For example, air interface resources may include at least one of time-domain resources, frequency-domain resources, code resources, and spatial resources. It should be noted that Figure 1 is a schematic diagram; the communication system 100 may also include other access network devices, such as wireless relay devices and wireless backhaul devices, which are not shown in Figure 1.

[0086] Access network equipment can be any device with wireless transceiver and / or sensing capabilities. For example, access network equipment can be a base station used to connect terminal devices to a radio access network (RAN). Access network equipment is sometimes also referred to as an access network element, access network node, RAN node, or RAN. It is understood that the names of devices with access network functionality may differ in systems employing different wireless access technologies. For ease of description, devices providing wireless communication access functionality to terminal devices can be collectively referred to as base stations or RANs. Exemplarily, access network equipment includes, but is not limited to: various forms of macro base stations (as shown in Figure 1, 111a), micro base stations or indoor stations (as shown in Figure 1, 111b), pico base stations, small cells, balloon stations, relay stations, access points, etc. Access network equipment can include evolved node Bs (eNBs or eNodeBs) in LTE, access points (APs), wireless relay nodes, wireless backhaul nodes, transmission points (TRPs or TPs), or transmission reception points (TRPs) in Wi-Fi systems. It can also include next-generation NodeBs (gNBs) or transmission points (TRPs or TPs) in 5G systems, one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, and network nodes constituting a gNB or transmission point, such as baseband units (BBUs) or distributed units (DUs). Furthermore, it can include access network equipment, servers, or vehicle-mounted equipment in networks evolving after 5G. Access network equipment can also be modules or units that perform some of the functions of a base station; for example, it can be a central unit (CU) or a DU.

[0087] In this embodiment, the apparatus for implementing the functions of the access network device can be the access network device itself, or it can be an apparatus capable of supporting the access network device in implementing the functions, such as a chip system, which can be installed in the access network device. The chip system can be composed of chips, or it can include chips and other discrete components.

[0088] In another possible scenario, multiple access network devices collaborate to assist the terminal in achieving wireless access, with each device performing a portion of the base station's functions. For example, the access network devices could be a CU, DU, CU (control plane, CP), CU (user plane, UP), or a radio unit (RU). The CU and DU can be separate entities or included in the same network element, such as a BBU. The RU can be included in radio equipment or radio units, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0089] 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 open radio access network (O-RAN) 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. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules. The embodiments of this application do not limit the specific technology or specific device form used in the access network equipment.

[0090] In some examples, the access network device can also be responsible for air interface resource management and some mobility management. In some examples, the access network device can also have sensing capabilities. For example, the access network device can act as a sensing measurement node, performing sensing tasks (or sensing sessions). The following description may use a base station as an example of the access network device.

[0091] Terminal equipment can be a device that provides voice and / or data connectivity to users; it can also be a device with wireless connectivity and / or sensing capabilities. Terminal equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on water (such as on ships); and it can also be deployed in the air (e.g., on airplanes, balloons, and satellites). Terminal equipment can also be referred to as user equipment (UE), access terminal, terminal, subscriber unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, wireless network equipment, user agent, or user device. In this application embodiment, terminal devices include, but are not limited to: cellular phones, mobile phones, wireless data cards, wireless modems, tablets, laptop computers, notebook computers, handheld computers, mobile internet devices (MIDs), computers with wireless transceiver capabilities, cordless phones, session initiation protocol (SIP) phones, smartphones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handsets with wireless communication capabilities, computing devices or other devices connected to wireless modems, in-vehicle devices (e.g., cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), wearable devices (e.g., smartwatches, smart bracelets, pedometers, smart glasses, etc.), satellite terminals, terminal devices in the Internet of Things or the Internet of Vehicles, as well as any form of terminal in future networks, relay user equipment, or terminals in future evolved public land mobile networks (PLMNs), etc.Terminal devices can also be virtual reality (VR) devices, augmented reality (AR) devices, smart point-of-sale (POS) machines, customer-premises equipment (CPE), light UE, reduced capability UE (REDCAP UE), machine-type communication (MTC) terminals, terminal devices in industrial control, terminal devices in self-driving, terminal devices in telemedicine, terminal devices in smart grids, wireless terminals in transportation safety, terminal devices in smart cities, terminal devices in smart homes, tactile terminal devices, smart home devices (e.g., refrigerators, televisions, air conditioners, electricity meters, etc.), smart robots, robotic arms, workshop equipment, wireless terminals in self-driving, or flying devices (e.g., smart robots, hot air balloons, drones, airplanes), etc. The terminal device can also be a vehicle device, such as a complete vehicle device, an in-vehicle module, an in-vehicle chip, an on-board unit (OBU), or a telematics box (T-BOX). The terminal device can also be other devices with terminal functions; for example, it can be a device that functions as a terminal in device-to-device (D2D) communication. This application does not limit the scope of the embodiments in this regard.

[0092] In this application embodiment, the device for implementing the functions of the terminal device can be the terminal device itself, or it can be any device capable of supporting the terminal device in implementing the functions, such as a chip or chip system. This device can be installed in the terminal device. The chip system can consist of chips or include chips and other discrete components. In the technical solution of this application embodiment, the device for implementing the functions of the terminal device is referred to as the terminal device, which can also be called a terminal. The following description may use a UE (User Equipment) as an example to illustrate the technical solution provided in this application embodiment.

[0093] The roles of base stations and terminals can be relative. For example, the helicopter or drone 112i in Figure 1 can be configured as a mobile base station. For terminals 112j that access the wireless access network 110 via 112i, terminal 112i is a base station; however, for base station 111a, 112i is a terminal, meaning that 111a and 112i communicate via a wireless air interface protocol. Of course, 111a and 112i can also communicate via a base station-to-base station interface protocol. In this case, relative to 111a, 112i is also a base station. Therefore, both base stations and terminals can be collectively referred to as communication devices. 111a and 111b in Figure 1 can be called communication devices with base station functions, and 112a-112j in Figure 1 can be called communication devices with terminal functions.

[0094] Access network devices and terminal devices can communicate via wireless links. The transmission link from the access network device to the terminal device can be called a downlink (DL) or downlink channel, used for transmitting downlink signals. The transmission link from the terminal device to the access network device can be called an uplink (UL) or uplink channel, used for transmitting uplink signals. The transmission link from one terminal device to another can be called a sidelink (SL) or sidelink channel, used for transmitting sidelink signals.

[0095] In mobile communication systems, with base stations employing higher frequency bands, such as millimeter waves or even terahertz, the idea of ​​achieving radar-like functions through mobile communication systems becomes possible. Similar to radar detecting targets, mobile communication systems can utilize the principles of radio wave (or wireless signal) transmission, reflection, or scattering to sense the physical world. By obtaining information such as distance, speed, or angle from wireless signals, sensing measurement information can be obtained, thereby enabling the perception and identification of specific areas, objects, or events.

[0096] Perception can be used for object localization, detection, and tracking; animal motion recognition; or target imaging. As an example, based on the application purpose and specific deployment environment, the perception capabilities of a base station can be planned, and then the base station can be deployed. Exemplarily, perception capabilities can be represented by at least one of the following:

[0097] Range resolution can be used to represent the ability to distinguish nearby targets by distance. For example, range resolution can be measured using the smallest resolvable distance interval.

[0098] Velocity resolution represents the ability to distinguish targets based on radial velocity. For example, if the difference between the radial velocities of two objects is less than or equal to the velocity resolution, they cannot be distinguished as two separate objects.

[0099] Angular accuracy can represent the ability to distinguish nearby targets at an angle. For example, range resolution can be measured using the smallest resolvable angle.

[0100] The field of view (FOV) can represent the maximum range that a base station (or other sensing node) can perceive (e.g., including horizontal and / or vertical views). For example, the FAV can be expressed in degrees.

[0101] When base stations have sensing capabilities, mobile communication systems can provide sensing application services (or sensing services). For example, the above solutions can be applied to scenarios such as smart transportation, smart low-altitude airspace, or smart parks.

[0102] For example, the types of perception services may include: target speed measurement, perception area monitoring (e.g., providing the trajectory of a target in the perception area, target recognition, or target counting, etc.), target imaging (e.g., depicting the outline of a target, or identifying the type of target), etc.

[0103] In the embodiments of this application, the terms "target", "object", "object", "perceived target", "perceived object" and "perceived object" can be interchanged without limitation.

[0104] Figure 2 is a schematic diagram of another communication system. Figure 2 shows multiple nodes that can communicate with each other. The solid line connecting two nodes in Figure 2 indicates that communication is possible between those two nodes. Figure 2 is only an example; the communication system in this embodiment may include more nodes, and there may be other communication paths between the nodes. This application does not impose any limitations.

[0105] The communication system shown in Figure 2 may include a base station (represented by RAN in Figure 2) and at least one network function (NF). For example, at least one NF may include at least one of the following: network exposure function (NEF), application function (AF), access and mobility management function (AMF), or sensing function (SF).

[0106] The Network Front-End (NEF) can expose certain network functionalities to applications in a controlled manner. For example, the NEF can reside between the core network and external third-party application functionalities (and possibly partially within the Application Front-End), managing external applications that expose network data. For instance, other devices accessing internal 5G core network data can do so through the NEF. The NEF can provide appropriate security safeguards to ensure external applications can access the 3G Partner Program (3GPP). rd This application provides security features for 3GPP (Generation Partnership Project) networks, including enabling QoS customization for external applications, mobility state event subscription, and AF request distribution. In future communication systems, the network open function may remain NEF (Network Open Function) or have other names; this application is not limited to these.

[0107] Application Function (AF) can refer to various services at the application layer. AF can be used to convey application-side requests to the network side. For example, requests may include QoS requirements or user state event subscriptions. AF can provide various application service data to the control plane network elements of the operator's communication network, or obtain network data and control information from the control plane network elements of the communication network. In 5G communication systems, application function network elements can be application functions (AFs). In future communication systems, application function network elements may still be AF network elements, or they may have other names; this application is not limited. For example, application function network elements can also be called application servers or service servers. Furthermore, application function network elements can be deployed on the operator's network (e.g., AF can be an application within the operator's network) or deployed by a third party. For example, AF can be a Voice over Long-Term Evolution (Volte) AF, or it can be a third-party AF (such as a video server or game server).

[0108] Access and Mobility Management (AMF) can implement terminal attachment, tracking area update procedures, or other functions in mobile networks. For example, AMF can provide non-access stratum (NAS) messages, complete registration management, connection management, reachability management, allocate tracking area lists (TA lists), grant access authorization, authenticate, and manage mobility. AMF can transparently route session management (SM) messages to session management network elements. AMF can provide a session management message transmission channel for the UE and the session management function (SMF), providing authentication and authorization functions for user access, and serving as the core network control plane access point for the terminal and radio. In 5G communication systems, the access and mobility management network element can be AMF. In future communication systems, the access and mobility management function can still be AMF, or it can have other names; this application is not limited to these.

[0109] SF can be a network element responsible for sensing. For example, SF can be responsible for receiving sensing requests from AF and / or NEF, configuring RAN to perform sensing measurements, processing measurement data reported by RAN, or generating sensing results, etc.

[0110] As an example of a separation between the control plane and the data plane (or user plane), the SF can include a first sensing network element and a second sensing network element. Exemplarily, the first sensing network element can be called a sensing control function (SCF) or other names; the second sensing network element can be called a sensing processing function (SPF) or other names.

[0111] The following description uses SCF as the first sensing element and SPF as the second sensing element as an example.

[0112] For example, the SCF can act as a control plane to receive sensing requests from the AF and / or NEF, configure the RAN to perform sensing measurements, or receive sensing processing results from the SPF, etc. In future communication systems, the first sensing network element responsible for sensing control can be called an SCF, or a sensing management function, sensing management control function, SF-control plane (CP), or other names, which are not limited in this application.

[0113] For example, the SPF can be responsible for processing sensing measurement data, reporting sensing measurement results to the SCF, AF, or NEF, or determining the sensing results, etc. In future communication systems, the second sensing network element responsible for sensing processing can be called SPF, or it can be called sensing data plane function, sensing data processing function, SF-user plane (UP), or other names, which are not limited in this application.

[0114] One SCF can correspond to one or more SPFs. For example, one SCF can control one or more SPFs to implement data plane (or user plane) functions such as perception processing.

[0115] As another example, the control plane and data plane can be combined, so that the SF can have the functions of both the SCF and SPF, that is, the SF can have the functions of both the control plane and the data plane.

[0116] The communication system in this application embodiment may include some or all of the nodes shown in Figure 1 and / or Figure 2, and may also include other nodes. For example, the communication system in this application embodiment may include a user plane function (UPF), a session management function (SMF), a network slice selection function (NSSF), an authentication server function (AUSF), a network function repository function (NRF), a policy control function (PCF), a unified data management (UDM), or other nodes.

[0117] The aforementioned network elements or functions can be network components in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (e.g., a cloud platform). These network elements or functions can be implemented by a single device, by multiple devices working together, or as a functional module within a single device; this application does not specifically limit their implementation in this regard.

[0118] The naming conventions described above are defined solely for the purpose of distinguishing different functions and do not constitute a limitation on this application. This application does not preclude the possibility of using other naming conventions in 5G networks and other future networks. For example, in future communication networks, some or all of the aforementioned network terminology may be retained from 5G, or other names may be used.

[0119] When the base station has sensing capabilities, the mobile communication system can also be regarded as a large sensor, providing sensing services for external applications.

[0120] For ease of description and understanding, in the following examples, the first sensing network element is referred to as SCF, the application function network element as AF, the network open function network element as NEF, the second sensing network element as SPF, and the access network element as RAN. However, those skilled in the art will understand that SCF, AF, NEF, SPF, or RAN are merely names for ease of understanding, and the first sensing network element, application function network element, network open function network element, second sensing network element, and access network element may have other names.

[0121] As an example, the system shown in Figure 1 or Figure 2 can provide sensing services to AFs with sensing service requirements.

[0122] For example, the SF can receive a sensing request from the AF and configure the RAN to perform the corresponding sensing measurement (or sensing detection) operation. It then processes the sensing measurement data (or sensing data, or measurement data) reported by the RAN to generate a sensing service result (or sensing result), which is then returned to the AF. The RAN can continuously perform sensing measurements after sensing is enabled.

[0123] For example, the SCF can configure the RAN to enable sensing. This configuration action can be triggered by the AF, by the AF via the NEF, or by operation and maintenance (O&M). After the RAN enables sensing, it can continuously perform sensing measurements and send sensing measurement data to the SCF and / or SPF. The SCF and / or SPF can generate sensing results based on the sensing measurement data (e.g., this may include target type, location, velocity, trajectory, or other information). The SCF and / or SPF can send the sensing results to the AF (or, in other words, make the sensing results available to the AF). The SCF and / or SPF can send the sensing results directly to the AF or send them to the AF via the NEF. The SCF and / or SPF can report sensing results once (or, in a one-time manner) or periodically.

[0124] The following are examples of two scenarios involved in the embodiments of this application, referred to as Scenario Example 1 and Scenario Example 2, respectively.

[0125] Scenario Example 1: When the AF is a third-party AF (or the AF belongs to a third party, or the AF is located in a non-trust domain), the AF can send a perception request to the NEF, and the NEF can forward the perception request to the SCF.

[0126] Scenario Example 2: When the AF is a local AF (or, in other words, the AF belongs to the operator, or the AF is located in the trust domain), the AF can send a perception request to the SCF. For example, the AF can send a perception request directly to the SCF without going through the NEF.

[0127] In this application embodiment, the perception task can be understood as or replaced as a perception session.

[0128] Figure 3 is a schematic flowchart of a sensing method 300 provided in an embodiment of this application. In method 300, by determining whether a new sensing request meets the conditions, it is determined whether to reuse the sensing results of an existing sensing task, thereby effectively processing the sensing request. Optional operations in method 300 are shown in Figure 3 with dashed lines.

[0129] The following section describes the various operations of method 300 in conjunction with Figure 3. First, we will introduce the various operations of method 300 in scenario example 1.

[0130] S310, NEF receives a first sensing request from AF, wherein the first sensing request is used to request a first sensing result. Correspondingly, AF sends a first sensing request to NEF.

[0131] The first perception request is used to request the first perception result, or it can be understood as the first perception request being used to subscribe to the first perception result, or it can be understood as the first perception request being used to query the first perception result, or it can be understood as the first perception request being used to instruct NEF to provide the first perception result.

[0132] For example, a first perception request may be used to indicate at least one of the following:

[0133] First business type.

[0134] First sensory area.

[0135] First QoS requirement.

[0136] Information from AF.

[0137] The first perception result can be a perception result corresponding to the first perception request. For example, the first perception result can be a result that satisfies the first service type or the first QoS requirement indicated by the first perception request. Another example is that the first perception result is obtained by performing perception within the first perception area indicated by the first perception request. Yet another example is that the reporting target of the first perception result is the AF indicated by the first perception request.

[0138] The first perception request can directly indicate the above information. For example, the first perception request may include at least one of the following: information on the first service type, information on the first perception area, information on the first QoS requirement, or information on AF.

[0139] The first sensing request can indirectly indicate the aforementioned information. For example, the first sensing request may include an identifier #1, and the receiving end of the first sensing request (e.g., NEF, SCF, or other network elements) may pre-store the mapping relationship between the identifier and information such as service type, sensing area, QoS requirements, or AF. In this way, the receiving end of the first sensing request can determine the information of the first service type, the first sensing area, the first QoS requirements, or the AF based on the identifier #1 and the pre-stored mapping relationship.

[0140] Here, "business type" can represent the type of perceived business (or perceived service). For example, business type can represent the content or form of the perceived result. Or, for another example, business type can represent the purpose of the perceived business.

[0141] For example, the business type may include at least one of the following:

[0142] Target velocity measurement. For example, measuring the velocity of a target within the sensing area.

[0143] Sensing area monitoring. For example, providing the trajectory, location, identification, or count of targets within the sensing area.

[0144] Target imaging. For example, outlining a target or identifying the type of target.

[0145] Presence indication. For example, determining whether a target exists within the sensing area.

[0146] In the embodiments of this application, the terms "target", "object", "object", "perceived target", "perceived object" and "perceived object" can be interchanged without limitation.

[0147] The aforementioned business types may also be referred to as awareness request types, awareness business types, session types, task types, service types, or other names, which are not limited in this application.

[0148] The sensing area can represent the area targeted by the sensing service.

[0149] QoS requirements can represent requirements for sensing services. For example, QoS requirements may include requirements for the sensing results themselves and / or requirements for RAN sensing capabilities.

[0150] For example, QoS requirements may include at least one of the following:

[0151] The positional error (or positional accuracy) of the sensing results;

[0152] The accuracy of the perceived results;

[0153] False alarm rate of perceived results;

[0154] The update frequency of the perception results;

[0155] The accuracy (or resolution) of the perceived results; or

[0156] The RAN can identify the maximum and / or minimum speeds.

[0157] The positional error (or positional accuracy) of the sensing result can represent the quality of the sensing result. For example, a positional accuracy of 1 meter (m) means that there is a maximum positional error of 1 meter, and a positional accuracy of 10 centimeters (cm) means that there is a maximum positional error of 10 centimeters. It is understandable that a positional accuracy of 1 meter is lower than a positional accuracy of 10 centimeters. A positional accuracy of 1 centimeter corresponds to a higher quality sensing result.

[0158] The accuracy of the sensing result can represent the probability that the sensing result meets the location error (or location precision). For example, a sensing result accuracy of 90% means that the sensing result has a 90% probability of meeting the location error (or location precision) requirements in the QoS framework.

[0159] The false alarm rate of a perception result can represent the probability that the perception result is incorrect. For example, if the perception result is a presence indication, a false alarm rate of 10% means that there is a 10% probability that the perception result is wrong, that is, no target is actually present.

[0160] The update frequency of the sensing results can be the frequency at which the updated sensing results are sent to the AF.

[0161] Understandably, higher QoS requirements mean that more resources (e.g., including bandwidth and / or computing resources) are needed to meet the sensing service, or that more capable RAN nodes are needed to perform sensing tasks.

[0162] The AF information may include an AF identifier (ID) and / or address information. The address information may indicate the address of the AF. Optionally, the AF information may also include an association ID, which corresponds to the first sensing request. For example, the SCF can send the first sensing result and the association ID to the AF via the NEF. In this way, the AF can determine from the association ID that the first sensing result is for the first sensing request.

[0163] The aforementioned associated ID can also be understood or replaced as the transmission reference ID.

[0164] S320, if the first sensing request meets the first condition, the NEF sends first information to the AF, which indicates the second sensing result. Correspondingly, the AF receives the first information from the NEF.

[0165] In some possible implementations, method 300 also includes: NEF determining that the first sensing request satisfies the first condition.

[0166] The first condition can be a condition for reusing the second perception result. An example of the second perception result will be introduced below.

[0167] The second perceptual result can be the perceptual result of the second perceptual task. For example, the second perceptual result can be the entire perceptual result of the second perceptual task. Or, for another example, the second perceptual result can be a partial perceptual result of the second perceptual task.

[0168] For example, the second sensing task is used to perform sensing on regions #1 and #2. The sensing results determined by the second sensing task include the sensing results obtained from performing sensing on region #1, and also include the sensing results obtained from performing sensing on region #2. The second sensing result can be the sensing result obtained from performing sensing on region #1. That is, a portion of the sensing results determined by the second sensing task may not be considered part of the second sensing result. In other words, the NEF may only indicate a portion of the sensing results of the second sensing task to the AF.

[0169] As an example, a second-sensory task can be used to determine the second-sensory outcome.

[0170] In some possible implementations, the RAN can perform a second sensing task to obtain a second sensing result.

[0171] In some possible implementations, the RAN can perform a second sensing task, obtain sensing measurement data for the second sensing task, and send the sensing measurement data to the SPF. The SPF can determine the second sensing result based on the aforementioned sensing measurement data. Further, the SPF can send the second sensing result to the SCF or NEF. The second sensing result sent by the SPF can carry identification information of the second sensing task, such as the ID of the second sensing task.

[0172] In some possible implementations, the RAN can perform a second sensing task, obtain sensing measurement data for the second sensing task, and send the sensing measurement data of the second sensing task to the SCF. Alternatively, the RAN can send the sensing measurement data of the second sensing task to the SPF, and the SPF will send the received sensing measurement data to the SCF. The SCF can then determine the second sensing result based on the aforementioned sensing measurement data.

[0173] The second sensing task can be an existing sensing task. For example, the second sensing task can be established before S310. Or, for example, the second sensing task can be established before S320. The second sensing task can also be understood as a sensing task currently being executed. For example, the second sensing task can be being executed at any time between the execution of S310 and the execution of S320, or at any time before the execution of S310.

[0174] The perception request corresponding to the second perception task can be denoted as the second perception request. AF' can send the second perception request to NEF or SCF before S310 or S320. The second perception request can be used to request the second perception result.

[0175] For example, a second perception request may be used to instruct at least one of the following:

[0176] Second business type;

[0177] Second sensory area;

[0178] Second QoS requirement; or

[0179] Information about AF'.

[0180] AF and AF' can be the same network element or different network elements. In other words, the first sensing request and the second sensing request can come from the same application function network element or from different application function network elements.

[0181] Optionally, the difference between the sending time of the first sensing request and the sending time of the second sensing request is less than or equal to a first threshold. For example, the first threshold can be a small value, such as 1 millisecond (ms), 5 ms, 1 second (s), 5 s, 10 s, or other values.

[0182] The above scheme can also be understood as follows: the first sensing request and the second sensing request are initiated within the same time period; they can also be understood as the first sensing request and the second sensing request are initiated almost simultaneously; or they can be understood as concurrent sensing requests. In other words, when AF and AF' are the same application function network element, the AF can continuously initiate two different sensing requests. When AF and AF' are different application function network elements, AF and AF' can initiate sensing requests almost simultaneously.

[0183] If AF' belongs to a third party, AF' can send a second perception request to NEF, and NEF can forward the second perception request to SCF.

[0184] If AF' belongs to an operator, AF' can directly send a second sensing request to SCF.

[0185] Other descriptions are similar to those in Scenario Example 1 and Scenario Example 2 above, and will not be repeated here.

[0186] When AF and AF' are different network elements, the attribution of AF' to AF can be the same, for example, both belonging to a third party or the operator. Alternatively, the attribution of AF' to AF can be different; for example, one network element in both AF' and AF may belong to a third party, while the other network element may belong to the operator.

[0187] In some examples, the first information can be direct indicative information. For example, the first information may include the second perceptual result.

[0188] In other examples, the first information may be indirect indication information. For instance, the first information may include first indication information. The first indication information can be used to indicate the reuse of the second sensing result.

[0189] For example, the first sensing request and the second sensing request can originate from the same AF. Before S320 is executed, the AF has already obtained the second sensing result, that is, all or part of the sensing result of the second sensing task. In this way, the NEF can send first information, which may include first indication information, which may instruct the AF to reuse the second sensing result as a response to the first sensing request.

[0190] As an example, the first indication information may include information about the second perception result. This information about the second perception result can be used to indicate the second perception result. For example, the information about the second perception result may be information about the first perception area. Assuming the first perception area is a part of the second perception area, then AF can use the perception results belonging to the first perception area from the perception results of the second perception task as the second perception result.

[0191] Based on the above scheme, the first information can directly indicate the second sensing result, thereby realizing the transmission of the second sensing result. The first information can also indicate the reuse of the second sensing result. AF can determine the second sensing result from the pre-obtained sensing results, thereby reducing the transmission overhead of the second sensing result.

[0192] Optionally, the first information includes a first identifier. This first identifier may be associated with the first sensing request. Thus, the AF can determine, based on the first identifier, that the second sensing request indicated by the first information is a response to the first sensing request.

[0193] For example, the first identifier may be an association ID. The association ID may also be called a transmission reference ID or other names, which are not limited in this application.

[0194] S330, if the first sensing request does not meet the first condition, the NEF sends the first sensing request to the SCF. Correspondingly, the SCF receives the first sensing request from the NEF. The SCF can then process the first sensing request.

[0195] In some possible implementations, method 300 also includes: NEF determining that the first sensing request does not satisfy the first condition.

[0196] In S330, the first sensing request received by SCF can be understood as coming from NEF or AF.

[0197] In some possible implementations, after S330, method 300 also includes: S360, where the SCF processes the first sensing request.

[0198] The above scheme can be understood as follows: if the first sensing request does not meet the first condition, the SCF processes the first sensing request. The condition that the first sensing request does not meet the first condition can be determined by the NEF. This application does not limit whether the SCF determines that the first sensing request does not meet the first condition.

[0199] In some examples, the SCF can process the first perception request received from the NEF without determining whether the first perception request meets the first condition.

[0200] In other examples, after receiving a first perception request from the NEF, the SCF can determine whether the first perception request meets a first condition. If the first perception request does not meet the first condition, the SCF can execute S360.

[0201] Specific examples of the S360 mentioned above will be provided later and will not be repeated here.

[0202] Based on the above scheme, NEF can flexibly handle different sensing requests in different ways when existing sensing tasks are being executed. For example, if sensing request #1 meets the first condition, the sensing results of the existing sensing task can be reused, thereby avoiding the overhead and latency of sensing and measuring again. As another example, if sensing request #2 does not meet the first condition, it can be sent to the first sensing network element (e.g., SCF) for further processing.

[0203] In other examples, S330 above can be replaced by: if the first sensing request does not meet the first condition, the NEF sends information 1 to the AF. This information 1 can be used to indicate that the first sensing request processing failed.

[0204] For example, if the first sensing request does not meet the first condition, it may indicate that the resource consumption of the first sensing request exceeds the capacity of the RAN in the first sensing area, thus failing to meet the QoS requirements indicated by the first sensing request, or failing to obtain the sensing result corresponding to the service type indicated by the first sensing request. In this case, the NEF can send the aforementioned information 1 to the AF, indicating that the first sensing request processing has failed.

[0205] The following section, with reference to Figure 3, describes the various operations of method 300 in scenario example 2.

[0206] S340, the SCF receives a first sensing request from the AF, wherein the first sensing request is used to request a first sensing result. Correspondingly, the AF sends a first sensing request to the SCF.

[0207] Examples of the first sensing request and the first sensing result are given above. For example, refer to the description of S310, where the receiver of the first sensing request is replaced by SCF instead of NEF. This will not be repeated here.

[0208] In some examples, such as in scenario example 2, the above-mentioned S340 may be that the SCF receives the first perception request directly from the AF.

[0209] In other examples, S340 described above is not limited to scenario example 2. For example, S340 may include S330. That is, if the NEF determines that the first perception request does not meet the first condition, the NEF may send the first perception request to the SCF. Correspondingly, the SCF receives the first perception request from the NEF.

[0210] The first sensing request sent by NEF comes from AF. Therefore, the above scheme can also be understood as SCF indirectly receiving the first sensing request from AF.

[0211] S350, if the first sensing request meets the first condition, the SCF sends first information to the AF, which indicates the second sensing result. Correspondingly, the AF receives the first information from the SCF.

[0212] In some possible implementations, method 300 further includes: SCF determining that the first sensing request satisfies the first condition.

[0213] For a specific example of the first message, please refer to the previous text. For example, refer to the description of S320, and replace the sender of the first message with SCF. This will not be repeated here.

[0214] In scenario example 1, the SCF can send the first information to the AF via the NEF.

[0215] In scenario example 2, the SCF can directly send the first message to the AF.

[0216] S360, if the first perception request does not meet the first condition, the SCF processes the first perception request.

[0217] In some possible implementations, method 300 further includes: SCF determining that the first sensing request does not satisfy the first condition.

[0218] In some other possible implementations, the first perception request received by the SCF comes from the NEF, i.e., applicable to scenario example 1. The SCF may not need to determine whether the first perception request meets the first condition.

[0219] In some other possible implementations, regardless of whether the first sensing request received by the SCF comes directly from the AF or from the NEF, the SCF must determine whether the first sensing request meets the first condition.

[0220] Based on the above scheme, SCF can flexibly handle different sensing requests in different ways when an existing sensing task is being executed. For example, if sensing request #1 meets the first condition, the sensing results of the existing sensing task can be reused, thereby avoiding the overhead and latency of sensing and measuring again. Conversely, if sensing request #2 does not meet the first condition, it can be further processed.

[0221] As an example of scenario example 1, method 300 may include: S310, S320.

[0222] As another example of scenario example 1, method 300 may include: S310, S330 (or S340), S360.

[0223] As an example of scenario example 2, method 300 may include: S340, S350.

[0224] As another example of scenario example 2, method 300 may include: S340, S360.

[0225] The following examples illustrate the first condition.

[0226] The first condition can be the condition for reusing the second perception result.

[0227] The above scheme can also be understood or replaced as follows: the first condition is the condition of reusing the second perception request or the second perception task.

[0228] For example, if the first perception request meets the first condition, then the second perception result is reused as the response to the first perception request. As another example, if the first perception request meets the first condition, then the second perception task or its perception result (i.e., the second perception result) is reused as the response to the first perception request. Yet another example, if the first perception request meets the first condition, then the second perception request or its corresponding perception result (i.e., the second perception result) is reused as the response to the first perception request.

[0229] Here, "reuse" can also be understood as or replaced by "use," "application," or "aggregation," etc. "Reuse second sensing request" can also be understood as or replaced by parallel processing of sensing requests, concurrent processing of sensing requests, or aggregation of sensing requests, etc.

[0230] SCF can have the ability to reuse sensing requests. "Having the ability to reuse sensing requests" can also be understood as or replaced by supporting parallel processing of sensing requests, supporting concurrent processing of sensing requests, supporting concurrent sensing requests, supporting aggregated sensing requests, or other expressions.

[0231] In some examples, the first condition can also be understood as a condition using the second perception result, the second perception task, or the second perception request.

[0232] For example, if the first perception request meets the first condition, then the second perception result is used as the response to the first perception request. As another example, if the first perception request meets the first condition, then the perception result of the second perception task (i.e., the second perception result) is used as the response to the first perception request. Yet another example, if the first perception request meets the first condition, then the perception result corresponding to the second perception request (i.e., the second perception result) is used as the response to the first perception request.

[0233] In other examples, the first condition can also be understood as the condition for applying the second perception result, the second perception task, or the second perception request.

[0234] For example, if the first perception request satisfies the first condition, then the second perception result is applied to the response to the first perception request. As another example, if the first perception request satisfies the first condition, then the second perception task or its perception result (i.e., the second perception result) is applied to the response to the first perception request. Yet another example, if the first perception request satisfies the first condition, then the second perception request or its corresponding perception result (i.e., the second perception result) is applied to the response to the first perception request.

[0235] The aforementioned "response to the first perception request" can also be understood or replaced as "the result of the first perception".

[0236] As another exemplary representation of applying a second perception result, a second perception task, or a second perception request to a first perception result, the first perception result may be applicable to the second perception result, the second perception task, or the second perception request; or, the first perception request may be applicable to the second perception result, the second perception task, or the second perception request.

[0237] In some other examples, the first condition can also be understood as the condition that aggregates the second perception result, the second perception task, or the second perception request.

[0238] For example, if the first perception request meets the first condition, then the second perception result is aggregated into the first perception result. As another example, if the first perception request meets the first condition, then the perception result of the second perception task (i.e., the second perception result) is aggregated into the first perception result. Yet another example, if the first perception request meets the first condition, then the first perception request and the second perception request are aggregated; that is, the perception result corresponding to the second perception request (i.e., the second perception result) is aggregated into the first perception result.

[0239] The term "aggregate" can also be replaced or understood as "combine," "merge," or other similar terms such as "current."

[0240] The first condition may also be called a reuse condition, aggregation condition, or other names, which are not limited in this application.

[0241] For example, the first condition includes at least one of the following conditions:

[0242] Condition 1: The first business type is the same as the second business type. The second business type can be an existing business type for the second sensing task.

[0243] Condition 2: The second sensing task satisfies the first QoS requirement; or

[0244] Condition 3: The first perception area belongs to the second perception area. The second perception area can be an existing perception area for a second perception task.

[0245] As an example, the first condition includes the above three items. If all three items are satisfied, the first perception request satisfies the first condition.

[0246] As another example, the first condition includes any two of the above. If both conditions are met, the first perception request satisfies the first condition.

[0247] As another example, the first condition includes any one of the above. If all of the above conditions are met, the first perception request satisfies the first condition.

[0248] The first condition may not be limited to the above three items, and may include other content, which is not limited in this application.

[0249] Based on the above scheme, the first condition can reasonably determine whether the second perception result can be reused.

[0250] The following are some examples of S360 (SCF handles first perception requests).

[0251] Figure 4 is a schematic flowchart of processing the first perception request provided in an embodiment of this application. Some examples of S360 are described below with reference to Figure 4.

[0252] As some examples of S360, SCF can establish a first perception task, thereby providing perception services in response to the first perception request.

[0253] "Establishing the first perception task" can include creating a new first perception task or updating an existing second perception task as the first perception task.

[0254] In some possible implementations, S360 may include: S410, whereby the SCF sends second information to the SPF, the second information being used to establish the first sensing task.

[0255] The first sensing task can be a sensing task that satisfies a first sensing request. For example, the service type of the first sensing task can be a first service type. Another example is that the sensing area of ​​the first sensing service can be a first sensing area. Yet another example is that the QoS requirement of the first sensing task can be a first QoS requirement.

[0256] The second information may also be referred to as a perception task creation request, or it may be carried within the perception task creation request. This application is not limited in this regard, and the second information may also be referred to by other names, or it may be carried in other messages. Further descriptions of the second information are provided below.

[0257] SCF can update the sensing parameters of RAN.

[0258] In some possible implementations, method 300 further includes: S420, the SCF sends third information to the first access network element, the third information being used to indicate the first sensing parameters. Correspondingly, the first access network element receives the third information from the SCF.

[0259] The first access network element can be an access network device (e.g., RAN), a component in the access network device (e.g., processor, device, circuit, chip, or chip system), or a functional module capable of implementing access functions.

[0260] For ease of understanding and description, the following description will take RAN as the first access network element, which can be denoted as RAN#1.

[0261] RAN#1 can be used to execute the first sensing task based on the first sensing parameters. RAN#1 can be a RAN that has already executed the second sensing task or is currently executing the second sensing task. For example, RAN#1 can be used to execute the second sensing task before the first sensing task is established. As another example, RAN#1 can execute the second sensing task before the third information is received.

[0262] The first perception parameter can be a perception parameter of the first perception task. The first perception parameter can be a full set of parameters or an incremental parameter relative to the second perception task.

[0263] In some possible implementations, method 300 further includes: S430, the SCF sends fourth information to the second access network element, the fourth information being used to indicate the second sensing parameters. Correspondingly, the second access network element receives the fourth information from the SCF.

[0264] The second access network element can be an access network device (e.g., RAN), a component in the access network device (e.g., processor, device, circuit, chip, or chip system), or a functional module capable of implementing access functions.

[0265] For ease of understanding and description, the following description will take RAN as the second access network element, which can be denoted as RAN#2.

[0266] RAN#2 can be used to execute the first sensing task within the third sensing region based on the second sensing parameter. RAN#2 can be a RAN different from RAN#1. Before the first sensing task is established, RAN#2 may not execute any sensing task, or it may execute other sensing tasks besides the second sensing task. Compared to RAN#1, RAN#2 can be understood as a newly added RAN.

[0267] When the SCF sends the fourth information, RAN#1 and RAN#2 can perform the first sensing task within the first sensing area.

[0268] The first sensing region may include a second sensing region and a third sensing region. RAN#1 performs the first sensing task within the second sensing region, while RAN#2 may perform the first sensing task within the third sensing region.

[0269] The third sensory region can be a part of the first sensory region; in other words, the third sensory region belongs to the first sensory region. The third sensory region is different from the second sensory region. For example, the third sensory region does not belong to the second sensory region.

[0270] In some examples, the first sensory region consists of a second sensory region and a third sensory region.

[0271] In other examples, the first sensing region includes the second sensing region, the third sensing region, and other sensing regions.

[0272] The second perception parameter can be a perception parameter of the first perception task. The second perception parameter can be the same as or different from the first perception parameter; this application does not impose any restrictions.

[0273] For example, the second information may include at least one of the following:

[0274] The identification information for the first sensing task. For example, the identification information for the first sensing task could be a session ID;

[0275] The identification information of the second access network element. For example, the ID of RAN#2, address information, the identifier of the area where RAN#2 is located (e.g., cell, TA or other area), or other information;

[0276] The location information of the second access network element; or

[0277] Information about the third sensing area. For example, the identifier, specific range, or other information of the third sensing area.

[0278] The second information may also include other information, which is not limited in this application. The SCF's processing method for the first perception request varies depending on the circumstances. If the SCF needs to establish a first perception task, the content of the second information may differ. See the examples below for details.

[0279] The following is an example of condition 1 (the first business type is the same as the second business type).

[0280] In some possible implementations, S360 includes: S362, in the case that the first service type is different from the second service type (i.e., the first perception request does not meet condition 1), the SCF processes the first perception request according to the relationship between the resource consumption corresponding to the first service type and the resource consumption corresponding to the second service type.

[0281] The resource consumption corresponding to the first service type can be understood as the resource consumption of the RAN in executing the perception task of the first service type.

[0282] For example, resource consumption may include computing power consumption and / or bandwidth consumption.

[0283] The computational overhead can be the processing overhead caused by the RAN performing data processing, transmitting and receiving sensing signals, or other sensing-related operations.

[0284] Among them, bandwidth consumption can be the bandwidth overhead occupied by the RAN for transmitting and receiving sensing signals.

[0285] The aforementioned resources may also be referred to as "sensing resources," "sensing measurement resources," "measurement resources," or other names, and this application does not limit them.

[0286] In this embodiment, resource consumption can also be replaced by: the amount of information in the first sensing result, the quality of the first sensing result, the accuracy of the first sensing result, or other parameters related to resource consumption.

[0287] Based on the above scheme, SCF can further process the first sensing request based on the resource consumption relationship when the business type is different, thereby effectively handling the first sensing request. For example, if the resource consumption corresponding to the business type of the first sensing request is greater, SCF can create a new sensing task or update the existing sensing task. Conversely, if the resource consumption corresponding to the business type of the first sensing request is smaller, SCF can reuse the existing sensing task.

[0288] In some possible implementations, the SCF can determine how to process the data based on the aforementioned resource consumption. For example, the SCF can send a third message to RAN#1, indicating the first sensing parameters, and a second message to the SPF, indicating the establishment of the first sensing task. Alternatively, the SCF can simply send the second message to the SPF without updating the sensing parameters. Yet another example is that the SPF can neither update the sensing parameters nor establish the first sensing task, but instead determine a new sensing result (e.g., the first sensing result) based on the existing sensing result (e.g., the second sensing result). These are described in detail below, referred to as Processing Example 1, Processing Example 2, and Processing Example 3, respectively.

[0289] Processing Example 1:

[0290] In some possible implementations, S362 includes: if the resource consumption corresponding to the first service type is greater than or equal to the resource consumption corresponding to the second service type, the SCF executes S410, that is, the SCF sends the second information to the SPF according to the first perception request.

[0291] In this context, “greater than or equal to” can be replaced with “greater than”.

[0292] The second piece of information can be used to establish the first sensing task. The business type of this first sensing task can be the first business type.

[0293] For example, the second information may include at least one of the following:

[0294] The identification information for this first sensing task;

[0295] Information about the first business type is used to indicate the first business type; or

[0296] The information for the first QoS requirement is used to indicate the first QoS requirement.

[0297] As an example, suppose the first service type is target speed measurement, sensing area monitoring, or target imaging, while the second service type is presence indication. In this scenario, the second sensing task being executed (or already existing) cannot provide the sensing service for the first service type; that is, it cannot meet the new sensing service requirement. The SCF can send a second message to the SPF, instructing the SPF to execute the new sensing service requirement, i.e., to establish the first sensing task.

[0298] In some possible implementations, the SCF can also perform S420, that is, the SCF sends a third message to RAN#1, which is used to indicate the first sensing parameter.

[0299] In some examples, the first sensing parameter can be the full set of sensing parameters.

[0300] In other examples, the first perception parameter may be an updated perception parameter relative to an existing perception task (e.g., a second perception task).

[0301] For example, the first sensing parameter may include parameters in the QoS requirements (referred to as "QoS parameters"), or parameters derived from the QoS requirements.

[0302] Some QoS parameters in the first sensing parameters may have higher requirements than the original QoS parameters of RAN#1. For example, compared to RAN#1 performing sensing measurements and reporting sensing measurement data based on the original sensing parameters, RAN#1 may send sensing measurement data more frequently based on the first sensing parameters, or the location accuracy of the sent sensing measurement data may be higher, or the quality of the sent sensing measurement data may be higher, or the amount of information in the sent sensing measurement data may be higher.

[0303] Higher positional accuracy can be understood as a smaller positional error. For example, a positional accuracy of 1 meter (m) means a maximum positional error of 1 meter, while a positional accuracy of 10 centimeters (cm) means a maximum positional error of 10 centimeters. It is understandable that a positional accuracy of 1 meter is lower than a positional accuracy of 10 centimeters.

[0304] For example, if the reporting period for the sensing results is 1 second (s), then the reporting period for the sensing measurement data required by RAN#1 can be less than 1 second. For example, the reporting period for the sensing measurement data in the first sensing parameter can be 500 milliseconds (ms), thus allowing for a delay budget to calculate the sensing results.

[0305] Optionally, the first perception parameter includes information about the first service type. Optionally, the first perception parameter and the information about the first service type are carried in the same message.

[0306] In some examples, the SPF can generate a perception result of a first service type for a first perception request, and a perception result of a second service type for a second perception request, based on better (e.g., higher quality or higher accuracy) sensing measurement data sent by RAN#1. For example, for the first perception request, the SPF can send the result of target velocity measurement, sensing area monitoring, or target imaging to the SCF. As another example, for the second perception request, the SPF can send a presence indication to the SCF.

[0307] Processing Example 2:

[0308] In some possible implementations, S362 includes: if the resource consumption corresponding to the first service type is less than or equal to the resource consumption corresponding to the second service type, the SCF executes S410, that is, the SCF sends the second information to the SPF according to the first perception request.

[0309] In this context, "less than or equal to" can be replaced with "less than".

[0310] The second piece of information can be used to establish the first sensing task. The business type of this first sensing task can be the first business type.

[0311] For example, the second information may include at least one of the following:

[0312] The identification information for this first sensing task;

[0313] Information about the first business type is used to indicate the first business type; or

[0314] The information for the first QoS requirement is used to indicate the first QoS requirement.

[0315] As an example, suppose the first service type is presence indication, and the second service type is target speed measurement, sensing area monitoring, or target imaging. In this case, the second sensing task being executed (or already existing) cannot directly provide the sensing service of the first service type; that is, it cannot directly meet the new sensing service requirement. The SCF can send a second message to the SPF, instructing the SPF to execute the new sensing service requirement, i.e., to establish the first sensing task.

[0316] In some possible implementations, the SCF also performs S420, that is, the SCF can send a third message to RAN#1, which is used to indicate the first sensing parameter.

[0317] In some examples, the first sensing parameter can be the full set of sensing parameters.

[0318] In other examples, the first perception parameter may be an updated perception parameter relative to an existing perception task (e.g., a second perception task).

[0319] Optionally, the first perception parameter includes information about the first service type. Optionally, the first perception parameter and the information about the first service type are carried in the same message.

[0320] In other examples, the SCF may not execute S420. For instance, the SCF may not update the sensing parameters of RAN#1, but instead instruct the SPF to establish the first sensing task. For example, RAN#1 can obtain the sensing measurement data based on existing sensing parameters (e.g., the sensing parameters of the second sensing task) to obtain the sensing results for the first service type. In this way, the SCF does not need to update the sensing parameters, thereby reducing the transmission overhead caused by updating the sensing parameters.

[0321] Processing Example 3:

[0322] In some possible implementations, S362 includes: if the resource consumption corresponding to the first service type is less than or equal to the resource consumption corresponding to the second service type, the SCF executes S440, that is, the SCF sends an indication information of the first sensing result to the AF.

[0323] In some examples, the first perception result can be determined based on the second perception result. For instance, the SCF can generate the first perception result based on the second perception result reported by the SPF. Or, for another example, the SCF can generate the first perception result based on a second perception result previously determined by the SCF.

[0324] In other examples, the first perceptual result may be determined based on the second perceptual task. For instance, the first perceptual result may be determined based on the perceptual result of the second perceptual task. Yet another example is that the first perceptual result may be determined based on perceptual measurement data from the second perceptual task.

[0325] Based on the above scheme, SCF can establish a perception task for the first perception request based on the relationship between resource consumption, or determine the perception result corresponding to the first perception request based on the previous perception results, thereby effectively processing the first perception request.

[0326] The following is an example of condition 2 (the second perception task satisfies the first QoS requirement).

[0327] The failure of the first sensing request to meet the first condition can also be understood as the first QoS requirement indicated by the first sensing request not matching the existing sensing task (e.g., the second sensing task), or as the first QoS requirement indicated by the first sensing request not matching the QoS requirement of the existing sensing task (e.g., the second QoS requirement). Therefore, the failure of the first sensing request to meet the first condition can include the situation where the second sensing task does not meet the first QoS requirement.

[0328] In some possible implementations, S360 includes: if the second sensing task does not meet the first QoS requirement (i.e., the first sensing request does not meet condition 2), the SCF executes S410, that is, the SCF can send second information to the second sensing network element according to the first sensing request.

[0329] As an example, suppose a certain QoS parameter in the first QoS requirement is 500ms, which means that RAN#1 reports sensing measurement data to SCF or SPF once every 500ms. However, based on the second sensing task, RAN#1 reports sensing measurement data to SCF or SPF once every 1s. Therefore, it can be considered that the second sensing task does not meet the QoS parameter in the first QoS requirement.

[0330] As another example, suppose a certain QoS parameter in the first QoS requirement is 100, which means that RAN#1 reports at least 100 data points in a single sensing measurement data report to SCF or SPF. However, based on the second sensing task, RAN#1 reports only 50 data points in each sensing measurement data report to SCF or SPF. Therefore, it can be considered that the second sensing task does not meet the QoS parameter in the first QoS requirement.

[0331] As another example, suppose a certain QoS parameter in the first QoS requirement is 10cm, which means that the location accuracy of the sensing result reported by the SCF or SPF is 10cm, while the location accuracy requirement for the sensing result in the second sensing task is 1m. Then it can be considered that the second sensing task does not meet the QoS parameter in the first QoS requirement.

[0332] The statement that the second sensing task does not meet the first QoS requirement can be understood as follows: some or all of the QoS parameters configured in the second sensing task do not meet some of the QoS parameters in the first QoS requirement; or it can be understood as some or all of the QoS parameters configured in the second sensing task do not meet all of the QoS parameters in the first QoS requirement.

[0333] For example, if any QoS parameter in the first QoS requirement is not satisfied by the second sensing task, then the second sensing task does not satisfy the first QoS requirement, that is, the first sensing request does not satisfy condition 2.

[0334] For example, if certain QoS parameters in the first QoS requirement (e.g., certain QoS parameters determined by RAN#1, certain predefined QoS parameters, or certain QoS parameters indicated by SCF or SPF) are not satisfied by the second sensing task, then the second sensing task does not satisfy the first QoS requirement, that is, the first sensing request does not satisfy condition 2.

[0335] For example, if all QoS parameters in the first QoS requirement are not satisfied by the second sensing task, then the second sensing task does not satisfy the first QoS requirement, that is, the first sensing request does not satisfy condition 2.

[0336] The second information can be used to establish a first sensing task. The QoS requirement of this first sensing task can be the first QoS requirement itself. Alternatively, the first sensing task can satisfy the first QoS requirement.

[0337] For example, the second information may include at least one of the following:

[0338] The identification information for this first sensing task;

[0339] Information on the first business type is used to indicate the first business type; or

[0340] The information for the first QoS requirement is used to indicate the first QoS requirement.

[0341] In some possible implementations, the SCF can also perform S420, that is, the SCF sends a third message to RAN#1, which is used to indicate the first sensing parameter.

[0342] In some examples, the first sensing parameter can be the full set of sensing parameters.

[0343] In other examples, the first perception parameter may be an updated perception parameter relative to an existing perception task (e.g., a second perception task).

[0344] For example, the first sensing parameter may include parameters in the QoS requirements (referred to as "QoS parameters"), or parameters derived from the QoS requirements.

[0345] Among them, some QoS parameters in the first perception parameters may have higher requirements than the original QoS parameters of RAN#1.

[0346] Other descriptions of the first perception parameter can be found in the aforementioned processing example 1, and will not be repeated here.

[0347] Based on the above scheme, if the existing sensing task does not meet the QoS requirements indicated by the new sensing request, SCF can establish a sensing task that meets the first QoS requirement, thereby realizing sensing.

[0348] The following is an example of condition 3 (the first sensory region belongs to the second sensory region).

[0349] In some possible implementations, S360 includes: if part or all of the area in the first sensing area does not belong to the second sensing area, the SCF executes S410, that is, the SCF sends second information to the second sensing network element according to the first sensing request.

[0350] The first perception request does not meet condition 3, which can also be understood as the first perception area exceeding the second perception area.

[0351] The second information is used to establish the first sensing task. The sensing area of ​​the first sensing task includes the first sensing region. For example, the sensing area of ​​the first sensing task can be the first sensing region itself. Alternatively, the sensing area of ​​the first sensing task can include the first sensing region and other regions.

[0352] In some possible implementations, prior to S410, method 300 further includes: the SCF determining, based on the first sensing area indicated by the first sensing request, whether it is necessary to notify (or invoke) a new access network element.

[0353] In some possible implementations, the SCF can also perform S430, that is, the SCF can send a fourth message to RAN#2, which is used to indicate the second sensing parameters.

[0354] As an example, the SCF can compare the sensing area (e.g., the second sensing area) corresponding to an existing (or currently being executed) sensing task (e.g., the second sensing task) with the first sensing area indicated by the first sensing request to obtain information about areas outside the sensing area corresponding to the existing sensing task (e.g., the third sensing area). The SCF can send sensing parameters (e.g., the second sensing parameters) to the RAN (e.g., RAN#2) corresponding to this area. If the RAN has not yet established a transmission channel for sensing measurement data with the SCF, the SCF can also send the SCF's address information to the RAN.

[0355] For example, the second information sent by the SCF to the SPF may include at least one of the following:

[0356] The identification information for this first sensing task;

[0357] Identification information of the second access network element;

[0358] The location information of the second access network element; or

[0359] Information from the third sensory region.

[0360] The information in the third sensory region can also be understood as the information in the newly added sensory region.

[0361] Optionally, the second information may also include information about the first QoS requirements.

[0362] RAN#2 can send sensing measurement data to SPF through existing sensing measurement data transmission channels. Alternatively, RAN#2 can establish a sensing measurement data transmission channel with SPF based on SPF's address information and send sensing measurement data to SPF.

[0363] This application does not specify whether the SCF should execute S420 if the first perception request does not meet condition 3. The SCF may or may not execute S420.

[0364] Based on the above scheme, when the sensing area indicated by the new sensing request exceeds the sensing area of ​​the existing sensing task, the SCF can establish a first sensing task, thereby enabling sensing in the new sensing area.

[0365] Those skilled in the art will understand that conditions 1 to 3 can be used in any combination, and will not be elaborated further.

[0366] Figure 5 is a schematic flowchart of another sensing method 500 provided in an embodiment of this application. Method 500 is described as a specific example of method 300. Optional operations in method 500 are shown in Figure 5 with dashed lines. Method 500 is described below with reference to Figure 5.

[0367] S510, RAN#1 transmits the sensing measurement data of the second sensing task to SPF. Correspondingly, SPF receives the sensing measurement data of the second sensing task from RAN#1.

[0368] Specifically, a second sensing task already exists before or during the execution of S510. This second sensing task can be initiated by a second sensing request from AF#2, that is, AF#2 subscribes to the sensing result of the second sensing request (denoted as the second sensing result).

[0369] S520, the SPF sends the indication information of the second sensing result to the SCF. Correspondingly, the SCF receives the indication information of the second sensing result from the SPF.

[0370] Optionally, the indication information of the second sensing result sent by SPF carries the session ID#2 corresponding to the second sensing task.

[0371] In other examples, the SPF can send sensing measurement data from RAN#1 to the SCF. The SCF can then determine a second sensing result based on this sensing measurement data.

[0372] In other examples, the SPF can send indications of the second sensing result directly to the AF.

[0373] S530, SCF sends an indication message of the second sensing result to AF#2.

[0374] If AF#2 belongs to a third party (Scenario Example 1), SCF can send the indication information of the second perception result to AF#2 via NEF. Optionally, the indication information sent by SCF to NEF can carry the associated ID#2 of the second perception task on NEF. Optionally, the indication information sent by NEF to AF#2 can carry the associated ID#2 of the second perception task on AF#2.

[0375] If AF#2 belongs to the operator (Scenario Example 2), SCF can directly send the indication information of the second sensing result to AF#2. Optionally, the indication information sent by SCF to AF can carry the associated ID#2 of the second sensing task on AF.

[0376] Here, the association ID#2 can correspond to the session ID#2. The association ID can also be called the transmission reference ID.

[0377] In other examples, the SPF can send indications of the second sensing results directly to the NEF.

[0378] S540, AF#1 initiates the first perception request to the network.

[0379] The above S540 can be understood as follows: when a sensing task already exists, AF#1 initiates a first sensing request to the network; or it can be understood as AF#1 and AF#2 initiating sensing requests within the same time period. For example, AF#1 and AF#2 initiate sensing requests within a first time period. The length of the first time period can be predefined, preconfigured, or determined by the operator's policy.

[0380] For a specific example of the first perception request, please refer to the previous text; it will not be repeated here.

[0381] In some examples, where AF#1 is a third party (Scenario Example 1), AF#1 can initiate a first perception request to NEF, i.e., S540 includes S310. Further, NEF can execute S320 or S330. If NEF executes S330, SCF can be understood as executing S340. Further, SCF can execute S350 or S360.

[0382] In other examples, where AF#1 belongs to the operator (Scenario Example 2), AF#1 can initiate a first sensing request to the SCF, i.e., S540 includes S340. Furthermore, the SCF can execute S350 or S360.

[0383] Optionally, if NEF executes S320, the first information sent by NEF to AF#1 may also include a first identifier. For example, the first identifier may be the associated ID#1 of the first sensing task on the AF.

[0384] Optionally, if the SCF executes S350, in scenario example 1, the first information sent by the SCF to the NEF also includes a second identifier. For example, the second identifier could be the association ID #1 corresponding to the first sensing task on the NEF. The first information sent by the NEF to AF #1 also includes the first identifier. For example, the first identifier could be the association ID #1 corresponding to the first sensing task on the AF.

[0385] Optionally, if the SCF executes S350, in scenario example 2, the first information sent by the SCF to AF#1 also includes a first identifier. For example, the first identifier could be the associated ID#1 of the first sensing task on the AF.

[0386] Optionally, if SCF executes S360, and the first sensing request does not meet condition 1, and the resource consumption corresponding to the first service type is less than or equal to the resource consumption corresponding to the second service type (see processing example 3), the indication information of the first sensing result may carry a first identifier. For example, the first identifier may be the associated ID#1 of the first sensing task on AF.

[0387] Optionally, if the SCF executes S360 and establishes a first sensing task, the indication information of the first sensing result (or sensing measurement data of the first sensing task) sent by the SPF to the SCF may carry the session ID#1 of the first sensing task.

[0388] Among them, the associated ID#1 can correspond to the session ID#1.

[0389] The communication device provided in the embodiments of this application will be described in detail below with reference to Figures 6 to 9. The description of the device embodiments corresponds to the description of the method embodiments. Therefore, for contents not described in detail, please refer to the method embodiments above. For the sake of brevity, some contents will not be repeated.

[0390] This application embodiment can divide the communication device into functional modules according to the above method example. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware, software, or a combination of both. The module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation. The following description uses the division of functional modules according to each function as an example.

[0391] Figure 6 is an exemplary block diagram of the communication device 10 provided in an embodiment of this application.

[0392] As shown in Figure 6, for example, the communication device 10 may include a chip system 110, a memory 120, a bus 130, a power management module 140, or a transceiver 150, etc.

[0393] The chip system 110 can be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed through integrated logic circuits in the hardware of the chip system 110 or through software instructions.

[0394] By way of example and not limitation, chip system 110 may include circuitry or chips responsible for signal processing (such as a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip or system-in-package (SIP) chip containing a modem core).

[0395] Optionally, the chip system 110 may also include a memory (such as a cache) for storing instructions and data. In some embodiments, the memory in the chip system 110 is a cache memory. This memory can store instructions or data that the chip system 110 has just used or that are used repeatedly. If the chip system 110 needs to use the instruction or data again, it can directly retrieve it from the memory. This avoids repeated accesses, reduces the waiting time of the chip system 110, and thus improves the efficiency of the system.

[0396] Optionally, a sensing module is provided in the chip system 110. This sensing module can be used to perform sensing measurements and / or sensing measurement data processing functions.

[0397] In some embodiments, the chip system 110 may include one or more interfaces. Interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0398] Memory 120 may include random access memory (RAM) and read-only memory (ROM). Memory 120 may store computer-readable, computer-executable code, including instructions that, when executed, cause the processor to perform the various functions described in this application.

[0399] Optionally, the code may include instructions for implementing various aspects of the embodiments of this application, such as instructions for receiving a first sensing request. The code may be stored in a non-transitory computer-readable medium such as system memory or other types of memory. In some cases, the code may not be directly executable by the chip system 110, but may enable a computer (e.g., at compile and execution time) to perform the functions described in this application. In some cases, memory 120 may contain a basic I / O system that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0400] For example, the chip system 110 executes various functional applications and data processing of the communication device 10 by running instructions stored in the memory 120. For instance, when the communication device 10 transfers files with other devices (which may also be terminals or access network devices), the chip system 110 of the communication device 10 can call the computer-executable program code stored in the memory 120 to implement the communication method provided in the embodiments of this application.

[0401] In addition, the memory 120 can be integrated into the chip system 110 or independent of the chip system 110.

[0402] For example, bus 130 may be USB for supporting communication between various parts of communication device 10.

[0403] The power management module 140 is used to receive charging input from the charger. Optionally, the power management module 140 can also supply power to the communication device 10 while charging it (e.g., the battery module of the communication device 10). By way of example and not limitation, the power management module 140 can also supply power to other devices besides the communication device 10.

[0404] Transceiver 150 can communicate bidirectionally via one or more antennas, wired links, or wireless links. For example, transceiver 150 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. Transceiver 150 may also include a modem for modulating packets and providing the modulated packets to the antenna for transmission, and for demodulating packets received from the antenna. Transceiver 150 may include a receiver and a transmitter, the receiver performing the function of receiving information and the transmitter performing the function of transmitting information.

[0405] In some cases, a wireless device may include a single antenna. However, in other cases, the device may have more than one antenna, such as antenna 1 and antenna 2 shown in FIG. 6, which may be capable of simultaneously transmitting or receiving multiple wireless transmissions. Exemplarily, antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in communication device 10 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In other embodiments, the antennas can be used in conjunction with a tuning switch. Communication device 10 can transfer files to other devices via wireless communication functions.

[0406] In one design, the communication device 10 may correspond to the first sensing network element in the above method embodiment.

[0407] The device 10 can implement the steps or processes corresponding to the first sensing network element in the above method embodiment. The transceiver 150 can be used to perform the transmission and reception related operations of the first sensing network element in the above method embodiment, for example, to perform step S340 in the above method embodiment. The chip system 110 can be used to perform the processing related operations of the first sensing network element in the above method embodiment, for example, to perform step S60 in the above method embodiment.

[0408] In another design, the communication device 10 may correspond to the NEF in the above method embodiment.

[0409] The device 10 can implement the steps or processes corresponding to the NEF execution in the above method embodiments. The transceiver 150 can be used to perform NEF transmission and reception related operations in the above method embodiments, such as executing step S330 in the above method embodiments. The chip system 110 can be used to perform NEF processing related operations in the above method embodiments.

[0410] In the design of the communication device 10 corresponding to NEF, the communication device 10 may include modules such as the short-range communication module 164, sensor 161, display 162, or camera 163 as shown in FIG6.

[0411] The short-range communication module 164 may include modules that support short-range communication, such as Wi-Fi and Bluetooth.

[0412] For example, sensor 161 may include pressure sensor, gyroscope sensor, barometric pressure sensor, magnetic sensor, accelerometer, distance sensor, proximity sensor, fingerprint sensor, temperature sensor, touch sensor, ambient light sensor, bone conduction sensor, etc.

[0413] For example, display 162 is used to display images, videos, etc. The display includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a mini light-emitting diode (LED), a micro LED, a micro OLED, a quantum dot light-emitting diode (QLED), etc. For example, in this embodiment, the display can be used to display the interface required by the communication device 10. For example, the communication device 10 implements display functions through a graphics processing unit (GPU), a display, and an application processor. The GPU is a microprocessor for image processing, connected to the display and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The chip system 110 may include one or more GPUs that execute program instructions to generate or modify display information.

[0414] For example, camera 163 is used to acquire images, videos, etc.

[0415] It is understood that the structure shown in Figure 6 does not constitute a specific limitation on the communication device 10, and the specific structure of the terminal device and / or access network device can be referred to Figure 6. In some embodiments, the communication device 10 may also include more or fewer components than shown in Figure 6, or combine some components, or split some components, or have different component arrangements, etc. Alternatively, some components shown in Figure 6 may be implemented in hardware, software, or a combination of software and hardware, and the terminal device and / or access network device may add or reduce components based on the structure given in Figure 6.

[0416] Figure 7 is a schematic block diagram of the communication device 20 provided in an embodiment of this application.

[0417] As shown in Figure 7, the communication device 20 may include a baseband unit 210, which can communicate with external devices via a cellular radio frequency (RF) transceiver 220 (e.g., if the communication device 20 is a terminal device, the baseband unit 210 can communicate with access network devices via the cellular RF transceiver 220; or, if the communication device 20 is an access network device, the baseband unit 210 can communicate with terminal devices and / or core network devices via the cellular RF transceiver 220). Optionally, the baseband unit 210 includes a sensing unit. This sensing unit can be used for sensing and / or processing sensing and measurement data.

[0418] Exemplarily, baseband unit 210 may include computer-readable media and / or memory. Baseband unit 210 may be responsible for general processing, including the execution of software stored on the computer-readable media / memory. When executed by baseband unit 304, the software causes baseband unit 210 to perform the various functions described above. The computer-readable media / memory may also be used to store data manipulated by baseband unit 210 when executing the software.

[0419] Optionally, the baseband unit 210 further includes a receiving unit 201, a management unit 202, and a transmitting unit 203. The management unit 202 includes one or more sub-units shown in FIG. 7. For example, a condition judgment sub-unit, which can be used to perform the operation of judging whether the first sensing request meets a first condition in the above method embodiments. The units within the management unit 201 can be stored in a computer-readable medium / memory and / or configured as hardware within the baseband unit 210. The receiving unit 201 and the transmitting unit 203 can be referred to as transceiver units.

[0420] When the communication device 20 is used to implement the function of the first sensing network element in the above method embodiments, the receiving unit 201 is used to perform the receiving step of the first sensing network element, the sending unit 203 is used to perform the sending step of the first sensing network element, and the management unit 202 is used to perform the processing step of the first sensing network element.

[0421] For example, when the communication device 20 is used to implement the function of the first sensing network element in the above method embodiments, the receiving unit 201 is used to receive a first sensing request from the application function network element, the first sensing request being used to request a first sensing result; if the first sensing request meets a first condition, the sending unit 203 is used to send first information to the application function network element, the first information being used to indicate a second sensing result; or, if the first sensing request does not meet the first condition, the management unit 202 is used to process the first sensing request; wherein, the first condition is the condition for reusing the second sensing result, and the second sensing result is the sensing result of the second sensing task.

[0422] For example, when the device 20 is used to perform the methods in Figures 3 to 5, the receiving unit 201 can be used to perform the step of receiving information in the method; the management unit 202 can be used to perform the processing step in the method; and the sending unit 203 can be used to perform the step of sending information in the method.

[0423] When the communication device 20 is used to implement the NEF function in the above method embodiments, the receiving unit 201 is used to perform the NEF receiving step, the sending unit 203 is used to perform the NEF sending step, and the management unit 202 is used to perform the NEF processing step.

[0424] For example, when the communication device 20 is used to implement the NEF function in the above method embodiments, the receiving unit 201 is used to receive a first sensing request from the application function network element, the first sensing request being used to request a first sensing result; if the first sensing request meets a first condition, the sending unit 203 is used to send first information to the application function network element, the first information being used to indicate a second sensing result; or, if the first sensing request does not meet the first condition, the sending unit 203 is used to send the first sensing request to the first sensing network element; wherein, the first condition is the condition for reusing the second sensing result, the second sensing result is the sensing result of the second sensing task, and the first sensing network element is used to process the first sensing request.

[0425] For example, when the device 20 is used to perform the methods in Figures 3 to 5, the receiving unit 201 can be used to perform the step of receiving information in the method; the management unit 202 can be used to perform the processing step in the method; and the sending unit 203 can be used to perform the step of sending information in the method.

[0426] For a more detailed description of the receiving unit 201, management unit 202 and sending unit 203, please refer to the relevant descriptions in the above method embodiments, which will not be repeated here.

[0427] By way of example and not limitation, the chip system in this application is shown in Figure 8, which is a schematic block diagram of the chip system 30 provided in an embodiment of this application. The chip system includes, but is not limited to, a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip or system-in-package (SIP) chip containing a modem core.

[0428] As can be seen from Figure 8, the chip system (or processing system) includes a processor 310, a memory 320, and an input / output interface 330.

[0429] The processor 310 can be a processing circuit in the chip system (including at least one processor, such as processor 1 and processor 2 as shown in FIG8). The processor 310 can be coupled to the memory 320 to call the instructions in the memory 320, so that the chip system can implement the methods and functions of the various embodiments of this application. The input / output interface 330 can be an input / output circuit in the chip system, which outputs the information processed by the chip system, or inputs the data or signaling information to be processed into the chip system for processing.

[0430] As one approach, the chip system is used to implement the operations performed by the first sensing network element or NEF in the various method embodiments described above.

[0431] For example, processor 310 is used to implement the processing-related operations performed by the first sensing network element or NEF in the above method embodiments, as described in the foregoing embodiments; input / output interface 330 is used to implement the sending and / or receiving-related operations performed by the first sensing network element or NEF in the above method embodiments, as described in the foregoing embodiments.

[0432] As an example and not a limitation, the chip system in this application is shown in FIG9, which is a schematic block diagram of the chip system 40 provided in an embodiment of this application.

[0433] As shown in Figure 9, the chip system (or processing system) includes an input / output interface 410 and logic circuitry 420. The input / output interface 410 can be an input / output circuit within the chip system, outputting processed information or inputting data or signaling information to be processed. For details, please refer to the descriptions in the preceding embodiments, executing, for example, the embodiments shown in Figures 3 to 5. The logic circuitry 420 is used to execute the aforementioned communication method, and for details, please refer to the descriptions in the preceding embodiments.

[0434] As one approach, the chip system is used to implement the operations performed by the first sensing network element or NEF in the various method embodiments described above.

[0435] For example, logic circuit 420 is used to implement processing-related operations performed by the first sensing network element or NEF in the above method embodiments; input / output interface 410 is used to implement transmission and / or reception-related operations performed by the first sensing network element or NEF in the above method embodiments.

[0436] This application also provides a computer-readable storage medium storing computer instructions for implementing the methods executed by the device in the above-described method embodiments.

[0437] For example, when the computer program is executed by a computer, it enables the computer to implement the methods executed by the first sensing network element or the NEF in the various embodiments of the above methods.

[0438] This application also provides a computer program product comprising instructions that, when executed by a computer, implement the methods performed by the first sensing network element or the NEF in the above-described method embodiments.

[0439] This application also provides a communication system, including the aforementioned first sensing network element and NEF.

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

[0441] Those skilled in the art will recognize that the units and algorithm steps of the various examples 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 implementation should not be considered beyond the scope of this application.

[0442] Those skilled in the art will 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.

[0443] 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.

[0444] 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.

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

[0446] 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 technical solution of this application, in essence, or the part that contributes to the prior art, 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, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

Claims

1. A sensing method, characterized in that, The method includes: Receive a first perception request from an application function network element, wherein the first perception request is used to request a first perception result; If the first sensing request meets the first condition, first information is sent to the application function network element, the first information indicating the second sensing result; or... If the first sensing request does not meet the first condition, process the first sensing request; The first condition is the condition for reusing the second perception result, where the second perception result is the perception result of the second perception task.

2. The method according to claim 1, characterized in that, The first information includes the second perception result; or, The first information includes first indication information, which is used to indicate the reuse of the second sensing result.

3. The method according to claim 1 or 2, characterized in that, The first perception request is used to indicate at least one of a first service type, a first quality of service (QoS) requirement, or a first perception area; The first condition includes at least one of the following: The first business type is the same as the second business type, and the second business type is the business type of the second sensing task. The second sensing task satisfies the first QoS requirement; or, The first sensing region belongs to the second sensing region, and the second sensing region is the sensing region of the second sensing task.

4. The method according to claim 3, characterized in that, If the first sensing request does not meet the first condition, the first sensing request is processed, including: If the first service type is different from the second service type, the first perception request is processed according to the relationship between the resource consumption of the first service type and the resource consumption of the second service type.

5. The method according to claim 4, characterized in that, The step of processing the first perception request based on the relationship between the resource consumption corresponding to the first service type and the resource consumption corresponding to the second service type includes: If the resource consumption corresponding to the first service type is greater than or equal to the resource consumption corresponding to the second service type, then, based on the first sensing request, the second information is sent to the second sensing network element; or... When the resource consumption corresponding to the first service type is less than or equal to the resource consumption corresponding to the second service type, according to the first perception request, the second information is sent to the second perception network element, or, according to the first perception request, the indication information of the first perception result is sent to the application function network element, wherein the first perception result is determined based on the second perception result; The second information is used to establish a first perception task, and the business type of the first perception task is the first business type.

6. The method according to claim 3, characterized in that, If the first sensing request does not meet the first condition, the first sensing request is processed, including: If the second sensing task does not meet the first QoS requirement, second information is sent to the second sensing network element according to the first sensing request. The second information is used to establish the first sensing task, wherein the first sensing task meets the first QoS requirement.

7. The method according to claim 3, characterized in that, If the first sensing request does not meet the first condition, the first sensing request is processed, including: If some or all of the areas in the first sensing area do not belong to the second sensing area, second information is sent to the second sensing network element according to the first sensing request. The second information is used to establish a first sensing task, and the sensing area of ​​the first sensing task includes the first sensing area.

8. The method according to any one of claims 5 to 7, characterized in that, The method further includes: Sending third information to a first access network element, the third information being used to indicate first sensing parameters, wherein the first access network element is used to perform the first sensing task according to the first sensing parameters; and / or, A fourth message is sent to the second access network element. The fourth message is used to indicate a second sensing parameter. The second access network element is used to perform the first sensing task in a third sensing area according to the second sensing parameter. The third sensing area belongs to the first sensing area and does not belong to the second sensing area.

9. The method according to any one of claims 5 to 8, characterized in that, The second information includes at least one of the following: The identification information of the first sensing task; Identification information of the second access network element; Location information of the second access network element; or... Information from the third sensory region.

10. The method according to any one of claims 1 to 9, characterized in that, The first information includes a first identifier, which is associated with the first perception request.

11. A sensing method, characterized in that, include: Receive a first perception request from an application function network element, wherein the first perception request is used to request a first perception result; If the first sensing request meets the first condition, first information is sent to the application function network element, the first information indicating the second sensing result; or... If the first sensing request does not meet the first condition, the first sensing request is sent to the first sensing network element. Wherein, the first condition is the condition for reusing the second perception result, the second perception result is the perception result of the second perception task, and the first perception network element is used to process the first perception request.

12. The method according to claim 11, characterized in that, The first perception request is used to indicate at least one of a first service type, a first quality of service (QoS) requirement, or a first perception area; The first condition includes at least one of the following: The first business type is the same as the second business type, and the second business type is the business type of the second sensing task. The second sensing task satisfies the first QoS requirement; or, The first sensing region belongs to the second sensing region, and the second sensing region is the sensing region of the second sensing task.

13. A communication device, characterized in that, It includes a transceiver unit and a processing unit, wherein, The transceiver unit is used to receive a first sensing request from an application function network element, wherein the first sensing request is used to request a first sensing result. If the first sensing request meets the first condition, the transceiver unit is further configured to send first information to the application function network element, wherein the first information is used to indicate the second sensing result; or... If the first sensing request does not meet the first condition, the processing unit is used to process the first sensing request; The first condition is the condition for reusing the second perception result, where the second perception result is the perception result of the second perception task.

14. The apparatus according to claim 13, characterized in that, The first information includes the second perception result; or, The first information includes first indication information, which is used to indicate the reuse of the second sensing result.

15. The apparatus according to claim 13 or 14, characterized in that, The first perception request is used to indicate at least one of a first service type, a first quality of service (QoS) requirement, or a first perception area; The first condition includes at least one of the following: The first business type is the same as the second business type, and the second business type is the business type of the second sensing task. The second sensing task satisfies the first QoS requirement; or, The first sensing region belongs to the second sensing region, and the second sensing region is the sensing region of the second sensing task.

16. The apparatus according to claim 15, characterized in that, When the first service type is different from the second service type, the processing unit is specifically used to process the first perception request based on the relationship between the resource consumption corresponding to the first service type and the resource consumption corresponding to the second service type.

17. The apparatus according to claim 16, characterized in that, If the resource consumption corresponding to the first service type is greater than or equal to the resource consumption corresponding to the second service type, the transceiver unit is further configured to send second information to the second sensing network element according to the first sensing request; or... When the resource consumption corresponding to the first service type is less than or equal to the resource consumption corresponding to the second service type, the transceiver unit is further configured to send second information to the second sensing network element according to the first sensing request, or the transceiver unit is further configured to send indication information of the first sensing result to the application function network element according to the first sensing request, wherein the first sensing result is determined based on the second sensing result; The second information is used to establish a first perception task, and the business type of the first perception task is the first business type.

18. The apparatus according to claim 15, characterized in that, If the second sensing task does not meet the first QoS requirement, the transceiver unit is further configured to send second information to the second sensing network element according to the first sensing request, the second information being used to establish the first sensing task, wherein the first sensing task meets the first QoS requirement.

19. The apparatus according to claim 15, characterized in that, In the case where some or all of the areas in the first sensing area do not belong to the second sensing area, the transceiver unit is further configured to send second information to the second sensing network element according to the first sensing request, the second information being used to establish a first sensing task, the sensing area of ​​the first sensing task including the first sensing area.

20. The apparatus according to any one of claims 17 to 19, characterized in that, The transceiver unit is further configured to send third information to the first access network element, the third information being used to indicate first sensing parameters, wherein the first access network element is configured to perform the first sensing task according to the first sensing parameters; and / or, The transceiver unit is further configured to send fourth information to the second access network element, the fourth information being used to indicate second sensing parameters, the second access network element being used to perform the first sensing task in a third sensing area according to the second sensing parameters, the third sensing area belonging to the first sensing area and not belonging to the second sensing area.

21. The apparatus according to any one of claims 17 to 20, characterized in that, The second information includes at least one of the following: The identification information of the first sensing task; Identification information of the second access network element; Location information of the second access network element; or... Information from the third sensory region.

22. The apparatus according to any one of claims 13 to 21, characterized in that, The first information includes a first identifier, which is associated with the first perception request.

23. A communication device, characterized in that, Including transceiver units, among which, The transceiver unit is used to receive a first sensing request from an application function network element, wherein the first sensing request is used to request a first sensing result. If the first sensing request meets the first condition, the transceiver unit is further configured to send first information to the application function network element, wherein the first information is used to indicate the second sensing result; or... If the first sensing request does not meet the first condition, the transceiver unit is further configured to send the first sensing request to the first sensing network element. Wherein, the first condition is the condition for reusing the second perception result, the second perception result is the perception result of the second perception task, and the first perception network element is used to process the first perception request.

24. The apparatus according to claim 23, characterized in that, The first perception request is used to indicate at least one of a first service type, a first quality of service (QoS) requirement, or a first perception area; The first condition includes at least one of the following: The first business type is the same as the second business type, and the second business type is the business type of the second sensing task. The second sensing task satisfies the first QoS requirement; or, The first sensing region belongs to the second sensing region, and the second sensing region is the sensing region of the second sensing task.

25. A communication device, characterized in that, include: A processor configured to execute a computer program or instructions to cause the method of any one of claims 1 to 12 to be performed.

26. The communication device according to claim 25, characterized in that, The communication device further includes a memory for storing the computer program or the instructions.

27. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions, and when the computer program or instructions are run, the method as described in any one of claims 1 to 12 is performed.

28. A computer program product, characterized in that, It includes a computer program or instructions that, when the computer program or instructions are executed, implement the method as described in any one of claims 1 to 12.

Citation Information

Patent Citations

  • Perception service implementation method and device, network side equipment and terminal

    CN116193500A

  • Communication awareness service processing method and device, equipment and storage medium

    CN117641390A

  • Measurement information sending method, measurement information receiving method and communication equipment

    CN117692921A

  • Communication method and device

    WO2024197569A1

  • Communication method, and device

    WO2024216558A1