WO2013141321A1 - 通信制御方法 - Google Patents
通信制御方法 Download PDFInfo
- Publication number
- WO2013141321A1 WO2013141321A1 PCT/JP2013/058143 JP2013058143W WO2013141321A1 WO 2013141321 A1 WO2013141321 A1 WO 2013141321A1 JP 2013058143 W JP2013058143 W JP 2013058143W WO 2013141321 A1 WO2013141321 A1 WO 2013141321A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- base station
- mrn
- list
- handover
- denb
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 93
- 238000004891 communication Methods 0.000 title claims abstract description 78
- 230000005540 biological transmission Effects 0.000 claims abstract description 41
- 238000010295 mobile communication Methods 0.000 claims description 28
- 210000000707 wrist Anatomy 0.000 claims description 5
- JZEPSDIWGBJOEH-UHFFFAOYSA-N 4-decylbicyclo[2.2.1]hept-2-ene Chemical compound C1CC2C=CC1(CCCCCCCCCC)C2 JZEPSDIWGBJOEH-UHFFFAOYSA-N 0.000 description 269
- 238000010586 diagram Methods 0.000 description 40
- 238000005259 measurement Methods 0.000 description 18
- 238000012545 processing Methods 0.000 description 11
- 230000001960 triggered effect Effects 0.000 description 4
- 238000013507 mapping Methods 0.000 description 3
- 101150086935 MRN1 gene Proteins 0.000 description 2
- 101100465000 Mus musculus Prag1 gene Proteins 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000011664 signaling Effects 0.000 description 2
- 230000004308 accommodation Effects 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000015572 biosynthetic process Effects 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 125000004122 cyclic group Chemical group 0.000 description 1
- 230000006837 decompression Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/14—Relay systems
- H04B7/15—Active relay systems
-
- 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
- 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/0061—Transmission or use of information for re-establishing the radio link of neighbour cell information
-
- 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/0072—Transmission or use of information for re-establishing the radio link of resource information of target access point
-
- 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/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
- H04W36/008357—Determination of target cell based on access point [AP] properties, e.g. AP service capabilities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/14—Relay systems
- H04B7/15—Active relay systems
- H04B7/155—Ground-based stations
- H04B7/15507—Relay station based processing for cell extension or control of coverage area
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/24—Reselection being triggered by specific parameters
- H04W36/249—Reselection being triggered by specific parameters according to timing information
-
- 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/047—Public Land Mobile systems, e.g. cellular systems using dedicated repeater stations
Definitions
- the present invention relates to a communication control method in a mobile communication system.
- 3GPP 3rd Generation Partnership Project
- 3GPP 3rd Generation Partnership Project
- the relay station performs relay transmission between the donor base station and the user terminal (for example, see Non-Patent Document 1).
- an object of the present invention is to provide a communication control method capable of supporting a movable relay station.
- the communication control method of the present invention maintains a donor base station list, connects to a donor base station existing in the donor base station list, and performs relay transmission between the donor base station and a user terminal
- a step A for specifying an adjacent base station a step B for inquiring whether the adjacent base station specified in the step A is acceptable for the relay station, and an inquiry in the step B
- C updating the donor base station list according to the result.
- the communication control method of the present invention is a communication control method applied to a mobile communication system including a relay station that performs relay transmission between a donor base station and a user terminal, and the relay station to a target base station
- a step A for transmitting a handover request for requesting acceptance of the relay station to the target base station and in the step A, information indicating a load status of the relay station together with the handover request It is characterized by transmitting.
- the communication control method of the present invention holds a donor base station list, connects to a donor base station existing in the donor base station list, and performs relay transmission between the donor base station and a user terminal.
- the communication control method of the present invention is a communication control method applied to a mobile communication system including a base station having a donor base station function and a relay station that performs relay transmission between the base station and a user terminal.
- the base station has a step A in which the base station holds an adjacent base station list including an identifier of the adjacent base station, and the adjacent base station list functions as a donor base station for each of the adjacent base stations. It further includes information indicating whether or not it has.
- the communication control method of the present invention is a communication control method applied to a mobile communication system in which the base station makes a handover decision of a user terminal connected to a base station, and is connected to a donor base station, and the donor base A relay station that performs relay transmission between the station and the user terminal, wherein the relay station performs handover determination.
- the relay station performs handover determination of the relay station.
- FIG. 1 is a configuration diagram of a mobile communication system.
- FIG. 2 is a protocol stack diagram of the Un interface.
- FIG. 3 is a protocol stack diagram of the X2 interface.
- FIG. 4 is a protocol stack diagram of the S1 interface.
- FIG. 5 is a configuration diagram of a radio frame.
- FIG. 6 is a block diagram of the UE.
- FIG. 7 is a block diagram of the eNB.
- FIG. 8 is a block diagram of the MRN.
- FIG. 9 is a sequence diagram of an operation pattern 1 according to the first embodiment.
- FIG. 10 is a sequence diagram of an operation pattern 2 according to the first embodiment.
- FIG. 11 is a sequence diagram of an operation pattern 3 according to the first embodiment.
- FIG. 12 is a sequence diagram of an operation pattern 1 according to the second embodiment.
- FIG. 9 is a sequence diagram of an operation pattern 1 according to the first embodiment.
- FIG. 13 is a sequence diagram of an operation pattern 2 according to the second embodiment.
- FIG. 14 is a configuration diagram of the DeNB list used in the operation pattern 4 according to the second embodiment.
- FIG. 15 is a sequence diagram of an operation pattern 1 according to the third embodiment.
- FIG. 16 is a sequence diagram of an operation pattern 2 according to the third embodiment.
- FIG. 17 is a configuration diagram of a neighboring eNB list according to the fourth embodiment.
- FIG. 18 is a sequence diagram of an operation pattern 1 according to the fourth embodiment.
- FIG. 19 is a sequence diagram of an operation pattern 2 according to the fourth embodiment.
- FIG. 20 is an operation sequence diagram according to the fifth embodiment.
- the communication control method holds a donor base station list, connects to a donor base station existing in the donor base station list, and performs relay transmission between the donor base station and a user terminal.
- a communication control method in a relay station to perform step A for specifying an adjacent base station, step B for inquiring whether the adjacent base station specified in step A is acceptable for the relay station, and step B And C for updating the donor base station list according to the inquiry result in (1).
- the step B includes a step B1 of inquiring whether the neighboring base station identified in the step A has a donor base station function.
- the step B includes a step B2 of notifying the adjacent base station identified in the step A of the load status of the relay station.
- the communication control method further includes a step D of notifying the core network device of the donor base station list updated in the step C via the donor base station.
- the communication control method is a communication control method applied to a mobile communication system including a relay station that performs relay transmission between a donor base station and a user terminal.
- the relay station In the handover procedure of the relay station, the relay station has a step A for transmitting a handover request for requesting acceptance of the relay station to the target base station, and in the step A, information indicating a load status of the relay station is Sent with a handover request.
- the relay station when the relay station determines whether to perform handover to the target base station, in step A, the relay station transmits information indicating the load status of the relay station together with the handover request.
- the relay station is a donor base station list that is a list of donor base station candidate base stations or an adjacent base station list that is a list of adjacent base stations. And determining the target base station based on: the donor base station list or the neighboring base station list for each of the donor base station candidate base station or the neighboring base station, It includes at least one information of cell direction, capacity, and cell size.
- the donor base station transmits information indicating the load status of the relay station together with the handover request.
- a communication control method holds a donor base station list, connects to a donor base station existing in the donor base station list, and performs relay transmission between the donor base station and a user terminal.
- a communication control method in a mobile communication system including a relay station for performing a relay station connection to a predetermined base station when handover of the relay station to a base station existing in the donor base station list is impossible Step A of acquiring a donor base station list held by the other relay station from the other relay station.
- the relay station receives, from the predetermined base station, relay station information that is information on other relay stations connected to the predetermined base station prior to the step A. Step C is further included.
- the communication control method includes a step D of transmitting a handover request from the relay station to a target base station, and a handover rejection response when the target base station rejects the handover request.
- the predetermined base station is the target base station, and the target base station transmits the relay station information by including the relay station information in the handover rejection response.
- the relay station receives the relay station information included in the handover rejection response.
- the communication control method further includes a step D of inquiring the predetermined base station about another relay station connected to the predetermined base station.
- a communication control method is applied to a mobile communication system including a base station having a donor base station function and a relay station that performs relay transmission between the base station and a user terminal.
- the base station has a neighbor base station list including an identifier of the neighbor base station, wherein the neighbor base station list is the donor base station for each neighbor base station. It further includes information indicating whether or not it has a function.
- the said base station when the said relay station connects to the said base station, the said base station requests
- the target base station in the handover procedure of the relay station from the base station to the target base station, receives a handover request from the base station, and the target base station receives the donor If the target base station does not have a base station function, the target base station further includes a step E of transmitting, to the base station, information indicating that the target base station does not have the donor base station function together with a rejection response to the handover request.
- the communication control method is a communication control method applied to a mobile communication system in which the base station performs handover determination of a user terminal connected to a base station, and is connected to a donor base station.
- the relay station performs step A for performing handover determination of the relay station that performs relay transmission between the donor base station and the user terminal, and in step A, the relay station performs handover determination of the relay station.
- the relay station when the communication control method determines that the handover to the target base station is performed in the step A, the relay station issues a handover request for requesting acceptance of the relay station. It further has a step B of transmitting.
- the relay station transmits the handover request to the target base station using a network interface established between the relay station and the target base station. including.
- the target base station requests information for handover of the relay station from the donor base station in response to reception of the handover request from the relay station.
- step D in which the donor base station transmits information for handover of the relay station to the target base station in response to a request from the target base station.
- handover of the relay station is performed using the network interface. Further comprising a step E of transmitting a handover permission response including information for the relay station to the relay station.
- the relay station in Step B, includes one or more identifiers of the target base station in the handover request and transmits the handover request to the donor base station.
- the relay station prior to step B, in the communication control method, responds to a handover request from the relay station to the donor base station and / or the target base station. It further includes the step of inquiring whether or not it is possible.
- FIG. 1 is a configuration diagram of a mobile communication system according to this embodiment.
- a mobile communication system includes a user terminal (UE) 100, a base station (eNB: evolved Node-B) 200, a movable relay station (MRN: Mobile Relay Node) 300, A mobility management device (MME: Mobility Management Entity) / gateway device (S-GW: Serving Gateway) 400 and an operation and maintenance device (OAM: Operation and Maintenance) 500.
- UE user terminal
- eNB evolved Node-B
- MRN Mobile Relay Node
- MME Mobility Management Entity
- S-GW Serving Gateway
- OAM Operation and Maintenance
- the eNB 200 and the MRN 300 are network devices included in a radio access network (E-UTRAN: Evolved-UMTS Terrestrial Radio Access Network) 10.
- E-UTRAN Evolved-UMTS Terrestrial Radio Access Network
- the MME / S-GW 400 and the OAM 500 are network devices included in a core network (EPC: Evolved Packet Core) 20.
- EPC Evolved Packet Core
- the UE 100 is a movable wireless communication device possessed by a user.
- the UE 100 performs radio communication with a cell (referred to as a “serving cell”) that has established a connection in a connection state corresponding to a state during communication.
- a serving cell a cell that has established a connection in a connection state corresponding to a state during communication.
- the “cell” is used as a term indicating the minimum unit of the radio communication area, and is also used as a function of performing radio communication with the UE 100.
- the eNB 200 may be referred to as a cell.
- the handover procedure includes a handover preparation stage (Preparation), a handover execution stage (Execution), and a handover completion stage (Completion).
- the handover source cell is called a “source cell”, and the handover destination cell is called a “target cell”.
- the handover source eNB 200 is referred to as a “source eNB”, and the handover destination eNB 200 is referred to as a “target eNB”.
- the eNB 200 is a fixed wireless communication device installed by a communication carrier, and is, for example, a macro base station (MeNB) or a pico base station (PeNB). Alternatively, the eNB 200 may be a home base station (HeNB) that can be installed indoors. The eNB 200 forms a cell. The eNB 200 performs radio communication with the UE 100.
- MeNB macro base station
- PeNB pico base station
- HeNB home base station
- the eNB 200 forms a cell.
- the eNB 200 performs radio communication with the UE 100.
- ENB 200 has the right to make a handover decision for UE 100 under its control. Specifically, the eNB 200 determines whether or not to perform a handover from the serving cell to another cell based on a measurement report (Measurement Report) from the UE 100. The eNB 200 maintains a list of neighboring eNBs (neighboring cells) (hereinafter referred to as “neighboring eNB list”) for handover control of the UE 100.
- neighboring eNB list neighboring eNBs
- the eNB 200 can establish a connection with the MRN 300 and operate as a donor of the MRN 300.
- a donor base station For example, an eNB 200 that supports a release after 3GPP Release 10 has a DeNB function as an optional function, but an eNB 200 that supports an earlier release does not have a DeNB function.
- eNB200 (HeNB) with low processing capability may not have a DeNB function.
- the eNB 200 communicates with the EPC 20 (MME / S-GW 400) on the S1 interface, which is a logical communication path with the EPC 20.
- the S1 interface is also established between the eNB 200 (DeNB 200-1) that operates as a donor of the MRN 300 and the MRN 300.
- the MRN 300 can communicate with the EPC 20 on the S1 interface via the DeNB 200-1.
- the MME is provided corresponding to a control plane that handles control information, and performs various types of mobility management and authentication processing for the UE 100.
- the S-GW is provided corresponding to a user plane that handles user data, and performs transfer control of user data transmitted and received by the UE 100.
- ENB200 communicates with the said adjacent eNB200 on the X2 interface which is a logical communication path between adjacent eNB200.
- the X2 interface is also established between the eNB 200 (DeNB 200-1) that operates as a donor of the MRN 300 and the MRN 300.
- the MRN 300 can communicate with the neighboring eNB 200-2 over the X2 interface via the DeNB 200-1.
- the S1 interface and / or the X2 interface corresponds to a network interface.
- the MRN 300 is a movable wireless communication device installed on a moving body such as a train or a bus.
- the MRN 300 holds a list of eNBs 200 (cells) that can be used as DeNBs (hereinafter referred to as “DeNB list”).
- DeNB list a list of eNBs 200 (cells) that can be used as DeNBs.
- the MRN 300 acquires the DeNB list from the OAM 500 when it starts up.
- the MRN 300 establishes a connection with the eNB 200 existing in the DeNB list (Connect), and performs radio communication with the eNB 200 (DeNB 200-1) that has established the connection. Then, the MRN 300 performs relay transmission between the UE 100 under its control and the DeNB 200-1.
- the MRN 300 is basically the same as the UE 100 from the viewpoint of the DeNB 200-1, and is similar to the eNB 200 from the viewpoint of the UE 100. That is, the MRN 300 has both the properties of the UE 100 and the properties of the eNB 200.
- connection with the new DeNB is established after the transition from the connection state to the idle state (Disconnect), or the connection with the new DeNB while maintaining the connection state.
- Disconnect the connection state to the idle state
- the connection with the new DeNB while maintaining the connection state.
- the former case Connect / Disconnect
- the latter case handover
- the MRN 300 has a handover decision right for the UE 100 under its control. Specifically, the MRN 300 determines whether or not to perform handover from the serving cell to another cell based on a measurement report (Measurement Report) from the UE 100.
- the eNB 200 maintains a neighboring eNB list for the handover control of the UE 100.
- FIG. 2 is a protocol stack diagram of the Un interface.
- layer 1 is a physical (PHY) layer.
- Layer 2 includes a MAC (Medium Access Control) layer, an RLC (Radio Link Control) layer, and a PDCP (Packet Data Convergence Protocol) layer.
- Layer 3 includes an RRC (Radio Resource Control) layer.
- the physical layer performs data encoding / decoding, modulation / demodulation, antenna mapping / demapping, and resource mapping / demapping.
- the physical layer provides a transmission service to an upper layer using a physical channel. Data is transmitted through a physical channel between the physical layer of the MRN 300 and the physical layer of the DeNB 200-1.
- the physical layer is connected to the MAC layer through a transport channel.
- the MAC layer performs data priority control, retransmission processing by hybrid ARQ (HARQ), and the like. Data is transmitted via the transport channel between the MAC layer of the MRN 300 and the MAC layer of the DeNB 200-1.
- the MAC layer of the DeNB 200-1 includes a MAC scheduler that determines a transport format and resource blocks for uplink and downlink.
- the transport format includes a transport block size, a modulation and coding scheme (MCS), and antenna mapping.
- the RLC layer transmits data to the RLC layer on the receiving side using the functions of the MAC layer and the physical layer. Data is transmitted via the logical channel between the RLC layer of the MRN 300 and the RLC layer of the DeNB 200-1.
- the PDCP layer performs header compression / decompression and encryption / decryption.
- the RRC layer is defined only in the control plane. Data is transmitted between the RRC layer of the MRN 300 and the RRC layer of the DeNB 200-1 via a radio bearer.
- the RRC layer controls the logical channel, the transport channel, and the physical channel according to establishment, re-establishment, and release of the radio bearer. If there is an RRC connection between the RRC of the MRN 300 and the RRC of the DeNB 200-1, the MRN 300 is in the “connected state”, otherwise the MRN 300 is in the “idle state”.
- the NAS (Non-Access Stratum) layer located above the RRC layer is provided in the MRN 300 and the MME 300, and performs session management, mobility management, and the like.
- FIG. 3 is a protocol stack diagram regarding the X2 interface established between the MRN 300 and the neighboring eNB 200-2. Here, the control plane will be described.
- IP Internet Protocol
- SCTP Stream Control Transmission Protocol
- X2-AP X2 Application Protocol
- the X2 message transmitted by the MRN 300 can be relayed by the DeNB 200-1 and transmitted to the neighboring eNB 200-2. Further, the X2 message transmitted by the neighboring eNB 200-2 can be relayed by the DeNB 200-1 and transmitted to the MRN 300.
- L1 and L2 between the MRN 300 and the DeNB 200-1 are the same as the L1 and L2 of the Un interface.
- FIG. 4 is a protocol stack diagram related to the S1 interface established between the MRN 300 and the MME 400. As shown in FIG. 4, the S1 interface differs from the X2 interface in that S1-AP is provided instead of X2-AP.
- FIG. 5 is a configuration diagram of a radio frame used in the mobile communication system (LTE system) according to the present embodiment.
- the LTE system employs OFDMA (Orthogonal Frequency Division Multiplexing Access) for the downlink, and SC-FDMA (Single Carrier Division Multiple Access) for the uplink.
- OFDMA Orthogonal Frequency Division Multiplexing Access
- SC-FDMA Single Carrier Division Multiple Access
- the radio frame is composed of 10 subframes arranged in the time direction, and each subframe is composed of two slots arranged in the time direction.
- the length of each subframe is 1 ms, and the length of each slot is 0.5 ms.
- Each subframe includes a plurality of resource blocks (RB) in the frequency direction and includes a plurality of symbols in the time direction.
- a guard interval called a cyclic prefix (CP) is provided at the head of each symbol.
- the section of the first few symbols of each subframe is a control region mainly used as a physical downlink control channel (PDCCH).
- the remaining section of each subframe is a data area mainly used as a physical downlink shared channel (PDSCH).
- a different reference signal (RS) is transmitted for each cell.
- both ends in the frequency direction in each subframe are control regions mainly used as a physical uplink control channel (PUCCH). Further, the central portion in the frequency direction in each subframe is a data region mainly used as a physical uplink shared channel (PUSCH).
- PUCCH physical uplink control channel
- PUSCH physical uplink shared channel
- the radio frame includes a plurality of MBSFN (MBMS Single Frequency Network) subframes.
- the MRN 300 performs communication with the DeNB 200-1 using the MBSFN subframe.
- FIG. 6 is a block diagram of the UE 100. As illustrated in FIG. 6, the UE 100 includes a radio transmission / reception unit 110, a storage unit 120, and a control unit 130.
- the wireless transceiver 110 transmits and receives wireless signals.
- the storage unit 120 stores various information used for control by the control unit 130.
- the control unit 130 controls various functions of the UE 100.
- the control unit 130 controls the operation of the UE 100 described above.
- FIG. 7 is a block diagram of the eNB 200. As illustrated in FIG. 7, the eNB 200 includes a radio transmission / reception unit 210, a network communication unit 220, a storage unit 230, and a control unit 240.
- the wireless transmission / reception unit 210 transmits / receives a wireless signal. Moreover, the radio
- the network communication unit 220 communicates with the MME / S-GW 400 over the S1 interface.
- the network communication unit 220 performs communication with the adjacent eNB 200 on the X2 interface.
- the storage unit 230 stores various information used for control by the control unit 240.
- the storage unit 230 stores (holds) the neighboring eNB list.
- the control unit 240 controls various functions of the eNB 200.
- the control unit 240 controls the operation of the eNB 200 described above and controls the operation of the eNB 200 described later.
- FIG. 8 is a block diagram of the MRN 300. As illustrated in FIG. 8, the MRN 300 includes an eNB radio transmission / reception unit 310, an UE radio transmission / reception unit 320, a storage unit 330, and a control unit 340.
- the MRN 300 includes an eNB radio transmission / reception unit 310, an UE radio transmission / reception unit 320, a storage unit 330, and a control unit 340.
- the eNB radio transmission / reception unit 310 receives a radio signal from the eNB 200 and transmits the radio signal to the eNB 200.
- the UE radio transceiver 320 receives a radio signal from the UE 100 and transmits a radio signal to the UE 100.
- the UE radio transceiver unit 320 forms a cell.
- the storage unit 330 stores various information used for control by the control unit 340. In addition, the storage unit 330 stores (holds) a neighboring eNB list for handover control of the UE 100 and a DeNB list for determining a DeNB to which the MRN 300 should establish a connection.
- Control unit 340 controls various functions of MRN 300. For example, control unit 340 controls the operation of MRN 300 described above and controls the operation of MRN 300 described later.
- the control unit 340 can determine any DeNB candidate existing in the DeNB list as a DeNB by measuring a radio signal (reference signal) received by the eNB radio transmission / reception unit 310.
- the MRN 300 may have a positioning system (for example, a GPS receiver 350) for acquiring its own position information.
- the MRN 300 can estimate its moving speed based on its own position information.
- the MRN 300 that holds the DeNB list connects to the DeNB 200-1 existing in the DeNB list, and performs relay transmission between the DeNB 200-1 and the UE 100 identifies the adjacent eNB 200. Then, the specified neighboring eNB 200 is inquired as to whether the MRN 300 can be accepted, and the DeNB list is updated according to the inquiry result.
- the MRN 300 specifies a neighboring eNB 200 that does not exist in the DeNB list.
- the MRN 300 updates the DeNB list so as to add the specified neighboring eNB 200 when the inquiry result of the identified neighboring eNB 200 indicates that the MRN 300 is accepted.
- the MRN 300 specifies the neighboring eNB 200 existing in the DeNB list.
- the MRN 300 updates the DeNB list so that the specified neighboring eNB 200 is invalidated (excluded) when the inquiry result of the identified neighboring eNB 200 indicates that the MRN 300 is not accepted.
- FIG. 9 is a sequence diagram of the operation pattern 1 according to the present embodiment.
- step S101 the OAM 500 notifies the MRN 300 via the DeNB 200-1 of the neighboring eNB list (NL) for handover control of the UE 100. Not only the case of notifying the entire neighboring eNB list, but only the portion related to the change may be notified.
- step S102 the MRN 300 updates the held neighboring eNB list (NL) with the neighboring eNB list received from the OAM 500.
- step S103 the MRN 300 compares the neighboring eNB list updated in step S102 with the held DeNB list. Specifically, the MRN 300 searches for a neighboring eNB that exists in the neighboring eNB list and does not exist in the DeNB list.
- the description will be made assuming that the eNB 200-2 is specified as a neighboring eNB that exists in the neighboring eNB list and does not exist in the DeNB list.
- step S104 the MRN 300 inquires of the eNB 200-2 specified in step S103 whether or not it has the DeNB function on the X2 interface.
- step S105 the eNB 200-2 confirms whether or not the eNB 200-2 has the DeNB function in response to the inquiry from the MRN 300.
- step S106 the eNB 200-2 notifies the MRN 300 on the X2 interface whether or not the eNB 200-2 has the DeNB function.
- step S107 the MRN 300 confirms whether the eNB 200-2 has a DeNB function.
- step S108 the MRN 300 updates the DeNB list to add the eNB 200-2. Specifically, the MRN 300 adds the identifier (cell ID) of the eNB 200-2 to the DeNB list.
- step S109 the MRN 300 notifies the OAM 500 of the DeNB list updated in step S108 via the DeNB 200-1. Not only the case where the entire updated DeNB list is notified, but only the part related to the update may be notified.
- the operation may be performed periodically in a period in which the moving speed of the MRN 300 exceeds the threshold value.
- the MRN 300 does not include the neighboring cell (neighboring eNB) detected by the measurement for the received reference signal in the DeNB list, or is the neighboring cell having the highest reference signal received power (RSRP) in the measurement for the received reference signal.
- An operation for updating the DeNB list may be started by using the fact that (neighboring eNB) is not included in the DeNB list, and the neighboring cell (neighboring eNB) may be inquired.
- FIG. 10 is a sequence diagram of an operation pattern 2 according to the present embodiment.
- step S111 the OAM 500 notifies the MRN 300 via the DeNB 200-1 of the neighboring eNB list for handover control of the UE 100. Not only the case of notifying the entire neighboring eNB list, but only the portion related to the change may be notified.
- step S112 the MRN 300 updates the held neighboring eNB list with the neighboring eNB list received from the OAM 500.
- step S113 the MRN 300 compares the neighboring eNB list updated in step S112 with the held DeNB list. Specifically, the MRN 300 searches for a neighboring eNB that exists in the neighboring eNB list and does not exist in the DeNB list.
- the description will be made assuming that the eNB 200-2 is specified as a neighboring eNB that exists in the neighboring eNB list and does not exist in the DeNB list.
- the MRN 300 grasps its own load status.
- the load status includes the number of UEs 100 accommodated by the MRN 300 (specifically, the number of UEs 100 connected to the MRN 300), the amount of traffic handled by the MRN 300, and the like.
- ascertain a potential load condition for example, processing capacity, such as the maximum number of accommodation UEs and a maximum traffic amount, not only an actual load condition.
- step S114 the MRN 300 notifies the eNB 200-2 identified in step S113 of the load status on the X2 interface and inquires whether the MRN 300 can be accepted. At that time, the MRN 300 may also notify that the subject that made the inquiry is “MRN”.
- step S115 the eNB 200-2 determines whether or not the MRN 300 can be accepted in response to an inquiry from the MRN 300. Specifically, the eNB 200-2 compares the margin based on its own load status with the load status of the MRN 300, and determines whether there is no problem even if the connection with the MRN 300 is established.
- step S116 the eNB 200-2 notifies the MRN 300 of whether or not the MRN 300 can be accepted on the X2 interface.
- step S117 the MRN 300 confirms whether the result of the inquiry to the eNB 200-2 is “acceptance permitted” or “acceptance rejection”.
- step S118 the MRN 300 updates the DeNB list to add the eNB 200-2. Specifically, the MRN 300 adds the identifier (cell ID) of the eNB 200-2 to the DeNB list.
- Step S119 the MRN 300 notifies the OAM 500 of the DeNB list updated in Step S118 via the DeNB 200-1. Not only the case where the entire updated DeNB list is notified, but only the part related to the update may be notified.
- FIG. 11 is a sequence diagram of the operation pattern 3 according to the present embodiment.
- step S121 the MRN 300 searches for a neighboring eNB existing in the neighboring eNB list, for example, triggered by a significant change in its load status.
- eNB 200-2 is specified as the neighboring eNB existing in the neighboring eNB list.
- the MRN 300 grasps its own load status.
- the load status includes the number of UEs 100 accommodated by the MRN 300 (specifically, the number of UEs 100 connected to the MRN 300), the amount of traffic handled by the MRN 300, and the like.
- step S122 the MRN 300 notifies the eNB 200-2 identified in step S121 of the load status on the X2 interface and inquires whether the MRN 300 can be accepted. At that time, the MRN 300 may also notify that the subject that made the inquiry is “MRN”.
- step S123 the eNB 200-2 determines whether or not the MRN 300 can be accepted in response to an inquiry from the MRN 300. Specifically, the eNB 200-2 compares the margin based on its own load status with the load status of the MRN 300, and determines whether there is no problem even if the connection with the MRN 300 is established.
- step S124 the eNB 200-2 notifies the MRN 300 of whether or not the MRN 300 can be accepted on the X2 interface.
- step S125 the MRN 300 confirms whether the result of the inquiry to the eNB 200-2 is “acceptance permitted” or “acceptance rejection”.
- step S126 the MRN 300 updates the DeNB list to invalidate the eNB 200-2. Specifically, the MRN 300 deletes the identifier (cell ID) of the eNB 200-2 from the DeNB list or temporarily sets it to invalid.
- step S127 the MRN 300 notifies the OAM 500 of the DeNB list updated in step S126 via the DeNB 200-1. Not only the case where the entire updated DeNB list is notified, but only the part related to the update may be notified.
- the DeNB list is held, connected to the DeNB 200-1 existing in the DeNB list, and relay transmission is performed between the DeNB 200-1 and the UE 100.
- the MRN 300 identifies the neighboring eNB 200, inquires whether the identified neighboring eNB 200 can accept the MRN 300, and updates the DeNB list according to the inquiry result. Thereby, even when the MRN 300 moves, the DeNB list can be adapted to the situation of the movement destination.
- the MRN 300 specifies a neighboring eNB 200 that does not exist in the DeNB list.
- the MRN 300 updates the DeNB list so as to add the specified neighboring eNB 200 when the inquiry result of the identified neighboring eNB 200 indicates that the MRN 300 is accepted.
- the new DeNB candidate can be added to the DeNB list.
- the MRN 300 specifies the neighboring eNB 200 existing in the DeNB list.
- the MRN 300 updates the DeNB list so as to invalidate the specified neighboring eNB 200 when the inquiry result of the identified neighboring eNB 200 indicates that the MRN 300 is not accepted.
- the eNB 200 that becomes unable to accept the MRN 300 can be prevented from being a DeNB candidate.
- the inquiry includes information indicating that the inquiry source is “MRN”.
- the neighboring eNB 200 can determine whether or not it is acceptable after recognizing that the inquiry source is “MRN”.
- the MRN 300 specifies the neighboring eNB 200 that does not exist in the DeNB list based on the comparison result between the neighboring eNB list notified from the OAM 500 via the DeNB 200-1 and the DeNB list held by the MRN 300. Thereby, the neighboring eNB 200 that does not exist in the DeNB list can be appropriately identified.
- the MRN 300 specifies the neighboring eNB 200 that does not exist in the DeNB list based on the radio signal received by the MRN 300 from the neighboring eNB 200. Thereby, the neighboring eNB 200 that does not exist in the DeNB list can be appropriately identified.
- the MRN 300 inquires of the identified neighboring eNB 200 whether or not it has the DeNB function. Thereby, only the neighboring eNB 200 having the DeNB function can be added to the DeNB list.
- the MRN 300 notifies the specified neighboring eNB 200 of the load status of the MRN 300. Thereby, the neighboring eNB 200 can determine whether or not the MRN 300 can be accepted based on its own load status and the load status of the MRN 300.
- the MRN 300 notifies the OAM 500 of all or part of the updated DeNB list via the DeNB 200-1. Thereby, the OAM 500 can notify the other updated MRN 300 around the DeNB 200-1 of the updated DeNB list. Therefore, the other MRN 300 can use the optimized DeNB list. Alternatively, the OAM 500 may hold the DeNB list as a backup, and notify the MRN 300 of the DeNB list as necessary.
- the MRN 300 that connects to the DeNB 200-1 and performs relay transmission between the DeNB 200-1 and the UE 100 The MRN 300 itself makes the handover decision. Then, the MRN 300 transmits a handover request to the target eNB 200 using the X2 interface established between the MRN 300 and the target eNB 200.
- FIG. 12 is a sequence diagram of the operation pattern 1 according to the present embodiment. In the initial state of this sequence, it is assumed that the MRN 300 is connected to the DeNB 200-1 and is performing relay transmission.
- step S200 the MRN 300 collates the measurement result for the received reference signal with the held DeNB list.
- step S201 the MRN 300 performs handover determination according to the collation result in step S200. For example, when a DeNB candidate whose RSRP is higher than that of the currently connected DeNB 200-1 is present in the DeNB list, the MRN 300 determines the DeNB candidate as the target eNB.
- the description will be made assuming that the eNB 200-2 is determined as the target eNB by such handover determination.
- step S202 the MRN 300 inquires of the eNB 200-2 on the X2 interface whether or not the handover request from the MRN 300 can be handled. Note that step S202 may be performed before step S201.
- step S203 in response to the inquiry from the MRN 300, the eNB 200-2 notifies the MRN 300 whether or not it can respond to the handover request from the MRN 300 on the X2 interface.
- the description will be made assuming that the eNB 200-2 can respond to the handover request from the MRN 300.
- step S204 the MRN 300 transmits a handover request for requesting its own acceptance to the eNB 200-2 on the X2 interface.
- the handover request includes information indicating that the transmission source of the handover request is “MRN”.
- MRN the transmission source of the handover request
- the preparation stage in the handover procedure is started by transmitting the handover request.
- the DeNB 200-1 is a “source eNB”.
- step S205 the eNB 200-2 determines whether to permit or reject the handover request based on the handover request from the MRN 300.
- the description will be made assuming that the eNB 200-2 determines that the handover request is permitted.
- step S206 the eNB 200-2 requests information for handover of the MRN 300 from the DeNB 200-1 on the X2 interface.
- the DeNB 200-1 transmits information for handover of the MRN 300 to the eNB 200-2 on the X2 interface together with the permission response (Ack) to the request from the eNB 200-2.
- the information for MRN300 handover includes MRN300 X2 signaling context reference, S1 EPC signaling context reference, target cell ID, RRC context, AS configuration, E-RAB, and so on.
- step S208 the eNB 200-2 notifies the MRN 300 of information necessary for establishing a connection with the eNB 200-2 together with an authorization response (Ack) to the handover request from the MRN 300 on the X2 interface.
- Information necessary for performing communication with the eNB 200-2 is, for example, a new C-RNTI and a security algorithm identifier, and optionally a dedicated RACH preamble and SIB.
- step S209 the MRN 300 disconnects from the DeNB 200-1 in response to the reception of the handover permission response from the eNB 200-2. Thereafter, the MRN 300 performs processing (random access processing, RRC connection establishment processing, etc.) for establishing a connection with the eNB 200-2 (step S212). On the other hand, the DeNB 200-1 performs processing (data forwarding) for transferring data not transmitted to the MRN 300 to the eNB 200-2 over the X2 interface (steps S210 and S211).
- the eNB 200-2 becomes a new DeNB of the MRN 300.
- FIG. 13 is a sequence diagram of an operation pattern 2 according to the present embodiment. Here, only differences from the operation pattern 1 according to the present embodiment will be described.
- the MRN 300 transmits information indicating the load status of the MRN 300 together with the handover request (step S204-1).
- the load status refers to the number of UEs 100 accommodated by the MRN 300 (specifically, the number of UEs 100 connected to the MRN 300), the amount of traffic handled by the MRN 300, and the like. Not only the actual load situation but also a potential load situation (for example, processing capacity such as the maximum number of accommodated UEs and maximum traffic amount) may be used.
- the target eNB 200 After receiving the information indicating the load status of the MRN 300 together with the handover request, the target eNB 200 determines whether to permit the handover request based on the information indicating the load status of the MRN 300 (step S205-1).
- the eNB 200-2 compares the margin based on its own load status with the load status of the MRN 300, and determines whether or not a problem occurs even if the connection with the MRN 300 is established.
- the MRN 300 performs processing for adjusting the timing of transmitting a handover request before transmitting the handover request (step S204).
- the MRN 300 adjusts the transmission timing of the handover request to be earlier than usual when the moving speed of the MRN 300 exceeds the threshold. In addition, when the moving speed of the MRN 300 becomes equal to or less than the threshold, the MRN 300 returns the handover request transmission timing to the normal timing.
- the MRN 300 determines the DeNB candidate as the target eNB when there is a DeNB candidate having a higher RSRP than the currently connected DeNB 200-1. In such a case, the MRN 300 corrects (offsets) the RSRP of the currently connected DeNB 200-1 low or corrects the RSRP of the DeNB candidate high (offset) if the moving speed of the MRN 300 exceeds the threshold. By doing so, a handover trigger is likely to occur, and the timing of the handover request can be advanced.
- the MRN 300 determines the DeNB candidate as the target eNB when the RSRP of the DeNB candidate exceeds a threshold value.
- the MRN 300 can easily correct (offset) the RSRP of the DeNB candidate or lower the threshold value, so that a handover trigger is likely to occur, and the handover request timing can be advanced.
- the MRN 300 may transmit a handover request without inquiring whether or not the handover request from the MRN 300 can be handled (step S202).
- FIG. 14 is a configuration diagram of the DeNB list used in the operation pattern 4.
- the DeNB list used in the operation pattern 4 includes information on a position, a cell direction, a capacity, and a cell size for each DeNB candidate (its identifier).
- the MRN 300 determines the target eNB based on such a DeNB list. Specifically, it is determined whether the DeNB candidate is appropriate as the target eNB under the following conditions (all or a part).
- the MRN 300 determines that the DeNB candidate is appropriate.
- the MRN 300 determines that the DeNB candidate is appropriate.
- the MRN 300 determines that the DeNB candidate is appropriate.
- the MRN 300 determines that the DeNB candidate is appropriate.
- the list of DeNB candidates may be updated.
- the operation in this case will be described in the third embodiment.
- the MRN 300 may make a handover determination using the neighboring eNB list.
- the UE 100 is connected to the DeNB 200-1 and between the DeNB 200-1 and the UE 100.
- the MRN 300 that performs relay transmission performs the handover determination of the MRN 300 by the MRN 300 itself.
- MRN300 can perform the optimal handover judgment according to its own situation, the situation of DeNB candidates, and the like.
- radio resources for the measurement report can be saved.
- the MRN 300 inquires of the target eNB 200 whether or not the handover request from the MRN 300 can be handled. Thereby, the MRN 300 can transmit the handover request to the target eNB 200 after confirming that it can respond to its own handover request.
- the MRN 300 transmits a handover request to the target eNB 200 using the X2 interface established between the MRN 300 and the target eNB 200.
- a handover request can be transmitted from the MRN 300 to the target eNB 200 without making a handover decision by the DeNB 200-1, so that the load on the DeNB 200-1 can be reduced and a quick handover can be performed.
- the handover request includes information indicating that the transmission source of the handover request is “MRN”. Thereby, the target eNB 200 can determine whether or not to permit the handover request after recognizing that the transmission source of the handover request is “MRN”.
- the target eNB 200 In response to receiving the handover request from the MRN 300, the target eNB 200 requests information for the handover of the MRN 300 from the DeNB 200-1.
- the DeNB 200-1 transmits information for handover of the MRN 300 to the target eNB 200 in response to a request from the target eNB 200.
- the target eNB 200 can acquire information for the MRN 300 handover from the DeNB 200-1.
- the target eNB 200 receives information for handover of the MRN 300 from the DeNB 200-1, and then transmits a handover permission response (Handover Request Ack) including information for handover of the MRN 300 to the MRN 300 using the X2 interface.
- a handover permission response can be transmitted from the target eNB 200 to the MRN 300 without making a handover determination by the DeNB 200-1, so that the load on the DeNB 200-1 can be reduced and a quick handover can be performed.
- the MRN 300 when transmitting a handover request to the target eNB 200 in the handover procedure of the MRN 300 to the target eNB 200, transmits information indicating the load status of the MRN 300 together with the handover request.
- the target eNB 200 after receiving the information indicating the load status of the MRN 300 together with the handover request, determines whether to permit the handover request based on the information indicating the load status of the MRN 300. Thereby, the target eNB 200 can determine whether or not to permit the handover request based on its own load status and the load status of the MRN 300.
- the MRN 300 transmits a handover request at a timing according to its moving speed. Thereby, for example, the frequency of handover failures when the MRN 300 moves at high speed can be reduced.
- the MRN 300 determines the target eNB 200 based on the DeNB list that is a list of DeNB candidates.
- the DeNB list includes at least one piece of information on position, cell direction, capacity, and cell size for each DeNB candidate. Accordingly, the MRN 300 can determine whether or not to set the DeNB candidate as the target eNB in consideration of at least one of the position, cell direction, capacity, and cell size of the DeNB candidate.
- the MRN 300 when the MRN 300 cannot be handed over to a DeNB candidate existing in the DeNB list, the MRN 300 uses the other MRN to store the DeNB list held by another MRN connected to the predetermined eNB (predetermined base station). Get from.
- predetermined eNB means “current DeNB” or “DeNB list” when there is no appropriate DeNB candidate in the DeNB list as the target eNB as described in the operation pattern 4 of the second embodiment.
- the following operation pattern 1 assumes the former case, and the following operation pattern 2 assumes the latter case.
- FIG. 15 is a sequence diagram of an operation pattern 1 according to the present embodiment.
- eNB 200-2 and eNB 200-3 which are DeNB candidates existing in the DeNB list, are “predetermined eNBs” when there is no DeNB candidate suitable as the target eNB in the DeNB list.
- Other MRN1 (MRN300-1) and MRN2 (MRN300-2) are connected to eNB200-2.
- step S301 the MRN 300 determines that all DeNB candidates existing in the DeNB list are inappropriate as the target eNB.
- step S302 the MRN 300 queries the eNB 200-2 and the eNB 200-3, which are DeNB candidates existing in the DeNB list, about the currently connected MRN (or RN) on the X2 interface.
- step S303 the eNB 200-2 and the eNB 200-3 notify the MRN 300 of the connected MRN on the X2 interface.
- eNB 200-2 notifies MRN 300 of the identifier of MRN 300-1 and the identifier of MRN 300-2.
- the eNB 200-3 notifies the MRN 300 that there is no connected MRN.
- step S304 based on the notification from the eNB 200-2, the MRN 300 accesses each of the MRN 300-1 and the MRN 300-2 on the X2 interface and requests a DeNB list.
- each of the MRN 300-1 and the MRN 300-2 notifies (reports) the DeNB list held by itself to the MRN 300 via the X2 interface.
- step S306 the MRN 300 collates the DeNB list held by itself with the DeNB list received from each of the MRN 300-1 and the MRN 300-2.
- step S307 it is determined whether or not there is a difference between the DeNB list held by itself and the DeNB list received from each of MRN 300-1 and MRN 300-2. Specifically, the MRN 300 confirms whether there is a DeNB candidate that does not exist in the DeNB list held by itself in the DeNB list received from each of the MRN 300-1 and the MRN 300-2.
- step S308 the MRN 300 updates its own DeNB list to add the DeNB candidate. Specifically, the identifier of the DeNB candidate is added to its own DeNB list. As a result, it becomes possible to start handover with the DeNB candidate as the target eNB.
- FIG. 16 is a sequence diagram of an operation pattern 2 according to the present embodiment.
- the eNB 200-2 is set as the “predetermined eNB” when a handover request from the MRN 300 is rejected by the eNB 200-2 will be described.
- step S311 the MRN 300 transmits a handover request to the eNB 200-2 over the X2 interface.
- step S312 the eNB 200-2 determines whether to permit or reject the MRN 300 handover request.
- the description will be made assuming that it is determined that the handover request of MRN 300 is rejected.
- step S313 the eNB 200-2 notifies the MRN 300 of the MRN (or RN) that is connected to the eNB 200-2 on the X2 interface together with the handover rejection response (Nack). Thereafter, the same operation as the operation after step S304 of the operation pattern 1 is performed.
- the MRN 300 receives information about other MRNs connected to the eNB 200-2 from the eNB 200-2. Thereby, the MRN 300 can grasp other MRNs connected to the eNB 200-2.
- the MRN 300 inquires of the eNB 200-2 about other MRNs connected to the eNB 200-2 prior to receiving information about the other MRNs connected to the eNB 200-2 from the eNB 200-2. Thereby, the eNB 200-2 can notify the MRN 300 of the MRN connected to the eNB 200-2 in response to the request from the MRN 300.
- the eNB 200-2 notifies the MRN 300 of information on the currently connected MRN together with a handover rejection response (Nack) to the MRN 300. Thereby, the MRN 300 can grasp other MRNs connected to the eNB 200-2.
- Nack handover rejection response
- the MRN 300 is handed over by the MRN 300, but in this embodiment, the MRN 300 is handed over by the DeNB 200-1. That is, in this embodiment, the MRN 300 is handed over by applying a normal handover procedure in LTE.
- the DeNB 200-1 determines whether to perform a handover of the MRN 300 to an eNB (cell) existing in the neighboring eNB list based on the measurement report from the MRN 300.
- the neighboring eNB list is configured and managed as follows.
- FIG. 17 is a configuration diagram of the neighboring eNB list according to the present embodiment.
- the neighboring eNB list further includes information indicating whether or not the neighboring eNB has a DeNB function for each neighboring eNB (cell ID (TCI) thereof). For example, for a neighboring eNB that does not have a DeNB function, a flag indicating that the DeNB function is not provided is set. Other items are the same as those in the adjacent eNB list (referred to as “adjacent relationship table (NRT)”) in the specification.
- NRT adjacent relationship table
- the neighboring eNB list may be updated by an ANR (Automatic Neighbor Relation) function.
- the eNB 200 acquires information related to the neighboring eNB list from the OAM 500, and manages the neighboring eNB list.
- the MRN 300 connects to the DeNB 200-1
- the OAM 500 is requested for information for updating the neighboring eNB list.
- the DeNB 200-1 updates the neighboring eNB list according to information from the OAM 500.
- FIG. 18 is a sequence diagram of operation pattern 1 according to the present embodiment.
- step S401 the MRN 300 transmits a measurement report to the DeNB 200-1.
- step S402 the DeNB 200-1 identifies the neighboring eNB having the DeNB function based on the neighboring eNB list (NL or NRT).
- the DeNB 200-1 determines the target eNB from the neighboring eNBs identified in step S402 based on the measurement report from the MRN 300. For example, the DeNB 200-1 determines the neighboring eNB identified in step S402 and having a high RSRP indicated by the measurement report as the target eNB.
- the description will be made assuming that the eNB 200-2 is determined as the target eNB.
- step S404 the DeNB 200-1 transmits a handover request to the target eNB 200-2 over the X2 interface.
- step S405 the target eNB 200-2 determines whether to permit or reject the handover request from the DeNB 200-1. Thereafter, a normal handover procedure is performed.
- FIG. 19 is a sequence diagram of an operation pattern 2 according to the present embodiment. Here, differences from the operation pattern 1 according to the present embodiment will be described.
- step S401-1 the MRN 300 notifies the DeNB 200-1 of its own load status when transmitting a measurement report to the DeNB 200-1.
- the timing for notifying the load status may be different from the timing of the measurement report. If the DeNB 200-1 knows the load status of the MRN 300, the notification of the load status of the MRN 300 to the DeNB 200-1 can be omitted.
- the load status refers to the number of UEs 100 accommodated by the MRN 300 (specifically, the number of UEs 100 connected to the MRN 300), the amount of traffic handled by the MRN 300, and the like. Not only the actual load situation but also a potential load situation (for example, processing capacity such as the maximum number of accommodated UEs and maximum traffic amount) may be used.
- Steps S402 and S403 are the same as in operation pattern 1.
- step S404-1 the DeNB 200-1 notifies the DeNB 200-1 of the load status of the MRN when transmitting a handover request to the target eNB 200-2 over the X2 interface.
- step S405-1 the target eNB 200-2 determines whether to permit or reject the handover request from the DeNB 200-1, considering the load status of the MRN. Specifically, the eNB 200-2 compares the margin based on its own load status with the load status of the MRN 300, and determines whether there is no problem even if the connection with the MRN 300 is established. Thereafter, a normal handover procedure is performed.
- the neighboring eNB list further includes information indicating whether or not the neighboring eNB has the DeNB function for each neighboring eNB. Accordingly, the eNB 200 (DeNB 200-1) can determine the target eNB 200 from the neighboring eNBs having the DeNB function based on the neighboring eNB list.
- the DeNB 200-1 requests the OAM 500 for information for updating the neighboring eNB list when the MRN 300 is connected to the DeNB 200-1. Then, the DeNB 200-1 updates the neighboring eNB list according to information from the OAM 500. Thereby, before the handover of MRN300 occurs, the neighboring eNB list can be updated.
- the target eNB 200 When the target eNB 200 receives the handover request from the DeNB 200-1, and the target eNB 200 does not have the DeNB function, the target eNB 200 provides information indicating that the target eNB 200 does not have the DeNB function together with a rejection response to the handover request. To -1. Then, the DeNB 200-1 updates the neighboring eNB list in response to receiving from the target eNB 200 information indicating that the DeNB function is not provided. Thereby, a neighbor eNB list
- the DeNB 200-1 transmits information indicating the load status of the MRN 300 to the target eNB 200 together with the handover request.
- the target eNB 200 after receiving the information indicating the load status of the MRN 300 together with the handover request, determines whether to permit the handover request based on the information indicating the load status of the MRN 300. Thereby, the target eNB 200 can determine whether or not to permit the handover request based on its own load status and the load status of the MRN 300.
- the handover procedure according to the second embodiment described above that is, the handover of the MRN 300 is basically performed by the MRN 300, and the DeNB 200-1 also performs the handover determination as in the fourth embodiment described above. Do.
- FIG. 20 is an operation sequence diagram according to the present embodiment. In the initial state of this sequence, it is assumed that the MRN 300 is connected to the DeNB 200-1 and is performing relay transmission.
- step S501 the MRN 300 collates the measurement result for the received reference signal with the held DeNB list.
- step S502 the MRN 300 makes a handover determination according to the collation result in step S501. For example, when a DeNB candidate whose RSRP is higher than that of the currently connected DeNB 200-1 is present in the DeNB list, the MRN 300 determines the DeNB candidate as the target eNB.
- the description will be made assuming that the eNB 200-2 is determined as the target eNB by such handover determination.
- the number of target eNBs determined in step S502 is not limited to one and may be plural.
- step S503 the MRN 300 inquires of the DeNB 200-1 whether or not it can respond to the handover request from the MRN 300. Note that step S503 may be performed before step S502.
- step S504 in response to the inquiry from the MRN 300, the DeNB 200-1 notifies the MRN 300 whether or not it can respond to the handover request from the MRN 300.
- the description will be made assuming that the DeNB 200-1 can respond to the handover request from the MRN 300.
- the MRN 300 transmits a handover request for requesting a handover to the eNB 200-2 to the DeNB 200-1 on the X2 interface.
- the handover request includes the identifier of eNB 200-2.
- the identifiers of the plurality of target eNBs are included.
- the handover request may include information indicating that the transmission source of the handover request is “MRN”.
- the DeNB 200-1 determines whether or not handover is possible for each target eNB 200 based on the handover request (identifier included therein) from the MRN 300. For example, as described in the fourth embodiment, the determination can be made based on the presence or absence of the DeNB function.
- the description will be made assuming that the DeNB 200-1 determines that the handover to the target eNB 200 is possible.
- step S507 the DeNB 200-1 transmits a handover request to the target eNB 200-2 over the X2 interface.
- step S508 the target eNB 200-2 determines whether to permit or reject the handover request from the DeNB 200-1. Thereafter, a normal handover procedure is performed.
- the load state of the MRN 300 can be taken into consideration as in the operation pattern 2 according to the fourth embodiment.
- the handover procedure according to the present embodiment and the handover procedure according to the second embodiment may be properly used.
- the handover procedure according to the present embodiment may be applied.
- the handover procedure according to the second embodiment is applied, and if the elapsed time exceeds the threshold, the present embodiment is applied.
- a handover procedure may be applied.
- the UE 100 is connected to the DeNB 200-1 and between the DeNB 200-1 and the UE 100.
- the MRN 300 that performs relay transmission performs the handover determination of the MRN 300 by the MRN 300 itself. Thereby, the MRN 300 can make an optimum handover determination according to its own situation, that is, in consideration of the circumstances peculiar to the MRN 300.
- the MRN 300 transmits one or more identifiers of the target eNB 200 in the handover request and then transmits the handover request to the DeNB 200-1.
- the DeNB 200-1 determines whether handover is possible for each target eNB 200 based on the handover request from the MRN 300. Thereby, it is possible for the DeNB 200-1 to determine whether or not the target eNB 200 determined by the MRN 300 is appropriate. Therefore, the target eNB 200 can be determined more appropriately.
- the MRN 300 inquires of the DeNB 200-1 whether or not it can respond to the handover request from the MRN 300. As a result, it is possible to transmit a handover request from the MRN 300 to the DeNB 200-1 after confirming that the handover request from the MRN 300 can be handled.
- first to fifth embodiments are not limited to being implemented separately and may be implemented in combination with each other.
- the DeNB list acquisition method described in the third embodiment may be applied to the fifth embodiment.
- the MRN 300 that is a movable relay station has been described as an example, but the present invention may be applied to a relay station that is not movable.
- the DeNB list (DL) and the neighboring eNB It may be necessary to update the list (NL or NRT) or perform relay station handover.
- the communication control method according to the present invention is useful in the mobile communication field because it can support a movable relay station.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
第1実施形態に係る通信制御方法は、ドナー基地局リストを保持しており、前記ドナー基地局リストに存在するドナー基地局に接続し、前記ドナー基地局とユーザ端末との間でリレー伝送を行うリレー局における通信制御方法であって、隣接基地局を特定するステップAと、前記ステップAで特定した前記隣接基地局に対して、前記リレー局の受け入れ可否に関して問い合せるステップBと、前記ステップBでの問い合せ結果に応じて、前記ドナー基地局リストを更新するステップCと、を有する。
本実施形態においては、リリース10以降の3GPP規格(すなわち、LTE Advanced)に基づいて構成される移動通信システムを例に説明する。
図1は、本実施形態に係る移動通信システムの構成図である。図1に示すように、移動通信システムは、ユーザ端末(UE:User Equipment)100と、基地局(eNB:evolved Node-B)200と、移動可能なリレー局(MRN:Mobile Relay Node)300と、モビリティ管理装置(MME:Mobility Management Entity)/ゲートウェイ装置(S-GW:Serving Gateway)400と、運用保守装置(OAM:Operation and Maintenance)500と、を有する。
以下において、UE100、eNB200、及びMRN300それぞれのブロック構成を説明する。
以下において、本実施形態に係る移動通信システムの動作を説明する。
図9は、本実施形態に係る動作パターン1のシーケンス図である。
図10は、本実施形態に係る動作パターン2のシーケンス図である。
図11は、本実施形態に係る動作パターン3のシーケンス図である。
以上説明したように、DeNBリストを保持しており、DeNBリストに存在するDeNB200-1に接続し、DeNB200-1とUE100との間でリレー伝送を行うMRN300は、隣接eNB200を特定し、特定した隣接eNB200に対してMRN300の受け入れ可否に関して問い合せ、問い合せ結果に応じてDeNBリストを更新する。これにより、MRN300が移動する場合であっても、DeNBリストを移動先の状況に適応させることができる。
以下、第2実施形態について、上述した第1実施形態との相違点を説明する。
以下において、本実施形態に係る移動通信システムの動作を説明する。
図12は、本実施形態に係る動作パターン1のシーケンス図である。本シーケンスの初期状態では、MRN300は、DeNB200-1に接続してリレー伝送を実行中であるとする。
図13は、本実施形態に係る動作パターン2のシーケンス図である。ここでは、本実施形態に係る動作パターン1との相違点のみ説明する。
本実施形態に係る動作パターン3では、MRN300は、ハンドオーバ要求を送信(ステップS204)する前において、ハンドオーバ要求を送信するタイミングを調整するための処理を行う。
本実施形態に係る動作パターン4では、MRN300は、付加情報が付されたDeNBリストを使用してハンドオーバ判断(ステップS201)を行う。
以上説明したように、eNB200に接続するUE100のハンドオーバ判断をeNB200が行う移動通信システムにおいて、DeNB200-1に接続し、DeNB200-1とUE100との間でリレー伝送を行うMRN300は、MRN300のハンドオーバ判断をMRN300自身で行う。これにより、MRN300は、自身の状況やDeNB候補の状況などに応じて、最適なハンドオーバ判断を行うことができる。また、MRN300からDeNB200-1への測定報告を行うことなく、ハンドオーバ判断を実施できるため、測定報告のための無線リソースを節約できる。
以下、第3実施形態について、上述した各実施形態との相違点を説明する。本実施形態は、第2実施形態の応用例に相当する。
以下において、本実施形態に係る移動通信システムの動作を説明する。
図15は、本実施形態に係る動作パターン1のシーケンス図である。ここでは、ターゲットeNBとして適切なDeNB候補がDeNBリストに存在しない場合に、DeNBリストに存在するDeNB候補であるeNB200-2及びeNB200-3を「所定eNB」とするケースを説明する。eNB200-2には、他のMRN1(MRN300-1)及びMRN2(MRN300-2)が接続している。
図16は、本実施形態に係る動作パターン2のシーケンス図である。ここでは、MRN300からのハンドオーバ要求がeNB200-2によって拒否された場合に、eNB200-2を「所定eNB」とするケースを説明する。
以上説明したように、DeNBリストに存在するDeNB候補をターゲットeNB200とするMRN300のハンドオーバが不能である場合において、MRN300は、当該DeNBリストに存在するeNB200-2に接続する他のMRNが保持するDeNBリストを当該他のMRNから取得する。そして、MRN300は、取得したDeNBリストの中から新たなターゲットeNBを決定する。これにより、DeNBリストに存在するDeNB候補をターゲットeNBとするMRN300のハンドオーバが不能である場合でも、他のMRNが保持するDeNBリストを利用して、新たなターゲットeNBへのハンドオーバを試みることができる。
以下、第4実施形態について、上述した各実施形態との相違点を説明する。
以下において、本実施形態に係る移動通信システムの動作を説明する。
図17は、本実施形態に係る隣接eNBリストの構成図である。
(4.1.2.1)動作パターン1
図18は、本実施形態に係る動作パターン1のシーケンス図である。
図19は、本実施形態に係る動作パターン2のシーケンス図である。ここでは、本実施形態に係る動作パターン1との相違点を説明する。
以上説明したように、隣接eNBリストは、隣接eNBそれぞれについて、当該隣接eNBがDeNB機能を有するか否かを示す情報をさらに含む。これにより、eNB200(DeNB200-1)は、隣接eNBリストに基づいて、DeNB機能を有する隣接eNBの中からターゲットeNB200を決定することができる。
以下、第5実施形態について、上述した各実施形態との相違点を説明する。
図20は、本実施形態に係る動作シーケンス図である。本シーケンスの初期状態では、MRN300は、DeNB200-1に接続してリレー伝送を実行中であるとする。
以上説明したように、eNB200に接続するUE100のハンドオーバ判断をeNB200が行う移動通信システムにおいて、DeNB200-1に接続し、DeNB200-1とUE100との間でリレー伝送を行うMRN300は、MRN300のハンドオーバ判断をMRN300自身で行う。これにより、MRN300は、自身の状況に応じて、すなわち、MRN300特有の事情を考慮して、最適なハンドオーバ判断を行うことができる。
この開示の一部をなす論述及び図面はこの発明を限定するものであると理解すべきではない。この開示から当業者には様々な代替実施形態、実施例及び運用技術が明らかとなる。
Claims (22)
- ドナー基地局リストを保持しており、前記ドナー基地局リストに存在するドナー基地局に接続し、前記ドナー基地局とユーザ端末との間でリレー伝送を行うリレー局における通信制御方法であって、
隣接基地局を特定するステップAと、
前記ステップAで特定した前記隣接基地局に対して、前記リレー局の受け入れ可否に関して問い合せるステップBと、
前記ステップBでの問い合せ結果に応じて、前記ドナー基地局リストを更新するステップCと、
を有することを特徴とする通信制御方法。 - 前記ステップBは、前記ステップAで特定した前記隣接基地局に対して、ドナー基地局機能を有しているか否かを問い合せるステップB1を含むことを特徴とする請求項1に記載の通信制御方法。
- 前記ステップBは、前記ステップAで特定した前記隣接基地局に対して、前記リレー局の負荷状況を通知するステップB2を含むことを特徴とする請求項1に記載の通信制御方法。
- 前記ステップCで更新された前記ドナー基地局リストを、前記ドナー基地局を介してコアネットワーク装置に通知するステップDをさらに有することを特徴とする請求項1に記載の通信制御方法。
- ドナー基地局とユーザ端末との間でリレー伝送を行うリレー局を含む移動通信システムに適用される通信制御方法であって、
ターゲット基地局への前記リレー局のハンドオーバ手順において、前記リレー局の受け入れを要求するためのハンドオーバ要求を前記ターゲット基地局に送信するステップAを有し、
前記ステップAにおいて、前記リレー局の負荷状況を示す情報を前記ハンドオーバ要求と共に送信することを特徴とする通信制御方法。 - 前記ターゲット基地局へのハンドオーバ判断を前記リレー局で行う場合、前記ステップAにおいて、前記リレー局が、前記リレー局の負荷状況を示す情報を前記ハンドオーバ要求と共に送信することを特徴とする請求項5に記載の通信制御方法。
- 前記ステップAに先立ち、前記リレー局が、ドナー基地局候補の基地局のリストであるドナー基地局リスト又は隣接基地局のリストである隣接基地局リストに基づいて、前記ターゲット基地局を決定するステップCをさらに有し、
前記ドナー基地局リスト又は前記隣接基地局リストは、前記ドナー基地局候補の基地局又は前記隣接基地局のそれぞれについて、位置、セル方向、キャパシティ、及びセルサイズの少なくとも1つの情報を含むことを特徴とする請求項6に記載の通信制御方法。 - 前記ターゲット基地局へのハンドオーバ判断を前記ドナー基地局で行う場合、前記ステップAにおいて、前記ドナー基地局が、前記リレー局の負荷状況を示す情報を前記ハンドオーバ要求と共に送信することを特徴とする請求項5に記載の通信制御方法。
- ドナー基地局リストを保持しており、前記ドナー基地局リストに存在するドナー基地局に接続し、前記ドナー基地局とユーザ端末との間でリレー伝送を行うリレー局を含む移動通信システムにおける通信制御方法であって、
前記ドナー基地局リストに存在する基地局への前記リレー局のハンドオーバが不能である場合において、前記リレー局が、所定基地局に接続する他のリレー局が保持するドナー基地局リストを前記他のリレー局から取得するステップAを有することを特徴とする通信制御方法。 - 前記リレー局が、前記ステップAに先立ち、前記所定基地局に接続する他のリレー局についての情報であるリレー局情報を前記所定基地局から受信するステップCをさらに有することを特徴とする請求項9に記載の通信制御方法。
- 前記リレー局からターゲット基地局にハンドオーバ要求を送信するステップDと、
前記ターゲット基地局が、前記ハンドオーバ要求を拒否する場合に、ハンドオーバ拒否応答を前記リレー局に送信するステップEと、をさらに有し、
前記所定基地局は、前記ターゲット基地局であり、
前記ステップEにおいて、前記ターゲット基地局は、前記リレー局情報を前記ハンドオーバ拒否応答に含めて送信し、
前記ステップCにおいて、前記リレー局は、前記ハンドオーバ拒否応答に含まれる前記リレー局情報を受信することを特徴とする請求項10に記載の通信制御方法。 - 前記ステップCに先立ち、前記所定基地局に接続する他のリレー局について前記所定基地局に問い合せるステップDをさらに有することを特徴とする請求項10に記載の通信制御方法。
- ドナー基地局機能を有する基地局と、前記基地局とユーザ端末との間でリレー伝送を行うリレー局とを含む移動通信システムに適用される通信制御方法であって、
隣接基地局の識別子を含む隣接基地局リストを前記基地局が保持するステップAを有し、
前記隣接基地局リストは、前記隣接基地局それぞれについて、当該隣接基地局がドナー基地局機能を有するか否かを示す情報をさらに含むことを特徴とする通信制御方法。 - 前記リレー局が前記基地局に接続した際に、前記基地局が、前記隣接基地局リストを更新するための情報をコアネットワーク装置に要求するステップBと、
前記基地局が、前記コアネットワーク装置からの情報に応じて、前記隣接基地局リストを更新するステップCとをさらに有することを特徴とする請求項13に記載の通信制御方法。 - 前記基地局からターゲット基地局への前記リレー局のハンドオーバ手順において、前記ターゲット基地局が、前記基地局からのハンドオーバ要求を受信するステップDと、
前記ターゲット基地局が前記ドナー基地局機能を有しない場合、前記ターゲット基地局が、前記ハンドオーバ要求に対する拒否応答と共に、自身が前記ドナー基地局機能を有しない旨の情報を前記基地局に送信するステップEとをさらに有することを特徴とする請求項13に記載の通信制御方法。 - 基地局に接続するユーザ端末のハンドオーバ判断を前記基地局が行う移動通信システムに適用される通信制御方法であって、
ドナー基地局に接続し、前記ドナー基地局とユーザ端末との間でリレー伝送を行うリレー局のハンドオーバ判断を行うステップAを有し、
前記ステップAにおいて、前記リレー局のハンドオーバ判断を前記リレー局が行うことを特徴とする通信制御方法。 - 前記ステップAによりターゲット基地局へのハンドオーバを行うと判断した場合に、前記リレー局の受け入れを要求するためのハンドオーバ要求を前記リレー局が送信するステップBをさらに有することを特徴とする請求項16に記載の通信制御方法。
- 前記ステップBにおいて、前記リレー局は、前記リレー局と前記ターゲット基地局との間に確立されるネットワークインターフェイスを用いて、前記ハンドオーバ要求を前記ターゲット基地局に送信するステップB1を含むことを特徴とする請求項17に記載の通信制御方法。
- 前記ターゲット基地局が、前記リレー局からの前記ハンドオーバ要求の受信に応じて、前記リレー局のハンドオーバのための情報を前記ドナー基地局に対して要求するステップCと、
前記ドナー基地局が、前記ターゲット基地局からの要求に応じて、前記リレー局のハンドオーバのための情報を前記ターゲット基地局に送信するステップDと、
をさらに有することを特徴とする請求項18に記載の通信制御方法。 - 前記ターゲット基地局が、前記リレー局のハンドオーバのための情報を前記ドナー基地局から受信した後、前記ネットワークインターフェイスを用いて、前記リレー局のハンドオーバのための情報を含むハンドオーバ許可応答を前記リレー局に送信するステップEをさらに有することを特徴とする請求項19に記載の通信制御方法。
- 前記ステップBにおいて、前記リレー局は、前記ハンドオーバ要求に前記ターゲット基地局の識別子を1つ又は複数含めた上で、前記ハンドオーバ要求を前記ドナー基地局に送信することを特徴とする請求項17に記載の通信制御方法。
- 前記ステップBに先立ち、前記リレー局が、前記ドナー基地局及び/又は前記ターゲット基地局に対して、前記リレー局からのハンドオーバ要求に対応可能であるか否かを問い合わせるステップをさらに有することを特徴とする請求項17に記載の通信制御方法。
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/386,407 US9642050B2 (en) | 2012-03-23 | 2013-03-21 | Communication control method |
JP2014506282A JP6062420B2 (ja) | 2012-03-23 | 2013-03-21 | 制御方法、リレー局、基地局及びプロセッサ |
EP13765247.5A EP2830344A4 (en) | 2012-03-23 | 2013-03-21 | COMMUNICATION CONTROL METHOD |
US15/469,314 US10244515B2 (en) | 2012-03-23 | 2017-03-24 | Communication control method |
US16/281,909 US10791547B2 (en) | 2012-03-23 | 2019-02-21 | Communication control method |
US17/001,107 US11337193B2 (en) | 2012-03-23 | 2020-08-24 | Communication control method |
Applications Claiming Priority (10)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201261615045P | 2012-03-23 | 2012-03-23 | |
US201261615087P | 2012-03-23 | 2012-03-23 | |
US201261615073P | 2012-03-23 | 2012-03-23 | |
US201261615067P | 2012-03-23 | 2012-03-23 | |
US201261615059P | 2012-03-23 | 2012-03-23 | |
US61/615,067 | 2012-03-23 | ||
US61/615,059 | 2012-03-23 | ||
US61/615,045 | 2012-03-23 | ||
US61/615,073 | 2012-03-23 | ||
US61/615,087 | 2012-03-23 |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/386,407 A-371-Of-International US9642050B2 (en) | 2012-03-23 | 2013-03-21 | Communication control method |
US15/469,314 Continuation US10244515B2 (en) | 2012-03-23 | 2017-03-24 | Communication control method |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2013141321A1 true WO2013141321A1 (ja) | 2013-09-26 |
Family
ID=49222775
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2013/058143 WO2013141321A1 (ja) | 2012-03-23 | 2013-03-21 | 通信制御方法 |
Country Status (4)
Country | Link |
---|---|
US (4) | US9642050B2 (ja) |
EP (2) | EP3226600A1 (ja) |
JP (5) | JP6062420B2 (ja) |
WO (1) | WO2013141321A1 (ja) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2020017507A1 (ja) * | 2018-07-18 | 2020-01-23 | Kddi株式会社 | 中継伝送路を含んだ無線通信システムにおいてハンドオーバ処理を実行する中継装置、その制御方法、及びプログラム |
WO2020066605A1 (ja) * | 2018-09-26 | 2020-04-02 | 京セラ株式会社 | 中継装置 |
US11368210B2 (en) | 2019-03-29 | 2022-06-21 | Honda Motor Co., Ltd. | Relay device, program, communication system, and communication method |
US11503517B2 (en) | 2019-03-29 | 2022-11-15 | Honda Motor Co., Ltd. | Relay apparatus, program, communication system, and method |
Families Citing this family (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3226600A1 (en) | 2012-03-23 | 2017-10-04 | Kyocera Corporation | Congestion aware x2 handover of relay node |
US9876557B2 (en) * | 2012-06-28 | 2018-01-23 | Lg Electronics Inc. | Method and apparatus for transmitting indication in wireless communication system |
GB2503942A (en) * | 2012-07-13 | 2014-01-15 | Nec Corp | Mobile relay node handover in a wireless communication system |
US9544782B2 (en) * | 2012-11-02 | 2017-01-10 | Qualcomm Incorporated | Systems, apparatus, and methods for range extension of wireless communication |
KR20140078511A (ko) * | 2012-12-17 | 2014-06-25 | 에릭슨 엘지 주식회사 | 타겟 기지국 셀 식별 시스템 및 방법 |
JP5750523B1 (ja) * | 2014-02-17 | 2015-07-22 | ソフトバンクモバイル株式会社 | 制御装置、中継装置、通信システム、プログラム及び制御方法 |
EP3114882B1 (en) * | 2014-03-06 | 2018-10-10 | LG Electronics Inc. | Method and apparatus for performing handover in wireless communication system |
EP3487225B1 (en) * | 2016-08-12 | 2022-10-12 | Huawei Technologies Co., Ltd. | Nb-iot cell reselection method and network devices |
US10609611B2 (en) * | 2017-05-04 | 2020-03-31 | Ofinno, LLP | Beam-based measurement configuration |
JP6875652B2 (ja) * | 2017-05-17 | 2021-05-26 | 富士通株式会社 | 無線基地局装置、端末装置、無線通信システム、及び無線通信方法 |
JP6498239B2 (ja) * | 2017-06-30 | 2019-04-10 | ソフトバンク株式会社 | 基地局、移動通信システム及びハンドオーバ制御方法 |
JP6557294B2 (ja) * | 2017-07-10 | 2019-08-07 | ソフトバンク株式会社 | 移動通信システム及びデータ処理装置 |
US10708854B2 (en) | 2017-10-12 | 2020-07-07 | Airspan Networks Inc. | Apparatus and method for providing network configurability in a wireless network |
US11102785B2 (en) | 2017-10-12 | 2021-08-24 | Airspan Ip Holdco Llc | Apparatus and method selecting a base station in a network |
US10616824B2 (en) * | 2017-11-03 | 2020-04-07 | Airspan Networks Inc. | Apparatus and method for providing network configurability in a wireless network |
JP2021078354A (ja) | 2018-03-08 | 2021-05-27 | 有限会社アルティザイム・インターナショナル | フラビンアデニンジヌクレオチドグルコース脱水素酵素とシトクロム分子との融合タンパク質 |
RU2755210C1 (ru) * | 2018-05-22 | 2021-09-14 | Гуандун Оппо Мобайл Телекоммьюникейшнз Корп., Лтд. | Способ доступа и точка передачи |
US20230336239A1 (en) | 2020-08-31 | 2023-10-19 | Wollochet Solutions Llc | Location dependent relay node configuration |
US20240040540A1 (en) * | 2020-12-15 | 2024-02-01 | Sharp Kabushiki Kaisha | Neighboring cell mobility information for vehicle-mounted relays |
US20230050960A1 (en) * | 2021-08-16 | 2023-02-16 | Qualcomm Incorporated | Target cell selection of autonomous mobile repeaters |
WO2024029520A1 (ja) * | 2022-08-04 | 2024-02-08 | 京セラ株式会社 | 通信制御方法 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2011166595A (ja) * | 2010-02-12 | 2011-08-25 | Mitsubishi Electric Corp | 無線中継基地局、通信システムおよび無線中継方法 |
JP2012005091A (ja) * | 2010-06-21 | 2012-01-05 | Ntt Docomo Inc | 移動通信方法及び無線基地局 |
JP2012080367A (ja) * | 2010-10-01 | 2012-04-19 | Ntt Docomo Inc | 移動通信方法 |
Family Cites Families (30)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
TWI289999B (en) * | 2001-06-08 | 2007-11-11 | Benq Corp | Transmission method for relay signal of wireless communication system |
KR20080003733A (ko) * | 2006-07-03 | 2008-01-08 | 한국전자통신연구원 | 기지국과 이동국을 중계하는 장치 및 방법, 그리고 제어정보 수신 방법 |
EP2041910A4 (en) * | 2006-07-06 | 2013-05-22 | Apple Inc | WIRELESS ACCESS POINT SECURITY FOR MULTIHOP NETWORKS |
JP2008034906A (ja) * | 2006-07-26 | 2008-02-14 | Matsushita Electric Ind Co Ltd | 無線基地局ハンドオーバ方法、及びデータ通信システム、並びに無線基地局、中継装置 |
EP2207277A4 (en) | 2007-10-16 | 2015-08-12 | Fujitsu Ltd | RELAY STATION DEVICE, TERMINAL STATION DEVICE, WIRELESS COMMUNICATION SYSTEM, AND CHARGE DISTRIBUTION METHOD |
FI20085193A0 (fi) * | 2008-02-29 | 2008-02-29 | Nokia Siemens Networks Oy | Toistinsolmun yhteydenhallinta |
JP4902605B2 (ja) * | 2008-07-11 | 2012-03-21 | 株式会社日立製作所 | 無線基地局、ハンドオフ制御方法、およびプログラム |
JP4796103B2 (ja) * | 2008-08-28 | 2011-10-19 | 京セラ株式会社 | 通信システム |
CN101729277B (zh) * | 2008-10-27 | 2015-07-08 | 华为技术有限公司 | 设备池的管理方法、节点设备和通信*** |
ES2407631T3 (es) * | 2008-11-04 | 2013-06-13 | Nokia Siemens Networks Oy | Gestión de sobrecargas y traspasos en una red de comunicaciones |
KR101632739B1 (ko) * | 2009-06-18 | 2016-06-22 | 한국전자통신연구원 | 통신 시스템의 데이터 전송 방법 및 이를 수행하는 릴레이 장치 |
CN101938798A (zh) * | 2009-07-03 | 2011-01-05 | 中兴通讯股份有限公司 | 一种无线中继***中终端的移动性管理方法及*** |
US8611333B2 (en) * | 2009-08-12 | 2013-12-17 | Qualcomm Incorporated | Systems and methods of mobile relay mobility in asynchronous networks |
JP2013502783A (ja) * | 2009-08-19 | 2013-01-24 | エヌイーシー ヨーロッパ リミテッド | 移動セルラ通信ネットワークにおける移動端末のハンドオーバ決定を支援する方法 |
JP5399830B2 (ja) * | 2009-09-09 | 2014-01-29 | 京セラ株式会社 | 無線通信システム、無線基地局、無線中継局及びハンドオーバ制御方法 |
JP5564273B2 (ja) | 2010-01-26 | 2014-07-30 | 京セラ株式会社 | 無線中継局及び制御方法 |
US8694012B2 (en) * | 2010-02-01 | 2014-04-08 | Intel Mobile Communications GmbH | Method and apparatuses for two or more neighboring wireless network devices accessing a plurality of radio resources |
KR101878000B1 (ko) * | 2010-04-02 | 2018-07-12 | 인터디지탈 패튼 홀딩스, 인크 | 릴레이 노드를 통한 통신을 지원하기 위한 방법 및 장치 |
CN102238667B (zh) * | 2010-05-07 | 2015-09-16 | 北京三星通信技术研究有限公司 | 一种建立基站间连接的方法 |
CN102291789B (zh) * | 2010-06-21 | 2015-08-12 | 中兴通讯股份有限公司 | 获取相邻小区信息方法、用户设备的小区切换方法及网络 |
GB201010410D0 (en) * | 2010-06-22 | 2010-08-04 | Nokia Siemens Networks Oy | Relaying communications |
CN102348255B (zh) | 2010-07-30 | 2016-07-06 | 中兴通讯股份有限公司 | 一种中继节点接入网络的方法和*** |
US20130163762A1 (en) * | 2010-09-13 | 2013-06-27 | Nec Corporation | Relay node device authentication mechanism |
WO2012091418A2 (ko) * | 2010-12-27 | 2012-07-05 | 한국전자통신연구원 | 단말간 직접 통신 및 단말 릴레잉 방법 |
EP2659709A1 (en) * | 2010-12-28 | 2013-11-06 | Nokia Siemens Networks Oy | Relay node configuration in preparation for handover |
WO2012096611A2 (en) * | 2011-01-14 | 2012-07-19 | Telefonaktiebolaget L M Ericsson (Publ) | Method and device for distinguish between relay types |
CN102098723B (zh) | 2011-02-12 | 2014-01-29 | 大唐移动通信设备有限公司 | 为移动中继节点配置施主基站或施主小区的方法和设备 |
US20130316712A1 (en) * | 2011-03-13 | 2013-11-28 | Lg Electronics Inc. | Method and apparatus for performing handover in wireless communication system |
IN2014CN03338A (ja) | 2011-11-04 | 2015-07-03 | Mitsubishi Electric Corp | |
EP3226600A1 (en) * | 2012-03-23 | 2017-10-04 | Kyocera Corporation | Congestion aware x2 handover of relay node |
-
2013
- 2013-03-21 EP EP17167753.7A patent/EP3226600A1/en not_active Withdrawn
- 2013-03-21 EP EP13765247.5A patent/EP2830344A4/en not_active Withdrawn
- 2013-03-21 US US14/386,407 patent/US9642050B2/en active Active
- 2013-03-21 JP JP2014506282A patent/JP6062420B2/ja active Active
- 2013-03-21 WO PCT/JP2013/058143 patent/WO2013141321A1/ja active Application Filing
-
2015
- 2015-11-30 JP JP2015234059A patent/JP6239572B2/ja active Active
-
2017
- 2017-03-24 US US15/469,314 patent/US10244515B2/en active Active
- 2017-11-01 JP JP2017211710A patent/JP6405025B2/ja active Active
-
2018
- 2018-09-13 JP JP2018171165A patent/JP2019009810A/ja active Pending
-
2019
- 2019-02-21 US US16/281,909 patent/US10791547B2/en active Active
-
2020
- 2020-04-07 JP JP2020069319A patent/JP6960010B2/ja active Active
- 2020-08-24 US US17/001,107 patent/US11337193B2/en active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2011166595A (ja) * | 2010-02-12 | 2011-08-25 | Mitsubishi Electric Corp | 無線中継基地局、通信システムおよび無線中継方法 |
JP2012005091A (ja) * | 2010-06-21 | 2012-01-05 | Ntt Docomo Inc | 移動通信方法及び無線基地局 |
JP2012080367A (ja) * | 2010-10-01 | 2012-04-19 | Ntt Docomo Inc | 移動通信方法 |
Non-Patent Citations (4)
Title |
---|
"TS 36.300 V11. 0. 0", 3GPP TECHNOLOGY SPECIFICATIONS, December 2011 (2011-12-01) |
CATT: "Key issues based on Alt1 relay", 3GPP TSG RAN WG3#75 R3-120104, 31 January 2012 (2012-01-31), XP050566597 * |
LG ELECTRONICS INC.: "Unavailable DeNB cells at phase II", 3GPP TSG-RAN WG2 #72 R2-106494, 9 November 2010 (2010-11-09), XP050605538 * |
See also references of EP2830344A4 |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2020017507A1 (ja) * | 2018-07-18 | 2020-01-23 | Kddi株式会社 | 中継伝送路を含んだ無線通信システムにおいてハンドオーバ処理を実行する中継装置、その制御方法、及びプログラム |
WO2020066605A1 (ja) * | 2018-09-26 | 2020-04-02 | 京セラ株式会社 | 中継装置 |
JPWO2020066605A1 (ja) * | 2018-09-26 | 2021-08-30 | 京セラ株式会社 | 中継装置 |
US11368210B2 (en) | 2019-03-29 | 2022-06-21 | Honda Motor Co., Ltd. | Relay device, program, communication system, and communication method |
US11503517B2 (en) | 2019-03-29 | 2022-11-15 | Honda Motor Co., Ltd. | Relay apparatus, program, communication system, and method |
Also Published As
Publication number | Publication date |
---|---|
JPWO2013141321A1 (ja) | 2015-08-03 |
EP3226600A1 (en) | 2017-10-04 |
US20190191431A1 (en) | 2019-06-20 |
US9642050B2 (en) | 2017-05-02 |
US20150043422A1 (en) | 2015-02-12 |
US20200389890A1 (en) | 2020-12-10 |
US20170201978A1 (en) | 2017-07-13 |
US10791547B2 (en) | 2020-09-29 |
JP6960010B2 (ja) | 2021-11-05 |
JP6405025B2 (ja) | 2018-10-17 |
JP2020114019A (ja) | 2020-07-27 |
JP6239572B2 (ja) | 2017-11-29 |
US10244515B2 (en) | 2019-03-26 |
EP2830344A1 (en) | 2015-01-28 |
US11337193B2 (en) | 2022-05-17 |
JP2018042275A (ja) | 2018-03-15 |
JP2016076960A (ja) | 2016-05-12 |
EP2830344A4 (en) | 2016-03-23 |
JP2019009810A (ja) | 2019-01-17 |
JP6062420B2 (ja) | 2017-01-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP6960010B2 (ja) | 通信制御方法 | |
JP5851586B2 (ja) | 通信制御方法、移動管理装置、及びホーム基地局 | |
CN109156005B (zh) | 基站和用户终端 | |
US9386442B2 (en) | Method and apparatus for performing membership verification or access control in wireless communication system | |
US20180227819A1 (en) | Method and apparatus for performing partial handover for continuous data transmission in wireless communication system | |
US9131424B2 (en) | Method and apparatus for releasing user equipment context in wireless communication system | |
WO2015115176A1 (ja) | 移動局、再接続要求方法、基地局及び再接続要求処理方法 | |
KR20120004525A (ko) | 분할 셀 중계 네트워크를 위한 장치 이동성 | |
KR20120013944A (ko) | 이동 중계국을 지원하는 광대역 무선통신 시스템의 그룹 핸드오버 방법 및 장치 | |
WO2017135343A1 (ja) | 通信方法、無線端末、プロセッサ及び基地局 | |
WO2013137460A1 (ja) | 通信制御方法、ユーザ端末、基地局、及びホーム基地局 | |
US9479921B2 (en) | Method and apparatus for performing closed subscriber group grouping in wireless communication system |
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: 13765247 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2014506282 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14386407 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REEP | Request for entry into the european phase |
Ref document number: 2013765247 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2013765247 Country of ref document: EP |