CN110381455B - Flow monitoring processing method and related device and system - Google Patents

Flow monitoring processing method and related device and system Download PDF

Info

Publication number
CN110381455B
CN110381455B CN201910631444.8A CN201910631444A CN110381455B CN 110381455 B CN110381455 B CN 110381455B CN 201910631444 A CN201910631444 A CN 201910631444A CN 110381455 B CN110381455 B CN 110381455B
Authority
CN
China
Prior art keywords
traffic
network element
application
value
flow
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
CN201910631444.8A
Other languages
Chinese (zh)
Other versions
CN110381455A (en
Inventor
荣传湘
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201910631444.8A priority Critical patent/CN110381455B/en
Publication of CN110381455A publication Critical patent/CN110381455A/en
Application granted granted Critical
Publication of CN110381455B publication Critical patent/CN110381455B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24Accounting or billing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/08Testing, supervising or monitoring using real traffic
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/0215Traffic management, e.g. flow control or congestion control based on user or device properties, e.g. MTC-capable devices
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/0231Traffic management, e.g. flow control or congestion control based on communication conditions
    • H04W28/0236Traffic management, e.g. flow control or congestion control based on communication conditions radio quality, e.g. interference, losses or delay
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/10Flow control between communication endpoints

Landscapes

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

Abstract

The embodiment of the application discloses a flow monitoring processing method and a related device and system. A traffic monitoring processing method comprises the following steps: the B2B charging network element receives a first traffic application request message from the B2C charging network element, the B2B charging network element determines a first authorized traffic value corresponding to an end user identifier based on the first application traffic value and a current reservable traffic value of a sponsor traffic account corresponding to a service identifier, and sends a first traffic application response message for responding to the first traffic application request message to the B2C charging network element. The technical scheme of the embodiment of the application is beneficial to improving the real-time performance of flow monitoring charging and further beneficial to improving the use experience of users on the sponsored flow.

Description

Flow monitoring processing method and related device and system
Technical Field
The present application relates to the field of communications computer technologies, and in particular, to a traffic monitoring processing method, and a related apparatus and system.
Background
With the development of technology, especially Internet Protocol (IP) technology and information technology, the convergence between the industries of telecommunication, information technology, media, consumer electronics, etc., the telecommunication industry is facing a great revolution. The next few years are a key period in the transition of the telecommunications industry, and digital telecommunications services have begun to gradually replace traditional telecommunications services. The business model of portable cooperation between telecom operators and some partners will become the mainstream direction of the future telecom market development. Partners of a telecommunications carrier may be content providers, service providers, application providers or other organizational enterprises, etc.
Some partners may offer traffic sponsorship to users, and such partners may refer to sponsors, such as Tencent, to offer traffic sponsorship to a micro-credited user. For the flow resources wholesale from the operators of the partners, the charging processing is generally performed through a special B2B (Business to Business) charging system, however, the traditional B2B charging system basically settles the billing rate offline, and based on the offline settlement pricing capability, it is generally difficult to support the real-time experience in the flow management activities of the telecom operators, and finally the flow use experience of the end users is affected.
Disclosure of Invention
The embodiment of the application provides a traffic monitoring processing method and a related device and system.
A first aspect of an embodiment of the present invention provides a traffic monitoring processing method, including:
an enterprise-to-enterprise (B2B) charging network element receives a first traffic application request message from an enterprise-to-user (B2C) charging network element, wherein the first traffic application request message carries a service identifier and an end user identifier; and the B2B charging network element determines a first authorized flow value corresponding to the end user identifier based on the first application flow value and the current reservable flow value of the sponsor traffic account corresponding to the service identifier, and subtracts the first authorized flow value from the current reservable flow value of the sponsor traffic account to obtain an updated reservable flow value of the sponsor traffic account. The B2B charging network element sends, to the B2C charging network element, a first traffic application response message used for responding to the first traffic application request message, where the first traffic application response message carries the first authorized traffic value, and the first traffic application response message indicates that the B2C charging network element performs charging-free processing on the service traffic corresponding to the service identifier, consumed by the user terminal corresponding to the terminal user identifier within the first authorized traffic value range.
The B2C Charging network element is a network element mainly Charging for an end user, and the B2C Charging network element is, for example, an Online Charging System (OCS) network element or a converged Charging System (CBS) network element.
The B2B charging network element is a network element mainly charging for enterprise users (such as traffic sponsors, referred to as sponsors). The B2B charging network element is, for example, a B2B Billing system network element.
A traffic sponsor (or sponsor for short) may be a partner of a telecommunications operator, such as an Tencent, Google or Baidu, for example. The service represented by the service identity may be a traffic-sponsored service, which may be, for example, a WeChat or Tencent video service.
Wherein the first application traffic value may be carried in the first traffic application request message. Or the first application flow value is a default application flow value (the default application flow value may be, for example, 5M or 15M or other value once). Or, the first application flow value is a preset application flow value corresponding to the service identifier or the terminal user identifier, for example, the service identifiers that are different may respectively correspond to different preset application flow values, for example, the corresponding preset application flow value of the WeChat is 5M, and the corresponding preset application flow value of the Tencent video is 10M).
For example, assuming that the first authorized flow value is 100M, the B2C charging network element performs charging-free processing on the service flow corresponding to the service identifier consumed by the user terminal corresponding to the terminal user identifier within a range of 100M.
It can be seen that, in the foregoing example scheme, since the B2C charging network element applies for the traffic to the B2B charging network element first, after applying for the authorized traffic (i.e., the sponsored traffic) from the B2B charging network element, the B2C charging network element may perform the charging-free processing on the traffic consumed by the user terminal corresponding to the end user identifier within the current authorized traffic range, based on such a mechanism, the end user may relatively learn in real time whether the currently used traffic can enjoy free, which is beneficial to improving the user experience. And the mechanism used after the flow is applied is favorable for reducing the complexity of the later-stage call ticket expense processing.
In some possible embodiments of the present invention, the determining a first authorized traffic value corresponding to the end user identifier based on the first application traffic value and the current reservable traffic value of the sponsor traffic account may include: judging whether a first application flow value exceeds a current reservable flow value of the sponsor flow account, wherein the reservable flow value of the flow account is used as a first authorized flow value corresponding to the terminal user identification under the condition that the first application flow value exceeds the current reservable flow value of the flow account; or taking the first application flow value as a first authorized flow value corresponding to the end user identification under the condition that the first application flow value does not exceed the current reservable flow value of the sponsor flow account.
In some possible embodiments of the present invention, before determining, by the B2B charging network element, a first authorized traffic value corresponding to the end user identifier based on the first application traffic value and the current reservable traffic value of the sponsor traffic account corresponding to the service identifier, the method may further include: and the B2B charging network element determines that the service represented by the service identification is the traffic sponsoring service of the sponsor.
In some possible embodiments of the present invention, before sending the first traffic application request message, the B2C charging network element may further include: the B2C charging network element receives a traffic monitoring trigger message from a service gateway, where the traffic monitoring trigger message carries the service identifier and the end user identifier, the traffic monitoring trigger message is sent by the service gateway after monitoring a service initiation message carrying the end user identifier and the service identifier, and the traffic monitoring trigger message is used to trigger the B2C charging network element to send the first traffic application request message.
That is, the B2C charging network element may be triggered by a service gateway (e.g., SGW, GGSN, or PGW) or the like for traffic monitoring, for example, when an end user initiates a certain traffic-sponsored service through a user terminal, the service gateway may monitor a corresponding service initiation message, and after monitoring the corresponding service initiation message, the service gateway may trigger traffic monitoring by sending a traffic monitoring trigger message to the B2C charging network element. The traffic monitoring trigger message may be, for example, a DCC (diameter credit control) protocol message or other protocol message.
The traffic application request message (e.g., the first traffic application request message or the second traffic application request message) may be a CCR (credit control request) message or other types of messages.
The traffic application response message (e.g., the first traffic application response message or the second traffic application response message) is a CCA (credit control response) message or other types of messages.
In some possible embodiments of the present invention, after the sending, by the B2B charging network element, the first traffic application response message for responding to the first traffic application request message to the B2C charging network element, the method may further include: the B2B charging network element receives a second traffic application request message from the B2C charging network element, where the second traffic application request message carries the service identifier and the end user identifier, and the second traffic application request message is sent by the B2C charging network element after the user terminal corresponding to the end user identifier consumes the first authorized traffic value (the traffic sponsorship service represented by the service identifier consumes the first authorized traffic value).
The B2B charging network element determines a second authorized flow value corresponding to the end user identifier based on a second application flow value and a current reservable flow value of the sponsor traffic account, and the B2B charging network element subtracts the second authorized flow value from the current reservable flow value of the sponsor traffic account to obtain an updated reservable flow value of the sponsor traffic account, where the first application flow value is carried in the first traffic application request message, or the first application flow value is a preset application flow value corresponding to the service identifier or the end user identifier, or the first application flow value is a default application flow value;
and the B2B charging network element sends, to the B2C charging network element, a second traffic application response message used for responding to the second traffic application request message, where the second traffic application response message carries the second authorized traffic value, and where the second traffic application response message indicates that the B2C charging network element performs charging-free processing on the service traffic corresponding to the service identifier, which is consumed by the user terminal corresponding to the end user identifier within the second authorized traffic value range.
That is, each time after the authorized traffic is exhausted by the traffic sponsoring service represented by the end user through the service identifier, the B2C charging network element may continue to apply for the sponsoring traffic from the B2B charging network element until the current reservable traffic value of the sponsor traffic account is exhausted. End users of the traffic-sponsored service represented by the service identity may share the current reservable traffic value of the sponsor traffic account.
A second aspect of the present invention provides a B2B charging network element, including:
a receiving unit, configured to receive a first traffic application request message carrying a service identifier and an end user identifier from a B2C charging network element.
An authorization unit, configured to determine a first authorized flow value corresponding to the end user identifier based on a first application flow value and a current reservable flow value of a sponsor flow account corresponding to the service identifier, and subtract the first authorized flow value from the current reservable flow value of the sponsor flow account to obtain an updated reservable flow value of the sponsor flow account; the first application flow value is carried in the first flow application request message, or the first application flow value is a preset application flow value corresponding to the service identifier or the terminal user identifier, or the first application flow value is a default application flow value;
a sending unit, configured to send, to the B2C charging network element, a first traffic application response message used for responding to the first traffic application request message, where the first traffic application response message carries the first authorized traffic value, and the first traffic application response message indicates that the B2C charging network element performs charging-free processing on the service traffic corresponding to the service identifier consumed by the user terminal corresponding to the terminal user identifier within the first authorized traffic value range.
In some possible embodiments of the present invention, in determining a first authorized traffic value corresponding to the end user identifier based on the first application traffic value and the current reservable traffic value of the sponsor traffic account corresponding to the service identifier, the authorization unit is specifically configured to: judging whether a first application flow value exceeds a current reservable flow value of the sponsor flow account, and taking the reservable flow value of the flow account as a first authorized flow value corresponding to the terminal user identification under the condition that the first application flow value exceeds the current reservable flow value of the flow account; or taking the first application flow value as a first authorized flow value corresponding to the end user identification under the condition that the first application flow value does not exceed the current reservable flow value of the sponsor flow account.
In some possible embodiments of the invention, the authorization unit is further configured to determine that the service represented by the service identifier is a traffic-sponsored service of the sponsor, before determining the first authorized traffic value corresponding to the end user identifier based on the first application traffic value and the current reservable traffic value of the sponsor traffic account.
In some possible embodiments of the present invention, the receiving unit is further configured to receive a second traffic application request message from the B2C charging network element, where the second traffic application request message carries the service identifier and the end user identifier, and the second traffic application request message is sent by the B2C charging network element after the user terminal corresponding to the end user identifier consumes the first authorized traffic value;
the authorization unit is further configured to determine a second authorized flow value corresponding to the end user identifier based on a second application flow value and a current reservable flow value of the sponsor traffic account, and subtract the second authorized flow value from the current reservable flow value of the sponsor traffic account to obtain an updated reservable flow value of the sponsor traffic account, where the first application flow value is carried in the first traffic application request message, or the first application flow value is a preset application flow value corresponding to the service identifier or the end user identifier, or the first application flow value is a default application flow value;
the sending unit is further configured to send, to the B2C charging network element, a second traffic application response message used for responding to the second traffic application request message, where the second traffic application response message carries the second authorized traffic value, and where the second traffic application response message indicates that the B2C charging network element performs charging-free processing on the service traffic corresponding to the service identifier consumed by the user terminal corresponding to the end user identifier within the second authorized traffic value range.
A third aspect of the present invention provides a telecommunications service system, which may include: B2C charging network element and B2B charging network element, where the B2C charging network element is configured to send a first traffic application request message to the B2B charging network element, where the first traffic application request message carries a service identifier and an end user identifier.
The B2B charging network element is configured to receive the first traffic application request message from the B2C charging network element, determine a first authorized traffic value corresponding to the end user identifier based on the first application traffic value and a current reservable traffic value of a sponsor traffic account corresponding to the service identifier, and subtract the first authorized traffic value from the current reservable traffic value of the sponsor traffic account to obtain an updated reservable traffic value of the sponsor traffic account; the first application traffic value is carried in the first traffic application request message, or the first application traffic value is a preset application traffic value corresponding to the service identifier or the terminal user identifier, or the first application traffic value is a default application traffic value; sending a first traffic application response message for responding to the first traffic application request message to the B2C charging network element, where the first traffic application response message carries the first authorized traffic value, and the first traffic application response message indicates that the B2C charging network element performs charging-free processing on the service traffic corresponding to the service identifier consumed by the user terminal corresponding to the terminal user identifier within the range of the first authorized traffic value.
In some possible embodiments of the present invention, the B2C charging network element is further configured to receive a traffic monitoring trigger message from a service gateway before sending the first traffic application request message, where the traffic monitoring trigger message carries the service identifier and the end user identifier, the traffic monitoring trigger message is sent by the service gateway after monitoring a service initiation message carrying the end user identifier and the service identifier, and the traffic monitoring trigger message is used to trigger the B2C charging network element to send the first traffic application request message.
Therein, the B2B charging network element in the telecommunication service system may be used for example to perform part or all of the steps performed by the B2B charging network element in the first aspect.
A fourth aspect of the present invention provides a traffic distribution processing method, including:
an enterprise-to-enterprise (B2B) charging network element receives a third flow application request message (flow red packet application request message) from an enterprise-to-user (B2C) charging network element, wherein the third flow application request message carries a service identifier (the service identifier is used for identifying a flow red packet application service) and an end user identifier; and the B2B charging network element determines a third authorized flow value (the authorized flow value is the flow red packet size) corresponding to the end user identifier based on the current reservable flow value of the sponsor traffic account corresponding to the service identifier, and subtracts the third authorized flow value from the current reservable flow value of the sponsor traffic account to obtain the updated reservable flow value of the sponsor traffic account. And the B2B charging network element sends, to the B2C charging network element, a third flow application response message for responding to the third flow application request message, where the third flow application response message carries the third authorized flow value, and the third flow application response message indicates that the B2C charging network element injects the third authorized flow value into a flow account corresponding to the end user identifier.
The third authorized flow value may be randomly calculated, or the third authorized flow value may also be the size of the default flow red packet. For example, assuming that the third authorized traffic value is 5M, the B2C charging network element injects 5M into the traffic account corresponding to the end user identifier.
In addition, a fifth aspect of the embodiments of the present application provides a flow monitoring processing apparatus. The flow monitoring processing device comprises a storage unit, a communication interface and a processor coupled with the storage unit and the communication interface. The storage unit is used for storing instructions, the processor is used for executing the instructions, and the communication interface is used for communicating with other equipment under the control of the processor. The method of the first aspect may be performed in accordance with the instructions when the instructions are executed by the processor.
Furthermore, a sixth aspect of embodiments herein provides a computer-readable storage medium storing program code for a traffic monitoring process. The program code comprises instructions for performing the method in the first aspect.
The technical scheme of the embodiment of the application is beneficial to improving the real-time performance of flow monitoring charging and further beneficial to improving the use experience of users on the sponsored flow.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.
1-a-1-b are schematic diagrams of several network architectures provided by embodiments of the present application;
fig. 2 is a schematic flow chart of a traffic monitoring processing method according to an embodiment of the present application;
fig. 3 is a schematic flow chart of a traffic distribution processing method according to an embodiment of the present application;
fig. 4 is a schematic diagram of an OCS interface relationship provided in the embodiment of the present application;
fig. 5-a is a schematic flow chart of another traffic monitoring processing method according to an embodiment of the present disclosure;
5-b-5-d are diagrams illustrating centralized parameter formats provided in accordance with embodiments of the present application;
fig. 6-a is a schematic flow chart of another traffic monitoring processing method according to an embodiment of the present disclosure;
6-b-6-c provide diagrams of lumped parameter formats for embodiments of the present application;
fig. 7-a is a schematic flow chart of another traffic distribution processing method according to the embodiment of the present application;
7-b-7-c provide diagrams of lumped parameter formats for embodiments of the present application;
fig. 8 is a schematic diagram of a B2B charging network element according to an embodiment of the present application;
fig. 9 is a schematic diagram of a telecommunication service system provided in an embodiment of the present application;
fig. 10 is a schematic diagram of another B2B charging network element according to an embodiment of the present application.
Detailed Description
The terms "comprising" and "having," and any variations thereof, as appearing in the specification, claims and drawings of this application, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus. Furthermore, the terms "first," "second," and "third," etc. are used to distinguish between different objects and are not used to describe a particular order.
The prior art drawbacks are illustrated below by exemplifying one prior art scenario.
For example, after Tencent (partner) wholesale of a traffic packet from an operator, an end user can access OTT (over The Top) service of Tencent to generate traffic for free, and The service of which The traffic can be generated for free can be called as a traffic sponsoring service. The traditional B2B charging system is basically configured to settle the wholesale price off-line, so when the end user uses the free traffic of OTT service, the B2B charging system cannot deduct the total amount in real time, or the B2B charging system cannot monitor whether the wholesale traffic packet is used up in real time, and there is no overdraft. Because the flow consumption of the end user cannot be deducted from the wholesale flow packet of the OTT service in real time, the end user cannot know whether the currently used flow can be really free (the wholesale flow packet may need to be paid after being used up) in real time, and after the actual use is delayed for a period of time, the B2C charging system can identify the flow charges used by which flow tickets to reduce or avoid. This is not very good for the end user to perceive the use of OTT services in real time (e.g., the end user cannot know whether the current traffic is free or not in real time).
For ease of understanding, some network architectures to which the aspects of the embodiments of the present application may be applied are first described below by way of example with reference to the accompanying drawings.
As shown in fig. 1-a for example, one possible network architecture mainly involves a service gateway, a B2C charging system (such as OCS/CBS) and a B2B charging system (B2B Billing system). The B2B Billing system is deployed in one or more network elements, and different functional components of the B2B Billing system can be deployed in the same or different network elements. The B2C billing system may be deployed among one or more network elements, and the different functional components in the B2C billing system may be deployed among the same or different network elements. The network element in which the charging system is deployed may be referred to as a charging network element, e.g., the network element in which the B2B charging system is deployed may be referred to as a B2B charging network element, e.g., the network element in which the B2C charging system is deployed may be referred to as a B2C charging network element. 1-B illustrate some possible interfacing ways between the B2C charging system, the B2B Billing system and other devices of the mobile communication network.
Referring to fig. 2, fig. 2 is a schematic flow chart of a flow monitoring process according to an embodiment of the present application, and as shown in fig. 2 by way of example, a method for monitoring a flow of electricity according to an embodiment of the present application may include:
201. and the B2C (Business-to-Customer) charging network element sends a first traffic application request message to the B2B charging network element. The first traffic application request message carries a service identifier and a terminal user identifier.
202. The B2B charging network element receives the first traffic application request message from the B2C charging network element. And the B2B charging network element determines a first authorized flow value corresponding to the end user identifier based on the first application flow value and the current reservable flow value of the sponsor traffic account corresponding to the service identifier, and subtracts the first authorized flow value from the current reservable flow value of the sponsor traffic account to obtain an updated reservable flow value of the sponsor traffic account.
Wherein, the B2B charging network element queries the corresponding sponsor traffic account, for example, by using the service identifier. Of course, if the first traffic application request message also carries a sponsor identifier, then the corresponding sponsor traffic account may also be determined based on the sponsor identifier.
The B2B charging network element sends, to the B2C charging network element, a first traffic application response message used for responding to the first traffic application request message, where the first traffic application response message carries the first authorized traffic value, and the first traffic application response message indicates that the B2C charging network element performs charging-free processing on the service traffic corresponding to the service identifier, consumed by the user terminal corresponding to the terminal user identifier within the first authorized traffic value range.
The B2C charging network element is a network element mainly charging for an end user, where the B2C charging network element is, for example, an Online Charging System (OCS) network element or a converged charging system (CBS) network element. The B2B charging network element is a network element mainly charging for enterprise users (such as traffic sponsors, referred to as sponsors). The B2B charging network element is, for example, a B2B Billing system network element.
A traffic sponsor (or sponsor for short) may be a partner of a telecommunications operator, such as an Tencent, Google or Baidu, for example. The service represented by the service identity may be a traffic-sponsored service, which may be, for example, a WeChat or Tencent video service.
Wherein the first application traffic value may be carried in the first traffic application request message. Or the first application flow value is a default application flow value (the default application flow value may be, for example, 5M or 15M or other value once). Or, the first application flow value is a preset application flow value corresponding to the service identifier or the terminal user identifier, for example, the service identifiers that are different may respectively correspond to different preset application flow values, for example, the corresponding preset application flow value of the WeChat is 5M, and the corresponding preset application flow value of the Tencent video is 10M).
For example, assuming that the first authorized flow value is 100M, the B2C charging network element performs charging-free processing on the service flow corresponding to the service identifier consumed by the user terminal corresponding to the terminal user identifier within a range of 100M.
It can be seen that, in the embodiment, since the B2C charging network element applies for the traffic from the B2B charging network element first, after applying for the authorized traffic (i.e., the sponsored traffic) from the B2B charging network element, the B2C charging network element may perform the charging-free processing on the traffic consumed by the user terminal corresponding to the end user identifier within the current authorized traffic range, based on such a mechanism, the end user may relatively learn in real time whether the currently used traffic can enjoy free, which is beneficial to improving the user experience. And the mechanism used after the flow is applied is favorable for reducing the complexity of the later-stage call ticket expense processing.
In some possible embodiments of the present invention, the determining a first authorized traffic value corresponding to the end user identifier based on the first application traffic value and the current reservable traffic value of the sponsor traffic account may include: judging whether a first application flow value exceeds a current reservable flow value of the sponsor flow account, wherein the reservable flow value of the flow account is used as a first authorized flow value corresponding to the terminal user identification under the condition that the first application flow value exceeds the current reservable flow value of the flow account; or taking the first application flow value as a first authorized flow value corresponding to the end user identification under the condition that the first application flow value does not exceed the current reservable flow value of the sponsor flow account.
In some possible embodiments of the present invention, before determining, by the B2B charging network element, a first authorized traffic value corresponding to the end user identifier based on the first application traffic value and the current reservable traffic value of the sponsor traffic account corresponding to the service identifier, the method may further include: and the B2B charging network element determines that the service represented by the service identification is the traffic sponsoring service of the sponsor.
In some possible embodiments of the present invention, before sending the first traffic application request message, the B2C charging network element may further include: the B2C charging network element receives a traffic monitoring trigger message from a service gateway, where the traffic monitoring trigger message carries the service identifier and the end user identifier, the traffic monitoring trigger message is sent by the service gateway after monitoring a service initiation message carrying the end user identifier and the service identifier, and the traffic monitoring trigger message is used to trigger the B2C charging network element to send the first traffic application request message.
That is, the B2C charging network element may be triggered by a service gateway (e.g., SGW, GGSN, or PGW) or the like for traffic monitoring, for example, when an end user initiates a certain traffic-sponsored service through a user terminal, the service gateway may monitor a corresponding service initiation message, and after monitoring the corresponding service initiation message, the service gateway may trigger traffic monitoring by sending a traffic monitoring trigger message to the B2C charging network element. The traffic monitoring trigger message is, for example, a Diameter Credit Control (DCC) protocol message or other protocol message.
The traffic application request message (e.g., the first traffic application request message or the second traffic application request message) may be a CCR (credit control request) message or other types of messages.
The traffic application response message (e.g., the first traffic application response message or the second traffic application response message) is a CCA (credit control response) message or other types of messages.
In some possible embodiments of the present invention, after the sending, by the B2B charging network element, the first traffic application response message for responding to the first traffic application request message to the B2C charging network element, the method may further include: the B2B charging network element receives a second traffic application request message from the B2C charging network element, where the second traffic application request message carries the service identifier and the end user identifier, and the second traffic application request message is sent by the B2C charging network element after the user terminal corresponding to the end user identifier consumes the first authorized traffic value (the traffic sponsorship service represented by the service identifier consumes the first authorized traffic value).
The B2B charging network element determines a second authorized flow value corresponding to the end user identifier based on a second application flow value and a current reservable flow value of the sponsor traffic account, and the B2B charging network element subtracts the second authorized flow value from the current reservable flow value of the sponsor traffic account to obtain an updated reservable flow value of the sponsor traffic account, where the first application flow value is carried in the first traffic application request message, or the first application flow value is a preset application flow value corresponding to the service identifier or the end user identifier, or the first application flow value is a default application flow value;
and the B2B charging network element sends, to the B2C charging network element, a second traffic application response message used for responding to the second traffic application request message, where the second traffic application response message carries the second authorized traffic value, and where the second traffic application response message indicates that the B2C charging network element performs charging-free processing on the service traffic corresponding to the service identifier, which is consumed by the user terminal corresponding to the end user identifier within the second authorized traffic value range.
That is, each time after the authorized traffic is exhausted by the traffic sponsoring service represented by the end user through the service identifier, the B2C charging network element may continue to apply for the sponsoring traffic from the B2B charging network element until the current reservable traffic value of the sponsor traffic account is exhausted. End users of the traffic-sponsored service represented by the service identity may share the current reservable traffic value of the sponsor traffic account.
Referring to fig. 3, fig. 3 is a schematic flow chart of another traffic monitoring processing method according to another embodiment of the present application, and as shown in fig. 3 by way of example, another traffic monitoring processing method according to another embodiment of the present application may include:
301. and the B2C charging network element sends a third flow application request message (flow red packet application request message) to the B2B charging network element. The third flow application request message carries a service identifier (the service identifier is used for identifying a flow red packet application service) and a terminal user identifier.
302. The B2B charging network element receives the third flow application request message from the B2C charging network element, where the third flow application request message carries a service identifier (the service identifier is used to identify a flow red packet application service) and an end user identifier. And the B2B charging network element determines a third authorized flow value corresponding to the end user identifier based on the current reservable flow value of the sponsor traffic account corresponding to the service identifier (the authorized flow value is the size of the traffic red packet). And the B2B charging network element subtracts the third authorized flow value from the current reservable flow value of the sponsor traffic account to obtain an updated reservable flow value of the sponsor traffic account.
303. And the B2B charging network element sends, to the B2C charging network element, a third flow application response message for responding to the third flow application request message, where the third flow application response message carries the third authorized flow value, and the third flow application response message indicates that the B2C charging network element injects the third authorized flow value into a flow account corresponding to the end user identifier.
304. And the charging network element of B2C injects the first authorized traffic value into a traffic account corresponding to the terminal user identifier.
It can be seen that the B2B charging network element and the B2C charging network element cooperate to complete the mechanism of allocating traffic red packets to end users.
The process of wholesale of traffic from the operator by the partner (sponsor) is described below.
The partner (sponsor) registers with the operator management platform (which may be a convergence platform or a dedicated operation management platform). The carrier management platform approves registration by the partner. The partner logs in the partner operation platform of the operator. The partner selects a flow wholesale package from the B2B product catalog. The operator has the partner subscribe to the B2B traffic wholesale package and synchronizes the subscribed B2B traffic wholesale package to the B2B Billing system. The B2B Billing system triggers the package ordering process (performs a monthly operation) and the B2B Billing system credits the complimentary traffic resource to the partner's traffic account.
For example, the service identifier of the package packed flight OTT service is synchronized to the service gateway (SCG, GGSN, PGW, etc.). And synchronizing the service identification of the Tencent OTT service to a B2C charging system, wherein the service is a real-time flow-free service of a B2B charging system. In the subsequent internet surfing process of the terminal user, the service gateway carries out real-time interactive monitoring with a B2C charging system through a Gy interface for example; the B2C billing system and the B2B billing system monitor the delivery in real time.
The operators IT build different systems, and the management flows are different. For example: the above describes a self-service management platform with partners by which the operator can register and subscribe via internet self-service means and the like.
From the latest 3Gpp 32.296d00 version looking at the OCS peripheral interface, the current specification has for the time being no dedicated real-time interface between the OCS and B2B Billing. Since OCS and B2B Billing are also used as credit control, the Ro interface between OCS and B2B Billing can be multiplexed, for example, CCR/CCA can be used for B2B traffic credit control. Based on the ability of the CCR/CCA mid-extension to carry the B2B traffic credit control parameter (B2B-Data-Info parameter). Fig. 4 illustrates an interface status diagram of the OCS.
Referring to fig. 5-a, fig. 5-a is a schematic flow chart of another traffic monitoring processing provided in another embodiment of the present application, and as shown in fig. 5-a by way of example, another traffic monitoring processing method provided in another embodiment of the present application may include:
501. the user terminal sends a service initiation request for using sponsor (such as Tencent) flow to sponsor services (such as OTT services like WeChat). The service initiation request carries a terminal user identifier, a service identifier and the like.
Wherein the service identifier is a service identifier of the traffic sponsoring service.
502. After the service gateway (such as SCG, GGSN, or PGW) monitors the service initiation message sent by the user terminal, the service gateway sends a traffic monitoring trigger message carrying the service identifier and the terminal user identifier to the charging network element in B2C (where the traffic monitoring trigger message is, for example, a DCC protocol message).
503. After receiving the traffic monitoring trigger message, the B2C charging network element sends a first CCR message to the B2B charging network element when determining that the user terminal uses the traffic sponsoring service based on the service identifier, where the first CCR message carries a B2B-data-info parameter such as an end user identifier, the service identifier, a first application traffic value, and the like.
The format of the B2B-data-info parameter carried by the first CCR message is shown in fig. 5-B as an example.
504. B2B, the charging network element queries a sponsor traffic account corresponding to the service identifier when determining that the user terminal uses the traffic sponsoring service based on the service identifier carried in the first CCR message.
505. B2B, the charging network element judges whether the first application flow value exceeds the current reservable flow value of the flow account.
If the first application flow value does not exceed the current reservable flow value of the sponsor flow account, the first application flow value is used as a first authorized flow value corresponding to the terminal user identifier, or if the first application flow value exceeds the current reservable flow value of the flow account, the reservable flow value of the flow account is used as a first authorized flow value corresponding to the terminal user identifier. B2B charging network element records the first authorized flow value and the terminal user identifier.
506. And the B2B charging network element subtracts the first authorized flow value from the current reservable flow value of the sponsor traffic account to obtain the updated reservable flow value of the sponsor traffic account.
For example, assuming that the sponsor traffic account has a current reservable traffic value of 1000M and the first authorized traffic value of 20M, the updated reservable traffic value of the sponsor traffic account is 1000M-20M 980M. That is, after the update, the sponsor traffic account currently has a reservable traffic value of 980M.
507. And the B2B charging network element sends a first CCA message for responding to the first CCR message to the B2C charging network element, where the first CCA message carries the B2B-data-info parameters, such as the first authorized traffic value, the service identifier, and the end user identifier.
The format of the B2B-data-info parameter carried by the first CCA message is shown in fig. 5-c, for example.
508. And the charging network element of B2B records the corresponding relationship between the first authorized flow value, the service identifier and the terminal user identifier. Subsequently, the B2C charging network element performs a charging-free process on the traffic of the traffic sponsorship service consumed by the user terminal corresponding to the terminal user identifier within the first authorized traffic value range.
509. And when the service gateway monitors that the user terminal uses the relevant flow fragment of the flow sponsorship service, reporting the flow value of the flow fragment to the B2C charging network element.
510. And the B2C charging network element performs charging-free processing on the traffic consumed by the user terminal within the first authorized traffic value range. And the B2C charging network element deducts the flow consumed by the user terminal from the first authorized flow value.
511. And after the first authorized traffic value is used up by the user terminal, the B2C charging network element sends a second CCR message to the B2B charging network element through a CCR interface, wherein the second CCR message can carry B2B-data-info parameters such as the service identifier, a second application traffic value and the like. The second CCR message may also carry a used grant traffic value, etc.
The format of the B2B-data-info parameter carried by the second CCR message is shown in fig. 5-d as an example.
512. The B2B charging network element may deduct the used traffic value from the sponsor traffic account and perform the step of authorizing traffic for the end user.
If the user terminal continues to use the traffic sponsoring service subsequently, the B2B charging network element may continue to authorize the traffic value for the user terminal until the reservable traffic value of the sponsor traffic account is used up.
It can be seen that, in the embodiment, since the B2C charging network element applies for the traffic from the B2B charging network element first, after applying for the authorized traffic (i.e., the sponsored traffic) from the B2B charging network element, the B2C charging network element may perform the charging-free processing on the traffic consumed by the user terminal corresponding to the end user identifier within the current authorized traffic range, based on such a mechanism, the end user may relatively learn in real time whether the currently used traffic can enjoy free, which is beneficial to improving the user experience. And the mechanism used after the flow is applied is favorable for reducing the complexity of the later-stage call ticket expense processing.
Referring to fig. 6-a, fig. 6-a is a schematic flow chart of another traffic monitoring processing provided in another embodiment of the present application, and as shown in fig. 6-a by way of example, another traffic monitoring processing method provided in another embodiment of the present application may include:
601. the user terminal sends a service initiation request for using sponsor (such as Tencent) flow to sponsor services (such as OTT services like WeChat). The service initiation request carries a user identifier, a service identifier and the like.
Wherein the service identifier is a service identifier of the traffic sponsoring service.
602. After the service gateway (such as SCG, GGSN, or PGW) monitors the service initiation message sent by the user terminal, the service gateway sends a traffic monitoring trigger message (for example, DCC protocol message) carrying the service identifier and the terminal user identifier to the charging network element in B2C.
603. After receiving the traffic monitoring trigger message, the B2C charging network element sends a third CCR message to the B2B charging network element when determining that the user terminal uses the traffic sponsoring service based on the service identifier, where the third CCR message carries a B2B-data-info parameter such as an end user identifier, the service identifier, and the like.
The format of the B2B-data-info parameter carried by the third CCR message is shown in fig. 6-B as an example.
604. B2B, the charging network element queries a sponsor traffic account corresponding to the service identifier when determining that the user terminal uses the traffic sponsoring service based on the service identifier carried in the third CCR message.
605. And B2B, the charging network element judges whether the default application flow value exceeds the current reservable flow value of the flow account.
And if the default application flow value does not exceed the current reservable flow value of the sponsor flow account, taking the default application flow value as a third authorized flow value corresponding to the terminal user identifier, or if the default application flow value exceeds the current reservable flow value of the flow account, taking the reservable flow value of the flow account as a third authorized flow value corresponding to the terminal user identifier. B2B, the charging network element records the third authorized traffic value and the terminal user identifier.
606. And the B2B charging network element subtracts the third authorized flow value from the current reservable flow value of the sponsor traffic account to obtain the updated reservable flow value of the sponsor traffic account.
For example, assuming that the sponsor traffic account has a current reservable traffic value of 500M and the third authorized traffic value of 50M, the updated reservable traffic value of the sponsor traffic account is 500M-50M-450M. That is, after the update, the sponsor traffic account currently has a reservable traffic value of 450M.
607. And the B2B charging network element sends a third CCA message for responding to a third CCR message to the B2C charging network element, where the third CCA message carries the B2B-data-info parameters, such as the third authorized traffic value, the service identifier, and the end user identifier.
The format of the B2B-data-info parameter carried by the third CCA message is shown in fig. 5-c, for example.
608. And the charging network element of B2B records the corresponding relationship between the third authorized traffic value, the service identifier and the end user identifier. Subsequently, the B2C charging network element performs a charging-free process on the traffic of the traffic sponsoring service consumed by the user terminal corresponding to the terminal user identifier within the third authorized traffic value range.
609. And when the service gateway monitors that the user terminal uses the relevant flow fragment of the flow sponsorship service, reporting the flow value of the flow fragment to the B2C charging network element.
610. And the B2C charging network element performs charging-free processing on the traffic consumed by the user terminal within the third authorized traffic value range. And the B2C charging network element deducts the flow consumed by the user terminal from the third authorized flow value.
611. And after the third authorized traffic value is used up by the user terminal, the B2C charging network element sends a fourth CCR message to the B2B charging network element through a CCR interface, where the fourth CCR message may carry a B2B-data-info parameter such as the service identifier and a fourth application traffic value. But may also carry used authorized flow values, etc.
The format of the B2B-data-info parameter carried by the fourth CCR message is shown in fig. 6-c as an example.
612. The B2B charging network element may deduct the used traffic value from the sponsor traffic account and perform the step of authorizing traffic for the end user. If the user terminal continues to use the traffic sponsoring service subsequently, the B2B charging network element may continue to authorize the traffic value for the user terminal until the reservable traffic value of the sponsor traffic account is used up.
It can be seen that, in the embodiment, because the B2C charging network element applies the default traffic value to the B2B charging network element first, after applying the authorized traffic (i.e., the sponsored traffic) from the B2B charging network element, the B2C charging network element may perform the charging-free processing on the traffic consumed by the user terminal corresponding to the end user identifier within the current authorized traffic range, and based on such a mechanism, the end user may relatively learn in real time whether the currently used traffic can enjoy free, which is beneficial to improving the user experience. And the mechanism used after the flow is applied is favorable for reducing the complexity of the later-stage call ticket expense processing.
The following is an example of a scenario where an end user is preempting a sponsor's traffic red envelope in real time.
The method comprises the steps that an end user snatches a flow red packet wholesale by a sponsor (such as an OTT partner) in real time, and the scene is a process that flow is distributed from a sponsor flow account to the end user (OCS account flow injected into the end user) in a flow red packet mode. The process is a non-session operation, belongs to flow credit control for the B2B Billing process, can reuse a Ro interface, and is realized by extending the B2B-data-info parameter of CCR/CCA.
Referring to fig. 7-a, fig. 7-a is a schematic flow chart of a traffic distribution processing method according to another embodiment of the present application, as shown in fig. 7-a by way of example, a traffic distribution processing method according to another embodiment of the present application may include:
701. the end user initiates a red envelope rush message, for example, via the traffic red envelope platform of the sponsor (e.g., Tencent).
702. The service gateway (such as SCG or GGSN) identifies the red packet robbing service identifier and triggers a real-time red packet robbing message to the B2C charging network element.
703. And the B2C charging network element identifies that the end user initiates the red packet service of the preemptive, and the B2C charging network element sends a fifth CCR message to the B2B Billing network element. The fifth CCR message carries a service identity (for red packet service) and an end user identity (e.g. a telephone number, etc.)
The format of the B2B-data-info parameter carried by the fifth CCR message may be as shown in fig. 7-B, for example.
704. And B2B Billing network element verifies that the current terminal user accesses the red packet robbery service based on the service identifier carried by the fifth CCR message, and after the verification is successful, the traffic account of the sponsor is obtained through the service identifier query.
705. The B2B Billing network element determines a traffic red envelope authorization value based on the preemptible traffic value of the sponsor's traffic account.
This is illustrated in several cases below.
For example, assuming that the fifth CCR message reports a traffic red packet application value, if the current preemptible traffic value is greater than or equal to the traffic red packet application value, the traffic red packet application value is a traffic red packet authorization value, and the authorized traffic is subtracted from the preemptible traffic value. And if the current flow value capable of being purchased is smaller than the flow red packet application value, taking the flow value capable of being purchased as a flow red packet authorization value, and simultaneously deducting the flow value capable of being purchased to 0.
For another example, if the fifth CCR message does not report the traffic red packet application value, there may be multiple algorithms for traffic red packet allocation, which are only one of the following: the network element can calculate the total number of the traffic red packets and the size of the traffic available for robbery in advance: for example: the total red packet flow is 300M, if 10 red packets are set and the proportion of available for robbery is 10%, the 270M flow is divided into 27M in advance, and then the remaining 30M flow is used as the transportation gas.
For example, the priority is from remaining 27M that have already been allocated red packets, and then the remaining 30M is provided in a level difference manner: for example: the first end user is assigned 10M, the second end user 5M, and so on. The issued traffic red packet authorization value is equal to the pre-allocated 27M + transportation gas part (e.g. 3M).
706. And the B2B Billing network element sends a fifth CCA message to the B2C charging network element, where the fifth CCA message carries the terminal user identifier, the traffic red packet authorization value, the service identifier, and the like.
The format of the B2B-data-info parameter carried by the fifth CCA message may be, for example, as shown in fig. 7-c.
707. And the B2C charging network element judges whether the authorized flow is issued by the B2B Billing, and injects the flow red packet authorization value into the flow account of the terminal user, and the wholesale price charge of the current robbery purchase of the red packet is 0.
The B2C charging network element may also return a cca (event) success to the GGSN.
It can be seen that the B2B charging network element and the B2C charging network element cooperate to complete the mechanism of allocating traffic red packets to end users.
The following also provides related apparatus that may be used to implement the above-described scheme.
Referring to fig. 8, an embodiment of the present invention provides a B2B charging network element 800, including:
a receiving unit 810, configured to receive a first traffic application request message carrying a service identifier and an end user identifier from a charging network element of B2C.
An authorization unit 820, configured to determine a first authorized flow value corresponding to the end user identifier based on a first application flow value and a current reservable flow value of a sponsor flow account corresponding to the service identifier, and subtract the first authorized flow value from the current reservable flow value of the sponsor flow account to obtain an updated reservable flow value of the sponsor flow account; the first application flow value is carried in the first flow application request message, or the first application flow value is a preset application flow value corresponding to the service identifier or the terminal user identifier, or the first application flow value is a default application flow value;
a sending unit 830, configured to send a first traffic application response message used for responding to the first traffic application request message to the B2C charging network element, where the first traffic application response message carries the first authorized traffic value, and the first traffic application response message indicates that the B2C charging network element performs charging-free processing on the service traffic corresponding to the service identifier consumed by the user terminal corresponding to the terminal user identifier within the first authorized traffic value range.
In some possible embodiments of the present invention, in determining a first authorized traffic value corresponding to the end user identifier based on the first application traffic value and the current reservable traffic value of the sponsor traffic account corresponding to the service identifier, the authorization unit is specifically configured to: judging whether a first application flow value exceeds a current reservable flow value of the sponsor flow account, and taking the reservable flow value of the flow account as a first authorized flow value corresponding to the terminal user identification under the condition that the first application flow value exceeds the current reservable flow value of the flow account; or taking the first application flow value as a first authorized flow value corresponding to the end user identification under the condition that the first application flow value does not exceed the current reservable flow value of the sponsor flow account.
In some possible embodiments of the present invention, the authorization unit 820 is further configured to determine that the service represented by the service identifier is a traffic-sponsored service of the sponsor before determining the first authorized traffic value corresponding to the end user identifier based on the first application traffic value and the current reservable traffic value of the sponsor traffic account.
In some possible embodiments of the present invention, the receiving unit 810 is further configured to receive a second traffic application request message from the B2C charging network element, where the second traffic application request message carries the service identifier and the end user identifier, and the second traffic application request message is sent by the B2C charging network element after the user terminal corresponding to the end user identifier consumes the first authorized traffic value.
The authorization unit 820 is further configured to determine a second authorized flow value corresponding to the end user identifier based on a second application flow value and a current reservable flow value of the sponsor flow account, and subtract the second authorized flow value from the current reservable flow value of the sponsor flow account to obtain an updated reservable flow value of the sponsor flow account, where the first application flow value is carried in the first flow application request message, or the first application flow value is a preset application flow value corresponding to the service identifier or the end user identifier, or the first application flow value is a default application flow value.
The sending unit 830 is further configured to send, to the B2C charging network element, a second traffic application response message used for responding to the second traffic application request message, where the second traffic application response message carries the second authorized traffic value, and where the second traffic application response message indicates that the B2C charging network element performs charging-free processing on the service traffic corresponding to the service identifier, which is consumed by the user terminal corresponding to the end user identifier within the second authorized traffic value range.
Referring to fig. 9, a third aspect of the present invention provides a telecommunication service system, which may include: B2C charging network element 910 and B2B charging network element 920, where the B2C charging network element 910 is configured to send a first traffic application request message to the B2B charging network element, and the first traffic application request message carries a service identifier and an end user identifier.
The B2B charging network element 920, configured to receive the first traffic application request message from the B2C charging network element, determine a first authorized traffic value corresponding to the end user identifier based on the first application traffic value and a current reservable traffic value of a sponsor traffic account corresponding to the service identifier, and subtract the first authorized traffic value from the current reservable traffic value of the sponsor traffic account to obtain an updated reservable traffic value of the sponsor traffic account; the first application traffic value is carried in the first traffic application request message, or the first application traffic value is a preset application traffic value corresponding to the service identifier or the terminal user identifier, or the first application traffic value is a default application traffic value; sending a first traffic application response message for responding to the first traffic application request message to the B2C charging network element, where the first traffic application response message carries the first authorized traffic value, and the first traffic application response message indicates that the B2C charging network element performs charging-free processing on the service traffic corresponding to the service identifier consumed by the user terminal corresponding to the terminal user identifier within the range of the first authorized traffic value.
In some possible embodiments of the present invention, the B2C charging network element 910 is further configured to receive, before sending the first traffic application request message, a traffic monitoring trigger message from a service gateway, where the traffic monitoring trigger message carries the service identifier and the end user identifier, the traffic monitoring trigger message is sent by the service gateway after monitoring a service initiation message carrying the end user identifier and the service identifier, and the traffic monitoring trigger message is used to trigger the B2C charging network element to send the first traffic application request message.
Therein, the B2B charging network element in the telecommunication service system may be used for example to perform part or all of the steps performed by the B2B charging network element in the first aspect.
Referring to fig. 10, a B2B charging network element 1000 provided in the embodiment of the present application includes:
a storage unit 1010, a communication interface 1010, and a processor 1030 coupled to the storage unit 1010 and the communication interface 1020. The storage unit 1010 is configured to store instructions, the processor 1020 is configured to execute the instructions, and the communication interface 1020 is configured to communicate with other devices under the control of the processor 1030. When executing the instructions, the processor 1030 may perform any one of the methods in the above embodiments of the present application according to the instructions.
Processor 1030 may also be referred to as a Central Processing Unit (CPU). Memory unit 1010 may include a read-only memory and a random access memory, and provides instructions and data, etc. to processor 1030. A portion of the memory unit 1010 may also include non-volatile random access memory. In a particular application the components of the B2B charging network element 1000 are coupled together, for example by a bus system. The bus system may include a power bus, a control bus, a status signal bus, and the like, in addition to the data bus. For clarity of illustration, however, the various buses are labeled in the figure as the bus system 1040. The methods disclosed in the embodiments of the present invention described above may be applied to processor 1030 or implemented by processor 1030. Processor 1030 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by instructions in the form of hardware, integrated logic circuits, or software in the processor 1030. The processor 1030 may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, an off-the-shelf programmable gate array or other programmable logic device, discrete gate or transistor logic, or discrete hardware components, among others. Processor 1030 may implement or perform the methods, steps, and logic blocks disclosed in embodiments of the present invention. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the storage unit 1010, and the processor 1030 can read information in the storage unit 1010 and complete the steps of the method in combination with hardware thereof.
For example, the B2B charging network element 1000 executes the method flow in step 201 and 203 in the above embodiments. Or the charging network element 1000 in B2B may further execute the method flow corresponding to the charging network element in B2B in the embodiments described in fig. 3, fig. 5-a, fig. 6-a, and fig. 7-a.
In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus may be implemented in other manners. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is merely a logical division, and the actual implementation may have another division, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted or not executed. In addition, the indirect coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, indirect coupling or communication connection of devices or units, and may be electrical or in other forms.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit may be implemented in the form of hardware, or may also be implemented 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 stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.

Claims (24)

1. A traffic monitoring processing method is applied to a charging network element of a user B2C by an enterprise, wherein the charging network element of the B2C is a network element for charging aiming at an end user, and the method comprises the following steps:
sending a first traffic application request message to a B2B charging network element of an enterprise, where the first traffic application request message carries an end user identifier and a service identifier, and the B2B charging network element is a network element for charging an enterprise user;
receiving a first traffic application response message from the B2B charging network element, where the first traffic application response message carries a first authorized traffic value;
and performing charging-free processing on the flow consumed by the user terminal corresponding to the terminal user identifier within the first authorized flow value range, or injecting the first authorized flow value into an account corresponding to the terminal user identifier.
2. The method according to claim 1, wherein the performing charging-free processing on the flow consumed by the user terminal corresponding to the terminal user identifier within the first authorized flow value range specifically includes:
and performing charging-free processing on the flow of the service corresponding to the service identifier consumed by the user terminal corresponding to the terminal user identifier within the first authorized flow value range.
3. The method according to claim 1 or 2, wherein before sending the first traffic application request message to the B2B charging network element, the method further comprises:
receiving a traffic monitoring trigger message, where the traffic monitoring trigger message includes the service identifier and the end user identifier, and the traffic monitoring trigger message is used to trigger the B2C charging network element to send the first traffic application request message.
4. The method according to claim 1 or 2, wherein the first traffic application request message further carries an enterprise user identity.
5. The method according to claim 1 or 2, wherein before sending the first traffic application request message to the B2B charging network element, the method further comprises:
and determining that the user terminal corresponding to the terminal user identification uses the flow sponsorship service based on the service identification.
6. The method according to claim 1 or 2, wherein the first traffic application request message further carries a first application traffic value.
7. The method according to any one of claims 1-2, further comprising:
and after the user terminal corresponding to the terminal user identifier consumes the first authorized flow value, sending a second flow application request message to the B2B charging network element, where the second flow application request message carries the service identifier and the terminal user identifier.
8. The method of claim 7, wherein the second traffic application request message further carries a used traffic value.
9. The method of claim 8, further comprising:
receiving a second traffic application response message from the B2B charging network element, where the second traffic application response message carries a second authorized traffic value;
and according to the second flow application response message, performing charging-free processing on the service flow corresponding to the service identification consumed by the user terminal corresponding to the terminal user identification within the second authorized flow value range.
10. The method of any one of claims 1-2, 8, and 9, wherein:
and the B2C charging network element is an OCS (online charging system) network element or a CBS (converged charging system) network element.
11. The method according to any of claims 1-2, 8, 9, wherein the traffic application request message is a credit control request CCR message and the traffic application response message is a credit control response CCA message.
12. A traffic monitoring processing method is applied to a charging network element of an enterprise to enterprise B2B, wherein the charging network element of B2B is a network element for charging enterprise users, and the method comprises the following steps:
receiving a first traffic application request message from an enterprise charging network element of a user B2C, wherein the first traffic application request message carries an end user identifier and a service identifier, and the B2C charging network element is a network element for charging for an end user;
determining a first authorized flow value corresponding to the end user identifier based on the first application flow value and the current reservable flow value of the sponsor flow account corresponding to the service identifier;
and sending a first traffic application response message to the B2C charging network element, where the first traffic application response message carries the first authorized traffic value.
13. The method of claim 12, wherein the first traffic application request message further carries an identifier of the enterprise user, and the enterprise user account is an enterprise user account corresponding to the identifier of the enterprise user.
14. The method of any of claims 12-13, wherein after determining the first authorized flow value for the end user identity based on the first application flow value and the current reservable flow value for the sponsor traffic account for the service identity, the method further comprises:
and deducting the first authorized flow value from the current reserved flow value of the enterprise user account to obtain an updated reserved flow value of the enterprise user account.
15. The method according to any of claims 12-13, wherein the first application traffic value is carried in the first traffic application request message, or the first application traffic value is a preset application traffic value corresponding to the service identifier or the end user identifier, or the first application traffic value is a default application traffic value.
16. The method according to any of claims 12-13, wherein the determining a first authorized traffic value for the end user identity based on the first application traffic value and a current reservable traffic value for a sponsor traffic account for the service identity comprises:
judging whether a first application flow value exceeds a current reservable flow value of the enterprise user account, wherein the reservable flow value of the account is used as a first authorized flow value corresponding to the terminal user identification under the condition that the first application flow value exceeds the current reservable flow value of the account; or taking the first application flow value as a first authorized flow value corresponding to the terminal user identifier under the condition that the first application flow value does not exceed the current reservable flow value of the enterprise user account.
17. The method of any of claims 12-13, wherein prior to determining the first authorized traffic value for the end user identifier based on the first application traffic value and the current reservable traffic value for the enterprise user account for the service identifier, the method further comprises:
and determining that the service represented by the service identification is the flow sponsoring service of the enterprise user.
18. The method according to any of claims 12-13, wherein after said sending a first traffic application response message to said B2C charging network element, the method further comprises:
receiving a second traffic application request message from the B2C charging network element, where the second traffic application request message carries the service identifier and the end user identifier;
determining a second authorized flow value corresponding to the terminal user identification based on a second application flow value and the current reservable flow value of the enterprise user account;
and sending a second traffic application response message to the B2C charging network element, where the second traffic application response message carries the second authorized traffic value.
19. The method of claim 18, wherein the second traffic application request message further includes a used traffic value, the method further comprising: deducting the used traffic value from the enterprise user account.
20. The method according to any of claims 12-13, 19, wherein the traffic application request message is a credit control request, CCR, message and the first traffic application response message is a credit control response, CCA, message.
21. An enterprise user B2C charging network element, comprising a processor and a memory, wherein:
the memory to store program instructions;
the processor is configured to call and execute the program instructions stored in the memory, so as to cause the B2C charging network element to execute the traffic monitoring processing method according to any one of claims 1 to 11.
22. A computer-readable storage medium comprising instructions that, when executed on a computer, cause the computer to perform the flow monitoring processing method of any one of claims 1 to 11.
23. An enterprise to enterprise B2B charging network element, comprising a processor and a memory, wherein:
the memory to store program instructions;
the processor is configured to call and execute the program instructions stored in the memory, so as to cause the B2B charging network element to execute the traffic monitoring processing method according to any one of claims 12 to 20.
24. A computer-readable storage medium comprising instructions that, when executed on a computer, cause the computer to perform the flow monitoring processing method of any one of claims 12 to 20.
CN201910631444.8A 2016-06-30 2016-06-30 Flow monitoring processing method and related device and system Active CN110381455B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910631444.8A CN110381455B (en) 2016-06-30 2016-06-30 Flow monitoring processing method and related device and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910631444.8A CN110381455B (en) 2016-06-30 2016-06-30 Flow monitoring processing method and related device and system
CN201610507022.6A CN105933883B (en) 2016-06-30 2016-06-30 Traffic monitoring processing method and relevant apparatus and system

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
CN201610507022.6A Division CN105933883B (en) 2016-06-30 2016-06-30 Traffic monitoring processing method and relevant apparatus and system

Publications (2)

Publication Number Publication Date
CN110381455A CN110381455A (en) 2019-10-25
CN110381455B true CN110381455B (en) 2021-02-23

Family

ID=56830185

Family Applications (2)

Application Number Title Priority Date Filing Date
CN201610507022.6A Active CN105933883B (en) 2016-06-30 2016-06-30 Traffic monitoring processing method and relevant apparatus and system
CN201910631444.8A Active CN110381455B (en) 2016-06-30 2016-06-30 Flow monitoring processing method and related device and system

Family Applications Before (1)

Application Number Title Priority Date Filing Date
CN201610507022.6A Active CN105933883B (en) 2016-06-30 2016-06-30 Traffic monitoring processing method and relevant apparatus and system

Country Status (2)

Country Link
CN (2) CN105933883B (en)
WO (1) WO2018000992A1 (en)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105933883B (en) * 2016-06-30 2019-07-19 华为技术有限公司 Traffic monitoring processing method and relevant apparatus and system
CN107819700B (en) * 2016-09-13 2021-07-27 法法汽车(中国)有限公司 Network flow control method and device of terminal equipment
CN108234141B (en) * 2016-12-22 2021-08-24 中移(杭州)信息技术有限公司 Directional traffic processing method and server
CN110198530B (en) * 2019-05-31 2022-07-08 中国联合网络通信集团有限公司 Flow-free service scheduling processing method, device, equipment and storage medium
CN115086092B (en) * 2021-03-15 2023-08-15 中国移动通信集团湖北有限公司 Method, device, equipment and storage medium for rating communication ticket
CN115037653B (en) * 2022-06-28 2023-10-13 北京奇艺世纪科技有限公司 Service flow monitoring method, device, electronic equipment and storage medium

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101959168A (en) * 2009-07-16 2011-01-26 华为技术有限公司 Billing statistical method and device
CN104506326A (en) * 2014-11-18 2015-04-08 华为技术有限公司 Billing method for sponsorship service, system and related equipment
CN104955013A (en) * 2014-03-26 2015-09-30 中兴通讯股份有限公司 Usage monitoring method, apparatus and system
CN105471753A (en) * 2014-08-15 2016-04-06 中国电信股份有限公司 Method, device and system for realizing accurate control for application data traffic
CN105591828A (en) * 2014-10-20 2016-05-18 中兴通讯股份有限公司 Traffic monitoring method and device
CN105703915A (en) * 2014-11-26 2016-06-22 阿尔卡特朗讯 Sponsor charging control method, sponsor charging control device and sponsor charging control system

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8125984B2 (en) * 2008-03-21 2012-02-28 International Business Machines Corporation Method, system, and computer program product for implementing stream processing using a reconfigurable optical switch
CN102480718B (en) * 2010-11-29 2015-04-01 中兴通讯股份有限公司 Method for supporting sponsored data connectivity at roaming scene and system thereof
CN102547854B (en) * 2010-12-24 2015-08-12 中兴通讯股份有限公司 Policy control method and device
CN103220158B (en) * 2012-01-21 2016-12-14 阿尔卡特朗讯 A kind of method and apparatus that sponsorship data application is carried out charging control
CN103379462B (en) * 2012-04-23 2017-03-01 阿尔卡特朗讯 A kind of method and apparatus for processing accounting request
US9014663B2 (en) * 2012-09-28 2015-04-21 Alcatel Lucent Sponsored data plan management
CN105025457B (en) * 2014-04-28 2019-02-26 中国电信股份有限公司 LTE charge on traffic method, system and packet data gateway
CN105933883B (en) * 2016-06-30 2019-07-19 华为技术有限公司 Traffic monitoring processing method and relevant apparatus and system

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101959168A (en) * 2009-07-16 2011-01-26 华为技术有限公司 Billing statistical method and device
CN104955013A (en) * 2014-03-26 2015-09-30 中兴通讯股份有限公司 Usage monitoring method, apparatus and system
CN105471753A (en) * 2014-08-15 2016-04-06 中国电信股份有限公司 Method, device and system for realizing accurate control for application data traffic
CN105591828A (en) * 2014-10-20 2016-05-18 中兴通讯股份有限公司 Traffic monitoring method and device
CN104506326A (en) * 2014-11-18 2015-04-08 华为技术有限公司 Billing method for sponsorship service, system and related equipment
CN105703915A (en) * 2014-11-26 2016-06-22 阿尔卡特朗讯 Sponsor charging control method, sponsor charging control device and sponsor charging control system

Also Published As

Publication number Publication date
CN105933883B (en) 2019-07-19
WO2018000992A1 (en) 2018-01-04
CN105933883A (en) 2016-09-07
CN110381455A (en) 2019-10-25

Similar Documents

Publication Publication Date Title
CN110381455B (en) Flow monitoring processing method and related device and system
CN106817686B (en) Charging method and device
CN100389561C (en) Charge network and charge agency device and charge method
US8090652B2 (en) System and method for charging in a communications network and a communications network charging server
EP2705654B1 (en) Method and apparatus for controlling charging of a service
CN110417561B (en) Block chain-based distributed charging method, device and system
EP3567799B1 (en) Charging methods, apparatuses and system
US8630397B2 (en) Method and system for enabling charging of non-charging controlled services
US20220286564A1 (en) Method and Apparatus for Dynamic Realtime Sharing of Credit Units for Online Charging
CN100365983C (en) Method for realizing packet data prepayment service
CN110324153B (en) Charging method and system
CN109547956B (en) Multi-service concurrent processing method
CN111542005B (en) Charging method, device, equipment and storage medium
CN109963260A (en) A kind of method and device that determining business terminates
CN108270580B (en) Reminding method, device and system for online charging
WO2017000644A1 (en) Method and device for account resource sharing
US9549306B2 (en) Usage triggered telecommunications charging
CN111818471B (en) Resource charging method, MEC management system and MEC host
CN108809666B (en) Method, device and equipment for online charging of flow
JP2016208131A (en) Tie-up service providing method
CN101212781A (en) Prepaid data service billing method for mobile terminal in roaming state
CN102480363B (en) Charging method, device and system based on flow or conversation flow
KR101061717B1 (en) Calculation method of attracting subscribers by communication service unit by session
US20230013156A1 (en) Method and Apparatus for Service Charging in a Communication Network
EP2590359B1 (en) Method, system, charging equipment, and account balance management center for free resources processing

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant