WO2020259116A1 - 一种计费系统、方法、存储介质及电子装置 - Google Patents

一种计费系统、方法、存储介质及电子装置 Download PDF

Info

Publication number
WO2020259116A1
WO2020259116A1 PCT/CN2020/090110 CN2020090110W WO2020259116A1 WO 2020259116 A1 WO2020259116 A1 WO 2020259116A1 CN 2020090110 W CN2020090110 W CN 2020090110W WO 2020259116 A1 WO2020259116 A1 WO 2020259116A1
Authority
WO
WIPO (PCT)
Prior art keywords
charging
service module
data
charging service
charging data
Prior art date
Application number
PCT/CN2020/090110
Other languages
English (en)
French (fr)
Inventor
陈启华
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2020259116A1 publication Critical patent/WO2020259116A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/64—On-line charging system [OCS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/65—Off-line charging system

Definitions

  • This application relates to the field of communications, and in particular to a charging system, method storage medium and electronic device.
  • the billing domain in the 2/3/4G period mainly relies on the offline charging system (Offline Charging System) and the online charging system (Online Charging System) to complete the billing;
  • the fee structure has many interfaces and the billing process is cumbersome.
  • CCS Converged Online Offline Charging System
  • 5G adopts a new converged offline and online billing system CCS (Converged Online Offline Charging System) to complete billing, simplifying the interface, but on 2/3/
  • CDF Charging Data Function
  • CDR Charging Data Record
  • this 5G converged billing system uses a single Nchf converged and online billing interface, and there is no corresponding solution when the CCS is abnormal.
  • the CCS abnormality here does not only refer to the network abnormality. , It also includes abnormal situations such as insufficient CCS performance, network attacks, and virus outbreaks that cause the entire Billing Domain to be paralyzed; on the other hand, because CCS integrates ABMF and RF functions, it is necessary to query the rate and deduct the user’s balance (or package).
  • the entire CCS will be implemented in the Billing Domain, so the charging data function (CDF) that can generate bills in CCS will also be implemented in the Billing Domain, so the CDF/CGF function is lacking in the network domain.
  • CDF charging data function
  • the network domain will not be able to provide bills for billing domain verification; in addition, the construction cost of CCS is high, and this billing system is not acceptable to operators.
  • the embodiments of the present application provide a charging system, method storage medium, and electronic device.
  • a charging system including: a first charging service module and a network function module, wherein the first charging service module and the network function module are both set in the network domain, and the network function module After the resource is delivered, the first charging data is reported to the first charging service module through the first service interface, the first charging data is used to indicate the usage of the resource; the first charging service module receives the first charging data , The first charging data is used for charging domain charging.
  • a charging method which includes: after the network function module delivers the resource, reporting first charging data to the first charging service module through a first service interface, and A charging data is used to indicate the usage of the resource, wherein the first charging service module and the network function module are both set in the network domain; the first charging service module receives the first accounting Charge data, the first charging data is used for charging domain charging.
  • a storage medium in which a computer program is stored, wherein the computer program is configured to execute the steps in any one of the foregoing method embodiments when running.
  • an electronic device including a memory and a processor, the memory is stored with a computer program, and the processor is configured to run the computer program to execute any of the above Steps in the method embodiment.
  • Fig. 1 is a structural block diagram of a charging system according to an embodiment of the present application
  • FIG. 2 is a flowchart of a charging method according to an embodiment of the present application.
  • Figure 3 is a 5G online charging function OCHF architecture diagram according to an optional embodiment of the present application.
  • Fig. 4 is a 5G offline charging function OFCHF architecture diagram according to an optional embodiment of the present application.
  • FIG. 5 is a schematic diagram of using 5G online charging query service according to an optional embodiment of the present application.
  • FIG. 6 is a schematic diagram of using 5G offline charging query service according to an optional embodiment of the present application.
  • FIG. 7 is a schematic diagram of using a 5G offline charging query service according to an optional embodiment of the present application.
  • Fig. 8 is a structural block diagram of a charging system according to an optional embodiment of the present application.
  • Fig. 9 is an architecture diagram of simultaneous deployment of OCHF and OFCHF in 5G according to an optional embodiment of the present application (NF integrated CTF);
  • FIG. 10 is an architecture diagram of simultaneous deployment of OCHF and OFCHF in 5G according to an optional embodiment of the present application (NF integrated CTF&CDF);
  • Figure 11 is a schematic diagram of switching from online charging to offline charging when 5G OCHF is abnormal according to an optional embodiment of the present application (NF integrated CTF);
  • Fig. 12 is a schematic diagram of switching from online charging to offline charging when 5G OCHF is abnormal according to an optional embodiment of the present application (NF integrated CTF&CDF);
  • Fig. 13 is a flowchart of a 5G online charging method according to an optional embodiment of the present application.
  • FIG 14 is a flowchart of a 5G offline charging method according to an optional embodiment of the present application (NF integrated CTF);
  • FIG. 15 is a flowchart of a 5G offline charging method according to an optional embodiment of the present application (NF integrated CDF);
  • Fig. 16 is a flowchart of an offline charging billing method consistent with an online charging session according to an optional embodiment of the present application (NF integrated CTF);
  • Fig. 17 is a flowchart of an offline charging billing method that is consistent with an online charging session according to an optional embodiment of the present application (NF integrated CTF&CDF);
  • FIG. 18 is a flowchart of a method for converting online charging to offline charging when OCHF is abnormal according to an optional embodiment of the present application (NF integrated CTF);
  • FIG. 19 is a flowchart of a method for converting online charging to offline charging when OCHF is abnormal according to an optional embodiment of the present application (NF integrated CTF&CDF);
  • FIG. 20 is a flowchart of a method for preventing double charging when NF sends charging requests to multiple sets of OCHF according to an optional embodiment of the present application (OCHF1 has been deducted);
  • FIG. 21 is a flowchart of a method for preventing double charging when NF sends charging requests to multiple sets of OCHF according to an optional embodiment of the present application (OCHF1 is not deducted);
  • FIG. 22 is a flowchart of a method for preventing duplicate bills from being generated when the NF (CTF) transmits offline charging information to multiple sets of OFCHF according to an optional embodiment of the present application (OFCHF1 has been stored);
  • FIG. 23 is a flowchart of a method for preventing duplicate bills when NF (CTF) transmits offline charging information to multiple sets of OFCHF according to an optional embodiment of the present application (OFCHF1 is not stored);
  • FIG. 24 is a flowchart of a method for preventing duplicate bills from being generated when the NF (CDF) transmits offline charging information to multiple OFCHFs according to an optional embodiment of the present application (OFCHF1 has been stored);
  • 25 is a flowchart of a method for preventing duplicate bills from being generated when the NF (CDF) transmits offline charging information to multiple sets of OFCHF according to an optional embodiment of the present application (OFCHF1 is not stored).
  • FIG. 1 is a structural block diagram of a charging system according to an embodiment of the present application. As shown in FIG. 1, the system includes:
  • the first charging service module and the network function module wherein the first charging service module and the network function module are both set in the network domain, and the network function module reports the first charging data to the first service interface after delivering the resource
  • the first billing service module where the first billing data is used to indicate resource usage
  • the first charging service module receives first charging data, and the first charging data is used for charging domain charging.
  • the first charging service module Since the first charging service module and the network function module are both set in the network domain, the first charging service module receives and stores the first charging data, so the first charging service module can provide the charging data for the charging domain Billing or data checking can effectively prevent the billing system from being unable to bill after an abnormality occurs in the billing system. Therefore, it can solve some problems existing in the billing system in related technologies and achieve the effect of improving the stability of the billing system.
  • the first charging data is reported to the first charging service module through the first service interface, and the first charging service module receives the first charging data, including:
  • the network function module reports the updated part of the first charging data to the first charging service module through the first service interface according to the usage of the resources; the first charging service module receives part of the first charging data and reports it according to the part of the first charging data.
  • the charge data updates the first charge data previously received; or,
  • the network function module updates the first charging data according to the resource usage, and reports the updated first charging data to the first charging service module through the first service interface; after the first charging service module receives the update The first billing data.
  • the system further includes:
  • the network function module When the network function module does not receive the first response fed back by the first charging service module, it marks the first charging data and reports it to the second charging service module, where the first response is used to indicate the first charging service The module successfully receives the first charging data;
  • the second charging service module receives the marked first charging data.
  • the system further includes:
  • the second charging service module temporarily stores the marked first charging data
  • the second charging service module sends a query request to the first charging service module, where the query request is used to query whether the first charging service module stores first charging data consistent with the marked first charging data;
  • the second charging service module When the second charging service module receives the query failure response sent by the first charging service module, it stores the marked first charging data.
  • the system further includes:
  • the second charging service module creates an initial first charging data record
  • the second charging service module sends a query request to the first charging service module, where the query request is used to query whether the first charging service module stores first charging data consistent with the marked first charging data;
  • the second charging service module When the second charging service module receives the query failure response sent by the first charging service module, it updates the initial first charging data record according to the marked first charging data, and stores the updated initial first charging data record.
  • the above process can also prevent the generation of duplicate billing data.
  • the system further includes a third charging service module, wherein the third charging service module is set in the charging domain, and the network function module sends a resource request to the third charging service module through the second service interface;
  • the third charging service module issues a resource quota to the network function module according to the preset resource quota;
  • the network function module receives the resource quota and delivers resources according to the resource quota.
  • system further includes:
  • the third charging service module performs pricing and/or withholding fees according to the received resource request.
  • the network function module after the network function module delivers the resource, it reports the second charging data to the first charging service module through the first service interface.
  • the first charging service module receives the second charging data
  • the second charging service module receives the second charging data.
  • Fee data is used to indicate the usage of resources.
  • the network function module reports the second charging data to the first charging service module through the first service interface, and the first charging service module receives the second charging data, including:
  • the network function module reports the updated part of the second billing data to the first billing service module through the first service interface according to the resource usage; the first billing service module receives part of the second billing data and calculates according to the part of the second billing data.
  • the charge data updates the previously received second charge data; or,
  • the network function module updates the second charging data according to the resource usage, and reports the updated second charging data to the first charging service module through the first service interface; after the first charging service module receives the update The second billing data.
  • the system further includes:
  • the network function module When the network function module does not receive the second response from the third charging service module, it marks the resource request and reports it to the fourth charging service module, where the second response is used to indicate that the third charging service module successfully received Resource request
  • the fourth charging service module receives the marked resource request and issues a resource quota to the network function module according to the preset resource quota.
  • the system further includes:
  • the third charging service module withholds fees according to the received marked resource request
  • the fourth charging service module sends a fee deduction query request to the third charging service module
  • the fourth charging service module When the fourth charging service module receives the non-deduction response fed back by the third charging service module, the fourth charging service module deducts fees according to the received marked resource request.
  • the system further includes:
  • the network function module When the network function module does not receive the second response fed back by the third charging service module, it marks the current charging data and reports it to the first charging service module, where the second response is used to indicate the third charging service module Successfully received the resource request;
  • the first charging service module receives the marked current charging data and stores the marked current charging data.
  • This embodiment also provides a charging method. As shown in FIG. 2, the method includes:
  • the network function module After delivering the resource, the network function module reports the first charging data to the first charging service module through the first service interface, where the first charging data is used to indicate the usage of the resource, where the first charging service Both the module and the network function module are set in the network domain;
  • the first charging service module receives first charging data, where the first charging data is used for charging domain charging.
  • the first charging service module and the network function module are both set in the network domain, and the first charging service module receives and stores the first charging data, the first charging service module can provide the calculation
  • the fee data is used for billing in the billing domain or checking the data, which can effectively prevent the billing system from being unable to bill after the billing system is abnormal. Therefore, it can solve some problems existing in the billing system in related technologies and achieve higher billing The effect of system stability.
  • the first charging data is reported to the first charging service module through the first service interface, and the first charging service module receives the first charging data, including:
  • the network function module reports the updated part of the first charging data to the first charging service module through the first service interface according to the usage of the resources; the first charging service module receives part of the first charging data and reports it according to the part of the first charging data.
  • the charge data updates the first charge data previously received; or,
  • the network function module updates the first charging data according to the resource usage, and reports the updated first charging data to the first charging service module through the first service interface; after the first charging service module receives the update The first billing data.
  • the method further includes:
  • the network function module When the network function module does not receive the first response fed back by the first charging service module, it marks the first charging data and reports it to the second charging service module, where the first response is used to indicate the first charging service The module successfully receives the first charging data;
  • the second charging service module receives the marked first charging data.
  • the method further includes:
  • the second charging service module temporarily stores the marked first charging data
  • the second charging service module sends a query request to the first charging service module, where the query request is used to query whether the first charging service module stores first charging data consistent with the marked first charging data;
  • the second charging service module When the second charging service module receives the query failure response sent by the first charging service module, it stores the marked first charging data.
  • the method further includes:
  • the second charging service module creates an initial first charging data record
  • the second charging service module sends a query request to the first charging service module, where the query request is used to query whether the first charging service module stores first charging data consistent with the marked first charging data;
  • the second charging service module When the second charging service module receives the query failure response sent by the first charging service module, it updates the initial first charging data record according to the marked first charging data, and stores the updated initial first charging data record.
  • the method further includes:
  • the network function module sends a resource request to the third charging service module through the second service interface, where the third charging service module is set in the charging domain;
  • the third charging service module issues a resource quota to the network function module according to the preset resource quota;
  • the network function module receives the resource quota and delivers resources according to the resource quota.
  • the method further includes:
  • the third charging service module performs pricing and/or withholding fees according to the received resource request.
  • the network function module after the network function module delivers the resource, it reports the second charging data to the first charging service module through the first service interface.
  • the first charging service module receives the second charging data
  • the second charging service module receives the second charging data.
  • Fee data is used to indicate the usage of resources.
  • the network function module reports the second charging data to the first charging service module through the first service interface, and the first charging service module receives the second charging data, including:
  • the network function module reports the updated part of the second billing data to the first billing service module through the first service interface according to the resource usage; the first billing service module receives part of the second billing data and calculates according to the part of the second billing data.
  • the charge data updates the previously received second charge data; or,
  • the network function module updates the second charging data according to the resource usage, and reports the updated second charging data to the first charging service module through the first service interface; after the first charging service module receives the update The second billing data.
  • the method further includes:
  • the network function module When the network function module does not receive the second response from the third charging service module, it marks the resource request and reports it to the fourth charging service module, where the second response is used to indicate that the third charging service module successfully received Resource request
  • the fourth charging service module receives the marked resource request and issues a resource quota to the network function module according to the preset resource quota.
  • the method further includes:
  • the third charging service module withholds fees according to the received marked resource request
  • the fourth charging service module sends a fee deduction query request to the third charging service module
  • the fourth charging service module When the fourth charging service module receives the non-deduction response fed back by the third charging service module, the fourth charging service module deducts fees according to the received marked resource request.
  • the method further includes:
  • the network function module When the network function module does not receive the second response fed back by the third charging service module, it marks the current charging data and reports it to the first charging service module, where the second response is used to indicate the third charging service module Successfully received the resource request;
  • the first charging service module receives the marked current charging data and stores the marked current charging data.
  • the method according to the above embodiment can be implemented by means of software plus the necessary general hardware platform, of course, it can also be implemented by hardware, but in many cases the former is Better implementation.
  • the technical solution of this application essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, The optical disc) includes a number of instructions to enable a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the method of each embodiment of the present application.
  • the optional implementation of this application adds a new online charging function OCHF (Online Charging Function) and an offline charging function OFCHF (Offline Charging Function), and proposes a more advanced and effective method of charging repetition based on the service architecture. It not only enriches the implementation of 5G billing, but also greatly reduces the complexity of the billing repetition process, meets the requirements of more operators in deploying 5G billing, and proposes a new 5G billing implementation.
  • OCHF Online Charging Function
  • OFCHF Offline Charging Function
  • Offline Charging mainly means that the user first uses network resources and generates corresponding billing bills by CDF (Charging Data Function), and then encodes the billing bills through CGF (Charging Gateway Function).
  • CDF Charging Data Function
  • CGF Charging Gateway Function
  • the bill file is transferred to the Billing System of the Billing Domain to complete the billing. Because the function of billing according to bills is completed in the Billing System of the Billing Domain, and the main functions of CDF and CGF are to generate bills or bill files, and are not responsible for charging users, CDF and CGF can be implemented on the network side.
  • Online Charging is mainly: when a user needs to use network resources, the CTF (Charging Trigger Function) on the network side first applies for a quota (usually used time or amount) from the online charging service, only when the user's balance ( Or package) is sufficient, the application will be successful and the user can start using the network.
  • the online billing service integrates rating, deduction functions, account balance management, rate management and other similar functions, it is necessary to query the rate and deduct the user's balance (or package), so the online billing service can be implemented in Billing Domain .
  • Offline Charging Bill CDR Charging Data Record generated based on the usage of network resources, which mainly includes user identification (IMSI, etc.), start and end time of using network resources, usage, etc. Since CDR is generated, it means that the user has used a certain amount of network resources, so CDR generally refers to offline billing bills, which can be used in scenarios such as offline billing, inter-network settlement, business analysis, and statistics.
  • Prepaid users refer to users who recharge first and then use the network.
  • the object of online charging generally refers to prepaid users. Prepaid users will also generate call bills. Call bills generated by prepaid users are also called offline call bills. Note: The object of online billing can also be post-paid users. If there is no balance in the post-paid account, you can first book the account and then settle the bill at the end of the month.
  • Post-paid users refers to users who can use the network first and then bill. Such users generally go through the offline billing process (it is not necessary to go through the online billing process because it is impossible to deduct fees in real time).
  • OCHF equivalent to the third charging service module in the above embodiment
  • OFCHF equivalent to the first charging service module in the above embodiment
  • SBI Service-based interface
  • each NF equivalent to the network function module in the above-mentioned embodiment
  • the interface name is Rickf (equivalent to the second service interface in the above embodiment) (Service-based interface exhibited by OCHF).
  • Rickf provides 2 services externally:
  • OFCHF as the unified export of the 5G core network for externally outputting offline bills, can be connected to one or more NFs for bill collection and reporting.
  • OFCHF uses SBI-based communication with each NF, and the interface name is Nofchf (equivalent to the above embodiment The first service interface) (Service-based interface exhibited by OFCHF).
  • Nofchf provides 4 external services:
  • Nofchf_ChargingDataService is responsible for collecting and processing offline charging messages of each NF (CTF): Charging Data Request and generating offline bills;
  • Nofchf_CDRStorageService is responsible for collecting and processing each NF (CDF) CDR message: CDR Request;
  • Nofchf_ChargingDataQueryService is responsible for querying the ChargingDataRequest messages that have been saved locally;
  • Nofchf_CDRQueryService is responsible for querying the offline charging CDRs that have been saved locally.
  • Oakf_ChargingService is responsible for receiving and processing the Online Charging Request message of each NF, calling RF according to the information of the service used by the (prepaid) user to complete the rating, and then calling ABMF according to the result of the rating to determine whether to pre-authorize the user ; If the user's account balance is sufficient, Rickf_ChargingService responds to NF to obtain pre-authorization success.
  • Nofchf_ChargingDataService is responsible for collecting the Charging Data Request messages of each NF (CTF) and generating offline CDRs; or Nofchf_CDRStorageService is responsible for collecting the CDR Request messages of each NF (CDF) and generating offline CDRs, and the CDRs pass through After merging, sorting, filtering, encoding, etc., it is stored locally, and finally the bill file is reported to the Billing System of Billing Domain through the Bx interface.
  • the service consumer sends a charging query request to Rickf_ChargingQueryService.
  • the request message carries but is not limited to: user identification IMSI, charging start time StartTime, charging end time EndTime (optional), and charging duration (optional) Optional), session identifier ChargingID, sequence number of the charging part, SequenceNumber (optional, if a session is divided into multiple Charging Requests, each Charging Request should have an increasing sequence number), NF-Address and other keywords; OCHF( Rickf_ChargingQueryService)
  • After receiving the query request if the corresponding Online Charging Request is found locally, it returns Debited.
  • the returned message can also carry the complete or partial Online Charging Request content, including the deducted fee or package balance. If the corresponding Online Charging Request message cannot be found locally, NoDebited will be returned.
  • the service consumer sends a charging query request to Nofchf_ChargingDataQueryService.
  • the request message carries but is not limited to: user identification IMSI, charging start time StartTime, charging end time EndTime (optional), and charging duration (optional) Optional), session identifier ChargingID, sequence number of the charging part, SequenceNumber (optional, if a session is divided into multiple Charging Data Requests, each Charging Data Request should have an increasing sequence number), NF-Address and other keywords;
  • OCHF Nofchf_ChargingDataQueryService
  • receives the query request if it finds the corresponding Charging Data Request locally, it returns Success.
  • the returned message can also carry the complete or partial Charging Data Request content.
  • Unsuccess will be returned. If there is a Charging Data Request of the previous sequence number for the session, the Unsuccess will be returned with the Charging Data Request message of the previous sequence number to facilitate other OFCHF supplements Generate bills (for details, please refer to optional implementations).
  • the service consumer sends a CDR query request to Nofchf_CDRQueryService.
  • the request message carries but is not limited to: user identification IMSI, charging start time StartTime, charging end time EndTime (optional), charging duration, and session Identifies the ChargingID, the sequence number of the charging part, the SequenceNumber (optional, if multiple part CDRs are output in one session, each part of the CDR should have an incremental sequence number), keywords such as NF-Address; OCHF (Nofchf_CDRQueryService) receives After the query request, if the corresponding CDR is found locally, Success will be returned. The returned message can also carry a complete or partial CDR. If the corresponding CDR cannot be found locally, Unsuccess is returned.
  • OFCHF is a unified export of one or more NFs that require offline charging to perform charging output.
  • the CGF function of OFCHF supports long-term storage of bills locally, which can effectively provide billing files for Billing Domain for a long time.
  • Fig. 8 is a structural block diagram of a charging system according to an optional embodiment of the present application.
  • the charging system simultaneously deploys an online charging service function (equivalent to the third charging service module in the above embodiment) and Offline charging service function (equivalent to the first charging service module in the above embodiment), and the two are respectively connected to NFs (equivalent to the network function module in the above embodiment) through a service-oriented interface.
  • an online charging service function equivalent to the third charging service module in the above embodiment
  • NFs equivalent to the network function module in the above embodiment
  • Figure 9 and Figure 10 in the scenario where OCHF and OFCHF are deployed at the same time, the method of the embodiment of the application can make the bill generated by OFCHF and OCHF completely consistent. Because of this, OCHF does not need to implement CDF and CGF functions.
  • the OCHF deduction of user fees can also be brought to OFCHF through an optional implementation of this application, so that OFCHF
  • the generated bills also have the ability to include information such as expenses.
  • OFCHF as a relatively stable function can be placed on the network Realization on the side. Since the CGF of OFCHF stores bills within a certain time range, in the future, when a billing exception occurs, the network side can provide a bill for checking with the Billing Domain.
  • OCHF/CCS is greatly affected by the parameters of user balance, package, and tariff, and can be implemented on the Billing Domain side. It is very possible that NF and OCHF/CCS are not the same manufacturer’s equipment, even if they are from the same manufacturer. It may also not be in the same network; therefore, when NF communicates with OCHF/CCS, it needs to fully consider OCHF/CCS abnormal scenarios, as shown in Figure 11 and Figure 12.
  • the optional embodiments of this application are in OCFH/CCS or even the entire Billing Domain
  • OFCHF can generate offline CDR files by transferring online to offline, which can be obtained by Billing System at any time and used for billing.
  • part of the call bill or the complete call bill in the offline charging step is equivalent to the first charging data in the foregoing embodiment;
  • the online charging request in the online charging step is equivalent to the foregoing The second charging data in the embodiment;
  • the response of the offline charging service function in the offline charging step is equivalent to the first response in the above embodiment;
  • the response of the online charging service function in the online charging step is equivalent to the above The second response in the embodiment.
  • the optional embodiment of this application can meet the requirement that some operators only want to establish an offline charging system, and also meet the requirements of some operators who want to continue to use the existing offline charging system or separate and separate charging systems from online; Operators have saved the cost of establishing a new converged billing system CCS.
  • an embodiment of the present application proposes a more advanced online charging method based on the service architecture, which provides a method to prevent double charging when the NF sends charging requests to multiple sets of OCHF. mechanism.
  • an embodiment of the present application proposes a more advanced offline charging transmission method based on the service architecture, and provides that when NF (CTF) transmits offline charging information to multiple OFCHFs, A mechanism to prevent duplicate bills.
  • CTF NF
  • the embodiment of the present application proposes a more advanced offline charging transmission method based on the service architecture, which simplifies the transmission of offline charging information through the Ga port in the 2/3/4G period.
  • the complex process provides a mechanism to prevent duplicate bills when the NF (CDF) transmits offline charging information to multiple OFCHFs.
  • the 5G online charging steps in this embodiment of the application are as follows:
  • Step S01 The user requests to use network resources.
  • Step S02 NF (CTF) estimates the amount of resources to be used.
  • Step S03 NF (CTF) sends an online charging request to OCHF (Nochf_ChargingService).
  • Step S04 OCHF (Nochf_ChargingService) calls ABMF, and RF calculates the amount allowed to be used by the user.
  • Step S05 OCHF (Nochf_ChargingService) delivers the amount to NF (CTF).
  • Step S06 The NF (CTF) delivers the available network usage to the user.
  • Step S07 When a quota management trigger arrives (for example, tariff switching), *[quota management process] is triggered, and * indicates that the process can be triggered multiple times.
  • a quota management trigger arrives (for example, tariff switching)
  • *[quota management process] is triggered
  • Step S08 NF (CTF) estimates the amount of resources to be used subsequently, and reports the amount already used by the user.
  • Step S09 OCHF (Nochf_Charging Service) deducts the user fee (or package balance) according to the amount already used by the user, and calls ABMF, and RF calculates the amount that the user is allowed to continue to use.
  • OCHF Nochf_Charging Service
  • Step S10 OCHF (Nochf_Charging Service) delivers the usage to NF (CTF).
  • Step S11 The NF (CTF) delivers the network usage that can be used continuously to the user.
  • Step S12 The process of the network used by the user this time ends, and the current session is released.
  • Step S13 The NF (CTF) sends an online charging request to release the session to the OCHF (Nochf_ChargingService), and reports the amount used by the user.
  • CTF CTF
  • Step S14 OCHF (Nochf_Charging Service) deducts the user fee (or the balance of the package) according to the amount used by the user.
  • OCHF Nochf_Charging Service
  • Step S15 OCHF (Nochf_ChargingService) sends a response message to NF (CTF) to inform the user that the fee deduction is successful.
  • CTF NF
  • the 5G offline charging steps in the embodiment of the present application are as follows, where the CTF function is integrated on the NF,
  • Step S01A NF (CTF) sends an initial charging data request to OFCHF (Nofchf_ChargingDataService).
  • Step S01B OFCHF (Nofchf_ChargingDataService) creates a new bill.
  • Step S01C OFCHF (Nofchf_ChargingDataService) sends a response to NF (CTF).
  • Step S01 NF (CTF) estimates the amount of resources to be used and delivers it directly to the user (Note: This step does not need to wait for S01A/B/C.. to complete. If OFCHF does not respond, the message should be cached locally in NF, as follows For steps similar to A/B/C.., please refer to this instruction uniformly).
  • Step S02 When the usage reporting management trigger arrives (for example, regular reporting), *[Usage reporting process] is triggered, and * indicates that the process can be triggered multiple times.
  • the usage reporting management trigger arrives (for example, regular reporting)
  • *[Usage reporting process] is triggered
  • Step S03A NF (CTF) sends a request for updating charging data to OFCHF (Nofchf_ChargingDataService).
  • Step S03B OFCHF (Nofchf_ChargingDataService) updates the content of the call bill, such as the accumulation of traffic or time, and can also output part of the call bill according to the condition of part of the bill issuance (for example, bill issued by time or bill by flow).
  • OFCHF Nofchf_ChargingDataService
  • Step S03C OFCHF (Nofchf_ChargingDataService) sends a response to NF (CTF).
  • Step S03 NF (CTF) estimates the amount of resources that need to be used subsequently, and directly delivers to users for use.
  • Step S04 The process of the network used by the user this time ends, and the current session is released.
  • Step S05A NF (CTF) sends a request for ending charging data to OFCHF (Nofchf_ChargingDataService).
  • Step S05B OFCHF (Nofchf_ChargingDataService) updates the bill content, such as the accumulation of traffic or time, and closes the bill.
  • OFCHF Nofchf_ChargingDataService
  • Step S05C OFCHF (Nofchf_ChargingDataService) sends a response to NF (CTF): closing the bill.
  • Step S05D OFCHF generates a bill file, and sends the bill file to Billing System through the Bx port.
  • the 5G offline charging steps in the embodiment of the present application are as follows, where NF integrates CDF.
  • Step S01A The NF (CDF) creates a new CDR (Open CDR) locally.
  • Step S01 NF (CDF) estimates the amount of resources to be used and directly delivers to users for use.
  • Step S02 When the usage reporting management trigger arrives (for example, regular reporting), *[Usage reporting process] is triggered, and * indicates that the process can be triggered multiple times.
  • the usage reporting management trigger arrives (for example, regular reporting)
  • *[Usage reporting process] is triggered
  • Step S03A NF (CDF) updates the content of the call bill, such as the accumulation of traffic or time, and can also generate part of the call bill locally based on the condition of issuing a bill by part of the bill (for example, billing by time or billing by traffic).
  • CDF updates the content of the call bill, such as the accumulation of traffic or time, and can also generate part of the call bill locally based on the condition of issuing a bill by part of the bill (for example, billing by time or billing by traffic).
  • Step S03B NF (CDF) sends a bill to OFCHF (Nofchf_CDRStorageService).
  • Step S03C OFCHF (Nofchf_CDRStorageService) receives and stores the CDR (or sends it to the CGF Dialog for processing).
  • Step S03D OFCHF (Nofchf_CDRStorageService) sends a response message.
  • Step S03 NF estimates the amount of resources to be used subsequently, and directly delivers to users for use.
  • Step S04 The process of the network used by the user this time ends, and the current session is released.
  • Step S05A NF (CDF) generates the last partial bill locally.
  • Step S05B NF (CDF) sends a bill to OFCHF (Nofchf_CDRStorageService).
  • Step S05C OFCHF (Nofchf_CDRStorageService) receives and stores the CDR (or sends it to the CGF Dialog for processing).
  • Step S05D OFCHF (Nofchf_CDRStorageService) sends a response message.
  • Step S05E OFCHF (Nofchf_CDRStorageService) generates a bill file, and sends the bill file to Billing System through the Bx port.
  • OFCHF Nofchf_CDRStorageService
  • the offline charging billing step that is consistent with the online charging session in the embodiment of the present application, in which NF integrates CTF.
  • Step S01 The user requests to use network resources.
  • Step S02 NF (CTF) estimates the amount of resources to be used.
  • Step S03 NF (CTF) sends an online charging request to OCHF (Nochf_ChargingService).
  • Step S04 OCHF (Nochf_ChargingService) calls ABMF, and RF calculates the amount allowed to be used by the user.
  • Step S05 OCHF (Nochf_ChargingService) delivers the amount to NF (CTF).
  • Step S06A NF (CTF) sends an initial charging data request to OFCHF (Nofchf_ChargingDataService).
  • Step S06B OFCHF (Nofchf_ChargingDataService) creates a new CDR (Open CDR).
  • Step S06C OFCHF (Nofchf_ChargingDataService) sends a response to NF (CTF).
  • Step S06 The NF (CTF) delivers the available network usage to the user.
  • Step S07 When the usage reporting management trigger arrives (for example, regular reporting), *[Usage reporting process] is triggered, and * indicates that the process can be triggered multiple times.
  • the usage reporting management trigger arrives (for example, regular reporting)
  • *[Usage reporting process] is triggered
  • Step S08A NF (CTF) sends a request for updating charging data to OFCHF (Nofchf_ChargingDataService).
  • Step S08B OFCHF (Nofchf_ChargingDataService) updates the bill content, such as the accumulation of traffic or time, and can also output part of the bill according to the condition of issuing a bill by part of the bill (for example, billing by time or billing by flow).
  • OFCHF Nofchf_ChargingDataService
  • Step S08C OFCHF (Nofchf_ChargingDataService) sends a response to NF (CTF).
  • Step S08 NF (CTF) estimates the amount of resources to be used subsequently (but not exceeding the amount issued by OCHF), and directly delivers to users for use.
  • CTF CTF
  • Step S09 When the quota management trigger arrives (for example, tariff switching), *[quota management process] is triggered, and * indicates that the process can be triggered multiple times.
  • the quota management trigger arrives (for example, tariff switching), *[quota management process] is triggered, and * indicates that the process can be triggered multiple times.
  • Step S10 NF (CTF) estimates the amount of resources to be used subsequently, and reports the amount already used by the user.
  • Step S11 OCHF (Nochf_Charging Service) deducts the user fee (or package balance) according to the amount already used by the user, and calls ABMF, and RF calculates the amount that the user is allowed to continue to use.
  • OCHF Nochf_Charging Service
  • Step S12 OCHF (Nochf_ChargingService) delivers the amount to NF (CTF).
  • Step S13A NF (CTF) sends a request for updating charging data to OFCHF (Nofchf_ChargingDataService).
  • Step S13B OFCHF (CDF) updates the call bill content, such as the accumulation of traffic or time, and can also output part of the call bill according to the condition of part of the bill issuance (for example, bill is issued by time or by flow).
  • CDF OFCHF
  • Step S13C OFCHF (Nofchf_ChargingDataService) sends a response to NF (CTF).
  • Step S13 The NF (CTF) delivers the network usage that can be used continuously to the user.
  • Step S14 The process of the network used by the user this time ends, and the current session is released.
  • Step S15A The NF (CTF) sends a request for ending charging data to OFCHF (Nofchf_ChargingDataService).
  • Step S15B OFCHF (Nofchf_ChargingDataService) updates the bill content, such as the accumulation of traffic or time, and closes the bill.
  • OFCHF Nofchf_ChargingDataService
  • Step S15C OFCHF (Nofchf_ChargingDataService) sends a response to NF (CTF): closing the bill.
  • Step S15 The NF (CTF) sends an online charging request to release the session to the OCHF (Nochf_ChargingService), and reports the amount used by the user.
  • CTF CTF
  • Step S16 OCHF (Nochf_Charging Service) deducts the user fee (or the balance of the package) according to the amount used by the user.
  • OCHF Nochf_Charging Service
  • Step S17 OCHF (Nochf_ChargingService) sends a response message to NF (CTF) to inform the user that the fee deduction is successful.
  • CTF NF
  • Step S18A The NF (CTF) sends a request for ending charging data to OFCHF (Nofchf_ChargingDataService).
  • Step S18B OFCHF (Nofchf_ChargingDataService) updates the bill content, such as the accumulation of traffic or time, and closes the bill.
  • OFCHF Nofchf_ChargingDataService
  • Step S18C OFCHF (Nofchf_ChargingDataService) sends a response to NF (CTF): closing the bill.
  • the offline charging billing step that is consistent with the online charging session in the embodiment of the present application (in the figure, NF integrates CTF&CDF).
  • Step S01 The user requests to use network resources.
  • Step S02 NF (CTF) estimates the amount of resources to be used.
  • Step S03 NF (CTF) sends an online charging request to OCHF (Nochf_ChargingService).
  • Step S04 OCHF (Nochf_ChargingService) calls ABMF, and RF calculates the amount allowed to be used by the user.
  • Step S05 OCH (Nochf_ChargingService) F delivers the amount to NF (CTF).
  • Step S06A The NF (CDF) creates a CDR (Open CDR) locally.
  • Step S06 The NF (CTF) delivers the available network usage to the user.
  • Step S07 When the usage reporting management trigger arrives (for example, regular reporting), *[Usage reporting process] is triggered, and * indicates that the process can be triggered multiple times.
  • the usage reporting management trigger arrives (for example, regular reporting)
  • *[Usage reporting process] is triggered
  • Step S08A NF (CDF) updates the call bill content, such as the accumulation of traffic or time, and can also generate part of the call bill locally according to the conditions of part of the bill issuance (for example: bill by time or bill by flow).
  • CDF CDF
  • Step S08B NF (CDF) sends a bill to OFCHF (Nofchf_CDRStorageService).
  • Step S08C OFCHF (Nofchf_CDRStorageService) receives and stores the CDR.
  • Step S08D OFCHF (Nofchf_CDRStorageService) sends a response message.
  • Step S08 NF (CTF) estimates the amount of resources to be used subsequently (but not exceeding the amount issued by OCHF), and directly delivers to users for use.
  • CTF CTF
  • Step S09 When the quota management trigger arrives (for example, tariff switching), *[quota management process] is triggered, and * indicates that the process can be triggered multiple times.
  • the quota management trigger arrives (for example, tariff switching), *[quota management process] is triggered, and * indicates that the process can be triggered multiple times.
  • Step S10 NF (CTF) estimates the amount of resources to be used subsequently, and reports the amount already used by the user.
  • Step S11 OCHF (Nochf_Charging Service) deducts the user fee (or package balance) according to the amount already used by the user, and calls ABMF, and RF calculates the amount that the user is allowed to continue to use.
  • OCHF Nochf_Charging Service
  • Step S12 OCHF (Nochf_ChargingService) delivers the amount to NF (CTF).
  • Step S13A NF (CDF) updates the call bill content, such as the accumulation of traffic or time, and can also generate part of the call bill locally based on partial bill issuing conditions (for example, bill issued by time or bill by flow).
  • NF CDF updates the call bill content, such as the accumulation of traffic or time, and can also generate part of the call bill locally based on partial bill issuing conditions (for example, bill issued by time or bill by flow).
  • Step S13B NF (CDF) sends a bill to OFCHF (Nofchf_CDRStorageService).
  • Step S13C OFCHF (Nofchf_CDRStorageService) receives and stores the bill.
  • Step S13D OFCHF (Nofchf_CDRStorageService) sends a response message.
  • Step S13 The NF (CTF) delivers the network usage that can be used continuously to the user.
  • Step S14 The process of the network used by the user this time ends, and the current session is released.
  • Step S15A NF (CDF) generates the last partial bill locally.
  • Step S15B NF (CDF) sends a bill to OFCHF (Nofchf_CDRStorageService).
  • Step S15C OFCHF (Nofchf_CDRStorageService) receives and stores the CDR.
  • Step S15D OFCHF (Nofchf_CDRStorageService) sends a response message.
  • Step S15 The NF (CTF) sends an online charging request to release the session to the OCHF (Nochf_ChargingService), and reports the amount used by the user.
  • CTF CTF
  • Step S16 OCHF (Nochf_Charging Service) deducts the user fee (or the balance of the package) according to the amount used by the user.
  • OCHF Nochf_Charging Service
  • Step S17 OCHF (Nochf_ChargingService) sends a response message to NF (CTF) to inform the user that the fee deduction is successful.
  • CTF NF
  • Step S18A NF (CDF) updates the last partial CDR.
  • Step S18B NF (CDF) reports the last CDR to OFCHF (Nofchf_ChargingStorageService).
  • Step S18C OFCHF (Nofchf_ChargingStorageService) stores the CDR.
  • Step S18D OFCHF (Nofchf_ChargingStorageService) sends a response.
  • the online charging is converted to offline charging when the OCHF is abnormal (in the figure, NF integrates CTF).
  • Step S01 NF (CTF) sends an online charging request to OCHF (Nochf_ChargingService).
  • Step S02 OCHF (Nochf_ChargingService) calls ABMF, and RF calculates the amount allowed by the user.
  • Step S03 OCHF (Nochf_ChargingService) delivers the usage amount to NF (CTF).
  • Step S04A NF (CTF) sends an initial charging data request to OFCHF (Nofchf_ChargingDataService).
  • Step S04B OFCHF (Nofchf_ChargingDataService) creates a new CDR (Open CDR).
  • Step S04C OFCHF (Nofchf_ChargingDataService) sends a response to NF (CTF).
  • Step S04 The NF (CTF) delivers the available network usage to the user.
  • Step S05 When the quota management trigger arrives (for example, tariff switching).
  • Step S06 The NF (CTF) estimates the amount of resources to be used subsequently, and reports the amount already used by the user.
  • Step S07 OCHF (Nochf_Charging Service) deducts the user fee (or package balance) according to the amount already used by the user, and calls ABMF, and RF calculates the amount that the user is allowed to continue to use.
  • OCHF Nochf_Charging Service
  • Step S08 OCHF (Nochf_ChargingService) delivers the amount to NF (CTF), and the NF (CTF) does not receive the delivered message due to an abnormality.
  • Step S09 Triggering [Change into Offline Charging] means the process of changing from online charging to offline charging.
  • Step S10A NF (CTF) sends a request for updating charging data to OFCHF (Nofchf_ChargingDataService), and marks the first occurrence of an abnormality in online charging in the request message.
  • OFCHF Nofchf_ChargingDataService
  • Step S10B OFCHF (Nofchf_ChargingDataService) updates the content of the bill and generates a part of the bill, which contains the first online charging abnormal mark.
  • the bill After the bill is transmitted to the Billing System, it needs to be checked with the online billing deduction record. If the online billing has been deducted, the bill cannot be used as the basis for deduction again; otherwise, the billing system can rely on the bill Reimbursement of fees for users.
  • Step S10C OFCHF (Nofchf_ChargingDataService) sends a response to NF (CTF).
  • Step S10 NF (CTF) estimates the amount of resources to be used in the future, and directly delivers it to the user (the online charging is abnormal at this time, but because the offline charging bill can be issued, the user can continue to use the network) .
  • CTF CTF
  • Step S11 When the usage reporting management trigger arrives (for example, timing reporting), *[Usage reporting process] is triggered, and * indicates that the process can be triggered multiple times.
  • the usage reporting management trigger arrives (for example, timing reporting)
  • *[Usage reporting process] is triggered
  • Step S12A NF (CTF) sends a charging data update request to OFCHF (Nofchf_ChargingDataService), and carries a subsequent online charging abnormality flag (different from the first online charging abnormal message).
  • OFCHF Nofchf_ChargingDataService
  • Step S12B OFCHF (Nofchf_ChargingDataService) updates the content of the call bill, and the content contains the subsequent online charging exception mark; it can also output part of the call bill according to the conditions of part of the bill issuance (such as billing by time or billing by traffic). The bill also needs to contain the subsequent online billing exception mark.
  • OFCHF Nofchf_ChargingDataService
  • Step S12C OFCHF (Nofchf_ChargingDataService) sends a response to NF (CTF).
  • Step S12 The NF (CTF) estimates the amount of resources that need to be used subsequently, and directly delivers to the user for use.
  • Step S13 The process of the network used by the user this time ends, and the current session is released.
  • Step S14A The NF (CTF) sends a request for ending charging data to OFCHF (Nofchf_ChargingDataService), carrying the subsequent online charging abnormality flag.
  • OFCHF Nofchf_ChargingDataService
  • Step S14B OFCHF (Nofchf_ChargingDataService) updates the bill content, such as the accumulation of traffic or time, and the bill also needs to contain the subsequent online charging abnormality flag, and the bill is closed.
  • OFCHF Nofchf_ChargingDataService
  • Step S14C OFCHF (Nofchf_ChargingDataService) sends a response to NF (CTF): closing the bill.
  • the online charging is converted to offline charging when the OCHF is abnormal (in the figure, NF integrates CTF&CDF).
  • Step S01 NF (CTF) sends an online charging request to OCHF (Nochf_ChargingService).
  • Step S02 OCHF (Nochf_ChargingService) calls ABMF, and RF calculates the amount allowed by the user.
  • Step S03 OCH (Nochf_ChargingService) F delivers the amount to NF (CDF).
  • Step S04A The NF (CDF) creates a CDR (Open CDR) locally.
  • Step S04 The NF (CTF) delivers the available network usage to the user.
  • Step S05 When the quota management trigger arrives (for example, tariff switching).
  • Step S06 The NF (CTF) estimates the amount of resources to be used subsequently, and reports the amount already used by the user.
  • Step S07 OCHF (Nochf_Charging Service) deducts the user fee (or package balance) according to the amount already used by the user, and calls ABMF, and RF calculates the amount that the user is allowed to continue to use.
  • OCHF Nochf_Charging Service
  • Step S08 OCHF (Nochf_ChargingService) delivers the amount to NF (CTF), and the NF (CTF) does not receive the delivered message due to an abnormality.
  • Step S09 Triggering [Change into Offline Charging] means the process of changing from online charging to offline charging.
  • Step S10A The NF (CDF) updates the content of the bill and generates a part of the bill, which contains the first online charging abnormal mark.
  • the bill After the bill is transmitted to the Billing System, it needs to be checked with the online billing deduction record. If the online billing has been deducted, the bill cannot be used as the basis for deduction again; otherwise, the billing system can rely on the bill Reimbursement of fees for users.
  • Step S10B NF (CDF) sends a bill to OFCHF.
  • Step S10C OFCHF (Nofchf_CDRStorageService) receives and stores the CDR (or sends it to the CGF Dialog for processing).
  • OFCHF Nofchf_CDRStorageService
  • Step S10D OFCHF (Nofchf_CDRStorageService) sends a response message.
  • Step S10 NF (CTF) estimates the amount of resources to be used in the future, and directly delivers it to the user (the online charging is abnormal at this time, but because the offline charging bill can be issued, the user can continue to use the network) .
  • CTF CTF
  • Step S11 When the usage reporting management trigger arrives (for example, timing reporting), *[Usage reporting process] is triggered, and * indicates that the process can be triggered multiple times.
  • the usage reporting management trigger arrives (for example, timing reporting)
  • *[Usage reporting process] is triggered
  • Step S12A NF (CDF) updates the content of the call bill and generates a part of the call bill, which contains a subsequent online charging abnormality flag (different from the first online charging abnormality flag).
  • CDF online charging abnormality flag
  • Step S12B NF (CDF) sends a bill to OFCHF (Nofchf_CDRStorageService).
  • Step S12C OFCHF (Nofchf_CDRStorageService) receives and stores the CDR (or sends it to the CGF Dialog for processing).
  • OFCHF Nofchf_CDRStorageService
  • Step S12D OFCHF (Nofchf_CDRStorageService) sends a response message.
  • Step S12 The NF (CTF) estimates the amount of resources that need to be used subsequently, and directly delivers to the user for use.
  • Step S13 The process of the network used by the user this time ends, and the current session is released.
  • Step S14A The NF (CDF) locally generates the last partial bill, which contains the subsequent online charging abnormality flag (different from the first online charging abnormality flag).
  • Step S14B NF (CDF) sends a bill to OFCHF (Nofchf_CDRStorageService).
  • Step S14C OFCHF (Nofchf_CDRStorageService) receives and stores the CDR (or sends it to the CGF Dialog for processing).
  • OFCHF Nofchf_CDRStorageService
  • Step S14D OFCHF (Nofchf_CDRStorageService) sends a response message.
  • the offline bill in the embodiment of the present application carries the steps of deducting fees.
  • NF integrates CTF.
  • Step S01 Every time the NF (CTF) reports the user's actual network usage to OCHF (Nochf_ChargingService), after OCHF (Nochf_ChargingService) deducts the fee or package usage according to the usage, the deducted fee or package usage can be passed through the Online Charging Response message belt Return to NF (CTF).
  • CTF Online Charging Response message belt Return to NF
  • Step S02 After receiving the Online Charging Response from OCHF (Nochf_ChargingService), the NF (CTF) brings the deducted fee or package usage to OFCHF (Nofchf_ChargingDataService) through the Charging Data Request.
  • OCHF Nochf_ChargingService
  • CTF OFCHF
  • Step S03 OFCHF (Nofchf_ChargingDataService) saves the deducted fee or package usage to the call bill. Refer to step 13B and step 18B of FIG. 16.
  • step 8B If you want to enable the function of carrying deducted charges in offline CDRs, you cannot output part of the CDRs during the [Usage Reporting Process] process (because there is no fee information in the output CDRs at this time), refer to step 8B in Figure 16 .
  • the offline bill in the embodiment of the present application carries the steps of deducting fees.
  • NF integrates CTF&CDF.
  • Step S01 Every time the NF (CTF) reports the user's actual network usage to OCHF (Nochf_ChargingService), after OCHF (Nochf_ChargingService) deducts the fee or package usage according to the usage, the deducted fee or package usage can be passed through the Online Charging Response message belt Return to NF (CTF).
  • CTF Online Charging Response message belt Return to NF
  • Step S02 After receiving the Online Charging Response from OCHF (Nochf_ChargingService), the NF (CTF) updates the deducted fee or package usage to the call bill.
  • OCHF Nochf_ChargingService
  • step 8A If you want to enable the function of carrying deducted charges in offline CDRs, you cannot output part of the CDRs during the [Usage Reporting Process] process (because there is no fee information in the output CDRs at this time), refer to step 8A in Figure 17 .
  • Step S01 The user requests to use network resources.
  • Step S02 NF (CTF) estimates the amount of resources to be used.
  • Step S03 NF (CTF) sends an online charging request to OCHF1 (Nochf_ChargingService).
  • Step S04 OCHF1 (Nochf_ChargingService) calls ABMF, and RF calculates the amount allowed to be used by the user.
  • Step S05 OCHF1 (Nochf_ChargingService) delivers the amount to NF (CTF).
  • Step S06 The NF (CTF) delivers the available network usage to the user.
  • Step S07 When the quota management trigger arrives (for example, tariff switching).
  • Step S08 NF (CTF) estimates the amount of resources to be used subsequently, and reports the amount already used by the user.
  • Step S09 OCHF1 (Nochf_ChargingService) deducts the user fee (or package balance) according to the amount already used by the user, and calls ABMF, and RF calculates the amount that the user is allowed to continue to use.
  • OCHF1 Nochf_ChargingService
  • Step S10 OCHF1 (Nochf_ChargingService) triggers an exception.
  • Step S11 Actually, OCHF1 (Nochf_ChargingService) cannot deliver the amount to NF (CTF).
  • Step S12 NF (CTF) finds that OCHF1 (Nochf_ChargingService) is abnormal, and sends an online charging request to OCHF2 (Nochf_ChargingService) (equivalent to the fourth charging service module in the above embodiment), and the request message marks that this message may be repeated (Possibly duplicate), and report the amount that the user has used this time.
  • OCHF1 Nochf_ChargingService
  • OCHF2 Nochf_ChargingService
  • Step S13 OCHF2 (Nochf_ChargingService) reserves user fees or package balance (not actually deducted) according to the amount used by the user this time, and calls ABMF, and RF calculates the amount that the user is allowed to continue to use.
  • OCHF2 Nochf_ChargingService
  • Step S14 OCHF2 (Nochf_ChargingService) delivers the amount to NF (CTF).
  • Step S15 The NF (CTF) delivers the network usage that can be used continuously to the user.
  • Step S16 OCHF1 (Nochf_ChargingService) recovers abnormally.
  • Step S17 OCHF2 sends an online charging query message to OCFH1 (Nochf_ChargingQueryService).
  • Step S18 OCHF1 (Nochf_ChargingQueryService) responds to OCHF2 that the fee has been deducted.
  • Step S19 OCHF2 (Nochf_ChargingService) releases/returns the user fee reserved in step 13.
  • Step S01 The user requests to use network resources.
  • Step S02 NF (CTF) estimates the amount of resources to be used.
  • Step S03 NF (CTF) sends an online charging request to OCHF1 (Nochf_ChargingService).
  • Step S04 OCHF1 (Nochf_ChargingService) calls ABMF, and RF calculates the amount allowed to be used by the user.
  • Step S05 OCHF1 (Nochf_ChargingService) delivers the amount to NF (CTF).
  • Step S06 The NF (CTF) delivers the available network usage to the user.
  • Step S07 When the quota management trigger arrives (for example, tariff switching).
  • Step S08 NF (CTF) estimates the amount of resources to be used subsequently, and reports the amount already used by the user.
  • Step S09 OCHF1 (Nochf_ChargingService) triggers an exception.
  • Step S10 OCHF1 (Nochf_ChargingService) does not actually remove user fees and other operations.
  • Step S11 Actually, OCHF1 (Nochf_ChargingService) cannot deliver the amount to NF (CTF).
  • Step S12 NF (CTF) finds that OCHF1 (Nochf_ChargingService) is abnormal, and sends an online charging request to OCHF2 (Nochf_ChargingService) (equivalent to the fourth charging service module in the above embodiment), and the request message marks that this message may be repeated (Possibly duplicate), and report the amount that the user has used this time.
  • OCHF1 Nochf_ChargingService
  • OCHF2 Nochf_ChargingService
  • Step S13 OCHF2 (Nochf_ChargingService) reserves user fees or package balance (not actually deducted) according to the amount used by the user this time, and calls ABMF, and RF calculates the amount that the user is allowed to continue to use.
  • OCHF2 Nochf_ChargingService
  • Step S14 OCHF2 (Nochf_ChargingService) delivers the amount to NF (CTF).
  • Step S15 The NF (CTF) delivers the network usage that can be used continuously to the user.
  • Step S16 OCHF1 (Nochf_ChargingService) recovers abnormally.
  • Step S17 OCHF2 sends an online charging query message to OCFH1 (Nochf_ChargingQueryService).
  • Step S18 OCHF1 (Nochf_ChargingQueryService) responds to OCHF2 that there is no charge.
  • Step S19 OCHF2 (Nochf_Charging Service) deducts the user fee reserved in step 13.
  • OFCHF1 (equivalent to the first calculation in the above embodiment) Service module) has stored the updated part of the CDR.
  • Step S01A NF (CTF) sends an initial charging data request to OFCHF1 (Nofchf_ChargingDataService).
  • Step S01B OFCHF1 (Nofchf_ChargingDataService) creates a new bill.
  • Step S01C OFCHF1 (Nofchf_ChargingDataService) sends a response to NF (CTF).
  • Step S01 NF (CTF) estimates the amount of resources to be used and directly delivers to users for use.
  • Step S02 When the usage report management trigger arrives.
  • Step S03A NF (CTF) sends a request for updating charging data to OFCHF1 (Nofchf_ChargingDataService).
  • Step S03B OFCHF1 (Nofchf_ChargingDataService) updates the bill content, such as the accumulation of traffic or time, and can also output part of the bill according to the condition of issuing a bill by part of the bill (for example, billing by time or billing by flow).
  • OFCHF1 Nofchf_ChargingDataService
  • Step S03C OFCHF1 (Nofchf_ChargingDataService) triggers an exception.
  • Step S03D Actual OFCHF1 (Nofchf_ChargingDataService) cannot send a response to NF (CTF).
  • Step S03E NF (CTF) finds that OFCHF1 (Nofchf_ChargingDataService) is abnormal, and sends a request for updating charging data to OFCHF2 (Nochf_ChargingDataService) (equivalent to the second charging service module in the above embodiment), and it is possible to mark this message in the request message Possibly duplicated.
  • OFCHF1 Nofchf_ChargingDataService
  • OFCHF2 Nochf_ChargingDataService
  • Step S03F OFCHF2 (Nofchf_ChargingDataService) creates a new bill.
  • Step S03G OFCHF2 (Nofchf_ChargingDataService) sends a response to NF (CTF).
  • Step S03 NF (CTF) estimates the amount of resources that need to be used subsequently, and directly delivers to users for use.
  • Step S04 OFCHF1 (Nofchf_ChargingDataService) abnormal recovery.
  • Step S05 OFCHF2 sends a charging data query message to OFCHF1 (Nofchf_ChargingDataQueryService).
  • Step S06 OFCHF1 (Nofchf_ChargingDataQueryService) responds to OFCHF2 that the query is successful.
  • Step S07 OFCHF2 (Nofchf_ChargingDataService) does not need to update the bill (that is, it does not need to obtain the content of the previous Charging Data Request message, and then update the bill with the current Charging Data Request message), but the current Charging Data Request is required as the start message , It is convenient for the subsequent Charging Data Request to update the bill.
  • OFCHF1 (equivalent to the first in the above embodiment) Billing service module) does not store part of the CDR.
  • Step S01A NF (CTF) sends an initial charging data request to OFCHF1 (Nofchf_ChargingDataService).
  • Step S01B OFCHF1 (Nofchf_ChargingDataService) creates a new bill.
  • Step S01C OFCHF1 (Nofchf_ChargingDataService) sends a response to NF (CTF).
  • Step S01 NF (CTF) estimates the amount of resources to be used and directly delivers to users for use.
  • Step S02 When the usage report management trigger arrives.
  • Step S03A NF (CTF) sends a request for updating charging data to OFCHF1 (Nofchf_ChargingDataService).
  • Step S03B OFCHF1 (Nofchf_ChargingDataService) triggers an exception.
  • Step S03C Actual OFCHF1 (Nofchf_ChargingDataService) cannot update the bill.
  • Step S03D Actual OFCHF1 (Nofchf_ChargingDataService) cannot send a response to NF (CTF).
  • Step S03E NF (CTF) finds that OFCHF1 (Nofchf_ChargingDataService) is abnormal, and sends a request for updating charging data to OFCHF2 (Nochf_ChargingDataService) (equivalent to the second charging service module in the above embodiment), and it is possible to mark this message in the request message Possibly duplicated.
  • OFCHF1 Nofchf_ChargingDataService
  • OFCHF2 Nochf_ChargingDataService
  • Step S03F OFCHF2 (Nofchf_ChargingDataService) creates a new bill.
  • Step S03G OFCHF2 (Nofchf_ChargingDataService) sends a response to NF (CTF).
  • Step S03 NF (CTF) estimates the amount of resources that need to be used subsequently, and directly delivers to users for use.
  • Step S04 OFCHF1 (Nofchf_ChargingDataService) abnormal recovery.
  • Step S05 OFCHF2 sends a charging data query message to OFCHF1 (Nofchf_ChargingDataQueryService).
  • Step S06 OFCHF1 (Nofchf_ChargingDataQueryService) responds to OFCHF2 with a query failure, and carries the Charging Data Request message of the previous sequence number (refer to FIG. 14).
  • Step S07 OFCHF2 (Nofchf_ChargingDataService) supplements and updates the CDR according to the Charging Data Request message of the previous sequence number (that is, obtains the content of the previous Charging Data Request message, and then updates the CDR in combination with the current Charging Data Request message).
  • the NF (CDF) in the embodiment of the present application prevents the generation of repeated bills when transmitting offline charging information to multiple sets of OFCHF.
  • OFCHF1 has stored CDRs.
  • Step S01A The NF (CDF) creates a new CDR (Open CDR) locally.
  • Step S01 NF (CDF) estimates the amount of resources to be used and directly delivers to users for use.
  • Step S02 When the usage reporting management trigger arrives (for example, regular reporting), the usage reporting is triggered.
  • the usage reporting management trigger arrives (for example, regular reporting)
  • Step S03A NF (CDF) updates the content of the call bill, such as the accumulation of traffic or time, and can also generate part of the call bill locally based on the condition of issuing a bill by part of the bill (for example, billing by time or billing by traffic).
  • CDF updates the content of the call bill, such as the accumulation of traffic or time, and can also generate part of the call bill locally based on the condition of issuing a bill by part of the bill (for example, billing by time or billing by traffic).
  • Step S03B NF (CDF) sends a bill to OFCHF1 (Nofchf_CDRStorageService).
  • Step S03C OFCHF1 (Nofchf_CDRStorageService) receives and stores the bill.
  • Step S03D OFCHF1 (Nofchf_CDRStorageService) triggers an exception.
  • Step S03E Actual OFCHF1 (Nofchf_CDRStorageService) cannot send a response message.
  • Step S03F NF (CDF) finds that OFCHF1 (Nofchf_CDRStorageService) is abnormal, sends a bill to OFCHF2 (Nochf_CDRStorageService), and marks that the bill is possibly duplicated.
  • OFCHF1 Nofchf_CDRStorageService
  • OFCHF2 Nochf_CDRStorageService
  • Step S03G OFCHF2 (Nofchf_CDRStorageService) receives and saves the CDR to the suspicious CDR cache (meaning that the CDR cannot be transmitted to the Billing System yet).
  • Step S03H OFCHF2 (Nofchf_CDRStorageService) sends a response message.
  • Step S03 NF estimates the amount of resources to be used subsequently, and directly delivers to users for use.
  • Step S04 OFCHF1 (Nofchf_CDRStorageService) recovers abnormally.
  • Step S05 OFCHF2 sends a CDR query message to OFCHF1 (Nofchf_CDRQueryService).
  • Step S06 OFCHF1 (Nofchf_CDRQueryService) responds to OFCHF2 that the query is successful.
  • Step S07 OFCHF2 (Nofchf_CDRStorageService) cancels (deletes) the possibly duplicated bill in the suspicious bill cache.
  • Step S01A The NF (CDF) creates a new CDR (Open CDR) locally.
  • Step S01 NF (CDF) estimates the amount of resources to be used and directly delivers to users for use.
  • Step S02 When the usage reporting management trigger arrives (for example, regular reporting), the usage reporting is triggered.
  • the usage reporting management trigger arrives (for example, regular reporting)
  • Step S03A NF (CDF) updates the content of the call bill, such as the accumulation of traffic or time, and can also generate part of the call bill locally based on the condition of issuing a bill by part of the bill (for example, billing by time or billing by traffic).
  • CDF updates the content of the call bill, such as the accumulation of traffic or time, and can also generate part of the call bill locally based on the condition of issuing a bill by part of the bill (for example, billing by time or billing by traffic).
  • Step S03B NF (CDF) sends a bill to OFCHF1 (Nofchf_CDRStorageService).
  • Step S03C OFCHF1 (Nofchf_CDRStorageService) triggers an exception.
  • Step S03D OFCHF1 (Nofchf_CDRStorageService) actually cannot receive and store the CDR.
  • Step S03E Actual OFCHF1 (Nofchf_CDRStorageService) cannot send a response message.
  • Step S03F NF (CDF) finds that OFCHF1 (Nofchf_CDRStorageService) is abnormal, sends a bill to OFCHF2 (Nochf_CDRStorageService), and marks that the bill is possibly duplicated.
  • OFCHF1 Nofchf_CDRStorageService
  • OFCHF2 Nochf_CDRStorageService
  • Step S03G OFCHF2 (Nofchf_CDRStorageService) receives and saves the CDR to the suspicious CDR cache (meaning that the CDR cannot be transmitted to the Billing System yet).
  • Step S03H OFCHF2 (Nofchf_CDRStorageService) sends a response message.
  • Step S03 NF estimates the amount of resources to be used subsequently, and directly delivers to users for use.
  • Step S04 OFCHF1 (Nofchf_CDRStorageService) recovers abnormally.
  • Step S05 OFCHF2 sends a CDR query message to OFCHF1 (Nofchf_CDRQueryService).
  • Step S06 OFCHF1 (Nofchf_CDRQueryService) responds to OFCHF2 that the query fails.
  • Step S07 OFCHF2 (Nofchf_CDRStorageService) releases the bill in the suspicious bill cache to normal storage (that is, the bill can now be transmitted to the Billing System).
  • the embodiment of the present application also provides a storage medium in which a computer program is stored, wherein the computer program is configured to execute the steps in any of the foregoing method embodiments when running.
  • the foregoing storage medium may be configured to store a computer program for executing the following steps:
  • the network function module After the network function module delivers the resource, it reports the first charging data to the first charging service module through the first service interface.
  • the first charging data is used to indicate the usage of the resource, where the first charging service Modules and network function modules are set in the network domain;
  • the first charging service module receives first charging data, and the first charging data is used for charging domain charging.
  • the storage medium is also configured to store a computer program for executing any one of the steps in the above-mentioned embodiments, which will not be repeated here.
  • the foregoing storage medium may include, but is not limited to: U disk, Read-Only Memory (Read-Only Memory, ROM for short), Random Access Memory (Random Access Memory, RAM for short), Various media that can store computer programs, such as mobile hard disks, magnetic disks, or optical disks.
  • the embodiment of the present application also provides an electronic device, including a memory and a processor, the memory is stored with a computer program, and the processor is configured to run the computer program to execute the steps in any of the foregoing method embodiments.
  • the aforementioned electronic device may further include a transmission device and an input-output device, wherein the transmission device is connected to the aforementioned processor, and the input-output device is connected to the aforementioned processor.
  • the foregoing processor may be configured to execute the following steps through a computer program:
  • the network function module After the network function module delivers the resource, it reports the first charging data to the first charging service module through the first service interface.
  • the first charging data is used to indicate the usage of the resource, where the first charging service Modules and network function modules are set in the network domain;
  • the first charging service module receives first charging data, and the first charging data is used for charging domain charging.
  • modules or steps of this application can be implemented by a general computing device, and they can be concentrated on a single computing device or distributed in a network composed of multiple computing devices.
  • they can be implemented with program codes executable by the computing device, so that they can be stored in the storage device for execution by the computing device, and in some cases, can be executed in a different order than here.

Abstract

本申请提供了一种计费系统、方法存储介质及电子装置，计费系统包括第一计费服务模块和网络功能模块，其中，第一计费服务模块和网络功能模块都设置在网络域，网络功能模块在交付资源之后，将第一计费数据通过第一服务接口上报给第一计费服务模块，第一计费数据用于表示资源的使用情况；第一计费服务模块接收第一计费数据，第一计费数据用于计费域计费。

Description

一种计费系统、方法、存储介质及电子装置
相关申请的交叉引用
本申请基于申请号为201910562738.X、申请日为2019年6月26日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此以引入方式并入本申请。
技术领域
本申请涉及通信领域，具体而言，涉及一种计费系统、方法存储介质及电子装置。
背景技术
相关技术中，2/3/4G时期的计费域(Billing Domain)主要依靠离线计费处理系统(Offline Charging System)和在线计费处理系统(Online Charging System)共同完成计费；但该种计费架构接口众多、计费流程繁琐；随着技术的发展，5G采用了全新的融合离线、在线计费系统CCS(Converged Online Offline Charging System)完成计费，简化了接口，但在2/3/4G计费架构中，为防止出现重复话单，都是利用计费数据记录(Charging Data Record，简称CDR)的发送者计费数据功能(Charging Data Function，简称CDF)与网关计费功能(Charging Gateway Function，简称CGF)和计费域之间的交互实现间接查重，此流程涉及参与者多，消息来往复杂，任何一个环节出问题就会导致话单重复或丢失，根本无法确保在多套计费网关(Charging Gateway，简称CG)之间没有重复计费。而5G的计费架构中，尚未提出行之有效的防止重复计费的方法。
针对5G融合计费系统来说，一方面，这种5G融合计费系统采用了单一的Nchf融合离、在线计费接口，CCS异常时缺少对应的解决方案，这里的CCS异常不单单指网络异常，还包括CCS性能不足，网络攻击，病毒爆发导致的整个Billing Domain瘫痪等异常情况；另一方面，因为CCS集成了ABMF和RF功能，需要查询费率以及扣除用户的余额(或套餐)，这就导致整个CCS都会在Billing Domain实现，那么CCS中的能够生成话单的计费数据功能(Charging Data Function，简称CDF)也会在Billing Domain实现，这样在网络域就缺少了CDF/CGF功能，当出现计费问题时，网络域将无法提供话单供Billing Domain核查；再者，CCS的建设成本很高，这种计费系统也并不是运营商乐于接受的。
发明内容
本申请实施例提供了一种计费系统、方法存储介质及电子装置。
根据本申请的一个实施例，提供了一种计费系统，包括：第一计费服务模块和网络功能模块，其中，第一计费服务模块和网络功能模块都设置在网络域，网络功能模块在交付资源之后，将第一计费数据通过第一服务接口上报给第一计费服务模块，第一计费数据用于表示资源的使用情况；第一计费服务模块接收第一计费数据，第一计费数据用于计费域计费。
根据本申请的另一个实施例，提供了一种计费方法，包括：网络功能模块在交付资源之后，将第一计费数据通过第一服务接口上报给第一计费服务模块，所述第一计费数据用于表示所述资源的使用情况，其中，所述第一计费服务模块和所述网络功能模块都设置在网络域；所述第一计费服务模块接收所述第一计费数据，所述第一计费数据用于计费域计费。
根据本申请的又一个实施例，还提供了一种存储介质，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
根据本申请的又一个实施例，还提供了一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行上述任一项方法实施例中的步骤。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1是根据本申请实施例的计费系统的结构框图；
图2是根据本申请实施例的计费方法的流程图；
图3是根据本申请可选实施例的5G在线计费功能OCHF架构图；
图4是根据本申请可选实施例5G离线计费功能OFCHF架构图；
图5是根据本申请可选实施例的5G在线计费查询服务使用示意图；
图6是根据本申请可选实施例的5G离线计费查询服务使用示意图；
图7是根据本申请可选实施例的5G离线计费查询服务使用示意图；
图8是根据本申请可选实施例的计费系统的结构框图；
图9是根据本申请可选实施例的5G同时部署OCHF和OFCHF的架构图(NF集成CTF)；
图10是根据本申请可选实施例的5G同时部署OCHF和OFCHF的架构图(NF集成CTF&CDF)；
图11是根据本申请可选实施例的5G OCHF异常时在线计费转离线计费示意图(NF集成CTF)；
图12是根据本申请可选实施例的5G OCHF异常时在线计费转离线计费示意图(NF集成CTF&CDF)；
图13是根据本申请可选实施例的5G在线计费方法流程图；
图14是根据本申请可选实施例的5G离线计费方法流程图(NF集成CTF)；
图15是根据本申请可选实施例的5G离线计费方法流程图(NF集成CDF)；
图16是根据本申请可选实施例的和在线计费会话保持一致的离线计费出单方法流程图(NF集成CTF)；
图17是根据本申请可选实施例的和在线计费会话保持一致的离线计费出单方法流程图(NF集成CTF&CDF)；
图18是根据本申请可选实施例的OCHF异常时在线计费转离线计费方法流程图(NF集成CTF)；
图19是根据本申请可选实施例的OCHF异常时在线计费转离线计费方法流程图(NF集成CTF&CDF)；
图20是根据本申请可选实施例的NF向多套OCHF发送计费请求时，防止重复计费的方法流程图(OCHF1已扣费)；
图21是根据本申请可选实施例的NF向多套OCHF发送计费请求时，防止重复计费的方法流程图(OCHF1未扣费)；
图22是根据本申请可选实施例的NF(CTF)向多套OFCHF传输离线计费信息时，防止产生重复话单的方法流程图(OFCHF1已存储)；
图23是根据本申请可选实施例的NF(CTF)向多套OFCHF传输离线计费信息时，防止产生重复话单的方法流程图(OFCHF1未存储)；
图24是根据本申请可选实施例的NF(CDF)向多套OFCHF传输离线计费信息时，防止产生重复话单的方法流程图(OFCHF1已存储)；
图25是根据本申请可选实施例的NF(CDF)向多套OFCHF传输离线计费信息时，防止产生重复话单的方法流程图(OFCHF1未存储)。
具体实施方式
下文中将参考附图并结合实施例来详细说明本申请。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
实施例1
本申请实施例一所提供的系统实施例可以在核心网(Core Network)计费装置中执行。在本实施例中提供了一种计费系统，图1是根据本申请实施例的计费系统的结构框图，如图1所示，该系统包括：
第一计费服务模块和网络功能模块，其中，第一计费服务模块和网络功能模块都设置在网络域，网络功能模块在交付资源之后，将第一计费数据通过第一服务接口上报给第一计费服务模块，第一计费数据用于表示资源的使用情况；
第一计费服务模块接收第一计费数据，第一计费数据用于计费域计费。
由于第一计费服务模块和网络功能模块都设置在网络域，第一计费服务模块接收第一计费数据并进行存储，所以第一计费服务模块可以提供计费数据用于计费域计费或者核对数据，这样可以有效防止计费系统出现异常后无法计费的情况，因此，可以解决相关技术中计费系统所存在的一些问题问题，达到提高计费系统稳定性的效果。
在一个实施方式中，网络功能模块在交付资源之后，将第一计费数据通过第一服务接口上报给第一计费服务模块，第一计费服务模块接收第一计费数据，包括：
网络功能模块根据资源的使用情况将更新的部分第一计费数据通过第一服务接口上报给第一计费服务模块；第一计费服务模块接收部分第一计费数据并根据部分第一计费数据对之前接收到的第一计费数据进行更新；或者，
网络功能模块根据资源的使用情况对第一计费数据进行更新，并将更新后的第一计费数据通过第一服务接口上报给第一计费服务模块；第一计费服务模块接收更新后的第一计费数据。
在一个实施方式中，在网络功能模块将第一计费数据通过第一服务接口上报给第一计费服务模块之后，系统还包括：
当网络功能模块未收到第一计费服务模块反馈的第一响应时，将第一计费数据标记后上报给第二计费服务模块，其中，第一响应用于表示第一计费服务模块成功接收第一计费数据；
第二计费服务模块接收被标记的第一计费数据。
在一个实施方式中，在第二计费服务模块接收被标记的第一计费数据之后，系统还包括：
第二计费服务模块临时存储被标记的第一计费数据；
第二计费服务模块向第一计费服务模块发送查询请求，查询请求用于查询第一计费服务模块是否存储了与被标记的第一计费数据一致的第一计费数据；
当第二计费服务模块接收到第一计费服务模块发送的查询成功响应时，删除临时存储的被标记的第一计费数据；
当第二计费服务模块接收到第一计费服务模块发送的查询失败响应时，将被标记的第一计费数据进行存储。
通过上述的过程可以防止产生重复计费数据。
在一个实施方式中，在第二计费服务模块接收被标记的第一计费数据之后，系统还包括：
第二计费服务模块创建初始第一计费数据记录；
第二计费服务模块向第一计费服务模块发送查询请求，查询请求用于查询第一计费服务模块是否存储了与被标记的第一计费数据一致的第一计费数据；
当第二计费服务模块接收到第一计费服务模块发送的查询成功响应时，不更新初始第一计费数据记录；
当第二计费服务模块接收到第一计费服务模块发送的查询失败响应时，根据被标记的第一计费数据更新初始第一计费数据记录，并存储更新后的初始第一计费数据记录。
通过上述的过程也可以防止产生重复计费数据。
在一个实施方式中，系统还包括第三计费服务模块，其中第三计费服务模块设置在计费域，其中，网络功能模块通过第二服务接口向第三计费服务模块发送资源请求；
第三计费服务模块根据预先设定的资源配额向网络功能模块下发资源额度；
网络功能模块接收资源额度并根据资源额度交付资源。
在一个实施方式中，系统还包括：
第三计费服务模块根据接收到的资源请求进行批价和/或预扣费。
在一个实施方式中，网络功能模块在交付资源之后，将第二计费数据通过第一服务接口上报给第一计费服务模块，第一计费服务模块接收第二计费数据，第二计费数据用于表示资源的使用情况。
在一个实施方式中，网络功能模块将第二计费数据通过第一服务接口上报给第一计费服务模块，第一计费服务模块接收第二计费数据，包括：
网络功能模块根据资源的使用情况将更新的部分第二计费数据通过第一服务接口上报给第一计费服务模块；第一计费服务模块接收部分第二计费数据并根据部分第二计费数据对之前接收到的第二计费数据进行更新；或者，
网络功能模块根据资源的使用情况对第二计费数据进行更新，并将更新后的第二计费数据通过第一服务接口上报给第一计费服务模块；第一计费服务模块接收更新后的第二计费数据。
在一个实施方式中，在网络功能模块通过第二服务接口向第三计费服务模块发送资源请求之后，系统还包括：
当网络功能模块未收到第三计费服务模块反馈的第二响应时，将资源请求标记后上报给第四计费服务模块，其中，第二响应用于表示第三计费服务模块成功接收资源请求；
第四计费服务模块接收被标记的资源请求并根据预先设定的资源配额向网络功能模块下发资源额度。
在一个实施方式中，在第四计费服务模块接收被标记的资源请求之后，系统还包括：
第三计费服务模块根据接收到的被标记的资源请求进行预扣费；
第四计费服务模块向第三计费服务模块发送扣费查询请求；
当第四计费服务模块接收到第三计费服务模块反馈的已扣费响应时，返还预扣费用；
当第四计费服务模块接收到第三计费服务模块反馈的未扣费响应时，第四计费服务模块根据接收到的被标记的资源请求进行扣费。
在一个实施方式中，在网络功能模块通过第二服务接口向第三计费服务模块发送资源请求之后，系统还包括：
当网络功能模块未收到第三计费服务模块反馈的第二响应时，将当前计费数据标记后上报给第一计费服务模块，其中，第二响应用于表示第三计费服务模块成功接收资源请求；
第一计费服务模块接收被标记的当前计费数据并将被标记的当前计费数据存储。
本实施例还提供了一种计费方法，如图2所示，该方法包括：
S202，网络功能模块在交付资源之后，将第一计费数据通过第一服务接口上报给第一计费服务模块，第一计费数据用于表示资源的使用情况，其中，第一计费服务模块和网络功能模块都设置在网络域；
S204，第一计费服务模块接收第一计费数据，第一计费数据用于计费域计费。
通过本实施例的方法，由于第一计费服务模块和网络功能模块都设置在网络域，第一计费服务模块接收第一计费数据并进行存储，所以第一计费服务模块可以提供计费数据用于计费域计费或者核对数据，这样可以有效防止计费系统出现异常后无法计费的情况，因此，可以解决相关技术中计费系统所存在的一些问题问题，达到提高计费系统稳定性的效果。
在一个实施方式中，网络功能模块在交付资源之后，将第一计费数据通过第一服务接口上报给第一计费服务模块，第一计费服务模块接收第一计费数据，包括：
网络功能模块根据资源的使用情况将更新的部分第一计费数据通过第一服务接口上报给第一计费服务模块；第一计费服务模块接收部分第一计费数据并根据部分第一计费数据对之前接收到的第一计费数据进行更新；或者，
网络功能模块根据资源的使用情况对第一计费数据进行更新，并将更新后的第一计费数 据通过第一服务接口上报给第一计费服务模块；第一计费服务模块接收更新后的第一计费数据。
在一个实施方式中，在网络功能模块将第一计费数据通过第一服务接口上报给第一计费服务模块之后，方法还包括：
当网络功能模块未收到第一计费服务模块反馈的第一响应时，将第一计费数据标记后上报给第二计费服务模块，其中，第一响应用于表示第一计费服务模块成功接收第一计费数据；
第二计费服务模块接收被标记的第一计费数据。
在一个实施方式中，在第二计费服务模块接收被标记的第一计费数据之后，方法还包括：
第二计费服务模块临时存储被标记的第一计费数据；
第二计费服务模块向第一计费服务模块发送查询请求，查询请求用于查询第一计费服务模块是否存储了与被标记的第一计费数据一致的第一计费数据；
当第二计费服务模块接收到第一计费服务模块发送的查询成功响应时，删除临时存储的被标记的第一计费数据；
当第二计费服务模块接收到第一计费服务模块发送的查询失败响应时，将被标记的第一计费数据进行存储。
在一个实施方式中，在第二计费服务模块接收被标记的第一计费数据之后，方法还包括：
第二计费服务模块创建初始第一计费数据记录；
第二计费服务模块向第一计费服务模块发送查询请求，查询请求用于查询第一计费服务模块是否存储了与被标记的第一计费数据一致的第一计费数据；
当第二计费服务模块接收到第一计费服务模块发送的查询成功响应时，不更新初始第一计费数据记录；
当第二计费服务模块接收到第一计费服务模块发送的查询失败响应时，根据被标记的第一计费数据更新初始第一计费数据记录，并存储更新后的初始第一计费数据记录。
在一个实施方式中，方法还包括：
网络功能模块通过第二服务接口向第三计费服务模块发送资源请求，其中，第三计费服务模块设置在计费域；
第三计费服务模块根据预先设定的资源配额向网络功能模块下发资源额度；
网络功能模块接收资源额度并根据资源额度交付资源。
在一个实施方式中，方法还包括：
第三计费服务模块根据接收到的资源请求进行批价和/或预扣费。
在一个实施方式中，网络功能模块在交付资源之后，将第二计费数据通过第一服务接口 上报给第一计费服务模块，第一计费服务模块接收第二计费数据，第二计费数据用于表示资源的使用情况。
在一个实施方式中，网络功能模块将第二计费数据通过第一服务接口上报给第一计费服务模块，第一计费服务模块接收第二计费数据，包括：
网络功能模块根据资源的使用情况将更新的部分第二计费数据通过第一服务接口上报给第一计费服务模块；第一计费服务模块接收部分第二计费数据并根据部分第二计费数据对之前接收到的第二计费数据进行更新；或者，
网络功能模块根据资源的使用情况对第二计费数据进行更新，并将更新后的第二计费数据通过第一服务接口上报给第一计费服务模块；第一计费服务模块接收更新后的第二计费数据。
在一个实施方式中，在网络功能模块通过第二服务接口向第三计费服务模块发送资源请求之后，方法还包括：
当网络功能模块未收到第三计费服务模块反馈的第二响应时，将资源请求标记后上报给第四计费服务模块，其中，第二响应用于表示第三计费服务模块成功接收资源请求；
第四计费服务模块接收被标记的资源请求并根据预先设定的资源配额向网络功能模块下发资源额度。
在一个实施方式中，在第四计费服务模块接收被标记的资源请求之后，方法还包括：
第三计费服务模块根据接收到的被标记的资源请求进行预扣费；
第四计费服务模块向第三计费服务模块发送扣费查询请求；
当第四计费服务模块接收到第三计费服务模块反馈的已扣费响应时，返还预扣费用；
当第四计费服务模块接收到第三计费服务模块反馈的未扣费响应时，第四计费服务模块根据接收到的被标记的资源请求进行扣费。
在一个实施方式中，在网络功能模块通过第二服务接口向第三计费服务模块发送资源请求之后，方法还包括：
当网络功能模块未收到第三计费服务模块反馈的第二响应时，将当前计费数据标记后上报给第一计费服务模块，其中，第二响应用于表示第三计费服务模块成功接收资源请求；
第一计费服务模块接收被标记的当前计费数据并将被标记的当前计费数据存储。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如 ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本申请各个实施例的方法。
可选实施方式
本申请可选实施方式增加新的在线计费功能OCHF(Online Charging Function)和离线计费功能OFCHF(Offline Charging Function)，并基于服务架构提出了一种更加先进更加有效的计费排重方法，不仅丰富了5G计费的实现方式，还大大减少了计费排重流程的复杂程度，满足了更多运营商部署5G计费方面的要求，提出了一种新的5G计费实现方式。下面将结合附图进一步说明：
本申请实施例涉及到的技术术语英文全称、中文名称和英文缩写如表1所示：
表1
缩写 英文全称 中文释义
ABMF Account Balance Management Function 账户余额管理系统
CCS Converged Online Offline Charging System 融合离线、在线计费系统
CDF Charging Data Function 计费话单(生成)功能
CDR Charging Data Record 计费话单
CGF Charging Gateway Function 计费网关功能
CTF Charging Trigger Function 计费触发功能
Nochf Service-based interface exhibited by OCHF 5G基于服务的在线计费接口
Nofchf Service-based interface exhibited by OFCHF 5G基于服务的离线计费接口
OCF Online Charging Function 2/3/4G在线计费功能
OFCHF Offline Charging Function 5G离线计费功能(系统)
OCHF Online Charging Function 5G在线计费功能(系统)
OCS Online Charging System 2/3/4G在线计费系统
RF Rating Function 费率管理功能
需要说明的是，离线计费Offline Charging主要是：用户先使用网络资源并由CDF(Charging Data Function)生成相应的计费话单，后经由CGF(Charging Gateway Function)将计费话单编码生成计费话单文件并传输给Billing Domain的Billing System完成计费。因为根据话单计费的功能是在Billing Domain的Billing System中完成，而CDF和CGF主要功能是生成话单或话单文件，并不负责对用户收费，所以CDF和CGF可以在网络侧实现。
在线计费Online Charging主要是：当用户需要使用网络资源时，先由网络侧的CTF(Charging Trigger Function)向在线计费服务申请配额(通常指使用时间或者用量)，只有在该用户的余额(或套餐)充足时，申请才会成功，用户才可以开始使用网络。因为在线计费服务集成了批价、扣费功能、账户余额管理、费率管理等类似的功能，需要查询费率以及扣除用户的余额(或套餐)，所以在线计费服务可以在Billing Domain实现。
(离线计费)话单CDR：根据网络资源的使用量生成的计费记录(Charging Data Record)， 主要包含内容有：用户标识(IMSI等)，使用网络资源的开始、结束时间，用量等。因为CDR生成后即表示用户已经使用了一定用量的网络资源，所以CDR一般都是指离线计费话单，它可以用于离线计费、网间结算、经营分析，统计等场景。
预付费用户：指先充值，后使用网络的用户。在线计费的对象一般是指预付费用户，预付费用户也会生成话单，预付费用户生成的话单也叫离线话单。说明：在线计费的对象也可以是后付费用户，如果后付费账户没有余额，可以先记账，月底再统一结算。
后付费用户：指可以先使用网络，后计费的用户。这样的用户一般走离线计费流程(没有必要走在线计费流程，因为无法实时扣费)。
本申请技术方案，设计了OCHF(相当于上述实施例中的第三计费服务模块)和OFCHF(相当于上述实施例中的第一计费服务模块)，分别作为在线和离线计费功能，其中OCHF负责在线计费控制；OFCHF负责生成离线话单。OCHF采用基于SBI(Service-based interface)和各NF(相当于上述实施例中的网络功能模块)(Network Function，本文统一理解为5G网络下有能力输出计费信息的NF)通讯，接口名称是Nochf(相当于上述实施例中的第二服务接口)(Service-based interface exhibited by OCHF)。Nochf对外提供了2种服务：
Nochf_ChargingService负责接收并处理各个NF的在线计费请求：Online Charging Request；
Nochf_ChargingQueryService负责查询本地已经处理的计费请求。
而OFCHF作为5G核心网的对外输出离线话单的统一出口，可以连接一个或者多个NF进行话单采集和上报，OFCHF采用基于SBI和各NF通讯，接口名称是Nofchf(相当于上述实施例中的第一服务接口)(Service-based interface exhibited by OFCHF)。Nofchf对外提供了4种服务：
Nofchf_ChargingDataService负责收集并处理各个NF(CTF)的离线计费消息：Charging Data Request并生成离线话单；
Nofchf_CDRStorageService负责收集并处理各个NF(CDF)的CDR消息：CDR Request；
Nofchf_ChargingDataQueryService负责查询本地已经保存的ChargingDataRequest消息；
Nofchf_CDRQueryService负责查询本地已经保存的离线计费话单。
如图3所示，Nochf_ChargingService负责接收并处理各个NF的Online Charging Request消息，根据(预付费)用户使用的业务等信息调用RF完成批价，再根据批价的结果调用ABMF确定是否对用户预授权；如果用户的账户余额充足，则Nochf_ChargingService给NF回应获取预授权成功。
如图4所示，由Nofchf_ChargingDataService负责收集各个NF(CTF)的Charging Data  Request消息并生成离线话单；或者由Nofchf_CDRStorageService负责收集各个NF(CDF)的CDR Request消息并生成离线话单，话单再经过合并、分拣、过滤、编码等处理后存储在本地，最后通过Bx接口上报话单文件给Billing Domain的Billing System。
如图5所示，服务消费者向Nochf_ChargingQueryService发送计费查询请求，请求消息中携带但不限于：用户标识IMSI，计费开始时间StartTime，计费结束时间EndTime(可选)，计费时长(可选)，会话标识ChargingID，计费部分序列号SequenceNumber(可选，如果一次会话分多次Charging Request实现，每次Charging Request都应该有个递增的序列号)，NF-Address等关键字；OCHF(Nochf_ChargingQueryService)收到查询请求后，如果在本地查找到对应的Online Charging Request，则返回Debited，返回消息中也可以携带完整或部分的Online Charging Request内容，包括已扣费用或套餐余量。如果在本地查找不到对应的Online Charging Request消息，则返回No Debited。
如图6所示，服务消费者向Nofchf_ChargingDataQueryService发送计费查询请求，请求消息中携带但不限于：用户标识IMSI，计费开始时间StartTime，计费结束时间EndTime(可选)，计费时长(可选)，会话标识ChargingID，计费部分序列号SequenceNumber(可选，如果一次会话分多次Charging Data Request实现，每次Charging Data Request都应该有个递增的序列号)，NF-Address等关键字；OCHF(Nofchf_ChargingDataQueryService)收到查询请求后，如果在本地查找到对应的Charging Data Request，则返回Success，返回消息中也可以携带完整或部分的Charging Data Request内容。如果在本地查找不到对应的Charging Data Request消息，则返回Unsuccess，如果存在该会话上一个序号的Charging Data Request，则在返回Unsuccess的同时携带上一个序号的Charging Data Request消息，以便于其他OFCHF补充生成话单(具体可参考可选实施方式)。
如图7所示，服务消费者向Nofchf_CDRQueryService发送话单查询请求，请求消息中携带但不限于：用户标识IMSI，计费开始时间StartTime，计费结束时间EndTime(可选)，计费时长，会话标识ChargingID，计费部分序列号SequenceNumber(可选，如果一次会话输出多个部分话单，每个部分话单都应该有个递增的序列号)，NF-Address等关键字；OCHF(Nofchf_CDRQueryService)收到查询请求后，如果在本地查找到对应的CDR则返回Success，返回消息中也可以携带完整或部分的CDR。如果在本地查找不到对应的CDR则返回Unsuccess。
OFCHF是一个或者多个需要离线计费的NF的统一出口，进行计费的输出。OFCHF的CGF功能支持在本地长时间存储话单，可长期有效的为Billing Domain提供话单文件。
图8是根据本申请可选实施例的计费系统的结构框图，在图8中，计费系统同时部署了 在线计费服务功能(相当于上述实施例中的第三计费服务模块)和离线计费服务功能(相当于上述实施例中的第一计费服务模块)，二者分别通过服务化的接口与NFs(相当于上述实施例中的网络功能模块)连接。如图9和图10所示，在同时部署OCHF和OFCHF场景下，通过本申请实施例的方法可以使得OFCHF生成的话单和OCHF完全保持一致，正因为如此，OCHF可以不用实现CDF和CGF功能。
如图9和图10所示，在同时部署OCHF和OFCHF场景下，还可以通过本申请的可选实施方式将OCHF扣除用户的费用(或套餐用量，或通话时长等)带给OFCHF，使得OFCHF生成的话单中同样具备包含费用等信息的能力。
需要说明的是，因为用户余额、套餐、费率这些参数会随着运营商的业务推广策略不断发生变化，而OFCHF的所有功能和这些参数无关，所以OFCHF作为一个相对稳定的功能可以放在网络侧实现，由于OFCHF的CGF存储了一定时间范围的话单，在将来发生计费异常时，网络侧可以提供一份话单用于和Billing Domain核对。
需要说明的是，OCHF/CCS受用户余额、套餐、费率这些参数影响较大，可以放在Billing Domain侧实现，很可能NF和OCHF/CCS不是一个厂家的设备，即使是同一个厂家的设备也可能不在同一个网络；因此NF在和OCHF/CCS通讯时需要充分考虑OCHF/CCS异常的场景，如图11和图12所示，本申请的可选实施例在OCFH/CCS甚至整个Billing Domain异常时，可以通过在线转离线的方式由OFCHF生成离线话单文件，供Billing System随时获取并用于计费。
需要说明的是，在本实施例中，离线计费步骤中的部分话单或者完整话单相当于上述实施例中的第一计费数据；在线计费步骤中的在线计费请求相当于上述实施例中的第二计费数据；离线计费步骤中的离线计费服务功能的响应相当于是上述实施例中的第一响应；在线计费步骤中的在线计费服务功能的响应相当于是上述实施例中的第二响应。
本申请可选实施例可以满足部分运营商只想建立一套离线计费系统的要求，也可满足部分运营商想继续沿用现有离线计费系统或离、在线分离计费系统的要求；为运营商节省了建立全新融合计费系统CCS的成本。
如图20和图21所示，可选地，本申请实施例基于服务架构提出了一种更加先进的在线计费方法，提供了NF向多套OCHF发送计费请求时，防止重复计费的机制。
如图22和图23所示，可选地，本申请实施例基于服务架构提出了一种更加先进的离线计费传输方法，提供了NF(CTF)向多套OFCHF传输离线计费信息时，防止产生重复话单的机制。
如图24和图25所示，可选地，本申请实施例基于服务架构提出了一种更加先进的离线 计费传输方法，简化了2/3/4G时期通过Ga口传输离线计费信息的复杂流程，提供了NF(CDF)向多套OFCHF传输离线计费信息时，防止产生重复话单的机制。
如图13所示，本申请实施例的5G在线计费步骤如下：
步骤S01：用户请求使用网络资源。
步骤S02：NF(CTF)预估需要使用的资源用量。
步骤S03：NF(CTF)向OCHF(Nochf_ChargingService)发送在线计费请求。
步骤S04：OCHF(Nochf_ChargingService)调用ABMF，RF计算该用户允许使用的用量。
步骤S05：OCHF(Nochf_ChargingService)向NF(CTF)下发用量。
步骤S06：NF(CTF)向用户交付使用可以使用的网络用量。
步骤S07：当配额管理触发器到达时(比如费率切换)触发*[配额管理过程]，*表示该过程可以被触发多次。
步骤S08：NF(CTF)预估后续需要使用的资源用量，并上报用户已经使用的用量。
步骤S09：OCHF(Nochf_ChargingService)根据用户已经使用的用量扣除用户费用(或套餐余量)，并调用ABMF，RF计算该用户允许继续使用的用量。
步骤S10：OCHF(Nochf_ChargingService)向NF(CTF)下发用量。
步骤S11：NF(CTF)向用户交付使用可以继续使用的网络用量。
步骤S12：用户本次使用的网络的过程结束，释放本次会话。
步骤S13：NF(CTF)向OCHF(Nochf_ChargingService)发送释放会话的在线计费请求，并上报用户已经使用的用量。
步骤S14：OCHF(Nochf_ChargingService)根据用户已经使用的用量扣除用户费用(或套餐余量)。
步骤S15：OCHF(Nochf_ChargingService)向NF(CTF)发送回应消息，告知用户费用扣除成功。
如图14所示，本申请实施例的5G离线计费步骤如下，其中NF上集成了CTF功能，
步骤S01A：NF(CTF)向OFCHF(Nofchf_ChargingDataService)发送初始计费数据请求。
步骤S01B：OFCHF(Nofchf_ChargingDataService)创建一个新的话单。
步骤S01C：OFCHF(Nofchf_ChargingDataService)向NF(CTF)发送回应。
步骤S01：NF(CTF)预估需要使用的资源用量，并直接向用户交付使用(说明：本步骤无需等待S01A/B/C..完成，如果OFCHF无回应，消息应当在NF本地缓存，下文类似A/B/C..的步骤请统一参考本说明)。
步骤S02：当用量上报管理触发器到达时(比如定时上报)触发*[用量上报过程]，*表示该过程可以被触发多次。
步骤S03A：NF(CTF)向OFCHF(Nofchf_ChargingDataService)发送更新计费数据请求。
步骤S03B：OFCHF(Nofchf_ChargingDataService)更新话单内容，比如流量或时间的累加，也可以根据部分话单出单条件(比如：按时间出单或按流量出单)输出部分话单。
步骤S03C：OFCHF(Nofchf_ChargingDataService)向NF(CTF)发送回应。
步骤S03：NF(CTF)预估需要后续需要使用的资源用量，并直接向用户交付使用。
步骤S04：用户本次使用的网络的过程结束，释放本次会话。
步骤S05A：NF(CTF)向OFCHF(Nofchf_ChargingDataService)发送结束计费数据请求。
步骤S05B：OFCHF(Nofchf_ChargingDataService)更新话单内容，比如流量或时间的累加，并关闭话单。
步骤S05C：OFCHF(Nofchf_ChargingDataService)向NF(CTF)发送回应：关闭话单。
步骤S05D：OFCHF生成话单文件，并将话单文件通过Bx口发给Billing System。
如图15所示，本申请实施例的5G离线计费步骤如下，其中NF集成CDF。
步骤S01A：NF(CDF)在本地创建一个新的话单(Open CDR)。
步骤S01：NF(CDF)预估需要使用的资源用量，并直接向用户交付使用。
步骤S02：当用量上报管理触发器到达时(比如定时上报)触发*[用量上报过程]，*表示该过程可以被触发多次。
步骤S03A：NF(CDF)更新话单内容，比如流量或时间的累加，也可以根据部分话单出单条件(比如：按时间出单或按流量出单)在本地生成部分话单。
步骤S03B：NF(CDF)向OFCHF(Nofchf_CDRStorageService)发送话单。
步骤S03C：OFCHF(Nofchf_CDRStorageService)接收并存储话单(或发送给CGF对话单进行处理)。
步骤S03D：OFCHF(Nofchf_CDRStorageService)发送回应消息。
步骤S03：NF预估需要后续需要使用的资源用量，并直接向用户交付使用。
步骤S04：用户本次使用的网络的过程结束，释放本次会话。
步骤S05A：NF(CDF)在本地产生最后一张部分话单。
步骤S05B：NF(CDF)向OFCHF(Nofchf_CDRStorageService)发送话单。
步骤S05C：OFCHF(Nofchf_CDRStorageService)接收并存储话单(或发送给CGF对话单进行处理)。
步骤S05D：OFCHF(Nofchf_CDRStorageService)发送回应消息。
步骤S05E：OFCHF(Nofchf_CDRStorageService)生成话单文件，并将话单文件通过Bx口发给Billing System。
如图16所示，本申请实施例的和在线计费会话保持一致的离线计费出单步骤，其中NF集成CTF。
步骤S01：用户请求使用网络资源。
步骤S02：NF(CTF)预估需要使用的资源用量。
步骤S03：NF(CTF)向OCHF(Nochf_ChargingService)发送在线计费请求。
步骤S04：OCHF(Nochf_ChargingService)调用ABMF，RF计算该用户允许使用的用量。
步骤S05：OCHF(Nochf_ChargingService)向NF(CTF)下发用量。
步骤S06A：NF(CTF)向OFCHF(Nofchf_ChargingDataService)发送初始计费数据请求。
步骤S06B：OFCHF(Nofchf_ChargingDataService)创建一个新的话单(Open CDR)。
步骤S06C：OFCHF(Nofchf_ChargingDataService)向NF(CTF)发送回应。
步骤S06：NF(CTF)向用户交付使用可以使用的网络用量。
步骤S07：当用量上报管理触发器到达时(比如定时上报)触发*[用量上报过程]，*表示该过程可以被触发多次。
步骤S08A：NF(CTF)向OFCHF(Nofchf_ChargingDataService)发送更新计费数据请求。
步骤S08B：OFCHF(Nofchf_ChargingDataService)更新话单内容，比如流量或时间的累加，也可以根据部分话单出单条件(比如：按时间出单或按流量出单)输出部分话单。
步骤S08C：OFCHF(Nofchf_ChargingDataService)向NF(CTF)发送回应。
步骤S08：NF(CTF)预估需要后续需要使用的资源用量(但不超过OCHF下发的用量)，并直接向用户交付使用。
步骤S09：当配额管理触发器到达时(比如费率切换)触发*[配额管理过程]，*表示该过程可以被触发多次。
步骤S10：NF(CTF)预估后续需要使用的资源用量，并上报用户已经使用的用量。
步骤S11：OCHF(Nochf_ChargingService)根据用户已经使用的用量扣除用户费用(或套餐余量)，并调用ABMF，RF计算该用户允许继续使用的用量。
步骤S12：OCHF(Nochf_ChargingService)向NF(CTF)下发用量。
步骤S13A：NF(CTF)向OFCHF(Nofchf_ChargingDataService)发送更新计费数据请求。
步骤S13B：OFCHF(CDF)更新话单内容，比如流量或时间的累加，也可以根据部分话单出单条件(比如：按时间出单或按流量出单)输出部分话单。
步骤S13C：OFCHF(Nofchf_ChargingDataService)向NF(CTF)发送回应。
步骤S13：NF(CTF)向用户交付使用可以继续使用的网络用量。
步骤S14：用户本次使用的网络的过程结束，释放本次会话。
步骤S15A：NF(CTF)向OFCHF(Nofchf_ChargingDataService)发送结束计费数据请求。
步骤S15B：OFCHF(Nofchf_ChargingDataService)更新话单内容，比如流量或时间的累加，并关闭话单。
步骤S15C：OFCHF(Nofchf_ChargingDataService)向NF(CTF)发送回应：关闭话单。
步骤S15：NF(CTF)向OCHF(Nochf_ChargingService)发送释放会话的在线计费请求，并上报用户已经使用的用量。
步骤S16：OCHF(Nochf_ChargingService)根据用户已经使用的用量扣除用户费用(或套餐余量)。
步骤S17：OCHF(Nochf_ChargingService)向NF(CTF)发送回应消息，告知用户费用扣除成功。
步骤S18A：NF(CTF)向OFCHF(Nofchf_ChargingDataService)发送结束计费数据请求。
步骤S18B：OFCHF(Nofchf_ChargingDataService)更新话单内容，比如流量或时间的累加，并关闭话单。
步骤S18C：OFCHF(Nofchf_ChargingDataService)向NF(CTF)发送回应：关闭话单。
如图17所示，本申请实施例的和在线计费会话保持一致的离线计费出单步骤(在图中，NF集成CTF&CDF)。
步骤S01：用户请求使用网络资源。
步骤S02：NF(CTF)预估需要使用的资源用量。
步骤S03：NF(CTF)向OCHF(Nochf_ChargingService)发送在线计费请求。
步骤S04：OCHF(Nochf_ChargingService)调用ABMF，RF计算该用户允许使用的用量。
步骤S05：OCH(Nochf_ChargingService)F向NF(CTF)下发用量。
步骤S06A：NF(CDF)在本地创建一个话单(Open CDR)。
步骤S06：NF(CTF)向用户交付使用可以使用的网络用量。
步骤S07：当用量上报管理触发器到达时(比如定时上报)触发*[用量上报过程]，*表示该过程可以被触发多次。
步骤S08A：NF(CDF)更新话单内容，比如流量或时间的累加，也可以根据部分话单出单条件(比如：按时间出单或按流量出单)在本地生成部分话单。
步骤S08B：NF(CDF)向OFCHF(Nofchf_CDRStorageService)发送话单。
步骤S08C：OFCHF(Nofchf_CDRStorageService)接收并存储话单。
步骤S08D：OFCHF(Nofchf_CDRStorageService)发送回应消息。
步骤S08：NF(CTF)预估需要后续需要使用的资源用量(但不超过OCHF下发的用量)，并直接向用户交付使用。
步骤S09：当配额管理触发器到达时(比如费率切换)触发*[配额管理过程]，*表示该过程可以被触发多次。
步骤S10：NF(CTF)预估后续需要使用的资源用量，并上报用户已经使用的用量。
步骤S11：OCHF(Nochf_ChargingService)根据用户已经使用的用量扣除用户费用(或套餐余量)，并调用ABMF，RF计算该用户允许继续使用的用量。
步骤S12：OCHF(Nochf_ChargingService)向NF(CTF)下发用量。
步骤S13A：NF(CDF)更新话单内容，比如流量或时间的累加，也可以根据部分话单出单条件(比如：按时间出单或按流量出单)在本地生成部分话单。
步骤S13B：NF(CDF)向OFCHF(Nofchf_CDRStorageService)发送话单。
步骤S13C：OFCHF(Nofchf_CDRStorageService)接收并存储话单。
步骤S13D：OFCHF(Nofchf_CDRStorageService)发送回应消息。
步骤S13：NF(CTF)向用户交付使用可以继续使用的网络用量。
步骤S14：用户本次使用的网络的过程结束，释放本次会话。
步骤S15A：NF(CDF)在本地产生最后一张部分话单。
步骤S15B：NF(CDF)向OFCHF(Nofchf_CDRStorageService)发送话单。
步骤S15C：OFCHF(Nofchf_CDRStorageService)接收并存储话单。
步骤S15D：OFCHF(Nofchf_CDRStorageService)发送回应消息。
步骤S15：NF(CTF)向OCHF(Nochf_ChargingService)发送释放会话的在线计费请求，并上报用户已经使用的用量。
步骤S16：OCHF(Nochf_ChargingService)根据用户已经使用的用量扣除用户费用(或套餐余量)。
步骤S17：OCHF(Nochf_ChargingService)向NF(CTF)发送回应消息，告知用户费用扣除成功。
步骤S18A：NF(CDF)更新最后一张部分CDR。
步骤S18B：NF(CDF)上报最后一张CDR给OFCHF(Nofchf_ChargingStorageService)。
步骤S18C：OFCHF(Nofchf_ChargingStorageService)存储CDR。
步骤S18D：OFCHF(Nofchf_ChargingStorageService)发送响应。
如图18所示，本申请实施例的OCHF异常时在线计费转离线计费步骤(在图中，NF集成CTF)。
步骤S01：NF(CTF)向OCHF(Nochf_ChargingService)发送在线计费请求。
步骤S02：OCHF(Nochf_ChargingService)调用ABMF，RF计算该用户允许使用的用量。
步骤S03：OCHF(Nochf_ChargingService)向NF(CTF)下发用量。
步骤S04A：NF(CTF)向OFCHF(Nofchf_ChargingDataService)发送初始计费数据请求。
步骤S04B：OFCHF(Nofchf_ChargingDataService)创建一个新的话单(Open CDR)。
步骤S04C：OFCHF(Nofchf_ChargingDataService)向NF(CTF)发送回应。
步骤S04：NF(CTF)向用户交付使用可以使用的网络用量。
步骤S05：当配额管理触发器到达时(比如费率切换)。
步骤S06：NF(CTF)预估后续需要使用的资源用量，并上报用户已经使用的用量。
步骤S07：OCHF(Nochf_ChargingService)根据用户已经使用的用量扣除用户费用(或套餐余量)，并调用ABMF，RF计算该用户允许继续使用的用量。
步骤S08：OCHF(Nochf_ChargingService)向NF(CTF)下发用量，因出现异常导致NF(CTF)没有收到该下发消息。
步骤S09：触发[Change into Offline Charging]表示从在线计费转到离线计费过程。
步骤S10A：NF(CTF)向OFCHF(Nofchf_ChargingDataService)发送更新计费数据请求，并在该请求消息中标记在线计费第一次出现异常。
步骤S10B：OFCHF(Nofchf_ChargingDataService)更新话单内容并生成部分话单，该部分话单中含有第一次在线计费异常标记。
说明：该话单传输到Billing System后，需要和在线计费扣费记录核对，如果在线计费已经执行过扣费，则该话单不能再次作为扣费依据；否则Billing System可以依据该话单对用户进行补扣费用。
步骤S10C：OFCHF(Nofchf_ChargingDataService)向NF(CTF)发送回应。
步骤S10：NF(CTF)预估后续需要使用的资源用量，并直接向用户交付使用(此时在线计费已经异常，但是因为可以出离线计费话单，所以才可以允许用户继续使用网络)。
步骤S11：当用量上报管理触发器到达时(比如定时上报)触发*[用量上报过程]，*表示该过程可以被触发多次。
步骤S12A：NF(CTF)向OFCHF(Nofchf_ChargingDataService)发送更新计费数据请求，携 带后续在线计费异常标记(区别于第一次的在线计费异常消息)。
步骤S12B：OFCHF(Nofchf_ChargingDataService)更新话单内容，内容中含有后续在线计费异常标记；也可以根据部分话单出单条件(比如：按时间出单或按流量出单)输出部分话单，话单中也需要含有后续在线计费异常标记。
说明：因为在线计费最多只会扣除第一次出现异常时用户的费用，所以从这以后(包括该话单)传输到Billing System后，不需要和在线计费核对，可以直接依据该话单对用户进行补扣费用。
步骤S12C：OFCHF(Nofchf_ChargingDataService)向NF(CTF)发送回应。
步骤S12：NF(CTF)预估需要后续需要使用的资源用量，并直接向用户交付使用。
步骤S13：用户本次使用的网络的过程结束，释放本次会话。
步骤S14A：NF(CTF)向OFCHF(Nofchf_ChargingDataService)发送结束计费数据请求，携带后续在线计费异常标记。
步骤S14B：OFCHF(Nofchf_ChargingDataService)更新话单内容，比如流量或时间的累加，并且话单中也需要含有后续在线计费异常标记，并关闭话单。
步骤S14C：OFCHF(Nofchf_ChargingDataService)向NF(CTF)发送回应：关闭话单。
如图19所示，本申请实施例的OCHF异常时在线计费转离线计费步骤(在图中，NF集成CTF&CDF)。
步骤S01：NF(CTF)向OCHF(Nochf_ChargingService)发送在线计费请求。
步骤S02：OCHF(Nochf_ChargingService)调用ABMF，RF计算该用户允许使用的用量。
步骤S03：OCH(Nochf_ChargingService)F向NF(CDF)下发用量。
步骤S04A：NF(CDF)在本地创建一个话单(Open CDR)。
步骤S04：NF(CTF)向用户交付使用可以使用的网络用量。
步骤S05：当配额管理触发器到达时(比如费率切换)。
步骤S06：NF(CTF)预估后续需要使用的资源用量，并上报用户已经使用的用量。
步骤S07：OCHF(Nochf_ChargingService)根据用户已经使用的用量扣除用户费用(或套餐余量)，并调用ABMF，RF计算该用户允许继续使用的用量。
步骤S08：OCHF(Nochf_ChargingService)向NF(CTF)下发用量，因出现异常导致NF(CTF)没有收到该下发消息。
步骤S09：触发[Change into Offline Charging]表示从在线计费转到离线计费过程。
步骤S10A：NF(CDF)更新话单内容并生成部分话单，该部分话单中含有第一次在线计费 异常标记。
说明：该话单传输到Billing System后，需要和在线计费扣费记录核对，如果在线计费已经执行过扣费，则该话单不能再次作为扣费依据；否则Billing System可以依据该话单对用户进行补扣费用。
步骤S10B：NF(CDF)向OFCHF发送话单。
步骤S10C：OFCHF(Nofchf_CDRStorageService)接收并存储话单(或发送给CGF对话单进行处理)。
步骤S10D：OFCHF(Nofchf_CDRStorageService)发送回应消息。
步骤S10：NF(CTF)预估后续需要使用的资源用量，并直接向用户交付使用(此时在线计费已经异常，但是因为可以出离线计费话单，所以才可以允许用户继续使用网络)。
步骤S11：当用量上报管理触发器到达时(比如定时上报)触发*[用量上报过程]，*表示该过程可以被触发多次。
步骤S12A：NF(CDF)更新话单内容并生成部分话单，该部分话单中含有后续在线计费异常标记(区别于第一次的在线计费异常标记)。
说明：因为在线计费最多只会扣除第一次出现异常时用户的费用，所以从这以后(包括该话单)传输到Billing System后，不需要和在线计费核对，可以直接依据该话单对用户进行补扣费用。
步骤S12B：NF(CDF)向OFCHF(Nofchf_CDRStorageService)发送话单。
步骤S12C：OFCHF(Nofchf_CDRStorageService)接收并存储话单(或发送给CGF对话单进行处理)。
步骤S12D：OFCHF(Nofchf_CDRStorageService)发送回应消息。
步骤S12：NF(CTF)预估需要后续需要使用的资源用量，并直接向用户交付使用。
步骤S13：用户本次使用的网络的过程结束，释放本次会话。
步骤S14A：NF(CDF)在本地产生最后一张部分话单，该部分话单中含有后续在线计费异常标记(区别于第一次的在线计费异常标记)。
步骤S14B：NF(CDF)向OFCHF(Nofchf_CDRStorageService)发送话单。
步骤S14C：OFCHF(Nofchf_CDRStorageService)接收并存储话单(或发送给CGF对话单进行处理)。
步骤S14D：OFCHF(Nofchf_CDRStorageService)发送回应消息。
如图16所示，本申请实施例的离线话单携带被扣费用的步骤，在该场景中，NF集成CTF。
步骤S01：每次在NF(CTF)向OCHF(Nochf_ChargingService)上报用户实际网络用量时，OCHF(Nochf_ChargingService)根据用量扣除费用或套餐用量后，可以将所扣除的费用或套餐用量通过Online Charging Response消息带回给NF(CTF)。参考图16的步骤12和步骤17。
步骤S02：NF(CTF)收到OCHF(Nochf_ChargingService)的Online Charging Response后，将所扣除费用或套餐用量通过Charging Data Request带给OFCHF(Nofchf_ChargingDataService)。参考图16的步骤13A和步骤18A。
步骤S03：OFCHF(Nofchf_ChargingDataService)将所扣费用或套餐用量保存到话单。参考图16的步骤13B和步骤18B。
说明：如果要启用离线话单携带被扣费用功能，在[用量上报过程]过程中，不可以输出部分话单(因为此时输出部分话单中还没有费用信息)，参考图16的步骤8B。
如图17所示，本申请实施例的离线话单携带被扣费用的步骤，在该场景中，NF集成CTF&CDF。
步骤S01：每次在NF(CTF)向OCHF(Nochf_ChargingService)上报用户实际网络用量时，OCHF(Nochf_ChargingService)根据用量扣除费用或套餐用量后，可以将所扣除的费用或套餐用量通过Online Charging Response消息带回给NF(CTF)。参考图17的步骤12和步骤17。
步骤S02：NF(CTF)收到OCHF(Nochf_ChargingService)的Online Charging Response后，将所扣除费用或套餐用量更新到话单中。参考图17的步骤13A和步骤18A。
说明：如果要启用离线话单携带被扣费用功能，在[用量上报过程]过程中，不可以输出部分话单(因为此时输出部分话单中还没有费用信息)，参考图17的步骤8A。
如图20所示，本申请实施例的NF向多套OCHF发送计费请求时，防止重复计费的步骤，在该场景下，OCHF1(相当于上述实施例中的第三计费服务模块)已扣费。
步骤S01：用户请求使用网络资源。
步骤S02：NF(CTF)预估需要使用的资源用量。
步骤S03：NF(CTF)向OCHF1(Nochf_ChargingService)发送在线计费请求。
步骤S04：OCHF1(Nochf_ChargingService)调用ABMF，RF计算该用户允许使用的用量。
步骤S05：OCHF1(Nochf_ChargingService)向NF(CTF)下发用量。
步骤S06：NF(CTF)向用户交付使用可以使用的网络用量。
步骤S07：当配额管理触发器到达时(比如费率切换)。
步骤S08：NF(CTF)预估后续需要使用的资源用量，并上报用户已经使用的用量。
步骤S09：OCHF1(Nochf_ChargingService)根据用户已经使用的用量扣除用户费用(或套餐余量)，并调用ABMF，RF计算该用户允许继续使用的用量。
步骤S10：OCHF1(Nochf_ChargingService)触发异常。
步骤S11：实际OCHF1(Nochf_ChargingService)没办法向NF(CTF)下发用量。
步骤S12：NF(CTF)发现OCHF1(Nochf_ChargingService)异常，向OCHF2(Nochf_ChargingService)(相当于上述实施例中的第四计费服务模块)发送在线计费请求，请求消息中标记本次消息是可能重复的(possibly duplicate)，并上报本次用户已经使用的用量。
步骤S13：OCHF2(Nochf_ChargingService)根据用户本次使用的用量预留用户费用或套餐余量(实际并不扣除)，并调用ABMF，RF计算该用户允许继续使用的用量。
步骤S14：OCHF2(Nochf_ChargingService)向NF(CTF)下发用量。
步骤S15：NF(CTF)向用户交付使用可以继续使用的网络用量。
步骤S16：OCHF1(Nochf_ChargingService)异常恢复。
步骤S17：OCHF2向OCFH1(Nochf_ChargingQueryService)发送在线计费查询消息。
步骤S18：OCHF1(Nochf_ChargingQueryService)向OCHF2回应已扣费。
步骤S19：OCHF2(Nochf_ChargingService)释放/返还步骤13预留的用户费用。
如图21所示，本申请实施例的NF向多套OCHF发送计费请求时，防止重复计费的步骤，在该场景下，OCHF1(相当于上述实施例中的第三计费服务模块)未扣费。
步骤S01：用户请求使用网络资源。
步骤S02：NF(CTF)预估需要使用的资源用量。
步骤S03：NF(CTF)向OCHF1(Nochf_ChargingService)发送在线计费请求。
步骤S04：OCHF1(Nochf_ChargingService)调用ABMF，RF计算该用户允许使用的用量。
步骤S05：OCHF1(Nochf_ChargingService)向NF(CTF)下发用量。
步骤S06：NF(CTF)向用户交付使用可以使用的网络用量。
步骤S07：当配额管理触发器到达时(比如费率切换)。
步骤S08：NF(CTF)预估后续需要使用的资源用量，并上报用户已经使用的用量。
步骤S09：OCHF1(Nochf_ChargingService)触发异常。
步骤S10：OCHF1(Nochf_ChargingService)实际并没有除用户费用等操作。
步骤S11：实际OCHF1(Nochf_ChargingService)没办法向NF(CTF)下发用量。
步骤S12：NF(CTF)发现OCHF1(Nochf_ChargingService)异常，向 OCHF2(Nochf_ChargingService)(相当于上述实施例中的第四计费服务模块)发送在线计费请求，请求消息中标记本次消息是可能重复的(possibly duplicate)，并上报本次用户已经使用的用量。
步骤S13：OCHF2(Nochf_ChargingService)根据用户本次使用的用量预留用户费用或套餐余量(实际并不扣除)，并调用ABMF，RF计算该用户允许继续使用的用量。
步骤S14：OCHF2(Nochf_ChargingService)向NF(CTF)下发用量。
步骤S15：NF(CTF)向用户交付使用可以继续使用的网络用量。
步骤S16：OCHF1(Nochf_ChargingService)异常恢复。
步骤S17：OCHF2向OCFH1(Nochf_ChargingQueryService)发送在线计费查询消息。
步骤S18：OCHF1(Nochf_ChargingQueryService)向OCHF2回应没扣费。
步骤S19：OCHF2(Nochf_ChargingService)扣除步骤13预留的用户费用。
如图22所示，本申请实施例的NF(CTF)向多套OFCHF传输离线计费信息时，防止产生重复话单的步骤，在该场景下OFCHF1(相当于上述实施例中的第一计费服务模块)已存储更新的部分CDR。
步骤S01A：NF(CTF)向OFCHF1(Nofchf_ChargingDataService)发送初始计费数据请求。
步骤S01B：OFCHF1(Nofchf_ChargingDataService)创建一个新的话单。
步骤S01C：OFCHF1(Nofchf_ChargingDataService)向NF(CTF)发送回应。
步骤S01：NF(CTF)预估需要使用的资源用量，并直接向用户交付使用。
步骤S02：当用量上报管理触发器到达。
步骤S03A：NF(CTF)向OFCHF1(Nofchf_ChargingDataService)发送更新计费数据请求。
步骤S03B：OFCHF1(Nofchf_ChargingDataService)更新话单内容，比如流量或时间的累加，也可以根据部分话单出单条件(比如：按时间出单或按流量出单)输出部分话单。
步骤S03C：OFCHF1(Nofchf_ChargingDataService)触发异常。
步骤S03D：实际OFCHF1(Nofchf_ChargingDataService)无法向NF(CTF)发送回应。
步骤S03E：NF(CTF)发现OFCHF1(Nofchf_ChargingDataService)异常，向OFCHF2(Nochf_ChargingDataService)(相当于上述实施例中的第二计费服务模块)发送更新计费数据请求，请求消息中标记本次消息是可能重复的(possibly duplicate)。
步骤S03F：OFCHF2(Nofchf_ChargingDataService)创建一个新的话单。
步骤S03G：OFCHF2(Nofchf_ChargingDataService)向NF(CTF)发送回应。
步骤S03：NF(CTF)预估需要后续需要使用的资源用量，并直接向用户交付使用。
步骤S04：OFCHF1(Nofchf_ChargingDataService)异常恢复。
步骤S05：OFCHF2向OFCHF1(Nofchf_ChargingDataQueryService)发送计费数据查询消息。
步骤S06：OFCHF1(Nofchf_ChargingDataQueryService)向OFCHF2回应查询成功。
步骤S07：OFCHF2(Nofchf_ChargingDataService)不需要更新话单(即：不需要获取前一次Charging Data Request消息内容，再结合本次Charging Data Request消息更新话单)，但是需要将本次Charging Data Request作为开始消息，方便后续Charging Data Request更新话单用。
后续步骤说明：除非OFCHF2(Nofchf_ChargingDataService)异常，NF(CTF)将本次会话后续的计费数据消息应当继续发给OFCHF2。
如图23所示，本申请实施例的NF(CTF)向多套OFCHF传输离线计费信息时，防止产生重复话单的步骤，在该场景下，OFCHF1(相当于上述实施例中的第一计费服务模块)未存储部分CDR。
步骤S01A：NF(CTF)向OFCHF1(Nofchf_ChargingDataService)发送初始计费数据请求。
步骤S01B：OFCHF1(Nofchf_ChargingDataService)创建一个新的话单。
步骤S01C：OFCHF1(Nofchf_ChargingDataService)向NF(CTF)发送回应。
步骤S01：NF(CTF)预估需要使用的资源用量，并直接向用户交付使用。
步骤S02：当用量上报管理触发器到达。
步骤S03A：NF(CTF)向OFCHF1(Nofchf_ChargingDataService)发送更新计费数据请求。
步骤S03B：OFCHF1(Nofchf_ChargingDataService)触发异常。
步骤S03C：实际OFCHF1(Nofchf_ChargingDataService)无法更新话单。
步骤S03D：实际OFCHF1(Nofchf_ChargingDataService)无法向NF(CTF)发送回应。
步骤S03E：NF(CTF)发现OFCHF1(Nofchf_ChargingDataService)异常，向OFCHF2(Nochf_ChargingDataService)(相当于上述实施例中的第二计费服务模块)发送更新计费数据请求，请求消息中标记本次消息是可能重复的(possibly duplicate)。
步骤S03F：OFCHF2(Nofchf_ChargingDataService)创建一个新的话单。
步骤S03G：OFCHF2(Nofchf_ChargingDataService)向NF(CTF)发送回应。
步骤S03：NF(CTF)预估需要后续需要使用的资源用量，并直接向用户交付使用。
步骤S04：OFCHF1(Nofchf_ChargingDataService)异常恢复。
步骤S05：OFCHF2向OFCHF1(Nofchf_ChargingDataQueryService)发送计费数据查询消息。
步骤S06：OFCHF1(Nofchf_ChargingDataQueryService)向OFCHF2回应查询失败，并携带了上一个序号的Charging Data Request消息(参考图14)。
步骤S07：OFCHF2(Nofchf_ChargingDataService)根据上一个序号的Charging Data Request消息补充更新话单(即：获取前一次Charging Data Request消息内容，再结合本次Charging Data Request消息更新话单)。
后续步骤说明：除非OFCHF2(Nofchf_ChargingDataService)异常，NF(CTF)将本次会话后续的计费数据消息应当继续发给OFCHF2。
如图24所示，本申请实施例的NF(CDF)向多套OFCHF传输离线计费信息时，防止产生重复话单的步骤，在该场景下，OFCHF1已存储CDR。
步骤S01A：NF(CDF)在本地创建一个新的话单(Open CDR)。
步骤S01：NF(CDF)预估需要使用的资源用量，并直接向用户交付使用。
步骤S02：当用量上报管理触发器到达时(比如定时上报)触发用量上报。
步骤S03A：NF(CDF)更新话单内容，比如流量或时间的累加，也可以根据部分话单出单条件(比如：按时间出单或按流量出单)在本地生成部分话单。
步骤S03B：NF(CDF)向OFCHF1(Nofchf_CDRStorageService)发送话单。
步骤S03C：OFCHF1(Nofchf_CDRStorageService)接收并存储话单。
步骤S03D：OFCHF1(Nofchf_CDRStorageService)触发异常。
步骤S03E：实际OFCHF1(Nofchf_CDRStorageService)无法发送回应消息。
步骤S03F：NF(CDF)发现OFCHF1(Nofchf_CDRStorageService)异常，向OFCHF2(Nochf_CDRStorageService)发送话单，并标记该话单是可能重复的(possibly duplicate)。
步骤S03G：OFCHF2(Nofchf_CDRStorageService)接收并保存该话单到可疑话单缓存(意思是该话单目前还不能传输给Billing System)。
步骤S03H：OFCHF2(Nofchf_CDRStorageService)发送回应消息。
步骤S03：NF预估需要后续需要使用的资源用量，并直接向用户交付使用。
步骤S04：OFCHF1(Nofchf_CDRStorageService)异常恢复。
步骤S05：OFCHF2向OFCHF1(Nofchf_CDRQueryService)发送话单查询消息。
步骤S06：OFCHF1(Nofchf_CDRQueryService)向OFCHF2回应查询成功。
步骤S07：OFCHF2(Nofchf_CDRStorageService)在可疑话单缓存中取消(删除)该可能重复的话单。
后续步骤说明：如果OFCHF开启了话单合并功能，并且OFCHF2(Nofchf_ChargingDataService)没有发生异常，NF(CTF)将本次会话后续的计费数据消息应当继续发给OFCHF2。
如图25所示，本申请实施例的NF(CDF)向多套OFCHF传输离线计费信息时，防止产生重复话单的步骤，在该场景中，OFCHF1未存储CDR。
步骤S01A：NF(CDF)在本地创建一个新的话单(Open CDR)。
步骤S01：NF(CDF)预估需要使用的资源用量，并直接向用户交付使用。
步骤S02：当用量上报管理触发器到达时(比如定时上报)触发用量上报。
步骤S03A：NF(CDF)更新话单内容，比如流量或时间的累加，也可以根据部分话单出单条件(比如：按时间出单或按流量出单)在本地生成部分话单。
步骤S03B：NF(CDF)向OFCHF1(Nofchf_CDRStorageService)发送话单。
步骤S03C：OFCHF1(Nofchf_CDRStorageService)触发异常。
步骤S03D：OFCHF1(Nofchf_CDRStorageService)实际无法接收并存储话单。
步骤S03E：实际OFCHF1(Nofchf_CDRStorageService)无法发送回应消息。
步骤S03F：NF(CDF)发现OFCHF1(Nofchf_CDRStorageService)异常，向OFCHF2(Nochf_CDRStorageService)发送话单，并标记该话单是可能重复的(possibly duplicate)。
步骤S03G：OFCHF2(Nofchf_CDRStorageService)接收并保存该话单到可疑话单缓存(意思是该话单目前还不能传输给Billing System)。
步骤S03H：OFCHF2(Nofchf_CDRStorageService)发送回应消息。
步骤S03：NF预估需要后续需要使用的资源用量，并直接向用户交付使用。
步骤S04：OFCHF1(Nofchf_CDRStorageService)异常恢复。
步骤S05：OFCHF2向OFCHF1(Nofchf_CDRQueryService)发送话单查询消息。
步骤S06：OFCHF1(Nofchf_CDRQueryService)向OFCHF2回应查询失败。
步骤S07：OFCHF2(Nofchf_CDRStorageService)将可疑话单缓存中的该话单释放到正常存储(即：该话单现在可以传输给Billing System了)。
后续步骤说明：如果OFCHF开启了话单合并功能，并且OFCHF2(Nofchf_ChargingDataService)没有发生异常，NF(CTF)将本次会话后续的计费数据消息应当继续发给OFCHF2。
实施例2
本申请的实施例还提供了一种存储介质，该存储介质中存储有计算机程序，其中，该计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的计算机程序：
S1，网络功能模块在交付资源之后，将第一计费数据通过第一服务接口上报给第一计费服务模块，第一计费数据用于表示资源的使用情况，其中，第一计费服务模块和网络功能模块都设置在网络域；
S2，第一计费服务模块接收第一计费数据，第一计费数据用于计费域计费。
可选地，存储介质还被设置为存储用于执行上述实施例中任一项步骤的计算机程序，在此不再赘述。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，简称为ROM)、随机存取存储器(Random Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储计算机程序的介质。
本申请的实施例还提供了一种电子装置，包括存储器和处理器，该存储器中存储有计算机程序，该处理器被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
可选地，上述电子装置还可以包括传输设备以及输入输出设备，其中，该传输设备和上述处理器连接，该输入输出设备和上述处理器连接。
可选地，在本实施例中，上述处理器可以被设置为通过计算机程序执行以下步骤：
S1，网络功能模块在交付资源之后，将第一计费数据通过第一服务接口上报给第一计费服务模块，第一计费数据用于表示资源的使用情况，其中，第一计费服务模块和网络功能模块都设置在网络域；
S2，第一计费服务模块接收第一计费数据，第一计费数据用于计费域计费。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本申请的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个 集成电路模块来实现。这样，本申请不限制于任何特定的硬件和软件结合。
以上所述仅为本申请的优选实施例而已，并不用于限制本申请，对于本领域的技术人员来说，本申请可以有各种更改和变化。凡在本申请的原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (26)

  1. 一种计费系统，包括：
    第一计费服务模块和网络功能模块，其中，所述第一计费服务模块和所述网络功能模块都设置在网络域，所述网络功能模块在交付资源之后，将第一计费数据通过第一服务接口上报给所述第一计费服务模块，所述第一计费数据用于表示所述资源的使用情况；
    所述第一计费服务模块接收所述第一计费数据，所述第一计费数据用于计费域计费。
  2. 根据权利要求1所述的系统，其中，所述网络功能模块在交付资源之后，将第一计费数据通过第一服务接口上报给所述第一计费服务模块，所述第一计费服务模块接收所述第一计费数据，包括：
    所述网络功能模块根据所述资源的使用情况将更新的部分第一计费数据通过所述第一服务接口上报给所述第一计费服务模块；所述第一计费服务模块接收所述部分第一计费数据并根据所述部分第一计费数据对之前接收到的第一计费数据进行更新；或者，
    所述网络功能模块根据所述资源的使用情况对所述第一计费数据进行更新，并将更新后的所述第一计费数据通过所述第一服务接口上报给所述第一计费服务模块；所述第一计费服务模块接收所述更新后的第一计费数据。
  3. 根据权利要求1所述的系统，其中，在所述网络功能模块将第一计费数据通过第一服务接口上报给所述第一计费服务模块之后，所述系统还包括：
    当所述网络功能模块未收到所述第一计费服务模块反馈的第一响应时，将所述第一计费数据标记后上报给第二计费服务模块，其中，所述第一响应用于表示所述第一计费服务模块成功接收所述第一计费数据；
    所述第二计费服务模块接收被标记的所述第一计费数据。
  4. 根据权利要求3所述的系统，其中，在所述第二计费服务模块接收被标记的所述第一计费数据之后，所述系统还包括：
    所述第二计费服务模块临时存储所述被标记的第一计费数据；
    所述第二计费服务模块向所述第一计费服务模块发送查询请求，所述查询请求用于查询所述第一计费服务模块是否存储了与被标记的所述第一计费数据一致的第一计费数据；
    当所述第二计费服务模块接收到所述第一计费服务模块发送的查询成功响应时，删除临时存储的被标记的所述第一计费数据；
    当所述第二计费服务模块接收到所述第一计费服务模块发送的查询失败响应时，将 被标记的所述第一计费数据进行存储。
  5. 根据权利要求3所述的系统，其中，在所述第二计费服务模块接收被标记的所述第一计费数据之后，所述系统还包括：
    所述第二计费服务模块创建初始第一计费数据记录；
    所述第二计费服务模块向所述第一计费服务模块发送查询请求，所述查询请求用于查询所述第一计费服务模块是否存储了与被标记的所述第一计费数据一致的第一计费数据；
    当所述第二计费服务模块接收到所述第一计费服务模块发送的查询成功响应时，不更新所述初始第一计费数据记录；
    当所述第二计费服务模块接收到所述第一计费服务模块发送的查询失败响应时，根据被标记的所述第一计费数据更新所述初始第一计费数据记录，并存储更新后的所述初始第一计费数据记录。
  6. 根据权利要求1所述的系统，其中，所述系统还包括第三计费服务模块，其中所述第三计费服务模块设置在所述计费域，其中，所述网络功能模块通过第二服务接口向所述第三计费服务模块发送资源请求；
    所述第三计费服务模块根据预先设定的资源配额向所述网络功能模块下发资源额度；
    所述网络功能模块接收所述资源额度并根据所述资源额度交付资源。
  7. 根据权利要求6所述的系统，其中，所述系统还包括：
    所述第三计费服务模块根据接收到的资源请求进行批价和/或预扣费。
  8. 根据权利要求6所述的系统，其中，所述网络功能模块在交付所述资源之后，将第二计费数据通过第一服务接口上报给所述第一计费服务模块，所述第一计费服务模块接收所述第二计费数据，所述第二计费数据用于表示所述资源的使用情况。
  9. 根据权利要求8所述的系统，其中，所述网络功能模块将第二计费数据通过第一服务接口上报给所述第一计费服务模块，所述第一计费服务模块接收所述第二计费数据，包括：
    所述网络功能模块根据所述资源的使用情况将更新的部分第二计费数据通过所述第一服务接口上报给所述第一计费服务模块；所述第一计费服务模块接收所述部分第二计费数据并根据所述部分第二计费数据对之前接收到的第二计费数据进行更新；或者，
    所述网络功能模块根据所述资源的使用情况对所述第二计费数据进行更新，并将更 新后的所述第二计费数据通过所述第一服务接口上报给所述第一计费服务模块；所述第一计费服务模块接收所述更新后的第二计费数据。
  10. 根据权利要求6所述的系统，其中，在所述网络功能模块通过第二服务接口向所述第三计费服务模块发送资源请求之后，所述系统还包括：
    当所述网络功能模块未收到所述第三计费服务模块反馈的第二响应时，将所述资源请求标记后上报给第四计费服务模块，其中，所述第二响应用于表示所述第三计费服务模块成功接收所述资源请求；
    所述第四计费服务模块接收被标记的所述资源请求并根据预先设定的资源配额向所述网络功能模块下发资源额度。
  11. 根据权利要求10所述的系统，其中，在所述第四计费服务模块接收被标记的所述资源请求之后，所述系统还包括：
    所述第三计费服务模块根据接收到的被标记的所述资源请求进行预扣费；
    所述第四计费服务模块向所述第三计费服务模块发送扣费查询请求；
    当所述第四计费服务模块接收到所述第三计费服务模块反馈的已扣费响应时，返还预扣费用；
    当所述第四计费服务模块接收到所述第三计费服务模块反馈的未扣费响应时，所述第四计费服务模块根据接收到的被标记的所述资源请求进行扣费。
  12. 根据权利要求6所述的系统，其中，在所述网络功能模块通过第二服务接口向所述第三计费服务模块发送资源请求之后，所述系统还包括：
    当所述网络功能模块未收到所述第三计费服务模块反馈的第二响应时，将当前计费数据标记后上报给第一计费服务模块，其中，所述第二响应用于表示所述第三计费服务模块成功接收所述资源请求；
    所述第一计费服务模块接收被标记的所述当前计费数据并将被标记的所述当前计费数据存储。
  13. 一种计费方法，包括：
    网络功能模块在交付资源之后，将第一计费数据通过第一服务接口上报给第一计费服务模块，所述第一计费数据用于表示所述资源的使用情况，其中，所述第一计费服务模块和所述网络功能模块都设置在网络域；
    所述第一计费服务模块接收所述第一计费数据，所述第一计费数据用于计费域计费。
  14. 根据权利要求13所述的方法，其中，所述网络功能模块在交付资源之后，将 第一计费数据通过第一服务接口上报给所述第一计费服务模块，所述第一计费服务模块接收所述第一计费数据，包括：
    所述网络功能模块根据所述资源的使用情况将更新的部分第一计费数据通过所述第一服务接口上报给所述第一计费服务模块；所述第一计费服务模块接收所述部分第一计费数据并根据所述部分第一计费数据对之前接收到的第一计费数据进行更新；或者，
    所述网络功能模块根据所述资源的使用情况对所述第一计费数据进行更新，并将更新后的所述第一计费数据通过所述第一服务接口上报给所述第一计费服务模块；所述第一计费服务模块接收所述更新后的第一计费数据。
  15. 根据权利要求13所述的方法，其中，在所述网络功能模块将第一计费数据通过第一服务接口上报给所述第一计费服务模块之后，所述方法还包括：
    当所述网络功能模块未收到所述第一计费服务模块反馈的第一响应时，将所述第一计费数据标记后上报给第二计费服务模块，其中，所述第一响应用于表示所述第一计费服务模块成功接收所述第一计费数据；
    所述第二计费服务模块接收被标记的所述第一计费数据。
  16. 根据权利要求15所述的方法，其中，在所述第二计费服务模块接收被标记的所述第一计费数据之后，所述方法还包括：
    所述第二计费服务模块临时存储所述被标记的第一计费数据；
    所述第二计费服务模块向所述第一计费服务模块发送查询请求，所述查询请求用于查询所述第一计费服务模块是否存储了与被标记的所述第一计费数据一致的第一计费数据；
    当所述第二计费服务模块接收到所述第一计费服务模块发送的查询成功响应时，删除临时存储的被标记的所述第一计费数据；
    当所述第二计费服务模块接收到所述第一计费服务模块发送的查询失败响应时，将被标记的所述第一计费数据进行存储。
  17. 根据权利要求15所述的方法，其中，在所述第二计费服务模块接收被标记的所述第一计费数据之后，所述方法还包括：
    所述第二计费服务模块创建初始第一计费数据记录；
    所述第二计费服务模块向所述第一计费服务模块发送查询请求，所述查询请求用于查询所述第一计费服务模块是否存储了与被标记的所述第一计费数据一致的第一计费数据；
    当所述第二计费服务模块接收到所述第一计费服务模块发送的查询成功响应时，不更新所述初始第一计费数据记录；
    当所述第二计费服务模块接收到所述第一计费服务模块发送的查询失败响应时，根据被标记的所述第一计费数据更新所述初始第一计费数据记录，并存储更新后的所述初始第一计费数据记录。
  18. 根据权利要求13所述的方法，其中，所述方法还包括：
    所述网络功能模块通过第二服务接口向所述第三计费服务模块发送资源请求，其中，所述第三计费服务模块设置在所述计费域；
    所述第三计费服务模块根据预先设定的资源配额向所述网络功能模块下发资源额度；
    所述网络功能模块接收所述资源额度并根据所述资源额度交付资源。
  19. 根据权利要求13所述的方法，其中，所述方法还包括：
    所述第三计费服务模块根据接收到的资源请求进行批价和/或预扣费。
  20. 根据权利要求13所述的方法，其中，所述网络功能模块在交付所述资源之后，将第二计费数据通过第一服务接口上报给所述第一计费服务模块，所述第一计费服务模块接收所述第二计费数据，所述第二计费数据用于表示所述资源的使用情况。
  21. 根据权利要求20所述的方法，其中，所述网络功能模块将第二计费数据通过第一服务接口上报给所述第一计费服务模块，所述第一计费服务模块接收所述第二计费数据，包括：
    所述网络功能模块根据所述资源的使用情况将更新的部分第二计费数据通过所述第一服务接口上报给所述第一计费服务模块；所述第一计费服务模块接收所述部分第二计费数据并根据所述部分第二计费数据对之前接收到的第二计费数据进行更新；或者，
    所述网络功能模块根据所述资源的使用情况对所述第二计费数据进行更新，并将更新后的所述第二计费数据通过所述第一服务接口上报给所述第一计费服务模块；所述第一计费服务模块接收所述更新后的第二计费数据。
  22. 根据权利要求13所述的方法，其中，在所述网络功能模块通过第二服务接口向所述第三计费服务模块发送资源请求之后，所述方法还包括：
    当所述网络功能模块未收到所述第三计费服务模块反馈的第二响应时，将所述资源请求标记后上报给第四计费服务模块，其中，所述第二响应用于表示所述第三计费服务模块成功接收所述资源请求；
    所述第四计费服务模块接收被标记的所述资源请求并根据预先设定的资源配额向所述网络功能模块下发资源额度。
  23. 根据权利要求22所述的方法，其中，在所述第四计费服务模块接收被标记的所述资源请求之后，所述方法还包括：
    所述第三计费服务模块根据接收到的被标记的所述资源请求进行预扣费；
    所述第四计费服务模块向所述第三计费服务模块发送扣费查询请求；
    当所述第四计费服务模块接收到所述第三计费服务模块反馈的已扣费响应时，返还预扣费用；
    当所述第四计费服务模块接收到所述第三计费服务模块反馈的未扣费响应时，所述第四计费服务模块根据接收到的被标记的所述资源请求进行扣费。
  24. 根据权利要求13所述的方法，其中，在所述网络功能模块通过第二服务接口向所述第三计费服务模块发送资源请求之后，所述方法还包括：
    当所述网络功能模块未收到所述第三计费服务模块反馈的第二响应时，将当前计费数据标记后上报给第一计费服务模块，其中，所述第二响应用于表示所述第三计费服务模块成功接收所述资源请求；
    所述第一计费服务模块接收被标记的所述当前计费数据并将被标记的所述当前计费数据存储。
  25. 一种存储介质，其中，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行所述权利要求13至24任一项中所述的方法。
  26. 一种电子装置，包括存储器和处理器，其中，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行所述权利要求13至24任一项中所述的方法。
PCT/CN2020/090110 2019-06-26 2020-05-13 一种计费系统、方法、存储介质及电子装置 WO2020259116A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910562738.X 2019-06-26
CN201910562738.XA CN112153585B (zh) 2019-06-26 2019-06-26 一种计费系统、方法、存储介质及电子装置

Publications (1)

Publication Number Publication Date
WO2020259116A1 true WO2020259116A1 (zh) 2020-12-30

Family

ID=73869946

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/090110 WO2020259116A1 (zh) 2019-06-26 2020-05-13 一种计费系统、方法、存储介质及电子装置

Country Status (2)

Country Link
CN (1) CN112153585B (zh)
WO (1) WO2020259116A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114629734A (zh) * 2022-03-14 2022-06-14 阿里巴巴（中国）有限公司 话单处理方法、设备、系统及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101068150A (zh) * 2007-06-08 2007-11-07 华为技术有限公司 基于数据通信的计费方法、计费信息采集设备和计费系统
CN106550162A (zh) * 2012-08-08 2017-03-29 华为技术有限公司 计费控制的方法及计费触发装置、在线计费系统
WO2018032884A1 (zh) * 2016-08-15 2018-02-22 华为技术有限公司 一种计费方法、装置及系统

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101132289B (zh) * 2006-08-24 2011-04-13 华为技术有限公司 融合计费方法及计费系统及应用服务器及融合计费系统
CN101488864B (zh) * 2008-01-14 2011-12-21 朗讯科技公司 用于通信网络的计费系统和计费方法
US9438746B2 (en) * 2008-05-01 2016-09-06 Alcatel Lucent Centralized charging systems for offline charging and online charging
CN103702306A (zh) * 2012-09-27 2014-04-02 阿尔卡特朗讯 一种在ocs计费失败时对用户设备进行计费的方法与设备
US9883052B2 (en) * 2016-06-24 2018-01-30 Alcatel-Lucent Usa Inc. Systems and methods for avoiding double accounting upon session failover

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101068150A (zh) * 2007-06-08 2007-11-07 华为技术有限公司 基于数据通信的计费方法、计费信息采集设备和计费系统
CN106550162A (zh) * 2012-08-08 2017-03-29 华为技术有限公司 计费控制的方法及计费触发装置、在线计费系统
WO2018032884A1 (zh) * 2016-08-15 2018-02-22 华为技术有限公司 一种计费方法、装置及系统

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
3GPP: "Services, operations and procedures of charging using Service Based Interface (SBI) (Release 15)", 3GPP TS 32.290 V15.1.0, 30 September 2018 (2018-09-30), DOI: 20200731143332X *
ERICSSON: "Update of description of flows", 3GPP TSG-SA5 MEETING #119AD-HOC S5-184146, 28 June 2018 (2018-06-28), XP051470899, DOI: 20200731143010X *
ERICSSON: "Update of description of flows", 3GPP TSG-SA5 MEETING #119AD-HOC S5-184221, 28 June 2018 (2018-06-28), XP051470983, DOI: 20200731142729X *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114629734A (zh) * 2022-03-14 2022-06-14 阿里巴巴（中国）有限公司 话单处理方法、设备、系统及存储介质
CN114629734B (zh) * 2022-03-14 2024-04-26 阿里巴巴（中国）有限公司 话单处理方法、设备、系统及存储介质

Also Published As

Publication number Publication date
CN112153585A (zh) 2020-12-29
CN112153585B (zh) 2023-02-21

Similar Documents

Publication Publication Date Title
EP2297986B1 (en) Synchronizing real-time and off-line accounts for communications
US10248465B2 (en) Convergent mediation system with dynamic resource allocation
EP2083532B1 (en) Convergent mediation system with improved data transfer
RU2417536C2 (ru) Система и устройство для реализации дополнительной услуги извещения о начислении платы
CN101132289B (zh) 融合计费方法及计费系统及应用服务器及融合计费系统
EP2083533B1 (en) Convergent mediation system with dedicated online streams
US20110161248A1 (en) Online charging correlation in ims networks
CN103843374A (zh) 基于sy的集成的策略和计费控制
US20100145838A1 (en) Method, system, and apparatus for opening accounting data capabilities
KR100434431B1 (ko) 무선 네트워크상에서의 통합 과금 시스템 및 그 운영 방법
WO2009100669A1 (zh) 计费方法、控制装置、计费装置与计费系统
CN101106464B (zh) 一种码分多址分组数据业务实现预付费的方法
CN101902721A (zh) 一种基于时间的策略控制实现方法及其装置
CN109547957A (zh) 移动通信系统的计费方法及相应设备
CN114868374A (zh) 用于无锁通信网络资源配额共享的方法、系统和计算机可读介质
WO2020259116A1 (zh) 一种计费系统、方法、存储介质及电子装置
WO2020048532A1 (zh) Gx会话异常的处理方法及装置
US11349996B2 (en) Offline charging of communications services
WO2020008384A1 (en) Provision and recovery of network usage advances
CN102316432A (zh) 用量的监控方法和系统
CN101771984A (zh) 数据业务实时计费方法、装置及系统
KR20040064081A (ko) 무선 패킷 데이터 네트워크 상에서의 통합 과금 실시간한도 관리 시스템 및 그 운영 방법
CN104717627A (zh) 计费话单创建方法、数据业务计费方法及相关装置
WO2021008256A1 (zh) 一种计费方法、装置、系统及计算机可读存储介质
CN110300235A (zh) 一种通信业务计费方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20830901

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20830901

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 25/05/2022)

122 Ep: pct application non-entry in european phase

Ref document number: 20830901

Country of ref document: EP

Kind code of ref document: A1