Fusion charging message processing method and device and nonvolatile storage medium

Abstract

The invention discloses a method and a device for processing a converged charging message and a nonvolatile storage medium. The method comprises the following steps: a charging message function component of a first network element receives a first request message sent by a second network element; a first charging strategy is determined based on first user information carried in the first request message, and the first user information at least comprises a first access point name and a first charging characteristic; when it is determined that the type of the first charging policy is offline charging, creating a first message based on the first request message, the first message being used for instructing a charging data function component of the first network element to create a call detail record for a converged charging session; and sending the first message to the charging data function component. According to the method and the device, the technical problem of low processing efficiency caused by the fact that the fused billing messages of online billing and offline billing all depend on a billing function to be processed when the fused billing messages are processed in the prior art is solved.

Description

Technical Field

[0001] The present application relates to the field of wireless communications, and in particular, to a method and device for processing converged billing messages and a non-volatile storage medium. Background Art

[0002] Converged billing refers to the integration of online billing and offline billing to achieve unified billing for different service types (such as voice, data, SMS, etc.). In 5G networks, this billing method has been widely used. Converged billing systems usually include multiple components, such as charging trigger function (CTF) and charging function (CHF), which work together to complete billing tasks.

[0003] In 4G / 5G networks, converged billing messages are exchanged online through the second major version of the Hypertext Transfer Protocol (HTTP) (Hypertext Transfer Protocol version 2, referred to as HTTP / 2). Since the message processing uses the JSON format to save the billing information and has many billing fields, there are high requirements for the message processing rate of CHF. When processing converged billing messages, the converged billing messages of online billing and offline billing all rely on the billing function for processing. Moreover, as the number of users continues to grow, the performance pressure of CHF will become greater and greater, and it is difficult to achieve significant improvements in a short period of time, and the processing efficiency is low.

[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0005] The embodiments of the present application provide a method, device and non-volatile storage medium for processing a converged billing message, so as to at least solve the technical problem in the related art that when processing a converged billing message, the converged billing messages of online billing and offline billing all rely on the billing function for processing, resulting in low processing efficiency.

[0006] According to one aspect of an embodiment of the present application, a method for processing a converged billing message is provided, including: a billing message function component of a first network element receives a first request message sent by a second network element, wherein the first request message is used to start a converged billing session; a first billing policy is determined based on first user information carried in the first request message, wherein the first user information at least includes a first access point name and a first billing feature, and the type of the first billing policy includes at least online billing and offline billing; when it is determined that the type of the first billing policy is offline billing, a first message is created based on the first request message, wherein the first message is used to instruct a billing data function component of the first network element to create a call detail record for the converged billing session, and the call detail record is used to store user session data associated with the converged billing session; and the first message is sent to the billing data function component.

[0007] In some embodiments of the present application, the first request message is a converged billing creation request message, the billing event notification address field in the first request message carries the IP address and port number of the second network element, and the target billing gateway identification field in the first request message carries the IP address of the first network element.

[0008] In some embodiments of the present application, after sending the first message to the billing data functional component, the method also includes: the billing data functional component creates a call detail record based on the first message; creates a second message based on the call detail record, wherein the second message is used to instruct the billing gateway functional component of the first network element to create a billing call record; and sends the second message to the billing gateway functional component.

[0009] In some embodiments of the present application, after determining the first charging policy based on the first user information carried in the first request message, the method also includes: generating a first response message corresponding to the first request message based on the first access point name and the first charging characteristic, and sending the first response message to the second network element, wherein the first response message is used to inform the second network element of the type of the first charging policy.

[0010] In some embodiments of the present application, the method also includes: the billing message function component receives a second request message sent by a second network element, wherein the second request message is used to update the converged billing session; determines a second billing policy based on second user information carried in the second request message, wherein the second user information includes at least a second access point name and a second billing characteristic; when it is determined that the type of the second billing policy is offline billing, creates a third message based on the second request message, wherein the third message is used to instruct the billing data function component to update the call detail record; and sends the third message to the billing data function component.

[0011] In some embodiments of the present application, the second request message is a converged billing update request message, the billing event notification address field in the second request message carries the IP address and port number of the second network element, and the target billing gateway identification field in the second request message carries the IP address of the first network element.

[0012] In some embodiments of the present application, after sending the third message to the billing data functional component, the method also includes: the billing data functional component updates the call detail record based on the third message; creates a fourth message based on the updated call detail record, wherein the fourth message is used to instruct the billing gateway functional component to update the billing call record; and sends the fourth message to the billing gateway functional component.

[0013] In some embodiments of the present application, after determining the second billing policy based on the second user information carried in the converged billing update request message, the method also includes: generating a second response message corresponding to the converged billing update request message based on the second access point name and the second billing characteristic, and sending the second response message to the second network element, wherein the second response message is used to inform the second network element that the billing message function component completes the update of the converged billing session.

[0014] In some embodiments of the present application, the method also includes: the billing message function component receives a first converged billing release request message sent by the second network element, wherein the first converged billing release request message is used to release the converged billing session; determines a third billing policy based on third user information carried in the first converged billing release request message, wherein the third user information includes at least a third access point name and a third billing characteristic; when it is determined that the type of the third billing policy is offline billing, creates a fifth message based on the first converged billing release request message, wherein the fifth message is used to instruct the billing data function component to release the call detail record; and sends the fifth message to the billing data function component.

[0015] In some embodiments of the present application, after sending the fifth message to the billing data functional component, the method also includes: the billing data functional component releases the call detail record based on the fifth message, and creates a sixth message based on the fifth message, and sends the sixth message to the billing gateway functional component, wherein the sixth message is used to instruct the billing gateway functional component to release the billing call record.

[0016] In some embodiments of the present application, after determining the third billing policy based on the third user information carried in the first converged billing release request message, the method also includes: generating a third response message corresponding to the first converged billing release request message based on the third access point name and the third billing characteristic, and sending the third response message to the second network element, wherein the third response message is used to inform the second network element that the billing message function component completes the release of the converged billing session.

[0017] According to another aspect of an embodiment of the present application, a method for processing converged billing messages is also provided, including: a second network element sends a third request message to a billing message function component of a first network element, wherein the third request message is used to start a converged billing session, the third request message is a converged billing update request message, the billing event notification address field in the third request message carries the IP address and port number of the second network element, and the target billing gateway identification field in the third request message carries the IP address of the first network element; and receives a fourth response message corresponding to the third request message sent by the billing message function component, wherein the fourth response message is used to inform the second network element of the type of the first billing policy.

[0018] In some embodiments of the present application, the method also includes: sending a fourth request message to the billing message functional component, wherein the fourth request message is used to update the converged billing session; the billing event notification address field in the fourth request message carries the IP address and port number of the second network element, and the target billing gateway identification field in the fourth request message carries the IP address of the first network element; receiving a fifth response message corresponding to the fourth request message sent by the billing message functional component, wherein the fifth response message is used to inform the second network element that the billing message functional component completes the update of the converged billing session.

[0019] In some embodiments of the present application, the method also includes: sending a second converged billing release request message to the billing message function component, wherein the second converged billing release request message is used to release the converged billing session; receiving a sixth response message corresponding to the second converged billing release request message sent by the billing message function component, wherein the sixth response message is used to inform the second network element that the billing message function component completes the release of the converged billing session.

[0020] In some embodiments of the present application, the first network element includes: a next generation charging gateway, and the second network element includes: a session management function entity.

[0021] According to another aspect of an embodiment of the present application, a device for processing a converged billing message is also provided, including: a receiving module, used for a billing message function component of a first network element to receive a first request message sent by a second network element, wherein the first request message is used to start a converged billing session; a determining module, used to determine a first billing policy based on first user information carried in the first request message, wherein the first user information at least includes a first access point name and a first billing characteristic, and the type of the first billing policy includes at least online billing and offline billing; a creating module, used to create a first message based on the first request message when it is determined that the type of the first billing policy is offline billing, wherein the first message is used to instruct a billing data function component of the first network element to create a call detail record for the converged billing session, and the call detail record is used to store user session data associated with the converged billing session; a sending module, used to send the first message to the billing data function component.

[0022] According to another aspect of an embodiment of the present application, a non-volatile storage medium is provided, in which a program is stored, wherein when the program is running, a method for processing converged billing messages executed on a device where the non-volatile storage medium is located is controlled.

[0023] According to another aspect of an embodiment of the present application, an electronic device is further provided, including: a memory and a processor, the processor being configured to run a program stored in the memory, wherein the above method for processing converged billing messages is executed when the program is running.

[0024] According to another aspect of an embodiment of the present application, a computer program product is provided, including computer instructions, and a method for processing converged billing messages is implemented when the computer instructions are executed by a processor.

[0025] In an embodiment of the present application, a charging message function component of a first network element is used to receive a first request message sent by a second network element, wherein the first request message is used to start a converged billing session; a first charging policy is determined based on first user information carried in the first request message, wherein the first user information at least includes a first access point name and a first billing characteristic, and the type of the first billing policy includes at least online billing and offline billing; when it is determined that the type of the first billing policy is offline billing, a first message is created based on the first request message, wherein the first message is used to instruct a charging data function component of the first network element to create a call detail record for the converged billing session, and the call detail record is used to store information associated with the converged billing session user session data; sending the first message to the billing data functional component, by receiving a first request message for opening a converged billing session, determining a first billing policy based on the first user information carried in the first request message, and in the case where the type of the first billing policy is offline billing, creating a first message based on the first request message, and sending the first message to the billing data functional component, thereby separating the converged billing message corresponding to the offline billing and no longer processing it by the billing function, thereby improving the processing efficiency, and further solving the technical problem in the related art that when processing the converged billing message, the converged billing messages of online billing and offline billing all rely on the billing function for processing, resulting in low processing efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0027] Figure 1 It is a hardware structure block diagram of a computer terminal for implementing a method for processing converged billing messages provided in an embodiment of the present application;

[0028] Figure 2 It is a flowchart of a method for processing a converged billing message provided according to an embodiment of the present application;

[0029] Figure 3 This is a schematic diagram of a billing creation process provided according to an embodiment of the present application;

[0030] Figure 4 is another schematic diagram of a billing creation process provided according to an embodiment of the present application;

[0031] Figure 5 It is a schematic diagram of billing update provided according to an embodiment of the present application;

[0032] Figure 6 is another billing update schematic diagram provided according to an embodiment of the present application;

[0033] Figure 7 It is a schematic diagram of a billing release process provided according to an embodiment of the present application;

[0034] Figure 8 is another schematic diagram of a charging release process provided according to an embodiment of the present application;

[0035] Fig. 9 It is a flowchart of another method for processing converged billing messages provided according to an embodiment of the present application;

[0036] Fig.10 It is a structural diagram of a device for processing converged billing messages provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0037] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0038] The information collected in the embodiments of the present application is information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with the relevant laws, regulations and standards of the relevant regions, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or reject automated decision-making results; if the user chooses to reject, the expert decision-making process will be entered.

[0039] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0040] In order to better understand the embodiments of the present application, the technical terms involved in the embodiments of the present application are explained as follows:

[0041] Charging Trigger Function (CTF): Mainly responsible for identifying and triggering charging events. CTF is usually embedded in network elements such as Session Management Function (SMF) or Policy Control Function (PCF). Its function is to monitor the service usage in the network. When an event that requires billing is detected, it will generate billing-related trigger information and assemble this information into a charging request (such as Accounting Request, ACR) and send it to the corresponding billing system, such as the Next-generation Charging Gateway (NCG).

[0042] Next-generation Charging Gateway (NCG): It has the characteristics of high performance, flexibility and scalability. It is responsible for aggregating, processing and transmitting the billing data from different network elements to ensure the accuracy and completeness of the billing information.

[0043] Charging Message Function (CMF) is a component responsible for billing message interaction in the 5G network. It mainly interacts with CTF and CHF for billing message interaction on the N40 interface, including billing creation, update and release requests. CMF is also responsible for the selection of CHF and notifies the Charging Data Function (CDF, ​​i.e., call bill) to create, update or release the billing session in order to generate the corresponding call detail record (CDR). CMF ensures the smooth progress of the billing process by managing the sending and receiving of billing messages.

[0044] Charging Data Function (CDF): responsible for constructing the charging information from the network entity into CDR and transmitting it to the Charging Gateway Function (CGF). CDR is a detailed billing record that contains various data on user service usage, such as time, data volume, service type, etc. CDF organizes this data into a CDR in a standard format and passes it to CGF for subsequent billing processing. CDF is an important logical functional entity in the offline billing process, which ensures the accuracy and integrity of the billing data.

[0045] Charging Gateway Function (CGF): CGF is a bridge connecting CDF and the billing domain. It is responsible for receiving CDR data transmitted by CDF and performing further processing, such as sorting, merging, filtering, decoding, routing and distribution. CGF routes the processed data to the corresponding accounting system, such as the billing center or billing database. CGF ensures that billing information can be accurately and timely transmitted to the billing domain by efficiently processing and routing billing data, providing data support for the final bill generation and billing analysis.

[0046] In the related art, when processing the converged billing message, the converged billing messages of online billing and offline billing all rely on the billing function for processing, resulting in a technical problem of low processing efficiency. In order to solve this problem, the embodiments of the present application provide a relevant solution, which is described in detail below.

[0047] According to an embodiment of the present application, an embodiment of a method for processing converged billing messages is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0048] The method embodiments provided in the embodiments of the present application can be executed in a computer terminal or a similar computing device. Figure 1 The hardware structure block diagram of a computer terminal for implementing a method for processing converged billing messages is shown. Figure 1 As shown, the computer terminal 10 may include one or more (102a, 102b, ..., 102n are used to illustrate) processors 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission module 106 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera. It can be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations shown.

[0049] It should be noted that the one or more processors 102 and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the computer terminal 10. As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0050] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the processing method of the converged billing message in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, the processing method of the converged billing message described above is realized. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the computer terminal 10 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.

[0051] The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0052] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 10 .

[0053] In the above-mentioned operating environment, an embodiment of the present application provides an embodiment of a method for processing converged billing messages. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0054] like Figure 2FIG. 1 is a flowchart of a method for processing a converged charging message according to an embodiment of the present application, including:

[0055] Step S202: The charging message function component of the first network element receives a first request message sent by the second network element, wherein the first request message is used to start a convergent charging session.

[0056] In the technical solution provided in step S202, the first network element includes: a next-generation billing gateway NCG, which integrates three components: a billing message function component CMF, a billing data function component CGF, and a billing gateway function component CDF. The second network element includes: a session management function entity; the first request message is a converged billing creation request message, the billing event notification address field in the first request message carries the IP address and port number of the second network element, and the target billing gateway identification field in the first request message carries the IP address of the first network element.

[0057] The following are specific embodiments:

[0058] The charging message function component (CMF) of the first network element (eg, the next generation charging gateway NCG network element) receives a first request message sent by the second network element (eg, SMF), where the first request message is a converged charging creation request message (eg, converged charging creation request message Nchf_ConvergedCharging_Create Request).

[0059] The charging event notification address field (notifyUri field) in the first request message header during HTTP / 2 interaction is used to indicate to which address the NCG should send the charging response or event notification after processing the charging event. In the HTTP / 2 protocol, it appears in the form of a uniform resource identifier (URI for short). The notifyUri field carries the IP address and port number of the second network element (SMF); the target charging gateway identification field (that is, the authority field) is used to indicate the network element address that initiates the request, that is, the IP address of the SMF). It carries the IP address of the first network element (NCG). That is, during the converged charging creation process, when the SMF sends the Nchf_ConvergedCharging_Create Request request to the NCG, the authority field will contain the IP address of the NCG, and the notifyUri field will contain the IP and port information of the SMF, so that the NCG can send the Nchf_ConvergedCharging_Create Response message (that is, the above-mentioned first response message) directly back to the address specified by the SMF after processing the request.

[0060] The first request message also carries multiple messages, such as: subscriber identifier (subscriberIdentifier): used to uniquely identify the user in the network, charging identifier (chargingId): used to uniquely identify a specific charging session or event to ensure tracking and management when processing charging information in the network, charging invocation timestamp (invocationTimeStamp): records the specific time point when the charging session starts or the charging event occurs, charging message sequence number (invocationSequenceNumber): used to identify the order of request or response messages, multiple charging unit usage triggers (multipleUnitUsagetriggers): triggers set a series of conditions, when the user's network usage reaches a specific threshold (such as traffic usage, voice duration, etc.), it will trigger the billing system to perform specific billing operations or notifications. And charging session information (pDUSessionChargingInformation): at least including the access point name (Access Point Name (APN) in 4G and DNN (Data Network Name) in 5G) and charging characteristics (Charging Characteristics, CC).

[0061] Step S204: determining a first charging policy based on the first user information carried in the first request message, wherein the first user information at least includes a first access point name and a first charging characteristic, and the type of the first charging policy at least includes online charging and offline charging.

[0062] Step S206, when it is determined that the type of the first billing policy is offline billing, a first message is created based on the first request message, wherein the first message is used to instruct the billing data function component of the first network element to create a call detail record for a converged billing session, and the call detail record is used to store user session data associated with the converged billing session.

[0063] The following are specific embodiments:

[0064] The CMF determines the first charging policy based on the first user information (i.e., the above-mentioned charging session information) carried in the first request message (i.e., the Nchf_ConvergedCharging_Create_Request message), for example, based on the configured first access point name (Access Point Name (APN) in 4G and DNN (Data Network Name) in 5G): APN is an identifier for identifying the service type, and different APNs correspond to different service types or applications. According to the service type requested by the user, when the service type indicates that it is applicable to offline charging (for example, the service type is a non-real-time data transmission service), the type of the first charging policy is determined to be offline charging; or the first charging policy is determined based on the configured first charging feature (i.e., CC): identifying the parameters of the first charging feature, the parameters of the first charging feature include information related to the type, for example, the charging feature indicates that the current user has a low requirement for real-time billing, for example, the billing cycle is monthly Based on the first request message, the key fields related to the converged billing session in the first message (for example, user identity identifier, billing identifier, billing activation timestamp, billing message sequence number, multiple billing unit usage triggers, and billing session information) are encapsulated and converted into a first message that can be recognized by the billing data function component (for example, CDF_CHARGING_MSG_INIT message, which contains all necessary information required for CDF to create or update a billing session, such as user identity identifier, billing identifier, etc., to ensure that CDF can generate CDR based on this information).

[0065] Step S208: Send the first message to the charging data function component.

[0066] In the technical solution provided in step S208, after the first message is sent to the billing data functional component, the billing data functional component creates a call detail record based on the first message; creates a second message based on the call detail record, wherein the second message is used to instruct the billing gateway functional component of the first network element to create a billing call record; and sends the second message to the billing gateway functional component.

[0067] The following are specific embodiments:

[0068] After CMF sends the first message (e.g., CDF_CHARGING_MSG_INIT message) to the charging data function component, the charging data function component creates a call detail record based on the first message. The CDR contains specific charging information, including but not limited to user activities, service usage, timestamps, session information, etc. Once the CDR is generated, the CDF component will further create a second message (e.g., CGF_CHARGING_MSG_INIT message) based on the CDR. This message is the communication content between CDF and CGF. CDF constructs the CGF_CHARGING_MSG_INIT message based on the generated CDR information (obtained by encapsulating the key fields (message fields related to converged billing) and the charging event summary in the CDR into a message that CGF can recognize). CDF sends the CGF_CHARGING_MSG_INIT message to CGF. After receiving the message, CGF starts to process the CDR data and create a billing bill. The billing bill is used to record the user's network usage details, including but not limited to the use of data traffic, voice calls, SMS services, and various value-added services. Further filtering, merging and routing of billing call records are performed to ensure that billing information can accurately reach the bill processing system.

[0069] After determining the first charging policy based on the first user information carried in the first request message, the CMF generates a first response message corresponding to the first request message based on the first access point name and the first charging characteristic, and sends the first response message to the second network element, wherein the first response message is used to inform the second network element of the type of the first charging policy.

[0070] The following are specific embodiments:

[0071] After the CMF determines the first charging policy based on the first user information carried in the first request message, it generates a first response message corresponding to the first request message based on the first access point name and the first charging feature: the CMF constructs the first response message based on the first access point name (DNN or APN) and the first charging feature (CC), fills in the invocation result field (invocationResult, used to indicate whether the request is successful, usually a status code), the charging message sequence number field (invocationSequenceNumber, used to identify the order of request or response messages, track the sequence identifier of a specific charging event or session creation request, this field is consistent between the request and response messages to ensure the order and consistency of the charging operation) and the charging session information field (pDUSessionChargingInformation, this field contains detailed information related to PDU session charging. In the response message, this field indicates how the SMF handles subsequent charging events and data, that is, the type of charging policy and specific charging rules and parameters.). The first response message contains at least the invocationResult, invocationSequenceNumber, and pDUSessionChargingInformation fields.

[0072] like Figure 3As shown, it is a schematic diagram of a billing creation process provided according to an embodiment of the present application. In the related art, during the creation of a converged billing session, SMF determines that a billing process needs to be initiated according to the APN configuration, and after successfully selecting NCG, it sends a converged billing creation request message (i.e., 1. Nchf_ConvergedCharging_Create_Request message) to CG (i.e., the next generation charging gateway NCG). After receiving the converged billing creation request message, CG (i.e., the next generation charging gateway NCG) forwards the billing request content (i.e., 2. Nchf_ConvergedCharging_Create_Request message) in the received converged billing creation request message to the service control point (Service Control Point, referred to as SCP for short). SCP selects the CHF of the corresponding scenario based on the billing characteristics CC and the user number segment. SCP will identify the user number segment and classify users according to the number segment. For example, users of a specific number segment may belong to an enterprise package, while users of another number segment may belong to a personal package. This helps SCP select the correct CHF based on the user's service level agreement (SLA) and billing policy. SCP sends a request message to CHF (i.e. 3.Nchf_ConvergedCharging_Create_Request message). The authority field of the request message is the IP address of SCP, and the notifyUri field is filled with the IP address and port number of SMF and the IP address and port number of NCG are added. CHF receives the request message, processes the service according to the information in the request, constructs a response message to SCP according to the charging policy (i.e. 4.Nchf_ConvergedCharging_Create_Response) and sends it to SCP. SCP receives the response message (i.e. 5.Nchf_ConvergedCharging_Create_Response) and forwards it to NCG according to the original route. NCG processes the response message and feeds back the response message to SMF, and sends a message to CDF to notify the creation of the charging session. After receiving the response message, SMF saves the relevant information (i.e. 6.Nchf_ConvergedCharging_Create_Response), notifies UPF of the relevant charging policy, and waits for the user plane function (UPF) to report the charging. In the related art, all convergent charging messages must be processed by CHF, resulting in low processing efficiency.

[0073] The method in the embodiment of the present application processes the converged charging message whose charging policy type is offline charging through NCG, without the need to process it through CHF. Figure 4FIG. 1 is a schematic diagram of another billing creation process provided in accordance with an embodiment of the present application. Figure 3 The improvement of the process shown in the figure is that NCG integrates three functional components: CMF, CDF, and CGF. After SMF or CTF sends the converged charging creation request message (1.Nchf_ConvergedCharging_Create_Request, i.e. the above-mentioned first request message) to CMF, CMF obtains the charging policy according to the user information and performs offline billing based on the APN or CC configuration: that is, the first charging policy is determined based on the first user information carried in the first request message, and when it is determined that the type of the first charging policy is offline billing, a first message is created based on the first request message, and the first message is sent to the billing data functional component; a response is returned to SMF: that is, a first response message corresponding to the first request message is generated based on the first access point name and the first billing feature (2.Nchf_ConvergedCharging_Create_Response in the figure), and the first response message is sent to the second network element (SMF or CTF). CMF creates a first message (1.1CDF_CHARGING_MSG_INIT in the figure) based on the first request message, and sends the message to CDF for CDF to create a call detail record CDR. CDF creates a second message (i.e. 1.2CGF_CHARGING_MSG_INIT in the figure) based on the call detail record and sends it to CGF. After receiving the message, CGF starts to process the CDR data and creates a billing call sheet, which is used to record the user's network usage details, including but not limited to data traffic, voice calls, SMS services, and the use of various value-added services. Further filtering, merging and routing of the billing call sheet ensures that the billing information can accurately reach the bill processing system.

[0074] After processing the first request message, the converged billing session is continued according to the update cycle (for example, 1 hour), as well as the updating of billing, billing bills, and call detail records. Specifically:

[0075] The billing message function component receives a second request message sent by a second network element, wherein the second request message is used to update a converged billing session; determines a second billing policy based on second user information carried in the second request message, wherein the second user information includes at least a second access point name and a second billing characteristic; creates a third message based on the second request message when it is determined that the type of the second billing policy is offline billing, wherein the third message is used to instruct the billing data function component to update a call detail record; and sends the third message to the billing data function component. The second request message is a converged billing update request message, the billing event notification address field in the second request message carries the IP address and port number of the second network element, and the target billing gateway identification field in the second request message carries the IP address of the first network element.

[0076] The billing data function component updates the call detail record based on the third message; creates a fourth message based on the updated call detail record, wherein the fourth message is used to instruct the billing gateway function component to update the billing call record; and sends the fourth message to the billing gateway function component.

[0077] After the billing message function component determines the second billing policy based on the second user information carried in the converged billing update request message, it generates a second response message corresponding to the converged billing update request message based on the second access point name and the second billing characteristic, and sends the second response message to the second network element, wherein the second response message is used to inform the second network element that the billing message function component has completed the update of the converged billing session.

[0078] It should be noted that the second request message and the first request message carry the same field type, and the message processing method is the same. The second request message is an update of the first request message, and the data of each field of the first request message is updated to the real-time data obtained in the current update cycle. The third message is an update of the first message in the current update cycle. The field type is consistent, and the message processing method is the same. The data carried in each field of the third message is the implementation data of the current update cycle; similarly, the fourth message is an update of the second message, and the second response message is an update of the first response message.

[0079] The following are specific embodiments: Figure 5As shown, it is a billing update schematic diagram provided according to an embodiment of the present application, which shows the converged billing update process when processing converged billing messages in the related technology. After SMF receives the billing report from UPF, after successfully selecting NCG, it sends a converged billing update request message to NCG. The authority field of the message is filled in with the IP address of NCG, and the notifyUri address needs to be supplemented with the IP address and port number of CG (i.e. NCG) on the basis of the IP address and port number of SMF (i.e. 1. Nchf_ConvergedCharging_Update_Request message in the figure). CG (i.e. Next Generation Billing Gateway NCG), NCG receives the request message, and forwards the received billing update request (i.e. 2. Nchf_ConvergedCharging_Update_Request message in the figure) to SCP. The authority field of the message is filled in with the IP address of SCP, and the notifyUri address needs to be supplemented with the IP address and port number of NCG on the basis of the IP address and port number of SMF. SCP selects the CHF of the corresponding scenario based on CC and user number segment, and sends an update request message to CHF (3.Nchf_ConvergedCharging_Update_Request in the figure). After receiving the update request message, CHF processes the service according to the information in the request, constructs a response message to SCP according to the charging policy (4.Nchf_ConvergedCharging_Update_Response in the figure) and sends it to SCP. SCP receives the response message (5.Nchf_ConvergedCharging_Update_Response in the figure) and forwards it to CG (i.e. NCG). NCG processes the response message, constructs a charging update request response message to SMF (6.Nchf_ConvergedCharging_Update_Response in the figure), and sends a message to CDF to notify the update of the charging session. After receiving the response message, SMF saves the relevant information, notifies UPF of the relevant charging policy, and waits for UPF to report the charging.

[0080] like Figure 6 FIG. 1 is another schematic diagram of billing update according to an embodiment of the present application, which is a fusion billing update process in an embodiment of the present application. Figure 5The process is improved, and the converged billing update message with the billing policy type of offline billing is processed through NCG, and there is no need to process it through CHF. Specifically: SMF sends (1.Nchf_ConvergedCharging_Update_Request, that is, the above-mentioned second request message) to CG (that is, NCG). After NCG receives the second request message, CMF obtains the billing policy according to the user information (that is, the above-mentioned second user information), and performs offline billing based on APN or CC configuration: that is, the second billing policy is determined based on the second user information carried in the second request message. When it is determined that the type of the second billing policy is offline billing, a second message is created based on the second request message, and the second message is sent to the billing data function component; a response is returned to SMF: that is, a second response message corresponding to the second request message is generated based on the second access point name and the second billing characteristics (2.Nchf_ConvergedCharging_Update_Response in the figure), and the second response message is sent to the second network element (SMF or CTF). CMF creates a third message (1.1CDF_CHARGING_MSG_UPDATE in the figure) based on the second request message, and sends the message to CDF for CDF to update the call detail record CDR. CDF creates a fourth message (i.e. 1.2CGF_CHARGING_MSG_UPDATE in the figure) based on the updated call detail record and sends it to CGF. After receiving the message, CGF starts to process CDR data and update the billing bill, which is used to record the user's network usage details, including but not limited to data traffic, voice calls, SMS services, and the use of various value-added services. Further filtering, merging and routing of the billing bills are performed to ensure that the billing information can accurately reach the bill processing system.

[0081] After completing the processing of the converged charging message, the release process of the converged charging is started, and the charging message function component receives the first converged charging release request message (Nchf_ConvergedCharging_ReleaseRequest message) sent by the second network element, wherein the first converged charging release request message is used to release the converged charging session; the third charging policy is determined based on the third user information carried in the first converged charging release request message, wherein the third user information at least includes a third access point name and a third charging characteristic; when it is determined that the type of the third charging policy is offline charging, a fifth message is created based on the first converged charging release request message (the same field type as the first message and the third message), wherein the fifth message is used to instruct the charging data function component to release the call detail record; and the fifth message is sent to the charging data function component. The charging data function component releases the call detail record based on the fifth message, and creates a sixth message based on the fifth message (the same field type as the second message and the fourth message), and sends the sixth message to the charging gateway function component, wherein the sixth message is used to instruct the charging gateway function component to release the charging call record. The billing gateway functional component releases the billing call record based on the sixth message. The billing message functional component generates a third response message (with the same field type as the first response message and the second response message) corresponding to the first converged billing release request message based on the third access point name and the third billing characteristic, and sends the third response message to the second network element (i.e., SMF), wherein the third response message is used to inform the second network element that the billing message functional component completes the release of the converged billing session. This process ensures that all necessary billing data is processed and released in a timely manner at the end of the session.

[0082] like Figure 7As shown, it is a schematic diagram of a charging release process provided according to an embodiment of the present application. In the related art, when the SMF releases the session, it selects NCG successfully and sends 1.Nchf_ConvergedCharging_Release Request message (converged charging release request message), and the authority field of the message is the IP address of NCG. NCG forwards the converged charging release request message (2.Nchf_ConvergedCharging_Release Request message in the figure) to the previously selected SCP, and the authority field of the message is the IP address of SCP. SCP selects the CHF of the corresponding scenario based on the charging characteristics CC and the user number segment, and sends a converged charging release request message (3.Nchf_ConvergedCharging_Release Request message in the figure) to CHF, and the authority field is the IP address of CHF. After receiving the request message, CHF processes the service according to the information in the converged charging release request message, constructs a response message to SCP (i.e., message 4.Nchf_ConvergedCharging_Release Response in the figure) and sends it to SCP. After receiving the response message, SCP forwards it to NCG according to the original route (i.e., message 5.Nchf_ConvergedCharging_Release Response in the figure). NCG processes the response message, constructs a charging release request response message to SMF (message 6.Nchf_ConvergedCharging_Release Response in the figure), and sends a message to CDF to notify the release of the converged charging session.

[0083] like Figure 8 FIG. 1 is a schematic diagram of another charging release process provided according to an embodiment of the present application, showing the fusion charging release process of the embodiment of the present application. Figure 7Improvement of the release process. The release process corresponding to the converged charging message with the charging policy type of offline charging is processed by NCG instead of CHF. Specifically, SMF sends (1.Nchf_ConvergedCharging_Release) to CG (i.e. NCG). Request, that is, the first converged charging release request message mentioned above), after NCG receives the first converged charging release request message, CMF obtains the charging policy according to the user information (that is, the third user information mentioned above), and performs offline billing based on the APN or CC configuration: that is, the third charging policy is determined based on the third user information carried in the first converged charging release request message, and when it is determined that the type of the third charging policy is offline billing, a fifth message is created based on the first converged charging release request message, and the fifth message is sent to the charging data function component, instructing the charging data function component to release the call detail record; and a response is returned to the SMF: that is, a third response message (2.Nchf_ConvergedCharging_ReleaseResponse in the figure) corresponding to the third request message is generated based on the third access point name and the third billing feature, and the third response message is sent to the second network element (SMF or CTF). CMF creates the fifth message (1.1CDF_CHARGING_MSG_RELEASE in the figure) based on the first converged billing release request message, and sends the message to CDF, which is used by CDF to release the call detail record CDR. CDF creates the sixth message (i.e. 1.2CGF_CHARGING_MSG_RELEASE in the figure) based on the fifth message and sends it to CGF. After receiving the message, CGF starts to process the CDR data and releases the billing call record.

[0084] like Fig. 9 FIG. 1 is a flowchart of another method for processing a converged charging message according to an embodiment of the present application, including:

[0085] In step S902, the second network element (i.e., SMF, or CTF) sends a third request message (the third request message may be the first request message) to the billing message function component of the first network element (NCG), wherein the third request message is used to start a converged billing session, the third request message is a converged billing update request message, the billing event notification address field in the third request message carries the IP address and port number of the second network element, and the target billing gateway identification field in the third request message carries the IP address of the first network element.

[0086] Step S904: Receive a fourth response message (the fourth response message may be the first response message) corresponding to the third request message sent by the charging message function component, wherein the fourth response message is used to inform the second network element of the type of the first charging policy.

[0087] Send a fourth request message (the fourth request message may be the second request message) to the billing message function component, wherein the fourth request message is used to update the converged billing session; the billing event notification address field in the fourth request message carries the IP address and port number of the second network element, and the target billing gateway identification field in the fourth request message carries the IP address of the first network element; receive a fifth response message (the fifth response message may be the second response message) corresponding to the fourth request message sent by the billing message function component, wherein the fifth response message is used to inform the second network element that the billing message function component completes the update of the converged billing session.

[0088] After processing the first request message, the converged billing session, as well as the update of billing, billing call records, and call detail records are continued according to the update cycle (for example, 1 hour). Specifically: SMF sends a second converged billing release request (the second converged billing release request can be the first converged billing release request) message to the billing message function component, wherein the second converged billing release request message is used to release the converged billing session; receives the sixth response message (the sixth response message can be the third response message) corresponding to the second converged billing release request message sent by the billing message function component, wherein the sixth response message is used to inform the second network element that the billing message function component has completed the release of the converged billing session.

[0089] The embodiment of the present application also provides a structural diagram of a device for processing a converged charging message, such as Fig.10 As shown, including:

[0090] The receiving module 1002 is used for the charging message function component of the first network element to receive a first request message sent by the second network element, wherein the first request message is used to start a convergent charging session.

[0091] The determination module 1004 is configured to determine a first charging policy based on the first user information carried in the first request message, wherein the first user information at least includes a first access point name and a first charging characteristic, and the type of the first charging policy at least includes online charging and offline charging.

[0092] The creation module 1006 is used to create a first message based on the first request message when it is determined that the type of the first billing policy is offline billing, wherein the first message is used to instruct the billing data function component of the first network element to create a call detail record for a converged billing session, and the call detail record is used to store user session data associated with the converged billing session.

[0093] The sending module 1008 is used to send the first message to the billing data function component.

[0094] It should be noted that Fig.10 The processing device of the fusion charging message is used to execute Figure 2 The processing method of the converged billing message shown is therefore Figure 2 The relevant explanations in the method for processing the integrated billing message in are also applicable to the processing device for the integrated billing message, and will not be repeated here.

[0095] It should be noted that the various modules in the above-mentioned converged billing message processing device can be program modules (for example, a set of program instructions that implement a certain specific function) or hardware modules. For the latter, it can be expressed in the following forms, but is not limited to this: the expression form of each of the above-mentioned modules is a processor, or the functions of each of the above-mentioned modules are implemented by a processor.

[0096] The embodiment of the present application also provides a non-volatile storage medium, the non-volatile storage medium includes a stored program, wherein when the program is running, the device where the non-volatile storage medium is located is controlled to execute the above method for processing converged billing messages. For example, the billing message function component of the first network element receives a first request message sent by the second network element, wherein the first request message is used to start a converged billing session; a first billing policy is determined based on the first user information carried in the first request message, wherein the first user information at least includes a first access point name and a first billing feature, and the type of the first billing policy includes at least online billing and offline billing; when it is determined that the type of the first billing policy is offline billing, a first message is created based on the first request message, wherein the first message is used to instruct the billing data function component of the first network element to create a call detail record for the converged billing session, and the call detail record is used to store user session data associated with the converged billing session; and the first message is sent to the billing data function component.

[0097] The embodiment of the present application also provides an electronic device, the electronic device includes a processor, the processor is used to run a program, wherein the above method for processing converged billing messages is executed when the program is running. For example, the billing message function component of the first network element receives a first request message sent by the second network element, wherein the first request message is used to start a converged billing session; based on the first user information carried in the first request message, a first billing policy is determined, wherein the first user information at least includes a first access point name and a first billing feature, and the type of the first billing policy includes at least online billing and offline billing; in the case where it is determined that the type of the first billing policy is offline billing, a first message is created based on the first request message, wherein the first message is used to instruct the billing data function component of the first network element to create a call detail record for the converged billing session, and the call detail record is used to store user session data associated with the converged billing session; the first message is sent to the billing data function component.

[0098] According to another aspect of the embodiment of the present application, a computer program product is also provided, including a computer program, which implements the above-mentioned method for processing converged billing messages when executed by a processor. For example, a billing message function component of a first network element receives a first request message sent by a second network element, wherein the first request message is used to start a converged billing session; a first billing policy is determined based on the first user information carried in the first request message, wherein the first user information at least includes a first access point name and a first billing feature, and the type of the first billing policy includes at least online billing and offline billing; when it is determined that the type of the first billing policy is offline billing, a first message is created based on the first request message, wherein the first message is used to instruct a billing data function component of the first network element to create a call detail record for a converged billing session, and the call detail record is used to store user session data associated with the converged billing session; and the first message is sent to the billing data function component.

[0099] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0100] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

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

[0102] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0103] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the relevant technology or all or part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk, etc. Various media that can store program codes.

[0104] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for processing a converged billing message, characterized in that: include: The charging message function component of the first network element receives a first request message sent by the second network element, wherein the first request message is used to start a convergent charging session; Determine a first charging policy based on the first user information carried in the first request message, wherein the first user information includes at least a first access point name and a first charging characteristic, and the type of the first charging policy includes at least online charging and offline charging; In a case where it is determined that the type of the first charging policy is offline charging, creating a first message based on the first request message, wherein the first message is used to instruct a charging data function component of the first network element to create a call detail record for the convergent charging session, and the call detail record is used to store user session data associated with the convergent charging session; The first message is sent to the charging data function component.

2. The method according to claim 1, characterized in that The first request message is a converged billing creation request message, the billing event notification address field in the first request message carries the IP address and port number of the second network element, and the target billing gateway identification field in the first request message carries the IP address of the first network element.

3. The method according to claim 1, characterized in that After sending the first message to the charging data function component, the method further includes: The charging data function component creates the call detail record based on the first message; Creating a second message based on the call detail record, wherein the second message is used to instruct the billing gateway function component of the first network element to create a billing call record; The second message is sent to the charging gateway functional component.

4. The method according to claim 1, characterized in that: After determining the first charging policy based on the first user information carried in the first request message, the method further includes: generating a first response message corresponding to the first request message based on the first access point name and the first charging feature, and sending the first response message to the second network element, wherein the first response message is used to inform the second network element of a type of the first charging policy.

5. The method according to claim 1, characterized in that The method further comprises: The charging message function component receives a second request message sent by the second network element, wherein the second request message is used to update the convergent charging session; Determining a second charging policy based on second user information carried in the second request message, wherein the second user information includes at least a second access point name and a second charging characteristic; In the case of determining that the type of the second charging policy is offline charging, creating a third message based on the second request message, wherein the third message is used to instruct the charging data function component to update the call detail record; The third message is sent to the charging data function component.

6. The method according to claim 5, characterized in that The second request message is a converged billing update request message, the billing event notification address field in the second request message carries the IP address and port number of the second network element, and the target billing gateway identification field in the second request message carries the IP address of the first network element.

7. The method according to claim 5, characterized in that After sending the third message to the charging data function component, the method further includes: The charging data function component updates the call detail record based on the third message; Creating a fourth message based on the updated call detail record, wherein the fourth message is used to instruct the billing gateway functional component to update the billing call record; The fourth message is sent to the charging gateway functional component.

8. The method according to claim 5, characterized in that After determining the second charging policy based on the second user information carried in the convergent charging update request message, the method further includes: generating a second response message corresponding to the convergent charging update request message based on the second access point name and the second charging characteristic, and sending the second response message to the second network element, wherein the second response message is used to inform the second network element that the charging message function component completes the update of the convergent charging session.

9. The method according to claim 1, characterized in that: The method further comprises: The charging message function component receives a first convergent charging release request message sent by the second network element, wherein the first convergent charging release request message is used to release the convergent charging session; Determine a third charging policy based on the third user information carried in the first converged charging release request message, wherein the third user information includes at least a third access point name and a third charging characteristic; In the case of determining that the type of the third charging policy is offline charging, creating a fifth message based on the first converged charging release request message, wherein the fifth message is used to instruct the charging data function component to release the call detail record; The fifth message is sent to the charging data function component.

10. The method according to claim 9, characterized in that After sending the fifth message to the charging data function component, the method further includes: The billing data function component releases the call detail record based on the fifth message, creates a sixth message based on the fifth message, and sends the sixth message to the billing gateway function component, wherein the sixth message is used to instruct the billing gateway function component to release the billing call record.

11. The method according to claim 9, characterized in that After determining the third charging policy based on the third user information carried in the first converged charging release request message, the method further includes: generating a third response message corresponding to the first converged charging release request message based on the third access point name and the third charging characteristic, and sending the third response message to the second network element, wherein the third response message is used to inform the second network element that the charging message function component completes the release of the converged charging session.

12. A method for processing a converged billing message, characterized in that: include: The second network element sends a third request message to the charging message function component of the first network element, wherein the third request message is used to start a converged charging session, the third request message is a converged charging update request message, the charging event notification address field in the third request message carries the IP address and port number of the second network element, and the target charging gateway identification field in the third request message carries the IP address of the first network element; Receive a fourth response message corresponding to the third request message sent by the charging message function component, wherein the fourth response message is used to inform the second network element of the type of the first charging policy.

13. The method according to claim 12, characterized in that The method further comprises: Sending a fourth request message to the charging message function component, wherein the fourth request message is used to update the converged charging session; the charging event notification address field in the fourth request message carries the IP address and port number of the second network element, and the target charging gateway identification field in the fourth request message carries the IP address of the first network element; Receive a fifth response message corresponding to the fourth request message sent by the charging message function component, wherein the fifth response message is used to inform the second network element that the charging message function component completes the update of the convergent charging session.

14. The method according to claim 12, characterized in that The method further comprises: Sending a second convergent billing release request message to the billing message function component, wherein the second convergent billing release request message is used to release the convergent billing session; Receive a sixth response message corresponding to the second convergent billing release request message sent by the billing message function component, wherein the sixth response message is used to inform the second network element that the billing message function component completes the release of the convergent billing session.

15. The method according to claim 12, characterized in that The first network element includes: a next generation charging gateway, and the second network element includes: a session management function entity.

16. A device for processing converged billing messages, characterized in that: include: A receiving module, configured for a charging message function component of a first network element to receive a first request message sent by a second network element, wherein the first request message is used to start a converged charging session; a determining module, configured to determine a first charging policy based on first user information carried in the first request message, wherein the first user information includes at least a first access point name and a first charging characteristic, and a type of the first charging policy includes at least online charging and offline charging; a creating module, configured to, when determining that the type of the first charging policy is offline charging, create a first message based on the first request message, wherein the first message is used to instruct a charging data function component of the first network element to create a call detail record for the convergent charging session, the call detail record being used to store user session data associated with the convergent charging session; A sending module is used to send the first message to the billing data function component.

17. A non-volatile storage medium, characterized in that: A program is stored in the non-volatile storage medium, wherein when the program is running, the device where the non-volatile storage medium is located is controlled to execute the method for processing the converged billing message described in any one of claims 1 to 11 or the method for processing the converged billing message described in any one of claims 12 to 15.

18. An electronic device, characterized in that: include: A memory and a processor, wherein the processor is used to run a program stored in the memory, wherein when the program is run, the method for processing a converged billing message described in any one of claims 1 to 11 or the method for processing a converged billing message described in any one of claims 12 to 15 is executed.

19. A computer program product comprising computer instructions, characterized in that When the computer instructions are executed by the processor, the method for processing the converged billing message described in any one of claims 1 to 11 or the method for processing the converged billing message described in any one of claims 12 to 15 is implemented.

Images