WO2011095025A1 - 一种对移动用户本地接入的策略控制方法和系统 - Google Patents

一种对移动用户本地接入的策略控制方法和系统 Download PDF

Info

Publication number
WO2011095025A1
WO2011095025A1 PCT/CN2010/078824 CN2010078824W WO2011095025A1 WO 2011095025 A1 WO2011095025 A1 WO 2011095025A1 CN 2010078824 W CN2010078824 W CN 2010078824W WO 2011095025 A1 WO2011095025 A1 WO 2011095025A1
Authority
WO
WIPO (PCT)
Prior art keywords
policy
entity
network
mobile
fixed network
Prior art date
Application number
PCT/CN2010/078824
Other languages
English (en)
French (fr)
Inventor
芮通
孙默
周娜
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2011095025A1 publication Critical patent/WO2011095025A1/zh

Links

Classifications

    • 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
    • H04L47/82—Miscellaneous aspects
    • H04L47/824—Applicable to portable or mobile terminals
    • 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
    • H04L47/80—Actions related to the user profile or the type of traffic
    • H04L47/805—QOS or priority aware
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access

Definitions

  • the present invention relates to access technologies in the field of mobile communications, and in particular, to a policy control method and system for local access of mobile users. Background technique
  • EPS 3rd Generation Partnership Project
  • Evolved Packet System Evolved Packet System
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • MME Mobile Management Unit
  • S-GW Serving Gateway
  • P-GW Packet Data Network Gateway
  • HSS Home Subscriber Server
  • AAA Authentication, Authorization and Accounting
  • PCRF Policy and Charging Rules Function
  • the existing EPS system architecture is shown in Figure 1.
  • the MME is responsible for the operation of the control plane such as mobility management, non-access stratum signaling processing, and user mobility management context management.
  • the S-GW is connected to the E-UTRAN.
  • the access gateway device forwards data between the E-UTRAN and the P-GW, and is responsible for buffering the paging waiting data;
  • the P-GW is a border gateway of the EPS and the Packet Data Network (PDN), which is responsible for PDN access and forwarding data between EPS and PDN;
  • PDN Packet Data Network
  • S-GW and P-GW are both core network gateways;
  • PCRF is connected to the service network protocol (IP, Internet Protocol) service network through the receiving interface Rx to obtain service information.
  • IP Internet Protocol
  • the PCRF is connected to the gateway device in the network through the Gx/Gxa/Gxc interface, and is responsible for initiating the establishment of the IP bearer, guaranteeing the quality of service (QoS, Quality of Service) of the service data, and performing the calculation. Fee control.
  • QoS Quality of Service
  • 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.
  • the non-3GPP IP access network is divided into a trusted non-3GPP IP access network and an untrusted non-3GPP IP access network.
  • the trusted non-3GPP IP access network can be directly connected to the P-GW through the S2a interface; the untrusted non-3GPP IP access network needs to be connected to the P-GW through an evolved packet data gateway (ePDG, evolved Packet Data Gateway), ePDG and
  • ePDG evolved Packet Data Gateway
  • the interface between the P-GWs is S2b.
  • the S2c provides user plane related control and mobility support between the user equipment (UE, User Equipment) and the P-GW.
  • the supported mobility management protocol is to support dual stack mobility.
  • IPv6 DSMIPv6, Mobile IPv6 Support for Dual Stack Hosts and Routers.
  • the Policy and Charging Enforcement Function exists in the P-GW, and the PCRF and the P-GW exchange information through the Gx interface.
  • the interface between the P-GW and the S-GW is based on Proxy Mobile IPv6 (PMIPv6)
  • the S-GW also has a bearer binding and event reporting function (BBERF, Bearer Binding and Event Report Function).
  • BBERF Bearer Binding and Event Report Function
  • QoS control is performed, and information is exchanged between the S-GW and the PCRF through the Gxc interface.
  • 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.
  • the S9 interface functions as an interface between the home PCRF and the visited PCRF, and provides an application function (AF, Application Function) for the UE, and sends a policy and charging control (PCC) to the PCRF through the Rx interface.
  • Policy and Charging Control The business information of the policy.
  • the corresponding PDN network can be found by the access point name (APN, Access Point Name).
  • a connection from a UE to a PDN network is usually referred to as an IP-Connected Access Network (IP-CAN) session.
  • IP-CAN IP-Connected Access Network
  • Diameter is established between BBERF and PCEF and PCRF respectively. Sessions, through these Diameter sessions, transmit policy charging information for controlling the IP-CAN session, information for formulating policies, and the like.
  • the home base station is a small, low-power base station deployed in indoor places such as homes and offices.
  • the main purpose is to provide users with higher service rates and lower the cost of using high-speed services, while making up for existing distributed Insufficient coverage of cellular wireless communication systems.
  • the home base station is a wireless side network element.
  • the home base station can be directly connected to the core network, as shown in Figure 2a.
  • the home network base station gateway can also be connected to the core network, as shown in Figure 2b.
  • the main functions of the home base station gateway are: Security, handling the registration of the home base station, performing operation and maintenance management on the home base station, configuring and controlling the home base station according to the operator's requirements, and exchanging data of the core network and the home base station, and the like.
  • mobile communication systems can also support local IP access functions, which can be achieved under the condition that the wireless side network element has local IP access capability and the user subscribes to allow local IP access.
  • local IP access functions can be achieved under the condition that the wireless side network element has local IP access capability and the user subscribes to allow local IP access.
  • the local access of the terminal to other IP devices or the Internet of the home network.
  • the implementation of local IP access can use multiple connection establishment methods: You can establish a connection to achieve core network access and local IP access at the same time. As shown in Figure 2a and Figure 2b, there is no need for the wireless side network element or The function of the local gateway is added to the home base station gateway. The local gateway can also be provided with strong support for the local IP access technology. The local gateway can be combined with the wireless side network element, as shown in Figure 3a. When there is a home base station gateway, the local gateway can be combined not only with the home base station but also with the home base station gateway, as shown in FIG. 3b.
  • the local gateway may be a local SGW (L-SGW, Local SGW) and a local PGW (L-PGW, Local PGW), and may be a separate L-PGW.
  • the home base station gateway can be combined with the home base station.
  • the core network gateway may be a Serving GPRS Support Node (SGSN), a Gateway GPRS Support Node (GGSN, Gateway GPRS). Support Node ) tart The local gateway can be a local GGSN (L-GGSN, Local GGSN) and a local SGSN (L-SGSN, Local SGSN), which can be a separate L-GGSN.
  • FIG. 4a shows the data flow of the local IP access and the core network connection in the wireless communication system of FIG. 2a, wherein the traffic of the local IP access is Connect to the fixed network through the fixed network access device, as shown in Figure 5a.
  • Figure 4b shows the data flow of the local IP access and the core network connection in the wireless communication system of Figure 3a, wherein the traffic of the local IP access is accessed to the fixed network through the fixed network access device, as shown in Figure 5b.
  • LTE Long Term Evolution
  • An access technology similar to the local IP access is a Femtocell.
  • the mobile operator deploys such a large number of home base stations to solve the problem of insufficient coverage.
  • ADSL asymmetric digital subscriber loop
  • Asymmetric Digital Subscriber Line Asymmetric Digital Subscriber Line
  • LAN Local Area Network
  • the user's service data flows through the home base station into the fixed network transmission node, such as an access network (AN, Access Network), a broadband remote access server (BRAS, Broadband Remote Access Server), and a broadband network.
  • the gateway BNG, Broadband Network Gateway
  • WIFI Wireless Fidelity
  • TISPAN Resource Admission Control Subsystem
  • NGN Next Generation Network
  • TISPAN divides the NGN architecture into a service layer and a transport layer.
  • RACS and N Attachment Subsystem are introduced.
  • the RACS solves the QoS problem of the NGN bearer network, while the NASS is responsible for providing independent services to the upper layer.
  • User access management The main functions of the TISPAN RACS are similar to the Resource and Admission Control Functions (RACF) of the International Telecommunication Union Telecommunications Standardization Sector (ITU-T).
  • RACF Resource and Admission Control Functions
  • ITU-T International Telecommunication Union Telecommunications Standardization Sector
  • the functional architecture of the TISPAN RACS as shown in Figure 6, the RACS associates the resource requirements of the service layer with the resource allocation of the transport layer, mainly completing policy control, resource reservation, admission control, and network address translation (NAT). Crossing and other functions.
  • the RACS provides the transport layer control service for the service layer through a series of QoS policies, so that the user equipment (UE, User Equipment) can obtain the required service quality assurance.
  • UE User Equipment
  • RACS consists of two entities: a business-based policy decision function entity (SPDF,
  • A-RACF Service-based Policy Decision Function and Access-Resource and Admission Control Function
  • the SPDF provides a unified interface to the application layer, shields the underlying network topology and specific access types, and provides service-based policy control; SPDF selects a local policy according to the request of the application function entity (AF, Application Function), and requests It is mapped to IP QoS parameters and sent to A-RACF and Border Gateway Function (BGF) to control the corresponding resources.
  • the A-RACF is located in the access network and has the functions of admission control and network policy aggregation. The request is received from the SPDF, and then the admission control is implemented based on the saved policy, accepting or rejecting the request for the transmission resource; the A-RACF is accessed through the e4 interface.
  • NASS obtains network attachment information and user subscription information, so that it can be determined according to network location information (such as the address of the physical node of the access user). Network resources, while referring to user subscription information when processing resource allocation requests.
  • the transport layer contains three functional entities: access node, BGF, and Resource Control Enforcement Function (RCEF).
  • BGF is a packet-to-packet gateway, which can be located between the access network and the core network (implementing the core border gateway function), or between the two core networks (implementing the interconnection border gateway function).
  • BGF performs NAT traversal, gating, QoS marking, bandwidth limitation, usage measurement, and resource synchronization under the control of SPDF.
  • the RCEF implements the Layer 2/Layer 3 (L2/L3) media stream policy defined by the access operator through the Re-interface to complete the functions of gating, QoS marking, and bandwidth limitation.
  • L2/L3 Layer 2/Layer 3
  • ITU-T is the telecommunications division of the International Telecommunication Union (ITU), which sets standards for resource admission control.
  • ITU International Telecommunication Union
  • RACF consists of two parts, namely, Policy Decision Functional Entity (PD-FE) and Transmission Resource Control.
  • PD-FE Policy Decision Functional Entity
  • TRC-FE Transport Resource Control Functional Entity
  • the TRC-FE interacts with the transmission function through the Rc, and interacts with the Transport Resource Enforcement Functional Entity (TRE-FE) through the Rn;
  • TRE-FE Transport Resource Enforcement Functional Entity
  • the PD-FE interacts with the TRC-FE through the Rt, and through the Rh and the customer premises network.
  • CPN Policy Enforcement Functional Entity
  • SCF Service Control Functions
  • NACF Network Attachment Control Functions
  • the PD-FE is independent of the transmission technology and has nothing to do with the SCF.
  • the PD-FE is based on the network policy rules, the service information provided by the SCF, the transport layer subscription information provided by the NACF, and the resource availability decision result provided by the TRC-FE. The final decision on resource acceptance control.
  • TRC-FE is not related to the business, but is related to transmission technology. TRC-FE is responsible for collecting and maintaining transmission After receiving the resource request from the PD-FE, the TRC-FE performs resource-based admission control based on the QoS, priority requirements, resource availability information, and transmission-related policy rules.
  • the transport layer consists of PE-FE and TRE-FE.
  • the PE-FE implements the policy rule delivered by the PD-FE.
  • the PE-FE is a packet-to-packet gateway. It can be located between the CPN and the access network, between the access network and the core network, or between different carrier networks. Dynamic QoS control, port address translation control, and key nodes for NAT traversal.
  • the TRE-FE implements the transmission resource policy rule delivered by the TRC-FE.
  • the Broadband Forum (BBF, Broadband Forum) proposed the centralized function of the broadband policy control architecture (BPCF, Centralized Deployment Functional Architecture), which is shown in Figure 8.
  • BPCF Centralized Deployment Functional Architecture
  • the corresponding policy is formulated;
  • the Policy Enforcement Point (PEP) is executed according to the corresponding policy formulated by the PDP;
  • the AAA stores the user subscription information;
  • the AF formulates the policy for the PDP and provides corresponding service information.
  • the main object of the present invention is to provide a policy control method and system for local access of mobile users to implement dynamic QoS control of traffic of data flows accessed by mobile users for local IP.
  • the present invention provides a policy control method for local access of mobile users, the method comprising: a policy decision entity of a mobile network formulating a policy for an IP connection access network (IP-CAN) session, a policy enforcement entity for the mobile network and a policy decision entity for the fixed network;
  • IP-CAN IP connection access network
  • the policy decision entity of the fixed network sends the received policy to the policy enforcement entity of the fixed network; the policy enforcement entity of the mobile network and the policy enforcement entity of the fixed network install and execute the received policy.
  • the method further includes:
  • the policy decision entity of the fixed network After receiving the policy, the policy decision entity of the fixed network saves the policy, and maps and/or adjusts the saved policy;
  • the fixed network policy decision entity sends the mapped and/or adjusted policy to the fixed network policy enforcement entity.
  • the method further includes:
  • the policy decision entity of the mobile network when the policy decision entity of the mobile network is triggered internally or externally, and needs to update the formulated policy, the policy decision entity of the mobile network; the policy decision of the fixed network The entity forwards the updated policy to the policy enforcement entity of the fixed network; the policy enforcement entity of the mobile network and the policy enforcement entity of the fixed network install and execute the updated policy.
  • the method further includes:
  • the policy decision entity of the mobile network notifies the policy enforcement entity of the mobile network and the policy decision entity of the fixed network to delete the policy associated with the IP-CAN session;
  • the policy enforcement entity of the mobile network and the policy decision entity of the fixed network respectively perform policy deletion, and the policy decision entity of the fixed network notifies the policy enforcement entity of the fixed network to delete the policy related to the IP-CAN session;
  • the policy enforcement entity of the fixed network performs policy deletion.
  • the policy decision entity of the fixed network is: a resource admission control subsystem (RACS), a resource admission control function entity (RACF), or a policy decision point (PDP).
  • RACS resource admission control subsystem
  • RACF resource admission control function entity
  • PDP policy decision point
  • the policy enforcement entity of the fixed network is: a Resource Control Execution Function Entity (RCEF), a Policy Execution Function Entity (PE-FE), or a Policy Execution Point (PEP).
  • RCEF Resource Control Execution Function Entity
  • PE-FE Policy Execution Function Entity
  • PEP Policy Execution Point
  • the policy enforcement entity of the mobile network includes at least one of: a wireless side network element, a local gateway (L-GW), and a home base station gateway.
  • the wireless side network element includes at least one of the following: a base station, a home base station, and a radio network controller;
  • the policy enforcement entity of the mobile network includes at least one of the following: a policy and a charging enforcement function entity (PCEF) and Bearer Binding and Event Reporting Functional Entity (BBERF).
  • PCEF policy and a charging enforcement function entity
  • BBERF Bearer Binding and Event Reporting Functional Entity
  • the policy is a quality of service (QoS) policy and/or a charging policy.
  • QoS quality of service
  • the present invention also provides a policy control system for local access of mobile users, the system comprising: a policy decision entity of a mobile network, a policy enforcement entity of a mobile network, a policy decision entity of a fixed network, and a policy enforcement entity of a fixed network, among them,
  • a policy decision entity of the mobile network configured to formulate a policy for an IP-CAN session, and use a policy enforcement entity of the mobile network to install and execute the received policy; the fixed network policy decision entity, a policy enforcement entity for transmitting the received policy to the fixed network;
  • the fixed network policy enforcement entity is configured to install and execute the received policy.
  • the policy decision entity of the fixed network is further configured to: after receiving the policy, save the policy, map and/or adjust the saved policy, and then send the mapped and/or the adjusted policy to the solid The policy enforcement entity of the network.
  • the policy decision entity of the mobile network is further configured to: when the IP-CAN session, the policy decision entity of the mobile network is triggered internally or externally, and needs a policy decision entity for the formulated network;
  • the policy decision entity of the fixed network is further configured to forward the updated policy to a policy enforcement entity of the fixed network;
  • the policy enforcement entity of the mobile network and the policy enforcement entity of the fixed network are further used to install and execute the updated policy.
  • the policy decision entity of the mobile network is further configured to: when the IP-CAN session ends, notify a policy enforcement entity of the mobile network and a policy decision entity of the fixed network to delete a policy related to the IP-CAN session;
  • the policy decision entity of the fixed network is further configured to perform policy deletion, and notify the policy enforcement entity of the fixed network to delete a policy related to the IP-CAN session;
  • the policy enforcement entity of the mobile network and the policy enforcement entity of the fixed network are further configured to perform policy deletion separately.
  • the policy decision entity of the fixed network is: RACS, RACF or PDP.
  • the policy enforcement entity of the fixed network is: RCEF, PE-FE or PEP.
  • the policy enforcement entity of the mobile network includes at least one of: a wireless side network element, an L-GW, and a home base station gateway; wherein the wireless side network element And including at least one of: a base station, a home base station, and a radio network controller; if the mobile user is a local access based on a Femtocell or a WIFI connection, the policy enforcement entity of the mobile network includes at least one of the following: PCEF and BBERF .
  • the invention provides a policy control method and system for local access of mobile users.
  • the policy decision entity of the mobile network is a locally accessed IP-CAN.
  • the policy decision entity of the network; the policy decision entity of the fixed network forwards the received policy to the policy enforcement entity of the fixed network; the policy enforcement entity of the mobile network and the policy enforcement entity of the fixed network install and execute the received policy.
  • the invention realizes dynamic QoS control on the traffic of the data flow of the mobile user's local IP access, and avoids the situation that when the mobile network and the fixed network belong to different operators, the traffic cannot be accurately controlled, and the data is made. The transmission quality of the stream is guaranteed.
  • FIG. 1 is a schematic diagram of a system architecture of an EPS in the prior art
  • 2a is a schematic diagram 1 of a connection of a mobile communication network in the prior art
  • 2b is a schematic diagram 2 of a connection of a mobile communication network in the prior art
  • FIG. 3a is a schematic diagram 3 of a connection of a mobile communication network in the prior art
  • FIG. 3b is a schematic diagram 4 of a connection of a mobile communication network in the prior art
  • FIG. 4a is a schematic diagram 1 of a local IP access data flow of a mobile communication system in the prior art
  • FIG. 4b is a schematic diagram 2 of a local IP access data flow of a mobile communication system in the prior art
  • FIG. 5a is a local IP connection of a mobile communication system in the prior art
  • Schematic diagram 1 of the data stream of the fixed network transmission device
  • FIG. 5b is a schematic diagram 2 of a data flow of a local IP access fixed network transmission device in a mobile communication system in the prior art
  • 5c is a schematic diagram 3 of a data flow of a local IP access fixed network transmission device of a mobile communication system in the prior art
  • FIG. 6 is a schematic diagram of a TISPAN RACS resource control architecture in the prior art
  • FIG. 7 is a schematic diagram of an ITU-T RACF resource control architecture in the prior art
  • FIG. 8 is a schematic diagram of a BPCF resource control architecture in the prior art
  • Figure 9a is a schematic diagram 1 of a local access connection in the present invention.
  • Figure 9b is a second schematic diagram of a local access connection in the present invention.
  • Figure 9c is a third schematic diagram of a local access connection in the present invention.
  • 10a is a flowchart of a policy control method according to Embodiment 1 of the present invention.
  • 10b is a flowchart of a policy control method according to Embodiment 2 of the present invention.
  • 11a is a flowchart of a policy control method according to Embodiment 3 of the present invention.
  • FIG. 1 is a flowchart of a policy control method according to Embodiment 4 of the present invention.
  • FIG. 12b is a flowchart of a method for controlling a policy according to Embodiment 6 of the present invention. detailed description
  • the present invention provides a policy control method for local access of mobile users, and the core idea is as follows: When the mobile user accesses the local network, the mobile network The policy decision entity formulates a policy for the locally accessed IP-Connectivity Access Network (IP-CAN, IP-Connectivity Access Network) session, and forwards the received policy to the policy enforcement entity of the fixed network by the policy decision entity of the network; The policy enforcement entity of the network and the policy enforcement entity of the fixed network install and execute the received policy.
  • IP-CAN IP-Connectivity Access Network
  • the policy decision entity of the mobile network when the policy decision entity of the mobile network is internally or externally triggered and needs to update the formulated policy, the policy decision entity of the mobile network will be the body; the fixed decision entity of the fixed network The updated policy is forwarded to the policy enforcement entity of the fixed network; the policy enforcement entity of the mobile network and the policy enforcement entity of the fixed network install and execute the updated policy.
  • the policy decision entity of the mobile network notifies the policy enforcement entity of the mobile network and the policy decision entity of the fixed network to delete the policy related to the IP-CAN session; the policy enforcement entity of the mobile network and the policy decision of the fixed network The entity performs policy deletion separately, and the policy decision entity of the fixed network notifies the policy enforcement entity of the fixed network to delete the policy related to the IP-CAN session; the policy enforcement entity of the fixed network performs the policy deletion. It should be noted that after receiving the policy, the policy decision entity of the fixed network needs to save the received policy.
  • the decision-making entity of the fixed network may need to map the received policy to the policy in the fixed network, such as: mapping the QoS parameters in the mobile network to the QoS parameters of the fixed network;
  • mapping the QoS parameters in the mobile network to the QoS parameters of the fixed network
  • the fixed network belongs to different operators, it may also need to adjust the received policies based on the protocols signed between the operators, such as: increase or decrease the bandwidth, increase or decrease the QoS level.
  • the policy decision entity of the fixed network sends the mapped and/or adjusted policy to the policy enforcement entity of the fixed network.
  • the policy decision entity of the mobile network in the present invention may be a PCRF;
  • the policy decision entity of the fixed network may be the RACS in the architecture shown in FIG. 6, or the RACF in the architecture shown in FIG. 7, or may be FIG.
  • the policy enforcement entity of the fixed network may be the RCEF in the architecture shown in FIG. 6, the PE-FE in the architecture shown in FIG. 7, or the PEP in the architecture shown in FIG.
  • the policy enforcement entity of the mobile network includes the following At least one of: a radio side network element, an L-GW, and a home base station gateway; wherein, the radio side network element includes at least one of: a base station, a home base station, and a radio network controller; if the mobile user ⁇ is shown in FIG. 9c as a Femtocell Or local access of the WIFI connection, then the policy enforcement entity of the mobile network includes at least one of the following: PCEF and BBERF.
  • the PCRF is triggered by an internal or external (for example, receiving a request message from the L-GW), and a policy needs to be formulated for the LIPA connection, and the policy may be QoS policy and/or charging policy; the PCRF delivers the formulated policy to the policy enforcement entity of the mobile network and sends the policy to the fixed network decision making entity (RACS/RACF/PDP); the fixed network decision making entity (RACS) /RACF/PDP ) saves the received policy and can map and/or adjust the policy, and then deliver it to the policy enforcement entity of the fixed network (RCEF/PE-FE/PEP), so that the QoS on each node into which the LIPA-connected data stream flows can be guaranteed.
  • the PCRF delivers the formulated policy to the policy enforcement entity of the mobile network and sends the policy to the fixed network decision making entity (RACS/RACF/PDP); the fixed network decision making entity (RACS) /RACF/PDP ) saves the received policy and can map and/or adjust the policy, and then
  • Step 101 The PCRF is triggered to formulate a corresponding policy for the LIPA connection.
  • the execution entity may be: at least one of a wireless side network element, an L-GW, and a home base station gateway.
  • Step 103 The policy enforcement entity of the mobile network installs and executes the policy after receiving the policy.
  • Step 104 The PCRF sends the formulated policy to the policy decision entity of the fixed network, where the policy decision entity of the fixed network may be: RACS, RACF, or PDP.
  • Step 105 The policy decision entity of the fixed network saves the received policy, and may map and/or adjust the received policy.
  • Step 106 The policy decision entity of the fixed network sends the policy to the policy enforcement entity of the fixed network, where the policy enforcement entity of the fixed network may be: RCEF, PE-FE, or PEP.
  • step 105 If there is a mapping and/or adjustment of the execution policy in step 105, then the policy execution entity sent to the fixed network in step 106 is a mapped and/or adjusted policy.
  • Step 107 The policy enforcement entity of the fixed network installs and executes the received policy.
  • step 102 and step 104 can be performed concurrently.
  • the PCRF is triggered by an internal or external (for example, receiving a request message from the L-GW), and a policy needs to be formulated for the Femtocell/WIFI connection. Is a QoS policy and/or a charging policy; the PCRF delivers the formulated policy to the policy enforcement entity of the mobile network, and sends the policy to the fixed network decision making entity (RACS/RACF/PDP); the fixed network policy decision entity ( RACS/RACF/PDP) The received policy can be mapped or adjusted, and then sent to the fixed network policy enforcement entity (RCEF/PE-FE/PEP) to ensure the data of the Femtocell/WIFI connection.
  • the fixed network decision making entity (RACS/RACF/PDP)
  • RACS/RACF/PDP fixed network policy decision entity
  • the received policy can be mapped or adjusted, and then sent to the fixed network policy enforcement entity (RCEF/PE-FE/PEP) to ensure the data of the Femtocell/WIFI connection.
  • the policy of the policy enforcement entity that is sent to the fixed network may be a dynamic policy that is delivered to the IP-Sec tunnel, because the UE and the mobile core network device establish an IP-Sec tunnel.
  • the specific implementation process is shown in Figure 10b, which mainly includes the following steps:
  • Step 201 The PCRF is triggered to formulate a corresponding strategy for the Femtocell/WIFI connection.
  • the slightly executing entities can be: PCEF and / or BBERF.
  • Step 203 The policy enforcement entity of the mobile network installs and executes the policy after receiving the policy.
  • the policy formulated by the PCRF does not need to be sent to the policy enforcement entity of the mobile network, that is, in this case, steps 202-203 The operation can be performed without.
  • Step 204 The PCRF sends the formulated policy to the policy decision entity of the fixed network, where the policy decision entity of the fixed network may be: RACS, RACF, or PDP.
  • Step 205 The policy decision entity of the fixed network saves the received policy, and may map or adjust the received policy.
  • Step 206 The policy enforcement entity of the fixed network sends the policy to the policy enforcement entity of the fixed network, where the policy enforcement entity of the fixed network may be: RCEF, PE-FE, or PEP.
  • Step 207 The policy enforcement entity of the fixed network installs and executes the received policy.
  • the step 202 and the step 204 can be performed concurrently.
  • the PCRF is triggered internally or externally (internal triggers such as changes in the operator policy, external triggers such as user subscription data transmission changes), and the previously formulated policies are required.
  • the update is performed by the PCRF to the fixed network policy decision entity (RACS/RACF/PDP); the fixed network policy decision entity saves the updated policy and delivers the updated policy to the fixed network policy enforcement entity (RCEF) /PE-FE/PEP ), after the fixed-line policy decision entity receives the update notification, it installs and executes the updated policy.
  • the local gateway, and/or the home base station gateway, and/or the wireless side network element; the policy decision entity of the mobile network installs and executes the updated policy after receiving the update.
  • the specific implementation process is shown in Figure 11a, which mainly includes the following steps:
  • Step 301 the PCRF is triggered internally or externally, and the previously formulated policy needs to be updated.
  • Step 302 The PCRF notifies the policy enforcement entity of the mobile network of the policy update, where the policy enforcement entity may be: at least one of a wireless side network element, an L-GW, and a home base station gateway.
  • the PCRF carries the ID of the policy that needs to be updated in the notification message, so that the policy enforcement entity of the mobile network can know which policies need to be updated after receiving the notification message.
  • Step 303 The policy enforcement entity of the mobile network receives the updated policy, and installs and executes the policy.
  • Step 304 The PCRF notifies the policy decision entity of the fixed network of the policy update, and the policy decision entity may be: RACS, RACF, or PDP.
  • Step 305 The policy decision entity of the fixed network saves the updated policy, and may map or adjust the received policy.
  • Step 306 The policy decision entity of the fixed network notifies the policy enforcement entity of the fixed network of the policy update, and the policy enforcement entity may be: RCEF, PE-FE, or PEP.
  • Step 307 The policy enforcement entity of the fixed network follows and executes the updated policy.
  • the step 302 and the step 304 can be performed concurrently.
  • the PCRF is internally or externally triggered, and the previously formulated policy needs to be updated; the PCRF to the fixed network policy decision entity (RACS/RACF/PDP) Notification update; the fixed network policy decision entity saves the updated policy, and delivers the updated policy to the fixed network policy enforcement entity (RCEF/PE-FE/PEP), and the fixed network policy decision entity receives the update notification. After that, install and execute the updated policy. It is PCEF and/or BBERF; after the policy decision entity of the mobile network receives the update, it installs and executes the updated policy.
  • the UE and the mobile core network device establish an IP-Sec tunnel
  • the policy of the policy enforcement entity that is sent to the fixed network may be a dynamic policy that is delivered to the IP-Sec tunnel.
  • the specific implementation process is shown in Figure l ib, which mainly includes the following steps:
  • step 401 the PCRF is triggered internally or externally, and the previously formulated policy needs to be updated.
  • Step 402 The PCRF notifies the policy enforcement entity of the mobile network of the policy update, and the policy enforcement entity may be: PCEF and/or BBERF.
  • Step 403 The policy enforcement entity of the mobile network receives the updated policy, and installs and executes the policy.
  • the PCRF updated policy does not need to be sent to the policy enforcement entity of the mobile network, that is, in this case, step 402 ⁇
  • the operation of 403 may not be performed.
  • Step 404 The PCRF notifies the policy decision entity of the fixed network of the policy update, and the policy decision entity may be: RACS, RACF, or PDP.
  • Step 405 The policy decision entity of the fixed network saves the updated policy, and may map or adjust the received policy.
  • Step 406 The policy decision entity of the fixed network notifies the policy enforcement entity of the fixed network of the policy update, and the policy enforcement entity may be: RCEF, PE-FE, or PEP.
  • Step 407 The policy enforcement entity of the fixed network follows and executes the updated policy.
  • the step 402 and the step 404 can be performed concurrently.
  • the PCRF when the LIPA connection is released, the PCRF notifies the fixed network policy decision entity (RACS/RACF/PDP) to delete the session-related policy, and the fixed network policy decision The decision-making enforcement entity (RCEF/PE-FE/PEP) of the fixed network is notified to delete the session-related policy.
  • the specific implementation process is shown in Figure 12a, which mainly includes the following steps:
  • Step 501 When the LIPA connection is released, the PCRF learns that the session ends, and needs to notify the deletion of the policy related to the session.
  • the policy enforcement entity may be: at least one of a wireless side network element, an L-GW, and a home base station gateway.
  • the PCRF carries the ID of the policy to be deleted in the notification message, so that the policy enforcement entity of the mobile network can know which policies need to be deleted after receiving the notification message.
  • Step 503 The policy execution entity of the mobile network performs an operation of deleting the policy.
  • Step 504 The PCRF notifies the policy decision entity of the fixed network to delete the policy related to the session, where the policy decision entity may be: RACS, RACF, or PDP.
  • Step 505 The policy decision entity of the fixed network performs an operation of deleting the policy.
  • Step 506 The policy decision entity of the fixed network notifies the policy enforcement entity of the fixed network to delete the policy related to the session.
  • Step 507 The policy enforcement entity of the fixed network performs an operation of deleting the policy.
  • the PCRF when the Femtocell/WIFI connection is released, the PCRF notifies the fixed network policy decision entity (RACS/RACF/PDP) to delete the session-related policy, and the fixed network policy decision entity notifies the fixed network decision.
  • the execution entity (RCEF/PE-FE/PEP) deletes the session-related policy.
  • Step 601 When the Femtocell/WIFI connection is released, the PCRF learns that the session ends, and needs to notify the deletion of the session-related policy.
  • the policy enforcement entity can be: PCEF and / or BBERF.
  • Step 603 The policy execution entity of the mobile network performs an operation of deleting the policy.
  • the PCRF does not need to notify the policy enforcement entity of the mobile network to perform policy deletion, that is, in this case, the operations of steps 602-603 may not be performed.
  • Step 604 The PCRF notifies the policy decision entity of the fixed network to delete the policy related to the session, where the policy decision entity may be: RACS, RACF, or PDP.
  • Step 605 The policy decision entity of the fixed network performs an operation of deleting the policy.
  • Step 606 The policy decision entity of the fixed network notifies the policy enforcement entity of the fixed network to delete the policy related to the session.
  • Step 607 The policy enforcement entity of the fixed network performs an operation of deleting the policy.
  • the present invention further provides a policy control system for local access of mobile users, including: a policy decision entity of a mobile network, a policy enforcement entity of a mobile network, a policy decision entity of a fixed network, and a fixed network. Policy enforcement entity.
  • the policy decision entity of the mobile network is configured to formulate a policy for the locally accessed IP-CAN session when the mobile user accesses the local, and send the formulated policy to the policy enforcement entity of the mobile network and the fixed network respectively.
  • the method and system of the present invention implement dynamic QoS control on the traffic of the data flow of the mobile user's local IP access, and avoid the precise control when the mobile network and the fixed network belong to different operators. In the case of this part of the traffic, the transmission quality of these data streams is guaranteed.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明公开了一种对移动用户本地接入的策略控制方法，包括：移动网络的策略决策实体为IP连接访问网络（IP-CAN）会话制定策略，并将制定的策略分别发送给移动网络的策略执行实体和固网的策略决策实体；固网的策略决策实体将接收的策略发送给固网的策略执行实体；移动网络的策略执行实体和固网的策略执行实体安装并执行所接收的策略。本发明还公开了一种对移动用户本地接入的策略控制的系统。通过本发明的方法和系统，实现了对移动用户本地IP访问的数据流的流量进行动态服务质量（QoS）控制。

Description

一种对移动用户本地接入的策略控制方法和系统 技术领 j或时
本发明涉及移动通信领域的接入技术， 尤其涉及一种对移动用户本地 接入的策略控制方法和系统。 背景技术
第三代合作伙伴计划 （3GPP, 3rd Generation Partnership Project )演进 的分组系统（ EPS , Evolved Packet System ) 由演进的通用移动通信系统陆 地无线接入网 （E-UTRAN , Evolved Universal Terrestrial Radio Access Network ), 移动管理单元 ( MME, Mobility Management Entity ), 服务网关 ( S-GW , Serving Gateway )、分组数据网络网关（ P-GW , Packet Data Network Gateway ), 归属用户服务器（HSS , Home Subscriber Server )、 3 GPP的认证 4受权计费 ( AAA, Authentication、 Authorization and Accounting )月良务器, 策略和计费规则功能实体 ( PCRF, Policy and Charging Rules Function )及 其他支撑节点组成。
现有的 EPS系统架构如图 1所示， MME负责移动性管理、非接入层信 令的处理和用户移动管理上下文的管理等控制面的相关操作； S-GW是与 E-UTRAN相连的接入网关设备， 在 E-UTRAN和 P-GW之间转发数据， 并 负责对寻呼等待数据进行緩存； P-GW则是 EPS与分组数据网络（PDN, Packet Data Network )的边界网关， 负责 PDN的接入及在 EPS与 PDN间转 发数据等； S-GW和 P-GW都属于核心网网关； PCRF通过接收接口 Rx和 运营商网络协议（ IP , Internet Protocol )业务网络相连， 获取业务信息， 此 夕卜， PCRF通过 Gx/Gxa/Gxc接口与网络中的网关设备相连， 负责发起 IP承 载的建立， 保证业务数据的服务质量（QoS, Quality of Service ), 并进行计 费控制。
EPS支持与非 3GPP 系统的互通， 其中， 与非 3GPP 系统的互通通过 S2a/b/c接口实现， P-GW作为 3GPP与非 3GPP系统间的锚点。 在 EPS的 系统架构图中，非 3GPP IP接入网被分为可信任非 3GPP IP接入网和不可信 任非 3GPP IP接入网。可信任非 3GPP IP接入网可直接通过 S2a接口与 P-GW 连接； 不可信任非 3GPP IP接入网需经过演进的分组数据网关 （ePDG, Evolved Packet Data Gateway )与 P-GW相连， ePDG与 P-GW间的接口为 S2b, S2c提供了用户设备 ( UE, User Equipment )与 P-GW之间的用户面 相关的控制和移动性支持， 其支持的移动性管理协议为支持双栈的移动 IPv6 ( DSMIPv6, Mobile IPv6 Support for Dual Stack Hosts and Routers )。
在 EPS系统中， 策略和计费执行功能实体 ( PCEF, Policy and Charging Enforcement Function )存在于 P-GW中， PCRF与 P-GW之间通过 Gx接口 交换信息。 当 P-GW与 S-GW间的接口基于代理移动 IPv6 ( PMIPv6, Proxy Mobile IPv6 )时， S-GW也具有承载绑定和事件报告功能（BBERF, Bearer Binding and Event Report Function )对业务数据流进行 QoS控制， S-GW与 PCRF之间通过 Gxc接口交换信息。 当通过可信任非 3GPP接入网接入时， 可信任非 3GPP接入网关中也驻留 BBERF。 可信任非 3GPP接入网关与 PCRF之间通过 Gxa接口交换信息。
当 UE漫游时， S9接口作为归属地 PCRF和拜访地 PCRF的接口， 同 时为 UE提供业务的应用功能（ AF, Application Function ), 通过 Rx接口向 PCRF发送用于制定策略和计费控制 （ PCC, Policy and Charging Control ) 策略的业务信息。在 3GPP中， 通过接入点名称（ APN, Access Point Name ) 可以找到对应的 PDN网络。 通常将 UE到 PDN网络的一个连接称为一个 IP连接接入网 （IP-CAN, IP Connectivity Access Network )会话。 在建立 IP-CAN会话的过程中， BBERF和 PCEF分别与 PCRF之间建立 Diameter 会话， 通过这些 Diameter会话来传送对该 IP-CAN会话进行控制的策略计 费信息和用于制定策略的信息等。
家用基站是一种小型、 低功率的基站， 部署在家庭及办公室等室内场 所， 主要作用是为了给用户提供更高的业务速率并降低使用高速率服务所 需要的费用， 同时弥补已有分布式蜂窝无线通信系统覆盖的不足。 在家用 基站系统中， 家用基站为无线侧网元。 家用基站可以直接连接到核心网络， 如图 2a所示； 也可以通过家用基站网关这个逻辑网元接入到核心网络， 如 图 2b所示， 其中， 家用基站网关的主要功能为： 验证家用基站的安全性， 处理家用基站的注册， 对家用基站进行运行维护管理， 根据运营商要求配 置和控制家用基站， 负责交换核心网和家用基站的数据等等。
除了支持移动核心网络的接入以外， 移动通信系统（包括家用基站系 统）还可支持本地 IP访问功能，在无线侧网元具备本地 IP访问能力以及用 户签约允许本地 IP访问的条件下，可实现终端对家用网络其他 IP设备或者 互联网络的本地接入。
本地 IP访问的实现可以釆用多种连接建立方式： 可通过建立一个连接 来同时实现核心网访问以及本地 IP的访问功能， 如图 2a和图 2b所示， 此 时无需在无线侧网元或家用基站网关上增设本地网关的功能； 也可通过增 设本地网关来提供对本地 IP访问技术的有力支持， 本地网关可与无线侧网 元进行合设， 如图 3a所示。 当存在家用基站网关的情况下， 本地网关不仅 可与家用基站进行合设， 也可与家用基站网关进行合设， 如图 3b所示。 本 地网关可以是本地 SGW ( L-SGW, Local SGW )和本地 PGW ( L-PGW, Local PGW ), 可以是单独的 L-PGW。 此外， 家用基站网关可以与家用基站 进行合设。对于通用陆地无线接入网络（ UTRAN, Universal Terrestrial Radio Access Network ) 系统， 核心网网关可以是服务 GPRS支持节点 （ SGSN, Serving GPRS Support Node )、网关 GPRS支持节点（ GGSN, Gateway GPRS Support Node )„ 本地网关可以是本地 GGSN ( L-GGSN, Local GGSN )和 本地 SGSN ( L-SGSN, Local SGSN ), 可以是单独的 L-GGSN。
以长期演进（ LTE , Long Term Evolution ) 的移动通信网络架构为例， 图 4a示出了在图 2a的无线通信系统中本地 IP访问和核心网连接的数据流， 其中， 本地 IP访问的流量是通过固网接入设备接入固网的， 如图 5a所示。 图 4b示出了在图 3a的无线通信系统中本地 IP访问和核心网连接的数据流， 其中， 本地 IP访问的流量是通过固网接入设备接入固网的， 如图 5b所示。
与本地 IP访问类似的一种接入技术为毫微微蜂窝基站（ Femtocell ) ,移 动运营商为了能够给用户带来更好的体验， 大量部署这类家用基站， 以此 解决了覆盖不足的问题； 借助固定宽带接入为室内环境中的用户提供质量 更好、 速度更快、 服务更多的移动业务； 用户的数据流通过家用基站接入， 利用用户已有的非对称数字用户环路（ ADSL, Asymmetric Digital Subscriber Line )、 局域网 （ LAN , Local Area Network )等宽带连接， 将用户的数据发 送到网络中。
当用户是移动用户时， 该用户的业务数据流通过家用基站流进固网传 输节点， 如接入网 （AN, Access Network )、 宽带远程接入服务器（ BRAS, Broadband Remote Access Server )、宽带网络网关（ BNG, Broadband Network Gateway )等设备， 再流向移动网络或直接通过本地路由出去， 如图 5c 中 的 Femtocell接入数据流所示；运营商也可以部署无线保真（ WIFI, Wireless Fidelity )来提供无线覆盖， 如图 5c中的 WIFI接入数据流所示， 为了能够 给用户带来更好的业务体验，需要为这些数据流提供相应的 QoS服务质量， 这意味着该数据流所流进的各个节点 (包括固网传输设备和移动传输设备） 的资源需要得到保证。
对于固网的资源控制， 目前有三大标准组织正在研究。
用于高级网络的通信和互联网融合的业务和协议 （ TISPAN ,
Telecommunication and Internet converged Services and Protocols for Advanced Networking )提出了资源接纳控制子系统 ( RACS , Resource and Admission Control Subsystem ) 来解决下一代网络 ( NGN, Next Generation Network )承载网的 QoS问题。 TISPAN将 NGN架构分为业务层和传输层， 在传输层引入了 RACS 与网络附着子系统 （NASS , Network Attachment Subsystem ) , RACS解决 NGN承载网的 QoS问题， 而 NASS则负责为上层 业务层提供独立的用户接入管理。 TISPAN RACS的主要功能与国际电信联 盟电信标准化邵门 ( ITU-T , International Telecommunication Union Telecommunications standardization sector ) 的资源接纳控制功能实体 ( RACF, Resource and Admission Control Functions )类似。
TISPAN RACS的功能架构， 如图 6所示， RACS将业务层的资源需求 与传输层的资源分配相关联， 主要完成策略控制、 资源预留、 接纳控制、 网络地址转换 ( NAT, Network Address Translation )穿越等功能。 RACS通 过一系列的 QoS策略为业务层提供传输层的控制服务，使得用户终端（UE, User Equipment )可以获得所需服务质量保证。
RACS 由两个实体组成： 基于业务的策略决策功能实体 （ SPDF ,
Service-based Policy Decision Function ) 和接入资源接纳控制功能实体 ( A-RACF, Access-Resource and Admission Control Function )。 其中, SPDF 向应用层提供统一的接口， 屏蔽底层网络拓朴和具体的接入类型， 提供基 于业务的策略控制； SPDF根据应用功能实体（AF, Application Function ) 的请求选择本地策略， 并将请求映射成 IP QoS参数， 发送给 A-RACF和边 界网关功能实体（BGF, Border Gateway Function ), 以控制相应的资源。 A-RACF位于接入网中， 具有接纳控制和网络策略汇聚的功能； 从 SPDF 接收请求， 然后基于所保存的策略实现接纳控制， 接受或拒绝对传输资源 的请求； A-RACF通过 e4接口从 NASS获得网络附着信息和用户签约信息， 从而可以根据网络位置信息 （例如接入用户的物理节点的地址）确定可用 的网络资源， 同时在处理资源分配请求时参考用户签约信息。
传输层中包含三种功能实体： 接入节点、 BGF、 资源控制执行功能实 体 ( RCEF, Resource Control Enforcement Function )。 其中, BGF是一个包 到包网关， 可位于接入网和核心网之间 （实现核心边界网关功能）， 也可以 位于两个核心网之间 （实现互联边界网关功能）。 BGF在 SPDF的控制下完 成 NAT穿越、 门控、 QoS标记、 带宽限制、 使用测量以及资源同步功能。 RCEF实施 A-RACF通过 Re接口传送过来的接入运营商定义的二层 /三层 ( L2/L3 )媒体流策略， 完成门控、 QoS标记、 带宽限制等功能。
ITU-T是国际电信联盟 ( ITU, International Telecommunication Union ) 的电信化部门， 制定了有关资源接纳控制的标准。 在 ITU-T 最新公布的 RACF草案中， 提供了 RACF的功能框架， 如图 7所示， RACF由两部分组 成， 分别是策略决策功能实体 ( PD-FE, Policy Decision Functional Entity ) 和传输资源控制功能实体 ( TRC-FE, Transport Resource Control Functional Entity )。 其中， TRC-FE通过 Rc与传输功能交互， 通过 Rn与传输资源执 行功能实体 ( TRE-FE, Transport Resource Enforcement Functional Entity )交 互； PD-FE通过 Rt与 TRC-FE交互，通过 Rh与用户驻地网（ CPN, Customer Premises Network ) 交互， 通过 Rw 与策略执行功能实体 ( PE-FE, Policy Enforcement Functional Entity ) 交互， 通过 Rs与业务层的业务控制功能实 体（SCF, Service Control Functions ) 交互， 通过 Ru与网络附着控制功能 ( NACF, Network Attachment Control Functions ) 交互, 并且 PD-FE通过 Ri接口与其他 NGN交互。
此外， PD-FE与传输技术无关， 与 SCF也无关， PD-FE基于网络策略 规则、 SCF提供的业务信息、 NACF提供的传输层签约信息， 以及 TRC-FE 提供的资源可用性决策结果， 做出资源接纳控制的最后决策。
TRC-FE与业务无关， 但与传输技术相关。 TRC-FE负责收集和维护传 输网信息和资源状态信息， 从 PD-FE收到资源请求后， TRC-FE基于 QoS、 优先级需求、 资源可用性信息以及与传输相关的策略规则， 执行基于资源 的接纳控制。
传输层 PE-FE和 TRE-FE组成。 PE-FE执行 PD-FE下发的策略规则， PE-FE是包到包网关， 可以位于 CPN和接入网络之间、 接入网和核心网之 间或者不同运营商网络之间， 是支持动态 QoS控制、 端口地址转换控制和 NAT穿越的关键节点。 TRE-FE执行 TRC-FE下发的传输资源策略规则。
宽带论坛 （ BBF , Broadband Forum )提出了宽带策略控制架构集中式 "^署功能架构 ( BPCF, Centralized Deployment Functional Architecture ), ^口 图 8所示， 策略决策点（PDP, Policy Decision Point )的主要功能是制定相 应的策略； 策略执行点 （ PEP , Policy Enforcement Point )根据 PDP制定的 相应策略进行执行； AAA储存用户签约信息； AF为 PDP制定策略， 提供 相应的业务信息。
然而， 在目前的本地 IP访问 （ LIPA, Local IP Access )技术中， 如何 对移动用户本地 IP访问的数据流的流量进行动态 QoS控制尚未明确， 当移 动网络和固定网络分属不同的运营商时， 会出现无法精确控制这部分流量 的情况， 从而会导致这些数据流的传输质量无法得到保证， 影响网络业务 的正常开展和运维。 发明内容
有鉴于此， 本发明的主要目的在于提供一种对移动用户本地接入的策 略控制方法和系统， 以实现对移动用户本地 IP访问的数据流的流量进行动 态 QoS控制。
为达到上述目的， 本发明的技术方案是这样实现的：
本发明提供了一种对移动用户本地接入的策略控制方法， 该方法包括： 移动网络的策略决策实体为 IP连接访问网络（ IP-CAN )会话制定策略， 给移动网络的策略执行实体和固网的策略决策实 体；
所述固网的策略决策实体将接收的策略发送给固网的策略执行实体； 所述移动网络的策略执行实体和固网的策略执行实体安装并执行所接 收的策略。
该方法进一步包括：
所述固网的策略决策实体接收到策略后， 对所述策略进行保存， 并对 保存的策略进行映射和 /或调整；
所述固网的策略决策实体将映射和 /或调整后的策略发送给固网的策略 执行实体。
该方法进一步包括：
在所述 IP-CAN会话过程中，当移动网络的策略决策实体受到内部或外 部触发， 并需要对制定的策略进行更新时， 所述移动网络的策略决策实体 体； 所述固网的策略决策实体将更新后的策略转发给固网的策略执行实体； 所述移动网络的策略执行实体和固网的策略执行实体安装并执行更新 后的策略。
该方法进一步包括：
在所述 IP-CAN会话结束时，所述移动网络的策略决策实体通知移动网 络的策略执行实体和固网的策略决策实体删除与所述 IP-CAN会话相关的 策略；
所述移动网络的策略执行实体和固网的策略决策实体分别执行策略删 除， 且所述固网的策略决策实体通知固网的策略执行实体删除与所述 IP-CAN会话相关的策略；
所述固网的策略执行实体执行策略删除。 所述固网的策略决策实体为： 资源接纳控制子系统（RACS )、 资源接 纳控制功能实体（RACF )或策略决策点 （PDP )。
所述固网的策略执行实体为： 资源控制执行功能实体（RCEF )、 策略 执行功能实体（PE-FE )或策略执行点 （PEP )。
如果所述移动用户是基于本地 IP访问 （LIPA )连接的本地接入， 则所 述移动网络的策略执行实体包括以下至少之一： 无线侧网元、 本地网关 ( L-GW )和家用基站网关； 其中， 所述无线侧网元包括以下至少之一： 基 站、 家用基站和无线网络控制器；
如果所述移动用户是基于毫微微蜂窝基站 （Femtocell ) 或无线保真 ( WIFI )连接的本地接入， 则所述移动网络的策略执行实体包括以下至少 之一： 策略和计费执行功能实体（PCEF )和承载绑定和事件报告功能实体 ( BBERF )。
所述策略为服务质量（QoS ) 策略和 /或计费策略。
本发明还提供了一种对移动用户本地接入的策略控制系统， 该系统包 括： 移动网络的策略决策实体、 移动网络的策略执行实体、 固网的策略决 策实体和固网的策略执行实体， 其中，
所述移动网络的策略决策实体，用于为 IP-CAN会话制定策略，并将制 所述移动网络的策略执行实体， 用于安装并执行所接收的策略； 所述固网的策略决策实体， 用于将接收的策略发送给固网的策略执行 实体；
所述固网的策略执行实体， 用于安装并执行所接收的策略。
所述固网的策略决策实体进一步用于， 在接收到策略后， 对所述策略 进行保存， 并对保存的策略进行映射和 /或调整， 再将映射和 /或调整后的策 略发送给固网的策略执行实体。 所述移动网络的策略决策实体进一步用于， 在所述 IP-CAN会话过程 中， 当移动网络的策略决策实体受到内部或外部触发， 并需要对制定的策 网的策略决策实体；
相应的， 所述固网的策略决策实体进一步用于， 将更新后的策略转发 给固网的策略执行实体；
所述移动网络的策略执行实体和固网的策略执行实体进一步用于， 安 装并执行更新后的策略。
所述移动网络的策略决策实体进一步用于， 在所述 IP-CAN会话结束 时， 通知移动网络的策略执行实体和固网的策略决策实体删除与所述 IP-CAN会话相关的策略；
相应的， 所述固网的策略决策实体进一步用于， 执行策略删除， 并通 知固网的策略执行实体删除与所述 IP-CAN会话相关的策略；
所述移动网络的策略执行实体和固网的策略执行实体进一步用于， 分 别执行策略删除。
所述固网的策略决策实体为： RACS、 RACF或 PDP。
所述固网的策略执行实体为： RCEF、 PE-FE或 PEP。
如果所述移动用户是基于 LIPA连接的本地接入，则所述移动网络的策 略执行实体包括以下至少之一：无线侧网元、 L-GW和家用基站网关；其中， 所述无线侧网元包括以下至少之一： 基站、 家用基站和无线网络控制器； 如果所述移动用户是基于 Femtocell或 WIFI连接的本地接入， 则所述 移动网络的策略执行实体包括以下至少之一： PCEF和 BBERF。
本发明所提供的一种对移动用户本地接入的策略控制方法和系统， 在 移动用户通过本地接入时，移动网络的策略决策实体为本地接入的 IP-CAN 网的策略决策实体； 固网的策略决策实体将接收的策略转发给固网的策略 执行实体； 移动网络的策略执行实体和固网的策略执行实体安装并执行所 接收的策略。 通过本发明， 实现了对移动用户本地 IP访问的数据流的流量 进行动态 QoS控制， 避免了当移动网络和固定网络分属不同的运营商时， 无法精确控制这部分流量的情况， 使这些数据流的传输质量得到保证。 附图说明
图 1为现有技术中 EPS的系统架构示意图；
图 2a为现有技术中移动通信网络连接的示意图一；
图 2b为现有技术中移动通信网络连接的示意图二；
图 3a为现有技术中移动通信网络连接的示意图三；
图 3b为现有技术中移动通信网络连接的示意图四；
图 4a为现有技术中移动通信系统本地 IP接入数据流的示意图一； 图 4b为现有技术中移动通信系统本地 IP接入数据流的示意图二； 图 5a为现有技术中移动通信系统本地 IP接入固网传输设备数据流的示 意图一；
图 5b为现有技术中移动通信系统本地 IP接入固网传输设备数据流的示 意图二；
图 5c为现有技术中移动通信系统本地 IP接入固网传输设备数据流的示 意图三；
图 6为现有技术中 TISPAN RACS资源控制架构的示意图；
图 7为现有技术中 ITU-T RACF资源控制架构的示意图；
图 8为现有技术中 BPCF资源控制架构的示意图；
图 9a为本发明中本地访问连接的示意图一；
图 9b为本发明中本地访问连接的示意图二；
图 9c为本发明中本地访问连接的示意图三； 图 10a为本发明实施例一的策略控制方法流程图；
图 10b为本发明实施例二的策略控制方法流程图；
图 11a为本发明实施例三的策略控制方法流程图；
图 l ib为本发明实施例四的策略控制方法流程图；
图 12a为本发明实施例五的策略控制方法流程图；
图 12b为本发明实施例六的策略控制方法流程图。 具体实施方式
下面结合附图和具体实施例对本发明的技术方案进一步详细阐述。 为实现对移动用户本地 IP访问的数据流的流量进行动态 QoS控制，本 发明提供一种对移动用户本地接入的策略控制方法， 其核心思想为： 当移 动用户通过本地接入时， 移动网络的策略决策实体为本地接入的 IP连接访 问网络（IP-CAN, IP-Connectivity Access Network )会话制定策略， 并将制 网的策略决策实体将接收的策略转发给固网的策略执行实体； 移动网络的 策略执行实体和固网的策略执行实体安装并执行所接收的策略。
另夕卜，在 IP-CAN会话过程中， 当移动网络的策略决策实体受到内部或 外部触发， 并需要对制定的策略进行更新时， 移动网络的策略决策实体将 体； 固网的策略决策实体将更新后的策略转发给固网的策略执行实体； 移 动网络的策略执行实体和固网的策略执行实体安装并执行更新后的策略。
在 IP-CAN会话结束时，移动网络的策略决策实体通知移动网络的策略 执行实体和固网的策略决策实体删除与 IP-CAN会话相关的策略；移动网络 的策略执行实体和固网的策略决策实体分别执行策略删除， 且固网的策略 决策实体通知固网的策略执行实体删除与 IP-CAN会话相关的策略；固网的 策略执行实体执行策略删除。 需要说明的是， 固网的策略决策实体在接收到策略后， 需要对接收的 策略进行保存。 由于移动网络和固网的差异性， 固网的策略决策实体可能 需要将接收的策略映射为固网中的策略， 如： 将移动网络中的 QoS参数映 射为固网的 QoS参数； 当移动网络和固网分属于不同的运营商时， 还可能 需要基于运营商之间签署的协议对接收的策略进行调整， 如： 提高或降低 带宽、 提高或降低 QoS等级。 在映射和 /或调整之后， 固网的策略决策实体 再将映射和 /或调整后的策略发送给固网的策略执行实体。
此外， 本发明中的移动网络的策略决策实体可以是 PCRF; 固网的策略 决策实体可以为图 6 所示架构中的 RACS , 也可以为图 7 所示架构中的 RACF, 还可以为图 8所示架构中的 PDP; 固网的策略执行实体可以为图 6 所示架构中的 RCEF, 也可以为图 7所示架构中的 PE-FE, 还可以为图 8所 示架构中的 PEP。
如果移动用户是基于图 9a ( L-GW与无线侧网元分设）或图 9M L-GW 与无线侧网元合设 )所示 LIPA连接的本地接入， 则移动网络的策略执行实 体包括以下至少之一： 无线侧网元、 L-GW和家用基站网关； 其中， 无线侧 网元包括以下至少之一： 基站、 家用基站和无线网络控制器； 如果移动用 户^ ^于图 9c所示 Femtocell或 WIFI连接的本地接入， 则移动网络的策略 执行实体包括以下至少之一： PCEF和 BBERF。
下面结合具体实施例对上述策略控制方法进一步详细阐述。
在本发明的实施例一中， 当移动用户完成认证后， PCRF受到一个内部 或是外部的触发（例如： 收到来自 L-GW的请求消息）， 需要为 LIPA连接 制定策略， 该策略可以是 QoS策略和 /或计费策略； PCRF向移动网络的策 略执行实体下发制定的策略，并向固网的策略决策实体（ RACS/RACF/PDP ) 发送该策略； 固网的策略决策实体（ RACS/RACF/PDP )保存接收的策略并 可以对该策略进行映射和 /或调整， 之后下发给固网的策略执行实体 ( RCEF/PE-FE/PEP ),从而使得该 LIPA连接的数据流所流进的各个节点上 的 QoS能够得到保证。 具体实现流程如图 10a所示， 主要包括以下步骤： 步骤 101 , PCRF受到触发， 为 LIPA连接制定相应的策略。 略执行实体可以为： 无线侧网元、 L-GW、 家用基站网关中的至少之一。
步骤 103 , 移动网络的策略执行实体在接收到策略后， 安装并执行该策 略。
步骤 104 , PCRF将制定的策略发送给固网的策略决策实体， 该固网的 策略决策实体可以为： RACS、 RACF或 PDP。
步骤 105 , 固网的策略决策实体保存接收到的策略， 并可以对接收的策 略进行映射和 /或调整。
步骤 106, 固网的策略决策实体将该策略发送给固网的策略执行实体， 该固网的策略执行实体可以为： RCEF、 PE-FE或 PEP。
如果步骤 105中有执行策略的映射和 /或调整， 那么步骤 106中发送给 固网的策略执行实体的是映射和 /或调整后的策略。
步骤 107, 固网的策略执行实体安装并执行所接收的策略。
其中， 步骤 102和步骤 104可以并发执行。
在本发明的实施例二中， 当移动用户完成认证后， PCRF受到一个内部 或外部的触发（例如：收到来自 L-GW的请求消息），需要为 Femtocell/WIFI 连接制定策略， 该策略可以是 QoS策略和 /或计费策略； PCRF向移动网络 的策略执行实体下发制定的策略， 并向固网的策略决策实体 ( RACS/RACF/PDP )发送该策略；固网的策略决策实体（ RACS/RACF/PDP ) 保存接收的策略并可以对该策略进行映射或调整， 之后下发给固网的策略 执行实体（ RCEF/PE-FE/PEP ),从而保证了该 Femtocell/WIFI连接的数据流 所流进的各个节点上的 QoS能够得到保证。 此时， 由于 UE和移动核心网设备建立 IP安全（ IP-Sec )隧道， 因此下 发给固网的策略执行实体的策略可以是针对 IP-Sec隧道下发的动态策略。 具体实现流程如图 10b所示， 主要包括以下步骤：
步骤 201 , PCRF受到触发， 为 Femtocell/WIFI连接制定相应的策略。 略执行实体可以为： PCEF和 /或 BBERF。
步骤 203 , 移动网络的策略执行实体在接收到策略后， 安装并执行该策 略。
需要说明的是， 如果数据流不经过移动网络， 而通过固网传输设备直 接路由出去， 那么 PCRF制定的策略不需要发送给移动网络的策略执行实 体， 即在这种情况下， 步骤 202~203的操作可以不用执行。
步骤 204 , PCRF将制定的策略发送给固网的策略决策实体， 该固网的 策略决策实体可以为： RACS、 RACF或 PDP。
步骤 205 , 固网的策略决策实体保存接收到的策略， 并可以对接收的策 略进行映射或调整。
步骤 206, 固网的策略决策实体将该策略发送给固网的策略执行实体， 该固网的策略执行实体可以为： RCEF、 PE-FE或 PEP。
步骤 207, 固网的策略执行实体安装并执行所接收的策略。
其中， 步骤 202和步骤 204可以并发执行。
在本发明的实施例三中， 在 IP-CAN会话过程中， PCRF受到内部或外 部的触发（内部触发如运营商策略发生变化， 外部触发如用户签约数据发 送变化）， 需要对之前制定的策略进行更新； PCRF向固网的策略决策实体 ( RACS/RACF/PDP )通知更新； 固网的策略决策实体保存更新后的策略， 并将更新后的策略下发给固网的策略执行实体（ RCEF/PE-FE/PEP )， 固网 的策略决策实体收到更新通知后， 安装并执行更新后的策略。 是本地网关、 和 /或家用基站网关、 和 /或无线侧网元； 移动网络的策略决策 实体收到更新后， 安装并执行更新后的策略。 具体实现流程如图 11a所示， 主要包括以下步骤：
步骤 301 , PCRF受到内部或是外部的触发， 需要对之前制定的策略进 行更新。
步骤 302, PCRF向移动网络的策略执行实体通知策略更新， 该策略执 行实体可以是： 无线侧网元、 L-GW、 家用基站网关中的至少之一。
PCRF在通知消息中携带需要更新的策略的 ID , 从而移动网络的策略 执行实体在接收到通知消息后， 能够获知哪些策略需要更新。
步骤 303 , 移动网络的策略执行实体收到更新后的策略， 安装并执行该 策略。
步骤 304, PCRF向固网的策略决策实体通知策略更新， 该策略决策实 体可以为： RACS、 RACF或 PDP。
步骤 305 , 固网的策略决策实体保存更新后的策略， 并可以对接收的策 略进行映射或调整。
步骤 306, 固网的策略决策实体将向固网的策略执行实体通知策略更 新， 该策略执行实体可以为： RCEF、 PE-FE或 PEP。
步骤 307, 固网的策略执行实体按照并执行更新后的策略。
其中， 步骤 302和步骤 304可以并发执行。
在本发明的实施例四中， 在 IP-CAN会话过程中， PCRF受到内部或是 外部的触发， 需要对之前制定的策略进行更新； PCRF向固网的策略决策实 体（ RACS/RACF/PDP )通知更新； 固网的策略决策实体保存更新后的策略， 并将更新后的策略下发给固网的策略执行实体（ RCEF/PE-FE/PEP )， 固网 的策略决策实体收到更新通知后， 安装并执行更新后的策略。 是 PCEF和 /或 BBERF; 移动网络的策略决策实体收到更新后， 安装并执行 更新后的策略。
此时， 由于 UE和移动核心网设备建立 IP-Sec隧道， 因此下发给固网 的策略执行实体的策略可以是针对 IP-Sec隧道下发的动态策略。 具体实现 流程如图 l ib所示， 主要包括以下步骤：
步骤 401 , PCRF受到内部或是外部的触发， 需要对之前制定的策略进 行更新。
步骤 402 , PCRF向移动网络的策略执行实体通知策略更新 , 该策略执 行实体可以是： PCEF和 /或 BBERF。
步骤 403 , 移动网络的策略执行实体收到更新后的策略， 安装并执行该 策略。
需要说明的是， 如果数据流不经过移动网络， 而通过固网传输设备直 接路由出去， 那么 PCRF 更新后的策略不需要发送给移动网络的策略执行 实体， 即在这种情况下， 步骤 402~403的操作可以不用执行。
步骤 404, PCRF向固网的策略决策实体通知策略更新， 该策略决策实 体可以为： RACS、 RACF或 PDP。
步骤 405 , 固网的策略决策实体保存更新后的策略， 并可以对接收的策 略进行映射或调整。
步骤 406, 固网的策略决策实体将向固网的策略执行实体通知策略更 新， 该策略执行实体可以为： RCEF、 PE-FE或 PEP。
步骤 407, 固网的策略执行实体按照并执行更新后的策略。
其中， 步骤 402和步骤 404可以并发执行。
在本发明的实施例五中， 当 LIPA连接释放时， PCRF通知固网的策略 决策实体（ RACS/RACF/PDP )删除与会话相关的策略， 固网的策略决策实 体通知固网的决策执行实体（ RCEF/PE-FE/PEP )删除与会话相关的策略。 具体实现流程如图 12a所示， 主要包括以下步骤：
步骤 501 , 当 LIPA连接释放时， PCRF获知会话结束， 并需要通知删 除与会话相关的策略。 该策略执行实体可以是： 无线侧网元、 L-GW、家用基站网关中的至少之一。
PCRF在通知消息中携带需要删除的策略的 ID , 从而移动网络的策略 执行实体在接收到通知消息后， 能够获知哪些策略需要删除。
步骤 503 , 移动网络的策略执行实体执行删除策略的操作。
步骤 504 , PCRF通知固网的策略决策实体删除与会话相关的策略， 该 策略决策实体可以为： RACS、 RACF或 PDP。
步骤 505 , 固网的策略决策实体执行删除策略的操作。
步骤 506 ,固网的策略决策实体通知固网的策略执行实体删除与会话相 关的策略。
步骤 507, 固网的策略执行实体执行删除策略的操作。
在本发明的实施例六中， 当 Femtocell/WIFI连接释放时， PCRF通知固 网的策略决策实体（ RACS/RACF/PDP )删除与会话相关的策略， 固网的策 略决策实体通知固网的决策执行实体（ RCEF/PE-FE/PEP )删除与会话相关 的策略。 具体实现流程如图 12b所示， 主要包括以下步骤：
步骤 601 , 当 Femtocell/WIFI连接释放时， PCRF获知会话结束， 并需 要通知删除与会话相关的策略。 该策略执行实体可以是： PCEF和 /或 BBERF。
步骤 603 , 移动网络的策略执行实体执行删除策略的操作。
需要说明的是， 如果数据流不经过移动网络， 而通过固网传输设备直 接路由出去， 那么 PCRF无需通知移动网络的策略执行实体执行策略删除， 即在这种情况下， 步骤 602~603的操作可以不用执行。
步骤 604 , PCRF通知固网的策略决策实体删除与会话相关的策略， 该 策略决策实体可以为： RACS、 RACF或 PDP。
步骤 605 , 固网的策略决策实体执行删除策略的操作。
步骤 606 ,固网的策略决策实体通知固网的策略执行实体删除与会话相 关的策略。
步骤 607, 固网的策略执行实体执行删除策略的操作。
对应上述策略控制方法， 本发明还提供了一种对移动用户本地接入的 策略控制系统， 包括： 移动网络的策略决策实体、 移动网络的策略执行实 体、 固网的策略决策实体和固网的策略执行实体。
其中， 移动网络的策略决策实体， 用于在移动用户通过本地接入时， 为本地接入的 IP-CAN会话制定策略，并将制定的策略分别发送给移动网络 的策略执行实体和固网的策略决策实体； 移动网络的策略执行实体， 用于 安装并执行所接收的策略； 固网的策略决策实体， 用于将接收的策略转发 给固网的策略执行实体； 固网的策略执行实体， 用于安装并执行所接收的 策略。
综上所述， 通过本发明的方法和系统， 实现了对移动用户本地 IP访问 的数据流的流量进行动态 QoS控制， 避免了当移动网络和固定网络分属不 同的运营商时， 无法精确控制这部分流量的情况， 使这些数据流的传输质 量得到保证。
以上所述， 仅为本发明的较佳实施例而已， 并非用于限定本发明的保 护范围。

Claims

权利要求书
1、 一种对移动用户本地接入的策略控制方法， 其特征在于， 该方法包 括：
移动网络的策略决策实体为 IP连接访问网络（ IP-CAN )会话制定策略， 体；
所述固网的策略决策实体将接收的策略发送给固网的策略执行实体； 所述移动网络的策略执行实体和固网的策略执行实体安装并执行所接 收的策略。
2、 根据权利要求 1所述对移动用户本地接入的策略控制方法， 其特征 在于， 该方法进一步包括：
所述固网的策略决策实体接收到策略后， 对所述策略进行保存， 并对 保存的策略进行映射和 /或调整；
所述固网的策略决策实体将映射和 /或调整后的策略发送给固网的策略 执行实体。
3、 根据权利要求 1所述对移动用户本地接入的策略控制方法， 其特征 在于， 该方法进一步包括：
在所述 IP-CAN会话过程中，当移动网络的策略决策实体受到内部或外 部触发， 并需要对制定的策略进行更新时， 所述移动网络的策略决策实体 体； 所述固网的策略决策实体将更新后的策略转发给固网的策略执行实体； 所述移动网络的策略执行实体和固网的策略执行实体安装并执行更新 后的策略。
4、 根据权利要求 1所述对移动用户本地接入的策略控制方法， 其特征 在于， 该方法进一步包括： 在所述 IP-CAN会话结束时，所述移动网络的策略决策实体通知移动网 络的策略执行实体和固网的策略决策实体删除与所述 IP-CAN会话相关的 策略；
所述移动网络的策略执行实体和固网的策略决策实体分别执行策略删 除， 且所述固网的策略决策实体通知固网的策略执行实体删除与所述 IP-CAN会话相关的策略；
所述固网的策略执行实体执行策略删除。
5、 根据权利要求 1至 4任一项所述对移动用户本地接入的策略控制方 法， 其特征在于， 所述固网的策略决策实体为： 资源接纳控制子系统
( RACS )、 资源接纳控制功能实体（RACF )或策略决策点 （PDP )。
6、 根据权利要求 1至 4任一项所述对移动用户本地接入的策略控制方 法， 其特征在于， 所述固网的策略执行实体为： 资源控制执行功能实体
( RCEF )、 策略执行功能实体（PE-FE )或策略执行点 （ PEP )。
7、 根据权利要求 1至 4任一项所述对移动用户本地接入的策略控制方 法， 其特征在于，
如果所述移动用户是基于本地 IP访问 （LIPA )连接的本地接入， 则所 述移动网络的策略执行实体包括以下至少之一： 无线侧网元、 本地网关 ( L-GW )和家用基站网关； 其中， 所述无线侧网元包括以下至少之一： 基 站、 家用基站和无线网络控制器；
如果所述移动用户是基于毫微微蜂窝基站 （Femtocell ) 或无线保真 ( WIFI )连接的本地接入， 则所述移动网络的策略执行实体包括以下至少 之一： 策略和计费执行功能实体（PCEF )和承载绑定和事件报告功能实体 ( BBERF )。
8、 根据权利要求 1至 4任一项所述对移动用户本地接入的策略控制方 法， 其特征在于， 所述策略为服务质量（QoS ) 策略和 /或计费策略。
9、 一种对移动用户本地接入的策略控制系统， 其特征在于， 该系统包 括： 移动网络的策略决策实体、 移动网络的策略执行实体、 固网的策略决 策实体和固网的策略执行实体， 其中，
所述移动网络的策略决策实体，用于为 IP-CAN会话制定策略，并将制 所述移动网络的策略执行实体， 用于安装并执行所接收的策略； 所述固网的策略决策实体， 用于将接收的策略发送给固网的策略执行 实体；
所述固网的策略执行实体， 用于安装并执行所接收的策略。
10、 根据权利要求 9所述对移动用户本地接入的策略控制系统， 其特 征在于， 所述固网的策略决策实体进一步用于， 在接收到策略后， 对所述 策略进行保存， 并对保存的策略进行映射和 /或调整， 再将映射和 /或调整后 的策略发送给固网的策略执行实体。
11、 根据权利要求 9 所述对移动用户本地接入的策略控制系统， 其特 征在于，所述移动网络的策略决策实体进一步用于，在所述 IP-CAN会话过 程中， 当移动网络的策略决策实体受到内部或外部触发， 并需要对制定的 固网的策略决策实体；
相应的， 所述固网的策略决策实体进一步用于， 将更新后的策略转发 给固网的策略执行实体；
所述移动网络的策略执行实体和固网的策略执行实体进一步用于， 安 装并执行更新后的策略。
12、 根据权利要求 9所述对移动用户本地接入的策略控制系统， 其特 征在于，所述移动网络的策略决策实体进一步用于，在所述 IP-CAN会话结 束时， 通知移动网络的策略执行实体和固网的策略决策实体删除与所述 IP-CAN会话相关的策略；
相应的， 所述固网的策略决策实体进一步用于， 执行策略删除， 并通 知固网的策略执行实体删除与所述 IP-CAN会话相关的策略；
所述移动网络的策略执行实体和固网的策略执行实体进一步用于， 分 别执行策略删除。
13、 根据权利要求 9至 12任一项所述对移动用户本地接入的策略控制 系统， 其特征在于， 所述固网的策略决策实体为： RACS、 RACF或 PDP。
14、 根据权利要求 9至 12任一项所述对移动用户本地接入的策略控制 系统， 其特征在于， 所述固网的策略执行实体为： RCEF、 PE-FE或 PEP。
15、 根据权利要求 9至 12任一项所述对移动用户本地接入的策略控制 系统， 其特征在于，
如果所述移动用户是基于 LIPA连接的本地接入，则所述移动网络的策 略执行实体包括以下至少之一：无线侧网元、 L-GW和家用基站网关；其中， 所述无线侧网元包括以下至少之一： 基站、 家用基站和无线网络控制器； 如果所述移动用户是基于 Femtocell或 WIFI连接的本地接入， 则所述 移动网络的策略执行实体包括以下至少之一： PCEF和 BBERF。
PCT/CN2010/078824 2010-02-03 2010-11-17 一种对移动用户本地接入的策略控制方法和系统 WO2011095025A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010110823.1 2010-02-03
CN201010110823.1A CN102143530B (zh) 2010-02-03 2010-02-03 一种对移动用户本地接入的策略控制方法和系统

Publications (1)

Publication Number Publication Date
WO2011095025A1 true WO2011095025A1 (zh) 2011-08-11

Family

ID=44354927

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/078824 WO2011095025A1 (zh) 2010-02-03 2010-11-17 一种对移动用户本地接入的策略控制方法和系统

Country Status (2)

Country Link
CN (1) CN102143530B (zh)
WO (1) WO2011095025A1 (zh)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103037408B (zh) * 2011-09-30 2015-12-16 华为终端有限公司 Ip业务流的切换方法、终端以及相应的功能实体
CN103297964B (zh) * 2012-02-24 2018-07-13 中兴通讯股份有限公司 资源接纳控制方法、bng和pdp
US9479443B2 (en) * 2014-05-16 2016-10-25 Cisco Technology, Inc. System and method for transporting information to services in a network environment
CN107343294B (zh) * 2016-04-29 2022-08-02 中兴通讯股份有限公司 背景数据传输策略配置方法及装置
CN107333338B (zh) * 2016-04-29 2020-02-21 中国电信股份有限公司 基于lipa的动态承载策略控制方法、装置和通信网络
CN109429272B (zh) 2017-08-31 2022-02-11 华为技术有限公司 一种漫游场景下的分流方法及相关设备
CN114423026A (zh) * 2019-02-18 2022-04-29 华为技术有限公司 通信方法、装置及系统
CN112333802A (zh) * 2020-11-25 2021-02-05 吉视传媒股份有限公司 一种用于无线通讯设备的跨网络切换系统
CN115915047A (zh) * 2021-08-04 2023-04-04 展讯通信（上海）有限公司 通信方法、电子设备和存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003085901A1 (en) * 2002-04-04 2003-10-16 Siemens Aktiengesellschaft Methods and devices for controlling data transmission policies in at least one telecommunication network
CN101150863A (zh) * 2007-10-23 2008-03-26 中兴通讯股份有限公司 微波接入全球互通系统中的业务计费方法
CN101483847A (zh) * 2008-01-07 2009-07-15 华为技术有限公司 实现策略控制的方法、装置及系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101262441B (zh) * 2008-04-29 2011-11-30 中兴通讯股份有限公司 一种资源接纳控制平台间的协同方法与系统
CN101291458B (zh) * 2008-06-06 2012-03-07 中兴通讯股份有限公司 一种系统间切换时保证服务质量连续性的方法
CN101431420B (zh) * 2008-11-25 2011-07-13 中兴通讯股份有限公司 策略和计费控制方法和系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003085901A1 (en) * 2002-04-04 2003-10-16 Siemens Aktiengesellschaft Methods and devices for controlling data transmission policies in at least one telecommunication network
CN101150863A (zh) * 2007-10-23 2008-03-26 中兴通讯股份有限公司 微波接入全球互通系统中的业务计费方法
CN101483847A (zh) * 2008-01-07 2009-07-15 华为技术有限公司 实现策略控制的方法、装置及系统

Also Published As

Publication number Publication date
CN102143530A (zh) 2011-08-03
CN102143530B (zh) 2016-04-13

Similar Documents

Publication Publication Date Title
WO2020177764A1 (zh) 数据传送的保障方法及通信设备
WO2011095025A1 (zh) 一种对移动用户本地接入的策略控制方法和系统
US9113436B2 (en) Method and system for information transmission
WO2008101392A1 (fr) Procédé de transmission de qualité de service lors de transfert entre systèmes et système de réseau et réseau de destination correspondants
WO2011124106A1 (zh) 一种策略计费控制方法、系统和装置
WO2015033580A1 (ja) 通信装置、制御装置、通信方法、制御方法およびプログラム
WO2012006909A1 (zh) 一种上报固网接入信息的方法及系统
WO2011085614A1 (zh) 在全业务融合网络中控制资源的方法和系统
WO2011006317A1 (zh) 删除家乡策略和计费规则功能冗余信息的方法及系统
WO2012065499A1 (zh) 一种实现服务质量控制的方法和系统
WO2011147074A1 (zh) 策略与计费控制的实现方法、系统及相应设备
WO2011029289A1 (zh) 漫游场景下承载控制模式的发送方法和系统
WO2012097676A1 (zh) 支持双栈的ip-can会话实现应用检测和控制的方法及系统
WO2011022893A1 (zh) 一种资源接纳控制系统间的交互方法和装置
CN102131240B (zh) 一种实现服务质量控制的方法及系统
WO2010078761A1 (zh) 基于多接入技术的策略计费控制方法、装置和系统
WO2014040552A1 (zh) 一种通知接入网位置信息的方法和系统
WO2012159321A1 (zh) 服务质量控制方法和设备
WO2010111944A1 (zh) 释放接入连接的方法、装置、策略控制实体及系统
CN102098653A (zh) 一种实现服务质量控制的方法及系统
WO2011088702A1 (zh) 在全业务融合网络中控制资源的方法和系统
WO2012028044A1 (zh) 一种ifom错误时的处理方法和系统
WO2014071790A1 (zh) 固网移动融合的策略控制方法、装置及系统
WO2015033579A1 (ja) 通信装置、制御装置、通信システム、通信方法、制御方法およびプログラム
CN103155637B (zh) 实现家庭基站回程网络服务质量控制的方法、设备及系统

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: 10845108

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10845108

Country of ref document: EP

Kind code of ref document: A1