WO2019042218A1 - 计费实现系统、计费实现方法及计费管理功能实体 - Google Patents

计费实现系统、计费实现方法及计费管理功能实体 Download PDF

Info

Publication number
WO2019042218A1
WO2019042218A1 PCT/CN2018/102024 CN2018102024W WO2019042218A1 WO 2019042218 A1 WO2019042218 A1 WO 2019042218A1 CN 2018102024 W CN2018102024 W CN 2018102024W WO 2019042218 A1 WO2019042218 A1 WO 2019042218A1
Authority
WO
WIPO (PCT)
Prior art keywords
charging
function entity
information
management function
policy
Prior art date
Application number
PCT/CN2018/102024
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 中兴通讯股份有限公司
Priority to EP18850699.2A priority Critical patent/EP3678329A1/en
Publication of WO2019042218A1 publication Critical patent/WO2019042218A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1432—Metric aspects
    • H04L12/1435—Metric aspects volume-based
    • 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/41—Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
    • 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
    • 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/66—Policy and charging system
    • 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/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8016—Rating or billing plans; Tariff determination aspects based on quality of service [QoS]
    • 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/82—Criteria or parameters used for performing billing operations
    • H04M15/8214—Data or packet based
    • 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/83—Notification aspects
    • H04M15/85—Notification aspects characterised by the type of condition triggering a notification
    • H04M15/852—Low balance or limit reached
    • 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/83—Notification aspects
    • H04M15/85—Notification aspects characterised by the type of condition triggering a notification
    • H04M15/853—Calculate maximum communication time or volume
    • 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/83—Notification aspects
    • H04M15/85—Notification aspects characterised by the type of condition triggering a notification
    • H04M15/854—Available credit
    • 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

Definitions

  • the present disclosure relates to, but is not limited to, the field of communication technology.
  • the service management function (SMF) is responsible for the service management such as session management
  • the billing information collection and billing information reporting function is also required, and the billing information is sent to the online meter.
  • OCS Online Charging System
  • BD Billing Center
  • some simple time billing and flow meter fees will occupy a lot of resources of SMF. Therefore, the load of the SMF needs to be alleviated.
  • the embodiment of the present application provides a charging implementation system, a charging implementation method, and a Charging Management Function (CMF).
  • CMF Charging Management Function
  • the embodiment of the present application provides a billing implementation system, including: a network function entity (NF), a user plane function entity (UPF), and a CMF; the CMF connects the NF and the user Functional entity
  • NF network function entity
  • UPF user plane function entity
  • CMF CMF
  • the CMF is configured to perform at least one of: delivering a charging policy to the user plane function entity or the NF; collecting charging information from the NF and the UPF; and reporting the charging information.
  • the embodiment of the present application provides a charging implementation method, including at least one of the following:
  • the CMF delivers a charging policy to the UPF or NF.
  • the CMF collects charging information from the NF and the UPF to be charged
  • the CMF reports the collected charging information.
  • an embodiment of the present application provides a CMF, including at least one of the following:
  • the policy delivery unit is configured to deliver a charging policy to the UPF or the NF.
  • An information collecting unit configured to collect charging information from the NF and the UPF to be charged
  • the information reporting unit is configured to report the collected charging information.
  • an embodiment of the present application provides a CMF, including: a memory and a processor, where the memory is configured to store a billing implementation program, where the billing implementation program is implemented by the processor to implement the second aspect. The steps of the billing implementation method.
  • an embodiment of the present application provides a computer readable medium, where a billing implementation program is stored, and the billing implementation program is implemented by a processor to implement the steps of the billing implementation method of the second aspect.
  • Figure 1 is a schematic diagram of the architecture of the 3GPP 23.501 standard
  • FIG. 2 is a schematic structural diagram of a charging implementation system according to an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a charging policy notification process according to an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a credit request flow process for online charging according to an embodiment of the present application.
  • FIG. 5 is a schematic diagram of a flow quota exhaustion process for online charging according to an embodiment of the present application
  • FIG. 6 is a schematic diagram of a flow quota exhaustion process for offline charging according to an embodiment of the present application
  • FIG. 7 is a schematic diagram of a time quota exhaustion process of online charging according to an embodiment of the present application.
  • FIG. 8 is a schematic diagram of a time quota exhaustion process of offline charging according to an embodiment of the present application.
  • FIG. 9 is a flow chart of charging triggered by a control plane according to an embodiment of the present application.
  • FIG. 10 is a schematic diagram of a CMF and an SMF of a UPF compatible merge deployment according to an embodiment of the present application
  • FIG. 11 is a schematic diagram of charging parameter transfer between a CMF, a UPF, and an SMF according to an embodiment of the present application;
  • FIG. 12 is a flowchart of a method for implementing charging according to an embodiment of the present application.
  • FIG. 13 is a schematic diagram of a CMF according to an embodiment of the present application.
  • FIG. 14 is another schematic diagram of a CMF according to an embodiment of the present application.
  • Figure 1 is a schematic diagram of the architecture of the 3GPP 23.501 standard, including the following structures: Network Open Functional Entity (NEF), Function Management Library (NRF), Policy Control Function Entity (PCF, Policy Control Function), User Data Management Entity (UDM, User Data) Management), Application Service Function (AF), Authentication Server Function (AUSF), Access Management Function (AMF), Service Management Function (SMF, Session Management Function) ), User Equipment (UE, User Equipment), (Wireless) Access Network ((R)AN, (Radio) Access Network), UPF, Data Network (DN, Data Network), Billing Center (BD, Billing Center) , Online Charging System (OCS, etc.).
  • NEF Network Open Functional Entity
  • NRF Network Open Functional Entity
  • PCF Policy Control Function Entity
  • UDM User Data Management Entity
  • UDM User Data Management Entity
  • AF Application Service Function
  • AUSF Authentication Server Function
  • AMF Access Management Function
  • SMF Session Management Function
  • UPF User Equipment
  • DN
  • Nnef represents the interface of the NEF
  • Nnrf represents the interface of the NRF
  • Npcf represents the interface of the PCF
  • Nudm represents the interface of the UDM
  • Naf represents the interface of the AF
  • Nausf represents the interface of the AUSF
  • Nsmf represents the interface of the SMF
  • N1 represents the UE and the AMF.
  • Inter-interface N2 represents the interface between AMF and (R)AN, N3 represents the interface between (R)AN and UPF, N4 represents the interface between SMF and UPF, and N6 represents the interface between UPF and DN.
  • the SMF needs to complete the charging information collection and charging information reporting function, and send the charging information to the OCS or BD.
  • FIG. 2 is a schematic structural diagram of a charging implementation system according to an embodiment of the present disclosure.
  • the charging implementation system provided in this embodiment includes at least: NF, UPF, and CMF; wherein, the CMF is connected to the NF and the UPF, and the CMF is configured to perform at least one of the following: charging the UPF or the NF. Policy; collecting billing information from NF and UPF; reporting billing information.
  • the NF can include an SMF.
  • the CMF is connected to the NF and the UPF to be charged, and is responsible for delivering the charging policy, collecting the charging information, and reporting the charging information.
  • the charging information collected by the CMF may include at least one of the following: online charging information, offline charging information. That is, the CMF can uniformly output online charging information and offline charging information.
  • the CMF is a unified export of all NFs that need to be billed. This simplifies the network connection and facilitates the subsequent billing maintenance and service management of the operator.
  • the communication between the CMF and the NF is implemented by using a Ncmf (Service-based Interface Presentation by CMF) interface, and communication is performed between the CMF and the UPF through the Ncmf-upf interface.
  • the interface provided by the CMF with the NF is Ncmf
  • the interface between the CMF and the UPF is Ncmf-upf.
  • the CMF can obtain the user's traffic information from the UPF through the Ncmf-upf, and can also send the charging policy to the UPF through the interface; the CMF can obtain the user information, the session information, and the charging policy by using the Ncmf between the NF and the NF. .
  • N1 represents an interface between the UE and the AMF
  • N2 represents an interface between the AMF and the (R) AN
  • N3 represents an interface between the (R) AN and the UPF
  • N4 represents an interface between the SMF and the UPF
  • N5 represents the interface between the PCF and the AF
  • N6 represents the interface between the UPF and the DN
  • N7 represents the interface between the SMF and the PCF
  • N9 represents the interface between the UPFs of different users.
  • the CMF may be configured to deliver a charging policy to the UPF in at least one of the following manners:
  • the CMF obtains the charging policy from the SMF or the PCF, and delivers the charging policy to the UPF.
  • the CMF obtains the charging policy from the OCS and sends the charging policy to the UPF.
  • the CMF can be configured to deliver a charging policy to the NF in the following manner: the CMF obtains the charging policy from the OCS, and delivers the charging policy to the NF (for example, SMF).
  • the NF for example, SMF
  • the charging policy may include quota information such as time or traffic corresponding to the service rate group (RG, Rating Group).
  • the charging policy may include: the user uses the data service to perform charging after 30 minutes; or the charging policy may include: charging after the user uses the data service to reach 30M.
  • the charging information may include: user information, traffic information, and session information;
  • CMF can be configured to collect billing information from NF and UPF in the following ways:
  • the CMF collects user information and session information from the NF;
  • the CMF collects traffic information from the UPF.
  • the CMF may be configured to collect traffic information from the UPF in at least one of the following ways:
  • the CMF queries the UPF for traffic information when the timer time set according to the charging policy arrives;
  • the CMF receives the traffic information notified by the UPF when the charging policy is met;
  • the CMF After triggering the update message on the control plane receiving the SMF notification, the CMF queries the UPF for the traffic information.
  • control plane trigger update message of the SMF notification may include a Public Land Mobile Network (PLMN) update message.
  • PLMN Public Land Mobile Network
  • the CMF has a charging policy reported by the user for 30 minutes.
  • the CMF sets the user's timer to 30 minutes.
  • the user uses the data service.
  • the timer expires for 30 minutes.
  • the CMF queries the UPF to query the user's traffic information. Then, the generated bill is reported to the billing center, and no SMF participation is required.
  • the CMF will send the charging policy reported by the 30M CDR to the UPF.
  • the UPF notifies the CMF of the traffic information, and the CMF generates the CDR. Reported to the billing center, no SMF participation is required.
  • the SMF notifies the CMF user that the PLMN has changed.
  • the CMF queries the online charging and offline charging policies of the user respectively. If the report needs to be reported, the CMF will generate the charging information for the response. And reported to the online billing and offline billing center.
  • the SMF only needs one message notification, and the CMF supports the simultaneous reporting of offline and online charging information, thereby reducing the SMF load.
  • the charging information may include at least one of the following: online charging information, offline charging information; the system of this embodiment may further include at least one of the following: OCS, BD; CMF connection OSC and BD At least one of;
  • the CMF can report the billing information in at least one of the following ways:
  • the CMF reports the online charging information to the OCS.
  • the CMF reports the offline charging information to the BD.
  • FIG. 3 is a schematic diagram of a charging policy notification process according to an embodiment of the present application. As shown in FIG. 3, the charging policy notification process in this embodiment includes the following steps:
  • the SMF obtains the charging policy of the user in the session creation or session update process, for example, obtaining a charging policy from the PCF, and notifying the CMF by using a charging policy notification message, where the charging policy notification message may include online charging. And offline charging policy;
  • the CMF After receiving the charging policy notification message, the CMF obtains the charging policy and the local charging policy, and then selects an appropriate charging policy according to the policy priority specified by the operator, and saves the charging policy to the charging context. And sending a charging policy notification message to the UPF, where the charging policy notification message carries an appropriate charging policy selected by the CMF;
  • the UPF After receiving the charging policy notification message, the UPF saves the charging policy carried in the charging policy context, and sends a charging policy notification response message to the CMF.
  • the CMF After receiving the charging policy notification response message sent by the UPF, the CMF sends a charging policy notification response message to the SMF.
  • FIG. 4 is a schematic diagram of a credit request flow process for online charging according to an embodiment of the present application. As shown in FIG. 4, the online charging credit request process of this embodiment includes the following steps:
  • the CMF identifies the current RG according to the information that the user service meets the request, and reports the CCR (CCR, Credit-Control-Request) message to the OCS, and requests the quota information from the OCS.
  • CCR Credit-Control-Request
  • S204 The OCS replies with a successful credit control response (CCA, Credit-Control-Answer), indicating that the service continues, and issuing quota information such as time or traffic corresponding to the RG;
  • CCA Credit-Control-Answer
  • the CMF After receiving the quota information such as the time or the traffic sent by the OCS, the CMF starts the timer if the time quota information is available, and if there is the traffic quota information, the CMF notifies the traffic quota information to the UPF through the service arrival response message. , UPF saves the received traffic quota information.
  • FIG. 5 is a schematic diagram of a flow quota exhaustion process for online charging according to an embodiment of the present application. As shown in FIG. 5, the flow quota exhaustion process of the online charging in this embodiment includes the following steps:
  • the CMF combines the user traffic, the time, and the user information into a CCR message, and reports it to the OCS to request a new quota from the OCS.
  • the OCS After receiving the CCR message, the OCS sends the corresponding quota information such as time or traffic through the CCA message.
  • the SMF and the CMF After receiving the quota information such as the time or the traffic sent by the OCS, the SMF and the CMF notify the UPF of the quota information that is newly sent by the OCS through the user quota exhaustion response message, and the UPF saves the received quota information.
  • FIG. 6 is a schematic diagram of a flow quota exhaustion process for offline charging according to an embodiment of the present application. As shown in FIG. 6, the flow quota exhaustion process of offline charging in this embodiment includes the following steps:
  • the UPF determines that the offline traffic quota is exhausted, and the UPF reports the user quota exhaustion request, and notifies the CMF that the offline traffic quota is exhausted and requests a new quota.
  • the CMF sends new quota information such as traffic to the UPF.
  • the CMF stores the CDR (Call Detail Record, Call Detail Record) message, stores the charging information, and sends the CDR message to the BD through the Bx interface for offline charging.
  • CDR Call Detail Record, Call Detail Record
  • FIG. 7 is a schematic diagram of a time quota exhaustion process of online charging according to an embodiment of the present application. As shown in FIG. 7, the time quota exhaustion process of the online charging in this embodiment includes the following steps:
  • S501 The online time quota is valid in the process of using the service, and the CMF is configured with a timer, and the user uses the service normally;
  • the CMF determines that the online time quota is exhausted, and the CMF sends a user traffic query request to the UPF; that is, the CMF queries the UPF for the user's traffic information.
  • the UPF reports the traffic information of the user to the CMF by using a user traffic query response message.
  • the S504 and the CMF form a CCR message, which is reported to the OCS, and requests a new quota from the OCS.
  • the S50 After receiving the CCR message, the S50 sends the corresponding time or traffic quota information to the CMF through the CCA message.
  • the CMF receives the quota information such as the time or the traffic delivered by the OCS, and notifies the UPF to determine the charging policy according to the new quota information.
  • FIG. 8 is a schematic diagram of a time quota exhaustion process of offline charging according to an embodiment of the present application. As shown in FIG. 8, the time quota exhaustion process of offline charging in this embodiment includes the following steps:
  • the CMF determines that the offline time quota is exhausted, and the CMF sends a user traffic query request to the UPF, that is, the CMF queries the UPF for the user's traffic information.
  • the UPF reports the traffic information of the user to the CMF by using a user traffic query response message.
  • the CMF generates a CDR message by using the traffic, the time, and the user information, and sends the CDR message to the BD through the Bx interface, so that the BD performs offline charging.
  • FIG. 9 is a flow chart of charging triggered by a control plane according to an embodiment of the present application. As shown in FIG. 9, the charging process triggered by the control plane of this embodiment includes the following steps:
  • S701 The user normally uses the business process
  • the user movement causes the user's PLMN to change (or may be another control plane trigger message), and the SMF sends a notification message to the CMF to notify the CMF user of the PLMN change;
  • the CMF sends a user traffic query request to the UPF, that is, the CMF to the UPF queries the user for online charging and offline charging traffic information;
  • the UPF reports the traffic information of the user to the CMF through the user traffic query response message.
  • the CMF combines the user traffic, the time, and the user information into a CCR message, reports the online charging information to the OCS, and requests a new quota from the OCS.
  • the CMF generates a CDR message by using the user traffic, time, and user information, and sends the CDR message to the BD through the Bx interface;
  • the OCS After receiving the CCR message, the OCS sends the corresponding time or traffic quota information through the CCA message.
  • the CMF receives the quota information such as the time or the traffic sent by the OCS, and notifies the UPF to install the charging policy according to the new quota information.
  • FIG. 10 is a schematic diagram of a CMF and an SMF of a UPF compatible merge deployment according to an embodiment of the present application.
  • the process of the UPF compatible merged CMF and SMF (hereinafter referred to as ComboSMF) in this embodiment includes the following steps:
  • the ComboSMF obtains the charging policy of the user (for example, obtains the charging policy from the PCF) in the process of session creation or session update, saves the charging policy related to the control plane, and charges the user-related charging policy.
  • the policy notification message is notified to the UPF, which may include a user-side charging policy for online charging and offline charging;
  • the S802 and the UPF After receiving the charging policy, the S802 and the UPF save the charging policy to the charging policy context, and send a charging policy notification response message to the ComboSMF.
  • the user sends a traffic request message to the UPF to query the user's traffic and other information.
  • the S804 After receiving the user traffic request message, the S804 obtains the traffic information of the user, and returns a user traffic response message to the ComboSMF.
  • the UPF may actively send a traffic threshold arrival request message to the ComboSMF, and continue to request the user's traffic quota.
  • the ComboSMF After receiving the S806 and the ComboSMF, the ComboSMF saves the related data of the user, generates a bill or CCR message to notify the OCS, and returns a traffic threshold arrival response message to the UPF.
  • FIG. 11 is a schematic diagram of charging parameter transfer between CMF, UPF, and SMF according to an embodiment of the present application. As shown in FIG. 11, the charging parameter flow between the CMF, the UPF, and the SMF in this embodiment includes the following steps:
  • S901 SMF, in the session to create the UPF, the protocol data unit (PDU, Protocol Data Unit) session ID, quality of service (QoS, Quality of Service) flow ID or bearer ID and user QoS information in the SMF and UPF Associated to the same QoS flow or bearer under the same session;
  • PDU Protocol Data Unit
  • QoS Quality of Service
  • bearer ID user QoS information
  • S902 When the SMF performs the charging start message to notify the CMF, the session ID of the PDU, the ID of the QoS flow, or the bearer ID parameter and the charging policy are carried to the CMF;
  • the CMF when the final charging policy is determined according to the policy, together with the session ID of the PDU and the ID or bearer ID of the QoS flow, is sent to the UPF through the charging policy notification message; after the UPF receives the message, according to the session of the PDU ID and bearer ID of the ID and QoS flow, find the current QoS flow or bearer, and save the charging policy;
  • the UPF has the user's packet arrival, obtains the service identifier (SI, Session ID) and the RG corresponding to the current packet according to the charging policy, and notifies the CMF in the message that the quota arrives; the CMF can fill in the CDR according to the SI and the RG. It is reported to the billing center to charge the user.
  • SI service identifier
  • Session ID the service identifier
  • RG the RG corresponding to the current packet according to the charging policy
  • the embodiment of the present application further provides a charging implementation method, including at least one of the following: the CMF sends a charging policy to the UPF or the NF; the CMF collects the charging information from the NF and the UPF to be charged; and the CMF reports the collected accounting. Fee information.
  • FIG. 12 is a flowchart of a method for implementing charging according to an embodiment of the present application. As shown in FIG. 12, the charging implementation method provided in this embodiment includes the following steps:
  • S1201 The CMF sends a charging policy to the UPF.
  • the CMF collects charging information from the NF and the UPF to be charged;
  • the CMF and the NF communicate through the Ncmf interface
  • the CMF and the UPF communicate through the Ncmf-upf interface.
  • the CMF issuing the charging policy to the UPF may include at least one of the following:
  • the CMF obtains the charging policy from the SMF or the PCF, and delivers the charging policy to the UPF.
  • the CMF obtains the charging policy from the OCS and sends the charging policy to the UPF.
  • the CMF sends the charging policy to the NF
  • the method includes: the CMF obtains the charging policy from the OCS, and delivers the charging policy to the NF.
  • the NF can include an SMF.
  • the charging information may include: user information, traffic information, and session information;
  • S1202 can include:
  • the CMF collects user information and session information from the NF;
  • the CMF collects traffic information from the UPF.
  • the CMF collects traffic information from the UPF, which may include at least one of the following:
  • the CMF queries the UPF for traffic information when the timer time set according to the charging policy arrives;
  • the CMF receives the traffic information notified by the UPF when the charging policy is met;
  • the CMF After triggering the update message on the control plane receiving the SMF notification, the CMF queries the UPF for the traffic information.
  • the charging information may include at least one of the following: online charging information, offline charging information;
  • S1203 may include at least one of the following:
  • the CMF reports the online charging information to the OCS.
  • the CMF reports the offline charging information to the BD.
  • FIG. 13 is a schematic diagram of a CMF according to an embodiment of the present application. As shown in FIG. 13, the CMF provided in this embodiment includes at least one of the following:
  • the policy issuance unit 1300 is configured to deliver a charging policy to the NF or the UPF.
  • the information collecting unit 1302 is configured to collect charging information from the NF and the UPF to be charged;
  • the information reporting unit 1304 is configured to report the collected charging information.
  • the CMF and the NF communicate through the Ncmf interface
  • the CMF and the UPF communicate through the Ncmf-upf interface.
  • the policy issuance unit 1300 may be configured to deliver a charging policy to the UPF in at least one of the following manners:
  • the policy issuance unit 1300 can be configured to deliver a charging policy to the NF in the following manner: the charging policy is obtained from the OCS, and the charging policy is delivered to the NF.
  • the NF can include an SMF.
  • the charging information may include: user information, traffic information, and session information;
  • the information collecting unit 1302 is configured to collect billing information in the following manner:
  • the information collection unit 1302 is configured to collect traffic information from the UPF in at least one of the following ways:
  • the UPF is queried for the traffic information
  • the UPF is queried for the traffic information.
  • the charging information may include at least one of the following: online charging information, offline charging information;
  • the information reporting unit 1304 is configured to report the collected charging information by using at least one of the following methods:
  • the offline charging information is reported to the BD.
  • FIG. 14 is another schematic diagram of a CMF according to an embodiment of the present application.
  • the CMF 1400 of this embodiment includes a memory 1404 and a processor 1402. It will be understood by those skilled in the art that the CMF structure shown in FIG. 14 does not constitute a limitation on the CMF 1400, which may include more or less components than those illustrated, or a combination of certain components, or different component arrangements. .
  • the processor 1402 may include, but is not limited to, a processing device such as a microprocessor (MCU) or a Field-Programmable Gate Array (FPGA).
  • the memory 1404 can be configured as a software program or module that stores application software, such as program instructions or modules corresponding to the billing implementation method in the present embodiment, and the processor 1402 executes each by executing a software program or module stored in the memory 1404.
  • the function application and data processing, that is, the billing implementation method of the embodiment is implemented.
  • Memory 1404 can include high speed random access memory and can also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory.
  • memory 1404 can further include memory remotely located relative to processor 1402, which can be connected to CMF 1400 via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • the CMF 1400 described above may also include a communication unit 1406; the communication unit 1406 may receive or transmit data via a network.
  • communication unit 1406 can be a radio frequency (RF) module configured to communicate with the Internet wirelessly.
  • RF radio frequency
  • the CMF provided in this embodiment may be implemented by software, hardware, or a combination of software and hardware. However, this application is not limited thereto.
  • the embodiment of the present application further provides a computer readable medium storing a billing implementation program, where the billing implementation program is implemented by a processor to implement the steps of the billing implementation method.
  • Such software may be distributed on a machine-readable medium, such as a computer-readable medium, which may include computer storage media (or non-transitory media) and communication media (or transitory media).
  • a machine-readable medium such as a computer-readable medium, which may include computer storage media (or non-transitory media) and communication media (or transitory media).
  • computer storage medium includes volatile and nonvolatile, implemented in any method or technology configured to store information, such as computer readable instructions, data structures, program modules, or other data. Sex, removable and non-removable media.
  • Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridge, magnetic tape, magnetic disk storage or other magnetic storage device, or may Any other medium that is configured to store the desired information and that can be accessed by the computer.
  • communication media typically includes computer readable instructions, data structures, program modules or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and can include any information delivery media. .

Abstract

本公开实施例提供了一种计费实现系统、方法、计费管理功能实体，其中，计费实现系统包括：网络功能实体、用户面功能实体以及计费管理功能实体；所述计费管理功能实体连接所述网络功能实体和所述用户面功能实体；所述计费管理功能实体配置为执行以下至少之一：向所述用户面功能实体或网络功能实体下发计费策略；从所述网络功能实体和所述用户面功能实体收集计费信息；上报所述计费信息。

Description

计费实现系统、计费实现方法及计费管理功能实体
相关申请的交叉引用
本申请基于申请号为201710766197.3、申请日为2017年08月30日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本公开涉及但不限于通信技术领域。
背景技术
移动通信经历了从语音到数据业务的飞跃式发展，深刻地改变了人们的生活方式，也极大地促进了社会和经济的快速发展。移动互联网和物联网作为未来移动通信发展的主要推动力，为第五代移动通信(5G，Fifth Generation)提供了广阔的前景。5G系统支持的数据流量千倍增长，设备以千亿数量连接。第三代合作伙伴计划(3GPP，Third Generation Partnership Project，)提供了5G的新架构，支持数据连接和服务，使部署能够使用网络功能虚拟化(NFV，Network Function Virtualization)来满足5G的网络要求。
在5G架构中，业务管理功能实体(SMF，Session Management Function)在负责完成会话管理等业务管理的情况下，还需要完成计费信息采集和计费信息上报功能，把计费信息送到在线计费系统(OCS，Online Charging System)或者计费中心(BD，Billing Center)。其中，一些单纯的时间计费和流量计费等会占用SMF的大量资源。因此，SMF的负荷有待减轻。
发明内容
以下是对本文详细描述的主题的概述。
本申请实施例提供一种计费实现系统、计费实现方法及计费管理功能实体(CMF，Charging Management Function)。
第一方面，本申请实施例提供一种计费实现系统，包括：网络功能实体(NF)、用户面功能实体(UPF，User Plane Function)以及CMF；所述CMF连接所述NF和所述用户面功能实体；
所述CMF配置为执行以下至少之一：向所述用户面功能实体或NF下发计费策略；从所述NF和所述UPF收集计费信息；上报所述计费信息。
第二方面，本申请实施例提供一种计费实现方法，包括以下至少之一：
CMF向UPF或NF下发计费策略；
所述CMF从待计费的NF和UPF收集计费信息；
所述CMF上报收集到的计费信息。
第三方面，本申请实施例提供一种CMF，包括以下至少之一：
策略下发单元，配置为向UPF或NF下发计费策略；
信息收集单元，配置为从待计费的NF和UPF收集计费信息；
信息上报单元，配置为上报收集到的计费信息。
第四方面，本申请实施例提供一种CMF，包括：存储器以及处理器，所述存储器配置为存储计费实现程序，所述计费实现程序被所述处理器执行时实现上述第二方面的计费实现方法的步骤。
第五方面，本申请实施例提供一种计算机可读介质，存储有计费实现程序，所述计费实现程序被处理器执行时实现上述第二方面的计费实现方法的步骤。
在本申请实施例中，通过扩展3GPP 23.501协议，新增一个CMF，在5G架构下进行计费策略下发、计费信息采集和上报，从而减轻了SMF的负荷，简化了网络连接，方便运营商的计费维护和业务管理。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图说明
图1为3GPP 23.501标准的架构示意图；
图2为本申请实施例提供的计费实现系统的架构示意图；
图3为本申请实施例的计费策略通知流程的示意图；
图4为本申请实施例的在线计费的信用请求流程的示意图；
图5为本申请实施例的在线计费的流量配额耗尽流程的示意图；
图6为本申请实施例的离线计费的流量配额耗尽流程的示意图；
图7为本申请实施例的在线计费的时间配额耗尽流程的示意图；
图8为本申请实施例的离线计费的时间配额耗尽流程的示意图；
图9为本申请实施例的控制面触发的计费流程图；
图10为本申请实施例的UPF兼容合并部署的CMF和SMF的示意图；
图11为本申请实施例的CMF、UPF及SMF之间的计费参数传递示意图；
图12为本申请实施例提供的计费实现方法的一种流程图；
图13为本申请实施例提供的CMF的示意图；
图14为本申请实施例提供的CMF的另一示意图。
具体实施方式
以下结合附图对本申请实施例进行详细说明，应当理解，以下所说明的实施例仅用于说明和解释本申请，并不用于限定本申请。
图1为3GPP 23.501标准的架构示意图，包括以下结构：网络开放功能实体(NEF)、功能管理库(NRF)、策略控制功能实体(PCF，Policy Control Function)、用户数据管理实体(UDM，User Data Management)、应用服务功能实体(AF，Application Function)、鉴权服务器功能实体(AUSF，Authentication Server Function)、接入管理功能实体(AMF，Access Management Function)、业务管理功能实体(SMF，Session Management Function)、用户设备(UE，User Equipment)、(无线)接入网络((R)AN， (Radio)Access Network)、UPF、数据网络(DN，Data Network)、计费中心(BD，Billing Center)、在线计费系统(OCS，Online Charging System)等。其中，Nnef表示NEF的接口，Nnrf表示NRF的接口，Npcf表示PCF的接口，Nudm表示UDM的接口，Naf表示AF的接口，Nausf表示AUSF的接口，Nsmf表示SMF的接口；N1表示UE和AMF之间的接口，N2表示AMF和(R)AN之间的接口，N3表示(R)AN和UPF之间的接口，N4表示SMF和UPF之间的接口，N6表示UPF和DN之间的接口。
在上述架构中，SMF在负责完成会话管理等业务管理的情况下，还需要完成计费信息采集和计费信息上报功能，把计费信息送到OCS或者BD。
图2为本申请实施例提供的计费实现系统的架构示意图。如图2所示，本实施例提供的计费实现系统，至少包括：NF、UPF以及CMF；其中，CMF连接NF和UPF，CMF配置为执行以下至少之一：向UPF或NF下发计费策略；从NF和UPF收集计费信息；上报计费信息。示例性地，NF可以包括SMF。
在本实施例中，CMF连接待计费的NF和UPF，负责下发计费策略、收集计费信息以及上报计费信息。示例性地，CMF收集的计费信息可以包括以下至少之一：在线计费信息、离线计费信息。即CMF可以统一输出在线计费信息和离线计费信息。CMF是所有需要计费的NF的统一出口，如此，简化了网络连接，方便了运营商后续的计费维护和业务管理。
在本实施例中，CMF与NF之间通过Ncmf(Service-based interface exhibited by CMF)接口实现通信，CMF和UPF之间通过Ncmf-upf接口实现通信。换言之，CMF提供的与NF之间的接口为Ncmf，CMF和UPF之间的接口为Ncmf-upf。示例性地，CMF可以通过Ncmf-upf从UPF获取用户的流量信息，还可以通过该接口向UPF下发计费策略；CMF可以通过和NF之间的Ncmf获取用户信息、会话信息和计费策略。
在图2中，N1表示UE和AMF之间的接口，N2表示AMF和(R)AN之间的接口，N3表示(R)AN和UPF之间的接口，N4表示SMF和UPF之间的接口，N5表示PCF和AF之间的接口，N6表示UPF和DN之间的接口，N7表示SMF和PCF之间的接口，N9表示不同用户的UPF之间的接 口。
在示例性实施方式中，CMF可以配置为通过以下至少之一方式向UPF下发计费策略：
CMF从SMF或PCF获取计费策略，并向UPF下发计费策略；
CMF从OCS获取计费策略，并向UPF下发计费策略；
CMF可以配置为通过以下方式向NF下发计费策略：CMF从OCS获取计费策略，并向NF(比如，SMF)下发计费策略。
其中，计费策略可以包括业务费率组(RG，Rating Group)对应的时间或流量等配额信息。比如，计费策略可以包括：用户使用数据业务30分钟后进行计费；或者，计费策略可以包括：用户使用数据业务的流量达到30M后进行计费。
在示例性实施方式中，计费信息可以包括：用户信息、流量信息以及会话信息；
CMF可以配置为通过以下方式从NF和UPF收集计费信息：
CMF从NF收集用户信息以及会话信息；
CMF从UPF收集流量信息。
在示例性实施方式中，CMF可以配置为通过以下至少之一方式从UPF收集流量信息：
CMF在根据计费策略设置的定时器时间到达时，向UPF查询流量信息；
CMF接收UPF在满足计费策略时通知的流量信息；
CMF在接收到SMF通知的控制面触发更新消息后，向UPF查询流量信息。
示例性地，SMF通知的控制面触发更新消息可以包括公共陆地移动网络(PLMN，Public Land Mobile Network)更新消息。
比如，CMF上用户有30分钟上报的计费策略，CMF会设置用户的定时器的定时时间为30分钟，用户使用数据业务，定时器的定时时间到达30分钟，CMF到UPF查询用户的流量信息，然后生成话单上报给计费中心， 不需要SMF参与。
比如，CMF上用户有30M话单上报的计费策略，CMF会把30M话单上报的计费策略下发给UPF，UPF在用户的流量达到30M时，向CMF通知流量信息，CMF生成话单上报给计费中心，不需要SMF参与。
比如，用户的位置发生移动，PLMN发生了改变，SMF通知CMF用户的PLMN发生了改变，CMF分别查询用户的在线计费和离线计费策略，如果需要上报，CMF会产生响应的计费信息，并上报给在线计费和离线计费中心。SMF只需要一次消息通知，CMF支持同时上报离线和在线计费的计费信息，从而减轻了SMF负荷。
在示例性实施方式中，计费信息可以包括以下至少之一：在线计费信息、离线计费信息；本实施例的系统还可以包括以下至少之一：OCS、BD；CMF连接OSC和BD中的至少之一；
CMF可以通过以下至少之一方式上报计费信息：
CMF将在线计费信息上报给OCS；
CMF将离线计费信息上报给BD。
下面通过多个示例对本申请的计费实现系统的处理流程进行说明。
图3为本申请实施例的计费策略通知流程的示意图。如图3所示，本实施例的计费策略通知流程包括以下步骤：
S101、SMF在会话创建或者会话更新流程，获取到用户的计费策略(比如，从PCF获取计费策略等)，通过计费策略通知消息通知CMF，计费策略通知消息中可以包括在线计费和离线计费的计费策略；
S102、CMF收到计费策略通知消息后，获取其中携带的计费策略和本地的计费策略，然后，可以根据运营商规定的策略优先级，选择合适的计费策略，保存到计费上下文，并发送计费策略通知消息给UPF，该计费策略通知消息中携带CMF选择出的合适的计费策略；
S103、UPF收到计费策略通知消息后，保存其中携带的计费策略到计费策略上下文，并发送计费策略通知响应消息给CMF；
S104、CMF收到UPF发送的计费策略通知响应消息后，发送计费策略 通知响应消息给SMF。
图4为本申请实施例的在线计费的信用请求流程的示意图。如图4所示，本实施例的在线计费的信用请求流程包括以下步骤：
S201、UE接入成功，其中，关于UE的附着过程可以参照3GPP 23.502协议流程，故于此不再赘述；
S202、UE使用业务时，UPF发现用户的新业务，向CMF上报用户业务到达请求；
S203、CMF根据用户业务达到请求携带的信息，识别出当前的RG，通过信用控制请求(CCR，Credit-Control-Request)消息上报给OCS，并向OCS请求配额信息；
S204、OCS回复成功的信用控制应答(CCA，Credit-Control-Answer)，指示业务继续，并下发RG对应的时间或者流量等配额信息；
S205、CMF收到OCS下发的时间或者流量等配额信息后，若有时间配额信息，则CMF启动定时器；若有流量配额信息，则CMF通过业务到达响应消息，将流量配额信息通知给UPF，UPF保存接收到的流量配额信息。
图5为本申请实施例的在线计费的流量配额耗尽流程的示意图。如图5所示，本实施例的在线计费的流量配额耗尽流程包括以下步骤：
S301、用户使用业务过程中，在线流量配额生效，正常使用业务；
S302、用户使用业务过程中，UPF判断在线流量配额耗尽，UPF上报用户配额耗尽请求，向CMF通知给用户的在线流量配额耗尽，请求新的配额；
S303、CMF将用户流量、时间以及用户信息组成CCR消息，上报给OCS，向OCS请求新的配额；
S304、OCS接收到CCR消息后，通过CCA消息下发对应的时间或者流量等配额信息；
S305、CMF收到OCS下发的时间或者流量等配额信息后，通过用户配额耗尽响应消息将OCS新下发的配额信息通知给UPF，UPF保存接收到的配额信息。
图6为本申请实施例的离线计费的流量配额耗尽流程的示意图。如图6所示，本实施例的离线计费的流量配额耗尽流程包括以下步骤：
S401、用户使用业务过程中，离线流量配额生效，正常使用业务；
S402、用户使用业务过程中，UPF判断离线流量配额耗尽，UPF上报用户配额耗尽请求，向CMF通知用户的离线流量配额耗尽，请求新的配额；
S403、CMF向UPF下发新的流量等配额信息；
S404、CMF通过生成CDR(Call Detail Record，呼叫详细记录，即话单)消息，存放计费信息，并通过Bx接口把CDR消息发给BD，用于进行离线计费。
图7为本申请实施例的在线计费的时间配额耗尽流程的示意图。如图7所示，本实施例的在线计费的时间配额耗尽流程包括以下步骤：
S501、用户使用业务过程中，在线时间配额生效，CMF设置有定时器，用户正常使用业务；
S502、用户使用业务过程中，CMF判断在线时间配额耗尽，CMF向UPF发送用户流量查询请求；即CMF向UPF查询用户的流量信息；
S503、UPF通过用户流量查询响应消息向CMF上报用户的流量信息；
S504、CMF把用户流量、时间以及用户信息组成CCR消息，上报给OCS，向OCS请求新的配额；
S505、OCS收到CCR消息后，通过CCA消息向CMF下发对应的时间或者流量等配额信息；
S506、CMF收到OCS下发的时间或者流量等配额信息，通知UPF根据新的配额信息确定计费策略。
图8为本申请实施例的离线计费的时间配额耗尽流程的示意图。如图8所示，本实施例的离线计费的时间配额耗尽流程包括以下步骤：
S601、用户使用业务过程中，离线时间配额生效，CMF设置有定时器，用户正常使用业务。
S602、用户使用业务过程中，CMF判断离线时间配额耗尽，CMF向 UPF发送用户流量查询请求，即CMF向UPF查询用户的流量信息；
S603、UPF通过用户流量查询响应消息向CMF上报用户的流量信息；
S604、CMF将流量、时间以及用户信息生成CDR消息，并通过Bx接口把CDR消息发给BD，以便BD进行离线计费。
图9为本申请实施例的控制面触发的计费流程图。如图9所示，本实施例的控制面触发的计费流程包括以下步骤：
S701、用户正常使用业务过程；
S702、用户移动导致用户的PLMN发生改变(或者，也可以是其它的控制面触发消息)，SMF发送通知消息给CMF，通知CMF用户的PLMN改变；
S703、CMF出话单，CMF向UPF发送用户流量查询请求，即CMF到UPF查询用户在线计费和离线计费的流量信息；
S704、UPF通过用户流量查询响应消息上报用户的流量信息到CMF；
S705、CMF把用户流量、时间及用户信息组成CCR消息，上报在线计费信息给OCS，并向OCS请求新的配额；
S706、CMF把用户流量、时间及用户信息生成CDR消息，并通过Bx接口把CDR消息发给BD；
S707、OCS收到CCR消息后，通过CCA消息下发对应的时间或者流量等配额信息；CMF收到OCS下发的时间或者流量等配额信息，通知UPF根据新的配额信息安装计费策略。
图10为本申请实施例的UPF兼容合并部署的CMF和SMF的示意图。如图10所示，本实施例的UPF兼容合并部署的CMF和SMF(以下简称ComboSMF)的流程包括以下步骤：
S801、ComboSMF在会话创建或者会话更新等流程，获取用户的计费策略(比如从PCF获取计费策略)，保存控制面相关的计费策略，并把用户面相关的计费策略，通过计费策略通知消息通知给UPF，其中可以包括在线计费和离线计费的用户面计费策略；
S802、UPF收到计费策略后，保存计费策略到计费策略上下文，并发 送计费策略通知响应消息给ComboSMF；
S803、ComboSMF要生成话单时，发送用户面的流量请求消息给UPF，查询用户的流量等信息；
S804、UPF收到用户流量请求消息后，获取用户的流量信息，返回用户流量应答消息给ComboSMF；
S805、如果用户的流量门限到达，UPF可以主动发送流量门限到达请求消息给ComboSMF，并继续请求用户的流量配额；
S806、ComboSMF收到后，保存用户的相关数据，生成话单或者CCR消息通知给OCS，并给UPF返回流量门限到达响应消息。
图11为本申请实施例的CMF、UPF及SMF之间的计费参数传递示意图。如图11所示，本实施例的CMF、UPF及SMF之间的计费参数流程包括以下步骤：
S901、SMF在会话创建UPF时，把协议数据单元(PDU，Protocol Data Unit)的会话ID、服务质量(QoS，Quality of Service)流的ID或者承载ID以及用户的QoS信息，在SMF和UPF之间关联到同一个会话下的同一个QoS流或者承载；
S902、SMF进行计费开始消息通知CMF时，会把PDU的会话ID、QoS流的ID或者承载ID参数和计费策略携带给CMF；
S903、CMF在根据策略决策出最终的计费策略时，连同PDU的会话ID和QoS流的ID或者承载ID，通过计费策略通知消息下发给UPF；UPF收到消息后，根据PDU的会话ID和QoS流的ID或者承载ID，找到当前的QoS流或者承载，保存计费策略；
S904、UPF有用户的报文到达，根据计费策略获取当前报文对应的业务标识(SI，Session ID)和RG，在配额到达等消息通知CMF；CMF可以根据把SI和RG填写在话单中，上报给计费中心，用来给用户计费。
本申请实施例还提供一种计费实现方法，包括以下至少之一：CMF向UPF或NF下发计费策略；CMF从待计费的NF和UPF收集计费信息；CMF上报收集到的计费信息。
图12为本申请实施例提供的计费实现方法的一种流程图。如图12所示，本实施例提供的计费实现方法，包括以下步骤：
S1201、CMF向UPF下发计费策略；
S1202、CMF从待计费的NF和UPF收集计费信息；
S1203、CMF上报收集到的计费信息。
其中，CMF与NF之间通过Ncmf接口实现通信，CMF和UPF之间通过Ncmf-upf接口实现通信。
示例性地，CMF向UPF下发计费策略可以包括以下至少之一：
CMF从SMF或PCF获取计费策略，并向UPF下发计费策略；
CMF从OCS获取计费策略，并向UPF下发计费策略；
示例性地，CMF向NF下发计费策略，可以包括：CMF从OCS获取计费策略，并向NF下发计费策略。示例性地，NF可以包括SMF。
示例性地，计费信息可以包括：用户信息、流量信息以及会话信息；
S1202可以包括：
CMF从NF收集用户信息以及会话信息；
CMF从UPF收集流量信息。
示例性地，CMF从UPF收集流量信息，可以包括以下至少之一：
CMF在根据计费策略设置的定时器时间到达时，向UPF查询流量信息；
CMF接收UPF在满足计费策略时通知的流量信息；
CMF在接收到SMF通知的控制面触发更新消息后，向UPF查询流量信息。
示例性地，计费信息可以包括以下至少之一：在线计费信息、离线计费信息；
S1203可以包括以下至少之一：
CMF将在线计费信息上报给OCS；
CMF将离线计费信息上报给BD。
关于本实施例提供的方法的相关说明可以参照上述系统实施例的描述，故于此不再赘述。
图13为本申请实施例提供的CMF的示意图。如图13所示，本实施例提供的CMF包括以下至少之一：
策略下发单元1300，配置为向NF或UPF下发计费策略；
信息收集单元1302，配置为从待计费的NF和UPF收集计费信息；
信息上报单元1304，配置为上报收集到的计费信息。
其中，CMF与NF之间通过Ncmf接口实现通信，CMF和UPF之间通过Ncmf-upf接口实现通信。
示例性地，策略下发单元1300，可以配置为通过以下至少之一方式向UPF下发计费策略：
从SMF或PCF获取计费策略，并向UPF下发计费策略；
从OCS获取计费策略，并向UPF下发计费策略；
策略下发单元1300，可以配置为通过以下方式向NF下发计费策略：从OCS获取计费策略，并向NF下发计费策略。示例性地，NF可以包括SMF。
示例性地，计费信息可以包括：用户信息、流量信息以及会话信息；
信息收集单元1302配置为通过以下方式收集计费信息：
从NF收集用户信息以及会话信息；
从UPF收集流量信息。
示例性地，信息收集单元1302配置为通过以下至少之一方式从UPF收集流量信息：
在根据计费策略设置的定时器时间到达时，向UPF查询流量信息；
接收UPF在满足计费策略时通知的流量信息；
在接收到SMF通知的控制面触发更新消息后，向UPF查询流量信息。
示例性地，计费信息可以包括以下至少之一：在线计费信息、离线计费信息；
信息上报单元1304配置为通过以下至少之一方式上报收集到的计费信息：
将在线计费信息上报给OCS；
将离线计费信息上报给BD。
关于本实施例提供的CMF的相关说明可以参照上述方法实施例和系统实施例的描述，故于此不再赘述。
图14为本申请实施例提供的CMF的另一示意图。如图14所示，本实施例的CMF 1400包括：存储器1404以及处理器1402。本领域技术人员可以理解，图14中示出的CMF结构并不构成对CMF 1400的限定，CMF 1400可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
其中，处理器1402可以包括但不限于微处理器(MCU，Microcontroller Unit)或可编程逻辑器件(FPGA，Field-Programmable Gate Array)等的处理装置。存储器1404可配置为存储应用软件的软件程序或模块，如本实施例中的计费实现方法对应的程序指令或模块，处理器1402通过运行存储在存储器1404内的软件程序或模块，从而执行各种功能应用以及数据处理，即实现本实施例的计费实现方法。存储器1404可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器1404可进一步包括相对于处理器1402远程设置的存储器，这些远程存储器可以通过网络连接至上述CMF 1400。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
示例性地，上述CMF 1400还可以包括通信单元1406；通信单元1406可以经由一个网络接收或者发送数据。在一个实例中，通信单元1406可以为射频(RF，Radio Frequency)模块，其配置为通过无线方式与互联网进行通信。
需要说明的是，本实施例提供的CMF可以由软件、硬件或者软件和硬件的组合实现。然而，本申请对此并不限定。
此外，本申请实施例还提供一种计算机可读介质，存储有计费实现程序，所述计费实现程序被处理器执行时实现上述计费实现方法的步骤。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块或单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块或单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些组件或所有组件可以被实施为由处理器，如数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在机器可读介质(比如，计算机可读介质)上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在配置为存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以配置为存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
以上显示和描述了本申请的基本原理和主要特征和本申请的优点。本申请不受上述实施例的限制，上述实施例和说明书中描述的只是说明本申请的原理，在不脱离本申请精神和范围的前提下，本申请还会有各种变化和改进，这些变化和改进都落入要求保护的本申请范围内。

Claims (16)

  1. 一种计费实现系统，包括：
    网络功能实体、用户面功能实体以及计费管理功能实体；所述计费管理功能实体连接所述网络功能实体和所述用户面功能实体；
    所述计费管理功能实体配置为执行以下至少之一：向所述用户面功能实体或网络功能实体下发计费策略；从所述网络功能实体和所述用户面功能实体收集计费信息；上报所述计费信息。
  2. 根据权利要求1所述的系统，其中，所述计费管理功能实体与网络功能实体之间通过Ncmf接口实现通信，所述计费管理功能实体和用户面功能实体之间通过Ncmf-upf接口实现通信。
  3. 根据权利要求1所述的系统，其中，所述计费管理功能实体配置为通过以下至少之一方式向所述用户面功能实体下发计费策略：
    所述计费管理功能实体从业务管理功能实体或策略控制功能实体获取计费策略，并向所述用户面功能实体下发所述计费策略；
    所述计费管理功能实体从在线计费系统获取计费策略，并向所述用户面功能实体下发所述计费策略；
    所述计费管理功能实体配置为通过以下方式向所述网络功能实体下发计费策略：所述计费管理功能实体从在线计费系统获取计费策略，并向所述网络功能实体下发所述计费策略。
  4. 根据权利要求1所述的系统，其中，所述计费信息包括：用户信息、流量信息以及会话信息；
    所述计费管理功能实体配置为通过以下方式从所述网络功能实体和所述用户面功能实体收集计费信息：
    所述计费管理功能实体从所述网络功能实体收集用户信息以及会话信息；
    所述计费管理功能实体从所述用户面功能实体收集流量信息。
  5. 根据权利要求4所述的系统，其中，所述计费管理功能实体配置 为通过以下至少之一方式从所述用户面功能实体收集流量信息：
    所述计费管理功能实体在根据计费策略设置的定时器时间到达时，向所述用户面功能实体查询流量信息；
    所述计费管理功能实体接收所述用户面功能实体在满足计费策略时通知的流量信息；
    所述计费管理功能实体在接收到业务管理功能实体通知的控制面触发更新消息后，向所述用户面功能实体查询流量信息。
  6. 根据权利要求1所述的系统，其中，所述计费信息包括以下至少之一：在线计费信息、离线计费信息；
    所述系统还包括以下至少之一：在线计费系统、计费中心；
    所述计费管理功能实体连接所述在线计费系统和所述计费中心中至少之一；
    所述计费管理功能实体通过以下至少之一方式上报所述计费信息：
    所述计费管理功能实体将所述在线计费信息上报给所述在线计费系统；
    所述计费管理功能实体将所述离线计费信息上报给所述计费中心。
  7. 一种计费实现方法，包括以下至少之一：
    计费管理功能实体向用户面功能实体或网络功能实体下发计费策略；
    所述计费管理功能实体从待计费的网络功能实体和用户面功能实体收集计费信息；
    所述计费管理功能实体上报收集到的计费信息。
  8. 根据权利要求7所述的方法，其中，所述计费管理功能实体与网络功能实体之间通过Ncmf接口实现通信，所述计费管理功能实体和用户面功能实体之间通过Ncmf-upf接口实现通信。
  9. 根据权利要求7所述的方法，其中，所述计费管理功能实体向用户面功能实体下发计费策略，包括以下至少之一：
    所述计费管理功能实体从业务管理功能实体或策略控制功能实体获取计费策略，并向所述用户面功能实体下发所述计费策略；
    所述计费管理功能实体从在线计费系统获取计费策略，并向所述用户面功能实体下发所述计费策略；
    所述计费管理功能实体向网络功能实体下发计费策略，包括：所述计费管理功能实体从在线计费系统获取计费策略，并向所述网络功能实体下发所述计费策略。
  10. 根据权利要求7所述的方法，其中，所述计费信息包括：用户信息、流量信息以及会话信息；
    所述计费管理功能实体从待计费的网络功能实体和用户面功能实体收集计费信息，包括：
    所述计费管理功能实体从所述网络功能实体收集用户信息以及会话信息；
    所述计费管理功能实体从所述用户面功能实体收集流量信息。
  11. 根据权利要求10所述的方法，其中，所述计费管理功能实体从所述用户面功能实体收集流量信息，包括以下至少之一：
    所述计费管理功能实体在根据计费策略设置的定时器时间到达时，向所述用户面功能实体查询流量信息；
    所述计费管理功能实体接收所述用户面功能实体在满足计费策略时通知的流量信息；
    所述计费管理功能实体在接收到业务管理功能实体通知的控制面触发更新消息后，向所述用户面功能实体查询流量信息。
  12. 根据权利要求7所述的方法，其中，所述计费信息包括以下至少之一：在线计费信息、离线计费信息；
    所述计费管理功能实体上报收集到的所述计费信息，包括以下至少之一：
    所述计费管理功能实体将所述在线计费信息上报给在线计费系统；
    所述计费管理功能实体将所述离线计费信息上报给计费中心。
  13. 一种计费管理功能实体，包括以下至少之一：
    策略下发单元，配置为向用户面功能实体或网络功能实体下发计费策略；
    信息收集单元，配置为从待计费的网络功能实体和用户面功能实体收集计费信息；
    信息上报单元，配置为上报收集到的计费信息。
  14. 根据权利要求13所述的计费管理功能实体，其中，所述计费管理功能实体与网络功能实体之间通过Ncmf接口实现通信，所述计费管理功能实体和用户面功能实体之间通过Ncmf-upf接口实现通信。
  15. 一种计费管理功能实体，包括：存储器以及处理器，所述存储器配置为存储计费实现程序，所述计费实现程序被所述处理器执行时实现如权利要求7至12中任一项所述的计费实现方法的步骤。
  16. 一种计算机可读介质，存储有计费实现程序，所述计费实现程序被处理器执行时实现如权利要求7至12中任一项所述的计费实现方法的步骤。
PCT/CN2018/102024 2017-08-30 2018-08-23 计费实现系统、计费实现方法及计费管理功能实体 WO2019042218A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP18850699.2A EP3678329A1 (en) 2017-08-30 2018-08-23 Charging realisation system, charging realisation method and charging management functional entity

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710766197.3 2017-08-30
CN201710766197.3A CN109428734B (zh) 2017-08-30 2017-08-30 计费实现系统、计费实现方法及计费管理功能实体

Publications (1)

Publication Number Publication Date
WO2019042218A1 true WO2019042218A1 (zh) 2019-03-07

Family

ID=65504210

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/102024 WO2019042218A1 (zh) 2017-08-30 2018-08-23 计费实现系统、计费实现方法及计费管理功能实体

Country Status (3)

Country Link
EP (1) EP3678329A1 (zh)
CN (1) CN109428734B (zh)
WO (1) WO2019042218A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112291725B (zh) * 2019-07-22 2021-11-09 华为技术有限公司 一种通信方法及装置
CN113068138A (zh) * 2020-01-02 2021-07-02 中国移动通信有限公司研究院 一种计费消息的发送方法及装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1735024A (zh) * 2004-08-10 2006-02-15 华为技术有限公司 一种基于业务数据流计费的计费信息处理方法
CN101141266A (zh) * 2007-09-30 2008-03-12 中兴通讯股份有限公司 策略规则下发方法以及在线计费方法和离线计费方法

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3101926B1 (en) * 2014-01-29 2021-03-10 Huawei Technologies Co., Ltd. Charging processing method, centralized network control node and function node

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1735024A (zh) * 2004-08-10 2006-02-15 华为技术有限公司 一种基于业务数据流计费的计费信息处理方法
CN101141266A (zh) * 2007-09-30 2008-03-12 中兴通讯股份有限公司 策略规则下发方法以及在线计费方法和离线计费方法

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI: "Pseudo CR on TS 23.502 for the NF Services and Service Operations of SMF", S2-173917, 3GPP SA WG2 MEETING #121, 15 May 2017 (2017-05-15), Hang- zhou, China, XP051281214 *
HUAWEI: "Roaming impacts to policy", S2-171290, 3GPP SA WG2 MEETING #119, 13 February 2017 (2017-02-13), Dubrov- nik, Croatia, XP051234465 *
NOKIA: "TS 23.501: P-CR to update Policy Architecture Requirements", S2-172035, 3GPP SA WG2 MEETING #120, 27 March 2017 (2017-03-27), Busan, Ko- rea, XP051257608 *

Also Published As

Publication number Publication date
CN109428734A (zh) 2019-03-05
EP3678329A1 (en) 2020-07-08
CN109428734B (zh) 2023-04-07

Similar Documents

Publication Publication Date Title
CN107535011B (zh) 数据处理方法、设备、系统及存储介质
WO2017088501A1 (zh) 一种计费方法及装置
US9100816B2 (en) Charging method, device, and system
WO2017219905A1 (zh) 一种计费方法、装置、系统和存储介质
JP2019057955A (ja) 第１の装置、ｐｃｒｆ装置、及びこれらの方法
EP4101188A1 (en) Extension of npcf_eventexposure with usage monitoring event
WO2019157873A1 (zh) 计费方法、装置及会话管理实体
WO2009012686A1 (fr) Procédé, équipement et système de mise en œuvre du contrôle des conditions d'utilisation et de facturation
US20160072963A1 (en) Group charging method, gateway device, charging device, and communications system
CN102202281B (zh) 话单处理方法及系统
WO2019095725A1 (zh) 一种计费方法、装置及系统
JP2018521524A (ja) 課金システム用コール詳細記録を生成するための方法およびシステム
WO2011134336A1 (zh) 机器类通信事件上报方法、装置及系统
CN104247331A (zh) 用于管理网络资源的方法和节点以及相应的系统和计算机程序
JPWO2015022764A1 (ja) 無線通信システム及び課金制御のための方法
CN102170625B (zh) 一种pcc策略的实现方法和装置
EP3567799A1 (en) Charging method, apparatus, and system
WO2019042218A1 (zh) 计费实现系统、计费实现方法及计费管理功能实体
EP3101926B1 (en) Charging processing method, centralized network control node and function node
WO2014059599A1 (zh) 计费处理方法、装置和系统
EP3157278A1 (en) Policy control and charging method, apparatus and device
WO2017193275A1 (zh) QoS资源分配方法和装置
CN103891328A (zh) 拜访的pcrf s9会话id生成
CN101009744A (zh) 一种无线接入网系统中提供计费信息的方法和装置
CN102868976A (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: 18850699

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018850699

Country of ref document: EP

Effective date: 20200330