[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

US20120147853A1 - Communication system and communication controlling method - Google Patents

Communication system and communication controlling method Download PDF

Info

Publication number
US20120147853A1
US20120147853A1 US13/398,002 US201213398002A US2012147853A1 US 20120147853 A1 US20120147853 A1 US 20120147853A1 US 201213398002 A US201213398002 A US 201213398002A US 2012147853 A1 US2012147853 A1 US 2012147853A1
Authority
US
United States
Prior art keywords
mme
user equipment
pgw
base station
gateway apparatus
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.)
Abandoned
Application number
US13/398,002
Inventor
Hajime Zembutsu
Toshiyuki Tamura
Stefan Schmid
Tarik TALEB
Gottfried Punz
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.)
NEC Europe Ltd
NEC Corp
Original Assignee
NEC Europe Ltd
NEC 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 NEC Europe Ltd, NEC Corp filed Critical NEC Europe Ltd
Priority to US13/398,002 priority Critical patent/US20120147853A1/en
Publication of US20120147853A1 publication Critical patent/US20120147853A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/12Reselecting a serving backbone network switching or routing node
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0011Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0055Transmission or use of information for re-establishing the radio link
    • H04W36/0061Transmission or use of information for re-establishing the radio link of neighbour cell information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/24Reselection being triggered by specific parameters
    • H04W36/32Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
    • H04W36/326Reselection being triggered by specific parameters by location or mobility data, e.g. speed data by proximity to another entity
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W40/00Communication routing or communication path finding
    • H04W40/34Modification of an existing route
    • H04W40/36Modification of an existing route due to handover
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/20Manipulation of established connections
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/20Manipulation of established connections
    • H04W76/22Manipulation of transport tunnels

Definitions

  • This invention relates to a mobile communication system and, more particularly, to a system optimal for re-selection of a gateway that connects a terminal to a packet data network. This invention also relates to a communication controlling method.
  • EPC Evolved Packet Core
  • bearer management is performed based on an ‘Always On’ concept in such a manner that a PGW (PDN (Packet Data Network) Gateway), initially selected when a UE (User Equipment or ‘terminal’) has attached the EPC, is fixedly used as anchor until the UE detaches.
  • PGW Packet Data Network
  • UE User Equipment or ‘terminal’
  • a service network a packet data network
  • an SGW Serving Gateway
  • a bearer between the SGW and the PGW is updated by disconnection and re-establishment to ensure connectivity from the UE to the PGW.
  • such a PGW is selected which is close to the SGW physically or from the perspective of network topology.
  • the PGW may be far away from a SGW in terms of a distance(a physical or network topological distance).
  • network efficiency is deteriorated to present problems such as transmission delay of user data or inefficient consumption of network resources within the EPC.
  • Such a system is thus desired that, when a UE moves over a long distance, and the UE is to connect from a serving area in which the UE resides to an external network (service network), allows re-selecting an optimal PGW (result of analysis by the present inventors).
  • a communication method in Local IP Access (LIPA)/Selected IP Traffic Offload (SIPTO) architecture wherein a gateway apparatus physically or topologically close to a site, where the user equipment is attached, is selected according to movement of the user equipment.
  • LIPA Local IP Access
  • SIPTO Select IP Traffic Offload
  • a communication system in Local IP Access (LIPA)/Selected IP Traffic Offload (SIPTO) architecture wherein a gateway apparatus physically or topologically close to a site, where the user equipment is attached, is selected, according to movement of the user equipment.
  • LIPA Local IP Access
  • SIPTO Select IP Traffic Offload
  • LIPA Local IP Access
  • SIPTO Select IP Traffic Offload
  • a communication method in Local IP Access (LIPA)/Selected IP Traffic Offload (SIPTO) architecture wherein, in case a Serving General Packet Radio Service Support Node (SGSN) decides that it is necessary to re-select a gateway apparatus, the SGSN sends a first signal for setting re-attachment to a user equipment, the user equipment on receipt of the first signal transmitting a second signal for re-attachment to the SGSN and the SGSN re-selecting the gateway apparatus.
  • LIPA Local IP Access
  • SIPTO Select IP Traffic Offload
  • a communication system in Local IP Access (LIPA)/Selected IP Traffic Offload (SIPTO) architecture comprising a Serving General Packet Radio Service Support Node (SGSN) and a user equipment, wherein the SGSN sends a first signal for setting re-attachment, when the SGSN decides that it is necessary to re-select a gateway apparatus, the user equipment transmits a second signal for re-attachment to the SGSN, on receipt of the first signal, and the SGSN re-selects the gateway apparatus.
  • LIPA Local IP Access
  • SIPTO Select IP Traffic Offload
  • a user equipment in a communication system by Local IP Access (LIPA)/Selected IP Traffic Offload (SIPTO) architecture wherein the user equipment receives a first signal that sets re-attachment from a Serving General Packet Radio Service Support Node (SGSN) and transmits a second signal for re-attachment to the SGSN to cause re-selection of a gateway apparatus to be performed.
  • LIPA Local IP Access
  • SIPTO Select IP Traffic Offload
  • a communication method in Local IP Access (LIPA)/Selected IP Traffic Offload (SIPTO) architecture comprises: the MME sending a deactivate bearer request (Deactivate Bearer request), requesting re-selection, to a base station, when a mobility management entity (MME) decides that it is necessary to re-select a gateway apparatus;
  • LIPA Local IP Access
  • SIPTO Select IP Traffic Offload
  • RRC connection reconfiguration RRC connection reconfiguration
  • RRC connection reconfiguration RRC connection reconfiguration
  • a communication system in Local IP Access (LIPA)/Selected IP Traffic Offload (SIPTO) architecture comprising:
  • MME mobility management entity
  • the MME decides that it is necessary to re-select a gateway apparatus, the MME sends a deactivate bearer request (Deactivate Bearer request), requesting re-selection, to the base station,
  • a deactivate bearer request (Deactivate Bearer request)
  • the base station sends an RRC connection reconfiguration (RRC connection reconfiguration) to the user equipment,
  • the user equipment sends a notification of completion of the RRC connection reconfiguration (RRC connection reconfiguration) to the base station,
  • the base station sends a deactivate bearer response (Deactivate Bearer response) to the MME,
  • the user equipment initiates a UE requested PDN connectivity (UE requested PDN connectivity) procedure to cause re-selection of a gateway apparatus to be performed.
  • UE requested PDN connectivity UE requested PDN connectivity
  • a user equipment in a communication system by Local IP Access (LIPA)/Selected IP Traffic Offload (SIPTO) architecture, wherein, in case of receiving an RRC connection reconfiguration from the base station, the user equipment sends a notification of completion of RRC connection reconfiguration to the base station to initiate a UE requested PDN connectivity procedure to cause re-selection of a gateway apparatus to be performed.
  • LIPA Local IP Access
  • SIPTO Select IP Traffic Offload
  • an optimal gateway node it is possible to re-select an optimal gateway node at a time when a user equipment is to connect from a serving area to an external network (service network).
  • FIG. 1 is a diagram showing a entire configuration of a system according to an exemplary embodiment of the present invention.
  • FIG. 2 is a diagram for explaining a Comparative Example.
  • FIG. 3 is a diagram for explaining the present invention.
  • FIG. 4 is a diagram illustrating a sequence of the Comparative Example.
  • FIG. 5 is a diagram illustrating a sequence of an exemplary embodiment 1 of the present invention.
  • FIG. 6 is a diagram illustrating a sequence of an exemplary embodiment 2 of the present invention.
  • FIG. 7 is a diagram illustrating a sequence of an exemplary embodiment 3 of the present invention.
  • FIG. 8 is a diagram illustrating a sequence of an exemplary embodiment 4 of the present invention.
  • FIG. 9 is a diagram showing a configuration of an exemplary embodiment 5 of the present invention.
  • FIG. 10 is a diagram showing a configuration of an exemplary embodiment 6 of the present invention.
  • FIG. 11 is a diagram illustrating a sequence of the exemplary embodiment 5 of the present invention.
  • FIG. 12 is a diagram illustrating a sequence of the exemplary embodiment 6 of the present invention.
  • FIG. 13 is a diagram illustrating a sequence of an exemplary embodiment 7 of the present invention.
  • FIG. 14 is a diagram illustrating a sequence of an exemplary embodiment 8 of the present invention.
  • a system re-selects a PGW (PDN gateway) in EPC in keeping with movement of a user equipment (UE) and re-establishes a default bearer, thereby realizing improvement of transmission delay and efficiency of network resources in the EPC.
  • PGW PDN gateway
  • LIPA Local IP Access
  • SIPTO Select IP Traffic Offload
  • a PGW is re-selected for a UE which is being attached to the EPC.
  • An EPC bearer usually uses in a fixed manner, a PGW which is initially selected when a UE is attached (registered) to the EPC network, as an anchor, until the UE is detached (deleted from registration). However, in case the UE moves over a long distance, it may occur frequently that the PGW initially selected ceases to be a most efficient gateway apparatus for the external network.
  • a path (bearer) between a UE and a PGW may be optimized by re-selecting and modifying the PGW, such as when the UE is in an idle state.
  • a default bearer is re-established, with the re-selection of as the PGW, when the UE is not involved in packet communication, i.e., when the UE is in idle mode.
  • FIG. 2 shows, as Comparative Example, a case where the present invention is not applied.
  • a PGW 71 which is closer to the left side SGW 61 in a physical distance or a network-topological distance, is initially selected, and a connection path 1 is set.
  • the UE is moved a long distance, the UE continues to use the left-side PGW 71 .
  • the UE and the PGW are connected by an inefficient connection path 2 .
  • FIG. 3 shows a case where the UE moves astride the SGW, as the present invention is applied.
  • the PGW 71 since the UE is attached to the SGW 61 on the left side of FIG. 3 , the PGW 71 , closer to the left side SGW 61 in a physical distance or a network-topological distance, is initially selected, and a connection path 3 is set.
  • the EPC then re-examines the connectivity between the UE and the external network (service network), using the UE's movement over the large distance as a trigger.
  • the EPC gives a decision that a right-side PGW 2 provides a more efficient connection (UE-PGW path) than the left-side PGW 71 .
  • UE-PGW path a more efficient connection
  • the path between the UE and the PGW is changed over from the connection path 3 to the connection path 4 , thus assuring more efficient connection.
  • FIG. 1 shows the arrangement of a network system according of the present exemplary embodiment.
  • the basic arrangement itself of the network remains unchanged from a hitherto-used EPC network arrangement.
  • UE 1 to UE 3 are mobile phones.
  • eNodeB evolved Node B
  • NodeB 21 and RNC Radio Network Controller
  • UMTS Universal Mobile Telecommunication System
  • An MME (Mobility Management Entity) 41 is an apparatus for mobility management as introduced by EPC.
  • An SGSN (Serving GPRS (General Packet Radio Service) Support Node) 51 is a serving apparatus, used for UMTS, and may or may not handle a user plane processing, depending on a connection modes.
  • the user plane is set between the SGW (Serving Gateway) and the RNC.
  • SGW Serving Gateway
  • SGWs 61 and 62 are serving apparatuses that may handle the user plane.
  • PGW 71 and 72 are gateway apparatuses that connect an external network (a service network 81 in the drawing) and RNC.
  • FIG. 4 shows a case of TA update accompanied by SGW change (Comparative Example). It is noted that, when a UE is in idle condition, that is, in a no-connection state, it is managed to which tracking area (position registration area) the UE belongs, however, it is not managed in which cell the UE resides.
  • MME receives a TA update request (TA Update Request) from the UE and, if it is determined that SGW needs to be changed, a create session request (Create Session Request) is sent to an SGW ( 2 ) which is a change-target SGW.
  • TA Update Request a TA update request
  • Create Session Request a create session request
  • the SGW( 2 ) sends a modify bearer request (Modify Bearer Request) to the PGW ( 1 ) to notify the PGW ( 1 ) of the fact that the SGW as destination of connection is changed.
  • a modify bearer request Modify Bearer Request
  • the PGW ( 1 ) On completion of update of the bearer context information, the PGW ( 1 ) sends a response to the modify bearer request (Modify Bearer Response) to the SGW ( 2 ).
  • the SGW ( 2 ) On receipt of the response to the modify bearer request (Modify Bearer Response) from the PGW ( 1 ), the SGW ( 2 ) sends a create session response (Create Session Response) to the MME.
  • Modify Bearer Response Modify Bearer Response
  • the SGW ( 2 ) On receipt of the response to the modify bearer request (Modify Bearer Response) from the PGW ( 1 ), the SGW ( 2 ) sends a create session response (Create Session Response) to the MME.
  • the MME On receipt of the create session response (normal response) from the SGW ( 2 ), the MME sends a delete session request (Delete Session Request) to the SGW ( 1 ), which is a change-source SGW.
  • Delete Session Request a delete session request
  • the SGW ( 1 ) After deletion of the bearer context, the SGW ( 1 ) sends a delete session response (Delete Session Response) to the MME.
  • a delete session response (Delete Session Response)
  • the MME On receipt of the delete session response (Delete Session Response) from the SGW ( 1 ), the MME sends a TA (Tracking Access) accept (TA accept) to the UE.
  • TA Track Access
  • the MME receives a TA update request (TA Update Request) from the UE.
  • TA Update Request TA Update Request
  • the MME sends a create session request (Create Session Request) to the SWG ( 2 ) which is a change-target SGW.
  • the MME selects a PGW ( 2 ) that can be efficiently connected to the external network (service network), and sets address information that identifies the PGW, in the create session request (Create Session Request).
  • the SGW ( 2 ) on receipt of the new PGW address, sends a create session request (Create Session Request) to the PGW ( 2 ).
  • the PGW ( 2 ) responsive to the create session request (Create Session Request) sent from the SGW ( 2 ), creates a bearer context.
  • the PGW ( 2 ) also assigns a new IP address for the user to the UE. After completion of assignment of the new IP address for the user and creation of the bearer context, the PGW ( 2 ) sends a create session response (Create Session Response) to the SGW ( 2 ).
  • the SGW ( 2 ) responsive to the create session response (Create Session Request) from the PGW ( 2 ), sends a delete session request (Delete Session Request) to the PGW ( 1 ).
  • the PGW ( 1 ) deletes the bearer context and sends a delete session response (Delete Session Response) to the SGW ( 2 ).
  • the SGW ( 2 ) responsive to the delete session response (Delete Session Response) from the PGW ( 1 ), sends a create session response (Create Session Response) to the MME.
  • the MME responsive to a normal response from the SGW ( 2 ), sends a delete session request (Delete Session Request) to the SGW ( 1 ), which is the change-source SGW.
  • the SGW ( 1 ) After deleting bearer context, the SGW ( 1 ) sends a delete session response (Delete Session Response) to the MME.
  • a delete session response (Delete Session Response)
  • the MME On receipt of the response, the MME sends a TA update accept (TA Update Accept) to the user.
  • TA Update Accept a TA update accept
  • the IP information newly assigned to the user, is set in the TA Update Accept and notified to the UE.
  • GTPv2 protocol GPRS (General Packet Radio Service) Tunneling Protocol v2
  • PMIPv6 Proxy Mobile IPv6
  • Proxy Binding Update is used in place of Create Session Request/Delete Session Request.
  • Proxy Binding Acknowledgement is used in place of Create Session Response/Delete Session Response.
  • the sequence to re-select a PGW is as shown in FIG. 5 .
  • FIG. 5 shows the operation when an SGW is changed. However, even in case an SGW is not changed, the basic operation is the same.
  • the message sequence, shown in FIG. 5 is explained using message names for a case where the communication between an SGW and a PGW is implemented in accordance with GTP protocol. However, similar effects may also be obtained in case the communication between the SGW and the PGW is implemented in accordance with PMIP (Proxy Mobile IP) protocol.
  • PMIP Proxy Mobile IP
  • an SGSN is substituted for an MME, the operation is that of PGW re-selection in case an access network is UMTS.
  • PGW PGW based on the position in which a UE resides becomes possible. Since a PGW which is of a physically short distance from the UE or network-topologically close to the UE is selected and connected to the UE, network resources may be optimized by efficient connection.
  • User data transmission delay may be reduced by efficient path connection between the UE and the PGW.
  • TA Update Request On receipt of a TA update request (TA Update Request), sent from a terminal (UE), MME examines whether or not a PGW, to which the UE is connected, is appropriate.
  • FIG. 6 shows a status in which a UE is connected to a PGW ( 1 ) (an EPS bearer established between the UE and the PGW ( 1 ): EPS bearer originally established).
  • the MME decides that re-selection of another suitable PGW is necessary, the MME sets a cause value that urges re-attach in a TA update request (TA Update Request) to send a TA update reject (TA Update Reject) to the UE.
  • TA Update Request TA Update request
  • TA Update Reject TA update reject
  • the UE In response to the TA update reject (TA Update Reject) from the MME, the UE sends an attach (ATTACH) signal to the MME.
  • ATTACH attach
  • the MME On receipt of the TA update reject (TA Update Reject), the MME is able to newly start up a logic for selecting a PGW, as a result of which an optimal PGW is re-selected.
  • a PGW ( 2 ) is re-selected to perform a connection procedure to the PGW ( 2 ). That is, a create session request (Create Session Request) from the MME is sent to the SGM ( 2 ) and the create session request (Create Session Request) is sent from the SGW ( 2 ) to the PGW ( 2 ).
  • the SGW ( 2 ) On receipt of a create session response (Create Session Response) from the PGW ( 2 ), the SGW ( 2 ) sends the create session response to the MME.
  • MME sends a delete session request (Delete Session Request) to the SGW ( 1 ).
  • the SGW ( 1 ) returns a delete session response (Delete Session Response) to the MME.
  • the MME returns TA Update Accept which indicates the completion of TA update, to the terminal (UE).
  • the sequence shown in FIG. 7 is a normal TA update procedure. As a point of change in the present exemplary embodiment, completion of the TA update procedure is notified from an MME to a UE.
  • the MME on receipt of a TA update request (TA Update Request) from the UE, the MME sends a create session request (Create Session Request) to the SGW ( 2 ).
  • a modify bearer request (Modify Bearer Request) is sent from the SGW ( 2 ) to the PGW ( 1 ).
  • the MME On receipt of a create session response (Create Session Response) from the SGW ( 2 ), the MME sends a delete session request (Delete Session Request) to the SGW ( 1 ).
  • the MME On receipt of the delete session response (Delete Session Response) from the SGW ( 1 ), the MME sends a TA update accept (TA Update Accept (PDN)).
  • PDN TA Update Accept
  • new information that is, PDN of the TA Update Accept (PDN) in FIG. 7
  • PDN packet data network
  • PDN packet data network
  • the UE On receipt of the TA update accept (TA Update Accept) signal, added by the new information (PDN), the UE recognizes the PDN (packet data network) for re-connection, based on the information specified. It is noted that a plurality of PDNs may sometimes be so added. For the PDN, the UE starts up a UE requested PDN Disconnection processing (processing of disconnection of the PDN as requested by the UE) or a UE requested PDN connectivity processing (processing of connection of the PDN as requested by the UE) to re-connect the packet data network (PDN).
  • PDN packet data network
  • FIG. 7 shows the operation for the case where the SGW is changed. However, even when the SGW is not changed, the basic operation remains the same.
  • PGW re-connection may be made without starting up ATTACH processing (re-attach).
  • Starting up ATACH processing means that, if there are a plurality of PDN connections, processing for PGW re-selection is started up for the entire PDN connections, and hence the processing of a relatively large scale is invoked.
  • PGW re-selection which may be started up by the EPC (MME) at an optional timing, is made in a manner not dependent upon the TA update procedure carried out by the UE. If, when the MME is in a connected state, PGW re-selection is decided to be necessary, a Page signal is sent to the UE and the connection with the UE is tried.
  • MME EPC
  • the cause information (reason information) is added as an option to the Page signal. See Page (cause) of FIG. 8 .
  • the UE is allowed to neglect this Page signal (Page signal with the cause information). This is a measure taken in order to avoid battery consumption in the UE caused by iterative execution of this processing.
  • the Page signal is a signal used for notification of an incoming call.
  • the Page signal sent in case PGW re-selection is needed, is for enhancing the efficiency of the connection path in the EPC, such that it may not be said to be an indispensable operation.
  • the UE On receipt of this Page signal, the UE sends a service request (Service request) signal to the MME for communication therewith.
  • the MME sends a deactivate bearer request (Deactivate Bearer request) from the MME to the eNodeB.
  • the eNodeB sends an RRC connection reconfiguration.
  • the eNodeB On receipt of a notification of completion of the RRC connection reconfiguration from the UE, the eNodeB sends a deactivate bearer response (Deactivate Bearer Response) to the MME.
  • Service request Service request
  • the MME sends a deactivate bearer request (Deactivate Bearer request) from the MME to the eNodeB.
  • the MME then disconnects the connection of the packet data network (PDN), for which PGW re-selection is necessary, to induce the procedure of UE requested packet data network connection from the UE (UE requested PDN connectivity).
  • PDN packet data network
  • the MME By carrying out this procedure, it becomes possible for the MME to newly start up the PGW selection logic. Thus, as a result, re-selection of suitable PGW becomes necessary.
  • the EPC MME is able to start up PGW re-connection at an optional timing.
  • O&M Operaation and Maintenance
  • LIPA Long Term Evolution
  • SIPTO Session Initiation and Maintenance
  • the MME may re-select PGW at an optional timing.
  • FIGS. 9 and 10 show the arrangement of the present exemplary embodiment.
  • UE 1 to UE 3 are mobile phone apparatuses.
  • eNodeB 11 and 12 are LTE base stations.
  • NodeB 21 and RNC 31 are apparatuses for radio access (Radio Access) adopted by the UMTS system.
  • An MME 41 is an apparatus introduced by EPC to manage the mobility.
  • An SGSN 51 is a serving apparatus used for the UMTS, and may or may not handle a user plane depending upon connection configurations. In case the SGSN does not handle a user plane, the user plane is set between the SGW and the RNC.
  • SGWs 61 and 62 are apparatuses inside the service range that handle the user plane.
  • the PGW 71 and 72 are gateway apparatuses that interconnect the external network (service network 81 in FIG. 9 ) and the EPC.
  • LPGW Local PGW 91 and 92 are gateway apparatuses that share certain portions in common with the eNodeB or that are located extremely close to the eNodeB and to allow connection to the service network 81 .
  • UE 1 and UE 2 are mobile phone apparatuses.
  • NodeB 21 and 22 and RNC 31 and 32 are apparatuses for radio access adopted in the UMTS system.
  • SGSNs 61 and 62 are serving apparatuses and may or may not handle the user plane depending upon connection configurations. In case the SGSN does not handle a user plane, the user plane is set between the GGSN and RNC. It is noted that the configuration in which the user plane is set between the GGSN and RNC is called the ‘direct tunnel connection’.
  • GGSNs 71 and 72 are gateway apparatuses that interconnect the external network (service network 81 in FIG. 10 ) and GPRS (General Packet Radio Service) network.
  • GPRS General Packet Radio Service
  • LGGSNs (Local GGSNs (Gateway GPRS Support Nodes)) 101 and 102 are gateway apparatuses that share certain portions in common with or are located extremely close to the RNCs (Radio Network Controllers) and that allow for connection to the service network 81 .
  • RNCs Radio Network Controllers
  • the MME receives a TA update request (TA Update Request) from the UE.
  • TA Update Request TA Update Request
  • the TA update request (TA Update Request) signal from the eNodeB to the MME is encapsulated in the S1-AP message for transmission.
  • the eNodeB notifies the MME on the S1-AP message of the fact that PDN connection may be set by the LIPA/SIPTO architecture.
  • the MME decides that the SGW needs to be changed, it sends a create session request (Create Session Request) to the SGW ( 2 ) which is a change-target SGW.
  • Create Session Request Create Session Request
  • the MME decides that re-arrangement to LPGW is necessary, the MME selects an LPGW that may efficiently be connected to the external network (service network 81 ), and sets address information that designates the PGW, in the create session request (Create Session Request).
  • the above mentioned notification on the S1-AP message that PDN connection may be set by the LIPA/SIPTO architecture is by way of illustration only such that it is also possible for the MME to decide on the necessity for re-selection based on some other information.
  • the SGW ( 2 ) On receipt of a new PGW address, the SGW ( 2 ) sends a create session request (Create Session Request) to the LPGW. On receipt of the create session request (Create Session Request), the LPGW creates a bearer context (Bearer Context).
  • Create Session Request On receipt of the create session request (Create Session Request), the LPGW creates a bearer context (Bearer Context).
  • the LPGW assigns a new IP address for the user to the UE.
  • the LPGW On completion of assignment of the new IP address for the user and creation of the bearer context (Bearer Context), the LPGW sends a create session response (Create Session Response) to the SGW ( 2 ).
  • the SGW ( 2 ) On receipt of the create session response (Create Session Response), the SGW ( 2 ) sends a delete session request (Delete Session Request) to the PGW( 1 ).
  • the PGW ( 1 ) deletes the bearer context (Bearer Context) and sends a delete session response (Delete Session Response) to the SGW ( 2 ).
  • the SGW On receipt of the delete session response (Delete Session Response), the SGW ( 2 ) sends a create session response (Create Session Response) to the MME.
  • the MME On receipt of the normal response from the LPGW, the MME sends a delete session request (Delete Session Request) to the SGW ( 1 ), a change-source SGW.
  • Delete Session Request a delete session request
  • the SGW ( 1 ) After deleting the bearer context (Bearer Context), the SGW ( 1 ) sends a delete session response (Delete Session Response) to the MME.
  • Delete Session Response Delete Session Response
  • the MME On receipt of the delete session response (Delete Session Response), the MME sends TA accept (TA Accept) to the UE.
  • TA accept TA Accept
  • IP address information newly assigned to the user, is set and notified of the UE.
  • Proxy Binding Update is used in place of the create session request (Create Session Request)/delete session request (Delete Session Request).
  • proxy binding acknowledgement is used in place of the create session response (Create Session Response)/delete session response (Delete Session Response).
  • the sequence for LPGW re-selection is shown in FIG. 11 . However, if the above function is to be implemented, it is necessary for the MME to re-select the PGW at an appropriate timing.
  • FIG. 11 shows the operation when the SGW is changed. However, even in case the SGW is not changed, the basic operation is the same.
  • the message sequence, shown in FIG. 11 is explained in terms of message names for a case where the communication between the SGW and the PGW is implemented using GTP protocol. However, similar effects may also be obtained in case the communication between the SGW and the PGW is implemented using PMIP protocol.
  • the operation is that of PGW re-selection in case the access network is the UMTS.
  • packet communication services may be extended by LPGW re-selection as no user traffic is taken into the EPC.
  • LPGW packet communication services
  • a mobile communication operator is able to reduce a load of an EPC network apparatus.
  • the MME receives a TA update request (TA Update Request) from the UE.
  • TA Update Request a TA update request (TA Update Request) signal is encapsulated in the S1-AP message for communication from the eNodeB to the ME.
  • the eNodeB sends to the MME a notification on the S1-AP message to the effect that PDN connection may be set based on the LIPA/SIPTO architecture.
  • the MME examines whether or not the PGW, the UE in question is connected to, is appropriate. It is noted that the above mentioned notification on the S1-AP message that setting of PDN connection by the LIPA/SIPTO architecture is possible is by way of illustration only such that it is also possible for the MME to decide on the necessity for re-selection of a new PGW based on some other information.
  • FIG. 12 shows a state in which the UE is connected to PGW ( 1 ) (EPS bearer originally established from the UE to the PGW ( 1 )).
  • PGW Packet Control Function
  • the UE is induced by the TA update reject (TA Update Reject) to send the ATTACH signal to the MME.
  • This ATTACH signal is also encapsulated in the S1-AP message for transmission.
  • the eNodeB sends to the MME a notification on the S1-AP message to the effect that PDN connection may be set based on the LIPA/SIPTO architecture.
  • FIG. 12 shows an example connection processing to LPGW re-selected.
  • a create session request (Create Session Request) from the MME to the SGW ( 2 ) and LPGW, a create session response (Create Session Response) from the LPGW to the SGW ( 2 ) and MME, a delete session request (Delete Session Request) from the MME to the SGW ( 1 ), a delete session response (Delete Session Response) from the SGW ( 1 ) to the MME and a TA update accept from the MME to the UE, are sent.
  • packet communication services may be extended by LPGW re-selection as no user traffic is taken into EPC.
  • LPGW packet communication services
  • a mobile communication operator is able to reduce a load of an EPC network apparatus.
  • the configuration of the present exemplary embodiment is that as shown FIG. 9 .
  • the operation of the present exemplary embodiment will now be described with reference to FIG. 13 .
  • the regular TA update procedure is changed.
  • the MME receives a TA update request (TA Update Request) from the UE. It is noted that, in the case of the LIPA/SIPTO architecture, the TA update request (TA Update Request) signal from the eNodeB to the MME is encapsulated in the S1-AP message for transmission.
  • a notification is sent on the S1-AP message to the MME to the effect that PDN connection may be set based on the LIPA/SIPTO architecture. It is noted however that the notification sent on the S1-AP message to the effect that PDN connection may be set based on the LIPA/SIPTO architecture is by way of illustration only such that it is also possible for the MME to decide on the necessity for re-selection of a new PGW based on some other information.
  • the TA update accept (TA Update Accept) signal that notifies the completion of the TA update procedure from the MME to the UE is added by new information (PDN in FIG. 13 ) to urge re-connection of the packet data network (PDN) which is currently in a connected state.
  • PDN packet data network
  • the UE recognizes the PDN (packet data network) for re-connection, based on the information specified. It is noted that a plurality of PDNs may sometimes be so added. For the PDN in question, the UE starts up the conventional UE requested PDN connection processing or the UE requested PDN connectivity processing to re-connect the packet data network (PDN).
  • packet communication services may be extended by LPGW re-selection as no user traffic is taken into EPC.
  • mobile communication operator is able to reduce a load of an EPC network apparatus.
  • the configuration of the present exemplary embodiment is that as shown FIG. 10 .
  • the operation of the present exemplary embodiment will now be described with reference to FIG. 14 .
  • the SGSN (Serving GPRS Support Node) receives an RA (Routing Area) update request (RA Update Request) from the UE.
  • RA Central Area
  • the RA update request signal from the NodeB to the SGSN is encapsulated in a RANUP (Radio Access Network Access Part) message for transmission.
  • the RRC sends to the SGSN a notification on the RANAP message to the effect that PDN connection may be set based on the LIPA/SIPTO architecture.
  • the SGSN examines whether or not the GGSN (Gateway GPRS Support Node), the UE in question is connected to, is appropriate. It is noted that the above mentioned notification on the RANAP message that PDN connection setting by the LIPA/SIPTO architecture is possible is only by way of illustration. That is, it is also possible for the MME to decide on the necessity for re-selection of a new PGW based on some other information.
  • FIG. 14 shows a state in which the UE is connected to GGSN (GTP tunnel connection is established between UE and GGSN: see ‘GTP Tunneling originally established’ of FIG. 14 ).
  • the SGSN decides that LGGSN re-selection is necessary, the SGSN sets a reason value (cause value) that urges re-attach (ATTACH) in the RA update request (RA Update Request) to send back an RA update reject (RA Update Reject) signal to the UE.
  • a reason value cause value
  • ATTACH re-attach
  • RA Update Request RA Update Request
  • RA Update Reject RA update reject
  • the UE is caused by the RA update reject (RA Update Reject) signal to send the ATTACH signal to the SGSN to try to re-attach (ATTACH) to the GPRS network.
  • the SGSN sends an RA update request (RA Update Request) to an HLR (Home Location Register).
  • An insert subscriber data (Insert Subscriber data) is sent from the HLR to the GGSN.
  • the GGSN sends back an insert subscriber data acknowledge (Insert Subscriber data ack) response to the HLR.
  • ack On receipt of the ack response (ack), the HLR sends back an RA update response (RA Update Response) to the SGSN.
  • the SGSN sends back an ATTACH accept (ATTACH Accept) to the UE.
  • the UE then sends a request for activating PDP context (Activate PDP context request), requesting PDP (Packet Data Protocol) connection, to the SGSN.
  • PDP context request Activate PDP context request
  • PDP Packet Data Protocol
  • the SGSN On receipt of the request for activating PDP context (Activate PDP context request), the SGSN decides whether or not the connection to LGGSN is appropriate. When the SGSN decides that the connection to LGGSN is appropriate, the SGSN performs creation of a GTP (GPRS Tunneling Protocol) tunnel to the LGGSN (Create PDP context request).
  • the Create PDP context request is sent back from the LGGSN to the SGSN, and a PDP context activate response (Activate PDP context response) is sent back from SGSN to the UE to enable connection between UE and LGGSN.
  • GTP GPRS Tunneling Protocol
  • packet communication services may be extended by LPGW re-selection as no user traffic is taken into the EPC.
  • LPGW packet communication services
  • a mobile communication operator is able to reduce a load of a GPRS network apparatus.

Landscapes

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

Abstract

A communication method in LIPA/SIPTO architecture is provided which, when a user equipment (UE) is to connect from a serving area to an external network, allows re-selection of an optimal gateway. The communication method allows selecting a gateway apparatus physically or topologically close to a site, where the user equipment is attached.

Description

    CROSS REFERENCE TO RELATED APPLICATIONS
  • This application is a divisional of U.S. patent application Ser. Nos. 13/118,743 filed May 31, 2011 and 13/149,264 filed May 31, 2011 which are divisionals of U.S. patent application Ser. No. 13/131,810, filed May 27, 2011 (published), which is a national stage of International Application No. PCT/JP2010/066211, filed Sep. 17, 2010, claiming priority based on Japanese Patent Application No. 2009-217757, filed Sep. 18, 2009, the contents of all of which are incorporated herein by reference in their entirety.
  • TECHNICAL FIELD
  • This invention relates to a mobile communication system and, more particularly, to a system optimal for re-selection of a gateway that connects a terminal to a packet data network. This invention also relates to a communication controlling method.
  • BACKGROUND
  • In EPC (Evolved Packet Core), bearer management is performed based on an ‘Always On’ concept in such a manner that a PGW (PDN (Packet Data Network) Gateway), initially selected when a UE (User Equipment or ‘terminal’) has attached the EPC, is fixedly used as anchor until the UE detaches. By this manner of operation, it is possible for a service network (a packet data network) to provide services premised on permanent connection. It is because the IP information driven out by the PGW is unchanged even if the UE moves repeatedly within the EPC.
  • When a UE moves within the EPC, an SGW (Serving Gateway) is re-selected in accompaniment with the movement of the UE. Each time the SGW is re-selected, a bearer between the SGW and the PGW is updated by disconnection and re-establishment to ensure connectivity from the UE to the PGW.
  • In general, in selecting a PGW, such a PGW is selected which is close to the SGW physically or from the perspective of network topology.
  • However, in case the UE performs repeated movement over long distances or has stayed in a far-away place after such long-distance movement, the PGW, initially selected, may be far away from a SGW in terms of a distance(a physical or network topological distance). As a result, network efficiency is deteriorated to present problems such as transmission delay of user data or inefficient consumption of network resources within the EPC.
  • For example, when a passenger to Japan from abroad enters at Narita International Airport, he/she may usually power-up the mobile phone apparatus at the International Airport to attach to EPC. Hence, a PGW located close to Narita International Airport is selected. However, after entrance to Japan, he/she may move to e.g., Tokyo, Osaka, Sapporo or Fukuoka. Hence, after each such movement, the PGW close to the Narita International Airport is no longer the most efficient PGW.
  • SUMMARY
  • The following is an analysis by the present inventors. In the EPC network, a default bearer, established at the time of attachment, is not deleted/ re-established until the time of detachment under the ‘Always On’ principle. If the bearer is to be switched due to UE's movement, the PGW, selected at the time of attachment, remains fixed as anchor.
  • Consequently, such a problem is raised that, when a UE moves over a long distance, maintaining connection to the PGW selected at the time of the attachment may be inefficient from the perspective of EPC network.
  • Such a system is thus desired that, when a UE moves over a long distance, and the UE is to connect from a serving area in which the UE resides to an external network (service network), allows re-selecting an optimal PGW (result of analysis by the present inventors).
  • It is therefore an object of the present invention to provide a system and a method, which make it possible to re-select an optimal gateway node, when a terminal (UE) is to connect from a serving area to an external network.
  • In one aspect of the present invention, there is provided In one aspect of the present invention, there is provided a communication method in Local IP Access (LIPA)/Selected IP Traffic Offload (SIPTO) architecture, wherein a gateway apparatus physically or topologically close to a site, where the user equipment is attached, is selected according to movement of the user equipment.
  • According to the present invention, there is provided a communication system in Local IP Access (LIPA)/Selected IP Traffic Offload (SIPTO) architecture, wherein a gateway apparatus physically or topologically close to a site, where the user equipment is attached, is selected, according to movement of the user equipment.
  • According to the present invention, there is provided user equipment in a communication system by Local IP Access (LIPA)/Selected IP Traffic Offload (SIPTO) architecture, wherein a gateway apparatus physically or topologically close to a site, where the user equipment is attached, is selected, according to movement of the user equipment.
  • In another aspect of the present invention, there is provided a communication method in Local IP Access (LIPA)/Selected IP Traffic Offload (SIPTO) architecture, wherein, in case a Serving General Packet Radio Service Support Node (SGSN) decides that it is necessary to re-select a gateway apparatus, the SGSN sends a first signal for setting re-attachment to a user equipment, the user equipment on receipt of the first signal transmitting a second signal for re-attachment to the SGSN and the SGSN re-selecting the gateway apparatus.
  • According to the present invention, there is provided a communication system in Local IP Access (LIPA)/Selected IP Traffic Offload (SIPTO) architecture, comprising a Serving General Packet Radio Service Support Node (SGSN) and a user equipment, wherein the SGSN sends a first signal for setting re-attachment, when the SGSN decides that it is necessary to re-select a gateway apparatus, the user equipment transmits a second signal for re-attachment to the SGSN, on receipt of the first signal, and the SGSN re-selects the gateway apparatus.
  • According to the present invention, there is provided a user equipment in a communication system by Local IP Access (LIPA)/Selected IP Traffic Offload (SIPTO) architecture, wherein the user equipment receives a first signal that sets re-attachment from a Serving General Packet Radio Service Support Node (SGSN) and transmits a second signal for re-attachment to the SGSN to cause re-selection of a gateway apparatus to be performed.
  • In yet another aspect of the present invention, there is provided a communication method in Local IP Access (LIPA)/Selected IP Traffic Offload (SIPTO) architecture, wherein the method comprises: the MME sending a deactivate bearer request (Deactivate Bearer request), requesting re-selection, to a base station, when a mobility management entity (MME) decides that it is necessary to re-select a gateway apparatus;
  • the base station sending an RRC connection reconfiguration (RRC connection reconfiguration) to a user equipment; and
  • the user equipment sending a notification of completion of an RRC connection reconfiguration (RRC connection reconfiguration) to the base station;
  • the base station sending a deactivate bearer response (Deactivate Bearer response) to the MME; and
  • the user equipment initiating a UE requested PDN connectivity (UE requested PDN connectivity) procedure,
  • as a result, re-selection of a gateway apparatus being performed.
  • According to the present invention, there is provided a communication system in Local IP Access (LIPA)/Selected IP Traffic Offload (SIPTO) architecture, comprising:
  • a mobility management entity (MME);
  • a base station; and
  • a user equipment, wherein when the MME decides that it is necessary to re-select a gateway apparatus, the MME sends a deactivate bearer request (Deactivate Bearer request), requesting re-selection, to the base station,
  • the base station sends an RRC connection reconfiguration (RRC connection reconfiguration) to the user equipment,
  • the user equipment sends a notification of completion of the RRC connection reconfiguration (RRC connection reconfiguration) to the base station,
  • the base station sends a deactivate bearer response (Deactivate Bearer response) to the MME,
  • the user equipment initiates a UE requested PDN connectivity (UE requested PDN connectivity) procedure to cause re-selection of a gateway apparatus to be performed.
  • According to the present invention, there is provided a user equipment in a communication system by Local IP Access (LIPA)/Selected IP Traffic Offload (SIPTO) architecture, wherein, in case of receiving an RRC connection reconfiguration from the base station, the user equipment sends a notification of completion of RRC connection reconfiguration to the base station to initiate a UE requested PDN connectivity procedure to cause re-selection of a gateway apparatus to be performed.
  • According to the present invention, it is possible to re-select an optimal gateway node at a time when a user equipment is to connect from a serving area to an external network (service network).
  • Still other features and advantages of the present invention will become readily apparent to those skilled in this art from the following detailed description in conjunction with the accompanying drawings wherein only exemplary embodiments of the invention are shown and described, simply by way of illustration of the best mode contemplated of carrying out this invention. As will be realized, the invention is capable of other and different embodiments, and its several details are capable of modifications in various obvious respects, all without departing from the invention. Accordingly, the drawing and description are to be regarded as illustrative in nature, and not as restrictive.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a diagram showing a entire configuration of a system according to an exemplary embodiment of the present invention.
  • FIG. 2 is a diagram for explaining a Comparative Example.
  • FIG. 3 is a diagram for explaining the present invention.
  • FIG. 4 is a diagram illustrating a sequence of the Comparative Example.
  • FIG. 5 is a diagram illustrating a sequence of an exemplary embodiment 1 of the present invention.
  • FIG. 6 is a diagram illustrating a sequence of an exemplary embodiment 2 of the present invention.
  • FIG. 7 is a diagram illustrating a sequence of an exemplary embodiment 3 of the present invention.
  • FIG. 8 is a diagram illustrating a sequence of an exemplary embodiment 4 of the present invention.
  • FIG. 9 is a diagram showing a configuration of an exemplary embodiment 5 of the present invention.
  • FIG. 10 is a diagram showing a configuration of an exemplary embodiment 6 of the present invention.
  • FIG. 11 is a diagram illustrating a sequence of the exemplary embodiment 5 of the present invention.
  • FIG. 12 is a diagram illustrating a sequence of the exemplary embodiment 6 of the present invention.
  • FIG. 13 is a diagram illustrating a sequence of an exemplary embodiment 7 of the present invention.
  • FIG. 14 is a diagram illustrating a sequence of an exemplary embodiment 8 of the present invention.
  • PREFERRED MODES
  • The following describes exemplary embodiments of the present invention will now be described. A system according to one of modes of the present invention re-selects a PGW (PDN gateway) in EPC in keeping with movement of a user equipment (UE) and re-establishes a default bearer, thereby realizing improvement of transmission delay and efficiency of network resources in the EPC.
  • In current 3GPP standardization, such techniques, termed LIPA (Local IP Access) or SIPTO (Selected IP Traffic Offload), are under study. In these techniques, user traffic is not taken into EPC and is made to have direct access to an external packet network from a radio access network, in which a UE resides. In case the present invention is adapted to cooperate with the LIPA/SIPTO architecture, it becomes possible to realize efficient utilization of network resource more effectively.
  • In a system according to an exemplary embodiment of the present invention, a PGW is re-selected for a UE which is being attached to the EPC.
  • An EPC bearer usually uses in a fixed manner, a PGW which is initially selected when a UE is attached (registered) to the EPC network, as an anchor, until the UE is detached (deleted from registration). However, in case the UE moves over a long distance, it may occur frequently that the PGW initially selected ceases to be a most efficient gateway apparatus for the external network.
  • In one of modes of the present invention, a path (bearer) between a UE and a PGW may be optimized by re-selecting and modifying the PGW, such as when the UE is in an idle state.
  • In one of modes of the present invention, a default bearer is re-established, with the re-selection of as the PGW, when the UE is not involved in packet communication, i.e., when the UE is in idle mode. By so doing, network resources between UE and PGW may be optimized without detracting from the user experience.
  • The following describes the operation in case the UE moved astride an SGW. FIG. 2 shows, as Comparative Example, a case where the present invention is not applied. Referring to FIG. 2, since the UE is attached to an SGW 61 on the left side of FIG. 2, a PGW 71, which is closer to the left side SGW 61 in a physical distance or a network-topological distance, is initially selected, and a connection path 1 is set. When the UE is moved a long distance, the UE continues to use the left-side PGW 71. Hence, the UE and the PGW are connected by an inefficient connection path 2.
  • In contrast, FIG. 3 shows a case where the UE moves astride the SGW, as the present invention is applied. Referring to FIG. 3, since the UE is attached to the SGW 61 on the left side of FIG. 3, the PGW 71, closer to the left side SGW 61 in a physical distance or a network-topological distance, is initially selected, and a connection path 3 is set. The EPC then re-examines the connectivity between the UE and the external network (service network), using the UE's movement over the large distance as a trigger. As a result of the re-check, the EPC gives a decision that a right-side PGW2 provides a more efficient connection (UE-PGW path) than the left-side PGW 71. Hence, the path between the UE and the PGW is changed over from the connection path 3 to the connection path 4, thus assuring more efficient connection. The present invention will now be described with reference to exemplary embodiments.
  • Exemplary Embodiment 1
  • FIG. 1 shows the arrangement of a network system according of the present exemplary embodiment. The basic arrangement itself of the network remains unchanged from a hitherto-used EPC network arrangement.
  • Referring to FIG. 1, UE1 to UE3 are mobile phones. In FIG. 1, eNodeB (evolved Node B) are base stations of LTE (Long Term Evolution), while NodeB 21 and RNC (Radio Network Controller) 31 are apparatuses for radio access adopted in the UMTS (Universal Mobile Telecommunication System).
  • An MME (Mobility Management Entity) 41 is an apparatus for mobility management as introduced by EPC.
  • An SGSN (Serving GPRS (General Packet Radio Service) Support Node) 51 is a serving apparatus, used for UMTS, and may or may not handle a user plane processing, depending on a connection modes.
  • In case the SGSN does not handle a user plane, the user plane is set between the SGW (Serving Gateway) and the RNC.
  • SGWs 61 and 62 are serving apparatuses that may handle the user plane. PGW 71 and 72 are gateway apparatuses that connect an external network (a service network 81 in the drawing) and RNC.
  • The following describes the operation of the present exemplary embodiment. Initially, an update procedure of a tracking area (TA Update Procedure) will be described with reference to a Comparative Example to which the present invention is not applied.
  • FIG. 4 shows a case of TA update accompanied by SGW change (Comparative Example). It is noted that, when a UE is in idle condition, that is, in a no-connection state, it is managed to which tracking area (position registration area) the UE belongs, however, it is not managed in which cell the UE resides.
  • MME receives a TA update request (TA Update Request) from the UE and, if it is determined that SGW needs to be changed, a create session request (Create Session Request) is sent to an SGW (2) which is a change-target SGW.
  • The SGW(2) sends a modify bearer request (Modify Bearer Request) to the PGW (1) to notify the PGW (1) of the fact that the SGW as destination of connection is changed.
  • On completion of update of the bearer context information, the PGW (1) sends a response to the modify bearer request (Modify Bearer Response) to the SGW (2).
  • On receipt of the response to the modify bearer request (Modify Bearer Response) from the PGW (1), the SGW (2) sends a create session response (Create Session Response) to the MME.
  • On receipt of the create session response (normal response) from the SGW (2), the MME sends a delete session request (Delete Session Request) to the SGW (1), which is a change-source SGW.
  • After deletion of the bearer context, the SGW (1) sends a delete session response (Delete Session Response) to the MME.
  • On receipt of the delete session response (Delete Session Response) from the SGW (1), the MME sends a TA (Tracking Access) accept (TA accept) to the UE.
  • In contrast to the Comparative Example, shown in FIG. 4, the sequence operation shown in FIG. 5 is carried out in an exemplary embodiment of the present invention. The following describes the sequence of the present exemplary embodiment with reference to FIG. 5.
  • The MME receives a TA update request (TA Update Request) from the UE. In case the MME decides that the SGW is to be changed, the MME sends a create session request (Create Session Request) to the SWG (2) which is a change-target SGW.
  • In case the MME decides that PGW re-arrangement is necessary, the MME selects a PGW (2) that can be efficiently connected to the external network (service network), and sets address information that identifies the PGW, in the create session request (Create Session Request).
  • The SGW (2), on receipt of the new PGW address, sends a create session request (Create Session Request) to the PGW (2).
  • The PGW (2), responsive to the create session request (Create Session Request) sent from the SGW (2), creates a bearer context. The PGW (2) also assigns a new IP address for the user to the UE. After completion of assignment of the new IP address for the user and creation of the bearer context, the PGW (2) sends a create session response (Create Session Response) to the SGW (2).
  • The SGW (2), responsive to the create session response (Create Session Request) from the PGW (2), sends a delete session request (Delete Session Request) to the PGW (1).
  • The PGW (1) deletes the bearer context and sends a delete session response (Delete Session Response) to the SGW (2).
  • The SGW (2), responsive to the delete session response (Delete Session Response) from the PGW (1), sends a create session response (Create Session Response) to the MME.
  • The MME, responsive to a normal response from the SGW (2), sends a delete session request (Delete Session Request) to the SGW (1), which is the change-source SGW.
  • After deleting bearer context, the SGW (1) sends a delete session response (Delete Session Response) to the MME.
  • On receipt of the response, the MME sends a TA update accept (TA Update Accept) to the user. The IP information, newly assigned to the user, is set in the TA Update Accept and notified to the UE.
  • In the foregoing, such a case has been explained in which GTPv2 protocol (GPRS (General Packet Radio Service) Tunneling Protocol v2) is used between SGW and PGW. Similar functions may be implemented for such a case where PMIPv6 (Proxy Mobile IPv6) is used.
  • In case of using PMIPv6 between the SGW and the PGW, Proxy Binding Update is used in place of Create Session Request/Delete Session Request. Also, Proxy Binding Acknowledgement is used in place of Create Session Response/Delete Session Response.
  • The sequence to re-select a PGW is as shown in FIG. 5. To implement the above functions, it is necessary for an MME to re-select a PGW at an appropriate timing.
  • If, during when a UE is performing packet communication, a PGW connected to a service network is changed, the information such as IP address is changed for a communication counterpart of the UE. As a result, the packet communication by the UE is disconnected. Thus, in the operation shown in FIG. 5, it is necessary to re-select a PGW, during when the UE is not performing packet communication, that is, during ECM (EPS Connection Management)—IDLE time).
  • FIG. 5 shows the operation when an SGW is changed. However, even in case an SGW is not changed, the basic operation is the same. The message sequence, shown in FIG. 5, is explained using message names for a case where the communication between an SGW and a PGW is implemented in accordance with GTP protocol. However, similar effects may also be obtained in case the communication between the SGW and the PGW is implemented in accordance with PMIP (Proxy Mobile IP) protocol.
  • If, in FIG. 5, an SGSN is substituted for an MME, the operation is that of PGW re-selection in case an access network is UMTS.
  • In the present exemplary embodiment, described above, the following operation and advantageous effect may be obtained.
  • The selection of PGW based on the position in which a UE resides becomes possible. Since a PGW which is of a physically short distance from the UE or network-topologically close to the UE is selected and connected to the UE, network resources may be optimized by efficient connection.
  • User data transmission delay may be reduced by efficient path connection between the UE and the PGW.
  • Cooperated with the LIPA/SIPTO architecture, it becomes possible to provide packet communication services without user data being taken into the EPC. Hence, it becomes possible for a mobile communication operator to reduce a load of an EPC network apparatus.
  • Exemplary Embodiment 2
  • The following describes a second exemplary embodiment of the present invention with reference to FIG. 6. On receipt of a TA update request (TA Update Request), sent from a terminal (UE), MME examines whether or not a PGW, to which the UE is connected, is appropriate.
  • FIG. 6 shows a status in which a UE is connected to a PGW (1) (an EPS bearer established between the UE and the PGW (1): EPS bearer originally established).
  • In case the MME decides that re-selection of another suitable PGW is necessary, the MME sets a cause value that urges re-attach in a TA update request (TA Update Request) to send a TA update reject (TA Update Reject) to the UE.
  • In response to the TA update reject (TA Update Reject) from the MME, the UE sends an attach (ATTACH) signal to the MME. On receipt of the TA update reject (TA Update Reject), the MME is able to newly start up a logic for selecting a PGW, as a result of which an optimal PGW is re-selected.
  • In the example of FIG. 6, such a case is shown in which a PGW (2) is re-selected to perform a connection procedure to the PGW (2). That is, a create session request (Create Session Request) from the MME is sent to the SGM (2) and the create session request (Create Session Request) is sent from the SGW (2) to the PGW (2). On receipt of a create session response (Create Session Response) from the PGW (2), the SGW (2) sends the create session response to the MME. MME sends a delete session request (Delete Session Request) to the SGW (1). The SGW (1) returns a delete session response (Delete Session Response) to the MME. On receipt of the delete session response, the MME returns TA Update Accept which indicates the completion of TA update, to the terminal (UE).
  • In the present exemplary embodiment, the following operation and advantageous effect may be obtained.
  • In the present exemplary embodiment 2, no impact is imposed on a UE in the first exemplary embodiment, while minimum changes may suffice insofar as the EPC is concerned.
  • Exemplary Embodiment 3
  • The following describes a third exemplary embodiment of the present invention with reference to FIG. 7. In the present exemplary embodiment, the usual TA update procedure is slightly changed.
  • The sequence shown in FIG. 7 is a normal TA update procedure. As a point of change in the present exemplary embodiment, completion of the TA update procedure is notified from an MME to a UE.
  • Referring to FIG. 7, on receipt of a TA update request (TA Update Request) from the UE, the MME sends a create session request (Create Session Request) to the SGW (2). A modify bearer request (Modify Bearer Request) is sent from the SGW (2) to the PGW (1). On receipt of a create session response (Create Session Response) from the SGW (2), the MME sends a delete session request (Delete Session Request) to the SGW (1). On receipt of the delete session response (Delete Session Response) from the SGW (1), the MME sends a TA update accept (TA Update Accept (PDN)).
  • In the present exemplary embodiment, new information, that is, PDN of the TA Update Accept (PDN) in FIG. 7, is added to a TA Update Accept signal to urge re-connection of the packet data network (PDN) which is currently in a connected state.
  • On receipt of the TA update accept (TA Update Accept) signal, added by the new information (PDN), the UE recognizes the PDN (packet data network) for re-connection, based on the information specified. It is noted that a plurality of PDNs may sometimes be so added. For the PDN, the UE starts up a UE requested PDN Disconnection processing (processing of disconnection of the PDN as requested by the UE) or a UE requested PDN connectivity processing (processing of connection of the PDN as requested by the UE) to re-connect the packet data network (PDN).
  • In this re-connection of the packet data network (PDN), it is possible for the MME to newly start up the PGW selection logic. As a result, it is necessary to re-select an optimum PGW.
  • FIG. 7 shows the operation for the case where the SGW is changed. However, even when the SGW is not changed, the basic operation remains the same.
  • The present exemplary embodiment has the following operation and meritorious effect:
  • According to the present exemplary embodiment, PGW re-connection may be made without starting up ATTACH processing (re-attach).
  • Starting up ATACH processing means that, if there are a plurality of PDN connections, processing for PGW re-selection is started up for the entire PDN connections, and hence the processing of a relatively large scale is invoked.
  • With the present exemplary embodiment, in contrast, only the re-selection of the PGW needed may be made by EPC startup.
  • Exemplary Embodiment 4
  • The following described a fourth exemplary embodiment of the present invention with reference to FIG. 8. In the fourth exemplary embodiment of the present invention, PGW re-selection, which may be started up by the EPC (MME) at an optional timing, is made in a manner not dependent upon the TA update procedure carried out by the UE. If, when the MME is in a connected state, PGW re-selection is decided to be necessary, a Page signal is sent to the UE and the connection with the UE is tried.
  • It is noted that the cause information (reason information) is added as an option to the Page signal. See Page (cause) of FIG. 8. The UE is allowed to neglect this Page signal (Page signal with the cause information). This is a measure taken in order to avoid battery consumption in the UE caused by iterative execution of this processing.
  • Inherently, the Page signal is a signal used for notification of an incoming call. In contrast, the Page signal, sent in case PGW re-selection is needed, is for enhancing the efficiency of the connection path in the EPC, such that it may not be said to be an indispensable operation. On receipt of this Page signal, the UE sends a service request (Service request) signal to the MME for communication therewith. The MME sends a deactivate bearer request (Deactivate Bearer request) from the MME to the eNodeB. The eNodeB sends an RRC connection reconfiguration. On receipt of a notification of completion of the RRC connection reconfiguration from the UE, the eNodeB sends a deactivate bearer response (Deactivate Bearer Response) to the MME.
  • The MME then disconnects the connection of the packet data network (PDN), for which PGW re-selection is necessary, to induce the procedure of UE requested packet data network connection from the UE (UE requested PDN connectivity).
  • By carrying out this procedure, it becomes possible for the MME to newly start up the PGW selection logic. Thus, as a result, re-selection of suitable PGW becomes necessary. For this procedure, the EPC (MME) is able to start up PGW re-connection at an optional timing. In this case, O&M (Operation and Maintenance), LIPA or SIPTO connection/disconnection may be used as a trigger.
  • In the present exemplary embodiment, such operation and meritorious effect may be obtained that the MME may re-select PGW at an optional timing.
  • Exemplary Embodiment 5
  • The following describes a utilization example of the present invention to a LIPA or SIPTO architecture. FIGS. 9 and 10 show the arrangement of the present exemplary embodiment.
  • Referring to FIG. 9, UE1 to UE3 are mobile phone apparatuses. eNodeB 11 and 12 are LTE base stations. NodeB 21 and RNC 31 are apparatuses for radio access (Radio Access) adopted by the UMTS system. An MME 41 is an apparatus introduced by EPC to manage the mobility. An SGSN 51 is a serving apparatus used for the UMTS, and may or may not handle a user plane depending upon connection configurations. In case the SGSN does not handle a user plane, the user plane is set between the SGW and the RNC.
  • SGWs 61 and 62 are apparatuses inside the service range that handle the user plane. The PGW 71 and 72 are gateway apparatuses that interconnect the external network (service network 81 in FIG. 9) and the EPC. LPGW (Local PGW 91 and 92) are gateway apparatuses that share certain portions in common with the eNodeB or that are located extremely close to the eNodeB and to allow connection to the service network 81.
  • In FIG. 10, UE1 and UE2 are mobile phone apparatuses. NodeB 21 and 22 and RNC 31 and 32 are apparatuses for radio access adopted in the UMTS system. SGSNs 61 and 62 are serving apparatuses and may or may not handle the user plane depending upon connection configurations. In case the SGSN does not handle a user plane, the user plane is set between the GGSN and RNC. It is noted that the configuration in which the user plane is set between the GGSN and RNC is called the ‘direct tunnel connection’.
  • GGSNs 71 and 72 are gateway apparatuses that interconnect the external network (service network 81 in FIG. 10) and GPRS (General Packet Radio Service) network.
  • LGGSNs (Local GGSNs (Gateway GPRS Support Nodes)) 101 and 102 are gateway apparatuses that share certain portions in common with or are located extremely close to the RNCs (Radio Network Controllers) and that allow for connection to the service network 81.
  • The following describes the operation of the fifth exemplary embodiment shown in FIG. 9, with reference to the sequence diagram shown in FIG. 11.
  • The MME receives a TA update request (TA Update Request) from the UE. In case the architecture is that of LIPA or SIPTO, the TA update request (TA Update Request) signal from the eNodeB to the MME is encapsulated in the S1-AP message for transmission.
  • At this time, the eNodeB notifies the MME on the S1-AP message of the fact that PDN connection may be set by the LIPA/SIPTO architecture.
  • In case the MME decides that the SGW needs to be changed, it sends a create session request (Create Session Request) to the SGW (2) which is a change-target SGW.
  • In case the MME decides that re-arrangement to LPGW is necessary, the MME selects an LPGW that may efficiently be connected to the external network (service network 81), and sets address information that designates the PGW, in the create session request (Create Session Request). It is noted that the above mentioned notification on the S1-AP message that PDN connection may be set by the LIPA/SIPTO architecture is by way of illustration only such that it is also possible for the MME to decide on the necessity for re-selection based on some other information.
  • On receipt of a new PGW address, the SGW (2) sends a create session request (Create Session Request) to the LPGW. On receipt of the create session request (Create Session Request), the LPGW creates a bearer context (Bearer Context).
  • The LPGW assigns a new IP address for the user to the UE.
  • On completion of assignment of the new IP address for the user and creation of the bearer context (Bearer Context), the LPGW sends a create session response (Create Session Response) to the SGW (2).
  • On receipt of the create session response (Create Session Response), the SGW (2) sends a delete session request (Delete Session Request) to the PGW(1).
  • The PGW (1) deletes the bearer context (Bearer Context) and sends a delete session response (Delete Session Response) to the SGW (2).
  • On receipt of the delete session response (Delete Session Response), the SGW (2) sends a create session response (Create Session Response) to the MME.
  • On receipt of the normal response from the LPGW, the MME sends a delete session request (Delete Session Request) to the SGW (1), a change-source SGW.
  • After deleting the bearer context (Bearer Context), the SGW (1) sends a delete session response (Delete Session Response) to the MME.
  • On receipt of the delete session response (Delete Session Response), the MME sends TA accept (TA Accept) to the UE. In this TA accept (TA Accept), IP address information, newly assigned to the user, is set and notified of the UE.
  • The foregoing description is for the case of using GTPv2 protocol between the SGW and the PGW. Similar functions may, however, be implemented using PMIPv6.
  • In this case, Proxy Binding Update is used in place of the create session request (Create Session Request)/delete session request (Delete Session Request). Also, proxy binding acknowledgement (Proxy Binding Acknowledgement) is used in place of the create session response (Create Session Response)/delete session response (Delete Session Response).
  • The sequence for LPGW re-selection is shown in FIG. 11. However, if the above function is to be implemented, it is necessary for the MME to re-select the PGW at an appropriate timing.
  • If, when the UE is engaged in packet communication, it is tried to change the PGW connected to the service network, the information such as the IP address is changed for the UE's counterpart of communication. As a result, the packet communication by the UE is disconnected. Thus, in the sequence operation shown in FIG. 11, it is necessary to re-select the PGW when the UE is not engaged in packet communication. That is, PGW re-selection is to be made during the ECM-IDLE time.
  • FIG. 11 shows the operation when the SGW is changed. However, even in case the SGW is not changed, the basic operation is the same. The message sequence, shown in FIG. 11, is explained in terms of message names for a case where the communication between the SGW and the PGW is implemented using GTP protocol. However, similar effects may also be obtained in case the communication between the SGW and the PGW is implemented using PMIP protocol.
  • If, in FIG. 11, the MME is substituted by the SGSN, and the eNodeB is substituted by RNC, the operation is that of PGW re-selection in case the access network is the UMTS.
  • In the present exemplary embodiment, as described above, packet communication services may be extended by LPGW re-selection as no user traffic is taken into the EPC. Hence, a mobile communication operator is able to reduce a load of an EPC network apparatus.
  • Exemplary Embodiment 6
  • Following describes a sixth exemplary embodiment of the present invention will now be described. The configuration of the present exemplary embodiment is that as shown FIG. 9. The following describes the operation of the present exemplary embodiment will now be set out with reference to FIG. 12.
  • The MME receives a TA update request (TA Update Request) from the UE. In the case of the LIPA/SIPTO architecture, a TA update request (TA Update Request) signal is encapsulated in the S1-AP message for communication from the eNodeB to the ME. The eNodeB sends to the MME a notification on the S1-AP message to the effect that PDN connection may be set based on the LIPA/SIPTO architecture.
  • The MME examines whether or not the PGW, the UE in question is connected to, is appropriate. It is noted that the above mentioned notification on the S1-AP message that setting of PDN connection by the LIPA/SIPTO architecture is possible is by way of illustration only such that it is also possible for the MME to decide on the necessity for re-selection of a new PGW based on some other information.
  • FIG. 12 shows a state in which the UE is connected to PGW (1) (EPS bearer originally established from the UE to the PGW (1)). In case the MME decides that LPGW re-selection is necessary, it sets a cause value that urges re-attach (ATTACH) in the TA update request (TA Update Request) and returns a TA update reject (TA Update Reject) to the UE.
  • The UE is induced by the TA update reject (TA Update Reject) to send the ATTACH signal to the MME. This ATTACH signal is also encapsulated in the S1-AP message for transmission. The eNodeB sends to the MME a notification on the S1-AP message to the effect that PDN connection may be set based on the LIPA/SIPTO architecture.
  • It is now possible for the MME to newly start up the PGW selection logic. As a result, it becomes necessary to re-select LPGW.
  • FIG. 12 shows an example connection processing to LPGW re-selected. A create session request (Create Session Request) from the MME to the SGW (2) and LPGW, a create session response (Create Session Response) from the LPGW to the SGW (2) and MME, a delete session request (Delete Session Request) from the MME to the SGW (1), a delete session response (Delete Session Response) from the SGW (1) to the MME and a TA update accept from the MME to the UE, are sent.
  • In the present exemplary embodiment, as described above, packet communication services may be extended by LPGW re-selection as no user traffic is taken into EPC. Hence, a mobile communication operator is able to reduce a load of an EPC network apparatus.
  • Exemplary Embodiment 7
  • The following describes a seventh exemplary embodiment of the present invention will now be described. The configuration of the present exemplary embodiment is that as shown FIG. 9. The operation of the present exemplary embodiment will now be described with reference to FIG. 13. In the present exemplary embodiment, the regular TA update procedure is changed.
  • The MME receives a TA update request (TA Update Request) from the UE. It is noted that, in the case of the LIPA/SIPTO architecture, the TA update request (TA Update Request) signal from the eNodeB to the MME is encapsulated in the S1-AP message for transmission.
  • At this time, a notification is sent on the S1-AP message to the MME to the effect that PDN connection may be set based on the LIPA/SIPTO architecture. It is noted however that the notification sent on the S1-AP message to the effect that PDN connection may be set based on the LIPA/SIPTO architecture is by way of illustration only such that it is also possible for the MME to decide on the necessity for re-selection of a new PGW based on some other information.
  • The TA update accept (TA Update Accept) signal that notifies the completion of the TA update procedure from the MME to the UE is added by new information (PDN in FIG. 13) to urge re-connection of the packet data network (PDN) which is currently in a connected state. On receipt of the TA update accept (TA Update Accept) signal added by the new information (PDN), the UE recognizes the PDN (packet data network) for re-connection, based on the information specified. It is noted that a plurality of PDNs may sometimes be so added. For the PDN in question, the UE starts up the conventional UE requested PDN connection processing or the UE requested PDN connectivity processing to re-connect the packet data network (PDN).
  • In this re-connection of the packet data network (PDN), it is possible for the MME to newly start up the PGW selection logic, as a result of which it becomes necessary to re-select an optimum PGW.
  • The operation for the case where the SGW is to be changed has been explained with reference to FIG. 13. However, even when the SGW is not changed, the basic operation remains the same.
  • In the present exemplary embodiment, as described above, packet communication services may be extended by LPGW re-selection as no user traffic is taken into EPC. Hence, mobile communication operator is able to reduce a load of an EPC network apparatus.
  • Exemplary Embodiment 8
  • The following describes an eighth exemplary embodiment of the present invention. The configuration of the present exemplary embodiment is that as shown FIG. 10. The operation of the present exemplary embodiment will now be described with reference to FIG. 14.
  • The SGSN (Serving GPRS Support Node) receives an RA (Routing Area) update request (RA Update Request) from the UE. In the case of the LIPA/SIPTO architecture, the RA update request signal from the NodeB to the SGSN is encapsulated in a RANUP (Radio Access Network Access Part) message for transmission. The RRC sends to the SGSN a notification on the RANAP message to the effect that PDN connection may be set based on the LIPA/SIPTO architecture.
  • The SGSN examines whether or not the GGSN (Gateway GPRS Support Node), the UE in question is connected to, is appropriate. It is noted that the above mentioned notification on the RANAP message that PDN connection setting by the LIPA/SIPTO architecture is possible is only by way of illustration. That is, it is also possible for the MME to decide on the necessity for re-selection of a new PGW based on some other information.
  • FIG. 14 shows a state in which the UE is connected to GGSN (GTP tunnel connection is established between UE and GGSN: see ‘GTP Tunneling originally established’ of FIG. 14).
  • In case the SGSN decides that LGGSN re-selection is necessary, the SGSN sets a reason value (cause value) that urges re-attach (ATTACH) in the RA update request (RA Update Request) to send back an RA update reject (RA Update Reject) signal to the UE.
  • The UE is caused by the RA update reject (RA Update Reject) signal to send the ATTACH signal to the SGSN to try to re-attach (ATTACH) to the GPRS network. The SGSN sends an RA update request (RA Update Request) to an HLR (Home Location Register). An insert subscriber data (Insert Subscriber data) is sent from the HLR to the GGSN. The GGSN sends back an insert subscriber data acknowledge (Insert Subscriber data ack) response to the HLR. On receipt of the ack response (ack), the HLR sends back an RA update response (RA Update Response) to the SGSN. The SGSN sends back an ATTACH accept (ATTACH Accept) to the UE.
  • The UE then sends a request for activating PDP context (Activate PDP context request), requesting PDP (Packet Data Protocol) connection, to the SGSN.
  • On receipt of the request for activating PDP context (Activate PDP context request), the SGSN decides whether or not the connection to LGGSN is appropriate. When the SGSN decides that the connection to LGGSN is appropriate, the SGSN performs creation of a GTP (GPRS Tunneling Protocol) tunnel to the LGGSN (Create PDP context request). The Create PDP context request is sent back from the LGGSN to the SGSN, and a PDP context activate response (Activate PDP context response) is sent back from SGSN to the UE to enable connection between UE and LGGSN.
  • In the present exemplary embodiment, as described above, packet communication services may be extended by LPGW re-selection as no user traffic is taken into the EPC. Hence, a mobile communication operator is able to reduce a load of a GPRS network apparatus.
  • The particular exemplary embodiments or examples may be changed or adjusted within the gamut of the entire disclosure of the present invention, inclusive of claims, based on the fundamental technical concept of the invention. Further, variegated combinations or selection of elements disclosed herein may be made within the framework of the claims. That is, the present invention may encompass various modifications or corrections that may occur to those skilled in the art in accordance with and within the gamut of the entire disclosure of the present invention, inclusive of claim and the technical concept of the present invention.

Claims (6)

1. A communication method in Local IP Access (LIPA)/Selected IP Traffic Offload (SIPTO) architecture, the method comprising:
a Mobility Management Entity (MME) sending a page signal to a user equipment, when a user equipment is in an EPS Connection Management (ECM)-IDLE state;
the user equipment, on receipt of the page signal, transmitting a service request signal to the MME;
the MME, on receipt of the service request signal, sending a 10 deactivate bearer request to a base station;
the base station transmitting an RRC (Radio Resource Control) connection reconfiguration to a user equipment;
the user equipment transmitting a notification of completion of the RRC connection reconfiguration to the base station;
the base station transmitting a deactivate bearer response to the MME; and
the user equipment initiating a packet data network connectivity procedure to cause the MME to perform re-selection of a gateway apparatus.
2. The communication method according to claim 1, wherein the gateway apparatus includes at least one of a serving gateway apparatus and a packet data network gateway apparatus.
3. A communication system in Selected IP Traffic Offload (SIPTO) architecture, the system comprising:
a plurality of gateway apparatuses;
a Mobility Management Entity (MME);
a base station; and
a user equipment, wherein
the MME sends a page signal to the user equipment, when the user equipment is in an EPS Connection Management (ECM)-IDLE state;
the user equipment, on receipt of the page signal, transmits a service request signal to the MME;
the MME, on receipt of the service request signal, sends a deactivate bearer request to the base station;
the base station transmits an RRC (Radio Resource Control)connection reconfiguration to the user equipment;
the user equipment transmits a notification of completion of the RRC connection reconfiguration to the base station;
the base station transmits a deactivate bearer response to the MME; and
the user equipment initiates a packet data network connectivity procedure to cause the MME to perform re-selection of the gateway apparatus.
4. The communication system according to claim 3, wherein the gateway apparatus includes at least a serving gateway apparatus and a packet data network gateway apparatus.
5. A user equipment in a communication system by Selected IP Traffic Offload (SIPTO) architecture, wherein on receipt of a page signal from a Mobility Management Entity (MME), when the user equipment is in an EPS Connection Management (ECM)-IDLE state,
the user equipment transmits a service request signal to the MME,
the user equipment, on receipt of an RRC (Radio Resource Control) connection reconfiguration transmitted from a base station, transmits a notification of completion of the RRC connection reconfiguration to the base station; and
the user equipment initiates a packet data network connectivity procedure to cause the MME to perform re-selection of a gateway apparatus to which the user equipment is to be connected.
6. The user equipment according to claim 5, wherein the gateway apparatus includes at least a serving gateway apparatus and a packet data network gateway apparatus.
US13/398,002 2009-09-18 2012-02-16 Communication system and communication controlling method Abandoned US20120147853A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US13/398,002 US20120147853A1 (en) 2009-09-18 2012-02-16 Communication system and communication controlling method

Applications Claiming Priority (7)

Application Number Priority Date Filing Date Title
JP2009-217757 2009-09-18
JP2009217757 2009-09-18
PCT/JP2010/066211 WO2011034173A1 (en) 2009-09-18 2010-09-17 Communication system and communication control method
US13/118,743 US8750221B2 (en) 2009-09-18 2011-05-31 Communication system and communication controlling method
US13/149,264 US8422452B2 (en) 2009-09-18 2011-05-31 Communication system and communication controlling method
US201113131810A 2011-08-08 2011-08-08
US13/398,002 US20120147853A1 (en) 2009-09-18 2012-02-16 Communication system and communication controlling method

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US13/118,743 Division US8750221B2 (en) 2009-09-18 2011-05-31 Communication system and communication controlling method

Publications (1)

Publication Number Publication Date
US20120147853A1 true US20120147853A1 (en) 2012-06-14

Family

ID=43758772

Family Applications (16)

Application Number Title Priority Date Filing Date
US13/131,810 Abandoned US20110286430A1 (en) 2009-09-18 2010-09-17 Communication system and communication controlling method
US13/149,264 Active US8422452B2 (en) 2009-09-18 2011-05-31 Communication system and communication controlling method
US13/118,743 Active US8750221B2 (en) 2009-09-18 2011-05-31 Communication system and communication controlling method
US13/370,031 Abandoned US20120147851A1 (en) 2009-09-18 2012-02-09 Communication system and communication controlling method
US13/370,112 Abandoned US20120140737A1 (en) 2009-09-18 2012-02-09 Communication system and communication controlling method
US13/370,077 Active US8891449B2 (en) 2009-09-18 2012-02-09 Communication system and communication controlling method
US13/369,995 Abandoned US20120140735A1 (en) 2009-09-18 2012-02-09 Communication system and communication controlling method
US13/370,642 Abandoned US20120140739A1 (en) 2009-09-18 2012-02-10 Communication system and communication controlling method
US13/370,434 Abandoned US20120140738A1 (en) 2009-09-18 2012-02-10 Communication system and communication controlling method
US13/398,253 Abandoned US20120213199A1 (en) 2009-09-18 2012-02-16 Communication system and communication controlling method
US13/398,002 Abandoned US20120147853A1 (en) 2009-09-18 2012-02-16 Communication system and communication controlling method
US13/398,172 Abandoned US20120140742A1 (en) 2009-09-18 2012-02-16 Communication system and communication controlling method
US13/398,223 Abandoned US20120140729A1 (en) 2009-09-18 2012-02-16 Communication system and communication controlling method
US13/397,980 Abandoned US20120147876A1 (en) 2009-09-18 2012-02-16 Communication system and communication controlling method
US14/152,872 Active 2030-11-13 US9247474B2 (en) 2009-09-18 2014-01-10 Communication system and communication controlling method
US14/336,012 Active 2031-05-30 US9565613B2 (en) 2009-09-18 2014-07-21 Communication system and communication controlling method

Family Applications Before (10)

Application Number Title Priority Date Filing Date
US13/131,810 Abandoned US20110286430A1 (en) 2009-09-18 2010-09-17 Communication system and communication controlling method
US13/149,264 Active US8422452B2 (en) 2009-09-18 2011-05-31 Communication system and communication controlling method
US13/118,743 Active US8750221B2 (en) 2009-09-18 2011-05-31 Communication system and communication controlling method
US13/370,031 Abandoned US20120147851A1 (en) 2009-09-18 2012-02-09 Communication system and communication controlling method
US13/370,112 Abandoned US20120140737A1 (en) 2009-09-18 2012-02-09 Communication system and communication controlling method
US13/370,077 Active US8891449B2 (en) 2009-09-18 2012-02-09 Communication system and communication controlling method
US13/369,995 Abandoned US20120140735A1 (en) 2009-09-18 2012-02-09 Communication system and communication controlling method
US13/370,642 Abandoned US20120140739A1 (en) 2009-09-18 2012-02-10 Communication system and communication controlling method
US13/370,434 Abandoned US20120140738A1 (en) 2009-09-18 2012-02-10 Communication system and communication controlling method
US13/398,253 Abandoned US20120213199A1 (en) 2009-09-18 2012-02-16 Communication system and communication controlling method

Family Applications After (5)

Application Number Title Priority Date Filing Date
US13/398,172 Abandoned US20120140742A1 (en) 2009-09-18 2012-02-16 Communication system and communication controlling method
US13/398,223 Abandoned US20120140729A1 (en) 2009-09-18 2012-02-16 Communication system and communication controlling method
US13/397,980 Abandoned US20120147876A1 (en) 2009-09-18 2012-02-16 Communication system and communication controlling method
US14/152,872 Active 2030-11-13 US9247474B2 (en) 2009-09-18 2014-01-10 Communication system and communication controlling method
US14/336,012 Active 2031-05-30 US9565613B2 (en) 2009-09-18 2014-07-21 Communication system and communication controlling method

Country Status (8)

Country Link
US (16) US20110286430A1 (en)
EP (14) EP2466962A3 (en)
JP (17) JP4839495B2 (en)
KR (3) KR101213527B1 (en)
CN (3) CN102484828A (en)
CA (3) CA2764054A1 (en)
ES (1) ES2545502T3 (en)
WO (1) WO2011034173A1 (en)

Families Citing this family (55)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101990192A (en) * 2009-07-30 2011-03-23 中兴通讯股份有限公司 Notification method and device for local IP access connection property
JP5637138B2 (en) 2009-09-18 2014-12-10 日本電気株式会社 Communication system and communication control method
EP2466962A3 (en) 2009-09-18 2013-01-02 NEC Corporation Communication system and communication controlling method
CN103229546B (en) 2010-09-28 2017-02-15 黑莓有限公司 Method and device for releasing connection with local GW when UE moved out of the residential/enterprise network coverage
KR101491579B1 (en) 2010-09-28 2015-02-09 블랙베리 리미티드 Releasing connections with local gw when ue moves out of residential/enterprise network coverage
US9986496B2 (en) 2010-10-13 2018-05-29 Telefonaktiebolaget Lm Ericsson (Publ) Method in a network node of a wireless communications network
US9668199B2 (en) * 2010-11-08 2017-05-30 Google Technology Holdings LLC Wireless communication system, method of routing data in a wireless communication system, and method of handing over a wireless communication device, having an established data connection to a local network
US9107139B2 (en) * 2011-04-01 2015-08-11 Intel Corporation Intelligent P-GW relocation for SIPTO service continuity
EP3171636A1 (en) 2011-04-01 2017-05-24 InterDigital Patent Holdings, Inc. Performing a selective ip traffic offload procedure
US9084093B2 (en) 2011-04-04 2015-07-14 Interdigital Patent Holdings, Inc. Method and apparatus for controlling the application of selected IP traffic offload and local IP access
JP5879751B2 (en) * 2011-06-01 2016-03-08 住友電気工業株式会社 Communication system and communication control method
CN102869042B (en) * 2011-07-05 2014-12-31 中怡(苏州)科技有限公司 Method and system for transmitting wireless data streams
KR20200010613A (en) * 2011-07-12 2020-01-30 인터디지탈 패튼 홀딩스, 인크 Method and apparatus for multi-rat access mode operation
JP5756705B2 (en) * 2011-07-29 2015-07-29 株式会社Nttドコモ Network reconnection system
EP2820884A4 (en) * 2012-03-01 2015-11-25 Nec Corp Communication system, gateway control apparatus, path control apparatus, communication method and program
EP2645777A1 (en) * 2012-03-30 2013-10-02 British Telecommunications Public Limited Company Gateway reselection
EP2709404B1 (en) * 2012-09-18 2020-03-11 Alcatel Lucent Support of nomadic or fixed users in a mobile network
CN104641681B (en) * 2012-09-20 2018-10-26 日本电气株式会社 Communication system and communication control method
US8923880B2 (en) 2012-09-28 2014-12-30 Intel Corporation Selective joinder of user equipment with wireless cell
CN103731811B (en) * 2012-10-11 2018-08-31 中兴通讯股份有限公司 A kind of packet core network of evolution realizes the method and system of mobile management
US20150312806A1 (en) * 2012-11-30 2015-10-29 Interdigital Patent Holdings, Inc. Distributed mobility management technology in a network environment
US9560583B2 (en) * 2012-12-21 2017-01-31 Verizon Patent And Licensing Inc. Gateway selection based on geographical location
US9271197B2 (en) * 2013-05-22 2016-02-23 Futurewei Technologies, Inc. System and method for distributed evolved packet core architecture
JP6191259B2 (en) 2013-06-11 2017-09-06 富士通株式会社 Network separation method and network separation device
JP5724046B1 (en) 2013-06-19 2015-05-27 ソフトバンクテレコム株式会社 Communication system and program
JP6229368B2 (en) * 2013-08-09 2017-11-15 富士通株式会社 Access control method, access control system, and access control apparatus
US9510376B2 (en) 2013-09-25 2016-11-29 At&T Intellectual Property I, L.P. Tunneling packet exchange in long term evolution protocol based networks
EP3637939B1 (en) * 2013-11-01 2021-06-23 Huawei Technologies Co., Ltd. Apparatus, device, and method for establishing connection to packet data network
CN104661205B (en) * 2013-11-22 2019-12-03 中兴通讯股份有限公司 A kind of gateway updates information notice method and controller
CN104735638B (en) * 2013-12-18 2020-10-23 中兴通讯股份有限公司 Method for information interaction in small cell environment, base station and mobile management entity
EP2887733A1 (en) * 2013-12-20 2015-06-24 NTT DoCoMo, Inc. Mobility for mobility anchors
KR20160014382A (en) * 2014-07-29 2016-02-11 삼성전자주식회사 Apparatus and method for relocating anchor gateway in wireless communication system
KR101639061B1 (en) * 2014-08-25 2016-07-12 에스케이텔레콤 주식회사 Network apparatus and control method thereof
JP7046487B2 (en) * 2014-09-25 2022-04-04 シャープ株式会社 UE, core network device and UE communication control method
JP2017532826A (en) * 2014-10-03 2017-11-02 インテル アイピー コーポレーション Establish packet data network connection during handover
US9538563B2 (en) 2014-10-13 2017-01-03 At&T Intellectual Property I, L.P. System and methods for managing a user data path
US9445256B1 (en) * 2014-10-22 2016-09-13 Sprint Spectrum L.P. Binding update forwarding between packet gateways
JP6599886B2 (en) * 2014-11-11 2019-10-30 シャープ株式会社 Terminal device, communication control method for terminal device, control device in core network, and communication control method for core network
KR102106547B1 (en) * 2015-08-14 2020-05-06 텔레호낙티에볼라게트 엘엠 에릭슨(피유비엘) Nodes and methods for managing packet data network connections
CN107005965B (en) 2015-08-17 2020-02-14 华为技术有限公司 Method and device for updating user plane gateway
US10237795B2 (en) * 2015-10-11 2019-03-19 Qualcomm Incorporated Evolved packet data gateway (EPDG) reselection
AU2015412035B2 (en) * 2015-10-14 2019-12-05 Telefonaktiebolaget Lm Ericsson (Publ) Method and nodes for handling network connections
JP2019009481A (en) * 2015-11-10 2019-01-17 シャープ株式会社 Terminal device, c-sgn, and communication control method
WO2017095809A1 (en) * 2015-11-30 2017-06-08 Intel Corporation Mobile-terminated packet transmission
US9924431B2 (en) * 2016-02-08 2018-03-20 Smartsky Networks LLC Seamless relocation of a mobile terminal in a wireless network
US9936430B1 (en) * 2016-03-07 2018-04-03 Sprint Spectrum L.P. Packet gateway reassignment
RU2713628C1 (en) 2016-05-13 2020-02-05 Телефонактиеболагет Лм Эрикссон (Пабл) Method and units for implementation of mobility by request
JP7018884B2 (en) * 2016-08-18 2022-02-14 株式会社Nttドコモ Communication method
EP3500043A4 (en) 2016-08-26 2019-09-04 Huawei Technologies Co., Ltd. Network management method and controller
CN106304228B (en) * 2016-09-05 2019-10-22 广东工业大学 A kind of PGW method for handover control, system and server
EP3346760B1 (en) * 2017-01-04 2021-07-07 HTC Corporation Devices and methods for handling a new radio connection in inter-system mobility
KR102001480B1 (en) 2017-10-25 2019-10-01 에스케이텔레콤 주식회사 Mobile communication system and method applying data packet manipulation for mission critical service
KR102055830B1 (en) 2019-06-25 2019-12-13 에스케이텔레콤 주식회사 Mobile communication system and method applying data packet manipulation for mission critical service
JP7280206B2 (en) 2020-01-09 2023-05-23 株式会社東芝 semiconductor equipment
US20220256623A1 (en) * 2021-02-05 2022-08-11 Parallel Wireless, Inc. GTPC (S11 and S5 Interface) Optimization for EPC Core Nodes

Family Cites Families (37)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5602839A (en) * 1995-11-09 1997-02-11 International Business Machines Corporation Adaptive and dynamic message routing system for multinode wormhole networks
JP3468177B2 (en) * 1999-10-28 2003-11-17 日本電気株式会社 Mobile wireless communication system, wireless communication gateway server device, position information calculation system, method therefor, and recording medium
US7181219B2 (en) * 2003-05-22 2007-02-20 Lucent Technologies Inc. Wireless handover using anchor termination
CN101170808B (en) * 2006-10-25 2011-03-30 华为技术有限公司 Switching method and system for heterogenous access systems
JP5021772B2 (en) 2007-03-20 2012-09-12 ゼットティーイー コーポレーション How to prevent resources being accidentally released during the tracking area update or switchover process
US8483174B2 (en) * 2007-04-20 2013-07-09 Qualcomm Incorporated Method and apparatus for providing gateway relocation
US8619668B2 (en) 2007-06-07 2013-12-31 Qualcomm Incorporated Mobility management mode selection in multiple access wireless networks
US20080320149A1 (en) 2007-06-25 2008-12-25 Stefano Faccin Service request device wireless access detach and bearer deactivation methods withou loss of internet protocol connectivity
KR101002810B1 (en) 2007-08-10 2010-12-21 삼성전자주식회사 Method and apparatus for registering terminal in packet switching domain
FI20075631A0 (en) * 2007-09-10 2007-09-10 Nokia Siemens Networks Oy Procedure, radio system and base station
CN101136835B (en) * 2007-09-30 2011-09-21 中兴通讯股份有限公司 Bearing establishment method under idle mode
EP2218270B1 (en) * 2007-10-29 2011-11-23 Nokia Corporation System and method for authenticating a context transfer
KR100960115B1 (en) 2007-11-29 2010-05-27 한국전자통신연구원 Mobile communication system and its method for tunnel management
US9247420B2 (en) 2007-12-12 2016-01-26 Lg Electronics Inc. Method of managing user equipment capabilities
CN101521871B (en) * 2008-02-26 2010-10-27 大唐移动通信设备有限公司 Method, device and system for updating tracking area
US8179903B2 (en) 2008-03-12 2012-05-15 Qualcomm Incorporated Providing multiple levels of service for wireless communication devices communicating with a small coverage access point
JP5149045B2 (en) 2008-03-13 2013-02-20 株式会社神戸製鋼所 Production plan creation device, production plan creation method, and program
CN101286915B (en) 2008-06-11 2012-05-09 中兴通讯股份有限公司 Access control method of packet data network, system thereof and PCRF entity
WO2009157171A1 (en) * 2008-06-24 2009-12-30 パナソニック株式会社 Handover processing method, and mobile terminal and connection management device used in the method
WO2010022082A1 (en) * 2008-08-18 2010-02-25 Starent Networks, Corp Combined gateway for network communications
EP2166724A1 (en) * 2008-09-23 2010-03-24 Panasonic Corporation Optimization of handovers to untrusted non-3GPP networks
KR101561063B1 (en) 2009-02-24 2015-10-19 삼성전자주식회사 Method and apparatus for supporting local breakout service at wireless communication network comprising femto cell
WO2010102652A1 (en) * 2009-03-13 2010-09-16 Nokia Siemens Networks Oy Local breakout with optimized interface
JP5383822B2 (en) * 2009-04-03 2014-01-08 パナソニック株式会社 Mobile communication method, mobile communication system, and apparatus used in the method
US8750140B2 (en) * 2009-05-05 2014-06-10 Motorola Mobility Llc Support of home network base station local internet protocol access
US8144696B2 (en) * 2009-06-18 2012-03-27 Nokia Siemens Networks Oy Mobile management entity operating in communications network and selection method therefor
US20100331012A1 (en) * 2009-06-29 2010-12-30 Yang Zhang TDOA-Based Reconstruction of Base Station Location Data
US8442004B2 (en) 2009-06-29 2013-05-14 Motorola Mobility Llc Service continuity during outbound handover from a home network base station with local internet protocol access
CN101990192A (en) * 2009-07-30 2011-03-23 中兴通讯股份有限公司 Notification method and device for local IP access connection property
WO2011020624A2 (en) 2009-08-20 2011-02-24 Nec Europe Ltd. A method for controlling the traffic within a network structure and a network structure
GB2472866B (en) 2009-08-21 2013-05-08 Samsung Electronics Co Ltd Network elements, integrated circuits and methods for routing control
KR20110020161A (en) 2009-08-21 2011-03-02 엘지전자 주식회사 Server for control plane at mobile communication network and method for controlling sipto based session
EP2466962A3 (en) 2009-09-18 2013-01-02 NEC Corporation Communication system and communication controlling method
US8418107B2 (en) 2010-11-10 2013-04-09 International Business Machines Corporation Performing statistical timing analysis with non-separable statistical and deterministic variations
JP4927213B1 (en) * 2010-12-03 2012-05-09 株式会社エヌ・ティ・ティ・ドコモ Mobile communication method, gateway device, mobility management node, and call session control server device
JP5021821B2 (en) * 2011-01-07 2012-09-12 株式会社エヌ・ティ・ティ・ドコモ Mobile communication method, mobility management node, and serving gateway device
MX2013006792A (en) * 2011-01-07 2013-07-29 Nec Corp Mobile communication method, mobile management nodes, and serving gateways.

Also Published As

Publication number Publication date
JP2012105304A (en) 2012-05-31
WO2011034173A1 (en) 2011-03-24
JP5704666B2 (en) 2015-04-22
JP2012044703A (en) 2012-03-01
EP2466962A3 (en) 2013-01-02
KR20120008082A (en) 2012-01-25
JP4852729B2 (en) 2012-01-11
EP2466960A3 (en) 2013-01-09
EP2466957A3 (en) 2013-01-09
EP2466955A3 (en) 2013-01-02
US20140126541A1 (en) 2014-05-08
US20120147876A1 (en) 2012-06-14
JP2012080579A (en) 2012-04-19
JP2011217396A (en) 2011-10-27
US20120140735A1 (en) 2012-06-07
JP2012120203A (en) 2012-06-21
EP2477440A3 (en) 2012-12-26
JP2014045513A (en) 2014-03-13
KR101215191B1 (en) 2012-12-24
EP2466960A2 (en) 2012-06-20
US20120140742A1 (en) 2012-06-07
JP2015119500A (en) 2015-06-25
EP2466962A2 (en) 2012-06-20
JP4839495B2 (en) 2011-12-21
KR20120023150A (en) 2012-03-12
CA2764054A1 (en) 2011-03-24
EP2477440A2 (en) 2012-07-18
EP2487959A3 (en) 2013-03-06
US20120140729A1 (en) 2012-06-07
EP2466958A3 (en) 2013-01-09
EP2475200A2 (en) 2012-07-11
US20110286410A1 (en) 2011-11-24
JP2011217397A (en) 2011-10-27
US20120140736A1 (en) 2012-06-07
JP5451939B2 (en) 2014-03-26
EP2466955A2 (en) 2012-06-20
EP2442611A4 (en) 2012-11-28
EP2442611A1 (en) 2012-04-18
US20110292912A1 (en) 2011-12-01
EP2498543A3 (en) 2012-11-28
US9565613B2 (en) 2017-02-07
US20120213199A1 (en) 2012-08-23
JP2012044702A (en) 2012-03-01
ES2545502T3 (en) 2015-09-11
JP2012070441A (en) 2012-04-05
EP2475200A3 (en) 2012-11-28
KR20120024893A (en) 2012-03-14
EP2466956A3 (en) 2013-03-06
JP2012120204A (en) 2012-06-21
JP2012080580A (en) 2012-04-19
EP2487959B1 (en) 2015-05-27
CN102547889A (en) 2012-07-04
EP2466957A2 (en) 2012-06-20
KR101203428B1 (en) 2012-11-21
CA2773288A1 (en) 2011-03-24
US8750221B2 (en) 2014-06-10
EP2466958A2 (en) 2012-06-20
US20120147851A1 (en) 2012-06-14
EP2477441A3 (en) 2012-11-28
EP2466956A2 (en) 2012-06-20
JP2012095329A (en) 2012-05-17
JP2014057379A (en) 2014-03-27
JP5413996B2 (en) 2014-02-12
US20120140737A1 (en) 2012-06-07
JP2012095330A (en) 2012-05-17
US20140328321A1 (en) 2014-11-06
US20110286430A1 (en) 2011-11-24
JP4997382B2 (en) 2012-08-08
EP2466959A2 (en) 2012-06-20
JP4852730B2 (en) 2012-01-11
US9247474B2 (en) 2016-01-26
US8891449B2 (en) 2014-11-18
EP2498543A2 (en) 2012-09-12
JP5322329B2 (en) 2013-10-23
JP5288515B2 (en) 2013-09-11
CA2773158A1 (en) 2011-03-24
JP4997381B2 (en) 2012-08-08
EP2477441B1 (en) 2014-05-21
JP2012060679A (en) 2012-03-22
KR101213527B1 (en) 2012-12-18
EP2466961A3 (en) 2013-01-02
JPWO2011034173A1 (en) 2013-02-14
EP2477441A2 (en) 2012-07-18
CN102523629A (en) 2012-06-27
EP2487959A2 (en) 2012-08-15
US8422452B2 (en) 2013-04-16
EP2466959A3 (en) 2013-01-09
US20120140738A1 (en) 2012-06-07
CA2773288C (en) 2015-10-27
EP2466961A2 (en) 2012-06-20
CA2773158C (en) 2015-10-27
US20120140739A1 (en) 2012-06-07
CN102484828A (en) 2012-05-30

Similar Documents

Publication Publication Date Title
US8422452B2 (en) Communication system and communication controlling method

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION