Method and apparatus for determining sensing service policy, and communication system

Abstract

Provided in the embodiments of the present application are a method and apparatus for determining a sensing service policy, and a communication system. The method comprises: a first functional network element acquiring identification information of a sensing service; determining policy information of the sensing service on the basis of the identification information of the sensing service, wherein the policy information of the sensing service comprises quality-of-service information of the sensing service; and the first functional network element then sending to a second functional network element the policy information of the sensing service. It can be seen that in the method, the first functional network element can determine, from a service dimension, policy information of a sensing service, so as to provide the quality of service of the sensing service; and the method is also applicable to an evolved communication network, and therefore the method can effectively satisfy and support a policy requirement for the sensing service.

Description

A method and device for determining a perception service strategy and a communication system

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of the People's Republic of China on December 27, 2023, with application number 202311828022.2 and application name "A method and device for determining a business policy and a communication system for perception", the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a method and device for determining a perception service strategy and a communication system. Background Art

[0004] The policy and charging control (PCC) architecture is used in existing communication networks to provide users with differentiated, intelligent business services and experiences, and to implement dynamic policy management and billing methods. The policy and charging rule function (PCRF) is the core of the PCC architecture of fourth-generation (4G) or long-term evolution (LTE) networks. PCRF is used to assist in service data flow detection, policy implementation, and flow-based charging, ensuring reliable monitoring of services or use cases and the costs associated with each use case. The policy control function (PCF) is the core of the PCC architecture of fifth-generation (5G) networks. PCF can be considered an evolution of PCRF. PCF adds the ability to request and monitor service quality on a per-session basis. In addition to retaining these session-based functions, PCF also adds other functions, including control of network slicing and new control mechanisms for terminal activities, such as roaming and mobility management.

[0005] In the 4G policy architecture, different quality of service (QoS) attributes are applied end-to-end across bearers. Data flows on the same bearer can receive the same QoS, while data flows on different types of bearers receive different QoS. This results in coarse-grained QoS control, leading to high signaling overhead and lengthy QoS control interactions, making it difficult to handle bursty and complex services. In the 5G policy architecture, QoS flows are implemented end-to-end, and two-level mapping between 5G next-generation user plane (NG-U) tunnels and radio bearers can be performed on the access network side. This allows the radio access network a certain degree of freedom, thereby improving the flexibility and adaptability of service bearer control.

[0006] With the evolution of communication technology, communication systems will provide not only connection services but also perception services. However, the existing policy architecture cannot support or meet the policy requirements of perception services.

[0007] Summary of the Invention

[0008] The present application proposes a method and device for determining a perception service policy and a communication system, which can meet or support policy requirements of perception services in a communication network.

[0009] In a first aspect, an embodiment of the present application provides a method for determining a perception service policy. The method can be executed by a first functional network element, or by a chip, chip system, logic module, or software corresponding to the first functional network element, without limitation. Taking the first functional network element as an example, the method may include: the first functional network element obtains identification information of the perception service; then, based on the identification information of the perception service, determines policy information of the perception service; the policy information of the perception service includes first service quality information of the perception service; and the first functional network element sends the policy information of the perception service to a second functional network element.

[0010] In an embodiment of the present application, the first functional network element can be independently deployed in the communication network / communication system. The first functional network element can also be co-located with the policy control function network element. The first functional network element can also be a policy control function PDF network element. The second functional network element can be independently deployed in the core network, access network, or network management system of the communication network / communication system. The second functional network element can also be co-located with the first service network element. The first service network element can be, but is not limited to, a data controller, a perception service control function, a task anchor, or a task scheduler. This application does not limit the specific deployment, form, or number of the first functional network element and the second functional network element.

[0011] Exemplarily, the sensing service may include identification, speed measurement, distance measurement, target positioning, etc.

[0012] In the present application, the first functional network element can determine policy information for the perception service based on the identification information of the perception service. The policy information for the perception service includes first quality of service information for the perception service. Therefore, it can be seen that the first functional network element in the present application determines the policy information for the perception service from a service perspective. The first functional network element can effectively provide quality of service for the perception service, and is also applicable to evolved communication systems. It can meet and support the policy requirements of the perception service.

[0013] In a possible implementation manner, the policy information of the sensing service further includes one or more items of execution scope information of the sensing service and collection policy information of the sensing service.

[0014] In the embodiment of the present application, the collection strategy of the sensing service may include but is not limited to the minimum sensing signal for sensing measurement, the time interval for collecting data, and whether the collected data is real-time or non-real-time.

[0015] In one possible implementation, the identification information of the perception service corresponds to the user information of the perception service (equivalent to the identification information of the perception service and the user information of the perception service being able to be associated with each other), and the user information of the perception service may include but is not limited to one or more of the following: user contract information of the perception service, user account opening information of the perception service, and service subscription information of the perception service.

[0016] For example, user contract information or service subscription information for the perception service may include perception service packages, perception service monthly packages, gift package discounts (e.g., number of discounts, duration, etc.), incentives for participating in the perception service, etc. User account opening information for the perception service may include user identity information, address information, user level information, etc.

[0017] Through this implementation, the first functional network element can effectively determine corresponding policy information for the perception service based on user information of the perception service.

[0018] In one possible implementation, the first functional network element obtains identification information of the perception service, including: obtaining identification information of the perception service and / or user information of the perception service from a service user management network element of the perception service. The service user management network element of the perception service may be independently deployed in the network, or the service user management network element of the perception service may be co-located with a data storage network element, or the service user management network element of the perception service may be a data storage network element.

[0019] In the embodiments of the present application, the service user management network element of the perception service may be used to manage or store user information and / or identification information of the perception service. For different perception services, the service user management network element of the perception service may be the same network element or different network elements, without limitation. If different perception services correspond to different service user management network elements, the names of the service user management network elements of the perception services may be the same or different, without limitation.

[0020] Through this implementation, the first functional network element can effectively obtain identification information of the perception service, and further effectively obtain user information of the perception service.

[0021] In one possible implementation, the first quality of service information of the perception service may include but is not limited to the transmission delay of the perception service, the maximum bandwidth of the perception service, the guaranteed bandwidth of the perception service, the execution cycle of the perception service, the maximum data burst of the perception service, the number of nodes participating in the perception service, the time difference range of the synchronous arrival of the perception service data, the deterministic delay of the synchronous arrival of the perception service data, and the priority of the perception service.

[0022] Through this implementation, the first functional network element allocates corresponding bandwidth, execution cycle, data volume, nodes participating in the perception service, transmission delay information of the perception service data, and priority of the perception service to the perception service based on the user information of the perception service to ensure the service quality of the perception service.

[0023] In one possible implementation, the policy information for the perception service may also include, but is not limited to, one or more of the following: flow policy information for the perception service and security policy information for the perception service. Through this implementation, the first functional network element can also determine other policy information required for the perception service to meet the various policy requirements of the perception service. The flow policy information for the perception service may provide a data bearer configuration strategy for implementing the perception service, which may include topology information such as the source, destination, intermediate nodes, and data pipelines, as well as policies such as the bandwidth and latency required for data flow.

[0024] In a second aspect, an embodiment of the present application provides a method for determining a perception service policy, which can be executed by a second functional network element, or by a chip, or chip system, or logic module, or software corresponding to the second functional network element, without limitation. Taking the second functional network element as an example, the method may include: the second functional network element receives policy information of the perception service from the first functional network element, where the policy information of the perception service includes first quality of service information of the perception service; and then, based on the policy information of the perception service, determines information of at least one data pipeline corresponding to the perception service, and determines second quality of service information corresponding to each of the at least one data pipelines.

[0025] In an embodiment of the present application, the first functional network element can be independently deployed in the communication network / communication system. The first functional network element can also be co-located with the policy control function network element. The first functional network element can also be a policy control function PDF network element. The second functional network element can be independently deployed in the core network, access network, or network management system of the communication network / communication system. The second functional network element can also be co-located with the first service network element. The first service network element can be, but is not limited to, a data controller, a perception service control function, a task anchor, or a task scheduler. This application does not limit the specific deployment, form, or number of the first functional network element and the second functional network element.

[0026] Exemplarily, the types of sensing services may include identification, speed measurement, distance measurement, target positioning, and the like.

[0027] In the present application, after receiving the policy information for the perception service, the second functional network element further determines information about at least one data pipeline for carrying the perception service data, as well as the quality of service information corresponding to each data pipeline, based on the policy information for the perception service. In this method, the second functional network element can perform more refined global planning and data pipeline orchestration based on the policy information for the perception service.

[0028] In one possible implementation, the first quality of service information of the perception service may include but is not limited to one or more of the following: the transmission delay of the perception service, the maximum bandwidth of the perception service, the guaranteed bandwidth of the perception service, the execution cycle of the perception service, the maximum data burst of the perception service, the number of nodes participating in the perception service, the time difference range of the synchronous arrival of the perception service data, the deterministic delay of the synchronous arrival of the perception service data, and the priority of the perception service.

[0029] Through this implementation, the first functional network element can provide the transmission delay, bandwidth information, sensing execution cycle, data volume information and the number of participating nodes corresponding to the perception service, as well as the delay difference and delay information of data transmission, so as to ensure that the second functional network element can effectively and accurately plan the specific policy information of the perception service, thereby meeting the policy requirements of the perception service.

[0030] In one possible implementation, the policy information for the sensor service may also include, but is not limited to, one or more of the following: flow policy information for the sensor service and security policy information for the sensor service. With this implementation, the second functional network element can also obtain other policy information required for the sensor service to further determine a more precise policy for the sensor service, thereby meeting the various policy requirements of the sensor service.

[0031] In one possible implementation, the policy information for the sensing service also includes collection policy information for the sensing service. The method may further include: the second functional network element determining, based on the collection policy information for the sensing service, collection policy information for the source nodes corresponding to the at least one data pipeline. With this implementation, the second functional network element can also determine collection policy information for the source nodes of each orchestrated data pipeline based on the collection policy information for the sensing service, thereby achieving more refined data collection and ensuring more accurate collection results.

[0032] In one possible implementation, the policy information of the perception service also includes execution scope information of the perception service; the method also includes: the second functional network element obtains the status information and / or node status information of the network within the execution scope of the perception service based on the execution scope information of the perception service; then the second functional network element determines the information of at least one data pipeline corresponding to the perception service based on the policy information of the perception service, which may include: determining the information of the destination node and the source node corresponding to the at least one data pipeline respectively based on the policy information of the perception service, as well as the status information of the network and / or the capability information of the node and / or the status information of the node.

[0033] In this embodiment, the second functional network element selects relatively robust and appropriate nodes within the execution scope of the perception service in combination with the state information of the network within the execution scope and / or the state information of each node in the network and / or the capability information of the nodes (such as perception capability, computing capability, etc.), and uses these nodes to construct at least one data pipeline for transmitting perception service data; the second functional network element can also determine the corresponding service quality for the at least one data pipeline based on the first service quality information of the perception service and in combination with the state information of the network and / or the capability information of each node in the network and / or the state information of each node. Through this embodiment, the second functional network element can effectively arrange a more accurate layout and service quality for the data bearer of the perception service.

[0034] In a possible implementation, the method further includes: the second functional network element sends corresponding second service quality information and collection strategy information of the source node to the source node corresponding to the at least one data pipeline based on the information of the source node corresponding to the at least one data pipeline.

[0035] Through this implementation, the second functional network element sends the service quality information corresponding to each data pipeline and the collection strategy information of the source node to the corresponding source node, so that each source node can effectively implement the collection strategy information and report the perception service data.

[0036] In one possible implementation, the information of any data pipeline may further include information of at least one intermediate node within the execution scope of the sensing service and / or identification information of the data pipeline, such as a data pipeline identifier (DPID).

[0037] Through this implementation, the number of nodes in the layout of the data pipeline can be flexible, and the location / type of the nodes can also be flexible. The second functional network element can flexibly topology and orchestrate each data pipeline; in addition, each data pipeline can be effectively identified through the corresponding identification information.

[0038] In one possible implementation, the method further includes: when the first source node of the first data pipeline moves out of the execution scope of the perception service, the second functional network element determines a second node within the execution scope of the perception service; and uses the second node as the source node of the first data pipeline to obtain an updated first data pipeline; the first data pipeline is any one of the at least one data pipeline.

[0039] Through this implementation, when the source node position of any data pipeline changes and becomes unusable, the second functional network element can determine a new node to replace it, thereby ensuring the transmission validity of each data pipeline.

[0040] In one possible implementation, the method also includes: the second functional network element determines the service quality information corresponding to the updated first data pipeline and the collection strategy information of the second node; and then sends the service quality information corresponding to the updated first data pipeline and the collection strategy information of the second node to the second node.

[0041] In an embodiment of the present application, the updated first data pipeline may continue to use the identification information of the original first data pipeline, or may use new pipeline identification information, without limitation. If the updated first data pipeline uses new pipeline identification information, then each node that stores the identification information of the original first data pipeline may delete the identification information.

[0042] Through this implementation, the second functional network element updates the source node of the data pipeline and simultaneously updates the quality of service corresponding to the data pipeline and the collection policy information of the source node to ensure the policy requirements of the perception service.

[0043] The following third aspect is the steps executed by a source node (the first source node of the first data pipeline) of a data pipeline (such as the first data pipeline) corresponding to the perception service. For other source nodes of the first data pipeline or source nodes of other data pipelines, the method provided in the third aspect can be referred to for execution. The embodiment of this application no longer describes all source nodes in detail one by one.

[0044] In a third aspect, embodiments of the present application provide a method for determining a perception service policy. This method can be executed by a first source node of a first data pipeline, or by a chip, chip system, logic module, or software corresponding to the first source node of the first data pipeline, without limitation. Taking the first source node of the first data pipeline as an example, the method may include: the first source node obtaining perception service data based on the first source node's collection policy information; and then transmitting the perception service data and an indication of the second quality of service information of the first data pipeline.

[0045] In an embodiment of the present application, the first source node can be a policy execution function network element; the policy execution function network element can be independently deployed and serve the second service network element, or the policy execution function network element can be deployed in the second service network element; the second service network element can be but is not limited to: a terminal, or a wireless access network node, or an access and mobility management function, or a session management function, or a unified data storage repository, or a user plane function, or a perception data processing function.

[0046] In the above, the collection strategy information of the first source node may include but is not limited to one or more of the following:

[0047] The minimum perceptual signal used for perceptual measurement, the time interval or period for collecting data, and whether the collected data is real-time or non-real-time.

[0048] The indication information of the second quality of service may be identification information of the second quality of service (eg, identification ID, serial number, label, name, etc.), or the indication information of the second quality of service itself may be the quality of service of the first data pipeline, which is not limited to this.

[0049] In the present application scheme, the source node of the first data pipeline performs collection and obtains the data of the perception service based on its own corresponding collection strategy information, so as to effectively guarantee the collection strategy requirements of the perception service. And the first source node sends the data of the perception service and the indication information of the second service quality information of the first data pipeline together. After the receiving end (such as the destination node of the first data pipeline) receives the data of the perception service sent by the first source node and the indication information of the second service quality information, it can determine the service quality information corresponding to the data of the perception service through the indication information of the second service quality information, so as to allocate corresponding resources (such as delay, rate, priority, etc.) for subsequent processing / transmission of the data of the perception service, so as to further meet the policy requirements of the perception service. In addition, the receiving end may also use the indication information of the second service quality (such as QoS identifier) ​​to perform corresponding communication tunnel / wireless bearer mapping for the data of the perception service, and effectively complete the data transmission of the perception service.

[0050] For example, the first source node is a terminal device, the receiving end is an access network device, and the indication information of the second service quality information corresponding to the first data pipe is a QoS identifier; after the access network device receives the data and QoS identifier of the perception service sent by the terminal device, it will use the QoS identifier and service quality rules to map the data of the perception service from the first data pipe to the corresponding wireless bearer.

[0051] In one possible implementation, the data of the sensing service and the indication information of the second quality of service information of the first data pipe are located in the same data packet. With this implementation, the first source node can effectively send the indication information of the second quality of service information of the first data pipe when sending the data of the sensing service.

[0052] In the embodiments of the present application, the data for the perceived service and the indication of the second quality of service information of the first data pipeline may be located in the same message, and the type of the message is not limited. Furthermore, the data for the perceived service and the indication of the second quality of service information of the first data pipeline may be located in different data packets or messages, and this is also not limited. The first source node may select an appropriate transmission method based on actual needs.

[0053] In one possible implementation, the method further includes: the first source node receiving second quality of service information of the first data pipeline and collection policy information of the first source node from the second functional network element. In this implementation, the second quality of service information of the first data pipeline and the collection policy information of the first source node can be formulated and / or provided by the second functional network element.

[0054] In one possible implementation, when the first source node is deployed in the first wireless access network node, the first source node sends data of the perception service and indication information of the second service quality information of the first data pipe, including: mapping the first data pipe to the corresponding first communication tunnel; sending data of the perception service and indication information of the second service quality information of the first data pipe to the second wireless access network node or the core network network element through the first communication tunnel; wherein the second wireless access network node and the core network network element can be the destination node or intermediate node corresponding to the first data pipe.

[0055] In the embodiment of the present application, at least one communication tunnel (including the first communication tunnel) may be established in advance or in real time, without limitation. The first source node may match the corresponding communication tunnel according to the quality of service information of the first data pipeline.

[0056] Exemplarily, a quality of service QoS value or quality of service QoS range corresponding to at least one communication tunnel (including the first communication tunnel) is pre-set; if the quality of service QoS value of the first data pipeline is the quality of service QoS value corresponding to the first communication tunnel, or the quality of service QoS value of the first data pipeline is within the quality of service QoS range corresponding to the first communication tunnel, then it is determined that the communication tunnel matched by the first data pipeline is the first communication tunnel.

[0057] Through this implementation, when the first source node is an access network node and the destination node is also an access network node or a core network node, the first source node can perform tunnel mapping, that is, determine the communication tunnel corresponding to the first data pipeline, and then effectively send the data of the perceived service and the indication information of the second service quality information of the first data pipeline to the destination node through the communication tunnel.

[0058] In one possible implementation, the first communication tunnel may also correspond to a second data pipeline, which is used to transmit data of other perception services. Thus, in the embodiment of the present application, data pipelines of different perception services can be matched to different communication tunnels or to the same communication tunnel.

[0059] In one possible implementation, when the first source node is deployed in a terminal or terminal device, the first source node sends data of the perception service and indication information of the second service quality information of the first data pipe, including: the first source node maps the first data pipe to the corresponding first data radio bearer; through the first data radio bearer, the data of the perception service and indication information of the second service quality information of the first data pipe are sent to the wireless access network node; the wireless access network node can be the destination node or intermediate node corresponding to the first data pipe.

[0060] In the embodiment of the present application, at least one data radio bearer (including the first data radio bearer) may be established in advance or in real time, without limitation. The first source node may match the corresponding data radio bearer according to the quality of service information of the first data pipeline.

[0061] Exemplarily, a quality of service QoS value or quality of service QoS range corresponding to at least one data radio bearer (including a first data radio bearer) is pre-set; if the quality of service QoS value of the first data pipe is the quality of service QoS value corresponding to the first data radio bearer, or the quality of service QoS value of the first data pipe is within the quality of service QoS range corresponding to the first data radio bearer, it is determined that the data radio bearer matched by the first data pipe is the first data radio bearer.

[0062] In one possible implementation, the first data radio bearer may also correspond to a second data pipe, which is used to transmit data of other perception services. Thus, in the embodiment of the present application, data pipes of different perception services can be matched to different data radio bearers or to the same data radio bearer.

[0063] In a fourth aspect, an embodiment of the present application provides a communication system, which may include: a first functional network element and a second functional network element; wherein the first functional network element is used to obtain identification information of the perception service; determine policy information of the perception service based on the identification information of the perception service; the policy information of the perception service includes first service quality information of the perception service; and send the policy information of the perception service to the second functional network element; the second functional network element is used to determine information of at least one data pipeline corresponding to the perception service based on the policy information of the perception service, and determine the second service quality information corresponding to the at least one data pipeline.

[0064] In the embodiments of the present application, the first functional network element can be independently deployed in the communication network / communication system. The first functional network element can also be co-located with the policy control function network element. The first functional network element can also be a policy control function PDF network element. The second functional network element can be independently deployed in the core network, access network, or network management system of the communication network / communication system. The second functional network element can also be co-located with the first service network element. The first service network element can be, but is not limited to, a data controller, a perception service control function, a task anchor, or a task scheduler. This application does not limit the specific deployment, form, or number of the first functional network element and the second functional network element.

[0065] In one possible design, the first functional network element is also used to execute the method provided by any possible implementation method of the first aspect above; the second functional network element is also used to execute the method provided by any possible implementation method of the second aspect above.

[0066] In one possible design, the communication system may also include at least one destination node and at least one source node corresponding to at least one data pipeline of the perception service; any one of the at least one source node can be used to execute the method provided in the above third aspect and any possible implementation method of the third aspect.

[0067] In an embodiment of the present application, the source node and / or the destination node and / or the intermediate node can be a policy execution function network element; the policy execution function network element can be deployed independently and serve the second service network element, or the policy execution function network element can be deployed in the second service network element; the second service network element can be but is not limited to: a terminal, or a wireless access network node, or an access and mobility management function, or a session management function, or a unified data storage repository, or a user plane function, or a perception data processing function.

[0068] In the fifth aspect, an embodiment of the present application also provides a communication device, which can be used to execute the method of the first aspect. The device can be a first functional network element, or the device can be a component in the first functional network element (for example, a chip, or a chip system, or a circuit), or the device can be a logic module or software corresponding to the first functional network element, or the device can be a device that can be used in combination with the first functional network element.

[0069] In one possible implementation, the device may include a module or unit corresponding to each of the methods / operations / steps / actions described in the first aspect. The module or unit may be a hardware circuit, software, or a combination of hardware circuits and software. In one possible implementation, the device may include a processing unit (also referred to as a processing module) and a communication unit (also referred to as a communication module), wherein the communication unit may be used to perform the functions of receiving and / or sending, and the processing unit may be used to perform the method described in the first aspect or any possible implementation of the first aspect.

[0070] In the sixth aspect, an embodiment of the present application also provides a communication device, which can be used to execute the method of the second aspect. The device can be a first functional network element, or the device can be a component in the second functional network element (for example, a chip, or a chip system, or a circuit), or the device can be a logical module or software corresponding to the second functional network element, or the device can be a device that can be matched with the second functional network element.

[0071] In one possible implementation, the device may include a module or unit corresponding to each of the methods / operations / steps / actions described in the second aspect. The module or unit may be a hardware circuit, software, or a combination of a hardware circuit and software. In one possible implementation, the device may include a processing unit (also referred to as a processing module) and a communication unit (also referred to as a communication module), wherein the communication unit may be used to perform the functions of receiving and / or sending, and the processing unit may be used to perform the method described in the second aspect or any possible implementation of the second aspect.

[0072] In the seventh aspect, an embodiment of the present application also provides a communication device, which can be used to execute the method of the third aspect. The device can be a first source node, or the device can be a component in the first source node (for example, a chip, or a chip system, or a circuit), or the device can be a logic module or software corresponding to the first source node, or the device can be a device that can be used in conjunction with the first source node.

[0073] In one possible implementation, the device may include a module or unit corresponding to each of the methods / operations / steps / actions described in the third aspect. The module or unit may be a hardware circuit, software, or a combination of a hardware circuit and software. In one possible implementation, the device may include a processing unit (also referred to as a processing module) and a communication unit (also referred to as a communication module), wherein the communication unit may be used to perform the functions of receiving and / or sending, and the processing unit may be used to perform the method described in the third aspect or any possible implementation of the third aspect.

[0074] In the embodiment of the present application, the devices of other source nodes corresponding to the sensing service are similar to those of the first source node and will not be described in detail.

[0075] In an eighth aspect, an embodiment of the present application provides a device comprising: at least one processor and a communication interface; wherein the communication interface is used to communicate with other devices; the processor is used to run a set of programs so that the device can implement the method provided in the above-mentioned first aspect or any possible implementation manner thereof, or so that the device can implement the method provided in the above-mentioned second aspect or any possible implementation manner thereof, or so that the device can implement the method provided in the above-mentioned third aspect or any possible implementation manner thereof.

[0076] In the ninth aspect, an embodiment of the present application also provides a computer-readable storage medium, which stores a computer program or instruction. When the computer program or instruction is executed by a computer, it can implement the method provided by the above-mentioned first aspect or any possible implementation method thereof, or implement the method provided by the above-mentioned second aspect or any possible implementation method thereof, or implement the method provided by the above-mentioned third aspect or any possible implementation method thereof.

[0077] In the tenth aspect, an embodiment of the present application also provides a computer program product comprising a computer program or instructions, which, when run on a computer, enables the execution of the method provided in the above-mentioned first aspect or any possible implementation thereof, or enables the execution of the method provided in the above-mentioned second aspect or any possible implementation thereof, or enables the execution of the method provided in the above-mentioned third aspect or any possible implementation thereof.

[0078] In the eleventh aspect, an embodiment of the present application also provides a chip system, which includes a processor for supporting a first functional network element to implement the functions involved in the above-mentioned first aspect; or for supporting a second functional network element to implement the functions involved in the above-mentioned second aspect; or for supporting a first source node to implement the functions involved in the above-mentioned third aspect.

[0079] In one possible design, the chip system further includes a memory for storing necessary program instructions and data for execution by the loading device. The chip system can be composed of a chip or include a chip and other discrete devices.

[0080] It should be noted that the technical effects that can be achieved by any possible implementation method of the above-mentioned fourth to eleventh aspects or the fourth to eleventh aspects can be correspondingly described with reference to the technical effects that can be achieved by any possible implementation method of the above-mentioned first to third aspects or the first to third aspects; they will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0081] FIG1 is a schematic diagram of a data plane functional architecture;

[0082] FIG2A is a schematic diagram of a mapping relationship between 4G and 5G data channels and underlying bearers;

[0083] FIG2B is a schematic diagram illustrating a specific mapping relationship between data channels and underlying bearers in a 5G PCC architecture;

[0084] FIG3 is a schematic diagram comparing the strategy architecture proposed in an embodiment of the present application with the current architecture;

[0085] FIG4 is a schematic diagram of a possible, non-restrictive policy architecture applicable to a perception service according to an embodiment of the present application;

[0086] FIG5 is a schematic diagram of the position of a DFP protocol layer in a 6G data plane protocol stack provided in an embodiment of the present application;

[0087] FIG6 is a schematic diagram of a specific mapping relationship between UE1, RAN1 node, and PEF provided in an embodiment of the present application;

[0088] FIG7 is a flow chart of a method for determining a perception service strategy according to an embodiment of the present application;

[0089] FIG8A is a schematic diagram of a method flow diagram of implementation mode 1 provided in an embodiment of the present application;

[0090] FIG8B is a schematic diagram of a policy architecture of a perception service provided in an embodiment of the present application;

[0091] FIG9 is a schematic diagram of quality of service information allocation for three data pipes provided in an embodiment of the present application;

[0092] FIG10 is a schematic diagram of a source node update provided in an embodiment of the present application;

[0093] FIG11 is a schematic diagram of a communication device provided in an embodiment of the present application;

[0094] FIG12 is a schematic diagram of another communication device provided in an embodiment of the present application;

[0095] FIG13 is a schematic diagram of another chip device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0096] The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application. The terms used in the following embodiments are only for the purpose of describing specific embodiments and are not intended to limit the present application. As used in the specification and claims of this application, the singular expressions "one", "a kind of", "said", "above", "the" and "this" are intended to also include expressions such as "one or more", unless the context clearly indicates otherwise. In the embodiments of the present application, for the number of nouns, unless otherwise specified, it means "singular noun or plural noun", that is, "one or more". "At least one" means one or more, and "more" means two or more. "And / or" describes the association relationship of 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, where A and B can be singular or plural. The character " / " generally indicates that the related objects are in an "or" relationship. For example, A / B means: A or B. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c means: a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c can be single or plural.

[0097] References to "one embodiment" or "some embodiments" etc. described in this specification mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the phrases "in one embodiment", "in some embodiments", "in other embodiments", etc. that appear in different places in this specification do not necessarily all refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways, and the "implementation methods" in this specification are the same as above. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways. Words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions, and any embodiment or design described as "exemplary" or "for example" should not be interpreted as being more preferred or more advantageous than other embodiments or design schemes. The use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete way for easy understanding.

[0098] The multiple involved in the embodiments of the present application refers to greater than or equal to two. It should be noted that, in the description of the embodiments of the present application, the words "first", "second", "1", "2" (except for special cases used to represent numerical values) are used to distinguish the purpose of description, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying order. In addition, the term "used to indicate" mentioned in the description of the embodiments of the present application can include being used for direct indication and being used for indirect indication. When describing a certain indication information for indicating A, it can include that the indication information directly indicates A or indirectly indicates A, and it does not mean that the indication information must carry A. In addition, the steps corresponding to the dotted boxes or dotted lines in the drawings of the specification are represented as optional steps.

[0099] In the embodiments of the present application, "data pipe" and "pipeline" can be interchangeable. "QoS identifier" and "QoS value" can be interchangeable, or "QoS value" can be used as an example of "QoS identifier", which is not limited to this.

[0100] This application provides a method for determining a perceived service policy. To better understand the embodiments of this application, the following explains the relevant technical features and names involved in the embodiments of this application. It should be noted that these explanations are intended to make the embodiments of this application easier to understand and should not be regarded as limiting the scope of protection claimed by this application.

[0101] 1. Data plane functional architecture:

[0102] Building a standardized data service architecture based on the data plane can provide trusted data for intelligent services such as artificial intelligence (AI) and perception in communication networks. Figure 1 shows a data plane functional architecture. The data plane mainly includes data orchestration (DO), data agent (DA), trust anchor agent (TAA), and data storage function (DSF).

[0103] Data Orchestration (DO): Responsible for coarse-grained, non-real-time data orchestration tasks. Based on received data service requests, DO selects data agents (DAs) and orchestrates and manages DA functions. This allows DOs to dynamically establish an end-to-end (E2E) logical overlay data transmission network topology for data applications, orchestrate the flow of data between DAs within this network, and provide responses to requests back to applications.

[0104] The DO can also convert received data service requests into corresponding data pipeline construction requests and send them to the data controller DC. The DO can also be responsible for collaborating with other network services. For example, the computing power network service orchestrates computing power, while the DO orchestrates data. In some embodiments, the DO and DC can also be deployed on the same physical device.

[0105] In addition, DO has a built-in data security and privacy protection technology library, which includes differential privacy, homomorphic encryption, zero-knowledge proof and other counts, which are used to provide data security and privacy protection capabilities and empower DA with data protection technology on demand.

[0106] Data controller (DC): Responsible for fine-grained, real-time orchestration. The DC monitors and manages data access authorization (DA) in real time, assembling data pipelines based on DA capabilities and data service requirements. The collaboration between the DO and the DC enables data pipeline elasticity (the ability to quickly adapt to changing requirements) and programmability (the ability to flexibly configure the data pipeline).

[0107] Data agent (DA): Provides data collection, preprocessing, storage, and analysis. DAs can be deployed in network functions (NFs), radio access networks (RANs), transfer network (TN) nodes, terminals, and the operator's network operation, administration, and maintenance (OAM) system. They can also be deployed standalone.

[0108] In an embodiment of the present application, the DO / DC can select a data agent DA based on business needs and the capabilities reported by each DA, and orchestrate the DA to establish a dynamic data bearer for providing services for the business. A data bearer has a business identifier (ID) and a data service task identifier (DSID), and a data bearer can be composed of multiple data pipelines, each of which has its own ID, such as a data pipeline identifier (DPID). Each data pipeline is composed of a series of data processing units on demand and in sequence, and the output of the previous unit is the input of the next unit. Therefore, the data stream carried by the data bearer, from data collection, preprocessing, storage to application / analysis, can be output from the DA according to business needs, and provided by the DA to external applications through the service interface.

[0109] Data storage function DSF: DSF is an extension of DA storage, supporting the storage of streaming and batch type data; and supports distributed or centralized deployment.

[0110] Trusted Anchor Agent (TAA): Provides trusted services such as authentication, authorization, and accounting (AAA). It can store immutable data, such as public keys for terminals or network devices, short transactions, indexes, or critical data that cannot be tampered with. This data service architecture uses the trusted anchor agent to enable users to control their data, ensuring data reliability, auditability, and traceability, meeting compliance requirements such as the Personal Information Protection Law (PIPL) and the General Data Protection Regulation (GDPR).

[0111] 2. Policy and Charging Control (PCC) Architecture

[0112] The PCC architecture is a commonly used policy architecture in current mobile communication networks. The PCC architecture of 4G or LTE networks is centered around the PCRF, which assists with service data flow detection, policy implementation, and flow-based charging, ensuring reliable monitoring of services or use cases and the costs associated with each use case. The PCF is the core of the PCC architecture of 5G networks. It is an evolution of the 4G Policy and Charging Rules Function (PCRF), adding the ability to request and monitor service quality on a per-session basis. In addition to retaining session-based functionality, the PCF adds additional capabilities, including control of network slicing and new control mechanisms for terminal activities, such as roaming and mobility management.

[0113] The differences between the 4G and 5G policy architectures are as follows:

[0114] (1) The mapping relationship between data channels and underlying bearers is different: 4G has end-to-end (E2E) bearers, such as the evolved packet system (EPS) bearer, which implements end-to-end QoS. 5G's end-to-end E2E transmission is through QoS flows, and the transmission involves two levels of mapping, such as the mapping of the 5G next-generation user plane function tunnel (NG-U Tunnel) and the mapping of the radio bearer (RB).

[0115] 4G first-level mapping: There is a one-to-one correspondence between the underlying bearers of 4G. The sending end completes the mapping of data packets to the evolved packet system EPS bearers, that is, the association of data packets to bearers can be achieved. As shown in (1) in Figure 2A, for the mapping of uplink EPS bearers, between the user equipment UE and the base station eNode, the physical transmission channel of the EPS bearer is the radio bearer RB. The UE can map an uplink service (such as APP1) data to an RB through the uplink (UL) traffic flow template (TFT) (TFT is a set of packet filters (PF)) and send it to the base station eNodeB. The UE can also aggregate and map multiple uplink services (such as APP2 and APP3) data to an RB through the UL TFT (a set of multiple PFs) and send it to the base station eNodeB. Between the eNodeB and the serving gateway (S-GW), the physical transmission channel of the EPS bearer can be a dedicated bearer (a type of S1 bearer). The eNode can map the RBs one by one to the dedicated bearer and transmit them to the S-GW through the dedicated bearer. Between the S-GW and the packet gateway (PDN) The physical transmission channel for EPS bearers between the service provider gateway (P-GW) and the service provider gateway (S-GW) is the S5 / S8 bearer (GTP tunnel). The S-GW can map dedicated bearers one by one to S5 / S8 bearers and transmit them to the P-GW via the S5 / S8 bearer. For downlink EPS bearer mapping, the P-GW can use the downlink (DL) transport flow template (TFT) to map the data of a service (such as application APP1) to an S5 / S8 bearer. It can also use the DL TFT to aggregate and map the data of multiple services (such as APP2 and APP3) to an S5 / S8 bearer and send it to the S-GW. The S-GW then maps the S5 / S8 bearers one by one to dedicated bearers and sends them to the eNodeB. The eNodeB then maps the dedicated bearers one by one to RBs and sends them to the terminal.

[0116] Secondary mapping of 5G: The data packet transmitter maps the data packet to the QoS flow, and the QoS flow on the air interface side to the radio bearer; it can achieve end-to-end association between the data packet and the QoS flow; the mapping relationship between the data packet and the QoS flow, as well as the mapping relationship between the QoS flow and the radio bearer, are both N:1, where N is an integer greater than or equal to 1. As shown in (2) in Figure 2A, the mapping between the UE and the access network (AN) is the mapping between the QoS flow and the radio bearer, and the mapping between the access network AN and the user plane function (UPF) in the core network is the mapping between the radio bearer and the next generation user plane function tunnel (NG-U tunnel). The mapping relationship between the radio bearer and the next generation user plane function tunnel (NG-U tunnel) is M:1, where M is an integer greater than or equal to 1.

[0117] Figure 2B illustrates the specific policy mapping relationships for 5G. As shown in Figure 2B, the first-level mapping maps data packets to QoS flows, while the second-level mapping maps QoS flows on the air interface to data radio bearers (DRBs). The mapping between QoS rules and QoS flows on the UE, and between packet description rules (PDRs) and QoS flows on the user plane function (UPF), is an N:1 relationship (N is an integer greater than or equal to 1). A QoS flow identifier (QFI) can be added to the user plane protocol stacks of the UE and gNB. The receiver can read the value of this identifier to perform the mapping between QoS flows and DRBs.

[0118] (2) The service offloading mechanisms of 4G and 5G are different: a PDU session has only one N3 / N9 tunnel. The N3 / N9 interface uses the general packet radio service (GPRS) tunneling protocol (GTP) and only uses one tunnel endpoint identifier (TEID). If different QFIs are to be identified, a new field is required. The GTP tunnel of the user plane message of the N3 interface encapsulates the QFI parameter in the message header. The padding in the signaling file is divided into four bits, the first two bits are used to identify the uplink or downlink, and the last two bits are used to identify the QFI.

[0119] In the 4G strategy architecture, all data flows on the same bearer receive the same QoS guarantees (e.g., scheduling policy, buffer queue management, link layer configuration, etc.). Different QoS guarantees utilize different EPS bearer types. The 4G QoS architecture suffers from coarse QoS control granularity, high signaling overhead, and lengthy QoS control interaction processes, making it unsuitable for bursty or integrated services.

[0120] The 5G QoS architecture, with its fundamental granularity refined to QoS flows, offers a two-level mapping approach that allows the RAN a degree of freedom compared to 4G QoS control. The 5G QoS architecture enhances the flexibility and adaptability of service bearer control.

[0121] With the evolution of communication technologies, communication systems will provide not only connectivity services but also awareness services. However, the existing policy architecture cannot meet or support the policy requirements of awareness services. For example, the following reasons may exist:

[0122] (1) For perception services, the selection of source and destination nodes is more flexible, rather than being anchored at the UE or UPF, and may terminate at the RAN node. This brings challenges to the classification of perception services and policy execution, which is not supported by the current policy architecture.

[0123] (2) The current policy architecture is not service-aware. From the perspective of the terminal, QoS tags are added based on information such as 5-tuples from the upstream and downstream sources, and traffic is split. However, there is a lack of a global policy orchestration mechanism for services with multiple terminals or multiple sources.

[0124] (3) The current policy architecture lacks the ability to perceive and update policies in real time, especially on the RAN side. In 5G networks, QoS requirements are determined by the core network. Since the core network cannot obtain real-time information such as resource conditions and air interface changes on the access network side in a timely manner, the core network only formulates QoS policies and parameters based on user contract information and service requirements. This will lead to a mismatch between the service QoS requirements and the network's QoS capabilities, resulting in poor service experience and inefficient network operation.

[0125] In view of the above problems, the embodiments of the present application provide a policy architecture and technical solutions that can support or meet the policy requirements of the perception service. The policy architecture and technical solutions provided in the embodiments of the present application can be applied to various communication systems that have evolved after 5G, such as 6G communication systems. Similarly, the policy architecture and technical solutions provided in the embodiments of the present application can also be applied to 4G communication systems, such as long-term evolution LTE communication systems, and can also be applied to 5G communication systems, such as 5G new radio (NR) communication systems, without limitation. In addition, the policy architecture and technical solutions provided in the embodiments of the present application can also be applied to satellite communication systems, wherein the satellite communication system can be integrated with the above-mentioned communication system. Of course, the policy architecture and technical solutions provided in the embodiments of the present application can also be applied to other communication systems as long as the communication system has a policy formulation requirement. In addition, the communication system can be applicable to future-oriented communication technologies. The system described in the embodiments of the present application is to more clearly illustrate the policy architecture and technical solutions of the embodiments of the present application, and does not constitute a limitation on the policy architecture and technical solutions provided in the embodiments of the present application. It is known to those skilled in the art that with the evolution of network architecture, the policy architecture and technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0126] The following is an introduction to the policy architecture provided in the embodiments of the present application.

[0127] A policy architecture proposed in an embodiment of the present application adds policy services for security, data, sustainability and other businesses in addition to the existing connection policies. These policy services can be called policy services beyond connection or other names, which are not limited.

[0128] Figure 3 shows a policy architecture provided by an embodiment of the present application and several existing policy architectures. Figure 3 (1) shows the 3G policy architecture, and Figure 3 (2) shows the 4G policy architecture. It can be seen that the 3G and 4G policy architectures provide quality of service (QoS) management and billing. Figure 3 (3) shows the 5G policy architecture. It can be seen that the 5G policy architecture has added access management (AM) and UE access policy management. In short, 3G to 5G is mainly a policy architecture for connection, that is, a strategy for establishing a communication channel between the UE and the network anchor point (such as the public data network (PDN) gateway (GW) of 4G and the UPF of 5G).

[0129] (4) in Figure 3 shows a policy architecture that supports policy services beyond connections proposed in an embodiment of the present application. As shown in (4) in Figure 3, this policy architecture is a policy architecture that adds a policy architecture beyond connections on the basis of the connection policy architecture. The policy architecture beyond connections mainly includes functions such as policy control function (PCF), policy delivery function (PDF) and policy enforcement function (PEF). The original policy architecture including PCF, session management function (SMF) / access and mobility management function (AMF) and user plane function (UPF) can still be used to serve connection policies.

[0130] Figure 4 shows a possible, non-restrictive policy architecture applicable to sensing services provided by an embodiment of the present application (hereinafter referred to as the sensing policy architecture). As shown in Figure 4, the policy architecture includes unified data management (UDM), policy control function PCF, access and mobility management function AMF, session management function SMF, sensing service control function (SSCF), user equipment (UE), (radio) access network (R)AN), and sensing data processing function (SDPF).

[0131] In addition, in this policy architecture, new functions / network elements are added to provide policy services for perception services (equivalent to the functions / network elements of the policy services beyond the connection mentioned above), including: policy decision-making function for perception services, policy transmission function for perception services (such as PDF in Figure 4), policy execution function for perception services (such as PEF in Figure 4), and management function for perception services (such as service user management (xSSM) in Figure 4).

[0132] Among them, the policy decision-making function of the perception service can obtain user contract information of the perception service (service beyond connection) from the management function of the perception service, and then formulate the policy of the perception service based on the user contract information of the perception service, and then send the policy of the perception service to the policy transmission function of the perception service; the policy transmission function of the perception service can generate policy parameters of specific perception service dimensions based on the policy of the perception service and combined with the actual needs of the perception service, network status and other information, and then send the policy parameters of the specific perception service dimensions to the policy execution function of the perception service for execution.

[0133] In the above description, the policy decision-making function for the perception service can be integrated or built into the policy control function (PCF) in Figure 4, or it can be a separate NF or network element, without limitation. If the policy decision-making function for the perception service is integrated or built into the policy control function (PCF), it is equivalent to adding the policy decision-making function for the perception service on top of the existing functions of the PCF.

[0134] The following is a detailed introduction to each network element / function / device in the policy architecture shown in Figure 4.

[0135] The functions of UDM include: user contract context management, responsible for managing user / terminal contract data, and notifying the corresponding network elements when the contract data is modified.

[0136] The functions of AMF include: terminal access management and mobility management, terminal status maintenance, terminal reachability management, mobility management (MM), forwarding of non-access-stratum (NAS) messages, forwarding of session management (SM) N2 messages, etc.

[0137] The SMF's functions include allocating and releasing resources for terminal sessions. These resources include session quality of service (QoS), session paths, and forwarding rules. The SMF is responsible for selecting or reselecting UPFs, allocating Internet Protocol (IP) addresses, and establishing, modifying, and releasing bearers.

[0138] User equipment UE: User equipment can refer to a terminal device that can communicate with the core network through the access network AN. The terminal device can include an access terminal, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device. The access terminal can be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal in various communication networks evolved after 5G (such as a 6G communication network), etc.

[0139] The functions of (R)AN include: providing wireless connections for terminal devices and ensuring reliable transmission of uplink and downlink data of terminal devices.

[0140] In one possible scenario, an access 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 sixth-generation (6G) mobile communication system, a base station in a future mobile communication system, a satellite, an access point (AP) in a WiFi system, an integrated access and backhaul (IAB) node, a mobile switching center, or a network device in a non-terrestrial network (NTN) communication system, i.e., it can be deployed on a high-altitude platform or satellite. The access network device can be a macro base station, a micro base station, an indoor station, a relay node or a donor node, or a wireless controller in a cloud radio access network (CRAN) scenario. The access network device can also be a device that functions as a base station in device-to-device (D2D) communication, vehicle-to-vehicle communication, drone communication, or machine communication. Optionally, the access network device may also be a server, a wearable device, a vehicle or an onboard device, etc. For example, the access network device in vehicle to everything (V2X) technology may be a road side unit (RSU).

[0141] In another possible scenario, multiple access network devices collaborate to assist the terminal in achieving wireless access, and different access network devices respectively implement part of the functions of the base station. For example, the access 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 they 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 access 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 device in the radio access network RAN, or the CU can be divided into a device in the core network (CN), without limitation here.

[0142] 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 radio access network (open RAN, 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.

[0143] xSSM's functions include storing and managing service-aware user contract information, new user account opening requests, and service subscriptions.

[0144] Here, x can be used to represent a service, and x can be the name or code of the service, for example, x stands for Sensing, and xSSM represents user management of the sensing service (sensing SSM, SSSM).

[0145] In the embodiment of the present application, the xSSM can be combined with the unified data management function UDM, or the xSSM can be combined with other storage / management network elements, or the xSSM can be deployed independently, without limitation.

[0146] The functions of SSCF include: receiving capability registrations of perception entities and implementing control and orchestration of perception services. SSCF can communicate with other network functions NF through a service-based interface (SBI). In one possible implementation, when constructing a perception data service architecture based on the data plane functional architecture shown in Figure 1 to provide data services for perception services, SSCF can be equivalent to DO / DC in the data plane functional architecture. In the embodiment of the present application, PDF can be deployed or integrated in SSCF.

[0147] The functions of PDF include: generating policy parameters corresponding to specific perception service dimensions (such as each data pipeline) based on the perception service strategy from PCF and combining the actual needs of the perception service, network status and other information, and sending them to PEF for execution.

[0148] Exemplarily, the functions of PDF may include: 1. If PDF is set in DO / DC, DO / DC selects to establish data bearer for perception service according to the perception service policy of PCF, determines the source node and destination node, and PDF sends the establishment policy of the DPID pipe to be built to the PEF of the source node and destination node (uplink and downlink) respectively; 2. Generates data transmission strategy, collection strategy, billing method, access strategy when user arrears, incentive policy, etc. (the strategy of the business dimension is decided by PCF, PDF determines the management and strategy of each data pipeline DP, and sends it to PEF for execution); 3. PDF determines the service quality value of the perception service and sends it to the PEF of the source node and destination node corresponding to the data bearer of the perception service.

[0149] In an embodiment of the present application, PDF can be deployed separately or inside any one of the data controller (DC), the perception service control function SSCF, the task anchor / task scheduler (TA / TS), etc. It can also be combined with any one of the data controller (DC), the perception service control function (SSCF), the task anchor / task scheduler (TA / TS), etc. in the same device, without limitation.

[0150] In the above description, the DC (or DO), as a function in the data plane architecture, can be used to collect the capabilities reported by the underlying data agent (DA). Then, based on the service requirements and the reported capabilities of the DA, it selects the appropriate DA and orchestrates the data bearer, including the topology structure and node functions, to complete the service. In one possible implementation, the DC can be deployed in the access network (which can be called the data controller of the radio access network, RAN-DC) or in the core network (which can be called the data controller of the core network, CN-DC), without limitation.

[0151] TA / TS is a core function in the task architecture, which uses tasks as the central mechanism. Tasks can be defined and completed collaboratively through four elements: computing power, algorithms, data, and connections. TA / TS is used to decompose tasks into one or more subtasks and orchestrate and schedule the resources of these four elements to complete the task.

[0152] Exemplarily, after receiving the perception service decision rules from the PCF, the PDF directly generates specific parameters for the perception service dimension strategy according to the perception service decision rules of the PCF, or the PDF generates specific parameters for the perception service dimension strategy according to the perception service decision rules of the PCF and in combination with the orchestration and control requirements of the DC, SSCF, TA / TS, etc., and then sends it to the PEF. In addition, the PDF can be directly sent to an independent PEF, or transparently transmitted to a built-in PEF via a network element, for example, the PDF is transparently transmitted to the PEF built-in to the UPF via the SMF, the PDF is transparently transmitted to the PEF built-in to the RAN via the AMF, and the PDF is transparently transmitted to the built-in PEF such as the UE via the non-access layer NAS message, and there is no limitation on this. Among them, the PDF can be a RAN-DC or a CN-DC, so that the PDF can sense the changes in resources in combination with the real-time reporting information of the DA, and perform real-time policy updates, thereby realizing the integration and dynamic adaptation of the communication network and the perception service, and the QoS supports cross-layer and cross-domain connectivity.

[0153] The functions of the SDPF include: data plane functions for implementing sensing services, for example, the SDPF is used to process sensing data of the sensing services to obtain sensing results of the sensing services. In one possible implementation, the PEF can be deployed in the SDPF or integrated with the PEF.

[0154] The functions of PEF include: PEF receives policy parameters issued by PDF, and performs data collection and processing of perception services, etc.

[0155] In the embodiments of the present application, the PEF may be independently deployed, or may be built into or integrated into the UE, RAN node, UPF, SDPF, etc., without limitation.

[0156] In a possible implementation, when building a perception data service architecture based on the data plane functional architecture shown in FIG1 to provide data services for perception services, the SDPF may be equivalent to the DA in the data plane functional architecture.

[0157] PEF is executed on a service-by-service basis. A perception service is provided by a data bearer, identified by a data service task identifier (DSID). A data bearer can consist of one or more data pipes, each identified by a data pipeline identifier (DPID). The minimum granularity of PEF execution policy is the data pipe (or, in other words, the data pipe is the basic unit of PEF execution policy).

[0158] The data pipes (with the same DPID) between the source node and the destination node that have the same QoS requirements and belong to the same perceived service are the minimum granularity of QoS processing in the communication system of the present application embodiment. The QoS of the data pipe can be controlled by the PDF, can be pre-configured, or can be determined or established during the establishment process of the data pipe IP address (DPIP) or the modification process of the data pipe IP address (DPIP), without specific limitation.

[0159] In the embodiment of the present application, there are ground side mapping and air interface bearer mapping on the PEF side, as shown below:

[0160] 1. Ground-side mapping: Mapping of data pipelines to tunnels (at both ends of the ground). 2. Air interface bearer mapping: Mapping of data pipelines to data radio bearers (DRBs) (i.e., mapping between both ends of the air interface).

[0161] In an embodiment of the present application, when establishing a tunnel, the source end can add a QoS identifier / label to the corresponding protocol layer of the data based on the transport protocol. In addition, a terminal can have multiple DRBs to the air interface, and the correspondence between DRBs and services (or data pipes) can be 1:N.

[0162] Figure 5 shows the location of a data forwarding protocol (DFP) layer in the data plane protocol stack. As shown in Figure 5, the data plane protocol stack may include the data forwarding protocol (DFP) layer, the packet data convergence protocol (PDCP) layer, the radio link control (RLC) layer, the medium access control (MAC) layer, and the physical (PHY) layer. The DFP layer includes the following two functions:

[0163] Function 1: The DFP layer at the transmitting (or source) end can add a QoS identifier / label, such as a QoS ID, to an uplink or downlink data packet. Correspondingly, the DFP layer at the receiving (or destination) end can read the QoS identifier / label from the uplink or downlink data packet. Function 2: Map one or more data pipelines to a data radio bearer (DRB).

[0164] Exemplarily, for a downlink data packet, the source-side PEF sends the downlink data packet to the destination-side UE, or the source-side RAN1 node sends the downlink data packet to the destination-side RAN2 node, or the source-side NF1 node sends the downlink data packet to the destination-side NF2 node. The source-side PEF, the RAN1 node, or the DFP layer of NF1 adds a QoS identifier / label to the downlink data packet and sends the downlink data packet carrying the QoS identifier / label.

[0165] In addition, if the intermediate end to which the downlink data packet carrying the QoS identifier / label reaches is a RAN node, then secondary mapping (ie, ground-side mapping and air interface bearer mapping) is performed on the RAN side.

[0166] For uplink data packets, when the source UE sends an uplink data packet to the destination PEF, the UE adds a QoS identifier / label to the uplink data packet (or the header of the uplink data packet). When the source RAN node sends an uplink data packet to the PEF, the RAN node adds a QoS label / label to the uplink data packet (or the header of the uplink data packet).

[0167] In addition, if the intermediate end to which the uplink data packet carrying the QoS identifier / label arrives is a RAN node, then secondary mapping (ie, ground-side mapping and air interface bearer mapping) is performed on the RAN side.

[0168] In the embodiments of the present application, the data radio bearer may also be referred to as a data air interface bearer, or other names, without limitation. The above-mentioned ground-side mapping and air interface bearer mapping may also be named by other names, for example, air interface bearer mapping may be referred to as air interface mapping, etc., without limitation, and may be replaced accordingly depending on the application scenario, as long as the substantive content is expressed in the same way.

[0169] The functions of PCF include: providing user policy management, generating and managing user, session, and QoS flow processing policies, and making policy decisions for perception services.

[0170] Specifically, PCF not only has the functions of connection, billing and access (such as AM access management and UE access policy management) policy decision-making, but also adds the function of data (such as perception data) policy decision-making.

[0171] For example, as shown in Table 1, each policy content corresponds to a policy input source and a policy output. For each policy content, PCF can obtain the policy input information from the corresponding input source, perform policy calculation based on the policy input information, and determine the corresponding policy output.

[0172] For connection policies (such as connection + billing + access policy): The PCF can obtain the user's contract information from the UDM, calculate the quality assurance of the user's Internet access, and match the "rules". The "rules" will carry the QoS parameters of the user's access service determined by the PCF. The PCF can also dynamically adjust the policy parameters based on the real-time analysis of the network status by the network data analytics function (NWDAF) and send them to the SMF / AMF, UPF or UE.

[0173] For policies beyond connectivity (i.e., policies other than connection, billing, and access policies, such as policies for sensory services): the PCF can obtain the contract information of sensory service users from the xSSM (or SSSM), calculate the service quality indicators for the sensory services, and send them to the PDF. The PDF then generates specific policy parameters for the sensory service dimensions based on the actual needs of the sensory services and sends them to each PEF.

[0174] For example, the PDF issues policy parameters of the perception service dimension along with the match and action (M&A) mechanism. The PCF can also dynamically adjust the policy parameters from the perception service dimension based on the real-time analysis results of the network status by the NWDAF and send them to each PEF. In this application, the M&A mechanism refers to setting at least one collection / filtering condition in the data orchestration DO or data controller DC, as well as the corresponding actions for each collection / filtering condition, sending the M&A to the data processing node, and executing the corresponding action when the data packet matches a certain collection / filtering condition.

[0175] In an embodiment of the present application, for the perception service, after receiving the request input from the requester of the perception service, the PCF determines the execution scope area, collection strategy and service quality of the perception service. In a possible implementation method, for the perception service, the input source and output source of its strategy can be shown in Table 1. The PCF can obtain the input information of the perception corresponding strategy from the input source of the perception corresponding strategy (such as xSSM), perform strategy calculation based on the input information of the strategy, and determine the output of the perception corresponding strategy. The data bearer established for the perception service includes topological components such as source nodes, intermediate nodes, destination nodes, data pipelines, and the specific functions that each node can complete, such as analysis, storage, etc. These are determined by DC / SSCF (built-in or integrated PDF) and belong to the scope of business processing. Therefore, the PCF only specifies the regional scope of the source, the collection strategy (or collection settings) of the source, and the service quality of the business dimension (or transmission settings of the business dimension). And the destination information of the perception data is used as the content of the data pipeline transmission (business dimension) range.

[0176] After the sensing service is processed, the sensing result is fed back to the requester of the sensing service. If the requester is a terminal, the location calculated from the final sensing result is considered from the perspective of the existing connection, such as SDPF, to establish a connection, determine the connection strategy, and send the final sensing result to the terminal. If the requester is a third party, the network exposure function (NEF) can be used to send the result to the third party. This can be implemented by referring to the current connection strategy and will not be detailed here.

[0177] Table 1 is only shown as an example of part of the policy content. In fact, the policy architecture proposed in the embodiment of the present application may support more or less policy content, which will not be listed in detail here.

[0178] Figure 4 is only an example of a perception policy architecture provided by an embodiment of the present application. Compared with the perception policy architecture shown in Figure 4, the perception policy architecture provided by the embodiment of the present application may actually include more or fewer functional network elements, etc., and there is no limitation on this. The perception policy architecture provided by the embodiment of the present application can also be applied to other communication networks / systems / scenarios. If applied in other communication networks / systems / scenarios, all or part of the functional network elements shown in Figure 4 can be replaced accordingly. In addition, the functional network elements in the perception policy architecture of the embodiment of the present application can also be represented by other names, and there is no limitation on this.

[0179] Table 1

[0180] For example, based on Figure 4, Figure 6 further illustrates a specific schematic diagram of perception service data transmission in a perception policy architecture proposed in an embodiment of the present application. As shown in Figure 6, UE1 (built-in PEF) participates in three perception services (such as perception service 1, perception service 2, and perception service 3 in Figure 6) and serves as the source node of these three perception services. The perception data processing function SDPF1 (built-in PEF) serves as the destination node of perception service 1 and perception service 2, and the RAN1 node (built-in PEF) serves as the destination node of perception service 3. Starting from the left, the SSCF (with built-in PDF) sends a NAS message carrying the QoS values ​​corresponding to each service data pipe to the source node UE1, and sends the QoS values ​​corresponding to each service data pipe to the destination node (i.e., the RAN1 node and SDPF1). In addition, the SSCF also issues a QoS rule to UE1. UE1 identifies and distributes the collected data of the three perception services based on the QoS rule (equivalent to a packet filter), adds a 6QI (QoS value), and transmits the data flow of each service through the corresponding data pipe. UE1 performs air interface bearer mapping, mapping the data pipes of the three perception services to the corresponding two radio bearers. For example, the data pipes of perception service 1 and perception service 2 are mapped to the same radio bearer DRB1, and the data pipe of perception service 3 is mapped to another radio bearer DRB2. The data of the three perception services is transmitted to the RAN1 node via these two radio air interfaces (also called DRB1 and DRB2). Since the destination node of perception service 3 is RAN1, no further data of perception service 3 is transmitted. For DRB1 carrying the data of perception service 1 and perception service 2, RAN1 node determines the QoS profile according to the QoS profile. Profiles (QoS profiles include various quality of service parameters and are used by RAN nodes to perform air interface processing) are separated into two flows, namely the flows corresponding to perception service 1 and perception service 2. These two flows are mapped to the tunnels corresponding to the data pipes and sent to SDPF1 (equivalent to the destination nodes PEF for perception service 1 and PEF for perception service 2 being deployed in SDPF1). SDPF1 then uses the QoS value corresponding to the data pipe of perception service 1 to allocate transmission resources (such as bandwidth, latency, priority, etc.) to the flow of perception service 1, and uses the QoS value corresponding to the data pipe of perception service 2 to allocate transmission resources (such as bandwidth, latency, priority, etc.) to the flow of perception service 2.

[0181] Figure 6 is only used as an example to introduce the implementation of the transmission of perception service data between the source node and the destination node. For other service data transmission between the source node and the destination node or other service data transmission between the source node and the destination node, the above Figure 6 can be used for implementation, and no further description is given.

[0182] The above is a detailed introduction to the policy architecture proposed in the embodiment of the present application. The description of the policy architecture and business scenarios in the embodiment of the present application is to more clearly illustrate the technical solutions of the embodiment of the present application, and does not constitute a limitation on the technical solutions provided in the embodiment of the present application. It is known to those skilled in the art that with the evolution of network architecture and the emergence of new business scenarios, the policy architecture provided in the embodiment of the present application can also be applied.

[0183] Some scenarios in the embodiments of the present application are illustrated using the scenarios of 5G / 6G communication networks in wireless communication networks as examples. It should be noted that the solutions in the embodiments of the present application can also be applied to other wireless communication networks, and the corresponding names can also be replaced by the names of corresponding functions in other wireless communication networks.

[0184] The technical solution of this application is introduced below in conjunction with specific embodiments.

[0185] The embodiment of the present application provides a method for determining a perception service policy, which is applicable to but not limited to the policy architecture shown in Figure 4. The method can be executed by a first functional network element, a second functional network element, and an execution node (for example, a first source node); or the method can be executed by components (modules, chips, etc.) corresponding to the first functional network element, the second functional network element, and the execution node; or the method can be executed by a device that matches and uses the first functional network element, the second functional network element, and the execution node; it can be understood that the present application does not make specific restrictions on the specific structure of the execution subject of the method provided in the embodiment of the present application and the number of each execution subject. As long as it is possible to communicate according to the method provided in the embodiment of the present application by running a program that records the code of the method provided in the embodiment of the present application, the interaction between the first functional network element, the second functional network element, and the first source node will be used as an example for explanation. The order of the steps in the following processes is only an example. In actual applications, the order of execution of the steps in each process can be adjusted.

[0186] Please refer to FIG7 , the specific process of the method is as follows:

[0187] S701: The first functional network element obtains identification information of the perception service.

[0188] In the embodiment of the present application, the first functional network element can be deployed independently in the network, or the first functional network element can be co-located with the policy control functional network element in the network, or the first functional network element can be a policy control functional network element, which is not limited.

[0189] Exemplarily, the sensing service may include identification, speed measurement, distance measurement, target positioning, etc.

[0190] In one possible implementation, the identification information of the perception service may correspond to the user information of the perception service (equivalent to the fact that the identification information of the perception service and the user information of the perception service may be associated with each other); the user information of the perception service may include but is not limited to one or more of the user contract information of the perception service, the user account opening information of the perception service, and the service subscription information of the perception service.

[0191] For example, user contract information or service subscription information for the perception service may include perception service packages, perception service monthly packages, gift package discounts (e.g., number of discounts, duration, etc.), incentives for participating in the perception service, etc. User account opening information for the perception service may include user identity information, address information, user level information, etc.

[0192] In one possible implementation, the first functional network element obtaining identification information of the perception service and / or user information of the perception service may include: obtaining identification information of the perception service and / or user information of the perception service from a service user management network element of the perception service. The service user management network element of the perception service may be independently deployed in the network, or the service user management network element of the perception service may be co-located with a data storage network element, or the service user management network element of the perception service may be a data storage network element, for example, the data storage network element may be a unified data management (UDM) network element.

[0193] Exemplarily, the service user management (or service user management network element) of the sensing service may be expressed as xSSM, where x may represent the corresponding sensing service. For example, the user management of the sensing service may be expressed as (sensing SSM, SSSM).

[0194] S702: The first functional network element determines policy information of the perception service according to identification information of the perception service; the policy information of the perception service includes first quality of service information of the perception service.

[0195] Exemplarily, the user information of the perception service corresponding to the identification information of the perception service may be equivalent to the input information of the policy provided by the policy input source in Table 1. The policy information of the perception service may be equivalent to the output of the policy in Table 1.

[0196] In a possible implementation, the first quality of service of the perceived service may include, but is not limited to, one or more of the following:

[0197] The transmission delay of the perception service, the maximum bandwidth of the perception service, the guaranteed bandwidth of the perception service, the execution cycle of the perception service, the maximum data burst of the perception service, the number of nodes participating in the perception service, the time difference range of the synchronous arrival of the perception service data, the deterministic delay of the synchronous arrival of the perception service data, and the priority of the perception service.

[0198] For example, the transmission delay of a perception service may include the maximum or minimum transmission delay, computation delay, etc. supported for perception service data / information. The maximum bandwidth of a perception service may include the maximum bandwidth occupied by the perception service (e.g., maximum uplink bandwidth, maximum downlink bandwidth), bandwidth type, etc. The guaranteed bandwidth of a perception service may include the bandwidth required to ensure normal execution of the perception service, the minimum bandwidth required for the perception service, etc. The execution period of a perception service may include the maximum or minimum execution period of the perception service, etc. The number of nodes participating in the perception service may refer to the number of perception entities that can participate in the perception service. The time difference range for the synchronous arrival of perception service data may refer to the range of the delay difference between the perception data reported and collected by each perception entity and reaching the receiving end (e.g., SDPF). The deterministic delay for the synchronous arrival of perception service data may refer to the delay between the perception data reported and collected by each perception entity and reaching the receiving end (e.g., SDPF) within an allowable range. The priority of a perception service may include the priority for transmitting or processing the data / information of the perception service, etc.

[0199] In a possible implementation manner, the policy information of the awareness service may further include one or more of the execution scope information of the awareness service and the collection policy information of the awareness service.

[0200] In an embodiment of the present application, the execution scope of the perception service may be the network area where the perception service is executed, or the candidate node corresponding to the perception service, or the candidate data pipeline corresponding to the perception service, and no specific limitation is made to this. Furthermore, there is no limitation on the number of network areas where the perception service is executed, the number of candidate nodes corresponding to the perception service, and the number of candidate pipelines corresponding to the perception service. Therefore, the execution scope information of the perception service may include, but is not limited to, one or more of the information on the network area of ​​the perception service, the information on the candidate node, and the information on the candidate data pipeline. The display form of the execution scope information of the perception service may be information, a list, and the like.

[0201] Exemplarily, the execution scope information of the sensing service is a list of network areas where the sensing service is executed, and the list may include one or more areas.

[0202] In an embodiment of the present application, the collection policy information of the sensing service may be used to indicate the collection channel and collection method of the sensing service data / information. In one possible implementation, the collection policy information of the sensing service may include, but is not limited to, at least one of the following: a minimum sensing signal for sensing measurement, a time interval for collecting data, and whether the collected data is real-time or non-real-time.

[0203] In an embodiment of the present application, the policy information of the perception service determined by the first functional network element may also include one or more of the flow policy information of the perception service, the calculation policy information of the perception service, the security policy information of the perception service, etc., without limitation.

[0204] For example, the flow policy information for a perception service can provide the data bearer configuration strategy for the perception service. This can include topological information such as the source, destination, intermediate nodes, and data pipeline, as well as policies such as the bandwidth and latency required for data flow. The computation policy information for a perception service can include the algorithm or method used for computation, the participating nodes, and the computation time. The security policy information for a perception service can include the integrity of the perception service and whether privacy protection is implemented for the data / information of the perception service.

[0205] S703: The first functional network element sends policy information of the sensing service to the second functional network element. Correspondingly, the second functional network element receives the policy information of the sensing service.

[0206] In the embodiment of the present application, the second function network element can be independently deployed in the core network, access network, or network management system, or the second function network element can be co-located with the first service network element; wherein the first service network element can be, but is not limited to, any of the following:

[0207] Data controller DC (such as DC of access network or DC of core network), perception service control function, task anchor point, and task scheduling.

[0208] S704: The second functional network element determines information of at least one data pipeline corresponding to the perception service according to the policy information of the perception service, and determines second quality of service information corresponding to the at least one data pipeline.

[0209] In an embodiment of the present application, the at least one data pipe may be used to carry or transmit data and / or information of the perception service.

[0210] In one possible implementation, the policy information of the perception service also includes the execution scope information of the perception service; the method may also include: the second functional network element obtains the status information of the network and / or the status information of the node within the execution scope of the perception service based on the execution scope information of the perception service.

[0211] Then in S704, the second functional network element determines the information of at least one data pipeline corresponding to the perception service based on the policy information of the perception service, which may include: the second functional network element determines the information of the destination node and the information of the source node corresponding to the at least one data pipeline based on the policy information of the perception service, as well as the status information of the network and / or the status information of the node and / or the capability information of the node.

[0212] The second functional network element determines the second service quality information corresponding to the at least one data pipeline according to the policy information of the perceived service, which may include: the second functional network element determines the second service quality information corresponding to the at least one data pipeline according to the policy information of the perceived service, as well as the status information of the network and / or the status information of the node and / or the capability information of the node.

[0213] In an embodiment of the present application, the execution scope information of the perception service in the above S702 includes information about the network area of ​​the perception service. The second functional network element can obtain the network status information (e.g., one or more of the network load, link load, link robustness, etc.) and / or the status information of each node in the network area (e.g., one or more of the node load, whether the node is occupied, and node robustness, etc.) in the network area based on the information about the network area of ​​the perception service. Optionally, the second functional network element also obtains the capability information (e.g., one or more of the perception capability, computing capability, etc.) of each node in the network area, and the capability of each node can be reported to the second functional network element in advance by each node or known to the second functional network element, and there is no limitation on this.

[0214] In the case where the execution scope information of the perception service includes information about candidate nodes corresponding to the perception service, the second functional network element can obtain status information of these candidate nodes (for example, one or more of the load of the node, whether the node is occupied, and the robustness of the node) based on the information about the candidate nodes corresponding to the perception service. Optionally, the second functional network element also obtains capability information (for example, perception capability, computing capability, etc.) of these candidate nodes. Similarly, the capability information of each node can be reported in advance by each node to the second functional network element or known to the second functional network element, and there is no limitation on this.

[0215] In the case where the execution scope information of the perception service includes information about the candidate pipelines corresponding to the perception service, the second functional network element can obtain the status information of each node (for example, one or more of the source node, intermediate node, and destination node) corresponding to at least one candidate data pipeline, and / or the status information of each node, and / or the capability information of each node (the channel for obtaining the capability information of the node is the same as above) based on the information about the candidate pipelines corresponding to the perception service, and can also obtain the status information of these candidate data pipelines (for example, one or more of the load, robustness, transmission direction, etc. of the data pipeline).

[0216] In summary, the second functional network element can flexibly obtain the network status information and / or node status information within the execution scope of the perception service according to the actual policy information of the perception service, and no specific limitation is made to this.

[0217] In an embodiment of the present application, the information of each data pipeline may include information of at least one destination node and information of at least one source node. This embodiment of the present application describes the solution by taking a data pipeline corresponding to one destination node and one source node as an example. Optionally, the information of the data pipeline may also include information of at least one intermediate node and / or identification information of the data pipeline (e.g., DPID). Exemplarily, the node information may include the node's address information, the node's identification information, etc.

[0218] In an embodiment of the present application, the source node, the destination node or the intermediate node can be regarded as a policy execution function network element; the policy execution function network element can be independently deployed in the network and serve the second service network element, or the policy execution function network element can be deployed in the second service network element; wherein, the second service network element can be but is not limited to: terminal / terminal equipment, wireless access network node, access and mobility management function, session management function, unified data storage repository, user plane function, perception data processing function.

[0219] In this embodiment of the present application, the second quality of service information corresponding to each data pipeline may include, but is not limited to, at least one of the following: the data pipeline's transmission latency, the data pipeline's maximum bandwidth, the data pipeline's guaranteed bandwidth, the data pipeline's execution transmission period, the data pipeline's maximum data burst capacity, the number of nodes participating in the data pipeline's perception service, the data pipeline's data synchronization arrival latency difference range, the data pipeline's data synchronization arrival deterministic latency, and the data pipeline's priority. Compared to the first quality of service information for the perception service, the second quality of service information corresponding to each data pipeline contains more specific and detailed content or information.

[0220] S705: The second functional network element determines, based on the policy information of the sensing service, the collection policy information of the source node corresponding to each of the at least one data pipeline. S705 is an optional step. In some embodiments, S705 can be performed simultaneously with S704.

[0221] In one possible implementation, the policy information of the perception service also includes the collection policy information of the perception service; then the second functional network element executing S705 may include: the second functional network element determines the collection policy information of the source node corresponding to the at least one data pipeline according to the collection policy information of the perception service.

[0222] In one possible implementation, the second functional network element can determine the collection strategy information of the source nodes corresponding to the at least one data pipeline based on the collection strategy information of the perception service, as well as the status information of the network and / or the status information of each node and / or the capability information of each node within the execution scope of the perception service.

[0223] Exemplarily, the collection strategy information of the source node may include but is not limited to one or more of the following: a minimum sensing signal for sensing measurement, a time interval for the source node to collect data, and whether the source node collects data in real time or in non-real time.

[0224] In an embodiment of the present application, the second functional network element can also determine the flow policy information, calculation policy information, security policy information, etc. corresponding to each data pipeline based on the flow policy of the perception service, the calculation policy information of the perception service, the security policy information of the perception service, etc. in the policy information of the perception service, which will not be described in detail here.

[0225] In one possible implementation, the method may further include: the second functional network element sending, based on information about the source nodes corresponding to the at least one data pipeline, corresponding second quality of service information and source node collection policy information to the source nodes corresponding to the at least one data pipeline. Exemplarily, the source node information may include one or more of address information, identification information, and the like of the source node.

[0226] In one possible implementation, the method may also include: when the first source node of the first data pipeline moves out of the execution scope of the perception service, the second functional network element can determine the second node within the execution scope of the perception service, and use the second node as the source node of the first data pipeline to obtain an updated first data pipeline; wherein the first data pipeline is one of the at least one data pipeline corresponding to the perception service.

[0227] In one possible implementation, the method may also include: the second functional network element determines the service quality information corresponding to the updated first data pipeline and the collection strategy information of the second node; and sends the service quality information corresponding to the updated first data pipeline and the collection strategy information of the second node to the second node.

[0228] The following S706-S708 use the first source node of the first data pipeline as an example to describe the scheme executed by the source node. The first data pipeline can be one of the at least one data pipeline corresponding to the aforementioned perception service. Other source nodes of the first data pipeline or source nodes of other data pipelines can refer to the implementation of the first source node, and this application will not further describe each one in detail.

[0229] S706: The second functional network element sends the second quality of service information of the first data pipeline and the collection strategy information of the first source node to the first source node. Accordingly, the first source node receives the second quality of service information of the first data pipeline and the collection strategy information of the first source node.

[0230] S706 is an optional step.

[0231] S707: The first source node obtains data of the sensing service based on the collection strategy information of the first source node.

[0232] S708: The first source node sends data of the perception service and indication information of the second service quality information of the first data pipeline.

[0233] In an embodiment of the present application, the indication information of the second quality of service information of the first data pipe (for example, one or more of an identifier, label, name, etc. of the quality of service information). The data of the perception service and the indication information of the second quality of service information of the first data pipe can be located in the same data packet or message and sent, or can be located in different data packets / messages and sent, without limitation. In addition, the indication information of the quality of service information of the first data pipe can be a value corresponding to the quality of service information of the first data pipe, or can be identification information (for example, an identification ID, label, name, etc.) used to identify the quality of service information of the first data pipe, which is also not specifically limited.

[0234] In the embodiment of the present application, the first source node may send the data of the perceived service and the indication information of the second quality of service information of the first data pipe including but not limited to the following implementations:

[0235] Implementation method 1: When the first source node is deployed in a first radio access network node, the first source node sending data of the perceived service and indication information of the second quality of service information of the first data pipeline may include: sending the data of the perceived service and indication information of the second quality of service information of the first data pipeline to a second radio access network node or a core network element via a first communication tunnel. The second radio access network node (or core network element) may be a destination node or an intermediate node corresponding to the first data pipeline.

[0236] In the embodiment of the present application, at least one communication tunnel (including the first communication tunnel) may be pre-established or established in real time, without limitation. The first source node may match the corresponding communication tunnel based on the quality of service information of the first data pipeline, for example, the first source node may map the first data pipeline to the corresponding first communication tunnel.

[0237] Exemplarily, at least one communication tunnel (including a first communication tunnel) is pre-set, and the at least one communication tunnel corresponds to a quality of service QoS value or a quality of service QoS range respectively); if the quality of service QoS value of the first data pipeline is the quality of service QoS value corresponding to the first communication tunnel, or the quality of service QoS value of the first data pipeline is within the quality of service QoS range corresponding to the first communication tunnel, then it is determined that the communication tunnel matched by the first data pipeline is the first communication tunnel.

[0238] In a possible implementation, the first communication tunnel may also correspond to a second data pipeline, and the second data pipeline is used to carry / transmit data of other services.

[0239] In the embodiment of the present application, the data pipes of the same service may correspond to the same communication tunnel or to different communication tunnels, and the data pipes of different services may correspond to different communication tunnels or to the same communication tunnel, which is not limited to this.

[0240] Implementation method 2: When the first source node is deployed in a terminal / terminal device, the first source node sending data of the perceived service and indication information of the second quality of service information of the first data pipeline may include: sending the data of the perceived service and indication information of the second quality of service information of the first data pipeline to a radio access network node via a first data radio bearer. The radio access network node may be a destination node or an intermediate node corresponding to the first data pipeline.

[0241] In the embodiment of the present application, at least one data radio bearer (including the first data radio bearer) may be pre-established or established in real time, without limitation. The first source node may match the corresponding data radio bearer based on the quality of service information of the first data pipe. For example, the first source node may map the first data pipe to the corresponding first data radio bearer.

[0242] Exemplarily, at least one data radio bearer (including a first data radio bearer) is pre-set, and the at least one data radio bearer corresponds to a quality of service QoS value or a quality of service QoS range, respectively; if the quality of service QoS value of the first data pipe is the quality of service QoS value corresponding to the first data radio bearer, or the quality of service QoS value of the first data pipe is within the quality of service QoS range corresponding to the first data radio bearer, then it is determined that the data radio bearer matched by the first data pipe is the first data radio bearer.

[0243] In a possible implementation, the first data radio bearer may also correspond to a second data pipe, and the second data pipe is used to carry / transmit data of other services.

[0244] In the embodiment of the present application, the data pipe of the same service may correspond to the same data radio bearer or to different data radio bearers, and the data pipes of different services may correspond to different data radio bearers or to the same data radio bearer, which is not limited to this.

[0245] In a possible implementation, the method may further include: when the first source node of the first data pipeline leaves or is not within the execution scope of the perception service, the second functional network element determines a second node within the execution scope of the perception service; and uses the second node as the source node of the first data pipeline to obtain an updated first data pipeline; the first data pipeline is any one of the at least one data pipeline.

[0246] In one possible implementation, the method may also include: the second functional network element determines the second service quality information corresponding to the updated first data pipeline and the collection strategy information of the second node; and sends the second service quality information corresponding to the updated first data pipeline and the collection strategy information of the second node to the second node.

[0247] In the embodiment of the present application, the identification information of the updated first data pipeline can be the identification information of the first data pipeline, or the identification information of a new data pipeline, which is not limited.

[0248] In summary, an embodiment of the present application provides a method for determining a perception service policy, the method comprising: a first functional network element obtaining identification information of a perception service; then, based on the identification information of the perception service, determining policy information for the perception service; the policy information for the perception service including first quality of service information of the perception service; and the first functional network element then sending the policy information for the perception service to a second functional network element. It can be seen that in this method, the first functional network element determines the policy information for the perception service from a service dimension to provide quality of service information for the perception service, and the method is applicable to evolving communication networks and can effectively meet the policy requirements of the perception service.

[0249] Based on the method for determining the perception service policy described in FIG. 7 , several specific implementation methods are further described below.

[0250] Implementation method one:

[0251] In the first embodiment, the process of determining the policy of the perception service is described in detail based on the method described in FIG7 . Referring to FIG8A , the process of determining the policy of the perception service is as follows:

[0252] S801A: The user requester performs user contract registration and service subscription with the SSSM.

[0253] The user requester registers with the SSSM and subscribes to the sensing service, and obtains authorization from the perceiver.

[0254] Exemplarily, the SSSM is a function or network element that provides user management services for the sensing service.

[0255] Exemplarily, the process of a user requester registering with SSSM and subscribing to a service may include the following steps:

[0256] Step 1: The user requester sends a user account opening request message to SSSM;

[0257] Step 2: SSSM verifies user qualifications and creates a customer;

[0258] Through this step 2, SSSM can generate user level information.

[0259] Step 3: SSSM sends confirmation information of the account opening request to the user requester;

[0260] Step 4: The user requester sends a sensing service subscription request message to the SSSM;

[0261] Step 5: SSSM generates the ID of the perception service (or the ID of the perception business), the perception business type, the region, etc., and the perception service policy based on the request information of the perception service subscription; wherein the perception service policy may include: the regional information of the perception service execution (such as the region where the entity that can provide the perception service is located, etc.), the transmission policy (such as the maximum bandwidth, guaranteed bandwidth, maximum repetition period, minimum delay, etc.), the collection policy (such as the number of measured perception signals, the maximum time interval, real-time / non-real-time), the flow policy (such as the source, destination, intermediate node, data pipeline and other topological information, as well as the bandwidth and delay required for the data to flow therein) one or more.

[0262] Step 6: SSSM sends confirmation information of the perception service subscription request to the user requester to inform the user requester that the perception service subscription is successful.

[0263] S801A belongs to the initial stage. In the initial stage, each sensing entity needs to report its own sensing capability to the SSCF.

[0264] In the first implementation mode, S801A can also be completed offline.

[0265] S802A: The user requester sends a request message for sensing the service to the SSCF. Correspondingly, the SSCF receives the request message for sensing the service.

[0266] Optionally, the request information of the perception service may include the ID of the perception service (an example of identification information of the perception service in the solution described in FIG. 7 ).

[0267] S803A: SSCF sends a request message for user contract information to SSSM. Correspondingly, SSSM receives the request message for user contract information.

[0268] Optionally, the request information for the user contract information may include the ID of the sensing service, or information of the user requester (eg, the user requester's name or ID).

[0269] S804A: SSSM sends the subscription information of the user requester to SSCF. Correspondingly, SSCF receives the subscription information of the user requester.

[0270] The SSCF obtains the contract information (perception service subscription information) of the user requester and may also obtain the location information carried by the user requester when he / she goes online.

[0271] S805A: The SSCF sends user information to the PCF (an example of user information of the perception service in the solution described in FIG. 7 ).

[0272] The user information includes the contract information of the user requester (such as the perception service subscription information) and the location information carried by the user requester when going online.

[0273] S806A: The PCF generates a policy for the perception service based on the user information (an example of the policy information for the perception service in the solution described in FIG. 7 ).

[0274] The policy for the perception service generated by PCF may include: the collection area of ​​perception service data (an example of the execution scope information of the perception service in the scheme described in Figure 7 above), the collection settings of the perception entity (an example of the collection strategy information of the perception service in the scheme described in Figure 7 above), and one or more parameter settings of the data pipeline for transmitting perception data (an example of the first service quality information of the perception service in the scheme described in Figure 7 above).

[0275] Among them, the collection area of ​​perception service data (an example of the execution scope information of the perception service in the solution described in Figure 7 above) may include one or more of the areas where the perception entities that can provide services are located, accuracy-limited areas, prohibited areas, etc.

[0276] The collection settings of the perception entity (or data source) (an example of the collection strategy information of the perception service in the scheme described in Figure 7 above) may include one or more of the minimum / maximum number of perception signals used for perception measurement, the minimum / maximum time interval for collecting data, whether the collected data is real-time or non-real-time, etc.

[0277] The parameter settings of the data pipeline used to transmit data (an example of the first service quality information of the perception service in the scheme described in Figure 7 above) may include one or more of the maximum bandwidth (or total bandwidth) of data transmission, guaranteed bandwidth, cycle of perception detection or data collection, minimum delay of data transmission, etc.

[0278] S807A: The PCF sends the policy of the sensing service to the SSCF. Correspondingly, the SSCF receives the policy of the sensing service.

[0279] As shown in Figure 8B , the SSCF is equivalent to the DO / DC in the data plane functional architecture. The PDF can be integrated or built into the SSCF, and the PEF can be integrated or built into the SDPF, RAN nodes (e.g., RAN1, RAN2, and RAN3), and UEs (e.g., UE1 and UE2). The SDPF can collect perception data from other nodes (e.g., UE1, UE2, and RAN3), process it to obtain perception results, and then report them uniformly.

[0280] S808A: SSCF selects the source node RAN, UE and destination node SDPF according to the policy of the perceived service, and determines the QoSS corresponding to at least one data pipe. Each QoSS includes the service quality of the data pipe and the collection policy of the corresponding source node.

[0281] It should be noted that in the implementation of this application, the quality of sensing service (QoSS) corresponding to the data pipeline may include the quality of service QoS of the data pipeline and the collection strategy of the corresponding source node as an example for introduction. In another possible implementation, the QoSS corresponding to each data pipeline is / includes the quality of service QoS of the data pipeline, but does not include the collection strategy corresponding to the data pipeline. Then, the SSCF not only needs to send the corresponding QoSS of the data pipeline to each source node, but also needs to send the corresponding collection strategy to each source node, or the SSCF carries the quality of service QoS of each data pipeline and the collection strategy of the corresponding source node in the same message and sends it to the corresponding source node.

[0282] In one possible implementation, the SSCF (with an integrated or built-in PDF) selects appropriate source nodes (such as RAN nodes, UEs) and destination nodes (such as SDPFs) based on network status information and status information and / or capability information of each node within the execution scope of the perceived service, designs at least one data pipeline, determines the source nodes and destination nodes (which may also include intermediate nodes) corresponding to each data pipeline, and the QoS value of each data pipeline, and also determines the collection strategy of the source node (such as RAN node, UE) corresponding to each data pipeline.

[0283] For example, the SSCF (integrated or built-in PDF) can orchestrate and generate data bearers and specific policy parts based on the perception service data collection area provided by the PCF and the perception capability information reported by each perception entity in the collection area, which may include the following:

[0284] 1) Select the perception entity (i.e., select the source node, destination node, etc.); 2) Transmission settings in the business dimension (i.e., determine the QoSS corresponding to the data pipeline), such as determining the number of data pipelines, the identifier of each data pipeline (DPID), and the transmission parameter value corresponding to each data pipeline (e.g., the QoS value corresponding to each data pipeline). The source node and destination node corresponding to each data pipeline can also be selected from the perception entity; 3) Determine the specific collection settings for each perception entity (i.e., determine the collection strategy for the source node corresponding to each data pipeline), which can include measuring one or more of the number of perception signals, the collection time interval, and whether the collection is real-time / non-real-time.

[0285] For example, as shown in Figure 8B , for sensing service 1 (identified as DSID1), the SSCF (with an integrated or built-in PDF) selects appropriate source nodes (e.g., UE1, UE2, RAN3 node) and destination nodes (e.g., SDPF) based on the sensing service data collection area in the sensing service policy provided by the PCF and the sensing capability information reported by each sensing entity within the collection area. It also determines three data pipelines, identified as DPID1, DPID2, and DPID3. The data pipeline identified as DPID1 (UE1—RAN1 node—SDPF) corresponds to the source node UE1, the intermediate node RAN1 node, and the destination node SDPF. The data pipeline identified as DPID2 (UE2—RAN2 node—SDPF) corresponds to the source node UE2, the intermediate node RAN2 node, and the destination node SDPF. The data pipeline identified as DPID3 (RAN3 node—SDPF) corresponds to the source node RAN3 node and the destination node SDPF. SSCF (integrated or built-in PDF) can also determine the corresponding service quality QoS values ​​for the three data pipelines based on the service quality QoS values ​​of the perception services provided by PCF, and can determine the collection settings (or collection strategies) of each source node (such as UE1, UE2, RAN3 nodes) based on the collection settings (or collection strategies) of the perception services provided by PCF.

[0286] PCF is an example of the first functional network element in the solution described in FIG. 7 , and SSCF is an example of the second functional network element in the solution described in FIG. 7 .

[0287] S809A: SSCF (built-in or integrated with PDF) sends QoSS of the corresponding data pipe to RAN, UE, and SDPF respectively. Each QoSS includes the QoS value of the corresponding data pipe and the collection policy of the corresponding source node.

[0288] For example, the SSCF (with built-in or integrated PDF) can, based on the M&A mechanism, deliver the quality of service (QoS) of each data pipeline to the corresponding source node and destination node (e.g., SDPF), deliver the acquisition policy of the source RAN node to the RAN node, and deliver the acquisition policy of the source UE to the UE. Optionally, the SCCF (with built-in or integrated PDF) can also deliver the QoSS of each data pipeline to at least one corresponding intermediate node.

[0289] For example, as shown in Figure 8B, SSCF (integrated or built-in PDF) determines that the data pipe identified as DPID1 corresponds to QoSS1 (including the quality of service QoS value 1 of the data pipe of DPID1 and the policy 1 of the source node UE1); SSCF (integrated or built-in PDF) determines that the data pipe identified as DPID2 corresponds to QoSS2 (including the quality of service QoS value 2 of the data pipe of DPID2 and the collection policy 2 of the source node UE2); SSCF (integrated or built-in PDF) determines that the data pipe identified as DPID3 corresponds to QoSS3 (including the quality of service QoS value 3 of the data pipe of DPID3 and the collection policy 3 of the source node RAN3).

[0290] Furthermore, the SSCF (integrated or built-in PDF) sends the QoS value 1 of the data pipe of DPID1 to UE1 and RAN1 nodes respectively, and also sends the collection policy 1 to UE1. The SSCF (integrated or built-in PDF) sends the QoS value 2 of the data pipe of DPID2 to UE2 and RAN2 nodes respectively, and also sends the collection policy 2 to UE2. The SSCF (integrated or built-in PDF) sends the QoS value 3 and collection policy 3 of the data pipe of DPID3 to RAN3 respectively. Since the SDPF is the common destination node for these three data pipes, the SSCF (integrated or built-in PDF) sends the QoS value 1 of the data pipe of DPID1, the QoS value 2 of the data pipe of DPID2, and the QoS value 3 of the data pipe of DPID3 to the SDPF.

[0291] Optionally, the SSCF (integrated or built-in PDF) can also send the identifier DPID1 of the corresponding data pipe to the UE1 and RAN1 nodes respectively, send the identifier DPID2 of the corresponding data pipe to the UE1 and RAN2 nodes respectively, send the identifier DPID3 of the corresponding data pipe to the RAN3 node, and send the identifiers DPID1, DPID2, and DPID3 of these three data pipes to the SDPF.

[0292] In this application, SSCF (integrated or built-in PDF) sends QoSS to the nodes corresponding to each data pipeline. The collection strategy of the source node and the time sequence of the identification of the data pipeline can be flexibly set without specific limitation.

[0293] S810A: The RAN node obtains the perception data packet 1 according to the RAN collection policy, and adds an ID / tag of the QoS value to the packet header of the perception data packet 1.

[0294] S811A: The UE obtains the perception data packet 2 according to the UE collection strategy, and adds an ID / label of the QoS value to the packet header of the perception data packet 2.

[0295] S810A and S811A can be executed synchronously or asynchronously, and there is no restriction on the order of execution.

[0296] S812A: The RAN node performs tunnel mapping and sends the sensing data packet 1 (carrying the ID / label of the QoS value) to the SDPF through the corresponding tunnel.

[0297] S813A: The UE performs DRB mapping and sends the sensing data packet 2 (carrying the ID / label of the QoS value) to the RAN through the corresponding DRB.

[0298] S812A and S813A may be executed synchronously or asynchronously, and there is no specific restriction on the order of execution.

[0299] S814A: The RAN node performs tunnel mapping and sends the sensing data packet 2 (carrying the ID / label of the QoS value) to the SDPF through the corresponding tunnel.

[0300] S815A: SDPF processes the sensing data according to sensing data packet 1 and sensing data packet 2, and obtains a sensing result.

[0301] For example, as shown in Figure 8B, after UE1 performs a sensing task based on QoSS1 corresponding to the data pipe of DPID1, it obtains sensing data packet 1 and adds the QoSS1 identifier / tag to the packet header of sensing data packet 1. UE1 performs air interface mapping on sensing data packet 1 (carrying the QoSS1 identifier / tag) and sends it to the RAN1 node. RAN1 then performs tunnel mapping on sensing data packet 1 and sends it to the SDPF. UE2 performs a sensing task based on QoSS2 corresponding to the data pipe of DPID2 and obtains sensing data packet 2. It adds the QoSS2 identifier / tag to the packet header of sensing data packet 2. UE2 performs air interface mapping on sensing data packet 2 (carrying the QoSS2 identifier / tag) and sends it to the RAN2 node. RAN2 then performs tunnel mapping on sensing data packet 2 and sends it to the SDPF. RAN3 performs a sensing task based on QoSS3 corresponding to the data pipe of DPID3 and obtains sensing data packet 3. It adds the QoSS3 identifier / tag to the packet header of sensing data packet 3. RAN3 performs tunnel mapping on sensing data packet 3 (carrying the QoSS3 identifier / tag) and sends it to the SDPF.

[0302] The SDPF may process the sensing data according to the sensing data packet 1, the sensing data packet 2, and the sensing data packet 3, and obtain a sensing result.

[0303] Furthermore, the SDPF sends the sensing results (such as measurement data or raw data) to the application function AF, which then forwards them to the user requester. In addition, the PDF in the PCF and / or SSCF can also dynamically update the policy based on the sensing results.

[0304] In addition, after confirming that the sensing task is completed, the SSCF can delete the data carrying information.

[0305] In the above-mentioned first embodiment, a policy architecture proposed in the embodiment of the present application is applied to the network scenario of the perception service, which can effectively formulate policies for the perception service and effectively implement the policies of the perception service.

[0306] Implementation Method 2: Based on the solutions described in Figures 7 and 8A above, and in conjunction with the example in Figure 8B, this section describes how the PDF in the SSCF determines the specific policy information corresponding to each node and data pipeline based on the policy information of the perception service provided by the PCF. Taking Perception Service 1 as an example, Perception Service 1 is used to represent a perception service and is identified as DSID1. The network topology corresponding to Perception Service 1 can be shown in Figure 9. The PDF in the SSCF may determine or generate the specific policy information for each node and data pipeline, including the following:

[0307] 1) Select appropriate perception entities and design data pipelines.

[0308] For example, as shown in Figure 9, the PDF in the SSCF selects the perception entities UE1, UE2, and RAN3 nodes, and designs three data pipelines. The corresponding identifiers of these three data pipelines are: DPID1, DPID2, and DPID3, and UE1, UE2, and RAN3 nodes are used as the source nodes (or data sources) corresponding to the three data pipelines.

[0309] 2) Set the transmission parameters of each data pipeline.

[0310] For example, as shown in FIG9 , the minimum number of perception entities determined by the PDF in the SSCF is 3. If the QoSS value of perception service 1 (perception service 1 is used to represent a certain perception service) provided by the PCF is 105, the PDF in the SSCF can determine that the QoSS values ​​of the three data pipes are 105 respectively based on the QoSS value 105 of perception service 1.

[0311] For example, a predefined QoSS value of 105 indicates a corresponding bandwidth of 10M and a latency of 10ms; a predefined QoSS value of 90 indicates a corresponding bandwidth of 100M and a latency of 1ms.

[0312] When the QoSS value of perception service 1 is 105, it means that the bandwidth of perception service 1 provided by PCF is 10M and the latency is 10ms. Then, the PDF in SSCF can determine that the data pipes of DPID1 and DPID2 are 3M and the data pipe of DPID3 is 4M respectively based on the bandwidth of perception service 1 of 10M. In addition, the PDF in SSCF determines that the synchronization delay difference of data from UE1, UE2, and RAN3 nodes reaching SDPF does not exceed 10ms.

[0313] 3) Set the collection strategy corresponding to each data pipeline.

[0314] For example, setting the collection strategy corresponding to each data pipeline may include the following:

[0315] Set the content collected at each perception entity (such as UE1, UE2, RAN3 node); for example, the collected content may include collecting part or all of the surrounding physical environment information (such as the surrounding physical environment information used to build a virtual environment), surrounding channel information (such as surrounding channel information used to assist communication, etc.), and collecting the movement behaviors and heartbeats of people or animals.

[0316] Each sensing entity (such as UE1, UE2, and RAN3 node) is set to collect sensing signals (such as I / Q path signals) in real time.

[0317] Set the collection interval of each sensing entity. For example, set the collection interval of UE1 and UE2 to 100 ns respectively, and the collection interval of RAN3 node to 10 ns.

[0318] Through the second implementation method, it can be seen that the PDF in the SSCF can flexibly topology or arrange the data pipeline for transmitting perception data based on the perception business policy, and can also formulate more detailed policy information for the data pipeline, thereby meeting flexible policy requirements.

[0319] Implementation Method 3: Based on the solutions described in Figures 7 and 8A above, and in conjunction with the example of Figure 8B, this section describes how to update the policy information corresponding to the data pipeline in the PDF of the SSCF when the location of the perception entity corresponding to the data pipeline changes. Taking Perception Service 1 as an example, Perception Service 1 is used to represent a certain perception service and is identified as DSID1. The network topology corresponding to Perception Service 1 can be shown in Figure 10. How to update the policy information corresponding to the data pipeline in the PDF of the SSCF when the location of the perception entity corresponding to the data pipeline changes may include the following:

[0320] The policy information of perception service 1 requires that the minimum number of perception entities is 3, and the service bandwidth remains unchanged. If the perception entity UE1 corresponding to the current DPID1 data pipe moves out of the range of the RAN1 node, for example, UE1 switches from the RAN1 node to another RAN node, then it is necessary to re-determine a perception entity (such as UE3) through the PDF in the SSCF to replace UE1, and update the policy information of the DPID1 data pipe to meet the policy requirements of perception service 1.

[0321] Exemplarily, the process of the PDF in the SSCF updating the policy information of the data pipe of DPID1 may include the following:

[0322] (1) When the sensing entity UE1 switches from the RAN1 node to another RAN node, the PDF in the SSCF can reselect another UE (assuming it is UE3) under the management of the RAN1 node to replace UE1 according to policy requirements, and use the new identifier DPID4 to replace DPID1 to identify the updated data pipe. The updated data pipe (DPID4) can be seen in Figure 10. Alternatively, the SSCF can use the original DPID1 to identify the updated data pipe.

[0323] In this step, if the perception entity UE1 moves and switches to another RAN node (or if the perception entity UE1 moves out of the execution area / range of the perception service 1), then UE1 can report this situation to the SSCF through the RAN1 node. For example, the RAN1 node reports indication information to instruct UE1 to move out of the RAN1 node; or the RAN1 node reports the measurement report of UE1 to notify the SSCF that UE1 has switched. The above-mentioned method of notifying the SSCF to reselect other UEs under the management of the RAN1 node is an example. The specific method of making the SSCF aware of the change in UE1's location and the need to update the perception entity is not limited, and the existing switching process can be referred to to notify the SSCF.

[0324] (2) The PDF in the SSCF updates the transmission parameters of the updated data pipe (an example of the service quality information of the updated data pipe in the solution described in FIG. 7 ).

[0325] For example, the source node of the updated data pipe is UE3, the intermediate node is RAN1, and the destination node is SDPF. The QoSS value of the updated data pipe (DPID4 or DPID1) is set to 103, the bandwidth is 4M, and the synchronization delay difference reaching SDPF does not exceed 10ms.

[0326] (3) PDF in SSCF updates the acquisition strategy of the updated data pipeline.

[0327] Exemplarily, the content collected by the endpoint of UE3 is set; UE3 is set to collect I / Q signals in real time, and the collection interval of UE3 is set to 100ns.

[0328] (4) SSCF may notify UE1 to be released; the specific notification process is not limited and may be implemented by referring to the existing process.

[0329] If a new identifier DPID4 is used to identify a new data pipe, then any node that has stored or received DPID1 can delete the identifier.

[0330] It should be noted that different embodiments or partial steps (e.g., any one or more steps) in different embodiments of the present invention may be combined to form new embodiments. Furthermore, any one or more steps in different embodiments may include optional steps in a particular embodiment, mandatory steps in a particular embodiment, or both optional and mandatory steps in a particular embodiment, and this application does not limit this.

[0331] It should be noted that, unless otherwise specified or there is no logical conflict, the terms and / or descriptions between different implementations are consistent and can be referenced to each other.

[0332] It should be noted that the present application does not limit the order of the steps in the implementation manner of the present application.

[0333] It should be noted that the order of judging different conditions in the implementation manner of the present application is not limited by the present application.

[0334] It should be noted that the terms “after” and “when” in this application do not strictly limit the time point.

[0335] It should be noted that the nouns, terms, etc. involved in this application are merely examples and may also be other names, which are not limited in this application.

[0336] In the embodiments provided in the present application above, the methods provided in the embodiments of the present application are introduced from the perspective of interaction between various devices. In order to implement the various functions in the methods provided in the embodiments of the present application above, the first functional network element or the second functional network element or the first source node may include a hardware structure and / or a software module, and implement the above functions in the form of a hardware structure, a software module, or a hardware structure plus a software module. Whether one of the above functions is executed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraints of the technical solution.

[0337] The division of modules in the embodiments of the present application is illustrative and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional modules in the various embodiments of the present application may be integrated into a single processor, or may exist physically separately, or two or more modules may be integrated into a single module. The aforementioned integrated modules may be implemented in the form of hardware or software functional modules.

[0338] Similar to the above concept, as shown in FIG11 , an embodiment of the present application further provides a communication device 1100 for implementing the functions of the first functional network element, the second functional network element, or the first source node in the above method. For example, the communication device 1100 may be a software module or a chip system. In the embodiment of the present application, the chip system may be composed of a chip, or may include a chip and other discrete devices. The communication device 1100 may include: a communication unit 1101 and a processing unit 1102.

[0339] In the embodiments of the present application, the communication unit 1101 may also be referred to as a transceiver unit, and may include a sending unit and / or a receiving unit, respectively configured to execute the steps of sending and receiving by the first functional network element, the second functional network element, or the first source node in the above method embodiments. The processing unit 1102 may be configured to read instructions and / or data from the storage module to enable the communication device 1100 to implement the above method embodiments.

[0340] Optionally, the communication device 1100 may further include a storage unit 1103 , which is equivalent to a storage module and may be used to store instructions and / or data.

[0341] The communication device provided in the embodiments of the present application is described in detail below in conjunction with Figures 11 and 12. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment. Therefore, for matters not described in detail, reference can be made to the method embodiment described in Figures 7 and 8A above. For the sake of brevity, they will not be repeated here.

[0342] Communication unit 1101 may also be referred to as a transceiver, transceiver, or transceiver device. A processing unit may also be referred to as a processor, processing board, processing module, or processing device. Alternatively, the device in communication unit 1101 that implements the receiving function may be considered a receiving unit, and the device in communication unit 1101 that implements the transmitting function may be considered a transmitting unit. That is, communication unit 1101 includes both a receiving unit and a transmitting unit. A communication unit may also be referred to as a transceiver, transceiver, or transceiver circuit. A receiving unit may also be referred to as a receiver, receiver, or receiving circuit. A transmitting unit may also be referred to as a transmitter, transmitter, or transmitting circuit.

[0343] When the communication device 1100 executes the first functional network element in the process shown in Figure 7 of the above embodiment: the communication unit 1101 is used to obtain the identification information of the perception service; the processing unit 1102 is used to determine the policy information of the perception service based on the identification information of the perception service; the policy information of the perception service includes the first service quality information of the perception service; the communication unit 1101 is also used to send the policy information of the perception service to the second functional network element.

[0344] When the communication device 1100 executes the second functional network element in the process shown in Figure 7 of the above embodiment: the communication unit 1101 is used to receive policy information of the perception service from the first functional network element, and the policy information of the perception service includes the first service quality information of the perception service; the processing unit 1102 is used to determine the information of at least one data pipeline corresponding to the perception service according to the policy information of the perception service, and determine the second service quality information corresponding to the at least one data pipeline.

[0345] When the communication device 1100 executes the first source node in the process shown in Figure 7 of the above embodiment: the processing unit 1102 is used to obtain the data of the perception service through the communication unit 1101 based on the collection strategy information of the first source node; the communication unit 1101 is used to send the data of the perception service and the indication information of the second service quality information of the first data pipeline.

[0346] The above is just an example. The processing unit 1102 and the communication unit 1101 can also perform other functions. For more detailed descriptions, please refer to the relevant descriptions in the method embodiments shown in Figures 7 and 8A, which are not repeated here.

[0347] FIG12 shows a communication device 1200 provided in an embodiment of the present application. The communication device shown in FIG12 may be a hardware circuit implementation of the communication device shown in FIG11 . The communication device 1200 may be applicable to the flowchart shown above, performing the functions of the first functional network element, the second functional network element, or the first source node in the above-described method embodiment. For ease of illustration, FIG12 only shows the main components of the communication device.

[0348] As shown in Figure 12, communication device 1200 includes a communication interface 1201 and a processor 1202. Communication interface 1201 and processor 1202 are coupled to each other. It is understood that communication interface 1201 can be a transceiver or input / output interface, or an interface circuit such as a transceiver circuit. Optionally, communication device 1200 can also include a memory 1203 for storing instructions executed by processor 1202, input data required by processor 1202 to execute instructions, or data generated by processor 1202 after executing instructions.

[0349] When the communication device 1200 is used to implement the method shown in FIG. 7 and FIG. 8A , the communication interface 1201 is used to implement the functions of the above-mentioned communication unit 1101 , and the processor 1202 is used to implement the functions of the above-mentioned processing unit 1102 .

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

[0351] When the communication device is a chip, FIG13 shows a simplified schematic diagram of the chip structure, wherein the chip 1300 includes an interface circuit 1301 and one or more processors 1302. Optionally, the chip 1300 may further include a bus.

[0352] The processor 1302 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above-mentioned method for determining service node information can be completed by hardware integrated logic circuits or software instructions in the processor 1302. The above-mentioned processor 1302 can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the various methods and steps disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc.

[0353] The interface circuit 1301 can be used to send or receive data, instructions or information. The processor 1302 can use the data, instructions or other information received by the interface circuit 1301 to process it, and can send the processing completion information through the interface circuit 1301.

[0354] Optionally, the chip further includes a memory 1303, which may include a read-only memory and a random access memory, and provides operating instructions and data to the processor. A portion of the memory 1303 may also include a non-volatile random access memory (NVRAM). In some embodiments, the memory 1303 includes a non-transitory storage.

[0355] Optionally, the memory stores an executable software module or a data structure, and the processor can perform corresponding operations by calling an operation instruction stored in the memory (the operation instruction may be stored in an operating system).

[0356] Optionally, the chip can be used in the first functional network element, the second functional network element, or the first source node involved in the embodiments of the present application. Optionally, the interface circuit 1301 can be used to output the execution result of the processor 1302. Regarding the method for determining the service node information provided by one or more embodiments of the present application, reference can be made to the aforementioned embodiments and will not be repeated here.

[0357] It should be noted that the corresponding functions of the interface circuit 1301 and the processor 1302 can be implemented through hardware design, software design, or a combination of hardware and software, and there is no limitation here.

[0358] An embodiment of the present application also provides a computer-readable storage medium storing a computer program or instruction for implementing the method executed by the first functional network element, the second functional network element, or the first source node in the above method embodiment.

[0359] For example, when the computer program or instruction is executed by a computer, the computer can implement the method executed by the first functional network element or the second functional network element or the first source node in the above method embodiment.

[0360] An embodiment of the present application also provides a computer program product comprising a computer program or instructions, which, when executed by a computer, enables the computer to implement the method executed by the first functional network element, the second functional network element, or the first source node in the above method embodiment.

[0361] An embodiment of the present application further provides a chip, including a processor, configured to call a computer program or computer instruction stored in the memory, so that the processor executes the method for determining the service node information of the embodiments shown in FIG. 7 and FIG. 8A .

[0362] In one possible implementation, the input of the chip corresponds to the receiving operation in the embodiment shown in FIG. 7 and FIG. 8A , and the output of the chip corresponds to the sending operation in the embodiment shown in FIG. 7 and FIG. 8A .

[0363] Optionally, the processor is coupled to the memory via an interface.

[0364] Optionally, the chip further includes a memory in which computer programs or computer instructions are stored.

[0365] The processor mentioned in any of the above places may be a general-purpose central processing unit, a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of a program of a policy determination method for a perception service in the embodiments shown in FIG. 7 and FIG. 8A . The memory mentioned in any of the above places may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM), etc.

[0366] It should be noted that, for the sake of convenience and brevity, the explanation and beneficial effects of the relevant contents in any of the above-mentioned communication devices may refer to the corresponding service node information determination method embodiments provided above, which will not be repeated here.

[0367] In the present application, the communication devices may further include a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on the operating system layer. The hardware layer may include hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also known as main memory). The operating system of the operating system layer may be any one or more computer operating systems that implement business processing through processes, such as the Linux operating system, Unix operating system, Android operating system, iOS operating system, or Windows operating system. The application layer may include applications such as browsers, address books, word processing software, and instant messaging software.

[0368] The division of modules in the embodiments of the present application is illustrative and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional modules in the various embodiments of the present application may be integrated into a single processor, or may exist physically separately, or two or more modules may be integrated into a single module. The aforementioned integrated modules may be implemented in the form of hardware or software functional modules.

[0369] Through the description of the above embodiments, it will be clear to those skilled in the art that the embodiments of the present application can be implemented in hardware, firmware, or a combination thereof. When software is used for implementation, the above functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein the communication media include any medium that facilitates the transmission of a computer program from one place to another. The storage medium can be any available medium that a computer can access. For example, but not limited to: a computer-readable medium may include RAM, ROM, electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store a desired program code in the form of an instruction or data structure and can be accessed by a computer. In addition, any connection can be appropriately a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of the medium. As used in the embodiments of the present application, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks typically reproduce data magnetically and discs use lasers to reproduce data optically. Combinations of the above should also be included within the scope of protection of computer-readable media.

[0370] In short, the above description is only an embodiment of the present application and is not intended to limit the scope of protection of the present application. Any modifications, equivalent replacements, improvements, etc. made based on the disclosure of the present application should be included in the scope of protection of the present application.

Claims

1. A method for determining a perception service strategy, characterized in that The method is applied to a first functional network element and includes: Obtaining identification information of a perception service; Determining policy information of the perception service according to the identification information of the perception service; the policy information of the perception service includes first quality of service information of the perception service; Sending the policy information of the perception service to a second functional network element.

2. The method according to claim 1, wherein The policy information of the perception service further includes one or more of execution scope information of the perception service and first collection policy information of the perception service.

3. The method according to claim 1 or 2, characterized in that, The identification information of the perception service corresponds to user information of the perception service, and the user information of the perception service includes one or more of the following: User subscription information of the perception service, service subscription information of the perception service, user account opening information of the perception service, service delay information of the perception service.

4. The method according to any one of claims 1 to 3, characterized in that The obtaining of the user information of the perception service includes: Obtaining the user information of the perception service from a user management network element of the perception service.

5. A method for determining a perception service policy, characterized in that, The method is applied to a second functional network element and includes: Receiving the policy information of the perception service from the first functional network element, where the policy information of the perception service includes first quality of service information of the perception service; Determining information of at least one data pipeline corresponding to the perception service according to the policy information of the perception service, and determining second quality of service information corresponding to each of the at least one data pipeline.

6. The method according to claim 5, characterized in that The policy information of the perception service further includes collection policy information of the perception service; the method further includes: Determining collection policy information of source nodes corresponding to each of the at least one data pipeline according to the collection policy information of the perception service.

7. The method according to claim 5 or 6, characterized in that, The policy information of the perception service further includes execution scope information of the perception service; the method further includes: Obtaining status information of a network within the execution scope of the perception service and / or status information of a node according to the execution scope information of the perception service; The determining of the information of at least one data pipeline corresponding to the perception service according to the policy information of the perception service includes: Determining information of destination nodes and source nodes corresponding to each of the at least one data pipeline according to the policy information of the perception service, and status information of the network and / or capability information of the node and / or status information of the node.

8. The method according to claim 7, wherein The method further includes: Sending the corresponding second quality of service information and the collection policy information of the source node to the source node corresponding to each of the at least one data pipeline according to the information of the source nodes corresponding to each of the at least one data pipeline.

9. The method according to claim 7 or 8, characterized in that, The information of the data pipeline further includes information of at least one intermediate node located within the execution scope, and / or identification information of the data pipeline.

10. The method according to any one of claims 7 to 9, characterized in that, The method further includes: When a first source node of a first data pipeline moves out of the execution scope of the perception service, determining a second node within the execution scope of the perception service; and using the second node as the source node of the first data pipeline to obtain an updated first data pipeline; the first data pipeline is any one of the at least one data pipeline.

11. The method according to claim 10, characterized in that, The method further includes: Determine the second quality of service information corresponding to the updated first data pipeline and the collection policy information of the second node; Send the second quality of service information corresponding to the updated first data pipeline and the collection policy information of the second node to the second node.

12. A method for determining a perception service policy, characterized in that, The method is applied to the first source node of the first data pipeline and includes: Obtain the data of the sensing service based on the collection policy information of the first source node; Send the indication information of the data of the sensing service and the second quality of service information of the first data pipeline.

13. The method according to claim 12, characterized in that The indication information of the data of the sensing service and the second quality of service information of the first data pipeline are located in the same data packet.

14. The method according to claim 12 or 13, characterized in that, The method further includes: Receive the second quality of service information of the first data pipeline and the collection policy information of the first source node from the second functional network element.

15. The method according to any one of claims 12 to 14, characterized in that, When the first source node is deployed in the first radio access network node, the sending of the indication information of the data of the sensing service and the second quality of service information of the first data pipeline includes: Map the first data pipeline to the corresponding first communication tunnel; Through the first communication tunnel, send the indication information of the data of the sensing service and the second quality of service information of the first data pipeline to the second radio access network node or the core network element; Wherein, the second radio access network node and the core network element are the destination node or intermediate node corresponding to the first data pipeline.

16. The method according to any one of claims 12 to 14, characterized in that, When the first source node is deployed in the terminal device, the sending of the indication information of the data of the sensing service and the second quality of service information of the first data pipeline includes: Map the first data pipeline to the corresponding first data radio bearer; Through the first data radio bearer, send the indication information of the data of the sensing service and the second quality of service information of the first data pipeline to the radio access network node; the radio access network node is the destination node or intermediate node corresponding to the first data pipeline.

17. The method according to claim 15, characterized in that, The first communication tunnel also corresponds to a second data pipeline, and the second data pipeline is used to transmit the data of other sensing services.

18. The method according to claim 16, wherein The first data radio bearer also corresponds to a second data pipeline, and the second data pipeline is used to transmit the data of other sensing services.

19. The method according to any one of claims 1 to 11, characterized in that, The first quality of service information of the sensing service includes one or more of the following: The transmission delay of the sensing service, the maximum bandwidth of the sensing service, the guaranteed bandwidth of the sensing service, the execution period of the sensing service, the maximum data burst volume of the sensing service, the number of nodes participating in the sensing service, the time difference range for the sensing service data to arrive synchronously, the deterministic delay for the sensing service data to arrive synchronously, the priority of the sensing service.

20. The method according to any one of claims 1 to 11, characterized in that, The policy information of the sensing service further includes one or more of the following: The flow policy information of the sensing service, the security policy information of the sensing service.

21. The method according to any one of claims 2, 6 - 11, 12 - 18, characterized in that, The collection policy information includes one or more of the following: The minimum sensing signal for sensing measurement, the time interval for collecting data, whether the data collection is real-time or non-real-time.

22. The method according to any one of claims 7 to 18, characterized in that, The node is a policy execution functional network element; The policy enforcement function network element is independently deployed and serves the second service network element, or the policy enforcement function network element is deployed in the second service network element; the second service network element is any one of the following: Terminal, radio access network node, access and mobility management function, session management function, unified data repository, user plane function, perception data processing function.

23. The method according to any one of claims 1 to 22, characterized in that, The second functional network element is independently deployed in the core network or the access network or the network management system, or the second functional network element is co-located with the first service network element; the first service network element is any one of the following: Data controller, perception service control function, task anchor, task scheduling.

24. A communication system, characterized in that, Including: A first functional network element and a second functional network element; The first functional network element is configured to obtain identification information of a perception service; According to the identification information of the perception service, determine the policy information of the perception service; the policy information of the perception service includes the first quality of service information of the perception service; Send the policy information of the perception service to the second functional network element; The second functional network element is configured to determine information of at least one data pipeline corresponding to the perception service according to the policy information of the perception service, and determine second quality of service information corresponding to each of the at least one data pipeline.

25. The communication system according to claim 24, wherein The first functional network element is further configured to execute the method according to any one of claims 2-4, 19-21, and 23; the second functional network element is further configured to execute the method according to any one of claims 6-11, and 19-23.

26. The communication system according to claim 24 or 25, characterized in that, It further includes at least one destination node and at least one source node corresponding to each data pipeline; any one of the at least one source nodes executes the method according to any one of claims 12-18, 21-23.

27. A communication device, characterized in that, It includes a module for executing the method according to any one of claims 1-4, 19-21, and 23; or includes a module for executing the method according to any one of claims 5-11, and 19-23; or includes a module for executing the method according to any one of claims 12-18, 21-23.

28. A computer-readable storage medium, characterized in that, It stores a computer program or instruction, and the computer program or instruction is used to implement the method according to any one of claims 1-23.

29. A computer program product, characterized in that, The computer program product includes a computer program or instruction, and when the computer program or instruction runs on a computer, the computer is caused to execute the method according to any one of claims 1-23.

Images