WO2013073556A1 - ホーム基地局装置、移動通信システム、移動端末装置及び位置管理装置 - Google Patents

ホーム基地局装置、移動通信システム、移動端末装置及び位置管理装置 Download PDF

Info

Publication number
WO2013073556A1
WO2013073556A1 PCT/JP2012/079474 JP2012079474W WO2013073556A1 WO 2013073556 A1 WO2013073556 A1 WO 2013073556A1 JP 2012079474 W JP2012079474 W JP 2012079474W WO 2013073556 A1 WO2013073556 A1 WO 2013073556A1
Authority
WO
WIPO (PCT)
Prior art keywords
henb
handover
lipa
base station
home base
Prior art date
Application number
PCT/JP2012/079474
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
政幸 榎本
真史 新本
順二 平出
Original Assignee
シャープ株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by シャープ株式会社 filed Critical シャープ株式会社
Priority to CN201280056589.6A priority Critical patent/CN103947257A/zh
Priority to US14/358,063 priority patent/US20140321429A1/en
Priority to EP12850142.6A priority patent/EP2782393A4/en
Publication of WO2013073556A1 publication Critical patent/WO2013073556A1/ja

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • H04W36/125—Reselecting a serving backbone network switching or routing node involving different types of service backbones
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • H04W64/006—Locating users or terminals or network equipment for network management purposes, e.g. mobility management with additional information processing, e.g. for direction or speed determination
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0064—Transmission or use of information for re-establishing the radio link of control information between different access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/00835—Determination of neighbour cell lists
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/04—Reselecting a cell layer in multi-layered cells
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/082—Mobility data transfer for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H04W84/045—Public Land Mobile systems, e.g. cellular systems using private Base Stations, e.g. femto Base Stations, home Node B

Definitions

  • the present invention relates to a mobile communication system in which a local home network to which a plurality of home base station devices including a mobile terminal device and a home base station device to which the mobile terminal device is connected is connected to an external network via a gateway device.
  • Non-Patent Document 1 The standardization organization 3GPP (The 3rd Generation Generation Partnership Project) of the mobile communication system is working on the specification of the EPS (Evolved Packet System) described in Non-Patent Document 1 as the next generation mobile communication system. It is being advanced.
  • 3GPP The 3rd Generation Generation Partnership Project
  • EPS Evolved Packet System
  • a base station device As a constituent device of EPS, a base station device (eNB) forms a macro cell and covers a radius of several hundred meters to several kilometers.
  • the base station apparatus accommodates mobile terminals using radio access technology. And it connects to the core network which is a network which a mobile communication provider operates, and relays the communication data of the mobile communication terminal (UE) to accommodate.
  • HeNB home base station device
  • the HeNB constructs a radio cell of several tens of meters called a femto cell, and accommodates the UE using the same radio access technology as that of a normal eNB. And it connects to the core network which is a network which a mobile communication carrier operates, and relays the communication data of UE to accommodate. Further, the HeNB can connect to the core network of the mobile communication system via a broadband line which is a network such as a home or office, and relay communication data of the accommodated UE. Further, the HeNB can directly connect to a local network (such as a home LAN or an intranet) and provide a connection between the UE and the local network (Local IP Access, LIPA).
  • LIPA Local IP Access
  • the UE During data transmission / reception, when the UE cannot maintain the connection state with the eNB that is transmitting / receiving data due to movement of the UE, the UE switches to an appropriate eNB, maintains the connection state, and transmits / receives data. Continuing is called a handover procedure.
  • the eNB that is the switching source (movement source) at the time of the handover procedure is referred to as a Source eNB.
  • an eNB that is a switching destination (movement destination) during the handover process is referred to as a Target eNB.
  • HeNB is studied and specified as an alternative means of access to eNB.
  • the HeNB can enjoy the same service as when the UE accesses the eNB even in a place that is not covered by the eNB.
  • a handover procedure can be performed.
  • Non-Patent Document 2 discusses a handover procedure in which a LIPA connection is made from a HeNB and the HeNB is switched while the LIPA connection is maintained by movement of the UE.
  • the HeNB has already been specified, and an HeNB that is not compatible with the LIPA handover procedure is beginning to be installed. In the future, even if the HeNB corresponding to the LIPA handover procedure is specified and the use is started, the HeNB not corresponding to the LIPA handover procedure may remain as it is, and the HeNB corresponding to the LIPA handover procedure is supported. It is assumed that HeNBs that are not compatible with HeNBs corresponding to the LIPA handover procedure are mixed. Since the LIPA handover procedure is a new function for the current version of HeNB, even if the conventional HeNB receives the handover request message in LIPA, it cannot process the handover request message in LIPA.
  • Such a mixture of HeNBs that support the LIPA handover procedure and HeNBs that do not support the LIPA handover procedure is such that the Source HeNB that supports the LIPA handover procedure performs handover to the Target HeNB that does not support the LIPA handover procedure.
  • the request is transmitted and the LIPA handover procedure cannot be started, the handover request is transmitted unnecessarily, and unnecessary control information (handover request) is transmitted.
  • the Source HeNB once determines that the LIPA handover procedure cannot be started, it does not manage the HeNB that does not support the LIPA handover procedure. An unnecessary handover request has been sent.
  • Non-Patent Document 2 and Non-Patent Document 3 the Source HeNB does not support the eNB corresponding to the LIPA handover procedure and the HeNB not corresponding to the LIPA handover procedure. Is stored in the neighboring HeNB relation table, and when the Source HeNB starts a handover procedure, the HeNB is used to select a HeNB that transmits a handover request with reference to the neighboring HeNB relation table.
  • Non-Patent Document 3 when the LIPA handover procedure is started in the case of LIPA connection, the source HeNB that is the source of movement during transmission / reception of data with the UE determines the start of the LIPA handover procedure, and the source HeNB It is described that a handover request, which is a trigger for a handover procedure, is transmitted to a target HeNB as a movement destination. At this time, the handover request includes an information element for performing the LIPA handover procedure in the local home network, not the conventional handover request.
  • Non-Patent Document 3 describes that when the Target HeNB does not support the LIPA handover procedure in the local network, the new parameter included in the handover request is ignored and a conventional handover request response is transmitted. Yes. At this time, if the conventional handover request response is transmitted in the Target HeNB without being involved in the new parameters included in the handover request, the Source HeNB confirms that the Target HeNB does not support the LIPA handover procedure in the local home network. Detect.
  • the Source HeNB detects a HeNB that does not support the LIPA handover procedure, and classifies the HeNB that does not support the LIPA handover procedure in the neighboring HeNB relation table.
  • the neighboring HeNB relation table is set in advance as a system configuration, but the HeNB can be freely installed by the user to some extent, and the arrangement of the HeNB may be frequently changed as the configuration of the local home network. Since it is assumed that there is a possibility that the neighbor HeNB relation table is frequently changed, it is necessary to dynamically create the neighbor HeNB relation table.
  • the conventional method for detecting a target HeNB by Source HeNB may not be detected correctly. For example, if the Source HeNB sends a handover request to the Target HeNB, and the Target HeNB sends a handover failure notification as a response that cannot start the LIPA handover procedure, the Source HeNB assumes that the Target HeNB is compatible with the LIPA handover procedure. Has also been detected as a HeNB that does not support the LIPA handover procedure.
  • the handover failure notification is not only performed when the Target HeNB is a HeNB that does not support the LIPA handover procedure, but also when the handover request is transmitted even if the HeNB is compatible with the LIPA handover procedure. Since there is a possibility of transmission even in the case of a HeNB that does not support the procedure, the Source HeNB has erroneously detected the Target HeNB.
  • Target HeNB does not support the LIPA handover procedure, and therefore it cannot be correctly classified as a HeNB corresponding to the LIPA handover procedure in the neighboring HeNB relation table.
  • a method for transmitting a handover request response indicating that the Target HeNB is compatible with the LIPA handover procedure is not defined, and it has not been possible to detect that the Target HeNB supports the LIPA handover procedure.
  • Target HeNB cannot correctly detect that the LIPA handover procedure is supported, it cannot be classified as a HeNB that supports the LIPA handover procedure in the neighboring HeNB relation table.
  • the object of the present invention is to have a source HeNB (home base station apparatus to which a mobile terminal apparatus is connected) transmit a handover request, and a target HeNB (other home base station apparatus)
  • a source HeNB home base station apparatus to which a mobile terminal apparatus is connected
  • a target HeNB other home base station apparatus
  • An object of the present invention is to provide a mobile communication system that can start a LIPA handover procedure using a management table by transmitting a response to a handover request.
  • the home base station apparatus of the present invention is A local home network to which a plurality of home base station devices including a mobile terminal device and a home base station device to which the mobile terminal device is connected is connected is included in a mobile communication system connected to an external network through a gateway device.
  • the home base station apparatus of the present invention is When the handover request includes an address of the gateway device, the updating means includes the address of the gateway device to which the home base station device to which the mobile terminal device is connected and the handover request. If the address of the gateway device is different, the home base station device updates that the LIPA handover is impossible.
  • the home base station apparatus of the present invention A local home network to which a plurality of home base station devices including a mobile terminal device and a home base station device to which the mobile terminal device is connected is connected is included in a mobile communication system connected to an external network through a gateway device.
  • a handover request receiving means for receiving a handover request from a home base station apparatus to which the mobile terminal apparatus is connected;
  • a handover request response transmitting means for transmitting a handover request response including an address of the gateway device to be connected when the address of the gateway device is included in the option area of the handover request and the LIPA handover can be accepted; , It is characterized by providing.
  • the mobile communication system of the present invention is In a mobile communication system in which a local home network to which a plurality of home base station devices including a mobile terminal device and a home base station device to which the mobile terminal device is connected is connected is connected to an external network via a gateway device.
  • the home base station device A management table for managing whether or not other home base station devices can perform LIPA handover; Determining means for determining, as a handover destination, a home base station apparatus capable of LIPA handover from the management table when the mobile terminal apparatus performs handover to another home base station apparatus; With A handover request transmitting means for transmitting a handover request including an address of a gateway device connected at least to the option area to another home base station device; Handover receiving means for receiving a handover request response from another home base station device; Updating means for updating the management table that the LIPA handover is possible when the handover request includes the address of the gateway device, and that the LIPA handover is impossible when the address of the gateway device is not included; , It is characterized by having.
  • the mobile station apparatus of the present invention is connected to the mobile communication system.
  • the position management device of the present invention is A local home network to which a plurality of home base station devices including a mobile terminal device and a home base station device to which the mobile terminal device is connected is connected to a mobile communication system connected to an external network via a gateway device.
  • a handover request receiving means for receiving a handover request from a home base station apparatus to which the mobile terminal apparatus is connected;
  • the confirmation means for confirming whether the home base station apparatus included in the handover request can accept the LIPA handover;
  • a handover request response transmission that transmits a handover request response including an address of a gateway apparatus to which the home base station apparatus is connected Means, It is provided with.
  • the Source HeNB detects whether the Target HeNB is compatible with the LIPA handover procedure by transmitting a handover request including an information element indicating the LIPA handover procedure, and the neighboring HeNB A table can be constructed, and the neighbor HeNB relationship table can be used to suppress transmission of unnecessary handover requests and to start an efficient LIPA handover procedure.
  • the Source HeNB can detect whether the Target HeNB is compatible with the LIPA handover procedure by including a new information element indicating that the procedure is a LIPA handover procedure in the handover request.
  • Target HeNB can indicate that it does not support the LIPA handover procedure by receiving the handover request from the Source HeNB and transmitting a conventional handover request response.
  • the Source HeNB can receive the conventional handover request response from the Target HeNB, and can detect that the Target HeNB is an HeNB that does not support the LIPA handover procedure.
  • the Source HeNB can detect that the Target HeNB is a HeNB that does not support the LIPA handover procedure, and can classify it as a HeNB that does not support the LIPA handover procedure in the neighboring HeNB relation table.
  • the Target HeNB can indicate that it corresponds to the LIPA handover procedure by receiving the handover request from the Source HeNB and transmitting a handover request response in the LIPA handover procedure.
  • the Source HeNB can detect that the Target HeNB is a HeNB corresponding to the LIPA handover procedure by receiving the handover request response in the LIPA handover procedure from the Target HeNB.
  • the Source HeNB can detect that the Target HeNB is a HeNB corresponding to the LIPA handover procedure, and can be classified as a HeNB corresponding to the LIPA handover procedure in the neighboring HeNB relation table.
  • the Source HeNB transmits a handover request to the HeNB that does not support the LIPA handover procedure by using the neighboring HeNB relationship table in which the HeNB that does not support the LIPA handover procedure and the HeNB that supports the LIPA handover procedure are classified in the neighbor HeNB related table. By suppressing this, an efficient LIPA handover procedure can be started.
  • HeNB (2nd Target HeNB) in 1st Embodiment It is a figure for demonstrating the function structure of HeNB (2nd Target HeNB) in 1st Embodiment. It is a figure which shows an example of a format of a LIPA handover request response message. It is a figure for demonstrating the function structure of UE in 1st Embodiment. It is a figure for demonstrating the function structure of LGW in 1st Embodiment. It is the figure which showed an example of the data structure of the binding information in 1st Embodiment. It is a figure for demonstrating the function structure of SGW in 1st Embodiment. It is a figure for demonstrating the function structure of MME in 1st Embodiment.
  • FIG. 1 is a schematic diagram showing a mobile communication system 1 according to the first embodiment of the present invention.
  • the mobile communication system 1 includes a home base station device (HeNB) 10, a home base station device (HeNB) 20, a home base station device (HeNB) 25, a mobile terminal device (UE) 30, an LGW 40, a PDN 70, A core network 80 and a home network 90 are included.
  • the core network 80 includes a PGW 45, an SGW 50, and an MME 60.
  • the home base station apparatus is simply referred to as “HeNB”
  • the mobile terminal apparatus UE is simply referred to as “UE”.
  • the mobile terminal apparatus will be described as a UE.
  • a communication device that transmits and receives data to and from the UE 30 is arranged.
  • the UE 30 moves from the HeNB 10 during data transmission / reception with the communication device in the home network 90 via the HeNB 10 and the LGW 40.
  • the transmission and reception of data between the UE 30 and the communication device in the home network 90 is referred to as LIPA (Local IP access).
  • the UE 30 when data is transmitted and received between the UE 30 and the communication device in the home network 90, the UE 30 must establish a PDN connection for LIPA with the LGW 40.
  • the PDN connection for LIPA is a logical path from the UE 30 to the LGW 40.
  • the UE 30 needs to set up the LGW 40 and the LIPA bearer after establishing the PDN connection for LIPA with the LGW 40 when transmitting / receiving data to / from the communication device in the home network via the LGW 40.
  • the LIPA bearer is a communication resource for transmitting and receiving data between the UE 30 and the LGW 40.
  • FIG. 1 shows one UE for convenience of explanation, a plurality of UEs may be included. Further, the HeNB 10 forms a femto cell 12.
  • the femtocell indicates an area where the HeNB and the UE can be wirelessly connected.
  • the UE 30 moves from the femto cell area of the HeNB 10 to the femto cell area of the HeNB 20, the connection from the HeNB 10 to the HeNB 20 must be switched.
  • the LIPA handover procedure can be used in the HeNB 10 and the HeNB 25.
  • UE30 moves to HeNB20 during transmission / reception of data via HeNB10, even if it performs a LIPA handover procedure, data transmission / reception cannot be continued in HeNB20.
  • the HeNB 20 is a HeNB that does not support the LIPA handover procedure, the LIPA handover procedure cannot be started, and data transmission / reception cannot be continued with the communication device in the home network via the HeNB 20. .
  • the HeNB 25 is a HeNB that supports the LIPA handover procedure, the HeNB 25 can start the LIPA handover procedure and continue to transmit and receive data to and from the communication device in the home network via the HeNB 25.
  • the LIPA handover procedure can continue communication in the HeNB connected to the LGW 40 when data transmission / reception is performed in the HeNB connected to the LGW 40.
  • data transmission / reception can be continued when the HeNB is connected to the PGW 45.
  • the PGW 45 is an end point of a core network to which an eNB or the like is connected, and provides a connection with a PDN 70 (Packet Data Network).
  • the PDN 70 is a packet communication network and indicates, for example, the Internet.
  • the PGW 45 is an end point in the core network, but the LGW 40 is not an end point in the core network but an end point in the home network 90.
  • the UE 30 needs to establish a PDN connection and set up a bearer.
  • the UE 30 in order to access the home network 90, the UE 30 establishes a PIP connection for LIPA and uses a LIPA bearer. Need to be set. That is, the PGW 45 cannot access the home network 90, cannot establish a PIP connection for LIPA, and cannot set a LIPA bearer, but the LGW 40 can access the home network 90. Since the LIPA PDN connection can be established and the LIPA bearer can be set up, the LIPA handover procedure can be performed.
  • the handover procedure can be used in the HeNB 10, HeNB 20, and HeNB 25, but this embodiment relates to a LIPA handover procedure that can be used in the HeNB 10 and HeNB 25.
  • the PGW 45 is connected to the SGW 50 and the PDN 70, and functions as a gateway that connects the core network 80 and the PDN 70.
  • the PGW 45 receives data transmitted from the PDN 70 to the UE 30 from the PDN and transfers it to the SGW 50, and receives data transmitted from the UE 30 to the PDN 70 from the SGW 50 and transfers it to the PDN 70.
  • the PGW 45 establishes a PDN connection in order to provide a connection between the UE 30 and the PDN 70.
  • the SGW 50 is a service control apparatus that is connected to the LGW 70, the HeNB 10, the HeNB 20, and the HeNB 25 and performs packet transfer between the SGW 50 and the HeNB 20.
  • the MME 60 is a device that performs signaling, and is also a location management device that leads the location management of the UE 30 and the establishment procedure of the EPS bearer.
  • the EPS bearer is a logical path for transferring a user IP packet established between the HeNB (HeNB10, HeNB20 or HeNB25) and the LGW 40 for each UE. Note that the UE 30 can establish a plurality of EPS bearers.
  • the local home network (Local Home Network, LHN) 3 includes an LGW 40, a HeNB 10, a HeNB 20, a HeNB 25, and a UE 30.
  • the LHN 3 is connected to the home network 90 via the LGW 40.
  • the local home network indicates, for example, a home network or a corporate network, and is connected to the home network 90 using an optical fiber or ADSL.
  • the LGW 40 functions as a home gateway in the LHN 3 that transfers a packet when connecting to the HeNB 10, HeNB 20, or HeNB 25 connected to the LGW 40. Further, when the UE 30 connects to the home network, the LIPA PDN connection is established.
  • the PDN connection for LIPA is a logical path that connects between the LGW 40 and the UE 30.
  • the HeNB 10 forms a femtocell 12 and can accommodate the UE 30 as a 3GPP LTE base station apparatus.
  • HeNB20 can form the femtocell 22 and can accommodate UE30 as a base station apparatus of 3GPP LTE.
  • HeNB25 can form the femtocell 27 and can accommodate UE30 as a base station of 3GPP LTE.
  • UE 30 is a communication device equipped with a 3GPP LTE communication interface, and is connected to HeNB 10.
  • FIG. 2 is a functional configuration diagram illustrating the configuration of the HeNB 10 (that is, the source HeNB).
  • the HeNB 10 is configured to include a transmission / reception unit 110, an LTE radio communication unit 120, a storage unit 130, a handover request generation unit 140, a path switch request signal generation unit 150, and an antenna 125 in the control unit 100. .
  • the control unit 100 implements various processes in the HeNB 10 by reading and executing various programs stored in the storage unit 130. This process is executed using a device such as a CPU (not shown) built in the control unit 100.
  • the transmission / reception unit 110 is a functional unit used for receiving downlink data addressed to the UE 30 received from the LGW 40.
  • uplink data from the UE 30 is received via the LTE wireless communication unit 120 and transferred to the LGW 40.
  • the LTE radio communication unit 120 is a functional unit that performs radio communication with the UE 30 and accommodates the UE 30.
  • an external antenna 125 is connected to the LTE wireless communication unit 120.
  • the storage unit 130 is a functional unit that stores various programs and various data necessary for the operation of the Source HeNB 10.
  • the storage unit 130 includes, for example, a semiconductor memory, an HDD (Hard Disk Drive), or the like.
  • the storage unit 130 stores a Target HeNB table 132 for each UE, a neighbor HeNB relation table 134, and a handover candidate table 136.
  • the UE-specific Target HeNB table 132 is a table for managing a list of HeNBs extracted using the measurement report transmitted from the UE 30.
  • An example of the Target HeNB table 132 by UE is shown in FIG. In FIG. 3, using the result of the source HeNB receiving the measurement report, the received power values in the UE 30 calculated in large order based on the reference signal transmitted for each HeNB (HeNB 20 and HeNB 25 in this embodiment) ( HeNB is included in received power value 1> received power value 2).
  • the measurement report is a report from the UE 30 in which a received power value and the like are calculated using a reference signal from a HeNB that is close to the UE 30.
  • the neighbor HeNB relation table 134 is a table that is managed by determining whether or not the Target HeNB is a HeNB capable of LIPA handover using a handover request response transmitted from the Target HeNB.
  • An example of the neighbor HeNB relationship table 134 is shown in FIG.
  • the neighboring HeNB relation table 134 manages a HeNB list that can be handed over and a HeNB list that cannot be handed over.
  • the neighbor HeNB relationship table 134 illustrated in FIG. 4 it is possible to limit transmission of a LIPA handover request to a HeNB that cannot perform LIPA handover using a HeNB list that cannot perform LIPA handover. Therefore, it is possible to determine a HeNB that can efficiently perform a LIPA handover.
  • the neighboring HeNB relation table 134 may manage only a list of HeNBs that are not compatible with the LIPA handover procedure (a HeNB list that cannot be handed over), and may limit HeNBs that transmit LIPA handover requests.
  • the handover candidate table 136 is a table for managing HeNB candidates to be handed over by the UE 30.
  • An example of the handover candidate table 136 is shown in FIG.
  • the handover candidate table 136 is a table generated using the UE-specific Target HeNB table 132 and the neighboring HeNB relation table 136. Specifically, the HeNB candidate capable of LIPA handover is managed by excluding the HeNB included in the handover impossible HeNB list included in the neighbor HeNB relation table 136 from the Target HeNB table 132 for each UE.
  • FIG. 5A is a handover candidate table 136 generated from the UE-specific Target HeNB table 132 generated by the measurement report and the neighboring HeNB relation table 134 shown in FIG. 4A. Since the HeNB list that cannot be handed over in the neighbor HeNB relationship table 134 is blank, the HeNB is not deleted from the Target HeNB list by the measurement report.
  • FIG. 5B is a handover candidate table 136 generated from the UE-specific Target HeNB table 132 generated by the measurement report and the neighboring HeNB relation table 134 shown in FIG. 4B. That is, it is generated by deleting the HeNB (here, HeNB25) in the HeNB list that cannot be handed over.
  • the handover request generation unit 140 determines to execute the handover, and generates a handover request message for transmission to the Target HeNB.
  • FIG. 6A shows the format of the handover request message.
  • the handover candidate table 136 need not be created if the following functions can be realized. That is, the Source HeNB may select the Target HeNB (for example, the HeNB having the largest received power value) from the Target HeNB table 132 for each UE, check the neighboring HeNB relation table 132, and may not support the LIPA handover procedure. For example, it is only necessary that the target HeNB 132 for each UE can be selected again.
  • the Target HeNB for example, the HeNB having the largest received power value
  • the information on the conventional handover request is included in the default area, and the LGW address of the LGW connected to the Source HeNB and the information on the LIPA bearer applied by the Source HeNB in the optional area.
  • the LIPA bearer is a communication resource from the LGW 40 to the UE 30 via the HeNB 10.
  • communication resources from the LGW 40 to the UE 30 via the HeNB 25 can be set while maintaining the LIPA PDN connection.
  • the LIPA PDN connection may be included in the option area in the handover request message.
  • the PIP connection for LIPA indicates a logical path from the UE 30 to the LGW 40, and the LIPA bearer transmits / receives data to / from a communication device in the home network 90 that is set after the UE 30 establishes the PDN connection for LIPA. Indicates the communication resource when performing.
  • the X2 interface unit 150 performs transmission / reception with the source HeNB.
  • the X2 interface unit 150 can exchange data and control information with the HeNB.
  • FIG. 7 is a functional configuration diagram for explaining the configuration of the HeNB 20.
  • the HeNB 20 includes a control unit 200, a transmission / reception unit 210, an LTE wireless communication unit 220, an antenna 225, a storage unit 230, a handover request response generation unit 240, and an X2 interface unit 260.
  • the control unit 200 implements various processes in the HeNB 20 by reading and executing various programs stored in the storage unit 230.
  • the transmission / reception unit 210 is a functional unit used for receiving downlink data addressed to the UE 30 received from the LGW 40.
  • uplink data from the UE 30 is received via the LTE wireless communication unit 220 and transferred to the LGW 40. Further, the transmission / reception unit 210 can receive a path switch response from the LGW 40.
  • the LTE wireless communication unit 220 functions as a base station of the mobile phone system LTE and performs transmission / reception with the UE 30.
  • An external antenna 225 is connected to the LTE wireless communication unit 220.
  • the storage unit 230 is a functional unit in which various programs necessary for the operation of the HeNB 20 and various data are stored.
  • the storage unit 230 includes, for example, a semiconductor memory, an HDD (Hard Disk Drive), or the like.
  • the handover request response generation unit 240 receives the LIPA handover request and generates a handover request response.
  • the LIPA bearer and the LGW address (LIPN PDN connection) included in the LIPA handover request are not processed, and a handover request response is transmitted.
  • the HeNB 10 Source HeNB
  • the X2 interface unit 250 performs transmission / reception with the source HeNB.
  • the X2 interface unit 250 can exchange data and control information with the HeNB.
  • HeNB 25 (2nd Target HeNB)
  • the structure of HeNB25 (2nd Target HeNB) is demonstrated using FIG.
  • the HeNB 25 is different from the HeNB 20 described in FIG. 7 in that the HeNB 25 includes a LIPA handover request response generation unit 245 instead of the handover request response generation unit 240.
  • the same functional units as those of the HeNB 20 are denoted by the same reference numerals and description thereof is omitted.
  • the LIPA handover request response generation unit 245 is a functional unit that receives a LIPA handover request and generates a LIPA handover request response when the LIPA handover is possible.
  • FIG. 9 shows a LIPA handover request response message.
  • the address of the LGW 40 to which the HeNB 20 is connected as an additional region is included in the handover request response message in the default region.
  • the HeNB 10 (Source HeNB) having received the LIPA handover request response to the LGW address to which the HeNB 20 is connected determines that the HeNB 25 (second Target HeNB) can perform the LIPA handover.
  • the UE 30 includes a control unit 300, an LTE radio communication unit 310, and a storage unit 330.
  • the control unit 300 is a functional unit for controlling the entire UE 30.
  • the control unit 300 realizes various functions by reading and executing various programs stored in the storage unit 330, and is configured by, for example, a CPU (Central Process Unit).
  • a CPU Central Process Unit
  • the LTE wireless communication unit 320 is a functional unit for allowing the UE to communicate with each HeNB and LTE.
  • An external antenna 325 is connected to the LTE wireless communication unit 320.
  • the storage unit 330 is a functional unit in which various programs necessary for the operation of the UE 30 and various data are stored.
  • the storage unit 330 includes, for example, a semiconductor memory, an HDD (Hard Disk Drive), or the like.
  • the UE 30 include terminals such as a PDA (personal digital assistant) and a smart phone in addition to the mobile terminal device connected to each HeNB via a radio access interface.
  • terminals such as a PDA (personal digital assistant) and a smart phone in addition to the mobile terminal device connected to each HeNB via a radio access interface.
  • FIG. 11 is a diagram for explaining a functional configuration of the LGW 40.
  • the LGW 40 includes a control unit 400, a transmission / reception unit 410, a storage unit 430, and a PMIP processing unit 440.
  • the control unit 400 is a functional unit for controlling the entire LGW 40.
  • the control unit 400 realizes various functions by reading and executing various programs stored in the storage unit 430, and is configured by, for example, a CPU (Central Process Unit).
  • a CPU Central Process Unit
  • the transmission / reception unit 410 is wired to a router or a switch, and transmits / receives packets to / from the home access network 90 or the HeNB 10 or HeNB 20. For example, packets are transmitted and received by Ethernet (registered trademark) or the like generally used as a connection method to the home access network 90.
  • the storage unit 430 is a functional unit that stores programs, data, and the like necessary for various operations of the LGW 40, and includes, for example, a semiconductor memory.
  • the storage unit 430 stores binding information 432.
  • the binding information 432 is information used to determine a transmission path for transferring the communication data to the UE 30 when the LGW 40 receives the communication data divided into packets addressed to the UE 30.
  • An example of binding information is shown in FIG.
  • the binding information 432 includes the IP address prefix of the UE 30 (hereinafter referred to as “HNP (Home Network Prefix)”) and a transmission path to the LGW 40 (for example, “PMIP tunnel 1”). ) And are managed in association with each other.
  • HNP Home Network Prefix
  • PMIP tunnel 1 a transmission path to the LGW 40
  • IP address prefix “UE1_HNP1” of UE 30 and the transmission path “PMIP tunnel 1” are entries for a certain UE (for example, UE 30).
  • each UE is assigned a unique (unique) HNP, and is used to generate an IPv6 (IP version 6) address for the UE.
  • IPv6 IP version 6
  • the allocated HNP does not need to be IPv6, and may be IPv4 (IP version 4).
  • the PMIP processing unit 440 is a functional unit that establishes a transfer path (referred to as a PMIP tunnel) used between the LGW 40 and the HeNB 10, or the HeNB 20 and the HeNB 25.
  • FIG. 13 is a functional block diagram illustrating the configuration of the SGW 50.
  • the SGW 50 includes a control unit 500, a transmission / reception unit 510, a storage unit 530, and a path switch processing unit 540.
  • the control unit 500 is a functional unit for controlling the entire SGW 50.
  • the control unit 500 implements various functions by reading and executing various programs stored in the storage unit 530, and includes, for example, a CPU (Central Process Unit).
  • a CPU Central Process Unit
  • the transmission / reception unit 510 is wired to a router or a switch, and transmits / receives packets to / from the LGW 40 and the MME 60.
  • transmission / reception is performed by Ethernet (registered trademark) or the like generally used as a network connection method.
  • the storage unit 530 is a functional unit that stores programs, data, and the like necessary for various operations of the SGW 50, and includes, for example, a semiconductor memory.
  • the path switch processing unit 560 In response to the path switch request received by the transmission / reception unit 510, the path switch processing unit 560 performs path switch processing so as to change the data transmission destination to the HeNB 20 and the HeNB 25 included in the path switch request. Then, the transmission unit 510 transmits a path switch request response to the MME 60.
  • FIG. 14 is a diagram for explaining a functional configuration of the MME 60.
  • the MME 60 includes a control unit 600, a transmission / reception unit 610, and a storage unit 630.
  • the control unit 600 is a functional unit for controlling the entire MME 60.
  • the control unit 600 implements various functions by reading and executing various programs stored in the storage unit 630, and is configured by, for example, a CPU (Central Process Unit).
  • a CPU Central Process Unit
  • the transmission / reception unit 610 is a functional unit that is wired to a router or a switch and transmits and receives packets.
  • the transmission / reception unit 610 performs transmission / reception with the HeNB 10, HeNB 20, and HeNB 25 using, for example, Ethernet (registered trademark) generally used as a network connection method.
  • the storage unit 630 is a functional unit in which various programs necessary for the operation of the MME 60 and various data are stored.
  • the storage unit 630 includes, for example, a semiconductor memory, an HDD (Hard Disk Drive), or the like.
  • the storage unit 630 stores a subscription DB 632, an APN-IP address translation DB 634, and an EPS bearer context 636.
  • the subscription DB 632 “UE1” generated from the UE identifier (for example, IMSI (International Mobile Subscriber Identify)) for the UE 30 managed by the mobile communication system 1. ), A permitted CSG identifier list (for example, “CSG1”), and a connectable APN list (for example, “LIPA”) in association with each other.
  • UE identifier for example, IMSI (International Mobile Subscriber Identify)
  • IMSI International Mobile Subscriber Identify
  • a permitted CSG identifier list for example, “CSG1”
  • a connectable APN list for example, “LIPA”
  • the CSG (Closed Subscriber Group) identifier is a group identifier assigned to the HeNB 20, and whether or not the UE 30 can access the HeNB 20 is determined according to the permitted CSG identifier list of the subscription DB 632.
  • the same CSG identifier can be allocated to a plurality of HeNBs, and management of access authority can be integrated.
  • APN is an identifier for identifying a service in EPS.
  • whether or not the UE can access the HeNB 10 is determined based on whether or not the currently connected HeNB 10 is included in the permitted CSG identifier list, and further, an APN (for example, LIPA) used for accessing the local home network is included in the connectable APN list. It is determined by whether it is included.
  • an APN for example, LIPA
  • the APN-IP address conversion DB 634 is a DB that resolves the IP address of the LGW using the APN and the HeNB identifier.
  • the APN-IP address conversion DB 634 includes an APN (eg, “type 1 / LIPA connection”), an HeNB identifier (eg, “HeNB1”), and an LGW address (eg, “2001: 100”). : 200: 300 :: 2 ”) in association with each other.
  • the MME 60 switches the HeNB to which the UE 30 is connected (for example, when switching from the switching source HeNB 10 to the switching destination HeNB 20), the assigned HeNB identifier, and the local IP access APN.
  • the LGW address to which the switching target HeNB is connected is acquired by referring to the APN-IP address conversion DB 634.
  • the HeNB identifier is an identifier that uniquely identifies all HeNBs connected to the mobile communication system 1.
  • the EPS bearer context 636 manages the context (setting information) of the EPS bearer set for each UE.
  • FIG. 17 shows an example of the EPS bearer context 636.
  • the EPS bearer context 636 includes a UE identifier (for example, “UE1”), a connected APN (for example, “type 1 / LIPA connection”), and HoA (for example, “2001: 100: 200: 300 :: 5”). ), LGW address (for example, “2001: 100: 200: 300 :: 2”), HeNB address (for example, “2001: 100: 200: 300 :: 1”), and S1-TEID (for example, “TEID1 "), A cell ID (for example,” ECG1 (E-UTRAN Cell Global Identifier) 1 ”) and an EPS bearer ID (for example," EPS bearer 1 ”) are managed in association with each other.
  • UE1 UE identifier
  • APN for example, “type 1 / LIPA connection”
  • HoA for example, “2001: 100: 200: 300 :: 5”.
  • LGW address for example, “2001: 100: 200: 300 :: 2”
  • HeNB address for example, “2001: 100:
  • S1-TEID is an ID of a logical path established between HeNB 10 (or HeNB 20) and SGW 50, and S1-TEID is assigned to each EPS bearer.
  • the cell ID is an identifier that uniquely identifies a radio cell formed by each HeNB.
  • the cell ID and the HeNB identifier are the same.
  • the handover process procedure will be described. Specifically, the description starts from the state in which the connection state is established and communication is started between the HeNB 10 and the UE 30 (from the LGW 40 to the Source HeNB).
  • the Source HeNB is the HeNB 10 that has established the connection state
  • the Target HeNB (the first Target HeNB or the second Target HeNB) cannot maintain the connection state with the Source HeNB because the UE 30 cannot maintain the connection state.
  • a Target HeNB first Target HeNB or second Target HeNB
  • a Target HeNB that is a transmission destination and newly establishes a connection state by a handover procedure.
  • FIG. 18 shows a sequence diagram for performing a handover procedure from the source HeNB to the target HeNB.
  • the Source HeNB uses the neighbor HeNB relationship table 134 to determine the start of the handover procedure (S1002). Then, handover destination determination and HeNB list creation processing are executed (step S1004).
  • the source HeNB (HeNB 10 in the present embodiment) executed in step S1004 uses the LIPA handover candidate table 136 to determine the procedure for determining the start of the handover procedure.
  • the Source HeNB creates a Target HeNB table 132 for each UE by using a measurement report from the UE 30 (Step S2000).
  • the UE 30 creates a measurement report by measuring reference signals transmitted from neighboring HeNBs (including HeNB 10, HeNB 20, and HeNB 25).
  • a measurement report for the HeNB 10 is created by measuring a reference signal transmitted from the HeNB 10.
  • the UE 30 creates a measurement report for the HeNB 20 by measuring the reference signal transmitted from the HeNB 20 (first target HeNB). Furthermore, UE30 measures the reference signal transmitted from HeNB25, and produces the measurement report about HeNB25 (2nd Target HeNB).
  • the measurement report for example, information on the received power value of the reference signal is described.
  • the Source HeNB (HeNB 10) deletes the HeNB included in the non-handoverable HeNB list included in the neighbor HeNB relation table 134 from the Target HeNB candidates based on the measurement report created in Step S2000, and performs the LIPA handover in the UE 30.
  • a possible handover candidate table 136 is created (step S2002).
  • the handover candidate table 136 need not be created if the following functions can be realized. In other words, if the source HeNB selects the target HeNB (for example, the HeNB having the largest received power value) from the target heNB table 132 for each UE, confirms the neighboring HeNB table 132, and does not support the LIPA handover procedure. It suffices if the target HeNB 132 for each UE can be selected again. * the target HeNB 132 for each UE can be selected again.
  • the Source HeNB creates a Target HeNB list (handover candidate table 136) capable of LIPA handover in the UE 30, if it is determined that there is no Target HeNB, the handover procedure is terminated (step S2004; No).
  • the target HeNB candidate is not left as a result of removing the HeNB included in the handover impossible HeNB list in the neighboring HeNB table 134 from the target HeNB 132 for each UE.
  • the handover procedure is terminated.
  • the source HeNB selects a target heNB capable of LIPA handover in the UE 30 (step S2006).
  • the Target HeNB there are various methods for selecting the Target HeNB. For example, the highest received power value reported in the measurement report from the UE 30 from the Target HeNB list (handover candidate table 136) capable of LIPA handover in the UE 30 can be considered. A high HeNB can be selected.
  • the Source HeNB transmits a handover request to the Target HeNB selected in Step S2006 (Step S2008).
  • the handover request transmitted by the Source HeNB includes at least the LGW address to which the Source HeNB is connected and information on the LIPA bearer as shown in FIG. 6 (a).
  • a PDN connection for LIPA may be included as an option.
  • the source HeNB includes the LGW address and the LIPA bearer in the handover request option, so that the HeNB not supporting the LIPA handover procedure is handed over without being involved in the LGW address and the LIPA bearer.
  • a request response can be sent.
  • the Target HeNB does not participate in the LIPA PDN connection.
  • the LGW address and the information of the LIPA bearer are extracted (including the LIPA PDN connection when the LIPA PDN connection is included in the handover request option). It is possible to send back a handover request response in the LIPA handover procedure.
  • this handover request message from the source HeNB, it is possible not only to return a response to the start of the conventional handover procedure, but also to check whether it has a function corresponding to the LIPA handover procedure. Become.
  • the Target HeNB that has received the handover request from the Source HeNB returns a handover request response, and the Source HeNB receives the handover request response (Step S2010).
  • Target HeNB that does not support the LIPA handover procedure
  • the first Target HeNB HeNB (HeNB20)
  • LIPA LIPA
  • the handover request response is returned without processing the PDN connection for LIPA
  • the LIPA handover information elements (LGW address, LIPA bearer, LIPA PDN connection) are included in the optional part of the handover request transmitted from the Source HeNB, the Target HeNB that does not support the LIPA handover procedure Without being involved in the information element of the LIPA handover included in the optional part, it can be processed as a conventional handover procedure and a handover request response can be transmitted to the Source HeNB.
  • the Target HeNB can notify the Source HeNB that it does not support the LIPA handover procedure.
  • the Target HeNB that has received the handover request from the Source HeNB is a HeNB that supports the LIPA handover procedure (for example, in the present embodiment, the second Target HeNB (HeNB25))
  • the second Target HeNB HeNB25
  • an optional part of the handover request The information about the LGW address and the LIPA bearer included in is extracted, and a handover request response is returned.
  • the handover request response includes the LGW address to which the Target HeNB is connected.
  • the Source HeNB includes the LGW address and the LIPA bearer (the PDN connection for LIPA) in the handover request option, so that the Target HeNB corresponding to the LIPA handover procedure can include the LGW address and , LIPA bearer information can be extracted, and a handover request response in the LIPA handover procedure can be returned.
  • LIPA bearer the PDN connection for LIPA
  • the Target HeNB can notify the Source HeNB that the LIPA handover procedure is supported.
  • the Source HeNB can notify the Source HeNB that it does not support the LIPA handover procedure by transmitting the information element of the LIPA handover in the option of the handover request message. Further, the Target HeNB can notify the Source HeNB that the Target HeNB is compatible with the handover procedure by transmitting a handover request response in the LIPA handover procedure.
  • the exchange of the handover request and the handover request response between the source HeNB and the target HeNB described above has a function corresponding to the LIPA handover procedure as well as returning a response to the start of the conventional handover procedure. It is possible to check whether or not
  • the Source HeNB that has received the handover request response (Step S2010; Yes) checks the LGW address of the Target HeNB included in the handover request response (Step S2012).
  • step S2014 if the LGW address is not included in the handover request response (step S2014; No), it is added to the neighboring HeNB relation table as a HeNB that cannot be handed over (step S2016).
  • the Source HeNB determines the HeNB included in the handover request as the Target HeNB and ends this procedure.
  • Step S2014 when it is determined in Step S2014 that the LGW address is included in the handover request response (Step S2014; Yes), it may be confirmed whether the Source HeNB and the Target HeNB are connected to the same LGW.
  • whether the source HeNB and the target HeNB are connected to the same LGW may be confirmed by checking whether the LGW address of the LGW to which the source HeNB is connected and the LGW address of the LGW to which the target HeNB is connected. If the LGW address of the LGW connected to the Source HeNB and the LGW address of the LGW connected to the Target HeNB are the same, it is determined that the Source HeNB and the Target HeNB are connected to the same LGW, and the Target HeNB is connected to the LIPA handover procedure. May be determined to be possible.
  • the Source HeNB and the Target HeNB are connected to different LGWs, they may be added to the neighboring HeNB relation table 134 as HeNBs that cannot be handed over (step S2016).
  • HeNB connected to said different HeNB may be managed in the neighbor HeNB relation table 134, and may be managed as another table.
  • the process of S2016 when the process of S2016 is performed, the process returns to the process of step S2000 and the above process is repeated. In this process, this process is repeated until the LGW address is included in the handover request response from the Target HeNB (or whether the Source HeNB and the Target HeNB are connected to the same LGW address) or there is no Target HeNB candidate.
  • the Target HeNB table 132 for each UE in FIG. 3 as a result of the measurement report from the UE 30, the HeNB 20 and the HeNB 25 are included. At this time, it is assumed that the result of the measurement report from the UE does not change with time, and the managed contents of the UE-specific Target HeNB table 132 are the same.
  • the handover candidate table 136 may not be created as long as the Target HeNB candidates can be limited from the Target HeNB table 132 for each UE by using the neighboring HeNB relation table 134.
  • the source HeNB selects the target HeNB (for example, the HeNB having the largest received power value) from the target heNB table 132 for each UE, confirms the neighboring HeNB table 132, and does not support the LIPA handover procedure. It suffices if the target HeNB 132 for each UE can be selected again.
  • the neighbor HeNB relation table 134 in FIG. 4A shows an initial state of the neighbor HeNB relation table. Since the HeNB 20 is not a HeNB that supports the LIPA handover procedure, the neighbor HeNB relationship table 134 in FIG. 4B does not include the LGW address in the handover request response in step S2014 in FIG. In step S2016, the HeNB 25 is added to the neighboring HeNB relation table 134 as a request for handover not possible.
  • the handover candidate table 136 in FIG. 5A is the handover candidate table 136 initially created in step S2002, and the neighboring HeNB table 134 shows the handover candidate table 136 created in the initial state of FIG. 4A.
  • FIG. 3 since the Target HeNB table 132 by UE in FIG. 3 includes the HeNB 20 and the HeNB 25, and the neighbor HeNB relation table in FIG. 4A does not include anything, FIG.
  • the handover candidate table 136 includes the HeNB 20 and the HeNB 25.
  • the HeNB 20 is selected as the Target HeNB, but since the HeNB 20 does not support the LIPA handover procedure, the HeNB 20 is added to the handover impossible list in the neighboring HeNB relation table 134 in step S2016.
  • the handover candidate table 136 created in a state where the HeNB 20 is included in the handover impossible list in the neighboring HeNB relation table 134 in FIG.
  • the HeNB 20 and the HeNB 25 are included in the Target HeNB table 132 for each UE in FIG. 3, the HeNB 20 is included in the handover impossible list in the neighboring HeNB relation table 134 in FIG. 4B.
  • the handover candidate table 136 in FIG. 5B only the HeNB 25 is included. Since the HeNB 25 can perform the LIPA handover procedure, the HeNB 25 is selected as the Target HeNB.
  • the Source HeNB does not create the handover candidate table 136
  • the Source HeNB excludes the HeNB 20 included in the handover impossible list in the neighboring HeNB table 134 from the Target HeNB table 132 for each UE, and the remaining Target HeNB candidates
  • the HeNB 25 is selected as the Target HeNB. Since the HeNB 25 is a HeNB corresponding to the LIPA handover procedure, the procedure in FIG. 19 can be completed.
  • the Source HeNB transmits an RRC connection reconfiguration notification to the UE 30 (S1006).
  • the RRC connection reconfiguration notification includes an identifier indicating the second Target HeNB.
  • the UE 30 performs RRC connection reconfiguration based on the information of the second Target HeNB included in the RRC connection reconfiguration notification, confirms that the setting with the second Target HeNB has been completed, and then sends the second Target HeNB to the second Target HeNB.
  • An RRC connection reconfiguration completion notification is transmitted (S1008).
  • the second Target HeNB that has received the RRC connection reconfiguration completion notification transmits a path switch request to the MME 60 (S1010).
  • the request for the path switch includes information on the UE for switching the HeNB, APN, information on the source HeNB serving as the path switch source, information on the second Target HeNB serving as the path switch destination, information on the LGW address to which the Target HeNB is connected, and information on the LIPA bearer.
  • a PIP connection for LIPA may be included.
  • the MME 60 that has received the path switch request from the second Target HeNB changes the HeNB address of the EPS bearer context 636 corresponding to the information about the UE and the information about the LIPA bearer included in the path switch request from the address of the Source HeNB to the address of the second Target HeNB. change. Subsequently, a bearer change request is transmitted to the SGW 50 (S1012).
  • the EPS bearer context may be changed in association with the PIP connection for LIPA.
  • the MME 60 includes, in the bearer change request, information on the UE that switches the HeNB (LIPA bearer), an APN, an LGW address to which the Source HeNB is connected, information on the Source HeNB that is the bearer change source, and information on the second Target HeNB that is the bearer change destination.
  • LIPA bearer information on the UE that switches the HeNB
  • APN Address Translation
  • LGW address to which the Source HeNB is connected
  • information on the Source HeNB that is the bearer change source information on the second Target HeNB that is the bearer change destination.
  • information on the PDN connection for LIPA may be included.
  • the SGW50 which received the bearer change request transmits a bearer change request to LGW40 (S1014).
  • the SGW 50 includes, in the bearer change request, information on the UE that switches the HeNB, an APN, an LGW address to which the Source HeNB is connected, information on the Source HeNB that is the bearer change source, and information on the second Target HeNB that is the bearer change destination.
  • information on the PDN connection for LIPA may be included.
  • the LGW 40 that has received the bearer change request from the SGW 50 changes the data destination to the UE 30 from the source HeNB to the second target HeNB and changes the LIPA bearer necessary for data transmission / reception at the same time.
  • the LGW 40 that has changed the data destination and the bearer respectively transmits a bearer change response to the SGW 50 (S1016).
  • the SGW 40 that has received the bearer change response from the LGW 40 confirms that the path change and the LIPA bearer change have been completed from the LGW 40 to the HeNB 20, and transmits a bearer change response to the MME 60 (S1018).
  • the LGW 40 transmits a path switch response indicating that the path switch has been completed to the second Target HeNB (S1020).
  • the second Target HeNB that has received the path switch response from the LGW 40 confirms that the path has been changed from the Source HeNB to the second Target HeNB, and transmits a resource release notification to the Source HeNB (S1022).
  • the Source HeNB detects whether the Target HeNB is compatible with the LIPA handover procedure by transmitting a handover request including an information element indicating the LIPA handover procedure, and the neighboring HeNB relation table. And unnecessary transmission of handover requests can be suppressed using the neighbor HeNB relationship table.
  • the Source HeNB detects whether the Target HeNB is a HeNB corresponding to the LIPA handover procedure by transmitting a new information element indicating that the procedure is a LIPA handover procedure in the handover request. Can do.
  • Target HeNB can indicate that it does not support the LIPA handover procedure by receiving the handover request from the Source HeNB and transmitting a conventional handover request response.
  • the Source HeNB can receive the conventional handover request response from the Target HeNB, and can detect that the Target HeNB is an HeNB that does not support the LIPA handover procedure.
  • the Source HeNB detects that the Target HeNB is an HeNB that does not support the LIPA handover procedure, and can be classified as a HeNB that does not support the LIPA handover procedure in the neighboring HeNB relation table.
  • the Target HeNB can indicate that it corresponds to the LIPA handover procedure by receiving the handover request from the Source HeNB and transmitting a handover request response in the LIPA handover procedure.
  • the Source HeNB can detect that the Target HeNB is a HeNB corresponding to the LIPA handover procedure by receiving the handover request response in the LIPA handover procedure from the Target HeNB.
  • the Source HeNB detects that the Target HeNB is a HeNB corresponding to the LIPA handover procedure, and can be classified as a HeNB corresponding to the LIPA handover procedure in the neighboring HeNB relation table.
  • the Source HeNB transmits a handover request to the HeNB that does not support the LIPA handover procedure by using the neighbor HeNB relationship table in which the HeNB that does not support the LIPA handover procedure and the HeNB that supports the LIPA handover procedure are classified in the neighbor HeNB related table. By suppressing this, an efficient LIPA handover procedure can be started.
  • the home network 90 may be a broadband access network that allows access to the Internet or the like.
  • the LGW 40 in the mobile communication system 1 is an access control device, and not only is connected to a home network such as a home network, but can also transmit / receive data transmitted from the UE 30 to the broadband access network.
  • SIPTO Select IP Traffic Offload, access This is called selective traffic offload.
  • the UE 30 uses the SIPTO PDN connection for connection from the HeNB to the broadband access network.
  • the UE 30 transmits and receives data to and from the communication device in the broadband access network via the LGW 40.
  • UE30 needs to set LGW40 and SIPTO bearer, when transmitting / receiving data with the communication apparatus in a broadband access network.
  • the Source HeNB when the mobile communication system 1 is replaced with a broadband access network instead of the home network 90, the Source HeNB includes the LGW address and the SIPTO bearer in the handover request options in the SIPTO handover procedure, so that the Target HeNB. However, it can detect whether it corresponds to a SIPTO handover procedure, and can build a neighbor HeNB relation table, and can suppress transmission of an unnecessary handover request using the neighbor HeNB relation table.
  • the SIPTO PDN connection may be included in the handover request option.
  • the Source HeNB includes a new information element (LGW address and SIPTO bearer (PTO connection for SIPTO)) indicating that it is a SIPTO handover procedure in the handover request, and transmits it in the optional part, so that the Target HeNB is SIPTO. It is possible to detect whether the HeNB is compatible with the handover procedure.
  • LGW address and SIPTO bearer PTO connection for SIPTO
  • Target HeNB can indicate that it does not support the SIPTO handover procedure by receiving the handover request from the Source HeNB and transmitting a conventional handover request response.
  • the Source HeNB can receive the conventional handover request response from the Target HeNB and detect that the Target HeNB is an HeNB that does not support the SIPTO handover procedure.
  • the Source HeNB can detect that the Target HeNB is a HeNB that does not support the SIPTO handover procedure, and can classify it as a HeNB that does not support the SIPTO handover procedure in the neighboring HeNB relation table.
  • the Target HeNB can indicate that it corresponds to the SIIPTO handover procedure by receiving the handover request from the Source HeNB and transmitting a handover request response in the SIPTO handover procedure.
  • the Source HeNB can detect that the Target HeNB is a HeNB corresponding to the SIPTO handover procedure by receiving a handover request response in the SIPTO handover procedure from the Target HeNB.
  • the Source HeNB can detect that the Target HeNB is a HeNB corresponding to the SIPTO handover procedure, and can be classified as a HeNB corresponding to the SIPTO handover procedure in the neighboring HeNB relation table.
  • the Source HeNB transmits a handover request to the HeNB that does not support the SIPTO handover procedure by using the neighboring HeNB relationship table in which the HeNB that does not support the SIPTO handover procedure and the HeNB that supports the SIPTO handover procedure are classified in the neighbor HeNB related table. By suppressing this, an efficient SIPTO handover procedure can be started.
  • a handover request transmitted from the source HeNB is transmitted to the MME 60.
  • the handover procedure can be started by exchanging control information between HeNBs.
  • the second embodiment it can be used when control information cannot be exchanged between HeNBs.
  • a handover procedure will be described. The processing described above will be described with reference to FIG.
  • the Source HeNB uses the measurement report periodically transmitted from the UE 30 to determine the start of the LIPA handover procedure (S3002).
  • the method described in the first embodiment can be used.
  • information on the received power value included in the measurement report can be used.
  • the Source HeNB determines a handover destination and creates a HeNB list (S3003).
  • S3003 is a process of determining a handover destination and creating a neighbor HeNB relationship table in the processes from S3004 to S3014 surrounded by a dotted line.
  • the procedure in which the source HeNB determines the handover destination using the neighbor HeNB relation table can similarly use the procedure described in the first embodiment between the source HeNB and the target HeNB. .
  • control information since control information cannot be directly exchanged between the source HeNB and the target HeNB, control information is exchanged via the MME 60 (processing from S3004 to S3014 in FIG. 20).
  • the procedure in which the Source HeNB exchanges a handover request and a handover request response with the Target HeNB via the MME 60 is as follows. First, the Source HeNB transmits a handover request to the MME 60 (S3004).
  • the handover request transmitted by the Source HeNB as shown in the handover request message in FIG. 6B, the LGW address to which the Source HeNB is connected, information on the LIPA bearer, and information on the Target HeNB are optional. Included.
  • the PIP connection for LIPA may be included as an option in the handover request transmitted by the Source HeNB.
  • the handover request is stopped and the LIPA is stopped. Search for HeNBs that can be handed over.
  • the MME 60 that has received the handover request from the Source HeNB includes the information related to the UE 30 and the information related to the LIPA bearer included in the handover request and transmits them to the SGW 50 (S3006).
  • the MME 60 includes, in the session generation request, information on the UE 30 that switches the source HeNB, information on the source HeNB that is the bearer change source, and information on the target HeNB that is the bearer change destination.
  • the SGW 50 that has received the session generation request from the LGW 40 confirms that the path change and bearer change have been completed from the LGW 40 to the HeNB 20, and transmits a session generation request to the MME 60 (S3008).
  • the MME 60 that has received the session generation request from the SGW 40 transmits a handover request to the Target HeNB notified in 3004 (S3010).
  • the handover request transmitted by the MME 60 information on the LGW address and the LIPA bearer to which the Source HeNB is connected is included in the options as shown in the handover request message in FIG.
  • the LIPA PDN connection may be included as an option in the handover request.
  • Target HeNB that has received the handover request from the MME 60 is a HeNB that does not support the LIPA handover procedure (for example, the HeNB 20)
  • the LGW address included in the optional part of the handover request and information on the LIPA bearer are ignored.
  • a handover request response is returned.
  • the Target HeNB that has received the handover request from the MME 60 is a HeNB that supports the LIPA handover procedure (for example, HeNB25)
  • the information about the LGW address and the LIPA bearer included in the optional part of the handover request is extracted.
  • a handover request response is returned (S3012).
  • the handover request response includes the LGW address to which the Target HeNB is connected as shown in FIG.
  • the response to the handover request transmitted by the Target HeNB corresponding to the LIPA handover procedure is not limited to the handover request response, and may be a signal indicating that the LIPA handover procedure is supported, for example. .
  • the MME 60 that has received the handover request response including the same LGW address as the source HeNB transmits a handover request response to the source HeNB (S3014).
  • the handover request response transmitted here is the same handover request response as the handover request response transmitted from the Target HeNB to the MME 60. That is, in the case of Target HeNB that does not support the LIPA handover procedure, a handover request response is transmitted without including the LGW address, and in the case of Target HeNB that supports the LIPA handover procedure, the LGW address is included. A handover request response is transmitted.
  • the handover request and the handover request response are transmitted between the Source HeNB and the Target HeNB by transferring the handover request and the handover request response to the Source HeNB and Target HeNB (HeNB20 or HeNB25), respectively, via the MME 60. can do. That is, determination of a handover destination and creation of a handover candidate table shown in FIG. 19 can be performed between the source HeNB and the target HeNB.
  • the MME 60 transmits a handover command to the source HeNB (S3016).
  • the handover command may be transmitted instead of transmitting the handover request response transmitted in S3016. That is, the handover command response information element and the LGW address to which the Target HeNB is connected may be included in the handover command.
  • the Source HeNB that has received the handover command transmits the handover command to the UE 30 (S3018).
  • the UE 30 that has received the handover command disconnects from the source HeNB and establishes a connection with the target HeNB.
  • the Source HeNB confirms that the connection with the UE 30 has been disconnected, and transmits a handover notification to the MME 60 (S3020).
  • the handover notification includes information for identifying the UE.
  • the MME 60 that has received the handover notification from the Source HeNB changes the information about the UE included in the handover notification and the HeNB address of the EPS bearer context 636 corresponding to LIPA from the Source HeNB address to the Target HeNB address. Subsequently, the MME 60 transmits a bearer change request to the SGW 50 (S3022).
  • the MME 60 includes, in the bearer change request, information on the UE that switches the HeNB (information on the LIPA bearer), APN (LIPA), information on the source HeNB that is the bearer change source, and information on the target HeNB that is the bearer change destination.
  • the MME 60 may include the PDN connection for LIPA in the session generation request.
  • the SGW50 which received the bearer change request transmits a bearer change request to LGW40 (S3024).
  • the SGW 50 includes, in the bearer change request, information on the UE for switching the HeNB (LIPA bearer), APN, information on the source HeNB serving as the bearer change source, and information on the target HeNB serving as the bearer change destination.
  • the MME 60 may include the PDN connection for LIPA in the session generation request.
  • the LGW 40 that has received the bearer change request from the SGW 50 changes the data destination for the UE 30 from the Source HeNB to the Target HeNB, and simultaneously changes the bearer necessary for data transmission / reception.
  • the LGW 40 that has changed the data destination and the bearer transmits a bearer change response to the SGW 50 (S3026).
  • the SGW 40 that has received the bearer change response from the LGW 40 confirms that the path change and bearer change have been completed from the LGW 40 to the HeNB 20, and transmits a bearer change response to the MME 60 (S3028).
  • the LGW 40 confirms that the path and bearer have been changed from the source HeNB to the target HeNB, and transmits a path switch response to the target HeNB (S3030).
  • the Target HeNB that has received the path switch response confirms that the communication path with the LGW has been established, and transmits a resource release notification to the Source HeNB (S3032).
  • the Source HeNB receives the resource release notification from the Target HeNB and grasps that the LIPA handover procedure has been completed.
  • the Source HeNB detects whether the Target HeNB is compatible with the LIPA handover procedure by transmitting a handover request including an information element indicating the LIPA handover procedure, and the neighboring HeNB relation table. And unnecessary transmission of handover requests can be suppressed using the neighbor HeNB relationship table.
  • the Source HeNB detects whether the Target HeNB is a HeNB corresponding to the LIPA handover procedure by transmitting a new information element indicating that the procedure is a LIPA handover procedure in the handover request. Can do.
  • Target HeNB can indicate that it does not support the LIPA handover procedure by receiving the handover request from the Source HeNB and transmitting a conventional handover request response.
  • the Source HeNB can receive the conventional handover request response from the Target HeNB, and can detect that the Target HeNB is an HeNB that does not support the LIPA handover procedure.
  • the Source HeNB can detect that the Target HeNB is a HeNB that does not support the LIPA handover procedure, and can classify it as a HeNB that does not support the LIPA handover procedure in the neighboring HeNB relation table.
  • the Target HeNB can indicate that it corresponds to the LIPA handover procedure by receiving the handover request from the Source HeNB and transmitting a handover request response in the LIPA handover procedure.
  • the Source HeNB can detect that the Target HeNB is a HeNB corresponding to the LIPA handover procedure by receiving the handover request response in the LIPA handover procedure from the Target HeNB.
  • the Source HeNB detects that the Target HeNB is a HeNB corresponding to the LIPA handover procedure, and can be classified as a HeNB corresponding to the LIPA handover procedure in the neighboring HeNB relation table.
  • the Source HeNB transmits a handover request to the HeNB that does not support the LIPA handover procedure by using the neighbor HeNB relationship table in which the HeNB that does not support the LIPA handover procedure and the HeNB that supports the LIPA handover procedure are classified in the neighbor HeNB related table. By suppressing this, an efficient LIPA handover procedure can be started.
  • the program that operates in each device is a program that controls the CPU or the like (a program that causes a computer to function) so as to realize the functions of the above-described embodiments.
  • Information handled by these devices is temporarily stored in a temporary storage device (for example, RAM) at the time of processing, then stored in various ROM or HDD storage devices, and read and corrected by the CPU as necessary. • Writing is performed.
  • a recording medium for storing the program a semiconductor medium (for example, ROM, a non-volatile memory card, etc.), an optical recording medium / a magneto-optical recording medium (for example, DVD (Digital Versatile Disc), MO (Magneto Optical) Disc), MD (Mini Disc), CD (Compact Disc), BD, etc.), magnetic recording medium (eg, magnetic tape, flexible disk, etc.), etc.
  • a semiconductor medium for example, ROM, a non-volatile memory card, etc.
  • an optical recording medium / a magneto-optical recording medium for example, DVD (Digital Versatile Disc), MO (Magneto Optical) Disc), MD (Mini Disc), CD (Compact Disc), BD, etc.
  • magnetic recording medium eg, magnetic tape, flexible disk, etc.
  • the program when distributing to the market, can be stored in a portable recording medium for distribution, or transferred to a server computer connected via a network such as the Internet.
  • a server computer connected via a network such as the Internet.
  • the storage device of the server computer is also included in the present invention.
  • LSI Large Scale Integration
  • Each functional block of each device may be individually chipped, or a part or all of them may be integrated into a chip.
  • the method of circuit integration is not limited to LSI, and may be realized by a dedicated circuit or a general-purpose processor.
  • integrated circuit technology that replaces LSI appears due to progress in semiconductor technology, it is of course possible to use an integrated circuit based on this technology.
  • SYMBOLS 1 Mobile communication system 3 Local home network 90 Home network 10 HeNB DESCRIPTION OF SYMBOLS 100 Control part 110 Transmission / reception part 120 LTE radio

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
PCT/JP2012/079474 2011-11-17 2012-11-14 ホーム基地局装置、移動通信システム、移動端末装置及び位置管理装置 WO2013073556A1 (ja)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN201280056589.6A CN103947257A (zh) 2011-11-17 2012-11-14 家庭基站装置、移动通信系统、移动终端装置以及位置管理装置
US14/358,063 US20140321429A1 (en) 2011-11-17 2012-11-14 Home base station device, mobile communication system, mobile terminal device, and position management device
EP12850142.6A EP2782393A4 (en) 2011-11-17 2012-11-14 HOME BASIS STATION, MOBILE COMMUNICATION SYSTEM, MOBILE DEVICE AND POSITION MANAGEMENT DEVICE

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2011251282A JP5889607B2 (ja) 2011-11-17 2011-11-17 ホーム基地局装置、位置管理装置及び移動通信システム
JP2011-251282 2011-11-17

Publications (1)

Publication Number Publication Date
WO2013073556A1 true WO2013073556A1 (ja) 2013-05-23

Family

ID=48429612

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2012/079474 WO2013073556A1 (ja) 2011-11-17 2012-11-14 ホーム基地局装置、移動通信システム、移動端末装置及び位置管理装置

Country Status (5)

Country Link
US (1) US20140321429A1 (enrdf_load_stackoverflow)
EP (1) EP2782393A4 (enrdf_load_stackoverflow)
JP (1) JP5889607B2 (enrdf_load_stackoverflow)
CN (1) CN103947257A (enrdf_load_stackoverflow)
WO (1) WO2013073556A1 (enrdf_load_stackoverflow)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013001610A1 (ja) * 2011-06-28 2013-01-03 京セラ株式会社 通信制御方法及びホーム基地局
KR20140050641A (ko) * 2011-07-01 2014-04-29 인터디지탈 패튼 홀딩스, 인크 선택적 인터넷 프로토콜(ip) 트래픽 오프로드(sipto) 및 로컬 ip 액세스(lipa) 이동성을 위한 방법 및 장치
CN105453644A (zh) * 2013-06-11 2016-03-30 日本电气株式会社 通信系统、基站、网关装置、基站控制方法和网关装置控制方法
EP3022973A4 (en) * 2013-07-19 2017-06-21 Appcard, Inc. Methods and apparatus for cellular-based identification of individuals within a vicinity
CN105704760B (zh) * 2014-11-26 2019-09-17 电信科学技术研究院 一种进行数据包传输的方法、设备和系统

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2773510C (en) * 2009-09-18 2015-06-23 Nec Corporation Communication system and communication control method
HUE032228T2 (en) * 2009-12-15 2017-09-28 Wireless Future Tech Inc Methods, apparatuses and related computer-readable storage medium for deciding on a signaling scheme for handover
US9398517B2 (en) * 2010-01-11 2016-07-19 Blackberry Limited System and method for enabling discovery of local service availability in local cellular coverage
WO2011129070A1 (en) * 2010-04-16 2011-10-20 Panasonic Corporation Handover method, handover system, and apparatus for a ue attaching to a local ip network
KR101772159B1 (ko) * 2011-05-16 2017-08-29 삼성전자 주식회사 이동통신시스템에서 ｌｉｍｏｎｅｔ 지원시 세션 연속 지원을 결정하는 장치 및 방법.
WO2013001610A1 (ja) * 2011-06-28 2013-01-03 京セラ株式会社 通信制御方法及びホーム基地局
US9237487B2 (en) * 2011-06-28 2016-01-12 Kyocera Corporation Communication control method and home base station
CN103096401B (zh) * 2011-10-31 2016-06-22 华为技术有限公司 切换承载的方法、家庭基站网关和家庭基站

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI: "LHN identification using L-GW@CN address", 3GPP, S2-112783, 20 May 2011 (2011-05-20), pages S2 - 112547, XP050525670 *
INTEL CORPORATION: "LIPA Deactivation", 3GPP, S2-113142, 15 July 2011 (2011-07-15), XP050548463 *
PANASONIC: "LIPA mobility support with standalone LGW", 3GPP, S2-111769, 25 February 2011 (2011-02-25), pages S2 - 110682, XP050524667 *

Also Published As

Publication number Publication date
JP5889607B2 (ja) 2016-03-22
EP2782393A4 (en) 2015-08-26
US20140321429A1 (en) 2014-10-30
EP2782393A1 (en) 2014-09-24
CN103947257A (zh) 2014-07-23
JP2013106334A (ja) 2013-05-30

Similar Documents

Publication Publication Date Title
JP6837447B2 (ja) 小型基地局環境で情報インタラクションを行う方法、及び基地局
JP5801430B2 (ja) フェムトセルを含む無線通信ネットワークにおけるローカルｉｐアクセスサポート方法及び装置
JP5898907B2 (ja) Ｘ２インタフェース管理方法、ハンドオーバ方法及び装置
JP5704370B2 (ja) 基地局間のハンドオーバーを管理するための方法及び装置
WO2011129273A1 (ja) 位置管理装置、パケットゲートウェイ装置、移動通信システム、移動局装置及び移動通信方法
US20180270741A1 (en) Terminal device, base station device, mme, and communication control method
CN103108303B (zh) 支持组移动的方法及设备
CN111641986B (zh) 一种通信方法、设备和计算机设备
CN103686932A (zh) 一种保证本地ip接入业务正确建立的方法
JP2013541231A (ja) 基地局装置、移動管理エンティティ、システム、方法及びコンピュータプログラム
KR20100119349A (ko) 펨토 셀을 포함하는 무선 통신 네트워크에서의 로컬 ｉｐ 액세스 지원 방법 및 장치
CN102740404A (zh) 一种保证本地ip接入业务正确建立的方法
JP5889607B2 (ja) ホーム基地局装置、位置管理装置及び移動通信システム
JP2015146654A (ja) 移動元基地局、移動先基地局、移動局、通信方法
CN108307521A (zh) 本地ip接入业务实现方法及装置、系统、家庭演进基站
CN106162774B (zh) 跨MeNB切换方法、装置及基站
JPWO2014054610A1 (ja) 移動通信システム、第１の基地局装置、移動局装置及び移動通信システムの通信方法
US20150146533A1 (en) Mobile communication system, home base station device, position managing device, communication method, and mobile station device
CN102892162A (zh) 一种宿主基站、中断节点设备及增强路径转换的方法
CN103621140A (zh) 通信控制方法和家庭基站
CN101932072A (zh) 无线接入网络信息的传递方法与装置
WO2014054644A1 (ja) 移動通信システム、第２の基地局装置、移動局装置及び移動通信システムの通信方法
CN102118734B (zh) 一种可实现无固定锚点切换的Wimax系统及其切换方法
CN103024838B (zh) 一种支持中继节点服务网关重定位的方法
WO2014050607A1 (ja) 移動通信システム、位置管理装置、ホーム基地局装置、移動局装置及び移動通信システムにおける通信方法

Legal Events

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

Ref document number: 12850142

Country of ref document: EP

Kind code of ref document: A1

REEP Request for entry into the european phase

Ref document number: 2012850142

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 14358063

Country of ref document: US

Ref document number: 2012850142

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE