WO2018199673A1 - Procédé de transmission de données basé sur une transmission edt - Google Patents

Procédé de transmission de données basé sur une transmission edt Download PDF

Info

Publication number
WO2018199673A1
WO2018199673A1 PCT/KR2018/004897 KR2018004897W WO2018199673A1 WO 2018199673 A1 WO2018199673 A1 WO 2018199673A1 KR 2018004897 W KR2018004897 W KR 2018004897W WO 2018199673 A1 WO2018199673 A1 WO 2018199673A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
message
edt
layer
rrc
Prior art date
Application number
PCT/KR2018/004897
Other languages
English (en)
Korean (ko)
Inventor
김태훈
김홍석
이재욱
Original Assignee
엘지전자 주식회사
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 엘지전자 주식회사 filed Critical 엘지전자 주식회사
Priority to KR1020187037554A priority Critical patent/KR102053229B1/ko
Priority to JP2019510630A priority patent/JP6935489B2/ja
Priority to EP18792170.5A priority patent/EP3471457B1/fr
Priority to CN201880003851.8A priority patent/CN109863783B/zh
Publication of WO2018199673A1 publication Critical patent/WO2018199673A1/fr
Priority to US16/242,458 priority patent/US10932121B2/en
Priority to US17/181,933 priority patent/US11812502B2/en
Priority to US18/375,864 priority patent/US20240031793A1/en

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/0215—Traffic management, e.g. flow control or congestion control based on user or device properties, e.g. MTC-capable devices
    • 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
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • 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
    • 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 mobile communications.
  • the 3GPP which enacts the technical specifications of the mobile communication system, has been trying to optimize and improve the performance of 3GPP technologies since late 2004 in order to respond to various forums and new technologies related to 4G mobile communication. Started research on Term Evolution / System Architecture Evolution technology.
  • 3GPP SAE centered on 3GPP SA WG2
  • 3GPP SA WG2 is a study on network technology aimed at determining network structure and supporting mobility between heterogeneous networks in parallel with LTE work of 3GPP TSG RAN.
  • Recent important standardization issues of 3GPP Is one of. This is a work to develop a 3GPP system into a system supporting various radio access technologies based on IP, and has been aimed at an optimized packet-based system that minimizes transmission delay with improved data transmission capability.
  • the Evolved Packet System (EPS) high-level reference model defined by 3GPP SA WG2, includes non-roaming cases and roaming cases in various scenarios. Reference may be made to documents TS 23.401 and TS 23.402.
  • the network structure diagram of FIG. 1 is a simple reconfiguration.
  • 1 is a structural diagram of an evolved mobile communication network.
  • the EPC may include various components, and in FIG. 1, some of them correspond to a Serving Gateway (S-GW) 52, a PDN Packet Data Network Gateway (GW) 53, and a Mobility Management Entity (MME). 51, a Serving General Packet Radio Service (GPRS) Supporting Node (SGSN), and an enhanced Packet Data Gateway (ePDG).
  • S-GW Serving Gateway
  • GW Packet Data Network Gateway
  • MME Mobility Management Entity
  • GPRS General Packet Radio Service
  • SGSN Serving General Packet Radio Service
  • ePDG enhanced Packet Data Gateway
  • the S-GW 52 operates as a boundary point between the radio access network (RAN) and the core network, and is an element that functions to maintain a data path between the eNodeB 20 and the PDN GW 53.
  • the S-GW 52 serves as a local mobility anchor point. That is, packets may be routed through the S-GW 52 for mobility in the E-UTRAN (Universal Mobile Telecommunications System (Evolved-UMTS) Terrestrial Radio Access Network defined in 3GPP Release-8 or later).
  • E-UTRAN Universal Mobile Telecommunications System (Evolved-UMTS) Terrestrial Radio Access Network defined in 3GPP Release-8 or later.
  • the S-GW 52 may be connected to other 3GPP networks (RANs defined before 3GPP Release-8, for example, UTRAN or GERAN (GSM (Global System for Mobile Communication) / EDGE (Enhanced Data rates for Global Evolution) Radio Access). It can also serve as an anchor point for mobility with a network).
  • 3GPP networks RANs defined before 3GPP Release-8, for example, UTRAN or GERAN (GSM (Global System for Mobile Communication) / EDGE (Enhanced Data rates for Global Evolution) Radio Access). It can also serve as an anchor point for mobility with a network).
  • PDN GW (or P-GW) 53 corresponds to the termination point of the data interface towards the packet data network.
  • the PDN GW 53 may support policy enforcement features, packet filtering, charging support, and the like.
  • mobility management between 3GPP networks and non-3GPP networks for example, untrusted networks such as Interworking Wireless Local Area Networks (I-WLANs), code-division multiple access (CDMA) networks, or trusted networks such as WiMax) Can serve as an anchor point for.
  • untrusted networks such as Interworking Wireless Local Area Networks (I-WLANs), code-division multiple access (CDMA) networks, or trusted networks such as WiMax
  • I-WLANs Interworking Wireless Local Area Networks
  • CDMA code-division multiple access
  • WiMax trusted networks
  • S-GW 52 and the PDN GW 53 are configured as separate gateways in the example of the network structure of FIG. 1, two gateways may be implemented according to a single gateway configuration option. have.
  • the MME 51 is an element that performs signaling and control functions to support access to the network connection of the UE, allocation of network resources, tracking, paging, roaming and handover, and the like. .
  • the MME 51 controls control plane functions related to subscriber and session management.
  • the MME 51 manages a number of eNodeBs 20 and performs signaling for the selection of a conventional gateway for handover to other 2G / 3G networks.
  • the MME 51 performs security procedures, terminal-to-network session handling, idle terminal location management, and the like.
  • the SGSN handles all packet data, such as user's mobility management and authentication to other connecting 3GPP networks (e.g., GPRS networks, UTRAN / GERAN).
  • 3GPP networks e.g., GPRS networks, UTRAN / GERAN.
  • the ePDG acts as a secure node for untrusted non-3GPP networks (eg, I-WLAN, WiFi hotspots, etc.).
  • untrusted non-3GPP networks eg, I-WLAN, WiFi hotspots, etc.
  • a terminal having IP capability is provided by an operator (ie, an operator) via various elements in the EPC, based on 3GPP access as well as non-3GPP access.
  • an IP service network eg, IMS
  • FIG. 1 illustrates various reference points (eg, S1-U, S1-MME, etc.).
  • a conceptual link defining two functions existing in different functional entities of E-UTRAN and EPC is defined as a reference point.
  • Table 1 below summarizes the reference points shown in FIG. 1.
  • This reference point can be used in PLMN-to-PLMN-to-for example (for PLMN-to-PLMN handover))
  • S5 Reference point providing user plane tunneling and tunnel management between the SGW and PDN GW. Used for SGW relocation because of UE mobility and when a connection to the PDN GW where the SGW is not co-located is required for the required PDN connectivity.
  • the PDN may be an operator external public or private PDN or, for example, an in-operator PDN for the provision of IMS services. This reference point corresponds to Gi of 3GPP access
  • S2a and S2b correspond to non-3GPP interfaces.
  • S2a is a reference point that provides the user plane with associated control and mobility support between trusted non-3GPP access and PDN GW.
  • S2b is a reference point that provides the user plane with relevant control and mobility support between the ePDG and PDN GW.
  • Figure 2 is an exemplary view showing the functions of the main nodes of the E-UTRAN and the general EPC in general.
  • the eNodeB 20 may route to a gateway, schedule and transmit paging signals, schedule and transmit broadcaster channels (BCHs), uplink and downlink while an RRC (Radio Resource Control) connection is active.
  • BCHs broadcaster channels
  • RRC Radio Resource Control
  • paging can occur, LTE_IDLE state management, user planes can perform encryption, EPS bearer control, NAS signaling encryption and integrity protection.
  • FIG. 3 is an exemplary diagram illustrating a structure of a radio interface protocol in a control plane between a UE and an eNodeB
  • FIG. 4 is a structure of a radio interface protocol in a user plane between a terminal and a base station. Another example is shown.
  • the radio interface protocol is based on the 3GPP radio access network standard.
  • the air interface protocol consists of a physical layer (Physical layer), a data link layer (Data Link layer) and a network layer (Network layer) horizontally, vertically the user plane (User Plane) and control for data information transmission It is divided into a control plane for signal transmission.
  • the protocol layers are based on the lower three layers of the Open System Interconnection (OSI) reference model, which is widely known in communication systems, and includes L1 (first layer), L2 (second layer), and L3 (third layer). ) Can be separated.
  • OSI Open System Interconnection
  • the physical layer which is the first layer, provides an information transfer service using a physical channel.
  • the physical layer is connected to a medium access control layer on the upper side through a transport channel, and data between the medium access control layer and the physical layer is transmitted through the transport channel.
  • data is transferred between different physical layers, that is, between physical layers of a transmitting side and a receiving side through a physical channel.
  • the physical channel is composed of several subframes on the time axis and several sub-carriers on the frequency axis.
  • one subframe includes a plurality of symbols and a plurality of subcarriers on the time axis.
  • One subframe consists of a plurality of resource blocks, and one resource block consists of a plurality of symbols and a plurality of subcarriers.
  • the transmission time interval (TTI) which is a unit time for transmitting data, is 1 ms corresponding to one subframe.
  • the physical channels existing in the physical layer of the transmitting side and the receiving side are physical downlink shared channel (PDSCH), physical uplink shared channel (PUSCH) and physical downlink control channel (PDCCH), which are control channels, It may be divided into a Physical Control Format Indicator Channel (PCFICH), a Physical Hybrid-ARQ Indicator Channel (PHICH), and a Physical Uplink Control Channel (PUCCH).
  • PCFICH Physical Control Format Indicator Channel
  • PHICH Physical Hybrid-ARQ Indicator Channel
  • PUCCH Physical Uplink Control Channel
  • the PCFICH transmitted in the first OFDM symbol of a subframe carries a control format indicator (CFI) regarding the number of OFDM symbols (that is, the size of the control region) used for transmission of control channels in the subframe.
  • CFI control format indicator
  • the wireless device first receives the CFI on the PCFICH and then monitors the PDCCH.
  • the PCFICH does not use blind decoding and is transmitted on a fixed PCFICH resource of a subframe.
  • the PHICH carries a positive-acknowledgement (ACK) / negative-acknowledgement (NACK) signal for a UL hybrid automatic repeat request (HARQ).
  • ACK positive-acknowledgement
  • NACK negative-acknowledgement
  • HARQ UL hybrid automatic repeat request
  • the Physical Broadcast Channel (PBCH) is transmitted in the preceding four OFDM symbols of the second slot of the first subframe of the radio frame.
  • the PBCH carries system information necessary for the wireless device to communicate with the base station, and the system information transmitted through the PBCH is called a master information block (MIB).
  • MIB master information block
  • SIB system information block
  • the PDCCH includes resource allocation and transmission format of downlink-shared channel (DL-SCH), resource allocation information of uplink shared channel (UL-SCH), paging information on PCH, system information on DL-SCH, and random access transmitted on PDSCH. Resource allocation of higher layer control messages such as responses, sets of transmit power control commands for individual UEs in any UE group, activation of voice over internet protocol (VoIP), and the like.
  • a plurality of PDCCHs may be transmitted in the control region, and the terminal may monitor the plurality of PDCCHs.
  • the PDCCH is transmitted on an aggregation of one or several consecutive control channel elements (CCEs).
  • CCEs control channel elements
  • CCE is a logical allocation unit used to provide a PDCCH with a coding rate according to a state of a radio channel.
  • the CCE corresponds to a plurality of resource element groups.
  • the format of the PDCCH and the number of bits of the PDCCH are determined according to the correlation between the number of CCEs and the coding rate provided by the CCEs.
  • DCI downlink control information
  • PDSCH also called DL grant
  • PUSCH resource allocation also called UL grant
  • VoIP Voice over Internet Protocol
  • the Medium Access Control (MAC) layer is responsible for mapping various logical channels to various transport channels, and also for logical channel multiplexing to map multiple logical channels to one transport channel. Play a role.
  • the MAC layer is connected to the upper layer RLC layer by a logical channel, and the logical channel includes a control channel for transmitting information of a control plane according to the type of information to be transmitted. It is divided into a traffic channel that transmits user plane information.
  • the Radio Link Control (RLC) layer of the second layer adjusts the data size so that the lower layer is suitable for transmitting data to the radio section by segmenting and concatenating data received from the upper layer. It plays a role.
  • RLC Radio Link Control
  • TM Transparent mode, transparent mode
  • UM Un-acknowledged mode, no response mode
  • AM Acknowledged mode, Response mode
  • the AM RLC performs a retransmission function through an Automatic Repeat and Request (ARQ) function for reliable data transmission.
  • ARQ Automatic Repeat and Request
  • the Packet Data Convergence Protocol (PDCP) layer of the second layer is an IP containing relatively large and unnecessary control information for efficient transmission in a low bandwidth wireless section when transmitting IP packets such as IPv4 or IPv6. Performs Header Compression, which reduces the packet header size. This transmits only the necessary information in the header portion of the data, thereby increasing the transmission efficiency of the radio section.
  • the PDCP layer also performs a security function, which is composed of encryption (Ciphering) to prevent third-party data interception and integrity protection (Integrity protection) to prevent third-party data manipulation.
  • the radio resource control layer (hereinafter RRC) layer located at the top of the third layer is defined only in the control plane, and the settings (setting) and reset (Re) of radio bearers (abbreviated as RBs) are performed. It is responsible for the control of logical channels, transport channels, and physical channels in connection with setup and release.
  • RB means a service provided by the second layer for data transmission between the terminal and the E-UTRAN.
  • RRC connection If there is an RRC connection (RRC connection) between the RRC of the terminal and the RRC layer of the radio network, the terminal is in the RRC connected state (Connected mode), otherwise it is in the RRC idle state (Idle mode).
  • RRC connection If there is an RRC connection (RRC connection) between the RRC of the terminal and the RRC layer of the radio network, the terminal is in the RRC connected state (Connected mode), otherwise it is in the RRC idle state (Idle mode).
  • the RRC state refers to whether or not the RRC of the UE is in a logical connection with the RRC of the E-UTRAN. If the RRC state is connected, the RRC_CONNECTED state is called, and the RRC_IDLE state is not connected. Since the UE in the RRC_CONNECTED state has an RRC connection, the E-UTRAN can grasp the existence of the UE in units of cells, and thus can effectively control the UE. On the other hand, the UE in the RRC_IDLE state cannot identify the existence of the UE by the E-UTRAN, and the core network manages the unit in a larger tracking area (TA) unit than the cell.
  • TA tracking area
  • each TA is identified by a tracking area identity (TAI).
  • TAI tracking area identity
  • the terminal may configure a TAI through a tracking area code (TAC), which is information broadcast in a cell.
  • TAC tracking area code
  • the terminal When the user first turns on the power of the terminal, the terminal first searches for an appropriate cell, then establishes an RRC connection in the cell, and registers the terminal's information in the core network. Thereafter, the terminal stays in the RRC_IDLE state. The terminal staying in the RRC_IDLE state selects a cell (re) as needed and looks at system information or paging information. This is called camping on the cell.
  • the UE staying in the RRC_IDLE state makes an RRC connection with the RRC of the E-UTRAN through an RRC connection procedure and transitions to the RRC_CONNECTED state.
  • RRC_CONNECTED state There are several cases in which the UE in RRC_IDLE state needs to establish an RRC connection. For example, when uplink data transmission is necessary due to a user's call attempt, or when a paging signal is received from E-UTRAN, Send a response message.
  • a non-access stratum (NAS) layer located above the RRC layer performs functions such as session management and mobility management.
  • NAS non-access stratum
  • Evolved Session Management belonging to the NAS layer performs functions such as Default Bearer management and Dedicated Bearer management, and is responsible for controlling the terminal to use the PS service from the network.
  • the default bearer resource is characterized in that it is allocated from the network when it is connected to the network when it first accesses a specific Packet Data Network (PDN).
  • PDN Packet Data Network
  • the network allocates an IP address usable by the terminal so that the terminal can use the data service, and also allocates QoS of the default bearer.
  • LTE supports two types of bearer having a guaranteed bit rate (GBR) QoS characteristic that guarantees a specific bandwidth for data transmission and reception, and a non-GBR bearer having a best effort QoS characteristic without guaranteeing bandwidth.
  • GBR guaranteed bit rate
  • Non-GBR bearer is assigned.
  • a bearer having a QoS characteristic of GBR or non-GBR may be allocated.
  • the bearer allocated to the terminal in the network is called an evolved packet service (EPS) bearer, and when the EPS bearer is allocated, the network allocates one ID. This is called EPS Bearer ID.
  • EPS bearer ID This is called EPS Bearer ID.
  • MLR maximum bit rate
  • GRR guaranteed bit rate
  • AMBR aggregated maximum bit rate
  • an RRC layer, an RLC layer, a MAC layer, and a PHY layer located under the NAS layer are collectively referred to as an access stratum (AS).
  • AS access stratum
  • 5a is a flowchart illustrating a random access procedure in 3GPP LTE.
  • the random access procedure is used for the UE 10 to obtain UL synchronization with the base station, that is, the eNodeB 20 or to be allocated UL radio resources.
  • the UE 10 receives a root index and a physical random access channel (PRACH) configuration index (configuration index) from the eNodeB 20.
  • PRACH physical random access channel
  • configuration index configuration index
  • Each cell has 64 candidate random access preambles defined by a Zadoff-Chu (ZC) sequence, and the root index is a logical index for the UE to generate 64 candidate random access preambles.
  • ZC Zadoff-Chu
  • the PRACH configuration index indicates a specific subframe and a preamble format capable of transmitting the random access preamble.
  • UE 10 transmits a randomly selected random access preamble to eNodeB 20.
  • the UE 10 selects one of the 64 candidate random access preambles. Then, the corresponding subframe is selected by the PRACH configuration index.
  • UE 10 transmits the selected random access preamble in the selected subframe.
  • the eNodeB 20 Upon receiving the random access preamble, the eNodeB 20 sends a random access response (RAR) to the UE 10.
  • RAR random access response
  • the random access response is detected in two steps. First, the UE 10 detects a PDCCH masked with a random access-RNTI (RA-RNTI). The UE 10 receives a random access response in a medium access control (MAC) protocol data unit (PDU) on the PDSCH indicated by the detected PDCCH.
  • MAC medium access control
  • RRC radio resource control
  • an RRC state is shown depending on whether RRC is connected.
  • the RRC state refers to whether or not an entity of the RRC layer of the UE 10 is in a logical connection with an entity of the RRC layer of the eNodeB 20. If the RRC state is connected, the RRC state is connected. A state that is not connected is called an RRC idle state.
  • the E-UTRAN may determine the existence of the corresponding UE in units of cells, and thus may effectively control the UE 10.
  • the UE 10 in the idle state cannot be understood by the eNodeB 20, and is managed by a core network in units of a tracking area, which is a larger area than a cell.
  • the tracking area is a collection unit of cells. That is, the idle state UE (10) is identified only in the presence of a large area unit, in order to receive the normal mobile communication services such as voice or data, the terminal must transition to the connected state (connected state).
  • the UE 10 When the user first powers up the UE 10, the UE 10 first searches for a suitable cell and then remains in an idle state in that cell. When the UE 10 staying in the idle state needs to establish an RRC connection, the UE 10 establishes an RRC connection with the RRC layer of the eNodeB 20 through an RRC connection procedure and performs an RRC connection state ( connected state).
  • the UE in the idle state needs to establish an RRC connection. For example, a user's call attempt or an uplink data transmission is necessary, or a paging message is received from EUTRAN. In this case, the response message may be transmitted.
  • the RRC connection process is largely a process in which the UE 10 sends an RRC connection request message to the eNodeB 20, and the eNodeB 20 transmits an RRC connection setup message to the UE 10. And a process in which the UE 10 transmits an RRC connection setup complete message to the eNodeB 20. This process will be described in more detail with reference to FIG. 5B.
  • the UE 10 When the UE 10 in idle state attempts to establish an RRC connection due to a call attempt, a data transmission attempt, or a response to the paging of the eNodeB 20, the UE 10 first performs an RRC connection. A RRC connection request message is transmitted to the eNodeB 20.
  • the eNB 20 When the RRC connection request message is received from the UE 10, the eNB 20 accepts the RRC connection request of the UE 10 when the radio resources are sufficient, and establishes an RRC connection, which is a response message (RRC connection). setup) message is transmitted to the UE 10.
  • RRC connection a response message
  • the UE 10 When the UE 10 receives the RRC connection setup message, the UE 10 transmits an RRC connection setup complete message to the eNodeB 20. When the UE 10 successfully transmits an RRC connection establishment message, the UE 10 establishes an RRC connection with the eNodeB 20 and transitions to the RRC connected mode.
  • MTC Machine Type Communication
  • MTC communication is also called Internet of Things (IoT) communication because there is no human intervention. It is called CIoT to perform IoT communication on a cellular basis, not on a wireless LAN such as Wi-Fi. Unlike wireless LAN, CIoT supports not only IP-based communication but also IP-based communication.
  • IoT Internet of Things
  • 3GPP has improved a physical layer, that is, a Radio Access Technology (RAT).
  • RAT Radio Access Technology
  • the improved RAT is called Narrowband-IoT (NB-IoT).
  • CIoT devices using NB-IoT generally transmit and receive a small amount of data.
  • a CIoT device in order for a CIoT device to transmit and receive data, a large number of signals must be exchanged with the base station in advance. In order to transmit and receive such a small amount of data, transmitting and receiving a large number of control signals in advance may be inefficient.
  • EDT early data transmission
  • the method may include receiving a first message from a mobility management entity (MME).
  • MME mobility management entity
  • the first NAS message may include downlink data.
  • the method may further include determining that there is no additional data other than the downlink data based on the reception of the first NAS message.
  • the method may further include the base station transmitting an initial UE (Initial User equipment) message to the MME.
  • the initial UE message may include data of the UE according to the EDT.
  • the first NAS message may include a downlink non-access-stratum transport message.
  • the method may further include the base station transmitting a UE context resume request message to the MME.
  • one disclosure of the present specification provides a method for transmitting uplink (UL) data according to Early Data Transmission (EDT) by a wireless device including a Radio Resource Control (RRC) layer and an upper layer.
  • the method includes obtaining a release assistance indication (RAI) from the upper layer; Determining whether EDT is applicable based on the RAI; If it is determined that the EDT is applicable, the method may include transmitting an RRC request message including the UL data.
  • RRC Radio Resource Control
  • an RRC establishment cause and a call type may be further obtained.
  • the RRC request message including the UL data may be transmitted through the third message of the random access procedure.
  • the RRC request message may include one or more of an EPS bearer ID and an LC (Logical Channel) ID.
  • the RAI may indicate that subsequent UL data is not expected or only one DL (Downlink) data for the UL data may be expected.
  • the RRC request message may be an RRC connection resumption request message.
  • an RRC connection resumption procedure may not be performed.
  • the RRC request message may be a different message from the RRC connection resume request message.
  • one disclosure of the present specification provides a method for transmitting uplink (UL) data according to Early Data Transmission (EDT) by a wireless device including a Radio Resource Control (RRC) layer.
  • the method includes transmitting a third message of a random access procedure to a base station; And receiving a fourth message of a random access procedure from the base station.
  • the third message may include an RRC connection resume request message for performing an RRC connection resume procedure in an RRC suspend state.
  • the RRC connection resume request message may include the UL data according to the EDT.
  • the fourth message may include DL (Downlink) data.
  • the fourth message may include one or more of an RRC connection resume message, an RRC connection setup message, and an RRC connection rejection message.
  • one disclosure of the present specification provides a wireless device for transmitting uplink (UL) data according to Early Data Transmission (EDT).
  • the wireless device includes a transceiver; And a processor that controls the transceiver and includes a radio resource control (RRC) layer and an upper layer.
  • RRC radio resource control
  • the RRC layer of the processor obtains Release Assistance Indication (RAI) from the upper layer, the RRC layer may determine whether EDT is applicable based on the RAI. If it is determined that the EDT is applicable, the RRC layer of the processor may transmit an RRC request message including the UL data.
  • RAI Release Assistance Indication
  • the CIoT device can perform EDT (Early Data Transmission), thereby enabling power saving.
  • 1 is a structural diagram of an evolved mobile communication network.
  • Figure 2 is an exemplary view showing the architecture of a general E-UTRAN and a general EPC.
  • FIG. 3 is an exemplary diagram illustrating a structure of a radio interface protocol in a control plane between a UE and an eNodeB.
  • FIG. 4 is another exemplary diagram illustrating a structure of a radio interface protocol in a user plane between a terminal and a base station.
  • 5a is a flowchart illustrating a random access procedure in 3GPP LTE.
  • RRC radio resource control
  • MTC machine type communication
  • FIG. 7 shows a series of procedures that a CIoT device performs for data communication.
  • FIG. 8 is a signal flow diagram illustrating a suspension procedure initiated by a base station.
  • FIG. 9 is a signal flow diagram illustrating a connection resumption procedure initiated by a CIoT device.
  • 10A and 10B illustrate a procedure of transmitting data by a CIoT device according to control plane (CP) CIoT EPS optimization.
  • CP control plane
  • 11 illustrates a procedure of transmitting data by a CIoT device according to user plane (UP) CIoT EPS optimization.
  • UP user plane
  • 12A and 12B are exemplary views illustrating transmission and reception of a context resume request message between the base station and the MME illustrated in FIG. 11.
  • FIG. 13 is an exemplary flow diagram illustrating a procedure for transmitting data early according to an EDT.
  • 14A and 14B are exemplary flowcharts illustrating a procedure of transmitting data according to an EDT.
  • 16 is a block diagram illustrating a configuration of a CIoT device 100 and a network device according to an embodiment of the present invention.
  • the present invention is described based on the Universal Mobile Telecommunication System (UMTS) and the Evolved Packet Core (EPC), the present invention is not limited to such a communication system, but also to all communication systems and methods to which the technical spirit of the present invention can be applied. Can be applied.
  • UMTS Universal Mobile Telecommunication System
  • EPC Evolved Packet Core
  • first and second may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another.
  • first component may be referred to as the second component, and similarly, the second component may also be referred to as the first component.
  • a component When a component is said to be connected or connected to another component, it may be directly connected to or connected to the other component, but other components may be present in between. On the other hand, when a component is mentioned as being directly connected or directly connected to another component, it should be understood that no other component exists in the middle.
  • a user equipment UE
  • the illustrated UE may be referred to in terms of terminal, mobile equipment (ME), and the like.
  • the UE may be a portable device such as a laptop, a mobile phone, a PDA, a smart phone, a multimedia device, or a non-portable device such as a PC or a vehicle-mounted device.
  • UMTS Abbreviation for Universal Mobile Telecommunication System, which means the third generation mobile communication network.
  • UE / MS means User Equipment / Mobile Station, terminal equipment.
  • EPS stands for Evolved Packet System and means a core network supporting a Long Term Evolution (LTE) network.
  • LTE Long Term Evolution
  • UMTS evolved network
  • PDN Public Data Network
  • Independent network where the server providing the service is located
  • PDN connection Connection from the terminal to the PDN, that is, association (connection) between the terminal represented by the IP address and the PDN represented by the APN.
  • PDN-GW Packet Data Network Gateway
  • Network node of EPS network that performs UE IP address allocation, Packet screening & filtering, Charging data collection
  • Serving GW Network node of EPS network that performs mobility anchor, packet routing, idle mode packet buffering, Triggering MME to page UE function
  • PCRF Policy and Charging Rule Function
  • APN Access Point Name
  • the name of the access point managed by the network which is provided to the UE. That is, a string that refers to or distinguishes a PDN.
  • PDN the name of the access point managed by the network. That is, a string that refers to or distinguishes a PDN.
  • PDN the name of the access point managed by the network. That is, a string that refers to or distinguishes a PDN.
  • PDN Access Point Name
  • the P-GW passes through the P-GW.
  • the name (string) predefined within the network to find this P-GW (example) internet.mnc012.mcc345.gprs
  • Tunnel Endpoint Identifier End point ID of a tunnel established between nodes in a network, and is set for each section in bearer units of each UE.
  • NodeB A base station of a UMTS network, which is installed outdoors, and a cell coverage scale corresponds to a macro cell.
  • eNodeB A base station of an evolved packet system (EPS), which is installed outdoors, and a cell coverage size corresponds to a macro cell.
  • EPS evolved packet system
  • NodeB A term referring to NodeB and eNodeB.
  • MME Mobility Management Entity
  • a session is a channel for data transmission.
  • the unit may be a PDN, a bearer, or an IP flow unit.
  • the difference in each unit can be divided into the entire target network unit (APN or PDN unit), the QoS classification unit (Bearer unit), and destination IP address unit as defined in 3GPP.
  • PDN connection (connection) A connection from the terminal to the PDN, that is, the association (connection) between the terminal represented by the IP address and the PDN represented by the APN.
  • UE Context Context information of UE used to manage UE in the network, ie Context Information composed of UE id, mobility (current location, etc.), session attributes (QoS, priority, etc.)
  • OMA DM Open Mobile Alliance Device Management
  • OMA DM Open Mobile Alliance Device Management
  • OAM Operaation Administration and Maintenance
  • OAM is a group of network management functions that provides network fault indication, performance information, and data and diagnostic functions.
  • NAS Configuration MO (Management Object): A MO (Management Object) used to set (set) parameters related to NAS functions to the UE.
  • NAS Non-Access-Stratum: Upper stratum of the control plane (control plane) between the UE and the MME. Supports mobility management, session management, and IP address management between UE and network
  • MM (Mobility Management) operation / procedure An operation or procedure for mobility control / management / control of a UE.
  • the MM operation / procedure may be interpreted as including one or more of the MM operation / procedure in the CS network, the GMM operation / procedure in the GPRS network, and the EMM operation / procedure in the EPS network.
  • the UE and the network nodes (MME, SGSN, MSC) send and receive MM messages to perform MM operation / procedure.
  • SM (Session Management) operation / procedure An operation or procedure for controlling / managing / processing / handling a user plane and / or bearer context / PDP context of a UE.
  • SM operation / procedure may be interpreted as including one or more of SM operation / procedure in GPRS network and ESM operation / procedure in EPS network.
  • the UE and the network nodes (MME, SGSN) exchange SM messages to perform SM operations / procedures.
  • PLMN Abbreviation for Public Land Mobile Network, which means the network identification number of the operator.
  • HPLMN Home PLMN
  • VPLMN Visited PLMN
  • CIoT Abbreviation for Cellular Internet of Things, which means performing based on IoT communication.
  • Narrowband-IoT For CIoT, means RAT (Radio Access Technology) improved in 3GPP. That is, it means a network operated with a bandwidth of up to 180 kHz (corresponding to one PRB).
  • RAT Radio Access Technology
  • Control plane CIoT EPS optimization signaling optimization on the control plane to enable efficient transmission of user data (IP-based or non-IP-based or SMS-based user data)
  • User plane CIoT EPS optimization Signaling optimization on the user plane to enable efficient transmission of user data (IP based or non-IP based or SMS based user data)
  • UEs that support CIoT EPS optimization UEs that support control plane CIoT EPS optimization or user plane CIOT EPS optimization and one or more other CIoT EPS optimizations
  • NB-S1 mode refers to a mode that operates with improved radio access technology (RAT) for narrowband (NB) IoT.
  • RAT radio access technology
  • NB narrowband
  • WB-S1 mode This refers to a mode that operates with general RAT, not RAT improved for NB IoT.
  • Machine type communication refers to communication between a machine, which excludes a person, and a device used here is called an MTC device.
  • the service provided through the MTC device is different from the communication service in which a person intervenes and may be applied to various categories of services.
  • MTC machine type communication
  • Machine Type Communication is an exchange of information through the base station 200 between MTC devices 100 without human interaction or information through a base station between the MTC device 100 and the MTC server 700. Say exchange.
  • the MTC server 700 is an entity that communicates with the MTC device 100.
  • the MTC server 700 executes an MTC application and provides an MTC specific service to the MTC device.
  • the MTC device 100 is a wireless device that provides MTC communication and may be fixed or mobile.
  • the MTC device may operate in a power saving mode (hereinafter, referred to as 'PSM').
  • the MTC device When entering the PSM state, the MTC device deactivates an Access Stratum (AS), so the PSM is similar to a power off state.
  • AS Access Stratum
  • the MTC device may exist as registered in the network, and thus, the MTC device does not need to reattach to the network and does not need to re-establish a PDN connection. As such, the PSM state and the power-off state are differentiated.
  • a mobile originated event such as periodic TAU / RAU or uplink data generation or detachment causes the MTC device to initiate some procedure in the network. Until you do that, you stay in the PSM state.
  • the MTC device Even if the MTC device is in the PSM state, it may leave the PSM at any time when a mobile originating service is required. That is, even in the PSM state, the MTC device may activate the access layer (AS) at any time for the mobile originated service and resume operation of the idle mode.
  • AS access layer
  • the MME may know that the MTC device has entered the PSM state, and therefore paging is impossible.
  • the mobile terminating service cannot be immediately received.
  • a signal after a periodic tracking area update (TAU) or routing area update (RAU) procedure is received for a mobile terminating service. It may respond only during an active time period after a mobile originated event such as a transmission or data transmission.
  • the PSM is only suitable for MTC devices that require infrequent outgoing and mobile terminating services and only for MTC devices that can tolerate a certain latency in communication.
  • the MTC device must request an active time long enough to enable the reception of potential mobile terminated services or data such as SMS.
  • the MTC device If the MTC device wishes to use the PSM, the MTC device must request the value of the active time during every attach and TAU / RAU procedure. If the network supports PSM and the MTC device accepts to use the PSM, it assigns a value of an active time to the MTC device. The network may determine an activation time value to be allocated to the MTC device in consideration of the activation time value requested by the MTC device and the MME / SGSN configuration. If the value of the activation time allocated by the network is not satisfactory, the MTC device may request the value of its desired activation time only during the next TAU / RAU procedure period.
  • PTC-applicable MTC devices request periodic TAU / RAU timer values suitable for latency / responsiveness for mobile terminated services to the network during attach and TAU / RAU procedures. Done. If the network assigns a periodic TAU / RAU timer value to the MTC device but the MTC device is not satisfied, the MTC device only wants its own periodic TAU / RAU during the next TAU / RAU procedure. You can request a timer value.
  • MTC communication is also called Internet of Things (IoT) communication because there is no human intervention. It is called CIoT to perform IoT communication on a cellular basis, not on a wireless LAN such as Wi-Fi. Unlike wireless LAN, CIoT supports not only IP-based communication but also IP-based communication.
  • IoT Internet of Things
  • 3GPP has improved a physical layer, that is, a Radio Access Technology (RAT).
  • RAT Radio Access Technology
  • the improved RAT is called Narrowband-IoT (NB-IoT).
  • the improved RAT for the NB-IoT uses a physical layer optimized for very low power consumption (eg, carrier bandwidth is 180 kHz, subcarrier spacing is 3.75 kHz or 15 kHz).
  • the CIoT device can operate in a network operated with an improved RAT for NB-IoT, that is, a bandwidth of up to 180 kHz (corresponding to one PRB). .
  • the CIoT device Even if the CIoT device transmits and receives a small amount of data, the CIoT device has to send and receive a lot of signaling with the network in advance. This will be described with reference to FIG. 7.
  • FIG. 7 shows a series of procedures that a CIoT device performs for data communication.
  • the CIoT device 100 performs a random access procedure for data communication. That is, the CIoT device 100 transmits a first message MSG1, for example, a random access preamble, to the base station 200. The CIoT device 100 receives a second message MSG2, for example, a random access response message, from the base station 200. Then, the CIoT device 100 transmits a third message (MSG3), for example, a scheduled message, to the base station 200. The scheduled message may include an RRC Connection Request message. Thereafter, the CIoT device 100 receives a fourth message MSG4, for example, an RRC connection setup message from the base station 200. Then, the CIoT device 100 transmits a fifth message MSG5, for example, an RRC connection complete message, to the base station 200. The RRC connection complete message may include a NAS service request message.
  • MSG3 for example, a random access response message
  • the base station 200 transmits an S1-AP-based Initial UE message to the MME 510.
  • the initial UE message may include the NAS service request message.
  • the MME 510 transmits an S1-AP based initial context setup request message to the base station.
  • the base station 200 transmits an RRC security mode command (SMC) to the CIoT device and receives an RRC security mode command response.
  • SMC RRC security mode command
  • the base station 200 transmits an RRC connection reconfiguration message to the CIoT device 100, and the CIoT device 100 sends an RRC connection reconfiguration complete message. Transmit to base station.
  • the base station 200 transmits an S1-AP based initial context setup complete message to the MME 510. Then, the MME 510 transmits a bearer modification request message to the S-GW 520 and receives a bearer modification response message from the S-GW 520.
  • the CIoT device 100 may perform data communication.
  • the base station 200 transmits an S1-AP based UE context release request message to the MME 510. Then, the MME 510 transmits a Release Access Bearer message to the S-GW 520. Then, the S-GW 510 transmits a Release Access Bearer Response message to the MME 510. The MME 510 transmits a S1-AP based UE context release command message to the base station.
  • the base station 200 transmits an RRC Connection Release message to the UE, and transmits an RRC Connection Release Complete message to the MME 510.
  • the CIoT device is expected to be located at a fairly high density within the coverage of the base station, in which case a significant number of signals can overload the network.
  • This procedure is used by the network to suspend connections if the UE and the network support User Plane CI Optimization EPS Optimization.
  • FIG. 8 is a signal flow diagram illustrating a suspension procedure initiated by a base station.
  • the base station transmits an S1 UE Context Suspend Request message to the MME to initiate a connection suspension procedure. Specifically, the base station suspends the RRC connection of the CIoT device and instructs the MME to enter the ECM-IDLE. Data related to the S1-AP association, UE context and bearer context needed to resume the connection is maintained at the base station, CIoT device and MME.
  • the base station may include information on the recommended cell and the base station for paging in the S1 UE Context Suspend Request message. If available, the MME should store the information when used when paging a CIoT device.
  • the base station includes information on enhanced (ie, extended) coverage if possible in the S1 UE Context Suspend Request message.
  • the MME sends a Release Bearer Request message to the Serving GW requesting the release of all S1-U bearers for the CIoT device.
  • the S-GW releases all base station related information (address and downlink TEID) for the CIoT device and responds to the MME with a Release Bearer Access Response message.
  • the S-GW begins to buffer the received downlink packet for the CIoT device and starts the network trigger service request procedure.
  • the S-GW informs the MME of the release of the S1-U bearer via a Release Access Bearer Response message.
  • the MME sends a S1-AP: UE Context Suspend Response message to the base station to successfully terminate the connection suspend procedure initiated by the base station. See TS 36.413 [36].
  • the base station transmits an RRC connection suspend message to suspend the RRC connection to the CIoT device.
  • the AS layer of the CIoT device When the AS layer of the CIoT device receives the RRC connection suspend message, it transmits an indication indicating that the RRC connection is suspended to the NAS layer.
  • the NAS layer of the CIoT device Upon receiving the indication, the NAS layer of the CIoT device enters an EMM idle state. The NAS layer considers that the NAS signaling connection has been released. However, the NAS layer does not consider that even the safe exchange of NAS messages has ended.
  • This procedure is used for resuming ECM connections by CIoT devices when the CIoT device and the network support user plane CIoT EPS optimization and the CIoT device has stored the information needed to perform the connection resumption procedure. Specifically, it is as follows.
  • the NAS layer of the CIoT device While in the EMM idle state based on the pause indication, when the procedure of using the NAS message is initiated, the NAS layer of the CIoT device requests the AS layer to resume the RRC connection. To this end, the NAS layer delivers an RRC establishment cause and a call type to the AS layer. At this time, the NAS message has not yet been delivered to the AS layer.
  • the NAS layer Upon receiving an indication from the AS layer indicating that an RRC connection has been resumed, the NAS layer enters an EMM connected state. If the NAS message that is not delivered to the AS layer and is waiting is a service request message, a Control Plane Service Request (CPSR) message, or an Extended Service Request message, the NAS The message is not delivered. If the NAS message is another message, the NAS layer encrypts the message. And after the NAS layer enters the EMM connected state, it sends the message as a ratio.
  • CPSR Control Plane Service Request
  • FIG. 9 is a signal flow diagram illustrating a connection resumption procedure initiated by a CIoT device.
  • the CIoT device initiates a random access procedure for the base station
  • the CIoT device triggers an RRC connection resumption procedure that includes information needed by the base station to access the AS context stored for the CIoT device.
  • E-UTRAN performs security checks.
  • EPS bearer state synchronization is performed between the CIoT device and the network. That is, when the radio bearer is not configured for the basic EPS bearer, the CIoT device does not set the radio bearer and internally removes the EPS bearer other than the control plane CIoT EPS bearer.
  • the base station notifies the MME that the RRC connection of the CIoT device has been resumed through the S1-AP UE context resumption request message including the cause of the RRC resumption. If the base station cannot accept all suspended bearers, the base station should include information about this fact in the rejected EPS bearer list.
  • the MME goes into the ECM-CONNECTED state. The MME confirms that the UE has returned to the base station associated with the MME storing data related to the S1-AP association, the UE context and the bearer context.
  • the MME responds to resumption of connection via an S1-AP UE context resume response message.
  • the base station If the list of E-RABs cannot be resumed, the base station resets the radio bearer.
  • UL (uplink) data transmitted by the CIoT device can now be forwarded to the S-GW by the base station.
  • the base station transmits UL data to the S-GW address and TEID stored during the connection suspension procedure.
  • the S-GW transmits UL data to the PDN GW.
  • the MME sends a Modify Bearer Request message.
  • the Modify Bearer Request message may include information on an address, S1 TEID, (DL), downlink packet delay notification request, RAT type, etc., to the base station for the EPS bearer.
  • S-GW sends Modify Bearer Response message.
  • the message includes the address of the S-GW, TEID.
  • Control plane (SRB +) for sending NAS messages such as attach and tracking area update (TAU) in the NAS layer without using user plane setup (DRB + S1-U path) required for existing data transfer Data is transmitted through S1-AP).
  • the S11-U path is newly defined between the MME and the S-GW. Data may be transmitted through the newly defined S11-U path.
  • the security of the data is used in the NAS layer security instead of the security of the AS layer.
  • a security mode command (SMC) procedure or the like may be omitted.
  • the required RRC signaling is reduced even when switching the RRC connected mode.
  • 10A and 10B illustrate a procedure of transmitting data by a CIoT device according to control plane (CP) CIoT EPS optimization.
  • CP control plane
  • the CIoT device 100 may include data in a NAS service request message included in a fifth message MSG5 of the random access procedure, for example, an RRC connection complete message, and transmit the data. have.
  • the CIoT device 100 may transmit data in the fifteenth process. However, in FIG. 10A, the CIoT device 100 may transmit data in the fifth process. It can be efficiently transmitted.
  • the context is maintained.
  • the CIoT device performs an RRC suspend procedure instead of performing an S1 release procedure. Therefore, when the CIoT device requests the RRC connection again, it can quickly switch from the RRC idle mode to the RRC connected mode. That is, instead of performing a service request procedure for setting up a user plane, an RRC connection resume procedure is performed. Therefore, the number of RRC signals to be transmitted and received in order for the CIoT device to switch from the RRC idle mode (EMM-IDLE) to the RRC connected mode (EMM-CONNECTED) is significantly reduced.
  • 11 illustrates a procedure of transmitting data by a CIoT device according to user plane (UP) CIoT EPS optimization.
  • UP user plane
  • the NAS layer of the CIoT device 100 triggers a service request procedure, a TAU procedure, or an attach procedure.
  • the NAS layer generates a NAS message and waits.
  • the NAS layer delivers the RRC establishment cause and call type to the AS layer. At this time, the NAS message is not delivered.
  • the AS layer of the CIoT device 100 transmits a first message (ie, MSG1) (eg, a random access preamble) of a random access procedure to the base station 200.
  • the CIoT device 100 receives a second message (ie, MSG2) (eg, a random access response) of a random access procedure from the base station 200.
  • the AS layer of the CIoT device 100 includes the RRC connection resumption request message in the third message (ie, MSG3) (eg, scheduled message) of the random access procedure and transmits the message.
  • a resume ID is included in the RRC connection resume request message.
  • the base station 200 transmits a fourth message (ie, MSG4) (eg, RRC connection resumption completion message) of a random access procedure to the CIoT device 100.
  • MSG4 eg, RRC connection resumption completion message
  • the RRC connection resume complete message includes a resume ID and a bearer descriptor.
  • the base station 200 transmits an S1-AP based UE context resumption request message to the MME 510.
  • the MME sends a context resume response message to the base station.
  • the AS layer of the CIoT device 100 transmits an indication indicating the success of resumption to the NAS layer.
  • the NAS layer enters an EMM connected mode.
  • the NAS layer forwards the waiting NAS message to the AS layer.
  • the AS layer of the CIoT device 100 transmits a fifth message (ie, MSG5) (eg, RRC connection resumption completion message) of a random access procedure to the base station 200.
  • the resume complete message may include the NAS message.
  • the CIoT device 100 may transmit data in a fifteenth process. However, in FIG. 11, the CIoT device 100 may transmit data in an eleventh process. It can be improved efficiently.
  • 12A and 12B are exemplary views illustrating transmission and reception of a context resume request message between the base station and the MME illustrated in FIG. 11.
  • the base station sends a UE context resume request message to request resume.
  • the MME accepts the resumption, as shown in FIG. 12A
  • the UE context resume response message is transmitted.
  • a UE context resume failure message is sent.
  • the base station If the MME transmits a context resume failure message, the base station performs an RRC release procedure.
  • the MME cannot resume one E-RAB, by sending a context resume failure message to the base station, the CIoT device related logic S1 connection is released.
  • the base station receives the failure message, it releases the RRC connection and releases all related signaling and user data transmission resources.
  • EDT EDT
  • DL data is transmitted between MSG1 and MSG5 of the random access procedure, that is, DL data through MSG2 or MSG4 for DL data and UL data through MSG3 for UL data.
  • the CIoT device can quickly perform early transmission. Once the early transmission is complete, the CIoT device can save power by disconnecting the RRC early.
  • FIG. 13 is an exemplary flow diagram illustrating a procedure for transmitting data early according to an EDT.
  • the upper layer of the CIoT device 100 triggers the connected mode.
  • the CIoT device 100 transmits MSG1 (ie, random access preamble) of a random access procedure.
  • the MSG1 may indicate for early data transmission.
  • the base station 200 transmits the MSG2 (ie, random access response message) of the random access procedure.
  • the CIoT device 100 resumes DRB and SRB when transmitting the UP data in the stored CIoT configuration.
  • the AS layer (ie, RRC layer) of the CIoT device 100 enters an RRC connected mode.
  • the AS layer (ie, RRC layer) of the CIoT device 100 transmits MSG3 of a random access procedure.
  • the MSG3 includes an RRC message.
  • the RRC message may include a NAS message including a NAS PDU, and in the case of an UP EDT, the MSG3 may include UP data.
  • the base station 200 may include a NAS PDU in an S1-AP based Initial UE message and transmit the same.
  • the base station may transmit UL data after transmitting the S1-AP based UE context resumption request message.
  • the MME 510 may deliver a DL NAS Transport message including a NAS PDU to the base station 200. .
  • DL data may be delivered to the base station 200 through the S1-U interface.
  • the base station 200 and the MME 510 may transmit and receive an S1-AP based UE context release message.
  • the base station 200 may deliver a NAS PDU including DL data to the CIoT device 100.
  • the base station 200 may transmit DL data to the CIoT device 100.
  • the EDT as described above has the following problems.
  • a CIoT device using CIoT EPS optimization includes an indication indicating whether CP CIoT EPS optimization or UP CIoT EPS optimization is included in MSG5 of the random access procedure.
  • the NAS layer of the CIoT device informs the AS layer of the requested CIoT EPS optimization. That is, in NB (narrowband) communication, when the NAS layer of the CIoT device requests an RRC connection to the AS layer and requests the use of an EMM registered state without a PDN connection, or requests the use of UP CIoT EPS optimization.
  • the CIoT device delivers an indication of the requested CIoT EPS optimization to the AS layer. If the CIoT device requests the use of S1-U data delivery without using the UP CIoT optimization, the CIoT device sends an indication for the UP CIoT EPS optimization to the AS layer.
  • the NAS layer of the CIoT device requests an RRC connection to the AS layer, requesting the use of an EMM registered state without a PDN connection, or using CP CIoT EPS optimization or UP CIoT EPS optimization.
  • the CIoT device delivers an indication of the requested CIoT EPS optimization to the AS layer.
  • the AS layer generates an RRC connection setup complete message and sends the RRC connection resumption complete message to MSG5.
  • the AS layer includes an attachWithoutPDN-connectivity indication in the message.
  • the AS layer includes an up-CIoT-EPS-Optimization indication or a cp-CIoT-EPS-Optimization indication in the message according to the request of the NAS layer.
  • UL data is included in the MSG3 and transmitted.
  • the CIoT device receives the MSG4, the UL data is not transmitted and the RRC connection is released.
  • the base station updates the UL data. You do not know whether to send on the path or on the CP path.
  • a simple solution for solving this problem may be that only one of the CP EDT and the UP EDT is supported in the EDT.
  • the base station determines whether to accept the resume. If the base station accepts the resumption, the base station transmits the MSG4 (including the RRC connection resume message) to the CIoT device, and then transmits a UE context resume request message to the MME. The CIoT device receiving the MSG4 internally performs the release. The CIoT device then transitions to the EMM idle state. In this case, the CIoT device may switch to the eDRX or PSM mode to save power.
  • MSG4 including the RRC connection resume message
  • the MME receives the UE context resume request message, but can not resume any one of the E-RAB, by sending a UE context resume failure message to the base station, the logical S1-connection associated with the CIoT device is released. .
  • the base station Upon receiving the UE context resume failure message, the base station releases the RRC connection and releases all associated signaling. The base station also releases resources for user data transfer.
  • the MME sends a UE context resume failure message to the base station, and the base station performs an RRC connection release procedure according to the failure message.
  • the CIoT device upon receiving the MSG4, the CIoT device performs the RRC connection release as described above, and then switches to the EMM-IDLE mode and further to eDRX or PSM. For this reason, the base station cannot perform the RRC disconnection.
  • the problem here is that the CIoT device switches to the EMM idle state and not to the eDRX or PSM state without knowing whether the UL data transmission is successful or failed. If the CIoT device can receive the RRC connection release request message from the base station, it is possible to infer whether the UL data is successful through the message, but the CIoT device determines that the success of the UL data has not been received. Can not.
  • the CIoT device in order to use the PSM, the CIoT device needs to request the MME to accept the use of the PSM through the TAU procedure.
  • the CIoT device supports the EDT, the UL data is transmitted through the MSG3 of the random access procedure, and the RRC connection is released before the TAU request message is transmitted.
  • the CIoT device cannot use the PSM, and thus the power saving effect cannot be obtained.
  • the disadvantage that occurs when the PSM cannot be used may be greater.
  • the CIoT device can support the EDT.
  • the CIoT device transmits UL data when the CIoT device is in the EMM idle state according to the pause indication and in the RRC idle state according to the pause indication, the resume procedure is performed.
  • the CIoT device and the network node perform an operation of checking each other's capability information for the EDT according to one of the following options.
  • the CIoT device should inform the network node of the capability information of its EDT. To this end, the CIoT device may transmit after setting the EDT support bit to “EDT supported” in the capability information field in the attach request message for performing the attach procedure or the TAU request message for performing the TAU procedure. If the network node (eg, MME) receiving the attach request message or the TAU request message also supports the EDT, the EDT supported " is set in the EPS network feature support field in the attach accept message or the TAU accept message. , May be transmitted to the CIoT device.
  • the network node eg, MME
  • an operation of checking bearer information supporting EDT may be performed.
  • the CIoT device transmits to the network node an attach request message or a TAU request message including bearer information supporting the EDT in addition to the capability information for the EDT support.
  • the network node (eg, MME) confirms the attach request message or the TAU request message.
  • the network node also supports the EDT, an attach accept message or a TAU accept message including bearer information to be used for the EDT among the bearers supporting the EDT is transmitted.
  • the network node eg, MME
  • the network node checks the bearer context of the current CIoT device, and provides information on the bearer supporting the EDT according to the confirmation. It may be included in the attach accept message or the TAU accept message and transmitted to the CIoT device.
  • Capability information verification for EDT support may be performed according to option A.
  • Confirmation of the bearer supporting the EDT may be performed as follows.
  • ESM Evolved Session Management Protocol
  • PDN connection request procedure bearer resource allocation request procedure
  • bearer resource modification procedure information about a bearer supporting EDT is included in a protocol configuration option (PCO) or an extended PCO.
  • PCO protocol configuration option
  • extended PCO extended PCO
  • EDT When the network node (eg, P-GW) supports the EDT for the bearer, an indication indicating that the EDT is supported is included in the PCO or the Extended PCO and transmitted to the CIoT device.
  • ESM procedure ESM procedure
  • MME can also check bearer information supporting EDT.
  • the "EDT supported” may be expressed by subdividing the CP EDT and the UP EDT. In other words, when CP EDT is supported, it may be expressed as "CP EDT supported” and when "UP EDT is supported”.
  • the second disclosure relates to a solution for solving the aforementioned first problem.
  • MSG3 ie, RRC connection resumption request message
  • MSG3 ie, RRC connection resumption request message
  • MSG3 ie, RRC connection resumption request message
  • CP path that is, CP data (or data transmitted by CP EDT)
  • CP Information on whether the EDT scheme is used or whether to transmit on the UP path (that is, whether the UP data scheme or the UP EDT scheme is used)
  • the operation of the CIoT device is as follows.
  • the application layer of the CIoT device delivers data to be transmitted to a lower layer (for example, NAS layer or AS layer), whether the data to be transmitted is CP data (or data transmitted by CP EDT) or UP data (or UP). It also sends an indication indicating whether the data is transmitted by the EDT.
  • a lower layer for example, NAS layer or AS layer
  • the CIoT device may consider the following cases according to the triggering path internally.
  • the application layer of the CIoT device sends the information to the AS layer via the NAS layer.
  • the NAS layer may transmit the EPS bearer ID information to transmit the information to the AS layer.
  • the point in time when the NAS layer delivers the information or EPS bearer ID information to the AS layer becomes a time point for transmitting the RRC establishment cause and the call type when the resumption procedure is triggered. Specifically, it is as follows.
  • the CIoT device requests the lower layer to resume the RRC connection.
  • the NAS layer delivers an indication for the EDT to the AS layer.
  • the NAS layer delivers information on the EPS bearer ID to which data is transmitted, the RRC establishment cause, and the call type to the AS layer.
  • the AS layer of the CIoT device includes the data in the MSG3 (including the RRC connection resumption request message) of the random access procedure and transmits the data to the base station.
  • the base station may accept or reject the resume request or indicate a fallback. If resume is refused or a fallback is instructed, an attempt is made to retransmit data through the conventional operation of the AS layer of the CIoT device.
  • the generated NAS message may be a control plane service request (CPSR) message. If resumption is refused or a fallback is instructed, retransmission is made through the data contained in the CPSR.
  • CPSR control plane service request
  • the information may be directly transmitted to the AS layer without passing through the NAS layer. That is, the application layer of the CIoT device may directly transfer the information to the AS layer.
  • the AS layer may know the EPS bearer ID to which data is transmitted.
  • the AS layer of the CIoT device determines that early transmission is necessary, and performs the following operation together with the resumption procedure.
  • the AS layer starts a random access procedure. Specifically, the AS layer of the CIoT device transmits MSG1, and upon successful reception of MSG2, transmits MSG3 (ie, including RRC connection resumption request message) including UL data to the base station.
  • MSG1 ie, including RRC connection resumption request message
  • the UL data is cryptographically secured and guaranteed by the AS security context (eg, authentication token, short MAC-I) stored in the AS layer of the CIoT device.
  • AS security context eg, authentication token, short MAC-I
  • the MSG3 of the random access procedure contains the following indication.
  • EPS bearer ID or LC (Logical Channel) ID.
  • LC Logical Channel
  • the base station When the base station receives the MSG3 including the UL data, it is checked whether the corresponding UL data is CP data (or data transmitted by the CP EDT) or UP data (or data transmitted by the UP EDT).
  • the EPS bearer ID or LC ID may be used to determine whether CP data (or data transmitted by CP EDT) or UP data (or data transmitted by UP EDT).
  • the base station transmits an S1-AP message to the MME as described below.
  • the base station may determine whether to resume the corresponding EPS bearer by checking the received EPS bearer ID or LC ID.
  • the base station transmits an RRC connection resume refusal message for notifying the CIoT device of the resumption refusal.
  • the rejection message may include cause information indicating a reason for the rejection.
  • the base station may immediately transmit CP data (or data transmitted by CP EDT) to the MME without performing resumption.
  • the UE context resumption request message may be transmitted to the MME.
  • the resume procedure is performed.
  • the base station sends a UE context resume request message to the MME.
  • the MME receives the UE context resume request message, the CIoT device resumes the EPS bearer desired to transmit, and then transmits a UE context resume response message to the base station. Meanwhile, even when the EPS bearer which the CIoT device wants to transmit is not resumed and another EPS bearer is resumed, the MME may transmit a UE context resume response message to the base station.
  • the base station transmits the EPS bearer ID received from the CIoT device in the UE context resumption request message in step 2).
  • the base station receives the LC ID from the CIoT device, it can find the EPS bearer ID mapped to the LC ID, and then include the found EPS bearer ID in the message.
  • the base station may generally generate and transmit a UE context resume request message.
  • the base station extracts the RRC connection resume request message in the MSG3, and in the RRC connection resume request message. Extract the included UL data.
  • the base station includes the extracted UL data in an S1-AP message and transmits it to the MME.
  • the S1-AP message may be a reuse or modification of a general UE context resume request message or an Initial UE message, or a newly defined message.
  • the S1-AP message may include a separate indication indicating that CP data (or data transmitted by CP EDT) is included. The specific operation is as follows.
  • An Information Element may be added as a container for CP data (or data transmitted by CP EDT) in the Initial UE message to include CP data (or data transmitted by CP EDT).
  • CP data (or data transmitted by CP EDT) may be included in the IE, or the CP data (or data transmitted by CP EDT) may be included in an existing NAS-PDU IE.
  • an indication indicating that the CP data (or data transmitted by the CP EDT) may be included.
  • E-RAB Failed To Resume List is not included.
  • CP data or data transmitted by CP EDT
  • CP data or data transmitted by CP EDT
  • CP data may be included in the newly added IE.
  • At least the message type, ID of S1-AP, may be included in the message.
  • the message includes CP data (or data transmitted by CP EDT).
  • the message may include an indication that separate CP data (or data transmitted by CP EDT) is included.
  • the UE context resume response message is transmitted to the base station.
  • the base station which receives this transmits corresponding UP data (or data transmitted by the UP EDT) through the resumed S1-U bearer without performing DRB setup with the CIoT device.
  • the base station may inform the CIoT device whether the UP data (or the data transmitted by the UP EDT) is successful.
  • the RRC message indicating whether the transmission is successful may be a general RRC message (eg, an RRC disconnection message) or a new RRC message.
  • the RRC message includes cause information indicating whether the UL data transmission has failed successfully.
  • the UE context resume failure message is transmitted to the base station.
  • the message includes cause information indicating whether or not the data transmission was successful.
  • the cause information may indicate a specific reason for the failure. For example, the cause information may indicate that the requested EPS bearer ID cannot be resumed.
  • the base station may inform the CIoT device of the corresponding cause information while transmitting an RRC connection release message or an RRC resumption rejection message.
  • the CIoT device receiving this recognizes that data transmission has failed.
  • the reason for the failure may be specifically recognized according to the cause information.
  • the MME If the optimization is not applied, the MME generates and transmits a UE context resume response message or a UE context resume failure message as conventionally.
  • the MME If the MME does not transmit CP data (or data transmitted by CP EDT) (rejects transmission), informs the CIoT device of the rejection and the reason for the rejection. To this end, the MME transmits an S1-AP message to the base station.
  • the S1-AP message may be a reuse or modification of a general S1-AP message (eg, a Downlink NAS Transport message or a UE context resumption failure message) or a newly defined message.
  • the S1-AP message used in the process 3-B determines which S1-AP message to use. For example, when an Initial UE message is used in step 3-B), when a Downlink NAS Transport message or a UE context resume request message is used, a UE context resume failure message is used.
  • the message may include cause information indicating the reason for the rejection.
  • DL data to be transmitted to the CIoT device is waiting for the MME, it is transmitted together with the base station.
  • the DL data may be included in the S1-AP message and transmitted.
  • the MME When the MME wants to transmit CP data (or data transmitted by CP EDT), it checks the EPS bearer ID to be transmitted and sends the CP data (or data transmitted by CP EDT) through an interface. Check if it should be sent. Specifically, the MME may check the PDN connection with the SCEF or P-GW based on the EPS bearer ID included in the message.
  • an S1-AP message may be transmitted to the base station or an S1 release procedure may be informed.
  • the S1-AP message may be a reuse or modification of a general S1-AP message (eg, Downlink NAS Transport message or UE context resume failure message), or may be a newly defined message.
  • the UE context resume failure message is used.
  • the message may include an indication indicating that transmission of CP data (or data transmitted by CP EDT) is successful.
  • the DL data is of a size that the base station can transmit in a general RRC message (e.g., MSG4 (i.e., RRC connection setup message, RRC connection rejection message, RRC connection resume message or RRC connection release message).
  • RRC message e.g., MSG4 (i.e., RRC connection setup message, RRC connection rejection message, RRC connection resume message or RRC connection release message).
  • Data i.e., data of a size that can be transmitted to the EDT
  • the MME or S-GW recognizes the allowed size information of the data and transmits it only to the base station if the DL data is the allowed size.
  • the operation may be performed only when there is no further buffered DL data other than the DL data for the CIoT device, specifically, the MME has DL data to be transmitted to the CIoT device and the DL data.
  • the base station when there is no longer buffered DL data, it may be notified to the base station.
  • a Downlink NAS Transport message including U including the DL data
  • an indication indicating that there is no additional data to be transmitted may be included in the Downlink NAS Transport message and transmitted.
  • the information about the allowed size of the data may be preset or signaling (e.g., from the base station to the MME and / or from the base station to the S-GW and / or Or MME or S-GW signaling through MME).
  • the MME determines whether the EDT is applied to the DL data.
  • the MME includes CP data (or data transmitted by CP EDT) in a NAS message (e.g., CPSR message) to deliver to lower layer (i.e., S1-AP layer), and It sends the 'EDT' indication to the lower layer to indicate that it is an EDT.
  • the lower layer transmits the NAS message including the CP data (or data transmitted by the CP EDT) and the EDT indication to the base station in an S1-AP message (eg, a downlink NAS transport message).
  • the S-GW determines whether to apply the EDT to the DL data.
  • the MME may inform the S-GW when performing process 4) that the EDT application is activated for a specific bearer.
  • the S-GW may know in advance through the first initiation whether EDT application for a specific bearer is activated. According to the above condition, when EDT is applied to DL data, the S-GW transmits UP data (or data transmitted by the UP EDT) to the base station. If the optimization of process 3-A) is applied, 'EDT' indication is sent to MME indicating EDT.
  • the MME delivers an 'EDT' indication indicating the EDT to the lower layer (that is, the S1-AP layer).
  • the lower layer transmits the EDT indication to the base station by including an S1-AP message (eg, a UE Context Release command message).
  • the S1-AP message including the DL data includes an indication indicating that the data is for EDT.
  • step 3-A If the corresponding DL data is UP data (or data transmitted by UP EDT), and the optimization of step 3-A) is applied, the following operation is performed.
  • the base station If there is a resumed / established bearer for transmitting the DL data (eg, data of the same bearer as the bearer of UL data transmitted in step 4), it is transmitted to the base station.
  • the DL data eg, data of the same bearer as the bearer of UL data transmitted in step 4
  • the resume procedure does not operate when the UL data or signaling transmission is not the same bearer data as the bearer of the UL data transmitted. Or unsuccessful), an additional S1-U bearer and DRB should be established for transmitting the DL data.
  • the S-GW transmits a downlink data notification (DDN) message to the MME.
  • DDN downlink data notification
  • the MME receiving the DDN transmits an E-RAB setup request message including the bearer information to establish the bearer.
  • the E-RAB setup request message includes an E-RAB ID and related information (eg, E-RAB level QoS parameters) of a bearer to transmit the DL data.
  • the MME receives and confirms the E-RAB setup response message that the E-RAB setup for the bearer was successfully performed and sends a DDN response message to the S-GW.
  • the S-GW Upon receiving the DDN response message, the S-GW transmits the DL data to a base station.
  • the MME performs a conventional operation for establishing an S1-U connection and a DRB as in the conventional operation. For example, if there is no UE context in the base station, an initial context setup procedure is performed. Or if the base station has a UE context, but the bearer is not activated, the E-RAB setup procedure is performed.
  • the base station When the base station receives the S1-AP message of process 4), it operates as described below. At this time, when the DL data is waiting (buffering), the base station transmits the DL data to the CIoT device.
  • step 4 if the MME succeeds in resuming the corresponding E-RAB bearer, and the MME transmits a UE context resume response message to the base station, the base station receiving the same transmits the data through the resumed S1-U bearer.
  • the message includes cause information indicating whether the data transmission was successful.
  • the cause information may indicate a specific reason for the failure. For example, the cause information may indicate that the requested EPS bearer ID cannot be resumed.
  • the base station checks whether the EPS bearer for transmitting the UL data received in the process 3) is resumed. When the EPS bearer is resumed, the base station transmits the data through the resumed S1-U bearer.
  • step 4 When the MME fails to resume in step 4) and transmits a UE context resume failure message to the base station,
  • CP data (or data transmitted by CP EDT), receive the S1-AP message described in step 4), and the base station recognizes the success or failure of the UL data transmission.
  • the CIoT device may attempt to retransmit through the RRC connection that is not released.
  • the CIoT device may retransmit the MSG5 (that is, the RRC Connection setup complete message) or another RRC message.
  • the base station When the base station receives the S1-AP message including the DL data described in step 4) and recognizes that there is no additional data to be transmitted, the base station includes the corresponding DL data in the MSG4 and attempts transmission to the CIoT device. If the DL data is CP data, it is included in the RRC message of the MSG4. If the DL data is UP data, the DL data may be transmitted in a separate DTCH from the RRC message of the MSG4. The base station checks whether the DL data can be included in the MSG4, and if the DL data has a size that can be transmitted to the MSG4, the base station transmits the DL data including the DL data.
  • the base station transmits an MSG4 that does not include the DL data according to the conventional operation (ie, after transmitting the RRC connection setup message) when the DL data is a size that cannot be included in the MSG4 or fails to transmit to the MSG4, the RRC connection is performed.
  • the DL data transmission is attempted or included in the DL data S1-AP message to the MME, and an indication indicating DL transmission failure is transmitted to the MME. .
  • the base station transmits an RRC message to the CIoT device.
  • the RRC message may be an RRC connection release message or another RRC message.
  • the RRC message includes cause information indicating the success or failure of the transmission.
  • the cause information may indicate a specific reason in case of failure. For example, the cause information may indicate failure of resuming the corresponding EPS bearer.
  • the DL data may be transmitted by being included in an existing RRC message (eg, an MSG4 (ie, an RRC connection setup message, an RRC connection rejection message, an RRC connection resume message, or an RRC connection release message)).
  • an existing RRC message eg, an MSG4 (ie, an RRC connection setup message, an RRC connection rejection message, an RRC connection resume message, or an RRC connection release message)
  • the RRC message other than the RRC connection release message may be used as the message for transmitting the DL data
  • the base station wants to transmit the RRC connection release message
  • the DL data is successfully transmitted to the AS layer of the CIoT device.
  • the RRC disconnection message can then be sent to the CIoT device.
  • an RRC message other than the RRC disconnection message may be transmitted.
  • the RRC message may be an RRC connection setup message or an RRC connection rejection message.
  • the CIoT device recognizes the success or failure of the UL data transmission.
  • the CIoT device may specifically recognize the reason according to the cause information. In case of failure, retransmission can be attempted. In case of failure, the CIoT device may determine whether to retransmit according to the cause information. If UL data fails and a retransmission can be attempted, the NAS layer or the RRC layer of the CIoT device may perform retransmission in the EMM connected state or the RRC connected state without switching to the EMM idle state or the RRC idle state.
  • the EDT indication may be represented by cause information.
  • the CIoT device assumes transmission in the EMM idle state according to the pause indication.
  • the NAS layer of the CIoT device may enter the EMM idle state.
  • CP data (or data transmitted by CP EDT) may be transmitted.
  • the base station may receive an RRC message (eg, an RRC connection request message or a new RRC message) for transmitting CP data (or data transmitted by the CP EDT) from the CIoT device. have. Thereafter, the base station can clear the context of the CIoT device that is being resumed.
  • RRC message eg, an RRC connection request message or a new RRC message
  • the base station extracts CP data (or data transmitted by CP EDT) included in the NAS message in the RRC message in the RRC idle state or the EMM-idle state.
  • the base station encapsulates the extracted CP data (or data transmitted by CP EDT) in a UL NAS transport message and then transmits the encapsulated CP data to an MME.
  • CP data (or data transmitted by CP EDT) described above in step 4) may be applied regardless of whether UP optimization is used. In other words, the above description may also apply to a case in which the CIoT device transmits CP data (or data transmitted by CP EDT) in the uplink in the EMM idle state.
  • the CIoT device in the EMM idle state according to the pause indication is applied by the EDT only when the initial NAS message is not transmitted to the network node (that is, the MME). Data).
  • EDT should not be performed when the initial NAS message should be delivered to the network node.
  • the initial NAS message is not sent to the network node.
  • the CIoT device switches to EMM connected mode when receiving an indication from the lower layer that the RRC connection has been resumed when in the EMM idle state according to the pause indication.
  • the NAS message is as follows.
  • the CIoT device does not include the ESM container, NAS message container, or EPS bearer context status IE.
  • the extended service request message and the service type IE indicates "packet services via S1", and the CIoT device does not include EPS bearer context state IE,
  • the message is not sent. Otherwise, the CIoT device encrypts the message and transmits the initial NAS message when it switches to the EMM connected mode.
  • the value of the uplink NAS COUNT corresponding to the message may be reused for the uplink NAS message to be transmitted next.
  • the CIoT device includes the ESP bearer ID in the MSG3, so that the bearer ID is delivered to the MME.
  • the bearer ID to be resumed may be included.
  • the base station can transmit the bearer for inclusion in an S1-AP message even if the EPS bearer ID is not received from the CIoT device.
  • the third disclosure proposes a method of allowing a CIoT device to know whether a UL data transmission is successful.
  • Option 1) described later relates to a method of additionally using a timer in the resume procedure, and option 2) relates to a method of improving the resume procedure.
  • the AS layer of the CIoT device transmits MSG3 (ie, RRC connection resumption request message) to the base station. If the base station accepts the resumption, the MSG4 (ie, RRC connection resumption message) is transmitted to the AS layer of the CIoT device.
  • the message may include an in-activity timer.
  • the AS layer of the CIoT device receiving the MSG4 starts a timer Txx. At this time, when the in-activity timer is included in the MSG4, the timer Txx is set by the in-activity timer. If there is no in-activity timer in MSG4, the CIoT device sets the timer Txx according to the set value.
  • the CIoT device While the timer Txx is running, when receiving signaling (eg, an RRC connection release message) or data from a base station, the CIoT device stops the timer Txx. When the timer Txx expires, the CIoT device releases the RRC connection internally and transitions to the EMM idle state. In this case, CIoT devices that were using eDRX continue to use eDRX.
  • signaling eg, an RRC connection release message
  • the CIoT device stops the timer Txx.
  • the CIoT device releases the RRC connection internally and transitions to the EMM idle state. In this case, CIoT devices that were using eDRX continue to use eDRX.
  • 14A and 14B are exemplary flowcharts illustrating a procedure of transmitting data according to an EDT.
  • the UP data is applied by applying the EDT only when the CIoT device is in the EMM idle state according to the suspend indication and when the initial NAS message is not sent to the network node (ie, MME). (Or data transmitted by the UP EDT) may be transmitted. In other words, EDT should not be performed when an initial NAS message has to be delivered to a network node. If the CIoT device is in the EMM idle state according to the suspend indication, and if the CP data (or data transmitted by the CP EDT) is transmitted by applying the EDT, the NAS layer of the CIoT device may enter the EMM idle state. Thereafter, CP data (or data transmitted by CP EDT) is transmitted. That is, the contents described below in the third disclosure assume a situation in which the CIoT device transmits UP data (or data transmitted by the UP EDT) when the CIoT device is in the EMM idle state according to the pause indication.
  • the AS layer of the CIoT device receives an indication from a higher layer.
  • the contents of Processes 1 and 2 of the first disclosure shall apply mutatis mutandis.
  • the AS layer of the CIoT device receives the indication, the AS layer performs a resume procedure.
  • the NAS layer may operate in one of two ways.
  • the NAS layer of the CIoT device does not buffer (or pending) the initial NAS message, but instead passes it directly to the AS layer.
  • an RRC establishment cause an indication that the call type and the EDT are possible may be delivered together. That is, it transmits to the AS layer of the CIoT device (that is, the RRC layer of the CIoT device).
  • the AS layer of the CIoT device (that is, the RRC layer of the CIoT device) transmits radio resources for the EDT to the MSG3 by transmitting the size of the UL data to be transmitted through the MSG3 (ie, data volume information) or the EDT indication in the MSG1. Request allocation.
  • the scheduling information for the UL data transmission according to the EDT may be confirmed through the MSG2. That is, it may be checked whether radio resources for UL data transmission according to the EDT have been allocated.
  • UL data initial NAS message including UL data in case of CP data (or data transmitted by CP EDT) is included in the MSG3 and transmitted.
  • the AS layer of the CIoT device may perform a general resumption procedure. That is, the AS layer performs a general resume procedure by sending a resume request message to the base station.
  • the NAS layer of the CIoT device buffers (or pending) the initial NAS message, an initial NAS containing the cause of the RRC establishment, an indication that the call type and EDT are possible, and the UL data that is buffered (or pending).
  • the size information (ie, data volume information) of the message is transmitted to the AS layer (ie, RRC layer of the CIoT device) of the CIoT device, and the following procedure is performed.
  • the AS layer of the CIoT device (that is, the RRC layer of the CIoT device) transmits radio resources for the MSG3 according to the EDT by transmitting the size of UL data (ie, data volume information) or EDT indication to the MSG1 to the MSG3.
  • the AS layer (ie, RRC layer) of the CIoT device may receive MSG2 and check scheduling information for UL data transmission according to the EDT through the MSG2. That is, whether radio resources for UL data transmission according to the EDT are allocated. You can check whether or not.
  • the AS layer of the CIoT device transmits an indication that the EDT is possible or resumed successfully to a higher layer (ie, a NAS layer).
  • the upper layer ie, NAS layer
  • the upper layer that receives this performs a conventional operation when it receives an indication that resumption is successful.
  • the AS layer of the CIoT device transmits UL data (initial NAS message including UL data in case of CP data (or data transmitted by CP EDT)) in MSG3.
  • UL data initial NAS message including UL data in case of CP data (or data transmitted by CP EDT)
  • the AS layer ie, the RRC layer
  • the AS layer may perform a general resumption procedure. That is, the AS layer performs a general resume procedure by sending a resume request message to the base station.
  • the AS layer of the CIoT device transmits MSG1 to the base station, and the base station transmits MSG2 to the AS layer of the CIoT device.
  • the AS layer of the CIoT device transmits the MSG3 (eg, RRC connection resumption request message) to the base station and waits for a response from the base station.
  • MSG3 eg, RRC connection resumption request message
  • the MME When the base station receives the MSG3 (ie, RRC connection resume request message) from the AS layer of the CIoT device, the MME does not send the MSG4 (RRC connection resume message or RRC connection setup message or RRC connection rejection message) to the CIoT device, Send an S1-AP message.
  • the details of the first disclosure will apply mutatis mutandis to the type of S1-AP message, the included information (IE), and a related procedure.
  • the S1-AP message transmitted by the base station to the MME may include a UE context resumption request message.
  • the S1-AP message transmitted by the base station to the MME may be a message as described in the first disclosure.
  • the MME Upon receipt of this, the MME decides to transmit and / or resume the data. In accordance with the determination, the MME sends an S1-AP to a base station.
  • the details of the first disclosure will apply mutatis mutandis to the type of S1-AP message, the included information (IE), and a related procedure.
  • the S1-AP message transmitted by the MME to the base station may be a UE context resume response or a UE context resume failure message.
  • the contents described in the first disclosure shall apply mutatis mutandis.
  • the S1-AP message transmitted by the MME to the base station may be a message as described in the first disclosure.
  • the base station receiving this may transmit an RRC message to the CIoT device.
  • details of the type of the RRC message, the included information (IE), and the related procedure shall apply mutatis mutandis to the contents of the first disclosure.
  • the CIoT device can recognize the success or failure of the UL data transmission transmitted from the received RRC message.
  • the AS layer of the CIoT device sends the indication 'UL data transmission succeeded' to the NAS layer.
  • the AS layer transmits a result of resume (success, failure, fallback) and an indication of whether to suspend the NAS layer.
  • the AS layer of the CIoT device may switch to the RRC idle state after receiving the RRC connection release message. If the RRC connection release message is not received, the AS layer internally releases the RRC connection to switch to the RRC idle state. If it was originally RRC idle, it stays there. In the case of the conventional eDRX, the state transitions to the eDRX state.
  • the NAS layer of the CIoT device When the NAS layer of the CIoT device recognizes that the 'UL data transmission is successful', it discards (or pending) the NAS message and transitions to the EMM idle state. When the pause indication is received, the EMM enters an idle state according to the indication.
  • the CIoT device may attempt to retransmit.
  • the AS layer of the CIoT device transmits an indication of the transmission failure to the NAS layer of the CIoT device.
  • the NAS layer of the CIoT device receives this, it operates as follows. In case of CP data (or data transmitted by CP EDT), retransmission is attempted through MSG5, and in case of UP data (or data transmitted by UP EDT), DRB (Data Radio Bearer) is established according to the service request procedure. Try to resend afterwards.
  • the transmission timing of MSG4 was not described in the first disclosure.
  • the first disclosure may be applied in conjunction with the conventional resume procedure or may be applied with the second disclosure.
  • the fourth disclosure proposes a method for using eDRX or PSM to solve the third problem.
  • a TAU request message when outgoing (MO) data is generated in a CIoT device in PSM mode, a TAU request message should be transmitted first.
  • the two technologies have difficulty coexisting because there is no meaning of performing the EDT operation.
  • CIoT devices that perform EDT in PSM mode should continue to use the PSM without performing the TAU procedure.
  • PSM-related operating parameters are reused as they are recently used.
  • MSG4 RRC message
  • the network node eg, MME
  • MME Mobility Management Entity
  • the MME Since the RRC message transmission of the base station is triggered by the MME, the MME can recognize it. If the timer expires, the base station can notify the MME.
  • the CIoT device using the PSM transmits the MSG3, the CIoT device transmits an indication requesting to continue using the PSM.
  • the base station receiving this is transmitted to the MME including the S1-AP message.
  • the MME receives the S1-AP message from the base station, and if the CIoT device continues to use the PSM, the MME includes an indication to continue using the PSM in the response message S1-AP, and the base station transmits the indication.
  • the application with the RRC message to the CIoT device. If the MME refuses to continue using the PSM, the indication is sent to the CIoT device.
  • the MME can start the procedure.
  • the MME recognizes that the CIoT device was in use of the PSM mode, and if the CIoT device recognizes that the PSM mode is being used, it performs the above operation.
  • the foregoing may also be applied to 5G systems.
  • the following shows a relationship in which the technical term used in the conventional EPC (LTE) is mapped with the technical term used in the 5G system.
  • the foregoing may be applied to 5G systems according to the mapping shown in the table below.
  • the MME-EMM is mapped to AMF
  • the MME-ESM is SMF
  • the interface between MME-EMM and MME-AMF is N11
  • the interface between MME-EMM and base station is mapped to N2.
  • RRC Connection Mode CM connection mode (RRC connection mode / RRC active mode eNodeB (eNB) gNB MME AMF (or SMF) MME-EMM (Layer) AMF (Layer) MME-ESM (layered), S-GW control plane function, P-GW control plane function SMF (Layer) User Plane Function of S-GW User Plane Function of P-GW UPF (Layer) S1-AP (Interface / Message) N2 (interface / message) NAS (Signaling Connection / Interface) N1 (connection / interface)
  • the fifth initiation proposes a scheme for resuming only bearers corresponding to UP data (or data transmitted by the UP EDT) among the contents of the second initiation. That is, in general, the base station resumes all bearers, but the fifth disclosure proposes to only resume bearers corresponding to the specific UP data (or data transmitted by the UP EDT) included in MSG3.
  • the network attempts to resume all bearers of the UE.
  • the base station receives the RRC connection resume request message, the base station transmits an S1-AP based UE context resume request message including a list of all bearers successfully resumed.
  • the MME resumes all bearers in the message and transmits a Modify Bearer Request message.
  • the S-GW resumes all bearers contained in the Modify Bearer Request message. Then, an S1-U bearer is established corresponding to the bearer successfully resumed.
  • the base station may find an ID of a bearer corresponding to the UP EDT data.
  • the base station does not have to send a request message to the MME for resuming other bearers other than the bearer associated with the UP EDT data.
  • the UE context resumption request message transmitted by the base station in step 4 of FIG. 15 is used not only to inform the MME that the CIoT device has resumed the RRC connection, but also informs the MME of the UE context, UE-related logical S1 connection, and associated bearer. Can be used to request to resume the context.
  • the base station may include the 'E-RAB Failed to Resume' list in the UE context resumption request message.
  • the 'E-RAB Failed to Resume' list may include information on the E-RAB that does not need to be resumed.
  • Option 1 If the base station requests resumption of all bearers as before,
  • the base station sends an S1-AP based UE context resume request message including a list of all bearers. If the MME fails to resume a bearer with a bearer ID of 1 but succeeds in resuming another bearer, the MME transmits information on the resumed bearer to the base station through an S1-AP based UE context response message and modifies the bearer. Send the request message. Then, since the BS fails to resume the bearer having a bearer ID of 1, the BS transmits an RRC connection rejection message to the CIoT device and transmits an S1 UE context release request message to the MME. The MME performs an S1 release procedure.
  • option 1 requires additional signaling.
  • the base station when the base station receives the MSG3 including the UP EDT data, it is effective that the base station only requests the MME to resume the bearer corresponding to the UP EDT data.
  • the CIoT device when the CIoT device is in the paused state, when the CIoT device transmits the outgoing (MO) CP EDT data through the MSG3, the CIoT device may not perform the resume procedure.
  • a message that the NAS layer does not forward to the lower layer may be an initial NAS message as described above.
  • Case 2 When a NAS message transmitting CP data (or data transmitted by CP EDT) is triggered, the control plane service request (CPRS) message, the ESM message container in the CPRS message may include an ESM data transmission message. have.
  • CPRS control plane service request
  • the CIoT device determines that EDT can be performed when the following conditions are satisfied.
  • the maximum grant size for the EDT provided in the SIB is greater than the EDT data and / or
  • the EDT request is made through the MSG1 of the random access procedure, and upon receiving the MSG2 (that is, the random access response), it is determined whether the EDT can be performed. In detail, when sufficient grant (ie, resource allocation) is obtained through MSG2 to transmit EDT data through MSG3, it may be determined that EDT data transmission is possible.
  • sufficient grant ie, resource allocation
  • the conventional resume procedure can be performed. That is, the CIoT device may transmit MSG3 (ie, RRC connection resumption request message) and receive MSG4 as conventionally.
  • MSG3 ie, RRC connection resumption request message
  • Case 2 In the above-described assumption, if it is determined that the EDT can be performed, the CP EDT data transmission procedure may be performed without performing the resume procedure. However, if it is determined that the EDT cannot be performed, the CIoT device may perform a conventional resume procedure. That is, the CIoT device may transmit MSG3 (ie, RRC connection resumption request message) and receive MSG4 as conventionally.
  • MSG3 ie, RRC connection resumption request message
  • CP data (or data transmitted by CP EDT) can be transmitted over MSG5 (ie, RRC connection setup complete message).
  • the NAS layer buffers (or pending) the initial NAS message and requests resumption from the AS layer (i.e., the RRC layer), and in hypothesis 2, the NAS layer buffers (or The data volume information in the pending NAS message must be provided to the AS layer (ie, RRC layer).
  • the data volume information is used as information for determining whether to perform EDT.
  • the NAS layer of the CIoT device may finally determine whether to resume.
  • the NAS layer of the CIoT device may operate according to the information on whether the AS layer of the CIoT device may perform EDT. Specifically, it is as follows.
  • Process 1 The following conventional operation is performed on the NAS layer of the CIoT device.
  • the NAS layer of the CIoT device requests the AS layer to resume the RRC connection.
  • the NAS layer may provide an RRC establishment cause and call type to the AS layer.
  • RRC Release Indication Release Assistance Indication
  • EDT EDT indication is provided to the AS layer (ie, RRC layer) along with the RRC establishment cause and call type.
  • Step 2 The AS layer of the CIoT device may determine whether to perform EDT. See the high level concept above.
  • Step 2-1 When it is determined that EDT can be performed, the AS layer transmits an indication that EDT can be performed to the NAS layer of the CIoT device, and proceeds to step 3-1 below.
  • Step 2-2 If it is determined that the EDT cannot be performed, the resume procedure is conventionally performed.
  • a message that the NAS layer of the CIoT device is buffering (or pending) contains a NAS message containing CP data (or data transmitted by CP EDT) (i.e. an ESM data transport mesh in the ESM message container).
  • CPSR message and together with the NAS message, further transmits the following information to the AS layer of the CIoT device and switches to the EMM-IDLE. And proceed to step 4.
  • the NAS layer delivers an indication to the AS layer indicating that the NAS message is a NAS message for transmitting CP data (or data transmitted by CP EDT).
  • the indication may be CP EDT or CP data (or data transmitted by CP EDT) transmission.
  • the NAS layer may send an indication to the AS layer not to perform a resume or to switch to an idle state.
  • Case B If a message that the NAS layer of the CIoT device is buffering (or pending) contains a NAS message containing CP data (or data transmitted by the CP EDT) (i.e. an ESM data transport mesh in the ESM message container). CPSR message), an acknowledgment (ACK) / response indication is transmitted to the AS layer of the CIoT device.
  • CP data or data transmitted by the CP EDT
  • ACK acknowledgment
  • response indication is transmitted to the AS layer of the CIoT device.
  • Case 4 In case A) of process 3, the AS layer of the CIoT device sends the MSG3 of the random access procedure and resumes the procedure to send a NAS message that transmits CP data (or data transmitted by the CP EDT). Do not perform. However, in case B) of process 3, the AS layer of the CIoT device performs the resume procedure.
  • the NAS layer of the CIoT device may inform the AS layer only when transmission of a NAS message including CP data (or data transmitted by the CP EDT) is triggered.
  • the AS layer of the CIoT device may additionally distinguish from the NAS layer of the CIoT device according to the EDT availability information.
  • Process 1 The following conventional operation is performed on the NAS layer of the CIoT device.
  • the NAS layer of the CIoT device requests the AS layer to resume the RRC connection.
  • the NAS layer may provide an RRC establishment cause and call type to the AS layer.
  • RRC Release Assistance Indication
  • EDT EDT
  • RAI Release Assistance Indication
  • / or EDT indication is provided to the AS layer (ie, RRC layer) together with the RRC establishment cause and call type.
  • the message being buffered (or pending) by the NAS layer of the CIoT device is a NAS message containing CP data (or data sent by CP EDT) (ie, a CPSR message containing an ESM data transport mesh in the ESM message container).
  • the NAS layer delivers an indication to the AS layer indicating that the NAS message is a NAS message for transmitting CP data (or data transmitted by CP EDT).
  • the indication may be CP EDT or CP data (or data transmitted by CP EDT) transmission.
  • Step 2 The AS layer of the CIoT device may determine whether to perform EDT. See the high level concept above.
  • Step 2-1 When it is determined that EDT can be performed, the AS layer transmits an indication that EDT can be performed to the NAS layer of the CIoT device, and proceeds to step 3-1 below.
  • Step 2-2 If it is determined that the EDT cannot be performed, the resume procedure is conventionally performed.
  • Step 3 For Step 2-1, the CIoT device NAS layer sends the following information to the AS layer of the CIoT device along with a NAS message containing the CP data (or data transmitted by the CP EDT) that is buffering (or pending): Send additionally and switch to EMM-IDLE.
  • the NAS layer may transmit an indication not to perform resumption or an indication to switch to an idle state to the AS layer.
  • Step 4 The AS layer of the CIoT device transmits the MSG3 of the random access procedure and does not perform the resume procedure to transmit a NAS message that transmits CP data (or data transmitted by the CP EDT).
  • the NAS layer of the CIoT device does not request for resumption, and after receiving EDT success from the AS layer of the CIoT device, it is possible to determine whether to request a resumption according to the type of the NAS message being buffered (or pending). Specifically, it is as follows.
  • Step 1 The NAS layer of the CIoT device does not perform an operation for requesting resumption in the following conventional operation.
  • the NAS layer of the CIoT device may provide an RRC establishment cause and call type to the AS layer.
  • RAI Release Assistance Indication
  • / or EDT indication is provided to the AS layer (ie, RRC layer) together with the RRC establishment cause and call type.
  • Step 2 The AS layer of the CIoT device may determine whether to perform EDT. See the high level concept above.
  • Step 2-1 If it is determined that EDT can be performed, the AS layer transmits an indication that EDT can be performed to the NAS layer of the CIoT device.
  • Step 2-2 If it is determined that the EDT cannot be performed, an indication that the EDT cannot be performed is transmitted to the NAS layer of the CIoT device.
  • the AS layer of the CIoT device does not send an MSG3 (for CP EDT) and perform a resume procedure to transmit a NAS message that transmits CP data (or data transmitted by CP EDT). Do not.
  • the AS layer of the CIoT device performs the final decision on whether to resume.
  • the initial NAS message does not buffer the initial NAS message as if it has been in the EMM idle state. Can be delivered directly to the AS layer of the CIoT device along with the RRC establishment cause and call type.
  • the NAS layer transmits a request for resuming the RRC connection to the AS layer of the CIoT device.
  • the NAS layer provides RAI and / or EDT indication to the AS layer (ie, RRC layer) together with the RRC establishment cause and the call type.
  • the NAS layer informs the AS layer of the CIoT device whether the NAS message is a NAS message (ie, a CPSR message) that transmits CP data (or data transmitted by CP EDT).
  • a NAS message ie, a CPSR message
  • CP data or data transmitted by CP EDT
  • the indication may be CP EDT or CP data (or data transmitted by CP EDT) transmission.
  • Step 2 The AS layer of the CIoT device may determine whether to perform EDT. See the high level concept above.
  • Step 2-1 If it is determined that EDT can be performed,
  • process 1) is a NAS message containing CP data (or data transmitted by CP EDT),
  • the AS layer of the CIoT device transmits MSG3 (for CP EDT) of a random access procedure to transmit a NAS message including CP data (or data transmitted by CP EDT). At this time, the AS layer does not perform the resumption procedure and informs the NAS layer of the CIoT device. The NAS layer of the CIoT device then transitions to the EMM idle state.
  • Step 2-2 If it is determined that the EDT cannot be performed, the resume procedure is conventionally performed.
  • option 1-B Comparing between options: For option 1-B, perform different actions only when a NAS message occurs that transmits CP data (or data transmitted by the CP EDT), thus giving a different NAS message than other options. It can be implemented without further improvement in the case in which it occurs.
  • 16 is a block diagram illustrating a configuration of a CIoT device 100 and a network device according to an embodiment of the present invention.
  • the CIoT device 100 includes a processor 101, a memory 102, and a transceiver 103.
  • the network device may be a base station 200 or an MME / SGSN 510.
  • the network device 200 or 510 includes a processor 201 or 511, a memory 202 or 512, and a transceiver 203 or 513.
  • the memories 102, 202 or 512 store the method described above.
  • the processors 101, 201, or 511 control the memories 102, 202, or 512 and the transceivers 103, 203, or 513, respectively. Specifically, the processors 101, 201, or 511 execute the methods stored in the memories 102, 202, or 512, respectively. The processors 101, 201, or 511 transmit the aforementioned signals through the transceivers 103, 203, or 513.

Landscapes

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

Abstract

Selon un mode de réalisation, la présente invention concerne un procédé permettant à une station de base de prendre en charge une transmission précoce de données (EDT). Le procédé peut comprendre une étape consistant à recevoir un premier message provenant d'une entité de gestion de mobilité (MME). Un premier message NAS peut comprendre des données de liaison descendante. Le procédé peut en outre comprendre une étape consistant à confirmer qu'il n'existe pas de données supplémentaires autres que les données de liaison descendante, sur la base de la réception du premier message NAS.
PCT/KR2018/004897 2017-04-28 2018-04-27 Procédé de transmission de données basé sur une transmission edt WO2018199673A1 (fr)

Priority Applications (7)

Application Number Priority Date Filing Date Title
KR1020187037554A KR102053229B1 (ko) 2017-04-28 2018-04-27 Edt에 따라 데이터를 전송하는 방안
JP2019510630A JP6935489B2 (ja) 2017-04-28 2018-04-27 Ｅｄｔによってデータを送信する方法
EP18792170.5A EP3471457B1 (fr) 2017-04-28 2018-04-27 Procédé de transmission de données basé sur une transmission edt
CN201880003851.8A CN109863783B (zh) 2017-04-28 2018-04-27 根据edt发送数据的方法
US16/242,458 US10932121B2 (en) 2017-04-28 2019-01-08 Method for transmitting data according to EDT
US17/181,933 US11812502B2 (en) 2017-04-28 2021-02-22 Method for transmitting data according to EDT
US18/375,864 US20240031793A1 (en) 2017-04-28 2023-10-02 Method for transmitting data according to edt

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
US201762491333P 2017-04-28 2017-04-28
US62/491,333 2017-04-28
US201762581045P 2017-11-03 2017-11-03
US62/581,045 2017-11-03
KR10-2018-0040020 2018-04-05
KR20180040020 2018-04-05

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/242,458 Continuation US10932121B2 (en) 2017-04-28 2019-01-08 Method for transmitting data according to EDT

Publications (1)

Publication Number Publication Date
WO2018199673A1 true WO2018199673A1 (fr) 2018-11-01

Family

ID=63919966

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2018/004897 WO2018199673A1 (fr) 2017-04-28 2018-04-27 Procédé de transmission de données basé sur une transmission edt

Country Status (2)

Country Link
KR (1) KR102053229B1 (fr)
WO (1) WO2018199673A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113261377A (zh) * 2019-01-10 2021-08-13 索尼集团公司 通信设备，通信方法和通信程序
CN114788368A (zh) * 2019-12-10 2022-07-22 联想(北京)有限公司 用于数据传输的方法及设备
US11540252B2 (en) * 2019-06-18 2022-12-27 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Data transmission method, network device

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20220123694A (ko) * 2020-01-22 2022-09-08 엘지전자 주식회사 무선 통신 시스템에서 소형 데이터의 고속 전송을 위한 방법 및 장치
US20230067158A1 (en) * 2020-02-07 2023-03-02 Lg Electronics Inc. Method and apparatus for small data transmission in rrc inactive state in mr-dc

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017014533A1 (fr) * 2015-07-22 2017-01-26 엘지전자 주식회사 Procédé et appareil permettant à un c-sgn de recevoir des informations concernant une transmission de petites données
US20170086062A1 (en) * 2015-09-21 2017-03-23 Acer Incorporated Apparatuses and methods for handling mobile originated (mo) cellular internet of things (ciot) data

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20110049622A (ko) * 2009-11-04 2011-05-12 삼성전자주식회사 무선 통신 네트워크 시스템에서 데이터 전송 방법 및 장치

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017014533A1 (fr) * 2015-07-22 2017-01-26 엘지전자 주식회사 Procédé et appareil permettant à un c-sgn de recevoir des informations concernant une transmission de petites données
US20170086062A1 (en) * 2015-09-21 2017-03-23 Acer Incorporated Apparatuses and methods for handling mobile originated (mo) cellular internet of things (ciot) data

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Early Data Transmission for NB-ioT", R1-1705189, 3GPP TSG RAN WG1 MEETING #88BIS, 25 March 2017 (2017-03-25), Spokane, USA, XP051251789 *
HUAWEI: "Consideration on Early Data Transmission", R3-170966, 3GPP TSG RAN WG3 MEETING #95BIS, 25 March 2017 (2017-03-25), Spokane, USA, XP051255099 *
ZTE ET AL.: "On Early Data Transmission for NB-IoT", R1-1705489, 3GPP TSG RAN WG1 MEETING #88BIS, 24 March 2017 (2017-03-24), Spokane, USA, XP051250945 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113261377A (zh) * 2019-01-10 2021-08-13 索尼集团公司 通信设备，通信方法和通信程序
EP3911100A4 (fr) * 2019-01-10 2022-01-19 Sony Group Corporation Dispositif de communication, procédé de communication et programme de communication
TWI811508B (zh) * 2019-01-10 2023-08-11 日商索尼股份有限公司 通訊裝置、通訊方法、及通訊程式
US11979922B2 (en) 2019-01-10 2024-05-07 Sony Group Corporation Communication device, communication method, and communication program
US11540252B2 (en) * 2019-06-18 2022-12-27 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Data transmission method, network device
CN114788368A (zh) * 2019-12-10 2022-07-22 联想(北京)有限公司 用于数据传输的方法及设备

Also Published As

Publication number Publication date
KR102053229B1 (ko) 2019-12-06
KR20190006021A (ko) 2019-01-16

Similar Documents

Publication Publication Date Title
WO2018231028A1 (fr) Procédé d'enregistrement d'un terminal dans un système de communication sans fil, et appareil associé
WO2018128456A1 (fr) Procédé et terminal pour effectuer une commande d'accès dans un système de communication mobile de 5ème génération
WO2018093168A1 (fr) Procédé de sélection de nœud de réseau dans un système de communication sans fil et dispositif correspondant
WO2018231029A1 (fr) Procédé d'enregistrement d'un terminal dans un système de communications sans fil, et appareil associé
WO2018174524A1 (fr) Procédé d'interaction entre des couches dans un système de communication sans fil et appareil associé
WO2018070689A1 (fr) Procédé d'application d'une qualité de service réfléchissante dans un système de communication sans fil, et dispositif correspondant
WO2018169244A1 (fr) Procédé de notification d'événement de mobilité dans un système de communication sans fil et dispositif correspondant
WO2018147698A1 (fr) Procédé de transmission/réception d'un message nas dans un système de communication sans fil, et appareil associé
WO2018008980A1 (fr) Procédé permettant de sélectionner une opération de ressource préférée par l'utilisateur dans un système de communication sans fil et dispositif associé
WO2018131984A1 (fr) Procédé de mise à jour de configuration d'ue dans un système de communication sans fil, et appareil associé
WO2018110939A1 (fr) Procédé d'attribution de zone de suivi dans un système de communication sans fil et appareil correspondant
WO2018097599A1 (fr) Procédé de désenregistrement dans un système de communication sans fil, et dispositif correspondant
WO2018080230A1 (fr) Procédé de détermination de mode d'emm dans un système de communication sans fil, et appareil pour cela
WO2018088756A1 (fr) Procédé de transmission de message de rrc et dispositif sans fil
WO2018236164A1 (fr) Procédé et dispositif d'exécution d'une procédure de demande de service dans un système de communication sans fil
WO2017188758A1 (fr) Procédé et appareil d'interruption/reprise de signalisation nas dans un système de communication sans fil
WO2016111591A1 (fr) Procédé de transmission de radiomessagerie dans un système de communication sans fil et dispositif associé
WO2019031865A1 (fr) Procédé permettant de réaliser une procédure de connexion rrc dans un système de communication sans fil et appareil s'y rapportant
WO2018079947A1 (fr) Procédé de prise en charge de mobilité d'équipement utilisateur dans un système de communication sans fil et dispositif associé
WO2016024789A1 (fr) Procédé de suivi d'accessibilité d'ue dans un système de communication sans fil, et dispositif associé
WO2016208997A1 (fr) Procédé pour gérer une zone d'un terminal dans un système de communication sans fil et appareil associé
WO2016003140A1 (fr) Procédé d'interdiction d'accès réseau pour chaque application et équipement utilisateur
WO2017142171A1 (fr) Procédé et terminal de création, modification, et libération de session dans un réseau de communications mobiles de prochaine génération
WO2015142048A1 (fr) Procédé d'exécution et équipement utilisateur pour procédure de demande de service
WO2016114611A1 (fr) Procédé de mise à jour d'une zone dans un système de communication sans fil et dispositif associé

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20187037554

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018792170

Country of ref document: EP

Effective date: 20190108

ENP Entry into the national phase

Ref document number: 2019510630

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE