WO2012062183A1 - Procédé et système pour contrôler une qualité de service et une politique de facturation de flux de données - Google Patents

Procédé et système pour contrôler une qualité de service et une politique de facturation de flux de données 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)
Chinese (zh)
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/fr

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

L'invention concerne un procédé et un système pour contrôler la qualité de service et la politique de facturation de flux de données. Ledit procédé comprend les étapes suivantes : après avoir identifié un flux de données à distribuer une passerelle locale notifie une fonction de politique et de règles de facturation pour l'identificateur dudit flux de données à distribuer, et cette fonction de politique et règles de facturation fournit à la passerelle locale des règles de politique de qualité de service et/ou de politique de facturation spécifiques au flux de données à distribuer. Cette organisation technique permet de contrôler avec souplesse la qualité de service et la politique de facturation du flux de données de la passerelle locale, ce qui permet d'améliorer les performances du système.
PCT/CN2011/081775 2010-11-09 2011-11-04 Procédé et système pour contrôler une qualité de service et une politique de facturation de flux de données WO2012062183A1 (fr)

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 (fr) 2012-05-18

Family

ID=46050401

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/081775 WO2012062183A1 (fr) 2010-11-09 2011-11-04 Procédé et système pour contrôler une qualité de service et une politique de facturation de flux de données

Country Status (2)

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

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 (fr) * 2017-02-28 2019-12-18 Huawei Technologies Co., Ltd. Procédé, dispositif et système d'interception légale
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 (fr) Procédé et système pour contrôler une qualité de service et une politique de facturation de flux de données
EP2475142B1 (fr) Procédé et système d'acquisition de stratégies d itinéraire
US8855045B2 (en) Method and system for controlling establishment of local IP access
KR20100060800A (ko) ＨｅＮＢ에서 단말에게 선택적으로 자원을 할당하기 위한 시스템 및 장치
WO2012025031A1 (fr) Procédé et système d'établissement de porteuse basés sur une adresse locale
WO2011054264A1 (fr) Procédé et système pour établir des canaux de données de liaison descendante pour un accès de protocole internet local
CN102056141B (zh) 一种实现本地接入的系统和方法
WO2013107240A1 (fr) Procédé de compte-rendu de capacité d'accès sans fil, station de base et procédé et système de contrôle de règle
JP2015510709A (ja) ローカルアクセス接続の処理方法及び装置
WO2012142889A1 (fr) Procédé de sélection de passerelle, et dispositif et système pour sa mise en œuvre
WO2012068946A1 (fr) Procédé et système pour une interrogation de passerelle
WO2011017979A1 (fr) Procede et dispositif de gestion de ressources dans un systeme de communication soutenant le shuntage ip
WO2012075907A1 (fr) Procédé de distribution de données et passerelle locale
WO2011097989A1 (fr) Procédé d'optimisation de recherche locale de personnes et appareil associé
WO2011144000A1 (fr) Procédé et appareil de sélection de route
WO2012126319A1 (fr) Procédé et système pour le transfert intercellulaire d'un service d'accès local
WO2012028071A1 (fr) Procédé et système pour rechercher une passerelle locale
WO2011050663A1 (fr) Procédé et système de mise à jour de tunnel dans un système de communication prenant en charge un accès sous protocole internet (ip) local
WO2014071790A1 (fr) Procédé, dispositif et système destinés à un contrôle de politique d'une convergence fixe-mobile
WO2011085623A1 (fr) Procédé et système permettant à une passerelle d'accès local d'obtenir des informations d'appel d'un terminal
WO2011157100A1 (fr) Procédé et système de mise en cache de données
WO2012041131A1 (fr) Procédé et système permettant à un abonné de participer à l'établissement d'une communication en accès local
WO2011038609A1 (fr) Procédé et dispositif d'envoi d'informations de connexion locale

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