WO2014166405A1 - 一种基于OpenFlow协议的计费的方法及系统 - Google Patents
一种基于OpenFlow协议的计费的方法及系统 Download PDFInfo
- Publication number
- WO2014166405A1 WO2014166405A1 PCT/CN2014/075062 CN2014075062W WO2014166405A1 WO 2014166405 A1 WO2014166405 A1 WO 2014166405A1 CN 2014075062 W CN2014075062 W CN 2014075062W WO 2014166405 A1 WO2014166405 A1 WO 2014166405A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- charging
- openflow
- billing
- flow
- data
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 72
- 238000013480 data collection Methods 0.000 claims abstract description 8
- 238000004891 communication Methods 0.000 abstract description 9
- 238000010295 mobile communication Methods 0.000 abstract description 5
- 230000006870 function Effects 0.000 description 27
- 230000008569 process Effects 0.000 description 13
- 238000010586 diagram Methods 0.000 description 10
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 208000001048 Oculocerebrocutaneous syndrome Diseases 0.000 description 1
- 206010033799 Paralysis Diseases 0.000 description 1
- 230000003213 activating effect Effects 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 235000014510 cooky Nutrition 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000003780 insertion Methods 0.000 description 1
- 230000037431 insertion Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 238000010977 unit operation Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1403—Architecture for metering, charging or billing
- H04L12/1407—Policy-and-charging control [PCC] architecture
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/65—Off-line charging system
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1403—Architecture for metering, charging or billing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/20—Traffic policing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/82—Criteria or parameters used for performing billing operations
- H04M15/8228—Session based
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/34—Signalling channels for network management communication
- H04L41/342—Signalling channels for network management communication between virtual entities, e.g. orchestrators, SDN or NFV entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/66—Policy and charging system
Definitions
- the present invention relates to the field of communications technologies, and in particular, to a method and system for charging based on an OpenFlow protocol (an interface protocol between a routing control plane and a data plane).
- OpenFlow protocol an interface protocol between a routing control plane and a data plane.
- a routing protocol is run in a traditional router, such as an Open Shortest Path First (OSPF) protocol.
- OSPF Open Shortest Path First
- a routing protocol can generate a routing table based on network topology information, and the routing table is the basis of routing forwarding. Since the routing protocol needs to know the information of all nodes or subnets on the network, the routing table is very large. With the development of the network, the rapid expansion of the routing table will bring about the problem of route convergence. When a router in a network, especially a router of a critical node, fails, the whole network may be paralyzed, resulting in an important technology of the network. The reason is that the traditional router relies on the routing protocol such as OSPF. It can only select one optimal route.
- OSPF Open Shortest Path First
- SDN software-defined networking
- the basic idea is to separate the control from the bearer. All the intelligence is concentrated on the control plane, and the bearer layer only forwards. And accept control of the control layer.
- SDN itself defines a network architecture, which mainly includes three parts: the basic network layer, the control layer, and the application layer.
- the basic network layer mainly includes routing and forwarding devices. Since the currently standardized interface between the control layer and the underlying network layer adopts the OpenFlow protocol, the device at the base network layer is called an OpenFlow switch.
- OpenFlow is a network-programmable mechanism that performs topology management through the OpenFlow controller at the control layer, and rewrites the forwarding table of the OpenFlow switch through the OpenFlow interface to redefine the path of the data stream.
- the extension of the OpenFlow protocol in the prior art is not sufficient. Summary of the invention
- a method and a system for charging based on the OpenFlow protocol are provided, which can meet the charging requirement.
- a method for charging based on an OpenFlow protocol including:
- the interface protocol between the routing control plane and the data plane receives the session request by the OpenFlow switch; [08] According to a preset charging rule, the OpenFlow switch collects charging data for the session by using a charging parameter obtained by the OpenFlow interface.
- the OpenFlow switch sends the collected charging data to a charging system, so that the charging system performs charging according to the charging data.
- the OpenFlow switch sends the collected charging data to a charging system, including:
- the OpenFlow switch sends the collected charging data to an OpenFlow controller, and the charging data is sent to the charging system by using the OpenFlow controller.
- the charging parameter includes:
- the OpenFlow switch is configured according to a pre-acquisition
- the fee parameter collects billing data for the session, including:
- the OpenFlow switch adds the charging parameter of the session to the charging ID of the session and the ID of the flow to be charged according to the charging ID of the session and the ID of the flow to be charged.
- different users correspond to different charging IDs; each charging ID corresponds to one charging table, or each charging ID corresponds to multiple charging tables and each of the same charging IDs
- a flow ID corresponds to a billing table.
- the billing table includes at least the following fields:
- the OpenFlow switch is an OpenFlow wireless access device or an OpenFlow gateway router.
- the second aspect provides a system for charging based on the OpenFlow protocol, including an OpenFlow controller, an OpenFlow switch, and a charging subsystem.
- the OpenFlow controller is configured to send a charging parameter to the OpenFlow switch according to a preset charging rule.
- the OpenFlow switch is configured to receive a session request, perform charging data collection on the session according to the charging parameter sent by the OpenFlow controller, and send the collected charging data to the charging.
- the charging subsystem is configured to perform charging according to charging data sent by the OpenFlow switch.
- the charging parameter includes:
- the OpenFlow switch is specifically configured to use the charging ID and the required charging according to the session.
- the ID of the stream, the charging parameter of the session is added to the charging table corresponding to the charging ID of the session and the ID of the stream to be charged, wherein different users correspond to different charging IDs;
- One billing ID corresponds to one billing table, or each billing ID corresponds to multiple billing tables, and each stream ID under the same billing ID corresponds to one billing table.
- the charging table includes at least the following Field:
- the OpenFlow switch is an OpenFlow wireless access device or an OpenFlow gateway router.
- a system for charging based on OpenFlow protocol including an OpenFlow controller, an OpenFlow switch, and a charging subsystem, is also provided.
- the OpenFlow controller is configured to send a charging parameter to the OpenFlow switch, and send the charging data collected by the OpenFlow switch to the charging subsystem;
- the OpenFlow switch is configured to receive a session request, perform charging data collection on the session according to the charging parameter sent by the OpenFlow controller, and send the collected charging data to the OpenFlow controller. ;
- the charging subsystem is configured to perform charging according to charging data sent by the OpenFlow controller.
- the charging parameter includes:
- the OpenFlow switch is specifically configured to perform charging according to the charging ID of the session and the required charging.
- the ID of the stream, the charging parameter of the session is added to the charging table corresponding to the charging ID of the session and the ID of the stream to be charged, wherein different users correspond to different charging IDs;
- One billing ID corresponds to one billing table, or each billing ID corresponds to multiple billing tables, and each stream ID under the same billing ID corresponds to one billing table.
- the charging table includes at least the following Field:
- the OpenFlow switch is an OpenFlow wireless access device or an OpenFlow gateway router.
- the embodiment of the present invention implements the application of the OpenFlow protocol in an operator, especially a mobile communication network, by adding a charging function based on an OpenFlow interface and an OpenFlow switch, so that OpenFlow can be used in a communication network to adapt The new architecture and features of the future mobile network.
- FIG. 1 is a flowchart of a method for charging based on the OpenFlow protocol according to an embodiment of the present invention
- FIG. 2 is a flow chart of charging an immediate event according to an embodiment of the present invention
- FIG. 3 is a flowchart of session charging based on unit reservation in an embodiment of the present invention.
- FIG. 4 is a schematic diagram of a charging table according to an embodiment of the present invention.
- FIG. 5a is a schematic diagram of an OpenFlow flow table defined in the prior art;
- FIG. 5b is a schematic diagram of an OpenFlow flow table according to an embodiment of the present invention
- FIG. 5c is a schematic diagram of a charging field in the OpenFlow flow table shown in FIG. 5b
- FIG. 6 is based on an embodiment of the present invention.
- FIG. 7 is a schematic structural diagram of another system based on the OpenFlow protocol for charging according to an embodiment of the present invention
- FIG. 8 is another OpenFlow protocol according to an embodiment of the present invention.
- FIG. 9 is a schematic structural diagram of another system for charging based on the OpenFlow protocol according to an embodiment of the present invention.
- the "stream” in the embodiment of the present invention refers to a plurality of data packets sent or received from one node, and generally classifies data packets having the same type of characteristics into one stream.
- FIG. 1 is a flowchart of a method for charging according to an OpenFlow protocol according to an embodiment of the present invention. [55] The method can include:
- Step 101 The OpenFlow switch receives the session request.
- the OpenFlow switch can be an OpenFlow gateway router or an OpenFlow wireless access device that supports OpenFlow function.
- the OpenFlow gateway router is mainly responsible for collecting outgoing user data
- the OpenFlow wireless access device is mainly responsible for communication between users in the mobile system. Data collection. The next step is performed when the OpenFlow switch receives the session request.
- Step 102 According to a preset charging rule, the OpenFlow switch collects charging data for the session by using a charging parameter obtained by the OpenFlow interface.
- the charging control information is controlled by a Policy and Charging Rule Function (PCRF).
- PCRF Policy and Charging Rule Function
- the OpenFlow protocol is required to support the meter. Fee parameter control. That is, it is necessary to preset a charging rule that can communicate between the PCRF and the OpenFlow switch.
- Charging-Rul e-Instal l Used to activate, install, and modify billing rules.
- Charging-Rul e-Remove Used to deactivate or delete the charging rules.
- Charging-Rul e-Report Used to report the status of charging rules, including whether the rules are successfully installed, deleted, modified, etc.
- the charging parameters of the OpenFlow can be sent to the OpenFlow switch through the OpenFlow interface by the controller, for example, the OpenFlow controller.
- the charging parameters can include:
- Billing method Online billing or offline billing
- Billing type Is it flow meter or time billing?
- Fees How much traffic or duration can be used.
- Billing data reporting mode Timed report or event trigger. If it is an event trigger, you need to define the trigger event. The timed report needs to determine the time interval, start time, and so on.
- the charging parameter may also be set according to a specific charging rule, which is not specifically limited herein.
- Step 103 The OpenFlow switch sends the collected charging data to the charging system, so that the charging system performs charging according to the charging data.
- the OpenFlow switch can send the charging data to the charging system in multiple manners based on different architectures.
- the billing system may be an On-line Charging System (OCS) or an offline billing system (OFCS).
- OCS On-line Charging System
- OFCS offline billing system
- the OpenFlow switch when an event requirement is met in the charging process, the OpenFlow switch needs to report the current state, and the OpenFlow controller may be reported when the user fee reaches a certain limit. Determine further actions.
- the embodiment of the present invention implements the application of the OpenFlow protocol in an operator, especially a mobile communication network, by adding a charging function based on an OpenFlow interface and an OpenFlow switch, so that OpenFlow can be used in a communication network to adapt to the future.
- the process in which the OpenFlow switch sends the collected charging data to the charging system may be in two ways:
- the OpenFlow switch directly sends the charging data to the charging system through the interface of the traditional charging system between the OpenFlow switch and the charging system.
- the OpenFlow switch needs to add the interface of the traditional billing system. BP needs to preset the billing rules that can communicate between the PCRF and the OpenFlow switch. After the OpenFlow switch obtains the billing data, the billing data can be sent to the billing system through the traditional interface.
- the collected billing data is sent by the OpenFlow switch to the OpenFlow controller through the OpenFlow interface, and the billing data is sent to the billing system through the OpenFlow controller.
- the interface of the traditional charging system is not required, and the OpenFlow interface can be used for charging control. Since the OpenFlow protocol interface supports many status and statistics reporting of OpenFlow, the OpenFlow interface can be extended to support the charging function. After the OpenFlow switch obtains the charging data, the charging data can be obtained through the extended OpenFlow interface. The data is sent to the OpenFlow controller, and the billing data is sent to the billing system by the OpenFlow controller.
- the interface of the second mode is more single, and the gateway function can be well compatible with the OpenFlow switch without additional interface support.
- the OpenFlow controller (or network controller) needs to be exchanged with the billing system to implement billing control.
- the OpenFlow interface needs to support the Credit (Account) request function.
- the OpenFlow interface needs to support several scenarios of Diameter: immediate event charging, event charging based on unit reservation, and session charging based on unit reservation (refer to 3GPP 32. 299 for details).
- it is an charging process of an immediate event.
- the OpenFlow access node/gateway node receives the service request in step 1, in the reserved unit operation, in step 2, OpenFlow is connected.
- the ingress/gateway node sends a Credit Control Request to the PCRF/OpenFlow controller.
- the Credit request is mainly used for request control, and the response message of the PCRF/OpenFlow controller in Step 3 contains the authorized service unit, price information, and remaining account information.
- Step 5 is when the OpenFlow access node/gateway node terminates the session.
- the initiated Credi t control request carries the quantity information used in the request so that the billing system can perform billing.
- Step 6 is the feedback information of the PCRF/OpenFlow controller, including the fee information, the remaining accounts, and the like.
- the event charging process based on unit reservation is the same as the process of immediate event, except that the message type is different.
- the session charging process based on unit reservation is as follows:
- step 3 will include parameters to control user account fees, such as Val i di ty-Time parameters and Low-Balance-Indication parameters.
- the OpenFlow wireless access point and the gateway router need to send an update request to the charging system to report the used time or amount of data.
- the billing system returns a new authorization service unit, rate information, and new bill balance information.
- Step 10 includes rate information and new billing balance information.
- the OpenFlow protocol can support the parameters and processes related to the above process.
- the specific parameters that need to be supported are as follows: [87] Request Type: Includes initial request, update request, and termination request.
- Unit information used such as effective time, amount of data, etc.
- Authorized service unit Information such as time, amount of data, etc. that can be used.
- the process of collecting the charging data of the session by the OpenFlow switch according to the charging parameter sent by the OpenFlow controller may specifically include:
- the OpenFlow switch adds the charging parameter of the session to the charging table corresponding to the charging ID of the session and the ID of the flow to be charged according to the charging ID of the session and the ID of the flow to be charged. .
- each charging ID may correspond to one charging table, or each charging ID may correspond to multiple charging tables, and each of the same charging IDs
- a flow ID corresponds to a billing table.
- Method 1 For a billing user, there may be multiple streams. For example, the QoS class of each stream may be different. Therefore, there are cases where multiple flows are charged by the same meter.
- the billing table may include the following fields: billing ID, stream ID/stream information, billing method, stream type, counter, and the like.
- the charging table may also include other fields or partial fields in the above fields, and the order of the fields in the accounting table is not limited to that shown in FIG.
- Billing ID The identification number of the OpenFlow switch that uniquely identifies the user's billing information, used for user division. Required field, recommended field length 32 bits.
- Flow ID (or flow information): Since each flow table entry in each flow table in the current OpenFlow switch does not contain ID information, if you want to be able to distinguish each flow, you need to assign one for each flow. ID to identify the flow. If the OpenFlow switch supports/adds this function, the flow ID can be used to distinguish the flow. Otherwise, stream matching is required to match the stream.
- the flow information refers to the information about the service flow, including the source IP address of the service flow, the destination IP address, the far TCP port, the destination TCP port, and the service layer information, and even the lower layer VLAN, MPLS label, and the like. Fee configuration requirements.
- Charging mode The charging that identifies the flow is based on time-based charging or traffic-based charging. Even if the flow of the Unified Classify ID (QCI) is different, the billing method is different. Then, different billing information needs to be collected.
- QCI Unified Classify ID
- Flow Category Used to identify the QoS Class (QCI) to which the flow belongs.
- QCI QoS Class
- 3GPP LTE defines nine different categories of services. In the actual charging, different types of services may adopt the same charging mode. This field is mainly used for the statistical reference of the accounting server when generating charging information.
- Counter The counter is mainly used to collect statistics on the stream, and obtain the statistics of the stream.
- the unit may be time or number of bytes, depending on the billing method.
- Trigger is mainly used to trigger the billing report.
- the OpenFlow switch needs to be triggered to report the billing parameters to the billing server. This The parameters may not be included in the table, but there must be other places in the switch to implement the trigger function.
- the switch needs to implement billing configuration information for each stream, including the trigger duration of the billing report, the flow unit, and the like.
- a billing ID corresponds to the billing entries of multiple streams, and the billing entry of each stream can support operations such as inserting, deleting, activating, and deactivating.
- the OpenFlow switch sends a request (credi t control request) message to the charging system.
- Method 2 Each user corresponds to a charging ID, and each flow is configured with an accounting table, and the relationship between each flow table is not associated. That is, each billing ID corresponds to multiple billing tables, and each stream ID under the same billing ID corresponds to one billing table.
- a billing table For example, when defining a billing table, a certain type of service can define a billing flow table. Therefore, a user can have multiple billing flow tables, and each flow table corresponds to a different type of service.
- a user can also have only one flow table, and the billing data of different services is counted by different counters in the table, which is convenient for user information management and the like.
- the billing table can be integrated into the OpenFlow stream table as a direct embedded billing function.
- Figure 5a shows the format of an OpenFlow flow table defined in the prior art, which may include a matching field ( Match Fi eld ). Priority (Priori ty), Counter (Counters), indications (instructions), timeouts (Timeouts), sessions Cache (Cooki es) and so on.
- the OpenFlow flow table may be as shown in FIG. 5b, and the Charging field is added to the original OpenFlow flow table.
- the location of the charging field in FIG. 5b is only an example, and Variety. Specifically, the charging field may further include a field as shown in FIG.
- the charging field may further include other fields or the foregoing FIG. 5c. Some of the fields in the field are shown, and the order in which the fields are arranged in the table is not limited to that shown in Fig. 5c.
- the field contains a stream ID that uniquely identifies the billing stream, if The OpenFlow flow table itself adds the stream ID function, and this field can be omitted.
- the OpenFlow controller or the billing system is required to associate the billing stream and the user by itself, and the stream is mapped to each user. If a user has multiple streams at the same time, each stream independently triggers the accounting statistics report. [114] Adding the above new meter function to the OpenFlow switch makes it easier to implement billing data collection and statistics.
- FIG. 6 is a schematic structural diagram of a system for charging based on the OpenFlow protocol according to an embodiment of the present invention.
- the system can include an OpenFlow controller 601, an 0penFlow switch 602, and a billing subsystem 603.
- the OpenFlow controller 601 is configured to send a charging parameter to the OpenFlow switch 602 according to a preset charging rule.
- the OpenFlow switch 602 is configured to receive a session request, perform charging data collection on the session according to the charging parameter sent by the OpenFlow controller 601, and send the collected charging data to the charging.
- the charging subsystem 603 is configured to perform charging according to the charging data sent by the OpenFlow switch 602.
- the charging control information is controlled by a Policy and Charging Rule Function (PCRF), in the embodiment of the present invention, There is no direct interface between the PCRF and the OpenFlow switch.
- PCRF Policy and Charging Rule Function
- the policy control is performed on the flow table control of the OpenFlow.
- the OpenFlow protocol is required to support the charging parameter control.
- Gp a charging rule that can communicate with the PCRF and OpenFlow switches is required.
- Charging-Rul e-Instal l Used to activate, install, and modify billing rules.
- Charging-Rule-Remove Used to deactivate or delete charging rules.
- Charging-Rule-Report Used to report the status of charging rules, including whether the rules are successfully installed, deleted, modified, etc.
- the charging parameters of the OpenFlow can be sent to the OpenFlow switch through the OpenFlow interface by the controller, for example, the OpenFlow controller.
- the charging parameters may include:
- Billing method online billing or offline billing
- Billing type Whether it is flow metering or time billing
- Fee amount How much traffic or duration can be used.
- Billing data reporting mode Timing report or event triggering. If it is an event trigger, you need to define the trigger event. The timing report needs to determine the time interval, start time, and so on.
- the charging parameter may also be set according to a specific charging rule, which is not specifically limited herein.
- the application of the OpenFlow protocol in an operator is implemented by adding a charging function on the basis of an OpenFlow switch, which greatly simplifies the complexity of the current mobile gateway and adapts to future mobility. New architecture and features of the network.
- the OpenFlow switch may include an OpenFlow radio accessor 701 and an OpenFlow gateway router 702, and the billing subsystem may include 0FCS 703 and 0CS 704.
- the OpenFlow wireless access device 701 is provided with an interface of a traditional charging system, and the OpenFlow wireless accessor 701 is simultaneously connected to the 0FCS 703 and the 0CS 704 through the traditional interface, and is mainly responsible for communication between users in the mobile system. Collection of data.
- the OpenFlow gateway router 702 is also provided with an interface of the traditional billing system.
- the OpenFlow gateway router 702 is also connected to the 0FCS 703 and the 0CS 704 through the conventional interface, and is mainly responsible for collecting the outgoing user data.
- the PCRF can be located in the OpenFlow controller through OpenFlow.
- the controller sends the charging parameter to the OpenFlow wireless access device 701 and the OpenFlow gateway router 702.
- the charging parameter may include: the identifier information ID of the stream to be charged, the flow information, the charging mode, and the charging type. , fee amount, billing data reporting method.
- the OpenFlow wireless accessor 701 or the OpenFlow gateway router 702 can collect the charging data according to the charging parameter sent by the OpenFlow controller, and then The collected charging data is sent to the 0FCS 703 or the 0CS 704 through the interface of the traditional charging system, and is charged by the 0FCS 703 or the 0CS 704.
- the foregoing OpenFlow switch such as an OpenFlow wireless access device and an OpenFlow gateway router, may internally set an accounting table, and after collecting charging data, may be based on the charging ID of the session. And the ID of the flow to be charged, adding the charging parameter of the session to the charging table corresponding to the charging ID of the session and the ID of the flow to be charged, wherein different users correspond to different accounting Fee ID;
- Each billing ID corresponds to one billing table, or each billing ID corresponds to multiple billing tables, and each stream ID under the same billing ID corresponds to one billing table.
- Fields can also be included in the billing table: billing method, stream category, counter.
- FIG. 8 is a schematic structural diagram of another system for charging based on the OpenFlow protocol according to an embodiment of the present invention.
- the system may also include an OpenFlow controller 801, an OpenFlow switch 802, and a billing subsystem 803.
- the OpenFlow controller 801 is configured to send a charging parameter to the OpenFlow switch 802 according to a preset charging rule, and send the charging data collected by the OpenFlow switch 802 to the charging subsystem 803. ;
- the OpenFlow switch 802 is configured to receive a session request, perform charging data collection on the session according to the charging parameter sent by the OpenFlow controller 801, and send the collected charging data to the OpenFlow control. 801;
- the charging subsystem 803 is configured to perform charging according to the charging data sent by the OpenFlow controller 801.
- the embodiment of the present invention implements the application of the OpenFlow protocol in an operator, especially a mobile communication network, by adding a charging function on the basis of an OpenFlow switch, which greatly simplifies the complexity of the current mobile gateway and adapts to future mobility. New architecture and features of the network.
- the OpenFlow switch may include an OpenFlow radio accessor 901 and an OpenFlow gateway router 902, and the billing subsystem may include an OFDMS 903 and an OCCS 904.
- the policy control is performed on the flow table control of the OpenFlow.
- the OpenFlow protocol is required to support the charging parameters. control.
- the PCRF may be located in the OpenFlow controller, and the charging parameter is sent to the OpenFlow wireless access device 901 and the OpenFlow gateway router 902 by using the OpenFlow controller.
- the charging parameter may include: an identifier information ID of the flow to be charged and Flow information, billing method, billing type, fee amount, and billing data reporting method.
- a functional unit is also required in the OpenFlow controller to perform interaction with the billing subsystems 0FCS 903 and 0CS 904, while enabling interaction with OpenFlow devices.
- Both the OpenFlow Wireless Accessor 901 and the OpenFlow Gateway Router 902 are connected to the OpenFlow Controller via the OpenFlow interface.
- the OpenFlow wireless accessor 901 or the OpenFlow gateway router 902 can collect the charging data according to the charging parameter sent by the OpenFlow controller, and then The collected charging data is sent to the OpenFlow controller through the OpenFlow interface, and then the charging data is sent to the 0FCS 903 or the 0CS 904 by the OpenFlow controller, and the charging is performed by the 0FCS 903 or the 0CS 904.
- the foregoing OpenFlow switch such as an OpenFlow wireless access device and an OpenFlow gateway router, may internally set an accounting table, and after collecting charging data, may be based on the charging ID of the session. And the ID of the flow to be charged, adding the charging parameter of the session to the charging table corresponding to the charging ID of the session and the ID of the flow to be charged, wherein different users correspond to different accounting Fee ID;
- Each billing ID corresponds to one billing table, or each billing ID corresponds to multiple billing tables, and each stream ID under the same billing ID corresponds to one billing table.
- the billing table may also include fields: billing ID, stream ID, billing method, stream type, counter. For the specific content and setting of the charging table, refer to the corresponding description of the foregoing method embodiments.
- the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple networks. On the unit. Some or all of the units may be selected according to actual needs to achieve the objectives of the solution of the embodiment.
- each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
- the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
- the technical solution of the present invention which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
- the instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to perform all or part of the steps of the methods described in various embodiments of the present invention.
- the foregoing storage medium includes: a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, and the like, which can store program codes. .
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Charge And Discharge Circuits For Batteries Or The Like (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Meter Arrangements (AREA)
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP14782320.7A EP2975869A4 (en) | 2013-04-10 | 2014-04-10 | LOADING METHOD AND SYSTEM BASED ON THE OPENFLOW PROTOCOL |
KR1020157031840A KR20150139941A (ko) | 2013-04-10 | 2014-04-10 | 오픈플로우 프로토콜 기반의 과금 방법 및 시스템 |
US14/879,725 US20160036597A1 (en) | 2013-04-10 | 2015-10-09 | Openflow-Protocol-Based Charging Method and System |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201310123149.4A CN104104520A (zh) | 2013-04-10 | 2013-04-10 | 一种基于OpenFlow协议的计费的方法及系统 |
CN201310123149.4 | 2013-04-10 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/879,725 Continuation US20160036597A1 (en) | 2013-04-10 | 2015-10-09 | Openflow-Protocol-Based Charging Method and System |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2014166405A1 true WO2014166405A1 (zh) | 2014-10-16 |
Family
ID=51672345
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2014/075062 WO2014166405A1 (zh) | 2013-04-10 | 2014-04-10 | 一种基于OpenFlow协议的计费的方法及系统 |
Country Status (5)
Country | Link |
---|---|
US (1) | US20160036597A1 (zh) |
EP (1) | EP2975869A4 (zh) |
KR (1) | KR20150139941A (zh) |
CN (1) | CN104104520A (zh) |
WO (1) | WO2014166405A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20170126975A (ko) * | 2015-03-04 | 2017-11-20 | 알까뗄 루슨트 | Sdn 네트워크에서 데이터 흐름에 대해 과금하는 방법, 장치 및 시스템 |
Families Citing this family (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104301881B (zh) * | 2014-10-22 | 2018-09-25 | 中国联合网络通信集团有限公司 | 一种计费的方法和计费装置 |
CN104378214A (zh) * | 2014-11-14 | 2015-02-25 | 杭州华三通信技术有限公司 | 流量计费方法及装置 |
CN105812330B (zh) * | 2014-12-31 | 2019-11-12 | 中国电信股份有限公司 | 蜂窝网络系统、控制方法、装置和网元及集中控制器 |
CN105871964B (zh) | 2015-01-23 | 2020-08-07 | 中兴通讯股份有限公司 | 用户设备ue处理方法及装置 |
CN106034296A (zh) * | 2015-03-09 | 2016-10-19 | 中兴通讯股份有限公司 | 一种实现在线计费的方法及系统 |
CN106712987A (zh) * | 2015-08-12 | 2017-05-24 | 中兴通讯股份有限公司 | 网络控制的处理方法、装置及软件定义网络系统 |
EP3338407A1 (en) | 2015-10-20 | 2018-06-27 | Huawei Technologies Co., Ltd. | Forwarding unit and controller unit for sdn |
EP3358865B1 (en) * | 2015-11-20 | 2021-04-07 | Huawei Technologies Co., Ltd. | Charging methods, forwarding plane network element and charging system |
CN105450668A (zh) * | 2015-12-30 | 2016-03-30 | 中电长城网际系统应用有限公司 | 云安全服务实现系统和云安全服务实现方法 |
CN108352994B (zh) * | 2016-03-14 | 2020-08-25 | 华为技术有限公司 | 一种计费测量的方法、装置及系统 |
CN107404435B (zh) * | 2016-05-19 | 2021-10-15 | 中兴通讯股份有限公司 | 一种管理组表项的方法和装置 |
CN110572270B (zh) | 2016-09-14 | 2020-08-21 | 华为技术有限公司 | 一种计费的方法、装置和系统 |
CN109274507B (zh) * | 2017-07-17 | 2020-07-14 | 华为技术有限公司 | 计费控制方法、设备及系统 |
US11388056B2 (en) * | 2018-05-17 | 2022-07-12 | Nippon Telegraph And Telephone Corporation | Information management system and information management method |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1741558A (zh) * | 2004-08-23 | 2006-03-01 | 华为技术有限公司 | 一种通话费用的计费方法 |
CN1859528A (zh) * | 2005-05-08 | 2006-11-08 | 上海粱江通信软件有限公司 | 一种实现通信网准实时计费的系统及方法 |
CN101998340A (zh) * | 2009-08-25 | 2011-03-30 | 中兴通讯股份有限公司 | 一种本地ip访问的计费方法及系统 |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101132405A (zh) * | 2006-08-21 | 2008-02-27 | 华为技术有限公司 | 提供业务代理功能的通信网络系统和方法及业务代理装置 |
US8023926B2 (en) * | 2008-02-16 | 2011-09-20 | Alcatel Lucent | Offline charging for sessions over a 3GPP network and a WLAN access network |
ATE541385T1 (de) * | 2008-03-25 | 2012-01-15 | Ericsson Telefon Ab L M | Richtlinien- und vergebührungssteuerarchitektur |
JPWO2011040511A1 (ja) * | 2009-09-30 | 2013-02-28 | 日本電気株式会社 | 課金処理システム、ネットワークスイッチ、ネットワーク管理サーバ、課金処理方法、及び課金処理プログラム |
EP2596604A4 (en) * | 2010-07-23 | 2016-06-08 | Nec Corp | COMMUNICATION SYSTEM, NODE, STATISTICAL DATA COLLECTION DEVICE, STATISTICAL DATA COLLECTION METHOD, AND PROGRAM |
US9398492B2 (en) * | 2012-06-14 | 2016-07-19 | Tekelec, Inc. | Methods, systems, and computer readable media for providing policy and charging rules function (PCRF) with integrated openflow controller |
-
2013
- 2013-04-10 CN CN201310123149.4A patent/CN104104520A/zh active Pending
-
2014
- 2014-04-10 EP EP14782320.7A patent/EP2975869A4/en not_active Withdrawn
- 2014-04-10 WO PCT/CN2014/075062 patent/WO2014166405A1/zh active Application Filing
- 2014-04-10 KR KR1020157031840A patent/KR20150139941A/ko not_active Application Discontinuation
-
2015
- 2015-10-09 US US14/879,725 patent/US20160036597A1/en not_active Abandoned
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1741558A (zh) * | 2004-08-23 | 2006-03-01 | 华为技术有限公司 | 一种通话费用的计费方法 |
CN1859528A (zh) * | 2005-05-08 | 2006-11-08 | 上海粱江通信软件有限公司 | 一种实现通信网准实时计费的系统及方法 |
CN101998340A (zh) * | 2009-08-25 | 2011-03-30 | 中兴通讯股份有限公司 | 一种本地ip访问的计费方法及系统 |
Non-Patent Citations (1)
Title |
---|
See also references of EP2975869A4 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20170126975A (ko) * | 2015-03-04 | 2017-11-20 | 알까뗄 루슨트 | Sdn 네트워크에서 데이터 흐름에 대해 과금하는 방법, 장치 및 시스템 |
KR101955144B1 (ko) * | 2015-03-04 | 2019-03-06 | 알까뗄 루슨트 | Sdn 네트워크에서 데이터 흐름에 대해 과금하는 방법, 장치 및 시스템 |
Also Published As
Publication number | Publication date |
---|---|
KR20150139941A (ko) | 2015-12-14 |
EP2975869A1 (en) | 2016-01-20 |
EP2975869A4 (en) | 2016-03-30 |
US20160036597A1 (en) | 2016-02-04 |
CN104104520A (zh) | 2014-10-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2014166405A1 (zh) | 一种基于OpenFlow协议的计费的方法及系统 | |
US10764727B2 (en) | Method for charging inter-PLMN roaming data service online, and device | |
US9769326B2 (en) | Charging method and device | |
US20090327112A1 (en) | Method, device and control system for online charging on roaming | |
EP3158682B1 (en) | Charging in a software defined network | |
JP4402714B2 (ja) | フローベース課金におけるイベント・トリガと再認証トリガを取り扱う方法 | |
WO2013155942A1 (zh) | 策略和计费控制方法、v-pcrf及v-ocs | |
WO2005109758A1 (en) | A processing method for perfect charging on line based on the service data stream | |
WO2006047965A1 (fr) | Procede de traitement de facturation en ligne | |
WO2014169877A1 (zh) | 基于sdn epc网络的计费实现方法、系统与存储介质 | |
WO2014040240A1 (zh) | 一种在线计费方法、设备及网络系统 | |
WO2014094488A1 (zh) | 漫游本地业务的计费策略方法及装置 | |
EP3232637A1 (en) | Network entity and service policy management method | |
WO2017092442A1 (zh) | 策略和计费控制快速调整方法、装置及系统 | |
EP3618468B1 (en) | Wireless communication method and device | |
US10499213B2 (en) | Charging method, control plane network element, forwarding plane network element, and charging system | |
WO2015109753A1 (zh) | 计费系统的切换方法及装置 | |
WO2006060964A1 (fr) | Systeme et procede de traitement permettant une facturation en fonction du flux de paquets de donnees | |
WO2014205783A1 (zh) | 一种路由消息传输方法及装置 | |
WO2016141708A1 (zh) | 一种实现在线计费的方法及系统 | |
WO2008089681A1 (fr) | Procédé et système de facturation dans un système de communication | |
WO2017185940A1 (zh) | 一种配额共享方法及信令路由设备 | |
WO2012010625A1 (en) | Message exchange at gx interface for efficiently restarting user session monitoring | |
EP2596600A1 (en) | Message exchange at gx interface for efficiently restarting user session monitoring |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 14782320 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REEP | Request for entry into the european phase |
Ref document number: 2014782320 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2014782320 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 20157031840 Country of ref document: KR Kind code of ref document: A |