WO2011063688A1

WO2011063688A1 - Method and system for selecting policy and charging rules function entity

Info

Publication number: WO2011063688A1
Application number: PCT/CN2010/077887
Authority: WO
Inventors: 周晓云; 芮通; 孙闵
Original assignee: 中兴通讯股份有限公司
Priority date: 2009-11-25
Filing date: 2010-10-19
Publication date: 2011-06-03
Also published as: CN102075894B; CN102075894A

Abstract

A method for selecting Policy and Charging Rules Function (PCRF) entity is provided in this invention, the method includes that a Diameter Routing Agent (DRA) selects the same PCRF entity for at least two users sharing the subscription information. A system for selecting PCRF entity is further provided in this invention, the system includes a selection unit, which is provided in the DRA, for selecting the same PCRF entity for the at least two users sharing the subscription information. By applying the method and system provided in the present invention, the same PCRF entity is ensured to be selected for all the users sharing the subscription information, thus preventing the policy and charging control from confliction. The scheme of the present invention is simple and practical.

Description

Policy and charging rule function entity selection method and system

The present invention relates to a technology for determining a Policy and Charging Rules Function (PCRF) in a wireless communication system, and more particularly to a policy and charging rule function entity in an evolved packet system (EPS, Evolved Packet System) Selection method and system. Background technique

1 is a schematic structural diagram of a 3GPP evolved packet system. As shown in FIG. 1, an 3GPP evolved packet system (EPS, Evolved Packet System) is an evolved universal mobile communication system terrestrial radio access network (E-UTRAN, Evolved Universal Terrestrial Radio Access Network). ), Mobility Management Entity (MME), Serving Gateway (S-GW), Packet Data Network Gateway (PDN GW or P-GW, Packet Data Network Gateway), Home Subscriber Server (HSS, Home Subscriber) Server), 3GPP's AAA, Authentication, Authorization and Accounting, and Policy and Charging Rules Function (PCRF) and other supporting nodes.

The MME is used for control plane related operations such as mobility management, non-access stratum signaling processing, and user mobility management context management; the S-GW is an access gateway device connected to the E-UTRAN, in the E-UTRAN and The data is forwarded between the P-GWs and used to buffer the paging waiting data. The P-GW is a border gateway between the EPS and the PDN, and is used for PDN access and forwarding data between the EPS and the PDN.

EPS supports interworking with non-3GPP systems. The interworking with the non-3GPP system is implemented through the S2a, S2b, and S2c interfaces, and the P-GW serves as an anchor point between the 3GPP system and the non-3GPP system. among them, Non-3GPP systems are classified into trusted non-3GPP access systems and untrusted non-3GPP access systems. The trusted non-3GPP access system can be directly connected to the P-GW through the S2a interface; the untrusted non-3GPP access system needs to be connected to the P-GW via an evolved Packet Data Gateway (ePDG), ePDG and P- The GW is an S2b interface. The S2c interface provides user plane-related control and mobility support between the user equipment (UE, User Equipment) and the P-GW. The supported mobility management protocol is dual-stack mobile IPv6 (DSMIPv6, Moblie IPv6 support for dual stack). Hosts and Routers).

The EPS system introduces the Policy Charging Control (PCC, Policy and Charging Control) function framework to perform dynamic policy charging control for user service access. Figure 2 is a schematic diagram of a PCC structure in a non-roaming scenario in the Rel-8. As shown in Figure 2, an application function entity (AF) is used to provide access points for service applications. The network resources used by these service applications are required. Perform dynamic policy control. When the parameters are negotiated on the service plane, the AF transmits the related service information to the PCRF. If the service information is consistent with the PCRF policy, the PCRF accepts the negotiation; otherwise, the PCRF rejects the negotiation and gives the business parameters acceptable to the PCRF upon feedback. The AF can then return these parameters to the user equipment (UE, User Equipment). The interface between AF and PCRF is the Rx interface.

The PCRF is the core of the PCC and is responsible for policy decision making and billing rules. The PCRF provides network control rules based on service data flows, including traffic data flow detection, Gating Control, Quality of Service (QoS) control, and data flow based charging rules. The PCRF sends its policy and charging rules to the Policy and Control Enforcement Function (PCEF). At the same time, the PCRF also needs to ensure that these rules are consistent with the user's subscription information. The basis for formulating the policy and charging rules by the PCRF includes: obtaining information related to the service from the AF, obtaining the subscription information related to the user policy charging control from the SPR (Spent Profile Repository), and obtaining the subscription information from the PCEF through the Gx interface. Information about the network associated with the bearer. The PCEF is usually located in the gateway (GW, Gate Way) and performs the policy and charging rules established by the PCRF on the bearer plane. The PCEF detects the service data flow according to the service data flow filter in the rule sent by the PCRF, and then executes the policy and charging rules formulated by the PCRF for these service data flows. When the bearer is established, the PCEF performs QoS authorization according to the rules sent by the PCRF, and performs gate control according to the execution of the AF. At the same time, the PCEF triggers reporting of events occurring on the bearer network according to events subscribed by the PCRF. According to the charging rule sent by the PCRF, the PCEF performs a corresponding service data flow charging operation, and the charging can be either online charging or offline charging. In the case of online charging, the PCEF needs to perform credit management together with the Online Charging System (OCS). When offline charging, the PCEF and the offline charging system (OFCS) exchange relevant accounting information. The interface between the PCEF and the PCRF is a Gx interface, the interface with the OCS is a Gy interface, and the interface between the OFCS and the OFCS is a Gz interface. PCEFs are generally located on the gateway of the network, such as the Packet Data Network Gateway (PDN-GW) of EPS, the GPRS Gateway Support Node (GGSN) in the General Packet Radio Service (GPRS), and the interconnected wireless LAN. Packet Data Gateway (PDG) in (I-WLAN, Interworking WLAN, ).

The Bearer Binding and Event Reporting Function (BBERF) is usually located in the Access Network Gateway. For example, when the user equipment accesses the EPS through the E-UTRAN, and the proxy mobile internet protocol version 6 (ΡΜΙΡνό, Proxy Mobile Internet Protocol version 6) protocol is used between the E-UTRAN and the P-GW, the S-GW exists. BBERF. When a user equipment accesses through a trusted non-3GPP access network, a BBERF is also present in the trusted non-3GPP access gateway.

The SPR stores user policy charging control subscription information related to policy control and charging. The interface between SPR and PCRF is the Sp interface.

The Online Charging System (OCS) and PCEF are used to control and manage user credits in the online charging mode. The offline charging system (OFCS) and the PCEF are used to complete the charging operation in the offline charging mode.

There may be multiple PCRF nodes in a public land mobile phone network (PLMN, Public Land Mobile Network, PL), and all PCRF nodes belong to one or more Diameter domains. A UE-to-PDN network connection is called an IP-Connected Network (IP-Access) network session. The policy charging control information for an IP-CAN session is determined by only one PCRF. In order to ensure that all PCEFs or BBERFs associated with an IP-CAN session are associated with the same PCRF, the EPS introduces a logical function module Diameter Routing Agent (DRA) in each Diameter domain. „ UE is to be established to a PDN. In the IP-CAN session, the DRA selects a PCRF for this IP-CAN session, and the PCEF or BBERF associated with this IP-CAN session is associated with the selected PCRF by the DRA. At the same time, the DRA can also use this IP-CAN. The session related AF is associated to the selected PCRF.

In the prior art, the DRA may select different PCRFs for different IP-CAN sessions of the UE according to the network policy (in this case, multiple IP-CAN sessions are established by the same UE), and may also be all IPs of the UE. The CAN session selects the same PCRF, ie the DRA selection PCRF can be based on the UE level or based on the IP-CAN level.

However, in some application scenarios, there is a problem in selecting PCRF based on the above two levels. For example, for a family package, multiple users participating in the package share the total contracted usage (this can be time, traffic, or other information), which is stored in the SPR. When the user participating in the package goes online to establish an IP-CAN session, the SPR sends the total contracted amount to the PCRF responsible for policy charging control of the user's IP-CAN session, and the PCRF establishes a usage detection control strategy. At this time, if another user who subscribes to the package goes online to establish an IP-CAN session, since the PCRF is selected in the prior art as the UE level or the IP-CAN session level, the PCRF selected by the DRA for different users may be different. Since SPR has been total The dosage has been issued to the previous PCRF, and if it is sent to the next PCRF, the usage detection control will conflict.

To sum up the above problems, it can be seen that when multiple users share a subscription information (such as the total subscription allowance), if the IP-CAN established by multiple users is controlled by different PCRFs, the policy will appear. Fee control conflicts. Summary of the invention

In view of this, the main purpose of the present invention is to provide a method and system for selecting a policy and charging rule function entity, which can select the same PCRF for two or more users sharing subscription information, and avoid users sharing the subscription information. Policy charging control conflicts occur between them.

In order to achieve the above object, the technical solution of the present invention is achieved as follows:

A method for selecting a policy and charging rule functional entity, including:

The DRA selects the same policy and charging rule function entity PCRF for more than two users sharing the subscription information.

Preferably, the shared subscription information is specifically:

The IP-connected network IP-CAN session sharing subscription information established by the two or more users for accessing the same packet data network PDN;

Or the IP-CAN session shared by the two or more users for accessing two or more PDNs;

Alternatively, the IP-CAN session established by the two or more users to access all PDNs shares subscription information.

Preferably, the two or more users sharing the subscription information select the same PCRF, including:

After receiving the gateway control session establishment message sent by the BBERF or the IP-CAN session establishment indication message sent by the PCEF, the DRA controls the session identification message or the user identification information in the IP-CAN session establishment indication message according to the gateway or / and the label of the PDN that the user wants to access The identification information determines whether the PCRF has been selected for other users sharing the subscription information with the user, and the PCRF selected for other users is used as the PCRF selected by the user.

Preferably, the DRA obtains the shared subscription user list information of the user by using a user subscription database SPR or an associated user database CSDB, where the shared subscription user list includes identification information of two or more users sharing the subscription information, or includes two The identification information of more than one user and the PDN network identification information for the shared subscription information.

Preferably, the method further includes:

Sending a shared subscription subscriber list request message to the SPR or the CSDB when the DRA is restarted;

The SPR or the CSDB returns an acknowledgement message to the DRA, where the acknowledgement message includes the SPR or the shared subscription subscriber identity list information currently stored by the CSDB.

Preferably, the method further includes:

When the SPR or the shared subscription user identifier list in the CSDB is updated, the shared subscription subscriber identity list update request message is sent to the DRA, and the shared subscription subscriber identity list update request message includes an updated shared subscription subscriber identity list. Information

The DRA replaces the updated shared subscription user identification list information with the original shared subscription user identification list information, and returns an acknowledgement message to the SPR or the CSDB.

A system for selecting a policy and charging rule functional entity, including:

The selection unit, located in the DRA, is used to select the same PCRF for more than two users sharing the subscription information.

Preferably, the shared subscription information is specifically:

Or the IP-CAN session sharing subscription information established by the two or more users to access two or more PDNs; Alternatively, the IP-CAN session shared by the two or more users for accessing all PDNs shares subscription information.

Preferably, the selecting unit comprises a receiving subunit, a determining subunit and a selecting subunit, wherein:

a receiving subunit, configured to receive a gateway control session establishment message sent by the BBERF or an IP-CAN session establishment indication message sent by the PCEF;

a determining subunit, configured to determine, according to the gateway control session establishment message or the user identification information in the IP-CAN session establishment indication message or/and the identification information of the PDN that the user wants to access, whether it is shared with the user Other users who subscribe to the information select PCRF, which triggers the selection subunit;

A subunit is selected for using the PCRF selected for the other user as the PCRF selected for the user.

Preferably, the system further includes: an acquiring unit, located in the DRA, configured to acquire shared subscription user list information of the user by using an SPR or a CSDB, where the shared subscription user list includes two or more shared subscription information The identification information of the user, or the identification information of the two or more users and the PDN network identification information for the shared subscription information.

Preferably, the system further comprises:

a first sending unit, located in the DRA, configured to send a shared subscription subscriber list request message to the SPR or the CSDB when the DRA is restarted;

The second sending unit is located in the SPR or the CSDB, and is configured to return an acknowledgement message to the DRA, where the acknowledgement message includes the SPR or the shared subscription subscriber identity list information currently stored by the CSDB.

Preferably, the system further comprises:

a third sending unit, located in the SPR or the CSDB, configured to send a shared subscription subscriber identity list update request message to the DRA when the shared subscription subscriber identity list is updated, The shared subscription subscriber identity list update request message includes updated shared subscription subscriber identity list information;

a replacement unit, located in the DRA, configured to replace the updated shared subscription user identifier list information with the original shared subscription user identifier list information;

And a fourth sending unit, located in the DRA, configured to return an acknowledgement message to the SPR or the CSDB.

In the present invention, when the PCRF is selected for the UE to be accessed, the DRA first determines whether the PCRF is selected for other users who have shared the subscription information with the currently ready-to-access user, and will select other users. The PCRF is used as the PCRF currently ready to access the user, thus ensuring that the same PCRF is selected for all users sharing the subscription information, thereby avoiding conflicts between policy and charging control. DRAWINGS

1 is a schematic structural diagram of a 3GPP evolved packet system;

2 is a schematic structural diagram of a PCC in a non-roaming scenario in Rel-8;

Figure 3 is a schematic structural view of a PCRF domain;

Figure 4 is another schematic diagram of the structure of the PCRF domain.

FIG. 5 is a flowchart of Embodiment 1 of a method for selecting a policy and charging rule function entity according to the present invention; FIG. 6 is a flowchart of Embodiment 2 of a method for selecting a policy and charging rule function entity according to the present invention; FIG. 8 is a flowchart of Embodiment 4 of a method for selecting a policy and charging rule function entity according to the present invention; FIG. 9 is a flowchart of a DRA acquiring a shared subscription user identifier according to the present invention; FIG. 10 is a flowchart of a second method for obtaining a shared subscription user identifier list by the DRA according to the present invention; FIG. 11 is a schematic structural diagram of a selection system of a policy and charging rule function entity according to the present invention. detailed description

The basic idea of the present invention is: When selecting a PCRF for a user who is ready to access, the DRA first determines whether the PCRF is selected for other users who have shared subscription information with the currently ready-to-access user, and is The PCRF selected by other users is used as the PCRF currently ready to access the UE. This ensures that all users who share the subscription information select the same PCRF, avoiding conflicts between policy and charging control.

The present invention will be further described in detail below with reference to the accompanying drawings.

Figure 3 is a schematic diagram of a structure of a PCRF domain. As shown in Figure 3, the DRA is responsible for managing the PCRF in the PCRF domain. The implementation of the DRA may be a Redirect Agent or a Proxy Agent. The number of PCRFs in the PCRF domain is two or more.

The SPR maintains a list of shared subscription user IDs and subscription data of the user. The information exchange between the DRA and the SPR is performed through the Sq interface, and the DRA obtains the shared subscription information user identification list (including the shared subscription information) from the SPR. PCRF clients (such as BBERF, PCEF, and AF) interact with the DRA to select PCRFs in the PCRF domain.

Figure 4 is a schematic diagram of another structure of the PCRF domain. As shown in Figure 4, the DRA is responsible for managing the PCRF in the PCRF domain. The implementation of the DRA can be either a redirect proxy or a proxy proxy. The number of PCRFs in the PCRF domain is two or more. The Correlative Subscriber Data Base (CSDB) is used to store the shared subscription user ID list. The DRA and the CSDB exchange information through the Sq interface. The DRA obtains the shared subscription information user ID list from the CSDB. PCRF clients (such as BBERF, PCEF, and AF) interact with the DRA to select PCRFs in the domain.

The essence of the technical solution of the present invention will be described in detail below in conjunction with the PCRF domain structure shown in Figs. 3 and 4 above.

Embodiment 1 This embodiment describes that UE1 (corresponding user 1) and UE2 (corresponding user 2) access from E-UTRAN in a non-roaming scenario and use the PMIPv6 protocol or from a trusted non-S-GW and P-GW. When the 3GPP network accesses or accesses the 3GPP system from the untrusted non-3GPP network, the IP-CAN session process and the selection process of the PCRF are established. The UE1 and the UE2 need to share the subscription information, and the shared subscription information is a service access for the PDN network 1 (PDN identifier 1), and the DRA is a Redirect Agent, which is implemented based on the structure line shown in FIG. FIG. 5 is a flowchart of Embodiment 1 of a method for selecting a policy and charging rule function entity according to the present invention. As shown in FIG. 5, the method for selecting a policy and charging rule function entity of the present invention specifically includes the following steps:

Step 501: UE1 establishes an IP-CAN session through E-UTRAN access or from a trusted non-3GPP network access request, and the S-GW or the trusted non-3GPP access gateway/BBERF1 receives a message requesting to establish IP-CAN session 1. , the protocol user ID 1 and the PDN identifier 1 in the message;

Step 502: The BBERF1 sends a gateway control session establishment message to the DRA, where the message carries the user identifier 1 and the PDN identifier 1;

Step 503: The DRA searches for locally saved information according to the user identifier 1 and the PDN identifier 1, and finds that the PCRF is not selected for the user or the user and the corresponding PDN identifier, and the PCRF is not selected for any user sharing the subscription information with the user. The DRA sends a subscription document request message to the SPR, where the message carries the user identifier 1 and the PDN identifier 1;

Step 504: The SPR returns a shared subscription user identifier list according to the user identifier 1. The shared subscription user identification list includes a user identification 1 and a user identification 2, and the shared subscription information is a service access to the PDN network 1;

Step 505: The DRA saves the shared subscription user identifier list.

Step 506: The DRA selects the PCRF1 for the user or the IP-CAN session, and saves the corresponding relationship (user identifier 1, PDN identifier 1, PCRF1 address), and returns a redirect message to the BBERF1, where the message carries the address of the selected PCRF1; Step 507: The BBERF1 sends a gateway control session setup message to the PCRF1, where the message carries the user identifier 1 and the PDN identifier 1;

Step 508: PCRF1 sends a subscription document request message to the SPR, where the message carries the user identifier 1 and the PDN identifier 1;

Step 509: The SPR returns the subscription information.

Step 510: The PCRF1 formulates policies according to the subscription information, the network policy, and the access network information, such as PCC rules, QoS rules, and event triggers. PCRF1 returns a gateway control session establishment confirmation message to BBERF1, carrying QoS rules and event triggers. BBERF1 installation strategy; Step 511: The gateway where BBERF1 is located sends a request to establish an IP-CAN session to the gateway where PCEF1 is located. The message carries the user identifier 1 and the PDN identifier 1. The gateway where PCEF1 is located allocates IP Address 1 to the established IP-CAN session 1;

Step 512: The PCEF1 sends an IP-CAN session establishment indication message to the DRA, where the message carries the user identifier 1, the PDN identifier 1 and the IP Address 1;

Step 513: The DRA searches for the saved information according to the user identifier 1 and the PDN identifier 1, and finds that the PCRF1 has been selected for the IP-CAN session 1, and the corresponding relationship (user identifier 1, PDN identifier 1, IP Address 1, PCRFl address) is updated. The DRA returns a redirect message to the PCEF1, carrying the PCRF1 address;

Step 514: The PCEF1 sends an IP-CAN session establishment indication message to the PCRF1, where the message carries the user identifier 1, the PDN identifier 1 and the IP Address 1;

Step 515: PCRF1 returns the corresponding PCC rule and event trigger according to step 510 according to user identifier 1 and PDN identifier 1;

Step 516: The gateway where the PCEF1 is located returns a response to the gateway where the BBERF1 is located to establish an IP-CAN session 1 , carrying an IP Address 1 ;

Step 517: The gateway where the BBERF1 is located returns a response to establish an IP-CAN session 1, carrying an IP Address 1. After the above process, the user 1 establishes the IP-CAN session 1, and the PCRF1 sends policy control information to the IP-CAN session-related policy enforcement entities (PCEF1, BBERF1) to implement policy control. When the user 1 accesses the service, the PCRF1 dynamically sends the policy control information, for example, the usage monitoring of the certain service accessed by the user 1 according to the subscription.

Step 518: UE2 establishes an IP-CAN session through E-UTRAN access or from a trusted non-3GPP network access request, and the S-GW or the trusted non-3GPP access gateway/BBERF2 receives a message requesting to establish an IP-CAN session 2. , the protocol user ID 2 and the PDN ID 1 in the message. BBERF1 and BBERF2 can be the same or different;

Step 519: BBERF2 sends a gateway control session establishment message to the DRA, where the message carries the user identifier 2 and the PDN identifier 1;

Step 520: The DRA searches for the locally saved information according to the user identifier 2 and the PDN identifier 1, and finds that the PCRF is not selected for the user or the user and the corresponding PDN identifier, but the user who has already subscribed to the subscription information is found according to the shared subscription user identifier list. Identification 1 and the corresponding PDN identifier 1 select PCRF1. Establish correspondence (user ID 2, PDN ID 1, PCRF1 address). The DRA returns a redirect message to the BBERF2, where the message carries the PCRF1 address;

Step 521: The BBERF2 sends a gateway control session establishment message to the PCRF1, where the message carries the user identifier 2 and the PDN identifier 1;

Step 522: PCRF1 sends a subscription document request message to the SPR, where the message carries the user identifier 2 and the PDN identifier 1;

Step 523: SPR returns the subscription information;

Step 524: The PCRF1 formulates policies according to the subscription information, the network policy, the access network information, and the like, such as PCC rules, QoS rules, and event triggers. PCRF1 returns a gateway control session setup confirmation message to BBERF2, carrying QoS rules and event triggers. BBERF2 installation strategy; Step 525: The gateway where the BBERF2 is located sends a request to establish a IP-CAN session 2 to the gateway where the PCEF2 is located, and the message carries the user identifier 2 and the PDN identifier 1. The gateway where PCEF2 is located is established. IP-CAN Session 2 is assigned IP Address2. PCEF1 and PCEF2 may be the same or different;

Step 526: The PCEF2 sends an IP-CAN session establishment indication message to the DRA, where the message carries the user identifier 2, the PDN identifier 1 and the IP Address2;

Step 527: The DRA searches for the saved information according to the user identifier 2 and the PDN identifier 1, and finds that the PCRF1 has been selected for the IP-CAN session 2, and the corresponding relationship (user identifier 2, PDN identifier 1, IP Address 1, and PCRF 1 address) is updated. The DRA returns a redirect message to PCEF2, carrying the PCRF1 address;

Step 528: The PCEF2 sends an IP-CAN session establishment indication message to the PCRF1, where the message carries the user identifier 2, the PDN identifier 1 and the IP Address 2;

Step 529: PCRF1 returns a corresponding PCC rule and event trigger according to step 524 according to user identifier 2 and PDN identifier 1;

Step 530: The gateway where the PCEF2 is located returns a response to the gateway where the BBERF2 is located to establish an IP-CAN session 2, carrying an IP Address2;

Step 531: The gateway where the BBERF2 is located returns a response to establish an IP-CAN session 2, carrying the IP

Address2.

After the above process, the user 2 establishes an IP-CAN session 2, and the PCRF1 sends policy control information to the IP-CAN session-related policy enforcement entity (PCEF2, BBERF2) to implement policy control. When User 2 accesses the service, PCRF1 also dynamically sends policy control information. At this time, PCRF1 can uniformly monitor the usage of the services accessed by User 1 and User 2 according to the shared subscription data.

Although the above embodiment only describes the process of selecting the same PCRF for the IP-CAN session of two users sharing the subscription information, the process of selecting the same PCRF for the IP-CAN session of two or more users sharing the subscription information is similar. of.

The selection method of the policy and charging rule function entity of the present invention is based on the implementation of the structure shown in FIG. The process is similar to the foregoing implementation process based on the structure shown in FIG. 3, and the difference is that the DRA and the CSDB interact to obtain a shared subscription information user identifier list, which is described here.

Embodiment 2

This embodiment describes that UE1 (corresponding user 1) and UE2 (corresponding user 2) establish IP in the non-roaming scenario when accessing from the E-UTRAN and using the GTP protocol between the S-GW and the P-GW. CAN session process and PCRF selection process. The UE1 and the UE2 need to share the subscription information, and the shared subscription information is a service access for the PDN network 1 (PDN identifier 1), and the DRA is a Redirect Agent, which is implemented based on the structure line shown in FIG. FIG. 6 is a flowchart of Embodiment 2 of a method for selecting a policy entity and a charging rule function entity. As shown in FIG. 6, the method for selecting a policy and charging rule function entity includes the following steps:

Step 601: The UE1 accesses the EPS system through the E-UTRAN, and the P-GW1/PCEF1 receives the message requesting to establish the IP-CAN session 1, in the message, the protocol user ID 1 and the PDN identifier 1; Step 602: PCEF1 sends the IP address to the DRA. a CAN session establishment indication message, where the message carries the user identifier 1 and the PDN identifier 1;

Step 603: The DRA searches for locally saved information according to the user identifier 1 and the PDN identifier 1, and finds that the PCRF is not selected for the user or the user and the corresponding PDN identifier, and does not select the PCRF for any user who shares the subscription information with the user. The DRA sends a subscription document request message to the SPR, where the message carries the user identifier 1 and the PDN identifier 1;

Step 604: The SPR returns a shared subscription user identifier list according to the user identifier 1. The shared subscription user identification list includes a user identification 1 and a user identification 2, and the shared subscription information is a service access to the PDN network 1;

Step 605: The DRA saves the shared subscription user identifier list.

Step 606: The DRA selects the PCRF1 for the user or the IP-CAN session, and saves the corresponding relationship (user identifier 1, PDN identifier 1, PCRF1 address), and returns a redirect message to the PCEF1. The message carries the address of the selected PCRF1;

Step 607: The PCEF1 sends an IP-CAN session establishment indication message to the PCRF1, where the message carries the user identifier 1, the PDN identifier 1 and the IP Address 1;

Step 608: The PCRF1 sends a subscription document request message to the SPR, where the message carries the user identifier 1 and the PDN identifier 1;

Step 609: The SPR returns the subscription information.

Step 610: The PCRF1 formulates policies according to the subscription information, the network policy, and the access network information, such as a PCC rule and an event trigger. PCRF1 returns an IP-CAN session establishment confirmation message to PCEF1, carrying PCC rules and event triggers. PCEF1 installation strategy;

Step 611: P-GW/PCEF1 returns a response to establish an IP-CAN session 1 and carries IP Address 1. After the above process, the user 1 establishes an IP-CAN session 1 , and the PCRF1 sends policy control information to the IP-CAN session-related policy enforcement entity (PCEF1) to implement policy control. When the user 1 accesses the service, the PCRF1 also dynamically sends policy control information, such as monitoring the usage of the service accessed by the user 1 according to the contract.

Step 612: The UE2 accesses the EPS system through the E-UTRAN, and the P-GW2/PCEF2 receives the message requesting to establish the IP-CAN session 2, where the protocol user ID 2 and the PDN identifier 1 are in the message. PCEF1 and PCEF2 may be the same or different;

Step 613: The PCEF2 sends an IP-CAN session establishment indication message to the DRA, where the message carries the user identifier 2 and the PDN identifier 1;

Step 614: The DRA searches for the locally saved information according to the user identifier 2 and the PDN identifier 1, and finds that the PCRF is not selected for the user or the user and the corresponding PDN identifier, but the user who has already subscribed to the subscription information is found according to the shared subscription user identifier list. Identification 1 and the corresponding PDN identifier 1 select PCRF1. Establish correspondence (user ID 2, PDN ID 1, PCRF1 address). The DRA returns a redirect message to the PCEF2, where the message carries the PCRF1 address;

Step 615: PCEF2 sends an IP-CAN session establishment indication message to the PCRF1, in the message. Carry user ID 2, PDN ID 1 and IP Address 2;

Step 616: The PCRF1 sends a subscription document request message to the SPR, where the message carries the user identifier 2 and the PDN identifier 1;

Step 617: The SPR returns the subscription information.

Step 618: The PCRF1 formulates policies according to the subscription information, the network policy, and the access network information, such as PCC rules and event triggers. PCRF1 returns a gateway control session establishment confirmation message to PCEF2, carrying the PCC and the event trigger. PCEF2 installation strategy;

Step 619: P-GW2/PCEF2 returns a reply to establish an IP-CAN session 2, carrying IP Address2.

After the above process, the user 2 establishes an IP-CAN session 2, and the PCRF1 sends policy control information to the IP-CAN session-related policy enforcement entity (PCEF2) to implement policy control. When User 2 accesses the service, PCRF1 also dynamically sends policy control information. At this time, PCRF1 can uniformly perform usage monitoring control on a certain service accessed by user 1 and user 2 according to the shared subscription data.

The implementation process of the policy and the charging rule function entity of the present invention is similar to the implementation process based on the structure shown in FIG. 3, and the difference is that the DRA and the CSDB exchange the user identification list of the shared subscription information. I will repeat them here.

In the present invention, UE1 can access and establish IP-CAN session 1 by using steps 501 to 517 of FIG. 5, and UE2 can access and establish IP-CAN2 session 2 by using steps 612 to 619 of FIG. 6; UE1 can access and establish IP-CAN session 1 by using steps 601 to 611 of FIG. 6, and UE2 can access and establish IP-CAN session 2 by using steps 518 to 531 of FIG. Embodiment 3

This embodiment describes that UE1 (corresponding user 1) and UE2 (corresponding user 2) access from E-UTRAN in a non-roaming scenario and use the PMIPv6 protocol or from a trusted non-S-GW and P-GW. When the 3GPP network accesses or accesses the 3GPP system from the untrusted non-3GPP network, the PCRF selection process is established during the IP-CAN session. The UE1 and the UE2 need to share the subscription information, and the shared subscription information is the service access for the PDN network 1 (the PDN identifier 1), and the DRA is the proxy agent, which is implemented based on the structure shown in FIG. FIG. 7 is a flowchart of Embodiment 3 of a method for selecting a policy entity and a charging rule function entity. As shown in FIG. 7, the method for selecting a policy and charging rule function entity includes the following steps:

Step 701: UE1 establishes an IP-CAN session through E-UTRAN access or from a trusted non-3GPP network access request, and the S-GW or the trusted non-3GPP access gateway/BBERF1 receives a message requesting to establish IP-CAN session 1. , the protocol user ID 1 and the PDN identifier 1 in the message;

Step 702: BBERF1 sends a gateway control session establishment message to the DRA, where the message carries the user identifier 1 and the PDN identifier 1;

Step 703: The DRA searches for the saved information according to the user identifier 1 and the PDN identifier 1, and finds that the PCRF is not selected for the user or the user and the corresponding PDN identifier, and the PCRF is not selected for any user sharing the subscription information with the user (ie, no The DRA sends a subscription document request message to the SPR, where the message carries the user identifier 1 and the PDN identifier 1;

Step 704: The SPR returns a shared subscription user identifier list according to the user identifier 1. The shared subscription user identifier list includes the user identifier 1 and the user identifier 2, and the shared subscription information is a service access for the PDN network 1;

Step 705: The DRA saves the shared subscription user identifier list.

Step 706: The DRA selects PCRF1 for the user or the IP-CAN session, and saves the corresponding relationship (user identifier 1, PDN identifier 1, PCRF1 address;), and forwards the gateway control conference to PCRF1. The message is established, and the message carries the user identifier 1 and the PDN identifier 1;

Step 707: PCRF1 sends a subscription document request message to the SPR, where the message carries the user identifier 1 and the PDN identifier 1;

Step 708: The SPR returns the subscription information.

Step 709: The PCRF1 formulates policies according to the subscription information, the network policy, and the access network information, such as PCC rules, QoS rules, and event triggers. PCRF1 returns a gateway control session setup confirmation message to the DRA, carrying QoS rules and event triggers.

Step 710: The DRA forwards the gateway control session establishment confirmation message to the BBERF1, and carries the QoS rule and the event trigger. BBERF1 installation strategy;

Step 711: The gateway where the BBERF1 is located sends a request to establish an IP-CAN session to the gateway where the PCEF1 is located. The message carries the user identifier 1 and the PDN identifier 1. The gateway where PCEF1 is located allocates IP Address 1 to the established IP-CAN session 1;

Step 712: The PCEF1 sends an IP-CAN session establishment indication message to the DRA, where the message carries the user identifier 1, the PDN identifier 1 and the IP Address 1;

Step 713: The DRA searches for the saved information according to the user identifier 1 and the PDN identifier 1, and finds that the PCRF1 has been selected for the IP-CAN session 1, and the corresponding relationship (user identifier 1, PDN identifier 1, IP Address 1, and PCRFl address) is updated. The DRA forwards the IP-CAN session establishment indication message to the PCRF1, and the message carries the user identifier 1, the PDN identifier 1 and the IP Address 1;

Step 714: The PCRF1 returns a PCC rule and an event trigger defined by the corresponding step 609 to the DRA according to the user identifier 1 and the PDN identifier 1;

Step 715: The DRA forwards the message to the PCEF1, and carries the PCC rule and the event trigger. Step 716: The gateway where the PCEF1 is located returns a response to the gateway where the BBERF1 is located to establish an IP-CAN session 1 , carrying the IP Address 1 ;

Step 717: The gateway where the BBERF1 is located returns a response to establish an IP-CAN session 1, carrying an IP Address 1. After the above process, the user 1 establishes the IP-CAN session 1, and the PCRF1 sends policy control information to the IP-CAN session-related policy enforcement entities (PCEF1, BBERF1) to implement policy control. When the user 1 accesses the service, the PCRF1 dynamically sends the policy control information, for example, the usage monitoring of the certain service accessed by the user 1 according to the subscription.

Step 718: UE2 establishes an IP-CAN session through E-UTRAN access or from a trusted non-3GPP network access request, and the S-GW or trusted non-3GPP access gateway/BBERF2 receives a message requesting to establish IP-CAN session 2. , the protocol user ID 2 and the PDN ID 1 in the message. BBERF1 and BBERF2 can be the same or different;

Step 719: The BBERF2 sends a gateway control session establishment message to the DRA, where the message carries the user identifier 2 and the PDN identifier 1;

Step 720: The DRA searches for the saved information according to the user identifier 2 and the PDN identifier 1, and finds that the PCRF is not selected for the user or the user and the corresponding PDN identifier, but the user identifier that has been the shared subscription information is found according to the shared subscription user identifier list. 1 and the corresponding PDN identifier 1 selects PCRF1. Establish correspondence (user ID 2, PDN ID 1, PCRF1 address). The DRA forwards the gateway control session establishment message to the PCRF, where the message carries the user identifier 2 and the PDN identifier 1;

Step 721: The PCRF1 sends a subscription document request message to the SPR, where the message carries the user identifier 2 and the PDN identifier 1;

Step 722: The SPR returns the subscription information.

Step 723: The PCRF1 formulates policies according to the subscription information, the network policy, and the access network information, such as PCC rules, QoS rules, and event triggers. PCRF1 returns a gateway control session establishment confirmation message to the DRA, carrying QoS rules and event triggers;

Step 724: The DRA returns a gateway control session establishment confirmation message to the BBERF2, carrying the QoS rule and the event trigger. BBERF2 installation strategy;

Step 725: The gateway where the BBERF2 is located sends a request to the gateway where the PCEF2 is located to establish an IP-CAN. Session 2, the message carries the user identifier 2 and the PDN identifier 1. The gateway where PCEF2 is located allocates IP Address2 to the established IP-CAN session 2. PCEF1 and PCEF2 may be the same or different;

Step 726: PCEF2 sends an IP-CAN session establishment indication message to the DRA, where the message carries the user identifier 2, the PDN identifier 1 and the IP Address2;

Step 727: The DRA searches for the saved information according to the user identifier 2 and the PDN identifier 1, and finds that the PCRF1 has been selected for the IP-CAN session 2, and the corresponding relationship is updated (user identifier 2, PDN identifier 1, IP Address 1, PCRFl address). The DRA forwards the IP-CAN session establishment indication message to the PCRF1, where the message carries the user identifier 2, the PDN identifier 1 and the IP Address 2;

Step 728: PCRF1 returns a corresponding PCC rule and event trigger according to step 624 according to user identifier 2 and PDN identifier 1;

Step 729: The DRA returns PCC rules and event triggers to PCEF2. PCEF2 installation strategy;

Step 730: The gateway where the PCEF2 is located returns a response to the gateway where the BBERF2 is located to establish an IP-CAN session 2, carrying an IP Address2;

Step 731: The gateway where BBERF2 is located returns a response to establish an IP-CAN session 2, carrying IP Address2.

After the above process, the user 2 establishes an IP-CAN session 2, and the PCRF1 sends policy control information to the IP-CAN session-related policy enforcement entities (PCEF2, BBERF2) to implement policy control. When the user 2 accesses the service, the PCRF1 also dynamically sends policy control information. At this time, the PCRF can perform the usage monitoring control on the services accessed by the user 1 and the user 2 according to the shared subscription data.

Although the above embodiment only describes the process of selecting the same PCRF for the IP-CAN session of two users sharing the subscription information, the process of selecting the same PCRF for the IP-CAN session of two or more users sharing the subscription information is similar. of. The implementation process of the policy and the charging rule function entity of the present invention is similar to the implementation process based on the structure shown in FIG. 3, and the difference is that the DRA and the CSDB exchange the user identification list of the shared subscription information. I will repeat them here.

Embodiment 4

This embodiment describes that UE1 (corresponding user 1) and UE2 (corresponding user 2) establish IP in the non-roaming scenario when accessing from the E-UTRAN and using the GTP protocol between the S-GW and the P-GW. The selection process of the PCRF during the CAN session. The UE1 and the UE2 need to share the subscription information, and the shared subscription information is a service access for the PDN network 1 (PDN identifier 1), and the DRA is a proxy agent, which is implemented based on the structure shown in FIG. FIG. 8 is a flowchart of Embodiment 4 of a method for selecting a policy and charging rule function entity according to the present invention. As shown in FIG. 8, the method for selecting a policy and charging rule function entity of the present invention specifically includes the following steps:

Step 801: UE1 establishes an IP-CAN session by using an E-UTRAN access request, and P-GW1/PCEF1 receives a message requesting to establish an IP-CAN session 1, in which the protocol user identifier 1 and the PDN identifier 1 are included;

Step 802: The PCEF1 sends an IP-CAN session establishment indication message to the DRA, where the message carries the user identifier 1 and the PDN identifier 1;

Step 803: The DRA searches for the saved information according to the user identifier 1 and the PDN identifier 1, and finds that the PCRF is not selected for the user or the user and the corresponding PDN identifier, and the PCRF is not selected for any user sharing the subscription information with the user (ie, no The DRA sends a subscription document request message to the SPR, where the message carries the user identifier 1 and the PDN identifier 1;

Step 804: The SPR returns a shared subscription user identifier list according to the user identifier 1. The shared subscription user identifier list includes the user identifier 1 and the user identifier 2, and the shared subscription information is a service access to the PDN network 1;

Step 805: The DRA saves the shared subscription user identifier list. Step 806: The DRA selects the PCRF1 for the user or the IP-CAN session, and saves the corresponding relationship (user identifier 1, PDN identifier 1, PCRF1 address), and forwards the IP-CAN session establishment indication message to the PCRF1, where the message carries the user identifier 1 And PDN logo 1;

Step 807: The PCRF1 sends a subscription document request message to the SPR, where the message carries the user identifier 1 and the PDN identifier 1;

Step 808: The SPR returns the subscription information.

Step 809: The PCRF1 formulates policies according to the subscription information, the network policy, and the access network information, such as PCC rules and event triggers. PCRF1 returns an IP-CAN session establishment confirmation message to the DRA, carrying PCC rules and event triggers.

Step 810: The DRA forwards the IP-CAN session establishment confirmation message to the PCEF1, carrying the PCC rule and the event trigger. PCEF1 installation strategy;

Step 811: P-GW1/PCEF1 returns an answer to establish an IP-CAN session 1 and carries IP Address 1.

After the above process, the user 1 establishes an IP-CAN session 1 , and the PCRF1 sends policy control information to the IP-CAN session-related policy enforcement entity (PCEF1) to implement policy control. When the user 1 accesses the service, the PCRF1 also dynamically sends policy control information, such as monitoring the usage of a certain service accessed by the user 1 according to the contract.

Step 812: UE2 establishes an IP-CAN session by using an E-UTRAN access request, and P-GW2/PCEF2 receives a message requesting to establish an IP-CAN session 2, where the protocol user ID 2 and the PDN identifier 1 are in the message. PCEF 1 and PCEF2 may be the same or different;

Step 813: The PCEF2 sends an IP-CAN session establishment indication message to the DRA, where the message carries the user identifier 2 and the PDN identifier 1;

Step 814: The DRA searches for the saved information according to the user identifier 2 and the PDN identifier 1, and finds that the PCRF is not selected for the user or the user and the corresponding PDN identifier, but finds the user identifier that has been the subscription information according to the shared subscription user identifier list. 1 and the corresponding PDN identifier 1 PCRF1 was selected. Establish correspondence (user ID 2, PDN ID 1, PCRF1 address). The DRA forwards an IP-CAN session establishment indication message to the PCRF, where the message carries the user identifier 2 and the PDN identifier 1;

Step 815: The PCRF1 sends a subscription document request message to the SPR, where the message carries the user identifier 2 and the PDN identifier 1;

Step 816: The SPR returns the subscription information.

Step 817: The PCRF1 formulates policies according to the subscription information, the network policy, and the access network information, such as PCC rules and event triggers. PCRF1 returns an IP-CAN session establishment confirmation message to the DRA, carrying PCC rules and event triggers;

Step 818: The DRA returns an IP-CAN session establishment confirmation message to the PCEF2, carrying the PCC rules and event triggers. PCEF2 installation strategy;

Step 819: The gateway where the P-GW2/PCEF2 is located returns a response to establish an IP-CAN session 2, carrying the IP Address2.

After the above process, the user 2 establishes an IP-CAN session 2, and the PCRF1 sends policy control information to the IP-CAN session-related policy enforcement entity (PCEF2) to implement policy control. When the user 2 accesses the service, the PCRF1 also dynamically sends policy control information. At this time, the PCRF can perform the usage monitoring control on the services that are accessed by the user 1 and the user 2 according to the shared subscription data.

In other embodiments, UE 1 accesses and establishes IP-CAN using steps 701 - 717 of FIG. Session 1 , UE2 accesses and establishes IP-CAN2 session 2 by using step 812-step 819 of FIG. 8; or, UE1 accesses and establishes IP-CAN session 1 by using step 801 of FIG. 8 - 811, UE2 uses Steps 718 - 731 of Figure 7 access and establish an IP-CAN session 2.

In all of the above embodiments, the subscription information is shared for the user 1 and the user 2, and the shared subscription information is a service access for a PDN network. At this time, the DRA selects the same PCRF for the IP-CAN session established by User 1 and User 2 to the same PDN network.

If 1 and user 2 share subscription information, and the subscription information is shared for multiple PDN networks, or all PDN networks are accessed. At this time, the DRA selects the same PCRF for the IP-CAN session of the multiple PDN networks established by User 1 and User 2 according to the shared subscription user identification list or selects the same PCRF for all IP-CAN sessions of User 1 and User 2 ( That is, User 1 and User 2 select the same PCRF), and the flow is similar.

FIG. 9 is a flowchart of a method for obtaining a shared subscription subscriber identity list by the DRA according to the present invention. When the DRA is started for the first time, or restarted after the fault is recovered, the SPR is requested to request the shared subscription subscriber identifier list. As shown in FIG. 9, the DRA obtains the shared subscription subscriber identifier. The specific way of the list is:

Step 901: The DRA is powered on;

Step 902: The DRA sends a shared subscription subscriber list request message to the SPR.

Step 903: The SPR returns an acknowledgement message, and sends the shared subscription subscriber identity list saved in the SPR to the DRA.

Through the above process, the DRA saves the list of all the shared subscriber IDs, so that when the DRA finds that the new subscriber identity appears, it does not need to request the shared subscription subscriber identity list from the SPR as in the first embodiment and the second embodiment.

The way in which the DRA shown in Figure 9 obtains a list of shared subscription user IDs also applies to CSDB. 10 is a flowchart of a method for obtaining a shared subscription user identifier list by the DRA according to the present invention. When the SPR updates the shared subscription user identifier list in the DRA, it is sent to the DRA, as shown in FIG.

The specific way for DRA to obtain a list of shared subscription user IDs is: Step 1001: The SPR detects that the trigger of the shared subscription subscriber identity list needs to be updated. Step 1002: The SPR sends a shared subscription subscriber identity list update request to the DRA, and carries the updated shared subscription subscriber identity list.

Step 1003: After the DRA updates the shared subscription user identifier list, a confirmation message is returned.

Through the above process, the DRA saves a list of all the shared subscription user identifiers, so that when the DRA finds that a new user identifier appears, it is not necessary to request the SPR to share the subscription subscriber identity list as in the first embodiment and the second embodiment.

The way DRA obtains the list of shared subscription user IDs as shown in Figure 10 also applies to

CSDB.

11 is a schematic structural diagram of a system for selecting a policy and charging rule function entity according to the present invention. As shown in FIG. 11, the selection system selection unit 110 of the policy and charging rule function entity of the present invention is located in the DRA for sharing. More than two users of the subscription information select the same PCRF. In the present invention, the shared subscription information is specifically: the IP connection access network IP-CAN session sharing subscription information established by the two or more users to access the same packet data network PDN; or, the two or more users The IP-CAN session established for accessing more than two PDNs shares subscription information; or the IP-CAN session established by the two or more users to access all PDNs shares subscription information.

The selecting unit in the present invention includes a receiving subunit, a judging subunit, and a selecting subunit, wherein the receiving subunit is configured to receive a gateway control session establishment message sent by the BBERF or an IP-CAN session establishment indication message sent by the PCEF; Determining, according to the gateway control session establishment message or the user identification information in the IP-CAN session establishment indication message or the identification information of the PDN that the user wants to access, whether the subscription information has been shared with the user. The user selects the PCRF, and triggers the selection subunit; the selection subunit is used to use the PCRF selected for the other user as the PCRF selected for the user.

As shown in FIG. 11, the selection system of the policy and charging rule function entity of the present invention further includes: The fetching unit 111 is located in the DRA, and is configured to acquire the shared subscription user list information of the user by using an SPR or a CSDB, where the shared subscription user list includes identification information of two or more users sharing the subscription information, or includes two The identification information of more than one user and the PDN network identification information for the shared subscription information. .

As shown in FIG. 11, the selection system of the policy and charging rule function entity of the present invention further includes a first sending unit 112 and a second sending unit 113, wherein the first sending unit 112 is located in the DRA, and is used in the Sending a shared subscription subscriber list request message to the SPR or the CSDB when the DRA is powered on; the second sending unit 113 is located in the SPR or the CSDB, and is configured to return an acknowledgement message to the DRA, where The confirmation message includes the SPR or the shared subscription user identifier list information currently stored by the CSDB.

As shown in FIG. 11, the selection system of the policy and charging rule function entity of the present invention may further include a third sending unit 114, a replacing unit 115, and a fourth sending unit 116, where the third sending unit 114 is located in the SPR or The CSDB is configured to send a shared subscription subscriber identity list update request message to the DRA when the shared subscription subscriber identity list is updated, where the shared subscription subscriber identity list update request message includes updated shared subscription subscriber identity list information. The replacing unit 115 is located in the DRA, and is configured to replace the updated shared subscription user identifier list information with the original shared subscription user identifier list information. The fourth sending unit 116 is located in the DRA, and is configured to The SPR or the CSDB returns an acknowledgement message.

Those skilled in the art should understand that the selection system of the policy and charging rule function entity shown in FIG. 11 is designed to implement the foregoing selection method of the policy and charging rule function entity, and the processing in the system shown in FIG. The functions of the unit and the processing sub-unit can be understood by referring to the related descriptions in the foregoing first embodiment to the fourth embodiment. The functions of each processing unit and processing sub-unit can be implemented by a program running on the processor, or through specific logic. The circuit is implemented. It should be understood by those skilled in the art that, except for the selection unit 110 in FIG. 11, the remaining processing units are non-essential technical features for implementing the basic technical solutions of the present invention. The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Claims

Claim

A method for selecting a policy and charging rule function entity, the method comprising:

Diameter Routing Agent DRA selects the same policy and charging rule function entity PCRF for more than two users sharing subscription information.

2. The method according to claim 1, wherein the shared subscription information is:

The method according to claim 2, wherein the two or more users sharing the subscription information select the same PCRF, specifically:

After receiving the gateway control session establishment message sent by the bearer binding and event reporting function entity BBERF or the IP-CAN session establishment indication message sent by the policy and charging execution function entity PCEF, the DRA controls the session establishment message according to the gateway or The user identification information in the IP-CAN session establishment indication message or/and the identification information of the PDN to be accessed by the user determines whether the PCRF has been selected for other users sharing the subscription information with the user, and will select other users. The PCRF serves as the PCRF selected by the user.

The method according to any one of claims 1 to 3, wherein the DRA acquires shared subscription user list information of the user through a user subscription database SPR or an associated user database CSDB, and the shared subscription user The list contains more than two shared subscription information Identification information of the user, or identification information including two or more users and shared subscription information

PDN network identification information.

The method according to claim 4, wherein the method further comprises: sending a shared subscription subscriber list request message to the SPR or the CSDB when the DRA is restarted;

The method according to claim 4, wherein the method further comprises: when the SPR or the shared subscription user identifier list in the CSDB is updated,

The DRA sends a shared subscription subscriber identity list update request message, where the shared subscription subscriber identity list update request message includes updated shared subscription subscriber identity list information;

7. A system for selecting a policy and charging rule functional entity, the system comprising:

8. The system according to claim 7, wherein the shared subscription information is:

Alternatively, the IP-CAN session shared by the two or more users for accessing all PDNs shares subscription information.

9. The system according to claim 8, wherein the selection unit further comprises a receiving subunit, a judging subunit, and a selecting subunit, wherein:

The system according to any one of claims 7 to 9, wherein the system further comprises: an obtaining unit, located in the DRA, for acquiring a shared subscription user of the user by using an SPR or a CSDB List information, the shared subscription user list includes identification information of two or more users sharing the subscription information, or identification information including two or more users and PDN network identification information for the shared subscription information.

The system according to claim 10, wherein the system further comprises: a first sending unit, located in the DRA, configured to send a share to the SPR or the CSDB when the DRA restarts Signing up a user list request message;

The system according to claim 10, wherein the system further comprises: a third sending unit, located in the SPR or the CSDB, configured to update the shared subscription user identifier list to the The DRA sends a shared subscription subscriber identity list update request message, where the shared subscription subscriber identity list update request message includes the updated shared subscription subscriber identity. List information