CN111314868B

CN111314868B - Method, device, equipment and medium for taking PCC static policy into effect

Info

Publication number: CN111314868B
Application number: CN201811517713.XA
Authority: CN
Inventors: 姚芋伶; 蔡家鹏
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Group Sichuan Co Ltd
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Group Sichuan Co Ltd
Priority date: 2018-12-12
Filing date: 2018-12-12
Publication date: 2021-03-09
Anticipated expiration: 2038-12-12
Also published as: CN111314868A

Abstract

The invention discloses a method, a device, equipment and a medium for validating a PCC static strategy. The method comprises the following steps: when a user uses the static policy service in a roaming place, receiving an identifier of the user, which is sent by a packet data gateway (PGW) in the roaming place; determining that the identifier of the roaming place PGW does not belong to the pre-stored identifier sets of all PGWs of the user attribution place; selecting any PGW from all PGWs of a user home location as a target PGW, and sending an identifier of the target PGW to a roaming PGW, so that the roaming PGW forwards the identifier of the target PGW to a Serving Gateway (SGW), the SGW sends a bearer establishment request to the target PGW by using the identifier of the target PGW, and the target PGW sends an identifier of the target PGW according to the bearer establishment request; and issuing a Policy and Charging Control (PCC) static policy corresponding to the static policy service to the target PGW according to the received identifier of the target PGW, so that the PCC static policy takes effect in a roaming place. By utilizing the embodiment of the invention, the user can normally use the PCC static strategy when roaming.

Description

Method, device, equipment and medium for taking PCC static policy into effect

Technical Field

The present invention relates to the field of data services, and in particular, to a method, an apparatus, a device, and a medium for validating a PCC static policy.

Background

In the 3GPP protocol, a Policy and Charging Rules Function (PCRF) network element is added in the R7 version, and is used to satisfy network resource management and control of different users, different services, and different scenarios, and implement personalized and differentiated network services. The PCRF is connected to a Gateway GPRS Support Node (GGSN) or a Packet Data Gateway (PGW) through a Routing Agent Node (DRA), and customizes services and charging management and control such as Quality of Service (QoS), bandwidth, and scale value (QoS Class Identifier, QCI) according to the personalized requirements of users. When a user signs a service on the PCRF, a policy on the PCRF is corresponded.

Policy and Charging Control (PCC) policies refer to Charging and Control policies issued by a PCRF, and relate to the cooperation of a PCRF and a PGW network element. The PCC policy consists of two parts, a trigger and a rule. And the trigger is issued to the PGW when the user is online and is used for informing the point of interest of the PCC strategy. And when the PGW detects that the user behavior meets the condition of the trigger, the PGW informs the PCRF and reports the specific content.

The rule consists of a condition and a content, wherein the condition is used for matching with the content fed back by the PGW, and the content refers to a specific implementation scheme of the strategy, and the content of the rule can be executed only after the condition is met.

The rules are divided into dynamic rules and static rules according to different content configuration modes of the rules. For static rules, the PCRF only configures trigger conditions of the policy, names of the rules, and configures names, contents, and priorities of the rules on the PGW. The rule names configured on both the PCRF and the PGW need to be consistent to ensure correct matching of the rules.

Taking the area management policy as an example: a 1-tuple/500M traffic packet is marketed and shows that the traffic packet will only be valid for a package when used in a specified commercial segment. It is worth noting that the existing network has free services, such as visiting an operator official network, and the like, and the priority of the existing network is higher than that of a 1 yuan/500M traffic packet. Fig. 1 shows a schematic diagram of an area management policy data configuration.

A trigger: configured in PCRF, and is sent to PGW when user is on line. When the user is on line newly or the position changes occur in the service using process, the PGW reports the latest position information to the PCRF user.

Rule conditions are as follows: and after receiving the user location information reported by the PGW, the PCRF judges according to rule conditions, and if the location of the user is found to belong to cells 46000012345678 and 46000012345679, the rule content is executed.

The rule content is as follows: the PGW puts on a special charging identifier (Rating Group) 3000000003, which is presented in the ticket for final settlement of charges. The rules are configured as static rules and have a lower priority than the free traffic. Then, the policy is executed only when the user uses the charging service in the area; free services are not affected by location areas.

The area management policy is limited to the location area, so that data preparation only needs to be performed on the PGW carrying the area service. However, in practical applications, there are still static rules based on time, terminal model, service type, etc., and the user is in a mobile state. Fig. 2 shows a networking diagram of an existing network PCRF and a PGW. And after the angelica attribution is signed with a PCC static strategy for the user of the city A, the user roams to the city B. The roaming place PGW-03 finds out the PCRF-01 of the user's home place through number segment configuration on Routing Agent node (DRA) equipment, and sends a static policy according to a trigger condition. However, the roaming PGW-03 does not configure the rule content, which may result in failure of PCC static policy enforcement. Therefore, when the user roams to other cities or returns from the roaming place, the PCRF may issue the static policy and fail to correctly take effect in the designated area.

Disclosure of Invention

The embodiment of the invention provides a method, a device, equipment and a medium for validating a PCC static strategy, which realize that a user can normally use the PCC static strategy in a roaming place under the condition that a PGW in the roaming place has no static strategy.

According to an aspect of the embodiments of the present invention, there is provided a method for validating a PCC static policy, where the method includes:

when a user uses the static policy service in a roaming place, receiving an identifier of the user, which is sent by a packet data gateway (PGW) in the roaming place;

determining that the identifier of the roaming place PGW does not belong to the pre-stored identifier sets of all PGWs of the user attribution place;

selecting any PGW from all PGWs of a user home location as a target PGW, and sending an identifier of the target PGW to a roaming PGW, so that the roaming PGW forwards the identifier of the target PGW to a Serving Gateway (SGW), the SGW sends a bearer establishment request to the target PGW by using the identifier of the target PGW, and the target PGW sends an identifier of the target PGW according to the bearer establishment request;

and issuing a Policy and Charging Control (PCC) static policy corresponding to the static policy service to the target PGW according to the received identifier of the target PGW, so that the PCC static policy takes effect in a roaming place.

In one embodiment, the identification of the PGW includes any of the following information:

IP address of the S5/S8 interface of the PGW and the hostname of the PGW.

In one embodiment, the error code is sent while the target PGW identifier is sent, so that the roaming PGW forwards the identifier of the target PGW to the SGW according to the error code.

According to another aspect of the embodiments of the present invention, there is provided a method for validating a PCC static policy, where the method includes:

when a user uses a static policy service in a roaming place, sending an identifier of a packet data gateway (PGW) in the roaming place to a Policy and Charging Rule Function (PCRF) of a home location of the user, so that the PCRF sends an identifier of a target PGW under the condition that the identifier of the PGW in the roaming place is determined not to belong to a pre-stored identifier set of all PGWs in the home location of the user, wherein the target PGW is any PGW selected by the PCRF from all PGWs in the home location;

receiving the identifier of the target PGW, sending the identifier of the target PGW to the SGW, so that the SGW sends a bearer establishment request to the target PGW by using the identifier of the target PGW, the target PGW sends the identifier of the target PGW to the PCRF according to the bearer establishment request, and the PCRF issues a policy and charging control PCC static policy corresponding to the static policy service to the target PGW according to the identifier of the target PGW, so that the PCC static policy takes effect in a roaming place.

IP address of the S5/S8 interface of the PGW and the hostname of the PGW.

receiving an identifier of a target packet data gateway (PGW), wherein the identifier of the target PGW is forwarded by a roaming place PGW under the condition that a Policy and Charging Rule Function (PCRF) unit of a user home location determines that the identifier of the roaming place PGW does not belong to a pre-stored identifier set of all PGWs of the user home location, the target PGW is any PGW selected from all PGWs of the home location, and the identifier of the roaming place PGW is sent by the roaming place PGW when the user uses a static policy service in the roaming place;

sending a bearer establishment request to a target PGW according to the identifier of the target PGW, so that the target PGW sends the identifier of the target PGW to a policy and charging rule functional unit PCRF according to the bearer establishment request, and the PCRF issues a Policy and Charging Control (PCC) static policy corresponding to the static policy service to the target PGW according to the identifier of the target PGW, so that the PCC static policy takes effect in a roaming place.

In one embodiment, the method further comprises:

sending the identifier of the target PGW to the network node MME.

According to another aspect of the embodiments of the present invention, there is provided an apparatus for validating a PCC static policy, including:

the first identification receiving module is used for receiving an identification of a user self sent by a packet data gateway (PGW) in a roaming place when the user uses a static policy service in the roaming place;

the determining module is used for determining that the identifier of the roaming place PGW does not belong to the pre-stored identifier sets of all PGWs of the user attribution place;

a first identifier sending module, configured to select any PGW from all PGWs of a user home location as a target PGW, and send an identifier of the target PGW to a roaming destination PGW, so that the roaming destination PGW forwards the identifier of the target PGW to a serving gateway SGW, and the SGW sends a bearer establishment request to the target PGW by using the identifier of the target PGW, where the target PGW sends its identifier according to the bearer establishment request;

and the policy issuing module is used for issuing a Policy and Charging Control (PCC) static policy corresponding to the static policy service to the target PGW according to the received identifier of the target PGW so as to enable the PCC static policy to take effect in a roaming place.

a second identifier sending module, configured to send, when the user uses the static policy service in the roaming place, an identifier of the packet data gateway PGW in the roaming place to the PCRF, so that the PCRF sends the identifier of the target PGW under the condition that it is determined that the identifier of the PGW in the roaming place does not belong to a pre-stored identifier set of all PGWs in the user home place, where the target PGW is any one PGW selected by the PCRF from all PGWs in the home place;

the second identifier receiving module is configured to receive an identifier of the target PGW, and send the identifier of the target PGW to the serving gateway SGW, so that the SGW sends a bearer establishment request to the target PGW by using the identifier of the target PGW, the target PGW sends an identifier of the target PGW to the PCRF according to the bearer establishment request, and the PCRF issues a policy and charging control PCC static policy corresponding to the static policy service to the target PGW according to the identifier of the target PGW, so that the PCC static policy takes effect in a roaming area.

IP address of the S5/S8 interface of the PGW and the hostname of the PGW.

a third identifier receiving module, configured to receive an identifier of a target packet data gateway PGW, where the identifier of the target PGW is forwarded by a roaming destination PGW when a policy and charging rule function unit PCRF of a user home location determines that the identifier of the roaming destination PGW does not belong to a pre-stored identifier set of all PGWs of the user home location, the target PGW is any one PGW selected from all PGWs of the home location, and the identifier of the roaming destination PGW is sent by the roaming destination PGW when the user uses a static policy service in the roaming destination;

and the request sending module is used for sending a bearer establishment request to the target PGW according to the identifier of the target PGW, so that the target PGW sends the identifier of the target PGW to the PCRF according to the bearer establishment request, and the PCRF issues a Policy and Charging Control (PCC) static policy corresponding to the static policy service to the target PGW according to the identifier of the target PGW, so that the PCC static policy takes effect in a roaming place.

According to another aspect of the embodiments of the present invention, there is provided an apparatus for validating a PCC static policy, where the apparatus includes: a processor and a memory storing computer program instructions;

the processor, when executing the computer program instructions, implements a method for validating a PCC static policy as provided by embodiments of the present invention.

According to a further aspect of the embodiments of the present invention, there is provided a computer storage medium having computer program instructions stored thereon, where the computer program instructions, when executed by a processor, implement a method for validating a PCC static policy according to the embodiments of the present invention.

According to the effective method, the effective device, the effective equipment and the effective medium in the embodiment of the invention, when the user uses the static policy service in the roaming place, the PCRF appoints the local PGW by using the pre-stored identification set of the user home PGW, so that the user can select the PGW of the user home place through the PCRF when the static policy is not configured in the PGW of the roaming place.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required to be used in the embodiments of the present invention will be briefly described below, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is a schematic diagram of a configuration of area management policy data.

Fig. 2 is a networking diagram of an existing network PCRF and a PGW.

Fig. 3 is a schematic structural diagram of a system for validating a PCC static policy according to an embodiment of the present invention;

fig. 4 is a flow chart illustrating a method for validating a PCC static policy according to some embodiments of the present invention;

fig. 5 is a flowchart illustrating a method for validating a PCC static policy according to another embodiment of the present invention;

fig. 6 is a flowchart illustrating a method for validating a PCC static policy according to still another embodiment of the present invention;

fig. 7 is a schematic structural diagram of an apparatus for validating a PCC static policy according to some embodiments of the present invention;

fig. 8 is a schematic structural diagram of an apparatus for validating a PCC static policy according to another embodiment of the present invention;

fig. 9 is a schematic structural diagram of an apparatus for validating a PCC static policy according to yet another embodiment of the present invention;

fig. 10 is a block diagram of an exemplary hardware architecture of a PCC static policy validation device according to an embodiment of the present invention.

Detailed Description

Features and exemplary embodiments of various aspects of the present invention will be described in detail below, and in order to make objects, technical solutions and advantages of the present invention more apparent, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not to be construed as limiting the invention. It will be apparent to one skilled in the art that the present invention may be practiced without some of these specific details. The following description of the embodiments is merely intended to provide a better understanding of the present invention by illustrating examples of the present invention.

It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

For better understanding of the present invention, the method, apparatus, device and medium for validating PCC static policy according to the embodiments of the present invention will be described in detail below with reference to the accompanying drawings, and it should be noted that these embodiments are not intended to limit the scope of the present disclosure.

The PCC static policies of the existing network have great workload and risk if all the PCC static policies are configured on all PGWs in the country. In practice, there is an optional static deployment strategy according to the actual demand. Namely, a static strategy with large demand, and all PGWs in the country make data. The static strategy with relatively small demand is independently opened by the city according to the actual demand, prompts the user that the service is only locally used, and suggests the user to stop the original service when roaming occurs.

However, due to the existence of a large number of boundary areas in the existing network or the fact that the user does not perform service interruption during location switching, when the user roams to another city or returns from the roaming place, the original PGW is still used, and the PCRF issues the static policy and fails to take effect correctly in the specified area.

The method for validating the PCC static strategy increases the process of appointing a new user home PGW by the PCRF, ensures that the user can select the PGW of the signed place through the PCRF when the PGW of the roaming place is not configured with the static strategy, realizes that the user can normally use the PCC static strategy in the roaming place under the condition that the PGW of the roaming place has no static strategy, and solves the problem that the current PCC static strategy is limited by the region of the city.

Fig. 3 is a flowchart illustrating an validating system of a PCC static policy according to an embodiment of the present invention. As shown in fig. 3, the system includes a terminal, a PCRF (i.e., PCRF-01) of a terminal home location a, all PGWs of the terminal home location, a network node MME (Mobility Management Entity) of a terminal roaming location B, a PGW (i.e., PGW-03) of the terminal roaming location, and an SGW (i.e., SGW-03) of the terminal roaming location.

The user of the terminal is the user of the home location A, and the PCRF-01 signs a static policy.

In step 01, the terminal moves from the home location A to the roaming location B.

When the terminal moves from the home location A to the roaming location B, if the service is not interrupted, the PGW is not changed according to the characteristic that the 4G is permanently online, the PGW-01 still carries the service, and at the moment, the PCC static strategy still normally takes effect. However, if the service is interrupted and the terminal is restarted or the flight mode is turned on, the terminal needs to be re-attached to the roaming site B, and the process proceeds to step 02.

And step 02, the terminal initiates an attachment request to the MME-03 of the roaming place.

Step 03, the MME-03 sends a bearer establishment request to the PGW-03.

The MME-03 queries a Domain Name System (DNS) to obtain an S5/S8 interface address of a PGW-03 at a roaming place according to an Access Point Name (APN) reported by the terminal to generate a corresponding Domain Name. And initiating a bearer establishment request to the SGW-03 by carrying the S5/S8 interface address of the PGW-03 in the 'PDN GW address' field of the session request message. And the SGW-03 transfers the message to the corresponding PGW-03.

Step 04, the PGW-03 sends a Credit Control Request-Initial (CCR-I) message to the PCRF-01.

After receiving the message sent by the SGW-03, the PGW-03 adds AN "AN-GW-Address" extension field to a CCR-I message initiated by the PCRF-01 to notify the PCRF-01 of the S5/S8 interface Address of the PGW-03 currently carrying the user service.

Step 05, the PCRF-01 returns a Credit Control corresponding Initial (CCA-I) message to the PGW-03.

In the embodiment of the invention, PCRF-01 analyzes the CCR-I message, and firstly judges whether the user signs a PCC static strategy.

And if not, the PCRF-01 replies CCA-I information to the CCR-I information and sends a trigger and a rule name corresponding to the PCC static strategy signed by the user down. At this time, the "Result-Code" field in the parsing message is filled with 2xxx to indicate successful interaction. Then step 06 and step 07 are executed to inform the terminal that the attachment is successful.

And if the user signs the PCC static strategy, the PCRF-01 judges whether the Address in the 'AN-GW-Address' field reported in the CCR-I information is in AN S5/S8 Address list in the static strategy stored in advance. The address list of the static policy pre-saved by the PCRF-01 comprises S5/S8 address lists of all PGWs of the user home.

If the S5/S8 interface address of the PGW-03 belongs to the address list of the static policy, step 06 and step 07 are performed to inform the terminal that the attachment is successful.

If the interface Address of the S5/S8 of the PGW-03 does not belong to the Address list of the static policy, AN error code is returned in the CCA-I, and the interface Address of the S5/S8 of a local PGW (such as PGW-01) is selected from all PGWs of the home location A in a random or polling mode and returned to the PGW-03 through a CCA-I information 'AN-GW-Address' field. Then step 08 is executed to notify the SGW-03 to initiate a bearer establishment request to the PGW-01.

As AN example, the PCRF-01 selects the PGW-01 in the local PGW list, and informs the PGW-03 of the Address 1.1.1.1 of the PGW-01 through the "AN-GW-Address" field, and fills 3333 in the "Result-Code" field. Wherein 3xxx indicates a protocol error, where 3333 is defined as a case where the user who has subscribed to the static policy uses the static policy in a roaming area, and then step 08 is executed to notify the SGW-03 that a bearer establishment request needs to be initiated to the PGW-01.

When the PGW-03 receives the CCA-I message which is sent by the PCRF-01 and comprises the 3333 error code, the original bearer establishment request is rejected, and the SGW-03 is informed to initiate the bearer establishment request to the new PGW-01.

And step 06, the PGW-03 sends a bearer establishment response to the MME-03.

And the PGW-03 performs matching of PGW side configuration according to the static policy rule name issued by the PCRF-01. Because no corresponding policy configuration exists on the PGW-03, the static policy is not effective, but the use of the user data service is not affected. The PGW-03 sends a bearer establishment response to the MME-03. Then step 07 is entered.

Step 07, the attachment is successful.

The base station and the terminal establish a wireless side S1 bearing link, and the MME-03 informs the terminal of successful attachment.

And step 08, the PGW-03 returns a bearer establishment response to the SGW-03.

In the embodiment of the invention, the PGW-03 carries out message analysis on the CCA-I message replied by the PCRF-01, finds that a 'Result-Code' field in the message returns AN error Code 3333, and obtains a PGW-01S5/S8 interface Address (taking PGW-01 as AN example) issued by the PCRF-01 through AN 'AN-GW-Address' field in the message. The PGW-03 replies a Create Session Response (Create Session Response) message to the SGW-03, wherein a 'cause' field informs the SGW-03 that the establishment of the bearer fails, and the reason of the failure is a 'PDN GW change' field fed back by the 'cause-result' field. When the PGW-03 receives the PDN GW change field, the PGW-03 changes the originally filled interface address of the S5/S8 of the PGW-03 to the interface address 1.1.1.1 of the PGW-01S5/S8 issued by the PCRF and informs the SGW-03.

And step 09, the SGW-03 initiates a bearer establishment request to the PGW-01 again according to the address of the home location PGW-01 returned by the PGW-03 in the field of the PDN GW addresses.

Step 10, after receiving the bearer establishment request, the PGW-01 initiates CCR-I information to the PCRF-01 to apply for establishing an IP-Connectivity Access Network (IP-CAN) session. In the CCR-I message, PGW-01 also fills its own S5/S8 interface Address in the newly added 'AN-GW-Address' extension field.

And step 11, the PCRF-01 issues the static policy of the user to the PGW-01.

And the PCRF-01 receives the CCR-I information, finds that the user is a static signed user, and judges that the S5/S8 interface address reported by the PGW-01 belongs to the S5/S8 interface address configured in the static policy, so that the PCRF-01 issues the static policy of the user to the PGW-01.

And step 12, the PGW-01 sends a bearer establishment response message to the SGW-03 to inform the SGW-03 to complete establishment of a bearer link between the PGW-01 and the SGW-03 and feed back related information of the PGW-01.

And step 13, the SGW-03 sends the address corresponding to the PGW-01 to the MME-03.

After the bearer link is established between the PGW-01 and the SGW-03, the SGW-03 returns a successful bearer establishment result to the MME-03, and informs the MME-03 of the address corresponding to the PGW-01 through a 'PDN GW addresses' field. The MME-03 finds that the address is inconsistent with the locally stored PGW address, knows that the PGW is changed, and modifies the locally stored PGW information according to the message. Namely, the locally stored PGW information is changed to the address corresponding to the PGW-01.

Step 14, the base station establishes a wireless side S1 bearer link with the terminal, and the MME-03 notifies the terminal that the attachment is successful.

In the embodiment of the invention, based on a Diameter protocol adopted between the PGW and the PCRF, AN 'AN-GW-Address' field is newly added in a CCA message interacted between the PCRF and the PGW to record the addresses of all local PGW S5/S8 interfaces. If the reported S5/S8 interface address of the PGW does not belong to the address list of the static policy, the S5/S8IP address of the PGW of the user home location can be selected randomly or by a polling mechanism to return to the PGW of the roaming location.

When a new local static policy is added to the PCRF, a local PGW S5/S8 interface address field is added to the condition issued by the rule to request configuration, and S5/S8 interface addresses of all local PGWs are filled.

The specific implementation method is that the PCRF records S5/S8 interface addresses of all local PGWs, and when a CCR-I session establishment request reported by the PGW is received, the PGW reports the S5/S8 interface addresses of the PGW through a newly-added 'AN-GW-Address' field. And the PCRF judges whether the reported PGW S5/S8 Address is the local PGW S5/S8 Address in the record of the static policy or not according to the 'AN-GW-Address' field. If the reported address does not belong to the local PGW address, returning a CCA-I message with an error code of 3333, and rejecting the session establishment request. Meanwhile, AN 'AN-GW-Address' field is newly added in the CCA-I message, one PGW device on the user subscription place is selected in a random or polling mode, and the S5/S8 Address is returned to the PGW on the roaming place.

After receiving the CCA-I message, the PGW at the roaming destination informs the SGW of the change of the bearer establishment according to the error code, and the SGW needs to initiate a bearer establishment request according to a new PGW address fed back by the PCRF.

And the SGW initiates a bearing request to the signed PGW again and informs the MME that the bearing is successfully established and the PGW is changed, the MME finishes the modification of the locally stored PGW information according to the address of the signed PGW fed back by the SGW and informs the user of successful attachment, thereby ensuring that the user signed the PCC static strategy always uses the home PGW and ensuring that the PCC static strategy can be normally used in a roaming place. And the MME modifies the locally stored PGW address according to the PGW address information returned by the SGW.

In the embodiment of the invention, the flow of appointing a new PGW by the PCRF is added, so that when the static policy is not configured in the PGW of the roaming place, the user can select the PGW of the signed place through the PCRF, and the static policy can be taken effect in different places.

In the embodiment of the present invention, after the PGW selected by the MME fails to meet the requirement of the static policy, the SGW may reinitiate the bearer establishment request according to the PGW address issued by the PCRF, so as to ensure that the user can successfully attach.

The method for validating the PCC static strategy provided by the embodiment of the invention does not influence the common users of the current network, is realized by depending on the current mechanism of the network element, and solves the problem that the current static strategy can not be validated nationwide without increasing data configuration.

In embodiments of the present invention, the hostname of the PGW may also be utilized in place of the S5/S8 interface address. That is to say, the scheme may be implemented by writing unique identification information capable of identifying the PGW in the "AN-GW-Address" field.

It should be noted that, when the S5/S8 interface address is replaced by a host name, between step 08 and step 09, after the SGW-03 acquires the host name of the PGW-01, it needs to acquire the IP address corresponding to the host name of the PGW-01 from the DNS, and then sends a bearer establishment request to the PGW-01 according to the IP address.

Fig. 4 is a flowchart illustrating an effective method applied to a PCC static policy on the PCRF side according to an embodiment of the present invention. As shown in fig. 4, an validating method 400 applied to a PCC static policy on a PCRF side in the embodiment of the present invention includes the following steps:

s410, when the user uses the static policy service in the roaming place, receiving the self identification sent by the packet data gateway PGW in the roaming place.

S420, determining that the identifier of the PGW at the roaming location does not belong to the pre-stored identifier sets of all PGWs at the user home location.

And S430, if not, selecting any PGW from all PGWs of the user home location as a target PGW, and sending the identifier of the target PGW to the roaming PGW, so that the roaming PGW forwards the identifier of the target PGW to the serving gateway SGW, and the SGW sends a bearer establishment request to the target PGW by using the identifier of the target PGW, and the target PGW sends the identifier of the target PGW according to the bearer establishment request.

And S440, according to the received identifier of the target PGW, issuing a Policy and Charging Control (PCC) static policy corresponding to the static policy service to the target PGW, so that the PCC static policy takes effect in a roaming place.

In an embodiment of the present invention, the identification of the PGW includes any one of the following information:

IP of the S5/S8 interface of the PGW and hostname of the PGW.

In the embodiment of the present invention, the error code is sent while the target PGW identifier is sent, so that the roaming PGW forwards the identifier of the target PGW to the SGW according to the error code.

Fig. 5 is a flowchart illustrating an implementation method of a PCC static policy applied to a PGW side of a roaming destination according to an embodiment of the present invention. As shown in fig. 5, an implementation method 500 of the PCC static policy applied to the PGW side of the roaming destination in the embodiment of the present invention includes the following steps:

s510, when the user uses the static policy service in the roaming area, sending an identifier of the PGW of the roaming area to the PCRF, so that the PCRF sends the identifier of the target PGW under the condition that it is determined that the identifier of the PGW of the roaming area does not belong to the pre-stored identifier sets of all PGWs of the user home area, where the target PGW is any PGW selected by the PCRF from all PGWs of the home area.

S520, receiving the identifier of the target PGW, and sending the identifier of the target PGW to the SGW, so that the SGW sends a bearer establishment request to the target PGW by using the identifier of the target PGW, the target PGW sends its identifier to the PCRF according to the bearer establishment request, and the PCRF issues a policy and charging control PCC static policy corresponding to the static policy service to the target PGW according to the identifier of the target PGW, so as to enable the PCC static policy to take effect in a roaming area.

IP address of the S5/S8 interface of the PGW and the hostname of the PGW.

Fig. 6 is a flowchart illustrating an implementation method of a PCC static policy applied to a SGW side of a roaming destination according to an embodiment of the present invention. As shown in fig. 6, a method 600 for validating a PCC static policy applied to an SGW side of a roaming destination in the embodiment of the present invention includes the following steps:

s610, receiving an identifier of a target packet data gateway PGW, where the identifier of the target PGW is forwarded by a roaming PGW when the PCRF of the policy and charging rule function unit of the user home location determines that the identifier of the roaming PGW does not belong to a pre-stored identifier set of all PGWs of the user home location, the target PGW is any one PGW selected from all PGWs of the home location, and the identifier of the roaming PGW is sent by the roaming PGW when the user uses a static policy service in the roaming location.

S620, sending a bearer establishment request to the target PGW according to the identifier of the target PGW, so that the target PGW sends its own identifier to the PCRF according to the bearer establishment request, and the PCRF issues a policy and charging control PCC static policy corresponding to the static policy service to the target PGW according to the identifier of the target PGW, so that the PCC static policy takes effect in the roaming area.

In an embodiment of the present invention, the method for validating the PCC static policy further includes:

sending the identifier of the target PGW to the network node MME.

Fig. 7 is a schematic structural diagram illustrating an apparatus for validating a PCC static policy according to an embodiment of the present invention. As shown in fig. 7, the apparatus 700 for validating the PCC static policy includes:

the first identity receiving module 710 is configured to receive an identity of a user, sent by a packet data gateway PGW of a roaming place, when the user uses a static policy service in the roaming place.

A determining module 720, configured to determine that the identifier of the PGW in the roaming location does not belong to the pre-stored identifier set of all PGWs in the user home location.

The first identifier sending module 730 is configured to select any PGW from all PGWs of the user home location as a target PGW, and send an identifier of the target PGW to the roaming destination PGW, so that the roaming destination PGW forwards the identifier of the target PGW to the serving gateway SGW, and the SGW sends a bearer establishment request to the target PGW by using the identifier of the target PGW, and the target PGW sends its identifier according to the bearer establishment request.

And the policy issuing module 740 is configured to issue the policy and charging control PCC static policy corresponding to the static policy service to the target PGW according to the received identifier of the target PGW, so that the PCC static policy takes effect in the roaming area.

Fig. 8 is a schematic structural diagram illustrating an apparatus for validating a PCC static policy according to another embodiment of the present invention. As shown in fig. 8, the apparatus 800 for validating the PCC static policy includes:

a second identifier sending module 810, configured to send, when the user uses the static policy service in the roaming place, an identifier of the packet data gateway PGW in the roaming place to the PCRF, so that the PCRF sends the identifier of the target PGW under the condition that it is determined that the identifier of the PGW in the roaming place does not belong to the pre-stored identifier sets of all PGWs in the user's home place, where the target PGW is any PGW selected by the PCRF from all PGWs in the home place.

The second identifier receiving module 820 is configured to receive an identifier of the target PGW, and send the identifier of the target PGW to the serving gateway SGW, so that the SGW sends a bearer establishment request to the target PGW by using the identifier of the target PGW, the target PGW sends an identifier of the target PGW to the PCRF according to the bearer establishment request, and the PCRF issues a policy and charging control PCC static policy corresponding to the static policy service to the target PGW according to the identifier of the target PGW, so as to enable the PCC static policy to take effect in a roaming area.

IP address of the S5/S8 interface of the PGW and the hostname of the PGW.

Fig. 9 is a schematic structural diagram illustrating an apparatus for validating a PCC static policy according to still another embodiment of the present invention. As shown in fig. 9, the apparatus 900 for validating the PCC static policy includes:

a third identifier receiving module 910, configured to receive an identifier of a target packet data gateway PGW, where the identifier of the target PGW is forwarded by a roaming destination PGW when the PCRF of the policy and charging rule function unit of the user home location determines that the identifier of the roaming destination PGW does not belong to a pre-stored identifier set of all PGWs of the user home location, the target PGW is any one PGW selected from all PGWs of the home location, and the identifier of the roaming destination PGW is sent by the roaming destination PGW when the user uses a static policy service in the roaming destination.

The request sending module 920 is configured to send a bearer establishment request to the target PGW according to the identifier of the target PGW, so that the target PGW sends an identifier of the target PGW to the PCRF according to the bearer establishment request, and the PCRF issues a policy and charging control PCC static policy corresponding to the static policy service to the target PGW according to the identifier of the target PGW, so that the PCC static policy takes effect in the roaming area.

Other details of the apparatus for validating a PCC static policy according to the embodiment of the present invention are similar to the method according to the embodiment of the present invention described above with reference to fig. 4 to 6, and are not described herein again.

The method and apparatus for validating a PCC static policy according to the embodiments of the present invention described in conjunction with fig. 4 to fig. 9 may be implemented by a validation device of the PCC static policy. Fig. 10 is a schematic diagram of a hardware structure 1000 of a device for validating a PCC static policy according to an embodiment of the present invention.

As shown in fig. 10, the validation device 1000 for the PCC static policy in this embodiment includes: the system comprises a processor 1001, a memory 1002, a communication interface 1003 and a bus 1010, wherein the processor 1001, the memory 1002 and the communication interface 1003 are connected through the bus 1010 and complete mutual communication.

In particular, the processor 1001 may include a Central Processing Unit (CPU), or A Specific Integrated Circuit (ASIC), or may be configured as one or more integrated circuits implementing an embodiment of the present invention.

Memory 1002 may include mass storage for data or instructions. By way of example, and not limitation, memory 1002 may include an HDD, floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or a Universal Serial Bus (USB) drive or a combination of two or more of these. Memory 1002 may include removable or non-removable (or fixed) media, where appropriate. The memory 1002 may be internal or external to the validating device 1000 of the PCC static policy, where appropriate. In a particular embodiment, the memory 1002 is non-volatile solid-state memory. In a particular embodiment, the memory 1002 includes Read Only Memory (ROM). Where appropriate, the ROM may be mask-programmed ROM, Programmable ROM (PROM), Erasable PROM (EPROM), Electrically Erasable PROM (EEPROM), electrically rewritable ROM (EAROM), or flash memory or a combination of two or more of these.

The communication interface 1003 is mainly used for implementing communication between modules, apparatuses, units and/or devices in the embodiment of the present invention.

Bus 1010 comprises hardware, software, or both to couple the components of validating device 1000 of the PCC static policy to each other. By way of example, and not limitation, a bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hypertransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an infiniband interconnect, a Low Pin Count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a video electronics standards association local (VLB) bus, or other suitable bus or a combination of two or more of these. Bus 1010 may include one or more buses, where appropriate. Although specific buses have been described and shown in the embodiments of the invention, any suitable buses or interconnects are contemplated by the invention.

That is, the validating device 1000 of the PCC static policy illustrated in fig. 10 may be implemented to include: a processor 1001, a memory 1002, a communication interface 1003, and a bus 1010. The processor 1001, the memory 1002, and the communication interface 1003 are connected by a bus 1010 and communicate with each other. The memory 1002 is used to store program codes; the processor 1001 executes a program corresponding to the executable program code by reading the executable program code stored in the memory 1002, so as to perform the method for validating the PCC static policy in any embodiment of the present invention, thereby implementing the method and apparatus for validating the PCC static policy described in conjunction with fig. 4 to 9.

The embodiment of the invention also provides a computer storage medium, wherein the computer storage medium is stored with computer program instructions; the computer program instructions, when executed by a processor, implement a method for validating a PCC static policy provided by embodiments of the present invention.

It is to be understood that the invention is not limited to the specific arrangements and instrumentality described above and shown in the drawings. A detailed description of known methods is omitted herein for the sake of brevity. In the above embodiments, several specific steps are described and shown as examples. However, the method processes of the present invention are not limited to the specific steps described and illustrated, and those skilled in the art can make various changes, modifications and additions or change the order between the steps after comprehending the spirit of the present invention.

The functional blocks shown in the above structural block diagrams may be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, it may be, for example, an electronic circuit, an Application Specific Integrated Circuit (ASIC), suitable firmware, plug-in, function card, or the like. When implemented in software, the elements of the invention are the programs or code segments used to perform the required tasks. The program or code segments may be stored in a machine-readable medium or transmitted by a data signal carried in a carrier wave over a transmission medium or a communication link. A "machine-readable medium" may include any medium that can store or transfer information. Examples of a machine-readable medium include electronic circuits, semiconductor memory devices, ROM, flash memory, Erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, Radio Frequency (RF) links, and so forth. The code segments may be downloaded via computer networks such as the internet, intranet, etc.

As will be apparent to those skilled in the art, for convenience and brevity of description, the specific working processes of the systems, modules and units described above may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again. It should be understood that the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive various equivalent modifications or substitutions within the technical scope of the present invention, and these modifications or substitutions should be covered within the scope of the present invention.

Claims

1. A method for validating a PCC static policy, the method comprising:

determining that the identifier of the roaming place PGW does not belong to a pre-stored identifier set of all PGWs of the user home location;

selecting any PGW from all PGWs of the user home location as a target PGW, and sending an identifier of the target PGW to the roaming location PGW, so that the roaming location PGW forwards the identifier of the target PGW to a Serving Gateway (SGW), and the SGW sends a bearer establishment request to the target PGW by using the identifier of the target PGW, and the target PGW sends an identifier of the target PGW according to the bearer establishment request;

and issuing a Policy and Charging Control (PCC) static policy corresponding to the static policy service to the target PGW according to the received identifier of the target PGW, so that the PCC static policy takes effect in the roaming place.

2. The method of claim 1, wherein the identification of the PGW comprises any one of the following information:

IP address of the S5/S8 interface of the PGW and the hostname of the PGW.

3. The method of claim 1, wherein an error code is sent while sending the target PGW identifier, so that the roaming PGW forwards the identifier of the target PGW to the SGW according to the error code.

4. A method for validating a PCC static policy, the method comprising:

when a user uses a static policy service in a roaming place, sending an identifier of a packet data gateway (PGW) in the roaming place to a Policy and Charging Rule Function (PCRF) in a home place of the user, so that the PCRF sends an identifier of a target PGW under the condition that the identifier of the PGW in the roaming place is determined not to belong to a pre-stored identifier set of all PGWs in the user home place, wherein the target PGW is any PGW selected by the PCRF from all PGWs in the home place;

receiving the identifier of the target PGW, and sending the identifier of the target PGW to a Serving Gateway (SGW), so that the SGW sends a bearer establishment request to the target PGW by using the identifier of the target PGW, the target PGW sends an identifier of the target PGW to the PCRF according to the bearer establishment request, and the PCRF issues a Policy and Charging Control (PCC) static policy corresponding to the static policy service to the target PGW according to the identifier of the target PGW, so that the PCC static policy takes effect in the roaming place.

5. The method of claim 4, wherein the identification of the PGW comprises any one of the following information:

IP address of the S5/S8 interface of the PGW and the hostname of the PGW.

6. A method for validating a PCC static policy, the method comprising:

sending a bearer establishment request to the target PGW according to the identifier of the target PGW, so that the target PGW sends an identifier of the target PGW to a Policy and Charging Rules Function (PCRF) according to the bearer establishment request, and the PCRF issues a Policy and Charging Control (PCC) static policy corresponding to the static policy service to the target PGW according to the identifier of the target PGW, so that the PCC static policy takes effect in the roaming place.

7. The method of claim 6, further comprising:

and sending the identifier of the target PGW to a network node MME.

8. An apparatus for validating a PCC static policy, the apparatus comprising:

a determining module, configured to determine that the identifier of the roaming destination PGW does not belong to a pre-stored identifier set of all PGWs of the user home location;

a first identifier sending module, configured to select any PGW from all PGWs of the user home location as a target PGW, and send an identifier of the target PGW to the roaming destination PGW, so that the roaming destination PGW forwards the identifier of the target PGW to a serving gateway SGW, and the SGW sends a bearer establishment request to the target PGW by using the identifier of the target PGW, where the target PGW sends an identifier of the target PGW according to the bearer establishment request;

and a policy issuing module, configured to issue a policy and charging control PCC static policy corresponding to the static policy service to the target PGW according to the received identifier of the target PGW, so that the PCC static policy takes effect in the roaming area.

9. An apparatus for validating a PCC static policy, the apparatus comprising:

a second identifier sending module, configured to send, when a user uses a static policy service in a roaming place, an identifier of a packet data gateway (PGW) in the roaming place to a Policy and Charging Rule Function (PCRF) of a home location of the user, so that the PCRF sends an identifier of a target PGW when determining that the identifier of the PGW in the roaming place does not belong to a pre-stored identifier set of all PGWs in the home location of the user, where the target PGW is any PGW selected by the PCRF from all PGWs in the home location;

a second identifier receiving module, configured to receive an identifier of the target PGW, and send the identifier of the target PGW to a serving gateway SGW, so that the SGW sends a bearer establishment request to the target PGW by using the identifier of the target PGW, where the target PGW sends an identifier of the target PGW to the PCRF according to the bearer establishment request, and the PCRF issues a policy and charging control PCC static policy corresponding to the static policy service to the target PGW according to the identifier of the target PGW, so as to implement that the PCC static policy takes effect in the roaming area.

10. The apparatus of claim 9, wherein the identification of the PGW comprises any one of the following information:

IP address of the S5/S8 interface of the PGW and the hostname of the PGW.

11. An apparatus for validating a PCC static policy, the apparatus comprising:

a third identifier receiving module, configured to receive an identifier of a target packet data gateway PGW, where the identifier of the target PGW is forwarded by a roaming destination PGW when a policy and charging rule function unit PCRF of the user home determines that an identifier of the roaming destination PGW does not belong to a pre-stored identifier set of all PGWs of the user home, the target PGW is any one PGW selected from all PGWs of the home, and the identifier of the roaming destination PGW is sent by the roaming destination PGW when the user uses a static policy service in the roaming destination;

a request sending module, configured to send a bearer establishment request to the target PGW according to the identifier of the target PGW, so that the target PGW sends an identifier of the target PGW to a policy and charging rules function unit PCRF according to the bearer establishment request, and the PCRF issues a policy and charging control PCC static policy corresponding to the static policy service to the target PGW according to the identifier of the target PGW, so that the PCC static policy takes effect in the roaming area.

12. An apparatus for validating a PCC static policy, the apparatus comprising: a processor and a memory storing computer program instructions;

the processor, when executing the computer program instructions, implements a method for validating a PCC static policy according to any one of claims 1 to 3, or a method for validating a PCC static policy according to any one of claims 4 to 5, or a method for validating a PCC static policy according to any one of claims 6 to 7.

13. A computer storage medium having stored thereon computer program instructions which, when executed by a processor, implement a method for validating a PCC static policy according to any one of claims 1 to 3, or a method for validating a PCC static policy according to any one of claims 4 to 5, or a method for validating a PCC static policy according to any one of claims 6 to 7.