Charging notification function entity, charging function entity, call record processing method and device

Abstract

The disclosed embodiments provide a billing notification function entity, a billing function entity, a call record processing method, a device, and a storage medium, and belong to the field of communication technology. The method is applied to the billing function entity, including: constructing a call record according to the billing message, and generating a call record file according to the call record; transmitting the call record file to the business operation support system, wherein the business operation support system is used to process the received call record file to sort the call record file, and if the business operation support system sorts out an erroneous call record file, it sends a recovery and recollection request to the billing function entity; obtaining an erroneous call record file list according to the recovery and recollection request sent by the business operation support system; restoring all erroneous call record files in the erroneous call record file list from the backup call record file directory, so that the erroneous call record files can be restored, thereby improving the real-time and accuracy of subsequent billing.

Description

Technical Field

[0001] The embodiments of the present disclosure relate to the field of communication technologies, and in particular to a charging notification function entity, a charging function entity, a call record processing method, a device, and a storage medium. Background Art

[0002] Billing is an important function in a communication system. During the billing process for communication services in the communication system, if a problem is found in the call record file, there is currently no error correction mechanism, which may result in billing errors. Summary of the Invention

[0003] The main purpose of the embodiments of the present disclosure is to propose a billing notification function entity, a billing function entity, a call record processing method, a device and a storage medium, aiming to restore erroneous call record files.

[0004] To achieve the above objectives, the present disclosure provides a method for processing a call record file, which is applied to a billing function entity. The method includes:

[0005] Constructing a call record according to the billing message, and generating a call record file according to the call record;

[0006] The call record file is transmitted to the business operation support system; wherein the business operation support system is used to process the received call record file and sort the call record file. If the business operation support system sorts out an erroneous call record file, it sends a recovery and re-collection request to the billing function entity;

[0007] Obtaining a list of error call record files according to the recovery and recollection request sent by the business operation support system;

[0008] Restore all erroneous call record files in the erroneous call record file list from the backup call record file directory; wherein, the business operation support system is used to re-collect the restored call record files.

[0009] To achieve the above-mentioned purpose, the embodiment of the present disclosure also proposes a billing notification functional entity, which is applied to the billing functional entity. The billing notification functional entity is used to communicate with the business operation support system. The billing notification functional entity includes a billing open service, which is used to register on the network storage functional entity. The billing open service is used to be called by the business operation support system through the network storage functional entity to implement the steps of the above-mentioned call record file processing method.

[0010] To achieve the above objectives, the embodiment of the present disclosure further proposes a charging function entity for communication connection with the service operation support system, wherein the charging function entity is the above-mentioned charging notification function entity.

[0011] To achieve the above-mentioned purpose, the embodiment of the present disclosure also proposes a call record file processing device, which includes a memory, a processor, a program stored on the memory and executable on the processor, and a data bus for realizing connection and communication between the processor and the memory. When the program is executed by the processor, the steps of the aforementioned method are implemented.

[0012] To achieve the above objectives, the present disclosure further provides another method for processing call record files, which is applied to a service operation support system. The method for processing call record files includes:

[0013] Receive the call record file delivered by the billing function entity;

[0014] Process the received call record files;

[0015] If an erroneous call record file is sorted out, a recovery and recollection request is sent to the billing function entity; wherein the billing function entity is used to obtain an erroneous call record file list according to the recovery and recollection request, and restore all erroneous call record files in the erroneous call record file list from the backup call record file directory;

[0016] Re-collect the restored call record file.

[0017] To achieve the above objectives, an embodiment of the present disclosure provides a storage medium for computer-readable storage, wherein the storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the steps of the aforementioned method.

[0018] The billing notification function entity, billing function entity, call record processing method, device and storage medium proposed in the embodiments of the present disclosure belong to the field of communication technology. The method is applied to the billing function entity, including: constructing a call record according to the billing message and generating a call record file according to the call record; transmitting the call record file to the business operation support system; wherein the business operation support system is used to send a recovery and recollection request according to the call record file; obtaining an erroneous call record file list according to the recovery and recollection request sent by the business operation support system; restoring all erroneous call record files in the erroneous call record file list from the backup call record file directory, thereby restoring the erroneous call record files, and then the business operation support system can recollect the restored call record files, thereby improving the accuracy of subsequent billing based on the call record files. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 This is a diagram of the basic modules of a 5G network.

[0020] Figure 2 This is a module diagram of the 5G core network.

[0021] Figure 3This is a module diagram for implementing 5G billing in 3GPP networks.

[0022] Figure 4 The present invention provides a flowchart of billing message interaction in the method for processing call record files provided in an embodiment of the present invention.

[0023] Figure 5 It is a module diagram of the billing function entity and other network function entities provided by the embodiment of the present disclosure.

[0024] Figure 6 This is a flowchart of the call record file processing method provided in the embodiment of the present disclosure applied to the billing function entity.

[0025] Figure 7 The flowchart of the call record file processing method provided in the embodiment of the present disclosure is applied to the business operation support system.

[0026] Figure 8 This is a flow chart of a business operation support system discovering a billing open service provided by an embodiment of the present disclosure.

[0027] Figure 9 This is a flowchart of performing call record file auditing through notification messages provided by an embodiment of the present disclosure.

[0028] Figure 10 This is a flow chart of performing call record file auditing through service invocation provided by an embodiment of the present disclosure.

[0029] Figure 11 This is a flowchart of performing call record file auditing through notification message mode and service call mode respectively provided by the embodiment of the present disclosure.

[0030] Figure 12 This is a flowchart of user call record auditing through notification message mode and service call mode respectively provided by the embodiment of the present disclosure. DETAILED DESCRIPTION

[0031] In order to make the purpose, technical solutions and advantages of the present disclosure more clearly understood, the present disclosure is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present disclosure and are not intended to limit the present disclosure.

[0032] It should be noted that although the network functional entities are divided in the device schematic and the logical order is shown in the flowchart, in some cases, the steps shown or described can be performed in a different order than the module division in the device or the order in the flowchart.

[0033] In the following description, suffixes such as “entity” used to indicate elements are used only to facilitate description of the embodiments of the present disclosure and have no special meaning by themselves.

[0034] 5G (the 5th Generation mobile communication technology) is the fifth generation mobile communication standard and an extension of LTE (Long Term Evolution). 5G is used to provide data connections and services. Figure 1 The 5G network includes user equipment (UE), (radio) access network (RAN), core network (CN), and data network (DN). The UE is used to access the (R)AN network and establish a PDU session. The CN is connected to the (R)AN, and the DN is connected to the CN.

[0035] See also Figure 2 The 5G core network consists of network functional entities such as User Plane Function (UPF), Session Management Function (SMF), Access and Mobility Management Function (AMF), Authentication Server Function (AUSF), Network Slice Selection Function (NSSF), Network Exposure Function (NEF), Network Repository Function (NRF), Policy Control Function (PCF), Unified Data Management Function (UDM), Application Function (AF), and Charging Function (CHF).

[0036] See also Figure 3In the 5G charging function of the 3GPP (the 3rd Generation Partnership Project) network, the CN area (Domain) includes SMF, where SMF includes the Charging Trigger Function (CTF). CTF is used to collect charging information and send the charging information to the Charging Function CHF through the Nchf service interface. The Charging Function CHF includes the Charging Data Function (CDF) and the Online Charging Function (OCF). For offline charging messages, CDF is responsible for constructing the charging information into a Call Detail Record (CDR) and transmitting it to the Charging Gateway Function (CGF). For online charging messages, OCF is responsible for processing the charging information. OCF works with the Rating Function (RF) and the Account Balance Management Function (CBM). The CGF is used to store and manage the CDRs received from the CDF and send the CDR files to the BOSS billing system through the Bx interface.

[0037] See also Figure 4 The embodiment of the present disclosure provides a step of billing message interaction in a method for processing a call record file, which at least includes:

[0038] 1. The UE accesses the (R)AN network, establishes a PDU session, and sends a Charging Data Request message to the CHF. In one embodiment, the SMF is configured to send the Charging Data Request message to the CHF via the Nchf interface.

[0039] 2. The CHF performs routing selection based on the user number segment and selects the BOSS at the user's home location. In one embodiment, the CHF obtains the user number information from the billing data request message and obtains the user number segment through the user number information. The billing data request message carries the user number information, so the CHF can obtain the user number information from the billing data request message. The CHF can select the BOSS corresponding to the user number segment, that is, the BOSS at the user's home location. In some applications, when an NRF is deployed on the network, the NRF can find the BOSS at the user's home location based on the user number segment.

[0040] 3. The CHF forwards the Charging Data Request message to the BOSS. The Charging Data Request message includes three types of request messages: a charging creation request message (Nchf_ConvergedCharging_Create), a charging update request message (Nchf_ConvergedCharging_Update), and a charging release request message (Nchf_ConvergedCharging_Release).

[0041] 4. The BOSS saves the received Charging Data Request message and returns a Charging Data Response message. The Charging Data Response message includes three types of response messages: Nchf_ConvergedCharging_Create, Nchf_ConvergedCharging_Update, and Nchf_ConvergedCharging_Release.

[0042] 5. CHF forwards the Charging Data Response message to SMF.

[0043] Through the above steps 1-5, the transmission of the Charging Data Request message and the Charging Data Response is completed.

[0044] The billing message interaction step in the method for processing a call record file disclosed in this embodiment at least includes:

[0045] 6. Trigger a Notify message. In one embodiment, the BOSS initiates a session re-authentication process, triggering a Notify message.

[0046] 7. BOSS sends a Charging Notify Request message to CHF;

[0047] 8. Based on the Charging Data Request message generated by the above process, BOSS obtains the address of CHF and forwards the Charging Notify Request message to SMF;

[0048] 9. The SMF sends a Charging Notify Response message to the CHF. Specifically, after receiving the Charging Notify Request message, the SMF processes the Notify request and sends a Charging Notify Response message to the CHF. In one embodiment, the Notify request may be a session re-authentication request.

[0049] 10. CHF forwards the Charging Notify Response message to BOSS.

[0050] Through the above steps 6-10, the Notify message is triggered and the transmission of the Charging Notify Request message and the Charging Notify Response is completed.

[0051] See also Figure 5This embodiment discloses a charging function entity CHF. In one embodiment, the charging function entity is applied in a 3GPP network; the charging function entity CHF is used to communicate with a business operation support system (BOSS) and to transmit data with the business operation support system (BOSS). The charging function entity CHF is also used to communicate with an SMF and to transmit data with the SMF to receive charging messages transmitted by the SMF. The CHF includes a charging message function (CMF), a charging data function (CDF), a charging gateway function (CGF), and a charging notification function (CNF) entity. CTF is embedded in SMF. SMF is used to collect billing information based on the user's network resource usage through the embedded CTF, and send the billing information to CHF through the Nchf service interface. The billing function entity CHF is used to receive billing messages from SMF, construct call records based on the received billing messages, generate call record files based on the constructed call records, and transmit call record files and route forwarding billing messages to the Business & Operation Support System (BOSS), so that the billing system in BOSS completes the final billing based on the received call record files and billing messages. Billing messages include offline and online billing messages. For offline billing messages, the CDF is responsible for constructing the billing information into a call detail record (CDR) and transmitting it to the CGF. For online billing messages, the OCF is responsible for billing information processing, interacting with the Rating Function (RF) and the Account Balance Management Function (ABMF) to implement rating and account balance management. The CGF stores and manages the CDRs received from the CDF and sends them to the BOSS's billing system via the Bx interface for billing processing. The billing function entity CHF disclosed in this embodiment can implement multiple functions, including but not limited to: call detail record recovery, call detail record auditing, call detail record querying, call detail record statistics, and user auditing.

[0052] In actual applications, the UE accesses the (R)AN network, establishes a PDU session, and the SMF reports the charging message and transmits it to the charging function entity. The charging function entity CHF can implement multiple functions, for example, as follows:

[0053] Construct a call record based on the billing information and generate a call record file based on the call record;

[0054] The call record file is delivered to the business operation support system (BOSS); the business operation support system is configured to send a recovery and recollection request based on the call record file; the recovery and recollection request refers to a recovery and recollection request. In one embodiment, the call record file is delivered to the BOSS via the Bx interface. After receiving the call record file delivered by the CHF, the BOSS processes the received call record file. If any error call record file is found, the BOSS sorts out the error call record file and sends a recovery and recollection request to the CHF.

[0055] Obtain a list of error call record files based on the recovery and recollection requests sent by the business operations support system;

[0056] All error call record files in the error call record file list are restored from the backup call record file directory; wherein the business operation support system is used to re-collect the restored call record files. Thus, the BOSS can re-collect the restored call record files from the CHF.

[0057] In one embodiment, before step 601, the charging function entity is further configured to:

[0058] Receive the billing message transmitted by SMF, so that the billing function entity can construct a call bill according to the received billing message and generate a call bill file based on the call bill.

[0059] In one embodiment, in order to verify and correct billing information and improve billing real-time performance and accuracy, the charging function CHF is further configured to:

[0060] Receive the call bill file audit request sent by BOSS; wherein, BOSS sends the call bill file audit request to CHF based on the received call bill file;

[0061] The call record file audit information is returned to the BOSS according to the received call record file audit request; wherein, the BOSS is used to verify the correctness of the call record file according to the call record file audit information returned by the CHF.

[0062] In one embodiment, to further verify and correct billing information and improve billing real-time performance and accuracy, the charging function entity CHF is also used to audit user call records, specifically to:

[0063] Receive user call bill audit requests from BOSS; if there are suspicious user call bills, BOSS sends a user call bill audit request to CHF;

[0064] The CHF returns the billing information of the user to be audited to the BOSS according to the received user call bill audit request; wherein, the BOSS is used to verify the billing information of the user to be audited returned by the CHF.

[0065] Furthermore, the charging notification function entity CNF is used to communicate with the business operation support system. The CNF includes a charging exposure service (Nchf_ChargingExposure service). The CNF is used to assemble all the functions of the CHF into the charging exposure service (Nchf_ChargingExposure service). In one embodiment, the charging exposure service (Nchf_ChargingExposure service) is used to register on the network storage function (Network Repository Function, referred to as NRF) entity, so that the charging exposure service (Nchf_ChargingExposure service) can be used to be called by the BOSS through the NRF to realize all the functions of the above-mentioned CHF. In actual applications, the charging exposure service (Nchf_ChargingExposure service) is registered on NRF and provided to BOSS or third-party systems through the service-based interface (SBI). BOSS or third-party systems discover and call the charging capability exposure service (Nchf_ChargingExposure service) through NRF, so that they can flexibly and conveniently call the corresponding functions of CHF, and then realize all the functions of CHF through service calls, avoiding being limited to CHF itself.

[0066] See also Figure 6 The present disclosure provides a method for processing call bill files, which is applied to a charging function entity (CHF). Prior to executing the method, the UE accesses the (R)AN network, establishes a PDU session, and the SMF reports and transmits charging information to the CHF. The method for processing call bill files applied to the charging function entity includes at least:

[0067] 601: Construct a call record according to the billing message and generate a call record file according to the call record;

[0068] 602: The call record file is transferred to the business operation support system (BOSS). The business operation support system is configured to send a recovery and recollection request based on the call record file. The business operation support system processes the received call record file and sorts it as a call record file. If the business operation support system sorts out an erroneous call record file, it sends a recovery and recollection request to the CHF. Specifically, after receiving the call record file transferred by the CHF, the BOSS processes the received call record file and sorts it as a call record file. If an erroneous call record file is present, the BOSS sorts out the erroneous call record file and sends a recovery and recollection request to the CHF. The recovery and recollection request refers to a recovery and recollection request, and the recovery and recollection request includes a list of erroneous call record files. In one embodiment, the call record file is transferred to the BOSS via the Bx interface.

[0069] 603: Obtaining a list of error call record files according to the recovery and recollection request sent by the business operation support system. Specifically, the CHF parses the recovery and recollection request sent by the business operation support system to obtain the list of error call record files in the recovery and recollection request.

[0070] 604: Restore all error call record files in the error call record file list from the backup call record file directory.

[0071] After step 604, the BOSS may re-collect the restored call record file from the CHF.

[0072] In one embodiment, before step 601, the method for processing a call record file further includes:

[0073] Receive the billing message transmitted by SMF. CHF can then construct a call bill based on the received billing message and generate a call bill file based on the call bill.

[0074] In one embodiment, in order to verify and correct billing information and improve billing real-time performance and accuracy, the call record file processing method further includes a call record file audit step before step 603, specifically including:

[0075] Receive the call bill file audit request sent by BOSS; wherein, BOSS sends the call bill file audit request to CHF based on the received call bill file;

[0076] The call record file audit information is returned to the BOSS according to the received call record file audit request; wherein, the BOSS is used to verify the correctness of the call record file according to the call record file audit information returned by the CHF.

[0077] In one embodiment, in order to further verify and correct billing information and improve billing real-time performance and accuracy, before step 603, the call record file processing method further includes a step of auditing the user call record, specifically including:

[0078] Receive user call bill audit requests from BOSS; if there are suspicious user call bills, BOSS sends a user call bill audit request to CHF;

[0079] CHF returns the billing information of the user to be audited to BOSS based on the received user call bill audit request; wherein, BOSS is used to verify the billing information of the user to be audited returned by CHF, thereby verifying the correctness of the billing information of the user to be audited.

[0080] See also Figure 7 The present disclosure provides a method for processing call bill files, which is applied to BOSS. Prior to executing the method, the UE accesses the (R)AN network, establishes a PDU session, and the SMF reports billing information and transmits it to the CHF. The CHF receives the billing message transmitted by the SMF, constructs a call bill based on the received billing message, generates a call bill file based on the call bill, and transmits the call bill file to the BOSS. The method for processing call bill files applied to the BOSS includes at least:

[0081] 701: receiving the call record file delivered by the billing function entity;

[0082] 702: Process the received call record files and sort them into call record files;

[0083] 703: If an erroneous call record file is found, a restore and recollection request is sent to the charging function entity. The restore and recollection request includes a list of erroneous call record files. The CHF parses the restore and recollection request sent by the business operation support system to obtain the list of erroneous call record files in the restore and recollection request. The CHF is also used to restore all erroneous call record files in the list of erroneous call record files from the backup call record file directory.

[0084] 704: Re-collect the restored call record file.

[0085] In one embodiment, to verify and correct billing information and improve billing real-timeness and accuracy, the call record file processing method further includes, before step 702, the step of auditing the call record file, specifically including:

[0086] Send a call record file audit request to the CHF based on the received call record file; wherein, the CHF is used to return the call record file audit information to the BOSS based on the call record file audit request;

[0087] Verify the correctness of the call record file based on the call record file audit information returned by CHF.

[0088] Furthermore, in order to improve the real-time performance and accuracy of billing, in one embodiment, the session document file is audited by means of a notification request message. Specifically, the steps of auditing the session document file by means of a notification request message include:

[0089] Get the CHF address based on the received call log file;

[0090] Send a notification request message to the CHF at the corresponding address according to the obtained address; wherein the notification request message is completed by the BOSS, and the notification request message includes a call record file audit instruction, and the call record file audit instruction includes a call record file list; after receiving the notification request, the CHF identifies the call record file audit instruction in the notification request message, obtains the call record file information according to the call record file audit instruction, sends a notification response message to the BOSS, and returns the call record file audit information according to the obtained call record file information; further, the call record file information may include but is not limited to: call record file name, call record file size, number of call record files, and call record file modification time;

[0091] Verify the correctness of the call record file based on the call record file audit information returned by CHF.

[0092] In one embodiment, to further verify and correct billing information and improve billing real-time performance and accuracy, step 702 includes auditing the user's call records, specifically including:

[0093] If there is a suspicious user call record, a user call record audit request is sent to the CHF; wherein, the CHF is used to return the billing information of the user to be audited according to the user call record audit request;

[0094] Verify the billing information of the user to be audited returned by CHF to verify the correctness of the billing information of the user to be audited.

[0095] Furthermore, in order to improve the real-time performance and accuracy of billing, in one embodiment, the user's call records are audited by means of a notification request message (Notify). Specifically, step 702 includes:

[0096] If there is a suspicious user call record, obtain the CHF address;

[0097] Send a notification request message to the CHF at the corresponding address based on the acquired address; wherein the notification request message is completed by the BOSS and includes a user call bill audit instruction, which includes user information, such as a user number segment; after receiving the notification request, the CHF identifies the user call bill audit instruction in the notification request message, obtains the user call charge information to be audited based on the user call bill audit instruction, sends a notification response message to the BOSS, and returns the obtained user call charge information to be audited; further, the user call charge information to be audited may include, but is not limited to, service identifier, rate group, session duration, and traffic information;

[0098] Verify the user call fee information returned by CHF for audit.

[0099] It is understandable that in order to improve the real-time performance and accuracy of billing, in another embodiment, the user's call records are audited by calling the billing open service. Specifically, step 702 includes:

[0100] If there are suspicious user call records, the user call record audit sub-service of the billing open service of CHF is called. After the user call record audit sub-service of the billing open service is called, the user call record is audited and the billing information of the user to be audited is returned through CHF. After the user call record audit is completed, CHF also sends a service call completion response to BOSS.

[0101] Receive the service call completion response sent by CHF and the billing information of the user to be audited;

[0102] Verify the user call fee information returned by CHF for audit.

[0103] The billing notification functional entity, billing functional entity and call record processing method proposed in the embodiments of the present disclosure construct a call record according to the billing message, generate a call record file according to the call record, pass the call record file to the business operation support system, send a recovery and re-collection request according to the call record file through the business operation support system, obtain an erroneous call record file list according to the recovery and re-collection request sent by the business operation support system, and restore all erroneous call record files in the erroneous call record file list from the backup call record file directory, so that the erroneous call record files can be restored, and then the business operation support system can re-collect the restored call record files, so as to improve the accuracy of subsequent billing based on the call record files.

[0104] In some embodiments, call record file processing can be achieved through the Notify method or service call method; call record file auditing can also be performed through the Notify method or service call method; and user call record auditing can also be performed through the Notify method or service call method. Detailed descriptions will be given later in conjunction with practical application examples.

[0105] In one embodiment, when NRF is deployed in the network and BOSS discovers the charging exposure service (Nchf_ChargingExposure service), the recovery and reacquisition request sent by BOSS is a service call request; in other embodiments, when NRF is not deployed in the network, the recovery and reacquisition request sent by BOSS is a Notify request.

[0106] In actual applications, the UE accesses the (R)AN network, establishes a PDU session, and the SMF reports the billing information and transmits it to the CHF. The call record file processing method includes at least the following:

[0107] CHF receives the charging message transmitted by SMF;

[0108] CHF constructs a call record based on the received billing message and generates a call record file;

[0109] The CHF transfers the call record file to the BOSS. In one embodiment, the call record file is transferred to the BOSS via the Bx interface.

[0110] BOSS receives the call log files delivered by CHF;

[0111] BOSS processes the received call record files;

[0112] If BOSS sorts out an erroneous call record file, BOSS sends a recovery and recollection request to CHF;

[0113] CHF receives recovery and re-acquisition requests sent by BOSS;

[0114] CHF obtains a list of error call record files based on the recovery and recollection requests;

[0115] CHF restores all error call record files in the error call record file list from the backup call record file directory;

[0116] BOSS re-collects the restored call record file.

[0117] See also Figure 8 In one embodiment, the step of discovering the billing open service at least includes:

[0118] 1. CHF sends a registration request for the Nchf_ChargingExposure service to NRF; the charging exposure service can be used to implement, but is not limited to, functions such as call record file recovery, call record file audit, call record query, call record statistics, and user audit;

[0119] 2. Register the Nchf_ChargingExposure service through NRF;

[0120] 3. NRF sends a registration completion response of Nchf_ChargingExposure service to CHF;

[0121] 4. BOSS sends a discovery request for the Nchf_ChargingExposure service to NRF;

[0122] 5. NRF sends a discovery success response of the Nchf_ChargingExposure service to BOSS.

[0123] In one embodiment, the method for processing a call record file further includes:

[0124] If BOSS sorts out an erroneous call record file, BOSS determines whether NRF is deployed in the network;

[0125] If BOSS determines that NRF is deployed in the network, BOSS searches for billing open services;

[0126] If BOSS finds the billing open service, it will call the billing open service and call the call record file recovery sub-service in the billing open service, that is, the calling method is call record file recovery;

[0127] CHF receives the call request and obtains the list of error call record files in the call request message;

[0128] CHF restores the corresponding call record files from the backup call record file directory to the collection directory;

[0129] BOSS collects call record files and then re-bills;

[0130] If the BOSS determines that there is no NRF deployed in the network, the BOSS obtains the address of the CHF and sends a Notify request message to the corresponding CHF based on the obtained CHF address. The BOSS sets the Notification type of the Notify message to "recollect call record files" and fills in the list of call record files that need to be recollected.

[0131] After receiving the Notify request message, the CHF identifies it as a call record file recovery and recollection message based on the Notification type and forwards the Notify message to the CNF unit. The CNF unit then restores the corresponding call record files from the CHF backup call record file directory to the collection directory based on the list of error call record files in the Notify message for further collection by the BOSS.

[0132] CHF responds to BOSS and returns the call record file recovery completion information. BOSS collects the call record file and then re-bills.

[0133] See also Figure 9 In actual applications, if NRF is not deployed in the network, the method for processing the bill file provided by the present disclosure can be implemented through a notification message (Notify), which at least includes:

[0134] 1. The UE accesses the (R)AN network, establishes a PDU session, reports billing information and transmits it to the CHF. The CHF receives the message, constructs a call record, and generates a call record file.

[0135] 2. CHF transfers the call record file to BOSS through the Bx interface;

[0136] 3. The BOSS sorts out the erroneous call record files from the call record files. Specifically, the BOSS processes the billing call record files to sort out the erroneous call record files, thereby triggering a call record file recovery and re-collection request.

[0137] 4. The BOSS sends a Charging Notify Request to the CHF, with the Notification Type set to "CDR Rescramble." Specifically, the BOSS obtains the CHF's address and enters the Charging Notify Request field, the Notification Type field, and the list of CDR files to be rescrambled. The Notification Type field is set to "CDR Rescramble." The BOSS then sends the Charging Notify Request to the CHF.

[0138] 5. The CHF performs call record file recovery. Specifically, upon receiving the Charging Notify Request, the CHF identifies it as a call record file recovery and recollection message based on the Notification type and forwards the Charging Notify Request to the CNF. The CNF then recovers all error record files from the backup directory based on the error record file list in the Charging Notify Request. The recovered record files are then available for further collection by the BOSS.

[0139] 6. CHF sends a Charging Notify Response to BOSS, returning information indicating that the call record file recovery is complete. BOSS collects the recovered call record file and performs re-billing.

[0140] See also Figure 10 In actual applications, if NRF is deployed in the network and BOSS discovers the billing open service, the bill file processing method provided by the present disclosure can be implemented by service call, which at least includes:

[0141] 1. The UE accesses the (R)AN network, establishes a PDU session, reports billing information and transmits it to the CHF. The CHF receives the message, constructs a call record, and generates a call record file.

[0142] 2. CHF transfers the call record file to BOSS through the Bx interface;

[0143] 3. The BOSS sorts out the erroneous call record files from the call record files. Specifically, the BOSS processes the billing call record files to sort out the erroneous call record files, thereby triggering a call record file recovery and re-collection request.

[0144] 4. BOSS sends a Nchf_ChargingExposure service call request to CHF, using the call file recovery method. This means that the call file audit sub-service of the billing exposure service is called.

[0145] 5. CHF performs call record file recovery. Specifically, after receiving the service call request, CHF recovers all error call record files in the error call record file list from the backup call record file directory based on the error call record file list in the request message. The recovered call record files can then be used by BOSS for further collection.

[0146] 6. CHF sends a Nchf_ChargingExposure service call completion response to BOSS and returns the call record file recovery completion information. BOSS collects the recovered call record file and re-bills.

[0147] See also Figure 11 In actual applications, the call record file processing method provided by the present disclosure also includes auditing the call record file, which can be audited by using the Notify method and the service call method. The steps of auditing the call record file by the Notify method include at least steps 1, 2, 3, 4, 5, and 6, and the steps of auditing the call record file by the service call method include at least steps 1, 2, 3, 4a, and 6a:

[0148] The method for auditing a conversation document includes at least the following steps:

[0149] Step S1: The UE accesses the (R)AN network, establishes a PDU session, reports billing information and transmits it to the CHF. The CHF receives the message, constructs a call record, and generates a call record file.

[0150] Step S2: CHF transfers the call record file to BOSS through the Bx interface;

[0151] Step S3: BOSS collects call bill file audit information. Specifically, before processing the billing call bill file, BOSS audits the received call bill file, triggering a call bill file audit request.

[0152] Step S4: The BOSS sends a Charging Notify Request to the CHF, with the Notification Type being "CDR File Audit." Specifically, the BOSS obtains the CHF address and enters the Charging Notify Request field, the Notification Type field, and the list of CDR files to be audited. The Notification Type field is "CDR File Resale." The BOSS then sends the Charging Notify Request to the CHF.

[0153] Step S4a: BOSS calls CHF's Nchf_ChargingExposure service, and the calling method is call record file audit;

[0154] Step S5: The CHF performs a call record file audit. Specifically, after receiving the Notify message, the CHF identifies it as a call record file audit message based on the Notification type and forwards the Charging Notify Request message to the CNF. The CNF then obtains the call record file information to be audited, including but not limited to: the call record file name, the call record file size, the number of call record files, and the call record file modification time.

[0155] Step S6: CHF sends a Charging Notify Response to BOSS and returns the call bill file audit information. BOSS verifies the correctness of the collected call bill file based on the call bill file audit information.

[0156] Step S6a: CHF sends a Nchf_ChargingExposure service call completion response to BOSS and returns the call bill file audit information. BOSS verifies the correctness of the collected call bill file.

[0157] See also Figure 12 In actual applications, the method for processing call records provided by the present disclosure also includes auditing user call records, which can be audited through the Notify method and the service call method. The steps of auditing user call records through the Notify method include at least the following: 1, 2, 3, 4, 5, and 6, and the steps of auditing user call records through the service call method include at least the following: 1, 2, 3, 4a, and 6a:

[0158] 1. The UE accesses the (R)AN network, establishes a PDU session, reports billing information and transmits it to the CHF. The CHF receives the message, constructs a call record, and generates a call record file.

[0159] 2. CHF transfers the call record file to BOSS through the Bx interface;

[0160] 3. BOSS collects user call bill audit information. Specifically, when BOSS processes billing call bills, it audits suspicious user call bills, triggering a user call bill audit request.

[0161] 4. The BOSS sends a Charging Notify Request to the CHF, with the Notification type set to User CDR Audit. Specifically, the BOSS obtains the CHF address and enters the Charging Notify Request field, the Notification type field, and the user information to be audited. The Notification type field is set to User CDR Audit, and the user information can be a user number segment.

[0162] 4a. BOSS calls CHF's Nchf_ChargingExposure service through user call record audit.

[0163] 5. The CHF performs a user bill audit. Specifically, upon receiving the Notify message, the CHF identifies it as a user bill audit message based on the NotificationType and forwards the Charging Notify Request message to the CNF. The CNF then obtains the user billing information to be audited. The user billing information to be audited includes, but is not limited to, service ID, rate group, session duration, and traffic information.

[0164] 6. CHF sends Charging Notify Response to BOSS, returning the user billing information to be audited. BOSS verifies the correctness of the user billing information based on the user billing information.

[0165] 6a. CHF sends a Nchf_ChargingExposure service call completion response to BOSS, returning the user billing information to be audited. BOSS verifies the correctness of the user billing information based on the user billing information.

[0166] The call record file processing method proposed in the embodiments of the present disclosure can be implemented through a billing notification function entity and a business operation support system, or through a billing function entity and a business operation support system, thereby restoring erroneous call record files to enable call record statistics and call record query, thereby improving the real-time and accuracy of subsequent billing. Furthermore, through the billing notification function entity and the business operation support system, or through the billing function entity and the business operation support system, call record file recovery, call record file auditing, and user call record auditing can also be implemented, further improving the accuracy of subsequent billing.

[0167] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory may optionally include a memory remotely arranged relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0168] The embodiments described in the embodiments of the present disclosure are intended to more clearly illustrate the technical solutions of the embodiments of the present disclosure and do not constitute a limitation on the technical solutions provided by the embodiments of the present disclosure. Those skilled in the art will appreciate that with the evolution of technology and the emergence of new application scenarios, the technical solutions provided by the embodiments of the present disclosure are also applicable to similar technical problems.

[0169] It will be understood by those skilled in the art that Figure 5 The charging function entities shown in the figure do not constitute a limitation on the embodiments of the present disclosure, and may include more or fewer network function entities than shown in the figure, or combine certain network function entities, or different network function entities. Figure 6 or Figure 7 The method for processing call record files shown in the figure does not constitute a limitation on the embodiments of the present disclosure, and may include more or fewer steps than shown in the figure, or a combination of certain steps, or different steps.

[0170] The embodiment of the present disclosure also provides a call record file processing device, which includes a memory, a processor, and a computer program stored in the memory and capable of running on the processor. When the processor executes the computer program, the above-described Figure 4 Steps 1 to 10 of the method, Figure 6 Steps 601 to 604 of the method, Figure 7 Steps 701 to 704 of the method, Figure 8 Steps 1 to 5 of the method, Figure 9Steps 1 to 6 of the method, Figure 10 Steps 1 to 6 of the method, Figure 11 Steps 1 to 6a of the method or Figure 12 Steps 1 to 6a of the method described in

[00145]

[0171] The non-transient software program and instructions required to implement the method for processing the call log file of the above embodiment are stored in the memory. When executed by the processor, the method for processing the call log file of the above embodiment is executed, for example, the method described above is executed. Figure 4 Steps 1 to 10 of the method, Figure 6 Steps 601 to 604 of the method, Figure 7 Steps 701 to 704 of the method, Figure 8 Steps 1 to 5 of the method, Figure 9 Steps 1 to 6 of the method, Figure 10 Steps 1 to 6 of the method, Figure 11 Steps 1 to 6a of the method or Figure 12 Steps 1 to 6a of the method described in

[00145]

[0172] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, i.e., they may be located in one place or distributed across multiple network units. Some or all of the modules may be selected based on actual needs to achieve the objectives of this embodiment.

[0173] In addition, the embodiment of the present disclosure further provides a storage medium, which is a computer-readable storage medium. The computer-readable storage medium stores computer-executable instructions. The computer-executable instructions are executed by a processor or controller, for example, by a processor in the above-mentioned node embodiment, so that the above-mentioned processor can execute the maintenance entity group intermediate point creation method in the above-mentioned embodiment, for example, execute the above-mentioned Figure 4 Steps 1 to 10 of the method, Figure 6 Steps 601 to 604 of the method, Figure 7 Steps 701 to 704 of the method, Figure 8 Steps 1 to 5 of the method, Figure 9 Steps 1 to 6 of the method, Figure 10 Steps 1 to 6 of the method, Figure 11 Steps 1 to 6a of the method or Figure 12 Steps 1 to 6a of the method described in

[00145]

[0174] The billing notification functional entity, billing functional entity, call record processing method, device and storage medium proposed in the embodiments of the present disclosure construct a call record according to the billing message, generate a call record file according to the call record, pass the call record file to the business operation support system, send a recovery and re-collection request according to the call record file through the business operation support system, obtain an erroneous call record file list according to the recovery and re-collection request sent by the business operation support system, and restore all erroneous call record files in the erroneous call record file list from the backup call record file directory, so that the erroneous call record files can be restored, and then the business operation support system can re-collect the restored call record files, so as to improve the accuracy of subsequent billing based on the call record files.

[0175] Those skilled in the art will appreciate that all or some of the steps in the methods, systems, and functional modules / units in the devices disclosed above may be implemented as software, firmware, hardware, or appropriate combinations thereof.

[0176] In a hardware implementation, the division between the network functional entities mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed by several physical components in cooperation. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include computer storage media (or non-transitory media) and communication media (or transient media). As is well known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by a computer. Furthermore, as is well known to those skilled in the art, communication media typically embodies computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0177] The preferred embodiments of the present disclosure are described above with reference to the accompanying drawings, but are not intended to limit the scope of the present disclosure. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and essence of the present disclosure should be within the scope of the present disclosure.

Claims

1. A method for processing call record files, applied to a billing function entity, characterized in that: The method for processing call record files includes: Constructing a call record according to the billing message, and generating a call record file according to the call record; The call record file is transmitted to the business operation support system; wherein the business operation support system is used to process the received call record file and sort the call record file. If the business operation support system sorts out an erroneous call record file, it sends a recovery and re-collection request to the billing function entity; Receiving a call record file audit request sent by the business operation support system; wherein the business operation support system is used to send a call record file audit request to the billing function entity based on the received call record file; Returning the call record file audit information to the business operation support system according to the received call record file audit request; wherein the business operation support system is used to verify the correctness of the call record file according to the call record file audit information returned by the billing function entity; Obtaining a list of error call record files according to the recovery and recollection request sent by the business operation support system; All error call record files in the error call record file list are restored from the backup call record file directory; wherein the business operation support system is used to re-collect the restored call record files.

2. The method for processing call record files according to claim 1, characterized in that: Also includes: Receiving a user call bill audit request sent by the business operation support system; wherein, if there is a suspicious user call bill, the business operation support system sends a user call bill audit request to the billing function entity; The billing function entity returns the billing information of the user to be audited to the business operation support system based on the received user call record audit request; wherein, the business operation support system is used to verify the billing information of the user to be audited returned by the billing function entity.

3. A method for processing call log files, applied to a business operation support system, characterized in that: The method for processing call record files includes: Receive the call record file delivered by the billing function entity; Sending a call record file audit request to the billing function entity according to the received call record file; wherein the billing function entity is used to return call record file audit information according to the call record file audit request; Verify the correctness of the bill file according to the bill file audit information returned by the billing function entity; Process the received call record files and sort them into call record files; If an erroneous call record file is sorted out, a recovery and recollection request is sent to the billing function entity; wherein the billing function entity is used to obtain an erroneous call record file list according to the recovery and recollection request, and restore all erroneous call record files in the erroneous call record file list from the backup call record file directory; Re-collect the restored call record file.

4. The method for processing call record files according to claim 3, characterized in that: The processing of the received call record file includes: If there is a suspicious user call record, a user call record audit request is sent to the billing function entity; wherein the billing function entity is used to return the billing information of the user to be audited according to the user call record audit request; Verify the billing information of the user to be audited returned by the billing function entity.

5. A charging notification function entity, characterized in that: The billing notification function entity is applied to the billing function entity, the billing notification function entity is used to communicate with the business operation support system, the billing notification function entity includes a billing open service, the billing open service is used to register on the network storage function entity, and the billing open service is used to be called by the business operation support system through the network storage function entity to implement the steps of the call record file processing method as described in any one of claims 1 to 2.

6. A charging function entity, used for communication connection business operation support system, characterized in that: The charging function entity includes the charging notification function entity according to claim 5.

7. A call record file processing device, characterized in that: The call record file processing device includes a memory, a processor, a program stored on the memory and executable on the processor, and a data bus for realizing connection and communication between the processor and the memory. When the program is executed by the processor, the steps of the call record file processing method as described in any one of claims 1 to 2 or the steps of the call record file processing method as described in any one of claims 3 to 4 are realized.

8. A storage medium for computer-readable storage, characterized in that: The storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the steps of the call record file processing method as described in any one of claims 1 to 2 or the steps of the call record file processing method as described in any one of claims 3 to 4.

Images