Method and apparatus for supporting light connection in next generation mobile communication systems

[0001] This application claims priority under 35 U.S.C. § 119(a) to Korean Patent Application Serial No. 10-2017-0000623, which was filed in the Korean Intellectual Property Office on Jan. 3, 2017, the entire content of which is hereby incorporated herein by reference.

[0002] The present disclosure relates generally to a method and an apparatus for supporting a multiple access in next generation mobile communication systems, and more particularly, to a method and apparatus for supporting light connection in next generation mobile communication systems.

[0003] The 5G communication system or the pre-5G communication system is called a beyond 4G network communication system or a post LTE system. To achieve a high data transmission rate, the 5G communication system is considered to be implemented in a very high frequency (mmWave) band (e.g., like 60 GHz band).

[0004] To relieve a path loss of a radio wave and increase a transfer distance of the radio wave in the very high frequency band, in the 5G communication system, beamforming, massive multiple-input and multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, analog beam-forming, and large scale antenna technologies have been used. To improve a network of the system, in the 5G communication system, technologies such as an evolved small cell, an advanced small cell, a cloud radio access network (cloud RAN), an ultra-dense network, a device to device communication (D2D), a wireless backhaul, a moving network, cooperative communication, coordinated multi-points (CoMP), and reception interference cancellation have been developed.

[0005] In addition, in the 5G system, hybrid frequency-shift keying (FSK) and quadrature amplitude modulation (QAM) modulation (FQAM) and sliding window superposition coding (SWSC) that are an advanced coding modulation (ACM) scheme and a filter bank multi carrier (FBMC), a nonorthogonal multiple access (NOMA), and a sparse code multiple access (SCMA) that are an advanced access technology, and so on have been developed.

[0006] The Internet has evolved from a human-centered connection network through which a human being generates and consumes information to the Internet of things (IoT) network that transmits/receives information between distributed components such as things and processes the information. The Internet of everything (IoE) technology in which big data processing technology is combined with the IoT technology by connection with a cloud server has also emerged. To implement the IoT, technology elements, such as a sensing technology, wired and wireless communication and network infrastructure, a service interface technology, and a security technology, have been used. Recently, technologies such as a sensor network, machine to machine (M2M), and machine type communication (MTC) for connecting between things have been used. In the IoT environment, an intelligent Internet technology (IT) service that creates a new value in human life by collecting and analyzing data generated in the connected things may be provided. The IoT may apply for fields, such as a smart home, a smart building, a smart city, a smart car or a connected car, a smart grid, health care, smart appliances, and an advanced healthcare service, by fusing and combining the existing information technology with various industries.

[0007] Therefore, 5G communication systems has been applied to the IoT network. The 5G communication technologies, such as the sensor network, the M2M, and the MTC, have been used by techniques such as the beamforming, the MIMO, and the array antenna. The application of the cloud RAN as the big data processing technology described above may also be used for combining the 5G communication technology with the IoT technology.

[0008] In the next generation mobile communication systems, when a terminal using a light connection releases a connection with a network and tries to reconnect with the network after a predetermined time, there is a need to identify a base station (or cell) that supports the light connection and a base station (or cell) that does not support the light connection. When the light connection to the base station (or cell) that does not support the light connection is resumed, a normal connection cannot be established.

[0009] In the next generation mobile communication systems, if only one sequence number (SN) is used, it is possible to reduce overhead upon supporting a single connection. However, it is impossible to support a multiple access with one SN. Therefore, a new mechanism needs to be added. Accordingly, an aspect of the present disclosure provides a gap encoding method, and a radio link control (RLC) status reporting method that supports a loss of a large number of packets.

[0010] In the next generation mobile communication systems, when the expiration date of the data packet expires, processing the expired packet is an important issue. The expired packet may already be a packet data convergence protocol (PDCP) protocol data unit (PDU), or may be an RLC PDU or a media access control (MAC) PDU. That is, functions of each layer may be affected depending on how to process the expired packet. Accordingly, an aspect of the present disclosure provides different processing methods depending on an extent that the expired packet is processed.

[0011] Accordingly, an aspect of the present disclosure provides a method for enabling a terminal to identify whether or not to support a light connection and establish a connection by broadcasting system information as to whether each base station supports a light connection in next generation mobile communication systems.

[0012] In the current LTE system, when a terminal performs a handover (HO), the terminal performs synchronization based on a random access procedure to a target cell, and receives an uplink grant to complete a handover procedure. If a handover without a random access procedure is introduced to reduce the influence of time interference in the handover procedure, there is no way to inform the successful completion of the handover procedure. Accordingly, an aspect of the present disclosure provides a method for determining successful completion of a handover with a target cell when a terminal performs handover without a random access.

[0013] When an LTE terminal supporting vehicle to everything (V2X) has a limited RF chain, there is a problem as to which link should be selected if an uplink transmission link to a base station and a side link transmission between the V2X terminals are generated at the same time. Accordingly, an aspect of the present disclosure provides a clear priority and operation principle of an uplink transmission link to a base station for an LTE terminal supporting V2X and a side link transmission between V2X terminals.

[0014] In accordance with an aspect of the present disclosure, there is provide a method by a terminal in a wireless communication system. The method includes receiving, from a source base station, a message indicating a handover without random access from the source base station to a target base station, receiving, on a downlink control channel from the target base station, an uplink grant for the handover, and transmitting, to the target base station, a message indicating a completion of the handover based on the uplink grant.

[0015] In accordance with an aspect of the present disclosure, there is provide a method by a target base station in a wireless communication system. The method includes receiving, from a source base station, a message to request a handover without random access for a terminal, transmitting, on a downlink control channel to the terminal, an uplink grant for the handover without random access, and receiving, from the terminal, a message indicating a completion of the handover without random access based on the uplink grant.

[0016] In accordance with an aspect of the present disclosure, there is provided a terminal in a wireless communication system. The terminal includes transceiver and a controller coupled with the transceiver and configured to control the transceiver to: receive, from a source base station, a message indicating a handover without random access from the source base station to a target base station, receive, on a downlink control channel from the target base station, an uplink grant for the handover, and transmit, to the target base station, a message indicating a completion of the handover based on the uplink grant.

[0017] In accordance with an aspect of the present disclosure, there is provided a target base station in a wireless communication system. The target base station includes a transceiver and a controller coupled with the transceiver and configured to control the transceiver to: receive, from a source base station, a message to request a handover without random access for a terminal, transmit, on a downlink control channel to the terminal, an uplink grant for the handover, and receive, from the terminal, a message indicating a completion of the handover based on the uplink grant.

[0087] Embodiments of the present disclosure will be described herein below with reference to the accompanying drawings. However, the embodiments of the present disclosure are not limited to the specific embodiments and should be construed as including all modifications, changes, equivalent devices and methods, and/or alternative embodiments of the present disclosure. In the description of the drawings, similar reference numerals are used for similar elements.

[0088] The terms “have,” “may have,” “include,” and “may include” as used herein indicate the presence of corresponding features (for example, elements such as numerical values, functions, operations, or parts), and do not preclude the presence of additional features.

[0089] The terms “A or B,” “at least one of A or/and B,” or “one or more of A or/and B” as used herein include all possible combinations of items enumerated with them. For example, “A or B,” “at least one of A and B,” or “at least one of A or B” means (1) including at least one A, (2) including at least one B, or (3) including both at least one A and at least one B.

[0090] The terms such as “first” and “second” as used herein may modify various elements regardless of an order and/or importance of the corresponding elements, and do not limit the corresponding elements. These terms may be used for the purpose of distinguishing one element from another element. For example, a first user device and a second user device may indicate different user devices regardless of the order or importance. For example, a first element may be referred to as a second element without departing from the scope the present invention, and similarly, a second element may be referred to as a first element.

[0091] It will be understood that, when an element (for example, a first element) is “(operatively or communicatively) coupled with/to” or “connected to” another element (for example, a second element), the element may be directly coupled with/to another element, and there may be an intervening element (for example, a third element) between the element and another element. To the contrary, it will be understood that, when an element (for example, a first element) is “directly coupled with/to” or “directly connected to” another element (for example, a second element), there is no intervening element (for example, a third element) between the element and another element.

[0092] The expression “configured to (or set to)” as used herein may be used interchangeably with “suitable for,” “having the capacity to,” “designed to,” “adapted to,” “made to,” or “capable of” according to a context. The term “configured to (set to)” does not necessarily mean “specifically designed to” in a hardware level. Instead, the expression “apparatus configured to . . . ” may mean that the apparatus is “capable of . . . ” along with other devices or parts in a certain context. For example, “a processor configured to (set to) perform A, B, and C” may mean a dedicated processor (e.g., an embedded processor) for performing a corresponding operation, or a generic-purpose processor (e.g., a central processing unit (CPU) or an application processor (AP)) capable of performing a corresponding operation by executing one or more software programs stored in a memory device.

[0093] The terms used in describing the various embodiments of the present disclosure are for the purpose of describing particular embodiments and are not intended to limit the present disclosure. As used herein, the singular forms are intended to include the plural forms as well, unless the context clearly indicates otherwise. All of the terms used herein including technical or scientific terms have the same meanings as those generally understood by an ordinary skilled person in the related art unless they are defined otherwise. The terms defined in a generally used dictionary should be interpreted as having the same or similar meanings as the contextual meanings of the relevant technology and should not be interpreted as having ideal or exaggerated meanings unless they are clearly defined herein. According to circumstances, even the terms defined in this disclosure should not be interpreted as excluding the embodiments of the present disclosure.

[0094] The term “module” as used herein may, for example, mean a unit including one of hardware, software, and firmware or a combination of two or more of them. The “module” may be interchangeably used with, for example, the term “unit”, “logic”, “logical block”, “component”, or “circuit”. The “module” may be a minimum unit of an integrated component element or a part thereof. The “module” may be a minimum unit for performing one or more functions or a part thereof. The “module” may be mechanically or electronically implemented. For example, the “module” according to the present invention may include at least one of an application-specific integrated circuit (ASIC) chip, a field-programmable gate arrays (FPGA), and a programmable-logic device for performing operations which has been known or are to be developed hereinafter.

[0095] An electronic device according to the present disclosure may include at least one of, for example, a smart phone, a tablet personal computer (PC), a mobile phone, a video phone, an electronic book reader (e-book reader), a desktop PC, a laptop PC, a netbook computer, a workstation, a server, a personal digital assistant (PDA), a portable multimedia player (PMP), a MPEG-1 audio layer-3 (MP3) player, a mobile medical device, a camera, and a wearable device. The wearable device may include at least one of an accessory type (e.g., a watch, a ring, a bracelet, an anklet, a necklace, a glasses, a contact lens, or a head-mounted device (HMD)), a fabric or clothing integrated type (e.g., an electronic clothing), a body-mounted type (e.g., a skin pad, or tattoo), and a bio-implantable type (e.g., an implantable circuit).

[0096] The electronic device may be a home appliance. The home appliance may include at least one of, for example, a television, a digital video disk (DVD) player, an audio, a refrigerator, an air conditioner, a vacuum cleaner, an oven, a microwave oven, a washing machine, an air cleaner, a set-top box, a home automation control panel, a security control panel, a TV box (e.g., Samsung HomeSync™, Apple TV™, or Google TV™), a game console (e.g., Xbox™ and PlayStation™), an electronic dictionary, an electronic key, a camcorder, and an electronic photo frame.

[0097] The electronic device may include at least one of various medical devices (e.g., various portable medical measuring devices (a blood glucose monitoring device, a heart rate monitoring device, a blood pressure measuring device, a body temperature measuring device, etc.), a magnetic resonance angiography (MRA), a magnetic resonance imaging (MRI), a computed tomography (CT) machine, and an ultrasonic machine), a navigation device, a global positioning system (GPS) receiver, an event data recorder (EDR), a flight data recorder (FDR), a vehicle infotainment device, an electronic device for a ship (e.g., a navigation device for a ship, and a gyro-compass), avionics, security devices, an automotive head unit, a robot for home or industry, an automatic teller machine (A™) in banks, point of sales (POS) devices in a shop, or an IoT device (e.g., a light bulb, various sensors, electric or gas meter, a sprinkler device, a fire alarm, a thermostat, a streetlamp, a toaster, a sporting goods, a hot water tank, a heater, a boiler, etc.).

[0098] The electronic device may include at least one of a part of furniture or a building/structure, an electronic board, an electronic signature receiving device, a projector, and various kinds of measuring instruments (e.g., a water meter, an electric meter, a gas meter, and a radio wave meter). The electronic device may be a combination of one or more of the aforementioned various devices. The electronic device may also be a flexible device. Further, the electronic device is not limited to the aforementioned devices, and may include an electronic device according to the development of new technology.

[0099] Hereinafter, an electronic device according to various embodiments will be described with reference to the accompanying drawings. In the present disclosure, the term “user” may indicate a person using an electronic device or a device (e.g., an artificial intelligence electronic device) using an electronic device.

[0100] The present disclosure discloses a method of a terminal including identifying missed RLC PDUs based on a SN of a plurality of RLC PDUs received from a base station; generating a message including a first field indicating the number of missed RLC PDUs and a second field indicating whether there is the first field; and transmitting a message from the base station.

[0101] The present disclosure discloses a method of a base station including transmitting a plurality of RLC PDUs to a terminal; and receiving, from the terminal, a message including a first field indicating the number of missed RLC PDUs among the plurality of RLC PDUs and a second field indicating whether there is the first field.

[0102] The present disclosure discloses a terminal including a transceiver configured to transmit/receive a signal; and a controller configured to identify missed RLC PDUs based on a SN of a plurality of RLC PDUs received from a base station, generate a message including a first field indicating the number of missed RLC PDUs and a second field indicating whether there is the first field, and transmit the message to the base station.

[0103] The present disclosure discloses a base station including a transceiver configured to transmit/receive a signal; and a controller configured to transmit a plurality of RLC PDUs to a terminal and receive, from a terminal, a message including a first field indicating the number of missed RLC PDUs among the plurality of RLC PDUs and a second field indicating whether there is the first field.

[0104] The present disclosure discloses a method of a terminal including receiving a PDCP service data unit (SDU) in PDCP entity; generating a PDCP PDU including a PDCP header for the PDCP SDU if a timer corresponding to the PDCP SDU expires; and transmitting the PDCP PDU to a base station.

[0105] The present disclosure discloses a method of a base station including receiving a PDCP PDU from a terminal; identifying whether the PDCP PDU includes only a PDCP header; and performing decoding on the PDCP PDU based on whether the PDCP PDU includes only the PDCP header, wherein if the PDCP PDU includes only the PDCP header, the decoding on the PDCP PDU may be omitted.

[0106] The present disclosure discloses a terminal including a transceiver configured to transmit/receive a signal; and a controller configured to receive a PDCP SDU in PDCP entity, generate a PDCP PDU including a PDCP header for the PDCP SDU if a timer corresponding to the PDCP SDU expires, and transmit the PDCP PDU to a base station.

[0107] The present disclosure discloses a method of a base station including a transceiver configured to transmit/receive a signal and a controller configured to receive a PDCP PDU from a terminal, identify whether the PDCP PDU includes only a PDCP header, and perform decoding on the PDCP PDU based on whether the PDCP PDU includes only the PDCP header, wherein if the PDCP PDU includes only the PDCP header, the decoding on the PDCP PDU may be omitted.

[0108] The present disclosure discloses a method of a terminal including receiving, from a base station, information indicating whether the base station supports a radio resource control (RRC) inactive mode; and transmitting a message requesting a PAU to the base station when the base station supports the RRC inactive mode.

[0109] The present disclosure discloses a method of a base station including transmitting information indicating whether the base station supports an RRC inactive mode to a terminal which is an RRC connected mode; and receiving a message requesting a paging area update from the terminal when the base station supports the RRC inactive mode.

[0110] The present disclosure discloses a terminal including a transceiver configured to transmit/receive a signal; and a controller configured to receive, from a base station, information indicating whether the base station supports an RRC inactive mode and transmit a message requesting a paging area update to the base station if the base station supports the RRC inactive mode.

[0111] The present disclosure discloses a base station including a transceiver configured to transmit/receive a signal; and a controller configured to receive, from a base station, information indicating whether the base station supports an RRC inactive mode to a terminal which is an RRC connected mode, and receive a message requesting a paging area update from a terminal if the base station supports the RRC inactive mode.

[0112] The present disclosure discloses a method of a terminal including receiving, from a source base station, a message indicating a handover without random access from the source base station to a target base station; receiving, on a downlink control channel from the target base station, an uplink grant for the handover without random access; and transmitting, to the target base station, a message indicating a completion of the handover without random access based on the uplink grant.

[0113] The present disclosure discloses a method of a base station including receiving, from a source base station, a message to request a handover without random access for a terminal; transmitting, on a downlink control channel to the terminal, an uplink grant for the handover without random access; and receiving, from the terminal, a message indicating a completion of the handover without random access based on the uplink grant.

[0114] The present disclosure discloses a terminal including a transceiver configured to transmit and receive signals; and a controller coupled with the transceiver and configured to control the transceiver to receive, from a source base station, a message indicating a handover without random access from the source base station to a target base station, receive, on a downlink control channel from the target base station, an uplink grant for the handover without random access, and transmit, to the target base station, a message indicating a completion of the handover without random access based on the uplink grant.

[0115] The present disclosure discloses a base station including a transceiver configured to transmit and receive signals; and a controller coupled with the transceiver and configured to control the transceiver to receive, from a source base station, a message to request a handover without random access for a terminal, transmit, on a downlink control channel to the terminal, an uplink grant for the handover without random access, and receive, from the terminal, a message indicating a completion of the handover without random access based on the uplink grant.

[0116] The present disclosure discloses a method of a terminal including identifying a generation of an uplink data to be transmitted to a base station and a generation of a side link data to be transmitted to an opponent terminal of device to device (D2D) communication; determining that the uplink data or the side link data are transmitted if the transmission of the uplink data and the transmission of the side link data overlap with each other; and transmitting determined data among the side link data.

[0117] The present disclosure discloses a terminal including a transceiver configured to transmit/receive a signal; a controller configured to identify a generation of an uplink data to be transmitted to a base station and a generation of a side link data to be transmitted to an opponent terminal of D2D communication; determine that the uplink data or the side link data are transmitted if the transmission of the uplink data and the transmission of the side link data overlap with each other; and transmit determined data among the side link data.

[0118] According to an aspect of the present disclosure, the overhead can be reduced by proposing the gap encoding method supporting multiple accesses with one SN, and when a large number of packets are lost, the new RLC status report method can be applied to reduce the overhead.

[0119] According to an aspect of the present disclosure, there is an effect of preventing a problem from occurring in each layer by proposing different processing methods depending on to what extent the expired packet is processed when the expired packet is processed.

[0120] According to an aspect of the present disclosure, the terminal to which the light connection is applied confirms whether the light connection is supported by the base station (or cell) which can be currently connected to system information and tries to establish the connection.

[0121] According to an aspect of the present disclosure, the method for determining a completion of successful handover with a target cell is defined when the terminal performs handover without the random access, thereby completing the handover without affecting the time interference in the handover procedure.

[0122] According to an aspect of the present disclosure, there is an effect of clarifying how to operate when the transmission of different links is generated at the same time by proposing the clear prioritization and operation principle of the uplink and downlink transmission link to the base station for the LTE terminal supporting the V2X and the side link between the V2X terminals.

[0123] Hereinafter, for convenience of explanation, the present disclosure uses terms and names defined in the 3rd generation partnership project long term evolution (3GPP LTE). However, the present disclosure is not limited to these terms and names but may also be identically applied to the system according to other standards.

[0124] FIG. 1A is a diagram of an LTE system, according to an embodiment of the present disclosure.

[0125] As illustrated in FIG. 1A, a RAN of an LTE system is configured to include next generation base stations (evolved node B, hereinafter, ENB, Node B, or base station) 1a-05, 1a-10, 1a-15, and 1a-20, an MME 1a-25, and an S-GW 1a-30. User equipment (hereinafter, UE or terminal) 1a-35 accesses an external network through the ENBs 1a-05 to 1a-20 and the S-GW 1a-30.

[0126] In FIG. 1A, the ENBs 1a-05 to 1a-20 correspond to an existing node B of the universal mobile telecommunications system (UMTS). The ENB is connected to the UE 1a-35 through a radio channel and performs a more complicated role than an existing node B. In the LTE system, in addition to a real-time service like a voice over internet protocol (VoIP) through the Internet protocol, all the user traffics are served through a shared channel, and therefore an apparatus for collecting and scheduling status information such as a buffer status, an available transmission power status, and a channel state of the terminals is required. Here, the ENBs 1a-05 to 1a-20 control collecting and scheduling status information. One ENB generally controls a plurality of cells. For example, to implement a transmission rate of 100 Mbps, the LTE system uses, as a radio access technology (RAT), orthogonal frequency division multiplexing (OFDM) in, for example, a bandwidth of 20 MHz. Further, an adaptive modulation & coding (AMC) scheme for determining a modulation scheme and a channel coding rate depending on a channel status of the terminal is applied. The S-GW 1a-30 is an apparatus for providing a data bearer and generates or removes the data bearer according to the control of the MME 1a-25. The MME is an apparatus for performing a mobility management function for the terminal and various control functions and is connected to a plurality of base stations.

[0127] FIG. 1B is a diagram of a radio protocol structure in the LTE system.

[0128] Referring to FIG. 1B, the radio protocol of the LTE system is configured to include PDCPs 1b-05 and 1b-40, RLCs 1b-10 and 1b-35, and MACs 1b-15 and 1b-30 in the terminal and the ENB. The PDCPs 1b-05 and 1b-40 control operations such as internet provider (IP) header compression/decompression. The main functions of the PDCP are summarized as follows.

[0129] Header compression and decompression function (Header compression and decompression: robust header compression (ROHC) only)

[0130] Transfer of user data

[0131] In-sequence delivery function (In-sequence delivery of upper layer PDUs at PDCP re-establishment procedure for RLC acknowledgement mode (AM))

[0132] Reordering function (For split bearers in dual connectivity (DC) (only support for RLC AM): PDCP PDU routing for transmission and PDCP PDU reordering for reception)

[0133] Duplicate detection function (Duplicate detection of lower layer service data unit (SDU)s at PDCP re-establishment procedure for RLC AM)

[0134] Retransmission function (Retransmission of PDCP SDUs at handover (HO) and, for split bearers in DC, of PDCP PDUs at PDCP data-recovery procedure, for RLC AM)

[0135] Ciphering and deciphering function (Ciphering and deciphering)

[0136] Timer-based SDU discard function (Timer-based SDU discard in uplink)

[0137] The RLCs 1b-10 and 1b-35 reconfigures the PDCP PDU to an appropriate size to perform the automatic repeat request (ARQ) operation or the like. The main functions of the RLC are summarized as follows.

[0138] Data transfer function (Transfer of upper layer PDUs)

[0139] ARQ function (Error Correction through ARQ (only for AM data transfer))

[0140] Concatenation, segmentation, reassembly functions (Concatenation, segmentation and reassembly of RLC SDUs (only for unacknowledged mode (UM) and AM data transfer))

[0141] Re-segmentation function (Re-segmentation of RLC data PDUs (only for AM data transfer))

[0142] Reordering function (Reordering of RLC data PDUs (only for UM and AM data transfer))

[0143] Duplicate detection function (Duplicate detection (only for UM and AM data transfer))

[0144] Error detection function (Protocol error detection (only for AM data transfer))

[0145] RLC SDU discard function (RLC SDU discard (only for UM and AM data transfer))

[0146] RLC re-establishment function (RLC re-establishment)

[0147] The MACs 1b-15 and 1b-30 are connected to several RLC layer apparatuses configured in one terminal and perform an operation of multiplexing RLC PDUs into an MAC PDU and demultiplexing the RLC PDUs from the MAC PDU. The main functions of the MAC are summarized as follows.

[0148] Mapping function (Mapping between logical channels and transport channels)

[0149] Multiplexing/demultiplexing function (Multiplexing/demultiplexing of MAC SDUs belonging to one or different logical channels into/from transport blocks (TB) delivered to/from the physical layer on transport channels)

[0150] Scheduling information reporting function (Scheduling information reporting)

[0151] Hybrid automatic repeat request (HARQ) function (Error correction through HARQ)

[0152] Priority handling function between logical channels (Priority handling between logical channels of one UE)

[0153] Priority handling function between terminals (Priority handling between UEs by dynamic scheduling)

[0154] Multimedia broadcast multicast service (MBMS) identification function (MBMS identification)

[0155] Transport format selection function (Transport format selection)

[0156] Padding function (Padding)

[0157] Physical layers 1b-20 and 1b-25 perform channel-coding and modulating higher layer data, making the higher layer data as an OFDM symbol and transmitting them to a radio channel, or demodulating and channel-decoding the OFDM symbol received through the radio channel and transmitting the demodulated and channel-decoded OFDM symbol to the higher layer.

[0158] FIG. 1C is a diagram of a next generation mobile communication system, according to an embodiment of the present disclosure.

[0159] Referring to FIG. 1C, a RAN of a next generation mobile communication system (hereinafter referred to as new radio (NR) or 5G) is configured to include a next generation base station (NR node B, hereinafter NR gNB or NR base station) 1c-10 and a NR core network (NR CN) 1c-05. The user terminal (NR UE or UE) 1c-15 accesses the external network through the NR gNB 1c-10 and the NR CN 1c-05.

[0160] In FIG. 1C, the NR gNB 1c-10 corresponds to an eNB of the existing LTE system. The NR gNB is connected to the NR UE 1c-15 via a radio channel and may provide a service superior to the existing node B. In the next generation mobile communication system, since all user traffics are served through a shared channel, an apparatus for collecting state information such as a buffer state, an available transmission power state, and a channel state of the UEs to perform scheduling is required. The NR NB 1c-10 may serve as the device. One NR gNB generally controls a plurality of cells. In order to realize high-speed data transmission compared with the current LTE, the NR gNB may have an existing maximum bandwidth, and may be additionally incorporated into a beam-forming technology and may be applied by using OFDM as a radio access technology. Further, an AMC scheme determining a modulation scheme and a channel coding rate depending on a channel status of the terminal is applied. The NR CN 1c-05 may perform functions such as mobility support, bearer setup, quality of service (QoS) setup, and the like. The NR CN 1c-05 is a device for performing a mobility management function for the terminal and various control functions and is connected to a plurality of base stations. In addition, the next generation mobile communication system can interwork with the existing LTE system, and the NR CN 1c-05 is connected to the MME 1c-25 through the network interface. The MME is connected to the eNB 1c-30 which is the existing base station.

[0161] FIG. 1D is a diagram of a radio protocol structure of a next generation mobile communication system, according to an embodiment of the present disclosure.

[0162] Referring to FIG. 1D, the radio protocol of the next generation mobile communication system is configured to include NR PDCPs 1d-05 and 1d-40, NR RLCs 1d-10 and 1d-35, and NR MACs 1d-15 and 1d-30 in the terminal and the NR base station. The main functions of the NR PDCPs 1d-05 and 1d-40 may include some of the following functions.

[0163] Header compression and decompression function (Header compression and decompression: ROHC only)

[0164] Transfer of user data

[0165] In-sequence delivery function (In-sequence delivery of upper layer PDUs)

[0166] Reordering function (PDCP PDU reordering for reception)

[0167] Duplicate detection function (Duplicate detection of lower layer SDUs)

[0168] Retransmission function (Retransmission of PDCP SDUs)

[0169] Ciphering and deciphering function (Ciphering and deciphering)

[0170] Timer-based SDU discard function (Timer-based SDU discard in uplink)

[0171] The reordering function of the NR PDCP apparatus is for rearranging PDCP PDUs received in a lower layer in order based on a PDCP SN and may include a function of transferring data to a higher layer in the rearranged order, a function of recording PDCP PDUs lost by the reordering, a function of reporting a state of the lost PDCP PDUs to a transmitting side, and a function of requesting a retransmission of the lost PDCP PDUs.

[0172] The main functions of the NR RLCs 1d-10 and 1d-35 may include some of the following functions.

[0173] Data transfer function (Transfer of upper layer PDUs)

[0174] In-sequence delivery function (In-sequence delivery of upper layer PDUs)

[0175] Out-of-sequence delivery function (Out-of-sequence delivery of upper layer PDUs)

[0176] ARQ function (Error correction through HARQ)

[0177] Concatenation, segmentation, reassembly function (Concatenation, segmentation and reassembly of RLC SDUs)

[0178] Re-segmentation function (Re-segmentation of RLC data PDUs)

[0179] Reordering function (Reordering of RLC data PDUs)

[0180] Duplicate detection function (Duplicate detection)

[0181] Error detection function (Protocol error detection)

[0182] RLC SDU discard function (RLC SDU discard)

[0183] RLC re-establishment function (RLC re-establishment)

[0184] The in-sequence delivery function of the NR RLC apparatus is for delivering RLC SDUs received from a lower layer to a higher layer in order, and may include a function of reassembling and transferring an original one RLC SDU which is divided into a plurality of RLC SDUs and received, a function of rearranging the received RLC PDUs based on the RLC SN or the PDCP SN, a function of recording the RLC PDUs lost by the reordering, a function of reporting a state of the lost RLC PDUs to the transmitting side, a function of requesting a retransmission of the lost RLC PDUs, a function of transferring only the SLC SDUs before the lost RLC SDU to the higher layer in order when there is the lost RLC SDU, a function of transferring all the received RLC SDUs to the higher layer before a predetermined timer starts if the timer expires even if there is the lost RLC SDU, or a function of transferring all the RLC SDUs received to the higher layer in order if the predetermined timer expires even if there is the lost RLC SDU.

[0185] The out-of-sequence delivery function of the NR RLC apparatus is for directly delivering the RLC SDUs received from the lower layer to the higher layer regardless of order, and may include a function of reassembling and transferring an original RLC SDU which is divided into several RLC SDUs and received, and a function of storing the RLC SN or the PDCP SP of the received RLC PDUs and arranging it in order to record the lost RLC PDUs.

[0186] The NR MACs 1d-15 and 1d-30 may be connected to several NR RLC layer apparatuses configured in one terminal, and the main functions of the NR MAC may include some of the following functions.

[0187] Mapping function (Mapping between logical channels and transport channels)

[0188] Multiplexing and demultiplexing function (Multiplexing/demultiplexing of MAC SDUs)

[0189] Scheduling information reporting function (Scheduling information reporting)

[0190] HARQ function (Error correction through HARQ)

[0191] Priority handling function between logical channels (Priority handling between logical channels of one UE)

[0192] Priority handling function between terminals (Priority handling between UEs by dynamic scheduling)

[0193] MBMS service identification function (MBMS service identification)

[0194] Transport format selection function (Transport format selection)

[0195] Padding function (Padding)

[0196] The NR PHY layers 1d-20 and 1d-25 may perform channel-coding and modulating higher layer data, making the higher layer data as an OFDM symbol and transmitting them to a radio channel, or demodulating and channel-decoding the OFDM symbol received through the radio channel and transmitting the demodulated and channel-decoded OFDM symbol to the higher layer.

[0197] FIG. 1E is a diagram of setting, by a terminal, each layer apparatus (entity, hereinafter, apparatus) in the next generation mobile communication, according to an embodiment of the present disclosure.

[0198] FIG. 1E also describes a procedure of setting a connection with a network via which a terminal transmits/receives data and setting apparatuses (entity, hereinafter, apparatuses) of each layer.

[0199] If there is data to be transmitted, a terminal 1e-01 (hereinafter, referred to as an idle mode UE) for which no connection is currently established performs an RRC connection establishment procedure with the LTE base station or the NR base station 1e-02. The terminal 1e-01 establishes uplink transmission synchronization with the base station 1e-02 through a random access procedure and transmits an RRCConnectionRequest message to the base station 1e-02 (at step 1e-05). The message includes establishmentCause for connection with an identifier of the terminal 1e-01. The base station 1e-02 transmits an RRCConnectionSetup message to allow the terminal 1e-01 to set the RRC connection (at step 1e-10). The message may store RRC connection configuration information, setting information of each layer, and the like. In other words, it may include configuration information on the PHY or NR PHY apparatus, the MAC or NR MAC apparatus, the RLC or NR RLC apparatus, the PDCP or the NR PDCP apparatus, and the information instructing the setting for the specific functions among the functions described in FIG. 1B or 1D supported by the layer apparatuses. In addition, the message may include an indication of whether to allocate a PDCP SN in the PDCP apparatus or may include an indication of whether to allocate an RLC SN in the RLC apparatus. The RRC connection is also called a signaling radio bearer (SRB) and is used for transmission and reception of the RRC message that is a control message between the terminal 1e-01 and the base station 1e-02. The terminal establishing the RRC connection transmits an RRCConnetionSetupComplete message to the base station (at step 1e-15). The base station transmits an RRCConnectionReconfiguration message to the terminal in order to set up a data radio bearer (DRB) (at step 1e-20). The configuration information of each layer and the like may be stored in the message. In other words, it may include configuration information on the PHY or NR PHY apparatus, the MAC or NR MAC apparatus, the RLC or NR RLC apparatus, the PDCP or the NR PDCP apparatus, and the information instructing the setting for the specific functions among the functions described in FIG. 1B or 1D supported by the layer apparatuses. In addition, the message may include an indication of whether to allocate a PDCP SN in the PDCP apparatus or may include an indication of whether to allocate an RLC SN in the RLC apparatus. In addition, the message includes the configuration information of the DRB in which user data are processed, and the terminal applies the information to set the DRB and set the functions of each layer and transmits an RRCConnectionReconfigurationComplete message to the base station 1e-02 (at step 1e-25). If the above procedure is completed, the terminal 1e-01 transmits and receives data to and from the base station 1e-02 (at step 1e-30). While transmitting and receiving data, the base station 1e-02 may again transmit the RRCConnectionReconfiguration message to the terminal 1e-01 (at step 1e-35), if necessary, set the configuration information of each layer of the terminal 1e-01. In other words, it may include configuration information on the PHY or NR PHY apparatus, the MAC or NR MAC apparatus, the RLC or NR RLC apparatus, the PDCP or the NR PDCP apparatus, and the information instructing the setting for the specific functions among the functions described in FIG. 1B or 1D supported by the layer apparatuses. In addition, the message may include an indication of whether to allocate a PDCP SN in the PDCP apparatus or may include an indication of whether to allocate an RLC SN in the RLC apparatus. In addition, the message may include the information for setting the interworking between the LTE base station (or NR base station) and the NR base station. The information for setting the interworking between the LTE base station and the NR base station may include information indicating a 3C type or a 1A type, information on each layer apparatus according to each type, and the like. Upon completion of the setting of apparatuses of each layer according to the message, the terminal 1e-01 transmits an RRCConnectionReconfigurationComplete message to the base station 1e-02 (at step 1e-40).

[0200] FIGS. 1FA and 1FB are diagrams of a terminal that receives services through an LTE base station and an NR base station in the next generation mobile communication system, according to an embodiment of the present disclosure.

[0201] In FIGS. 1FA and 1FB, 1f-01 shows that the LTE base station is a master (MeNB) in the 3C type LTE base station-LTE base station interworking, 1f-02 shows that the LTE base station is a master (MeNB) in the 3C type LTE base station-NR base station interworking, 1f-03 shows that the NR base station is a master (MeNB) in the 3C type LTE base station-NR base station interworking, and 1f-04 shows that the NR base station is a master (MeNB) in the 3C type NR base station-NR base station interworking, 1f-05 shows a 1A type LTE base station-NR base station interworking, 1f-06 shows a 1A type NR base station-NR base station interworking, and 1F-07 shows the NR base station.

[0202] The LTE system allocates a PDCP SN in the PDCP apparatus, and allocates an RLC SN in the RLC apparatus. However, in the next generation mobile communication systems, a PDCP SN may be allocated only in the NR PDCP device, and an RLC SN may not be allocated and a PDCP SN may be used in the NR RLC apparatus. Therefore, the overhead may be reduced by deleting the RLC SN. When a terminal accesses only one cell or a base station, the terminal can operate with a single SN without any problem. However, a problem may arise in the multiple access scenario described above with reference to FIGS. 1FA and 1FB. The above-mentioned problems that may occur are described with respect to FIGS. 1GA and 1GB.

[0203] FIGS. 1GA and 1GB are diagrams when one SN is used in the multiple access environment, according to an embodiment of the present disclosure.

[0204] In FIGS. 1GA and 1GB, 1g-05 shows that the LTE base station is the master (MeNB) in the 3C type interworking between the LTE base station and the LTE base station and allocates the PDCP SN in the PDCP apparatus of the MeNB, and the RLC apparatuses of the MeNB and the RLC apparatuses of SeNB each allocate independent RLC SNs. Therefore, each RLC apparatus can normally perform an RLC ARQ operation based on the RLC SN together with the RLC apparatus of the receiving end.

[0205] In FIGS. 1GA and 1GB, 1g-10 shows that the LTE base station is the master (MeNB) in the 3C type interworking between the LTE base station and the NR base station, the PDCP SN is assigned in the MeNB PDCP apparatus of the MeNB, and since the RLC apparatus of the MeNB allocates the independent RLC SN and the NR RLC apparatus of the SeNB supports one SN, the RLC apparatus may reuse the PDCP SN without changing it. The RLC apparatus of the MeNB can normally perform an RLC ARQ operation based on the RLC SN together with the RLC apparatus of the receiving end. However, the NR RLC apparatus of the SeNB cannot normally perform the RLC ARQ operation together with the NR RLC apparatus of the receiving end. For example, if it is assumed that the NR RLC apparatus of the transmitting end transmits SNs 1, 2, and 4 to the receiving end and that the receiving end normally receives the SNs, the receiving end cannot know whether the SN 3 is lost during the transmission or whether the SN 3 is originally transmitted from another MeNB. Therefore, the NR RLC apparatus of the receiving end continuously waits for the SN 3. As a result, the transmission delay may occur and the window stalling problem may occur. Such a problem may occur in the NR RLC apparatus of the transmitting end in the scenarios 1f-02, 1f-03, and 1f-04 in FIGS. 1FA and 1FB.

[0206] FIG. 1H is a diagram in which multiple access is supported by one SN, according to an embodiment of the present disclosure in the present disclosure.

[0207] In FIG. 1H, 1h-01 shows that the LTE base station is the master (MeNB) in the 3C type LTE base station-NR base station interworking, the PDCP SN is allocated in the MeNB PDCP apparatus of the MeNB, and since the RLC apparatus of the MeNB allocates the independent RLC SN and the NR RLC apparatus of the SeNB supports one SN, the RLC apparatus may reuse the PDCP SN without changing it. Therefore the transmission delay and window stalling problem that is mentioned in FIGS. 1GA and 1GB may occur. In 1f-02, 1f-03, and 1f-04 in FIGS. 1FA and 1FB in which the same problem as described above, a method for inserting into an RLC header a SN that the NR RLC apparatus transmits as in 1h-05 may be used. That is, since the SN is the first RLC PDU of the corresponding NR RLC layer, the SN 1 indicating itself can be inserted into the RLC header (if the same SN is inserted, it may indicate the first RLC PDU). SN 2 that is transmitted subsequently may insert the SN 1 because it was the previous SN. SN 4 that is transmitted subsequently may insert the SN 2 because it was the previous SN. Therefore, if the NR RLC apparatus of the transmitting end transmits the SNs 1, 2, and 4 and the NR RLC apparatus successfully receives them, it can be confirmed that the previous SN is 2 in the header of the RLC PDU of the SN 4 and the SN 3 is transmitted in another MeNB. Therefore, the NR RLC apparatus of the transmitting end and the receiving end can normally perform the RLC ARQ operation. This operation can be equally applied to the NR RLC apparatus of the scenarios such as 1f-02, 1f-03, and 1f-04 in FIGS. 1FA and 1FB.

[0208] FIG. 1I is a diagram in which multiple access is supported by one SN, according to an embodiment of the present disclosure.

[0209] In FIG. 1I, 1i-01 shows that the LTE base station is the master (MeNB) in the 3C type interworking between the LTE base station and the NR base station, the PDCP SN is assigned in the MeNB PDCP apparatus of the MeNB, and since the RLC apparatus of the MeNB allocates the independent RLC SN and the NR RLC apparatus of the SeNB supports one SN, the RLC apparatus may reuse the PDCP SN without changing it. Therefore the transmission delay and window stalling problem that is mentioned in FIGS. 1GA and 1GB may occur. In the scenarios such as 1f-02, 1f-03, and 1f-04 in FIGS. 1FA and 1FB in which the same problem as described above may occur, a method for inserting into an RLC header a gap between the SN the NR RLC apparatus transmits just before 1i-05 and the currently transmitted SN can be used. Here, if the gap is 0, it indicates the first RLC PDU in the corresponding connection. That is, since the SN 1 is the first RLC PDU of the corresponding NR RLC layer, the gap 0 can be inserted into the RLC header. SN 2 that is transmitted subsequently may insert gap 1 because a gap (2−1=1) from the just previous SN is 1. SN 4 that is transmitted subsequently may insert the gap 2 which is a gap (4−2=2) from the just previous SN, because the just previous SN is 2. Therefore, if the NR RLC apparatus of the transmitting end transmits the SNs 1, 2, and 4 and the NR RLC apparatus successfully receives them, it can be confirmed that the gap from the previous SN is 2 in the header of the RLC PDU of the SN 4 and the SN 3 is transmitted in another MeNB. Therefore, the NR RLC apparatus of the transmitting end and the receiving end can normally perform the RLC ARQ operation. The above operations can be equally applied to the NR RLC apparatus of the scenarios such as 1f-02, 1f-03, and 1f-04 in FIGS. 1FA and 1FB. Instead of the method for inserting into the RLC header the gap between the SN that the NR RLC apparatus transmits just before and the currently transmitted SN t, a method for inserting into an MAC subheader a gap between a SN (or other indicators) that the NR MAC apparatus transmits just before and the currently transmitted SN (or other indicators) may be applied. In this case, other indicators may be an indicator indicating the order of the corresponding packet.

[0210] FIG. 1J is a diagram in which multiple access is supported by one SN, according to an embodiment of the present disclosure.

[0211] In FIG. 1J, 1j-01 shows that the LTE base station is the master (MeNB) in the 3C type interworking between the LTE base station and the NR base station, the PDCP SN is assigned in the MeNB PDCP apparatus of the MeNB, and since the RLC apparatus of the MeNB allocates the independent RLC SN and the NR RLC apparatus of the SeNB supports one SN, the RLC apparatus may reuse the PDCP SN without changing it. Therefore the transmission delay and window stalling problem that is mentioned in FIGS. 1GA and 1GB may occur. In the scenarios such as 1f-02, 1f-03, and 1f-04 in FIGS. 1FA and 1FB in which the same problem as described above may occur, a method for inserting into an RLC header a gap between the SN the NR RLC apparatus transmits just before like 1j-05 and the currently transmitted SN can be used. The method for coding and inserting a gap between SNs in the NR RLC apparatus is the same as that of FIG. 1I, and if a gap is 0, it indicates the first RLC PDU in the corresponding connection.

[0212] However, if the gap is encoded and put in the header of all RLC PDUs, the overhead may be increased. For example, if it is assumed that the PDCP SN has a length of 18 bits, the length of the gap needs to have 18 bits (since the PDCP SN is separated and transmitted as MeNB and SeNB, the gap may need to indicate the whole space of the PDCP sequence). Therefore, since an 18-bit gap is inserted in the RLC header of all RLC PDUs, the overhead can be increased. To reduce the overhead, a gap indicator (GI) field having a size of 1 bit in the RLC header is defined as in Table 1-1.

[0213]

	TABLE 1-1
	GI field	Description
	0	5 bits gap field
	1	12 bits gap
		field

[0214] The GI field value and information can be mapped to two different cases.

[0215] That is, if the GI field having a size of 1 bit is defined in the RLC header and thus the GI field value is 0, it may indicate that the gap is not inserted into the RLC header, and if the GI field value is 1, it may indicate that the gap is inserted into the RLC header. The case in which it is not necessary to insert the gap into the RLC header in the 1-2-2 embodiment corresponds to the case in which the RLC PDUs have a consecutive SN or do not correspond to a first segment among segments of one RLC PDU. For example, in the case of the SN 1 such as 1j-10, since it is the first RLC PDU of the corresponding connection, to indicate this, the GI field may be set to be 1 to indicate that there is a gap and insert a gap value as 0. In the case of the SN 2, there is no need to insert an interval value because it is a SN that is consecutive with the previous SN 1. Therefore, the GI field is set to be 0 and the overhead is reduced without inserting a gap value into the RLC header. In the case of the SN 4, there is no need to insert a gap value because it is not a SN that is consecutive with the previous SN 2. Therefore, the GI field is set to be 1 and the gap value 2 is inserted into the RLC header. In the case of the segments of one RLC PDU, in the case of the first segment, the gap value with the previous SN is inserted into the RLC header and the segment may not be inserted in other cases. If the first segment has the SN consecutive to the previous SN, the GI field is set to be 0 and thus the gap value may also be omitted.

[0216] Therefore, if the NR RLC apparatus of the transmitting end transmits the SNs 1, 2, and 4 and the NR RLC apparatus successfully receives them, since the GI field is set to be 1 in the RLC PDU of the SN 4, it can be confirmed that there is the gap value, and it can be confirmed that the gap from the previous SN is 2 and the SN 3 is transmitted from another MeNB. Therefore, the NR RLC apparatus of the transmitting end and the receiving end can normally perform the RLC ARQ operation. These operations can be equally applied to the NR RLC apparatus of the scenarios such as 1f-02, 1f-03, and 1f-04 in FIGS. 1FA and 1FB. Instead of the method for inserting into the RLC header the gap between the SN that the NR RLC apparatus transmits just before and the currently transmitted SN, a method for inserting into an MAC subheader a gap between a SN (or other indicators) that the NR MAC apparatus transmits just before and the currently transmitted SN (or other indicators) may be applied. In this case, other indicators may be an indicator indicating the order of the corresponding packet. In addition, the GI field is defined in the MAC subheader field and may be identical to and modified as described above to be applied to the MAC subheader.

[0217] FIG. 1K is a diagram in which multiple access is supported by one SN, according to an embodiment of the present disclosure.

[0218] In FIG. 1K, 1k-01 shows that the LTE base station is the master (MeNB) in the 3C type LTE base station-NR base station interworking, the PDCP SN is allocated in the MeNB PDCP apparatus of the MeNB, and since the RLC apparatus of the MeNB allocates the independent RLC SN and the NR RLC apparatus of the SeNB supports one SN, the RLC apparatus may reuse the PDCP SN without changing it. Therefore the transmission delay and window stalling problem that is mentioned in FIGS. 1GA and 1GB may occur. In the scenarios such as 1f-02, 1f-03, and 1f-04 in FIGS. 1FA and 1FB in which the same problem as described above may occur, a method for inserting into an RLC header a gap between the SN the NR RLC apparatus transmits just before 1k-05 and the currently transmitted SN can be used. The method for encoding and inserting a gap between the SNs in the NR RLC apparatus is the same as that of FIG. 1I.

[0219] However, if the gap is encoded and put in the header of all RLC PDUs, the overhead may be increased. For example, if it is assumed that the PDCP SN has a length of 18 bits, the length of the gap needs to have 18 bits (since the PDCP SN is separated and transmitted as MeNB and SeNB, the gap may need to indicate the whole space of the PDCP sequence). Therefore, in this case, since an 18-bit gap is inserted in the RLC header of all RLC PDUs, the overhead can be increased. To reduce the overhead, a GI field having a size of 2 bits defined in the RLC header is defined in Table 1-2.

[0220]

	TABLE 1-2
	GI field	Description
	00	The first RLC PDU without gap
	01	No gap for continuous RLC PDU
	10	Gap
	11	No gap for segments

[0221] The GI field value and information can be mapped to 24 different cases, and the present disclosure includes the same.

[0222] That is, if the GI field having a size of 2 bits is defined in the RLC header and thus the GI field value is 00, it may be indicated that the first RLC PDU is in the corresponding connection and the gap is not inserted into the RLC header, if the GI field value is 01, it may be indicated that the current SN is a sequence consecutive to the previous sequence and thus the gap need not to be inserted into the RLC header, if the GI field value is 10, it may be indicated that the gap between the previous SN and the current SN is present and thus the gap is inserted into the RLC header, and if the GI field value 11, it may be indicated that it is segments of one RLC PDU and thus the gap is not inserted. In the case of the first segment among the segments, there is a need to insert the gap. However, if the SN of the first segment is consecutive with the previous SN, the gap may be omitted. The case in which it is not necessary to insert the gap into the RLC header corresponds to the case in which the RLC PDUs have a consecutive SN or do not correspond to a first segment among segments of one RLC PDU. For example, in the case of SN 1 such as 1k-10, since it is the first RLC PDU, the GI field is set to be 00 to indicate it and the gap may be omitted to reduce the overhead. In the case of the SN 2, there is no need to insert an interval value because it is a SN that is consecutive with the previous SN 1. Therefore, the GI field is set to be 01 and the overhead is reduced without inserting a gap value into the RLC header. In the case of the SN 4, there is no need to insert a gap value because it is not a SN that is consecutive with the previous SN 2. Therefore, the GI field is set to be 10 and the gap value 2 is inserted into the RLC header. In the case of the segments of one RLC PDU, in the case of the first segment, the gap value with the previous SN is inserted into the RLC header and the segment may not be inserted in other cases. If the first segment has the SN consecutive to the previous SN, the GI field is set to be 0 and thus the gap value may also be omitted.

[0223] Therefore, if the NR RLC apparatus of the transmitting end transmits the SNs 1, 2, and 4 and the NR RLC apparatus successfully receives them, since the GI field is set to be 10 in the RLC PDU of the SN 4, it can be confirmed that there is the gap value, and it can be confirmed that the gap from the previous SN is 2 and the SN 3 is transmitted from another MeNB. Therefore, the NR RLC apparatus of the transmitting end and the receiving end can normally perform the RLC ARQ operation. These operations can be equally applied to the NR RLC apparatus of the scenarios such as 1f-02, 1f-03, and 1f-04 in FIGS. 1FA and 1FB. Instead of the method for inserting into the RLC header the gap between the SN that the NR RLC apparatus transmits just before and the currently transmitted SN, a method for inserting into an MAC subheader a gap between a SN (or other indicators) that the NR MAC apparatus transmits just before and the currently transmitted SN (or other indicators) may be applied. In this case, other indicators may be an indicator indicating the order of the corresponding packet. In addition, the GI field is defined in the MAC subheader field and may be identical to and modified as described above to be applied to the MAC subheader.

[0224] FIG. 1L is a diagram in which multiple access is supported by one SN, according to an embodiment of the present disclosure.

[0225] In FIG. 1L, 1l-01 shows that the LTE base station is the master (MeNB) in the 3C type LTE base station-NR base station interworking, the PDCP SN is allocated in the MeNB PDCP apparatus of the MeNB, and since the RLC apparatus of the MeNB allocates the independent RLC SN and the NR RLC apparatus of the SeNB supports one SN, the RLC apparatus may reuse the PDCP SN without changing it. Therefore the transmission delay and window stalling problem that is mentioned in FIGS. 1GA and 1GB may occur. In the scenarios such as 1f-02, 1f-03, and 1f-04 in FIGS. 1Fa and 1FB in which the same problem as described above may occur, a method for inserting into an RLC header a gap between the SN the NR RLC apparatus transmits just before 1l-05 and the currently transmitted SN can be used. The method for coding and inserting a gap between SNs in the NR RLC apparatus is the same as that of FIG. 1I, and if a gap is 0, it indicates the first RLC PDU in the corresponding connection. In addition, a gap is encoded and put in all the RLC PDUs; however, to reduce the overhead, a variable gap size is used.

[0226] For example, if it is assumed that the PDCP SN has a length of 12 bits, the length of the gap needs to have 12 bits (since the PDCP SN is separated and transmitted as MeNB and SeNB, the gap may need to indicate the whole space of the PDCP sequence. Therefore, in this case, since a 12-bit gap is inserted in the RLC header of all RLC PDUs, the overhead can be increased. A gap length (GL) field having a size of 1 bit is defined in the RLC header to reduce the overhead. In the above description, a predetermined bit may have several bits, and if x bits are included, a size of 2{circumflex over ( )}x gap fields may be indicated. For example, a 1-bit GL field may be defined as in Table 1-3.

[0227]

	TABLE 1-3
	GI field	Description
	0	5 bits gap field
	1	12 bits gap field

[0228] The mapping information may indicate a size of various gap fields using several bits.

[0229] That is, if the GL field having a size of 1 bit is defined in the RLC header and thus the field value is 0, a field having a length of 5 bits is used to indicate a gap in the corresponding RLC PDU, and if the GL field value is 1, a field having a length of 12 bits is used to indicate the gap in the PDU. For example, in the case of the SN 1 such as 11-10, since it is the first RLC PDU of the corresponding connection, the GI field is set to be 00 to indicate it and the gap having a size of 5 bits may be used to reduce the overhead. In the case of the SN 2, since it is a SN consecutive to the previous SN 1, the gap value is reduced, so the GL field is set to be 0 and the gap having a size of 5 bits may be used. Even in the case of the SN 4, since it the previous SN 2 and the gap value are reduced, so the GL field is set to be 0 and the gap having a size of 5 bits may be used. However, in the case of the SN 1010, since the gap from the previous SN 4 is large, it is possible to set a GL field to be 1 and use a gap having a size of 12 bits.

[0230] Therefore, if the NR RLC apparatus of the transmitting end transmits the SNs 1, 2, and 4 and the NR RLC apparatus successfully receives them, since the GI field is set to be 0 in the RLC PDU of the SN 4, it can be confirmed that there is the gap value having a size of 5 bits, and it can be confirmed that the gap from the previous SN is 2 and the SN 3 is transmitted from another MeNB. Therefore, the NR RLC apparatus of the transmitting end and the receiving end can normally perform the RLC ARQ operation. These operations can be equally applied to the NR RLC apparatus of the scenarios such as 1f-02, 1f-03, and 1f-04 in FIGS. 1FA and 1FB. Instead of the method for inserting into the RLC header the gap between the SN that the NR RLC apparatus transmits just before and the currently transmitted SN, a method for inserting into an MAC subheader a gap between a SN (or other indicators) that the NR MAC apparatus transmits just before and the currently transmitted SN (or other indicators) may be applied. In this case, other indicators may be an indicator indicating the order of the corresponding packet. In addition, the GI field is defined in the MAC subheader field and may be identical to and modified as described above to be applied to the MAC subheader.

[0231] In the next generation mobile communication systems, a high data rate is supported, so if data is missed, a large amount of data is likely to be lost. Therefore, an RLC status report method is needed. The present disclosure proposes various RLC status reporting methods suitable for the next generation mobile communication system. The RLC status reporting methods proposed below can identically be transmitted in a single access environment connecting only to the LTE or the NR as well as the multiple access environment as described above.

[0232] FIG. 1M is a diagram of a RLC status reporting method, according to an embodiment of the present disclosure.

[0233] FIG. 1M an RLC status report can be sent from a receiving side RLC layer apparatus to a transmitting side RLC layer apparatus (assuming a 10 bit RLC SN length).

[0234] The receiving side RLC layer apparatus stores the received RLC PDUs in the receiving buffer and then checks the SN to recognize the SN of the RLC PDU missed during the transmission. If the predetermined condition is satisfied, the receiving side RLC layer apparatus generates an RLC status report message and transmits the generated RLC status report message to the transmitting side RLC layer apparatus. The RLC status report message includes information on the RLC PDU reception state of the receiving side RLC layer apparatus, and the transmitting side RLC layer apparatus identifies that the RLC PDU successfully transmitted and the RLC PDU failed to transmit, through the RLC status report message. The RLC status report message may be 1m-05 in FIG. 1M. The RLC status report message includes one ACK_SN or one ACK_SN and one or more NACK. The presence of NACK_SN is indicated by an E1 field. The E1 field indicates one NACK_SN, an E1 field, and an E2 field follow, and the E2 field indicates whether or not SOstart and SOend fields indicating a part of the NACK_SN follow. The ACK_SN field includes the next SN of the highest SN among the SNs of RLC PDUs successfully received so far and the NACK_SN includes the SNs of the RLC PDUs that have not been received. For example, the transmitting side RLC layer apparatus transmits RLC PDU 7 to RLC PDU 10 at any time, and the receiving side RLC layer apparatus receives only RLC PDU 7 and RLC PDU 9 and stores the received RLC PDU 7 and RLC PDU 9 in the receiving buffer. If the RLC status report message generation condition is satisfied at any time, the receiving side RLC layer apparatus generates the RLC status report message. A SN 10 is included in the ACK_SN field of the RLC status report message, and a SN 8 is included in the NACK_SN field. The transmitting side RLC layer apparatus receiving the RLC status report message determines that the RLC PDU having a SN lower than the lowest NACK_SN, that is, the RLC PDUs having a SN lower than 7 is successfully transmitted and discards it in a retransmission buffer. In addition, PDCP SDUs mapped to the RLC PDUs having a SN lower than 7 among the PDCP SDUs stored in the transmission buffer is also discarded. The transmitting side RLC layer apparatus retransmits the RLC PDU 8 reporting that the receiving side RLC layer apparatus has not received.

[0235] The RLC layer apparatus transmits the RLC PDU with the SN, and checks whether the transmitted RLC PDU succeeds based on the RLC status report message and retransmits the RLC PDU, thereby ensuring reliable transmission/reception.

[0236] By receiving a general RLC status report message, the transmitting side RLC layer apparatus acquires the following two pieces of information largely.

[0237] Identify RLC PDU failed in transmission

[0238] Identify RLC PDU succeeded in transmission

[0239] It is recognized which RLC PDU to retransmit in the future by identifying the RLC PDU failing to transmit, and it determines which RLC PDU or PDCP SDU of RLC PDUs or PDCP SDUs stored in the retransmission buffer and the transmission buffer is discarded.

[0240] The fields applied to the RLC status reporting method for the present disclosure are as follows.

[0241] The D/C field has a length of 1 bit and indicates whether the RLC PDU is an RLC data PDU or an RLC control PDU as in Table 1-4.

[0242]

	TABLE 1-4
	D/C field value	Description
	0	Control PDU
	1	Data PDU

[0243] The CPT field has a length of 1 bit and indicates a kind of RLC control PDU, as in Table 1-5.

[0244]

	TABLE 1-5
	CPT field value	Description
	000	STATUS PDU
	001-111	Reserved
		(PDUs with this coding will be discarded by the
		receiving entity for this release of the protocol)

[0245] ACK_SN indicates the next SN of the RLC PDU that has not yet been received and a SN that is not reported as missed in the RLC status report. Upon receiving the RLC status report at the transmitting end, it is determined that the SN indicated by the ACK_SN is not included, the SN indicated by the NACK_SN is not included, and a SN smaller than ACK_SN has been received successfully (when the NACK_SN is indicated together with the SOstart and the SOend, it is determined that the SOstart and the SOend successfully receive only a part other than the part indicated by the NACK_SN). The ACK_SN has a predetermined length, and the predetermined length can be variously defined such as 10 bits, 16 bits, or 18 bits.

[0246] The E1 field has a length of 1 bit and indicates whether or not the NACK_SN, the E1 field, and the E2 field follow as in Table 1-6.

[0247]

TABLE 1-6
E1 field value	Description
0	A set of NACK_SN, E1 and E2 does not follow.
1	A set of NACK_SN, E1 and E2 follows.

[0248] NACK_SN indicates the SN of the missed RLC PDU, and may indicate a part of the lost RLC PDU together with SOstart and SOend. The NACK_SN has a predetermined length, and the predetermined length can be variously defined such as 10 bits, 16 bits, or 18 bits.

[0249] The E2 field has a length of 1 bit and indicates whether the SOstart and the SOend follow as in Table 1-7.

[0250]

TABLE 1-7
E2 field value	Description
0	A set of SOstart and SOend does not follow for this
	NACK_SN.
1	A set of SOstart and SOend follows for this NACK_SN.

[0251] The SOstart field indicates a head position of the part when indicating a part of the NACK_SN. The head position may be indicated by a byte unit. The SOstart has a predetermined length, and the predetermined length can be variously defined such as 15 bits, 16 bits, and 18 bits.

[0252] The SOend field indicates a tail position of the part when indicating a part of the NACK_SN. The tail position may be indicated by a byte unit. The SOend has a predetermined length, and the predetermined length can be variously defined such as 15 bits, 16 bits, and 18 bits.

[0253] The RLC status reporting method proposed above can be equally applied to the NR RLC apparatus of 1f-02, 1f-03, and 1f-04 in FIGS. 1FA and 1FB.

[0254] FIG. 1N shows an RLC status reporting method, according to an embodiment of the present disclosure.

[0255] In FIG. 1N an RLC status report can be sent from a receiving side RLC layer apparatus to a transmitting side RLC layer device according to a RLC status reporting method (assuming a 10 bit RLC SN length).

[0256] The receiving side RLC layer device stores the received RLC PDUs in the receiving buffer and then checks the SN to recognize the SN of the RLC PDU missed during the transmission. If the predetermined condition is satisfied, the receiving side RLC layer apparatus generates an RLC status report message and transmits the generated RLC status report message to the transmitting side RLC layer apparatus. The RLC status report message includes information on the RLC PDU reception state of the receiving side RLC layer apparatus, and the transmitting side RLC layer apparatus identifies the RLC PDU successfully transmitted and the RLC PDU failed to transmit, through the RLC status report message. The RLC status report message may be written as 1n-05 in FIG. 1N. The RLC status report message includes one ACK_SN or a set of one ACK_SN and one or more LOWER_SN, UPPER_SN, E1, and E2 fields. It is indicated by the E1 field whether there are the set of LOWER_SN, UPPER_SN, E1, and E2 fields. The E1 field indicates whether a set of one LOWER_SN field, the UPPER_SN field, the E1 field, and the E2 field follow, and the E2 field indicates whether or not SOstart and SOend fields indicating a part of the NACK_SN follow. The ACK_SN field includes the next SN of the highest SN among the SNs of RLC PDUs that have successfully been received and the NACK_SN includes the lowest SN that has successfully been received. The UPPER_SN may include the highest SN that has not been received. The LOWER_SN and the UPPER_SN may include the SN by various predetermined methods to indicate a range of a large number of missed SNs. That is, the RLC apparatus of the receiving end may request the retransmission to the RLC apparatus of the transmitting end since the RLC PDUs corresponding to all SNs between the LOWER_SN<SN<=UPPER_SN is missed. For example, the transmitting side RLC layer apparatus transmits RLC PDU 5 to RLC PDU 80 at any time, and the receiving side RLC layer apparatus receives only RLC PDU 5, RLC PDU 78, RLC PDU 79, and RLC PDU 80 and stores the received RLC PDU 5, RLC PDU 78, RLC PDU 79, and RLC PDU 80 in the receiving buffer. If the RLC status report message generation condition is satisfied at any time, the receiving side RLC layer apparatus generates the RLC status report message. The ACK_SN field of the RLC status reporting message may include SN 81, the LOWER_SN field my include SN 5, and the UPPER_SN may include 77. The transmitting side RLC layer apparatus receiving the RLC status report message determines that the RLC PDU having a SN lower than the lowest LOWER_SN, that is, the RLC PDUs having a SN lower than 5 is successfully transmitted and discards it in a retransmitting buffer. In addition, PDCP SDUs mapped to the RLC PDUs having a SN lower than 5 among the PDCP SDUs stored in the transmission buffer is also discarded. The transmitting side RLC layer apparatus retransmits the RLC PDU 6 to RLC PDU 77 reporting that the receiving side RLC layer apparatus has not received.

[0257] When the first RLC PDU of the RLC layer apparatus of the transmitting end is missed, the LOWER_SN may be allocated as the same value as the UPPER_SN to notify the transmitting end that all the SNs smaller than the UPPER_SN are not received. For example, if the LOWER_SN field includes a SN 77 and the UPPER_SN includes 77, (SN<=77) may be indicated. When the first RLC PDU is missed, the LOWER_SN and the UPPER_SN may be defined by various methods. Alternatively, another field may be defined.

[0258] The RLC layer apparatus transmits the RLC PDU with the SN, and checks whether the transmitted RLC PDU succeeds based on the RLC status report message and retransmits the RLC PDU, thereby ensuring reliable transmission/reception.

[0259] By receiving a general RLC status report message, the transmitting side RLC layer apparatus acquires the following two pieces of information largely.

[0260] Identify RLC PDU failed in transmission

[0261] Identify RLC PDU succeeded in transmission

[0262] It is recognized which RLC PDU to retransmit in the future by identifying the RLC PDU failing to transmit, and it determines which RLC PDU or PDCP SDU of RLC PDUs or PDCP SDUs stored in the retransmission buffer and the transmission buffer is discarded.

[0263] The fields applied to the RLC status reporting method for the present disclosure are as follows.

[0264] The D/C field has a length of 1 bit and indicates whether the RLC PDU is an RLC data PDU or an RLC control PDU as in Table 1-8.

[0265]

	TABLE 1-8
	D/C field value	Description
	0	Control PDU
	1	Data PDU

[0266] The CPT field has a length of 1 bit and indicates a kind of RLC control PDU as in Table 1-9.

[0267]

	TABLE 1-9
	CPT field value	Description
	000	STATUS PDU
	001-111	Reserved
		(PDUs with this coding will be discarded by the
		receiving entity for this release of the protocol)

[0268] ACK_SN indicates the next SN of the RLC PDU that has not yet been received and a SN that is not reported as missed in the RLC status report. Upon receiving the RLC status report at the transmitting end, it is determined that the SN indicated by the ACK_SN is not included, the SNs indicated by the LOWER_SN and the UPPER_SN are not included, and a SN smaller than ACK_SN has been received successfully (when the UPPER_SN is indicated together with the SOstart and the SOend, it is determined that the SOstart and the SOend successfully receive only a part other than the part indicated by the UPPER_SN). The ACK_SN has a predetermined length, and the predetermined length can be variously defined such as 10 bits, 16 bits, or 18 bits.

[0269] The E1 field has a length of 1 bit and indicates whether or not the LOWER_SN, the UPPER_SN, the E1 field, and the E2 field follow, as in Table 1-10.

[0270]

TABLE 1-10
E1 field value	Description
0	A set of LOWER_SN, UPPER_SN, E1 and E2 does not
	follow.
1	A set of LOWER_SN, UPPER_SN, E1 and E2 follows.

[0271] The LOWER_SN may include the lowest SN that has successfully been received. The UPPER_SN may include the highest SN that has not been received. The LOWER_SN and the UPPER_SN may include the SN by various predetermined methods to indicate a range of a large number of missed SNs. The LOWER_SN and UPPER_SN have a predetermined length, and the predetermined length can be variously defined such as 10 bits, 16 bits, or 18 bits. When the first RLC PDU of the RLC layer apparatus of the transmitting end is missed, the LOWER_SN may be allocated as the same value as the UPPER_SN to notify the transmitting end that all the SNs smaller than the UPPER_SN are not received. For example, if the LOWER_SN field includes a SN 77 and the UPPER_SN includes 77, (SN<=77) may be indicated. When the first RLC PDU is missed, the LOWER_SN and the UPPER_SN may be defined by various methods. Alternatively, another field may be defined.

[0272] The E2 field has a length of 1 bit and indicates whether the SOstart and the SOend follow, as in Table 1-11.

[0273]

TABLE 1-11
E2 field value	Description
0	A set of SOstart and SOend does not follow for this
	UPPER_SN.
1	A set of SOstart and SOend follows for this UPPER_SN.

[0274] The SOstart field indicates a head position of the part when indicating a part of the UPPER_SN. The head position may be indicated by a byte unit. The SOstart has a predetermined length, and the predetermined length can be variously defined such as 15 bits, 16 bits, and 18 bits.

[0275] The SOend field indicates a tail position of the part when indicating a part of the UPPER_SN. The tail position may be indicated by a byte unit. The SOend has a predetermined length, and the predetermined length can be variously defined such as 15 bits, 16 bits, and 18 bits.

[0276] The 1 RLC status reporting method proposed above can be equally applied to the NR RLC apparatus of 1f-02, 1f-03, and 1f-04 in FIGS. 1FA and 1FB.

[0277] FIG. 1O is a diagram of an RLC status reporting method, according to an embodiment of the present disclosure.

[0278] In FIG. 1O an RLC status report is sent from a receiving side RLC layer apparatus to a transmitting side RLC layer device (assuming a 10 bit RLC SN length).

[0279] The receiving side RLC layer device stores the received RLC PDUs in the receiving buffer and then checks the SN to recognize the SN of the RLC PDU missed during the transmission. If the predetermined condition is satisfied, the receiving side RLC layer apparatus generates an RLC status report message and transmits the generated RLC status report message to the transmitting side RLC layer apparatus. The RLC status report message includes information on the RLC PDU reception state of the receiving side RLC layer apparatus, and the transmitting side RLC layer apparatus identifies the RLC PDU successfully transmitted and the RLC PDU failed to transmit, through the RLC status report message. The RLC status report message may be written as 1o-05 in FIG. 1O. The RLC status report message includes one ACK_SN or a set of one ACK_SN and one or more LOWER_SN, E2, UPPER_SN, E1, and E2 fields. It is indicated by the E1 field whether there are the set of LOWER_SN, UPPER_SN, E1, and E2 fields. The E1 field indicates whether a set of one LOWER_SN field, the E2 UPPER_SN field, the E1 field, and the E2 field follow, and the E2 field indicates whether or not SOstart and SOend fields indicating a part of the LOWER_SN or the UPPER_SN follow. The ACK_SN field includes the next SN of the highest SN among the SNs of RLC PDUs that have been successfully received and the NACK_SN includes the lowest SN that has been successfully received. The UPPER_SN may include the highest SN that has not received so far. The LOWER_SN and the UPPER_SN may include the SN by various predetermined methods to indicate a range of a large number of missed SNs. That is, as an example, the RLC apparatus of the receiving end may request the retransmission to the RLC apparatus of the transmitting end since the RLC PDUs corresponding to all SNs between the LOWER_SN<SN<=UPPER_SN is missed. For example, the transmitting side RLC layer apparatus transmits RLC PDU 5 to RLC PDU 80 at any time, and the receiving side RLC layer apparatus receives only RLC PDU 5, RLC PDU 78, RLC PDU 79, and RLC PDU 80 and stores the received RLC PDU 5, RLC PDU 78, RLC PDU 79, and RLC PDU 80 in the receiving buffer. If the RLC status report message generation condition is satisfied at any time, the receiving side RLC layer apparatus generates the RLC status report message. The ACK_SN field of the RLC status reporting message may include SN 81, the LOWER_SN field my include SN 5, and the UPPER_SN may include 77. The transmitting side RLC layer apparatus receiving the RLC status report message determines that the RLC PDU having a SN lower than the lowest LOWER_SN, that is, the RLC PDUs having a SN lower than 5 is successfully transmitted and discards it in a retransmitting buffer. In addition, PDCP SDUs mapped to the RLC PDUs having a SN lower than 5 among the PDCP SDUs stored in the transmission buffer is also discarded. The transmitting side RLC layer apparatus retransmits the RLC PDU 6 to RLC PDU 77 reporting that the receiving side RLC layer apparatus has not received.

[0280] When the first RLC PDU of the RLC layer apparatus of the transmitting end is missed, the LOWER_SN may be allocated as the same value as the UPPER_SN to notify the transmitting end that all the SNs smaller than the UPPER_SN are not received. For example, if the LOWER_SN field includes a SN 77 and the UPPER_SN includes 77, (SN<=77) may be indicated. When the first RLC PDU is missed, the LOWER_SN and the UPPER_SN may be defined by various methods. Alternatively, another field may be defined.

[0281] The RLC layer apparatus transmits the RLC PDU with the SN, and checks whether the transmitted RLC PDU succeeds based on the RLC status report message and retransmits the RLC PDU, thereby ensuring reliable transmission/reception.

[0282] By receiving a general RLC status report message, the transmitting side RLC layer apparatus acquires the following two pieces of information.

[0283] Identify RLC PDU failed in transmission

[0284] Identify RLC PDU succeeded in transmission

[0285] It is recognized which RLC PDU to retransmit in the future by identifying the RLC PDU failing to transmit, and it determines which RLC PDU or PDCP SDU of RLC PDUs or PDCP SDUs stored in the retransmission buffer and the transmission buffer is discarded.

[0286] The fields applied to the 1-3-3-th RLC status reporting method for the present disclosure are as follows.

[0287] The D/C field has a length of 1 bit and indicates whether the RLC PDU is an RLC data PDU or an RLC control PDU as in Table 1-12.

[0288]

	TABLE 1-12
	D/C field value	Description
	0	Control PDU
	1	Data PDU

[0289] The CPT field has a length of 1 bit and indicates a kind of RLC control PDU as in Table 1-13.

[0290]

	TABLE 1-13
	CPT field value	Description
	000	STATUS PDU
	001-111	Reserved
		(PDUs with this coding will be discarded by the
		receiving entity for this release of the protocol)

[0291] ACK_SN indicates the next SN of the RLC PDU that has not yet been received and a SN that is not reported as missed in the RLC status report. Upon receiving the RLC status report at the transmitting end, it is determined that the SN indicated by the ACK_SN is not included, the SNs indicated by the LOWER_SN and the UPPER_SN are not included, and a SN smaller than ACK_SN has been received successfully (when the LOWER_SN is indicated together with the SOstart and the SOend or the UPPER_SN is indicated together with the SOstart and the SO end, it is determined that the SOstart and the SOend successfully receive only a part other than the part indicated by the LOWER_SN or a part other than the part indicated by the UPPER_SN). The ACK_SN has a predetermined length, and the predetermined length can be variously defined such as 10 bits, 16 bits, or 18 bits.

[0292] The E1 field has a length of 1 bit and indicates whether or not the LOWER_SN, the UPPER_SN, the E1 field, and the E2 field follow as in Table 1-14.

[0293]

	TABLE 1-14
	E1 field value	Description
	0	A set of LOWER_SN, E2, UPPER_SN, E1 and E2
		does not follow.
	1	A set of LOWER_SN, E2, UPPER_SN, E1 and E2
		follows.

[0294] The LOWER_SN may include the lowest SN that has been successfully received. The UPPER_SN may include the highest SN that has not been received. The LOWER_SN and the UPPER_SN may include the SN by various predetermined methods to indicate a range of a large number of missed SNs. The LOWER_SN and UPPER_SN have a predetermined length, and the predetermined length can be variously defined such as 10 bits, 16 bits, or 18 bits. When the first RLC PDU of the RLC layer apparatus of the transmitting end is missed, the LOWER_SN may be allocated as the same value as the UPPER_SN to notify the transmitting end that all the SNs smaller than the UPPER_SN are not received. For example, if the LOWER_SN field may include a SN 77 and the UPPER_SN includes 77, (SN<=77) may be indicated. When the first RLC PDU is missed, the LOWER_SN and the UPPER_SN may be defined by various methods. Alternatively, another field may be defined.

[0295] The E2 field has a length of 1 bit and indicates whether the SOstart and the SOend follow as in Table 1-15.

[0296]

TABLE 1-15
E2 field value	Description
0	A set of SOstart and SOend does not follow for this
	LOWER_SN or UPPER_SN.
1	A set of SOstart and SOend follows for this LOWER_SN
	or UPPER_SN.

[0297] The SOstart field indicates a head position of the part when indicating a part of the LOWER_SN or the UPPER_SN. The head position may be indicated by a byte unit. The SOstart has a predetermined length, and the predetermined length can be variously defined such as 15 bits, 16 bits, and 18 bits.

[0298] The SOend field indicates a tail position of the part when indicating a part of the LOWER_SN or the UPPER_SN. The tail position may be indicated by a byte unit. The SOend has a predetermined length, and the predetermined length can be variously defined such as 15 bits, 16 bits, and 18 bits.

[0299] The 1-3-3-th RLC status reporting method proposed above can be equally applied to the NR RLC apparatus of the scenarios such as 1f-02, 1f-03, and 1f-04 in FIGS. 1FA and 1FB.

[0300] FIG. 1P is a diagram of an RLC status reporting method, according to an embodiment of the present disclosure.

[0301] In FIG. 1P an RLC status report is sent from a receiving side RLC layer apparatus to a transmitting side RLC layer device (assuming a 10 bit RLC SN length).

[0302] The receiving side RLC layer device stores the received RLC PDUs in the receiving buffer and then checks the SN to recognize the SN of the RLC PDU missed during the transmission. If the predetermined condition is satisfied, the receiving side RLC layer apparatus generates an RLC status report message and transmits the generated RLC status report message to the transmitting side RLC layer apparatus. The RLC status report message includes information on the RLC PDU reception state of the receiving side RLC layer apparatus, and the transmitting side RLC layer apparatus identifies the RLC PDU successfully transmitted and the RLC PDU failed to transmit, through the RLC status report message. The RLC status report message may be written as 1p-05 in FIG. 1P. The RLC status report message includes one ACK_SN or a set of one ACK_SN and one or more NACK_SN, E1, E2, and E3 fields. It is indicated by the E1 field whether there are the set of NACK_SN, E1, E2, and E3 fields. The E1 field indicates whether a set of one NACK_SN field, the E1 field, the E2 field, and the E3 field follow, and the E2 field indicates whether or not SOstart and SOend fields indicating a part of the NACK_SN follow. The E3 field indicates whether there are N (number of missing RLC PDUs) fields indicating how many SNs above (larger) or below (smaller) from the SN indicated by the NACK_SN are missed. The N field is a field indicating how many SNs above (having a larger SN) or below (having a smaller SN) from the SN indicated by the NACK_SN are missed.

[0303] The ACK_SN field may include the next SN of the highest SN among the SNs of RLC PDUs that have successfully been received and the NACK_SN may include the SN that has not been successfully received. When a plurality of consecutive RLC PDUs are missed, the highest SN that has not been received or the lowest SN that has not been received can be included in the NACK_SN in order to use NACK_SN together with the N field, and the N field may include the number of missed SNs. The NACK_SN and N fields nay be defined and applied by various other methods to indicate a number of RLC PDUs that have been missed consecutively. That is, as an example, the RLC apparatus of the receiving end may request the retransmission to the RLC apparatus of the transmitting end since the RLC PDUs corresponding to all SNs between 2<SN<=8 as the NACK_SN=8 and N=6. As another example, the transmitting side RLC layer apparatus transmits RLC PDU 5 to RLC PDU 80 at any time, and the receiving side RLC layer apparatus receives only RLC PDU 5, RLC PDU 78, RLC PDU 79, and RLC PDU 80 and stores the received RLC PDU 5, RLC PDU 78, RLC PDU 79, and RLC PDU 80 in the receiving buffer. If the RLC status report message generation condition is satisfied at any time, the receiving side RLC layer apparatus generates the RLC status report message. The ACK_SN field of the RLC status report message may include the SN 81, the NACK_SN field may include the SN 6, and another NACK_SN field may include 69 in the N field together with the SN 8 (6, 8<=SN<=77). The transmitting side RLC layer apparatus receiving the RLC status report message determines that the RLC PDU having a SN lower than the lowest NACK_SN, that is, the RLC PDUs having a SN lower than 6 is successfully transmitted and discards it in a retransmitting buffer. In addition, PDCP SDUs mapped to the RLC PDUs having a SN lower than 6 among the PDCP SDUs stored in the transmission buffer is also discarded. The transmitting side RLC layer apparatus retransmits the RLC PDU 6 to RLC PDU 8 to RLC PDU 77 reporting that the receiving side RLC layer apparatus has not received.

[0304] The RLC layer apparatus transmits the RLC PDU with the SN, and checks whether the transmitted RLC PDU succeeds based on the RLC status report message and retransmits the RLC PDU, thereby ensuring reliable transmission/reception.

[0305] By receiving a general RLC status report message, the transmitting side RLC layer apparatus acquires the following two pieces of information largely.

[0306] Identify RLC PDU failed in transmission

[0307] Identify RLC PDU succeeded in transmission

[0308] It is recognized which RLC PDU to retransmit in the future by identifying the RLC PDU failing to transmit, and it determines which RLC PDU or PDCP SDU of RLC PDUs or PDCP SDUs stored in the retransmission buffer and the transmission buffer is discarded.

[0309] The fields applied to the RLC status reporting method for the present disclosure are as follows.

[0310] The D/C field has a length of 1 bit and indicates whether the RLC PDU is an RLC data PDU or an RLC control PDU as in Table 1-16.

[0311]

	TABLE 1-16
	D/C field value	Description
	0	Control PDU
	1	Data PDU

[0312] The CPT field has a length of 1 bit and indicates a kind of RLC control PDU as in Table 1-17.

[0313]

	TABLE 1-17
	CPT field value	Description
	000	STATUS PDU
	001-111	Reserved
		(PDUs with this coding will be discarded by the
		receiving entity for this release of the protocol)

[0314] ACK_SN indicates the next SN of the RLC PDU that has not yet been received and a SN that is not reported as missed in the RLC status report. Upon receiving the RLC status report at the transmitting end, it is determined that the SN indicated by the ACK_SN is not included, the SNs indicated by the NACK_SN are not included, the SNs included in the range indicated by the NACK_SN and the N field are not included, and the SN smaller than the ACK_SN has been received successfully (when the NACK_SN is indicated together with the SOstart and the SOend, it is determined that the SOstart and the SOend successfully receive only a part other than the part indicated by the NACK_SN). The ACK_SN has a predetermined length, and the predetermined length can be variously defined such as 10 bits, 16 bits, or 18 bits.

[0315] The E1 field has a length of 1 bit and indicates whether or not the LOWER_SN, the UPPER_SN, the E1 field, and the E2 field follow as in Table 1-18.

[0316]

TABLE 1-18
E1 field value	Description
0	A set of NACK_SN, E1, E2, and E3 does not follow.
1	A set of NACK_SN, E1, E2, and E3 follows.

[0317] The NACK_SN may include the SN that has not been received. When a plurality of consecutive RLC PDUs are missed, the highest SN that has not been received or the lowest SN that has not been received can be included in the NACK_SN in order to use NACK_SN together with the N field, and the N field may include the number of missed SNs. The NACK_SN and N fields may be defined and applied by various other methods to indicate a number of RLC PDUs that have been missed consecutively. The NACK_SN has a predetermined length, and the predetermined length can be variously defined such as 10 bits, 16 bits, or 18 bits.

[0318] The N field is a field indicating how many SNs above (having a larger SN) or below (having a smaller SN) from the SN indicated by the NACK_SN are missed.

[0319] The E2 field has a length of 1 bit and indicates whether the SOstart and the SOend follow as in Table 1-19.

[0320]

Table 1-19
E2 field value	Description
0	A set of SOstart and SOend does not follow for this
	LOWER_SN or UPPER_SN.
1	A set of SOstart and SOend follows for this LOWER_SN
	or UPPER_SN.

[0321] The E3 field indicates whether there are N (number of missing RLC PDUs) fields indicating how many SNs above (larger) or below (smaller) from the SN indicated by the NACK_SN are missed as in Table 1-20.

[0322]

	TABLE 1-20
	E3 field value	Description
	0	N does not follow for this NACK_SN.
	1	N follows for this NACK_SN.

[0323] The SOstart field indicates a head position of the part when indicating a part of the NACK_SN. The head position may be indicated by a byte unit. The SOstart has a predetermined length, and the predetermined length can be variously defined such as 15 bits, 16 bits, and 18 bits.

[0324] The SOend field indicates a tail position of the part when indicating a part of the NACK_SN. The tail position may be indicated by a byte unit. The SOend has a predetermined length, and the predetermined length can be variously defined such as 15 bits, 16 bits, and 18 bits.

[0325] The RLC status reporting method proposed above can be equally applied to the NR RLC apparatus of 1f-02, 1f-03, and 1f-04 in FIGS. 1FA and 1FB.

[0326] FIG. 1Q is a flowchart of a method of the terminal.

[0327] In FIG. 1Q, the terminal receives a packet from the higher layer (at step 1q-05) and configures an RLC header (at step 1q-10) to generate the received packet as the RLC PDU. When configuring the RLC header, one of the previously described methods for configuring the RLC header can be used to configure the RLC header (at step 1q-15). The generated RLC PDU is transferred to a lower layer (at step 1q-20). The operation of the terminal may equally apply to the NR RLC apparatus of the 1f-02, 1f-03, 1f-04 in FIGS. 1FA and 1FB.

[0328] FIG. 1R is a diagram of the terminal, according to an embodiment of the present disclosure.

[0329] Referring to FIG. 1R, the terminal includes a radio frequency (RF) processor 1r-10, a baseband processor 1r-20, a memory 1r-30, and a controller 1r-40.

[0330] The RF processor 1r-10 serves to transmit and receive a signal through a radio channel, such as band conversion and amplification of a signal. That is, the RF processor 1r-10 up-converts a baseband signal provided from the baseband processor 1r-20 into an RF band signal and then transmits the RF band signal through an antenna and down-converts the RF band signal received through the antenna into the baseband signal. The RF processor 1r-10 may include a transmitting filter, a receiving filter, an amplifier, a mixer, an oscillator, a digital to analog converter (DAC), an analog to digital converter (ADC), or the like. FIG. 1R illustrates only one antenna but the terminal may include a plurality of antennas. The RF processor 1r-10 may include a plurality of RF chains. The RF processor 1r-10 may perform beamforming. For the beamforming, the RF processor 1r-10 may adjust a phase and a size of each of the signals transmitted and received through a plurality of antennas or antenna elements. In addition, the RF processor may perform MIMO and may receive a plurality of layers when performing a MIMO operation. The RF processor 1r-10 may perform reception beam sweeping by appropriately configuring a plurality of antennas or antenna elements under the control of the controller or adjust a direction and a beam width of the reception beam so that the reception beam is resonated with the transmission beam.

[0331] The baseband processor 1r-20 performs a conversion function between a baseband signal and a bit string according to a physical layer standard of a system. When data is transmitted, the baseband processor 1r-20 generates complex symbols by coding and modulating a transmitted bit string. Further, when data is received, the baseband processor 1r-20 recovers the received bit string by demodulating and decoding the baseband signal provided from the RF processor 1r-10. According to the OFDM scheme, when data is transmitted, the baseband processor 1r-20 generates the complex symbols by coding and modulating the transmitting bit string, maps the complex symbols to sub-carriers, and then performs an inverse fast Fourier transform (IFFT) operation and a cyclic prefix (CP) insertion to configure the OFDM symbols. Further, when data are received, the baseband processor 1r-20 divides the baseband signal provided from the RF processor 1r-10 in an OFDM symbol unit and recovers the signals mapped to the sub-carriers by a fast Fourier transform (FFT) operation and then recovers the received bit string by the modulation and decoding.

[0332] The baseband processor 1r-20 and the RF processor 1r-10 transmit and receive a signal as described above. The baseband processor 1r-20 and the RF processor 1r-10 may be called a transmitter, a receiver, a transceiver, or a communication unit. At least one of the baseband processor 1r-20 and the RF processor 1r-10 may include a plurality of communication modules to support a plurality of different RATs. Further, at least one of the baseband processor 1r-20 and the RF processor 1r-10 may include different communication modules to process signals in different frequency bands. The different wireless access technologies may include an LTE network, an NR network, and the like. Further, different frequency bands may include a super high frequency (SHF) (for example, 2.5 GHz, 5 GHz) band, a millimeter wave (for example, 60 GHz) band.

[0333] The memory 1r-30 stores data such as basic programs, application programs, and configuration information for the operation of the terminal. Further, the memory 1r-30 provides the stored data according to the request of the controller 1r-40.

[0334] The controller 1r-40 controls the overall operations of the terminal. The controller 1r-40 transmits and receives a signal through the baseband processor 1r-20 and the RF processor 1r-10. Further, the controller 1r-40 records and reads data in and from the memory 1r-40. The controller 1r-40 may include at least one processor, and may include a communication processor (CP) performing a control for communication, an application processor (AP) controlling a higher layer such as the application programs, and a multiple connection processor 1r-42 controlling connections between multiple nodes.

[0335] FIG. 1S is a diagram of a base station or a TRP (transmission and reception point) in a wireless communication system, according to an embodiment of the present disclosure.

[0336] As illustrated in FIG. 1S, the base station is configured to include an RF processor 1s-10, a baseband processor 1s-20, a communication unit 1s-30, a memory 1s-40, and a controller 1s-50.

[0337] The RF processor 1s-10 serves to transmit and receive a signal through a radio channel, such as band conversion and amplification of a signal. That is, the RF processor 1s-10 up-converts a baseband signal provided from the baseband processor 1s-20 into an RF band signal and then transmits the RF band signal through an antenna and down-converts the RF band signal received through the antenna into the baseband signal. The RF processor 1s-10 may include a transmitting filter, a receiving filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, or the like. FIG. 1S illustrates only one antenna but the first access node may include a plurality of antennas. The RF processor 1s-10 may include a plurality of RF chains. Further, the RF processor 1s-10 may perform the beamforming. For the beamforming, the RF processor 1s-10 may adjust a phase and a size of each of the signals transmitted/received through a plurality of antennas or antenna elements. The RF processor 1s-10 may perform a downward MIMO operation by transmitting one or more layers.

[0338] The baseband processor 1s-20 performs a conversion function between the baseband signal and the bit string according to the physical layer standard of the first radio access technology. When data is transmitted, the baseband processor 1s-20 generates complex symbols by coding and modulating a transmitted bit string. Further, when data is received, the baseband processor 1s-20 recovers the received bit string by demodulating and decoding the baseband signal provided from the RF processor 1s-10. According to the OFDM scheme, when data is transmitted, the baseband processor 1s-20 generates the complex symbols by coding and modulating the transmitting bit string, maps the complex symbols to the sub-carriers, and then performs the IFFT operation and the CP insertion to construct the OFDM symbols. When data is received, the baseband processor 1s-20 divides the baseband signal provided from the RF processor 1s-10 in the OFDM symbol unit and recovers the signals mapped to the sub-carriers by the FFT operation and then recovers the receiving bit string by the modulation and decoding. The baseband processor 1s-20 and the RF processor 1s-10 transmit and receive a signal as described above. Therefore, the baseband processor 1s-20 and the RF processor 1s-10 may be called a transmitter, a receiver, a transceiver, or a communication unit.

[0339] The communication unit 1s-30 provides an interface for performing communication with other nodes within the network.

[0340] The memory 1s-40 stores data such as basic programs, application programs, and setting information for the operation of the main base station. In particular, the memory 1s-40 may store the information on the bearer allocated to the accessed terminal, the measured results reported from the accessed terminal, etc. The memory 1s-40 may store information that is a determination criterion on whether to provide a multiple connection to the terminal or stop the multiple connection to the terminal. Further, the memory 1s-40 provides the stored data according to the request of the controller 1s-50.

[0341] The controller 1s-50 controls the general operations of the main base station. The controller 1s-50 transmits/receives a signal through the baseband processor 1s-20 and the RF processor 1s-10 or the communication unit 1s-30. Further, the controller 1s-50 records and reads data in and from the memory 1s-40. For this purpose, the controller 1s-50 may include at least one processor and/or a multiple connection processor 1s-52 controlling connections between multiple nodes.

[0342] FIG. 2A is a diagram of an LTE system, according to an embodiment of the present disclosure.

[0343] As illustrated in FIG. 1A, a RAT of an LTE system is configured to include next generation base stations (ENB, Node B, or base station) 2a-05, 2a-10, 2a-15, and 2a-20, an MME 2a-25, and a S-GW 2a-30. UE or terminal 2a-35 accesses an external network through the ENBs 2a-05 to 2a-20 and the S-GW 2a-30.

[0344] The ENBs 2a-05 to 2a-20 correspond to the existing node B of the UMTS system. The ENB is connected to the UE 2a-35 through a radio channel and performs more complicated role than the existing node B. In the LTE system, in addition to a real-time service like a VoIP through the internet protocol, all the user traffics are served through a shared channel and therefore an apparatus for collecting and scheduling status information such as a buffer status, an available transmission power status, and a channel state of the terminals is required. The ENBs 2a-05 to 2a-20 take charge of the collecting and scheduling status information. One ENB generally controls a plurality of cells. For example, to implement a transmission rate of 100 Mbps, the LTE system uses, as a RAT, OFDM in, for example, a bandwidth of 20 MHz. Further, an AMC scheme for determining a modulation scheme and a channel coding rate depending on a channel status of the terminal is applied. The S-GW 2a-30 is an apparatus for providing a data bearer and generates or removes the data bearer according to the control of the MME 2a-25. The MME is an apparatus for performing a mobility management function for the terminal and various control functions and is connected to a plurality of base station.

[0345] FIG. 2B is a diagram of a radio protocol structure in the LTE system.

[0346] The radio protocol of the LTE system is configured to include PDCPs 2b-05 and 2b-40, RLCs 2b-10 and 2b-35, and medium access controls (MACs 2b-15 and 2b-30 in the terminal and the ENB, respectively. The PDCPs 2b-05 and 2b-40 control operations such as IP header compression/decompression. The main functions of the PDCP are summarized as follows.

[0347] Header compression and decompression function (Header compression and decompression: ROHC only)

[0348] Transfer of user data

[0349] In-sequence delivery function (In-sequence delivery of upper layer PDUs at PDCP re-establishment procedure for RLC AM)

[0350] Reordering function (For split bearers in DC (only support for RLC AM): PDCP PDU routing for transmission and PDCP PDU reordering for reception)

[0351] Duplicate detection function (Duplicate detection of lower layer SDUs at PDCP re-establishment procedure for RLC AM)

[0352] Retransmission function (Retransmission of PDCP SDUs at HO and, for split bearers in DC, of PDCP PDUs at PDCP data-recovery procedure, for RLC AM)

[0353] Ciphering and deciphering function (Ciphering and deciphering)

[0354] Timer-based SDU discard function (Timer-based SDU discard in uplink)

[0355] The RLCs 2b-10 and 2b-35 reconfigures the PDCP PDU to an appropriate size to perform the ARQ operation or the like. The main functions of the RLC are summarized as follows.

[0356] Data transfer function (Transfer of upper layer PDUs)

[0357] ARQ function (Error Correction through ARQ (only for AM data transfer))

[0358] Concatenation, segmentation, reassembly functions (Concatenation, segmentation and reassembly of RLC SDUs (only for UM and AM data transfer))

[0359] Re-segmentation function (Re-segmentation of RLC data PDUs (only for AM data transfer))

[0360] Reordering function (Reordering of RLC data PDUs (only for UM and AM data transfer))

[0361] Duplicate detection function (Duplicate detection (only for UM and AM data transfer))

[0362] Error detection function (Protocol error detection (only for AM data transfer))

[0363] RLC SDU discard function (RLC SDU discard (only for UM and AM data transfer))

[0364] RLC re-establishment function (RLC re-establishment)

[0365] The MACs 2b-15 and 2b-30 are connected to several RLC layer apparatuses configured in one terminal and perform multiplexing RLC PDUs into an MAC PDU and demultiplexing the RLC PDUs from the MAC PDU. The main functions of the MAC are summarized as follows.

[0366] Mapping function (Mapping between logical channels and transport channels)

[0367] Multiplexing/demultiplexing function (Multiplexing/demultiplexing of MAC SDUs belonging to one or different logical channels into/from TBs delivered to/from the physical layer on transport channels)

[0368] Scheduling information reporting function (Scheduling information reporting)

[0369] HARQ function (Error correction through HARQ)

[0370] Priority handling function between logical channels (Priority handling between logical channels of one UE)

[0371] Priority handling function between terminals (Priority handling between UEs by means of dynamic scheduling)

[0372] MBMS service identification function (MBMS service identification)

[0373] Transport format selection function (Transport format selection)

[0374] Padding function (Padding)

[0375] Physical layers 2b-20 and 2b-25 perform channel-coding and modulating higher layer data, making the higher layer data as an OFDM symbol and transmitting them to a radio channel, or demodulating and channel-decoding the OFDM symbol received through the radio channel and transmitting the demodulated and channel-decoded OFDM symbol to the higher layer.

[0376] FIG. 2C is a diagram of a next generation mobile communication system, according to an embodiment of the present disclosure.

[0377] A RAN of a next generation mobile communication system (hereinafter referred to as NR or 5G) is configured to include a next generation base station (NR node B, hereinafter NR gNB or NR base station) 2c-10 and an NR CN 2c-05. The user terminal (NR UE or UE) 8c-15 accesses the external network through the NR gNB 2c-10 and the NR CN 2c-05.

[0378] In FIG. 2C, the NR gNB 2c-10 corresponds to an eNB of the existing LTE system. The NR gNB is connected to the NR UE 2c-15 via a radio channel and may provide a service superior to the existing node B. In the next generation mobile communication system, since all user traffics are served through a shared channel, an apparatus for collecting state information such as a buffer state, an available transmission power state, and a channel state of the UEs to perform scheduling is required. The NR NB 2c-10 may serve as the device. One NR gNB generally controls a plurality of cells. In order to realize high-speed data transmission compared with the current LTE, the NR gNB may have an existing maximum bandwidth or more, and may be additionally incorporated into a beam-forming technology may be applied by using OFDM as a RAT. An AMC scheme for determining a modulation scheme and a channel coding rate depending on a channel status of the terminal is applied. The NR CN 2c-05 may perform functions such as mobility support, bearer setup, QoS setup, and the like. The NR CN is a device for performing a mobility management function for the terminal and various control functions and is connected to a plurality of base stations. In addition, the next generation mobile communication system can interwork with the existing LTE system, and the NR CN is connected to the MME 2c-25 through the network interface. The MME is connected to the eNB 2c-30 which is the existing base station.

[0379] FIG. 2D is a diagram of a radio protocol structure of a next generation mobile communication system, according to an embodiment of the present disclosure.

[0380] The radio protocol of the next generation mobile communication system is configured to include NR PDCPs 2d-05 and 2d-40, NR RLCs 2d-10 and 2d-35, and NR MACs 2d-15 and 2d-30 in the terminal and the NR base station. The main functions of the NR PDCPs 2d-05 and 2d-40 may include some of the following functions.

[0381] Header compression and decompression function (Header compression and decompression: ROHC only)

[0382] Transfer of user data

[0383] In-sequence delivery function (In-sequence delivery of upper layer PDUs)

[0384] Reordering function (PDCP PDU reordering for reception)

[0385] Duplicate detection function (Duplicate detection of lower layer SDUs)

[0386] Retransmission function (Retransmission of PDCP SDUs)

[0387] Ciphering and deciphering function (Ciphering and deciphering)

[0388] Timer-based SDU discard function (Timer-based SDU discard in uplink)

[0389] In this case, the reordering function of the NR PDCP apparatus is for rearranging PDCP PDUs received in a lower layer in order based on a PDCP SN and may include a function of transferring data to a higher layer in the rearranged order, a function of recording PDCP PDUs lost by the reordering, a function of reporting a state of the lost PDCP PDUs to a transmitting side, and a function of requesting a retransmission of the lost PDCP PDUs.

[0390] The main functions of the NR RLCs 2d-10 and 2d-35 may include some of the following functions.

[0391] Data transfer function (Transfer of upper layer PDUs)

[0392] In-sequence delivery function (In-sequence delivery of upper layer PDUs)

[0393] Out-of-sequence delivery function (Out-of-sequence delivery of upper layer PDUs)

[0394] ARQ function (Error correction through HARQ)

[0395] Concatenation, segmentation, reassembly function (Concatenation, segmentation and reassembly of RLC SDUs)

[0396] Re-segmentation function (Re-segmentation of RLC data PDUs)

[0397] Reordering function (Reordering of RLC data PDUs)

[0398] Duplicate detection function (Duplicate detection)

[0399] Error detection function (Protocol error detection)

[0400] RLC SDU discard function (RLC SDU discard)

[0401] RLC re-establishment function (RLC re-establishment)

[0402] In the above description, the in-sequence delivery function of the NR RLC apparatus is for delivering RLC SDUs received from a lower layer to a higher layer in order, and may include a function of reassembling and transferring an original one RLC SDU which is divided into a plurality of RLC SDUs and received, a function of rearranging the received RLC PDUs based on the RLC SN or the PDCP SN, a function of recording the RLC PDUs lost by the reordering, a function of reporting a state of the lost RLC PDUs to the transmitting side, a function of requesting a retransmission of the lost RLC PDUs, a function of transferring only the SLC SDUs before the lost RLC SDU to the higher layer in order when there is the lost RLC SDU, a function of transferring all the received RLC SDUs to the higher layer before a predetermined timer starts if the timer expires even if there is the lost RLC SDU, or a function of transferring all the RLC SDUs received to the higher layer if the predetermined timer expires even if there is the lost RLC SDU.

[0403] The out-of-sequence delivery function of the NR RLC apparatus is for directly delivering the RLC SDUs received from the lower layer to the higher layer regardless of order, and may include a function of reassembling and transferring an original one RLC SDU which is divided into several RLC SDUs and received, and a function of storing the RLC SN or the PDCP SP of the received RLC PDUs and arranging it in order to record the lost RLC PDUs.

[0404] The NR MACs 2d-15 and 2d-30 may be connected to several NR RLC layer apparatuses configured in one terminal, and the main functions of the NR MAC may include some of the following functions.

[0405] Mapping function (Mapping between logical channels and transport channels)

[0406] Multiplexing and demultiplexing function (Multiplexing/demultiplexing of MAC SDUs)

[0407] Scheduling information reporting function (Scheduling information reporting)

[0408] HARQ function (Error correction through HARQ)

[0409] Priority handling function between logical channels (Priority handling between logical channels of one UE)

[0410] Priority handling function between terminals (Priority handling between UEs by means of dynamic scheduling)

[0411] MBMS service identification function (MBMS service identification)

[0412] Transport format selection function (Transport format selection)

[0413] Padding function (Padding)

[0414] The NR PHY layers 2d-20 and 2d-25 may perform an operation of channel-coding and modulating higher layer data, making the higher layer data as an OFDM symbol and transmitting them to a radio channel, or demodulating and channel-decoding the OFDM symbol received through the radio channel and transmitting the demodulated and channel-decoded OFDM symbol to the higher layer.

[0415] FIGS. 2EA and 2EB are diagrams of the terminal that receives services through an LTE base station and an NR base station in the next generation mobile communication system, according to an embodiment of the present disclosure.

[0416] In FIGS. 2EA and 2EB, 2e-01 shows that the terminal is served from the NR base station, 2e-02 shows that the LTE base station is the master (MeNB) in the 3C type LTE base station-NR base station interworking, 2e-03 shows that the NR base station is the master (MeNB) in the 3C type LTE base station-NR base station interworking, 2e-04 shows that the NR base station is the master (MeNB) in the 3C type NR base station-NR base station interworking, 2e-05 shows a 2a type LTE-base station-NR base station interworking, and 2e-06 shows a 2a type NR base station-NR base station interworking.

[0417] FIG. 2F is a diagram of a method for processing a data packet in advance, according to an embodiment of the present disclosure.

[0418] In 2e-01, 2e-02, 2e-03, 2e-04, 2e-05, and 2e-06 of FIGS. 2EA and 2EB, when receiving the IP packet 2f-05 from a higher layer on a user plane layer, the NR base station or the terminal of the next generation mobile communication systems may process the received package in advance. The processing refers to processing the IP packet to the PDCP PDU 2f-10 of the PDCP layer, the RLC PDU 2f-15 of the RLC layer, or the MAC SDU 2f-20 together with the MAC subheader of the MAC layer in advance.

[0419] FIG. 2G is a diagram illustrating problems that may occur by a timer (e.g., PDCP discard timer) maintained at a PDCP layer.

[0420] In FIG. 2G, when the IP packets are received by the PDCP layer, the PDCP layer may maintain one timer for each IP packet. The timer may represent the expiration date of the corresponding packet, and if the timer expires, the corresponding packet is discarded since the expiration date of the packet expires. For example, it is assumed that the timer for the IP packet 4 expires. If the IP packet 4 is processed in the PDCP layer 2g-05 in advance to be the PDCP PDU, since the expiration date of the corresponding IP packet has expired, the corresponding PDCP PDU should be discarded. Therefore, the PDCP SN 3 2g-15 is discarded. The PDCP layer of the receiving end may not know whether the discarded PDCP SN 3 is missed during the transmission or is discarded since the timer has expired. Therefore, the receiving end waits for the PDCP SN 3 to be retransmitted, thereby causing a transmission delay. If the IP packet 4 is processed in the PDCP layer in advance and transmitted to the RLC layer 2g-20 and processed in the RLC layer in advance to be the RLC PDU 2g-25, the RLC PDU should be discarded. In this case, the RLC SN 3 is discarded. Therefore, the RLC layer of the receiving end may not know whether the RLC SN 3 is missed or discarded during the transmission and therefore continuously waits, such that the window stalling problem occurs and the normal RLC ARQ operation may not be performed. The problem may occur when the PDCP SN is reused in the RLC and the RLC SN is not used in the RLC layer, in other words, when only one SN is used during the whole data processing.

[0421] FIGS. 2HA, 2HB, and 2HC are diagrams of a 2-1-th packet that has expired, according to an embodiment of the present disclosure.

[0422] In FIGS. 2HA, 2HB, and 2HC, the 2-1-th expired packet processing method for the present disclosure may be divided into the operations of the PDCP layer, the RLC layer, and the MAC layer as follows.

[0423] Operation of PDCP Layer

[0424] In the PDCP layer, the timer is driven for each packet entering the PDCP layer. The timer may be a timer representing the expiration date of each timer, and each timer value may be indicated as the RRC message by the base station. If the timer has expired, the following operations are performed.

[0425] The timer has expired,

[0426] if the 1-1-th condition is satisfied, the 1-1-th method is performed,

[0427] if the 1-2-th condition is satisfied, the 1-2-th method is performed, and

[0428] if the 1-3-th condition is satisfied, the 1-3-th method is performed.

[0429] The 1-1-th condition is a case in which a packet corresponding to the expired timer is not yet processed in the PDCP layer and is stored in a packet or PDCP SDU 2h-11.

[0430] The 1-2-th condition is a case in which the packet corresponding to an expired timer is processed in the PDCP layer in advance and stored in the PDCP PDU and not yet transmitted to the RLC layer 2h-12.

[0431] The 1-3-th condition is a case in which the packet corresponding to an expired timer is processed in the PDCP layer in advance and stored in the PDCP PDU and transmitted to the RLC layer in advance 2h-13.

[0432] The 1-1-th method is a method for discarding a packet or a PDCP SDU stored in the PDCP layer 2h-16.

[0433] The 1-2-th method is a method for discarding the packet or the PDCP SDU stored in the PDCP layer, discarding only a payload of the PDCP PDU corresponding to the packet, and transmitting the PDCP header without discarding the PDCP header 2h-17, and only the PDCP header is transmitted to the RLC layer.

[0434] The 1-3-th method is a method for discarding a packet or a PDCP SDU stored in the PDCP layer and transmitting and notifying an indication of information on a packet having the expired timer to the RLC layer 2h-18.

[0435] Operation of RLC Layer

[0436] The RLC layer stores the PDCP PDUs received from the PDCP layer and may process the RLC PDUs in advance. If the RLC layer receives an indication of information on the expired packet from the PDCP layer, the RLC layer performs the following operations.

[0437] The RLC layer receives the indication of the information on the expired packet from the PDCP layer,

[0438] if the 2-1-th condition is satisfied, the 2-1-th method is performed,

[0439] if the 2-2-th condition is satisfied, the 2-2-th method is performed, and

[0440] if the 2-3-th condition is satisfied, the 2-3-th method is performed.

[0441] The 2-1-th condition is a case in which a packet corresponding to the expired timer is transmitted to the RLC layer, not yet processed, and stored in PDCP SDU (RLC SDU) 2h-21.

[0442] The 2-2 condition is a case in which the packet corresponding to an expired timer is transmitted to the RLC layer, processed in advance to be stored in the PDCP layer, and is not yet transmitted to the RLC layer 2h-22.

[0443] The 2-3 condition is a case in which the packet corresponding to an expired timer is transmitted to the RLC layer, processed in advance to be stored in the RLC layer, and is transmitted to the RLC layer in advance 2h-23.

[0444] The 2-1-th method is a method for discarding only the payload of the PDCP PDU (RLC SDU) stored in the RLC layer corresponding to the expired packet and transmitting the PDCP header without discarding the PDCP header 2h-26, attaching only the PDCP header to the RLC header and transmitting it to the MAC layer.

[0445] The 2-2-th method is a method for discarding only the payload of the PDCP PDU of the RLC SDU processed and stored in the RLC layer and transmitting the RLC header and the PDCP header without discarding the RLC header and the PDCP header 2h-27, and transmitting only the PDCP header and RLC header to the MAC layer.

[0446] The 2-3-th method is a method for discarding only the payload of the PDCP PDU of the RLC PDU processed in the RLC layer corresponding to the expired packet and stored in the retransmission buffer and not discarding the RLC header and the PDCP header 2h-28 and transmitting and notifying the indication of the information on the packet having the expired timer to the MAC layer 2h-28.

[0447] Operation of MAC layer

[0448] The MAC layer stores the RLC PDU received from the RLC layer and may perform the processing with the MAC subheader and the MAC PDU in advance. If the MAC layer receives an indication of information on the expired packet from the RLC layer, the RLC layer performs the following operations.

[0449] The MAC layer receives the indication of the information on the expired packet from the RLC layer,

[0450] if the 3-1-th condition is satisfied, the 3-1-th method is performed,

[0451] if the 3-2-th condition is satisfied, the 3-2-th method is performed, and

[0452] if the 3-3-th condition is satisfied, the 3-3-th method is performed.

[0453] The 3-1-th condition refers to a case in which a packet corresponding to the expired timer is transmitted to the MAC layer, not yet processed, and stored in RLC PDU (MAC SDU) 2h-31.

[0454] The 3-2 condition is a case in which the packet corresponding to the expired timer is transmitted to the MAC layer, processed in advance to be stored in the MAC subheader and the MAC SDU, and is not a part of the MAC PDU 2h-32.

[0455] The 3-3 condition is a case in which the packet corresponding to the expired timer is transmitted to the MAC layer, processed in advance to be stored in the MAC subheader and the MAC SDU, and is a part of the MAC PDU in advance 2h-33.

[0456] The 3-1-th method is a method for discarding only the payload of the PDCP PDU of the RLC SDU stored in the MAC layer corresponding to the expired packet and transmitting the PDCP header and the RLC header without discarding the PDCP header and the RLC header 2h-36, attaching only the MAC subheader to the PDCP header and the RLC header, and configured as the MAC PDU and transmitted.

[0457] The 3-2-th method is a method for discarding the MAC subheader and only the payload of the PDCP PDU of MAC SDU (RLC PDU) that are processed and stored in the MAC layer corresponding to the expired packet and transmitting the RLC header and the PDCP header without discarding the RLC header and the PDCP header 2h-37, and newly update the MAC subheader corresponding to the PDCP header and the RLC header, and configured as the MAC PDU and transmitted (for example, the L field of the MAC subheader should be updated if the payload part of the PDCP PDU of the MAC SDU is deleted).

[0458] The 3-3-th method does not perform the processing on the packet that is processed in the MAC layer in advance to be a part of the MAC PDU 2h-38.

[0459] The 2-1-th condition processes the expired packet for discarding only a part corresponding to the expired packet and transmitting only the headers when the expired packet is processed with the PDCP PDU, the RLC PDU, or the MAC subheader and the MAC SDU in advance, to solve the problem occurring in FIG. 2G. Since the header is transmitted by the method as described above, the missing of the SN does not occur in the PDCP layer or the RLC layer due to the expired packet. However, the overhead may be increased according to the size of the header during the transmission, and the overhead is insignificant at a high data rate. The 2-1-th condition for processing the expired packet may be applied to solve the problem that may likewise occur in 2e-01, 2e-02, 2e-03, 2e-04, 2e-05 and 2e-06 in FIGS. 2EA and 2EB.

[0460] When the 2-1-th condition for processing the expired packet is applied to the transmitting end, the operation at the receiving end is as follows.

[0461] When the MAC PDU is received at the receiving end, it is demultiplexed and transmitted to the RLC layer, and when the segmented segments are present, the RLC layer creates a complete RLC SDU (PDCP PDU) and transmits it to the PDCP layer. When the PDCP PDU is a header only packet, the PDCP layer updates the decoding related parameters (e.g., HFN (Hyper Frame Number), Next_PDCP_TX_SN, etc.) and does not perform a decoding process on the packet including only the headers (the reason is that there is no information to be transmitted to the higher layer because it is the header only information). If the PDCP PDU received by the PDCP layer is not a packet including only the header but a general data packet, the PDCP layer of the receiving end updates the parameters related to the decoding (e.g., HFN, Next_PDCP_TX_SN, etc.) and performs the decoding procedure on the data packet and performs the integrity verification if necessary.

[0462] FIGS. 2IA and 2IB are diagrams of a terminal to which the 2-1-th condition is applied, according to an embodiment of the present disclosure.

[0463] When a terminal proceeds to step 2i-10, if the PDCP discard timer on any packet expires in the PDCP layer at step 2i-05, the terminal 2i-01 proceeds to step 2i-10 to confirm the processing of the packet. If the 1-1-th condition is satisfied, the 1-1-th method is applied in the PDCP (at step 2i-15), if the 1-2-th condition is satisfied, the 1-2-th method is applied in the PDCP (at step 2i-20), if the 1-3-th condition is satisfied, the 1-3-th method is applied in the PDCP layer (at step 2i-25), if the 2-1-th condition is satisfied, the 2-1-th method is applied in the RLC layer (2i-30), if the 2-2-th condition is satisfied, the 2-2-th method is applied in the RLC layer (at step 2i-35), if the 2-3-th condition is satisfied, the 2-3-th method is applied in the RLC layer (at step 2i-40), if the 3-1-th condition is satisfied, the 3-1-th method is applied in the MAC layer (at step 2i-45), if the 3-2-th condition is satisfied, the 3-2-th method is applied in the MAC layer (at step 2i-50), and if the 3-3-th condition is satisfied, the 3-3-th method is applied in the MAC layer (at step 2i-55).

[0464] FIG. 2J is a flowchart of a method of a terminal of a receiving end when the 2-1-th condition is applied, according to an embodiment of the present disclosure.

[0465] When the receiving terminal receives the MAC PDU, it demultiplexes the MAC PDU and transmits the demultiplexed MAC PDU to the RLC layer, and when the segmented segments are present, the RLC layer creates a complete RLC SDU (PDCP PDU) and transmits it to the PDCP layer (at step 2j-05). When the PDCP layer receives the RLC SDU (PDCP PDU) from the RLC layer, it is confirmed whether the PDCP PDU is a header only packet (at step 2j-10). In the case of the header only packet, the decoding related parameters (e.g., HFN, Next_PDCP_TX_SN, etc.) are updated (at step 2j-15) and the decoding procedure on the packet including only the headers is not performed (at step 2j-20) (i.e., there is no information to be transmitted to the higher layer because it is the header only information). If the PDCP PDU received by the PDCP layer is not a packet including only the header but a general data packet, the PDCP layer of the receiving end updates the decoding related parameters (e.g., HFN, Next_PDCP_TX_SN, etc.) (at step 2j-25) and performs the decoding procedure on the data packet and performs the integrity verification if necessary (at step 2j-30).

[0466] FIGS. 2KA and 2KB show a 2-2-th packet that has expired, according to an embodiment of the present disclosure.

[0467] In FIGS. 2Ka and 2KB, the 2-2-th expired packet processing method may be divided into the operations of the PDCP layer and the RLC layer as follows.

[0468] Operation of PDCP Layer

[0469] In the PDCP layer, the timer is driven for each packet entering the PDCP layer. The timer may be a timer representing the expiration date of each timer, and each timer value may be indicated as the RRC message by the base station. If the timer has expired, the following operations are performed.

[0470] The timer has expired,

[0471] if the 1-1-th condition is satisfied, the 1-1-th method is performed,

[0472] if the 1-2-th condition is satisfied, the 1-2-th method is performed, and

[0473] if the 1-3-th condition is satisfied, the 1-3-th method is performed.

[0474] The 1-1-th condition is a case in which a packet corresponding to the expired timer is not yet processed in the PDCP layer and is stored in a packet or PDCP SDU 2k-11.

[0475] The 1-2-th condition is a case in which the packet corresponding to an expired timer is processed in the PDCP layer in advance and stored in the PDCP PDU and not yet transmitted to the RLC layer 2k-12.

[0476] The 1-3-th condition is a case in which the packet corresponding to an expired timer is processed in the PDCP layer in advance and stored in the PDCP PDU and transmitted to the RLC layer in advance 2k-13.

[0477] The 1-1-th method is a method for discarding a packet or a PDCP SDU stored in the PDCP layer 2k-16.

[0478] The 1-2-th method is a method for discarding a packet or a PDCP SDU stored in the PDCP layer and discarding a PDCP PDU corresponding to a packet 2k-17 (the PDCP header is also discarded).

[0479] The 1-3-th method is a method for discarding a packet or a PDCP SDU stored in the PDCP layer and transmitting and notifying an indication of information on a packet having the expired timer to the RLC layer 2k-18.

[0480] Operation of RLC layer

[0481] The RLC layer stores the PDCP PDUs received from the PDCP layer and may process the RLC PDUs in advance. If the RLC layer receives an indication of information on the expired packet from the PDCP layer, the RLC layer performs the following operations.

[0482] The RLC layer receives the indication of the information on the expired packet from the PDCP layer,

[0483] if the 2-1-th condition is satisfied, the 2-1-th method is performed, and

[0484] if the 2-2-th condition is satisfied, the 2-2-th method is performed.

[0485] The 2-1-th condition is a case in which a packet corresponding to the expired timer is transmitted to the RLC layer, not yet processed, and stored in PDCP SDU (RLC SDU) 2k-21.

[0486] The 2-2-th condition is a case in which the packet corresponding to an expired timer is transmitted to the RLC layer, processed in advance to be stored in the PDCP layer, and is not yet transmitted to the RLC layer 2k-22.

[0487] The 2-1-th condition described above is for discarding the PDCP PDU stored in the RLC layer corresponding to the expired packet 2k-26 (The PDCP header is also discarded).

[0488] The 2-2-th condition described above does not take any action on the RLC PDU stored in the RLC layer corresponding to the expired packet. At the time of discarding the RLC PDU, a problem may occur in the RLC ARQ of the receiving end.

[0489] The 2-2-th condition is for discarding the PDCP PDU corresponding to the expired packet when the expired packet has already been processed with the PDCP PDU or the RLC PDU and not discarding the RLC PDU, to solve the problem arising in FIG. 2G. Therefore, although the RLC ARQ problem can be prevented, the transmission delay may occur in the PDCP layer. However, since the case where the packet expires is rare, the effect of the transmission delay may be insignificant. The 2-2-th condition may be applied to solve the problem that may likewise occur even in 2e-01, 2e-02, 2e-03, 2e-04, 2e-05 and 2e-06 in FIGS. 2EA and 2EB.

[0490] FIG. 2L is a flowchart of a method of a terminal to which the 2-2-th condition is applied, according to an embodiment of the present disclosure.

[0491] When a terminal proceeds to step 2i-10, if the PDCP discard timer on any packet expires in the PDCP layer (at step 2l-05), the terminal proceeds to step 2l-10 to identify the processing of the packet. If the 1-1-th condition is satisfied, the 1-1-th method is applied in the PDCP layer (at step 2l-15), if 1-2-th condition is satisfied, the 1-2-th method is applied in the PDCP layer (at step 2l-20), if the 1-3-th condition is satisfied, the 1-3-th method is applied in the PDCP layer (at step 2l-25), if the 2-1-th condition is satisfied, the 2-1-th method is applied in the RLC layer (at step 2l-30), and if the 2-2-th condition is satisfied, the 2-2-th method is applied in the RLC layer (at step 2l-35).

[0492] FIG. 2M is a diagram of a PDCP control PDU for explaining a 2-3-th packet that has expired, according to an embodiment of the present disclosure.

[0493] FIG. 2M shows an example of a PDCP status report format of a PDCP control PDU using 18 bits as a PDCP SN. The PDCP SNs discarded due to the expiration of the timer are transferred from the transmitting end to the receiving end. The PDCP SN may have any bit and may be set in the base station by the RRC message. As in 2m-05, the header may have a D/C field, a PDU Type field, an R field, a first discarded SN (FDS) field, and a bitmap field. Some or all of these fields or another new field may be included or defined in the PDCP status report format. The D/C field has a length of 1 bit and can indicate a PDCP control PDU if it has a value of 0 and indicate a PDCP data PDU if it has a value of 1 as in Table 2-1.

[0494]

	TABLE 2-1
	D/C field	Description
	0	Control PDU
	1	Data PDU
	D/C field	Description

[0495] The PDU Type field may have a length of 3 bits, and each bit value may indicate different PDU types as follows. The PDU Type field may have a predetermined different length and may be defined differently to indicate a PDCP status report as in Table 2-2.

[0496]

	TABLE 2-2
	PDU type field	Description
	000	Tx PDCP status report
	001-111	Reserved

[0497] The FDS field may have a length equal to the PDCP SN, and may indicate a discarded first SN.

[0498] The bitmap field may have a predetermined length, and each bit may sequentially indicate whether to discard the SNs are discarded based on the SN of the FDS field.

[0499] The 2-3-th expired packet uses the PDCP status report to transmit the information on the packet discarded due to the expiration of the timer (PDCP discard timer). If the PDCP SNs 3, 4, 5, and 6 are discarded due to the expiration of the timer, the PDCP SNs 3, 4, 5, and 6 are discarded when the PDCP status report is sent to the PDCP control PDU and is indicated by the FDS field and the bitmap, and may be transmitted to the receiving side. The receiving side receives the PDCP status report, confirms the fact that the packets corresponding to the PDCP SNs 3, 4, 5 and 6 are not missed but discarded, and does not wait for the PDCP SNs 3, 4, 5 and 6, thereby preventing the transmission delay.

[0500] The PDCP status report transmitted in order to indicate the packet discarded due to the expiration may be transmitted according to a predetermined criterion. The predetermined conditions may be the following examples.

[0501] if the transmitting end transmits more than a predetermined number of PDCP SNs,

[0502] transmission if the predetermined period is satisfied, that is, at each predetermined period,

[0503] if the PDCP SN discarded due to the expiration is present,

[0504] if the PDCP SN discarded due to the expiration is present and the transmission resource is allocated,

[0505] if the retransmission is requested in the PDCP layer of the receiving end,

[0506] and/or other reasons.

[0507] The PDCP control PDU of the PDCP status report may be located at the header if necessary when the transmitting end configures the MAC PDU.

[0508] FIG. 2N is a flowchart of a method of setting, by a terminal, each layer apparatus in the next generation mobile communication systems of the present disclosure.

[0509] FIG. 2N also shows a method for setting a connection with a network in which a terminal transmits/receives data and configuring apparatuses of each layer.

[0510] If there is data to be transmitted, a terminal 2n-01 for which no connection is currently established performs an RRC connection establishment procedure with the LTE base station or the NR base station 2n-02. The terminal 2n-01 establishes uplink transmission synchronization with the base station 2n-02 through a random access procedure and transmits an RRCConnectionRequest message to the base station (at step 2n-05). The message includes establishmentCause for connection with an identifier of the terminal 2n-01.

[0511] The base station 2n-02 transmits an RRCConnectionSetup message to allow the terminal 2n-01 to set the RRC connection (at step 2n-10). The message may store RRC connection configuration information, setting information of each layer, and the like. In other words, it may include configuration information on the PHY or NR PHY apparatus, the MAC or NR MAC apparatus, the RLC or NR RLC apparatus, the PDCP or the NR PDCP apparatus, and the information instructing the setting for the specific functions among the functions (functions for each layer described in FIG. 2B or 2D) supported by the layer apparatuses. In addition, the message may include an indication as to whether to use the PDCP discard timer value to be used in the PDCP apparatus or the header-only packet, an indication as to whether the PDCP control PDU sends the information on the discarded packet due to the expiration of the timer to the PDCP status report, and the like. The RRC connection is also called a signaling radio bearer (SRB) and is used for transmission and reception of the RRC message that is a control message between the terminal 2n-01 and the base station 2n-02.

[0512] The terminal 2n-01 establishing the RRC connection transmits an RRCConnetionSetupComplete message to the base station 2n-02 (at step 2n-15). The base station 2n-02 transmits an RRCConnectionReconfiguration message to the terminal 2n-01 in order to set up a DRB (at step 2n-20). The configuration information of each layer and the like may be stored in the message. In other words, it may include configuration information on the PHY or NR PHY apparatus, the MAC or NR MAC apparatus, the RLC or NR RLC apparatus, the PDCP or the NR PDCP apparatus, and the information instructing the setting for the specific functions among the functions (functions for each layer described in FIG. 2B or 2D) supported by the layer apparatuses.

[0513] In addition, the message may include an indication as to whether to use the PDCP discard timer value to be used in the PDCP apparatus or the header-only packet, an indication as to whether the PDCP control PDU sends the information on the discarded packet due to the expiration of the timer to the PDCP status report, and the like. In addition, the message includes the configuration information of the DRB in which user data are processed, and the terminal 2n-01 applies the information to set the DRB and set the functions of each layer and transmits an RRCConnectionReconfigurationComplete message to the base station 2n-02 (at step 2n-25).

[0514] If the above procedure is completed, the terminal 2n-01 transmits and receives data to and from the base station 2n-02 (at step 2n-30). While transmitting and receiving data, the base station 2n-02 may again transmit the RRCConnectionReconfiguration message to the terminal 2n-01 (at step 2n-35), if necessary, and again set the configuration information of each layer of the terminal 2n-01.

[0515] In other words, it may include configuration information on the PHY or NR PHY apparatus, the MAC or NR MAC apparatus, the RLC or NR RLC apparatus, the PDCP or the NR PDCP apparatus, and the information instructing the setting for the specific functions among the functions (functions for each layer described in FIG. 2B or 2D) supported by the layer apparatuses.

[0516] In addition, the message may include an indication as to whether to use the PDCP discard timer value to be used in the PDCP apparatus or the header-only packet, an indication as to whether the PDCP control PDU sends the information on the discarded packet due to the expiration of the timer to the PDCP status report, and the like. The message may include the information for configuring the interworking between the LTE base station (or NR base station) and the NR base station. The information for setting the interworking between the LTE base station and the NR base station may include information indicating a 3C type or a 2a type, information on each layer apparatus according to each type, and the like. Upon completion of the setting of apparatuses of each layer according to the message, the terminal 2n-01 transmits an RRCConnectionReconfigurationComplete message to the base station 2n-02 (at step 2n-40).

[0517] In the above procedure, if the terminal 2n-01 receives the PDCP discard timer value by the RRCConnectionSetup message (at step 2n-10) or the RRCConnectionReconfiguration message (at steps 2n-20 and 2n-35), the terminal 2n-01 can set the value as a timer value for each packet in the PDCP layer. If the indicator for the header only packet is received in the above messages, the 2-1-th processing of the expired packet can be applied. If the indicator for the header only packet is not received, the 2-2-th processing of the expired packet can be applied, and if the PDCP control PDU receives an indication as to whether to transmit the information on the packet discarded due to the expiration of the timer to the PDCP status report, the 2-3-th processing of the expired packet can be applied. If the indication for the header only packet is received in the messages and the PDCP control PDU receives the indication as to whether to transmit the information on the packet discarded due to the expiration of the timer to the PCCP status report, both of the 2-2-th and 2-3-th processing of the expired packet can be applied.

[0518] FIG. 2O is a diagram of the terminal, according to an embodiment of the present disclosure.

[0519] Referring to FIG. 2O, the terminal includes an RF processor 2o-10, a baseband processor 2o-20, a memory 2o-30, and a controller 2o-40 including a multiple connection processor 2o-42.

[0520] The RF processor 2o-10 serves to transmit and receive a signal through a radio channel, such as band conversion and amplification of a signal. That is, the RF processor 2o-10 up-converts a baseband signal provided from the baseband processor 2o-20 into an RF band signal and then transmits the RF band signal through an antenna and down-converts the RF band signal received through the antenna into the baseband signal. The RF processor 2o-10 may include a transmitting filter, a receiving filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, or the like. FIG. 2O illustrates only one antenna but the terminal may include a plurality of antennas. Further, the RF processor 2o-10 may include a plurality of RF chains. Further, the RF processor 2o-10 may perform beamforming. The RF processor 2o-10 may adjust a phase and a size of each of the signals transmitted and received through a plurality of antennas or antenna elements. In addition, the RF processor 2o-10 may perform MIMO and may receive a plurality of layers when performing a MIMO operation. The RF processor 2o-10 may perform reception beam sweeping by appropriately configuring a plurality of antennas or antenna elements under the control of the controller or adjust a direction and a beam width of the reception beam so that the reception beam is resonated with the transmission beam.

[0521] The baseband processor 2o-20 performs a conversion function between a baseband signal and a bit string according to a physical layer standard of a system. When data is transmitted, the baseband processor 2o-20 generates complex symbols by coding and modulating a transmitted bit string. Further, when data is received, the baseband processor 2o-20 recovers the received bit string by demodulating and decoding the baseband signal provided from the RF processor 2o-10. According to the OFDM scheme, when data is transmitted, the baseband processor 2o-20 generates the complex symbols by coding and modulating the transmitting bit string, maps the complex symbols to sub-carriers, and then performs an IFFT operation and a CP insertion to construct the OFDM symbols. Further, when data is received, the baseband processor 2o-20 divides the baseband signal provided from the RF processor 2o-10 in an OFDM symbol unit and recovers the signals mapped to the sub-carriers by an FFT operation and then recovers the received bit string by the modulation and decoding.

[0522] The baseband processor 2o-20 and the RF processor 2o-10 transmit and receive a signal as described above. Therefore, the baseband processor 2o-20 and the RF processor 2o-10 may be called a transmitter, a receiver, a transceiver, or a communication unit. Further, at least one of the baseband processor 2o-20 and the RF processor 2o-10 may include a plurality of communication modules to support a plurality of different RATs. Further, at least one of the baseband processor 2o-20 and the RF processor 2o-10 may include different communication modules to process signals in different frequency bands. The different wireless access technologies may include an LTE network, an NR network, and the like. Further, different frequency bands may include an SHF (for example: 2.5 GHz, 5 GHz) band, a millimeter wave (for example: 60 GHz) band.

[0523] The memory 2o-30 stores data such as basic programs, application programs, and configuration information for the terminal. The memory 2o-30 provides the stored data according to the request of the controller 2o-40.

[0524] The controller 2o-40 controls the overall operations of the terminal. The controller 2o-40 transmits and receives a signal through the baseband processor 2o-20 and the RF processor 2o-10. The controller 2o-40 records and reads data in and from the memory 2o-40. The controller 2o-40 may include at least one processor, a CP performing a control for communication and an AP controlling an upper layer such as the application programs.

[0525] FIG. 2P is a diagram of a base station or a TRP in a wireless communication system, according to an embodiment of the present disclosure.

[0526] The base station is configured to include an RF processor 2p-10, a baseband processor 2p-20, a communication unit 2p-30, a memory 2p-40, and a controller 2p-50.

[0527] The RF processor 2p-10 serves to transmit and receive a signal through a radio channel, such as band conversion and amplification of a signal. The RF processor 2p-10 up-converts a baseband signal provided from the baseband processor 2p-20 into an RF band signal and then transmits the RF band signal through an antenna and down-converts the RF band signal received through the antenna into the baseband signal. The RF processor 2p-10 may include a transmitting filter, a receiving filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, or the like. FIG. 2P illustrates only one antenna but the RF processor 2p-10 may include a plurality of antennas. The RF processor 2p-10 may include a plurality of RF chains. The RF processor 2p-10 may perform beamforming. The RF processor 2p-10 may adjust a phase and a size of each of the signals transmitted/received through a plurality of antennas or antenna elements. The RF processor 2p-10 may perform a downward MIMO operation by transmitting one or more layers.

[0528] The baseband processor 2p-20 performs a conversion function between the baseband signal and the bit string according to the physical layer standard of the first RAT. When data is transmitted, the baseband processor 2p-20 generates complex symbols by coding and modulating a transmitted bit string. When data is received, the baseband processor 2p-20 recovers the received bit string by demodulating and decoding the baseband signal provided from the RF processor 2p-10. According to the OFDM scheme, when data is transmitted, the baseband processor 2p-20 generates the complex symbols by coding and modulating the transmitting bit string, maps the complex symbols to the sub-carriers, and then performs the IFFT operation and the CP insertion to construct the OFDM symbols. When data is received, the baseband processor 2p-20 divides the baseband signal provided from the RF processor 2p-10 in the OFDM symbol unit and recovers the signals mapped to the sub-carriers by the FFT operation and then recovers the receiving bit string by the modulation and decoding. The baseband processor 2p-20 and the RF processor 2p-10 transmit and receive a signal as described above. The baseband processor 2p-20 and the RF processor 2p-10 may be called a transmitter, a receiver, a transceiver, or a communication unit.

[0529] The communication unit 2p-30 provides an interface for performing communication with other nodes within the network.

[0530] The memory 2p-40 stores data such as basic programs, application programs, and setting information for the main base station. In particular, the memory 2p-40 may store the information on the bearer allocated to the accessed terminal, the measured results reported from the accessed terminal, etc. Further, the memory 2p-40 may store information that is a determination criterion on whether to provide a multiple connection to the terminal or stop the multiple connection to the terminal. Further, the memory 2p-40 provides the stored data according to the request of the controller 2p-50.

[0531] The controller 2p-50 controls the general operations of the main base station. The controller 2p-50 transmits and receives a signal through the baseband processor 2p-20 and the RF processor 2p-10 or the communication unit 2p-30. The controller 2p-50 records and reads data in and from the memory 2p-40. For this purpose, the controller 2p-50 may include at least one processor.

[0532] FIG. 3A is a diagram of a structure of an LTE system, in accordance with an embodiment of the present disclosure.

[0533] As illustrated in FIG. 1A, a RAN of an LTE system is configured to include next generation base stations (ENB, Node B, or base station) 3a-05, 3a-10, 3a-15, and 3a-20, an MME 3a-25, and a S-GW 3a-30. UE or terminal 3a-35 accesses an external network through the ENBs 3a-05 to 3a-20 and the S-GW 3a-30.

[0534] In FIG. 3A, the ENBs 3a-05 to 3a-20 correspond to the existing node B of the UMTS system. The ENB is connected to the UE 3a-35 through a radio channel and performs a more complicated role than the existing node B. In the LTE system, in addition to a real-time service like a VoIP through the internet protocol, all the user traffics are served through a shared channel and therefore an apparatus for collecting and scheduling status information such as a buffer status, an available transmission power status, and a channel state of the terminals is required. Here, the ENBs 3a-05 to 3a-20 control the collecting and scheduling of the buffer status information. One ENB generally controls a plurality of cells. For example, to implement a transmission rate of 100 Mbps, the LTE system uses, as RAT, OFDM in, for example, a bandwidth of 20 MHz. Further, an AMC scheme determining a modulation scheme and a channel coding rate depending on a channel status of the terminal is applied. The S-GW 3a-30 is an apparatus for providing a data bearer and generates or removes the data bearer according to the control of the MME 3a-25. The MME is an apparatus for performing a mobility management function for the terminal and various control functions and is connected to a plurality of base stations.

[0535] FIG. 3B is a diagram of a radio protocol structure in the LTE system, in accordance with an embodiment of the present disclosure.

[0536] Referring to FIG. 3B, the radio protocol of the LTE system is configured to include PDCPs 3b-05 and 3b-40, RLCs 3b-10 and 3b-35, and MACs 3b-15 and 3b-30 in the terminal and the ENB, respectively. The PDCPs 3b-05 and 3b-40 control operations such as IP header compression/decompression. The main functions of the PDCP are summarized as follows.

[0537] Header compression and decompression function (Header compression and decompression: ROHC only)

[0538] Transfer of user data

[0539] In-sequence delivery function (In-sequence delivery of upper layer PDUs at PDCP re-establishment procedure for RLC AM)

[0540] Reordering function (For split bearers in DC (only support for RLC AM): PDCP PDU routing for transmission and PDCP PDU reordering for reception)

[0541] Duplicate detection function (Duplicate detection of lower layer SDUs at PDCP re-establishment procedure for RLC AM)

[0542] Retransmission function (Retransmission of PDCP SDUs at HO and, for split bearers in DC, of PDCP PDUs at PDCP data-recovery procedure, for RLC AM)

[0543] Ciphering and deciphering function (Ciphering and deciphering)

[0544] Timer-based SDU discard function (Timer-based SDU discard in uplink)

[0545] The RLCs 3b-10 and 3b-35 reconfigure the PDCP PDU to an appropriate size to perform the ARQ operation or the like. The main functions of the RLC are summarized as follows.

[0546] Data transfer function (Transfer of upper layer PDUs)

[0547] ARQ function (Error Correction through ARQ (only for AM data transfer))

[0548] Concatenation, segmentation, reassembly functions (Concatenation, segmentation and reassembly of RLC SDUs (only for UM and AM data transfer))

[0549] Re-segmentation function (Re-segmentation of RLC data PDUs (only for AM data transfer))

[0550] Reordering function (Reordering of RLC data PDUs (only for UM and AM data transfer))

[0551] Duplicate detection function (Duplicate detection (only for UM and AM data transfer))

[0552] Error detection function (Protocol error detection (only for AM data transfer))

[0553] RLC SDU discard function (RLC SDU discard (only for UM and AM data transfer))

[0554] RLC re-establishment function (RLC re-establishment)

[0555] The MACs 3b-15 and 3b-30 are connected to several RLC layer apparatuses configured in one terminal and perform multiplexing RLC PDUs into an MAC PDU and demultiplexing the RLC PDUs from the MAC PDU. The main functions of the MAC are summarized as follows.

[0556] Mapping function (Mapping between logical channels and transport channels)

[0557] Multiplexing/demultiplexing function (Multiplexing/demultiplexing of MAC SDUs belonging to one or different logical channels into/from TBs delivered to/from the physical layer on transport channels)

[0558] Scheduling information reporting function (Scheduling information reporting)

[0559] HARQ function (Error correction through HARQ)

[0560] Priority handling function between logical channels (Priority handling between logical channels of one UE)

[0561] Priority handling function between terminals (Priority handling between UEs by means of dynamic scheduling)

[0562] MBMS service identification function (MBMS service identification)

[0563] Transport format selection function (Transport format selection)

[0564] Padding function (Padding)

[0565] Physical layers 3b-20 and 3b-25 perform channel-coding and modulating higher layer data, making the higher layer data as an OFDM symbol and transmitting them to a radio channel, or demodulating and channel-decoding the OFDM symbol received through the radio channel and transmitting the demodulated and channel-decoded OFDM symbol to the higher layer.

[0566] FIG. 3C is a diagram of a next generation mobile communication system, in accordance with an embodiment of the present disclosure.

[0567] Referring to FIG. 3C, a RAN of a next generation mobile communication system (e.g., NR or 5G) is configured to include a next generation base station (NR node B, NR gNB or NR base station) 3c-10 and an NR CN 3c-05. The user terminal (NR UE or UE) 3c-15 accesses the external network through the NR gNB 3c-10 and the NR CN 3c-05.

[0568] In FIG. 3C, the NR gNB 3c-10 corresponds to an eNB of the existing LTE system. The NR gNB is connected to the NR UE 3c-15 via a radio channel and may provide a service superior to the existing node B. In the next generation mobile communication system, since all user traffics are served through a shared channel, an apparatus for collecting state information such as a buffer state, an available transmission power state, and a channel state of the UEs to perform scheduling is required. The NR NB 3c-10 may serve as the device. One NR gNB generally controls a plurality of cells. In order to realize high-speed data transmission compared with the current LTE, the NR gNB may have an existing maximum bandwidth, and may be additionally incorporated into a beam-forming technology may be applied by using OFDM as a RAT. Further, an AMC scheme determining a modulation scheme and a channel coding rate depending on a channel status of the terminal is applied. The NR CN 3c-05 may perform functions such as mobility support, bearer setup, QoS setup, and the like. The NR CN is a device for performing a mobility management function for the terminal and various control functions and is connected to a plurality of base stations. In addition, the next generation mobile communication system can interwork with the existing LTE system, and the NR CN is connected to the MME 3c-25 through the network interface. The MME is connected to the eNB 3c-30 which is the existing base station.

[0569] FIG. 3D is a diagram of a radio protocol structure of a next generation mobile communication system, in accordance with an embodiment of the present disclosure.

[0570] Referring to FIG. 3D, the radio protocol of the next generation mobile communication system is configured to include NR PDCPs 3d-05 and 3d-40, NR RLCs 3d-10 and 3d-35, and NR MACs 3d-15 and 3d-30 in the terminal and the NR base station. The main functions of the NR PDCPs 3d-05 and 3d-40 may include some of the following functions.

[0571] Header compression and decompression function (Header compression and decompression: ROHC only)

[0572] Transfer of user data

[0573] In-sequence delivery function (In-sequence delivery of upper layer PDUs)

[0574] Reordering function (PDCP PDU reordering for reception)

[0575] Duplicate detection function (Duplicate detection of lower layer SDUs)

[0576] Retransmission function (Retransmission of PDCP SDUs)

[0577] Ciphering and deciphering function (Ciphering and deciphering)

[0578] Timer-based SDU discard function (Timer-based SDU discard in uplink)

[0579] In this case, the reordering function of the NR PDCP apparatus is for rearranging PDCP PDUs received in a lower layer in order based on a PDCP (SN and may include a function of transferring data to a higher layer in the rearranged order, a function of recording PDCP PDUs lost by the reordering, a function of reporting a state of the lost PDCP PDUs to a transmitting side, and a function of requesting a retransmission of the lost PDCP PDUs.

[0580] The main functions of the NR RLCs 3d-10 and 3d-35 may include some of the following functions.

[0581] Data transfer function (Transfer of upper layer PDUs)

[0582] In-sequence delivery function (In-sequence delivery of upper layer PDUs)

[0583] Out-of-sequence delivery function (Out-of-sequence delivery of upper layer PDUs)

[0584] ARQ function (Error correction through HARQ)

[0585] Concatenation, segmentation, reassembly function (Concatenation, segmentation and reassembly of RLC SDUs)

[0586] Re-segmentation function (Re-segmentation of RLC data PDUs)

[0587] Reordering function (Reordering of RLC data PDUs)

[0588] Duplicate detection function (Duplicate detection)

[0589] Error detection function (Protocol error detection)

[0590] RLC SDU discard function (RLC SDU discard)

[0591] RLC re-establishment function (RLC re-establishment)

[0592] In the above description, the in-sequence delivery function of the NR RLC apparatus is for of delivering RLC SDUs received from a lower layer to a higher layer in order, and may include a function of reassembling and transferring an original one RLC SDU which is divided into a plurality of RLC SDUs and received, a function of rearranging the received RLC PDUs based on the RLC SN or the PDCP SN, a function of recording the RLC PDUs lost by the reordering, a function of reporting a state of the lost RLC PDUs to the transmitting side, a function of requesting a retransmission of the lost RLC PDUs, a function of transferring only the SLC SDUs before the lost RLC SDU to the higher layer in order when there is the lost RLC SDU, a function of transferring all the received RLC SDUs to the higher layer before a predetermined timer starts if the timer expires even if there is the lost RLC SDU, or a function of transferring all the RLC SDUs received until now to the higher layer in order if the predetermined timer expires even if there is the lost RLC SDU.

[0593] In this case, the out-of-sequence delivery function of the NR RLC apparatus is for directly delivering the RLC SDUs received from the lower layer to the higher layer regardless of order, and may include a function of reassembling and transferring an original one RLC SDU which is divided into several RLC SDUs and received, and a function of storing the RLC SN or the PDCP SP of the received RLC PDUs and arranging it in order to record the lost RLC PDUs.

[0594] The NR MACs 3d-15 and 3d-30 may be connected to several NR RLC layer apparatus configured in one terminal, and the main functions of the NR MAC may include some of the following functions.

[0595] Mapping function (Mapping between logical channels and transport channels)

[0596] Multiplexing and demultiplexing function (Multiplexing/demultiplexing of MAC SDUs)

[0597] Scheduling information reporting function (Scheduling information reporting)

[0598] HARQ function (Error correction through HARQ)

[0599] Priority handling function between logical channels (Priority handling between logical channels of one UE)

[0600] Priority handling function between terminals (Priority handling between UEs by means of dynamic scheduling)

[0601] MBMS service identification function (MBMS service identification)

[0602] Transport format selection function (Transport format selection)

[0603] Padding function (Padding)

[0604] The NR PHY layers 3d-20 and 3d-25 may perform channel-coding and modulating higher layer data, making the higher layer data as an OFDM symbol and transmitting them to a radio channel, or demodulating and channel-decoding the OFDM symbol received through the radio channel and transmitting the demodulated and channel-decoded OFDM symbol to the higher layer.

[0605] Although not illustrated, RRC layers are present at an upper part of the PDCP layer of the terminal and the base station, and the RRC layer may receive and transmit connection and measurement related control messages for a RRC.

[0606] FIG. 3E is a diagram of a light connection concept, in accordance with an embodiment of the present disclosure.

[0607] In FIG. 3E, the light connection technology defines a new terminal mode in addition to the idle mode or the connected mode in order to reduce the signaling overhead due to the existing HO and paging transmission operation. The new terminal mode can be established as a light connected mode, an RRC Inactive mode or any other named modes. Hereinafter, for the terminal 3e-03 in the light connected mode, the UE context of the terminal is stored, the S1 connection is maintained, and the paging is triggered by the base station 3e-02 and 3e-04 or the MME. Therefore, since the terminal 3e-03 is recognized as the connected mode, if there is data to be transmitted to the terminal 3e-03, the MME 3e-01 does not first trigger the paging but immediately transmits the data to the base station. The base station 3e-02 and 3e-04 receiving the data forwards the paging to all base stations in a predetermined PA 3e-05, and all base stations transmit the paging.

[0608] The terminal 3e-03 and the network can reduce the battery consumption and signaling overhead of the terminal 3e-03 in consideration of the above-mentioned light connection features.

[0609] FIG. 3F is a diagram of a method for establishing a connection of a general terminal to a network so that the general terminal transmits/receives data, in accordance with an embodiment of the present disclosure.

[0610] When a UE (idle mode UE) 3f-01 that is not currently connected generates data to be transmitted, the UE 3f-01 performs an RRCConnectionSetup procedure with the base station 3f-02. The UE 3f-01 establishes uplink transmission synchronization with the base station 3f-02 through a RAP and transmits an RRCConnectionRequest message to the base station (at step 3f-05). The message includes establishmentCause of connection with the identifier of the UE 3f-01. The base station 3f-02 transmits an RRCConnectionSetup message to allow the UE 3f-01 to set the RRC connection (at step 3f-10). The RRCConnectionSetup message includes the RRC connection configuration information, etc. The RRC connection is also called a SRB and is used for transmission and reception of the RRC message that is a control message between the UE 3f-01 and the base station 3f-02. The UE 3f-01 establishing the RRC connection transmits an RRCConnetionSetupComplete message to the base station 3f-02 (at step 3f-15). The message includes a control message called a service request that that allows the UE 3f-01 to request a bearer setup for a predetermined service to an MME 3f-03. The base station 3f-02 transmits a service request message included in the RRCConnectionSetupComplete message to the MME 3f-03 (at step 3f-20) and the MME 3f-03 determines whether to provide the service the UE 3f-01 requests as the determination result, if the MME 3f-03 decides to provide the service that the UE 3f-01 requests, the MME 3f-03 transmits an initial context setup request message to the base station 3f-02 (at step 3f-25). The initial context setup request message may include information such as QoS information to be applied when setting up a DRB and security related information (e.g., security key, security algorithm) to be applied to the DRB. The base station 3f-02 exchanges a SecurityModeCommand message at step 3f-30 and a SecurityModeComplete message at step 3f-35 with the UE 3f-01 to establish security. When the security establishment is completed, the base station 3f-02 transmits an RRCConnectionReconfiguration message to the UE 3f-01 (at step 3f-40). The message includes the configuration information of the DRB in which user data are processed, and the UE 3f-01 applies the information to setup the DRB and transmits an RRCConnectionReconfigurationComplete message to the base station (at step 3f-45). The base station 3f-02 that completes the DRB setup with the UE 3f-01 transmits an initial context setup complete message to the MME 3f-03 (at step 3f-50) and the MME 3f-03 receiving the message exchanges an S1 bearer setup message and an S1 bearer setup response message with a S-GW 3f-04 to setup an S1 bearer (at steps 3f-55 and 3f-60). The S1 bearer is a data transmission connection established between the S-GW 3f-04 and the base station 3f-02 and corresponds to a DRB on a one-to-one basis. If all of the procedures are completed, the UE 3f-01 transmits and receives data to and from the base station 3f-02 through the S-GW 3f-04 (at steps 3f-65 and 3f-70). As described above, the normal data transmission procedure largely consists of three stages: RRCConnectionSetup, security setup, and DRB setup.

[0611] FIG. 3G is a diagram of a method of updating, by a general terminal, a tracking region, in accordance with an embodiment of the present disclosure.

[0612] In FIG. 3G, a UE 3g-01 may establish a tracking area for a predetermined reason (at step 3g-05). The tracking area may be indicated by a list of tracking area identifiers (IDs). The predetermined reason can be established in a procedure in which the terminal initially accesses the network, can be established when the tracking area is periodically updated, and can be established by other causes. The UE 3g-01 may establish the tracking area by receiving a tracking area update (TAU) accept message by an MME in the tracking area establishing procedure. The TAU accept message may be included in the RRC message, and may be transmitted to the terminal by being included in, for example, the DedicatedInfoNAS of the RRCConnectionReconfiguration message or DLInformationTransfer message. The base station (old eNB) 3g-03 may disconnect the UE 3g-01 for a predetermined reason (at step 3g-10). The predetermined reason may be that the inactive timer expires because there is no data transmission/reception between the UE 3g-01 and the network for a predetermined time. The UE 3g-01 returns to the idle mode and can move according to the movement of the user. The UE 3g-01 may out of the established tracking area due to the mobility (at step 3g-15), confirm the tracking area identifier from the system information of the current cell (at step 3g-20), and perform the TAU procedure (at step 3g-30). The UE 3g-01 may transmit the RRCConnectionRequest message to the base station 3g-03 in order to establish a connection to the new base station or the cell 3g-02 and to update the tracking area at step 3g-35. The RRC message may try to update the tracking area by mo (mobile originated)-signaling the RRC connection establishmentCause. The base station 3g-02 can send the RRCConnectionSetup message to the UE 3g-01 to allow the RRCConnectionSetup (at step 3g-40). In order to update the tracking area setup, the UE 3g-01 may transmit the TAU request message by including the TAU request message in the DedicatedInfoNAS of the RRCConnectionSetupComplete message (at step 3g-45). The base station 3g-02 may transmit the TAU request message to an MME 3g-04 to request the TAU (at step 3g-50). When receiving the TAU request message and accepting the TAU, the MME 3g-04 transmits the TAU accept message to the base station 3g-02 (at step 3g-55), and the base station 3g-02 transmits the TAU accept message to the UE 3g-01 by including the TAU accept message in the RRC message. The TAU accept message may include new tracking area information. The RRC message transmitted from the base station 3g-02 to the UE 3g-01 may be an RRCConnectionReconfiguration message or a DLInformationTransfer message.

[0613] FIG. 3H is a diagram of a method of a terminal and a base station for supporting a light connection in a next generation mobile communication system, in accordance with an embodiment of the present disclosure.

[0614] FIG. 3H illustrates the overall flow of a terminal (UE) 3h-01, an anchor eNB (base station) 3h-02, a new eNB 3h-03, and an MME 3h-04 so that the terminal 3h-01 and the base station 3h-02 performs the UE context (terminal context) and the SI bearer. The terminal 3h-01 in the RRC connected state performs data transmission/reception with the base station 3h-02. When the data transmission/reception stops, the base station 3h-02 drives a predetermined timer and if the data transmission/reception is not resumed until the timer expires (at step 3h-05), the base station 3h-02 considers releasing the RRC connection of the terminal 3h-01. The base station 3h-02 may release the RRC connection of the terminal 3h-01 according to a predetermined rule, store the UE context, allocate a Resume ID while transmitting a control message instructing the terminal 3h-01 to release the RRC connection, and allow the terminal 3h-01 to establish the paging area (PA) to which the mobility is reported during the light connected mode. In this case, it can be appreciated that the terminal 3h-01 should store the UE context due to the Resume ID allocation. Alternatively, the base station 3h-02 may send to the message a separate context retention indication that instructs the base station 3h-02 to operate the terminal 3h-01 in the light connected mode and to store the UE context (at step 3h-10). In addition, the control message may include a list of cells, or the like to which a procedure of using the stored context may be applied, when the base station 3h-02 tries to again setup the RRC connection within the period when the UE context is retained or the expiration date of the UE. The PA may be constructed and configured in the paging area identify of the PA or the list of cell identifiers (IDs). The base station 3h-02 releases the RRC connection of the terminal 3h-01 and then retains the UE context and the S1 bearer of the UE as they are (at step 3h-15). The S1 bearer is called an S1-control bearer used to transmit and receive the control message between the base station 3h-02 and an MME 3h-04 and an S1-user plane bearer used to transmit and receive user data between the base station 3h-02 and the S-GW 3h-04. By retaining the S1 bearer, it is possible to omit the procedure for S1 bearer setup when the terminal 3h-01 tries to setup an RRC connection in the same cell or in the same base station. If the expiration date expires, the base station 3h-02 may delete the UE context and release the S1 bearer. The terminal 3h-01 receiving the RRC connection release message in step 3h-10 is switched to the light connected mode.

[0615] The base station base station 3h-02 transmits a control message requesting a connection pause to the MME 3h-04 (at step 3h-20). The MME 3h-04 receiving the control message requests the S-GW to allow the MME 3h-04 to start the paging procedure without transmitting the downlink data to the base station when the downlink data for the terminal 3h-01 is generated, the S-GW is operated accordingly (at step 3h-35) or immediately transmits the downlink data to an anchor eNB 3h-03 when the downlink data for the terminal 3h-01 is generated, and the anchor eNB 3h-03 may generate the paging message and transmit the generated paging message to neighboring base stations. That is, the anchor eNB 3h-03 receiving the downlink data stores the data in the buffer and performs the paging procedure. The anchor eNB 3h-03 is named the base station 3h-02 that maintains the UE context and the S1-U bearer of the terminal.

[0616] The terminal 3h-01 receiving the RRC connection release message at step 3h-10 including the information indicating the context retention and the resume ID may release the RRC connection, drive the timer corresponding to the expiration date and record a valid cell list in the memory, maintain the currently terminal context in the memory without deleting the currently terminal context (at step 3h-25) and may be shifted to the light connected mode. In above description, the UE context is various information associated with the RRC connection of the terminal 3h-01 and includes SRB setup information, DRB setup information, security key information, etc. Hereinafter, for any reason, a necessity to setup the RRC connection may be generated (at step 3h-30). A terminal that has not been allocated the Resume ID or is not instructed to maintain the context during the previous RRC connection release initiates the general RRCConnectionSetup process described in FIG. 3F, but the light connected mode terminal which has been allocated the Resume ID during the previous RRC connection release may try the RRCConnectionResume process using the stored terminal context.

[0617] In above description, the light connected mode terminal may perform the general RRCConnectionSetup process (FIG. 3F) and perform the RRCConnectionResume process using the stored terminal context according to whether to support the light connection of the network. In the present disclosure, each base station or cell may transmit an indication as to whether or not each base station or cell supports the light connection by including the indication in the system information. The indication may be included in a second bloc of system information (Systeminformation 2), or may be included in blocks of other system information (Systeminformation 1 to 19). In the above description, supporting the light connection may mean that the corresponding base station 3h-02 or the corresponding cell may establish and support the following at steps 3h-50, 3h-55, 3h-60, 3h-65, 3h-70, 3h-75, 3h-80, 3h-85, and 3h-90. If the light connected mode terminal needs to establish the RRC connection, it reads the system information of the currently camped-on cell. If the system information does not include the indication that the base station 3h-02 or the cell supports light connection, the terminal 3h-01 can perform the general RRC connection establishment procedure described in FIG. 3F (at step 3h-45). However, if the system information includes the indication that the base station 3h-02 or the cell supports light connection, the terminal 3h-02 can perform an RRCConnectionResume process using the stored UE context (at step 3h-45). The RRCConnectionResume process using the stored UE context is as follows.

[0618] First, the terminal 3h-01 transmits a preamble in a message 1 to perform the RAP. If the resource allocation is possible according to the preamble received in the message 1, the base station 3h-02 allocates the corresponding uplink resource to the terminal 3h-01 in q message 2. The terminal 3h-01 transmits a Resume request message including the Resume ID received in step 3h-10 based on the received uplink resource information (at step 3h-50). The message may be a modified message of the RRCConnectionRequest message or a newly defined message (e.g., RRCConnectionResumeRequest). When the terminal 3h-01 in the light connected mode moves to camp on the cell of another base station by releasing the connection from the existing anchor eNB, e.g., base station 3h-02, (at step 3h-02), the new base station 3h-03 receives and confirms the Resume ID of the terminal, such that it can be appreciated from which base station the corresponding terminal receives a service previously. If the new base station 3h-03 successfully receives and confirms the Resume ID, it performs a procedure of retrieving the UE context from the existing base station 3h-02 (Context Retrieve Procedure at steps 3h-55 and 3h-60). The new base station 3h-03 may obtain the terminal context from the existing base station 3h-02 through the S1 or X2 interface. If the new base station 3h-03 receives the Resume ID but fails to successfully identify the terminal 3h-01 for predetermined reasons, the RRC connection establishment procedure may be sent to the terminal 3h-01 and may return to the general connection setup procedure described in FIG. 3F. That is, if the RRCConnectionSetup message is sent to the terminal 3h-01 and the terminal 3h-01 receives the message, the RRCConnectionSetup message may be sent to the base station 3h-02 to establish the connection. Alternatively, if the new base station 3h-03 receives the Resume ID but does not successfully identify the terminal 3h-01 (e.g., when fails to retrieve the UE context from the existing anchor eNB), the RRCConnectionRelease message or the RRCConnectionReject message is sent to the terminal 3h-01 to reject the connection of the terminal 3h-01 and the general RRCConnectionSetup procedure described in FIG. 2F may be tried from the beginning.

[0619] The new base station 3h-03 confirms the MAC-I based on the retrieved UE context (at step 3h-65). The MAC-I is a message authentication code calculated by the terminal 3h-01 for the control message by applying the security information of the restored UE context, that is, applying a security key and a security counter. The base station 3h-03 confirms the integrity of the message using the MAC-I of the message, a security key, a security counter stored in the context of the terminal 3h-01, or the like. The base station 3h-03 determines the establishment to be applied to the RRC connection of the terminal 3h-01 and transmits the RRCConnectionResume receiving the configuration information to the terminal 3h-01 (at step 3h-70). The RRCConnectionResume message may be a control message in which the reuse indicator indicating ‘RRC context reuse’ is included in the general RRC connection request message. The RRCConnectionResume message modified RRCConnectionSetup message receives various information related to the RRCConnectionSetup of the terminal like the RRCConnectionSetup message. When the terminal 3h-01 receives the normal RRCConnectionSetup message, the terminal 3h-01 establishes the RRC connection on the basis of the configuration information indicated in the RRC connection setup message, but when the terminal 3h-01 receives the RRCConnectionResume message, the terminal 3h-01 establishes (delta configuration) the RRC connection in consideration of both of the stored configuration information and the configuration information indicated in the control message.

[0620] In summary, the terminal 3h-01 determines the indicated configuration information as the delta information on the stored configuration information to determine the configuration information to be applied and updates the configuration information or the UE context. For example, if the modified RRCConnectionResume message includes the SRB configuration information, the SRB is configured by applying the indicated SRB configuration information, and if the SRB configuration information is not included in the RRCConnectionResume message, the SRB may be configured by applying the SRB configuration information stored in the UE context.

[0621] The terminal 3h-01 configures the RRC connection by applying the updated terminal and the configuration information and transmits the RRCConnectionResumeComplete message to the base station 3h-03 (at step 3h-75). The control message requesting the connection pause to the MME 3h-04 is transmitted and the S1 bearer is requested to be reestablished in a new base station (3h-80 and 3h-85). When receiving the message, the MME instructs the S-GW to reestablish the S1 bearer as a new base station and normally process data for the terminal 3h-01. When the process is completed, the terminal resumes data transmission/reception in the cell (at step 3h-90).

[0622] In the above procedure, if the terminal 3h-01 in the light connected mode does not greatly move by releasing the connection from the base station (anchor eNB) 3h-02, and thus if the camped-on cell (base station 3h-02) of the existing anchor eNB 3h-03 is made, the existing anchor eNB 3h-03 does not perform steps 3h-55 and 3h-60 but performs only the connection pause of the S1 bearer in place of steps 3h-80 and 3h-85 and refers to the Resume ID indicated in the message 3 to search for the UE context of the terminal and reestablish the connection by the method similar to the above procedures based on the same.

[0623] If the data transmission/reception stops, the base station 3h-02 drives a predetermined timer and if the data transmission/reception is not resumed until the timer expires (at step 3h-95), the base station 3h-02 considers releasing the RRC connection of the terminal 3h-02. The base station 3h-02 may release the RRC connection of the terminal 3h-01 according to a predetermined rule, store the UE context, allocate a Resume ID while transmitting a control message instructing the terminal 3h-01 to release the RRC connection, and allow the terminal 3h-01 to establish the PA to which the mobility is reported during the light connected mode (at step 3h-100). The terminal 3h-01 at step 3h-105 in the light connected mode performs a procedure of updating the paging area if the terminal 3h-01 at step 3h-105 is out of the established PA.

[0624] FIG. 3I is a diagram of a method for performing a paging area update (PAU) to a new base station by the light connected terminal, in accordance with an embodiment of the present disclosure.

[0625] In FIG. 3I, the terminal (UE) 3i-01 in the connection state with the anchor eNB 3i-03 receives the RRCConnectionRelease message from the anchor eNB 3i-03 (at step 3i-05). If there is no data transmission/reception for a predetermined period of time, the anchor eNB 3i-03 can transmit the RRCConnectionRelease message to the terminal 3i-01 to be established in the light connected mode. The RRC message may include the information on the resume ID and the PA for the light-connected terminal 3i-01. The information on the PA may indicate one or more PA identifiers (PA IDs) or a list of one or more cell identifiers (Cell IDs). The terminal 3i-01 receiving the RRC message 3i-03 3i-05 can go to the light connected mode or the RRC idle state. The anchor eNB 3i-03 may store the context information of the terminal 3i-01 and may maintain the S1 bearer (at steps 3i-10 and 3i-15). In addition, the anchor eNB 3i-03 can manage the mobility of the terminal 3i-01 instead of an MME 3i-04. That is, if the anchor eNB 3i-03 has the downlink data to be transmitted to the terminal, it can generate a paging message and send the generated paging message to the terminal 3i-01 through the PA.

[0626] The terminal 3i-01 may move to another new base station or cell (new eNB) 3i-02 in another PA (at step 3i-20). Each cell managed by the base stations uses the predetermined system information (SIB) to broadcast the PA information such as its own cell ID or a PA ID or whether the cell (base station) supports the light connection (for example, using the indication) (at step 3i-25). In step 3i-30, the terminal 3i-01 receives the system information of the camped-on cell and confirms whether the PA information or the cell supports light connection (at step 3i-30). When the indication indicating that the cell (or the base station) supports light connection is not included in the system information, the terminal 3i-01 may perform the general TAU procedure as shown in FIG. 3G. However, if the indication indicating that the cell (or the base station) supports light connection is included in the system information, the terminal 3i-01 can perform the method of FIG. 3I of updating the following paging area (at step 3i-35).

[0627] If the PA ID or the cell identifiers broadcast in the system information are not included in the PA information established the terminal in step 3i-05, it is determined that the terminal 3i-01 is out of the PA, and the RRCConnectionResumeRequest is transmitted to the base station 3i-02 of the currently camped-on cell to request the paging area update (at step 3i-40). The establishment cause for the PA updating request in the message is newly defined and may be included. Alternatively, it may include the indication to indicate that the request is for updating the paging area using the reserved 1 bit of the message. Also, the message includes at least one of the Resume ID, the MAC-I, and the establishment cause. The base station 3i-02 receiving the RRCConnectionResumeRequest message uses the Resume ID to know the anchor eNB 3i-03 that previously supports the terminal (at step 3i-45). Accordingly, the base station 3i-02 can request the context information of the terminal 3i-01 to the anchor eNB 3i-03 (at steps 3i-50 and 3i-55). The security establishment can be confirmed using the retrieved terminal context information. The above steps at 3i-50 and 3i-55 may be omitted if the terminal 3i-01 attempts the connection establishment to original anchor eNB 3i-03. The base station 3i-02 transmits an RRCConnectionResume message to the terminal 3i-01 in step to allow the terminal 3i-01 to establish the connection (at step 3i-60), and the terminal 3i-01 can transmit an RRCConnectionResumeComplete message to complete the connection setup (at step 3i-65). In the message, the terminal 3i-01 may transmit a message or an indicator for requesting paging area update to the base station 3i-02. The base station 3i-02 receiving the paging area update request can send a paging area update response in the RRC message and establish new PA information (at step 3i-70).

[0628] In the above description, the RRC message may be the RRConnectionRelease message or the RRCConnectionReconfiguration message and may be a newly defined RRC message. The base station 3i-02 can confirm the mobility, speed, traffic pattern, and the like of the terminal 3i-01 through the history information of the terminal 3i-01, and can establish a new PA of the terminal 3i-01 by reflecting the information (at step 3i-70). The history information may be received when a new base station exchanges messages with the anchor eNB 3i-03, and may include information such as the number of times, the period, and the time that the terminal performs the paging update at steps 3i-50, 3i-55. After the base station 3i-02 updates the PA of the terminal 3i-01, it updates the PA for the terminal 3i-01 of the anchor eNB 3i-03 (at step 3i-75). Since the anchor eNB 3i-03 is the base station that maintains the terminal context and the SI-U bearer of the terminal 3i-01 and the base station that manages the mobility of the terminal 3i-01, the paging area of the terminal should be updated. If the downlink data for the corresponding terminal reaches the anchor eNB 3i-03 in future, the anchor eNB 3i-03 managing the mobility of the terminal 3i-01 appropriately generates and transmits the paging message to each find the terminal 3i-01.

[0629] In the above procedure, if the mobility of the terminal 3i-01 is small and the connection to the base station 3i-03 that is connected previously is attempted, steps 3i-50, 3i-55, and 3i-75 are not performed and the procedure of updating the PA may be performed.

[0630] FIG. 3J is a diagram of a method for performing a PAU to a new base station by the light connected terminal, in accordance with an embodiment of the present disclosure.

[0631] In FIG. 3J, the terminal 3j-01 in the connection state with the anchor eNB 3j-03 receives the RRCConnectionRelease message from the anchor eNB 3j-03 (at step 3j-05). If there is no data transmission/reception for a predetermined period of time, the anchor eNB 3j-03 can transmit the RRCConnectionRelease message to the terminal 3j-01 to be established in the light connected mode. The RRC message may include the information on the resume ID and the PA for the light-connected terminal. The information on the PA may indicate one or more PA IDs or a list of one or more Cell IDs. The terminal 3j-01 receiving the RRC message at step 3j-05 can go to the light connected mode or the RRC idle state. The anchor eNB 3j-03 may store the context information of the terminal 3j-01 and may maintain the S1 bearer (at steps 3j-10 and 3j-15). In addition, the anchor eNB 3j-03 can manage the mobility of the terminal 3j-01 instead of N MME 3j-04. That is, if the anchor eNB 3j-03 has the downlink data to be transmitted to the terminal 3j-01, it can generate a paging message and send the generated paging message to the mobile station through the PA.

[0632] The terminal 3j-01 may move to another new base station or cell (eNB) 3j-02 in another PA (at step 3j-20). Each cell managed by the base stations uses the predetermined SIB to broadcast the PA information such as its own cell ID or a PA ID or whether the cell (base station) supports the light connection (for example, using the indication) (at step 3j-25). In step 3j-30, the terminal 3j-01 receives the system information of the camped-on cell and confirms whether the PA information or the cell supports light connection (at step 3j-30). When the indication indicating that the cell (or the base station) supports light connection is not included in the system information, the terminal 3j-01 may perform the general TAU procedure as shown in FIG. 3G. However, if the indication indicating that the cell (or the base station) supports light connection is included in the system information, the terminal 3j-01 can perform the method of FIG. 3J for updating the following PA (at step 3j-35).

[0633] If the PA ID or the cell identifiers broadcast in the system information are not included in the PA information established the terminal 3j-01 in step 3j-05, it is determined that the terminal 3j-01 is out of the PA, and the RRCConnectionResumeRequest is transmitted to the base station of the currently camped-on cell to request the PA update (at step 3j-40). The establishment cause for the paging area updating request in the message is newly defined and may be included. Alternatively, it may include the indication to indicate that the request is for updating the paging area using the reserved 1 bit of the message. Also, the message includes at least one of the Resume ID, the MAC-I, and the establishment cause. The base station receiving the RRCConnectionResumeRequest message uses the Resume ID to know the anchor eNB 3j-03 that previously supports the terminal 3j-01 (at step 3j-45). Accordingly, the new base station 3j-02 can request the context information of the terminal 3j-01 to the anchor eNB 3j-03 (at steps 3j-50 and 3j-55). The security establishment can be confirmed using the retrieved terminal context information. The above steps 3j-50 and 3j-55 may be omitted if the terminal 3j-01 attempts the connection establishment to original anchor eNB 3j-03. The base station 3j-02 can transmit a RRCConnectionResume message at step 3j-60 in order to receive the PA update request of the terminal 3j-01 in the message at step 3j-40 and permit the PA update message (at step 3j-60). The base station 3j-02 may include information on a new PA in response to the paging area update request in the message, and may include a new resume ID, and if necessary, the new resume ID may be transmitted to the terminal 3j-01 by being included in the RRCConnectionRelease message at step 3j-75.

[0634] The new base station 3j-02 can confirm the mobility, speed, traffic pattern, and the like of the terminal 3j-01 through the history information of the terminal 3j-01, and can establish a new paging area of the terminal 3j-01 by reflecting the information (3j-70). The history information may be received when a new base station 3j-02 exchanges messages with the anchor eNB 3j-03, and may include information such as the number of times, the period, and the time that the terminal 3j-01 performs the paging update procedure (3i-50, 55). After the new base station 3j-02 updates the paging area of the terminal 3j-01, it updates the paging area for the terminal of the anchor eNB 3j-03 (at step 3j-65). The terminal 3j-01 can transmit the RRCConnectionResumeComplete message to complete the connection establishment (at step 3j-70). If there is no data transmission/reception while the predetermined time elapses, the base station 3j-02 can send the RRCConnectionRelease message to establish the terminal 3j-01 to be in the light connected mode again (at step 3j-75). Since the anchor eNB 3j-03 is the base station 3j-01 that maintains the terminal 3j-01 context and the SI-U bearer of the terminal 3j-01 and the base station 3j-02 that manages the mobility of the terminal 3j-01, the paging area of the terminal 3j-01 should be updated. If the downlink data for the corresponding terminal 3j-01 reaches the anchor eNB 3j-03 in future, the anchor eNB 3j-03 managing the mobility of the terminal appropriately generates and transmits the paging message to each find the terminal 3j-01.

[0635] In the above procedure, if the mobility of the terminal 3j-01 is small and the connection to the base station 3j-03 that is connected previously is attempted, steps 3j-50, 3j-55, and 3j-65 are not performed and the method of FIG. 3J for updating the PA may be performed.

[0636] FIG. 3K is a diagram of a method for performing a PAU to a new base station by the light connected terminal, in accordance with an embodiment of the present disclosure.

[0637] In FIG. 3K, the terminal 3k-01 in the connection state with the anchor eNB 3k-03 receives the RRCConnectionRelease message from the anchor eNB (at step 3k-05). If there is no data transmission/reception for a predetermined period of time, the anchor eNB 3k-03 can transmit the RRCConnectionRelease message to the terminal 3k-01 to be established in the light connected mode. The RRC message may include the information on the resume ID and the PA for the light-connected terminal. The information on the PA may indicate one or more PA IDs or a list of one or more Cell IDs. The terminal 3k-01 receiving the RRC message at step 3k-05 can go to the light connected mode or the RRC idle state. The anchor eNB 3k-03 may store the context information of the terminal 3k-01 and may maintain the S1 bearer (at steps 3k-10 and 3k-15). In addition, the anchor eNB 3k-03 can manage the mobility of the terminal 3k-01 instead of an MME 3k-04. That is, if the anchor eNB 3k-03 has the downlink data to be transmitted to the terminal 3k-01, it can generate a paging message and send the generated paging message to the mobile station through the PA.

[0638] The terminal 3k-01 may move to another new base station or cell 3k-02 in another PA (at step 3k-20). Each cell managed by the base stations uses the predetermined SIB to broadcast the PA information such as its own cell ID or a PA ID or whether the cell (base station) supports the light connection (for example, using the indication) (at step 3k-25). In step 3k-30, the terminal 3k-01 receives the system information of the camped-on cell and confirms whether the PA information or the cell supports light connection (at step 3k-30). When the indication indicating that the cell (or the base station) supports light connection is not included in the system information, the terminal 3k-01 may perform the general TAU procedure as shown in FIG. 3G. However, if the indication indicating that the cell (or the base station) supports light connection is included in the system information, the terminal 3k-01 can perform the method of FIG. 3K for updating the PA (at step 3k-35).

[0639] If the PA ID or the cell identifiers broadcast in the system information are not included in the paging area information established the terminal in step 3k-05, it is determined that the terminal is out of the PA, and the RRCConnectionResumeRequest is transmitted to the base station of the currently camped-on cell to request the paging area update (at step 3k-40). The establishment cause for the PA updating request in the message is newly defined and may be included. Alternatively, it may include the indication to indicate that the request is for updating the PA using the reserved 1 bit of the message. Also, the message includes at least one of the Resume ID, the MAC-I, and the establishment cause. The base station receiving the RRCConnectionResumeRequest message uses the Resume ID to know the anchor eNB 3k-03 that previously supports the terminal 3k-01 (at step 3k-45). Accordingly, the new base station 3k-02 can request the context information of the terminal 3k-01 to the anchor eNB 3k-03 (at steps 3k-50 and 3k-55). The security establishment can be confirmed using the retrieved terminal context information. The steps of 3k-50 and 3k-55 may be omitted if the terminal 3k-01 attempts the connection establishment to original anchor eNB 3k-03. The base station 3k-02 can transmit the RRC message as the response to the PA update request in order to receive the PA update request of the terminal 3k-01 in the message at step 3k-40 and permit the PA update message (at step 3k-60). The base station 3k-02 may include information on a new PA as response to the paging area update request in the message, and may include a new resume ID. The RRC message may be a newly defined RRC message, an RRCConnectionRelease message, an RRCConnectionReconfiguration message, or an RRCConnectionResume message. The new base station 3k-02 can confirm the mobility, speed, traffic pattern, and the like of the terminal 3k-01 through the history information of the terminal, and can establish a new PA of the terminal 3k-01 by reflecting the information (at step 3k-60). The history information may be received when a new base station 3k-02 exchanges messages with the anchor eNB 3k-03, and may include information such as the number of times, the period, and the time that the terminal performs the paging update procedure (at step 3k-50, 3k-55). After the new base station 3k-02 updates the PA of the terminal 3k-01, it updates the paging area for the terminal 3k-01 of the anchor eNB 3k-03 (at step 3k-65). If there is no data transmission/reception while the predetermined time elapses, the base station 3k-02 may send the RRCConnectionRelease message and again establish the terminal in the light connected mode or may omit the message when using the RRCConnectionRelease message in step 3k-60. Since the anchor eNB 3k-03 is the base station 3k-03 that maintains the terminal context and the SI-U bearer of the terminal 3k-01 and the base station 3k-02 that manages the mobility of the terminal 3k-01, the PA of the terminal 3k-01 should be updated. If the downlink data for the corresponding terminal 3k-01 reaches the anchor eNB 3k-03 in future, the anchor eNB 3k-03 managing the mobility of the terminal 3k-01 appropriately generates and transmits the paging message to each find the terminal.

[0640] In the above procedure, if the mobility of the terminal 3k-01 is small and the connection to the base station (eNB) 3k-03 that is connected previously is attempted, steps 3k-50, 3k-55, 3k-65 are not performed and the method of FIG. 3K for updating the PA may be performed.

[0641] FIG. 3I is a flowchart of a method of a terminal when the light connected mode terminal establishes an RRC connection to the network, in accordance with an embodiment of the present disclosure.

[0642] In FIG. 31, the terminal in the connection state to the anchor eNB receives an RRC ConnectionRelease message from the anchor eNB (at step 3l-05). The anchor eNB may establish the terminal in the light connected mode if there is no data transmission/reception for the predetermined time. The terminal receiving the message is switched to the light connected mode (at step 3l-10). Also, the terminal receiving the RRCConnectionRelease message may go to the RRC idle state. The terminal is allocated the Resume ID through the RRCConnectionRelease message and establishes the PA information. In the above description, the PA may indicate one or more than two sets of cells, and may indicate one or two or more PA ID (at step 3l-05). The terminal may move to another PA of the existing anchor eNB or another base station. If it is necessary for the terminal to establish the RRCConnectionsetup to the network for a predetermined reason, the terminal performs a cell reselection procedure and searches for a suitable cell (at step 3l-15). If an appropriate cell is found in the cell reselection procedure, the cell is camped on and the system information is read (at step 3l-20). The terminal confirms whether the PA information or the camped-on cell in the system information supports light connection (at step 3l-25). If the cell does not support the light connection, the terminal performs the general RRC connection establishment procedure described in FIG. 3F (at step 3l-30). If the cell supports light connection, the terminal performs the RRCConnectionResume procedure based on the terminal context as described in FIG. 3H (at step 3l-35).

[0643] FIG. 3M is a flowchart of a method of the terminal when the light connected mode terminal performs the procedure of performing the paging area update, in accordance with an embodiment of the present disclosure.

[0644] In FIG. 3M, the terminal in the connection state to the anchor eNB receives an RRCConnectionRelease message from the anchor eNB (at step 3m-05). The anchor eNB may establish the terminal in the light connected mode if there is no data transmission/reception for the predetermined time. The terminal receiving the message is switched to the light connected mode (at step 3m-10). Also, the terminal receiving the RRCConnectionRelease message may go to the RRC idle state. The terminal is allocated the Resume ID through the RRCConnectionRelease message and establishes the PA information. In the above description, the PA may indicate one or more than two lists of cells, and may indicate one or two or more PA (at step 3m-05). The terminal may move to another PA of the existing anchor eNB or another base station. The terminal performs a cell reselection procedure to search for a suitable cell (at step 3m-15). If an appropriate cell is found in the cell reselection procedure, the cell is camped on and the system information is read (at step 3m-20). The terminal confirms the PA information in the system information, compares the confirmed PA information with the PA information established in step 3m-05, and then determines the PA as a different paging area if the terminal does not have the same PA information (at step 3m-25). If the PA information read from the system information is included in the PA information established in step 3m-05, the terminal determines that it is within the established paging area and continuously performs the cell reselection procedure without performing the PA update procedure (at step 3m-15). If it is determined that the terminal is currently in another PA, the process proceeds to step 3m-30 to check whether the currently camped-on cell supports the light connection in the system information. If the currently camped-on cell does not support the light connection, the terminal performs the general TAU procedure described in FIG. 3G (at step 3m-35), and if the currently camped-on cell supports the light conception, the methods described in FIGS. 3I, 3J, and 3K is performed (at step 3m-40).

[0645] FIG. 3N is a diagram of the terminal, in accordance with an embodiment of the present disclosure.

[0646] The terminal includes an RF processor 3n-10, a baseband processor 3n-20, a memory 3n-30, and a controller 3n-40 including a multiple connection processor 3n-42.

[0647] The RF processor 3n-10 serves to transmit and receive a signal through a radio channel, such as band conversion and amplification of a signal. That is, the RF processor 3n-10 up-converts a baseband signal provided from the baseband processor 3n-20 into an RF band signal and then transmits the RF band signal through an antenna and down-converts the RF band signal received through the antenna into the baseband signal. The RF processor 3n-10 may include a transmitting filter, a receiving filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, or the like. FIG. 3N illustrates only one antenna but the terminal may include a plurality of antennas. The RF processor 3n-10 may include a plurality of RF chains. Further, the RF processor 3n-10 may perform beamforming. The RF processor 3n-10 may adjust a phase and a size of each of the signals transmitted and received through a plurality of antennas or antenna elements. In addition, the RF processor 3n-10 may perform MIMO and may receive a plurality of layers when performing a MIMO operation. The RF processor 3n-10 may perform reception beam sweeping by appropriately configuring a plurality of antennas or antenna elements under the control of the controller or adjust a direction and a beam width of the reception beam so that the reception beam is resonated with the transmission beam.

[0648] The baseband processor 3n-20 performs a conversion function between a baseband signal and a bit string according to a physical layer standard of a system. When data are transmitted, the baseband processor 3n-20 generates complex symbols by coding and modulating a transmitted bit string. When data is received, the baseband processor 3n-20 recovers the received bit string by demodulating and decoding the baseband signal provided from the RF processor 3n-10. For example, according to the OFDM scheme, when data is transmitted, the baseband processor 3n-20 generates the complex symbols by coding and modulating the transmitting bit string, maps the complex symbols to sub-carriers, and then performs an IFFT operation and a CP insertion to construct the OFDM symbols. When data are received, the baseband processor 3n-20 divides the baseband signal provided from the RF processor 3n-10 in an OFDM symbol unit and recovers the signals mapped to the sub-carriers by an FFT operation and then recovers the received bit string by the modulation and decoding.

[0649] The baseband processor 3n-20 and the RF processor 3n-10 transmit and receive a signal as described above. Therefore, the baseband processor 3n-20 and the RF processor 3n-10 may be called a transmitter, a receiver, a transceiver, or a communication unit. At least one of the baseband processor 3n-20 and the RF processor 3n-10 may include a plurality of communication modules to support a plurality of different RATs. At least one of the baseband processor 3n-20 and the RF processor 3n-10 may include different communication modules to process signals in different frequency bands. The different wireless access technologies may include an LTE network, an NR network, and the like. Further, different frequency bands may include an SHF (for example: 2.5 GHz, 5 GHz) band, a millimeter wave (for example: 60 GHz) band.

[0650] The memory 3n-30 stores data such as basic programs, application programs, and configuration information for the terminal. Further, the memory 3n-30 provides the stored data according to the request of the controller 3n-40.

[0651] The controller 3n-40 controls the overall operations of the terminal. The controller 3n-40 transmits and receives a signal through the baseband processor 3n-20 and the RF processor 3n-10. The controller 3n-40 records and reads data in and from the memory 3n-40. The controller 3n-40 may include at least one processor, and may include a CP performing a control for communication and an AP controlling a higher layer such as the application programs.

[0652] FIG. 3O is a diagram of TRP in a wireless communication system, according to an embodiment of the present disclosure.

[0653] As illustrated in FIG. 3O, the base station is configured to include an RF processor 3o-10, a baseband processor 3o-20, a communication unit 3o-30, a memory 3o-40, and a controller 3o-50.

[0654] The RF processor 3o-10 serves to transmit and receive a signal through a radio channel, such as band conversion and amplification of a signal. That is, the RF processor 3o-10 up-converts a baseband signal provided from the baseband processor 3o-20 into an RF band signal and then transmits the RF band signal through an antenna and down-converts the RF band signal received through the antenna into the baseband signal. The RF processor 3o-10 may include a transmitting filter, a receiving filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, or the like. FIG. 3O illustrates only one antenna but the first access node may include a plurality of antennas. The RF processor 3o-10 may include a plurality of RF chains. Further, the RF processor 3o-10 may perform the beamforming. The RF processor 3o-10 may adjust a phase and a size of each of the signals transmitted/received through a plurality of antennas or antenna elements. The RF processor 3o-10 may perform a downward MIMO operation by transmitting one or more layers.

[0655] The baseband processor 3o-20 performs a conversion function between the baseband signal and the bit string according to the physical layer standard of the first RAT. When data are transmitted, the baseband processor 3o-20 generates complex symbols by coding and modulating a transmitted bit string. When data are received, the baseband processor 3o-20 recovers the received bit string by demodulating and decoding the baseband signal provided from the RF processor 3o-10. For example, according to the OFDM scheme, when data are transmitted, the baseband processor 3o-20 generates the complex symbols by coding and modulating the transmitting bit string, maps the complex symbols to the sub-carriers, and then performs the IFFT operation and the CP insertion to construct the OFDM symbols. When data are received, the baseband processor 3o-20 divides the baseband signal provided from the RF processor 3o-10 in the OFDM symbol unit and recovers the signals mapped to the sub-carriers by the FFT operation and then recovers the receiving bit string by the modulation and decoding. The baseband processor 3o-20 and the RF processor 3o-10 transmit and receive a signal as described above. Therefore, the baseband processor 3o-20 and the RF processor 3o-10 may be called a transmitter, a receiver, a transceiver, or a communication unit.

[0656] The communication unit 3o-30 provides an interface for performing communication with other nodes within the network.

[0657] The memory 3o-40 stores data such as basic programs, application programs, and setting information for the main base station. In particular, the memory 3o-40 may store the information on the bearer allocated to the accessed terminal, the measured results reported from the accessed terminal, etc. The memory 3o-40 may store information that is a determination criterion on whether to provide a multiple connection to the terminal or stop the multiple connection to the terminal. The memory 3o-40 provides the stored data according to the request of the controller 3o-50.

[0658] The controller 3o-50 controls the general operations of the main base station. The controller 3o-50 transmits/receives a signal through the baseband processor 3o-20 and the RF processor 3o-10 or the communication unit 3o-30. Further, the controller 3o-50 records and reads data in and from the memory 3o-40. For this purpose, the controller 3o-50 may include at least one processor.

[0659] FIG. 4A is a diagram of the LTE system, in accordance with an embodiment of the present disclosure.

[0660] Referring to FIG. 4A, the wireless communication system is configured to include a plurality of base stations 4a-05, 4a-10, 4a-15, and 4a-20, an MME 4a-25, an S-GW 4a-30. UE or terminal 4a-35 accesses an external network through the base stations 4a-05, 4a-10, 4a-15, and 4a-20 and the S-GW 4a-30.

[0661] The base stations 4a-05, 4a-10, 4a-15, and 4a-20 are access nodes of a cellular network and provides a wireless access to terminals that are connected to a network. That is, in order to serve traffic of users, the base stations 4a-05, 4a-10, 4a-15, and 4a-20 collect state information such as a buffer state, an available transmission power state, a channel state, or the like of the terminals to perform scheduling, thereby supporting a connection between the terminals and a CN. The MME 4a-25 is an apparatus for performing various control functions as well as a mobility management function for the terminal 4a-35 and is connected to the plurality of base stations 4a-05, 4a-10, 4a-15, and 4a-20, and the S-GW 4a-30 is an apparatus for providing a data bearer. The MME 4a-25 and the S-GW 4a-30 may further perform authentication, bearer management, etc., on the terminal 4a-35 connected to the network and may process packets that are to be received from the base stations 4a-05, 4a-10, 4a-15, and 4a-20 and packets that are to be transmitted to the base stations 4a-05, 4a-10, 4a-15, and 4a-20.

[0662] FIG. 4B is a diagram of a radio protocol structure in an LTE system, in accordance with an embodiment of the present disclosure.

[0663] Referring to FIG. 4B, the radio protocol of the LTE system is configured to include PDCPs 4b-05 and 4b-40, RLCs 4b-10 and 4b-35, and MACs 4b-15 and 4b-30 in the terminal and the eNB, respectively. The PDCPs 4b-05 and 4b-40 control IP header compression/decompression. The main functions of the PDCP are summarized as follows.

[0664] Header compression and decompression function (Header compression and decompression: ROHC only)

[0665] Transfer function of user data (Transfer of user data)

[0666] In-sequence delivery function (In-sequence delivery of upper layer PDUs at PDCP re-establishment procedure for RLC AM)

[0667] Reordering function (For split bearers in DC (only support for RLC AM): PDCP PDU routing for transmission and PDCP PDU reordering for reception)

[0668] Duplicate detection function (Duplicate detection of lower layer SDUs at PDCP re-establishment procedure for RLC AM)

[0669] Retransmission function (Retransmission of PDCP SDUs at HO and, for split bearers in DC, of PDCP PDUs at PDCP data-recovery procedure, for RLC AM)

[0670] Ciphering and deciphering function (Ciphering and deciphering)

[0671] Timer-based SDU discard function (Timer-based SDU discard in uplink)

[0672] The RLCs 4b-10 and 4b-35 reconfigures the PDU to an appropriate size to perform the ARQ operation or the like. The main functions of the RLC are summarized as follows.

[0673] Data transfer function (Transfer of upper layer PDUs)

[0674] ARQ function (Error Correction through ARQ (only for AM data transfer))

[0675] Concatenation, segmentation, reassembly functions (Concatenation, segmentation and reassembly of RLC SDUs (only for UM and AM data transfer))

[0676] Re-segmentation function (Re-segmentation of RLC data PDUs (only for AM data transfer))

[0677] Reordering function (Reordering of RLC data PDUs (only for UM and AM data transfer)

[0678] Duplicate detection function (Duplicate detection (only for UM and AM data transfer))

[0679] Error detection function (Protocol error detection (only for AM data transfer))

[0680] RLC SDU discard function (RLC SDU discard (only for UM and AM data transfer))

[0681] RLC re-establishment function (RLC re-establishment)

[0682] The MACs 4b-15 and 4b-30 are connected to several RLC layer devices configured in one terminal and perform multiplexing RLC PDUs into an MAC PDU and demultiplexing the RLC PDUs from the MAC PDU. The main functions of the MAC are summarized as follows.

[0683] Mapping function (Mapping between logical channels and transport channels)

[0684] Multiplexing/demultiplexing function (Multiplexing/demultiplexing of MAC SDUs belonging to one or different logical channels into/from TBs delivered to/from the physical layer on transport channels)

[0685] Scheduling information reporting function (Scheduling information reporting)

[0686] HARQ function (Error correction through HARQ)

[0687] Priority handling function between Logical channels (Priority handling between logical channels of one UE)

[0688] Priority handling function between terminals (Priority handling between UEs by means of dynamic scheduling)

[0689] MBMS service identification function (MBMS service identification)

[0690] Transport format selection function (Transport format selection)

[0691] Padding function (Padding)

[0692] Physical layers 4b-20 and 4b-25 perform channel-coding and modulating higher layer data, making the higher layer data as an OFDM symbol and transmitting them to a radio channel, or demodulating and channel-decoding the OFDM symbol received through the radio channel and transmitting the demodulated and channel-decoded OFDM symbol to the higher layer.

[0693] Although not illustrated, RRC layers are present at an upper part of the PDCP layer of the terminal and the base station, and the RRC layer may receive and transmit connection and measurement related control messages for a RRC.

[0694] FIG. 4C is a diagram of a method of performing an HO in the existing LTE system, in accordance with an embodiment of the present disclosure.

[0695] The terminal (UE) 4c-01 in the connection mode state reports the cell measurement information to a source base station (source eNB) 4c-02 when the periodic or specific event is satisfied (at step 4c-05). Based on the measurement information, the source base station 4c-02 determines whether to perform an HO to neighboring cells. The HO is a technique for changing a source base station providing a service to a terminal in a connection mode to another base station. When the source base station 4c-02 determines the handover, the source base station 4c-02 sends an HO request message to a new base station, i.e., a target base station (target eNB) 4c-03 that services a service to the terminal 4c-01 to request the HO (at step 4c-10). If the target base station 4c-03 accepts the HO request, it transmits the HO request ACK message to the source base station 4c-02 (at step 4c-15). The source base 4c-02 station receiving the message transmits an HO command message to the terminal 4c-01 (at step 4c-20). The source base station 4c-02 transmits the HO command message to the terminal 4c-01 using the RRC ConnectionReconfiguration message (at step 4c-20). When the terminal 4c-01 receives the message, it stops transmitting/receiving data to/from the source base station 4c-02 and starts a T304 timer. If the terminal 4c-01 fails to succeed the HO to the target base station 4c-03 for a predetermined time, the T304 timer returns to the original establishment of the terminal 4c-01 and switches to the RRC Idle state. The source base station 4c-02 transmits a SN status for the uplink/downlink data and transmits it to the target base station 4c-03 if there is downlink data (at steps 4c-30, 4c-35). The terminal 4c-01 attempts random access to the target base station 4c-03 indicated by the source base station 4c-02 (at step 4c-40).

[0696] The random access is to fit an uplink synchronization simultaneously with notifying a target cell that the terminal 4c-01 moves through the HO. For the random access, the terminal 4c-01 transmits the preamble corresponding to the preamble ID received from the source base station 4c-02 or the randomly selected preamble ID to the target base station 4c-03. After a certain number of subframes have passed after the preamble is transmitted, the terminal 4c-01 monitors whether a random access response (RAR) is transmitted from the target base station 4c-03. The time period in which the monitoring is performed is referred to as an RAR window. If the RAR is received during the specific time (at step 4c-45), the terminal 4c-01 transmits an HO complete message to the target base station 4c-03 by including the HO compete message in an RRCConnectionReconfigurationComplete message (at step 4c-50). As described above, if the RAP from the target base station 4c-03 is successfully completed in the MAC, the terminal 4c-01 ends the T304 timer (at step 4c-55). The target base station 4c-03 requests the path modification to modify the path of the bearers established in the source base station 4c-02 (at steps 4c-60, 4c-65) and notifies the source base station 4c-02 that the UE context of the terminal 4c-01 is deleted. Accordingly, the terminal 4c-01 attempts to receive data from the RAR window starting time for the target base station 4c-03, and receives the RAR and then starts the transmission to the target base station 4c-03 while transmitting the RRCConnectionReconfigurationComplete message.

[0697] Referring to the HO procedure in the LTE system shown in FIG. 4C, the specific terminal may not transmit or receive its own data until the HO complete message (RRCConnectionReconfigurationComplete) is transmitted since the HO to the target base station 4c-03 is completed from the time when the HO command message (RRCConnectionReconfiguration) is received from a source base station 4c-02. This data transmission/reception disconnection state causes a certain time delay in transmitting/receiving data by the terminal. In the present disclosure, a RACH-less HO method that minimizes the data transmission interruption time is considered, and the corresponding terminal is specified. In the RACH-less HO method, when the terminal 4c-01 performs the HO from the source base station 4c-02 to the target base station 4c-03, the RRCConnectionReconfigurationComplete message is directly transmitted through the uplink resource previously allocated from the target base station 4c-03 without performing the RAP, thereby establishing the connection with the target base station 4c-03. The RACH-less HO may have various embodiments according to a specific operation procedure.

[0698] FIG. 4D is a diagram of a method for performing a RACH-less HO, in accordance with an embodiment of the present disclosure.

[0699] In FIG. 4D, the source base station 4d-02 may request to the terminal 4d-01 the UE capability information using a UECapabilityEnquiry message (at step 4d-05). The terminal 4d-01 can report whether to support RACH-less HO for each band or band combination to the source base station using the UECapabilityInformation message (at step 4d-10). If the source base station 4d-02 also supports the RACH-less HO for each band or band combination, the RACH-less HO may be used. The terminal 4c-01 in the connection mode state reports the cell measurement information to the source base station (source eNB) 4d-02 when the periodic or specific event is satisfied (at step 4d-15). Based on the measurement information, the source base station 4d-02 determines whether to perform an HO to neighboring cells. When the source base station 4d-02 determines the HO, the source base station 4d-02 sends an HO request message to a new base station, i.e., a target base station (target eNB) 4d-03 that services a service to the terminal 4d-01 to request the HO (at step 4c-20). The source base station 4d-02 additionally determines whether the target base station 4d-03 applies RACH-less HO to the terminal 4d-01 supporting the RACH-less HO, and then requests HO to the target base station 4d-03 (at step 4d-20). In addition, when the HO is requested, it may include an indication (Indication 1) indicating whether to apply the RACH-less HO. If the target base station 4d-03 accepts the HO request, it transmits the HO request ACK message to the source base station 4d-02 (at step 4c-25). The HO request Ack message includes the configuration information of a target base station 4d-03 necessary for handover. The configuration information may include an indication (indication 2) indicating that RACH-less HO is supported when the target base station 4d-03 supports the RACH-less HO and the information on an uplink transmission resource that can be used when the terminal 4d-01 sends an RRC message (RRConnectionReconfigurationComplete) to the target base station 4d-03. The source base station 4d-02 instructs the terminal 4d-01 to perform the HO to the target base station 4d-03 using the RRCConnectionReconfiguration message (at step 4d-30). At this time, the RRC message includes one indication (indication 2) indicating to perform the RACH-less HO, and the information on an uplink transmission resource that can be used when the terminal 4d-01 sends an RRC message (RRConnectionReconfigurationComplete) to the target base station 4d-03. When the terminal 4d-01 receives the message, it stops transmitting/receiving data to/from the source base station 4d-02 and starts the T304 timer (at step 4d-35). If the terminal 4d-01 fails the HO to the target base station 4d-03 for a predetermined time, the T304 timer returns to the original establishment of the terminal 4d-01 and switches to the RRC Idle state. The source base station 4d-02 transmits a SN status for the uplink/downlink data and transmits it to the target base station 4d-03 if there is downlink data (at steps 4d-40, 4d-45). In step 4d-30, when the terminal 4d-01 receives the indicator, it performs the RACH-less HO operation. That is, the terminal 4d-01 does not perform an RAP such as in steps 4c-40 and 4c-45 in FIG. 4C and transmits an RRC message (RRConnectionReconfigurationComplete) as the uplink resource of the target base station 4d-03 included in the RRC message (RRConnectionReconfiguration) at step 4d-30 to the target base station 4d-03, including the C-RNTI (Cell Radio Network Temporary Identifier) information (at step 4d-50). The target base station 4d-03 can forward msg4 for confirming the reception of the RRC message corresponding to the msg3 through the PDCCH (at step 4d-55). The msg4 PDCCH signal is transmitted to the C-RNTI received in msg3 and includes uplink resource information.

[0700] If the RRC message 4d-30 does not include an indication indicating to perform the RACH-less HO, the terminal 4d-01 performs an HO operation as shown in FIG. 4C (at step 4d-30). When the HO procedure is successfully completed as described above, the terminal 4d-01 ends the T304 timer (at step 4d-60). The target base station 4d-03 requests the path modification to modify the path of the bearers established in the source base station 4d-02 (at steps 4d-60, 4d-65) and notifies the source base station 4d-02 that the UE context of the terminal 4d-01 is deleted (at step 4d-70).

[0701] FIG. 4E is a diagram of a method for performing a RACH-less HO, in accordance with an embodiment of the present disclosure.

[0702] In FIG. 4D, the source base station 4e-02 may request to the terminal 4e-01 the UE capability information using a UECapabilityEnquiry message (at step 4e-05). The terminal 4e-01 can report whether to support RACH-less HO for each band or band combination to the source base station 4e-02 using the UECapabilityInformation message (at step 4e-10). If the source base station 4e-02 also supports the RACH-less HO for each band or band combination, the RACH-less HO may be used. The terminal 4e-01 in the connection mode state reports the cell measurement information to a source base station (source eNB) 4e-02 when the periodic or specific event is satisfied (at step 4e15). Based on the measurement information, the source base station 4e-02 determines whether to perform an HO to neighboring cells. When the source base station 4e-02 determines the HO, the source base station 4e-02 sends an HO request message to a new base station, i.e., a target base station (target eNB) 4e-03 that services a service to the terminal 4e-01 to request the HO (at step 4e-20). The source base station 4e-02 additionally determines whether the target base station 4e-03 applies RACH-less HO to the terminal 4e-01 supporting the RACH-less HO, and then requests HO to the target base station 4e-03 (at step 4e-20). In addition, when the HO is requested, it may include an indication (Indication 1) indicating whether to apply the RACH-less HO. If the target base station 4e-03 accepts the HO request, it transmits the HO request ACK message to the source base station 4e-02 (at step 4e-25). The HO request Ack message includes the configuration information of a target base station 4e-03 necessary for HO. The configuration information may include an indication (indication 2) that RACH-less HO is supported when the target base station 4e-03 supports the RACH-less HO. The source base station 4e-02 instructs the terminal 4e-01 to perform the HO to the target base station 4e-02 using the RRCConnectionReconfiguration message (at step 4e-30). At this time, the RRC message may include one indication (indication 2) indicating to perform the RACH-less HO. When the terminal 4e-01 receives the message, it stops transmitting/\receiving data to/from the source base station 4e-02 and starts the T304 timer (at step 4e-35). If the terminal 4e-01 fails to succeed the HO to the target base station 4e-03 for a predetermined time, the T304 timer returns to the original establishment of the terminal 4e-01 and switches to the RRC Idle state. The source base station 4e-01 transmits a SN status for the uplink/downlink data and transmits it to the target base station 4e-03 if there is downlink data (at steps 4e-40, 4e-45). In step 4e-30, when the terminal 4e-01 receives the indicator, it performs the RACH-less HO operation. That is, the terminal 4e-01 monitors uplink resource allocation information repeatedly transmitted from the target base station to the PDCCH without performing the RAP as shown at steps 4c-40 and 4c-45 in FIG. 4C. The target base station 4e-03 allocates fixed uplink resources to the terminal 4e-01 on the PDCCH so that the terminal 4e-01 can complete the HO procedure (at step 4e-50). In the above step, the target base station 4e-03 continues to transmit the fixed uplink resource allocation information on the PDCCH and then stops when receiving a response indicating that the uplink resource allocation information has been successfully received from the terminal 4e-01. When the terminal 4e-01 receives the uplink resource allocation, the terminal 4e-01 transmits a RRC message (RRConnectionReconfigurationComplete) corresponding to msg3 to the target base station 4e-03, including the C-RNTI (at step 4e-55). The target base station 4e-03 can forward msg4 for confirming the reception of the RRC message corresponding to the msg3 through the PDCCH (at step 4e-60). The present disclosure proposes two methods of transmitting the PDCCH signal (msg4).

[0703] Option 1: When the target base station 4e-03 successfully receives the RRC message (msg3), a method can include scheduling an uplink resource allocation (grant) having parameters different from an uplink resource allocation previously transmitted to the terminal.

[0704] Option 2: If the target base station 4e-03 successfully receives the RRC message (msg3), a method can include scheduling downlink resource allocation.

[0705] When Option 1 is used, there is a restriction that parameters should be set to be scheduled in the same physical resource block (PRB) when initial uplink resource allocation is performed in the target base station 4e-03. That is, the terminal 4e-01 should repeatedly transmit the same parameters continuously for the same resource allocation before the terminal 4e-01 receives the uplink resource. On the other hand, when the Option 2 is used, there is a degree of freedom in initial uplink resource allocation in the target base station 4e-03. That is, since the terminal 4e-01 can know that the HO operation is completed when receiving the downlink resource allocation in the PDCCH, the terminal 4e-01 can identify the uplink resource allocation by transmitting another uplink resource allocation from the target base station 4e-03. In addition, the terminal 4e-01 may include UE Contention Resolution Identity in the MAC control element (CE) upon the downlink transmission for clear operation.

[0706] If the RRC message at step 4e-30 does not include an indication indicating to perform the RACH-less HO, the terminal 4e-01 performs an HO operation as shown in FIG. 4C (at step 4e-30). When the HO procedure is successfully completed as described above, the terminal 4e-01 ends the T304 timer (at step 4e-65). The target base station 4e-03 requests the path modification to modify the path of the bearers established in the source base station 4e-02 (at steps 4e-70, 4e-75) and notifies the source base station 4e-02 that the UE context of the terminal 4e-01 is deleted (at step 4e-80).

[0707] FIG. 4F is a diagram of a PDCCH structure corresponding to mgs4, in accordance with an embodiment of the present disclosure.

[0708] In the first operation and the second operation of the present disclosure, RACH-less HO is premised, that is, the connection is established through the uplink resource previously allocated from the target base station by directly sending the RRCConnectionReconfigurationComplete message without performing the RAP when the terminal performs HO from the source base station to the target base station. The terminal can receive the reception acknowledgment of the RRC message corresponding to the msg3 on the PDCCH, and Option 1 and Option 2 for sending the msg4.

[0709] Option 1 has the same PDCCH structure as in the existing LTE, and the uplink resource grant has a value different from the uplink resource grant that was transmitted in the previous step. In Option 2, the PDCCH downlink resource allocation (grant) corresponding to the msg4 is transmitted to inform that the msg3 transmitted by the terminal is successfully received. If the terminal receives the acknowledgment message, the MS performs uplink transmission through uplink resource allocation previously transmitted by the base station. A MAC CE composed of UE contention resolution identity having a length of 6 bytes is transmitted to the MAC PDU of the PDCCH (4f-05). In addition, the RRCConnectionReconfigurationComplete message received in msg3 may be copied and used in the payload of the UE contention resolution identity configuration content (payload) of the MAC CE. The RRC message requires at least the following 3 bytes.

[0710] PDPC header (4f-10): 1 byte

[0711] RLC header (4f-15): 2 bytes

[0712] Payload: RRC transaction identifier (2 bits) (4f-20)+other bits needs for the extension containers (4f-25)

[0713] If the RRCConnectionReconfigurationComplete message cannot be completely represented by 6 bytes, the RRCConnectionReconfigurationComplete message may be composed of only 48 bits and the remaining bits may be discarded. The above operation is similar to the method of configuring the UE contention resolution identity MAC CE in the LTE, and can use existing methods. Alternatively, a new MAC CE having the same structure and purpose as the UE contention resolution identity MAC CE may be defined and used.

[0714] FIG. 4G is a flowchart of a method of a terminal for performing an RACH-less HO, in accordance with an embodiment of the present disclosure.

[0715] First, it is assumed that the terminal is connected to the source base station to transmit/receive data. The terminal in the connected mode may instruct the current source base station to perform the HO based on the measurement information and may receive the HO command from the target base station through the RRCConnectionReconfiguration message (at step 4g-02). The terminal receiving the HO message starts a T304 timer (at step 4g-05), performs an HO process, and stops if the HO procedure is completed (at steps 4g-40, 4g-70, 4g-90). The HO operation can be performed differently depending on whether the RRC message includes an indicator indicating the RACH-less HO to the target cell.

[0716] If there is no RACH-less HO indication in the RRCConnectionReconfiguration message, the existing LTE HO procedure described in FIG. 4C is performed. The terminal transmits a random access preamble (at step 4g-15), receives an RAR from the target BS, and identifies uplink resource allocation (at step 4g-20). The terminal generates a msg3 signal including a C-RNTI to notify the target base station of the completion of the HO procedure (at step 4g-25), and transmits the HO complete message to the target base station by including the HO complete message in the RRCConnectionReconfigurationComplete message (at step 4g-30). The msg4 for identifying the reception of the RRC message corresponding to the msg3 is received through the PDCCH (at step 4g-35). The PDCCH is transmitted to the C-RNTI transmitted from the msg3 and includes the uplink resource allocation information. As described above, if the RAP from the target base station is successfully completed in the MAC, the terminal ends the T304 timer (at step 4g-40).

[0717] If the RACH-less HO indicator is in the RRCConnectionReconfiguration message, the terminal monitors the PDCCH or the RRC to receive the uplink resource allocation. Upon receiving the uplink resource allocation through the transmitted RRC message, a first operation of the RACH-less HO except for the RAP is performed. That is, the terminal generates a msg3 signal including a C-RNTI to notify the target base station of the completion of the HO procedure (at step 4g-55), and transmits the HO complete message to the target base station by including the HO complete message in the RRCConnectionReconfigurationComplete message (at step 4g-60). The msg4 for identifying the reception of the RRC message corresponding to the msg3 is received through the PDCCH (at step 4g-65). The PDCCH is transmitted to the C-RNTI transmitted from the msg3 and includes the uplink resource allocation information. As described above, if the RAP from the target base station is successfully completed in the MAC, the terminal ends the T304 timer (at step 4g-70).

[0718] If the terminal receives the uplink resource allocation on the PDCCH in step 4g-50, a second operation of the RACH-less HO except for the RAP is performed. The PDCCH may be repeatedly transmitted from the target base station. In particular, the uplink resource allocation information included in the PDCCH may have the same value or different values until the terminal transmits msg3. The terminal generates a msg3 signal including a C-RNTI to notify the target base station of the completion of the HO procedure (at step 4g-75), and transmits the HO complete message to the target base station by including the HO complete message in the RRCConnectionReconfigurationComplete message (at step 4g-80). The msg4 for identifying the reception of the RRC message corresponding to the msg3 is received through the PDCCH (at step 4g-85). The PDCCH is transmitted to the C-RNTI transmitted in the msg3, and the method for identifying the reception of the msg3 can include one of the following two methods.

[0719] Option 1: When the target base station successfully receives the RRC message (msg3), a method can include scheduling an uplink resource allocation (grant) having parameters different from an uplink resource allocation previously transmitted to the terminal.

[0720] Option 2: If the target base station successfully receives the RRC message (msg3), a method can include scheduling downlink resource allocation.

[0721] When Option 1 is used, there is a restriction that parameters should be set to be scheduled in the same PRB when initial uplink resource allocation is performed in the target cell. That is, the terminal should repeatedly transmit the same parameters continuously for the same resource allocation before the terminal receives the uplink resource. On the other hand, when Option 2 is used, there is a degree of freedom in initial uplink resource allocation in the target cell. That is, since the terminal can know that the HO operation is completed when receiving the downlink resource allocation in the PDCCH, the terminal can identify the uplink resource allocation by transmitting another uplink resource allocation from the target base station. In addition, the UE Contention Resolution Identity may be included in the MAC CE upon the downlink transmission for clear operation. The MAC CE design method is described in detail with reference to FIG. 4F. As described above, if the RAP from the target base station is successfully completed in the MAC, the terminal ends the T304 timer (at step 4g-90).

[0722] FIG. 4H is a diagram of the terminal, according to an embodiment of the present disclosure.

[0723] Referring to FIG. 4H, the terminal includes a transceiver 4h-05, a controller 4h-10, a multiplexer and demultiplexer 4h-15, a control message processor 4h-30, various higher layer processors 4h-20 and 4h-25, an EPS bearer manager 4h-35, and a NAS layer apparatus 4h-40.

[0724] The transceiver 4h-05 receives data and a predetermined control signal through a forward channel of the serving cell and transmits the data and the predetermined control signal through a the reverse channel. When a plurality of serving cells are configured, the transceiver 4h-05 transmits and receives data and a control signal through the plurality of carriers.

[0725] The multiplexer and demultiplexer 4h-15 serves to multiplex data generated from the upper layer processors 4h-20 and 4h-25 or the control message processor 4h-30 or demultiplex data received by the transceiver 4h-05 and transmit the data to the appropriate upper layer processors 4h-20 and 4h-25 or the control message processor 4h-30.

[0726] The control message processor 4h-30 is an RRC layer apparatus and process the control message received from the base station to take the required operation. For example, when receiving an RRC CONNECTION SETUP message, it configures an SRB and a temporary DRB.

[0727] The upper layer processors 4h-20 and 4h-25 are the DRB apparatus and may be configured for each service. The higher layer processors 4h-20 and 4h-25 process data generated from user services such as a file transfer protocol (FTP) or a VoIP and transfer the processed data to the multiplexer and demultiplexer 4h-15 or process the data transferred from the multiplexer and demultiplexer 4h-15 and transfer the processed data to service application of the higher layer. One service may be mapped one-to-one with one evolved packet system (EPS) bearer and one higher layer processor on a one-to-one basis.

[0728] The controller 4h-10 confirms scheduling commands, for example, reverse grants, received through the transceiver 4h-05 to control the transceiver 4h-05 and the multiplexer and demultiplexer 4h-15 to perform the reverse transmission by an appropriate transmission resource at an appropriate time.

[0729] FIG. 4I is a diagram of a base station, MME, and S-GW, according to an embodiment of the present disclosure.

[0730] The base station of FIG. 4I includes a transceiver 4i-05, a controller 4i-10, a multiplexer and demultiplexer 4i-20, a control message processor 4i-35, various upper layer processors 4i-25 and 4i-30, a scheduler 4i-15, EPS bearer apparatuses 4i-40 and 4i-45, and a NAS layer apparatus 4i-50. The EPS bearer apparatuses 4i-40 and 4i-45 are located on the S-GW and the NAS layer apparatus is located on the MME.

[0731] The transceiver 4i-05 transmits data and a predetermined control signal through a forward carrier and receives the data and the predetermined control signal through a reverse carrier. When a plurality of carriers are configured, the transceiver 4i-05 transmits and receives the data and the control signal through the plurality of carriers.

[0732] The multiplexer and demultiplexer 4i-20 serves to multiplex data generated from the upper layer processors 4i-25 and 4i-30 or the control message processor 4i-35 or demultiplex data received by the transceiver 4i-05 and transmit the data to the appropriate upper layer processors 4i-25 and 4i-30 or the control message processor 4i-35 or the controller 4i-10. The control message processor 4i-35 allows the UE to process the transmitted control message to perform the required operation or generates the control message to be transmitted to the UE and transmits the generated control message to the lower layer.

[0733] The higher layer processors 4i-25 and 4i-30 may be configured for each EPS bearer and configure data transferred from the EPS bearer apparatuses 4i-40 and 4i-45 as the RLC PDU and may transfer the data to the multiplexer and demultiplexer 4i-20 or configure RLC PDU transferred from the multiplexer and demultiplexer 4i-20 as the PDCP SDU and transfer the RLC PDU to the EPS bearer apparatuses 4i-40 and 4i-45.

[0734] The scheduler 4i-15 allocates a transmission resource to the terminal at appropriate timing in consideration of the buffer status and the channel status of the terminal, etc. and allows the transceiver to process the signal transmitted from the terminal or perform a process to transmit a signal to the terminal.

[0735] The EPS bearer apparatuses 4i-40 and 4i-45 are configured for each EPS bearer, and processes the data transmitted from the higher layer processor and transmits the processed data to the next network node.

[0736] The upper layer processors 4i-25 and 4i-30 and the EPS bearer apparatuses 4i-40 and 4i-45 are connected to each other by the S1-U bearer. The higher layer processor corresponding to the common DRB is connected to the EPS bearer for the common DRB by a common S1-U bearer.

[0737] The NAS layer apparatus 4i-50 processes the IP packet included in the NAS message and transmits the processed IP packet to the S-GW.

[0738] A method for determining and identifying a successful uplink resource allocation of a terminal in an HO when a random access is not used.

[0739] 1. A method of receiving an indicator indicating that a terminal does not use random access.

[0740] A method for receiving the indication through an RRC message (HO command) of a source base station;

[0741] 2. A method for making an operation different according to whether the indication is received.

[0742] A method for performing the existing LTE HO procedure when the indicator is not included;

[0743] A method for not using a random access for an HO to a target base station when the indicator is included;

[0744] 3. A method for performing a first operation and a second operation of an HO without a random access according to a method for receiving uplink resource allocation information.

[0745] A method for allowing a terminal to receive resource allocation information to an RRC message (HO command) by a first operation;

[0746] A method for allowing a terminal to receive uplink resource allocation information on a PDCCH by a second operation;

[0747] The first operation receives the uplink resource allocation by the RRC message to omit the random access operation;

[0748] A method for performing an HO procedure of the existing LTE after omitting the random access in the first operation;

[0749] A method for omitting, by a terminal, a random access and receiving uplink resource allocation (msg2) on a PDCCH in the second operation;

[0750] A method for repeatedly transmitting the same uplink resource allocation by allowing a base station to use the same parameter for the msg2 of the second operation;

[0751] A method for generating and transmitting msg3 including C-RNTI of a terminal in the second operation;

[0752] A method for differently operating option 1 and option 2 in a method for receiving msg4 in the second operation;

[0753] An object to notify that the msg4 of the second operation successfully receives the msg3 transmitted by the terminal;

[0754] A method for receiving a resource allocation value different from an uplink resource already received on a PDCCH in the option 1 of the second operation;

[0755] A method for including downlink resource allocation information in the option 2 of the second operation;

[0756] A method for including “UE Contention Resolution Identity” in MAC PDU of the downlink resource allocation information;

[0757] A method for allowing the “UE Contention Resolution Identity” to include a content of the RRC message received in the msg3;

[0758] The “UE Contention Resolution Identity” reuses the existing LTE structure or uses a new MAC CE;

[0759] A method for including only initial 48 bit information when the content of the msg3 exceeds 48 bits.

[0760] The present disclosure relates to a mobile communication system, and more particularly, to a method and apparatus for determining priority of uplink and downlink transmission links and side links in an LTE terminal supporting vehicle-to-everything (V2X).

[0761] FIG. 5A is a diagram of the LTE system, in accordance with an embodiment of the present disclosure.

[0762] Referring to FIG. 5A, the wireless communication system is configured to include a plurality of base stations 5a-05, 5a-10, 5a-15, and 5a-20, an MME 5a-25, an S-GW 5a-30. UE or terminal 5a-35 accesses an external network through the base stations 5a-05, 5a-10, 5a-15, and 5a-20 and the S-GW 5a-30.

[0763] The base stations 5a-05, 5a-10, 5a-15, and 5a-20 are access nodes of a cellular network and provides a wireless access to terminals that are connected to a network. That is, in order to serve traffic of users, the base stations 5a-05, 5a-10, 5a-15, and 5a-20 collect state information such as a buffer state, an available transmission power state, a channel state, or the like of the terminals to perform scheduling, thereby supporting a connection between the terminals and a core network (CN). The MME 5a-25 is an apparatus for performing various control functions as well as a mobility management function for the terminal 5a-35 and is connected to a plurality of base stations 5a-05, 5a-10, 5a-15, and 5a-20, and the S-GW 5a-30 is an apparatus for providing a data bearer. Further, the MME 5a-25 and the S-GW 5a-30 may further perform authentication, bearer management, etc., on the terminal 5a-35 connected to the network and may process packets that are to be received from the base stations 5a-05, 5a-10, 5a-15, and 5a-20 and packets that are to be transmitted to the base stations 5a-05, 5a-10, 5a-15, and 5a-20.

[0764] FIG. 5B is a diagram of a radio protocol structure in the LTE system, in accordance with an embodiment of the present disclosure.

[0765] Referring to FIG. 5B, the radio protocol of the LTE system is configured to include PDCPs 5b-05 and 5b-40, RLCs 5b-10 and 5b-35, and MACs 5b-15 and 5b-30 in the terminal and the eNB, respectively. The PDCPs 5b-05 and 5b-40 control IP header compression/decompression. The main functions of the PDCP are summarized as follows.

[0766] Header compression and decompression function (Header compression and decompression: ROHC only)

[0767] Transfer function of user data (Transfer of user data)

[0768] In-sequence delivery function (In-sequence delivery of upper layer PDUs at PDCP re-establishment procedure for RLC AM)

[0769] Reordering function (For split bearers in DC (only support for RLC AM): PDCP PDU routing for transmission and PDCP PDU reordering for reception)

[0770] Duplicate detection function (Duplicate detection of lower layer SDUs at PDCP re-establishment procedure for RLC AM)

[0771] Retransmission function (Retransmission of PDCP SDUs at HO and, for split bearers in DC, of PDCP PDUs at PDCP data-recovery procedure, for RLC AM)

[0772] Ciphering and deciphering function (Ciphering and deciphering)

[0773] Timer-based SDU discard function (Timer-based SDU discard in uplink)

[0774] The RLCs 5b-10 and 5b-35 reconfigures the PDCP PDU to an appropriate size to perform the ARQ operation or the like. The main functions of the RLC are summarized as follows.

[0775] Data transfer function (Transfer of upper layer PDUs)

[0776] ARQ function (Error Correction through ARQ (only for AM data transfer))

[0777] Concatenation, segmentation, reassembly functions (Concatenation, segmentation and reassembly of RLC SDUs (only for UM and AM data transfer))

[0778] Re-segmentation function (Re-segmentation of RLC data PDUs (only for AM data transfer))

[0779] Reordering function (Reordering of RLC data PDUs (only for UM and AM data transfer)

[0780] Duplicate detection function (Duplicate detection (only for UM and AM data transfer))

[0781] Error detection function (Protocol error detection (only for AM data transfer))

[0782] RLC SDU discard function (RLC SDU discard (only for UM and AM data transfer))

[0783] RLC re-establishment function (RLC re-establishment)

[0784] The MACs 5b-15 and 5b-30 are connected to several RLC layer devices configured in one terminal and perform multiplexing RLC PDUs into an MAC PDU and demultiplexing the RLC PDUs from the MAC PDU. The main functions of the MAC are summarized as follows.

[0785] Mapping function (Mapping between logical channels and transport channels)

[0786] Multiplexing/demultiplexing function (Multiplexing/demultiplexing of MAC SDUs belonging to one or different logical channels into/from TBs delivered to/from the physical layer on transport channels)

[0787] Scheduling information reporting function (Scheduling information reporting)

[0788] HARQ function (Error correction through HARQ)

[0789] Priority handling function between logical channels (Priority handling between logical channels of one UE)

[0790] Priority handling function between terminals (Priority handling between UEs by means of dynamic scheduling)

[0791] MBMS service identification function (MBMS service identification)

[0792] Transport format selection function (Transport format selection)

[0793] Padding function (Padding)

[0794] Physical layers 5b-20 and 5b-25 perform channel-coding and modulating higher layer data, making the higher layer data as an OFDM symbol and transmitting them to a radio channel, or demodulating and channel-decoding the OFDM symbol received through the radio channel and transmitting the demodulated and channel-decoded OFDM symbol to the higher layer.

[0795] Although not illustrated, RRC layers are present at an upper part of the PDCP layer of the terminal and the base station, and the RRC layer may receive and transmit connection and measurement related control messages for a radio resource control.

[0796] FIG. 5C is a diagram of vehicle-to-everything (V2X) communication within a cellular system, in accordance with an embodiment of the present disclosure.

[0797] A V2X is a communication technology through a vehicle and all interfaces, and examples thereof may include a vehicle-to-vehicle (V2V), vehicle-to-infra-structure (V2I), a vehicle-to-pedestrian (V2P), and the like according to the form thereof and the component forming the communication. The V2P and V2V depends on a structure and an operation principle of device-to-device (D2D).

[0798] The base station 5c-01 includes at least one vehicle terminal 5c-05 and 5c-10 and a pedestrian portable terminal 5c-15 located in a cell 5c-02 supporting V2X. That is, the vehicle terminal 5c-05 performs cellular communication using the base station 5c-01 and the vehicle terminal-base link 5c-30 and 5c-35 or the device-to-device communication using side links 5c-20 and 5c-25 with the other vehicle terminal 5c-10 or the pedestrian portable terminal 5c-15. In order for the vehicle terminals 5c-05 and 5c-10 and the pedestrian portable terminal 5c-15 to directly transmit and receive information using the side links 5c-20 and 5c-25, the base station 5c-01 should allocate a resource pool that may be used for the side link communication. It may be divided into a scheduled resource allocation (mode 3) and UE autonomous resource allocation (mode 4), by a base station. In the case of the scheduled resource allocation, the base station allocates resources used for the side link transmission to the RRC-connected UEs in a dedicated scheduling manner. The above method is effective for interference management and resource pool management (semi-persistence transmission) because the base station 5c-01 can manage the resources of the side link.