WO2016107405A1 - 业务流传输路径优化方法、装置及mme - Google Patents

业务流传输路径优化方法、装置及mme Download PDF

Info

Publication number
WO2016107405A1
WO2016107405A1 PCT/CN2015/097502 CN2015097502W WO2016107405A1 WO 2016107405 A1 WO2016107405 A1 WO 2016107405A1 CN 2015097502 W CN2015097502 W CN 2015097502W WO 2016107405 A1 WO2016107405 A1 WO 2016107405A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdn connection
service
handover
pdn
apn
Prior art date
Application number
PCT/CN2015/097502
Other languages
English (en)
French (fr)
Inventor
毛玉欣
王静
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2016107405A1 publication Critical patent/WO2016107405A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition

Definitions

  • the present invention relates to the field of communications, and in particular to a method, an apparatus, and an MME for optimizing a traffic stream transmission path.
  • FIG. 1 is a schematic diagram of the EPS system architecture in the related art, as shown in Figure 1. .
  • the architecture consists of an Evolved Universal Terrestrial Radio Access Network (E-UTRAN), a Mobility Management Entity (MME), and a Serving Gateway (S-GW). ), a Packet Data Network Gateway (P-GW), a Home Subscriber Server (HSS), a Policy and Charging Rules Function (PCRF), and The other support nodes are composed.
  • 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
  • the MME is responsible for mobility management, non-access stratum signaling processing, user mobility management context management and other control plane related work, P-GW and S-GW selection, mobile phone reachability management and tracking area list in idle state. Choose other features.
  • the S-GW is an access gateway device connected to the E-UTRAN.
  • the function includes: forwarding the data between the E-UTRAN and the P-GW as a local anchor for the inter-eNodeB handover, and is responsible for buffering the paging waiting data. Monitoring, data packet routing, and user-based QoS Class Identifier (QCI)-based charging.
  • QCI QoS Class Identifier
  • the P-GW is a border gateway between the EPS system and the PDN network. Its functions include: user terminal IP address allocation, user data packet filtering, and quality of service (QoS) label management of transport layer packets.
  • QoS quality of service
  • the Dynamic Host Configuration Protocol version 4/version 6 (DHCPv4/v6) function is based on the Aggregate Maximum Bit Rate (AMBR).
  • ABR Aggregate Maximum Bit Rate
  • the rate guarantee is based on the downlink rate guarantee of the cumulative MBR of the QCI of the same Guaranteed Rate (GBR). It is responsible for the uplink and downlink bearer binding and lawful interception.
  • the PCRF is a policy and charging rule function entity. It connects to the service network protocol (Internet Protocol, Internet Protocol for short) service network through the Rx interface to obtain service information.
  • the PCRF generates QoS and charging policies through the Gx/Gxc interface.
  • the QoS and charging policies are delivered by the policy execution function.
  • Policy execution function It can be a Policy and Charging Enforcement Function (PCEF) located on the P-GW or a Bearer Binding and Event Report Function (Bearer Binding and Event Report Function). BBERF) implementation.
  • PCEF Policy and Charging Enforcement Function
  • BBERF Bearer Binding and Event Report Function
  • the existing system of the 3GPP defines that a user equipment (User Equipment, UE for short) must establish a PDN connection between the access network, for example, E-UTRAN, and the PDN network before performing data services.
  • UE User Equipment
  • 2 is a flowchart of establishing a PDN connection in the related art. As shown in FIG. 2, the process includes the following steps:
  • the UE initiates a non-access stratum (Non-Access Stratum, NAS for short) message, that is, a PDN connection setup request message.
  • the message carries the Access Point Name (APN), PDN Type (PDN Type), Protocol Configuration Options (PCO), and Request Type.
  • API Access Point Name
  • PDN Type PDN Type
  • PCO Protocol Configuration Options
  • the PDN Type is used to indicate whether the type of the IP address requested by the UE is IPv4, IPv4v6 or IPv6; the PCO is used to transmit information between the UE and the P-GW, and the information is transparently transmitted on the MME and the S-GW; Whether the indication is "initial request” or "handover”; APN is used by the MME to select the basis of the P-GW.
  • the MME When the MME receives the APN, it needs to verify whether the APN is allowed to be used by the user according to the user subscription information. If the APN is not carried in the request message, the MME selects the default APN carried in the Default PDN Subscription Context (the default PDN subscription context) to be used by the subsequent process.
  • the MME processes the request message.
  • the MME needs to use the P-GW address stored in the user data.
  • the P-GW address is retrieved and saved by the MME during the location update during the attach procedure.
  • the Request Type indication in 201 is "initial request”
  • the MME needs to perform a P-GW selection procedure, and select a P-type that can be established by the UE and the PDN network corresponding to the APN according to the APN, the P-GW capacity, the UE location information, and the like. GW.
  • the MME allocates a Bearer ID (bearer ID) to the user request, and initiates a create session request message to the S-GW.
  • the message carries the International Mobile Subscriber Identification Number (IMSI), the Mobile Subscriber ISDN Number (MSISDN), the RAT Type, and the P-GW Address. P-GW address), PDN Address, Default Bearer QoS, PDN Type, Proprietary Type APN-AMBR, APN, EPS Bearer ID ), PCO, ECGI (User Location Information, etc.).
  • the S-GW creates a new record on its own EPS Bearer table and sends a session creation to the P-GW. Request message.
  • the P-GW address is obtained by the MME by the P-GW selection procedure in step 202.
  • the message carries: IMSI, MSISDN, RAT Type, PDN Type, Default EPS Bearer QoS, Subscribed APN-AMBR, PDN Address, APN, EPS Bearer ID, PCO, ECGI, and the like.
  • the S-GW buffers the downlink data from the P-GW until it receives the message from the MME 213.
  • the P-GW After receiving the session creation request, the P-GW initiates an IP-CAN session establishment to the PCRF if it is not a "handover" condition.
  • the PCRF returns a default PCC rule for the UE to the P-GW.
  • the establishment process of the dedicated bearer can also be triggered.
  • the P-GW receives the indication of the Handover Indication ("Handover"), the P-GW initiates the IP-CAN session modification process and reports the new IP-CAN Type to the PCRF.
  • Handover Handover Indication
  • the P-GW creates a new record in the EPS bearer context list and creates a Charging ID for the default bearer. This record allows the P-GW to exchange data between the S-GW and the PDN network and initiate charging.
  • the P-GW returns a Create Session Response message to the S-GW.
  • the message carries information such as P-GW Address, PDN Address, PDN Type, EPS Bearer ID, EPS Bearer QoS, PCO, Charging ID, MS Info Change Reporting Action (Start), APN-AMBR.
  • the PDN Type is used to return the address of the PDN network to the UE. If it is a handover situation, the PDN network address returned to the UE should remain unchanged before and after the handover.
  • the P-GW cannot send downlink data packets to the S-GW.
  • the S-GW returns a create session response message to the MME.
  • the message carries information such as PDN Type, PDN Address, P-GW Address, EPS Bearer ID, EPS Bearer QoS, PCO, MS Info Change Reporting Action (Start), APN-AMBR.
  • sending the message to the MME also indicates that the bearer between the S-GW and the P-GW has been established.
  • the MME needs to save the information for the bearer context.
  • the MME needs to report the location information of the UE to the P-GW through the S-GW.
  • the MME needs to modify the UE-AMBR allocated to the eNodeB based on the UE-AMBR subscribed by the user and all APN-AMBRs currently being used.
  • the MME returns a PDN Connection Setup Response message to the UE.
  • the message carries: APN, PDN Type, PDN Address, EPS Bearer ID, Session Management Request, PCO, etc.
  • the message is sent to the eNodeB in an S1_MME control message, that is, a bearer setup request message.
  • the message also includes: PDN connection setup response message, EPS Bearer QoS, UE-AMBR, S-GW Address and other information.
  • the S1_MME control message that is, the bearer setup request message, also includes a SIPTO Correlation ID.
  • the SIPTO Correlation ID is used to identify the direct transmission channel of the HeNB and the L-GW.
  • the Session Management Request carries the APN-AMBR and QCI information. If the UE supports UTRAN or GERAN (GSM EDGE Radio Access Network) access, the MME also generates corresponding QoS negotiation parameters of the PDP according to the EPS Bearer QoS parameters, Radio Priority, Packet Flow ID, TI. Information, etc., and is also included in the session management request.
  • UTRAN GSM EDGE Radio Access Network
  • the eNodeB sends an RRC Link Reconfiguration message to the UE.
  • the message carries a PDN connection setup response message.
  • the UE saves the message in the session management request, that is, the QoS negotiation parameter, the Radio Priority, the Packet Flow ID, the TI, and the like, so that the UE accesses through the GERAN or the UTRAN.
  • the UE provides EPS Bearer QoS parameters to the application for processing traffic flow.
  • the UE uses DHCPv4 for IPv4 address negotiation. If the UE receives the IPv6 interface identifier, it waits for the IPv6 prefix information carried in the Router Advertisement message from the network.
  • the UE sends an RRC Link Reconfiguration Complete message to the eNodeB.
  • the eNodeB returns an S1-AP bearer setup response message to the MME.
  • the eNodeB uses this information to establish a direct data path between the eNodeB and the L-GW.
  • the NAS layer of the UE establishes a PDN connection setup response message, and the message includes the EPS Bearer ID information.
  • the UE sends a direct transfer message (PDN Connection Setup Response) to the eNodeB.
  • PDN Connection Setup Response PDN Connection Setup Response
  • the eNodeB sends an uplink NAS transport message (PDN connection setup response) to the MME.
  • PDN connection setup response PDN connection setup response
  • the UE may send an uplink data packet through the eNodeB, and the data packet may be tunneled to the S-GW and the P-GW.
  • the MME After receiving the bearer setup response message of step 210 and the PDN connection setup response message of step 212, the MME sends a bearer modification request message to the S-GW.
  • the message carries: EPS Bearer ID, eNodeB address, Handover Indication, and the like. Handover Indication is provided if the Request Type is indicated as "Handover".
  • the S-GW sends a bearer modification request message to the P-GW, triggering a tunnel change between the P-GW and the non-3GPP IP access, and why the tunnel between the 3GPP access systems And immediately route the default EPS bearer and all the packets on the dedicated EPS bearer to the S-GW.
  • the P-GW returns a bearer modification response to the S-GW.
  • the S-GW returns a bearer modification response to the MME.
  • the S-GW can then send the locally blocked downlink packet to the UE.
  • the Request Type is not indicated as "handover" and an EPS bearer is established
  • the user subscription data indicates that the UE is allowed to perform handover to the non-3GPP access system
  • the PDN connection is the first PDN connection corresponding to the APN
  • the P-GW selected by the MME is different from the P-GW address in the PDN user context indicated by the previous HSS
  • the MME needs to send an information report request message to the HSS.
  • the message carries the P-GW address and the APN used to establish the PDN connection, and further needs to carry information indicating which PLMN the P-GW is located in.
  • the HSS saves the P-GW identifier and its corresponding APN, and returns an information report response message to the MME.
  • the UE establishes a default PDN connection during the process of attaching to the network.
  • the UE may also establish a PDN connection to other PDN networks as needed during the subsequent service.
  • Each PDN network has an APN corresponding. To which PDN network the UE wants to establish a connection, the corresponding APN needs to be sent to the MME, so that the MME selects a P-GW for the user.
  • the P-GW is a connection point between the UE and the PDN network, and the UE establishes a PDN connection with the P-GW according to the P-GW selected by the MME.
  • multiple PDN connections can be established between the UE and the same PDN network, that is, multiple PDN connections can be established for the same APN, but the existing system stipulates that the multiple PDN connections must use the same P-GW. .
  • the 3GPP system also defines information such as the APN information, the geographic location of the user, and the P-GW capability (eg, capacity) when selecting the P-GW required to establish a PDN connection for the UE.
  • the final P-GW selects a functional entity, such as the MME, to determine a P-GW list for the UE to establish the PDN connection based on the reference information.
  • Each P-GW in the list has a corresponding weight information, and an appropriate P-GW (the highest or lowest weight) is selected for the UE to establish the PDN connection.
  • FIG. 3 is a schematic diagram of data routing in a user switching scenario in the related art.
  • the P-GW selection mechanism selects P-GW1, P-GW2, and P-GW3 for the UE to establish a PDN connection corresponding to the APN according to information such as the APN, the P-GW capacity, and the geographic location of the UE.
  • the current access location of the UE is closer to P-GW1, and P-GW1 is selected to establish PDN connection 1.
  • the dotted line A is a data service through the PDN connection 1 after the UE accesses.
  • the UE moves, moving from area A to area B, that is, switching across the access area occurs.
  • the network mechanism of the related art stipulates that the continuity of the service must be ensured, that is, when the UE accesses through the area B, the S-GW2 that is closer to the area B is selected as the UE access.
  • the service and the P-GW2 closer to the area B may also provide the PDN connection between the UE and the PDN network, but the UE must still use the PDN connection 1 established by the P-GW1, as shown by the broken line B in the figure. business. In this way, the data service carried out when the UE moves to the area B does not interrupt.
  • P-GW1 as an anchor point ensures that the service experience during the user's mobile process is not affected, but also causes data routing to be detoured, that is, the P can be selected closer after the original mobile.
  • - GW2 performs data routing, and now must still use P-GW1 far away from access area B for data routing, which will inevitably lead to unreasonable use of network resources.
  • the present invention provides a service stream transmission path optimization method and apparatus to solve at least the problem of resource waste in the transmission path of the data stream in the related art.
  • a service stream transmission path optimization method includes: detecting, by a user equipment UE, a packet data gateway P-GW adjusting CSIPTO indication information for a specified Internet Protocol IP stream offloading; CSIPTO indication information, selecting a first P-GW for the access point name APN of the UE, establishing a first packet data network PDN connection based on the first P-GW, and selecting a second for the APN of the UE a P-GW, and establishing a second PDN connection based on the second P-GW; performing optimization processing on the service flow transmission path of the UE according to the established first PDN connection and/or the second PDN connection.
  • the first P-GW is selected for the access point name APN of the UE according to the CSIPTO indication information, and Establishing a first packet data network PDN connection based on the first P-GW, selecting a second P-GW for the APN of the UE, and establishing a second PDN connection based on the second P-GW, and establishing according to the
  • the first PDN connection and/or the second PDN connection to optimize the service flow transmission path of the UE includes: during the UE handover process, retaining the PDN connection before the UE handover as the first The PDN is connected, and the service without the service continuity requirement in the first PDN connection is released, and the service with the service continuity requirement is continued to be carried; Selecting, by the second P-GW, the second P-GW to establish the second PDN connection according to the current access location of the UE, and using the second PDN connection to carry the service with no service continuity requirement
  • optimizing the service flow transmission path of the UE according to the established first PDN connection and/or the second PDN connection comprises: allocating the first PDN connection and the second PDN connection PDN connection priority, wherein the priority of the second PDN connection is higher than the priority of the first PDN connection, after the handover, the newly launched service of the UE preferentially uses the second according to the PDN connection priority The PDN connection is carried.
  • Point name APN selects a first P-GW, and establishes a first packet data network PDN connection based on the first P-GW, selects a second P-GW for the APN of the UE, and is based on the second P - GW establishing a second PDN connection, and optimizing the traffic flow path of the UE according to the established first PDN connection and/or the second PDN connection comprises: during the UE handover process, reserved for The PDN connection of the service carrying the service continuity requirement is the first PDN connection, and continues to carry the service with the service continuity requirement before the UE handover and the new service continuity requirement after the UE handover.
  • the second PDN connection carries the The service required by the UE before the handover without service continuity and the service newly required after the UE handover without the service continuity requirement.
  • optimizing the service flow transmission path of the UE according to the established first PDN connection and/or the second PDN connection comprises: setting a PDN connection type for the first PDN connection, for illustrating
  • the service carrying the service continuity requirement is configured to set a PDN connection type for the second PDN connection, and is used to describe the service that carries the service continuity requirement; and the UE is determined to be newly developed according to the matching relationship between the PDN connection type and the service type.
  • the service is carried using the corresponding PDN connection.
  • optimizing the service flow transmission path of the UE according to the established first PDN connection and/or the second PDN connection comprises: selecting the second second closest to the current access location of the UE a P-GW, and establishing the second PDN connection based on the second P-GW.
  • a service stream transmission path optimization apparatus including: a detection module, configured to detect that a user equipment UE performs a packet data gateway P-GW adjustment for a specified Internet Protocol IP stream offloading CSIPTO Instructing information, the establishing module is configured to select a first P-GW for the access point name APN of the UE according to the CSIPTO indication information, and establish a first packet data network PDN connection based on the first P-GW, Selecting a second P-GW for the APN of the UE, and building the second P-GW based on the second P-GW Establishing a second PDN connection; the processing module is configured to perform optimization processing on the service flow transmission path of the UE according to the established first PDN connection and/or the second PDN connection.
  • a detection module configured to detect that a user equipment UE performs a packet data gateway P-GW adjustment for a specified Internet Protocol IP stream offloading CSIPTO Instructing information
  • the establishing module is configured to select a first P-GW for the access point
  • the establishing module is further configured to reserve, before the UE handover, that all services of the UE are carried by one PDN connection, and retain the PDN connection before the UE handover in the UE handover process.
  • the processing module is further configured to release a service that does not have a service continuity requirement in the first PDN connection, and continue to carry a service with a service continuity requirement;
  • the establishing module is further configured to Selecting, by the second P-GW, the second P-GW to establish the second PDN connection according to the current access location of the UE; the processing module is further configured to use the second PDN connection to carry the service with no service continuity requirement and All newly launched services after the UE is switched.
  • the processing module includes: an allocating unit, configured to allocate a PDN connection priority for the first PDN connection and the second PDN connection, wherein the second PDN connection has a higher priority than the first The priority of a PDN connection, after the handover, the new service of the UE is preferentially used to carry the second PDN connection according to the PDN connection priority.
  • an allocating unit configured to allocate a PDN connection priority for the first PDN connection and the second PDN connection, wherein the second PDN connection has a higher priority than the first
  • the priority of a PDN connection after the handover, the new service of the UE is preferentially used to carry the second PDN connection according to the PDN connection priority.
  • the establishing module is further configured to: before the UE handover, the service required by the service continuity and the service without the service continuity are respectively carried in different PDN connections, in the UE handover process
  • the PDN connection for the service that carries the service continuity requirement is reserved for the first PDN connection
  • the processing module is further configured to continue to carry the service and the service continuity requirement that is performed before the UE handover a service that has a new service continuity requirement after the UE is switched; releasing a PDN connection for carrying a service without a service continuity requirement
  • the establishing module is further configured to reselect the according to the current access location of the UE.
  • the second P-GW re-establishes the PDN connection as the second PDN connection; the processing module is further configured to use the second PDN connection to carry the service without the service continuity requirement performed before the UE handover, and the New services that are not required for business continuity after UE handover.
  • the processing module includes: a setting unit, configured to set a PDN connection type for the first PDN connection, to describe a service carrying a service continuity requirement, and to set a PDN connection type for the second PDN connection, And the determining unit is configured to determine, according to the matching relationship between the PDN connection type and the service type, the PDN connection corresponding to the newly used service of the UE to perform bearer.
  • a setting unit configured to set a PDN connection type for the first PDN connection, to describe a service carrying a service continuity requirement, and to set a PDN connection type for the second PDN connection
  • the determining unit is configured to determine, according to the matching relationship between the PDN connection type and the service type, the PDN connection corresponding to the newly used service of the UE to perform bearer.
  • the processing module comprises: a processing unit, configured to select the second P-GW that is closest to the current access location of the UE, and establish the second PDN connection based on the second P-GW.
  • a mobility management entity MME including the apparatus of any of the above.
  • the uninstallation of the specified Internet Protocol IP stream by the user equipment UE is detected.
  • the packet data gateway P-GW adjusts the CSIPTO indication information, selects a first P-GW for the access point name APN of the UE according to the CSIPTO indication information, and establishes a first packet data network based on the first P-GW.
  • connection optimizes the service flow transmission path of the UE, and solves the problem of waste of resources in the transmission path of the data flow in the related art, thereby achieving the goal of optimizing the data routing path without affecting the user service experience. Save the effect of network resource overhead.
  • FIG. 1 is a schematic diagram of an EPS system architecture in the related art
  • FIG. 3 is a schematic diagram of data routing in a user switching scenario in the related art
  • FIG. 4 is a flowchart of a method for optimizing a traffic stream transmission path according to an embodiment of the present invention
  • FIG. 5 is a structural block diagram of a service flow path optimization apparatus according to an embodiment of the present invention.
  • FIG. 6 is a block diagram 1 of a preferred structure of a processing module 56 in a service flow path optimization apparatus according to an embodiment of the present invention
  • FIG. 7 is a block diagram 2 of a preferred structure of a processing module 56 in a service flow path optimization apparatus according to an embodiment of the present invention
  • FIG. 8 is a block diagram 3 of a preferred structure of a processing module 56 in a service flow path optimization apparatus according to an embodiment of the present invention.
  • FIG. 9 is a structural block diagram of a mobility management entity MME according to an embodiment of the present invention.
  • FIG. 10 is a schematic diagram of data routing optimization in a user handover scenario according to an embodiment of the present invention.
  • FIG. 11 is a schematic diagram of user initial access and PDN connection establishment in a handover process according to an embodiment of the present invention.
  • FIG. 12 is a flowchart of user completion attachment and PDN connection establishment according to an embodiment of the present invention.
  • FIG. 13 is a diagram after the user completes the attach and PDN connection establishment shown in FIG. 12 according to an embodiment of the present invention. Switch flow chart;
  • FIG. 14 is a flowchart of UE handover across MME according to an embodiment of the present invention.
  • Figure 15 is a flow chart showing the development of traffic after handover, in accordance with an embodiment of the present invention.
  • FIG. 4 is a flowchart of a service flow path optimization method according to an embodiment of the present invention. As shown in FIG. 4, the process includes the following steps:
  • Step S402 detecting that the user equipment UE performs the packet data gateway P-GW to adjust the CSIPTO indication information for the specified Internet Protocol IP flow offloading;
  • Step S404 selecting a first P-GW for the access point name APN of the UE according to the CSIPTO indication information, and establishing a PDN connection of the first packet data network based on the first P-GW, and selecting a second P-GW for the APN of the UE, And establishing a second PDN connection based on the second P-GW;
  • Step S406 performing optimization processing on the service flow transmission path of the UE according to the established first PDN connection and/or the second PDN connection.
  • the first PDN connection is established for the UE based on the first P-GW
  • the second PDN connection is established for the UE based on the second P-GW, according to the CSIPTO indication information, according to the established first PDN connection, and the second PDN connection pair.
  • the service flow transmission path of the UE is optimized, and the problem of resource waste in the transmission path of the data flow in the related art is solved, thereby achieving the saving of network resource overhead by optimizing the data routing path without affecting the user service experience. Effect.
  • the manner in which the first PDN connection is established for the UE, the second PDN connection, and the service flow path of the UE is optimized according to the first PDN connection and the second PDN connection may be different according to different service bearers before the UE is switched. , respectively, explained below.
  • the first P-GW is selected for the access point name APN of the UE according to the CSIPTO indication information, and the first P-GW is established based on the first P-GW.
  • the optimization process of the transmission path may include: maintaining the PDN connection before the UE handover as the first PDN connection in the UE handover process, and releasing the service without the service continuity requirement in the first PDN connection, and continuing to carry the service continuity requirement.
  • Service selecting a second P-GW to establish a second PDN connection according to the current access location of the UE, The second PDN connection is used to carry services that have no service continuity requirements and all services that are newly launched after the UE is switched.
  • Optimizing the service flow transmission path of the UE according to the established first PDN connection and/or the second PDN connection includes: allocating a PDN connection priority for the first PDN connection and the second PDN connection, wherein the second PDN connection is prioritized The level is higher than the priority of the first PDN connection.
  • the newly developed service of the UE preferentially uses the second PDN connection to carry the bearer according to the PDN connection priority.
  • the UE selects the first access point name APN according to the CSIPTO indication information.
  • a P-GW and establishing a first packet data network PDN connection based on the first P-GW, selecting a second P-GW for the APN of the UE, and establishing a second PDN connection based on the second P-GW, and establishing the second PDN connection
  • the PDN connection and/or the second PDN connection to optimize the service flow transmission path of the UE includes: during the UE handover process, the PDN connection for the service carrying the service continuity requirement is reserved as the first PDN connection, and continues to carry the UE A service with service continuity requirements before the handover and a service with new service continuity requirements after the UE is switched; releasing the PDN connection for carrying the service without the service continuity requirement, and reselecting according to the current access location of the UE.
  • the second P-GW re-establishe
  • optimizing the service flow transmission path of the UE according to the established first PDN connection and/or the second PDN connection comprises: setting a PDN connection type for the first PDN connection, and indicating the service carrying the service continuity requirement
  • the PDN connection type is set for the second PDN connection, and is used to describe the service that carries the service continuity-free requirement. According to the matching relationship between the PDN connection type and the service type, the PDN connection corresponding to the newly used service of the UE is determined to be carried.
  • optimizing the service flow transmission path of the UE according to the established first PDN connection and/or the second PDN connection includes: selecting a second P-GW closest to the current access location of the UE, and based on the second The P-GW establishes a second PDN connection.
  • a service flow path optimization device is further provided, which is used to implement the foregoing embodiments and preferred embodiments, and details are not described herein.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 5 is a structural block diagram of a service flow path optimization apparatus according to an embodiment of the present invention. As shown in FIG. 5, the apparatus includes a detection module 52, an establishment module 54, and a processing module 56, which will be described below.
  • the detecting module 52 is configured to detect that the user equipment UE performs the packet data gateway P-GW adjustment CSIPTO indication information for the specified Internet Protocol IP stream offloading;
  • the establishing module 54 is connected to the detecting module 52, and is configured to For selecting the first P-GW for the access point name APN of the UE according to the CSIPTO indication information, and establishing a PDN connection of the first packet data network based on the first P-GW, selecting a second P-GW for the APN of the UE, and based on The second P-GW establishes a second PDN connection;
  • the processing module 56 is connected to the foregoing establishing module 54 and configured to perform optimization processing on the service flow transmission path of the UE according to the established first PDN connection and/or the second PDN connection.
  • the establishing module 54 is further configured to reserve the PDN connection before the UE handover as the first PDN connection in the UE handover process, in the case that the UE is in the PDN connection before the UE handover, and the processing module 56
  • the service is further configured to release the service that does not have the service continuity requirement in the first PDN connection, and continues to carry the service with the service continuity requirement;
  • the establishing module 54 is further configured to select the second P-GW to establish the second according to the current access location of the UE.
  • the PDN is connected to the processing module 56.
  • the processing module 56 is further configured to use the second PDN connection to carry services without service continuity requirements and all services newly performed after the UE is switched.
  • FIG. 6 is a block diagram of a preferred structure of the processing module 56 in the traffic stream path optimization apparatus according to an embodiment of the present invention. As shown in FIG. 6, the processing module 56 includes an allocating unit 62, which will be described below.
  • the allocating unit 62 is configured to allocate a PDN connection priority for the first PDN connection and the second PDN connection, wherein the priority of the second PDN connection is higher than the priority of the first PDN connection, and the newly developed service of the UE according to the PDN after the handover
  • the connection priority is preferentially carried using the second PDN connection.
  • the establishing module 54 is further configured to: before the UE handover, the service with the service continuity requirement and the service without the service continuity requirement are respectively carried in different PDN connections, and are reserved for the UE handover process.
  • the PDN connection of the service carrying the service continuity requirement is the first PDN connection;
  • the processing module 56 is further configured to continue to carry the service with the service continuity requirement before the UE handover and the new service continuity requirement after the UE handover Service; releasing a PDN connection for carrying a service without service continuity requirement;
  • the establishing module 54 is further configured to re-select the second P-GW to re-establish the PDN connection as the second PDN connection according to the current access location of the UE; 56. It is further configured to use the second PDN connection to carry the service without the service continuity requirement performed before the UE handover, and the newly developed service without the service continuity requirement after the UE handover.
  • FIG. 7 is a block diagram of a preferred structure of the processing module 56 in the service stream transmission path optimization apparatus according to an embodiment of the present invention. As shown in FIG. 7, the processing module 56 includes: a setting unit 72 and a determining unit 74. Module 56 is described.
  • the setting unit 72 is configured to set a PDN connection type for the first PDN connection, to describe the service carrying the service continuity requirement, and set a PDN connection type for the second PDN connection, which is used to describe the service carrying the service continuity requirement;
  • the determining unit 74 is connected to the setting unit 72, and is configured to determine, according to the matching relationship between the PDN connection type and the service type, that the newly-developed service of the UE uses the PDN connection corresponding to the bearer.
  • FIG. 8 is a block diagram 3 of a preferred structure of the processing module 56 in the service stream transmission path optimization apparatus according to the embodiment of the present invention.
  • the processing module 56 includes a processing unit 82, and the processing unit 82 is described below. Bright.
  • the processing unit 82 is configured to select a second P-GW that is closest to the current access location of the UE, and establish a second PDN connection based on the second P-GW.
  • FIG. 9 is a structural block diagram of a mobility management entity MME according to an embodiment of the present invention. As shown in FIG. 9, the MME 90 includes the service flow path optimization device 92 of any of the above.
  • the user service experience at the time of handover is not affected by sacrificing the use efficiency of the network resources.
  • the services carried out by users are diverse, the requirements for delay can be divided into two categories, one is services such as IP telephony and VPN, which have high requirements for business continuity, and such services are transmitted.
  • the process can not be interrupted, once the interruption occurs, it will have a greater impact on the business experience.
  • Such services are called real-time services; the other is services such as short messages and web browsing that require less business continuity. Even if an interruption occurs during the transmission, it will not have a great impact on the user's business experience, and even a short interruption of the user can not feel, such services are called non-real-time services.
  • the handover process adopts a route bypass mode for both real-time service and non-real-time service, so that data is routed through the P-GW1 anchor point to ensure continuous service.
  • this method ensures the service experience, it also causes the network. Waste of resources.
  • a method for optimizing a traffic stream transmission path comprising: checking that a user equipment UE performs PGW adjustment for a specified IP stream offload (Coordinated PGW change for Selected IP Traffic Offload)
  • the indication information is abbreviated as CSIPTO.
  • the indication information is used to describe the optimization of the transmission path of the data stream when the UE performs the service, and selects two different P-GWs for the user's APN to establish two PDN connections according to the indication information.
  • the user terminal optimizes the access connection during the mobile process to achieve the optimal transmission path of the service flow without mitigating the user service experience, thereby reducing the route bypass and saving network resources. The method will be briefly described below.
  • the user service experience is ensured and the routing path is optimized.
  • One PDN connection is used to carry the service continuity.
  • the required service the PDN connection is always uninterrupted during the handover process, that is, the P-GW used by the PDN connection remains unchanged during the handover process; the other PDN connection is used to carry the service without the service continuity requirement,
  • the P-GW used by the PDN connection is close to the user access location.
  • the PDN connection is released, and the P-GW that is connected to the user location after the MME chooses to re-establish the PDN connection to carry the above-mentioned non-service continuity.
  • Sexual requirements for business This implementation mode does not affect the user's service experience, and at the same time optimizes the data routing path and saves network resources.
  • FIG. 10 is a schematic diagram of data routing optimization in a user switching scenario according to an embodiment of the present invention, as shown in FIG.
  • PDN connection 1 (established using P-GW1) is used for both real-time and non-real-time services before user handover.
  • the P-GW 2 that is closer to the area B as shown by the dotted line C in FIG. 10 is selected to establish the PDN connection 2 for routing; and for the real-time service, the dotted line B is still used.
  • PDN connection 1 is routed.
  • FIG. 11 is a schematic diagram of PDN connection establishment during initial access and handover in a user according to an embodiment of the present invention.
  • - GW establishes two PDN connections, as shown by the dotted line 1 shown in the left figure, PDN connection 1 (established using P-GW1) for carrying non-real-time services, and PDN connection 2 shown by dashed line 2 (using P-GW2) Used to carry real-time services.
  • PDN connection 1 is unchanged (still using P-GW2), and the PDN connection 1 is released.
  • the MME selects the P-GW3 that is close to the access location after the user switches to establish the PDN connection. Real-time business.
  • the effect of saving part of network resource overhead can be achieved by optimizing the data routing path without affecting the user service experience.
  • the MME determines whether to establish two PDN connections by selecting two different P-GWs for the APN of the user according to the CSIPTO (Coordinated PGW change for Selected IP Traffic Offload) indication information in the user subscription information. .
  • the CSIPTO indication information is used to indicate whether to allow route optimization for user data.
  • the MME completes the PDN connection operation in the attach or handover process according to the prior art
  • the MME selects two P-GWs for the same APN to establish a PDN connection, where one PDN connection is used to carry services with service continuity requirements (such as real-time services), and A PDN connection is used to carry services without business continuity requirements (eg, non-real time services).
  • service continuity requirements such as real-time services
  • business continuity requirements e.g, non-real time services
  • the MME selects two different P-GWs for the same APN (as shown in the left figure of FIG. 11).
  • P-GW1 and P-GW2 respectively establish a PDN connection (the PDN connection 1 indicated by the dotted line 1 is used to carry the service without the service continuity requirement, and the PDN connection 2 indicated by the dotted line 2 is used to carry the service with the service continuity requirement).
  • the request message received by the MME is indicated as a handover request message, and the CSIPTO indication information is allowed to be used
  • the request message received by the MME is indicated as a handover request message, and the CSIPTO indication information is allowed to be used
  • the CSIPTO indication information is allowed to be used in the case of user data for route optimization:
  • the MME decides to release during the handover.
  • PDN connection 1 established by P-GW1 in Figure 10 For the dedicated bearer carrying the service without continuity requirement, select the P-GW that is close to the access location after the user is switched to establish a new PDN connection (as shown in Figure 10, select PDN connection 2 established by P-GW2, indicated by the broken line C) Businesses that are not required for business continuity and new services after switching (including those with continuity requirements and non-continuity requirements).
  • the PDN connection for the service carrying the service continuity requirement is not released during the handover process (as shown in Figure 10, PDN connection 1 established by P-GW1 is selected, and the dotted line B is indicated). After the service ends, the PDN connection is released.
  • PDN connection bearers are used (as shown in the left diagram of FIG. 11 , the PDN connection 1 established by the dotted line 1 using P-GW1, The MME decides to release the PDN connection 1 and re-establish the PDN connection 2 established by the P-GW 2 to be used to carry the service with the service continuity requirement.
  • the P-GW 3 that is close to the access location after the user is switched to establish a PDN connection 3 is used to carry the service that is carried out before the handover and that is newly performed after the handover without the service continuity requirement.
  • the PDN connection 2 remains uninterrupted and is used to carry services that have business continuity requirements during handover and after handover.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • the first embodiment illustrates that two PDN connections are established for the same APN of the user according to the CSIPTO indication during the initial attachment process of the user.
  • One of the PDN connections 1 (established using P-GW1) is used to carry services without service continuity requirements (non-real-time services);
  • PDN connection 2 (established using P-GW2) is used to carry services with business continuity requirements (real-time) business).
  • the PDN connection 2 is not interrupted, the PDN connection 1 is released, and the PDN connection 3 (established using P-GW3) is established for carrying services without service continuity requirements.
  • the UE can subscribe to multiple APNs, and the user terminal can establish a PDN connection by using each APN.
  • this embodiment assumes that the user establishes a PDN connection only between one APN and the PDN network. Refer to this procedure for the PDN connection establishment process of other APNs.
  • FIG. 12 is a flowchart of user completion attachment and PDN connection establishment according to an embodiment of the present invention. As shown in FIG. 12, the process includes the following steps:
  • the UE attaches to the network and requests to establish a PDN connection.
  • the UE initiates a PDN Connection Setup Request message.
  • the message carries information such as APN.
  • the MME When the MME receives the APN, it needs to verify whether the APN is allowed to be used by the user according to the user subscription information. If the APN is not carried in the request message, the MME selects the default APN to be used by the subsequent process.
  • the MME processes the request message.
  • the MME first queries the user subscription information whether the user supports CSIPTO. If it supports, it decides to establish two P-GWs for the user to establish a PDN connection; if not, the PDN connection is established according to the original process.
  • User subscription information is obtained by the MME from the HSS during the user attachment phase and thereafter stored in the user context.
  • the MME performs a P-GW selection procedure, and selects a P-GW for the user to establish a PDN connection according to the APN, the P-GW capacity, the UE location information, and the like.
  • the MME selects P-GW1 and P-GW2 to establish a PDN connection for the APN.
  • the MME initiates a Create Session 1 Request message to the S-GW.
  • the message carries information such as IMSI, P-GW1 address, PDN address, APN, and PDN connection type.
  • the PDN connection type is used to indicate that the PDN connection is used to carry services without service continuity requirements.
  • the S-GW creates a new record on its own EPS Bearer table and sends a Session 1 Create Request message to P-GW1.
  • the P-GW1 address is acquired by the MME by the P-GW selection procedure in step 2.
  • the message carries information such as IMSI, PDN address, APN, and PDN connection type.
  • P-GW1 After receiving the session 1 creation request, P-GW1 initiates IP-CAN session 1 establishment to the PCRF.
  • the PCRF returns a default PCC rule for the UE to P-GW1.
  • a dedicated bearer setup process can also be triggered.
  • P-GW1 sends information such as APN and PDN connection type to the PCRF.
  • P-GW1 creates a new record in the EPS bearer context list. This record allows P-GW1 to exchange data between the S-GW and the PDN network and initiate charging.
  • P-GW1 returns a Create Session 1 response message to the S-GW.
  • the message carries information such as the P-GW1 address and the PDN address.
  • the S-GW returns a Create Session 1 Response message to the MME.
  • the message carries information such as a PDN address and a P-GW1 address.
  • the MME also selects P-GW2 to establish a PDN connection for the APN according to the MME, and the MME initiates a request for creating a session 2 to the S-GW.
  • the request message carries an IMSI, an APN, a PDN connection type, and a PDN address. Information such as the P-GW2 address.
  • the APN carried in the message is the same as the APN in step 3.
  • the PDN connection type is a service carrying the business continuity requirement.
  • the S-GW creates a new record on its own EPS Bearer table and sends a Session 2 Create Request message to P-GW2.
  • the message carries information such as IMSI, PDN address, APN, and PDN connection type.
  • P-GW2 After receiving the Session 2 creation request, P-GW2 initiates an IP-CAN Session 2 setup to the PCRF.
  • the PCRF returns a default PCC rule for the UE to P-GW2.
  • the establishment process of the dedicated bearer can also be triggered.
  • P-GW2 sends information such as APN and PDN connection type to the PCRF. Since the APNs are the same in the IMSIs provided in steps 4 and 9, the PCRFs selected accordingly are also the same.
  • P-GW2 creates a new record in the EPS bearer context list. This record allows P-GW2 to exchange data between the S-GW and the PDN network and initiate charging.
  • P-GW2 returns a Create Session 2 response message to the S-GW.
  • the message carries information such as the P-GW2 address and the PDN address.
  • the S-GW returns a Create Session 2 response message to the MME.
  • the message carries information such as a PDN address and a P-GW2 address.
  • the MME needs to modify the UE-AMBR allocated to the eNodeB based on the UE-AMBR subscribed by the user and all APN-AMBRs currently being used.
  • the MME returns a PDN Connection Setup Response message to the UE.
  • the message carries information such as APN, PDN Type, PDN address, and SGW TEID.
  • the SGW TEID is used to distinguish PDN connections.
  • the PDN connection 1 has a corresponding SGW TEID1
  • the PDN connection 2 has a corresponding SGW TEID2.
  • the MME needs to return the SGW TEID1 and the SGW TEID2 to the eNodeB for the eNodeB to distinguish between the PDN connection 1 and the PDN connection 2.
  • the message is sent to the eNodeB in an S1_MME control message, that is, a bearer setup request message.
  • the message also includes: a PDN connection setup response message, a UE-AMBR, and the like.
  • the eNodeB sends an RRC Link Reconfiguration message to the UE.
  • the message carries a PDN connection setup response message.
  • the UE sends an RRC Link Reconfiguration Complete message to the eNodeB.
  • the eNodeB returns an S1-AP Bearer Setup Response message to the MME.
  • the UE layer of the UE establishes a PDN connection setup response message.
  • the UE sends a direct to the eNodeB Transfer message (PDN connection establishment response).
  • the eNodeB sends an uplink NAS transport message (PDN Connection Setup Response) to the MME.
  • PDN Connection Setup Response PDN Connection Setup Response
  • the MME After receiving the 16-step bearer setup response message and the 18-step PDN connection setup response message, the MME needs to report the P-GW2 address to the HSS (P-GW2 is used as an anchor point in the handover process, and PDN connection 2 is used for The service bears the continuity requirement for the service, so that once the user switches, the P-GW2 can be found when the session is established after the handover, that is, the PDN connection 2 does not interrupt.
  • the HSS saves the P-GW2 identifier and its corresponding APN, and returns an information report response message to the MME.
  • the PDN 1 and the PDN 2 are established for the UE by selecting P-GW1 and P-GW2. Both PDN connection 1 and PDN connection 2 are established for the same APN.
  • two PDN connections established for the same APN use the same S-GW, and the MME may also select two different S-GWs to establish the PDN connection according to the S-GW selection procedure.
  • FIG. 13 is a flowchart of a handover after the user completes the attachment and the PDN connection establishment shown in FIG. 12 according to an embodiment of the present invention.
  • the non-real-time service uses the PDN connection 1 for data routing before the handover, in real time.
  • the service uses PDN connection 2 for data routing.
  • the UE moves to the area covered by the target eNodeB, and handover occurs across the eNodeB, but handover across the MME does not occur.
  • the UE When the UE moves to the eNodeB coverage area, the UE needs to switch, and establish a data channel between the source eNodeB and the target eNodeB, so that the data of the user on the source eNodeB is adjusted to the target eNodeB;
  • the UE initiates a handover request to the target eNodeB;
  • the target eNodeB After receiving the request, the target eNodeB sends a path switch request to the MME;
  • the MME processes the PDN connection of the user according to the received handover request message according to the CSIPTO indication information in the user context saved in the attachment phase.
  • the PDN connection 2 carries the real-time service, and the PDN connection 2 carries the real-time service.
  • the MME initiates the release of the PDN connection 1, while the P-GW1 initiates the termination process of the IP-CAN session 1.
  • the MME selects a target S-GW that is closer to the current access of the UE to access the UE according to the S-GW selection procedure.
  • the MME sends a request to create a session 2 to the target S-GW, where the request message carries information such as an APN, a PDN connection type, and a P-GW2 address.
  • the target S-GW After receiving the session 2 creation request, the target S-GW initiates a bearer modification request message to the P-GW2.
  • the target S-GW sends the APN and PDN connection type information to the P-GW2.
  • P-GW2 initiates modification of IP-CAN session 2 to the PCRF, and sends the APN and PDN connection type to the PCRF;
  • the target S-GW returns a response message for creating a session 2 request to the MME;
  • the MME initiates a delete session request message to the source S-GW to release the bearer resource.
  • the MME decides to establish PDN connection 3 for the APN selection P-GW3.
  • the MME initiates a session creation 3 request message to the target S-GW, and carries information such as an APN, a PDN connection type, and an address of the P-GW3.
  • the P-GW3 is selected by the MME according to the P-GW selection procedure, and its location is close to the switched user.
  • the APN is the same as the APN information in step 6.
  • the PDN connection type in this step is set to be used to carry non-real time services.
  • the target S-GW initiates a request message for creating a session 3 to the P-GW3, and the message carries information such as an APN and a PDN connection type.
  • the P-GW3 After the P-GW3 receives the request message, it determines, according to the user identifier, the APN, and the PDN connection type information, that multiple PDN connections established by different P-GWs are selected for the same APN of the same user, and therefore the same PCRF needs to be selected. User access service.
  • the PCRF selection program selects the same PCRF for the user based on the user identification, APN, and the like.
  • the P-GW3 initiates an IP-CAN session 3 setup request to the PCRF, and sends the APN and PDN connection type information to the PCRF.
  • IP-CAN session 3 is established between P-GW3 and the PCRF.
  • P-GW3 returns a response to create session 3 to the target S-GW.
  • the target S-GW returns a response to create session 3 to the MME.
  • the MME determines that the process of completing the PDN connection re-establishment for the handover of the UE on the network side.
  • the MME returns a path switch response message to the target eNodeB.
  • the UE-AMBR changes, and the MME needs to send the updated UE-AMBR to the target eNodeB.
  • the target eNodeB After the target eNodeB receives the message, the target eNodeB sends a resource release message to the source eNodeB to notify the source eNodeB that the handover is successful, and requests to release the network resource between the source eNodeB and the target eNodeB.
  • the target eNodeB returns a handover response message to the UE, notifying the user that the handover was successful.
  • the PDN connection 2 will not be interrupted during the entire handover process, and the PDN connection 1 will be released.
  • the MME reselects the nearest P-GW3 to re-establish the PDN connection 3 for carrying services that are not required for service continuity.
  • Both PDN connection 2 and PDN connection 3 are established for the same APN.
  • the real-time service carried on the PDN connection 2 is not interrupted, and the user's service experience is guaranteed.
  • the release of the PDN connection 1 for carrying the non-real-time service before the handover results in a non-real-time service interruption, which can be re-launched after the P-GW3 connection is established.
  • the interruption of non-real-time services will not have a significant impact on the user's business experience.
  • the P-GW3 is closer to the access location after the user switches, so the data routing process of the non-real-time service is optimized, and the network resources are saved.
  • the PCRF determines to bind the PCC rule corresponding to the service flow to the corresponding PDN connection according to the service type and the PDN connection type, that is, for the real-time service, the corresponding PCC rule is bound to the PDN connection 2, It is determined that the real-time service uses the PDN connection 2 bearer; for the non-real-time service, the corresponding PCC rule is bound to the PDN connection 3, which determines that the non-real-time service uses the PDN connection 3 for bearer.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • the PDN connection in the initial attachment process of the user is based on the prior art, that is, a PDN connection 1 (established using P-GW1) is established before the handover to carry real-time and non-real-time services.
  • the second embodiment illustrates that during the handover process, the MME establishes two PDN connections for the same APN of the user according to the CSIPTO indication.
  • One of the PDN connections 1 is not interrupted, but is only used to carry real-time services; the MME establishes a PDN connection 2 (established using P-GW2) for carrying Non-real-time services that were carried out before the switchover, and all new services that were launched after the switchover.
  • the PDN connection 1 is released once the service on the PDN connection 1 is over.
  • the UE can subscribe to multiple APNs, and the user terminal can establish one PDN connection by using each APN, and can also establish multiple PDN connections.
  • the following process messages are for the PDN connection level. If the UE establishes multiple PDN connections by using multiple APNs before the handover, or establishes multiple APN connections by using a single APN, each PDN connection has a corresponding message flow. For convenience of explanation, this embodiment assumes that the user establishes only one PDN connection between the APN and the network.
  • the UE moves to the area covered by the target eNodeB, and the UE needs to switch across the eNodeB, but the MME remains unchanged.
  • FIG. 14 is a flowchart of a UE cross-MME handover according to an embodiment of the present invention. As shown in FIG. 14, the process includes the following steps:
  • the UE When the UE moves to the eNodeB coverage area, the UE needs to switch. Establishing a data channel between the source eNodeB and the target eNodeB, so that the data of the user on the source eNodeB is adjusted to the target eNodeB;
  • the UE initiates a handover request to the target eNodeB;
  • the target eNodeB After receiving the request, the target eNodeB sends a path switch request to the MME;
  • the MME processes the PDN connection of the user according to the received handover request message according to the CSIPTO indication information in the user context saved in the attachment phase.
  • the MME decides to release the dedicated bearer carrying the non-real-time service on the PDN connection 1, and selects the P-GW2 to re-establish the PDN connection 2 to carry the non-real-time service according to the P-GW selection procedure.
  • the MME selects a target S-GW that is closer to the current access of the UE to access the UE according to the S-GW selection procedure.
  • the MME sends a request to create a session 1 to the target S-GW, and the request message carries information such as an APN, a PDN-Priority (PDN connection priority), and a P-GW1 address.
  • the MME sets the PDN-Priority for the PDN connection 1, and its priority is set to low.
  • the MME determines which dedicated bearers need to be migrated according to the EPS bearer list, and which dedicated bearers need to be released. For example, the dedicated bearer used by the real-time service needs to be migrated, and the dedicated bearer used by the non-real-time service needs to be released. For the dedicated bearer to be used, the MME initiates a bearer release procedure.
  • the target S-GW After receiving the session 1 creation request, the target S-GW initiates a bearer modification request message to the P-GW1.
  • the target S-GW sends the APN, PDN-Priority information to the P-GW1.
  • P-GW1 initiates modification of IP-CAN session 1 to the PCRF, and sends APN and PDN-Priority to the PCRF;
  • the target S-GW returns a response message for creating a session 1 request to the MME;
  • the MME initiates a delete session request message to the source S-GW to release the bearer resource.
  • the MME decides to establish a PDN connection 2 for the APN to select P-GW2.
  • the MME initiates a Create Session 2 Request message to the target S-GW, and carries information such as the addresses of the APN, PDN-Priority, and P-GW2.
  • the P-GW2 is selected by the MME according to the P-GW selection procedure, and its location is close to the switched user.
  • the APN is the same as the APN information in step 5.
  • the MME sets the PDN-Priority for the PDN connection 2, which has a higher priority than the PDN connection 1.
  • the target S-GW initiates a request message for creating a session 2 to the P-GW2, and the message carries information such as APN, PDN-Priority, and the like.
  • the P-GW2 After receiving the request message, the P-GW2 determines, according to the user identifier, the APN and the PDN-Priority information, that multiple PDN connections established by different P-GWs are selected for the same APN of the same user, so the same PCRF needs to be selected as the User access service.
  • the PCRF selection program selects the same PCRF for the user based on the user identification, APN, and the like.
  • the P-GW2 initiates an IP-CAN Session 2 setup request to the PCRF, and sends the APN, PDN-Priority information to the PCRF.
  • IP-CAN session 2 is established between P-GW2 and the PCRF.
  • P-GW2 returns a response to create session 2 to the target S-GW.
  • the target S-GW returns a response to create session 2 to the MME.
  • the MME After receiving the response message of step 8 and step 15, the MME determines that the UE is already on the network side. The handover completes the process of PDN connection re-establishment. The MME returns a path switch response message to the target eNodeB.
  • the MME needs to send the updated UE-AMBR to the target eNodeB.
  • the MME also needs to return the target SGW TEID information to the target eNodeB, where the SGW TEID is used to distinguish the PDN connection.
  • the PDN connection 1 has a corresponding SGW TEID1
  • the PDN connection 2 has a corresponding SGW TEID2.
  • the MME needs to return the SGW TEID1 and the SGW TEID2 to the eNodeB for the eNodeB to distinguish between the PDN connection 1 and the PDN connection 2.
  • the target eNodeB After the target eNodeB receives the message, the target eNodeB sends a resource release message to the source eNodeB to notify the source eNodeB that the handover is successful, and requests to release the network resource between the source eNodeB and the target eNodeB.
  • the target eNodeB returns a handover response message to the UE, notifying the user that the handover was successful.
  • FIG. 15 is a flowchart showing service development after handover according to an embodiment of the present invention. As shown in FIG. 15, the process includes the following steps:
  • the PDN connection 1 is still used for routing before and after the handover.
  • P-GW1 determines that there is no data flow on PDN connection 1, and needs to release PDN connection 1.
  • P-GW1 initiates the release process of PDN connection 1.
  • P-GW1 initiates an IP-CAN session termination procedure. At this time, there is only one PDN connection corresponding to the user's APN.
  • the PCRF makes policy decisions for non-real-time services and new services that the user is conducting before the handover.
  • a PCC rule is generated for the service flow decision according to the service type and the PDN connection priority information, and the PCC rule is bound to the bearer corresponding to the PDN connection 1, and the PDN connection 1 is used for routing.
  • the PCRF sends the PCC rule to P-GW2.
  • P-GW2 completes the binding between the service flow (PCC rule description) and the bearer on PDN connection 1.
  • the PDN connection 1 will not be interrupted during the entire handover process, so the real-time service carried on the PDN connection 1 will not be interrupted, ensuring the user's service experience.
  • the dedicated bearer for PDN connection 1 for carrying non-real-time services will be released, and the MME reselects the nearest P-GW2 to re-establish PDN connection 2 for carrying non-real-time services.
  • Both PDN connection 1 and PDN connection 1 are established for the same APN.
  • the P-GW connection 2 can be re-launched after the connection is established, but the interruption of the non-real-time service does not significantly affect the user's service experience.
  • the P-GW2 is closer to the access location after the user is switched, so the data routing process of the non-real-time service is optimized, and the network resources are saved.
  • the PCRF decides to bind the PCC rules corresponding to the service flow to the higher-priority PDN connection 2 according to the PDN connection priority, and once the service carried out on the PDN connection 1 is completed, The PDN connection 1 is released, which realizes that the service data after the handover is routed using the P-GW2 that is closer to the current location of the user, thereby saving network resources.
  • modules or steps of the embodiments of the present invention can be implemented by a general computing device, which can be concentrated on a single computing device or distributed in 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 and, in some cases, may be different from The steps shown or described are performed sequentially, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated into a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.

Landscapes

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

Abstract

本发明公开了一种业务流传输路径优化方法、装置及MME。检测到用户设备UE的对指定因特网协议IP流卸载进行分组数据网关P-GW调整CSIPTO指示信息；依据CSIPTO指示信息，为UE的接入点名称APN选择第一P-GW，并基于第一P-GW建立第一分组数据网络PDN连接，为UE的APN选择第二P-GW，并基于第二P-GW建立第二PDN连接；依据建立的第一PDN连接和/或第二PDN连接对UE的业务流传输路径进行优化处理，通过本发明，解决了相关技术中的数据流的传输路径存在资源浪费的问题，进而达到了在不影响用户业务体验的前提下，通过优化数据路由路径达到节省网络资源开销的效果。

Description

业务流传输路径优化方法、装置及MME 技术领域
本发明涉及通信领域，具体而言，涉及一种业务流传输路径优化方法、装置及MME。
背景技术
第三代合作伙伴计划(3rd Generation Partnership Project，简称为3GPP)开发了演进的分组系统(Evolved Packet System，简称为EPS)网络架构，图1是相关技术中EPS系统架构示意图，如图1所示。该架构由演进的陆地通用无线接入网络(Evolved Universal Terrestrial Radio Access Network，简称为E-UTRAN)、移动管理实体(Mobility Management Entity，简称为MME)、服务网关(Serving Gateway，简称为S-GW)、分组数据网络网关(Packet Data Network Gateway，简称为P-GW)、归属用户服务器(Home Subscriber Server，简称为HSS)、策略和计费规则功能(Policy and Charging Rules Function，简称为PCRF)及其他支撑节点组成。
MME负责移动性管理，非接入层信令的处理，用户移动管理上下文的管理等控制面相关工作，P-GW以及S-GW的选择，空闲状态下手机可达性管理以及跟踪区列表的选择等功能。
S-GW是与E-UTRAN相连的接入网关设备，其功能包括：作为eNodeB间切换的本地锚点在E-UTRAN和P-GW之间转发数据，负责对寻呼等待数据进行缓存，合法监听，数据报文路由以及用户在跨运营商接入的情况下实现基于用户与服务质量类标识(QoS Class Identifier，简称为QCI)的计费。
P-GW则是EPS系统和PDN网络之间的边界网关，其功能包括：用户终端IP地址分配，用户数据报文过滤，传输层报文的服务质量(Quality of Service，简称为QoS)标签管理，基于业务流的计费，动态主机配置版本4/版本6协议(Dynamic Host Configuration Protocol version4/version6，简称为DHCPv4/v6)功能，基于聚合最大速率(Aggregate Maximum Bit Rate，简称为AMBR)的下行速率保证，基于相同保证速率(Guaranteed Bit Rate，简称为GBR)QCI的累积MBR的下行速率保证，负责上下行的承载绑定以及合法监听等功能。
PCRF是策略和计费规则功能实体，它通过Rx接口和运营商网络协议(Internet Protocol，简称为因特网协议)业务网络相连，获取业务信息，PCRF生成QoS以及计费策略，通过Gx/Gxc接口把QoS和计费策略下发策略执行功能执行。策略执行功能 可以是位于P-GW上的策略和计费执行功能(Policy and Charging Enforcement Function，简称为PCEF)或者是位于S-GW上的承载绑定和事件上报功能(Bearer Binding and Event Report Function，简称为BBERF)执行。
3GPP现有系统定义了用户设备(User Equipment，简称为UE)在开展数据业务之前，必须通过接入网络，例如，E-UTRAN，和PDN网络之间建立PDN连接。图2是相关技术中PDN连接建立的流程图，如图2所示，该流程包括如下步骤：
201.UE发起一条非接入层(Non-Access Stratum，简称为NAS)消息，即PDN连接建立请求消息。消息中携带接入点名称(Access Point Name，简称为APN)，PDN Type(PDN类型)，协议配置选项(Protocol Configuration Options，简称为PCO)，Request Type(请求类型)等信息。
其中，PDN Type用于指示UE请求的IP地址的类型是IPv4，IPv4v6还是IPv6；PCO用于在UE和P-GW之间传递信息，这些信息在MME和S-GW上透传；Request Type用于指示是“初始请求”还是“切换”；APN用于MME选择P-GW的依据。
当MME收到APN时，需要根据用户签约信息核实该APN是否允许被用户使用。如果请求消息中没有携带APN，则MME选择Default PDN Subscription Context(缺省的PDN签约上下文)中携带的缺省APN被后续流程使用。
202.MME对请求消息进行处理。
如果201中的Request Type指示为“切换”，则MME需要使用保存在用户数据中的P-GW地址。该P-GW地址是在附着过程中执行位置更新期间由MME取回并保存。如果201中的Request Type指示为“初始请求”，则MME需要执行P-GW选择程序，根据APN、P-GW容量、UE位置信息等选择可供UE和APN对应的PDN网络建立连接的P-GW。
MME为用户请求分配一个Bearer ID(承载标识)，并向S-GW发起创建会话请求消息。消息中携带国际移动用户标识码(International Mobile Subscriber Identification Number，简称为IMSI)，移动用户ISDN号码(Mobile Subscriber International ISDN Number，简称为MSISDN)，RAT Type(无线接入类型)，P-GW Address(P-GW地址)，PDN Address(PDN地址)，Default Bearer QoS(缺省承载QoS)，PDN Type(PDN类型)，Subscribed APN-AMBR(签约APN-AMBR)，APN，EPS Bearer ID(EPS承载标识)，PCO，ECGI(User Location Information，用户位置信息)等信息。
如果Request Type指示为“切换”，则还需要包含Handover Indication信息。
203.S-GW在自己的EPS Bearer表上创建一条新记录，并向P-GW发送会话创建 请求消息。其中P-GW地址在步骤202中由MME执行P-GW选择程序获取。消息中携带：IMSI，MSISDN，RAT Type，PDN Type，Default EPS Bearer QoS，Subscribed APN-AMBR，PDN Address，APN，EPS Bearer ID，PCO，ECGI等信息。
如果Request Type指示为“切换”，则还需要包含Handover Indication信息。
在这一步执行完成之后，S-GW缓存来自P-GW的下行数据，直到接收来自MME的213的消息。
204.P-GW接收会话创建请求之后，如果不是“切换”情况，则向PCRF发起IP-CAN会话建立。PCRF向P-GW返回针对该UE的缺省PCC规则。同时还可以触发专用承载的建立过程。
如果P-GW收到Handover Indication(“切换”)的指示，则P-GW发起IP-CAN会话修改的过程，并向PCRF上报新的IP-CAN Type。
205.P-GW在EPS bearer上下文列表中创建一条新记录，并为缺省承载创建一个Charging ID(计费标识)。该记录允许P-GW在S-GW和PDN网络之间的交互数据，并启动计费。
P-GW向S-GW返回创建会话响应消息。消息中携带P-GW Address，PDN Address，PDN Type，EPS Bearer ID，EPS Bearer QoS，PCO，Charging ID，MS Info Change Reporting Action(Start)，APN-AMBR等信息。
PDN Type用于向UE返回PDN网络的地址。如果是切换情况，则返回给UE的PDN网络地址在切换前后应该保持不变。
如果是“切换”情况，则P-GW不能向S-GW发送下行数据报文。
206.S-GW向MME返回创建会话响应消息。消息携带：PDN Type，PDN Address，P-GW Address，EPS Bearer ID，EPS Bearer QoS，PCO，MS Info Change Reporting Action(Start)，APN-AMBR等信息。
如果是“切换”情况，则向MME发送该消息也表示S-GW和P-GW之间的承载已经建立。
207.如果MME从承载上下文中接收到MS Info Change Reporting Action(Start)信息，则MME需要为该承载上下文保存该信息。当终端位置信息发生改变时，MME需要通过S-GW将UE位置信息上报给P-GW。MME需要基于用户签约的UE-AMBR和当前正在使用的所有APN-AMBR，修改分配给eNodeB的UE-AMBR。
MME向UE返回PDN连接建立响应消息。消息中携带：APN，PDN Type，PDN  Address，EPS Bearer ID，Session Management Request(会话管理请求)，PCO等信息。
该消息包含在一条S1_MME控制消息，即承载建立请求消息中发送给eNodeB。消息中还包含：PDN连接建立响应消息，EPS Bearer QoS，UE-AMBR，S-GW Address等信息。
如果是SIPTO at the Local Network(选择IP流在本地网络卸载)的情况，则S1_MME控制消息，即承载建立请求消息中还包含SIPTO Correlation ID(SIPTO关联标识)。SIPTO Correlation ID用于标识HeNB和L-GW的直接传输通道。
Session Management Request中携带APN-AMBR，QCI信息。如果UE支持UTRAN或者GERAN(GSM EDGE Radio Access Network，GSM/EDGE无线接入网络)接入，则MME还根据EPS Bearer QoS参数产生对应的PDP上下的QoS协商参数，Radio Priority，Packet Flow ID，TI等信息，并且也包含在会话管理请求中。
208.eNodeB向UE发送RRC链接重配置消息。消息中携带PDN连接建立响应消息。
UE保存会话管理请求中的消息，即QoS协商参数，Radio Priority，Packet Flow ID，TI等参数，以便UE通过GERAN或者UTRAN接入。
UE向应用提供EPS Bearer QoS参数用于处理traffic flow。
如果UE接收到的IPv4地址值为0.0.0.0，则UE使用DHCPv4进行IPv4地址协商。如果UE接收的是IPv6接口标识，则等待来自网络的Router Advertisement消息中携带的IPv6prefix信息。
209.UE向eNodeB发送RRC链接重配置完成消息。
210.eNodeB向MME返回S1-AP承载建立响应消息。
如果在207步中包含有SIPTO Correlation ID，eNodeB使用该信息在eNodeB和L-GW之间建立直接的数据通道。
211.UE的NAS层建立一个PDN连接建立响应消息，消息中包含EPS Bearer ID信息。UE给eNodeB发送一个直接传输消息(PDN连接建立响应)。
212.eNodeB给MME发送一个上行NAS传输消息(PDN连接建立响应)。
在发送PDN连接建立响应消息之后，如果UE已经获取到了PDN地址信息，则UE就可以通过eNodeB发送上行数据报文，该数据报文可以通过隧道传输到S-GW和P-GW。
213.在接收到210步的承载建立响应消息和212步的PDN连接建立响应消息后，MME向S-GW发送承载修改请求消息。消息中携带：EPS Bearer ID，eNodeB地址，Handover Indication等信息。Handover Indication是在Request Type指示为“切换”的情况下提供。
214.如果在213步包含了Handover Indication，则S-GW向P-GW发送承载修改请求消息，触发P-GW将和非3GPP IP接入之间的隧道变更为何3GPP接入系统之间的隧道，并立即将缺省EPS承载以及所有专用EPS承载上的报文路由至S-GW。
215.P-GW向S-GW返回承载修改响应。
216.S-GW向MME返回承载修改响应。随后S-GW可以将本地阻塞的下行报文发送给UE。
217.在216步MME接收到承载修改响应消息之后，如果Request Type没有指示为“切换”，且建立了一个EPS bearer，如果用户签约数据指示允许UE执行到非3GPP接入系统的切换，且如果这个PDN连接是第一个和该APN对应的PDN连接，且MME选择的P-GW和此前HSS指示的PDN用户上下文中P-GW地址不同，则MME需要向HSS发送给信息上报请求消息。消息中携带建立PDN连接所使用的P-GW地址和APN，此外还需要携带用于指示P-GW位于哪个PLMN的信息。
218.HSS保存P-GW标识以及和其对应的APN，并向MME返回信息上报响应消息。
UE在附着到网络的过程中会建立缺省的PDN连接。在后续开展业务的过程中根据需要，UE还可以建立到其他PDN网络的PDN连接。每个PDN网络都有一个APN对应，UE想要和哪个PDN网络建立连接，就需要将对应的APN发送给MME，以便MME为用户选择一个P-GW。P-GW是UE和PDN网络之间的连接点，UE根据MME选择的P-GW，建立和P-GW之间的PDN连接。此外根据需要，UE和同一个PDN网络之间还可以建立多个PDN连接，即针对同一个APN可以建立多个PDN连接，但是现有系统规定了这多个PDN连接必须使用相同的P-GW。
3GPP系统还定义了在为UE建立PDN连接所需的P-GW进行选择时，需要参考APN信息、用户的地理位置、P-GW能力(例如容量)等信息。最终P-GW选择功能实体，例如MME，根据这些参考信息确定一个可供UE建立该PDN连接的P-GW列表。列表中的每个P-GW都有一个对应的权重信息，选择一个合适的P-GW(权重最高或最低)供UE建立该PDN连接。
上述相关技术在实现过程中也存在一定的缺陷，图3是相关技术中用户切换场景下进行数据路由的示意图，如图3所示，当用户终端(UE)从区域A的无线网络接入， P-GW选择机制根据UE接入时提供的APN、P-GW容量、UE地理位置等信息，选择了P-GW1、P-GW2、P-GW3可供UE建立和该APN对应的PDN连接。
UE的当前接入位置离P-GW1较近，选择P-GW1建立PDN连接1。虚线A为当UE接入之后通过PDN连接1开展数据业务。
此后UE发生移动，从区域A移动到区域B，即发生了跨接入区域的切换。为了保证切换过程中不影响用户业务体验，相关技术的网络机制规定必须保证业务的连续性，即当UE通过区域B接入时，虽然选择了离区域B较近的S-GW2为UE接入服务，且离区域B较近的P-GW2也可以提供UE和上述PDN网络之间的PDN连接，但是UE必须仍然使用P-GW1建立的PDN连接1，如图中的虚线B所示，开展业务。这样UE移动到区域B时开展的数据业务不会发生中断。
这种在UE移动过程中，将P-GW1作为锚点的方式，虽然保证了用户移动过程中的业务体验不受影响，但也造成了数据路由迂回，即原本移动之后可以选择更近的P-GW2进行数据路由，现在必须仍然使用离接入区域B较远的P-GW1进行数据路由，这势必导致了网络资源的不合理使用。
因此，在相关技术中的数据流的传输路径存在资源浪费的问题。
发明内容
本发明提供了一种业务流传输路径优化方法及装置，以至少解决在相关技术中的数据流的传输路径存在资源浪费的问题。
根据本发明实施例的一个方面，提供了一种业务流传输路径优化方法，包括：检测到用户设备UE的对指定因特网协议IP流卸载进行分组数据网关P-GW调整CSIPTO指示信息；依据所述CSIPTO指示信息，为所述UE的接入点名称APN选择第一P-GW，并基于所述第一P-GW建立第一分组数据网络PDN连接，为所述UE的所述APN选择第二P-GW，并基于所述第二P-GW建立第二PDN连接；依据建立的所述第一PDN连接和/或所述第二PDN连接对所述UE的业务流传输路径进行优化处理。
优选地，在所述UE切换之前，所述UE的所有业务承载于一条PDN连接的情况下，依据所述CSIPTO指示信息，为所述UE的接入点名称APN选择第一P-GW，并基于所述第一P-GW建立第一分组数据网络PDN连接，为所述UE的所述APN选择第二P-GW，并基于所述第二P-GW建立第二PDN连接，以及依据建立的所述第一PDN连接和/或第二PDN连接对所述UE的业务流传输路径进行优化处理包括：在所述UE切换过程中，保留UE切换前的所述PDN连接为所述第一PDN连接，并释放所述第一PDN连接内无业务连续性要求的业务，继续承载有业务连续性要求的业务； 依据所述UE当前接入位置选择所述第二P-GW建立所述第二PDN连接，采用所述第二PDN连接承载所述无业务连续性要求的业务以及所述UE切换后新开展的所有业务。
优选地，依据建立的所述第一PDN连接和/或所述第二PDN连接对所述UE的业务流传输路径进行优化处理包括：为所述第一PDN连接和所述第二PDN连接分配PDN连接优先级，其中，所述第二PDN连接的优先级高于所述第一PDN连接的优先级，切换之后所述UE新开展的业务根据所述PDN连接优先级优先使用所述第二PDN连接进行承载。
优选地，在所述UE切换之前，有业务连续性要求的业务和无业务连续性要求的业务分别承载于不同的PDN连接的情况下，依据所述CSIPTO指示信息，为所述UE的接入点名称APN选择第一P-GW，并基于所述第一P-GW建立第一分组数据网络PDN连接，为所述UE的所述APN选择第二P-GW，并基于所述第二P-GW建立第二PDN连接，以及依据建立的所述第一PDN连接和/或第二PDN连接对所述UE的业务流传输路径进行优化处理包括：在所述UE切换过程中，保留用于承载有业务连续性要求的业务的PDN连接为所述第一PDN连接，继续承载所述UE切换前开展的有业务连续性要求的业务和所述UE切换后新开展的有业务连续性要求的业务；释放用于承载无业务连续性要求的业务的PDN连接，以及依据所述UE当前接入位置重新选择所述第二P-GW重新建立PDN连接为所述第二PDN连接，采用所述第二PDN连接承载所述UE切换前开展的无业务连续性要求的业务和所述UE切换后新开展的无业务连续性要求的业务。
优选地，依据建立的所述第一PDN连接和/或所述第二PDN连接对所述UE的业务流传输路径进行优化处理包括：为所述第一PDN连接设置PDN连接类型，用于说明承载有业务连续性要求的业务，为所述第二PDN连接设置PDN连接类型，用于说明承载无业务连续性要求的业务；依据PDN连接类型和业务类型的匹配关系，确定所述UE新开展的业务使用对应的PDN连接进行承载。
优选地，依据建立的所述第一PDN连接和/或所述第二PDN连接对所述UE的业务流传输路径进行优化处理包括：选择与所述UE当前接入位置最近的所述第二P-GW，并基于所述第二P-GW建立所述第二PDN连接。
根据本发明实施例的另一方面，提供了一种业务流传输路径优化装置，包括：检测模块，设置为检测到用户设备UE的对指定因特网协议IP流卸载进行分组数据网关P-GW调整CSIPTO指示信息；建立模块，设置为依据所述CSIPTO指示信息，为所述UE的接入点名称APN选择第一P-GW，并基于所述第一P-GW建立第一分组数据网络PDN连接，为所述UE的所述APN选择第二P-GW，并基于所述第二P-GW建 立第二PDN连接；处理模块，设置为依据建立的所述第一PDN连接和/或所述第二PDN连接对所述UE的业务流传输路径进行优化处理。
优选地，所述建立模块，还设置为在所述UE切换之前，所述UE的所有业务承载于一条PDN连接的情况下，在所述UE切换过程中，保留UE切换前的所述PDN连接为所述第一PDN连接；所述处理模块，还设置为释放所述第一PDN连接内无业务连续性要求的业务，继续承载有业务连续性要求的业务；所述建立模块，还设置为依据所述UE当前接入位置选择所述第二P-GW建立所述第二PDN连接；所述处理模块，还设置为采用所述第二PDN连接承载所述无业务连续性要求的业务以及所述UE切换后新开展的所有业务。
优选地，所述处理模块包括：分配单元，设置为为所述第一PDN连接和所述第二PDN连接分配PDN连接优先级，其中，所述第二PDN连接的优先级高于所述第一PDN连接的优先级，切换之后所述UE新开展的业务根据所述PDN连接优先级优先使用所述第二PDN连接进行承载。
优选地，所述建立模块，还设置为在所述UE切换之前，有业务连续性要求的业务和无业务连续性要求的业务分别承载于不同的PDN连接的情况下，在所述UE切换过程中，保留用于承载有业务连续性要求的业务的PDN连接为所述第一PDN连接；所述处理模块，还设置为继续承载所述UE切换前开展的有业务连续性要求的业务和所述UE切换后新开展的有业务连续性要求的业务；释放用于承载无业务连续性要求的业务的PDN连接；所述建立模块，还设置为依据所述UE当前接入位置重新选择所述第二P-GW重新建立PDN连接为所述第二PDN连接；所述处理模块，还设置为采用所述第二PDN连接承载所述UE切换前开展的无业务连续性要求的业务和所述UE切换后新开展的无业务连续性要求的业务。
优选地，所述处理模块包括：设置单元，设置为为所述第一PDN连接设置PDN连接类型，用于说明承载有业务连续性要求的业务，为所述第二PDN连接设置PDN连接类型，用于说明承载无业务连续性要求的业务；确定单元，设置为依据PDN连接类型和业务类型的匹配关系，确定所述UE新开展的业务使用对应的PDN连接进行承载。
优选地，所述处理模块包括：处理单元，设置为选择与所述UE当前接入位置最近的所述第二P-GW，并基于所述第二P-GW建立所述第二PDN连接。
根据本发明实施例的还一方面，提供了一种移动性管理实体MME，包括上述任一项所述的装置。
通过本发明实施例，采用检测到用户设备UE的对指定因特网协议IP流卸载进行 分组数据网关P-GW调整CSIPTO指示信息；依据所述CSIPTO指示信息，为所述UE的接入点名称APN选择第一P-GW，并基于所述第一P-GW建立第一分组数据网络PDN连接，为所述UE的所述APN选择第二P-GW，并基于所述第二P-GW建立第二PDN连接；依据建立的所述第一PDN连接和/或所述第二PDN连接对所述UE的业务流传输路径进行优化处理，解决了相关技术中的数据流的传输路径存在资源浪费的问题，进而达到了在不影响用户业务体验的前提下，通过优化数据路由路径达到节省网络资源开销的效果。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是相关技术中EPS系统架构示意图；
图2是相关技术中PDN连接建立的流程图；
图3是相关技术中用户切换场景下进行数据路由的示意图；
图4是根据本发明实施例的业务流传输路径优化方法的流程图；
图5是根据本发明实施例的业务流传输路径优化装置的结构框图；
图6是根据本发明实施例的业务流传输路径优化装置中处理模块56的优选结构框图一；
图7是根据本发明实施例的业务流传输路径优化装置中处理模块56的优选结构框图二；
图8是根据本发明实施例的业务流传输路径优化装置中处理模块56的优选结构框图三；
图9是根据本发明实施例的移动性管理实体MME的结构框图；
图10是根据本发明实施例的用户切换场景下进行数据路由优化的示意图；
图11是根据本发明实施例的用户初始接入以及切换过程中PDN连接建立的示意图；
图12是根据本发明实施例的用户完成附着和PDN连接建立的流程图；
图13是根据本发明实施例的在图12所示的用户完成附着和PDN连接建立之后的 切换流程图；
图14是根据本发明实施例的UE跨MME切换的流程图；
图15是根据本发明实施例的显示的是切换之后的业务开展的流程图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
在本实施例中提供了一种业务流传输路径优化方法，图4是根据本发明实施例的业务流传输路径优化方法的流程图，如图4所示，该流程包括如下步骤：
步骤S402，检测到用户设备UE的对指定因特网协议IP流卸载进行分组数据网关P-GW调整CSIPTO指示信息；
步骤S404，依据CSIPTO指示信息，为UE的接入点名称APN选择第一P-GW，并基于第一P-GW建立第一分组数据网络PDN连接，为UE的APN选择第二P-GW，并基于第二P-GW建立第二PDN连接；
步骤S406，依据建立的第一PDN连接和/或第二PDN连接对UE的业务流传输路径进行优化处理。
通过上述步骤，基于CSIPTO指示信息，为UE基于第一P-GW建立第一PDN连接，为UE基于第二P-GW建立第二PDN连接，依据建立的第一PDN连接，第二PDN连接对UE的业务流传输路径进行优化处理，解决了相关技术中的数据流的传输路径存在资源浪费的问题，进而达到了在不影响用户业务体验的前提下，通过优化数据路由路径达到节省网络资源开销的效果。
依据UE切换前，业务承载情况的不同，为UE建立第一PDN连接，第二PDN连接，以及依据第一PDN连接、第二PDN连接进行UE的业务流传输路径进行优化处理的方式也可以不同，下面分别说明。
例如，在UE切换之前，UE的所有业务承载于一条PDN连接的情况下，依据CSIPTO指示信息，为UE的接入点名称APN选择第一P-GW，并基于第一P-GW建立第一分组数据网络PDN连接，为UE的APN选择第二P-GW，并基于第二P-GW建立第二PDN连接，以及依据建立的第一PDN连接和/或第二PDN连接对UE的业务流传输路径进行优化处理，可以包括：在UE切换过程中，保留UE切换前的PDN连接为第一PDN连接，并释放第一PDN连接内无业务连续性要求的业务，继续承载有业务连续性要求的业务；依据UE当前接入位置选择第二P-GW建立第二PDN连接， 采用第二PDN连接承载无业务连续性要求的业务以及UE切换后新开展的所有业务。
依据建立的第一PDN连接和/或第二PDN连接对UE的业务流传输路径进行优化处理包括：为第一PDN连接和第二PDN连接分配PDN连接优先级，其中，第二PDN连接的优先级高于第一PDN连接的优先级，切换之后UE新开展的业务根据PDN连接优先级优先使用第二PDN连接进行承载。
又例如，在UE切换之前，有业务连续性要求的业务和无业务连续性要求的业务分别承载于不同的PDN连接的情况下，依据CSIPTO指示信息，为UE的接入点名称APN选择第一P-GW，并基于第一P-GW建立第一分组数据网络PDN连接，为UE的APN选择第二P-GW，并基于第二P-GW建立第二PDN连接，以及依据建立的第一PDN连接和/或第二PDN连接对UE的业务流传输路径进行优化处理包括：在UE切换过程中，保留用于承载有业务连续性要求的业务的PDN连接为第一PDN连接，继续承载UE切换前开展的有业务连续性要求的业务和UE切换后新开展的有业务连续性要求的业务；释放用于承载无业务连续性要求的业务的PDN连接，以及依据UE当前接入位置重新选择第二P-GW重新建立PDN连接为第二PDN连接，采用第二PDN连接承载UE切换前开展的无业务连续性要求的业务和UE切换后新开展的无业务连续性要求的业务。
优选地，依据建立的第一PDN连接和/或第二PDN连接对UE的业务流传输路径进行优化处理包括：为第一PDN连接设置PDN连接类型，用于说明承载有业务连续性要求的业务，为第二PDN连接设置PDN连接类型，用于说明承载无业务连续性要求的业务；依据PDN连接类型和业务类型的匹配关系，确定UE新开展的业务使用对应的PDN连接进行承载。
需要说明的是，依据建立的第一PDN连接和/或第二PDN连接对UE的业务流传输路径进行优化处理包括：选择与UE当前接入位置最近的第二P-GW，并基于第二P-GW建立第二PDN连接。
在本实施例中还提供了一种业务流传输路径优化装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图5是根据本发明实施例的业务流传输路径优化装置的结构框图，如图5所示，该装置包括检测模块52、建立模块54和处理模块56，下面对该装置进行说明。
检测模块52，设置为检测到用户设备UE的对指定因特网协议IP流卸载进行分组数据网关P-GW调整CSIPTO指示信息；建立模块54，连接至上述检测模块52，设置 为依据CSIPTO指示信息，为UE的接入点名称APN选择第一P-GW，并基于第一P-GW建立第一分组数据网络PDN连接，为UE的APN选择第二P-GW，并基于第二P-GW建立第二PDN连接；处理模块56，连接至上述建立模块54，设置为依据建立的第一PDN连接和/或第二PDN连接对UE的业务流传输路径进行优化处理。
优选地，建立模块54，还设置为在UE切换之前，UE的所有业务承载于一条PDN连接的情况下，在UE切换过程中，保留UE切换前的PDN连接为第一PDN连接；处理模块56，还设置为释放第一PDN连接内无业务连续性要求的业务，继续承载有业务连续性要求的业务；建立模块54，还设置为依据UE当前接入位置选择第二P-GW建立第二PDN连接；处理模块56，还设置为采用第二PDN连接承载无业务连续性要求的业务以及UE切换后新开展的所有业务。
图6是根据本发明实施例的业务流传输路径优化装置中处理模块56的优选结构框图一，如图6所示，该处理模块56包括分配单元62，下面对该分配单元62进行说明。
分配单元62，设置为为第一PDN连接和第二PDN连接分配PDN连接优先级，其中，第二PDN连接的优先级高于第一PDN连接的优先级，切换之后UE新开展的业务根据PDN连接优先级优先使用第二PDN连接进行承载。
优选地，建立模块54，还设置为在UE切换之前，有业务连续性要求的业务和无业务连续性要求的业务分别承载于不同的PDN连接的情况下，在UE切换过程中，保留用于承载有业务连续性要求的业务的PDN连接为第一PDN连接；处理模块56，还设置为继续承载UE切换前开展的有业务连续性要求的业务和UE切换后新开展的有业务连续性要求的业务；释放用于承载无业务连续性要求的业务的PDN连接；建立模块54，还设置为依据UE当前接入位置重新选择第二P-GW重新建立PDN连接为第二PDN连接；处理模块56，还设置为采用第二PDN连接承载UE切换前开展的无业务连续性要求的业务和UE切换后新开展的无业务连续性要求的业务。
图7是根据本发明实施例的业务流传输路径优化装置中处理模块56的优选结构框图二，如图7所示，该处理模块56包括：设置单元72和确定单元74，下面对该处理模块56进行说明。
设置单元72，设置为为第一PDN连接设置PDN连接类型，用于说明承载有业务连续性要求的业务，为第二PDN连接设置PDN连接类型，用于说明承载无业务连续性要求的业务；确定单元74，连接至上述设置单元72，设置为依据PDN连接类型和业务类型的匹配关系，确定UE新开展的业务使用对应的PDN连接进行承载。
图8是根据本发明实施例的业务流传输路径优化装置中处理模块56的优选结构框图三，如图8所示，该处理模块56包括：处理单元82，下面对该处理单元82进行说 明。
处理单元82，设置为选择与UE当前接入位置最近的第二P-GW，并基于第二P-GW建立第二PDN连接。
图9是根据本发明实施例的移动性管理实体MME的结构框图，如图9所示，该MME90包括上述任一项的业务流传输路径优化装置92。
在相关技术中，通过牺牲网络资源的使用效率，来达到切换时用户业务体验不受影响。而在实际应用中，用户开展的业务虽然多样，但是对时延的要求可分为两大类，一类是诸如IP电话、VPN等对业务连续性要求较高的业务，这类业务在传输过程中不能中断，一旦中断发生就会对业务体验造成较大影响，这类业务称为实时业务；另一类是诸如短消息、网页浏览等对业务连续性要求较低的业务，这类业务在传输过程中即使发生中断也不会对用户的业务体验造成很大影响，甚至短暂的中断用户都感受不到，这类业务称为非实时业务。
在相关技术实现中，切换过程不管对实时业务还是非实时业务都采用路由迂回方式，使数据通过P-GW1锚点路由，保证业务连续，这种做法虽然保证了业务体验，但也造成了网络资源的浪费。
针对相关技术的上述问题，在本实施例中，提供了一种业务流传输路径优化方法，该方法包括：检查到用户设备UE对指定IP流卸载进行PGW调整(Coordinated PGW change for Selected IP Traffic Offload，简称为CSIPTO)的指示信息，该指示信息用于说明UE开展业务时支持数据流的传输路径优化，根据该指示信息为用户的APN选择两个不同的P-GW建立两个PDN连接。用户终端在移动过程中优化接入连接，以实现在不影响用户业务体验的前提下达到业务流的最优传输路径，减轻路由迂回，节省网络资源的目的。下面对该方法进行简单说明。
通过为到PDN网络的同一个APN选择两个不同的P-GW建立两个PDN连接的方式来实现即保证用户业务体验又达到路由路径优化的目的，其中一个PDN连接用于承载有业务连续性要求的业务，在切换过程中该PDN连接始终不会中断，即该PDN连接所使用的P-GW在切换过程中保持不变；另一个PDN连接用于承载没有业务连续性要求的业务，该PDN连接所使用的P-GW靠近用户接入位置，切换过程中，该PDN连接会被释放，并由MME选择切换后靠近用户位置的其他P-GW重新建立PDN连接用于承载上述无业务连续性要求的业务。这种实现方式即不会影响到用户的业务的体验，同时又实现了数据路由路径的优化，节省了网络资源。
下面结合附图对上述方法进行说明。
图10是根据本发明实施例的用户切换场景下进行数据路由优化的示意图，如图 10中，用户切换之前对于实时和非实时业务都使用PDN连接1(使用P-GW1建立)承载。用户切换过程中以及切换之后，对于非实时业务，选择如图10虚线C所示的离区域B较近的P-GW2建立PDN连接2进行路由；而对于实时业务，仍然使用虚线B所示的PDN连接1进行路由。
图11是根据本发明实施例的用户初始接入以及切换过程中PDN连接建立的示意图，如图11所示，用户在初始附着的时候就为到PDN网络的同一个APN选择两个不同的P-GW建立两个PDN连接，如左侧图所示虚线1所示的PDN连接1(使用P-GW1建立)用于承载非实时业务，虚线2所示的PDN连接2(使用P-GW2)用于承载实时业务。用户在切换过程或切换之后，PDN连接2不变(仍然使用P-GW2)，而PDN连接1被释放，由MME选择靠用户切换后接入位置较近的P-GW3建立PDN连接3承载非实时业务。
通过上述数据路由方式，可以在不影响用户业务体验的前提下，通过优化数据路由路径达到节省部分网络资源开销的效果。
下面结合图10、图11对本发明优选实施例进行补充说明。
MME根据用户签约信息中的CSIPTO(Coordinated PGW change for Selected IP Traffic Offload，用于对指定IP流卸载的PGW调整)指示信息判断是否为用户的APN选择两个不同的P-GW建立两个PDN连接。其中，该CSIPTO指示信息用于说明是否允许对用户数据进行路由优化。
如果CSIPTO指示信息不允许对用户数据进行路由优化，则MME按照现有技术完成附着或切换过程中的PDN连接操作；
如果CSIPTO指示信息允许对用户数据进行路由优化，则MME为同一个APN选择两个P-GW分别建立PDN连接，其中一个PDN连接用于承载有业务连续性要求的业务(例如实时业务)，另一个PDN连接用于承载无业务连续性要求的业务(例如非实时业务)。
如果MME收到的请求消息指示为初始请求消息，且CSIPTO指示信息允许对用户数据进行路由优化的情况下，MME为同一个APN选择两个不同的P-GW(如图11左侧图中的P-GW1和P-GW2)分别建立PDN连接(虚线1表示的PDN连接1用于承载无业务连续性要求的业务，虚线2表示的PDN连接2用于承载有业务连续性要求的业务)。
如果MME收到的请求消息指示为切换请求消息，且CSIPTO指示信息允许对用 户数据进行路由优化的情况下：
(1)如果切换前，所有业务(有连续性要求和无连续性要求)使用相同的PDN连接(如图10中选择P-GW1建立的PDN连接1)承载，则切换过程中，MME决定释放用于承载无连续性要求的业务的专用承载，选择靠近用户切换后接入位置的P-GW新建PDN连接(如图10中选择P-GW2建立的PDN连接2，虚线C表示)承载切换前开展的无业务连续性要求的业务以及切换后新开展的业务(包含有连续性要求和无连续性要求的业务)。切换过程中用于承载有业务连续性要求的业务的PDN连接不会释放(如图10中选择P-GW1建立的PDN连接1，虚线B表示)，待业务结束后，释放PDN连接。
(2)如果切换前，有业务连续性要求和无业务连续性要求的业务分别使用不同的PDN连接承载(如图11左侧图中，虚线1表示的使用P-GW1建立的PDN连接1，用于承载无业务连续性要求的业务，虚线2表示的使用P-GW2建立的PDN连接2，用于承载有业务连续性要求的业务)，则切换过程中，MME决定释放PDN连接1，重新选择靠近用户切换后接入位置的P-GW3建立PDN连接3用于承载切换前开展的以及切换后新开展的无业务连续性要求的业务。PDN连接2则保持不中断，用于承载切换过程中以及切换之后有业务连续性要求的业务。
下面对本发明优选实施例进行说明。
实施例一：
实施例一说明的是在用户初始附着过程中就根据CSIPTO指示为用户的同一个APN建立两个PDN连接。其中一个PDN连接1(使用P-GW1建立)用于承载没有业务连续性要求的业务(非实时业务)；PDN连接2(使用P-GW2建立)用于承载有业务连续性要求的业务(实时业务)。切换过程中以及切换之后，PDN连接2不中断，释放PDN连接1，建立PDN连接3(使用P-GW3建立)用于承载没有业务连续性要求的业务。
UE可以签约多个APN，用户终端利用每个APN可以建立一个PDN连接。为了说明方便，本实施例假设用户仅使用一个APN和PDN网络之间建立PDN连接。其他APN的PDN连接建立过程参考本流程。
图12是根据本发明实施例的用户完成附着和PDN连接建立的流程图，如图12所示，该流程包括如下步骤：
1.UE附着到网络，请求建立PDN连接。UE发起PDN连接建立请求消息。消息中携带APN等信息。
当MME收到APN时，需要根据用户签约信息核实该APN是否允许被用户使用。如果请求消息中没有携带APN，则MME选择缺省APN被后续流程使用。
2.MME对请求消息进行处理。
MME首先从用户签约信息中查询该用户是否支持CSIPTO，如果支持则决定为用户选择两个P-GW建立PDN连接；如果不支持则按照原流程建立PDN连接。用户签约信息是在用户附着阶段由MME从HSS获取，此后保存在用户上下文中。
MME执行P-GW选择程序，根据APN、P-GW容量、UE位置信息等选择P-GW供用户建立PDN连接。MME选择P-GW1和P-GW2为该APN建立PDN连接。
3.MME向S-GW发起创建会话1请求消息。消息中携带IMSI，P-GW1地址，PDN地址，APN，以及PDN连接类型等信息。其中PDN连接类型用于说明该PDN连接用于承载无业务连续性要求的业务。
4.S-GW在自己的EPS Bearer表上创建一条新记录，并向P-GW1发送会话1创建请求消息。其中P-GW1地址在步骤2中由MME执行P-GW选择程序获取。消息中携带：IMSI，PDN地址，APN，PDN连接类型等信息。
5.P-GW1接收会话1创建请求之后，向PCRF发起IP-CAN会话1建立。PCRF向P-GW1返回针对该UE的缺省PCC规则。同时还可以触发专用承载建立过程。P-GW1将APN，PDN连接类型等信息发送给PCRF。
6.P-GW1在EPS bearer上下文列表中创建一条新记录。该记录允许P-GW1在S-GW和PDN网络之间的交互数据，并启动计费。
P-GW1向S-GW返回创建会话1响应消息。消息中携带P-GW1地址，PDN地址等信息。
7.S-GW向MME返回创建会话1响应消息。消息携带PDN地址，P-GW1地址等信息。
8.根据步骤2中MME还选择了P-GW2为该APN建立PDN连接，MME向S-GW发起创建会话2的请求，请求消息中携带IMSI，APN，PDN连接类型，PDN地址， P-GW2地址等信息。该消息中携带的APN和步骤3中的APN相同。该步骤中PDN连接类型为承载有业务连续性要求的业务。
9.S-GW在自己的EPS Bearer表上创建一条新记录，并向P-GW2发送会话2创建请求消息。消息中携带：IMSI，PDN地址，APN，PDN连接类型等信息。
10.P-GW2接收会话2创建请求之后，向PCRF发起IP-CAN会话2建立。PCRF向P-GW2返回针对该UE的缺省PCC规则。同时还可以触发专用承载的建立过程。P-GW2将APN，PDN连接类型等信息发送给PCRF。由于步骤4和步骤9中提供的IMSI，APN相同，因此据此选择的PCRF也为同一个。
11.P-GW2在EPS bearer上下文列表中创建一条新记录。该记录允许P-GW2在S-GW和PDN网络之间的交互数据，并启动计费。
P-GW2向S-GW返回创建会话2响应消息。消息中携带P-GW2地址，PDN地址等信息。
12.S-GW向MME返回创建会话2响应消息。消息携带PDN地址，P-GW2地址等信息。
13.MME需要基于用户签约的UE-AMBR和当前正在使用的所有APN-AMBR，修改分配给eNodeB的UE-AMBR。
MME向UE返回PDN连接建立响应消息。消息中携带：APN，PDN Type，PDN地址，SGW TEID等信息。其中SGW TEID用于区分PDN连接。PDN连接1有对应的SGW TEID1，PDN连接2有对应的SGW TEID2，MME需要将SGW TEID1和SGW TEID2返回给eNodeB，供eNodeB区分PDN连接1和PDN连接2。
该消息包含在一条S1_MME控制消息，即承载建立请求消息中发送给eNodeB。消息中还包含：PDN连接建立响应消息，UE-AMBR等信息。
14.eNodeB向UE发送RRC链接重配置消息。消息中携带PDN连接建立响应消息。
15.UE向eNodeB发送RRC链接重配置完成消息。
16.eNodeB向MME返回S1-AP承载建立响应消息。
17.UE的NAS层建立一个PDN连接建立响应消息。UE给eNodeB发送一个直接 传输消息(PDN连接建立响应)。
18.eNodeB给MME发送一个上行NAS传输消息(PDN连接建立响应)。
19.在接收到16步的承载建立响应消息和18步的PDN连接建立响应消息后，MME需要将P-GW2地址上报给HSS(P-GW2作为切换过程中的锚点，PDN连接2用于承载对业务有连续性要求的业务)，以便用户一旦发生切换，保证切换之后建立会话时还能找到P-GW2，即PDN连接2不会发生中断。
20.HSS保存P-GW2标识以及和其对应的APN，并向MME返回信息上报响应消息。
在UE附着成功之后，为UE选择了P-GW1和P-GW2建立了PDN连接1和PDN连接2。PDN连接1和PDN连接2都针对相同的APN建立。本实施例中为同一个APN建立的两个PDN连接都使用相同的S-GW，MME也可根据S-GW选择程序，分别选择两个不同的S-GW建立上述PDN连接。
图13是根据本发明实施例的在图12所示的用户完成附着和PDN连接建立之后的切换流程图，如图13所示，在切换之前，非实时业务使用PDN连接1进行数据路由，实时业务使用PDN连接2进行数据路由。此后UE移动到了目标eNodeB覆盖的区域下面，发生了跨eNodeB的切换，但是不会发生跨MME的切换。
实施步骤如下描述：
1.当UE移动到eNodeB覆盖区域时，UE需要切换，在源eNodeB和目标eNodeB之间建立数据通道，以便该用户在源eNodeB上的数据调整到目标eNodeB中；
2.UE向目标eNodeB发起切换请求；
3.目标eNodeB接收请求之后，向MME发送路径切换请求；
4.MME根据接收的切换请求消息，根据附着阶段保存的用户上下文中的CSIPTO指示信息，对用户的PDN连接进行处理。由于切换之前PDN连接1承载非实时业务，PDN连接2承载实时业务，因此MME决定释放PDN连接1，根据P-GW选择程序选择P-GW3重新建立PDN连接3承载非实时业务。
5.MME发起PDN连接1的释放，同时P-GW1发起IP-CAN会话1的终止过程。
6.MME根据S-GW选择程序，选择离UE当前接入较近的目标S-GW为UE接入服务。MME向目标S-GW发送创建会话2请求，请求消息中携带APN，PDN连接类型，P-GW2地址等信息。
7.目标S-GW接收到会话2创建请求之后，向P-GW2发起承载修改请求消息。目标S-GW将APN，PDN连接类型信息发送给P-GW2。
8.P-GW2向PCRF发起IP-CAN会话2的修改，将APN和PDN连接类型发送给PCRF；
9.目标S-GW向MME返回创建会话2请求的响应消息；
10.MME向源S-GW发起删除会话请求消息，用于释放承载资源；
11.当S-GW释放了相关承载资源后，向MME返回删除会话响应消息；
12.根据步骤4中MME的判断，MME决定为该APN选择P-GW3建立PDN连接3。
MME向目标S-GW发起创建会话3请求消息，携带APN，PDN连接类型，P-GW3的地址等信息。P-GW3由MME根据P-GW选择程序选择，其位置靠近切换后的用户。该APN和步骤6中的APN信息相同。该步骤中的PDN连接类型设置为用于承载非实时业务。
13.目标S-GW向P-GW3发起创建会话3的请求消息，消息中携带APN，PDN连接类型等信息。
14.P-GW3接收请求消息之后，根据用户标识，APN，PDN连接类型信息判断是为同一个用户的同一个APN选择不同的P-GW建立的多PDN连接，因此需要选择相同的PCRF为该用户的接入服务。PCRF选择程序根据用户标识、APN等信息为用户选择相同的PCRF。
P-GW3向PCRF发起IP-CAN会话3建立请求，并将APN，PDN连接类型信息发送给PCRF。
P-GW3和PCRF之间建立IP-CAN会话3。
15.P-GW3向目标S-GW返回创建会话3的响应。
16.目标S-GW向MME返回创建会话3的响应。
17.在收到步骤9和步骤16的响应消息之后，MME判断在网络侧已经为UE的切换完成了PDN连接重建的过程。MME向目标eNodeB返回路径切换响应消息。
在切换过程中，如果和该用户相关的专用承载的发生修改或者释放，则UE-AMBR发生改变，此时MME需要将更新后的UE-AMBR发送给目标eNodeB。
18.目标eNodeB收到消息之后，目标eNodeB向源eNodeB发送资源释放消息，通知源eNodeB切换成功，要求释放源eNodeB和目标eNodeB之间的网络资源。
19.目标eNodeB向UE返回切换响应消息，通知用户切换成功。
整个切换过程中PDN连接2不会发生中断，PDN连接1会被释放，MME重新选择就近的P-GW3重新建立PDN连接3用于承载对业务连续性没有要求的业务。PDN连接2和PDN连接3都是针对同一个APN建立。
因此承载在PDN连接2上的实时业务不会发生中断，保证了用户的业务体验。而在切换之前用于承载非实时业务的PDN连接1的释放导致了非实时业务中断，在P-GW3连接上建立之后才能重新开展。但非实时业务得中断不会对用户的业务体验造成显著影响。而在切换之后P-GW3更靠近用户切换之后的接入位置，因此对非实时业务的数据路由过程进行了优化，节省了网络资源。
对于新开展的业务，PCRF根据业务类型和PDN连接类型，决定将业务流对应的PCC规则绑定到对应的PDN连接上，即对于实时业务，其对应的PCC规则绑定到PDN连接2上，决定了实时业务使用PDN连接2承载；对于非实时业务，其对应的PCC规则绑定到PDN连接3上，决定了非实时业务使用PDN连接3进行承载。
实施例二：
用户初始附着过程中PDN连接按照现有技术，即切换之前建立一个PDN连接1(使用P-GW1建立)承载实时和非实时业务。实施例二说明的是在切换过程中，MME根据CSIPTO指示为用户的同一个APN建立两个PDN连接。其中一个PDN连接1不中断，但仅用于承载实时业务；MME建立PDN连接2(使用P-GW2建立)用于承载 切换之前开展的非实时业务，以及切换之后新开展的所有业务。切换之后，PDN连接1上的业务一旦结束就释放PDN连接1。
UE可以签约多个APN，用户终端利用每个APN可以建立一个PDN连接，也可以建立多个PDN连接。下面的流程消息是针对PDN连接级别的。如果切换之前UE利用多个APN建立了多个PDN连接，或者利用单个APN建立了多个APN连接，则每个PDN连接都有对应的消息流程。为了说明的方便，本实施例假设用户仅使用了一个APN和网络之间建立了一个PDN连接。
在切换之前，UE开展的所有业务(包含实时业务和非实时业务)使用PDN连接进行数据路由。
此后UE移动到了目标eNodeB覆盖的区域下面，UE需要发生跨eNodeB的切换，但MME保持不变。
图14是根据本发明实施例的UE跨MME切换的流程图，如图14所示，该流程包括如下步骤：
1.当UE移动到eNodeB覆盖区域时，UE需要切换。在源eNodeB和目标eNodeB之间建立数据通道，以便该用户在源eNodeB上的数据调整到目标eNodeB中；
2.UE向目标eNodeB发起切换请求；
3.目标eNodeB接收请求之后，向MME发送路径切换请求；
4.MME根据接收的切换请求消息，根据附着阶段保存的用户上下文中的CSIPTO指示信息，对用户的PDN连接进行处理。
由于切换之前PDN连接1承载实时和非实时业务，因此MME决定释放PDN连接1上承载非实时业务的专用承载，并根据P-GW选择程序选择P-GW2重新建立PDN连接2承载非实时业务。
5.MME根据S-GW选择程序，选择离UE当前接入较近的目标S-GW为UE接入服务。MME向目标S-GW发送创建会话1请求，请求消息中携带APN，PDN-Priority(PDN连接优先级)，P-GW1地址等信息。
则MME为该PDN连接1设置PDN-Priority，其优先级设置为低。
MME根据EPS承载列表决定哪些专用承载需要迁移，哪些专用承载需要释 放，例如被实时业务使用的专用承载需要迁移，被非实时业务使用的专用承载需要释放；对于需要使用的专用承载，MME发起承载释放流程。
6.目标S-GW接收到会话1创建请求之后，向P-GW1发起承载修改请求消息。目标S-GW将APN，PDN-Priority信息发送给P-GW1。
7.P-GW1向PCRF发起IP-CAN会话1的修改，将APN和PDN-Priority发送给PCRF；
8.目标S-GW向MME返回创建会话1请求的响应消息；
9.MME向源S-GW发起删除会话请求消息，用于释放承载资源；
10.当源S-GW释放了相关承载资源后，向MME返回删除会话响应消息；
11.MME决定为该APN选择P-GW2建立PDN连接2。
MME向目标S-GW发起创建会话2请求消息，携带APN，PDN-Priority，P-GW2的地址等信息。P-GW2由MME根据P-GW选择程序选择，其位置靠近切换后的用户。该APN和步骤5中的APN信息相同。
MME为PDN连接2设置PDN-Priority，其优先级要高于PDN连接1的优先级。
12.目标S-GW向P-GW2发起创建会话2的请求消息，消息中携带APN，PDN-Priority等信息。
13.P-GW2接收请求消息之后，根据用户标识，APN，PDN-Priority信息判断是为同一个用户的同一个APN选择不同的P-GW建立的多PDN连接，因此需要选择相同的PCRF为该用户的接入服务。PCRF选择程序根据用户标识、APN等信息为用户选择相同的PCRF。
P-GW2向PCRF发起IP-CAN会话2建立请求，并将APN，PDN-Priority信息发送给PCRF。
P-GW2和PCRF之间建立IP-CAN会话2。
14.P-GW2向目标S-GW返回创建会话2的响应。
15.目标S-GW向MME返回创建会话2的响应。
16.在收到步骤8和步骤15的响应消息之后，MME判断在网络侧已经为UE的 切换完成了PDN连接重建的过程。MME向目标eNodeB返回路径切换响应消息。
在切换过程中，如果和该用户相关的专用承载的发生修改或者释放，则UE-AMBR发生改变，此时MME需要将更新后的UE-AMBR发送给目标eNodeB。另外MME还需要向目标eNodeB返回目标SGW TEID信息，其中SGW TEID用于区分PDN连接。PDN连接1有对应的SGW TEID1，PDN连接2有对应的SGW TEID2，MME需要将SGW TEID1和SGW TEID2返回给eNodeB，供eNodeB区分PDN连接1和PDN连接2。
17.目标eNodeB收到消息之后，目标eNodeB向源eNodeB发送资源释放消息，通知源eNodeB切换成功，要求释放源eNodeB和目标eNodeB之间的网络资源。
18.目标eNodeB向UE返回切换响应消息，通知用户切换成功。
切换完成之后，针对同一个APN建立有PDN连接1和PDN连接2，且PDN连接2的优先级高于PDN连接1的优先级。图15是根据本发明实施例的显示的是切换之后的业务开展的流程图，如图15所示，该流程包括如下步骤：
1.对于切换之前用户正在开展的实时业务，由于这部分业务在切换过程一旦发生中断，则会对用户的业务体验造成较大的冲击，因此在切换前后仍然使用PDN连接1进行路由。
2.当业务开展结束，P-GW1判断PDN连接1上已经没有数据流存在时，需要释放PDN连接1。
3.P-GW1发起PDN连接1的释放过程。
4.P-GW1发起IP-CAN会话终止过程。此时和用户的该APN对应的只有一个PDN连接。
对于切换之前用户正在开展的非实时业务以及新开展的业务，PCRF进行策略决策。根据业务类型和PDN连接优先级信息，为业务流决策产生PCC规则，将PCC规则绑定到PDN连接1对应的承载上，使用PDN连接1进行路由。
5.PCRF将PCC规则下发给P-GW2。
6.P-GW2完成业务流(PCC规则描述)和PDN连接1上的承载之间的绑定。
7.切换之前开展的非实时业务和新开展的业务使用PDN连接2进行传输。
整个切换过程中PDN连接1不会发生中断，因此承载在PDN连接1上的实时业务不会发生中断，保证了用户的业务体验。PDN连接1用于承载非实时业务的专用承载会被释放，MME重新选择就近的P-GW2重新建立PDN连接2用于承载非实时业务。PDN连接1和PDN连接1都是针对同一个APN建立。
因此，切换过程中虽然非实时业务发生中断，在P-GW连接2建立之后才能重新开展，但非实时业务的中断不会对用户的业务体验造成显著影响。而在切换之后P-GW2更靠近用户切换之后的接入位置，因此对非实时业务的数据路由过程进行了优化，节省了网络资源。
对于新开展的实时和非实时业务，PCRF根据PDN连接优先级，会决定将业务流对应的PCC规则绑定到优先级较高PDN连接2上，而对于PDN连接1上开展的业务一旦结束，就会释放PDN连接1，这就实现了切换之后的业务数据都使用离用户当前位置较近的P-GW2进行路由，节省了网络资源。
显然，本领域的技术人员应该明白，上述的本发明实施例的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
如上所述，通过上述实施例及优选实施方式，解决了相关技术中的数据流的传输路径存在资源浪费的问题，进而达到了在不影响用户业务体验的前提下，通过优化数据路由路径达到节省网络资源开销的效果。

Claims (13)

  1. 一种业务流传输路径优化方法，包括：
    检测到用户设备UE的对指定因特网协议IP流卸载进行分组数据网关P-GW调整CSIPTO指示信息；
    依据所述CSIPTO指示信息，为所述UE的接入点名称APN选择第一P-GW，并基于所述第一P-GW建立第一分组数据网络PDN连接，为所述UE的所述APN选择第二P-GW，并基于所述第二P-GW建立第二PDN连接；
    依据建立的所述第一PDN连接和/或所述第二PDN连接对所述UE的业务流传输路径进行优化处理。
  2. 根据权利要求1所述的方法，其中，在所述UE切换之前，所述UE的所有业务承载于一条PDN连接的情况下，依据所述CSIPTO指示信息，为所述UE的接入点名称APN选择第一P-GW，并基于所述第一P-GW建立第一分组数据网络PDN连接，为所述UE的所述APN选择第二P-GW，并基于所述第二P-GW建立第二PDN连接，以及依据建立的所述第一PDN连接和/或第二PDN连接对所述UE的业务流传输路径进行优化处理包括：
    在所述UE切换过程中，保留UE切换前的所述PDN连接为所述第一PDN连接，并释放所述第一PDN连接内无业务连续性要求的业务，继续承载有业务连续性要求的业务；依据所述UE当前接入位置选择所述第二P-GW建立所述第二PDN连接，采用所述第二PDN连接承载所述无业务连续性要求的业务以及所述UE切换后新开展的所有业务。
  3. 根据权利要求2所述的方法，其中，依据建立的所述第一PDN连接和/或所述第二PDN连接对所述UE的业务流传输路径进行优化处理包括：
    为所述第一PDN连接和所述第二PDN连接分配PDN连接优先级，其中，所述第二PDN连接的优先级高于所述第一PDN连接的优先级，切换之后所述UE新开展的业务根据所述PDN连接优先级优先使用所述第二PDN连接进行承载。
  4. 根据权利要求1所述的方法，其中，在所述UE切换之前，有业务连续性要求的业务和无业务连续性要求的业务分别承载于不同的PDN连接的情况下，依据所述CSIPTO指示信息，为所述UE的接入点名称APN选择第一P-GW，并基于所述第一P-GW建立第一分组数据网络PDN连接，为所述UE的所述APN选择第二P-GW，并基于所述第二P-GW建立第二PDN连接，以及依据建立的所述第一PDN连接和/或第二PDN连接对所述UE的业务流传输路径进行优化处理包括：
    在所述UE切换过程中，保留用于承载有业务连续性要求的业务的PDN连接 为所述第一PDN连接，继续承载所述UE切换前开展的有业务连续性要求的业务和所述UE切换后新开展的有业务连续性要求的业务；释放用于承载无业务连续性要求的业务的PDN连接，以及依据所述UE当前接入位置重新选择所述第二P-GW重新建立PDN连接为所述第二PDN连接，采用所述第二PDN连接承载所述UE切换前开展的无业务连续性要求的业务和所述UE切换后新开展的无业务连续性要求的业务。
  5. 根据权利要求4所述的方法，其中，依据建立的所述第一PDN连接和/或所述第二PDN连接对所述UE的业务流传输路径进行优化处理包括：
    为所述第一PDN连接设置PDN连接类型，用于说明承载有业务连续性要求的业务，为所述第二PDN连接设置PDN连接类型，用于说明承载无业务连续性要求的业务；
    依据PDN连接类型和业务类型的匹配关系，确定所述UE新开展的业务使用对应的PDN连接进行承载。
  6. 根据权利要求1至5中任一项所述的方法，其中，依据建立的所述第一PDN连接和/或所述第二PDN连接对所述UE的业务流传输路径进行优化处理包括：
    选择与所述UE当前接入位置最近的所述第二P-GW，并基于所述第二P-GW建立所述第二PDN连接。
  7. 一种业务流传输路径优化装置，包括：
    检测模块，设置为检测到用户设备UE的对指定因特网协议IP流卸载进行分组数据网关P-GW调整CSIPTO指示信息；
    建立模块，设置为依据所述CSIPTO指示信息，为所述UE的接入点名称APN选择第一P-GW，并基于所述第一P-GW建立第一分组数据网络PDN连接，为所述UE的所述APN选择第二P-GW，并基于所述第二P-GW建立第二PDN连接；
    处理模块，设置为依据建立的所述第一PDN连接和/或所述第二PDN连接对所述UE的业务流传输路径进行优化处理。
  8. 根据权利要求7所述的装置，其中，
    所述建立模块，还设置为在所述UE切换之前，所述UE的所有业务承载于一条PDN连接的情况下，在所述UE切换过程中，保留UE切换前的所述PDN连接为所述第一PDN连接；
    所述处理模块，还设置为释放所述第一PDN连接内无业务连续性要求的业 务，继续承载有业务连续性要求的业务；
    所述建立模块，还设置为依据所述UE当前接入位置选择所述第二P-GW建立所述第二PDN连接；
    所述处理模块，还设置为采用所述第二PDN连接承载所述无业务连续性要求的业务以及所述UE切换后新开展的所有业务。
  9. 根据权利要求8所述的装置，其中，所述处理模块包括：
    分配单元，设置为为所述第一PDN连接和所述第二PDN连接分配PDN连接优先级，其中，所述第二PDN连接的优先级高于所述第一PDN连接的优先级，切换之后所述UE新开展的业务根据所述PDN连接优先级优先使用所述第二PDN连接进行承载。
  10. 根据权利要求7所述的装置，其中，
    所述建立模块，还设置为在所述UE切换之前，有业务连续性要求的业务和无业务连续性要求的业务分别承载于不同的PDN连接的情况下，在所述UE切换过程中，保留用于承载有业务连续性要求的业务的PDN连接为所述第一PDN连接；
    所述处理模块，还设置为继续承载所述UE切换前开展的有业务连续性要求的业务和所述UE切换后新开展的有业务连续性要求的业务；释放用于承载无业务连续性要求的业务的PDN连接；
    所述建立模块，还设置为依据所述UE当前接入位置重新选择所述第二P-GW重新建立PDN连接为所述第二PDN连接；
    所述处理模块，还设置为采用所述第二PDN连接承载所述UE切换前开展的无业务连续性要求的业务和所述UE切换后新开展的无业务连续性要求的业务。
  11. 根据权利要求10所述的装置，其中，所述处理模块包括：
    设置单元，设置为为所述第一PDN连接设置PDN连接类型，用于说明承载有业务连续性要求的业务，为所述第二PDN连接设置PDN连接类型，用于说明承载无业务连续性要求的业务；
    确定单元，设置为依据PDN连接类型和业务类型的匹配关系，确定所述UE新开展的业务使用对应的PDN连接进行承载。
  12. 根据权利要求7至11中任一项所述的装置，其中，所述处理模块包括：
    处理单元，设置为选择与所述UE当前接入位置最近的所述第二P-GW，并基于所述第二P-GW建立所述第二PDN连接。
  13. 一种移动性管理实体MME，包括权利要求7至12中任一项所述的装置。
PCT/CN2015/097502 2014-12-31 2015-12-15 业务流传输路径优化方法、装置及mme WO2016107405A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410854958.7A CN105813111B (zh) 2014-12-31 2014-12-31 业务流传输路径优化方法、装置及mme
CN201410854958.7 2014-12-31

Publications (1)

Publication Number Publication Date
WO2016107405A1 true WO2016107405A1 (zh) 2016-07-07

Family

ID=56284209

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/097502 WO2016107405A1 (zh) 2014-12-31 2015-12-15 业务流传输路径优化方法、装置及mme

Country Status (2)

Country Link
CN (1) CN105813111B (zh)
WO (1) WO2016107405A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106255161B (zh) * 2016-08-09 2019-10-25 上海华为技术有限公司 分组数据网pdn连接建立的方法、控制面cp及用户设备ue
CN106332204A (zh) * 2016-08-19 2017-01-11 广东工业大学 一种pgw切换方法及系统
CN107888398B (zh) * 2016-09-29 2019-05-14 中国联合网络通信集团有限公司 一种业务承载系统及控制方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101552978A (zh) * 2008-03-31 2009-10-07 华为技术有限公司 实现路由优化的方法、系统及装置
WO2011085373A2 (en) * 2010-01-11 2011-07-14 Research In Motion Limited System and method for enabling session context continuity of local service availability in local cellular coverage
CN102868999A (zh) * 2011-07-04 2013-01-09 中兴通讯股份有限公司 分组数据网络连接的建立方法及系统
CN102892211A (zh) * 2011-07-22 2013-01-23 华为终端有限公司 一种业务卸载方法、移动性管理实体

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100428717C (zh) * 2005-09-29 2008-10-22 华为技术有限公司 保持业务会话连续性的方法
CN1980224A (zh) * 2005-12-01 2007-06-13 华为技术有限公司 基于主备网关设备状态切换后业务恢复的方法及系统
CN101212810B (zh) * 2006-12-27 2012-04-25 华为技术有限公司 无线网络中用户设备切换方法
CN102480782B (zh) * 2010-11-25 2016-03-30 中兴通讯股份有限公司 网关重定位方法和源分流网关
CN103517264B (zh) * 2012-06-29 2017-04-12 华为终端有限公司 用于切换网络的方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101552978A (zh) * 2008-03-31 2009-10-07 华为技术有限公司 实现路由优化的方法、系统及装置
WO2011085373A2 (en) * 2010-01-11 2011-07-14 Research In Motion Limited System and method for enabling session context continuity of local service availability in local cellular coverage
CN102868999A (zh) * 2011-07-04 2013-01-09 中兴通讯股份有限公司 分组数据网络连接的建立方法及系统
CN102892211A (zh) * 2011-07-22 2013-01-23 华为终端有限公司 一种业务卸载方法、移动性管理实体

Also Published As

Publication number Publication date
CN105813111B (zh) 2021-01-26
CN105813111A (zh) 2016-07-27

Similar Documents

Publication Publication Date Title
CN107548127B (zh) 支持数据传输的方法和设备
EP3249863B1 (en) Access control apparatus, system and method
US8693456B2 (en) Method, system, and device for radio network aggregation
US9913174B2 (en) Method, device and system for implementing optimized inter-rat handover
WO2016107404A1 (zh) 业务流传输路径优化方法、装置及mme
US9480099B2 (en) Mobility anchor relocation
JP5970723B2 (ja) 輻輳状態報告方法およびアクセス・ネットワーク装置
US11825356B2 (en) Policy control method and system, network element, and storage medium
KR20100060800A (ko) ＨｅＮＢ에서 단말에게 선택적으로 자원을 할당하기 위한 시스템 및 장치
KR101673980B1 (ko) 3gpp 무선 액세스 기술 간 핸드오버 시의 ip 트래픽 분산 방법 및 장치
JP6199862B2 (ja) ハンドオーバー失敗防止方法
TW201320697A (zh) 網際網路協定流行動的方法
US20140169332A1 (en) Method for supporting selection of pdn connections for a mobile terminal and mobile terminal
WO2011095100A1 (zh) 一种对本地ip连接的建立进行控制的方法和系统
US20160183127A1 (en) Methods, systems and devices for supporting local breakout in small cell architecture
WO2012041073A1 (zh) 一种实现流迁移的方法及系统
WO2015174700A1 (ko) Csipto를 지원하는 무선 통신 시스템에서 apn-ambr 설정 방법 및 이를 위한 장치
WO2015062065A1 (zh) 一种与分组数据网络建立连接的装置、设备及方法
US20180255481A1 (en) Service flow transmission method and apparatus
WO2016107405A1 (zh) 业务流传输路径优化方法、装置及mme
WO2012167460A1 (zh) 实现lipa或sipto的移动性的方法和设备
WO2012065293A1 (zh) 业务的接入控制方法、装置及用户设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15875083

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

Country of ref document: EP

Kind code of ref document: A1