WO2019024645A1 - 一种计费方法及设备 - Google Patents

一种计费方法及设备 Download PDF

Info

Publication number
WO2019024645A1
WO2019024645A1 PCT/CN2018/094481 CN2018094481W WO2019024645A1 WO 2019024645 A1 WO2019024645 A1 WO 2019024645A1 CN 2018094481 W CN2018094481 W CN 2018094481W WO 2019024645 A1 WO2019024645 A1 WO 2019024645A1
Authority
WO
WIPO (PCT)
Prior art keywords
charging
quota
session
data
information
Prior art date
Application number
PCT/CN2018/094481
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 EP21154943.1A priority Critical patent/EP3883180B1/en
Priority to EP18841358.7A priority patent/EP3588846B1/en
Publication of WO2019024645A1 publication Critical patent/WO2019024645A1/zh
Priority to US16/586,129 priority patent/US10674330B2/en
Priority to US16/832,985 priority patent/US10945104B2/en
Priority to US17/162,505 priority patent/US11671802B2/en

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
    • 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
    • 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/1442—Charging, metering or billing arrangements for data wireline or wireless communications at network operator level
    • H04L12/145—Charging, metering or billing arrangements for data wireline or wireless communications at network operator level trading network capacity or selecting route based on tariff
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/143—Termination or inactivation of sessions, e.g. event-controlled end of session
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/563—Data redirection of data network streams
    • 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/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/70—Administration or customization aspects; Counter-checking correct charges
    • H04M15/775—Account specifications on parallel communications
    • 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/70—Administration or customization aspects; Counter-checking correct charges
    • H04M15/78—Redistributing amount between accounts
    • 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/70—Administration or customization aspects; Counter-checking correct charges
    • H04M15/785—Reserving amount on the account
    • 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
    • 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/8228—Session 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
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/32—Involving wireless systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/78—Metric aspects
    • H04M2215/7833—Session based

Definitions

  • the present application relates to the field of communications, and in particular, to a charging method and apparatus.
  • the basic mechanism of online charging is: the Charging Trigger Function (CTF) applies to the Online Charging System (OCS) to reserve a quota for a Rate Group, and the OCS grants a quota.
  • the CTF performs the quota management, the quota usage, and the charging information collection, and reports the collected charging information to the charging system when the monitoring of the charging reporting condition (trigger condition) is satisfied.
  • the policy and the Charging Enforcement Function (PCEF) of the gateway is the CTF.
  • the PCEF sends the accounting policy based on the Policy and Charging Rules Function (PCRF).
  • Determine the charging mode online charging or offline charging
  • statistical methods traffic or duration
  • rate group Rate Group, this application is called charging key
  • reporting granularity and so on.
  • the billing granularity includes: SERVICE_IDENTIFIER_LEVEL or RATING_GROUP_LEVEL. If the billing granularity is RATING_GROUP_LEVEL, the PCEF must report the billing information for each rate group. If the billing granularity is SERVICE_IDENTIFIER_LEVEL, the PCEF must be for each rate group and service. The identifier reports the billing information.
  • the network architecture of the control plane and the user plane is extended under the 4G network, and the billing under the network architecture of the control plane and the user plane can be realized to some extent.
  • Serving Gateway-C, PDN Gateway-C, and TDF-C belong to the control plane
  • Serving Gateway-U, PDN Gateway-U, and TDF-U belong to the user plane.
  • the control plane is the charging trigger point, and the charging trigger function is completed.
  • the user plane is the charging collection point, and the charging collection function is completed.
  • the number of control planes and the number of user planes in the running state are 1 to 1 relationship.
  • the embodiment of the present application provides a charging method, which is mainly used to solve the service data of a user when a user plane of a PDU session is switched, or when multiple user planes exist in a PDU session in a network control and data flow forwarding separation architecture. Billing processing that flows between user planes.
  • a charging method includes: the control plane function entity CP determines that a data stream transmitted by the user equipment UE on the first data session needs to be migrated to the second data session, where the first data session is a data session between the UE and the first user plane function entity UP, the second data session is a data session between the UE and the second UP, and the first UP and the second UP are UP corresponding to the CP.
  • the first data session and the second data session correspond to the same PDU session; the CP acquires the charging information before the data flow migration of the first UP statistics; and the CP determines the location that needs to be sent to the second UP.
  • the quota used after the data flow is migrated and sent to the second UP.
  • the CP obtains the accounting information on the UP before the data stream is migrated, and further determines the quota that needs to be delivered to the target UP after the migration, and delivers the accounting data of the user's service data flow between the user planes. Continuity.
  • the CP charges the data flow on the first UP by using a first charging session with a charging system, where the CP determines that the data flow migrates from the first UP to the first After the second UP, the first UP has no other data stream that uses the charging key corresponding to the data stream; the CP is used for charging the data flow on the second UP by using the first charging session, based on In this scheme, the switched charging session may not be changed.
  • the CP obtains the charging information before the data flow of the first UP statistics, determines the quota that needs to be sent to the second UP, and sends the quota to the second UP, where the CP receives the first The billing information before the migration of the data stream reported by the UP, reporting the billing information to the billing system, and applying a quota for the data flow for the second UP; the CP receiving the billing system The quota is sent; the CP generates a quota that is sent to the second UP according to the quota issued by the charging system. Based on the solution, the charging system senses the occurrence of the migration, and can switch the UP. Make more accurate quota control.
  • the CP obtains the charging information of the first UP, and determines the quota that needs to be sent to the second UP, where the CP includes the pre-migration calculation of the data flow according to the obtained first UP statistics.
  • the fee information is used to determine the remaining available quota, and the quota that is delivered to the second UP is generated according to the remaining available quota. Based on the solution, the charging system does not need to perceive the UP handover or the data flow migration, which can reduce the burden of the charging system.
  • the method further includes: the CP buffering the charging information before the migration of the data flow reported by the first UP; and the receiving, by the CP, the charging information after the data flow migrated by the second UP;
  • the CP combines the charging information reported by the second UP with the charging information of the cached first UP, and reports the combined charging information to the charging system.
  • the method further includes: sending, by the CP, the charging information before the data flow that is reported by the first UP to the second UP, so that the second UP is based on the data reported by the first UP
  • the billing information before the stream migration continues to collect the billing information after the data stream is migrated; the CP receives the billing information before and after the migration of the data stream reported by the second UP when the reporting condition is met, and Reported to the billing system.
  • the CP determines, after the data flow on the PDU session is migrated from the first UP to the second UP, according to the indication sent by the charging system, and reports the data flow before the migration to the charging system. Billing information. Based on the solution, the charging system can set the charging report related to the data flow switching to be sent to the CP to enhance the flexibility of charging.
  • the CP obtains the charging information before the data flow migration of the first UP statistics, and the method includes: receiving, by the CP, the first data session interruption to trigger the charging information reported by the first UP.
  • the CP obtains the charging information before the data flow migration of the first UP statistics, and the method includes: after the CP detects the data flow start event corresponding to the data flow reported by the second UP, acquiring the first The billing information before the data stream migration is counted on an UP.
  • the method further includes: the CP charging the data flow on the first UP by using a first charging session with a charging system, where the CP determines the data flow from After the first UP is migrated to the second UP, the first UP has another data stream that uses the charging key corresponding to the data stream; and the CP uses the first billing for the data stream on the second UP. a session; the CP acquires charging information of the data stream from the first UP and the second UP at the same time.
  • “other” refers to the data flow that is not migrated relative to the past, and is called “other" data streams, which are the data streams on the PDU session established by the CP. Based on the solution, the data flow under the SSC mode 3 can be accurately charged, and the data flow across the CK is not ignored because of the UP switch.
  • the CP further determines a quota that needs to be sent to the first UP, where the method includes: the CP divides the quota that is sent by the charging system for the charging key into multiple sub-quotas and sends the quotas to the sub-quotas respectively.
  • the method further includes: after the quota is used up on the UP and reporting the charging information corresponding to the quota, the CP obtains the charging information corresponding to the quota calculated by the other UP; The CP combines the charging information corresponding to the quota and reports it to the charging system.
  • the method further includes: after the quota is used up on the UP and reporting the charging information corresponding to the quota, the CP obtains the charging information corresponding to the quota calculated by the other UP; The CP caches the charging information corresponding to the quota reported by all the UPs, determines the remaining available amount of the quota, reallocates the remaining available amount of the quota, and delivers the reallocation to the first UP and the second UP. If the quota is used up, or the remaining available amount of the quota satisfies the reporting threshold, the CP combines the billing information corresponding to the cached quota, and reports the combined meter to the charging system. Fee information.
  • the method further includes: the CP charging the data flow on the first UP by using a first charging session with a charging system; the CP determining the data flow from After the first UP is migrated to the second UP, the first UP has another data stream that uses the charging key corresponding to the data stream; and the CP is used for the second data session on the second UP that transmits the data stream.
  • a second charging session applying a quota to the charging system through the second charging session, and sending the applied quota to the second UP;
  • the second charging session is the CP and the charging system is the first A charging session established by the second data session on the second UP.
  • a new accounting session dedicated to the target UP is implemented to implement efficient and accurate charging, and reduce the burden of the CP on the quota processing.
  • a second aspect provides a charging method, where the method includes: the control plane function entity CP acquires, from the first user plane function entity UP and the second UP, a data flow of a data flow on a PDU session corresponding to the CP.
  • the first UP and the second UP are the UP corresponding to the CP;
  • the CP divides the quota issued by the charging system into multiple sub-quotas, and sends the quotas to the first UP and the second UP respectively.
  • the CP can simultaneously charge the data streams generated on the corresponding two UPs.
  • a data flow using the same charging key exists on the first UP and the second UP; the CP acquires charging information of the data flow from the first UP and the second UP at the same time; for Diameter In the case of a protocol interface, the CP charges the first UP and the second UP through a charging session with the charging system.
  • the CP divides the quota that is sent by the charging system into multiple sub-quotas and sends the quota to the UP
  • the method includes: the CP divides the quota issued by the charging system into the plurality of sub-quotas The first UP and the second UP are respectively delivered.
  • the method further includes: after the quota is used up on the UP and reporting the charging information corresponding to the quota, the CP obtains the charging information corresponding to the quota calculated by the other UP; The CP combines the charging information corresponding to the quota and reports it to the charging system.
  • the method further includes: after the quota is used up on the UP and reporting the charging information corresponding to the quota, the CP obtains the charging information corresponding to the quota calculated by the other UP; The CP caches the charging information corresponding to the quota reported by all the UPs, determines the remaining available amount of the quota, reallocates the remaining available amount of the quota, and delivers the reallocation to the first UP and the second UP. If the quota is used up, or the remaining available amount of the quota satisfies the reporting threshold, the CP combines the billing information corresponding to the cached quota, and reports the combined meter to the charging system. Fee information.
  • the third aspect provides a charging method, including the following steps: the online charging system OCS sends the indication information to the control plane function entity CP, where the indication information is used to indicate that the CP is in the user plane function entity corresponding to the CP. After the first UP is switched to the second UP, the charging information before the first UP switching is reported to the OCS; the OCS receives the charging information before the switching of the first UP statistics reported by the CP. .
  • the indication information is sent along with the quota that is sent by the OCS to the CP.
  • the OCS after receiving the charging information reported by the CP, the OCS sends a second UP to the CP, or a quota of the first UP and the second UP.
  • the fourth aspect provides a charging device, including a determining module, an obtaining module, and a processing module, where the determining module is configured to determine that the data stream transmitted by the user equipment UE on the first data session needs to be migrated to the second data session.
  • the first data session is a data session between the UE and the first user plane function entity UP;
  • the second data session is a data session between the UE and the second UP, the first UP and the second UP An UP corresponding to the charging device, where the first data session and the second data session correspond to the same PDU session;
  • the acquiring module is configured to obtain the charging information before the data flow migration of the first UP statistics.
  • the processing module is configured to determine a quota used after the data stream that needs to be delivered to the second UP is migrated, and is sent to the second UP.
  • the session module is further configured to establish a first charging session with the charging system, and charge the data flow on the first UP by using the first charging session, where
  • the determining module is further configured to: after the data stream is migrated from the first UP to the second UP, the first UP has no other data stream that uses the charging key corresponding to the data stream, and the session module is further used to The data stream on the second UP uses the first charging session for charging.
  • the acquiring module is configured to receive the charging information before the data flow that is reported by the first UP, and report the charging information to the charging system by using the session module, and use the charging information for the second UP application. a quota for the data flow; the session module is configured to receive the quota issued by the charging system; and the processing module generates a delivery to the second UP according to the quota issued by the charging system. quota.
  • the processing module is configured to determine the remaining available quota according to the obtained charging information of the first UP statistics, and generate the remaining available quota according to the remaining available quotas. Quota.
  • the obtaining module is configured to receive, by the first data session, the charging information that is triggered by the first UP.
  • the acquiring module is configured to obtain the charging information before the data stream migration on the first UP after the data flow start event corresponding to the data flow reported by the second UP.
  • the method further includes a session module, configured to establish a first charging session with the charging system, and charge the data flow on the first UP by using the first charging session, the determining module After determining that the data stream is migrated from the first UP to the second UP, the first UP has another data stream that uses a charging key corresponding to the data stream; the obtaining module is further configured to simultaneously The charging information of the data stream is acquired on the first UP and the second UP.
  • a session module configured to establish a first charging session with the charging system, and charge the data flow on the first UP by using the first charging session
  • the determining module After determining that the data stream is migrated from the first UP to the second UP, the first UP has another data stream that uses a charging key corresponding to the data stream; the obtaining module is further configured to simultaneously The charging information of the data stream is acquired on the first UP and the second UP.
  • the method further includes a session module, configured to establish a first charging session with the charging system, and charge the data flow on the first UP by using the first charging session, the determining module Further for determining that the data stream is migrated from the first UP to the second UP, the first UP has another data stream that uses a charging key corresponding to the data stream; the session module is further configured to be a second Transmitting, by the second data session establishment and charging system, the second charging session of the data stream, applying a quota to the charging system through the second charging session, and the processing module is further used to apply for the quota Issued to the second UP.
  • a session module configured to establish a first charging session with the charging system, and charge the data flow on the first UP by using the first charging session
  • the determining module Further for determining that the data stream is migrated from the first UP to the second UP, the first UP has another data stream that uses a charging key corresponding to the data stream
  • the session module is further configured to be a second
  • a fifth aspect provides a charging system, including a sending module and a receiving module, where the sending module is configured to send indication information to a control plane function entity CP, where the indication information is used to indicate that the CP is in the CP After the corresponding user plane function entity UP is switched from the first UP to the second UP, the charging information before the first UP switching is reported to the OCS, and the receiving module is configured to receive the The charging information before the switching of the first UP statistics.
  • a computing device where the implementation may be a CP, corresponding to an SMF functional entity in the 5G, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, and the processor is configured to The memory is connected by the bus, and when the computing device is running, the processor executes the computer-executed instructions stored by the memory to cause the computing device to perform the charging method according to any one of the first aspect or the second aspect .
  • a seventh aspect provides a computing device, which may be an OCS functional entity, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, and the processor is connected to the memory through the bus.
  • the processor executes the computer-executable instructions stored by the memory to cause the computing device to perform the charging method of any of the above third aspects.
  • an embodiment of the present application provides a computer readable storage medium, where the computer readable storage medium stores instructions that, when run on a computer, enable the computer to perform the first aspect, the second aspect, or The charging method of any of the third aspects.
  • the embodiment of the present application provides a computer program product comprising instructions, when the computer is running on a computer, enabling the computer to perform the charging method of the first aspect, the second aspect or the third aspect .
  • a tenth aspect a network system, comprising the charging device of any of the preceding aspects, and the charging system of any of the above aspects.
  • the solution of the embodiment of the present invention implements the service data flow of the user when a user plane of a PDU Session is switched, or when multiple user planes exist in one PDU Session, in a scenario where the user plane of a PDU session is switched.
  • Accounting in the case of migration between user planes enables billing to support lower end-to-end delays of the service and optimize the deployment of network efficiency, achieve accurate billing of data services under optimized deployment, and improve network efficiency. And user experience.
  • FIG. 1 is a schematic diagram of a network architecture in which a control plane and a user plane are separated in the prior art
  • FIG. 2 is a schematic diagram of a network architecture according to an embodiment of the present application.
  • FIG. 3 is a schematic diagram showing the hardware structure of a computer device 300 according to an embodiment of the present application.
  • FIG. 4 is an exemplary flowchart of a charging method 400 in accordance with an embodiment of the present application.
  • FIG. 5 is an exemplary flowchart of a charging method 500 in accordance with an embodiment of the present application.
  • FIG. 6 is an exemplary flowchart of a charging method 600 in accordance with an embodiment of the present application.
  • FIG. 7 is an exemplary flowchart of a charging method 700 in accordance with an embodiment of the present application.
  • FIG. 8 is an exemplary flowchart of a charging method 800 in accordance with an embodiment of the present application.
  • FIG. 9 is an exemplary flowchart of a charging method 900 in accordance with an embodiment of the present application.
  • FIG. 10 is an exemplary flowchart of a charging method 1000 according to an embodiment of the present application.
  • FIG. 11 is an exemplary flowchart of a charging method 1100 according to an embodiment of the present application.
  • FIG. 12 is a schematic diagram of a possible structure of a charging device 1200 according to an embodiment of the present application.
  • FIG. 13 is a schematic diagram of a possible structure of a charging system 1300 according to an embodiment of the present application.
  • the network element name involved in the embodiment of the present application does not limit the device itself.
  • the name of the session management function itself does not limit the device. In practice, it can be other names.
  • the name of the user plane function of UP does not limit the device itself. In practice, it can be other names.
  • User Plane Function Entity The name of the online billing system itself does not limit the device. In practice, it can be other names, such as billing systems, or other names. A unified explanation is given here, and will not be described below.
  • the solution of the embodiment of the present application takes a 5G network as an example, but a transitional network that is not limited to a 5G network, a part of 4G, or a 4G to 5G network may be used, and may also be applied to other possible communication or charging systems in the future.
  • a transitional network that is not limited to a 5G network, a part of 4G, or a 4G to 5G network may be used, and may also be applied to other possible communication or charging systems in the future.
  • the user's service data flows between the user planes, and the corresponding charging methods are The solution of the related embodiments of the present invention can be employed.
  • the SMF is a session management function
  • the PCF is a policy control function
  • the UPF is a user plane function (User Plane Function)
  • the OCS is an online charging system (Online Charging System)
  • the UE is a user.
  • User equipment The SMF communicates with the PCF through the N7 interface.
  • the SMF communicates with the UPF through the N4 interface.
  • the different UPFs communicate through the N9 interface.
  • the functions of the SMF include management of protocol data unit (PDU) sessions, such as establishment, modification and release; Internet Protocol (IP) address allocation of the UE; UPF selection; UPF routing policy configuration; The control strategy of the PCF, and the control plane part of the control policy; determining the Service and Session Continuity (SSC) mode of the PDU Session (referred to as SSC mode) under the IP type, specifically, the PDU session
  • SSC mode Service and Session Continuity
  • SSC mode Service and Session Continuity
  • SSC mode 1 In this mode, after the terminal establishes a PDU session, regardless of whether the terminal moves to any area or any access technology, The UPF network element of the PDU session acts as an anchor point for the terminal, that is, the PDU session does not undergo any form of interruption due to the movement of the terminal.
  • SSC Mode 2 In this mode, after the terminal establishes a PDU session, when the terminal moves, if the terminal leaves the service area of the UPF network element, or because the UPF network element fails, the load is too large, etc., the network can be the PDU of the terminal.
  • the session reselects the UPF network element and enables the terminal to re-select the PDU session after the UPF network element is re-selected.
  • the user's service is migrated from the original UPF to the new UPF.
  • the UPF network element can be considered to have a specific service area.
  • the UPF network element When the terminal moves in the service area, the UPF network element is a terminal service, and if the terminal leaves the service area, the network side can determine the The UPF network element cannot serve the terminal.
  • the PDU session established through the UPF network element will be interrupted, and a PDU session will be established with the new UPF.
  • SSC Mode 3 In this mode, after the terminal establishes a PDU session, the service area of the UPF network element also has a range. After the terminal leaves the service area of the UPF network element, the network selects a new UPF network element for the terminal as the terminal. Service, the terminal establishes a PDU session with the original DN network element through the new UPF network element. However, unlike the foregoing SSC mode 2, the PDU session established by the terminal through the old UPF network element may temporarily not release the connection, but is new. The PDU session is established after the session is established.
  • the functions of the UPF include an anchor function that performs interaction with the external data network (UPF with anchor function is called UPF anchor point); packet routing and forwarding; packet detection, and a user plane portion of the control strategy for performing PCF activation.
  • UPF anchor point an anchor function that performs interaction with the external data network
  • packet routing and forwarding packet detection, and a user plane portion of the control strategy for performing PCF activation.
  • the functions of the PCF include generating and delivering policies, or activating the statically configured policies on the SMF, and controlling the QoS, gating, and accounting of the service data flows routed on the UPF through policies.
  • the SMF can determine whether to establish an online charging session with the OCS according to the policy delivered by the PCF, and determine a charging key corresponding to the service data flow.
  • the OCS function includes quota granting according to the request of the SMF, and deducting or returning the balance according to the quota usage information reported by the SMF.
  • the UE is a device having a Subscriber Permanent Identity (SUPI) or an International Mobile Subscriber Identification Number (IMSI), and may be a mobile phone, a tablet, a computer, an IoT device, or the like having SIM/eSIM.
  • SUPI Subscriber Permanent Identity
  • IMSI International Mobile Subscriber Identification Number
  • the quota application, allocation, and accounting information reporting interface may be a Diameter protocol interface or a serviced interface, and a serviced interface, such as Restful, etc., in a serviced interface mode, a charging session is not established between the CP and the charging system. It is to interact directly through the service message, and the service message (such as Restful) is a stateless message.
  • This application mainly exemplifies the Diameter protocol, but the present application does not limit the message format, and other formats such as the Restful API may also be used.
  • Control plane performs functions such as PDU session management, IP address allocation, and user plane selection. This application is called a CP or CP functional entity and corresponds to the SMF in the 5G core network.
  • User plane Performs packet routing and forwarding, packet inspection, etc. This application is called UP or UP functional entity and corresponds to UPF in the 5G core network.
  • PDU Session (similar to the IP-CAN Session of 4G, 4G/5G transition network, in the following description, PDU session is used to indicate related or similar concepts), PDU Session is a data network established on the UE and providing PDU connection service (Data Network, DN), and the connection DN is UPF, so it can also be said that the PDU Session is established between the UE and the UPF.
  • the establishment of the PDU Session is controlled by the SMF, so the UE sends a PDU Session Establishment Request to the SMF, and the SMF selects the UPF that establishes a connection with the UE.
  • a PDU Session can exist/correspond to multiple UPF entities.
  • FIG. 3 is a schematic diagram showing the hardware structure of a computer device 300 according to an embodiment of the present application.
  • computer device 300 includes a processor 302, a memory 304, a communication interface 306, and a bus 308.
  • the processor 302, the memory 304, and the communication interface 306 implement a communication connection with each other through the bus 308.
  • the processor 302 can be a general-purpose central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), or one or more integrated circuits for executing related programs.
  • CPU central processing unit
  • ASIC application specific integrated circuit
  • the memory 304 may be a read only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM).
  • Memory 304 can store operating system 3041 and other applications 3042.
  • the program code for implementing the technical solution provided by the embodiment of the present application is saved in the memory 304 and executed by the processor 302.
  • Communication interface 306 implements communication with other devices or communication networks using transceivers such as, but not limited to, transceivers.
  • Bus 308 can include a path for communicating information between various components (e.g., processor 302, memory 304, communication interface 306).
  • the processor 302 executes the program code stored in the memory 304 for implementing the technical solution provided by the embodiment of the present application to implement the method shown in the embodiment of FIG. 4 to FIG.
  • the processor 302 executes the program code stored in the memory 304 for implementing the technical solution provided by the embodiment of the present application to implement the method shown in the embodiment of FIG. 4 to FIG.
  • the service data stream of the user is migrated between user planes, and the data service is accurately charged. Improve network efficiency and user experience.
  • the charging method 400 can be performed by SMF (CP), OCS, or UPF (UP) shown in FIG. 2.
  • SMF SMF
  • OCS OCS
  • UPF UPF
  • the control plane function entity CP determines that the data stream transmitted by the UE on the first data session needs to be migrated to the second data session, where the first data session is a data session between the UE established by the CP and the first UP (UP1).
  • the second data session is a data session between the UE and the second UP (UP2), the first UP and the second UP are UP corresponding to the CP, the first data session and the second data session Corresponding to the same PDU Session; the CP charges the data flow on the first UP by using a first charging session with the charging system;
  • the data stream transmission between the UE and the data network is implemented by the established PDU Session, which is established between the UE and the data network (DN) that provides the PDU connection service.
  • the establishment of the PDU session is controlled by the control plane function entity CP, such as the SMF. Therefore, the UE sends a PDU Session establishment request to the CP, and the CP selects the UP to establish a connection with the UE.
  • the PDU session of the UE and the user plane is migrated to different user planes because the user plane of one PDU session is switched, or when there are multiple user planes in one PDU session, the service data flow of the user migrates between user planes.
  • two or more user planes are established at the same time, but during the migration process, two or more UPs correspond to the same CP, and the PDU Session is unchanged.
  • the term "unchanged” or “same” PDU session refers to the change of the PDU session during the UP process.
  • the control plane is basically unchanged, specifically the session ID, the IP address of the UE, and the access point. (DNN) is unchanged.
  • the CP acquires charging information before the data flow migration of the first UP statistics.
  • the service data flow is migrated to the second UP, and the charging collection point is also changed.
  • the change includes, but is not limited to, the charging collection point is migrated from the first UP to the second UP.
  • the second UP is used as the sole charging collection point; or the first UP and the second UP are simultaneously used as the charging collection point after the migration.
  • the CP obtains the charging information on the first UP before the migration is completed (including during the migration process). If the data connection between the UE and the first UP still exists after the migration is completed, the CP may continue to obtain the charging information of the first UP. Used for quota management during migration or after migration to ensure the continuity and accuracy of the billing process;
  • the specific manner of obtaining the charging information may be that the first UP is actively reported, or the CP may send the obtaining request to the first UP to obtain the triggering manner.
  • the triggering manner may also be implemented in multiple manners, such as the occurrence of the migration (decision migration or actual occurrence).
  • the migration such as the release of the first UP session, may trigger the first UP to be actively reported.
  • the CP may also report the first UP request after the second UP starts to transmit the service data flow, etc., and may be configured on the CP or the UP.
  • Related trigger conditions (trigger) implementation may be that the first UP is actively reported, or the CP may send the obtaining request to the first UP to obtain the triggering manner.
  • the triggering manner may also be implemented in multiple manners, such as the occurrence of the migration (decision migration or actual occurrence).
  • the migration such as the release of the first UP session, may trigger the first UP to be actively reported.
  • the CP may also report the first
  • the CP determines the quota used after the data flow that needs to be sent to the second UP, and sends the quota to the second UP.
  • the CP In the case of online charging, the CP needs to determine the quota that is sent to the second UP to ensure that the traffic generated on the second UP can be counted and billed.
  • the CP can determine the quota that is delivered to the second UP (the OCS does not sense the UP migration) or apply for a new quota to the OCS (the OCS perceives the UP migration, because the migration causes the quota to be required. Reissue).
  • the charging during user plane migration ensures the continuity and accuracy of charging.
  • the data stream is a data stream of a PDU session.
  • the first UP (UP1) is the UP before the migration
  • the second UP (UP2) is the UP after the migration.
  • the change in the UP carrying the data stream includes one of the following conditions:
  • Case A The CP first disconnects the connection with the UE and the UP1, and then establishes the connection between the UE and the UP2, that is, one PDU Session only corresponds to one UP at the same time.
  • the case of SSC mode 2 belongs to case A;
  • Case B The CP establishes the connection between the UE and the UP2, but does not remove the connection with the UP1, that is, one PDU Session corresponds to multiple UPs at the same time.
  • the CP may be the same as the service data flow after being migrated to the UP2 and then disconnected from the UP1 (all the data flows of the PDU Session are migrated), or the UP2 connection is not removed, but the UP2 connection is used to carry part of the traffic (PDU Session). Part of the data stream migration).
  • the case of SSC mode3 belongs to case B;
  • the CP interacts with the CTF and the accounting system to establish a charging session for the PDU session, and the UP reports the collected charging information to the CP.
  • the CP first interrupts the PDU session between the UE and the UP1, and then establishes the PDU session between the UE and the UP2. At this time, the UP of the data flow changes. The following describes whether the data flow is migrated between the UPs according to the OCS. Billing processing method:
  • the charging processing method for the OCS-aware data flow to migrate between the UPs is as follows:
  • Step 501 The CP determines that the UP of the data stream is to be changed, and the CP first interrupts the PDU Session of the UE and the UP1, and establishes a PDU Session of the UE and the UP2; (the UP of the charging information collection changes)
  • Step 502 The CP initiates the interruption of the PDU session on the UP1, and receives the charging information reported by the UP1. Specifically, the CP initiates the release of the PDU Session of the UP1, and establishes the PDU Session of the UP2. The PDU session release process on the UP1 triggers the UP1 to report the accounting information to the CP.
  • the report of the UP1 includes the cause of the report (that is, the trigger condition for triggering the report).
  • the reason for the report is PDU Session Release.
  • Step 503 The CP generates the charging information reported to the OCS according to the charging information reported by the UP1, and reports the information to the OCS, and the reporting reason indicates that the UP is changed, and the new quota used by the data flow on the second UP is applied;
  • the reported information carries UP1 information (such as an IP address).
  • Reporting-Reason (specify the reason for reporting: UP changed)
  • Step 504 The OCS sends a new quota for the data flow on the second UP to the CP.
  • Step 505 The CP generates the information that is sent to the UP2 according to the new quota, and the information carries the new quota corresponding information, and sends the generated information to the UP2, so that the UP2 uses the new quota for the subsequent data flow.
  • the information generated by the new quota granted by the OCS is sent to the UP2 before the PDU session is established on the UP2 or the PDU session is established on the UP2 and the data stream is transmitted.
  • the delivered information includes the data flow detection rule and the threshold information corresponding to the new quota, and carries the associated information of the two.
  • the solution of the embodiment of the present invention implements the charging process when the user plane of a PDU session is switched in the network control and the data flow forwarding and separation architecture.
  • the UP1 is triggered to report the accounting to the CP.
  • the information is further reported by the CP to the OCS, and the reporting reason is indicated as UP change, and the new quota is applied to the UP2, so that the OCS perceptible data flow is migrated and charged between the UPs. Since the OCS perceives the migration of the data stream on the UP plane, the OCS can perform different rates for the service data flow on different UPs to support more flexible and reasonable charging, and also reduces the burden of the CP participating in the quota management. .
  • A2 The charging processing method in which the OCS does not perceive the migration of the data flow between the UPs, refer to FIG. 6, and the specific steps are as follows:
  • Step 601 The CP determines that the UP of the data flow is to be changed (the UP of the charging information collection is changed), and the CP first interrupts the PDU Session of the UE and the UP1, and establishes a PDU Session of the UE and the UP2;
  • Step 602 The CP initiates the interruption of the PDU Session on the UP1, and receives the charging information reported by the UP1.
  • the CP initiates release of the PDU Session of UP1 and establishes a PDU Session of UP2.
  • the PDU session release process on the UP1 triggers the UP1 to report the accounting information to the CP.
  • the report of the UP1 includes the cause of the report (that is, the condition for triggering the report).
  • the reason for the report is PDU Session Release.
  • Step 603 The CP determines the remaining available quota according to the charging information of the data flow reported by the UP1, and generates information that is sent to the UP2 according to the remaining available quota, where the information carries the remaining available quota corresponding information.
  • the method for determining the remaining available quota based on the accounting information reported by the UP1 is as follows:
  • the UP1 can report only the usage information of the quota.
  • the CP subtracts the usage information of the quota reported by the UP1 according to the cached quota information, that is, the remaining available quota.
  • Quota ID Reporting Reason Reporting Trigger
  • the UP1 reports the quota usage information and the remaining quota value.
  • the CP uses the remaining quota value reported by the received UP1 as the remaining available quota.
  • Quota ID Reporting Reason Reporting Trigger
  • Billing information ⁇ Usage information, remainder quota ⁇
  • the CP After obtaining the remaining available quota, the CP further determines whether the condition for reporting to the OCS is satisfied. The judgment is based on the trigger condition issued by the OCS. For example, if the remaining quota is just below the threshold specified by the OCS, the satisfaction is satisfied. The conditions reported by OCS. If it is satisfied, the information reported to the OCS is generated based on the UP1 report, and the new quota is reported to the OCS, and the reason for the report indicates the trigger condition that is satisfied. If the condition for reporting to the OCS is not met, the information sent to the UP2 is generated according to the remaining available quota, and the information carries the remaining available quota corresponding information.
  • Step 604 The CP sends the information carrying the remaining available quota to the UP2, so that the UP2 uses the remaining available quota for the subsequent data flow.
  • the information generated by the remaining available quota is sent to the UP2 before the PDU session is established on the UP2 or the PDU session is established on the UP2 and the data stream is transmitted.
  • the CP processes the accounting information reported by UP1 in any of the following ways:
  • the CP caches the usage information reported by UP1;
  • the CP also sends the information reported by UP1 to UP2 at the same time. UP2 continues to count on this basis.
  • Step 605 The CP receives the usage information reported by the UP2 when the reporting condition is satisfied, and generates the information reported to the OCS according to the usage information reported by the UP1 and the UP2, and reports the information to the OCS.
  • the CP caches the accounting information reported by the UP1
  • the CP combines the usage information reported by the UP2 with the usage information reported by the cached UP1, and generates the accounting information reported to the OCS, and reports the information to the OCS;
  • the information reported by the UP1 is also sent to the O2, and the UP2 continues to accumulate based on the usage information of the UP1, and the combined information is reported.
  • the CP generates the accounting information reported to the OCS according to the accounting information reported by the UP2, and reports the information to the OCS.
  • the solution of the embodiment of the present invention implements the charging process when the user plane of a PDU session is switched in the network control and the data flow forwarding and separation architecture.
  • the UP1 is triggered to report the accounting to the CP.
  • the information is used by the CP to process the remaining quotas after the data stream is migrated according to the accounting information reported by the UP1.
  • the OCS does not perceive the migration of the UP, and reduces the number of signaling reported to the OCS when the OCS does not need to perform the charging processing based on the UP. , reducing the burden of OCS.
  • the CP may determine, according to the OCS indication, the related charging method in the foregoing A1 or A2 embodiment.
  • the OCS may be configured separately with the quota according to its own decision or the configuration of the operator.
  • a trigger condition (Trigger) indicating an UP change is issued.
  • the trigger condition is used to instruct the CP to initiate a re-authorization to the OCS when the UP using the quota changes.
  • Step 1 The CP determines that the UP of the data stream is to be changed (the UP of the performing charging changes), and the CP first interrupts the PDU Session of the UE and the UP1, and establishes a PDU Session of the UE and the UP2;
  • Step 2 The CP initiates the interruption of the PDU session on the UP1 and receives the charging information reported by the UP1.
  • the PDU session release process on the UP1 triggers the UP1 to report the charging information to the CP.
  • the report of the UP1 includes the cause of the report (that is, the condition for triggering the report).
  • the reason for the report is PDU Session Release;
  • Step 3 If the OCS sends a triggering condition indicating the UP change to the quota, the reporting of the UP1 causes the triggering condition to be satisfied, and the CP performs the steps 503-505 of the A1; if the OCS does not issue the trigger for indicating the UP change for the quota Condition, the CP performs steps 603-605 of A2.
  • the triggering condition for indicating the change of the UP is issued along with the quota according to the decision of the OCS, and the flexibility of the charging can be enhanced, and the autonomy of the OCS can be enhanced.
  • the CP reports the data flow to be migrated between the UPs.
  • the OCS does not need to perform the charging processing based on the UP, the CP does not report the data flow. Migration between UPs to reduce signaling.
  • the CP can determine whether the data flow of a charging key crosses the UP when the migration or the migration is performed.
  • the CP can consider whether to cross the UP. That is, the routing table can be controlled when generating the routing policy.
  • the method may be: the CP determines, according to the routing table generated by the UP1 and the UP2, and the flow template corresponding to the charging key sent by the PCF, whether the content covered by the flow template corresponding to the charging key is split into the UP1 and the UP2.
  • the routing table determines whether the data flow under a charging key crosses UP.
  • the specific method of charging is as follows:
  • Step 701 The CP determines that the UP of the data flow is to be changed (the UP of performing the charging changes);
  • Step 702 The CP initiates establishment of a PDU Session on the UP2.
  • Step 703 After the PDU session on the UP2 is successfully established, the SMF notifies the UE that the UE initiates the uplink data to be sent to the PDU Session of the UP2, and the UP2 triggers the start of SDF (Service Data Flow Start) event when receiving the upstream flow. And escalate the incident to the CP;
  • SDF Service Data Flow Start
  • Step 704 After receiving the Start of SDF event reported by the UP2, the CP sends a message requesting the reporting of the charging information to the UP1, and receives the charging information reported by the UP1.
  • the report of the UP1 includes the cause of the report (that is, the condition for triggering the report).
  • the reason for the report is PDU Session Release.
  • Step 705 The CP generates the charging information reported to the OCS according to the charging information reported by the UP1, and reports the information to the OCS, indicating that the reason is UP changed, and applying for a new quota.
  • the reported information carries UP1 information (such as an IP address).
  • Reporting-Reason (specify the reason for reporting: UP changed)
  • Step 706 The OCS sends a new quota to the CP.
  • Step 707 The CP generates the information that is sent to the UP2 according to the new quota, and the information carries the new quota corresponding information, and sends the generated information to the UP2, so that the UP2 uses the new quota for the subsequent data flow.
  • the subsequent CP After receiving the Termination of SDF event of UP1, the subsequent CP triggers the release of the PDU Session between the UE and UP1.
  • the OCS does not sense the charging processing method for the data stream to migrate between the UPs. As shown in FIG. 8, the specific steps are described as follows:
  • Step 801 The CP determines that the UP of the data flow is to be changed (the UP of performing the charging collection changes);
  • Step 802 The CP initiates establishment of a PDU Session on the UP2.
  • the CP initiates a PDU Session establishment process of the UP2.
  • Step 803 After the PDU session on the UP2 is successfully established, the UE migrates the sent uplink data stream to the PDU Session of the UP2. When receiving the upstream stream, the UP2 triggers the start of the SDF event, and reports the event to the CP.
  • Step 804 After receiving the Start of SDF event reported by the UP2, the CP sends a message requesting the reporting of the charging information to the UP1, and receives the charging information reported by the UP1.
  • the report of the UP1 includes the cause of the report (that is, the condition for triggering the report).
  • the reason for the report is PDU Session Release.
  • Step 805 The CP determines the remaining available quota according to the charging information of the data flow reported by the UP1, and generates information that is sent to the UP2 according to the remaining available quota, where the information carries the remaining available quota corresponding information.
  • the method for determining the remaining quota based on the accounting information reported by the UP1 is as follows:
  • the UP1 If the quota information is cached by the CP, the UP1 only reports the usage information of the quota.
  • the CP subtracts the usage information of the quota reported by the UP1 according to the cached quota information, that is, the remaining available quota.
  • Quota ID Reporting Reason Reporting Trigger
  • the UP1 reports the usage information of the quota and the remaining quota value.
  • the CP uses the remaining quota value reported by the received UP1 as the remaining available quota.
  • the CP After obtaining the remaining available quota, the CP further determines whether the condition for reporting to the OCS is satisfied. The judgment is based on the trigger condition issued by the OCS. For example, if the remaining quota is just below the threshold specified by the OCS, the satisfaction is satisfied. The conditions reported by OCS. If it is satisfied, the information reported to the OCS is generated based on the UP1 report, and the new quota is reported to the OCS, and the reason for the report indicates the trigger condition that is satisfied. If the condition for reporting to the OCS is not met, the information sent to the UP2 is generated according to the remaining available quota, and the information carries the remaining available quota corresponding information.
  • Step 806 The CP sends the generated information to the UP2, where the information carries the remaining available quota, so that the UP2 uses the remaining available quota for the subsequent data flow.
  • the CP processes the accounting information reported by UP1 in any of the following ways:
  • the CP caches the usage information reported by UP1.
  • the CP will also send the information reported by UP1 to UP2 at the same time. UP2 continues to count on this basis.
  • Step 807 The CP receives the usage information reported by the UP2 when the reporting condition is satisfied, and generates the information reported to the OCS according to the usage information reported by the UP1 and the UP2, and reports the information to the OCS.
  • the CP caches the accounting information reported by the UP1
  • the CP combines the usage information reported by the UP2 with the usage information reported by the cached UP1, and generates the accounting information reported to the OCS, and reports the information to the OCS. If the information that is reported by the UP1 is also sent to the UP2, the UP2 continues to accumulate based on the usage information of the UP1 and merges the report.
  • the CP generates the accounting information reported to the OCS according to the accounting information reported by the UP2, and sends the information to the OCS. Reported.
  • the CP uses the start of SDF event reported by the UP2 as a flag for the PDU session of the UP2 to be successfully established and starts the data transmission, and triggers the sending of the message requesting the reporting of the charging information to the UP1.
  • a PDU Session corresponds to multiple UPs at the same time, and the data flow of the same charging key does not charge across the UP.
  • the B11 and B12 schemes further distinguish whether the OCS is aware of the migration processing mode, so that the charging processing is more flexible. .
  • the CP determines the method of using the above B11 or B12 according to the OCS indication.
  • the triggering condition for indicating the UP change may be issued along with the quota, or the trigger condition may not be issued.
  • the triggering condition is used to instruct the CP to initiate a re-authorization to the OCS when the UP using the quota changes.
  • Step 1 The CP determines that the UP of the data flow is to be changed (the UP of the execution charging changes);
  • Step 2 The CP initiates the establishment of a PDU session on UP2.
  • Step 3 The UE migrates the sent uplink data stream to the PDU Session of the UP2, and the UP2 triggers the Start of SDF event when the uplink of the UE is received, and reports the event to the CP.
  • Step 4 After receiving the start of the SDF event reported by the UP2, the CP sends a message requesting the reporting of the charging information to the UP1, and receives the charging information reported by the UP1.
  • the reporting information of the UP1 includes the reporting reason (ie, triggering the reporting). Condition), the reason for reporting here is PDU Session Release.
  • Step 5 If the OCS sends a trigger condition indicating the UP change to the quota, the UP1 reports that the trigger condition is satisfied, and the CP performs steps 705-707 of B11; if the OCS does not issue the UP change for the quota. The trigger condition then the CP performs steps 805-807 of B12.
  • the triggering condition indicating the UP change is issued along with the quota according to the self-decision or the configuration of the operator, thereby enhancing the flexibility of the charging and improving the autonomy of the OCS.
  • the right instructs the CP to report the migration of the data flow between the UPs, and does not need to perform charging based on the UP in the OCS. During processing, the CP does not report the migration of data streams between UPs to reduce signaling.
  • the CP can determine whether the data flow of a charging key crosses the UP or the routing table can be controlled by the routing table.
  • the specific method can be: the routing table generated by the CP according to the UP1 and the UP2, and the routing table issued by the PCF.
  • the flow template corresponding to the charging key determines whether the content covered by the flow template corresponding to a charging key is divided into the routing tables of UP1 and UP2, and further determines whether the data flow under a charging key crosses UP, and the example of Table 3 above
  • the SF1 data stream corresponding to CK1 spans UP.
  • the specific processing methods for billing are as follows:
  • B21 and CP manage quotas, including controlling the use and reporting of quotas
  • CP and OCS can interact directly through serviced messages
  • a PDU Session uses a charging session, that is, does not add a new charging session due to the migration of the data stream.
  • the following steps do not involve the CP and the OCS.
  • the part of the interaction also applies to the way the service protocol interface is used. The specific steps are as follows:
  • Step 901 The CP determines to collect the UP of the charging information.
  • the CP needs to determine the UP of the collection of the accounting information, and the CP determines the UP of the collection of the charging information according to the policy sent and activated by the PCF.
  • UP1 and UP2 are the charging collection points determined by the CP.
  • the CP determines the timing of collecting the UP of the charging information, and the CP determines the timing of the CK data flow across the UP, and does not have a strict timing relationship.
  • Step 902 The CP processes the quota granted by the OCS.
  • the quota granted by the OCS here includes the newly granted quota of the OCS (the CP applies for the quota to the OCS according to the charging key), or the unused available quota on the UP1 obtained by the CP.
  • the CP must separately control the quota for each UP, including: the issuance of quotas and the reporting of usage information.
  • the policy for different UPs issued by the PCF uses the same charging key, and the OCS allocates quota according to the charging key. Therefore, the quota allocated by the CP for the OCS may be a cross-UP quota. To prevent the quota allocated by the OCS from being UP, or to use it after the UP, the specific method is as follows:
  • Step 9021 The CP applies to the OCS for the quota of the charging key regardless of whether the charging key crosses UP.
  • Step 9022 After receiving the quota allocated by the OCS, the CP determines whether the quota is shared by multiple UPs when generating the rule that is sent to the UP. Specifically, the CP may distribute according to the data flow corresponding to the charging key corresponding to the quota. Determining in different UPs, if the data flow corresponding to the charging key is distributed over multiple UPs, it means that the quota is shared by multiple UPs;
  • Step 9023 If the CP detects that a quota is across the UP, the policy is divided into a small quota, and a small quota is divided for each UP, and then the rule issued to the UP is sent to the UP for execution.
  • the CP records the small quotas after the division and the correspondence with UP.
  • Step 9024 The CP receives the charging data reported by any UP (such as UP1) when the quota is exhausted or when the reporting condition is met.
  • the CP sends a request to the other UP to report the quota according to the corresponding relationship between the saved small quota and the UP.
  • the CP can perform the following processing:
  • the CP combines the usage information of the quota reported by all the UPs into one message and reports it to the OCS.
  • the usage information of each UP in the message is used as a separate container, and the container corresponding to the information reported by the UP1 includes the satisfied trigger and the corresponding UP identifier, and the container corresponding to the information reported by the other UP, including the information indication.
  • the report is caused by other reports. Specifically, the related trigger may be carried in the container, or the value of the Reporting Reason indicates that the report is associated with the report and carries the corresponding UP identifier.
  • Used-Service-Unit corresponds to UP1
  • Used-Service-Unit corresponds to UP2
  • Reporting-Reason (specify the reason for reporting: report together)
  • the merged part merges the parts before the Tariff-Time-Change in the report information of each UP, and the subsequent parts are merged.
  • the report may also carry the reason for the report.
  • the reason is: the report caused by a certain UP.
  • Reporting-Reason (specify the reason for reporting: escalation caused by an UP)
  • the CP caches the usage information reported by each UP (this information will be reported to the OCS when it is reported to the OCS next time), summarizes the remaining remaining available quotas, and then re-segments into small quotas (each UP allocates a small quota) and Send it to UP to continue using it.
  • the CP needs to add one step to judge: if the condition for reporting to the OCS is met (the reporting condition may be a re-authorization trigger condition issued by the OCS, or a quota usage restriction condition, such as a quota expiration, etc.), then a) Otherwise, execute b).
  • the reporting condition may be a re-authorization trigger condition issued by the OCS, or a quota usage restriction condition, such as a quota expiration, etc.
  • the solution of the B21 embodiment of the present invention controls the use of quotas on multiple UPs through the CP, coordinates the use of quota sharing among multiple UPs, and shields the impact of the complexity of quota usage on the OCS, thereby improving the efficiency of the OCS.
  • the CP establishes a new online charging session for the UP2.
  • the CP establishes a new online charging session for the UP2.
  • Step 1001 The CP determines the UP of collecting the charging information.
  • the CP needs to determine the UP of the charging information. Specifically, the CP receives the policy activated by the PCF, and determines the UP of the charging information according to the policy.
  • both UP1 and UP2 are charging information collection points.
  • Step 1002 The CP determines that the service data flow corresponding to a charging key of the PDU session crosses the UP, and initiates a new UP2 proprietary online charging session to the OCS for the newly established UP that needs to perform online charging statistics.
  • the figure is only an example. It should be noted that the timing of the CP determining the UP of the charging information and the timing of the CP determining the CK data stream across the UP do not have a strict timing relationship.
  • the CP determines the current SSC mode. If it is the SSC mode 3, it is presumed that a service data flow corresponding to a certain charging key may cross the UP, and a new charging session is initiated for the UP2;
  • a service data flow corresponding to a specific charging key may span UP1 and UP2, and a new charging session is initiated for UP2.
  • the above judgment is also performed after determining that the UP of the online charging statistics needs to be performed. If the service data flow corresponding to a specific charging key crosses UP1 and UP2, UP2 or BP or UL CL to perform online charging function initiates the establishment of a new charging session.
  • the CP saves the correspondence between the UP and the charging session.
  • the CP applies for quotas, manages quota usage, and reports quota usage information for UP2 in the new accounting session.
  • Step B1003 The CP initiates the removal of the charging session corresponding to UP1 to the OCS when the PDU session on the UP1 is removed or when there is no data flow on the UP1.
  • the quota usage information collected on UP1 is reported to the OCS when the session is removed.
  • Step 1101 The CP determines to delete the PDU Session on the UP1.
  • Step 1102 The CP sends a message to the UP1 to delete the PDU Session.
  • Step 1103 The CP receives the charging information reported by the UP1.
  • Step 1104 The CP initiates the end of the charging session to the OCS according to the saved relationship between the UP1 and the corresponding charging session, and carries the usage information reported by the UP1.
  • the online charging session of other UPs is not affected by the end of the PDU session on UP1, and is not affected by the end of the online charging session corresponding to UP1.
  • the solution of the B22 embodiment of the present invention establishes an independent charging session for each UP through the CP, which reduces the implementation complexity of the CP and the OCS, and the CP does not need to coordinate the use of a quota among multiple UPs.
  • Solution C The embodiment of the present invention further provides a charging method, which describes from a static perspective that the CP interacts with its corresponding two UPs and the charging system, completes collection and reporting of charging information, and applies for quotas. And the process of issuing.
  • the method includes: the control plane function entity CP acquires charging information of a data flow on a PDU session corresponding to the CP from the first user plane function entity UP and the second UP, the first UP and the second UP The UP corresponding to the CP; the CP divides the quota issued by the charging system into a plurality of sub-quotas, and delivers the quotas to the first UP and the second UP respectively.
  • the CP acquires charging information of the data stream from the first UP and the second UP at the same time; for Diameter In the case of a protocol interface, the CP charges the first UP and the second UP through a charging session with the charging system.
  • the CP divides the quota issued by the charging system into a plurality of sub-quotas and sends the quotas to the UP, and the CP divides the quotas issued by the charging system for the charging key into multiple sub-quotas and respectively delivers them to the sub-quotes.
  • the method further includes: after the quota is used up on the UP and reporting the charging information corresponding to the quota, the CP obtains the charging information corresponding to the quota calculated by the other UP; The accounting information corresponding to the quota is reported to the charging system.
  • the method further includes: after the quota is used up on the UP and reporting the charging information corresponding to the quota, the CP obtains the charging information corresponding to the quota calculated by the other UP; the CP caches all The charging information corresponding to the quota reported by the UP, determining the remaining available amount of the quota, reallocating the remaining available amount of the quota, and delivering the re-allocated quota to the first UP and the second UP; When the quota is used up or the remaining available amount of the quota meets the reporting threshold, the CP combines the billing information corresponding to the cached quota, and reports the merged billing information to the billing system.
  • the CP can simultaneously charge the data streams generated on the corresponding two UPs.
  • the billing system includes an online billing system OCS and an offline billing system OFCS.
  • Offline charging only involves the collection and reporting of accounting information (including the triggering conditions for reporting).
  • online charging includes quota granting and quota usage management (including quota usage).
  • Conditional monitoring includes dynamic Trigger (trigger conditions for OCS activation), and quota usage information reporting.
  • the accounting report is applicable to the reporting in the online charging and the reporting in the offline charging, and the charging quota application, the quota usage management, and the dynamic Trigger are only applicable to the online charging.
  • Step 1 The CP determines that the UP of the data stream is to be changed (the UP of the performing charging changes), and the CP first interrupts the PDU Session of the UE and the UP1, and simultaneously establishes the PDU Session of the UE and the UP2;
  • Step 2 The CP initiates the interruption of the PDU Session on UP1 and receives the charging information reported by UP1.
  • the PDU session release process on the UP1 triggers the UP1 to report the accounting information to the CP.
  • the report of the UP1 includes the cause of the report (that is, the condition for triggering the report).
  • the reason for the report is PDU Session Release.
  • Step 3 The charging system senses the UP switch.
  • the CP reports the accounting information to the CDF/CGF/BS, and reports the reason for “UP switching”.
  • Step 3 ′ (the charging system does not sense the UP switch):
  • the CP caches the usage information of the UP1 and waits for the UP2 to report the usage information. After receiving the usage information of the UP2, the CP reports the usage information reported by the UP2 and the cached UP1. The information is used for merging, and the combined information is reported to the CDF/CGF/BS.
  • Step 1 The CP determines that the UP of the data flow is to be changed (the UP of the performing charging changes), and the CP first establishes the PDU Session of the UE and the UP2, and after the data flow is switched to the UP2, the PDU Session of the UE and the UP1 is interrupted;
  • Step 2 The CP initiates establishment of a PDU Session on UP2.
  • Step 3 The UE switches the sent uplink data stream to the PDU Session of the UP2, and when the uplink stream is received, the UP2 triggers the start of the SDF event, and reports the event to the CP.
  • Step 4 After receiving the start of the SDF event reported by the UP2, the CP sends a message requesting the reporting of the charging information to the UP1, and receives the charging information reported by the UP1.
  • the report of the UP1 includes the cause of the report (that is, the condition for triggering the report).
  • the reason for the report is PDU Session Release.
  • Step 5 The charging system detects the UP switch.
  • the CP reports the accounting information to the CDF/CGF/BS, and reports the reason "UP switching".
  • Step 5 ′ (the charging system does not sense the UP switch):
  • the CP caches the usage information of the UP1, and waits for the UP2 to report the usage information. After receiving the usage information of the UP2, the CP reports the usage information reported by the UD2 and the cached UP1. The information is used for merging, and the combined information is reported to the CDF/CGF/BS.
  • the offline solution of the embodiment of the present invention also implements the service of the user when the user plane of a PDU Session is switched, or when there are multiple user planes in one PDU Session, in a scenario where the user plane of a PDU session is switched.
  • the billing in the case of the data stream being migrated between the user planes enables the offline billing to support the end-to-end delay of the service and optimize the deployment of the network efficiency, so as to achieve accurate billing of the data service under optimized deployment. Improve network efficiency and user experience.
  • the solution provided by the embodiment of the present application is mainly introduced from the perspective of interaction between the network elements. It can be understood that the foregoing CP, UP or OCS/OFCS, in order to implement the above functions, includes corresponding hardware structures and/or software modules for performing various functions. Those skilled in the art will readily appreciate that the present application can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.
  • the embodiment of the present application may divide the function modules of the CP and the OCS/OFCS according to the foregoing method example.
  • each function module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present application is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 12 shows a possible structural diagram of the CP involved in the foregoing embodiment as the charging device 1200.
  • the charging device 1200 includes a determining module 1202, an obtaining module 1206, and a processing module 1208.
  • the determining module 1202 is configured to determine that the data stream transmitted by the user equipment UE on the first data session needs to be migrated to the second data session, where the first data session is a data session between the UE and the first user plane function entity UP;
  • the second data session is a data session between the UE and the second UP, where the first UP and the second UP are UPs corresponding to the charging device, and the first data session and the second data session correspond to The same PDU session.
  • the obtaining module 1206 is configured to obtain charging information before the data flow migration of the first UP statistics.
  • the processing module 1208 is configured to determine a quota used after the migration of the data stream that needs to be sent to the second UP, and send the quota to the second UP.
  • the accounting information reporting interface can be a Diameter protocol interface or a serviced interface.
  • the accounting session is not established between the CP and the charging system, but directly through the serviced message.
  • the serviced message (such as Restful) is a stateless message, and each message carries complete information.
  • a charging session needs to be established between the CP and the charging system.
  • the session module 1204 is configured to establish a first charging session with the charging system, and charge the data flow on the first UP by using the first charging session;
  • the determining module 1202 is further configured to: after the data stream is migrated from the first UP to the second UP, the first UP does not use another data stream that uses the charging key corresponding to the data stream, and the session module 1204 Further, the charging is performed by using the first charging session for the data flow on the second UP.
  • the obtaining module 1206 is configured to receive the charging information before the data flow that is reported by the first UP, and report the charging information to the charging system by using the session module 1204, which is the second UP. Applying a quota for the data flow; the session module 1204 is configured to receive the quota that is sent by the charging system; and the processing module 1208 generates a second to the second, according to the quota issued by the charging system. The quota issued by the UP.
  • the processing module 1208 is configured to determine, according to the obtained charging information of the first UP statistics, the remaining available quotas, and generate the remaining available quotas according to the remaining available quotas. The quota issued.
  • the obtaining module 1206 is configured to receive, by using the first data session interruption, the charging information that is triggered by the first UP.
  • the obtaining module 1206 is configured to obtain the charging information before the data stream migration on the first UP after the data flow start event corresponding to the data flow reported by the second UP.
  • the determining module 1202 is configured to determine, after the data flow is migrated from the first UP to the second UP, the first UP has another data flow that uses a charging key corresponding to the data flow;
  • the obtaining module 1206 is further configured to acquire charging information of the data stream from the first UP and the second UP at the same time.
  • the determining the module 1202 is further configured to: after determining that the data flow is migrated from the first UP to the second UP, the first UP has another data stream that uses a charging key corresponding to the data stream;
  • the session module 1204 is further configured to use a second charging session of the second data session establishment and charging system for transmitting the data flow on the second UP, and apply for a quota to the charging system by using the second charging session,
  • the processing module 1208 is further configured to send the quota of the application to the second UP.
  • FIG. 13 is a schematic diagram showing a possible structure of the charging system 1300 involved in the foregoing embodiment.
  • the charging system 1300 includes: a sending module 1302 and receiving Module 1304,
  • the sending module 1302 is configured to send the indication information to the control plane function entity CP, where the indication information is used to indicate that the CP after the user plane function entity UP corresponding to the CP is switched from the first UP to the second UP.
  • the charging information before the first UP switching is reported to the OCS; the receiving module 1304 is configured to receive the charging information before the switching of the first UP statistics reported by the CP.
  • the charging system is an online charging system OCS, and the indication information is sent along with a quota issued by the OCS to the CP.
  • the OCS after receiving the charging information reported by the CP, the OCS sends a new quota to the CP.
  • the OCS after receiving the charging information reported by the CP, the OCS sends a second UP to the CP, or a quota of the first UP and the second UP.
  • the "module" in the embodiment of FIG. 12 and FIG. 13 may be an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor and a memory that execute one or more software or firmware programs, a combination logic circuit, and Other components that provide the above features.
  • ASIC Application Specific Integrated Circuit
  • the foregoing charging device and the charging system are implemented by using a computer device.
  • the receiving module and the sending module may be implemented by a processor, a memory, and a communication interface of the computer device, where the processing module may be processed by the computer device. And memory to achieve.
  • the computer device 300 illustrated in FIG. 3 only shows the processor 302, the memory 304, the communication interface 306, and the bus 308, those skilled in the art will appreciate that the above-described charging device and The billing system also contains other devices necessary to achieve proper operation.
  • the above charging device and charging system may also include hardware devices that implement other additional functions.
  • the above-described charging device and billing system may also only include the devices necessary to implement the embodiments of the present application, and do not necessarily include all of the devices shown in FIG.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • a computer readable storage medium A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) or a processor to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Meter Arrangements (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种计费方法，控制面功能实体CP确定用户设备UE在第一数据会话上传输的数据流需要迁移到第二数据会话上，所述第一数据会话是UE和第一用户面功能实体UP间的数据会话；所述第二数据会话是所述UE和第二UP间的数据会话，所述第一UP和第二UP为所述CP对应的UP，所述第一数据会话和第二数据会话对应同一个PDU session，所述CP通过与计费***之间的第一计费会话对所述第一UP上的所述数据流计费；所述CP获取第一UP统计的所述数据流迁移前的计费信息；所述CP确定需要向第二UP下发的所述数据流迁移后使用的配额，并下发给第二UP，实现了一个PDU Session的用户面发生切换时，或者一个PDU Session存在多个用户面时，用户的业务数据流在用户面之间迁移情况下的计费。

Description

一种计费方法及设备
本申请要求于2017年8月3日提交中国专利局、申请号为201710657128.9，发明名称为“一种计费方法及设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种计费方法及装置。
背景技术
目前在线计费的基本机制是：计费触发功能(Charging Trigger Function，CTF)向在线计费***(Online Charging System，OCS)申请预留某一费率组(Rating Group)的配额，OCS授予配额，CTF执行配额管理、配额使用及计费信息采集，并在监测到计费上报条件(触发条件)满足时，向计费***上报所采集的计费信息。
在4G网络中，位于网关的策略和计费执行功能(Policy and Charging Enforcement Function，PCEF)为CTF，PCEF会根据策略和计费规则功能(Policy and Charging Rules Function，PCRF)下发的计费策略确定计费模式(在线计费或离线计费)、统计方法(流量或时长等)、费率组(Rating Group，本申请称之为charging key)、上报粒度等。其中，计费粒度包括：SERVICE_IDENTIFIER_LEVEL或RATING_GROUP_LEVEL，如果计费粒度为RATING_GROUP_LEVEL，则PCEF必须为每个费率组上报计费信息，如果计费粒度为SERVICE_IDENTIFIER_LEVEL，则PCEF必须为每个费率组和业务标识上报计费信息。
随着数据流量的剧增，对移动网络提出了新的挑战。为了应对此挑战，演进出了控制面和用户面分离的移动数据网架构。在此架构下，控制面只做控制，可以集中部署；数据流在用户面通过，分布式部署。用户可以就近接入用户面，减少数据在网络中的传输距离，减小网络时延，提高网络效率。
目前，4G网络下已经扩展了控制面和用户面分离的网络架构，可以一定程度上实现对于控制面和用户面分离的网络架构下计费。如图1所示，Serving Gateway-C、PDN Gateway-C、TDF-C属于控制面，Serving Gateway-U、PDN Gateway-U、TDF-U属于用户面。一般来说，控制面是计费触发点，完成计费触发功能，用户面是计费采集点，完成计费采集功能，在此架构下，控制面的数量和用户面在运行态的数量是1比1的关系。
然而，随着移动流量剧增、接入设备量剧增、业务对带宽时延等的增强需求，逐渐演变出了面向未来业务需求的较为复杂的网络架构，例如随着用户的移动、用户面负荷的压力、用户业务的特殊需求，使得用户所接入的用户面可能会出现较为频繁的切换，或者，一个用户同时会有多个用户面，用户的业务数据流在不同用户面之间迁移，目前的计费机制无法在这样的场景下实现准确的计费处理。
发明内容
本申请的实施例提供一种计费方法，主要解决在网络控制和数据流转发分离架 构中，一个PDU Session的用户面发生切换时，或者一个PDU Session存在多个用户面时，用户的业务数据流在用户面之间迁移的计费处理。
第一方面，提供一种计费方法，该方法包括：控制面功能实体CP确定用户设备UE在第一数据会话上传输的数据流需要迁移到第二数据会话上，所述第一数据会话是UE和第一用户面功能实体UP间的数据会话，所述第二数据会话是所述UE和第二UP间的数据会话，所述第一UP和第二UP为所述CP对应的UP，所述第一数据会话和第二数据会话对应同一个PDU session；所述CP获取第一UP统计的所述数据流迁移前的计费信息；所述CP确定需要向第二UP下发的所述数据流迁移后使用的配额，并下发给第二UP。基于该方案，CP获取数据流迁移前UP上的计费信息，并进一步确定迁移后需要给目标UP下发的配额并下发，实现用户的业务数据流在用户面之间迁移的计费处理的连续性。
可选的，所述CP通过与计费***之间的第一计费会话对所述第一UP上的所述数据流计费，所述CP确定所述数据流从第一UP迁移到第二UP后，所述第一UP上无使用所述数据流对应的charging key的其他数据流；所述CP为第二UP上所述数据流使用所述第一计费会话进行计费，基于该方案，可以不改变切换后的计费会话。
可选的，所述CP获取第一UP统计的所述数据流迁移前的计费信息，确定需要向第二UP下发的配额并下发给第二UP，包括：所述CP接收第一UP上报的所述数据流迁移前的计费信息，向计费***上报所述计费信息，并为第二UP申请用于所述数据流的配额；所述CP接收所述计费***下发的所述配额；所述CP根据所述计费***下发的配额，生成向第二UP下发的配额，基于该方案，计费***感知到迁移的发生，可以对UP的切换计费进行更加准确的配额控制。
可选的，所述CP获取第一UP的计费信息，确定需要向所述第二UP下发的配额，包括：所述CP根据获取的第一UP统计的所述数据流迁移前的计费信息，确定剩余的可用配额，并根据所述剩余的可用配额生成向第二UP下发的配额。基于该方案，计费***不需要感知到UP的切换，或者数据流的迁移，可以减轻计费***的负担。
可选的，所述方法还包括：所述CP缓存第一UP上报的所述数据流迁移前的计费信息；所述CP接收第二UP上报的所述数据流迁移后的计费信息；所述CP合并所述第二UP上报的计费信息和所缓存的第一UP上报的计费信息，将合并后的计费信息上报给计费***。
可选的，所述方法还包括：所述CP将第一UP上报的所述数据流迁移前的计费信息发送给第二UP，使得第二UP基于所述第一UP上报的所述数据流迁移前的计费信息，继续统计所述数据流迁移后的计费信息；所述CP接收第二UP在满足上报条件时上报的所述数据流迁移前和迁移后的计费信息，并上报给计费***。
可选的，所述CP根据所述计费***下发的指示，确定所述PDU session上的数据流从第一UP迁移到第二UP后，向计费***上报所述数据流迁移前的计费信息。基于该方案，计费***可以设置数据流切换相关的计费上报指示下发给CP，增强计费的灵活性。
可选的，所述CP获取第一UP统计的所述数据流迁移前的计费信息，包括：所 述CP接收第一数据会话中断触发第一UP上报的计费信息。
可选的，所述CP获取第一UP统计的所述数据流迁移前的计费信息，包括：所述CP检测到第二UP上报的所述数据流对应的数据流开始事件后，获取第一UP上统计的所述数据流迁移前的计费信息。
可选的，所述方法进一步包括：所述CP通过与计费***之间的第一计费会话对所述第一UP上的所述数据流计费，所述CP确定所述数据流从第一UP迁移到第二UP后，所述第一UP上存在使用所述数据流对应的charging key的其他数据流；所述CP为第二UP上所述数据流使用所述第一计费会话；所述CP同时从所述第一UP和第二UP上获取所述数据流的计费信息。这里的“其他”是指相对于迁移过去的数据流，没有迁移过去的，叫做“其他”数据流，它们都是CP建立的PDU session上的数据流。基于该方案，可以实现SSC mode3下的数据流准确计费，确保跨CK的数据流不因为UP的切换而被忽略。
可选的，所述CP进一步确定需要向第一UP下发的配额，所述方法包括：所述CP将计费***为所述charging key下发的配额分割成多个子配额并分别下发给所述第一UP和第二UP。
可选的，所述方法进一步包括：所述CP在任一个UP上所述配额用完并上报所述配额对应的计费信息后，获取其他UP上统计的所述配额对应的计费信息；所述CP合并所述配额对应的计费信息，并上报给计费***。
可选的，所述方法进一步包括：所述CP在任一个UP上所述配额用完并上报所述配额对应的计费信息后，获取其他UP上统计的所述配额对应的计费信息；所述CP缓存所有UP上报的所述配额对应的计费信息，确定所述配额的剩余可用量，重新分配所述配额的剩余可用量，并向第一UP和第二UP下发所述重新分配的配额；所述CP在所述配额用完或者所述配额的剩余可用量满足上报阈值时，合并所述缓存的所述配额对应的计费信息，并向计费***上报所述合并的计费信息。
可选的，所述方法进一步包括，所述CP通过与计费***之间的第一计费会话对所述第一UP上的所述数据流计费；所述CP确定所述数据流从第一UP迁移到第二UP后，所述第一UP上存在使用所述数据流对应的charging key的其他数据流；所述CP为第二UP上传输所述数据流的第二数据会话使用第二计费会话，通过第二计费会话向计费***申请配额，并将申请的配额下发给第二UP；所述第二计费会话是所述CP与计费***为所述第二UP上的第二数据会话建立的计费会话。基于该方案，通过新建一个专门为目标UP计费的计费会话，来实现高效准确的计费，降低CP在配额处理上的负担。
第二方面，提供一种计费方法，所述方法包括：控制面功能实体CP从第一用户面功能实体UP和第二UP上获取所述CP对应的一个PDU session上的数据流的计费信息，所述第一UP和第二UP为所述CP对应的UP；所述CP将计费***下发的配额分割成多个子配额，并分别下发给所述第一UP和第二UP。基于该方案，CP可同时对其对应的两个UP上产生的数据流进行计费。
可选的，所述第一UP和第二UP上存在使用相同charging key的数据流；所述CP同时从所述第一UP和第二UP上获取所述数据流的计费信息；对于Diameter协议接口的情形，所述CP通过与计费***间的一个计费会话对第一UP和第二UP 进行计费。
可选的，所述CP将计费***下发的配额分割成多个子配额并下发给UP，包括：所述CP将计费***为所述charging key下发的配额分割成多个子配额并分别下发给所述第一UP和第二UP。
可选的，所述方法进一步包括：所述CP在任一个UP上所述配额用完并上报所述配额对应的计费信息后，获取其他UP上统计的所述配额对应的计费信息；所述CP合并所述配额对应的计费信息，并上报给计费***。
可选的，所述方法进一步包括：所述CP在任一个UP上所述配额用完并上报所述配额对应的计费信息后，获取其他UP上统计的所述配额对应的计费信息；所述CP缓存所有UP上报的所述配额对应的计费信息，确定所述配额的剩余可用量，重新分配所述配额的剩余可用量，并向第一UP和第二UP下发所述重新分配的配额；所述CP在所述配额用完或者所述配额的剩余可用量满足上报阈值时，合并所述缓存的所述配额对应的计费信息，并向计费***上报所述合并的计费信息。
第三方面，提供一种计费方法，包括以下步骤：在线计费***OCS向控制面功能实体CP下发指示信息，所述指示信息用于指示CP在所述CP对应的用户面功能实体UP从第一UP切换为第二UP后，向所述OCS上报所述第一UP切换前的计费信息；所述OCS接收所述CP上报的所述第一UP统计的切换前的计费信息。
可选的，所述指示信息随所述OCS下发给所述CP的配额一起下发。
可选的，所述OCS接收所述CP上报的计费信息后，向所述CP下发给第二UP，或同时给第一UP和第二UP的配额。
第四方面，提供一种计费设备，包括判断模块，获取模块和处理模块：所述判断模块，用于确定用户设备UE在第一数据会话上传输的数据流需要迁移到第二数据会话上，所述第一数据会话是UE和第一用户面功能实体UP间的数据会话；所述第二数据会话是所述UE和第二UP间的数据会话，所述第一UP和第二UP是所述计费设备对应的UP，所述第一数据会话和第二数据会话对应同一个PDU session；所述获取模块，用于获取第一UP统计的所述数据流迁移前的计费信息；所述处理模块，用于确定需要向第二UP下发的所述数据流迁移后使用的配额，并下发给第二UP。
可选的，还包括所述会话模块，用于与计费***建立第一计费会话，并通过所述第一计费会话对所述第一UP上的所述数据流计费，所述判断模块还用于确定所述数据流从第一UP迁移到第二UP后，所述第一UP上无使用所述数据流对应的charging key的其他数据流，所述会话模块进一步用于为第二UP上所述数据流使用所述第一计费会话进行计费。
可选的，所述获取模块用于接收第一UP上报的所述数据流迁移前的计费信息，并通过所述会话模块向计费***上报所述计费信息，为第二UP申请用于所述数据流的配额；所述会话模块用于接收所述计费***下发的所述配额；所述处理模块根据所述计费***下发的配额，生成向第二UP下发的配额。
可选的，所述处理模块用于根据获取的第一UP统计的所述数据流迁移前的计费信息，确定剩余的可用配额，并根据所述剩余的可用配额生成向第二UP下发的配额。
可选的，所述获取模块用于接收第一数据会话中断触发第一UP上报的计费信息。
可选的，所述获取模块用于获取第二UP上报的所述数据流对应的数据流开始事件后，第一UP上统计的所述数据流迁移前的计费信息。
可选的，还包括会话模块，用于与计费***建立第一计费会话，并通过所述第一计费会话对所述第一UP上的所述数据流计费，所述判断模块用于确定所述数据流从第一UP迁移到第二UP后，所述第一UP上存在使用所述数据流对应的charging key的其他数据流；所述获取模块进一步用于同时从所述第一UP和第二UP上获取所述数据流的计费信息。
可选的，还包括会话模块，用于与计费***建立第一计费会话，并通过所述第一计费会话对所述第一UP上的所述数据流计费，所述判断模块进一步用于确定所述数据流从第一UP迁移到第二UP后，所述第一UP上存在使用所述数据流对应的charging key的其他数据流；所述会话模块进一步用于为第二UP上传输所述数据流的第二数据会话建立和计费***的第二计费会话，通过第二计费会话向计费***申请配额，所述处理模块进一步用于并将申请的配额下发给第二UP。
第五方面，提供一种计费***，包括下发模块和接收模块，所述下发模块，用于向控制面功能实体CP下发指示信息，所述指示信息用于指示CP在所述CP对应的用户面功能实体UP从第一UP切换为第二UP后，向所述OCS上报所述第一UP切换前的计费信息；所述接收模块，用于接收所述CP上报的所述第一UP统计的切换前的计费信息。
第六方面，提供一种计算设备，实现中可以是CP，对应5G中的SMF功能实体，包括：处理器、存储器、总线和通信接口；该存储器用于存储计算机执行指令，该处理器与该存储器通过该总线连接，当该计算设备运行时，该处理器执行该存储器存储的该计算机执行指令，以使该计算设备执行如上述第一方面或者第二方面中任一所述的计费方法。
第七方面，提供一种计算设备，实现中可以是OCS功能实体，包括：处理器、存储器、总线和通信接口；该存储器用于存储计算机执行指令，该处理器与该存储器通过该总线连接，当该计算设备运行时，该处理器执行该存储器存储的该计算机执行指令，以使该计算设备执行如上述第三方面中任一所述的计费方法。
第八方面，本申请实施例提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第一方面，第二方面或者第三方面中任意一项的计费方法。
第九方面，本申请实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第一方面，第二方面或者第三方面任意一项的计费方法。
其中，第二方面至第九方面中任一种设计方式所带来的技术效果可参见第一方面中或者实施例中不同设计方式所带来的技术效果描述，此处不再赘述。
第十方面，提供一种网络***，包括如上述任一方面所述的计费设备和如上述任一方面所述的计费***。
本申请的上述方面或其他方面在以下实施例的描述中会更加简明易懂。
本发明实施例的方案，实现了在较为复杂的控制面和用户面分离场景下，例如，一个PDU Session的用户面发生切换时，或者一个PDU Session存在多个用户面时，用户的业务数据流在用户面之间迁移情况下的计费，使得计费可以支撑业务端到端的更低时延、且提高了网络的效率的优化部署，实现优化部署下数据业务的精准计费，提高网络效率和用户体验。
附图说明
图1是现有技术中控制面和用户面分离的网络架构的示意图；
图2是依据本申请一实施例的网络架构的示意图；
图3是依据本申请一实施例的计算机设备300的硬件结构示意图；
图4是依据本申请一实施例的计费方法400的示范性流程图；
图5是依据本申请一实施例的计费方法500的示范性流程图；
图6是依据本申请一实施例的计费方法600的示范性流程图；
图7是依据本申请一实施例的计费方法700的示范性流程图；
图8是依据本申请一实施例的计费方法800的示范性流程图；
图9是依据本申请一实施例的计费方法900的示范性流程图；
图10是依据本申请一实施例的计费方法1000的示范性流程图；
图11是依据本申请一实施例的计费方法1100的示范性流程图；
图12是依据本申请一实施例计费设备1200的一种可能的结构示意图；
图13是依据本申请一实施例计费***1300的一种可能的结构示意图。
具体实施方式
本申请实施例涉及的网元名称本身不对设备构成限定。具体来说，会话管理功能这个名字本身对设备不构成限定，实际中，可以为其他名字，比如：UP(User Plane)用户面功能这个名字本身对设备不构成限定，实际中，可以为其他名字，比如：用户面功能实体(User Plane Function Entity)。在线计费***这个名字本身对设备不构成限定，实际中，可以为其他名字，比如：计费***，或其他名字。在此进行统一说明，以下不再赘述。
本申请实施例方案以5G网络为例，但使用范围不限5G网络，部分4G，或者4G到5G网络的过渡网络也可能使用，也可以应用到未来的可能的其他通信或者计费***中，只要存在同一个PDU Session(或者类似的数据连接)的用户面发生切换，或者一个PDU Session存在多个用户面时，用户的业务数据流在用户面之间迁移的场景，相应的计费方法都可以采用本发明相关实施例的方案。
图2是依据本申请一实施例的网络架构的示意图。其中，SMF为会话管理功能(Session Management Function)，PCF为策略控制功能(Policy Control Function)，UPF为用户面功能(User Plane Function)，OCS为在线计费***(Online Charging System)，UE为用户设备(user equipment)。SMF与PCF之间通过N7 接口通信，SMF与UPF之间通过N4接口通信，不同UPF之间通过N9接口通信。
SMF的功能包括协议数据单元(Protocol Data Unit，PDU)会话(Session)的管理，如建立、修改和释放；UE的互联网协议(Internet Protocol，IP)地址分配；UPF选择；UPF路由策略配置；获取PCF的控制策略，并执行该控制策略的控制面部分；确定在IP类型下，PDU Session的业务及会话连续性(Service and Session Continuity，SSC)模式(称为SSC mode)，具体的，PDU会话有三种SSC模式Mode，分别为：SSC模式1、SSC模式2以及SSC模式3；SSC Mode 1：在该模式下，终端建立PDU会话之后，无论终端移动到任何区域或者任何接入技术下，该PDU会话的UPF网元均作为锚点，为该终端服务，即该PDU会话不会由于终端的移动发生任何形式的中断。SSC Mode 2：在该模式下，终端建立PDU会话之后，当终端移动，如果终端离开了UPF网元的服务区域，或者因为UPF网元故障，负载过大等原因，网络可以为终端的该PDU会话重选UPF网元，并使终端建立重选UPF网元后的PDU会话，用户的业务会从原UPF迁移到新的UPF。在这种模式下，UPF网元可以认为是有特定服务区域的，当终端在该服务区域移动时，该UPF网元为终端服务，而如果终端离开了这个服务区域，则网络侧可以确定该UPF网元则不能为终端服务，原通过该UPF网元建立的PDU会话将会发生中断，同时和新的UPF建立PDU会话。SSC Mode 3:在该模式下，终端建立PDU会话之后，UPF网元的服务区域也是有范围的，当终端离开了UPF网元的服务区域后，网络为终端选择新的UPF网元为该终端服务，终端通过该新的UPF网元与原DN网元建立PDU会话，但是与上述SSC模式2不同的是，终端通过旧的UPF网元建立的PDU会话可以暂时不释放连接，而是在新的PDU会话建立完成后再释放。
UPF的功能包括完成与外部数据网交互的锚点功能(具有锚点功能的UPF称为UPF锚点)；数据包路由和转发；数据包检测，并执行PCF激活的控制策略的用户面部分。
PCF的功能包括生成并下发策略，或者激活SMF上静态配置的策略，通过策略控制UPF上路由的业务数据流的QoS、门控、计费等。SMF可以根据PCF下发的策略确定是否和OCS建立在线计费会话，以及确定业务数据流对应的charging key。
OCS的功能包括根据SMF的请求进行配额授予，并根据SMF上报的配额使用信息进行余额扣减或返还。
UE是具有用户永久身份(Subscriber Permanent Identity，SUPI)或者国际移动用户识别码(International Mobile Subscriber Identification Number，IMSI)的设备，可以为具有SIM/eSIM的手机、平板、电脑、IoT设备、或者其他可以连接5G网络或者其他网络的设备。
本申请中配额申请、分配、计费信息上报接口可以是Diameter协议接口或者服务化接口，服务化接口如Restful等，服务化接口的方式下，CP和计费***间不建立计费会话，而是直接通过服务化消息进行交互，服务化消息(如：Restful)是无状态的消息。
本申请主要以Diameter协议进行示例说明，但本申请并不限定消息格式，也可以使用Restful API等其他格式。
本申请中涉及的一些概念，进一步说明如下：
控制面：执行PDU Session管理、IP地址分配、用户面选择等功能，本申请称之为CP或者CP功能实体，在5G核心网中对应SMF；
用户面：执行数据包路由和转发、数据包检测等，本申请称之为UP或者UP功能实体，在5G核心网中对应UPF。
PDU Session：(类似4G、4G/5G过渡网络的IP-CAN Session，后续描述中，一律用PDU session来表示相关或者类似概念)，PDU Session是建立在UE和提供PDU连接业务的数据网络(Data Network，DN)之间的，而连接DN的是UPF，因此也可以说PDU Session是建立在UE和UPF之间的。PDU Session的建立由SMF控制，因此UE会向SMF发送PDU Session建立请求，SMF来选择与UE建立连接的UPF。一个PDU Session可以存在/对应多个UPF实体。
CP、OCS和UP可以通过计算机设备的形式实现。图3是依据本申请一实施例的计算机设备300的硬件结构示意图。如图3所示，计算机设备300包括处理器302、存储器304、通信接口306和总线308。其中，处理器302、存储器304和通信接口306通过总线308实现彼此之间的通信连接。
处理器302可以采用通用的中央处理器(Central Processing Unit，CPU)，微处理器，应用专用集成电路(Application Specific Integrated Circuit，ASIC)，或者一个或多个集成电路，用于执行相关程序，以实现本申请实施例所提供的技术方案。
存储器304可以是只读存储器(Read Only Memory，ROM)，静态存储设备，动态存储设备或者随机存取存储器(Random Access Memory，RAM)。存储器304可以存储操作***3041和其他应用程序3042。在通过软件或者固件来实现本申请实施例提供的技术方案时，用于实现本申请实施例提供的技术方案的程序代码保存在存储器304中，并由处理器302来执行。
通信接口306使用例如但不限于收发器一类的收发装置，来实现与其他设备或通信网络之间的通信。
总线308可包括一通路，在各个部件(例如处理器302、存储器304、通信接口306)之间传送信息。
当计算机设备300是CP时，处理器302执行存储器304中保存的用于实现本申请实施例提供的技术方案的程序代码，以实现图4至图11实施例所示的方法。
当计算机设备300是OCS/OFCS时，处理器302执行存储器304中保存的用于实现本申请实施例提供的技术方案的程序代码，以实现图4至图10实施例所示的方法。
本申请实施例，可以实现在一个PDU Session的用户面发生切换时，或者一个PDU Session存在多个用户面时，用户的业务数据流在用户面之间迁移情况下，对数据业务的精准计费，提高网络效率和用户体验。
图4是依据本申请一实施例的计费方法400的示范性流程图。计费方法400可以由图2所示的SMF(CP)、OCS、或UPF(UP)来执行。
S401，控制面功能实体CP确定UE在第一数据会话上传输的数据流需要迁移到第二数据会话上，所述第一数据会话是CP建立的UE和第一UP(UP1)间的数据会话；所述第二数据会话是所述UE和第二UP(UP2)间的数据会话，所述第一UP和第二UP为该CP对应的UP，所述第一数据会话和第二数据会话对应同一个PDU Session；所述CP通过与计费***之间的第一计费会话对所述第一UP上的所述数据流计费；
UE和数据网络之间的数据流传输是通过建立的PDU Session来实现的，PDU Session是建立在UE和提供PDU连接业务的数据网络(Data Network，DN)之间的。PDU Session的建立由控制面功能实体CP，如SMF控制，因此UE会向CP发送PDU Session建立请求，CP来选择与UE建立连接的UP。由于存在一个PDU Session的用户面发生切换，或者一个PDU Session存在多个用户面时，用户的业务数据流在用户面之间迁移情况，将UE和用户面的PDU Session迁移到不同的用户面上，或者同时建立到两个或以上用户面上，但是在迁移过程中，两个或者多个UP是对应同一个CP，PDU Session是不变的。这里所说的“不变”，或者说“同一个”PDU session，指的是该PDU session在UP的变化过程中，控制面基本不变，具体为session ID，UE的IP地址和接入点(DNN)不变。
S402，CP获取第一UP统计的所述数据流迁移前的计费信息；
由于涉及到用户面的切换，业务数据流迁移到第二UP,计费采集点也会产生变化，这种变化包括但不限于：计费采集点从第一UP迁移到第二UP，迁移后第二UP作为唯一的计费采集点；或者迁移后第一UP和第二UP同时作为计费采集点。CP获取迁移完成之前(包括迁移过程中)第一UP上的计费信息，如果UE和第一UP的数据连接在迁移完成后依然存在的话，CP还可以继续获取第一UP的计费信息，用于迁移期间或者迁移后的配额管理，保证计费过程的连续性和准确性；
计费信息的具体的获取方式，可以是第一UP主动上报，也可以是CP向第一UP发送获取请求来获取；触发方式也可以有多种实现，例如迁移的发生(决策迁移或实际发生迁移，如第一UP会话释放)会触发第一UP主动上报；也可以是CP检测到第二UP开始传输业务数据流后，向第一UP请求上报等；具体可以通过在CP或者UP上配置相关触发条件(trigger)实现。
S403，CP确定需要向第二UP下发的所述数据流迁移后使用的配额并下发给第二UP。
对于在线计费的情况，CP需要确定给第二UP下发的配额，以保证在第二UP上产生的流量可以被统计和计费；
具体的，根据OCS对迁移是否感知，CP可以自主确定向第二UP下发的配额(OCS不感知UP迁移)或者向OCS申请新配额(OCS感知到UP迁移，因为迁移，导致需要进行配额的重新下发)。
根据本申请实施例提供的技术方案，CP决策要进行UP迁移后，会获取迁移前UP的计费信息，并进一步确定迁移后需要给目标UP下发的配额并下发，从而实现一个控制面对应多个用户面的CU分离场景下，用户面迁移时的计费，保证了计费的连续性和准确性。
下面结合更多的具体实现，说明承载数据流的UP发生变化情况下的计费处理过程。本发明实施例中，数据流为某一PDU Session的数据流，迁移过程中，PDU Session不变，第一UP(UP1)是迁移前UP，第二UP(UP2)是迁移后UP。承载数据流的UP发生变化包括如下情况之一：
情况A:CP先拆除与UE与UP1的连接,再建立UE和UP2的连接，即：一个PDU Session同时只对应一个UP。SSC mode 2的情形属于情况A；
情况B:CP建立UE和UP2的连接,但并未拆除和UP1的连接，即：一个PDU Session同时会对应有多个UP。CP可以是等业务数据流全部迁移到UP2上后再拆除和UP1的连接(PDU Session的所有数据流全部迁移)，或者不拆除UP2的连接，而是用UP2的连接承载部分业务流量(PDU Session的数据流部分迁移)。SSC mode3的情形属于情况B；
上述A,B两种情况下，CP都作为CTF和计费***进行交互，为PDU Session建立计费会话，UP向CP上报采集到的计费信息。
针对情况A，CP先中断UE与UP1的PDU Session，然后建立UE与UP2的PDU Session，此时数据流的UP发生了变化,下面根据OCS是否感知到数据流在UP间迁移，详细描述情况A下的计费处理方法：
A1、OCS感知数据流在UP间迁移的计费处理方法，参考附图5：
步骤501：CP确定要改变数据流的UP，CP将首先中断UE与UP1的PDU Session，并建立UE与UP2的PDU Session；(执行计费信息采集的UP发生变化)
步骤502：CP发起中断UP1上的PDU Session，并接收UP1上报的计费信息，具体的，CP发起释放UP1的PDU Session，并建立UP2的PDU Session。UP1上的PDU Session释放流程触发UP1向CP上报计费信息；
UP1的上报信息中包括上报原因(即：触发上报的触发条件)，这里的上报原因为PDU Session Release。
上报信息格式示例：
配额对应ID
上报原因(Reporting Trigger)
计费信息(Measurement information)
步骤503：CP根据UP1上报的计费信息，生成向OCS上报的计费信息，并向OCS上报，上报原因指明为UP变化，同时申请第二UP上该数据流使用的新配额；
上报信息中携带UP1信息(如IP地址)。
上报格式示例：Diameter格式
Used-Service-Unit
Reporting-Reason(指明上报原因：UP changed)
Tariff-Time-Change
CC-Time
CC-Total-Octets
CC-Input-Octets
CC-Output-Octets
Rating-Group
如果是Restful格式，则消息示例如下；
Figure PCTCN2018094481-appb-000001
步骤504：OCS向CP下发授予的用于第二UP上该数据流的新配额；
步骤505：CP根据该新配额，生成向UP2下发的信息，该信息携带新配额对应信息，并向UP2下发该生成的信息，以使得UP2为后续的数据流使用该新配额。
CP在UP2上建立该PDU Session时或者在UP2上完成该PDU Session建立且数据流传输之前，向UP2下发根据OCS授予的新配额生成的信息。
下发信息包括数据流检测规则和新配额对应的门限信息，并且携带了二者的关联信息。
本发明实施例的方案，实现了网络控制和数据流转发分离架构中，一个PDU Session的用户面发生切换时的计费处理，在UE和UP1的PDU session释放后，触发UP1向CP上报计费信息，CP进一步向OCS上报UP1的计费信息，上报原因指明为UP变化，并申请新配额给UP2，实现了OCS可感知数据流在UP间的迁移计费处理。由于OCS感知到数据流在UP面的迁移，可以使得OCS对不同UP上的业务数据流使用执行不同的费率以支持更为灵活和合理的计费，并且也降低了CP参与配额管理的负担。
A2：OCS不感知数据流在UP间迁移的计费处理方法，参考附图6，具体步骤说明如下：
步骤601：CP确定要改变数据流的UP(执行计费信息采集的UP发生变化)，CP将首先中断UE与UP1的PDU Session，并建立UE与UP2的PDU Session；
步骤602：CP发起中断UP1上的PDU Session，并接收UP1上报的计费信息；
具体的，CP发起释放UP1的PDU Session，并建立UP2的PDU Session。可以是UP1上的PDU Session释放流程触发UP1向CP上报计费信息。
UP1的上报信息中包括上报原因(即：触发上报的条件)，这里的上报原因为PDU Session Release。
步骤603：CP根据UP1上报的该数据流的计费信息，确定剩余可用配额，并根据该剩余可用配额生成向UP2下发的信息，该信息携带该剩余可用配额对应信息。
CP根据UP1上报的计费信息确定剩余可用配额的方法为如下之一：
如果CP向UP1下发该配额时，缓存了配额信息，则UP1可以只上报配额的使用信息，CP根据所缓存的配额信息减去UP1上报的配额的使用信息，即为剩余可用配额；
上报信息格式示例：
配额对应ID
上报原因(Reporting Trigger)
计费信息：{Usage information}
如果CP向UP1下发该配额时，未缓存配额信息，则UP1同时上报配额的使用信息和剩余配额值，CP把接收到的UP1上报的剩余配额值作为剩余可用配额。
上报信息格式示例：
配额对应ID
上报原因(Reporting Trigger)
计费信息：{Usage information，remainder quota}
CP在得到剩余可用配额后，进一步，还判断是否满足向OCS上报的条件，该判断是基于OCS所下发的触发条件来判断，比如：剩余配额刚好低于OCS所规定的门限，则满足向OCS上报的条件。如果满足则基于UP1的上报生成向OCS上报的信息，正常向OCS上报并申请新配额，上报的原因指明所满足的触发条件。若未满足向OCS上报的条件，则根据该剩余可用配额生成向UP2下发的信息，该信息携带该剩余可用配额对应信息。
步骤604：CP向UP2下发携带所述剩余可用配额的信息，以使得UP2为后续的数据流使用该剩余可用配额；
CP在UP2上建立该PDU Session时或者在UP2上完成该PDU Session建立且数据流传输之前，向UP2下发根据剩余可用配额生成的信息。
CP对UP1所上报的计费信息进行如下任一方法处理：
a.CP缓存UP1上报的使用信息；
b.CP将UP1上报的信息也同时下发给UP2，UP2在此基础上继续统计。
步骤605：CP接收UP2在上报条件满足时上报的使用信息，并根据UP1和UP2上报的使用信息生成向OCS上报的信息，并向OCS上报。
具体的，若CP缓存UP1上报的计费信息，则CP将UP2上报的使用信息和所缓 存的UP1上报的使用信息进行合并，生成向OCS上报的计费信息，并向OCS上报；若之前CP将UP1上报的信息也同时下发给了UP2，则UP2基于UP1的使用信息继续累积，并合并上报，CP根据UP2上报的计费信息生成向OCS上报的计费信息，并向OCS上报。
本发明实施例的方案，实现了网络控制和数据流转发分离架构中，一个PDU Session的用户面发生切换时的计费处理，在UE和UP1的PDU session释放后，触发UP1向CP上报计费信息，CP根据UP1上报的计费信息，自主处理数据流迁移后剩余配额的使用，OCS对于UP的迁移不感知，在OCS无需基于UP执行计费处理时，减少了向OCS上报的信令数量，降低了OCS的负担。
A3、CP可以根据OCS指示，确定使用上述A1或者A2实施例中的相关计费方法，具体的，OCS据自身决策或者运营商配置，可以单独或者在向CP下发配额时，随配额一起下发指示UP变化的触发条件(Trigger)。该触发条件用于指示CP，在使用该配额的UP发生变化时，向OCS发起重授权。具体步骤说明如下：
步骤1：CP确定要改变数据流的UP(执行计费的UP发生变化)，CP将首先中断UE与UP1的PDU Session，并建立UE与UP2的PDU Session；
步骤2：CP发起中断UP1上的PDU Session，并接收UP1上报的计费信息；UP1上的PDU Session释放流程触发UP1向CP上报计费信息。UP1的上报信息中包括上报原因(即：触发上报的条件)，这里的上报原因为PDU Session Release；
步骤3：若OCS为该配额下发了指示UP变化的触发条件，则UP1的上报使得该触发条件满足，CP执行A1的步骤503-505；若OCS没有为该配额下发指示UP变化的触发条件，CP执行A2的步骤603-605。
通过OCS在向CP下发配额时，根据自身决策或者运营商配置，随配额一起下发指示UP变化的触发条件，可以增强计费的灵活性，提升OCS的自主权，进而在需要对不同UP上的业务数据流使用执行不同的费率以支持更为灵活和合理的计费时，指示CP上报数据流在UP间的迁移，在OCS无需基于UP执行计费处理时，CP不上报数据流在UP间的迁移，以减少信令。
下面描述情况B,即CP建立UE与UP2的PDU Session，但并未拆除和UP1的连接，即：一个PDU Session同时会对应有多个UP，此时数据流的UP发生了变化，分两种情况进行处理：
B1：在建立UE到UP2的PDU Session后，若UP1上的业务数据流是以charging key(CK)为粒度迁移到UP2的，包括：UP1上的数据流全部迁移到UP2，如表1示例；
Figure PCTCN2018094481-appb-000002
表1
以及包括：UP1上部分charging key(如CK2)对应的数据流迁移到UP2，如表2示例；
Figure PCTCN2018094481-appb-000003
表2
CP可以在迁移时或者迁移后判断一个charging key的数据流是否跨UP，也可以下发路由表的时候就已经考虑了是否跨UP的情况，即可以在生成路由策略时通过路由表控制，具体方法可以是：CP根据其为UP1及UP2生成的路由表，以及PCF下发的charging key对应的流模板，判断一个charging key所对应的流模板所覆盖的内容，是否被分割到UP1和UP2的路由表，进而确定一个charging key下的数据流是否跨UP。
本实施例中，CP判断业务数据流是以CK为粒度跨UP的情况下，计费的具体方法如下：
B11、OCS感知数据流在UP间迁移的计费处理方法，参考附图7，
步骤701：CP确定要改变数据流的UP(执行计费的UP发生变化)；
步骤702：CP发起建立UP2上的PDU Session；
步骤703：UP2上的PDU Session建立成功后，SMF通知UE,UE发起将发送的上行数据流到UP2的PDU Session上，UP2在接收到上行流时，触发start of SDF(业务数据流开始)事件，并将该事件上报给CP；
步骤704：CP在接收到UP2上报的Start of SDF事件后，向UP1发送请求上报计费信息的消息，并接收UP1上报的计费信息；
UP1的上报信息中包括上报原因(即：触发上报的条件)，这里的上报原因为PDU Session Release。
上报信息格式示例：
配额对应ID
上报原因(Reporting Trigger)
计费信息(Measurement information)
步骤705：CP根据UP1上报的计费信息，生成向OCS上报的计费信息，并向OCS上报，上报原因指明为UP变化，同时申请新配额；
上报信息中携带UP1信息(如IP地址)。
上报格式示例：
Used-Service-Unit
Reporting-Reason(指明上报原因：UP changed)
Tariff-Time-Change
CC-Time
CC-Total-Octets
CC-Input-Octets
CC-Output-Octets
Rating-Group
步骤706：OCS向CP下发新配额；
步骤707：CP根据该新配额，生成向UP2下发的信息，该信息携带新配额对应信息，并向UP2下发该生成的信息，以使得UP2为后续的数据流使用该新配额；
后续CP收到UP1的Termination of SDF事件后，触发释放UE和UP1之间的PDU Session。
B12、OCS不感知数据流在UP间迁移的计费处理方法，如附图8所示，具体步骤描述如下：
步骤801：CP确定要改变数据流的UP(执行计费收集的UP发生变化)；
步骤802：CP发起建立UP2上的PDU Session；
具体的，CP发起UP2的PDU Session建立流程。
步骤803：UP2上的PDU Session建立成功后，UE将发送的上行数据流迁移到UP2的PDU Session上，UP2在接收到上行流时，触发start of SDF事件，并将该事件上报给CP；
步骤804：CP在接收到UP2上报的Start of SDF事件后，向UP1发送请求上报计费信息的消息，并接收UP1上报的计费信息；
UP1的上报信息中包括上报原因(即：触发上报的条件)，这里的上报原因为PDU Session Release。
步骤805：CP根据UP1上报的该数据流的计费信息确定剩余可用配额，并根据该剩余可用配额生成向UP2下发的信息，该信息携带该剩余可用配额对应信息；
CP根据UP1上报的计费信息确定剩余配额的方法为如下之一：
a.如果CP向UP1下发该配额时，缓存了配额信息，则UP1只上报配额的使用信息，CP根据所缓存的配额信息减去UP1上报的配额的使用信息，即为剩余可用配额；
上报信息格式示例：
配额对应ID
上报原因(Reporting Trigger)
计费信息：{Usage information}
b.如果CP向UP1下发该配额时，未缓存配额信息，则UP1同时上报配额的使用信息和剩余配额值，CP把接收到的UP1上报的剩余配额值作为剩余可用配额。
CP在得到剩余可用配额后，进一步，还判断是否满足向OCS上报的条件，该 判断是基于OCS所下发的触发条件来判断，比如：剩余配额刚好低于OCS所规定的门限，则满足向OCS上报的条件。如果满足则基于UP1的上报生成向OCS上报的信息，正常向OCS上报并申请新配额，上报的原因指明所满足的触发条件。若未满足向OCS上报的条件，则根据该剩余可用配额生成向UP2下发的信息，该信息携带该剩余可用配额对应信息。
步骤806：CP向UP2下发该生成的信息，该信息携带所述剩余可用配额，以使得UP2为后续的数据流使用该剩余可用配额；
CP对UP1所上报的计费信息进行如下任一方法处理：
–CP缓存UP1上报的使用信息；
–CP将UP1上报的信息也同时下发给UP2，UP2在此基础上继续统计。
步骤807：CP接收UP2在上报条件满足时上报的使用信息，并根据UP1和UP2上报的使用信息生成向OCS上报的信息，并向OCS上报。
具体的，若CP缓存UP1上报的计费信息，则CP将UP2上报的使用信息和所缓存的UP1上报的使用信息进行合并，生成向OCS上报的计费信息，并向OCS上报。若之前CP将UP1上报的信息也同时下发给了UP2，则UP2基于UP1的使用信息继续累积，并合并上报，CP根据UP2上报的计费信息生成向OCS上报的计费信息，并向OCS上报。
本发明B11，B12实施例的方案，CP以UP2上报的start of SDF事件作为UP2的PDU session建立成功并开始数据传输的标志，并以此触发向UP1发送请求上报计费信息的消息，实现了一个PDU Session同时对应有多个UP，并且同一个charging key的数据流不跨UP的情形下计费，B11和B12的方案进一步区分了OCS是否感知迁移的处理方式，使得计费的处理更加灵活。
B13、CP根据OCS指示，确定使用上述B11或B12的方法
OCS在向CP下发配额时，根据自身决策，可以随配额一起下发指示UP变化的触发条件，或者不下发该触发条件。该触发条件用以指示CP，在使用该配额的UP发生变化时，向OCS发起重授权，具体步骤如下：
步骤1：CP确定要改变数据流的UP(执行计费的UP发生变化)；
步骤2：CP发起建立UP2上的PDU Session
步骤3：UE将发送的上行数据流迁移到UP2的PDU Session上，UP2在接收到UE的上行流时，触发Start of SDF事件，并将该事件上报给CP；
步骤4：CP在接收到UP2上报的start of SDF事件后，向UP1发送请求上报计费信息的消息，并接收UP1上报的计费信息；UP1的上报信息中包括上报原因(即：触发上报的条件)，这里的上报原因为PDU Session Release。
步骤5：若OCS为该配额下发了指示UP变化的触发条件，则UP1的上报使得该触发条件满足，则CP执行B11的步骤705-707；若OCS没有为该配额下发指示UP变化的触发条件，则CP执行B12的步骤805-807。
本发明B13实施例的方案，通过OCS在向CP下发配额时，根据自身决策或者 运营商配置，随配额一起下发指示UP变化的触发条件，可以增强计费的灵活性，提升OCS的自主权，进而在需要对不同UP上的业务数据流使用执行不同的费率以支持更为灵活和合理的计费时，指示CP上报数据流在UP间的迁移，在OCS无需基于UP执行计费处理时，CP不上报数据流在UP间的迁移，以减少信令。
B2：在建立UP2的PDU session后，若UP1上的业务数据流是部分迁移到UP2，且一个charging key对应的业务数据流会跨UP，即：在一段时间内(一般是UP2发送start of SDF事件后,到UP1发送termination OF SDF事件之前)，UP1和UP2上会同时有同一charging key的业务数据流)，如下表3示意：
Figure PCTCN2018094481-appb-000004
表3
CP可以在迁移后判断一个charging key的数据流是否跨UP，也可以在生成路由策略时通过路由表控制，具体方法可以是：CP根据其为UP1及UP2生成的路由表，以及PCF下发的charging key对应的流模板，判断一个charging key所对应的流模板所覆盖的内容，是否被分割到UP1和UP2的路由表，进而确定一个charging key下的数据流是否跨UP，上述表3的例子中，CK1对应的SF1数据流跨越了UP。计费方面的具体处理方法如下：
B21、CP进行配额的管理，包括对配额的使用和上报进行控制；
对于服务化协议接口的方式(如Restful)，CP和OCS可以直接通过服务化消息进行交互；
对于Diameter协议的接口，一个PDU Session使用一个计费会话，即不因为数据流的迁移而增加新的计费会话，参考附图9，需要说明的是，下述步骤中，不涉及CP和OCS交互的部分，同样适用于服务化协议接口的方式。具体步骤说明如下：
步骤901：CP确定采集计费信息的UP；
由于数据流迁移时UP1和UP2上同时存在有同一charging key的业务数据流，CP需要确定采集计费信息的UP，具体的，CP根据PCF发送并激活的policy确定采集计费信息的UP。这里UP1和UP2即CP确定的计费采集点。CP确定采集计费信息的UP的时机，和CP确定CK数据流跨UP的时机，并没有严格的时序关系。
步骤902：CP处理OCS授予的配额；
这里OCS授予的配额包括OCS新授予的配额(CP按照charging key向OCS申请配额)，或者CP获取的UP1上的未使用的可用配额。
由于多UP是逻辑独立的，所以CP必须为每个UP单独控制配额，包括：配额的下发、使用信息的上报。由于PCF下发的面向不同UP的policy使用相同的charging key，而OCS是按照charging key分配配额，所以CP接收到的OCS分配的配额可能是跨UP配额。为了防止OCS分配的配额跨UP，或者跨UP后还能正常的使用，具体方法如下：
步骤9021.CP不管charging key是否跨UP，均向OCS申请该charging key的配额；
步骤9022.CP接收到OCS分配的配额后，在生成向UP下发的规则时，判断该配额是否是多个UP共享，具体的，CP可以根据该配额对应的charging key对应的数据流是否分布在不同的UP来确定，若该charging key对应的数据流分布在多个UP上，则意味着该配额多个UP共享；
步骤9023.CP若检测到一个配额跨UP，则将该配额分割成小配额，为每个UP均分割一个小配额，然后使用小配额生成向UP下发的规则下发给UP执行。CP记录这些分割后的小配额及与UP的对应关系。
步骤9024.CP接收任一UP(如UP1)在配额用完时或者上报条件满足时上报的计费数据，CP根据所保存的小配额与UP的对应关系，向其他UP发送请求上报该配额的使用信息，等收到所有UP返回该配额的使用信息后，CP可以进行如下处理：
CP将所有UP上报的该配额的使用信息合并在一个消息中，向OCS上报。其中，该消息中的每个UP的使用信息作为独立的容器，对于UP1上报的信息对应的容器，包括所满足的trigger和对应的UP标识，对于其他UP上报的信息对应的容器，包括信息指明该上报是因为其他上报导致的，具体的，可以在容器中携带related trigger，或者Reporting Reason的值指明是连带上报，同时携带对应的UP标识；
上报格式示例：
CCA消息
Rating-Group对应charging key
Used-Service-Unit对应UP1
Reporting-Reason(指明上报原因：满足的trigger)
Tariff-Time-Change
CC-Time
CC-Total-Octets
CC-Input-Octets
CC-Output-Octets
Used-Service-Unit对应UP2
Reporting-Reason(指明上报原因：连带上报)
Tariff-Time-Change
CC-Time
CC-Total-Octets
CC-Input-Octets
CC-Output-Octets
或者，
合并所有UP上报的使用信息，并使用一个容器上报合并的使用信息。如果存在Tariff-Time-Change，则合并时将每个UP的上报信息中的Tariff-Time-Change之前的部分合并，之后的部分合并。
上报消息中还可以携带上报原因，该原因为：某一UP导致的上报。
消息示例：
CCA消息
Rating-Group对应charging key
Used-Service-Unit合并的UP1和UP2的使用信息
Reporting-Reason(指明上报原因：某一UP导致的上报)
Tariff-Time-Change
CC-Time
CC-Total-Octets
CC-Input-Octets
CC-Output-Octets
CP缓存各UP上报的使用信息(该信息将在下次向OCS上报时一起上报给OCS)，将未使用的剩余可用配额汇总，再重新分割成小配额(每个UP分配一个小配额)并下发给UP继续使用。
上述a)和b)可以选择一个实现；或者，
上述a)和b)可以同时实现。如果是同时实现，则CP需要增加一步判断：若满足向OCS上报的条件(上报条件可以是OCS下发的重授权触发条件，或者配额的使用限制条件，如配额过期等)，则执行a)，否则执行b)。
本发明B21实施例的方案，通过CP控制配额在多个UP上的使用，协调了多UP间配额共享使用，同时屏蔽了配额使用的复杂性对OCS的影响，从而提高了OCS的效率。
B22、对于CP和计费***之间采用Diameter协议交互的情况，CP为UP2建立一个新的在线计费会话；参考附图10，
步骤1001：CP确定采集计费信息的UP
如果有多个UP时，CP需要确定采集计费信息的UP，具体的，CP接收PCF激活的policy，根据该policy确定采集计费信息的UP，这里UP1和UP2都是计费信 息采集点。
步骤1002：CP确定会存在该PDU Session的一个charging key对应的业务数据流会跨UP，则为新建立的需要执行在线计费统计的UP向OCS发起建立新的UP2专有在线计费会话。附图仅为实例，需要说明的是CP确定采集计费信息的UP的时机和CP确定CK数据流跨UP的时机，并没有严格的时序关系。
具体的，
CP判断当前的SSC mode，如果是SSC mode 3，推定为可能存在某个charging key对应的业务数据流会跨UP，则为UP2发起建立新的计费会话；
或者，如果是SSC mode 3，且根据分配的路由信息，会出现某特定charging key对应的业务数据流会跨UP1和UP2，则为UP2发起建立新的计费会话。
若CP为PDU Session增加一个BP或UL CL，则在确定需要执行在线计费统计的UP后，同样执行上述判断，若会出现某特定charging key对应的业务数据流会跨UP1和UP2，则为UP2或要执行在线计费功能的BP或UL CL发起建立新的计费会话。
CP保存UP和该计费会话的对应关系。
此时，CP在新的计费会话中，为UP2单独申请配额、管理配额使用、上报配额使用信息。
步骤B1003：CP确定UP1上PDU Session拆除时或者UP1上无数据流时，向OCS发起拆除UP1对应的计费会话。
拆除会话时或之前，向OCS上报UP1上收集的配额使用信息。
进一步的，若CP删除某一个UP上的PDU Session，则步骤如附图11所示，如下：
步骤1101：CP确定删除UP1上的PDU Session；
步骤1102：CP向UP1下发信息，删除PDU Session；
步骤1103：CP接收UP1上报的计费信息；
步骤1104：CP根据所保存的UP1和其对应计费会话的对应关系，向OCS发起该计费会话的结束请求，同时携带UP1上报的使用信息；
其他的UP的在线计费会话不受UP1上PDU Session结束的影响，也不受UP1对应在线计费会话结束的影响。
本发明B22实施例的方案，通过CP分别为每个UP建立独立的计费会话，降低了CP和OCS的实现复杂度，CP无需协调一个配额在多个UP间的使用。
方案C:本发明实施例还提供了一种计费方法，该方法从静态的角度描述了CP同时与其对应的两个UP以及计费***交互，完成计费信息的收集和上报，以及配额申请和下发的过程。
所述方法包括：控制面功能实体CP从第一用户面功能实体UP和第二UP上获取所述CP对应的一个PDU session上的数据流的计费信息，所述第一UP和第二UP为所述CP对应的UP；所述CP将计费***下发的配额分割成多个子配额，并分 别下发给所述第一UP和第二UP。
一般来说，所述第一UP和第二UP上存在使用相同charging key的数据流；所述CP同时从所述第一UP和第二UP上获取所述数据流的计费信息；对于Diameter协议接口的情形，所述CP通过与计费***间的一个计费会话对第一UP和第二UP进行计费。
所述CP将计费***下发的配额分割成多个子配额并下发给UP，包括：所述CP将计费***为所述charging key下发的配额分割成多个子配额并分别下发给所述第一UP和第二UP。
所述方法进一步包括：所述CP在任一个UP上所述配额用完并上报所述配额对应的计费信息后，获取其他UP上统计的所述配额对应的计费信息；所述CP合并所述配额对应的计费信息，并上报给计费***。
所述方法进一步包括：所述CP在任一个UP上所述配额用完并上报所述配额对应的计费信息后，获取其他UP上统计的所述配额对应的计费信息；所述CP缓存所有UP上报的所述配额对应的计费信息，确定所述配额的剩余可用量，重新分配所述配额的剩余可用量，并向第一UP和第二UP下发所述重新分配的配额；所述CP在所述配额用完或者所述配额的剩余可用量满足上报阈值时，合并所述缓存的所述配额对应的计费信息，并向计费***上报所述合并的计费信息。
需要说明的是，前述实施例A,B所涉及的各步骤的相关内容，特别是实施例B21的情形，根据其相关性可以援引到方案C中，在此不再赘述,基于该实施例描述的技术方案，CP可同时对其对应的两个UP上产生的数据流进行计费。
计费***包括在线计费***OCS和离线计费***OFCS。其中离线计费仅仅涉及计费信息采集和上报(包括上报触发条件)，而在线计费除了和离线计费类似的计费信息采集和上报外，还包括配额授予、配额使用管理(包括配额使用条件监控)、动态Trigger(OCS激活的触发条件)、配额使用信息上报。本申请中如果没有特殊说明，计费上报适用于在线计费中的上报和离线计费中的上报，而计费配额申请、配额使用管理、动态Trigger仅仅适用于在线计费。离线的计费有几种方法，包括CTF实时上报计费信息、CTF生成CDR后上报CDR、CTF直接生成CDR文件后上报CDR文件。在这几种方式下计费信息的采集粒度、用于触发实时上报或写CDR的触发条件等都是相同的，所以本申请实施例中仅以CTF实时上报计费信息为例进行说明。
对于前述实施例中，情况A的情形，即CP先拆除与UE与UP1的连接,再建立UE和UP2的连接，离线计费方法简要描述如下，相关的细节可以类似参考前述实施例，在此不再赘述：
步骤1：CP确定要改变数据流的UP(执行计费的UP发生变化)，CP将首先中断UE与UP1的PDU Session，同时建立UE与UP2的PDU Session；
步骤2：CP发起中断UP1上的PDU Session，并接收UP1上报的计费信息；
UP1上的PDU Session释放流程触发UP1向CP上报计费信息。UP1的上报信息中包括上报原因(即：触发上报的条件)，这里的上报原因为PDU Session Release。
步骤3(计费***感知UP切换)：CP向CDF/CGF/BS上报计费信息，上报原 因“UP切换”；
步骤3’(计费***不感知UP切换)：CP缓存UP1的使用信息，并等待UP2上报使用信息，在收到UP2的使用信息后，CP将UP2上报的使用信息和所缓存的UP1上报的使用信息进行合并，将合并后的信息向CDF/CGF/BS上报。
对于情况B:CP建立UE和UP2的连接,但并未拆除和UP1的连接；离线计费的方法简要描述如下：
步骤1：CP确定要改变数据流的UP(执行计费的UP发生变化)，CP将首先建立UE与UP2的PDU Session，在数据流切换到UP2后，中断UE与UP1的PDU Session；
步骤2：CP发起建立UP2上的PDU Session；
步骤3：UE将发送的上行数据流切换到UP2的PDU Session上，UP2在接收到上行流时，触发start of SDF事件，并将该事件上报给CP；
步骤4：CP在接收到UP2上报的start of SDF事件后，向UP1发送请求上报计费信息的消息，并接收UP1上报的计费信息；
UP1的上报信息中包括上报原因(即：触发上报的条件)，这里的上报原因为PDU Session Release。
步骤5(计费***感知UP切换)：CP向CDF/CGF/BS上报计费信息，上报原因“UP切换”；
步骤5’(计费***不感知UP切换)：CP缓存UP1的使用信息，并等待UP2上报使用信息，在收到UP2的使用信息后，CP将UD2上报的使用信息和所缓存的UP1上报的使用信息进行合并，将合并后的信息向CDF/CGF/BS上报。
本发明实施例的离线方案，也实现了在较为复杂的控制面和用户面分离场景下，例如，一个PDU Session的用户面发生切换时，或者一个PDU Session存在多个用户面时，用户的业务数据流在用户面之间迁移情况下的计费，使得离线计费可以支撑业务端到端的更低时延、且提高了网络的效率的优化部署，实现优化部署下数据业务的精准计费，提高网络效率和用户体验。
以上主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，上述CP,UP或者OCS/OFCS，为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对CP和OCS/OFCS进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
比如，在采用对应各个功能划分各个功能模块的情况下，图12示出了前述实施例中所涉及CP作为计费设备1200的一种可能的结构示意图。
该计费设备1200包括判断模块1202，获取模块1206和处理模块1208。判断模块1202，用于确定用户设备UE在第一数据会话上传输的数据流需要迁移到第二数据会话上，所述第一数据会话是UE和第一用户面功能实体UP间的数据会话；所述第二数据会话是所述UE和第二UP间的数据会话，所述第一UP和第二UP是所述计费设备对应的UP，所述第一数据会话和第二数据会话对应同一个PDU session。获取模块1206，用于获取第一UP统计的所述数据流迁移前的计费信息。处理模块1208用于用于确定需要向第二UP下发的所述数据流迁移后使用的配额，并下发给第二UP。
计费信息上报接口可以是Diameter协议接口或者服务化接口。服务化接口的方式下，CP和计费***间不建立计费会话，而是直接通过服务化消息进行交互，服务化消息(如：Restful)是无状态的消息，每个消息携带完整的信息。而Diameter协议接口的情况下，CP和计费***之间需要建立计费会话。
可选的，还包括会话模块1204，用于建立与计费***之间的第一计费会话，并通过所述第一计费会话对所述第一UP上的所述数据流计费；所述判断模块1202还用于确定所述数据流从第一UP迁移到第二UP后，所述第一UP上无使用所述数据流对应的charging key的其他数据流，所述会话模块1204进一步用于为第二UP上所述数据流使用所述第一计费会话进行计费。
可选的，所述获取模块1206用于接收第一UP上报的所述数据流迁移前的计费信息，并通过所述会话模块1204向计费***上报所述计费信息，为第二UP申请用于所述数据流的配额；所述会话模块1204用于接收所述计费***下发的所述配额；所述处理模块1208根据所述计费***下发的配额，生成向第二UP下发的配额。
可选的，所述处理模块1208用于根据获取的第一UP统计的所述数据流迁移前的计费信息，确定剩余的可用配额，并根据所述剩余的可用配额生成向第二UP下发的配额。
可选的，所述获取模块1206用于接收第一数据会话中断触发第一UP上报的计费信息。
可选的，所述获取模块1206用于获取第二UP上报的所述数据流对应的数据流开始事件后，第一UP上统计的所述数据流迁移前的计费信息。
可选的，所述判断模块1202用于确定所述数据流从第一UP迁移到第二UP后，所述第一UP上存在使用所述数据流对应的charging key的其他数据流；所述获取模块1206进一步用于同时从所述第一UP和第二UP上获取所述数据流的计费信息。
可选的，发所述判断模块1202进一步用于确定所述数据流从第一UP迁移到第二UP后，所述第一UP上存在使用所述数据流对应的charging key的其他数据流；所述会话模块1204进一步用于为第二UP上传输所述数据流的第二数据会话建立和计费***的第二计费会话，通过第二计费会话向计费***申请配额，所述处理模块1208进一步用于将申请的配额下发给第二UP。
需要说明的是，上述所有方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
以采用集成的方式划分各个功能模块的情况下，图13示出了上述实施例中所涉及的计费***1300的一种可能的结构示意图，该计费***1300包括：下发模块1302和接收模块1304，
所述下发模块1302，用于向控制面功能实体CP下发指示信息，所述指示信息用于指示CP在所述CP对应的用户面功能实体UP从第一UP切换为第二UP后，向所述OCS上报所述第一UP切换前的计费信息；所述接收模块1304用于接收所述CP上报的所述第一UP统计的切换前的计费信息。
可选的，所述计费***是在线计费***OCS,所述指示信息随所述OCS下发给所述CP的配额一起下发。
可选的，所述OCS接收所述CP上报的计费信息后，向所述CP下发新的配额。
可选的，所述OCS接收所述CP上报的计费信息后，向所述CP下发给第二UP，或同时给第一UP和第二UP的配额。
需要说明的是，上述所有方法实施例涉及的计费***执行的各步骤的所有相关内容均可以援引到上述对应功能模块的功能描述，在此不再赘述。
其中，图12和图13实施例中的“模块”可以为专用集成电路(Application Specific Integrated Circuit，ASIC)、电子线路、执行一个或多个软件或固件程序的处理器和存储器、组合逻辑电路和其他提供上述功能的组件。可选的，上述计费设备和计费***通过计算机设备的形式来实现，上述接收模块、发送模块可以通过计算机设备的处理器、存储器和通信接口来实现，上述处理模块可以通过计算机设备的处理器和存储器来实现。
应注意，尽管图3所示的计算机设备300仅仅示出了处理器302、存储器304、通信接口306和总线308，但是在具体实现过程中，本领域的技术人员应当明白，上述计费设备和计费***还包含实现正常运行所必须的其他器件。同时，根据具体需要，本领域的技术人员应当明白，上述计费设备和计费***还可包含实现其他附加功能的硬件器件。此外，本领域的技术人员应当明白，上述计费设备和计费***也可仅仅包含实现本申请实施例所必须的器件，而不必包含图3中所示的全部器件。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述 的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (30)

  1. 一种计费方法，其特征在于，所述方法包括：
    控制面功能实体CP确定用户设备UE在第一数据会话上传输的数据流需要迁移到第二数据会话上，所述第一数据会话是UE和第一用户面功能实体UP间的数据会话，所述第二数据会话是所述UE和第二UP间的数据会话，所述第一UP和第二UP为所述CP对应的UP，所述第一数据会话和第二数据会话对应同一个PDU session；
    所述CP获取第一UP统计的所述数据流迁移前的计费信息；
    所述CP确定需要向第二UP下发的所述数据流迁移后使用的配额，并下发给第二UP。
  2. 如权利要求1所述方法，其特征在于，所述方法进一步包括：
    所述CP通过与计费***之间的第一计费会话对所述第一UP上的所述数据流计费；
    所述CP确定所述数据流从第一UP迁移到第二UP后，所述第一UP上无使用所述数据流对应的charging key的其他数据流；
    所述CP为第二UP上所述数据流使用所述第一计费会话进行计费。
  3. 如权利要求1或2所述方法，其特征在于，所述CP获取第一UP统计的所述数据流迁移前的计费信息，确定需要向第二UP下发的配额并下发给第二UP，包括：
    所述CP接收第一UP上报的所述数据流迁移前的计费信息，向计费***上报所述计费信息，并为第二UP申请用于所述数据流的配额；
    所述CP接收所述计费***下发的所述配额；
    所述CP根据所述计费***下发的配额，生成向第二UP下发的配额。
  4. 如权利要求1或2所述方法，其特征在于，所述CP获取第一UP的计费信息，确定需要向所述第二UP下发的配额，包括：
    所述CP根据获取的第一UP统计的所述数据流迁移前的计费信息，确定剩余的可用配额，并根据所述剩余的可用配额生成向第二UP下发的配额。
  5. 如权利要求要1，2或4任一项所述的方法，其特征在于，所述方法还包括：
    所述CP缓存第一UP上报的所述数据流迁移前的计费信息；
    所述CP接收第二UP上报的所述数据流迁移后的计费信息；
    所述CP合并所述第二UP上报的计费信息和所缓存的第一UP上报的计费信息，将合并后的计费信息上报给计费***。
  6. 如权利要求1，2或4任一项所述的方法，其特征在于，所述方法还包括：
    所述CP将第一UP上报的所述数据流迁移前的计费信息发送给第二UP，使得第二UP基于所述第一UP上报的所述数据流迁移前的计费信息，继续统计所述数据流迁移后的计费信息；
    所述CP接收第二UP在满足上报条件时上报的所述数据流迁移前和迁移后的计费信息，并上报给计费***。
  7. 如权利要求1至6任一项所述的方法，其特征在于：
    所述CP根据所述计费***下发的指示，确定所述PDU session上的数据流从第一UP迁移到第二UP后，向计费***上报所述数据流迁移前的计费信息。
  8. 如权利要求1至7任一项所述的方法，其特征在于，所述CP获取第一UP统计的所述数据流迁移前的计费信息，包括：
    所述CP接收第一数据会话中断触发第一UP上报的计费信息。
  9. 如权利要求1～7任一项所述方法，其特征在于，所述CP获取第一UP统计的所述数据流迁移前的计费信息，包括：
    所述CP检测到第二UP上报的所述数据流对应的数据流开始事件后，获取第一UP上统计的所述数据流迁移前的计费信息。
  10. 如权利要求1所述方法，其特征在于，所述方法进一步包括：
    所述CP通过与计费***之间的第一计费会话对所述第一UP上的所述数据流计费；
    所述CP确定所述数据流从第一UP迁移到第二UP后，所述第一UP上存在使用所述数据流对应的charging key的其他数据流；
    所述CP为第二UP上所述数据流使用所述第一计费会话；
    所述CP同时从所述第一UP和第二UP上获取所述数据流的计费信息。
  11. 如权利要求1或者10所述方法，其特征在于，所述CP进一步确定需要向第一UP下发的配额，所述方法包括：
    所述CP将计费***为所述charging key下发的配额分割成多个子配额并分别下发给所述第一UP和第二UP。
  12. 如权利要求11所述的方法，其特征在于，所述方法进一步包括：
    所述CP在任一个UP上所述配额用完并上报所述配额对应的计费信息后，获取其他UP上统计的所述配额对应的计费信息；
    所述CP合并所述配额对应的计费信息，并上报给计费***。
  13. 如权利要求11所述方法，其特征在于，所述方法进一步包括：
    所述CP在任一个UP上所述配额用完并上报所述配额对应的计费信息后，获取其他UP上统计的所述配额对应的计费信息；
    所述CP缓存所有UP上报的所述配额对应的计费信息，确定所述配额的剩余可用量，重新分配所述配额的剩余可用量，并向第一UP和第二UP下发所述重新分配的配额；
    所述CP在所述配额用完或者所述配额的剩余可用量满足上报阈值时，合并所述缓存的所述配额对应的计费信息，并向计费***上报所述合并的计费信息。
  14. 如权利要求1所述方法，其特征在于，所述方法进一步包括：
    所述CP通过与计费***之间的第一计费会话对所述第一UP上的所述数据流计费；
    所述CP确定所述数据流从第一UP迁移到第二UP后，所述第一UP上存在使用所述数据流对应的charging key的其他数据流；
    所述CP为第二UP上传输所述数据流的第二数据会话使用第二计费会话，通过第二计费会话向计费***申请配额，并将申请的配额下发给第二UP；所述第二计费会话是所述CP与计费***为所述第二UP上的第二数据会话建立的计费会话。
  15. 一种计费方法，其特征在于，包括以下步骤：
    在线计费***OCS向控制面功能实体CP下发指示信息，所述指示信息用于指 示CP在所述CP对应的用户面功能实体UP从第一UP切换为第二UP后，向所述OCS上报所述第一UP切换前的计费信息；
    所述OCS接收所述CP上报的所述第一UP统计的切换前的计费信息。
  16. 如权利要求15中所述的计费方法，其特征在于，所述指示信息随所述OCS下发给所述CP的配额一起下发。
  17. 如权利要求15或16中所述的计费方法，其特征在于，所述OCS接收所述CP上报的计费信息后，向所述CP下发给第二UP，或同时给第一UP和第二UP的配额。
  18. 一种计费设备，其特征在于，包括判断模块，获取模块和处理模块：
    所述判断模块，用于确定用户设备UE在第一数据会话上传输的数据流需要迁移到第二数据会话上，所述第一数据会话是UE和第一用户面功能实体UP间的数据会话；所述第二数据会话是所述UE和第二UP间的数据会话，所述第一UP和第二UP是所述计费设备对应的UP，所述第一数据会话和第二数据会话对应同一个PDU session；
    所述获取模块，用于获取第一UP统计的所述数据流迁移前的计费信息；
    所述处理模块，用于确定需要向第二UP下发的所述数据流迁移后使用的配额，并下发给第二UP。
  19. 如权利要求18所述的计费设备，其特征在于，还包括会话模块，用于与计费***建立第一计费会话，并通过所述第一计费会话对所述第一UP上的所述数据流计费；所述判断模块还用于确定所述数据流从第一UP迁移到第二UP后，所述第一UP上无使用所述数据流对应的charging key的其他数据流，所述会话模块进一步用于为第二UP上所述数据流使用所述第一计费会话进行计费。
  20. 如权利要求18或19所述计费设备，其特征在于，
    所述获取模块用于接收第一UP上报的所述数据流迁移前的计费信息，并通过所述会话模块向计费***上报所述计费信息，为第二UP申请用于所述数据流的配额；所述会话模块用于接收所述计费***下发的所述配额；所述处理模块根据所述计费***下发的配额，生成向第二UP下发的配额。
  21. 如权利要求18或19所述计费设备，其特征在于，
    所述处理模块用于根据获取的第一UP统计的所述数据流迁移前的计费信息，确定剩余的可用配额，并根据所述剩余的可用配额生成向第二UP下发的配额。
  22. 如权利要求18所述的计费设备，其特征在于，所述获取模块用于接收第一数据会话中断触发第一UP上报的计费信息。
  23. 如权利要求18所述计费设备，其特征在于，所述获取模块用于获取第二UP上报的所述数据流对应的数据流开始事件后，第一UP上统计的所述数据流迁移前的计费信息。
  24. 如权利要求18所述的计费设备，其特征在于，还包括会话模块，所述会话模块用于与计费***建立第一计费会话，并通过所述第一计费会话对所述第一UP上的所述数据流计费；
    所述判断模块用于确定所述数据流从第一UP迁移到第二UP后，所述第一UP上存在使用所述数据流对应的charging key的其他数据流；
    所述获取模块进一步用于同时从所述第一UP和第二UP上获取所述数据流的计费信息。
  25. 如权利要求18所述计费设备，其特征在于，还包括会话模块，用于与计费***建立第一计费会话，并通过所述第一计费会话对所述第一UP上的所述数据流计费；
    所述判断模块进一步用于确定所述数据流从第一UP迁移到第二UP后，所述第一UP上存在使用所述数据流对应的charging key的其他数据流；
    所述会话模块进一步用于为第二UP上传输所述数据流的第二数据会话建立和计费***的第二计费会话，通过第二计费会话向计费***申请配额；
    所述处理模块进一步用于并将申请的配额下发给第二UP。
  26. 一种计费***，其特征在于，包括下发模块和接收模块，
    所述下发模块，用于向控制面功能实体CP下发指示信息，所述指示信息用于指示CP在所述CP对应的用户面功能实体UP从第一UP切换为第二UP后，向所述OCS上报所述第一UP切换前的计费信息；
    所述接收模块，用于接收所述CP上报的所述第一UP统计的切换前的计费信息。
  27. 一种计算设备，包括：处理器、存储器、总线和通信接口；所述存储器用于存储计算设备执行指令，所述处理器与所述存储器通过所述总线连接，当所述计算设备运行时，所述处理器执行所述存储器存储的所述计算设备执行指令，以使所述计算设备执行权利要求1至14任意一项所述的方法。
  28. 一种计算设备，包括：处理器、存储器、总线和通信接口；所述存储器用于存储计算设备执行指令，所述处理器与所述存储器通过所述总线连接，当所述计算设备运行时，所述处理器执行所述存储器存储的所述计算设备执行指令，以使所述计算设备执行权利要求15至17中任意一项所述的方法。
  29. 一种网络***，其特征在于，包括权利要求18至25任意一项所述的计费设备，以及权利要求26所述的计费***。
  30. 一种计费方法，其特征在于，所述方法包括：
    控制面功能实体CP从第一用户面功能实体UP和第二UP上获取所述CP对应的一个PDU session上的数据流的计费信息，所述第一UP和第二UP为所述CP对应的UP；所述第一UP和第二UP上存在使用相同charging key的数据流；
    所述CP将计费***下发的配额分割成多个子配额，并分别下发给所述第一UP和第二UP。
PCT/CN2018/094481 2017-08-03 2018-07-04 一种计费方法及设备 WO2019024645A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP21154943.1A EP3883180B1 (en) 2017-08-03 2018-07-04 Charging method, apparatus, computer program and system.
EP18841358.7A EP3588846B1 (en) 2017-08-03 2018-07-04 Charging method and device
US16/586,129 US10674330B2 (en) 2017-08-03 2019-09-27 Charging method and device
US16/832,985 US10945104B2 (en) 2017-08-03 2020-03-27 Charging method and device
US17/162,505 US11671802B2 (en) 2017-08-03 2021-01-29 Charging method and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710657128.9 2017-08-03
CN201710657128.9A CN109391475B (zh) 2017-08-03 2017-08-03 一种计费方法及设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/586,129 Continuation US10674330B2 (en) 2017-08-03 2019-09-27 Charging method and device

Publications (1)

Publication Number Publication Date
WO2019024645A1 true WO2019024645A1 (zh) 2019-02-07

Family

ID=65233090

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/094481 WO2019024645A1 (zh) 2017-08-03 2018-07-04 一种计费方法及设备

Country Status (5)

Country Link
US (3) US10674330B2 (zh)
EP (2) EP3883180B1 (zh)
CN (3) CN109391475B (zh)
ES (1) ES2965185T3 (zh)
WO (1) WO2019024645A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110505196A (zh) * 2019-07-02 2019-11-26 中国联合网络通信集团有限公司 物联网卡异常检测方法及装置

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3769469A1 (en) * 2018-03-20 2021-01-27 Nokia Solutions and Networks Oy Quota management in a session management function (smf) for online charging
WO2019182573A1 (en) * 2018-03-20 2019-09-26 Nokia Solutions And Networks Oy Quota management in mobile edge computing (mec)
CN111211912B (zh) 2018-04-28 2020-11-10 华为技术有限公司 计费的方法和装置
WO2019216884A1 (en) * 2018-05-08 2019-11-14 Nokia Solutions And Networks Oy Charging policies in network entities that have separate control plane and user plane
CN113365238B (zh) 2019-03-29 2022-03-29 华为技术有限公司 一种计费方法和装置
CN111836221A (zh) * 2019-04-22 2020-10-27 华为技术有限公司 计费管理方法、设备及***
CN114205765A (zh) * 2021-12-29 2022-03-18 浪潮通信信息***有限公司 一种解决ocs***多会话预留异常扣费的方法及***
JP7242953B1 (ja) 2022-09-27 2023-03-20 Kddi株式会社 情報処理装置及び情報処理方法
JP7242954B1 (ja) 2022-09-27 2023-03-20 Kddi株式会社 情報処理システム及び情報処理方法
CN116074135B (zh) * 2023-01-31 2024-05-03 中国联合网络通信集团有限公司 一种配额配置方法及装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101582777A (zh) * 2008-05-16 2009-11-18 华为技术有限公司 策略和计费控制规则的获取方法及装置
US9531554B1 (en) * 2014-01-31 2016-12-27 Sprint Communications Company L.P. Default quota implementation for wireless devices

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120184244A1 (en) * 2009-09-30 2012-07-19 Yigang Cai Online charging in ims networks for sessions handed over between different operator networks
CN102264056B (zh) * 2010-05-28 2014-03-05 华为技术有限公司 策略控制方法、***和相关装置
KR20130051820A (ko) * 2011-11-10 2013-05-21 삼성전자주식회사 모바일 환경에서의 소프트웨어 마이그레이션 장치 및 방법
AU2013374126B2 (en) * 2013-01-15 2015-12-03 Huawei Technologies Co., Ltd. Charging method and device
EP3001601B1 (en) 2013-06-28 2019-01-16 Huawei Technologies Co., Ltd. Credit control method, policy and charging enforcement function entity, and online charging system
MX361969B (es) * 2014-04-25 2018-12-19 Redknee Inc Método, sistema y aparato para determinación de cuotas adaptivo para recursos compartidos.
WO2017078779A1 (en) * 2015-11-02 2017-05-11 Intel Corporation Split of control plane and user plane for 5g radio access networks
CN106851856B (zh) * 2016-12-23 2019-04-09 电信科学技术研究院有限公司 一种基于移动中继的无线通信建立方法及网络设备

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101582777A (zh) * 2008-05-16 2009-11-18 华为技术有限公司 策略和计费控制规则的获取方法及装置
US9531554B1 (en) * 2014-01-31 2016-12-27 Sprint Communications Company L.P. Default quota implementation for wireless devices

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Telecommunication Management; Charging Management; Study on Charging Aspects of 5G System Architecture Phase 1 (Release 15", 3GPP TR 32.899, V0.2.0., 15 June 2017 (2017-06-15), XP055638559 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110505196A (zh) * 2019-07-02 2019-11-26 中国联合网络通信集团有限公司 物联网卡异常检测方法及装置

Also Published As

Publication number Publication date
US10674330B2 (en) 2020-06-02
CN109391475B (zh) 2021-02-09
US10945104B2 (en) 2021-03-09
US20200228942A1 (en) 2020-07-16
EP3883180A1 (en) 2021-09-22
EP3588846A1 (en) 2020-01-01
US20200045514A1 (en) 2020-02-06
EP3588846B1 (en) 2021-06-30
CN110519069B (zh) 2020-07-14
US11671802B2 (en) 2023-06-06
US20210152989A1 (en) 2021-05-20
CN110519069A (zh) 2019-11-29
EP3883180B1 (en) 2023-10-25
ES2965185T3 (es) 2024-04-11
CN112865985B (zh) 2022-09-16
EP3588846A4 (en) 2020-04-15
CN109391475A (zh) 2019-02-26
CN112865985A (zh) 2021-05-28

Similar Documents

Publication Publication Date Title
WO2019024645A1 (zh) 一种计费方法及设备
US10715680B2 (en) Charging method and device involved in a protocol data unit (PDU) session
CN110971419B (zh) 一种计费会话管理方法、装置
US9538017B2 (en) Charging method and device
US10609225B2 (en) Charging method, apparatus, and system
EP3657827B1 (en) Billing method and device for mobile communication system and storage medium

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: 18841358

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2018841358

Country of ref document: EP

Effective date: 20190924

NENP Non-entry into the national phase

Ref country code: DE