KR102380612B1 - Method and apparatus for transmitting data in rrc inactive state or rrc active state - Google Patents

Abstract

The present disclosure relates to a communication technique that converges a 5G communication system for supporting a higher data rate after a 4G system with IoT technology, and a system thereof. The present disclosure provides intelligent services (eg, smart home, smart building, smart city, smart car or connected car, healthcare, digital education, retail business, security and safety-related services, etc.) based on 5G communication technology and IoT-related technology. ) can be applied to In the present invention, in a method for transmitting uplink data of a terminal in a wireless communication system, when the terminal is in an RRC (radio resource control) inactive state, an RRC connection request message corresponding to an RA response message (RRC connection request) Disclosed is a technique for transmitting uplink data to a base station by adding uplink data to the .

Description

Method and device for data transmission in RRC inactive or active state

The present invention relates to a description of an operation method of a base station and a terminal for achieving Energy Efficiency KPI discussed in 3GPP RAN 5G SI.

Efforts are being made to develop an improved 5G communication system or pre-5G communication system in order to meet the increasing demand for wireless data traffic after commercialization of the 4G communication system. For this reason, the 5G communication system or the pre-5G communication system is called a system after the 4G network (Beyond 4G Network) communication system or the LTE system after (Post LTE). In order to achieve a high data rate, the 5G communication system is being considered for implementation in a very high frequency (mmWave) band (eg, such as a 60 gigabyte (60 GHz) band). In order to alleviate the path loss of radio waves and increase the propagation distance of radio waves in the ultra-high frequency band, in the 5G communication system, beamforming, massive MIMO, and Full Dimensional MIMO (FD-MIMO) are used. ), array antenna, analog beam-forming, and large scale antenna technologies are being discussed. In addition, for network improvement of the system, in the 5G communication system, an evolved small cell, an advanced small cell, a cloud radio access network (cloud radio access network: cloud RAN), an ultra-dense network (ultra-dense network) , Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), and interference cancellation Technology development is underway. In addition, in the 5G system, advanced coding modulation (ACM) methods such as FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding), and advanced access technologies such as Filter Bank Multi Carrier (FBMC), NOMA (non orthogonal multiple access), and sparse code multiple access (SCMA) are being developed.

On the other hand, the Internet is evolving from a human-centered connection network where humans create and consume information to an Internet of Things (IoT) network that exchanges and processes information between distributed components such as objects. Internet of Everything (IoE) technology, which combines big data processing technology through connection with cloud servers, etc. with IoT technology, is also emerging. In order to implement IoT, technology elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required. , M2M), and MTC (Machine Type Communication) are being studied. In the IoT environment, an intelligent IT (Internet Technology) service that collects and analyzes data generated from connected objects and creates new values in human life can be provided. IoT is a field of smart home, smart building, smart city, smart car or connected car, smart grid, health care, smart home appliance, advanced medical service, etc. can be applied to

Accordingly, various attempts are being made to apply the 5G communication system to the IoT network. For example, in technologies such as sensor network, machine to machine (M2M), and MTC (Machine Type Communication), 5G communication technology is implemented by techniques such as beam forming, MIMO, and array antenna. there will be The application of cloud radio access network (cloud RAN) as the big data processing technology described above can be said to be an example of convergence of 5G technology and IoT technology.

In particular, the standard defines energy-efficient operation with the main goal of improving the power efficiency [bit/J] of terminals and base station networks by more than 1000 times within the next 10 years. To this end, in order to solve the possibility of additional power consumption due to the beamforming transmission method, which is essential during mmW operation in the high frequency band, a discussion is starting on a control to reduce the active operation time of the terminal.

In the existing LTE system, since only resources having one type of TTI exist, if the UL resources allocated by considering only the priorities between logical channels in the LCP process are used, the operation is performed without problems. However, in a future system such as a 5G mobile communication system, it is expected that a plurality of services having different performance requirements will be serviced using resources having various types of TTIs. Data transmission and reception using resources with different TTIs show different performance. Therefore, in the LCP process, the UL resource allocated to the UE must be utilized in consideration of the TTI attribute as well as the priority between logical channels. In this context, the present invention proposes an LCP process in consideration of the properties of TTI.

In addition, the design of the RRC state for the wireless communication terminal to transmit and receive data was designed too conservatively with the design philosophy of the previous generation focusing on voice calls. For example, even if there is no traffic arrival for a certain period of time after traffic is received, the standby time such as RRC connected (Connected DRX) is maintained, and power consumption due to this is serious. In addition, in the case of smartphone users, keep alive messages, etc., which are not related to user QoS, are frequently generated as data. Therefore, another object of the present invention is to improve the spectral efficiency and channel access method for efficiently transmitting the RRC state (Inactive and/or Active) determination method for data transmission and the UE traffic transmission in the RRC Inactive state in the patent. suggest

In addition, in the existing LTE system, the numerology of the physical layer set for the terminal to receive the signal from the base station - that is, values related to the structure of the physical layer, such as subcarrier spacing, subframe length, symbol length, etc. - is a random access procedure. were identical. However, when a mobile communication system that dynamically changes a plurality of numerologies is introduced, the terminal needs to receive numerology information required for the initial access procedure and transmission/reception operation in the connected state from the base station. Accordingly, the present invention proposes operations and procedures necessary for the base station to transmit which information to the terminal at which point in time and for the terminal to receive the numerology information of the base station.

A method for transmitting uplink data of a terminal in a wireless communication system according to an embodiment of the present invention includes the steps of receiving logical channel configuration information for uplink scheduling from a base station, and a scheduling request message (scheduling request) transmitting to the base station; and receiving an uplink resource allocation message configured based on the logical channel configuration information from the base station in response to the scheduling request message; and the uplink resource allocation message and transmitting uplink data to the base station according to

The logical channel configuration information includes correspondence information between an uplink resource and a logical channel transmittable through the uplink resource, and the uplink resource includes at least one of a transmission time interval (TTI) and a subcarrier spacing. can be classified based on

The logical channel configuration information may further include priority information on the logical channel transmittable through the uplink resource.

The uplink data may be transmitted to the base station through a resource determined based on the priority information for the logical channel included in the logical channel configuration information and resource allocation information included in the uplink resource allocation message. .

The scheduling request message may include information on a transmittable logical channel preferred by the terminal.

A method for receiving uplink data by a base station in a wireless communication system according to an embodiment of the present invention includes transmitting logical channel configuration information for uplink scheduling to a terminal, and a scheduling request message (scheduling request) Receiving from the terminal, and in response to the scheduling request message, transmitting an uplink resource allocation message configured based on the logical channel configuration information to the terminal, and in the uplink resource allocation message and receiving uplink data from the terminal accordingly.

The logical channel configuration information includes correspondence information between an uplink resource and a logical channel transmittable through the uplink resource, and the uplink resource includes at least one of a transmission time interval (TTI) and a subcarrier spacing. can be classified based on

The logical channel configuration information may further include priority information on the logical channel transmittable through the uplink resource.

The uplink data may be received from the terminal through a resource determined based on the priority information for the logical channel included in the logical channel configuration information and the resource allocation information included in the uplink resource allocation message. .

The scheduling request message may include information on a transmittable logical channel preferred by the terminal.

A terminal for transmitting uplink data in a wireless communication system according to an embodiment of the present invention includes a transceiver for transmitting and receiving a signal, and a control unit connected to the transceiver to control the transceiver. The control unit receives logical channel configuration information for uplink scheduling from the base station, transmits a scheduling request message to the base station, and responds to the scheduling request message to the logical channel configuration information It is possible to control the transceiver to receive an uplink resource allocation message (uplink grant) set based on , from the base station, and to transmit uplink data to the base station according to the uplink resource allocation message.

A base station for receiving uplink data in a wireless communication system according to an embodiment of the present invention includes a transceiver for transmitting and receiving a signal, and a control unit connected to the transceiver to control the transceiver. The controller transmits logical channel configuration information for uplink scheduling to the terminal, receives a scheduling request message from the terminal, and responds to the scheduling request message to the logical channel configuration information It is possible to control the transceiver to transmit an uplink resource allocation message configured based on the uplink grant to the terminal, and to receive uplink data from the terminal according to the uplink resource allocation message.

In a method for transmitting uplink data of a terminal in a wireless communication system according to another embodiment of the present invention, when the terminal is in a radio resource control (RRC) inactive state, a random access (RA) preamble is transmitted to a base station. to the base station, receiving an RA response message corresponding to the RA preamble from the base station, and adding uplink data to an RRC connection request message corresponding to the RA response message to the base station It includes the step of transmitting.

In the uplink data transmission method of the terminal, when the uplink data transmission is not completed when the RRC connection request message is transmitted, a buffer state report is further added to the RRC connection request message and transmitted to the base station It may include further steps.

In the uplink data transmission method of the terminal, when the state of the terminal is determined to be transitioned to the RRC connected state (connected stste) based on the buffer state report, an RRC connection resume message corresponding to the RRC connection request message (RRC connection) resume ) may further include the step of receiving from the base station.

In the uplink data transmission method of the terminal, when it is determined that the state of the terminal is maintained in the RRC inactive state based on the buffer status report, an RRC connection suspend message corresponding to the RRC connection request message is provided. It may further include the step of receiving from the base station.

The method for transmitting uplink data of the terminal may further include adding uplink data to an RRC connection resume complete message corresponding to the RRC connection resume message and transmitting the uplink data to the base station.

The method for transmitting uplink data of the terminal may further include transmitting uplink data to the base station in the RRC connected state when the terminal transitions to the RRC connected state according to the RRC connection resume message.

According to an embodiment, the RRC connection request message and the uplink data may be multiplexed and transmitted in one transport block.

In a method for receiving uplink data of a base station in a wireless communication system according to another embodiment of the present invention, when a terminal is in a radio resource control (RRC) inactive state, a random access (RA) preamble from the terminal receiving, transmitting an RA response message corresponding to the RA preamble from the terminal, an RRC connection request message corresponding to the RA response message, and an uplink added to the RRC connection request message and receiving link data from the terminal.

In the method for receiving uplink data of the base station, when the terminal fails to complete uplink data transmission when transmitting the RRC connection request message, a buffer state report added to the RRC connection request message is transmitted from the terminal It may further include the step of receiving.

The method for receiving uplink data of the base station includes determining to transition the state of the terminal to an RRC connected state (connected stste) based on the buffer state report, and the RRC connection request message according to the determination result. The method may further include transmitting an RRC connection resume message to the terminal.

The method for receiving uplink data by the base station includes determining to maintain the state of the terminal in the RRC inactive state based on the buffer state report, and an RRC connection stop message corresponding to the RRC connection request message according to the determination result The method may further include transmitting (RRC connection suspend) to the terminal.

In the method for receiving uplink data of the base station, an RRC connection resume complete message corresponding to the RRC connection resume message and uplink data added to the RRC connection resume complete message may be received from the terminal. .

The method for receiving uplink data of the base station may further include receiving uplink data from the terminal in the RRC connected state when the terminal transitions to the RRC connected state according to the RRC connection resume message.

According to an embodiment, the RRC connection request message and the uplink data may be multiplexed and received in one transport block.

A terminal for transmitting uplink data in a wireless communication system according to another embodiment of the present invention includes a transceiver for transmitting and receiving a signal, and a control unit connected to the transceiver to control the transceiver. When the terminal is in a radio resource control (RRC) inactive state, the controller transmits a random access (RA) preamble to the base station, and transmits an RA response message corresponding to the RA preamble from the base station It is possible to control the transceiver to receive and transmit uplink data to the base station by adding uplink data to an RRC connection request message corresponding to the RA response message.

A base station for receiving uplink data in a wireless communication system according to another embodiment of the present invention includes a transceiver for transmitting and receiving a signal, and a control unit connected to the transceiver to control the transceiver. When the terminal is in a radio resource control (RRC) inactive state, the controller receives a random access (RA) preamble from the terminal, and sends an RA response message corresponding to the RA preamble from the terminal and control the transceiver to receive an RRC connection request message corresponding to the RA response message and uplink data added to the RRC connection request message from the terminal.

According to an embodiment of the present invention, if the LCP operation considering the TTI attribute is used, when the UE is allocated an uplink resource, it is possible to clearly know through which TTI data belonging to a specific logical channel should be transmitted. In particular, when data having a low latency requirement is transmitted, it is possible to prevent a phenomenon in which retransmission is delayed due to the relatively long HARQ timeline although transmission was performed earlier through the previously allocated resource.

In addition, according to another embodiment of the present invention, when the communication system of the terminal and the base station selects the RRC state for data transmission and transmits data directly from the Inactive state while performing a procedure for this, it transitions to the RRC Connected_Active (or RRC_CONNECTED) state. (Transition) is not performed, so standby time (C-DRX, Radio tail) in the active state is kept to a minimum, so the power consumption saving effect of the terminal is expected. In addition, by transmitting data without an RRC release message for RRC state transition, when data is transmitted in the Inactive (Idle) state, the RRC state does not transition to Connected_active (or RRC_CONNECTED), so the delay required for related Control Signaling is removed. It has the effect of reducing data transmission delay. In addition, the reduction of the RRC release message for RRC state transition is expected to increase the efficiency of using radio resources through cost efficiency through reduction of power consumption of 5G base stations (RU/TRP) and reduction of peripheral interference between 5G cells.

In addition, according to another embodiment of the present invention, it is possible to transmit numerology information by efficiently using radio resources according to the density of the terminal or the service required by the terminal. In addition, in order to assist the terminal in selecting a signal transmission method for informing the base station, the base station may inform the service/slice/numerology/UE information provided by the network. In addition, this information can be used in the paging procedure for waking the terminal.

1 is a diagram illustrating how a UE utilizes uplink resources based on LCP in LTE.
2 is a diagram illustrating a plurality of services provided by the 5G mobile communication system and performance requirements for each service according to the first embodiment of the present invention.
3 is a diagram illustrating a time relationship between initial transmission, ACK/NACK feedback, and retransmission when HARQ-based transmission/reception is performed on resources having different TTIs according to the first embodiment of the present invention.
4 is a diagram for explaining a case in which a resource having a long TTI is allocated to a UE before a resource having a short TTI according to the first embodiment of the present invention.
5 is a diagram illustrating a signal flow diagram for operation 1 proposed according to the first embodiment of the present invention.
6 is a diagram illustrating a case in which a terminal is allocated a resource having one type of TTI from a base station according to the first embodiment of the present invention.
7 is a diagram illustrating a case in which a terminal is simultaneously allocated resources having several types of TTIs from a base station according to the first embodiment of the present invention.
8 is a diagram illustrating a flowchart of operation 2 proposed according to the first embodiment of the present invention.
9 is a diagram showing a flowchart of operation 3 proposed according to the first embodiment of the present invention.
10 is a diagram illustrating an example for explaining operation 4 proposed according to the first embodiment of the present invention.
11 is a diagram illustrating a hard split between a logical channel and a TTI proposed according to the first embodiment of the present invention.
12 is a diagram illustrating a soft split between a logical channel and a TTI proposed according to the first embodiment of the present invention.
13 is a diagram illustrating a hybrid split between a logical channel and a TTI proposed according to the first embodiment of the present invention from the viewpoint of a logical channel.
14 is a diagram illustrating a hybrid split between a logical channel and a TTI proposed according to the first embodiment of the present invention from the viewpoint of TTI.
15 is a diagram illustrating a method in which a base station notifies a terminal of an LCP set through a UL grant according to the first embodiment of the present invention.
16 is a diagram illustrating a method in which a terminal notifies a preferred LCP set to a base station through a scheduling request according to the first embodiment of the present invention.
17 is a diagram illustrating a method for a base station to efficiently apply a default priority and a special priority to a terminal according to the first embodiment of the present invention.
18 is a diagram illustrating a method in which a base station assigns a degree of freedom to a terminal's logical channel priority selection after allocating a TTI-specific priority to a terminal according to the first embodiment of the present invention.
19 is a diagram illustrating a modified method in which a base station efficiently applies a default priority and a special priority to a terminal according to the first embodiment of the present invention.
20 is a diagram schematically illustrating the structure of a 5G or NR communication system according to a second embodiment of the present invention.
21 is a diagram illustrating an example of operation of three RRC states, Connected_Active (or RRC_CONNECTED), Connected_Inactive, and Idle applied in the 5G or NR communication system according to the second embodiment of the present invention.
22 is a diagram illustrating examples of states of a terminal, a base station, and an MME in an inactive state in a 5G or NR communication system according to a second embodiment of the present invention.
23 is a diagram illustrating an example of state transition between RRC states (idle, Connected_Active (or RRC_CONNECTED) and Connected_Inactive (or RRC_INACTIVE)) according to the second embodiment of the present invention.
24 is a diagram schematically illustrating a data transmission operation in an INACTIVE state in an NR system according to a second embodiment of the present invention. It is a drawing.
25 is a diagram schematically illustrating a data transmission operation in an INACTIVE state in an NR system according to a second embodiment of the present invention.
26 is a diagram schematically illustrating a data transmission operation in an INACTIVE state in an NR system according to a second embodiment of the present invention.
27 is a diagram schematically illustrating a data transmission operation in an INACTIVE state in an NR system according to a second embodiment of the present invention.
28 is a diagram schematically illustrating a data transmission operation after a state transition from INACTIVE to ACTIVE in the NR system according to the second embodiment of the present invention.
29 is a diagram schematically illustrating a data transmission operation after starting data transmission in an INACTIVE state and transitioning to an ACTIVE state in the NR system according to the second embodiment of the present invention.
30 is an NR system according to the second embodiment of the present invention, starting data transmission through MSG3 in the INACTIVE state, adding data to Message5 RRC connection (resume) complete, and transmitting it. Upon completion of data transmission, (ACK) and suspend) to maintain the Inactive state.
31 is a diagram schematically illustrating a data transmission operation after starting data transmission in an INACTIVE state and transitioning to an ACTIVE state in the NR system according to the second embodiment of the present invention.
32 is a diagram in the NR system according to the second embodiment of the present invention that starts data transmission through MSG3 in the INACTIVE state, adds data to Message5 RRC connection (resume) complete, and transmits it. When data transmission is additionally required, RRC connection This diagram explains the operation of transitioning to the Active state by transmitting (ACK and Resume) to the response and then transitioning back to Inactive through RRC connection suspend message transmission when data transmission is completed again.
33 is a diagram illustrating an example of a signaling operation between UEs for determining and controlling an RRC state (Inactive and/or Active) for data transmission in an NR system according to a second embodiment of the present invention.
34 is a diagram illustrating an example of a signaling operation between UEs for determining and controlling an RRC state (Inactive and/or Active) for data transmission in an NR system according to a second embodiment of the present invention.
35 is a diagram illustrating an example of a signaling operation between UEs for determining and controlling an RRC state (Inactive and/or Active) for data transmission in an NR system according to a second embodiment of the present invention.
36 is a diagram illustrating an example of a signaling operation between UEs for determining and controlling an RRC state (Inactive and/or Active) for data transmission in an NR system according to a second embodiment of the present invention.
37 is a diagram illustrating an example of a signaling operation between UEs for determining and controlling an RRC state (Inactive and/or Active) for data transmission in an NR system according to a second embodiment of the present invention.
38 is a diagram illustrating an example of a signaling operation between UEs for determining and controlling an RRC state (Inactive and/or Active) for data transmission in an NR system according to a second embodiment of the present invention.
39 is an operation of a method of determining an operation mode related to MSG3 or MSG5 or RRC state transition in which the terminal transmits data based on an event trigger configured by the base station for data transmission in the NR system according to the second embodiment of the present invention; is a diagram for explaining
40 shows MSG3 or MSG5 to which the terminal transmits data when the terminal operates without additional feedback on the corresponding event to the base station based on an event trigger configured by the base station for data transmission in the NR system according to the second embodiment of the present invention. Alternatively, it is a diagram explaining an operation of a method of determining an RRC state transition related operation mode.
41 is a diagram illustrating MSG3 or MSG5 to which the terminal transmits data when the terminal transmits additional feedback on a corresponding event to the base station based on an event trigger configured by the base station for data transmission in the NR system according to the second embodiment of the present invention. Alternatively, it is a diagram explaining an operation of a method of determining an RRC state transition related operation mode.
42 is a view for explaining an operation in which the terminal transmits data based on an event trigger configured by the base station for data transmission and the base station determines the RRC state transition related operation mode as an operation according to the second embodiment of the present invention.
43 is a diagram illustrating an example of an information acquisition method for improving spectral efficiency in the case of efficiently performing transmission in the NR RRC inactive state according to the second embodiment of the present invention.
44 is a diagram illustrating an example of a method for acquiring information for improving channel access in the case of efficiently performing transmission in an NR RRC Inactive state according to the second embodiment of the present invention.
45 is a diagram illustrating an example of a method for improving channel access efficiency in the case of efficiently performing transmission in the NR RRC Inactive state according to the second embodiment of the present invention.
46 is a diagram illustrating multiple UL grant allocation and a corresponding UL transmission procedure based on UE buffer state information when data is transmitted in the NR RRC Inactive state according to the second embodiment of the present invention.
47 is an operation by allocating a preamble sequence and resources for dedicated RACH and grant-free transmission during data transmission in the NR RRC Inactive state according to the second embodiment of the present invention, and setting a valid timer for these resources. A diagram showing the process.
48 illustrates a criterion for determining whether to perform a contention based RACH-based data transmission operation, a dedicated based RACH-based data transmission operation, or a grant-free based data transmission when data is transmitted in the NR RRC Inactive state according to the second embodiment of the present invention. It is a drawing showing
49 is a diagram illustrating an additional continuous transmission procedure after initial transmission when data is transmitted in the NR RRC Inactive state according to the second embodiment of the present invention.
50 is a diagram illustrating an example of traffic characteristics of a keep alive message of a specific application according to the second embodiment of the present invention.
51 is a diagram illustrating various procedures for setting a dedicated numerology set according to a third embodiment of the present invention.
52 is a diagram illustrating an initial access procedure according to a third embodiment of the present invention.
53 is an example-I diagram of an initial access procedure in consideration of a UL presence signal according to a third embodiment of the present invention.
54 is an example-I diagram of an initial access procedure in consideration of a DL probing signal according to a third embodiment of the present invention.
55 is an example initial access procedure-I diagram in consideration of the UL presence signal and the DL probing signal according to the third embodiment of the present invention.
56 is an example initial access procedure-II diagram in consideration of the UL presence signal and the DL probing signal according to the third embodiment of the present invention.
57 is an example initial access procedure-II diagram in consideration of the UL presence signal according to the third embodiment of the present invention.
58 is an example of a method for transmitting and receiving a tone-based signal based on UE ID and service ID according to a third embodiment of the present invention.
59 is an example of overlapping tone-based signals from a plurality of terminals according to the third embodiment of the present invention.
60 is an example of a base station inquiring an MME with tone or hash code information according to a third embodiment of the present invention.
61 is an example in which the base station sends a matching indication to the MME according to the third embodiment of the present invention.
62 is a diagram illustrating a configuration of a terminal device according to a third embodiment of the present invention.
63 is a diagram illustrating options applied in a process in which a terminal switches from an idle state to a connected state according to a third embodiment of the present invention.
64 is an example when the UPCH reuses the existing RA procedure according to the third embodiment of the present invention.
65 is an example when the UPCH uses a modified RA procedure according to the third embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. In addition, in the description of the present invention, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted. In addition, the terms to be described later are terms defined in consideration of functions in the present invention, which may vary according to intentions or customs of users and operators. Therefore, the definition should be made based on the content throughout this specification.

Advantages and features of the present invention, and a method for achieving them will become apparent with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but may be implemented in various different forms, and only these embodiments allow the disclosure of the present invention to be complete, and common knowledge in the technical field to which the present invention belongs It is provided to fully inform the possessor of the scope of the invention, and the present invention is only defined by the scope of the claims. Like reference numerals refer to like elements throughout.

<First embodiment>

The present invention proposes a UL scheduling method in a 5G mobile communication system. Various services (or slices) such as enhanced Mobile BroadBand (eMBB), Ultra Reliable and Low Latency Communication (URLLC), and enhanced Machine Type Communication (eMTC) are expected to be supported in the 5G mobile communication system. This can be understood in the same context that the 4G mobile communication system, LTE, supports voice-specific services such as VoIP (Voice over Internet Protocol) and BE (Best Effort) services. In addition, it is expected that various numerologies will be supported in the 5G mobile communication system. This specifically means subcarrier spacing (SCS) or Transmission Time Interval (TTI).

Therefore, it is expected that various lengths of TTI or SCS will be supported in the 5G mobile communication system. This can be seen as one of the characteristics of the 5G mobile communication system, which is very different from the support of only one type of TTI (1 ms) and one type of SCS (15 kHz) in LTE standardized so far. If the 5G mobile communication system supports a much shorter TTI (eg 0.1 ms) than the 1 ms TTI of LTE, it is expected to be of great help in supporting URLLC that requires a short delay time.

The present invention proposes a UL scheduling method considering the characteristics of such a 5G mobile communication system, that is, various services and various numerology (TTI and SCS) support. The difference from the UL scheduling method defined in LTE is that, in the past, it was a scheduling method to support various services, but in the present invention, it can be viewed as a scheduling method to support various services using various numerology. Note that in this document, TTI, subcarrier spacing, etc. are used as terms that play the same role. That is, the method considering TTI among the examples of the present invention may be extended to the method considering SCS in the same principle.

Before describing the present invention, let's look at the existing method. The present invention focuses on Logical Channel Prioritization (LCP) among UL scheduling. 36.321, one of LTE standards, defines an LCP operation for UL scheduling. In the case of DL scheduling, the subject that generates and transmits DL traffic is the base station, and the subject that performs DL scheduling is also the base station. That is, the base station only needs to perform DL scheduling and transmit the generated DL traffic. However, in the case of UL scheduling, the subject that generates and transmits UL traffic is the UE, but the subject that performs UL scheduling is the base station. Therefore, the base station allocates a resource of a certain size to the terminal through UL scheduling, and the terminal fills the allocated resource with UL traffic generated by it and transmits it to the base station. Here, the method of "filling the UL traffic generated by the terminal to the allocated resource" is referred to as LCP.

1 is a diagram illustrating how a UE utilizes uplink resources based on LCP in LTE.

Uplink traffic (UL traffic) generated in the terminal corresponds to a logical channel according to a service type and the like. For example, each logical channel or a group of multiple logical channels may correspond to each service. Each logical channel has priority according to the configuration of the base station.

Referring to FIG. 1 , logical channels 1, 2, and 3 correspond to priorities 1, 2, and 3, respectively. When a resource is allocated from the base station, the terminal fills the allocated resource with data that satisfies the PBR (Prioritized Bit Rate) condition in order of logical channels with high priority (basically). Here, the PBR of each logical channel may also be set by the base station through RRC signaling or the like. Thereafter, the terminal fills the allocated resources according to the priority until all allocated resources are exhausted. The specific operation for this is defined in the LTE standard as follows.

------------------------------------------------------------ ------------------------------------------------------------ ------------------------

5.4.3 Multiplexing and assembly

5.4.3.1 Logical channel prioritization

The Logical Channel Prioritization procedure is applied when a new transmission is performed.

RRC controls the scheduling of uplink data by signaling for each logical channel: priority where an increasing priority value indicates a lower priority level, prioritisedBitRatewhich sets the Prioritized Bit Rate (PBR), bucketSizeDuration which sets the Bucket Size Duration (BSD).

The MAC entity shall maintain a variable Bj for each logical channel j. Bj shall be initialized to zero when the related logical channel is established, and incremented by the product PBR X TTI duration for each TTI, where PBR is Prioritized Bit Rate of logical channel j. However, the value of Bj can never exceed the bucket size and if the value of Bj is larger than the bucket size of logical channel j, it shall be set to the bucket size. The bucket size of a logical channel is equal to PBR X BSD, where PBR and BSD are configured by upper layers.

The MAC entity shall perform the following Logical Channel Prioritization procedure when a new transmission is performed:

- The MAC entity shall allocate resources to the logical channels in the following steps:

- Step 1: All the logical channels with Bj> 0 are allocated resources in a decreasing priority order. If the PBR of a logical channel is set to "infinity", the MAC entity shall allocate resources for all the data that is available for transmission on the logical channel before meeting the PBR of the lower priority logical channel(s);

- Step 2: the MAC entity shall decrement Bj by the total size of MAC SDUs served to logical channel j in Step 1

NOTE: The value of Bj can be negative.

- Step 3: if any resources remain, all the logical channels are served in a strict decreasing priority order (regardless of the value of Bj) until either the data for that logical channel or the UL grant is exhausted, whichever comes first. Logical channels configured with equal priority should be served equally.

------------------------------------------------------------ ------------------------------------------------------------ ------------------------

1 illustrates how LCP operates in LTE, and if one logical channel or a group of a plurality of logical channels corresponds to one service, it can be seen that LCP considering a plurality of services is already supported in LTE.

2 is a diagram showing a plurality of services provided by the 5G mobile communication system and performance requirements for each service.

The first embodiment proposes a method for how LCP should be improved when multiple TTIs or SCSs as well as multiple services are introduced in a 5G mobile communication system. Referring to FIG. 2 , in a 5G mobile communication system, eMBB, URLLC, eMTC, etc. require different performance. In particular, in terms of latency, it can be seen that different performance is required for each service.

In terms of TTI, transmission and reception performed through resources having different TTIs have different HARQ timelines (data initial transmission, ACK or NACK transmission, and data retransmission). This is because the TTI is mainly proportional to the time required for data encoding and decoding.

3 is a diagram illustrating a time relationship between initial transmission, ACK/NACK feedback, and retransmission when HARQ-based transmission/reception is performed in resources having different TTIs. Referring to FIG. 3 , it shows HARQ timelines of different TTIs.

As described above, since latency requirements for each service are different in the 5G mobile communication system, in general, services requiring short latency should be transmitted and received through short TTI, and services requiring relatively long latency may be transmitted/received through long TTI. Since LTE's LCP does not reflect these TTI characteristics, the 5G mobile communication system must design the LCP reflecting this point.

From now on, for convenience of discussion, the following assumptions are made. This is for convenience only, and the content of the present invention is not limited to the following assumptions.

1) The terminal is using services S1 and S2 at the same time.

A. Both UL traffic of current services S1 and S2 exist in the UL buffer of the UE.

2) Services S1 and S2 are optimized for transmission/reception through TTI1 and TTI2, respectively.

A. Services S1 and S2 are optimized for transmission and reception through TTI1 and TTI2, respectively, but S1 may be transmitted to TTI2 or S2 may be transmitted to TTI1.

In addition, each service may perform transmission/reception using only a TTI optimized for itself. For example, service S1 may perform transmission/reception using only TTI1, and service S2 may perform transmission/reception using only TTI2.

In addition, a specific service may perform transmission/reception using only the TTI optimized for itself, and other specific services may perform transmission/reception using all TTIs. For example, service S1 may perform transmission/reception using only TTI1, and service S2 may perform transmission/reception using both TTI1 and TTI2.

3) Services S1 and S2 share and use time/frequency radio resources.

4) TTI2 is shorter than TTI 1.

5) Service S2 requires lower latency than S1.

When this assumption is applied, FIG. 4 shows in detail the conditions to be considered when designing an LCP in a 5G mobile communication system.

4 is a diagram for explaining a case in which a resource having a long TTI is allocated before a resource having a short TTI to a terminal according to the present invention.

<Situation 1>

Referring to FIG. 4 , at time T1, the terminal may be allocated a TTI1 resource from the base station. The UE transmits both UL traffic for service S1 and UL traffic for service S2 that are currently in its UL buffer in the corresponding resource. Here, it is assumed that the size of the corresponding resource is sufficient. Situation 1 corresponds to a situation in which services S1 and S2 use the same time/frequency radio resource. The present invention includes the resource utilization method described in <Situation 1>. That is, the resource utilization method is set so that both the service S1 and the service S2 can use the TTI1 resource. Here, the situation in which the services S1 and S2 use the same time/frequency radio resource refers to a situation in which the services S1 and S2 use the time/frequency radio resource having the same TTI more specifically.

<Situation 2>

Referring to FIG. 4 , at time T1, the terminal may be allocated a TTI1 resource from the base station. The UE transmits the resource including the UL traffic for the service S1 currently present in its UL buffer, but may not transmit the UL traffic for the service S2. At time point T2, the terminal may be allocated a TTI2 resource from the base station. The UE transmits the resource including UL traffic for service S2 currently present in its UL buffer. Situation 2 corresponds to a situation in which services S1 and S2 use different time/frequency radio resources. The present invention includes the resource utilization method described in <Situation 2>. That is, it is a resource utilization method in which the service S1 and the service S2 are set to use time/frequency radio resources having different TTIs, respectively. In other words, service S1 uses a radio resource having TTI1 and service S2 uses a radio resource having TTI2.

Situations 1 and 2 above show a case in which the base station first allocates a long TTI resource to the terminal while the terminal has both UL traffic of service S1 optimized for TTI1 and service S2 optimized for TTI2. In this case, the UE must satisfy the latency requirements of services S1 and S2 (especially S2 with short latency requirements).

If the UE does not know that a TTI2 resource capable of faster transmission and reception will be allocated from the viewpoint of the HARQ timeline within a certain period of time, it is the best choice to transmit all UL traffic in T1, which is the earliest time. This corresponds to situation 1. However, if the UE knows that a TTI2 resource capable of faster transmission and reception will be allocated from the viewpoint of the HARQ timeline within a certain period of time, UL traffic of the service S1 optimized for TTI1 in T1 rather than transmitting all UL traffic in T1, which is the fastest time currently. , and the UL traffic of service S2 optimized for TTI2 is the best choice to transmit at the time T2 when TTI2 resources are allocated after some time. This corresponds to situation 2.

However, in general, it is difficult for the terminal to know when the base station will allocate the TTI2 resource to itself at the time T1. Therefore, if a rule considering the type of TTI is created and applied to the LCP, it will be possible to properly respond to the above situation. The LCP operation in consideration of the TTI type will now be described.

<Action 1>

(1) The base station provides the terminal with a default priority for each logical channel. This can be done through LogicalChannelConfig IE (Information Element) during RRC signaling as shown below.

- LogicalChannelConfig

The IE LogicalChannelConfig is used to configure the logical channel parameters.

LogicalChannelConfig information element

-- ASN1START

LogicalChannelConfig ::= SEQUENCE {

ul-SpecificParameters SEQUENCE {

defaultPriority INTEGER (1..16),

prioritisedBitRate ENUMERATED {

kBps0, kBps8, kBps16, kBps32, kBps64, kBps128,

kBps256, infinity, kBps512-v1020, kBps1024-v1020,

kBps2048-v1020, spare5, spare4, spare3, spare2,

spare1},

bucketSizeDuration ENUMERATED {

ms50, ms100, ms150, ms300, ms500, ms1000, spare2,

spare1},

logicalChannelGroup INTEGER (0..3) OPTIONAL -- Need OR

} OPTIONAL, -- Cond UL

...,

[[ logicalChannelSR-Mask-r9 ENUMERATED {setup} OPTIONAL -- Cond SRmask

]],

[[ logicalChannelSR-Prohibit-r12 BOOLEAN OPTIONAL -- Need ON

]]

}

-- ASN1STOP

[Table 1]

(2) The base station provides a special priority applied to the UL grant when allocating the UL grant to the terminal. This may be accomplished through Downlink Control Information (DCI) transmitted through the PDCCH.

A. Here, special priority may be set for one logical channel or may be set for two or more logical channels. Also, special priority may not be set for any logical channel.

B. Table 2 below shows an example in which the base station notifies the terminal of the highest priority logical channel applied to the UL grant when the base station allocates the UL grant to the terminal.

[Table 2]

(3) Through the processes of (1) and (2) above, the UE is provided with default priority and special priority for the logical channel. Based on this, the terminal operates as follows.

A. Data is filled in the UL grant allocated from the base station in the order of logical channels with high special priority. That is, LCP is applied to a logical channel in which special priority is set.

B. When resources remain in the UL grant after filling the UL grant with all the data of the logical channel designated with the special priority, the data is filled in the order of the logical channel with the higher default priority. That is, after data is filled by applying LCP to a logical channel in which a special priority is set, LCP is applied to a logical channel in which a default priority is set.

5 is a diagram illustrating a signal flow diagram for operation 1 proposed according to the first embodiment of the present invention.

(1) The base station (5G-NB) may provide the terminal (UE) by setting default priorities for logical channels A, B, C, and D in the order of A > B > C > D. Here, the format of A > B > C > D means that A is the 1st, B is the 2nd, C is the 3rd, and D is the 4th.

(2) When the base station (5G-NB) allocates the UL grant to the UE, the special priority applied to the UL grant is set in the order of C > A and provided.

(3) The UE fills the UL grant by first performing LCP operations in the order of special priority C > A for A and C, which are logical channels to which special priority is specified.

(4) If the UE performs the LCP operation in the order of special priority C > A and fills the UL grant and there are resources left in the UL grant, according to the default priority for the remaining logical channels except for A and C already considered The UL grant is filled by performing the LCP operation in the order of B > D.

A. If no special priority is set in the UL grant, the UE fills the UL grant by performing LCP operations in the order of default priority A > B > C > D.

<Action 2>

(1) The base station provides a logical channel priority for each type of TTI to the terminal. This can be done through LogicalChannelConfig IE during RRC signaling.

A. For example, a UL grant having a 1 ms TTI is provided with a priority in the order of A > B > C > D, and a UL grant having a 0.2 ms TTI is provided with a priority in the order of C > B > A > D. This means that logical channels A, B, C, and D can use a UL grant with 1 ms TTI, and when logical channels A, B, C, and D are transmitted through a UL grant with 1 ms TTI, LCP It means that the priority applied in the process is A > B > C > D. Similarly, it means that logical channels A, B, C, and D can use a UL grant with 0.2 ms TTI, and when logical channels A, B, C, and D are transmitted through a UL grant with 0.2 ms TTI, LCP It means that the priority applied in the process is C > B > A > D.

If priority is provided in the order of A > B to a UL grant with 1 ms TTI and priority in order of C > D to a UL grant with 0.2 ms TTI, this means that logical channels A and B receive a UL grant with 1 ms TTI. means it can be used. That is, logical channels other than logical channels A and B mean that a UL grant having a 1 ms TTI cannot be used. In order to perform the LCP operation, priority information is absolutely necessary. Therefore, the absence of priority information for a specific logical channel means that the logical channel cannot be used. Similarly, it means that logical channels C and D can use a UL grant having a TTI of 0.2 ms. That is, logical channels other than logical channels C and D mean that a UL grant having a TTI of 0.2 ms cannot be used.

(2) In addition, the base station provides a priority for each type of TTI to the terminal. This can also be done through LogicalChannelConfig IE during RRC signaling.

A. For example, a UL grant having a 0.2 ms TTI may be configured to have a higher priority than a UL grant having a 1 ms TTI. According to the description above, the priority between TTIs is included in the LogicalChannelConfig IE. Here, the LogicalChannelConfig IE includes information on a specific logical channel. Therefore, if the TTI priority for a specific logical channel is set to have 0.2 ms TTI higher than 1 ms TTI, it can be considered that the logical channel includes information that 0.2 ms TTI and 1 ms TTI can be used.

B. The LogicalChannelConfig IE below shows how logical channel priority information for each TTI type (priorityForTTIType1, priorityForTTIType2) and priority information for each TTI type (ulTTI-SpecificParameters, TTIType, priorityAmongTTIType) are set.

- LogicalChannelConfig

The IE LogicalChannelConfig is used to configure the logical channel parameters.

LogicalChannelConfig information element

-- ASN1START

LogicalChannelConfig ::= SEQUENCE {

ul-SpecificParameters SEQUENCE {

priorityForTTIType1 INTEGER (1..16),

priorityForTTIType2 INTEGER (1..16),

prioritisedBitRate ENUMERATED {

kBps0, kBps8, kBps16, kBps32, kBps64, kBps128,

kBps256, infinity, kBps512-v1020, kBps1024-v1020,

kBps2048-v1020, spare5, spare4, spare3, spare2,

spare1},

bucketSizeDuration ENUMERATED {

ms50, ms100, ms150, ms300, ms500, ms1000, spare2,

spare1},

logicalChannelGroup INTEGER (0..3) OPTIONAL -- Need OR

} OPTIONAL, -- Cond UL

ulTTI-SpecificParameters SEQUENCE {

TTIType INTEGER (1..16),

priorityAmongTTIType INTEGER (1..16),

}

...,

[[ logicalChannelSR-Mask-r9 ENUMERATED {setup} OPTIONAL -- Cond SRmask

]],

[[ logicalChannelSR-Prohibit-r12 BOOLEAN OPTIONAL -- Need ON

]]

}

-- ASN1STOP

[Table 3]

6 is a diagram illustrating a case in which a terminal is allocated a resource having one type of TTI at a specific time from a base station according to the first embodiment of the present invention.

(3) When the UE is allocated a UL grant corresponding to one type of TTI at a specific time from the base station as shown in FIG. 6, the UE operates as follows.

A. If the terminal is allocated a UL grant having a 1 ms TTI from the base station, the corresponding logical channels A, B, C, and D are given priorities in the order of A > B > C > D through LCP operation. Fill in the grant.

B. If the terminal is allocated a UL grant having a 0.2 ms TTI from the base station, the corresponding logical channels A, B, C, and D are given priority C > B > A > D in the order of UL through LCP operation Fill in the grant.

7 is a diagram illustrating a case in which a terminal is simultaneously allocated resources having several types of TTIs from a base station.

(4) The UE operates as follows when it is simultaneously allocated UL grants corresponding to two or more types of TTIs from the base station.

A. As an example, this includes a case in which the UE is allocated two UL grants (a UL grant with 1 ms TTI and a UL grant with 0.2 ms TTI) indicating the same time point as shown in FIG. 7 .

B. The UE fills the UL grant with a TTI having a high priority between TTIs according to the priority information for each TTI type provided by the base station in the order of the logical channel priority of the corresponding TTI.

i. In this example, since the UL grant with 0.2 ms TTI has a higher priority than the UL grant with 1 ms TTI, the UE first has a logical channel priority corresponding to the UL grant with 0.2 ms TTI, C > B > A > D Fill in the UL grant in order.

ii. If all data is filled in the UL grant with 0.2 ms TTI through LCP operation, the UL grant is filled in the order of A > B > C > D, which is the logical channel priority corresponding to the UL grant with the next priority, 1 ms TTI. .

8 is a diagram illustrating a flowchart of operation 2 proposed according to the first embodiment of the present invention.

Referring to FIG. 8 , the UE may identify a TTI having an M th priority and may determine a logical channel priority for a TTI having an M th priority. Thereafter, the UE may transmit data to a TTI (UL resource) having an M-th priority according to a corresponding logical channel priority.

The UE may determine whether it is the last TTI type or whether all the allocated UL resources are exhausted. According to an embodiment, when the last TTI type or all allocated UL resources are exhausted, the UE may terminate the LCP operation. According to another embodiment, when it is not the last TTI type or all allocated UL resources are not exhausted, the UE may identify a TTI having the next priority (M+1 th) and repeat the LCP operations.

The base station may provide priority information between logical channels for each type of TTI to the terminal. In the present invention, it is considered that, in addition to priority information between logical channels, PBR (Prioritized Bit Rate) and BSD (Bucket Size Duration) information may also be provided by the base station to the terminal for each TTI type through RRC signaling or the like.

Therefore, the UE can apply different PBRs (PBRa and PBRb) and different BSDs (BSDa and BSDb) when transmitting data belonging to the same logical channel using TTI type a and TTI type b. The roles of PBR and BSD are considered the same as those of existing LTE. That is, it works as follows.

* When transmitting data belonging to a specific logical channel using TTI type a (corresponds to step 1 of the LCP procedure defined in LTE)

- One-time quota: PBRa X TTIa

- Maximum quota: PBRa X BSDa

* When transmitting data belonging to a specific logical channel using TTI type b (corresponds to step 1 of the LCP procedure defined in LTE)

- One-time quota: PBRb X TTIb

- Maximum quota: PBRb X BSDb

<Action 3>

(1) The base station provides logical channel priority to the terminal in the same way as LTE. This can be done through LogicalChannelConfig IE during RRC signaling.

A. For example, priority is provided in the order of logical channel A > B > C > D.

(2) In addition, the base station provides the terminal with a priority for the TTI type for each logical channel. This can also be done through LogicalChannelConfig IE during RRC signaling.

A. For example, in logical channel A, a UL grant with a 1 ms TTI has higher priority than a UL grant with a 0.2 ms TTI. This means that logical channel A can use both a UL grant having a 1 ms TTI and a UL grant having a 0.2 ms TTI.

B. In addition, in logical channel B, a UL grant with a 0.2 ms TTI has higher priority than a UL grant with a 1 ms TTI. This means that logical channel B can use both a UL grant having a 0.2 ms TTI and a UL grant having a 1 ms TTI.

C. The LogicalChannelConfig IE below shows how priority information (ulTTI-SpecificParameters, TTIType, priorityAmongTTIType) for each TTI type is set.

- LogicalChannelConfig

The IE LogicalChannelConfig is used to configure the logical channel parameters.

LogicalChannelConfig information element

-- ASN1START

LogicalChannelConfig ::= SEQUENCE {

ul-SpecificParameters SEQUENCE {

priority INTEGER (1..16),

prioritisedBitRate ENUMERATED {

kBps0, kBps8, kBps16, kBps32, kBps64, kBps128,

kBps256, infinity, kBps512-v1020, kBps1024-v1020,

kBps2048-v1020, spare5, spare4, spare3, spare2,

spare1},

bucketSizeDuration ENUMERATED {

ms50, ms100, ms150, ms300, ms500, ms1000, spare2,

spare1},

logicalChannelGroup INTEGER (0..3) OPTIONAL -- Need OR

} OPTIONAL, -- Cond UL

ulTTI-SpecificParameters SEQUENCE {

TTIType INTEGER (1..16),

priorityAmongTTIType INTEGER (1..16),

}

...,

[[ logicalChannelSR-Mask-r9 ENUMERATED {setup} OPTIONAL -- Cond SRmask

]],

[[ logicalChannelSR-Prohibit-r12 BOOLEAN OPTIONAL -- Need ON

]]

}

-- ASN1STOP

[Table 4]

(3) When the terminal is allocated a UL grant corresponding to one type of TTI from the base station, it operates as follows.

A. The UE fills the UL grant allocated from the base station with data in the order of priority A > B > C > D (regardless of the TTI type of the UL grant).

(4) The UE operates as follows when receiving UL grants corresponding to two or more types of TTIs from the base station.

A. The UE fills data in the UL grant allocated according to the TTI priority of each logical channel in the order of the logical channels with the highest priority.

i. In this example, it is assumed that logical channel A has the highest priority. It is also assumed that a UL grant having a 1 ms TTI for logical channel A has a higher priority than a UL grant having a 0.2 ms TTI. Therefore, the UE first fills the UL grant with 1 ms TTI with data corresponding to logical channel A, and then fills the data following the UL grant with 0.2 ms TTI when the corresponding UL grant is insufficient.

ii. The UE repeats the same operation for logical channel B, which has the next highest priority after logical channel A. Here, for logical channel B, it is assumed that a UL grant having a TTI of 0.2 ms has a higher priority than a UL grant having a TTI of 1 ms. Therefore, the UE first fills the UL grant with 0.2 ms TTI with data corresponding to logical channel B, and then fills the data following the UL grant with 1 ms TTI when the corresponding UL grant is insufficient.

1. This describes a case in which data corresponding to logical channel B is filled assuming that resources are left in each UL grant after filling data corresponding to logical channel A into UL grants having 1 ms and 0.2 ms TTI. If all UL grants are exhausted after filling data corresponding to logical channel A, the LCP operation is terminated. If some UL grants are exhausted and only some resources remain after filling data corresponding to logical channel A, the same operation as above is continued for the UL grants in which the remaining resources exist.

9 is a diagram showing a flowchart of operation 3 proposed according to the first embodiment of the present invention.

Referring to FIG. 9 , the UE may identify a logical channel having an M th priority and may determine a TTI priority for a logical channel having an M th priority. Thereafter, the terminal may transmit data of the logical channel having the Mth priority on the resource allocated according to the corresponding TTI priority.

The UE may determine whether it is the last logical channel or whether all the allocated UL resources are exhausted. According to an embodiment, when the last logical channel or all allocated UL resources are exhausted, the UE may terminate the LCP operation. According to another embodiment, if it is not the last logical channel or all allocated UL resources are not exhausted, the UE may identify a logical channel having the next priority (M+1 th) and repeat the LCP operations.

The base station may provide the terminal with logical channel priority information for each TTI type. In the present invention, it is considered that, in addition to priority information of a logical channel, PBR (Prioritized Bit Rate) and BSD (Bucket Size Duration) information may also be provided by the base station to the terminal for each TTI type through RRC signaling or the like. The UE applies different PBRs (PBRa and PBRb) and different BSDs (BSDa and BSDb) when transmitting data belonging to the same logical channel using TTI type a and TTI type b. The roles of PBR and BSD are considered the same as those of existing LTE. That is, it works as follows.

* When transmitting data belonging to a specific logical channel using TTI type a (corresponds to step 1 of the LCP procedure defined in LTE)

- One-time quota: PBRa X TTIa

- Maximum quota: PBRa X BSDa

* When transmitting data belonging to a specific logical channel using TTI type b (corresponds to step 1 of the LCP procedure defined in LTE)

- One-time quota: PBRb X TTIb

- Maximum quota: PBRb X BSDb

<Action 4>

(1) The base station provides logical channel priority to the terminal in the same way as LTE. This can be done through LogicalChannelConfig IE during RRC signaling.

(2) The base station grants the terminal the right to repeatedly transmit data belonging to a specific logical channel within a predetermined time. This setting can also be made through LogicalChannelConfig IE as shown below.

A. Repetitive transmission as used herein means that data belonging to a specific logical channel is transmitted when UL grant is allocated, and then transmitted again when the next UL grant is allocated, independently of HARQ and ACK/NACK feedback.

B. More specifically, the base station may perform the following settings to the terminal.

i. Whether to allow repeated transmission of data belonging to a specific logical channel

ii. Maximum time interval allowed for repeated transmission of data belonging to a specific logical channel

iii. Maximum number of repeated transmissions of data belonging to a specific logical channel

- LogicalChannelConfig

The IE LogicalChannelConfig is used to configure the logical channel parameters.

LogicalChannelConfig information element

-- ASN1START

LogicalChannelConfig ::= SEQUENCE {

ul-SpecificParameters SEQUENCE {

priority INTEGER (1..16),

allowRepeatedTransmission BOOLEAN OPTIONAL -- Need ON

allowRepeatedTransmissionTimer ENUMERATED {sf1, sf2, sf4, sf8, sf16, spare1, spare2}, OPTIONAL -- Need ON

maxRepeatedTransmission INTEGER (1..16), OPTIONAL -- Need ON

prioritisedBitRate ENUMERATED {

kBps0, kBps8, kBps16, kBps32, kBps64, kBps128,

kBps256, infinity, kBps512-v1020, kBps1024-v1020,

kBps2048-v1020, spare5, spare4, spare3, spare2,

spare1},

bucketSizeDuration ENUMERATED {

ms50, ms100, ms150, ms300, ms500, ms1000, spare2,

spare1},

logicalChannelGroup INTEGER (0..3) OPTIONAL -- Need OR

} OPTIONAL, -- Cond UL

...,

[[ logicalChannelSR-Mask-r9 ENUMERATED {setup} OPTIONAL -- Cond SRmask

]],

[[ logicalChannelSR-Prohibit-r12 BOOLEAN OPTIONAL -- Need ON

]]

}

-- ASN1STOP

[Table 5]

(3) If the base station permits repeated transmission of data belonging to a specific logical channel, the UE performs repeated transmission in consideration of the maximum time period during which repeated transmission is allowed and the maximum number of possible repeated transmissions.

10 is a diagram illustrating an example for explaining operation 4 proposed according to the first embodiment of the present invention.

i. The base station allowed repeated transmission for logical channel A to the terminal. In addition, the maximum time interval allowed for repeated transmission was set to 5 normal TTI, and the maximum number of times for repeated transmission was set to 3 times.

Referring to FIG. 10, the UE fills the UL grant allocated at the time T1 with data of logical channel A and transmits it for the first time. After that, when the UL grant is received within 5 normal TTI, which is the maximum time interval for which repeated transmission is allowed, if the maximum number of repeated transmissions does not exceed 3 times, the data of logical channel A transmitted at the time T1 is the UL allocated at the time T2. It can be transmitted after refilling the grant. The same operation can be applied to the UL grant allocated at the time T3 in the same principle.

<Correspondence between Logical Channel and TTI>

In operations 2 and 3 described above, the base station provides information on the priority (priorityForTTIType1, priorityForTTIType2, etc.) of the logical channel for each TTI type to the UE and the priority between different TTI types (TTIType, priorityAmongTTIType, etc.) through the LogicalChannelConfig IE. . Here, it can be interpreted that the terminal uses only the TTI type included in the LogicalChannelConfig IE of the specific logical channel provided by the base station when transmitting and receiving data belonging to a specific logical channel. In other words, it can be seen that the base station designates the TTI type that the terminal can use to transmit and receive data belonging to the corresponding logical channel through the LogicalChannelConfig IE. This point has been mentioned in the descriptions of operations 2 and 3, but will be described in more detail in this section.

11 is a diagram illustrating a hard split between a logical channel and a TTI proposed according to the first embodiment of the present invention.

(1) Hard split-based approach (FIG. 11)

- Assume that the base station supports six logical channels {1, 2, 3, 4, 5, 6} and two TTI types {A, B} to the terminal.

- The UE can use only TTI type A when transmitting data belonging to logical channel {1, 2, 3}. That is, data belonging to logical channel {1, 2, 3} cannot be transmitted using TTI type B.

- The UE can use only TTI type B when transmitting data belonging to logical channel {4, 5, 6}. That is, data belonging to logical channel {4, 5, 6} cannot be transmitted using TTI type A.

-

12 is a diagram illustrating a soft split between a logical channel and a TTI proposed according to the first embodiment of the present invention.

(2) Soft split-based approach (Fig. 12)

- Assume that the base station supports six logical channels {1, 2, 3, 4, 5, 6} and two TTI types {A, B} to the terminal.

- The UE may use one, some, or all of the TTI types {A, B} when transmitting data belonging to the logical channel {1, 2, 3, 4, 5, 6}.

13 is a diagram illustrating a hybrid split between a logical channel and a TTI proposed according to the first embodiment of the present invention from the viewpoint of a logical channel.

(3) Hybrid approach (FIG. 13)

- Assume that the base station supports 9 logical channels {1, 2, 3, 4, 5, 6, 7, 8, 9} and 3 TTI types {A, B, C} to the terminal.

- TTI type A can be used when transmitting data belonging to logical channel {1, 2, 3}.

- TTI type B can be used to transmit data belonging to any logical channel among logical channels {1, 2, 3, 4, 5, 6, 7, 8, 9}.

- TTI type C can be used when transmitting data belonging to logical channel {4, 5, 6, 7, 8, 9}.

14 is a diagram illustrating a hybrid split between a logical channel and a TTI proposed according to the first embodiment of the present invention from the viewpoint of TTI.

- Data belonging to the logical channel {1, 2, 3} can be transmitted/received by TTI type A.

- Data belonging to the logical channel {4, 5, 6} can be transmitted/received through all TTI types.

- Data belonging to the logical channel {7, 8, 9} may be transmitted/received according to the TTI type {B, C}.

In order to realize the hard split-based approach, soft split-based approach, and hybrid approach operations described so far, when the base station notifies the terminal of information about logical channel configuration, the TTI type that can be used to transmit and receive data included should be informed together. This can be reported through LogicalChannelConfig IE as follows. It can be seen that the LogicalChannelConfig IE mentioned in the description of operations 2 and 3 also additionally includes priority information about the logical channel along with this information.

The base station may inform the terminal of the type of TTI through which data belonging to each logical channel can be transmitted through methods other than the use of the LogicalChannelConfig IE described above.

<Action 5>

(1) The base station provides a plurality of logical channel priority sets to the terminal. This can be done through LogicalChannelConfig IE during RRC signaling.

A. For example, logical channel priority set 1 provides priority in the order of A > B > C > D, and logical channel priority set 2 provides priority in the order of C > D > A > B.

B. The LogicalChannelConfig IE below shows how a plurality of logical channel priority sets are configured.

(2) The base station provides a logical channel priority set ID applied to the UL grant when allocating the UL grant to the terminal. This may be accomplished through DCI transmitted through the PDCCH, or the like.

A. The table below shows an example of notifying the logical channel priority set ID applied to the UL grant when the base station allocates a UL grant to the terminal.

(3) Through the processes of (1) and (2) above, the UE was provided with a plurality of logical channel priority sets and logical channel priority set IDs corresponding to UL grants. Based on this, the terminal operates as follows.

A. The UE checks the logical channel priority set ID specified in the UL grant and checks the corresponding logical channel priority.

B. The UE fills the UL grant with data currently in the buffer according to the logical channel priority confirmed above.

15 is a diagram illustrating a method in which a base station notifies a terminal of an LCP set through a UL grant according to the first embodiment of the present invention.

(1) The base station provides a plurality of logical channel priority (LCP) sets 1 and 2 to the terminal. Here, the logical channel priority of logical channel priority set 1 is set to A > B > C > D, and the logical channel priority of logical channel priority set 2 is set to C > D > A > B.

(2) The base station provides a logical channel priority set ID applied to the UL grant when allocating the UL grant to the terminal.

A. When the logical channel priority set ID applied to the UL grant is 1, in the order of priority A > B > C > D, the resources allocated to the UL grant through the LCP operation are filled.

B. When the logical channel priority set ID applied to the UL grant is 2, in the order of priority C > D > A > B, the resources allocated to the UL grant through the LCP operation are filled.

In operation (1) above, the base station may provide logical channel priority information for each type of TTI to the terminal. In the present invention, it is considered that, in addition to logical channel priority information, PBR (Prioritized Bit Rate) and BSD (Bucket Size Duration) information can also be provided by the base station to the terminal for each TTI type through RRC signaling, etc. Therefore, the UE applies different PBRs (PBRa and PBRb) and different BSDs (BSDa and BSDb) when transmitting data belonging to the same logical channel using TTI type a and TTI type b. The roles of PBR and BSD are considered the same as those of existing LTE. That is, it works as follows.

- When data belonging to a specific logical channel is transmitted using TTI type a (corresponds to step 1 of the LCP procedure defined in LTE)

- One-time quota: PBRa X TTIa

- Maximum quota: PBRa X BSDa

- When data belonging to a specific logical channel is transmitted using TTI type b (corresponds to step 1 of the LCP procedure defined in LTE)

- One-time quota: PBRb X TTIb

- Maximum quota: PBRb X BSDb

<Action 6>

Operations 1 to 5 described so far can be seen as operations in which the base station determines priorities among logical channels to be used by the terminal. In operation 6, an operation in which the terminal proactively selects an LCP to be used will be described.

(1) The base station provides a plurality of logical channel priorities to the terminal. As an example, the logical channel priority provided to the terminal can be viewed as a logical channel priority optimized for each TTI type currently operated by the base station. This can be done through LogicalChannelConfig IE during RRC signaling.

A. For example, the base station sets and provides one logical channel priority set in the order of logical channel A > B > C > D to the terminal and additionally sets and provides one logical channel priority set in the order of C > D > A > B . For example, logical channel priority set A > B > C > D is a priority that is easy to apply to a normal-length TTI, and logical channel priority set C > D > A > B is a priority that is easy to apply to a short-length TTI. can

B. The following LogicalChannelConfig IE shows an example in which the base station provides a plurality of logical channel priority sets to the terminal.

(2) When the terminal requests a UL resource from the base station (when transmitting a scheduling request signal or when transmitting a buffer status report MAC CE, etc.) Notify the base station.

(3) In step (2), the base station receiving the preferred logical channel priority set ID information from the UE is a resource (for example, a resource having a short TTI or a long TTI) that is easy to apply the logical channel priority indicated by the corresponding set ID. After selecting a resource with , it is allocated to the UE through a UL grant.

(4) In step (3), the terminal, which has been allocated resources through the UL grant from the base station, performs LCP and transmits data after generating data according to the logical channel priority indicated by the logical channel priority set ID that it informs to the base station.

16 is a diagram illustrating a method in which a terminal notifies a preferred LCP set to a base station through a scheduling request according to the first embodiment of the present invention. 16 corresponds to an example of operation 6 .

It has been explained that in step (2) above, the terminal provides the base station with information on its preferred logical channel priority in the form of set ID, etc. In addition, it was explained that this information is provided when a scheduling request signal is transmitted or when a buffer status report MAC CE is transmitted. In the present invention, it is considered that the terminal may provide information on the logical channel priority set ID preferred by the terminal to the base station through various methods. Below is an example of this.

- The preferred logical channel priority set ID is included in the Buffer status report MAC CE.

- Newly defined MAC CE including preferred logical channel priority set ID information.

- Allocate a plurality of scheduling request signals to the UE and associate each scheduling request signal with each preferred logical channel priority set ID. Therefore, when the base station receives a specific scheduling request signal, it can find out the preferred logical channel priority set ID of the terminal according to the type of the scheduling request signal.

- Allocate one scheduling request signal to the UE, classify time or frequency resources that can transmit the scheduling request signal, and associate each time or frequency resource with each preferred logical channel priority set ID. Therefore, even if the terminal always transmits the same scheduling request signal, the base station can find out the preferred logical channel set ID of the terminal according to the received time or frequency resource.

In operation (1) above, the base station provided priority information for each TTI type to the terminal. In the present invention, it is considered that, in addition to priority information, PBR (Prioritized Bit Rate) and BSD (Bucket Size Duration) information can also be provided by the base station to the terminal for each TTI type through RRC signaling or the like. Therefore, the UE applies different PBRs (PBRa and PBRb) and different BSDs (BSDa and BSDb) when transmitting data belonging to the same logical channel using TTI type a and TTI type b. The roles of PBR and BSD are considered the same as those of existing LTE. That is, it works as follows.

- When data belonging to a specific logical channel is transmitted using TTI type a (corresponds to step 1 of the LCP procedure defined in LTE)

- One-time quota: PBRa X TTIa

- Maximum quota: PBRa X BSDa

- When data belonging to a specific logical channel is transmitted using TTI type b (corresponds to step 1 of the LCP procedure defined in LTE)

- One-time quota: PBRb X TTIb

- Maximum quota: PBRb X BSDb

<Action 7>

In this operation, when the UE is allocated a UL resource through the UL grant, the overall operation of including data in the UL resource allocated through the LCP will be described. Basically, it is based on the LCP operation of LTE described above. In this operation, we focus on how the LCP operation of LTE should be improved when a plurality of logical channels and a plurality of TTIs exist.

First, as shown in FIG. 11, when hard split, that is, logical channels {1, 2, 3} is set to use only TTI type A, and logical channels {4, 5, 6} are set to use only TTI type B, LTE It is enough to apply the LCP operation of That is, when data belonging to logical channel {1, 2, 3} is included in the UL resource corresponding to TTI type A, the LCP operation of LTE may be applied as it is, and data belonging to logical channel {4, 5, 6} is TTI When included in the UL resource corresponding to type B, the LCP operation of LTE may be applied as it is. More specifically, it operates as follows.

(1) The terminal fills data belonging to LCH 1 as much as PBR1 * TTIA.

A. Here, it is assumed that the order of priority among LCH {1, 2, 3} is 1 > 2 > 3.

B. In addition, data belonging to LCH 1 can be filled as much as the maximum total PBR1 * BSDA.

(2) If the allocated UL resource remains after the process (1) is performed, data belonging to LCH 2 is filled as much as PBR2 * TTIA.

(3) If the allocated UL resources remain after the process (2) is performed, data belonging to LCH 3 is filled by PBR3 * TTIA.

(4) If the allocated UL resource remains after the process (3) is performed, all remaining data of LCH 1 is filled in the allocated resource.

(5) If allocated resources remain after performing step (4), all remaining data of LCH 2 is filled in allocated resources.

(6) If allocated resources remain after performing step (5), all remaining data of LCH 3 is filled in allocated resources.

(7) If all the allocated UL resources are exhausted while performing the above process, the entire operation is terminated.

The above operation can be equally applied to LCH {4, 5, 6} and TTI type B.

Next, as shown in FIG. 12, soft split, that is, LCH {1, 2, 3} and {4, 5, 6} can use both TTI type A and B, but for TTI type A, LCH {1, 2, 3} Consider a case where {4, 5, 6} has a higher priority and LCH {4, 5, 6} has a higher priority than {1, 2 3} for TTI type B. In this case, two operations are possible as follows.

First, when the UE includes data to be transmitted in the UL resource corresponding to TTI type A, the LCP operation of LTE is applied as it is after setting priorities between LCHs as follows. More specifically, it operates as follows.

(1) The UE fills data belonging to LCH 1 as much as PBR1,A * TTIA.

A. Here, it is assumed that the priorities between LCH {1, 2, 3, 4, 5, 6} are 1 > 2 > 3 > 4 > 5 > 6.

B. Here, PBR1,A means PBR applied when data belonging to LCH 1 is included in data belonging to TTI type A.

C. In addition, data belonging to LCH 1 can be filled as much as the maximum total PBR1,A * BSDA in LCP step 1.

(2) If the allocated UL resources remain after the process (1) is performed, data belonging to LCH 2 is filled with PBR2,A * TTIA.

(3) If the allocated UL resources remain after performing step (2), data belonging to LCH 3 is filled with PBR3,A * TTIA as much as PBR3,A * TTIA.

(4) If the allocated UL resources remain after the process (3) is performed, data belonging to LCH 4 is filled with PBR4,A * TTIA.

(5) If the allocated UL resources remain after the process (4) is performed, data belonging to LCH 5 is filled as much as PBR5,A * TTIA.

(6) If the allocated UL resource remains after performing step (5), data belonging to LCH 6 is filled with PBR6,A * TTIA.

(7) If allocated UL resources remain after performing step (6), all remaining data of each LCH is filled in the allocated UL resources in the order of priority between LCHs.

(8) If all the allocated UL resources are exhausted while performing the above process, the entire operation is terminated.

The above operation can be equally applied to LCH {1, 2, 3, 4, 5, 6} and TTI type B.

Second, when the UE includes data to be transmitted in the UL resource corresponding to TTI type A, the UL resource allocated after including all data belonging to the LCH {1, 2, 3} having a high priority for TTI type A Data belonging to LCH {4, 5, 6} may be included only in the remaining case. More specifically, it operates as follows.

(1) The UE fills data belonging to LCH 1 as much as PBR1,A * TTIA.

A. Here, it is assumed that the order of priority among LCH {1, 2, 3} is 1 > 2 > 3.

B. Here, PBR1,A means PBR applied when data belonging to LCH 1 is included in data belonging to TTI type A.

C. In addition, data belonging to LCH 1 can be filled as much as the maximum total PBR1,A * BSDA in LCP step 1.

(2) If the allocated UL resources remain after the process (1) is performed, data belonging to LCH 2 is filled with PBR2,A * TTIA.

(3) If the allocated UL resources remain after performing step (2), data belonging to LCH 3 is filled with PBR3,A * TTIA as much as PBR3,A * TTIA.

(4) If the allocated UL resources remain after performing step (3), all remaining data of each LCH is filled in the allocated UL resources in the order of priority 1 > 2 > 3 of LCH {1, 2, 3}. .

(5) If, after the process (4) is performed, that is, if the allocated UL resources remain despite all data belonging to LCH {1, 2, 3} being included in the allocated UL resources, LCH {4, 5, 6} Start filling in the data belonging to That is, data belonging to LCH 4 is filled as much as PBR4,A * TTIA.

A. Here, it is assumed that the priorities between LCHs {4, 5, 6} are 4 > 5 > 6 in the order.

(6) If the allocated UL resources remain after the process (5) is performed, data belonging to LCH 5 is filled as much as PBR5,A * TTIA.

(7) If the allocated UL resource remains after the process (6) is performed, data belonging to LCH 6 is filled as much as PBR6,A * TTIA.

(8) If the allocated UL resources remain after performing the process (7), the UL resources to which all remaining data of each LCH are allocated in the order of priority 4 > 5 > 6 of LCH {4, 5, 6} fill in

(9) If all the allocated UL resources are exhausted while performing the above process, the entire operation is terminated.

The above operation can be equally applied to TTI type B.

<Action 8>

In operation 8, a method for the base station to efficiently apply a default priority and a special (eg, TTI-specific) priority to the terminal will be described. This works as follows.

(1) The base station provides a plurality of logical channel priorities to the terminal. As an example, the logical channel priority provided by the base station to the terminal can be viewed as a logical channel priority optimized for each TTI type currently operated by the base station. This can be done through LogicalChannelConfig IE during RRC signaling.

A. For example, the base station may set the priority for TTI type 1 in the order of logical channel B > C > A. In addition, the base station may set the priority for TTI type 2 in the order of logical channel C > A > B.

(2) The base station provides a default logical channel priority to the terminal. Here, the default logical channel priority can be seen as a logical channel priority that can be applied regardless of the characteristics (eg, TTI length or numerology) of the UL resource allocated to the terminal by the base station. This can be done through LogicalChannelConfig IE during RRC signaling.

A. For example, the base station can set the default priority in the order of logical channel A > B > C.

B. The following LogicalChannelConfig IE provides the base station with a default logical channel priority that can be applied to the terminal, for example, regardless of the special logical channel priority and UL grant characteristics that can be applied to each TTI, for example, the TTI length. showing an example

(3) In addition, the base station includes a 1-bit indication indicating whether the default logical channel priority is applied when transmitting the UL grant to the terminal.

(4) The UE operates as follows in consideration of RRC configuration for the logical channel and whether the default logical channel priority included in the UL grant is applied.

A. If 1 bit indicating whether the default logical channel priority is applied in the UL grant is set to 1, the UE performs LCP according to the default logical channel priority set by the base station when transmitting data through the UL grant.

B. If 1 bit indicating whether or not the default logical channel priority is applied in the UL grant is set to 0, the UE transmits data through the UL grant according to the characteristics of the UL grant (eg, TTI) and a corresponding special ( Alternatively, LCP is performed according to TTI-specific) logical channel priority.

17 is a diagram illustrating a method for a base station to efficiently apply a default priority and a special priority to a terminal according to the first embodiment of the present invention. 17 corresponds to an example of operation 8 .

1) When the base station configures logical channels A, B, and C used by the terminal, as a TTI-specific logical channel priority for TTI type 1, B > C > A, TTI-specific logical channel for TTI type 2 It is set as C > A > B as priority. In addition, the default logical channel priority used regardless of the characteristics of the UL grant (eg, TTI) is set to A > B > C.

2) The terminal transmits a scheduling request signal to the base station to transmit UL data, and the base station transmits a UL grant including UL resource allocation information to the terminal. At this time, the UE operates as follows according to the indicator of whether the default logical channel priority is applied or not included in the UL grant. In this specification, for convenience of explanation, if the default logical channel priority indicator is 0, the default logical channel priority is not applied, and if the default logical channel priority application status indicator is 1, the default logical channel priority is applied. Depending on the specification, the indicator whether the default logical channel priority is applied may be set differently.

A. If the terminal is allocated a UL resource corresponding to TTI type 1 and the indicator indicating whether the default logical channel priority is applied or not is set to 0, when the terminal transmits data through the UL grant, the logical channel corresponding to TTI type 1 LCP is performed according to priority B > C > A.

B. If the terminal is allocated a UL resource corresponding to TTI type 2 and the indicator indicating whether the default logical channel priority is applied is set to 0, when the terminal transmits data through the UL grant, the logical channel corresponding to TTI type 2 LCP is performed according to priority C > A > B.

C. If the terminal is allocated a UL resource corresponding to TTI type 1 and the indicator indicating whether the default logical channel priority is applied or not is set to 1, when the terminal transmits data through the UL grant, the logical channel corresponding to TTI type 1 The priority B > C > A is ignored and LCP is performed according to the default logical channel priority A > B > C.

D. If the terminal is allocated a UL resource corresponding to TTI type 2 and the indicator indicating whether the default logical channel priority is applied or not is set to 1, when the terminal transmits data through the UL grant, the logical channel corresponding to TTI type 2 The priority C > A > B is ignored and LCP is performed according to the default logical channel priority A > B > C.

<Action 9>

In operation 9, after the base station allocates a TTI-specific priority to the terminal, in some cases, a method of granting a degree of freedom to the terminal's logical channel priority selection will be described. This works as follows.

(1) The base station provides a plurality of logical channel priorities to the terminal. As an example, the logical channel priority provided by the base station to the terminal can be viewed as a logical channel priority optimized for each TTI type currently operated by the base station. This can be done through LogicalChannelConfig IE during RRC signaling.

A. For example, the base station may set the priority for TTI type 1 in the order of logical channel B > C > A. In addition, the base station may set the priority for TTI type 2 in the order of logical channel C > A > B.

(2) In addition, when the base station transmits a UL grant to the terminal, the terminal includes a 1-bit indication that grants the right to select a logical channel priority without an indication of the base station.

(3) The UE operates as follows in consideration of the RRC configuration for the logical channel, that is, the TTI-specific logical channel priority and whether the UE has the right to select the logical channel priority of the UE included in the UL grant.

A. If 1 bit, which means whether or not the UE is authorized to select logical channel priority in the UL grant, is set to 0, the UE transmits data through the UL grant according to the characteristics of the UL grant (eg, TTI) and corresponding LCP is performed according to a special (or TTI-specific) logical channel priority.

B. If 1 bit indicating the presence or absence of the right to select the logical channel priority of the terminal in the UL grant is set to 1, the terminal performs LCP according to the logical channel priority set by the terminal itself when transmitting data through the UL grant.

18 is a diagram illustrating a method in which a base station assigns a degree of freedom to a terminal's logical channel priority selection after allocating a TTI-specific priority to a terminal according to the first embodiment of the present invention. 18 corresponds to an example of operation 9 .

1) When the base station configures logical channels A, B, and C used by the terminal, as a TTI-specific logical channel priority for TTI type 1, B > C > A, TTI-specific logical channel for TTI type 2 It is set as C > A > B as priority.

2) The terminal transmits a scheduling request signal to the base station to transmit UL data, and the base station transmits a UL grant including UL resource allocation information to the terminal. At this time, the UE operates as follows according to the indicator of whether or not the UE is authorized to set the logical channel priority included in the UL grant. In this specification, for convenience of explanation, if the logical channel priority setting authority indicator is 0, the terminal does not have the logical channel priority setting authority, and if the logical channel priority setting authority presence indicator is 1, it is set as having the logical channel priority setting authority of the terminal. , the logical channel priority setting authority indicator can be set in various ways according to design specifications.

A. If the terminal is allocated a UL resource corresponding to TTI type 1 and the terminal's logical channel priority setting authority indicator is set to 0, when the terminal transmits data through the UL grant, the logical channel corresponding to TTI type 1 LCP is performed according to the priority B > C > A.

B. If the terminal is allocated a UL resource corresponding to TTI type 2 and the terminal's logical channel priority setting authority indicator is set to 0, when the terminal transmits data through the UL grant, the logical channel corresponding to TTI type 2 LCP is performed according to priority C > A > B.

C. If the terminal is allocated a UL resource corresponding to TTI type 1 and the terminal's logical channel priority setting authority indicator is set to 1, when the terminal transmits data through the UL grant, the logical channel corresponding to TTI type 1 The priority B > C > A is ignored and LCP is performed according to the logical channel priority A > B > C set by the terminal itself.

<Action 10>

In the present invention, various methods for performing an LCP operation after the UE applies different logical channel priorities to UL resources having different TTIs have been proposed. Here, the TTI is one of the physical properties of the UL resource allocated by the base station to the terminal through the UL grant. Accordingly, the UL resource allocated by the base station to the terminal may be distinguished by the TTI of the corresponding resource or may be distinguished by other attributes other than the TTI. It may also be distinguished by a combination of TTI or other attributes. In operation 10, various examples of classifying UL resources will be described.

(1) UL resources may be classified by TTI.

- Here, the TTI length may be a subframe length, a slot length, a mini-slot length, and a transmission period of a control channel such as an LTE PDCCH. For example, some of the values expressed in various ways such as 1/2 m ms, i.e. 1 ms (m = 0), 0.5 ms (m = 1), 0.25 ms (m = 2), 0.125 ms (m = 3), etc. can be

(2) UL resources may be classified by subcarrier spacing.

- Here, as an example of subcarrier spacing, 15*2m kHz, that is, 15 kHz (m = 0), 30 kHz (m = 1), 60 kHz (m = 2), 120 kHz (m = 3), etc. may be 15 *n kHz, i.e. 15 kHz (n = 1), 30 kHz (n = 2), 45 kHz (n = 3), 60 kHz (n = 4), etc. can be some of the values expressed in various ways.

(3) UL resources may be distinguished by a CP (Cyclic Prefix) length.

- Here, the CP length is determined in consideration of aspects such as performance and overhead, and for example, it may be a part of several values such as 4.7 us, 0.9 us, 0.1 us, etc.

(4) UL resources can be classified according to the modulation/coding method and coding rate to be applied to the corresponding resource.

- The base station informs the modulation/coding method applied to the corresponding resource through the UL grant when allocating the UL resource to the terminal, and the terminal can classify the UL resource allocated to it based on this.

(5) UL resources may be classified by the number of OFDM symbols included in a certain unit (eg, 1 ms, subframe, slot, mini-slot, TTI, etc.).

- Here, the number of OFDM symbols included in a certain unit may be 14, 70, 560, etc. depending on the case.

- Here, as an additional example of a predetermined unit (eg, 1 ms, subframe, slot, mini-slot, TTI, etc.), the transmission time required for the allocated resource may be included. The transmission required time of the allocated resource refers to the total number of symbols from the first OFDM symbol to the last OFDM symbol allocated to the terminal when the base station allocates a data channel, ie, PUSCH or PDSCH, to the terminal.

(6) UL resources can be divided by OFDM symbol length.

(7) UL resources can be divided by the bandwidth occupied by the resource.

(8) UL resources are (i) UL grant-based resources that the base station allocates by transmitting UL resource allocation information, i.e., UL grant, through a control channel such as PDCCH to the terminal when each resource is allocated, or (ii) every resource allocation Instead of a method in which the base station transmits a UL grant to the terminal and allocates UL resources, regardless of whether data is generated by the terminal, UL resources are allocated periodically through RRC signaling in advance, and when data is generated, the resources allocated in this way It can be classified according to whether it is a UL grant-free based resource using Accordingly, the base station may configure the UE to transmit and receive data generated in a specific logical channel through a UL grant-based resource, and data generated in another logical channel may be configured to be transmitted/received through a UL grant-free based resource.

(9) UL resources are (i) whether there is no possibility of collision that occurs when multiple terminals simultaneously perform UL transmission on the same resource because the resource is allocated exclusively to one terminal, or whether the resource is allocated to a plurality of terminals It can be classified according to whether there is a possibility of collision that occurs when multiple terminals simultaneously transmit on the same resource because they are commonly allocated. Accordingly, the base station can set the terminal to transmit and receive data generated in a specific logical channel through a UL resource that is allocated exclusively to one terminal and has no possibility of collision, and data generated in another logical channel is allocated to a plurality of terminals and collides It can be configured to be transmitted/received through a possible UL resource.

(10) UL resources may be classified by a transmission period of a control channel to which the resource is allocated. Here, the transmission period of the control channel to which the UL resource is allocated includes a PDCCH transmission period of the base station, a PDCCH monitoring periodicity of the terminal, and a control resource set (CORESET) observation period set by the base station for the terminal. This may be expressed in units such as symbol or mini-slot or slot or subframe.

(11) The UL resource may be classified by comprehensively considering the transmission period of the control channel to which the resource is allocated and the time length of the allocated UL resource. In the present invention, as a method for classifying the control channel to which UL resources are allocated and the time length of the allocated UL resources in consideration of comprehensively, the method for classifying them is the greater of the transmission period of the control channel to which UL resources are allocated and the time length of the allocated UL resources. A method of classifying UL resources based on values is proposed. As an example, if the transmission period of the control channel to which the UL resource is allocated is 7 symbols and the time length of the allocated UL resource is 2 symbols, the corresponding UL resource is according to the 7 symbol, which is the transmission period of the control channel to which the UL resource is allocated. are separated As another example, if the transmission period of the control channel to which the UL resource is allocated is 3 symbols and the time length of the allocated UL resource is 14 symbols, the corresponding UL resource is divided according to 14 symbols, which is the time length of the allocated UL resource. The table below shows an example of a UL resource classification method proposed by the present invention.

In the above example, the Type A UL resource refers to a resource in which the larger value of the standard value for UL resource classification, that is, the transmission period of the control channel for allocating the UL resource and the time length of the allocated UL resource, is 1 symbol or 2 symbol. . In addition, the Type B UL resource refers to a resource having a value of 3 to 14 symbols as a criterion for UL resource classification. In addition, the Type C UL resource refers to a resource whose standard value for UL resource classification exceeds 14 symbols. This corresponds to one example. The present invention includes a method for the base station to provide the terminal with an index of a logical channel that can be transmitted according to the type of UL resource, that is, whether it is Type A, Type B, or Type C. In this example, in the Type A UL resource, data generated on LCH 1, LCH 2, and LCH 3 may be transmitted, in the Type B UL resource, data generated on LCH 2 and LCH 3 may be transmitted, and in the Type C resource, data generated on LCH 3 may be transmitted. The situation in which the generated data can be transmitted has been described. The classification of the UL resources and the correspondence relationship with the LCH can prevent a case in which data generated in a specific LCH is transmitted through a UL resource that is not suitable for transmission thereof as much as possible.

In the present invention, all operations proposed in the present invention, such as assigning an ID to each type of UL resource classified according to the above criteria and performing LCP operation by applying different logical channel priorities to each ID, can be made possible. Therefore, although this document has focused on performing LCP operation by applying different logical channel priorities to each UL resource divided according to TTI, in addition to subcarrier spacing, CP length, modulation/coding method and coding rate, OFDM symbol It is also possible to perform the LCP operation by applying different logical channel priorities to each UL resource divided by criteria such as the number, OFDM symbol length, and bandwidth of the allocated resource block. In the present invention, an operation of assigning an ID to each UL resource type and applying a different logical channel priority to each ID has been described. In the present invention, when applying the same logical channel priority as well as a different logical channel priority for each ID also includes Applying the same logical channel priority to each ID is considered to be included in a special example of applying a different logical channel priority to each ID.

Also, in the present invention, an ID is assigned to each UL resource type divided by two or more criteria among the attributes of the UL resource mentioned above, and LCP operation is performed by applying a different logical channel priority to each ID. All suggested actions can be made possible.

As an example, the base station classifies UL resources based on TTI and subcarrier spacing among various attributes of UL resources, and then assigns IDs to the types of UL resources as follows.

- TTI types currently used by base stations: 1 ms, 0.5 ms, 0.25 ms

- Subcarrier spacing currently used by the base station: 15 kHz, 30 kHz, 60 kHz

- Classification of UL resources according to TTI and subcarrier spacing

As described above, the base station classifies UL resources based on TTI and subcarrier spacing and assigns IDs to each UL resource type. Based on this, the base station can set a correspondence between the UL resource corresponding to each ID and a logical channel that can be transmitted through it. In addition, the base station may set the priority between logical channels that can be transmitted through the UL resource corresponding to each ID. An example of this is as follows.

- TTI types currently used by base stations: 1 ms, 0.5 ms, 0.25 ms

- Subcarrier spacing currently used by the base station: 15 kHz, 30 kHz, 60 kHz

- Type of logical channel currently assigned to UE: LCH A, B, C, D

- Example of correspondence and priority between each ID and logical channel

According to the table above, logical channels A, B, and C can be transmitted through a UL resource having a TTI length of 1 ms and a subcarrier spacing of 15 kHz or 30 kHz or 60 kHz. In this case, the priority between logical channels is A > The order is B > C. In addition, logical channels A, B, and C may be transmitted through a UL resource having a TTI length of 0.5 ms and a subcarrier spacing of 15 kHz or 30 kHz, and in this case, the priority between logical channels is A > B > C. In addition, logical channels B, C, and D may be transmitted through a UL resource having a TTI length of 0.5 ms and a subcarrier spacing of 60 kHz. In this case, the priority between logical channels is D > C > B. In addition, logical channels B, C, and D can be transmitted through a UL resource having a TTI length of 0.25 ms and a subcarrier spacing of 15 kHz or 30 kHz or 60 kHz. becomes

Another example is:

- TTI types currently used by base stations: 1 ms, 0.5 ms, 0.25 ms

- Subcarrier spacing currently used by the base station: 15 kHz, 30 kHz, 60 kHz

- Type of logical channel currently assigned to UE: LCH A, B, C, D

- Example of correspondence and priority between each ID and logical channel

According to the table above, logical channels A and B can be transmitted through a UL resource having a TTI length of 1 ms and a subcarrier spacing of 15 kHz or 30 kHz or 60 kHz. becomes In addition, logical channels A and B may be transmitted through a UL resource having a TTI length of 0.5 ms and a subcarrier spacing of 15 kHz or 30 kHz, and in this case, the priority between logical channels is in the order of A > B. In addition, logical channels C and D may be transmitted through a UL resource having a TTI length of 0.5 ms and a subcarrier spacing of 60 kHz, and in this case, the priority between logical channels becomes C > D. In addition, logical channels C and D may be transmitted through a UL resource having a TTI length of 0.25 ms and a subcarrier spacing of 15 kHz or 30 kHz or 60 kHz, and in this case, the priority between logical channels becomes C > D.

In this example, it is assumed that the priorities between logical channels are set in the order of A > B > C > D for all logical channels. Therefore, when logical channels A and B are transmittable, the priorities are set in the order of A > B based on the priorities among all logical channels, and when logical channels C and D are transmittable, the priorities are set based on the priorities among all logical channels. Priority is set in the order of C > D.

In the above example, classification of UL resources according to TTI and subcarrier spacing, correspondence between UL resources and logical channels, priority between logical channels, etc. have been described. In the present invention, without being limited thereto, UL resources are divided as in the example above for any combination of {TTI, subcarrier spacing, CP length, modulation/coding method and coding rate, number of OFDM symbols, OFDM symbol length, bandwidth, etc.} and setting the correspondence between the UL resource and the logical channel, and setting the priority between the logical channels. The content proposed in the present invention, that is, TTI, subcarrier spacing, CP length, modulation/coding method, and coding rate. , the number of OFDM symbols, OFDM symbol length, bandwidth, etc., information necessary for classification of UL resources according to the base station provides to the terminal through RRC signaling. More specifically, this information may be transmitted through a LogicalChannelConfig IE (Information Element) that provides parameters and configuration information related to a specific logical channel. For convenience, let's call the type of UL resource through which data generated in a specific logical channel can be transmitted 'profile'. And, as an example, the type of UL resource through which the logical channel can be transmitted is subcarrier spacing, time length, cell or component carrier to which the UL resource belongs, whether the UL resource is a resource allocated in a UL grant-free scheme, or UL grant- Assume that it is classified according to whether or not it is a resource allocated in the based method. Here, the length of time may be one of the TTI proposed in the present invention or the number of OFDM symbols included in a predetermined unit.

The following shows LogicalChannelConfig for a specific logical channel. Here, the specific logical channel specifies which UL resource can be transmitted/received among UL resources divided by subcarrier spacing, time length, UL resource allocation method, cell to which the UL resource belongs, and the like.

- In this example, subcarrier spacing is specified as ‘subcarrierSpacing’. In this example, one of 15 kHz, 30 kHz, 60 kHz, and 120 kHz may have a value, which is only an example and other values may be used in the present invention.

- In this example, the length of time is specified as ‘timeParameter’. In this example, it may have one of 0.125 ms, 0.25 ms, 0.5 ms, and 1 ms, and this is just one example and other values may be used in the present invention. Here, the meaning of the length of time may be as follows.

- When the UL resource of the TTI having a value smaller than 'timeParameter' is allocated, the corresponding logical channel may be transmitted/received through the corresponding UL resource.

- When a UL resource is allocated for a time corresponding to the number of OFDM symbols included in a certain unit (eg, allocated UL resource) (ie, the number of OFDM symbols times the length of an OFDM symbol) is shorter than 'timeParameter', the corresponding logical channel may be transmitted/received through the corresponding UL resource.

- Refers to the time of a specific TTI

- Refers to a specific value of the time (ie, the number of OFDM symbols multiplied by the OFDM symbol time length) corresponding to the number of OFDM symbols included in a certain unit (eg, the allocated UL resource)

- In this example, the UL resource allocation method is specified as 'ulGrantMode'. In this example, it can have one of the values 'ulGrantBased', 'ulGrantFree', and 'both'. 'ulGrantBased' means that the logical channel can transmit and receive through the UL resource allocated in the UL grant-based method. In addition, 'ulGrantFree' means that the logical channel can transmit and receive through the UL resource allocated in the UL grant-free method. In addition, 'both' means that the logical channel can transmit and receive through UL resources allocated in UL grant-based and UL grant-free schemes.

- In this example, the cell to which the UL resource belongs is specified as 'allowedCellList'. This corresponds to an index list of serving cells that can be used to transmit/receive the corresponding logical channel among the serving cells currently being used.

- Example 1 below expresses the resource type (in this document, the UL resource type is called profile) by a combination of subcarrier spacing, timeParameter, ulGrantMode, and allowedCellList. In addition, Example 2 expresses the resource type through a combination of subcarrier spacing, timeParameter, and ulGrantMode and an allowedCellList set separately. In addition, Example 3 expresses the resource type through a combination of subcarrier spacing and timeParameter and separately set ulGrantMode and allowedCellList. In addition to these examples, the present invention allows other types of UL resource type expression methods.

The examples described so far show a case in which the LogicalChannelConfig IE includes all the characteristics of a UL resource through which data generated in a specific logical channel can be transmitted is included in the LogicalChannelConfig IE. As another example, the LogicalChannelConfigIE includes an identifier of a UL resource through which data generated in a specific logical channel can be transmitted, and an example in which the attribute of the UL resource having the corresponding identifier is described in a separate IE is also possible. A more specific ID form is as follows.

----- (a) When the LogicalChannelConfig IE includes only the ID of the profile (composed of subcarrierSpacing, timeParameter, ulGrantMode, and allowedCellList) and the parameters constituting the profile ID are transmitted through a separate IE -----

In the above IE, applicableProfileIdList is a list of applicableProfileId, where applicableProfileId is simply an integer and the details indicated by that integer are described in ApplicableProfile IE. In this example, ApplicableProfile IE includes subcarrierSpacing, timeParameter, ulGrantMode, and allowedCellList.

----- When the LogicalChannelConfig IE includes the ID of the profile (composed of subcarrierSpacing, timeParameter, and ulGrantMode) and a separate allowedCellList, and the parameters constituting the profile ID are transmitted through a separate IE -----

In the above IE, applicableProfileIdList is a list of applicableProfileId, where applicableProfileId is simply an integer and the details indicated by that integer are described in ApplicableProfile IE. In this example, ApplicableProfile IE includes subcarrierSpacing, timeParameter, and ulGrantMode. allowedCellList information is included in LogicalChanneConfig separately from ApplicableProfile.

----- When the LogicalChannelConfig IE includes the ID of the profile (composed of subcarrierSpacing and timeParameter) and separate ulGrantMode and allowedCellList, and the parameters constituting the profile ID are transmitted through a separate IE -----

In the above IE, applicableProfileIdList is a list of applicableProfileId, where applicableProfileId is simply an integer and the details indicated by that integer are described in ApplicableProfile IE. In this example, ApplicableProfile IE includes subcarrierSpacing and timeParameter. ulGrantMode and allowedCellList information is included in LogicalChanneConfig separately from ApplicableProfile.

<Action 11>

In operation 11, a modified method for the base station to efficiently apply the default priority and special (eg, TTI-specific) priority to the terminal will be investigated. This works as follows.

(1) The base station provides a plurality of logical channel priorities to the terminal. As an example, the logical channel priority provided by the base station to the terminal can be viewed as a logical channel priority optimized for each TTI type currently operated by the base station. This can be done through LogicalChannelConfig IE during RRC signaling.

A. For example, the base station may set the priority for TTI type 3 in the order of logical channel B > C > A.

(2) The base station provides a default logical channel priority to the terminal. Here, the default logical channel priority can be seen as a logical channel priority used except when the base station assigns a special logical channel priority. This can be done through LogicalChannelConfig IE during RRC signaling.

A. For example, the base station may set the default priority in the order of logical channel A > B > C.

B. The following LogicalChannelConfig IE shows an example in which the base station provides a special (TTI-specific) logical channel priority and a default logical channel priority to the terminal.

(3) The UE operates as follows in consideration of the RRC configuration for the logical channel and the characteristics (eg, TTI) of the UL resources allocated through the UL grant.

A. If a UL resource configured with a TTI configured with a special logical channel priority is allocated, the UE performs LCP according to the special logical channel priority set by the base station when transmitting data through the corresponding UL grant.

B. If a UL resource configured with a TTI for which special logical channel priority is not set is assigned, the UE performs LCP according to the default logical channel priority set by the base station when transmitting data through the corresponding UL grant.

19 is a diagram illustrating a modified method in which a base station efficiently applies a default priority and a special priority to a terminal according to the first embodiment of the present invention. 19 corresponds to an example of operation 11 .

1) When the base station configures logical channels A, B, and C used by the terminal, B > C > A as the TTI-specific logical channel priority for TTI type 3 is determined. Also, the default logical channel priority is set to A > B > C.

2) The terminal transmits a scheduling request signal to the base station to transmit UL data, and the base station transmits a UL grant including UL resource allocation information to the terminal. At this time, according to the characteristics of the UL resource allocated through the UL grant, for example, TTI, the UE operates as follows.

A. If the UE is allocated a UL resource corresponding to TTI type 1, the UE performs LCP according to the default logical channel priority A > B > C when transmitting data through the UL grant.

B. If the UE is allocated a UL resource corresponding to TTI type 2, the UE performs LCP according to the default logical channel priority A > B > C when transmitting data through the UL grant.

C. If the UE is allocated a UL resource corresponding to TTI type 3, the UE performs LCP according to B > A > C, which is a special logical channel priority corresponding to TTI type 3, when transmitting data through the UL grant.

<Second embodiment>

The present invention is a technology for operating methods of a base station and a terminal to achieve Energy Efficiency KPI [1] discussed in 3GPP RAN 5G SI. The standard defines energy-efficient operation with the main goal [2][3] to improve the power efficiency [bit/J] of terminals and base station networks by more than 1000 times within the next 10 years. To this end, in order to solve the possibility of additional power consumption due to the beamforming transmission method, which is essential during mmW operation in the high frequency band, a discussion is starting on a control to reduce the active operation time of the terminal.

The technology proposed in the present invention relates to the RRC connection control and maintenance method based on three RRC states, Connected_Active (RRC CONNECTED), Connected_Inactive (RRC INACTIVE), and Idle (RRC IDLE), which are scheduled to be applied in a mobile communication system (5G or NR). it is about technology The terms for the RRC state described below, RRC state, Connected_Active, means RRC CONNECTED. Connected_Inactive means RRC INACTIVE state, Idle means RRC IDLE state, and it is described based on this.

In particular, the function of improving the spectral efficiency and the channel access method for a method of determining the RRC state (Inactive and/or Active) for data transmission and for efficiently performing transmission in the RRC Inactive state when transmitting traffic of the UE How to apply.

The design of the RRC state for the wireless communication terminal to transmit and receive data was designed too conservatively with the design philosophy of the previous generation focusing on voice calls. For example, even if there is no traffic arrival for a certain period of time after traffic is received, the standby time such as RRC connected (Connected DRX) is maintained, and power consumption due to this is serious. In addition, in the case of smartphone users, keep alive messages, etc., which are not related to user QoS, are frequently generated as data.

Therefore, the main content of this patent is to improve the RRC state (Inactive and/or Active) determination method for data transmission and the improvement of the spectral efficiency and the channel access method for efficiently transmitting the traffic transmission of the UE in the RRC Inactive state. 20 is a diagram schematically showing the structure of a 5G (or NR) communication system according to a second embodiment of the present invention.

Referring to FIG. 20 , a 5G (or NR) communication system may include a gNB, a Mobility Management Entity (MME), a Serving Gateway (S-GW), and the like.

The gNB is, for example, a 5G (or NR) communication system base station, which is connected to the UE through a radio channel and can perform a more complex role than a conventional (UMTS) NodeB and an LTE eNodeB base station.

In the mobile communication system, when all user traffic including real-time services such as VoIP (Voice over IP) service through the Internet protocol are serviced through a shared channel, the gNB determines the buffer status of UEs, the available transmission power status, It is possible to schedule by collecting status information such as channel status. One gNB typically controls multiple cells.

The S-GW is a device that provides a data bearer, and creates or removes a data bearer under the control of the MME. The MME is a device in charge of various control functions as well as a mobility management function for the terminal, and is connected to a plurality of base stations.

21 is a diagram illustrating an operation example of three RRC states, Connected_Active (RRC_CONNECTED), Connected_Inactive, (RRC_INACTIVE), and Idle (RRC_IDLE) applied in the 5G or NR communication system according to the second embodiment of the present invention.

As shown in FIG. 21, 3GPP NR operates three RRC states by adding an inactive state to the existing two RRC states, and the UE has decided to operate with one RRC state at a time.

22 is a diagram illustrating examples of states of a terminal, a base station, and an MME in an inactive state in a 5G or NR communication system according to a second embodiment of the present invention.

In the new RRC state, Inactive, the air interface of the terminal and the base station is in a non-connected state, but the core network of the base station and the MME maintains the connected state, and even if the terminal releases the RRC Connected_Active (RRC_CONNECTED) state with the base station (Release), the base station and the MME are ECM In the connected state, it is assumed that the terminal context is stored by the base station and the MME.

23 is a diagram illustrating an example of state transition between RRC states (idle, Connected_Active (RRC_CONNECTED), Connected_Inactive (RRC_INACTIVE)) according to the second embodiment of the present invention.

The operation of the three RRC states transition is 1-1) in preparation for the operation in which the two RRC states are Idle ⇔ Connected_Active (RRC_CONNECTED) transition in the existing LTE 1-1) In 5G NR, the RRC state transitions as follows. ) The movement between the three states proceeds as follows, and according to the occurrence of the corresponding event under Idle(RRC_IDLE) ⇔ Connected_Inactive (RRC_INACTIVE)⇔ Connected_Active (RRC_CONNECTED), the following operation examples are possible.

① Initial connection: Idle ->Connected_Active(RRC_CONNECTED),

② Traffic timer expires: Connected_Active(RRC_CONNECTED) ->Connected_Inactive(RRC_INACTIVE),

③ When traffic arrives: Connected_Inactive(RRC_INACTIVE) ->Connected_Active(RRC_CONNECTED),

④ UE power off: no coverage: It can operate as Connected_Inactive (RRC_INACTIVE) or Connected_Active (RRC_CONNECTED)->Idle.

As an example of three RRC state transition operations, a state transition between RRC_Connected and RRC_Inactive, a state transition between RRC_Connected and RRC_Idle, and a state transition between RRC_Inactive and RRC_Idle are all supported.

When the state transition between RRC_Connected and RRC_Inactive, the state transition between RRC_Connected and RRC_Idle, and the state transition between RRC_Inactive and RRC_Idle are all supported, the event-based operation for the RRC state transition as an example is as follows.

① During initial connection, the terminal transitions from RRC_Idle state to RRC_Connected state;

② Transition from RRC_Connected to RRC_Inactive when an event that the standard timer (UE_inactivity_timer_inactive) expires based on the last arrived traffic occurs;

③ When new traffic arrives, if the state of the terminal at that point is RRC_Inactive, the operation transitions from the RRC_Inactive state to the RRC_Connected state;

④ When the terminal is powered off or not included in the base station cell coverage of the corresponding service, transition from RRC_Connected state to RRC_Idle if the point in time state of the terminal is RRC_Connected, or transition from RRC_Inactive state to RRC_Idle if the state is RRC_Inactive.

As an operation method in which the RRC state is transitioned, option 2) In an operation that transitions to Idle ⇔ Connected_Active, Connected_Inactive ⇔ Connected_Active and there is no Idle ⇔ Connected_Inactive transition, the following operation embodiments are possible according to the occurrence of the corresponding event.

① Initial connection: Idle ->Connected_Active ,

② Traffic timer expires: Connected_Active -> Connected_Inactive

③ Traffic Arrival: Connected_Inactive ->Connected_Active,

④ UE power off: no coverage: Connected_Active -> Idle, Connected_Inactive -> Connected_Active -> Idle.

In other words, as an example of a transition operation of three RRC states, a state transition between RRC_Connected and RRC_Inactive and a state transition between RRC_Connected and RRC_Idle are supported, but a direct (direct) state transition between RRC_Inactive and RRC_Idle is not supported. It is a diagram illustrating a supported case.

① During initial connection, the terminal transitions from RRC_Idle state to RRC_Connected state;

② Transition from RRC_Connected to RRC_Inactive when an event that the standard timer (UE_inactivity_timer_inactive) expires based on the last arrived traffic occurs;

③ When new traffic arrives, if the state of the terminal at that point is RRC_Inactive, the operation transitions from the RRC_Inactive state to the RRC_Connected state;

④ If the terminal is powered off or not included in the base station cell coverage of the corresponding service, it transitions from the RRC_Connected state to RRC_Idle if the time point state of the terminal is RRC_Connected, or transitions from the RRC_Inactive state to the RRC_Connected state and then transitions back to RRC_Idle if the RRC_Inactive state. includes actions to

As an operation method in which the RRC state is transitioned, as option 3), only two states, Connected_Inactive ⇔ Connected_Active, are transitioned, and the following operation embodiment is possible according to the occurrence of the corresponding event.

(1) Initial connection: Connected_Inactive ->Connected_Active

(2) Traffic timer expires: Connected_Active ->Connected_Inactive

(3) Traffic Arrival: Connected_Inactive ->Connected_Active

(4) UE power off: no coverage: Connected_Active -> Connected_Inactive

As an example of the three RRC state transition operations, only the state transition between RRC_Connected and RRC_Inactive is supported. Except for certain exceptions, the transition to RRC_Idle is not supported, so the state transition between RRC RRC_Connected and RRC_Idle and the state transition between RRC_Inactive and RRC_Idle are limitedly supported. It is a diagram illustrating the case.

① During initial connection, the terminal transitions from RRC_Inactive state to RRC_Connected state. At this time, the stored UE context is not terminal-specific information, but a common setting used in the network supporting the corresponding service.

② Transition from RRC_Connected to RRC_Inactive when an event that the standard timer (UE_inactivity_timer_inactive) expires based on the last arrived traffic occurs;

③ When new traffic arrives, transition from RRC_Inactive state to RRC_Connected state, or transition from RRC_Idle state to RRC_Connected state,

④ If the terminal is powered off or is not included in the base station cell coverage of the corresponding service, it transitions from the RRC_Connected state to RRC_Inactive if the state of the terminal is RRC_Connected, or the RRC_Inactive state if the terminal is in the RRC_Inactive state (to store UE-specific UE context information) It includes the operation of transitioning from RRC_Inactive (to save network common UE context) state.

In the operation illustrating an example of state transition between the RRC states (idle, Connected_Active, Connected_Inactive) shown in FIG. 23 , there are three examples of modes in which the terminal transmits and receives data as follows.

-Mode 1) Data transmission in INACTIVE state (FIGS. 24 to 26, 30)

- Mode 2) Data transmission after transition from INACTIVE to ACTIVE state (FIG. 28)

-Mode 3) includes a method of starting data transmission in the INACTIVE state and additionally transmitting data after transition to the ACTIVE state (FIGS. 27, 29, 31, and 32).

The following example includes configuring/transmitting the RRC state type and event trigger method to be applied to each terminal determined by the base station to each terminal.

1) Terminal link initial setup (when link setup or transition to RRC_Connected (applied RRC state configuration and transition event rule of the corresponding terminal) configure/set with RRC configuration message;

2) How to configure/set with RRC reconfiguration message when detecting a change in RRC state application criteria at any time (applied RRC state configuration and transition event rule of the corresponding terminal);

3) In case of RRC Connection release, it includes a method of configuring/setting (configuration of RRC state applied to the terminal and transition event rule) with RRC release message.

24 to 26 and 30 schematically show a data transmission operation in an INACTIVE state corresponding to mode 1) in an NR system according to embodiments of the present invention.

The operation of transmitting data directly in the INACTIVE state does not require delay and control signaling for the UE to transition from the inactive state to the RRC active state, and has the advantage of eliminating the waiting time in the active state, but due to the grant-free transmission, There are disadvantages in that channel access efficiency is reduced and transmission spectral efficiency is reduced due to the subtitle of information such as CQI and BSR.

The existing data transmission in the idle state has disadvantages in the reduction of channel access efficiency due to grant-free transmission and the reduction in transmission spectral efficiency due to the subtitle of information such as CQI and BSR. In the design method, methods for improving spectral efficiency and improving channel access for efficiently transmitting traffic of the UE in the RRC Inactive state are further proposed in FIGS. 31 to 34 .

24 to 26 and 30, in the data transmission operation in the INACTIVE state corresponding to “mode 1)” in the NR system according to the second embodiment of the present invention, in the terminal RACH procedure in the Inactive state, RACH signaling, which is a control message It shows how to piggyback data and transmit it. 24 is a diagram schematically illustrating a data transmission operation in an INACTIVE state in an NR system according to a second embodiment of the present invention, and shows an example of transmitting data by adding data to a Message3 RRC connection (resume) request in the RACH procedure.

25 is a diagram schematically illustrating a data transmission operation in an INACTIVE state in an NR system according to a second embodiment of the present invention. In the RACH procedure, data is added to a Message3 RRC connection (resume) request and BSR information is added and transmitted. shows an example to

In this case, the information transmitted together in MSG3 is as follows.

- AS ID as UE identity (or UE context identity)

- Establishment (or resume) cause information

- Includes UE's security information (e.g. authentication token)

In addition, it exemplifies a method of transmitting the RRC Connection request by including the following information to MSG3.

- NAS message

- 5G CN node selection,

- UE capability of supporting high frequency,

- Information including the access category indicating a type of services, exemplifies how to transmit some or all of the information that can be transmitted to MSG5 to MSG3.

25, although the RRC connection (resume) request transmitted as RACH Message3 is transmitted to the SRB and uplink data is transmitted to the DRB, these two can be transmitted in one transport block through MAC multiplexing in one transmission. . In this case, if data transmission to MSG3 is not completed, terminal buffer status information (BSR) may be transmitted to MSG3 to transmit information on the need for subsequent transmission to the base station.

26 shows an example of adding and transmitting data to RRC connection (resume) complete transmitted as Message5 in the RACH procedure.

27 shows that when data transmission to MSG3 is not completed, terminal buffer status information (BSR) is transmitted to MSG3 to transmit information on the need for subsequent transmission to the base station, and the base station sends an RRC resume response including ACK information for MSG3. It shows a method of transmitting the remaining data in the active state after transmitting to the terminal and transitioning to the active state.

30 , after data transmission in MSG3, the remaining data may be additionally transmitted in an inactive state through MSG5. In addition, when it is determined that data transmission is not completed even with MSG5 transmission and transition to the active state is more advantageous (related determination criteria will be additionally described in FIG. 35), RRC resume response including ACK information for MSG5 as shown in FIG. 32 This is a method in which the base station transmits to the terminal and transmits the remaining data in the active state after transition to the active state.

In FIG. 24, the method of transmitting data by adding data to RACH Message3 has the effect of reducing network control burden and delay because the number of control signaling is small compared to the method of transmitting and adding data to RACH Message5 in FIG. 26. However, RA before RACH Message3 There is a possibility that the transmission SE may decrease because the information available for the preamble and RA response is limited.

The UE may indicate whether to transmit UL data in the corresponding RACH Message 3 while transmitting the RACH preamble that is RACH Message 1. In this case, RACH Message1 includes an operation of indicating whether to transmit UL data by separating a pool of PRACH resources.

For example, the RACH Message1 preamble is separated according to whether UL data is transmitted, the base station configures the terminal, and the terminal operates based on this;

Alternatively, the base station configures the terminal by separating the RACH Message1 transmission time (eg, TTI or time slot from the reference time) according to whether UL data is transmitted, and the terminal operates based on this;

Or by separating the RACH Message1 transmission frequency (eg, ARFCN-based frequency band) according to whether UL data is transmitted, the base station configures the terminal, and the terminal operates based on this;

Alternatively, depending on whether UL data is transmitted or not, the carrier domain of the PRACH frequency for transmitting RACH Message1 (eg, a sub-carrier or bandwidth part (BWP)) is separated from the reference frequency band, and the base station configures it in the terminal and How the terminal operates based on

It includes a method of operating based on each and a plurality of combinations.

In this case, as a method for the base station to transmit reference information for partitioning the PRACH resource to the terminal according to whether to transmit the corresponding UL data,

When releasing the previous RRC connection (a method of configuring reference information for partitioning the corresponding PRACH resource in the RRC connection suspend or RRC connection release message, and

In the system information (SI) information transmitted by each target base station, each and combination of the broadcasting (broadcasting method) is included.

The UL carrier frequency, UL bandwidth, and IE RadioResourceConfigCommon related to uplink information are broadcast in SIB2 as a method in which the base station transmits reference information for partitioning PRACH resources to the terminal according to whether the corresponding UL data is transmitted. IE RadioResourceConfigCommon includes information for configuring PUSCH including RACH configuration, PUCCH, and sounding RS (SRS) transmitted in uplink. At this time, in order to transmit reference information for partitioning the PRACH resource according to whether UL data is transmitted or not, the PRACH parameter is divided into two sets and transmitted.

In more detail, for example, in the case of partitioning the PRACH preamble according to whether UL data is transmitted (Early Data Transmission: EDT), it can be configured as shown in the table below.

In addition, the PRACH pool partitioning including the timing, frequency band, and carrier domain for PRACH transmission as exemplified above also includes an operation of dividing and setting the PRACH configuration parameters of the SI into separate sets (two parameter groups).

As another embodiment, system information transmission in the case of supporting Supplemental Uplink Frequency (SUL) will be described. The SUL technology is a technology that additionally supports UL in the lower frequency band to extend the UL coverage of the higher frequency band of NR. In the case of downlink, since the spatial power capacity of the base station is high, beam gain can be obtained with a larger number of antennas, and downlink coverage can be extended with higher transmission power. On the other hand, in the case of uplink, it is difficult to secure wide coverage in a higher frequency band due to the limitations of spatial and physical power of the terminal, so the operation is supplemented with the lower frequency of SUL.

When the UE performs initial access, a criterion for determining whether the RACH uses the SUL band (lower frequency band) or the NR UL (uplink uplink) is required.

The information includes a method of configuring reference information for partitioning a corresponding PRACH resource in an RRC connection suspend or RRC connection release message when the base station releases a previous RRC connection, and

In the system information (SI) information transmitted by each target base station, each and combination of the broadcasting (broadcasting method) is included.

In particular, in the case of NR, beamforming is performed due to high pathloss in the high frequency band. Since system information is broadcast information that must be transmitted in the entire beam direction, when it is transmitted to the PBCH, the payload size is insufficient. To solve this, extra SI information not loaded on the PBCH is broadcast on the PDCCH or PDSCH, which is called RMSI (Remaining System Information).

That is, the uplink configuration information of the RACH for the UE to perform initial access includes broadcasting to the base station (cell) by loading the relevant parameters in the RMSI.

In particular, when the UE performs RACH, the base station sets a threshold that becomes a criterion for determining whether to use the SUL band (lower frequency band) or perform the RACH in the NR UL (uplink uplink) system. Information (eg, RMSI) includes an operation of broadcasting within the base station cell.

The threshold includes a threshold (threshold value) of the received signal level,

As another threshold, an operation may be performed based on the degree of congestion of the corresponding uplink path (SUL or NR UL). For example, it includes an operation method based on the number of occurrences of timing backoff due to occurrence of contention in the RACH procedure or frequency of occurrence of timing backoff.

The above contention occurrence standard is applicable in the following situations. When transmitting the RACH preamble, which is RACH message 1, it is transmitted with initial transmission power until it successfully receives a RAR (RACH response) from the base station, and after a predetermined time (pre-configured RAR waiting time), the transmission power is increased again based on powerRampingParameters. The RACH preamble, which is RACH message 1, is retransmitted.

In addition, the criterion for selecting the uplink transmission path as SUL transmission or NR UL based on the degree of occurrence of contention described above is applicable in the following situations.

When a channel collision occurs due to congestion in the uplink transmission path (e.g. SUL), where the RACH preamble is determined to be transmitted as the RACH message1 when RAR (RACH response) is successfully received from the base station. RACH message 4 (RRC connection response) is set by changing from the previous uplink transmission path (eg SUL) to another uplink transmission path (eg NR UL), and applying this to RACH message 5 (RRC connection complete) including how to transmit it.

As an example of a threshold serving as a corresponding criterion, if each and combination of reception RSRP, RSRQ, RSSI, etc. of the terminal is greater than or equal to the threshold, RACH is performed with NR UL,

If it is less than the threshold, RACH is performed in the SUL frequency band.

In addition, since the NR UL and the SUL have different frequency bands and a distance between the transmitting and receiving terminals that operate, a separate PRACH parameter for supporting this is divided into two sets and transmitted.

In more detail, for example, when performing RACH, in the case of setting the PRACH parameter according to whether to use the SUL band (lower frequency band) or perform the RACH with NR UL (uplink uplink), it can be set as shown in the table below. there is.

Unlike the method of setting each independent two RACH-ConfigCommon parameter sets for SUL transmission and NR UL transmission as described previously,

Another embodiment includes a method of designing one common RACH-ConfigCommon parameter set and extending the parameter to a larger value capable of compensating for the pathloss difference in the SUL frequency band and the NR frequency band.

For example, a method of setting and applying two independent powerRampingParameters parameter sets for SUL transmission and NR UL transmission in the operation of applying as a method of setting powerRampingParameters,

In contrast to this, a common powerRampingParameters parameter set for SUL transmission and NR UL transmission is set, and the maximum power ramping up value is extended and set to a larger value that can compensate for the pathloss difference in the SUL frequency band and the NR frequency band. method includes.

When the UE transmits the RACH preamble, which is RACH message 1, it transmits with the initial transmission power until it successfully receives a RAR (RACH response) from the base station, and after a predetermined time (pre-configured RAR waiting time), the transmission power is again based on powerRampingParameters. The RACH preamble, which is RACH message 1, is retransmitted by increasing it.

If RAR (RACH response) is successfully received from the base station, RRC Connection Request, which is RACH MSG3, is transmitted.

In this RACH preamble retransmission process, as a method of determining whether to transmit SUL or NR UL,

1) When the uplink transmission path according to the threshold value set by the RMSI is determined during the first RACH preamble transmission, the uplink path (SUL or NR UL) is fixed until RAR (RACH response) is successfully received from the base station. ) to transfer;

1-1) If the uplink path determined at the time of the first RACH preamble transmission is SUL, the RACH preamble retransmission attempt, which is transmitted by power ramping up, is continuously transmitted to the SUL until RAR (RACH response) is successfully received from the base station. method

1-2) If the uplink path determined at the time of initial RACH preamble transmission is UL NR, the RACH preamble retransmission attempt, which is transmitted by power ramping up, is continued as UL NR until RAR (RACH response) is successfully received from the base station. How to send

2) an operation of newly determining and applying an uplink transmission path (SUL or NR UL) according to the threshold value set by the RMSI at the time of the first RACH preamble transmission and at each subsequent attempt to retransmit the RACH preamble transmitted after (power ramping up);

2-1) If the uplink path determined at the time of the first RACH preamble transmission is NR UL (power ramping up), the RMSI is set until RAR (RACH response) is successfully received from the base station every time the RACH preamble retransmission is attempted. A method of newly determining and applying an uplink transmission path (SUL or NR UL) according to a threshold value for transmission

2-2) If the uplink path determined at the time of the first RACH preamble transmission is SUL (power ramping up), the RMSI set until RAR (RACH response) is successfully received from the base station every time the RACH preamble retransmission is attempted. A method of newly determining and applying an uplink transmission path (SUL or NR UL) according to a threshold value for transmission

In another embodiment, as a method of determining transmission to SUL or NR UL in the RACH procedure for initial access,

1) RRC connection request transmitted as RACH message 3 using the same uplink transmission path (SUL or NR UL) of the RACH preamble transmitted as RACH message 1 when RAR (RACH response) is successfully received from the base station, or a method of transmitting an RRC connection resume request or an RRC resume request;

2) RACH message 3 and RACH message 5 (RRC connection complete) using the same uplink transmission path (SUL or NR UL) of the RACH preamble transmitted as RACH message1 when RAR (RACH response) is successfully received from the base station ) to transmit;

3) RACH message 3 is transmitted using the same uplink transmission path (SUL or NR UL) of the RACH preamble transmitted as RACH message1 when RAR (RACH response) is successfully received from the base station, and then RACH message 4 ( a method of transmitting RACH message 5 (RRC connection complete) through an uplink transmission path (SUL or NR UL) configured in RRC configuration based on RRC connection response);

4) When a channel collision occurs due to congestion in the uplink transmission path (e.g., SUL), which is determined to transmit the RACH preamble transmitted as RACH message1 when RAR (RACH response) is successfully received from the base station As an action, RACH message 4 (RRC connection response) is set by changing from the previous uplink transmission path (eg SUL) to another uplink transmission path (eg NR UL) and applying this to RACH message 5 (RRC connection complete) ) to transmit;

In this case, since SUL supports only uplink and does not have downlink and downlink reference signaling, the pathloss of SUL must be corrected based on reference signaling transmitted in NR downlink. For this, a method in which the base station broadcasts the pathloss difference in the SUL frequency band and the NR frequency band to the terminal in RMSI is included.

Reference signaling as a reference here includes a synch signal (SS), a Channel State Information Reference Signal (CSI-RS), a demodulation RS (DMRS), and a tracking RS (TRS).

A method of broadcasting different values according to a reference signaling type, which is a reference in a method in which the base station broadcasts the pathloss difference in the SUL frequency band and the NR frequency band to the terminal in RMSI, and

It includes a method of transmitting a limited number of pathloss difference values (in the SUL frequency band and the NR frequency band) for the applied single RS or some RSs.

The UE includes the operation of adjusting the transmission power of the RACH preamble based on the difference value of the pathloss (in the SUL frequency band and the NR frequency band) of the number of transmissions.

Alternatively, when calculating PH (power headroom) for uplink data transmission in RRC_CONNECTED state, the PH value of SUL is calculated based on the correction value in the pathloss corresponding to RS in NR DL, and PHR (Power Headroom Report) is transmitted. includes

43 to 45 additionally propose a method for improving spectral efficiency and improving channel access when a UE transmits traffic in an inactive state, which is a corresponding content.

In both RACH Message3 of FIG. 24 and RACH Message5 of FIG. 26, after data transmission, ACK for the data and information on whether RRC state transition is transmitted as RRC response. At this time, if the RRC response is suspend, it maintains the Inactive state, and if it is resume, it transitions to the Active state and then data transmission proceeds.

28 schematically illustrates a data transmission operation after a state transition from INACTIVE to ACTIVE corresponding to “mode 2)” in the NR system according to the second embodiment of the present invention.

In the operation of starting data transmission after the transition to the active state, there is a delay in transitioning the terminal from the inactive state to the RRC active (RRC CONNECTED) state and the burden of control signaling exists, and due to the waiting time in the active (RRC CONNECTED) state Terminal power consumption occurs.

However, the operation of starting data transmission after the transition to the active state (RRC CONNECTED state) increases the channel access efficiency due to the granted transmission in the active (RRC CONNECTED) state, and transmits spectral efficiency by utilizing information such as CQI and BSR can improve

In FIG. 28, the data transmission operation after the state transition from INACTIVE (RRC INACTIVE) to ACTIVE (RRC CONNECTED) corresponding to “Mode 2)” in FIG. 28 is similar to the existing LTE operation in that data is transmitted after the transition to the active state, but is transmitted in RACH The control signal used is an RRC connection (resume) request, which has the effect of reducing the signaling delay and number between the core (gNB-MME) networks by utilizing the UE context stored in the RRC setup process. In addition, after data transmission, the UE can quickly transition to the low power mode, Inactive state, through the 6. RRC connection suspend message.

27, 29, 31, and 32 schematically show the data transmission operation after the transition to the ACTIVE state by starting data transmission in the INACTIVE state corresponding to “mode 3)” in the NR system according to an embodiment of the present invention. do.

By transmitting data in a hybrid form of “mode 1)” and “mode 2)”, it reduces the initial transmission delay of data by removing the delay of the UE transitioning from the inactive state to the RRC active state and the burden of control signaling. Channel access efficiency increase due to granted transmission of data transmission. By using information such as CQI and BSR, transmission spectral efficiency can be improved at the same time.

At this time, after data transmission in both RACH Message3 of FIG. 29 and RACH Message5 of FIG. 31, ACK for the data and information on whether RRC state transition is transmitted as an RRC response. At this time, if the RRC response is suspend, it maintains the Inactive state, and if it is resume, it transitions to the Active state and then data transmission proceeds.

When transmitting the RRC connection complement or RRC connection resume complete or RRC resume complete signal of MSG5, the following information is loaded and transmitted.

- NAS PDUs

- 5CN node selection information (e.g. selected PLMN identity or NSSAI

- selectedPLMN-Identity,

- registeredMME,

- gummei-Type,

- s-TMSI,

- attachWithoutPDN-Connectivity,

- up-CIoT-EPS-Optimisation,

- cp-CIoT-EPS-Optimisation,

- dcn-ID.

In order for the information of the embodiment to be transmitted to MSG5, if the previously stored UE context is successfully retrieved from the anchor base station and new security key information (K_gNB_target) can be generated from the target base station, the information is transmitted to SRB1 and It includes an operation in which the terminal transmits the corresponding information to the base station safely for security by applying the new security key.

Some or all of the information also includes a method of being loaded in an RRC connection request or RRC connection resume request or RRC resume request transmitted to MSG3 and transmitted to (SRB0 or DRB).

In other words, the following information may be loaded and transmitted in the RRC connection request message transmitted to MSG3.

- NAS message

- 5G CN node selection,

- UE capability of supporting high frequency,

- Information including the access category indicating a type of services, exemplifies how to transmit some or all of the information that can be transmitted to MSG5 to MSG3.

Another embodiment relates to the procedure and operation when the UE transitions from RRC_CONNECTED to RRC_INACTIVE when Dual Connectivity (DC) (or Carrier Aggregation (CA)) is applied.

The first method is a method of suspending by storing all of the radio bearer settings of the corresponding DC or CA in the UE context stored by the terminal and anchor base station in the inactive state, and then resumes when RRC_Connected.

The second method leaves only the master node (MN) setting (MCG bearer) among the radio bearer settings to which the corresponding DC is applied and deletes the secondary node (SN) setting (SCG bearer setting), and then the terminal and anchor base station in Inactive state are stored This is a method to suspend by saving some in the UE context and resume it when RRC_Connected afterwards.

Or, from among the radio bearer settings to which the corresponding CA is applied, only the PCell setting (Radio bearer) is left and the Scell setting (radio bearer setting) is deleted, and then partially stored in the UE context stored by the UE and anchor base station in the inactive state and suspend, and then This is a method to resume when RRC_Connected.

If DC is described as an example, after deleting the setting (SCG bearer setting) of the second node (SN) leaving only the setting (MCG bearer) of the master node (MN) among the radio bearer settings to which the corresponding DC is applied, the terminal and anchor base station in Inactive state As an example of a method of suspending by saving some in the saving UE context, and then resuming it when RRC_Connected

1) How to release all radio bearer settings (SCG bearer settings) of the second node (SN)

2) How to change all settings (SCG bearer settings) of Second node (SN) to MCG bearer

3) It includes a method of changing some of the settings (SCG bearer settings) of the Second node (SN) to MCG bearers and releasing some radio bearers.

In the case of CA, extension can be applied by substituting Scell for SN operation.

That is, after deleting the Scell setting (radio bearer setting) while leaving only the PCell setting (Radio bearer) among the radio bearer settings to which the corresponding CA is applied, it is partially stored and suspended in the UE context stored by the terminal and anchor base station in the inactive state. Afterwards, as an embodiment of a method to resume when RRC_Connected,

1) How to release all radio bearers (radio bearer settings) set in Scells

2) How to change the radio bearer to PCell all (radio bearer setting) set in Scells

3) It includes a method of changing some of the radio bearers set in Scells (radio bearer setting) to PCell and releasing some radio bearers.

At this time, a method of changing the radio bearer to an MN (MCG bearer or PCell bearer), storing it in the UE context, and then enabling transmission to the radio bearer immediately through suspend and resume procedures;

Or, by releasing a radio bearer to reduce the capacity of the terminal and anchor base station to store the corresponding radio bearer information in the UE context, or to update the RAN-based paging area when the terminal moves. Control for managing and controlling the radio bearer The process of choosing a method to reduce the burden includes:

1) In the case of DC, if the radio bearer configured in the corresponding SN (SCG or Scell in the case of CA) overlaps with the PDU session in which the radio bearer of the PCell is configured (MCG bearer or CA in the case of CA), this is referred to as MN (MCG bearer in the case of DC). Alternatively, in the case of CA, it is changed to the radio bearer of the PCell, and if there is no overlap, the cost of maintaining the PDU session occurs, so the radio bearer is released.

2) In the case of DC, if the QoS level of a flow or service supported by the radio bearer set in the corresponding SN (SCG or Scell in the case of CA) is higher than a specific threshold, it is set to MN (MCG bearer in the case of DC or PCell in the case of CA) Change to radio bearer If the QoS level is lower than the threshold, release the radio bearer.

3) In the case of DC, if the latency limit of the flow or service supported by the radio bearer set in the corresponding SN (SCG or Scell in the case of CA) is shorter than a specific threshold, in order to reduce the delay occurring during resumption, in the case of DC In case of MN (MCG bearer or CA, it is changed to PCell radio bearer). When the required latency limit is longer than a specific threshold and delay is irrelevant, it includes the operation of releasing the corresponding radio bearer.

For this operation, the core network determines based on the above-described PDU session information, bearer or supported QoS of the corresponding flow, and request delay, etc. and includes an operation of setting the base station. This includes an operation of determining whether to release the corresponding radio bearer or perform a transfer (bearer type change) and an operation of transitioning the RRC state to Inactive by applying the same.

As a method of deciding whether to release the corresponding radio bearer or perform a transfer (bearer type change)

1) A method in which the core network sets the base station based on additional information including the above-described PDU Session information for the corresponding decision, the bearer or support QoS of the corresponding flow, and the request delay;

2) How the core network sets measures/standards (PDU Session information described above, bearer or supported QoS and request delay of the corresponding flow) and rules for the determination in the base station;

3) The base station determines whether to release the radio bearer or perform the transfer (bearer type change) with base station possession information and terminal feedback information within the master cell of the corresponding base station (including MN for DC and PCell for CA) include

4) Whether the base station releases the radio bearer or performs transfer (bearer type change) with base station possession information and terminal feedback information within the base station (including both MN and SN for DC, and Pcell and Scell for CA) including how to decide.

In this process, in the case of DC (LTE-NR DC, NR-NR DC, 5G applicable NSA or DC structure on SA), the QoS required for the flow or service supported by the radio bearer configured in the corresponding SN (SCG) However, it includes the operation of feeding back each or combination of information including latency requirements or service categories to the base station.

In the above-described operation, in the case of CA, the UE includes the operation of feeding back each or combination of information including the QoS or latency requirement or service category of the flow or service supported by the radio bearer configured in the corresponding Scell to the base station.

29 shows a case in which data is additionally transmitted by transitioning to the RRC active state after data transmission in the RACH Message3-based inactive state, and FIG. Indicates the case of transmission. After the terminal transmits data in the active state, the base station can quickly transition the terminal to the inactive state, which is a low power mode, through the 6. RRC connection suspend message. resume) This is a diagram explaining the operation of adding and transmitting data to complete and maintaining the Inactive state by transmitting (ACK and suspend) to the RRC response when data transmission is complete.

31 is a diagram schematically illustrating a data transmission operation after starting data transmission in an INACTIVE state and transitioning to an ACTIVE state.

32 shows that data transmission is started through MSG3 in INACTIVE state, data is added to Message5 RRC connection (resume) complete and transmitted. It is a diagram explaining the operation of transitioning back to Inactive through RRC connection suspend message transmission when data transmission is completed again.

33 to 35 are diagrams illustrating examples of signaling operations between a terminal and a base station for determining and controlling an RRC state (Inactive and/or Active) for data transmission in an NR system according to a second embodiment of the present invention.

33 illustrates a method in which the terminal triggers an event based on the base station configuration in order to determine the RRC state-related operation mode to transmit data, and the base station determines the event by feedback.

Step 1) The terminal may receive configuration information regarding a method of determining an RRC state (Inactive and/or Active) for data transmission from the base station. When the terminal performs initial access to the corresponding communication system or powers on (Turn on) or when the terminal receives System Information (SI) from the corresponding base station, the base station determines the type of RRC state and the switching method to be applied to each terminal may transmit configuration information related to .

Step 2) The UE may trigger an event based on configuration information related to determining the type of RRC state and switching method transmitted from the base station and feedback it to the base station. Then, based on the feedback, the base station performs any one of continuous data transmission operations in the data transmission mode (1) data transmission in INACTIVE state, (2) transition decision to ACTIVE state, (3) data transmission in INACTIVE start and active You can choose. Among the three modes, since mode (1) and mode (3) have the same operation before the RRC response, the base station can distinguish and inform only modes (1), (3) and mode (2). Thereafter, mode (1) and mode (3) can be divided based on RRC response 1) ACK & suspend, and 2) Resume.

Step 3) After the base station determines (or switches) the data transmission mode, it can transmit it to the terminal through system information or dedicated signaling (paging, etc.).

Step 4) When data transmission is required in the active state after data transmission in the initial inactive state, the base station transmits the information within the RRC response 1) ACK & suspend, 2) Resume, and based on this, the terminal transmits the data later and sets the RRC state to Inactive It is possible to perform an operation to keep it as or to transition to active.

FIG. 34 shows a method in which the terminal determines event triggering and data transmission mode conversion based on the base station configuration, and transmits it to the base station (eg, embedded in a RACH UL message) in the data transmission process to inform the method.

While the base station selects the data transmission mode based on the feedback of the terminal in FIG. 33 , in FIG. 34 , the terminal may directly select the data transmission mode based on the base station configuration and inform the base station of the selection result.

Step 1) The terminal may receive a configuration related to the method of determining the RRC state (Inactive and/or Active) for data transmission from the base station. When the terminal performs initial access to the corresponding communication system or powers on (Turn on) or when the terminal receives System Information (SI) from the corresponding base station, the base station determines the type of RRC state and the switching method to be applied to each terminal may transmit configuration information related to .

Step 2) The UE may trigger an event based on configuration information related to determining the RRC state type and switching method transmitted from the base station, and may determine the data transmission mode based on this. The UE can select a data transmission mode from among three transmission modes: (1) data transmission in INACTIVE state, (2) transition decision to ACTIVE state, and (3) data transmission start to INACTIVE and continuous data transmission operation to active. Among the three modes, mode (1) and mode (3) have the same operation before the RRC response, but the terminal can distinguish only modes (1), (3) and mode (2) and inform the base station. Thereafter, mode (1) and mode (3) can be distinguished based on RRC response 1) ACK & suspend, and 2) Resume.

Step 3) In order to transmit the selected data transmission mode to the base station, the terminal may transmit a data transmission mode update to the base station (for example, embedded in the RACH UL message) in the data transmission process.

At this time, among the three data transmission modes, mode (1) and mode (3) have the same operation before the RRC response, but the terminal distinguishes all modes (1) (2) (3) and informs the base station for an appropriate RRC response 1 ) ACK & suspend, 2) Resume can be transmitted.

Step 4) When data transmission is required in the active state after data transmission in the initial inactive state, the base station transmits the information within the RRC response 1) ACK & suspend, 2) Resume, and based on this, the terminal transmits the data later and sets the RRC state to Inactive It maintains or transitions to active.

35 illustrates a method for determining an RRC state related operation mode in which a base station transmits data without event trigger and feedback of a terminal based on a base station configuration. Compared with FIG. 33, the method shown in FIG. 35 is similar in that the base station determines the data transmission mode, but there is a difference between the two methods in that there is no event trigger and feedback of the terminal.

Step 1) The terminal may receive configuration information regarding a method of determining an RRC state (Inactive and/or Active) for data transmission from the base station. When the terminal performs initial access to the corresponding communication system or powers on (Turn on) or when the terminal receives System Information (SI) from the corresponding base station, the base station determines the type of RRC state and the switching method to be applied to each terminal may transmit configuration information related to .

36 is a diagram illustrating an example of a signaling operation between UEs for determining and controlling an RRC state (Inactive and/or Active) for data transmission. In the inactive state configuration process, the base station may set the buffer size and RSRP threshold for determining the data transmission mode to the terminal.

Referring to FIG. 36, the corresponding configuration can be set by the base station to the terminal when the RRC inactive state starts setting, for example, determining the RRC state (Inactive and/or Active) for data transmission and determining the MSG3 or MSG5 transmission mode. The operation of defining the event and setting the parameters for this, the corresponding parameters include setting the buffer size of the terminal and the RSRP threshold value. Also, the base station may update the corresponding configuration through System Information.

Step 2) The base station transmits data without feedback from the terminal (1) data transmission in INACTIVE state, (2) decision to transition to ACTIVE state, (3) data transmission mode among continuous data transmission operations starting in INACTIVE and active can be selected. Among the three data transmission modes, mode (1) and mode (3) have the same operation before the RRC response, so the base station can distinguish only modes (1), (3) and mode (2) and inform the terminal. Thereafter, mode (1) and mode (3) can be distinguished based on RRC response 1) ACK & suspend, and 2) Resume.

Step 3) After the base station selects (or switches) the data transmission mode, it can transmit it to the terminal through system information or dedicated signaling (paging, etc.).

Step 4) When data transmission is required in the active state after data transmission in the initial inactive state, the base station transmits the information within the RRC response 1) ACK & suspend, 2) Resume, and based on this, the terminal transmits the data later and sets the RRC state to Inactive It is possible to perform an operation to keep it as or to transition to active.

Information for determining the RRC state-related operation mode for data transmission may be determined based on the following transmission data traffic characteristics and terminal characteristics.

1) An operation in which the base station determines the RRC state for data transmission by feedback to the base station and transmits an RRC response (RRC suspend or RRC resume)

2) Alternatively, the operation of determining the RRC state for data transmission within the terminal and dividing it into inactive_data transmission or Active_data transmission as resume_cause within the RRC connection request (resume request) message

An operation of selecting based on some or a combination of the following factors as a traffic characteristic-based decision criterion to determine the RRC state-related operation mode to transmit data,

* Data packet size is advantageous in terms of terminal power efficiency or data transmission/reception delay to transmit in the inactive state in case of small data. As an embodiment of the operation, it can be defined as 2/3 SDU size, and the detailed value can be configured and operated according to the system.

* Data Packet Interval: When frequent data traffic arrives, it may be advantageous to transmit it by transitioning to the active state. Operation based on the number of arrivals of traffic units per unit time, etc.

- In the method of determining based on the traffic pattern, the base station determines this based on the ratio of the connected_active state, the ratio of the inactive state, and the ratio of the idle state reflecting the UE inactivity timer of the base station (network)

- Based on the RRC state ratio when transmitting previous data stored in the terminal

If the base station does not know this information due to the terminal's idle mobility (the operation in which the terminal moves without handover in the idle or inactive state, and the currently located base station does not receive information/feedback from the terminal), the terminal feeds back previous information to the base station and An operation in which the base station determines the RRC state for data transmission based on

- Or, when transmitting the previous data stored in the terminal, the terminal information (traffic pattern, mobility information) is stored in the UE context, updated, and forwarded from the anchor base station to the camped base station through X2 and transmitted.

* Data packet sum in UE/gNB buffer: A method to determine the RRC state-related operation mode to transmit data to the buffer of the terminal and/or base station based on the traffic size. , it can operate including the buffer of the PHY stage.

* Data packet delay requirement is determined based on characteristics for each traffic service such as eNBB, ULRRC, mMTC, etc. defined in NR and QoS (CQI for each bearer), etc. mode selection action

* Network loading (contention probability): The operation of determining the RRC state to transmit data based on the contention probability that occurs during channel access determined by the terminal or the base station

- In one embodiment, when the number of terminals accessing the channel for data transmission is large, it includes an operation to transmit data by transitioning to the RRC connected active state.

- The probability of contention occurring during channel access can be determined by using the information identified by the base station through contention resolution.

- Alternatively, the UE measures the nearby interference level (for example) based on the RSRQ, and if an event occurs based on a threshold pre-configured by the base station, the operation is determined based on this

As a terminal characteristic for determining an RRC state-related operation mode to transmit data, an operation of selecting based on some or a combination of the following factors,

* Terminal-base station distance (Short/Long Coverage) is based on the pathloss between the terminal and the base station, for example, based on reception RSRP/RSRQ.

The operation of determining whether the terminal location is located in the cell center area or the boundary area from the base station based on the terminal-base station distance threshold or the received signal value (eg RSRP/RSRQ)

: In one embodiment, for example, during RACH operation, the corresponding information can be identified in the process of RA preamble transmission and RAR reception, so an operation of determining the RRC state related operation mode for data transmission based on this information

: This information is the standard for determining the payload length that can be transmitted in the Inactive state.

- When retaining CQI and similar information, it is advantageous to transmit data in Inactive as it is closer (higher received signal quality).

- In the absence of CQI and similar information, the closer the distance (higher received signal quality), the more advantageous the method of transmitting data in the active state.

* Terminal usage state: Latency Tolerance, if the traffic to the terminal is not directly input by the user or directly affecting QoS, the low latency factor is not important, so data in the active state to improve network-wide (SE) efficiency An example of an operation to select a method to transmit

Alternatively, if there is no direct input by the user or direct traffic that affects QoS, selecting a data transmission mode in the Active (RRC_CONNECTED) state for low-power operation of the terminal (to remove unnecessary C-DRX section) Example of

* Terminal movement speed and whether idle mobility from the recently RRC connected base station:

- Determining the RRC state related operation mode to transmit data based on whether the UE ID (Cell ID C-RNTI) can be reused in the Inactive state data transmission situation

- Determining the RRC state related operation mode to transmit data based on whether the UP security information (security key) of the terminal can be reused in the inactive state data transmission situation

- Performs an operation to determine in consideration of factors including idle mobility support overhead (Paging S1, X2).

A method of determining an RRC state transition for data transmission based on a terminal mobility support overhead (Paging S1, X2) according to a paging operation method (CN-based paging or RAN-based paging) or a tracking area/paging area size.

If the base station does not know this information due to the terminal's idle mobility (the operation in which the terminal moves without handover in the idle or inactive state and the currently located base station does not receive information/feedback from the terminal), the terminal feeds back previous information to the base station and An operation in which the base station determines the RRC state for data transmission based on

- Or, when transmitting the previous data stored in the terminal, the terminal information (traffic pattern, mobility information) is stored in the UE context, updated, and forwarded from the anchor base station to the camped base station through X2 and transmitted.

* UE battery status: A method of determining the RRC state to transmit data by feeding back the power consumption state of the terminal to the base station with reference to this

Such feedback may be performed by data transmission in the inactive state without transition or transition of the RRC state to the RRC connected active. A terminal in which the base station sets an RRC state related operation mode for transmitting data based on the characteristics including the above elements Determination by adding base station information based on event trigger and feedback, or by using only base station internal information, or by the terminal internally according to a rule set by the base station Transmission by changing the mode.

The reflection of factors including the terminal/data traffic characteristics for determining the RRC state-related operation mode to transmit the data described above can be reflected in the RRC state transition procedure as a control message transmission, or some DRBs are dedicated DRBs for inactive state data transmission. It can be set and other DRBs are set as DRBs dedicated to data transmission in the active state, and when data traffic occurs, it can be reflected in the process of mapping and transmitting the corresponding transmissions to different DRBs.

37 is a diagram illustrating an example of a signaling operation between a terminal and a base station for determining and controlling an RRC state (Inactive and/or Active) for data transmission in the NR system according to the second embodiment of the present invention. Based on the base station configuration and the event trigger of the terminal, the terminal may determine the RRC state related operation mode in which the base station transmits data without feedback to the base station.

In the case of this operation, since the base station cannot know the corresponding information before transmitting the BSR or RSRP information of MSG3, when MSG3 is allocated to the base station, the allocation size of MSG3 can be assigned as a default without the corresponding BSR or RSRP information.

In addition, the UE may transmit information related to BSR or RSRP information based on, for example, Group information of an RA sequence based on MSG1 (RA preamble). However, since the amount of information that can be transmitted is limited, the operation of transmitting information specifying the size of a small number of, for example, 2-3 MSG3s with low-precision corresponding to small data. In addition to the sequence domain of the PA preamble, the time domain and frequency domain , based on the pre-configured rule of the beam domain (spatial domain), the base station may allocate the MSG3 according to the indication of the resource (time, frequency. Beam) to which the terminal accesses the RACH.

In an embodiment, when the terminal performs RACH in 2 of sub-slots 1-5, the base station grants the size of the UL resource corresponding to the second MSG3 size based on the pre-configured look up table (LUT). may include

38 is a diagram illustrating an example of a signaling operation between a terminal and a base station for determining and controlling an RRC state (Inactive and/or Active) for data transmission in an NR system according to a second embodiment of the present invention. Based on the base station configuration and the event trigger of the terminal, the terminal transmits terminal information (RSPR or BSR) to the base station through additional feedback, and the base station may determine an RRC state related operation mode to transmit data.

In the case of this operation, since the BSR or RSRP information of MSG3 is transmitted before data transmission, the base station knows the information. It can be allocated to the minimum size required for , or the maximum size allowed by the channel conditions).

39 is a view for explaining a method for determining a MSG3, MSG5, or RRC state transition related operation mode in which the terminal transmits data based on an event trigger configured by the base station for data transmission in the NR system according to the second embodiment of the present invention; am.

Referring to step S3901, the base station may set the buffer size and RSRP threshold for determining the data transmission mode by the terminal.

Referring to step S3903, it is checked whether the UE buffer size is greater than 0, and if the UE buffer size is greater than 0, it can be checked whether the RSRP is greater than the RSRP threshold for MSG3 (RSRP_thresold_MSG3) in step S3905. If RSRP is greater than the RSRP threshold for MSG3 (RSRP_thresold_MSG3), it may be confirmed in step S3907 whether the UE buffer size is greater than the buffer size threshold for MSG3 (T_thresold_MSG3). If the UE buffer size is greater than the buffer size threshold for MSG3 (T_thresold_MSG3), it may be checked in step S3909 whether the UE buffer size is greater than the buffer size threshold for MSG5 (T_thresold_MSG5). If the UE buffer size is greater than the buffer size threshold (T_thresold_MSG5) for MSG5, in step S3911, Data and BSR are transmitted to MSG3, Data is transmitted to MSG5, and an RRC response (Resume) can be transmitted to MSG6. In step S3913, the UE may transition to the RRC Active state.

If RSRP is smaller than the RSRP threshold (RSRP_thresold_MSG3) for MSG3 in step S3905, data can be transmitted to MSG5 in step S3915. Thereafter, in step S3921 , it may be checked whether the UE buffer size is greater than the buffer size threshold value for MSG5 (T_thresold_MSG5). If the UE buffer size is greater than the buffer size threshold (T_thresold_MSG5) for MSG5 in step S3921, after data transmission to MSG5 in step S3923, an RRC response (resume) may be transmitted to MSG6. In step S3925, the UE may transition to the RRC Active state. If the UE buffer size is smaller than the buffer size threshold (T_thresold_MSG5) for MSG5 in step S3921, data may be transmitted to MSG5 in step S3927 and an RRC response (Suspend) may be transmitted to MSG6.

If the UE buffer size is smaller than the buffer size threshold for MSG3 (T_thresold_MSG3) in step S3907, data may be transmitted to MSG3 in step S3917 and an RRC response (Suspend) may be transmitted to MSG4.

The RRC message transmitted to the corresponding RACH MSG4 (message4) includes a method of transmitting an RRC connection response or an RRC resume response, or an RRC suspend response, an RRC connection resume response, an RRC connection suspend response, and the like.

If the UE buffer size is smaller than the buffer size threshold for MSG5 (T_thresold_MSG5) in step S3909, data and BSR are transmitted to MSG3 in step S3919, data is transmitted to MSG5, and an RRC response (Suspend) can be transmitted to MSG6.

In this case, the base station includes an operation of explicitly indicating the target RRC state (target state = RRC_IDLE, RRC_INACTIVE, RRC_CONNECTED) in the RRC connection response (suspend) or RRC connection suspend message transmitted to MSG4. Based on this, the UE transitions to the RRC state.

Alternatively, when uplink data transmission is performed in the RRC connection request transmitted to RACH MSG3, the base station determines the RRC state of the terminal and implicitly informs the terminal in an RRC connection response. If the base station controls the transition of the RRC state of the terminal to the RRC_CONNECTED (Active) state, the base station instructs the terminal with an RRC connection response (resume) or RRC connection resume message transmitted to MSG4.

Conversely, when the terminal decides to stay in RRC_Inactive, the base station instructs the terminal with an RRC connection response (suspend) or RRC connection suspend message transmitted to MSG4.

When the MSG4 instructs the UE to transition to RRC_INACTIVE (or RRC_IDLE), it includes an operation of updating the relevant parameter operating in the RRC state and transmitting it in the MSG4.

When the UE transitions to RRC_IDLE, the corresponding information included in MSG4 is

- cause information

- redirect carrier frequency

- mobility control information

- frequency/RAT deprioritisation information

- Includes wait timer.

In another embodiment, when the UE transitions to RRC_INACTIVE, the corresponding information included in MSG4 is

- cause information

- redirect carrier frequency

- mobility control information

- Including frequency/RAT deprioritisation information and additionally

- UE identity (or UE context identity

- RAN configured DRX cycle,

- RAN periodic notification timer;

- RAN notification area

- Includes wait timer.

However, when a fake UE or a fake base station attempts a DoS attack, the information that can be updated and transmitted to MSG4 is different for security reasons.

In other words, the information that can be updated and transmitted to MSG4 varies depending on whether MSG4 is transmitted to SRB0 (security applied cyphering) or SRB1 is transmitted (security not applied not cyphering).

When MSG4 transfer succeeds in retrieving (retrieving) the UE context previously stored in the terminal from the anchor base station and new security key information (K_gNB_target) can be created from the target base station, it is possible to transmit the corresponding information to SRB1. Conversely, the UE context In the case of failure to retrieve (retrieval) from the anchor base station or the base station rejects the RRC connection request of the corresponding terminal due to congestion, new security key information (K_gNB_target) cannot be generated from the target base station, so MSG4 is transmitted to SRB0. do.

For example, the waiting timer is a timer in which the terminal waits for a certain amount of time after receiving the RRC Connection Response from the base station and operates so that the RRC connection request can be attempted again when the corresponding timer expires. If the fake base station sets a long wait timer, the corresponding terminal cannot start data transmission by requesting an RRC connection request for a long time, so it may damage the QoS of the terminal. However, if the network limits the range of the wait timer that can be set in SRB0, the fake base station cannot succeed in an attack that sets the wait timer to a value that is too large.

Therefore, MSG4 transmitted to SRB1 includes the operation of setting the range of the wait timer to be adjustable. In addition, MSG4 transmitted from SRB0 includes an operation for enabling the wait timer to be set only within a previously set (pre-configured) limited range.

For this, the category and maximum value (limit value) of the wait timer include the method of setting in the previous RRC message to which security is applied (SRB1 or cyphering application, or integrity applied) The operation of setting the category and maximum value (limit value) of the wait timer can be performed through system information as well.

In other words, MSG4 transmitted to SRB0 or SRB1 may transmit a waiting timer. However, MSG4 transmitted to SRB0 includes the operation of setting a relatively short waiting timer with a limited maximum value.

In another embodiment, when MSG4 is transmitted to SRB0, the related parameter is not updated, but a fixed value is used, and when MSG4 is transmitted to SRB1, the related parameter is updated. The corresponding parameter includes cause information, redirect carrier frequency, mobility control information, frequency/RAT deprioritisation information, and Wait timer as the corresponding information included in MSG4 when the UE transitions to RRC_IDLE as described above.

In another embodiment, when the UE transitions to RRC_INACTIVE, the corresponding information included in MSG4 includes cause information, redirect carrier frequency, mobility control information, frequency/RAT deprioritisation information, and additionally UE identity (or UE context identity, RAN configured It includes a DRX cycle, a RAN periodic notification timer, a RAN notification area, and a Wait timer.

That is, when the buffer state size of the terminal is 0 or more, when data to be transmitted occurs, it is possible to determine whether to transmit data to MSG3 based on the maximum coverage that the RSRP of the terminal can transmit the RRC connection request or RRC resume request of MSG3. Thereafter, it is operated by sequentially determining whether to transmit data to MSG3 and whether to transmit additional data to MSG5 or whether to transmit additional data after transition to the active state according to the buffer state information of the terminal.

At this time, when data transmission is completed, an RRC suspend message is transmitted as an RRC response message, and an RRC resume message is transmitted in case of an additional transmission operation in an active state.

40 shows MSG3 or MSG5 to which the terminal transmits data when the terminal operates without additional feedback on the corresponding event to the base station based on an event trigger configured by the base station for data transmission in the NR system according to the second embodiment of the present invention. Alternatively, a diagram for explaining an operation of a method of determining an RRC state transition related operation mode.

In the case of this operation, since the base station cannot know the corresponding information before transmitting the BSR or RSRP information of MSG3, when MSG3 is allocated to the base station, the allocation size of MSG3 can be assigned as a default without the corresponding BSR or RSRP information.

Referring to step S4001, the base station may set the buffer size and RSRP threshold to determine the data transmission mode to the terminal.

Referring to step S4003, it is checked whether the UE buffer size is greater than 0, and if the UE buffer size is greater than 0, it can be checked whether the RSRP is greater than the RSRP threshold for MSG3 (RSRP_thresold_MSG3) in step S4005. If RSRP is greater than the RSRP threshold for MSG3 (RSRP_thresold_MSG3), it can be checked whether the UE buffer size is greater than the buffer size threshold for MSG3 (T_thresold_MSG3) in step S4007. If the UE buffer size is greater than the buffer size threshold for MSG3 (T_thresold_MSG3), it may be checked in step S4009 whether the UE buffer size is greater than the buffer size threshold for MSG5 (T_thresold_MSG5). If the UE buffer size is greater than the buffer size threshold for MSG5 (T_thresold_MSG5), in step S4011, the base station allocates a default MSG3 size, the terminal transmits data to MSG3, and the remaining traffic is transmitted to the BSR. Data can be transmitted to MSG5 and RRC response (Resume) can be transmitted to MSG6. In step S4013, the UE may transition to the RRC Active state.

If the RSRP is smaller than the RSRP threshold for MSG3 (RSRP_thresold_MSG3) in step S4005, the base station default MSG3 size is allocated in step S4015, and the terminal transmits the BSR without transmitting data to MSG3. You can send data to After completion of step S4015, the operation after step S4009 may be performed.

If the UE buffer size is greater than the buffer size threshold for MSG3 (T_thresold_MSG3) in step S4007, the base station default MSG3 size is allocated in step S4017, the terminal transmits data to MSG3, and an RRC response (Suspend) may be transmitted to MSG4.

If the UE buffer size is smaller than the buffer size threshold (T_thresold_MSG5) for MSG5 in step S4009, the base station allocates a default MSG3 size in step S4019, and the terminal transmits data to MSG3 and transmits the remaining traffic to the BSR and based on the BSR Data can be transmitted to MSG5 by receiving UL grant and an RRC response (Suspend) can be transmitted to MSG6.

41 is a diagram illustrating MSG3 or MSG5 to which the terminal transmits data when the terminal transmits additional feedback on a corresponding event to the base station based on an event trigger configured by the base station for data transmission in the NR system according to the second embodiment of the present invention. Alternatively, it is a diagram explaining an operation of a method of determining an RRC state transition related operation mode.

In the case of this operation, since the BSR or RSRP information of MSG3 is transmitted before data transmission, the base station knows the information. It can be allocated to the minimum size required for , or the maximum size allowed by the channel conditions).

Referring to step S4101, the base station may set the buffer size and RSRP threshold to determine the data transmission mode to the terminal.

Referring to step S4103, it is checked whether the UE buffer size is greater than 0, and if the UE buffer size is greater than 0, it can be checked whether the RSRP is greater than the RSRP threshold for MSG3 (RSRP_thresold_MSG3) in step S4105. If RSRP is greater than the RSRP threshold for MSG3 (RSRP_thresold_MSG3), it may be confirmed in step S4107 whether the UE buffer size is greater than the buffer size threshold for MSG3 (T_thresold_MSG3). If the UE buffer size is greater than the buffer size threshold for MSG3 (T_thresold_MSG3), it may be checked in step S4109 whether the UE buffer size is greater than the buffer size threshold for MSG5 (T_thresold_MSG5). If the UE buffer size is larger than the buffer size threshold for MSG5 (T_thresold_MSG5), in step S4111, the base station allocates an appropriate MSG3 size, and the terminal transmits data to MSG3 and the remaining traffic to the BSR. Data can be transmitted to MSG5 and RRC response (Resume) can be transmitted to MSG6. In step S4013, the UE may transition to the RRC Active state.

If RSRP is smaller than the RSRP threshold (RSRP_thresold_MSG3) for MSG3 in step S4105, the base station allocates the minimum MSG3 size in step S4115, and the terminal transmits the BSR without transmitting data to MSG3. You can send data to After step S4115 is completed, the operation after step S4109 may be performed.

If the UE buffer size is smaller than the buffer size threshold for MSG3 (T_thresold_MSG3) in step S4107, an appropriate MSG3 size is allocated to the base station in step S4117, the UE transmits data to MSG3, and an RRC response (Suspend) may be transmitted to MSG4.

If the UE buffer size is smaller than the buffer size threshold for MSG5 (T_thresold_MSG5) in step S4109, an appropriate MSG3 size is allocated to the base station in step S4119, and the terminal transmits data to MSG3 and transmits the remaining traffic to the BSR, and the corresponding BSR-based UL By receiving the grant, data can be transmitted to MSG5 and an RRC response (Suspend) can be transmitted to MSG6.

42 is an operation for determining in which RRC state data transmission is performed as an operation according to the second embodiment of the present invention. Based on the event trigger configured by the base station, if there is data to be transmitted by the terminal, additional feedback for the corresponding event is required and transmitted. Based on this, the base station may determine the RRC state transition related operation mode.

In this case, the criteria for the event trigger configured by the base station may be network loading, UE mobility, UE battery status, UE location (cell center or boundary, respectively, or a combination thereof).

Although data transmission in the existing idle state has disadvantages in reducing channel access efficiency due to grant-free transmission and reducing transmission spectral efficiency due to the subtitle of information such as CQI and BSR, the terminal operation in the newly defined Inactive state exists. In the design method, methods for improving spectral efficiency and improving channel access when transmitting traffic of a UE in an Inactive (RRC_INACTIVE) state are additionally proposed in FIGS. 43 to 45 .

43 is a diagram illustrating an example of an information acquisition method for improving spectral efficiency when data transmission is performed in an NR RRC inactive state according to the second embodiment of the present invention.

The terminal-to-base station distance (Short/Long Coverage) may be determined based on, for example, received RSRP/RSRQ based on the terminal-to-base station pathloss. In an embodiment, since the corresponding information can be identified in the RA preamble transmission and RAR reception process during RACH operation, an RRC state related operation mode for transmitting data can be determined based on this information.

: This information is the standard for determining the payload length that can be transmitted in the Inactive state.

- When retaining CQI and similar information, it is advantageous to transmit data in Inactive as it is closer (higher received signal quality).

- In the absence of CQI and similar information, the closer the distance (higher received signal quality), the more advantageous the method of transmitting data in the active state.

In the embodiment, when RACH is used as an example of grant-free transmission, an operation of determining a RACH Message 1/2 based CQI (MCS) as a method of acquiring CQI information based on previous transmission DL/UL;

In more detail, the existing RACH preamble performs Tx power ramping up, reaches Tx power to reach the base station, and receives RAR. As a result, the base station cannot know the Tx power information of the terminal. This is because the existing RACH Preamble UL Tx power is not fixed.

* As a solution, by adding a Tx power index to the RACH preamble sequence and informing the base station of the UL tx power level, the base station identifies the Tx power of the successfully received RACH preamble and uses the MCS mapped to the corresponding CQI for subsequent transmission. , the operation of allocating the corresponding MCS-based radio resource (frequency time, etc.) even when the UL grant is applied

* Transmits the existing RACH preamble sequence and performs Tx power ramping up to receive RAR after reaching Tx power to reach the base station. A method of transmitting this by applying this to Message3/or Message5. In this case, since the base station does not know the applied MCS, the UL grant is performed incorrectly in unit units, and the UL payload (header is transmitted as a fixed MCS, payload MCS information is indicated in the header) How to

In the embodiment, when RACH is used as an example of grant-free transmission, as a method of acquiring CQI information based on previous transmission DL/UL

A method of indicating whether the CQI is valid when transmitting previously transmitted RACH data and transmitting the feedback to the base station by adjusting the CQI change to (+alpha, -beta) within a certain time, for example, within 1 second, or the terminal itself It may include a method of adjusting and transmitting by judgment.

In the embodiment, when RACH is used as an example of grant-free transmission, a method of applying a security key to data to be piggybacked based on RACH Message 3/5;

Because the NAS security key that can be utilized in the existing Inactive mode requires security processing in the MME,

Problem 1: Exceeded MME capacity - Relatively large data, MME expansion is required

Problem 2: Delay - SRB is a cause of delay due to the long base station routing path.

Therefore, instead of using NAS security key (SRB-based transmission), AS (DRB) security key is used.

* Last eNB (AS security key based) Inactive status data transmission operation,

In the inactive state, since the terminal and the network have the UE context including the security key, data transmission is performed using the existing AS security key within a predefined period of validity (security timer).

* A predefined period of validity (security timer) has elapsed or (security timer expired)

* When a base station change occurs due to terminal movement after RRC release (suspend) (Other transmission options are operated when gNB is changed)

- Inactive transmission with NAS security applied,

- Alternatively, after switching to ACTIVE, updating AS security and applying it includes a method of transmitting data.

In such an inactive state, it may include an operation and method in which the terminal feeds back information on the setting of the security key operation to be applied to data transmission, and the base station sets and transmits the information.

44 is a diagram illustrating an example of a method for acquiring information for improving channel access in the case of efficiently performing transmission in an NR RRC Inactive state according to the second embodiment of the present invention. 44 is an example of a method of acquiring additional information required before an active transition when performing RACH in an inactive state.

A method of reducing the data transmission delay time by transmitting active transmission-related information such as SR, BSR, and UL grant required for the existing UL data transmission in the inactive (small) data transmission section in advance is as follows.

- SR allocation

- Buffer size information (BSR and similar information)

- UL grant, DL scheduling resource allocation in advance

- UE ID (C-RNTI) assignment

- The operation including the dedicated RACH allocation is loaded as information in the sequence and payload including the RACH message 1/2/3/4/5, and this is not limited to the message included in the RACH operation, but grant-free It can include transmission of Inactive state data, which is a stage before the transition.

45 is a diagram illustrating an example of a method for improving channel access efficiency in the case of efficiently performing transmission in the NR RRC Inactive state according to the second embodiment of the present invention. In particular, FIG. 45 is a diagram illustrating an example of a method for acquiring information for improving channel access when data is transmitted while maintaining the inactive state of the terminal. When performing RACH in the inactive state, it relates to a method of acquiring additional information necessary before the active transition This is an example.

The existing RACH and RACH separation method for data transfer include the operation of dividing the preamble sequence domain, time and frequency, and beam resource, and based on this, the existing RACH (RRC State transition, TA update, etc.) and RACH for inactive state data transmission are used. It may include an operation of determining the priority of the corresponding transmission by dividing it.

A method to apply different related barring statistics when applying barring in situations such as network congestion Including barring action and reverse action.

In addition, as a method for classifying and supporting QoS levels when data transmission is performed in the RRC Inactive state, the RACH separation method includes an operation of dividing into a preamble sequence domain, time and frequency, and beam resource, and traffic generated based on this. It may include the operation of determining the priority of the transmission by classifying the RACH for each QoS.

A method to apply different related barring statistics when applying barring in situations such as network congestion Including barring action and reverse action.

46 is a diagram illustrating multiple UL grant allocation and a corresponding UL transmission procedure based on terminal buffer state information when data is transmitted in the NR RRC Inactive state according to the second embodiment of the present invention.

When the UE knows the transmission data capacity, after MSG3 transmission, the buffer status information required for additional transmission is piggybacked to MSG3 as BSR and transmitted. Based on this, the UL grant for MSG5 transmission of subsequent data can be transmitted to MSG5. In this case, multiple UL grants for a case where a plurality of data transmissions are required for MSG5 may be used.

The multiple UL grant refers to allocating a plurality of UL transmission resources, and means an operation of allocating UL resources within one sub-frame or UL grants spanning multiple sub-frames.

In addition to the baseline operation of performing continuous PDCCH decoding when data is received in MSG5, the UE performs UL transmission by turning on only the resource corresponding to the slot/sub-frame corresponding to the UL grant, and performs additional update (checking whether DL transmission is added). action can be performed. The UE operates in a selective non-continuous turn on from the Multiple UL grant to the resource corresponding to the last UL grant, and thereafter, in the operation for receiving the RRC response (suspend or resume), an offset for receiving the RRC response (suspend or resume) (base station is UL It is possible to selectively receive data by setting a receiving window for receiving and decoding data and generating ACK/NACK) and RRC response (suspend or resume + ACK/NACK). The UE includes the operation of setting a new RRC response reception timer (RRC-response waiting timer or RRC-response waiting window) for the waiting window waiting to receive the RRC response (suspend or resume + ACK/NACK) of the corresponding operation. .

47 is an operation by allocating a preamble sequence and resources for dedicated RACH and grant-free transmission during data transmission in the NR RRC Inactive state according to the second embodiment of the present invention, and setting a valid timer for these resources. It is a drawing.

As an example of an operation when the UE transmits data in inactive data, contention-based RACH may be performed in the initial transmission, and then a resource allocation operation for continuous data transmission may be performed for a predetermined time (consecutive data transfer timer).

The resource allocation is performed within a predetermined time (consecutive data transfer valid timer) after performing contention-based RACH in the initial transmission of the effective time.

After the second, an operation of allocating a RACH preamble sequence for a dedicated RACH operation for inactive data transmission may be included.

The corresponding operation allocates the corresponding RACH preamble sequence to the RRC response message (suspend) transmitted by the base station when the first data transmission is completed in the inactive state or the first data transmission that occurs after a valid time (consecutive data transfer valid timer) in the previous data transmission is completed It may include an operation of loading information.

The resource allocation is performed within a predetermined time (consecutive data transfer valid timer) after performing contention-based RACH in the initial transmission of the effective time.

Operation in which the base station allocates and indicates radio resources to which the terminal can access grant-free in order to support the grant-free operation for the second and subsequent inactive data transmission The operation of loading the allocation information of the corresponding RACH preamble sequence in the RRC response message (suspend) transmitted by the base station upon completion of the first data transmission occurring after a time (consecutive data transfer valid timer) may be included. 48 illustrates a criterion for determining whether to perform a contention based RACH-based data transmission operation, a dedicated based RACH-based data transmission operation, or a grant-free based data transmission when data is transmitted in the NR RRC Inactive state according to the second embodiment of the present invention. It is a drawing showing

As shown in FIG. 48, in the operation of transmitting continuous data to MSG5 after MSG3 data transmission, the criterion for determining whether to perform the contention based RACH-based data transmission operation or the dedicated based RACH-based data transmission operation or the grant-free based data transmission is It is as below.

According to an embodiment, if there is a sufficient number of extra RACH preambles depending on whether a valid number of preambles starts data transmission in an inactive state and can be allocated to terminals within a subsequent effective time (consecutive data transfer timer), Dedicated based A RACH-based data transmission operation may be performed.

According to another embodiment, when synchronization information needs to be acquired through additional RACH operation depending on whether synchronization information is valid by performing RACH through data transmission in the previous inactive state, RACH-based data transmission is performed, and the previous transmission is performed. Grant-free transmission can be performed when there is valid synchronization information through the

The base station can determine whether to transmit such 1) contention-based RACH, 2) dedicated-based RACH, and 3) grant-free data. The corresponding operation is an indication operation by loading in the RRC response message (suspend) transmitted by the base station upon completion of the first data transmission that occurs after the first data transfer in the inactive state or the valid time in the previous data transfer (consecutive data transfer valid timer); An operation in which the base station notifies the terminal as system information (or on-demand SI) may be included.

When the inactive state starts, the base station within the RRC configuration message

- Valid time from previous data transfer (consecutive data transfer valid timer)

- Transmission mode for second transmission

1) Contention-based RACH,

2) Dedicated-based RACH;

3) Whether or not to transmit grant-free data is determined by the base station and includes a method for transmitting to the terminal.

Based on the setting, the UE may determine whether the elapsed time from the inactive state to the previous transmission is within the valid time (consecutive data transfer valid timer).

If the elapsed time is within the effective time, or even within the effective time, if the synchronization information (synchronization information) is valid according to whether the synchronization information (synchronization information) is valid by updating the synchronization information in the previous transmission using the RACH procedure, etc. 3) Grant-free transmission can be done

If a valid time (consecutive data transfer valid timer) has elapsed from the previous transmission or if the synchronization information (synchronization information) is invalid because the synchronization information is not updated in the previous transmission using the RACH procedure, etc., the RACH procedure can be performed.

In this case, if the allocated RACH preamble information exists, 2) dedicated-based RACH may be performed, and if the allocated RACH preamble information does not exist, 1) Contention-based RACH may be performed.

49 illustrates an additional data transmission procedure after initial UL data transmission when data is transmitted in the NR RRC Inactive state according to the second embodiment of the present invention.

In one embodiment of determining whether to transmit from RRC_Inactive state or transition to RRC_connected (active) when transmitting data of the terminal, whether the terminal is within the anchor base station where the previous UE context including the security key is stored If the information is transmitted together when the UE transmits the RRC_connection request (RRC resume request) and it is within the anchor base station where the previous UE context including the security key is stored, the base station may perform data transmission in the RRC_INACTIVE state.

When moving out of the anchor base station, it transitions to RRC_CONNECTED and includes an operation of determining an operation to transmit data and an operation of indicating this with an RRC connection response message. (RRC resume: transfer data by switching to connected state, RRC suspend message: maintain RRC_INACTIVE state and transfer data)

In the present invention, the same anchor base station transmits and receives information indicating whether within each unit by changing within the same sector, the same PDCP entity, the same DU, and the same CU, and determines whether the RRC state transition is based on this, or a new security It may include the operation of generating a key.

Depending on whether the terminal is within the anchor base station that stores the previous UE context including the security key or whether the base station has changed, information indicating this is transmitted together when the terminal transmits the RRC_connection request (RRC resume request), and based on this, the information indicating this is transmitted outside the anchor base station. It may include an operation of generating a new security key when moving.

The operation of determining whether the same anchor base station is within each unit by changing within the same sector, the same PDCP entity, the same DU, and the same CU is a Physical Cell ID or / and System information that the base station transmits Broadcast / unicast to System information Broadcast / Based on unicast transmission and CU entity, DU entity, and PDCP entity information set by RRC, the terminal receiver determines whether to change to the base station or indicates whether the terminal has received Physical Cell ID, CU entity, DU entity, PDCP entity information The terminal may include the operation of determining whether to change by copying transmission to the base station, and the base station comparing it with its Physical Cell ID, CU entity, DU entity, and PDCP entity information.

As another example of determining whether to transmit from RRC_Inactive state or transition to RRC_connected (active) when transmitting data of the UE, the buffer size of the UE transmitted together when the UE transmits RRC_connection request (RRC resume request), the amount of data to be transmitted, Based on the BSR, when the base station receives a BSR below the threshold, data transmission is performed in the RRC_INACTIVE state, and when a BSR above the threshold is received, the base station transitions to RRC_CONNECTED to determine the operation to transmit data, and this is converted into an RRC connection response message. indication. (RRC resume: data transfer is performed by switching to connected state, RRC suspend message: data transfer is performed while maintaining RRC_INACTIVE state)

When the UE buffer size during initial transmission is greater than or equal to the threshold for RRC transition determination, the operation of directly transitioning to RRC_CONNECTED (or RRC_ACTIVE) through an RRC connection response (RRC resume message) without transmitting the initial transmission UL data;

or an operation of transmitting only initially transmittable UL data in the INATIVE state, transmitting a DL acknowledgment corresponding to the initially transmitted UL data in an RRC connection response (RRC resume message), and transitioning to RRC_CONNECTED (or RRC_ACTIVE); and

If the UE buffer size during initial transmission is less than or equal to the threshold for RRC transition determination, it does not transition to RRC_CONNECTED (or RRC_ACTIVE) and performs subsequent data transmission after the initial transmission while maintaining RRC_INACTIVE,

In this case, when all of the buffered data cannot be transmitted in the first transmission, data and BSR are transmitted together to notify the base station that transmission is required later;

The base station performs a UL grant based on the BSR included in the data transmission in the inactive state of the terminal, which multiplexes and transmits the DL Acknowledgment for the transmission of the first UL data in the RACH contentionresolution message;

The terminal transmits residual UL data in the Inactive state and, when all buffered data cannot be transmitted in this transmission, transmits both Data and BSR to inform the base station that transmission is required later;

In this case, the buffered data that the terminal considers transmission is an operation including residual data of the previous transmission and (generated) data newly arrived at the terminal after the previous transmission,

At this time, if the UE buffer size is less than or equal to the threshold for RRC transition determination, the operation of performing data transmission while maintaining RRC_INACTIVE without transitioning to RRC_CONNECTED (or RRC_ACTIVE);

When the buffered data that the terminal considers to be transmitted is larger than the previous UL grant when performing subsequent UL data, the terminal transmits the data and the BSR together and informs the base station that transmission is required later;

The base station receiving this transmits and receives by multiplexing/de-multiplexing at the MAC PDU level together with the DL acknowledgment (DRB) and RRC connection response (RRC suspend) (SRB1) corresponding to the subsequent UL data that received the BSR-based UL grant transmission. method;

A method for the UE to repeatedly perform subsequent UL data transmission procedures as in an embodiment based on the received UL grant; When performing subsequent UL data, if the buffered data that the UE considers for transmission is smaller than the previous UL grant, the UE an operation of notifying the base station that additional transmission is not necessary after transmitting only data or transmitting it together with a BSR (=0) value;

Upon receiving this, the base station does not transmit the UL grant based on the BSR, but multiplexes/de-multiplexes it at the MAC PDU level together with the DL acknowledgment (DRB) and RRC connection response (RRC suspend) (SRB1) corresponding to the received subsequent UL data. how to send and receive;

Thereafter, the UE maintains the INACTIVE state and includes a method of restarting the initial UL data transmission procedure when additional UL data is generated.

If the UE buffer size is greater than or equal to the threshold during subsequent transmission after the initial transmission within the RRC_INACTIVE state, the operation of directly transitioning to RRC_CONNECTED (or RRC_ACTIVE) through the RRC connection response (RRC resume message) without transmitting the initial transmission UL data;

Alternatively, only subsequent transmittable UL data is transmitted in the INATIVE state, a DL acknowledgment corresponding to the UL data initially transmitted in an RRC connection response (RRC resume message) is transmitted, and an operation of transitioning to RRC_CONNECTED (or RRC_ACTIVE) includes;

Also, when performing subsequent UL data after initial transmission, if the base station is within the anchor base station where the previous UE context including the security key is stored, the base station performs data transmission in the RRC_INACTIVE state, and if it moves out of the anchor base station, it transitions to RRC_CONNECTED to transmit data. It includes an operation for determining and an operation for indicating this in an RRC connection response message.

50 is a diagram illustrating an example of traffic characteristics of a keep alive message of a specific application according to the second embodiment of the present invention.

As observed in FIG. 50, in the case of keep alive traffic, uplink/downlink traffic bursts are transmitted/received in succession, and after a short burst, no traffic is generated for a relatively long time, and then uplink/downlink traffic bursts are transmitted/received in succession. am. The specific traffic payload size, inter-packet arrival interval, and the number of uplink/downlink traffic packets within one burst vary depending on the application and server.

As a method for improving channel access efficiency in the case of performing data transmission in the RRC Inactive state, this method can be applied as a method to increase the transmission efficiency of the initial data transmission and subsequent link transmission continuously, uplink It can be applied to the corresponding downlink traffic to support traffic, for example, ACK/NACK of MAC/RLC level, that is, transmission/reception of ARQ/HARQ response.

1) A method of permanently allocating radio resource grants (eg, dedicated RACH or SR resources, etc.) for inactive terminals to all terminals;

1-1) or a method of statically allocating a terminal designated as (mode 1) or mode 3) among terminals in an inactive state because there is a high possibility that the resource is insufficient to allocate to all inactive terminals;

2) A method of allocating radio resource grants (eg, dedicated RACH or SR resources, etc.) for inactive terminals periodically to all terminals

2-1) or a method of periodically allocating a terminal designated as (mode 1) or mode 3) among terminals in an inactive state because there is a high possibility that the resource is insufficient to allocate to all inactive terminals;

- The corresponding period is based on the terminal's application information or previous activation history, base station decision or terminal request (feedback),

3) A method of transmitting data through contention (non-orthogonal channel access) whenever data occurs in the inactive state based on grant-free,

4) An operation including a method of performing grant-free transmission only initially and then performing grant-based transmission for consecutive packets,

4) As a specific operation for the method, the two-step Grant-free/Grant continuous transmission method is

Grant-free transmission of the initial packet: For example, contention-based RACH-based transmission is performed based on contention, and for subsequent packets, for example, dedicated-based RACH or scheduled-based data transmission is performed by grant transmission.

- In a specific embodiment, since allocation of the dedicated RACH preamble is highly likely to be insufficient resources to allocate to all inactive terminals, a limited time for terminals designated as (mode 1, in which data transmission starts in inactive) or mode 3) among terminals in an inactive state (Short duration) How to allocate a valid preamble

In the Dedicated RACH Preamble allocation or UL grant / DL scheduling (Paging period PF / PO adjustment) method valid for this limited time

* Determination of the limited time based on data traffic characteristics is explicitly (explicitly) based on the average duration of uplink/downlink traffic packets within one burst in the traffic characteristics of keep alive message illustrated in FIG. 2L. The action of setting and sending

* Alternatively, based on the fixed timer (between inter-arrival), the arrival time of uplink/downlink traffic packets within a burst includes an operation method of updating the validity of resources valid for a limited time when a packet arrives within this timer.

A method of transmitting BSR-like information to the RA preamble in a method of determining, for example, RACH Message3/5 length as an operation based on the terminal/base station buffer status, BSR, and similar information as a valid time determination method, (addition of a new field to the RA preamble For example, a method of transmitting terminal buffer status information to a base station through Inactive_BSR or RA preamble group, UL grant transmission operation in RA response based on this, and a method of performing differential allocation of UL resource length of Message3/5 compared to existing RACH;

In the inactive state, the data transmission method supports the case where the data to be transmitted in data transmission is greater than or less than the packet length.

- Base station setting for whether to support fragmentation/reassemble for the corresponding traffic (performs RRC configuration-based last connected RRC configuration-based operation or SI Broadcast-based update-based configuration operation)

As an example of the operation, if multiple transmissions of RACH message3 with continuous traffic size are required, an additional UL grant is received by adding a next bit as a new field to Message3, and the next data is continuously transmitted as RACH message3 without RACH message1/2 method,

In this case, a header field is required to support Reassemble, and for example, by applying 2 bits, the first transmission packet is marked with 10, the middle packet is marked with 00, the last packet is marked with 01, and so on.

- Base station setting for multiplexing support (performing last connected RRC configuration-based operation based on RRC configuration or configuration operation through SI Broadcast-based update)

In one embodiment, for example, when multiplexing is supported, a field is required and valid in the header, but data length information and other multiplexed packets and, when multiplexing is not supported, includes an operation for classifying a zero padding area.

The data transmission method in the inactive state described above can be applied to both uplink and downlink. In particular, the downlink transmission method is a method of transmitting downlink data in the inactive state.

1) As a way to improve paging

* The existing paging concatenates and transmits the ID of the UE to be paging from the PDSCH mapped in the PDCCH, and the operation method of piggybacking the DL data to the corresponding PDSCH and transmitting it;

2) Operation including a grant-free transmission scheme (eg, data piggyback transmission in RACH message 4) after receiving the existing paging

This includes an operation in which the base station sets the downlink transmission mode to be used when the terminal transmits downlink data in an inactive state, such as system information or RRC configuration.

The procedure required for RACH contention resolution of data transmission in the inactive state is

When data is transmitted as RACH Message5, contention resolution is performed with C-RNTI as in the existing method.

When data is transmitted in RACH Message3/Message 4, contention resolution is performed based on RA-RNTI or T-CRNTI;

In addition, it includes the operation of performing contention resolution based on IDs of P-RNTI, S-TIMSI, and IMSI, which are IDs available to the terminal in the inactive state, and IDs in combination.

The terminal ID required for the corresponding uplink/downlink transmission for data transmission in the inactive state is

1) Transmission based on P-RNTI within PAU (Paging area unit) based on RAN-based Paging, or

2) If the terminal is camping without moving in the base station (last cell) that was recently RRC connected, transmit based on C-RNTI or

3) or an operation of transmitting based on P-RNTI and

4) Alternatively, a new ID required for RRC Resume is defined with UE ID, for example, all CID or a few upper/lower bits + a combination of C-RNTI, etc. How to use the course

5) Alternatively, a method of generating a new ID based on IDs and combinations of P-RNTI, S-TIMSI, and IMSI, which are IDs available to the terminal in the Inactive state, and using it in the data transmission process

It includes an operation in which the base station sets the terminal ID to be used when the terminal transmits downlink data in an inactive state, such as system information or RRC configuration.

<Third embodiment>

The present invention proposes a method for transmitting/receiving and setting numerology information in a 5G mobile communication system. Various services (or slices) such as enhanced Mobile BroadBand (eMBB), Ultra Reliable and Low Latency Communication (URLLC), and enhanced Machine Type Communication (eMTC) are expected to be supported in the 5G mobile communication system. This can be understood in the same context that the 4G mobile communication system, LTE, supports voice-specific services such as VoIP (Voice over Internet Protocol) and BE (Best Effort) services. In addition, it is expected that various numerologies will be supported in the 5G mobile communication system. This specifically means subcarrier spacing, etc., which directly affects the Transmission Time Interval (TTI). Therefore, it is expected that TTI of various lengths will be supported in the 5G mobile communication system. This can be seen as one of the characteristics of the 5G mobile communication system, which is very different from the support of only one type of TTI (1 ms) in LTE standardized so far. If the 5G mobile communication system supports a much shorter TTI (eg 0.1 ms) than the 1 ms TTI of LTE, it is expected to be of great help in supporting URLLC that requires a short delay time. Note that in this document, numerology is used as a term that plays a role such as subcarrier spacing, subframe length, symbol/sequence length, etc. The base station may be represented for various abbreviations such as gNB, eNB, NB, BS, etc. The terminal may be represented for various abbreviations such as UE, MS, and STA.

The present invention proposes a numerology transmission/reception and setting method in consideration of the characteristics of the 5G mobile communication system, that is, various services and various numerology (TTI) support. The difference from LTE corresponds to a numerology transmission/reception and setting method for supporting dynamically changing numerology in the present invention, whereas the existing method for transmitting/receiving operation according to a fixed numerology corresponds to the method. In addition, since there are advantages and disadvantages depending on the type of numerology transmission/reception method according to the density of the terminal, the transmission/reception method must also be dynamically changed.

First, it is intended to define terms for system and numerology classification assumed in the present invention. The terminal must have at least one or more numerology information given according to the standard. According to this information, the terminal should be able to receive at least the synchronization signal transmitted by the base station of the mobile communication system. The base station may operate a synchronization signal according to a plurality of numerology if it is determined by the standard. If the terminal succeeds in receiving the synchronization signal transmitted by the base station according to a specific numerology, if there is no separate setting from the base station, the numerology applied to the successful synchronization signal or additional numerology that can be derived from the numerology It operates. A collection of one or more numerology that can be identified by successful synchronization signal reception in this way can be called a default numerology set.

On the other hand, the network or base station resides (camped) or is connected (connected) with information on numerology additionally required for each service (or slice) according to the request of the terminal or the judgment of the service (or slice) control server It should be able to set the terminal in A collection of numerology for operating a service/slice that is not basically provided by the network or the base station, but additionally provided as needed may be called a dedicated numerology set.

In the fourth embodiment of the present invention, a procedure and method for setting a dedicated numerology set to a terminal operating according to a default numerology set will be described.

51 is a diagram illustrating various procedures for setting a dedicated numerology set according to a third embodiment of the present invention.

Referring to FIG. 51 , four options transmit dedicated numerology set information or a corresponding ID (identification) to the terminal with different signals at different times.

According to Option 1, the base station must transmit the dedicated numerology set information in the synchronization signal. However, considering the actual synchronization signal reception performance and the reception complexity of the terminal, it can be a considerable burden to load and send various numerology information in a sequence-based synchronization signal.

According to Option 2, the base station must send dedicated numerology set information in an SI (System Information) message. The existing LTE base station transmits the most important SI contents as a Master Information Block as BCH (Broadcast Channel) and transmits additional SI contents at different intervals according to the importance as a System Information Block as a Shared Channel (shared channel). In order to receive the SIB in the Shared Channel, the UE must check a control channel signal that can be distinguished by SI-RNTI (System Information-Radio Network Temporary Identifier). The UE performs a random access procedure and a control/data channel transmission/reception operation in a connected state according to a dedicated numerology set set through an SI message. If the access request performance of random access for each service is different, it is necessary to inform the appropriate random access configuration and required numerology for each service in the SI message.

As another method according to Option 2, the network or base station can send dedicated numerology set information in the paging message, and the terminal can perform a random access procedure according to the dedicated numerology set information included in the paging message. (Mobile terminated) It is limited to the case of a call. Option 3, on the other hand, is a method of performing a common random access procedure irrespective of the terminal and service. This method has the advantage of being able to allocate the numerology required for the connected state operation only to the terminal that undergoes the random access process. Therefore, the network or base station can allocate a dedicated numerology set only when necessary by identifying the type/service/requirement of the terminal when a random access attempt is made by the terminal, thereby contributing to the efficient use of radio resources.

Depending on the scenario, a dedicated numerology set may be assigned through a connection establishment process or a connection-less method. Option 4 shows a process in which the terminal acquires a dedicated numerology set through a connection establishment procedure or a numerology/service/slice request procedure after operating according to the default numerology set and proceeding to the connected state.

Looking at the method of delivering such various dedicated numerology set information, the method in which the base station informs the terminal of the information can be considered in detail with respect to the options as follows.

Option 2)-a: Method of transmitting Minimum SI on BCH

Option 2)-b: Method of transmitting additional SI on BCH

Option 2)-c: A method of transmitting additional SI through a shared channel separated by SI-RNTI

Option 2)-d: A method of transmitting a paging message through a shared channel separated by P-RNTI

Option 3)-a: A method of transmitting a random access response message (msg2) through a shared channel separated by RA-RNTI during the random access procedure

Option 3)-b: A method of transmitting the connection setup complete message (msg4) through the shared channel separated by C-RNTI during the random access procedure

Option 4): A method of transmitting a separate upper layer message to a shared channel separated by C-RNTI after completion of connection establishment

If such a transmission method of the base station is classified, it can be roughly divided into four types.

Method 1: A broadcast signal transmitted by BCH. The UE can receive the BCH according to the synchronization signal detection. The terminal may receive the broadcast signal in the idle state.

Method 2: A broadcast/multicast signal transmitted through a DL-SCH (downlink shared channel). The terminal can receive the broadcast/multicast signal only after receiving and setting the information on the physical layer control/data channel from the minimum SI conforming to the default numerology set. The terminal may receive the broadcast/multicast signal in the idle state.

Method 3: A unicast (UE-specific) signal for a terminal without a connection transmitted through a DL-SCH (downlink shared channel). The terminal can receive the unicast signal only after receiving and setting information on the physical layer control/data channel from the minimum SI conforming to the default numerology set. The UE may receive the unicast signal in the idle state.

Method 4: A unicast (UE-specific) signal for a terminal with a connection transmitted through a DL-SCH (downlink shared channel). The terminal can receive the unicast signal only after receiving and setting information on the physical layer control/data channel from the minimum SI conforming to the default numerology set. The terminal can receive the unicast signal only in the connected state.

63 illustrates options applied in the process of the UE switching from the idle state to the connected state in the above-described methods.

63 is a diagram illustrating options applied in a process in which a terminal switches from an idle state to a connected state according to a third embodiment of the present invention.

Option 1: A dedicated numerology set can be delivered via SI. In this case, the corresponding information may be included in the minimum SI or other SI. In the case of other SI, it may be set and transmitted in a base station-specific or terminal-specific manner. By setting dedicated numerology before the connection establishment procedure, the UE has the advantage of reducing processing overhead.

Option 2: Connection establishment can be performed using both default numerology and dedicated numerology. Through the paging message, the base station may notify the terminal of a service type corresponding to MT (mobile-terminated) data waiting to be transmitted in the network. Based on the corresponding type information, the UE may select a RACH resource and a dedicated numerology set to be used for random access preamble transmission, RAR detection, and data transmission/reception in the connected mode. Downlink and Uplink RRC messages may also be transmitted with a corresponding dedicated numerology set set.

Option 3: Can be delivered via RAR. In this option, SI acquisition, paging, and random access are performed using the default numerology set. When the random access preamble is successfully detected and detected by the base station, a response to the corresponding message is transmitted. In this case, dedicated numerology set information may be transmitted. However, since the UE has set the default when attempting random access, RAR transmission for this also needs to be set as the default set. Accordingly, the base station may transmit by setting an indication for a dedicated set preferred to the corresponding UE, or may allocate among the numerology resources available to the base station itself.

Option 4: Connection establishment can be performed using default numerology. Common control signaling (other SI transmission, paging indication with P-RNTI and RAR) between the terminal and the base station using the default numerology used for initial SI acquisition

It can be used to transmit/receive and transmit RRC messages 3 (Msg3) and 4 (Msg4). In this option, dedicated numerology may be included and transmitted in message 4 for establishing a dedicated connection to the terminal. The terminal needs to inform the base station of preferred or implementable numerology information in advance at the time of initial access.

The above options can also be used to reset the numerology set.

Meanwhile, the suitability of the above four methods may vary according to the density of the terminal and the service/slice. For example, the BCH-based broadcast signal of method 1 is suitable when the number of terminals of the same type in the base station is large. The DL-SCH-based broadcast/multicast signal of method 2 is suitable when a significant number of different types of terminals or terminal groups in the base station are distributed at different ratios. The DL-SCH-based connection-less unicast signal of method 3 can be transmitted limitedly to a requested terminal among terminals in the base station, and is suitable when rapid numerology conversion is required. The DL-SCH connection-based unicast signal of method 4 can be transmitted limitedly to the requested terminals among the terminals in the base station. Do.

However, since methods 1, 2, and 3 except for method 4 must operate even when the terminal is in the idle state, if the base station cannot know which base station the terminal resides in in the idle state, it is difficult to operate an appropriate method according to the density of the terminal. do. In addition, if the base station cannot know the ID of the terminal or the service/slice desired by the terminal, it is difficult to operate a suitable method for each service/slice. On the other hand, in the case of method 4 in which the terminal is already in the connected state, the base station can determine the intention of the terminal to use the service/slice based on the BSR (Buffer Status Report) or information that can be additionally transmitted along with the BSR.

Therefore, in the present invention, presence information indicating that the terminal resides in a specific base station or is close to a specific base station and information that can specify the service/slice of the terminal (eg, terminal/service/slice ID) are added to the uplink signal of the idle mode terminal. A method and procedure for the base station to determine the location and characteristics/identity of the terminal by this and appropriately select a method for setting the dedicated numerology set accordingly will be described.

In order for the idle mode terminal to transmit its ID/service/slice information to, for example, a presence signal (or probing, discovery, beacon signal) to at least one or more base stations, the terminal first receives a synchronization signal of the base station and receives a reference time should match In addition, since the fixed resource location for transmitting the presence signal in advance according to the location of the synchronization signal hinders the free design of the system, a channel for transmitting and receiving the presence signal must be set in the minimum SI or additional SI. In the present invention, such a channel will be referred to as a UL presence channel (UPCH).

When the UL presence channel is configured, it may be a burden in terms of complexity and power consumption of the terminal for the terminal to transmit the UL presence signal in a short period. In response to this problem, the base station may configure a DL probing channel (DPCH) corresponding to the UL presence channel. The DL probing channel can also be configured in minimum SI or additional SI, and the DL probing signal transmits information or ID of at least one of UE, UE group, service, slice, and numerology.

The UL presence signal or the DL probing signal may be a contention-based signal that can be separated even if a part of a sequence or signal overlaps. Alternatively, a tone-based signal may be considered to indicate a large number of possible terminals and their services/slice. In particular, in the case of mapping the ID and information of the terminal to the multi-tone, it is possible to consider a method of encoding and transmitting with a different hash code for each terminal, and the base station receives it with a bloom filter.

As an example of a method of using a contention-based signal as the UL presence signal, the existing random access procedure may be used as it is. That is, following the Random Access Preamble of the UE and the Random Access Response of the BS, a service/slice related request may be transmitted to msg 3 of the UE.

As another example of a method of using a contention-based signal as the UL presence signal, it may be a modification of the existing random access signal. However, since the existing Random Access Preamble sends a sequence, it cannot contain a large amount of information. Also, it is difficult to send information that can be changed dynamically as a sequence. Therefore, when the base station configures the UPCH as the SI, it is necessary to send the mapping information between the sequence and the service/slice together. The UE may select a sequence corresponding to a service/slice that is being used or want to use and transmit it on the UPCH.

As another example of a method of using a contention-based signal as the UL presence signal, a new signal transmission method based on sparse coding may be used. According to the sparse coding, the base station can receive the overlapped signals transmitted by a plurality of terminals and distinguish the signals for each terminal. The terminal can send service/slice ID according to sparse coding, or compress and send the ID using the same method as hash code.

As another example of a method of using a contention-based signal as a UL presence signal or a DL probing signal, a tone-based signal and a hash code may be used.

The advantage of this method is that any type of data representing the terminal and information of the terminal can be encoded through a hash code. Also, since there is no false negative error and only false positive (or false alarm) errors occur, when a specific ID is transmitted, the probability of determining that it has not been transmitted is extremely low. Accordingly, if the base station stores the information regardless of the type of information, the base station can distinguish the signal from which terminal. If the UL presence signal is not a sequence, the RAP signal reception of the UE is required in order for the base station to calculate the TA of the UE. Also, if the same tone mapping is used, there is no interference between signals from different transmitters because signals only overlap. The DL probing signal may also be designed in the same structure as the UL presence signal. Therefore, a DL probing signal can be configured based on the terminal information stored by the MME or the service/slice control server. This feature is useful when using a DL probing signal in one or more base stations to replace the function of the paging signal.

52 is a flow chart showing an initial access procedure that can be considered according to the third embodiment of the present invention. After the UE detects the synchronization signal of the base station and acquires the SI message, when the PRACH (Physical Random Access Channel, physical layer random access channel) configuration is completed based on the information in the SI, the UE receives a paging message or data to be sent to the UL buffer When , a Random Access Preamble (RAP) may be transmitted. The UE may select and transmit an arbitrary RA-RNTI from among the RA preamble sets for each UE distance defined in the PRACH configuration in the SI. The base station is a RAR (Random Access Response) message that is divided into RA-RNTIs corresponding to the received RAP. RAP ID, Timing Advance value, Temporary C-RNTI (Temporary C-RNTI), resource allocation information for msg3 transmission of the terminal ( RB, MCS), etc. are transmitted. The UE transmits the ID (TMSI - Temporary Mobile Subscriber Identity or random value) and the connection establishment cause as msg3, that is, an RRC connection establishment message, according to the success of RAR reception. The base station transmits the ID of the terminal received in msg3 and the C-RNTI to be used in the connected state in order to notify the completion of connection establishment with an RRC connection setup message corresponding to msg3. An example of an initial access procedure considering a signal-I is a diagram.

According to FIG. 53 , the base station transmits UPCH and PRACH configuration information with minimum SI (or additional SI), and when the terminal receives the minimum SI, the UPCH and PRACH configuration can be completed. The UE transmits the UL presence signal determined according to the UPCH configuration to a specific UPCH resource. When the terminal notifies the base station of the UL presence in the case of a mobile-terminated (MT) call, the base station transmits a paging message in response according to the matching result. In this case, the paging message may include a numerology for RACH or a dedicated numerology set.

In the case of a mobile-oriented (MO) call, after notifying the base station of the UL presence, the terminal performs RAP and RAR procedures according to the default numerology set. If the base station sets a dedicated resource set with the RAR message, it performs transmission/reception operations with resources corresponding to the dedicated numerology set from msg3 and msg4. If the base station sets the dedicated numerology set with the RRC connection setup (msg4) message, the terminal performs the connected mode operation on the resource corresponding to the dedicated numerology set while switching the connected state. It is an example-I diagram of the initial access procedure considering the DL probing signal.

54 shows a procedure for replacing the function of paging with a DL probing signal. In the case of a synchronous network, the DL probing signal is transmitted and received by composing the same signal from one or a plurality of base stations. Accordingly, even if the network does not know the exact location of the terminal, one or more base stations in a certain area can simultaneously transmit a DL probing signal indicating the terminal to wake the terminal. The UE performs a random access procedure according to the matching result of the received DL probing signal. FIG. 55 is an example initial access procedure-I diagram in consideration of the UL presence signal and the DL probing signal according to the third embodiment of the present invention.

55 shows a procedure in which a paging signal is changed to a DL probing signal in the case in which paging is transmitted and received in FIG. 53 . The base station transmits a DL probing signal when matching for a UL presence signal from a specific terminal is successful. The UE matches the DL probing signal according to information corresponding to the UL presence signal, and if the result is successful, a random access procedure is performed. If the UL presence signal can match the service/slice/numerology information required by the UE, the random access procedure can be performed according to the dedicated numerology set. Here, it is assumed that the dedicated numerology set is transmitted as a minimum SI or an additional SI. FIG. 56 is an example-II diagram of an initial access procedure in consideration of a UL presence signal and a DL probing signal according to the third embodiment of the present invention.

In FIG. 56 , the base station first transmits a DL probing signal, and the terminal successfully matching the DL probing signal transmits a UL presence signal. Since the base station does not send the paging signal, the terminal does not need to monitor the paging signal with the default numerology set, and the random access procedure can be performed directly with the dedicated numerology set. According to another example, since the intention of interconnection between the base station and the terminal was identified through the DL probing and UL presence process, the ID and C-RNTI information of the terminal transmitted in msg4 are transmitted in msg2 without transmitting msg 3 and msg 4 can do. However, the RA-RNTI used for RAP transmission/reception must be derived based on information specifying the UE used in the DL probing and UL presence process. For example, the RA-RNTI may be determined based on a time/frequency location of a resource for transmitting DL probing or UL presence. Alternatively, if the state information in the connected state of the terminal is stored in the network, a pre-allocated RNTI may be used for a shortened random access procedure. Considered initial access procedure example-II diagram.

57 is a modification of the procedure based on the UL presence signal shown in FIG. 53 , and shows a case in which the base station transmits the additional SI in response to the UL presence signal of the terminal, rather than transmitting the minimum SI. Accordingly, the PRACH configuration or dedicated numerology set configuration information is included only in the additional SI. FIG. 64 is an example when the UPCH reuses the existing RA procedure according to the third embodiment of the present invention.

64 is an example when the UPCH reuses an existing RA procedure. The terminal acquires synchronization and SI from the base station and operates according to the UPCH and PRACH information set to the SI. When the RAP signal of the UE is received in the resource configured for the UPCH, the base station operates in a UPCH-related procedure different from the existing RA procedure. That is, it operates according to the sequence following RAP(msg1)-RAR(msg2)-UL presence(msg3). The UL presence ACK (msg4), which is a response of the base station to Msg3, may be transmitted only when necessary. Since the base station can check the service/slice information of the terminal by receiving the UL presence signal, in the case of an MT call, the numerology information can be set when sending a paging message to the terminal. Upon receiving the paging signal, if the UL synchronization is valid, the UE immediately transmits the RRC connection request to the set numerology, and the base station responds to this with RRC connection setup. In the case of an MO call, if the UL synchronization matched according to the Timing Advanced information of the previous msg2 is valid, the UE immediately transmits the RRC connection request to the configured Numerology, and the base station responds to this with RRC connection setup. In this procedure, the RRC message exchanged between the base station and the terminal after the numerology is set follows the set numerology.

65 is an example when the UPCH uses a modified RA procedure. The terminal acquires synchronization and SI from the base station and operates according to the UPCH and PRACH information set to the SI. The UE transmits the RAP (msg1) by selecting an appropriate sequence or/and UPCH resource according to a service/slice ID that can be expressed as a sequence or a combination of a sequence and an index of the UPCH resource. When the RAP signal of the UE is received in the resource configured for the UPCH, the base station operates in a UPCH-related procedure different from the existing RA procedure. That is, it operates according to the sequence leading to UL presence (msg1)-RAR (msg2). Since the base station can check the service/slice information of the terminal by receiving the UL presence signal, in the case of an MT call, the numerology information can be set when sending a paging message to the terminal. Upon receiving the paging signal, if the UL synchronization matched according to the Timing Advanced information of the previous msg2 is valid, the terminal immediately transmits the RRC connection request to the set Numerology, and the base station responds to this with RRC connection setup. In the case of an MO call, if the UL synchronization is valid, the UE immediately transmits the RRC connection request to the set Numerology, and the base station responds to this with RRC connection setup. In this procedure, the RRC messages exchanged between the base station and the terminal after setting the numerology follow the set numerology.

Various procedures for setting a dedicated numerology set shown in FIG. 51 and initial access procedures from FIGS. 52 to 57, 60, 61, 63, 64, and 65 may be combined and operated. Accordingly, combinations of the various options shown in FIG. 51 and various procedures illustrated in FIGS. 57, 60, 61, 63, 64, and 65 in FIGS. 52 are also included in the content of the present disclosure.

Here, a specific example of how to transmit the configuration of the physical layer of the UL presence signal or the DL probing signal, the ID of the terminal, and the service/slice ID will be disclosed. The core of the present invention is to map the terminal ID and service/slice ID information possessed by the upper layer of the terminal and the upper layer of the network, in particular, the MME or service/slice control server to multi-tone to transmit and receive the existence and request of the terminal. A server or base station of a network provides the terminal with dedicated numerology set information that can identify the service/slice ID and support the service/slice. Accordingly, details of how to transmit and receive ID information of a higher layer as a tone-based signal and how to specify a terminal that has transmitted a tone-based signal so that the base station can receive the dedicated numerology set information are disclosed.

First, the UL presence signal transmitted from the terminal to the base station or the DL probing signal transmitted from the base station to the terminal follows the same transmission/reception method. FIG. 4H shows a process of performing tone mapping based on the UE ID and service ID in the transmitter and a matching process of the UE ID and service ID information based on the tone information detected by the receiver. If it is not necessary to specify the terminal in the procedure, for example, when the network only wants to know the distribution of service requests, the terminal may be preset to transmit only the service/slice ID, or may be configured by the network or the base station. When configured by the network or the base station, the format of ID information to be used as input for tone mapping in Minimum SI or additional SI may be set. The transmitter (terminal) receives an output value that is a hashed code from a hash function using the ID as an input value. Based on the hash code, the UE determines which tone to send a signal (energy) to based on the UPCH information previously set in the minimum SI or additional SI. The UPCH configuration includes a structure of a tone resource divided by time/frequency and a method of assigning a logical index to a plurality of tones. There is often a time-first or frequency-first method, and in FIG. 4H, it is expressed according to the frequency-first method. That is, indexes are assigned in a direction that increases from low frequency tones, and if all frequency tones are indexed in one time unit, the same is applied in the next time unit and indexes are assigned starting from the lower frequency tones.

58 is an example of a method for transmitting and receiving a tone-based signal based on UE ID and service ID according to a third embodiment of the present invention.

58 shows a structure in which a total of 1280 tones from tone 0 to tone 1279 are indexed. The hash code obtained from the hash function can be recognized according to the general order of MSB (Most Significant Bit) or LSB (Least Significant Bit). The UE may sequentially allocate, for example, from tone index 0 of the UPCH to the MSB.

According to an embodiment, in order to improve reception performance, different scrambling codes or interleaving rules may be applied to each base station by changing the order to a scrambling or interleaving method instead of sequential tone mapping. If such additional order conversion for each base station or each terminal is possible at the cost of additional complexity, the base station may be utilized to determine the current residence base station of the terminal.

In an example to which sequential tone mapping is applied, the base station performs a procedure of mapping tone to code based on detected tone information. In this case, the tone information received by the base station may be a signal in which tone signals from one or a plurality of terminals are superimposed.

59 is an example of overlapping tone-based signals from a plurality of terminals according to the third embodiment of the present invention.

As shown in FIG. 59 , the overlapped signal may partially overlap the tone transmitted by the terminal 1 ( UE1 ) and the tone transmitted by the terminal 2 ( UE2 ). However, the base station or network server can match the ID of the terminal based on the output obtained by putting the ID information of the terminal as an input to the hash function while having the terminal ID information in advance, and check the existence of the terminal or the service request status of the terminal. This is because the overlapped signal does not affect tone mapping of other terminals. That is, this is because the receiver checks only a specific tone with a hash function to determine whether matching occurs. According to an embodiment, a method of minimizing the false alarm probability by using a bloom filter composed of a plurality of hash functions may be used.

According to an embodiment, the base station may allocate, in advance, tone mapping information for each ID or service ID of the terminal or tone mapping information for a combination of ID and service ID of the terminal to the terminal when accessing the network. When the terminal switches from the connected state to the idle state again, the terminal may transmit a UL presence signal or detect and recognize the DL probing signal of the base station if necessary according to the tone mapping information set by the base station.

Since the UE knows the period, resource location, etc. of the UPCH set as the Minimum SI or the additional SI, when UL data for a specific service/slice is accumulated in the buffer, the UL presence signal can be transmitted on the nearest UPCH. According to an embodiment, the UE transmits a UL presence signal at a period of a different multiple of the period of the UPCH according to the priority of the service/slice, or the UL presence at the UPCH location (separated by offset and period) separated from each other for each service/slice transmit a signal Alternatively, if the paging occasion is configured, the terminal may be configured by the base station or the network to transmit the UL presence signal on the k UPCH before the next paging occasion.

On the other hand, the base station or network that has received the UL presence signal and confirmed the existence of the terminal or the request of the terminal should inform the terminal of dedicated numerology set information suitable for the service/slice. The terminal transmits the UL presence signal as a tone-based signal, but the dedicated numerology set information of the base station must be transmitted as a message. (DL Control Information) or higher layer message should be transmitted. In addition, the terminal must also know information about the RNTI sent by the base station. Therefore, in the present disclosure, it will be described in detail whether the terminal can determine a new RNTI for receiving a message from the base station in the idle state. Since the new RNTI is used in the idle state, it will be referred to as I-RNTI.

The base station and the terminal should be able to determine the same RNTI without a random access procedure in a situation in which a connection is not established. According to various embodiments of the present disclosure, the terminal may transmit the UL presence signal as a tone-based signal. The UE ID mapped to the plurality of tones in the UPCH is too large information to be directly converted to the I-RNTI. Therefore, determining the I-RNTI of the terminal based on the hash code converted into a small size or the mapping information converted into tone contributes to reducing the complexity of the terminal.

For example, 1) I-RNTI is the result of performing a modular operation on the sum of the index values of mapped tones with the total size of the RNTI, or 2) dividing the tone area (space) into N sections, each After converting the bits column of the section to a partial value of RNTI (eg, hexadeimel value), the combined value is determined as I-RNTI, or 3) the value obtained by sequentially concatenating the index values of the mapped tones is converted into I-RNTI Alternatively, 4) a result value obtained by performing a modular operation on the total size of the RNTI on the sum of the interval values of the empty tones between the mapped tones may be determined as the I-RNTI.

In addition, various transformation methods based on a generally known algorithm may be considered. If the size of the hash code area is smaller than the size of the I-RNTI area, the converted value may be repeated so that the value is mapped to the total area of the I-RNTI. If the size of the hash code area is larger than the size of the I-RNTI area, the values of some areas may be omitted according to a rule to fit the size of the I-RNTI area.

The terminal generates an I-RNTI based on the tone information of the UL presence signal or DL probing signal according to the same I-RNTI generation rule as that of the network server or the base station as described above. Meanwhile, according to an embodiment, the base station may request and receive the ID and service/slice ID information of the terminal expected within the area from the MME or the service/slice control server in advance.

Alternatively, the base station may generate a hash code based on the received tone information and send it to the MME or service/slice control server to inquire about matching. 4J shows an embodiment in which the base station queries the MME or the service/slice server for the received tone mapping information or hash code information obtained through tone-to-code mapping, and the MME transmits paging to the terminal accordingly.

61 is an example in which the base station sends a matching indication to the MME according to the third embodiment of the present invention.

Figure 61 shows that the MME in advance, for example, provides a UE/service/slice ID or hash code for matching to a base station in the Tracking Area, and the base station performs matching on the UL presence signal based on the information provided so that the matching can be performed. do. If matching is successful, the base station needs to inform the MME about the details. At this time, the matching indication may be transmitted including the UE ID and service/slice ID information that has been successfully matched.

The UE may perform the following operation based on the I-RNTI determined from the tone-based signal. At this time, the base station transmits the corresponding dedicated numerology set information to the BCH-based additional SI based on the UL presence signals from multiple terminals, for example, if the number of terminals requesting a specific service is large; Or, for example, if the number of terminals requesting a specific service is small but the number of services is large, the corresponding dedicated numerology set information is transmitted to the SI-RNTI; Alternatively, if the number of terminals requesting a specific service is very small, the corresponding dedicated numerology set information is transmitted to the I-RNTI. Therefore, after transmitting the UL presence signal, the terminal searches for a signal of a base station distinguishable by I-RNTI while waiting within the I-RNTI reception window set as Minimum SI or additional SI.

In the resource to which the base station is to transmit the BCH, the terminal must perform the BCH reception operation regardless of the reception window. This means that the UE may not perform the I-RNTI reception operation for BCH reception depending on implementation. On the other hand, in the resource for the base station to transmit SI-RNTI (obtained by SI scheduling), the UE must perform both the SI-RNTI reception operation and the I-RNTI reception operation separately from the reception window. Depending on the capability of the terminal, it may be difficult for a certain terminal to simultaneously perform an SI-RNTI reception operation and an I-RNTI reception operation. Such a terminal does not receive the SI-RNTI within the I-RNTI reception window, and receives the SI-RNTI when the I-RNTI reception window expires.

The ID of the terminal may be various IDs (IMSI, GUTI, S-TMSI, IP/PDN address UE S1AP ID, UE X2AP ID) used in the network/base station, or it may be a subscriber ID determined for each service/application/slice. 62 is a diagram showing the configuration of a terminal device according to a third embodiment of the present invention.

62 is a diagram illustrating a configuration of a terminal device according to a third embodiment of the present disclosure.

The terminal device may include a transceiver for transmitting and receiving signals with other terminals, and a control unit for controlling all operations of the terminal device. It may be understood that all operations for synchronization support described above in the present disclosure are performed by the controller. However, the controller and the transceiver do not necessarily have to be implemented as separate devices, and may be implemented as a single component in the form of a single chip.

It should be noted that the configuration diagram of the terminal illustrated in FIGS. 51 to 57 , an example of a control/data signal transmission method, an example of an operation procedure of the terminal, and configuration diagrams of a terminal device are not intended to limit the scope of the present disclosure. shall. That is, all components, entities, or steps of operation described in FIGS. 51 to 57 should not be construed as essential components for implementation of the disclosure, and even including only some components, the scope does not impair the essence of the disclosure. can be implemented in

The operations of the base station or the terminal described above can be realized by providing a memory device storing the corresponding program code in an arbitrary component in the base station or the terminal device. That is, the control unit of the base station or the terminal device may execute the above-described operations by reading and executing the program code stored in the memory device by a processor or a central processing unit (CPU).

The various components and modules of the entity, base station or terminal device described in this specification include a hardware circuit, for example, a complementary metal oxide semiconductor-based logic circuit, and firmware. and software and/or hardware circuitry, such as a combination of hardware and firmware and/or software embedded in a machine-readable medium. As an example, various electrical structures and methods may be implemented using electrical circuits such as transistors, logic gates, and application-specific semiconductors.

Claims (24)

A method for transmitting uplink data of a terminal in a wireless communication system, the method comprising:
When the terminal is in a radio resource control (RRC) inactive state, transmitting a random access (RA) preamble to the base station;
receiving an RA response message corresponding to the RA preamble from the base station;
Transmitting an RRC resume request message including a terminal identifier (identity), resume cause information (information) and an authentication token (authentication token) to the base station; and
Receiving an RRC message for terminating an RRC connection including prioritization information from the base station; including,
The RRC message for stopping the RRC connection includes a terminal identifier, a radio access network (RAN), notification area information, and RAN periodic notification timer information. how to do it with According to claim 1,
The RRC message for stopping the RRC connection further includes redirect carrier frequency information. According to claim 1,
When the state of the terminal is switched to RRC idle, the RRC message for stopping the RRC connection further includes wait timer information. delete delete delete delete A method for receiving uplink data by a base station in a wireless communication system, the method comprising:
When the terminal is in a radio resource control (RRC) inactive state, receiving a random access (RA) preamble from the terminal;
transmitting an RA response message corresponding to the RA preamble from the terminal;
Receiving an RRC resume request message including a terminal identifier (identity), resume cause information (information) and an authentication token (authentication token) from the terminal; and
transmitting an RRC message for terminating an RRC connection including priority release information; including,
The RRC message for stopping the RRC connection includes a terminal identifier, a radio access network (RAN), notification area information, and RAN periodic notification timer information. how to do it with 9. The method of claim 8,
The RRC message for stopping the RRC connection further includes redirect carrier frequency information. 9. The method of claim 8,
When the state of the terminal is switched to RRC idle, the RRC message for stopping the RRC connection further includes wait timer information. delete delete delete delete A terminal for transmitting uplink data in a wireless communication system, comprising:
a transceiver for transmitting and receiving a signal; and
and a control unit connected to the transceiver to control the transceiver,
The control unit is
When the terminal is in a radio resource control (RRC) inactive state, a random access (RA) preamble is transmitted to the base station, and an RA response message corresponding to the RA preamble is transmitted. Controls the transceiver to transmit an RRC resume request message including a terminal identifier (identity), resume cause information and an authentication token (authentication token) to the base station, which is received from the base station, and priority is released from the base station characterized in that the transceiver is controlled to receive an RRC message for terminating an RRC connection including information (deprioritization information),
The RRC message for stopping the RRC connection further includes a terminal identifier, a radio access network (RAN), notification area information, and RAN periodic notification timer information. A terminal, characterized in that. The terminal of claim 15, wherein the RRC message for stopping the RRC connection further includes redirect carrier frequency information. The terminal of claim 15, wherein when the state of the terminal is switched to RRC idle, the RRC message for stopping the RRC connection further includes wait timer information. delete delete A base station for receiving uplink data in a wireless communication system, comprising:
a transceiver for transmitting and receiving a signal; and
and a control unit connected to the transceiver to control the transceiver,
The control unit is
When the terminal is in a radio resource control (RRC) inactive state, a random access (RA) preamble is received from the terminal, and an RA response message corresponding to the RA preamble is transmitted. Controls the transceiver to receive an RRC resume request message from the terminal, which is transmitted from the terminal, and includes a terminal identifier (identity), resume cause information (information) and an authentication token (authentication token),
The RRC message for stopping the RRC connection further includes a terminal identifier, a radio access network (RAN), notification area information, and RAN periodic notification timer information. base station. The base station of claim 20, wherein the RRC message for stopping the RRC connection further includes redirect carrier frequency information. 21. The base station of claim 20, wherein when the state of the terminal is changed to RRC idle, the RRC message for stopping the RRC connection further includes wait timer information. delete delete

Images