Charging system and method

Abstract

The application provides a charging system and method, which comprises a user data analysis module, a GGSN, and an online charging module. The user data analysis module is used for obtaining the corresponding user level according to the historical call data, the historical service average resource consumption and the current residual resource amount of each user, and configuring the upgrade protocol request of BOSS according to the user level. The GGSN is used for disconnecting the connection with the online charging module, keeping the connection with the offline charging module, and buffering the resource amount used by the user to the buffer module or sending the credit control request corresponding to the user to the offline charging module for charging processing when the upgrade protocol request is received. The online charging module is used for obtaining the charging processing result corresponding to each user according to the resource amount in the buffer module and the charging processing result in the offline charging module when the upgrade of BOSS is completed. The application realizes the cooperative charging of GGSN and BOSS, so as to reduce the waste of computing resource and improve the upgrade efficiency.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of communication technology, in particular to a charging system and method. BACKGROUND

[0002] When a Business Operation Support System (BOSS) is upgraded, offline charging needs to be used for a short time to record the call records during this period. Therefore, the BOSS sets an online charging system and an offline charging system at the same time. A Gateway General Packet Radio Service Support Node (GGSN) is connected with the two charging systems. When the BOSS is in a normal state, the online charging system is used for charging. When the BOSS is in an upgrade state, the GGSN cannot communicate with the online charging system, and then the offline charging system is used for charging.

[0003] When the system is upgraded, users will still generate charging call records. At this time, in order to ensure the consistency of the data of each user, the offline charging call record data of the users during the upgrade period must be recorded. At present, the charging call records during the upgrade period are recorded by the offline charging system. The GGSN often only plays a role of receiving and sending requests, that is, the charging operation performed during the system upgrade is still executed by the BOSS end. This will cause the BOSS end, which is not often used, to need to be pre-allocated with sufficient computing power, and the GGSN with sufficient computing power only plays a role of sending instructions, resulting in waste of computing power resources and low upgrade efficiency.

[0004] With the continuous development of technology, communication between users is also increasing, and the demand for updating communication services is also increasing frequently, which in turn causes the upgrade speed of the BOSS end to be faster and faster. Therefore, in the module upgrade scenario of the communication service provider, how to charge the data of the users during the upgrade period while reducing the waste of computing power resources and improving the upgrade efficiency has become a problem to be solved in the industry. SUMMARY

[0005] The present application provides a charging system and method to solve the defect that the charging operation performed during the upgrade period is still executed by the BOSS end in the prior art, resulting in waste of computing power resources and low upgrade efficiency, and to achieve charging of the data of the users during the upgrade period while reducing the waste of computing power resources and improving the upgrade efficiency.

[0006] The present application provides a charging system, comprising: a user data analysis module, a Gateway General Packet Radio Service Support Node (GGSN), and a Business Operation Support System (BOSS).

[0007] The gateway general packet radio service support node includes a caching module, and the service operation support system includes an offline billing module and an online billing module;

[0008] The user data analysis module is used to obtain the user level of each user based on the user's historical call detail records (CDRs) and historical average resource consumption, as well as the user's current remaining resources, and to configure the upgrade protocol request of the business operation support system according to the user's user level; the historical CDRs and historical average resource consumption are respectively the CDRs and average resource consumption generated by each user in the historical time period that matches the current upgrade time period.

[0009] The gateway general packet radio service support node is used to disconnect from the online billing module and maintain the connection with the offline billing module when it receives the upgrade protocol request sent by the business operation support system. It also caches the amount of resources used by each user in the current upgrade time period to the cache module according to the user level of each user, or sends the credit control request corresponding to each user to the offline billing module.

[0010] The offline billing module is used to perform billing processing based on the credit control request during the current upgrade time period;

[0011] The online billing module is used to obtain the billing processing result corresponding to each user based on the resource quantity in the cache module and the billing processing result in the offline billing module when it is determined that the upgrade of the business operation support system has been completed.

[0012] According to a billing system provided by the present invention, the user data analysis module is further used for:

[0013] If any user's historical call detail record (CDR) data is less than or equal to the CDR data threshold, the user level of that user is determined to be the first level.

[0014] If the historical call detail record (CDR) data of any user is greater than the CDR data threshold, the current remaining resource amount of any user is compared with a preset multiple of the historical average resource consumption of any user.

[0015] If it is known that the current remaining resources of any user are greater than a preset multiple of the historical average resource consumption, the user level of any user is determined to be the second level.

[0016] If it is known that the current remaining resources of any user are less than or equal to a preset multiple of the historical average resource consumption, the user level of any user is determined to be the third level.

[0017] According to a billing system provided by the present invention, the gateway general packet radio service support node is further configured to:

[0018] Upon receiving a Packet Data Protocol Context Creation Request from any user, if it is determined that the user level of any user is Level 1, a First Context Creation Response is sent to any user so that the user can use the service based on the First Context Creation Response.

[0019] The resource amount generated by any user creating a response based on the first context for business use during the current upgrade time period is cached in the cache module.

[0020] According to a billing system provided by the present invention, the gateway general packet radio service support node is further configured to:

[0021] Upon receiving a Packet Data Protocol Context Creation Request from any user, if it is determined that the user's level is Level 2, then the credit control request corresponding to the user is sent to the offline billing module.

[0022] Receive a credit control response message returned by the offline billing module; the credit control response message includes preset resource information allocated by the offline billing module to any user according to the credit control request;

[0023] A second context creation response is sent to any user based on the preset resource information, so that any user can use the service based on the second context creation response;

[0024] If it is determined that the preset resource information has been used up, and if it is determined that the service of any user has not been used up, then the process returns to the step of sending the credit control request corresponding to any user to the offline billing module, until the service of any user is used up.

[0025] According to a billing system provided by the present invention, the gateway general packet radio service support node is further configured to:

[0026] Upon receiving a Packet Data Protocol Context Creation Request from any user, if it is determined that the user's level is Level 3, then the credit control request corresponding to the user is sent to the offline billing module.

[0027] Receive a credit control response message returned by the offline billing module; the credit control response message includes preset resource information allocated by the offline billing module to any user according to the credit control request;

[0028] If it is determined that the current remaining resources of any user are greater than the resource threshold, a second context creation response is sent to any user according to the preset resource information, so that any user can use the service according to the second context creation response;

[0029] If it is determined that the preset resource information has been used up, the amount of resources corresponding to the preset resource information is deducted from the current remaining resource amount to obtain an updated current remaining resource amount;

[0030] If it is determined that the service of any user has not ended and the updated current remaining resource amount is greater than the resource amount threshold, then return to the step of sending the credit control request corresponding to any user to the offline billing module, until the service of any user ends and / or the updated current remaining resource amount is less than or equal to the resource amount threshold.

[0031] According to a billing system provided by the present invention, the system further includes an upgrade time prediction module, used for:

[0032] Obtain the target upgrade duration corresponding to the business operation support system;

[0033] Based on the target upgrade duration, the historical call detail records (CDRs) generated by all users in the historical time periods that match each of the alternative upgrade periods are statistically analyzed to obtain the total historical CDR data corresponding to each of the alternative upgrade periods.

[0034] Based on the total historical call detail records, the candidate upgrade periods are sorted.

[0035] Based on the sorting results, the current upgrade time period is obtained from multiple candidate upgrade time periods.

[0036] According to a billing system provided by the present invention, the upgrade time prediction module is further configured to:

[0037] Based on the type of upgrade content corresponding to the business operation support system, historical call detail records (CDRs) generated by each user within the historical time period matching each of the alternative upgrade periods are obtained from the historical call data, historical traffic data, and historical SMS data generated by each user within the historical time period matching each of the alternative upgrade periods.

[0038] The present invention also provides a billing method, the method being applied to a billing system as described in any of the preceding claims, the method comprising:

[0039] Using the user data analysis module, based on each user's historical call detail records (CDRs) and historical average resource consumption, as well as the current remaining resources of each user, the user level corresponding to each user is obtained, and the upgrade protocol request of the business operation support system is configured according to the user level of each user; the historical CDRs and historical average resource consumption are respectively the CDRs and average resource consumption generated by each user in the historical time period matching the current upgrade time period.

[0040] Upon receiving the upgrade protocol request sent by the business operation support system, the gateway general packet radio service support node disconnects the connection with the online billing module of the business operation support system while maintaining the connection with the offline billing module of the business operation support system. Based on the user level of each user, the amount of resources used by each user during the current upgrade time period is cached in the cache module of the gateway general packet radio service support node, or the credit control request corresponding to each user is sent to the offline billing module.

[0041] Using the offline billing module, billing is performed based on the credit control request during the current upgrade period;

[0042] Upon determining that the upgrade of the business operation support system is complete, the online billing module is used to obtain the billing processing results corresponding to each user based on the resource quantity in the cache module and the billing processing results in the offline billing module.

[0043] The present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the billing method described above.

[0044] The present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the billing method as described above.

[0045] The present invention also provides a computer program product, including a computer program that, when executed by a processor, implements the billing method as described above.

[0046] The billing system and method provided by this invention, through a user data analysis module, adaptively classifies users into more refined user levels based on their historical call detail records, historical average resource consumption, and current remaining resources. By classifying users into different levels, the offline communication billing functions that the BOSS (Browser OSS) is required to perform are moved forward to the GGSN (Generic Gateway SN) for completion. This enables billing through collaboration between the GGSN module and the BOSS, effectively reducing unnecessary waste of computing resources in the offline billing system during BOSS upgrades, improving resource utilization in the GGSN, and reducing the overhead and operating costs associated with wasting computing resources. Ultimately, this allows for effective billing of user data during upgrades while minimizing the waste of computing resources and improving upgrade efficiency. Attached Figure Description

[0047] To more clearly illustrate the technical solutions in this invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0048] Figure 1 This is a schematic diagram of the billing system provided by the present invention.

[0049] Figure 2 This is a schematic diagram of the upgrade preparation process provided by the present invention.

[0050] Figure 3 This is a flowchart illustrating the user level classification process provided by the present invention.

[0051] Figure 4 This is a connection topology diagram between the user terminal, GGSN, and BOSS provided by the present invention.

[0052] Figure 5 This is a schematic diagram of the collaborative billing process between GGSN and BOSS provided by the present invention.

[0053] Figure 6 This is a schematic diagram of the upgrade time period prediction process provided by the present invention.

[0054] Figure 7 This is a flowchart illustrating the billing method provided by the present invention.

[0055] Figure 8 This is a schematic diagram of the structure of the electronic device provided by the present invention. Detailed Implementation

[0056] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.

[0057] The GGSN primarily functions as a gateway, connecting to various data networks such as Integrated Services Digital Network (ISDN), Packet Switched Public Data Network (PSPDN), and Local Area Network (LAN). The GGSN also has billing information collection capabilities, enabling it to gather billing information (G_CDR) related to external data network and General Packet Radio Service (GPRS) network resources used by each mobile station (MS).

[0058] BOSS refers to the Business Operations Support System. Typically, BOSS consists of four parts: Billing and Settlement System, Sales and Accounting System, Customer Service System, and Decision Support System. From a business perspective, BOSS is a framework that houses the business systems, Customer Relationship Management (CRM) system, and billing system, enabling vertical and horizontal management within a unified framework.

[0059] Signaling refers to control commands in a communication system. In GGSN and BOSS, signaling is commonly used to transmit control signals. Signaling plays a crucial role in communication systems, serving as a vital means of ensuring communication quality and reliability. Through signaling, communication systems can manage and control communication connections, including establishing, maintaining, and releasing connections, as well as transmitting, managing, and controlling communication data. Furthermore, signaling can also be used for network management and maintenance, including fault diagnosis, performance monitoring, and security management.

[0060] Offline billing refers to a billing mechanism that collects billing information after the session has ended, ensuring that the billing information does not affect service delivery in real time. In the Internet Protocol Multimedia Subsystem (IPS) network, offline billing information from various billing network elements is transmitted to the Charging Collection Function (CCF) via the Radio Frequency Interface (RF). The CCF preprocesses the information to generate a Charging Data Record (CDR), which is then transmitted from the Billing Interface (Bi) to the operator-designated billing center.

[0061] Online billing refers to the system periodically interacting with the user's account during the session to monitor the user's account balance information in real time, so as to prevent the user from continuing to use paid services when the account balance is insufficient.

[0062] Because online billing has many advantages over offline billing, most operator services have already transitioned to online billing. However, when the BOSS (Business OSS) is being upgraded, offline billing is needed for a short period to record call details. Therefore, the BOSS is configured with both online and offline billing systems. The GGSN (Gateway Gate Service) establishes connections with both systems. When the BOSS is in normal operation, online billing is used for billing. When the BOSS is undergoing an upgrade, the GGSN cannot communicate with the online billing system, and billing is switched to the offline billing system.

[0063] Because the previously developed system dealt with relatively simple business scenarios and the BOSS was not upgraded frequently, the starting point of the processing flow was to minimize the involvement of the GGSN in the specific details of billing. This is because the GGSN is a data transmission device, which is often not part of the business payment department in the architecture, and the operations involved are more at the lower level of data transmission. Therefore, the existing processing flow is as follows:

[0064] Step 1: The user sends a Packet Data Protocol (PDP) context creation request to the GGSN;

[0065] Step 2: After receiving the PDP context creation request, the GGSN starts the billing process;

[0066] Step 3: GGSN sends a billing request to the transceiver module of the online billing system in BOSS. This billing request carries a Credit Control Request (CCR) message to establish a connection.

[0067] Step 4: The sending and receiving module of the online billing system in BOSS sends the billing request to the business processing module of the online billing system in BOSS and waits for the response from the business processing module.

[0068] Step 5: If a response is received, billing will be performed according to the normal procedure; otherwise, proceed to step 6.

[0069] Step 6: Send a response message to GGSN indicating that the online billing system is not working;

[0070] Step 7: GGSN sends a CCR message to the offline billing system in BOSS, and the offline billing system completes the billing.

[0071] With the development of operator services and the continuous improvement of refined customer services, the types of related services are increasing, leading to more frequent adjustments, upgrades, and promotions. When upgrade promotions occur, it is usually necessary to upgrade the relevant system functions, resulting in increasingly frequent upgrades to the related BOSS (Business Controller). As can be seen from the billing process above, users will still generate billing records during system upgrades. To ensure the consistency of data across users, it is necessary to record the offline billing record data of users during the upgrade period. Currently, due to various reasons such as ensuring network security and improving business performance, it is necessary to circumvent and protect the GGSN in existing technologies. This puts increasing pressure on the BOSS. For example, the signaling interaction increases during upgrades, and the BOSS's limited business processing capacity can easily create bottlenecks. Also, billing call details during upgrades are recorded by the offline billing system, and the GGSN often only serves to receive and send requests. That is, billing operations performed during system upgrades are still executed by the BOSS. This requires the offline billing system in the BOSS, which is not frequently used, to pre-allocate sufficient computing power, increasing expenses and expanding operating costs. Meanwhile, the GGSN, with its sufficient computing power, only serves to send instructions, resulting in a waste of computing resources and low upgrade efficiency.

[0072] To address the technical problems existing in the prior art, this embodiment provides a billing system that performs billing through collaboration between GGSN and BOSS. By reasonably selecting the current upgrade time period of BOSS and performing BOSS upgrades within the current upgrade time period, all upgrade functions originally placed in BOSS are transferred to GGSN. That is, billing is performed collaboratively by GGSN and BOSS, which effectively improves the rational utilization of computing resources while improving the efficiency and stability of BOSS upgrades.

[0073] Figure 1 This is a schematic diagram of the billing system provided by the present invention, as shown below. Figure 1As shown, the billing system 100 includes a user data analysis module 130, a gateway general packet radio service support node 110, and a service operation support system 120; the gateway general packet radio service support node 110 includes a caching module, and the service operation support system 120 includes an offline billing module and an online billing module.

[0074] Among them, the gateway general packet radio service support node 110 is connected to the user data analysis module 130 and the business operation support system 120 for communication.

[0075] The user data analysis module can statistically analyze the historical call detail records (CDRs) of each user within the selected current upgrade time period to categorize them.

[0076] The GGSN includes a caching module. The GGSN can receive upgrade assistance requests (or upgrade protocol requests) from the BOSS, and after receiving the request, it sends a response reply to the BOSS, then disconnects from the online billing module in the BOSS, only maintaining the connection with the offline billing module in the BOSS, and sets the BOSS upgrade flag to indicate that the BOSS module is performing an upgrade operation.

[0077] Meanwhile, GGSN can determine whether to process the data generated by users during the upgrade process in its local cache module or forward it to the offline billing module in BOSS based on the user level classification in the user data analysis module. This allows for more refined and targeted processing of users at different levels. Furthermore, some functions that the offline billing module in BOSS needs to perform can be moved to GGSN to reduce the computing power requirements of the offline billing module in BOSS and lower the overall operating costs.

[0078] BOSS includes online and offline billing modules. Before performing an upgrade, BOSS can send an upgrade assistance request to GGSN and, upon receiving a response from GGSN, apply different billing methods to users of different tiers.

[0079] The user data analysis module is used to obtain the user level of each user based on the user's historical call detail record (CDR) data, historical average resource consumption, and the current remaining resources of each user, and to configure the upgrade protocol request of the business operation support system according to the user level of each user; the historical CDR data and the historical average resource consumption are respectively the CDR data and average resource consumption of each user in the historical time period that matches the current upgrade time period.

[0080] Optionally, the user data analysis module may perform the following steps to classify users:

[0081] First, obtain the current upgrade time period of the BOSS in the current cycle. Here, the current upgrade time period can be obtained based on prediction model prediction or through logical calculation. For example, for prediction model prediction, it can be obtained by collecting historical call detail records (CDRs) or network parameters that can monitor the activity of user-generated billing data within the sample upgrade duration of a large number of candidate upgrade time periods, as well as sample upgrade time periods. Then, using historical CDRs or network parameters as samples and sample upgrade time periods as labels, the neural network model is trained to obtain the prediction model. Subsequently, the historical CDRs or network parameters within the target upgrade duration of each candidate upgrade time period are input into the prediction model to predict the current upgrade time period. For logical calculation, it can be obtained by performing logical judgment on the historical CDRs or network parameters within the target upgrade duration of each candidate upgrade time period, and selecting a suitable upgrade time period as the current upgrade time period based on the logical judgment.

[0082] Subsequently, within several historical periods preceding the current period, time intervals belonging to the same time range as the current upgrade time period are obtained as historical time intervals matching the current upgrade time period. The average number of call detail records (CDRs) for each user and the average resource consumption per service within these historical time intervals are then calculated to obtain the historical CDR data and historical average resource consumption for each user. The historical CDR data includes, but is not limited to, at least one of historical call data, historical traffic data, and historical SMS data, which can be adaptively determined based on the type of upgrade content corresponding to the BOSS. The period and time interval can be defined as dividing each day into a period, and different time intervals within each day into different time intervals. Correspondingly, for historical information statistics, the CDR data and average resource consumption for each user within the same time interval as the current upgrade time period over N historical days can be calculated. For example, assuming N is 30 days and the current upgrade time period is from 8:00 AM to 8:05 AM, the historical CDR data and average resource consumption for each user within the same time range over the past 30 days can be calculated to obtain the historical CDR data and historical average resource consumption for each user.

[0083] Furthermore, obtain the remaining resource amount of each user in the current period, and use it as the current remaining resource amount.

[0084] Subsequently, by combining each user's historical call detail record (CDR) data, historical average resource consumption, and current remaining resources, users are categorized into different levels to obtain their corresponding user levels. This level categorization can be based on a pre-trained classification model or on logical judgment. For example, for classification modeling, a large amount of sample CDR data, sample average resource consumption, sample remaining resources, and user level labels generated by users within historical time periods matching the sample upgrade time period can be collected. Then, using the sample CDR data, sample average resource consumption, and sample remaining resources as samples, and the user level labels as labels, a neural network model is trained to obtain the classification model. Subsequently, the CDR data, average resource consumption, and current remaining resources generated by each user within historical time periods matching the current upgrade time period are input into the classification model to obtain the corresponding user level. For logical judgment, at least one logical judgment can be performed on each user based on the CDR data, average resource consumption, and current remaining resources generated within historical time periods matching the current upgrade time period to obtain the corresponding user level.

[0085] After obtaining the user level of each user, the upgrade protocol request of BOSS can be configured based on the user level. Then, GGSN can determine the user type according to the upgrade protocol request, and then determine whether to forward the data generated by the user during the upgrade to the offline billing module in BOSS for processing. This allows for more refined and targeted processing for users of different levels. In this way, some functions that the offline billing module in BOSS needs to perform are moved to GGSN to reduce the computing power requirements of the offline billing module in BOSS and reduce the overall operating cost.

[0086] Here, the upgrade protocol request can be configured in the following ways: different lists can be configured based on each user's user level and current resource information, and upgrade information can be configured based on the current upgrade time period.

[0087] Figure 2 This is a schematic diagram of the upgrade preparation process provided by the present invention; as shown below. Figure 2As shown, users are categorized into three levels based on their frequency of occurrence and remaining resources: occasional users (Level 1), non-occasional users with sufficient resources (Level 2), and non-occasional users with insufficient resources (Level 3). Since the system selects the least active time for upgrades, even looking back N days, the vast majority of users fall into the occasional user category during the short upgrade period. Subsequent processing will focus on non-occasional users. Therefore, a first list can be set in the BOSS upgrade protocol request, including the user identifiers (IDs) and current remaining resources for Level 2 users, and a second list can be set in the BOSS upgrade protocol request, including the user IDs and current remaining resources for Level 3 users. Furthermore, the upgrade start and end times can be configured based on the current upgrade time period. This allows BOSS to send an upgrade protocol request to GGSN containing the first and second lists, as well as the upgrade start and end times, when an upgrade is needed. This facilitates GGSN's identification of user levels based on the list information and determines the current upgrade time period required by BOSS based on the upgrade information.

[0088] The gateway general packet radio service support node is used to disconnect from the online billing module and maintain the connection with the offline billing module when it receives the upgrade protocol request sent by the business operation support system. It also caches the amount of resources used by each user during the current upgrade time period in the cache module according to the user level of each user, or sends the credit control request corresponding to each user to the offline billing module.

[0089] The offline billing module is used to perform billing processing based on the credit control request during the current upgrade time period.

[0090] like Figure 2 As shown, after receiving the upgrade protocol request, GGSN sends a response reply to BOSS, disconnects the connection with the online billing module during the current upgrade time period, retains the connection with the offline billing module, and sets the upgrade flag of BOSS to indicate that BOSS is performing an upgrade operation.

[0091] Furthermore, based on the first and second list information in the upgrade protocol request, GGSN determines the user level corresponding to each user. Based on different user levels, it caches the amount of resources used by each user during the current upgrade period in the cache module for billing processing on the local cache module, or forwards the credit control request corresponding to each user to the offline billing module for billing processing.

[0092] For example, if GGSN determines that a user is an occasional user based on the user level, it will cache the amount of resources used by that user during the current upgrade period in GGSN's caching module; if GGSN determines that a user is a non-occasional user based on the user level, it will transfer the corresponding credit control request to the offline billing module for billing processing.

[0093] The online billing module is used to obtain the billing processing result corresponding to each user based on the resource quantity in the cache module and the billing processing result in the offline billing module when it is determined that the upgrade of the business operation support system has been completed.

[0094] Optionally, after determining that the BOSS upgrade is complete, the online billing module connects with the GGSN and the offline billing module to obtain the billing processing results from the offline billing module, such as the call detail records (CDRs) used by non-occasional users during the current upgrade period, and obtains the amount of resources used by occasional users during the current upgrade period from the GGSN's cache module. The above information is then aggregated to complete the billing operation for all users, thereby obtaining the billing processing results for each user.

[0095] In summary, unlike existing technologies, the system provided in this embodiment does not focus on the switching between online and offline billing modules during upgrades. Instead, it analyzes historical call detail record (CDR) data based on the current upgrade period to classify users into different levels. During system upgrades, the GGSN is placed in the upgrade position, disconnected from the online billing module, but connected to the offline billing module. The level of received user data is determined; if the user is an intermittent user, the data is cached in the GGSN module; if the user is a non-intermittent user, the data is transferred to the offline billing module for processing. After the system upgrade is complete, the data cached in the GGSN is... The results of data processing in the data and offline billing modules are merged in the online billing module. This allows for system upgrades through reasonable upgrade timing and computing power allocation. While performing the same service, this reduces signaling interactions and improves the collaborative processing capabilities between various communication billing modules during system upgrades. It also enables the effective allocation of computing power to the GGSN module with sufficient computing power, ensuring better resource distribution, reducing waste, improving upgrade efficiency, and ultimately enhancing the overall network processing capacity. This has significant implications for improving operator profitability and yields substantial economic benefits.

[0096] The system provided in this embodiment, through a user data analysis module, adaptively classifies users into more refined user levels based on their historical call detail records, historical average resource consumption, and current remaining resources. By classifying users into different levels, some offline communication billing functions that the BOSS (Business OSS) is required to perform are moved forward to the GGSN (Google Generic Service SN). This enables billing through collaboration between the GGSN module and the BOSS, effectively reducing unnecessary waste of computing resources in the offline billing system during BOSS upgrades, improving resource utilization in the GGSN, and reducing the overhead and operating costs associated with wasting computing resources. Ultimately, this allows for effective billing of user data during upgrades while minimizing the waste of computing resources and improving upgrade efficiency.

[0097] In some embodiments, the user data analysis module is further configured to:

[0098] If any user's historical call detail record (CDR) data is less than or equal to the CDR data threshold, the user level of that user is determined to be the first level.

[0099] If the historical call detail record (CDR) data of any user is greater than the CDR data threshold, the current remaining resource amount of any user is compared with a preset multiple of the historical average resource consumption of any user.

[0100] If it is known that the current remaining resources of any user are greater than a preset multiple of the historical average resource consumption, the user level of any user is determined to be the second level.

[0101] If it is known that the current remaining resources of any user are less than or equal to a preset multiple of the historical average resource consumption, the user level of any user is determined to be the third level.

[0102] Figure 3 This is a flowchart illustrating the user level classification process provided by the present invention; optionally, the user data analysis stage is executed by the user data analysis module, and the specific functional execution flowchart is as follows. Figure 3 As shown, the detailed steps are steps 310 to 320.

[0103] Step 310: Based on the current upgrade time period, obtain time periods belonging to the same time interval as the current upgrade time period from multiple historical periods prior to the current period as historical time periods to match the current upgrade time period. Count the number of call detail records (CDRs) initiated by each user within this historical time period to obtain historical CDR data. For example, to count CDR data for the most recent N days within this historical time period, assuming N is 30 days and the current upgrade time period is set to 8:00 AM to 8:05 AM, then count the number of CDRs initiated by each user within this historical time period of 8:00 AM to 8:05 AM over the past 30 days to obtain the historical CDR data for each user.

[0104] Step 320: Based on historical call detail record (CDR) data, users are divided into three levels: Level 1, historical CDR data is less than or equal to the CDR data threshold; Level 2, historical CDR data is greater than the CDR data threshold, and current remaining resources are sufficient; Level 3, historical CDR data is greater than the CDR data threshold, and current remaining resources are insufficient. Specifically, within the historical period, a time interval belonging to the same time interval as the current upgrade time period is obtained as the historical time interval. If the total number of CDRs generated by any user within this historical time interval is less than the CDR data threshold, then the user is determined to be in Level 1, i.e., the type is occasional; and the remaining users are classified as non-occasional. Further, the average resource consumption per service for each non-occasional user within this historical time interval and the user's current remaining resources are calculated. If the current remaining resources > m × the average resource consumption per service, then the user is determined to be in Level 2, i.e., the user is a non-occasional user with sufficient remaining resources; otherwise, the user is determined to be in Level 3, i.e., the user is a non-occasional user with insufficient remaining resources. The preset multiple m can be configured according to actual needs, such as m=2, etc. This embodiment does not make a specific limitation on this.

[0105] In some embodiments, historical call detail record (CDR) data includes, but is not limited to, at least one of historical call data, historical data traffic, and historical SMS data. That is, historical CDR data can be historical call data, historical data traffic, or historical SMS data, or it can be a weighted fusion result of historical call data, historical data traffic, and historical SMS data. Specifically, it can be adaptively selected according to the type of upgrade content corresponding to the BOSS in order to improve the accuracy of user classification.

[0106] For example, assuming the current upgrade period is set to 8:00 AM to 8:10 AM, and the upgrade targets call items in the call detail records (CDRs), we can statistically analyze the call activity of each user during this period over the past 30 days and categorize users accordingly. Setting a CDR data threshold of 2, if user A has only one historical call during this upgrade period, they belong to the first level, i.e., an occasional user. If user B has two historical calls during this upgrade period, with an average call duration of one minute per call and a remaining call duration of 50 minutes (greater than 2 × the average resource consumption per call), they belong to the second level. If user C has two historical calls during this upgrade period, with an average call duration of two minutes per call and a remaining call duration of 2 minutes (less than or equal to 2 × the average resource consumption per call), they belong to the third level.

[0107] The system provided in this embodiment analyzes the historical call detail records, historical average resource consumption, and current remaining resources of each user within the selected current upgrade time period. This allows for the classification of each user, enabling different billing methods to be formulated for different users in subsequent billing processes. This achieves the rational utilization of computing resources, thereby enabling effective billing of user data during the upgrade period while reducing the waste of computing resources and improving upgrade efficiency.

[0108] In some embodiments, the gateway General Packet Radio Service (GPRS) support node is further configured to:

[0109] Upon receiving a Packet Data Protocol Context Creation Request from any user, if it is determined that the user level of any user is Level 1, a First Context Creation Response is sent to any user so that the user can use the service based on the First Context Creation Response.

[0110] The resource amount generated by any user creating a response based on the first context for business use during the current upgrade time period is cached in the cache module.

[0111] Figure 4 This is a connection topology diagram between the user terminal, GGSN, and BOSS provided by the present invention; as shown below. Figure 4 As shown, the GGSN communicates with the user terminal. When the GGSN receives a Packet Data Protocol Context Creation Request sent by any user through the user terminal, the GGSN determines that the upgrade flag is set, and then queries the user ID in the first list and the second list.

[0112] If the user is not in the first or second list, the user is identified as a first-level user, i.e., an occasional user. In this case, the GGSN can directly send a first context creation response to the user to authorize the user to use services based on the first context creation response. The cache module will cache the amount of resources generated by the user's service use during the current upgrade period. After the BOSS upgrade is completed, the cached resources will be sent to the online billing module for billing summary, thereby maintaining the integrity of the user's billing call detail record data.

[0113] In some embodiments, the gateway General Packet Radio Service (GPRS) support node is further configured to:

[0114] Upon receiving a Packet Data Protocol Context Creation Request from any user, if it is determined that the user's level is Level 2, then the credit control request corresponding to the user is sent to the offline billing module.

[0115] Receive a credit control response message returned by the offline billing module; the credit control response message includes preset resource information allocated by the offline billing module to any user according to the credit control request;

[0116] A second context creation response is sent to any user based on the preset resource information, so that any user can use the service based on the second context creation response;

[0117] If it is determined that the preset resource information has been used up, and if it is determined that the service of any user has not been used up, then the process returns to the step of sending the credit control request corresponding to any user to the offline billing module, until the service of any user is used up.

[0118] Optionally, when the GGSN receives a Packet Data Protocol Context Creation Request sent by any user through a user terminal, if the GGSN determines that the upgrade flag is set, it will query the user ID in the first list and the second list.

[0119] If the user is in the first list, the user is identified as a second-tier user, meaning a non-occasional user with sufficient resources. At this point, the GGSN can establish a connection with the offline billing module and send a CCR message corresponding to the user to the offline billing module. Upon receiving the CCR message, the offline billing module sets the resource quota for the user to a preset fixed value, forming preset resource information, and returns this information to the GGSN via a CCA message. The GGSN then sends a second context creation response to the user based on the preset resource information, authorizing the user to use the service according to the second context creation response. When the allocated preset resources are used up, if it is determined that the user's service usage has not ended, the process returns to sending the corresponding CCR message to the offline billing module to authorize the user to allocate preset resource information again for service usage, until the user's service usage ends.

[0120] In some embodiments, the gateway General Packet Radio Service (GPRS) support node is further configured to:

[0121] Upon receiving a Packet Data Protocol Context Creation Request from any user, if it is determined that the user's level is Level 3, then the credit control request corresponding to the user is sent to the offline billing module.

[0122] Receive a credit control response message returned by the offline billing module; the credit control response message includes preset resource information allocated by the offline billing module to any user according to the credit control request;

[0123] If it is determined that the current remaining resources of any user are greater than the resource threshold, a second context creation response is sent to any user according to the preset resource information, so that any user can use the service according to the second context creation response;

[0124] If it is determined that the preset resource information has been used up, the amount of resources corresponding to the preset resource information is deducted from the current remaining resource amount to obtain an updated current remaining resource amount;

[0125] If it is determined that the service of any user has not ended and the updated current remaining resource amount is greater than the resource amount threshold, then return to the step of sending the credit control request corresponding to any user to the offline billing module, until the service of any user ends and / or the updated current remaining resource amount is less than or equal to the resource amount threshold.

[0126] Optionally, when the GGSN receives a Packet Data Protocol Context Creation Request sent by any user through a user terminal, if the GGSN determines that the upgrade flag is set, it will query the user ID in the first list and the second list.

[0127] If the user is in the second list, then the user is determined to be a third-level user, that is, a non-occasional user with insufficient resources. At this point, the GGSN can establish a connection with the offline billing module and send the corresponding CCR message to the offline billing module. Upon receiving the CCR message, the offline billing module sets the resource quota for that user to a preset fixed value, forming preset resource information, and returns this information to the GGSN via a CCA message. The GGSN then determines whether the user's current remaining resources are greater than the resource threshold. If they are, the GGSN sends a second context creation response to the user based on the preset resource information, authorizing the user to use the service according to the second context creation response. When the allocated preset resources are used up, if it is determined that the user's service has not ended, the resource amount corresponding to the preset resource information is deducted from the user's current remaining resources to obtain an updated current remaining resource amount. The GGSN then determines whether the updated current remaining resource amount is greater than the resource threshold. If it is, the GGSN returns to the step of sending the corresponding CCR message to the offline billing module to authorize the user to allocate preset resource information again for service use, until the user's service use ends, or the updated current remaining resource amount is less than or equal to the resource threshold, thus prematurely ending the service.

[0128] In summary, the system provided in this embodiment, when determining that a user is an occasional user, directly caches the resource usage amount generated by the user during the current upgrade period in the GGSN. When determining that a user is a non-occasional user, the credit control request is transmitted to the offline billing module, so that the offline billing module can perform billing processing on the resource usage amount generated by the user during the current upgrade period. This realizes collaborative billing between GGSN and BOSS, and effectively moves some billing processing functions that BOSS needs to complete to GGSN, reducing the computing power requirements of the offline billing module in BOSS and lowering the overall operating cost.

[0129] Figure 5 This is a schematic diagram of the GGSN and BOSS collaborative billing process provided by the present invention; as shown. Figure 5 As shown, the upgrade billing phase is jointly executed by GGSN and BOSS. The specific functional execution flowchart is as follows. Figure 5 As shown, the detailed steps are 510 to 560.

[0130] Step 510: Since users have been categorized into different levels through the user data analysis module, more refined and targeted processing can be implemented for each user. This allows some functionalities that need to be completed in this system to be moved forward to the GGSN for execution. First, the GGSN receives the PDP context creation request sent by the user through the user terminal.

[0131] In step 520, if the GGSN determines that the upgrade flag is set, it will query the user's user ID in the first list and the second list.

[0132] Step 530: If the user ID is in the first list, the GGSN establishes a connection with the offline billing module and sends the corresponding CCR message to the offline billing module. The offline billing module sets the resource quota to a preset fixed value based on the CCR message and returns the allocated preset resource information to the GGSN via a CCA message. The GGSN sends a PDP context creation response to the user based on the allocated preset resource information to authorize the user to use the service. When the user has used up the allocated preset resource information, the GGSN sends the corresponding CCR message to the offline billing module again to authorize the user to use the preset fixed value of preset resource information for the service again, until the service is used up.

[0133] Step 540: If the user is in the second list, the GGSN establishes a connection with the offline billing module and sends the corresponding CCR message to the offline billing module. The offline billing module sets the resource quota to a preset fixed value based on the CCR message and returns the allocated preset resource information to the GGSN via a CCA message. The GGSN determines whether the user's current remaining resource amount is greater than the resource amount threshold. If it is, the GGSN sends a PDP context creation response to the user to authorize the user to use the service and deducts the resource amount corresponding to the allocated preset resource information from the current remaining resource amount. When the user's allocated preset resource information is used up, if the updated current remaining resource amount is greater than the resource amount threshold, the GGSN sends the corresponding CCR message to the offline billing module again to authorize the user to use the preset fixed value of preset resource information for the service until the service is used up; otherwise, the service is terminated early.

[0134] Step 550: If the user list is not in the first or second list, the GGSN directly sends a PDP context creation response to the user to authorize the user to use the service and caches the amount of resources used by the user so that the cached data can be sent to the online billing module after the upgrade is completed, thus maintaining the integrity of the user's billing call detail record data.

[0135] Step 560: After the online billing module upgrade is completed, the offline billing module sends the saved call detail records to the online billing module. The GGSN sends the cached user resource usage to the online billing module. The online billing module collects the above information and completes the billing operation for all users, so as to allocate some computing power to the GGSN module with sufficient computing power, thereby reducing the waste of computing power resources and improving the efficiency of the upgrade.

[0136] In some embodiments, the system further includes an upgrade time prediction module 140, configured to:

[0137] Obtain the target upgrade duration corresponding to the business operation support system;

[0138] Based on the target upgrade duration, the historical call detail records (CDRs) generated by all users in the historical time periods that match each of the alternative upgrade periods are statistically analyzed to obtain the total historical CDR data corresponding to each of the alternative upgrade periods.

[0139] Based on the total historical call detail records, the candidate upgrade periods are sorted.

[0140] Based on the sorting results, the current upgrade time period is obtained from multiple candidate upgrade time periods.

[0141] It should be noted that upgrade times in related technologies are mostly selected based on human experience. However, with the explosive growth of users and user data, upgrade times selected by human experience are often unreliable and cannot achieve optimal results in the long run, resulting in reduced upgrade efficiency and, in severe cases, system crashes. Therefore, the selection of upgrade times needs to be systematically and scientifically evaluated. To address this, this system is equipped with an upgrade time prediction module, which intelligently predicts upgrade time periods to complete system upgrades efficiently and with high performance through reasonable upgrade time periods.

[0142] Figure 6 This is a flowchart illustrating the upgrade time prediction process provided by the present invention; optionally, the upgrade time prediction is executed by the upgrade time prediction module 140, and the specific functional execution flowchart is as follows. Figure 6 As shown, the detailed steps are 610 to 640.

[0143] Step 610: Since the upgrade time needs to be scientifically selected before the system is upgraded, the upgrade time prediction module first obtains the historical call detail records of each user in the historical period.

[0144] Step 620: Based on historical call detail record (CDR) data, different preset upgrade time periods are pre-set, and different preset upgrade durations are set for each preset upgrade time period. That is, at least one preset upgrade duration is selected from each preset upgrade time period throughout the day. Typically, to ensure the accuracy of the upgrade time prediction module, multiple different preset upgrade durations are selected. Based on these different preset upgrade durations, the total CDR data for all users is determined. Through extensive data statistical analysis, the current upgrade time period can be selected later based on the target upgrade duration. For example, the preset upgrade duration could be a reasonable length such as 5 minutes, 10 minutes, or 15 minutes.

[0145] For example, morning / noon / evening or every hour can be used as a preset upgrade time period, and multiple different durations can be selected within each preset upgrade time period. The duration selection can be appropriately extended to accommodate different upgrade times. For example, if the upgrade time is 5 minutes, a duration of 7 minutes can be selected.

[0146] Historical call detail records (CDRs) are analyzed and statistically analyzed within several different preset upgrade durations to obtain statistical results. Based on these results, several time periods with fewer CDRs are identified as candidate upgrade periods. These candidate upgrade periods can be selected based on specific circumstances; for example, the top 5 from the statistical results can be chosen as candidate upgrade periods.

[0147] Therefore, during the next system upgrade, the current upgrade time period can be selected based on the target upgrade duration set by the operator.

[0148] Step 630: Based on the preset target upgrade duration, analyze the user's historical call detail record (CDR) data. This allows for rapid prediction of the upgrade time period when operators select the upgrade time. For example, if the preset upgrade duration is 5 minutes, statistical analysis is performed on the historical CDR data within those 5 minutes that match the selected alternative upgrade time period. This yields the total historical CDR data for different alternative upgrade time periods, and at least one time period is selected as the current upgrade time period. For instance, among the three alternative upgrade time periods—8:00-8:05 AM, 12:00-12:05 PM, and 7:00-7:05 PM—with a target upgrade duration of 5 minutes, the total historical CDR data for each alternative upgrade time period shows that the total historical CDR data for the corresponding upgrade time period in the morning is the least. Therefore, 8:00-8:05 AM can be selected as the current upgrade time period.

[0149] It should be noted that the upgrade time period selected through the total historical call detail record (CDR) data can be one or more. If only one is output, the one with the least total historical CDR data among the multiple alternative upgrade time periods will be selected as the current upgrade time period. If multiple are output, the operator can make further selections based on their experience. This achieves a combination of intelligent output and human experience, making the final selected current upgrade time period more accurate and more suitable for system upgrades.

[0150] Step 640: Steps 610 to 630 above are the training process using historical call detail record data. Through pre-training, the actual selection of upgrade duration can be more accurate and faster. In step 640, the actual set target upgrade duration can be obtained, and the current upgrade time period can be predicted and selected through the same execution steps of steps 610 to 630 above.

[0151] The method provided in this embodiment analyzes historical communication billing records generated during user communications periodically to determine the period with the fewest communication billing records as the current upgrade time period. This effectively grasps the appropriate upgrade timing, improves the stability of recording user billing data during system upgrades, thereby enhancing upgrade stability and billing stability, increasing user satisfaction, and ultimately attracting more customers.

[0152] In some embodiments, historical call detail records (CDRs) include, but are not limited to, at least one of historical call data, historical data traffic, and historical SMS data.

[0153] Accordingly, the upgrade time prediction module is also used for:

[0154] Based on the type of upgrade content corresponding to the business operation support system, historical call detail records (CDRs) generated by each user within the historical time period matching each of the alternative upgrade periods are obtained from the historical call data, historical traffic data, and historical SMS data generated by each user within the historical time period matching each of the alternative upgrade periods.

[0155] Optionally, according to the system settings, historical call detail record (CDR) data includes three aspects: historical call data, historical data traffic, and historical SMS data. However, different users utilize CDR data to varying degrees; for example, in the past, communication was mainly by telephone, resulting in more call data than other types of data. Now, people often use messaging apps or entertainment apps for relaxation, leading to more data traffic than other types. Therefore, when selecting upgrade time periods based on historical CDR data, the selection can be targeted and specific as needed.

[0156] In other words, different historical call detail record (CDR) data can be sampled based on different billing schemes for historical CDR data to predict and obtain different current upgrade time periods.

[0157] For example, if the upgrade of this BOSS is related to traffic, when using historical call detail records (CDRs) for statistical analysis, you can focus only on the historical traffic data. That is, obtain the traffic usage within the historical time period that matches each of the three alternative upgrade time periods. For example, if the historical traffic usage counts for all users in the three alternative upgrade time periods of 8:00 to 8:05 am, 12:00 to 12:05 pm, and 7:00 to 7:05 pm are 10, 50, and 80 times respectively, then you can select 8:00 to 8:05 am as the current upgrade time period.

[0158] For example, if the upgrade focuses on call-related aspects, when using historical call detail records (CDRs) for statistical analysis, you can focus only on historical call data. This means obtaining call usage within historical time periods that match each of the candidate upgrade time periods. For instance, if the historical call usage counts for all users in the three candidate upgrade time periods of 8:00-8:05 AM, 12:00-12:05 PM, and 7:00-7:05 PM are 10, 5, and 20 respectively, then 12:00-12:05 PM can be selected as the current upgrade time period.

[0159] For example, weights can be assigned to various aspects of historical call detail record (CDR) data for targeted data utilization. For instance, historical call data, historical data traffic, and historical SMS data can be weighted at 0.4, 0.4, and 0.2 respectively. When acquiring historical CDR data, the focus is not solely on one data point, but rather on evaluating different historical CDR data for each user in a targeted manner. This allows for a more accurate selection of the current upgrade timeframe based on specific circumstances.

[0160] The system provided in this embodiment intelligently selects the corresponding historical call detail records from historical call data, historical traffic data, and historical SMS data for the upgrade time period based on the different types of upgrade content corresponding to BOSS. This makes the final selected current upgrade time period more adaptable to business needs, thereby effectively ensuring the continuity and stability of BOSS system upgrades and providing users with a better service experience.

[0161] The billing method provided by this invention is described below. The billing method described below can be referred to in correspondence with the billing system described above.

[0162] Figure 7 This is a flowchart illustrating the billing method provided by the present invention; for example... Figure 7The method is implemented based on the billing system provided in the above embodiments, and includes steps 710, 720, 730 and 740.

[0163] Step 710: Using the user data analysis module, based on each user's historical call detail record (CDR) data, historical average service resource consumption, and current remaining resources, obtain the user level corresponding to each user, and configure the upgrade protocol request for the business operation support system according to the user level of each user; the historical CDR data and the historical average service resource consumption are respectively the CDR data and average service resource consumption generated by each user in the historical time period matching the current upgrade time period.

[0164] Step 720: Upon receiving the upgrade protocol request sent by the business operation support system, the connection between the gateway general packet radio service support node and the online billing module of the business operation support system is disconnected, while the connection between the gateway general packet radio service support node and the offline billing module of the business operation support system is maintained. Based on the user level of each user, the amount of resources used by each user during the current upgrade time period is cached in the cache module of the gateway general packet radio service support node, or the credit control request corresponding to each user is sent to the offline billing module.

[0165] Step 730: Using the offline billing module, billing is performed according to the credit control request during the current upgrade time period;

[0166] Step 740: If it is determined that the upgrade of the business operation support system is completed, the online billing module is used to obtain the billing processing result corresponding to each user based on the resource quantity in the cache module and the billing processing result in the offline billing module.

[0167] Optionally, the user data analysis module may perform the following steps to classify users:

[0168] First, obtain the current upgrade time period of the BOSS in the current cycle.

[0169] Subsequently, within several historical periods prior to the current period, time intervals belonging to the same time range as the current upgrade time period are obtained as historical time intervals to match the current upgrade time period. The average number of call detail records (CDRs) for each user and the average amount of resources consumed for each service within this historical time interval are then calculated to obtain the historical CDR data and the average resource consumption of historical services for each user.

[0170] Furthermore, obtain the remaining resource amount of each user in the current period, and use it as the current remaining resource amount.

[0171] Subsequently, by combining each user's historical call detail records, historical average resource consumption, and current remaining resources, each user is classified into different levels to obtain their corresponding user level.

[0172] After obtaining the user level of each user, the upgrade protocol request of BOSS can be configured based on the user level. Then, GGSN can determine the user type according to the upgrade protocol request, and then determine whether to forward the data generated by the user during the upgrade to the offline billing module in BOSS for processing. This allows for more refined and targeted processing for users of different levels. In this way, some functions that the offline billing module in BOSS needs to perform are moved to GGSN to reduce the computing power requirements of the offline billing module in BOSS and reduce the overall operating cost.

[0173] like Figure 2 As shown, after receiving the upgrade protocol request, GGSN sends a response reply to BOSS, disconnects the connection with the online billing module during the current upgrade time period, retains the connection with the offline billing module, and sets the upgrade flag of BOSS to indicate that BOSS is performing an upgrade operation.

[0174] Furthermore, based on the first and second list information in the upgrade protocol request, GGSN determines the user level corresponding to each user. Based on different user levels, it caches the amount of resources used by each user during the current upgrade period in the cache module for billing processing on the local cache module, or forwards the credit control request corresponding to each user to the offline billing module for billing processing.

[0175] Optionally, after determining that the BOSS upgrade is complete, the online billing module connects with the GGSN and the offline billing module to obtain the billing processing results from the offline billing module, such as the call detail records (CDRs) used by non-occasional users during the current upgrade period, and obtains the amount of resources used by occasional users during the current upgrade period from the GGSN's cache module. The above information is then aggregated to complete the billing operation for all users, thereby obtaining the billing processing results for each user.

[0176] The method provided in this embodiment, through a user data analysis module, adaptively classifies users into more refined user levels based on their historical call detail records, historical average resource consumption, and current remaining resources. By classifying users into levels, some offline communication billing functions that the BOSS (Business OSS) is required to perform are moved forward to the GGSN (Google Generic Service SN). This enables billing through collaboration between the GGSN module and the BOSS, effectively reducing unnecessary waste of computing resources in the offline billing system during BOSS upgrades, improving resource utilization in the GGSN, and reducing the overhead and operating costs associated with wasting computing resources. Ultimately, this allows for effective billing of user data during upgrades while minimizing the waste of computing resources and improving upgrade efficiency.

[0177] Figure 8 An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 8 As shown, the electronic device may include: a processor 810, a communication interface 820, a memory 830, and a communication bus 840, wherein the processor 810, the communication interface 820, and the memory 830 communicate with each other through the communication bus 840. The processor 810 can call logical instructions in the memory 830 to execute a billing method, which includes: using a user data analysis module to obtain the user level corresponding to each user based on the historical call detail records (CDRs) and historical average resource consumption of each user, as well as the current remaining resources of each user; and configuring the upgrade protocol request of the service operation support system according to the user level of each user; the historical CDRs and historical average resource consumption are respectively the CDRs and average resource consumption generated by each user in a historical time period matching the current upgrade time period; upon receiving the upgrade protocol request sent by the service operation support system, using a gateway general packet radio service support node to disconnect from the service operation support system. The system maintains connections between the online billing modules of the business operation support system and the offline billing modules of the business operation support system. Based on the user level of each user, it caches the resource usage of each user during the current upgrade period in the cache module of the gateway's General Packet Radio Service support node, or sends the credit control requests corresponding to each user to the offline billing module. Using the offline billing module, it performs billing processing based on the credit control requests during the current upgrade period. Upon determining that the upgrade of the business operation support system is complete, it uses the online billing module to obtain the billing processing results corresponding to each user based on the resource usage in the cache module and the billing processing results in the offline billing module.

[0178] Furthermore, the logical instructions in the aforementioned memory 830 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or a part of the technical solution, 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 steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0179] On the other hand, the present invention also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute the billing method provided by the above-described methods. The method includes: using a user data analysis module, obtaining the user level corresponding to each user based on the historical call detail record data and historical average resource consumption of each user, as well as the current remaining resources of each user, and configuring the upgrade protocol request of the business operation support system according to the user level of each user; the historical call detail record data and the historical average resource consumption are respectively the call detail record data and average resource consumption of each user generated in a historical time period matching the current upgrade time period; upon receiving the upgrade protocol sent by the business operation support system... In the event of a request, the Gateway GPRS Support Node disconnects the connection with the online billing module of the Business Operation Support System while maintaining the connection with the offline billing module. Based on the user level of each user, the resource usage of each user during the current upgrade period is cached in the cache module of the Gateway GPRS Support Node, or the credit control request corresponding to each user is sent to the offline billing module. The offline billing module then performs billing processing based on the credit control request during the current upgrade period. Upon determining that the Business Operation Support System upgrade is complete, the online billing module obtains the billing result for each user based on the resource usage in the cache module and the billing processing result in the offline billing module.

[0180] In another aspect, the present invention also provides a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the billing method provided by the above methods. This method includes: using a user data analysis module to obtain the user level corresponding to each user based on the user's historical call detail record (CDR) data, historical average resource consumption, and the user's current remaining resources; and configuring an upgrade protocol request for the service operation support system according to the user's user level; the historical CDR data and the historical average resource consumption are respectively the CDR data and average resource consumption generated by each user within a historical time period matching the current upgrade time period; upon receiving the upgrade protocol request sent by the service operation support system, using a gateway general segmentation... The group of wireless service support nodes disconnects from the online billing module of the business operation support system, maintains the connection with the offline billing module of the business operation support system, and caches the amount of resources used by each user during the current upgrade period in the cache module of the gateway general packet radio service support node according to the user level of each user, or sends the credit control request corresponding to each user to the offline billing module; using the offline billing module, billing is processed according to the credit control request during the current upgrade period; when it is determined that the upgrade of the business operation support system is completed, the online billing module is used to obtain the billing result corresponding to each user according to the resource amount in the cache module and the billing processing result in the offline billing module.

[0181] The device embodiments described above are merely illustrative. The units described 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 modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0182] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0183] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A billing system, characterized in that, include: User data analysis module, gateway general packet radio service support node and business operation support system; The gateway general packet radio service support node includes a caching module, and the service operation support system includes an offline billing module and an online billing module; The user data analysis module is used to obtain the user level of each user based on the user's historical call detail records (CDRs) and historical average resource consumption, as well as the user's current remaining resources, and to configure the upgrade protocol request of the business operation support system according to the user's user level; the historical CDRs and historical average resource consumption are respectively the CDRs and average resource consumption generated by each user in the historical time period that matches the current upgrade time period. The gateway general packet radio service support node is used to disconnect from the online billing module and maintain the connection with the offline billing module when it receives the upgrade protocol request sent by the business operation support system. It also caches the amount of resources used by each user in the current upgrade time period to the cache module according to the user level of each user, or sends the credit control request corresponding to each user to the offline billing module. The offline billing module is used to perform billing processing based on the credit control request during the current upgrade time period; The online billing module is used to obtain the billing processing result corresponding to each user based on the resource quantity in the cache module and the billing processing result in the offline billing module when it is determined that the upgrade of the business operation support system has been completed. The user data analysis module is also used for: If any user's historical call detail record (CDR) data is less than or equal to the CDR data threshold, the user level of that user is determined to be the first level. If the historical call detail record (CDR) data of any user is greater than the CDR data threshold, the current remaining resource amount of any user is compared with a preset multiple of the historical average resource consumption of any user. If it is known that the current remaining resources of any user are greater than a preset multiple of the historical average resource consumption, the user level of any user is determined to be the second level. If it is known that the current remaining resources of any user are less than or equal to a preset multiple of the historical average resource consumption, the user level of any user is determined to be the third level. The gateway general packet radio service support node is also used for: Upon receiving a Packet Data Protocol Context Creation Request from any user, if it is determined that the user level of any user is Level 1, a First Context Creation Response is sent to any user so that the user can use the service based on the First Context Creation Response. The resource amount generated by any user during the current upgrade time period for using services by creating a response based on the first context is cached in the cache module. The gateway general packet radio service support node is also used for: Upon receiving a Packet Data Protocol Context Creation Request from any user, if it is determined that the user's level is Level 2, then the credit control request corresponding to the user is sent to the offline billing module. Receive the credit control response message returned by the offline billing module; The credit control response message includes preset resource information allocated by the offline billing module to any user based on the credit control request; A second context creation response is sent to any user based on the preset resource information, so that any user can use the service based on the second context creation response; If it is determined that the preset resource information has been used up, and if it is determined that the service of any user has not been used up, then return to the step of sending the credit control request corresponding to any user to the offline billing module, until the service of any user is used up; The gateway general packet radio service support node is also used for: Upon receiving a Packet Data Protocol Context Creation Request from any user, if it is determined that the user's level is Level 3, then the credit control request corresponding to the user is sent to the offline billing module. Receive the credit control response message returned by the offline billing module; The credit control response message includes preset resource information allocated by the offline billing module to any user based on the credit control request; If it is determined that the current remaining resources of any user are greater than the resource threshold, a second context creation response is sent to any user according to the preset resource information, so that any user can use the service according to the second context creation response; If it is determined that the preset resource information has been used up, the amount of resources corresponding to the preset resource information is deducted from the current remaining resource amount to obtain an updated current remaining resource amount; If it is determined that the service of any user has not ended and the updated current remaining resource amount is greater than the resource amount threshold, then return to the step of sending the credit control request corresponding to any user to the offline billing module, until the service of any user ends and / or the updated current remaining resource amount is less than or equal to the resource amount threshold.

2. The billing system according to claim 1, characterized in that, The system also includes an upgrade time prediction module, used for: Obtain the target upgrade duration corresponding to the business operation support system; Based on the target upgrade duration, the historical call detail records (CDRs) generated by all users in the historical time periods that match each of the alternative upgrade periods are statistically analyzed to obtain the total historical CDR data corresponding to each of the alternative upgrade periods. Based on the total historical call detail records, the candidate upgrade periods are sorted. Based on the sorting results, the current upgrade time period is obtained from multiple candidate upgrade time periods.

3. The billing system according to claim 2, characterized in that, The upgrade time prediction module is also used for: Based on the type of upgrade content corresponding to the business operation support system, historical call detail records (CDRs) generated by each user within the historical time period matching each of the alternative upgrade periods are obtained from the historical call data, historical traffic data, and historical SMS data generated by each user within the historical time period matching each of the alternative upgrade periods.

4. A billing method, characterized in that, The method is applied to the billing system as described in any one of claims 1 to 3, and the method includes: Using the user data analysis module, based on each user's historical call detail records (CDRs) and historical average resource consumption, as well as the current remaining resources of each user, the user level corresponding to each user is obtained, and the upgrade protocol request of the business operation support system is configured according to the user level of each user; the historical CDRs and historical average resource consumption are respectively the CDRs and average resource consumption generated by each user in the historical time period matching the current upgrade time period. Upon receiving the upgrade protocol request sent by the business operation support system, the gateway general packet radio service support node disconnects the connection with the online billing module of the business operation support system while maintaining the connection with the offline billing module of the business operation support system. Based on the user level of each user, the amount of resources used by each user during the current upgrade time period is cached in the cache module of the gateway general packet radio service support node, or the credit control request corresponding to each user is sent to the offline billing module. Using the offline billing module, billing is performed based on the credit control request during the current upgrade period; Upon determining that the upgrade of the business operation support system is complete, the online billing module is used to obtain the billing processing result corresponding to each user based on the resource quantity in the cache module and the billing processing result in the offline billing module. If any user's historical call detail record (CDR) data is less than or equal to the CDR data threshold, the user level of that user is determined to be the first level. If the historical call detail record (CDR) data of any user is greater than the CDR data threshold, the current remaining resource amount of any user is compared with a preset multiple of the historical average resource consumption of any user. If it is known that the current remaining resources of any user are greater than a preset multiple of the historical average resource consumption, the user level of any user is determined to be the second level. If it is known that the current remaining resources of any user are less than or equal to a preset multiple of the historical average resource consumption, the user level of any user is determined to be the third level. Upon receiving a Packet Data Protocol Context Creation Request from any user, if it is determined that the user level of any user is Level 1, a First Context Creation Response is sent to any user so that the user can use the service based on the First Context Creation Response. The resource amount generated by any user during the current upgrade time period for using services by creating a response based on the first context is cached in the cache module. Upon receiving a Packet Data Protocol Context Creation Request from any user, if it is determined that the user's level is Level 2, then the credit control request corresponding to the user is sent to the offline billing module. Receive a credit control response message returned by the offline billing module; the credit control response message includes preset resource information allocated by the offline billing module to any user according to the credit control request; A second context creation response is sent to any user based on the preset resource information, so that any user can use the service based on the second context creation response; If it is determined that the preset resource information has been used up, and if it is determined that the service of any user has not been used up, then return to the step of sending the credit control request corresponding to any user to the offline billing module, until the service of any user is used up; Upon receiving a Packet Data Protocol Context Creation Request from any user, if it is determined that the user's level is Level 3, then the credit control request corresponding to the user is sent to the offline billing module. Receive a credit control response message returned by the offline billing module; the credit control response message includes preset resource information allocated by the offline billing module to any user according to the credit control request; If it is determined that the current remaining resources of any user are greater than the resource threshold, a second context creation response is sent to any user according to the preset resource information, so that any user can use the service according to the second context creation response; If it is determined that the preset resource information has been used up, the amount of resources corresponding to the preset resource information is deducted from the current remaining resource amount to obtain an updated current remaining resource amount; If it is determined that the service of any user has not ended and the updated current remaining resource amount is greater than the resource amount threshold, then return to the step of sending the credit control request corresponding to any user to the offline billing module, until the service of any user ends and / or the updated current remaining resource amount is less than or equal to the resource amount threshold.

5. An electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the billing method as described in claim 4.

6. A non-transitory 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 billing method as described in claim 4.

7. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the billing method as described in claim 4.

Images