[go: up one dir, main page]

WO2018016895A1 - Procédé de réalisation d'un processus de mobilité du terminal nb-iot et appareil associé - Google Patents

Procédé de réalisation d'un processus de mobilité du terminal nb-iot et appareil associé Download PDF

Info

Publication number
WO2018016895A1
WO2018016895A1 PCT/KR2017/007831 KR2017007831W WO2018016895A1 WO 2018016895 A1 WO2018016895 A1 WO 2018016895A1 KR 2017007831 W KR2017007831 W KR 2017007831W WO 2018016895 A1 WO2018016895 A1 WO 2018016895A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
base station
rrc connection
iot
message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/KR2017/007831
Other languages
English (en)
Korean (ko)
Inventor
홍성표
최우진
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
KT Corp
Original Assignee
KT Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by KT Corp filed Critical KT Corp
Priority to US16/319,043 priority Critical patent/US10813028B2/en
Priority to CN201780043220.4A priority patent/CN109479230B/zh
Priority claimed from KR1020170091825A external-priority patent/KR101960177B1/ko
Publication of WO2018016895A1 publication Critical patent/WO2018016895A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • 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/36—Reselection control by user or terminal equipment
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present invention relates to a method and apparatus for performing mobility processing of an NB-IoT terminal, and more particularly, to a method and apparatus for maintaining service continuity of an NB-IoT terminal.
  • the NB-IoT (Narrowband Internet of Things) technology is being studied by the International Organization for Standardization Discussion. This study is aimed at researching technologies for IoT terminals that use cellular networks for improved indoor coverage, support for large-scale low-speed terminals, low sensitivity, low-cost terminal cost, low power consumption, and optimized network structure.
  • IoT terminals require low power consumption and low unit cost for long term use. Therefore, in the case of IoT terminals, there are many differences in terms of functions that are supported from terminals to which the existing LTE technology is applied.
  • the IoT terminal handover technology is not supported like a general LTE terminal.
  • the IoT terminal does not perform an operation of periodically measuring the channel state of the connected channel and transmitting the same to the base station.
  • the base station did not know this. If the IoT terminal detects a radio link failure in an existing cell, the IoT terminal should transition to the IDLE state and perform reconnection.
  • the present disclosure devised in the above background proposes a mobility processing method and apparatus for preventing service interruption of an NB-IoT terminal having low unit cost and low power requirement.
  • the present disclosure is to provide a specific method and apparatus for controlling to recover the radio link quickly to transmit and receive data while preventing unnecessary power consumption when a radio link failure of the NB-IoT terminal occurs.
  • a method of performing mobility processing by a NB-IoT (NarrowBand-Internet of Things) terminal may include transmitting an RRC connection reconfiguration request message to a base station when a preset event occurs; A method comprising receiving an RRC connection reset message from a base station and resuming a signaling radio bearer based on the RRC connection reset message.
  • NB-IoT NearBand-Internet of Things
  • an embodiment is a method for the base station to perform the mobility processing of the NB-IoT (Narrow-Band-Internet of Things) terminal, receiving the RRC connection reset request message from the NB-IoT terminal and the RRC connection reset request message Verifying the terminal context of the NB-IoT terminal based on the step and transmitting an RRC connection reestablishment message for resuming the signaling radio bearer of the NB-IoT terminal.
  • NB-IoT Near-Band-Internet of Things
  • an embodiment of the NB-IoT (NarrowBand-Internet of Things) terminal performing the mobility processing, when a predetermined event occurs, the RRC connection reconfiguration message from the base station and the base station transmitting the RRC connection reconfiguration request message to the base station It provides an NB-IoT terminal device including a receiving unit and a control unit for resuming the signaling radio bearer based on the RRC connection reestablishment message.
  • NB-IoT terminal device including a receiving unit and a control unit for resuming the signaling radio bearer based on the RRC connection reestablishment message.
  • an embodiment is a base station performing mobility processing of a NB-IoT (NarrowBand-Internet of Things) terminal, based on a receiver for receiving an RRC connection reset request message from the NB-IoT terminal and the RRC connection reset request message
  • a base station apparatus including a control unit for checking a terminal context of an NB-IoT terminal and a transmitter for transmitting an RRC connection reestablishment message for resuming the signaling radio bearer of the NB-IoT terminal.
  • the service can be quickly resumed even if service interruption due to deterioration of mobile or communication channel state occurs.
  • FIG. 1 is a diagram illustrating an operation of a terminal according to an exemplary embodiment.
  • FIG. 2 is a view for explaining the operation of the terminal according to another embodiment.
  • FIG. 3 is a diagram illustrating an operation of a base station according to an exemplary embodiment.
  • FIG. 4 is a diagram illustrating a cell change procedure of a connected state terminal according to an embodiment.
  • FIG. 5 is a diagram illustrating a terminal configuration according to an embodiment.
  • FIG. 6 is a diagram illustrating a configuration of a base station according to an embodiment.
  • the MTC terminal may mean a terminal supporting low cost (or low complexity) or a terminal supporting coverage enhancement.
  • the MTC terminal may mean a terminal supporting low cost (or low complexity) and coverage enhancement.
  • the MTC terminal may mean a terminal defined in a specific category for supporting low cost (or low complexity) and / or coverage enhancement.
  • the MTC terminal may mean a newly defined 3GPP Release-13 low cost (or low complexity) UE category / type for performing LTE-based MTC related operations.
  • the MTC terminal supports enhanced coverage compared to the existing LTE coverage, or supports UE category / type defined in the existing 3GPP Release-12 or lower, or newly defined Release-13 low cost (or lower power consumption).
  • low complexity can mean UE category / type.
  • the wireless communication system in the present invention is widely deployed to provide various communication services such as voice, packet data, and the like.
  • the wireless communication system includes a user equipment (UE) and a base station (base station, BS, or eNB).
  • a user terminal is a generic concept meaning a terminal in wireless communication.
  • user equipment (UE) in WCDMA, LTE, and HSPA, as well as mobile station (MS) in GSM, user terminal (UT), and SS It should be interpreted as a concept that includes a subscriber station, a wireless device, and the like.
  • a base station or a cell generally refers to a station that communicates with a user terminal, and includes a Node-B, an evolved Node-B, an Sector, a Site, and a BTS.
  • Other terms such as a base transceiver system, an access point, a relay node, a remote radio head (RRH), a radio unit (RU), and a small cell may be called.
  • RRH remote radio head
  • RU radio unit
  • a base station or a cell is interpreted in a comprehensive sense to indicate some areas or functions covered by a base station controller (BSC) in CDMA, a NodeB in WCDMA, an eNB or a sector (site) in LTE, and the like. It is meant to cover various coverage areas such as mega cell, macro cell, micro cell, pico cell, femto cell and relay node, RRH, RU, small cell communication range.
  • BSC base station controller
  • the base station may be interpreted in two senses. i) the device providing the megacell, the macrocell, the microcell, the picocell, the femtocell, the small cell in relation to the wireless area, or ii) the wireless area itself. In i) all devices which provide a given wireless area are controlled by the same entity or interact with each other to cooperatively configure the wireless area to direct the base station.
  • the base station may indicate the radio area itself to receive or transmit a signal from the viewpoint of the user terminal or the position of a neighboring base station.
  • megacells macrocells, microcells, picocells, femtocells, small cells, RRHs, antennas, RUs, low power nodes (LPNs), points, eNBs, transmit / receive points, transmit points, and receive points are collectively referred to as base stations. do.
  • the user terminal and the base station are two transmitting and receiving entities used to implement the technology or technical idea described in this specification in a comprehensive sense and are not limited by the terms or words specifically referred to.
  • the user terminal and the base station are two types of uplink or downlink transmitting / receiving subjects used to implement the technology or the technical idea described in the present invention, and are used in a generic sense and are not limited by the terms or words specifically referred to.
  • the uplink (Uplink, UL, or uplink) refers to a method for transmitting and receiving data to the base station by the user terminal
  • the downlink (Downlink, DL, or downlink) means to transmit and receive data to the user terminal by the base station It means the way.
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • OFDM-FDMA OFDM-TDMA
  • UMB Universal Mobile Broadband
  • the uplink transmission and the downlink transmission may use a time division duplex (TDD) scheme that is transmitted using different times, or may use a frequency division duplex (FDD) scheme that is transmitted using different frequencies.
  • TDD time division duplex
  • FDD frequency division duplex
  • a standard is configured by configuring uplink and downlink based on one carrier or a pair of carriers.
  • the uplink and the downlink include a Physical Downlink Control CHannel (PDCCH), a Physical Control Format Indicator CHannel (PCFICH), a Physical Hybrid ARQ Indicator CHannel (PHICH), a Physical Uplink Control CHannel (PUCCH), an Enhanced Physical Downlink Control CHannel (EPDCCH), and the like.
  • Control information is transmitted through the same control channel, and data is configured by a data channel such as a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH).
  • PDSCH physical downlink shared channel
  • PUSCH physical uplink shared channel
  • control information may also be transmitted using an enhanced PDCCH (EPDCCH or extended PDCCH).
  • EPDCCH enhanced PDCCH
  • extended PDCCH extended PDCCH
  • a cell means a component carrier having a coverage of a signal transmitted from a transmission / reception point or a signal transmitted from a transmission point or a transmission / reception point, and the transmission / reception point itself. Can be.
  • a wireless communication system to which embodiments are applied may be a coordinated multi-point transmission / reception system (CoMP system) or a coordinated multi-antenna transmission scheme in which two or more transmission / reception points cooperate to transmit a signal.
  • antenna transmission system a cooperative multi-cell communication system.
  • the CoMP system may include at least two multiple transmission / reception points and terminals.
  • the multiple transmit / receive point is at least one having a high transmission power or a low transmission power in a macro cell region, which is connected to an eNB or a macro cell (hereinafter referred to as an 'eNB') and wired controlled by an optical cable or an optical fiber to an eNB. May be RRH.
  • downlink refers to a communication or communication path from a multiple transmission / reception point to a terminal
  • uplink refers to a communication or communication path from a terminal to multiple transmission / reception points.
  • a transmitter may be part of multiple transmission / reception points, and a receiver may be part of a terminal.
  • a transmitter may be part of a terminal, and a receiver may be part of multiple transmission / reception points.
  • a situation in which a signal is transmitted and received through a channel such as a PUCCH, a PUSCH, a PDCCH, an EPDCCH, and a PDSCH may be described in the form of 'sending and receiving a PUCCH, a PUSCH, a PDCCH, an EPDCCH, and a PDSCH.
  • a description of transmitting or receiving a PDCCH or transmitting or receiving a signal through the PDCCH may be used as a meaning including transmitting or receiving an EPDCCH or transmitting or receiving a signal through the EPDCCH.
  • the physical downlink control channel described below may mean PDCCH or EPDCCH, and may also be used to include both PDCCH and EPDCCH.
  • the EPDCCH which is an embodiment of the present invention, may be applied to the portion described as the PDCCH, and the EPDCCH may be applied to the portion described as the EPDCCH as an embodiment of the present invention.
  • high layer signaling described below includes RRC signaling for transmitting RRC information including an RRC parameter.
  • the eNB performs downlink transmission to the terminals.
  • the eNB includes downlink control information and an uplink data channel (eg, a physical downlink shared channel (PDSCH), which is a primary physical channel for unicast transmission, and scheduling required to receive the PDSCH.
  • a physical downlink control channel (PDCCH) for transmitting scheduling grant information for transmission on a physical uplink shared channel (PUSCH) may be transmitted.
  • PUSCH physical uplink shared channel
  • NB-IoT narrowband Internet of Things
  • the purpose of the study is to specify wireless access for the cellular IoT, which includes improved indoor coverage, support for large scale low speed terminals, low sensitivity, low cost terminal cost, low power consumption and optimized network architecture.
  • Rel-13 NB-IoT provided only the essential features needed to enable 3GPP systems to rapidly penetrate the low-cost IoT market. Accordingly, a number of functions provided in a general LTE terminal providing a mobile broadband service are not provided. For example, for the Rel-13 NB-IoT terminal, the handover provided for the normal connected mode terminal is not provided.
  • the base station configures measurement and reporting on the terminal and reports to the base station when the terminal reaches a specific criterion based thereon.
  • the terminal instructs to handover to the target cell through signaling with the target base station.
  • These processes may cause power consumption of the terminal and may complicate the operation of the terminal. Therefore, Rel-13 NB-IoT did not support handover related operation in connected mode. Accordingly, even when the NB-IoT terminal in the connected state is out of coverage or seriously deteriorates as the wireless state moves, the base station did not know this. If the UE detects a radio link failure in the existing cell, the UE transitions to the IDLE state and performs reconnection.
  • the handover provided for the general connected state terminal is not provided for the NB-IoT terminal. Accordingly, even when the NB-IoT terminal in the connected state moves out of coverage or seriously degrades the wireless state, the base station did not know this. When the terminal detects a radio link failure, the base station transitions to the IDLE state and performs reconnection. .
  • the present disclosure devised to solve this problem is to provide a method and apparatus for improving service continuity for the NB-IoT terminal in the Connected state.
  • the embodiments may be applied to an NB-IoT terminal.
  • the embodiments may be applied to a general terminal providing the corresponding capability.
  • the present specification will be described based on LTE technology as a radio access technology, but the present disclosure is a terminal using a next generation (for example, 5G New RAT) radio access technology as well as a UE using LTE radio access technology. Applicable for
  • the NB-IoT terminal may be referred to as a terminal as necessary.
  • CIoT Cellular IoT
  • PDCP is not used while AS security is not activated.
  • Solutions for optimization of CIoT signaling reduction include control plane CIoT EPS optimization and user plane CIoT EPS optimization.
  • RRC connection set up only for control plane CIoT EPS optimization has the following characteristics.
  • An uplink NAS signaling message or an uplink NAS message carrying data may be sent in an uplink RRC container message.
  • the downlink NAS signaling message or downlink NAS data may be sent in the downlink RRC container message.
  • RRC connection reconfiguration and RRC connection reconfiguration are not supported.
  • the RRC connection set up for user plane CIoT EPS optimization has the following characteristics.
  • the RRC Connection Suspension procedure is used to release an RRC connection.
  • the base station may request that the terminal maintain an AS context including the terminal capability in the RRC IDLE state.
  • the RRC connection resume procedure is used when transitioning from RRC IDLE to RRC CONNECTED. Use previously stored information in the terminal and in the base station to use for resuming the RRC connection.
  • the NB-IoT terminal in the message to be resumed provides a ResumeID which is used to access the stored information necessary to resume the RRC connection.
  • Short Message Authentication Code (MAC) -I is reused as an authentication token in the RRC reset procedure and the RRC resume procedure.
  • the base station provides an NCC.
  • the terminal resets the COUNT.
  • NB-IoT terminals that support both control plane CIoT EPS optimization and user plane CIoT EPS optimization can refer to terminal characteristics that support user plane CIoT EPS optimization.
  • the terminal or the NB-IoT terminal in the present specification may mean a terminal that supports the aforementioned control plane CIoT EPS optimization or user plane CIoT EPS optimization.
  • the mobility support of the connected terminal may be composed of the following series of procedures.
  • UE measurement configuration and reporting configuration by the source base station measurement of the terminal, measurement reporting to the base station when a specific criterion is reached, determination of handover of the source base station, signaling between the source base station and the target base station, and instruction to handover to the target cell.
  • the measurement reporting is configured for the rare data transmission, low sensitivity, low cost, and low power consumption terminal, power consumption may be increased as compared with the conventional NB-IoT terminal.
  • FIG. 1 is a diagram illustrating an operation of a terminal according to an exemplary embodiment.
  • a NB-IoT (NarrowBand-Internet of Things) terminal transmits an RRC connection reset request message to a base station and receives an RRC connection reset message from a base station when a predetermined event occurs, and an RRC connection reset message. Resuming the signaling radio bearer based on the operation may be performed.
  • the NB-IoT terminal may perform a step of transmitting an RRC connection reconfiguration request message to a base station (S110). For example, the NB-IoT terminal may determine whether a preset event condition is satisfied, and transmit an RRC connection re-establishment request message to the base station when the event condition is satisfied.
  • the preset event may mean any one of radio link failure detection and handover failure detection of the NB-IoT terminal.
  • the preset event may be set under a plurality of conditions.
  • the NB-IoT UE when configured to support the control plane CIoT EPS optimization and receives the RRC connection reset permission indication information of the NB-IoT UE transmitted by the base station without AS security activated.
  • the radio link failure detection or the handover failure detection it may be determined that the preset event is satisfied.
  • the RRC connection reconfiguration request message may include terminal identifier information set to SAE-Temporary Mobile Subscriber Identity (S-TMSI).
  • S-TMSI SAE-Temporary Mobile Subscriber Identity
  • the base station can query the terminal context by using the terminal identifier information received from the NB-IoT terminal.
  • the terminal context may be confirmed by using the MME or may be confirmed by contents stored in the base station.
  • the base station receiving the RRC connection reconfiguration request message is the target base station, the base station may query the terminal context for inquiry and confirm the request.
  • the RRC connection reset request message may include a message authentication code.
  • the message authentication code may include NAS MAC information for confirming the message authentication of the terminal in the MME.
  • the NB-IoT terminal may transmit an RRC connection reconfiguration request message to the base station to prevent service interruption while minimizing power consumption by restarting signaling radio bearer of the NB-IoT terminal.
  • the NB-IoT terminal may perform the step of receiving the RRC connection reconfiguration message from the base station (S120).
  • the RRC connection reset message may include message authentication code information.
  • the message authentication code may include NAS MAC information.
  • the RRC connection reconfiguration message may include information for controlling to resume signaling radio bearer of the NB-IoT terminal.
  • the NB-IoT terminal may perform the step of resuming the signaling radio bearer based on the RRC connection reestablishment message (S130).
  • the NB-IoT terminal receiving the RRC connection reconfiguration message from the base station may resume signaling radio bearer.
  • the NB-IoT terminal supporting the control plane CIoT EPS optimization may transmit and receive a small amount of data through the signaling radio bearer as described above. Accordingly, the NB-IoT terminal may maintain the data communication by minimizing service interruption by resuming the signaling radio bearer.
  • the NB-IoT terminal described above may be a terminal configured to support Control Plane CIoT Cellular IoT Evolved Packet System (EPS) Optimization.
  • EPS Control Plane CIoT Cellular IoT Evolved Packet System
  • the NB-IoT terminal does not configure a data radio bearer, it may mean a terminal that performs data transmission and reception in a state that AS security is not activated.
  • the above-described base station may be a source base station or a target base station.
  • FIG. 2 is a view for explaining the operation of the terminal according to another embodiment.
  • the NB-IoT terminal supports the control plane CIoT Cellular IoT Evolved Packet System (EPS) Optimization prior to the step of transmitting the RRC connection reset request message (S110).
  • the step of transmitting the capability may be further performed (S210).
  • EPS Evolved Packet System
  • the NB-IoT terminal may transmit information indicating that it can support the control plane CIoT EPS optimization operation to the base station in advance so that the base station recognizes it.
  • the terminal capability information may be transmitted during initial setup of the NB-IoT terminal and the base station.
  • the NB-IoT terminal may further perform the step of receiving information indicating the permission of the mobility processing of the NB-IoT terminal from the base station through the system information (S220).
  • the base station may transmit information indicating that the signaling radio bearer resumes operation through RRC connection reconfiguration.
  • the NB-IoT terminal may perform the operation described with reference to FIG. 1 by checking information indicating that the signaling radio bearer is allowed to resume operation received through system information and transmitting an RRC connection reconfiguration request message to the base station.
  • steps S210 and S220 may be changed, and either step may be omitted.
  • FIG. 3 is a diagram illustrating an operation of a base station according to an exemplary embodiment.
  • the base station may perform a step of receiving an RRC connection reestablishment request message from an NB-IoT terminal in performing mobility processing of a NB-IoT terminal (S310).
  • the RRC connection reconfiguration request message may be received in a radio link failure detection and handover failure situation of the NB-IoT terminal.
  • the RRC connection reset request message is configured to allow the NB-IoT terminal to support the control plane CIoT EPS optimization, and the RRC connection reset allowance indication information of the NB-IoT terminal transmitted by the base station while the AS security is not activated.
  • reception if a plurality of conditions for generating a radio link failure detection or a handover failure detection are satisfied, it may be received.
  • the RRC connection reconfiguration request message may include terminal identifier information set to SAE-Temporary Mobile Subscriber Identity (S-TMSI).
  • the RRC connection reset request message may include a message authentication code.
  • the message authentication code may include NAS MAC information for confirming the message authentication of the terminal in the MME.
  • the base station may perform the step of checking the terminal context of the NB-IoT terminal based on the RRC connection reconfiguration request message (S320). For example, the base station may query the terminal context by using the terminal identifier information included in the RRC connection reconfiguration request message. For example, the terminal context may check the message authentication of the terminal using the MME, or may be confirmed by the content stored in the base station. Alternatively, when the base station receiving the RRC connection reconfiguration request message is the target base station, the terminal may check the message authentication of the terminal by requesting the terminal context to the source base station.
  • the base station may perform a step of transmitting an RRC connection reconfiguration message for resuming the signaling radio bearer of the NB-IoT terminal (S330).
  • the RRC connection reconfiguration message may include information for controlling to resume signaling radio bearer of the NB-IoT terminal.
  • the NB-IoT terminal supporting the control plane CIoT EPS optimization may transmit and receive a small amount of data through the signaling radio bearer as described above. Accordingly, the NB-IoT terminal may maintain the data communication by minimizing service interruption by resuming the signaling radio bearer.
  • the base station may receive the terminal capability indicating that the control plane (Control Plane) CIoT Cellular IoT Evolved Packet System (EPS) Optimization (Optimization).
  • the terminal capability may be received during an initial setup of the NB-IoT terminal and the base station, and the base station performs the mobility processing by the NB-IoT terminal through the RRC connection reestablishment operation (eg, SRB resume) through the terminal capability. You can see that it supports.
  • the base station may transmit information indicating that the base station allows the mobility processing of the NB-IoT terminal through the system information.
  • the base station may transmit information indicating that the restart operation (perform mobility processing) of the signaling radio bearer of the NB-IoT terminal through the RRC connection reconfiguration.
  • the NB-IoT terminal may perform the operation described with reference to FIG. 1 by checking information indicating that the signaling radio bearer is allowed to resume operation received through system information and transmitting an RRC connection reconfiguration request message to the base station.
  • the NB-IoT terminal described above may be a terminal configured to support Control Plane CIoT Cellular IoT Evolved Packet System (EPS) Optimization.
  • EPS Control Plane CIoT Cellular IoT Evolved Packet System
  • the NB-IoT terminal does not configure a data radio bearer, it may mean a terminal that performs data transmission and reception in a state that AS security is not activated.
  • the above-described base station may be a source base station or a target base station.
  • the NB-IoT terminal can quickly interrupt service interruption in a situation of deterioration or handover failure of radio channel quality while minimizing power consumption. Through this, service continuity of the NB-IoT terminal may be supported.
  • the NB-IoT terminal is described as a terminal, and when a distinction from the conventional LTE terminal is required, the NB-IoT terminal is described.
  • First Example RRC connection by receiving help / instruction information from the terminal Suspend How to do it.
  • the terminal is characterized by infrequent data transmission, low latency sensitivity, low cost, and low power consumption, it may be difficult for the terminal to remain connected even after the data transmission ends after the terminal is connected to the network for data transmission. It may cause undesirable consumption.
  • the terminal may transmit the help information for this to the base station through the RRC message.
  • the terminal may transmit indication information indicating / suggesting an RRC connection suspension through an RRC message.
  • the base station may broadcast information through the system information on whether the terminal allows the above-described help / instruction information to be sent. Alternatively, the base station may provide information on whether to allow the terminal to send the above-described help / instruction information through dedicated information.
  • the above help information may include information including one or more of information indicating that a transaction is completed, transaction data amount, next transaction time, remaining time until next transaction, transaction cycle, next transaction expected time, and next transaction data amount. Can be.
  • the help information may be transmitted to the base station.
  • the base station receiving the help / instruction information suspends the RRC connection. This may include suspension of the established radio bearer.
  • the base station receiving the help / instruction information may store it in the terminal context.
  • the terminal receiving the RRC message (eg, RRC connection release message) including information indicating the RRC connection suspend stores the above-described help information.
  • a UE receiving an RRC message (eg, an RRC connection release message) including information indicating an RRC connection suspend suspends an RRC connection. This may include suspension of the established radio bearer.
  • the terminal stores the terminal AS context.
  • the terminal leaves the RRC connection state.
  • the terminal may be connected to the network for data transmission and remain in the connected state for a long time after the data transmission ends. May cause undesirable.
  • the terminal may transmit the help information for this to the MME through a NAS message.
  • the terminal may transmit indication information indicating / suggesting the RRC connection suspension through a NAS message.
  • the above help information may include information including one or more of information indicating that a transaction is completed, transaction data amount, next transaction time, remaining time until next transaction, transaction cycle, next transaction expected time, and next transaction data amount. Help information may be transmitted to the base station.
  • the MME may maintain information on the expected UE behavior of the terminal based on the subscription information and the statistical information.
  • the MME may transmit the help information to the MME after data transmission is completed after the terminal accesses a network for data transmission at an application layer / upper layer through an SCS server / external MTC server / application server.
  • the above help information may include one or more of information indicating that a transaction is completed, transaction data amount, next transaction time, remaining time until next transaction, transaction period, next transaction expected time, and next transaction data amount.
  • the MME sends an S1 message to the base station that includes information indicating to suspend the RRC connection.
  • the MME may include the above help information in the S1 message.
  • the base station receiving the assistance information suspends the RRC connection. This includes suspension of the radio bearer set up.
  • the base station receiving the assistance information may store it in the terminal context.
  • a terminal receiving an RRC message (eg, an RRC connection release message) including information indicating an RRC connection suspension stores the aforementioned help information.
  • a terminal receiving an RRC message (eg, an RRC connection release message) including information indicating an RRC connection suspend stores a terminal AS context including the above-described help information.
  • the terminal leaves the RRC connection state.
  • the base station sends a response message to the S1 message containing information instructing the MME to suspend the aforementioned RRC connection.
  • one or more of mobility procedures such as measurement configuration, reporting configuration, and handover command by base station control may be applied to the general CONNECTED terminal.
  • the power consumption of the NB-IoT terminal is increased to satisfy the low power requirements of the NB-IoT terminal. It can be difficult.
  • the base station can simplify mobility procedure related configuration to reduce terminal power consumption increase.
  • the measurement configuration can be simplified.
  • the base station may configure the filtering coefficient for the measurement quantity to be different from the filtering coefficient for the measurement quantity for the general terminal.
  • the filtering coefficient represents a value used for Layer 3 filtering of the measured value.
  • the UE filters the measured values using the following formula before using the UE for measurement reporting or evaluation of reporting criteria for each measurement quantity in which the UE performs measurement.
  • Is the last measurement received from the physical layer Is the updated filtered measure, Indicates the previous filtered measurement, , Where Denotes a filter coefficient.
  • the filtering coefficient may be used as another value (eg, a natural number of k> 4) assuming a larger sample rate.
  • a cell change threshold may be configured, but no reporting is performed.
  • the base station may configure information for instructing the above-described operation in the terminal.
  • an NB-IoT terminal capable of supporting measurement configuration or reporting configuration or connected mode mobility may be defined so that the base station provides measurement configuration or reporting configuration or connected mode mobility support only for the corresponding NB-IoT terminal.
  • the corresponding NB-IoT terminal provides a measurement configuration, a reporting configuration, or a connected mode mobility support function for the NB-IoT terminal (terminals classified into the NB-IoT category)
  • the corresponding NB-IoT terminal is included in the terminal capability information.
  • Information on whether such a function is supported may be indicated to the base station.
  • the NB-IoT terminal may include the same in the RRC connection request message and transmit the same to the base station.
  • the NB-IoT terminal may be included in the RRC connection resumption request message and delivered to the base station.
  • information on whether such a function is supported may be transferred from the terminal to the base station using the UE capability transfer procedure.
  • information on whether such a function is supported may be instructed by the terminal to the MME through NAS signaling (attach procedure, etc.) and transmitted to the base station through the S1 interface.
  • the base station may send an RRC connection reconfiguration message for providing the measurement configuration or reporting configuration or the connected mode mobility support function for the terminal.
  • the method of allowing the NB-IoT terminal to transmit the measurement reporting in a timely manner and the base station performs the handover based on this may be a significant overhead.
  • the following mobility support method may be provided for the UE in the connected state.
  • the base station may instruct the terminal of the cell change threshold criteria and the terminal to trigger the RRC connection resetting procedure when the terminal reaches the criteria.
  • an event for cell change criteria may be defined.
  • an event of an A3 event (Neighbor becomes amount of offset better than PCell) of a general LTE terminal may be defined.
  • an A2 event (Serving becomes worse than absolute threshold) event of a general LTE terminal may be defined.
  • an A2 event (Serving becomes worse than absolute threshold) and an A4 event (Neighbor becomes better than absolute threshold) type event of a general LTE terminal may be defined.
  • an RLF criterion of a general LTE terminal may be defined. This allows the UE to detect a radio link failure through the RLF timer and related parameters broadcast by the base station.
  • the terminal may trigger the above procedure when two events are satisfied at the same time.
  • the base station can recognize the terminal capable of performing this operation through the terminal capability information.
  • the base station may configure the information for instructing such an operation to the terminal. As an example, this may be indicated through system information and configured in the terminal. As another example, this may be indicated through dedicated signaling information and configured in the terminal.
  • the RRC connection reset procedure can only be initiated when AS security is activated. Therefore, this can be applied to an NB-IoT terminal that supports both control plane CIoT EPS optimization and user plane CIoT EPS optimization, or NB-IoT terminal that supports user plane CIoT EPS optimization. If the NB-IoT terminal supports only control plane CIoT EPS optimization, this may be possible by adding a process of activating AS security or performing message authentication when checking the terminal context through the MME. .
  • the UE may perform RRC connection resetting by performing at least one of the following operations.
  • the terminal When initiating the RRC connection reestablishment procedure, the terminal stops if a timer (eg T310 or T312) is running.
  • a timer eg T310 or T312
  • the terminal suspends all radio bearers except SRB0.
  • the terminal resets the MAC.
  • the terminal applies a default physical channel configuration.
  • the terminal applies the default MAC main configuration.
  • the terminal performs cell selection.
  • the terminal applies timealignmenttimercommon included in the system information.
  • the terminal initiates the transmission of the RRC connection reset request message.
  • the terminal identifier is set to C-RNTI used in the source PCell.
  • the terminal identifier is set to S-TMSI.
  • the physical cell identifier is set to the physCellId used in the source PCell.
  • shortMAC-I is set to 16 least significant bits of the calculated MAC-I.
  • the terminal identifier is set to S-TMSI, the terminal may include a NAS MAC.
  • the reset cause (reestablishmentCause) is set to cell change (or mobility support or handover).
  • the base station transmits an RRC connection reconfiguration message to the terminal.
  • the UE that receives the RRC connection reconfiguration message operates as an example.
  • the terminal resets the PDCP for the SRB1.
  • the terminal resets the RLC for the SRB1.
  • the terminal performs radio resource configuration according to the received radio resource configuration dedicated information.
  • the terminal resumes SRB1.
  • the terminal updates the K eNB key based on the K ASME key with which the current K eNB is associated using the NCC value indicated in the RRC connection reconfiguration message.
  • the terminal derives K RRCint associated with the previously configured integrity algorithm.
  • the terminal derives K RRCint and K UPenc associated with the previously configured ciphering algorithm.
  • the terminal is configured to activate integrity protection in the lower layer by using the previously configured algorithm and K RRCint .
  • the terminal is configured to apply a ciphering algorithm, K RRCint , K UPenc to the lower layer.
  • the terminal transmits an RRC connection reset complete message to the base station.
  • the UE that has received the RRC connection reconfiguration message operates as follows as another example. That is, when receiving the RRC connection reconfiguration request message with the reset cause information set to the cell change, the base station may reconfigure all DRBs through the RRC connection reconfiguration message.
  • the terminal resets the PDCP for the SRB1 and all the DRBs.
  • the terminal resets the RLC for the SRB1 and all the DRBs.
  • the terminal performs radio resource configuration according to the received radio resource configuration dedicated information.
  • the UE resumes SRB1 and all DRBs.
  • the terminal updates the K eNB key based on the K ASME key with which the current K eNB is associated using the NCC value indicated in the RRC connection reconfiguration message.
  • the terminal derives K RRCint associated with the previously configured integrity algorithm.
  • the terminal derives K RRCint and K UPenc associated with the previously configured ciphering algorithm.
  • the terminal is configured to activate integrity protection in the lower layer by using the previously configured algorithm and K RRCint .
  • the terminal is configured to apply a ciphering algorithm, K RRCint , K UPenc to the lower layer.
  • the terminal transmits an RRC connection reset complete message to the base station.
  • the method of allowing the NB-IoT terminal to transmit the measurement reporting in a timely manner and the base station performs the handover based on this may be a significant overhead.
  • the following mobility support method may be provided for the UE in the connected state.
  • the base station may instruct the terminal to the cell change threshold criteria and to trigger the RRC connection resumption (after cell change) when the terminal reaches the criteria.
  • an event of an A3 event (Neighbor becomes amount of offset better than PCell) of a general LTE terminal may be defined.
  • an A2 event (Serving becomes worse than absolute threshold) event of a general LTE terminal may be defined.
  • an A2 event (Serving becomes worse than absolute threshold) and an A4 event (Neighbor becomes better than absolute threshold) type event of a general LTE terminal may be defined.
  • an RLF criterion of a general LTE terminal may be defined. This enables the UE to detect a radio link failure through the RLF timer and related parameters broadcast by the base station.
  • the terminal may trigger the above procedure when two events are satisfied at the same time.
  • the base station can recognize the terminal capable of performing this operation through the terminal capability information.
  • the base station may configure the information for instructing such an operation to the terminal.
  • One or more of the operations may be performed.
  • the UE may include an AS including one or more of a current RRC connection, a current security context, a PDCP state including a ROHC state, a C-RNTI used in the source PCell, a physical cell identifier and a cellIdentity of the source PCell. Save the context.
  • the UE may include an AS including one or more of a current RRC connection, a current security context, a PDCP state including an ROHC state, a C-RNTI used in the source PCell, a physical cell identifier of the source PCell, and a cellIdentity. Keep the context.
  • an AS contact that includes one or more of a current RRC connection, a current security context, a PDCP state including a ROHC state, a C-RNTI used in the source PCell, a physical cell identifier and a cellIdentity of the source PCell. Suspend the strap.
  • the terminal stores / maintains the resume identifier / terminal identifier / base station identifier and terminal identifier (which may be referred to as a resume identifier below for convenience of description).
  • the UE suspends all SRB (s) and DRB (s).
  • the terminal for example, T310 or T312 If the terminal (for example, T310 or T312) is running, it stops.
  • the terminal resets the MAC.
  • the terminal starts synchronization in the downlink of the target cell.
  • the terminal may select the target cell based on the neighbor cell information satisfying the above-described cell change criteria.
  • the terminal acquires MIB information from the target cell.
  • the terminal acquires system information (eg, RA-preamble, etc.) related to the RRC connection resumption request in the target cell.
  • system information eg, RA-preamble, etc.
  • the UE may receive the RRC connection resumption request related information (for example, RA-preamble, etc.) of the neighbor cell in the source cell through system information or dedicated information.
  • the terminal applies a default physical channel configuration.
  • the terminal applies the default MAC main configuration.
  • the terminal applies the (default) CCCH configuration (specified in section 9.1.1.2 of 3GPP TS36.331 document).
  • the terminal starts an associated timer (eg, T300).
  • T300 an associated timer
  • the UE transmits an RRC connection resumption request message (described as using an RRC connection resumption request message for convenience of description, but a new RRC connection message for supporting mobility is also included in the scope of the present invention) to the base station.
  • an RRC connection resumption request message (described as using an RRC connection resumption request message for convenience of description, but a new RRC connection message for supporting mobility is also included in the scope of the present invention) to the base station.
  • the resume identifier / terminal identifier is set to a resumeIdentity / terminal identifier indicated by the source base station.
  • the resume identifier may be set to a stored resume identifier (resumeIdentity).
  • short-resume-MAC-I sets to 16 least significant bits of the calculated MAC-I.
  • the resume cause (resumeCause) is set to cell change (or mobility support or handover).
  • the terminal may ignore this. Alternatively, the access barring check for the general LTE terminal may not be performed.
  • the target base station transmits an RRC connection resume message to the terminal.
  • the UE that receives the RRC connection resume message operates as follows, for example.
  • the terminal stops the associated timer (for example, T300).
  • the terminal resumes the RRC connection.
  • the terminal resumes the security context.
  • the terminal resets the RLC entity for all SRBs and DRBs.
  • the terminal resets PDCP entities for all SRBs and DRBs.
  • the terminal discards the resume identifier (resumeIdentity).
  • the terminal performs radio resource configuration according to the received radio resource configuration dedicated information.
  • the UE resumes all SRBs and DRBs.
  • the UE updates the K eNB key based on the K ASME key associated with the current K eNB using the NCC value indicated in the RRC connection resume message.
  • the terminal derives K RRCint associated with the previously configured integrity algorithm.
  • the terminal requests the lower layer to verify the integrity protection of the RRC connection resume message by using the previously configured algorithm and K RRCint .
  • the terminal derives K RRCint and K UPenc associated with the previously configured ciphering algorithm.
  • the terminal is configured to activate integrity protection in the lower layer by using the previously configured algorithm and K RRCint .
  • the terminal is configured to apply a ciphering algorithm, K RRCint , K UPenc to the lower layer.
  • the terminal considers the current cell as a PCell.
  • the terminal transmits an RRC connection resumption completion message to the target base station.
  • the terminal operates as follows.
  • the terminal starts synchronization in the downlink of the target cell.
  • the terminal may select the target cell based on the neighbor cell information satisfying the above-described cell change criteria.
  • the terminal acquires MIB information from the target cell. Or, the terminal acquires system information (eg, RA-preamble, etc.) related to the RRC connection resumption request in the target cell. As another method, the UE may receive the RRC connection resumption request related information (for example, RA-preamble, etc.) of the neighbor cell in the source cell through system information or dedicated information.
  • system information eg, RA-preamble, etc.
  • the UE may receive the RRC connection resumption request related information (for example, RA-preamble, etc.) of the neighbor cell in the source cell through system information or dedicated information.
  • the terminal applies a default physical channel configuration.
  • the terminal applies the default MAC main configuration.
  • the terminal applies the (default) CCCH configuration (specified in section 9.1.1.2 of 3GPP TS36.331).
  • the terminal starts an associated timer (eg, T300).
  • T300 an associated timer
  • the UE transmits an RRC connection resumption request message (described as using an RRC connection resumption request message for convenience of description, but a new RRC connection message for supporting mobility is also included in the scope of the present invention) to the base station.
  • an RRC connection resumption request message (described as using an RRC connection resumption request message for convenience of description, but a new RRC connection message for supporting mobility is also included in the scope of the present invention) to the base station.
  • the resume identifier / terminal identifier is set to a resumeIdentity / terminal identifier indicated by the source base station.
  • the resume identifier may be set to a stored resume identifier (resumeIdentity).
  • short-resume-MAC-I sets to 16 least significant bits of the calculated MAC-I.
  • ResumeCause is set to cell change (or mobility support or handover).
  • the above operation may be an operation for supporting mobility of the RRC connected state terminal. Accordingly, the terminal may not perform measurement and evaluation related to cell reselection. In addition, the terminal may not perform the access barring check procedure.
  • the terminal since the RRC connection resumption procedure was for resuming the connection of the RRC idle state terminal, the cell reselection related measurement and evaluation and the access barring check procedure had to be performed during the RRC connection resumption.
  • the target base station transmits an RRC connection resume message to the terminal.
  • the UE that receives the RRC connection resume message operates as follows, for example.
  • the terminal stops the associated timer (eg, T300).
  • the terminal recovers the RRC connection and security context from the stored / maintained terminal AS context.
  • the terminal resets the RLC entities for all SRBs and DRBs.
  • the terminal resets PDCP entities for all SRBs and DRBs.
  • the terminal discards the stored terminal AS context and the resumeIdentity.
  • the terminal performs radio resource configuration according to the received radio resource configuration dedicated information.
  • the UE resumes all SRBs and DRBs.
  • the UE updates the K eNB key based on the K ASME key with which the current K eNB is associated using the NCC value indicated in the RRC connection resume message.
  • the terminal derives K RRCint associated with the previously configured integrity algorithm.
  • the terminal requests the lower layer to verify the integrity protection of the RRC connection resume message by using the previously configured algorithm and K RRCint .
  • the terminal derives K RRCint and K UPenc associated with the previously configured ciphering algorithm.
  • the terminal is configured to activate integrity protection in the lower layer by using the previously configured algorithm and K RRCint .
  • the terminal is configured to apply a ciphering algorithm, K RRCint , K UPenc to the lower layer.
  • the terminal considers the current cell as a PCell.
  • the terminal transmits an RRC connection resumption completion message to the target base station.
  • the target base station receiving the aforementioned RRC connection resumption message fails for some reason (for example, fails to receive the terminal context from the source base station, the target base station is not ready for handover due to the terminal context failure), and the like. Failure to resume connection or may want to instruct the RRC connection configuration instructions to the terminal.
  • the target base station receiving the aforementioned RRC connection resumption message may transmit an RRC connection setup message to the UE without transmitting the RRC connection resumption success message (RRC connection resumption message) for any reason.
  • the terminal may perform one or more of the following operations.
  • the terminal removes the terminal AS context and the re-identifier.
  • the UE requests the upper layer for necessary information (eg, S-TMSI) to set up / receive / receive / set up the terminal context from the MME.
  • the terminal sets the s-TMSI to the value received from the upper layer in the RRC Connection setup complete message.
  • the UE may include the message / information received from the upper layer in the RRC Connection setup complete message.
  • the conventional RRC connection resumption procedure is used to recover the AS configuration including the SRB and the DRB from the stored context for the RRC IDLE terminal whose RRC connection is released due to the RRC suspend.
  • an RRC connection resumption procedure may be used for an RRC CONNECTED terminal.
  • the conventional RRC connection resumption procedure may be applied to an NB-IoT terminal that supports both control plane CIoT EPS optimization and user plane CIoT EPS optimization, or NB-IoT terminal that supports user plane CIoT EPS optimization. In the prior art, it could not support the NB-IoT terminal that supports only the control plane CIoT EPS optimization. However, if the present embodiment is applied, an RRC connection resumption procedure may be used for mobility support even for an NB-IoT terminal that supports only control plane CIoT EPS optimization.
  • the resume identifier of the terminal is configured for the RRC connection suspend, it could be provided included only on the RRC connection release message. That is, when the cause of the release of the RRC connection suspend on the RRC connection release message, including the resume identifier was instructed to the terminal.
  • the re-identifier may be configured in advance to the terminal through the RRC connection reconfiguration message.
  • the method of allowing the NB-IoT terminal to transmit the measurement reporting in a timely manner and the base station performs the handover based on this may be a significant overhead.
  • the following mobility support method may be provided for the UE in the connected state.
  • the base station instructs the terminal to change the cell threshold to the terminal and when the terminal reaches the RRC connection cell change procedure (hereinafter referred to as RRC connection cell change for convenience of description.
  • RRC connection cell change for convenience of description.
  • mobility support which may be changed / replaced in other terms).
  • an event of an A3 event (Neighbor becomes amount of offset better than PCell) of a general LTE terminal may be defined.
  • an A2 event (Serving becomes worse than absolute threshold) event of a general LTE terminal may be defined.
  • an A2 event (Serving becomes worse than absolute threshold) and an A4 event (Neighbor becomes better than absolute threshold) type event of a general LTE terminal may be defined.
  • an RLF criterion of a general LTE terminal may be defined. This enables the UE to detect a radio link failure through the RLF timer and related parameters broadcast by the base station.
  • the terminal may trigger the above procedure when two events are satisfied at the same time.
  • the base station can recognize the terminal capable of performing this operation through the terminal capability information.
  • the base station may configure the information for instructing such an operation to the terminal.
  • the RRC connection cell change procedure can be used for NB-IoT terminals that support only control plane CIoT EPS optimization, NB-IoT terminals that support both control plane CIoT EPS optimization and user plane CIoT EPS optimization, or NB- that supports user plane CIoT EPS optimization. It can be applied to IoT terminals.
  • the RRC connection resetting procedure or the RRC connection resumption procedure according to the prior art are both procedures applicable to the RRC IDLE state terminal. Therefore, in order to use as a procedure for supporting cell change for the RRC connected state terminal, as described above, indication information for distinguishing this may be necessary. Alternatively, you can provide this behavior by defining a new RRC procedure that is separate from the RRC connection reset procedure or the RRC connection resume procedure. Hereinafter, for convenience of description, this is referred to as an RRC connection cell change procedure.
  • the RRC connection cell change procedure may be provided through SRB0.
  • This request is not cyphered but can be protected with a message authentication code. That is, the RRC connection cell change request message triggered by the UE may be protected with a message authentication code and thus may be used for an NB-IoT UE that supports only the control plane CIoT EPS optimization in which AS security is not activated.
  • This message authentication code may include NAS authentication code information (NAS MAC) for confirming the message authentication of the terminal in the MME.
  • NAS MAC NAS authentication code information
  • the terminal may perform one or more of the following operations.
  • the UE may include an AS contact including one or more of a current RRC connection, a current security context, a PDCP state including an ROHC state, a C-RNTI used in the source PCell, a physical cell identifier and a cellIdentity of the source PCell. Keep the strings.
  • AS context that includes one or more of a current RRC connection, a current security context, a PDCP state that includes a ROHC state, a C-RNTI used in the source PCell, a physical cell identifier and a cellIdentity of the source PCell. Suspend.
  • the terminal stores / maintains the resume identifier / terminal identifier / base station identifier and terminal identifier (which may be referred to as a resume identifier below for convenience of description).
  • the UE suspends all SRB (s) and DRB (s).
  • the terminal for example, T310 or T312 If the terminal (for example, T310 or T312) is running, it stops.
  • the terminal resets the MAC.
  • the terminal starts synchronization in the downlink of the target cell.
  • the terminal may select the target cell based on the neighbor cell information satisfying the above-described cell change criteria.
  • the terminal acquires MIB information from the target cell. Or, the terminal acquires RRC connection cell change request related system information (eg, RA-preamble, etc.) in the target cell. As another method, the UE may receive RRC connection cell change request related information (eg, RA-preamble, etc.) of the neighbor cell in the source cell through system information or dedicated information.
  • RRC connection cell change request related information eg, RA-preamble, etc.
  • the terminal applies a default physical channel configuration.
  • the terminal applies the default MAC main configuration.
  • the terminal applies the (default) CCCH configuration (specified in section TS.1.23.331).
  • the terminal starts the associated timer (eg T300).
  • the terminal transmits an RRC connection cell change request message to the base station.
  • the resume identifier / terminal identifier is set to a resumeIdentity / terminal identifier indicated by the source base station.
  • short-resume-MAC-I sets to 16 least significant bits of the calculated MAC-I.
  • ResumeCause is set to cell change (or mobility support or handover).
  • the terminal may ignore this.
  • the access barring check for the general terminal may not be performed.
  • the target base station transmits an RRC connection cell change message to the terminal.
  • the UE that receives the RRC connection cell change message operates as follows, for example.
  • the terminal stops the associated timer (for example, T300).
  • the terminal resumes the RRC connection.
  • the terminal resumes the security context.
  • the terminal resets the RLC entity for all SRBs and DRBs.
  • the terminal resets PDCP entities for all SRBs and DRBs.
  • the terminal discards the resume identifier (resumeIdentity).
  • the terminal performs radio resource configuration according to the received radio resource configuration dedicated information.
  • the UE resumes all SRBs and DRBs.
  • the UE updates the K eNB key based on the K ASME key to which the current K eNB is associated using the NCC value indicated in the RRC connection cell change message.
  • the terminal derives K RRCint associated with the previously configured integrity algorithm.
  • the terminal requests the lower layer to verify the integrity protection of the RRC connection resume message by using the previously configured algorithm and K RRCint .
  • the terminal derives K RRCint and K UPenc associated with the previously configured ciphering algorithm.
  • the terminal is configured to activate integrity protection in the lower layer by using the previously configured algorithm and K RRCint .
  • the terminal is configured to apply a ciphering algorithm, K RRCint , K UPenc to the lower layer.
  • the terminal considers the current cell as a PCell.
  • the terminal transmits an RRC connection cell change complete message to the target base station.
  • the target base station receiving the aforementioned RRC connection cell change message fails for some reason (for example, fails to retrieve the terminal context from the source base station, the target base station is not ready for handover due to insufficient terminal context, etc.) Failure to change the connection cell or may be directed to the RRC connection configuration instructions to the terminal.
  • the target base station receiving the aforementioned RRC connection cell change message may transmit an RRC connection setup message to the UE without transmitting the RRC connection cell change success message (RRC connection cell change message) for any reason. .
  • the terminal may perform one or more of the following operations.
  • the terminal deletes / removes / discards the terminal AS context and the resume identifier.
  • the UE requests the upper layer for necessary information (eg, S-TMSI) to set up / receive / receive / set up the terminal context from the MME.
  • the terminal sets the s-TMSI to the value received from the upper layer in the RRC Connection setup complete message.
  • the UE may include the message / information received from the upper layer in the RRC Connection setup complete message.
  • the re-identifier of the terminal since the re-identifier of the terminal is configured for the RRC connection suspend, it could be provided included only on the RRC connection release message. That is, when the cause of the release of the RRC connection suspend on the RRC connection release message, including the re-identifier was instructed to the terminal.
  • the re-identifier may be configured in advance to the terminal through the RRC connection reconfiguration message.
  • FIG. 4 is a diagram illustrating a cell change procedure of a connected state terminal according to an embodiment.
  • the base stations 410 and 420 recognize that the terminal 400 is the terminal 400 capable of changing the cell through the terminal capability information. As another example, the base stations 410 and 420 may indicate that the cell change is supported in the cell through system information.
  • the information indicating that the cell change is provided through the system information indicates the RRC message transmission allowance for the NB-IoT UE supporting only the control plane CIoT EPS optimization.
  • the information indicating that the cell change is provided through the system information may allow the UE to transmit the RRC message triggered by the UE to the NB-IoT UE supporting both the control plane CIoT EPS optimization and the user plane CIoT EPS optimization. Indicates information to be indicated.
  • the source base station 410 instructs the terminal 400 of the cell change criteria / rule / threshold value / event of the connected state terminal (S400).
  • the cell change criteria / rule / threshold / event may be included in the RRC connection reconfiguration message.
  • the cell change criterion / rule / threshold / event may be included in the RRC connection setup message for the UE using the control plane CIoT EPS optimization.
  • the cell change criterion / rule / threshold / event may be a parameter related to a radio link failure (RLF) timer configured to be UE-specifically configured by the base station.
  • RLF radio link failure
  • the cell change criteria / rule / threshold / event may be an RLF timer and related parameters broadcasted by the base station through system information.
  • the cell change criteria / rule / threshold / event may be an RLF timer and related parameters broadcast by the base station through system information.
  • the terminal 400 may initiate the above-described cell change procedure when the cell change criterion / rule / threshold value / event of the connection state terminal indicated by the base station 410 is exceeded / reached / satisfied (S405). For example, when the radio link failure criterion is reached, a cell change procedure triggered by the aforementioned terminal can be initiated.
  • the terminal 400 transmits an RRC message for cell change to the target base station 420 (S410).
  • the target base station 420 requests the terminal context to the source base station 410 (S415). As another example, the target base station 420 requests the terminal context to the MME 430.
  • the source base station 410 responds to this (S420).
  • Data forwarding may be performed (S425).
  • the target base station 420 transmits an RRC message for configuring the RRC cell change to the terminal 400 (S430).
  • the above-described RRC message may be an RRC connection reconfiguration message.
  • the above-described RRC message may be an RRC message distinguished from an RRC connection reconfiguration message.
  • the terminal 400 transmits a confirmation message to the target base station 420 (S435).
  • the target base station 420 sends a path switch request message to the MME 430 (S440).
  • the MME 430 responds to this (S445).
  • the target base station 420 instructs the source base station 410 to release the terminal context (S450).
  • the steps S415 to S425 may be performed simultaneously with the steps S430 to S435 or after the steps S430 to S435.
  • the source base station 410 may continue to retransmit without knowing this and may waste radio resources or cause interference.
  • the terminal 400 may transmit the indication information about the target base station cell change attempt or the target base station cell change threshold reached to the source base station 410.
  • the conveyed information may use an RRC message or MAC CE or PHY signaling for fast transmission.
  • the present disclosure has an effect of improving service continuity for an NB-IoT terminal in a connected state.
  • the foregoing has described an RRC suspend method, a low power mobility support embodiment, and an example of a cell change procedure for reducing power consumption of an NB-IoT terminal.
  • First Example target Method for requesting UE context for UE reconfiguration / change / reconfiguration from base station to MME.
  • the target base station If the terminal transmits an RRC message requesting the cell change to the target base station in order to attempt cell change directly, the target base station receiving the message configures, reconfigures, resumes, and changes the RRC connection for the cell change requesting UE. You can do a reset.
  • the target base station may request a terminal context to a core network entity (MME, which is a core network control plane entity in case of LTE), in order to perform connection configuration / reconfiguration / resume / change for the terminal.
  • MME core network entity
  • the terminal may include an S-TMSI capable of identifying the serving MME by the terminal identifier in the RRC message requesting the cell change to the target base station.
  • S-TMSI is composed of the MMEC and m-TMSI can identify the serving MME of the terminal.
  • the message for requesting the terminal context from the target base station to the MME may be one of the S1 messages.
  • the message for requesting the UE context to the MME may be one of an E-RAB setup / modify / release request / response message, an initial context setup / modification request / response message, and an eNB Status Transfer message. .
  • the message for requesting the UE context to the MME may be a UE context release request message.
  • the message for requesting the terminal context from the target base station to the MME may be a Handover Required message.
  • the message for requesting the terminal context from the target base station to the MME may be a Handover Notify message.
  • the target base station may inform the MME of the cell change request of the terminal.
  • the message for requesting the terminal context from the target base station to the MME may be a path switch request message.
  • the message for requesting the terminal context from the target base station to the MME may be a terminal context resume request message.
  • the message for requesting the terminal context from the target base station to the MME may be a new S1 message distinguished from the above-described message.
  • the above-described message for requesting the terminal context by the target base station to the MME includes S-TMSI information for identifying the terminal in the MME, NAS authentication code information for confirming the message authentication of the terminal in the MME (NAS MAC: Non Access Stratum Message Authentication Code) and information to reduce data transmission interruption.
  • S-TMSI information for identifying the terminal in the MME
  • NAS authentication code information for confirming the message authentication of the terminal in the MME
  • NAS MAC Non Access Stratum Message Authentication Code
  • information to reduce data transmission interruption For example, it may include information for requesting uplink PDCP SN and HFN reception status and / or downlink PDCP SN and HFN transmission status transmission from a source base station.
  • the terminal context resume message is the uplink PDCP SN and HFN reception status and / or downlink PDCP from the source base station It may include information for requesting transmission of the SN and HFN transmission status.
  • the UE context resume message is a message for instructing the MME to resume a suspended RRC connection, so if the target base station uses this message to request an UE context to the MME for an RRC connected UE, the MME suspended RRC connection It may include information indicating whether to instruct to resume.
  • the MME may transfer this information to the source base station.
  • the source base station receives this information, it can send uplink PDCP SN and HFN reception status and / or downlink PDCP SN and HFN transmission status information to the MME.
  • the MME may again transmit uplink PDCP SN and HFN reception status and / or downlink PDCP SN and HFN transmission status information to the target base station.
  • the MME may transmit the terminal context of the corresponding terminal to the target base station.
  • the MME may receive the terminal context information of the terminal through the source base station (retrieve) and deliver it to the target base station.
  • the source base station When the source base station receives a message requesting a terminal context to be delivered from the MME to the target base station, or the source base station transmits an uplink PDCP SN and HFN reception state and / or a downlink PDCP SN and HFN transmission state to be transmitted from the MME to the target base station.
  • the source base station may start data forwarding to the target base station through an uplink / downlink tunnel with the target base station. .
  • a message in which the target base station requests the terminal context to the MME and / or a message instructed by the MME to the source base station according to the message that the target base station requests the terminal context to the MME may include uplink forwarding proposal / instruction information and downlink.
  • the aforementioned uplink PDCP SN and HFN reception status and / or downlink PDCP SN and HFN transmission status information may be information distinguished for each bearer.
  • the uplink GTP tunnel endpoint information for data forwarding and the downlink GTP tunnel endpoint information for data forwarding may be information distinguished for each bearer.
  • Second Embodiment A method for requesting a terminal context from a target base station to a source base station.
  • the target base station If the terminal transmits an RRC message requesting the cell change to the target base station in order to attempt cell change directly, the target base station receiving the message configures, reconfigures, resumes, and changes the RRC connection for the cell change requesting UE. You can do a reset.
  • the target base station may request the terminal context to the source base station to perform the connection configuration / reconfiguration / resume / change to the cell request terminal for the terminal.
  • the terminal may include the terminal identification information including the base station identification information in the RRC message requesting the cell change to the target base station as the terminal identifier.
  • the Resume ID may be used as a terminal identifier.
  • Resume ID is composed of the base station identification information of the source base station and the terminal identification information assigned by the source base station can identify the source base station of the terminal.
  • the source base station identification information and the C-RNTI information allocated by the source base station may be used as the terminal identifier.
  • the source cell identification information and the C-RNTI information allocated by the source base station may be used as the terminal identifier.
  • one or more of source cell identification information, source base station identification information, C-RNTI information allocated by the source base station, and shorMAC-I may be used as a terminal identifier.
  • the message for requesting the terminal context from the target base station to the source base station may be one of the X2 messages.
  • the message for requesting the terminal context from the target base station to the source base station may be a Retrieve UE context request message.
  • the message for requesting the terminal context from the target base station to the source base station may be a UE context release message.
  • the message for requesting the terminal context from the target base station to the source base station may be a Handover Report message.
  • the message for requesting the terminal context from the target base station to the source base station may be a new X2 message distinguished from the above-described message.
  • the above-described message for requesting the terminal context from the target base station to the source base station includes C-RNTI information for identifying the terminal from the source base station and AS authentication for confirming the message authentication of the terminal from the source base station. It may include code information (AS MAC: Access Stratum Message Authentication Code) and information for reducing data transmission interruption. For example, it may include information for requesting uplink PDCP SN and HFN reception status and / or downlink PDCP SN and HFN transmission status transmission from a source base station.
  • AS MAC Access Stratum Message Authentication Code
  • the retrieve UE context request message is the uplink PDCP SN and HFN reception status and / or downlink from the source base station It may include information for requesting transmission of PDCP SN and HFN transmission status.
  • the Retrieve UE context request message is a message for receiving the terminal context from the previous base station to which the RRC connection is suspended and transmitting it to a new base station requested to resume the RRC connection, if this message is the target base station for the RRC connected terminal. If used to request a terminal context from the source base station, the terminal may receive information from the suspended base station (retrieve) and may include information indicating whether the RRC connection is to resume.
  • the source base station receives information requesting uplink PDCP SN and HFN transmission status and / or downlink PDCP SN and HFN transmission status transmission from the target base station, the source base station receives the uplink PDCP SN and HFN reception status and / or downlink. Link PDCP SN and HFN transmission status information can be transmitted.
  • the source base station When the source base station receives the message for requesting the terminal context from the target base station, the source base station may transmit the terminal context of the terminal to the target base station.
  • the source base station When the source base station receives a message requesting a terminal context to be delivered to the target base station, or the source base station receives information from the target base station requesting transmission of uplink PDCP SN and HFN and / or downlink PDCP SN and HFN transmission status. Upon receipt (or upon receipt of information by the source base station suggesting / instructing data forwarding from the target base station), the source base station may begin data forwarding to the target base station via an uplink / downlink tunnel with the target base station.
  • a message requesting a terminal context from a target base station to a source base station includes uplink forwarding proposal / instruction information, downlink forwarding proposal / instruction information, forwarding proposal / instruction information, uplink GTP tunnel endpoint information for data forwarding, One or more of downlink GTP tunnel endpoint information for data forwarding may be included.
  • the aforementioned uplink PDCP SN and HFN reception status and / or downlink PDCP SN and HFN transmission status information may be information distinguished for each bearer.
  • the uplink GTP tunnel endpoint information for data forwarding and the downlink GTP tunnel endpoint information for data forwarding may be information distinguished for each bearer.
  • Third embodiment Method of requesting UE context from target base station to anchor base station.
  • a specific base station maintaining a terminal context may be defined as an anchor base station.
  • the target base station may request data transmission to the anchor base station.
  • the target base station If the terminal transmits an RRC message requesting the cell change to the target base station in order to attempt cell change directly, the target base station receiving the message configures, reconfigures, resumes, and changes the RRC connection for the cell change requesting UE. You can do a reset.
  • the target base station may request the terminal context to the anchor base station to perform the connection configuration / reconfiguration / resume / change for the cell change request terminal for the terminal.
  • the terminal may include terminal identification information including anchor base station identification information as a terminal identifier in an RRC message requesting a cell change to the target base station.
  • the Resume ID may be used as a terminal identifier.
  • Resume ID is composed of the base station identification information of the anchor base station and the terminal identification information assigned by the anchor base station can identify the anchor base station of the terminal.
  • the anchor base station identification information and the C-RNTI information allocated by the source base station may be used as the terminal identifier.
  • the source cell identification information and the C-RNTI information allocated by the anchor base station may be used as the terminal identifier.
  • one or more of source cell identification information, anchor base station identification information, C-RNTI information allocated by the source base station, and shorMAC-I may be used as a terminal identifier.
  • the message for requesting the terminal context from the target base station to the anchor base station may be one of the X2 messages.
  • the message for requesting the terminal context from the target base station to the anchor base station may be a Retrieve UE context request message.
  • the message for requesting the terminal context from the target base station to the anchor base station may be a UE context release message.
  • the message for requesting the terminal context from the target base station to the anchor base station may be a Handover Report message.
  • the message for requesting the terminal context from the target base station to the anchor base station may be a new X2 message distinguished from the above-described message.
  • the message for requesting the terminal context from the target base station to the anchor base station includes Resume ID information for identifying the terminal from the anchor base station, and an AS authentication code for confirming the message authentication of the terminal from the anchor base station.
  • Information (AS MAC: Access Stratum Message Authentication Code) and information for reducing data transmission interruption. For example, it may include information for requesting uplink PDCP SN and HFN reception status and / or downlink PDCP SN and HFN transmission status transmission from a source base station.
  • the anchor base station may transfer this information to the source base station.
  • the source base station can transmit the uplink PDCP SN and HFN reception status and / or downlink PDCP SN and HFN transmission status information to the anchor base station.
  • the anchor base station may again transmit the uplink PDCP SN and HFN reception status and / or downlink PDCP SN and HFN transmission status information to the target base station.
  • the anchor base station may transmit the terminal context of the corresponding terminal to the target base station.
  • the anchor base station may receive the terminal context information of the corresponding terminal through the source base station (retrieve) and deliver it to the target base station.
  • the source base station When the source base station receives a message requesting a terminal context to be delivered from the anchor base station to the target base station, or the source base station receives an uplink PDCP SN and HFN reception state and / or downlink PDCP SN and HFN to be delivered from the anchor base station to the target base station.
  • the source base station When receiving the information requesting the status transmission (or when the source base station receives information suggesting / instructing data forwarding from the anchor base station), the source base station transmits data to the target base station through an uplink / downlink tunnel with the target base station. You can start forwarding.
  • the message indicated by the anchor base station to the source base station according to the message for requesting the terminal context from the target base station to the anchor base station and / or the message from the target base station to the terminal base station to the anchor base station may include uplink forwarding proposal / instruction information. It may include one or more of information, downlink forwarding proposal / indication information, forwarding proposal / indication information, uplink GTP tunnel endpoint information for data forwarding, downlink GTP tunnel endpoint information for data forwarding.
  • the aforementioned uplink PDCP SN and HFN reception status and / or downlink PDCP SN and HFN transmission status information may be information distinguished for each bearer.
  • the uplink GTP tunnel endpoint information for data forwarding and the downlink GTP tunnel endpoint information for data forwarding may be information distinguished for each bearer.
  • the aforementioned methods are NB-IoT terminals supporting only control plane CIoT EPS optimization, NB-IoT supporting both control plane CIoT EPS optimization and user plane CIoT EPS optimization.
  • the present disclosure has an effect of performing a cell change or a base station change while reducing a data transmission interruption time due to a cell change or a base station change.
  • FIG. 5 is a diagram illustrating a terminal configuration according to an embodiment.
  • the NB-IoT (NB-IoT) terminal 500 performing mobility processing may transmit an RRC connection reconfiguration request message to a base station and a RRC from a base station when a predetermined event occurs.
  • the receiver 530 may receive a connection reset message and a controller 510 may resume signaling radio bearer based on the RRC connection reset message.
  • the controller 510 may determine whether a preset event condition is satisfied, and when the corresponding event condition is satisfied, the transmitter 520 may transmit an RRC connection re-establishment request message to the base station.
  • the preset event may mean any one of radio link failure detection and handover failure detection of the NB-IoT terminal.
  • the preset event may be set under a plurality of conditions. For example, when the NB-IoT UE is configured to support the control plane CIoT EPS optimization and receives the RRC connection reset permission indication information of the NB-IoT UE transmitted by the base station without AS security activated.
  • the controller 510 may determine that a preset event is satisfied.
  • the RRC connection reconfiguration request message may include terminal identifier information set to SAE-Temporary Mobile Subscriber Identity (S-TMSI).
  • S-TMSI SAE-Temporary Mobile Subscriber Identity
  • the base station can query the terminal context by using the terminal identifier information received from the NB-IoT terminal.
  • the terminal context may be confirmed by using the MME or may be confirmed by contents stored in the base station.
  • the base station receiving the RRC connection reconfiguration request message is the target base station, the base station may query the terminal context for inquiry and confirm the request.
  • the RRC connection reset request message may include a message authentication code.
  • the message authentication code may include NAS MAC information.
  • the RRC connection reset message may also include message authentication code information.
  • the message authentication code may include NAS MAC information.
  • the RRC connection reconfiguration message may include information for controlling to resume signaling radio bearer of the NB-IoT terminal.
  • the control unit 510 receiving the RRC connection reconfiguration message from the base station may resume the signaling radio bearer.
  • the NB-IoT terminal supporting the control plane CIoT EPS optimization may transmit and receive a small amount of data through the signaling radio bearer as described above. Accordingly, the NB-IoT terminal may maintain the data communication by minimizing service interruption by resuming the signaling radio bearer.
  • the transmitter 520 may transmit a terminal capability indicating that the control plane CIoT Cellular IoT Evolved Packet System (EPS) Optimization is supported.
  • the transmitter 520 may transmit information indicating that the NB-IoT terminal 500 can support the control plane CIoT EPS optimization operation to the base station in advance so that the base station recognizes it.
  • the terminal capability information may be transmitted during initial setup of the NB-IoT terminal 500 and the base station.
  • the receiving unit 530 may receive information indicating the permission of the mobility processing of the NB-IoT terminal 500 from the base station through the system information.
  • the base station may transmit information indicating that the signaling radio bearer resumes operation through RRC connection reconfiguration.
  • the controller 510 may check information indicating that the signaling radio bearer resume operation is received through the system information, and may control the transmitter 520 to transmit an RRC connection reset request message to the base station.
  • the receiver 530 receives downlink control information, data, and a message from a base station through a corresponding channel.
  • the controller 5100 controls the overall operation of the terminal 500 to improve service continuity for the NB-IoT terminal 500 required to perform the above-described embodiments.
  • the transmitter 520 transmits uplink control information, data, and messages to the base station through the corresponding channel.
  • the NB-IoT terminal described above may be a terminal configured to support Control Plane CIoT Cellular IoT Evolved Packet System (EPS) Optimization.
  • EPS Control Plane CIoT Cellular IoT Evolved Packet System
  • the NB-IoT terminal does not configure a data radio bearer, it may mean a terminal that performs data transmission and reception in a state that AS security is not activated.
  • the above-described base station may be a source base station or a target base station.
  • FIG. 6 is a diagram illustrating a configuration of a base station according to an embodiment.
  • the base station 600 performing mobility processing of a NB-IoT terminal receives an RRC connection reset request message from an NB-IoT terminal and an RRC connection reset request.
  • the control unit 610 may check the terminal context of the NB-IoT terminal based on the message, and the transmitter 620 may transmit an RRC connection reestablishment message for resuming the signaling radio bearer of the NB-IoT terminal.
  • the RRC connection reconfiguration request message may be received in a radio link failure detection and handover failure situation of the NB-IoT terminal.
  • the RRC connection reset request message is configured to allow the NB-IoT terminal to support the control plane CIoT EPS optimization, and the RRC connection reset allowance indication information of the NB-IoT terminal transmitted by the base station while the AS security is not activated.
  • reception if a plurality of conditions for generating a radio link failure detection or a handover failure detection are satisfied, it may be received.
  • the RRC connection reconfiguration request message may include terminal identifier information set to SAE-Temporary Mobile Subscriber Identity (S-TMSI).
  • the RRC connection reset request message may include a message authentication code.
  • the message authentication code may include NAS MAC information.
  • the controller 610 may query the terminal context using the terminal identifier information included in the RRC connection reset request message.
  • the terminal context may be confirmed by using the MME or may be confirmed by contents stored in the base station.
  • the base station receiving the RRC connection reconfiguration request message is the target base station, the base station may query the terminal context for inquiry and confirm the request.
  • the RRC connection reconfiguration message may include information for controlling to resume signaling radio bearer of the NB-IoT terminal.
  • the NB-IoT terminal supporting the control plane CIoT EPS optimization may transmit and receive a small amount of data through the signaling radio bearer as described above. Accordingly, the NB-IoT terminal may maintain the data communication by minimizing service interruption by resuming the signaling radio bearer.
  • the receiver 630 may receive a terminal capability indicating that the control plane CIoT Cellular IoT Evolved Packet System (EPS) Optimization is supported.
  • the terminal capability may be received during an initial setup process of the NB-IoT terminal and the base station, and the controller 610 performs mobility processing through the RRC connection reconfiguration operation by the NB-IoT terminal through the terminal capability (eg, SRB Resume).
  • the terminal capability eg, SRB Resume
  • the transmitter 620 may transmit information indicating that the base station allows mobility processing of the NB-IoT terminal through system information.
  • the transmitter 620 may transmit information indicating that the signaling radio bearer of the NB-IoT terminal is allowed to resume operation (mobility processing) through RRC connection reconfiguration.
  • the NB-IoT terminal checks information indicating that the signaling radio bearer is allowed to resume operation received through system information, and transmits an RRC connection reconfiguration request message to the base station 600, thereby performing a mobility processing procedure.
  • the NB-IoT terminal described above may be a terminal configured to support Control Plane CIoT Cellular IoT Evolved Packet System (EPS) Optimization.
  • EPS Control Plane CIoT Cellular IoT Evolved Packet System
  • the NB-IoT terminal does not configure a data radio bearer, it may mean a terminal that performs data transmission and reception in a state that AS security is not activated.
  • the above-described base station may be a source base station or a target base station.
  • controller 610 controls the overall operation of the base station 600 according to improving service continuity for the NB-IoT terminal required to perform the above-described embodiments.
  • the transmitter 620 and the receiver 630 are used to transmit and receive signals, messages, and data necessary for performing the above-described embodiments.

Landscapes

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

Abstract

La présente invention porte sur un procédé pour effectuer un processus de mobilité d'un terminal de l'Internet des objets à bande étroite (NB-IoT, "narrowband Internet of things") et sur un appareil pour celui-ci et, plus particulièrement, sur un procédé pour maintenir la continuité de service d'un terminal NB-IoT et un appareil associé. Dans un mode de réalisation, l'invention porte sur un procédé pour un terminal NB-IoT, pour effectuer un processus de mobilité, et sur un appareil associé, le procédé comprenant les étapes consistant à : transmettre un message de demande de rétablissement de connexion RRC à une station de base lorsqu'un événement préétabli se produit; recevoir un message de rétablissement de connexion RRC en provenance de la station de base; et reprendre un support radio de signalisation sur la base du message de rétablissement de connexion RRC.
PCT/KR2017/007831 2016-07-21 2017-07-20 Procédé de réalisation d'un processus de mobilité du terminal nb-iot et appareil associé Ceased WO2018016895A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US16/319,043 US10813028B2 (en) 2016-07-21 2017-07-20 Method for performing mobility process of NB-IoT terminal, and apparatus therefor
CN201780043220.4A CN109479230B (zh) 2016-07-21 2017-07-20 用于执行NB-IoT终端的移动性处理的方法及其装置

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
KR10-2016-0092771 2016-07-21
KR20160092771 2016-07-21
KR10-2016-0092742 2016-07-21
KR20160092742 2016-07-21
KR10-2017-0091825 2017-07-20
KR1020170091825A KR101960177B1 (ko) 2016-07-21 2017-07-20 NB-IoT 단말의 이동성 처리 수행 방법 및 그 장치

Publications (1)

Publication Number Publication Date
WO2018016895A1 true WO2018016895A1 (fr) 2018-01-25

Family

ID=60992281

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2017/007831 Ceased WO2018016895A1 (fr) 2016-07-21 2017-07-20 Procédé de réalisation d'un processus de mobilité du terminal nb-iot et appareil associé

Country Status (1)

Country Link
WO (1) WO2018016895A1 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3340688A1 (fr) * 2016-08-09 2018-06-27 HTC Corporation Dispositif et procédé de gestion de communication de l'internet des objets à bande étroite
CN110636578A (zh) * 2018-06-21 2019-12-31 中兴通讯股份有限公司 一种请求系统消息的方法、装置、存储介质及终端
CN112218285A (zh) * 2019-07-11 2021-01-12 华为技术有限公司 上行用户数据传输的方法、设备及系统
CN113940105A (zh) * 2019-06-13 2022-01-14 苹果公司 用于在未激活安全时重新建立5g-nr rrc连接的方法
CN115134949A (zh) * 2021-03-26 2022-09-30 大唐移动通信设备有限公司 信息发送方法、装置、设备以及存储介质
CN116158189A (zh) * 2021-09-23 2023-05-23 苹果公司 快速无线电链路故障恢复
WO2025090102A1 (fr) * 2023-10-26 2025-05-01 Rakuten Symphony, Inc. Recherche efficace de contexte d'ue pendant une procédure de reprise de station de base

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140023032A1 (en) * 2011-04-11 2014-01-23 Samsung Electronics Co., Ltd. Method and apparatus for efficiently transmitting information acquired by a terminal to a base station
US20160066312A1 (en) * 2014-08-28 2016-03-03 Telefonaktiebolaget L M Ericsson (Publ) Methods receiving radiation pattern information and related network nodes and base stations

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140023032A1 (en) * 2011-04-11 2014-01-23 Samsung Electronics Co., Ltd. Method and apparatus for efficiently transmitting information acquired by a terminal to a base station
US20160066312A1 (en) * 2014-08-28 2016-03-03 Telefonaktiebolaget L M Ericsson (Publ) Methods receiving radiation pattern information and related network nodes and base stations

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3GPP; TSG SA; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access (Release 14", 3GPP TS 23.401 V14.0.0, 22 June 2016 (2016-06-22), XP055602606, Retrieved from the Internet <URL:https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=849> *
LG ELECTRONICS: "Clarification of new active flag handling for CP CIoT EPS Optimizaition", SA WG2 MEETING #116, 5 July 2016 (2016-07-05), Vienna, Austria, pages 2 - 163514, XP051121207, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_116_Vienna/Docs> *
NEC: "Key Issue CN overload protection from data transfer via control plane CIoT EPS optimizations - solution 1", SA WG2 MEETING #116 163484, 5 July 2016 (2016-07-05), Vienna , Austria, pages 2, XP051121185, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_116_Vienna/Docs> *

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3340688A1 (fr) * 2016-08-09 2018-06-27 HTC Corporation Dispositif et procédé de gestion de communication de l'internet des objets à bande étroite
US10314045B2 (en) 2016-08-09 2019-06-04 Htc Corporation Device and method of handling narrowband internet of things communication
US10863514B2 (en) 2016-08-09 2020-12-08 Htc Corporation Device and method of handling narrowband internet of things communication
CN110636578A (zh) * 2018-06-21 2019-12-31 中兴通讯股份有限公司 一种请求系统消息的方法、装置、存储介质及终端
CN110636578B (zh) * 2018-06-21 2023-10-31 中兴通讯股份有限公司 一种请求系统消息的方法、装置、存储介质及终端
CN113940105A (zh) * 2019-06-13 2022-01-14 苹果公司 用于在未激活安全时重新建立5g-nr rrc连接的方法
CN112218285A (zh) * 2019-07-11 2021-01-12 华为技术有限公司 上行用户数据传输的方法、设备及系统
CN115134949A (zh) * 2021-03-26 2022-09-30 大唐移动通信设备有限公司 信息发送方法、装置、设备以及存储介质
CN116158189A (zh) * 2021-09-23 2023-05-23 苹果公司 快速无线电链路故障恢复
WO2025090102A1 (fr) * 2023-10-26 2025-05-01 Rakuten Symphony, Inc. Recherche efficace de contexte d'ue pendant une procédure de reprise de station de base

Similar Documents

Publication Publication Date Title
WO2020204501A1 (fr) Procédé de prise en charge d&#39;accès à un réseau fermé, ue, station de base et support d&#39;enregistrement lisible
WO2019160342A1 (fr) Procédé et appareil prenant en charge une mobilité sans rach utilisant des faisceaux préalablement attribués dans un système de communication sans fil
WO2017126919A1 (fr) Procédé de traitement d&#39;échec de liaison radio et appareil associé
WO2016175603A1 (fr) Procédé et appareil de commande de la communication d&#39;un terminal portable dans un système de communication sans fil
WO2018016895A1 (fr) Procédé de réalisation d&#39;un processus de mobilité du terminal nb-iot et appareil associé
WO2019194518A1 (fr) Procédé de création d&#39;entrée de mesure journalisée, et dispositif prenant en charge le procédé
WO2015115843A1 (fr) Procédé et appareil de maintenance et de libération de ressouces d&#39;équipements utilisateurs
WO2018194326A1 (fr) Procédé de réalisation d&#39;un transfert basé sur un terminal et dispositif correspondant
EP3420754A1 (fr) Procédé et équipement de noeud b évolué (enb) pour prendre en charge un transfert intercellulaire continu
EP3443805A1 (fr) Procédé et appareil de commande de connexion légère
WO2015064972A1 (fr) Procédé et appareil de configuration de connexion double dans un réseau de communication mobile
WO2018117313A1 (fr) Procédé de commande de liaison sans fil et de connexion sans fil de terminal dans un système de communication sans fil, et appareil prenant en charge ledit procédé
WO2017039042A1 (fr) Procédé et dispositif de transmission/réception de données de terminal dans un système de communication sans fil
WO2015020475A1 (fr) Appareil et procédé d&#39;exécution d&#39;opération de commutation entre une macro cellule et une petite cellule dans un système de communications mobiles
WO2019031941A1 (fr) Procédé permettant de prendre en charge un transfert intercellulaire et appareil correspondant
WO2017196161A1 (fr) Procédé et appareil de commande de connexion légère
WO2016163851A1 (fr) Procédé mis en œuvre par un terminal pour la détermination d&#39;une priorité de transmission dans un système de communication sans fil et terminal utilisant ledit procédé
WO2019177397A1 (fr) Procédé et appareil permettant d&#39;établir support radio
WO2018164499A1 (fr) Procédé de transmission de rapport d&#39;état de tampon, et dispositif associé
WO2018056718A1 (fr) Procédé et appareil pour changer un état de connexion d&#39;un terminal
WO2013172638A1 (fr) Procédé et appareil pour le traitement d&#39;information d&#39;état dans un système de communication
WO2015152554A1 (fr) Procédé de commande de fonctionnement de cellule secondaire d&#39;un terminal, et appareil associé
WO2025023739A1 (fr) Gestion de transfert conditionnel avec un scg candidat dans un réseau de communication sans fil
WO2014163419A1 (fr) Procédé de traitement d&#39;échec de liaison radio et dispositif associé
WO2014148746A1 (fr) Procédé et appareil pour la transmission de données en faible quantité

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 155A DATED 17.05.2019)

122 Ep: pct application non-entry in european phase

Ref document number: 17831368

Country of ref document: EP

Kind code of ref document: A1