CN110890967B - Charging processing method, network element and network system - Google Patents

Abstract

The present invention provides a charging processing method, a network element and a network system, wherein the method includes: in a non-independent networking scenario, acquiring an IP address of a base station corresponding to a bearer; Access technology RAT type; sending the RAT type to the packet data network gateway PGW, so that the PGW performs charging according to the RAT type. In this way, traffic statistics and charging marking for distinguishing RAT types can be implemented.

Description

Billing processing method, network element and network system

technical field

The present invention relates to the field of communication technology, in particular to a billing processing method, a network element and a network system.

Background technique

5G non-standalone networking refers to the joint networking of Long Term Evolution (LTE) and 5G based on dual connectivity technology. After the Convergence Protocol (PDCP for short) layer performs segmentation, the user data stream is simultaneously transmitted to the user through multiple base stations. When the LTE and 5G systems are jointly networked, there are multiple options for both the core network and the wireless network. The core network adopts 4G core network (Evolved Packet Core, referred to as EPC), LTE evolved base station (evolved Node B, referred to as eNB) and 5G base station gNB user plane can be directly connected to EPC, and the control plane is only connected to EPC via LTE eNB. The user plane can be offloaded via LTE eNB, EPC or gNB respectively, corresponding to Option3/3a/3x:

1. When the 5G user plane is connected to the EPC via the LTE eNB, it corresponds to Option3;

2. When both the user planes of 5G and LTE are directly connected to the EPC, it corresponds to Option3a;

3. When the LTE user plane is connected to the EPC via 5G gNB, it corresponds to Option3x.

The 3GPP specification defines: eNB reports the uplink and downlink usage of the secondary RAT (NR) (Radio Access Technologies, RAT for short, New Radio for short, NR for short) to the Mobility Management Entity (Mobility Management Entity, short for NR) in units of bearers MME), forwarded by the MME to the Serving Gateway (Serving GateWay, referred to as SGW), and further forwarded to the PDN Gateway (PDN GateWay, referred to as PGW), the trigger condition can be the usage report triggered by processes such as S1 connection release, session deletion, and handover. Periodic usage reporting is also possible.

Under the current Long Term Evolution (LTE for short) charging architecture: both the SGW and the PGW can collect charging information. The SGW collects the relevant billing information of the wireless network used by each user equipment (User Equipment, referred to as UE), and generates a SGW-CDR bill (Call Detail Record, referred to as CDR, called a call detail record), and the PGW collects each UE The relevant charging information of the external network used, and generate the PGW-CDR bill, and the SGW and PGW jointly collect the relevant charging information of using the EPC network resources. The charging information collected by the SGW can be used for charging among operating enterprises, and the charging information collected by the PGW is used for charging users. PGW-CDR is the charging basis, and PGW is the content charging implementation point.

The existing PGW supports the statistics of the total traffic of users within a period of time, and can realize billing according to the content (for example, distinguishing the traffic visiting website A from the traffic visiting website B). However, when the access technology types include 4G and 5G, The PGW cannot distinguish the traffic of the access type 5G from the traffic of other access types, so that the PGW cannot perform billing according to the radio access technology type.

Contents of the invention

Embodiments of the present invention provide a billing processing method, network element, and network system to solve the problem that the PGW in the prior art cannot distinguish the traffic of the access type 5G from the traffic of other access types, so that the PGW cannot The issue of billing by access technology type.

In order to solve the problems of the technologies described above, the present invention is achieved in that:

In the first aspect, the embodiment of the present invention provides a charging processing method, which is applied to the serving gateway SGW, including:

In a non-independent networking scenario, obtain the IP address of the base station corresponding to the bearer;

Determine the bearer radio access technology RAT type according to the IP address;

Sending the RAT type to the packet data network gateway PGW, so that the PGW performs charging according to the RAT type.

In the second aspect, the embodiment of the present invention also provides a charging processing method, which is applied to the packet data network gateway PGW, including:

In a non-independent networking scenario, receiving the RAT type of the bearer sent by the serving gateway SGW, wherein the SGW determines the RAT type of the bearer according to the acquired IP address of the base station corresponding to the bearer;

The bearer is charged according to the RAT type.

In the third aspect, the embodiment of the present invention also provides a service gateway, including:

The base station IP address acquisition module is used to obtain the IP address of the base station corresponding to the bearer in the non-independent networking scenario;

A RAT type determination module, configured to determine the RAT type of the bearer radio access technology according to the IP address;

A RAT type sending module, configured to send the RAT type to the packet data network gateway PGW, so that the PGW performs charging according to the RAT type.

In a fourth aspect, the embodiment of the present invention also provides a packet data network gateway, including:

The RAT type receiving module is configured to receive the RAT type of the bearer sent by the service gateway SGW in a non-independent networking scenario, wherein the SGW determines the RAT type of the bearer according to the acquired IP address of the base station corresponding to the bearer ;

A charging module, configured to charge the bearer according to the RAT type.

In the fifth aspect, the embodiment of the present invention further provides a network system, including the above-mentioned service gateway and the above-mentioned packet data network gateway.

In the embodiment of the present invention, first in the non-independent networking scenario, the IP address of the base station corresponding to the bearer is obtained; according to the IP address, the radio access technology RAT type of the bearer is determined; The RAT type, so that the PGW performs charging according to the RAT type. Through the above steps, the SGW can obtain the bearer RAT type according to the IP address of the base station, and send the RAT type to the PGW, so that the PGW can count the data traffic according to the RAT type, so as to realize the purpose of charging according to the RAT type.

Description of drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following will briefly introduce the accompanying drawings that need to be used in the description of the embodiments of the present invention. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For those skilled in the art, other drawings can also be obtained based on these drawings without any creative effort.

FIG. 1 is one of the flowcharts of the billing processing method provided by Embodiment 1 of the present invention;

FIG. 2 is one of the flow charts of the billing processing method provided in Embodiment 2 of the present invention;

FIG. 3 is one of the structural diagrams of the service gateway provided by Embodiment 3 of the present invention;

FIG. 4 is the second structural diagram of the service gateway provided by Embodiment 3 of the present invention;

Fig. 5 is one of the structural diagrams of the packet data network gateway provided by Embodiment 4 of the present invention.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are some of the embodiments of the present invention, but not all of them. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of the present invention.

Embodiment one

Referring to FIG. 1, FIG. 1 is one of the flowcharts of the charging processing method provided by an embodiment of the present invention. As shown in FIG. 1, the charging processing method provided by this embodiment is applied to the serving gateway SGW, and includes the following steps:

Step 101. In a non-independent networking scenario, obtain the IP address of the base station corresponding to the bearer.

In scenarios such as user attachment, handover, and service requests initiated by user equipment (UE), the SGW will record, update, and save the EPS Bearer ID (that is, the EPS bearer ID) and the S1 eNodeB F-TEID (including The corresponding relationship between the IP address of the eNB/gNB data plane), that is, when the data is transmitted through the bearer, the SGW records the EPS bearer ID of the bearer and the IP address of the base station sending the data in the bearer context.

In this step, it is necessary to obtain the IP address of the base station that establishes the bearer with the SGW, that is, the IP address of the base station corresponding to the bearer.

Step 102: Determine the RAT type of the bearer according to the IP address.

When determining the bearer RAT type according to the IP address, the SGW may obtain a target IP address list in advance, and if the acquired IP address is in the IP address list, it means that the bearer RAT type is the RAT type corresponding to the target IP address list. In addition, the RAT type can also be added in the GTP header of the data packet sent by the base station, and the SGW determines the carried RAT type according to the GTP header and the IP address of the base station.

Step 103: Send the RAT type to the packet data network gateway PGW, so that the PGW performs charging according to the RAT type.

Specifically, in the attachment process, the UE-initiated public data network (Public Data Network, PDN) connection process, and the bearer migration process, the SGW will send a modify bearer request (Modify Bearer Request) to the PGW. In the process of establishing a dedicated bearer, the SGW will send a create bearer response (Create bearer response) to the PGW.

In the 3GPP specification, the RAT type of the bearer is carried in the bearer modification request or the bearer creation response. The bearer modification request or the bearer creation response includes a RAT type field. The RAT type field is used to identify the RAT type of the bearer. The RAT type that the RAT type field can identify It has been stipulated in 3GPP. However, for the newly added RAT type, the RAT type field in the 3GPP specification cannot be identified. Based on this, in order to identify the newly added RAT type, in this step, two methods are used to add the newly added RAT type of the bearer to the bearer modification request or the bearer creation response.

Among them, the first method is to add a new secondary RAT type (ie Secondary RAT Type) field in the bearer modification request or the bearer creation response. The secondary RAT type field is at least used to identify the newly added RAT type of the bearer, that is, the secondary RAT type field can be It is used to identify the newly added RAT type of the bearer (such as 5G). For example, when the value of the secondary RAT type field is 1, it means that the RAT type of the bearer is 5G. The newly added RAT type is a RAT type other than the RAT type identified by the RAT type field .

The second method is to increase the value range of the RAT type in the request to modify the bearer or create the bearer response, so that the RAT type field is also used to identify the newly added RAT type of the bearer, for example, add a value of 9 (a value greater than or equal to 9 is acceptable) , when the value of the RAT type field is 9, it indicates that the RAT type of the bearer is 5G.

After obtaining the RAT type, the PGW can know which RAT type is used for the data transmitted on the bearer, and then count the data traffic according to the RAT type, so as to realize the purpose of charging according to the RAT type.

It should be noted that, the charging processing method in this embodiment is preferably applied in a Non-Standalone (Non-Standalone, NSA for short) Option3a solution.

In the billing processing method provided in this embodiment, firstly, in a non-independent networking scenario, the IP address of the base station corresponding to the bearer is obtained; according to the IP address, the radio access technology RAT type of the bearer is determined; The gateway PGW sends the RAT type, so that the PGW performs charging according to the RAT type. Through the above steps, the SGW can obtain the bearer RAT type according to the IP address of the base station, and send the RAT type to the PGW, so that the PGW can count the data traffic according to the RAT type, so as to realize the purpose of charging according to the RAT type.

Further, in one embodiment of the present invention, step 102, the step of determining the RAT type of the bearer radio access technology according to the IP address includes:

If the IP address is in the target IP address list, determine that the RAT type of the bearer is the RAT type corresponding to the target IP address list.

The target IP address list can be configured on the SGW or on an external device, that is, the target IP address list is pre-configured in the SGW, or the target IP address list is pre-configured in the external device Yes, the external device establishes a communication connection with the SGW.

When the SGW needs to use the target IP address list, it can obtain it from a local or external device. The target IP address list includes IP addresses of base stations using a certain RAT type for data transmission, for example, when the RAT type is 5G, the target IP address list includes IP addresses of base stations using 5G for data transmission.

When the bearer is established and migrated, the SGW obtains the S1 eNodeB F-TEID corresponding to the bearer (that is, the IP address of the base station sending data) through a signaling message (sent to the SGW by the Mobility Management Entity (MME) function), and resolves Whether the IP of the base station is in the pre-acquired target IP address list. If yes, the access technology type corresponding to the bearer is the RAT type corresponding to the target IP address list.

For example, for the currently used 4G and 5GRAT types, the target IP address list of the gNB is configured on the SGW, and the SGW obtains the S1 eNodeB F-TEID corresponding to the bearer through signaling messages when the bearer is established and migrated, and judges the base station's F-TEID. Whether the IP is in the list of target IP addresses of the configured gNB. If yes, the RAT type corresponding to the bearer is gNB; if not, the RAT type corresponding to the bearer is eNB. The SGW may only configure the target IP address list of the gNB within the preset range.

In addition to using the above method to determine the RAT type of the bearer, the embodiment of the present invention also provides another way to determine the RAT type of the bearer: before step 102, it also includes:

Receiving the data message sent by the base station, the general packet radio service technology tunneling protocol GTP header of the data message includes the identification information bearer used to identify the RAT type; then the SGW determines the bearer according to the IP address and the identification information The RAT type.

In this implementation, the currently used 4G and 5GRAT types are also used as examples for illustration. When sending the data message, the base station adds a newly added field identifier in the GTP header of the data message to identify the RAT type. That is, a new field identifier is added to the GTP packet header of the data message to identify the eNB or gNB, and the SGW knows whether the data message is routed by the eNB or the gNB by identifying the identifier, and the RAT type corresponding to the bearer used by the data message routed by the eNB is The RAT type corresponding to the bearer used by the data packets routed by the eNB and gNB is gNB. The RAT type corresponding to the bearer can be obtained by associating the bearer context with the newly added field identifier and the IP address of the base station.

Further, in another embodiment of the present invention, step 103, the step of sending the RAT type to the packet data network gateway PGW includes:

Sending a bearer modification request or a bearer creation response to the PGW, wherein the bearer modification request or bearer creation response is at least used to indicate the RAT type.

When the RAT type of the bearer is changed from 4G to 5G, or the RAT type of the bearer is changed from 5G to 4G, modify the value of the secondary RAT type field in the modify bearer request, or modify the RAT type field to identify the current RAT type of the bearer;

Specifically, in the 3GPP specification, if the secondary RAT usage report is not involved, the bearer modification request sent by the MME is only sent to the SGW, and will not be forwarded to the PGW. At this time, the PGW’s traffic charging according to the RAT type will cause errors. Therefore, , in this embodiment, when the RAT type of the bearer is changed from 4G to 5G, or when the RAT type of the bearer is changed from 5G to 4G, a bearer modification request is sent to the PGW, and the bearer modification request carries the bearer The current RAT type, to inform the PGW of the current RAT type carried by the PGW, and realize the traffic statistics and billing marking of the PGW distinguishing between 4G and 5G.

Further, before the step of sending a bearer modification request or creating a bearer response to the PGW, the method further includes:

Determine the value of the RAT type field in the modify bearer request or create bearer response according to the RAT type.

In the 3GPP specification, the RAT type of the bearer is carried in the bearer modification request or the bearer creation response. The bearer modification request or the bearer creation response includes a RAT type field. The RAT type field is used to identify the RAT type of the bearer. The RAT type that the RAT type field can identify It has been stipulated in 3GPP. However, for the newly added RAT type, the RAT type field in the 3GPP specification cannot be identified. Based on this, in order to identify the newly added RAT type, in this step, two methods are used to add the newly added RAT type of the bearer to the bearer modification request or the bearer creation response.

Among them, the first method is to add a new secondary RAT type (ie Secondary RAT Type) field in the bearer modification request or the bearer creation response. The secondary RAT type field is at least used to identify the newly added RAT type of the bearer, that is, the secondary RAT type field can be It is used to identify the newly added RAT type of the bearer (such as 5G). For example, when the value of the secondary RAT type field is 1, it means that the RAT type of the bearer is 5G. The newly added RAT type is a RAT type other than the RAT type identified by the RAT type field .

The second method is to increase the value range of the RAT type in the request to modify the bearer or create the bearer response, so that the RAT type field is also used to identify the newly added RAT type of the bearer, for example, add a value of 9 (a value greater than or equal to 9 is acceptable) , when the value of the RAT type field is 9, it indicates that the RAT type of the bearer is 5G.

Further, determining the value of the RAT type field in the bearer modification request includes:

When the RAT type of the bearer changes, modify the value of the RAT type field in the modify bearer request.

For example, when the RAT type of the bearer is changed from 4G to 5G, or when the RAT type of the bearer is changed from 5G to 4G, modify the value of the secondary RAT type field in the modify bearer request, or modify the RAT The value of the type field to identify the current RAT type of the bearer.

Further, after the step of sending the modifying bearer request or creating the bearer response to the PGW, it also includes:

When the RAT type of the bearer changes, the secondary RAT type field is deleted or added in the bearer modification request or bearer creation response, or the value of the secondary RAT type field is modified.

For example, when the RAT type of the bearer is changed from 4G to 5G, a secondary RAT type field needs to be added, and the secondary RAT type field is used to identify 5G. When the RAT type of the bearer is changed from 5G to 4G, at this time, the RAT type field can be used to identify 4G, and the secondary RAT type field can be deleted, or the value of the secondary RAT type field can be modified so that the value of the secondary RAT type field is If it is 0, it means that the bearer RAT type is 4G.

Embodiment two

Referring to FIG. 2, FIG. 2 is one of the flowcharts of the billing processing method provided in Embodiment 2 of the present invention. As shown in FIG. 2, the billing processing method provided in this embodiment is applied to the packet data network gateway PGW, including:

Step 201, in a non-independent networking scenario, receiving the RAT type of the bearer sent by the serving gateway SGW, wherein the SGW determines the RAT type of the bearer according to the acquired IP address of the base station corresponding to the bearer.

During the attach process, the UE-initiated public data network (Public Data Network, PDN) connection process, and the bearer migration process, the PGW will receive a modify bearer request (Modify Bearer Request) sent by the SGW. In the process of establishing a dedicated bearer, the PGW will receive a create bearer response (Create bearer response) sent by the SGW.

In the 3GPP specification, the RAT type of the bearer is carried in the bearer modification request or the bearer creation response. The bearer modification request or the bearer creation response includes a RAT type field. The RAT type field is used to identify the RAT type of the bearer. The RAT type that the RAT type field can identify It has been stipulated in 3GPP. However, for the newly added RAT type, the RAT type field in the 3GPP specification cannot be identified. Based on this, in order to identify the newly added RAT type, in this step, two methods are used to add the newly added RAT type of the bearer to the bearer modification request or the bearer creation response.

Among them, the first method is to add a new secondary RAT type (ie Secondary RAT Type) field in the bearer modification request or the bearer creation response. The secondary RAT type field is at least used to identify the newly added RAT type of the bearer, that is, the secondary RAT type field can be It is used to identify the newly added RAT type of the bearer (for example, 5G). For example, when the value of the secondary RAT type field is 1, it indicates that the RAT type of the bearer is 5G. The newly added RAT type is a RAT type other than the bearer RAT type identified by the RAT type field.

The second method is to increase the value range of the RAT type in the request to modify the bearer or create the bearer response, so that the RAT type field is also used to identify the newly added RAT type of the bearer, for example, add a value of 9 (a value greater than or equal to 9 is acceptable) , when the value of the RAT type field is 9, it indicates that the RAT type of the bearer is 5G.

Step 202, charge the bearer according to the RAT type.

After receiving the bearer modification request or the bearer creation response, the PGW obtains the corresponding field value from its secondary RAT type field or RAT type field, and obtains the RAT type of the bearer according to the field value.

After acquiring the RAT type, the PGW collects statistics on the data traffic according to the RAT type, so as to realize the purpose of charging according to the RAT type.

It should be noted that, the charging processing method in this embodiment is preferably applied in the non-standalone networking (Non-Standalone, NSA for short) Option 3a solution.

In the charging processing method provided in this embodiment, in a non-independent networking scenario, the RAT type of the bearer sent by the serving gateway SGW is received, and the bearer is charged according to the RAT type. Through the above steps, the PGW can obtain the RAT type of the bearer, and implement traffic statistics and charging marking for distinguishing RAT types.

In an embodiment of the present invention, step 201, the step of receiving the RAT type of the bearer sent by the serving gateway SGW includes:

receiving a bearer modification request or a bearer creation response sent by the SGW; wherein the modification bearer request or the bearer creation response is at least used to indicate the RAT type.

During the attach process, the UE-initiated public data network (Public Data Network, PDN) connection process, and the bearer migration process, the PGW will receive the bearer modification request sent by the SGW. In the process of establishing a dedicated bearer, the PGW will receive the bearer creation response sent by the SGW. The modify bearer request or create bearer response includes a field indicating the RAT type.

The value of the RAT type field in the bearer modification request or the bearer creation response is used to indicate the RAT type, such as 4G, and the secondary RAT type field in the bearer modification request or bearer creation response is used to indicate the RAT type, for example, 5G.

If the response according to the modify bearer request or create bearer includes the secondary RAT type field, obtain the RAT type according to the secondary RAT type field or the RAT type field; if the modify bearer request or create If the bearer response does not include the secondary RAT type field, the RAT type is obtained according to the RAT type field.

When modifying the bearer request or creating the bearer response includes the secondary RAT type field, the RAT type of the bearer is obtained through the secondary RAT type field or the RAT type field. For example, when the RAT type is 5G, the secondary RAT type field can be used. RAT type; when the RAT type is 3G, the RAT type carried can be known through the RAT type field.

When modifying the bearer request or creating the bearer response does not include the secondary RAT type field, the RAT type is obtained directly according to the RAT type field.

Further, in one embodiment of the present invention, step 201, the step of charging the bearer according to the RAT type, includes:

When the RAT type changes, trigger the closing of the PGW-CDR bill, and record the RAT type before the change in the PGW-CDR for offline charging, wherein the RAT type before the change in the PGW-CDR includes : Modify the value of the RAT type field of PGW-CDR, or delete the Secondary RAT type field in PGW-CDR, or add the Secondary RAT type field in PGW-CDR, or modify the value of the Secondary RAT type field of PGW-CDR, The RAT type field or the Secondary RAT type field of the PGW-CDR is used to indicate the RAT type before the change.

If the RAT type field of the modification bearer request or the bearer creation response is used to identify the newly added RAT type, then increase the value range of the RAT type field of the PGW-CDR bill to identify the newly added RAT type of the bearer ; If the RAT type field of the modification bearer request or the bearer creation response is not used to identify the newly added RAT type, then add a secondary RAT type field in the PGW-CDR bill to identify the newly added RAT type of the bearer .

Specifically, in the 3GPP specification, the PGW-CDR bill includes a RAT type field, which is used to identify the bearer RAT type, and the RAT type that can be identified by the RAT type field of the PGW-CDR bill has been specified in 3GPP. However, for the newly added RAT type, the RAT type field of the PGW-CDR bill in the 3GPP specification cannot be identified.

When the RAT type field of the bearer modification request or the bearer creation response is used to identify the new RAT type, correspondingly, the value range of the RAT type field of the PGW-CDR bill is increased to identify the new RAT type of the bearer. At this point, the PGW obtains the value of the field according to the RAT type field, and fills the value into the RAT type field of the PGW-CDR bill, so that the RAT type identified in the RAT type field of the PGW-CDR bill is the same as The RAT type identified in the RAT type field of the bearer modification request (or bearer creation response) is consistent.

When the RAT type field of the bearer modification request or the bearer creation response is not used to identify the new RAT type, it means that the bearer modification request or the bearer creation response adopts an additional field to identify the new RAT type, and correspondingly, in The secondary RAT type field is added in the PGW-CDR bill to identify the newly added RAT type carried. At this time, the PGW obtains the value of this field according to the secondary RAT type field, and fills the value into the secondary RAT type field of the PGW-CDR bill, so that the RAT identified in the secondary RAT type field of the PGW-CDR bill The type is consistent with the RAT type identified in the secondary RAT type field of the bearer modification request (or bearer creation response).

It should be noted that when the bearer is migrated from the first RAT type (such as 4G) to the second RAT type (such as 5G), or from the second RAT type to the first RAT type, the trigger part The CDR is closed, and the trigger condition is that the RAT type changes.

In the billing processing method in this embodiment, the PGW-CDR bill includes the bearer RAT type, which can realize offline traffic statistics and billing marking for distinguishing RAT types.

Further, in one embodiment of the present invention, step 201, the step of charging the bearer according to the RAT type, further includes:

When the RAT type changes, update the RAT type in the credit control request update message CCR-U, and send the updated CCR-U message to the business operation support system BOSS to perform online charging and update the CCR-U The RAT type in the message includes modifying the value of 3GPP-RAT-Type AVP in the CCR-U message, or deleting the 3GPP-Secondary-RAT-Type AVP in the CCR-U message, or adding 3GPP-Secondary in the CCR-U message -RAT-Type AVP, or modify the value of 3GPP-Secondary-RAT-Type AVP in the CCR-U message, where the 3GPP-RAT-Type field or 3GPP-Secondary-RAT-Type AVP in the CCR-U message is used for Indicates the changed RAT type.

Specifically, when the RAT type changes, for example, when the bearer RAT type changes from 4G to 5G, a secondary RAT type field needs to be added, and the secondary RAT type field is used to identify 5G. When the RAT type of the bearer is changed from 5G to 4G, at this time, the RAT type field can be used to identify 4G, and the secondary RAT type field can be deleted, or the value of the secondary RAT type field can be modified so that the value of the secondary RAT type field is If it is 0, it means that the bearer RAT type is 4G.

For the changed RAT type is a newly added RAT type, the following two methods are used to process the CCR-U message.

When modifying the bearer request or creating the bearer response RAT type field is used to identify the newly added RAT type, correspondingly, increase the value of the 3GPP-RAT-Type field in the PS-Information AVP in the CCR-U to identify the bearer The new RAT type mentioned above. At this time, the PGW obtains the value of this field according to the RAT type field of the PGW-CDR bill, and fills the value into the 3GPP-RAT-Type field in the PS-Information AVP in the CCR-U message to inform The RAT type currently borne by the BOSS implements charging based on the RAT type.

When the RAT type field of the bearer modification request or the bearer creation response is not used to identify the new RAT type, it means that the bearer modification request or the bearer creation response adopts an additional field to identify the new RAT type, and correspondingly, in A 3GPP-Secondary-RAT-Type AVP field is added to the CCR-U message to identify the newly added RAT type carried. At this time, the PGW obtains the value of the field according to the RAT type field of the PGW-CDR bill, and fills the value into the new identification field added in the CCR-U message (ie 3GPP-Secondary-RAT-Type AVP) , make the RAT type identified by the new identification field of the PGW-CDR bill consistent with the RAT type identified by the secondary RAT type field of the modify bearer request (or create bearer response).

It should be noted that when the bearer is migrated from the first RAT type (such as 4G) to the second RAT type (such as 5G), or from the second RAT type to the first RAT type, the trigger part When the CDR is closed, the trigger condition is that the RAT type changes, and at the same time, the PGW needs to support sending a CCR-U message to the BOSS to apply for a new quota.

The billing processing method in this embodiment includes the RAT type of the bearer in the CCR-U message sent to the BOSS, which can realize online traffic statistics and billing marking for distinguishing RAT types. Since the PGW counts the traffic carried by the PGW in real time, and The flow is reflected in the PGW-CDR bill and the CCR-U message. Therefore, the charging processing method in this embodiment can also realize real-time reporting of the flow.

Embodiment Three

The service gateway in this embodiment is a device embodiment corresponding to Embodiment 1.

Referring to FIG. 3, FIG. 3 is one of the structural diagrams of the service gateway provided by Embodiment 3 of the present invention. As shown in FIG. 3, the service gateway 300 provided by this embodiment includes:

A base station IP address acquisition module 301, configured to acquire the IP address of the base station corresponding to the bearer in a non-independent networking scenario;

The RAT type determination module 302 is configured to determine the RAT type of the bearer radio access technology according to the IP address;

The RAT type sending module 303 is configured to send the RAT type to the packet data network gateway PGW, so that the PGW performs charging according to the RAT type.

The service gateway 300 provided in this embodiment first acquires the IP address of the base station corresponding to the bearer in a non-independent networking scenario; determines the RAT type of the bearer according to the IP address; The PGW sends the RAT type, so that the PGW performs charging according to the RAT type. Through the above steps, the SGW can obtain the bearer RAT type according to the IP address of the base station, and send the RAT type to the PGW, so that the PGW can count the data traffic according to the RAT type, so as to realize the purpose of charging according to the RAT type.

Further, the RAT type determining module 302 is configured to: if the IP address is in the target IP address list, determine that the RAT type of the bearer is the RAT type corresponding to the target IP address list.

Further, the target IP address list is pre-configured in the SGW, or the target IP address list is pre-configured in an external device, and the external device establishes a communication connection with the SGW.

Further, the above service gateway 300 also includes: a message receiving module, configured to receive a data message sent by the base station, the general packet radio service technology tunneling protocol GTP header of the data message includes identification information for identifying the RAT type carrying;

The RAT type determination module 302 is configured to determine the RAT type of the bearer according to the IP address and the identification information.

Further, the RAT type sending module 303 is configured to send a bearer modification request or a bearer creation response to the PGW, wherein the bearer modification request or bearer creation response is at least used to indicate the RAT type.

Further, as shown in FIG. 4 , the service gateway 300 further includes a sending message determining module 304, configured to determine the value of the RAT type field in the bearer modification request or bearer creation response according to the RAT type.

Further, the sending message determining module 304 is configured to modify the value of the RAT type field in the modify bearer request when the RAT type of the bearer changes.

Further, as shown in FIG. 4, the service gateway 300 also includes:

The modifying module 305 is configured to delete or add a secondary RAT type field in the modify bearer request or create bearer response, or modify the value of the secondary RAT type field when the RAT type of the bearer changes.

Since the service gateway 300 in this embodiment is a device embodiment corresponding to the first embodiment, and can implement each step in the first embodiment, in order to avoid repetition, details are not repeated here.

Embodiment Four

The packet data network gateway in this embodiment is a device embodiment corresponding to the second embodiment.

Referring to FIG. 5, FIG. 5 is one of the structural diagrams of the packet data network gateway provided in Embodiment 4 of the present invention. As shown in FIG. 5, the packet data network gateway 400 provided in this embodiment includes:

The RAT type receiving module 401 is configured to receive the RAT type of the bearer sent by the service gateway SGW in a non-independent networking scenario, wherein the SGW determines the RAT of the bearer according to the acquired IP address of the base station corresponding to the bearer type;

The charging module 402 is configured to charge the bearer according to the RAT type.

The packet data network gateway 400 provided in this embodiment receives the RAT type of the bearer sent by the serving gateway SGW in a non-independent networking scenario, and charges the bearer according to the RAT type. Through the above steps, the PGW can obtain the RAT type of the bearer, and implement traffic statistics and charging marking for distinguishing RAT types.

Further, the RAT type receiving module 401 is used for:

receiving a bearer modification request or a bearer creation response sent by the SGW; wherein the modification bearer request or the bearer creation response is at least used to indicate the RAT type.

Further, the value of the RAT type field in the modify bearer request or create bearer response is used to indicate the RAT type.

Further, the secondary RAT type field in the bearer modification request or bearer creation response is used to indicate the RAT type.

Further, the charging module 402 is configured to trigger the closing of the PGW-CDR bill when the RAT type changes, and record the RAT type before the change in the PGW-CDR for offline charging, wherein, Recording the RAT type before the change in PGW-CDR includes: modifying the value of the RAT type field of PGW-CDR, or deleting the Secondary RAT type field in PGW-CDR, or adding a Secondary RAT type field in PGW-CDR, or modifying The value of the SecondaryRAT type field of PGW-CDR, the RAT type field of PGW-CDR or the Secondary RAT type field is used to indicate the RAT type before the change.

Further, the billing module 402 is also used for:

When the RAT type changes, update the RAT type in the credit control request update message CCR-U, and send the updated CCR-U message to the business operation support system BOSS to perform online charging and update the CCR-U The RAT type in the message includes modifying the value of 3GPP-RAT-Type AVP in the CCR-U message, or deleting the 3GPP-Secondary-RAT-Type AVP in the CCR-U message, or adding 3GPP-Secondary in the CCR-U message -RAT-Type AVP, or modify the value of 3GPP-Secondary-RAT-Type AVP in the CCR-U message, where the 3GPP-RAT-Type field or 3GPP-Secondary-RAT-Type AVP in the CCR-U message is used for Indicates the changed RAT type.

Since the packet data network gateway 400 in this embodiment is a device embodiment corresponding to the second embodiment, and can implement each step in the second embodiment, in order to avoid repetition, details are not repeated here.

Further, the present invention also provides a network system, including the service gateway 300 in the third embodiment and the packet data network gateway 400 in the fourth embodiment.

The embodiment of the present invention also provides a computer-readable storage medium. A computer program is stored on the computer-readable storage medium. When the computer program is executed by a processor, each process of the above-mentioned billing processing method embodiment is realized, and the same Technical effects, in order to avoid repetition, will not be repeated here. Wherein, the computer-readable storage medium is, for example, a read-only memory (Read-Only Memory, ROM for short), a random access memory (Random Access Memory, RAM for short), a magnetic disk or an optical disk, and the like.

It should be noted that, in this document, the term "comprising", "comprising" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article or apparatus comprising a set of elements includes not only those elements, It also includes other elements not expressly listed, or elements inherent in the process, method, article, or device. Without further limitations, an element defined by the phrase "comprising a ..." does not preclude the presence of additional identical elements in the process, method, article, or apparatus comprising that element.

Through the description of the above embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also by hardware, but in many cases the former is better implementation. Based on such an understanding, the essence of the technical solution of the present invention or the part that contributes to the prior art can be embodied in the form of software products, and the computer software products are stored in a storage medium (such as ROM/RAM, disk, CD) contains several instructions to make a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the methods described in various embodiments of the present invention.

Embodiments of the present invention have been described above in conjunction with the accompanying drawings, but the present invention is not limited to the above-mentioned specific implementations, and the above-mentioned specific implementations are only illustrative, rather than restrictive, and those of ordinary skill in the art will Under the enlightenment of the present invention, without departing from the gist of the present invention and the protection scope of the claims, many forms can also be made, all of which belong to the protection of the present invention.

Claims (21)

1. A billing processing method applied to a serving gateway SGW, characterized in that it comprises: In a non-independent networking scenario, obtain the IP address of the base station corresponding to the bearer; Determine the bearer radio access technology RAT type according to the IP address; Sending the RAT type to the packet data network gateway PGW, so that the PGW performs charging according to the RAT type, includes: sending a modify bearer request or create a bearer response to the PGW, wherein the modify bearer request or create The bearer response is at least used to indicate the RAT type; When the RAT type of the bearer changes, the secondary RAT type field is deleted or added in the bearer modification request or bearer creation response, or the value of the secondary RAT type field is modified. 2. The method according to claim 1, wherein, according to the IP address, the step of determining the RAT type of the bearer comprises: If the IP address is in the target IP address list, determine that the RAT type of the bearer is the RAT type corresponding to the target IP address list. 3. The method according to claim 2, wherein the target IP address list is pre-configured in the SGW, or the target IP address list is pre-configured in an external device, the The external device establishes a communication connection with the SGW. 4. The method according to claim 1, characterized in that, before the step of determining the bearer radio access technology RAT type according to the IP address, further comprising: Receiving the data message sent by the base station, the General Packet Radio Service Technology Tunneling Protocol GTP header of the data message includes an identification information bearer for identifying the RAT type; According to the IP address, the step of determining the RAT type of the bearer includes: Determine the RAT type of the bearer according to the IP address and the identification information. 5. The method according to claim 1, wherein after the RAT type of the bearer is determined according to the IP address, before the step of sending a bearer modification request or creating a bearer response to the PGW, further comprising: Determine the value of the RAT type field in the modify bearer request or create bearer response according to the RAT type. 6. The method according to claim 5, wherein, according to the RAT type, determining the value of the RAT type field in the modification bearer request comprises: When the RAT type of the bearer changes, modify the value of the RAT type field in the modify bearer request. 7. A billing processing method applied to a packet data network gateway PGW, characterized in that, comprising: In a non-independent networking scenario, receiving the RAT type of the bearer sent by the serving gateway SGW, wherein the SGW determines the RAT type of the bearer according to the acquired IP address of the base station corresponding to the bearer; including : receiving the modify bearer request or create bearer response sent by the SGW; wherein, the modify bearer request or create bearer response is at least used to indicate the RAT type; the secondary RAT type field in the modify bearer request or create bearer response Used to indicate the RAT type; The bearer is charged according to the RAT type. 8. The method according to claim 7, wherein the value of the RAT type field in the modify bearer request or create bearer response is used to indicate the RAT type. 9. The method according to any one of claims 7 to 8, wherein the step of charging the bearer according to the RAT type comprises: When the RAT type changes, the PGW-CDR bill is triggered to close, and the RAT type before the change is recorded in the PGW-CDR for offline charging; Wherein, recording the RAT type before the change in the PGW-CDR includes updating the RAT type in the PGW-CDR includes: modifying the value of the RAT type field of the PGW-CDR, or deleting the Secondary RAT type field in the PGW-CDR, or in the PGW -Increase the Secondary RAT type field in the CDR, or modify the value of the Secondary RAT type field of the PGW-CDR, and the RAT type field or the Secondary RAT type field of the PGW-CDR is used to indicate the RAT type before the change. 10. The method according to any one of claims 7 to 8, wherein the step of charging the bearer according to the RAT type further comprises: When the RAT type changes, update the RAT type in the credit control request update message CCR-U, and send the updated CCR-U message to the business operation support system BOSS to perform online charging and update the CCR-U The RAT type in the message includes modifying the value of 3GPP-RAT-Type AVP in the CCR-U message, or deleting the 3GPP-Secondary-RAT-Type AVP in the CCR-U message, or adding 3GPP-Secondary in the CCR-U message -RAT-Type AVP, or modify the value of 3GPP-Secondary-RAT-Type AVP in the CCR-U message, where the 3GPP-RAT-Type field or 3GPP-Secondary-RAT-Type AVP in the CCR-U message is used for Indicates the changed RAT type. 11. A service gateway, characterized in that it comprises: The base station IP address acquisition module is used to obtain the IP address of the base station corresponding to the bearer in the non-independent networking scenario; A RAT type determination module, configured to determine the RAT type of the bearer radio access technology according to the IP address; A RAT type sending module, configured to send the RAT type to the packet data network gateway PGW, so that the PGW performs charging according to the RAT type; A RAT type sending module, configured to send a modify bearer request or create a bearer response to the PGW, wherein the modify bearer request or create a bearer response is at least used to indicate the RAT type; A modifying module, configured to delete or add a secondary RAT type field in the modify bearer request or create bearer response, or modify the value of the secondary RAT type field when the RAT type of the bearer changes. 12. The serving gateway according to claim 11, wherein the RAT type determining module is used for: If the IP address is in the target IP address list, determine that the RAT type of the bearer is the RAT type corresponding to the target IP address list. 13. The serving gateway according to claim 12, wherein the target IP address list is pre-configured in the SGW, or the target IP address list is pre-configured in an external device, so The external device establishes a communication connection with the SGW. 14. The service gateway according to claim 11, further comprising: The message receiving module is used to receive the data message sent by the base station, and the General Packet Radio Service Technology Tunneling Protocol GTP header of the data message includes an identification information bearer for identifying the RAT type; The RAT type determination module is configured to determine the RAT type of the bearer according to the IP address and the identification information. 15. The serving gateway according to claim 11, further comprising a sending message determining module, configured to determine the value of the RAT type field in the modify bearer request or create bearer response according to the RAT type. 16. The service gateway according to claim 15, wherein the sending message determining module is configured to: When the RAT type of the bearer changes, modify the value of the RAT type field in the modify bearer request. 17. A packet data network gateway, characterized in that, comprising: The RAT type receiving module is configured to receive the radio access technology RAT type of the bearer sent by the serving gateway SGW in a non-independent networking scenario, wherein the SGW determines the IP address of the base station corresponding to the acquired bearer. The type of RAT carried; A charging module, configured to charge the bearer according to the RAT type; The RAT type receiving module is configured to: receive a modify bearer request or create a bearer response sent by the SGW; wherein the modify bearer request or create a bearer response is at least used to indicate the RAT type; the modify bearer request or create The secondary RAT type field in the bearer response is used to indicate the RAT type. 18. The packet data network gateway according to claim 17, wherein the value of the RAT type field in the modify bearer request or create bearer response is used to indicate the RAT type. 19. The packet data network gateway according to any one of claims 17 to 18, wherein the billing module is configured to trigger the closing of the PGW-CDR bill when the RAT type changes, and Record the RAT type before the change in PGW-CDR for offline charging; Wherein, recording the RAT type before the change in the PGW-CDR includes: modifying the value of the RAT type field of the PGW-CDR, or deleting the Secondary RAT type field in the PGW-CDR, or adding the Secondary RAT type field in the PGW-CDR, Or modify the value of the Secondary RAT type field of the PGW-CDR, where the RAT type field or the Secondary RAT type field of the PGW-CDR is used to indicate the RAT type before the change. 20. The packet data network gateway according to any one of claims 17 to 18, wherein the billing module is also used for: When the RAT type changes, update the RAT type in the credit control request update message CCR-U, and send the updated CCR-U message to the business operation support system BOSS to perform online charging and update the CCR-U The RAT type in the message includes modifying the value of 3GPP-RAT-Type AVP in the CCR-U message, or deleting the 3GPP-Secondary-RAT-Type AVP in the CCR-U message, or adding 3GPP-Secondary in the CCR-U message -RAT-Type AVP, or modify the value of 3GPP-Secondary-RAT-Type AVP in the CCR-U message, where the 3GPP-RAT-Type field or 3GPP-Secondary-RAT-Type field in the CCR-U message is used for Indicates the changed RAT type. 21. A network system, characterized by comprising the service gateway according to any one of claims 11-16 and the packet data network gateway according to any one of claims 17-20.

Images