WO2009149642A1 - 分组数据网络的接入控制方法和系统、pcrf实体 - Google Patents
分组数据网络的接入控制方法和系统、pcrf实体 Download PDFInfo
- Publication number
- WO2009149642A1 WO2009149642A1 PCT/CN2009/072109 CN2009072109W WO2009149642A1 WO 2009149642 A1 WO2009149642 A1 WO 2009149642A1 CN 2009072109 W CN2009072109 W CN 2009072109W WO 2009149642 A1 WO2009149642 A1 WO 2009149642A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- session
- function entity
- indication message
- session establishment
- message
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1453—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network
- H04L12/1457—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network using an account
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1453—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network
- H04L12/1471—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network splitting of costs
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/08—Access security
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/11—Allocation or use of connection identifiers
Definitions
- the present invention relates to the field of communications, and in particular to a packet data network (Packet Data Network, PDN for short) access control method and system, and a policy and charging rule function (referred to as PCRF) entity.
- a packet data network Packet Data Network, PDN for short
- PCRF policy and charging rule function
- EPS Packet Data Network
- E-UTRAN Mobility Management Entity
- MME Mobility Management Entity
- S-GW Serving Gateway
- P-GW Packet Data Network Gateway
- PDN GW Packet Data Network Gateway
- HSS Home Subscriber Server
- PCRF Policy and charging rules Function
- PCRF Policy and charging rules Function
- the MME is responsible for control planes such as mobility management, processing of non-access stratum signaling, and management of user mobility management context
- GW is an access gateway device connected to E-UTRAN, which forwards data between E-UTRAN and P-GW, and is responsible for buffering paging waiting data
- P-GW is EPS and packet data network (Packet Data Network) , referred to as PDN)
- PDN packet data network
- PCRF Policy and charging rule function entity, which is through the receiving interface Rx and the carrier network.
- Protocol abbreviated as IP
- IP IP
- EPS supports interworking with non-3GPP systems. Interworking with non-3GPP systems is implemented through the S2a/b/c interface, and the P-GW acts as an anchor between 3GPP and non-3GPP systems. In the system architecture diagram of EPS, non-3GPP systems are classified into trusted non-3GPP IP access and untrusted non-3GPP IP access.
- the trusted non-3GPP IP access can be directly connected to the P-GW through the S2a interface; the untrusted non-3GPP IP access needs to be connected to the P-GW through an Evolved Packet Data Gateway (ePDG), ePDG and The interface between the P-GWs is S2b.
- the S2c provides user-side control and mobility support between the user equipment (User Equipment, UE for short) and the P-GW.
- the supported mobility management is supported.
- Mobile IPv6 Support for Dual Stack Hosts and Routers (referred to as DSMIPv6). Policy and Charging enforcement in 3GPP networks prior to EPS (Policy and Charging
- PCEF Policy Enforcement Function
- the entity exists in the P-GW.
- the interface between the PCRF and the P-GW can complete all functions.
- the PCRF and the P-GW exchange information through the Gx interface (see Figure 1).
- the S-GW also has a Bearer Binding and Event Report Function (BBERF).
- BBERF Bearer Binding and Event Report Function
- the entity performs QoS control on the service data flow, and the S-GW and the PCRF exchange information through the Gxc interface (see FIG. 1).
- the BBERF is also resident in the trusted non-3GPP access gateway.
- the trusted non-3GPP access gateway exchanges information with the PCRF through the Gxa interface (see Figure 1).
- the S9 interface functions as an interface between the home PCRF and the visited PCRF, and provides an application function (Application Function, abbreviated as AF) for the UE, and sends the policy and charging control to the PCRF through the Rx interface.
- Policy and Charging Control (PCC for short) is the business information of the policy.
- the EPS system supports Multiple PDN access, that is, the UE can simultaneously access multiple PDNs through multiple P-GWs or one P-GW, and the EPS support UE can simultaneously access the same PDN multiple times.
- the corresponding PDN network can be found by using an Access Point Name (APN).
- API Access Point Name
- IP-CAN IP Connectivity Access Network
- the EPS support UE can simultaneously have multiple IP-CAN sessions with one PDN network.
- 2 is a flow chart of an initial attachment of a UE to a EPS through a trusted non-3GPP access network according to the related art. As shown in FIG. 2, the UE is initially attached to a PDN through a trusted non-3GPP access network.
- Step S201 The UE accesses the trusted non-3GPP access network
- Step S202 After the UE accesses the trusted non-3GPP access network, request the EPS access authentication from the HSS/AAA; after the HSS/AAA receives the EPS access authentication request, perform authentication on the requesting UE; After the HSS/AAA completes the authentication of the UE, the P-GW selection information of the UE subscription and the APN signed by the UE are sent to the trusted non-3GPP access gateway, including the default APN.
- Step S203 After the authentication succeeds, the layer 3 attach procedure
- the network access identifier (Network Access Identifier, referred to as the network access identifier) of the UE is sent to the PCRF by the trusted non-3GPP access gateway that resides in the BBERF.
- Step S205 the PCRF determines the PCC rules and QoS rules according to the user's subscription data, network policy, bearer attributes, etc., and may also formulate corresponding event triggers; the PCRF establishes through the "gateway control session" Acknowledging that the message sends the QoS rules and event triggers to the trusted non-3GPP access gateway; the trusted non-3GPP access gateway installs the QoS rules and event triggers; step S206, After receiving the P-GW selection information, the trusted non-3GPP access gateway selects the P-GW according to the P-GW selection information, and sends a proxy binding update message to the selected P-GW, and the proxy binding update message is used.
- Step S207 after receiving the proxy binding update message, the P-GW camping on the PCEF sends an IP-CAN session establishment indication to the PCRF, and carries the UE in the IP-CAN session establishment indication.
- the NAI and the P-GW allocate the IP address and the default APN for the UE.
- Step S209 after receiving the IP-CAN session establishment confirmation message, the P-GW installs and executes the PCC rule carried in the IP-CAN session establishment confirmation message, and at the same time, Its own IP Address sent to the HSS; step S210, P-GW returns a proxy to the trusted non-3GPP access gateway a binding acknowledgment message; Step S211, if the QoS rule that is specified in step S208 is different from that delivered in step S205, the PCRF sends the updated QoS rule to the trusted non-3GPP access gateway by using the gateway control and the QoS policy rule providing message; S212, the trusted non-3GPP access gateway installs the QoS rule, and returns the gateway control and the QoS policy rule to provide the confirmation; Step S213, the layer 3 attachment is completed; Step S214, the PMMS6 is established between the trusted non-3GPP access gateway and the P-GW. tunnel,
- the UE can send or receive data, and the process ends.
- the UE establishes a second PDN connection to the default APN
- the UE sends a "trigger new PDN connection message" to the trusted non-3GPP access gateway, and carries the default APN in the "trigger new PDN connection message”
- the remaining steps are as follows: S204-S214 is shown.
- the P-GW allocates an IP address to the UE.
- the interaction between the trusted 3GPP access gateway and the PCRF is before the interaction between the P-GW and the PCRF.
- the trusted non-3GPP gateway does not have the IP address allocated by the P-GW for the UE, regardless of the initial attachment.
- the trusted non-3GPP access gateway has only the NAI and the default APN. Since a UE has multiple connections to the same PDN (or APN), the NAI and the default APN are the same. Therefore, the PCRF cannot distinguish the multiple PDN connections based on the information, and thus cannot connect the gateways belonging to the same PDN connection.
- Control session messages are associated with IP-CAN session messages. However, for PCRF, the gateway control session message and the IP-CAN session message belonging to the same IP-CAN session must be - corresponding. Because the PCC rules include QoS control policies and charging policies, and only QoS control policies are included in the QoS rules.
- the charging policy of the PCC rule is related to the provided QoS, that is, the charging policy installed on the PCEF and the QoS control policy installed on the BBERF must be related.
- the PCRF In order to ensure correct charging, the PCRF must ensure that the successfully activated PCC rules in the PCEF have corresponding successfully activated QoS rules in the BBERF.
- the corresponding PCC rules and QoS rules are sent by the corresponding gateway control session message and IP-CAN session message.
- the UE accesses the same PDN (or APN) multiple times, it will also cause problems with the existing handover technology.
- 3 is a flow of a UE switching from one trusted non-3GPP access network 1 to another trusted non-3GPP access network 2, and two trusted non-3GPPs.
- Step S301 The UE accesses the trusted non-3GPP access network 1 through the process of FIG. 2, and establishes a PDN connection to the default APN through the access network; Step S302, the UE finds that the trusted non-3GPP is connected.
- Step S303 after the UE accesses the trusted non-3GPP access network 2, requesting EPS access authentication from the HSS/AAA; after the HSS/AAA receives the EPS access authentication request And authenticating the requesting UE; after the HSS/AAA completes the authentication of the UE, transmitting, to the trusted non-3GPP access gateway 2, the IP address of the P-GW selected by the UE through the access network 1 and the APN signed by the UE
- step S304 after the authentication succeeds, the attach procedure of layer 3 is triggered; step S305, the trusted non-3GPP access gateway 2 camping on the BBERF sends a gateway control session establishment request message to the PCRF, at the gateway.
- the control session establishment request message carries the NAI of the UE and the default APN.
- the PCRF finds the information before the user handover according to the NAI and the default APN of the UE, associates the message with the session before the handover, and associates the corresponding QoS. Rules and events
- the sender sends a "Gateway Control Session Establishment Confirmation" message to the trusted non-3GPP access gateway 2.
- the PCRF may also update previous QoS rules and event triggers.
- the trusted non-3GPP access gateway 2 installs a QoS rule and an event trigger.
- Step S307 The trusted non-3GPP access gateway 2 sends a proxy binding update message to the P-GW, where the binding update message carries the UE.
- Step S308 after receiving the proxy binding update message, the P-GW camping on the PCEF sends an IP-CAN session modification indication to the PCRF, and carries the NAI and P of the UE in the IP-CAN session modification indication.
- - GW assigns an IP address and a default APN to the UE;
- Step S309 after receiving the IP-CAN session modification indication, the PCRF sends an IP-CAN session modification confirmation message to the P-GW according to the PCC rule before the UE handover.
- the PCRF may update the previously established PCC and QoS rules.
- the P-GW installs and executes the PCC rule.
- Step S310 the P-GW returns a proxy binding confirmation message to the trusted non-3GPP access gateway.
- Step S311 If the QoS rule updated in step S309 is different from that delivered in step S306, the PCRF sends the updated QoS rule to the trusted non-3GPP access gateway by using the gateway control and the QoS policy rule providing message.
- the trusted non-3GPP access gateway installs the QoS rule, and returns the gateway control and the QoS policy rule to provide the confirmation; Step S313, the layer 3 attachment is completed; Step S314, the trusted non-3GPP access gateway 2 and the P-GW are established.
- PMIPv6 tunnel
- the UE can send or receive data, and the process ends.
- the PCRF in S305 receives the gateway control session establishment indication message carrying the NAI and the default APN
- the PCRF cannot determine that the UE has occurred because the message received when the UE accesses the APN again is the same.
- the handover ie, BBERF for reselection
- BBERF for reselection
- the prior art also has the above two problems.
- the present invention is directed to an access control method and system for a packet data network, and a policy and charging rule function entity, to solve the problem that when the UE accesses the same APN multiple times, the PCRF cannot determine whether the UE is multiple times. Access to the same APN does not identify different IP-CAN sessions. According to an aspect of the present invention, an access control method for a packet data network is provided.
- the access control method of the packet data network includes: the policy and charging rule function entity receives a gateway control session establishment indication message from the bearer binding and event reporting function entity, where the gateway control session establishment indication message carries The session identifier is used to identify whether the user equipment accesses the same packet data network or the bearer binding and event reporting function entity for reselection; the policy and charging rule function entity receives the control session establishment indication message from the gateway, Obtaining a session identifier, and determining, according to the session identifier, that the user equipment is accessing the packet data network again It is a physical reselection of the bearer binding and event reporting function.
- the session identifier is also used to uniquely identify a network protocol connection access network session of the user equipment.
- the method further includes: a bearer binding and an event reporting function entity Sending a proxy binding update request message to the policy and charging execution function entity, and carrying the session identifier in the proxy binding update request message; the policy and charging execution function entity receiving the proxy binding update request message, to the policy and charging rule
- the function entity sends a network protocol connection access network session establishment indication message, and carries the session identifier in the network protocol connection access network session establishment indication message; the policy and charging rule function entity uses the session identifier to control the gateway control session establishment indication message and the network The protocol connects to the access network session establishment indication message for association.
- the method further includes: the bearer binding and event reporting function entity assigning the session identifier.
- the method before the bearer binding and event reporting function entity sends the gateway control session establishment indication message, the method further includes: the mobility management unit assigns the session identifier; and the mobility management unit sends a default bearer setup request to the bearer binding and event reporting function entity.
- the message carries the session identifier in the default bearer setup request message.
- the information of the session identifier is added to the access point name, and the name of the access point carrying the information of the session identifier is used as the session identifier.
- the information of the session identifier is added to the default bearer address, and the default 7
- the method further includes: establishing a session based on the gateway control session The indication message, the policy and charging rule function entity formulates a policy and charging control rule, a quality of service rule and a corresponding event trigger, and sends a gateway control session establishment confirmation message to the bearer binding and event reporting function entity, and controls at the gateway
- the session establishment confirmation message carries the quality of service rule and the event trigger; the bearer binding and event reporting function entity receives the gateway control session establishment confirmation message, obtains the service quality rule and the event trigger, and installs the service quality rule and the event trigger.
- the gateway control session establishment indication message does not carry the session identifier.
- the method before the policy and charging rule function entity receives the gateway control session establishment indication message from the bearer binding and event reporting function entity, the method further includes: a user equipment based packet data network connection request message, a bearer binding and an event reporting function. The entity sends a gateway control session establishment indication message to the policy and charging rule function entity.
- an access control method for a packet data network is also provided.
- the access control method of the packet data network includes: the bearer binding and event reporting function entity sends a gateway control session establishment indication message to the policy and charging rule function entity, where the gateway control session establishment indication message carries a session identifier, the session identifier is used to uniquely identify a network protocol connection access network session of the user equipment; the bearer binding and event reporting function entity sends a proxy binding update request message to the policy and charging execution function entity, and binds in the proxy The update request message carries the session identifier; the policy and charging execution function entity receives the proxy binding update request message, and sends a network protocol connection access network session establishment indication message or a network protocol connection access network session to the policy and charging rule function entity.
- an access control system for a packet data network is provided.
- the access control system of the packet data network includes: a bearer binding and event reporting function entity, configured to send a gateway control session establishment indication message, and carry a session identifier in the gateway control session establishment indication message, where The session identifier is used to distinguish whether the user equipment accesses the same packet data network or the bearer binding and event reporting function entity reselection, and a network protocol connection access network session that uniquely identifies the user equipment; the policy and charging rule function entity And receiving, by the gateway from the bearer binding and event reporting function, a control session establishment indication message, obtaining a session identifier, and determining, according to the session identifier, whether the user equipment accesses the packet data network or bears the binding and event reporting function. Weight selection.
- the bearer binding and event reporting function entity is further configured to allocate a session identifier.
- the bearer binding and event reporting function entity is further configured to send the session identifier a proxy binding update request message, and a receiving gateway control session establishment confirmation message, obtaining a quality of service rule and an event trigger, and installing a quality of service rule and an event trigger; a policy and charging rule function entity, and also receiving a network protocol Connecting the access network session establishment indication message, and carrying the session identifier in the network protocol connection access network session establishment indication message, and correlating the gateway control session establishment indication message with the network protocol connection access network session establishment indication message by using the session identifier, And, based on the gateway control session establishment indication message, formulating a policy and charging control rule, a quality of service rule, and a corresponding event trigger, and sending a gateway control session establishment confirmation message to the bearer binding and event reporting function entity, and controlling the session at the gateway
- the establishment confirmation message carries the quality of service rules and event triggers.
- the access control system of the packet data network further includes: a policy and charging execution function entity, configured to receive a proxy binding update request message from the bearer binding and event reporting function entity, to the policy and charging rule function The entity sends a network protocol connection access network session establishment indication message, and carries the session identifier in the network protocol connection access network session establishment indication message.
- the access control system of the packet data network further includes: a mobility management unit, configured to allocate a session identifier, and send a default bearer setup request message to the bearer binding and event reporting function entity, and in the default bearer setup request message Carry the session ID.
- an access control system for a packet data network is also provided.
- An access control system for a packet data network includes: a bearer binding and event reporting function entity, configured to send a gateway control session establishment indication message to a policy and charging rule function entity, and establish a control session establishment indication at the gateway The message carries a session identifier, where the session identifier is used to uniquely identify a network protocol connection access network session of the user equipment; the bearer binding and event reporting function entity is further configured to send a proxy binding update to the policy and charging execution function entity.
- a policy and charging execution function entity configured to receive a proxy binding update request message, and send a network protocol connection access network to the policy and charging rule function entity
- the session establishment indication message or the network protocol connection access network session modification indication message and carrying the session identifier in the network protocol connection access network session establishment indication message or the network protocol connection access network session modification indication message
- the policy and the charging rule function Entity used to receive bindings from bearers and
- the gateway control session establishment indication message of the report function entity and the network protocol connection access network session establishment indication message or the network protocol connection access network session modification indication message of the policy and charging execution function entity, and the gateway is determined according to the session identifier Controlling the session establishment indication message and the network protocol connection access network session establishment indication message or the network protocol connection access network session modification indication message
- a policy and charging rule function entity is provided.
- the policy and charging rule function entity includes: a receiving module, configured to receive a gateway control session establishment indication message from a bearer binding and event reporting function entity, where the gateway control session establishment indication message carries a session The identifier, the session identifier is used to identify whether the user equipment accesses the same packet data network or the bearer binding and event reporting function entity reselection; the obtaining module is configured to obtain the session identifier from the control session establishment indication message; According to the session identifier, it is determined whether the user equipment is re-accessed to the packet data network or the bearer binding and event reporting function entity reselection. According to still another aspect of the present invention, a policy and charging rule function entity is also provided.
- the policy and charging rule function entity includes: a receiving module, configured to receive a gateway control session establishment indication message from a bearer binding and event reporting function entity, and a network protocol connection access of a policy charging execution function entity
- the network session establishment indication message or the network protocol connection access network session modification indication message where the gateway control session establishment indication message, the network protocol connection access network session establishment indication message, and the network protocol connection access network session modification indication message are carried in a session identifier, where the session identifier is used to uniquely identify a network protocol connection access network session of the user equipment; and an acquisition module, configured to control the session establishment indication message from the gateway and the network protocol connection access network session establishment indication message or network protocol connection Obtaining a session identifier in the access network session modification indication message; the association module, configured to: use the gateway control session establishment indication message and the network protocol connection access network session establishment indication message or the network protocol connection access network session modification indication according to the session identifier Message Union.
- the gateway control session establishment indication message by carrying the session identifier in the gateway control session establishment indication message, it is provided whether the user equipment is re-accessed to the same packet data network or the bearer binding and event reporting function entity reselection and identifies different IP-CANs.
- the session method is applied to the 3GPP evolved packet system.
- the PCRF can determine that the UE accesses the same APN multiple times and uniquely identifies different IP-CAN sessions.
- FIG. 1 is a schematic diagram of a system architecture of an EPS according to the related art
- 2 is a flow chart of an initial attachment of a UE to a EPS through a trusted non-3GPP access network according to the related art
- FIG. 3 is a diagram of a UE switching from one trusted non-3GPP access network to another according to the related art
- FIG. 4 is a flowchart of a method for controlling access of a packet data network according to an embodiment of the present invention
- FIG. 5 is a flowchart of an access control method for a packet data network according to an embodiment of the present invention
- FIG. 6 is a flowchart of an access control method of a packet data network according to Embodiment 2 of the present invention
- FIG. 7 is a flowchart of an access control method of a packet data network according to Embodiment 3 of the present invention
- FIG. 9 is a block diagram of a preferred structure of an access control system for a packet data network according to an embodiment of the present invention
- FIG. 10 is a schematic diagram of a preferred structure of an access control system for a packet data network according to an embodiment of the present invention
- the access control method includes: Step S402: A PCRF entity receives a gateway control session establishment indication message from a BBERF entity, where The gateway control session establishment indication message carries a session identifier, where the session identifier is used to identify whether the user equipment accesses the same packet data network or the BBERF entity reselection; the session identifier is also used to uniquely identify a network protocol connection access of the user equipment.
- Step S404 The PCRF entity receives a control session establishment indication message from the gateway, obtains a session identifier from the gateway, and determines, according to the session identifier, whether the UE accesses the packet data network or the BBERF entity reselection.
- the method further includes: (41) controlling a session establishment indication message based on the gateway, the PCRF entity formulating a policy and charging control rule, a quality of service rule, and a corresponding event trigger, and sending a gateway control session establishment to the BBERF entity. Acknowledge the message, and carry the quality of service rules and event triggers in the gateway control session establishment confirmation message;
- the BBERF entity receives a gateway control session establishment confirmation message, obtains a service quality rule and an event trigger, and installs a quality of service rule and an event trigger;
- the BBERF entity sends a proxy binding update request message to the PCEF entity, and carries the session identifier in the proxy binding update request message;
- the PCEF entity receives the proxy binding update request message, sends a network protocol connection access network session establishment indication message to the PCRF entity, and carries the session identifier in the network protocol connection access network session establishment indication message;
- the PCRF entity associates the gateway control session establishment indication message with the network protocol connection access network session establishment indication message by using the session identifier.
- the above method further includes one of the following two situations:
- the BBERF entity allocates a session identifier.
- the session identifier may also be in the following manner: The session identifier information is added to the access point name, and the access point name carrying the session identifier information is used as the session identifier.
- the mobility management unit allocates a session identifier; the mobility management unit sends a default bearer setup request message to the BBERF entity, and carries the session identifier in the default bearer setup request message; wherein the session identifier may also have the following two representation manners: The information of the session identifier is added to the access point name, and the name of the access point carrying the information of the session identifier is used as the session identifier; the information of the session identifier is added to the default bearer address (ie, the default bearer ID), and the session identifier is carried. The default 7
- the piece reporting function entity sends a gateway control session establishment indication message to the policy and charging rule function entity.
- the session control session establishment indication message does not carry the session identifier when the UE first accesses or reestablishes the initial access PDN.
- Embodiment 1 This embodiment describes that when the UE is in the coverage of the trusted non-3GPP access network and accesses the EPS system by using PMIPv6, the UE has accessed one PDN1 through the P-GW, and the UE triggers a new one. PDN connection, the process of accessing this PDN1 again.
- 5 is a flowchart of an access control method of a packet data network according to Embodiment 1 of the present invention. As shown in FIG. 5, the steps of this embodiment are described as follows: Step S501: The UE performs initial attach to trusted non-3GPP access. The gateway obtains an IP connection with the default PDN1 through the P-GW, and the access point corresponding to the PDN1 is named APN1.
- step S502 the UE determines to establish a new PDN connection with the PDN1, and sends a trigger indication to the trusted non-3GPP access gateway.
- a message where the trigger indication message carries the APN1
- the trusted non-3GPP access gateway that camps on the BBERF sends a "Gateway Control Session Establishment Indication" message to the PCRF, where Controlling the session establishment indication "The message carries the identity of the UE NAI, APN1 and the session identifier; wherein the session identifier can be assigned by the trusted non-3GPP access gateway, in order to ensure that an IP-CAN session is uniquely identified, the identifier is at least for the same The UE is unique to the same APN.
- the trusted non-3GPP access gateway may modify APN1 to force the information of the session identification.
- APN1 is internet.operator.com
- the session number is only 2
- APN1 is the internet.operator.com:2.
- the session label is only included in the APN1 of the decoration.
- the PCRF determines that the UE establishes a connection to the PDN1 according to the session identifier, so that the PCRF formulates the PCC rule according to the subscription data, the network policy, and the bearer attribute of the user.
- PCRF sends QoS rules and event triggers to BBERF via "Gateway Control Session Establishment Confirmation", BBERF installs QoS rules and event triggers;
- the S503 message carries the modified APN1, and then the PCRF can analyze that the UE establishes a connection and session identification information to the PDN1 according to the modified APN1.
- Step S505 the trusted non-3GPP access gateway to the P-GW And sending a "Proxy Binding Update" request message, where the "Proxy Binding Update” request message carries the NAI, APN1, and the session identifier, and the step S505 can be sent after receiving the step S502 step message, without waiting for step S504.
- the NAI and the modified APN1 may also be carried in the "Proxy Binding Update” message, and the session identification information is included in the modified APN1;
- Step S506 the P-GW camping on the PCEF sends the "IP" to the PCRF.
- the -CAN session establishment indication message wherein the "IP-CAN session establishment indication" message carries the NAI, the APN1, the session identifier, and the IP address assigned by the P-GW to the UE. Passing the NAI, APN1, and session identifiers to associate the IP-CAN session establishment indication message with the "Gateway Control Session Establishment Indication" message in step S503, thereby associating the information established by the two messages in the PCRF to the same IP-CAN session;
- the NAI and the modified APN 1 may also be carried in the IP-CAN session establishment indication message, and the session identification information is included in the decorated APN 1; in step S507, the PCRF returns an "IP-CAN session establishment confirmation" to the P-GW. , message, where,
- the "IP-CAN session establishment confirmation" message carries the corresponding PCC rule and event trigger, and the P-GW installs the PCC rule and the event trigger. If the modified APN1 carried in step S506, the PCRF can analyze the session identifier. Information: Step S508, the P-GW saves information such as its own IP address to the HSS; Step S509, the P-GW returns a "Proxy Binding Confirmation” message to the trusted non-3GPP access gateway, where the "Proxy Binding Confirmation” The message carries the IP address assigned by the P-GW to the UE. Step S510, the trusted non-3GPP access gateway returns a response message to the UE, where the response The answer message carries the IP address of the UE.
- Step S511 If the information carried in the IP-CAN session establishment indication message in step S506 causes the QoS rule to change, the PCRF sends the new QoS rule through the gateway control and the QoS rule providing message.
- the message may be sent simultaneously with step S507;
- Step S512 the trusted non-3GPP access gateway returns through the gateway control and QoS The rule provides a confirmation message; Step S513, a trusted ⁇ tunnel is established between the trusted non-3GPP access gateway and the P-GW in addition to the initially established ⁇ tunnel.
- the trusted non-3GPP access gateway may not need to allocate the session identifier, and may only be trusted when the UE accesses the same PDN for the second time or the second time.
- the non-3GPP access gateway only needs to allocate the session identifier, so that the PCRF determines that the same PDN establishes the connection again and associates the message sent by the trusted non-3GPP access gateway with the message sent by the PCEF.
- Embodiment 2 This embodiment describes that when the UE is in the coverage of 3GPP, access is through E-UTRAN, and the PM-IPv6 is used between the S-GW and the P-GW, and the UE is already connected through the P-GW.
- FIG. 6 is a flowchart of an access control method of a packet data network according to Embodiment 2 of the present invention. As shown in FIG. 6, the steps of the access control method are as follows: Step S601: The UE performs initial attach to E-UTRAN, Obtaining an IP connection with the default PDN1 through the P-GW, the access point corresponding to the PDN1 is named APN1; Step S602, the UE determines to establish a new PDN connection with the PDN1, and sends a PDN connection request message, where the PDN connection request message The APN1 carries the APN1; Step S603, the MME allocates a session identifier to the connection according to the PDN connection request message, and sends a default bearer setup request message to the S-GW, where the default bearer setup request message carries the APN1 and the default 7
- the "Gateway Control Session Establishment Indication” message carries the NAI and the modified APN1; Step S605, the PCRF determines that the UE has established a connection to the PDN1 according to the session identifier, so that the PCRF is based on the user's subscription data, network policy, The PCC rules and the Qos rules are formulated for the bearer attributes. At the same time, corresponding event triggers may be formulated.
- the PCRF sends the QoS rules and event triggers to the S-GW through the "Gateway Control Session Establishment Confirmation" message, and the S-GW installs the QoS rules.
- step S604 the S-GW sends the decorated APN1, then the PCRF can analyze the modified APN1 and the UE establishes a connection and session identification information to the PDN1;
- step S606 the S-GW sends a "Proxy Binding Update” request message to the P-GW, where the "Proxy Binding Update” request message carries the NAI, APN 1 and the session identifier;
- Step S606 may receive the message of step S603.
- Step S607 the P-GW camping on the PCEF sends an "IP-CAN Session Establishment Indication” message to the PCRF, where the "IP-CAN Session Establishment Indication” message carries the NAI, APN1, session identifier, and P - the IP address assigned by the GW to the UE; the PCRF associates the "IP-CAN Session Establishment Indication” message with the "Gateway Control Session Establishment Indication” message in step S605 via NAI, APN1 and session identification, thereby, the two messages are in the PCRF
- the established information is associated with the same IP-CAN session; step S608, the PCRF returns an "IP-CAN Session Establishment Confirmation" message to the P-GW, wherein the "IP-CAN Session Establishment Confirmation” message carries
- the QoS rule providing message sends the new QoS rule to the trusted non-3GPP access gateway. If the event trigger also changes, providing a new event trigger, the message may be sent simultaneously with step S608; Step S611, S-GW Returning the gateway control and QoS rule providing confirmation message to the PCRF; Step S612, the S-GW returns a default bearer setup confirmation message to the MME, where the default bearer setup acknowledgement message carries the IP address of the UE; Step S613, the MME, the eNodeB, and the UE After the radio bearer is established, the MME sends an update bearer request to the S-GW, notifies the eNodeB of the address information, and the S-GW returns a response message.
- the embodiment may be implemented by the following process:
- the MME sends a default bearer setup request message to the S-GW, where the default setup request message carries the APN1 and the default ID.
- the default ID is different from the default MME assigned by the MME at the initial attach; in step S604, the S-GW camping on the BBERF determines that the UE establishes a connection with the PDN1 according to the default bearer ID.
- the "Gateway Control Session Establishment Indication" message carries the identifiers of the UEs NAI, APN1, and the default 7
- step S604 the S-GW camping on the BBERF determines that the UE establishes a connection with the PDN1 according to the default bearer ID, and may also assign a session identifier to the connection, in the "gateway control session establishment indication" message. And the message carries this session identifier. It should be noted that when the UE accesses the PDN network for the first time, the MME or the S-GW does not need to allocate the session identifier.
- Embodiment 3 After the UE establishes two PDN connections to APN1 according to the procedure of Embodiment 1, the UE switches from one trusted non-3GPP access network 1 to another trusted non-3GPP access network 2 to access the EPS. The process is as shown in FIG. 7.
- the radio access technologies of the two trusted non-3GPP access networks are the same.
- Step S701 The UE accesses the trusted non-3GPP through the process of FIG. Entering the network 1 and establishing two PDN connections to the default APN1 through the access network; Step S702, the UE discovers the trusted non-3GPP access network 2, and decides to initiate the handover; Step S703, the UE accesses the trusted non- After the 3GPP access network 2, the HSS/AAA is requested to perform EPS access authentication; after the HSS/AAA receives the EPS access authentication request, the requesting UE is authenticated; after the HSS/AAA completes the authentication of the UE, Sending, to the trusted non-3GPP access gateway 2, the IP address of the P-GW selected by the UE through the access network 1 and the APN signed by the UE, including the default APN1; Step S704, after the authentication succeeds, the attach procedure of layer 3 is triggered.
- Step S705 trusted non-3GPP access residing with BBERF
- the gateway 2 sends a gateway control session establishment request message to the PCRF, and carries the NAI of the UE and the default APN 1 in the gateway control session establishment request message.
- the PCRF finds the information before the user handover according to the NAI of the UE and the default APN1, and The message is associated with the session before the handover, and the QoS rule and the event trigger corresponding to the first PDN connection to the APN1 established before the handover are sent to the trusted non-3GPP access through the "Gateway Control Session Establishment Confirmation" message.
- the PCRF may also update previous QoS rules and event triggers.
- the trusted non-3GPP access gateway 2 installs a QoS rule and an event trigger.
- Step S707 The trusted non-3GPP access gateway 2 sends a proxy binding update message to the P-GW, where the proxy binding update message carries the NAI of the UE, The default APN1, step S707 can be sent after receiving the message of step S704, without waiting for the response of step S706; step S708, after receiving the proxy binding update message, the P-GW camping on the PCEF sends the IP to the PCRF.
- the IP session modification indication indicates that the IP-CAN session modification indication carries the NAI of the UE, the P-GW is the IP address assigned by the first PDN connection established before the UE handover, and the default APN1;
- the PCRF receives the IP-CAN session.
- the PCC rule of the first PDN connection established before the UE handover is sent to the IP-CAN session tampering confirmation message ⁇ P-GW.
- the PCRF may update the previously established PCC, QoS rules, and event triggers.
- the P-GW installs and executes the PCC rules and event triggers.
- the P-GW sends the trusted non-3GPP.
- Step S711 If the QoS rule updated in step S709 is different from that delivered in step S706, the PCRF provides the updated QoS rule by using the gateway control and the QoS policy rule.
- the event trigger is sent to the trusted non-3GPP access gateway;
- Step S712 the trusted non-3GPP access gateway installs the QoS rule, and returns the gateway control and the QoS policy rule to provide confirmation;
- Step S713, the layer 3 attachment is completed;
- Step S714 A PMIPv6 tunnel is established between the trusted non-3GPP access gateway 2 and the P-GW.
- the UE re-establishes a PDN connection to the default APN1.
- the UE sends a trigger indication message to the trusted non-3GPP access gateway 2, where the trigger indication message carries the APN1 and the handover indication, and the handover indication is used to the trusted non-
- the 3GPP access gateway indicates that a PDN connection before the handover is re-established; in step S716, the trusted non-3GPP access gateway 2 camping on the BBERF determines that a PDN connection to the APN1 needs to be established according to the handover indication, so the gateway is sent to the PCRF.
- Control session establishment indication "The message carries the identity of the UE NAI, APN1 and the session identifier; wherein the session identifier may be the same as the session identifier in the trusted non-3GPP access gateway 1, and the session identifier is accessed through trusted non-3GPP
- the gateway 1 and the trusted non-3GPP access gateway 2 are obtained by interaction; the session identifier may also be different from the trusted non-3GPP access gateway 1 except that it is allocated by the trusted non-3GPP access gateway 2, and the identifier is used to indicate that a PDN is reconstructed.
- the trusted non-3GPP access gateway 2 may modify APN1 to force the information of the session identification.
- APN1 it forms an APN1, for example: APN1 is internet.operator.com, the session is only 2, and the APN1 is internet.operator.com:2, which means that the session is only It is included in the APN1 of the enamel.
- Step S717 the PCRF finds the letter before the user switching according to the NAI of the UE and the default APN1. Interest. If the session identifier of the step S716 is obtained through the interaction between the access gateways, the PCRF passes the QoS rule and the event trigger corresponding to the second PDN connection to the APN1 established before the handover according to the session identifier.
- the session establishment confirmation message is sent to the trusted non-3GPP access gateway 2.
- the trusted non-3GPP access gateway 2 installs QoS rules and event triggers. Otherwise, the PCRF does not perform any operation; if the APN1 is carried in the message in the step S716, the PCRF may analyze that the UE re-establishes a connection and session identification information to the PDN1 according to the modified APN1; Step S718, The trusted non-3GPP access gateway 2 sends a "proxy binding update" request message to the P-GW, where the "proxy binding update” request message carries the NAI, APN1 and session identifier, and step S718 can receive the step After the S715 step message can be sent, there is no need to wait for the response of step S717; also in the "proxy binding update” message can also carry the NAI and the modified APN1, the session identification information is included in the modified APN1; step S719, resident The P-GW that leaves the PCEF sends an "IP-CAN Se
- the IP address assigned by the second PDN connection is established; the NAI and the modified APN 1 may also be carried in the IP-CAN session establishment indication message, and the session identification information is included in the decorated APN 1; Step S720, P
- the CRF associates the IP-CAN session modification indication with the gateway control session establishment indication message in step S716 according to the session identifier, so as to connect the PCC of the second PDN connection established before the UE handover.
- the rules and event triggers are sent to the P-GW via an IP-CAN session modification confirmation message.
- the PCRF may update the previously established PCC, QoS rules, and event triggers.
- the P-GW After receiving the IP-CAN session modification confirmation message, the P-GW installs and executes the PCC rules and event triggers; if the modified APN1 carried in step S719 The PCRF may analyze the session identification information.
- Step S723 if the information carried in the IP-CAN session establishment indication message in step S719 leads to the QoS rule A change has occurred.
- the PCRF will send a new QoS rule to the trusted non-3GPP access gateway through the gateway control and QoS rule provisioning message. If the event trigger has also changed, a new event trigger is provided, and the message can be followed.
- S720 transmits at the same time;
- Step S724 the trusted non-3GPP access gateway 2 returns an acknowledgement message through the gateway control and the QoS rule;
- Step S725 the trusted 3 ⁇ tunnel between the non-3GPP access gateway 2 and the P-GW Bu, a new ⁇ 6 tunnel is established, and now the UE establishes two PDN connections with APN1.
- the UE accesses the EPS through the E-UTRAN according to the embodiment 2, and establishes two PDN connections to the APN1.
- the BBERF reselection occurs.
- the UE also re-establishes the connection of the first PDN established before the handover.
- the BBERF does not carry the session identifier when interacting with the PCRF and the PCEF and the PCRF.
- the PCRF will correspond to the rule and event trigger of the first PDN connection established before the handover.
- FIG. 8 is a block diagram of an access control system of a packet data network according to an embodiment of the present invention. As shown in FIG.
- the access control system includes: a BBERF entity 82, configured to send a gateway control session establishment indication message, where When the UE requests to access the same packet data network after accessing the packet data network, the BBERF entity carries the session identifier in the gateway control session establishment indication message, where the session identifier is used to uniquely identify the UE in one access point name. In addition, it is also used to allocate a session identifier, send a proxy binding update request message carrying a session identifier, and receive a gateway control session establishment confirmation message, Quality of service rules and event triggers, and install quality of service rules and event triggers;
- the PCRF entity 84 is connected to the BBERF entity 82, and configured to receive a control session establishment indication message from the gateway of the BBERF entity, obtain a session identifier from the network identifier, and determine, according to the session identifier, that the UE establishes a connection to the access point name again;
- the network protocol is connected to the access network session establishment indication message, and carries the session identifier in the network protocol connection access network session establishment indication message, and the gateway control session establishment indication message and the network protocol connection access network session establishment indication message are performed by using the session identifier.
- FIG. 9 is a block diagram showing a preferred structure of an access control system of a packet data network according to an embodiment of the present invention. As shown in FIG. 9, the access control system of the packet data network further includes:
- the PCEF entity 92 is connected to the BBERF entity 82 and the PCRF entity 84, configured to receive a proxy binding update request message from the BBERF entity, send a network protocol connection access network session establishment indication message to the PCRF entity, and access the network protocol connection.
- the network session establishment indication message carries the session identifier;
- the mobility management unit 94 is connected to the BBERF entity 82, configured to allocate the session identifier, and sends a default 7* bearer setup request message to the BBERF entity, and in the default 7
- a policy and charging rule function entity is provided.
- FIG. 10 is a block diagram of a policy and charging rule function entity according to an embodiment of the present invention.
- a policy and charging rule function entity includes: a receiving module 102, configured to receive a bearer from a bearer. And a gateway control session establishment indication message, where the gateway control session establishment indication message carries a session identifier, where the session identifier is used to identify whether the user equipment accesses the same packet data network or bears bindings and events again.
- the reporting function entity reselection; the obtaining module 104 is connected to the receiving module 102, and configured to obtain the session identifier from the control session establishment indication message;
- the determining module 106 is connected to the obtaining module 104, configured to determine, according to the session identifier, whether the user equipment is re-accessing the packet data network or the bearer binding and event reporting function entity reselection.
- a method for distinguishing different IP-CAN sessions is provided, which is applied to the 3GPP evolved packet system, so that when the UE accesses the same APN multiple times, the PCRF It can be judged that the UE accesses the same APN multiple times, and uniquely identifies only different IP-CAN sessions.
- the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices.
- the invention is not limited to any specific combination of hardware and software.
- the above is only the preferred embodiment of the present invention, and is not intended to limit the present invention.
- various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made therein are intended to be included within the scope of the present invention.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Description
分组数据网络的接入控制方法和系统
PCRF实体
技术领域 本发明涉及通信领域, 具体而言, 涉及一种分组数据网络( Packet Data Network ,简称为 PDN )的接入控制方法和系统、策略和计费规则功能( Policy and Charging Rules Function, 简称为 PCRF ) 实体。 背景技术 第三 4弋合作伙伴计划( 3rd Generation Partnership Project, 简称为 3GPP ) 演进的分组系统 ( Evolved Packet System , 简称为 EPS ) 由演进的通用移动 通信系统陆地无线接入网 ( Evolved Universal Terrestrial Radio Access Network , 简称为 E-UTRAN ) , 移动管理单元 ( Mobility Management Entity , 简称为 MME )、 月艮务网关 (Serving Gateway , S-GW )、 分组数据网络网关 ( Packet Data Network Gateway , 简称为 P-GW或者 PDN GW)、 归属用户月艮 务器 ( Home Subscriber Server , 简称为 HSS )、 3GPP 的认证 4曼权计费 ( Authentication、 Authorization and Accounting , 简称为 AAA )月艮务器, 策 略和计费规则功能 (简称为 PCRF ) 实体及其他支撑节点组成。 图 1是根据相关技术的 EPS的系统架构的示意图, 如图 1所示, MME 负责移动性管理、 非接入层信令的处理和用户移动管理上下文的管理等控制 面的相关工作; S-GW是与 E-UTRAN相连的接入网关设备, 在 E-UTRAN 和 P-GW之间转发数据,并且负责对寻呼等待数据进行緩存; P-GW则是 EPS 与分组数据网络 ( Packet Data Network , 简称为 PDN ) 网络的边界网关, 负 责 PDN的接入及在 EPS与 PDN间转发数据等功能; PCRF是策略和计费规 则功能实体, 它通过接收接口 Rx和运营商网络十办议 ( Internet Protocol , 简称 为 IP ) 业务网络相连, 获取业务信息, 此外, 它通过 Gx/Gxa/Gxc接口与网 络中的网关设备相连, 负责发起 IP 承载的建立, 保证业务数据的服务质量 ( Quality of Service , 简称为 QoS ), 并进行计费控制。
EPS 支持与非 3GPP 系统的互通, 其中, 与非 3GPP 系统的互通通过 S2a/b/c接口实现, P-GW作为 3GPP与非 3GPP系统间的锚点。 在 EPS的系 统架构图中,非 3GPP系统被分为可信任非 3GPP IP接入和不可信任非 3GPP IP接入。 可信任非 3GPP IP接入可直接通过 S2a接口与 P-GW连接; 不可信 任非 3GPP IP接入需经过演进的分组数据网关( Evolved Packet Data Gateway, 简称为 ePDG ) 与 P-GW相连, ePDG与 P-GW间的接口为 S2b, S2c提供了 用户设备 ( User Equipment , 简称为 UE )与 P-GW之间的用户面 目关的控制 和移动性支持, 其支持的移动性管理¼、议为支持双栈的移动 IPv6 (Mobile IPv6 Support for Dual Stack Hosts and Routers , 简称为 DSMIPv6)。 在 EPS之前的 3GPP网络中,策略和计费执行功能( Policy and Charging
Enforcement Function, 简称为 PCEF ) 实体存在于 P-GW中, PCRF与 P-GW 之间只要存在接口即可完成所有功能的控制, PCRF与 P-GW间通过 Gx接 口(见图 1 )交换信息。 当 P-GW与 S-GW间的接口基于代理移动 IPv6( Proxy Mobile IPv6, 简称为 PMIPv6 ) 时, S-GW也具有承载绑定和事件报告功能 ( Bearer Binding and Event Report Function, 简称为 BBERF ) 实体对业务数 据流进行 QoS控制, S-GW与 PCRF之间通过 Gxc接口 (见图 1 )交换信息。 当通过可信任非 3GPP接入系统接入时, 可信任非 3GPP接入网关中也驻留 BBERF。 可信任非 3GPP接入网关与 PCRF之间通过 Gxa接口 (见图 1 ) 交 换信息。 当 UE漫游时, S9接口作为归属地 PCRF和拜访地 PCRF的接口, 同时为 UE提供业务的应用功能 (Application Function, 简称为 AF ), 通过 Rx接口向 PCRF发送用于制定策略和计费控制( Policy and Charging Control, 简称为 PCC ) 策略的业务信息。 EPS系统支持 Multiple PDN接入, 即, UE 可以通过多个 P-GW或者一个 P-GW同时接入到多个 PDN, 并且 EPS支持 UE可以同时接入同一个 PDN多次。 在 3GPP中, 通过接入点名称 ( Access Point Name, 简称为 APN )可以找到对应的 PDN网络。 因 匕, 可以认为 UE 可以同时接入同一个 APN多次。 通常将 UE到 PDN网络的一个连接称为一 个 IP连接接入网 ( IP Connectivity Access Network, 简称为 IP-CAN ) 会话, 因此, EPS支持 UE可以同时与一个 PDN网络有多个 IP-CAN会话。 图 2是才艮据相关技术的 UE通过可信任非 3GPP接入网接入 EPS的初始 附着的流程图, 如图 2所示, UE通过可信任非 3GPP接入网初始附着到一个 PDN的具体步骤如下: 步骤 S201 , UE接入可信任非 3GPP接入网;
步骤 S202 , 在 UE接入到可信任非 3GPP接入网之后, 向 HSS/AAA请 求进行 EPS接入认证; 在 HSS/AAA接收到 EPS接入认证请求之后, 对发出 请求的 UE进行认证;在 HSS/AAA完成对 UE的认证之后,向可信任非 3GPP 接入网关发送 UE签约的 P-GW选择信息和 UE签约的 APN,包括默认 APN; 步骤 S203 , 在认证成功之后, 层 3的附着流程被触发; 步骤 S204, 驻留有 BBERF的可信任非 3GPP接入网关向 PCRF发送网 关控制会话建立请求消息, 在网关控制会话建立请求消息中携带 UE的网络 接入标识 ( Network Access Identifier, 简称为 NAI ) 和,默认 APN; 步骤 S205 , PCRF 才艮据用户的签约数据、 网络策略、 承载属性等制定 PCC规则和 QoS规则, 同时,也可能制定相应的事件触发器; PCRF通过"网 关控制会话建立确认" 消息将 QoS规则和事件触发器发送给可信任非 3GPP 接入网关; 可信任非 3GPP接入网关安装 QoS规则和事件触发器; 步骤 S206, 可信任非 3GPP接入网关接收到 P-GW选择信息后, 根据 P-GW选择信息选定 P-GW, 并向所选定的 P-GW发送代理绑定更新消息, 代理绑定更新消息中携带有 UE的 NAI和默认 APN; 步骤 S207,驻留有 PCEF的 P-GW接收到代理绑定更新消息后,向 PCRF 发送 IP-CAN会话建立指示, 在 IP-CAN会话建立指示中携带 UE的 NAI、 P-GW为 UE分配的 IP地址和默认 APN; 步骤 S208 , PCRF接收到 IP-CAN会话建立指示后, 才艮据 UE的 NAI 和默认 APN将 IP-CAN会话建立指示消息和之前的网关控制会话建立指示消 息进行关联, 同时, 查询 UE的签约信息, 根据用户的签约信息、 网络策略 和承载属性等对之前制定的规则进行更新, PCRF向 P-GW发送 IP-CAN会 话建立确认消息, 在该 IP-CAN会话建立确认消息中携带 PCC规则; 步骤 S209, P-GW接收到 IP-CAN会话建立确认消息后, 安装并执行 IP-CAN会话建立确认消息中携带的 PCC规则, 同时, 将其自身的 IP地址发 送到 HSS; 步骤 S210, P-GW向可信任非 3GPP接入网关返回代理绑定确认消息;
步骤 S211 , 若步骤 S208步中制定的 QoS规则与步骤 S205步中下发的 不同, 则 PCRF通过网关控制和 QoS策略规则提供消息将更新的 QoS规则 下发给可信任非 3GPP接入网关; 步骤 S212, 可信任非 3GPP接入网关安装 QoS规则, 并返回网关控制 和 QoS策略规则提供确认; 步骤 S213 , 层 3附着完成; 步骤 S214, 可信任非 3GPP接入网关与 P-GW之间建立 PMIPv6隧道,
UE可以进行数据发送或接收, 本次流程结束。 当 UE建立到默认 APN的第二个 PDN连接时, UE向可信任非 3GPP 接入网关发送 "触发新建 PDN连接消息", 并在 "触发新建 PDN连接消息" 中携带默认 APN, 其余的步骤如 S204-S214所示。 每建立一个 PDN连接, P-GW为 UE分配一个 IP地址。 在上述流程中, 可信任非 3GPP接入网关与 PCRF的交互在 P-GW与 PCRF的交互之前, 此时, 可信任非 3GPP网关还没有 P-GW为 UE分配的 IP地址, 不管是初始附着还是第二次接入, 以及多次接入同一个 PDN, 当可 信任非 3GPP接入网关与 PCRF交互时, 可信任非 3GPP接入网关只有 NAI 和,默认 APN。 由于一个 UE对于同一个 PDN (或者 APN )的多次连接, NAI 和默认 APN都是相同的, 所以, PCRF根据这些信息无法区分这多个 PDN 连接,也就无法将属于同一个 PDN连接的网关控制会话消息和 IP-CAN会话 消息进行关联。 然而, 对于 PCRF来说, 属于同一个 IP-CAN会话的网关控制会话消息 和 IP-CAN会话消息必须是——对应的。 因为 PCC规则包括 QoS控制策略 和计费策略, 而 QoS规则中只有 QoS控制策略。 PCC规则的计费策略是跟 提供的 QoS相关的, 也就是说安装在 PCEF的计费策略与安装在 BBERF上 的 QoS控制策略必须是相关的。为了保证计费的正确, PCRF必须确保 PCEF 中成功激活的 PCC规则在 BBERF中存在对应的成功激活的 QoS规则。而对 应的 PCC规则和 QoS规则是通过对应的网关控制会话消息和 IP-CAN会话 消息下发的。 同样地, UE接入同一个 PDN (或者 APN ) 多次, 也会使现有 的切换技术存在问题。 图 3为 UE从一个可信任非 3GPP接入网 1接入 EPS 切换到另一个可信任非 3GPP接入网 2接入 EPS的流程,两个可信任非 3GPP
接入网络的无线接入技术是相同的。 具体步骤如下: 步骤 S301 , UE通过如图 2的流程, 接入可信任非 3GPP接入网 1 , 并 通过该接入网络建立到默认 APN的 PDN连接; 步骤 S302, UE发现可信任非 3GPP接入网 2, 并决定发起切换; 步骤 S303 , 在 UE接入到可信任非 3GPP接入网 2之后, 向 HSS/AAA 请求进行 EPS接入认证; 在 HSS/AAA接收到 EPS接入认证请求之后, 对发 出请求的 UE进行认证; 在 HSS/AAA完成对 UE的认证之后, 向可信任非 3GPP接入网关 2发送 UE在通过接入网络 1选择的 P-GW的 IP地址和 UE 签约的 APN , 包括,默认 APN; 步骤 S304, 在认证成功之后, 层 3的附着流程被触发; 步骤 S305 , 驻留有 BBERF的可信任非 3GPP接入网关 2向 PCRF发送 网关控制会话建立请求消息, 在网关控制会话建立请求消息中携带 UE 的 NAI和默认 APN; 步骤 S306, PCRF才艮据 UE的 NAI和默认 APN找到用户切换前的信息, 将该消息与切换前的会话进行关联,并将对应的 QoS规则和事件触发器通过 "网关控制会话建立确认" 消息发送给可信任非 3GPP接入网关 2。 PCRF也 可能更新之前的 QoS规则和事件触发器。 可信任非 3GPP接入网关 2安装 QoS规则和事件触发器; 步骤 S307 , 可信任非 3GPP接入网关 2向 P-GW发送代理绑定更新消 息, 4弋理绑定更新消息中携带有 UE的 NAI和,默认 APN; 步骤 S308 ,驻留有 PCEF的 P-GW接收到代理绑定更新消息后,向 PCRF 发送 IP-CAN会话修改指示, 在 IP-CAN会话修改指示中携带 UE的 NAI、 P-GW为 UE分配的 IP地址和默认 APN; 步骤 S309 , PCRF接收到 IP-CAN会话修改指示后, 才艮据 UE切换前的 PCC规则通过 IP-CAN会话修改确认消息发送给 P-GW。 PCRF可能更新之 前制定的 PCC和 QoS规则。 P-GW接收到 IP-CAN会话建立确认消息后, 安 装并执行 PCC规则; 步骤 S310, P-GW向可信任非 3GPP接入网关返回代理绑定确认消息;
步骤 S311 , 若步骤 S309步中更新的 QoS规则与步骤 S306步中下发的 不同, 则 PCRF通过网关控制和 QoS策略规则提供消息将更新的 QoS规则 下发给可信任非 3GPP接入网关; 步骤 S312, 可信任非 3GPP接入网关安装 QoS规则, 并返回网关控制 和 QoS策略规则提供确认; 步骤 S313 , 层 3附着完成; 步骤 S314,可信任非 3GPP接入网关 2与 P-GW之间建立 PMIPv6隧道,
UE可以进行数据发送或接收, 本次流程结束。 在该流程中, 当 S305中 PCRF接收到携带有 NAI和默认 APN的网关 控制会话建立指示消息时,由于与 UE再次接入 APN时收到的消息是一样的, 因此 PCRF无法判断是 UE发生了切换(即 BBERF进行重选)还是 UE请求 建立到默认 APN的又一个 PDN连接。 当 UE从 E-UTRAN接入, 并且 S-GW和 P-GW之间釆用 PMIPv6十办议 时, 现有技术同样存在上述两个问题。 (1 ) 当 PCRF收到网关控制会话建立 指示消息时, 无法判断是 BBERF重选还是 UE请求建立到一个 APN的有一 个 PDN 连接。 (2 ) 无法将与同一个 PDN 连接相关的网关控制会话消息和 IP-CAN会话消息进行关联。 发明内容 本发明旨在提供一种分组数据网络的接入控制方法和系统、策略和计费 规则功能实体, 以解决当 UE接入同一个 APN 多次时, PCRF 不能够判断 UE是否为多次接入同一个 APN, 无法标识不同的 IP-CAN会话的问题。 才艮据本发明的一个方面, 提供了一种分组数据网络的接入控制方法。 根据本发明实施例的分组数据网络的接入控制方法包括:策略和计费规 则功能实体接收来自承载绑定和事件报告功能实体的网关控制会话建立指示 消息, 其中, 网关控制会话建立指示消息携带有会话标识, 会话标识用于标 识用户设备是再次接入同一个分组数据网络还是承载绑定和事件报告功能实 体进行重选; 策略和计费规则功能实体从网关接收控制会话建立指示消息, 从中获取会话标识, 根据会话标识判断用户设备是再次接入分组数据网络还
是承载绑定和事件报告功能实体重选。 优选地,会话标识还用于唯一标识用户设备的一个网络协议连接接入网 会话。 优选地,在策略和计费规则功能实体根据会话标识判断用户设备是再次 接入分组数据网络还是承载绑定和事件报告功能实体重选之后, 上述方法进 一步包括: 承载绑定和事件报告功能实体向策略和计费执行功能实体发送代 理绑定更新请求消息, 并在代理绑定更新请求消息中携带会话标识; 策略和 计费执行功能实体接收代理绑定更新请求消息, 向策略和计费规则功能实体 发送网络协议连接接入网会话建立指示消息, 并在网络协议连接接入网会话 建立指示消息中携带会话标识; 策略和计费规则功能实体通过会话标识将网 关控制会话建立指示消息和网络协议连接接入网会话建立指示消息进行关 联。 优选地,在承载绑定和事件报告功能实体发送网关控制会话建立指示消 息之前, 上述方法进一步包括: 承载绑定和事件报告功能实体分配会话标识。 优选地,在承载绑定和事件报告功能实体发送网关控制会话建立指示消 息之前, 上述方法进一步包括: 移动管理单元分配会话标识; 移动管理单元 向承载绑定和事件报告功能实体发送默认承载建立请求消息, 并在默认承载 建立请求消息中携带会话标识。 优选地, 将会话标识的信息加入接入点名称, 并将携带有会话标识的信 息的接入点名称作为会话标识。 优选地, 将会话标识的信息加入默认承载地址, 并将携带有会话标识的 信息的默认 7|载地址作为会话标识。 优选地 ,在策略和计费规则功能实体才艮据会话标识判断用户设备再是再 次接入分组数据网络还是承载绑定和事件报告功能实体重选之后, 上述方法 进一步包括: 基于网关控制会话建立指示消息, 策略和计费规则功能实体制 定策略和计费控制规则、 服务质量规则和相应的事件触发器, 并向承载绑定 和事件 告功能实体发送网关控制会话建立确认消息, 并在网关控制会话建 立确认消息中携带服务质量规则和事件触发器; 承载绑定和事件报告功能实 体接收网关控制会话建立确认消息, 从中获取服务质量规则和事件触发器, 并安装艮务质量规则和事件触发器。
优选地, 在用户设备初次接入或重建初次接入分组数据网络时, 网关控 制会话建立指示消息中不携带会话标识。 优选地,在策略和计费规则功能实体接收来自承载绑定和事件报告功能 实体的网关控制会话建立指示消息之前还包括: 基于用户设备的分组数据网 络连接请求消息, 承载绑定和事件报告功能实体向策略和计费规则功能实体 发送网关控制会话建立指示消息。 才艮据本发明的一个方面, 还提供了一种分组数据网络的接入控制方法。 根据本发明实施例的分组数据网络的接入控制方法包括:承载绑定和事 件报告功能实体向策略和计费规则功能实体发送网关控制会话建立指示消 息, 其中, 网关控制会话建立指示消息携带有会话标识, 会话标识用于唯一 标识用户设备的一个网络协议连接接入网会话; 承载绑定和事件报告功能实 体向策略和计费执行功能实体发送代理绑定更新请求消息, 并在代理绑定更 新请求消息中携带会话标识; 策略和计费执行功能实体接收代理绑定更新请 求消息, 向策略和计费规则功能实体发送网络协议连接接入网会话建立指示 消息或网络协议连接接入网会话修改指示消息, 并在网络协议连接接入网会 话建立指示消息或网络协议连接接入网会话修改指示消息中携带会话标识; 策略和计费规则功能实体通过会话标识将网关控制会话建立指示消息和网络 协议连接接入网会话建立指示消息或网络协议连接接入网会话修改指示消息 进行关联。 根据本发明的另一个方面, 提供了一种分组数据网络的接入控制系统。 根据本发明实施例的分组数据网络的接入控制系统包括:承载绑定和事 件报告功能实体, 用于发送网关控制会话建立指示消息, 并在网关控制会话 建立指示消息中携带会话标识, 其中, 会话标识用于区分用户设备为再次接 入同一个分组数据网络还是承载绑定和事件报告功能实体重选, 以及唯一标 识用户设备的一个网络协议连接接入网会话; 策略和计费规则功能实体, 用 于接收来自承载绑定和事件报告功能实体的网关接收控制会话建立指示消 息, 从中获取会话标识, 并根据会话标识判断用户设备为再次接入分组数据 网络还是承载绑定和事件报告功能实体重选。 优选地, 承载绑定和事件报告功能实体还用于分配会话标识。 优选地, 承载绑定和事件报告功能实体, 还用于发送携带有会话标识的
代理绑定更新请求消息, 以及接收网关控制会话建立确认消息, 从中获取服 务质量规则和事件触发器, 并安装服务质量规则和事件触发器; 策略和计费 规则功能实体, 还用于接收网络协议连接接入网会话建立指示消息, 并在网 络协议连接接入网会话建立指示消息中携带会话标识, 通过会话标识将网关 控制会话建立指示消息和网络协议连接接入网会话建立指示消息进行关联, 以及基于网关控制会话建立指示消息, 制定策略和计费控制规则、 服务质量 规则和相应的事件触发器, 并向承载绑定和事件报告功能实体发送网关控制 会话建立确认消息, 并在网关控制会话建立确认消息中携带服务质量规则和 事件触发器。 优选地, 上述分组数据网络的接入控制系统进一步包括: 策略和计费执 行功能实体, 用于接收来自承载绑定和事件报告功能实体的代理绑定更新请 求消息, 向策略和计费规则功能实体发送网络协议连接接入网会话建立指示 消息, 并在网络协议连接接入网会话建立指示消息中携带会话标识。 优选地,上述分组数据网络的接入控制系统进一步包括:移动管理单元, 用于分配会话标识, 以及向承载绑定和事件报告功能实体发送默认承载建立 请求消息, 并在默认承载建立请求消息中携带会话标识。 根据本发明的另一个方面, 还提供了一种分组数据网络的接入控制系 统。 根据本发明实施例的分组数据网络的接入控制系统包括:承载绑定和事 件报告功能实体, 用于向策略和计费规则功能实体发送网关控制会话建立指 示消息, 并在网关控制会话建立指示消息中携带会话标识, 其中, 会话标识 用于唯一标识用户设备的一个网络协议连接接入网会话; 承载绑定和事件报 告功能实体还用于向策略和计费执行功能实体发送代理绑定更新请求消息, 并在代理绑定更新请求消息中携带会话标识; 策略和计费执行功能实体, 用 于接收代理绑定更新请求消息, 并向策略和计费规则功能实体发送网络协议 连接接入网会话建立指示消息或网络协议连接接入网会话修改指示消息, 并 在网络协议连接接入网会话建立指示消息或网络协议连接接入网会话修改指 示消息中携带会话标识; 策略和计费规则功能实体, 用于接收来自承载绑定 和事件报告功能实体的网关控制会话建立指示消息和策略和计费执行功能实 体的网络协议连接接入网会话建立指示消息或网络协议连接接入网会话修改 指示消息, 并才艮据会话标识将网关控制会话建立指示消息和网络协议连接接 入网会话建立指示消息或网络协议连接接入网会话修改指示消息进行关
根据本发明的再一个方面, 提供了一种策略和计费规则功能实体。 根据本发明实施例的策略和计费规则功能实体包括: 接收模块, 用于接 收来自承载绑定和事件报告功能实体的网关控制会话建立指示消息, 其中, 网关控制会话建立指示消息中携带有会话标识, 会话标识用于标识用户设备 是再次接入同一个分组数据网络还是承载绑定和事件报告功能实体重选; 获 取模块, 用于从控制会话建立指示消息中获取会话标识; 判断模块, 用于根 据会话标识判断用户设备是再次接入分组数据网络还是承载绑定和事件报告 功能实体重选。 根据本发明的再一个方面, 还提供了一种策略和计费规则功能实体。 根据本发明实施例的策略和计费规则功能实体包括: 接收模块, 用于接 收来自承载绑定和事件报告功能实体的网关控制会话建立指示消息和策略计 费执行功能实体的网络协议连接接入网会话建立指示消息或网络协议连接接 入网会话修改指示消息, 其中, 网关控制会话建立指示消息、 网络协议连接 接入网会话建立指示消息、 网络协议连接接入网会话修改指示消息中携带有 会话标识, 其中, 会话标识用于唯一标识用户设备的一个网络协议连接接入 网会话; 获取模块, 用于从网关控制会话建立指示消息和网络协议连接接入 网会话建立指示消息或网络协议连接接入网会话修改指示消息中获取会话标 识; 关联模块, 用于才艮据会话标识将网关控制会话建立指示消息和网络协议 连接接入网会话建立指示消息或网络协议连接接入网会话修改指示消息进行 关联。 在以上实施例中, 通过在网关控制会话建立指示消息中携带会话标识, 提供了区分用户设备是再次接入同一个分组数据网络还是承载绑定和事件报 告功能实体重选以及标识不同 IP-CAN会话的方法, 应用于 3GPP演进的分 组系统, 使得 UE接入同一个 APN多次时, PCRF能够判断 UE多次接入同 一个 APN , 并且唯一标识不同的 IP-CAN会话。 附图说明 附图用来提供对本发明的进一步理解, 并且构成说明书的一部分, 与本 发明的实施例一起用于解释本发明, 并不构成对本发明的限制。 在附图中: 图 1是根据相关技术的 EPS的系统架构的示意图;
图 2是才艮据相关技术的 UE通过可信任非 3GPP接入网接入 EPS的初始 附着的流程图; 图 3是根据相关技术的 UE从一个可信任非 3GPP接入网切换到另外一 个可信任非 3GPP接入网的流程图; 图 4是根据本发明实施例的分组数据网络的接入控制方法的流程图; 图 5是根据本发明实施例一的分组数据网络的接入控制方法的流程图; 图 6是根据本发明实施例二的分组数据网络的接入控制方法的流程图; 图 7是根据本发明实施例三的分组数据网络的接入控制方法的流程图; 图 8是根据本发明实施例的分组数据网络的接入控制系统的方框图; 图 9 是根据本发明实施例的分组数据网络的接入控制系统的优选结构 的方才匡图; 图 10是根据本发明实施例的策略和计费规则功能实体的方框图。 具体实施方式 以下结合附图对本发明的优选实施例进行说明, 应当理解, 此处所描述 的优选实施例仅用于说明和解释本发明, 并不用于限定本发明。 方法实施例 根据本发明的实施例, 提供了一种分组数据网络的接入控制方法。 图 4是根据本发明实施例的 PDN的接入控制方法的流程图, 如图 4所 示, 该接入控制方法包括: 步骤 S402 , PCRF实体接收来自 BBERF实体的网关控制会话建立指示 消息, 其中, 网关控制会话建立指示消息携带有会话标识, 会话标识用于标 识用户设备是再次接入同一个分组数据网络还是 BBERF 实体重选; 会话标 识还用于唯一标识用户设备的一个网络协议连接接入网会话;需要说明的是, 在 UE初次接入或重建初次接入 PDN时, 网关控制会话建立指示消息中不携 带会话标识, 这样, 就可以对终端的再次接入和 BBERF重选进行区分;
步骤 S404, PCRF实体从网关接收控制会话建立指示消息, 从中获取会 话标识, 艮据会话标识判断 UE 是再次接入所述分组数据网络还是 BBERF 实体重选。 在步骤 S404之后, 上述方法进一步包括: ( 41 )基于网关控制会话建立指示消息, PCRF实体制定策略和计费控 制规则、 服务质量规则和相应的事件触发器, 并向 BBERF 实体发送网关控 制会话建立确认消息, 并在网关控制会话建立确认消息中携带服务质量规则 和事件触发器;
( 42 ) BBERF 实体接收网关控制会话建立确认消息, 从中获取服务质 量规则和事件触发器, 并安装服务质量规则和事件触发器;
( 43 ) BBERF实体向 PCEF实体发送代理绑定更新请求消息, 并在代 理绑定更新请求消息中携带会话标识;
( 44 ) PCEF实体接收代理绑定更新请求消息, 向 PCRF实体发送网络 协议连接接入网会话建立指示消息, 并在网络协议连接接入网会话建立指示 消息中携带会话标识;
( 45 ) PCRF实体通过会话标识将网关控制会话建立指示消息和网络协 议连接接入网会话建立指示消息进行关联。 在步骤 S402之前, 上述方法进一步包括以下两种情况之一:
( 1 ) BBERF实体分配会话标识; 其中, 上述会话标识还可以有如下表 示方式: 将会话标识的信息加入接入点名称, 并将携带有会话标识的信息的 接入点名称作为会话标识。
( 2 ) 移动管理单元分配会话标识; 移动管理单元向 BBERF 实体发送 默认承载建立请求消息, 并在默认承载建立请求消息中携带会话标识; 其中, 上述会话标识还可以有如下两种表示方式: 将会话标识的信息加入接入点名 称, 并将携带有会话标识的信息的接入点名称作为会话标识; 将会话标识的 信息加入默认承载地址 (即, 默认承载 ID ), 并将携带有会话标识的信息的 默认 7|载地址作为会话标识。 在此之后, 基于用户设备的分组数据网络连接请求消息, 承载绑定和事
件报告功能实体向策略和计费规则功能实体发送网关控制会话建立指示消 息。 并且, 在 UE初次接入或重建初次接入 PDN时, 网关控制会话建立指 示消息中不携带会话标识。 通过以上实施例, 当 UE接入同一个 APN多次时, PCRF能够判断 UE 多次接入同一个 APN , 并且唯一标只不同的 IP-CAN会话。 实施例一 本实施例描述的是当 UE处于可信任非 3GPP接入网的覆盖范围内, 并 釆用 PMIPv6接入到 EPS系统, UE通过 P-GW已经接入一个 PDN1 , UE又 触发新的 PDN连接, 又一次接入这个 PDN1的过程。 图 5是根据本发明实施例一的分组数据网络的接入控制方法的流程图, 如图 5所示, 该实施例的步骤描述如下: 步骤 S501 , UE执行初始附着到可信任非 3GPP接入网关, 通过 P-GW 获得了与默认 PDN1的 IP连接, 该 PDN1对应的接入点名为 APN1; 步骤 S502, UE决定与 PDN1建立新的 PDN连接, 向可信任非 3GPP 接入网关发送触发指示消息, 其中, 触发指示消息中携带有 APN1; 步骤 S503 , 基于上述触发指示消息, 驻留有 BBERF的可信任非 3GPP 接入网关在向 PCRF发送 "网关控制会话建立指示" 消息, 其中, "网关控制 会话建立指示" 消息中携带有 UE的标识 NAI、 APN1和会话标识; 其中, 会话标识可以由可信任非 3GPP接入网关分配, 为了确保唯一标 识一个 IP-CAN会话, 该标识至少对于同一个 UE同一个 APN是唯一的。 在实现时, 可信任非 3GPP接入网关可以将 APN1进行修饰, 将会话标 识的信息力。入 APN1 中 , 构成一个 爹饰的 APN1。 如: APN1 为 internet.operator.com , 会话标 只为 2 , 刃 么 爹饰 后 的 APN1 为 internet.operator.com:2。 也是说, 会话标只包含在爹饰的 APN1里。 步骤 S504, PCRF才艮据会话标识, 判断 UE又建立了一个到 PDN1的连 接, 从而, PCRF根据用户的签约数据、 网络策略、 承载属性等制定 PCC规
则和 QoS规则, 同时, 也可能制定相应的事件触发器; PCRF通过 "网关控 制会话建立确认', 消息将 QoS规则和事件触发器发送给 BBERF, BBERF安 装 QoS规则和事件触发器; 如果在步骤 S503消息中携带的是修饰后的 APN1 , 那么, PCRF可以根 据修饰后的 APN1分析出 UE又建立了一个到 PDN1的连接和会话标识信息。 步骤 S505 , 可信任非 3GPP接入网关向 P-GW发送 "代理绑定更新" 请求消息, 其中, 该 "代理绑定更新" 请求消息中携带有 NAI、 APN1和会 话标识, 步骤 S505可以在接收到步骤 S502步消息后就能发送, 不必等待步 骤 S504的响应; 同样在 "代理绑定更新" 消息中也可以携带 NAI和修改后的 APN1 , 会 话标识信息包含在修饰后的 APN1中; 步骤 S506, 驻留有 PCEF的 P-GW向 PCRF发送 "IP-CAN会话建立指 示" 消息, 其中, 该 "IP-CAN会话建立指示" 消息中携带有 NAI、 APN1、 会话标识和 P-GW为 UE分配的 IP地址。 PCRF通过 NAI、 APN1和会话标 识将 IP-CAN会话建立指示消息与步骤 S503中的 "网关控制会话建立指示" 消息进行关联, 从而将两消息在 PCRF建立的信息关联到同一个 IP-CAN会 话; 同样在 IP-CAN 会话建立指示消息中也可以携带 NAI 和修饰后的 APN 1 , 会话标识信息包含在爹饰后的 APN 1中; 步骤 S507 , PCRF向 P-GW返回 "IP-CAN会话建立确认 ', 消息, 其中,
"IP-CAN 会话建立确认" 消息中携带有相应的 PCC 规则和事件触发器, P-GW安装 PCC规则和事件触发器; 如果在步骤 S506中携带的修饰后的 APN1 , PCRF可以分析出会话标识 信息; 步骤 S508 , P-GW将自己的 IP地址等信息保存到 HSS; 步骤 S509 , P-GW向可信任非 3GPP接入网关返回 "代理绑定确认" 消 息, 其中, 该 "代理绑定确认" 消息中携带有 P-GW为 UE分配的 IP地址; 步骤 S510, 可信任非 3GPP接入网关向 UE返回应答消息, 其中, 该应
答消息携带有 UE的 IP地址; 步骤 S511 , 如果步骤 S506中 IP-CAN会话建立指示消息中携带的信息 导致 QoS规则发生了变化, PCRF将通过网关控制和 QoS规则提供消息将新 的 QoS规则发送给可信任非 3GPP接入网关, 若事件触发器也发生了改变, 提供新的事件触发器, 该消息可以和步骤 S507同时发送; 步骤 S512 , 可信任非 3GPP接入网关返回通过网关控制和 QoS规则提 供确认消息; 步骤 S513 , 可信任非 3GPP 接入网关和 P-GW 之间除了初始建立的 ΡΜΙΡνό隧道外, 又建立了新 ΡΜΙΡνό隧道。 需要指出的是, 当 UE第一次接入 PDN网络时, 可信任非 3GPP接入 网关可以不需要分配会话标识,只有当 UE接入同一个 PDN第二次或第二次 以上时, 可信任非 3GPP接入网关才需要分配会话标识, 以便于 PCRF判断 同一个 PDN的又一次建立连接和将可信任非 3GPP接入网关发送的消息与 PCEF发送的消息进行关联。 实施例二 本实施例描述的是当 UE处于 3GPP的覆盖范围内, 通过 E-UTRAN接 入, 并且 S-GW和 P-GW之间釆用 PMIPv6十办议, UE通过 P-GW已经接入 一个 PDN1 , UE又触发新的 PDN连接, 又一次接入这个 PDN1的过程。 图 6是根据本发明实施例二的分组数据网络的接入控制方法的流程图, 如图 6所示, 该接入控制方法的步骤描述如下: 步骤 S601 , UE执行初始附着到 E-UTRAN, 通过 P-GW获得了与默认 PDN1的 IP连接, 该 PDN1对应的接入点名为 APN1 ; 步骤 S602, UE决定与 PDN1建立新的 PDN连接, 发送 PDN连接请求 消息, 其中, 该 PDN连接请求消息中携带 APN1 ; 步骤 S603 , 基于上述 PDN连接请求消息, MME为该连接分配会话标 识, 并向 S-GW发送默认承载建立请求消息, 其中, 该默认承载建立请求消 息携带有 APN1和默认 7|载 ID和会话标识信息;
在实现时, MME可以将 APN1进行爹饰,将会话标识的信息力口入 APN1 中, 构成一个修_饰的 APN 1; 步骤 S604, 驻留有 BBERF的 S-GW在 "网关控制会话建立指示" 消息 中携带 UE的标只 NAI、 APN1和会话标只; 如果在步骤 S603中, MME发送的是爹饰后的 APN1 , 那么, S-GW在
"网关控制会话建立指示" 消息中携带 NAI和修饰后的 APN1; 步骤 S605 , PCRF才艮据会话标识, 判断 UE又建立了一个到 PDN1的连 接, 从而, PCRF根据用户的签约数据、 网络策略、 承载属性等制定 PCC规 则和 Qos规则, 同时, 也可能制定相应的事件触发器, PCRF通过 "网关控 制会话建立确认" 消息将 QoS规则和事件触发器发送给 S-GW, S-GW安装 QoS规则和事件触发器; 如果在步骤 S604 中, S-GW 发送的是爹饰后的 APN1 , 那么, PCRF 可以才艮据修饰后的 APN1分析出 UE又建立了一个到 PDN1的连接和会话标 识信息; 步骤 S606, S-GW向 P-GW发送 "代理绑定更新" 请求消息, 其中, 该 "代理绑定更新" 请求消息中携带 NAI、 APN 1和会话标识; 步骤 S606可 以在接收到步骤 S603消息后就能发送, 不必等待步骤 S605的响应; 如果在步骤 S603中釆用了修饰后的 APN1 , 那么, "代理绑定更新" 请 求消息中携带 NAI和修 _饰后的 APN 1; 步骤 S607 , 驻留有 PCEF的 P-GW向 PCRF发送 "IP-CAN会话建立指 示" 消息, 其中, 该 "IP-CAN会话建立指示" 消息携带有 NAI、 APN1、 会 话标识和 P-GW为 UE分配的 IP地址; PCRF通过 NAI、 APN1和会话标识 将 "IP-CAN会话建立指示"消息与步骤 S605中的 "网关控制会话建立指示" 消息进行关联, 从而, 将两消息在 PCRF建立的信息关联到同一个 IP-CAN 会话; 步骤 S608 , PCRF向 P-GW返回 "IP-CAN会话建立确认" 消息, 其中, 该 "IP-CAN会话建立确认"消息携带有相应的 PCC规则和事件触发器, PCEF 安装 PCC规则和事件触发器; 步骤 S609 , P-GW向 S-GW返回 "代理绑定确认" 消息, 其中, 该 "代
理绑定确认 ', 消息携带有 P-GW为 UE分配的 IP地址; 步骤 S610, 如果步骤 S607中 IP-CAN会话建立指示消息中携带的信息 导致 QoS规则发生了变化, PCRF将通过网关控制和 QoS规则提供消息将新 的 QoS规则发送给可信任非 3GPP接入网关, 若事件触发器也发生了改变, 提供新的事件触发器, 该消息可以和步骤 S608同时发送; 步骤 S611 , S-GW向 PCRF返回网关控制和 QoS规则提供确认消息; 步骤 S612, S-GW向 MME返回默认 载建立确认消息, 其中, 该默认 载建立确认消息携带有 UE的 IP地址; 步骤 S613 , MME、 eNodeB、 UE之间交互, 建立无线^载; 步骤 S614, 在无线承载建立之后, MME向 S-GW发送更新承载请求, 通知 eNodeB的地址信息等, S-GW返回应答消息。 此外, 该实施例也可以通过如下过程来实现: 在步骤 S603中, MME 向 S-GW发送默认承载建立请求消息, 其中, 该默认 ^l载建立请求消息携带有 APN1和默认 ^l载 ID, 该默认 ^l载 ID与初 始附着时 MME分配的 ,默认 载 ID是不同的; 在步骤 S604中, 驻留有 BBERF的 S-GW才艮据默认承载 ID来判断 UE 与 PDN1 又建立了一个连接, 在 "网关控制会话建立指示" 消息中携带 UE 的标识 NAI、 APN1和默认 7|载 ID, 即, 会话标识釆用默认 载 ID; 在后续 的步骤中, 均可以用默认 载 ID作为会话标识; 在步骤 S604中, 驻留有 BBERF的 S-GW才艮据默认承载 ID来判断 UE 与 PDN1又建立了一个连接, 也可以为这个连接分配一个会话标识, 在 "网 关控制会话建立指示 " 消息和消息中携带这个会话标识。 需要指出的是, 当 UE第一次接入 PDN网络时, MME或 S-GW都不需 要分配会话标识,只有当 UE接入同一个 PDN第二次或第二次以上时, MME 或 S-GW才需要分配会话标识, 以便于 PCRF能够判断同一个 PDN的又一 次建立连接和将 S-GW发送的消息与 PCEF发送的消息进行关联。 实施例三
UE才艮据实施例一的流程, 建立了两个到 APN1的 PDN连接后, UE从 一个可信任非 3GPP接入网 1接入 EPS切换到另一个可信任非 3GPP接入网 2接入 EPS的过程如图 7所示, 其中, 两个可信任非 3GPP接入网络的无线 接入技术是相同的, 具体步骤包括: 步骤 S701 , UE通过如图 5的流程, 接入可信任非 3GPP接入网 1 , 并 通过该接入网络建立到默认 APN1的两个 PDN连接; 步骤 S702, UE发现可信任非 3GPP接入网 2, 并决定发起切换; 步骤 S703 , 在 UE接入到可信任非 3GPP接入网 2之后, 向 HSS/AAA 请求进行 EPS接入认证; 在 HSS/AAA接收到 EPS接入认证请求之后, 对发 出请求的 UE进行认证; 在 HSS/AAA完成对 UE的认证之后, 向可信任非 3GPP接入网关 2发送 UE在通过接入网络 1选择的 P-GW的 IP地址和 UE 签约的 APN , 包括默认 APN1; 步骤 S704, 在认证成功之后, 层 3的附着流程被触发; 步骤 S705 , 驻留有 BBERF的可信任非 3GPP接入网关 2向 PCRF发送 网关控制会话建立请求消息, 在网关控制会话建立请求消息中携带 UE 的 NAI、 默认 APN 1 ; 步骤 S706, PCRF才艮据 UE的 NAI和默认 APN1找到用户切换前的信 息, 将该消息与切换前的会话进行关联, 并将切换前建立的到 APN1的第一 个 PDN连接所对应的 QoS规则和事件触发器通过 "网关控制会话建立确认" 消息发送给可信任非 3GPP接入网关 2。 PCRF也可能更新之前的 QoS规则 和事件触发器。 可信任非 3GPP接入网关 2安装 QoS规则和事件触发器; 步骤 S707 , 可信任非 3GPP接入网关 2向 P-GW发送代理绑定更新消 息, 代理绑定更新消息中携带有 UE的 NAI、 默认 APN1 , 步骤 S707可以在 接收到步骤 S704步消息后就能发送, 不必等待步骤 S706的响应; 步骤 S708,驻留有 PCEF的 P-GW接收到代理绑定更新消息后,向 PCRF 发送 IP-CAN会话修改指示, 在 IP-CAN会话修改指示中携带 UE的 NAI、 P-GW为 UE切换前建立的第一个 PDN连接分配的 IP地址和默认 APN1 ; 步骤 S709 , PCRF接收到 IP-CAN会话修改指示后, 将 UE切换前建立 的第一个 PDN 连接的 PCC 规则通过 IP-CAN 会话爹改确认消息^送给
P-GW。 PCRF可能更新之前制定的 PCC、 QoS规则和事件触发器, P-GW接 收到 IP-CAN会话修改确认消息后, 安装并执行 PCC规则和事件触发器; 步骤 S710, P-GW向可信任非 3GPP接入网关 2返回代理绑定确认消息; 步骤 S711 , 若步骤 S709步中更新的 QoS规则与步骤 S706步中下发的 不同, 则 PCRF通过网关控制和 QoS策略规则提供消息将更新的 QoS规则 和事件触发器下发给可信任非 3GPP接入网关; 步骤 S712, 可信任非 3GPP接入网关安装 QoS规则, 并返回网关控制 和 QoS策略规则提供确认; 步骤 S713 , 层 3附着完成; 步骤 S714,可信任非 3GPP接入网关 2与 P-GW之间建立 PMIPv6隧道,
UE重建了到默认 APN1的一个 PDN连接; 步骤 S715 , UE向可信任非 3GPP接入网关 2发送触发指示消息,其中, 触发指示消息中携带有 APN1 和切换指示, 切换指示用于向可信任非 3GPP 接入网关表明重建切换前的一个 PDN连接; 步骤 S716 ,驻留有 BBERF的可信任非 3GPP接入网关 2根据切换指示 判断需要再建立一个到 APN1的 PDN连接, 所以在向 PCRF发送 "网关控制 会话建立指示" 消息中携带 UE的标识 NAI、 APN1和会话标识; 其中, 会话标识可以与可信任非 3GPP接入网关 1中的会话标识相同, 而这会话标识是通过可信任非 3GPP接入网关 1和可信任非 3GPP接入网关 2 交互获得的; 会话标识也可以与可信任非 3GPP接入网关 1不同, 只是由可 信任非 3GPP接入网关 2分配,该标识用来表明再建一个 PDN连接或唯一标 识一个 IP-CAN会话, 若需要唯一标识一个 IP-CAN会话, 该标识至少对于 同一个 UE同一个 APN是唯一的。 在实现时, 可信任非 3GPP接入网关 2可以将 APN1进行修饰, 将会话 标识的信息力。入 APN1 中, 构成一个爹饰的 APN1 , 例如: APN1 为 internet.operator.com , 会话标 只为 2 , 刃 么 , 爹饰后的 APN1 为 internet.operator.com:2 , 也是说, 会话标只包含在爹饰的 APN1里。 步骤 S717 , PCRF才艮据 UE的 NAI和默认 APN1找到用户切换前的信
息。 若步骤 S716 的会话标识是通过接入网关之间交互获得的, 那么 PCRF 才艮据会话标识将切换前建立的到 APN1的第二个 PDN连接所对应的 QoS规 则和事件触发器通过 "网关控制会话建立确认" 消息发送给可信任非 3GPP 接入网关 2。 可信任非 3GPP接入网关 2安装 QoS规则和事件触发器。 否则 PCRF不故任何操作; 如果在步骤 S716消息中携带的是爹饰后的 APN1, 那么, PCRF可以根 据修饰后的 APN1分析出 UE又重建了一个到 PDN1的连接和会话标识信息; 步骤 S718 , 可信任非 3GPP接入网关 2向 P-GW发送 "代理绑定更新" 请求消息, 其中, 该 "代理绑定更新" 请求消息中携带有 NAI、 APN1和会 话标识, 步骤 S718可以在接收到步骤 S715步消息后就能发送, 不必等待步 骤 S717的响应; 同样在 "代理绑定更新" 消息中也可以携带 NAI和修改后的 APN1 , 会 话标识信息包含在修饰后的 APN1中; 步骤 S719 , 驻留有 PCEF的 P-GW向 PCRF发送 "IP-CAN会话爹改指 示" 消息, 其中, 该 "IP-CAN会话修改指示" 消息中携带有 NAI、 APN1、 会话标识和 P-GW为 UE切换前建立的第二个 PDN连接分配的 IP地址; 同样在 IP-CAN 会话建立指示消息中也可以携带 NAI 和修饰后的 APN 1 , 会话标识信息包含在爹饰后的 APN 1中; 步骤 S720, PCRF接收到 IP-CAN会话修改指示后, 根据会话标识, 将 IP-CAN会话修改指示与 S716步中的网关控制会话建立指示消息进行关联, 从而将 UE 切换前建立的第二个 PDN 连接的 PCC规则和事件触发器通过 IP-CAN会话修改确认消息发送给 P-GW。 PCRF可能更新之前制定的 PCC、 QoS规则和事件触发器, P-GW接收到 IP-CAN会话修改确认消息后, 安装 并执行 PCC规则和事件触发器; 如果在步骤 S719中携带的修饰后的 APN1 , PCRF可以分析出会话标识 信息; 步骤 S721 , P-GW向可信任非 3GPP接入网关 2返回 "代理绑定确认" 消息, 其中, 该 "代理绑定确认" 消息中携带有 P-GW为 UE切换前建立的 第二个 PDN连接分配的 IP地址;
步骤 S722, 可信任非 3GPP接入网关 2向 UE返回应答消息, 其中, 该 应答消息携带有 UE的 IP地址; 步骤 S723 , 如果步骤 S719中 IP-CAN会话建立指示消息中携带的信息 导致 QoS规则发生了变化, PCRF将通过网关控制和 QoS规则提供消息将新 的 QoS规则发送给可信任非 3GPP接入网关, 若事件触发器也发生了改变, 提供新的事件触发器, 该消息可以和步骤 S720同时发送; 步骤 S724 , 可信任非 3GPP接入网关 2返回通过网关控制和 QoS规则 提供确认消息; 步骤 S725 , 可信任非 3GPP接入网关 2和 P-GW之间除了切换建立的 ΡΜΙΡνό隧道夕卜, 又建立了新 ΡΜΙΡν6隧道, 现在 UE与 APN1建立了两个 PDN连接。
UE才艮据实施例 2通过 E-UTRAN接入 EPS ,建立了到 APN1的两个 PDN 连接, 当 UE发生跨 S-GW的跟踪区更新或跨 S-GW的切换而导致 BBERF 重选时,UE同样先重建在切换前建立的第一个 PDN的连接, BBERF与 PCRF 以及 PCEF与 PCRF交互时不携带会话标识, PCRF将对应于切换前建立的 第一个 PDN连接的规则和事件触发器分别下发给 BBERF和 PCEF; 当 UE 触发重建第二 PDN连接时, BBERF与 PCEF以及 PCEF与 PCRF交互时携 带会话标识, PCRF将对应于切换前建立的第二个 PDN连接的规则和事件触 发器分别下发给 BBERF和 PCEF。 系统实施例 实施例一 根据本发明的实施例, 提供了一种分组数据网络的接入控制系统。 图 8是根据本发明实施例的分组数据网络的接入控制系统的方框图,如 图 8所示, 该接入控制系统包括: BBERF实体 82, 用于发送网关控制会话建立指示消息, 其中, 当 UE 在接入分组数据网络后再次请求接入同一分组数据网络时, BBERF实体在网 关控制会话建立指示消息中携带会话标识,其中,会话标识用于唯一标识 UE 在一个接入点名称的一次接入; 还用于分配会话标识, 发送携带有会话标识 的代理绑定更新请求消息, 以及接收网关控制会话建立确认消息, 从中兹耳又
服务质量规则和事件触发器, 并安装服务质量规则和事件触发器;
PCRF实体 84, 连接至 BBERF实体 82, 用于接收来自 BBERF实体的 网关接收控制会话建立指示消息, 从中获取会话标识, 并根据会话标识判断 UE 再次建立到接入点名称的连接; 还用于接收网络协议连接接入网会话建 立指示消息, 并在网络协议连接接入网会话建立指示消息中携带会话标识, 通过会话标识将网关控制会话建立指示消息和网络协议连接接入网会话建立 指示消息进行关联, 以及基于网关控制会话建立指示消息, 制定策略和计费 控制规则、 月艮务质量规则和相应的事件触发器, 并向 BBERF 实体发送网关 控制会话建立确认消息, 并在网关控制会话建立确认消息中携带服务质量规 则和事件触发器。 图 9 是根据本发明实施例的分组数据网络的接入控制系统的优选结构 的方框图, 如图 9所示, 上述分组数据网络的接入控制系统进一步包括:
PCEF实体 92, 连接至 BBERF实体 82和 PCRF实体 84, 用于接收来 自 BBERF实体的代理绑定更新请求消息, 向 PCRF实体发送网络协议连接 接入网会话建立指示消息, 并在网络协议连接接入网会话建立指示消息中携 带会话标识; 移动管理单元 94, 连接至 BBERF实体 82, 用于分配会话标识, 以及 向 BBERF 实体发送默认 7|载建立请求消息, 并在默认 7|载建立请求消息中 携带会话标识。 实施例二 根据本发明的另一个方面, 提供了一种策略和计费规则功能实体。 图 10是根据本发明实施例的策略和计费规则功能实体的方框图,如图 10所示, 根据本发明实施例的策略和计费规则功能实体包括: 接收模块 102, 用于接收来自承载绑定和事件报告功能实体的网关控制 会话建立指示消息, 其中, 网关控制会话建立指示消息中携带有会话标识, 会话标识用于标识用户设备是再次接入同一个分组数据网络还是承载绑定和 事件报告功能实体重选; 获取模块 104, 连接至接收模块 102, 用于从控制会话建立指示消息中 获取会话标识;
判断模块 106, 连接至获取模块 104, 用于才艮据会话标识判断用户设备 是再次接入分组数据网络还是承载绑定和事件报告功能实体重选。 在以上实施例中, 通过在网关控制会话建立指示消息中携带会话标识, 提供了区分不同 IP-CAN会话的方法, 应用于 3GPP演进的分组系统, 使得 UE接入同一个 APN多次时, PCRF能够判断 UE多次接入同一个 APN , 并 且唯一标只不同的 IP-CAN会话。 显然, 本领域的技术人员应该明白, 上述的本发明的各模块或各步骤可 以用通用的计算装置来实现, 它们可以集中在单个的计算装置上, 或者分布 在多个计算装置所组成的网络上, 可选地, 它们可以用计算装置可执行的程 序代码来实现, 从而, 可以将它们存储在存储装置中由计算装置来执行, 或 者将它们分别制作成各个集成电路模块, 或者将它们中的多个模块或步骤制 作成单个集成电路模块来实现。 这样, 本发明不限制于任何特定的硬件和软 件结合。 以上所述仅为本发明的优选实施例而已, 并不用于限制本发明, 对于本 领域的技术人员来说, 本发明可以有各种更改和变^^ 凡在本发明的 4青申和 原则之内, 所作的任何修改、 等同替换、 改进等, 均应包含在本发明的保护 范围之内。
Claims
1. 一种分组数据网络的接入控制方法, 其特征在于, 包括:
策略和计费规则功能实体接收来自承载绑定和事件报告功能实体 的网关控制会话建立指示消息, 其中, 所述网关控制会话建立指示消息 携带有会话标识, 所述会话标识用于标识用户设备是再次接入同一个分 组数据网络还是承载绑定和事件报告功能实体重选;
所述策略和计费规则功能实体从所述控制会话建立指示消息中获 取所述会话标识, 才艮据所述会话标识判断所述用户设备是再次接入所述 分组数据网络还是承载绑定和事件报告功能实体重选。
2. 根据权利要求 1所述的接入控制方法, 其特征在于, 所述会话标识还用 于唯一标识所述用户设备的一个网络协议连接接入网会话。
3. 才艮据权利要求 2所述的接入控制方法, 其特征在于, 在所述策略和计费 规则功能实体才艮据所述会话标识判断所述用户设备是再次接入所述分组 数据网络还是承载绑定和事件报告功能实体重选之后, 所述方法进一步 包括:
所述承载绑定和事件报告功能实体向策略和计费执行功能实体发 送代理绑定更新请求消息, 并在所述代理绑定更新请求消息中携带所述 会话标识;
所述策略和计费执行功能实体接收所述代理绑定更新请求消息,向 所述策略和计费规则功能实体发送网络协议连接接入网会话建立指示消 息, 并在所述网络协议连接接入网会话建立指示消息中携带所述会话标 识;
所述策略和计费规则功能实体通过所述会话标识将所述网关控制 会话建立指示消息和所述网络协议连接接入网会话建立指示消息进行关 联。
4. 才艮据权利要求 2所述的接入控制方法, 其特征在于, 在所述承载绑定和 事件报告功能实体发送所述网关控制会话建立指示消息之前, 所述方法 进一步包括:
所述承载绑定和事件报告功能实体分配所述会话标识。
5. 4艮据权利要求 2所述的接入控制方法, 其特征在于, 在所述承载绑定和 事件报告功能实体发送所述网关控制会话建立指示消息之前, 所述方法 进一步包括:
移动管理单元分配所述会话标识;
所述移动管理单元向所述承载绑定和事件报告功能实体发送默认 承载建立请求消息, 并在所述默认承载建立请求消息中携带所述会话标 识。
6. 根据权利要求 4或 5所述的接入控制方法, 其特征在于, 将所述会话标 识的信息加入接入点名称, 并将携带有所述会话标识的信息的接入点名 称作为所述会话标识。
7. 根据权利要求 5所述的接入控制方法, 其特征在于, 将默认承载标识作 为所述会话标识。
8. 才艮据权利要求 1所述的接入控制方法, 其特征在于, 在所述策略和计费 规则功能实体才艮据所述会话标识判断所述用户设备是再次接入所述分组 数据网络还是承载绑定和事件报告功能实体重选之后, 所述方法进一步 包括:
基于所述网关控制会话建立指示消息,所述策略和计费规则功能实 体制定策略和计费控制规则、 服务质量规则和相应的事件触发器, 并向 所述承载绑定和事件报告功能实体发送网关控制会话建立确认消息, 并 在所述网关控制会话建立确认消息中携带所述服务质量规则和所述事件 触发器;
所述承载绑定和事件报告功能实体接收所述网关控制会话建立确 认消息, 从中获取所述服务质量规则和所述事件触发器, 并安装所述服 务质量规则和所述事件触发器。
9. 根据权利要求 1至 5中任一项、 7或 8所述的接入控制方法, 其特征在 于,
在所述用户设备初次接入或重建初次接入所述分组数据网络时, 网 关控制会话建立指示消息中不携带所述会话标识。
10. 根据权利要求 1所述的接入控制方法, 其特征在于, 在策略和计费规则 功能实体接收来自承载绑定和事件报告功能实体的网关控制会话建立指
示消息之前还包括:
基于所述用户设备的分组数据网络连接请求消息,承载绑定和事件 报告功能实体向策略和计费规则功能实体发送所述网关控制会话建立指 示消息。
11. 一种分组数据网络的接入控制方法, 其特征在于, 包括:
承载绑定和事件报告功能实体向策略和计费规则功能实体发送网 关控制会话建立指示消息, 其中, 所述网关控制会话建立指示消息携带 有会话标识, 所述会话标识用于唯一标识用户设备的一个网络协议连接 接入网会话; 所述承载绑定和事件报告功能实体向策略和计费执行功能实体发 送代理绑定更新请求消息, 并在所述代理绑定更新请求消息中携带所述 会话标识;
所述策略和计费执行功能实体接收所述代理绑定更新请求消息,向 所述策略和计费规则功能实体发送网络协议连接接入网会话建立指示消 息或网络协议连接接入网会话修改指示消息, 并在所述网络协议连接接 入网会话建立指示消息或所述网络协议连接接入网会话修改指示消息中 携带所述会话标识;
所述策略和计费规则功能实体通过所述会话标识将所述网关控制 会话建立指示消息和所述网络协议连接接入网会话建立指示消息或所述 网络协议连接接入网会话修改指示消息进行关联。
12.一种分组数据网络的接入控制系统, 其特征在于, 包括:
承载绑定和事件报告功能实体,用于发送网关控制会话建立指示消 息, 并在所述网关控制会话建立指示消息中携带会话标识, 其中, 所述 会话标识用于区分所述用户设备为再次接入同一个分组数据网络还是承 载绑定和事件报告功能实体重选, 以及唯一标识所述用户设备的一个网 络协议连接接入网会话;
策略和计费规则功能实体,用于接收来自所述承载绑定和事件报告 功能实体的所述网关控制会话建立指示消息, 从中获取所述会话标识, 并才艮据所述会话标识判断所述用户设备为再次接入所述分组数据网络还 是承载绑定和事件报告功能实体重选。
13. 根据权利要求 12所述的接入控制系统, 其特征在于:
所述承载绑定和事件报告功能实体, 还用于分配所述会话标识。
14. 根据权利要求 12所述的接入控制系统, 其特征在于: 所述承载绑定和事件报告功能实体,还用于发送携带有所述会话标 识的代理绑定更新请求消息, 以及接收网关控制会话建立确认消息, 从 中获取服务质量规则和事件触发器, 并安装所述服务质量规则和所述事 件触发器;
所述策略和计费规则功能实体,还用于接收网络协议连接接入网会 话建立指示消息, 并在所述网络协议连接接入网会话建立指示消息中携 带所述会话标识, 通过所述会话标识将所述网关控制会话建立指示消息 和所述网络协议连接接入网会话建立指示消息进行关联, 以及基于所述 网关控制会话建立指示消息, 制定策略和计费控制规则、 服务质量规则 和相应的事件触发器, 并向所述承载绑定和事件报告功能实体发送所述 网关控制会话建立确认消息, 并在所述网关控制会话建立确认消息中携 带所述服务质量规则和所述事件触发器。
15. 根据权利要求 14所述的接入控制系统, 其特征在于, 进一步包括: 策略和计费执行功能实体,用于接收来自所述承载绑定和事件报告 功能实体的所述代理绑定更新请求消息, 向所述策略和计费规则功能实 体发送所述网络协议连接接入网会话建立指示消息, 并在所述网络协议 连接接入网会话建立指示消息中携带所述会话标识。
16. 根据权利要求 12所述的接入控制系统, 其特征在于, 进一步包括: 移动管理单元, 用于分配所述会话标识, 以及向所述承载绑定和事 件报告功能实体发送默认承载建立请求消息, 并在所述默认承载建立请 求消息中携带所述会话标识。
17. 一种分组数据网络的接入控制系统, 其特征在于, 包括:
承载绑定和事件报告功能实体,用于向策略和计费规则功能实体发 送网关控制会话建立指示消息, 并在所述网关控制会话建立指示消息中 携带会话标识, 其中, 所述会话标识用于唯一标识用户设备的一个网络 协议连接接入网会话;
所述承载绑定和事件报告功能实体还用于向策略和计费执行功能 实体发送代理绑定更新请求消息, 并在所述代理绑定更新请求消息中携 带所述会话标识;
所述策略和计费执行功能实体,用于接收所述代理绑定更新请求消 息, 并向所述策略和计费规则功能实体发送网络协议连接接入网会话建 立指示消息或网络协议连接接入网会话修改指示消息, 并在所述网络协 议连接接入网会话建立指示消息或所述网络协议连接接入网会话修改指 示消息中携带所述会话标识;
所述策略和计费规则功能实体,用于接收来自所述承载绑定和事件 报告功能实体的所述网关控制会话建立指示消息和所述策略和计费执行 功能实体的网络协议连接接入网会话建立指示消息或网络协议连接接入 网会话修改指示消息, 并才艮据所述会话标识将网关控制会话建立指示消 息和所述网络协议连接接入网会话建立指示消息或所述网络协议连接接 入网会话修改指示消息进行关联。
18. 一种策略和计费规则功能实体, 其特征在于, 包括:
接收模块,用于接收来自承载绑定和事件报告功能实体的网关控制 会话建立指示消息, 其中, 所述网关控制会话建立指示消息中携带有会 话标识, 所述会话标识用于标识用户设备是再次接入同一个分组数据网 络还是承载绑定和事件报告功能实体重选;
获取模块, 用于从所述控制会话建立指示消息中获取所述会话标 识;
判断模块,用于根据所述会话标识判断所述用户设备是再次接入所 述分组数据网络还是承载绑定和事件报告功能实体重选。
19. 一种策略和计费规则功能实体, 其特征在于, 包括:
接收模块,用于接收来自承载绑定和事件报告功能实体的网关控制 会话建立指示消息和策略计费执行功能实体的网络协议连接接入网会话 建立指示消息或网络协议连接接入网会话修改指示消息, 其中, 所述网 关控制会话建立指示消息、所述网络协议连接接入网会话建立指示消息、 所述网络协议连接接入网会话修改指示消息中携带有会话标识, 其中, 所述会话标识用于唯一标识用户设备的一个网络协议连接接入网会话;
获耳 JUf莫块,用于从所述网关控制会话建立指示消息和所述网络协议 连接接入网会话建立指示消息或所述网络协议连接接入网会话修改指示 消息中获取所述会话标识;
关联模块,用于根据所述会话标识将网关控制会话建立指示消息和 网络协议连接接入网会话建立指示消息或网络协议连接接入网会话修改 指示消息进行关联。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP09761267A EP2290883A4 (en) | 2008-06-11 | 2009-06-03 | METHOD AND SYSTEM FOR ACCESS CONTROL FOR PACKET DATA NETWORK, PCRF ENTITY |
US12/997,509 US8621555B2 (en) | 2008-06-11 | 2009-06-03 | Access control method and system for packet data network, PCRF entity |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200810100442.8 | 2008-06-11 | ||
CN2008101004428A CN101286915B (zh) | 2008-06-11 | 2008-06-11 | 分组数据网络的接入控制方法和系统、pcrf实体 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2009149642A1 true WO2009149642A1 (zh) | 2009-12-17 |
Family
ID=40058893
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2009/072109 WO2009149642A1 (zh) | 2008-06-11 | 2009-06-03 | 分组数据网络的接入控制方法和系统、pcrf实体 |
Country Status (4)
Country | Link |
---|---|
US (1) | US8621555B2 (zh) |
EP (1) | EP2290883A4 (zh) |
CN (1) | CN101286915B (zh) |
WO (1) | WO2009149642A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110182206A1 (en) * | 2010-01-25 | 2011-07-28 | Qualcomm Incorporated | Apparatus and method for associating a gateway control session with an internet protocol connectivity access network (ip-can) session |
Families Citing this family (45)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101286915B (zh) | 2008-06-11 | 2012-05-09 | 中兴通讯股份有限公司 | 分组数据网络的接入控制方法和系统、pcrf实体 |
CN101742009B (zh) * | 2008-11-07 | 2012-06-27 | 华为技术有限公司 | 一种会话关联的方法、系统及装置 |
US8325638B2 (en) * | 2008-12-09 | 2012-12-04 | Qualcomm Incorporated | Performing packet flow optimization with policy and charging control |
KR101384697B1 (ko) * | 2009-02-03 | 2014-04-14 | 노키아 솔루션스 앤드 네트웍스 오와이 | 통신 접속을 제공하기 위한 방법 및 통신 엔티티 |
CN101841798B (zh) * | 2009-03-20 | 2014-01-01 | 中兴通讯股份有限公司 | 计费标识的关联方法和装置 |
CN101860865A (zh) * | 2009-04-10 | 2010-10-13 | 中兴通讯股份有限公司 | 二次接入实现方法和装置 |
CN101931928B (zh) * | 2009-06-19 | 2014-08-13 | 中兴通讯股份有限公司 | 漫游场景下单apn多pdn连接的策略计费控制的方法及系统 |
CN101959257B (zh) * | 2009-07-20 | 2013-06-12 | 中兴通讯股份有限公司 | 一种承载绑定和事件报告功能的重选方法 |
CN101969673B (zh) | 2009-07-27 | 2013-08-07 | 中兴通讯股份有限公司 | 一种承载绑定和事件报告功能的重选方法 |
CN101969632B (zh) * | 2009-07-28 | 2013-06-05 | 中兴通讯股份有限公司 | 一种漫游场景下的策略计费控制实现方法 |
ES2545502T3 (es) | 2009-09-18 | 2015-09-11 | Nec Corporation | Sistema de comunicaciones y método de control de comunicaciones |
CN101800987B (zh) * | 2010-02-10 | 2014-04-09 | 中兴通讯股份有限公司 | 一种智能卡鉴权装置及方法 |
US20120014352A1 (en) * | 2010-07-13 | 2012-01-19 | Qualcomm Incorporated | Apparatus and method for enforcement of multiple packet data network (pdn) connections to the same access point name (apn) |
EP2676462B1 (en) * | 2011-02-17 | 2014-12-31 | Telefonaktiebolaget LM Ericsson (PUBL) | Method and apparatus for establishing a pdn connection |
EP2538721A1 (en) * | 2011-06-22 | 2012-12-26 | Alcatel Lucent | Support of IP connections over trusted non-3GPP access |
US8601134B1 (en) * | 2011-06-30 | 2013-12-03 | Amazon Technologies, Inc. | Remote storage gateway management using gateway-initiated connections |
US8789208B1 (en) | 2011-10-04 | 2014-07-22 | Amazon Technologies, Inc. | Methods and apparatus for controlling snapshot exports |
ES2883576T3 (es) * | 2012-01-06 | 2021-12-09 | Alcatel Lucent | Reducir la carga debido al reporte de cambios de información a un controlador de política y/o carga en un sistema de comunicación móvil |
CN103517378B (zh) * | 2012-06-30 | 2018-09-21 | 华为终端有限公司 | 分组数据网连接建立方法和设备 |
EP2876965B1 (en) | 2012-07-18 | 2023-09-06 | Huawei Technologies Co., Ltd. | Data connection management method, device and system |
CN103686846B (zh) * | 2012-09-07 | 2019-04-05 | 中兴通讯股份有限公司 | 数据报文传输方法、pdn连接标识处理方法、及装置 |
US11102689B2 (en) | 2013-01-03 | 2021-08-24 | Apple Inc. | Packet data connections in a wireless communication system using a wireless local area network |
WO2014117865A1 (en) * | 2013-02-01 | 2014-08-07 | Telefonaktiebolaget L M Ericsson (Publ) | Mobile gateway selection using a direct connection between a pcrf node and a mobility management node |
ES2941246T3 (es) * | 2013-04-29 | 2023-05-19 | Alcatel Lucent | QoS de extremo a extremo cuando se integran redes de acceso distintas de 3GPP de confianza y redes principales de 3GPP |
EP2975880B1 (en) * | 2013-06-20 | 2019-08-21 | Samsung Electronics Co., Ltd. | Method and device for controlling multiple connections in wireless lan |
US9521077B2 (en) * | 2013-07-22 | 2016-12-13 | Verizon Patent And Licensing Inc. | Network connection via a proxy device using a generic access point name |
WO2014173252A1 (zh) * | 2013-07-26 | 2014-10-30 | 中兴通讯股份有限公司 | 会话管理方法、应用功能实体、策略服务器和协议转换器 |
JP5681772B1 (ja) * | 2013-09-24 | 2015-03-11 | 株式会社Nttドコモ | Ipマルチメディアサブシステム、プロキシセッション制御装置及び通信制御方法 |
US9515938B2 (en) | 2013-10-24 | 2016-12-06 | Microsoft Technology Licensing, Llc | Service policies for communication sessions |
WO2015120902A1 (en) * | 2014-02-14 | 2015-08-20 | Telefonaktiebolaget L M Ericsson (Publ) | Pcrf assisted apn selection |
JP6441951B2 (ja) * | 2014-02-19 | 2018-12-19 | コンヴィーダ ワイヤレス, エルエルシー | システム間モビリティのためのサービングゲートウェイ拡張 |
RU2682856C1 (ru) * | 2015-04-03 | 2019-03-21 | Хуавэй Текнолоджиз Ко., Лтд. | Способ доступа в сети беспроводной связи, соответствующие устройство и система |
US9961112B2 (en) * | 2015-04-20 | 2018-05-01 | Bomgar Corporation | Method and apparatus for enforcing realtime access controls for endpoints |
US10397233B2 (en) | 2015-04-20 | 2019-08-27 | Bomgar Corporation | Method and apparatus for credential handling |
US10229262B2 (en) | 2015-04-20 | 2019-03-12 | Bomgar Corporation | Systems, methods, and apparatuses for credential handling |
CN107113612B (zh) * | 2015-04-22 | 2020-06-26 | 华为技术有限公司 | 接入点名称授权的方法、装置及系统 |
US10498764B2 (en) * | 2015-12-08 | 2019-12-03 | Jpu.Io Ltd | Network routing and security within a mobile radio network |
EP3485608B1 (en) * | 2016-07-13 | 2020-06-24 | Telefonaktiebolaget LM Ericsson (PUBL) | Methods and servers for managing traffic steering policies |
CN108307530B (zh) * | 2016-09-30 | 2023-09-22 | 华为技术有限公司 | 一种会话连接建立方法、相关设备及系统 |
CN113194515A (zh) * | 2017-05-05 | 2021-07-30 | 华为技术有限公司 | 一种会话管理方法、网络设备和通信系统 |
US20200305211A1 (en) * | 2017-12-04 | 2020-09-24 | Telefonaktiebolaget Lm Ericsson (Publ) | System and methods for ims session continuity across 4g and 5g networks |
WO2019127038A1 (zh) * | 2017-12-26 | 2019-07-04 | Oppo广东移动通信有限公司 | 用于数据传输的方法、终端设备和网络设备 |
WO2019136265A2 (en) | 2018-01-08 | 2019-07-11 | Ppc Broadband, Inc. | Multi-tap having selectable conditioning modules |
CN110972216B (zh) * | 2018-09-30 | 2022-04-29 | 华为技术有限公司 | 通信方法和装置 |
CN111756592B (zh) * | 2019-03-28 | 2022-03-08 | 中国移动通信有限公司研究院 | 一种策略处理方法及实体 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2007026268A1 (en) * | 2005-08-31 | 2007-03-08 | Nokia Corporation | Inter-access mobility and service control |
CN101119211A (zh) * | 2007-09-18 | 2008-02-06 | 中兴通讯股份有限公司 | 一种公平用户策略的业务实现方法 |
CN101159563A (zh) * | 2007-11-02 | 2008-04-09 | 中兴通讯股份有限公司 | 一种策略计费控制服务器的选择方法及系统 |
CN101286915A (zh) * | 2008-06-11 | 2008-10-15 | 中兴通讯股份有限公司 | 分组数据网络的接入控制方法和系统、pcrf实体 |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1310476C (zh) * | 2004-07-05 | 2007-04-11 | 华为技术有限公司 | 无线局域网用户建立会话连接的方法 |
US8064400B2 (en) * | 2005-07-20 | 2011-11-22 | Interdigital Technology Corporation | Method and system for supporting an evolved UTRAN |
US8042148B2 (en) * | 2006-02-07 | 2011-10-18 | Cisco Technology, Inc. | System and method for enforcing policy in a communication network |
US8856860B2 (en) * | 2006-08-18 | 2014-10-07 | Cisco Technology, Inc. | System and method for implementing policy server based application interaction manager |
WO2008127662A1 (en) * | 2007-04-12 | 2008-10-23 | Marvell World Trade Ltd. | Packet data network connectivity domain selection and bearer setup |
US8331314B2 (en) * | 2007-04-20 | 2012-12-11 | Telefonaktiebolaget L M Ericsson (Publ) | Dormant session management associated with handover |
EP2163068B1 (en) * | 2007-05-22 | 2016-02-03 | Telefonaktiebolaget LM Ericsson (publ) | Method, apparatuses and computer program for dynamically configuring a proxy call session control function of the ip multimedia subsystem from a policy control rules server |
WO2008154236A1 (en) * | 2007-06-08 | 2008-12-18 | Interdigital Technology Corporation | Method and apparatus for providing capability and core network information to support interworking between 3gpp and non-3gpp networks |
US8116728B2 (en) * | 2008-04-22 | 2012-02-14 | Alcatel Lucent | Charging in LTE/EPC communication networks |
US20090300207A1 (en) * | 2008-06-02 | 2009-12-03 | Qualcomm Incorporated | Pcc enhancements for ciphering support |
US8249551B2 (en) * | 2008-06-05 | 2012-08-21 | Bridgewater Systems Corp. | Long-term evolution (LTE) policy control and charging rules function (PCRF) selection |
KR101413675B1 (ko) * | 2009-06-03 | 2014-07-01 | 블랙베리 리미티드 | 진화형 패킷 시스템에서의 음성 서비스 |
-
2008
- 2008-06-11 CN CN2008101004428A patent/CN101286915B/zh active Active
-
2009
- 2009-06-03 US US12/997,509 patent/US8621555B2/en active Active
- 2009-06-03 EP EP09761267A patent/EP2290883A4/en not_active Withdrawn
- 2009-06-03 WO PCT/CN2009/072109 patent/WO2009149642A1/zh active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2007026268A1 (en) * | 2005-08-31 | 2007-03-08 | Nokia Corporation | Inter-access mobility and service control |
CN101119211A (zh) * | 2007-09-18 | 2008-02-06 | 中兴通讯股份有限公司 | 一种公平用户策略的业务实现方法 |
CN101159563A (zh) * | 2007-11-02 | 2008-04-09 | 中兴通讯股份有限公司 | 一种策略计费控制服务器的选择方法及系统 |
CN101286915A (zh) * | 2008-06-11 | 2008-10-15 | 中兴通讯股份有限公司 | 分组数据网络的接入控制方法和系统、pcrf实体 |
Non-Patent Citations (1)
Title |
---|
See also references of EP2290883A4 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110182206A1 (en) * | 2010-01-25 | 2011-07-28 | Qualcomm Incorporated | Apparatus and method for associating a gateway control session with an internet protocol connectivity access network (ip-can) session |
WO2011091445A1 (en) * | 2010-01-25 | 2011-07-28 | Qualcomm Incorporated | Apparatus and method for associating a gateway control session with an internet protocol connectivity access network (ip-can) session |
Also Published As
Publication number | Publication date |
---|---|
US20110099604A1 (en) | 2011-04-28 |
EP2290883A4 (en) | 2012-08-08 |
CN101286915A (zh) | 2008-10-15 |
US8621555B2 (en) | 2013-12-31 |
EP2290883A1 (en) | 2011-03-02 |
CN101286915B (zh) | 2012-05-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2009149642A1 (zh) | 分组数据网络的接入控制方法和系统、pcrf实体 | |
US8799440B2 (en) | Policy and charging control method and system for multi-PDN connections of single APN | |
US9351325B2 (en) | Policy control method and system for converged network | |
US9137652B2 (en) | Method for implementing policy and charging control in a roaming scene | |
WO2009086734A1 (zh) | 非漫游场景下策略和计费规则功能实体的选择方法 | |
WO2009094837A1 (en) | A method for selecting a policy and charging rules function server on a non-roaming scene | |
WO2010121511A1 (zh) | 多网接入控制方法、通讯系统以及相关设备 | |
WO2009135362A1 (zh) | 一种隐藏拜访地网络拓扑结构的策略计费控制的方法 | |
WO2011011943A1 (zh) | 一种承载绑定和事件报告功能的重选方法 | |
WO2011009257A1 (zh) | 一种承载绑定和事件报告功能的重选系统及方法 | |
WO2009124436A1 (zh) | 一种承载绑定和事件报告功能策略控制的方法及系统 | |
WO2010006491A1 (zh) | 一种事件触发器的下发和安装方法 | |
WO2010081329A1 (zh) | 业务流迁移过程中对网络资源进行控制的方法和系统 | |
WO2013189217A1 (zh) | 分组网关标识信息的更新方法、aaa服务器和分组网关 | |
WO2012006909A1 (zh) | 一种上报固网接入信息的方法及系统 | |
WO2011006317A1 (zh) | 删除家乡策略和计费规则功能冗余信息的方法及系统 | |
EP2557729A1 (en) | Method and system for information transmission | |
WO2010034195A1 (zh) | 用户设备ip地址提供方法、diameter 路由代理 | |
WO2011029289A1 (zh) | 漫游场景下承载控制模式的发送方法和系统 | |
WO2011134327A1 (zh) | 确定策略和计费规则功能的方法及系统 | |
WO2009111983A1 (zh) | 一种寻呼用户的方法、无线接入设备及终端 | |
WO2008154874A1 (fr) | Procédé et système permettant d'établir un tunnel dans le réseau en évolution | |
WO2010078761A1 (zh) | 基于多接入技术的策略计费控制方法、装置和系统 | |
CN101841798B (zh) | 计费标识的关联方法和装置 | |
WO2011018020A1 (zh) | 控制pcrf负载均衡的方法、系统及重定向dra |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 09761267 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 12997509 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2009761267 Country of ref document: EP |