WO2017072905A1 - Noeud relais, système de communication sans fil et procédé de communication dans un système de communication sans fil - Google Patents

Noeud relais, système de communication sans fil et procédé de communication dans un système de communication sans fil Download PDF

Info

Publication number
WO2017072905A1
WO2017072905A1 PCT/JP2015/080519 JP2015080519W WO2017072905A1 WO 2017072905 A1 WO2017072905 A1 WO 2017072905A1 JP 2015080519 W JP2015080519 W JP 2015080519W WO 2017072905 A1 WO2017072905 A1 WO 2017072905A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
message
henb
connection
relay node
Prior art date
Application number
PCT/JP2015/080519
Other languages
English (en)
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 PCT/JP2015/080519 priority Critical patent/WO2017072905A1/fr
Priority to JP2017547273A priority patent/JP6443561B2/ja
Publication of WO2017072905A1 publication Critical patent/WO2017072905A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/24—Cell structures
    • H04W16/26—Cell enhancers or enhancement, e.g. for tunnels, building shadow
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/20—Interfaces between hierarchically similar devices between access points

Definitions

  • the technology described in this specification relates to a relay node, a wireless communication system, and a communication method in the wireless communication system.
  • LTE Long ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ Term Evolution
  • 3GPP Third Generation Partnership Project
  • X2 GW that aggregates multiple X2 interfaces
  • X2 GW For convenience.
  • X2 connection an increase in load due to concentration of connections using the X2 interface (may be referred to as “X2 connection”) to a specific base station.
  • base stations with different versions of 3GPP supported may be mixed.
  • an older release version of a base station (which may be referred to as a “legacy base station”) may not support an X2 connection with an X2 GW.
  • the X2 GW may be regarded as an example of a “relay node” that relays communication over an X2 connection.
  • one of the objectives of the techniques described herein is a relay node with another base station that supports connection with the relay node, even if the base station does not support connection with the relay node. To establish a connection over the network.
  • the relay node relays communication between a core node connected to the first base station and a second base station different from the first base station.
  • the relay node may include a reception unit, a determination unit, and a transmission unit.
  • the receiving unit may receive a base station-core node message from the core node.
  • the determination unit may be configured such that the message between the base station and the core node does not support inter-base station connection with a second relay node in which the second base station connects between base stations via an inter-base station interface. It may be determined whether the message is a message transmitted from the station and includes an information element for requesting the address information of the second base station.
  • the transmitter includes a message including an information element for requesting the address information of the second base station, wherein the base station-core node message is transmitted from the first base station to the second base station. If it is determined by the determination unit, the message between the base station and the core node may be terminated, and the address information of the first relay node may be transmitted to the first base station.
  • the wireless communication system includes a first base station, a second base station, a core node connected to the first base station, and between the second base station and the core node. And a second relay node in which the second base station connects between base stations via an inter-base station interface.
  • the first relay node may include the above-described reception unit, determination unit, and transmission unit.
  • a communication method requests address information of the second base station from the first base station that does not support inter-base station connection with the second relay node to the core node.
  • a base station-core node message including the information element may be transmitted.
  • the base station-core node message may be transmitted from the core node to the first relay node.
  • the first relay node Relay node address information may be returned to the first base station via the core node.
  • a base station that does not support connection with a relay node can establish a connection via the relay node with another base station that supports connection with the relay node.
  • FIG. 6 is a schematic diagram illustrating an example of an aspect in which X2 connections between a plurality of HeNBs and MeNBs in FIG. 5 are aggregated in a gateway (X2 GW). It is a schematic diagram which shows an example of the message format which provided the RNL (Radio
  • IE information element
  • LMNB legacy MeNB
  • FIG. 16 is a sequence diagram for explaining a procedure corresponding to FIG. 15. It is a schematic diagram for demonstrating an example of the establishment procedure of X connection via X2 GW between LMNB and HeNB illustrated in FIG. It is a figure which shows an example of IE of the encapsulated X2 message which HeNB GW transmits to X2 GW in the example of FIG. It is a flowchart which shows the operation example of HeNB GW corresponding to FIG.
  • FIG. 20 is a sequence diagram for explaining a procedure corresponding to FIG. 19.
  • FIG. 25 is a sequence diagram for explaining a procedure corresponding to FIG. 24.
  • FIG. 26 is a sequence diagram for explaining a procedure corresponding to FIG. 25.
  • FIG. 31 is a sequence diagram for explaining a procedure corresponding to FIG. 30.
  • FIG. 33 is a sequence diagram for explaining a procedure corresponding to FIGS. 31 and 32. It is a block diagram which shows the structural example of HeNB GW. It is a block diagram which shows the hardware structural example of HeNBGW.
  • eNB radio base station
  • base station a radio base station
  • ENB is an abbreviation of “evolved (Universal Mobile Telecommunications System Terrestrial Radio Access Network) Node B”.
  • the radio area formed by the eNB may be a “cell” or a “sector”.
  • a cell formed by an eNB may be referred to as a “macro cell”.
  • a radio base station (eNB) that forms a macro cell may be referred to as a “macro base station”, a “macro eNB”, a “MeNB”, or the like.
  • a “cell” is an example of a wireless area formed according to the reachable range (also referred to as “coverage”) of a radio wave transmitted by a wireless base station.
  • a wireless device such as a mobile station located in a cell can wirelessly communicate with a wireless base station that forms the cell.
  • a small cell having a smaller coverage than the macro cell may be arranged in the macro cell (MC).
  • Small cell may include, for example, cells called “home cell”, “femto cell”, “pico cell”, “micro cell”, “metro cell”, and the like.
  • a radio base station that forms a small cell may be referred to as a “small base station”.
  • the small base station may include a home base station, a femto base station, a pico base station, a micro base station, a metro base station, and the like according to the designation of the small cell.
  • the home base station may be referred to as HeNB (Home eNodeB).
  • each of the macro base station and the small base station is an example of a network element (NE) constituting the radio access network.
  • NE network element
  • a small base station is a HeNB, but the small base station is any one of a femto base station, a pico base station, a micro base station, and a metro base station. May be.
  • FIG. 1 shows an example of a wireless communication system 1 including a plurality of MeNBs.
  • the radio communication system 1 may be referred to as “network 1” for convenience.
  • the wireless communication system 1 illustrated in FIG. 1 may include, for example, three MeNBs # 1 to # 3.
  • MeNB # i 1 to n, where n is an integer of 2 or more by way of example) each forms a macro cell MC # i.
  • MeNB # i and macrocell MC # i may be described as “MeNB” and “macrocell MC”, respectively.
  • the MeNB may be communicably connected to the MME as illustrated in FIG.
  • MME is an abbreviation of “Mobility Management Entity” and is an example of an entity or node of the core network. Therefore, the MME may be referred to as a “core node”. In other words, an example of “core node” is “MME”.
  • the MME may function as an access gateway of a control plane (Control Plane) that handles control of the radio access network in the core network.
  • Control Plane a control plane
  • the MME may support management of location registration of a wireless device such as a UE (User Equipment), calling of the wireless device, handover between base stations, and the like in the control plane.
  • UE User Equipment
  • connection interface between an eNB that is an example of a base station (any of MeNB and HeNB) and an MME that is an example of a core node may be referred to as an “S1 interface”. Connection by the S1 interface may be referred to as “S1 connection” for convenience. “S1 connection” is an example of “base station-core node connection”.
  • a signal or message transmitted / received by “S1 connection” may be referred to as an S1 signal (or S1AP signal) or an S1 message (or S1AP message) for convenience.
  • S1 signal or S1AP signal
  • S1 message or S1AP message
  • AP is an abbreviation of “Application Protocol”.
  • the S1 message is an example of a “base station-core node message”.
  • HeNB # j and the small cell SC # j may be expressed as “HeNB” and “small cell SC”, respectively.
  • eNB eNode B
  • HeNB # j may be communicably connected to the MME via the S1 interface. However, it is assumed that the HeNB is installed in a larger amount in the wireless communication system 1 than the MeNB that forms the macro cell MC. If a large number of HeNBs are directly connected to the MME via S1, the load on the MME may increase.
  • the HeNB # j may not be directly connected to the MME by S1, but may be S1 connected to the gateway (GW) as schematically illustrated in FIG.
  • the GW to which the HeNB # j is S1 connected may be referred to as “HeNB GW” for convenience.
  • the number of S1 connections managed by the MME can be reduced by one SNB connection to the MME by one HeNB GW accommodating a plurality of HeNB # j. Therefore, the load on the MME can be reduced.
  • the HeNB GW may aggregate and notify the SME message received from the HeNB # j and the SCTP message belonging to the lower layer of the S1 connection to the MME.
  • SCTP is an abbreviation for “Stream Control Transmission Protocol”.
  • the wireless communication system 1 it is assumed that there are 100 HeNBs # 1 to # 100.
  • 100 HeNBs directly connects to the MME with S1, 100 sets of SCTP connections and S1 connections are established, so the MME manages 100 sets of SCTP connections and S1 connections.
  • the HeNB GW when the HeNB GW is installed, the HeNB GW terminates the SCTP connection and the S1 connection with the HeNB, and sets one SCTP connection and the MME. Establish S1 connection.
  • the HeNB GW associates 100 sets of SCTP connections and S1 connections with 100 HeNBs with one set of SCTP connections and S1 connections with the MME.
  • the MME only has to manage a set of SCTP connection and S1 connection with the HeNB GW, and the load is reduced.
  • the format of the S1 message does not have to be changed. This is because, even when the HeNB GW is installed, the SCTP connection and the S1 connection are associated one-to-one as illustrated in FIG.
  • the X2 interface is defined in addition to the S1 interface.
  • the X2 interface is an example of an interface between base stations for performing communication between base stations.
  • the MeNB # i illustrated in FIG. 1 is connected to each other via the X2 interface and can communicate via the X2 interface as illustrated in FIG.
  • X2 connection The connection using the X2 interface may be referred to as “X2 connection” for convenience.
  • X2 connection is an example of “inter-base station connection”.
  • signals and messages transmitted and received through the X2 connection may be referred to as X2 signals (or X2AP signals) or X2 messages (or X2AP messages).
  • the X2 message is an example of the “inter-base station message”.
  • HeNB # j when HeNB # j is installed in the wireless communication system 1, as illustrated in FIG. 5, between MeNB-MeNB, between MeNB-HeNB, and between HeNB-HeNB Each may be X2 connected, and communication between base stations by X2 connection may be performed.
  • HeNB # j installed in large quantities in the radio communication system 1 is directly connected to MeNB # i by X2, the load of the MeNB may increase.
  • the HeNB is not directly X2 connected to the MeNB, but as schematically illustrated in FIG. X2 connection is being considered.
  • the GW to which the HeNB is X2 connected may be referred to as “X2 GW” for convenience.
  • the X2 GW may aggregate and notify the MeNB of SCTP messages belonging to the lower layer of the X2 connection received from the HeNB.
  • the wireless communication system 1 includes 100 HeNBs # 1 to # 100. Since 100 HeBNs establish SCTP connection and X2 connection, respectively, when 100 HeNBs directly connect with MeNB by X2, MeNB manages 100 sets of SCTP connection and X2 connection.
  • the X2 GW terminates the SCTP connection with the HeNB and establishes one SCTP connection with the MeNB. May be connected.
  • the X2 GW may associate 100 sets of SCTP connections and X2 connections with the HeNB and one SCTP connection with the MeNB.
  • the MeNB has only to manage one SCTP connection and 100 X2 connections, for example, and the load is reduced.
  • X2 messages in different formats may be used when the X2 connection is made directly between the MeNB-MeNB, the HeNB-MeNB, and the HeNB-HeNB and when the X2 connection is made via the X2 GW. .
  • the X2 connection is not aggregated into one in one SCTP connection, and the SCTP connection and the X2 connection are not. This is because they are not necessarily associated one-to-one.
  • an X2 message obtained by encapsulating the X2 message not via the X2 GW together with the RNL header may be used.
  • the X2 message may be referred to as “X2AP: MESSAGE TRANSFER”.
  • RNL is an abbreviation for “Radio Network Layer”.
  • the RNL header is an example of an information element (Information Element, IE) of “X2AP: MESSAGE TRANSFER”.
  • the RNL header may include a source eNB identifier (SourceeNBeNB ID) and a destination eNB identifier (Target eNB ID) as an example of IE.
  • SourceeNBeNB ID source eNB identifier
  • Tiget eNB ID destination eNB identifier
  • ENB ID is an example of eNB identification information.
  • Source ⁇ eNB ID is an example of the source information of the encapsulated X2 message
  • Target eNB ID is an example of the destination information of the encapsulated X2 message.
  • the X2 GW may determine the transfer destination of the received “X2AP:“ MESSAGE ”TRANSFER” with reference to the destination information “Target eNB” ID.
  • FIG. 9 shows a transfer example of "X2AP:" MESSAGE "TRANSFER".
  • FIG. 9 exemplifies a mode in which three HeNBs # 1 to # 3 are connected to the X2 GW in the same manner as in FIG. Also, it is assumed that the eNB IDs of HeNBs # 1 to # 3 are H1, H2, and H3, respectively, and the eNB of MeNB # 1 is M1.
  • HeNB # 1 sets “H1” to “Source eNB ID” and “X1AP: MESSAGE TRANSFER” that sets “M1” to “Target eNB ID” Is transmitted to the X2 interface.
  • the X2 GW When the X2 GW receives the “X2AP:“ MESSAGE ”TRANSFER” via the X2 interface, the X2 GW refers to the “Target“ eNB ”ID”. Since “M1” which is the eNB ID of MeNB # 1 is set in “Target eNB ID”, the X2 GW transfers the received “X2AP: MESSAGE TRANSFER” to MeNB # 1.
  • HeNB # 2 and HeNB # 3 transmit "X2AP:" MESSAGE "TRANSFER" to MeNB # 1.
  • HeNB # 3 sets “Source eNB ID” to “H3” and “Target eNB ID” to “X2AP” : MESSAGE TRANSFER "is generated and sent to the X2 interface.
  • the X2 GW When the X2 GW receives the “X2AP:“ MESSAGE ”TRANSFER” via the X2 interface, the X2 GW refers to the “Target“ eNB ”ID”. Since “H2” that is the eNB ID of HeNB # 2 is set in “Target eNB ID”, the X2 GW transfers the received “X2AP: MESSAGE TRANSFER” to HeNB # 2.
  • HeNB # 3 transmits to HeNB # 1, HeNB # 1 transmits to HeNB # 2 or # 3, or HeNB # 2 transmits to HeNB # 1 or # 3 "X2AP: MESSAGE TRANSFER" It is.
  • the X2 GW uses the eNB's ID (eNB ⁇ ID) and IP (Internet ⁇ ⁇ ⁇ ⁇ Protocol) address in order to enable the transfer of “X2AP: MESSAGE TRANSFER” to the eNB specified by the “Target eNB ID”. Store it in association.
  • the IP address is an example of address information.
  • the eNB connected to the X2 GW may transmit “X2AP: MESSAGE TRANSFER” not including the “Target eNB ID” and the X2 message to the X2 GW at the time of startup or the like.
  • the X2 GW associates the eNB ID set in “Source” eNB ”ID with the IP address that is an example of the source address of“ X2AP: “MESSAGE” TRANSFER ”by receiving the“ X2AP: “MESSAGE” TRANSFER ”. It is possible to memorize.
  • X2 connection establishment procedure Next, an example of the procedure for establishing the X2 connection will be described.
  • the first eNB may attempt to establish an X2 connection to the second eNB.
  • Both the first eNB and the second eNB may be MeNB or HeNB.
  • the presence of the second eNB illustratively indicates that the UE (User Equipment) located in both the first eNB and the second eNB cell is included in the signal received from the second eNB. May be detected by notifying the first eNB of the ID of the eNB.
  • the UE is an example of a wireless terminal or a wireless device.
  • the IP address of each eNB that performs the X2 connection may be used. Therefore, the first eNB acquires the IP address of the second eNB when establishing an X2 connection with the second eNB.
  • the IP address of the second eNB can be acquired by using, for example, the S1 message by the MME connected to the second eNB through the S1 interface.
  • the IP address may be obtained by inquiring of the MME.
  • the eNB ID of the eNB that wants to know the IP address may be set to “Target eNB ID” that is an IE of “S1AP: eNB CONFIGURATION TRANSFER” as shown in FIG.
  • “X2 TNL Configuration Info.” May be specified in “SON Information Request” of “S1AP: eNB CONFIGURATION TRANSFER”.
  • the eNB ID of the eNB that is requested to respond to the IP address is “Target eNB-ID” (for example, see FIG. 13) that is an IE of “S1AP: eNB CONFIGURATION TRANSFER” May be set.
  • the eNB # 1 may inquire the MME for the IP address of the partner eNB # 2 using “S1AP eNB CONFIGURATION TRANSFER”.
  • eNB # 1 that supports X2 GW and X2 connection is also supported by eNB # 2 that supports X2 connection with X2 GW and X2 via X2 GW. Assume that a connection is established.
  • eNB # 1 can obtain the IP address used by partner eNB # 2 for X2 connection with X2 GW, for example, by the following procedure.
  • eNB # 2 sets “S1AP: eNB CONFIGURATION TRANSFER” in which the IP address of the X2 GW to which the eNB # 2 can connect X2 is set to “IE: eNB Indirect X2 Transport Layer Addresses” (see FIG. 13). It may be generated and sent back to the MME.
  • the MME generates “S1AP: MME CONFIGURATION TRANSFER” in which the IP address of X2 GW notified by the “S1AP: eNB CONFIGURATION TRANSFER” is set to “IE: eNB Indirect X2 Transport Layer Addresses”. Good.
  • the MME may notify and respond to the IP address requesting eNB # 1 of the IP address of the X2 GW by transmitting the “S1AP: MME CONFIGURATION TRANSFER” to the eNB # 1.
  • the eNB # 1 can request the establishment of the X2 connection with the partner eNB # 2 via the X2 GW from the X2 GW to which the partner eNB # 2 can connect X2 using the IP address.
  • the X2 GW is installed in order to reduce the load of the MeNB even if a large amount of HeNB is installed in the MeNB cell as described above.
  • compatibility with an existing network may deteriorate.
  • the “IE: eNB Indirect X2 Transport Layer Addresses” for X2 GW is “S1AP: eNB CONFIGURATION TRANSFER” that is sent to the MME when the MeNB before 3GPP Rel. Not set.
  • the HeNB of 3GPP Rel. 12 or later sets “IE: eNB Indirect X2 Transport Layer Addresses '' in“ S1AP: MME CONFIGURATION TRANSFER ”used for the response addressed to the MME.
  • IE eNB Indirect X2 Transport Layer Addresses '' in“ S1AP: MME CONFIGURATION TRANSFER ”used for the response addressed to the MME.
  • the MeNB before 3GPP Rel. 11 cannot read the IE.
  • X2 GW is based on the premise that MeNB supports X2 connection with X2 GW specified in 3GPP Rel. 12 or later version.
  • LMeNB Legacy MeNB
  • a wireless communication system 1 including an LMeNB, MeNB, HeNB, HeNB GW, X2 GW, and MME will be described as an example.
  • the LMeNB is an example of a “first base station”
  • the HeNB is an example of a “second base station”.
  • the HeNB GW is an example of a “first relay node” that relays communication between the MME and the HeNB.
  • X2 GW is an example of a “second relay node” to which HeNB can connect X2.
  • the HeNB GW exemplified in FIGS. 14 and 15 may exemplarily perform the following processing.
  • the HeNB GW has additional second address information (for example, IP address) used for establishing the X2 connection. Address) may be assigned.
  • the second IP address may be referred to as a “pseudo X2 connection IP address” for convenience.
  • the second IP address may be used, for example, when the LMeNB establishes an X2 connection via the X2 GW with a HeNB that can make an X2 connection to the HeNB GW.
  • the HeNB GW confirms the IE configuring “S1AP:“ MME ”CONFIGURATION“ TRANSFER ”received from the MME, and whether“ IE: “eNB” Indirect “X2” Transport “Layer” Addresses ”is set (may be referred to as“ selection ”). It may be determined whether or not.
  • the “S1AP: MME CONFIGURATION TRANSFER” is an S1 message sent to the MME by the LMeNB that does not support X2 connection with X2 GW Can be judged.
  • the HeNB GW may forward (may be referred to as “transparent”) to the HeNB for “S1AP: MME CONFIGURATION TRANSFER” in which “IE: eNB Indirect X2 Transport Layer Addresses” is selected.
  • the HeNB GW may be terminated without being transferred to the HeNB.
  • the HeNB GW may transmit a pseudo X2 connection IP address that is an example of the IP address of the HeNB GW to the MME.
  • the IP address for pseudo X2 connection may be set to “IE: eNB Indirect X2 Transport Layer Addresses” in “S1AP: eNB CONFIGURATION TRANSFER” addressed to the MME.
  • the HeNB GW may store the eNB ID set in each of “IE:“ Target ”eNB” ID ”and“ IE: “Source: eNB” ID ”in the received“ S1AP: “MME CONFIGURATION” TRANSFER ”.
  • the HeNB GW registers the eNB ID set in each of “IE: IE Target eNB-ID” and “IE: Source eNB ID” in the X2 mapping table 19 as shown in FIG. You may remember.
  • the eNB ID set in “IE:“ Target ”eNB“ ID ” is illustratively equivalent to the eNB ID of the HeNB to which the LMeNB has attempted X2 connection.
  • the eNB ID set in “IE:“ Source ”eNB“ ID ” illustratively corresponds to the eNB ID of the LMeNB that attempted X2 connection to the HeNB.
  • flag information (for example, Yes or No) indicating whether the X2 connection has been established may be registered together.
  • the flag information may be referred to as “X2 establishment flag” for convenience. Since the X2 connection is not established at the time when the above association is registered in the X2 mapping table 19, the X2 establishment flag may be set to information indicating “No”.
  • FIG. 14 shows an example of message transfer when the MeNB tries to make an X2 connection with the HeNB
  • FIG. 15 shows an example of message transfer when the LM eNB attempts an X2 connection with the HeNB.
  • FIG. 16 is a flowchart illustrating an operation example focusing on the HeNB GW in the examples of FIGS. 14 and 15.
  • FIG. 18 is a sequence diagram corresponding to the example of FIG.
  • the HeNB uses the IP address used for the X2 connection with the X2 GW as the MME. You may contact (or request)
  • the MeNB may transmit an S1 message “S1AP: eNB CONFIGURATION TRANSFER” in which “IE: eNB Indirect X2 Transport Address ⁇ ”(see FIG. 12) is set to the MME (procedure 1).
  • S1 message is an example of a message in which the eNB requests an IP address from the MME, and may be referred to as an “eNB address request message” for convenience.
  • the MME may send “S1AP: MME CONFIGURATION TRANSFER” to the HeNB (procedure 2).
  • S1AP:“ MME CONFIGURATION ”TRANSFER” is an example of an S1 message in which the MME requests an IP address from the eNB, and may be referred to as an MME address request message for convenience.
  • the MME may set “IE: eNB Indirect X2 Transport Layer Addresses” of the eNB address request message received from the MeNB in the MME address request message.
  • the Heme can request the IP address of the X2 GW that can connect to the X2 in the MME address request message.
  • the MME address request message “S1AP:“ MME CONFIGURATION ”TRANSFER” transmitted from the MME to the HeNB is received by the HeNB GW to which the destination HeNB is connected before reaching the destination HeNB.
  • the HeNB GW may confirm the IE constituting the message (processes P11 to P13 in FIG. 16).
  • the HeNB GW may confirm whether “IE: SON Information ⁇ Request ”is selected in“ IE: SON Information ”of the received“ S1AP: MME CONFIGURATIONUTRANSFER ”(processing P11).
  • the HeNB GW further checks whether “X2 TNL Configuration Info.” Is selected in “IE: SON Information Request”. (Process P12).
  • the HeNB GW determines whether “IE: eNB Indirect X2 Transport Layer Addresses” is set in “X2 TNL Configuration Info.”. You may confirm (process P13).
  • the HeNB GW may transfer the MME address request message “S1AP: MME CONFIGURATION TRANSFER” to the HeNB (may be referred to as “transparency”) (process P15 and procedure 3 in FIG. 14).
  • the HeNB GW forwards the received “S1AP: MME CONFIGURATION TRANSFER” to the HeNB. You can do it.
  • the HeNB may reply to the MME with the IP address of the X2 GW to which the HeNB can connect X2 (FIG. 14). Procedure 4).
  • S1AP: eNB "CONFIGURATION” TRANSFER "may be used for the IP address response.
  • the S1 message is an example of a message in which an eNB that has received an inquiry about an IP address responds to the MME with an IP address, and may be referred to as an “eNB address response message” for convenience.
  • the HeNB generates an eNB address response message “S1AP: eNB CONFIGURATION TRANSFER” in which the IP address of X2 GW is set to “IE: eNB Indirect X2 Transport Layer Addresses” (see FIG. 13), and returns to the MME as a response. You can do it.
  • the eNB address response message “S1AP: eNB CONFIGURATION TRANSFER” is received by the HeNB GW before reaching the MME.
  • the HeNB GW may confirm the IE in the same manner as the above-described processing P11 to P13.
  • the HeNB GW may transfer the eNB address response message “S1AP: eNB CONFIGURATION TRANSFER” received from the HeNB to the MME (process P15 in FIG. 16 and procedure 5 in FIG. 14).
  • the MME may generate an S1 message “S1AP: MME CONFIGURATION TRANSFER” in which the IP address of the X2 GW notified in the eNB address response message is set to “IE: eNB Indirect X2 Transport Layer Addresses”.
  • the S1 message is an example of a message in which the MME returns or responds to the IP address request source (in other words, the source of the eNB address request message).
  • the SME message is referred to as an “MME address response message”. You may call it.
  • the MME may transmit the generated MME address response message “S1AP: MME CONFIGURATION TRANSFER” to the MeNB that is the address request source.
  • MME address response message “S1AP: MME CONFIGURATION TRANSFER”
  • the MeNB receives the MME address response message, the IP address of the X2 GW is notified to the MeNB (procedure 6 in FIG. 14).
  • the MeNB can acquire the IP address by inquiring the MME from the S1 message about the IP address used by the HeNB for the X2 connection with the X2 GW.
  • the MeNB can request the X2 GW to which the HeNB can connect X2 using the acquired IP address to establish the X2 connection with the HeNB via the X2 GW. Thereby, MeNB can establish X2 connection via HeNB and X2 GW.
  • the LMeNB may transmit an eNB address request message “S1AP: eNB CONFIGURATION H TRANSFER” requesting the HeNB IP address to the MME (procedure 1 and process P21 in FIG. 18).
  • the eNB ID of the HeNB that the LLMeNB wants to know the IP address is set in “Target eNB ID” of “IE: SON Configuration Transfer” (see FIG. 12). Good. Also, since the eNB that wants to know the IP address is a HeNB, “IE: SON Information Request” may be designated as “X2 TNL Configuration Info.”.
  • the MME may request the reply of the IP address by transmitting the MME address request message “S1AP: MME CONFIGURATION TRANSFER” to the HeNB, as in the example of FIG. .
  • This process corresponds to procedure 2 in FIG. 15 and process P22 in FIG.
  • the MME address request message “S1AP:“ MME CONFIGURATION ”TRANSFER” transmitted from the MME to the HeNB is received by the HeNB GW before reaching the destination HeNB.
  • the HeNB GW may perform the IE confirmation (also referred to as “determination process”) exemplified in the processes P11 to P13 in FIG. 16 (the process in FIG. 18). P23).
  • IE: eNB Indirect X2 Transport Layer Addresses set when X2 connection with X2 GW is possible is not set in “IE: X2 TNL Configuration Info.”
  • Process P13 in FIG. Is determined as NO.
  • the HeNB GW may determine that the transmission source of the MME address request message received from the MME is the LMNB.
  • the HeNB GW may terminate the MME address request message “S1AP: MME CONFIGURATION TRANSFER” received from the MME without forwarding it to the HeNB.
  • the HeNB GW may respond to and notify the MME of the IP address of the HeNB GW.
  • This process corresponds to, for example, the procedure 4 in FIG. 15, the process P14 in FIG. 16, and the process P25 in FIG.
  • the IP address of the HeNB GW that responds to and notifies the MME may be the above-described pseudo X2 connection IP address.
  • the HeNB GW generates “S1AP: eNB CONFIGURATION TRANSFER” in which the IP address for pseudo X2 is set in “IE: Target eNB ID” of “IE: SON Configuration Transfer” illustrated in FIG. 13 to the MME. May be sent.
  • the HeNB GW associates the eNB ID set in each of “Source eNB ID” and “Target eNB ID” of the MME address request message received from the MME with the X2 mapping table. 19 may be stored.
  • the “Source eNB ID” of the MME address request message is set to the eNB ID of the LMeNB
  • the “Target eNB ID” is the eNB ID of the HeNB to which the LMeNB has attempted X2 connection. Is set.
  • the HeNB GW may register and store the eNB ID of the LMeNB in association with the eNB ID of the HeNB to which the LMeNB has attempted X2 connection in the X2 mapping table 19.
  • the registration to the X2 mapping table 19 may be performed before or after the eNB address response message “S1AP: eNB CONFIGURATION TRANSFER” in which the IP address of the HeNB GW is set is sent back to the MME, and in parallel with the reply processing. May be implemented.
  • the registration process P24 to the X2 mapping table 19 is performed after the determination process P23 and before the reply process P25 of the eNB address response message “S1AP: eNB CONFIGURATIONUTRANSFER”.
  • S1AP eNB CONFIGURATIONUTRANSFER
  • the MME may generate an MME address response message “S1AP: MME CONFIGURATION TRANSFER” including the IP address of the HeNB GW notified by the eNB address response message from the HeNB GW and transmit it to the LMeNB.
  • This process corresponds to, for example, the procedure 5 in FIG. 15 and the process P26 in FIG.
  • the IP address of the HeNB GW may be set to “IE: Target eNB ID” of “IE: SON Configuration Transfer” as illustrated in FIG. .
  • the LM eNB receives the MME address response message “S1AP: MME ⁇ ⁇ ⁇ ⁇ CONFIGURATION TRANSFER” from the MME, and acquires the IP address of the HeNB GW instead of the IP address of the HeNB trying to establish the X2 connection.
  • the LMeNB recognizes that the acquired HeNB GW IP address is the IP address of the HeNB trying to establish the X2 connection. Therefore, the LMeNB is actually making a request to the HeNB GW even though it intends to request the HeNB to establish the X2 connection using the acquired IP address.
  • the HeNB GW may perform the process of establishing the X2 connection between the LMeNB and the HeNB via the X2 GW based on the entry of the X2 mapping table 19, for example.
  • the HeNB GW may check whether or not an X2 connection has already been established with the registered LMeNB after the entry registration in the X2 mapping table 19 (process P31 in FIG. 21 and process P41 in FIG. 22).
  • the HeNB GW receives the X2 message “X2AP: X2 SETUP REQUEST” requesting establishment of the X2 connection from the LMeNB.
  • the process enters a waiting state (process P32 in FIG. 21).
  • the X2 message may be referred to as an “X2 connection establishment request message” for convenience.
  • the HeNB GW may return the response message“ X2AP: X2 “SETUP” RESPONSE ”to the LMeNB to establish the X2 connection with the LMeNB.
  • This process corresponds to, for example, the procedures 1 and 2 in FIG. 19 and the processes P42 and P43 in FIG.
  • the HeNB GW can make the LMeNB recognize that the X2 connection with the HeNB desiring to establish the X2 connection is normally established by transmitting “X2AP: X2 SETUP RESPONSE” to the LMeNB.
  • step 5 of FIG. 10 if the LMeNB sends “X2AP: X2 SETUP REQUEST” to the HeNB that wishes to establish the X2 connection as usual, the X2 connection with the HeNB is normal. Can be established.
  • the HeNB GW may confirm whether the X2 connection with the LMeNB has been established (process P33 in FIG. 21 and process P44 in FIG. 22).
  • the HeNB GW may start the process of establishing the X2 connection with the HeNB via the X2 GW (step 3 in FIG. 19). . Thereby, HeNB GW can start establishment of X2 connection with HeNB via X2 GW, without burdening LMNB with an additional process.
  • the HeNB GW may encapsulate “X2AP: X2 SETUP REQUEST” received from the LMeNB into a transfer message “X2AP: X2AP MESSAGE TRANSFER” and transmit it to the X2 GW.
  • This process corresponds to, for example, the procedure 3 in FIG. 19, the process P34 in FIG. 21, and the process P45 in FIG.
  • “IE: Source eNB ID” of “IE: RNL Header” included in the transfer message “X2AP: X2AP MESSAGE TRANSFER” is the transmission source of “X2AP: X2 SETUP REQUEST”.
  • the eNB ID of the LMeNB may be set.
  • the eNB ID of the HeNB associated with the eNB ID of the LMeNB in the X2 mapping table 19 may be set.
  • the X2 GW When the X2 GW receives “X2AP: X2AP MESSAGE TRANSFER” from the HeNB GW, the received “X2AP: X2AP MESSAGE TRANSFER” is addressed to the HeNB identified by the eNB ID set in “IE: Target eNB ID”. May be forwarded.
  • the HeNB When the HeNB receives “X2AP: X2 MESSAGE TRANSFER” from the X2 GW, the HeNB encapsulates the response message “X2AP: X2 SETUP ⁇ ⁇ ⁇ ⁇ RESPONSE” to “X2AP: X2 MESSAGE ⁇ TRANSFER” and sends it to the X2 GW Send back.
  • the X2GW may forward the “X2AP: X2 MESSAGE TRANSFER” to the HeNB GW (processing in FIG. 22). P48).
  • the HeNB GW When the HeNB GW receives “X2AP: X2 MESSAGE TRANSFER” including “X2AP: X2 SETUP RESPONSE” from the X2 GW, the X2 connection between the HeNB GW and the X2 GW is established. Thereby, X2 connection via X2 GW is established between HeNB GW and HeNB (process P34 of FIG. 21). Therefore, X2 connection via HeNB GW and X2 GW is established between LMeNB and HeNB.
  • the HeNB GW updates the X2 establishment flag of the entry corresponding to the LMeNB and HeNB with which the X2 connection is established in the X2 mapping table 19 to information indicating established (Yes). It's okay.
  • This process corresponds to, for example, the process P35 in FIG. 21 and the process P49 in FIG.
  • the LMeNB registered in the X2 mapping table 19 and the HeNB GW may have already established an X2 connection.
  • the X2 mapping table 19 for example, as illustrated in FIG. 23, another entry whose X2 establishment flag is “Yes” has been registered for the LMeNB having the same eNB ID.
  • the HeNB GW does not wait for reception of “X2AP: X2 SETUP REQUEST” from the LMeNB, and X2 via the X2 GW with the HeNB described above.
  • a connection establishment process may be started.
  • the process corresponds to, for example, a process in a case where YES is determined in the procedure 3 in FIG. 19 and the process P31 in FIG. 21 and the process P41 in FIG.
  • the HeNB GW can quickly establish an X2 connection via the X2 GW with the HeNB that the LMeNB desires an X2 connection without burdening the LMeNB with additional processing.
  • the HeNB GW may be terminated without updating the X2 establishment flag.
  • the HeNB GW may relay the X2 message transmitted / received by the X2 connection established between the LMeNB and the HeNB based on the entry of the X2 mapping table 19.
  • the relay process may include, for example, a process of encapsulating an X2 message and a process of releasing the encapsulated X2 message (may be referred to as “decapsulation”).
  • the encapsulation of the X2 message and the decapsulation of the encapsulated X2 message may be regarded as an example of the format conversion of the X2 message.
  • the format conversion may be regarded as conversion between the old and new X2 interfaces.
  • the X2 interface used by the LMeNB for the X2 connection may correspond to the “old X2 interface”, and the X2 interface used by the 3GPP Rel. 12 or later version of the eNB for the X2 connection may correspond to the “new X2 interface”.
  • FIGS. 24 and 28 show an example of the X2 message transfer process from the HeNB to the LMeNB
  • FIGS. 25 and 29 show an example of the X2 message transfer process from the LMeNB to the HeNB.
  • FIG. 26 shows an operation example in the HeNB GW corresponding to FIGS. 24 and 28, and
  • FIG. 27 shows an operation example in the HeNB GW corresponding to FIGS.
  • the HeNB transmits “X2AP: X2AP MESSAGE TRANSFER” in which the X2 message is encapsulated to the LMeNB (procedure 1 in FIG. 24 and process P71 in FIG. 28). ).
  • the “X2AP:“ X2AP ”MESSAGE“ TRANSFER ” is received by the X2 GW, and the X2 GW transfers the received“ X2AP: “X2AP“ MESSAGE ”TRANSFER” to the HeNB GW (step 2 in FIG. 24 and process P72 in FIG. 28).
  • IE: Target eNB ID” and “IE: Source eNB ID” are included.
  • RNL Header is set.
  • eNB ID of LMNB is set in “IE: IETarget eNB ID”
  • eNB ID of HeNB is set in “IE: Source eNB ID”.
  • the encapsulated X2 message is received by the HeNB GW (process P51 in FIG. 26).
  • the HeNB GW checks whether the combination of the eNB ID set in “IE: Target eNB ID” and “IE: Source eNB ID” of the encapsulated X2 message is registered in the X2 mapping table 19 (Process P52 in FIG. 26 and Process P73 in FIG. 28).
  • the HeNB GW may decapsulate the X2 message encapsulated in “X2AP: X2AP MESSAGE TRANSFER” and forward the X2 message to the LM eNB specified by “IE: Target eNB ID”.
  • the process corresponds to, for example, the procedures 3 and 4 in FIG. 24, the process P53 in FIG. 26, and the processes P74 and P75 in FIG.
  • the X2 message is received by the HeNB GW (process P61 in FIG. 27).
  • the HeNB GW may confirm whether or not the eNB ID of the LMeNB that is the transmission source of the received X2 message is registered in the X2 mapping table 19 (process P62 in FIG. 27).
  • the HeNB GW may further confirm whether or not the received X2 message is a message specifying (or specifying) a destination (process P63 in FIG. 27 and FIG. 29). Process P82).
  • the LMeNB does not recognize that the communication partner HeNB has X2 connection with the X2 GW, so the SCTP connection and the X2 connection do not correspond one-to-one (for example, see FIG. 6). We do not recognize that there is sex.
  • the LMeNB recognizes that there is a one-to-one correspondence between the X2 connection and the SCTP connection because it does not recognize that the X2 GW intervenes in the X2 connection established with the HeNB. ing.
  • an X2 message designating a destination may be transmitted from the LMeNB, or an X2 message not designating a destination may be transmitted.
  • the X2 message designating the destination is, for example, a message in which the eNB ID of a specific eNB, a specific cell formed by the eNB, an ID for identifying a sector into which the cell is divided, or the like is set in the destination information of the X2 message. It's okay.
  • the X2 message may include control information related to handover and control information for transmission power control in a cell or sector.
  • the HeNB GW may specify the destination from the IE of the received X2 message (FIG. 27, process P64).
  • the HeNB GW may confirm whether or not the eNB ID corresponding to the identified destination is registered in the X2 mapping table 19 in association with the eNB ID of the source LMeNB of the received X2 message (FIG. 27). Process P65).
  • the HeNB GW may encapsulate the X2 message received from the LMeNB into “X2AP: X2AP MESSAGE TRANSFER” and transmit it to the X2 GW (process P66 in FIG. 27).
  • the destination specified from the IE of the received X2 message is set in “IE: Target eNB ID” of “IE: RNL Header”, and the eNB ID of the source LMeNB of the X2 message is set in “IE: Source eNB ID” May be set.
  • the processes P64 to P66 of FIG. 27 described above determine and determine the transfer destination of the received X2 message based on the IE included in the received X2 message, and receive it at the determined one transfer destination.
  • This process encapsulates the X2 message and sends it to the X2 GW.
  • the process corresponds to, for example, the procedure 2 (2a) and the procedure 3 in FIG. 25 and the processes P84 and P85 in FIG.
  • the X2 GW When the X2 GW receives the X2 message encapsulated in “X2AP: X2AP MESSAGE TRANSFER” from the HeNB GW, the X2AP is sent to the HeNB indicated in “IE: Target eNB ID” of “IE: RNL Header”. "MESSAGE TRANSFER" may be transferred. This process corresponds to, for example, the procedure 4 in FIG. 25 and the process P86 in FIG.
  • the HeNB GW may discard the X2 message received from the LMeNB (process P68 in FIG. 27).
  • the HeNB GW sends an X2 message based on the X2 mapping table 19
  • the transfer destination may be determined and determined.
  • the HeNB GW determines and determines eNBs corresponding to all eNB IDs associated with the eNB ID of the source LMeNB of the received X2 message in the X2 mapping table 19 as the forwarding destination of the received X2 message. It's okay.
  • the HeNB GW may generate “X2AP: X2AP MESSAGE TRANSFER” encapsulating the received X2 message, and send it to the X2 GW by the number of determined transfer destination eNBs.
  • the ID of the corresponding forwarding destination eNB may be set in "IE: Target eNB ID”.
  • the “IE: Source eNB ID” of the “IE: RNL Header” may be set to the eNB ID of the transmission source LMeNB of the X2 message.
  • an X2 connection via the X2 GW can be established between the old eNB and the new eNB, so that the X2 GW can be effectively used.
  • FIG. 31, FIG. 32 and FIG. 36 show an operation example when the SCTP connection is disconnected due to an abnormality in the SCTP connection between the HeNB and the X2 GW. Further, FIG. 33 shows an operation example in the HeNB GW corresponding to FIGS. 30 and 35, and FIG. 34 shows an operation example in the HeNB GW corresponding to FIGS. 31, 32, and 36.
  • the disconnection detection corresponds to, for example, the procedure 1 in FIG. 30, the process P101 in FIG. 33, and the process P121 in FIG.
  • the HeNB GW In response to detection of disconnection of the SCTP connection of the X2 connection with the LMeNB, the HeNB GW checks whether or not the eNB ID of the HeNB registered in association with the eNB ID of the LMeNB exists in the X2 mapping table 19 You can do it. This process corresponds to, for example, the process P102 in FIG. 33 and the process P122 in FIG.
  • the HeNB GW If the eNB ID of the corresponding HeNB exists in the X2 mapping table 19 (YES in process P102 in FIG. 33), the HeNB GW generates “X2AP: X2 RELEASE” requesting the release of the X2 connection by the number of the corresponding HeNB. And may be sent to X2 GW.
  • each “X2AP: X2 RELEASE” “IE: Global eNB ID” may be set to the eNB ID of the LMeNB registered in the X2 mapping table 19.
  • Each of “X2AP: X2 RELEASE” may be encapsulated in “X2AP: X2 MESSAGE TRANSFER” and transmitted to X2 GW.
  • Each “X2AP: X2 MESSAGE TRANSFER” transmitted from the HeNB GW to the X2 GW is received by the X2 GW and forwarded from the X2 GW to the corresponding HeNB (step 5 in FIG. 30 and FIG. 35).
  • Process P124 Thereby, in HeNB GW, the X2 connection which has become unnecessary to maintain and manage can be reliably released, and the effective use of resources for X2 communication can be achieved.
  • the HeNB GW may delete all the entries associated with the same LMeNB from the X2 mapping table 19.
  • the deletion process corresponds to, for example, the procedure 4 in FIG. 30, the process P104 in FIG. 33, and the process P125 in FIG.
  • the HeNB sent an X2 message “X2AP: X2 RELEASE” requesting the release of the X2 connection with the X2 GW to the X2 GW It also occurs in some cases. These correspond to the procedure 1 in FIGS. 31 and 32 and the process P131 in FIG. 36, for example.
  • the X2 GW detects the disconnection of the SCTP connection or receives “X2AP: X2 RELEASE” from the HeNB and sets the eNB ID of the corresponding HeNB to “Source eNB ID” and sets the “X2AP: X2 RELEASE” to the HeNB GW You may send it to.
  • the “X2AP: X2 RELEASE” may be encapsulated in “X2AP: X2 MESSAGE TRANSFER”. This process corresponds to, for example, the procedure 3 in FIGS. 31 and 32 and the process P132 in FIG.
  • the HeNB GW receives from the X2 GW “X2AP: X2 MESSAGE TRANSFER” in which “X2AP: X2 RELEASE” is encapsulated (process P111 in FIG. 34).
  • the HeNB GW confirms whether or not the eNB ID of the LMeNB registered in the X2 mapping table 19 is set in the “IE: Target eNB ID” in the “IE: RNL Header” of the “X2AP: X2 MESSAGE TRANSFER”. It's okay.
  • the HeNB GW has the eNB ID of the HeNB registered in the X2 mapping table 19 in the “IE: Target eNB ID” of “X2AP: X2 RELEASE” encapsulated in the received “X2AP: X2 MESSAGE TRANSFER”. You may check whether it is set.
  • the HeNB GW determines whether the pair of the received destination of “X2AP: APX2 MESSAGE TRANSFER” and the source of the encapsulated “X2AP: X2 RELEASE” is registered in the X2 mapping table 19 or not. You can check that.
  • the confirmation process corresponds to, for example, the process P112 in FIG. 34 and the process P133 in FIG.
  • the entry deletion corresponds to, for example, procedure 4 in FIGS. 31 and 32, process P113 in the case where YES is determined in process P112 in FIG. 34, and process P134 in FIG.
  • the HeNB GW checks in the X2 entry table 19 whether there is an entry of the LMeNB in which the number of HeNB eNB IDs associated with the LNB eNB ID is “0”. Good.
  • the confirmation process corresponds to, for example, the process P114 in FIG. 34 and the process P135 in FIG.
  • the HeNB GW disconnects the SCTP connection with the corresponding LMeNB. You can do it.
  • the cutting process corresponds to, for example, the procedure 5 in FIG. 32, the process P115 in FIG. 34, and the process P136 in FIG.
  • X2 connection with LMNB which has become unnecessary to maintain and manage can be cut off surely. Therefore, it is possible to effectively use resources for X2 communication between the HeNB GW and the LMeNB.
  • the HeNB GW can send and receive messages between the base station and the X2 GW.
  • the HeNB GW When the HeNB GW reads an S1 message for establishing an X2 connection that is transmitted and received between base stations and meets specific conditions, the S1 message is terminated at the HeNB GW without being transferred to the destination base station. It's okay.
  • An example of the “specific condition” is that the source of the S1 message is a base station that does not support X2 connection with the X2 GW.
  • -HeNB GW may notify the address information of HeNB GW addressed to the 1st base station which is the transmission origin of S1 message.
  • the address information of the HeNB GW may be used for the first base station to establish an X2 connection via the X2 GW with a second base station that can connect to the X2 GW.
  • -HeNB GW may memorize
  • the HeNB GW When the HeNB GW receives an X2 connection establishment request from the first base station that has notified the address information of the HeNB GW, the HeNB GW accepts the request and establishes an X2 connection with the first base station. It's okay.
  • the HeNB GW refers to the combination of the base stations that wish to establish the stored X2 connection in response to the establishment of the X2 connection with the first base station.
  • a message for establishing the X2 connection may be transmitted to the X2 GW to establish the X2 connection.
  • the HeNB GW does not wait for reception of an X2 connection establishment request from the first base station, The process of establishing an X2 connection with the second base station may be started.
  • the HeNB GW stores the combination of the first base station established with the HeNB GW and the X2 connection without going through the X2 GW and the second base station established with the HeNB GW and the X2 connection through the X2 GW. You can do it.
  • the HeNB GW may release the encapsulation of the received message and transmit it to the first base station.
  • the HeNB GW When the HeNB GW receives a message specifying the destination from the first base station through the X2 connection not via the X2 GW, the HeNB GW may specify the destination from the information element of the received message. Then, the HeNB GW may encapsulate the received message by giving the base station ID corresponding to the identified destination and the ID of the first base station, and transmit the encapsulated message to the X2 GW.
  • the HeNB GW receives a message that does not specify a destination from the first base station via an X2 connection that does not go through the X2 GW, the HeNB GW selects the destination from the combination of the stored base stations that have established the X2 connection. It's okay. Then, for each selected destination, the HeNB GW assigns the base station ID corresponding to the destination and the ID of the first base station to encapsulate the received message, and sends the encapsulated message to the X2 GW. May be sent.
  • the HeNB GW may delete the stored combination of the corresponding base stations.
  • the HeNB GW may delete the stored combination of the corresponding base stations.
  • the HeNB GW may disconnect the X2 connection with the first eNB.
  • the S1 connection using the S1 interface is given as an example of the “base station-core node connection” which is a connection between the base station and the core node.
  • the connection between the base station and the core node is described.
  • the connection corresponding to is not limited to the S1 connection.
  • the message transmitted in the “base station-core node connection” is not limited to the S1 message. If the message is transmitted in the connection between the base station and the core node, the message “between the base station and the core node” is used. Corresponds to "Message".
  • inter-base station connection is not limited to X2 connection by the X2 interface, and corresponds to “inter-base station connection” if the connection is between base stations. Therefore, the message transmitted in the “inter-base station connection” is not limited to the X2 message, and if the message is transmitted in the connection between the base stations, it corresponds to the “inter-base station message”.
  • the HeNB GW may include, for example, an S1 transmission / reception unit 11 for HeNB, an S1 transmission / reception unit 12 for MME, an X2 transmission / reception unit 13 for X2 GW, and an X2 transmission / reception unit 14 for LMENB.
  • the HeNB GW may include, for example, an S1 message determination unit 15, an X2 establishment unit 16, an X2 processing unit 17, an X2 monitoring unit 18, and an X2 mapping table 19.
  • the S1 transmission / reception unit 11 for HeNB illustratively performs transmission / reception of an S1 message with the HeNB.
  • the S1 transmission / reception unit 12 for MME illustratively performs transmission / reception of M1 and S1 messages.
  • the S1 transmission / reception unit 12 for MME is an example of a first reception unit that receives an S1 message from the MME.
  • the S1 transmission / reception part 12 for MME is also an example of the 1st transmission part which transmits the S1 message addressed to LMeNB including the IP address of HeNB GW to MME.
  • the X2 transmission / reception unit 13 for X2 GW for example, transmits / receives an X2 message to / from the X2 GW.
  • the X2 transmission / reception unit 14 for LMeNB illustratively performs transmission / reception of an X2 message with the LMeNB.
  • the X2 transmission / reception unit 14 for the LMeNB is an example of a second reception unit that receives an X2 connection establishment request with the HeNB from the LMeNB that has received the IP address of the HeNB GW.
  • the X2 transmission / reception unit 14 for LMeNB is also an example of a second transmission unit that transmits a response to the establishment request to the LMeNB.
  • the S1 message determination unit 15 illustratively determines whether or not to establish an X2 connection with the transmission source eNB in response to reception of “MMEMCONFIGURATION TRANSFER” which is an example of the S1 message.
  • the S1 message determination unit 15 may update the X2 mapping table 19.
  • the operation example described in the flowchart of FIG. 16 may be performed by the S1 message determination unit 15.
  • the S1 message determination unit 15 may determine whether or not the received S1 message is an address request message having the LMeNB as a transmission source.
  • the S1 message determination unit 15 may terminate the received address request message without transferring it to the HeNB.
  • the S1 message determination unit 15 may transmit an address response message including the IP address of the HeNB GW to the LMeNB of the IP address request source through the S1 transmission / reception unit 12 for MME.
  • the X2 establishment unit 16 is an example of an “inter-base station connection establishment unit”, and may exemplarily perform a process of establishing an X2 connection between the X2 GW and the LMeNB. Therefore, X2 establishment part 16 may be provided with X2 establishment part 161 for X2 GW, and X2 establishment part 162 for LMeNB, for example.
  • the X2 GW-facing X2 establishment unit 161 illustratively performs processing for establishing an X2 connection with the X2 GW.
  • the L2 eNB-oriented X2 establishment unit 162 illustratively performs a process of establishing an X2 connection with the LMeNB.
  • the X2 establishment unit 16 may update the X2 mapping table 19. For example, the operation example described in the flowchart of FIG. 21 may be performed by the X2 establishment unit 16.
  • the X2 processing unit 17 is an example of an “inter-base station message processing unit”, and may illustratively process an X2 message transmitted / received through the X2 transmitting / receiving units 13 and 14. Therefore, the X2 processing unit 17 may exemplarily include a message processing unit 171 for LMeNB and a message processing unit 172 for X2 GW.
  • the message processing unit 171 for LMeNB decapsulates the X2 message received by the X2 transmission / reception unit 13 for X2 GW, for example.
  • the decapsulated X2 message is exemplarily transmitted to the LMeNB through the X2 transmission / reception unit 14 for LMeNB.
  • the message processing unit 172 for X2 GW illustratively encapsulates the X2 message received by the X2 transmission / reception unit 14 for LMeNB and sets an appropriate “IE: Target eNB ID”.
  • the encapsulated X2 message is illustratively transmitted to the X2 GW via the X2 GW-oriented X2 transmission / reception unit 13.
  • the X2 processing unit 17 is an example of a processing unit that performs transfer processing of an X2 message transmitted and received through the X2 connection established between the LMeNB and the HeNB via the X2 GW based on the entry of the X2 mapping table 19. is there.
  • the X2 monitoring unit 18 may, for example, monitor the establishment state of the X2 connection and delete an unnecessary entry in the X2 mapping table 19. In addition, the X2 monitoring unit 18 may perform a process of disconnecting communication over an X2 connection that does not need to be established according to deletion of an unnecessary entry.
  • the operation described in the flowcharts of FIGS. 33 and 34 may be performed in the X2 monitoring unit 18.
  • the X2 monitoring unit 18 that performs the operation described in the flowchart of FIG. 33 is an example of a first monitoring unit.
  • the X2 monitoring unit 18 that performs the operation described in the flowchart of FIG. 34 is an example of a second monitoring unit.
  • the X2 mapping table 19 may be associated with the eNB ID of the LMeNB and the eNB of the HeNB and stored together with the X2 establishment flag.
  • FIG. 38 illustrates a hardware configuration example of the HeNB GW.
  • the HeNB GW illustrated in FIG. 38 illustratively includes a processor 301, a RAM (Random Access Memory) 302, a ROM (Read Only Memory) 303, an HDD (Hard Disc Drive) 304, and a network interface (NW-IF) 305. You may be prepared.
  • a processor 301 a RAM (Random Access Memory) 302
  • ROM Read Only Memory
  • HDD Hard Disc Drive
  • NW-IF network interface
  • the HeNB GW may include, as an option, all or part of the input interface (IF) 306, the output IF 307, the input / output IF 308, and the drive device 309, for example.
  • IF input interface
  • the processor 301, the RAM 302, the ROM 303, the HDD 304, the IFs 305 to 308, and the drive device 309 may be connected to the communication bus 310 and can communicate with each other via the processor 301, for example.
  • the processor 301 is an example of a processor circuit or a processor device having a computing capability, and is an integrated circuit (Integrated Circuit, IC) such as a CPU (Central Processing Unit), an MPU (Micro Processing Unit), or a DSP (Digital Signal Processor). Etc. may be used.
  • IC Integrated Circuit
  • a processor circuit or processor device with computing power may be referred to as a “computer”.
  • the RAM 302 and the ROM 303 are both examples of memories that store various data and programs.
  • the “program” may be referred to as “software” or “application”.
  • the RAM 302 may be used as a work memory for the CPU 301.
  • data and programs stored in the ROM 303 and the HDD 304 may be expanded in the RAM 302 and used for computation by the processor 301.
  • the HDD 304 is an example of a storage device, and stores various data and programs.
  • Other examples of the storage device include a semiconductor drive device such as a solid state drive (SSD), a nonvolatile memory such as a flash memory, and the like. Therefore, the HDD 304 may be replaced with an SSD or a flash memory.
  • SSD solid state drive
  • nonvolatile memory such as a flash memory
  • the program stored in the HDD 304 may include a program that can realize all or part of various functions as the HeNB GW illustrated in FIG. 37 (may be referred to as a “HeNB GW program” for convenience). . Note that all or part of the program code constituting the HeNB GW program may be stored in the ROM 303 or may be described as part of the operating system (OS).
  • OS operating system
  • the data stored in the HDD 304 may include the X2 mapping table 19 described above.
  • the processor 301 expands and executes the OFC program stored in the HDD 304 in, for example, the RAM 302, various functions as the HeNB GW are realized.
  • the RAM 302, the ROM 303, and the HDD 304 may be collectively referred to as the “storage unit 311” of the HeNB GW for convenience.
  • the program and data may be provided in a form recorded in a computer-readable recording medium 80.
  • the recording medium include a flexible disk, CD-ROM, CD-R, CD-RW, MO, DVD, Blu-ray disk, portable hard disk, and the like.
  • a semiconductor memory 70 such as a USB (UniversalUniversSerial Bus) memory is also an example of the recording medium 80.
  • the program and data stored in the semiconductor memory 70 may be read by the CPU 301 through the input / output IF 308, for example. Further, the program and data stored in the recording medium 80 may be read by the CPU 301 through the drive device 309, for example.
  • the program and data may be provided (in other words, “downloaded”) from the server computer or the like to the HeNB GW via a communication line.
  • a program or data may be provided to the HeNB GW through the NW-IF 305.
  • the program and data may be provided from the input device 50 to the HeNB GW through the input IF 306.
  • the NW-IF 305 is an interface that enables S1 communication or X2 communication with the HeNB, MME, X2 GW, and LMeNB, and one or more may be provided in the HeNB GW.
  • One or a plurality of NW-IFs 305 allow some or all of the S1 transmission / reception unit 11 for HeNB, the S1 transmission / reception unit 12 for MME, the X2 transmission / reception unit 13 for XGW, and the X2 transmission / reception unit 14 for LMeNB illustrated in FIG. May be realized.
  • the input device 50 may be connected to the input IF 306.
  • An example of the input device 50 is a keyboard, a mouse, operation buttons, a microphone, or the like.
  • the display device 60 as an example of an output device may be connected to the output IF 307 exemplarily.
  • a liquid crystal display or the like may be applied to the display device 60.
  • the touch panel liquid crystal display may be regarded as corresponding to the input device 50.
  • a printer, a speaker, and the like may be connected to the output IF 307 as another example of the output device.
  • the input device 50 may be used for operations such as registration and change of settings for the HeNB GW, various operations of the HeNB GW, and data input by an administrator of the HeNB GW.
  • the display device 60 which is an example of an output device, may be used for confirmation of settings by a HeNB GW administrator or the like, or for outputting various notifications to the administrator or the like.
  • the hardware configuration example of the HeNB GW illustrated in FIG. 38 is merely an example, and hardware increase / decrease may be appropriately performed in the HeNB GW.
  • addition or deletion of an arbitrary hardware block, division, integration in an arbitrary combination, addition or deletion of a communication bus, and the like may be appropriately performed in the HeNB GW.

Landscapes

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

Abstract

Selon l'invention, un système de communication sans fil (1) peut comprendre une première station de base (exemple: LMeNB); une seconde station de base (exemple: HeNB); un noeud central (exemple: MME); un premier noeud relais (exemple: HeNB GW) qui relaie une communication entre la seconde station de base (exemple: HeNB) et le noeud central (MME), et un second noeud relais (exemple: X2 GW) à travers lequel la seconde station de base (HeNB) effectue une connexion inter-stations de base au moyen d'une interface inter-stations de base. La première station de base qui ne prend pas en charge une connexion inter-stations de base avec le second noeud relais peut transmettre au noeud central un message station de base-noeud central comportant un élément d'information demandant des informations d'adresse concernant la seconde station de base. Le noeud central peut transmettre le message station de base-noeud central au premier noeud relais. Après réception du message station de base-noeud central, le premier noeud relais peut répondre à la première station de base, par l'intermédiaire du noeud central, en apportant des informations d'adresse concernant le premier noeud relais.
PCT/JP2015/080519 2015-10-29 2015-10-29 Noeud relais, système de communication sans fil et procédé de communication dans un système de communication sans fil WO2017072905A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/JP2015/080519 WO2017072905A1 (fr) 2015-10-29 2015-10-29 Noeud relais, système de communication sans fil et procédé de communication dans un système de communication sans fil
JP2017547273A JP6443561B2 (ja) 2015-10-29 2015-10-29 中継ノード、無線通信システム、及び、無線通信システムにおける通信方法

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2015/080519 WO2017072905A1 (fr) 2015-10-29 2015-10-29 Noeud relais, système de communication sans fil et procédé de communication dans un système de communication sans fil

Publications (1)

Publication Number Publication Date
WO2017072905A1 true WO2017072905A1 (fr) 2017-05-04

Family

ID=58631479

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2015/080519 WO2017072905A1 (fr) 2015-10-29 2015-10-29 Noeud relais, système de communication sans fil et procédé de communication dans un système de communication sans fil

Country Status (2)

Country Link
JP (1) JP6443561B2 (fr)
WO (1) WO2017072905A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2017108467A (ja) * 2013-04-05 2017-06-15 日本電気株式会社 Ｘ２ゲートウェイ装置および方法

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2014161105A (ja) * 2010-06-22 2014-09-04 Qualcomm Inc リレーノード、ホーム基地局、および関連するエンティティのための自動近隣関係（ａｎｒ）機能

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014169687A1 (fr) * 2013-04-16 2014-10-23 中兴通讯股份有限公司 Méthode et système de notification d'adresse de couche de transport
GB2514806A (en) * 2013-06-04 2014-12-10 Nec Corp Communications system

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2014161105A (ja) * 2010-06-22 2014-09-04 Qualcomm Inc リレーノード、ホーム基地局、および関連するエンティティのための自動近隣関係（ａｎｒ）機能

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
NEW POSTCOM: "Discussion of enhanced mobility solutions between MeNB and HeNB", 3GPP TSG-RAN WG3 ADHOC_2010_06_BEIJING R3-101850, 1 July 2010 (2010-07-01), XP050453764, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG3_Iu/TSGR3_AHGs/2010_06_Beijing/Docs/R3-101850.zip> *
SAMSUNG: "X2 connectivity issues in case of X2GW deployment", 3GPP TSG-RAN WG3#78 R3-122639, 16 November 2012 (2012-11-16), XP050670513, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG3_Iu/TSGR3_78/Docs/R3-122639.zip> *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2017108467A (ja) * 2013-04-05 2017-06-15 日本電気株式会社 Ｘ２ゲートウェイ装置および方法
US11272410B2 (en) 2013-04-05 2022-03-08 Nec Corporation Communication system

Also Published As

Publication number Publication date
JPWO2017072905A1 (ja) 2018-05-31
JP6443561B2 (ja) 2018-12-26

Similar Documents

Publication Publication Date Title
US10390376B2 (en) Communications system
JP6631818B2 (ja) Ｘ２−ゲートウェイを用いたトランスポートネットワーク層アドレス発見
US10660064B2 (en) Communication system, base station, host node, and communication method
JP5568567B2 (ja) ハンドオーバ、変換、及びルーティング機能を提供するように構成されたネットワークゲートウェイ
JP2018102013A (ja) Ｘ２ゲートウェイを有する通信システム
WO2011021875A2 (fr) Serveur pour plan de commande au niveau d&#39;un réseau de communication mobile et procédé de commande de service d&#39;accès ip local
JP6384591B2 (ja) 基地局装置および基地局間ゲートウェイ装置
US20140308959A1 (en) Methods and Apparatus for Handover Management
WO2021167290A1 (fr) Procedé et appareil pour améliorer la précision de la sélection de réseau dans un système de communication sans fil
JP2012518352A (ja) 家庭用基地局に基づくアクセスモード処理方法
JP5665680B2 (ja) 通信システム、通信方法、基地局、および、管理装置
WO2013189443A2 (fr) Procédé, système et passerelle pour obtenir une relation de correspondance entre un identifiant et une adresse dans une station de base enodeb
WO2012019554A1 (fr) Procédé, dispositif et système permettant l&#39;acquisition d&#39;informations de commande de nœud
WO2016061791A1 (fr) Procédé et appareil pour établir une interface
WO2012025059A1 (fr) Procédé, système et dispositif pour l&#39;émission de l&#39;adresse de transport x2 et l&#39;établissement de l&#39;interface x2
JP5671139B2 (ja) 通信制御方法及びホーム基地局
JP5671141B2 (ja) 通信制御方法及びホーム基地局
WO2012155656A1 (fr) Station de base hôte, appareil formant nœud relais et procédé de commutation à chemin amélioré
JP6443561B2 (ja) 中継ノード、無線通信システム、及び、無線通信システムにおける通信方法
WO2011083763A1 (fr) Appareil de gestion de station relais et procédé de gestion de station relais
JP5671140B2 (ja) 通信制御方法及びホーム基地局
WO2012152226A1 (fr) Procédé, dispositif de réseau d&#39;accès radio et système de communication permettant de transmettre des données
WO2011124135A1 (fr) Procédé et dispositif pour l&#39;adressage d&#39;un nœud de cœur de réseau au cours d&#39;une procédure de transfert intercellulaire
WO2015043289A1 (fr) Procédé d&#39;interaction d&#39;un nœud b avec une passerelle x2, nœud b, et passerelle x2
WO2013013552A1 (fr) Procédé, appareil et système pour le traitement de contexte d&#39;équipement utilisateur

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2017547273

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15907269

Country of ref document: EP

Kind code of ref document: A1