WO2017116115A1 - 사용자 데이터의 전송을 위한 베어러를 설정하는 방법 및 장치 - Google Patents
사용자 데이터의 전송을 위한 베어러를 설정하는 방법 및 장치 Download PDFInfo
- Publication number
- WO2017116115A1 WO2017116115A1 PCT/KR2016/015328 KR2016015328W WO2017116115A1 WO 2017116115 A1 WO2017116115 A1 WO 2017116115A1 KR 2016015328 W KR2016015328 W KR 2016015328W WO 2017116115 A1 WO2017116115 A1 WO 2017116115A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- terminal
- message
- resume
- mme
- request message
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0226—Traffic management, e.g. flow control or congestion control based on location or mobility
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/19—Connection re-establishment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/27—Transitions between radio resource control [RRC] states
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/08—Access point devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/06—Registration at serving network Location Register, VLR or user mobility server
Definitions
- the present invention relates to a wireless communication system, and more particularly, in a wireless communication system, a base station sets up a bearer for transmission of user data in a user plane based cellular internet of things (CIoT). It relates to a method and a device supporting the same.
- CCIoT internet of things
- M2M / IoT which connects everything around us through a network, can easily acquire and deliver necessary information anytime, anywhere, and enables various services to be provided and used. It is highlighted.
- M2M originated from sensor and RFID networks mainly targeting local areas, but various wired / wireless networks can be used as the purpose and characteristics of applications gradually increase.
- the mobile communication network has been developed in consideration of the wide range of service areas including mobility of objects, islands and mountains as well as the ocean, ease of operation and maintenance of the network, security for reliable data transmission, and guarantee of service quality.
- MTC Machine Type Communications
- a machine is an entity that does not require human intervention or intervention
- MTC is defined as a form of data communication in which one or more of these machines are included.
- a machine a form of a smart meter or vending machine equipped with a mobile communication module is mentioned, but recently, a smart phone that automatically connects to a network and performs communication without user intervention or intervention according to the user's location or situation.
- a gateway-type MTC device connected to an IEEE 802.15 WPAN-based micro sensor or RFID is also considered.
- the Internet of Things is the future infrastructure and service of future information and communication where all things are connected to the Internet and communicate directly with each other.
- the reason why the Internet of Things is needed is to improve the quality of life and productivity based on a hyper-connected society, but ultimately it is important because it forms the central nervous system for the nation's own infrastructure, and furthermore, for civilization and the earth.
- the Internet of Things is the beginning of a notable big profit model yet, but the future market size of IoT, a new paradigm for the 21st century, is expected to grow more than 10 times compared to the existing cellular telecommunications market.
- the IoT is largely divided into cellular mobile communication based IoT (CIoT) and non-cellular based IoT.
- the UE may transmit an RRC connection resume request message including a TAU request with an active flag.
- the bearer context is not activated because the RRC connection resumption request message does not include 'Bearer Ind'. Therefore, in order for the terminal to transmit UL data, an unnecessary procedure may need to be performed.
- the bearer context is not activated, even if the MME identifies that there is downlink data to be transmitted to the terminal, the downlink data cannot be transmitted to the terminal. Therefore, improved S1 signaling for transmission of user data in user plane based CIoT needs to be proposed.
- a method for setting a bearer for transmission of user data in a user plane based cellular Internet of Things (CIoT) by a base station in a wireless communication system receives a TAU request (Tracking Area Update Request) message from the terminal, transmits an Initial UE Message message including the TAU request message to a mobility management entity (MME), and includes a resume indication (Resume Indication) Receiving a link NAS Transport message from the MME, and transmitting a UE context resume request message to the MME based on the resume indication.
- TAU request Tracking Area Update Request
- MME mobility management entity
- Resume indication Resume Indication
- the TAU request message received from the terminal may be included in the RRC connection resumption request message.
- the RRC connection resumption request message may not include a bearer indication.
- the suspend of the RRC connection may be prohibited by the resume instruction, and transmission of the UE context resume request message may be triggered. If the TAU request message includes an active flag, the resume indication may be received from the MME. If it is identified by the MME that there is downlink data to be transmitted to the terminal, the resume instruction may be received from the MME.
- the base station may further include receiving from the terminal a resume request instruction requesting for the terminal to resume and determining whether resumption of a previously suspended RRC connection is possible based on the resume request instruction.
- the resume request indication may be included in an RRC connection request message.
- the TAU request message received from the terminal may be included in an RRC connection setup complete message.
- the Initial UE Message message may include a resumeable indication indicating whether the base station can resume a previously suspended RRC connection. Transmission of the UE context resume request message may be triggered by the resume instruction. If the TAU request message includes an active flag, the resume indication may be received from the MME. If it is identified by the MME that there is downlink data to be transmitted to the terminal, the resume instruction may be received from the MME.
- the terminal may be in an RRC_IDLE state.
- a base station for setting up a bearer for transmission of user data in a user plane based cellular internet of things (CIoT) in a wireless communication system.
- the base station includes a memory; Transceiver; And a processor connecting the memory and the transceiver, wherein the processor controls the transceiver to receive a TAU request message from a terminal, and the transceiver includes the TAU request message.
- MME mobility management entity
- FIG. 1 shows a structure of an LTE system.
- FIG. 2 shows an air interface protocol of an LTE system for a control plane.
- FIG 3 shows an air interface protocol of an LTE system for a user plane.
- FIG. 5 illustrates a procedure of suspending an RRC connection in a user plane based CIoT.
- FIG. 6 shows a procedure for resuming RRC connection in user plane based CIoT.
- FIG. 8 illustrates an RRC resumption procedure when a TAU request is triggered according to an embodiment of the present invention.
- FIG 9 illustrates an RRC resume procedure when a TAU request is triggered according to an embodiment of the present invention.
- FIG. 10 illustrates an RRC resumption procedure when a TAU request is triggered according to an embodiment of the present invention.
- FIG. 11 illustrates an RRC resume procedure when a TAU request is triggered according to an embodiment of the present invention.
- FIG. 12 is a block diagram illustrating a method for setting a bearer for transmission of user data in a user plane based CIoT according to an embodiment of the present invention.
- FIG. 13 is a block diagram of a wireless communication system in which an embodiment of the present invention is implemented.
- CDMA code division multiple access
- FDMA frequency division multiple access
- TDMA time division multiple access
- OFDMA orthogonal frequency division multiple access
- SC-FDMA single carrier frequency division multiple access
- CDMA may be implemented with a radio technology such as universal terrestrial radio access (UTRA) or CDMA2000.
- TDMA may be implemented with wireless technologies such as global system for mobile communications (GSM) / general packet radio service (GPRS) / enhanced data rates for GSM evolution (EDGE).
- GSM global system for mobile communications
- GPRS general packet radio service
- EDGE enhanced data rates for GSM evolution
- OFDMA may be implemented by wireless technologies such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, evolved UTRA (E-UTRA), and the like.
- IEEE 802.16m is an evolution of IEEE 802.16e and provides backward compatibility with systems based on IEEE 802.16e.
- UTRA is part of a universal mobile telecommunications system (UMTS).
- 3rd generation partnership project (3GPP) long term evolution (LTE) is part of evolved UMTS (E-UMTS) using evolved-UMTS terrestrial radio access (E-UTRA), which employs OFDMA in downlink and SC in uplink -FDMA is adopted.
- LTE-A (advanced) is the evolution of 3GPP LTE.
- FIG. 1 shows a structure of an LTE system.
- Communication networks are widely deployed to provide various communication services such as IMS and Voice over internet protocol (VoIP) over packet data.
- VoIP Voice over internet protocol
- an LTE system structure includes one or more UEs 10, an evolved-UMTS terrestrial radio access network (E-UTRAN), and an evolved packet core (EPC).
- the terminal 10 is a communication device moved by a user.
- the terminal 10 may be fixed or mobile and may be called by other terms such as a mobile station (MS), a user terminal (UT), a subscriber station (SS), and a wireless device.
- MS mobile station
- UT user terminal
- SS subscriber station
- wireless device a wireless device.
- the E-UTRAN may include one or more evolved node-eB (eNB) 20, and a plurality of terminals may exist in one cell.
- the eNB 20 provides an end point of a control plane and a user plane to the terminal.
- the eNB 20 generally refers to a fixed station communicating with the terminal 10, and may be referred to in other terms such as a base station (BS), a base transceiver system (BTS), an access point, and the like.
- BS base station
- BTS base transceiver system
- One eNB 20 may be arranged per cell. There may be one or more cells within the coverage of the eNB 20.
- One cell may be configured to have one of bandwidths such as 1.25, 2.5, 5, 10, and 20 MHz to provide downlink (DL) or uplink (UL) transmission service to various terminals. In this case, different cells may be configured to provide different bandwidths.
- DL means communication from the eNB 20 to the terminal 10
- UL means communication from the terminal 10 to the eNB 20.
- the transmitter may be part of the eNB 20 and the receiver may be part of the terminal 10.
- the transmitter may be part of the terminal 10 and the receiver may be part of the eNB 20.
- the EPC may include a mobility management entity (MME) that serves as a control plane, and a system architecture evolution (SAE) gateway (S-GW) that serves as a user plane.
- MME mobility management entity
- SAE system architecture evolution gateway
- S-GW gateway
- the MME / S-GW 30 may be located at the end of the network and is connected to an external network.
- the MME has information about the access information of the terminal or the capability of the terminal, and this information may be mainly used for mobility management of the terminal.
- S-GW is a gateway having an E-UTRAN as an endpoint.
- the MME / S-GW 30 provides the terminal 10 with the endpoint of the session and the mobility management function.
- the EPC may further include a packet data network (PDN) -gateway (GW).
- PDN-GW is a gateway with PDN as an endpoint.
- the MME includes non-access stratum (NAS) signaling to the eNB 20, NAS signaling security, access stratum (AS) security control, inter CN (node network) signaling for mobility between 3GPP access networks, idle mode terminal reachability ( Control and execution of paging retransmission), tracking area list management (for terminals in idle mode and active mode), P-GW and S-GW selection, MME selection for handover with MME change, 2G or 3G 3GPP access Bearer management, including roaming, authentication, and dedicated bearer settings, SGSN (serving GPRS support node) for handover to the network, public warning system (ETWS) and commercial mobile alarm system (PWS) It provides various functions such as CMAS) and message transmission support.
- NAS non-access stratum
- AS access stratum
- inter CN node network
- MME selection for handover with MME change
- 2G or 3G 3GPP access Bearer management including roaming, authentication, and dedicated bearer settings
- SGSN serving GPRS support no
- S-GW hosts can be based on per-user packet filtering (eg, through deep packet inspection), legal blocking, terminal IP (Internet protocol) address assignment, transport level packing marking in DL, UL / DL service level charging, gating and It provides various functions of class enforcement, DL class enforcement based on APN-AMBR.
- MME / S-GW 30 is simply represented as a "gateway", which may include both MME and S-GW.
- An interface for user traffic transmission or control traffic transmission may be used.
- the terminal 10 and the eNB 20 may be connected by the Uu interface.
- the eNBs 20 may be interconnected by an X2 interface. Neighboring eNBs 20 may have a mesh network structure by the X2 interface.
- the eNBs 20 may be connected with the EPC by the S1 interface.
- the eNBs 20 may be connected to the EPC by the S1-MME interface and may be connected to the S-GW by the S1-U interface.
- the S1 interface supports a many-to-many-relation between eNB 20 and MME / S-GW 30.
- the eNB 20 may select for the gateway 30, routing to the gateway 30 during radio resource control (RRC) activation, scheduling and transmission of paging messages, scheduling channel information (BCH), and the like.
- RRC radio resource control
- BCH scheduling channel information
- the gateway 30 may perform paging initiation, LTE idle state management, user plane encryption, SAE bearer control, and encryption and integrity protection functions of NAS signaling in the EPC.
- FIG. 2 shows an air interface protocol of an LTE system for a control plane.
- 3 shows an air interface protocol of an LTE system for a user plane.
- the layer of the air interface protocol between the UE and the E-UTRAN is based on the lower three layers of the open system interconnection (OSI) model, which is well known in communication systems, and includes L1 (first layer), L2 (second layer), and L3 (third layer). Hierarchical).
- the air interface protocol between the UE and the E-UTRAN may be horizontally divided into a physical layer, a data link layer, and a network layer, and vertically a protocol stack for transmitting control signals.
- Layers of the radio interface protocol may exist in pairs in the UE and the E-UTRAN, which may be responsible for data transmission of the Uu interface.
- the physical layer belongs to L1.
- the physical layer provides an information transmission service to a higher layer through a physical channel.
- the physical layer is connected to a higher layer of a media access control (MAC) layer through a transport channel.
- Physical channels are mapped to transport channels.
- Data may be transmitted between the MAC layer and the physical layer through a transport channel.
- Data between different physical layers, that is, between the physical layer of the transmitter and the physical layer of the receiver may be transmitted using radio resources through a physical channel.
- the physical layer may be modulated using an orthogonal frequency division multiplexing (OFDM) scheme, and utilizes time and frequency as radio resources.
- OFDM orthogonal frequency division multiplexing
- the physical layer uses several physical control channels.
- a physical downlink control channel (PDCCH) reports resource allocation of a paging channel (PCH) and a downlink shared channel (DL-SCH), and hybrid automatic repeat request (HARQ) information related to the DL-SCH to the UE.
- the PDCCH may carry an uplink grant to report to the UE regarding resource allocation of uplink transmission.
- the physical control format indicator channel (PCFICH) informs the UE of the number of OFDM symbols used for the PDCCH and is transmitted every subframe.
- a physical hybrid ARQ indicator channel (PHICH) carries a HARQ ACK (non-acknowledgement) / NACK (non-acknowledgement) signal for UL-SCH transmission.
- a physical uplink control channel (PUCCH) carries UL control information such as HARQ ACK / NACK, a scheduling request, and a CQI for downlink transmission.
- the physical uplink shared channel (PUSCH) carries an uplink shared channel (UL-SCH).
- the physical channel includes a plurality of subframes in the time domain and a plurality of subcarriers in the frequency domain.
- One subframe consists of a plurality of symbols in the time domain.
- One subframe consists of a plurality of resource blocks (RBs).
- One resource block is composed of a plurality of symbols and a plurality of subcarriers.
- each subframe may use specific subcarriers of specific symbols of the corresponding subframe for the PDCCH.
- the first symbol of the subframe may be used for the PDCCH.
- the PDCCH may carry dynamically allocated resources, such as a physical resource block (PRB) and modulation and coding schemes (MCS).
- a transmission time interval (TTI) which is a unit time at which data is transmitted, may be equal to the length of one subframe.
- One subframe may have a length of 1 ms.
- a DL transport channel for transmitting data from a network to a UE includes a broadcast channel (BCH) for transmitting system information, a paging channel (PCH) for transmitting a paging message, and a DL-SCH for transmitting user traffic or control signals. And the like.
- BCH broadcast channel
- PCH paging channel
- DL-SCH supports dynamic link adaptation and dynamic / semi-static resource allocation by varying HARQ, modulation, coding and transmit power.
- the DL-SCH may enable the use of broadcast and beamforming throughout the cell.
- System information carries one or more system information blocks. All system information blocks can be transmitted in the same period. Traffic or control signals of a multimedia broadcast / multicast service (MBMS) are transmitted through a multicast channel (MCH).
- MCH multicast channel
- the UL transport channel for transmitting data from the terminal to the network includes a random access channel (RAC) for transmitting an initial control message, a UL-SCH for transmitting user traffic or a control signal, and the like.
- the UL-SCH can support dynamic link adaptation due to HARQ and transmit power and potential changes in modulation and coding.
- the UL-SCH may enable the use of beamforming.
- RACH is generally used for initial connection to a cell.
- the MAC layer belonging to L2 provides a service to a radio link control (RLC) layer, which is a higher layer, through a logical channel.
- RLC radio link control
- the MAC layer provides a mapping function from a plurality of logical channels to a plurality of transport channels.
- the MAC layer also provides a logical channel multiplexing function by mapping from multiple logical channels to a single transport channel.
- the MAC sublayer provides data transfer services on logical channels.
- the logical channel may be divided into a control channel for information transmission in the control plane and a traffic channel for information transmission in the user plane according to the type of information to be transmitted. That is, a set of logical channel types is defined for other data transfer services provided by the MAC layer.
- the logical channel is located above the transport channel and mapped to the transport channel.
- the control channel is used only for conveying information in the control plane.
- the control channel provided by the MAC layer includes a broadcast control channel (BCCH), a paging control channel (PCCH), a common control channel (CCCH), a multicast control channel (MCCH), and a dedicated control channel (DCCH).
- BCCH is a downlink channel for broadcasting system control information.
- PCCH is a downlink channel used for transmitting paging information and paging a terminal whose cell-level location is not known to the network.
- CCCH is used by the terminal when there is no RRC connection with the network.
- MCCH is a one-to-many downlink channel used to transmit MBMS control information from the network to the terminal.
- DCCH is a one-to-one bidirectional channel used by the terminal for transmitting dedicated control information between the terminal and the network in an RRC connection state.
- the traffic channel is used only for conveying information in the user plane.
- the traffic channel provided by the MAC layer includes a dedicated traffic channel (DTCH) and a multicast traffic channel (MTCH).
- DTCH is used for transmission of user information of one UE in a one-to-one channel and may exist in both uplink and downlink.
- MTCH is a one-to-many downlink channel for transmitting traffic data from the network to the terminal.
- the uplink connection between the logical channel and the transport channel includes a DCCH that can be mapped to the UL-SCH, a DTCH that can be mapped to the UL-SCH, and a CCCH that can be mapped to the UL-SCH.
- the downlink connection between the logical channel and the transport channel is a BCCH that can be mapped to a BCH or DL-SCH, a PCCH that can be mapped to a PCH, a DCCH that can be mapped to a DL-SCH, a DTCH that can be mapped to a DL-SCH, MCCH that can be mapped to MCH and MTCH that can be mapped to MCH.
- the RLC layer belongs to L2.
- the function of the RLC layer includes adjusting the size of the data by segmentation / concatenation of the data received from the upper layer in the radio section such that the lower layer is suitable for transmitting data.
- the RLC layer is divided into three modes: transparent mode (TM), unacknowledged mode (UM) and acknowledged mode (AM). Provides three modes of operation.
- TM transparent mode
- UM unacknowledged mode
- AM acknowledged mode
- AM RLC provides retransmission through automatic repeat request (ARQ) for reliable data transmission.
- ARQ automatic repeat request
- the function of the RLC layer may be implemented as a functional block inside the MAC layer, in which case the RLC layer may not exist.
- the packet data convergence protocol (PDCP) layer belongs to L2.
- the PDCP layer introduces an IP packet, such as IPv4 or IPv6, over a relatively low bandwidth air interface to provide header compression that reduces unnecessary control information so that the transmitted data is transmitted efficiently. Header compression improves transmission efficiency in the wireless section by transmitting only the information necessary for the header of the data.
- the PDCP layer provides security. Security functions include encryption to prevent third party inspection and integrity protection to prevent third party data manipulation.
- the radio resource control (RRC) layer belongs to L3.
- the RRC layer at the bottom of L3 is defined only in the control plane.
- the RRC layer serves to control radio resources between the terminal and the network.
- the UE and the network exchange RRC messages through the RRC layer.
- the RRC layer is responsible for the control of logical channels, transport channels and physical channels in connection with the configuration, re-configuration and release of RBs.
- RB is a logical path provided by L1 and L2 for data transmission between the terminal and the network. That is, RB means a service provided by L2 for data transmission between the UE and the E-UTRAN. Setting up an RB means defining the characteristics of the radio protocol layer and channel to provide a particular service, and determining each specific parameter and method of operation.
- RBs may be classified into two types: signaling RBs (SRBs) and data RBs (DRBs).
- SRBs signaling RBs
- DRBs data RBs
- the non-access stratum (NAS) layer located above the RRC layer performs functions such as session management and mobility management.
- the RLC and MAC layers may perform functions such as scheduling, ARQ and HARQ.
- the RRC layer (ended at the eNB at the network side) may perform functions such as broadcast, paging, RRC connection management, RB control, mobility function, and UE measurement report / control.
- the NAS control protocol (terminated at the gateway's MME at the network side) may perform functions such as SAE bearer management, authentication, LTE_IDLE mobility handling, paging initiation at LTE_IDLE, and security control for signaling between the terminal and the gateway.
- the RLC and MAC layer may perform the same function as the function in the control plane.
- the PDCP layer may perform user plane functions such as header compression, integrity protection and encryption.
- the RRC state indicates whether the RRC layer of the UE is logically connected with the RRC layer of the E-UTRAN.
- the RRC state may be divided into two types, such as an RRC connected state (RRC_CONNECTED) and an RRC idle state (RRC_IDLE).
- RRC_CONNECTED RRC connected state
- RRC_IDLE RRC idle state
- the E-UTRAN cannot grasp the terminal of the RRC_IDLE, and manages the terminal in units of a tracking area in which a core network (CN) is larger than a cell. That is, the terminal of the RRC_IDLE is only identified as a unit of a larger area, and in order to receive a normal mobile communication service such as voice or data communication, the terminal must transition to RRC_CONNECTED.
- CN core network
- the terminal may receive a broadcast of system information and paging information.
- the terminal may be assigned an identification (ID) that uniquely designates the terminal in the tracking area, and perform public land mobile network (PLMN) selection and cell reselection.
- ID an identification
- PLMN public land mobile network
- the UE may have an E-UTRAN RRC connection and an RRC context in the E-UTRAN to transmit data to the eNB and / or receive data from the eNB.
- the terminal may report channel quality information and feedback information to the eNB.
- the E-UTRAN may know the cell to which the UE belongs. Therefore, the network may transmit data to the terminal and / or receive data from the terminal, and the network may inter-RAT with a GSM EDGE radio access network (GERAN) through mobility of the terminal (handover and network assisted cell change (NACC)). radio access technology (cell change indication), and the network may perform cell measurement for a neighboring cell.
- GSM EDGE radio access network GERAN
- NACC network assisted cell change
- the UE designates a paging DRX cycle.
- the UE monitors a paging signal at a specific paging occasion for each UE specific paging DRX cycle.
- Paging opportunity is the time interval during which the paging signal is transmitted.
- the terminal has its own paging opportunity.
- the paging message is sent across all cells belonging to the same tracking area. If the terminal moves from one tracking area to another tracking area, the terminal sends a tracking area update (TAU) message to the network to update the location.
- TAU tracking area update
- the terminal When the user first turns on the power of the terminal, the terminal first searches for an appropriate cell and then stays in RRC_IDLE in that cell. When it is necessary to establish an RRC connection, the terminal staying in the RRC_IDLE may make an RRC connection with the RRC of the E-UTRAN through the RRC connection procedure and may transition to the RRC_CONNECTED. The UE staying in RRC_IDLE needs to establish an RRC connection with the E-UTRAN when uplink data transmission is necessary due to a user's call attempt or when a paging message is received from the E-UTRAN and a response message is required. Can be.
- EMM-REGISTERED EPS Mobility Management-REGISTERED
- EMM-DEREGISTERED EMM-DEREGISTERED
- the initial terminal is in the EMM-DEREGISTERED state, and the terminal performs a process of registering with the corresponding network through an initial attach procedure to access the network. If the attach procedure is successfully performed, the UE and the MME are in the EMM-REGISTERED state.
- an EPS Connection Management (ECM) -IDLE state In order to manage a signaling connection between the UE and the EPC, two states are defined, an EPS Connection Management (ECM) -IDLE state and an ECM-CONNECTED state, and these two states are applied to the UE and the MME.
- ECM EPS Connection Management
- ECM-IDLE state When the UE in the ECM-IDLE state establishes an RRC connection with the E-UTRAN, the UE is in the ECM-CONNECTED state.
- the MME in the ECM-IDLE state becomes the ECM-CONNECTED state when it establishes an S1 connection with the E-UTRAN.
- the E-UTRAN does not have the context information of the terminal.
- the UE in the ECM-IDLE state performs a terminal-based mobility related procedure such as cell selection or cell reselection without receiving a command from the network.
- a terminal-based mobility related procedure such as cell selection or cell reselection without receiving a command from the network.
- the terminal when the terminal is in the ECM-CONNECTED state, the mobility of the terminal is managed by the command of the network.
- the terminal In the ECM-IDLE state, if the position of the terminal is different from the position known by the network, the terminal informs the network of the corresponding position of the terminal through a tracking area update procedure.
- MTC machine type communication
- the MTC refers to the exchange of information through the base station 420 or the exchange of information through the base station between the MTC terminal 410 and the MTC server 430 between the MTC terminal 410 that does not involve human interaction.
- the services offered through MTC are different from those in existing human-involved communications, and there are various categories of services such as tracking, metering, payment, medical services, and remote control. exist. More specifically, services provided through the MTC may include meter reading, level measurement, utilization of surveillance cameras, inventory reporting of vending machines, and the like.
- a low cost / low specification terminal focused on data communication that provides such a service is referred to as an MTC terminal or a low complexity type UE for convenience.
- the base station may determine whether the terminal is an MTC terminal based on the capability of the terminal.
- an MTC terminal, a low complexity type terminal, a low cost UE, and a UE Category 0 terminal may be used in the same concept, and a general terminal refers to a terminal other than the terminals listed above. Can be used.
- the MTC server 430 is an entity that communicates with the MTC terminal 410.
- the MTC server 430 executes an MTC application and provides an MTC specific service to the MTC device.
- the MTC terminal 410 is a wireless device that provides MTC communication and may be fixed or mobile.
- MTC terminal since the amount of transmission data is small and uplink / downlink data transmission and reception occur occasionally, it is effective to lower the unit cost and reduce battery consumption in accordance with such a low data rate. Since the MTC terminal is characterized by low mobility, the channel environment is hardly changed.
- MTC terminal does not require a high performance function and the amount of use data is not large.
- UE Category is a general value used in 3GPP, which indicates how much data a terminal can process in a communication modem. Table 1 shows 3GPP UE Category.
- Table 1 UE Category DL speed UL speed UE Category DL speed UL speed 0 1 Mbps 1 Mbps 7 300 Mbps 100 Mbps 100 Mbps One 10 Mbps 5 Mbps 8 3 Gbps 1.5 Gbps 2 50 Mbps 25 Mbps 9 450 Mbps 50 Mbps 3 100 Mbps 50 Mbps 10 450 Mbps 100 Mbps 4 150 Mbps 50 Mbps 11 600 Mbps 50 Mbps 5 300 Mbps 75 Mbps 12 600 Mbps 100 Mbps 6 300 Mbps 50 Mbps 13 400 Mbps 50 Mbps
- UE Category 0 terminals can handle only 1 Mbps, so it can be easily made without much effort and cost when producing a modem. Only one antenna can be used. In addition, since it can transmit or receive only during a specific time without transmitting and receiving at the same time, FDD can operate like TDD. In addition, unlike conventional TDD, sufficient switching time of 1ms can be given between the transmission and reception switching periods, which can significantly reduce the overall cost in terms of hardware components, especially modem and RF.
- the MTC terminal may be installed in a coverage-limited place such as a basement as well as a building and a factory. For example, about 20% of MTC terminals supporting MTC services such as smart metering may be installed in a poor 'deep indoor' environment such as a basement. Therefore, for successful MTC data transmission, the coverage of the MTC terminal should be improved by about 20 dB compared to the coverage of the conventional general terminal. In consideration of such a situation, various coverage enhancement techniques, such as a repetitive transmission method for an MTC terminal for each channel / signal, are currently discussed.
- CIoT Celluar Internet of Things
- the Internet of Things is the future infrastructure and service of future information and communication where all things are connected to the Internet and communicate directly with each other.
- the reason why the Internet of Things is needed is to improve the quality of life and productivity based on a hyper-connected society, but ultimately it is important because it forms the central nervous system for the nation's own infrastructure, and furthermore, for civilization and the earth.
- the IoT can be classified into a cellular mobile communication IoT and a non-cellular IoT.
- CIoT means cellular internet based IoT.
- MTC traffic generated in the form of intermittent and sporadic short length packets must be efficiently delivered.
- large-scale random access for IoT services needs to reduce the cost and power consumption of devices, increase coverage, and improve the efficiency and efficiency of random access.
- the main use case of CIoT is a device for transmitting and receiving small data packets.
- the system may be required to send and receive small data packets efficiently.
- the battery consumption of the terminal should be small.
- the amount of signaling required in the network and over the air should be reduced.
- a new RRC suspend procedure and an RRC resume procedure have been newly proposed for user data transmission in a user plane based CIoT.
- the base station may suspend the RRC connection.
- the RRC connection may be temporarily suspended.
- the base station may resume the RRC connection.
- the RRC resume procedure the RRC connection can be resumed.
- the MM (Mobility Management) procedure has been newly proposed for the Traking Area Update (TAU) in the user plane based CIoT.
- FIG. 5 illustrates a procedure of suspending an RRC connection in a user plane based CIoT.
- the RRC suspend procedure may be used to transition from the RRC_CONNECTED state to the RRC_IDLE state. And, the RRC suspend procedure may allow the terminal to hold the context in the RRC_IDLE mode.
- the network may determine to suspend an RRC connection.
- the base station may indicate to the MME that the RRC connection of the terminal is suspended with a new S1AP message.
- the new S1AP message may be an S1AP UE context inactive message.
- the MME and the base station may store an S1AP association and associated UE context.
- the MME may send a Release Access Bearers Request (abnormal release or 'new cause' of the Radio Link Indication) message to the S-GW.
- the Release Access Bearers Request message may request the release of all S1-U bearers for the UE.
- the S-GW may assume that the terminal is in the IDLE state.
- the S-GW may send a response to the Release Access Bearers Request message to the MME.
- the MME may send an ACK for the S1AP UE context inactivity message to the base station.
- step S506 the MME may enter the ECM_IDLE state.
- the base station may suspend the RRC connection to the terminal.
- An identifier may be provided for use in subsequent resumption of a suspended RRC connection.
- the identifier may be 'Resume ID'.
- step S508 the terminal RRC layer may enter the RRC_IDLE state, the terminal NAS layer may enter the ECM_IDLE state.
- FIG. 6 shows a procedure for resuming RRC connection in user plane based CIoT.
- steps S601 to S603 since the terminal follows a legacy procedure, a detailed description thereof will be omitted.
- the terminal may transmit msg3 to the base station.
- the msg3 may be a new RRC connection resumption request message.
- the new RRC connection resumption request message may include a resume ID, an authentication token, a bearer indicator, and a establishment cause of the terminal.
- the base station may use the Resume ID to associate the UE transmitting the Resume ID with a previously stored UE context.
- step S605 the base station may transmit a RRC connection resumption completion message to the terminal. If RRC connection resume is specified as complete, the network may indicate which DRB is resumed.
- step S606 the terminal and the base station can resume the stored security context.
- the base station may notify the MME of the terminal state change.
- the terminal state change may be notified through a new message.
- the new message may be an S1AP UE context active message.
- the MME may enter the ECM_CONNECTED state.
- the MME may send a Modify Bearer Request message to the S-GW for each PDN connection. If the S-GW supports the Modify Access Bearers Request procedure, and if the S-GW does not need to send signaling to the P-GW, the MME sends a Modify Access Bearers Request message to the S-GW per terminal to optimize the signaling. Can be. Now, the S-GW can transmit downlink data toward the terminal. The S-GW may consider that the terminal is in the CONNECTED state.
- the S-GW may send a response to the Modify Bearer Request message to the MME.
- the response may be a Modify Bearer Response message.
- the MME may send an ACK for the S1AP UE context activation message to the base station.
- the base station may suspend the RRC connection and implicitly indicate that the user plane was successfully received. .
- steps S701 to S702 the terminal follows a legacy procedure, and thus a detailed description thereof will be omitted.
- the terminal may transmit msg3 to the base station.
- the msg3 may be a new RRC connection resumption request message.
- the new RRC connection resumption request message may include a resume ID of the terminal, an authentication token, an establishment cause, and a NAS PDU.
- the base station may use the Resume ID to associate the UE transmitting the Resume ID with a previously stored UE context.
- the msg3 may include a NAS PDU including a TAU REQUEST.
- the msg3 may not include a bearer indicator unlike the RRC connection resumption request message. The lack of bearer indicator may indicate to the base station that only SRB is needed. If there is not enough space to include the TAU REQUEST, the flag may indicate a subsequent message including the TAU REQUEST in step S705.
- the base station may transmit a RRC connection resumption completion message to the terminal.
- the network may complete contention resolution.
- the RRC connection resumption completion message may include a Resume ID.
- Step S705 may be performed when there is not enough space for the msg 3 to include a TAU REQUEST.
- the base station may deliver a TAU REQUEST to the MME.
- the TAU REQUEST may be included in an S1AP Initial UE Message message.
- the MME may send a TAU ACCEPT to the base station.
- the TAU ACCEPT may be included in an S1AP Downlink NAS Transport message.
- the base station may transmit a TAU ACCEPT to the terminal.
- the TAU ACCEPT may be included in a DL Information Transfer message.
- the base station may transmit an RRC suspension message to the terminal.
- the RRC suspension message may include a Resume ID.
- the terminal transmits an RRC connection resumption request message that does not include 'Bearer Ind'.
- the UE since the UE does not transmit UL data during the TAU, when the base station transmits the TAU REQUEST to the MME, it is intended to indicate that the bearer context does not need to be resumed.
- the base station receives the RRC connection resumption request message, the base station does not transmit a UE context activate message, while the base station may transmit an Initial UE Message message including a TAU REQUEST.
- the UE context activation message may be used in the same concept as a UE context resume request message.
- the UE may transmit an RRC connection resumption request message including a TAU REQUEST with an active flag.
- the bearer context is not activated because the RRC connection resumption request message does not include 'Bearer Ind'. Therefore, in this case, in order for the terminal to transmit UL data, after the MM procedure is completed and the terminal transitions to the RRC_IDLE state, the terminal should perform an RRC resumption procedure. Therefore, in order to suspend RRC and resume RRC, unnecessary signaling may be generated in the Uu interface, and unnecessary RRC state transition of the UE may occur.
- the terminal may deactivate the AS functions (Access Stratum functions) of the terminal, and may enter a power saving mode (PSM).
- PSM power saving mode
- the MME receives a TAU request message without an active flag, even if the MME identifies that there is DL data to be transmitted to the terminal, the MME cannot transmit the DL data to the terminal. According to the MM procedure, the bearer context for DL data transmission is not activated.
- a method for setting a bearer for transmitting user data in a user plane based cellular internet of things (CIoT) and an apparatus supporting the same demonstrates.
- FIG. 8 illustrates an RRC resumption procedure when a TAU request is triggered according to an embodiment of the present invention.
- the MME may inform the base station of a specific indication.
- the TAU request message including the active flag may be transmitted by the terminal and transmitted to the MME via the base station.
- the MME may instruct the base station to prohibit suspension of the RRC connection and resume the RRC connection.
- the MME may inform the base station of a specific indication. Through the specific indication, the MME may instruct the base station to prohibit the suspension of the RRC connection and resume the RRC connection.
- step S800 the terminal may be in an RRC_IDLE state.
- step S801 the terminal may transmit a random access preamble to the base station.
- the base station may transmit a response to the random access preamble to the terminal.
- the response to the random access preamble may be a random access response.
- the terminal may transmit an RRC Connection Resume Request message to the base station.
- the RRC connection resumption request message may not include a bearer indicator.
- the RRC connection resumption request message may include a TAU request message. Further, the TAU request message may have an active flag.
- the base station may transmit an RRC Connection Resume Complete message to the terminal to complete contention resolution.
- the base station may transmit a TAU request message to the MME.
- the TAU request message may be delivered using an Initial UE Message message.
- step S806 when the MME receives a message from the base station, the MME may identify whether the TAU request message includes an active flag and whether there is downlink data to be transmitted to the terminal.
- the MME may send a specific indication to the base station.
- the MME may transmit a specific indication to the base station.
- the specific indication may be included in a downlink NAS transport message. Further, the downlink NAS Transport message may include a TAU Accept message.
- the specific indication may indicate not to suspend the RRC connection and trigger a UE context resume request message. That is, the suspension of the RRC connection is prohibited by the specific indication, and transmission of the UE context resume request message may be triggered.
- the specific indication may inform the base station to resume the stored S1AP association and / or S1-U bearer context related information.
- the base station may deliver a TAU accept message to the terminal.
- the TAU accept message may be delivered using a DL Information Transfer message.
- the base station may inform the terminal of which DRB is resumed through a downlink information transfer message.
- step S808 the terminal and the base station can resume the stored security context (stored security context).
- the base station may transmit a UE context resume request message to the MME.
- the UE context resume request message may be a UE context active message.
- the MME may modify the S-GW and bearer.
- the MME may transmit a UE context resume response message to the base station in response to the UE context resume request message.
- the UE context resume response message may be a UE context active acknowledgment message.
- FIG 9 illustrates an RRC resume procedure when a TAU request is triggered according to an embodiment of the present invention.
- the base station may inform the MME whether resumption of the terminal is possible.
- the MME may provide an indicator for triggering a UE context resume request message to the base station.
- the base station may inform the MME whether resumption of the terminal is possible. If there is downlink data to be transmitted to the terminal, the MME may provide an indicator for triggering the UE context resumption request message to the base station.
- step S900 the terminal may be in an RRC_IDLE state.
- step S901 the terminal may transmit a random access preamble to the base station.
- the base station may transmit a response to the random access preamble to the terminal.
- the response to the random access preamble may be a random access response.
- the terminal may transmit a resume request indication to the base station requesting the resume of the terminal.
- the terminal may transmit the Resume ID to the base station.
- the resume request indication may be included in an RRC Connection Request message.
- step S904 when the base station receives the RRC connection request message from the base station, based on the resume request indication, the base station can determine whether the resumption of the RRC connection with the previously suspended terminal is possible.
- the base station may transmit an RRC connection setup message to the terminal.
- the terminal may transmit an RRC connection setup complete message to the base station.
- the RRC connection setup complete message may include a TAU request message.
- the TAU request message may have an active flag.
- the base station may deliver a TAU request message to the MME.
- the TAU request message may be delivered using an Initial UE Message message.
- the Initial UE Message message may include a Resumable Indication.
- the resumable indication may inform the MME whether resumption of the RRC connection with the previously suspended terminal is possible.
- step S908 when the MME receives a message from the base station, the MME may identify whether the TAU request message includes an active flag and whether there is downlink data to be transmitted to the terminal.
- the MME may send a resume indication to the base station.
- the MME may transmit a resume indication to the base station.
- the resume indication may be included in a downlink NAS transport message.
- the downlink NAS Transport message may include a TAU Accept message.
- the resume instruction may instruct to trigger a UE context resume request message. That is, the transmission of the UE context resume request message can be triggered by the resume instruction.
- the UE context resume request message may be a UE context active message.
- the resume indication may inform the base station to resume the stored S1AP association and / or S1-U bearer context related information.
- the MME may transmit a downlink NAS transport message not including a resume indication to the base station.
- the base station may transmit a TAU accept message to the terminal.
- the TAU accept message may be delivered using a DL Information Transfer message.
- the base station may inform the UE which DRB is resumed through a downlink information transfer message.
- the base station may transmit a UE context resume request message to the MME.
- the UE context resume request message may be a UE context active message.
- the MME may modify the S-GW and the bearer.
- the MME may transmit a UE context resume response message to the base station in response to the UE context resume request message.
- the UE context resume response message may be a UE context active acknowledgment message.
- FIG. 10 illustrates an RRC resumption procedure when a TAU request is triggered according to an embodiment of the present invention.
- the base station may transmit a TAU request message to the MME using the UE context resumption request message.
- the MME may provide a TAU accept message to the base station using the UE context resume response message.
- the UE context resume request message may be a UE context active message.
- the UE context resume response message may be a UE context activation grant message.
- step S1000 the terminal may be in an RRC_IDLE state.
- step S1001 the terminal may transmit a random access preamble to the base station.
- the base station may transmit a response to the random access preamble to the terminal.
- the response to the random access preamble may be a random access response.
- the UE may transmit an RRC connection resumption request message including an establishment cause with mo-signalling indicated to mo-signalling to the base station.
- the terminal may transmit an RRC connection request message including the establishment cause indicated by mo-signalling to the base station. If the RRC connection request message is used for resumption, the RRC connection request message may include an instruction for requesting a resume for the terminal.
- step S1004 upon receipt of a message from the terminal, the base station can determine whether resumption is possible. If resumption is possible and the cause of establishment is indicated as mo-signalling, the base station is in a UE context until a NAS message or an RRC connection setup complete message included in a UL Information Transfer message is received from the terminal. The transmission of the resume request message should be suspended. The base station may transmit an RRC connection resumption complete message or an RRC connection setup message to the terminal to indicate whether resumption is possible.
- the terminal may transmit a TAU request message to the base station.
- the TAU request message may be included in an UL information transfer message or an RRC connection setup complete message.
- step S1006 the terminal and the base station can resume the stored security context (stored security context).
- the base station may transmit a TAU request message to the MME.
- the TAU request message may be included in a UE context resume request message.
- the UE context resume request message may be a UE context active message.
- the MME may modify the S-GW and the bearer.
- the MME may transmit a UE context resume response message to the base station in response to the UE context resume request message.
- the UE context resume response message may include a TAU accept message.
- the UE context resume response message may be a UE context active acknowledgment message.
- the base station may deliver a TAU accept message to the terminal.
- the TAU accept message may be delivered using a DL Information Transfer message.
- FIG. 11 illustrates an RRC resume procedure when a TAU request is triggered according to an embodiment of the present invention.
- the MME may inform the base station to activate a previously stored UE context. Or, if there is downlink data to be transmitted to the terminal, the MME may inform the base station to activate the previously stored UE context.
- the terminal in step S1100, the terminal may be in an RRC_IDLE state.
- the terminal may transmit a random access preamble to the base station.
- the base station may transmit a response to the random access preamble to the terminal.
- the response to the random access preamble may be a random access response.
- the terminal may transmit an RRC connection request message to the base station.
- the base station may transmit an RRC connection setup message to the terminal.
- the terminal may transmit an RRC connection setup complete message to the base station in response to the RRC connection setup message.
- the RRC connection setup complete message may include a TAU request message.
- the TAU request message may have an active flag.
- the base station may deliver a TAU request message to the MME.
- the TAU request message may be delivered using an Initial UE Message message.
- step S1107 upon receiving a message from the base station, the MME may identify whether the TAU request message includes an active flag and whether there is downlink data to be transmitted to the terminal.
- the MME can determine whether the base station that sent the Initial UE Message message in step S1106 is suspending the UE context for the terminal that sent the TAU request message. Or, if there is downlink data to be transmitted to the terminal, the MME can determine whether the base station that sent the Initial UE Message message in step S1106 suspend the UE context for the terminal that sent the TAU request message.
- the TAU request message may be transmitted by the terminal through a RRC connection suspend procedure. If any of the items listed below exist in the MME, the MME may identify that the base station is suspending the UE context.
- the information, which the MME stores, on the MME stores the UE context for the UE, while suspending the RRC connection.
- eNB which is suspending the UE context for this UE.
- Tunnel Endpoint ID allocated by the eNB during RRC Suspend procedure for the UE during an RRC suspend procedure for the UE.
- the MME may modify the S-GW and the bearer. Otherwise, the MME may perform an existing TAU procedure. If the TAU request message does not include an active flag and there is no downlink data to be transmitted to the terminal, the MME may proceed with the existing TAU procedure without performing bearer modification.
- step S1108 if the TAU request message includes an active flag or there is downlink data to be transmitted to the terminal, and the MME identifies the base station storing the UE context for the terminal requesting the TAU (in step S1107),
- the MME may send a UE context activation indication (UE Context Activation Indication) to the base station to indicate the activation of the previously stored UE context.
- the UE context activation indication may be included in a downlink NAS Transport message. Further, the downlink NAS Transport message may include a TAU Accept message.
- the MME may transmit a downlink NAS transport message not including the UE context activation indication to the base station. In this case, bearer modification is also not performed.
- step S1109 upon receipt of a message from the MME, the base station activates a previously stored UE context.
- the base station may transmit a TAU accept message to the terminal.
- the TAU accept message may be delivered using a DL Information Transfer message. Through this, it may be indicated to the UE that the UE context is activated.
- FIG. 12 is a block diagram illustrating a method for setting a bearer for transmission of user data in a user plane based CIoT according to an embodiment of the present invention.
- the base station may receive a TAU request (Tracking Area Update Request) message from the terminal.
- the terminal may be in an RRC_IDLE state.
- the base station may transmit an Initial UE Message message including the TAU request message to a Mobility Management Entity (MME).
- MME Mobility Management Entity
- the base station may receive a downlink NAS transport message including a resume indication from the MME.
- the base station may transmit a UE context resume request message to the MME based on the resume instruction.
- the TAU request message received from the terminal may be included in the RRC connection resumption request message.
- the RRC connection resumption request message may not include a bearer indication.
- the suspend of the RRC connection may be prohibited by the resume instruction, and transmission of the UE context resume request message may be triggered. If the TAU request message includes an active flag, the resume indication may be received from the MME. Or, if it is identified by the MME that there is downlink data to be transmitted to the terminal, the resume instruction may be received from the MME.
- the base station may receive a resume request instruction requesting the resume for the terminal from the terminal, and may determine whether to resume the previously suspended RRC connection based on the resume request instruction.
- the resume request indication may be included in an RRC connection request message.
- the TAU request message received from the terminal may be included in an RRC connection setup complete message.
- the Initial UE Message message may include a resumeable indication indicating whether the base station can resume a previously suspended RRC connection. Transmission of the UE context resume request message may be triggered by the resume instruction.
- the resume indication may be received from the MME. Or, if it is identified by the MME that there is downlink data to be transmitted to the terminal, the resume instruction may be received from the MME.
- FIG. 13 is a block diagram of a wireless communication system in which an embodiment of the present invention is implemented.
- the terminal 1300 includes a processor 1301, a memory 1302, and a transceiver 1303.
- the memory 1302 is connected to the processor 1301 and stores various information for driving the processor 1301.
- the transceiver 1303 is connected to the processor 1301 to transmit and / or receive a radio signal.
- the processor 1301 implements the proposed functions, processes, and / or methods. In the above-described embodiment, the operation of the terminal may be implemented by the processor 1301.
- the base station 1310 includes a processor 1311, a memory 1312, and a transceiver 1313.
- the memory 1312 is connected to the processor 1311 and stores various information for driving the processor 1311.
- the transceiver 1313 is connected to the processor 1311 to transmit and / or receive a radio signal.
- the processor 1311 implements the proposed functions, processes and / or methods. In the above-described embodiment, the operation of the base station may be implemented by the processor 1311.
- the MME 1320 includes a processor 1321, a memory 1322, and a transceiver 1323.
- the memory 1322 is connected to the processor 1321 and stores various information for driving the processor 1321.
- the transceiver 1323 is connected to the processor 1321 to transmit and / or receive a radio signal.
- Processor 1321 implements the proposed functions, processes, and / or methods. In the above-described embodiment, the operation of the MME may be implemented by the processor 1321.
- the processor may include application-specific integrated circuits (ASICs), other chipsets, logic circuits, and / or data processing devices.
- the memory may include read-only memory (ROM), random access memory (RAM), flash memory, memory card, storage medium and / or other storage device.
- the transceiver may include baseband circuitry for processing wireless signals.
- the above-described technique may be implemented as a module (process, function, etc.) for performing the above-described function.
- the module may be stored in memory and executed by a processor.
- the memory may be internal or external to the processor and may be coupled to the processor by various well known means.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
UE Category | DL 속도 | UL 속도 | UE Category | DL 속도 | UL 속도 |
0 | 1 Mbps | 1 Mbps | 7 | 300 Mbps | 100 Mbps |
1 | 10 Mbps | 5 Mbps | 8 | 3 Gbps | 1.5 Gbps |
2 | 50 Mbps | 25 Mbps | 9 | 450 Mbps | 50 Mbps |
3 | 100 Mbps | 50 Mbps | 10 | 450 Mbps | 100 Mbps |
4 | 150 Mbps | 50 Mbps | 11 | 600 Mbps | 50 Mbps |
5 | 300 Mbps | 75 Mbps | 12 | 600 Mbps | 100 Mbps |
6 | 300 Mbps | 50 Mbps | 13 | 400 Mbps | 50 Mbps |
Claims (15)
- 무선 통신 시스템에서 기지국이 사용자 평면 기반 CIoT(User Plane Based Celluar Internet of Things)에서 사용자 데이터(user data)의 전송을 위한 베어러(bearer)를 설정하는 방법에 있어서,TAU 요청(Tracking Area Update Request) 메시지를 단말로부터 수신하고,상기 TAU 요청 메시지를 포함하는 Initial UE Message 메시지를 MME(Mobility Management Entity)에게 전송하고,재개 지시(Resume Indication)를 포함하는 하향링크 NAS Transport 메시지를 상기 MME로부터 수신하고,상기 재개 지시를 기반으로 UE 컨텍스트 재개 요청(Context Resume Request) 메시지를 상기 MME에게 전송하는 것을 포함하는 것을 특징으로 하는 방법.
- 제 1 항에 있어서,상기 단말로부터 수신된 TAU 요청 메시지는 RRC 연결 재개 요청 메시지에 포함되는 것을 특징으로 하는 방법.
- 제 2 항에 있어서,상기 RRC 연결 재개 요청 메시지는 베어러 지시(Bearer Indication)를 포함하지 않는 것을 특징으로 하는 방법.
- 제 3 항에 있어서,상기 재개 지시에 의해 RRC 연결의 일시 중단(suspension)이 금지되고, 상기 UE 컨텍스트 재개 요청 메시지의 전송이 트리거되는 것을 특징으로 하는 방법.
- 제 3 항에 있어서,상기 TAU 요청 메시지가 활성 플래그(Active Flag)를 포함하면, 상기 재개 지시는 상기 MME로부터 수신되는 것을 특징으로 하는 방법.
- 제 3 항에 있어서,단말에게 전송될 하향링크 데이터가 있음이 상기 MME에 의해 식별되면, 상기 재개 지시는 상기 MME로부터 수신되는 것을 특징으로 하는 방법.
- 제 1 항에 있어서,상기 기지국은, 상기 단말에 대하여 재개를 요청하는 재개 요청 지시를 상기 단말로부터 수신하고, 상기 재개 요청 지시를 기반으로 이전에 일시 중단된 RRC 연결의 재개가 가능한지 여부를 결정하는 것을 더 포함하는 것을 특징으로 하는 방법.
- 제 7 항에 있어서,상기 재개 요청 지시는 RRC 연결 요청(connection request) 메시지에 포함되는 것을 특징으로 하는 방법.
- 제 8 항에 있어서,상기 단말로부터 수신된 TAU 요청 메시지는 RRC 연결 셋업 완료(connection setup complete) 메시지에 포함되는 것을 특징으로 하는 방법.
- 제 9 항에 있어서,상기 Initial UE Message 메시지는 상기 기지국이 이전에 일시 중단된 RRC 연결을 재개할 수 있는지 여부를 지시하는 재개 가능 지시(resumeable indication)를 포함하는 것을 특징으로 하는 방법.
- 제 10 항에 있어서,상기 재개 지시에 의해 상기 UE 컨텍스트 재개 요청 메시지의 전송이 트리거되는 것을 특징으로 하는 방법.
- 제 10 항에 있어서,상기 TAU 요청 메시지가 활성 플래그(Active Flag)를 포함하면, 상기 재개 지시는 상기 MME로부터 수신되는 것을 특징으로 하는 방법.
- 제 10 항에 있어서,단말에게 전송될 하향링크 데이터가 있음이 상기 MME에 의해 식별되면, 상기 재개 지시는 상기 MME로부터 수신되는 것을 특징으로 하는 방법.
- 제 1 항에 있어서,상기 단말은 RRC_IDLE 상태인 것을 특징으로 하는 방법.
- 무선 통신 시스템에서 사용자 평면 기반 CIoT(User Plane Based Celluar Internet of Things)에서 사용자 데이터(user data)의 전송을 위한 베어러를 설정하는 기지국에 있어서,메모리; 송수신기; 및 상기 메모리와 상기 송수신기를 연결하는 프로세서를 포함하되, 상기 프로세서는상기 송수신기가 TAU 요청(Tracking Area Update Request) 메시지를 단말로부터 수신하도록 제어하고,상기 송수신기가 상기 TAU 요청 메시지를 포함하는 Initial UE Message 메시지를 MME(Mobility Management Entity)에게 전송하도록 제어하고,상기 송수신기가 재개 지시(Resume Indication)를 포함하는 하향링크 NAS Transport 메시지를 상기 MME로부터 수신하도록 제어하고,상기 송수신기가 상기 재개 지시를 기반으로 UE 컨텍스트 재개 요청(Context Resume Request) 메시지를 상기 MME에게 전송하는 것을 제어하도록 구성되는 것을 특징으로 하는 기지국.
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020187015593A KR102051552B1 (ko) | 2015-12-29 | 2016-12-27 | 사용자 데이터의 전송을 위한 베어러를 설정하는 방법 및 장치 |
US16/065,615 US10616789B2 (en) | 2015-12-29 | 2016-12-27 | Method and device for establishing bearer for transmission of user data |
EP16882067.8A EP3399831B1 (en) | 2015-12-29 | 2016-12-27 | Method and device for establishing bearer for transmission of user data |
CN201680077128.5A CN108476546B (zh) | 2015-12-29 | 2016-12-27 | 建立用于用户数据的传输的承载的方法和设备 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201562272620P | 2015-12-29 | 2015-12-29 | |
US62/272,620 | 2015-12-29 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2017116115A1 true WO2017116115A1 (ko) | 2017-07-06 |
Family
ID=59225377
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2016/015328 WO2017116115A1 (ko) | 2015-12-29 | 2016-12-27 | 사용자 데이터의 전송을 위한 베어러를 설정하는 방법 및 장치 |
Country Status (5)
Country | Link |
---|---|
US (1) | US10616789B2 (ko) |
EP (1) | EP3399831B1 (ko) |
KR (1) | KR102051552B1 (ko) |
CN (1) | CN108476546B (ko) |
WO (1) | WO2017116115A1 (ko) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2019027205A1 (ko) * | 2017-07-30 | 2019-02-07 | 엘지전자 주식회사 | Cu-du 분할 시나리오에서 rrc 연결을 재개하는 방법 및 장치 |
WO2019134657A1 (zh) * | 2018-01-04 | 2019-07-11 | 维沃移动通信有限公司 | 会话控制方法、网络设备及终端 |
CN110235513A (zh) * | 2017-07-27 | 2019-09-13 | Lg电子株式会社 | 用于执行edt的方法和装置 |
WO2019215331A1 (en) * | 2018-05-11 | 2019-11-14 | Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. | Uplink access management concept |
Families Citing this family (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3322240A4 (en) * | 2015-08-06 | 2018-07-11 | Huawei Technologies Co., Ltd. | Method and apparatus for establishing data radio bearer |
WO2017126922A1 (ko) | 2016-01-19 | 2017-07-27 | 엘지전자(주) | 무선 통신 시스템에서 연결 재개 방법 및 이를 위한 장치 |
US10506389B2 (en) * | 2016-02-04 | 2019-12-10 | Nec Corporation | Radio terminal, radio station, and method therefor |
ES2922993T3 (es) * | 2016-02-17 | 2022-09-22 | Nec Corp | Selección de plano de control y plano de usuario para la transmisión de datos |
WO2017155259A1 (ko) * | 2016-03-09 | 2017-09-14 | 엘지전자 주식회사 | 사용자 데이터의 전송을 위한 베어러를 설정하는 방법 및 장치 |
US11044776B2 (en) * | 2016-03-27 | 2021-06-22 | Lg Electronics Inc. | Method for attempting network access from NB-IoT RAT |
GB2548878A (en) * | 2016-03-31 | 2017-10-04 | Nec Corp | Communication system |
EP3445127B1 (en) * | 2016-05-13 | 2020-11-25 | Kyocera Corporation | Wireless terminal |
US10917789B2 (en) | 2017-04-21 | 2021-02-09 | Nokia Technologies Oy | Radio link recovery for user equipment |
KR20190143782A (ko) * | 2018-06-21 | 2019-12-31 | 삼성전자주식회사 | 차세대 이동 통신 시스템에서 rrc 비활성화 모드 단말의 이중 접속을 지원하는 방법 및 장치 |
WO2020067813A1 (en) | 2018-09-27 | 2020-04-02 | Samsung Electronics Co., Ltd. | Apparatus and method for performing dual connectivity in wireless communication system |
WO2020062072A1 (zh) * | 2018-09-28 | 2020-04-02 | 深圳大学 | 基于服务网络的无线物联网物理层混合认证方法及系统 |
CN109561516B (zh) * | 2018-11-29 | 2021-09-28 | 西安电子科技大学 | 一种rrc的nas pdu新传和重传的发送方法 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20140001244A (ko) * | 2011-01-21 | 2014-01-06 | 블랙베리 리미티드 | (로컬) 오프로딩에 이용되는 접속에 대한 접속 컨텍스트를 결정하기 위한 네트워크 장치 및 프로세스 |
KR20140005304A (ko) * | 2011-04-29 | 2014-01-14 | 엘지전자 주식회사 | 세션 관리 및 이동성 관리에 관련된 데이터를 처리하는 방법 |
JP2014132785A (ja) * | 2011-09-30 | 2014-07-17 | Nec Corp | 通信システムと方法と装置 |
US20150139054A1 (en) * | 2012-05-29 | 2015-05-21 | Zte Corporation | Method and system for controlling signalling transmission in power-saving mode |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101610494B (zh) * | 2008-06-16 | 2013-04-24 | 华为技术有限公司 | 实现过载控制或差异化服务的方法、系统及设备 |
CN101742576B (zh) * | 2008-11-07 | 2013-06-05 | 华为技术有限公司 | 恢复保留态gbr承载的方法及装置 |
WO2013028026A2 (en) * | 2011-08-24 | 2013-02-28 | Lg Electronics Inc. | Method and apparatus for transmitting uplink data associated with mtc device trigger function |
US9247575B2 (en) * | 2012-03-27 | 2016-01-26 | Blackberry Limited | eNB storing RRC configuration information at another network component |
EP3346753B1 (en) * | 2015-11-06 | 2020-04-29 | Samsung Electronics Co., Ltd. | Method for transmitting data in ciot system and device therefor |
-
2016
- 2016-12-27 KR KR1020187015593A patent/KR102051552B1/ko active IP Right Grant
- 2016-12-27 WO PCT/KR2016/015328 patent/WO2017116115A1/ko active Application Filing
- 2016-12-27 US US16/065,615 patent/US10616789B2/en active Active
- 2016-12-27 EP EP16882067.8A patent/EP3399831B1/en active Active
- 2016-12-27 CN CN201680077128.5A patent/CN108476546B/zh active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20140001244A (ko) * | 2011-01-21 | 2014-01-06 | 블랙베리 리미티드 | (로컬) 오프로딩에 이용되는 접속에 대한 접속 컨텍스트를 결정하기 위한 네트워크 장치 및 프로세스 |
KR20140005304A (ko) * | 2011-04-29 | 2014-01-14 | 엘지전자 주식회사 | 세션 관리 및 이동성 관리에 관련된 데이터를 처리하는 방법 |
JP2014132785A (ja) * | 2011-09-30 | 2014-07-17 | Nec Corp | 通信システムと方法と装置 |
US20150139054A1 (en) * | 2012-05-29 | 2015-05-21 | Zte Corporation | Method and system for controlling signalling transmission in power-saving mode |
Non-Patent Citations (1)
Title |
---|
3GPP: "3GPP; TSG SA; General Packet Radio Service (GPRS) Enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Access (Release 13", 3GPP TS 23.401 V13.5.0, 15 December 2015 (2015-12-15), XP055506928 * |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110235513A (zh) * | 2017-07-27 | 2019-09-13 | Lg电子株式会社 | 用于执行edt的方法和装置 |
CN110235513B (zh) * | 2017-07-27 | 2023-05-09 | Lg电子株式会社 | 用于执行edt的方法和装置 |
WO2019027205A1 (ko) * | 2017-07-30 | 2019-02-07 | 엘지전자 주식회사 | Cu-du 분할 시나리오에서 rrc 연결을 재개하는 방법 및 장치 |
KR20190013633A (ko) * | 2017-07-30 | 2019-02-11 | 엘지전자 주식회사 | Cu-du 분할 시나리오에서 rrc 연결을 재개하는 방법 및 장치 |
KR101988459B1 (ko) | 2017-07-30 | 2019-06-12 | 엘지전자 주식회사 | Cu-du 분할 시나리오에서 rrc 연결을 재개하는 방법 및 장치 |
US10904941B2 (en) | 2017-07-30 | 2021-01-26 | Lg Electronics Inc. | Method and apparatus for resuming RRC connection in CU-DU division scenario |
US11638320B2 (en) | 2017-07-30 | 2023-04-25 | Lg Electronics Inc. | Method and apparatus for resuming RRC connection in CU-DU division scenario |
WO2019134657A1 (zh) * | 2018-01-04 | 2019-07-11 | 维沃移动通信有限公司 | 会话控制方法、网络设备及终端 |
CN110012553A (zh) * | 2018-01-04 | 2019-07-12 | 维沃移动通信有限公司 | 会话控制方法、网络设备及终端 |
WO2019215331A1 (en) * | 2018-05-11 | 2019-11-14 | Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. | Uplink access management concept |
Also Published As
Publication number | Publication date |
---|---|
US20190021023A1 (en) | 2019-01-17 |
EP3399831A1 (en) | 2018-11-07 |
KR20180071365A (ko) | 2018-06-27 |
CN108476546B (zh) | 2021-11-09 |
CN108476546A (zh) | 2018-08-31 |
KR102051552B1 (ko) | 2019-12-03 |
US10616789B2 (en) | 2020-04-07 |
EP3399831B1 (en) | 2020-08-19 |
EP3399831A4 (en) | 2019-07-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2017116115A1 (ko) | 사용자 데이터의 전송을 위한 베어러를 설정하는 방법 및 장치 | |
WO2019088531A1 (en) | Method for handling for bandwidth part operation in wireless communication system and a device therefor | |
WO2018194338A1 (en) | Method for performing measurement for aerial ue in wireless communication system and a device therefor | |
WO2019027205A1 (ko) | Cu-du 분할 시나리오에서 rrc 연결을 재개하는 방법 및 장치 | |
WO2017095020A1 (ko) | 무선 통신 시스템에서 ue id를 전송하는 방법 및 장치 | |
WO2015142082A1 (en) | Method and apparatus for configuring buffer status report for public safety transmission or vehicle-related transmission in wireless communication system | |
WO2017171477A1 (ko) | 무선 통신 시스템에서 v2p 통신을 향상시키는 방법 및 장치 | |
WO2017026781A1 (ko) | 단말이 scptm에 대한 pdcch 모니터링을 수행하는 방법 및 장치 | |
WO2018164528A1 (ko) | 단말 능력을 전달하는 방법 및 이를 지원하는 장치 | |
WO2017192018A1 (ko) | 무선 통신 시스템에서 라이트 연결 상태에 있는 단말을 페이징하는 방법 및 장치 | |
WO2018062848A1 (ko) | Rrc 연결 재확립 절차의 수행 방법 및 이를 지원하는 장치 | |
WO2018088837A1 (ko) | 단말이 셀 재선택 절차를 수행하는 방법 및 이를 지원하는 장치 | |
WO2018016865A1 (ko) | 관심 있는 sib을 요청하는 방법 및 장치 | |
WO2016144074A1 (ko) | 페이징 시그널링을 감소시키기 위한 방법 및 장치 | |
WO2017135740A1 (ko) | V2x 통신을 수행하는 방법 및 장치 | |
WO2017155361A1 (ko) | V2x 통신을 위한 자원 할당 방법 및 장치 | |
WO2017078323A1 (ko) | 페이징을 수행하는 방법 및 장치 | |
WO2017078316A1 (ko) | 단말이 주파수 측정을 수행하는 방법 및 장치 | |
WO2018084630A1 (ko) | 시스템 정보를 수신하는 방법 및 장치 | |
WO2019083245A1 (en) | METHOD FOR REALIZING A RANDOM ACCESS PROCEDURE IN BANDWIDTH PART (BWP) OPERATION IN A WIRELESS COMMUNICATION SYSTEM AND DEVICE THEREOF | |
WO2017135684A1 (ko) | 무선 통신 시스템에서 측정을 수행하는 방법 및 장치 | |
WO2016186345A1 (en) | Method for transmitting discovery signal for establishing d2d link with relay ue in wireless communication system and apparatus therefor | |
WO2018143709A1 (ko) | Rrc 상태를 결정하는 방법 및 장치 | |
WO2017026763A1 (en) | Method for performing realy functions at ue in wireless communication system and apparatus therefor | |
WO2017052154A1 (ko) | 우선되는 서비스가 전송되는 방법 및 장치 |
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: 16882067 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 20187015593 Country of ref document: KR Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2016882067 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2016882067 Country of ref document: EP Effective date: 20180730 |