WO2017170202A1 - 通信方法、プロセッサ、基地局、及びネットワーク装置 - Google Patents
通信方法、プロセッサ、基地局、及びネットワーク装置 Download PDFInfo
- Publication number
- WO2017170202A1 WO2017170202A1 PCT/JP2017/011956 JP2017011956W WO2017170202A1 WO 2017170202 A1 WO2017170202 A1 WO 2017170202A1 JP 2017011956 W JP2017011956 W JP 2017011956W WO 2017170202 A1 WO2017170202 A1 WO 2017170202A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- wlan
- base station
- request message
- identifier
- enb
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 56
- 238000004891 communication Methods 0.000 title claims abstract description 33
- 230000008569 process Effects 0.000 claims description 31
- 230000004044 response Effects 0.000 claims description 21
- 238000002360 preparation method Methods 0.000 claims description 16
- 238000012545 processing Methods 0.000 claims description 7
- 230000000717 retained effect Effects 0.000 claims description 5
- 238000005259 measurement Methods 0.000 description 33
- 230000005540 biological transmission Effects 0.000 description 17
- 238000010586 diagram Methods 0.000 description 16
- 230000008859 change Effects 0.000 description 9
- 230000010267 cellular communication Effects 0.000 description 7
- 230000011664 signaling Effects 0.000 description 6
- 238000012508 change request Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 238000012546 transfer Methods 0.000 description 4
- 230000002776 aggregation Effects 0.000 description 3
- 238000004220 aggregation Methods 0.000 description 3
- 230000009977 dual effect Effects 0.000 description 3
- 101000741965 Homo sapiens Inactive tyrosine-protein kinase PRAG1 Proteins 0.000 description 2
- 102100038659 Inactive tyrosine-protein kinase PRAG1 Human genes 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 2
- 238000012790 confirmation Methods 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 101150014328 RAN2 gene Proteins 0.000 description 1
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 230000006837 decompression Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0009—Control or signalling for completing the hand-off for a plurality of users or terminals, e.g. group communication or moving wireless networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
-
- 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/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
- H04W36/00698—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink using different RATs
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/08—Reselecting an access point
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/34—Reselection control
- H04W36/38—Reselection control by fixed network equipment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/11—Allocation or use of connection identifiers
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/02—Data link layer protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/08—Upper layer protocols
-
- 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/10—Small scale networks; Flat hierarchical networks
- H04W84/12—WLAN [Wireless Local Area Networks]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/02—Terminal devices
- H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
Definitions
- This application relates to a communication method, a processor, a base station, and a network device.
- LTE Long Term Evolution
- 3GPP 3rd Generation Partnership Project
- LWA LTE-WLAN Aggregation
- a user apparatus can use not only LTE (cellular communication system) radio resources but also WLAN (Wireless LAN (Local Area Network): WLAN communication system) radio resources.
- LTE cellular communication system
- WLAN Wireless LAN (Local Area Network): WLAN communication system
- data packets from a base station to a user apparatus is sent via a WLAN termination device (WT: WLAN Termination).
- WT WLAN Termination
- the first base station sets a WLAN mobility set, which is a set of one or more WLAN (Wireless Local Area Network) identifiers, in the user apparatus.
- the first base station determines a handover of the user equipment to a second base station.
- the first base station includes an identifier of a WLAN termination device associated with the one or more WLAN identifiers in a handover request message for the user device.
- the first base station sends the handover request message including an identifier of the WLAN termination device to the second base station.
- the processor is a processor for controlling a base station (second base station).
- the processor executes a process of receiving a handover request message for a user apparatus configured with a WLAN mobility set, which is a set of one or more WLAN (Wireless Local Area Network) identifiers, from a first base station, and performs the handover
- the request message includes an identifier of a WLAN terminator associated with the one or more WLAN identifiers.
- the base station includes a controller.
- the controller is configured to receive, from the first base station, a handover request message for a user apparatus in which a WLAN mobility set that is a set of one or more WLAN (Wireless Local Area Network) identifiers is set.
- the handover request message includes an identifier of a WLAN terminator associated with the one or more WLAN identifiers.
- the processor is a processor for controlling a network device.
- the processor performs a process of receiving a WLAN addition request message for requesting resource preparation for a user apparatus from a base station.
- the WLAN addition request message includes an identifier of a user device assigned by the network device.
- the network device (WLAN termination device) includes a controller.
- the controller is configured to receive a WLAN addition request message from a base station for requesting resource preparation for a user equipment.
- the WLAN addition request message includes an identifier of a user device assigned by the network device.
- FIG. 1 is a diagram showing a system configuration.
- FIG. 2 is a protocol stack diagram of a radio interface in the LTE system.
- FIG. 3 is a diagram illustrating a radio protocol structure of an eNB used in LWA.
- FIG. 4 is a block diagram showing the UE 100.
- FIG. 5 is a block diagram showing the eNB 200.
- FIG. 6 is a block diagram showing the AP 300.
- FIG. 7 is a block diagram showing WT 600.
- FIG. 8 is a sequence diagram for explaining the operation according to the embodiment.
- FIG. 9 is a sequence diagram for explaining inter-eNB handover without WT change.
- the second base station may send a WLAN addition request message for requesting resource preparation for the user apparatus to the WLAN termination apparatus specified based on the identifier of the WLAN termination apparatus. Good.
- the first base station may include the identifier of the user apparatus assigned by the WLAN terminating device in the handover request message.
- the first base station may send the handover request message including an identifier of the user apparatus to the second base station.
- the second base station may include an identifier of the user device assigned by the WLAN termination device in a WLAN addition request message for requesting resource preparation for the user device.
- the second base station may send the WLAN addition request message including an identifier of the user device identifier to the WLAN terminating device.
- the WLAN termination device may send a WLAN addition request approval message, which is a response to the WLAN addition request message, to the second base station.
- the second base station may include holding information indicating that the WLAN terminating device holds the context of the user apparatus in a handover request approval message that is a response to the handover request message.
- the second base station may send the handover request approval message including the retained information to the first base station.
- the base station (first base station) includes a controller.
- the controller sets a WLAN mobility set, which is a set of one or more WLAN (Wireless Local Area Network) identifiers, to the user apparatus, determines handover of the user apparatus to a second base station, and for the user apparatus A handover request message including an identifier of a WLAN termination device associated with the one or more WLAN identifiers, and transmitting the handover request message including the identifier of the WLAN termination device to the second base station.
- a WLAN mobility set which is a set of one or more WLAN (Wireless Local Area Network) identifiers
- the base station includes a controller.
- the controller is configured to receive, from the first base station, a handover request message for a user apparatus in which a WLAN mobility set that is a set of one or more WLAN (Wireless Local Area Network) identifiers is set.
- the handover request message includes an identifier of a WLAN terminator associated with the one or more WLAN identifiers.
- the processor is a processor for controlling a network device.
- the processor performs a process of receiving a WLAN addition request message for requesting resource preparation for a user apparatus from a base station.
- the WLAN addition request message includes an identifier of a user device assigned by the network device.
- the handover request message may include the WLAN mobility set.
- a target base station includes a controller that receives a handover request message for a user apparatus in which a WLAN mobility set is set from a source base station.
- the handover request message includes an identifier of a WLAN terminating device associated with an identifier of a WLAN access point included in the WLAN mobility set.
- the controller may send a WT addition request message to the WLAN termination device based on the identifier of the WLAN termination device.
- the handover request message may include WLAN measurement report information from the user apparatus.
- the WT addition request rejection message may include reason information indicating that the WLAN mobility set candidate does not match the WLAN mobility set set in the user terminal.
- E-UTRAN 10 corresponds to cellular RAN.
- the EPC 20 corresponds to a core network.
- the E-UTRAN 10 and the EPC 20 constitute an LTE system network.
- the EPC 20 includes a plurality of MME400 / S-GW500.
- the MME 400 is a network node that performs various mobility controls for the UE 100, and corresponds to a control station.
- the SGW 500 is a network node that performs user data transfer control, and corresponds to an exchange.
- FIG. 2 is a protocol stack diagram of a radio interface in the LTE system. As shown in FIG. 2, the radio interface protocol is divided into the first to third layers of the OSI reference model.
- the first layer is a physical (PHY) layer.
- the second layer includes a MAC (Medium Access Control) layer, an RLC (Radio Link Control) layer, and a PDCP (Packet Data Convergence Protocol) layer.
- the third layer includes an RRC (Radio Resource Control) layer.
- LWA LWA LTE-WLAN Aggregation
- FIG. 3 shows a radio protocol architecture of the eNB 200 used in the LWA.
- the eNB 200 is provided with an LWAAP (LTE-WLAN Aggregation Adaptation Protocol) entity.
- the LWAAP entity generates an LWA PDU.
- the LWA PDU is a PDU (Protocol Data Unit) including a DRB (Data Radio Bearer) identifier (DRB ID) generated by the LWAAP entity for transmission via the WLAN 30 in the LWA.
- DRB ID Data Radio Bearer
- the WT 600 uses LWA EtherType for data transfer to the UE 100 via the WLAN 30.
- the UE 100 uses LWA EtherType in order to determine that the received PDU belongs to the LWA bearer.
- the UE 100 uses the DRB identifier to determine the LWA bearer to which the PDU belongs.
- LWA bearer In LWA, there is a bearer (LWA bearer) in which data (packet) is transmitted using only radio resources of eNB 200 (LTE).
- LWA there are two bearer types.
- the two bearer types are a split LWA bearer and a switched LWA bearer.
- the split LWA bearer is a bearer in which a radio protocol is located in both the eNB 200 and the WLAN 30 in order to use radio resources of the eNB 200 and the WLAN 30 in the LWA.
- the split LWA bearer is a bearer that splits (splits) in the PDCP layer.
- One split bearer transmits data using radio resources of the eNB 200.
- Data is transmitted through the PDCP layer (first PDCP layer), the RLC layer, and the MAC layer.
- the other split bearer transmits data using the wireless resources of the WLAN 30.
- Data is transmitted from the PDCP layer to the WT 600 via the LWAAP.
- Data is transmitted to the UE 100 via the WLAN layer (WLAN entity) of the WT 600 and the AP 300.
- the switched LWA bearer is a bearer in which only radio resources of the WLAN 30 are used although the radio protocol is located in both the eNB 200 and the WLAN 30 in the LWA.
- data is transmitted from the PDCP layer (second PDCP layer) to the WT 600 via the LWAAP.
- the destination (PDCP layer) of data (packets) transmitted from the UE 100 to the eNB 200 via the WLAN 30 differs depending on the bearer to which the data belongs.
- the LWAAP determines the destination PDCP based on the DRB identifier included in the data (packet).
- the LWAAP sends data to the first PDCP layer if the data belongs to a split LWA bearer (ie, the data includes an identifier of the split LWA bearer).
- the data (packet) sent from the RLC layer is combined.
- the first PDCP layer sends the combined data to the upper node (MME400 / SGW500).
- the LWAAP sends the data to the second PDCP layer.
- the second PDCP layer sends data to the upper node (MME400 / SGW500).
- a WLAN mobility set is a set of one or more APs 300 identified by one or more WLAN identifiers (for example, BSSID (Basic Service Set ID), HESSID (Homogenous Extended Service Set ID), and SSID (Service Set ID)). is there.
- UE100 may perform mobility between AP300 which belongs to a WLAN mobility set, without notifying eNB200.
- ENB200 provides the WLAN mobility set to UE100.
- the UE 100 attempts to connect to the WLAN 30 (AP 300) having an identifier that matches one of the set WLAN mobility sets.
- the mobility of the UE 100 to the AP 300 that does not belong to the WLAN mobility set is controlled by the eNB 200.
- the eNB 200 updates the WLAN mobility set based on the measurement report provided from the UE 100.
- the UE 100 connects to at most one WLAN mobility set (AP 300) at a time. All APs belonging to the WLAN mobility set share a common WT 600 that terminates Xw-C and Xw-U.
- the WLAN identifier belonging to the WLAN mobility set may be a part (subset) of all WLAN identifiers associated with the WT 600.
- the UE 100 that supports LWA may be configured (configured) by the eNB 200 (E-UTRAN 10) to execute the WLAN measurement report.
- the WLAN measurement target may be set by at least one of a WLAN identifier, a WLAN channel number, and a WLAN band.
- the WLAN measurement report is triggered using a reception strength (RSSI: Received Signal Strength Indicator) of a radio signal (for example, a beacon signal) from the AP 300.
- the WLAN measurement report may include RSSI, channel utilization, station count, authentication capacity, backhaul rate, and WLAN identifier.
- FIG. 4 is a block diagram showing the UE 100.
- the UE 100 includes a receiver (receiver) 110, a transmitter (transmitter) 120, and a controller (controller) 130.
- the receiver 110 and the transmitter 120 may be an integrated transceiver (transmission / reception unit).
- the UE 100 may include a receiver 110 and a transmitter 120 that are commonly used for cellular communication and WLAN communication.
- the UE 100 may include a receiver 110 and a transmitter 120 for cellular communication, and a receiver 110 and a transmitter 120 for WLAN communication, respectively.
- the receiver 110 performs various types of reception under the control of the controller 130.
- the receiver 110 includes an antenna.
- the receiver 110 converts a radio signal received by the antenna into a baseband signal (received signal) and outputs it to the controller 130.
- the transmitter 120 performs various transmissions under the control of the controller 130.
- the transmitter 120 includes an antenna.
- the transmitter 120 converts the baseband signal (transmission signal) output from the controller 130 into a radio signal and transmits it from the antenna.
- the controller 130 performs various controls in the UE 100.
- the controller 130 can control the receiver 110 and the transceiver 120.
- the controller 130 includes a processor and a memory.
- the memory stores a program executed by the processor and information used for processing by the processor.
- the processor includes a baseband processor and a CPU (Central Processing Unit).
- the baseband processor performs modulation / demodulation and encoding / decoding of the baseband signal.
- the CPU performs various processes by executing programs stored in the memory.
- the controller 130 executes various processes described later and various communication protocols described above.
- a process executed by at least one of the receiver 110, the transmitter 120, and the controller 130 included in the UE 100 will be described as a process (operation) executed by the UE 100 for convenience.
- FIG. 5 is a block diagram showing the eNB 200.
- the eNB 200 includes a receiver (reception unit) 210, a transmitter (transmission unit) 220, a controller (control unit) 230, and a network interface 240.
- the receiver 210 and the transmitter 220 may be an integrated transceiver (transmission / reception unit).
- the receiver 210 performs various types of reception under the control of the controller 230.
- the receiver 210 includes an antenna.
- the receiver 210 converts a radio signal received by the antenna into a baseband signal (received signal) and outputs it to the controller 230.
- the transmitter 220 performs various transmissions under the control of the controller 230.
- the transmitter 220 includes an antenna.
- the transmitter 220 converts the baseband signal (transmission signal) output from the controller 230 into a radio signal and transmits it from the antenna.
- the controller 230 performs various controls in the eNB 200.
- the controller 230 can control the receiver 210, the transmitter 220 and the network interface 240.
- the controller 230 includes a processor and a memory.
- the memory stores a program executed by the processor and information used for processing by the processor.
- the processor includes a baseband processor and a CPU.
- the baseband processor performs modulation / demodulation and encoding / decoding of the baseband signal.
- the CPU performs various processes by executing programs stored in the memory.
- the controller 230 executes various processes described later and various communication protocols described above.
- the network interface 240 is connected to the neighboring eNB 200 via the X2 interface.
- the network interface 240 is connected to the MME 400 and the SGW 500 via the S1 interface.
- the network interface 240 is used for communication performed on the X2 interface and communication performed on the S1 interface.
- the network interface 240 is connected to the WT 600 via the Xw interface.
- the network interface 240 is used for communication performed on the Xw interface.
- a process executed by at least one of the receiver 210, the transmitter 220, the controller 230, and the network interface 240 included in the eNB 200 will be described as a process (operation) executed by the eNB 200 for convenience.
- FIG. 6 is a block diagram showing the AP 300.
- the AP 300 includes a receiver (reception unit) 310, a transmitter (transmission unit) 320, a controller (control unit) 330, and a network interface 340.
- the receiver 310 and the transmitter 320 may be an integrated transceiver (transmission / reception unit).
- the receiver 310 performs various types of reception under the control of the controller 330.
- Receiver 310 includes an antenna.
- the receiver 310 converts a radio signal received by the antenna into a baseband signal (received signal) and outputs it to the controller 330.
- the transmitter 320 performs various transmissions under the control of the controller 330.
- the transmitter 320 includes an antenna.
- the transmitter 320 converts the baseband signal (transmission signal) output from the controller 330 into a radio signal and transmits it from the antenna.
- the controller 330 performs various controls in the AP 300.
- the controller 330 can control the receiver 310, the transmitter 320 and the network interface 340.
- the controller 330 includes a processor and a memory.
- the memory stores a program executed by the processor and information used for processing by the processor.
- the processor includes a baseband processor and a CPU.
- the baseband processor performs modulation / demodulation and encoding / decoding of the baseband signal.
- the CPU performs various processes by executing programs stored in the memory.
- the controller 330 executes various processes described later and various communication protocols described above.
- the network interface 340 is connected to the backhaul via a predetermined interface.
- Network interface 340 is connected to WT 600 and is used for communication with WT 600 and the like.
- a process executed by at least one of the receiver 310, the transmitter 320, the controller 330, and the network interface 340 included in the AP 300 will be described as a process (operation) executed by the AP 300 for convenience.
- FIG. 7 is a block diagram showing WT 600.
- the WT 600 includes a controller (control unit) 630 and a network interface 640.
- the controller 630 performs various controls in the WT 600.
- the controller 630 can control the network interface 640.
- the controller 630 includes a processor and a memory.
- the memory stores a program executed by the processor and information used for processing by the processor.
- the processor includes a baseband processor and a CPU.
- the baseband processor performs modulation / demodulation and encoding / decoding of the baseband signal.
- the CPU performs various processes by executing programs stored in the memory.
- the controller 630 executes various processes described later and various communication protocols described above.
- the network interface 640 is connected to the backhaul via a predetermined interface.
- the network interface 640 is connected to the AP 300 and is used for communication with the AP 300.
- the network interface 640 is connected to the eNB 200 via the Xw interface.
- the network interface 640 is used for communication performed on the Xw interface.
- a process executed by at least one of the controller 630 and the network interface 640 included in the WT 600 will be described as a process (operation) executed by the WT 600 for the sake of convenience.
- FIG. 8 is a sequence diagram for explaining the operation according to the embodiment.
- UE 100 is located in a cell (Primary Cell) managed by eNB 200-1 (Source eNB 200-1). In the initial state, the UE 100 is in the RRC connection state.
- the eNB 200-1 transmits the LWA configuration (LWA configuration) to the UE 100.
- the UE 100 is configured (configured) with LWA.
- the eNB 200-1 may transmit the LWA setting to the UE 100 by individual signaling (for example, RRC Connection Reconfiguration message).
- the LWA setting includes WLAN mobility set. Accordingly, the eNB 200 sets (configures) the WLAN mobility set in the UE 100.
- the UE 100 is configured (configured) with a WLAN mobility set.
- the WLAN mobility set includes the identifier of the AP 300 that is associated with the WT 600. That is, the WT 600 can transfer the data of the UE 100 to the UE 100 or the eNB 200 via the AP 300 indicated by the identifier of the AP 300.
- the UE 100 can execute the LWA operation.
- the UE 100 can communicate with the eNB 200 by using not only the radio resource of the eNB 200 but also the radio resource of the WLAN 30.
- the eNB 200 may transmit the WLAN measurement configuration (WLAN Measurement configuration) to the UE 100. Accordingly, the UE 100 is set (configured) to perform the WLAN measurement report.
- WLAN Measurement configuration WLAN Measurement configuration
- the UE 100 may transmit a WLAN measurement report to the eNB 200-1.
- the UE 100 transmits a WLAN measurement report to the eNB 200-1 using RSSI based on the radio signal from the AP 300 as a trigger.
- the eNB 200 receives the WLAN measurement report from the UE 100.
- the UE 100 transmits a measurement report (Measurement Report) to the eNB 200-1.
- eNB200 receives a measurement report from UE100.
- the measurement report includes a measurement value of a reception level (reception strength: RSRP (Reference Signal Receive Power) and / or reception quality: RSRQ (Reference Signal Received Quality), etc.) of the received signal from the eNB 200 (cell).
- RSRP Reference Signal Receive Power
- RSRQ Reference Signal Received Quality
- step S105 the eNB 200-1 determines handover to the eNB 200-2 based on the measurement report.
- step S106 the eNB 200-1 sends a handover request message to the eNB 200-2 in response to the handover decision.
- the handover request message is a message for requesting preparation of resources for handover.
- the handover request message is a message for passing information necessary for preparing a handover on the target side.
- the handover request message may include an identifier of WT 600 (for example, WT ID).
- the identifier of WT 600 indicates WT 600 associated with the identifier of AP 300 included in the WLAN mobility set set for UE 100. That is, WT 600 and AP 300 included in the WLAN mobility set are associated with each other.
- the WT 600 manages the AP 300.
- the handover request message may include the UE 100 identifier.
- the identifier of the UE 100 is, for example, at least one of UE ID and WT UE XwAP ID.
- the UE ID indicates the WLAN MAC address of the UE.
- the WT UE XwAP ID is an identifier of the UE 100 assigned by the WT 600.
- the eNB 200-2 can omit the operation (transmission / reception of the RRC message) of acquiring the UE's WLAN MAC address from the UE 100.
- the handover request message may include a WLAN mobility set set for the UE 100.
- the handover request message may include information on the WLAN measurement report from the UE 100.
- the eNB 200-1 may include the latest WLAN measurement report information received from the UE 100 in the handover request message.
- the WLAN measurement report information may be all of the WLAN measurement reports received from the UE 100.
- the WLAN measurement report information may be a part of the WLAN measurement report received from the UE 100.
- the eNB 200-2 receives the handover request message.
- the eNB 200-2 can determine that the LWA is set for the UE 100 that is the handover target.
- the eNB 200-2 can grasp the WT 600 associated with the identifier of the AP 300 included in the WLAN mobility set set in the UE 100 based on the identifier of the WT 600. That is, the eNB 200-2 can specify a transmission destination of a WT addition request message described later. Therefore, the eNB 200-2 does not need to send a WT addition request message to another WT 600.
- the eNB 200-2 sends a WT addition request message (WT Addition Request) to the WT 600.
- the eNB 200-2 may send a WT addition request message to the WT 600 based on the identifier of the WT 600 included in the handover request message.
- the eNB 200-2 may send a WT addition request message to the WT 600 in response to receiving the handover request message.
- WT addition request message is a message for requesting resource preparation for LWA for a specific UE (UE 100).
- the WT addition request message may include the UE 100 identifier (at least one of UE ID and WT UE XwAP ID) included in the handover request message. With this identifier, WT 600 can identify UE 100. Therefore, the WT 600 can determine whether the UE 100 is a known UE in which the WLAN mobility set is set.
- the WT addition request message includes a WLAN mobility set.
- the WLAN mobility set may be a WLAN mobility set included in the handover request message. Thereby, the WLAN mobility set already set in the UE 100 can be effectively used.
- the eNB 200-2 may include the WLAN mobility set based on the information in the WT addition request message.
- the eNB 200-2 can set an appropriate WLAN mobility set in the UE 100 by creating (updating) the WLAN mobility set based on the information of the WLAN measurement report.
- the eNB 200-2 may be a WLAN mobility set candidate scheduled to be provided to the UE 100 by the eNB 200-2 as a WLAN mobility set to be included in the WT addition request message.
- the eNB 200-2 may include the WLAN mobility set candidate created based on the information of the WLAN measurement report as a WLAN mobility set in the WT addition request message.
- the WT 600 receives a WT addition request message from eNB 200.
- the WT 600 may determine whether to approve the WT addition request based on the WLAN mobility set.
- step S108 the WT 600 sends a response to the WT addition request message to the eNB 200.
- WT 600 may send a WT addition request approval message (WT Addition Request ACK. (ACKNOWLEDGE)) as a response.
- WT Addition Request ACK. ACKNOWLEDGE
- the WT addition request approval message is a message for the eNB 200 to confirm (confirm) the WT addition preparation.
- the WT 600 may send a WT addition request approval message when the WLAN mobility set included in the WT addition request message matches the WLAN mobility set set in the UE 100.
- the WT 600 may send a WT addition request approval message.
- the WT addition request approval message may include information indicating that the WT 600 holds the UE 100 context information (for example, the UE 100 identifier and the WLAN mobility set).
- the WT 600 may update the WLAN mobility set (candidate).
- the WT 600 may include the updated WLAN mobility set in the WT addition request approval message.
- the WT 600 may add the identifier of the AP 300 that is not included in the WLAN mobility set (candidate) among the identifiers of the AP 300 of the WLAN mobility set set in the UE 100 to the WLAN mobility set (candidate).
- the WT 600 may include the added WLAN mobility set as an updated WLAN mobility set in the WT addition request approval message.
- the WT 600 may include the WLAN mobility set itself set in the UE 100 as an updated WLAN mobility set in the WT addition request approval message.
- WT 600 may send a WT addition request rejection message (WT Addition Request NACK. (NACKNOWLEDGE)) as a response.
- WT Addition Request NACK. NACKNOWLEDGE
- the WT addition request rejection message is a message for notifying the eNB 200 that the WT addition preparation has failed.
- WT 600 may send a WT addition request rejection message based on the WLAN mobility set included in the WT addition request message. For example, if the WLAN mobility set included in the WT addition request message includes an identifier of the AP 300 that is not associated with itself (WT 600), the WT 600 may send a WT addition request rejection message. When the WLAN mobility set included in the WT addition request message includes the identifier of the AP 300 that is not included in the WLAN mobility set configured in the UE 100, the WT 600 may send a WT addition request rejection message.
- the WT addition request rejection message may include reason information indicating that the message is based on the WLAN mobility set included in the WT addition request message.
- the reason information may indicate that the WLAN mobility set (candidate) includes an identifier of the AP 300 that is not associated with the WT 600.
- the reason information may indicate that the WLAN mobility set (candidate) does not match the WLAN mobility set set in the user terminal.
- the reason information may indicate that the WLAN mobility set (candidate) includes an identifier of the AP 300 that is not included in the WLAN mobility set configured in the user terminal.
- the WT addition request rejection message may include the WLAN mobility set (the identifier of the AP 300) set in the UE 100.
- the eNB 200-2 can grasp the WLAN mobility set (the identifier of the AP 300) set in the UE 100.
- the eNB 200-2 can update the WLAN mobility set based on the reason information and / or the WLAN mobility set included in the WT addition request rejection message.
- the eNB 200-2 may send a new WT addition request message including the updated WLAN mobility set to the WT 600.
- step S109 the eNB 200-2 sends a response to the handover request message to the eNB 200-1.
- the eNB 200-2 may send a handover request approval message (HO Request ACK. (ACKNOWLEDGE)) as a response.
- the eNB 200-2 may send a handover request approval message in response to receiving the WT addition request approval message.
- the handover request approval message is a message for notifying the eNB 200-1 about resources prepared in the target (eNB 200-2).
- the handover request approval message may include holding information indicating that the WT 600 holds UE 100 context information (for example, a WLAN mobility set).
- the eNB 200-2 may include the information received from the WT 600 in the handover request approval message by the WT addition request approval message.
- the eNB 200-2 may newly generate information indicating that the WT 600 holds the context information of the UE 100, and may include the generated information in the handover request approval message.
- eNB200-1 can grasp
- the eNB 200-1 sends a WT release request message to the WT 600 when the UE 100 executes a handover.
- the WT release request message is a message requesting release of resources.
- WT600 also releases the context information of UE100.
- the eNB 200-1 may send a WT release request message including an instruction (information) for not releasing the context information of the UE 100 to the WT 600.
- the instruction may be retained information.
- the WT 600 can release the connection (UE Associated Signaling Connection (XwAP)) between the eNB 200 and the WT 600 while retaining the context information of the UE 100.
- XwAP UE Associated Signaling Connection
- the holding information may be different from the existing UE context holding indicator (UE Context Kept Indicator).
- the UE context holding indicator indicates that UE context information is held in the SeNB in a case where a handover is performed between the MeNB (Master eNB) (inter-MeNB) without changing the SeNB (Secondary eNB).
- MeNB Master eNB
- inter-MeNB inter-MeNB
- SeNB SeNB
- eNB200-1 can grasp
- the eNB 200-2 when handover is executed between the MeNBs without changing the SeNB, the handover request approval message May be included.
- DC is an operation mode of the UE 100 in the RRC connection state in which a master cell group and a secondary cell group are set.
- a master cell group is a group of serving cells associated with a MeNB in a DC, and is composed of a PCell and optionally one or more SCells.
- a secondary cell group is a group of serving cells associated with a SeNB and is composed of PSCells and optionally one or more SCells.
- the SeNB is an eNB 200 that provides additional radio resources for the UE 100 in the DC but is not a MeNB.
- the eNB 200-2 may use an existing UE context holding indicator (UE Context Kept Indicator) as holding information when DC is not being executed.
- the eNB 200-1 may recognize an existing UE context holding indicator (UE Context Kept Indicator) as holding information when DC is not being executed.
- the eNB 200-2 may send a handover request rejection message (HO Request NACK. (NACKNOWLEDGE)) as a response.
- the eNB 200-2 may send a handover request rejection message in response to receiving the WT addition request rejection message.
- the handover request rejection message is a message for notifying the eNB 200-1 that handover preparation has failed.
- the eNB 200-2 will be described assuming that a handover request approval message has been sent as a response.
- step S110 the eNB 200-1 transmits an RRC message (RRC Conn. Reconf.) For executing the handover to the UE 100.
- the UE 100 starts an operation for executing a handover.
- step S111 operations in the handover execution phase (HO Exception) and the handover completion phase (HO Completion) are executed.
- the UE 100 performs an LWA operation in communication with the eNB 200-2.
- the eNB 200-2 may execute LWA (WLAN mobility set) setting for the UE 100.
- the eNB 200-2 may transmit the difference from the LWA setting already set in the UE 100 to the UE 100.
- the handover can be executed in a state in which the WT 600 related to the WLAN mobility set set in the UE 100 is maintained. As a result, even when a handover is executed, the LWA operation can be executed smoothly. After the handover is completed, signaling (or overhead) for newly setting up the LWA may be reduced.
- the eNB 200-2 transmits the WT addition request message has been described, but the present invention is not limited to this.
- the eNB 200 may send a WT change request message (WT Modification Request) instead of the WT addition request message. Therefore, the “WT addition request” described above can be appropriately replaced with a “WT change request”.
- the WT change request message sent from the eNB 200-2 to the WT 600 is a message requesting preparation for changing the WT resource for the specific UE.
- the WT change request approval message sent from the WT 600 to the eNB 200-2 is a message for confirming (approving) the request of the eNB 200-2 for changing the WT resource for the specific UE.
- the WT change request rejection message sent from the WT 600 to the eNB 200-2 is a message for notifying the eNB 200-2 that the WT change initiated by the eNB 200-2 has failed.
- the operations of the UE 100, the eNB 200, and the WT 600 have been described in a series of sequences. However, only a part of the operations may be performed and not all the operations may be performed.
- a program for causing a computer to execute each process performed by any of the above-described nodes may be provided.
- the program may be recorded on a computer readable medium. If a computer-readable medium is used, a program can be installed in the computer.
- the computer-readable medium on which the program is recorded may be a non-transitory recording medium.
- the non-transitory recording medium is not particularly limited, but may be a recording medium such as a CD-ROM or a DVD-ROM.
- a chip configured by a memory that stores a program for executing each process performed by any of the UE 100, eNB 200, AP 300, and WT 600 and a processor that executes the program stored in the memory may be provided.
- the LTE system has been described as an example of the mobile communication system, but the present disclosure is not limited to the LTE system.
- the present disclosure may be applied to a system other than the LTE system.
- Steps S1 and S2 Handover request and WT addition request (HANDOVER REQUEST & WT ADDITION REQUEST) Regarding the extension (ExtDC), the handover request includes a Global SeNB ID and a SeNB UE X2AP ID IE as UE context reference in the SeNB, and these information are used in the corresponding SENB addition request.
- WT ID and WT UE XwAP ID IE are required for handover request, and WT UE XwAP ID IE needs to be included in WT addition request.
- the WT addition request has the UE identifier IE (ie, the UE's WLAN MAC address) as a mandatory IE.
- the handover request needs to notify the UE identifier IE when it is desirable to hold the UE identifier IE as essential in the WT addition request.
- Mobility set Assume that the source eNB and the target eNB each have a mobility set and different mobility sets may be provided to the WT during inter-eNB handover without WT changes. In this case, it may be a problem if the new mobility set provided by the target eNB does not include the WLAN (eg, BSSID) that the UE is currently associated with. Therefore, either the eNB or the WT checks whether a new mobility set is applicable to this LWA. If the target eNB performs the check, depending on the implementation, in the handover request, for example, the WLAN measurement result (to be understood from the RRC container), the WLAN identifier currently associated with the UE, and / or (old) The mobility set may need to be notified from the source eNB.
- the WLAN eg, BSSID
- the WT performs the check, such information transfer may not be necessary since it knows the WLAN identifier associated with the UE, but it is done blindly from the perspective of the target eNB, That is, the target eNB does not know that the WLAN is included in the mobility set. To avoid such ambiguous behavior, it may be desirable to be responsible for the eNB.
- Step S3 WT addition request approval (WT Addition REQUEST ACKNOWLEDGE) If the WT can grant the WLAN resource request, the WT responds with a WT add request approval. In an abnormal case where the WT receives a WT UE XwAP ID IE and the WT UE XwAP ID IE does not match an existing UE context with such an ID, the WT rejects the WT addition request (as in the extended DC case) WT ADDITION REQUEST REJECT) can be used to reject the procedure.
- Step S4 Handover request approval (HANDOVER REQUEST ACKNOWLEDGE)
- the target eNB may indicate to the source MeNB whether the UE context is maintained in the WT. With respect to this indication (indication), unless the source eNB needs to distinguish between eLWA and extended DC, that is, unless simultaneous execution of inter-eNB handover without WT change and inter-MeNB handover without SeNB change is permitted.
- the existing UE Context Kept Indicator IE may be reusable. This release makes sense because the simultaneous deployment of LWA and DC is excluded.
- Step S5 WT release request (WT RELEASE REQUEST) Similar to the assumption of handover request approval, the UE Context Kept Indicator IE may be reusable. The IE facilitates that the WT understands that only resources related to UE related signaling connections towards the source eNB should be released.
- Step S6 WT related confirmation (WT ASSOCIATION CONFIRMATION)
- the WT may send this message to the target eNB after successful association.
- ⁇ Whether UE re-association is required depends on the RAN2.
- Step S7 Path switching procedure (Path Switch procedure) Since the LWA operation is transparent to the MME, the target eNB executes a path switching procedure like a normal handover.
- Step S9 Release UE context from source eNB to WT
- the UE context release is the source Initiated by MeNB.
- the UE context release has not been clarified so far and so is not the same. It should be considered whether a WT release request can be used for this purpose, i.e., after step 5, only the WT can release C-plane related resources. If necessary, a new UE context release procedure may be introduced in XwAP.
- Proposal 1 The above consideration should be taken into account.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
一の実施形態に係る通信方法では、第1の基地局が、1以上のWLAN(Wireless Local Area Network)識別子のセットであるWLANモビリティセットをユーザ装置へ設定する。前記第1の基地局が、第2の基地局への前記ユーザ装置のハンドオーバを決定する。前記第1の基地局が、前記ユーザ装置のためのハンドオーバ要求メッセージに、前記1以上のWLAN識別子が関連付けられているWLAN終端装置の識別子を含める。前記第1の基地局が、前記WLAN終端装置の識別子を含む前記ハンドオーバ要求メッセージを前記第2の基地局へ送る。
図1は、実施形態に係るシステム構成を示す図である。図1に示すように、LTEシステムは、複数のUE(User Equipment)100と、E-UTRAN(Evolved Universal Terrestrial Radio Access Network)10と、EPC(Evolved Packet Core)20と、を含む。
LWA(LTE-WLAN Aggregation)について、図3を用いて説明する。図3は、LWAで用いられるeNB200の無線プロトコル構造(radio protocol architecture)を示す。
WLANモビリティセットについて、説明する。WLANモビリティセットは、1以上のWLAN識別子(例えば、BSSID(Basic Service Set ID)、HESSID(Homogenous Extended Service Set ID)及びSSID(Service Set ID)など)により識別される1つ以上のAP300のセットである。UE100は、eNB200への通知なく、WLANモビリティセットに属するAP300間でモビリティを実行してもよい。
LWAをサポートするUE100は、WLAN測定報告を実行するためにeNB200(E-UTRAN10)により設定(コンフィグ)されてもよい。WLAN測定対象は、WLAN識別子、WLANチャネル番号(WLAN channel number)及びWLAN帯域(WLAN band)の少なくともいずれかにより設定されてもよい。
UE100(無線端末)の構成について説明する。図4は、UE100を示すブロック図である。
eNB200(基地局)の構成について説明する。図5は、eNB200を示すブロック図である。
AP300(無線LANアクセスポイント)の構成について説明する。図6は、AP300を示すブロック図である。
WT600(WLAN終端装置)の構成について説明する。図7は、WT600を示すブロック図である。
実施形態に係る動作について、図8を用いて説明する。図8は、実施形態に係る動作を説明するためのシーケンス図である。
上述した各実施形態によって、本出願の内容を説明したが、この開示の一部をなす論述及び図面は、本出願の内容を限定するものであると理解すべきではない。この開示から当業者には様々な代替実施形態、実施例及び運用技術が明らかとなろう。
(1)導入
この付記では、WT変更を伴わないeNB間ハンドオーバ(inter eNB handover)の初期考察を提供する。
UE関連のXwAP手順(UE-associated XwAP procedures)は、Rel-12 DCに関するX2手順に基づいてRel-13で明確化された。従って、それを、拡張DC(ExtDC)のためのRel-13 X2手順(すなわち、SeNB変更を伴わないMeNB間ハンドオーバ)を考慮して、WT変更を伴わないeNB間ハンドオーバの拡張について検討するベースラインとみなすことができる。WT変更を伴わないeNB間ハンドオーバのベースラインとして、シグナリングフローを図9に示すことができる。図9は、WT変更を伴わないeNB間ハンドオーバのためのベースラインシグナリングフローを示す。
拡張(ExtDC)に関して、ハンドオーバ要求は、SeNBにおけるUEコンテキストリファレンスとして、Global SeNB ID及びSeNB UE X2AP ID IEを含み、これらの情報は、対応するSENB追加要求で用いられる。eLWAに対応して、WT ID及びWT UE XwAP ID IEがハンドオーバ要求に必要であり、WT UE XwAP ID IEがWT追加要求に含まれる必要がある。
WT追加要求は、UE識別子IE(すなわち、UEのWLAN MACアドレス)を必須IEとして有する。しかしながら、ターゲットeNBが、WT追加要求上でその識別子を知る方法がない可能性がある。従って、ハンドオーバ要求は、WT追加要求においてUE識別子IEを必須として保持することが望ましい場合には、UE識別子IEを通知する必要がある。
ソースeNB及びターゲットeNBはそれぞれ、モビリティセットを有し、WT変更を伴わないeNB間ハンドオーバ中に異なるモビリティセットがWTに提供される可能性があると仮定する。このケースでは、ターゲットeNBによって提供される新たなモビリティセットが、UEが現在関連しているWLAN(例えば、BSSID)を含まない場合、問題である可能性がある。従って、eNB又はWTのいずれかが、新しいモビリティセットがこのLWAに適用可能かどうかをチェックする。ターゲットeNBがチェックを実行する場合、実装に応じて、ハンドオーバ要求内で、例えば、(RRCコンテナから理解されるべき)WLAN測定結果、UEに現在関連付けられているWLAN識別子、及び/又は(古い)モビリティセットを、ソースeNBから通知される必要があってもよい。一方、WTがチェックを実行する場合、UEに関連するWLAN識別子を知っているので、そのような情報転送は必要ではないかもしれないが、ターゲットeNBの観点からは盲目的に行われている、すなわち、ターゲットeNBはWLANがそのモビリティセットに含まれていることを知らない。そのような曖昧な動作を避けるためには、eNBに責任を有することが望ましい可能性がある。
WTがWLANリソース要求を認めることができる場合、WTは、WT追加要求承認で応答する。WTがWT UE XwAP ID IEを受信し、WT UE XwAP ID IEがそのようなIDを有する既存のUEコンテキストと一致しないアブノーマルケースでは、WTは、拡張DCのケースと同様に、WT追加要求拒否(WT ADDITION REQUEST REJECT)を用いて、当該手順を拒否できる。
拡張DCのための既存の手順によれば、ターゲットeNBは、UEコンテキストがWTに保持されているかどうかをソースMeNBに示してもよい。この指示(インディケーション)に関して、ソースeNBがeLWAと拡張DCとを区別する必要がない限り、すなわち、WT変更を伴わないeNB間ハンドオーバとSeNB変更を伴わないMeNB間ハンドオーバの同時実行が許可されない限り、既存のUE Context Kept Indicator IEを再利用できてもよい。今回のリリースでは、LWAとDCの同時展開が除外されているため、意味がある。
ハンドオーバ要求承認の仮定と同様に、UE Context Kept Indicator IEを再使用できてもよい。当該IEは、ソースeNBに向けたUE関連シグナリング接続に関するリソースのみが解放されるべきであることをWTが理解することを容易にする。
WTは、関連付け成功後、このメッセージをターゲットeNBに送信してもよい。
LWA動作は、MMEに対してトランスペアレントであるため、ターゲットeNBは、通常のハンドオーバのようにパス切り替え手順を実行する。
ターゲットeNBは、現在のように、当該メッセージをソースeNBへ送る。
拡張DCの既存の手順によれば、ソースMeNBに向かうUEコンテキストに関連付けられたリソースに関するCプレーンをSeNBに解放させるために、UEコンテキスト解放は、ソースMeNBによって開始される。eLWAのケースでは、XwAPにおいて、UEコンテキスト解放がこれまで明確化されていないため、同じではない。WT解放要求がこの目的のために使用できるかどうか、すなわち、ステップ5の後に、WTのみがCプレーン関連リソースを解放できるかどうか、を検討すべきである。必要に応じて、XwAPにおいて、新しいUEコンテキスト解放手順が導入されてもよい。
Claims (12)
- 通信方法であって、
第1の基地局が、1以上のWLAN(Wireless Local Area Network)識別子のセットであるWLANモビリティセットをユーザ装置へ設定し、
前記第1の基地局が、第2の基地局への前記ユーザ装置のハンドオーバを決定し、
前記第1の基地局が、前記ユーザ装置のためのハンドオーバ要求メッセージに、前記1以上のWLAN識別子が関連付けられているWLAN終端装置の識別子を含め、
前記第1の基地局が、前記WLAN終端装置の識別子を含む前記ハンドオーバ要求メッセージを前記第2の基地局へ送る、通信方法。 - 前記第2の基地局が、前記WLAN終端装置の識別子に基づいて特定された前記WLAN終端装置に対して、前記ユーザ装置のためのリソースの準備を要求するためのWLAN追加要求メッセージを送る請求項1に記載の通信方法。
- 前記第1の基地局が、前記ハンドオーバ要求メッセージに、前記WLAN終端装置により割り当てられた前記ユーザ装置の識別子を含め、
前記第1の基地局が、前記ユーザ装置の識別子を含む前記ハンドオーバ要求メッセージを前記第2の基地局へ送る請求項1に記載の通信方法。 - 前記第2の基地局が、前記ユーザ装置のためのリソースの準備を要求するためのWLAN追加要求メッセージに、前記WLAN終端装置により割り当てられた前記ユーザ装置の識別子を含め、
前記第2の基地局が、前記ユーザ装置の識別子の識別子を含む前記WLAN追加要求メッセージを前記WLAN終端装置へ送る請求項3に記載の通信方法。 - 前記WLAN終端装置が、前記WLAN追加要求メッセージに対する応答であるWLAN追加要求承認メッセージを前記第2の基地局へ送り、
前記第2の基地局が、前記ハンドオーバ要求メッセージに対する応答であるハンドオーバ要求承認メッセージに、前記WLAN終端装置が前記ユーザ装置のコンテキストを保持することを示す保持情報を含め、
前記第2の基地局が、前記保持情報を含む前記ハンドオーバ要求承認メッセージを前記第1の基地局へ送る請求項4に記載の通信方法。 - 前記第1の基地局が、前記ユーザ装置のためのリソースの解放を要求するWT解放メッセージに、前記WLAN終端装置が前記ユーザ装置のコンテキストを保持することを示す保持情報を含め、
前記第1の基地局が、前記保持情報を含む前記WT解放メッセージを前記WLAN終端装置へ送る請求項1に記載の通信方法。 - 第1の基地局を制御するためのプロセッサであって、
1以上のWLAN(Wireless Local Area Network)識別子のセットであるWLANモビリティセットをユーザ装置へ設定する処理と、
第2の基地局への前記ユーザ装置のハンドオーバを決定する処理と、
前記ユーザ装置のためのハンドオーバ要求メッセージに、前記1以上のWLAN識別子が関連付けられているWLAN終端装置の識別子を含める処理と、
前記WLAN終端装置の識別子を含む前記ハンドオーバ要求メッセージを前記第2の基地局へ送る処理と、を実行するプロセッサ。 - 第1の基地局であって、
コントローラを備え、
前記コントローラは、
1以上のWLAN(Wireless Local Area Network)識別子のセットであるWLANモビリティセットをユーザ装置へ設定し、
第2の基地局への前記ユーザ装置のハンドオーバを決定し、
前記ユーザ装置のためのハンドオーバ要求メッセージに、前記1以上のWLAN識別子が関連付けられているWLAN終端装置の識別子を含め、
前記WLAN終端装置の識別子を含む前記ハンドオーバ要求メッセージを前記第2の基地局へ送る、よう構成される第1の基地局。 - 第2の基地局を制御するためのプロセッサであって、
1以上のWLAN(Wireless Local Area Network)識別子のセットであるWLANモビリティセットが設定されたユーザ装置のためのハンドオーバ要求メッセージを第1の基地局から受信する処理を実行し、
前記ハンドオーバ要求メッセージは、前記1以上のWLAN識別子が関連付けられているWLAN終端装置の識別子を含むプロセッサ。 - 第2の基地局であって、
コントローラを備え、
前記コントローラは、
1以上のWLAN(Wireless Local Area Network)識別子のセットであるWLANモビリティセットが設定されたユーザ装置のためのハンドオーバ要求メッセージを第1の基地局から受信するよう構成され、
前記ハンドオーバ要求メッセージは、前記1以上のWLAN識別子が関連付けられているWLAN終端装置の識別子を含む第2の基地局。 - ネットワーク装置を制御するためのプロセッサであって、
ユーザ装置のためのリソースの準備を要求するためのWLAN追加要求メッセージを基地局から受信する処理を実行し、
前記WLAN追加要求メッセージは、前記ネットワーク装置により割り当てられたユーザ装置の識別子を含むプロセッサ。 - ネットワーク装置であって、
コントローラを備え、
前記コントローラは、
ユーザ装置のためのリソースの準備を要求するためのWLAN追加要求メッセージを基地局から受信するよう構成され、
前記WLAN追加要求メッセージは、前記ネットワーク装置により割り当てられたユーザ装置の識別子を含むネットワーク装置。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP17774739.1A EP3422769B1 (en) | 2016-04-01 | 2017-03-24 | Communication method, processor, base station, and network device |
JP2018509227A JP6487111B2 (ja) | 2016-04-01 | 2017-03-24 | 通信方法、プロセッサ、基地局、及びネットワーク装置 |
US16/145,636 US10820239B2 (en) | 2016-04-01 | 2018-09-28 | Communication method, processor, base station, and network apparatus |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201662316752P | 2016-04-01 | 2016-04-01 | |
US62/316,752 | 2016-04-01 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/145,636 Continuation US10820239B2 (en) | 2016-04-01 | 2018-09-28 | Communication method, processor, base station, and network apparatus |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2017170202A1 true WO2017170202A1 (ja) | 2017-10-05 |
Family
ID=59965601
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2017/011956 WO2017170202A1 (ja) | 2016-04-01 | 2017-03-24 | 通信方法、プロセッサ、基地局、及びネットワーク装置 |
Country Status (4)
Country | Link |
---|---|
US (1) | US10820239B2 (ja) |
EP (1) | EP3422769B1 (ja) |
JP (2) | JP6487111B2 (ja) |
WO (1) | WO2017170202A1 (ja) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109842901A (zh) * | 2018-12-17 | 2019-06-04 | 中磊电子股份有限公司 | 基地台及其换手控制方法 |
US11363504B2 (en) | 2018-12-17 | 2022-06-14 | Sercomm Corporation | Base station and handover control method thereof |
WO2024110693A1 (en) * | 2022-11-25 | 2024-05-30 | Elisa Oyj | Overshooter detection in a radio network based on restriction of data traffic |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3481102B1 (en) * | 2016-06-29 | 2020-08-05 | Beijing Xiaomi Mobile Software Co., Ltd. | Data transmission system, data transmission method, data aggregation method and apparatus |
CN112888022B (zh) * | 2016-11-16 | 2024-02-02 | 华为技术有限公司 | 数据迁移方法及装置 |
CN111200851A (zh) * | 2018-11-20 | 2020-05-26 | 华为技术有限公司 | 一种数据通信方法以及装置 |
Family Cites Families (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3016437B1 (en) * | 2013-08-07 | 2019-01-02 | Huawei Technologies Co., Ltd. | Handover in dual connection mode |
US20150109927A1 (en) * | 2013-10-18 | 2015-04-23 | Qualcomm Incorporated | Base station to access point interface for data bearer routing |
EP3917212A1 (en) * | 2014-02-19 | 2021-12-01 | Convida Wireless, LLC | Serving gateway extensions for inter-system mobility |
WO2016190902A1 (en) * | 2015-05-26 | 2016-12-01 | Intel IP Corporation | Wlan mobility for lte/wlan aggregation |
US10517132B2 (en) * | 2015-07-17 | 2019-12-24 | Telefonaktiebolaget Lm Ericsson (Publ) | Terminal devices, network nodes and methods of operating the same |
CN108141898A (zh) * | 2015-09-22 | 2018-06-08 | Lg电子株式会社 | 基站支持ran共享的方法和装置 |
WO2017078459A1 (en) * | 2015-11-05 | 2017-05-11 | Samsung Electronics Co., Ltd. | Method, ue and network node for protecting user privacy in networks |
WO2017095131A1 (en) * | 2015-12-01 | 2017-06-08 | Lg Electronics Inc. | Method and apparatus for performing application category based traffic steering in wireless communication system |
CN107277850B (zh) * | 2016-04-01 | 2022-04-19 | 北京三星通信技术研究有限公司 | 无线局域网聚合的控制方法和相关设备 |
WO2017170164A1 (ja) * | 2016-04-01 | 2017-10-05 | 京セラ株式会社 | 通信方法、プロセッサ、及びユーザ装置 |
US10313933B2 (en) * | 2016-04-01 | 2019-06-04 | Lg Electronics Inc. | Method and apparatus for enhancing mobility for 3GPP LTE-WLAN aggregation in wireless communication system |
WO2017171600A1 (en) * | 2016-04-01 | 2017-10-05 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods, source network node and target network node for handover of a wireless communication device |
US10021617B2 (en) * | 2016-04-01 | 2018-07-10 | Lg Electronics Inc. | Method and apparatus for performing, by terminal in WLAN interworking operation, handover |
US10681541B2 (en) * | 2016-04-29 | 2020-06-09 | Nokia Technologies Oy | Security key usage across handover that keeps the same wireless termination |
-
2017
- 2017-03-24 WO PCT/JP2017/011956 patent/WO2017170202A1/ja active Application Filing
- 2017-03-24 EP EP17774739.1A patent/EP3422769B1/en active Active
- 2017-03-24 JP JP2018509227A patent/JP6487111B2/ja active Active
-
2018
- 2018-09-28 US US16/145,636 patent/US10820239B2/en active Active
-
2019
- 2019-02-20 JP JP2019028183A patent/JP6511208B1/ja active Active
Non-Patent Citations (6)
Title |
---|
3GPP: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2", 3GPP TS 36.300 V13.2.0, 13 January 2016 (2016-01-13) |
CATT: "Discussion on Inter-eNB Handover Procedure for Rel-14 LWA", 3GPP TSG-RAN WG2#93BIS, R2-162187, 1 April 2016 (2016-04-01), XP051081996, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_93bis/Docs/R2-162187.zip> * |
ERICSSON: "Mobility procedures for LTE-WLAN aggregation", 3GPP TSG-RAN WG2#91, R2-153689, 24 August 2015 (2015-08-24), XP051004347, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/ WG2_RL2/TSGR2_91/Docs/R2-153689.zip> * |
LG ELECTRONICS INC: "Consideration on the procedures of Xw AP", 3GPP TSG-RAN WG3#89BIS, R3-152220, 5 October 2015 (2015-10-05), pages 1 - 3, XP051007242, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG3_Iu/TSGR3_89bis/Docs/R3-152220.zip> * |
LG ELECTRONICS: "Serving PLMN for WTAddition and Modification procedure", 3GPP TSG-RAN WG3#91 R3-160455, 15 February 2016 (2016-02-15), pages 2 - 5, XP051066884, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG3_Iu/TSGR3_91/Docs/R3-160455.zip> * |
NEC: "Serving WLAN reporting in LWA", 3GPP TSG-RAN WG3#91, R3-160266, 15 February 2016 (2016-02-15), XP051056137, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG3_Iu/TSGR3_91/Docs/R3-160266.zip> * |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109842901A (zh) * | 2018-12-17 | 2019-06-04 | 中磊电子股份有限公司 | 基地台及其换手控制方法 |
US11363504B2 (en) | 2018-12-17 | 2022-06-14 | Sercomm Corporation | Base station and handover control method thereof |
WO2024110693A1 (en) * | 2022-11-25 | 2024-05-30 | Elisa Oyj | Overshooter detection in a radio network based on restriction of data traffic |
US12114251B2 (en) | 2022-11-25 | 2024-10-08 | Elisa Oyj | Overshooter detection in a radio network based on restriction of data traffic |
Also Published As
Publication number | Publication date |
---|---|
JP6511208B1 (ja) | 2019-05-15 |
JPWO2017170202A1 (ja) | 2018-12-20 |
EP3422769A4 (en) | 2019-01-02 |
US20190045402A1 (en) | 2019-02-07 |
JP6487111B2 (ja) | 2019-03-20 |
US10820239B2 (en) | 2020-10-27 |
JP2019115056A (ja) | 2019-07-11 |
EP3422769B1 (en) | 2020-03-04 |
EP3422769A1 (en) | 2019-01-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP7022793B2 (ja) | 基地局及び無線端末 | |
JP6511208B1 (ja) | 通信方法、プロセッサ、及びネットワーク装置 | |
JP6272444B2 (ja) | 通信方法、基地局、及びプロセッサ | |
JP6638099B2 (ja) | 通信方法、プロセッサ、及びユーザ装置 | |
US10492177B2 (en) | Base station and radio terminal | |
EP3567975B1 (en) | Methods of operating network nodes in a communication network, and network nodes implementing the same | |
WO2016125887A1 (ja) | 基地局 | |
WO2016190357A1 (ja) | 通信制御方法、基地局、及びユーザ端末 | |
JP6423107B2 (ja) | 基地局、プロセッサ、及び終端装置 | |
WO2017026442A1 (ja) | 無線端末、基地局及びwlan装置 | |
WO2017018460A1 (ja) | 基地局 | |
JP6479823B2 (ja) | 基地局、プロセッサ及びネットワーク装置 | |
US20180255601A1 (en) | Base station, wlan terminal node, and radio terminal | |
KR20170036959A (ko) | Lte-wlan 이동성 제어방법 및 장치 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 2018509227 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2017774739 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2017774739 Country of ref document: EP Effective date: 20180928 |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 17774739 Country of ref document: EP Kind code of ref document: A1 |