WO2011085620A1 - Procédé et système de mise en œuvre d'un contrôle de qualité de service - Google Patents

Procédé et système de mise en œuvre d'un contrôle de qualité de service Download PDF

Info

Publication number
WO2011085620A1
WO2011085620A1 PCT/CN2010/079235 CN2010079235W WO2011085620A1 WO 2011085620 A1 WO2011085620 A1 WO 2011085620A1 CN 2010079235 W CN2010079235 W CN 2010079235W WO 2011085620 A1 WO2011085620 A1 WO 2011085620A1
Authority
WO
WIPO (PCT)
Prior art keywords
policy
user
subscription information
function entity
user subscription
Prior art date
Application number
PCT/CN2010/079235
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 WO2011085620A1 publication Critical patent/WO2011085620A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/78—Architectures of resource allocation
    • H04L47/781—Centralised allocation of resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/80—Actions related to the user profile or the type of traffic
    • H04L47/808—User-type aware

Definitions

  • the present invention relates to a Local IP Access (LIPA) technology, and more particularly to a method and system for implementing Quality of Service (QoS) control when a mobile subscriber accesses a fixed network.
  • LIPA Local IP Access
  • QoS Quality of Service
  • EPS 3rd Generation Partnership Project
  • Evolved Packet System evolved packet system
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • P-GW Packet Data Network Gateway
  • HSS Home Subscriber Server
  • PCRF Policy and Charging Rules Function
  • FIG. 1 is a schematic diagram of a composition of an existing EPS architecture.
  • the MME is responsible for control planes such as mobility management, non-access stratum signaling processing, and user mobility management context management.
  • the access gateway includes S. - GW and P-GW, wherein the S-GW is an access gateway device connected to the E-UTRAN, configured to forward data between the E-UTRAN and the P-GW, and is responsible for buffering the paging waiting data; -GW is a border gateway between EPS and Packet Data Network (PDN), responsible for PDN access and forwarding data between EPS and PDN; authentication authorization server includes HSS, AAA server; PCRF is policy and meter The fee-based functional entity, the PCRF is connected to the IP service network through the Rx receiving interface to obtain service information.
  • PDN Packet Data Network
  • the PCRF is connected to the gateway device in the network through the Gx/Gxa/Gxc interface, and is responsible for initiating the IP bearer. Establish, guarantee the quality of service (QoS, Quality of Service) of the service data, and perform charging control.
  • QoS Quality of Service
  • the EPS supports interworking with the non-3GPP IP access network, wherein the interworking with the non-3GPP IP access network is implemented through the S2a/b/c interface, and the P-GW serves as an anchor point between the 3GPP and the non-3GPP IP access network.
  • the non-3GPP IP access network is divided into a trusted non-3GPP IP access network and an untrusted non-3GPP IP access network.
  • the trusted non-3GPP IP access network can be directly connected to the P-GW through the S2a interface; the untrusted non-3GPP IP access network needs to be connected to the P-GW through an evolved Packet Data Gateway (ePDG), ePDG and
  • ePDG evolved Packet Data Gateway
  • ePDG evolved Packet Data Gateway
  • the S2c provides user plane-related control and mobility support between the user equipment (UE, User Equipment) and the P-GW.
  • the supported mobility management protocol is to support dual-stack mobility.
  • IPv6 DSMIPv6, Moblie IPv6 Support for Dual Stack Hosts and Routers).
  • the Policy and Charging Enforcement Function (PCEF) entity exists in the P-GW, and the PCRF and the P-GW exchange information through the Gx interface.
  • the S-GW also has a Bearer Binding and Event Report Function (BBERF) entity to perform Quality of Service (QoS) control on the service data stream.
  • BBERF Bearer Binding and Event Report Function
  • QoS Quality of Service
  • the S-GW exchanges information with the PCRF through the Gxc interface.
  • the BBERF is also resident in the trusted non-3GPP access gateway.
  • the trusted non-3GPP access gateway exchanges information with the PCRF through the Gxa interface.
  • the S9 interface functions as an interface between the home PCRF and the visited PCRF, and provides an application function (AF, Application Function) for the UE, and sends the policy and charging control (PCC) to the PCRF through the Rx interface.
  • AF Application Function
  • PCC policy and charging control
  • the corresponding PDN network can be found by the access point name (APN, Access Point Name).
  • APN Access Point Name
  • IP connection usually a connection from the UE to the PDN network is called an IP connection.
  • IP-CAN IP Connectivity Access Network
  • the BBERF and the PCEF respectively establish a Diameter session with the PCRF, and the policy charging information for controlling the IP-CAN session and the information for formulating the policy are transmitted through the Diameter sessions.
  • the home base station (HNB, Home NodeB) is a small, low-power base station deployed in indoor places such as homes and offices.
  • the main purpose is to provide users with higher service rates and lower the cost of using high-speed services. At the same time, it compensates for the shortage of existing distributed cellular wireless communication systems.
  • the advantages of HNB are affordable, convenient, low power output, plug and play and more.
  • the home base station is a wireless side network element.
  • 2a is a schematic diagram of a connection of an HNB in a mobile communication network in the prior art. As shown in FIG. 2a, a home base station can be directly connected to a core network.
  • FIG. 2b is a schematic diagram of a connection of an HNB in a mobile communication network in the prior art.
  • the home base station can also access the core network through the logical network element of the home base station gateway.
  • the main function of the home base station gateway is to verify the security of the HNB, handle the registration of the HNB, perform operation and maintenance management on the HNB, configure and control the home base station according to the operator's requirements, and exchange data of the core network and the home base station.
  • mobile communication systems can also support local IP access functions, which can be achieved under the condition that the wireless side network element has local IP access capability and the user subscribes to allow local IP access.
  • local IP access functions can be achieved under the condition that the wireless side network element has local IP access capability and the user subscribes to allow local IP access.
  • the local access of the terminal to other IP devices or the Internet of the home network.
  • FIG. 3a is a schematic diagram 1 for providing local IP access through a local gateway
  • FIG. 3b is provided through a local gateway.
  • the local gateway can be combined with the wireless side network element (as shown in Figure 3a).
  • the local gateway can be configured not only with the home base station but also with the home base station gateway (as shown in FIG. 3b).
  • the local gateway may be a local SGW (L-SGW, Local SGW) and a local PGW (L-PGW, Local PGW), or may be a separate L-PGW.
  • the home base station gateway can be combined with the home base station.
  • the core network gateway may be a Serving GPRS Support Node (SGSN) or a Gateway GPRS Support Node (GGSN).
  • the local gateway may be a local GGSN (L-GGSN, Local GGSN) and a local SGSN (L-SGSN, Local SGSN), or may be a separate L-GGSN.
  • FIG. 4a is a schematic diagram of a local IP access data flow in the mobile communication system shown in FIG. 2a in the prior art
  • FIG. 4b is a prior art diagram.
  • the local IP access data flow diagram In the mobile communication system shown in 3a, the local IP access data flow diagram.
  • FIG. 5 is a schematic diagram of data flow of a local IP access broadband remote access server (BRAS) in a mobile communication system in the prior art, as shown in FIG. 5, and a bold one-dot chain line indicates local IP access.
  • the data stream, bold double-dotted line indicates the data stream connected to the core network.
  • the local IP access traffic is accessed through a fixed network device such as a BRAS, and the BRAS may also be compatible with the L-GW.
  • the fixed network and the mobile network marked in FIG. 5 may belong to different operators, or may belong to the same An operator.
  • Femtocell technology provides mobile users with better quality, faster speed and more services for users in indoor environments by means of fixed broadband access.
  • the user's data stream is accessed through the home base station, and the user's existing ADSL, LAN and other broadband connections are used. Send the user's data to the network.
  • the user's service data flows through the home base station and flows into the fixed network transmission node, for example, AN, BRAS, BNG, etc., which can flow to the mobile network or directly from the local fixed network.
  • Figure 6 shows the existing Schematic diagram of the data flow in the Femtocell via the local fixed network; in order to provide a better service experience for the user, it is necessary to provide the corresponding QoS quality of service for the data stream, which means that the data stream flows into various nodes, for example: fixed network
  • the resources of the transmission equipment and the mobile transmission equipment need to be guaranteed.
  • Femtocell and LIPA technologies are similar. When mobile users access through a home base station or base station, the data traffic of mobile users must pass through the fixed network, and these data QoS needs to be guaranteed.
  • the International Telecommunication Union-Telecommunications Standardization Sector (ITU-T) is the telecommunications sector of the International Telecommunication Union (ITU), which sets standards for resource access control.
  • ITU-T International Telecommunication Union-Telecommunications Standardization Sector
  • RAF Resource-Admission Control Functions
  • the RACF consists of two parts, namely the policy decision function entity (PD-FE (Policy Decision Functional Entity) and Transport Resource Control Functional Entity (TRC-FE), where TRC-FE interacts with the transmission function through Rc, and performs functional entities through Rn and transmission resources (TRE- FE, Transport Resource Enforcement Functional Entity); PD-FE interacts with TRC-FE through Rt, interacts with Customer Premises Network (CPN) through Rh, and performs functional entities (PE-FE, Policy Enforcement) through Rw and policy Functional Entity) interacts with the business layer's Service Control Functions (SCF) through Rs, interacts with the Network Attachment Control Functions (NACF) through Ru, and the PD-FE communicates with the other through the Ri interface.
  • SCF Service Control Function
  • NACF Network Attachment Control Functions
  • Ru Network Attachment Control Functions
  • Ru Network Attachment Control Functions
  • the PD-FE is independent of the transmission technology and has nothing to do with the SCF.
  • the PD-FE is based on the network policy rules, the service information provided by the SCF, the transport layer subscription information provided by the NACF, and the resource availability decision result provided by the TRC-FE. The final decision on resource acceptance control.
  • TRC-FE is not related to the business, but is related to transmission technology. TRC-FE is responsible for collecting and maintaining transmission Transmission network information and resource status information. Upon receiving the resource request from the PD-FE, the TRC-FE performs resource-based admission control based on QoS, priority requirements, resource availability information, and policy rules related to the transmission.
  • the transport layer consists of a Policy Enforcement Functional Entity (PE-FE) and a Transport Resource Enforcement Functional Entity (TRE-FE).
  • the PE-FE performs the policy rule delivered by the PD-FE.
  • the PE-FE is a packet-to-packet gateway. It can be located between the Customer Premises Network (CPN) and the access network, between the access network and the core network, or between the access network and the core network. Between different carrier networks, it is a key node that supports dynamic QoS control, port address translation control, and Network Address Translator (NAT) traversal.
  • the TRE-FE implements the transmission resource policy rule delivered by the TRC-FE. Its scope and function and the Rn interface need to be further studied, and are not in the scope of the R2 phase.
  • the Service and Protocol for Advanced Networking proposes that the Resource Admission Control Subsystem (RACS) solves the QoS problem of the NGN bearer network.
  • RACS Resource Admission Control Subsystem
  • TISPAN divides the NGN architecture into a service layer and a transport layer.
  • RACS Network Attachment Subsystem
  • the RACS solves the QoS problem of the NGN bearer network, while the NASS is responsible for providing the upper layer service layer.
  • the main functions of the TISPAN RACS are similar to those of the ITU-T RACF.
  • FIG 8 is a schematic diagram of the functional architecture of the TISPAN RACS.
  • the RACS associates the resource requirements of the service layer with the resource allocation of the transport layer, and mainly performs functions such as policy control, resource reservation, admission control, and NAT traversal.
  • the RACS provides the transport layer control service for the service layer through a series of QoS policies, so that the user equipment (UE, User Equipment) can obtain the required QoS guarantee.
  • UE User Equipment
  • RACS includes business-based policy decision-making functions (SPDF, Service-based Policy)
  • A-RACF Access-Resource and Admission Control Function
  • SPDF provides a unified interface to the application layer, shielding the underlying network topology and specific access types, and providing business-based policy control. SPDF selects the local policy according to the request of the application function (AF, Application Function), and maps the request to IP QoS parameters, and sends it to A-RACF and Border Gateway Function (BGF) to control the corresponding resources.
  • application function AF, Application Function
  • BGF Border Gateway Function
  • the A-RACF is located in the access network and has the function of admission control and network policy aggregation.
  • the request is received from the SPDF, and then the admission control is implemented based on the saved policy, accepting or rejecting the request for the transmission resource.
  • the A-RACF obtains the network attachment information and the user subscription information from the NASS through the e4 interface, so that the available network resources can be determined according to the network location information (for example, the address of the physical node of the access user), and the user is contracted when processing the resource allocation request. information.
  • the transport layer contains two functional entities: BGF, Resource Control Enforcement Function (RCEF). among them,
  • BGF Resource Control Enforcement Function
  • RCEF Resource Control Enforcement Function
  • the BGF is a packet-to-packet gateway that can be located between the access network and the core network (implementing the core border gateway function) or between the two core networks (implementing the interconnected border gateway function).
  • the BGF performs NAT traversal, gating, QoS marking, bandwidth throttling, usage measurement, and resource synchronization under the control of SPDF.
  • the RCEF is used to implement the Layer 2/Layer 3 (L2/L3) media stream policy defined by the access operator that the A-RACF transmits to the RCEF via the Re interface, and performs functions such as gating, QoS marking, and bandwidth limitation.
  • L2/L3 Layer 2/Layer 3
  • FIG 9 is a schematic diagram of a broadband policy control architecture (BPCF, Centralized Deployment Functional Architecture) proposed by the Broadband Forum (BBF), as shown in Figure 9, where the policy decision point (PDP, Policy Decision) Point), mainly used to formulate corresponding policies; Policy Enforcement Point (PEP), which is used to execute according to the corresponding policies formulated by the PDP; AAA server, for storage User signing information.
  • BPCF broadband policy control architecture
  • PDP Policy Decision Point
  • PDP Policy Enforcement Point
  • AAA server for storage User signing information.
  • the AF is used to formulate policies for the PDP and provide corresponding business information.
  • the main purpose of the present invention is to provide a method and system for implementing quality of service control, which can perform QoS control on traffic of data flows accessed by local IP, and avoids that these data streams occupy a large amount of network resources, thereby ensuring normal network.
  • quality of service control which can perform QoS control on traffic of data flows accessed by local IP, and avoids that these data streams occupy a large amount of network resources, thereby ensuring normal network.
  • a method of implementing quality of service control including:
  • the user subscription database of the fixed network sends the user subscription information corresponding to the user terminal to the policy decision function entity;
  • the policy decision function entity formulates the policy of the user terminal and sends it to the policy execution function entity.
  • the method Before the sending the user subscription information corresponding to the user terminal to the policy decision function entity, the method further includes:
  • the fixed network user subscription database sends a request to the subscription information repository of the home network, and the subscription information storage of the home network is performed.
  • the library returns the user subscription information to the user subscription database of the fixed network.
  • the method further includes: when the subscription information repository of the home network senses that the user subscription information changes, the method further includes: sending, by the subscription information repository of the home network, an update notification to the user subscription database of the fixed network;
  • the user subscription database of the fixed network sends an update notification to the policy decision function entity; A row function entity, the policy execution function entity performing a policy update operation.
  • the subscription information storage of the home network is a home subscriber server or a service subscription management network element (HSS or SPR).
  • HSS service subscription management network element
  • the user subscription database of the fixed network sends the user subscription information corresponding to the user terminal to the policy decision function entity, and further includes:
  • the user subscription database of the fixed network After receiving the internal or external trigger, the user subscription database of the fixed network sends the user subscription information corresponding to the user terminal to the policy decision function entity.
  • the trigger includes: a request from the policy decision function entity to trigger a user subscription database of the fixed network to deliver the subscription information of the user.
  • the method further includes: when the policy enforcement function entity perceives that the local IP access (LIPA) connection of the user terminal is released, the policy execution function entity deletes the user-related policy.
  • LIPA local IP access
  • the policy includes a quality of service QoS policy, and/or a charging policy
  • the parameters of the QoS policy include: a maximum bit rate AMBR, and/or a QoS level identification QCI, and/or an allocation reservation priority ARP, and/or a allowable usage quota.
  • the user subscription database of the fixed network is a network attach control function (NACF) server or a network attached subsystem (NASS) server or an authentication, authorized charging (AAA) server; and the policy decision function entity is a resource admission control function. (RACF) or resource admission control subsystem RACS or Policy Decision Point (PDP);
  • the policy enforcement function entity is a Policy Execution Function Entity (PE-FE) or a Resource Control Execution Function (RCEF) or a Decision Execution Point (PEP).
  • PE-FE Policy Execution Function Entity
  • RCEF Resource Control Execution Function
  • PEP Decision Execution Point
  • the present invention also provides a system for implementing quality of service control, the system comprising: a user subscription database of a fixed network, a policy decision function entity, and a policy execution function entity, wherein a user subscription database of the fixed network, configured to send the user subscription information corresponding to the user terminal to the policy decision function entity;
  • a policy decision function entity configured to receive user subscription information from a user subscription database of the fixed network, formulate a policy of the user terminal, and send the policy to the policy execution function entity;
  • a policy enforcement function entity that executes policies from a policy decision function entity.
  • the system further includes: a subscription information repository of the home network,
  • the user subscription database of the fixed network is further configured to send a request to the subscription information repository of the home network when the user does not have the current user subscription information or the user subscription information is incomplete; the subscription information storage database of the home network is used. After receiving the request from the fixed network user subscription database, the user subscription database of the fixed network returns the corresponding user subscription information.
  • the subscription information storage database of the home network is further configured to send an update notification to the user subscription database of the fixed network when the user subscription information changes.
  • the user subscription database of the fixed network is further configured to send an update notification to the policy decision function entity during the session;
  • the policy enforcement function entity is also used to perform policy update operations.
  • the subscription information storage of the home network is a home subscriber server or a service subscription management network element (HSS or SPR).
  • HSS service subscription management network element
  • the policy execution function entity is further configured to: when the LIPA connection of the user terminal is released, delete the policy related to the user.
  • the user subscription database of the fixed network is a NACF server or a NASS server or an AAA server;
  • the policy decision function entity is a RACF or a RACS or a PDP;
  • the policy enforcement function entity is a PE-FE or RCEF or PEP. It can be seen from the technical solution provided by the present invention that after the user terminal completes the authentication, the user subscription database of the fixed network sends the user subscription information corresponding to the user terminal to the policy decision function entity; the policy decision function entity formulates the user terminal. The policy is sent to the policy enforcement function entity.
  • the method of the invention realizes the control of the traffic of the data stream of the user accessing the fixed network, and avoids that the data stream occupies a large amount of network resources, thereby ensuring the normal service development and operation and maintenance of the network.
  • Figure 1 is a schematic diagram of the composition of an existing EPS architecture
  • FIG. 2a is a schematic diagram 1 of a connection of an HNB in a mobile communication network in the prior art
  • FIG. 2b is a schematic diagram 2 of a connection of an HNB in a mobile communication network in the prior art
  • FIG. 3a is a schematic diagram of providing access to a local IP through a local gateway. ;
  • Figure 3b is a schematic diagram 2 of providing local IP access through a local gateway
  • FIG. 4a is a schematic diagram of a local IP access data flow in the mobile communication system shown in FIG. 2a in the prior art
  • 4b is a schematic diagram of a local IP access data flow in the mobile communication system shown in FIG. 3a in the prior art
  • FIG. 5 is a schematic diagram of data flow of a local IP access BRAS in a mobile communication system in the prior art
  • FIG. 6 is a schematic diagram of data flow in a local Femtocell via a local fixed network
  • Figure 7 is a schematic diagram of the functional framework of the RACF
  • Figure 8 is a schematic diagram of the functional architecture of the TISPAN RACS
  • Figure 9 is a schematic diagram of the BPCF architecture proposed by BBF.
  • FIG. 10 is a flowchart of a method for implementing QoS control according to the present invention.
  • 11 is a schematic diagram of a method for QoS control based on an ITU-T standard protocol when a local IP access connection accesses a fixed network;
  • Figure 12 is a diagram of a TISPAN RACS based on a local IP access connection when accessing a fixed network. Schematic diagram of a method of QoS control of a standard protocol
  • FIG. 13 is a schematic diagram of a method for QoS control based on a BBF BPCF standard protocol when a local IP access connection is connected to a fixed network;
  • FIG. 14 is a schematic structural diagram of a system for implementing QoS control according to the present invention.
  • 15 is a flow chart of a first embodiment of QoS control based on an ITU-T standard protocol according to the present invention.
  • 16 is a flow chart of a second embodiment of QoS control based on an ITU-T standard protocol according to the present invention.
  • FIG. 17 is a flowchart of a first embodiment of QoS control based on the TISPAN RACS standard protocol according to the present invention.
  • FIG. 19 is a flowchart of a first embodiment of QoS control based on the BBF BPCF standard protocol according to the present invention.
  • Figure 20 is a flow chart showing a second embodiment of QoS control based on the BBF BPCF standard protocol of the present invention. detailed description
  • FIG. 10 is a flowchart of a method for implementing QoS control according to the present invention. As shown in FIG. 10, the following steps are included:
  • Step 1000 The user subscription database of the fixed network sends the user subscription information corresponding to the user terminal to the policy decision function entity.
  • the fixed network user subscription database receives an internal or external trigger, for example: a request from the policy decision function entity to trigger the fixed network user subscription database to subscribe to the user information. Disbursed.
  • the fixed network subscriber subscription database sends a request to the home network subscription information repository, such as the home subscriber server/service subscription management network element (HSS/SPR), and the HSS/SPR to the fixed network user.
  • the contract database returns the user subscription information.
  • Step 1001 The policy decision function entity formulates a policy of the user terminal, and sends the policy to the policy execution function entity.
  • the policy includes a QoS policy and/or a charging policy.
  • the method of the present invention further includes: when the HSS/SPR senses that the user subscription information changes, sending an update notification to the subscriber subscription database of the fixed network;
  • the policy decision function entity updates the policy and sends the updated policy to the policy execution function entity, and the policy is executed.
  • the functional entity performs a policy update operation.
  • the method of the present invention further includes: when the policy enforcement function entity perceives that the LIPA connection of the user terminal is released, the policy execution function entity deletes the policy related to the user.
  • the user's QoS policy parameters may include: an AMBR (Aggregate Maximum Bit Rate), and/or a QoS Class Identifier (QCI), and/or an allocation reservation priority ( ARP, Allocation and Retention Priority), and/or allow the use of related QoS information such as allowance.
  • AMBR Access Maximum Bit Rate
  • QCI QoS Class Identifier
  • ARP Allocation and Retention Priority
  • the method of the present invention is applicable to LIPA and Femtocell technologies.
  • the embodiment of the present invention is described by taking a local IP access connection to the fixed network as an example.
  • the application of the method of the present invention to the Femtocell technology is easily implemented by those skilled in the art, and will not be described in detail herein.
  • FIG. 11 is a schematic diagram of a method for QoS control based on the ITU-T standard protocol according to an example of a local IP access connection accessing a fixed network.
  • the user subscription database of the fixed network is a NACF server
  • the policy decision function entity is RACF
  • the policy execution function entity is PE-FE.
  • the bold one-dot chain line indicates the data flow of the local IP access
  • the bold two-dot chain line indicates the data stream connected by the core network.
  • the NACF server After the UE is authenticated, if the NACF server locally stores the user subscription information of the UE, the NACF server sends the user subscription information to the RACF, and the RACF formulates the policy of the UE and sends the policy to the PE-FE. If the NACF server does not have the user subscription information of the UE or the user subscription information is incomplete, the NACF server first sends a request to the HSS/SPR through the interface, and the HSS/SPR returns the user subscription information, and then the NACF server sends the RACF to the RACF. The QoS policy of the UE is formulated and sent to the PE-FE for execution.
  • the HSS/SPR When the HSS/SPR senses that the subscriber subscription information changes, the HSS/SPR sends an update notification to the NACF server. If the NACF server delivers the update notification to the RACF during the session, the RACF sends the updated policy to the PE-FE, and the PE-FE performs the policy update operation.
  • the PE-FE When the PE-FE senses that the LIP A connection of the UE is released, the PE-FE deletes the UE-related policy.
  • the QoS policy parameters of the UE may include: AMBR, and/or QCI, and/or ARP, and/or related QoS information such as the allowed usage quota.
  • FIG. 12 is a schematic diagram of a method for QoS control based on the TISPAN RACS standard protocol when the local IP access connection is connected to the fixed network.
  • the user subscription database of the fixed network is the NASS server
  • the policy decision function entity is the RACS.
  • the policy execution function entity is RCEF.
  • a bold one-dot chain line indicates the data flow of the local IP access
  • a bold two-dot chain line indicates the data stream connected by the core network.
  • the NASS server After the UE authentication is completed, if the NASS server locally stores the user subscription information of the UE, the NACF server sends the user subscription information to the RACS, and the RACS formulates the policy of the UE and sends the policy to the RCEF for execution. If the NASS server does not have the user subscription information or the user subscription information is not complete, the NASS server first sends a request to the HSS/SPR through the interface, and the HSS/SPR returns the user subscription information, and then the NACS server sends the information to the RACS. After the policy of the UE is formulated, it is sent to the RCEF for execution.
  • the HSS/SPR When the HSS/SPR senses that the user subscription information changes, the HSS/SPR sends an update notification to the NASS server. If during the session, the NASS server sends an update notification to RACS, RACS sends the updated policy to RCEF, and RCEF performs policy update operation. When the RCEF senses that the UE's LIPA connection is released, the RCEF deletes the UE-related policy.
  • the QoS policy parameters of the UE may include: AMBR, and/or QCI, and/or ARP, and/or related QoS information such as the allowed usage quota.
  • FIG. 13 is a schematic diagram of a method for QoS control based on the BBF BPCF standard protocol according to an example of a local IP access connection accessing a fixed network.
  • the user subscription database of the fixed network is an AAA server
  • the policy decision function entity is a PDP.
  • the policy enforcement point is PEP.
  • the bold one-dot chain line indicates the data flow of the local IP access
  • the bold two-dot chain line indicates the data flow of the core network connection.
  • the AAA server After the UE is authenticated, if the AAA server locally stores the user subscription information of the UE, the AAA server sends the user subscription information to the PDP, and the PDP formulates the policy of the UE and sends the policy to the PEP. If the AAA server does not have the user subscription information of the UE or the user subscription information is incomplete, the AAA server first sends a request to the HSS/SPR through the interface, and the HSS/SPR returns the user subscription information, and then the AAA server delivers the PDP to the PDP. After the policy of the UE is formulated, it is sent to the PEP for execution.
  • the HSS/SPR When the HSS/SPR senses that the subscriber subscription information changes, the HSS/SPR sends an update notification to the AAA server. If the AAA server delivers the update notification to the PDP during the session, the PDP sends the updated policy to the PEP, and the PEP performs the policy update operation.
  • the PEP When the PEP perceives that the UE's LIP A connection is released, the PEP deletes the UE-related policy.
  • the QoS policy parameters of the UE may include: AMBR, and/or QCI, and/or ARP, and/or related QoS information such as the allowed usage quota.
  • FIG. 14 is a schematic structural diagram of a system for implementing QoS control according to the present invention, as shown in FIG. 14, which mainly includes a user subscription database, a policy decision function entity, and a policy execution function entity of a fixed network, where
  • Fixed-line user subscription database used to receive the trigger, the user corresponding to the user terminal
  • the subscription information is sent to the policy decision function entity;
  • the user terminal is the user terminal that has completed the authentication.
  • a policy decision function entity configured to receive user subscription information from a user subscription database of the fixed network, formulate a policy of the user terminal, and send the policy to the policy execution function entity;
  • a policy enforcement function entity that executes policies from a policy decision function entity.
  • the system of the present invention further includes HSS/SPR, at this time,
  • the user subscription database of the fixed network is also used to send a request to the HSS/SPR when there is no user subscription information of the current user or the user subscription information is incomplete;
  • the HSS/SPR is configured to receive a request from a subscriber subscription database of the fixed network, and return a corresponding subscriber subscription information to the subscriber subscription database of the fixed network.
  • the HSS/SPR is also used to notify the user of the fixed network to send an update notification when the user subscription information changes.
  • the user subscription database of the fixed network is also used to send the update notification to the policy decision function entity during the session; the policy decision function entity is also used to update the policy and send the updated policy to the policy execution function entity;
  • the policy enforcement function entity is also used to perform policy update operations.
  • the policy execution function entity is further configured to delete the user-related policy when the LIPA connection of the user terminal is released.
  • the user subscription database of the fixed network is a NACF server or a NASS server or an AAA server
  • the policy decision function entity is a RACF or a RACS or a PDP
  • the policy execution function entity is a PE-FE or a RCEF or a PEP.
  • the policy includes a QoS policy as an example.
  • the NACF server receives an internal or external trigger (for example: receiving From the RACF request message), the user's subscription information needs to be sent to the RACF. If the NACF server locally stores user subscription information, the NACF server will use The user subscription information is sent to the RACF. The RACF sends the corresponding QoS policy to the PE-FE. If the NACF server does not have the user subscription information or the user subscription information is incomplete, the NACF server sends the HSS through the interface.
  • an internal or external trigger for example: receiving From the RACF request message
  • the SPR request, the HSS/SPR returns the user subscription information, and then is sent to the RACF by the NACF server.
  • the RACF formulates the corresponding QoS policy for the user and sends it to the PE-FE. As shown in FIG. 14, the specific includes:
  • Step 1500a The NACF server queries the local user subscription data to find the current user subscription information.
  • Step 1501a The NACF server sends the user subscription information of the current user to the RACF.
  • Step 1502a The RACF formulates a corresponding QoS policy for the user and sends the QoS policy to the PE-FE. If the NACF server does not save the current user subscription information or the user subscription information is incomplete, perform steps 1500b to 1506b.
  • Step 1500b The NACF server queries the local user subscription data. If the user subscription information is not found or the user subscription information is incomplete, the NACF server requests the current user subscription information from the HSS/SPR.
  • Step 1501b The NACF server requests user subscription information from the HSS/SPR.
  • Step 1502b The HSS/SPR queries the locally saved user subscription data, and finds the user subscription information of the user.
  • Step 1503b The HSS/SPR returns a response to the NACF server, where the response message carries the user subscription information of the current user.
  • Step 1504b The NACF server saves the received user subscription information. This step can also be omitted, that is, the NACF server may not save the received user subscription information;
  • Step 1505b The NACF server sends the received user subscription information to the RACF.
  • Step 1506b The RACF sends a corresponding QoS policy to the user and sends the information to the PE-FE.
  • FIG. 16 is a flowchart of a second embodiment of QoS control based on the ITU-T standard protocol according to the present invention. In this embodiment, after the HSS/SPR senses that the user subscription information changes, the NACF server is notified to update. As shown in FIG. 16, the specific includes:
  • Step 1600 The HSS/SPR senses that the user subscription information changes.
  • Step 1601 The HSS/SPR sends an update notification to the NACF server.
  • Step 1602 The NACF server sends an update notification to the RACF.
  • Step 1603 The RACF updates the corresponding QoS policy for the user whose subscriber subscription information changes.
  • Step 1604 The RACF sends an updated QoS policy to the PE-FE. After receiving the message, the PE-FE performs the corresponding update operation. End this process.
  • Step 1605 The PE-FE deletes the user-related QoS policy released by the LIPA connection.
  • FIG. 17 is a flowchart of a first embodiment of QoS control based on the TISPAN RACS standard protocol according to the present invention.
  • the NASS server receives an internal or external trigger, for example:
  • the RACS request message needs to send the user's subscription information to the RACS. If the NASS server has the user subscription information stored locally, the NASS server sends the user subscription information to the RACS.
  • the RACS sends the corresponding QoS policy to the RCEF. If the NASS server does not have the user subscription information or the user signs the contract. The information is incomplete.
  • the NASS server sends an HSS/SPR request through the interface.
  • the HSS/SPR returns the user subscription information, which is then sent to the RACS by the NASS server.
  • the RACS formulates the corresponding QoS policy for the user and sends it to the RCEF. As shown in Figure 17, the details include:
  • Step 1700a If the NASS server saves the user subscription information locally, go to Step 1700a to Step 1702a:
  • Step 1700a The NASS server queries the local user subscription data, and finds the current user subscription information.
  • Step 1701a The NASS server sends the user subscription information of the current user to the RACS.
  • Step 1702a The RACS formulates a corresponding QoS policy for the user and sends the QoS policy to the RCEF. If the NASS server does not save the current user subscription information or the user subscription information is not complete, go to steps 1700b to 1706b.
  • Step 1700b The NASS server queries the local user subscription data, and if the user subscription information is not found or the user subscription information is incomplete, the NASS server requests the current user subscription information from the HSS/SPR.
  • Step 1701b The NASS server requests user subscription information from the HSS/SPR.
  • Step 1702b The HSS/SPR queries the locally saved user subscription data, and finds the user subscription information of the user.
  • Step 1703b The HSS/SPR returns a response to the NASS server, where the response message carries the user subscription information of the current user.
  • Step 1704b The NASS server saves the received user subscription information. This step can also be omitted, that is, the NASS server may not save the received user subscription information;
  • Step 1705b The NASS server sends the received user subscription information to the RACS.
  • Step 1706b The RACS sends a corresponding QoS policy to the user and sends the QoS policy to the RCEF.
  • FIG. 18 is a flowchart of a second embodiment of QoS control based on the TISPAN RACS standard protocol.
  • the HSS/SPR senses that the user subscription information changes
  • the NASS server is notified to update. As shown in Figure 18, the details include:
  • Step 1800 The HSS/SPR senses that the user subscription information changes
  • Step 1801 The HSS/SPR sends an update notification to the NASS server.
  • Step 1802 The NASS server sends an update notification to the RACS.
  • Step 1803 The RACS updates the corresponding QoS policy for the user whose subscriber subscription information changes.
  • Step 1804 The RACS sends an updated QoS policy to the RCEF. After the RCEF receives the message, Perform the appropriate update operation. End this process.
  • the method further includes step 1605: the RCEF deletes the user-related QoS policy released by the LIPA connection.
  • FIG. 19 is a flowchart of a first embodiment of QoS control based on the BBF BPCF standard protocol according to the present invention.
  • the AAA server receives an internal or external trigger (for example: received from The PDP request message), the user needs to send the subscription information to the PDP. If the AAA server locally stores the user subscription information, the AAA server sends the user subscription information to the PDP. The PDP sends the user the corresponding QoS policy to the PEP. If the AAA server does not have the user subscription information or the user signing the contract. The information is incomplete.
  • the AAA server sends an HSS/SPR request through the interface. The HSS/SPR returns the user subscription information, and then the AAA server sends the information to the PDP.
  • the PDP sends the corresponding QoS policy to the user and sends the information to the PEP. As shown in Figure 19, the details include:
  • Step 1900a The AAA server queries the local user subscription data to find the current user subscription information.
  • Step 1901a The AAA server sends the user subscription information of the current user to the PDP.
  • Step 1902a The PDP formulates a corresponding QoS policy for the user, and sends the QoS policy to the PEP.
  • AAA server does not save the current user subscription information or the user subscription information is incomplete, perform steps 1900b to 1906b.
  • Step 1900b The AAA server queries the local user subscription data, and if the user subscription information is not found or the user subscription information is incomplete, the AAA server requests the HSS/SPR for the current user subscription information.
  • Step 1901b The AAA server requests user subscription information from the HSS/SPR.
  • Step 1902b The HSS/SPR queries the locally saved user subscription data to find the user's use. Household signing information;
  • Step 1903b The HSS/SPR returns a response to the AAA server, where the response message carries the user subscription information of the current user.
  • Step 1904b The AAA server saves the received user subscription information.
  • This step can also be omitted, that is, the AAA server may not save the received user subscription information.
  • Step 1905b The AAA server sends the received user subscription information to the PDP.
  • Step 1906b The PDP sends a corresponding QoS policy to the PEP.
  • FIG. 20 is a flowchart of a second embodiment of QoS control based on the BBF BPCF standard protocol in the present invention.
  • the AAA server is notified to update.
  • the specific includes:
  • Step 2000 The HSS/SPR senses that the user subscription information changes
  • Step 2001 The HSS/SPR sends an update notification to the AAA server;
  • Step 2002 The AAA server sends an update notification to the PDP.
  • Step 2003 The PDP updates the corresponding QoS policy for the user whose subscriber subscription information changes.
  • the method further includes the following step 1905: The PEP deletes the user-related QoS policy released by the LIPA connection.

Landscapes

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

Abstract

L'invention porte sur un procédé et sur un système de mise en œuvre de contrôle de qualité de service. Après authentification d'un terminal d'utilisateur, la base de données d'abonnement d'utilisateur du réseau fixe adresse les informations d'abonnement d'utilisateur correspondant au terminal d'utilisateur à l'entité fonctionnelle de décision stratégique; l'entité fonctionnelle de décision stratégique établit la stratégie du terminal d'utilisateur, et adresse la stratégie à l'entité fonctionnelle d'exécution de stratégie. Au moyen du procédé de la présente invention, on réalise la commande d'écoulement du flux de données pour les utilisateurs accédant au réseau fixe, et on évite l'occupation d'un grand nombre de ressources de réseau par le flux de données, afin d'assurer le développement et le fonctionnement normal des activités de réseau.
PCT/CN2010/079235 2010-01-15 2010-11-29 Procédé et système de mise en œuvre d'un contrôle de qualité de service WO2011085620A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010001240.5 2010-01-15
CN201010001240.5A CN102131240B (zh) 2010-01-15 2010-01-15 一种实现服务质量控制的方法及系统

Publications (1)

Publication Number Publication Date
WO2011085620A1 true WO2011085620A1 (fr) 2011-07-21

Family

ID=44269106

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/079235 WO2011085620A1 (fr) 2010-01-15 2010-11-29 Procédé et système de mise en œuvre d'un contrôle de qualité de service

Country Status (2)

Country Link
CN (1) CN102131240B (fr)
WO (1) WO2011085620A1 (fr)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103037408B (zh) * 2011-09-30 2015-12-16 华为终端有限公司 Ip业务流的切换方法、终端以及相应的功能实体
CN103209497B (zh) * 2012-01-11 2018-05-11 中兴通讯股份有限公司 一种策略会话建立方法及装置
CN103596272B (zh) 2012-08-13 2017-03-15 电信科学技术研究院 一种固定宽带网络的资源分配方法、装置及系统
US20160065575A1 (en) * 2013-04-28 2016-03-03 Zte Corporation Communication Managing Method and Communication System
CN109429272B (zh) * 2017-08-31 2022-02-11 华为技术有限公司 一种漫游场景下的分流方法及相关设备
CN112333802A (zh) * 2020-11-25 2021-02-05 吉视传媒股份有限公司 一种用于无线通讯设备的跨网络切换系统

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005029904A1 (fr) * 2003-09-15 2005-03-31 Qualcomm, Incorporated Systemes et procedes de determination d'un support de reseau domestique au moyen d'un serveur centralise
CN1774015A (zh) * 2004-11-08 2006-05-17 华为技术有限公司 为用户提供固网智能业务的方法及其系统

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005029904A1 (fr) * 2003-09-15 2005-03-31 Qualcomm, Incorporated Systemes et procedes de determination d'un support de reseau domestique au moyen d'un serveur centralise
CN1774015A (zh) * 2004-11-08 2006-05-17 华为技术有限公司 为用户提供固网智能业务的方法及其系统

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"IP Multimedia(IM) Subsystem Sh interface; Signalling flows and message contents (Release 8)", 3GPP TS 29.328 V8.7.0: TSG CORE NETWORK AND TERMINALS, December 2009 (2009-12-01), Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Specs/2009-12/Rel-8/29series/29328-870.zip> [retrieved on 20101205] *
HUANG YU ET AL.: "Solution for accessing IMS from fixed network.", MODEM SCIENCE & TECHNOLOGY OF TELECOMMUNICATIONS., no. 9, September 2007 (2007-09-01), pages 55 - 59,66 *

Also Published As

Publication number Publication date
CN102131240B (zh) 2014-12-17
CN102131240A (zh) 2011-07-20

Similar Documents

Publication Publication Date Title
WO2011095025A1 (fr) Procédé et système de commande de politique pour accès local d&#39;utilisateur mobile
WO2011085614A1 (fr) Procédé de gestion de ressources dans un réseau convergent à service complet et système correspondant
WO2012006909A1 (fr) Procédé et système de rapport d&#39;informations d&#39;accès à un réseau fixe
WO2011060698A1 (fr) Procédé et système de réalisation de contrôle de surveillance d&#39;utilisation
WO2009086734A1 (fr) Procédé pour sélectionner une entité à fonction de règles de politique et de facturation dans le scénario sans itinérance
WO2012065499A1 (fr) Procédé et système d&#39;établissement d&#39;un contrôle de qualité de service
WO2011029289A1 (fr) Procédé et système de transmission d&#39;un mode de commande de support dans des scénarios d&#39;itinérance
WO2008022602A1 (fr) Procédé, dispositif et système de commande de conditions d&#39;utilisation et de facturation
US20130094487A1 (en) Method and System for Information Transmission
WO2008128459A1 (fr) Procédé pour établir des supports par défaut de réseau sans fil et système pour celui-ci
WO2012097676A1 (fr) Procédé et système pour réaliser la détection et le contrôle d&#39;applications dans une session ip-can prenant en charge la double pile
WO2011085620A1 (fr) Procédé et système de mise en œuvre d&#39;un contrôle de qualité de service
WO2011147074A1 (fr) Procédé, système et dispositif associé pour la mise en œuvre d&#39;un contrôle de politique et de tarification
WO2011022893A1 (fr) Procédé et appareil d&#39;interaction entre des systèmes de commande de ressources et d&#39;admission
WO2014094488A1 (fr) Procédé et dispositif de gestion de politique de facturation destinés à un service local d&#39;itinérance
WO2014107985A1 (fr) Procédé de facturation en ligne de services d&#39;itinérance locale, h-ocs et v-ocs
WO2011088702A1 (fr) Procédé et système permettant de contrôler des ressources dans un réseau de convergence multiservice
WO2013135213A1 (fr) Procédé de traitement de session tdf et pcrf
WO2012129992A1 (fr) Procédé de traitement de connectivité de données sponsorisées, et fonction d&#39;imputation et de règles
WO2012010036A1 (fr) Procédé et système de contrôle de politique
WO2014071790A1 (fr) Procédé, dispositif et système destinés à un contrôle de politique d&#39;une convergence fixe-mobile
WO2010118673A1 (fr) Procédé, système et dispositif de gestion du contrôle des règles d&#39;utilisation et de facturation
WO2012003781A1 (fr) Procédé et système de contrôle d&#39;admission à un service
WO2011022961A1 (fr) Procédé d&#39;interaction entre des systèmes de commande de ressources et d&#39;admission et système de commande de ressources et d&#39;admission
WO2013082987A1 (fr) Procédé et système permettant d&#39;effectuer une commande de ressources sur des données allégées locales

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

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

Country of ref document: EP

Kind code of ref document: A1