专利摘要:
a method is provided for a user device (eu) to carry out the anticipated data transmission (edt) in a wireless communication, and a device supporting it. the method may include: receiving information from the system, including a limit for edt; determining whether a condition to initiate edt is met by comparing the limit for edt with a data size for transmission; if the condition is satisfied, execute edt; and if the condition is not met, perform a procedure for establishing or resuming the radio resource control (rrc) connection.
公开号:BR112019014859A2
申请号:R112019014859
申请日:2018-07-26
公开日:2020-04-14
发明作者:Kim Hongsuk;Choe Hyunjung;Lee Youngdae
申请人:Lg Electronics Inc;
IPC主号:
专利说明:

“METHOD AND APPARATUS TO PERFORM EDT”
Technical Field [001] The present invention relates to a wireless communication system and, more particularly, to a process for a user equipment (UE), to carry out the anticipated data transmission (EDT) and an apparatus to support the same.
Background Technique [002] In order to meet the demand for wireless data traffic, which has increased since the commercialization of a fourth generation (4G) communication system, efforts are being made to develop an improved fifth generation communication system (5G) or pre-5G system communication system. For this reason, a 5G communication system or pre-5G communication system is referred to as a network communication system beyond-4G or post-long term evolution (LTE) system.
Disclosure of the Invention
Technical problem [003] Meanwhile, for low-cost EU, it is important to save energy from EU. Thus, the number of transmissions should be reduced as much as possible. Early data transmission (EDT) in RRC Connection Establishment or RRC Connection Resume is one of the solutions to reduce the power consumption of the UE. However, the current system does not support early data transmission. Thus, a method for a UE to perform EDT and an apparatus that supports the same need to be proposed.
Solution to the Problem [004] A modality provides a method to perform, through a user equipment (UE), anticipated data transmission (EDT) in a wireless communication. The method may include: receiving system information, including a limit on the
Petition 870190068249, of 07/18/2019, p. 12/77
2/43
EDT; determine whether or not a condition to start EDT is met, compare the limit for EDT with a data size for transmission; if the condition is satisfied, perform the EDT; and if the condition is not satisfied, perform a radio resource control connection establishment or resumption procedure (RRC).
[005] Another modality provides a user equipment (UE) that performs the anticipated data transmission (EDT) in a wireless communication. The UE may include: a memory; a transmitter and receiver; and a processor, connected to memory and the transceiver, which: controls the transceiver to receive system information, including a limit for the EDT; determines whether or not a condition to start EDT is met, compares the limit for EDT with a data size for transmission; if the condition is satisfied, the EDT executes; and if the condition is not satisfied, perform an RRC connection establishment or resumption procedure.
Advantageous Effects of the Invention [006] The power consumption of the UE can be reduced.
Brief Description of the Figures [007] FIG. 1 shows LTE system architecture.
[008] FIG. 2 shows a control plan for an LTE system radio interface protocol.
[009] FIG. 3 shows a user plan for an LTE system radio interface protocol.
[010] FIG. 4 shows 5G system architecture.
[011] FIG. 5 shows functional division between NG-RAN and 5GC.
[012] FIG. 6 shows a contention-based random access procedure.
[013] FIG. 7 shows a random access procedure based on no
Petition 870190068249, of 07/18/2019, p. 13/77
3/43 containment.
[014] FIG. 8 shows an example of MAC PDU including MAC header, MAC control elements, MAC SDUs and padding.
[015] FIG. 9 shows a procedure for determining whether or not to perform EDT according to an embodiment of the present invention.
[016] FIG. 10A and 10B show a process for carrying out EDT according to an embodiment of the present invention.
[017] FIG. 11A and 11B show a process for carrying out EDT according to an embodiment of the present invention.
[018] FIG. 12 is a block diagram illustrating a method for a UE to perform EDT in accordance with an embodiment of the present invention.
[019] FIG. 13 is a block diagram illustrating a wireless communication system in accordance with the embodiment of the present invention.
Mode for the Invention [020] The technology described below can be used in various wireless communication systems, such as Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), etc. CDMA can be implemented with radio technology, such as Universal Terrestrial Radio Access (UTRA) or CDMA-2000. TDMA can be implemented with radio technology as the global system for mobile communications (GSM) ZGeneral Packet Radio Service (GPRS) Enhanced data rate for GSM Evolution (EDGE). OFDMA can be implemented with radio technology such as the Institute of Electrical and Electronic Engineers (IEEE) 802.11 (WiFi), IEEE 802.16 (WiMAX), IEEE 802.20, evolved UTRA (E-UTRA), etc. IEEE 802. 16m is evolved from IEEE 802.16e, and provides compatibility with a system based on
Petition 870190068249, of 07/18/2019, p. 14/77
4/43 in the IEEE 802.16e standard. UTRA is a part of a universal mobile telecommunications system (UMTS). Long Term Evolution (LTE) of 3rd Generation Partnership Project (3GPP) is a part of an evolved UMTS (E-UMTS) that uses E-UTRA. LTE 3GPP uses OFDMA in a downlink and uses SC-FDMA in an uplink. Advanced LTE (LTE-A) is an evolution of LTE. 5G communication system is an evolution of LTE-A.
[021] For clarity, the following description will focus on LTE-A. However, the technical characteristics of the present invention are not limited to these.
[022] FIG. 1 shows LTE system architecture. The communication network is widely deployed to provide a variety of communication services, such as voice over internet protocol (VoIP) through IMS and packet data.
[023] With reference to FIG. 1, the LTE system architecture includes one or more user equipment (UE; 10), an evolved UMTS terrestrial radio access network (E-UTRAN) and an evolved packet core (EPC). The UE 10 refers to a communication equipment made by a user. UE 10 can be fixed or mobile, and can be referred to as another terminology, such as a mobile station (MS), a user terminal (UT), a subscriber station (SS), a wireless device, etc.
[024] The E-UTRAN includes one or more evolved B-nodes (eNB) 20, and a plurality of UEs can be located in a cell. ENB 20 provides an endpoint of a control plan and a user plan for the UE 10. The eNB 20 is generally a fixed station, which communicates with the UE 10 and can be referred to as another terminology, such as a base station (BS), a base transceiver system (BTS), an access point, etc. One eNB 20 can be implemented per cell. There are one or more cells within the eNB 20 coverage.
Petition 870190068249, of 07/18/2019, p. 15/77
5/43
A single cell is configured to have a selected bandwidth starting at 1.25, 2.5, 5, 10, and 20 MHz, etc., and provides downlink or uplink transmission services for several UEs. In this case, different cells can be configured to provide different bandwidth.
[025] Hereinafter, a downlink (DL) indicates communication from eNB 20 to UE 10, and an uplink (UL) indicates communication from UE 10 to eNB 20. In DL, a transmitter can be a part of eNB 20, and a receiver can be a part of UE 10. In UL, the transmitter can be a part of UE 10, and the receiver can be a part of eNB 20.
[026] The EPC includes a mobility management entity (MME), which is responsible for control plan functions, and a System Architecture Evolution (SAE) gateway (S-GW), which is responsible for the functions of the user plan. MME / SGW 30 can be positioned at the end of the network and connected to an external network. The MME has UE access information or UE capacity information, and such information can be used mainly in the management of UE mobility. The S-GW is a gateway of which an endpoint is an E-UTRAN. The MME / SGW 30 provides a session endpoint and mobility management function for the UE 10. The EPC may further include a packet data network (PDN) gateway (PDN-GW). The PDN-GW is a gateway of which an endpoint is a PDN.
[027] MME provides several functions, including non-access layer (NAS) signaling for eNBs 20, NAS signaling security, access layer security (AS) control, inter-core node (CN) signaling for mobility between 3GPP access networks, idle mode. UE scope (including paging relay control and execution), area list management tracking (for UE in idle and active mode), P-GW and S-GW selection, MME selection for MME change handovers , selection of GPRS support node of
Petition 870190068249, of 07/18/2019, p. 16/77
6/43 service (SGSN) for handovers for 3GPP 2G or 3G access networks, roaming, authentication, bearer management functions including dedicated bearer establishment, support for public warning system (PWS) (which includes earthquake warning system and tsunamis (ETWS) and commercial mobile alert system (CMAS) message transmission. The S-GW host provides a variety of functions, including per-user packet-based filtering (eg, deep packet inspection), legal interception, UE Internet Protocol (IP) address assignment, transport-level packet marking on DL, UL and DL service level loading, port and rate application, DL rate application based on APN-AMBR. For clarity MME / S-GW 30 will be referred to here simply as a gateway, but it is understood that this entity includes both MME and S-GW.
[028] Interfaces to transmit user traffic or control traffic can be used. The UE 10 and eNB 20 are connected via a Uu interface. The eNBs 20 are interconnected via an X2 interface. Neighboring eNBs can have a mesh network structure that has the X2 interface. The eNBs 20 are connected to the EPC via an S1 interface. The eNB 20 are connected to MME, through an S1-MME interface, and are connected to S-GW through an S1-U interface. The S1 interface supports a many-to-many relationship between eNB 20 and MME / SGW [029] eNB 20 can perform selection functions for gateway 30, routing to gateway 30 during a radio resource control (RRC) activation ), programming and transmission of paging messages, programming and transmission of broadcast channel information (BCH), dynamic allocation of resources to the UE 10 in both UL and DL, configuration and provisioning of eNB measurements, radio carrier control, control radio admission (CCR), and connection mobility control in LTE_ACTIVE state. At EPC, and how
Petition 870190068249, of 07/18/2019, p. 17/77
7/43 noted above, gateway 30 can perform paging source functions, LTEJDLE state management, user plan encryption, SAE carrier control, and encryption protection and NAS signaling integrity.
[030] FIG. 2 shows a control plan of an LTE system radio interface protocol. FIG. 3 shows a user plan for an LTE system radio interface protocol.
[031] Layers of a radio interface protocol between the UE and EUTRAN can be classified into a first layer (L1), a second layer (L2), and a third layer (L3) based on the bottom three layers of the open system interconnection model (OSI) that is well known in the communication system. The radio interface protocol between the UE and the E-UTRAN can be divided horizontally into a physical layer, a data link layer, and a network layer, and can be divided vertically into a control plane (C-plane ), which is a stack of protocols for transmitting control signals and a user plane (U-plane), which is a stack of protocols for transmitting data information. The layers of the radio interface protocol exist in pairs in the UE and the E-UTRAN, and are responsible for the transmission of data from the Uu interface.
[032] A physical layer (PHY) belongs to L1. The PHY layer provides an upper layer with an information transfer service through a physical channel. The PHY layer is connected to a medium access control layer (MAC), which is a top layer of the PHY layer, through a transport channel. A physical channel is mapped to the transport channel. Data is transferred between the MAC layer and the PHY layer through the transport channel. Between different PHY layers, that is, a PHY layer from a transmitter and a PHY layer from a receiver, data is transferred through the physical channel using radio resources. The physical channel is modulated using a
Petition 870190068249, of 07/18/2019, p. 18/77
8/43 orthogonal frequency division multiplexing (OFDM), and uses time and frequency as a radio resource.
[033] The PHY layer uses several physical control channels. A physical downlink control channel (PDCCH) reports to a UE about the allocation of resources from a paging channel (PCH) and a shared downlink channel (DL-SCH) and hybrid auto-repeat request information (HARQ) related to DL-SCH. The PDCCH may carry a UL grant to report to the UE on the allocation of UL transmission resources. A physical control format indicator channel (PCFICH) indicates the number of OFDM symbols, used for PDCCHs for the UE, and is transmitted in each subframe. A physical hybrid ARQ indicator channel (PHICH) carries a HARQ acknowledgment (ACK) / negative acknowledgment (NACK) signal in response to UL transmission. A physical uplink control channel (PUCCH) carries UL control information such as ACK / NACK from HARQ for DL transmission, programming request, and CQI. A physical uplink shared channel (PUSCH) carries a UL uplink shared channel (SCH).
[034] A physical channel consists of a plurality of subframes in the time domain and a plurality of subcarriers in the frequency domain. A subframe consists of a plurality of symbols in the time domain. A subframe consists of a plurality of resource blocks (RBs). A RB consists of a plurality of symbols and a plurality of subcarriers. In addition, each subframe can use specific subcarriers of symbols specific to a corresponding subframe for a PDCCH. For example, a first symbol in the subframe can be used for the PDCCH. The PDCCH carries dynamic allocated resources, such as a physical resource block (PRB) and a coding and modulation scheme (MCS). A transmission time interval (TTI), which is a unit of time for data transmission, can be equal to
Petition 870190068249, of 07/18/2019, p. 19/77
9/43 is a length of a subframe. The length of a subframe can be 1 ms.
[035] The transport channel is classified into a common transport channel and a dedicated transport channel according to whether the channel is shared or not. A DL transport channel for transmitting data from the network to the UE includes a broadcast channel (BCH) for transmitting system information, a paging channel (PCH) for transmitting a paging message, a DL-SCH for transmitting user traffic or control signals, etc. The DL-SCH supports HARQ, dynamic link adaptation varying the modulation, encoding and transmission power and allocation of dynamic and semi-static resources. DL-SCH can also allow for cell-wide broadcasting and the use of beam formation. The system information carries one or more blocks of system information. All blocks of system information can be transmitted with the same periodicity. Traffic or control signals from a multimedia broadcast / multicast service (MBMS) can be transmitted via the DL-SCH or a multicast channel (MCH).
[036] An UL transport channel for transmitting data from the UE to the network includes a random access channel (RACH) for transmitting an initial control message, an UL-SCH for transmitting user traffic or signals control, etc. UL-SCH supports HARQ and dynamic link adaptation by varying transmission power and, potentially, modulation and encoding. UL-SCH can also allow the use of beam formation. RACH is normally used for initial access to a cell.
[037] A MAC layer belongs to L2. The MAC layer provides services for a Radiolink control layer (RLC), which is an upper layer of the MAC layer, through a logical channel. The MAC layer provides a function for mapping multiple logical channels to multiple transport channels. Bedridden
Petition 870190068249, of 07/18/2019, p. 20/77
10/43
MAC also provides a logical channel multiplexing function by mapping multiple logical channels to a single transport channel. The MAC sublayer offers data transfer services on logical channels.
[038] The logical channels are classified into control channels for the transfer of control plan information and traffic channels for the transfer of user plan information, according to a type of information transmitted. That is, a set of logical channel types is defined for different data transmission services offered by the MAC layer. The logical channels are located above the transport channel, and are mapped to the transport channels.
[039] Control channels are used to transfer only control plan information. The control channels provided by the MAC layer include a broadcast control channel (BCCH), a paging control channel (PCCH), a common control channel (CCCH), a multicast control channel (MCCH) and a channel dedicated control (DCCH). BCCH is a downlink channel for broadcasting system control information. The PCCH is a downlink channel that transfers paging information and is used when the network does not know a UE's local cell. CCCH is used by UEs having no RRC connection to the network. MCCH is a point-to-multipoint downlink channel used to transmit MBMS control information from the network to an UE. DCCH is a point-to-point bidirectional channel used by UEs that have an RRC connection that transmits dedicated control information between a UE and the network.
[040] Traffic channels are used for the transfer of user plan information only. The traffic channels provided by the MAC layer include a dedicated traffic channel (DTCH) and a multicast traffic channel (MTCH). DTCH is a point-to-point channel, dedicated to a UE for transferring
Petition 870190068249, of 07/18/2019, p. 21/77
11/43 user information and can exist on both uplink and downlink. MTCH is a point-to-multipoint downlink channel for transmitting network traffic data to the EU.
[041] Uplink connections between logical channels and transport channels include DCCH that can be mapped to UL-SCH, DTCH that can be mapped to UL-SCH and CCCH that can be mapped to UL-SCH. Downlink connections between logical channels and transport channels include BCCH which can be mapped to BCH or DL-SCH, PCCH which can be mapped to PCH, DCCH which can be mapped to DL-SCH, and DTCH that can be mapped to the DL-SCH, the MCCH that can be mapped to the MCH, and the MTCH that can be mapped to the MCH.
[042] An RLC layer belongs to L2. The RLC layer provides the function of adjusting the size of the data, so as to be suitable for a lower layer to transmit the data, by concatenating and segmenting the data received from an upper layer of a radio section. In addition, to ensure a variety of Quality of Service (QoS) required by a radio carrier (RB), the RLC layer provides three modes of operation, namely, a transparent mode (TM), a non-confirmation mode (UM), and a confirmation mode (AM). The RLC AM offers a retransmission function through an automatic repeat request (ARQ) for reliable data transmission. Meanwhile, a function of the RLC layer can be implemented with a function block within the MAC layer. In this case, the RLC layer may not exist.
[043] A layer of packet data convergence protocol (PDCP) belongs to L2. The PDCP layer provides a function of the header compression function that reduces unnecessary control information in such a way that the data to be transmitted using IP packets, such as IPv4 or IPv6, can be efficiently transmitted over an
Petition 870190068249, of 07/18/2019, p. 22/77
12/43 radio interface that has a relatively small bandwidth. The compression header increases the transmission efficiency in the radio section by transmitting only necessary information in a data header. In addition, the PDCP layer provides a security function. The security function includes encryption that prevents third party inspection, and integrity protection that prevents manipulation of third party data.
[044] A radio resource control layer (RRC) belongs to L3. The RLC layer is located in the lowest portion of L3, and is only defined in the control plane. The RRC layer assumes a role in controlling a radio resource between the UE and the network. To do this, the UE and the network exchange an RRC message through the RRC layer. The RRC layer controls the logical channels, transport channels and the physical channels, in relation to the configuration, reconfiguration, and release of RBs. An RB is a logical path provided by L1 and L2 for data delivery between the UE and the network. That is, RB means a service provided for L2 for data transmission between the UE and E-UTRAN. The configuration of the RB involves a process for specifying a radio protocol layer and channel properties to provide a specific service and to determine the respective parameters and operations. The RB is classified into two types, that is, a signaling RB (SRB) and a data RB (DRB). The SRB is used as a route for the transmission of an RRC message on the control plane. DRB is used as a route for transmitting user data on the user plane.
[045] With reference to FIG. 2, the RLC and MAC layers (terminating in the eNB on the network side) can perform functions, such as programming, automatic repeat request (ARQ), and hybrid automatic repeat request (HARQ). The RRC layer (terminated in the eNB on the network side) can perform functions, such as transmission, paging, connection management
Petition 870190068249, of 07/18/2019, p. 23/77
13/43 RRC, RB control, mobility functions, and UE measurement and control reports. The NAS control protocol (terminated at the gateway's MME on the network side) can perform functions such as SAE bearer management, authentication, LTE_IDLE mobility handling, LTEJDLE paging origin, and security control for signaling between the gateway and the UE.
[046] With reference to FIG. 3, the RLC and MAC layers (terminated in the eNB on the network side) can perform the same functions for the control plane. The PDCP layer (terminated in the eNB on the network side) can perform user plan functions, such as header compression, integrity protection and encryption.
[047] FIG. 4 shows 5G system architecture.
[048] With reference to FIG. 4, a Next Generation Radio Access Network (NG-RAN) node can be a gNB providing terminations of a user plan protocol and NR Radio Access control plan (NR) to the UE or an ng-eNB providing terminations protocol of user plan and control plan for Evolved Universal Terrestrial Radio Access (E-UTRA) in relation to the UE. The gNBs and ng-eNBs can be interconnected with each other via the Xn interface. The gNBs and ng-eNB can also be connected through the ng interfaces to the 5G core network (5GC), more specifically the AMF (Access and Mobility Management Function) through the NG-C interface and to the UPF (Function of Access and Mobility) User Palno), through the NG-U interface. The NG-C can be a control plane interface between NG-RAN and 5GC, and the NG-L can be a user plane interface between NG-RAN and 5GC.
[049] FIG. 5 shows functional division between NG-RAN and 5GC.
[050] With reference to FIG. 5, gnB and nb-eNB can accommodate the following functions:
- Radio Resource Management Functions: Control of
Petition 870190068249, of 07/18/2019, p. 24/77
14/43
Radio carrier, Radio Admission Control, Connection Mobility Control, Dynamic allocation of resources to UEs in both uplink and downlink (programming);
- Compression of IP header, encryption and data integrity protection;
- Selection of an AMF in an UE attachment when no routing to an AMF can be determined from the information provided by the UE;
- User Plan data routing to UPF (s);
- Control Plan information routing to AMF;
- Connection configuration and release;
- Programming and transmission of paging messages;
- Programming and transmission of system broadcast information (originated from AMF or O&M);
- Measurement and configuration of measurement report for mobility and programming;
- Marking a transport level package in the uplink;
- Session Management;
- Network Division support;
- QoS Flow Management and mapping for radio data carriers;
- Support of UEs in RRCJNACTIVE state;
- Distribution function for NAS messages;
- Radio access network sharing;
- Dual connectivity;
- Close interworking between NR and E-UTRA.
[051] The Access and Mobility Management Function (AMF) can host the following main functions:
Petition 870190068249, of 07/18/2019, p. 25/77
15/43
- NAS signaling termination;
- NAS signaling security;
- AS Security Control;
- Inter CN node signaling for mobility between 3GPP access networks;
- UE accessibility in idle mode (including control and execution of paging relay);
- Registration Area Management;
- Support of intra-system and inter-system mobility;
- Access Authentication;
-Access Authorization including verification of roaming rights;
- Mobility management control (subscription and policies);
- Network Division support;
- SMF selection.
[052] The User Plan Role (UPF) can host the following main functions:
- Anchoring point for intra / Inter-RAT mobility (when applicable);
- External PDU session point for interconnection to the data network;
- Routing and packet forwarding;
- Package Inspection and part of user plan of application of policy rule;
- Traffic usage reports;
- Uplink classifier to support routing traffic flows to a data network;
- Branch point to support multidomestic PDU session;
- QoS handling for user plan, for example, packet filtering, gating, application of UL / DL rate;
- Verification of uplink traffic (flow mapping from SDF to QoS);
Petition 870190068249, of 07/18/2019, p. 26/77
16/43
- Downlink pack buffer storage and downlink data notification trigger.
[053] The Session Management (SMF) function can host the following main functions:
- Session Management;
- UE IP address allocation and management;
- Selection and control of the UP function;
- Directing traffic of condifugations at the UPF to route traffic to the appropriate destination;
- Control part of application of policies and QoS;
- Notification of Downlink Data.
[054] Hereafter, a random access procedure is described in the LTE system.
[055] First of all, a user device performs a random access procedure in the case of one of the following cases.
- In case user equipment performs initial access, without a connection (for example, RRC connection) to a base station
- In case a user's equipment initially accesses a target cell through a handover procedure
- If requested by a command given by a base station
- In case uplink data is generated in a situation that an uplink time synchronization is not matched or a radio resource used to request a radio resource is not allocated
- Case of a recovery process in case of a Radiolink failure (RLF) or a handover failure [056] In the LTE system, a random access procedure based on non-containment is provided as follows. First, a base station assigns a
Petition 870190068249, of 07/18/2019, p. 27/77
17/43 dedicated random access preamble designed for specific user equipment. Second, the corresponding user equipment performs a random access procedure using the random access preamble. So to speak, in a random access preamble selection process, there is a contention-based random access procedure and a non-contention-based random access procedure. In particular, according to the contention-based random access procedure, a user device randomly selects a random access preamble from a specific set and then uses the selected random access preamble. According to the non-contention based random access procedure, a random access preamble assigned by a base station to specific user equipment is used only. The differences between the two types of random access procedures are found in the presence or absence of a containment problem. The random access procedure based on non-containment can be used, as mentioned in the previous description, only if a handover process is performed or is requested by a command given by a base station.
[057] FIG. 6 shows a contention-based random access procedure.
[058] In step S610, in a contention-based random access procedure, a user device randomly selects a random access preamble from a set of random access preambles indicated by means of a system information or a security command. handover, selects a PRACH resource (physical RACH) capable of carrying the selected random access preamble, and then transmits the corresponding random access preamble through the selected resource.
[059] In step S620, after the user equipment has transmitted the
Petition 870190068249, of 07/18/2019, p. 28/77
18/43 random access preamble as above, it attempts to receive its random access response within a random access response receiver window indicated via system information or the handover command from a base station. In particular, the random access response information is transmitted in the MAC PDU format. And, the MAC PDU is delivered through PDSCH (shared physical downlink channel). In order that the user equipment properly receives the information transmitted through the PDSCH, PDCCH is delivered, too. In particular, information about user equipment should receive PDSCH, time and frequency information from a radio resource from the PDSCH, a transmission format from the PDSCH, and the like are included in the PDCCH. Once the user equipment successfully receives the PDCCH transmitted to it, the user equipment appropriately receives a random access response transmitted over the PDSCH according to the PDCCH information. And, in the random access response, a random access preamble identifier (ID), a UL grant (UL radio resources), a temporary cell identifier (temporary C-RNTI), and time alignment commands (values of correction of time synchronization, hereinafter abbreviated TAC) are included. As mentioned in the description above, the random access preamble identifier is required for the random access response. The reason for this is described as follows. First, since random access response information for at least one or more user devices can be included in a single random access response, it is necessary to notify that the UL grant, the temporary C-RNTI and the TAC are valid for each user equipment. And, the random access preamble identifier corresponds to the random access preamble selected by the user equipment in step S610.
[060] In step S630, if the user equipment receives the response from
Petition 870190068249, of 07/18/2019, p. 29/77
19/43 random access valid by itself, the user equipment individually processes each of the information included in the received random access response. In particular, the user equipment applies the TAC and saves the temporary C-RNTI. In addition, the user equipment transmits a set of data stored in its buffer or newly generated data at the base station using the received UL grant. In this case, the data included in the UL grant must contain an identifier for the user equipment. In the contention-based random access procedure, the base station is unable to determine which types of user equipment perform the random access procedure. Thus, in order to resolve contention in the future, the base station must identify the corresponding user equipment. The user equipment identifier can be included by one of the two types of methods as follows. First, if the user equipment has a valid cell identifier previously assigned by a corresponding cell before the random access procedure, the user equipment transmits its cell identifier through the UL grant. On the contrary, if the user equipment fails to receive the valid cell identifier before the random access procedure, the user equipment transmits its unique identifier (for example, STMSI, Random Id, etc.), inclusive. In general, the exclusive ID is greater than a cell identifier. If the user equipment transmits data through the UL grant, the user equipment starts a contention timer (hereinafter referred to as a contention timer resolution).
[061] In step S640, after the user equipment transmits the data containing its identifier through the UL grant included in the random access response, it waits for an indication from the base station for the containment resolution. In particular, the user equipment attempts to receive a PDCCH in order to receive a specific message. When receiving the PDCCH, there are two types
Petition 870190068249, of 07/18/2019, p. 30/77
20/43 of methods. As mentioned in the previous description, if the user equipment identifier transmitted through the UL grant is the cell identifier, the user equipment attempts to receive the PDCCH using its cell identifier. If the identifier is the unique identifier, the user equipment attempts to receive the PDCCH using the temporary C-RNTI included in the random access response. Then, in the first case, if the user device receives the PDCCH through its cell identifier before the containment resolution timer expires, the user device determines that the random access procedure has been performed normally and then ends the procedure random access. In the latter case, if the user equipment receives the PDCCH through the temporary cell identifier before the contention resolution timer expires, the user equipment checks the data delivered by the PDSCH indicated by the PDCCH. If the unique identifier of the user equipment is included in the substance of the data, the user equipment determines that the random access procedure was performed normally and then ends the random access procedure.
[062] FIG. 7 shows a random access procedure based on noncontainment.
[063] Unlike the contention-based random access procedure, in a non-contention-based random access procedure, if a random access response information is received, a random access procedure is terminated by determining that the random access procedure was performed normally. The random access procedure based on non-containment can exist in one of two cases, that is, a first case of a transfer process and a second case requested by a command given by a base station. Of course, a contention-based random access procedure can be performed in either case. First, for a
Petition 870190068249, of 07/18/2019, p. 31/77
21/43 random access procedure based on non-containment, it is important to receive a designated random access preamble having no possibility of containment from a base station. The preamble of random access can be indicated by a handover command or a PDCCH command. After the base station has assigned the random access preamble designated only for the user's equipment, the user's equipment transmits the preamble to the base station.
[064] Hereinafter, a protocol data unit (PDU) is described.
[065] A MAC PDU is a string of bits that is aligned in bytes (ie multiple of 8 bits) in length. MAC SDUs are strings of bits that are aligned in bytes (ie multiple of 8 bits) in length. A service data unit (SDU) is included in a MAC PDU from the first bit onwards.
[066] FIG. 8 shows an example of MAC PDU including MAC header, MAC control elements, MAC SDUs and padding.
[067] With reference to FIG. 8, a MAC PDU consists of a MAC header, zero or more MAC SDUs, zero or more MAC control elements, and optionally padding. Both the MAC header and the MAC SDUs are of variable sizes. Both the MAC header and the MAC SDUs are of variable sizes. A MAC PDU header consists of one or more MAC PDU subheadings. Each subheader corresponds to either a MAC SDU, a MAC control element or padding. A MAC PDU subheader consists of five or six fields of the R / F2 / E / LCID / (F) / L header but for the last subheader in the MAC PDU and for fixed-size MAC control elements. The last sub-header in the MAC PDU and sub-headers for fixed-length MAC control elements consist of only one of the four header fields
Petition 870190068249, of 07/18/2019, p. 32/77
22/43
R / F2 / E / LCID. A sub-header PDU MAC corresponding to the padding consists of the four fields of the R / F2 / E / LCID header.
[068] MAC PDU subheadings have the same order as the MAC SDUs, corresponding MAC control elements and padding. MAC control elements are always placed before any MAC SDU. Filling occurs at the end of the MAC PDU, except when single-byte or two-byte filling is required. Padding can have any value and the MAC entity must ignore it. When filling is done at the end of the MAC PDU, zero or more filling bytes are allowed. When single-byte padding or two bytes is required, one or two MAC PDU subheadings corresponding to the padding are placed at the beginning of the MAC PDU, before any other MAC PDU subheader. A maximum of one MAC PDU can be transmitted per transport block (TB) per MAC entity. A maximum of one MCH MAC PDU can be transmitted per transmission time slot (TTI).
[069] Meanwhile, for low-cost EU, it is important to save EU power. For example, the low-cost UE includes narrowband Internet of Things (NB-loT) UE, low-complexity (BL) and reduced-bandwidth UE, Machine-Type Communication UE (TCM) or an UE in improved coverage . Thus, the number of transmissions should be reduced to the maximum possible. Early data transmission (EDT) in RRC Connection Establishment or RRC Connection Resume is one of the solutions to reduce the power consumption of the UE. However, the current system does not support early data transmission. Hereinafter, a method for a UE to perform EDT and an apparatus supporting it according to an embodiment of the present invention are described in detail. In the specification, EDT can be transmission of uplink data during the random access procedure. EDT can optionally allow the transmission of uplink data followed by a transmission of
Petition 870190068249, of 07/18/2019, p. 33/77
23/43 downlink data during the random access procedure. For example, EDT may optionally allow the transmission of uplink data followed by a transmission of downlink data during the random access procedure without establishing or resuming the RRC connection. S1 connection can be established or resumed after receiving uplink data and can be released or suspended after downlink data transmission. Early data transmission may refer to both EDT control plan (CP) -EDT and user plan (UP) EDT [070] According to a modality of the present invention, during the execution of the state transition procedure , such as RRC RRC connection establishment or resumption procedure procedure, the UE may transmit data in a message along radio carrier signaling (SRB), such as DCCH or CCCH. The message can be a NAS message or an RRC message, such as an RRC Connection Request message or RRC Connection resume message. Alternatively, during the execution of the state transition procedure, such as RRC RRC connection establishment or resumption procedure procedure, the UE can transmit data from a message on the EDT-configured data carrier (DRB).
[071] FIG. 9 shows a procedure for determining whether or not to perform EDT according to an embodiment of the present invention.
[072] EDT can be triggered when the upper layers request the establishment or resumption of RRC Connection for Mobile Originated data (ie, without signaling or SMS) and the size of the uplink data is less than or equal to one transport block size (TB) indicated in the system information. EDT cannot be used for data on the control plane when using EPS CloT optimizations of User Plan. EDT can be
Petition 870190068249, of 07/18/2019, p. 34/77
24/43 applicable to BL UEs, UEs in improved coverage or NB-loC UEs. EDT can be initiated by the upper layers (for example, EU RRC).
[073] With reference to FIG. 9, in step S910, the UE can receive system information, including a limit for the EDT, from a base station. The limit for EDT can be a limit related to a data size for EDT. The limit for EDT can be a limit related to QoS characteristics, maximum bit rate or delay requirement for the UE. For example, the system information can be defined as Table 1.
[Table 1] § EDT-TBS-NB-rlS: - SEQÜENCIA {esít-SfflíillTBS-EfiâMeíhrij 8GQLEANO
Enumerated MOS. bSOL U584,; bO. blOÕQ} ::> ':: $:
[074] Referring to Table 1, edt-SmalITBS-enabled can be a TRUE value which indicates that the UE performing EDT is allowed to select TBS smaller than edt-TBS for Msg3 according to the corresponding NPRACH resource, edt-TBS can be larger TBS for Msg3 for an NPRACH resource applicable to a UE performing EDT. Value in bits. Value b328 corresponds to 328 bits, value b408 corresponds to 408 bits and so on. Edt-TBS can be a limit related to a data size for EDT [075] In step S920, the UE can determine whether a condition to initiate EDT is satisfied or not, based on the limit and a data size for transmission. The data for data transmission can be layer 2 data or layer 3 data. For example, layer 2 data can be MAC PDU. For example, the data size can be uplink data available for transmission plus MAC header and, where necessary,
Petition 870190068249, of 07/18/2019, p. 35/77
25/43
MAC.
[076] Specifically, the UE can compare the limit for EDT with the size of the data for transmission. The UE can then determine whether the condition for initiating EDT is met or not, by comparing this limit for EDT with the data size for transmission.
[077] - Option 1: If the data size for transmission is less than the EDT limit, the UE can determine that the condition to start EDT is satisfied. In this case, in step S930, the UE can perform EDT. That is, the UE can transmit data to the base station using message 3 during the random access procedure.
[078] - Option 2: If the data size for transmission is greater than the limit for EDT, the UE may determine that the condition for initiating EDT is not met. In this case, in step S935, the UE cannot perform EDT. That is, the UE can transmit data to the base station after the completion of the RRC connection establishment or resumption procedure. For example, in the case where the data size for transmission is higher than the limit for EDT, the UE can transmit data to the base station after the UE transitions from RRCJDLE to RRC_CONNECTED. In addition, an EU MAC can indicate to the EU RRC that EDT is canceled.
[079] In addition, the UE can determine whether a condition to initiate EDT is met or not, based on the limit and data delay requirement. The limit can be a limit related to the delay requirement for EDT. The UE can determine whether the data for transmission meets the delay requirement for EDT or not. If the data delay requirement is less than the limit for EDT, the UE may determine that the data for transmission meets the delay requirement for EDT. If the data delay requirement is greater than the limit for EDT, the UE may determine that the data for transmission does not meet the requirement for
Petition 870190068249, of 07/18/2019, p. 36/77
26/43 delay for EDT.
[080] In accordance with an embodiment of the present invention, the UE can determine whether or not to perform EDT during the random access procedure. For example, in the case where the data size for transmission is less than the limit for EDT, the UE can transmit data to the base station using message 3 during the random access procedure. Thus, the power consumption of the UE (for example, low-cost UE) can be reduced.
[081] In accordance with an embodiment of the present invention, the configuration of the radio carriers can be mapped to EDT. If a cell indicates EDT for User Palno EPS loT optimization, the UE supporting EDT for User Palno EPS loT optimization can configure DRB (s) (including RLC / PDCP entities and logical channels) mapped to EDT. The UE in RRC_CONNECTED can be configured with DRB (s) mapped to EDT and other DRB (s) not mapped to EDT. If the UE receives release of the RRC connection indicating indication of suspend and the DRB (s) mapped to EDT, and if the cell indicates EDT for the EPS optimization of Palno de User, the UE that establishes an RRC connection in the cell it may be allowed to transmit data available for transmission via the DRB (s) mapped to EDT while in the procedure of establishing or resuming RRC connection. However, the UE cannot be allowed to transmit data available for transmission via DRB (s) not mapped to EDT in the procedure for establishing or resuming RRC connection. If the UE transmits a MAC PDU, including data about the DRB (s) mapped to EDT, an LCID indicating the DCCH mapped to EDT can be included as a MAC sub-header of the MAC PDU. The embodiment of the present invention can be applied in conjunction with the example in FIG. 10A and 10B.
[082] In accordance with an embodiment of the present invention, EDT can be authorized by priority. To control EDT, the base station can indicate one or
Petition 870190068249, of 07/18/2019, p. 37/77
27/43 various priorities for the UE through system information or a dedicated RRC message such as RRC connection release message. The priority can be one of a logical channel priority and a packet priority. The priority can be mapped to one or more radio carriers or logical channels mapped to EDTs. The base station can inform the UE that the priorities are allowed to run EDT during the RRC connection establishment or resumption procedure. Thus, if data becomes available for a radio carrier or a logical channel, and if the base station indicating the priority of the radio carrier or the logical channel is allowed for EDT, the UE can perform EDT. Otherwise, the UE cannot execute EDT. That is, the UE can perform data transmission after completing the RRC connection establishment or resumption procedure. The embodiment of the present invention can be applied in conjunction with the example in FIG. 10A and 10B.
[083] In accordance with an embodiment of the present invention, to control EDT, the base station can indicate one or more QoS class identifiers (QCIs) to the UE through system information or a dedicated RRC message as a release message RRC connection QCI can be mapped to one or more radio carriers or logical channels mapped to EDTs. The base station can inform the UE that QCI (s) are allowed to perform EDT during the RRC connection establishment or resumption procedure. Thus, if the data becomes available for a radio carrier or a logical channel, and if the base station indicates that the QCI of the radio carrier or the logical channel is allowed for EDT, the UE can perform EDT. Otherwise, the UE cannot execute EDT. That is, the UE can perform data transmission after the completion of the procedure for establishing or resuming the RRC connection. The embodiment of the present invention can be applied in conjunction with the example in FIG. 10A and 10B.
[084] In accordance with an embodiment of the present invention, to control
Petition 870190068249, of 07/18/2019, p. 38/77
28/43
EDT, the base station can indicate one or more QoS flows to the UE through the system information or a dedicated RRC message, such as an RRC connection release message. The QoS flow can be mapped to one or more radio carriers or logical channels mapped to EDTs. The base station can inform the UE which QoS flow (s) are authorized to perform EDT during the RRC connection establishment or resumption procedure. Thus, if data becomes available for a radio carrier or a logical channel, and if the base station indicates that the QoS flow from the radio carrier or the logical channel is allowed for EDT, the UE can perform EDT. Otherwise, the UE cannot execute EDT. That is, the UE can perform data transmission after the completion of the procedure for establishing or resuming the RRC connection. The embodiment of the present invention can be applied in conjunction with the example in FIG. 10A and 10B.
[085] In accordance with an embodiment of the present invention, EDT may be allowed based on QoS characteristics, such as bit rate or delay. To control EDT, the base station can indicate one or more limits. The one or more limits can be related to at least one of the QoS characteristics, the amount of data (for example, a data size), the bit rate (maximum) or delay requirement for the UE through the system information or a dedicated RRC message such as an RRC connection release message. The characteristics of QoS, bit rate (maximum) or delay requirement can be mapped to one or more radio carriers or logical channels mapped to EDTs.
[086] For example, the base station can inform the UE about the maximum bit rate that is allowed to execute EDT during the RRC connection establishment or resumption procedure. So, if the data becomes available to a radio carrier or a logical channel, and if the amount of data
Petition 870190068249, of 07/18/2019, p. 39/77
29/43 (for example, a data size or message size) available for transmission is less than the limit indicated by the base station, the UE performs EDT. The limit can be included in the system information, and the data can be in layer 2 (for example, MAC PDU) and / or layer 3 (for example, RRC message). Otherwise, the UE cannot execute EDT. That is, the UE can perform data transmission after the completion of the procedure for establishing or resuming the RRC connection.
[087] For example, the base station can inform the UE about the delay requirement that is allowed to execute EDT during the RRC connection establishment or resumption procedure. Thus, if the data becomes available to a radio carrier or a logical channel, and if the amount of data (for example, a data size or message size) available for transmission must satisfy the delay requirement indicated by the base station , for example, data must be transmitted within 100 ms indicated by the base station, the UE can perform EDT. Otherwise, the UE cannot execute EDT. That is, the UE can perform data transmission after the completion of the procedure for establishing or resuming the RRC connection. The embodiment of the present invention can be applied in conjunction with the example in FIG. 10A and 10B.
[088] FIG. 10A and 10B show a process for carrying out EDT according to an embodiment of the present invention.
[089] With reference to FIG. 10A and 10B, in step S1000, the UE can camp in a cell. For example, the cell can be an NB-loT cell or an LTE cell supporting one or more narrow band for low cost UE capabilities, such as Category M1.
[090] In step S1010, the UE can receive system information from a base station via the cell. The system information can transmit at least one of CCCH2 to EDT configuration, configuration of
Petition 870190068249, of 07/18/2019, p. 40/77
30/43 radio carriers (for example DRBs including DTCHs) mapped to EDT, RAPID indicating EDT or LCID from CCCH2 to EDT. Each cell can inform one or more UEs that this cell supports EDT for the optimization of EPS CloT of Control Plan and / or EDT for the optimization of EPS CloT of User Plan via system information.
[091] If the cell indicates EDT for User Palno EPS loT optimization, the UE supporting EDT for User Palno EPS loT optimization can configure DRB (s) (including RLC / PDCP entities and logical channels) mapped to EDT. In this case, the UE can configure a logical CCCH channel and one or more logical DTCH channels for uplink. The CCCH logical channel may have a higher priority than the DTCH logical channel (s) mapped to EDT and all MAC control elements. The DTCH logical channel (s) mapped to EDT may have a higher priority than some or all of the MAC Control Element (s) (for example, the Data Volume MAC Control and Power Headroom Report element ( DPR), Buffer Status Report MAC Control Element, Power Headroom MAC Control Element). The DTCH logical channel (s) mapped to EDT may have a higher priority than DTCH logical channels not mapped to EDT.
[092] If the cell indicates EDT for the optimization of EPS CloT of Control Plan, the UE supporting EDT for the optimization of EPS CloT of Control Plan can configure CCCH2 for EDT. In this case, the UE can configure two different CCCH logical channels for uplink. The first CCCH logical channel may have a higher priority than the second CCCH logical channel in MAC logical channel prioritization. The first CCCH logic channel can be SRBO while the second CCCH logic channel can be SRBObis. The first CCCH logical channel may be applicable for uplink and downlink, while the second CCCH logical channel may be applicable only for uplink. The first CCCH logical channel can have a
Petition 870190068249, of 07/18/2019, p. 41/77
31/43 higher priority than all MAC control elements. The second CCCH logic channel may have a lower priority than a given MAC control element (s) (for example, Data Volume MAC Control Element and Power Headroom Report (DPR), Control Element Buffer Status Report MAC, Power Headroom MAC Control Element). The second logical CCCH channel can have a higher priority than the other MAC control element (s). Alternatively, both CCCH logic channels can have a higher priority than all MAC Control Elements.
[093] CCCH2 can be replaced by DCCH mapped to EDT or a legacy CCCH. For example, DCCH mapped to EDT can be used to transport EDT instead of CCCH2. However, DCCH not mapped to EDT cannot be used to transport EDT.
[094] If the cell does not indicate EDT, UE does not perform EDT.
[095] In step S1020, if the UE has been suspended after releasing the previous RRC connection, DTCH (s) mapped to EDT may have been configured but suspended for the UE. In this case, if the UE detects UL data for the DTCH (s), the UE can resume the DTCH (s) mapped to EDT and then submit the UL data to the lower layers (RLC / PDCP entities) on the mapped DTCH for EDT. This behavior cannot be applied to DTCHs (ie DRBs) not mapped to EDT. Therefore, the UE cannot perform EDT for UL data during DTCHs (i.e. DRBs) not mapped to EDT. If the UE detects UL data, the UE can also trigger RRC connection establishment procedure or RRC connection resumption procedure. The RRC connection request message or the RRC resume request message can be submitted to CCCH1 for SRBO.
[096] In step S1030, if a random access procedure is triggered,
Petition 870190068249, of 07/18/2019, p. 42/77
32/43 the MAC layer of the UE (i.e. MAC UE) can select one of the random access preamble identifiers (Rapids) mapped to EDT (as received from the cell via the system information). The UE can then transmit a random access preamble with the selected random access preamble identifier (RAPID).
[097] In step S1040, MAC UE can receive a random access response message (RAR) that indicates the transmitted RAPID and an uplink lease. If MAC UE does not receive any RAR indicating transmitted RAPID, MAC UE retransmits a random access preamble with power increase.
[098] The EU MAC can perform logical channel prioritization. Then, the EU MAC can build MAC PDU according to the logical channel priorities and the uplink grant. In prioritizing the logical channel, CCCH1 and DCTs mapped to EDT may have a higher priority than all MAC control elements and other DCCHs not mapped to EDT.
[099] In the MAC PDU, if CCCH data is included, LCID indicating CCCH can be included as a MAC subheader. In addition, if DCT data mapped to EDT is included, LCID indicating the DCCH mapped to EDT can be included as a MAC subheader.
[0100] If the UL grant received can accommodate all UL data on the DCCH mapped to EDT, and if the UE has no remaining UL data during any logical channel, the UE can include MAC Control Element Buffer Status Report ( BSR) indicating that there is no data, Data Volume MAC Control Element and Power Buffer Report (DPR) indicating that there is no data (ie, DV value = 0), or no MAC Control Element.
[0101] If the UL grant received can accommodate some UL data on the DCCH mapped to EDT with a MAC control element, such as CE MAC BSR or CE MAC DPR, and if the UE has remaining UL data on any channel
Petition 870190068249, of 07/18/2019, p. 43/77
Of course, the UE may include CE MAC BSR indicating the amount of UL data remaining or CE MAC DPR indicating the amount of UL data remaining.
[0102] If the UL grant received cannot accommodate any UL data in the DCCH mapped to EDT with a MAC control element, such as CE MAC BSR or CE MAC DPR, the UE can include CE MAC BSR indicating the amount of data Remaining UL or CE MAC DPR indicating the amount of UL data remaining.
[0103] In step S1050, the EU MAC can transmit the MAC PDU (ie message 3 (MSG3)) to the base station using the uplink lease.
[0104] In step S1060, if the EU MAC can receive contention resolution for message 3 from the base station (for example, through PDCCH or CE Containment Resolution MAC), the EU MAC can consider the RACH procedure well successful. Otherwise, the EU MAC may re-transmit a random access preamble.
[0105] The UE can receive RRC connection establishment message or RRC connection resume message from the base station. If the message received indicates NACK for EDT, the UE layer that received the NACK can send the NACK to a higher layer of the UE. For example, for EDT over SRB in the EPS CloT Optimization Control Plan, if the EU RRC receives the NACK from the message, the EU RRC can inform the EU NAS about the NACK to UL data. Upon receiving the NACK, the upper layer of the UE (for example, NAS UE) can relay UL data. If so, the EU RRC can create an RRC message, including UL data and send the RRC message to lower layers (for example PDCP / RLC / MAC). The RRC message can be carried over any CCCH2 or DCCH. If the message is carried over DCCH, the message can be a complete RRC connection setup / resume including UL data. UL data can include UL data that is
Petition 870190068249, of 07/18/2019, p. 44/77
34/43
NACKed (unconfirmed) and / or UL data remaining. In this way, the UE can transmit a single MAC SDU including complete RRC connection setup / resume, including UL data with an EC MAC on a MAC PDU. The EC MAC on the MAC PDU can be either CE MAC BSR indicating the amount of UL data remaining or CE MAC DPR indicating the amount of UL data remaining. If there is no UL data remaining except the UL data included in the MAC PDU, the CE MAC can indicate the absence of data.
[0106] If the UE receives an RRC message indicating that the data is confirmed, the UE can consider that the data is confirmed at Layer 1, 2 or 3, and the UE can stop with data (re) transmissions and RLC / acknowledgments MAC, if any. The UE can release the connection of RRC and Layer 2 entities, and insert RRCJDLE. The RRC message can be an RRC connection release message, an RRC connection rejection message, an RRC connection configuration message and an RRC connection resume message.
[0107] For example, if the CE MAC indicates that there is no data, and if the base station successfully receives all UL data, in which case there is no DL data, the base station can transmit RRC connection release indicating ACK to UL data. Upon receiving the RRC connection release indicating ACK for UL data, the UE can assume that the UL data that was transmitted is confirmed and enter RRCJDLE. the EU RRC can inform RLC / MAC EU that the UL data that has been transmitted is confirmed and (re) transmissions must be stopped.
[0108] If the UE receives RRC connection release or rejection message not indicating ACK for UL data, the UE can consider that the UL data that was transmitted is unconfirmed and enter RRCJDLE. The UE can trigger RRC connection establishment procedure or RRC connection reconnection procedure to retransmit unconfirmed data later.
Petition 870190068249, of 07/18/2019, p. 45/77
35/43 [0109] If the UE transmits data about SRB or DRB, and if the UE receives an RRC connection configuration message (or an RRC connection resume message), indicating that the data is confirmed, the UE cannot transmit a complete RRC connection setup message (or a complete RRC connection resume message), and consider the RRC procedure successful, and then insert RRCJDLE.
[0110] If the UE transmits data about SRB or DRB, and if the procedure for establishing RRC connection or resuming RRC connection with EDT fails, for example, the procedure ends unsuccessfully due to the receipt of the RRC connection rejecting or T300 expires, the UE can consider that the data is unconfirmed at Layer 1, 2 or 3, and the UE can stop with data (re) transmissions and RLC / MAC acknowledgments, if any. So, if the data was transmitted via DRB (or SRB), the UE can reinstate and suspend Layer 2 entities. If the data was transmitted via SRB, the UE can release Layer 2 entities. Finally, the UE can insert RRCJDLE and can trigger the procedure for establishing RRC connection or resuming RRC connection for re-transmission of data that has not been delivered and not confirmed in Layer 1,2 or 3.
[0111] According to one embodiment of the present invention, the UE can perform the initial transmission on one type of SRB and re-transmission through another type of SRB, based on an RRC (or NAS) message indicating NACK for the initial transmission over SRB. If the UE receives RRC connection establishment message or RRC connection resume message indicating NACK for data transmission via SRB, the UE can retransmit the data in the same type of message (for example, connection request message from RRC or RRC connection resume message) or other type of message (for example, complete
Petition 870190068249, of 07/18/2019, p. 46/77
36/43 RRC connection or full message resume from RRC connection). If the UE receives a CCCH message indicating NACK for the transmission of data over SRB, the UE can retransmit the data over CCCH regardless of DCCH configuration. If the UE receives a CCCH message indicating NACK for the transmission of data over SRB, the UE can retransmit the data over DCCH, if DCCH is configured. The embodiment of the present invention can be applied in conjunction with the example in FIG. 11A and 11B.
[0112] FIG. 11A and 11B show a process for carrying out EDT according to an embodiment of the present invention.
[0113] With reference to FIG. 11A and 11B, in step S1100, the UE can camp in a cell. For example, the cell can be an NB-loT cell or an LTE cell supporting one or more narrow band for low cost UE capabilities, such as Category M1. The system information can transmit at least one CCCH2 to EDT configuration, radio carrier configuration (for example DRBs including DTCHs) mapped to EDT, RAPID indicating EDT or LCID from CCCH2 to EDT. Each cell can inform one or more UEs that this cell supports EDT for the optimization of EPS CloT of Control Plan and / or EDT for the optimization of EPS CloT of User Plan via system information.
[0114] If the cell indicates EDT for the optimization of EPS CloT of Control Plan, the UE supporting EDT for the optimization of EPS CloT of Control Plan can configure CCCH2 for EDT. In this case, the UE can configure two different CCCH logical channels for uplink. The first CCCH logical channel may have a higher priority than the second CCCH logical channel in MAC logical channel prioritization. The first CCCH logic channel can be SRBO while the second CCCH logic channel can be SRBObis. The first CCCH logical channel may be applicable for uplink and downlink, while the second CCCH logical channel may be applicable only for uplink. The first CCCH logic channel can have a
Petition 870190068249, of 07/18/2019, p. 4ΊΠΊ
37/43 higher priority than all MAC CEs. The second CCCH logical channel may have a lower priority than a given MAC CE (s) (eg, Data Volume and Headroom Power Report (DPR) MAC, CE Buffer Status Report MAC, CE Headroom MAC), and a higher priority than the other MAC CE (s). Alternatively, both CCCH logic channels can have a higher priority than all MAC CEs. CCCH2 can be replaced with DCCH mapped to EDT or a legacy CCCH. For example, DCCH mapped to EDT can be used to transport EDT instead of CCCH2. However, DCCH not mapped to EDT cannot be used to transport EDT.
[0115] If the cell does not indicate EDT, UE does not perform EDT.
[0116] If the UE detects UL and CCCH2 data is configured, the UE can send the UL data to lower layers over CCCH type 2 (for example, an RLC entity from CCCH2 to SRBObis). If the UE detects UL data and an EDT-mapped DTCH is configured, the UE can send the UL data to lower layers (RLC / PDCP entities) over the EDT-mapped DTCH.
[0117] If the UE detects UL data, the UE can also trigger RRC connection establishment procedure or RRC connection resumption procedure. The RRC connection request message or the RRC resume request message can be submitted to CCCH1 for SRBO.
[0118] In step S1110, if a random access procedure is triggered, the MAC layer of the UE (ie the MAC UE) can select one of the random access preamble identifiers (RAPIDS) mapped to EDT (as received from cell via system information). The UE can then transmit a random access preamble with the selected random access preamble identifier (RAPID).
Petition 870190068249, of 07/18/2019, p. 48/77
38/43 [0119] In step S1120, the EU MAC can receive a random access response message (RAR) indicating the transmitted RAPID and an uplink grant. If the MAC UE does not receive any RAR indicating the transmitted RAPID, the MAC UE re-transmits a random access preamble with increased power.
[0120] In step S1130, the EU MAC can perform logical channel phohtization. Then, the EU MAC can build MAC PDU according to the logical channel priorities and the uplink grant. In logical channel prioritization, CCCH1 and CCCH2 can have a higher priority than all MAC CEs.
[0121] In the MAC PDU, if CCCH data is included, LCID indicating CCCH can be included as a MAC subheader. In addition, if CCCH2 data is included, LCID indicating CCCH2 can be included as a MAC subheader.
[0122] If the UL grant received can accommodate all UL data in CCCH2, and if the UE has no remaining UL data on any logical channel, the UE can include CE MAC BSR indicating that there is no data, CE MAC DPR indicating that there is no data (that is, DV value = 0), or there is no CE MAC.
[0123] If the UL grant received can accommodate some UL data in CCCH2 with a CE MAC such as CE MAC BSR or CE MAC DPR, and if the UE has remaining UL data on any logical channel, the UE can include CE MAC BSR indicating the amount of remaining UL data or CE MAC DPR indicating the amount of remaining UL data.
[0124] If the UL grant received cannot accommodate any UL data in CCCH2 with a CE MAC such as CE MAC BSR or CE MAC DPR, the UE may include CE MAC BSR indicating the amount of remaining UL data or CE MAC DPR indicating the amount of the remaining UL data.
Petition 870190068249, of 07/18/2019, p. 49/77
39/43 [0125] In step S1140, the EU MAC can transmit the MAC PDU (ie message 3 (MSG3)) to the base station using the uplink lease.
[0126] In step S1150, if the EU MAC can receive contention resolution for message 3 from the base station (for example, through PDCCH or CE Containment Resolution MAC), the EU MAC can consider the RACH procedure as well successful. Otherwise, the EU MAC may re-transmit a random access preamble.
[0127] In step S1160, the UE can receive RRC connection establishment message or RRC connection resume message from the base station. If the received message indicates NACK for EDT, the UE layer that received the NACK can send the NACK to a higher layer of the UE. For example, for EDT on SRB in EPS CloT Optimization Control Plan, if the EU RRC receives the NACK from the message, the EU RRC can report the EU NAS on the NACK to UL data. Upon receiving the NACK, the upper layer of the UE (for example, NAS UE) can relay UL data. If so, the EU RRC can create an RRC message, including UL data and send the RRC message to the lower layers (ie, PDCP / RLC / MAC). The RRC message can be carried out over CCCH2 or DCCH.
[0128] In step S1170, if the message is carried over DCCH, the message can be a complete RRC connection setup / resume including UL data. UL data can include UL data that is NACKed (unconfirmed) and / or remaining UL data. In this way, the UE can transmit a single MAC SDU including complete RRC connection setup / resume, including UL data with an EC MAC on a MAC PDU.
[0129] In step S1175, if the message is transmitted via CCCH such as CCCH2, the UE can transmit a complete RRC connection establishment / resume message over the DCCH and including the UL data message
Petition 870190068249, of 07/18/2019, p. 50/77
40/43 during CCCH with a CE MAC on a single MAC PDU or separate MAC PDU. UL data can include UL data that is NACKed (unconfirmed) and / or remaining UL data.
[0130] The CE MAC in the MAC PDU can be either CE MAC BSR indicating the amount of UL data remaining or CE MAC DPR indicating the amount of UL data remaining. If there is no UL data remaining except the UL data included in the MAC PDU, the CE MAC can indicate the absence of data.
[0131] In step S1180, if the CE MAC indicates that there is no data, and if the base station successfully receives all UL data, in which case there is no DL data, the base station can transmit RRC connection release indicating ACK for UL data. Upon receiving the RRC connection release indicating ACK for UL data, the UE can assume that the UL data that was transmitted is confirmed and enter RRCJDLE. the EU RRC can inform RLC / MAC EU that the UL data that has been transmitted is confirmed and (re) transmissions must be stopped.
[0132] If the UE receives RRC connection release not indicating ACK for UL data, the UE can consider that the UL data that was transmitted is not confirmed and enter RRCJDLE. The UE can trigger RRC connection establishment procedure or RRC connection reconnection procedure to retransmit unconfirmed data later.
[0133] FIG. 12 is a block diagram illustrating a method for a UE to perform EDT in accordance with an embodiment of the present invention.
[0134] With reference to FIG. 12, in step S1210, the UE can receive system information, including a limit for the EDT. The UE can be in an RRCJDLE. The UE can be an NB-loT UE. The limit for EDT can be a limit related to the size of data for EDT.
[0135] In step s1220, the UE can determine whether a condition (for example, first condition) to start EDT is met or not, by comparing the
Petition 870190068249, of 07/18/2019, p. 51/77
41/43 limit for EDT with a data size for transmission. EDT can be a transmission of uplink data during a random access procedure.
[0136] The UE may determine that the condition to start EDT is met, if the data size for transmission is less than the limit for EDT. The UE may determine that the condition for initiating EDT is not met, if the data size for transmission is greater than the limit for EDT. The data size can be a data size in layer 2, which includes the MAC layer. The data size for uplink transmission can be data available for transmission plus MAC header.
[0137] The limit for the BRT may be a limit related to the delay requirement for the EDT. In this case, the UE can further determine whether a condition (for example, second condition) to start EDT is met or not, by comparing the limit for EDT with the data delay requirement. The UE can determine that the condition to start EDT is met, if the data delay requirement is less than the limit for EDT. The UE may determine that the condition for initiating EDT is not satisfied, if the requirement for data delay is greater than the limit for EDT.
[0138] In step S1230, the UE can perform EDT if the condition is met.
[0139] In step S1240, the UE can perform a procedure for establishing or resuming an RRC connection if the condition is not met. In addition, the UE can perform data transmission after the RRC connection establishment or resumption procedure is performed, if the condition is not met.
[0140] According to an embodiment of the present invention, the UE can determine whether or not to perform EDT during the random access procedure. For example, in the case where the data size for transmission is
Petition 870190068249, of 07/18/2019, p. 52/77
42/43 less than the limit for EDT, the UE can transmit data to the base station using message 3 during the random access procedure. For example, in the case where the data size for transmission is less than the limit for EDT and the data delay requirement is less than the limit for EDT, the UE can transmit data to the base station using the message 3 during the random access procedure. Thus, the power consumption of the UE (eg low cost EU) can be reduced.
[0141] FIG. 13 is a block diagram illustrating a wireless communication system in accordance with the embodiment of the present invention.
[0142] BS 1300 includes a processor 1301, a memory 1302 and a transceiver 1303. Memory 1302 is connected to processor 1301, and stores various information for driving processor 1301. Transceiver 1303 is connected to processor 1301, and transmits and / or receives radio signals. Processor 1301 implements proposed functions, processes and / or methods. In the above embodiment, a base station operation can be implemented by processor 1301.
[0143] An UE 1310 includes a 1311 processor, a 1312 memory and a 1313 transceiver. The 1312 memory is connected to the 1311 processor, and stores various information to drive the 1311 processor. The 1313 transceiver is connected to the 1311 processor, and transmits and / or receives radio signals. The 1311 processor implements the proposed functions, processes and / or methods. In the above modality, an operation of the user equipment can be implemented by the 1311 processor.
[0144] The processor may include an application specific integrated circuit (ASIC), a separate chip set, a logic circuit, and / or a data processing unit. The memory can include a read-only memory (ROM), a random access memory (RAM), a flash memory, a
Petition 870190068249, of 07/18/2019, p. 53/77
43/43 memory card, a storage medium, and / or other equivalent storage devices. The transceiver may include a baseband circuit for processing a wireless signal. When the modality is implemented in software, the methods mentioned above can be implemented with a module (ie, process, function, etc.) to perform the functions mentioned above. The module can be stored in memory and can be executed by the processor. The memory can be located inside or outside the processor, and it can be coupled to the processor through several well-known means.
[0145] Various methods based on this specification have been described with reference to the drawings and the reference numerals indicated in the drawings on the basis of the examples mentioned above. Although each method describes several steps or blocks in a specific order for ease of explanation, the invention disclosed in the claims is not limited to the order of the steps or blocks, and each step or block can be implemented in a different order, or can be executed simultaneously with other steps or blocks. In addition, those skilled in the art may know that the invention is not limited to each of the steps or blocks, and at least one different step can be added or deleted without departing from the scope and spirit of the invention.
[0146] The aforementioned modality includes several examples. It should be noted that those skilled in the art know that all possible combinations of examples cannot be explained, and they also know that various combinations can be derived from the technique of the present specification. Therefore, the scope of protection of the invention must be determined by combining several examples described in the detailed explanation, without departing from the scope of the following claims.
权利要求:
Claims (15)
[1]
1. Method for performing, by a user equipment (UE), anticipated data transmission (EDT) in a wireless communication, the CHARACTERIZED method because it comprises:
receive system information, including a limit for EDT;
determine whether a condition to start EDT is met or not, by comparing the limit for EDT with a data size for transmission;
if the condition is satisfied, perform the EDT; and if the condition is not met, perform a procedure for establishing or resuming the radio resource control (RRC) connection.
[2]
2. Method according to claim 1, CHARACTERIZED by the fact that the UE determines that the condition to start EDT is satisfied, if the data size for transmission is less than the limit for EDT.
[3]
3. Method according to claim 1, CHARACTERIZED by the fact that the UE determines that the condition to start EDT is not met, if the data size for transmission is higher than the limit for EDT.
[4]
4. Method according to claim 1, CHARACTERIZED by the fact that it additionally comprises:
perform data transmission after the RRC connection establishment or resumption procedure is performed, if the condition is not met.
[5]
5. Method according to claim 1, CHARACTERIZED by the fact that the limit for EDT is a limit related to the size of data for EDT
[6]
6. Method according to claim 1, CHARACTERIZED by the fact that the data size is a data size in a layer 2, which includes a layer of access control to the medium (MAC).
[7]
7. Method according to claim 1, CHARACTERIZED by the fact that
Petition 870190068249, of 07/18/2019, p. 55/77
2/3 that the limit for EDT is a limit related to the delay requirement for EDT
[8]
8. Method according to claim 7, CHARACTERIZED by the fact that it additionally comprises:
determine whether a condition to initiate EDT is met or not, by comparing the limit for EDT with the data delay requirement.
[9]
9. Method according to claim 8, CHARACTERIZED by the fact that the UE determines that the condition to start EDT is satisfied, if the data delay requirement is less than the limit for EDT.
[10]
10. Method according to claim 8, CHARACTERIZED by the fact that the UE determines that the condition to start EDT is not satisfied, if the requirement for data delay is greater than the limit for EDT.
[11]
11. Method according to claim 1, CHARACTERIZED by the fact that the data size for transmission is uplink data available for transmission plus MAC header.
[12]
12. Method according to claim 1, CHARACTERIZED by the fact that EDT is a transmission of uplink data during a random access procedure.
[13]
13. Method according to claim 1, CHARACTERIZED by the fact that the UE is in an RRCJDLE.
[14]
14. Method according to claim 1, CHARACTERIZED by the fact that the UE is a narrowband Internet of Things UE (NB-loT).
[15]
15. User equipment (UE) that performs early data transmission (EDT) in a wireless communication, the UE, FEATURED by the fact that it comprises:
a memory; a transmitter and a processor, connected to the memory and the transceiver, which:
Petition 870190068249, of 07/18/2019, p. 56/77
3/3 controls the transceiver to receive system information, including a limit for the EDT;
determines whether a condition to start EDT is met or not, by comparing the limit for EDT with a data size for transmission;
if the condition is satisfied, the EDT executes; and if the condition is not satisfied, perform an RRC connection establishment or resumption procedure.
类似技术:
公开号 | 公开日 | 专利标题
BR112019014859A2|2020-04-14|method and apparatus for executing edt
US10123254B2|2018-11-06|System and method for applying extended accessing barring in wireless communication system
EP3560273B1|2021-06-09|Method and apparatus for performing edt
JP6074053B2|2017-02-01|Method and apparatus for performing backoff in a wireless communication system
KR20170106988A|2017-09-22|Paging transmission method and apparatus for the same in a wireless communication system
EP3512296B1|2021-02-24|Methods and device for modifying a radio bearer in cu-du split scenario
US20190349803A1|2019-11-14|Method and apparatus for establishing drb
US11057804B2|2021-07-06|Method and device for adjusting random access backoff parameter
KR20180078233A|2018-07-09|A method for establishing a bearer for transmitting and receiving data in a wireless communication system and a device supporting the same
US20200146040A1|2020-05-07|Method and apparatus for selecting carrier
同族专利:
公开号 | 公开日
US20190394808A1|2019-12-26|
EP3560234A1|2019-10-30|
US20200068442A1|2020-02-27|
WO2019022530A1|2019-01-31|
CN110291810A|2019-09-27|
US20190335363A1|2019-10-31|
JP2020522962A|2020-07-30|
US10764787B2|2020-09-01|
JP6846545B2|2021-03-24|
US11026123B2|2021-06-01|
EP3560234A4|2019-12-11|
US10772012B2|2020-09-08|
US10397833B2|2019-08-27|
US20190037447A1|2019-01-31|
引用文献:
公开号 | 申请日 | 公开日 | 申请人 | 专利标题

EP1873935A4|2005-03-29|2015-02-25|Ntt Docomo Inc|Transmission power control method and mobile station|
US8130667B2|2008-09-19|2012-03-06|Texas Instruments Incorporated|Preamble group selection in random access of wireless networks|
CN102714800A|2010-01-12|2012-10-03|住友电气工业株式会社|Base station device|
EP2809092B1|2012-01-27|2018-05-23|Kyocera Corporation|Communication control method and user terminal|
WO2015046944A1|2013-09-26|2015-04-02|엘지전자 주식회사|Method for d2d communication performed by terminals in wireless communication system, and devices for supporting same|
KR102247142B1|2014-05-09|2021-05-04|삼성전자주식회사|Method and apparatus for transmitting synchronization signals in device-to-device communication|
BR112017006044A2|2014-10-23|2017-12-12|Intel Ip Corp|connection control for machine type communication devices|
TWI622311B|2016-06-28|2018-04-21|宏達國際電子股份有限公司|Device and method of handling uplink transmission|
KR20190125499A|2017-03-22|2019-11-06|엘지전자 주식회사|Method for performing random access procedure and apparatus therefor|
EP3636031B1|2017-05-17|2021-01-20|Telefonaktiebolaget LM Ericsson |Partitioning of random access preambles|
US10397833B2|2017-07-27|2019-08-27|Lg Electronics Inc.|Method and apparatus for performing EDT|US20180324869A1|2017-05-04|2018-11-08|Qualcomm Incorporated|Uplink early data transmission|
US10397833B2|2017-07-27|2019-08-27|Lg Electronics Inc.|Method and apparatus for performing EDT|
WO2019031427A1|2017-08-10|2019-02-14|京セラ株式会社|Communication control method|
US10798775B2|2017-08-10|2020-10-06|Qualcomm Incorporated|Techniques and apparatuses for duplication bearer management|
WO2019035624A1|2017-08-12|2019-02-21|주식회사 윌러스표준기술연구소|Method, device, and system for channel access in unlicensed band|
US10779333B2|2017-09-28|2020-09-15|Apple Inc.|Early data transmission in wireless communication system|
US10849164B2|2017-09-29|2020-11-24|Mediatek Inc.|High reliability and early data transmission|
US11039477B2|2017-11-17|2021-06-15|Mediatek Inc.|NB-IoT PRACH resource partitioning and multiple grants in RAR for EDT|
US11102764B2|2018-02-07|2021-08-24|Apple Inc.|Minimization of padding and resource wastage in message 3for early data transmission |
WO2019157752A1|2018-02-14|2019-08-22|华为技术有限公司|Random access method and device|
US20190208411A1|2018-03-16|2019-07-04|Intel Corporation|Security framework for msg3 and msg4 in early data transmission|
US11044775B2|2018-08-03|2021-06-22|Qualcomm Incorporated|Data path selection post connection re-establishment|
WO2020032860A1|2018-08-09|2020-02-13|Telefonaktiebolaget Lm Ericsson |Channel quality reporting in lte-m|
EP3857753A1|2018-09-25|2021-08-04|Hughes Network Systems, LLC|Efficient transport of internet of thingstraffic in terrestrial wireless and satellite networks|
CN111132332A|2018-10-31|2020-05-08|华硕电脑股份有限公司|Method and apparatus for transmitting using preconfigured uplink resources|
WO2020155112A1|2019-02-01|2020-08-06|华为技术有限公司|Resource management method and device|
US11166294B2|2019-02-08|2021-11-02|Qualcomm Incorporated|Scheduling in repetitive RF environments|
EP3952373A4|2019-03-28|2022-03-16|Huawei Tech Co Ltd|Data transmission method and device|
CN113396605A|2019-06-27|2021-09-14|Oppo广东移动通信有限公司|Data transmission method and device and terminal|
CN111800888A|2019-08-13|2020-10-20|维沃移动通信有限公司|SDT processing method, device and system|
CN113632530A|2019-08-22|2021-11-09|Oppo广东移动通信有限公司|Information processing method and terminal equipment|
CN111083218A|2019-12-12|2020-04-28|天翼物联科技有限公司|Internet of things anomaly reporting method, detection method, terminal, platform and storage medium|
WO2021149965A1|2020-01-22|2021-07-29|Lg Electronics Inc.|Method and apparatus for performing random access procedure with data transmission in wireless communication system|
GB2593537A|2020-03-27|2021-09-29|Nec Corp|Communication system|
WO2021207467A1|2020-04-08|2021-10-14|Idac Holdings, Inc.|Methods and apparatus for downlink small data reception|
WO2021226793A1|2020-05-11|2021-11-18|Qualcomm Incorporated|Low-latency transmit for rolling comments|
WO2021228676A1|2020-05-12|2021-11-18|Nokia Technologies Oy|Selection mechanism and use of multiple ul transmission schemes|
WO2022006915A1|2020-07-10|2022-01-13|Oppo广东移动通信有限公司|Uplink data transmission method and apparatus, terminal, and storage medium|
法律状态:
2021-10-19| B350| Update of information on the portal [chapter 15.35 patent gazette]|
优先权:
申请号 | 申请日 | 专利标题
US201762537456P| true| 2017-07-27|2017-07-27|
US201762537457P| true| 2017-07-27|2017-07-27|
PCT/KR2018/008460|WO2019022530A1|2017-07-27|2018-07-26|Method and apparatus for performing edt|
[返回顶部]