CN103384202B - The transmission method and equipment of a kind of flow report message - Google Patents
The transmission method and equipment of a kind of flow report message Download PDFInfo
- Publication number
- CN103384202B CN103384202B CN201310302670.4A CN201310302670A CN103384202B CN 103384202 B CN103384202 B CN 103384202B CN 201310302670 A CN201310302670 A CN 201310302670A CN 103384202 B CN103384202 B CN 103384202B
- Authority
- CN
- China
- Prior art keywords
- bearer
- charging
- management module
- information
- service
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 32
- 230000005540 biological transmission Effects 0.000 title claims abstract description 9
- 238000007600 charging Methods 0.000 claims abstract description 189
- 230000011664 signaling Effects 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses the transmission method and equipment of a kind of flow report message, the method includes：When IP CAN carry corresponding charge information and meet charging report condition, the corresponding relation between the service traffics information that the index and IP CAN that service surface management module records IP CAN carryings in form in IP CAN carryings are carried；The startup of service surface management module reports timer T；After timer T time-out is reported, the index carried using multiple IP CAN selects the service traffics information that corresponding multiple IP CAN are carried from form in IP CAN carryings, the service traffics information that multiple IP CAN are carried is added in same flow report message, and flow report message is sent to billing management module.In the embodiment of the present invention, it is possible to reduce the quantity forwarded of flow report message, the process performance of billing management module is improved, and reduce the message processing load of PGW chargings, effectively alleviate the processing pressure of charge system.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method and a device for transmitting a traffic report message.
Background
In an EPC (Evolved Packet Core) system, a charging mechanism of a PGW (Packet Gateway) involves the following functional modules: a signaling plane management module (or called as a control plane management module), a service plane management module, and a Charging management module (e.g., a Charging Data Record System (CDRS)). The signaling plane management module is used for acquiring a charging parameter and configuring the charging parameter to the service plane management module and the charging management module; the service face management module is used for carrying out service flow statistics on the data flow according to the charging parameters and reporting the service flow statistical result to the charging management module; the Charging management module is configured to generate a CDR (Charging Data Record) according to the Charging parameter and the service traffic statistic result, and report the CDR to a CGF (Charging gateway function) entity, thereby completing a Charging function.
Aiming at the processing process of a service Plane (User Plane) management module, after an IP-CAN (IP-Connectivity Access Network) bearer corresponding to a terminal device is successfully established, in the data transmission process, the service Plane management module counts service traffic (including uplink traffic and downlink traffic) transmitted on the IP-CAN bearer, reports the service traffic information of the IP-CAN bearer to a charging management module through a traffic report message when charging information corresponding to the IP-CAN bearer meets a charging report condition, and generates a corresponding CDR for the IP-CAN bearer by the charging management module.
In the above implementation manner, when the charging information corresponding to each IP-CAN bearer satisfies the charging reporting condition, the service plane management module reports the service traffic information of one IP-CAN bearer to the charging management module through one traffic reporting message, so that how many traffic reporting messages need to be sent to the charging management module if how many charging information corresponding to each IP-CAN bearer satisfies the charging reporting condition.
In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art:
when a large number of online terminal devices exist and each terminal device corresponds to a plurality of IP-CAN bearers, the service plane management module may need to send a large number of traffic report messages to the charging management module at the same time, thereby causing a transient burst of the traffic report messages, causing an impact on the charging management module, and affecting the normal charging process of other services currently performed by the charging management module; in addition, the charging management module needs to process a large amount of flow reporting messages instantly, so that the processing performance of the charging management module is reduced.
Disclosure of Invention
Embodiments of the present invention provide a method and an apparatus for transmitting a traffic report message, so as to reduce the number of traffic report messages sent and improve the processing performance of a charging management module.
In order to achieve the above object, an embodiment of the present invention provides a method for transmitting a traffic report message, where the method includes:
when the charging information corresponding to the IP-CAN bearer of the IP connection access network meets the charging reporting condition, the service plane management module records the index of the IP-CAN bearer and the corresponding relation between the service flow information of the IP-CAN bearer in an IP-CAN bearer upper report; wherein, the index of each IP-CAN bearer recorded in the report on the IP-CAN bearer is unique;
the service plane management module starts a reporting timer T; after the reporting timer T is overtime, the service plane management module selects corresponding service flow information of a plurality of IP-CAN bearers from the IP-CAN bearer reporting table by using indexes of the plurality of IP-CAN bearers, adds the service flow information of the plurality of IP-CAN bearers into the same flow reporting message, and sends the flow reporting message to a charging management module; and the charging management module generates corresponding charging data call ticket CDR for the IP-CAN bearers by utilizing the service flow information borne by the IP-CAN bearers.
The embodiment of the invention provides a transmission device for a flow report message, which comprises a service plane management module and a charging management module, wherein the service plane management module specifically comprises:
the determining unit is used for determining that the charging information corresponding to the IP-CAN bearer of the IP connection access network meets the charging reporting condition;
the recording unit is used for recording the corresponding relation between the index of the IP-CAN bearer and the service flow information of the IP-CAN bearer in an IP-CAN bearer upper report when the charging information corresponding to the IP-CAN bearer meets a charging upper report condition; wherein, the index of each IP-CAN bearer recorded in the report on the IP-CAN bearer is unique;
a sending unit, configured to start a reporting timer T; after the reporting timer T is overtime, selecting corresponding service flow information of a plurality of IP-CAN bearers from the IP-CAN bearer reporting table by using indexes of the plurality of IP-CAN bearers, adding the service flow information of the plurality of IP-CAN bearers into the same flow reporting message, and sending the flow reporting message to a charging management module; and the charging management module generates corresponding charging data call ticket CDR for the IP-CAN bearers by utilizing the service flow information borne by the IP-CAN bearers.
Compared with the prior art, the embodiment of the invention at least has the following advantages: in the embodiment of the invention, when the charging information corresponding to the IP-CAN bearer meets the charging reporting condition, the service plane management module does not directly send the flow reporting message to the charging management module, but records the service flow information of the IP-CAN bearer in the report form of the IP-CAN bearer, so that after the reporting timer T is overtime, the service flow information of a plurality of IP-CAN bearers is sent to the charging management module through one flow reporting message, and the charging management module respectively generates corresponding CDRs for the plurality of IP-CAN bearers by using the service flow information of the plurality of IP-CAN bearers, thereby reducing the sending quantity of the flow reporting message, improving the processing performance of the charging management module, greatly reducing the message processing load of PGW charging and effectively relieving the processing pressure of a charging system. Furthermore, the processing capability of the PGW may be enhanced, and particularly, the fault tolerance of the PGW may be effectively improved when the PGW fails or is abnormal.
Drawings
In order to more clearly illustrate the technical solution of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is apparent that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained based on these drawings without inventive labor.
Fig. 1 is a flowchart of a method for transmitting a traffic report message according to an embodiment of the present invention;
fig. 2 is a structural diagram of a device for reporting a message on a traffic flow according to a second embodiment of the present invention.
Detailed Description
The technical solutions in the present invention will be described clearly and completely with reference to the accompanying drawings, and it is obvious that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Example one
To solve the problems in the prior art, an embodiment of the present invention provides a method for transmitting a traffic report message, where the method may be applied to an EPC system, and a charging mechanism of a PGW in the EPC system involves the following functional modules: a signaling plane management module (or called as a control plane management module) for acquiring a charging parameter and configuring the charging parameter to a service plane management module and a charging management module, a service plane management module (for performing service traffic statistics on a data stream according to the charging parameter and reporting the service traffic statistical result to the charging management module), and a charging management module (such as a CDRS for generating a CDR according to the charging parameter and the service traffic statistical result and reporting the CDR to a CGF entity, thereby completing a charging function). Further, in terms of the processing procedure of the service plane management module, after the IP-CAN bearer corresponding to the terminal device is successfully established, in the data transmission procedure, the service plane management module counts the service traffic (including uplink traffic and downlink traffic) transmitted on the IP-CAN bearer, and when the charging information corresponding to the IP-CAN bearer meets the charging reporting condition, as shown in fig. 1, the method includes the following steps:
step 101, when the charging information corresponding to the IP-CAN bearer meets the charging reporting condition, the service plane management module (located in the PGW) records the index of the IP-CAN bearer and the corresponding relationship between the service traffic information of the IP-CAN bearer in an IP-CAN bearer upper report (such as a local bearer example).
In the embodiment of the present invention, the process of determining that the charging information corresponding to the IP-CAN bearer satisfies the charging reporting condition by the service plane management module specifically includes, but is not limited to, the following modes:
in the first situation, when the service plane management module learns that the time threshold (which CAN be set according to actual experience) corresponding to the IP-CAN bearer arrives, it is determined that the charging information corresponding to the IP-CAN bearer meets the charging reporting condition.
And in the second situation, when the service plane management module learns that the flow threshold (which CAN be set according to actual experience) corresponding to the IP-CAN bearer reaches, the service plane management module determines that the charging information corresponding to the IP-CAN bearer meets the charging reporting condition.
And thirdly, when the service plane management module learns that the rate change time point corresponding to the IP-CAN bearer arrives, determining that the charging information corresponding to the IP-CAN bearer meets the charging reporting condition.
And fourthly, when the service plane management module learns that the rate group level time threshold corresponding to the IP-CAN bearer is reached, determining that the charging information corresponding to the IP-CAN bearer meets the charging reporting condition. For the set of all traffic flows with the same rate ID on the IP-CAN bearer, one CAN understand a rate group, and the rate group level time threshold is for all traffic flows in the rate group, which CAN be set according to practical experience.
And fifthly, when the service plane management module learns that the rate group level flow threshold corresponding to the IP-CAN bearer is reached, determining that the charging information corresponding to the IP-CAN bearer meets the charging reporting condition. For the set of all traffic flows with the same rate ID on the IP-CAN bearer, one CAN understand a rate group, and the rate group level traffic threshold is limited to the sum of the traffic flows generated on all traffic flows in the rate group, which CAN be set according to practical experience.
In the embodiment of the present invention, the service traffic information carried by the IP-CAN specifically includes, but is not limited to, one or any combination of the following: identification information of an IP-CAN bearer (for identifying a certain IP-CAN bearer of a certain terminal device), system time information when charging information corresponding to the IP-CAN bearer satisfies a charging reporting condition (e.g., a time period from a current system time, a system time when the charging information corresponding to the last IP-CAN bearer satisfies the charging reporting condition to a system time when the charging information corresponding to the current IP-CAN bearer satisfies the charging reporting condition, a system time when the charging information corresponding to the last IP-CAN bearer satisfies the charging reporting condition, a system time when the charging information corresponding to the current IP-CAN bearer satisfies the charging reporting condition, etc.), bearer flow information (i.e., a period from the system time when the charging information corresponding to the last IP-CAN bearer satisfies the charging reporting condition to the system time when the charging information corresponding to the current IP-CAN bearer satisfies the charging reporting condition, the flow value of the bearer), bearer level charging cause information (e.g.: reporting due to arrival of a time threshold corresponding to the IP-CAN bearer, reporting due to arrival of a flow threshold corresponding to the IP-CAN bearer, reporting due to arrival of a rate change time point corresponding to the IP-CAN bearer, reporting due to arrival of a rate group level time threshold corresponding to the IP-CAN bearer, and reporting due to arrival of a rate group level flow threshold corresponding to the IP-CAN bearer).
In the embodiment of the invention, a service plane management module needs to maintain an IP-CAN bearing report in advance, the IP-CAN bearing report is used for recording the corresponding relation between the index of an IP-CAN bearing and service flow information of the IP-CAN bearing, and the index of each IP-CAN bearing recorded in the IP-CAN bearing report is unique; as shown in table 1, when the charging information corresponding to 99 IP-CAN bearers at the same time satisfies the charging reporting condition, the service plane management module maintains an IP-CAN bearer upper report.
TABLE 1
| Indexing of IP-CAN bearers | IP-CAN borne service flow information |
| 1 | Traffic flow information 1 |
| 2 | Traffic flow information 2 |
| 3 | Traffic flow information 3 |
| .... | ... |
| 98 | Traffic flow information 98 |
| 99 | Traffic flow information 99 |
Step 102, a service plane management module starts a report timer T; after the report timer T is overtime, the service plane management module selects the corresponding service flow information of a plurality of IP-CAN bearers from the IP-CAN bearer report table by using the indexes of the plurality of IP-CAN bearers, adds the service flow information of the plurality of IP-CAN bearers into the same flow report message, and sends the flow report message to the charging management module.
In the embodiment of the present invention, the reporting timer T is a periodic timer, and the reporting timer T is used to detect an IP-CAN bearer that currently needs to report traffic, and the timeout time of the reporting timer T may be set according to an actual experience value, for example: may be set to 10ms (milliseconds).
In the embodiment of the present invention, after the reporting timer T is overtime, the service plane management module selects corresponding service traffic information of multiple IP-CAN bearers from the IP-CAN bearer reporting table by using indexes of the multiple IP-CAN bearers, adds the service traffic information of the multiple IP-CAN bearers to the same traffic reporting message, and sends the traffic reporting message to the charging management module, which specifically includes but is not limited to the following modes:
step A, a service plane management module judges whether an index of an IP-CAN bearer is recorded in an IP-CAN bearer upper report or not; if yes, executing step B; if not, executing step D.
B, based on all the IP-CAN bearers stored in the IP-CAN bearer report table, the service plane management module selects an index of the IP-CAN bearer from the IP-CAN bearer report table, selects service flow information of the IP-CAN bearer corresponding to the index of the IP-CAN bearer from the IP-CAN bearer report table, and deletes a record corresponding to the index of the IP-CAN bearer from the IP-CAN bearer upper report table; step C is then performed.
The service plane management module CAN randomly select an index of the IP-CAN bearer from the report form on the IP-CAN bearer by traversing all the IP-CAN bearers stored in the local IP-CAN bearer report table, or the service plane management module CAN select an index of the IP-CAN bearer with the smallest index from the IP-CAN bearer report table, or the service plane management module CAN select an index of the IP-CAN bearer with the largest index from the IP-CAN bearer report table.
Step C, the service plane management module adds the service flow information of the IP-CAN load currently selected into the flow reporting message and judges whether the quantity of the IP-CAN load added in the flow reporting message reaches the load number; if yes, executing step D; if not, executing the step A.
The number of bearers is the number of IP-CAN bearers that CAN be carried in the traffic report message, and the number of bearers CAN be determined according to a traffic model, for example, when the processing performance of the PGW is relatively high, the number of bearers is relatively large; when the processing performance of the PGW is low, the number of bearers is relatively small.
And step D, the service plane management module finishes the flow reporting message generation process, and sends the currently generated flow reporting message to the charging management module when the service flow information loaded by the IP-CAN is added in the currently generated flow reporting message. And then, the service plane management module waits for the overtime of the reporting timer T, and continues to execute the step A after the overtime of the reporting timer T at the next time, and so on.
It should be noted that, when the step a is executed for the first time after the reporting timer T times out, if the judgment result is that no index of the IP-CAN bearer is recorded in the IP-CAN bearer reporting table, when the step D is executed, since no service traffic information of the IP-CAN bearer is added to the traffic reporting message at this time, the service plane management module does not need to send the traffic reporting message to the charging management module.
Taking the IP-CAN on-bearer report shown in table 1 as an example, assuming that no charging information corresponding to the IP-CAN bearer satisfies the charging reporting condition after the IP-CAN on-bearer report shown in table 1 is generated, and assuming that the bearer number is 10, after the reporting timer T times out, through the above steps a-D, the traffic surface management module carries the traffic flow information 1 of the IP-CAN bearer 1, the traffic flow information 2 of the IP-CAN bearer 2, the traffic flow information 3 of the IP-CAN bearer 3, the traffic flow information 4 of the IP-CAN bearer 4, the traffic flow information 5 of the IP-CAN bearer 5, the traffic flow information 6 of the IP-CAN bearer 6, the traffic flow information 7 of the IP-CAN bearer 7, the traffic flow information 8 of the IP-CAN bearer 8, the traffic flow information 1 of the IP-CAN bearer, the traffic flow information 2 of the IP-CAN bearer 2, the traffic flow information 3 of the IP-CAN bearer 3, service flow information 9 of an IP-CAN bearer 9 and service flow information 10 of an IP-CAN bearer 10; further, after the above steps a-D, the IP-CAN carries the report form as shown in table 2.
TABLE 2
| Indexing of IP-CAN bearers | IP-CAN borne service flow information |
| 11 | Traffic flow information 11 |
| 12 | Traffic flow information 12 |
| 13 | Traffic flow information 13 |
| .... | ... |
| 98 | Traffic flow information 98 |
| 99 | Traffic flow information 99 |
Based on the IP-CAN bearer upper report shown in Table 2, assuming that no charging information corresponding to the IP-CAN bearer satisfies the charging reporting condition after the IP-CAN bearer upper report shown in Table 2 is generated, after the next reporting timer T is overtime, through the steps A-D, the traffic reporting message sent by the service plane management module to the charging management module carries the traffic information 11 of the IP-CAN bearer 11, the traffic information 12 of the IP-CAN bearer 12, the traffic information 13 of the IP-CAN bearer 13, the traffic information 14 of the IP-CAN bearer 14, the traffic information 15 of the IP-CAN bearer 15, the traffic information 16 of the IP-CAN bearer 16, the traffic information 17 of the IP-CAN bearer 17, and the traffic information 18 of the IP-CAN bearer 18, Service flow information 19 of an IP-CAN bearer 19 and service flow information 20 of an IP-CAN bearer 20; further, after the above steps a-D, the IP-CAN carries the report form as shown in table 3. And by analogy, all the IP-CAN borne service flow information in the report form borne by the IP-CAN is sent to the charging management module by the service plane management module, and the subsequent processing is not repeated in the embodiment of the invention.
TABLE 3
| Indexing of IP-CAN bearers | IP-CAN borne service flow information |
| 21 | Traffic flow information 21 |
| 22 | Traffic flow information 22 |
| 23 | Traffic flow information 23 |
| .... | ... |
| 98 | Traffic flow information 98 |
| 99 | Traffic flow information 99 |
In a specific implementation manner of the embodiment of the present invention, the service plane management module maintains all IP-CAN bearers in a local bearer instance (in the embodiment of the present invention, the local bearer instance is referred to as an IP-CAN bearer upper report), and when charging information corresponding to the IP-CAN bearers satisfies a charging reporting condition, the service plane management module needs to set a bearer identifier (in the embodiment of the present invention, the bearer identifier is referred to as an index of the IP-CAN bearer) for the IP-CAN bearer, and record service traffic information of the IP-CAN bearer in the IP-CAN bearer upper report. As shown in table 4, an example of the report on IP-CAN bearer corresponding to table 1 is shown.
TABLE 4
| IP-CAN bearer | Indexing of IP-CAN bearers | IP-CAN borne service flow information |
| IP-CAN bearer 1 | 1 | Traffic flow information 1 |
| IP-CAN bearer 2 | 2 | Traffic flow information 2 |
| IP-CAN bearer 3 | 3 | Traffic flow information 3 |
| ... | .... | ... |
| IP-CAN bearer 98 | 98 | Traffic flow information 98 |
| IP-CAN bearer 99 | 99 | Traffic flow information 99 |
| IP-CAN bearer 100 | ||
| ... | ||
| IP-CAN bearer 10000 |
In this case, after the service traffic information of the IP-CAN bearer corresponding to the index of the IP-CAN bearer is selected from the IP-CAN bearer reporting table, the index of the IP-CAN bearer and the service traffic information of the IP-CAN bearer need to be deleted from the IP-CAN bearer upper report. Further, if the current flow report message cannot bear all the IP-CAN borne service flow information in the IP-CAN borne report, the service plane management module continues to send the IP-CAN borne service flow information corresponding to the index of the IP-CAN bearing in the IP-CAN borne report through the flow report message after the next report timer T is overtime until all the IP-CAN borne service flow information in the IP-CAN borne report is sent to the charging management module.
And 103, the charging management module generates corresponding CDR for the IP-CAN bearers respectively by using the service flow information of the IP-CAN bearers. Specifically, after receiving the traffic report message, the charging management module performs call ticket processing on the service traffic information of all IP-CAN bearers carried in the traffic report message, so as to generate corresponding respective CDRs for all IP-CAN bearers.
To sum up, when the charging information corresponding to the IP-CAN bearer satisfies the charging reporting condition, the service plane management module does not directly send a traffic reporting message to the charging management module, but records the service traffic information of the IP-CAN bearer in the IP-CAN bearer upper report, so that after the reporting timer T times out, the service traffic information of a plurality of IP-CAN bearers is sent to the charging management module through one traffic reporting message, and the charging management module respectively generates corresponding CDRs for the plurality of IP-CAN bearers by using the service traffic information of the plurality of IP-CAN bearers, thereby reducing the sending number of the traffic reporting message, improving the processing performance of the charging management module, greatly reducing the message processing load of PGW charging, and effectively relieving the processing pressure of the charging system. Furthermore, the processing capability of the PGW may be enhanced, and particularly, the fault tolerance of the PGW may be effectively improved when the PGW fails or is abnormal.
Example two
Based on the same inventive concept as the above method, an embodiment of the present invention further provides a transmission device (e.g., PGW) for reporting a message by using a traffic, where the transmission device includes a service plane management module 11 and a charging management module 12, and as shown in fig. 2, the service plane management module 11 specifically includes:
a determining unit 111, configured to determine that charging information corresponding to an IP-CAN bearer of an IP connectivity access network satisfies a charging reporting condition;
a recording unit 112, configured to record, in an IP-CAN bearer reporting table, a corresponding relationship between an index of the IP-CAN bearer and service traffic information of the IP-CAN bearer when charging information corresponding to the IP-CAN bearer meets a charging reporting condition; wherein, the index of each IP-CAN bearer recorded in the report on the IP-CAN bearer is unique;
a sending unit 113, configured to start a reporting timer T; after the reporting timer T is overtime, selecting the corresponding service traffic information of multiple IP-CAN bearers from the IP-CAN bearer reporting table by using the indexes of the multiple IP-CAN bearers, adding the service traffic information of the multiple IP-CAN bearers to the same traffic reporting message, and sending the traffic reporting message to the charging management module 12; and the charging management module 12 generates corresponding charging data call ticket CDR for the plurality of IP-CAN bearers respectively by using the service flow information of the plurality of IP-CAN bearers.
The determining unit 111 is specifically configured to determine that the charging information corresponding to the IP-CAN bearer meets a charging reporting condition when it is known that the time threshold corresponding to the IP-CAN bearer is reached; or,
when the fact that the flow threshold corresponding to the IP-CAN bearer is reached is known, it is determined that charging information corresponding to the IP-CAN bearer meets charging reporting conditions; or,
when the arrival of the rate change time point corresponding to the IP-CAN bearer is known, determining that the charging information corresponding to the IP-CAN bearer meets the charging reporting condition; or,
when the arrival of the rate group level time threshold corresponding to the IP-CAN bearer is known, determining that the charging information corresponding to the IP-CAN bearer meets the charging reporting condition; or,
and when the arrival of the rate group level flow threshold corresponding to the IP-CAN bearer is known, determining that the charging information corresponding to the IP-CAN bearer meets the charging reporting condition.
The service flow information carried by the IP-CAN specifically includes one or any combination of the following:
the IP-CAN bearing identification information, the system time information when the charging information corresponding to the IP-CAN bearing meets the charging reporting condition, the bearing flow information and the bearing level charging reason information.
The sending unit 113 is specifically configured to send the traffic report message to the charging management module 12 by executing the following steps:
step A, judging whether an index of the IP-CAN bearer is recorded in the report on the IP-CAN bearer; if yes, executing step B; if not, executing the step D;
b, selecting an index of the IP-CAN bearer from the IP-CAN bearer report table, selecting the service flow information of the IP-CAN bearer corresponding to the index of the IP-CAN bearer from the IP-CAN bearer report table, and deleting a record corresponding to the index of the IP-CAN bearer from the report form on the IP-CAN bearer; then, executing step C;
step C, adding the service flow information of the currently selected IP-CAN bearer into a flow reporting message, and judging whether the quantity of the IP-CAN bearers added in the flow reporting message reaches the bearer number; if yes, executing step D; otherwise, executing the step A;
and step D, ending the flow reporting message generation process, and sending the currently generated flow reporting message to the charging management module 12 when the service flow information loaded by the IP-CAN is added in the currently generated flow reporting message.
The service plane management module 11 and the charging management module 12 are located in a packet gateway PGW.
The modules of the device can be integrated into a whole or can be separately deployed. The modules can be combined into one module, and can also be further split into a plurality of sub-modules.
Through the above description of the embodiments, those skilled in the art will clearly understand that the present invention may be implemented by software plus a necessary general hardware platform, and certainly may also be implemented by hardware, but in many cases, the former is a better embodiment. Based on such understanding, the technical solutions of the present invention may be embodied in the form of 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 the methods according to the embodiments of the present invention.
Those skilled in the art will appreciate that the drawings are merely schematic representations of one preferred embodiment and that the blocks or flow diagrams in the drawings are not necessarily required to practice the present invention.
Those skilled in the art will appreciate that the modules in the devices in the embodiments may be distributed in the devices in the embodiments according to the description of the embodiments, and may be correspondingly changed in one or more devices different from the embodiments. The modules of the above embodiments may be combined into one module, or further split into multiple sub-modules.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
The above disclosure is only for a few specific embodiments of the present invention, but the present invention is not limited thereto, and any variations that can be made by those skilled in the art are intended to fall within the scope of the present invention.
Claims (8)
1. A transmission method of a traffic report message is characterized in that the method comprises the following steps:
when the charging information corresponding to the IP-CAN bearer of the IP connection access network meets the charging reporting condition, the service plane management module records the index of the IP-CAN bearer and the corresponding relation between the service flow information of the IP-CAN bearer in an IP-CAN bearer upper report; wherein, the index of each IP-CAN bearer recorded in the report on the IP-CAN bearer is unique;
the service plane management module starts a reporting timer T; after the reporting timer T is overtime, the service plane management module selects corresponding service flow information of a plurality of IP-CAN bearers from the IP-CAN bearer reporting table by using indexes of the plurality of IP-CAN bearers, adds the service flow information of the plurality of IP-CAN bearers into the same flow reporting message, and sends the flow reporting message to a charging management module; the charging management module generates corresponding charging data call ticket CDR for the IP-CAN bearers by utilizing the service flow information borne by the IP-CAN bearers;
the service plane management module selects corresponding service traffic information of multiple IP-CAN bearers from the IP-CAN bearer report table by using indexes of the multiple IP-CAN bearers, adds the service traffic information of the multiple IP-CAN bearers to the same traffic report message, and sends the traffic report message to the charging management module, which specifically comprises:
step A, the service plane management module judges whether an index of the IP-CAN bearer is recorded in the report on the IP-CAN bearer; if yes, executing step B; if not, executing the step D;
b, the service plane management module selects an index of the IP-CAN bearer from the IP-CAN bearer report table, selects service flow information of the IP-CAN bearer corresponding to the index of the IP-CAN bearer from the IP-CAN bearer report table, and deletes a record corresponding to the index of the IP-CAN bearer from the report form of the IP-CAN bearer; then, executing step C;
step C, the service plane management module adds the service flow information of the IP-CAN load currently selected into a flow reporting message and judges whether the quantity of the IP-CAN load added in the flow reporting message reaches the load number; if yes, executing step D; otherwise, executing the step A;
and step D, the service plane management module finishes the flow reporting message generation process, and sends the currently generated flow reporting message to the charging management module when the service flow information loaded by the IP-CAN is added in the currently generated flow reporting message.
2. The method of claim 1, wherein the process of the service plane management module determining that the charging information corresponding to the IP-CAN bearer satisfies the charging reporting condition specifically comprises:
when the service plane management module learns that the time threshold corresponding to the IP-CAN bearer reaches, determining that the charging information corresponding to the IP-CAN bearer meets the charging reporting condition; or,
when the service plane management module learns that the flow threshold corresponding to the IP-CAN bearer reaches, determining that the charging information corresponding to the IP-CAN bearer meets a charging reporting condition; or,
when the service plane management module learns that the rate change time point corresponding to the IP-CAN bearer arrives, determining that the charging information corresponding to the IP-CAN bearer meets the charging reporting condition; or,
when the service plane management module learns that the rate group level time threshold corresponding to the IP-CAN bearer is reached, determining that the charging information corresponding to the IP-CAN bearer meets a charging reporting condition; or,
and when the service plane management module learns that the rate group level flow threshold corresponding to the IP-CAN bearer is reached, determining that the charging information corresponding to the IP-CAN bearer meets the charging reporting condition.
3. The method according to claim 1 or 2, wherein the service traffic information carried by the IP-CAN specifically includes one or any combination of the following:
the IP-CAN bearing identification information, the system time information when the charging information corresponding to the IP-CAN bearing meets the charging reporting condition, the bearing flow information and the bearing level charging reason information.
4. The method of claim 1, wherein the traffic plane management module and the charging management module are located in a Packet Gateway (PGW).
5. A transmission device for reporting message of flow comprises a service plane management module and a charging management module, and is characterized in that the service plane management module specifically comprises:
the determining unit is used for determining that the charging information corresponding to the IP-CAN bearer of the IP connection access network meets the charging reporting condition;
the recording unit is used for recording the corresponding relation between the index of the IP-CAN bearer and the service flow information of the IP-CAN bearer in an IP-CAN bearer upper report when the charging information corresponding to the IP-CAN bearer meets a charging upper report condition; wherein, the index of each IP-CAN bearer recorded in the report on the IP-CAN bearer is unique;
a sending unit, configured to start a reporting timer T; after the reporting timer T is overtime, selecting corresponding service flow information of a plurality of IP-CAN bearers from the IP-CAN bearer reporting table by using indexes of the plurality of IP-CAN bearers, adding the service flow information of the plurality of IP-CAN bearers into the same flow reporting message, and sending the flow reporting message to a charging management module; the charging management module generates corresponding charging data call ticket CDR for the IP-CAN bearers by utilizing the service flow information borne by the IP-CAN bearers;
the sending unit is specifically configured to send the traffic report message to a charging management module by performing the following steps:
step A, judging whether an index of the IP-CAN bearer is recorded in the report on the IP-CAN bearer; if yes, executing step B; if not, executing the step D;
b, selecting an index of the IP-CAN bearer from the IP-CAN bearer report table, selecting the service flow information of the IP-CAN bearer corresponding to the index of the IP-CAN bearer from the IP-CAN bearer report table, and deleting a record corresponding to the index of the IP-CAN bearer from the report form on the IP-CAN bearer; then, executing step C;
step C, adding the service flow information of the currently selected IP-CAN bearer into a flow reporting message, and judging whether the quantity of the IP-CAN bearers added in the flow reporting message reaches the bearer number; if yes, executing step D; otherwise, executing the step A;
and D, ending the flow reporting message generation process, and sending the currently generated flow reporting message to the charging management module when the service flow information loaded by the IP-CAN is added in the currently generated flow reporting message.
6. The apparatus of claim 5,
the determining unit is specifically configured to determine that charging information corresponding to the IP-CAN bearer meets a charging reporting condition when it is known that a time threshold corresponding to the IP-CAN bearer is reached; or,
when the fact that the flow threshold corresponding to the IP-CAN bearer is reached is known, it is determined that charging information corresponding to the IP-CAN bearer meets charging reporting conditions; or,
when the arrival of the rate change time point corresponding to the IP-CAN bearer is known, determining that the charging information corresponding to the IP-CAN bearer meets the charging reporting condition; or,
when the arrival of the rate group level time threshold corresponding to the IP-CAN bearer is known, determining that the charging information corresponding to the IP-CAN bearer meets the charging reporting condition; or,
and when the arrival of the rate group level flow threshold corresponding to the IP-CAN bearer is known, determining that the charging information corresponding to the IP-CAN bearer meets the charging reporting condition.
7. The device according to claim 5 or 6, wherein the service traffic information carried by the IP-CAN specifically includes one or any combination of the following:
the IP-CAN bearing identification information, the system time information when the charging information corresponding to the IP-CAN bearing meets the charging reporting condition, the bearing flow information and the bearing level charging reason information.
8. The apparatus of claim 5, wherein the traffic plane management module and the charging management module are located in a Packet Gateway (PGW).
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310302670.4A CN103384202B (en) | 2013-07-17 | 2013-07-17 | The transmission method and equipment of a kind of flow report message |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310302670.4A CN103384202B (en) | 2013-07-17 | 2013-07-17 | The transmission method and equipment of a kind of flow report message |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103384202A CN103384202A (en) | 2013-11-06 |
| CN103384202B true CN103384202B (en) | 2017-06-13 |
Family
ID=49491904
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310302670.4A Active CN103384202B (en) | 2013-07-17 | 2013-07-17 | The transmission method and equipment of a kind of flow report message |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103384202B (en) |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1735024A (en) * | 2004-08-10 | 2006-02-15 | 华为技术有限公司 | Charging information processing method based on service data flow charge |
| CN1972245A (en) * | 2006-10-24 | 2007-05-30 | 华为技术有限公司 | Method and soft switching for obtaining flow information, gathering flow information in bill |
| CN101127612A (en) * | 2007-09-24 | 2008-02-20 | 中兴通讯股份有限公司 | Consolidation method for manifold billing data records in IP multimedia sub-system |
| CN101127741A (en) * | 2007-09-17 | 2008-02-20 | 中兴通讯股份有限公司 | CDR merging device for billing gateway |
| CN101442733A (en) * | 2008-12-19 | 2009-05-27 | 华为技术有限公司 | Processing method, apparatus and system for charging communication network |
| CN102256231A (en) * | 2011-07-05 | 2011-11-23 | 中兴通讯股份有限公司 | Multi-network element fusion charging method and system, and charging gateway function |
| CN102316432A (en) * | 2010-07-05 | 2012-01-11 | 中兴通讯股份有限公司 | Consumption monitoring method and system |
| CN102511181A (en) * | 2011-11-22 | 2012-06-20 | 华为技术有限公司 | Cell state reporting method and device thereof |
| CN102647698A (en) * | 2012-04-10 | 2012-08-22 | 华为技术有限公司 | Policy and charging control (PCC) system and method |
| US8305922B2 (en) * | 2010-02-18 | 2012-11-06 | Alcatel Lucent | Method for PCRF to autonomously respond to cell capacity shortage |
| CN102868988A (en) * | 2011-07-05 | 2013-01-09 | 中国电信股份有限公司 | Policy charging control-based business processing method and system in wireless network |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101309153B (en) * | 2008-06-23 | 2012-02-29 | 华为技术有限公司 | Service process method of multiple service streams and access service network gateway and charging server |
| CN102202281B (en) * | 2010-03-24 | 2015-05-13 | 中兴通讯股份有限公司 | Ticket processing method and system |
| CN103188645A (en) * | 2011-12-29 | 2013-07-03 | 北京信威通信技术股份有限公司 | Base station data service charging method used for flat network architecture |
-
2013
- 2013-07-17 CN CN201310302670.4A patent/CN103384202B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1735024A (en) * | 2004-08-10 | 2006-02-15 | 华为技术有限公司 | Charging information processing method based on service data flow charge |
| CN1972245A (en) * | 2006-10-24 | 2007-05-30 | 华为技术有限公司 | Method and soft switching for obtaining flow information, gathering flow information in bill |
| CN101127741A (en) * | 2007-09-17 | 2008-02-20 | 中兴通讯股份有限公司 | CDR merging device for billing gateway |
| CN101127612A (en) * | 2007-09-24 | 2008-02-20 | 中兴通讯股份有限公司 | Consolidation method for manifold billing data records in IP multimedia sub-system |
| CN101442733A (en) * | 2008-12-19 | 2009-05-27 | 华为技术有限公司 | Processing method, apparatus and system for charging communication network |
| US8305922B2 (en) * | 2010-02-18 | 2012-11-06 | Alcatel Lucent | Method for PCRF to autonomously respond to cell capacity shortage |
| CN102316432A (en) * | 2010-07-05 | 2012-01-11 | 中兴通讯股份有限公司 | Consumption monitoring method and system |
| CN102256231A (en) * | 2011-07-05 | 2011-11-23 | 中兴通讯股份有限公司 | Multi-network element fusion charging method and system, and charging gateway function |
| CN102868988A (en) * | 2011-07-05 | 2013-01-09 | 中国电信股份有限公司 | Policy charging control-based business processing method and system in wireless network |
| CN102511181A (en) * | 2011-11-22 | 2012-06-20 | 华为技术有限公司 | Cell state reporting method and device thereof |
| CN102647698A (en) * | 2012-04-10 | 2012-08-22 | 华为技术有限公司 | Policy and charging control (PCC) system and method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103384202A (en) | 2013-11-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3214861B1 (en) | Method, device and system for detecting fraudulent user | |
| EP3890240B1 (en) | User plane function method, user plane function entity, computer program and system | |
| US9602382B2 (en) | Dynamic reaction to diameter routing failures | |
| CN109818816B (en) | VoLTE calling time delay analysis method and device | |
| CN102870445B (en) | A kind of identify that network shares the method for behavior, node, mobile terminal and system | |
| EP2512176A1 (en) | Congestion control method, operations maintenance center and base station | |
| US20090111382A1 (en) | Methods for scheduling collection of key performance indicators from elements in a communications network | |
| US20080183604A1 (en) | Operation support system for wireless networks | |
| CN103517245B (en) | A kind of charging method and system of D2D communications | |
| CN102868988B (en) | Based on the method for processing business of policy and charging control and system in wireless network | |
| CN107872503B (en) | Firewall session number monitoring method and device | |
| CN102612165B (en) | Method and device for releasing resource | |
| US11075989B2 (en) | Cellular network hierarchical operational data storage | |
| CN110072251B (en) | Method and device for analyzing user communication behavior and managing user | |
| US20190036793A1 (en) | Network service implementation method, service controller, and communications system | |
| WO2011025424A1 (en) | Handling alarms based on user session records | |
| EP2571314A1 (en) | Method and apparatus for inter-system reselection frequency statistics | |
| CN108024222B (en) | Traffic ticket generating method and device | |
| CN103384202B (en) | The transmission method and equipment of a kind of flow report message | |
| CN114710801B (en) | Processing method and device of evaluation parameters of network performance, storage medium and equipment | |
| JP2017521933A (en) | Message processing method and apparatus | |
| CN113411828B (en) | Method, device, equipment and computer readable storage medium for sensing call quality | |
| CN103401700A (en) | Processing method and equipment of frequency shake alarm | |
| CN105188043A (en) | Method, device and system for charging based on PDN connection | |
| CN108243013A (en) | A kind of method and device of charge on traffic |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |