Aggregated billing methods, electronic devices, storage media and computer program products

Abstract

This application discloses an aggregation billing method, which includes: in response to receiving a communication resource request from any of a plurality of user terminals participating in aggregation billing for the first time, sending a billing request to a billing function network element; receiving a billing response message from the billing function network element, the billing response message including a preset number of communication resources and a billing policy, the preset number of communication resources being determined by the access device in consultation with the billing function network element based on the historical communication resource usage information of the plurality of user terminals participating in aggregation billing; and billing the plurality of user terminals participating in aggregation billing based on the billing response message.

Description

Technical Field

[0001] This application relates to the field of Internet of Things (IoT) technology, and in particular to an aggregated billing method, electronic device, storage medium, and computer program product. Background Technology

[0002] In related technologies, when IoT terminals perform billing, they need to interact directly with the Charge Handling Function (CHF) in the Business and Operation Support System (BOSS). When a large number of IoT terminals connect to the CHF at the same time and request billing operations, it will lead to excessive interaction between IoT terminals and the CHF, which can easily cause CHF to overload. Summary of the Invention

[0003] In view of this, embodiments of this application provide an aggregated billing method, an electronic device, a storage medium, and a computer program product.

[0004] The technical solution of this application embodiment is implemented as follows:

[0005] This application provides an aggregation billing method applied to an access device. The method includes: in response to receiving a communication resource request from any of a plurality of user terminals participating in aggregation billing for the first time, sending a billing request to a billing function network element; receiving a billing response message from the billing function network element, the billing response message including a preset number of communication resources and a billing policy, the preset number of communication resources being determined by the access device in consultation with the billing function network element based on the historical communication resource usage information of the plurality of user terminals participating in aggregation billing; and billing the plurality of user terminals participating in aggregation billing based on the billing response message.

[0006] In the above scheme, the billing strategy represents the cost per unit quantity of communication resources; the billing of the multiple user terminals participating in the aggregated billing based on the billing response message includes: deducting the number of communication resources corresponding to the communication resource request from a preset number of communication resources based on the communication resource request sent by the user terminal participating in the aggregated billing; and billing the corresponding user terminal based on the number of deducted communication resources and the billing strategy.

[0007] In the above scheme, the method further includes: if the first process information sent by the preset process is not received within a preset time, a liveness detection message is sent to the preset process; the liveness detection message is used to instruct the preset process to send the first process information to the server.

[0008] In the above scheme, before sending a billing request to the billing function network element, the method further includes: sending aggregated billing subscription messages to multiple user terminals accessing the access device; receiving feedback messages sent by the user terminals; the feedback messages indicating whether the corresponding user terminal agrees or disagrees with aggregated billing.

[0009] In the above scheme, before billing the multiple user terminals participating in the aggregated billing, the method further includes: verifying the communication resource requests initiated by the user terminals participating in the aggregated billing; if among the user terminals participating in the aggregated billing, there is a user terminal whose initiated communication resource request does not match the user terminal's historical communication resource usage information, the user terminal is billed separately.

[0010] In the above scheme, after billing multiple user terminals participating in aggregated billing, the method further includes: monitoring the consumption of communication resources; if the communication resources are exhausted, requesting communication resources from the billing function network element.

[0011] This application also provides an aggregation billing method applied to a billing function network element. The method includes: receiving a billing request from an access device in response to receiving a communication resource request from any of a plurality of user terminals participating in aggregation billing for the first time; sending a billing response message to the access device; the billing response message includes a preset number of communication resources and a billing policy, wherein the preset number of communication resources is determined by the access device in consultation with the billing function network element based on the historical communication resource usage information of the plurality of user terminals participating in aggregation billing.

[0012] In the above scheme, the billing request includes the terminal identifier and billing type of the user terminal; before sending the billing response message to the access device, the method further includes: determining the billing policy corresponding to the user terminal based on the terminal identifier and billing type of the user terminal.

[0013] This application also provides an electronic device, including: a processor and a memory for storing a computer program that can run on the processor, wherein the processor, when running the computer program, executes the steps of the method in the above-described scheme.

[0014] This application also provides a computer storage medium storing a computer program. When the computer program is executed by a processor, it implements the steps of the method applied to the server in the above-described scheme.

[0015] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the method applied to the access device in the above-described scheme.

[0016] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the method applied to the billing function network element in the above scheme.

[0017] This embodiment of the application, in response to the first receipt of a communication resource request from any of the multiple user terminals participating in aggregated billing, sends a billing request to the billing function network element. It then receives a billing response message from the billing function network element, which includes a preset number of communication resources and a billing policy. The preset number of communication resources is determined by the access device in consultation with the billing function network element based on the historical communication resource usage information of the multiple user terminals participating in aggregated billing. Based on the billing response message, billing is performed on the multiple user terminals participating in aggregated billing. In this embodiment, the access device obtains communication resources and billing policies from the billing function network element and performs billing on the multiple user terminals participating in aggregated billing. The multiple user terminals participating in aggregated billing do not directly interact with the billing function network element, thereby alleviating the service pressure on the billing function network element and improving the user's billing experience. Attached Figure Description

[0018] Figure 1 A flowchart illustrating an aggregated billing method provided in an embodiment of this application;

[0019] Figure 2 A flowchart illustrating another aggregated billing method provided in this application embodiment.

[0020] Figure 3 This is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0021] The present application will now be described in further detail with reference to the accompanying drawings and embodiments.

[0022] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application.

[0023] In related technologies, when a terminal requests a price approval from the CHF in the BOSS via an access device, the following process is involved:

[0024] Initiating a billing request: When a terminal needs to perform billing, it sends a billing request to the access device it is connected to. This request usually contains the terminal's identification information, such as the International Mobile Subscriber Identity (IMSI), the International Mobile Equipment Identity (IMEI), as well as the billing type and billing cycle.

[0025] Access device transmits request: The access device is responsible for transmitting the billing request initiated by the terminal to CHF in BOSS. This step may involve data encryption and secure transmission to ensure the privacy and integrity of the billing request.

[0026] Billing Policy Lookup: CHF will look up the corresponding billing policy based on the terminal's identifier and billing type. The billing policy may include information such as billing rules, billing units, and prices, which are usually pre-configured by the operator.

[0027] Billing Calculation: Once a suitable billing strategy is found, CHF will calculate the billing based on the terminal usage and the billing strategy. This may involve factors such as cumulative usage, time, and location to determine the fees to be charged.

[0028] Generate billing details: Based on the results of the batch pricing calculation, CHF will generate billing details, which will describe in detail the terminal usage, billing policy and corresponding cost amount.

[0029] Returning billing results: CHF returns the generated billing details and cost amount to the access device, which then transmits this information to the terminal, allowing the terminal to understand its billing status based on this information.

[0030] Billing data storage: CHF also stores billing details and related billing data in a database or record system for subsequent queries, report generation, and billing generation.

[0031] However, the aforementioned technologies also have many drawbacks. With the full deployment of 5G (5th Generation Mobile Communication Technology), many IoT terminals utilize 5G networks for various services. In some application environments, the number of IoT terminals is very large. If the original billing method is used, it will lead to excessive interaction between IoT terminals and the billing network (CHF), easily causing CHF overload. Specific drawbacks are manifested in the following aspects:

[0032] Massive connectivity: The Internet of Things (IoT) is characterized by a massive number of terminals, potentially reaching millions or even more. When a large number of IoT terminals simultaneously connect to the 5G network and request billing operations, CHF will face a massive influx of billing requests, exceeding its original processing capacity.

[0033] Frequent interactions: Terminals may send billing requests frequently within a short period of time, especially in certain application scenarios such as industrial automation and intelligent transportation. This requires CHF to process requests at a high frequency, increasing the system load.

[0034] Billing requests are complex: Billing requests from IoT terminals may involve multiple different services and billing policies, resulting in high computational complexity. This consumes more computing resources, leading to a decrease in CHF processing speed.

[0035] Latency issues: Due to frequent interactions and the complexity of billing, processing billing requests may lead to increased latency. This can impact user experience and business processes in time-sensitive applications such as real-time monitoring and remote operation.

[0036] Reduced system availability: If CHF is unable to respond in a timely manner to a large number of billing requests, it may lead to a decrease in system availability, preventing users from performing billing operations normally, and even affecting normal business operations.

[0037] To address the shortcomings of the aforementioned related technologies, this application provides an aggregated billing method that can avoid the problem of excessive burden on CHF caused by a large number of user terminals directly interacting with CHF. To illustrate the technical solution described in this invention, specific embodiments are described below.

[0038] Figure 1 This is a flowchart illustrating an aggregated billing method provided in an embodiment of this application. The execution subject of this method is an access device, such as... Figure 1 As shown, steps 101 to 203 are included:

[0039] Step 101: In response to receiving a communication resource request from any of the multiple user terminals participating in the aggregated billing for the first time, a billing request is sent to the billing function network element.

[0040] In some embodiments, the user terminal can be a server, mobile terminal, computer, etc., and the access device can be a device in a wireless local area network (WLAN) that allows the user terminal to access the network, such as an access point (AP). Generally, users using the same billing package within the network area can be grouped together for aggregated billing.

[0041] In some embodiments, a user terminal can access the network through an access device. Once the user terminal connects to the access device, it becomes a terminal within the network coverage of that access device. The access device can perform aggregated billing for user terminals connected to it, and the user terminal corresponding to the access device is the user terminal that accesses the network through that access device. Specifically, in this embodiment, the terminal interacts with the access device to access the network, and the access device interacts with the billing function network element to obtain billing response messages and bills the terminal's internet access actions.

[0042] In some embodiments, when the access device first receives a communication resource request from a user terminal participating in the aggregation billing, it sends a billing request to the billing function network element. For example, if user terminals A, B, C, and D are participating in aggregation billing, and user terminal A initiates the communication resource request first, then the communication resource request initiated by user terminal A is the first communication resource request received by the access device. If user terminal B subsequently initiates a communication resource request, then it is not the first communication resource request received by the access device. It should be noted that if the members of the user terminals participating in aggregation billing have not changed, the operation in step 101 can be performed only once. If it is necessary to recount the user terminals participating in aggregation billing or if the user terminal members have changed, then step 101 needs to be performed again.

[0043] In some embodiments, the communication resource request initiated by the user terminal is used to request resources for accessing the network. For example, if the user needs to access the internet, the requested communication resource is communication traffic; if the user needs to make a phone call, the requested communication resource is mobile call resources. Specifically, the communication resource request can be a data packet or a message. Further, after the access device initiates a billing request to the billing function network element, it waits for the billing function network element's response in order to bill the user terminals participating in the aggregation billing.

[0044] In some embodiments, a communication resource request may include the user's terminal identifier (IMSI and IMEI) and the user's billing type. Specifically, the user's billing type may be the tariff plan used by the user.

[0045] Step 102: Receive a billing response message from the billing function network element. The billing response message includes a preset number of communication resources and a billing policy. The preset number of communication resources is determined by the access device in consultation with the billing function network element based on the historical communication resource usage information of the multiple user terminals participating in the aggregated billing.

[0046] In some embodiments, the billing function network element can be the CHF in BOSS. When the billing request sent by the access device is received by the billing function network element, it can receive a billing response message issued by the billing function network element. Specifically, the billing response message includes a preset number of communication resources and a billing policy. The communication resources can be mobile data traffic, voice data traffic, etc., and the billing policy can be a rule for billing the user terminal, such as charging the user terminal for each megabyte of data traffic or charging the user terminal for each minute of voice traffic.

[0047] In some embodiments, the number of communication resources corresponding to the preset number in the billing response message can also be called the batch pricing quantity, and the corresponding billing strategy can be called the batch pricing. Based on the batch pricing and the preset number of communication resources, the cost of communication resources consumed by the user terminal can be calculated. Further, the billing function network element can send communication resources to the access device by sending call detail records (CDRs) containing the preset number of communication resources. Here, the CDR can be a data packet.

[0048] In some embodiments, the preset number of communication resources is determined through negotiation between the access device and the billing function network element. Specifically, the access device first obtains historical communication resource information of all user terminals participating in the aggregation billing. This historical communication resource information may include the quantity, trend, and pattern of historical traffic used by the user terminals. Based on the historical communication resource information, the access device predicts the amount of communication resources that each user terminal may use in the future, obtains a predicted amount of communication resources, and negotiates with the billing function network element. The specific negotiation process may involve the access device informing the billing function network element of the amount of communication resources that may be needed in the future, and the billing function network element responding whether it agrees with the communication resource amount suggested by the access device based on factors such as network load and resource allocation. If it does not agree, the access device and the billing function network element need to negotiate again until the negotiation is successful and the preset number of communication resources is obtained.

[0049] Step 103: Based on the billing response message, bill the multiple user terminals participating in the aggregated billing.

[0050] In some embodiments, the communication resource request received from the user terminal in step 101 needs to be processed first, and billing needs to be performed on the corresponding user terminal. When the access device receives another communication resource request from the user terminal, it can calculate the cost incurred by the user terminal when using the network while responding to the user terminal's communication resource request. This involves modifying the access device, which originally only had network access functions, to add a simple billing function, enabling the access device to bill the user terminal based on the billing response message returned by the billing function network element.

[0051] In some embodiments, the communication resource request sent by the user terminal generally includes information such as the type and quantity of traffic to be used. The access device can charge the user terminal based on the amount of traffic used by the user terminal and the billing policy obtained from the billing function network element.

[0052] This embodiment of the application, in response to the first receipt of a communication resource request from any of the multiple user terminals participating in aggregated billing, sends a billing request to the billing function network element. It then receives a billing response message from the billing function network element, which includes a preset number of communication resources and a billing policy. The preset number of communication resources is determined by the access device in consultation with the billing function network element based on the historical communication resource usage information of the multiple user terminals participating in aggregated billing. Based on the billing response message, billing is performed on the multiple user terminals participating in aggregated billing. In this embodiment, the access device obtains communication resources and billing policies from the billing function network element and performs billing on the multiple user terminals participating in aggregated billing. The multiple user terminals participating in aggregated billing do not directly interact with the billing function network element, thereby alleviating the service pressure on the billing function network element and improving the user's billing experience.

[0053] In some embodiments, the billing policy represents the cost per unit quantity of communication resources; the billing of the plurality of user terminals participating in aggregate billing based on the billing response message includes:

[0054] Based on the communication resource request sent by the user terminal participating in the aggregation billing, the number of communication resources corresponding to the communication resource request is deducted from the preset number of communication resources;

[0055] Billing is performed on the corresponding user terminal based on the amount of communication resources deducted and the billing strategy.

[0056] In some embodiments, the billing request sent by the access device may include the user's identifier and billing type. The user can be an electronic device such as a mobile phone, laptop, or desktop computer. Each user can be uniquely identified. The billing type may specifically refer to the billing package used by the user, such as a monthly plan or a data package. The billing function network element can determine the corresponding billing policy based on the user's identifier and billing type and send it to the access device.

[0057] In some embodiments, after receiving a preset amount of communication resources and a billing policy from the billing function network element, the access device can allocate corresponding communication resources to the user terminal when it receives another communication resource request from the user terminal, and perform billing according to the billing policy. For example, if the billing function network element distributes 100GB of traffic, and the user terminal needs to watch videos online, consuming 500MB of traffic, and the billing policy is 1MB / 0.3 yuan, then 500MB of traffic will be deducted from the distributed 100GB of traffic, and the user terminal's consumption amount for this transaction will be calculated as 150 yuan.

[0058] Based on the above embodiments, the interaction between the access device and the user terminal is carried out by the user terminal, which no longer interacts directly with the billing function network element. This greatly reduces the service pressure on the billing function network element, while not affecting the billing needs of the user terminal.

[0059] In some embodiments, before sending an accounting request to the accounting function network element, the method further includes:

[0060] Send aggregated billing subscription messages to multiple user terminals connected to the access device;

[0061] Receive feedback messages sent by the user terminal; the feedback messages indicate whether the corresponding user terminal agrees or disagrees with aggregate billing.

[0062] In some embodiments, before performing aggregated billing on user terminals, it is necessary to determine whether the user agrees to participate in aggregated billing. This can be achieved by the access device sending an aggregated billing subscription message to all connected user terminals. Specifically, the aggregated billing subscription message inquires whether the user terminal agrees to participate in aggregated billing. The user terminal can send a feedback message to indicate whether it agrees or disagrees to participate in aggregated billing. User terminals that disagree with participating in aggregated billing can be billed separately, i.e., using general billing methods in related technologies.

[0063] In some embodiments, when a new user terminal connects to the access device, an aggregated billing subscription message can be sent to it immediately to confirm whether it participates in aggregated billing.

[0064] Based on the above embodiments, before performing aggregated billing, the number of users who agree to participate in aggregated billing can be counted, and billing can be performed using the billing method specified by the user. Users are not forced to use aggregated billing, so that users can have a better billing experience.

[0065] In some embodiments, before billing the plurality of user terminals participating in aggregated billing, the method further includes:

[0066] The communication resource requests initiated by the user terminals participating in the aggregation billing are verified;

[0067] If, among the user terminals participating in the aggregated billing, there is a communication resource request initiated by a user terminal that does not match the user terminal's historical communication resource usage information, the user terminal will be billed separately.

[0068] In some embodiments, before billing a user, the communication resource request initiated by the user is examined to determine whether the resource currently requested by the user is the same as the resource used in the past. For example, if the user has historically used mobile data for internet access, but is currently requesting voice resources, then the user is removed from the aggregated billing and billed separately. It should be noted that users participating in aggregated billing can have similar network behaviors such as data usage habits and data usage types. For users whose network behaviors suddenly change, aggregated billing also requires a separate billing strategy for their tariff requests, which consumes additional network resources. Therefore, they are removed from aggregated billing and billed separately.

[0069] In some embodiments, for users removed from aggregated billing, they are allowed to reapply for aggregated billing. Their historical communication resource usage is evaluated, and if it is similar to other users currently participating in aggregated billing, they are allowed to rejoin. For users whose repeated requests for communication resources do not match their historical communication resource usage information, they can be temporarily blacklisted, prohibiting them from participating in aggregated billing for a period of time. The blacklisting period can be determined based on the number of times the user's requested communication resources do not match their historical usage information; the two can be positively correlated. If a blacklisted user's requests for communication resources match their historical requests within a certain period, the blacklisting period can be appropriately reduced.

[0070] Based on the above embodiments, separate billing can be performed for user terminals whose requested communication resources do not match their historical communication resource usage information, which can ensure the billing efficiency of aggregate billing and avoid generating additional traffic consumption.

[0071] In some embodiments, after billing multiple user terminals participating in aggregated billing, the method further includes:

[0072] Monitor the consumption of the communication resources;

[0073] If the communication resources are exhausted, request communication resources from the billing function network element.

[0074] In some embodiments, when the access device bills the user terminal, it can simultaneously monitor the consumption of communication resources issued by the billing function network element. It is understood that the access device consumes communication resources while billing the user terminal. When the communication resources are exhausted, the access device needs to request communication resources again from the billing function network element.

[0075] In some embodiments, communication resources can be requested from the billing function network element when the communication resource reserve is less than 5%. The specific value can be determined based on factors such as the consumption rate of communication resources, and is not specifically limited here. Furthermore, when the access device requests communication resources from the billing function network element, it can first perform statistics on the user's historical communication resource usage information, and then request communication resources from the billing function network element. This can also be understood as a process of negotiating with the decryption function network element again.

[0076] Based on the above embodiments, by monitoring the consumption of communication resources and requesting communication resources from the billing function network element when communication resources are exhausted, the continuous execution of aggregated billing is ensured, providing users with continuous billing services.

[0077] Figure 2 This application provides an alternative aggregated billing method, which is applied to a billing function network element, such as... Figure 2 As shown, this includes steps 201 to 202:

[0078] Step 201: The receiving access device responds to the first receipt of a communication resource request sent by any of the multiple user terminals participating in the aggregated billing.

[0079] In some embodiments, the billing function network element can receive aggregated billing requests initiated by the access device and billing requests initiated by individual user terminals, respectively. After receiving a billing request sent by the access terminal, the corresponding billing policy can be determined based on the user terminal identifier and billing type included in the billing request.

[0080] Step 202: Send a billing response message to the access device; the billing response message includes a preset number of communication resources and a billing policy, wherein the preset number of communication resources is determined by the access device in consultation with the billing network element based on the historical communication resource usage information of the multiple user terminals participating in aggregated billing.

[0081] In some embodiments, once the billing function network element determines the corresponding billing policy, it can send the previously negotiated preset number of communication resources and the billing policy as a billing response message to the access device. Specifically, in cases where the number of communication resources is large, the messages can be sent to the access device in batches.

[0082] Furthermore, when the communication resources of the access device are exhausted, it will request communication resources again from the billing function network element. The billing function network element can then renegotiate with the access device to determine how many communication resources to allocate to the access device.

[0083] Based on the above facts, the billing function network element only needs to interact with the access device to realize billing for multiple user terminals, which reduces the service pressure of the billing function network element and can better meet the billing needs of users.

[0084] In some embodiments, when a terminal accesses a cellular network, the base station equipment can detect the way the terminal accesses the cellular network. The main ways include the following two:

[0085] Method 1: The terminal directly connects to the base station.

[0086] Terminal sends access request: The terminal first sends an access request within the range of nearby base stations to connect to the 5G cellular network.

[0087] The base station receives and verifies the request: When the base station receives the terminal's access request, it performs identity verification and permission checks to ensure that the terminal has the right to access the network.

[0088] Base station resource allocation: If the verification is successful, the base station allocates network resources to the terminal, including frequency bands, bandwidth, etc., so that the terminal can communicate with the network.

[0089] Terminal establishes connection with base station: The terminal uses allocated resources to establish a connection with the base station and becomes part of the network.

[0090] Method 2: The terminal accesses the base station through the access point.

[0091] Terminal sends access request: Similar to method 1, the IoT terminal sends an access request, but this time the request is to connect to the access point, rather than directly to the base station.

[0092] Access point receives and verifies requests: When the access point receives an access request from a terminal, it performs identity verification and permission checks to ensure that the terminal has the right to access the network.

[0093] Access point resource allocation: If the verification is successful, the access point allocates resources to the terminal, similar to the base station resource allocation in method 1.

[0094] Terminal establishes connection with access point: The terminal uses the allocated resources to establish a connection with the access point and becomes a device under the access point.

[0095] Access point communication with base station: The access point acts as an intermediate device, communicating with nearby base stations and transmitting data from terminals connected to it to the base stations.

[0096] Base station allocates resources to access points: Base stations may allocate specific resources to access points to facilitate communication between the access points and the base station.

[0097] For terminals accessing the IoT via method 1, conventional billing methods from relevant technologies are used. For terminals accessing the IoT via method 2, the base station sends an aggregated billing subscription to the access point. Upon receiving the aggregated billing subscription, the access point forwards it to the terminals connected to that access point. After receiving the aggregated billing subscription, the terminal determines whether to accept the aggregated billing based on its settings and sends the result back to the access point. This process can be divided into the following steps.

[0098] Terminal receives aggregated billing subscription: The terminal receives an aggregated billing subscription message from the access point. This message indicates that the base station wants to perform aggregated billing for terminals connected to it.

[0099] Terminal parsing subscription messages: IoT terminals parse the aggregated billing subscription messages they receive and extract relevant information such as billing policies and periods.

[0100] The terminal determines the billing method based on its settings: The IoT terminal determines whether it is willing to accept the aggregated billing method notified by the base station based on the preset policy and the user's settings.

[0101] Terminal generates billing decision result: Based on the judgment, the terminal generates a billing decision result, namely whether to accept aggregate billing. This result is usually a Boolean value, which represents logical true or false, i.e., accept or not accept.

[0102] In some embodiments, after receiving the results feedback from all terminals, the access point determines the list of terminals that accept aggregated billing and the list of terminals that do not accept aggregated billing from the results, and sends the list to CHF in BOSS through the base station. This process is designed with the following steps.

[0103] Access point receives terminal feedback: The access point receives billing decision feedback from all connected IoT terminals, including information on whether the terminal accepts aggregate billing.

[0104] Access point integrates terminal feedback: The access point integrates feedback from all terminals and compiles this feedback into a list of whether the terminal accepts aggregated billing.

[0105] Access points determine the acceptance and non-acceptance lists: Based on the integrated terminal feedback list, access points determine which terminals are willing to accept aggregated billing and which are not.

[0106] Access point generates terminal list report: Based on the determined acceptance and rejection list, the access point generates a report containing the identification information of these terminals and the corresponding billing decisions. The identification information here is the same as the identification information mentioned above, and will not be repeated here.

[0107] Access points send terminal list reports to base stations: Access points send the generated terminal list reports, which include lists of terminals that accept aggregated billing and those that do not, to the IoT base stations.

[0108] In some embodiments, the access point analyzes the historical communication resource usage of terminals accepting aggregated billing to determine the expected communication resource usage of these terminals per unit time period, which typically involves the following specific processes:

[0109] Data collection and recording: The access point needs to collect and record the usage of communication resources from the connected terminals, which may include communication metrics such as data transmission volume, call duration, and network connection duration.

[0110] Data aggregation and analysis: The access point aggregates and analyzes the collected communication resource usage data. This may involve grouping data by time period (such as hour, day, week) and calculating average usage, peak usage, etc.

[0111] Historical trend analysis: By analyzing historical data, access points can identify trends and patterns in communication resource usage, which can help predict resource demand during specific time periods, such as peak or off-peak hours.

[0112] Terminal analysis: For each terminal performing aggregated billing, the access point may analyze its historical communication resource usage separately to better understand its individual characteristics.

[0113] Communication pattern recognition: Access points may identify different types of communication patterns, such as data transmission, voice calls, and video streaming, in order to more accurately predict communication resource usage.

[0114] Prediction per unit time: Based on historical trends, terminal analysis, and communication pattern recognition, the access point predicts how many communication resources this group of terminals will use within a unit time. This prediction will serve as the basis for negotiating the price in aggregated billing. The price quantity referred to here can be the resource quantity corresponding to the preset quantity of communication resources in the aforementioned embodiments.

[0115] In some embodiments, the amount of a single CDR is negotiated with the CHF based on the expected communication resource usage. Here, the CDR may be a data packet containing a preset number of communication resources sent by the billing function network element to the access device in a single step in a subsequent step.

[0116] Preparation for anticipated communication resource usage: Based on previous analysis, the access point determines the expected communication resource usage of these terminals per unit time, such as the expected data transmission volume and call duration.

[0117] Correspondence between communication resources and the quantity of CDRs: The access point needs to determine the correspondence between the communication resources and the previously negotiated quantity of CDRs based on the expected usage of communication resources, i.e., how many terminals' communication resources are included in a single billing cycle.

[0118] Negotiating with CHF: The access point will negotiate with CHF regarding the anticipated communication resource usage and the correspondence between communication resources and the approved pricing quantity. This may involve sending a request to CHF explaining the anticipated communication resource situation and proposing a single CDR pricing quantity.

[0119] CHF Assessment and Response: Based on the access point's request, CHF assesses the expected communication resource usage and the recommended single CDR pricing quantity. CHF may consider factors such as network load and resource allocation, and then responds to the access point to determine whether it agrees with the recommended pricing quantity.

[0120] Negotiation results for the pricing quantity: Based on CHF's response, the access point and CHF have reached an agreement on the pricing quantity for a single CDR. If the negotiation fails, the two parties may renegotiate to reach an agreement.

[0121] Through these steps, the access point and CHF jointly determine how many terminal billing data to include in a single aggregated billing, thereby ensuring the reasonable aggregation of billing data to adapt to different communication resource usage and billing strategies.

[0122] In some embodiments, once a terminal performing aggregated billing requests communication resources from the access point for the first time, the access point requests the aggregated billing rate from the CHF. Specifically, this may be the access point receiving a communication resource request from a terminal participating in aggregated billing for the first time.

[0123] Terminal requests communication resources: When a terminal performing aggregate billing initiates a request for the first time, it requests specific communication resources, such as data transmission and call time, to meet its business needs.

[0124] Access point receives terminal request: Access point receives a communication resource request from the terminal, which may be a data packet or a message.

[0125] Access point checks pricing requirements: After receiving a terminal request, the access point checks whether the terminal has already participated in aggregated billing within the current billing cycle. If it is the first request or the billing cycle has ended, the access point needs to process the pricing. This pricing can be the billing strategy described in the previous embodiments, i.e., the billing rules for communication resources, such as the cost per unit of communication resources. Simultaneously, this terminal can be considered a newly added terminal to aggregated billing; therefore, the access point needs to re-initiate pricing with the billing CHF.

[0126] The access point initiates a pricing request to the CHF: Based on the correspondence between the predetermined communication resources and the single CDR pricing quantity, as well as the expected communication resource usage, the access point initiates a pricing request for aggregated billing to the CHF. This pricing request can be the billing request in the aforementioned embodiments.

[0127] CHF handles pricing requests: After receiving a pricing request from an access point, the CHF entity calculates the aggregated billing price according to the negotiated pricing rules. This price will cover the billing data of multiple terminals within the negotiated pricing quantity. Similarly, the billing data here can be the billing strategy in the aforementioned embodiments.

[0128] CHF generates a batch pricing response: After calculating the batch price for aggregate billing, the CHF entity generates a batch pricing response, which contains billing data. This batch pricing response can be the billing response message in the aforementioned embodiments.

[0129] CHF sends a pricing response to the access point: The CHF entity sends the generated pricing response back to the access point as a response to the pricing request.

[0130] Access point receives billing response: Access point receives billing response from CHF, which includes billing data for aggregated billing.

[0131] Through this series of steps, after the terminal requests communication resources, the access point initiates a billing request for aggregated billing to the CHF based on the predicted communication resource usage. The CHF entity processes the request and returns billing data to bill the terminal's communication resource usage.

[0132] In some embodiments, the CHF sends a CDR to the access point based on the negotiated price amount. Specifically, the CDR may be a preset number of communication resources allocated by the CHF to the access device. The access point performs billing for all terminals performing aggregate billing until the resources in the CDR, i.e., the preset number of communication resources, are exhausted, at which point it requests CDR resources from the CHF again.

[0133] The process of billing terminals by the access point includes the following steps.

[0134] Perform aggregated billing: The access point performs aggregated billing operations based on the billing data obtained from CHF and the terminal communication resource usage, and applies this billing data to the corresponding terminal account. The billing data here can be a billing policy. In some scenarios, the user terminals participating in aggregated billing can use the same billing policy for billing.

[0135] Monitoring CDR resource status: While performing aggregate billing, the access point monitors the usage of communication resources in the CDR and tracks the amount of resources used.

[0136] Resource exhaustion detection: Based on the monitoring results, the access point determines whether the resources in the CDR have been exhausted.

[0137] CDR resources not exhausted: If the CDR resources have not been exhausted, the access point will continue to perform aggregate billing operations, applying the remaining communication resources to the terminal account until all resources in the CDR are used.

[0138] CDR resource exhaustion: Once the access point detects that the communication resources in the CDR have been exhausted, it means that the communication resources in the CDR can no longer be used for aggregate billing.

[0139] Requesting CDR resources from CHF: When CDR resources are exhausted, the access point will send another request to CHF to obtain new CDR resources in order to continue performing aggregate billing operations.

[0140] CHF responds to CDR requests: After receiving a CDR resource request from an access point, the CHF entity generates a new CDR resource based on the request and then sends it back to the access point.

[0141] Continued aggregated billing: After receiving new CDR resources, the access point can continue to perform aggregated billing operations, applying these new communication resources to the terminal account.

[0142] Through this series of steps, the access point can continuously bill the terminals performing aggregate billing until the communication resources in the CDR are exhausted. Once the resources are exhausted, the access point will request new CDR resources from the CHF to continue performing aggregate billing operations, thereby ensuring the continuity of billing.

[0143] Furthermore, the preferred aggregated billing process includes the following steps:

[0144] Step 1) The access point analyzes the historical communication resource usage of terminals that accept aggregated billing and records the patterns of communication resource usage for each terminal.

[0145] Step 2) Determine the expected usage of communication resources for this batch of terminals per unit time based on the patterns of communication resource usage across all terminals.

[0146] Step 3) Negotiate the price of a single CDR with the CHF entity based on the expected communication resource usage. The price of this can also be the number of communication resources preset.

[0147] Step 4) Once a terminal performing aggregated billing requests communication resources from the access point for the first time, the access point requests the aggregated billing rate from the CHF. The rate here can be the billing rules for the communication resources.

[0148] Step 5) CHF sends the negotiated price to the access point CDR.

[0149] Step 6) The access point continuously monitors the communication resource requests of each terminal. If the communication resource requested by the terminal matches the historical data, aggregate billing is performed for the terminal until the communication resources in the CDR are exhausted. Then, the access point requests CDR resources from the CHF again. If the communication resource requested by the terminal does not match the historical data, the terminal is excluded from aggregate billing and switched to the regular individual billing mode.

[0150] Through this series of steps, the access point flexibly decides whether a terminal should participate in aggregated billing based on the matching of the terminal's communication resource requests with historical data, thereby improving the accuracy and efficiency of billing. For matching terminals, billing will continue until CDR resources are exhausted, requiring a request for new CDR resources to continue. For mismatched terminals, the conventional individual billing mode will be used.

[0151] This application also provides an aggregation billing device, which corresponds to the aggregation billing method applied to access devices described above. The steps in the above aggregation billing method embodiments are also fully applicable to this device embodiment.

[0152] The device includes:

[0153] The first sending module is used to send a billing request to the billing function network element in response to receiving a communication resource request from any of the multiple user terminals participating in the aggregate billing for the first time.

[0154] The first receiving module is used to receive a billing response message sent by the billing function network element. The billing response message includes a preset number of communication resources and a billing policy. The preset number of communication resources is determined by the access device in consultation with the billing network element based on the historical communication resource usage information of the multiple user terminals participating in the aggregated billing.

[0155] The processing module is used to bill the multiple user terminals participating in aggregated billing based on the billing response message.

[0156] The processing module is further configured to deduct the number of communication resources corresponding to the communication resource request from a preset number of communication resources based on the communication resource request sent by the user terminal participating in the aggregation billing; and to bill the corresponding user terminal based on the number of communication resources deducted and the billing strategy.

[0157] The first sending module is further configured to send aggregated billing subscription messages to multiple user terminals connected to the access device.

[0158] The first receiving module is further configured to receive feedback messages sent by the user terminal; the feedback messages indicate whether the corresponding user terminal agrees or disagrees with aggregate billing.

[0159] The processing module is further configured to verify the communication resource requests initiated by the user terminals participating in the aggregated billing; if there is a user terminal among the user terminals participating in the aggregated billing whose communication resource requests do not match the user terminal's historical communication resource usage information, the user terminal will be billed separately.

[0160] The processing module is also used to monitor the consumption of the communication resources; if the communication resources are exhausted, it requests communication resources from the billing function network element.

[0161] This application embodiment also provides another aggregation billing device, which corresponds to the aggregation billing method in the above-mentioned application billing function network element. The steps in the above-mentioned aggregation billing method embodiment are also fully applicable to this device embodiment.

[0162] The device includes:

[0163] The second receiving module is used to receive the billing request issued by the access device in response to the first receipt of a communication resource request sent by any of the multiple user terminals participating in the aggregate billing.

[0164] The second sending module is used to send a billing response message to the access device; the billing response message includes a preset number of communication resources and a billing policy, the preset number of communication resources being determined by the access device in consultation with the billing network element based on the historical communication resource usage information of the multiple user terminals participating in aggregated billing.

[0165] In practical applications, the aforementioned first transmitting module, first receiving module, processing module, second transmitting module, and second receiving module can be implemented by the processor in the aggregated billing device. Of course, the processor needs to run the computer program in the memory to implement its functions.

[0166] It should be noted that the apparatus provided in the above embodiments is only illustrated by the division of the above program modules. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the apparatus can be divided into different program modules to complete all or part of the processing described above. In addition, the apparatus and method embodiments provided in the above embodiments belong to the same concept, and will not be described again here.

[0167] Based on the hardware implementation of the above program modules, and in order to implement the method of the embodiments of this application, the embodiments of this application also provide an electronic device. Figure 3 This is a schematic diagram of the hardware composition structure of an electronic device provided in an embodiment of this application, such as... Figure 3 As shown, the electronic device includes:

[0168] The communication interface 301 enables information exchange with other devices, such as network devices.

[0169] The processor 302 is connected to the communication interface 301 to enable information interaction with other devices and to execute the methods provided by one or more of the above-mentioned technical solutions when running a computer program. The computer program is stored in the memory 303.

[0170] Of course, in practical applications, the various components in an electronic device are coupled together through a bus system 304. It can be understood that the bus system 304 is used to realize the connection and communication between these components. In addition to the data bus, the bus system also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, in... Figure 3 The general designated all buses as Bus System 304.

[0171] The memory 303 in this embodiment is used to store various types of data to support the operation of the computer device. Examples of such data include any computer program used to operate on the electronic device.

[0172] It is understood that memory 303 can be volatile memory or non-volatile memory, or both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), ferromagnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); magnetic surface memory can be disk storage or magnetic tape storage. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memories described in the embodiments of this application are intended to include, but are not limited to, these and any other suitable types of memories.

[0173] The methods disclosed in the embodiments of this application can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor may be a general-purpose processor, a DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The processor can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. A general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, which is located in memory. The processor reads the program from the memory and, in conjunction with its hardware, completes the steps of the aforementioned method.

[0174] Optionally, when the processor 302 executes the program, it implements the corresponding processes implemented by the computer device in the various methods of the embodiments of this application. For the sake of brevity, these will not be described in detail here.

[0175] In an exemplary embodiment, this application also provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium, such as a first memory storing a computer program, which can be executed by a processor of a computer device to complete the steps described in the aforementioned method. The computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM.

[0176] In the several embodiments provided in this application, it should be understood that the disclosed apparatus, computer devices, and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components may be combined, or integrated into another system, or some features may be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed may be through some interfaces, and the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

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

[0178] In addition, each functional unit in the various embodiments of this application can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be implemented in hardware or in the form of hardware plus software functional units.

[0179] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media that can store program code, such as mobile storage devices, ROM, RAM, magnetic disks, or optical disks.

[0180] Alternatively, if the integrated units described above are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROM, RAM, magnetic disks, or optical disks.

[0181] In an exemplary embodiment, this application also provides a computer program product, including a computer program that can be executed by a processor 302 of an electronic device to perform the steps described in the method applied to the access device in this application embodiment.

[0182] In an exemplary embodiment, this application also provides a computer program product, including a computer program that can be executed by a processor 302 of an electronic device to complete the steps described in the method applied to a billing function network element in this application embodiment.

[0183] It should be noted that terms such as "first" and "second" are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0184] Furthermore, the technical solutions described in the embodiments of this application can be combined arbitrarily without conflict.

[0185] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. An aggregated billing method, applied to access equipment, characterized in that, The method includes: In response to the first receipt of a communication resource request from any of the multiple user terminals participating in aggregated billing, a billing request is sent to the billing function network element; The access device receives a billing response message from the billing function network element. The billing response message includes a preset number of communication resources and a billing policy. The preset number of communication resources is determined by the access device in consultation with the billing function network element based on the historical communication resource usage information of the multiple user terminals participating in the aggregated billing. Based on the billing response message, billing is performed on the multiple user terminals participating in aggregate billing; Before billing the multiple user terminals participating in aggregated billing based on the billing response message, the method further includes: verifying the communication resource requests initiated by the multiple user terminals participating in aggregated billing based on their historical communication resource usage information; if there is a user terminal among the multiple user terminals participating in aggregated billing whose communication resource request does not match its historical communication resource usage information, billing the mismatched user terminal separately.

2. The method according to claim 1, characterized in that, The billing strategy represents the cost per unit quantity of communication resources; the billing of the multiple user terminals participating in aggregate billing based on the billing response message includes: Based on the communication resource request sent by the user terminal participating in the aggregation billing, the number of communication resources corresponding to the communication resource request is deducted from the preset number of communication resources; Billing is performed on the corresponding user terminal based on the amount of communication resources deducted and the billing strategy.

3. The method according to claim 1, characterized in that, Before sending the billing request to the billing function network element, the method further includes: Send aggregated billing subscription messages to multiple user terminals connected to the access device; Receive feedback messages sent by the user terminal; the feedback messages indicate whether the corresponding user terminal agrees or disagrees with aggregate billing.

4. The method according to claim 1, characterized in that, After billing the multiple user terminals participating in aggregated billing, the method further includes: Monitor the consumption of the communication resources; If the communication resources are exhausted, request communication resources from the billing function network element.

5. An aggregated billing method, applied to a billing function network element, characterized in that, The method includes: The receiving access device responds to the first receipt of a communication resource request sent by any of the multiple user terminals participating in the aggregation billing; A billing response message is sent to the access device. The billing response message includes a preset number of communication resources and a billing policy. The preset number of communication resources is determined by the access device in consultation with the billing function network element based on the historical communication resource usage information of the multiple user terminals participating in the aggregated billing. The billing response message is used to instruct the access device to bill the multiple user terminals participating in the aggregated billing. Before billing the multiple user terminals participating in the aggregated billing, the following steps are taken: based on the historical communication resource usage information of the multiple user terminals participating in the aggregated billing, the communication resource requests initiated by the multiple user terminals participating in the aggregated billing are checked; if there is a user terminal among the multiple user terminals participating in the aggregated billing whose communication resource request does not match the historical communication resource usage information, the user terminal with the mismatch is billed separately.

6. An electronic device, characterized in that, include: A processor and a memory for storing a computer program capable of running on the processor, wherein the processor, when running the computer program, performs the steps of the method according to any one of claims 1 to 4 or 5.

7. A computer storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method described in any one of claims 1 to 4 or 5.

8. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method described in any one of claims 1 to 4.

9. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the method of claim 5.

Images