WO2017135343A1 - 通信方法、無線端末、プロセッサ及び基地局 - Google Patents
通信方法、無線端末、プロセッサ及び基地局 Download PDFInfo
- Publication number
- WO2017135343A1 WO2017135343A1 PCT/JP2017/003702 JP2017003702W WO2017135343A1 WO 2017135343 A1 WO2017135343 A1 WO 2017135343A1 JP 2017003702 W JP2017003702 W JP 2017003702W WO 2017135343 A1 WO2017135343 A1 WO 2017135343A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- enb
- identifier
- base station
- wireless terminal
- connection
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/19—Connection re-establishment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
-
- 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
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/15—Setup of multiple wireless link connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/20—Selecting an access point
-
- 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
-
- 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/08—Access point devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/04—Interfaces between hierarchically different network devices
- H04W92/12—Interfaces between hierarchically different network devices between access points and access point controllers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/16—Interfaces between hierarchically similar devices
- H04W92/20—Interfaces between hierarchically similar devices between access points
Definitions
- the present disclosure relates to a communication method, a wireless terminal, a processor, and a base station used in a communication system.
- Non-Patent Document 1 In 3GPP (3rd Generation Partnership Project), which is a standardization project for mobile communication systems, NB-IoT (NarrowBand Internet of Things) specifications, a new narrowband wireless technology, to meet the demands of IoT (Internet of Things). The formulation is underway (see Non-Patent Document 1, for example).
- Suspend Connection procedure For temporarily suspending a connection between a wireless terminal and a network and a resume procedure (Resume Connection procedure) for resuming the connection are being considered.
- a resume identifier associated with context information of the wireless terminal from the first base station to the wireless terminal Send is information for identifying the first base station.
- the wireless terminal includes a receiver.
- the receiver is configured to receive from the first base station a resume identifier associated with the context information of the wireless terminal in a procedure in which a connection between the wireless terminal and the network is temporarily suspended.
- a part of the restart identifier is information for identifying the first base station.
- the processor is a processor for controlling a wireless terminal.
- the processor executes a process of receiving a resume identifier associated with the context information of the wireless terminal from the first base station in a procedure in which the connection between the wireless terminal and the network is temporarily suspended.
- a part of the restart identifier is information for identifying the first base station.
- the base station includes a transmitter.
- the transmitter is configured to transmit a resume identifier associated with the wireless terminal's context information to the wireless terminal in a procedure in which a connection between the wireless terminal and the network is suspended.
- a part of the restart identifier is information for identifying the base station.
- the processor is a processor for controlling a base station.
- the processor performs a process of transmitting a resumption identifier associated with context information of the wireless terminal to the wireless terminal in a procedure in which the connection between the wireless terminal and the network is temporarily interrupted.
- a part of the restart identifier is information for identifying the base station.
- an unrelated terminal executes a procedure in which the connection between the wireless terminal and the network is temporarily interrupted.
- Information indicating whether the connection can be resumed is transmitted from the base station to the wireless terminal.
- the wireless terminal determines whether the connection can be resumed based on the information.
- FIG. 1 is a diagram illustrating a configuration of an LTE system.
- FIG. 2 is a protocol stack diagram of a radio interface in the LTE system.
- FIG. 3 is a configuration diagram of a radio frame used in the LTE system.
- FIG. 4 is a block diagram of the UE 100.
- FIG. 5 is a block diagram of the eNB 200.
- FIG. 6 is a sequence diagram for explaining the outline of the temporary suspension procedure.
- FIG. 7 is a sequence diagram for explaining the outline of the restart procedure.
- FIG. 8 is a sequence diagram for explaining the operation according to the first embodiment.
- FIG. 9 is a sequence diagram for explaining the first modification according to the first embodiment.
- FIG. 10 is a sequence diagram for explaining the second modification according to the first embodiment.
- FIG. 11 is a flowchart for explaining the third modification example according to the first embodiment.
- FIG. 12 is a sequence diagram for explaining the second embodiment.
- a resume identifier associated with context information of the wireless terminal from the first base station to the wireless terminal Send is information for identifying the first base station.
- a connection restart request message may be transmitted from the wireless terminal to a second base station different from the first base station.
- the connection resumption request message may include the resumption identifier.
- a request message for transferring context information of the wireless terminal from the second base station to the first base station and from the second base station to the first base station may be sent.
- the request message may include the resume identifier.
- the wireless terminal may send context information of the wireless terminal from the first base station to the second base station.
- the second base station After the second base station receives the wireless terminal context information, the second base station establishes a connection between the second base station and the mobility management entity (MME) between the second base station and the MME.
- MME mobility management entity
- the second base station may identify the first base station using the restart identifier from the wireless terminal.
- the second resumption identifier associated with the context information of the second wireless terminal may be transmitted from the second wireless terminal to the first base station.
- the second resume identifier may be an identifier shorter than the resume identifier.
- the wireless terminal includes a receiver.
- the receiver is configured to receive from the first base station a resume identifier associated with the context information of the wireless terminal in a procedure in which a connection between the wireless terminal and the network is temporarily suspended.
- a part of the restart identifier is information for identifying the first base station.
- the processor is a processor for controlling a wireless terminal.
- the processor executes a process of receiving a resume identifier associated with the context information of the wireless terminal from the first base station in a procedure in which the connection between the wireless terminal and the network is temporarily suspended.
- a part of the restart identifier is information for identifying the first base station.
- the base station includes a transmitter.
- the transmitter is configured to transmit a resume identifier associated with the wireless terminal's context information to the wireless terminal in a procedure in which a connection between the wireless terminal and the network is suspended.
- a part of the restart identifier is information for identifying the base station.
- the processor is a processor for controlling a base station.
- the processor performs a process of transmitting a resumption identifier associated with context information of the wireless terminal to the wireless terminal in a procedure in which the connection between the wireless terminal and the network is temporarily interrupted.
- a part of the restart identifier is information for identifying the base station.
- an unrelated terminal executes a procedure in which the connection between the wireless terminal and the network is temporarily interrupted.
- Information indicating whether the connection can be resumed is transmitted from the base station to the wireless terminal.
- the wireless terminal determines whether the connection can be resumed based on the information.
- the base station that has temporarily suspended the connection with the wireless terminal holds the context information of the wireless terminal.
- the base station restarts the context information of the wireless terminal.
- the wireless terminal that has shifted to the ECM idle state by the temporary suspension procedure has selected a cell managed by another base station due to movement. If another base station does not hold the context information of the wireless terminal, the restart procedure fails.
- the wireless terminal may have to perform a procedure for establishing a connection after the restart procedure fails. As a result, signaling may increase.
- the wireless terminal requests a resumption of the connection with a receiver that receives a resumption identifier assigned to the wireless terminal in a procedure in which the connection between the wireless terminal and the network is temporarily suspended.
- the identification information may be an identifier of a cell to which the wireless terminal is connected when the procedure is executed.
- the transmitter may transmit information necessary for establishing an RRC connection between the wireless terminal and the base station to the base station together with the resume identifier.
- the transmitter may transmit the resume identifier to the base station when the number of cell reselections after the procedure is executed is less than a threshold.
- the transmitter may omit transmission of the resume identifier when the number of cell reselections is equal to or greater than the threshold.
- the transmitter may transmit the resume identifier to the base station when the wireless terminal is located in an area where the connection can be resumed.
- the transmitter may omit transmitting the resume identifier when the wireless terminal is not located in the area.
- the transmitter may transmit the resume identifier to the base station when the base station is included in a base station group that supports transfer of context information of the wireless terminal.
- the transmitter may omit the transmission of the resume identifier when the base station is not included in the base station group.
- the wireless terminal requests a resumption of the connection with a receiver that receives a resumption identifier assigned to the wireless terminal in a procedure in which the connection between the wireless terminal and the network is temporarily suspended.
- the transmitter may transmit the identification information together with the resume identifier to the base station.
- the receiver may receive information indicating that the base station does not hold the context information from the base station after transmitting the resume identifier.
- the transmitter may transmit the identification information to the base station in response to receiving the information.
- a base station includes a receiver that receives a resume identifier from a wireless terminal, and a controller that, after receiving the resume identifier, sends predetermined information for receiving context information of the wireless terminal to another base station.
- the resume identifier is an identifier assigned to the wireless terminal in a procedure in which a connection between the wireless terminal and the network is temporarily suspended.
- the context information is used to resume the connection.
- At least a part of the resume identifier is identification information for identifying a connection base station to which the wireless terminal is connected when the procedure is executed.
- the controller sends the predetermined information to the other base station.
- the receiver may receive information necessary for establishing an RRC connection between the wireless terminal and the base station from the wireless terminal together with the resume identifier. If the controller does not receive the context information from the other base station, the controller may establish the RRC connection based on the necessary information.
- a base station includes a receiver that receives a resume identifier from a wireless terminal, and a controller that sends predetermined information for receiving context information of the wireless terminal to another base station.
- the resume identifier is an identifier assigned to the wireless terminal in a procedure in which a connection between the wireless terminal and the network is temporarily suspended.
- the context information is used to resume the connection.
- the receiver receives identification information for identifying a connected base station to which the wireless terminal is connected when the procedure is executed from the wireless terminal. When the connected base station is not the base station but the other base station, the controller sends the predetermined information to the other base station.
- the base station may further include a transmitter that transmits information indicating that the context information is not held to the wireless terminal after receiving the resume identifier.
- the receiver may receive the identification information from the wireless terminal after transmitting the information.
- the base station includes a receiver that receives a NAS (Non-Access Stratum) message including uplink data and a resume identifier from a wireless terminal, and an identifier of the wireless terminal in a Mobility Management Entity (MME). And a controller that executes control to send a message including the uplink data to the MME.
- the resume identifier is an identifier assigned to the wireless terminal in a procedure in which a connection between the wireless terminal and the network is temporarily suspended.
- the restart identifier is associated with context information including an identifier of the wireless terminal in the MME.
- a wireless terminal includes a transmitter that transmits a NAS (Non-Access Stratum) message including uplink data to a base station.
- NAS PDU NAS Protocol Data Unit
- the transmitter transmits a restart identifier together with the NAS message to the base station.
- the resume identifier is an identifier assigned to the wireless terminal in a procedure in which a connection between the wireless terminal and the network is temporarily suspended.
- the resume identifier is associated with context information including the identifier of the wireless terminal in MME (Mobility Management Entity).
- FIG. 1 is a diagram illustrating a configuration of an LTE system.
- the LTE system includes a UE (User Equipment) 100, an E-UTRAN (Evolved Universal Terrestrial Radio Access Network) 10, and an EPC (Evolved Packet Core) 20.
- UE User Equipment
- E-UTRAN Evolved Universal Terrestrial Radio Access Network
- EPC Evolved Packet Core
- the UE 100 corresponds to a wireless terminal.
- the UE 100 is a mobile communication device.
- UE100 performs radio
- the configuration of the UE 100 will be described later.
- the E-UTRAN 10 corresponds to a radio access network.
- the E-UTRAN 10 includes an eNB 200 (evolved Node-B).
- the eNB 200 corresponds to a base station.
- the eNB 200 is connected to each other via the X2 interface. The configuration of the eNB 200 will be described later.
- ENB 200 manages one or a plurality of cells.
- eNB200 performs radio
- the eNB 200 has a radio resource management (RRM) function, a routing function of user data (hereinafter also referred to as “data”), a measurement control function for mobility control / scheduling, and the like.
- RRM radio resource management
- Cell is used as a term indicating a minimum unit of a wireless communication area. “Cell” may also be used as a term indicating a function of performing wireless communication with the UE 100.
- the EPC 20 corresponds to a core network.
- the EPC 20 may form a network together with the E-UTRAN 10.
- the EPC 20 includes an MME (Mobility Management Entity) 300, an SGW (Serving Gateway) 400, and a PGW (Packet Data Network Gateway) 500.
- MME Mobility Management Entity
- SGW Serving Gateway
- PGW Packet Data Network Gateway
- the MME 300 performs various mobility controls for the UE 100, for example.
- the SGW 400 performs data transfer control.
- MME300 and SGW400 are connected with eNB200 via a S1 interface.
- the PGW 500 performs control to relay user data from an external network (and to the external network).
- 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.
- the physical layer performs encoding / decoding, modulation / demodulation, antenna mapping / demapping, and resource mapping / demapping.
- Data and control signals are transmitted between the physical layer of the UE 100 and the physical layer of the eNB 200 via a physical channel.
- the MAC layer performs data priority control, retransmission processing by hybrid ARQ (HARQ), random access procedure, and the like. Data and control signals are transmitted between the MAC layer of the UE 100 and the MAC layer of the eNB 200 via a transport channel.
- the MAC layer of the eNB 200 includes a scheduler (MAC scheduler). The scheduler determines the uplink / downlink transport format (transport block size, modulation / coding scheme (MCS)) and the resource blocks allocated to the UE 100.
- MCS modulation / coding scheme
- 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 and control signals are transmitted between the RLC layer of the UE 100 and the RLC layer of the eNB 200 via a logical channel.
- the PDCP layer performs header compression / decompression and encryption / decryption.
- the RRC layer is defined only in the control plane that handles control signals. Messages for various settings (RRC messages) are transmitted between the RRC layer of the UE 100 and the RRC layer of the eNB 200.
- 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.
- RRC Radio Resource Control
- a NAS (Non-Access Stratum) layer located above the RRC layer performs, for example, session management and mobility management.
- FIG. 3 is a configuration diagram of a radio frame used in the LTE system.
- OFDMA Orthogonal Frequency Division Multiple Access
- SC-FDMA Single Carrier Frequency Division Multiple Access
- the radio frame is composed of 10 subframes arranged in the time direction.
- Each subframe is composed of two slots arranged in the time direction.
- the length of each subframe is 1 ms.
- the length of each slot is 0.5 ms.
- Each subframe includes a plurality of resource blocks (RB: Resource Block) in the frequency direction.
- Each subframe includes a plurality of symbols in the time direction.
- Each resource block includes a plurality of subcarriers in the frequency direction.
- One resource element (RE) is configured by one symbol and one subcarrier.
- a radio resource (time / frequency resource) is allocated to the UE 100.
- radio resources frequency resources
- radio resources are configured by resource blocks.
- radio resources (time resources) are configured by subframes (or slots).
- the section of the first several symbols of each subframe is an area that can be used as a physical downlink control channel (PDCCH: Physical Downlink. Control Channel) for transmitting a downlink control signal.
- the remaining part of each subframe is an area that can be used as a physical downlink shared channel (PDSCH) for transmitting downlink data.
- PDCH Physical Downlink control channel
- PDSCH physical downlink shared channel
- both ends in the frequency direction in each subframe are areas that can be used as physical uplink control channels (PUCCH: Physical Uplink Control Channels) for transmitting uplink control signals.
- PUCCH Physical Uplink Control Channels
- the remaining part of each subframe is an area that can be used as a physical uplink shared channel (PUSCH) for transmitting uplink data.
- PUSCH physical uplink shared channel
- FIG. 4 is a block diagram of the UE 100. As illustrated in FIG. 4, 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 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).
- the receiver 110 outputs a baseband signal 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.
- the transmitter 130 transmits a radio signal from the antenna.
- the controller 130 performs various controls in the UE 100.
- 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, for example, modulation / demodulation and encoding / decoding of a baseband signal.
- the CPU performs various processes by executing programs stored in the memory.
- the processor may include a codec that performs encoding / decoding of an audio / video signal.
- the processor executes various processes described later and various communication protocols described above.
- the UE 100 may include a GNSS receiver.
- the GNSS receiver can receive a GNSS signal in order to obtain location information indicating the geographical location of the UE 100.
- the GNSS receiver outputs a GNSS signal to the controller 130.
- UE100 may have a GPS function for acquiring position information of UE100.
- 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 of the eNB 200. As illustrated in FIG. 5, 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 transmitter 210 and the receiver 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).
- the receiver 210 outputs a baseband signal 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.
- the transmitter 220 transmits a radio signal from the antenna.
- the controller 230 performs various controls in the eNB 200.
- 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, for example, modulation / demodulation and encoding / decoding of a baseband signal.
- the CPU performs various processes by executing programs stored in the memory.
- the processor 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 300 and the SGW 400 via the S1 interface.
- the network interface 240 is used for communication performed on the X2 interface and communication performed on the S1 interface, for example.
- a process executed by at least one of the transmitter 210, the receiver 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.
- ECM state An ECM (EPS Connection Management) state will be described.
- the ECM state represents signaling connectivity between the UE 100 and the EPC 20.
- the ECM state includes an ECM idle state (ECM-IDLE state) and an ECM connection state (ECM-CONNECTED state).
- NAS signaling connection consists of S1 MME connection and S1 U connection.
- the S1 MME connection is a connection between the eNB 200 and the MME 300 in a C (Control) plane for transmitting a control signal.
- the S1 U connection is a connection between the eNB 200 and the SGW 400 in the U (User) plane for transmitting user data.
- the S1 MME connection and the S1 U connection constitute an S1 connection.
- the UE context of the UE 100 (a context other than the context for managing the mobility (eg, tracking area (TA)) of the UE 100 does not exist in the E-UTRAN 10. However, when a temporary restart procedure described later is executed, the UE context of the UE 100 may exist in the E-UTRAN 10 in the ECM idle state.
- TA tracking area
- the ECM connection state there is a NAS signaling connection between the UE 100 and the network.
- the ECM connection state the UE context of the UE 100 exists in the E-UTRAN 10.
- the position of the UE 100 is known to the MME 300 with the accuracy of the identifier of the SGW 400.
- UE 100 and MME 300 switch the ECM state between an ECM idle state and an ECM connected state (ECM connected state).
- ECM connected state an ECM connected state
- the UE 100 and the MME 300 enter the ECM connection state from the ECM idle state when the signaling connection between the UE 100 and the MME 300 is established.
- the UE 100 enters the ECM connection state from the ECM idle state by establishing the RRC connection.
- the MME 300 enters the ECM connection state from the ECM idle state by establishing the S1 connection between the eNB 200 and the SGW 400.
- the S1 connection is composed of an S1 MME connection and an S1 U connection.
- the UE 100 and the MME 300 enter the ECM idle state from the ECM connection state when the signaling connection between the UE 100 and the MME 300 is released or when the signaling connection breaks.
- the UE 100 enters the ECM idle state from the ECM connection state by releasing the RRC connection.
- the UE 100 may explicitly indicate from the eNB 200 the release or break (failure) of the signaling connection.
- the UE 100 may detect the release or break (failure) of the signaling connection.
- the MME 300 enters the ECM idle state from the ECM connection state by releasing the S1 connection.
- FIG. 6 is a sequence diagram for explaining the outline of the temporary suspension procedure.
- the temporary suspension procedure is a procedure for temporarily suspending the connection between the UE 100 and the network.
- the UE 100 In the initial state of FIG. 6, the UE 100 has established an RRC connection with the eNB 200. Therefore, the UE 100 is in the RRC connection state. The UE 100 is in an ECM connection state.
- step S ⁇ b> 110 the eNB 200 starts a temporary suspension procedure for the MME 300. Specifically, the eNB 200 sends a UE Deactivate Context (UE Deactivate Context) message to the MME 300.
- the UE deactivate context message is a message for indicating to the MME 300 that the RRC connection of the UE 100 should be suspended when the MME 300 enters the ECM idle state.
- the context information includes, for example, at least one of data related to the S1 AP association, UE context and bearer context, information indispensable for resuming the connection, and security information (for example, integrity algorithm).
- the context information is deactivated.
- step S120 the MME 300 sends a release access bearer request (Release Access Bearers Request) message to the SGW 400.
- the release access bearer request message is a message for requesting release of all S1 U bearers for the UE 100.
- S1 U bearer corresponds to S1 U connection.
- the MME 300 enters the ECM idle state from the ECM connection state.
- SGW 400 releases the S1 U bearer (S1 U connection).
- the SGW 400 releases all eNB related information regarding the UE 100.
- SGW300 may hold other information of UE100.
- the SGW 400 responds to the MME 300 with a release access bearer response (Release Access Bearers Response) message.
- the release access bearer response message is a message for informing the MME 300 about the release of the S1 U bearer.
- step S140 the MME 300 sends a release access bearer acknowledgment (UE Deactivate Context ACK) message to the eNB 200.
- UE Deactivate Context ACK release access bearer acknowledgment
- step S150 the RRC connection is temporarily suspended between the UE 100 and the eNB 200.
- the eNB 200 transmits a message indicating that the RRC connection is temporarily suspended to the UE 100.
- the UE 100 enters the ECM idle state from the ECM connection state.
- Step S150 is an RRC connection temporary interruption procedure.
- the RRC connection suspension procedure is a part of the connection suspension procedure.
- the outline of the resume procedure (Resume Connection procedure) will be described with reference to FIG.
- FIG. 7 is a sequence diagram for explaining the outline of the restart procedure.
- the restart procedure is a procedure for restarting the connection between the UE 100 and the network.
- the connection between the UE 100 and the network is temporarily suspended by the temporary suspension procedure. Therefore, the RRC connection is interrupted.
- the UE 100 is in an ECM idle state.
- step S210 the UE 100 and the eNB 200 execute a procedure (RRC Connection Resume) for resuming the RRC connection.
- the UE 100 triggers an RRC restart procedure (RRC Connection Resume) to restart the RRC connection.
- RRC Connection Resume an RRC restart procedure
- the UE 100 transmits an RRC connection resumption request to the eNB 200.
- the RRC connection restart procedure is a part of the restart procedure.
- step S220 the eNB 200 and the MME 300 execute an activate context procedure.
- the activate context procedure the eNB 200 notifies the MME 300 that the RRC connection of the UE is resumed.
- the MME 300 enters the ECM connection state.
- the MME 300 activates the context information of the UE 100.
- step S230 the UE 100 transmits uplink data to the eNB 200.
- the eNB 200 sends the uplink data to the SGW 400.
- the SGW 400 transfers the uplink data to the PGW 500.
- step S240 the MME 300 sends a change bearer request (Modify Bearer Request) message to the SGW 400 for each PDN (Packet Data Network) connection.
- PDN Packet Data Network
- step S250 the SGW 400 sends a change bearer response (Modify Bearer Response) message to the MME 300.
- a change bearer response Modify Bearer Response
- FIG. 8 is a sequence diagram for explaining the operation according to the first embodiment.
- steps S301 to S304 correspond to a temporary interruption procedure. Specifically, steps S301 to S303 correspond to steps S110, S120, and S150.
- step S303 the eNB 200-1 assigns a resume identifier (Resume ID) to the UE 100.
- the resume identifier is an identifier assigned to the UE 100 in the temporary suspension procedure.
- the resume identifier is associated with the context information of the UE 100 held in the eNB 200-1.
- the context information may include information such as an RRC context or an S1AP context, for example.
- the length of the resume identifier may be variable.
- the eNB 200-1 may change the length of the resume identifier according to the number of UEs in the own cell.
- the eNB 200-1 may change the length of the resume identifier according to a specific setting.
- the variable length identifier is an identifier whose length can be changed.
- the variable length identifier may be an identifier indicating predetermined information (for example, identification information and C-RNTI).
- the additional identifier may have a length corresponding to the variable length identifier.
- the restart identifier may include information for identifying the length of the restart identifier. For example, it is as follows.
- (A) Resume identifier length identifier + variable length identifier
- the length identifier indicates the length of the variable length identifier (or the resume identifier). The case where the length identifier is 3 bits is shown as an example. When the length identifier indicates “001”, the variable length identifier (resumption identifier) is 5 bits (8 bits). When the length identifier indicates “010”, the variable length identifier (resumption identifier) is 13 bits (16 bits). When the length identifier indicates “011”, the variable length identifier (resumption identifier) is 21 bits (24 bits). When the length identifier indicates “100”, the variable length identifier (resumption identifier) is 29 bits (32 bits).
- (B) Resume identifier header + variable length identifier
- the header indicates the length of the variable length identifier. For example, when the header indicates “1”, the variable length identifier is 1 byte. When the header indicates “2”, the variable length identifier is 2 bytes. When the header indicates “3”, the variable length identifier is 3 bytes.
- the Mth identifier is a fixed value (for example, 7 bits).
- the Mth length identifier indicates whether the identifier follows. For example, when the Mth length identifier indicates “1”, the identifier exists later. In this case, an identifier of at least 8 bits ((M + 1) identifier (7 bits) + (M + 1) length identifier (1 bit)) exists after the M length identifier. When the Mth length identifier indicates “0”, there is no identifier later.
- the restart identifier is “first identifier (7 bits) + first length identifier (1 bit: 1) + second identifier (7 bits) + second length Identifier (1 bit: 0) ".
- the resume identifier may be configured by a continuous identifier set (Mth identifier + Mth length identifier).
- the eNB 200 can grasp the length of the resume identifier from the information for identifying the length of the resume identifier. Therefore, even when the eNB 200 receives a plurality of resume identifiers having different lengths by changing the length of the resume identifier, the eNB 200 can accurately grasp each resume identifier without being confused. The eNB 200 can accurately grasp the resume identifier even if it is a resume identifier assigned by another eNB 200.
- At least a part of the resume identifier may be identification information for identifying the eNB 200-1 to which the UE 100 was connected when the temporary suspension procedure is executed. Therefore, the restart identifier may include identification information.
- the identification information is, for example, a cell identifier for identifying a cell to which the UE 100 is connected when the temporary suspension procedure is executed.
- the cell identifier is, for example, PCI (Physical-layer Cell Identity) or ECGI (E-UTRAN Cell Global ID).
- the ECGI includes an identifier of a PLMN (Public Land Mobile Network) to which the cell belongs and a CI (Cell Indentity).
- the identification information may include information on an eNB identifier for identifying the eNB 200-1 to which the UE 100 is connected when the temporary suspension procedure is executed.
- the eNB identifier is, for example, an eNB ID or a global eNB identifier.
- the global eNB identifier is configured by the PLMN to which the eNB 200-1 belongs and the eNB ID.
- At least a part of the resume identifier may be C-RNTI (Cell-Radio Network Temporary Identifier).
- C-RNTI is a temporary identifier of UE 100 in a cell to which UE 100 is connected.
- the UE 100 temporarily suspends the RRC connection by executing the RRC connection suspending procedure.
- the UE 100 transitions to the ECM idle state.
- step S304 the UE 100 moves to a new eNB (eNB 200-2). Specifically, the UE 100 moves into a cell managed by the eNB 200-2. UE100 selects the said cell by performing cell reselection.
- eNB 200-2 a new eNB
- step S305 when resuming the RRC connection, the UE 100 transmits an RRC connection resume request (RRC Connection Resume Request) message to the eNB 200-2.
- the RRC connection resumption request message is a message for requesting resumption of the RRC connection.
- the RRC connection resumption request message includes a resumption identifier. Therefore, the UE 100 transmits a resume identifier to the eNB 200-2.
- the UE 100 may include the above-described identification information (such as PCI or ECGI) in the RRC connection resumption request message. Therefore, the UE 100 may transmit identification information together with the resume identifier to the eNB 200-2. The UE 100 may transmit the identification information to the eNB 200-2 when at least a part of the resume identifier is not the identification information.
- identification information such as PCI or ECGI
- the identification information may include C-RNTI and / or Short MAC-I.
- C-RNTI is C-RNTI assigned to eNB 200-1.
- Short MAC-I is the 16 least significant bits of MAC-I calculated using the security setting of the source cell (cell of eNB 200-1) and the re-established cell (cell of eNB 200-2) identifier.
- the UE 100 may transmit the identification information to the eNB 200-2 when the number of cell reselections after the temporary suspension procedure is executed is equal to or greater than a threshold value.
- UE100 may abbreviate
- the threshold is a value of 1 or more.
- the UE 100 can transmit identification information when there is a high possibility of requesting resumption of connection to another eNB (eNB 200-2) different from the eNB 200-1 to which the resumption identifier is assigned.
- the eNB 200-2 can identify the eNB 200-1 to which the resume identifier is assigned, that is, the eNB 200-1 that holds the context information of the UE 100, based on the identification information.
- the UE 100 may include the identification information in the RRC connection restart request message only when the cell (or eNB) when the temporary suspension procedure is executed and the transmission destination of the RRC connection restart request message are different. That is, the UE 100 may transmit the identification information to the eNB 200-2 when the temporary suspension procedure is not executed in the cell of the eNB 200-2. For example, the UE 100 stores a cell identifier (or eNB identifier) when the temporary suspension procedure is executed. The UE 100 includes the identification information in the RRC connection resumption request message only when the stored cell identifier (or eNB identifier) does not match the identifier of the cell selected by cell reselection (or the eNB identifier that manages the selected cell). May be.
- the UE 100 may transmit information necessary for (re-) establishing the RRC connection to the eNB 200-2 together with the resume identifier.
- Necessary information is information included in the RRC (re) connection request message.
- necessary information is PCI, C-RNTI, and Short MAC-I.
- the eNB 200-2 receives the RRC connection resumption request message from the UE 100.
- the eNB 200-2 receives the resume identifier (and identification information).
- the eNB 200-2 determines whether to hold the context information of the UE 100 based on the restart identifier (and / or identification information). For example, the eNB 200-2 may determine that the context information of the UE 100 is not held when the resume identifier received from the UE 100 is not the resume identifier assigned by the eNB 200-2. The eNB 200-2 determines that the context information of the UE 100 is held when the resume identifier received from the UE 100 is the resume identifier assigned by itself. The eNB 200-2 may determine that the context information is not held when the identification information is received together with the resume identifier from the UE 100. The eNB 200-2 may determine that the context information is held when the identification information is not received from the UE 100. The eNB 200-2 may determine whether or not to retain the context information of the UE 100 through the process of step S306.
- the eNB 200-2 identifies the eNB 200-1 that has assigned the resume identifier to the UE 100, that is, the eNB 200-1 that holds the UE 100 context information, based on the resume identifier and / or identification information.
- the eNB 200-1 is an eNB that manages a cell to which the UE 100 is connected when the resumption identifier is assigned to the UE 100.
- the eNB 200-2 may indirectly identify the eNB 200-1 based on a list of cells managed by the neighboring eNB.
- the eNB 200-2 determines that the eNB 200-2 holds the context information.
- the eNB 200-2 executes a restart procedure. That is, the eNB 200-2 resumes the RRC connection based on the context information of the UE 100.
- the eNB 200-2 executes the process of step S307.
- the eNB 200-2 identifies the eNB 200-1 based on the restart identifier and / or identification information.
- the eNB 200-2 performs the process of step S307 on the identified eNB 200-1.
- step S307 the eNB 200-2 sends a context fetch request (Context Fetch Request) message to the eNB 200-1.
- the eNB 200-1 receives the context fetch request message from the eNB 200-2.
- the context fetch request message is a message (information) for receiving context information of the UE 100.
- the context fetch request message may include a resume identifier.
- the context fetch request message may include identification information.
- step S308 the eNB 200-1 identifies the context information of the UE 100 based on the resume identifier (and identification information).
- step S309 the eNB 200-1 sends a context fetch response (Context Fetch Response) message to the eNB 200-2.
- the eNB 200-2 receives the context fetch response message from the eNB 200-1.
- the context fetch response message includes the UE 100 context information.
- the context fetch response message may include a resume identifier.
- the context fetch response message may include identification information.
- the eNB 200-2 resumes the RRC connection based on the UE 100 context information.
- step S310 the eNB 200-2 transmits an RRC connection resume complete (RRC Connection Resume Complete) message to the UE 100.
- the UE 100 receives the RRC connection resume completion message from the eNB 200-2.
- the UE 100 enters the RRC connection state.
- the UE 100 enters the ECM connection state.
- the RRC connection resume completion message may include a resume identifier.
- step S311 the eNB 200-2 and the MME 300 execute a UE context activation procedure.
- Step S311 corresponds to step S220.
- the MME 300 enters the ECM connection state.
- the eNB 200-2 may send a message including information indicating that the eNB 200 managing the UE 100 is changed and a resume identifier to the MME 300.
- the message may be a path switch request message.
- the MME 300 can execute control for switching the S1 U connection from the eNB 200-1 to the eNB 200-2 based on the path switch request message.
- FIG. 9 is a sequence diagram for explaining the first modification according to the first embodiment. The same description as above is omitted.
- the UE 100 transmits identification information to the eNB 200 when the eNB 200 receives information indicating that the eNB 200 does not hold the context information of the UE 100 from the eNB 200.
- steps S401 to S404 correspond to steps S301 to S304.
- step S405 the UE 100 transmits an RRC connection resumption request message to the eNB 200-2.
- the RRC connection resumption request message includes a resumption identifier.
- the RRC connection resumption request message does not include identification information.
- step S406 the eNB 200-2 determines whether or not the context information of the UE 100 is held based on the resume identifier. If the eNB 200-2 determines that the context information of the UE 100 is not held based on the resume identifier, that is, if the context information of the UE 100 cannot be identified, the eNB 200-2 performs the process of step S407.
- the eNB 200-2 resumes the RRC connection when it holds the context information of the UE 100. Then, the process of step S310 and S311 is performed.
- the eNB 200-2 may determine whether to resume the RRC connection. When the eNB 200-2 holds the context information of the UE 100, the eNB 200-2 determines to resume the RRC connection. When the eNB 200-2 does not hold the context information of the UE 100, the eNB 200-2 determines that the RRC connection is not resumed (resume failure).
- step S407 the eNB 200-2 transmits an RRC connection resumption failure (RRC Connection Resume Failure) message to the UE 100.
- the UE 100 receives an RRC connection restart failure message from the eNB 200-2.
- the RRC connection restart failure message may include information indicating that the eNB 200 does not hold the context information of the UE 100.
- the information may be reason information that the context information of the UE 100 could not be identified.
- the RRC connection restart failure message may indicate that the eNB 200 does not hold the context information of the UE 100.
- step S408 the UE 100 transmits an RRC connection re-establishment request (RRC Connection Reestablishment Request) message to the eNB 200-2 in response to reception of the information.
- the eNB 200-2 receives the RRC connection re-establishment request message from the UE 100.
- the UE 100 may transmit an RRC connection re-establishment request message to the eNB 200-2 even when the T310 timer has not expired.
- the UE 100 can start the RRC connection re-establishment procedure when the T310 timer expires.
- the UE 100 may transmit an RRC connection re-establishment request message to the eNB 200-2 even in the ECM idle state.
- the RRC connection re-establishment request message includes identification information.
- the RRC connection re-establishment request message includes PCI, C-RNTI, and Short MAC-I.
- Steps S409 to S412 correspond to steps S306 to S309.
- step S413 the eNB 200-2 transmits an RRC connection re-establishment (RRC Connection Reestablishment) message to the UE 100.
- the UE 100 receives the RRC connection re-establishment message from the eNB 200-2.
- the RRC connection re-establishment message may include a resume identifier.
- step S414 the UE 100 transmits an RRC connection re-establishment completion (RRC Connection Reestablishment Complete) message to the eNB 200-2.
- the eNB 200-2 receives the RRC connection re-establishment completion message from the UE 100.
- RRC connection is established between the UE 100 and the eNB 200-2.
- UE100 transfers to a RRC connection state.
- UE100 transfers to an ECM connection state.
- Step S415 corresponds to step S311.
- FIG. 10 is a sequence diagram for explaining the second modification according to the first embodiment. The same description as above is omitted.
- the eNB 200-2 receives the context information of the UE 100 from the eNB 200-1 by a method different from that of the first embodiment.
- the UE 100 in the initial state, is in the cell (source cell) of the eNB 200-1 (Source eNB).
- the UE 100 receives packet data from the SGW 400 via the eNB 200-1.
- the UE 100 transmits packet data to the SGW 400 via the eNB 200-1.
- step S501 the UE 100 executes an RRC temporary suspension procedure.
- the UE 100 includes a re-establishment identifier.
- step S502 the UE 100 detects a radio link failure (RLF).
- the UE 100 may transition (voluntarily) to the RRC idle state without detecting the RLF.
- step S503 the UE 100 performs cell reselection.
- UE100 selects a target cell.
- the target cell is a cell managed by the eNB 200-2.
- the UE 100 transmits an RRC connection re-establishment message to the eNB 200-2.
- the RRC connection re-establishment message includes a re-establishment identifier.
- the RRC connection re-establishment message includes PCI, C-RNTI, and Short MAC-I.
- the UE 100 may use an RRC connection establishment (RRC Connection Establishment Request) message instead of the RRC connection re-establishment message.
- the UE 100 that has shifted to the RRC idle state in step S502 may transmit an RRC connection re-establishment message to the eNB 200-2 when desiring to start data communication. Therefore, the UE 100 may start the process of step S504 with the generation of data as a trigger.
- step S505 the eNB 200-2 determines whether or not to execute context fetch.
- the eNB 200-2 determines to perform the context fetch when the RRC connection re-establishment message includes the re-establishment identifier. In this case, the eNB 200-2 executes the process of step S506.
- the eNB 200-2 determines that the context fetch is not executed when the context information of the UE 100 is retained. In this case, the eNB 200-2 starts establishing an RRC connection with the UE 100 based on the context information.
- the eNB 200-2 sends an RLF indication to the eNB 200-1.
- the RLF indication is an indication indicating that RLF has occurred.
- the RLF indication includes PCI (or ECGI), C-RNTI, and Short MAC-I to identify the UE 100 context information.
- the RLF indication includes an ECGI for identifying the target cell.
- the RLF indication may include a resume identifier.
- the RLF indication may include failure information indicating that connection resumption has failed.
- the RRC Conn Reestab Indicator IE included in the RLF indication may include a value indicating a resumption failure (ENUMRATED: Resume Failure).
- the RLF indication may include a new IE (RRC Resume indicator).
- the new IE includes information (Resume Failure) indicating a connection resumption failure.
- the eNB 200-2 may send a new X2 message to the eNB 200-1 instead of the RLF indication when the RLF has not occurred, that is, when the UE 100 spontaneously shifts to the RRC idle state.
- the new X2 message can contain the same information as the RLF indication described above.
- step S507 the eNB 200-1 determines whether or not to execute the context fetch in response to reception of the RLF indication (resumption identifier).
- the eNB 200-1 determines to execute the context fetch. In this case, the eNB 200-1 executes the process of step S508.
- the eNB 200-1 determines not to execute the context fetch. In this case, the eNB 200-1 may end the process.
- the eNB 200-1 sends a handover request to the eNB 200-2.
- the handover request includes context information of the UE 100.
- the handover request may include a resume identifier.
- the context information of the UE 100 is included in a container (Source eNB to target eNB Container IE).
- step S509 the eNB 200-2 executes admission control.
- step S510 the eNB 200-2 sends a response (HANDOVER REQUEST ACK) to the handover request to the eNB 200-1.
- Steps S511 and S512 correspond to steps S413 and S414.
- step S513 the eNB 200-1 determines to transfer the data of the UE 100 to the eNB 200-2.
- step S514 the eNB 200-1 sends an SN state transfer (SN STATUS TRANSFER) message for transmitting the sequence number of the data received from the UE 100 (PDCP SN) and the sequence number of the data transmitted to the UE 100 (PDCP SN) to the eNB 200- Send to 2.
- SN STATUS TRANSFER SN state transfer
- step S515 the eNB 200-1 transfers the data to the eNB 200-2.
- step S5166 the eNB 200-2 stores the data (packet) transferred from the eNB 200-1.
- step S517 the eNB 200-2 transmits an RRC connection reconfiguration (RRC Connection Reconfiguration) message to the UE 100.
- RRC connection reconfiguration RRC Connection Reconfiguration
- step S5128 the UE 100 transmits an RRC connection reconfiguration complete (RRC Connection Reconfiguration Complete) message to the eNB 200-2.
- RRC connection reconfiguration complete RRC Connection Reconfiguration Complete
- step S519 packet data is transmitted (and / or received) between the UE 100 and the eNB 200-2.
- the eNB 200-2 sends packet data to the SGW 400.
- the eNB 200-2 transmits a path switch request (PATH SWITCH REQUEST) message for notifying that the UE 100 has changed the cell to the MME 300.
- the path switch request message includes the identifier of the UE 100 in the MME 300 (MME UE S1 AP ID) and the identifier of the UE 100 in the eNB 200-2 (eNB UE S1 AP ID).
- the path switch request message may be the MME UE S1 AP ID and the UE 100 identifier (eNB UE S1 AP ID) in the eNB 200-1.
- the identifier of the UE 100 in the eNB 200-1 may be included in the context information of the UE 100.
- the MME 300 restarts the connection based on these identifiers. Specifically, the MME 300 switches the S1 MME connection for the UE 100 based on these identifiers. That is, the MME 300 switches the connection destination of the S1 MME connection from the eNB 200-1 to the eNB 200-2.
- step S521 the MME 300 sends a change bearer request message to the SGW 400.
- step S522 the SGW 400 switches the downlink data path. That is, the SGW 400 switches the connection destination of the S1 U connection (S1 U bearer) from the eNB 200-1 to the eNB 200-2 so that the downlink data path passes through the eNB 200-2.
- S1 U connection S1 U bearer
- step S523 the SGW 400 sends an end marker packet to the eNB 200-1.
- the eNB 200-1 sends an end marker packet to the eNB 200-2.
- step S524 the SGW 400 and the eNB 200-2 transmit and / or receive the data packet of the UE 100.
- step S525 the SGW 400 sends a change bearer response (Modify Bearer Response) to the MME 300.
- a change bearer response Modify Bearer Response
- step S526 the MME 300 sends an affirmative response (PATH SWITCH REQUEST ACK) to the path switch request to the eNB 200-2.
- PATH SWITCH REQUEST ACK an affirmative response
- step S527 the eNB 200-2 sends a UE context release message to the eNB 200-1.
- FIG. 11 is a flowchart for explaining the third modification example according to the first embodiment. The same description as above is omitted.
- the UE 100 determines whether to request connection resumption based on the condition.
- the operating environment is the same as in the first embodiment.
- the UE 100 In the initial state, the UE 100 has the RRC connection temporarily suspended by the RRC temporary suspension procedure. The UE 100 is in an ECM idle state.
- step S610 when the UE 100 desires to resume RRC connection or (re) establish RRC connection, the UE 100 executes the process of step S610.
- step S610 the UE 100 determines whether or not to hold a resume identifier.
- the UE 100 executes the process of step S620.
- UE100 performs the process of step S640, when not hold
- step S620 the UE 100 determines whether or not the condition for executing the RRC restart procedure is satisfied. If the condition is satisfied, the UE 100 executes the process of step S630. UE100 performs the process of step S640, when not satisfy
- Requirement is at least one of the following conditions.
- UE100 may perform the process of step S630, when several conditions are satisfy
- the first condition is that the number of cell reselections after the temporary suspension procedure is executed is less than a threshold value.
- UE100 performs the process of step S630, when the frequency
- UE100 performs the process of step S640, when the frequency
- the threshold is a value of 1 or more.
- the second condition is that the UE 100 is located in an area where connection can be resumed.
- UE100 performs the process of step S630, when UE100 is located in the area
- UE100 performs the process of step S640, when UE100 is not located in the area
- the UE 100 may determine whether or not the UE 100 is in an area where the connection can be resumed (resume area) based on the resume identifier.
- the resume identifier may be area information indicating a resume area.
- the area information indicates a tracking area, for example.
- the header of the resume identifier may be area information.
- the UE 100 determines that the UE 100 is located in the resume area when the tracking area where the UE 100 is located and the area information match.
- the third condition is a condition that the eNB 200 that establishes the RRC connection is included in an eNB group (eNB cluster) that supports the transfer of the context information of the UE 100.
- UE100 performs the process of step S630, when eNB200 which manages the selected cell is contained in the said eNB group by execution of cell reselection.
- UE100 performs the process of step S640, when eNB200 is not contained in an eNB group.
- UE100 may determine whether eNB200 is included in an eNB group based on cluster information, for example.
- Cluster information is information for identifying an eNB group that supports transfer of context information of the UE 100.
- the context information of the UE 100 can be transferred between eNBs (for example, neighboring eNBs) belonging to the same eNB group.
- An X2 interface may be established between eNBs included in the same eNB group.
- the cluster information may include information for identifying cells such as PLMN and PCI, for example.
- the UE 100 can determine whether or not the eNB 200 (cell) is included in the eNB group by receiving a system information block (for example, SIB1: System Information Block 1) including information for identifying the cell.
- SIB1 System Information Block 1
- the cluster information may include other information (for example, the identification information described above).
- the UE 100 may receive the cluster information from the MME 300 by the NAS message when the context information of the UE 100 is generated by an attach procedure or the like, for example.
- the UE 100 may receive the cluster information when the temporary suspension procedure is executed.
- step S630 the UE 100 executes an RRC restart procedure. That is, the UE 100 transmits a resume identifier to the eNB 200.
- step S640 the UE 100 executes an RRC (re) connection procedure. That is, the UE 100 does not transmit the resume identifier to the eNB 200.
- the UE 100 transmits a resume identifier to the eNB 200.
- UE100 abbreviate
- UE100 can transmit a resumption identifier, when possibility of requesting resumption of a connection is high with respect to eNB200 (eNB200 holding context information) which allocated a resumption identifier.
- the UE 100 makes an existing RRC (re) connection request when there is a high possibility of requesting resumption of connection to another eNB 200 (eNB 200 that does not hold context information) to which no resumption identifier is assigned. Therefore, since the failure of the RRC restart procedure can be reduced, signaling can be reduced.
- the UE 100 When the UE 100 is located in an area where the connection can be resumed, the UE 100 transmits a resume identifier to the eNB 200. When the UE 100 is not located in the area where the connection can be resumed, the UE 100 omits the transmission of the resume identifier. Thereby, UE100 can abbreviate
- UE100 transmits a restart identifier, when eNB200 of a connection destination is contained in an eNB group.
- the connection destination eNB 200 is not included in the eNB group, the UE 100 omits transmission of the resume identifier.
- UE100 can abbreviate
- FIG. 12 is a sequence diagram for explaining the second embodiment.
- uplink data is sent from the UE 100 to the MME 300 by the NAS message in a state where the S1 U bearer is not established.
- uplink data (and downlink data) can be carried between the UE 100 and the MME 300.
- signaling related to an initial context setup procedure for E-RAB setting and signaling related to an RRC security mode command can be reduced.
- uplink data is sent from the eNB 200 to the MME 300 by an initial UE message (Initial UE Message).
- a downlink S1AP message (Downlink S1-AP msg.) Including downlink data is sent from the MME 300 to the eNB 200.
- the downlink S1AP message includes the identifier (MME UE S1AP ID) of the UE 100 in the MME 300.
- the uplink data is transmitted from the eNB 200 to the MME 300 by the NAS UL transport message.
- the NAS UL transport message needs to include the identifier (MME UE S1AP ID) of the UE 100 in the MME 300.
- the eNB 200 can include the MME UE S1AP ID notified from the MME 300 in the NAS UL transport message.
- the downlink S1AP message is not sent from the MME 300 to the eNB 200. Therefore, the eNB 200 may not be able to include the identifier of the UE 100 in the MME in the NAS UL transport message. Since it is essential that the NAS UL transport message includes the identifier of the UE 100 in the MME 300, the eNB 200 may not be able to send uplink data to the MME 300 by the NAS UL transport message.
- the UE 100 in the initial state, the UE 100 is in the RRC idle state.
- the UE 100 is in an ECM idle state.
- step S701 the UE 100 and the eNB 200-2 establish an RRC connection in order to send uplink data from the UE 100 to the eNB 200.
- UE100 transmits the NAS message containing uplink data to eNB200.
- the NAS message may include release assistance information (Release Assistance Information).
- the release assistance information is, for example, information indicating whether or not downlink data (ACK or response) is expected for uplink data.
- the release assistance information may be information indicating whether or not the S1 connection is released after downlink data transmission.
- step S702 the eNB 200 sends an initial UE message to the MME 300.
- the initial UE message includes uplink data included in the NAS message.
- Steps S703 to S705 correspond to steps S301 to S303.
- the eNB 200 assigns to the UE 100 a resume identifier associated with the context information of the UE 100 in the temporary suspension procedure.
- step S706 when uplink data exists, the UE 100 determines whether or not to execute the process of step S707. That is, the UE 100 determines whether or not to send uplink data by a NAS message using the restart procedure.
- UE100 may perform the process of step S707, when NAS PDU (NAS Protocol Data Unit) including downlink data is not received from eNB200.
- the NAS PDU is sent from the eNB 200 to the UE 100 when the downlink S1AP message is sent from the MME 300 to the eNB 200. For this reason, when the eNB 200 transmits a NAS PDU including downlink data to the UE 100, the eNB 200 already knows the MME UE S1AP ID.
- NAS PDU NAS Protocol Data Unit
- UE 100 may execute the process of step S707 when the number of times uplink data is transmitted by the NAS message is two or more and when the resumption identifier is held.
- the UE 100 may trigger the RRC temporary suspension procedure when it does not hold the resume identifier. That is, since the resumption identifier is assigned from the eNB 200, the UE 100 may request the eNB 200-2 to execute the RRC temporary suspension procedure.
- step S707 the UE 100 transmits a restart request to the eNB 200.
- UE100 transmits the restart request
- the restart request includes a NAS message (NAS PDU) including uplink data and a restart identifier. Therefore, the UE 100 transmits a resume identifier to the eNB 200 together with the NAS message.
- NAS PDU NAS Protocol Data Unit
- the restart request may include release assistance information.
- step S708 the eNB 200 transmits a restart response to the UE 100.
- the eNB 200 identifies the MME UE S1AP ID based on the resume identifier. Specifically, eNB200 identifies the context information of UE100 linked
- the eNB 200 performs control to send a NAS UL transport message including the MME UE S1AP ID and uplink data to the MME 300.
- the NAS UL transport message may include an eNB UE S1AP ID that is an identifier of the UE 100 in the eNB 200.
- step S711 the eNB 200 and the MME 300 may execute the above-described UE context activation procedure.
- the eNB 200 and the MME 300 may omit the UE context activation procedure. Thereby, signaling can be further reduced.
- step S712 the UE 100 and the eNB 200 may execute the RRC connection temporary suspension procedure described above. Alternatively, the UE 100 and the eNB 200 may omit the RRC connection temporary interruption procedure. Thereby, signaling can be further reduced.
- the UE 100 transmits the resume identifier to the eNB 200 together with the NAS message including the uplink data.
- the eNB 200 receives the restart identifier from the UE 100 together with the NAS message including the uplink data.
- eNB200 identifies MME UE S1AP ID based on a restart identifier. Accordingly, the eNB 200 can acquire the MME UE S1AP ID even when the downlink S1AP message is not received from the MME 300, and thus can transmit the NAS UL transport message including the uplink data.
- messages including the resumption identifier from the UE 100 to the eNB 200-2 are other messages (for example, new messages). There may be.
- the UE 100 may include a resume identifier in a message that can be transmitted in the RRC state.
- the RRC connection resumption request message may be replaced with an RRC (re) connection establishment request message.
- the RRC (re) connection establishment request message may be replaced with an RRC connection resumption request message.
- Steps S307 to S309 in the first embodiment may be replaced with steps S506 to S510.
- the context fetch request message in step S307 may be the RLF indication (Radio Link Failure Indication) in step S506.
- the context fetch response message in step S309 may be the handover request message in step S508.
- the eNB 200-2 may send a response (HANDOVER REQUEST ACK) to the handover request to the eNB 200-1.
- the eNB 200-1 may send the context information of the UE 100 to the neighboring eNB 200 different from the eNB 200-2.
- the eNB 200-1 may send the context information of the UE 100 to the neighboring eNB 200 by a handover request message. Therefore, the eNB 200-1 may send the context information of the UE 100 to a neighboring eNB different from the transmission source of the RLF indication.
- steps S506 to S510 may be replaced with steps S307 to S309.
- the resume identifier is assigned from one eNB 200, but the present invention is not limited to this.
- the UE 100 may be assigned a resume identifier from each of the plurality of eNBs 200. For example, after executing the restart procedure, the UE 100 stores the restart identifier without deleting the restart identifier. The UE 100 newly acquires a resume identifier by executing a temporary suspension procedure in a new cell (new eNB 200). Thereby, UE100 memorize
- the MME 300 manages a plurality of pieces of context information for one UE 100.
- the MME 300 may associate information of the UE 100 included in the initial attachment (for example, GUTI: Global Unique Identity) with context information common to each eNB 200.
- GUTI Global Unique Identity
- the common context information is a context other than the S1 UE context related to the S1 connection (S1-MME connection) between the eNB 200 and the MME 300.
- the eNB 200 and / or the MME 300 may create the context information of the UE 100 again when connection resumption fails.
- the eNB 200 may notify the UE 100 and / or the MME 300 of (re) creation of context information.
- the UE 100 and / or the MME 300 may send information necessary for (re) creation of the context information to the eNB 200-2.
- the MME 300 may notify the UE 100 and / or the eNB 200-2 of (re) creation of context information.
- the UE 100 and / or the eNB 200-2 may send information necessary for (re) creation of the context information to the MME 300.
- the eNB 200 and / or the MME 300 may use the remaining connection that has been successfully resumed when resuming some of the connections (for example, RRC connection and / or S1 connection, etc.) fails. That is, the eNB 200 and / or the MME 300 may (re-) establish only some of the connections that have failed to resume. Thereby, signaling can be reduced.
- some of the connections for example, RRC connection and / or S1 connection, etc.
- the UE 100 may send a NAS message including uplink data and a resume identifier using another message different from the resume request.
- the UE 100 may send the NAS message and the resume identifier by a message (RRC setup request message) in the RRC setup procedure.
- the UE 100 may omit transmission of the resume identifier. That is, the UE 100 may transmit a message including a NAS message including uplink data to the eNB 200 without including the resume identifier.
- NAS PDU NAS Protocol Data Unit
- 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 either the UE 100 or the eNB 200 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.
- the present invention is not limited to the LTE system, and the content according to the present application may be applied to a system other than the LTE system.
- the RRC idle (RRC_IDLE) UE may attempt to resume connection with an eNB different from where the connection was interrupted. .
- the conventional eNB discards the UE context, and thus is not supported by the existing UE context transfer function.
- the eNB that supports this solution can retain the UE context even if the UE transitions to RRC idle, and the eNB that supports this solution does not retain the UE context,
- the eNB receives an RRC message from a UE, the eNB still has an opportunity to fetch (fetch) the UE context from the other eNB if the other eNB holds the UE context for the UE Means that. Therefore, both the RRC connection and RRC idle cases need to be considered to respect the UP-based solution, i.e. the original motivation to reduce signaling overhead.
- an eNB that supports this solution uses UE context transfer for RRC idle UEs (NB-IoT UEs) because the UE can retain the UE context during RRC idle transition Will be able to.
- NB-IoT UEs RRC idle UEs
- eNB1 After receiving the RRC connection re-establishment request message, eNB1 (without UE context) identifies the previous eNB (eNB2) where the UE was previously served and informs that the UE context is needed. An indication message is transmitted to eNB2.
- eNB1 needs to identify the previous eNB and indicate which UE context is required. Due to these requirements, eNB1 can use information (ie, PCI and C-RNTI) included in the RRC connection re-establishment request message.
- information ie, PCI and C-RNTI
- Step 2 After receiving the RLF indication message from eNB1, eNB2 needs to identify which UE context is requested and should be forwarded to eNB1. The eNB 2 can use the handover request message to transfer the UE context. Because of this requirement, eNB 2 can use ECGI to identify the address of the handover request message included in the RLF indication message, using C-RNTI and PCI to identify the UE context.
- eNB1 After receiving the UE context from eNB2, eNB1 needs to update the DL path using Source MME UE S1AP ID IE.
- this message is not only an existing UE context transfer function when there is no valid UE context, but also a trigger for the UE context transfer function for NB-IoT UEs after RLF, for example.
- ENB can assume.
- the information required to achieve UE context transfer for the UE ie, PCI, C-RNTI is the same as in the conventional procedure, so no additional information may be needed.
- the MME only needs the Source MME UE S1AP ID IE to switch the old path to the new path. Therefore, the eNB needs to care about which eNB UE S1AP ID (ie, eNB UE S1AP ID suspended by eNB2 or eNB UE S1AP ID newly allocated by eNB1) should be included in the path switch request. There is no need.
- eNB UE S1AP ID ie, eNB UE S1AP ID suspended by eNB2 or eNB UE S1AP ID newly allocated by eNB1
- the eNB assumes that the RRC connection re-establishment request message triggers the UE context transfer function for NB-IoT UEs that support UP-based solutions be able to. In this case, the eNB can use the existing UE context transfer function (existing X2 message) for the UE without any influence.
- the RRC resume procedure message has not yet been determined and the UE context transfer trigger has not been determined for the RRC idle UE supporting the UP-based solution. Therefore, it is not possible to know whether there is enough information such as PCI and C-RNTI for UE context transfer or not in the trigger message.
- the RRC message is used for the RRC restart procedure. Even if RAN2 decides to use a message different from the RRC re-establishment request message as the RRC resume request, this message contains sufficient information for UE context transfer, and this message is used as a trigger for UE context transfer. It is necessary to consider that it can be used.
- the influence of specifications may be expected due to different RRC messages and information different from existing information.
- the trigger for the RLF indication message ie, RRC re-establishment attempt or RLF report reception
- the trigger for the RLF indication message ie, RRC re-establishment attempt or RLF report reception
- Proposal 1 If the RRC resumption request message from the RRC idle UE is different from the existing RRC connection re-establishment request message for the RRC idle UE that supports the UP-based solution, the effect of UE context fetching should be considered.
Abstract
Description
一の実施形態に係る通信方法では、無線端末とネットワークとの間の接続が一時中断される手順において、第1の基地局から前記無線端末へ、前記無線端末のコンテキスト情報と関連付けられた再開識別子を送信する。前記再開識別子の一部は、前記第1の基地局を識別するための情報である。
(移動通信システム)
以下において、実施形態に係る移動通信システムであるLTEシステムについて説明する。図1は、LTEシステムの構成を示す図である。
実施形態に係るUE100(無線端末)について説明する。図4は、UE100のブロック図である。図4に示すように、UE100は、レシーバ(Receiver:受信部)110、トランスミッタ(Transmitter:送信部)120、及びコントローラ(Controller:制御部)130を備える。レシーバ110とトランスミッタ120とは、一体化されたトランシーバ(送受信部)であってもよい。
実施形態に係るeNB200(基地局)について説明する。図5は、eNB200のブロック図である。図5に示すように、eNB200は、レシーバ(受信部)210、トランスミッタ(送信部)220、コントローラ(制御部)230、及びネットワークインターフェイス240を備える。トランスミッタ210とレシーバ220は、一体化されたトランシーバ(送受信部)であってもよい。
ECM(EPS Connection Management)状態について説明する。ECM状態は、UE100とEPC20との間のシグナリング接続性を表す。ECM状態は、ECMアイドル状態(ECM-IDLE state)とECM接続状態(ECM-CONNECTED state)とを含む。
一時中断手順(Suspend Connection procedure)の概略について、図6を用いて説明する。図6は、一時中断手順の概略を説明するためのシーケンス図である。一時中断手順は、UE100とネットワークとの間の接続を一時中断するための手順である。
再開手順(Resume Connection procedure)の概略について図7を用いて説明する。図7は、再開手順の概略を説明するためのシーケンス図である。再開手順は、UE100とネットワークとの間の接続を再開するための手順である。
第1実施形態に係る動作について図8を用いて説明する。図8は、第1実施形態に係る動作を説明するためのシーケンス図である。
長さ識別子は、可変長識別子(又は再開識別子)の長さを示す。長さ識別子が3ビットのケースを例に示す。長さ識別子が「001」を示す場合、可変長識別子(再開識別子)は、5ビット(8ビット)である。長さ識別子が「010」を示す場合、可変長識別子(再開識別子)は、13ビット(16ビット)である。長さ識別子が「011」を示す場合、可変長識別子(再開識別子)は、21ビット(24ビット)である。長さ識別子が「100」を示す場合、可変長識別子(再開識別子)は、29ビット(32ビット)である。
ヘッダは、可変長識別子の長さを示す。例えば、ヘッダが「1」を示す場合、可変長識別子は、1バイトである。ヘッダが「2」を示す場合、可変長識別子は、2バイトである。ヘッダが「3」を示す場合、可変長識別子は、3バイトである。
第M識別子は、固定値(例えば、7ビット)である。第M長さ識別子は、後に識別子が続くか否かを示す。例えば、第M長さ識別子が「1」を示す場合、後に識別子が存在する。この場合、第M長さ識別子の後に少なくとも8ビットの識別子(第(M+1)識別子(7ビット)+第(M+1)長さ識別子(1ビット))が存在する。第M長さ識別子が「0」を示す場合、後に識別子が存在しない。例えば、第2長さ識別子が0を示す場合、再開識別子は、「第1識別子(7ビット)+第1長さ識別子(1ビット:1)+第2識別子(7ビット)+第2長さ識別子(1ビット:0)」である。このように、再開識別子は、連続する識別子セット(第M識別子+第M長さ識別子)によって構成されてもよい。
第1実施形態に係る変更例1について図9を用いて説明する。図9は、第1実施形態に係る変更例1を説明するためのシーケンス図である。上述と同じ説明は、省略する。
第1実施形態に係る変更例2について図10を用いて説明する。図10は、第1実施形態に係る変更例2を説明するためのシーケンス図である。上述と同じ説明は、省略する。
第1実施形態に係る変更例3について図11を用いて説明する。図11は、第1実施形態に係る変更例3を説明するためのフローチャートである。上述と同じ説明は、省略する。
第2実施形態について図12を用いて説明する。図12は、第2実施形態を説明するためのシーケンス図である。
各実施形態によって、本出願の内容を説明したが、この開示の一部をなす論述及び図面は、本出願の内容を限定するものであると理解すべきではない。この開示から当業者には様々な代替実施形態、実施例及び運用技術が明らかとなろう。
(1)検討
接続が中断された場所とは異なるeNBとの接続を再開する機能を達成するために、以前にUEをサーブしたeNBから、再開要求を受信し、有効なUEコンテキストを持たない他のeNBへのUEコンテキストの転送が必要であるが、従来のUEのために同様の機能(すなわちUEコンテキスト転送)が利用可能である。既存のUEコンテキスト転送は、RRC接続再確立要求メッセージによって開始されると仮定される。このメッセージは、RRC接続(RRC_CONNECTED)状態、厳密に言えば、RRC接続の第2段階で送信されると仮定される。それは、既存のUEコンテキスト転送がRRC接続中にのみ利用可能であることを示す。
UEコンテキスト転送の機能について既に議論しており、この機能を達成するためにステージ2の変更を追加しました。この既存の機能は、UE状態がRRC接続の場合に実行可能である。この既存の機能は、少なくとも次の3つのステップで構成されている。
RRC接続再確立要求メッセージを受信した後、(UEコンテキストを持たない)eNB1は、UEが以前にサービスされた前のeNB(eNB2)を識別し、UEコンテキストが必要であることを知らせるためのRLFインディケーションメッセージをeNB2に送信する。
eNB1からRLFインディケーションメッセージを受信した後、eNB2は、どのUEのコンテキストが要求され、eNB1に転送されるべきかを識別する必要がある。eNB2は、UEコンテキストを転送するためにハンドオーバ要求メッセージを使用することができる。この要件のために、eNB2は、UEコンテキストを識別するためにC-RNTIおよびPCIを使用して、RLFインディケーションメッセージに含まれるハンドオーバ要求メッセージのアドレスを識別するためにECGIを使用できる。
eNB2からUEコンテキストを受信した後、eNB1は、Source MME UE S1AP ID IEを使用してDLパスを更新する必要がある。
NB-IoT UEの場合、標準化努力を減少させるために、そのようなUEのためのUEコンテキスト転送が既存の機能に基づくと考えるべきである。さらに、「ソリューション2に関して、RLFでは、再確立がサポートされていないため、UEがアイドルへ解放されるだろう。ソリューション18に関して、再確立を行うことが可能だろう(再確立の失敗時に、UEが従来のLTEのようにアイドルへ解放されるかどうかは、更なる課題である)。」ことが決定された。これは、RRC接続状態の間に、UPベースのソリューションをサポートするNB-IoT UEがRLFに直面する場合、当該UEは、RRC接続を維持するためRRC接続再確立要求メッセージを送信することができることを示す。従って、eNBの観点からは、このメッセージが、有効なUEコンテキストが存在しない場合の既存のUEコンテキスト転送機能だけでなく、例えばRLF後のNB-IoT UEのためのUEコンテキスト転送機能のトリガであるとeNBが想定することができる。UEのためのUEコンテキスト転送を達成するために必要な情報(すなわち、PCI、C-RNTI)は、従来の手順と同じであるので、追加の情報は必要なくてもよい。
この場合、以下の要件に従ってRRCアイドルUEモビリティを考慮する必要がある。
Claims (12)
- 通信方法であって、
無線端末とネットワークとの間の接続が一時中断される手順において、第1の基地局から前記無線端末へ、前記無線端末のコンテキスト情報と関連付けられた再開識別子を送信し、
前記再開識別子の一部は、前記第1の基地局を識別するための情報である通信方法。 - 前記無線端末が前記接続を再開する場合に、前記無線端末から前記第1の基地局と異なる第2の基地局へ接続再開要求メッセージを送信し、
前記接続再開要求メッセージは、前記再開識別子を含む請求項1に記載の通信方法。 - 前記第2の基地局から前記第1の基地局へ、前記第2の基地局から前記第1の基地局へ前記無線端末のコンテキスト情報を転送するための要求メッセージを送り、
前記要求メッセージは、前記再開識別子を含む請求項2に記載の通信方法。 - 前記第1の基地局が前記要求メッセージを受信したことに応じて、前記第1の基地局から前記第2の基地局へ、前記無線端末のコンテキスト情報を送る請求項3に記載の通信方法。
- 前記第2の基地局が前記無線端末のコンテキスト情報を受信した後に、前記第2の基地局からMobility Management Entity(MME)へ、前記第2の基地局と前記MMEとの間の接続を確立するために要求メッセージを送る請求項4に記載の通信方法。
- 前記第2の基地局は、前記無線端末からの前記再開識別子を用いて、前記第1の基地局を識別する請求項2に記載の通信方法。
- 第2の無線端末から前記第1の基地局へ、前記第2の無線端末のコンテキスト情報と関連付けられた第2の再開識別子を送信し、
前記第2の再開識別子は、前記再開識別子よりも短い識別子である請求項1の記載の通信方法。 - 無線端末であって、
レシーバを備え、
前記レシーバは、前記無線端末とネットワークとの間の接続が一時中断される手順において、前記無線端末のコンテキスト情報と関連付けられた再開識別子を第1の基地局から受信するよう構成され、
前記再開識別子の一部は、前記第1の基地局を識別するための情報である無線端末。 - 無線端末を制御するためのプロセッサであって、
前記無線端末とネットワークとの間の接続が一時中断される手順において、前記無線端末のコンテキスト情報と関連付けられた再開識別子を第1の基地局から受信する処理を実行し、
前記再開識別子の一部は、前記第1の基地局を識別するための情報であるプロセッサ。 - 基地局であって、
トランスミッタを備え、
前記トランスミッタは、無線端末とネットワークとの間の接続が一時中断される手順において、前記無線端末へ、前記無線端末のコンテキスト情報と関連付けられた再開識別子を送信するよう構成され、
前記再開識別子の一部は、前記基地局を識別するための情報である基地局。 - 基地局を制御するためのプロセッサであって、
無線端末とネットワークとの間の接続が一時中断される手順において、前記無線端末へ、前記無線端末のコンテキスト情報と関連付けられた再開識別子を送信する処理を実行し、
前記再開識別子の一部は、前記基地局を識別するための情報であるプロセッサ。 - 通信方法であって、
無縁端末が前記無線端末とネットワークとの間の接続が一時中断される手順を実行し、
基地局から前記無線端末へ前記接続を再開できるか否かを示す情報を送信し、
前記無線端末は、前記情報により前記接続を再開できるか否かを判定する通信方法。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2017565612A JP6467072B2 (ja) | 2016-02-04 | 2017-02-02 | 通信方法、無線端末、プロセッサ及び基地局 |
EP17747494.7A EP3399833B1 (en) | 2016-02-04 | 2017-02-02 | Communication method, wireless terminal, processor and base station |
US16/052,926 US10893567B2 (en) | 2016-02-04 | 2018-08-02 | Communication method, radio terminal, processor, and base station |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201662291128P | 2016-02-04 | 2016-02-04 | |
US62/291,128 | 2016-02-04 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/052,926 Continuation US10893567B2 (en) | 2016-02-04 | 2018-08-02 | Communication method, radio terminal, processor, and base station |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2017135343A1 true WO2017135343A1 (ja) | 2017-08-10 |
Family
ID=59500061
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2017/003702 WO2017135343A1 (ja) | 2016-02-04 | 2017-02-02 | 通信方法、無線端末、プロセッサ及び基地局 |
Country Status (4)
Country | Link |
---|---|
US (1) | US10893567B2 (ja) |
EP (1) | EP3399833B1 (ja) |
JP (4) | JP6467072B2 (ja) |
WO (1) | WO2017135343A1 (ja) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111542053A (zh) * | 2017-11-29 | 2020-08-14 | Oppo广东移动通信有限公司 | 重建rrc连接的方法、终端和存储介质 |
Families Citing this family (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10687202B2 (en) * | 2016-03-09 | 2020-06-16 | Lg Electronics Inc. | Method and device for configuring bearer for transmission of user data |
CN107295578B (zh) * | 2016-03-30 | 2020-01-21 | 中兴通讯股份有限公司 | 一种无线通信方法和设备 |
WO2017178944A1 (en) * | 2016-04-11 | 2017-10-19 | Telefonaktiebolaget Lm Ericsson (Publ) | A method and a first node for decoupling sctp and s1ap |
DE112019005461T5 (de) | 2018-11-02 | 2021-07-15 | Honda Motor Co., Ltd. | Reaktor und mehrphasiger dc-dc-wandler des interleave-typs |
US11638319B2 (en) * | 2019-02-12 | 2023-04-25 | Samsung Electronics Co., Ltd. | Handling radio link failure in cellular mesh networks |
US11963252B2 (en) * | 2019-02-19 | 2024-04-16 | Lg Electronics Inc. | Uplink data fast transmission in CU-DU split |
CN113038550B (zh) * | 2019-12-25 | 2023-10-27 | 中兴通讯股份有限公司 | 网络连接的重建立方法及装置、存储介质、电子装置 |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130260810A1 (en) * | 2012-03-27 | 2013-10-03 | Research In Motion Limited | RE-ESTABLISHMENT OF SUSPENDED RRC CONNECTION AT A DIFFERENT eNB |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP4415789B2 (ja) * | 2004-08-20 | 2010-02-17 | 株式会社日立製作所 | 無線通信システム |
EP2742767B1 (en) * | 2011-08-12 | 2018-04-04 | BlackBerry Limited | Suspending a connection in a wireless communication system |
EP2645804B1 (en) * | 2012-03-27 | 2017-12-20 | BlackBerry Limited | Re-establishment of suspended RRC connection at a different ENB |
US9652024B2 (en) * | 2013-08-23 | 2017-05-16 | Samsung Electronics Co., Ltd. | Mode switching method and apparatus of terminal |
US9820328B2 (en) * | 2014-06-24 | 2017-11-14 | Intel Corporation | Apparatuses, methods, and systems to reduce handover latency in an integrated wireless local area network and cellular network |
PL3213557T3 (pl) * | 2014-10-28 | 2020-06-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Węzły sieciowe, urządzenie użytkownika i ich sposoby do obsługi połączenia między urządzeniem użytkownika a bezprzewodową siecią komunikacyjną |
WO2017054154A1 (en) * | 2015-09-30 | 2017-04-06 | Apple Inc. | Rrc state transition techniques with reduced signaling overhead |
CN108464057A (zh) * | 2016-01-08 | 2018-08-28 | 诺基亚技术有限公司 | 用于窄带物联网的用户平面优化 |
-
2017
- 2017-02-02 EP EP17747494.7A patent/EP3399833B1/en active Active
- 2017-02-02 JP JP2017565612A patent/JP6467072B2/ja active Active
- 2017-02-02 WO PCT/JP2017/003702 patent/WO2017135343A1/ja active Application Filing
-
2018
- 2018-08-02 US US16/052,926 patent/US10893567B2/en active Active
- 2018-08-29 JP JP2018160445A patent/JP6464306B2/ja active Active
-
2019
- 2019-01-10 JP JP2019002974A patent/JP2019071664A/ja active Pending
- 2019-12-09 JP JP2019222519A patent/JP6857707B2/ja active Active
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130260810A1 (en) * | 2012-03-27 | 2013-10-03 | Research In Motion Limited | RE-ESTABLISHMENT OF SUSPENDED RRC CONNECTION AT A DIFFERENT eNB |
Non-Patent Citations (5)
Title |
---|
BLACKBERRY UK LIMITED: "Re-use of RRC connection re-establishment procedure for RRC Resume signaling", 3GPP TSG RAN WG2 NB-IOT AD-HOC MEETING R2-160515, 18 January 2016 (2016-01-18), pages 1 - 6, XP051054801, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2-RL2/TSGR2-AHs/2016_01_LTE_NB_IoT/Docs7R2-160515.zip> * |
CATT: "Open Issues of Solution 18", 3GPP TSG-RAN WG2 #NB-IOT R2-160460, 21 January 2016 (2016-01-21), Budapest, pages 1 - 4, XP055537270, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_AHs/2016_01_LTE_NB_IoT/Docs/R2-160460.zip> * |
ERICSSON: "Corrections to C-IoT optimisations in Stage-2", 3GPP TSG-RAN WG2#95 R2-165473, 21 August 2016 (2016-08-21), pages 1 - 7, XP051126947, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_95/Docs/R2_165473.zip> * |
NTT DOCOMO, INC.: "Work on user plane based solution with AS information stored in RAN", 3GPP TSG-RAN WG2#92 R2-156424, 16 November 2015 (2015-11-16), pages 1 - 12, XP051005843 * |
ZTE: "Open issues for cloT optimization", 3GPP TSG-RAN WG2#94 R2-164320, 27 May 2016 (2016-05-27), pages 1 - 5, XP051105560, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR294/Docs/R2-164320.zip> * |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111542053A (zh) * | 2017-11-29 | 2020-08-14 | Oppo广东移动通信有限公司 | 重建rrc连接的方法、终端和存储介质 |
JP2021504995A (ja) * | 2017-11-29 | 2021-02-15 | オッポ広東移動通信有限公司Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Rrc接続の再確立のための方法、ターミナル、及び記憶媒体 |
CN111542053B (zh) * | 2017-11-29 | 2022-07-08 | Oppo广东移动通信有限公司 | 重建rrc连接的方法和终端 |
US11570835B2 (en) | 2017-11-29 | 2023-01-31 | Guangdong Oppo Mobile Telecommunications Corp. | Method for reestablishing RRC connection, terminal and storage medium |
Also Published As
Publication number | Publication date |
---|---|
EP3399833A1 (en) | 2018-11-07 |
JP6857707B2 (ja) | 2021-04-14 |
JP2019071664A (ja) | 2019-05-09 |
US10893567B2 (en) | 2021-01-12 |
JP6467072B2 (ja) | 2019-02-06 |
EP3399833B1 (en) | 2020-03-04 |
US20180343698A1 (en) | 2018-11-29 |
EP3399833A4 (en) | 2018-11-07 |
JP6464306B2 (ja) | 2019-02-06 |
JPWO2017135343A1 (ja) | 2018-10-25 |
JP2020053994A (ja) | 2020-04-02 |
JP2018207522A (ja) | 2018-12-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP6464306B2 (ja) | 通信方法、無線端末、プロセッサ | |
JP7335862B2 (ja) | ユーザ端末及び基地局 | |
US11395196B2 (en) | Base station and user terminal | |
JP6475887B2 (ja) | 通信方法、無線端末、及びプロセッサ | |
JP6239572B2 (ja) | 通信制御方法 | |
US11350467B2 (en) | Mobile communication system, relay node, and base station | |
JP6387396B2 (ja) | セカンダリ基地局、移動通信システム及び通信制御方法 | |
US20180027456A1 (en) | Base station | |
US20220174564A1 (en) | Handover control method, relay apparatus, and donor apparatus | |
JP6231557B2 (ja) | ユーザ端末、基地局及びプロセッサ | |
JP6820937B2 (ja) | 無線端末及びネットワーク装置 | |
JP6586515B2 (ja) | リレーノード及び無線端末 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 17747494 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2017565612 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2017747494 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: 2017747494 Country of ref document: EP Effective date: 20180802 |