Passive Internet of Things (IoT) billing methods, billing systems, network devices, and storage media

Abstract

This disclosure provides a passive IoT billing method, billing system, network device, and storage medium, relating to the field of wireless communication technology. The passive IoT billing method includes: a NEF module receiving a passive IoT service request matching a service mode sent by an Application Function (AF) module, the service request including the AF module's subscription list of Ambient UEs; the NEF module initiating a service request to a Passive IoT Function (AIF) module, whereby the AIF module reports the service mode to a PCF module, causing the PCF module to send a billing policy corresponding to the service mode to a CHF module; the AIF module reporting terminal data of Ambient UEs collected based on the subscription list to the CHF module, which then bills the terminal data based on the billing policy; and the NEF module receiving the billing result reported by the CHF module and reporting the billing result to the corresponding AF module. This technical solution enables billing of passive IoT terminals when the AF module provides passive IoT services.

Description

Technical Field

[0001] This disclosure relates to the field of wireless communication technology, and in particular to a passive Internet of Things (IoT) billing method, a passive IoT billing system, a network device, and a computer-readable storage medium. Background Technology

[0002] Passive Internet of Things (IoT) refers to the Internet of Things based on wireless electromagnetic energy capture technology. Terminals used in passive IoT do not have SIM (Subscriber Identity Module) cards and do not actively access the network. Therefore, they are characterized by simple structure, single function, low cost, wide variety, and large quantity. They also differ from existing 3GPP (3rd Generation Partnership Project) terminals and services. Therefore, there is an urgent need for a billing scheme for services applied to passive IoT to enable billing when providing network access to passive IoT terminals and when application functions (AF) provide passive IoT-related data and information services.

[0003] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0004] The purpose of this disclosure is to provide a passive Internet of Things (IoT) billing method, billing system, network device, and storage medium, which at least to some extent overcomes the problem in related technologies of billing when network access is not provided for passive IoT terminals and passive IoT-related data and information services are not provided for the terminal's application function AF module.

[0005] Other features and advantages of this disclosure will become apparent from the following detailed description, or may be learned in part from practice of this disclosure.

[0006] According to one aspect of this disclosure, a passive Internet of Things (IoT) billing method is provided, comprising: a Network Open Function (NEF) module receiving a passive IoT service request matching a service mode sent by an Application Function (AF) module, the service request including a subscription list of passive Internet Terminals (Ambient UEs) by the AF module; the NEF module initiating the service request to a Passive Internet Function (AIF) module, so that the AIF module reports the service mode to a Policy Control Function (PCF) module, causing the PCF module to send a billing policy corresponding to the service mode to a Billing Function (CHF) module; the AIF module reporting terminal data of the Ambient UEs collected based on the subscription list to the CHF module; and the CHF module billing the terminal data based on the billing policy; the NEF module receiving the billing result reported by the CHF module; and the NEF module reporting the billing result to the corresponding AF module.

[0007] In one embodiment, after the NEF module initiates the service request to the Passive Internet of Things Function (AIF) module, the method further includes: the NEF module receiving the status information of the Ambient UE belonging to the subscription list and the terminal data reported by the AIF module based on the service request.

[0008] In one embodiment, before the AIF module reports the service mode to the Policy Control Function (PCF) module, the method further includes: the NEF module performing a registration operation for the billing policy subscription to the PCF module, so that the PCF module updates the billing policy configuration of the CHF module.

[0009] In one embodiment, the NEF module reports the billing result to the corresponding AF module, and further includes: the NEF module also pushes the status information of the Ambient UE and the terminal data to the AF module.

[0010] In one embodiment, the service mode includes a single request mode, wherein the Network Open Function (NEF) module receives a passive IoT service request matching the service mode sent by the Application Function (AF) module, including: the NEF module receiving a remote single data request from the Ambient UE sent by the AF module based on the single request mode as the service request.

[0011] In one embodiment, the service mode includes a single-request mode, and the billing strategy corresponding to the service mode includes a single-request billing strategy.

[0012] In one embodiment, the service mode includes a subscription push mode. The Network Open Function (NEF) module receives a passive IoT service request matching the service mode from the Application Function (AF) module. This includes: the NEF module receiving a push registration request for the passive IoT service subscription sent by the AF module based on the subscription push mode; the NEF module initiating the service request to the Passive IoT Function (AIF) module; and the NEF module initiating a registration operation between the AF module and the subscription request on the AIF module based on the push registration request.

[0013] In one embodiment, the service mode includes a subscription push mode, and the billing strategy corresponding to the service mode includes a subscription push billing strategy.

[0014] In one embodiment, in the non-first-time periodic subscription of the subscription push mode, the NEF module receives the status information of the Ambient UE and the terminal data reported by the AIF module based on the service request, and further includes: the NEF module receiving abnormal information pushed by the AIF module based on the abnormal status of the Ambient UE.

[0015] In one embodiment, the service mode includes a hybrid mode, wherein the Network Open Function (NEF) module receives a passive IoT service request matching the service mode sent by the Application Function (AF) module, including: the NEF module receiving a remote single data request from the Ambient UE and a push registration request for the passive IoT service subscription sent by the AF module based on the hybrid mode, as the service request.

[0016] In one embodiment, the service mode includes a hybrid mode, and the billing policy corresponding to the service mode is configured by the CHF module according to the hybrid billing scheme issued by the PCF module.

[0017] According to another aspect of this disclosure, a passive Internet of Things (IoT) billing method is provided, comprising: a passive IoT function (AIF) module receiving a passive IoT service request initiated by a network open function (NEF) module, wherein the service request is sent to the NEF module by an application function (AF) module based on a service mode; the AIF module collecting terminal data of the Ambient UE based on the subscription list of the Ambient UE carried by the AF module in the service request; the AIF module reporting the terminal data to a billing function (CHF) module, whereby the CHF module bills the terminal data based on a billing policy, reports the billing result to the NEF module, and the NEF module reports the billing result to the corresponding AF module.

[0018] In one embodiment, the AIF module collects terminal data of the Ambient UE based on the subscription list of the Passive Internet Terminal (Ambient UE) carried by the AF module in the service request. This includes: if the AIF module stores complete terminal data, it directly collects the terminal data; if the AIF module does not store complete terminal data, it requests the terminal data of the Ambient UE belonging to the subscription list from the Radio Access Network (RAN) module of the Passive Internet of Things (AIoT), so that the RAN module broadcasts a data reporting request to the Ambient UEs within its coverage area, and reports feedback information to the Mobility Management Function (AMF) module based on the identification and stored data reported by the Ambient UE; the AIF module receives the status information and mobility information of the Ambient UE reported by the AMF module based on the feedback information, and reports the number and status information of the Ambient UEs, the terminal data, and the number of abnormal terminals to the CHF module based on the status information and mobility information, and performs billing operations.

[0019] In one embodiment, before the AIF module reports the terminal data to the billing function CHF module, the method further includes: the AIF module reporting the service mode to the policy control function PCF module, so that the PCF module sends the configuration file of the billing policy corresponding to the service mode to the CHF module.

[0020] In one embodiment, the AIF module reporting the service mode to the Policy Control Function (PCF) module includes: the AIF module reporting any one of the single request mode, subscription push mode, and hybrid mode to the PCF module.

[0021] In one embodiment, before the AIF module receives the status information and mobility information of the Ambient UE reported by the AMF module based on the feedback information in the single request mode, or in the first subscription of the subscription push mode, or in the first request of the hybrid mode, the AIF module further includes: the AIF module receiving the correspondence information and terminal data reported by the RAN module based on the identifier and the stored data, wherein the correspondence information is the correspondence between the RAN module and the Ambient UE.

[0022] In one embodiment, the AIF module reports the terminal data to the billing function CHF module, and further includes: in the single request mode, the AIF module reports the status information of the Ambient UE and the terminal data obtained based on the remote single data request to the NEF.

[0023] In one embodiment, the AIF module reports the terminal data to the billing function CHF module, and further includes: in the first subscription of the subscription push mode, the AIF module reports the status information of the Ambient UE and the terminal data of the first subscription obtained based on the push registration request to the NEF.

[0024] In one embodiment, in the non-first-time periodic subscription of the subscription push mode, the AIF module collects terminal data of the passive Internet terminal Ambient UE based on the service request, including: the AIF module periodically collects the latest terminal data that needs to be billed.

[0025] In one embodiment, in the non-first-time periodic subscription of the subscription push mode, after the AIF module receives the status information and mobility information of the Ambient UE reported by the AMF module based on the feedback information, the AIF module further includes: pushing the status information of the Ambient UE and the terminal data obtained based on the service subscription push registration request to the NEF; and when a terminal with an abnormal status is detected, the AIF module pushes the abnormal information of the abnormal Ambient UE to the NEF.

[0026] According to another aspect of this disclosure, a passive Internet of Things (IoT) billing method is provided, comprising: a radio access network (RAN) module of a passive IoT receiving a service request from a passive Internet Function (AIF) module for terminal data of a passive Internet terminal (Ambient UE); the RAN module receiving reported data from the Ambient UE in response to the service request; the RAN module reporting feedback information to a mobility management (AMF) module based on the reported data, so that the AMF module reports the status information and mobility information of the Ambient UE to the AIF module based on the feedback information, enabling the AIF module to obtain the terminal data based on the status information and mobility information; the AIF module reporting the terminal data to a charging function (CHF) module, whereby the CHF module bills the terminal data based on a charging policy and reports the billing result to the NEF module, so that the NEF module reports the billing result to the corresponding AF module.

[0027] In one embodiment, the RAN module receives the reported data from the Ambient UE in response to the service request, including: the RAN module broadcasting a data reporting request to the Ambient UE within its coverage area; and the RAN module receiving the identification and storage data reported by the Ambient UE as the reported data.

[0028] In one embodiment, the RAN module reports feedback information to the Mobility Management AMF module based on the reported data, including: the RAN module reporting correspondence information and the location information of the Ambient UE to the AMF module based on the identifier and the stored data, wherein the correspondence information is the correspondence between the RAN module and the Ambient UE; in single-request mode, or in the first subscription in subscription-push mode, or in the first request in hybrid mode, the RAN module reporting the correspondence information and the terminal data to the AIF module based on the identifier and the stored data; in non-first-time periodic subscriptions in subscription-push mode, the RAN module reporting the correspondence information and the terminal data to the AMF module based on the identifier and the stored data.

[0029] According to another aspect of this disclosure, a passive Internet of Things (IoT) billing system is provided, comprising at least one of the following modules as described in the above embodiments: a Network Open Function (NEF) module, an Application Function (AF) module, a Passive Internet Terminal (Ambient UE), a Passive Internet Function (AIF) module, a Policy Control Function (PCF) module, a Billing Function (CHF) module, a Radio Access Network (RAN) module, and a Mobility Management Function (AMF) module.

[0030] According to another aspect of this disclosure, a network device is provided, comprising: a processor; and a memory for storing executable instructions of the processor; the processor being configured to perform the passive IoT billing method of the first aspect described above by executing the executable instructions.

[0031] According to another aspect of this disclosure, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the passive Internet of Things (IoT) billing method described above.

[0032] The passive IoT billing scheme provided in this disclosure aims to better meet the needs of passive IoT terminal services. By configuring a Passive IoT Function (AIF) module for the Ambient UE, the AIF module collects terminal data from the Ambient UE. Combined with corresponding billing policies configured for different service modes, the Billing Function (CHF) module performs billing based on the billing policies and the collected terminal data. This enables billing of passive IoT terminals when providing network access and when the AF module provides passive IoT-related data and information services. This provides more efficient network services when deploying passive IoT terminals and services in the network, ensuring the reliable and efficient operation of the passive IoT system.

[0033] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0034] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0035] Figure 1 This diagram illustrates a passive Internet of Things (IoT) billing system according to an embodiment of the present disclosure.

[0036] Figure 2 This diagram illustrates a flowchart of a passive Internet of Things (IoT) billing method according to an embodiment of this disclosure.

[0037] Figure 3 This diagram illustrates a flowchart of another passive IoT billing method in an embodiment of this disclosure;

[0038] Figure 4 This diagram illustrates a flowchart of yet another passive IoT billing method according to an embodiment of the present disclosure;

[0039] Figure 5 This illustration shows a flowchart of yet another passive IoT billing method according to an embodiment of the present disclosure;

[0040] Figure 6 This illustration shows a flowchart of yet another passive IoT billing method according to an embodiment of the present disclosure;

[0041] Figure 7 This illustration shows a flowchart of yet another passive IoT billing method according to an embodiment of the present disclosure;

[0042] Figure 8 This diagram illustrates a passive Internet of Things (IoT) billing device according to an embodiment of the present disclosure.

[0043] Figure 9 This diagram illustrates another passive IoT billing device in an embodiment of the present disclosure;

[0044] Figure 10 This diagram illustrates yet another passive IoT billing device according to an embodiment of the present disclosure;

[0045] Figure 11 A structural block diagram of a computer device according to an embodiment of the present disclosure is shown. Detailed Implementation

[0046] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, they are provided so that this disclosure will be more comprehensive and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0047] Furthermore, the accompanying drawings are merely illustrative of this disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted. Some block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0048] As a new type of terminal and service, passive IoT terminals require networks to not only provide network access but also offer related services to these terminals, services, and their corresponding application functions (AFs). Furthermore, the large number and diverse types of passive IoT terminals lead to a multitude of corresponding service types and a large number of AFs providing different services based on these terminals. To better manage these numerous passive IoT terminals and provide corresponding services to the AFs, single-request and subscription-push models for passive IoT services have emerged. Consequently, network-side billing functions lack corresponding billing schemes for these new types of terminals and services. While existing Session Management (SMF), Short Message Service (SMSF), and Access and Mobility Management (AMF) modules have billing designs and definitions related to the Credit Function (CHF), the dependence and potential impact of passive IoT terminal-related services on these modules are relatively small due to the characteristics of passive IoT terminals, especially their passive response nature. The Network Functions Open Module (NEF) is the core network module most closely connected to the existing services related to passive IoT terminals. However, according to 3GPP TS 23.501 and 3GPP TS 32.254, the services and specifications related to CHF of NEF do not cover passive IoT services, and the existing specifications do not take into account the relevant characteristics of passive IoT terminals and services.

[0049] Considering the future deployment of passive IoT terminals and services into existing networks, and building upon the existing passive IoT service models and processes, a feasible billing scheme and specifications need to be designed and defined for passive IoT services. Based on two service request modes designed for passive IoT terminals and services—the single-request mode and the subscription-push mode—a billing scheme based on the passive IoT core network element AIF is designed, defining the relevant request and billing content. Billing processes for both service request modes are also designed and defined. A corresponding billing service scheme and process are designed for the future deployment of passive IoT terminals and related services in the network.

[0050] Figure 1 A schematic diagram of a passive Internet of Things (IoT) system according to an embodiment of this disclosure is shown. Figure 1 As shown, the system mainly includes at least one of the following: Ambient Internet Terminal (UE) 102, Application Function (AF) module 104, Passive Internet of Things (AIF) module 106, Network Open Function (NEF) module 108, Policy Control Function (PCF) module 110, Charging Function (CHF) module 112, Radio Access Network (RAN) module 114, and Mobility Management Function (AMF) module 116.

[0051] Ambient UE102 (Ambient IoT / Ambient UE) is a new type of IoT terminal device that does not have a SIM card, has a simple structure, low manufacturing cost, single function, extremely low power consumption, and generally does not have energy storage or has very low energy storage, and only passively responds to requests.

[0052] Application Function (AF) module 104 primarily refers to the application function module that provides related services to passive IoT terminals and third parties, with passive IoT terminals and their data as the core. In this system, it mainly requests and obtains terminal information (such as status information, location information, etc.) and terminal data (related data stored in the terminal) from passive IoT terminals.

[0053] The Passive IoT Function (AIF) module 106 is primarily responsible for collecting, storing, and processing passive IoT terminal data. It stores the mapping information between passive IoT terminal IDs and base station IDs for quick retrieval when querying terminals. It performs operations such as classifying, simplifying, security checks, and timeliness checks on the collected Ambient IoT terminal data. In subscription service mode, this module also stores terminal subscription list information: which Ambient IoT terminals each AF has subscribed to, along with their status and data information. It also has push functionality: based on the actual stored subscription information, this module periodically pushes information to the corresponding AF after data collection.

[0054] The Network Exposure Function (NEF) module 108 is primarily responsible for performing security desensitization and classification / packaging of the information and data provided by the Network Passive Internet of Things (AIF) module to the Application Function (AF) module when the network-side AIF module provides relevant data and terminal information. It also connects the Network Passive Internet of Things (AIF) module, the Policy Control Module (PCF), and the Billing Function Module (CHF) on the network side.

[0055] The Policy Control Function (PCF) module 110 is used to select the corresponding service policy and billing policy based on the service type requested by the application service from the passive IoT function module AIF on the network side.

[0056] The Charging Function (CHF) module 112 is the charging function center, which provides corresponding charging functions for the passive IoT function module AIF on the network side when it provides relevant data services to the application function AF.

[0057] The Radio Access Network (RAN) module 114 is used to interact with the Ambient UE and obtain terminal data.

[0058] The Access and Mobility Management Function (AMF) module 116 is used for the mobility management of passive IoT terminals. Based on the correspondence between passive IoT terminals and base stations, and the fact that base stations can roughly locate terminals with low precision during the process of providing access services to passive IoT terminals, the mobility management of a large number of passive IoT terminals can be achieved.

[0059] The following will describe in more detail each step of the passive IoT billing method in this exemplary embodiment, with reference to the accompanying drawings and embodiments.

[0060] Figure 2 A flowchart of a passive Internet of Things (IoT) billing method according to an embodiment of this disclosure is shown.

[0061] like Figure 2 As shown, a passive IoT billing method according to an embodiment of this disclosure, applied to a Network Open Function (NEF) module, includes:

[0062] In step S202, the Network Open Function (NEF) module receives a passive IoT service request matching the service mode sent by the Application Function (AF) module. The service request includes the AF module's subscription list for passive Internet UE terminals.

[0063] The service modes include, but are not limited to, single request mode, recurring subscription push mode, and a hybrid mode of the above.

[0064] The terminals in the subscription list are the Ambient UEs that provide services to them via the Passive Internet of Things (AF). The subscription list may include the ID of the AF module, the ID of the Ambient UE, and the specific requirements of each AF module for the subscription service (including the number of terminal devices, data type, and data timeliness requirements).

[0065] In step S204, the NEF module initiates a service request to the Passive Internet of Things Function (AIF) module, so that the AIF module reports the service mode to the Policy Control Function (PCF) module, which in turn sends the billing policy corresponding to the service mode to the Billing Function (CHF) module. The AIF module then reports the terminal data of the Ambient UE collected based on the subscription list to the CHF module, which then bills the terminal data based on the billing policy.

[0066] The AF module sends service requests to the NEF module, which then forwards them to the AIF module. The AIF module reports the service mode to the PCF module, which in turn sends the billing policy to the CHF module. The AIF module also reports the collected terminal data to the CHF module, which then bills the terminal data based on the billing policy.

[0067] Terminal data includes specific data volume and data type, enabling the CHF module to bill based on data volume and data type according to the billing policy.

[0068] Step S206: The NEF module receives the billing results reported by the CHF module.

[0069] In step S208, the NEF module reports the billing results to the corresponding AF module.

[0070] In this embodiment, to better meet the relevant needs of passive IoT terminal services, a passive IoT function (AIF) module is configured for the AmbientUE. The AIF module collects terminal data from the Ambient UE and combines this with corresponding billing policies configured for different service modes. The billing function (CHF) module then performs billing based on the billing policies and the collected terminal data. This enables billing of passive IoT terminals when providing network access and when the AF module provides passive IoT-related data and information services. This provides more efficient network services when deploying passive IoT terminals and services in the network, ensuring the reliable and efficient operation of the passive IoT system.

[0071] In one embodiment, after the NEF module initiates a service request to the Passive Internet of Things (AIF) module, the method further includes: the NEF module receiving the status information and terminal data of the Ambient UE belonging to the subscription list reported by the AIF module based on the service request.

[0072] Among them, the status information is used to characterize whether the Ambient UE is in a service state, a normal state, or whether it is lost or destroyed, so as to determine the validity of the collected terminal data based on the status information.

[0073] For example, the Ambient UE stores the service data provided by the Internet of Things, namely terminal data. After the Ambient UE reports the terminal data to the AIF, the AIF reports the information to the CHF for billing based on the relevant dimensions such as the data volume, data dimension and number of terminals. For example, if it receives 100MB of data from 1000 terminals, then the billing information is: 100 terminals, 100MB of data.

[0074] In one embodiment, before the AIF module reports the service mode to the Policy Control Function (PCF) module, the method further includes: the NEF module performing a registration operation for the billing policy subscription to the PCF module, so that the PCF module can update the billing policy configuration of the CHF module.

[0075] In this embodiment, before performing the billing operation, the NEF module needs to register with the PCF module in advance to subscribe to the corresponding billing policy. Based on the subscription operation, when billing is required, the PCF module updates the billing policy configuration of the CHF module to ensure the matching of the CHF module's billing of the terminal with the service mode.

[0076] In one embodiment, the NEF module reports the billing results to the corresponding AF module, and further includes:

[0077] The NEF module also pushes the status information and terminal data of the Ambient UE to the AF module.

[0078] In one embodiment, in the single-request service mode, i.e., the service mode includes the single-request mode, the Network Open Function (NEF) module receives a passive IoT service request sent by the Application Function (AF) module that matches the service mode, including: the NEF module receiving a remote single data request from the Ambient UE sent by the AF module based on the single-request mode as a service request.

[0079] In one embodiment, the service mode includes a single request mode, and the billing strategy corresponding to the service mode includes a single request billing strategy.

[0080] For example, the single request mode is mainly used when the application function AF module has business needs and initiates a data acquisition request to the network element AIF module responsible for the passive IoT terminal management business function through the network open function NEF module. The AIF module collects and organizes the requested terminal data based on the actual stored terminal information and data, reports it to the AF module, and performs related billing based on the number of terminals collected, terminal information, and terminal data volume.

[0081] The billing process for single-request mode includes:

[0082] The AF module initiates a single information data retrieval request to the network through the NEF module.

[0083] After receiving the request, the NEF module sends a data acquisition request to the AIF module, and at the same time sends the billing-related configuration to the CHF module through the PCF module.

[0084] After collecting all relevant data, the AIF module will report the number of terminals, terminal information, and terminal data volume to the CHF module for billing purposes.

[0085] Finally, the AIF module will report the relevant data to the NEF module, the CHF module will report the billing results to the NEF module at the same time, and the NEF module will report the requested data and the relevant billing results to the corresponding AF module.

[0086] In addition, those skilled in the art will understand that the single request mode is closer to the current service mode in 3GPP networks. For AF modules that need to request a small number of terminals or a low frequency of requests, or AF modules that have high requirements for data timeliness, this mode can better meet the needs. In the single request mode, the network element of passive IoT related services will report the billing function CHF to perform related billing based on the actual request content and quantity.

[0087] In one embodiment, the service mode includes a subscription push service mode.

[0088] Among them, the Network Open Function (NEF) module receives passive IoT service requests that match the service mode sent by the Application Function (AF) module, including: the NEF module receiving a push registration request for passive IoT service subscription sent by the AF module based on the subscription push mode.

[0089] The NEF module initiates a service request to the Passive Internet of Things (AIF) module, which also includes: the NEF module initiating the registration operation of the AF module and subscription requirements on the AIF module based on the push registration request.

[0090] In one embodiment, the service mode includes a subscription push mode, and the billing strategy corresponding to the service mode includes a subscription push billing strategy.

[0091] For example, in the subscription push mode billing, the AIF module actively collects terminal information and pushes relevant status information and data according to the relevant subscription information and subscription requirements registered by the AF module on the AIF module. The network billing function module CHF then reports the corresponding billing based on the actual subscription requests, subscription service requirements, and the actual push status of the AIF module.

[0092] The billing process for the subscription push model includes:

[0093] The AF module initiates a passive IoT service subscription and push registration request to the network through the NEF module.

[0094] Upon receiving the request, the NEF module sends a request to the AIF module to register for subscription and to specify the subscription service requirements.

[0095] The NEF module also sends the relevant billing scheme configuration for the AF module subscription push to the CHF module through the PCF module.

[0096] After receiving a subscription registration request, the AIF module will collect relevant terminal information and data according to the specific subscription business requirements, and return the relevant request data for the first subscription.

[0097] After collecting all relevant data, the AIF module will report the number of terminals, terminal information, and terminal data volume to the CHF module for billing purposes.

[0098] Finally, the AIF module will report the relevant data to the NEF module, the CHF module will report the billing results to the NEF module at the same time, and the NEF module will report the requested data and the relevant billing results to the corresponding AF module.

[0099] Based on the subscription push model, the periodic push function will repeat the process of collecting data, reporting to CHF for billing, and finally having NEF push relevant request data and billing information during each subsequent data collection cycle of the AIF module.

[0100] Furthermore, those skilled in the art will understand that the subscription push mode itself is a mode and process for providing related services to AF modules based on the characteristics of passive IoT terminals and services. This mode solves the problem of request congestion that may be caused by a large number of AFs sending requests to AIF modules due to the large number and variety of terminals in passive IoT. This allows the passive IoT network element AIF module on the core network side to manage a large number of passive IoT terminals more orderly and efficiently and provide related services to the same number and variety of AF modules. For this subscription service, based on the corresponding billing scheme and workflow, the network side can provide passive IoT related services to AF modules while also actually billing the corresponding services.

[0101] In one embodiment, during a non-initial periodic subscription in the subscription push mode, the NEF module receives the Ambient UE status information and terminal data reported by the AIF module based on the service request, and further includes:

[0102] The NEF module receives exception information pushed by the AIF module based on the status anomalies of the Ambient UE.

[0103] In one embodiment, the service mode includes a hybrid mode, where the Network Open Function (NEF) module receives a passive IoT service request matching the service mode sent by the AF module, including: the NEF module receiving a remote single data request from the Ambient UE and a push registration request for passive IoT service subscription sent by the AF module based on the hybrid mode, as a service request.

[0104] In one embodiment, the service mode includes a hybrid mode, and the billing policy corresponding to the service mode is configured by the CHF module according to the hybrid billing scheme issued by the PCF module.

[0105] Hybrid billing can be understood as a combination of single-request mode and subscription mode. Therefore, hybrid mode can simultaneously take into account the service characteristics of AF modules, which are used in single-request mode for those with fewer requests or higher requirements for data timeliness, and the service characteristics of some AF modules, which have relatively complex service content, requiring a large amount of relevant terminal data from the network side, and may also have temporary or frequent requirements for high data timeliness. In this case, the AF module can send a single data acquisition request to the AIF module while having already registered the relevant subscription push service with the AIF module. After receiving the relevant request, the AIF module will perform the relevant operations normally according to the single-request mode. Finally, in hybrid mode, the specific billing scheme will be performed by the CHF module according to the actual billing scheme configuration issued by the PCF module and reported to the AF module through the NEF module.

[0106] like Figure 3 As shown, a passive IoT billing method according to another embodiment of this disclosure, applied to a passive IoT function (AIF) module, includes:

[0107] In step S302, the Passive Internet of Things (AIF) module receives a Passive Internet of Things (IoT) service request initiated by the Network Open Function (NEF) module. The service request is sent from the AF module to the NEF module based on the service mode.

[0108] In step S304, the AIF module collects terminal data of the Ambient UE based on the subscription list of the Ambient UE carried by the AF module in the service request.

[0109] In step S306, the AIF module reports the terminal data to the billing function CHF module, which then bills the terminal data based on the billing policy and reports the billing result to the NEF module. The NEF module then reports the billing result to the corresponding AF module.

[0110] In this embodiment, the AIF module, as the main functional module of the passive IoT billing system, collects terminal data of the Ambient UEs in the subscription list carried in the service request when it receives a passive IoT service request. This terminal data is then reported to the CHF module, and the PCF module sends a billing policy corresponding to the service mode to the CHF module. This enables billing of passive IoT terminals when providing network access and when the AF module provides passive IoT-related data and information services. This provides more efficient network services when deploying passive IoT terminals and services in the network, ensuring the reliable and efficient operation of the passive IoT system.

[0111] In one embodiment, the AIF module collects terminal data of the Ambient UE based on the subscription list of the passive Internet terminal (AmbientUE) carried by the AF module in the service request, including:

[0112] The AIF module stores complete terminal data and directly collects terminal data.

[0113] Among them, the operation of directly collecting terminal data is usually performed in single request mode.

[0114] The AIF module does not store complete terminal data, so it requests terminal data belonging to the Ambient UE in the subscription list from the Radio Access Network (RAN) module of the Passive Internet of Things (AIoT). The RAN module then broadcasts the data reporting request to the Ambient UEs within its coverage area and reports feedback information to the Mobility Management (AMF) module based on the identification and stored data reported by the Ambient UEs.

[0115] Specifically, the base station broadcasts a data reporting request to Ambient UEs within the coverage area that belong to the subscription list, enabling the Ambient UEs to report terminal data based on the reporting request, thereby ensuring the accuracy of the billing operation.

[0116] The AIF module receives the status and mobility information of the Ambient UE reported by the AMF module based on feedback information. Based on the status and mobility information, the AIF module reports the number and status information of the Ambient UE, terminal data, and the number of abnormal terminals to the CHF module for billing operations.

[0117] Specifically, mobility information may include location information of Ambient UEs, and terminal data includes the number and status information of Ambient UEs, terminal data, and the number of abnormal terminals. The number of valid terminals is determined based on the number of Ambient UEs and the number of abnormal terminals, the specific data volume is determined based on the data volume and type, and billing operations are performed based on the specific data volume and the number of valid terminals.

[0118] In one embodiment, before the AIF module reports terminal data to the billing function CHF module, the method further includes: the AIF module reporting the service mode to the policy control function PCF module, so that the PCF module sends the configuration file of the billing policy corresponding to the service mode to the CHF module.

[0119] In one embodiment, the service mode reported by the AIF module to the Policy Control Function (PCF) module includes: the AIF module reporting any one of the single request mode, subscription push mode, and hybrid mode to the PCF module.

[0120] In one embodiment, before the AIF module receives the status information and mobility information of the Ambient UE reported by the AMF module based on feedback information in a single request mode, or in the first subscription in a subscription push mode, or in the first request in a hybrid mode, the AIF module further includes: receiving the correspondence information and terminal data reported by the RAN module based on identification and storage data, wherein the correspondence information is the correspondence between the RAN module and the Ambient UE.

[0121] In this embodiment, in the single request mode, or in the first subscription of the subscription push mode, or in the first request of the hybrid mode, the correspondence facilitates quick retrieval when querying the terminal to determine the terminal that needs to collect data.

[0122] In one embodiment, the AIF module reports terminal data to the billing function CHF module, and further includes: in single request mode, the AIF module reports the status information of the Ambient UE and the terminal data obtained based on the remote single data request to the NEF.

[0123] In one embodiment, the AIF module reports terminal data to the billing function CHF module, and further includes: in the first subscription of the subscription push mode, the AIF module reports the status information of the Ambient UE and the terminal data of the first subscription obtained based on the push registration request to the NEF.

[0124] In one embodiment, in a non-initial periodic subscription of the subscription push mode, the AIF module collects terminal data of the passive Internet terminal Ambient UE based on service requests, including: the AIF module periodically collects the latest terminal data that needs to be billed.

[0125] In this embodiment, in order to ensure the timeliness and effectiveness of billing, the AIF module needs to periodically collect the latest terminal data that needs to be billed, so as to ensure the timeliness of the terminal data.

[0126] In one embodiment, in a non-first-time periodic subscription in the subscription push mode, after the AIF module receives the status information and mobility information of the Ambient UE reported by the AMF module based on feedback information, the AIF module further includes: pushing the status information of the Ambient UE and terminal data obtained based on the service subscription push registration request to the NEF; and when a terminal with an abnormal status is detected, the AIF module pushes the abnormal information of the abnormal Ambient UE to the NEF.

[0127] like Figure 4 As shown, a passive Internet of Things (IoT) billing method according to another embodiment of this disclosure, applied to a Radio Access Network (RAN) module, includes:

[0128] In step S402, the Radio Access Network (RAN) module of the Passive Internet of Things (IoT) receives a service request from the Passive Internet of Things Function (AIF) module for terminal data of the Passive Internet Terminal (Ambient UE).

[0129] In step S404, the RAN module receives the data reported by the Ambient UE in response to the service request.

[0130] In step S406, the RAN module reports feedback information to the Mobility Management (AMF) module based on the reported data. The AMF module then reports the status and mobility information of the Ambient UE to the AIF module based on the feedback information. The AIF module then obtains terminal data based on the status and mobility information. The AIF module reports the terminal data to the Charging Function (CHF) module, which performs charging on the terminal data based on the charging policy and reports the charging result to the NEF module. The NEF module then reports the charging result to the corresponding AF module.

[0131] In this embodiment, on the RAN module side, in order to ensure that complete terminal data requiring billing can be obtained, if the detected data is incomplete, the Ambient UE needs to report its ID and data, and further report it to the AIF module. This realizes the function of billing passive IoT terminals when providing network access to passive IoT terminals and when the AF module provides passive IoT-related data and information services. This provides more efficient network services when deploying passive IoT terminals and services in the network, ensuring the reliable and efficient operation of the passive IoT system.

[0132] In one embodiment, the RAN module receives reported data from the Ambient UE in response to a service request, including:

[0133] The RAN module broadcasts a data reporting request to the Ambient UEs within its coverage area.

[0134] The RAN module receives the identifier and stored data reported by the Ambient UE as the reported data.

[0135] In one embodiment, the RAN module reports feedback information to the mobility management AMF module based on the reported data, including:

[0136] The RAN module reports the correspondence information and the location information of the Ambient UE to the AMF module based on the identification and storage data. The correspondence information is the correspondence between the RAN module and the Ambient UE.

[0137] In single-request mode, or in the initial subscription of subscription-push mode, or in the initial request of hybrid mode, the RAN module reports the corresponding relationship information and terminal data to the AIF module based on the identifier and stored data.

[0138] In non-initial periodic subscriptions under the subscription push mode, the RAN module reports corresponding relationship information and terminal data to the AMF module based on the identifier and stored data.

[0139] like Figure 5 As shown, based on the interaction of network elements in a passive IoT system, and according to another embodiment of the passive IoT billing method of this disclosure, implemented in a single-use mode, it includes:

[0140] Step S502: The AF module remotely requests a single Ambient UE data.

[0141] In step S504, the NEF module initiates a single Ambient UE information and data request.

[0142] Step S506: NEF module registers subscription billing policy.

[0143] In step S508, the PCF module requests the CHF module to update the billing policy configuration.

[0144] Step S510A: If AIF has no relevant data or the data is incomplete, request Ambient UE to report the data.

[0145] Step S510B: If AIF has no relevant data or the data is incomplete, request Ambient UE to report the data.

[0146] In step S512, the corresponding base station broadcasts a data reporting request to all Ambient UEs within the range.

[0147] Step S514: Ambient UE reports ID and stores data.

[0148] In step S516, the RAN module reports the correspondence information between the terminal and the base station, as well as the location information.

[0149] In step S518, the RAN module reports the correspondence information between the terminal and the base station, as well as the terminal data.

[0150] In step S520, the AMF module reports terminal status information and mobility information.

[0151] Step S522: The AIF module reports the service type of the single request mode.

[0152] Step S524: The PCF module issues the configuration file for the single-request billing policy.

[0153] Step S526: The AIF module reports the content used to perform the billing operation this time.

[0154] The data used to perform the billing operation includes the number of terminals, terminal status information, terminal data volume and type, and the number of abnormal interruptions.

[0155] Step S528: The CHF module reports the billing results.

[0156] In step S530, the AIF module returns the terminal status and terminal data requested in this transaction.

[0157] In step S532, the NEF module pushes terminal status information, terminal data, and billing results.

[0158] like Figure 6 As shown, based on the interaction of network elements in a passive IoT system, and according to another embodiment of the passive IoT billing method of this disclosure, the initial subscription process based on a subscription push mode is implemented, including:

[0159] In step S602, the AF module remotely requests to subscribe to Ambient UE data.

[0160] In step S604, the NEF module initiates AF registration, registering the AF and subscription requirements on the AIF.

[0161] Step S606: NEF module registers subscription billing policy.

[0162] In step S608, the CF module requests the CHF module to update the billing policy configuration.

[0163] In step S610, the AIF module requests all Ambient UEs registered with AIF to report the latest data.

[0164] In step S612, the corresponding base station broadcasts a data reporting request to all Ambient UEs within the range.

[0165] Step S614: Ambient UE reports ID and stores data.

[0166] In step S616, the RAN module reports the correspondence information between the terminal and the base station, as well as the location information.

[0167] In step S618, the RAN module reports the correspondence information between the terminal and the base station, as well as the terminal data.

[0168] In step S620, the AMF module reports terminal status information and mobility information.

[0169] Step S622: The AIF module reports the service type of the subscription push mode.

[0170] Step S624: The PCF module distributes the configuration file for the subscription push billing strategy.

[0171] Step S626: The AIF module reports the content used to perform the billing operation this time.

[0172] Step S628: The CHF module reports the billing results.

[0173] In step S630, the AIF module returns the terminal status and terminal data of the initial subscription.

[0174] In step S632, the NEF module pushes terminal status information, terminal data, and billing results.

[0175] like Figure 7 As shown, based on the interaction of network elements in a passive IoT system, and according to another embodiment of the passive IoT billing method of this disclosure, a periodic subscription and push process based on a subscription and push mode is implemented, including:

[0176] In step S702, the AIF module periodically collects Ambient UE data.

[0177] In step S704, the AIF module requests all Ambient UEs registered with AIF to report the latest data.

[0178] Step S706: The corresponding base station broadcasts a data reporting request to all Ambient UEs within the range.

[0179] Step S708: Ambient UE reports ID and stores data.

[0180] In step S710, the RAN module reports the correspondence information between the terminal and the base station, as well as the location information.

[0181] In step S712, the RAN module reports the correspondence information between the terminal and the base station, as well as the terminal data.

[0182] In step S714, the AMF module reports terminal status information and mobility information.

[0183] In step S716A, after processing the data, the AIF module pushes the terminal status and terminal data according to the subscription service configuration.

[0184] In step S716B, if the AIF module detects an abnormal terminal, it directly pushes the abnormal information to the subscriber.

[0185] Step S718: The AIF module reports the service type of the subscription push mode.

[0186] Step S720: The PCF module distributes the configuration file for the subscription push billing strategy.

[0187] Step S722: The AIF module reports the content used to perform the billing operation this time.

[0188] Step S724: The CHF module reports the billing results.

[0189] Step S726: The NEF module pushes terminal status information, terminal data, and billing results.

[0190] It should be noted that the above figures are merely illustrative of the processes included in the method according to exemplary embodiments of the present invention, and are not intended to be limiting. It is readily understood that the processes shown in the above figures do not indicate or limit the temporal order of these processes. Furthermore, it is readily understood that these processes may, for example, be executed synchronously or asynchronously in multiple modules.

[0191] The following reference Figure 8 To describe a passive Internet of Things (IoT) billing device 800 according to an embodiment of the present invention. Figure 8 The passive IoT billing device 800 shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.

[0192] The passive IoT billing device 800 is manifested as a hardware module. Components of the passive IoT billing device 800 may include, but are not limited to: a first receiving module 802, used by the Network Open Function (NEF) module to receive a passive IoT service request matching the service mode sent by the AF module, the service request including the AF module's subscription list for passive Internet terminal Ambient UE; an initiating module 804, used by the NEF module to initiate a service request to the Passive IoT Function (AIF) module, so that the AIF module reports the service mode to the Policy Control Function (PCF) module, causing the PCF module to send a billing policy corresponding to the service mode to the Billing Function (CHF) module, and the AIF module reports the terminal data of Ambient UE collected based on the subscription list to the CHF module, which then bills the terminal data based on the billing policy; the first receiving module 802 is also used for: the NEF module receiving the billing results reported by the CHF module; and a first reporting module 806, used by the NEF module to report the billing results to the corresponding AF module.

[0193] The following reference Figure 9 To describe a passive Internet of Things (IoT) billing device 900 according to an embodiment of the present invention. Figure 9 The passive IoT billing device 900 shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.

[0194] The passive IoT billing device 900 is manifested in the form of a hardware module. Components of the passive IoT billing device 900 may include, but are not limited to: a second receiving module 902, used by the passive IoT function AIF module to receive passive IoT service requests initiated by the Network Open Function NEF module, the service request being sent to the NEF module by the AF module based on the service mode; a collection module 904, used by the AIF module to collect terminal data of the Ambient UE based on the subscription list of the passive Internet terminal Ambient UE carried in the service request; and a second reporting module 906, used by the AIF module to report the terminal data to the billing function CHF module, the CHF module to bill the terminal data based on the billing policy, report the billing result to the NEF module, and the NEF module to report the billing result to the corresponding AF module.

[0195] The following reference Figure 10 To describe a passive Internet of Things (IoT) billing device 1000 according to an embodiment of the present invention. Figure 10 The passive IoT billing device 1000 shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.

[0196] The passive IoT billing device 1000 is manifested in the form of a hardware module. Components of the passive IoT billing device 1000 may include, but are not limited to: a third receiving module 1002, used by the radio access network (RAN) module of the passive IoT to receive service requests for terminal data from the passive IoT function (AIF) module to the passive Internet terminal (Ambient UE); the third receiving module 1002 is also used by the RAN module to receive reported data from the Ambient UE in response to the service request; and a third reporting module 1004, used by the RAN module to report feedback information to the mobility management (AMF) module based on the reported data, so that the AMF module can report the status information and mobility information of the Ambient UE to the AIF module based on the feedback information, enabling the AIF module to obtain terminal data based on the status information and mobility information, and the AIF module to report the terminal data to the billing function (CHF) module, which bills the terminal data based on the billing policy and reports the billing result to the NEF module, which then reports the billing result to the corresponding AF module.

[0197] Those skilled in the art will understand that various aspects of the present invention can be implemented as systems, methods, or program products. Therefore, various aspects of the present invention can be specifically implemented in the following forms: entirely in hardware, entirely in software (including firmware, microcode, etc.), or in a combination of hardware and software, collectively referred to herein as “circuit,” “module,” or “system.”

[0198] The following reference Figure 11To describe an electronic device 1100 according to this embodiment of the present invention, it may be a network device or a terminal. Figure 11 The electronic device 1100 shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.

[0199] like Figure 11 As shown, the electronic device 1100 is manifested in the form of a general-purpose computing device. The components of the electronic device 1100 may include, but are not limited to: at least one processing unit 1110, at least one storage unit 1120, and a bus 1130 connecting different system components (including storage unit 1120 and processing unit 1110).

[0200] The storage unit stores program code that can be executed by the processing unit 1110, causing the processing unit 1110 to perform the steps described in the "Exemplary Methods" section of this specification according to various exemplary embodiments of the present invention. For example, the processing unit 1110 can perform actions such as... Figures 2 to 7 The described solution.

[0201] Storage unit 1120 may include readable media in the form of volatile storage units, such as random access memory (RAM) 11201 and / or cache memory 11202, and may further include read-only memory (ROM) 11203.

[0202] Storage unit 1120 may also include a program / utility 11204 having a set (at least one) program module 11205, such program module 11205 including but not limited to: operating system, one or more application programs, other program modules and program data, each or some combination of these examples may include an implementation of a network environment.

[0203] Bus 1130 can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any of the various bus structures.

[0204] Electronic device 1100 can also communicate with one or more external devices 1170 (e.g., keyboard, pointing device, Bluetooth device, etc.), one or more devices that enable a user to interact with electronic device 1100, and / or any device that enables electronic device 1100 to communicate with one or more other computing devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 1150. Furthermore, electronic device 1100 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 1160. As shown, network adapter 1160 communicates with other modules of electronic device 1100 via bus 1130. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with electronic device 1100, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0205] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, terminal device, or network device, etc.) to execute the methods according to the embodiments of this disclosure.

[0206] In exemplary embodiments of this disclosure, a computer-readable storage medium is also provided, on which a program product capable of implementing the methods described above is stored. In some possible embodiments, various aspects of the invention may also be implemented as a program product comprising program code that, when the program product is run on an electronic device, causes the electronic device to perform the steps of the various exemplary embodiments of the invention described in the "Exemplary Methods" section above.

[0207] According to embodiments of the present invention, a program product for implementing the above-described method may employ a portable compact disc read-only memory (CD-ROM) and include program code, and may run on an electronic device, such as a personal computer. However, the program product of the present invention is not limited thereto. In this document, a readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system, apparatus, or device.

[0208] The program product may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0209] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of sending, propagating, or transmitting programs for use by or in conjunction with an instruction execution system, apparatus, or device.

[0210] The program code contained on the readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.

[0211] Program code for performing the operations of this invention can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0212] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to embodiments of this disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0213] Furthermore, although the steps of the method in this disclosure are described in a specific order in the accompanying drawings, this does not require or imply that the steps must be performed in that specific order, or that all the steps shown must be performed to achieve the desired result. Additional or alternative steps may be omitted, multiple steps may be combined into one step, and / or a step may be broken down into multiple steps.

[0214] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, mobile terminal, or network device, etc.) to execute the methods according to the embodiments of this disclosure.

[0215] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the appended claims.

Claims

1. A passive Internet of Things (IoT) billing method, characterized in that, include: The Network Open Function (NEF) module receives a passive IoT service request matching the service mode sent by the Application Function (AF) module. The service request includes the subscription list of the passive Internet terminal Ambient UE by the AF module. The NEF module initiates the service request to the Passive Internet of Things Function (AIF) module, so that the AIF module reports the service mode to the Policy Control Function (PCF) module, and the PCF module sends the billing policy corresponding to the service mode to the Billing Function (CHF) module. The AIF module reports the terminal data of the Ambient UE collected based on the subscription list to the CHF module, and the CHF module bills the terminal data based on the billing policy. The NEF module receives the billing results reported by the CHF module; The NEF module reports the billing results to the corresponding AF module.

2. The passive IoT billing method according to claim 1, characterized in that, After the NEF module initiates the service request to the Passive Internet of Things (AIF) module, it also includes: The NEF module receives the status information of the Ambient UE belonging to the subscription list and the terminal data reported by the AIF module based on the service request.

3. The passive IoT billing method according to claim 1, characterized in that, Before the AIF module reports the service mode to the Policy Control Function (PCF) module, the following is also included: The NEF module performs a registration operation for the billing policy subscription to the PCF module, so that the PCF module can update the billing policy configuration of the CHF module.

4. The passive IoT billing method according to claim 2, characterized in that, The NEF module reports the billing result to the corresponding AF module, and also includes: The NEF module also pushes the status information of the Ambient UE and the terminal data to the AF module.

5. The passive IoT billing method according to any one of claims 1 to 4, characterized in that, The service modes include a single request mode, where the Network Open Function (NEF) module receives passive IoT service requests matching the service mode sent by the Application Function (AF) module, including: The NEF module receives the remote single data request from the Ambient UE sent by the AF module based on the single request mode, as the service request.

6. The passive IoT billing method according to claim 3, characterized in that, The service modes include a single request mode. The billing strategies corresponding to the service mode include a single-request billing strategy.

7. The passive IoT billing method according to any one of claims 1 to 4, characterized in that, The service model includes a subscription push model. The Network Open Function (NEF) module receives passive IoT service requests matching the service mode from the Application Function (AF) module, including: The NEF module receives a push registration request for the passive IoT service subscription sent by the AF module based on the subscription push mode. The NEF module initiates the service request to the Passive Internet of Things (AIF) module, which also includes: The NEF module initiates the registration operation of the AF module and the subscription request on the AIF module based on the push registration request.

8. The passive IoT billing method according to claim 3, characterized in that, The service model includes a subscription push model. The billing strategies corresponding to the service model include subscription push billing strategies.

9. The passive IoT billing method according to claim 8, characterized in that, In the non-initial periodic subscription of the subscription push mode, the NEF module receives the status information of the Ambient UE and the terminal data reported by the AIF module based on the service request, and further includes: The NEF module receives the exception information pushed by the AIF module based on the abnormal status of the Ambient UE.

10. The passive IoT billing method according to any one of claims 1 to 4, characterized in that, The service mode includes a hybrid mode, where the Network Open Function (NEF) module receives passive IoT service requests matching the service mode sent by the Application Function (AF) module, including: The NEF module receives the remote single data request from the Ambient UE and the push registration request for the passive IoT service subscription sent by the AF module based on the hybrid mode, as the service request.

11. The passive IoT billing method according to claim 3, characterized in that, The service model includes a hybrid model. The billing strategy corresponding to the service mode is configured by the CHF module according to the hybrid billing scheme issued by the PCF module.

12. A passive Internet of Things (IoT) billing method, characterized in that, include: The Passive Internet of Things (AIF) module receives a passive Internet of Things (IoT) service request initiated by the Network Open Function (NEF) module. The service request is sent to the NEF module by the Application Function (AF) module based on the service mode. The AIF module reports the service mode to the Policy Control Function (PCF) module, which then sends the billing policy corresponding to the service mode to the CHF module. The AIF module collects terminal data of the Ambient UE based on the subscription list of the Ambient UE carried by the AF module in the service request; The AIF module reports the terminal data to the billing function CHF module, which then bills the terminal data based on the billing policy and reports the billing result to the NEF module. The NEF module then reports the billing result to the corresponding AF module.

13. The passive IoT billing method according to claim 12, characterized in that, The AIF module collects terminal data of the Ambient UE based on the subscription list of the AF module for the passive Internet terminal (Ambient UE) carried in the service request, including: The AIF module stores complete terminal data and directly collects the terminal data. If the AIF module does not store complete terminal data, it requests terminal data belonging to the Ambient UE in the subscription list from the Radio Access Network (RAN) module of the Passive Internet of Things (AIoT). The RAN module then broadcasts the data reporting request to the Ambient UE within its coverage area and reports feedback information to the Mobility Management (AMF) module based on the identification and stored data reported by the Ambient UE. The AIF module receives the status information and mobility information of the Ambient UE reported by the AMF module based on the feedback information, and reports the number and status information of the Ambient UE, the terminal data, and the number of abnormal terminals to the CHF module based on the status information and mobility information, and performs billing operations.

14. The passive IoT billing method according to claim 13, characterized in that, Before the AIF module reports the terminal data to the billing function CHF module, it also includes: The AIF module reports the service mode to the Policy Control Function (PCF) module, which then sends the configuration file of the billing policy corresponding to the service mode to the CHF module.

15. The passive IoT billing method according to claim 14, characterized in that, The service modes reported by the AIF module to the Policy Control Function (PCF) module include: The AIF module reports any one of the following modes to the Policy Control Function (PCF) module: single request mode, subscription push mode, and hybrid mode.

16. The passive IoT billing method according to claim 15, characterized in that, In the single-request mode, or in the initial subscription of the subscription push mode, or in the initial request of the hybrid mode, if the AIF module does not store complete terminal data, it also includes: The AIF module receives the correspondence information reported by the RAN module based on the identifier and the stored data, and the terminal data. The correspondence information is the correspondence between the RAN module and the Ambient UE.

17. The passive IoT billing method according to claim 15, characterized in that, The AIF module reports the terminal data to the billing function CHF module, and also includes: In the single request mode, the AIF module reports the status information of the Ambient UE and the terminal data obtained based on the remote single data request to the NEF.

18. The passive IoT billing method according to claim 15, characterized in that, The AIF module reports the terminal data to the billing function CHF module, and also includes: In the initial subscription of the subscription push mode, the AIF module reports the status information of the Ambient UE and the terminal data of the initial subscription obtained based on the push registration request to the NEF.

19. The passive IoT billing method according to claim 15, characterized in that, In the non-initial periodic subscription of the subscription push mode, the AIF module collects terminal data of the passive Internet terminal Ambient UE based on the service request, including: The AIF module periodically collects the latest terminal data that requires billing.

20. The passive IoT billing method according to claim 19, characterized in that, In the non-initial periodic subscription of the subscription push mode, after the AIF module receives the status information and mobility information of the Ambient UE reported by the AMF module based on the feedback information, it further includes: The AIF module pushes the status information of the Ambient UE and the terminal data obtained from the service subscription push registration request to the NEF; and When a terminal with an abnormal state is detected, the AIF module pushes the abnormal Ambient UE information to the NEF.

21. A passive Internet of Things (IoT) billing method, characterized in that, include: The Radio Access Network (RAN) module of the Passive Internet of Things (Passive IoT) receives a service request from the Passive Internet Function (AIF) module for terminal data of the Passive Internet Terminal (Ambient UE). The service request includes the subscription list of the Passive Internet Terminal (Ambient UE) by the AF module. The RAN module receives the reported data from the Ambient UE in response to the service request; The RAN module reports feedback information to the Mobility Management (AMF) module based on the reported data. The AMF module then reports the status and mobility information of the Ambient UE to the AIF module based on the feedback information. The AIF module obtains the terminal data based on the status and mobility information. The AIF module reports the terminal data to the Charging Function (CHF) module. The CHF module charges the terminal data based on the charging policy and reports the charging result to the NEF module. The NEF module then reports the charging result to the corresponding AF module. The NEF module initiates a service request to the Passive Internet of Things (AIF) module. The AIF module reports the service mode to the Policy Control Function (PCF) module, which then sends the charging policy corresponding to the service mode to the CHF module.

22. The passive IoT billing method according to claim 21, characterized in that, The RAN module receives the reported data from the Ambient UE in response to the service request, including: The RAN module broadcasts a data reporting request to the Ambient UE within the coverage area; The RAN module receives the identifier and stored data reported by the Ambient UE as the reported data.

23. The passive IoT billing method according to claim 22, characterized in that, The RAN module reports feedback information to the mobility management AMF module based on the reported data, including: The RAN module reports the correspondence information and the location information of the Ambient UE to the AMF module based on the identifier and the stored data. The correspondence information is the correspondence between the RAN module and the Ambient UE. In single-request mode, or in the first subscription in subscription-push mode, or in the first request in hybrid mode, the RAN module reports the correspondence information and the terminal data to the AIF module based on the identifier and the stored data; In non-initial periodic subscriptions in the subscription push mode, the RAN module reports the correspondence information and the terminal data to the AMF module based on the identifier and the stored data.

24. A passive Internet of Things (IoT) billing system, characterized in that, include: The Network Open Function (NEF) module, Application Function (AF) module, Passive Internet Terminal (Ambient UE), Passive Internet of Things Function (AIF) module, Policy Control Function (PCF) module, and Billing Function (CHF) module as described in claims 1 to 11; Mobility Management (AMF) module as described in claims 12-20; and At least one of the Radio Access Network (RAN) modules as described in claims 21 to 23.

25. A network device, characterized in that, include: processor; as well as Memory for storing the executable instructions of the processor; The processor is configured to execute the passive IoT billing method according to any one of claims 1 to 11, 12 to 20, or 21 to 23 by executing the executable instructions.

26. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the passive Internet of Things billing method according to any one of claims 1 to 23.

Images