Sensing service charging method, communication apparatus, and system

Abstract

The present application relates to the technical field of sensing, and provides a sensing service charging method, a communication apparatus, and a system. In the method, after a sensing service control network element determines charging configuration information, the charging configuration information can be issued to a data function network element; on the basis of the charging configuration information, the data function network element performs charging processing for the sensing service, in order to support performing charging processing for the sensing service.

Description

Billing method, communication device and system for perception service

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on December 6, 2023, with application number 202311671278.7 and application name “Billing method, communication device and system for perception services”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and more specifically, to a billing method, communication device, and system for perception services. Background Art

[0003] Wireless communication and wireless sensing are both based on electromagnetic wave theory. The transmitter modulates electromagnetic wave signals, allowing them to carry information about the source. However, electromagnetic wave signals are affected by the wireless environment during propagation, meaning they are modulated by the environment and thus carry environmental information. The receiver analyzes the electromagnetic wave signals to not only obtain the source information but also extract perception information reflecting the characteristics of the propagation environment. This makes the integration of communication and perception possible.

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

[0005] There may be a large number of sensing services in the communication system, and how to charge for the sensing services is a technical problem that needs to be solved urgently.

[0006] Summary of the Invention

[0007] The present application provides a billing method and a communication device that can support billing processing for perception services.

[0008] In a first aspect, a billing method for a perception service is provided, which is applied to a perception service control network element. The method includes: determining billing configuration information, where the billing configuration information is used to perform billing processing on the perception service; and sending the billing configuration information to a data function network element.

[0009] In the above solution, after the perception service control network element determines the billing configuration information, it can send the billing configuration information to the data function network element. The data function network element performs billing processing on the perception service according to the billing configuration information, thereby supporting billing processing for the perception service.

[0010] By deploying data function network elements, embodiments of the present application can reduce the overall time required for billing processing of perception services. For example, the data function network element performs statistical processing on the perception data of the perception service based on the billing configuration information, obtains corresponding billing information, and feeds back the billing information. The network element responsible for the billing function directly performs billing processing for the perception service based on the billing information.

[0011] In the first aspect, the charging configuration information includes charging parameters, and the determining of the charging configuration information includes: sending first information to the charging function network element, where the first information is used to request the charging parameters; and receiving the charging parameters from the charging function network element.

[0012] In this way, the billing parameters can be obtained.

[0013] In the first aspect, the charging configuration information includes charging parameters, and the determining of the charging configuration information includes: the charging parameters are preconfigured, or the charging parameters are predefined.

[0014] In this way, the signaling interaction overhead for obtaining charging parameters can be reduced.

[0015] In the first aspect, the charging configuration information includes a charging policy, and determining the charging configuration information includes: sending second information to a policy control network element, where the second information is used to request a charging policy; and receiving the charging policy from the policy control network element.

[0016] In this way, the charging policy can be obtained.

[0017] In the first aspect, the charging configuration information includes a charging policy, and the determining of the charging configuration information includes: the charging policy is preconfigured, or the charging policy is predefined.

[0018] In this way, the signaling interaction overhead for obtaining the charging policy can be reduced.

[0019] In the first aspect, the method also includes: receiving billing information of the perception service from the data function network element; in response to the billing information, sending third information to the billing function network element, the third information is used to request a second billing quota for the perception service, and the second billing quota is associated with the billing information.

[0020] The second charging quota of the interactive perception service can prevent the perception service user from using up all the charging quota of the perception service while continuing to use the perception service, thereby causing economic losses.

[0021] In the first aspect, before determining the charging configuration information, the method further includes: receiving fourth information from a user of the perception service, where the fourth information is used to request the perception service.

[0022] In this way, the awareness service control network element can determine corresponding charging configuration information according to the request information sent by the awareness service user, thereby supporting charging processing for the awareness service.

[0023] In a second aspect, a billing method for a perception service is provided, which is applied to a data function network element. The method includes: receiving billing configuration information from a perception service control network element; and performing billing processing on the perception service according to the billing configuration information.

[0024] In a second aspect, the method further includes: sending charging information of the perception service to the perception service control network element; and receiving a second charging quota of the perception service from the perception service control network element, where the second charging quota is determined based on the charging information.

[0025] By using the second billing quota for the interactive perception service, it is possible to prevent the perception service user from using up all of the billing quota for the perception service while continuing to use the perception service, thereby causing economic losses. In conjunction with the solution described in either of the first and second aspects, the billing configuration information includes one or both of the billing policy and the billing parameters.

[0026] For example, the charging configuration information includes a charging policy, which indicates a policy when charging for the perception service;

[0027] For another example, the charging configuration information includes charging parameters, which indicate parameters for charging the sensing service;

[0028] For another example, the charging configuration information includes a charging policy and charging parameters, which respectively indicate a policy and parameters for charging the perception service.

[0029] Through the above-mentioned billing strategy and / or billing parameters, the embodiment of the present application can support billing processing for perception services.

[0030] In combination with the solution described in any one of the first aspect and the second aspect, the charging strategy includes one or both of the charging method and the charging granularity.

[0031] Through the above-mentioned billing granularity and / or billing method, the data function network element can complete the statistical processing of the perception service, and based on the information obtained from the statistical processing, the embodiment of the present application can support billing processing of the perception service.

[0032] In combination with the solution described in any one of the first and second aspects, the billing method includes one or both of online billing and offline billing.

[0033] When the billing method is online billing, the data function network element can obtain the billing information of the perception service in real time, which is conducive to real-time monitoring of the account balance of the perception service user and timely stopping the perception service user from continuing to use the perception service when the account balance of the perception service user is exhausted.

[0034] When the billing method is offline billing, the data function network element can obtain the billing information of the perception service at a specified time, which is conducive to reducing the signaling interaction overhead of the data function network element. For example, the data function network element does not need to frequently report the billing information of the perception service to the perception service control network element.

[0035] In combination with the solution described in any one of the first and second aspects, the billing granularity includes one or both of service-based billing and service quality flow-based billing.

[0036] When the billing granularity is service-based billing, the data function network element can perform appropriate statistics based on the type of perception services performed by perception service users and obtain corresponding billing information to support billing processing for the perception services.

[0037] When the billing granularity is based on service quality flow, the data function network element can perform appropriate statistics on the service quality flow of the perception service performed by the perception service user and obtain corresponding billing information to support billing processing for the perception service.

[0038] When the billing granularity is service-based billing and service quality flow-based billing, the data function network element can perform appropriate statistics based on the service quality flow and type of the perception service performed by the perception service user, and obtain corresponding billing information to support billing processing for the perception service.

[0039] In combination with the solution described in any one of the first and second aspects, the charging parameter includes at least one of the following: a charging mode, a charging event, a first charging quota, or a threshold of a charging event.

[0040] When the charging parameters include a charging mode, the data function network element may determine a charging mode for the perception service.

[0041] When the charging parameters include charging events, the data function network element may determine a condition for reporting charging information of the perception service to the perception service control network element.

[0042] When the billing parameters include a first billing quota, the data function network element can determine the initial quota for the perception service user. By issuing the first billing quota, the number of call records and the amount of information sent by the data function network element to the perception service control network element can be controlled, thereby reducing signaling interaction overhead and the impact on the billing function network element.

[0043] When the charging parameters include a threshold for a charging event, the data function network element may determine specific conditions for reporting charging information for the perception service to the perception service control network element. In conjunction with the solution described in any one of the first and second aspects, the charging mode includes at least one of the following: flow-based charging, duration-based charging, charging based on the time at which the service occurs, or charging based on the number of times the service occurs.

[0044] Through one or more of the above, the embodiment of the present application can support billing processing for the perception service. For example, the data function network element can determine the specific content that needs to be counted when performing perception service on the perception service user.

[0045] In combination with the solutions described in any one of the first and second aspects, the billing event includes at least one of the following: traffic reaches a threshold, duration reaches a threshold, the time point of service occurrence changes, or the number of service occurrences reaches a threshold.

[0046] Through one or more of the above, the embodiment of the present application can support billing processing for the perception service. For example, the data function network element can determine the conditions for reporting billing information to the perception service control network element.

[0047] In combination with the solutions described in any one of the first and second aspects, the threshold of the billing event includes at least one of the following: a traffic threshold, a duration threshold, or a service occurrence count threshold.

[0048] Through one or more of the above, the embodiment of the present application can support billing processing for the perception service. For example, the data function network element can determine the specific conditions for reporting billing information to the perception service control network element.

[0049] On the third aspect, a billing method for perception services is provided, including: receiving registration information from a perception service user, the registration information being used to request completion of the registration of the perception service user, the perception service user being a user requesting the perception service; and sending a first response message to the perception service user, the first response message being used to respond to the registration information.

[0050] Through the above method, the embodiment of the present application can support the completion of the registration process for perception service users.

[0051] In a third aspect, the method further includes: receiving request information from the perception service user, the request information being used to request the perception service; and sending second response information to the perception service user, the second response information being used to respond to the request information.

[0052] Through the method, the embodiment of the present application can support perception service users to request or use perception services.

[0053] In the third aspect, the registration information includes at least one of the following: user name, user identification, user type, authentication data, and billing attributes.

[0054] Through one or more of the above, the awareness service user management network element can obtain relevant information about the awareness service user and can complete registration management of the awareness service user based on the relevant information.

[0055] In the third aspect, the registration information further includes at least one of the following: a type of perception service allowed to be requested, a service prohibited area, a user priority, or service subscription information.

[0056] Through one or more of the above, the awareness service user management network element can further complete the registration management of the awareness service users.

[0057] In a fourth aspect, a communication system is provided, including: a perception service control network element, used to determine billing configuration information, which is used to perform billing processing on the perception service; the perception service control network element, also used to send billing configuration information to the data function network element; the data function network element, used to receive the billing configuration information, and, also used to perform billing processing on the perception service according to the billing configuration information.

[0058] The aforementioned perception service control network element may also be used to execute the method described in the first aspect. The aforementioned data function network element may also be used to execute the method described in the second aspect.

[0059] Optionally, the communication system may further include a policy control network element, which is used to execute the method described in the first aspect.

[0060] Optionally, the communication system may further include a charging function network element, which is used to execute the method described in the first aspect.

[0061] Optionally, the communication system may further include an awareness service user management network element, which is used to execute the method described in the third aspect.

[0062] In a fifth aspect, a communication device is provided, including: a processing unit for determining billing configuration information, the billing configuration information is used to perform billing processing on the perception service; and an interface unit for sending the billing configuration information to a data function network element.

[0063] The communication device described in the fifth aspect can be used to execute the method described in the first aspect and any possible implementation method of the first aspect. For details, please refer to the description of the method described in the first aspect and any possible implementation method of the first aspect, and no further details will be given.

[0064] In the sixth aspect, a communication device is provided, including: an interface unit for receiving billing configuration information from a perception service control network element, the billing configuration information being used to perform billing processing on the perception service; and a processing unit for performing billing processing on the perception service according to the billing configuration information.

[0065] The communication device described in the sixth aspect can be used to execute the method described in the second aspect and any possible implementation method of the second aspect. For details, please refer to the description of the method described in the second aspect and any possible implementation method of the second aspect, and no further details will be given.

[0066] In the seventh aspect, a communication device is provided, including: an interface unit for receiving registration information from a perception service user, the registration information being used to request completion of the registration of the perception service user, the perception service user being a user who requests the perception service; the interface unit is also used to send a first response message to the perception service user, the first response message being used to respond to the registration information.

[0067] In one possible implementation, the above-mentioned communication device may further include a processing unit, which is used to process the content related to information processing of the communication device. The specific description can be found in the above text and will not be repeated here.

[0068] The communication device described in the seventh aspect can be used to execute the method described in the third aspect and any possible implementation method of the third aspect. For details, please refer to the description of the method described in the third aspect and any possible implementation method of the third aspect, and no further details will be given.

[0069] In an eighth aspect, a communication device is provided, comprising a processor, wherein the processor is used to, by executing a computer program or instruction, or by a logic circuit, enable the communication device to execute the method described in the first aspect and any possible implementation of the first aspect; or, enable the communication device to execute the method described in the second aspect and any possible implementation of the second aspect; or, enable the communication device to execute the method described in the third aspect and any possible implementation of the third aspect.

[0070] In the ninth aspect, a communication device is provided, comprising a logic circuit and an input / output interface, wherein the input / output interface is used to input and / or output signals, and the logic circuit is used to execute the method described in the first aspect and any possible implementation of the first aspect; or, the logic circuit is used to execute the method described in the second aspect and any possible implementation of the second aspect; or, the logic circuit is used to execute the method described in the third aspect and any possible implementation of the third aspect.

[0071] In the tenth aspect, a computer-readable storage medium is provided, on which a computer program or instructions are stored. When the computer program or the instructions are run on a computer, the method described in the first aspect and any possible implementation of the first aspect is executed; or, the method described in the second aspect and any possible implementation of the second aspect is executed; or, the method described in the third aspect and any possible implementation of the third aspect is executed.

[0072] In the eleventh aspect, a computer program product is provided, comprising instructions, which, when executed on a computer, cause the method described in the first aspect and any possible implementation of the first aspect to be executed; or, cause the method described in the second aspect and any possible implementation of the second aspect to be executed; or, cause the method described in the third aspect and any possible implementation of the third aspect to be executed.

[0073] In a twelfth aspect, an embodiment of the present application provides a communication device, comprising a module for executing the method of all possible modes in the first aspect, the second aspect, or the third aspect.

[0074] In the thirteenth aspect, an embodiment of the present application provides a communication device, including an interface circuit and a processor, and the communication device is used to execute any possible method of the first aspect, the second aspect, or the third aspect.

[0075] The aforementioned interface circuit may also be a communication interface. The aforementioned processor may also be a logic circuit or a processing circuit.

[0076] In the fourteenth aspect, an embodiment of the present application provides a processor for coupling with a memory, for executing any possible method of the above-mentioned first aspect, second aspect, or third aspect.

[0077] In the fifteenth aspect, a communication device is provided, comprising: a processor for executing computer instructions stored in a memory so that the communication device performs the method described in any possible manner in the first aspect, the second aspect, or the third aspect above.

[0078] In one possible implementation, the above-mentioned communication device further includes a memory.

[0079] In one possible implementation, the communication device further includes a communication interface, which is coupled to the processor, and the communication interface is used to input and / or output information.

[0080] In the sixteenth aspect, a chip is provided, which is connected to a memory and is used to read and execute a software program stored in the memory to execute the method described in any possible manner in the first aspect, the second aspect, or the third aspect above. BRIEF DESCRIPTION OF THE DRAWINGS

[0081] FIG1 is a schematic diagram of a communication system 100 to which an embodiment of the present application is applicable.

[0082] FIG2 is a schematic diagram of a perception scene 200 according to an embodiment of the present application.

[0083] FIG3 is a schematic diagram of a networking architecture 300 according to an embodiment of the present application.

[0084] FIG4 is a schematic diagram of an interaction flow of a billing method 400 for a perception service according to an embodiment of the present application.

[0085] FIG5 is a schematic diagram of an interaction flow of a billing method 500 for a perception service according to an embodiment of the present application.

[0086] FIG6 is a schematic diagram of an interaction flow of a billing method 600 for a perception service according to an embodiment of the present application.

[0087] FIG7 is a schematic diagram of an interaction flow of a billing method 700 for a perception service according to an embodiment of the present application.

[0088] FIG8 is a schematic diagram of an interaction flow of a billing method 800 for a perception service according to an embodiment of the present application.

[0089] FIG9 is a schematic diagram of an interaction flow of a billing method 900 for a perception service according to an embodiment of the present application.

[0090] FIG10 is a schematic diagram of a communication device 1000 according to an embodiment of the present application.

[0091] FIG11 is a schematic diagram of a communication device 1100 according to an embodiment of the present application. DETAILED DESCRIPTION

[0092] The technical solution in this application will be described below with reference to the accompanying drawings.

[0093] In order to facilitate understanding of the embodiments of the present application, the following points are first explained.

[0094] 1. Unless otherwise specified, “plurality” means two or more.

[0095] 2. Unless otherwise specified or there is no logical conflict, the terms and / or descriptions between different embodiments of this application are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments based on their internal logical relationships.

[0096] 3. The various numerical numbers involved in this application are only used for the convenience of description and are not used to limit the scope of protection of this application. The size of the serial numbers involved in this application does not mean the order of execution. The order of execution of each process should be determined by its function and internal logic. For example, the terms "first", "second", "third", "fourth" and other various terminology labels (if any) in the specification and claims and drawings of this application are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. Among them, the data used in this way can be interchangeable where appropriate, so that the embodiments described here can be implemented in an order other than what is illustrated or described here.

[0097] At the same time, any embodiment or design described in this application as "exemplary" or "for example" should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner to facilitate understanding.

[0098] 4. The terms "comprise" and "have" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or apparatus that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such process, method, product or apparatus.

[0099] 5. In this application, "used to indicate" can be understood as "enabling," and "enabling" can include direct enabling and indirect enabling. When describing that certain information is used to enable A, it can include that the information directly enables A or indirectly enables A, and does not necessarily mean that the information contains A.

[0100] The information enabled by the information is called information to be enabled. In the specific implementation process, there are many ways to enable the enabled information, such as but not limited to, directly enabling the information to be enabled, such as the information to be enabled itself or the index of the information to be enabled. The information to be enabled can also be indirectly enabled by enabling other information, wherein there is an association between the other information and the information to be enabled. It is also possible to enable only a part of the information to be enabled, while the other parts of the information to be enabled are known or agreed in advance. For example, it is also possible to enable specific information with the help of the arrangement order of each piece of information agreed in advance (such as specified in the protocol), thereby reducing the enabling overhead to a certain extent. At the same time, it is also possible to identify the common parts of each piece of information and enable them uniformly to reduce the enabling overhead caused by enabling the same information separately.

[0101] 6. In this application, "pre-configuration" may include pre-definition, such as protocol definition. "Pre-definition" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., including each network element). This application does not limit the specific implementation method.

[0102] 7. "Storage" or "saving" as used in this application may refer to storage in one or more memories. The one or more memories may be provided separately or integrated into an encoder or decoder, a processor, or a communication device. The one or more memories may also be provided in part separately and in part integrated into a decoder, processor, or communication device. The type of memory may be any form of storage medium and is not limited thereto.

[0103] 8. The “protocol” referred to in this application may refer to a standard protocol in the field of communications, such as the fourth generation (4G) th generation, 4G) network, fifth generation (5 th generation, 5G) network protocol, NR protocol, 5.5G network protocol, sixth generation (6 th generation, 6G) network protocols and related protocols used in future communication systems, which are not limited in this application.

[0104] 9. The arrows or boxes indicated by dotted lines in the schematic diagrams in the accompanying drawings of this application specification represent optional steps or optional modules.

[0105] 10. Unless otherwise specified, “ / ” indicates that the objects associated with each other are in an “or” relationship. For example, A / B can mean A or B. “And / or” in this application is only a description of the association relationship between the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. A and B can be singular or plural.

[0106] 11. In this application, "indication" may include direct indication, indirect indication, explicit indication, and implicit indication. When describing a certain indication information as indicating A, it can be understood that the indication information carries A, directly indicates A, or indirectly indicates A.

[0107] In this application, the information indicated by the indication information is referred to as the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated, such as but not limited to, the information to be indicated can be directly indicated, such as the information to be indicated itself or the index of the information to be indicated. The information to be indicated can also be indirectly indicated by indicating other information, wherein there is an association between the other information and the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while the other parts of the information to be indicated are known or agreed in advance. For example, the indication of specific information can also be achieved with the help of the arrangement order of each information agreed in advance (for example, stipulated by the protocol), thereby reducing the indication overhead to a certain extent. In addition, the information to be indicated can be sent together as a whole, or it can be divided into multiple sub-information and sent separately, and the sending period and / or sending time of these sub-information can be the same or different.

[0108] 12. In this application, "sending" and "receiving" indicate the direction of signal transmission. For example, "sending information to XX" can be understood as the destination of the information being XX, which can include direct sending through the air interface, as well as indirect sending through the air interface by other units or modules. "Receiving information from YY" can be understood as the source of the information being YY, which can include direct receiving from YY through the air interface, as well as indirect receiving from YY through the air interface from other units or modules. "Sending" can also be understood as the "output" of the chip interface, and "receiving" can also be understood as the "input" of the chip interface. In other words, sending and receiving can be performed between devices, for example, between a network device and a terminal device, or can be performed within a device, for example, sending or receiving between components, modules, chips, software modules, or hardware modules within the device through a bus, trace, or interface.

[0109] First, a communication system to which the embodiments of the present application are applicable is described.

[0110] The technical solution provided by this application can be applied to various communication systems, such as the fifth generation (5th generation, 5G) or new radio (NR) system, long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, etc. The technical solution provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system. The technical solution provided in this application can also be applied to device to device (D2D) communication, vehicle-to-everything (V2X) communication, machine to machine (M2M) communication, machine type communication (MTC), and Internet of Things (IoT) communication system or other communication systems.

[0111] The terminal devices in the embodiments of the present application include various devices with wireless communication functions, which can be used to connect people, objects, machines, etc. The terminal devices can be widely used in various scenarios, such as: cellular communication, D2D, V2X, peer to peer (P2P), M2M, MTC, IoT, virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery and other scenarios. The terminal device can be a terminal in any of the above scenarios, such as an MTC terminal, an IoT terminal, etc. The terminal device can be a 3GPP (3rd Generation Partnership Project) terminal. rdThe present invention relates to user equipment (UE), terminal, fixed device, mobile station device or mobile device, subscriber unit, handheld device, vehicle-mounted device, wearable device, cellular phone, smart phone, SIP phone, wireless data card, personal digital assistant (PDA), computer, tablet computer, notebook computer, wireless modem, handheld device, laptop computer, computer with wireless transceiver function, smart book, vehicle, satellite, global positioning system (GPS) device, target tracking device, aircraft (such as drone, helicopter, multi-copter, quadcopter, or airplane), ship, remote control device, smart home device, industrial equipment, or device built into the above devices (such as communication module, modem or chip in the above devices), or other processing devices connected to the wireless modem. For the convenience of description, the terminal device will be described below by taking the terminal or UE as an example.

[0112] In some scenarios, the terminal device can also be used to act as a base station. For example, the terminal device can act as a scheduling entity, which provides sidelink signals between UEs in scenarios such as V2X, D2D, or P2P.

[0113] In the embodiments of the present application, the device for implementing the function of the terminal device can be the terminal device, or it can be a device that can support the terminal device to implement the function, such as a chip system or chip, which can be installed in the terminal device. In the embodiments of the present application, the chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0114] The network device in the embodiments of the present application may be a device for communicating with a terminal device, and may also be referred to as an access network device or a radio access network device. For example, the network device may be a base station. The network device in the embodiments of the present application may refer to a radio access network (RAN) node (or device) that connects a terminal device to a wireless network. Base station can broadly cover various names as follows, or replace the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmission point (TRP), transmission point (TP), master station, auxiliary station, multi-standard wireless (motor slide retainer, MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. The base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof. The base station can also refer to a communication module, modem or chip used to be set in the aforementioned device or apparatus. The base station can also be a mobile switching center and a device that performs base station functions in D2D, V2X, and M2M communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. The base station can support networks with the same or different access technologies. The embodiments of this application do not limit the specific technology and specific device form used by the network equipment.

[0115] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.

[0116] In the embodiments of the present application, the device for implementing the function of the network device can be a terminal device, or a device that can support the network device to implement the function, such as a chip system or chip, which can be installed in the network device. In the embodiments of the present application, the chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0117] The network equipment and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the scenarios in which the network equipment and terminal devices are located.

[0118] First, a brief introduction to the network architecture applicable to the embodiments of the present application is given.

[0119] FIG1 is a schematic diagram of a communication system 100 applicable to an embodiment of the present application. As shown in FIG1 , the communication system 100 includes a radio access network (RAN) 110 and a core network (CN) 200. The RAN 100 includes at least one RAN node (e.g., 110a and 110b, collectively referred to as 110) and at least one terminal device (e.g., 120a-120j, collectively referred to as 120). The RAN 100 may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in FIG1 ). The terminal device 120 is wirelessly connected to the RAN node 110. The RAN node 110 is wirelessly or wiredly connected to the core network 200. The core network devices in the core network 200 and the RAN node 110 in the RAN 100 may be different physical devices, or they may be the same physical device that integrates the core network logical functions and the radio access network logical functions.

[0120] The RAN 100 may be a 3GPP-related cellular system, such as a 4G or 5G mobile communication system, or a future-oriented evolutionary system (such as a 6G mobile communication system). The RAN 100 may also be an open access network (O-RAN or ORAN), a cloud RAN (CRAN), or a wireless fidelity (WiFi) system. The RAN 100 may also be a communication system that integrates two or more of the above systems.

[0121] RAN node 110, sometimes also referred to as access network equipment, RAN entity, or access node, constitutes part of a communication system and facilitates wireless access for terminal devices. Multiple RAN nodes 110 in the communication system can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal device 120 are relative. For example, network element 120i can be a helicopter or drone configured as a mobile base station. For terminal device 120j accessing RAN 100 via network element 120i, network element 120i is a base station; however, for base station 110a, network element 120i is a terminal device. RAN node 110 and terminal 120 are sometimes referred to as communication devices. For example, network elements 110a and 110b can be understood as communication devices with base station functionality, and network elements 120a-120j can be understood as communication devices with terminal functionality.

[0122] In one possible scenario, a RAN node may be a base station (BS), an eNodeB, an access point (AP), a Transmitter Relay (TRP), a gNB, a next-generation base station in a 6G mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system. A RAN node may be a macro base station (such as 110a in Figure 1 ), a micro base station or an indoor station (such as 110b in Figure 1 ), a relay node or a donor node, or a wireless controller in a CRAN scenario.

[0123] Optionally, the RAN node may also be a server, a wearable device, a vehicle or an on-board device, etc. For example, the access network device in the V2X technology may be a road-side unit (RSU) or a base station. All or part of the functions of the RAN node in this application may also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (such as a cloud platform). The RAN node in this application may also be a logical node, logical module or software that can implement all or part of the functions of the RAN node.

[0124] In another possible scenario, multiple RAN nodes collaborate to assist terminal devices in achieving wireless access, and different RAN nodes respectively implement part of the functions of the base station. For example, the RAN node 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 be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0125] In different communication 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 (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.

[0126] The number of devices in the above-mentioned communication system is for illustration only and is not limited thereto. In actual applications, the communication system may further include more terminal devices, more RAN devices, and other devices.

[0127] It should be understood that Figure 1 is a simplified schematic diagram for ease of understanding, and the communication system may also include a larger number of network devices or terminal devices. The embodiments of the present application may be applicable to any communication scenario in which a transmitting device and a receiving device communicate with each other.

[0128] To facilitate understanding of the embodiments of the present application, the following is a brief explanation of the terms involved in the embodiments of the present application.

[0129] 1. Definition of Perception

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

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

[0132] 2. Perception of the scene

[0133] Perception scenarios can be divided into perception scenarios based on network devices, perception scenarios based on network devices and terminal devices, and perception scenarios based on terminal devices. For example, see the perception scenarios shown in (1) to (6) of Figure 2. Figure 2 is a schematic diagram of a perception scenario 200 of an embodiment of the present application.

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

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

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

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

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

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

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

[0141] 3. Sensing Entity (SE)

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

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

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

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

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

[0147] The above-mentioned perception entities may include a perception control entity and a perception processing entity. The perception control entity may be used to implement the control plane function of the perception service, such as for receiving the perception capability information of the perception entity, and for orchestrating the perception service based on the perception capability information of the perception entity. The perception processing entity may be used to implement the data plane function of the perception service, such as for processing the perception data of the perception service to obtain the perception result of the perception service. After the control plane function of the perception service and the data plane function of the perception service are deployed independently of each other, the number of control plane functional entities and data plane functional entities can be flexibly configured and adjusted according to resources and business conditions; secondly, attacks on the data plane will not affect the control plane, and vice versa, thereby improving the reliability and security of the perception service.

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

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

[0150] The names of the perception control entity and the perception processing entity are used for example and do not constitute a limitation on the embodiments of the present application. With the development of communication technology and perception technology, these two modules may adopt other names. For example, the perception control entity can also be described as a sensing service control function (SSCF), or a perception service control network element, or a perception control network element, etc.; the perception processing entity can also be described as a sensing data processing function (SDPF), or a perception data processing network element, or a perception processing network element, a perception data function network element, a data function network element, etc. For the convenience of description, the perception control entity is described as SSCF in the following embodiments, and the perception processing entity is described as SDPF.

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

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

[0153] Figure 3 is a schematic diagram of a networking architecture 300 according to an embodiment of the present application. In the networking architecture shown in (1) of Figure 3 , the RAN is connected to the SSCF via the access and mobility management function (AMF), the RAN is connected to the SDPF via the user plane function (UPF), the SDPF is mounted on the SBI bus via the SBI, and the SSCF is mounted on the SBI bus via the SBI. Therefore, the RAN can communicate with the SSCF on the control plane via the AMF, and the RAN can communicate with the SDPF on the data plane via the UPF.

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

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

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

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

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

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

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

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

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

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

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

[0165] Based on the networking architecture shown in Figure 3, the SSCF and SDPF can be independently upgraded and maintained without impacting each other, enabling flexible deployment and management of core network functional entities. Figure 3 uses one SSCF and one SDPF as an example, which does not limit the embodiments of this application. For example, the number of SDPFs can be increased or decreased based on actual needs, and even if the number of SDPFs is reduced, the SSCF will not be impacted. This makes network expansion or streamlining easier.

[0166] The introduction of SSCF and SDPF allows for the separation of the control and data planes for sensing services. This prevents attackers from attacking control plane entities (such as SSCF) through data plane entities (such as SDPF), helping to improve network security. By separating the control and data planes for sensing services, control plane entities can respond more quickly to requests from data plane entities, reducing network latency and improving network responsiveness.

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

[0168] The following describes the billing method, communication device, and system for the perception service according to the embodiments of the present application in conjunction with the accompanying drawings.

[0169] For ease of understanding and explanation, the following describes the billing method for the perception service of the embodiment of the present application by taking the interaction between the perception service control network element and the data function network element as an example, but this should not constitute any limitation on the execution subject of the billing method for the perception service of the embodiment of the present application. For example, the method executed by the perception service control network element can also be executed by a module of the perception service control network element (such as a circuit, chip or chip system, etc.), and can also be implemented by a logical node, logical module or software that can realize all or part of the functions of the perception service control network element. The method executed by the data function network element can also be executed by a module of the second network element (such as a circuit, chip or chip system, etc.), and can also be implemented by a logical node, logical module or software that can realize all or part of the functions of the data function network element.

[0170] The aforementioned network elements may also be entities and other concepts, for example, perception service control entities and data function entities.

[0171] FIG4 is a schematic diagram of an interactive process of a billing method 400 for a perception service according to an embodiment of the present application. As shown in FIG4 , the method includes:

[0172] S401. The perception service control network element determines charging configuration information.

[0173] The billing configuration information can be used to process billing for sensing services. A sensing service can be a service requested by a sensing service user. For example, a sensing service can include one or more of positioning sensing services, speed sensing services, and imaging sensing services. A sensing service can also be any of the six scenarios shown in Figure 2, without limitation.

[0174] The user of the perception service can be in various forms. For example, the user of the perception service can be a terminal, or an application or software in the terminal, without limitation. In summary, the user of the perception service can be a user who requires the perception service.

[0175] The charging configuration information may also be charging function information, charging configuration information of the perception service, or charging function information of the perception service, etc.

[0176] For example, the billing configuration information is billing configuration information of the perception service, and the billing configuration information of the perception service is used to perform billing processing on the perception service;

[0177] For example, the billing configuration information is billing function information of the perception service, and the billing function information of the perception service is used to perform billing processing on the perception service;

[0178] For example, the billing configuration information is billing function information, and the billing function information is used to perform billing processing on the perception service.

[0179] In summary, the term "billing configuration information" is only an example, and future standards may adopt terminology with similar or identical meanings.

[0180] The charging configuration information may include one or both of a charging policy and a charging parameter.

[0181] For example, the charging configuration information includes a charging policy, which indicates a policy when charging for the perception service;

[0182] For another example, the charging configuration information includes charging parameters, which indicate parameters for charging the sensing service;

[0183] For another example, the charging configuration information includes a charging policy and charging parameters, which respectively indicate a policy and parameters for charging the perception service.

[0184] Through the above-mentioned billing strategy and / or billing parameters, the embodiment of the present application can support billing processing for perception services.

[0185] In a possible implementation, the billing policy includes one or both of billing granularity and billing method.

[0186] Through the above-mentioned billing granularity and / or billing method, the data function network element can complete the statistical processing of the perception service, and based on the information obtained from the statistical processing, the embodiment of the present application can support billing processing of the perception service.

[0187] When the charging policy includes charging granularity, the charging granularity may include one or both of service-based charging and quality of service (QoS)-based charging.

[0188] Billing granularity includes service-based billing, which allows for differentiated billing for different sensing services. For example, sensing service 1 is billed at rate 1, while sensing service 2 is billed at rate 2. Since the type of sensing service 1 is different from that of sensing service 2, rate 1 can be different from rate 2.

[0189] Billing granularity includes QoS-based billing, which allows for differentiated billing for services or flows that implement different QoS requirements. For example, services or flows that implement QoS 1 are billed at Rate 3, while services or flows that implement QoS 2 are billed at Rate 4. QoS 1 is different from QoS 2, and Rate 3 is different from Rate 4.

[0190] The billing granularity includes service-based billing and QoS-based billing. The perception service can be charged according to both service-based billing and QoS-based billing granularity.

[0191] When the billing granularity is service-based billing, the data function network element can collect statistics based on the types of perception services performed by perception service users and obtain corresponding billing information to support billing processing for the perception services.

[0192] When the billing granularity is based on QoS flow, the data function network element can count the QoS flows of the perception services performed by perception service users and obtain corresponding billing information to support billing processing for the perception services.

[0193] When the billing granularity is service-based billing and service quality flow-based billing, the data function network element can collect statistics based on the service quality flow and type of the perception service performed by the perception service user, and obtain corresponding billing information to support billing processing for the perception service.

[0194] When the charging policy includes a charging method, the charging method may include one or both of online charging and offline charging.

[0195] When the billing method includes online billing, the account balance of the perception service user is monitored online or in real time. When the user account balance is exhausted, the system can control the perception service user to stop using the perception service in real time.

[0196] When the billing method includes offline billing, the account balance of the awareness service user is updated at a specified time or periodically. When the user account balance is exhausted, the system can control the awareness service user to stop using the awareness service.

[0197] When the billing method includes online billing and offline billing, billing may be performed according to the online billing method during the first time period, and according to the offline billing method at a certain time in the designated second time period.

[0198] When the billing method is online billing, the data function network element can obtain the billing information of the perception service in real time, which is conducive to real-time monitoring of the account balance of the perception service user and timely stopping the perception service user from continuing to use the perception service when the account balance of the perception service user is exhausted.

[0199] Optionally, the embodiment of the present application may also support reminding the user of the perception service to pay when the account balance of the perception service user reaches a certain ratio or threshold value. In this way, the perception service user can pay the fee in time.

[0200] When the billing method is offline billing, the data function network element can obtain the billing information of the perception service at a specified time, which is conducive to reducing the signaling interaction overhead of the data function network element. For example, the data function network element does not need to frequently report the billing information of the perception service to the perception service control network element.

[0201] Exemplarily, the charging parameters include one or more of a charging mode, a charging event, a first charging quota, or a threshold value of a charging event.

[0202] The charging parameters include a charging mode, which is used to indicate a mode for charging the sensing service;

[0203] The charging parameters include charging events, which are used to indicate the conditions for reporting charging information of the perception service;

[0204] The charging parameters include a first charging quota, which is used to indicate a charging quota for the perception service.

[0205] When the charging parameters include a charging mode, the data function network element may determine a charging mode for the perception service.

[0206] When the charging parameters include charging events, the data function network element may determine a condition for reporting charging information of the perception service to the perception service control network element.

[0207] When the billing parameters include a first billing quota, the data function network element can determine the initial quota for the perception service user. By issuing the first billing quota, the number of call records and the amount of information sent by the data function network element to the perception service control network element can be controlled, thereby reducing signaling interaction overhead and the impact on the billing function network element.

[0208] When the charging parameters include a threshold value of a charging event, the data function network element may determine specific conditions for reporting the charging information of the perception service to the perception service control network element.

[0209] In one possible implementation, the billing mode includes one or more of traffic-based billing, duration-based billing, billing based on the time point of service occurrence, billing based on the area where the service occurs, billing based on the type of service, billing based on the perception accuracy of the service, or billing based on the number of times the service occurs.

[0210] For example, the billing mode includes flow-based billing, which can count the traffic used by users of the sensing service when performing the sensing service and charge the sensing service based on the traffic;

[0211] For example, the billing mode includes time-based billing, which can count the time when the perception service user performs the perception service and charge the perception service based on the time;

[0212] For example, the billing mode includes billing based on the time point when the service occurs. The time point when the perception service user performs the perception service can be counted and the perception service can be billed based on the time point. For example, if the time point when the perception service user performs the perception service is 10:00, the perception service performed by the perception service user between 0:00 and 12:00 is charged using rate 1; if the time point when the perception service user performs the perception service is 15:00, the perception service performed by the perception service user between 12:00 and 17:00 is charged using rate 2; if the time point when the perception service user performs the perception service is 22:00, the perception service performed by the perception service user between 17:00 and midnight is charged using rate 3.

[0213] ■Optionally, when the perception service user starts the perception service at 10:00 and ends the perception service at 15:00, rate 1 can be used to charge the perception service user for using the perception service during 10:00-12:00, and rate 2 can be used to charge the perception service user for using the perception service during 12:00-15:00. When the service occurrence time reaches 12:00, the billing event report can be triggered.

[0214] For example, the billing mode includes billing based on the number of service occurrences, and the number of times the perception service user performs the perception service can be counted, and the perception service can be billed based on the number of times.

[0215] For example, the billing model includes billing based on the area where the service occurs. This can determine the area in which the user of the awareness service performs the awareness service and charge the awareness service based on that area. For example, if the user performs the awareness service in area 1, the awareness service can be charged at rate 1; if the user performs the awareness service in area 2, the awareness service can be charged at rate 2.

[0216] For example, the billing model includes billing based on service type, which can be used to bill different types of sensing services. For example, if a sensing service user performs sensing service 1, rate 1 will be used to bill sensing service 1; if a sensing service user performs sensing service 2, rate 2 will be used to bill sensing service 2. The type of sensing service 1 is different from the type of sensing service 2. For example, if the billing model includes billing based on service-specific perception accuracy, different perception accuracies can be billed. For example, if a user of a perception service performs perception service 1 with a perception accuracy of 1, rate 1 can be used for billing of perception service 1; if a user of a perception service performs perception service 1 with a perception accuracy of 2, rate 2 can be used for billing of perception service 1. Perception accuracy can include one or more of the following: positioning accuracy, velocity estimation accuracy, imaging accuracy, missed detection pattern, false alarm probability, perception resolution, and latency.

[0217] By using one or more of the above-mentioned charging parameters, the embodiment of the present application can support the completion of charging processing for the perception service. For example, the data function network element can determine the specific content that needs to be counted when performing perception service on the perception service user.

[0218] In a possible implementation, the billing event includes one or more of traffic reaching a threshold, duration reaching a threshold, a change in the time point of service occurrence, or the number of service occurrences reaching a threshold.

[0219] For example, a billing event includes traffic reaching a threshold, and traffic information of a user performing a perception service can be reported (which can be one of the billing information for the perception service). For example, the traffic threshold is 80M. When the traffic used by the perception service user during the perception service reaches 80M, the traffic information of the perception service user during the perception service can be reported to other network elements, which can then use this information to bill for the perception service.

[0220] For example, a billing event includes a duration reaching a threshold, and the duration information of the perception service user performing the perception service can be reported (which can be one of the billing information of the perception service). For example, the duration threshold is 80 hours. When the duration of the perception service user performing the perception service reaches 80 hours, the duration information of the perception service user performing the perception service can be reported to other network elements, and the other network elements can use this information to bill the perception service.

[0221] For example, the billing event includes a change in the time point at which the service occurs, and the time information of the perception service user when performing the perception service can be reported (which can be one of the billing information of the perception service). Exemplarily, the time point at which the service occurs is 13:00, and the time point when the perception service user performs the perception service is past 12:00, then the time information of the perception service user when performing the perception service can be reported to other network elements, and other network elements will bill the perception service accordingly. Exemplarily, when the perception service user starts the perception service at 10:00 and ends the perception service at 15:00, when the service occurrence time reaches 12:00, the billing event report can be triggered.

[0222] Optionally, when a billing event includes a change in the time at which a service occurs, the billing event may also include the time at which the service ends. For example, if a user of a perception service performs a perception service, the service occurs at 17:00 and ends at 23:00, and the perception service can be charged based on the service occurrence and end times.

[0223] For example, a billing event includes the number of service occurrences reaching a threshold, and information about the number of occurrences when the perception service user performs the perception service can be reported (which can be one of the billing information for the perception service). For example, the threshold for the number of service occurrences is 50 times. When the number of service occurrences when the perception service user performs the perception service reaches 50 times, the information about the number of service occurrences when the perception service user performs the perception service can be reported to other network elements, which can then use this information to bill the perception service.

[0224] Through one or more of the above charging events, the embodiment of the present application can support charging processing for the perception service. For example, the data function network element can determine the conditions for reporting charging information to the perception service control network element.

[0225] When the billing parameter includes the first billing quota, the first billing quota may be one or more of a duration quota, a traffic quota, or a service occurrence times quota.

[0226] For example, the first billing quota is a duration quota. When the duration of the perception service user performing the perception service does not reach the quota or a fixed ratio of the quota (for example, 80%), the data function network element does not need to report the billing information of the perception service user. When the duration of the perception service user performing the perception service reaches the quota or a fixed ratio of the quota (for example, 80%), the data function network element reports the billing information of the perception service user.

[0227] For example, the first billing quota is a traffic quota. When the traffic of the perception service user when performing the perception service does not reach the quota or a fixed ratio of the quota (for example, 80%), the data function network element does not need to report the billing information of the perception service user. When the traffic of the perception service user when performing the perception service reaches the quota or a fixed ratio of the quota (for example, 80%), the data function network element reports the billing information of the perception service user.

[0228] For example, the first billing quota is a service occurrence quota. When the number of service occurrences of the perception service user when performing the perception service does not reach the quota or a fixed ratio of the quota (for example, 80%), the data function network element does not need to report the billing information of the perception service user. When the number of service occurrences of the perception service user when performing the perception service reaches the quota or a fixed ratio of the quota (for example, 80%), the data function network element reports the billing information of the perception service user.

[0229] By issuing the first billing quota, the number of call records and the amount of information sent from the data function network element to the perception service control network element can be controlled, thereby reducing signaling interaction overhead. This also reduces the impact on the billing function network element's load and facilitates the billing function network element's reconciliation of perception services.

[0230] In the embodiment of the present application, the description of the billing information of the perception service user can be found in Table 1. The content shown in Table 1 is only an example and is not a final limitation.

[0231] Table 1

[0232] As shown in Table 1, the billing information includes at least one of the following:

[0233] URR ID field, which indicates the identifier of the usage reporting rule (URR);

[0234] The start time field indicates the start time of the sensing service user's sensing service;

[0235] The end time field indicates the end time of the sensing service user's sensing service;

[0236] The volume usage field indicates the traffic usage of the user performing the sensing service.

[0237] The duration field indicates the duration of the user's use of the service.

[0238] The events usage field indicates the number of times a service occurs when the user performs the service.

[0239] The location field indicates the area where the user of the sensing service performs the sensing service.

[0240] In specific applications, some or all of the parameters described in Table 1 may be selected.

[0241] It should be noted that URR can be understood as a billing group. For example, services with the same rate and the same statistical method belong to the same billing group. For example, if the rate of Service 1 and Service 2 are the same and both are billed using traffic, then Services 1 and 2 can belong to the same billing group. The data function network element can accumulate the traffic of Service 1 and Service 2 and report the billing information of Service 1 and Service 2 when the traffic reaches the threshold.

[0242] Based on the above-mentioned billing information, the embodiment of the present application can support billing processing for perception services.

[0243] In a possible implementation, the threshold of the charging event may include one or more of a traffic threshold, a duration threshold, or a service occurrence count threshold.

[0244] For example, when the threshold of the billing event includes a flow threshold, the flow threshold may be a fixed ratio of the first billing quota. For example, if the first billing quota is 100M and the fixed ratio of the billing quota is 80%, the flow threshold may be 80M.

[0245] For example, when the threshold of the billing event includes a duration threshold, the duration threshold may be a fixed ratio of the first billing quota. For example, if the first billing quota is 100 hours and the fixed ratio of the billing quota is 80%, the duration threshold may be 80 hours.

[0246] For example, when the threshold of the charging event includes a threshold of the number of service occurrences, the duration threshold may be a fixed ratio of the first charging quota.

[0247] Exemplarily, the first billing quota is 100 times, the fixed ratio of the billing quota is 80%, and the threshold value of the number of service occurrences may be 80 times.

[0248] By using one or more of the above thresholds for charging events, the embodiment of the present application can support charging processing for the perception service. For example, the data function network element can determine the specific conditions for reporting charging information to the perception service control network element.

[0249] For a description of the charging parameters, please refer to Table 2. The contents shown in Table 2 are only examples and are not intended to be final limitations.

[0250] Table 2

[0251] As shown in Table 2, the billing parameters include at least one of the following:

[0252] URR ID field, which indicates the identifier of the usage reporting rule;

[0253] Charging mode field, which indicates the charging mode;

[0254] Charging trigger field, which indicates the charging event;

[0255] The volume threshold field indicates the volume threshold.

[0256] The time threshold field indicates the duration threshold.

[0257] The event threshold field indicates the threshold for the number of service occurrences.

[0258] Based on one or more of the above-mentioned billing parameters, the embodiment of the present application can support billing processing for perception services.

[0259] In specific applications, some or all of the parameters described in Table 2 may be selected.

[0260] When the charging parameters include a charging mode, the data function network element may determine a charging mode for the perception service.

[0261] When the charging parameters include charging events, the data function network element may determine a condition for reporting charging information of the perception service to the perception service control network element.

[0262] When the billing parameters include a first billing quota, the data function network element can determine the initial quota for the awareness service user. Furthermore, by issuing the first billing quota, the number of call records and the amount of information sent from the data function network element to the awareness service control network element can be controlled, thereby reducing signaling interaction overhead and the load on the billing function network element.

[0263] When the charging parameters include a threshold value of a charging event, the data function network element may determine specific conditions for reporting the charging information of the perception service to the perception service control network element.

[0264] S402. The perception service control network element sends charging configuration information to the data function network element.

[0265] Correspondingly, the data function network element receives the charging configuration information from the perception service control network element.

[0266] S403: The data function network element performs billing processing on the sensing service according to the billing configuration information.

[0267] The data function network element can obtain the perception data of the perception service user when performing the perception service for billing processing.

[0268] Exemplarily, the data function network element counts the traffic volume of the perception service based on the billing granularity, for example, counting the duration, traffic volume, or number of occurrences of the perception service, and obtains billing information corresponding to the perception service. When it is determined that the conditions for reporting the billing information of the perception service are met, for example, after the data function network element counts the traffic volume of the perception service and determines that the traffic volume of the perception service has reached a traffic threshold, the data function network element may report the billing information of the perception service to the perception service control network element.

[0269] Through the above technical solution, the data function network element can perform billing processing on the perception service performed by the perception service user according to the billing configuration information, thereby supporting the billing processing of the perception service. In addition, by deploying the data function network element, the embodiment of the present application can support reducing the overall time required for the billing processing of the perception service. For example, the data function network element performs statistical processing on the perception data of the perception service obtained according to the billing configuration information, obtains the corresponding billing information, and feeds back the billing information. The network element responsible for the billing function directly performs billing processing on the perception service according to the billing information.

[0270] The method shown in Figure 4 is further described below in conjunction with Figures 5 to 8. For ease of understanding and explanation, the following description is made by taking SSCF as the aforementioned perception service control network element and SDPF as the data function network element as an example.

[0271] FIG5 is a schematic diagram of an interactive process of a billing method 500 for a sensing service according to an embodiment of the present application. As shown in FIG5 , the method includes:

[0272] S501. SSCF sends first information to a charging function (CHF).

[0273] Correspondingly, the CHF receives the first information, wherein the first information is used to request charging parameters.

[0274] When the SSCF determines that charging processing needs to be performed on the perception service, it can send first information for requesting charging parameters to the CHF. The CHF can send the charging parameters to the SSCF according to the first information.

[0275] Optionally, the first information may also carry indication information of the "charging policy corresponding to a specific service." For example, for a location-aware service, the SSCF may obtain the charging parameters for the location-aware service from the CHF through the first information (e.g., the first information includes indication information for indicating the location-aware service); for a speed-aware service, the SSCF may obtain the charging parameters for the speed-aware service from the CHF through the first information (e.g., the first information includes indication information for indicating the speed-aware service). In this way, the charging parameters can be obtained in a targeted manner to support charging processing for users of the perception service.

[0276] Optionally, when the SSCF obtains the charging parameters from the CHF, the SSCF may request to obtain the charging parameters of the predefined awareness service. In this way, the SSCF does not need to indicate to the CHF the type information of the awareness service used by the awareness service user.

[0277] The first information may also be replaced by other terms, for example, it may be replaced by charging parameter request information or request information, etc., without limitation. In summary, the term first information is only an example, and future standards may adopt term names with similar or identical meanings.

[0278] S502. CHF sends charging parameters to SSCF.

[0279] Correspondingly, the SSCF receives charging parameters from the CHF.

[0280] S503. SSCF sends charging configuration information to SDPF.

[0281] Correspondingly, SDPF receives the charging configuration information from SSCF.

[0282] The charging policy can be predefined or preconfigured. The SSCF can determine the charging policy on its own.

[0283] For example, a correspondence between charging parameters and charging policies can be established and configured in the SSCF. After the SSCF obtains the charging parameters from the CHF, it can determine a corresponding charging policy based on the correspondence and the obtained charging parameters.

[0284] Optionally, multiple charging policies may be pre-configured, and the SSCF selects a charging policy from the multiple charging policies.

[0285] After the SSCF determines the charging policy, it may send the charging policy and charging parameters to the SDPF.

[0286] S504. SDPF performs billing processing on the sensing service according to the billing configuration information.

[0287] For the description of S504 , please refer to the description of S403 and will not be repeated here.

[0288] Through the above solution, the perception service control network element can obtain the charging parameters from the charging function network element. In this way, the charging parameters can be obtained.

[0289] FIG5 is described by taking the example that the SSCF obtains the charging parameters from the CHF and the charging policy is predefined or preconfigured. However, the charging parameters may also be predefined or preconfigured, as shown in FIG6 .

[0290] FIG6 is a schematic diagram of an interactive process of a billing method 600 for a perception service according to an embodiment of the present application. As shown in FIG6 , the method includes:

[0291] S601. SSCF sends second information to a policy control function (PCF).

[0292] Correspondingly, the PCF receives the second information, which is used to request a charging policy.

[0293] When the SSCF determines that billing processing is required for the perception service, it may send a second message requesting a billing policy to the PCF. The PCF may determine the billing policy to be sent to the SSCF based on the second message. Alternatively, before performing billing processing for the perception service, the SSCF may send a second message requesting a billing policy to the PCF. The PCF may determine the billing policy to be sent to the SSCF based on the second message.

[0294] Optionally, the second information may also carry indication information regarding the "charging policy corresponding to a specific service." For example, for location-aware services, the SSCF may obtain the charging policy for location-aware services from the PCF via the second information (e.g., the second information includes indication information indicating the location-aware service). For speed-aware services, the SSCF may obtain the charging policy for speed-aware services from the PCF via the second information (e.g., the second information includes indication information indicating the speed-aware service). In this way, charging policies can be obtained in a targeted manner to support billing for users of these services.

[0295] Optionally, when the SSCF obtains the charging policy from the PCF, the SSCF may request to obtain the charging policy of the predefined awareness service. In this way, the SSCF does not need to indicate to the PCF the type information of the awareness service used by the awareness service user.

[0296] The second information may also be replaced by other terms, for example, charging policy request information or request information, etc., without limitation. In summary, the term second information is only an example, and future standards may adopt terms with similar or identical meanings.

[0297] S602. The PCF sends a charging policy to the SSCF.

[0298] Correspondingly, the SSCF receives the charging policy from the PCF.

[0299] S603. SSCF sends charging configuration information to SDPF.

[0300] Correspondingly, SDPF receives the charging configuration information from SSCF.

[0301] The charging parameters may be predefined or preconfigured. Therefore, the SSCF may determine the charging parameters on its own.

[0302] For example, a correspondence between charging parameters and charging policies can be established and configured in the SSCF. After the SSCF obtains the charging policy from the PCF, it can determine the corresponding charging parameters based on the correspondence and the obtained charging policy.

[0303] Optionally, multiple charging parameters may be preconfigured, and the SSCF selects one charging parameter from the multiple charging parameters.

[0304] After the SSCF determines the charging parameters, it may send the charging policy and charging parameters to the SDPF.

[0305] S604. SDPF performs billing processing on the sensing service according to the billing configuration information.

[0306] For the description of S604 , please refer to the description of S403 and will not be repeated here.

[0307] Through the above solution, the perception service control network element can obtain the charging policy from the policy control network element. In this way, the charging policy can be obtained.

[0308] Figures 5 and 6 illustrate the example of the SSCF obtaining charging parameters and charging policies from the CHF or PCF, respectively. However, embodiments of the present application also support scenarios where both charging policies and charging parameters are predefined or preconfigured. The SSCF can select a charging policy and charging parameters from one or more preconfigured charging parameters and charging policies and send the determined charging policy and charging parameters to the SDPF. This reduces the signaling overhead required for the SSCF to obtain charging parameters and / or charging policies.

[0309] Figures 4 to 6 describe the example of SSCF sending billing configuration information to SDPF and SDPF performing billing processing on the perception service based on the billing configuration information. After SDPF completes the billing processing of the perception service, it can also interact with SSCF, as shown in Figure 7.

[0310] FIG7 is a schematic diagram of an interactive process of a billing method 700 for a sensing service according to an embodiment of the present application. As shown in FIG7 , the method includes:

[0311] S701. SDPF sends billing information of the sensing service to SSCF.

[0312] Correspondingly, the SSCF receives the billing information of the perception service from the SDPF.

[0313] For the description of the billing information of the perception service, please refer to the description of S403 above and will not be repeated here.

[0314] S702. The SSCF sends third information to the CHF.

[0315] Correspondingly, the CHF receives the third information, where the third information is used to request a second charging quota for the perception service.

[0316] When the SDPF determines that the billing method is online billing, it can obtain the billing information of the perception service in real time, and when it determines that the billing information of the perception service is satisfied, it can send the billing information of the perception service to the SSCF.

[0317] When the SDPF determines that the billing method is offline billing, it can obtain the billing information of the perception service at a specified time, and when it determines that the billing information of the perception service is satisfied, it can send the billing information of the perception service to the SSCF.

[0318] When the SSCF determines that the account balance of the awareness service user is not exhausted, it can send third information for requesting the second charging quota of the awareness service to the CHF. This is beneficial for the SDPF to determine whether to report the charging information of the awareness service according to the new charging quota.

[0319] The third information may also be replaced by other terms, for example, billing quota request information or request information, etc., without limitation. In summary, the term third information is only an example, and future standards may adopt terms with similar or identical meanings.

[0320] S703 : CHF sends the second charging quota of the perception service to SSCF.

[0321] Correspondingly, the SSCF receives the second charging quota of the sensing service.

[0322] S704. SSCF sends the second charging quota of the perception service to SDPF.

[0323] Correspondingly, the SDPF receives the second charging quota of the perception service.

[0324] After receiving the second charging quota, the SDPF may determine a new charging event threshold, and may determine whether the charging information of the perception service needs to be reported based on the new charging event threshold.

[0325] Optionally, the second billing quota may be the same as the first billing quota or may be different from the first billing quota, which is not limited.

[0326] Through the above solution, the embodiment of the present application can support the SDPF to determine the second billing quota for the perception service. In addition, through the second billing quota for the interactive perception service, the billing function network element can check the account balance of the perception service user based on the third information, thereby avoiding the situation where the billing quota is exhausted and the perception service user continues to use the perception service, thereby causing economic losses.

[0327] It should be noted that the above-mentioned second billing quota can be issued cyclically until the account balance of the perception service user is used up.

[0328] Figures 4 to 7 are described using the example of the interaction of billing configuration information and billing information of perceived services between SSCF and SDPF. SSCF can also interact with other network elements to start or execute the process of sending billing configuration information to SDPF, as shown in Figure 8.

[0329] FIG8 is a schematic diagram of an interactive process of a billing method 800 for a sensing service according to an embodiment of the present application. As shown in FIG8 , the method includes:

[0330] S801. A user aware of the service sends fourth information to the SSCF.

[0331] Correspondingly, the SSCF receives the fourth information, which is used to request the sensing service.

[0332] The SSCF may determine, based on the fourth information, that charging processing needs to be performed on the perception service, and may start executing the following process.

[0333] The fourth information may also be replaced by other terms, for example, perception service request information or request information, etc., without limitation. In summary, the term fourth information is only an example, and future standards may adopt term names with similar or identical meanings.

[0334] S802. SSCF determines charging configuration information.

[0335] For the description of S802 , please refer to the description of S401 and will not be repeated here.

[0336] S803. SSCF sends charging configuration information to SDPF.

[0337] Correspondingly, the SDPF receives the charging configuration information.

[0338] S804. SDPF performs billing processing on the sensing service according to the billing configuration information.

[0339] For the description of S804 , please refer to the description of S404 and will not be repeated here.

[0340] Through the technical solution described in Figure 8, SSCF can determine the billing configuration information based on the information sent by the perception service user to request the perception service, and complete the process of exchanging billing configuration information with SDPF, thereby supporting billing processing for the perception service.

[0341] The contents described in Figures 4 to 8 are described by taking the example of multiple network elements interacting with each other to complete the billing process for the perception service. The following describes how to complete the registration of the perception service user in conjunction with Figure 9.

[0342] FIG9 is a schematic diagram of an interactive process of a billing method 900 for a perception service according to an embodiment of the present application. As shown in FIG9 , the method includes:

[0343] S901. The perception service user sends registration information to the perception service user management network element.

[0344] Correspondingly, the perception service user management network element receives the registration information.

[0345] The Awareness Service User Management NE is responsible for managing awareness service users and can be responsible for one or more of the following:

[0346] ·Perceive business users' account opening and account closing;

[0347] ·Contract subscription for sensing services;

[0348] Authentication and authorization of business users;

[0349] Account balance management for perception service users. Additionally, the registration information is used to request the completion of the perception service user registration. For a description of the registration information, see Table 3. The contents shown in Table 3 are for illustrative purposes only and are not intended to be definitive.

[0350] Table 3

[0351] As shown in Table 3, the registration information may include at least one of the following:

[0352] User name field, which is used to indicate the name of the awareness service user;

[0353] User ID field, which is used to indicate the ID of the user of the awareness service (which is a unique ID);

[0354] User type field, which is used to indicate whether the perceived service user is an internal user or an external user;

[0355] Authentication data field, which is used to indicate the user password of the awareness service user, etc., and is used to authenticate the identity of the awareness service user;

[0356] The field of the awareness service type allowed to be requested is used to indicate the list of awareness service types supported by the awareness service user;

[0357] The service prohibited area field is used to indicate that the user of the sensing service is prohibited from performing the sensing service in the area, which can be a cell identifier or a location identifier;

[0358] User priority field, which is used to identify the priority of the user of the awareness service, and can be a value from 1 to 15. The smaller the value, the higher the priority;

[0359] The charging attribute field indicates the charging attributes of the user of the service, including postpaid, prepaid, and free users.

[0360] The service subscription information field is used to indicate relevant information of the subscribed sensing service, such as service type, time, duration, and sensing accuracy.

[0361] Through the above registration information, the embodiment of the present application can support the registration management of perception service users.

[0362] In one possible implementation, the registration information includes the name of the awareness service user, the awareness service user's identifier, the user type of the awareness service user, the authentication data of the awareness service user, and billing attributes. Using one or more of the above information, the awareness service user management network element can obtain relevant information about the awareness service user and, based on this information, manage the registration of the awareness service user.

[0363] In one possible implementation, the registration information further includes at least one of the following: the type of awareness service allowed to be requested, the service prohibited area, the user priority, or the service subscription information. Through one or more of the above, the awareness service user management network element can further complete the registration management of the awareness service user.

[0364] S902. The perception service user management network element sends a first response message to the perception service user.

[0365] Correspondingly, the awareness service user receives the first response information. The first response information is used to respond to the registration information, for example, the first response information indicates that the awareness service user has successfully registered, or the first response information indicates that the awareness service user has failed to register.

[0366] Through the above method, the embodiment of the present application can support the completion of the registration process for perception service users.

[0367] S903: The perception service user sends a perception service request message to the perception service user management network element.

[0368] Correspondingly, the perception service user management network element receives the perception service request information, which is used to request the perception service.

[0369] S904. The perception service user management network element sends second response information to the perception service user.

[0370] Correspondingly, the user of the sensing service receives the second response information. The second response information is used to respond to the request information of the sensing service, for example, the second response information indicates that the user of the sensing service is allowed to perform the sensing service, or the second response information indicates that the user of the sensing service is not allowed to perform the sensing service.

[0371] When the awareness service user management network element allows the awareness service user to perform the awareness service, the awareness service user management network element may determine parameters such as the type and area of ​​the awareness service.

[0372] Through the method described in FIG. 9 , the embodiment of the present application can support perception service users to request or use perception services.

[0373] The awareness service user management network element may also exchange information about the awareness service user with other network elements. For example, the awareness service user management network element exchanges charging information initialization information of the awareness service user with the CHF or the account balance management function (ABMF) network element.

[0374] When the perception service user completes the registration process and completes the request for perception service, SSCF, SDPF, CHF and PCF can exchange information to complete the billing processing of the perception service. For specific content, please refer to the description of Figures 4-8 and will not be repeated here.

[0375] It should be noted that Figures 5-9 above are separate embodiments, and the contents shown in Figures 5-9 can be combined with each other to form new embodiments. For example, the method shown in Figure 5 can be combined with the method shown in Figure 6; the method shown in Figure 5 can be combined with the method shown in Figure 7, and so on. In summary, the embodiments of this application do not limit the specific combination of the contents shown in Figures 5-9.

[0376] Finally, the device embodiment of the embodiment of the present application is introduced.

[0377] To implement the functions of the methods provided herein, the network elements may include hardware structures and / or software modules, with the functions implemented in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is implemented in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0378] Figure 10 is a schematic block diagram of a communication device 1000 according to an embodiment of the present application. The communication device 1000 includes a processor 1010 and a communication interface 1020, which may be interconnected via a bus 1030. The communication device 1000 may be a perception service control network element, a data function network element, a perception service user management network element, a CHF network element, a PCF network element, or the like.

[0379] Optionally, the communication device 1000 may further include a memory 1040. The memory 1040 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or portable read-only memory (CD-ROM), and is used for related instructions and data.

[0380] The processor 1010 may be one or more central processing units (CPUs). In the case where the processor 1010 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

[0381] When the communication device 1000 is a perception service control network element, illustratively, the processor 1010 is configured to perform the following operations: determine charging configuration information; send the charging configuration information to a data function network element, etc.

[0382] When the communication device 1000 is a data function network element, illustratively, the processor 1010 is configured to perform the following operations: receive charging configuration information; perform charging processing on the perception service according to the charging configuration information, etc.

[0383] The above contents are described as examples only. The communication device 1000 is a perception service control network element or a data function network element, which is responsible for executing the methods or steps related to the perception service control network element or the data function network element in the above method embodiments.

[0384] The above-mentioned communication device 1000 may also be other network elements, which will not be described in detail.

[0385] The above description is only an exemplary description, and for specific details, please refer to the contents shown in the above method embodiment.

[0386] It should be noted that the implementation of each operation in FIG10 may also correspond to the corresponding description of the method embodiments shown in FIG4 to FIG9 .

[0387] Figure 11 is a schematic block diagram of a communication device 1100 according to an embodiment of the present application. The communication device 1100 may be a perception service control network element, a data function network element, a perception service user management network element, a CHF network element, a PCF network element, or the like.

[0388] The communication device 1100 includes an interface unit 1110 and a processing unit 1120. The interface unit 1110 may include a transmitting unit and a receiving unit. The transmitting unit is configured to execute a transmitting operation of the communication device, and the receiving unit is configured to execute a receiving operation of the communication device. For ease of description, this embodiment of the application combines the transmitting unit and the receiving unit into a single transceiver unit. This is described here as a unified description and will not be repeated later.

[0389] When the communication device 1100 is a perception service control network element, illustratively, the interface unit 1110 is used to send charging configuration information, and the processing unit 1120 is used to determine the charging configuration information.

[0390] When the communication device 1100 is the second device, illustratively, the interface unit 1110 is configured to receive charging configuration information, and the processing unit 1120 is configured to perform charging processing on the sensing service according to the charging configuration information.

[0391] The above contents are described as examples only. The communication device 1000 is a perception service control network element or a data function network element, which is responsible for executing the methods or steps related to the perception service control network element or the data function network element in the above method embodiments.

[0392] Optionally, the communication device further includes a storage unit 1130, which is used to store a program or code for executing the aforementioned method.

[0393] The above-mentioned communication device 1000 may also be other network elements, which will not be described in detail.

[0394] The above description is only an exemplary description, and for specific details, please refer to the contents shown in the above method embodiment.

[0395] It should be noted that the device embodiment shown in Figure 11 is used to implement the contents described in Figures 4 to 9. The specific execution steps and methods of the device shown in Figure 11 can refer to the contents described in the above method embodiments.

[0396] The present application also provides a chip, including a processor, for calling and executing instructions stored in a memory from the memory, so that a communication device equipped with the chip executes the methods in the above examples.

[0397] The present application also provides another chip, comprising: an input interface, an output interface, and a processor, wherein the input interface, the output interface, and the processor are connected via an internal connection path, and the processor is configured to execute code in a memory. When the code is executed, the processor is configured to execute the methods in the above examples. Optionally, the chip also includes a memory, which is configured to store computer programs or code.

[0398] The present application also provides a processor for coupling with a memory, and for executing the methods and functions involving a network device or a terminal device in any of the above embodiments.

[0399] In another embodiment of the present application, a computer program product including instructions is provided. When the computer program product is run on a computer, the method of the above embodiment is implemented.

[0400] The present application also provides a computer program. When the computer program is executed in a computer, the method of the aforementioned embodiment is implemented.

[0401] In another embodiment of the present application, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program. When the computer program is executed by a computer, the method described in the above embodiment is implemented.

[0402] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

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

[0404] In the several embodiments provided in this application, the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0406] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0407] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

[0408] The above is only a specific implementation of the embodiment of the present application, but the scope of protection of the embodiment of the present application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the embodiment of the present application, and they should be included in the scope of protection of the embodiment of the present application. Therefore, the scope of protection of the embodiment of the present application should be based on the scope of protection of the claims.

Claims

1. A billing method for perception services, characterized in that: include: Determining billing configuration information, where the billing configuration information is used to perform billing processing on the perception service; Send the charging configuration information to the data function network element.

2. The method according to claim 1, characterized in that The charging configuration information includes one or both of a charging strategy and a charging parameter.

3. The method according to claim 2, characterized in that The charging configuration information includes the charging parameters, and the determining of the charging configuration information includes: Sending first information to a charging function network element, where the first information is used to request the charging parameter; The charging parameter is received from the charging function network element.

4. The method according to claim 2, characterized in that: The charging configuration information includes the charging parameters, and the determining of the charging configuration information includes: The charging parameters are preconfigured, or the charging parameters are predefined.

5. The method according to claim 2, characterized in that: The charging configuration information includes the charging policy, and the determining of the charging configuration information includes: Sending second information to a policy control network element, where the second information is used to request the charging policy; The charging policy is received from the policy control network element.

6. The method according to claim 2, characterized in that The charging configuration information includes the charging policy, and the determining of the charging configuration information includes: The charging policy is preconfigured, or the charging policy is predefined.

7. The method according to any one of claims 2 to 6, characterized in that The charging strategy includes one or both of a charging method and a charging granularity.

8. The method according to claim 7, characterized in that The charging method includes one or both of online charging and offline charging.

9. The method according to claim 7, characterized in that: The charging granularity includes one or both of service-based charging and service quality flow-based charging.

10. The method according to any one of claims 2 to 9, characterized in that The charging parameters include at least one of the following: A charging mode, a charging event, a first charging quota, or a threshold value of the charging event.

11. The method according to claim 10, characterized in that The billing mode includes at least one of the following: Billing based on traffic, billing based on duration, billing based on the time point when the service occurs, or billing based on the number of times the service occurs.

12. The method according to claim 10, characterized in that The billing event includes at least one of the following: The traffic volume reaches the threshold, the duration reaches the threshold, the time when the service occurs changes, or the number of service occurrences reaches the threshold.

13. The method according to claim 10, characterized in that The threshold of the charging event includes at least one of the following: Traffic threshold, duration threshold, or service occurrence number threshold.

14. The method according to any one of claims 1 to 13, characterized in that The method further comprises: receiving charging information of the sensing service from the data function network element; In response to the charging information, third information is sent to the charging function network element, where the third information is used to request a second charging quota for the perception service, and the second charging quota is associated with the charging information.

15. The method according to claim 14, characterized in that The method further comprises: receiving the second charging quota from the charging function network element; Send the second billing quota to the data function network element.

16. The method according to any one of claims 1 to 15, characterized in that Before determining the charging configuration information of the perception service, the method further includes: Receive fourth information from a user management function network element, where the fourth information is used to request the perception service.

17. A billing method for perception services, characterized in that: include: Receiving charging configuration information from the sensing service control network element; The sensing service is charged according to the charging configuration information.

18. The method according to claim 17, characterized in that The charging configuration information includes one or both of a charging strategy and a charging parameter.

19. The method according to claim 18, characterized in that The charging strategy includes one or both of a charging method and a charging granularity.

20. The method according to claim 18, characterized in that The charging method includes one or both of online charging and offline charging.

21. The method according to claim 18, characterized in that The charging granularity includes one or both of service-based charging and service quality flow-based charging.

22. The method according to any one of claims 17 to 21, characterized in that The charging parameters include at least one of the following: A charging mode, a charging event, a first charging quota, or a threshold value of the charging event.

23. The method according to claim 22, characterized in that The billing mode includes at least one of the following: Billing based on traffic, billing based on duration, billing based on the time point when the service occurs, or billing based on the number of times the service occurs.

24. The method according to claim 22, characterized in that The billing event includes at least one of the following: The traffic volume reaches the threshold, the duration reaches the threshold, the time when the service occurs changes, or the number of service occurrences reaches the threshold.

25. The method according to claim 22, characterized in that The threshold of the charging event includes at least one of the following: Traffic threshold, duration threshold, or service occurrence number threshold.

26. The method according to any one of claims 16 to 25, characterized in that The method further comprises: Sending charging information of the perception service to the perception service control network element; A second quota of the perception service is received from the perception service control network element, where the second charging quota of the perception service is determined according to the charging information.

27. A billing method for perception services, characterized in that: include: receiving registration information from a perception service user, the registration information being used to request completion of registration of the perception service user, the perception service user being a user requesting the perception service; Sending first response information to the awareness service user, where the first response information is used to respond to the registration information.

28. The method according to claim 27, characterized in that The method further comprises: Receiving request information from the perception service user, the request information being used to request the perception service; Sending second response information to the perception service user, where the second response information is used to respond to the request information.

29. The method according to claim 27 or 28, characterized in that The registration information includes: User name, user ID, user type, authentication data, and billing attributes.

30. The method according to claim 29, characterized in that The registration information also includes at least one of the following: The requested perceived service type, service prohibited area, user priority, or service subscription information is allowed.

31. A communication system, characterized in that: include: A perception service control network element, used to determine charging configuration information, wherein the charging configuration information is used to perform charging processing on the perception service; The perception service control network element is further used to send the charging configuration information to the data function network element; The data function network element is used to receive the charging configuration information, and is also used to perform charging processing on the perception service according to the charging configuration information.

32. A communication device, characterized in that: comprising a processor configured to, by executing a computer program or instructions, or, by means of a logic circuit, enabling the communication device to perform the method according to any one of claims 1 to 16; or, causing the communication device to perform the method according to any one of claims 17 to 26; or, The communication device is enabled to perform the method according to any one of claims 27 to 30.

33. A communication device, characterized in that: It includes a logic circuit and an input / output interface, wherein the input / output interface is used to input and / or output signals. The logic circuit is used to execute the method according to any one of claims 1 to 16; or, The logic circuit is used to execute the method according to any one of claims 17 to 26; or, The logic circuit is configured to execute the method according to any one of claims 27 to 30.

34. A computer-readable storage medium, characterized in that: The computer readable storage medium stores a computer program or instruction. When the computer program or instruction is executed on a computer, so that the method of any one of claims 1 to 16 is performed; or, so that the method of any one of claims 17 to 26 is performed; or, The method according to any one of claims 27 to 30 is performed.

35. A computer program product, characterized in that Contains instructions that, when executed on a computer, so that the method of any one of claims 1 to 16 is performed; or, so that the method of any one of claims 17 to 26 is performed; or, The method according to any one of claims 27 to 30 is performed.

Images