CN102480782B - Gateway method for relocating and source shunting gateway - Google Patents

Gateway method for relocating and source shunting gateway Download PDF

Info

Publication number
CN102480782B
CN102480782B CN201010560767.1A CN201010560767A CN102480782B CN 102480782 B CN102480782 B CN 102480782B CN 201010560767 A CN201010560767 A CN 201010560767A CN 102480782 B CN102480782 B CN 102480782B
Authority
CN
China
Prior art keywords
shunting gateway
gateway
information
shunting
management entity
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
CN201010560767.1A
Other languages
Chinese (zh)
Other versions
CN102480782A (en
Inventor
吴瑟
叶海洋
刘建业
周娜
梁爽
霍玉臻
王静
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Suzhou Medical Device Industry Development Group Co ltd
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to CN201010560767.1A priority Critical patent/CN102480782B/en
Priority to PCT/CN2011/081151 priority patent/WO2012068935A1/en
Publication of CN102480782A publication Critical patent/CN102480782A/en
Application granted granted Critical
Publication of CN102480782B publication Critical patent/CN102480782B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16—Gateway arrangements

Abstract

The invention discloses a kind of gateway method for relocating and source shunting gateway, wherein, the method comprises: when terminal carries out mobility event, the information updating request that source shunting gateway receiving mobility management entity sends; Described source shunting gateway creates information to target shunting gateway; Described source shunting gateway sends information updating response to described Mobility Management Entity, and wherein, described information updating response carries the information of described target shunting gateway.The invention solves the problem that existing mobile flow process cannot complete the handoff functionality across shunting gateway, achieve the locomotive function across shunting gateway.

Description

Gateway method for relocating and source shunting gateway
Technical field
The present invention relates to moving communicating field, in particular to a kind of gateway method for relocating and source shunting gateway.
Background technology
Third generation partner program (3rdGenerationPartnershipProject, referred to as 3GPP) grouping system (EvolvedPacketSystem of evolution, referred to as EPS) by the universal mobile telecommunications system land radio access web (EvolvedUniversalTerrestrialRadioAccessNetwork of evolution, referred to as E-UTRAN), mobile management unit (MobilityManagementEntity, referred to as MME), gateway (ServingGateway, S-GW), grouped data network gateway (PacketDataNetworkGateway, referred to as P-GW or PDNGW), home subscriber server (HomeSubscriberServer, referred to as HSS), authentication and authorization charging (the Authentication of 3GPP, AuthorizationandAccounting, referred to as AAA) server, "Policy and Charging Rules Function (PolicyandChargingRulesFunction, referred to as PCRF) entity and other support nodes composition.
Fig. 1 is the schematic diagram of the EPS framework according to correlation technique, and as shown in Figure 1, Mobility Management Entity is responsible for the related work of the chain of command such as process and the contextual management of user's mobile management of mobile management, Non-Access Stratum signaling; Shunting gateway S-GW is the accessing gateway equipment be connected with E-UTRAN, forwarding data between E-UTRAN and P-GW, and is responsible for carrying out buffer memory to pending datas such as pagings; IAD P-GW is then the borde gateway of EPS and packet data network (PacketDataNetwork, referred to as PDN) network, be responsible for PDN access and between EPS and PDN the function such as forwarding data; S-GW and P-GW belongs to core network gateway.
Base station from home is a kind of small-sized, lower powered base station, be deployed in the indoor place such as family and office, Main Function is to provide higher service rate to user and reduce the expense used required for high rate services, making up the deficiency that existing distributed cellular radio communication system covers simultaneously.The advantage of base station from home is economical, convenient, low-power output, plug and play etc.In home base station system, base station from home and/or home base-station gateway are wireless side network element, and home base-station gateway can carry out conjunction with base station from home and establish.
Fig. 2 is the schematic diagram two of existing communication system architecture, as shown in Figure 2, base station from home can be linked into core network by this logical ne of home base-station gateway, also core network (as shown in Figure 1) can be directly connected to, wherein, home base-station gateway major function is: the fail safe of checking base station from home, the registration of process base station from home, operation maintenance management is carried out to base station from home, according to Carrier Requirements configuration and control base station from home, be responsible for the data of exchcange core net and base station from home.
Except supporting the access of mobile core network, mobile communication system (comprising home base station system) also can support IP diverter function, possess IP separation capacity at wireless side network element, user contract allow IP shunting condition under, this locality access of terminal to other IP devices of home network or internet can be realized.
The realization of IP shunting in Fig. 1 and system shown in Figure 2 can provide providing powerful support for IP dividing technology by setting up shunting gateway, shunting gateway is linked into the gateway of external network (such as Internet) as this locality, address assignment is provided, charging, grouping packet filtering, policy control, data distribution function, NAS/S1-AP/RANAP (RadiosAccessNetworkApplicationPart, wireless access network applying portion)/GTP (GeneralTunnelingProtocol, universal tunnel agreement)/PMIP (ProxyMobileIP, proxy mobile IP protocol)/MIP (MobileIP, mobile IP protocol) message parse, NAT (NetworkAddressTranslation, network address translation), the functions such as IP distributing strategy route and execution.Shunting gateway can carry out conjunction with wireless side network element and establish.Shunting gateway can be ISGW (IntegratedServiceGateway, integrated service gateway), can be Home serving gateway (LocalSGW, referred to as L-SGW) and local packet data gateway (LocalPGW, referred to as L-PGW), also can be independent L-PGW, can be data distribution functional entity.
For Fig. 1 communication system, IP shunting can be set up by shutting at shunting net or not set up NAT address translation feature to realize, and is not limited by the access function that a connection realizes core net access and IP shunting simultaneously simultaneously.
When user moves to new wireless side network element, shunting gateway can carry out reorientation, and IP shunts business datum and can be undertaken shunting (as shown in Figure 3) by new shunting net pass, now shunts business and cannot ensure continuity; Also can carry out shunting (as shown in Figure 4) in the original shunting net pass of grappling, now can maintain the continuity of shunting business.
Between wireless side network element and IAD, existence shunting gateway realizes service distributing, existing mobile flow process cannot complete the handoff functionality across shunting gateway, can not ensure the continuity realizing core network data in fast mobile terminal process.
Summary of the invention
Main purpose of the present invention is to provide a kind of gateway method for relocating and source shunting gateway, at least to solve the problem.
According to an aspect of the present invention, provide a kind of gateway method for relocating, it comprises: when terminal carries out mobility event, the information updating request that source shunting gateway receiving mobility management entity sends; Described source shunting gateway creates information to target shunting gateway; Described source shunting gateway sends information updating response to described Mobility Management Entity, and wherein, described information updating response carries the information of described target shunting gateway.
Further, described mobility event comprises one of following: switch, location updating or service request.
Further, described information updating request comprises one of following: upgrade PDP Context request, bearer update request; Described establishment information comprises one of following: create PDP Context, set up carrying; Described information updating response comprises one of following: upgrade PDP Context response, bearer update response.
Further, the shunting gateway of described source shunting gateway for using before described terminal switch or before location updating, the shunting gateway of described target shunting gateway for using after described terminal switch or after location updating.
Further, when described terminal switches, if the Mobility Management Entity before and after described terminal switch changes, then the Mobility Management Entity sending described information updating request and receive described information updating response is Mobility Management Entity after described terminal switch.
Further, after the information updating request that described source shunting gateway receiving mobility management entity sends, also comprise: described source shunting gateway judges the type of the business of described terminal transmission; If the business of described transmission is the business that business continuance is low, then perform shunting gateway in described source creates step from information to target shunting gateway.
Further, after described source shunting gateway judges the type of the business transmitted, also comprise: if the business of described transmission is not the business that business continuance is low, then described source shunting gateway does not perform shunting gateway in described source creates step from information to target shunting gateway, and sends described information updating response to described Mobility Management Entity.
Further, described source shunting gateway and described target shunting gateway are one of following: ISGW; L-SGW and L-PGW; Or L-PGW.
According to a further aspect in the invention, provide a provenance shunting net and close, it comprises: receiving element, for when terminal carries out mobility event, and the information updating request that receiving mobility management entity sends; Creating unit, for creating information to target shunting gateway; Transmission unit, for creating the rear to described Mobility Management Entity transmission information updating response of described information, wherein, described information updating response is carrying the information of described target shunting gateway.
Further, the shunting gateway of described source shunting gateway for using before described terminal switch or before location updating, wherein, the shunting gateway of described target shunting gateway for using after described terminal switch or after location updating.
Further, described source shunting gateway also comprises: judging unit, for judging the type of the business of described terminal transmission after the information updating request that sends at receiving mobility management entity; Notification unit, for when judging that the business of described transmission is the low business of business continuance, notifies that described creating unit performs the step creating described information to described target shunting gateway.
In the present invention, created the information of such as PDP Context to target shunting gateway by source shunting gateway, and send to Mobility Management Entity the information updating response that such as PDP upgrades context response, thus solve the problem that existing mobile flow process cannot complete the handoff functionality across shunting gateway, achieve the locomotive function across shunting gateway, effectively to strengthen user's experience.
Accompanying drawing explanation
Accompanying drawing described herein is used to provide a further understanding of the present invention, and form a application's part, schematic description and description of the present invention, for explaining the present invention, does not form inappropriate limitation of the present invention.In the accompanying drawings:
Fig. 1 is a kind of schematic diagram connected according to the cordless communication network of correlation technique;
Fig. 2 is the another kind of schematic diagram connected according to the cordless communication network of correlation technique;
Fig. 3 is a kind of schematic diagram of the wireless communication system IP streamed data in correlation technique;
Fig. 4 is the another kind of schematic diagram of the wireless communication system IP streamed data in correlation technique;
Fig. 5 is the preferred flow chart of one of the gateway method for relocating according to the embodiment of the present invention;
Fig. 6 is the scene of the system architecture based on Fig. 1 according to the embodiment of the present invention, and when Mobility Management Entity changes, terminal carries out the flow chart of handoff procedure;
Fig. 7 is the scene of the system architecture based on Fig. 1 according to the embodiment of the present invention, and when Mobility Management Entity does not change, terminal carries out the flow chart of handoff procedure;
Fig. 8 is the scene of the system architecture based on Fig. 1 according to the embodiment of the present invention, and when Mobility Management Entity changes, terminal carries out the flow chart of handoff procedure;
Fig. 9 is the scene of the system architecture based on Fig. 1 according to the embodiment of the present invention, the flow chart of terminal position renewal process when Mobility Management Entity changes;
Figure 10 is the scene of the system architecture based on Fig. 1 according to the embodiment of the present invention, the flow chart of terminal position renewal process when Mobility Management Entity does not change;
Figure 11 is the scene of the system architecture based on Fig. 1 according to the embodiment of the present invention, carries out the flow chart of service request procedure when the terminal provided transfers connected state to by Idle state;
Figure 12 is the preferred structured flowchart of one of the source shunting gateway according to the embodiment of the present invention.
Embodiment
Below in conjunction with the drawings and specific embodiments, technical scheme of the present invention is described in further detail, can better understand the present invention to make those skilled in the art and can be implemented, but illustrated embodiment is not as a limitation of the invention.
Embodiment 1
Fig. 5 is the preferred flow chart of one of the gateway method for relocating according to the embodiment of the present invention, and it comprises the steps:
S502, when terminal carries out mobility event, the information updating request that source shunting gateway receiving mobility management entity sends;
S504, described source shunting gateway creates information to target shunting gateway;
S506, described source shunting gateway sends information updating response to described Mobility Management Entity, and wherein, described information updating response carries the information of described target shunting gateway.
In this preferred embodiment, created the information of such as PDP Context to target shunting gateway by source shunting gateway, and send to Mobility Management Entity the information updating response that such as PDP upgrades context response, thus solve the problem that existing mobile flow process cannot complete the handoff functionality across shunting gateway, the continuity of business when ensure that terminal from source shunting gateway handoff to target shunting gateway, effectively to strengthen user's experience.
Preferably, described mobility event comprises one of following: switch, location updating or service request.In this preferred embodiment, by the definition of different mobility events, add practicality of the present invention.
Preferably, described information updating request comprises one of following: upgrade PDP Context request, bearer update request; Described establishment information comprises one of following: create PDP Context, set up carrying; Described information updating response comprises one of following: upgrade PDP Context response, bearer update response.In this preferred embodiment, gateway method for relocating of the present invention can be applicable to different scenes.
Preferably, the shunting gateway of described source shunting gateway for using before described terminal switch or before location updating, the shunting gateway of described target shunting gateway for using after described terminal switch or after location updating.
Preferably, when described terminal switches, if the Mobility Management Entity before and after described terminal switch changes, then the Mobility Management Entity sending described information updating request and receive described information updating response is Mobility Management Entity after described terminal switch.In this preferred embodiment, by communicating with the Mobility Management Entity after described terminal switch, ensure that correct transmission and the continuity of the business of terminal.
Preferably, after the information updating request that described source shunting gateway receiving mobility management entity sends, also comprise: described source shunting gateway judges the type of the business of described terminal transmission; If the business of described transmission is the business that business continuance is low, then perform shunting gateway in described source creates step from information to target shunting gateway.In this preferred embodiment, perform the step of shunting gateway in described source to target shunting gateway establishment information by the business low to business continuance, the continuity of the business that this business continuance is low can be ensured better.
Preferably, after described source shunting gateway judges the type of the business transmitted, also comprise: if the business of described transmission is not the business that business continuance is low, then described source shunting gateway does not perform shunting gateway in described source creates step from information to target shunting gateway, and sends information updating response to described Mobility Management Entity.In this preferred embodiment, by not to type for the low business of business continuance performs shunting gateway in described source to create step from information to target shunting gateway, the continuity of the business that this business continuance is low can be ensured better.
Preferably, described source shunting gateway and described target shunting gateway are one of following: ISGW, L-SGW and L-PGW or, L-PGW.Preferably, described source shunting gateway and described target shunting gateway are ISGW, or, be respectively L-SGW and L-PGW, or be L-PGW.By the present embodiment, add applicability of the present invention.
Following examples set forth based on UTRAN (UniversalTerrestrialRadioAccessNetwork, universal mobile telecommunications system land radio access web) systematic difference scene.
Embodiment 2
Fig. 6 is the scene based on Fig. 1 system architecture, and when Mobility Management Entity changes, terminal carries out the flow chart of handoff procedure.Concrete steps are described below:
Step 602, wireless side network element judges to need to initiate to switch.
Step 603, source wireless side network element sends re-positioning request to source Mobility Management Entity.
Step 604, source Mobility Management Entity sends reorientation forwarding request message to target mobility management entity.
Step 605, target mobility management entity request target wireless side network element carries out reorientation.
Step 606, Target Wireless side network element responds relocation response message to target mobility management entity.
Step 607, target mobility management entity sends reorientation forward response message to source Mobility Management Entity.
Step 608, source Mobility Management Entity sends reorientation order to source wireless side network element.
Step 609, source wireless side network element sends execution message of repositioning to Target Wireless side network element.
Step 610, after receiving reorientation and performing, Target Wireless side network element is initiated reorientation to target mobility management entity and is detected.
Step 611, Target Wireless side network element sends RAN Mobility Information to terminal; After terminal reconfigures, reply acknowledge message to Target Wireless side network element.
Step 612, Target Wireless side network element sends reorientation completion notice message to target mobility management entity.
Step 613, between source Mobility Management Entity and target mobility management entity, mutual reorientation forward completes message.
Step 614, target mobility management entity sends PDP Context update request message to source shunting gateway.
Step 615, source shunting gateway select target shunting gateway, its selection mode can be: selected by terminal positional information.
Step 616, shunting gateway in source sends PDP Context request to create to target shunting gateway, carries accessing gateway information.
Step 617, target shunting gateway sends PDP Context update request to IAD.
Step 618, IAD is replied PDP Context and is upgraded response.
Step 619, target shunting gateway is replied PDP Context to source shunting gateway and is set up response.
Step 620, shunting gateway in source is initiated PDP Context to target mobility management entity and is upgraded response, carries target shunting gateway information.
Step 621, target mobility management entity can upgrade the local shunting gateway information preserved, and upgrades radio bearer to Target Wireless side network element, carries target shunting gateway information.
Embodiment 3
Fig. 7 is the scene based on Fig. 1 system architecture, and when Mobility Management Entity does not change, terminal carries out the flow chart of handoff procedure.Concrete steps are described below:
Step 6a02, wireless side network element judges to need to initiate to switch.
Step 6a03, source wireless side network element sends re-positioning request to Mobility Management Entity.
Step 6a04, Mobility Management Entity request target wireless side network element carries out reorientation.
Step 6a05, Target Wireless side network element responds relocation response message to Mobility Management Entity.
Step 6a06, Mobility Management Entity sends reorientation order to source wireless side network element.
Step 6a07, source wireless side network element sends execution message of repositioning to Target Wireless side network element.
Step 6a08, after receiving reorientation and performing, Target Wireless side network element is initiated reorientation to target mobility management entity and is detected.
Step 6a09, Target Wireless side network element sends RAN Mobility Information to terminal; After terminal reconfigures, reply acknowledge message to Target Wireless side network element.
Step 6a10, Target Wireless side network element sends reorientation completion notice message to Mobility Management Entity.
Step 6a11, Mobility Management Entity sends PDP Context update request message to source shunting gateway.
Step 6a12, source shunting gateway select target shunting gateway, its selection mode can be: selected by terminal positional information.
Step 6a13, shunting gateway in source sends PDP Context request to create to target shunting gateway, carries accessing gateway information.
Step 6a14, target shunting gateway sends PDP Context update request to IAD.
Step 6a15, IAD is replied PDP Context and is upgraded response.
Step 6a16, target shunting gateway is replied PDP Context to source shunting gateway and is set up response.
Step 6a17, shunting gateway in source is initiated PDP Context to Mobility Management Entity and is upgraded response, carries target shunting gateway information.
Step 6a18, Mobility Management Entity can upgrade the local shunting gateway information preserved, and upgrades radio bearer to Target Wireless side network element, carries target shunting gateway information.
Embodiment 4
Fig. 8 is the scene based on Fig. 1 system architecture, and when Mobility Management Entity changes, terminal carries out the flow chart of handoff procedure.In this flow process, closed by source shunting net and carry out switching mode selection.Concrete steps are described below:
Step 702, wireless side network element judges to need to initiate to switch.
Step 703, source wireless side network element sends re-positioning request to source Mobility Management Entity.
Step 704, source Mobility Management Entity sends reorientation forwarding request message to target mobility management entity.
Step 705, target mobility management entity request target wireless side network element carries out reorientation.
Step 706, Target Wireless side network element responds relocation response message to target mobility management entity.
Step 707, target mobility management entity sends reorientation forward response message to source Mobility Management Entity.
Step 708, source Mobility Management Entity sends reorientation order to source wireless side network element.
Step 709, source wireless side network element sends execution message of repositioning to Target Wireless side network element.
Step 710, after receiving reorientation and performing, Target Wireless side network element is initiated reorientation to target mobility management entity and is detected.
Step 711, Target Wireless side network element sends RAN Mobility Information to terminal; After terminal reconfigures, reply acknowledge message to Target Wireless side network element.
Step 712, Target Wireless side network element sends reorientation completion notice message to target mobility management entity.
Step 713, between source Mobility Management Entity and target mobility management entity, mutual reorientation forward completes message.
Step 714, target mobility management entity sends PDP Context update request message to source shunting gateway.
Step 715, source shunting gateway determines switching mode according to type of service, as business continuance requires low business, then adopts Fig. 6 switching mode, performs step 615 to step 621; Otherwise, perform following steps 716.
Step 716, shunting gateway in source is initiated PDP Context to target mobility management entity and is upgraded response.
Embodiment 5
Fig. 9 is the scene according to the present invention is based on Fig. 1 system architecture, the flow chart of terminal position renewal process when Mobility Management Entity changes.Concrete steps are described below:
Step 801, terminal sends Routing Area Update request message through Target Wireless side network element to target mobility management entity.
Step 802, target mobility management entity sends context request message to source Mobility Management Entity.
Step 803, source Mobility Management Entity sends context acknowledge message to target mobility management entity.
Step 804, target mobility management entity sends context Accept message to source Mobility Management Entity.
Step 805, target mobility management entity initiates PDP Context update request to source shunting gateway.
Step 806, source shunting gateway select target shunting gateway, its selection mode can be: selected by terminal positional information.
Step 807, shunting gateway in source sends PDP Context request to create to target shunting gateway, carries accessing gateway information.
Step 808, target shunting gateway sends PDP Context update request to IAD.
Step 809, IAD is replied PDP Context and is upgraded response.
Step 810, target shunting gateway is replied PDP Context to source shunting gateway and is set up response.
Step 811, shunting gateway in source is initiated PDP Context to target mobility management entity and is upgraded response, carries target shunting gateway information.
Step 812, target mobility management entity and Authentication Authorization database executing location upgrade, contracting obtains; Source Mobility Management Entity and Authentication Authorization database executing location cancel process.
Step 813, target mobility management entity accepts message through Target Wireless side network element to terminal initiating updating of tracking area.
Step 814, terminal replies tracing section updating completes message.
Embodiment 6
Figure 10 is the scene according to the present invention is based on Fig. 1 system architecture, the flow chart of terminal position renewal process when Mobility Management Entity does not change.Concrete steps are described below:
Step 8a01, terminal sends Routing Area Update request message through Target Wireless side network element to Mobility Management Entity.
Step 8a02, target mobility management entity initiates PDP Context update request to source shunting gateway.
Step 8a03, source shunting gateway select target shunting gateway, its selection mode can be: selected by terminal positional information.
Step 8a04, shunting gateway in source sends PDP Context request to create to target shunting gateway, carries accessing gateway information.
Step 8a05, target shunting gateway sends PDP Context update request to IAD.
Step 8a06, IAD is replied PDP Context and is upgraded response.
Step 8a07, target shunting gateway is replied PDP Context to source shunting gateway and is set up response.
Step 8a08, shunting gateway in source is initiated PDP Context to target mobility management entity and is upgraded response, carries target shunting gateway information.
Step 8a09, Mobility Management Entity accepts message through Target Wireless side network element to terminal initiating updating of tracking area.
Step 8a10, terminal replies tracing section updating completes message.
Embodiment 7
Figure 11 shows the present invention on the basis of Fig. 1 system architecture, carries out the flow chart of service request procedure when the terminal provided transfers connected state to by Idle state.Concrete steps are described below:
Step 901, terminal sends the request of RRC connection establishment to wireless side network element.
Step 902, wireless side network element carries out RRC connection establishment.
Step 903, terminal sends service request information through wireless side network element to Mobility Management Entity.
Step 904, Mobility Management Entity sends radio bearer assignment request to wireless side network element, and Mobility Management Entity, wireless side network element and terminal perform radio bearer and assign and process of establishing.
Step 905, Mobility Management Entity sends PDP Context update request message to source shunting gateway.
Step 906, source shunting gateway select target shunting gateway, its selection mode can be: selected by terminal positional information.
Step 907, shunting gateway in source sends PDP Context request to create to target shunting gateway, carries accessing gateway information.
Step 908, target shunting gateway sends PDP Context update request to IAD.
Step 909, IAD is replied PDP Context and is upgraded response.
Step 910, target shunting gateway is replied PDP Context to source shunting gateway and is set up response.
Step 911, shunting gateway in source is initiated PDP Context to Mobility Management Entity and is upgraded response, carries target shunting gateway information.
Step 912, Mobility Management Entity can upgrade the local shunting gateway information preserved, and upgrades radio bearer to wireless side network element, carries target shunting gateway information.
Embodiment 8
Figure 12 is the preferred structured flowchart of one of the source shunting gateway according to the embodiment of the present invention, and it comprises: receiving element 1202, for when terminal carries out mobility event, and the information updating request that receiving mobility management entity sends; Creating unit 1204, for creating information to target shunting gateway; Transmission unit 1206, for creating the rear to described Mobility Management Entity transmission information updating response of described information, wherein, described information updating response is carrying the information of described target shunting gateway.
In this preferred embodiment, created the information of such as PDP Context to target shunting gateway by source shunting gateway, and send to Mobility Management Entity the information updating response that such as PDP upgrades context response, thus solve the problem that existing mobile flow process cannot complete the handoff functionality across shunting gateway, the continuity of business when ensure that terminal from source shunting gateway handoff to target shunting gateway, effectively to strengthen user's experience.
Preferably, described mobility event comprises one of following: switch, location updating or service request.In this preferred embodiment, by the definition of different mobility events, add practicality of the present invention.
Preferably, described information updating request comprises one of following: upgrade PDP Context request, bearer update request; Described establishment information comprises one of following: create PDP Context, set up carrying; Described information updating response comprises one of following: upgrade PDP Context response, bearer update response.In this preferred embodiment, gateway method for relocating of the present invention can be applicable to different scenes.
Preferably, the shunting gateway of described source shunting gateway for using before described terminal switch or before location updating, wherein, the shunting gateway of described target shunting gateway for using after described terminal switch or after location updating.
Preferably, when described terminal switches, if the Mobility Management Entity before and after described terminal switch changes, then the Mobility Management Entity sending described information updating request and receive described information updating response is Mobility Management Entity after described terminal switch.In this preferred embodiment, by communicating with the Mobility Management Entity after described terminal switch, ensure that correct transmission and the continuity of the business of terminal.
Preferably, described source shunting gateway also comprises: judging unit 1208, for after the information updating request that receiving mobility management entity sends, judges the type of the business of described terminal transmission; Notification unit 1210, for when judging that the business of described transmission is the low business of business continuance, notifies that described creating unit 1204 performs the step creating information to described target shunting gateway.In this preferred embodiment, perform the step of shunting gateway in described source to target shunting gateway establishment information by the business low to business continuance, the continuity of the business that this business continuance is low can be ensured better.
Preferably, after described source shunting gateway judges the type of the business transmitted, if judging unit 1208 judges that the business of described transmission is not the business that business continuance is low, then notification unit 1210 notifies that described creating unit 1204 does not perform shunting gateway in described source creates step from information to target shunting gateway, and sends information updating response to described Mobility Management Entity.In this preferred embodiment, by not to type for the low business of business continuance performs shunting gateway in described source to create step from information to target shunting gateway, the continuity of the business that this business continuance is low can be ensured better.
Preferably, described source shunting gateway and described target shunting gateway are one of following: 1) ISGW; 2) L-SGW and L-PGW; Or 3) L-PGW.Preferably, described source shunting gateway and described target shunting gateway are ISGW, or, be respectively L-SGW and L-PGW, or be L-PGW.By the present embodiment, add applicability of the present invention.
In various embodiments of the present invention, shunting gateway information can a kind of information or multiple below: shunting gateway identification, shunting gateway address.
In order to simplified characterization, for the situation of Fig. 1, above embodiment only illustrates that there is gateway in IP shunting connection communication system carries out the mode of reorientation.When Fig. 2 system, no matter be E-UTRAN or UTRAN system, the request of renewal PDP Context can be replaced with bearer update request, establishment PDP Context replaced with foundation carrying, the response of renewal PDP Context is replaced with bearer update response, the flow process of shunting net pass being carried out to reorientation is similar to the aforementioned embodiment, can not impact elaboration the present invention, therefore repeat no more.
When terminal carries out mobility event, the information updating request that source shunting gateway receiving mobility management entity sends; Described source shunting gateway creates information to target shunting gateway; Described source shunting gateway sends information updating response to described Mobility Management Entity, and wherein, described renewal PDP Context response carries the information of described target shunting gateway.Wherein, information updating request comprises one of following: upgrade PDP Context request, bearer update request.Establishment information comprises one of following: create PDP Context, set up carrying.Information updating response comprises one of following: upgrade PDP Context response, bearer update response.
In above all embodiments, shunting gateway can be ISGW, can be L-SGW and L-PGW, and can be independent L-PGW, can be L-GGSN and L-SGSN, can be independent L-GGSN, can be data distribution functional entity.Shunting gateway comprises shunting IAD and/or shunting gateway; Described shunting IAD is L-PGW or L-GGSN; Described shunting gateway is L-SGW or L-SGSN.
Wireless side network element can be base station, base station from home, RNC, shunting gateway, diverter function entity, home base-station gateway.Mobility Management Entity can be MME, MSC, SGSN, home base-station gateway.
IAD can be core net IAD, can be shunting IAD; Gateway can be Core Network Service gateway, can be shunting gateway.
Core net IAD is P-GW or GGSN; Core Network Service gateway is S-GW or SGSN.
IP shunting can be local IP access user local network, local IP access company local network, local IP access the Internet, the triage operator of Internet service, specific IP data distribution.
The information of shunting gateway can be that FQDN is or/and IP address.
Obviously, those skilled in the art should be understood that, above-mentioned of the present invention each module or each step can realize with general calculation element, they can concentrate on single calculation element, or be distributed on network that multiple calculation element forms, alternatively, they can realize with the executable program code of calculation element, thus, they can be stored and be performed by calculation element in the storage device, and in some cases, step shown or described by can performing with the order be different from herein, or they are made into each integrated circuit modules respectively, or the multiple module in them or step are made into single integrated circuit module to realize.Like this, the present invention is not restricted to any specific hardware and software combination.
The foregoing is only the preferred embodiments of the present invention, be not limited to the present invention, for a person skilled in the art, the present invention can have various modifications and variations.Within the spirit and principles in the present invention all, any amendment done, equivalent replacement, improvement etc., all should be included within protection scope of the present invention.

Claims (8)

1. a gateway method for relocating, is characterized in that, comprising:
When terminal carries out mobility event, the information updating request that source shunting gateway receiving mobility management entity sends, wherein, described information updating request at least comprises: upgrade PDP Context request;
Described source shunting gateway by terminal positional information select target shunting gateway, and creates information to described target shunting gateway, and wherein, described establishment information at least comprises: PDP Context information;
Described source shunting gateway sends information updating response to described Mobility Management Entity, and wherein, described information updating response carries the information of described target shunting gateway, and wherein, described information updating response at least comprises: upgrade PDP Context response;
Wherein, after the information updating request that described source shunting gateway receiving mobility management entity sends, also comprise: described source shunting gateway judges the type of the business of described terminal transmission; If the business of described transmission is the business that business continuance is low, then perform shunting gateway in described source creates step from information to target shunting gateway; If the business of described transmission is not the business that business continuance is low, then described source shunting gateway does not perform shunting gateway in described source creates step from information to target shunting gateway, and sends described information updating response to described Mobility Management Entity.
2. method according to claim 1, is characterized in that, described mobility event comprises one of following: switch, location updating or service request.
3. method according to claim 1, is characterized in that, described information updating request also comprises: bearer update request; Described establishment information also comprises: set up carrying; Described information updating response also comprises: bearer update responds.
4. method according to claim 1, is characterized in that, the shunting gateway of described source shunting gateway for using before described terminal switch or before location updating, the shunting gateway of described target shunting gateway for using after described terminal switch or after location updating.
5. method according to claim 4, it is characterized in that, when described terminal switches, if the Mobility Management Entity before and after described terminal switch changes, then the Mobility Management Entity sending described information updating request and receive described information updating response is Mobility Management Entity after described terminal switch.
6. method according to claim 1, is characterized in that, described source shunting gateway and described target shunting gateway are one of following: ISGW; L-SGW and L-PGW; Or L-PGW.
7. a provenance shunting net closes, and it is characterized in that, comprising:
Receiving element, for when terminal carries out mobility event, the information updating request that receiving mobility management entity sends, wherein, described information updating request at least comprises: upgrade PDP Context request;
Creating unit, for shunting gateway by terminal positional information select target, and create information to described target shunting gateway, wherein, described establishment information at least comprises: PDP Context information;
Transmission unit, for creating the rear to described Mobility Management Entity transmission information updating response of described information, wherein, described information updating response is carrying the information of described target shunting gateway, wherein, described information updating response at least comprises: upgrade PDP Context response;
Wherein, described source shunting gateway also comprises: judging unit, for judging the type of the business of described terminal transmission after the information updating request that sends at receiving mobility management entity; Notification unit, for when judging that the business of described transmission is the low business of business continuance, notifies that described creating unit performs the step creating described information to described target shunting gateway.
8. shunting gateway in source according to claim 7, it is characterized in that, the shunting gateway of described source shunting gateway for using before described terminal switch or before location updating, wherein, the shunting gateway of described target shunting gateway for using after described terminal switch or after location updating.
CN201010560767.1A 2010-11-25 2010-11-25 Gateway method for relocating and source shunting gateway Active CN102480782B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201010560767.1A CN102480782B (en) 2010-11-25 2010-11-25 Gateway method for relocating and source shunting gateway
PCT/CN2011/081151 WO2012068935A1 (en) 2010-11-25 2011-10-21 Gateway relocation method and source shunt gateway

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201010560767.1A CN102480782B (en) 2010-11-25 2010-11-25 Gateway method for relocating and source shunting gateway

Publications (2)

Publication Number Publication Date
CN102480782A CN102480782A (en) 2012-05-30
CN102480782B true CN102480782B (en) 2016-03-30

Family

ID=46093222

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201010560767.1A Active CN102480782B (en) 2010-11-25 2010-11-25 Gateway method for relocating and source shunting gateway

Country Status (2)

Country Link
CN (1) CN102480782B (en)
WO (1) WO2012068935A1 (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105813111B (en) * 2014-12-31 2021-01-26 中兴通讯股份有限公司 Service flow transmission path optimization method and device and MME
CN108377459B (en) 2016-10-11 2020-09-01 中国移动通信有限公司研究院 Connection management method and device
WO2024031341A1 (en) * 2022-08-09 2024-02-15 Nokia Shanghai Bell Co., Ltd. Mobility between gateway devices in non-3gpp access

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101072425A (en) * 2006-05-11 2007-11-14 华为技术有限公司 Wireless evolution network switching method and system
CN101505510A (en) * 2008-02-04 2009-08-12 华为技术有限公司 Method for handover between macro cell and private cell, macro network system
CN101720119A (en) * 2009-05-27 2010-06-02 中兴通讯股份有限公司 Method and system for realizing PDN connecting selection

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101361386B (en) * 2005-12-22 2011-07-06 中兴通讯股份有限公司 Method making packet data stream uninterrupted when mobile terminal moving across wireless access networks
EP1890455A1 (en) * 2006-08-18 2008-02-20 Nokia Siemens Networks Gmbh & Co. Kg Method and apparatus for handover to a WLAN connection involving a trigger for mobility at Packet Data Gateway (PDG)

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101072425A (en) * 2006-05-11 2007-11-14 华为技术有限公司 Wireless evolution network switching method and system
CN101505510A (en) * 2008-02-04 2009-08-12 华为技术有限公司 Method for handover between macro cell and private cell, macro network system
CN101720119A (en) * 2009-05-27 2010-06-02 中兴通讯股份有限公司 Method and system for realizing PDN connecting selection

Also Published As

Publication number Publication date
CN102480782A (en) 2012-05-30
WO2012068935A1 (en) 2012-05-31

Similar Documents

Publication Publication Date Title
CN102026145B (en) Local IP access method and system
CN102149071B (en) Method for controlling establishment of local IP (internet protocol) connection
CN101790150B (en) Method and device for updating contract allocation of access point name
CN101568149B (en) Method and system for preferably selecting service gateway
CN105554789A (en) Communication system, method, and apparatus
CN101990192A (en) Notification method and device for local IP access connection property
CN102868999A (en) Method and system for establishing packet data network connection
CN102256329B (en) A kind of method and apparatus realizing Route Selection
CN101330751B (en) The method of releasing source network resource, gateway entity and the network equipment
CN102469619A (en) Mobile communication system and method for relocation of service gateway thereof
KR20120052223A (en) Message-sending method and serving gprs support node
EP2571302A1 (en) Method, apparatus and system for processing local address in shunt connection
CN102480528B (en) IAD system of selection and device
CN102480782B (en) Gateway method for relocating and source shunting gateway
CN102256326B (en) A kind of method and apparatus realizing Route Selection
CN102438328B (en) A kind of user participates in the method and system of local IP access connection establishment
CN102056137B (en) Method and system for acquiring local gateway selection information
CN102378359B (en) A kind of network element information acquisition method and system
CN102238633B (en) A kind of dynamic control method of data distribution and system
CN101610462A (en) A kind of data message sending method, device and communication system
CN103155683B (en) Realize mobility method and the equipment of LIPA or SIPTO
CN102149067B (en) Method for managing local IP data and mobile communication system
CN103813397A (en) Management shunting connection method, wireless-side network element and mobile management entity
CN102300194B (en) A kind of method and device, system transmitting diffluent information
CN101420679A (en) Signing data distributing method and apparatus

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant
TR01 Transfer of patent right
TR01 Transfer of patent right

Effective date of registration: 20201216

Address after: 215163 8 Jinfeng Road, science and Technology City, Suzhou high tech Zone, Jiangsu

Patentee after: Suzhou Medical Device Industry Development Co.,Ltd.

Address before: 518057 No. 55 South Science and technology road, Shenzhen, Guangdong, Nanshan District

Patentee before: ZTE Corp.

CP01 Change in the name or title of a patent holder
CP01 Change in the name or title of a patent holder

Address after: 215163 8 Jinfeng Road, science and Technology City, Suzhou high tech Zone, Jiangsu

Patentee after: Suzhou Medical Device Industry Development Group Co.,Ltd.

Address before: 215163 8 Jinfeng Road, science and Technology City, Suzhou high tech Zone, Jiangsu

Patentee before: Suzhou Medical Device Industry Development Co.,Ltd.