Sensing service processing method and communication apparatus

By introducing perceptual control entities and perceptual processing entities into the communication system, which are responsible for the control surface and data surface functions of perceptual services, the problem of low efficiency in handling large amounts of perceptual services is solved, and efficient perceptual service processing and system security is achieved.

WO2025043425A1PCT designated stage expired Publication Date: 2025-03-06HUAWEI TECH CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2023/115116
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-08-26
Publication Date
2025-03-06

AI Technical Summary

Technical Problem

How to efficiently process large amounts of perceived business data and improve the processing efficiency of perceived business.

Method used

By introducing perceptual control entities and perceptual processing entities, they are responsible for the control surface and data surface functions of perceptual services, and realize the effective processing and management of perceptual service data.

Benefits of technology

It improves the processing efficiency of perceived services, enhances the flexibility and security of the system, and avoids the mutual influence between the data plane and the control plane.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2023115116_06032025_PF_FP_ABST
    Figure CN2023115116_06032025_PF_FP_ABST
Patent Text Reader

Abstract

A sensing service processing method and a communication apparatus, which can process a large amount of sensing service data when there is a large amount of sensing service data in a communication system, thereby facilitating an improvement in the processing efficiency of a sensing service. The method may comprise: acquiring a first sensing service identifier; determining a sensing entity pair associated with a sensing service identified by the sensing service identifier, wherein the sensing entity pair comprises a sending sensing entity and a receiving sensing entity; sending a first sensing control message to the sending sensing entity, so as to instruct the sending sensing entity to send a sensing signal of the sensing service; and sending a second sensing control message to the receiving sensing entity, so as to instruct the receiving sensing entity to receive the sensing signal of the sensing service. The method may further comprise sending a third sensing control message to a sensing processing entity, so as to instruct the sensing processing entity to process sensing data of the sensing service that comes from the receiving sensing entity.
Need to check novelty before this filing date? Find Prior Art

Description

Perception service processing method and communication device Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and in particular to a perception service processing method and a communication device. Background Art

[0002] Wireless communication and wireless sensing are both based on electromagnetic wave theory. At the transmitter, electromagnetic wave signals are modulated, carrying information about the source. However, as they propagate, electromagnetic wave signals are affected by the wireless environment, meaning they are modulated by the environment and thus carry environmental information. By analyzing the electromagnetic wave signals, the receiver can not only obtain the source information but also extract sensory information reflecting the characteristics of the propagation environment. This makes the integration of communication and sensing possible.

[0003] Communication systems are evolving toward higher frequency bands, greater bandwidths, and denser distribution of large-scale antenna arrays. This allows a single system to integrate both perception and communication capabilities, enabling mutual performance enhancements between systems. Perception, a fundamental characteristic of communication systems, can observe and sample both the physical and biological worlds, opening a new channel for the convergence of the physical and biological worlds with the digital world.

[0004] There may be a large amount of perception service data in the communication system. How to process the large amount of perception service data is a technical problem that needs to be solved urgently.

[0005] Summary of the Invention

[0006] The embodiments of the present application provide a perception service processing method and a communication device, which can process a large amount of perception service data, thereby helping to improve the processing efficiency of the perception service.

[0007] In a first aspect, an embodiment of the present application provides a perception service control method, which may include: obtaining a first perception service identifier; determining a first perception entity and a second perception entity associated with the first perception service, wherein the first perception service is determined based on the first perception service identifier; sending a first perception control message to the first perception entity, the first perception control message including first indication information, and the first indication information is used to indicate the first perception entity to send a first perception signal for the first perception service; sending a second perception control message to the second perception entity, the second perception control message including second indication information, and the second indication information is used to indicate the second perception entity to receive a second perception signal for the first perception service.

[0008] The above method provides a control method for perception services, which can determine the perception entity associated with the first perception service in a scenario where there are a large number of perception services in the communication system, and send a perception control message to it, so that the perception entity processes its corresponding perception service, which helps to improve the processing efficiency of the perception service.

[0009] Among them, the perception entity associated with the first perception service can be understood as a perception entity that provides the first perception service, or a perception entity that provides a perception signal of the first perception service, or a perception entity that provides perception data of the first perception service, etc.

[0010] In one possible implementation, the method provided in the first aspect can be performed by a perception control entity, or by a device compatible with the perception control entity, such as a processor, chip, or chip system. It can also be implemented by a logical node, logic module, or software that implements all or part of the perception control entity's functions. Having a dedicated perception control entity implement control-related operations for the perception service, separating them from the data processing of the perception service, can improve flexibility, reliability, and security.

[0011] In another possible implementation, the method provided in the first aspect can be executed by an access management entity, or by a device that matches the access management entity, such as a processor, chip or chip system, etc. It can also be implemented by a logical node, logical module or software that can implement all or part of the functions of the access management entity.

[0012] In one possible implementation, when the method provided in the first aspect is performed by a perception control entity, the perception control entity may further send a third perception control message to the perception processing entity, the third perception control message being used to instruct the perception processing entity to process perception data of a first perception service from a second perception entity. Having a dedicated perception processing entity process perception data for a perception service can separate the perception processing entity from modules that process other data, thereby helping to improve the processing efficiency of the perception service.

[0013] In one possible implementation, before determining the first perception entity and the second perception entity associated with the first perception service, perception capability information of the first perception entity is received so that the first perception entity can be determined as a sending perception entity and / or a receiving perception entity based on the perception capability information of the first perception entity.

[0014] For the method provided in the first aspect to be executed by a perception control entity, the perception control entity can receive the perception capability information directly from the first perception entity, or it can receive the perception capability information from the first perception entity through the access management entity, that is, the first perception entity sends its perception capability information to the access management entity, and the access management entity sends the perception capability information of the first perception entity to the perception control entity.

[0015] In the case where the method provided in the first aspect is performed by an access management entity, the access management entity receives sensing capability information from a first sensing entity. Optionally, the access management entity sends the sensing capability information of the first sensing entity to a sensing control entity, so that the sensing control entity determines, based on the sensing capability information, that the first sensing entity is a sending sensing entity and / or a receiving sensing entity.

[0016] In one possible implementation, before determining the first perception entity and the second perception entity associated with the first perception service, perception capability information of the second perception entity is received so that the second perception entity can be determined as a sending perception entity and / or a receiving perception entity based on the perception capability information of the second perception entity.

[0017] For the method provided in the first aspect to be executed by a perception control entity, the perception control entity can receive the perception capability information directly from the second perception entity, or it can receive the perception capability information from the second perception entity through the access management entity, that is, the second perception entity sends its perception capability information to the access management entity, and the access management entity sends the perception capability information of the second perception entity to the perception control entity.

[0018] In the case where the method provided in the first aspect is performed by an access management entity, the access management entity receives sensing capability information from the second sensing entity. Optionally, the access management entity sends the sensing capability information of the second sensing entity to the sensing control entity, so that the sensing control entity determines, based on the sensing capability information, that the second sensing entity is a sending sensing entity and / or a receiving sensing entity.

[0019] In one possible implementation, the above-mentioned perception capability information includes one or more of the following information: device identification, role identification, device type, geographic location information, perception processing capability, and supported perception service types. The device identification is used to uniquely identify the perception entity; the role identification is used to indicate whether the perception entity is a sending perception entity and / or a receiving perception entity; the device type is used to indicate whether the perception entity is one or more of the following: network equipment, user equipment, vehicle-mounted equipment, IoT equipment, etc.; the geographic location information is used to indicate the current geographic location of the perception entity; the perception processing capability is used to indicate which perception data the perception entity can process; and the supported perception service types are used to indicate the types of perception services that the perception entity can provide.

[0020] Among them, the perception processing capability includes one or more of the following capabilities: layer 1 perception capability, layer 2 perception capability, and layer 3 perception capability; among them, layer 1 perception capability is used to perceive raw data, layer 2 perception capability is used to perceive measurement data, and layer 3 perception capability is used to process perception data to obtain perception results; perception data includes raw data and / or measurement data.

[0021] In a possible implementation, the first sensing entity and the second sensing entity are the same, that is, the first sensing entity can serve as both a sending sensing entity and a receiving sensing entity. The first sensing entity and the second sensing entity can be the same network device or the same terminal device.

[0022] In one possible implementation, the first sensing entity is different from the second sensing entity. The first sensing entity and the second sensing entity may be different network devices or different terminal devices; or the first sensing entity may be a network device and the second sensing entity may be a terminal device; or the first sensing entity may be a terminal device and the second sensing entity may be a network device.

[0023] In one possible implementation, when the method provided in the first aspect is performed by a perception control entity, the perception control entity receives a subscription request message from a perception subscriber before receiving the perception service request message, generates a first perception service identifier based on the subscription request message, and sends a subscription response message to the perception subscriber, where the subscription response message includes the first perception service identifier. The perception control entity feeds back the generated perception service identifier to the perception subscriber, so that the perception subscriber requests the corresponding perception service from the perception control entity.

[0024] In one possible implementation, the subscription request message includes one or more of the following information: an identifier of the perception subscriber, subscription region information, the subscribed perception service type, and subscribed perception requirement information. The perception control entity can then generate a first perception service identifier based on the content carried in the subscription request message. The first perception service identifier is used to identify the first perception service, i.e., the perception service to which the perception subscriber requests subscription.

[0025] In one possible implementation, the first perception control message also includes one or more of the following information: a first perception service identifier, a perception service type of the first perception service, and perception requirement information of the first perception service; the second perception control message also includes one or more of the following information: a first perception service identifier, a perception service type of the first perception service, and perception requirement information of the first perception service.

[0026] The first perception service identifier is used by the perception entity to know which perception service's perception signal is to be sent and / or received.

[0027] The perception requirement information may include but is not limited to one or more of distance accuracy, resolution, recognition accuracy, false alarm rate, positioning accuracy, delay, etc., so that the perception entity sends and / or receives a perception signal that meets the perception requirement information.

[0028] In one possible implementation, a first sensing entity and a second sensing entity are associated with a first subtask of processing a first sensing service; the first subtask is any subtask of at least one subtask of processing the first sensing service. That is, processing the first sensing service can be achieved by processing at least one subtask, each of which can be processed by a pair of sensing entities (e.g., a first sensing entity and a second sensing entity), and a pair of sensing entities can process one or more subtasks. Processing the first sensing service by at least one pair of sensing entities can improve the processing efficiency of the sensing service.

[0029] In one possible implementation, the first perception control message also includes a first subtask identifier, so that the first perception entity knows which subtask in the first perception service is to be processed, and the first perception entity can then send a perception signal for the subtask. The second perception control message also includes the first subtask identifier, so that the second perception entity knows which subtask in the first perception service is to be processed, and the first perception entity can then receive a perception signal for the subtask. The third perception control message is further used to indicate the identifier of at least one of the above-mentioned subtasks, so that the perception processing entity processes the perception data of the at least one subtask to obtain a perception result for the first perception service.

[0030] In a second aspect, an embodiment of the present application provides a method for processing a perception service, which may include: receiving a third perception control message from a perception control entity, the third perception control message being used to indicate processing of perception data of a first perception service; receiving the perception data of the first perception service, and obtaining a perception result of the first perception service based on the perception data of the first perception service; and sending the perception result of the first perception service.

[0031] The method provided in the second aspect can be executed by a perception processing entity, or by a device that matches the perception processing entity, such as a processor, chip or chip system, etc. It can also be implemented by a logical node, logical module or software that can realize all or part of the functions of the perception processing entity.

[0032] As can be seen, upon receiving the third perception control message, the perception processing entity can process the received perception data of the first perception service to obtain a perception result for the first perception service. Having a dedicated perception processing entity process the perception data of the perception service can separate the perception processing entity from modules that process other data, thereby helping to improve the processing efficiency and flexibility of the perception service, as well as separating the perception processing entity from the control entity of the perception service, thereby improving reliability and security.

[0033] In a possible implementation, when sending the perception result of the first perception service, the perception result of the first perception service may be sent to the perception subscription terminal of the first perception service through the network open module so that the perception result of the first perception service can be transmitted to the perception subscription terminal.

[0034] In one possible implementation, when receiving perception data for a first perception service, the perception data for the first perception service may be received via a perception data bearer. The perception data bearer is a channel established by a perception entity for transmitting perception data. The perception data bearer may support a logical data transmission channel for data in-path processing and forwarding.

[0035] In a third aspect, an embodiment of the present application provides a method for processing a perception service, which may include: receiving a first perception control message and / or a second perception control message; the first perception control message is used to indicate the sending of a first perception signal for a first perception service; the second perception control message is used to indicate the receiving of a second perception signal for the first perception service; based on the first perception control message, sending the first perception signal; and / or, based on the second perception control message, receiving the second perception signal.

[0036] The method provided in the third aspect can be performed by a sensing entity, or by a device compatible with the sensing entity, such as a processor, chip, or chip system. It can also be implemented by a logical node, logic module, or software that implements all or part of the functions of the sensing entity. The first sensing entity can be understood as a sending sensing entity, and the second sensing entity can be understood as a receiving sensing entity.

[0037] As can be seen, the sensing entity can send a first sensing signal for a first sensing service based on the first sensing control message, and can receive a second sensing signal for the first sensing service based on the second sensing control message. Therefore, in scenarios where a large number of sensing services exist in the communication system, each sensing entity can process its own corresponding sensing service data, which helps improve the processing efficiency of sensing services.

[0038] In one possible implementation, before receiving the first perception control message and / or the second perception control message, the perception entity may further send perception capability information. Optionally, the perception entity sends the perception capability information to the access management entity and / or the perception control entity, so that the access management entity and / or the perception control entity determines, based on the perception capability information, that the perception entity is a sending perception entity and / or a receiving perception entity for a certain perception service.

[0039] In one possible implementation, the above-mentioned perception capability information includes one or more of the following information: device identification, role identification, device type, geographic location information, perception processing capability, and supported perception service types. The device identification is used to uniquely identify the perception entity; the role identification is used to indicate whether the perception entity is a sending perception entity and / or a receiving perception entity; the device type is used to indicate whether the perception entity is one or more of the following: network equipment, user equipment, vehicle-mounted equipment, IoT equipment, etc.; the geographic location information is used to indicate the current geographic location of the perception entity; the perception processing capability is used to indicate which perception data the perception entity can process; and the supported perception service types are used to indicate the types of perception services that the perception entity can provide.

[0040] Among them, the perception processing capability includes one or more of the following capabilities: layer 1 perception capability, layer 2 perception capability, and layer 3 perception capability; among them, layer 1 perception capability is used to perceive raw data, layer 2 perception capability is used to perceive measurement data, and layer 3 perception capability is used to process perception data to obtain perception results; perception data includes raw data and / or measurement data.

[0041] In one possible implementation, the first perception control message is also used to indicate one or more of the following information: the first perception service identifier, the perception service type of the first perception service; and / or, the second perception control message is also used to indicate one or more of the following information: the first perception service identifier, the perception service type of the first perception service.

[0042] In one possible implementation, the first perception control message further indicates a first subtask identifier; and / or the second perception control message further indicates a first subtask identifier. The first subtask identifier identifies a first subtask, which is any of at least one subtask that processes the first perception service. In other words, the first perception entity and / or the second perception entity is configured to process the first subtask of the first perception service.

[0043] In a fourth aspect, an embodiment of the present application provides a communication device, which may be a perception control entity, or a device in a perception control entity, or a device that can be used in conjunction with a perception control entity. Alternatively, the communication device may be an access management entity, or a device in an access management entity, or a device that can be used in conjunction with an access management entity. The communication device may also be a chip system. The communication device may execute the method described in the first aspect. The functions of the communication device may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions. The unit or module may be software and / or hardware. The operations and beneficial effects performed by the communication device may refer to the method and beneficial effects described in the first aspect above.

[0044] In a fifth aspect, the present application provides a communication device, which may be a perception processing entity, or a device in a perception processing entity, or a device that can be used in conjunction with a perception processing entity. The communication device may also be a chip system. The communication device may execute the method described in the second aspect. The functions of the communication device may be implemented by hardware, or by hardware executing corresponding software implementations. The hardware or software includes one or more units or modules corresponding to the above functions. The unit or module may be software and / or hardware. The operations and beneficial effects performed by the communication device may refer to the method and beneficial effects described in the second aspect above.

[0045] In a sixth aspect, the present application provides a communication device, which may be a perception entity, a device in a perception entity, or a device that can be used in conjunction with a perception entity. The communication device may also be a chip system. The communication device may execute the method described in the third aspect. The functions of the communication device may be implemented by hardware, or by hardware executing corresponding software implementations. The hardware or software includes one or more units or modules corresponding to the above functions. The unit or module may be software and / or hardware. The operations and beneficial effects performed by the communication device may refer to the method and beneficial effects described in the third aspect above.

[0046] In a seventh aspect, the present application provides a communication device, comprising a processor, wherein the processor is configured to execute the method described in the first aspect, the method described in the second aspect, or the method described in the third aspect.

[0047] In an eighth aspect, the present application provides a communication device, comprising a processor coupled to a memory, wherein the memory stores instructions, and when the instructions are executed by the processor, the communication device executes the method as described in the first aspect, or the method as described in the second aspect, or the method as described in the third aspect.

[0048] In one possible implementation, the communication device further includes a memory. Optionally, the processor and the memory are integrated together. Optionally, the memory and the processor are independently provided.

[0049] In the ninth aspect, the present application provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor is used to implement the method as described in the first aspect, the method as described in the second aspect, or the method as described in the third aspect through logic circuits or executing computer instructions.

[0050] In the tenth aspect, the present application provides a computer-readable storage medium, which stores instructions. When the computer program or instructions are executed by a communication device, it implements the method described in the first aspect, the method described in the second aspect, or the method described in the third aspect.

[0051] In an eleventh aspect, the present application provides a computer program product comprising instructions, which, when a communication device reads and executes the instructions, causes the communication device to execute the method as described in the first aspect, or the method as described in the second aspect, or the method as described in the third aspect.

[0052] In the twelfth aspect, the present application provides a communication system, including a perception control entity and a perception processing entity; the perception entity is used to execute the method in the first aspect and its various possible implementations, and the perception processing entity is used to execute the method in the second aspect and its various possible implementations.

[0053] In a possible implementation, the communication system further includes a perception entity, which is configured to execute the method in the third aspect and various possible implementations thereof.

[0054] In a thirteenth aspect, the present application provides a communication system, including a perception control entity and a perception processing entity; the perception control entity is configured to obtain a first perception service identifier; determine a first perception entity and a second perception entity associated with the first perception service, where the first perception service is determined based on the first perception service identifier; send a first perception control message to the first perception entity, the first perception control message including first indication information, the first indication information being used to instruct the first perception entity to send a first perception signal for the first perception service; send a second perception control message to the second perception entity, the second perception control message including second indication information, the second indication information being used to instruct the second perception entity to receive a second perception signal for the first perception service; send a third perception control message to the perception processing entity, the third perception control message being used to instruct the perception processing entity to process perception data for the first perception service from the second perception entity;

[0055] The perception processing entity is used to receive perception data of the first perception service, obtain a perception result of the first perception service based on the perception data of the first perception service, and send the perception result of the first perception service.

[0056] In a possible implementation, the communication system further includes a first perception entity and a second perception entity; the first perception entity is configured to send a first perception signal based on a first perception control message; and the second perception entity is configured to receive a second perception signal based on a second perception control message.

[0057] In a possible implementation, the first sensing entity is further configured to send sensing capability information of the first sensing entity; and the second sensing entity is further configured to send sensing capability information of the second sensing entity.

[0058] In a fourteenth aspect, the present application provides a communication system, including an access management entity, a perception control entity, and a perception processing entity;

[0059] A perception control entity is configured to obtain a first perception service identifier and send a perception service request message to an access management entity; and send a third perception control message to a perception processing entity, where the third perception control message is used to instruct the perception processing entity to process perception data of the first perception service from the second perception entity.

[0060] An access management entity is configured to determine a first perception entity and a second perception entity associated with a first perception service, where the first perception service is determined based on a first perception service identifier; send a first perception control message to the first perception entity, where the first perception control message includes first indication information, where the first indication information is used to instruct the first perception entity to send a first perception signal for the first perception service; and send a second perception control message to the second perception entity, where the second perception control message includes second indication information, where the second indication information is used to instruct the second perception entity to receive a second perception signal for the first perception service.

[0061] The perception processing entity is used to receive perception data of the first perception service, obtain a perception result of the first perception service based on the perception data of the first perception service, and send the perception result of the first perception service.

[0062] In a possible implementation, the communication system further includes a first sensing entity and a second sensing entity;

[0063] A first perception entity, configured to send a first perception signal based on a first perception control message;

[0064] The second perception entity is configured to receive a second perception signal based on the second perception control message.

[0065] In a possible implementation, the first sensing entity is further configured to send sensing capability information of the first sensing entity; and the second sensing entity is further configured to send sensing capability information of the second sensing entity. BRIEF DESCRIPTION OF THE DRAWINGS

[0066] Figure 1 is an example diagram of six perception scenarios;

[0067] FIG2 is an example diagram of several networking architectures provided in an embodiment of the present application;

[0068] FIG3 is a schematic diagram of a process for registering sensing capability information provided in an embodiment of the present application;

[0069] FIG4 is another schematic diagram of a process for registering sensing capability information provided by an embodiment of the present application;

[0070] FIG5 is a schematic diagram of a process of subscription to a perception service provided in an embodiment of the present application;

[0071] FIG6 is a flow chart of a method for processing a perception service according to an embodiment of the present application;

[0072] FIG7 is a flow chart of another method for processing a perception service according to an embodiment of the present application;

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

[0074] FIG9 is a schematic structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0075] In this application, words such as "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit differences. "And / or" describes the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the related objects are in an "or" relationship.

[0076] It should be understood that, in this application, "at least one" refers to one or more, and "a plurality" refers to two or more. Furthermore, in this application, "equal to" can be used in conjunction with "greater than" or "less than." When "equal to" and "greater than" are used together, the technical solution of "greater than" is adopted; when "equal to" and "less than" are used together, the technical solution of "less than" is adopted.

[0077] In this application, "sending information to... (e.g., a terminal device)" can be understood as the destination of the information being the terminal device. This can include sending information to the terminal device directly or indirectly. "Receiving information from... (e.g., a terminal device)" or "receiving information from... (e.g., a terminal device)" can be understood as the source of the information being the terminal device, which can include receiving information from the terminal device directly or indirectly. The information may be processed as necessary between the source and destination of the information, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be understood similarly and will not be elaborated on here.

[0078] First, the relevant names or terms involved in this application are explained to facilitate understanding by those skilled in the art.

[0079] 1. Perception

[0080] 1. Definition of Perception

[0081] Wireless sensing uses wireless signals for sensing. Perception is the process of collecting, processing, and generating sensing results from collected data. For example, collected data can be used to determine the distance, shape, and type of surrounding obstacles, or to determine the breathing rate and heart rate of the monitored subject. The collected data can be collected by sensors or wireless signals.

[0082] Both wireless sensing and wireless communications are based on electromagnetic wave theory. At the transmitter, electromagnetic wave signals are modulated, allowing them to carry information about the source. During propagation, electromagnetic wave signals are affected by the wireless environment, meaning they can also carry environmental information. By analyzing the electromagnetic wave signals, the receiver can not only obtain the source information but also extract sensory information reflecting the characteristics of the propagation environment. In other words, electromagnetic wave signals inherently possess both communication and perception capabilities, making integrated sensing and communication (ISAC) possible. This is also known as joint communications and sensing (JCAS), or simply as integrated synaesthesia. Compared to systems that separate sensing and communication, ISAC offers a range of advantages, including cost savings, reduced device size, lower power consumption, improved frequency efficiency, and reduced interference between communication and sensing.

[0083] 2. Perception Scene

[0084] Perception scenarios can be divided into perception scenarios based on network devices, perception scenarios based on network devices and terminal devices, and perception scenarios based on terminal devices. For example, see the perception scenarios shown in (1) to (6) of Figure 1.

[0085] The perception scenario shown in (1) of Figure 1 is based on a network device, which acts as both the transmitter and receiver of the perception signal. For example, perception signal 1 sent by the network device reaches a target object (e.g., a car). After being reflected by the target object, the network device receives perception signal 2, which it then processes to obtain a perception result.

[0086] The perception scenario shown in (2) of Figure 1 is also a network device-based perception scenario, with one network device acting as the transmitter of the perception signal and the other as the receiver. For example, perception signal 1 sent by network device A reaches the target object. After being reflected by the target object, network device B can receive perception signal 2. Network device B can then process perception signal 2 to obtain the perception result.

[0087] The perception scenario shown in (3) of Figure 1 is based on a network device and a terminal device. The network device acts as the transmitter of the perception signal, and the terminal device acts as the receiver of the perception signal. For example, perception signal 1 sent by the network device reaches the target object. After being reflected by the target object, perception signal 1 is received by the terminal device. The terminal device then processes perception signal 2 to obtain a perception result.

[0088] The perception scenario shown in (4) of Figure 1 is also a perception scenario based on network devices and terminal devices. The terminal device acts as the transmitter of the perception signal, and the network device acts as the receiver of the perception signal. For example, perception signal 1 sent by the terminal device reaches the target object. After being reflected by the target object, perception signal 1 can be received by the network device. The network device can then process perception signal 2 to obtain the perception result.

[0089] The perception scenario shown in (5) of Figure 1 is based on a terminal device, which acts as both the transmitter and receiver of the perception signal. For example, perception signal 1 sent by the terminal device reaches the target object. After being reflected by the target object, perception signal 1 is received by the terminal device as perception signal 2, which is then processed to obtain a perception result.

[0090] The perception scenario shown in (6) of Figure 1 is also a perception scenario based on terminal devices, with one terminal device acting as the transmitter of the perception signal and the other terminal device acting as the receiver of the perception signal. For example, perception signal 1 sent by terminal device a reaches the target object. After being reflected by the target object, perception signal 1 can be received by terminal device b, which can then process perception signal 2 to obtain the perception result.

[0091] The above-mentioned perception signal 2 can be understood as a reflection signal of the above-mentioned perception signal 1. The perception signal 2 carries more information than the information carried by the perception signal 1. For example, the perception signal 2 can carry source information and environmental information.

[0092] 3. Sensing Entity (SE)

[0093] The sensing entity may send and / or receive sensing signals, and may also send sensing capabilities to the sensing control entity or access management entity. In an embodiment of the present application, the sensing capabilities may include one or more of the following capabilities:

[0094] 1) Layer 1 (L1) sensing capability, used to sense raw data. Raw data refers to basic information about the sensed signal, such as amplitude, phase, and whether the sensed signal is an I-path signal or a Q-path signal.

[0095] 2) Layer 2 (L2) perception capability, used to perceive measurement data. Measurement data refers to data obtained by processing raw data and used to represent the measurement dimension. It may include but is not limited to one or more of the following information: sampling point delay, reception angle of the perception signal, signal strength of the perception signal, Doppler (i.e., frequency offset of the perception signal), location of the target object, and speed of the target object. Sampling points refer to signal values ​​at specific moments or locations selected during the discretization of continuous signals during signal processing.

[0096] 3) Layer 3 (L3) perception capability, which is used to process perception data to obtain perception results. The perception data can be raw data and / or measurement data. The perception results can include but are not limited to one or more of the following information: the distance between the perception entity and the target object, the speed of the target object, the position of the target object, the angle between the perception entity and the target object, the movement path of the target object, the breathing rate of the target object, the heartbeat of the target object, etc.

[0097] A perception entity is a logical entity, also known as a logical perception entity. A perception entity can be deployed on network devices or terminal devices. In other words, any network device or terminal device with perception capabilities can serve as a perception entity. A network device or terminal device may possess the three capabilities described above, or it may possess one or more of these capabilities. For example, some terminal devices with less computing power may possess L1 perception capabilities but not L2 or L3 perception capabilities. Another example is that some network devices possess all three capabilities described above. A perception entity can also be deployed independently.

[0098] 2. Terminal Equipment

[0099] Terminal devices can also be called user equipment (UE), mobile station (MS), mobile terminal (MT), etc. They are devices used to provide voice or data connectivity to users, or they can be IoT devices. For example, terminal devices include handheld devices with wireless connectivity, in-vehicle devices, etc. Currently, terminal devices can include: mobile phones, tablet computers, laptop computers, PDAs, mobile internet devices (MIDs), wearable devices (such as smart watches, smart bracelets, pedometers, etc.), vehicle-mounted devices (such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), satellite terminals, virtual reality (VR) devices, augmented reality (AR) devices, smart point-of-sale (POS) machines, customer-premises equipment (CPE), wireless terminals in industrial control, smart home devices (such as refrigerators, televisions, air conditioners, electricity meters, etc.), intelligent robots, robotic arms, workshop equipment, wireless terminals in unmanned driving, wireless terminals in telemedicine, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, and flying devices (such as intelligent robots, hot air balloons, drones, airplanes). Terminal devices can also be other devices with terminal functions, for example, terminal devices can also be devices that function as terminals in D2D communication.

[0100] 3. Network Equipment

[0101] A network device is a node in a radio access network (RAN), and can also be referred to as an access network device or a RAN node (or device). A network device is used to help terminal devices achieve wireless access. In one possible scenario, a network device can be a base station, an evolved NodeB (eNodeB), a transmitting and receiving point (TRP), a transmitting point (TP), a next-generation NodeB (gNB), a next-generation base station in a 6G system, a base station in a future mobile communication system, a satellite, an integrated access and backhaul (IAB) node, a mobile switching center, or an access network device in a non-terrestrial network (NTN) communication system, that is, it can be deployed on a high-altitude platform or satellite. A network device can be a macro base station, a micro base station or an indoor station, a relay node or a donor node, or a wireless controller in a cloud radio access network (CRAN) scenario. A network device can also be a device that acts as a base station in device-to-device (D2D) communication, Internet of Vehicles (IoV) communication, drone communication, or machine communication. Alternatively, a network device can be a server, wearable device, vehicle, or vehicle-mounted device. For example, a network device in vehicle-to-everything (V2X) technology can be a roadside unit (RSU).

[0102] All or part of the functions of the network device in this application may also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform). The network device in this application may also be a logical node, logical module, or software that can implement all or part of the network device functions.

[0103] In another possible scenario, multiple network devices collaborate to assist the terminal in achieving wireless access, and different network devices respectively implement part of the functions of the base station. For example, the network device can be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU can be set separately, or can also be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or a radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH). It can be understood that the network device can be a CU node, a DU node, or a device including a CU node and a DU node. In addition, the CU can be divided into a network device in the access network RAN, or the CU can be divided into a network device in the core network CN, which is not limited here.

[0104] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in an open access network (open RAN, O-RAN or ORAN) system, CU may also be called O-CU (open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. For the convenience of description, this application takes CU, CU-CP, CU-UP, DU and RU as examples for description. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0105] With the rapid development of communication technology and perception technology, more and more perception service data is being generated. How to process a large amount of perception service data is a technical problem that needs to be solved urgently. In one implementation, in order to enable the 5G system to support ISAC, the introduction of a sensing function (SF) entity into the 5G core network architecture is considered. However, the position of the SF entity in the 5G core network architecture and the connection relationship between the SF entity and other core network entities are not clearly defined, nor is the end-to-end signaling process defined. In this implementation, perception-related control signaling and service data are all processed by one entity, sharing the transmission bandwidth, resulting in poor security and inconvenient upgrades and expansions.

[0106] In view of this, an embodiment of the present application provides a perception service processing method and a communication device, which introduce two core network functional modules to process a large amount of perception service data, thereby helping to improve the processing efficiency of the perception service. Among the two core network functional modules, one core network functional module is used to implement the control plane function of the perception service, such as receiving the perception capability information of the perception entity and orchestrating the perception service based on the perception capability information of the perception entity; the other core network functional module is used to implement the data plane function of the perception service, such as processing the perception data of the perception service to obtain the perception result of the perception service. After the control plane function of the perception service and the data plane function of the perception service are deployed independently, the number of control plane functional entities and data plane functional entities can be flexibly configured and adjusted according to resources and business conditions; secondly, attacks on the data plane will not affect the control plane, and vice versa, thereby improving the reliability and security of the perception service.

[0107] The orchestration of the sensing service may include selecting a transmitting sensing entity and a receiving sensing entity. The transmitting sensing entity and the receiving sensing entity may be the same sensing entity. The transmitting sensing entity is a transmitter of a sensing signal and is configured to send the sensing signal. The receiving sensing entity is a receiver of the sensing signal and is configured to receive the sensing signal.

[0108] The processing of the perception data may include processing the raw data to obtain measurement data, and / or processing the measurement data to obtain a perception result. The measurement data may be obtained by processing the raw data or by perception by a perception entity.

[0109] In the embodiments of the present application, the core network function module for receiving perception capability information and orchestrating perception services may be referred to as a perception control entity, and the core network function module for processing perception data to obtain perception results may be referred to as a perception processing entity. The names of perception control entity and perception processing entity are used for example and do not constitute a limitation on the embodiments of the present application. With the development of communication technology and perception technology, these two modules may adopt other names. For example, the perception control entity may also be described as a sensing service control function (SSCF), or a perception service control network element, or a perception control network element, etc.; the perception processing entity may also be described as a sensing data process function (SDPF), or a perception data processing network element, or a perception processing network element, etc. For the convenience of description, the perception control entity is described as an SSCF and the perception processing entity is described as an SDPF in the following embodiments.

[0110] The embodiment of the present application takes the introduction of SSCF and SDPF into the core network architecture of the 5G system as an example to achieve better compatibility with the 5G system so that it can smoothly evolve to the 6G system. The SSCF can communicate with other core network functional modules by mounting it on the SBI bus through the service-based inferface (SBI); the SDPF can communicate with other core network functional modules by mounting it on the SBI bus through the SBI, or through a separate interface, such as communicating with other SDPFs through a separate interface, or communicating with the SSCF through a separate interface.

[0111] For example, the network architecture after the introduction of SSCF and SDPF can be seen from (1) to (8) in FIG2 .

[0112] In the networking architecture shown in (1) of Figure 2, the RAN connects to the SSCF via the access and mobility management function (AMF), and the RAN connects to the SDPF via the user plane function (UPF). The SDPF is mounted on the SBI bus via the SBI, and the SSCF is mounted on the SBI bus via the SBI. Therefore, the RAN can communicate with the SSCF on the control plane via the AMF, and the RAN can communicate with the SDPF on the data plane via the UPF.

[0113] In the networking architecture shown in (2) of Figure 2, the RAN is directly connected to the SSCF, which is connected to the SDPF via the UPF. The SDPF is mounted on the SBI bus via the SBI interface, while the SSCF is not mounted on the SBI bus. Therefore, the RAN can directly communicate with the SSCF on the control plane, and the RAN can communicate with the SDPF on the data plane via the UPF.

[0114] In the networking architecture shown in (3) of Figure 2, the RAN connects to the SSCF via the AMF, and the RAN connects to the SDPF via the UPF. The SDPF is not mounted on the SBI bus, and the SSCF is mounted on the SBI bus via the SBI. Therefore, the RAN can communicate with the SSCF on the control plane via the AMF, and the RAN can communicate with the SDPF on the data plane via the UPF.

[0115] In the networking architecture shown in (4) of Figure 2, the RAN is directly connected to the SSCF, and the RAN is connected to the SDPF through the UPF. The SDPF is not mounted on the SBI bus, and the SSCF is not mounted on the SBI bus. Therefore, the RAN can directly communicate with the SSCF on the control plane, and the RAN can communicate with the SDPF on the data plane through the UPF.

[0116] In the networking architecture shown in (5) of Figure 2, the RAN connects to the SSCF via the AMF, and the RAN directly connects to the SDPF. The SDPF is mounted on the SBI bus via the SBI, and the SSCF is mounted on the SBI bus via the SBI. Therefore, the RAN can communicate with the SSCF on the control plane via the AMF, and the RAN can communicate directly with the SDPF on the data plane.

[0117] In the networking architecture shown in (6) of Figure 2, the RAN is directly connected to the SSCF and the SDPF. The SDPF is mounted on the SBI bus via the SBI, while the SSCF is not mounted on the SBI bus. Therefore, the RAN can directly communicate with the SSCF on the control plane, and the RAN can directly communicate with the SDPF on the data plane.

[0118] In the networking architecture shown in (7) of Figure 2, the RAN connects to the SSCF via the AMF. The RAN connects directly to the SDPF. The SDPF is not mounted on the SBI bus, and the SSCF is mounted on the SBI bus via the SBI. Therefore, the RAN can communicate with the SSCF on the control plane via the AMF, and the RAN can communicate directly with the SDPF on the data plane.

[0119] In the networking architecture shown in (8) of Figure 2, the RAN is directly connected to the SSCF, and the RAN is directly connected to the SDPF. The SDPF is not mounted on the SBI bus, and the SSCF is not mounted on the SBI bus. Therefore, the RAN can directly communicate with the SSCF on the control plane, and the RAN can directly communicate with the SDPF on the data plane.

[0120] As shown in Figure 2, 1) the RAN can communicate with the SSCF directly on the control plane, or through the AMF; 2) the SDPF can be mounted on the SBI bus or not; 3) the RAN can communicate with the SDPF directly on the data plane, or through the UPF. Control plane communication refers to the transmission of control plane messages, such as the control messages in the embodiments of this application; data plane communication refers to the transmission of sensing data and / or sensing results.

[0121] The subscript L1 of the RAN in Figure 2 indicates that the RAN has L1 perception capabilities. Therefore, the RAN can send perception signals to target objects (such as the bicycle and car in the figure) and perceive the original data through the perception signals reflected by the target objects. Figure 2 uses the RAN with L1 perception capabilities as an example. In actual applications, the RAN may also have L2 perception capabilities, or may have both L2 and L3 perception capabilities. In actual applications, the UE may also have perception capabilities, for example, at least one of L1, L2, and L3 perception capabilities.

[0122] The dashed line between the SDPF and the network exposure function (NEF) in Figure 2 indicates that the SDPF and NEF can communicate or not. If the SDPF is not attached to the SBI bus, the SDPF can communicate with the NEF via this dashed line. Arrows pointing from an SDPF to itself in Figure 2 indicate that SDPFs can communicate with each other, for example, to transmit sensing data and / or sensing results.

[0123] In the embodiments of the present application, AMF is referred to as an access management entity and NEF is referred to as a network open entity. For ease of description, the following embodiments are described using AMF and NEF as examples.

[0124] Based on the networking architecture shown in Figure 2, SSCF and SDPF can be upgraded and maintained independently without affecting each other, so that the network can flexibly deploy and manage core network functional entities. Figure 2 takes one SSCF and one SDPF as an example, which does not constitute a limitation on the embodiments of the present application. For example, the number of SDPFs can be increased or decreased according to actual needs, and even if the number of SDPFs is reduced, it will not affect the SSCF. This makes the network easier to expand or streamline. By introducing SSCF and SDPF, the control plane and data plane of the perception service can be separated, so that attackers cannot attack the control plane entity (i.e., SSCF) through the data plane entity (i.e., SDPF), which helps to improve the security of the network. In addition, the control plane and data plane of the perception service are separated, so that the control plane entity can respond to the request of the data plane entity more quickly, thereby reducing network latency and helping to improve network response speed.

[0125] The embodiments of the present application can be applied to communication systems evolved after 5G, such as 5G systems and 6G systems, satellite communications, and short-range wireless communication systems. Among them, the wireless communication systems mentioned in the embodiments of the present application include but are not limited to: the three major application scenarios of 5G / 6G systems: enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC) and massive machine-type communications (mMTC), long range LoRa systems or vehicle networking systems. The embodiments of the present application can also be applied to ORAN systems, CRAN systems, etc.

[0126] The following is a detailed description of the perception service processing method provided in the embodiment of the present application based on the networking architecture shown in FIG2 .

[0127] Please refer to FIG3 , which is a schematic diagram of a process for registering sensory capability information according to an embodiment of the present application. The registration process may include but is not limited to the following steps:

[0128] 301: A first sensing entity sends sensing capability information of the first sensing entity to an SSCF. Correspondingly, the SSCF receives the sensing capability information of the first sensing entity from the first sensing entity.

[0129] 302: The second sensing entity sends sensing capability information of the second sensing entity to the SSCF. Correspondingly, the SSCF receives the sensing capability information of the second sensing entity from the second sensing entity.

[0130] The first perception entity is the same as or different from the second perception entity. The first perception entity is the same as the second perception entity, which means that the first perception entity can serve as both a sending perception entity and a receiving perception entity. For the same, the first perception entity and the second perception entity can be the same network device or the same terminal device. Optionally, the network device or the terminal device can send a perception capability information to the SSCF, which is beneficial to saving air interface resources and signaling overhead. For the different, the first perception entity and the second perception entity can be different network devices, or different terminal devices; or, the first perception entity can be a network device and the second perception entity can be a terminal device; or, the first perception entity can be a terminal device and the second perception entity can be a network device; or, the first perception entity and the second perception entity can be different network devices; or, the first perception entity and the second perception entity can be different terminal devices. Then, the first perception entity and the second perception entity respectively send perception capability information to the SSCF.

[0131] The above-mentioned perception capability information includes one or more of the following information: device identification, role identification, device type, geographic location information, perception processing capability, and supported perception service types.

[0132] Among them, the device identifier is used to uniquely identify the perception entity. For example, if the first perception entity is a terminal device, the device identifier can be an international mobile equipment identity (IMEI), a user permanent identifier (SUPI), a user hidden identifier (SUCI), a media access control (MAC) address, etc. For another example, if the first perception entity is a network device, the device identifier can be a cell identifier and / or a tracking area identity (TAI), etc., and the cell identifier can be, for example, a physical cell identifier (PCI).

[0133] The role identifier is used to indicate that the sensing entity is a sending sensing entity and / or a receiving sensing entity.

[0134] The device type is used to indicate whether the sensing entity is a network device or a terminal device. Optionally, if it is a network device, the device type can also indicate whether the network device is a base station, CU, or DU. If it is a terminal device, the device type can also indicate whether the terminal device is a UE, IoT device, flight device, or VR device.

[0135] The geographic location information may be used to indicate one or more of the following: the current geographic location of the sensing entity, the geographic location range that the sensing entity can sense, and the geographic location, such as latitude and longitude information, global positioning system (GPS) location information, etc.

[0136] The perception processing capability indicates that the perception entity has one or more of the following: L1 perception processing capability, L2 perception processing capability, and L3 perception processing capability. The three perception capabilities are described in detail in "3. Perception Entity" above and will not be repeated here.

[0137] The supported perception service types are used to indicate the types of perception services that the perception entity can provide, and may include but are not limited to one or more of the following types: environment type, monitoring type, imaging type, positioning type, etc. The environment type may include but are not limited to one or more of the following: ambient temperature, ambient humidity, air quality, weather conditions, crowd density, traffic density, air pressure, etc. The monitoring type may include but are not limited to one or more of the following: mobile monitoring, intrusion monitoring, fall monitoring, health monitoring, etc. Mobile monitoring may include but are not limited to one or more of the following: distance monitoring, location monitoring, mobile speed monitoring, mobile path monitoring, etc. Health monitoring may include but are not limited to one or more of the following: respiratory rate, heartbeat, etc. The imaging type may include but are not limited to one or more of the following: medical imaging, 3D map imaging, 3D map construction, building imaging, body temperature imaging, etc.

[0138] In one implementation, the sensing capability information includes one or more of the following information elements:

[0139] 1) NodeID, this information element is used to indicate the device identification;

[0140] 2) role_list, this information element is used to indicate whether the sensing entity is a sending sensing entity and / or a receiving sensing entity;

[0141] 3) Node_type, this information element is used to indicate whether the sensing entity is a base station, CU, DU, UE, IoT device, flight device, or VR device;

[0142] 4) Location: This information element is used to indicate the current geographical location of the sensing entity.

[0143] 5) Capability_indicator, which is used to indicate that the sensing entity has one or more of L1 sensing processing capability, L2 sensing processing capability, and L3 sensing processing capability;

[0144] 6) service_type: This information element is used to indicate the perception information of the perception service that can be provided by the perception entity.

[0145] Figure 3 uses two sensing entities sending sensing capability information to the SSCF as an example. In actual applications, multiple sensing entities may send sensing capability information to the SSCF. Multiple sensing entities may send sensing capability information simultaneously or at different times. Optionally, a sensing entity may send sensing capability information to the SSCF when it is powered on or restarted.

[0146] Optionally, when the SSCF receives the sensing capability information, it may store the sensing capability information of the sensing entity and store the corresponding relationship between each sensing entity and the sensing capability information.

[0147] The perception capability information sent by the perception entity to the SSCF for the first time may be carried in the registration message, that is, the perception entity registers the perception capability information with the SSCF. If one or more of the above-mentioned perception capability information changes, the perception entity sends updated perception capability information to the SSCF, and the updated perception capability information may be carried in the update message. The updated perception capability information may include the changed information or the changed items, or may include all items of information. For example, after the geographical location of the perception entity moves from location A to location B, the updated perception capability information includes the geographical location information of location B. Upon receiving the updated perception capability information, the SSCF updates the previously stored perception capability information, so that the perception capability information is real-time.

[0148] In the embodiment shown in FIG3 , the sensing entity sends sensing capability information to the SSCF, so that the SSCF can determine whether the sensing entity is a sending sensing entity and / or a receiving sensing entity based on the sensing capability information.

[0149] Please refer to FIG4 , which is another flowchart of registering sensing capability information provided by an embodiment of the present application. The registration process may include but is not limited to the following steps:

[0150] 401: A first sensing entity sends sensing capability information of the first sensing entity to an AMF. Correspondingly, the AMF receives the sensing capability information of the first sensing entity from the first sensing entity.

[0151] 402. The AMF sends the sensing capability information of the first sensing entity to the SSCF. Correspondingly, the SSCF receives the sensing capability information of the first sensing entity from the AMF.

[0152] 403. The second sensing entity sends the sensing capability information of the second sensing entity to the AMF. Correspondingly, the AMF receives the sensing capability information of the second sensing entity from the second sensing entity.

[0153] 404. The AMF sends the sensing capability information of the second sensing entity to the SSCF. Correspondingly, the SSCF receives the sensing capability information of the second sensing entity from the AMF.

[0154] The difference between the embodiment shown in Figure 4 and the embodiment shown in Figure 3 is that in the embodiment shown in Figure 3, the perception entity sends the perception capability information directly to the SSCF, while in the embodiment shown in Figure 4, the perception entity sends the perception capability information to the SSCF through the AMF.

[0155] The perception capability information sent by the perception entity to the AMF may be carried in a non-access stratum (NAS) message, and the perception capability information sent by the AMF to the SSCF may be carried in a registration message.

[0156] Optionally, upon receiving the sensing capability information, the AMF may store the sensing capability information and establish a correspondence between each sensing entity and the sensing capability information. The AMF stores the sensing capability information so that the AMF can determine whether the sensing entity is a sending sensing entity and / or a receiving sensing entity based on the sensing capability information.

[0157] In the embodiment shown in FIG4 , the sensing entity sends sensing capability information to the SSCF through the AMF, so that both the AMF and the SSCF can determine that the sensing entity is a sending sensing entity and / or a receiving sensing entity based on the sensing capability information.

[0158] In the embodiments shown in Figures 3 and 4, if the first sensing entity and / or the second sensing entity is a terminal device, then its sensing capability information will be sent to the SSCF via the RAN, or sent to the AMF via the RAN, and then sent to the SSCF by the AMF. If the first sensing entity is a terminal device and the second sensing entity is a network device, then the second sensing entity may first send its own sensing capability information to the SSCF, and then send the sensing capability information of the first sensing entity to the SSCF; or, the sensing capability information of the first sensing entity and the sensing capability information of the second sensing entity may be sent to the SSCF together; or, the sensing capability information of the first sensing entity may be first sent to the SSCF, and then the sensing capability information of the second sensing entity may be sent to the SSCF.

[0159] Please refer to FIG5 , which is a schematic diagram of a process for subscription to a perception service provided in an embodiment of the present application. The subscription process may include but is not limited to the following steps:

[0160] 501. The sensing subscriber sends a subscription request message to the SSCF. Correspondingly, the SSCF receives the subscription request message from the sensing subscriber.

[0161] The perception subscriber can be understood as the consumer or user of the perception service, that is, the party requesting to use or obtain the perception service, such as an operator, client, or server. The SDPF can be understood as the provider of the perception service, that is, the party that provides the perception results of the perception service to the perception subscriber. The perception entity can be understood as the producer of the perception service, that is, the party that can provide the perception data of the perception service to the SDPF, such as raw data and / or measurement data. The SSCF can be understood as the party that controls the SDPF to provide the perception results.

[0162] The subscription request message is used to request subscription to a certain type of perception service. Upon receiving the subscription request message, the SSCF may generate a perception service identifier to identify the specific perception service subscribed to. In the embodiment of the present application, the generation of the first perception service identifier by the SSCF is taken as an example. Exemplarily, the SSCF may randomly generate the first perception service identifier, or generate the first perception service identifier based on the content carried in the subscription request message.

[0163] In one possible implementation, the subscription request message may include one or more of the following information: an identifier of the perception subscriber, subscription region information, the subscribed perception service type, and subscribed perception requirement information. The perception control entity may then generate a first perception service identifier corresponding to the content carried in the subscription request message. The first perception service identifier is used to identify the first perception service, i.e., the perception service to which the perception subscriber requests subscription.

[0164] Among them, the identification of the perception subscription end is used to identify the perception subscription end. The subscribed area information is used to indicate which area or areas of the perception service to request subscription. The area is the geographical location range divided by the operator according to the deployment location of the perception entity. The subscribed perception service type is used to indicate the type of perception service requested for subscription, which can be divided into monitoring, environment, imaging, positioning, etc. These four categories are large categories, and each category is further refined. For example, the monitoring category can be divided into mobile monitoring, intrusion monitoring, fall monitoring, health monitoring (such as monitoring respiratory rate, heartbeat, etc.), etc. Mobile monitoring can be divided into distance monitoring, location monitoring, mobile speed monitoring, mobile path monitoring, etc.; the environment category can be divided into ambient temperature, ambient humidity, air quality, weather conditions, crowd density, traffic density, air pressure, etc.; the imaging category can be divided into medical imaging, 3D map imaging, 3D map construction, building imaging, body temperature imaging, etc. The subscribed perception demand information is used to describe the indicator requirements of the perception service. The indicators may include but are not limited to one or more of distance accuracy, resolution, recognition accuracy, false alarm rate, positioning accuracy, latency, etc. Indicator requirements include, for example, the positioning accuracy error is within 10cm, the recognition accuracy is higher than 90%, etc.

[0165] It can be understood that the sensing service type in the subscription request message is coarse-grained, while the sensing service type in the sensing capability information is fine-grained.

[0166] In one implementation, the subscription request message may include one or more of the following information elements:

[0167] 1) sub_ID, which is used to identify the sensing subscriber;

[0168] 2) area_list, this information element is used to indicate the area or areas for which the perception service is requested to be subscribed;

[0169] 3) service_type, which is used to indicate the type of the perception service requested for subscription;

[0170] 4) kpi_list: This information element is used to indicate the indicator requirements of the perception service.

[0171] In one implementation, the awareness subscriber may send a subscription request message directly to the SSCF. In another implementation, the awareness subscriber may send a subscription request message to the SSCF via the NEF.

[0172] 502. SSCF generates a first perception service identifier.

[0173] When generating perception service identifiers, the SSCF avoids generating duplicate perception service identifiers. Optionally, the SSCF may generate a first perception service identifier corresponding to the content carried in the subscription request message. In other words, the first perception service identifier is bound to at least one of the regional information, perception service type, and perception requirement information in the subscription request message.

[0174] 503. The SSCF sends a subscription response message to the sensing subscriber. Correspondingly, the sensing subscriber receives the subscription response message from the SSCF.

[0175] Among them, the subscription response message carries the first perception service identifier.

[0176] Steps 501 to 503 are the perception service subscription process. Similarly, the perception subscription end can also request SSCF to cancel the perception service. For example, the perception subscription end sends a cancellation request message to SSCF, which can carry the first perception service identifier. If SSCF agrees to the cancellation, it can feedback a cancellation confirmation message to the perception subscription end.

[0177] In one implementation, the SSCF may directly send a subscription response message to the awareness subscriber. In another implementation, the SSCF may send a subscription response message to the awareness subscriber via the NEF.

[0178] In the embodiment shown in FIG5 , the SSCF feeds back the generated awareness service identifier to the awareness subscriber, so that the awareness subscriber requests the corresponding awareness service from the awareness control entity.

[0179] Please refer to FIG6 , which is a flowchart of a method for processing a perception service provided by an embodiment of the present application. The method may include but is not limited to the following steps:

[0180] 601: The third-party entity sends a service awareness request message to the SSCF. Correspondingly, the SSCF receives the service awareness request message from the third-party entity.

[0181] The third-party entity may be the perception subscription end in FIG5 , or may be another entity requesting a perception service.

[0182] In one implementation, the third-party entity may be the perception subscriber in FIG5 , and the perception service request message may include a perception service identifier for identifying the perception service subscribed to by the perception subscriber. In this embodiment of the application, taking the perception subscriber's subscription to a first perception service as an example, the perception service request message may include the first perception service identifier. It is understood that the perception service request message is used to request the perception result of the first perception service. This approach is based on the perception subscriber having subscribed to the perception service.

[0183] In another implementation, the third-party entity may be the entity requesting the perception service. The perception service request message is used to request the perception result of the first perception service. The perception service request message may include one or more of the following information: the identifier of the third-party entity, the area information of the first perception service, the perception service type of the first perception service, and the perception requirement information of the first perception service. This information is used to represent the perception service requested by the third-party entity. The identifier of the third-party entity is used to identify the third-party entity. In this method, the third-party entity does not subscribe to the perception service and directly carries information related to the first perception service in the perception service request message.

[0184] In one implementation, the third-party entity may send the awareness service request message directly to the SSCF. In another implementation, the third-party entity may send the awareness service request message to the SSCF via the NEF.

[0185] Step 601 is one possible way for the SSCF to obtain the first perception service identifier. In another possible way, at least one perception service exists on the SSCF, and the first perception service identifier is the perception service identifier of any perception service in the at least one perception service. The SSCF can also obtain the first perception service identifier through other methods.

[0186] 602. The SSCF determines a first perception entity and a second perception entity associated with a first perception service.

[0187] After receiving the first perception service request message, SSCF obtains the perception service type, regional information and perception demand information of the perception service (for example, the first perception service) subscribed by the third-party entity perception subscriber based on the first perception service identifier carried by the message, and allocates the task ID of the first perception service based on this information; or, allocates the task ID of the first perception service based on the perception service type, regional information and perception demand information of the first perception service carried by the first perception service request message (that is, allocates the task ID for processing the first perception service).

[0188] Optionally, the SSCF randomly assigns a task ID for the first perception service, and the task IDs for different perception services may be different.

[0189] The SSCF selects a sending sensing entity and a receiving sensing entity for processing the first sensing service based on the sensing service type, regional information, and one or more of the sensing requirement information, as well as the sensing capability information of each sensing entity. The selected sending sensing entities can be one or more, and the selected receiving sensing entities can also be one or more. The sensing entity processing the sensing service can be understood as a sensing entity that provides raw data and / or measurement data for the sensing service.

[0190] For example, a third-party entity requests the first perception service of area 1, and the type of the requested first perception service is mobile monitoring. The demand information indicates that the positioning accuracy error of the first perception service is within 10 cm. The current latitude and longitude information of perception entity a and perception entity b are within the range of area 1. The role identification of perception entity a is a sending perception entity, and the role identification of perception entity b is a receiving perception entity. Both perception entity a and perception entity b can support mobile information monitoring of mobile targets. Then SSCF can select perception entity a as the sending perception entity for processing the first perception service, and select perception entity b as the receiving perception entity for processing the first perception service.

[0191] Optionally, the SSCF assigns subtask IDs when or after assigning a task ID for processing the first perception service. In other words, the larger task of processing the first perception service is divided into multiple subtasks. When selecting the sending and receiving perception entities, the SSCF selects several pairs of perception entities, one pair of which is used to process one subtask. After assigning subtask IDs and selecting several pairs of perception entities, the SSCF establishes a correspondence between the subtask IDs and the perception entity pairs.

[0192] In the embodiment of the present application, the first perception entity is used as a sending perception entity, the second perception entity is used as a receiving perception entity, and the first perception entity and the second perception entity process the first subtask of the first perception service as an example.

[0193] 603: The SSCF sends a first awareness control message to the first awareness entity. Correspondingly, the first awareness entity receives the first awareness control message from the SSCF.

[0194] The first perception control message includes first indication information, and the first indication information is used to instruct the first perception entity to send a first perception signal for a first perception service. For example, the first indication information instructs the first perception entity to send the first perception signal to an object (such as a car or an IoT device) within a geographical location range that it can perceive.

[0195] In one possible implementation, the first perception control message further includes one or more of the following information: a first perception service identifier, a perception service type of the first perception service, and perception requirement information of the first perception service. The perception service type of the first perception service may be the same as the perception service type in the subscription request message, or may be a further refined perception service type. The perception requirement information of the first perception service may be the same as the perception requirement information in the subscription request message.

[0196] In one possible implementation, the first perception control message also includes a first subtask identifier, so that the first perception entity knows which subtask in the first perception service is being processed, and the first perception entity can then send a perception signal for the subtask. Alternatively, the first perception control message also includes a task identifier for processing the first perception service and a first subtask identifier, so that the first perception entity knows which subtask of which perception service is being processed.

[0197] 604: The SSCF sends a second awareness control message to the second awareness entity. Correspondingly, the second awareness entity receives the second awareness control message from the SSCF.

[0198] The second perception control message includes second indication information, where the second indication information is used to instruct the second perception entity to receive a second perception signal of the first perception service. For example, the second indication information instructs the second perception entity to perceive a second perception signal reflected by a target object. The second perception signal can be understood as a reflection of the first perception signal.

[0199] In a possible implementation, the second perception control message further includes one or more of the following information: a first perception service identifier, a perception service type of the first perception service, and perception requirement information of the first perception service.

[0200] In one possible implementation, the second perception control message also includes a first subtask identifier, so that the second perception entity knows which subtask in the first perception service is being processed, and the first perception entity can then receive the perception signal of the subtask. Alternatively, the second perception control message also includes a task identifier for processing the first perception service and a first subtask identifier, so that the second perception entity knows which subtask of which perception service is being processed.

[0201] In a possible implementation, the second perception control message is further used to instruct the second perception entity to perform layer 2 perception processing and / or layer 3 perception processing on the first subtask.

[0202] 605. The SSCF sends a third awareness control message to the SDPF. Correspondingly, the SDPF receives the third awareness control message from the SSCF.

[0203] The third perception control message is used to instruct the SDPF to process the perception data of the first perception service from the second perception entity.

[0204] In one possible implementation, the third perception control message is also used to indicate one or more of the following information: a first perception service identifier, a perception service type of the first perception service, perception requirement information of the first perception service, and a task identifier for processing the first perception service.

[0205] In one possible implementation, the third perception control message is also used to indicate the identifiers of each subtask for processing the first perception service, so that the SDPF processes the perception data of at least one subtask to obtain the perception result of the first perception service.

[0206] In one possible implementation, the third perception control message is further used to instruct the SDPF to perform L2 perception processing and / or L3 perception processing. Optionally, the third perception control message is further used to indicate the subtask identifier for performing L2 perception processing and / or the subtask identifier for performing L3 perception processing, allowing the SDPF to adopt different processing methods for different subtasks. For example, the third perception control message instructs the SDPF to perform L2 perception processing on the first subtask, instructs the SDPF to perform L3 perception processing on the second subtask, and so on.

[0207] In the embodiment of the present application, the order in which steps 603 to 605 are executed is not limited.

[0208] 606. The first perception entity performs the first perception service.

[0209] After receiving the first perception control message, the first perception entity executes a first perception service. Executing the first perception service may specifically be executing a first subtask of the first perception service, such as sending a first perception signal of the first subtask.

[0210] 607. The second perception entity executes the first perception service.

[0211] After receiving the second perception control message, the second perception entity executes the first perception service. Executing the first perception service may specifically be executing the first subtask of the first perception service, which may include, for example, receiving the second perception signal of the first subtask; establishing a perception data bearer with the SDPF, and sending the perception data and / or perception results of the first subtask to the SDPF via the established perception data bearer.

[0212] If the second perception entity has layer 1 perception processing capability, the second perception entity obtains information such as the phase and amplitude of the second perception signal to obtain the original data of the first subtask, and then can send the original data of the first subtask to the SDPF through the perception data bearer.

[0213] If the second perception entity has layer 1 perception processing capabilities and layer 2 perception processing capabilities, then the second perception entity can obtain the original data of the first subtask through the received second perception signal, process the original data of the first subtask to obtain the measurement data of the first subtask, and then send the measurement data of the first subtask to the SDPF through the perception data bearer.

[0214] If the second perception entity has layer 1 perception processing capability, layer 2 perception processing capability and layer 3 perception processing capability, then the second perception entity can obtain the original data of the first subtask through the received second perception signal, and then send the original data of the first subtask to the SDPF through the perception data bearer; or, the second perception entity can obtain the original data of the first subtask through the received second perception signal, process the original data of the first subtask to obtain the measurement data of the first subtask, and then send the measurement data of the first subtask to the SDPF through the perception data bearer; or, the second perception entity can obtain the original data of the first subtask through the received second perception signal, process the original data of the first subtask to obtain the measurement data of the first subtask, process the measurement data of the first subtask to obtain the perception result of the first subtask, and then send the perception result of the first subtask to the SDPF through the perception data bearer.

[0215] If the second perception entity has Layer 1, Layer 2, and Layer 3 perception processing capabilities, the second perception control message may further indicate whether the second perception entity should perform perception processing on the first subtask. If it indicates that the second perception entity should perform perception processing on the first subtask, it may further indicate that at least one of Layer 1, Layer 2, and Layer 3 perception processing should be performed. For example, the second perception control message may instruct the second perception entity to perform Layer 1 and Layer 2 perception processing on the first subtask, while the third perception control message may instruct the SDPF to perform Layer 3 perception processing on the first subtask. In other words, the second perception control message instructing the second perception entity to perform perception processing on a certain subtask may complement the third perception control message instructing the SDPF to perform perception processing on that subtask.

[0216] 608. SDPF executes the first perception service.

[0217] The SDPF receives the perception data and / or perception results of one or more subtasks from one or more receiving perception entities via one or more perception data bearers. In other words, the SDPF may receive the perception data of some subtasks and the perception results of some subtasks.

[0218] If the third perception control message instructs the SDPF to perform L2 processing, the SDPF processes the received perception data (ie, original data) to obtain a measurement result, which can be used as the perception result.

[0219] If the third perception control message instructs the SDPF to perform L3 processing, the SDPF processes the received perception data (ie, original data and / or measurement data) to obtain a perception result.

[0220] If the third perception control message indicates a subtask identifier for L2 processing and / or a subtask identifier for L3 processing, the SDPF processes the perception data of these subtasks according to the subtask identifier for L2 processing to obtain measurement results; and / or processes the perception data of these subtasks according to the subtask identifier for L3 processing to obtain perception results.

[0221] SDPF fuses the perception results of each subtask to obtain the perception result of the first perception service. How SDPF specifically fuses the perception results of each subtask is not limited in the embodiment of this application, and there may be different fusion methods for different perception service types. For example, the first perception service is to locate the target object, and the perception result of each subtask is a longitude and latitude coordinate. The average value of multiple longitude and latitude coordinates is used as the perception result of the first perception service.

[0222] 609. SDPF sends the perception result of the first perception service.

[0223] In one implementation, the SDPF directly sends the perception result of the first perception service to the third-party entity. In another implementation, the SDPF sends the perception result of the first perception service to the third-party entity via the NEF. When the third-party entity sends a perception service request message, the SDPF feeds back the perception result of the first perception service to the third-party entity.

[0224] In the embodiment shown in Figure 6, in a scenario where there are a large number of perception services in the communication system, SSCF serves as the control plane entity of the perception services, and SDPF serves as the data plane entity of the perception services, which can realize the processing of the perception services and help improve the processing efficiency of the perception services.

[0225] As an optional embodiment, if the first perception entity and the second perception entity are the same, the SSCF only needs to send a perception control message to the perception entity. The perception control message is used to instruct the perception entity to send a first perception signal of the first perception service and receive a second perception signal of the first perception service. This eliminates the need for perception signal transmission between the first perception entity and the second perception entity, saving air interface resources and signaling overhead.

[0226] Please refer to FIG7 , which is a flowchart of another method for processing a sensing service provided in an embodiment of the present application. The method may include but is not limited to the following steps:

[0227] 701, the third-party entity sends a first awareness service request message to the SSCF. Correspondingly, the SSCF receives the first awareness service request message from the third-party entity. The implementation process of step 701 can refer to the detailed description of step 601 in the embodiment shown in Figure 6, and will not be repeated here.

[0228] 702. The SSCF sends a second awareness service request message to the AMF. Correspondingly, the AMF receives the second awareness service request message from the SSCF.

[0229] After receiving the first perception service request message, the SSCF obtains the perception service type, regional information, and perception requirement information of the perception service (for example, the first perception service) subscribed by the third-party entity perception subscriber based on the first perception service identifier carried in the message, and sends a second perception service request message to the AMF based on this information; or, based on the perception service type, regional information, and perception requirement information of the first perception service carried in the first perception service request message, sends a second perception service request message to the AMF. The second perception service request message includes the perception service type, regional information, and perception requirement information of the first perception service.

[0230] In a possible implementation, the SSCF may allocate a task ID of the first perception service, and the second perception service request message may further include the task ID of the first perception service.

[0231] In one possible implementation, the SSCF may further allocate a subtask ID, and the second perception service request message may further include the subtask ID of each subtask.

[0232] 703. The SSCF sends a third awareness control message to the SDPF. Correspondingly, the SDPF receives the third awareness control message from the SSCF.

[0233] The third perception control message is used to instruct the SDPF to process the perception data of the first perception service from the second perception entity.

[0234] In one possible implementation, the third perception control message is further used to indicate one or more of the following information: a first perception service identifier, a perception service type of the first perception service, perception requirement information of the first perception service, and a task ID for processing the first perception service.

[0235] In one possible implementation, the third perception control message is also used to indicate the identifiers of each subtask for processing the first perception service, so that the SDPF processes the perception data of at least one subtask to obtain the perception result of the first perception service.

[0236] In one possible implementation, the third perception control message is further used to instruct the SDPF to perform L2 processing and / or L3 processing. The third perception control message instructing the SDPF to perform L2 processing indicates that the perception entity has L1 perception processing capabilities; the third perception control message instructing the SDPF to perform L3 processing indicates that the perception entity has both L1 and L2 perception processing capabilities. Optionally, the third perception control message is further used to indicate the subtask identifier for performing L2 processing and / or the subtask identifier for performing L3 processing, allowing the SDPF to adopt different processing methods for different subtasks.

[0237] 704. AMF determines a first perception entity and a second perception entity associated with the first perception service.

[0238] When SSCF receives the second perception service request message, it selects the sending perception entity and the receiving perception entity for processing the first perception service based on the perception service type, area information and perception demand information of the first perception service carried by it, as well as the perception capability information of each stored perception entity.

[0239] Optionally, the second perception service request message also includes the task ID and subtask ID of the first perception service. When selecting the sending perception entity and the receiving perception entity, the AMF selects at least one pair of perception entities, each of which is used to process one subtask. The AMF establishes a correspondence between the subtask ID and the perception entity pair.

[0240] 705. The AMF sends a first perception control message to the first perception entity. Correspondingly, the first perception entity receives the first perception control message from the AMF. For details about the content of the first perception control message, refer to the detailed description of the first perception control message in the embodiment shown in FIG. 6 , and are not further described here.

[0241] 706. The AMF sends a second perception control message to the second perception entity. Correspondingly, the second perception entity receives the second perception control message from the AMF. For details about the content of the second perception control message, refer to the detailed description of the second perception control message in the embodiment shown in FIG. 6 , and are not further described here.

[0242] 707. The first perception entity performs the first perception service.

[0243] 708. The second perception entity executes the first perception service.

[0244] 709. SDPF executes the first perception service.

[0245] 710. SDPF sends the perception result of the first perception service.

[0246] The implementation process of steps 707 to 710 may refer to the detailed description of steps 606 to 609 in the embodiment shown in FIG6 , and will not be repeated here.

[0247] In the embodiment shown in Figure 7, in a scenario where there are a large number of perception services in the communication system, SSCF and AMF serve as control plane entities of the perception services, and SDPF serves as the data plane entity of the perception services, which can realize the processing of the perception services and help improve the processing efficiency of the perception services.

[0248] As an optional embodiment, if the first perception entity and the second perception entity are the same, the AMF only needs to send a perception control message to the perception entity. The perception control message is used to instruct the perception entity to send a first perception signal for the first perception service and receive a second perception signal for the first perception service. This eliminates the need for perception signal transmission between the first perception entity and the second perception entity, saving air interface resources and signaling overhead.

[0249] The difference between the embodiment shown in Figure 7 and the embodiment shown in Figure 6 is that, in the embodiment shown in Figure 6, the SSCF determines the perception entity associated with the perception business, while the AMF determines the perception entity associated with the perception business in the embodiment shown in Figure 7, which is more easily compatible with the 5G system.

[0250] The present application provides a communication device that can be used to implement the functions of the above-mentioned SSCF, SDPF, perception entity or AMF. The communication device can be SSCF, SDPF, perception entity or AMF. The communication device includes a unit that corresponds one-to-one to the method / operation / step / action performed by SSCF, SDPF, perception entity or AMF in the above-mentioned method embodiment. The unit can be a hardware circuit, or software, or a combination of a hardware circuit and software. Please refer to Figure 8, which shows a structural diagram of a communication device 800 of an embodiment of the present application. The communication device 800 may include an interface unit 801 and a processing unit 802. Specifically, the processing unit 802 is used to process signaling and / or data, and the signaling and / or data may be data received by the interface unit 801, and the processed signaling and / or data may also be sent by the interface unit 801;

[0251] In one embodiment, when the communication device 800 is an SSCF, wherein:

[0252] The interface unit 801 is configured to obtain a first perception service identifier;

[0253] A processing unit 802 is configured to determine a first sensing entity and a second sensing entity associated with a first sensing service, where the first sensing service is determined according to a first sensing service identifier;

[0254] The interface unit 801 is also used to send a first perception control message to the first perception entity, where the first perception control message includes first indication information, and the first indication information is used to instruct the first perception entity to send a first perception signal for the first perception service; and to send a second perception control message to the second perception entity, where the second perception control message includes second indication information, and the second indication information is used to instruct the second perception entity to receive a second perception signal for the first perception service.

[0255] In this embodiment, for the specific implementation of the above-mentioned interface unit 801 and processing unit 802, reference may be made to the specific implementation steps of the SSCF in FIG6 , which will not be repeated here.

[0256] In another embodiment, when the communication device shown in FIG8 is an AMF, wherein:

[0257] The interface unit 801 is configured to obtain a first perception service identifier;

[0258] A processing unit 802 is configured to determine a first sensing entity and a second sensing entity associated with a first sensing service, where the first sensing service is determined according to a first sensing service identifier;

[0259] The interface unit 801 is also used to send a first perception control message to the first perception entity, where the first perception control message includes first indication information, and the first indication information is used to instruct the first perception entity to send a first perception signal for the first perception service; and to send a second perception control message to the second perception entity, where the second perception control message includes second indication information, and the second indication information is used to instruct the second perception entity to receive a second perception signal for the first perception service.

[0260] In this embodiment, for the specific implementation of the above-mentioned interface unit 801 and processing unit 802, please refer to the specific implementation steps of AMF in Figure 7, which will not be repeated here.

[0261] In yet another embodiment, when the communication device shown in FIG8 is an SDPF, wherein:

[0262] The interface unit 801 is configured to receive a third perception control message from the perception control entity, where the third perception control message is used to instruct processing of perception data of a first perception service; and receive perception data of the first perception service;

[0263] The processing unit 802 is configured to obtain a perception result of the first perception service based on the perception data of the first perception service, and send the perception result of the first perception service.

[0264] In this embodiment, for the specific implementation of the above-mentioned interface unit 801 and processing unit 802, reference may be made to the specific implementation steps of SDPF in FIG. 6 or FIG. 7 , which will not be repeated here.

[0265] In yet another embodiment, when the communication device shown in FIG8 is a sensing entity, wherein:

[0266] The interface unit 801 is configured to receive a first perception control message and / or a second perception control message; the first perception control message is used to instruct the sending of a first perception signal for a first perception service; the second perception control message is used to instruct the receiving of a second perception signal for the first perception service;

[0267] The processing unit 802 is configured to send a first perception signal based on the first perception control message; and / or receive the second perception signal based on the second perception control message.

[0268] In this embodiment, regarding the specific implementation of the above-mentioned interface unit 801 and processing unit 802, please refer to the specific implementation steps of the first perception entity and the second perception entity in Figure 6 or Figure 7, which will not be repeated here.

[0269] FIG9 shows a communication device 900 provided in an embodiment of the present application, configured to implement the aforementioned functions of the SSCF, SDPF, perception entity, or AMF. The device may be a communication device or a device used in a communication device. The communication device may be an SSCF, SDPF, perception entity, or AMF. The device used in the communication device may be a system-on-chip (SoC) or chip within the communication device. The SoC may consist of a chip or may include a chip and other discrete components.

[0270] The communication device 900 includes at least one processor 910 for implementing the processing functions of the device (such as SSCF, SDPF, perception entity or AMF) in the method provided in the embodiment of the present application. The communication device 900 may also include a communication interface 920 for implementing the transceiver operation of the device (such as SSCF, SDPF, perception entity or AMF) in the method provided in the embodiment of the present application. In the embodiment of the present application, the communication interface may be a transceiver, circuit, bus, module or other type of communication interface for communicating with other devices through a transmission medium. For example, the communication interface 920 is used for the device in the communication device 900 to communicate with other devices. The processor 910 uses the communication interface 920 to send and receive data, and is used to implement the method described in the above method embodiment.

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

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

[0273] When the communication device 900 is specifically a device for a device (such as an SSCF, SDPF, a perception entity, or an AMF), for example, when the communication device 900 is specifically a chip or a chip system, the communication interface 920 may output or receive a baseband signal. When the communication device 900 is specifically a device (such as a perception entity), the communication interface 920 may output or receive a radio frequency signal. In an embodiment of the present application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array, or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.

[0274] It should be noted that the above-mentioned communication interface 920 can be used to perform the functions of the above-mentioned interface unit 801, and the above-mentioned processor 910 can be used to perform the functions of the above-mentioned processing unit 802, which will not be repeated here.

[0275] When the above-mentioned communication device is a chip applied to SSCF, the chip implements the function of SSCF in the above-mentioned method embodiment, and the chip receives information from other devices; or the chip sends information to other devices.

[0276] When the communication device is a chip used in an SDPF, the chip implements the functions of the SDPF in the above method embodiment. The chip receives information from other devices; or the chip sends information to other devices.

[0277] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0278] The method steps in the embodiments of the present application can be implemented by hardware or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, mobile hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and storage medium can be located in an ASIC. In addition, the ASIC can be located in an access network device or a terminal. Of course, the processor and storage medium can also exist as discrete components in a terminal or access network device.

[0279] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instruction is loaded and executed on a computer, the process or function described in the embodiment of the present application is executed in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program or instruction can be stored in a computer-readable storage medium or transmitted via the computer-readable storage medium. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it can also be an optical medium; it can also be a semiconductor medium, such as a solid state drive (SSD).

[0280] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0281] It is understood that the various numbers used in the embodiments of this application are merely for ease of description and are not intended to limit the scope of the embodiments of this application. The order of the sequence numbers of the above-mentioned processes does not necessarily imply a specific order of execution; the order of execution of the processes should be determined by their functions and inherent logic.

[0282] An embodiment of the present application also provides a computer-readable storage medium, which stores computer execution instructions. When the computer execution instructions are executed, the method executed by the SSCF module, SDPF module, perception entity or AMF module in the above method embodiment is implemented.

[0283] An embodiment of the present application also provides a computer program product, which includes a computer program. When the computer program is executed, the method performed by the SSCF module, SDPF module, perception entity or AMF module in the above method embodiment is implemented.

[0284] The embodiment of the present application further provides a communication system, which includes an SSCF module, an SDPF module, a perception entity, and an AMF module. Each module is used to execute the method executed by each module in the above method embodiment.

[0285] It should be noted that for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by this application.

[0286] The descriptions of the various embodiments provided in this application can refer to each other. The descriptions of each embodiment have their own focus. For parts not described in detail in a particular embodiment, please refer to the relevant descriptions of other embodiments. For the convenience and brevity of description, for example, the functions and execution steps of the various devices and equipment provided in the embodiments of this application can refer to the relevant descriptions of the method embodiments of this application. The various method embodiments and the various device embodiments can also refer to, be combined with, or quote each other.

[0287] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some or all of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for processing a perception service, characterized in that: The method comprises: Get the first perception service identifier Determine a first perception entity and a second perception entity associated with a first perception service; the first perception service is determined according to the first perception service identifier; Sending a first perception control message to the first perception entity, where the first perception control message includes first indication information, where the first indication information is used to instruct the first perception entity to send a first perception signal for the first perception service; A second perception control message is sent to the second perception entity, where the second perception control message includes second indication information, and the second indication information is used to instruct the second perception entity to receive a second perception signal of the first perception service.

2. The method according to claim 1, characterized in that The method further comprises: A third perception control message is sent to a perception processing entity, where the third perception control message is used to instruct the perception processing entity to process the perception data of the first perception service from the second perception entity.

3. The method according to claim 1 or 2, characterized in that: Before determining the first perception entity and the second perception entity associated with the first perception service, the method further includes: receiving sensing capability information of the first sensing entity; and / or, Receive the sensing capability information of the second sensing entity.

4. The method according to claim 3, characterized in that The method further comprises: The sensing capability information of the first sensing entity and / or the sensing capability information of the second sensing entity is sent to a sensing control entity.

5. The method according to claim 3 or 4, characterized in that: The perception capability information includes one or more of the following information: device identification, role identification, device type, geographic location information, perception processing capability, and supported perception service types.

6. The method according to claim 5, characterized in that The perception processing capability includes one or more of the following capabilities: layer 1 perception capability, layer 2 perception capability, and layer 3 perception capability; wherein the layer 1 perception capability is used to perceive raw data, the layer 2 perception capability is used to perceive measurement data, and the layer 3 perception capability is used to process the perception data to obtain a perception result; the perception data includes the raw data and / or the measurement data.

7. The method according to any one of claims 1 to 6, characterized in that: The first perceiving entity is the same as or different from the second perceiving entity.

8. The method according to any one of claims 1 to 7, characterized in that: The method further comprises: Receive a subscription request message from a sensing subscriber; Generate the first perception service identifier according to the subscription request message; A subscription response message is sent to the perception subscription end, where the subscription response message includes the first perception service identifier.

9. The method according to claim 8, characterized in that The subscription request message includes one or more of the following information: the identifier of the perception subscription end, the subscribed area information, the subscribed perception service type, and the subscribed perception demand information.

10. The method according to any one of claims 1 to 9, characterized in that: The first perception control message also includes one or more of the following information: the first perception service identifier, the perception service type of the first perception service, and the perception demand information of the first perception service; the second perception control message also includes one or more of the following information: the first perception service identifier, the perception service type of the first perception service, and the perception demand information of the first perception service.

11. The method according to any one of claims 2 to 10, characterized in that: The first sensing entity and the second sensing entity are associated with a first subtask of processing a first sensing service; wherein the first subtask The task is to process any subtask of at least one subtask of the first perception service.

12. The method according to claim 11, characterized in that The first perception control message also includes a first subtask identifier, the second perception control message also includes the first subtask identifier, and the third perception control message is further used to indicate an identifier of at least one subtask; wherein the first subtask identifier is used to identify the first subtask.

13. A method for processing a perception service, characterized in that: The method comprises: receiving a third perception control message from the perception control entity, where the third perception control message is used to instruct processing of perception data of the first perception service; receiving the perception data of the first perception service; Obtaining a perception result of the first perception service according to the perception data of the first perception service; Sending a perception result of the first perception service.

14. The method according to claim 13, characterized in that The sending the perception result of the first perception service includes: The perception result of the first perception service is sent to the perception subscription terminal of the first perception service through the network open module.

15. The method according to claim 13 or 14, characterized in that The receiving the perception data of the first perception service includes: The perception data of the first perception service is received through the perception data bearer.

16. A method for processing a perception service, characterized in that: The method comprises: receiving a first perception control message and / or a second perception control message; the first perception control message is used to indicate sending a first perception signal of a first perception service; the second perception control message is used to indicate receiving a second perception signal of the first perception service; Based on the first perception control message, the first perception signal is sent; and / or based on the second perception control message, the second perception signal is received.

17. The method according to claim 16, characterized in that Before receiving the first perception control message and / or the second perception control message, the method further includes: Sends sensory capability information.

18. The method according to claim 17, characterized in that The perception capability information includes one or more of the following information: device identification, role identification, device type, geographic location information, perception processing capability, and supported perception service types.

19. The method according to claim 18, characterized in that The perception processing capability includes one or more of the following capabilities: layer 1 perception capability, layer 2 perception capability, and layer 3 perception capability; wherein the layer 1 perception capability is used to perceive raw data, the layer 2 perception capability is used to perceive measurement data, and the layer 3 perception capability is used to process the perception data to obtain a perception result; the perception data includes the raw data and / or the measurement data.

20. A communication device, characterized in that: Comprising modules for executing the method as claimed in any one of claims 1 to 12.

21. A communication device, characterized in that: Comprising means for performing the method as claimed in any one of claims 13 to 15.

22. A communication device, characterized in that: Comprising means for performing the method as claimed in any one of claims 16 to 19.

23. A communication device, characterized in that: The method comprises a processor, wherein the processor is used to implement the method according to any one of claims 1 to 12, the method according to any one of claims 13 to 15, or the method according to any one of claims 16 to 19 through a logic circuit and / or by executing a computer program or instruction.

24. The communication device according to claim 23, characterized in that Also includes: The memory is used to store the computer program or instructions.

25. A communication device, characterized in that: It includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor is used to implement the method as described in any one of claims 1 to 12; or the method as described in any one of claims 13 to 15; or the method as described in any one of claims 16 to 19 through a logic circuit or executing code instructions.

26. A computer-readable storage medium, characterized in that: The storage medium stores a computer program or instruction. When the computer program or instruction is executed by the communication device, it implements the method as described in any one of claims 1 to 12; or the method as described in any one of claims 13 to 15; or the method as described in any one of claims 16 to 19.

27. A computer program product, characterized in that The method comprises a computer program code, which, when executed, implements the method according to any one of claims 1 to 12; or the method according to any one of claims 13 to 15; or the method according to any one of claims 16 to 19.

28. A communication system, characterized in that: The invention comprises an apparatus for executing the method according to any one of claims 1 to 12, and an apparatus for executing the method according to any one of claims 13 to 15.

29. The communication system according to claim 28, characterized in that Also included is an apparatus for executing the method of any one of claims 16-19.

Citation Information

Patent Citations

  • Method, communication device and system for providing communication awareness service

    CN115706955A

  • Method for sensing terminal equipment and communication device

    CN115734200A

  • Method and equipment for processing perception service

    CN115755027A

  • Method and device for establishing sensing channel, communication equipment, storage medium and system

    CN115811736A

  • Wireless sensing method and apparatus, device, and storage medium

    WO2023131315A1