WO2012062183A1 - 一种实现数据流服务质量和计费策略控制的方法及*** - Google Patents

一种实现数据流服务质量和计费策略控制的方法及*** Download PDF

Info

Publication number
WO2012062183A1
WO2012062183A1 PCT/CN2011/081775 CN2011081775W WO2012062183A1 WO 2012062183 A1 WO2012062183 A1 WO 2012062183A1 CN 2011081775 W CN2011081775 W CN 2011081775W WO 2012062183 A1 WO2012062183 A1 WO 2012062183A1
Authority
WO
WIPO (PCT)
Prior art keywords
policy
charging
local gateway
gateway
service
Prior art date
Application number
PCT/CN2011/081775
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 WO2012062183A1 publication Critical patent/WO2012062183A1/zh

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
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/62—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on trigger specification
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8022—Determining tariff or charge band
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing

Definitions

  • the present invention relates to a technology for implementing data flow quality of service and charging policy control in the field of mobile communications, and in particular to a method and system for implementing data flow service quality and charging policy control.
  • FIG. 1 shows a schematic structural diagram of an evolved packet domain system. As shown in FIG. 1, the entire EPS system is divided into two parts: a radio access network and a core network. In the core network, the home subscriber server (HSS), the Mobility Management Entity (MME), the Serving GPRS Support Node (SGSN), and the policy charging rule function (PCRF) are included. , Policy and Charging Rule Function ), S-GW (Serving Gateway), Packet Data Gateway (P-GW, PDN Gateway), and Packet Data Network (PDN). The following describes each part of the function in detail:
  • HSS home subscriber server
  • MME Mobility Management Entity
  • SGSN Serving GPRS Support Node
  • PCRF policy charging rule function
  • S-GW Serving Gateway
  • PDN Gateway Packet Data Gateway
  • PDN Gateway Packet Data Network
  • the home subscriber server is the permanent storage location of the subscriber's subscription data and is located on the home network to which the subscriber subscribes.
  • the mobility management entity is the location where the user subscription data is stored in the current network, responsible for terminal-to-network non-access layer signaling management, terminal security verification function, terminal mobility management, user idle mode tracking and paging. Management functions and bearer management.
  • the service GPRS support node is a service support point for GERAN and UTRAN users to access the core network. It is similar in function to the mobility management entity and is responsible for user location update, paging management, and bearer management.
  • the service gateway is a gateway from the core network to the wireless system, and is responsible for the user plane bearer of the terminal to the core network, the data buffer in the idle mode of the terminal, the function of initiating the service request by the network side, and the lawful interception and The packet data routing and forwarding function; the service gateway is responsible for counting the situation in which the user terminal uses the wireless network, and generates the CDRs of the terminal using the wireless network, and transmits the CDRs to the charging gateway.
  • the packet data gateway is a gateway of the evolved system and the external packet data network of the system. It is connected to the Internet and the packet data network, and is responsible for the Internet Protocol (IP) address allocation, charging function, and packet filtering of the terminal. , policy control and other functions.
  • IP Internet Protocol
  • the packet data network is the operator's IP service network, which provides IP services to users through the carrier's core network.
  • the policy charging rule function entity is a server in the evolution system responsible for providing rules for charging control, online credit control, threshold control, and quality of service (QoS) policies.
  • the radio access network is composed of an evolved base station (eNB, E-UTRAN NodeB) and a 3G radio network controller (RNC), which is mainly responsible for transmitting and receiving wireless signals, and communicating with the terminal through the air interface to manage the air interface. Radio resources, resource scheduling, access control.
  • eNB evolved base station
  • RNC 3G radio network controller
  • the above service GPRS support node is an upgraded SGSN, which can support the S4 interface with the service gateway and communicate with the mobility management unit using the GTPv2 protocol.
  • the PS domain network architecture is different from that of Figure 1.
  • the SGSN and the MME are connected by the Gn interface, and the GTPvl protocol is used for interworking.
  • the SGSN cannot connect to the serving gateway, and connects to the gateway GPRS support node (GGSN, Gateway GPRS Support Node) through the Gn interface to directly access the packet data network.
  • GGSN Gateway GPRS Support Node
  • a home base station (HNB, Home NodeB) or an evolved home base station (HeNB, Home eNodeN) is a type of small, low-power base station that is used as a dedicated resource for certain users and deployed in private places such as homes, groups, companies, or schools.
  • the main purpose is to provide users with higher service rates and reduce the cost of using high-rate services, while at the same time making up for the shortage of existing distributed cellular wireless communication systems.
  • the advantages of home base stations are affordability, convenience, low power output, plug and play, broadband access, use of single mode terminals, and more.
  • Home base stations can be used in third generation (3G, 3 Generation) or long term evolution (LTE,
  • a new network element that is, a home base station gateway
  • the main functions performed by the home base station gateway are: verifying the security of the home base station, and performing maintenance and management on the operation of the home base station, according to the operator's requirements.
  • Configure and control the home base station which is responsible for exchanging data information of the core network and the home base station.
  • 2 is a 3G home base station network architecture diagram.
  • the 3G home base station is connected to the home base station gateway through a newly defined Iuh interface, and the home base station gateway provides IuPS and IuCs interfaces to the core network packet domain and the circuit domain.
  • the home base station gateway For a 3G network, the home base station gateway must be deployed to shield the impact on the terminal and network side after the home base station is introduced.
  • the home base station gateway can be optionally deployed. Therefore, the LTE home base station and the core network are connected in two ways. One is that the home base station and the core network element are directly connected, and the other is the home base station through the gateway and the core network. The elements are connected, as shown in Figures 3 and 4.
  • the home base station gateway may not integrate the user plane function, and the user plane is directly established between the home base station and the core network user plane gateway, so that the user plane is flattened and the data transmission delay is reduced. , as shown in Figure 5.
  • the home base station can also support local IP access functions. Under the condition that the home base station has local IP access capability and the user subscribes to allow local IP access, the user can implement the user to the home network. Local access to IP devices or the Internet. Through the local access function, the Internet data service can be offloaded, the core network load can be reduced, and access to the home network device can be forwarded without the core network, and the data transmission is convenient and efficient.
  • the local IP access function can also be used on the macro cell. The main purpose is similar to that of the home base station, and more is applied to the scenario where the local IP accesses the Internet, in order to reduce the core network load.
  • Figure 6 and Figure 7 show the architecture for implementing the above-mentioned local access function.
  • the local access gateway serves as a local access network to an external network (such as the internet), and provides address allocation, charging, packet filtering, policy control, data offloading, and radio access network application (RANAP, Radios Access Network). Application Part) Functions such as message parsing, Network Address Translation (NAT), local IP access policy routing, and execution.
  • RANAP Radios Access Network
  • Application Part Functions such as message parsing, Network Address Translation (NAT), local IP access policy routing, and execution.
  • the network element can be deployed as an independent network element or an existing home base station or a home base station gateway.
  • the local access architecture or the access architecture without the home base station gateway, it can be implemented by the architecture of FIG.
  • the local gateway uses the method of listening data, and the local data stream is directly offloaded, and the core network data is ignored, that is, the actual path of the core network data is as shown in FIG. 7.
  • a tunnel is used between the local gateway and the core network gateway. All data, that is, core network data and local data, need to pass through the local gateway.
  • the local gateway directly offloads it; for core network data, the local gateway forwards the tunnel to the core network gateway by establishing a tunnel with the core network gateway.
  • the local gateway determines which data needs to be split according to different policies. According to different traffic distribution policies, it is possible that part of the data in a bearer or PDN connection needs to be sent out through the core network gateway, and part of it is offloaded through the local gateway.
  • the process of dynamically acquiring related policies by the core network gateway is shown in Figure 9.
  • the PCRF is used as the entity generated by the policy and the accounting rule, and the generated rule is sent to the gateway of the core network, and the related policy is controlled.
  • the enforcement point of the policy in the GPRS network is GGSN
  • the enforcement point of the policy in the EPC network is P-GW.
  • the GPRS network is taken as an example to illustrate how the policy is issued.
  • the EPC network is a similar process.
  • Step 901 The terminal initiates an activation PDP context request, and the non-access stratum message is sent to the SGSN via the base station.
  • Step 902 The SGSN selects a suitable core network gateway for the UE according to an access point (APN) provided by the UE.
  • the SGSN sends a PDP context request to the core network gateway, which carries parameters such as a UE identifier, a PDP type, QoS information, and charging information. If it is accessing the GPRS network, the core network gateway is the GGSN. If the EPC network is connected, the core network gateway refers to the S-GW and the P-GW.
  • the access network is different, the messages are different, but the effect is similar.
  • the description of accessing the GRPS network is taken as an example.
  • the core network gateway verifies the parameters carried in the PDP context request message and authorizes the QoS parameters carried in the request.
  • Step 903 The core network gateway sends an IP connection access network (IP-CAN) session establishment request to the PCRF, where the UE identifier information and/or the IP address of the UEr are carried.
  • IP-CAN IP connection access network
  • Step 904 to step 905, the PCRF obtains the subscription data of the user from the identifier description register (SPR, Subscriber Profile Register), and is used to formulate related rules.
  • SPR Subscriber Description Register
  • Step 906 The PCRF sends an IP-CAN session establishment response, where the policy and charging rules are included.
  • Step 907 The core network gateway returns a create PDP context response to the SGSN, where the tunnel end identifier, the authorized QoS parameter, and the like allocated for the UE are carried.
  • MSISDN mobile station international subscriber directory number
  • Step 909 If the base station accepts the QoS parameters sent by the core network gateway, the base station initiates a process of establishing a radio resource control (RRC) connection.
  • RRC radio resource control
  • Step 910 The base station returns a radio access bearer (RAB, Radio Access Bearer) assignment response message to the SGSN. If multiple bearers are established at the same time, the base station will return multiple RAN assignment response messages.
  • RAB Radio Access Bearer
  • Step 911 If the base station cannot accept the QoS parameter in the RAB assignment message, the SGSN is indicated in the returned RAN assignment response message. According to the indication, the SGSN may choose to deliver new QoS parameters.
  • Step 912 The SGSN determines whether to send an update PDP context request to the core network gateway according to whether to establish a direct tunnel, and if it is sent, carries the tunnel end identifier of the base station. If the QoS is inconsistent with the QoS delivered by the previous core network gateway, the SGSN notifies the core network gateway through the PDP update process.
  • Step 913 The SGSN returns an Activate PDP Context Response message to the UE.
  • the quality of service and charging policies used by the local gateway can only be implemented through local configuration. How to enable the carrier to configure the local offloading policy more flexibly, and how to dynamically configure the local shunting policy is a technical problem that needs to be solved. Summary of the invention
  • the present invention provides a method for implementing data flow service quality and charging policy control to improve system service performance.
  • a method for implementing data flow service quality and charging policy control including:
  • the local gateway determines the data stream to be offloaded
  • the identifier of the offloaded data stream is notified to a policy charging rule function (PCRF)
  • PCRF policy charging rule function
  • the method also includes:
  • the policy charging rule function is established in the network connection of the same user by the local gateway.
  • a session association relationship is established between the access network session and the access network session established by the core network gateway.
  • the method also includes:
  • the policy charging rule function when the QoS policy and/or the charging policy rule allocated for the offloaded data flow changes, according to the session association relationship related to the offloaded data flow to the core network gateway and the The local gateway delivers the updated quality of service policy and/or charging policy rule.
  • the step of the local gateway determining the data flow to be offloaded includes:
  • the local gateway intercepts the bearer assignment request sent by the mobility management unit to the base station, and determines, according to the information carried in the bearer assignment request, that data is to be offloaded; or
  • the local gateway intercepts the bearer assignment response sent by the base station to the mobility management unit, and determines that data splitting is to be performed according to the information carried in the bearer assignment response.
  • the step of the local gateway determining the data flow to be offloaded includes:
  • the mobility management unit selects the local gateway through which the terminal is selected, and after the local gateway receives the request for creating a packet data protocol context issued by the mobility management unit, the packet data protocol is created according to the method.
  • the information carried in the context request determines that data is to be offloaded; or,
  • the local gateway selects a core network gateway to be accessed by the user, and the local gateway determines to perform data offloading after receiving the request to create a packet data protocol context request sent by the core network gateway.
  • the step of the policy charging rule function sending the updated QoS policy and/or the charging policy rule to the local gateway includes:
  • the user notifies the service data flow identifier that is modified by the policy charging rule function by using the core network gateway, and the policy charging rule function determines, according to the modified service data flow identifier, that the policy on the local gateway needs to be modified,
  • the local gateway delivers the updated quality of service policy and/or charging policy rule.
  • the step of the policy charging rule function sending the updated QoS policy and/or the charging policy rule to the local gateway includes:
  • the local gateway is determined according to the affected packet data network connection and/or the service data flow.
  • the updated quality of service policy and/or charging policy rule is delivered to the local gateway.
  • the step of the policy charging rule function sending the updated QoS policy and/or the charging policy rule to the local gateway includes:
  • the local gateway After the local gateway intercepts the modified bearer information sent by the base station to the core network, and determines that the service data flow needs to be modified according to the bearer information, the local service gateway notifies the modified service data flow identifier to the policy charging rule function. And the policy charging rule function updates the quality of service policy and/or the charging policy rule, and sends the updated quality of service policy and/or charging policy rule to the local gateway.
  • a system for implementing data flow quality of service and charging policy control comprising a local gateway and a policy charging rule function (PCRF), wherein
  • PCRF policy charging rule function
  • the local gateway is configured to: after determining the data flow to be offloaded, notifying the identifier of the offloaded data flow to the policy charging rule function;
  • the policy charging rule function is configured to: provide the local gateway with a quality of service policy and/or a charging policy rule for the offloaded data flow.
  • the policy charging rule function is further configured to:
  • the local gateway is configured to determine a data flow to be offloaded according to one of the following manners:
  • the bearer assignment response sent by the base station to the mobility management unit is intercepted, and data offloading is determined according to the information carried in the bearer assignment response.
  • the local gateway is configured to determine data to be offloaded according to one of the following manners. After the terminal accesses the core network, after receiving the request to create a packet data protocol context issued by the mobility management unit, determining, according to the information carried in the context information request of the created packet data protocol, that data is to be offloaded; or
  • the user selects the core network gateway to be accessed, and after receiving the request to create a packet data protocol context request sent by the core network gateway, it is determined that data is to be offloaded.
  • the policy charging rule function is configured to deliver the updated quality of service policy and/or charging policy rule to the local gateway in the following manner:
  • the policy charging rule function is configured to deliver the updated quality of service policy and/or charging policy rule to the local gateway in the following manner:
  • the policy on the local gateway needs to be modified according to the affected packet data network connection and/or the service data flow, and the update is sent to the local gateway.
  • the local gateway is further configured to:
  • the intercepting terminal After the intercepting terminal sends the modified bearer information to the core network, the intercepting terminal, according to the bearer information, determines that the modified service data stream needs to be modified, and the modified service data stream identifier is notified to the policy charging rule function;
  • the policy charging rule function is further configured to: update a quality of service policy and/or a charging policy rule, and send the updated quality of service policy and/or charging policy rule to the local gateway.
  • BRIEF abstract 1 is a schematic structural diagram of an evolved packet domain system
  • FIG. 2 is a schematic diagram of a 3G home base station network architecture
  • FIG. 3 is a schematic diagram of a network architecture of an LTE home base station
  • FIG. 4 is a schematic diagram of a network architecture of an LTE home base station
  • Figure 5 is a third schematic diagram of the LTE home base station network architecture
  • FIG. 6 is a schematic diagram of a network architecture for implementing local access
  • FIG. 7 is a schematic diagram of a network architecture for implementing local access
  • FIG. 8 is a schematic diagram of a network architecture for implementing local access
  • Figure 9 is a schematic flow chart of a dynamic acquisition strategy
  • FIG. 12 is a first embodiment of implementing a policy modification in an embodiment of the present invention.
  • FIG. 13 is a second embodiment of implementing a policy modification in an embodiment of the present invention.
  • FIG. 14 is a third implementation manner of implementing policy modification in an embodiment of the present invention. Preferred embodiment of the invention
  • the system for implementing data flow quality of service and charging policy control includes a local gateway and a policy charging rule function (PCRF).
  • PCRF policy charging rule function
  • the local gateway is configured to: notify the function of the offloaded data stream to notify the policy charging rule function after the offloaded data stream to be transmitted locally;
  • the policy charging rule function is configured to: provide the local gateway with a quality of service policy and/or a charging policy rule for the offloaded data flow.
  • the policy charging rule function is further configured to: establish a session association relationship between the connection access network session established by the local gateway in the network connection of the same user and the access network session established by the core network gateway; and the offloaded data flow of the user
  • the assigned quality of service policy and/or charging policy rule changes, according to the session association relationship of the access network session related to the offloaded data flow to the core network gateway and
  • the local gateway delivers the updated quality of service policy and/or charging policy rules.
  • the local gateway is configured to determine a data flow to be offloaded according to one of the following manners: intercepting a bearer assignment request sent by the mobility management unit to the base station, and determining, according to the information carried by the bearer assignment request, to perform data offloading; Or,
  • the bearer assignment response sent by the base station to the mobility management unit is intercepted, and the data shunting is determined according to the information carried by the bearer assignment response.
  • the local gateway is further configured to: when the terminal accesses the core network, after receiving the request to create a packet data protocol context sent by the mobility management unit, determine, according to the information carried in the request to create a packet data protocol context request, to perform data Alternatively, the user selects a core network gateway to access, and after receiving the context of creating a packet data protocol sent by the core network gateway, it determines that data is to be offloaded.
  • the policy charging rule function is configured to deliver the updated QoS policy and/or charging policy rule to the local gateway in the following manner. :
  • the modified service data flow identifier After receiving the modified service data flow identifier that is notified by the core network gateway to the policy charging rule function, after the modified service data flow identifier is used, it is determined that the policy on the local gateway needs to be modified, and the update is sent to the local gateway. Quality of Service Policy and / or Billing Policy Rules.
  • the policy charging rule function is configured to deliver the updated QoS policy and/or charging policy rule to the local gateway in the following manner. After the query or the QoS policy and/or the accounting policy rule are changed, the updated service is delivered to the local gateway when the policy on the local gateway needs to be modified according to the affected packet data network connection and/or the service data flow. Quality policy and / or billing strategy rules.
  • the local gateway is further configured to: after the intercepting terminal sends the modified bearer information to the core network by using the base station, and determines, according to the bearer information, that the service data flow needs to be modified, the modified service data flow identifier is notified to the policy charging rule function;
  • the policy charging rule function is further configured to: update the quality of service policy and/or the charging policy rule, and send the updated quality of service policy and/or charging policy rule to the local gateway.
  • the method for implementing the data flow service quality and the charging policy control includes: the local gateway determining, after the offloaded data stream to be locally transmitted, notifying the identifier of the offloaded data flow to the policy charging rule function, where the policy charging rule function is The local gateway provides quality of service policies and/or charging policy rules for offloaded data flows.
  • the policy charging rule function establishes a session association relationship between the connection access network session established by the local gateway in the network connection of the same user and the access network session established by the core network gateway.
  • the policy charging rule function when the QoS policy and/or the charging policy rule allocated for the user's offloaded data flow changes, according to the session association relationship of the access network session related to the offloaded data flow to the core network
  • the gateway and the local gateway deliver the updated quality of service policy and/or charging policy rules.
  • Figure 10 depicts an implementation mode 1 for implementing a local gateway acquisition policy.
  • the manner in which the local gateway determines the data stream to be offloaded is: the local gateway intercepts the bearer assignment request sent by the mobility management unit to the base station, and determines, according to the information carried by the bearer assignment request, that data is to be performed.
  • the local gateway intercepts the bearer assignment response sent by the base station to the mobility management unit, and determines that data splitting is to be performed according to the information carried in the bearer assignment response.
  • This embodiment is directed to the routing method described in FIG.
  • Step 1001 The terminal initiates an activation PDP context request, and the non-access stratum message is sent to the MME via the base station.
  • the mobility management unit is a high-level description of the mobility management entity (MME) and the SGSN.
  • MME mobility management entity
  • the message in this embodiment is described by taking GERAN/UTRAN access to the GRPS network as an example.
  • the mobile management unit is the SGSN.
  • Step 1002 The SGSN selects a suitable core network gateway for the UE according to the APN provided by the UE.
  • the SGSN sends a PDP context request to the core network gateway, which carries parameters such as a UE identifier, a PDP type, QoS information, and charging information. If it is accessing the GPRS network, the core network gateway is the GGSN. If the EPC network is connected, the core network gateway refers to the S-GW and the P-GW.
  • the access network is unreachable and the messages are different, but the effect is similar.
  • the description of accessing the GRPS network is taken as an example.
  • steps 1002, 1007 are to create a session request/response, and step 1017 is to modify the bearer process and does not support QoS negotiation.
  • the above processes are all well known to those skilled in the art and are not mentioned here.
  • the core network gateway verifies the parameters carried in the PDP context request message and authorizes the QoS parameters carried in the request.
  • Step 1003 The core network gateway sends an IP-CAN session establishment request to the PCRF, where the UE identifier information and/or the UE IP address are carried.
  • Step 1004 to step 1005 the PCRF obtains the user's subscription data from the SPR, and uses it to formulate related rules.
  • Step 1006 the PCRF sends an IP-CAN session setup response, which includes policies and charging rules.
  • Step 1007 The core network gateway returns a Create PDP Context Response to the SGSN, where the tunnel end identifier, the authorized QoS parameter, and the like allocated for the UE are carried.
  • Step 1008 The SGSN sends a bearer assignment request to the base station, where the MSISDN number, APN, and QoS parameters of the UE are carried.
  • the bearer assignment request message also includes the IP address of the user and the currently established PDN connection identifier information.
  • the PDN connection identification information may be APN information or a bearer identifier.
  • Step 1009 The local gateway intercepts the RAB assignment request sent by the SGSN, and determines, according to the operator policy judgment and the MSISDN, APN, and charging feature information included in the RAB assignment message, whether all bearers, or some of the bearers, will be The data is shunted.
  • Step 1010 The local gateway sends an IP-CAN session establishment or an IP-CAN session modification request to the PCRF, where the service data flow identifier of the offload and one or more of the following information are carried: UE Identification information, UE IP address, APN, bearer identity.
  • UE Identification information UE IP address
  • APN APN
  • bearer identity The identifier information of the UE, the IP address information of the UE, the APN, and the bearer identifier are consistent with the information carried in step 1009.
  • Step 1011 The PCRF associates the IP-CAN session established by the core network with the IP-CAN session established by the local gateway, that is, establishes an association relationship.
  • Step 1012 The PCRF generates a corresponding charging and quality of service policy according to the service data flow identifier in step 1010, and sends the response message to the local gateway through the IP-CAN session establishment response message.
  • Step 1013 The local gateway sends an RAB dominating message to the base station.
  • Step 1014 If the base station accepts the QoS parameters sent by the core network gateway, the base station initiates an RRC connection establishment process.
  • Step 1015 1016 The base station returns an RAB assignment response message to the SGSN. If multiple bearers are established at the same time, the base station will return multiple RAN assignment response messages.
  • the base station If the base station is unable to accept the QoS parameters in the RAB Assignment message, it is indicated to the SGSN in the returned RAN Assignment Response message. According to the indication, the SGSN may choose to deliver new QoS parameters.
  • the SGSN determines whether to send an update PDP context request to the core network gateway according to whether a direct tunnel is established, and if it is sent, carries the tunnel end identifier of the base station. If the QoS is inconsistent with the QoS delivered by the previous core network gateway, the SGSN updates the process core network gateway through the PDP context.
  • Step 1018 The SGSN returns an Activate PDP Context Response message to the UE.
  • step 1009 1012 may be performed before step 1016 after step 1015.
  • the process is applicable to the PDP activation, the secondary PDP activation initiated by the UE in the UTRAN/GERAN, the network initiated PDP and the secondary PDP activation procedure. It is also applicable to the PDN connection establishment initiated by the UE in the EUTRAN, the ATTACH procedure, the request resource modification or allocation procedure initiated by the UE, and the bearer activation procedure initiated by the network.
  • Figure 11 depicts an implementation 2 of implementing a local gateway acquisition policy.
  • the mobility management unit selects the local gateway through which the terminal passes, and the local gateway receives the Create Packet Data Protocol (PDP) context request sent by the mobility management unit. After that, according to the information carried in the creation of the packet data protocol context request, it is determined that data is to be offloaded.
  • the local gateway selects a core network gateway to be accessed by the user, and the local gateway determines to perform data offloading after receiving the request to create a packet data protocol context request sent by the core network gateway.
  • PDP Packet Data Protocol
  • This embodiment is directed to the routing method described in FIG.
  • Step 1101 The terminal initiates an activation PDP context request, and the non-access stratum message is sent to the SGSN via the base station.
  • the mobility management unit is a higher description of the mobility management entity (MME) and the SGSN.
  • MME mobility management entity
  • the message in this embodiment is described by taking GERAN/UTRAN access GRPS network as an example.
  • Step 1102 The SGSN selects a suitable local gateway for the UE according to the APN provided by the UE.
  • the SGSN sends a PDP context request to the local gateway, which carries parameters such as a UE identifier, a PDP type, QoS information, charging information, and a tunnel end identifier.
  • Step 1103 The local gateway sends a PDP context request to the core network gateway, where the request is carried. It carries parameters such as UE identity, PDP type, QoS information, charging information, and tunnel end identifier.
  • the core network gateway is the GGSN. If the EPC network is connected, the core network gateway refers to the S-GW and the P-GW. The access network is different, the message is different, but the effect is similar. Here, the description of accessing the GRPS network is taken as an example. If the core network gateway is an S-GW and a P-GW, steps 1102, 1103, 1108, and 1113 are to create a session request/response, and step 1117 is to modify the bearer process and does not support QoS negotiation. The above processes are all well known to those skilled in the art and are not mentioned here.
  • the core network gateway verifies the parameters carried in the PDP context request message.
  • Step 1104 The core network gateway sends an IP-CAN session establishment request to the PCRF, where
  • UE identification information and/or UE IP address.
  • Step 1105 to step 1106, the PCRF obtains the user's subscription data from the SPR, and uses it to formulate related rules.
  • Step 1107 the PCRF sends an IP-CAN session setup response, which includes policies and charging rules.
  • Step 1108 The core network gateway returns a PDP context response to the local gateway, where the tunnel end identifier, the authorized QoS parameter, and the like are allocated.
  • Step 1109 Determine, according to the operator policy, whether all bearers, or some of the bearers, will be The data is shunted.
  • step 1109 can be performed between steps 1102 and 1103.
  • Step 1110 The local gateway sends an IP-CAN session establishment or an IP-CAN session modification request to the PCRF, where the service data flow identifier of the offload and one or more of the following information are carried: UE identification information, UE IP address, APN, bearer Logo.
  • UE identification information UE IP address
  • APN APN
  • bearer Logo The identity information of the UE, the IP address of the UE, the APN, and the bearer identifier are consistent with the information carried in step 1109.
  • Step 1111 The PCRF associates the IP-CAN session established by the core network with the IP-CAN established by the local gateway, that is, establishes an association relationship.
  • Step 1112 The PCRF generates a corresponding charging and quality of service policy according to the service data flow identifier in step 1110, and sends the response message to the local gateway through the IP-CAN session establishment response message.
  • step 1110 and step 1112 may be performed before step 2 after step 2. If steps 1110 and 1112 are performed first, then step 1111 is performed prior to step 1107 and after step 1107.
  • Step 1113 The local gateway returns a PDP context response to the SGSN, where the tunnel end identifier, the authorized QoS parameter, and the like are allocated.
  • Step 1114 The local gateway sends a RAB dominating message to the base station.
  • Step 1115 If the base station accepts the QoS parameters sent by the core network gateway, the base station initiates an RRC connection establishment process.
  • Step 1116 1117 the base station returns an RAB assignment response message to the SGSN. If multiple bearers are established at the same time, the base station will return multiple RAN assignment response messages.
  • the base station If the base station is unable to accept the QoS parameters in the RAB Assignment message, it is indicated to the SGSN in the returned RAN Assignment Response message. According to the indication, the SGSN may choose to deliver new QoS parameters.
  • Step 1118 The SGSN determines whether to send an update PDP context request to the core network gateway according to whether a direct tunnel is established, and if it is sent, carries the tunnel end identifier of the base station. If the QoS is inconsistent with the QoS delivered by the previous core network gateway, the SGSN updates the process core network gateway through the PDP context.
  • Step 1119 The SGSN returns an Activate PDP Context Response message to the UE.
  • the process is applicable to the PDP activation initiated by the UE in UTRAN/GERAN, the secondary PDP activation, the network initiated PDP and the secondary PDP activation procedure. It is also applicable to the PDN connection establishment initiated by the UE in the EUTRAN, the ATTACH procedure, the request resource modification or allocation procedure initiated by the UE, and the network initiated bearer activation procedure.
  • Figure 12 depicts an implementation mode 1 for implementing local gateway policy modification.
  • the policy charging rule function delivers the updated QoS policy and/or the charging policy rule to the local gateway, the following is implemented:
  • the user notifies the policy data flow identifier by the policy of the policy charging rule through the core network gateway, the policy
  • the charging rule function sends the updated service quality policy and/or the charging policy rule to the local gateway when the policy of the local gateway needs to be modified according to the modified service data flow identifier.
  • Step 1201 The UE initiates a PDP modification request or a resource allocation request or a resource modification request to the core network. If the UE accesses from the GERAN/UTRAN, the UE initiates a PDP modification request. If the UE accesses from the EUTRAN, the UE initiates a resource allocation request, or a resource modification request.
  • Step 1202 The core network gateway sends an IP-CAN session modification request to the PCRF, where the modified service data flow identifier and one or more UE identification information of the following parameters are carried: the UE IP address, the APN, and the 7?
  • Step 1203 The PCRF determines, according to the modified service data flow identifier, whether to modify the policy information on the local gateway. It is assumed here that the judgment is yes.
  • Step 1204 The PCRF sends an update service quality and charging policy request to the local gateway, where the modified service data flow identifier and the identified service quality and charging policy and one or more of the following parameters are carried: the UE identifier, and or UE IP address, and or APN, and or 7 logo.
  • step 1205 the local gateway sends an updated service quality and charging policy response to the CPRF.
  • Step 1206 The PCRF sends an IP-CAN session modification response to the core network gateway, where the modified service data flow identifier identifies the service quality and the charging policy and one or more of the following parameters: the UE identifier, the UE IP address, APN, with the logo.
  • Step 1207 the PDP modification, or the remaining process of resource allocation or resource modification is completed, and the process is a technology well known to those skilled in the art, and details are not described herein.
  • Figure 13 depicts an implementation second that implements local gateway policy tampering.
  • the mobility management unit selects the local gateway through which the terminal is selected, and when the policy charging rule function delivers the updated QoS policy and/or the charging policy rule to the local gateway, according to the following manner Implementation: After the policy charging rule function queries or learns that the quality of service policy and/or the charging policy rule is changed, according to the affected packet data network connection and/or service data flow, when the policy on the local gateway needs to be modified, the local gateway is The updated quality of service policy and/or charging policy rules are issued.
  • step 1301 the quality of service and or the charging policy changes, for example, an AF trigger, or a user subscription change causes the SPR to be triggered.
  • the PCRF determines whether it needs to notify the local gateway and the core network gateway. The judgment here is yes.
  • Step 1302 The PCRF sends an update service quality and charging policy request to the core network gateway, where the affected service data flow and the modified quality of service and or charging policy and one or more UE identification information of the following parameters are carried. , UE IP address, ⁇ , bearer ID.
  • Step 1303 The core network gateway sends an updated service quality and charging policy response to the PCRF.
  • Step 1305 The local gateway sends an updated service quality and charging policy response to the PCRF.
  • step 1306 the PDP activation/PDP modification/PDP deactivation is performed, or the activation/bearer modification/bearer deactivation process is performed.
  • the process is a technology well known to those skilled in the art, and details are not described herein.
  • Figure 14 depicts an implementation third implementation of local gateway policy modification.
  • the policy charging rule function sends the updated QoS policy and/or the charging policy rule to the local gateway, the following is implemented: After the local gateway intercepts the terminal to send the modified bearer information to the core network, the bearer information is obtained according to the bearer information. When it is determined that the service data flow needs to be modified, the modified service data flow identifier is notified to the policy charging rule function, and the policy charging rule function updates the service quality policy and/or the charging policy rule, and sends the updated service quality to the local gateway. Policy and/or billing policy rules.
  • Step 1401 The UE initiates a PDP modification request, or a resource allocation request or a resource modification request. If the UE accesses from GERAN/UTRAN, the UE initiates a PDP modification request. If UE Upon access from the EUTRAN, the UE initiates a resource allocation request, or a resource modification request. Step 1402: If the architecture of FIG. 7 is used, the local gateway intercepts the PDP modification request sent by the base station to the mobility management unit, or the resource allocation request or the resource modification request. If the architecture of Figure 8 is used, the mobility management unit sends a PDP modification request or a bearer modification request to the local gateway.
  • the local gateway determines whether the modified bearer has an impact on the offload data, and assumes that the judgment is yes.
  • Step 1403 The local gateway sends an IP-CAN session modification request to the PCRF, where the modified service data flow identifier and one or more of the following information are carried: the UE identification information, the UE IP address, the APN, and the 7?
  • Step 1404 The PCRF sends an IP-CAN session modification response to the local gateway, where the UE identifier, and or the UE IP address, and or APN, and or?
  • the identification, and the tampering service data flow identify the identified quality of service and charging policy.
  • Step 1405 the PDP modification, or the remaining process of resource allocation or resource modification is completed, and the process is a technology well known to those skilled in the art, and details are not described herein.
  • the base station type that is, the home base station or the ordinary base station, is not limited in the above embodiments.
  • the base station is taken as an example, and the impact on the home base station is the same.
  • Embodiments may be applicable to the case where UTRAN/GERAN accesses a GPRS or EPC network, or an EPC network accessed by EUTRAN.
  • the home base station/base station is HNB/RNC.
  • the core network gateway refers to the GGSN/P-GW located in the core network, and the network element has nothing to do with the present invention, and is not limited herein.
  • the home base station/base station refers to the HeNB/eNB
  • the core network gateway refers to the S-GW/P-GW located in the core network.
  • the local gateway may be a data offload function (TOF) entity or a NAT gateway or an L-GW, but the implementation functions are similar.
  • TOF data offload function
  • the home base station there may be a home base station gateway in the network. If there is a home base station gateway, the messages between all the home base stations and the mobility management unit need to pass through the home base station gateway. The message between the home base station and the local gateway may be through the home base station gateway or not through the home base station gateway.
  • the home base station gateway transparently transmits the passed message, and the transparent transmission process has nothing to do with the present invention, and no comment is made here.
  • the message of the embodiment is based on the GERAN/UTRAN accessing the GRPS network.
  • the content of the invention is consistent, and is not mentioned here.
  • the foregoing technical solution can flexibly control the service quality and charging policy of the data flow of the local gateway, and improve system service performance. Therefore, the present invention has strong industrial applicability.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种实现数据流服务质量和计费策略控制的方法和***，该方法包括：本地网关确定需分流的数据流后将所述分流数据流的标识通知给策略计费规则功能，所述策略计费规则功能向所述本地网关提供针对所述分流数据流的服务质量策略和/或计费策略规则。上述技术方案可以对本地网关的数据流的服务质量和计费策略进行灵活控制，提高***服务性能。

Description

一种实现数据流服务质量和计费策略控制的方法及***
技术领域
本发明涉及移动通信领域中的实现数据流服务质量和计费策略控制的技 术， 具体涉及一种实现数据流服务质量和计费策略控制的方法及***。
背景技术
为了保持第三代移动通信***在通信领域的竟争力， 为用户提供速率更 快、 时延更低、 更加个性化的移动通信服务， 同时， 降低运营商的运营成本， 第三代合作伙伴计划 （3GPP, 3rd Generation Partnership Project )标准工作组 正致力于演进分组***（EPS, Evolved Packet System ) 的研究。 图 1示出了 演进分组域***的结构示意图， 如图 1所示， 整个 EPS***分为无线接入网 和核心网两部分。在核心网中，包含了归属用户服务器（ HSS, Home Subscriber Server )、移动性管理实体（MME, Mobility Management Entity )、服务 GPRS 支持节点（SGSN, Serving GPRS Support Node ) , 策略计费规则功能（ PCRF, Policy and Charging Rule Function ) 、 月良务网关 ( S-GW, Serving Gateway ) 、 分组数据网关 （ P-GW, PDN Gateway )和分组数据网络（ PDN, Packet Data Network ) 。 下面详细介绍各部分功能：
归属用户服务器， 是用户签约数据的永久存放地点， 位于用户签约的归 属网。
移动性管理实体， 是用户签约数据在当前网络的存放地点， 负责终端到 网络的非接入层信令管理、 终端的安全验证功能、 终端的移动性管理、 用户 空闲模式下的跟踪和寻呼管理功能和承载管理。
服务 GPRS支持节点， 是 GERAN和 UTRAN用户接入核心网络的业务 支持点， 功能上与移动性管理实体类似， 负责用户的位置更新、 寻呼管理和 承载管理等功能。
服务网关， 是核心网到无线***的网关， 负责终端到核心网的用户面承 载、 终端空闲模式下的数据緩存、 网络侧发起业务请求的功能、 合法监听和 分组数据路由和转发功能； 服务网关负责统计用户终端使用无线网的情况， 并产生终端使用无线网的话单， 传送给计费网关。
分组数据网关， 是演进***和该***外部分组数据网络的网关， 它连接 到因特网和分组数据网络上， 负责终端的互联网协议（ Internet Protocol , 简称 为 IP )地址分配、 计费功能、 分组包过滤、 策略控制等功能。
分组数据网络， 是运营商的 IP业务网络， 该网络通过运营商的核心网为 用户提供 IP服务。
策略计费规则功能实体， 是演进***中负责提供计费控制、 在线信用控 制、 门限控制、 服务质量（QoS, Quality of Service )策略方面规则的服务器。
无线接入网， 是由演进基站（eNB, E-UTRAN NodeB )和 3G无线网络 控制器（RNC, Radio Network Control )组成， 它主要负责无线信号的收发， 通过空中接口和终端联系， 管理空中接口的无线资源、 资源调度、 接入控制。
上述服务 GPRS支持节点是升级过的 SGSN, 能够支持与服务网关之间 的 S4接口， 并与移动性管理单元之间釆用 GTPv2协议进行互通。 而对于支 持 3G核心网的 SGSN来说 PS域网络架构与图 1有所不同。 此时 SGSN与 MME釆用 Gn接口相连，互通釆用 GTPvl协议。 SGSN不能与服务网关相连， 通过 Gn接口连接到网关 GPRS支持节点 （GGSN, Gateway GPRS Support Node )直接进行分组数据网络访问。
家用基站 （HNB, Home NodeB )或者演进的家用基站 （HeNB, Home eNodeN )是一类小型、 低功率的基站， 作为某些用户的专属资源， 部署在家 庭、 团体、 公司或者学校等私人场所使用， 主要是为了给用户提供更高的业 务速率并降低使用高速率服务所需要的费用， 同时弥补已有分布式蜂窝无线 通信***覆盖的不足。 家用基站的优点是实惠、 便捷、 低功率输出、 即插即 用、 宽带接入、 使用单模终端等。
家用基站可以应用在第三代（3G, 3 Generation )或者长期演进（LTE,
Long Term Evolution )移动通信网络中。 为了便于对家用基站进行管理， 在网 络中引入了一个新网元， 即家用基站网关。 家用基站网关主要执行的功能为： 验证家用基站的安全性， 对家用基站的运行进行维护管理， 根据运营商要求 配置和控制家用基站， 负责交换核心网和家用基站的数据信息。 图 2是 3G 家用基站网络架构图， 3G家用基站通过新定义的 Iuh接口连接至家用基站网 关， 家用基站网关提供到核心网分组域和电路域的 IuPS和 IuCs接口。 对于 3G 网络来说家用基站网关必选部署用来屏蔽引入家用基站后对终端和网络 侧的影响。对于 LTE网络来说家用基站网关可选部署， 因此 LTE家用基站和 核心网连接有两种方式， 一种是家用基站和核心网网元直接相连， 另一种是 家用基站通过网关和核心网网元相连， 如图 3和 4所示。 对于图 4所示引入 家用基站网关的场景， 家用基站网关可以不集成用户面功能， 家用基站和核 心网用户面网关间直接建立用户面， 这样可以使用户面扁平化， 数据传输时 延减小， 如图 5所示。
家用基站除了支持通过移动核心网络的接入之外，还可以支持本地 IP接 入功能， 在家用基站具备本地 IP接入能力并且用户签约允许本地 IP访问的 条件下， 可以实现用户对家庭网络其他 IP设备或者互联网络的本地接入。 通 过本地接入功能， 可以实现 Internet数据业务的分流， 降低核心网负荷， 并且 对于家庭网络设备的访问可以不通过核心网来进行转发，数据传输便捷高效。 本地 IP接入功能在宏蜂窝上也可以使用， 主要用途和家用基站类似， 更多的 是应用在本地 IP接入 Internet这种场景， 目的是降低核心网负荷。 图 6和图 7 分别给出了实现上述本地接入功能的架构， 主要差别体现在是否存在家用基 站网关。 其中， 本地接入网关作为本地接入到外部网络（例如 internet ) 的网 络， 提供地址分配、 计费、 分组包过滤、 策略控制、 数据分流功能、 无线接 入网应用部分 ( RANAP , Radios Access Network Application Part ) 消息解析、 网络地址转换（NAT, Network Address Translation ) 、 本地 IP访问策略路由 和执行等功能。 该网元作为一个逻辑单元在实际部署的时候可以作为独立存 在的网元也可以和现有的家用基站或者家用基站网关联合部署。 对于宏蜂窝 实现本地接入架构， 或者没有家用基站网关的接入架构， 可以通过图 7的架 构实现。 在部署了本地网关的以后， 如果用户同时还有核心网数据， 则有核 心网数据的路由方式有两种， 分别如图 7和图 8所示。 主要差别在于本地网 关如何处理核心网数据。 图 7的架构中， 本地网关釆用监听数据的方式， 对 于本地数据流直接分流出去， 而对核心网数据忽略， 即核心网数据的实际路 径如图 7所示。 图 8的架构中， 本地网关和核心网网关之间釆用隧道的方式。 所有数据， 即核心网数据和本地数据都需要经过本地网关， 对于本地数据， 本地网关直接将其分流； 对于核心网数据， 本地网关通过建立与核心网网关 的隧道转发给核心网网关。
当用户接入网络中， 本地网关根据不同的策略决定哪些数据需要分流出 去。根据不同的分流策略， 可能某个承载或者 PDN连接中的数据一部分是需 要通过核心网网关发送出去的， 一部分通过本地网关分流出去。
核心网网关动态获取相关策略的流程如图 9所示。 PCRF作为策略和计费 规则生成的实体， 将生成的规则下发给核心网的网关， 由其执行相关策略的 控制。 在 GPRS网络中策略的执行点为 GGSN, 而在 EPC网络中策略的执行 点为 P-GW。 这里以 GPRS网络为例说明策略如何下发， EPC网络是类似的 过程。
步骤 901 , 终端发起激活 PDP上下文请求， 此非接入层消息经由基站发 送至 SGSN。
步骤 902, SGSN根据 UE提供的接入点 （APN ) , 为 UE选择一个合适 的核心网网关。 SGSN向核心网网关发送创建 PDP上下文请求，其中携带 UE 标识， PDP类型， QoS信息， 计费信息等参数。 如果是接入 GPRS网络， 则 核心网网关为 GGSN, 如果接入 EPC 网络， 则核心网网关指的是 S-GW和 P-GW。 接入的网络不同， 消息有所不同， 但是作用类似， 这里以接入 GRPS 网络的描述为例。
核心网网关对创建 PDP上下文请求消息中携带的参数进行验证， 并对请 求中携带的 QoS参数进行授权。
步骤 903 , 核心网网关向 PCRF发送 IP连接访问网络（ IP-CAN )会话 建立请求， 其中携带 UE标识信息和 /或 UEr的 IP地址。
步骤 904〜步骤 905, PCRF从标识描述寄存器（ SPR, Subscriber Profile Register )获取用户的签约数据， 用于制定相关规则。
步骤 906 , PCRF发送 IP-CAN会话建立响应，其中包含策略和计费规则。 步骤 907, 核心网网关向 SGSN返回创建 PDP上下文响应， 其中携带为 UE分配的隧道端标识， 授权的 QoS参数等信息。 步骤 908, SGSN向基站发送承载指配请求， 其中携带 UE的移动台国际 用户目录号 （MSISDN )号码， APN, QoS参数等信息。
步骤 909, 如果基站接受了核心网网关下发的 QoS参数， 则基站发起无 线资源控制 （RRC )连接建立的过程。
步骤 910,基站向 SGSN返回无线接入承载 ( RAB , Radio Access Bearer ) 指配响应消息。如果同时建立多条承载， 则基站会返回多个 RAN指配响应消 息。
步骤 911 , 如果基站无法接受 RAB指配消息中的 QoS参数， 则在返回的 RAN指配响应消息中指示给 SGSN。 SGSN根据该指示， 可以选择下发新的 QoS参数。
步骤 912, SGSN根据是否建立直接隧道， 判断是否要向核心网网关发送 更新 PDP上下文请求， 如果发送， 则其中携带基站的隧道端标识。 如果 QoS 与之前核心网网关下发的 QoS不一致，则 SGSN通过 PDP更新过程通知核心 网网关。
步骤 913 , SGSN向 UE返回激活 PDP上下文响应消息。
上述流程中， 本地网关所釆用的服务质量和计费策略都只能够通过本地 配置来实现。 如何使运营商对本地分流策略配置更为灵活， 对如何做本地分 流的策略进行动态配置是需要解决的技术问题。 发明内容
本发明提供了一种实现数据流服务质量和计费策略控制的方法， 提高系 统的服务性能。
一种实现数据流服务质量和计费策略控制的方法， 包括：
本地网关确定需分流的数据流后将所述分流数据流的标识通知给策略计 费规则功能（PCRF ) ， 所述策略计费规则功能向所述本地网关提供针对所述 分流数据流的服务质量策略和 /或计费策略规则。
该方法还包括：
所述策略计费规则功能在同一用户的网络连接中所述本地网关建立的连 接接入网络会话和核心网网关建立的接入网络会话之间建立会话关联关系。 该方法还包括：
所述策略计费规则功能在为所述分流数据流分配的服务质量策略和 /或 计费策略规则发生变化时， 根据与所述分流数据流相关的会话关联关系向所 述核心网网关和所述本地网关下发更新后的服务质量策略和 /或计费策略规 则。
其中， 本地网关确定需分流的数据流的步骤包括：
所述本地网关截获移动性管理单元向基站发送的承载指配请求， 并根据 所述承载指配请求中携带的信息判定要进行数据分流； 或者 ,
所述本地网关截获所述基站向所述移动性管理单元发送的承载指配响 应， 并根据所述承载指配响应中携带的信息判定要进行数据分流。
其中， 本地网关确定需分流的数据流的步骤包括：
终端接入核心网时 ,移动性管理单元为所述终端选择所经由的本地网关 , 本地网关收到所述移动性管理单元下发的创建分组数据协议上下文请求后， 根据所述创建分组数据协议上下文请求中携带的信息判定要进行数据分流； 或者，
本地网关为用户选择要接入的核心网网关， 所述本地网关收到所述核心 网网关发送的创建分组数据协议上下文请求响应后， 判定要进行数据分流。
其中， 策略计费规则功能向所述本地网关下发更新后的服务质量策略和 / 或计费策略规则的步骤包括：
用户通过核心网网关通知所述策略计费规则功能修改后的业务数据流标 识， 所述策略计费规则功能根据修改后的业务数据流标识， 判断所述本地网 关上的策略需要修改时， 向所述本地网关下发更新后的服务质量策略和 /或计 费策略规则。
其中， 策略计费规则功能向所述本地网关下发更新后的服务质量策略和 / 或计费策略规则的步骤包括：
所述策略计费规则功能查询或获知服务质量策略和 /或计费策略规则变 化后， 根据受影响的分组数据网络连接和 /或业务数据流判断所述本地网关上 的策略需要修改时， 向所述本地网关下发更新后的服务质量策略和 /或计费策 略规则。
其中， 策略计费规则功能向所述本地网关下发更新后的服务质量策略和 / 或计费策略规则的步骤包括：
所述本地网关截获终端通过基站向核心网发送的修改后的承载信息后， 根据所述承载信息判断需要修改业务数据流时， 将修改后的业务数据流标识 通知至所述策略计费规则功能， 所述策略计费规则功能更新服务质量策略和 / 或计费策略规则， 向所述本地网关发送更新后的服务质量策略和 /或计费策略 规则。
一种实现数据流服务质量和计费策略控制的***， 包括本地网关和策略 计费规则功能（PCRF ) , 其中，
所述本地网关设置成： 确定需分流的数据流后将所述分流数据流的标识 通知至所述策略计费规则功能；
所述策略计费规则功能设置成： 向所述本地网关提供针对分流数据流的 服务质量策略和 /或计费策略规则。
其中， 所述策略计费规则功能还设置成：
在同一用户的网络连接中本地网关建立的连接接入网络会话和核心网网 关建立的接入网络会话之间建立会话关联关系； 为所述分流数据流分配的服 务质量策略和 /或计费策略规则发生变化时， 根据与所述分流数据流相关的会 话关联关系向所述核心网网关和所述本地网关下发更新后的服务质量策略和 /或计费策略规则。
其中， 所述本地网关设置成按照以下方式中的一种确定需分流的数据 流：
截获移动性管理单元向基站发送的承载指配请求， 并根据所述承载指配 请求中携带的信息判定要进行数据分流；
截获所述基站向所述移动性管理单元发送的承载指配响应， 并根据所述 承载指配响应中携带的信息判定要进行数据分流。
其中， 所述本地网关设置成按照以下方式中的一种确定需分流的数据 在终端接入核心网时， 收到移动性管理单元下发的创建分组数据协议上 下文请求后， 根据所述创建分组数据协议上下文请求中携带的信息判定要进 行数据分流； 或者，
为用户选择要接入的核心网网关， 收到所述核心网网关发送的创建分组 数据协议上下文请求响应后， 判定要进行数据分流。
其中， 所述策略计费规则功能设置成按照以下方式实现向本地网关下发 更新后的服务质量策略和 /或计费策略规则：
收到用户通过核心网网关发来的修改后的业务数据流标识后， 根据修改 后的业务数据流标识， 判断所述本地网关上的策略需要修改时， 向所述本地 网关下发更新后的服务质量策略和 /或计费策略规则。
其中， 所述策略计费规则功能设置成按照以下方式实现向本地网关下发 更新后的服务质量策略和 /或计费策略规则：
查询或获知服务质量策略和 /或计费策略规则变化后， 根据受影响的分组 数据网络连接和 /或业务数据流判断所述本地网关上的策略需要修改时， 向所 述本地网关下发更新后的服务质量策略和 /或计费策略规则。
其中， 所述本地网关还设置成：
截获终端通过基站向核心网发送修改后的承载信息后， 根据所述承载信 息判断需要修改业务数据流时， 将修改后的业务数据流标识通知至策略计费 规则功能；
所述策略计费规则功能还设置成： 更新服务质量策略和 /或计费策略规 则， 向所述本地网关发送更新后的服务质量策略和 /或计费策略规则。
上述技术方案可以对本地网关的数据流的服务质量和计费策略进行灵活 控制， 提高***服务性能。 附图概述 图 1是演进分组域***的结构示意图；
图 2是 3G家用基站网络架构示意图；
图 3是 LTE家用基站网络架构示意图之一；
图 4是 LTE家用基站网络架构示意图之二；
图 5是 LTE家用基站网络架构示意图之三；
图 6是实现本地接入的网络架构示意图之一；
图 7是实现本地接入的网络架构示意图之一；
图 8是实现本地接入的网络架构示意图之一；
图 9是动态获取策略的流程示意图；
图 12是本发明实施例中实现策略修改的实施方式一；
图 13是本发明实施例中实现策略修改的实施方式二；
图 14是本发明实施例中实现策略修改的实施方式三。 本发明的较佳实施方式
实现数据流服务质量和计费策略控制的***包括本地网关和策略计费规 则功能（PCRF ) 。
所述本地网关设置成： 确定需在本地传输的分流数据流后将分流数据流 的标识通知至策略计费规则功能；
所述策略计费规则功能设置成： 向所述本地网关提供针对分流数据流的 服务质量策略和 /或计费策略规则。
所述策略计费规则功能还设置成： 对同一用户的网络连接中本地网关建 立的连接接入网络会话和核心网网关建立的接入网络会话建立会话关联关系； 为所述用户的分流数据流分配的服务质量策略和 /或计费策略规则发生变化 时， 根据与分流数据流相关的接入网络会话的会话关联关系向核心网网关和 本地网关下发更新后的服务质量策略和 /或计费策略规则。
所述本地网关设置成按照以下方式中的一种确定要分流的数据流： 截获移动性管理单元向基站发送的承载指配请求， 并根据此承载指配请 求携带的信息判定要进行数据分流； 或者，
截获基站向移动性管理单元发送的承载指配响应， 并根据此承载指配响 应携带的信息判定要进行数据分流。
所述本地网关还设置成： 在终端接入核心网时， 收到所述移动性管理单 元下发的创建分组数据协议上下文请求后， 根据此创建分组数据协议上下文 请求携带的信息判定要进行数据分流； 或者， 为用户选择要接入的核心网网关， 收到所述核心网网关发送的创建分组 数据协议上下文后， 判定要进行数据分流。
本***釆用第一种服务质量策略和 /或计费策略规则更新方式时： 策略计费规则功能设置成按照以下方式实现向本地网关下发更新后的服 务质量策略和 /或计费策略规则：
收到用户通过核心网网关向策略计费规则功能通知的修改后的业务数据 流标识后， 根据修改后的业务数据流标识， 判断本地网关上的策略需要修改 时， 向本地网关下发更新后的服务质量策略和 /或计费策略规则。
本***釆用第二种服务质量策略和 /或计费策略规则更新方式时： 策略计费规则功能设置成按照以下方式实现向本地网关下发更新后的服 务质量策略和 /或计费策略规则：查询或获知服务质量策略和 /或计费策略规则 变化后， 根据受影响的分组数据网络连接和 /或业务数据流判断本地网关上的 策略需要修改时， 向本地网关下发更新后的服务质量策略和 /或计费策略规 则。
本***釆用第三种服务质量策略和 /或计费策略规则更新方式时: 所述本地网关还设置成： 截获终端通过基站向核心网发送修改后的承载 信息后， 根据承载信息判断需要修改业务数据流时， 将修改后的业务数据流 标识通知至策略计费规则功能；
所述策略计费规则功能还设置成： 更新服务质量策略和 /或计费策略规 则， 向本地网关发送更新后的服务质量策略和 /或计费策略规则。
实现数据流服务质量和计费策略控制的方法包括： 本地网关确定需在本 地传输的分流数据流后将分流数据流的标识通知至策略计费规则功能， 所述 策略计费规则功能向所述本地网关提供针对分流数据流的服务质量策略和 / 或计费策略规则。
所述策略计费规则功能对同一用户的网络连接中本地网关建立的连接接 入网络会话和核心网网关建立的接入网络会话建立会话关联关系。
所述策略计费规则功能在为所述用户的分流数据流分配的服务质量策略 和 /或计费策略规则发生变化时， 根据与分流数据流相关的接入网络会话的会 话关联关系向核心网网关和本地网关下发更新后的服务质量策略和 /或计费 策略规则。
为详细说明本发明， 以下结合附图对本发明作进一步详细的描述。
图 10描述了实现本地网关获取策略的实施方式一。 在本实施方式中， 本 地网关确定要分流的数据流的方式为： 所述本地网关截获移动性管理单元向 基站发送的承载指配请求， 并根据此承载指配请求携带的信息判定要进行数 据分流； 或者， 所述本地网关截获基站向移动性管理单元发送的承载指配响 应， 并根据此承载指配响应携带的信息判定要进行数据分流。
本实施例中针对图 7中所述的路由方式。
步骤 1001 , 终端发起激活 PDP上下文请求， 该非接入层消息经由基站发 送至 MME。
一般情况下， 移动管理单元是移动管理实体（MME )和 SGSN的上位描 述。本实施例的消息以 GERAN/UTRAN接入 GRPS网络为例进行描述， 则移 动管理单元是 SGSN。
步骤 1002, SGSN根据 UE提供的 APN, 为 UE选择一个合适的核心网 网关。 SGSN向核心网网关发送创建 PDP上下文请求， 其中携带 UE标识， PDP类型， QoS信息， 计费信息等参数。 如果是接入 GPRS网络， 则核心网 网关为 GGSN, 如果接入 EPC网络， 则核心网网关指的是 S-GW和 P-GW。 接入的网络不通， 消息有所不同， 但是作用类似， 这里以接入 GRPS网络的 描述为例。 如果核心网网关是 S-GW和 P-GW, 则步骤 1002、 1007为创建会 话请求 /响应， 步骤 1017为修改承载过程， 并且不支持 QoS协商。 上述过程 都为本领域技术人员所公知的技术， 这里不做赞述。 核心网网关对创建 PDP上下文请求消息中携带的参数进行验证， 并对请 求中携带的 QoS参数进行授权。
步骤 1003 , 核心网网关向 PCRF发送 IP-CAN会话建立请求， 其中携带 UE标识信息和 /或 UE IP地址。
步骤 1004〜步骤 1005, PCRF从 SPR获取用户的签约数据， 用于制定相 关规则。
步骤 1006, PCRF发送 IP-CAN会话建立响应， 其中包含策略和计费规 则。
步骤 1007,核心网网关向 SGSN返回创建 PDP上下文响应，其中携带为 UE分配的隧道端标识， 授权的 QoS参数等信息。
步骤 1008, SGSN向基站发送承载指配请求， 其中携带 UE的 MSISDN 号码， APN, QoS参数等信息。 承载指配请求消息中还包含用户的 IP地址和 当前建立的 PDN连接标识信息。 PDN连接标识信息可以是 APN信息， 或者 承载标识。
步骤 1009, 本地网关截获 SGSN发送的 RAB指配请求， 根据运营商策 略判断以及 RAB指配消息中包含的 MSISDN, APN和或计费特征信息， 判 断将是否将全部承载， 或者承载中的某些数据进行分流。
步骤 1010, 本地网关向 PCRF发送 IP-CAN会话建立或者 IP-CAN会话 修改请求， 其中携带分流的业务数据流标识以及以下信息的一种或多种： UE 标识信息， UE IP地址， APN, 承载标识。 其中 UE的标识信息， UE IP地 址信息， APN, 承载标识与步骤 1009中携带的信息一致。
步骤 1011 , PCRF将核心网建立的 IP-CAN会话和本地网关建立的 IP-CAN 会话关联， 即建立关联关系。
步骤 1012, PCRF根据步骤 1010中的业务数据流标识生成相应的计费和 服务质量策略， 并通过 IP-CAN会话建立响应消息发送给本地网关。
步骤 1013 , 本地网关将 RAB支配消息发送给基站。
步骤 1014, 如果基站接受了核心网网关下发的 QoS参数， 则基站发起 RRC连接建立的过程。
步骤 1015 1016, 基站向 SGSN返回 RAB指配响应消息。 如果同时建立 多条承载， 则基站会返回多个 RAN指配响应消息。
如果基站无法接受 RAB指配消息中的 QoS参数， 则在返回的 RAN指配 响应消息中指示给 SGSN。 SGSN根据该指示， 可以选择下发新的 QoS参数。
步骤 1017, SGSN根据是否建立直接隧道， 判断是否要向核心网网关发 送更新 PDP上下文请求， 如果发送， 则其中携带基站的隧道端标识。 如果 QoS与之前核心网网关下发的 QoS不一致，则 SGSN通过 PDP上下文更新过 程通 口核心网网关。
步骤 1018, SGSN向 UE返回激活 PDP上下文响应消息。
可选的， 步骤 1009 1012可以在步骤 1015之后步骤 1016之前执行。 该过程适用于 UE在 UTRAN/GERAN发起的 PDP激活、 次 PDP激活， 网络发起的 PDP和次 PDP激活流程。 也适用于 UE在 EUTRAN发起的 PDN 连接建立， ATTACH流程， UE发起的请求资源修改或者分配流程， 以及网 络发起的承载激活流程。
图 11描述了实现本地网关获取策略的实施方式二。 在本实施方式中， 终 端接入核心网时， 移动性管理单元为所述终端选择所经由的本地网关， 本地 网关收到所述移动性管理单元下发的创建分组数据协议（PDP )上下文请求 后， 根据此创建分组数据协议上下文请求携带的信息判定要进行数据分流， 或者， 本地网关为用户选择要接入的核心网网关， 所述本地网关收到所述核 心网网关发送的创建分组数据协议上下文请求响应后，判定要进行数据分流。
本实施例中针对图 8中所述的路由方式。
步骤 1101 , 终端发起激活 PDP上下文请求， 该非接入层消息经由基站发 送至 SGSN。
一般情况下， 移动管理单元是移动管理实体（MME )和 SGSN的上位描 述。 本实施例的消息以 GERAN/UTRAN接入 GRPS网络为例进行描述。
步骤 1102, SGSN根据 UE提供的 APN, 为 UE选择一个合适的本地网 关。 SGSN向本地网关发送创建 PDP上下文请求， 其中携带 UE标识， PDP 类型， QoS信息， 计费信息， 隧道端标识等参数。
步骤 1103 ,本地网关向核心网网关发送创建 PDP上下文请求，其中携带。 其中携带 UE标识， PDP类型， QoS信息， 计费信息， 隧道端标识等参数。
如果是接入 GPRS网络， 则核心网网关为 GGSN, 如果接入 EPC网络， 则核心网网关指的是 S-GW和 P-GW。 接入的网络不同， 消息有所不同， 但 是作用类似， 这里以接入 GRPS 网络的描述为例。 如果核心网网关是 S-GW 和 P-GW,则步骤 1102、 1103、 1108和 1113为创建会话请求 /响应，步骤 1117 为修改承载过程， 并且不支持 QoS协商。 上述过程都为本领域技术人员所公 知的技术， 这里不做赞述。
核心网网关对创建 PDP上下文请求消息中携带的参数进行验证。
步骤 1104 , 核心网网关向 PCRF发送 IP-CAN会话建立请求， 其中携带
UE标识信息和 /或 UE IP地址。
步骤 1105〜步骤 1106, PCRF从 SPR获取用户的签约数据， 用于制定相 关规则。
步骤 1107, PCRF发送 IP-CAN会话建立响应， 其中包含策略和计费规 则。
步骤 1108,核心网网关向本地网关返回创建 PDP上下文响应， 其中携带 为 UE分配的隧道端标识， 授权的 QoS参数等信息。
步骤 1109, 根据运营商策略判断将是否将全部承载， 或者承载中的某些 数据进行分流。
可选的， 步骤 1109的判断可以在步骤 1102与 1103之间执行。
步骤 1110, 本地网关向 PCRF发送 IP-CAN会话建立或者 IP-CAN会话 修改请求， 其中携带分流的业务数据流标识以及以下信息的一种或多种： UE 标识信息， UE IP地址， APN, 承载标识。 其中 UE的标识信息， UE IP地 址信息， APN, 承载标识与步骤 1109中携带的信息一致。
步骤 1111 , PCRF将核心网建立的 IP-CAN会话和本地网关建立的 IP-CAN 关联， 即建立关联关系。
步骤 1112, PCRF根据步骤 1110中的业务数据流标识生成相应的计费和 服务质量策略， 并通过 IP-CAN会话建立响应消息发送给本地网关。
可选的， 步骤 1110和步骤 1112可以在步骤 2之后步骤 3之前执行。 如 果先执行了步骤 1110和 1112, 则步骤 1111在步骤 1106之后步骤 1107之前 执行。
步骤 1113 , 本地网关向 SGSN返回创建 PDP上下文响应， 其中携带为 UE分配的隧道端标识， 授权的 QoS参数等信息。
步骤 1114, 本地网关将 RAB支配消息发送给基站。
步骤 1115, 如果基站接受了核心网网关下发的 QoS参数， 则基站发起 RRC连接建立的过程。
步骤 1116 1117, 基站向 SGSN返回 RAB指配响应消息。 如果同时建立 多条承载， 则基站会返回多个 RAN指配响应消息。
如果基站无法接受 RAB指配消息中的 QoS参数， 则在返回的 RAN指配 响应消息中指示给 SGSN。 SGSN根据该指示， 可以选择下发新的 QoS参数。
步骤 1118, SGSN根据是否建立直接隧道， 判断是否要向核心网网关发 送更新 PDP上下文请求， 如果发送， 则其中携带基站的隧道端标识。 如果 QoS与之前核心网网关下发的 QoS不一致，则 SGSN通过 PDP上下文更新过 程通 口核心网网关。
步骤 1119, SGSN向 UE返回激活 PDP上下文响应消息。 该过程适用于 UE在 UTRAN/GERAN发起的 PDP激活、 次 PDP激活， 网络发起的 PDP和次 PDP激活流程。 也适用于 UE在 EUTRAN发起的 PDN 连接建立， ATTACH流程， UE发起的请求资源修改或者分配流程， 以及网 络发起的承载激活流程。
图 12描述了实现本地网关策略修改的实施方式一。策略计费规则功能向 本地网关下发更新后的服务质量策略和 /或计费策略规则时， 根据以下方式实 现： 用户通过核心网网关通知策略计费规则功能修改后的业务数据流标识， 策略计费规则功能根据修改后的业务数据流标识， 判断本地网关上的策略需 要修改时， 向本地网关下发更新后的服务质量策略和 /或计费策略规则。
步骤 1201 , UE向核心网发起 PDP修改请求或者资源分配请求或者资源 修改请求。 如果 UE从 GERAN/UTRAN接入， 则 UE发起 PDP修改请求。 如 果 UE从 EUTRAN接入， 则 UE发起资源分配请求， 或者资源修改请求。
步骤 1202 , 核心网网关向 PCRF发送 IP-CAN会话修改请求， 其中携带 修改的业务数据流标识以及以下参数中的一种或多种 UE标识信息： UE IP地 址， APN, 7?ι载标识。
步骤 1203 , PCRF根据修改的业务数据流标识， 判断是否要修改本地网 关上的策略信息。 这里假设判断为是。
步骤 1204, PCRF向本地网关发送更新服务质量和计费策略请求， 其中 携带修改的业务数据流标识以及所标识服务质量和计费策略以及以下参数中 的一种或多种： UE标识， 和或 UE IP地址， 和或 APN, 和或 7 载标识。
步骤 1205, 本地网关向 CPRF发送更新服务质量和计费策略响应。
步骤 1206, PCRF向核心网网关发送 IP-CAN会话修改响应， 其中携带 修改的业务数据流标识所标识服务质量和计费策略以及以下参数中的一种或 多种： UE标识， UE IP地址， APN, 载标识。
步骤 1207, 完成 PDP修改， 或者资源分配或者资源修改的剩余流程， 该 过程为本领域技术人员所公知的技术， 这里不做赘述。 图 13描述了实现本地网关策略^ ί'爹改的实施方式二。 终端接入核心网时， 移动性管理单元为所述终端选择所经由的本地网关， 策略计费规则功能向本 地网关下发更新后的服务质量策略和 /或计费策略规则时， 根据以下方式实 现： 策略计费规则功能查询或获知服务质量策略和 /或计费策略规则变化后， 根据受影响的分组数据网络连接和 /或业务数据流判断本地网关上的策略需 要修改时， 向本地网关下发更新后的服务质量策略和 /或计费策略规则。
步骤 1301 , 服务质量和或计费策略发生变化， 例如 AF触发， 或者用户 签约变化导致 SPR触发。 PCRF根据受影响的 PDN连接和或业务数据流， 判 断是否需要通知本地网关和核心网网关， 这里判断都为是。
步骤 1302, PCRF向核心网网关发送更新服务质量和计费策略请求， 其 中携带受到影响的业务数据流以及修改后的服务质量和或计费策略以及以下 参数中的一种或多种 UE标识信息， UE IP地址， ΑΡΝ, 承载标识。
步骤 1303 , 核心网网关向 PCRF发送更新服务质量和计费策略响应。 步骤 1304, PCRF向本地网关发送更新服务质量和计费策略请求， 其中 携带受到影响的业务数据流， 以及修改后的服务质量和或计费策略， 以及以 下参数中的一种或多种： UE标识， UE IP地址， APN, 承载标识。
步骤 1305, 本地网关向 PCRF发送更新服务质量和计费策略响应。
步骤 1306, 完成 PDP激活/ PDP修改/ PDP去活， 或者承载激活 /承载修改 /承载去活的流程， 该过程为本领域技术人员所公知的技术， 这里不做赘述。
图 14描述了实现本地网关策略修改的实施方式三。策略计费规则功能向 本地网关下发更新后的服务质量策略和 /或计费策略规则时， 根据以下方式实 现： 本地网关截获终端通过基站向核心网发送修改后的承载信息后， 根据承 载信息判断需要修改业务数据流时， 将修改后的业务数据流标识通知至策略 计费规则功能， 策略计费规则功能更新服务质量策略和 /或计费策略规则， 向 本地网关发送更新后的服务质量策略和 /或计费策略规则。
步骤 1401 , UE发起 PDP修改请求， 或者资源分配请求或者资源修改请 求。 如果 UE从 GERAN/UTRAN接入， 则 UE发起 PDP修改请求。 如果 UE 从 EUTRAN接入， 则 UE发起资源分配请求， 或者资源修改请求。 步骤 1402, 如果釆用图 7的架构， 则本地网关截获基站发给移动性管理 单元的 PDP修改请求， 或者资源分配请求或者资源修改请求。 如果釆用图 8 的架构，则移动性管理单元向本地网关发送 PDP修改请求或者承载修改请求。
本地网关判断修改的承载对分流数据是否有影响， 这里假设判断为是。 步骤 1403 , 本地网关向 PCRF发送 IP-CAN会话修改请求， 其中携带修 改的业务数据流标识以及以下信息中的一种或多种： UE标识信息 , UE IP地 址， APN, 7?ι载标识。
步骤 1404 , PCRF向本地网关发送 IP-CAN会话修改响应， 其中携带 UE 标识， 和或 UE IP地址， 和或 APN, 和或？ 载标识， 以及爹改的业务数据流 标识所标识服务质量和计费策略。
步骤 1405, 完成 PDP修改， 或者资源分配或者资源修改的剩余流程， 该 过程为本领域技术人员所公知的技术， 这里不做赘述。
上述实施方式中均不限定基站类型， 即家用基站或者普通基站。 流程描 述中以基站为例， 对家用基站的影响是相同的。 实施方式可以适用于 UTRAN/GERAN接入 GPRS或者 EPC网络的情况 ,或者 EUTRAN接入的 EPC 网络。 对于 UTRAN/GERAN接入来说， 家用基站 /基站为 HNB/RNC。 而核心 网网关指的是位于核心网的 GGSN/P-GW, 该网元与本发明无关， 这里不做 过多限定。对于 EUTRAN接入来说家用基站 /基站指的是 HeNB/eNB, 而核心 网网关指的是位于核心网的 S-GW/P-GW。本地网关在实施方式中可以为数据 分流功能（TOF ) 实体或者 NAT网关或者 L-GW, 但是实现功能类似。 对于 家用基站的场景， 网络中可能存在家用基站网关， 如果存在家用基站网关， 那么所有家用基站和移动性管理单元之间的消息都需要经过家用基站网关。 家用基站和本地网关之间的消息， 可以通过家用基站网关也可以不通过家用 基站网关。 对于通过家用基站网关转发消息的场景， 家用基站网关对经过的 消息进行透传， 透传的过程与本发明无关， 这里不做赞述。 实施例的消息以 GERAN/UTRAN接入 GRPS网络为例， 对于其他上述适用的接入情况， 发明 点所针对的内容是一致的， 这里不做赞述。 下文中将结合附图对本发明的实施例进行详细说明。 需要说明的是， 在 不冲突的情况下， 本申请中的实施例及实施例中的特征可以相互任意组合。
当然， 本发明还可有其他多种实施例， 在不背离本发明精神及其实质的 但这些相应的改变和变形都应属于本发明所附的权利要求的保护范围。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序 来指令相关硬件完成， 所述程序可以存储于计算机可读存储介质中， 如只读 存储器、 磁盘或光盘等。 可选地， 上述实施例的全部或部分步骤也可以使用 一个或多个集成电路来实现。 相应地， 上述实施例中的各模块 /单元可以釆用 硬件的形式实现， 也可以釆用软件功能模块的形式实现。 本发明不限制于任 何特定形式的硬件和软件的结合。
工业实用性
上述技术方案可以对本地网关的数据流的服务质量和计费策略进行灵活 控制， 提高***服务性能。 因此本发明具有很强的工业实用性。

Claims

权 利 要 求 书
1、 一种实现数据流服务质量和计费策略控制的方法， 包括：
本地网关确定需分流的数据流后将所述分流数据流的标识通知给策略计 费规则功能（PCRF ) ， 所述策略计费规则功能向所述本地网关提供针对所述 分流数据流的服务质量策略和 /或计费策略规则。
2、 如权利要求 1所述的方法， 该方法还包括：
所述策略计费规则功能在同一用户的网络连接中所述本地网关建立的连 接接入网络会话和核心网网关建立的接入网络会话之间建立会话关联关系。
3、 如权利要求 2所述的方法， 该方法还包括：
所述策略计费规则功能在为所述分流数据流分配的服务质量策略和 /或 计费策略规则发生变化时， 根据与所述分流数据流相关的会话关联关系向所 述核心网网关和所述本地网关下发更新后的服务质量策略和 /或计费策略规 则。
4、 如权利要求 1、 2或 3所述的方法， 其中， 本地网关确定需分流的数 据流的步骤包括：
所述本地网关截获移动性管理单元向基站发送的承载指配请求， 并根据 所述承载指配请求中携带的信息判定要进行数据分流； 或者 ,
所述本地网关截获所述基站向所述移动性管理单元发送的承载指配响 应， 并根据所述承载指配响应中携带的信息判定要进行数据分流。
5、 如权利要求 1、 2或 3所述的方法， 其中， 本地网关确定需分流的数 据流的步骤包括：
终端接入核心网时 ,移动性管理单元为所述终端选择所经由的本地网关 , 本地网关收到所述移动性管理单元下发的创建分组数据协议上下文请求后， 根据所述创建分组数据协议上下文请求中携带的信息判定要进行数据分流； 或者，
本地网关为用户选择要接入的核心网网关， 所述本地网关收到所述核心 网网关发送的创建分组数据协议上下文请求响应后， 判定要进行数据分流。
6、 如权利要求 3所述的方法， 其中， 策略计费规则功能向所述本地网关 下发更新后的服务质量策略和 /或计费策略规则的步骤包括：
用户通过核心网网关通知所述策略计费规则功能修改后的业务数据流标 识， 所述策略计费规则功能根据修改后的业务数据流标识， 判断所述本地网 关上的策略需要修改时， 向所述本地网关下发更新后的服务质量策略和 /或计 费策略规则。
7、 如权利要求 3所述的方法， 其中， 策略计费规则功能向所述本地网关 下发更新后的服务质量策略和 /或计费策略规则的步骤包括：
所述策略计费规则功能查询或获知服务质量策略和 /或计费策略规则变 化后， 根据受影响的分组数据网络连接和 /或业务数据流判断所述本地网关上 的策略需要修改时， 向所述本地网关下发更新后的服务质量策略和 /或计费策 略规则。
8、 如权利要求 3所述的方法， 其中， 策略计费规则功能向所述本地网关 下发更新后的服务质量策略和 /或计费策略规则的步骤包括：
所述本地网关截获终端通过基站向核心网发送的修改后的承载信息后， 根据所述承载信息判断需要修改业务数据流时， 将修改后的业务数据流标识 通知至所述策略计费规则功能， 所述策略计费规则功能更新服务质量策略和 / 或计费策略规则， 向所述本地网关发送更新后的服务质量策略和 /或计费策略 规则。
9、 一种实现数据流服务质量和计费策略控制的***， 包括本地网关和策 略计费规则功能（PCRF ) , 其中，
所述本地网关设置成： 确定需分流的数据流后将所述分流数据流的标识 通知至所述策略计费规则功能；
所述策略计费规则功能设置成： 向所述本地网关提供针对分流数据流的 服务质量策略和 /或计费策略规则。
10、如权利要求 9所述的***，其中， 所述策略计费规则功能还设置成： 在同一用户的网络连接中本地网关建立的连接接入网络会话和核心网网 关建立的接入网络会话之间建立会话关联关系； 为所述分流数据流分配的服 务质量策略和 /或计费策略规则发生变化时， 根据与所述分流数据流相关的会 话关联关系向所述核心网网关和所述本地网关下发更新后的服务质量策略和 /或计费策略规则。
11、 如权利要求 9或 10所述的***， 其中， 所述本地网关设置成按照 以下方式中的一种确定需分流的数据流：
截获移动性管理单元向基站发送的承载指配请求， 并根据所述承载指配 请求中携带的信息判定要进行数据分流；
截获所述基站向所述移动性管理单元发送的承载指配响应， 并根据所述 承载指配响应中携带的信息判定要进行数据分流。
12、 如权利要求 9或 10所述的***， 其中， 所述本地网关设置成按照 以下方式中的一种确定需分流的数据流：
在终端接入核心网时， 收到移动性管理单元下发的创建分组数据协议上 下文请求后， 根据所述创建分组数据协议上下文请求中携带的信息判定要进 行数据分流； 或者，
为用户选择要接入的核心网网关， 收到所述核心网网关发送的创建分组 数据协议上下文请求响应后， 判定要进行数据分流。
13、 如权利要求 9或 10所述的***， 其中， 所述策略计费规则功能设置 成按照以下方式实现向本地网关下发更新后的服务质量策略和 /或计费策略 规则：
收到用户通过核心网网关发来的修改后的业务数据流标识后， 根据修改 后的业务数据流标识， 判断所述本地网关上的策略需要修改时， 向所述本地 网关下发更新后的服务质量策略和 /或计费策略规则。
14、 如权利要求 9或 10所述的***， 其中， 所述策略计费规则功能设置 成按照以下方式实现向本地网关下发更新后的服务质量策略和 /或计费策略 规则：
查询或获知服务质量策略和 /或计费策略规则变化后， 根据受影响的分组 数据网络连接和 /或业务数据流判断所述本地网关上的策略需要修改时， 向所 述本地网关下发更新后的服务质量策略和 /或计费策略规则。
15、 如权利要求 9或 10所述的***， 其中， 所述本地网关还设置成： 截获终端通过基站向核心网发送修改后的承载信息后， 根据所述承载信 息判断需要修改业务数据流时， 将修改后的业务数据流标识通知至策略计费 规则功能；
所述策略计费规则功能还设置成： 更新服务质量策略和 /或计费策略规 则， 向所述本地网关发送更新后的服务质量策略和 /或计费策略规则。
PCT/CN2011/081775 2010-11-09 2011-11-04 一种实现数据流服务质量和计费策略控制的方法及*** WO2012062183A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010538119.6 2010-11-09
CN201010538119.6A CN102469433B (zh) 2010-11-09 2010-11-09 一种实现数据流服务质量和计费策略控制的方法及***

Publications (1)

Publication Number Publication Date
WO2012062183A1 true WO2012062183A1 (zh) 2012-05-18

Family

ID=46050401

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/081775 WO2012062183A1 (zh) 2010-11-09 2011-11-04 一种实现数据流服务质量和计费策略控制的方法及***

Country Status (2)

Country Link
CN (1) CN102469433B (zh)
WO (1) WO2012062183A1 (zh)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103491517B (zh) * 2012-06-13 2017-05-10 电信科学技术研究院 一种pcc规则获取方法及设备
CN103517249B (zh) * 2012-06-29 2018-11-16 中兴通讯股份有限公司 一种策略控制的方法、装置和***
CN103718504B (zh) 2012-06-30 2016-11-09 华为技术有限公司 一种网关计费处理方法及网关
DE102014221975A1 (de) * 2014-10-28 2016-04-28 Robert Bosch Gmbh Verfahren und Vorrichtung zum Regeln einer Dienstgüte zwischen einem lokalen Netzwerk und einem Weitverkehrsnetz
CN107154901B (zh) * 2016-03-03 2021-07-06 中兴通讯股份有限公司 数据传输的控制方法及***、数据传输方法及装置
JP6662176B2 (ja) * 2016-04-21 2020-03-11 ソニー株式会社 情報処理装置、情報処理システム、情報処理方法およびプログラム
EP3582478A4 (en) * 2017-02-28 2019-12-18 Huawei Technologies Co., Ltd. METHOD, DEVICE AND SYSTEM OF LEGAL INTERCEPTION
CN111770545B (zh) * 2019-04-02 2022-08-26 华为技术有限公司 一种业务流路由控制方法、装置及***
CN110225475B (zh) * 2019-05-16 2020-07-14 中国联合网络通信集团有限公司 一种用户接入方法和核心网
CN116137699A (zh) * 2021-11-16 2023-05-19 中兴通讯股份有限公司 流量计费方法、网元及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101364901A (zh) * 2007-08-10 2009-02-11 华为技术有限公司 合法监听方法、合法监听***、分组数据网关、监听中心
CN101552682A (zh) * 2008-04-03 2009-10-07 华为技术有限公司 策略和计费控制信息控制方法及***
US20090300207A1 (en) * 2008-06-02 2009-12-03 Qualcomm Incorporated Pcc enhancements for ciphering support
CN101730047A (zh) * 2009-06-26 2010-06-09 中兴通讯股份有限公司 策略制定方法及***
CN101841797A (zh) * 2009-03-21 2010-09-22 中兴通讯股份有限公司 一种终端通过多接入网接入的计费方法和***及上报方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101364901A (zh) * 2007-08-10 2009-02-11 华为技术有限公司 合法监听方法、合法监听***、分组数据网关、监听中心
CN101552682A (zh) * 2008-04-03 2009-10-07 华为技术有限公司 策略和计费控制信息控制方法及***
US20090300207A1 (en) * 2008-06-02 2009-12-03 Qualcomm Incorporated Pcc enhancements for ciphering support
CN101841797A (zh) * 2009-03-21 2010-09-22 中兴通讯股份有限公司 一种终端通过多接入网接入的计费方法和***及上报方法
CN101730047A (zh) * 2009-06-26 2010-06-09 中兴通讯股份有限公司 策略制定方法及***

Also Published As

Publication number Publication date
CN102469433A (zh) 2012-05-23
CN102469433B (zh) 2015-10-21

Similar Documents

Publication Publication Date Title
US9320075B2 (en) Method, system and transmission distribution network element for indicating data-distribution
US8811317B2 (en) Method for implementing local access and system thereof
WO2012062183A1 (zh) 一种实现数据流服务质量和计费策略控制的方法及***
US8855045B2 (en) Method and system for controlling establishment of local IP access
EP2475142B1 (en) Method and system for acquiring route strategies
KR20100060800A (ko) ＨｅＮＢ에서 단말에게 선택적으로 자원을 할당하기 위한 시스템 및 장치
WO2012025031A1 (zh) 基于本地接入的承载建立方法及***
WO2011054264A1 (zh) 一种建立本地ip访问下行数据通道的方法及***
CN102056141B (zh) 一种实现本地接入的***和方法
WO2013107240A1 (zh) 无线接入能力上报方法和基站、策略控制方法和***
WO2012142889A1 (zh) 一种网关的选择方法、实现设备及***
WO2012068946A1 (zh) 查询网关的方法及***
WO2011017979A1 (zh) 支持ip分流的通信***中资源管理方法与装置
WO2012075907A1 (zh) 数据分流方法及本地网关
JP2015510709A (ja) ローカルアクセス接続の処理方法及び装置
WO2011097989A1 (zh) 一种本地访问寻呼优化方法及装置
WO2011144000A1 (zh) 一种实现路由选择的方法和装置
WO2012126319A1 (zh) 一种本地访问业务的切换方法及***
WO2012028071A1 (zh) 一种查询本地网关的方法和***
WO2011050663A1 (zh) 支持本地ip访问的通信***中隧道更新方法与***
WO2014071790A1 (zh) 固网移动融合的策略控制方法、装置及***
WO2011085623A1 (zh) 本地接入网关获取终端的寻呼信息的方法和***
WO2011157100A1 (zh) 一种数据缓存的方法和***
WO2012041131A1 (zh) 一种用户参与本地访问连接建立的方法及***
WO2011038609A1 (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: 11839211

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

Country of ref document: EP

Kind code of ref document: A1