Charging method for sensing service, communication device and system

Abstract

The invention provides a charging method for a perception service, a communication device and a system, and relates to the technical field of perception. In the method, after a perception service control network element determines charging configuration information, the charging configuration information can be issued to a data function network element, and the data function network element performs charging processing on the perception service according to the charging configuration information, so that charging processing on the perception service can be supported.

Description

Technical Field

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

[0002] Wireless communication and wireless perception are both based on electromagnetic wave theory. The transmitter modulates the electromagnetic wave signal so that it carries the source information. The electromagnetic wave signal is affected by the wireless environment during propagation, that is, the electromagnetic wave signal is modulated by the environment and therefore also carries environmental information. The receiver can not only obtain the source information carried by the electromagnetic wave signal, but also extract the perception information reflecting the characteristics of the propagation environment by analyzing the electromagnetic wave signal, which makes the integration of communication and perception possible.

[0003] Communication systems are developing towards higher frequency bands, larger bandwidths, and denser distribution of large-scale antenna arrays, so that a single system can integrate perception and communication capabilities, allowing each system to improve performance. Perception can be used as a basic characteristic of communication systems, which can observe and sample the physical and biological worlds, thereby opening up a "new channel" for the integration of the physical and biological worlds with the digital world.

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

[0005] The present application provides a billing method and a communication device, which can support billing processing for perception services.

[0006] In a first aspect, a billing method for a perception service is provided, which is applied to a perception service control network element, and the method includes: determining billing configuration information, 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.

[0007] In the above scheme, 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, and the data function network element performs billing processing on the perception service according to the billing configuration information, thereby being able to support billing processing for the perception service.

[0008] By deploying data function network elements, the embodiments of the present application can support reducing 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 acquired perception service 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.

[0009] In the first aspect, the charging configuration information includes 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 parameters; and receiving the charging parameters from the charging function network element.

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

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

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

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

[0014] In this way, the charging strategy can be obtained.

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

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

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

[0018] 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 and continuing to use the perception service, thereby causing economic losses.

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

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

[0021] In a second aspect, a billing method for a perception service is provided, which is applied to a data function network element, and 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.

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

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

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

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

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

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

[0028] 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 a charging method and a charging granularity.

[0029] Through the above-mentioned billing granularity and / or billing method, the data functional 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.

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

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

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

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

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

[0035] When the billing granularity is based on the service quality flow, the data function network element can make 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.

[0036] When the billing granularity is service-based billing and service quality flow-based billing, the data function network element can perform appropriate statistics 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.

[0037] In combination with the solution described in any one of the first aspect and the second aspect, 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.

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

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

[0040] When the billing parameters include the first billing quota, the data function network element can determine the initial amount configured for the perception service user when performing the perception service. 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 the signaling interaction overhead. At the same time, the impact on the load of the billing function network element can also be reduced.

[0041] When the charging parameter includes a threshold value of a charging event, the data function network element may determine specific conditions for reporting charging information of the perception service to the perception service control network element. In combination 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 point when the service occurs, or charging based on the number of times the service occurs.

[0042] Through one or more of the above, 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 content that needs to be counted when performing the perception service for the perception service user.

[0043] 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 at which the service occurs changes, or the number of service occurrences reaches a threshold.

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

[0045] In combination with the solution described in any one of the first aspect and the second aspect, 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.

[0046] Through one or more of the above, 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.

[0047] On the third aspect, a billing method for a perception service is provided, comprising: 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; and sending a first response information to the perception service user, the first response information being used to respond to the registration information.

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

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

[0050] Through the method, the embodiment of the present application can support the perception service user to request to perform or use the perception service.

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

[0052] 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 the registration management of the awareness service user based on the relevant information.

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

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

[0055] In a fourth aspect, a communication system is provided, including: a perception service control network element, used to determine billing configuration information, and the billing configuration information 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.

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

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

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

[0059] Optionally, the communication system may further include a service-aware user management network element, which is used to execute the method described in the third aspect.

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

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

[0062] In a sixth aspect, a communication device is provided, comprising: 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.

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

[0064] In the seventh aspect, a communication device is provided, including: an interface unit, used to receive registration information from a perception service user, the registration information is used to request to complete the registration of the perception service user, and the perception service user is a user who requires the perception service; the interface unit is also used to send a first response information to the perception service user, and the first response information is used to respond to the registration information.

[0065] In a 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.

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

[0067] 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 perform the method described in the first aspect and any possible implementation of the first aspect; or enable the communication device to perform the method described in the second aspect and any possible implementation of the second aspect; or enable the communication device to perform the method described in the third aspect and any possible implementation of the third aspect.

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

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

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

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

[0072] 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 in the first aspect, the second aspect, or the third aspect.

[0073] The above-mentioned interface circuit may also be a communication interface. The above-mentioned processor may also be a logic circuit or a processing circuit.

[0074] In a fourteenth aspect, an embodiment of the present application provides a processor, which is coupled to a memory and is used to execute any possible method in the above-mentioned first aspect, second aspect or third aspect.

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

[0076] In a possible implementation, the above-mentioned communication device also includes a memory.

[0077] In a 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.

[0078] 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 a method as described in any possible manner in the first aspect, the second aspect or the third aspect above. BRIEF DESCRIPTION OF THE DRAWINGS

[0079] Figure 1 It is a schematic diagram of a communication system 100 to which an embodiment of the present application is applicable.

[0080] Figure 2 It is a schematic diagram of a perception scene 200 according to an embodiment of the present application.

[0081] Figure 3 It is a schematic diagram of the networking architecture 300 of an embodiment of the present application.

[0082] Figure 4 It is a schematic diagram of the interaction flow of the billing method 400 for the perception service according to an embodiment of the present application.

[0083] Figure 5 It is a schematic diagram of the interaction flow of the billing method 500 for the perception service according to an embodiment of the present application.

[0084] Figure 6 It is a schematic diagram of the interaction flow of the billing method 600 for the perception service according to an embodiment of the present application.

[0085] Figure 7 It is a schematic diagram of the interaction flow of the billing method 700 for the perception service according to an embodiment of the present application.

[0086] Figure 8 It is a schematic diagram of the interaction flow of the billing method 800 for the perception service according to an embodiment of the present application.

[0087] Fig. 9 It is a schematic diagram of the interaction flow of the billing method 900 for the perception service according to an embodiment of the present application.

[0088] Fig.10 is a schematic diagram of a communication device 1000 according to an embodiment of the present application.

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

[0090] The technical solution in this application will be described below in conjunction with the accompanying drawings.

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

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

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

[0094] 3. The various digital 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 execution order 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.

[0095] At the same time, any embodiment or design described in the present 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 related concepts in a concrete manner for ease of understanding.

[0096] 4. The terms "comprise", "include", "have" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or apparatus comprising 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.

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

[0098] The information enabled by the information is called information to be enabled. In the specific implementation process, there are many ways to enable the information to be enabled, such as but not limited to, the information to be enabled can be directly 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 relationship 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, the enabling of specific information can also be achieved by means of the arrangement order of each piece of information agreed in advance (such as specified by the protocol), thereby reducing the enabling overhead to a certain extent. At the same time, the common parts of each piece of information can also be identified and enabled uniformly to reduce the enabling overhead caused by enabling the same information separately.

[0099] 6. In this application, "pre-configuration" may include pre-definition, such as protocol definition. Among them, "pre-definition" can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including each network element), and this application does not limit its specific implementation method.

[0100] 7. The term "storage" or "saving" as used in this application may refer to saving in one or more memories. The one or more memories may be provided separately or integrated in an encoder or decoder, a processor, or a communication device. The one or more memories may also be partially provided separately and partially integrated in a decoder, a processor, or a communication device. The type of memory may be any form of storage medium, without limitation.

[0101] 8. The "protocol" referred to in this application may refer to a standard protocol in the field of communications, for example, the fourth generation (4 th generation, 4G) network, fifth generation (5 th generation, 5G) network protocol, NR protocol, 5.5G network protocol, sixth generation (6 th The present application does not limit the network protocols used in future communication systems.

[0102] 9. The dotted arrows or boxes in the schematic diagrams of the drawings in the specification of this application represent optional steps or optional modules.

[0103] 10. Unless otherwise specified, “ / ” indicates that the objects associated with each other are in an “or” relationship. For example, A / B can represent A or B. The “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 represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural.

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

[0105] In the present 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 relationship 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 by means of the arrangement order of each information agreed in advance (for example, specified by the protocol), thereby reducing the indication overhead to a certain extent. In addition, the information to be indicated can be sent 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.

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

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

[0108] The technical solution provided by this application can be applied to various communication systems, such as the fifth generation (5th The technical solutions provided in the present application can also be applied to future communication systems, such as the sixth generation mobile communication system. The technical solutions provided in the present 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 systems or other communication systems.

[0109] 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 Third Generation Partnership Project (3GPP) terminal. rdThe present invention relates to a user equipment (UE), terminal, fixed equipment, mobile station equipment or mobile device, subscriber unit, handheld device, vehicle-mounted equipment, 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) equipment, target tracking equipment, aircraft (such as drone, helicopter, multi-copter, quadcopter, or airplane), ship, remote control equipment, smart home equipment, industrial equipment, or a device built in the above equipment (such as a communication module, modem or chip in the above equipment), or other processing equipment connected to the wireless modem. For the convenience of description, the terminal device is described below by taking the terminal or UE as an example.

[0110] 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 that provides sidelink signals between UEs in scenarios such as V2X, D2D or P2P.

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

[0112] The network device in the embodiment of the present application may be a device for communicating with a terminal device, and the network device may also be referred to as an access network device or a wireless access network device, such as a base station. The network device in the embodiment of the present application may refer to a wireless 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 with 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, a modem or a 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 the base station function in D2D, V2X, and M2M communications, a network-side device in a 6G network, or a device that performs the base station function in a future communication system. 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 device.

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

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

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

[0116] First, a network architecture applicable to the embodiments of the present application is briefly introduced.

[0117] Figure 1 1 is a schematic diagram of a communication system 100 to which the present application embodiment is applicable. Figure 1 As shown, the communication system 100 includes: a radio access network (RAN) 100 and a core network (CN) 200. The RAN 100 includes at least one RAN node (such as 110a and 110b, collectively referred to as 110) and at least one terminal device (such as 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 ( Figure 1 The terminal device 120 is connected to the RAN node 110 in a wireless manner. The RAN node 110 is connected to the core network 200 in a wireless or wired manner. The core network device in the core network 200 and the RAN node 110 in the RAN 100 can be different physical devices, or can be the same physical device that integrates the core network logical function and the radio access network logical function.

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

[0119] The RAN node 110, which may also be sometimes referred to as an access network device, a RAN entity or an access node, etc., constitutes a part of a communication system to help terminal devices achieve wireless access. The multiple RAN nodes 110 in the communication system may be nodes of the same type or nodes of different types. In some scenarios, the roles of the RAN node 110 and the terminal device 120 are relative. For example, the network element 120i may be a helicopter or a drone, which may be configured as a mobile base station. For the terminal devices 120j that access the RAN 100 through the network element 120i, the network element 120i is a base station; but for the base station 110a, the network element 120i is a terminal device. The RAN node 110 and the terminal 120 are sometimes referred to as communication devices. For example, the network elements 110a and 110b may be understood as communication devices with base station functions, and the network elements 120a-120j may be understood as communication devices with terminal functions.

[0120] In one possible scenario, the RAN node may be a BS, an eNodeB, an access point (AP), a 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. The RAN node may be a macro base station (e.g. Figure 1 110a in), micro base stations or indoor stations (such as Figure 1 110b in the figure), a relay node or a donor node, or a wireless controller in a CRAN scenario.

[0121] 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, a logical module or software that can implement all or part of the functions of the RAN node.

[0122] In another possible scenario, multiple RAN nodes collaborate to assist the terminal device 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 can also be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or a radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU) or a remote radio head (RRH).

[0123] 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 may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

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

[0125] It should be understood that Figure 1 The simplified schematic diagram is provided for ease of understanding, and the communication system may also include a greater 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.

[0126] In order to facilitate understanding of the embodiments of the present application, the terms involved in the embodiments of the present application are briefly explained below.

[0127] 1. Definition of Perception

[0128] Wireless sensing is the use of wireless signals for sensing. Sensing is the process of collecting and processing collected data and generating sensing results. For example, the distance, shape, and type of surrounding obstacles can be determined through collected data. Another example is that the breathing rate and heartbeat of the monitored object can be determined through collected data. The collected data can be data collected by sensors or data collected by wireless signals.

[0129] Wireless sensing and wireless communication are both based on electromagnetic wave theory. The transmitter modulates the electromagnetic wave signal so that the electromagnetic wave signal carries the source information. The electromagnetic wave signal will be affected by the wireless environment during the propagation process, that is, the electromagnetic wave signal is affected by the environment and can therefore also carry environmental information. By analyzing the electromagnetic wave signal, the receiver can not only obtain the source information carried, but also extract the perception information reflecting the characteristics of the propagation environment. In other words, electromagnetic wave signals have the inherent dual capabilities of communication and perception, which makes integrated sensing and communication (ISAC) possible. The integration of communication and perception can also be called joint communications and sensing (JCAS). The integration of communication and perception can also be referred to as synaesthesia integration. Compared with systems that separate perception and communication, ISAC has a series of advantages, such as cost savings, reduced equipment size, reduced power consumption, improved frequency efficiency, and reduced mutual interference between communication and perception.

[0130] 2. Perception of the scene

[0131] The 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. Figure 2 The perception scenes shown in (1) to (6). Figure 2 It is a schematic diagram of a perception scene 200 according to an embodiment of the present application.

[0132] Figure 2 The perception scenario shown in (1) is a perception scenario based on a network device, and the network device acts as a transmitter and receiver of a perception signal. For example, a perception signal 1 sent by a network device reaches a target object (such as a car), and after the perception signal 1 is reflected by the target object, the network device can receive a perception signal 2, and then process the perception signal 2 to obtain a perception result.

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

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

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

[0136] Figure 2 The perception scenario shown in (5) is a perception scenario based on a terminal device, and the terminal device serves as a transmitter and receiver of a perception signal. For example, a perception signal 1 sent by a terminal device reaches a target object, and after being reflected by the target object, the terminal device can receive a perception signal 2, and then process the perception signal 2 to obtain a perception result.

[0137] Figure 2 The perception scenario shown in (6) is also a perception scenario based on terminal devices, where one terminal device acts as a transmitter of a perception signal and the other terminal device acts as a receiver of a perception signal. For example, the perception signal 1 sent by the terminal device a reaches the target object, and the perception signal 1 is reflected by the target object. The terminal device b can receive the perception signal 2, and then the terminal device b can process the perception signal 2 to obtain the perception result.

[0138] 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 information source information and environmental information.

[0139] 3. Sensing entity (SE)

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

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

[0142] 2) Layer 2 (L2) perception capability, used to perceive measurement data. Measurement data refers to data obtained by processing raw data and used to characterize measurement dimensions. It may include but is not limited to one or more of the following information: time delay of sampling points, receiving angle of perceived signals, signal strength of perceived signals, Doppler (i.e., frequency offset of perceived signals), position of target objects, speed of target objects, etc.; sampling points refer to signal values ​​at specific moments or positions selected during the discretization of continuous signals during signal processing;

[0143] 3) Layer 3 (L3) perception capability, used to process perception data to obtain perception results. The perception data may be raw data and / or measurement data. The perception results may include but are not limited to one or more of 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 moving path of the target object, the breathing frequency of the target object, the heartbeat of the target object, and the like.

[0144] A perception entity is a logical entity, which can also be called a logical perception entity. A perception entity can be deployed on a network device or a terminal device, that is, a network device or a terminal device with perception capabilities can serve as a perception entity, and a perception entity can be a network device or a terminal device with perception capabilities. A network device or a terminal device may have the above three capabilities, or may have a certain capability or several capabilities. For example, some terminal devices with weaker computing power have L1 perception capabilities, but do not have L2 perception capabilities and L3 perception capabilities. For another example, some network devices have the above three capabilities. Perception entities can also be deployed independently.

[0145] 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 from each other, the number of control plane function entities and data plane function 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.

[0146] The above-mentioned orchestration of the perception service may include selecting a sending perception entity and a receiving perception entity, and the sending perception entity and the receiving perception entity may be the same perception entity. The sending perception entity is a sending end of the perception signal, which is used to send the perception signal. The receiving perception entity is a receiving end of the perception signal, which is used to receive the perception signal.

[0147] The processing of the sensed data may include processing the original data to obtain the measurement data, and / or processing the measurement data to obtain the sensed result. The measurement data may be obtained by processing the original data, or may be sensed by the sensing entity.

[0148] The names of perception control entity and perception processing entity are used for example and do not constitute a limitation on the embodiments of the present application. With the development of communication technology and perception technology, these two modules may adopt other names. For example, the perception control entity 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 sensing data processing network element, or a sensing processing network element, a sensing 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.

[0149] 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 better be compatible with the 5G system so that it can smoothly evolve to the 6G system. SSCF can be mounted to the SBI bus through the service-based inferface (SBI) interface to communicate with other core network function modules; SDPF can be mounted to the SBI bus through the SBI to communicate with other core network function modules, or it can communicate through a separate interface, such as communicating with other SDPFs through a separate interface, or communicating with SSCF through a separate interface.

[0150] For example, the network architecture after the introduction of SSCF and SDPF can be found in Figure 3 As shown in (1) to (8).

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

[0152] Figure 3 In the networking architecture shown in (2), RAN is directly connected to SSCF, RAN is connected to SDPF through UPF, SDPF is mounted on SBI bus through SBI interface, and SSCF is not mounted on SBI bus. Then, RAN can directly communicate with SSCF on control plane, and RAN can communicate with SDPF on data plane through UPF.

[0153] Figure 3 In the networking architecture shown in (3), RAN is connected to SSCF through AMF, RAN is connected to SDPF through UPF, SDPF is not mounted on the SBI bus, and SSCF is mounted on the SBI bus through SBI. Then, RAN can communicate with SSCF on the control plane through AMF, and RAN can communicate with SDPF on the data plane through UPF.

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

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

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

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

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

[0159] Depend on Figure 3 It can be seen that 1) RAN can communicate with SSCF directly on the control plane, or communicate with SSCF on the control plane through AMF; 2) SDPF can be mounted on the SBI bus, or not mounted on the SBI bus; 3) RAN can communicate with SDPF directly on the data plane, or communicate with SDPF on the data plane through UPF. Among them, control plane communication refers to the transmission of control plane messages, such as the control messages in the embodiments of the present application; data plane communication refers to the transmission of perception data and / or perception results.

[0160] Figure 3The subscript L1 of RAN in the figure indicates that RAN has L1 perception capability, so RAN can send perception signals to target objects (such as bicycles and cars in the figure) and perceive original data through the perception signals reflected by the target objects. Figure 3 Taking the example of RAN having L1 perception capability, in actual applications, RAN may also have L2 perception capability, or may also have L2 perception capability and L3 perception capability; in actual applications, UE may also have perception capability, for example, UE has at least one of L1 perception capability, L2 perception capability, and L3 perception capability.

[0161] Figure 3 The dotted line between the SDPF and the network exposure function (NEF) indicates that the SDPF and the NEF may or may not communicate. If the SDPF is not mounted on the SBI bus, the SDPF may communicate with the NEF through the dotted line. Figure 3 The arrow from one SDPF to itself indicates that the SDPFs can communicate with each other, for example, transmitting sensing data and / or sensing results.

[0162] In the embodiment of the present application, AMF is referred to as an access management entity and NEF is referred to as a network open entity. For the convenience of description, the following embodiments are described by taking AMF and NEF as examples.

[0163] based on Figure 3 In the networking architecture shown, SSCF and SDPF can be upgraded and maintained independently without affecting each other, so that the network can flexibly deploy and manage core network functional entities. Figure 3 Taking one SSCF and one SDPF as an example does not constitute a limitation on the embodiments of the present application. For example, the number of SDPFs can be increased or decreased according to actual needs, and even if the number of SDPFs is reduced, the SSCF will not be affected. This makes it easier to expand or streamline the network.

[0164] By introducing SSCF and SDPF, the control plane and data plane of the perception service can be separated, and attackers cannot attack the control plane entity (such as SSCF) through the data plane entity (such as SDPF), which helps to improve network security. By separating the control plane and data plane of the perception service, the control plane entity can respond to the request of the data plane entity more quickly, thereby reducing network latency and helping to improve network response speed.

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

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

[0167] For ease of understanding and explanation, the following text describes the billing method of 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 of 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, logic 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, logic module or software that can realize all or part of the functions of the data function network element.

[0168] The above network elements may also be concepts such as entities, for example, perception service control entities and data function entities.

[0169] Figure 4 FIG. 4 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. Figure 4 As shown, the method includes:

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

[0171] The charging configuration information can be used to perform charging processing on the sensing service. The sensing service can be a service required by the sensing service user. For example, the sensing service can include one or more of the positioning sensing service, the speed sensing service, and the imaging sensing service. The sensing service can also be Figure 2 The services existing in the six scenarios shown are not limited to this.

[0172] The perception service user may be in various forms. For example, the perception service user may be a terminal, or an application or software in the terminal, which is not limited. In summary, the perception service user may be a user who requires the perception service.

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

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

[0175] 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;

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

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

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

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

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

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

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

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

[0184] Through the above-mentioned billing granularity and / or billing method, the data functional 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.

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

[0186] The billing granularity includes service-based billing, and differentiated billing for different sensing services. For example, sensing service 1 is billed according to rate 1, and sensing service 2 is billed according to rate 2. The type of sensing service 1 is different from the type of sensing service 2, and rate 1 can be different from rate 2.

[0187] The billing granularity includes QoS-based billing, and differential billing for services or flows that implement different QoS. For example, services or flows that implement QoS1 are billed at rate 3, and services or flows that implement QoS2 are billed at rate 4. QoS1 is different from QoS2, and rate 3 is different from rate 4.

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

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

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

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

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

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

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

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

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

[0197] Optionally, the embodiment of the present application may also support reminding the perception service user 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 in time.

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

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

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

[0201] The charging parameters include charging events, which are used to indicate the conditions when the charging information of the perception service is reported;

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

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

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

[0205] When the billing parameters include the first billing quota, the data function network element can determine the initial amount configured for the perception service user when performing the perception service. 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 the signaling interaction overhead. At the same time, the impact on the load of the billing function network element can also be reduced.

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

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

[0208] For example, the billing mode includes flow-based billing, which can count the traffic used by the perception service user when performing the perception service, and bill the perception service based on the traffic;

[0209] For example, the billing mode includes billing based on duration, which can count the duration of the perception service user performing the perception service and bill the perception service based on the duration;

[0210] 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. Exemplarily, the time point when the perception service user performs the perception service is 10:00, and the rate 1 is used to bill the perception service user between 0:00 and 12:00; the time point when the perception service user performs the perception service is 15:00, and the rate 2 is used to bill the perception service user between 12:00 and 17:00; the time point when the perception service user performs the perception service is 22:00, and the rate 3 is used to bill the perception service user between 17:00 and 24:00.

[0211] ■Optionally, when the perception service user starts the perception service from 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.

[0212] For example, the charging mode includes charging based on the number of service occurrences. The number of times the perception service user performs the perception service can be counted, and the perception service can be charged based on the number of times.

[0213] For example, the billing mode includes billing based on the area where the service occurs, and the area where the perception service user performs the perception service can be determined, and the perception service can be billed based on the area. For example, if the perception service user performs the perception service in area 1, the perception service can be billed at rate 1; if the perception service user performs the perception service in area 2, the perception service can be billed at rate 2.

[0214] For example, the billing mode includes billing based on the type of service, and different types of perception services can be billed. For example, if a perception service user performs perception service 1, rate 1 is used to bill perception service 1; if a perception service user performs perception service 2, rate 2 is used to bill perception service 2. The type of perception service 1 is different from the type of perception service 2.

[0215] For example, if the billing mode includes billing based on the perception accuracy of the service, different perception accuracies can be billed. Exemplarily, when the perception accuracy of the perception service user is perception accuracy 1 when performing perception service 1, the perception service 1 can be billed using rate 1; when the perception accuracy of the perception service user is perception accuracy 2 when performing perception service 1, the perception service 1 can be billed using rate 2. The perception accuracy can include one or more of the following: positioning accuracy, velocity estimation accuracy, imaging accuracy, missed detection rule, false alarm probability, perception resolution, latency, etc.

[0216] Through one or more of the above 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 the perception service for the perception service user.

[0217] In a possible implementation, the billing event includes one or more of the following: traffic volume reaching a threshold, duration reaching a threshold, a time point at which the service occurs changing, or the number of times the service occurs reaching a threshold.

[0218] For example, the billing event includes traffic reaching a threshold, and the traffic 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 traffic threshold is 80M, and when the traffic used by the perception service user when performing the perception service reaches 80M, the traffic information of the perception service user when performing the perception service can be reported to other network elements, and other network elements will charge the perception service accordingly.

[0219] For example, the billing event includes that the duration reaches 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). Exemplarily, the duration threshold is 80 hours. When the duration of the perception service user performing the perception service has reached 80 hours, the duration information of the perception service user performing the perception service can be reported to other network elements, and other network elements will charge the perception service accordingly.

[0220] For example, a billing event includes a change in the time point at which a service occurs, and the time information when the perception service user performs 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 has passed 12:00, then the time information when the perception service user performs 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 to perceive the 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.

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

[0222] For example, the billing event includes that the number of service occurrences reaches a threshold, and the number of occurrences when the perception service user performs the perception service can be reported (which can be one of the billing information of the perception service). Exemplarily, the threshold of the number of service occurrences is 50 times. When the number of service occurrences when the perception service user performs the perception service has reached 50 times, the number of service occurrences when the perception service user performs the perception service can be reported to other network elements, and other network elements will charge the perception service accordingly.

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

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

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

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

[0227] For example, the first billing quota is a quota for the number of service occurrences. 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.

[0228] 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 the signaling interaction overhead. At the same time, the impact on the load of the billing function network element can also be reduced. In addition, it is also convenient for the billing function network element to reconcile the perception service.

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

[0230] Table 1

[0231] Fields meaning URR ID Identifies the reported URR start time Start time end time End Time volume usage flow duration Duration events usage Number of business occurrences location Business area

[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 when the sensing service user performs the 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 sensing service user when performing the sensing service;

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

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

[0239] The location field indicates the area where the sensing service user 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 one billing group. For example, if the rate of service 1 is the same as that of service 2, and both are billed in the form of traffic, service 1 and service 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 it reaches the threshold.

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

[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 number threshold.

[0244] For example, when the threshold of the charging event includes a flow threshold, the flow threshold may be a fixed ratio of the first charging quota. For example, the first charging quota is 100M, the fixed ratio of the charging quota is 80%, and 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, the first billing quota is 100 hours, the fixed ratio of the billing quota is 80%, and 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. For example, the first charging quota is 100 times, the fixed ratio of the charging quota is 80%, and the threshold of the number of service occurrences may be 80 times.

[0247] Through one or more of the above thresholds of 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.

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

[0249] Table 2

[0250] Fields meaning URR ID URR logo charging mode Billing Model charging trigger Billing Events volume threshold Traffic threshold time threshold Duration Threshold event threshold Business occurrence threshold

[0251] As shown in Table 2, the charging 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 time threshold;

[0257] The event threshold field indicates the threshold of 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 the perception service.

[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 the first billing quota, the data function network element can determine the initial amount configured for the perception service user when performing the perception service. In addition, 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 the signaling interaction overhead. At the same time, the load of the billing function network element can also be reduced.

[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 perception 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, counts the duration, flow rate or number of occurrences of the perception service, and obtains the 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, it is determined that the flow rate of the perception service has reached the flow threshold, the data function network element can 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 of 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 acquired perception service 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] Combined with the following Figures 5 to 8 right Figure 4For 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] Figure 5 FIG. 5 is a schematic diagram of an interactive process of a billing method 500 for a perception service according to an embodiment of the present application. Figure 5 As shown, the method includes:

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

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

[0274] When the SSCF determines that the perception service needs to be charged, 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 "charging policy corresponding to a specific service". For example, for location-aware services, SSCF may obtain charging parameters for location-aware services from CHF through the first information (for example, the first information includes indication information for indicating location-aware services); for speed-aware services, SSCF may obtain charging parameters for speed-aware services from CHF through the first information (for example, the first information includes indication information for indicating speed-aware services). In this way, charging parameters may be obtained in a targeted manner to support charging processing for users of perception services using perception services.

[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 the type information of the awareness service used by the awareness service user to the CHF.

[0277] The first information may also be replaced by other terms, for example, may be replaced by charging parameter request information or request information, etc., which is not limited. 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] Exemplarily, a correspondence between charging parameters and charging policies can be established, and the correspondence can be configured in SSCF. After SSCF obtains charging parameters from CHF, it can determine a corresponding charging policy according to the correspondence and the obtained charging parameters.

[0284] Optionally, multiple charging policies may be preconfigured, 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 perception service according to the billing configuration information.

[0287] For the description of S504, please refer to the description of S403, which 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] Figure 5 The following description takes the case where SSCF obtains charging parameters from CHF and the charging policy is predefined or preconfigured as an example. However, the charging parameters may also be predefined or preconfigured. Figure 6 .

[0290] Figure 6 FIG. 6 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. Figure 6 As shown, the method includes:

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

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

[0293] When SSCF determines that it is necessary to perform billing processing on the perception service, it can send a second message for requesting a billing policy to PCF. PCF can determine the billing policy that needs to be sent to SSCF based on the second message. Alternatively, before SSCF performs billing processing on the perception service, it sends a second message for requesting a billing policy to PCF. PCF can determine the billing policy that needs to be sent to SSCF based on the second message.

[0294] Optionally, the second information may also carry indication information of "charging policy corresponding to a specific service". For example, for location-aware services, SSCF may obtain the charging policy for location-aware services from PCF through the second information (for example, the second information includes indication information for indicating location-aware services); for speed-aware services, SSCF may obtain the charging policy for speed-aware services from PCF through the second information (for example, the second information includes indication information for indicating speed-aware services). In this way, the charging policy may be obtained in a targeted manner so as to support the charging processing of users of the perception services using the perception 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 the type information of the awareness service used by the awareness service user to the PCF.

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

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

[0298] Correspondingly, SSCF receives the charging policy from 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] Exemplarily, a correspondence between charging parameters and charging policies can be established, and the correspondence can be configured in SSCF. After SSCF obtains the charging policy from PCF, it can determine the corresponding charging parameters according to the correspondence and the obtained charging policy.

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

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

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

[0306] For the description of S604, please refer to the description of S403, which 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] Figure 5 and Figure 6 The description is based on the example that SSCF obtains the charging parameters and charging policies from CHF or PCF respectively. The embodiment of the present application also supports the scenario that the charging policies and charging parameters are predefined or preconfigured. SSCF can select a charging policy and a charging parameter from one or more preconfigured charging parameters and charging policies, and send the determined charging policy and charging parameters to SDPF. In this way, the signaling interaction overhead of SSCF obtaining charging parameters and / or charging policies can be reduced.

[0309] Figures 4 to 6 The following example describes the process of SSCF sending charging configuration information to SDPF and SDPF performing charging processing on the perception service according to the charging configuration information. After SDPF completes the charging processing on the perception service, it can also interact with SSCF. Figure 7 .

[0310] Figure 7 FIG. 7 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. Figure 7 As shown, the method includes:

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

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

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

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

[0315] Correspondingly, the CHF receives the third information. 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 is determined 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 is determined 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 perception service user is not exhausted, the SSCF may send third information for requesting the second charging quota of the perception service to the CHF, so that the SDPF can determine whether to report the charging information of the perception service according to the new charging quota.

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

[0320] S703. CHF sends a second charging quota for the perception service to SSCF.

[0321] Correspondingly, the SSCF receives the second charging quota for the perceived 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 perceived 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 scheme, the embodiment of the present application can support SDPF to determine the second billing quota of the perception service. In addition, through the second billing quota of the interactive perception service, the billing function network element can check the account balance of the perception service user according to the third information, which can avoid the billing quota being used up and the perception service user continuing 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 The following describes the exchange of charging configuration information and service-aware charging information between SSCF and SDPF as an example. SSCF can also exchange information with other network elements to start or execute the process of sending charging configuration information to SDPF. Figure 8 .

[0329] Figure 8 FIG. 8 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. Figure 8 As shown, the method includes:

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

[0331] Correspondingly, the SSCF receives the fourth information. The fourth information is used to request the perception 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, by 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, reference may be made to the description of S401, which 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 perception service according to the billing configuration information.

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

[0340] pass Figure 8 According to the technical solution, SSCF can determine the charging configuration information based on the information sent by the perception service user for requesting the perception service, and complete the process of exchanging the charging configuration information with SDPF, thereby supporting the charging processing of the perception service.

[0341] Figures 4 to 8 The above content is described by taking multiple network elements performing information interaction to complete the billing process of the perception service as an example. Fig. 9 Describe how to complete the registration of awareness service users.

[0342] Fig. 9 FIG. 9 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. Fig. 9 As shown, the method includes:

[0343] S901. A perception service user sends registration information to a 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 network element is responsible for managing awareness service users. It can be responsible for one or more of the following:

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

[0347] ·Contracting and subscribing to the sensing service;

[0348] · Authentication and authorization of perceived business users;

[0349] ·Account balance management of perception service users. In addition, the registration information is used to request the completion of the registration of the perception service user. For a description of the registration information, please refer to Table 3. The content shown in Table 3 is only an example and is not a final limitation.

[0350] Table 3

[0351] Fields meaning Username Name of the aware business user User ID Perceive the unique identity of the business user User Type Internal users, external users Authentication data Such as user password, etc. Allows the requested business type List of perceived service types supported by the user Prohibited business areas Instructs users to prohibit sensing services in this area User Priority Identifies the user priority, the value is 1-15 Billing attributes Including postpaid, prepaid, free users Business subscription information Subscribed sensing service related information

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

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

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

[0355] A user type field is used to indicate whether the perceived service user is an internal user or an external user;

[0356] An 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;

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

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

[0359] User priority field, which is used to identify the priority of the perception service user, and the value can be 1-15. The smaller the value, the higher the priority;

[0360] The charging attribute field is used to indicate the charging attributes of the perceived service user, including post-paid, pre-paid, and free users;

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

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

[0363] In a possible implementation, the registration information includes the name of the perception service user, the identification of the perception service user, the user type of the perception service user, the authentication data of the perception service user, and the billing attributes. Through one or more of the above, the perception service user management network element can obtain relevant information about the perception service user, and can complete the registration management of the perception service user based on the relevant information.

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

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

[0366] 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 is successfully registered, or the first response information indicates that the awareness service user fails to register.

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

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

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

[0370] S904. The perception service user management network element sends a second response message to the perception service user.

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

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

[0373] pass Fig. 9 The method described in the embodiment of the present application can support the perception service user to request to perform or use the perception service.

[0374] 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 the billing information initialization information of the awareness service user with the CHF or the account balance management function (ABMF) network element.

[0375] When the user of the perception service completes the registration process and completes the request for the perception service, the SSCF, SDPF, CHF and PCF can exchange information to complete the billing process for the perception service. For details, see Figure 4-Figure 8 The description is not repeated here.

[0376] It should be noted that the above Figure 5-Figure 9 is a separate embodiment, Figure 5-Figure 9 The contents shown can be combined with each other to form new embodiments. For example, Figure 5 The method and Figure 6 The methods described can be combined; Figure 5 The method and Figure 7 The methods shown can be combined, etc. In summary, the embodiments of the present application do not limit Figures 5 to 9 The specific combination method between the contents shown.

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

[0378] In order to implement the functions in the method provided in this application, the above network element may include a hardware structure and / or a software module, and the above functions may be implemented in the form of a hardware structure, a software module, or a hardware structure plus a software module. Whether one of the above functions is executed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraints of the technical solution.

[0379] Fig.10 1 is a schematic block diagram of a communication device 1000 of an embodiment of the present application. The communication device 1000 includes a processor 1010 and a communication interface 1020, and the processor 1010 and the communication interface 1020 can be connected to each other via a bus 1030. The communication device 1000 can 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, and the like.

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

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

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

[0383] When the communication device 1000 is a data function network element, illustratively, the processor 1010 is used to perform the following operations: receiving billing configuration information; performing billing processing on the perception service according to the billing configuration information, etc.

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

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

[0386] The above description is only an exemplary description, and the specific content can refer to the content shown in the above method embodiment.

[0387] It should be noted that Fig.10 The implementation of each operation in can also refer to Figures 4 to 9 The corresponding description of the method embodiment shown.

[0388] Fig.11 1 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, and the like.

[0389] The communication device 1100 includes an interface unit 1110 and a processing unit 1120. The interface unit 1110 may include a sending unit and a receiving unit. The sending unit is used to perform a sending action of the communication device, and the receiving unit is used to perform a receiving action of the communication device. For ease of description, the embodiment of the present application combines the sending unit and the receiving unit into a transceiver unit. A unified description is given here, and no further description is given later.

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

[0391] When the communication device 1100 is a second device, illustratively, the interface unit 1110 is used to receive charging configuration information. The processing unit 1120 is used to perform charging processing on the perception service according to the charging configuration information.

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

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

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

[0395] The above description is only an exemplary description, and the specific content can refer to the content shown in the above method embodiment.

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

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

[0398] The present application also provides another chip, including: 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 used to execute the code in the memory, and when the code is executed, the processor is used to execute the method in each of the above examples. Optionally, the chip also includes a memory, and the memory is used to store computer programs or codes.

[0399] The present application also provides a processor, which is coupled to a memory and is used to execute the methods and functions involving a network device or a terminal device in any of the above-mentioned embodiments.

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

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

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

[0403] Those of ordinary skill 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 to be beyond the scope of this application.

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

[0405] In several embodiments provided in the present application, the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units is only a logical function division. There may be other division methods in actual implementation. For example, 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.

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

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

[0408] 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 can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods of each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks, or optical disks.

[0409] The above are only specific implementations of the embodiments of the present application, but the protection scope of the embodiments of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or replacements within the technical scope disclosed in the embodiments of the present application, which should be included in the protection scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application shall be based on the protection scope of the claims.

Claims

1. A service-aware billing method, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is characterized in that The charging method includes one or both of online charging and offline charging.

9. The method according to claim 7, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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 based on business awareness. It is 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, It is 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, It is 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, It is characterized in that The charging method includes one or both of online charging and offline charging.

21. The method according to claim 18, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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 perceiving services, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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