WO2010081329A1 - Procédé et système pour réguler des ressources de réseau pendant une procédure de migration de flux de services - Google Patents

Procédé et système pour réguler des ressources de réseau pendant une procédure de migration de flux de services Download PDF

Info

Publication number
WO2010081329A1
WO2010081329A1 PCT/CN2009/073638 CN2009073638W WO2010081329A1 WO 2010081329 A1 WO2010081329 A1 WO 2010081329A1 CN 2009073638 W CN2009073638 W CN 2009073638W WO 2010081329 A1 WO2010081329 A1 WO 2010081329A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
resource
gateway
control information
bearer
Prior art date
Application number
PCT/CN2009/073638
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 WO2010081329A1 publication Critical patent/WO2010081329A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/61—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources taking into account QoS or priority requirements

Definitions

  • the present invention relates to the field of mobile communications, and in particular, to a method for controlling network resources when a service flow is migrated.
  • the 3rd Generation Partnership Project (3GPP) Evolved Packet System is an Evolved Universal Terrestrial Radio Access Network (Evolved Universal Terrestrial Radio Access Network).
  • E-UTRAN Mobility Management Entity (MME), Serving Gateway (S-GW), Packet Data Network Gateway (P-GW or PDN GW), Home Subscriber Server (HSS), 3GPP Authentication and Authorization and Accounting (AAA), Policy and Charging Rules Function (referred to as PCRF) consists of entities and other supporting nodes.
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • P-GW or PDN GW Packet Data Network Gateway
  • HSS Home Subscriber Server
  • AAA 3GPP Authentication and Authorization and Accounting
  • PCRF Policy and Charging Rules Function
  • the MME is responsible for control planes such as mobility management, processing of non-access stratum signaling, and management of user mobility management context
  • GW is an access gateway device connected to E-UTRAN, which forwards data between E-UTRAN and P-GW, and is responsible for buffering paging waiting data
  • P-GW is EPS and packet data network (Packet Data Network) , referred to as PDN)
  • PDN packet data network
  • the border gateway of the network responsible for PDN access and forwarding data between EPS and PDN
  • PCRF is a policy and charging rule function entity, which receives the interface Rx and the carrier network protocol (Internet Protocol, For example, the IP service network is connected to obtain the service information.
  • the gateway device in the network through the Gx/Gxa/Gxc interface, and is responsible for initiating the establishment of the IP bearer and ensuring the quality of service data (Quality of Service, referred to as QoS), and charge control.
  • QoS Quality of Service
  • EPS supports interworking with non-3GPP systems, where interworking with non-3GPP systems passes S2a/b/c Interface implementation, P-GW acts as an anchor between 3GPP and non-3GPP systems.
  • non-3GPP systems are classified into trusted non-3GPP IP access and untrusted non-3GPP IP access.
  • the trusted non-3GPP IP access can be directly connected to the P-GW through the S2a interface; the untrusted non-3GPP IP access needs to be connected to the P-GW through an Evolved Packet Data Gateway (ePDG), ePDG and
  • ePDG Evolved Packet Data Gateway
  • the S2c provides user plane-related control and mobility support between the user equipment (User Equipment, UE for short) and the P-GW.
  • the supported mobility management protocol supports dual stacks.
  • Mobile IPv6 Moblie IPv6 Support for Dual Stack Hosts and Routers, referred to as DSMIPv6.
  • the Policy and Charging Enforcement Function (PCEF) entity exists in the P-GW, and the Gx interface between the PCRF and the P-GW (see Figure 1) exchanges information.
  • PCEF Policy and Charging Enforcement Function
  • the S-GW also has a Bearer Binding and Event Report Function (BBERF) entity to perform QoS control on the service data flow, S-
  • BBERF Bearer Binding and Event Report Function
  • S- The information is exchanged between the GW and the PCRF through the Gxc interface (see Figure 1).
  • the BBERF is also resident in the trusted non-3GPP access gateway.
  • the trusted non-3GPP access gateway exchanges information with the PCRF through the Gxa interface (see Figure 1).
  • the S9 interface functions as an interface between the home PCRF and the visited PCRF, and provides an application function (Application Function, abbreviated as AF) for the UE, and sends the policy and charging control to the PCRF through the Rx interface.
  • Policy and Charging Control (referred to as PCC) policy business information.
  • PCC Policy and Charging Control
  • the corresponding PDN network can be found through the Access Point Name (APN).
  • a connection from a UE to a PDN network is usually referred to as an IP Connectivity Access Network (IP-Access) network.
  • IP-Access IP Connectivity Access Network
  • the BBERF and the PCEF respectively establish a Diameter session with the PCRF, and through these Diameter sessions, the policy charging information and the information for formulating the policy for controlling the IP-CAN session are transmitted.
  • the EPS supports the UE to access one PDN through multiple access networks at the same time, that is, Multiple Access.
  • the UE accesses the PDN through the same P-GW through the non-3GPP IP access network and the 3GPP access network under the coverage of the non-3GPP and 3GPP access.
  • the P-GW allocates an IP address to the UE, that is, there is only one IP-CAN session between the UE and the PDN. In this way, the data stream of different services requested by the UE can be transmitted in the access network suitable for its transmission.
  • the service data streams of Http and Ftp can access the network through the WiFi, and at the same time, the service data stream of the VoIP can be sent to the UE through the 3GPP.
  • services with lower real-time requirements such as Http and Ftp can take advantage of lower WiFi tariffs
  • services with higher real-time requirements for VoIP can take advantage of 3GPP QoS control and better mobility management.
  • users can use multiple services through different access systems at the same time. They can also dynamically migrate these service flows between access systems.
  • traffic flow migration may be wireless signal coverage factors (eg, multiple wireless signal coverage in 3GPP and non-3GPP indoors, and only 3GPP network signals in outdoor), when the covered network signal changes.
  • traffic flow migration may be wireless signal coverage factors (eg, multiple wireless signal coverage in 3GPP and non-3GPP indoors, and only 3GPP network signals in outdoor), when the covered network signal changes, Continuing to use certain services, the user wants to migrate some of the services in the source network to the target network. After the service migration ends, all the information related to the user in the source network should be released. In addition, service flow migration can also be caused by the user's will. At this time, the user is in the coverage of multiple access networks.
  • a solution to the existing network is to establish a default bearer first, and then perform a dedicated bearer setup.
  • Migration is a wireless signal coverage factor (eg, there are multiple wireless signal coverages in 3GPP and non-3GPP in the room, and only 3GPP network signals in the outdoor), which may make the bearer setup time longer.
  • the existing network can also establish the default bearer and the dedicated bearer together, and then let the user initiate the deletion of the service that is not desired to be migrated.
  • the method not only prolongs the flow migration process, increases the network processing burden, but may also Users charge more business usage fees, which reduces the user experience.
  • the present invention provides a method for controlling network resources during stream migration, so as to effectively enhance the controllable performance of network resources.
  • the present invention provides a method for controlling network resources during service flow migration, including: in a service flow migration process, a user terminal UE transmits resource control information to a gateway of a target network, and a gateway of a source network or a target network according to the The resource control information or the quality of service QoS policy corresponding to the resource control information controls the network resources of the network in which the network is located.
  • the gateway of the target network is a packet data network gateway P-GW shared by the source network and the target network;
  • the resource control information is a resource release indication;
  • the step of the source network or the gateway of the target network controlling the network resources of the network according to the resource control information or the QoS policy corresponding to the resource control information includes: the P-GW according to the The resource release indication determines whether to delete the source network resource from the network resource of the source network, and if so, performs a release operation.
  • the resource control information is transmitted by the UE through the network element in the process of establishing a default bearer, a 3GPP modify bearer resource, a trusted non-3GPP setup connection, an untrusted non-3GPP setup connection, or a 3GPP setup PDN connection.
  • the P-GW is a default bearer, a 3GPP modify bearer resource, a trusted non-3GPP setup connection, an untrusted non-3GPP setup connection, or a 3GPP setup PDN connection.
  • the process of modifying a bearer resource by the 3GPP is a process of establishing a dedicated bearer.
  • the bearer resource modification request sent by the UE to the mobility management unit MME carries the resource release indication, where the resource release indication sequentially passes the bearer resource modification request sent by the MME to the S-GW, and the S-GW sends the request to the P
  • the bearer resource modification request or the proxy binding update message sent by the GW is uploaded to the P-GW.
  • the P-GW acquires the resource release indication in the process of establishing the last dedicated bearer.
  • the resource release indication is carried by using a protocol configuration option PCO, including a network coverage identifier, a handover scenario identifier, a deletion operation identifier, or a network identifier of a resource to be released.
  • a protocol configuration option PCO including a network coverage identifier, a handover scenario identifier, a deletion operation identifier, or a network identifier of a resource to be released.
  • the resource control information is sent by the UE to a gateway of the target network in a process of default bearer establishment, PDN connection establishment, or dedicated bearer establishment, where the resource control information includes a need to be established and/or deleted.
  • the step of the source network or the gateway of the target network controlling the network resources of the network according to the resource control information or the QoS policy corresponding to the resource control information includes: The target network gateway initiates a setup operation of the corresponding bearer according to the QoS policy corresponding to the resource control information; the source network gateway releases the source network resource corresponding to the flow information.
  • the resource control information is transmitted by the UE to a target network gateway and a public gateway in a process of default bearer establishment, PDN connection establishment, or dedicated bearer establishment, where the public gateway refers to a packet data network gateway P-GW.
  • the resource control information includes flow information that needs to be established and/or deleted.
  • the step of the source network or the gateway of the target network controlling the network resources of the network according to the resource control information or the QoS policy corresponding to the resource control information includes: the target network gateway according to the QoS policy Initiating an establishing operation of the corresponding bearer; the P-GW releasing the source network resource corresponding to the flow information.
  • the quality of service QoS policy is obtained by the policy and charging rule function PCRF or statically configured.
  • the source network or the target network gateway refers to a gateway where the bearer binding and event reporting function BBERF or the policy and charging execution function PCEF is located.
  • the service flow information is carried by the protocol configuration option PC0, and includes a service template flow TFT information, a message filter identifier, or a QoS parameter.
  • the present invention also provides a system for controlling network resources when a service flow is migrated, where the system includes a gateway of the source network and a gateway of the target network, where
  • the gateway of the source network is configured to perform control operations on network resources of the source network according to resource control information or a quality of service QoS policy corresponding to the resource control information;
  • the gateway of the target network is configured to receive resource control information transmitted by the user terminal, and perform control operations on the network resources of the target network according to the received resource control information or a QoS policy corresponding to the resource control information.
  • the resource control information is a resource release indication
  • the system further includes: a mobility management unit MME and a serving gateway S-GW; wherein the MME is configured to receive a bearer resource modification request that is sent by the user terminal and that carries the resource release indication, and send the request to the S-GW;
  • the S-GW is configured to receive a bearer resource modification request that is sent by the MME and that carries a resource release indication, and send a bearer resource modification request or a proxy binding update message that carries a resource release indication to the P-GW;
  • the P-GW is configured to determine whether to delete the source network resource according to the resource release indication, and if yes, perform a release operation.
  • the gateway of the target network is configured to receive resource control information, and initiate a corresponding bearer according to the QoS policy corresponding to the received resource control information.
  • the gateway of the source network is configured to release source network resources corresponding to the service flow information.
  • the gateway of the target network is configured to receive resource control information, and initiate a corresponding bearer according to the QoS policy corresponding to the received resource control information.
  • the establishing operation is performed to release the source network resource corresponding to the service flow information.
  • the network resource is controlled by the network gateway.
  • the network gateway having the knowledge of the network resources of the source network and the target network acquires resource control information, and performs network resource according to the resource control information.
  • the control operation effectively saves the service flow migration process, improves the network operation efficiency, and effectively enhances the controllable performance of the network resources.
  • Figure 1 is a schematic diagram of the EPS system architecture.
  • Figure 2 is a schematic diagram of a multi-access scenario.
  • Figure 3 is a flow chart of the first embodiment of the present invention.
  • Embodiment 4 is a flow chart of Embodiment 2 of the present invention.
  • Figure 5 is a flow chart of the third embodiment of the present invention.
  • Figure 6 is a flow chart of Embodiment 4 of the present invention.
  • Figure 7 is a flow chart of Embodiment 5 of the present invention.
  • Figure 8 is a flow chart of Embodiment 6 of the present invention.
  • Figure 9 is a flow chart of Embodiment 7 of the present invention.
  • Figure 10 is a flow chart of Embodiment 8 of the present invention.
  • Figure 11 is a flow chart of Embodiment 9 of the present invention.
  • the user terminal UE transmits resource control information to a gateway of the target network, and the gateway of the source network or the target network according to the resource control information or corresponding
  • the quality of service QoS policy controls the network resources of the network in which it resides.
  • the method of the present invention can control the resources of the source network and the target network.
  • the source network referred to in the present invention refers to the network system before the service flow migration; the target network refers to the network system after the service flow migration.
  • the resource control information referred to in the present invention may be a resource release indication or a service flow information.
  • the resource release indication of the present invention indicates that the UE informs the network side whether it is necessary to release the UE-related resources of the source network, and does not judge the control (eg, establishment or deletion) of the target network resource, and only the public gateway P- in the target network.
  • the GW is aware of the source network resources of the UE. For example, the P-GW saves the bearer information of the UE in the source network. Therefore, the resource release indication needs to notify the P-GW during the process of establishing the target network bearer during the flow migration. - The GW determines whether to perform source network resource deletion and performs corresponding processing operations.
  • the resource control information is transmitted by the user terminal UE via the network element in the process of establishing a default bearer, a 3GPP modify bearer resource, a trusted non-3GPP setup connection, an untrusted non-3GPP setup connection, or a 3GPP setup PDN connection. P-GW.
  • a default bearer a 3GPP modify bearer resource
  • a trusted non-3GPP setup connection a trusted non-3GPP setup connection
  • an untrusted non-3GPP setup connection or a 3GPP setup PDN connection.
  • P-GW 3GPP setup PDN connection.
  • Embodiment 1 Figure 3 is a flow chart of the first embodiment of the present invention.
  • the UE first accesses the P-GW through the trusted non-3GPP access network. After the UE decides to migrate some service flows from the non-3GPP access network to the 3GPP access network, the default bearer establishment is performed in the 3GPP access network. Process.
  • the core network can use the PMIPv6 protocol, the GTP (General Tunneling Protocol) or the DSMIP protocol.
  • the scenario in which the 3GPP core network uses the PMIP protocol is taken as an example.
  • Other implementation scenarios, such as the use of the GTP and the DSMIP protocol are very similar to the embodiment, and do not affect the description of the present invention. Therefore, it is not repeated here.
  • the P-GW obtains the resource release indication in the following manner: when the 3GPP default bearer is established, the user terminal UE carries the resource release indication in an attach request sent by the node eNB; the resource release indication sequentially passes An attach request sent by the eNB to the mobility management unit MME, a default bearer request sent by the MME to the serving gateway S-GW, and a default bearer request or proxy binding sent by the S-GW to the P-GW. An update message is uploaded to the P-GW.
  • the specific steps of this embodiment are described as follows:
  • Step 301 The UE accesses through a trusted non-3GPP system, and related services are transmitted on the connection.
  • Step 302 The UE decides to migrate some service flows from the non-3GPP system to the 3GPP access system according to the local policy.
  • Step 303 The UE sends an attach request message to the MME, and carries a resource release indication.
  • Step 305 The MME sends a default bearer setup request message to the S-GW, and carries a resource release indication.
  • Step 306 The S-GW initiates a gateway control session establishment to the PCRF, and obtains the rule information required for the bearer binding.
  • Step 307 The S-GW sends a proxy binding update request message to the P-GW, where the proxy binding update request message carries the NAI, the APN, and the resource release indication.
  • Step 308 A Diameter session established between the P-GW of the PCEF and the PCRF is stored, and an "IP-CAN Session Modification" message is sent to the PCRF, and the PCRF returns an "IP-CAN Session Tampering Confirmation” message to the P-GW.
  • Step 309 the P-GW processes the binding update, and returns a "proxy binding acknowledgement" message to the S-GW, carrying the IP address assigned by the P-GW to the UE;
  • Step 310 The S-GW returns a default bearer setup confirmation message to the MME, where the default bearer setup acknowledgement message carries the IP address of the UE.
  • Step 311 The MME, the eNodeB, and the UE interact to establish a radio bearer.
  • Step 312 After the radio bearer is established, the MME sends an update bearer request to the S-GW, notifies the address information of the eNodeB, and the S-GW returns a response message.
  • Step 313 The P-GW initiates a non-3GPP access system resource release process according to the resource release indication carried in the Proxy Binding Update request message (see step 307). This release process can occur after step 308.
  • Embodiment 4 is a flow chart of Embodiment 2 of the present invention.
  • the UE has accessed the same P-GW through the trusted non-3GPP and the 3GPP access network. After the UE decides to migrate some service flows from the non-3GPP access network to the 3GPP access network, the UE initiates in the 3GPP access network. The process of establishing a proprietary bearer.
  • the GTP protocol is used between the S-GW and the P-GW through 3GPP access.
  • the P-GW obtains the resource release indication in the following manner:
  • the user equipment UE carries the resource in the bearer resource modification request sent by the mobility management unit MME.
  • a release indication the resource release indication is sequentially uploaded to the S-GW by using a bearer resource modification request sent by the MME to the S-GW, and the S-GW sends a bearer resource modification request to the P-GW or a proxy strap update message to the P-GW.
  • the S-GW After receiving the specific bearer setup request sent by the MME, the S-GW sends a proxy binding update message to the P-GW, and the P-GW responds to the S-GW with a binding acknowledgement message.
  • the specific steps of the second embodiment are described as follows:
  • Step 401 The UE accesses the same P-GW through the 3GPP and the non-3GPP access network, and related services are transmitted through the non-3GPP system.
  • Step 402 The UE decides to migrate some service flows from the non-3GPP system to the local policy.
  • Step 403 The UE sends a bearer resource modification request to the MME, to establish a dedicated bearer, where the resource release indication is carried.
  • Step 405 The S-GW sends a bearer resource modification request to the P-GW to establish a dedicated bearer, and carries a resource release indication.
  • Step 406 The P-GW interacts with the PCRF to start performing an IP-CAN session update.
  • Step 407 The P-GW initiates a process of establishing a dedicated bearer.
  • Step 408 After the establishment of the dedicated bearer is completed, the P-GW informs the PCRF policy execution result, and the IP-CAN session update ends.
  • Step 409 The P-GW initiates a non-3GPP system resource release process according to the resource release indication carried in the dedicated bearer setup request (see step 405). This release process can occur after step 406.
  • FIG. 5 is a flowchart of Embodiment 3 of the present invention.
  • the UE has accessed the same P-GW through the trusted non-3GPP and the 3GPP access network. After the UE decides to migrate some service flows from the non-3GPP access network to the 3GPP access network, the UE initiates in the 3GPP access network. The process of establishing a proprietary bearer. The PMIP protocol is adopted between the S-GW and the P-GW through 3GPP access. The specific steps are described as follows:
  • Step 501 The UE accesses the same P-GW through the 3GPP and the non-3GPP access network, and related services are transmitted through the non-3GPP system.
  • Step 502 The UE decides to migrate some service flows from the non-3GPP system to the 3GPP access system according to the local policy.
  • Step 503 The UE sends a bearer resource modification request to the MME, to establish a dedicated bearer, where the resource release indication is carried;
  • Step 504 The MME sends a bearer resource modification request to the S-GW to establish a dedicated bearer, and also carries a resource release indication.
  • Step 505 The S-GW initiates a request for a gating and a QoS policy to the PCRF.
  • Step 506 The S-GW sends a proxy binding update message to the P-GW, and carries a resource release indication.
  • Step 507 The P-GW returns a proxy binding update response.
  • Step 508 The S-GW initiates a process for establishing a 3GPP dedicated bearer.
  • Step 509 After the establishment of the dedicated bearer is completed, the S-GW informs the PCRF policy execution result, and the gating and QoS policy execution process ends.
  • Step 510 The PCRF updates the QoS policy to the P-GW.
  • Step 511 The P-GW initiates a non-3GPP system resource release process according to the resource release indication carried in the proxy binding update message (see step 506).
  • FIG. 6 is a flow chart of Embodiment 4 of the present invention.
  • the UE first accesses the EPS system through the 3GPP access network, and after the UE decides to migrate certain service flows from the 3GPP access network to the trusted non-3GPP access network, the connection establishment is performed in the trusted non-3GPP access network. Process.
  • the PMIPv6 protocol is used between the trusted non-3GPP access network and the P-GW.
  • the P-GW obtains the resource release indication in the following manner:
  • the user terminal UE carries the resource release indication in the attach request sent by the trusted non-3GPP access gateway.
  • the resource release indication is sent to the P-GW by using a proxy strap update message sent by the trusted non-3GPP access gateway to the P-GW.
  • Step 601 The UE accesses the EPS system through the 3GPP access network, and related services are transmitted on the connection, where the S-GW and the P-GW establish a data channel through the GTP or the PMIPv6 protocol.
  • Step 602 The UE decides to migrate some service flows from the 3GPP system to the non-3GPP access system according to the local policy.
  • Step 603 The UE performs a specific non-3GPP access procedure, and accesses the trusted non-3GPP access network.
  • Step 604 After the UE accesses the trusted non-3GPP access network, request the EPS access authentication from the HSS/AAA; after the HSS/AAA receives the EPS access authentication request, perform authentication on the requesting UE; After the HSS/AAA completes the authentication of the UE, sending, to the trusted non-3GPP access gateway, the APN that is selected by the P-GW and the UE that is selected in the 3GPP access, including the default APN;
  • Step 605 after the authentication succeeds, the attach procedure of layer 3 is triggered, and the UE provides trusted access.
  • the message sent by the gateway carries a resource release indication.
  • Step 606 Perform a gateway control session establishment process between the trusted non-3GPP access gateway and the PCRF.
  • Step 607 The trusted non-3GPP access gateway sends a proxy binding update request message to the P-GW, where the proxy binding update request message carries the NAI, the APN, and the resource release indication.
  • Step 608 Perform an IP-CAN session modification process between the P-GW and the PCRF.
  • Step 609 The P-GW returns a "proxy binding acknowledgement" message to the trusted non-3GPP access gateway, where the "proxy binding acknowledgement” message carries the IP address allocated by the P-GW to the UE;
  • Step 610 The trusted non-3GPP access gateway returns a response message to the UE, where the response message carries the IP address of the UE.
  • Step 611 The p_GW initiates a 3GPP access system resource release process according to the resource release indication carried in the proxy binding update request message (see step 607).
  • FIG. 7 is a flow chart of Embodiment 5 of the present invention.
  • the UE first accesses the EPS system through the 3GPP access network, and after the UE decides to migrate certain service flows from the 3GPP access network to the trusted non-3GPP access network, the connection establishment is performed in the trusted non-3GPP access network. Process. When the non-3GPP access is trusted, the UE uses DSMIPv6 access.
  • the P-GW obtains the resource release indication as follows:
  • the user terminal UE sends a strap update message to the P-GW, where the resource release indication is carried.
  • the specific steps in this embodiment are described as follows: Step 701: The UE accesses the EPS system through the 3GPP access network, and related services are transmitted on the connection, where the S-GW and the P-GW are established through the GTP or the PMIPv6 protocol. Data channel
  • Step 702 The UE decides to migrate some service flows from the 3GPP system to the non-local according to the local policy.
  • Step 703 layer 2 access.
  • the UE accesses the trusted non-3GPP access network, and the HSS/AAA performs access authentication and authorization for the UE;
  • the access system allocates an IP address to the UE as the care-of address CoA of the UE;
  • Step 705 The UE performs a DNS query according to the APN, and obtains an IP address of the P-GW that provides the access service network. A security association is established between the UE and the P-GW, and the home address HoA is assigned to the UE.
  • the P-GW interacts with the HSS to perform an authentication and authorization process;
  • Step 706 The UE sends a “Binding Update” request message to the P-GW, and carries a resource release indication.
  • Step 707 The P-GW returns a “Binding Confirmation” message to the trusted non-3GPP access gateway.
  • FIG 8 is a flow chart of Embodiment 6 of the present invention.
  • the UE first accesses the EPS system through the 3GPP access network. After the UE decides to migrate certain service flows from the 3GPP access network to the untrusted non-3GPP access network, the UE connects through the untrusted non-3GPP access network through the ePDG. Established process. When the non-trusted non-3GPP access is used, an IPSec tunnel is established between the UE and the ePDG, and PMIPv6 is used between the ePDG and the P-GW.
  • the P-GW obtains the resource release indication in this manner: when the untrusted non-3GPP connection is established, the tunnel establishment request sent by the user terminal UE to the ePDG carries the resource release message and is uploaded to the P- GW.
  • the specific steps of this embodiment are described as follows:
  • Step 801 The UE accesses the EPS system through the 3GPP access network, and related services are transmitted on the connection, where the S-GW and the P-GW establish a data channel through the GTP or the PMIPv6 protocol.
  • Step 802 The UE decides to migrate some service flows from the 3GPP system to the non-3GPP access system according to the local policy.
  • Step 803 The UE obtains an address of the ePDG through a DNS query, and initiates IKEv2 to the ePDG.
  • Step 804 After the authentication succeeds, the attach procedure of layer 3 is triggered, and the ePDG sends a “binding update” request message to the P-GW, and carries a resource release indication.
  • Step 805 the P-GW processes the binding update, returns a "binding acknowledgement" message to the ePDG, and brings the IP address assigned to the UE to the ePDG in the message;
  • Step 806 after the binding update is successfully completed, the ePDG is successfully authenticated by the UE, and the IPsec tunnel is established.
  • Step 807 The ePDG sends IKEv2 signaling, and brings the IP address allocated to the UE to the UE.
  • the IP connection from the UE to the P-GW is established.
  • Step 808 The P-GW initiates a 3GPP access system resource release process according to the resource release indication carried in the “Binding Update” request message (see step 804).
  • the process only needs to replace the attach request of FIG. 3 and FIG. 6 with the PDN connection establishment request, and the resource release indication is carried in the PDN connection establishment request, and is established with the default bearer.
  • the embodiment is very similar.
  • the P-GW obtains the resource release indication in the following manner:
  • the PDN connection request sent by the user terminal UE to the eNB carries the resource release indication, where the resource is Release the indication by the PDN connection request of the eNB to the MME, the establishment of the default bearer request sent by the MME to the S-GW, and the default bearer setup request or the proxy strap update message sent by the S-GW to the P-GW.
  • the P-GW obtains the resource release indication in the following manner:
  • the PDN connection request sent by the user terminal UE to the eNB carries the resource release indication, where the resource is Release the indication by the PDN connection request of the eNB to the MME, the establishment of the default bearer request sent by the MME to the S-GW, and the default bearer setup request or the proxy strap update message sent by the S-GW to the P-GW.
  • the source network represents the network system in which the traffic flow was prior to migration.
  • the indication may include one or more network identifiers of the resources that should be released.
  • the resource release indication needs to be carried when the last dedicated bearer is established.
  • the indication that the UE informs the P-GW to delete the source network resource may be carried in the message by using a protocol configuration option PCO, where the resource release indication may be: a network coverage identifier, a handover scenario identifier, a deletion operation identifier, a migration or/and a need Deleted stream information.
  • the resource release indication is carried by using a protocol configuration option PCO, including a network coverage identifier, a handover scenario identifier, a deletion operation identifier, or a network identifier to be released.
  • PCO protocol configuration option
  • the P-GW deletes the network resources related to the flow information to be migrated or/and deleted.
  • the P-GW does not obtain the resource release indication, or according to the indication that the source network resource does not need to be deleted, the P-GW does not initiate the release of the source network resource, or only releases the network bearer without any service flow transmission in the source network.
  • Embodiment 7 shows a scenario in which the resource control information is service flow information: Embodiment 7
  • FIG 9 is a flow chart of Embodiment 7 of the present invention.
  • the UE first accesses the P-GW through the trusted non-3GPP access network (the core network uses the PMIP protocol), and after the UE decides to migrate some service flows from the non-3GPP access network to the 3GPP access network, the UE is connected in the 3GPP.
  • the core network uses the GTP (General Tunneling Protocol) protocol.
  • GTP General Tunneling Protocol
  • the P-GW obtains the service flow information in the following manner:
  • the user terminal UE carries the attach request or the PDN connection setup request sent by the node eNB to carry the Traffic flow information, which in turn passes an attach request or a PDN connection establishment request sent by the eNB to the MME, a default bearer request sent by the MME to the S-GW, and a default bearer setup request of the S-GW to the P-GW or A proxy binding update message is uploaded to the P-GW.
  • the specific steps of this embodiment are described as follows:
  • Step 901 The UE accesses through a trusted non-3GPP system, and related services are transmitted on the connection.
  • Step 902 The UE decides to migrate some service flows from the non-3GPP system to the local policy according to the local policy.
  • Step 903 The UE sends an attach request message to the MME, and carries the service flow information that needs to be migrated or/and needs to be deleted.
  • Step 904 Perform UE access authentication and location update by using an HSS.
  • Step 905 The MME sends a default bearer setup request message to the S-GW, and carries the service flow information that needs to be migrated or/and needs to be deleted.
  • Step 906 The S-GW sends a default bearer setup request message to the P-GW, where the message carries service flow information to be migrated or/and deleted.
  • Step 907 The P-GW may interact with the PCRF to perform an IP-CAN session update to trigger a PCC decision corresponding to the flow information carried in step 906, that is, a QoS policy.
  • Step 908 The P-GW initiates a default bearer setup response. At the same time, the P-GW allocates the bearer layer QoS according to the QoS policy returned by the PCRF or uses the locally configured QoS policy, and initiates a dedicated bearer setup procedure corresponding to the migrated flow information.
  • Step 909 The S-GW sends a default bearer setup response to the MME, and a request for establishing a dedicated bearer.
  • Step 910 The MME, the eNodeB, and the UE interact to establish a radio bearer, including a default bearer and a dedicated bearer.
  • Step 911 After the radio bearer is established, the MME sends an update bearer request to the S-GW, notifies the address information of the eNodeB, and the S-GW returns a response message; and the S-GW sends a response to the P-GW in response to the dedicated bearer;
  • Step 912 The non-3GPP access gateway deletes the service flow from the existing bearer according to the QoS policy returned by the PCRF, and releases the network bearer without any service flow transmission in the non-3GPP access system, so as to perform control processing on the trusted non-3GPP connection.
  • the P-GW releases the resources corresponding to the non-3GPP access system according to the mobility information carried in step 906 to be migrated or/and to be deleted.
  • FIG 10 is a flowchart of Embodiment 8 of the present invention.
  • the UE first accesses the P-GW through the trusted non-3GPP access network (the core network uses the PMIPv6 protocol), and after the UE decides to migrate some service flows from the non-3GPP access network to the 3GPP access network, the UE is connected in the 3GPP.
  • the core network uses the PMIP protocol.
  • the S-GW obtains the service flow information in the following manner: when the 3GPP default bearer setup or the PDN connection is established, the user terminal UE carries the attach request or the PDN connection setup request sent by the node eNB to carry the The service flow information is sequentially set by the eNB to the MME to send an attach request or a PDN connection setup request, and the MME sends a default bearer request to the S-GW.
  • the specific steps of this embodiment are described as follows:
  • Step 1001 The UE accesses through a trusted non-3GPP system, and related services are transmitted on the connection.
  • Step 1003 The UE sends an attach request message to the MME, where the flow information that needs to be migrated or/and needs to be deleted is carried.
  • Step 1004 Perform UE access authentication and location update by using an HSS.
  • Step 1005 The MME sends a default bearer setup request message to the S-GW, and carries the flow information to be migrated or/and deleted.
  • Step 1006 The S-GW initiates a gateway control session establishment to the PCRF.
  • Step 1007 the S-GW sends a "Proxy Binding Update" request message to the P-GW, where the "Proxy Binding Update” request message carries the NAI and the APN;
  • Step 1008 A Diameter session established between the P-GW and the PCRF residing the PCEF, sending an "IP-CAN Session Modification” message to the PCRF, and the PCRF returns an "IP-CAN Session Modification Confirmation” message to the P-GW, carrying the QoS. rule.
  • Step 1009 The P-GW processes the binding update, and returns a “proxy binding acknowledgement” message to the S-GW, and carries the IP address allocated by the P-GW to the UE.
  • Step 1010 The PCRF interacts with the S-GW to perform a gateway control session modification process, and the S-GW sends the flow information to the PCRF in step 1005, and obtains the QoS rule corresponding to the migrated flow information.
  • Step 1011 The S-GW sends the QoS rule to the MME.
  • the default bearer establishes a response, and according to the QoS rule or the local policy returned by the PCRF, performs a dedicated bearer establishment process corresponding to the migrating flow information;
  • the MME, the eNodeB, and the UE interact to establish a radio bearer, including a default bearer and a dedicated bearer. ;
  • Step 1012 After the establishment of the dedicated bearer is completed, the P-GW informs the PCRF policy execution result, and the gateway control and the QoS rule execution process ends.
  • Step 1013 The trusted non-3GPP access gateway deletes the service flow from the existing bearer according to the QoS policy provided by the PCRF, and releases the network bearer without any service flow transmission in the non-3GPP access system, so as to control the trusted non-3GPP connection. deal with.
  • Example nine Figure 11 is a flow chart of Embodiment 9 of the present invention.
  • the UE first accesses the EPS system through the 3GPP access network (the core network uses the GTP protocol), and after the UE decides to migrate certain service flows from the 3GPP access network to the trusted non-3GPP access network, the trusted non-3GPP The process of establishing a connection in the access network.
  • the PMIPv6 protocol is used between the trusted non-3GPP access network and the P-GW.
  • Step 1101 The UE accesses the EPS system through the 3GPP access network, and related services are transmitted on the connection, where the S-GW and the P-GW establish a data channel through the GTP protocol.
  • Step 1102 The UE decides to migrate certain service flows from the 3GPP system to the non-3GPP access system according to the local policy.
  • Step 1103 The UE performs a specific non-3GPP access procedure, and accesses the trusted non-3GPP access network.
  • Step 1104 After the UE accesses the trusted non-3GPP access network, request the EPS access authentication from the HSS/AAA; after the HSS/AAA receives the EPS access authentication request, perform authentication on the requesting UE; After the HSS/AAA completes the authentication of the UE, sending, to the trusted non-3GPP access gateway, the APN that is selected by the P-GW and the UE that is selected in the 3GPP access, including the default APN;
  • Step 1105 After the authentication succeeds, the attach procedure of layer 3 is triggered, and the message sent by the UE to the trusted access gateway carries the flow information to be migrated or/and deleted.
  • Step 1106 Perform a gateway control session establishment process between the trusted non-3GPP access gateway and the PCRF.
  • Step 1107 the trusted non-3GPP access gateway sends a "proxy binding update” request message to the P-GW, where the "proxy binding update” request message carries the NAI and the APN;
  • Step 1108 Perform an IP-CAN session modification process between the P-GW and the PCRF.
  • Step 1109 The P-GW returns a "Proxy Binding Acknowledgement" message to the trusted non-3GPP access gateway, where the "Proxy Binding Acknowledgement” message carries the IP address assigned by the P-GW to the UE;
  • Step 1110 PCRF Interacting with the trusted non-3GPP access gateway to perform the gateway control session modification process, the trusted non-3GPP access gateway sends the flow information to the PCRF in step 1105, and the PCRF provides the trusted non-3GPP access gateway with the step 1105 carrying the required migration flow.
  • Information corresponding QoS rules
  • Step 1111 The trusted non-3GPP access gateway returns a response message to the UE, where the response message carries the IP address of the UE.
  • the trusted non-3GPP access gateway performs a corresponding bearer establishment process corresponding to the flow information to be migrated according to the QoS rule or the local policy returned by the PCRF;
  • Step 1112 The P-GW deletes the service flow from the existing bearer according to the QoS policy returned by the PCRF, and sends an update bearer request to the S-GW to perform the QoS update process of the 3GPP bearer.
  • the process of establishing a connection in the trusted non-3GPP access network is similar to the process of FIG. 10, and the description is not repeated here.
  • the process only needs to replace the attach request of FIG. 9, FIG. 10 and FIG. 11 with the PDN connection establishment request, and the migration flow or/and the flow information to be deleted is established in the PDN connection.
  • the carrying in the request is very similar to the embodiment established by the default bearer described above, and does not affect the description of the present invention. Therefore, the description is not repeated here.
  • the UE informs the P-GW that the service flow information can be carried by the PCO (Protocol Configuration Options) in the message; the UE informs the S-GW or the P-GW that the service flow information can be the service template flow TFT information.
  • the message filter identifier may also be a QoS parameter.
  • the service flow information may include flow information of one or more services.
  • the UE informs the network gateway that the service flow information includes service flow information to be established in the target network (the service flow is migrated from the source network to the target network) or needs to be in the source network.
  • the deleted service flow information, the target network or the source network gateway deletes the source network resources corresponding to the flows. If the flow information to be created is to be migrated from the source network to the target network, the corresponding resources of the source network should be deleted. Therefore, the flow information to be created may not be included in the flow information to be deleted.
  • the UE informs the network gateway that the service flow information may include flow operation information, such as a migration flow, a deletion flow, an increase flow, and the like;
  • the service flow information indicates that the UE informs the network side of the resource information that needs to be established in the target network (eg, Service flow) or / and need to delete the resource information of the source network (for example, traffic flow), therefore, it is necessary to judge and process the network elements in the source network and the target network that are known to these resources, and these processing network elements are
  • the target network eg, Service flow
  • the source network for example, traffic flow
  • the processing network element is the network entity where the PCEF is located (ie, the P-GW), if With the PCC architecture with BBERF (for example, the PMIP protocol is used between the S-GW and the P-GW), the processing network element is the network entity where the BBERF is located (ie, the S-GW or the non-3GPP access gateway).
  • the PCC architecture without BBERF for example, the GTP protocol is used between the S-GW and the P-GW
  • the processing network element is the network entity where the BBERF is located (ie, the S-GW or the non-3GPP access gateway).
  • the PCRF For the establishment of the resource, the PCRF notifies the target network P-GW of the corresponding QoS policy, and the P-GW determines to establish the resource;
  • the PCRF For the deletion of the resource, when the source network uses the PCC architecture with the BBERF, the PCRF notifies the corresponding QoS policy of the network element where the BBERF of the source network is located, and the network element determines whether to delete the corresponding resource; When the PCC architecture of the BBERF is used, the PCRF notifies the corresponding QoS policy of the network element where the PCEF is located. The NE determines whether to delete the corresponding resource.
  • the target network uses the PCC architecture with BBERF
  • the service flow information needs to be brought to the S-GW or the non-3GPP access gateway, and the resource is controlled by the interaction with the PCRF;
  • the PCRF For the establishment of the resource, the PCRF notifies the target network S-GW or the non-3GPP access gateway of the corresponding QoS policy, and the S-GW or the non-3GPP access gateway determines to establish the resource;
  • the PCRF For the deletion of the resource, when the source network uses the PCC architecture with the BBERF, the PCRF notifies the corresponding QoS policy of the network element where the BBERF of the source network is located, and the network element determines whether to delete the corresponding resource; When the PCC architecture of the BBERF is used, the PCRF notifies the corresponding QoS policy of the network element where the PCEF is located. The NE determines whether to delete the corresponding resource.
  • the service flow information needs to be brought to the public gateway (such as the P-GW) and the network entity where the PCEF is located, and the processing network element established by the resource is the network entity where the PCEF is located; If the PCC architecture with BBERF is used, the service flow information needs to be brought to the public gateway (such as P-GW) and the network entity where the BBERF is located, and the processing network element established by the resource The network entity where BBERF is located.
  • the processing network element is a public gateway (such as P-GW).
  • the resource control information is sent by the UE to the gateway of the target network when the default bearer is established or the PDN connection is established or the dedicated bearer is established, and the resource control information includes flow information that needs to be established and/or deleted.
  • the control operation of the network resource is performed in the following manner: the target network gateway initiates a setup operation of the corresponding bearer according to the QoS policy corresponding to the resource control information; and the source network gateway releases the source network resource corresponding to the flow information.
  • the resource control information is transmitted by the UE to a target network gateway and a public gateway when a default bearer setup, a PDN connection setup, or a dedicated bearer setup, where the public gateway refers to a packet data network gateway P-GW, and the resource control
  • the information includes the flow information that needs to be established and/or needs to be deleted; the control operation of the network resource is performed as follows: the target network gateway initiates a setup operation of the corresponding bearer according to the QoS policy; and the P-GW releases the flow information correspondingly Source network resources.
  • the source network or the target network gateway mentioned here refers to the gateway where the bearer binding and event reporting function BBERF or the policy and charging execution function PCEF is located, that is, the S-GW or the non-3GPP access gateway.
  • the above-mentioned quality of service QoS policy is obtained through the policy and charging rule function PCRF, or it can be statically configured.
  • the present invention also provides a system for controlling network resources during service flow migration, the system mainly includes: a gateway of a source network and a gateway of a target network, where
  • the gateway of the source network is configured to perform control operations on the network resources of the source network according to the resource control information or the quality of service QoS policy corresponding to the resource control information;
  • the gateway of the target network is configured to receive the resource control information transmitted by the user terminal, and perform control operations on the network resources of the target network according to the received resource control information or the quality of service QoS policy corresponding to the resource control information.
  • the resource control information is a resource release indication or service flow information
  • the system further includes: a mobility management unit MME and a serving gateway S-GW, when the control information is a resource release indication.
  • a mobility management unit MME and a serving gateway S-GW when the control information is a resource release indication.
  • the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device, or they may be separately fabricated into individual integrated circuit modules, or they may be Multiple modules or steps are made into a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the method for controlling the network resource is: when the service flow is migrated, the resource control information obtained by the network gateway having the knowledge of the network resources of the source network and the target network is obtained, and the network resource is obtained according to the resource control information.
  • the control operation is performed, thereby effectively saving the business flow migration process, improving the network operation efficiency, and effectively enhancing the controllable performance of the network resources.
  • the method for controlling network resources during traffic flow migration according to the present invention, the resource control information acquired by the network gateway having knowledge of the network resources of the source network and the target network, and the network resources are performed according to the resource control information.
  • the control operation effectively saves the service flow migration process, improves the network operation efficiency, and effectively enhances the controllable performance of the network resources.

Landscapes

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

Abstract

L'invention concerne un procédé et un système pour réguler des ressources de réseau pendant une procédure de migration de flux de services. Le procédé comprend les étapes suivantes. Pendant la procédure de migration de flux de services, un équipement d'utilisateur envoie les informations de régulation de ressources à la passerelle du réseau cible, et la passerelle du réseau source ou du réseau cible régule les ressources de réseau de son réseau selon les informations de régulation de ressources ou la politique de qualité de service (QoS) correspondant aux informations de régulation de ressources. Le procédé et le système améliorent l'efficacité de fonctionnement du réseau et optimisent la procédure de traitement.
PCT/CN2009/073638 2009-01-19 2009-08-31 Procédé et système pour réguler des ressources de réseau pendant une procédure de migration de flux de services WO2010081329A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910003099.X 2009-01-19
CN200910003099.XA CN101730150B (zh) 2009-01-19 2009-01-19 业务流迁移时对网络资源进行控制的方法

Publications (1)

Publication Number Publication Date
WO2010081329A1 true WO2010081329A1 (fr) 2010-07-22

Family

ID=42339415

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/073638 WO2010081329A1 (fr) 2009-01-19 2009-08-31 Procédé et système pour réguler des ressources de réseau pendant une procédure de migration de flux de services

Country Status (2)

Country Link
CN (1) CN101730150B (fr)
WO (1) WO2010081329A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114884816A (zh) * 2022-06-17 2022-08-09 中国联合网络通信集团有限公司 数据包限速规则处理方法、装置、设备、存储介质

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102421155B (zh) * 2010-09-27 2017-03-01 中兴通讯股份有限公司 一种实现流迁移的方法及系统
CN103024823A (zh) * 2011-09-20 2013-04-03 中兴通讯股份有限公司 一种流迁移的实现方法、终端和分组数据网络网关
CN103379569A (zh) * 2012-04-17 2013-10-30 中兴通讯股份有限公司 流迁移的触发方法及装置
US8988999B2 (en) * 2012-05-30 2015-03-24 Intel Corporation Method, system and apparatus of wireless local area network (WLAN) communication in conjunction with cellular communication
CN103458468B (zh) * 2012-05-31 2016-12-14 华为终端有限公司 一种承载资源修改的方法及设备
CN104105152B (zh) * 2013-04-03 2017-11-21 中国移动通信集团公司 一种业务迁移方法、网络侧设备及终端
CN104144457B (zh) * 2013-05-08 2017-11-24 中国移动通信集团公司 一种业务从wlan网络迁转到蜂窝网络的方法及装置
CN104782173B (zh) * 2013-11-08 2018-11-06 华为技术有限公司 转发面迁移方法、控制器及网关
WO2015152659A1 (fr) * 2014-04-02 2015-10-08 삼성전자 주식회사 Procédé et appareil pour orienter un trafic entre un réseau cellulaire et un réseau de réseau local (lan) sans fil dans un système de communication mobile
CN110337150B (zh) * 2014-04-21 2023-06-27 华为技术有限公司 承载控制方法及系统
CN105897375A (zh) * 2015-01-26 2016-08-24 中兴通讯股份有限公司 业务迁移方法及装置
CN106162758B (zh) * 2015-03-23 2020-01-10 华为技术有限公司 业务处理方法、pcrf以及业务处理系统
EP3319367B1 (fr) 2015-07-31 2020-07-22 Huawei Technologies Co., Ltd. Procédé, dispositif et système de commutation de noeud
CN107920065A (zh) * 2017-11-13 2018-04-17 中山大学新华学院 基于异构网络的动态迁移访问控制技术设计方法
CN110650467B (zh) * 2018-06-26 2022-03-29 华为技术有限公司 管理用户数据的方法和装置
CN110831088B (zh) * 2018-08-13 2021-05-04 华为技术有限公司 策略控制方法、设备及系统
CN113452555B (zh) * 2021-06-22 2023-12-26 新华三大数据技术有限公司 一种服务质量保障方法及装置

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101075995A (zh) * 2007-06-29 2007-11-21 华为技术有限公司 控制网关处理呼叫的装置、网关及其处理呼叫的方法

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100417254C (zh) * 2005-08-23 2008-09-03 华为技术有限公司 一种无线接入网中内部接口数据通路特性调整方法及网络

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101075995A (zh) * 2007-06-29 2007-11-21 华为技术有限公司 控制网关处理呼叫的装置、网关及其处理呼叫的方法

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"3GPP, 3rd Generation Partnership Project; Technical Specification Group Services 1-15 and System Aspects", MULTI ACCESS PDN CONNECTIVITY AND IP FLOW MOBILITY (RELEASE 9), TR 23.XXX V0.1.0, November 2008 (2008-11-01), pages 10 - 11 *
"3GPP, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects", December 2008, article "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access (Release 8), TS23.401 V8.4.1", pages: 104, 107 *
ZTE: "MAPIM Call flows for Solution B", 3 GPP TSG SA WG2 MEETING #72, TD 1-15 S2-091943, pages 1 - 8 *
ZTE: "Procedure for UE initiated MAPIM attach and IP flow mobility", 3 GPP TSG 1-15 SAWG2 MEETING #70, TD S2-090052, 12 January 2009 (2009-01-12), pages 7 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114884816A (zh) * 2022-06-17 2022-08-09 中国联合网络通信集团有限公司 数据包限速规则处理方法、装置、设备、存储介质
CN114884816B (zh) * 2022-06-17 2024-02-13 中国联合网络通信集团有限公司 数据包限速规则处理方法、装置、设备、存储介质

Also Published As

Publication number Publication date
CN101730150A (zh) 2010-06-09
CN101730150B (zh) 2013-08-07

Similar Documents

Publication Publication Date Title
WO2010081329A1 (fr) Procédé et système pour réguler des ressources de réseau pendant une procédure de migration de flux de services
WO2012058998A1 (fr) Procédé de commande de politique et de facturation soutenant une mobilité de flux ip dans un scénario d'itinérance
US9113436B2 (en) Method and system for information transmission
WO2012006909A1 (fr) Procédé et système de rapport d'informations d'accès à un réseau fixe
WO2014056445A1 (fr) Procédé, système et contrôleur pour transfert de routage
WO2009135362A1 (fr) Procédé de commande de politique et de facturation pour cacher la topologie d'un réseau visité
WO2013104234A1 (fr) Procédé et système de contrôle de règles pour un réseau convergé
WO2011011943A1 (fr) Procédé pour la ré-sélection de fonction de liaison de support et de rapport d’événements
WO2011009257A1 (fr) Système de resélection pour fonction de liaison de porteuse et de rapport d'événement et procédé associé
US9544832B2 (en) Method, apparatus and system for policy control
WO2009059544A1 (fr) Procédé, dispositif et système permettant de mettre en œuvre la commutation entre des réseaux
WO2013016968A1 (fr) Procédé et système d'accès, et point d'accès intelligent mobile
WO2011006317A1 (fr) Procédé et système permettant d'effacer des informations redondantes d'une fonction d’imputation et de règles domestique
WO2013064004A1 (fr) Procédé et système de mise à jour de la qualité de service
WO2012051897A1 (fr) Système et procédé pour intégrer un réseau fixe avec un réseau mobile
WO2012019507A1 (fr) Procédé et système de contrôle de politique permettant d'accéder à un réseau d'accès à large bande fixe
WO2013131487A1 (fr) Réseau central convergent et procédé d'accès associé
WO2009046598A1 (fr) Procédé pour établir une porteuse dédiée pour un terminal utilisateur
WO2012022222A1 (fr) Procédé et système permettant une association de sessions de contrôle de politique
WO2010054560A1 (fr) Procédé et système de mise en œuvre d’un accès multiple
WO2010078761A1 (fr) Procédé, appareil et système de détermination de la politique et de la facturation
EP2741530A1 (fr) Procédé et système d'accès, et point d'accès intelligent mobile
WO2012142889A1 (fr) Procédé de sélection de passerelle, et dispositif et système pour sa mise en œuvre
CN101742471B (zh) 一种数据流与接入网连接绑定的方法
WO2012010036A1 (fr) Procédé et système de contrôle de politique

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

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

Country of ref document: EP

Kind code of ref document: A1