Session charging method, session charging apparatus, electronic device, and storage medium

Abstract

The present disclosure provides a session charging method, a session charging device, an electronic device and a computer readable storage medium, and belongs to the technical field of communication. The method comprises: obtaining a to-be-processed session, and identifying a charging identifier in the to-be-processed session; determining a charging rule of the to-be-processed session according to the identification result of the charging identifier; generating a charging configuration script based on the charging rule; and running the charging configuration script to charge the to-be-processed session. The present disclosure can accurately and efficiently charge the session.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a session billing method, session billing device, electronic device, and computer-readable storage medium. Background Technology

[0002] User Plane Function (UPF) is primarily used in 5G (5th Generation Mobile Communication Technology) customized network services, and the billing types involved differ among different customized network services. Currently, existing technologies can only manually configure billing rules by checking or tracking signaling, which is time-consuming, costly to debug, and inefficient. Summary of the Invention

[0003] This disclosure provides a session billing method, session billing device, electronic device, and computer-readable storage medium, thereby overcoming, at least to some extent, the problems of high billing costs and low efficiency in the prior art.

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

[0005] According to a first aspect of this disclosure, a session billing method is provided, applied to a user plane function terminal, comprising: acquiring a session to be processed and identifying a billing identifier in the session to be processed; determining a billing rule for the session to be processed based on the identification result of the billing identifier; generating a billing configuration script based on the billing rule; and running the billing configuration script to bill the session to be processed.

[0006] In an exemplary embodiment of this disclosure, determining the billing rule of the session to be processed based on the identification result of the billing identifier includes: when the billing identifier is identified as a user plane identifier, determining the billing rule of the session to be processed as a static billing rule; when the billing identifier is identified as a control plane identifier, determining the billing rule of the session to be processed as a dynamic billing rule.

[0007] In one exemplary embodiment of this disclosure, generating a billing configuration script based on the billing rule includes: when the billing rule is the static billing rule, generating a static billing configuration script from a preset static configuration template; and when the billing rule is the dynamic billing rule, generating a dynamic billing configuration script from a preset dynamic configuration template.

[0008] In one exemplary embodiment of this disclosure, before running the billing configuration script to bill the session to be processed, the method further includes: performing a first verification on the billing configuration script through a preset verification module, and returning a first verification result.

[0009] In one exemplary embodiment of this disclosure, before running the billing configuration script to bill the session to be processed, the method further includes: extracting preset keywords from the session messages of the session to be processed; performing a second verification on the billing configuration script based on the preset keywords, and returning the second verification result.

[0010] In one exemplary embodiment of this disclosure, the method further includes: if both the first verification and the second verification pass, running the billing configuration script to bill the session to be processed.

[0011] In one exemplary embodiment of this disclosure, the method further includes: determining whether the production source of the session management function terminal and the user plane function terminal is the same; the step of generating a billing configuration script based on the billing rules includes: when the production source of the session management function terminal and the user plane function terminal is the same, generating a billing configuration script for the session management function terminal and a billing configuration script for the user plane function terminal according to the billing rules and a standard configuration module; when the production source of the session management function terminal and the user plane function terminal is different, generating a billing configuration script for the session management function terminal according to the billing rules and a predefined configuration module for the production source of the session management function terminal, and generating a billing configuration script for the user plane function terminal according to the billing rules and a predefined configuration module for the production source of the user plane function terminal.

[0012] According to a second aspect of this disclosure, a session billing apparatus is provided, applied to a user plane function terminal, comprising: an identifier identification module, configured to acquire a session to be processed and identify a billing identifier in the session to be processed; a rule determination module, configured to determine a billing rule for the session to be processed based on the identification result of the billing identifier; a script generation module, configured to generate a billing configuration script based on the billing rule; and a script execution module, configured to run the billing configuration script to bill the session to be processed.

[0013] In one exemplary embodiment of this disclosure, the rule determination module includes: a first rule determination unit, configured to determine that the billing rule for the session to be processed is a static billing rule when the billing identifier is identified as a user plane identifier; and a second rule determination unit, configured to determine that the billing rule for the session to be processed is a dynamic billing rule when the billing identifier is identified as a control plane identifier.

[0014] In one exemplary embodiment of this disclosure, the script generation module includes: a first script generation unit, configured to generate a static billing configuration script from a preset static configuration template when the billing rule is a static billing rule; and a second script generation unit, configured to generate a dynamic billing configuration script from a preset dynamic configuration template when the billing rule is a dynamic billing rule.

[0015] In one exemplary embodiment of this disclosure, the session billing device further includes: a first verification module, configured to perform a first verification on the billing configuration script through a preset verification module before running the billing configuration script to bill the session to be processed, and return a first verification result.

[0016] In one exemplary embodiment of this disclosure, the session billing apparatus further includes: a second verification module, configured to extract preset keywords from the session messages of the session to be processed before running a billing configuration script to bill the session to be processed; perform a second verification on the billing configuration script based on the preset keywords, and return a second verification result.

[0017] In one exemplary embodiment of this disclosure, the session billing apparatus further includes a session billing module, configured to run a billing configuration script to bill the session to be processed if both the first and second verifications pass.

[0018] In one exemplary embodiment of this disclosure, the session billing apparatus further includes: a manufacturer determination module, configured to determine whether the production source of the session management function terminal and the user plane function terminal is the same; and a script generation module, including: a first determination unit, configured to generate a billing configuration script for the session management function terminal and a billing configuration script for the user plane function terminal according to billing rules and a standard configuration module when the production source of the session management function terminal and the user plane function terminal is the same; and a second determination unit, configured to generate a billing configuration script for the session management function terminal according to billing rules and a predefined configuration module of the production source of the session management function terminal, and generate a billing configuration script for the user plane function terminal according to billing rules and a predefined configuration module of the production source of the user plane function terminal when the production source of the session management function terminal and the user plane function terminal are different.

[0019] According to a third aspect of this disclosure, an electronic device is provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform the method described in any of the preceding methods by executing the executable instructions.

[0020] According to a fourth aspect of this disclosure, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the method described in any of the preceding claims.

[0021] The exemplary embodiments disclosed herein have the following beneficial effects:

[0022] The process involves acquiring a session to be processed and identifying the billing identifier within that session. Based on the identification result, the billing rules for the session are determined. A billing configuration script is generated based on the billing rules. The billing configuration script is then run to bill the session. On one hand, this exemplary embodiment proposes a novel session billing method. By identifying the billing identifier within the session, billing rules can be automatically determined. Corresponding billing configuration scripts can be quickly generated for sessions with different billing rules, enabling billing of the session without the need for manual analysis, thus saving manpower and time costs. On the other hand, this exemplary embodiment can adaptively generate billing configuration scripts based on billing rules, resulting in a simple, convenient, highly automated billing process with high accuracy.

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

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

[0025] Figure 1 This schematically illustrates a flowchart of a session billing method in this exemplary embodiment;

[0026] Figure 2 This diagram illustrates a flowchart of a session billing method in related technologies;

[0027] Figure 3 The diagram illustrates the architecture flowchart of a session billing method in related technologies.

[0028] Figure 4 This schematic diagram illustrates a structural block diagram of a session billing device in this exemplary embodiment;

[0029] Figure 5 This schematically illustrates the architecture flowchart of a session billing method in this exemplary embodiment;

[0030] Figure 6 This schematic diagram illustrates a structural block diagram of another session billing device in this exemplary embodiment;

[0031] Figure 7An electronic device for implementing the above method is illustrated in this exemplary embodiment. Detailed Implementation

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

[0033] Exemplary embodiments of this disclosure first provide a session billing method, which is described below in conjunction with the appendix. Figure 1 The exemplary embodiments will be further described as follows: Figure 1 As shown, the session billing method may include the following steps S110 to S140:

[0034] Step S110: Obtain the session to be processed and identify the billing identifier in the session to be processed.

[0035] The executing entity in this exemplary embodiment can be a UPF (User-Defined Function) terminal, which can first acquire the session to be processed. The session to be processed refers to a session that requires billing processing. In the application scenario of a 5G core network, the session to be processed can be a user PFCF (Packet Forwarding Control Protocol) session. Then, the billing identifier in the session to be processed can be identified. The billing identifier is a parameter identifier predefined in the session used to determine the billing rules.

[0036] This exemplary embodiment can establish a billing identifier in the session request of the pending session so that when the pending session is obtained, the billing identifier can be extracted from the pending session and identified. For example, UPF can establish a create URR (Create Billing Report Identifier) ​​in the session request for the user's PFCP session so that the billing identifier can be identified by identifying the create URR.

[0037] Step S120: Determine the billing rules for the session to be processed based on the identification result of the billing identifier.

[0038] The billing identifier identification result refers to the result of identifying which type of billing identifier is identified. In this exemplary embodiment, the billing identifier may include an UP (user plane) identifier or a CP (control plane) identifier. The identification result may be an UP identifier or a CP identifier, etc. Depending on the specific billing identifier settings, the identification result may also be represented by other identifiers. This exemplary embodiment is only for illustrative purposes and does not impose any specific limitations on it.

[0039] Based on the identification results, the billing rules for the session to be processed can be determined. In this exemplary embodiment, different billing identifiers can correspond to different billing rules. For example, the UP identifier can be set to correspond to a static billing rule. Then, when the identification result is the UP identifier, it can be determined that the session to be processed has a static billing identifier. Similarly, the CP identifier can correspond to a dynamic billing rule, etc.

[0040] Specifically, in an exemplary embodiment, step S120 may include:

[0041] When the billing identifier is identified as a user plane identifier, the billing rule for the session to be processed is determined to be a static billing rule;

[0042] When the billing identifier is identified as a control plane identifier, the billing rule for the session to be processed is determined to be a dynamic billing rule.

[0043] In this embodiment, the user plane identifier can be represented by UP, and the control plane identifier can be represented by CP. This exemplary embodiment can set a static billing rule corresponding to the user plane identifier. When the billing identifier is identified as a user plane identifier, the billing rule for the session to be processed can be determined to be a static billing rule. Similarly, a dynamic billing rule can be set to correspond to the control plane identifier. When the billing identifier is identified as a control plane identifier, the session to be processed can be determined to use a dynamic billing rule. A dynamic billing rule refers to a billing rule that can be dynamically updated based on time changes.

[0044] Step S130: Generate a billing configuration script based on the billing rules.

[0045] Here, a billing configuration script refers to an executable text written in a specific descriptive language according to a certain format. Different billing rules can generate different billing configuration scripts. Running the billing configuration script can execute the billing process for the pending session. This exemplary embodiment can adaptively generate billing configuration scripts according to billing rules, and can also automatically generate new billing configuration scripts in a timely manner according to the changed billing rules when billing rules change.

[0046] In this exemplary embodiment, the billing configuration script may include a billing configuration script for the UPF side and a billing configuration script for the SMF (Session Management Function). After generating the UPF billing configuration script and the SMF billing configuration script, the UPF side can also send the SMF billing configuration script to the SMF side when running the UPF billing configuration script, so that the SMF side can run the SMF billing configuration script and complete the billing process for the session to be processed.

[0047] Furthermore, in an exemplary embodiment, step S130 described above may include:

[0048] When the billing rule is a static billing rule, a static billing configuration script is generated from a preset static configuration template.

[0049] When the billing rule is a dynamic billing rule, a dynamic billing configuration script is generated from a preset dynamic configuration template.

[0050] In this exemplary embodiment, static billing rules and dynamic billing rules can correspond to different billing configuration scripts. When the billing rule for the session to be processed is a static billing rule, a static billing configuration script can be adaptively generated based on a built-in preset static configuration template. The preset static configuration template may include a variety of pre-configured static billing configuration scripts. By matching the current session to be processed, the corresponding static billing configuration script can be determined. When the billing rule for the session to be processed is a dynamic billing rule, a dynamic billing configuration script can be adaptively generated based on a preset dynamic configuration template. The preset dynamic configuration template may include a variety of pre-configured dynamic billing configuration scripts. By matching the current session to be processed, the corresponding dynamic billing configuration script can be determined.

[0051] Step S140: Run the billing configuration script to bill the session to be processed.

[0052] This exemplary embodiment can send the generated billing configuration script to the corresponding terminal, run the billing configuration script to complete the billing process for the session to be processed. For example, the generated SMF billing configuration script can be sent to the SMF terminal to run the SMF billing configuration script, and the generated UPF billing configuration script can be run on the UPF terminal.

[0053] Based on the above description, in this exemplary embodiment, a session to be processed is acquired, and a billing identifier in the session is identified; based on the identification result of the billing identifier, the billing rules for the session to be processed are determined; based on the billing rules, a billing configuration script is generated; and the billing configuration script is run to bill the session to be processed. On the one hand, this exemplary embodiment proposes a new session billing method, which can automatically determine the billing rules by identifying the billing identifier in the session to be processed. For sessions with different billing rules, corresponding billing configuration scripts can be quickly generated to realize the billing of the session to be processed without the need for manual analysis, saving manpower and time costs. On the other hand, this exemplary embodiment can adaptively generate billing configuration scripts based on billing rules, making the billing process simple, convenient, highly automated, and with high billing accuracy.

[0054] In an exemplary embodiment, prior to step S140, the session billing method may further include:

[0055] The pre-defined verification module performs the first verification on the billing configuration script and returns the first verification result.

[0056] To ensure the accuracy of session billing, this exemplary embodiment may also include a preset verification module, which may include a pre-set standard script. By matching the standard script in the verification module with the billing configuration script, a first verification can be performed on the generated billing configuration script to determine whether the billing configuration script is correct. The result of the first verification is the result of whether the generated billing configuration script passes the verification or whether the billing configuration script is correct. After obtaining the first verification result of the billing configuration script, the preset verification module can return it to the UPF end.

[0057] In an exemplary embodiment, prior to step S140, the session billing method may further include:

[0058] Extract preset keywords from the session messages of the session to be processed;

[0059] Based on preset keywords, a second verification is performed on the billing configuration script, and the second verification result is returned.

[0060] In addition to the first verification process described above, this exemplary embodiment may also include a mechanism for performing a second verification on the billing configuration script to further ensure the accuracy of the billing configuration script.

[0061] Specifically, this can begin by extracting preset keywords from the session messages of the session to be processed. For example, keywords from the private Information Element (IE) in the session messages can be extracted. These keywords identify the device manufacturer on the SMF side. By recognizing the keywords of the private IE, the SMF device manufacturer can be determined. Furthermore, a second verification can be performed on the billing configuration script based on the SMF device manufacturer's own script template. This avoids incompatibility issues caused by different manufacturers' varying levels of software compatibility and further ensures the accuracy of the script.

[0062] In one exemplary embodiment, the above session billing method may further include:

[0063] If both the first and second verifications pass, run the billing configuration script to bill the session to be processed.

[0064] In other words, the billing configuration script can only be run and billed for the pending session after the generated billing configuration script passes both the first and second checks mentioned above. This ensures the effectiveness of the billing configuration script and improves the billing accuracy of the pending session.

[0065] In one exemplary embodiment, the above session billing method may further include:

[0066] Determine whether the production source of the session management function and the user plane function is the same;

[0067] Based on the billing rules, a billing configuration script is generated, including:

[0068] When the production source of the session management function and the user plane function is the same, the billing configuration scripts for the session management function and the user plane function are generated according to the billing rules and the standard configuration module.

[0069] When the production sources of the session management function and the user plane function are different, the billing configuration script for the session management function is generated according to the billing rules and the predefined configuration module of the production source of the session management function, and the billing configuration script for the user plane function is generated according to the billing rules and the predefined configuration module of the production source of the user plane function.

[0070] Finally, this exemplary embodiment can also identify the production source of the SMF and UPF devices. The production source can be simply the manufacturer of the SMF or UPF devices. When it is determined that they are from the same manufacturer, the UPF billing configuration script and the SMF billing configuration script can be generated through the standard configuration module. When it is determined that they are from different manufacturers, the billing configuration script for the session management function can be generated according to the billing rules and the predefined configuration module of the manufacturer of the session management function, and the billing configuration script for the user plane function can be generated according to the billing rules and the predefined configuration module of the manufacturer of the user plane function.

[0071] Figure 2 A flowchart of a session billing method in the related technology is shown. The related technology relies on manual configuration for session billing, and specifically includes the following steps: Step S210, manual negotiation of billing rules for the UPF (User Plane Function), used to manually negotiate the billing rules used by the session to be processed; Step S220, configuration of billing rules for the SMF (Session Management Function) and UPF, used to configure the billing rules for the SMF and UPF; Step S230, modification of dynamic billing method for the SMF, used to manually modify the billing rules after the billing method is updated with static or dynamic rules; Step S240, configuration of billing rules for the SMF and UPF, used to reconfigure the billing rules for the SMF and UPF.

[0072] The specific architecture flowchart is as follows Figure 3As shown, it may include SMF 310, PCF (Policy Control Function) 320, CHF (Charging Function) 330, and UPF 340, and includes the following steps:

[0073] Step S311, SMF 310 requests a session charging policy from PCF 320; the session charging policy may include static charging rules or dynamic charging rules;

[0074] In step S312, SMF 310 requests CHF 330 to establish a billing session and requests a quota;

[0075] In step S313, after receiving the charging session establishment request and quota request sent by SMF 310, CHF 330 establishes a charging session and issues a quota.

[0076] Step S314: SMF 310 sends billing rules to UPF 340 for the PFCP session;

[0077] Step S315, UPF 340 reports the billing amount to SMF 310 for the PFCP session;

[0078] Step S316: SMF 310 reports the charge amount to CHF 330;

[0079] Step S317: CHF 330 issues a new billing quota to SMF 310;

[0080] Step S318: SMF 310 sends billing rules to UPF 340 for the PFCP session;

[0081] In step S319, UPF 340 reports the billing amount to SMF 310 for the PFCP session.

[0082] The billing methods of the aforementioned technologies cannot adaptively complete session billing according to the billing rules. When the user's billing rules change, the UPF needs to actively analyze the signaling to obtain the billing rules and regenerate the billing configuration, resulting in low billing efficiency.

[0083] Figure 4The diagram illustrates the modules of the session billing apparatus in this exemplary embodiment, which may include: an automatic billing rule identification module 410, used to identify billing identifiers and automatically determine billing rules; a billing configuration conversion module 420, used to generate a billing configuration script based on the billing rules; an automatic billing configuration distribution module 430, used to automatically distribute the billing configuration script to execute session billing; and a cross-vendor adaptation module 440, used to determine the manufacturers of the SMF and UPF devices, and when it is determined that the manufacturers of the SMF and UPF devices are different, to generate billing configuration scripts for the SMF manufacturer and the UPF manufacturer respectively.

[0084] Figure 5 This exemplary embodiment illustrates the interaction flowchart between various modules and the core network in a session charging method. The core network includes SMF, CHF, PCF, etc., and may specifically include:

[0085] In step S511, the core network 510 can automatically identify the billing identifier in the PFCP session through the billing rule automatic identification module 410, and determine the billing rule based on the identification result.

[0086] The billing configuration conversion module 420 is used to generate billing configuration scripts based on billing rules.

[0087] In step S512, the core network 510 can automatically send the billing configuration script to the SMF and UPF terminals through the billing configuration automatic distribution module 430;

[0088] In step S513, the core network 510 can determine the manufacturers of SMF and UPF through the cross-vendor adaptation module 440. When it is determined that the manufacturers of SMF and UPF end equipment are different, it generates billing configuration scripts for the SMF end manufacturer and the UPF end manufacturer respectively.

[0089] An exemplary embodiment of this disclosure also provides a session billing apparatus. (Refer to...) Figure 6 The device 600 is applied to the user plane function terminal and may include: an identifier identification module 610 for acquiring a session to be processed and identifying the billing identifier in the session to be processed; a rule determination module 620 for determining the billing rules for the session to be processed based on the identification result of the billing identifier; a script generation module 630 for generating a billing configuration script based on the billing rules; and a script execution module 640 for running the billing configuration script to perform billing for the session to be processed.

[0090] In an exemplary embodiment, the rule determination module includes: a first rule determination unit, configured to determine that the billing rule for the session to be processed is a static billing rule when the billing identifier is identified as a user plane identifier; and a second rule determination unit, configured to determine that the billing rule for the session to be processed is a dynamic billing rule when the billing identifier is identified as a control plane identifier.

[0091] In one exemplary embodiment, the script generation module includes: a first script generation unit, configured to generate a static billing configuration script from a preset static configuration template when the billing rule is a static billing rule; and a second script generation unit, configured to generate a dynamic billing configuration script from a preset dynamic configuration template when the billing rule is a dynamic billing rule.

[0092] In an exemplary embodiment, the session billing apparatus further includes: a first verification module, configured to perform a first verification on the billing configuration script through a preset verification module before running the billing configuration script to bill the session to be processed, and return a first verification result.

[0093] In an exemplary embodiment, the session billing apparatus further includes: a second verification module, configured to extract preset keywords from the session messages of the session to be processed before running the billing configuration script to bill the session to be processed; perform a second verification on the billing configuration script based on the preset keywords, and return a second verification result.

[0094] In one exemplary embodiment, the session billing apparatus further includes a session billing module, configured to run a billing configuration script to bill the session to be processed if both the first and second verifications pass.

[0095] In an exemplary embodiment, the session billing apparatus further includes: a manufacturer determination module, configured to determine whether the production sources of the session management function terminal and the user plane function terminal are the same; and a script generation module, comprising: a first determination unit, configured to generate a billing configuration script for the session management function terminal and a billing configuration script for the user plane function terminal according to billing rules and a standard configuration module when the production sources of the session management function terminal and the user plane function terminal are the same; and a second determination unit, configured to generate a billing configuration script for the session management function terminal according to billing rules and a predefined configuration module of the production source of the session management function terminal, and generate a billing configuration script for the user plane function terminal according to billing rules and a predefined configuration module of the production source of the user plane function terminal when the production sources of the session management function terminal and the user plane function terminal are different.

[0096] The specific details of each module / unit in the above-mentioned device have been described in detail in the embodiments of the method section. For any undisclosed details, please refer to the embodiments of the method section, and therefore will not be repeated here.

[0097] An exemplary embodiment of this disclosure also provides an electronic device capable of implementing the above-described method.

[0098] Those skilled in the art will understand that various aspects of this disclosure can be implemented as a system, method, or program product. Therefore, various aspects of this disclosure can be specifically implemented in the following forms: a completely hardware implementation, a completely software implementation (including firmware, microcode, etc.), or a combination of hardware and software aspects, collectively referred to herein as a "circuit," "module," or "system."

[0099] The following reference Figure 7 To describe an electronic device 700 according to such an exemplary embodiment of the present disclosure. Figure 7 The electronic device 700 shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments disclosed herein.

[0100] like Figure 7 As shown, the electronic device 700 is manifested in the form of a general-purpose computing device. The components of the electronic device 700 may include, but are not limited to: at least one processing unit 710, at least one storage unit 720, a bus 730 connecting different system components (including storage unit 720 and processing unit 710), and a display unit 740.

[0101] The storage unit stores program code, which can be executed by the processing unit 710 to perform the steps described in the "Exemplary Methods" section of this specification according to various exemplary embodiments of this disclosure. For example, the processing unit 710 can execute... Figure 1 or Figure 5 The steps shown are as follows.

[0102] Storage unit 720 may include a readable medium in the form of a volatile storage unit, such as random access memory (RAM) 721 and / or cache memory 722, and may further include a read-only memory (ROM) 723.

[0103] The storage unit 720 may also include a program / utility 724 having a set (at least one) of program modules 725, including but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of these examples may include an implementation of a network environment.

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

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

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

[0107] Exemplary embodiments of this disclosure also provide a computer-readable storage medium having a program product stored thereon capable of implementing the methods described above in this specification. In some possible implementations, various aspects of this disclosure may also be implemented as a program product including program code that, when the program product is run on a terminal device, causes the terminal device to perform the steps described in the "Exemplary Methods" section of this specification according to various exemplary embodiments of this disclosure.

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

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

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

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

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

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

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

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

[0116] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is defined only by the appended claims.

Claims

1. A session billing method, applied to a user plane function terminal, characterized in that, The method includes: Obtain the sessions to be processed and identify the billing identifiers in the sessions to be processed; Based on the identification result of the billing identifier, the billing rules for the session to be processed are determined; different billing identifiers correspond to different billing rules. Based on the aforementioned billing rules, a billing configuration script is generated; Run the billing configuration script to bill the pending session; The method further includes: Determine whether the production source of the session management function and the user plane function is the same; The step of generating a billing configuration script based on the billing rules includes: When the production source of the session management function terminal and the user plane function terminal is the same, the billing configuration script of the session management function terminal and the billing configuration script of the user plane function terminal are generated according to the billing rules and the standard configuration module. When the production source of the session management function terminal and the user plane function terminal are different, the billing configuration script of the session management function terminal is generated according to the billing rules and the predefined configuration module of the production source of the session management function terminal, and the billing configuration script of the user plane function terminal is generated according to the billing rules and the predefined configuration module of the production source of the user plane function terminal.

2. The method according to claim 1, characterized in that, The step of determining the billing rules for the session to be processed based on the identification result of the billing identifier includes: When the billing identifier is identified as a user plane identifier, the billing rule for the session to be processed is determined to be a static billing rule; When the billing identifier is identified as a control plane identifier, the billing rule for the session to be processed is determined to be a dynamic billing rule.

3. The method according to claim 2, characterized in that, The step of generating a billing configuration script based on the billing rules includes: When the billing rule is the static billing rule, a static billing configuration script is generated from a preset static configuration template; When the billing rule is the dynamic billing rule, a dynamic billing configuration script is generated from a preset dynamic configuration template.

4. The method according to claim 1, characterized in that, Before running the billing configuration script to bill the pending session, the method further includes: The billing configuration script is first verified by a preset verification module, and the first verification result is returned.

5. The method according to claim 4, characterized in that, Before running the billing configuration script to bill the pending session, the method further includes: Extract preset keywords from the session messages of the session to be processed; Based on the preset keywords, the billing configuration script is subjected to a second verification, and the second verification result is returned.

6. The method according to claim 5, characterized in that, The method further includes: If both the first and second verifications pass, the billing configuration script is run to bill the pending session.

7. A session billing device, applied to a user plane function terminal, characterized in that, The device includes: The identifier recognition module is used to acquire the session to be processed and identify the billing identifier in the session to be processed; The rule determination module is used to determine the billing rules for the session to be processed based on the identification result of the billing identifier; different billing identifiers correspond to different billing rules; The script generation module is used to generate a billing configuration script based on the billing rules; The script execution module is used to run the billing configuration script to bill the pending session; The device is also configured to: Determine whether the production source of the session management function and the user plane function is the same; The script generation module is configured as follows: When the production source of the session management function terminal and the user plane function terminal is the same, the billing configuration script of the session management function terminal and the billing configuration script of the user plane function terminal are generated according to the billing rules and the standard configuration module. When the production source of the session management function terminal and the user plane function terminal are different, the billing configuration script of the session management function terminal is generated according to the billing rules and the predefined configuration module of the production source of the session management function terminal, and the billing configuration script of the user plane function terminal is generated according to the billing rules and the predefined configuration module of the production source of the user plane function terminal.

8. An electronic device, characterized in that, include: processor; as well as Memory for storing the executable instructions of the processor; The processor is configured to execute the method of any one of claims 1-6 by executing the executable instructions.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method described in any one of claims 1-6.

Images