Method and apparatus for performing communication in wireless communication system

Abstract

The present disclosure relates to a method and apparatus for a terminal to perform communication in a wireless communication system. A terminal according to one embodiment of the present disclosure receives danger area information from a base station, and if the terminal is identified as being located in a danger area based on the danger area information, acquires pedestrian-to-vehicle (P2V) data and can transmit the P2V data through resources allocated to the terminal from the base station.

Description

Technology Field

[0001] The present disclosure relates to a wireless communication system, and more specifically, to a method and apparatus for performing communication between a vehicle terminal and a pedestrian terminal in a wireless communication system. Additionally, the present disclosure relates to a mobile communication system, and relates to a method for controlling an RRC connection between a terminal and a base station according to the wireless bearer settings of the terminal. Background Technology

[0002] Efforts are being made to develop improved 5G communication systems (NR, New Radio) to meet the increasing demand for wireless data traffic following the commercialization of 4G communication systems. To achieve high data transmission rates, 5G communication systems have been designed to enable resources in the mmWave band (e.g., the 28 GHz frequency band). To mitigate path loss and increase the transmission distance of radio waves in the mmWave band, beamforming, massive array multiple input / output (massive MIMO), full-dimensional multiple input / output (Full Dimensional MIMO: FD-MIMO), array antenna, analog beamforming, and large-scale antenna technologies are being discussed for 5G communication systems. In addition, unlike LTE, 5G communication systems utilize various subcarrier spacings, including 15 kHz, 30 kHz, 60 kHz, and 120 kHz; the Physical Control Channel uses Polar Coding, and the Physical Data Channel uses Low Density Parity Check (LDPC). Furthermore, for uplink transmission, waveforms such as DFT-S-OFDM as well as CP-OFDM are used. While LTE utilizes Hybrid ARQ (HARQ) retransmission in the Transport Block (TB) unit, 5G can additionally utilize Code Block Group (CBG)-based HARQ retransmission, which bundles multiple Code Blocks (CBs).

[0003] In addition, to improve the network of the system, the development of technologies such as advanced small cell, advanced small cell, cloud radio access network (cloud RAN), ultra-dense network, Device to Device communication (D2D), wireless backhaul, Vehicle to Everything (V2X) network, cooperative communication, Coordinated Multi-Points (CoMP), and interference cancellation is being carried out in 5G communication systems.

[0004] Meanwhile, the Internet is evolving from a human-centric network where humans generate and consume information into an IoT (Internet of Things) network that processes information by exchanging it among distributed components, such as objects. IoE (Internet of Everything) technology, which combines IoT with Big Data processing technologies through connections with cloud servers, is also emerging. To implement IoT, technological elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required; consequently, technologies such as sensor networks, Machine-to-Machine (M2M) communication, and Machine-Type Communication (MTC) are currently being researched to facilitate the connection of objects. In an IoT environment, intelligent IT services that create new value for human life by collecting and analyzing data generated from connected objects can be provided. Through the convergence and integration of existing IT technologies with various industries, IoT can be applied to fields such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart home appliances, and advanced medical services.

[0005] Accordingly, various attempts are being made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, Machine-to-Machine (M2M) communication, and Machine Type Communication (MTC) are being implemented using 5G communication techniques such as beamforming, MIMO, and array antennas. The application of cloud radio access networks (cloud RAN) as the big data processing technology described earlier can also be considered an example of the convergence of 3eG and IoT technologies. As such, multiple services can be provided to users within a communication system, and to provide these multiple services to users, methods and devices utilizing such methods are required to provide each service within the same time interval according to its characteristics. Various services provided by the aforementioned 5G communication system are being researched, one of which is a service that satisfies the requirements for low latency and high reliability. This is called Ultra Reliability and Low Latency Communication (URLC). Another example is V2X (vehicle-to-everything), a general term referring to all forms of communication applicable to vehicles—specifically, means of transportation located on the road—and signifies specific communication technologies for realizing 'Connected Vehicles' or 'Networked Vehicles'. V2X networking is broadly divided into three categories: vehicle-to-infrastructure (V2I), vehicle-to-vehicle (V2V), and vehicle-to-pedestrian (V2P) communication.

[0006] As a result of the aforementioned developments and advancements in wireless communication systems, it has become possible to provide various services, and thus measures are required to facilitate the smooth provision of these services. The problem to be solved

[0007] One embodiment of the present disclosure aims to provide a method for efficiently performing communication between a pedestrian terminal and a vehicle terminal in a wireless communication system. Additionally, another embodiment of the present disclosure aims to provide a method for a vehicle terminal in a wireless communication system to efficiently perform paging according to service-specific characteristics.

[0008] According to one embodiment of the present disclosure, when only SRB1 and DRB are established (i.e., SRB2 is not established) and security is enabled in a terminal in RRC connection mode, a method is proposed in which, upon receiving an RRC connection reconfiguration message from a base station, if a reconfiguration failure occurs, the terminal does not immediately transition to RRC idle mode but performs an RRC connection re-establishment procedure.

[0009] In addition, according to one embodiment of the present disclosure, when only SRB1 and DRB are established and security is enabled in a terminal in RRC connection mode, and when an RRC connection reconfiguration message received from a base station includes ReconfigurationWithSync (an indicator related to performing a handover), a method is proposed for the terminal to perform a normal RRC connection reconfiguration procedure with the base station.

[0010] In addition, according to one embodiment of the present disclosure, when only SRB1 and DRB are established in a terminal in RRC connection mode, the base station may instruct the terminal to transition to an inactive mode by sending an RRC connection disconnection message containing suspendConfig.

[0011] In addition, according to one embodiment of the present disclosure, even when only SRB1 and DRB are established, the terminal may be in an RRC disabled mode and may perform a normal connection resumption (RRC connectionresume) procedure.

[0012] In addition, according to one embodiment of the present disclosure, if an integrity check failure occurs when only SRB1 and DRB are established in a terminal in RRC connection mode, an RRC connection re-establishment procedure can be performed. If only SRB1 is established in a terminal in RRC connection mode, MDT-related information can be transmitted to a base station through SRB1. means of solving the problem

[0013] A method for a terminal to perform communication in a wireless communication system according to one embodiment may include: receiving danger area information from a base station; acquiring pedestrian-to-vehicle (P2V) data when the terminal is identified as being located in a danger area based on the danger area information; and transmitting the P2V data through a resource allocated to the terminal from the base station.

[0014] In a method for a terminal to perform communication in a wireless communication system according to one embodiment, the danger area information is information indicating whether the terminal is located in a danger area.

[0015] In a method for a terminal to perform communication in a wireless communication system according to one embodiment, the danger area information includes location information of a danger area, and may further include the step of identifying whether the terminal is located in a danger area by comparing the location information of the danger area with the location information of the terminal.

[0016] In a method for a terminal to perform communication in a wireless communication system according to one embodiment, the danger area information includes SSB (synchronization signal block) identification information corresponding to the danger area, and may further include the step of performing an SSB measurement; the step of identifying an SSB in which the strength of a received signal exceeds a threshold value based on the SSB measurement; and the step of comparing the identified SSB with the SSB identification information corresponding to the danger area to identify whether the terminal is located in the danger area.

[0017] In a method for a terminal to perform communication in a wireless communication system according to one embodiment, the step of receiving danger area information may be to receive the danger area information through at least one of system information, a paging signal, or a short message.

[0018] In a method for a terminal to perform communication in a wireless communication system according to one embodiment, the step of receiving danger area information may include: a step of obtaining SSB identification information corresponding to the danger area from system information or a paging signal; and a step of receiving a short message indicating that the terminal is located in the danger area in an area covered by the SSB corresponding to the danger area.

[0019] A method for a base station to perform communication in a wireless communication system according to one embodiment may include: transmitting danger area information; receiving a request for P2V transmission resource allocation from a terminal identified as being located in a danger area based on the danger area information; and allocating a P2V transmission resource to the terminal based on the request for P2V transmission resource allocation.

[0020] In a method for a terminal to perform communication in a wireless communication system according to one embodiment, the step of transmitting danger area information may transmit the danger area information to a cover area of ​​an SSB corresponding to the danger area through either a paging signal or a short message.

[0021] A terminal performing communication in a wireless communication system according to one embodiment includes a transceiver; and a processor connected to the transceiver. The processor controls the transceiver to receive danger area information from a base station, and if the terminal is identified as being located in a danger area based on the danger area information, acquires P2V (pedestrian-to-vehicle) data and can control the transceiver to transmit P2V data through resources allocated to the terminal from the base station.

[0022] A base station performing communication in a wireless communication system according to one embodiment includes a transceiver; and a processor connected to the transceiver. The processor transmits danger area information and controls the transceiver to receive a P2V transmission resource allocation request from a terminal identified as being located in a danger area based on the danger area information, and can allocate a P2V transmission resource to the terminal based on the P2V transmission resource allocation request. Effects of the invention

[0023] According to the present disclosure, a vehicle terminal or a pedestrian terminal in a wireless communication system can perform communication while using power efficiently.

[0024] According to the present disclosure, even if RRC reconfiguration fails, if only SRB1 and DRB are established in the RRC-connected terminal and security is enabled, signaling overhead can be reduced and a fast connection can be performed through the RRC reconfiguration procedure. Furthermore, according to the present disclosure, if only SRB1 and DRB are established in the RRC-connected terminal and security is enabled, if the RRC connection reconfiguration message includes an indicator related to performing a handover, data transmission and reception with the target cell can be performed by maintaining the RRC connection mode without transitioning to the RRC idle mode.

[0025] Furthermore, according to the present disclosure, even when only SRB1 and DRB are established in a terminal in an RRC connection state, the terminal can be made to transition to an inactive mode, thereby reducing signaling overhead and enabling fast data transmission and reception through an RRC connection re-establishment procedure. Additionally, according to the present disclosure, when an integrity check failure occurs in a terminal in an RRC connection mode where only SRB1 and DRB are established, the terminal can maintain an RRC connection with the base station because an RRC connection re-establishment procedure can be performed.

[0026] Additionally, according to the present disclosure, a terminal in RRC connection mode with only SRB1 established can send MDT-related information to a base station via SRB1. That is, since the terminal can send MDT-related information to the base station without establishing SRB2 or performing a new RRC connection reset procedure, the base station can receive MDT-related information more quickly. Brief explanation of the drawing

[0027] FIG. 1a is a drawing illustrating the structure of an LTE system according to one embodiment of the present disclosure. FIG. 1b is a diagram illustrating a wireless protocol structure in an LTE system according to one embodiment of the present disclosure. FIG. 1c is a drawing illustrating the structure of a next-generation mobile communication system according to one embodiment of the present disclosure. FIG. 1d is a diagram showing the wireless protocol structure of a next-generation mobile communication system according to one embodiment of the present disclosure. FIG. 1e is a diagram illustrating V2X communication within a mobile communication system according to one embodiment of the present disclosure. FIG. 1f is a diagram illustrating a procedure for a terminal to select a random resource when a base station according to one embodiment of the present disclosure allocates resources to a terminal using a scheduled resource allocation method. FIG. 1g is a diagram illustrating a procedure for a terminal to select a random resource when a base station according to one embodiment of the present disclosure allocates resources to a terminal using a UE autonomous resource allocation method. FIG. 1h is a diagram illustrating the partial sensing operation of a terminal in V2P communication. FIG. 1i is a diagram illustrating a method for a pedestrian terminal to perform transmission and reception of V2P signals with the help of a base station / vehicle terminal to reduce power consumption of the pedestrian terminal in V2P communication according to one embodiment of the present disclosure. FIG. 1j is a diagram illustrating a method for a pedestrian terminal to perform transmission and reception of V2P signals with the help of a base station / vehicle terminal to reduce power consumption of the pedestrian terminal in V2P communication according to one embodiment of the present disclosure. FIG. 1k is a diagram illustrating a method in which a pedestrian terminal performs transmission and reception of V2P signals with the help of a base station / vehicle terminal to reduce power consumption of the pedestrian terminal in V2P communication according to one embodiment of the present disclosure. FIG. 11 is a diagram illustrating a method for a pedestrian mobile terminal to perform transmission and reception of V2P signals with the help of a base station / vehicle terminal to reduce power consumption of the pedestrian terminal in V2P communication according to one embodiment of the present disclosure. FIG. 1m is a drawing for explaining a method in which a pedestrian mobile terminal performs transmission and reception of V2P signals with the help of a base station / vehicle terminal to reduce power consumption of the pedestrian terminal in V2P communication according to one embodiment of the present disclosure. FIG. 2e is a conceptual diagram illustrating a typical or vertical paging point of an RRC idle mode (RRC Idle mode) or RRC inactive mode terminal in a next-generation mobile communication system according to one embodiment of the present disclosure. FIG. 2f is a diagram illustrating a method for a terminal in RRC Idle mode or RRC Inactive mode to monitor a general paging signal or a vertical paging signal in a next-generation mobile communication system according to one embodiment of the present disclosure. FIG. 2g is a diagram illustrating a method for receiving DCI to receive a general paging signal or a vertical paging signal and a method for interpreting the paging signal in an RRC idle mode or RRC inactive mode terminal in a next-generation mobile communication system according to one embodiment of the present disclosure. FIG. 2h is a block diagram illustrating the structure of a terminal according to one embodiment of the present disclosure. FIG. 2i is a block diagram illustrating the structure of a base station according to one embodiment of the present disclosure. FIG. 3e shows that, according to one embodiment of the present disclosure, a terminal establishes an RRC connection with a base station (RRC This is a diagram illustrating the procedure for switching from RRC idle mode to RRC connected mode by performing the connection establishment procedure, and the procedure for the base station and the terminal to perform the RRC reconfiguration procedure. FIG. 3f is a diagram illustrating, according to one embodiment of the present disclosure, a procedure in which a terminal performs an RRC connection establishment procedure with a base station to switch from an RRC idle mode to an RRC connected mode, and a procedure in which a base station and a terminal perform an RRC reconfiguration procedure. FIG. 3g is a flowchart of the operation of a terminal according to the condition in which a wireless bearer setting is instructed when a terminal in RRC connection mode (RRC_CONNECTED) receives an RRCReconfiguration message from a base station in accordance with one embodiment of the present disclosure. FIG. 3h is a flowchart of the operation of a terminal according to a pre-configured wireless bearer setting when a terminal in RRC connection mode (RRC_CONNECTED) receives an RRCRelease message containing suspend configuration information (suspendConfig) from a base station according to one embodiment of the present disclosure. FIG. 3i is a flowchart of the operation of a terminal according to a set radio bearer when a terminal in RRC connection mode (RRC_CONNECTED) detects a radio link failure (hereinafter RLF) according to one embodiment of the present disclosure. FIG. 3j illustrates the structure of a terminal according to one embodiment of the present disclosure. FIG. 3k illustrates the structure of a base station in one embodiment of the present disclosure. FIG. 31 is a diagram showing an NR-DC structure according to one embodiment of the present invention. FIG. 3m is a drawing showing an NR-DC structure according to one embodiment of the present invention. FIG. 3n shows legacy network communication and 5G network according to an embodiment of the present invention. This is a block diagram of an electronic device to support communication. Specific details for implementing the invention

[0028] The operating principles of the present disclosure will be described in detail below with reference to the attached drawings. In describing the present invention below, specific descriptions of related known functions or configurations will be omitted if it is determined that such detailed descriptions would unnecessarily obscure the essence of the present disclosure. Furthermore, the terms described below are defined considering their functions in the present invention, and these may vary depending on the intentions or conventions of the user or operator. Therefore, their definitions should be based on the content throughout this specification.

[0029] At this point, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment may create means for performing the functions described in the flow diagram block(s). Since these computer program instructions may also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the function in a specific way, the instructions stored in computer-available or computer-readable memory may also produce a manufactured item containing instruction means for performing the function described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).

[0030] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specific logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For example, two blocks described in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order according to their corresponding functions.

[0031] In this embodiment, the term "part" refers to a software or hardware component such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit), and the "part" performs certain roles. However, the meaning of "part" is not limited to software or hardware. The "part" may be configured to reside in an addressable storage medium or configured to run one or more processors. Thus, as an example, the "part" includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and "parts" may be combined into a smaller number of components and "parts" or further separated into additional components and "parts." In addition, the components and 'parts' may be implemented to utilize one or more CPUs within the device or secure multimedia card. Also, in the embodiments, 'parts' may include one or more processors.

[0032] In this disclosure, the Downlink (DL) refers to the wireless transmission path of a signal transmitted by a base station to a terminal, and the Uplink (UL) refers to the wireless transmission path of a signal transmitted by a terminal to a base station. Furthermore, while LTE or LTE-A systems may be described below as examples, embodiments of this disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included in systems to which embodiments of this disclosure can be applied, and the 5G below may be a concept that includes existing LTE, LTE-A, and other similar services. Additionally, this disclosure may be applied to other communication systems with some modifications made at the discretion of a person with skilled technical knowledge, provided that it does not deviate significantly from the scope of this disclosure.

[0033] Terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc., are examples provided for the convenience of explanation. Accordingly, the present invention is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.

[0034] For convenience of explanation below, the present invention uses terms and names defined in the 3GPP LTE (3rd Generation Partnership Project Long Term Evolution) standard. However, the present invention is not limited by these terms and names and can be applied in the same way to systems conforming to other standards.

[0035] Hereinafter, the base station is an entity that performs resource allocation for terminals and may be at least one of a gNode B, eNode B, Node B, BS (Base Station), wireless access unit, base station controller, or a node on a network. The terminal may include a UE (User Equipment), MS (Mobile Station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions. Of course, it is not limited to the above examples.

[0036] In particular, the present disclosure is applicable to 3GPP NR (5th generation mobile communication standard). Furthermore, the present disclosure is applicable to intelligent services (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail, security and safety-related services, etc.) based on 5G communication technology and IoT-related technology. In the present invention, eNB may be used interchangeably with gNB for convenience of explanation. That is, a base station described as eNB may represent a gNB. Additionally, the term terminal may refer to mobile phones, NB-IoT devices, sensors, as well as other wireless communication devices.

[0037] Wireless communication systems are evolving from providing early voice-oriented services to broadband wireless communication systems that provide high-speed, high-quality packet data services, such as communication standards like 3GPP’s HSPA (High Speed ​​Packet Access), LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2’s HRPD (High Rate Packet Data), UMB (Ultra Mobile Broadband), and IEEE’s 802.16e.

[0038] As a representative example of a broadband wireless communication system, the LTE system employs the Orthogonal Frequency Division Multiplexing (OFDM) method for the downlink (DL) and the Single Carrier Frequency Division Multiple Access (SC-FDMA) method for the uplink (UL). The uplink refers to a wireless link through which a terminal (User Equipment; UE or Mobile Station; MS) transmits data or control signals to a base station (eNode B or BS; Base Station), and the downlink refers to a wireless link through which a base station transmits data or control signals to a terminal. The above multiple access method distinguishes the data or control information of each user by allocating and operating time-frequency resources to be transmitted for each user so that they do not overlap, that is, so that orthogonality is established.

[0039] As a future communication system following LTE, that is, a 5G communication system, it must be able to freely reflect the diverse requirements of users and service providers, and therefore, services that satisfy various requirements simultaneously must be supported. Services being considered for the 5G communication system include Enhanced Mobile BroadBand (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC).

[0040] According to one embodiment, eMBB may aim to provide a data transmission speed that is higher than the data transmission speed supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must be able to provide a peak data rate of 20 Gbps in the downlink and a peak data rate of 10 Gbps in the uplink from the perspective of a single base station. In addition, the 5G communication system may need to provide a user-perceived data rate while simultaneously providing the peak data rate. To satisfy these requirements, the 5G communication system may require improvements in various transmission and reception technologies, including enhanced Multi-Input Multi-Output (MIMO) transmission technology. Furthermore, while current LTE transmits signals using a maximum transmission bandwidth of 20 MHz in the 2 GHz band, the 5G communication system can satisfy the data transmission speed required by the 5G communication system by using a frequency bandwidth wider than 20 MHz in frequency bands of 3 to 6 GHz or above 6 GHz.

[0041] Simultaneously, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide IoT services, mMTC may require support for a large number of terminal connections within a cell, improved terminal coverage, enhanced battery life, and reduced terminal costs. Since IoT devices are attached to various sensors and equipment to provide communication functions, the system must be able to support a large number of terminals within a cell (e.g., 1,000,000 terminals / km²). Furthermore, due to the nature of the service, terminals supporting mMTC are likely to be located in dead zones not covered by cells, such as building basements; therefore, wider coverage may be required compared to other services provided by 5G communication systems. Terminals supporting mMTC must consist of low-cost devices, and since it is difficult to frequently replace terminal batteries, a very long battery life of 10 to 15 years may be required.

[0042] Finally, URLLC is a mission-critical cellular-based wireless communication service that can be used for services such as remote control of robots or machinery, industrial automation, unmanned aerial vehicles, remote health care, and emergency alerts. Therefore, the communication provided by URLLC may need to offer very low latency and very high reliability. For example, services supporting URLLC must satisfy an air interface latency of less than 0.5 milliseconds and may simultaneously require a packet error rate of 10⁻⁵ or less. Consequently, for services supporting URLLC, 5G systems must provide a Transmit Time Interval (TTI) smaller than other services, and design considerations may be required to allocate wide resources in the frequency band to ensure the reliability of the communication link.

[0043] The three services considered in the aforementioned 5G communication system, namely eMBB, URLLC, and mMTC, can be multiplexed and transmitted within a single system. In this case, different transmission and reception techniques and parameters may be used between the services to satisfy the different requirements of each service. However, the aforementioned mMTC, URLLC, and eMBB are merely examples of different service types, and the service types to which the present disclosure applies are not limited to the examples mentioned above.

[0044] In addition, although embodiments of the present invention are described below using LTE, LTE-A, LTE Pro, or 5G (or NR, next-generation mobile communication) systems as examples, embodiments of the present invention may be applied to other communication systems having similar technical backgrounds or channel types. Furthermore, embodiments of the present invention may be applied to other communication systems with some modifications made at the discretion of a person with skilled technical knowledge, without significantly departing from the scope of the present invention.

[0045] In describing the present disclosure below, if it is determined that a detailed description of related known functions or configurations could unnecessarily obscure the essence of the present disclosure, such detailed description will be omitted. An embodiment of the present disclosure will be described below with reference to the attached drawings.

[0046] FIG. 1a is a drawing illustrating the structure of an LTE system according to one embodiment of the present disclosure.

[0047] Referring to FIG. 1a, the wireless access network of an LTE system may be composed of a next-generation base station (Evolved Node B, hereinafter ENB, Node B or base station) (1a-05, 1a-10, 1a-15, 1a-20), a Mobility Management Entity (MME) (1a-25), and an S-GW (1a-30, Serving-Gateway). A user terminal (User Equipment, hereinafter UE or terminal) (1a-35) may connect to an external network through the ENB (1a-05 to 1a-20) and the S-GW (1a-30).

[0048] In FIG. 1a, the ENB (1a-05 to 1a-20) can correspond to the existing Node B of the UMTS (Universal Mobile Telecommunication System) system. The ENB can be connected to the UE (1a-35) via a wireless channel and can perform more complex roles than the existing Node B. In an LTE system, all user traffic, including real-time services such as VoIP (Voice over IP) via the Internet Protocol, can be serviced through a shared channel. Therefore, a device is required to collect status information such as the buffer status, available transmission power status, and channel status of the UEs to perform scheduling, and this can be handled by the ENB (1a-05 to 1a-20).

[0049] A single ENB can typically control multiple cells. For example, to achieve a transmission speed of 100 Mbps, an LTE system can use Orthogonal Frequency Division Multiplexing (OFDM) as a radio access technology in a 20 MHz bandwidth. Additionally, it can apply Adaptive Modulation & Coding (AMC) to determine the modulation scheme and channel coding rate according to the terminal's channel conditions.

[0050] The S-GW (1a-30) is a device that provides a data bearer and can create or remove data bearers under the control of the MME (1a-25). The MME is a device responsible for various control functions as well as mobility management functions for terminals and can be connected to multiple base stations.

[0051] FIG. 1b is a diagram illustrating a wireless protocol structure in an LTE system according to one embodiment of the present disclosure.

[0052] Referring to FIG. 1b, the wireless protocol of the LTE system may consist of a Packet Data Convergence Protocol (PDCP) (1b-05, 1b-40), Radio Link Control (RLC) (1b-10, 1b-35), and Medium Access Control (MAC) (1b-15, 1b-30) at the terminal and the ENB, respectively. PDCP (1b-05, 1b-40) may be responsible for operations such as IP header compression / decompression. The main functions of PDCP (1b-05, 1b-40) can be summarized as follows.

[0053] - Header compression and decompression: ROHC only

[0054] - User data transfer function (Transfer of user data)

[0055] - In-sequence delivery of upper layer PDUs at PDCP re-establishment procedure for RLC AM

[0056] - Split bearers in DC (only support for RLC AM): PDCP PDU routing for transmission and PDCP PDU reordering for reception

[0057] Duplicate detection of lower layer SDUs at PDCP re-establishment procedure for RLC AM

[0058] - Retransmission of PDCP SDUs at handover for split bearers in DC and, for split bearers in DC, of ​​PDCP PDUs at PDCP data-recovery procedure for RLC AM

[0059] - Encryption and decryption functions (Ciphering and deciphering)

[0060] - Timer-based SDU discard in uplink.

[0061] Radio Link Control (RLC) (1b-10, 1b-35) can perform ARQ operations, etc., by reconfiguring PDCP Packet Data Units (PDUs) to an appropriate size. The main functions of RLC (1b-05, 1b-40) can be summarized as follows.

[0062] - Data transfer function of upper layer PDUS (Transfer of upper layer PDUs)

[0063] - Error Correction through ARQ (only for AM data transfer)

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

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

[0066] - Reordering of RLC data PDUs (only for UM and AM data transfer)

[0067] - Duplicate detection (only for UM and AM data transfer)

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

[0069] - RLC SDU discard (only for UM and AM data transfer)

[0070] RLC re-establishment function

[0071] MAC (1b-15, 1b-30) is connected to multiple RLC layer devices configured in a terminal and can perform operations of multiplexing RLC PDUs into MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. The main functions of MAC (1b-15, 1b-30) can be summarized as follows.

[0072] - Mapping function between logical channels and transport channels

[0073] - Multiplexing and demultiplexing of MAC SDUs belonging to one or different logical channels in transport blocks (TB) delivered to / from the physical layer on transport channels

[0074] - Scheduling information reporting function

[0075] - Error correction through HARQ

[0076] - Priority handling between logical channels of one UE

[0077] - Priority handling between UEs by means of dynamic scheduling

[0078] - MBMS service identification function

[0079] - Transport format selection function

[0080] - Padding

[0081] The physical layer (1b-20, 1b-25) can perform the operation of channel coding and modulating upper layer data, creating OFDM symbols and transmitting them to the wireless channel, or demodulating OFDM symbols received through the wireless channel and channel decoding them to transmit them to the upper layer.

[0082] FIG. 1c is a drawing illustrating the structure of a next-generation mobile communication system according to one embodiment of the present disclosure.

[0083] Referring to FIG. 1c, the wireless access network of a next-generation mobile communication system (hereinafter NR or 5G) may be composed of a next-generation base station (New Radio Node B, hereinafter NR gNB or NR base station) (1c-10) and a next-generation wireless core network (New Radio Core Network, NR CN) (1c-05). A next-generation wireless user terminal (New Radio User Equipment, NR UE or terminal) (1c-15) can connect to an external network through the NR gNB (1c-10) and the NR CN (1c-05).

[0084] In FIG. 1c, the NR gNB (1c-10) can correspond to the eNB (Evolved Node B) of the existing LTE system. The NR gNB (1c-10) is connected to the NR UE (1c-15) via a wireless channel and can provide superior service compared to the existing Node B. In the next-generation mobile communication system, all user traffic can be serviced through a shared channel. Therefore, a device is required to collect status information such as the buffer status, available transmission power status, and channel status of the UEs to perform scheduling, and this can be handled by the NR NB (1c-10). A single NR gNB (1c-10) can control multiple cells. In the next-generation mobile communication system, a bandwidth exceeding the current maximum bandwidth can be applied to achieve ultra-high-speed data transmission compared to current LTE. Additionally, beamforming technology can be incorporated using Orthogonal Frequency Division Multiplexing (OFDM) wireless access technology. In addition, an Adaptive Modulation & Coding (hereinafter referred to as AMC) scheme that determines the modulation scheme and channel coding rate according to the channel conditions of the terminal may be applied.

[0085] The NR CN (1c-05) can perform functions such as mobility support, bearer configuration, and QoS configuration. The NR CN (1c-05) is a device responsible for various control functions as well as mobility management functions for terminals, and can be connected to multiple base stations. In addition, the next-generation mobile communication system can be interoperable with existing LTE systems, and the NR CN (1c-05) can be connected to the MME (1c-25) via a network interface. The MME (1c-25) can be connected to the existing base station eNB (1c-30).

[0086] FIGS. 31 and FIGS. 3m illustrate an example of configuring an NR-DC. As illustrated, the wireless access network of a next-generation mobile communication system (new radio, NR) can be composed of a next-generation base station (hereinafter gNB) (31-10, 31-30, 1m-10) and an AMF (31-05, 31-25, 3m-05, new radio core network). A user terminal (N NR UE or terminal) (31-15, 3m-15) connects to an external network through the gNB (31-10, 3m-10) and the AMF (31-05, 3m-05).

[0087] Referring to FIGS. 3c, 3l, and 3m, a situation in which macro cells and pico cells are mixed can be considered. A macro cell is a cell controlled by a macro base station and provides service over a relatively wide area. On the other hand, a pico cell is a cell controlled by a SeNB and typically provides service over a significantly narrower area compared to a macro cell. Although there is no strict criterion for distinguishing between macro cells and pico cells, for example, the area of ​​a macro cell can be assumed to be about 500m in radius, and the area of ​​a pico cell about tens of meters in radius. In the embodiments of the present invention, pico cells and small cells are mixed. In this case, the macro cell may be an LTE or NR base station (MeNB or MgNB), and the pico cell may be an NR or LTE base station (SeNB or SgNB). In particular, a 5G base station supporting pico cells may use a frequency band of 6GHz or higher.

[0088] In the embodiments of the present invention, a situation in which macro cells and macro cells are mixed may be considered. A macro cell is a cell controlled by a macro base station and provides service over a relatively wide area. In this case, the macro cell may be composed of an LTE base station (MeNB) and an LTE base station (SeNB). In another embodiment, the macro cell may be composed of an LTE (MeNB) base station and an NR base station (SgNB). In yet another embodiment, the macro cell may be composed of an NR (MgNB) base station and an LTE base station (SeNB). In yet another embodiment, the macro cell may be composed of an NR (MgNB) base station and an NR base station (SgNB).

[0089] Both 4G systems (LTE) and 5G systems are based on Orthogonal Frequency Division Multiplexing (OFDM). While LTE has a fixed subcarrier spacing (SCS) of 15 kHz, 5G systems can support multiple subcarrier spacings (e.g., SCS: 7.5 kHz, 15 kHz, 30 kHz, 60 kHz, 120 kHz, etc.) to provide various services (e.g., eMBB, URLLC, mMTC, etc.) and wireless communication in various frequency ranges (e.g., sub-6 GHz, above-6 GHz, etc.). Going a step further, 5G systems can allow multiple SCSs to be time division multiplexed (TDM) or frequency division multiplexed (FDM) even within a single carrier. In addition, while the maximum bandwidth of a component carrier (CC) in LTE is assumed to be 20 MHz, in 5G systems, it can be considered up to 1 GHz.

[0090] Therefore, in the case of 5G systems, radio resources with different SCSs can be FDM or TDM. While LTE assumed a subframe as the basic unit of scheduling, 5G systems can assume a slot with 14 symbols as the basic unit of scheduling. That is, in LTE, the absolute time of a subframe was always fixed at 1ms, but in 5G systems, the length of a slot can vary depending on the SCS.

[0091] In particular, regarding the synchronous signal (SS) used in the initial connection procedure, 3GPP has defined the SS / PBCH (physical broadcast channel) block. The SS / PBCH block may include at least a primary synchronous signal (PSS), a secondary synchronous signal (SSS), and a PBCH. Furthermore, when the SS / PBCH block is transmitted, the PSS, SSS, and PBCH may always be transmitted in a sequence. Additionally, the SCS of the SS / PBCH block may be transmitted at one of 15 kHz, 30 kHz, 120 kHz, or 240 kHz depending on the frequency band. More specifically, in frequency bands below 6 GHz, an SCS having 15 kHz or 30 kHz is transmitted, and in frequency bands above 6 GHz, it may be transmitted at one of 120 kHz or 240 kHz. In addition, the above frequency bands can be classified in more detail, and an SS / PBCH block composed of a single SCS can be transmitted for each frequency band.

[0092] In addition, multiple SS / PBCH blocks can be transmitted within a single operating band. This is intended to allow terminals with various capabilities to coexist and operate within the system bandwidth. In this case, although the system bandwidth has increased, the location of the SS / PBCH block received by the terminal may vary depending on the network configuration. Furthermore, the transmission timing of the SS / PBCH block may also vary depending on the network configuration. Additionally, the transmission interval of the SS / PBCH block may not be constant. More specifically, as in the message below

[0093] The information indicating the system's channel bandwidth is designed to provide the SCS value used within that channel bandwidth.

[0094] FIG. 1d is a diagram showing the wireless protocol structure of a next-generation mobile communication system according to one embodiment of the present disclosure.

[0095] Referring to FIG. 1d, the wireless protocol of the next-generation mobile communication system can be composed of the NR Service Data Adaptation Protocol (SDAP) (1d-01, 1d-45), NR PDCP (1d-05, 1d-40), NR RLC (1d-10, 1d-35), and NR MAC (1d-15, 1d-30) at the terminal and the NR base station, respectively.

[0096] The main functions of NR SDAP (1d-01, 1d-45) may include at least some of the following functions.

[0097] - Transfer of user plane data

[0098] - Mapping function between a QoS flow and a DRB for both DL and UL for uplink and downlink

[0099] - Marking QoS flow ID in both DL and UL packets for uplink and downlink

[0100] - Function to map reflective QoS flow to data bearers for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

[0101] For SDAP layer devices, the terminal may receive a Radio Resource Control (RRC) message indicating whether to use the header of the SDAP layer device or to use the functions of the SDAP layer device for each PDCP layer device, for each bearer, or for each logical channel. If the SDAP header is configured, the terminal may instruct the terminal to update or reset the mapping information for the uplink and downlink QoS flows and data bearers through the 1-bit NAS reflective QoS indicator and the 1-bit AS reflective QoS indicator of the SDAP header. The SDAP header may include QoS flow ID information indicating QoS. The QoS information may be used for data processing priorities, scheduling information, etc., to support seamless service.

[0102] The main functions of NR PDCP(1d-05, 1d-40) may include at least some of the following functions.

[0103] - Header compression and decompression: ROHC (Robust Header Compression) only

[0104] - User data transfer function (Transfer of user data)

[0105] - In-sequence delivery of upper layer PDUs

[0106] - Out-of-sequence delivery of upper layer PDUs

[0107] - PDCP PDU reordering for reception

[0108] - Duplicate detection of lower layer SDUs

[0109] - Retransmission of PDCP SDUs

[0110] - Encryption and decryption functions (Ciphering and deciphering)

[0111] - Timer-based SDU discard in uplink.

[0112] In the above description, the reordering function of the NR PDCP (1d-05, 1d-40) device may mean a function that reorders PDCP PDUs received from the lower layer in order based on the PDCP SN (sequence number). The reordering function of the NR PDCP (1d-05, 1d-40) device may include a function to transmit data to the upper layer in the reordered order, a function to transmit immediately without considering the order, a function to record lost PDCP PDUs by reordering, a function to report the status of lost PDCP PDUs to the transmitting side, and a function to request retransmission of lost PDCP PDUs.

[0113] The main functions of NR RLC(1d-10, 1d-35) may include at least some of the following functions.

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

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

[0116] - Out-of-sequence delivery of upper layer PDUs

[0117] - ARQ function (Error Correction through ARQ)

[0118] - Concatenation, segmentation, and reassembly functions of RLC SDUs

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

[0120] - Reordering function (Reordering of RLC data PDUs)

[0121] - Duplicate detection

[0122] - Error detection function (Protocol error detection)

[0123] - RLC SDU discard function

[0124] RLC re-establishment function

[0125] In the above description, the in-sequence delivery function of the NR RLC (1d-10, 1d-35) device may mean a function of delivering RLC SDUs received from a lower layer to an upper layer in sequence. If a single RLC SDU is originally received divided into multiple RLC SDUs, the in-sequence delivery function of the NR RLC (1d-10, 1d-35) device may include a function of reassembling and delivering them.

[0126] The in-sequence delivery function of the NR RLC (1d-10, 1d-35) device may include a function to rearrange received RLC PDUs based on an RLC SN (sequence number) or PDCP SN (sequence number), a function to record lost RLC PDUs by rearranging the order, a function to report the status of lost RLC PDUs to the transmitting side, and a function to request retransmission of lost RLC PDUs.

[0127] The in-sequence delivery function of the NR RLC (1d-10, 1d-35) device may include a function to deliver only the RLC SDUs prior to the lost RLC SDU in order to the upper layer if there is a lost RLC SDU. Additionally, the in-sequence delivery function of the NR RLC (1d-10, 1d-35) device may include a function to deliver all RLC SDUs received before the timer started in order to the upper layer if a predetermined timer has expired, even if there is a lost RLC SDU. Additionally, the in-sequence delivery function of the NR RLC (1d-10, 1d-35) device may include a function to deliver all RLC SDUs received up to the present in order to the upper layer if a predetermined timer has expired, even if there is a lost RLC SDU.

[0128] The NR RLC (1d-10, 1d-35) device can process the RLC PDUs in the order they are received, regardless of the sequence number (out-of-sequence delivery), and deliver them to the NR PDCP (1d-05, 1d-40) device.

[0129] When the NR RLC (1d-10, 1d-35) device receives a segment, it can receive segments stored in a buffer or to be received later, reconstruct them into a complete RLC PDU, and then transmit it to the NR PDCP device.

[0130] The NR RLC layer may not include a concatenation function, and the function may be performed by the NR MAC layer or replaced by the multiplexing function of the NR MAC layer.

[0131] In the above description, the out-of-sequence delivery function of the NR RLC (1d-10, 1d-35) device may mean a function of delivering RLC SDUs received from a lower layer directly to an upper layer regardless of order. The out-of-sequence delivery function of the NR RLC (1d-10, 1d-35) device may include a function of reassembling and delivering a single RLC SDU when it is received divided into multiple RLC SDUs. The out-of-sequence delivery function of the NR RLC (1d-10, 1d-35) device may include a function of storing the RLC SN or PDCP SN of the received RLC PDUs, sorting the order, and recording the lost RLC PDUs.

[0132] The NR MAC (1d-15, 1d-30) can be connected to multiple NR RLC layer devices configured in a terminal, and the main functions of the NR MAC (1d-15, 1d-30) may include at least some of the following functions.

[0133] - Mapping function (Mapping between logical channels and transport channels)

[0134] - Multiplexing and demultiplexing functions (Multiplexing / demultiplexing of MAC SDUs)

[0135] - Scheduling information reporting function

[0136] - HARQ function (Error correction through HARQ)

[0137] - Priority handling between logical channels of one UE

[0138] - Priority handling between UEs by means of dynamic scheduling

[0139] - MBMS service identification function

[0140] - Transport format selection function

[0141] - Padding

[0142] The NR PHY layer (1d-20, 1d-25) can perform the operation of channel coding and modulating upper layer data, creating OFDM symbols and transmitting them to the wireless channel, or demodulating OFDM symbols received through the wireless channel and channel decoding them to transmit them to the upper layer.

[0143] FIG. 1e is a drawing illustrating V2X communication within a mobile communication system according to one embodiment of the present disclosure.

[0144] V2X (vehicle-to-everything) is a collective term for communication technologies that utilize a vehicle and all interfaces. Depending on its form and the components constituting the communication, it includes V2V (vehicle-to-vehicle), V2I (vehicle-to-intrastructure), V2P (vehicle-to-pedestrian), and V2N (vehicle-to-network). V2P and V2V can follow the structure and operating principles of Rel-13 device-to-device (D2D) communication. In other words, V2P and V2V operate based on sidelink (PC5) operations; actual data packets can be transmitted and received through the sidelink—a transmission channel between terminals—rather than through the uplinks and downlinks between a base station and a terminal. This fundamental concept is applicable not only to V2X defined in LTE but also to V2X newly defined in next-generation mobile communication (NR), and upgrades may be applied in specific scenarios.

[0145] A base station (1e-01) may include at least one vehicle terminal (1e-05, 1e-10) and a pedestrian mobile terminal (1e-15) located within a cell (1e-02) that supports V2X. That is, the vehicle terminal (1e-05) performs cellular communication with the base station (1e-01) using a vehicle terminal-base station link (Uu, 1e-30, 1e-35), and the pedestrian mobile terminal (1e-15) can perform cellular communication using a pedestrian terminal-base station link (Uu, 1e-40). The vehicle terminal (1e-05) can perform inter-device communication with another vehicle terminal (1e-10) or pedestrian mobile terminal (1e-15) using a side link (PC5, 1e-20, 1e-25). In the above, the base station (1e-01) may be an upgraded eNB that supports gNB or NR, and in order for the vehicle terminal (1e-05, 1e-10) and the pedestrian mobile terminal (1e-15) to directly exchange information using the side link (1e-20, 1e-25), the base station (1e-01) must allocate a resource pool that can be used for side link communication. Below, the method by which a base station allocates resources to a terminal in V2X of an LTE system is summarized in detail, and a similar approach to that in LTE can be applied to V2X introduced in an NR system. However, in NR, a different numerology is used, and the design of the side link resource pool may differ.

[0146] Based on V2X of the LTE system, the method by which a base station allocates resources to a terminal can be divided into two types: scheduled resource allocation (mode 3) and UE autonomous resource allocation (mode 4).

[0147] Scheduled resource allocation is a method in which a base station allocates resources used for sidelink transmission to RRC-connected terminals using a dedicated scheduling method. Since the scheduled resource allocation method allows the base station to manage sidelink resources, it is effective for interference management and resource pool management (dynamic allocation, semi-persistence transmission). Furthermore, in the case of scheduled resource allocation (mode 3), where the base station allocates and manages resources for V2X, if an RRC-connected terminal has data to transmit to other terminals, the terminal can transmit information to the base station indicating that there is data to transmit to other terminals using an RRC message or a MAC Control Element (hereinafter CE). Here, SidelinkUEInformation and UEAssistanceInformation messages can be used as RRC messages.

[0148] Meanwhile, MAC CE may be, for example, a buffer status report MAC CE of a new format (including an indicator indicating that it is a buffer status report for V2X communication and information about the size of the data buffered for sidelink communication). For detailed formats and contents regarding buffer status reports used by 3GPP, refer to 3GPP standard TS36.321 "E-UTRA MAC Protocol Specification".

[0149] UE autonomous resource allocation is a resource allocation method in which a base station provides a pool of sidelink transmission and reception resources for V2X to a terminal as system information, and the terminal selects a resource pool according to a set rule. Resource selection methods for the terminal may include zone mapping, sensing-based resource selection, and random selection. In the structure of the resource pool for V2X, resources for SA (scheduling allocation) (1e-45, 1e-55, 1e-65) and resources for data transmission (1e-50, 1e-60, 1e-70) may be adjacent to form a single sub-channel, or resources for SA (1e-75, 1e-80, 1e-85) and resources for data (1e-90, 1e-95, 1e-100) may not be adjacent. Regardless of which of the two structures is used, the SA consists of two consecutive PRBs and may include content indicating the location of the resources for data. The number of terminals receiving V2X services in a cell may be multiple, and the relationship between the base station (1e-01) and terminals (1e-05, 1e-10, 1e-15) described above may be extended and applied.

[0150] In addition, for sidelink data transmission and reception through a resource pool, V2X services in LTE systems were fundamentally distinguished using the Destination Layer 2 ID (or destination ID). That is, the terminal's Source / Destination Layer 2 IDs (each 24 bits in size) are included in the header of the V2X data packet (i.e., MAC PDU) transmitted via the sidelink, and the Destination Layer 2 ID can indicate the type of service of the V2X data traffic transmitted by the terminal. Here, the Source Layer 2 ID refers to the terminal's unique identifier.

[0151] If another terminal receives a Destination Layer 2 ID sent by a transmitting terminal, and is subscribed to the service for that Destination Layer 2 ID and configured to receive that service, it can decode the data packets belonging to the corresponding MAC PDU and forward them to the upper layer. Mapping information between the Destination Layer 2 ID and the V2X data packet is transmitted from the V2X server to the V2X Control Function and can be provisioned to the terminal.

[0152] FIG. 1f is a diagram illustrating a procedure for a terminal to select a random resource when a base station according to one embodiment of the present disclosure allocates resources to a terminal using a scheduled resource allocation method.

[0153] Referring to FIG. 1f, in V2P communication, a base station (1f-03) can allocate a resource pool for random resource selection and a pool for resource selection through partial sensing for a pedestrian mobile terminal (1f-01). For the mobile terminal (1f-01) to perform a partial sensing operation, it must have a sidelink reception capability. Therefore, considering that there may be a mobile terminal (1f-01) in the cell that does not have a sidelink reception capability, the base station can provide at least one resource pool for random resource selection to the mobile terminal (1f-01).

[0154] A mobile terminal (1f-01) that is in camp (1f-05) can receive system information (SIB21 or SIB22 or SIBx to be newly defined for vehicle communication) from a base station (1f-03) (1f-10). The system information received by the mobile terminal (1f-01) may include resource pool information for transmission and reception, setting information for sensing operations, information for setting synchronization, etc.

[0155] The mobile terminal (1f-01) can generate data traffic for P2V (pedestrian-to-vehicle) communication (1f-15) and perform an RRC connection with the base station (1f-03) (1f-20). The RRC connection process between the mobile terminal (1f-01) and the base station (1f-03) can be performed before the mobile terminal (1f-01) generates the data traffic (1f-15).

[0156] A mobile terminal (1f-01) can request a transmission resource from a base station (1f-03) to enable P2V communication with other vehicle terminals (1f-02) (1f-25). At this time, the mobile terminal (1f-01) can request a transmission resource from the base station (1f-03) to enable P2V communication using an RRC message or a MAC CE. Here, SidelinkUEInformation and UEAssistanceInformation messages may be used as RRC messages. Meanwhile, the MAC CE may be, for example, a buffer status report MAC CE of a new format (including an indicator indicating that it is a buffer status report for V2P communication and information about the size of the data buffered for D2D communication).

[0157] The base station (1f-03) can allocate P2V transmission resources to the mobile terminal (1f-01) via a dedicated RRC message (1f-30). The dedicated RRC message can be included in the RRCConnectionReconfiguration message.

[0158] A mobile terminal (1f-01) can randomly select a resource in the time / frequency domain (1f-35) from the resources allocated from the base station (1f-03) and transmit data to a vehicle terminal (1f-02) using the selected resource in the time / frequency domain (1f-40).

[0159] FIG. 1g is a diagram illustrating a procedure for a terminal to select a random resource when a base station according to one embodiment of the present disclosure allocates resources to a terminal using a UE autonomous resource allocation method.

[0160] Unlike the scheduled resource allocation mode (Mode 3), where the base station (1g-03) is directly involved in resource allocation, the UE autonomous resource allocation mode (Mode 4) operation allows the mobile terminal (1g-01) to autonomously select resources and transmit data based on a resource pool of system information received in advance. In V2P communication, the base station (1g-03) can allocate a resource pool for random resource selection and a pool for resource selection through partial sensing for the mobile terminal (1g-01). For the mobile terminal (1g-01) to perform a partial sensing operation, it must have the capability to receive a side link. Therefore, considering that there may be a mobile terminal (1g-01) in the cell that does not have the capability to receive a side link, the base station will provide at least one resource pool for random resource selection.

[0161] A mobile terminal (1g-01) that is in camp (1g-05) can receive system information (SIB21 or SIB22 or SIBx, which will be newly defined for vehicle communication) from a base station (1g-03) (1g-10). The system information received by the mobile terminal (1g-01) from the base station (1g-03) may include resource pool information for transmission and reception, setting information for sensing operations, information for setting synchronization, etc. The mobile terminal (1g-01) can generate data traffic for P2V communication (1g-15), select a pool capable of random resource selection from the resource pool received via system information from the base station (1g-03), and randomly select a resource in the time / frequency domain (1g-20). The mobile terminal (1g-01) can transmit data to a vehicle terminal (1g-02) using the selected resource in the time / frequency domain (1g-25).

[0162] FIG. 1h is a diagram illustrating partial sensing operations of a terminal in V2P (vehicle-to-pedestrian) communication.

[0163] Referring to FIG. 1h, the pedestrian mobile terminal (or P2V mobile terminal) can perform random resource selection or partial sensing operations for data transmission and reception. The pedestrian mobile terminal can repeat the operation of sensing surrounding resources only for a certain period of time at a 100ms interval during the sensing period (1h-05) without using the 1-second sensing window used in conventional sensing operations. Here, the sensing window (1h-15) can have a small size of about 10ms.

[0164] The pedestrian mobile terminal can select a resource at step 1h-20 by reflecting the sensing results measured 10 times during the sensing period (1h-05). That is, the pedestrian mobile terminal can select an empty resource excluding the resource occupied by another terminal based on the sensing results. Additionally, the pedestrian mobile terminal can transmit SA and related data through the selected resource via the selection window at step 1h-25. Partial sensing operation can be performed only for pedestrian mobile terminals equipped with sidelink Rx capability.

[0165] In next-generation mobile communication systems, V2P communication is expected to support vulnerable road user use cases to enhance driver safety and facilitate autonomous driving by enabling vehicles to communicate with other vehicles, infrastructure, Road-Side Units (RSUs), and road users. The technical requirements for V2P communication to support vulnerable road user use cases in next-generation mobile communication systems may be as follows.

[0166] 1. Determination of the timing for V2P signal transmission and V2P signal reception to reduce power consumption of pedestrian mobile terminals (Pedestrian-UE, hereinafter P-UE) (wherein, pedestrian mobile terminals collectively refer to mobile terminals of pedestrians, cyclists, motorcycle users, persons with physical disabilities, persons with mobility difficulties due to geographical limitations, etc.)

[0167] 2. Positioning accuracy: Collision warning messages requiring accuracy within 50cm to 1m, awareness messages requiring accuracy within 1m to 5m

[0168] 3. Pedestrian determination utilizing localized infrastructure equipped with infrastructure or Multi-access Edge Computing (MEC) capabilities (e.g., localized infrastructure equipped with surveillance cameras or wireless technology) and cooperative pedestrian determination through vehicle-to-vehicle communication

[0169] The present disclosure proposes a method for a pedestrian mobile terminal to perform transmission and reception of V2P signals with the assistance of a base station / vehicle terminal to support vulnerable road-side user use cases.

[0170] FIG. 1i is a diagram illustrating a method for a pedestrian terminal to perform transmission and reception of V2P signals with the help of a base station / vehicle terminal to reduce power consumption of the pedestrian terminal in V2P (vehicle-to-pedestrian) communication according to one embodiment of the present disclosure.

[0171] Referring to FIG. 1i, a pedestrian mobile terminal (1i-01) can camp on (1i-05) an LTE cell or an NR cell (1i-03). An LTE cell or an NR cell (1i-03) set as a danger zone can broadcast a system information (SIB21 or SIB26 or SIBx to be newly defined for vehicle communication) including a 1 bit indicating that it is a danger zone.

[0172] A pedestrian mobile terminal (1i-01) can receive system information after camp-on to an LTE cell or an NR cell (1i-10). The pedestrian mobile terminal (1i-01) can check whether the received system information includes a 1 bit indicating a danger area (e.g., whether the bit is set to TRUE) (1i-15). If the pedestrian mobile terminal (1i-01) determines that the received system information does not contain a 1 bit indicating a danger area, it may not transmit a P2V signal to the vehicle terminal (1i-02) and may not receive a V2P signal transmitted by the vehicle terminal (1i-2). If the pedestrian mobile terminal (1i-01) determines that the received system information contains a 1 bit indicating a danger area, the pedestrian mobile terminal may receive a V2P message. The pedestrian mobile terminal may then perform a series of processes to periodically broadcast the P2V message to other vehicle terminals.

[0173] A pedestrian mobile terminal (1i-01) can generate P2V data (1i-20) to inform a nearby vehicle terminal or another pedestrian terminal (1i-02) of the presence of a pedestrian (indicator, or GPS coordinates indicating the current location).

[0174] When the pedestrian mobile terminal (1i-01) and the vehicle terminal (1i-02) are operating in a scheduled resource allocation mode (mode 3), they can perform an RRC connection with the base station (1i-03) (1i-25). The RRC connection process can be performed before P2V data is generated (1i-20). The pedestrian mobile terminal (1i-01) can request transmission resources from the base station (1i-03) to perform P2V communication with the vehicle terminal (1i-02) (1i-30). At this time, the pedestrian mobile terminal (1i-01) can request transmission resources from the base station (1i-03) to perform P2V communication using an RRC message or MAC CE. Here, SidelinkUEInformation and UEAssistanceInformation messages can be used as RRC messages.

[0175] Meanwhile, the MAC CE may be, for example, a buffer status report MAC CE of a new format (including an indicator indicating that it is a buffer status report for V2P communication and information about the size of the data buffered for D2D communication). The base station (1i-03) may allocate P2V transmission resources to the mobile terminal (1i-01) via a dedicated RRC message (1i-35). The dedicated RRC message may be included in an RRC connection reconfiguration message (RRCConnectionReconfiguration message). The pedestrian mobile terminal (1i-01) may randomly select a resource in the time / frequency domain from the resource instructed by the base station (1i-03) or an exception pool (1i-40), and periodically transmit P2V data to the vehicle terminal (1i-02) (1i-45). A vehicle terminal (1i-02) that has received P2V data can use it to drive (e.g., display the location of the pedestrian mobile terminal on the navigation) or transmit the P2V data received from the mobile terminal (1i-01) to other vehicle terminals in the vicinity.

[0176] After the pedestrian mobile terminal (1i-01) generates P2V data (1i-50) to inform the surrounding vehicle terminal (1i-02) of the presence of a pedestrian, when operating in UE autonomous resource allocation mode (mode 4), steps 1i-25, 1i-30, and 1i-35 are not performed, and a pool capable of random resource selection is selected from the resource pool received through system information from the base station (1i-03), and a resource in the time / frequency domain can be randomly selected (1i-40).

[0177] A pedestrian mobile terminal (1i-01) can transmit P2V data to a vehicle terminal (1i-02) using resources in a selected time / frequency range (1i-45). A vehicle terminal (1i-02) that receives the P2V data can use the P2V data to drive (e.g., display the location of the pedestrian mobile terminal on a navigation system) or transmit the P2V data received from the mobile terminal (1i-01) to other vehicle terminals in the vicinity.

[0178] FIG. 1j is a diagram illustrating a method for a pedestrian terminal to perform transmission and reception of V2P signals with the help of a base station / vehicle terminal to reduce power consumption of the pedestrian terminal in V2P (vehicle-to-pedestrian) communication according to one embodiment of the present disclosure.

[0179] Referring to FIG. 1j, a pedestrian mobile terminal (1j-01) can camp on (1j-05) to an LTE cell or NR cell (1j-03). An LTE cell or NR cell (1j-03) set as a risk area can broadcast system information (SIB21 or SIB26 or SIBx to be newly defined for vehicle communication) containing a Risk Area Information Element (RiskAreaInformation IE). The Risk Area Information IE contained in the system information may include information indicating a risk area (e.g., GPS coordinates). After camping on to the LTE cell or NR cell, the pedestrian mobile terminal (1j-01) can receive the system information (1j-10). The pedestrian mobile terminal (1j-01) can check whether the received system information contains the Risk Area Information IE (1j-15).

[0180] If the received system information does not contain RiskAreaInformation IE indicating a danger area, the pedestrian mobile terminal (1j-01) may not transmit a P2V signal to the vehicle terminal (1j-02) and may not receive a V2P signal transmitted by the vehicle terminal (1j-2). If the received system information includes RiskAreaInformation IE indicating a danger area, the pedestrian mobile terminal can compare its location with the RiskAreaInformation IE. If the pedestrian mobile terminal (1j-01) determines that its location is within the danger area, it may receive a V2P message. The pedestrian mobile terminal (1j-01) may then perform a series of processes to periodically broadcast P2V messages to other vehicle terminals.

[0181] A pedestrian mobile terminal (1j-01) can generate P2V data (1j-20) to inform a nearby vehicle terminal or another pedestrian terminal (1j-02) of the presence of a pedestrian (indicator, or GPS coordinates indicating the current location).

[0182] When operating in scheduled resource allocation mode (mode 3), the pedestrian mobile terminal (1j-01) and the vehicle terminal (1j-02) can perform an RRC connection with the base station (1j-03) (1j-25). The RRC connection process can be performed before P2V data is generated (1j-20). The pedestrian mobile terminal (1j-01) can request transmission resources from the base station (1j-03) to perform P2V communication with the vehicle terminal (1j-02) (1j-30). At this time, the pedestrian mobile terminal (1j-01) can request transmission resources from the base station (1j-03) to perform P2V communication using an RRC message or MAC CE. Here, SidelinkUEInformation and UEAssistanceInformation messages can be used as RRC messages. Meanwhile, the MAC CE may be, for example, a buffer status report MAC CE of a new format (including an indicator indicating that it is a buffer status report for V2P communication and information about the size of the data buffered for D2D communication).

[0183] The base station (1j-03) can allocate P2V transmission resources to the mobile terminal (1j-01) via a dedicated RRC message (1j-35). The dedicated RRC message may be included in an RRC connection reconfiguration message (RRCConnectionReconfiguration message). The pedestrian mobile terminal (1j-01) can randomly select a resource in the time / frequency domain (1j-40) from a resource instructed by the base station (1j-03) or an exception pool, and periodically transmit P2V data to the vehicle terminal (1j-02) (1j-45). The vehicle terminal (1j-02) that receives the P2V data can use it to drive (e.g., display the location of the pedestrian mobile terminal on the navigation) or transmit the P2V data received from the mobile terminal (1j-01) to other nearby vehicle terminals.

[0184] After generating P2V data (1j-50) to inform a surrounding vehicle terminal (1j-02) of the presence of a pedestrian, the pedestrian mobile terminal (1j-01) does not perform steps 1j-25, 1j-30, and 1j-35 when operating in UE autonomous resource allocation mode (mode 4), and selects a pool capable of random resource selection from a pool of resources received via system information from a base station (1j-03), and can randomly select a resource in the time / frequency domain (1j-40). The pedestrian mobile terminal (1j-01) can transmit P2V data to the vehicle terminal (1j-02) using the selected resource in the time / frequency domain (1j-45). The vehicle terminal (1j-02) that receives the P2V data can use it to drive (e.g., display the location of the pedestrian mobile terminal on the navigation) or transmit the P2V data received from the mobile terminal (1j-01) to other surrounding vehicle terminals. And the pedestrian hand terminal (1j-01) can perform a series of processes to periodically broadcast P2V messages to other vehicle terminals.

[0185] FIG. 1k is a diagram illustrating a method in which a pedestrian terminal performs transmission and reception of V2P signals with the help of a base station / vehicle terminal to reduce power consumption of the pedestrian terminal in V2P (vehicle-to-pedestrian) communication according to one embodiment of the present disclosure.

[0186] Referring to FIG. 1k, a pedestrian mobile terminal (1k-01) can camp on (1k-05) to an LTE cell or an NR cell (1k-03). An LTE cell or an NR cell (1k-03) set as a risk area can broadcast a Risk Area Information Element (RiskAreaInformation IE) included in system information (SIB21 or SIB26 or SIBx to be newly defined for vehicle communication). In the Risk Area Information IE contained in the system information, the risk area can be represented as beam information (e.g., SSB IDs (Synchronization Signal / Physical Broadcast Channel Block IDs)). After camping on to the LTE cell or an NR cell, the pedestrian mobile terminal (1k-01) can receive the system information (1k-10). The pedestrian mobile terminal (1k-01) can perform SSB measurements (1k-15). The pedestrian mobile terminal (1k-01) can identify a list of SSB IDs in which the absolute signal strength of the synchronization signal (Synchronization Signal Reference Received Power, SS-RSRP) exceeds a threshold as a result of SSB measurement (1k-20). Then, the pedestrian mobile terminal (1k-01) can compare the above list of SSB IDs with the SSB ID(s) stored in the system information (1k-25). If there is no matching SSB ID, the pedestrian mobile terminal (1k-01) may not transmit a P2V signal to the vehicle terminal (1k-02) and may not receive the V2P signal transmitted by the vehicle terminal (1k-2). If there is a matching SSB ID, the pedestrian mobile terminal (1k-01) can receive the V2P message. Then, the pedestrian mobile terminal (1k-01) can perform a series of processes to periodically broadcast the P2V message to other vehicle terminals.

[0187] A pedestrian mobile terminal (1k-01) can generate P2V data (1k-30) to inform a nearby vehicle terminal or another pedestrian terminal (1k-02) of the presence of a pedestrian (indicator, or GPS coordinates indicating the current location).

[0188] When operating in scheduled resource allocation mode (mode 3), the pedestrian mobile terminal (1k-01) and the vehicle terminal (1k-02) can perform an RRC connection with the base station (1k-03) (1k-35). The RRC connection process can be performed before P2V data is generated (1k-30). The pedestrian mobile terminal (1k-01) can request transmission resources from the base station (1k-03) to perform P2V communication with the vehicle terminal (1k-02) (1k-40). At this time, the pedestrian mobile terminal (1k-01) can request transmission resources from the base station (1k-03) to perform P2V communication using an RRC message or MAC CE. Here, SidelinkUEInformation and UEAssistanceInformation messages can be used as RRC messages. Meanwhile, the MAC CE may be, for example, a buffer status report MAC CE of a new format (including an indicator indicating that it is a buffer status report for V2P communication and information about the size of the data buffered for D2D communication).

[0189] The base station (1k-03) can allocate P2V transmission resources to the mobile terminal (1k-01) via a dedicated RRC message (1k-45). The dedicated RRC message may be included in an RRC connection reconfiguration message (RRCConnectionReconfiguration message). The pedestrian mobile terminal (1k-01) can randomly select a resource in the time / frequency domain (1k-50) from a resource instructed by the base station (1k-03) or an exception pool, and periodically transmit P2V data to the vehicle terminal (1k-02) (1k-55). The vehicle terminal (1k-02) that receives the P2V data can use it to drive (e.g., display the location of the pedestrian mobile terminal on the navigation system) or transmit the P2V data received from the mobile terminal (1k-01) to other nearby vehicle terminals.

[0190] After generating P2V data (1k-30) to inform a nearby vehicle terminal (1k-02) of the presence of a pedestrian, the pedestrian mobile terminal (1k-01) does not perform steps 1k-35, 1k-40, and 1k-45 when operating in UE autonomous resource allocation mode (mode 4), but selects a pool capable of random resource selection from a pool of resources received via system information from a base station (1k-03), and can randomly select a resource in the time / frequency domain (1k-50). The pedestrian mobile terminal (1k-01) can transmit P2V data to the vehicle terminal (1k-02) using the selected resource in the time / frequency domain (1k-55). The vehicle terminal (1k-02) that receives the P2V data can use it to drive (e.g., display the location of the pedestrian mobile terminal on the navigation) or transmit the P2V data received from the mobile terminal (1k-01) to other nearby vehicle terminals.

[0191] FIG. 11 is a drawing for explaining a method in which a pedestrian handheld terminal (11-01) performs transmission and reception of V2P signals with the help of a base station / vehicle terminal to reduce power consumption of the pedestrian terminal in V2P (vehicle-to-pedestrian) communication according to one embodiment of the present disclosure.

[0192] Referring to FIG. 11, a pedestrian mobile terminal (1l-01) can camp on (1l-05) to an LTE cell or NR cell (1l-03). An LTE cell or NR cell (1l-03) set as a danger zone can broadcast system information (SIB21 or SIB26 or SIBx to be newly defined for vehicle communication). After camping on to the LTE cell or NR cell, the pedestrian mobile terminal (1l-01) can receive system information (1l-10). An LTE cell or NR cell (1l-03) can broadcast a beam-based paging message to a location determined to be a danger zone (1l-15). At this time, the LTE cell or NR cell (1l-03) broadcasts the paging message only to a location covered by an SSB ID(s) mapped to the danger zone, and the paging message can include a 1 bit indicating that it is a danger zone. Alternatively, an LTE cell or NR cell (1l-03) may broadcast paging messages only in areas covered by SSB ID(s) mapped to a danger zone, and the paging message may include a 1 bit instructing the pedestrian mobile terminal to transmit a P2V message. The pedestrian mobile terminal (1l-01) that receives the paging message may receive a V2P message. The pedestrian mobile terminal (1l-01) may perform a series of processes to periodically broadcast the P2V message to other vehicle terminals.

[0193] A pedestrian mobile terminal (1l-01) can generate P2V data (1l-25) to inform a nearby vehicle terminal or another pedestrian terminal (1l-02) of the presence of a pedestrian (indicator, or GPS coordinates indicating the current location).

[0194] When operating in scheduled resource allocation mode (mode 3), the pedestrian mobile terminal (1l-01) and the vehicle terminal (1l-02) can perform an RRC connection with the base station (1l-03) (1l-30). The RRC connection process can be performed before P2V data is generated (1l-25). The pedestrian mobile terminal (1l-01) can request transmission resources from the base station (1l-03) to perform P2V communication with the vehicle terminal (1l-02) (1l-35). At this time, the pedestrian mobile terminal (1l-01) can request transmission resources from the base station (1l-03) to perform P2V communication using an RRC message or MAC CE. Here, SidelinkUEInformation and UEAssistanceInformation messages can be used as RRC messages.

[0195] Meanwhile, the MAC CE may be, for example, a buffer status report MAC CE of a new format (including an indicator indicating that it is a buffer status report for V2P communication and information about the size of the data buffered for D2D communication). The base station (1l-03) may allocate P2V transmission resources to the mobile terminal (1l-01) via a dedicated RRC message (1l-40). The dedicated RRC message may be included in an RRC connection reconfiguration message (RRCConnectionReconfiguration message). The pedestrian mobile terminal (1l-01) may randomly select a resource in the time / frequency domain from the resource instructed by the base station (1l-03) or an exception pool (1l-45), and periodically transmit P2V data to the vehicle terminal (1l-02) (1l-50). A vehicle terminal (1l-02) that has received P2V data can use it to drive (e.g., display the location of a pedestrian's mobile terminal on a navigation system) or transmit the P2V data received from the mobile terminal (1l-01) to other vehicle terminals in the vicinity.

[0196] After generating P2V data (11-25) to inform a surrounding vehicle terminal (11-02) of the presence of a pedestrian, the pedestrian mobile terminal (11-01) does not perform steps 11-30, 11-35, and 11-40 when operating in UE autonomous resource allocation mode (mode 4), and selects a pool capable of random resource selection from a pool of resources received via system information from a base station (11-03), and can randomly select a resource in the time / frequency domain (11-45). The pedestrian mobile terminal (11-01) can transmit P2V data to the vehicle terminal (11-02) using the selected resource in the time / frequency domain (11-50). The vehicle terminal (11-02) that receives the P2V data can use it to drive (e.g., display the location of the pedestrian mobile terminal on the navigation) or transmit the P2V data received from the mobile terminal (11-01) to other surrounding vehicle terminals.

[0197] FIG. 1m is a drawing for explaining a method in which a pedestrian handheld terminal (1m-01) performs transmission and reception of V2P signals with the help of a base station / vehicle terminal to reduce power consumption of the pedestrian terminal in V2P (vehicle-to-pedestrian) communication according to one embodiment of the present disclosure.

[0198] Referring to FIG. 1m, a pedestrian mobile terminal (1m-01) can camp on (1m-05) to an LTE cell or NR cell (1m-03). The LTE cell or NR cell (1m-03) designated as a danger zone can broadcast system information (SIB21 or SIB26 or SIBx to be newly defined for vehicle communication). After camping on to the LTE cell or NR cell (1m-03), the pedestrian mobile terminal (1m-01) can receive system information (1m-10). The LTE cell or NR cell can broadcast short messages based on beams in areas determined to be danger zones (1m-15). Short messages in the present disclosure can be defined as follows.

[0199] Short messages can be transmitted on PDCCH using P-RNTI with or without associated paging messages using the Short message field in DCI formal 1_0. The table below defines short messages. Bit 1 corresponds to the most significant bit.

[0200]

[0201] According to the table above, if bit 1 is set to 1 in a short message, it indicates a BCCH modification other than SIB 6, SIB 7, and SIB 8, and if bit 2 is set to 1, it indicates an ETWS primary notification and / or ETWS secondary notification and / or CMAS notification. Additionally, according to the table above, if bit 3 is set to 1 in a short message, it may indicate a danger or P2V / V2P transmission / reception. Meanwhile, bits 4-8 in a short message are not used and may be ignored by the UE upon receipt.

[0202] At this time, the LTE cell or NR cell (1m-03) may broadcast short messages only in areas covered by SSB ID(s) mapped to a danger area, and the short message may include 1 bit indicating that it is a danger area. Meanwhile, information regarding the SSB ID mapped to a danger area may be provided through system information or paging messages. Alternatively, the LTE cell or NR cell (1m-03) may broadcast short messages only in areas covered by SSB ID(s) mapped to a danger area, and the short message may include 1 bit instructing the pedestrian mobile terminal (1m-01) to transmit a P2V message. The pedestrian mobile terminal (1m-01) that receives the short message may receive a V2P message. The pedestrian mobile terminal (1m-01) may perform a series of processes to periodically broadcast the P2V message to other vehicle terminals.

[0203] A pedestrian mobile terminal (1m-01) can generate P2V data (1m-25) to inform a nearby vehicle terminal or another pedestrian terminal (1m-02) of the presence of a pedestrian (indicator, or GPS coordinates indicating the current location).

[0204] When operating in scheduled resource allocation mode (mode 3), the pedestrian mobile terminal (1m-01) and the vehicle terminal (1m-02) can establish an RRC connection with the base station (1m-03) (1m-30). The RRC connection process can be performed before P2V data is generated (1m-25). The pedestrian mobile terminal (1m-01) can request transmission resources from the base station (1m-03) to perform P2V communication with the vehicle terminal (1m-02) (1m-35). At this time, the pedestrian mobile terminal (1m-01) can request transmission resources from the base station (1m-03) to perform P2V communication using an RRC message or MAC CE. Here, SidelinkUEInformation and UEAssistanceInformation messages may be used as RRC messages.

[0205] Meanwhile, the MAC CE may be, for example, a buffer status report MAC CE of a new format (including an indicator indicating that it is a buffer status report for V2P communication and information about the size of the data buffered for D2D communication). The base station (1m-03) may allocate P2V transmission resources to the mobile terminal (1m-01) via a dedicated RRC message (1m-40). The dedicated RRC message may be included in an RRC connection reconfiguration message (RRCConnectionReconfiguration message). The pedestrian mobile terminal (1m-01) may randomly select a resource in the time / frequency domain from the resource instructed by the base station (1m-03) or an exception pool (1m-45), and periodically transmit P2V data to the vehicle terminal (1m-02) (1m-50). A vehicle terminal (1m-02) that has received P2V data can use it to drive (e.g., display the location of the pedestrian mobile terminal on the navigation) or transmit the P2V data received from the pedestrian mobile terminal (1m-01) to other vehicle terminals in the vicinity.

[0206] After generating P2V data (1m-25) to inform a nearby vehicle terminal (1m-02) of the presence of a pedestrian, the pedestrian mobile terminal (1m-01) does not perform steps 1m-30, 1m-35, and 1m-40 when operating in UE autonomous resource allocation mode (mode 4), and selects a pool capable of random resource selection from a pool of resources received via system information from a base station (1m-03), and can randomly select a resource in the time / frequency domain (1m-45). The pedestrian mobile terminal (1m-01) can transmit P2V data to the vehicle terminal (1m-02) using the selected resource in the time / frequency domain (1m-50). The vehicle terminal (1m-02) that receives the P2V data can use it to drive (e.g., display the location of the pedestrian mobile terminal on the navigation) or transmit the P2V data received from the mobile terminal (1m-01) to another nearby vehicle terminal.

[0207] In next-generation mobile communication systems, various vertical services, such as Vehicle to Everything (V2X) and the Industrial Internet of Things (IIoT), are expected to become active. Accordingly, it is anticipated that various terminals suitable for these diverse vertical services will exist. However, current paging mechanisms are designed for various purposes based on a single paging resource set that applies universally to all terminals, without considering the requirements of these diverse vertical services and terminals. A single paging resource set refers to a set of physical and logical resources required to transmit paging signals for various purposes, based on the same default and common P-RNTI across UEs that all terminals use by default. Here, these various purposes refer to paging messages indicating that there is a Mobile terminated call (MT call) to the terminal based on the paging record, short messages indicating that system information has been changed or modified, and short messages indicating that a disaster has occurred. Accordingly, general paging mechanisms designed for UMTS systems, LTE systems, and NR Phase 1 systems can be summarized as shown in Table 1 below. According to Table 1, the purposes of general paging can be classified into paging for MT, system information updates, and ETWS / CMAS.

[0208]

[0209]

[0210] General paging designed to date has not been designed to be differentiated between all terminals and specific vertical services. Therefore, general paging may unnecessarily provide paging information to specific terminals that desire specific vertical services, which may cause the terminal to wake up unnecessarily and induce power consumption. Accordingly, the present disclosure proposes a method in which a base station sets up vertical paging for terminals on a need basis in addition to general paging. The proposed vertical paging can be summarized as shown in Table 2 below. According to Table 2, the purpose of vertical paging can be classified into paging for V2X specific MTs, paging for V2X specific system information updates, paging for V2X specific P2V displays, and group paging for V2X specific UEs.

[0211] Table 2

[0212]

[0213] Referring to Table 2, in a next-generation mobile communication system, a terminal in RRC idle mode or RRC disabled mode may have general paging set up by default through a base station. For example, if the terminal is subscribed to a V2X service, the base station may suggest setting up V2X paging in addition to general paging to the terminal. Although V2X services are used as an example in this disclosure, the method proposed above can be applied in the same way when supporting various other vertical services, such as IIoT services.

[0214] FIG. 2e is a conceptual diagram illustrating a typical or vertical paging point of an RRC idle mode (RRC Idle mode) or RRC inactive mode terminal in a next-generation mobile communication system according to one embodiment of the present disclosure.

[0215] A terminal in RRC Idle mode or RRC Inactive mode may perform a Discontinuous Reception (DRX) operation to receive a paging signal from a base station. A DRX operation means attempting to receive a paging signal by performing a reception operation at a single Paging Occasion (PO, 2e-05) periodically, rather than constantly monitoring the paging signal to reduce power consumption. Specifically, a PO (2e-05) consisting of a set of PDCCH monitoring occasions may exist in one or more time slots in which Paging Downlink Control Information (2e-10) is transmitted. The unit of a time slot may be a single subframe or a single OFDM symbol. The System Frame Number (SFN) may increase by 1 for each radio frame. A paging frame (PF) may exist within a radio frame. According to another example, a PF composed of one or more POs may mean a single radio frame (2f-15). Also, according to yet another example, if a PF composed of one or more POs exists across multiple radio frames, the point in time when the POs begin may be considered as the PF (2f-20).

[0216] FIG. 2f is a diagram illustrating a method for a terminal in RRC Idle mode or RRC Inactive mode to monitor a general paging signal or a vertical paging signal in a next-generation mobile communication system according to one embodiment of the present disclosure.

[0217] Referring to FIG. 2f, an RRC idle mode or RRC disabled mode terminal (2f-01) can camp on to an NR cell (2f-05). An RRC idle mode or RRC disabled mode terminal that has camped on to an NR cell can receive system information from the cell it has camped on (2f-10). The system information may include at least one of MIB (Master Information Block), SIB1 (System Information Block 1), and SIB2 (System Information Block 2). Additionally, if the terminal supports vertical services, it may additionally receive system information (SIBx) for vertical services (2f-10). The present disclosure proposes that the DRX operation of an RRC idle mode or RRC disabled mode terminal that has received system information is performed through the following Equations 1 and 2.

[0218] For each radio frame, the System Frame Number (SFN) can be increased by 1. When a paging signal is transmitted in a radio frame satisfying Equation 1, the terminal can perform a reception operation via the DRX. A radio frame can be described as a paging frame (PF). A PF can consist of one or more paging occasions. If a PF consists of one or more POs spanning multiple radio frames, the point at which the PO begins can be considered the PF. An RRC idle mode or RRC disabled mode terminal can monitor its paging signal in a PF derived from Equation 1 and in a single PO derived from Equation 2 (2f-15).

[0219] <Formula 1>

[0220] (SFN + PF_offset) mod T = (T div N)*(UE_ID mod N)

[0221] <Equation 2>

[0222] i_s = floor(UE_ID / N) mod Ns

[0224] Here, each parameter can be defined as follows.

[0225] SFN: System Frame Number, which is 10 bits.

[0226] T: DRX cycle of the UE (T is determined by the shortest of the UE specific DRX value, if configured by RRC or upper layers, and a default DRX value in system information. IF UE specific DRX is not configured by RRC or upper layers, the default value is applied.)

[0227] N: Number of total paging frames in T.

[0228] *203 PF_offset: Offset used for PF determination

[0229] UE_ID: 5G-S-TMSI mod 1024

[0230] i_s: Index indicating the start of a set of PDCCH monitoring occasions for the paging DCI

[0231] The System Frame Number (SFN) can be composed of 10 bits. The base station may explicitly include the top 6 bits of the SFN in the Master Information Block (MIB), which is one of the system information, and transmit it to the terminal, and the bottom 4 bits of the SFN may be transmitted to the terminal as part of channel coding in the Physical Broadcast Channel (PBCH) transport block. To receive a general paging signal in Table 2 above, the terminal can derive Equations 1 and 2 by applying the paging channel configuration information (PCCH-Config) included in SIB1 broadcast by the base station (2f-15). On the other hand, to receive a vertical paging signal in Table 2 above, the terminal can derive Equations 1 and 2 by applying the vertical paging channel configuration information (PCCH-Config for Vertical Paging) included in SIBx broadcast by the base station (2f-20).

[0232] To receive a normal paging signal in step 2f-20, the terminal can apply the default DRX period (defaultPagingCycle) included in the SIB broadcast by the base station. To receive a vertical paging signal in step 2f-20, the terminal can apply the default DRX period (defaultPagingCycle for vertical paging) to the SIBx broadcast by the base station. If the defaultPagingCycle for vertical paging value does not exist in the SIBx broadcast by the base station, the terminal can apply the default DRX period (defaultPagingCycle) included in the SIB1 broadcast by the base station.

[0233] The actual T value applied in the aforementioned Equation 1 can be derived through coordination between the terminal, the base station, and the AMF. If the terminal desires a DRX period shorter than the default DRX period length, it can provide a terminal-specific DRX value (UE-specific DRX value) to the AMF through the ATTACH process. If paging is available for the terminal, the AMF can transmit the terminal-specific DRX value received from the terminal to the base station along with the paging. The terminal can determine the shorter value between the UE-specific DRX value transmitted to the AMF and the default DRX value received from the base station as the DRX period. The base station can also determine the shorter value between the UE-specific DRX value received from the AMF and the default DRX value it is broadcasting as the DRX period. The DRX period value can be the actual T value applied in the aforementioned Equation 1. Therefore, the terminal and the base station can select the same DRX period. The base station can determine the PF based on the proposed Equation 1 based on the DRX period and then transmit paging to the terminal. To receive a general paging signal, the terminal can use the paging channel configuration information included in the SIB1 broadcast by the base station to apply the total number of PFs during T (N), the offset used to determine the PF (PF_offset), the number of POs in one PF (Ns), and a value indicating the first PDDCH monitoring opportunity of each PO within the PF (firstPDDCH-MonitoringOccasionOfPO).Additionally, to receive vertical paging signals, the terminal may use the vertical paging channel configuration information included in the SIBx broadcast by the base station to apply the total number of PFs during T (N), the offset used to determine the PF (PF_offset), the number of POs in one PF (Ns), and a value indicating the first PDDCH monitoring opportunity of each PO within the PF (firstPDDCH-MonitoringOccasionOfPO). If the value of N does not exist in the SIBx, the terminal may derive Equation 1 or Equation 2 by applying the value of N broadcast in SIB1 to receive vertical paging signals. Similarly, the terminal may derive Equation 1 or Equation 2 by applying the respective values ​​according to the aforementioned procedure to PF_offset, Ns, and firstPDCCH-MonitoringOccasionOfPO. 5G-S-TMSI is a unique number assigned when the terminal is registered with the network, and if the terminal is not registered with the network, UE_ID may be considered as 0.

[0234] PDDCH monitoring opportunities for receiving general paging signals can be determined by the paging-SearchSpace set in SIB1 transmitted from the base station to the terminal and the firstPDCCH-MonitoringOCcasionOfPO set in SIBx. Otherwise, PDCCH monitoring opportunities for receiving general paging signals can be determined in the same way by being connected to the RMSI (Remaining Minimum System Information), which can be described as a default association. If the PDCCH monitoring opportunities for receiving general paging signals are in a default association, Ns can have a value of 1 or 2. If Ns has a value of 1, i_s can have a value of 0 according to Equation 2. This means that there is only one PO starting from a single PF. If Ns has a value of 1, the terminal can monitor paging signals from the PO derived according to Equation 2 in the PF derived from Equation 1 above. When Ns has a value of 2, i_s can have a value of 0 or 1 according to the aforementioned Equation 2. If i_s is 0, it means the first half-radio frame, and if i_s is 1, it means the second half-radio frame. That is, in the PF derived from the aforementioned Equation 1, if the value of i_s derived according to the aforementioned Equation 2 is 0, the terminal monitors the paging signal in the first half-radio frame (meaning PO) of the PF, and if the value derived from the aforementioned Equation 2 is 1, the terminal monitors the paging signal in the second half-radio frame (meaning PO) of the PF (2f-25).

[0235] If the paging search space is used and the PDCCH monitoring opportunities for receiving general paging signals are not associated by default (non-default association), the terminal can monitor the (i_s+1)th PO using the i_s value derived according to the aforementioned Equation 2 in the PF derived from the aforementioned Equation 1 to perform monitoring for the paging signal (2f-25). In this case, if the PDCCH monitoring opportunities for receiving general paging signals do not overlap with uplink symbols, the first PDCCH monitoring opportunity can be indexed starting from 0. If firstPDCCH-MonitoringOccasionOfPO exists in SIB1, the (i_s+1)th PO refers to a set of S consecutive PDCCH monitoring opportunities starting from the PDCCH monitoring opportunity indicated by firstPDCCH-MonitoringOccasionOfPO. Otherwise, the (i_s+1)th PO represents a set of S consecutive PDCCH monitoring opportunities starting from the (i_s*S)th PDCCH monitoring opportunity. Here, S represents the number of SSBs (Synchronization Signal / Physical Broadcast Channel Blocks) actually transmitted, which can be determined by ssb-PositionsInBurst included in SIB1. The Kth PDDCH monitoring opportunity within the PO corresponds to the Kth transmitted SSB.

[0236] In the above-described embodiment, PDDCH monitoring opportunities for receiving vertical paging signals can be determined by the paging-SearchSpace set in SIB1 transmitted from the base station to the terminal and the firstPDCCH-MonitoringOCcasionOfPO set in SIBx. Otherwise, PDCCH monitoring opportunities for receiving vertical paging signals can be determined identically by the connection of RMSI (Remaining Minimum System Information), which can be described as a default association. If the PDCCH monitoring opportunities for receiving vertical paging signals are in a default association, Ns can have a value of 1 or 2. If Ns has a value of 1, i_s can have a value of 0 according to the above-described Equation 2. This means that there is only one PO starting from a single PF. When Ns has a value of 1, the terminal can monitor the paging signal in the PF derived from the aforementioned Equation 1 and the PO derived from the aforementioned Equation 2 (2f-30). When Ns has a value of 2, i_s can have a value of 0 or 1 according to the aforementioned Equation 2. If i_s is 0, it means the first half-radio frame, and if i_s is 1, it means the second half-radio frame. That is, in the PF derived from the aforementioned Equation 1, if the value of i_s derived from the aforementioned Equation 2 is 0, the terminal monitors the paging signal in the first half-radio frame (meaning PO) in the PF, and if the value derived from the aforementioned Equation 2 is 1, the terminal monitors the paging signal in the second half-radio frame (meaning PO) in the PF.

[0237] If the paging search space is used and the PDCCH monitoring opportunities for receiving vertical paging signals are not connected by default (non-default association), the terminal can monitor the paging signal by monitoring the (i_s+1)th PO using the i_s value derived from Equation 2 above in the PF derived from Equation 1 above (2f-30). In this case, if the PDCCH monitoring opportunities for receiving vertical paging signals do not overlap with uplink symbols, the first PDCCH monitoring opportunity can be indexed starting from 0. If firstPDCCH-MonitoringOccasionOfPO exists in SIBx, the (i_s+1)th PO refers to a set of S consecutive PDCCH monitoring opportunities starting from the PDCCH monitoring opportunity indicated by firstPDCCH-MonitoringOccasionOfPO. Otherwise, the (i_s+1)th PO represents a set of S consecutive PDCCH monitoring opportunities starting from the (i_s*S)th PDCCH monitoring opportunity. Here, S represents the number of SSBs (Synchronization Signal / Physical Broadcast Channel Blocks) actually transmitted, which can be determined by ssb-PositionsInBurst included in SIB1 or by ssb-PositionsInBurst included in SIBx. The Kth PDDCH monitoring opportunity within the PO corresponds to the Kth transmitted SSB.

[0238] FIG. 2g is a diagram illustrating a method for receiving DCI to receive a general paging signal or a vertical paging signal and a method for interpreting the paging signal in an RRC idle mode or RRC inactive mode terminal in a next-generation mobile communication system according to one embodiment of the present disclosure.

[0239] Referring to FIG. 2g, an RRC idle mode or RRC disabled mode terminal (2g-01) can receive DCIs at all PDCCH opportunities in the Common Search Space (CSS) to receive general paging signals or vertical paging signals (2g-05). In step 2g-10, the RRC idle mode or RRC disabled mode terminal can perform a Cyclic Redundancy Check through P-RNTI (Default and Common P-RNTI across all UEs) to receive general paging signals. In step 2g-10, the RRC idle mode or RRC disabled mode terminal can perform a Cyclic Redundancy Check through P-RNTI configured for vertical paging to receive vertical paging signals. If the CRC is successfully performed through P-RNTI, the terminal can determine it as a short message for general paging signals and decode it (2g-15). A message received via a scheduled PDSCH in a DCI where the CRC was successful via P-RNTI can be determined as a general paging message and decoded (2g-15). If the CRC was successfully performed via P-RNTI configured vertical paging, the terminal can determine it as a short message for vertical paging signals and decode it (2g-20). If the CRC was successfully performed via P-RNTI configured vertical paging, a message received via a scheduled PDSCH in a DCI can be determined as a paging message for vertical paging signals and decoded (2g-20).

[0240] FIG. 2h is a block diagram illustrating the structure of a terminal according to one embodiment of the present disclosure.

[0241] The terminal may include a radio frequency (RF) processing unit (2h-10), a baseband processing unit (2h-20), a storage unit (2h-30), and a control unit (2h-40).

[0242] A terminal according to one embodiment of the present disclosure can perform operations to implement the above-described embodiment with reference to FIGS. 1a to 2g.

[0243] An RF processing unit (2h-10) according to one embodiment of the present disclosure can perform functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (2h-10) can up-convert a baseband signal provided by a baseband processing unit (2h-20) into an RF band signal and transmit it through an antenna, and down-convert an RF band signal received through an antenna into a baseband signal. For example, the RF processing unit (2h-10) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), etc.

[0244] In FIG. 2h, only one antenna is shown, but the terminal may include multiple antennas.

[0245] Additionally, the RF processing unit (2h-10) may include multiple RF chains. Furthermore, the RF processing unit (2h-10) may perform beamforming. For beamforming, the RF processing unit (2h-10) may adjust the phase and magnitude of each of the signals transmitted and received through multiple antennas or antenna elements. Additionally, the RF processing unit (2h-10) may perform MIMO (Multiple-Input Multiple-Output) and may receive multiple layers when performing MIMO operation. The RF processing unit (2h-10) may perform receiving beam sweeping by appropriately setting multiple antennas or antenna elements according to the control of the control unit (2h-40), or adjust the direction and beam width of the receiving beam so that the receiving beam is coordinated with the transmitting beam.

[0246] The baseband processing unit (2h-20) can perform conversion functions between baseband signals and bit sequences according to the physical layer specifications of the system. For example, when transmitting data, the baseband processing unit (2h-20) can generate complex symbols by encoding and modulating the transmitted bit sequence. Additionally, when receiving data, the baseband processing unit (2h-20) can restore the received bit sequence through demodulation and decoding of the baseband signal provided by the RF processing unit (2h-10). For example, in the case of following the orthogonal frequency division multiplexing (OFDM) method, when transmitting data, the baseband processing unit (2h-20) can generate complex symbols by encoding and modulating the transmitted bit sequence, map the complex symbols to subcarriers, and then construct OFDM symbols through inverse fast Fourier transform (IFFT) operations and cyclic prefix (CP) insertion. Additionally, upon receiving data, the baseband processing unit (2h-20) can divide the baseband signal provided by the RF processing unit (2h-10) into OFDM symbol units, restore the signals mapped to subcarriers through a fast Fourier transform (FFT) operation, and then restore the received bit sequence through demodulation and decoding.

[0247] The baseband processing unit (2h-20) and the RF processing unit (2h-10) can transmit and receive signals as described above. Accordingly, the baseband processing unit (2h-20) and the RF processing unit (2h-10) may be referred to as a transmitting unit, a receiving unit, a transmitting and receiving unit, or a communication unit. Furthermore, at least one of the baseband processing unit (2h-20) and the RF processing unit (2h-10) may include a plurality of communication modules to support a plurality of different wireless access technologies. Additionally, at least one of the baseband processing unit (2h-20) and the RF processing unit (2h-10) may include different communication modules to process signals of different frequency bands. For example, different wireless access technologies may include LTE networks, NR networks, etc. In addition, different frequency bands may include super high frequency (SHF) bands (e.g., 2.2 GHz, 2 GHz) and millimeter wave (e.g., 60 GHz) bands.

[0248] The storage unit (2h-30) can store data such as basic programs, application programs, and setting information for the operation of the terminal. The storage unit (2h-30) can provide the stored data upon request from the control unit (2h-40).

[0249] The control unit (2h-40) can control the overall operations of the terminal. For example, the control unit (2h-40) can transmit and receive signals through the baseband processing unit (2h-20) and the RF processing unit (2h-10). Additionally, the control unit (2h-40) can write and read data to and from the storage unit (2h-40). To this end, the control unit (2h-40) may include at least one processor. For example, the control unit (2h-40) may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as applications. Additionally, the control unit (2h-40) according to one embodiment may include a multiple connection processing unit (2h-42).

[0250] FIG. 2i is a block diagram illustrating the structure of a base station according to one embodiment of the present disclosure.

[0251] A base station according to one embodiment of the present disclosure may include one or more transmission reception points (TRPs).

[0252] A base station according to one embodiment of the present disclosure may include an RF processing unit (2i-10), a baseband processing unit (2i-20), a communication unit (2i-30), a storage unit (2i-40), and a control unit (2i-50).

[0253] A base station according to the present disclosure can perform operations to implement the above-described embodiment with reference to FIGS. 1a to 2g.

[0254] The RF processing unit (2i-10) can perform functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (2i-10) can up-convert a baseband signal provided by the baseband processing unit (2i-20) into an RF band signal and transmit it through an antenna, and down-convert an RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (2i-10) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc.

[0255] In FIG. 2i, only one antenna is shown, but the base station may include multiple antennas.

[0256] Additionally, the RF processing unit (2i-10) may include a plurality of RF chains. Furthermore, the RF processing unit (2i-10) may perform beamforming. For beamforming, the RF processing unit (2i-10) may adjust the phase and magnitude of each of the signals transmitted and received through a plurality of antennas or antenna elements. The RF processing unit (2i-10) may perform down-MIMO operation by transmitting one or more layers.

[0257] The baseband processing unit (2i-20) can perform a conversion function between a baseband signal and a bit sequence according to the physical layer specifications of the first wireless access technology. For example, when transmitting data, the baseband processing unit (2i-20) can generate complex symbols by encoding and modulating the transmitted bit sequence. Additionally, when receiving data, the baseband processing unit (2i-20) can restore the received bit sequence through demodulation and decoding of the baseband signal provided by the RF processing unit (2i-10). For example, in the case of an OFDM method, when transmitting data, the baseband processing unit (2i-20) can generate complex symbols by encoding and modulating the transmitted bit sequence, map the complex symbols to subcarriers, and then construct OFDM symbols through IFFT operation and CP insertion. Additionally, upon receiving data, the baseband processing unit (2i-20) can divide the baseband signal provided by the RF processing unit (2i-10) into OFDM symbol units, restore the signals mapped to subcarriers through FFT operations, and then restore the received bit sequence through demodulation and decoding. The baseband processing unit (2i-20) and the RF processing unit (2i-10) can transmit and receive signals as described above.

[0258] Accordingly, the baseband processing unit (2i-20) and the RF processing unit (2i-10) may be referred to as a transmitting unit, a receiving unit, a transmitting and receiving unit, a communication unit, or a wireless communication unit.

[0259] The communication unit (2i-30) can provide an interface for communicating with other nodes within the network. That is, the communication unit (2i-30) can convert a bit sequence transmitted from the main base station to other nodes, such as an auxiliary base station or a core network, into a physical signal, and can convert a physical signal received from other nodes into a bit sequence.

[0260] The storage unit (2i-40) can store data such as basic programs, application programs, and configuration information for the operation of the base station. In particular, the storage unit (2i-40) can store information regarding a bearer assigned to a connected terminal, measurement results reported from the connected terminal, etc. Additionally, the storage unit (2i-40) can store information that serves as a criterion for determining whether to provide or disconnect multiple connections to the terminal. Furthermore, the storage unit (2i-40) can provide the stored data upon a request from the control unit (2i-50).

[0261] The control unit (2i-50) can control the overall operations of the base station. For example, the control unit (2i-50) can transmit and receive signals through the baseband processing unit (2i-20) and the RF processing unit (2i-10) or through the communication unit (2i-30). Additionally, the control unit (2i-50) can write and read data to and from the storage unit (2i-40). To this end, the control unit (2i-50) may include at least one processor. Furthermore, the control unit (2i-50) according to one embodiment may include a multiple connection processing unit (2i-52).

[0262] FIG. 3e is a diagram illustrating a procedure in which a terminal performs an RRC connection establishment procedure with a base station to switch from an RRC idle mode to an RRC connected mode according to one embodiment of the present disclosure, and a procedure in which the base station and the terminal perform an RRC reconfiguration procedure.

[0263] Referring to FIG. 3e, a terminal (3e-01) may be in an RRC connected mode (RRC_CONNECTED) by establishing an RRC connection with a base station (3e-02) (3e-05). If the terminal transmitting and receiving data in the RRC connected mode does not transmit or receive data for a certain reason or for a certain period of time, the base station may cause the terminal to switch to an RRC idle mode (RRC_IDLE) by transmitting an RRC disconnection message (RRCRelease message) that does not include suspend configuration information (suspendConfig) (3e-10). In the RRC idle mode, the terminal may find a suitable cell and camp on it through a cell selection procedure and / or a cell re-selection procedure to receive system information (3e-15).

[0264] The terminal (3e-01) can perform a random access procedure to establish an RRC connection with the base station (3e-02). When the random access is triggered (3e-16), the terminal can select a PRACH occasion and transmit a random access preamble to the base station (3e-20). Upon receiving the random access preamble, the base station can transmit a random access response (hereinafter RAR) message to the terminal (3e-25). The terminal (3e-01) in RRC idle mode can establish reverse transmission synchronization with the base station (3e-02) through steps 3e-20 and 3e-25.

[0265] A terminal (3e-01) in an RRC idle mode that has established reverse transmission synchronization can perform an RRC connection establishment procedure with a base station (3e-02). First, the terminal can send an RRC connection establishment request message to the base station (3e-30). The message may include the terminal's identifier (ue-Identity) and the reason for establishing the RRC connection (establishmentCause). Upon receiving the RRC connection establishment request message, the base station can send an RRC connection establishment message to the terminal (3e-35). The message may include radio bearer configuration information and master cell group configuration information. Specifically, the wireless bearer configuration information and master cell group configuration information may include information involving an SRB1 (signaling radio bearer1) connection, RLC bearer configuration information for SRB1, MAC cell group configuration information (mac-CellGroupConfig), physical cell group configuration information (physicalCellGroupConfig), etc. That is, the establishment of an RRC connection may involve an SRB1 connection and may not involve other wireless bearer connections excluding SRB1 (for example, it does not involve an SRB2 for transmitting and receiving NAS messages between the terminal and the base station or a DRB (Data Radio Bearer) connection for transmitting and receiving data). When an RRC connection configuration message is received, the terminal may apply the above information and switch to an RRC connection mode (3e-36). The terminal that has switched to an RRC connection mode may transmit an RRC connection setup completion message (RRCSetupComplete message) to the base station via SRB1 (3e-40).The message may include a service request message in which the terminal requests the AMF or MME to set up a bearer for a specific service.

[0266] When the RRC connection establishment procedure is successfully performed, the base station (3e-02) can send a security mode command message to the terminal (3e-01) in RRC connection mode to activate AS Security (3e-45). When the terminal receives the security mode command message, it can send a security mode complete message to the base station (3e-50).

[0267] The base station (3e-02) may perform an RRC reconfiguration procedure with the terminal (3e-01) when transmitting a security mode command message, after transmitting the security mode command message, or after receiving the security mode completion message. First, the base station may transmit an RRC reconfiguration message to the terminal (3e-55). The message may include some or all of the following information.

[0268] - Directive (fullConfig) indicating whether to apply full configuration information

[0269] - Radio Bearer Configuration Information (radioBearerConfig): radioBearerConfig may include at least one of the following information.

[0270] * List of SRBs to add or modify (srb-ToAddModList):

[0271] srb-ToAddModList contains one or more SRB setting information (SRB-ToAddMod).

[0272] Each SRB-ToAddMod may include an SRB identifier (srb-Identity), an indicator indicating whether to re-establish PDCP (reestablishmentPDCP), an indicator indicating whether to discard Service Data Units (SDU) and Protocol Data Units (PDU) stored in the terminal, or PDCP configuration information (pdcp-Config).

[0273] * Indicator for whether to release SRB3 (srb3-ToRelease): SRB3 can be released only through SRB1, and SRB3 can be released only when releasing a Secondary Cell Group (hereinafter SCG) configured for the terminal and / or by reconfiguration with sync.

[0274] * List of DRBs to be added or modified (drb-ToAddModList): drb-ToAddModList may contain one or more DRB configuration information (DRB-ToAddMod), and each DRB-ToAddMod may contain a DRB identifier (drb-Identity), an indicator indicating whether to re-establish PDCP (reestablishmentPDCP), an indicator indicating whether PDCP will perform a recovery procedure (recoverPDCP), PDCP configuration information (pdcp-Config), or information indicating whether the bearer is associated with eps-bearerIdentity or SDAP configuration information (sdapConfig) (cnAssociation). cnAssociation may include eps-BearerIdentity if connected to EPC and sdap-Config if connected to 5GC.

[0275] * List of DRBs to be released (drb-ToReleaseList): drbToReleaseList may include one or more DRB identifiers (DRBIdentity) to be released.

[0276] * Security configuration information (securityConfig): securityConfig may include information indicating whether to use a master key (key for Master Cell Group (hereinafter MCG)) or a secondary key (key for SCG) to derive a key for security algorithm configuration information (SecurityAlgorithmConfig) or for ciphering and / or integrity protection.

[0277] - Master cell group configuration information (masterCellGroup): masterCellGroupConfig may include at least one of the following information.

[0278] * Information that identifies a cell group (cellGroupId): CellGroupId can be indicated by a single value. For example, if indicated by 0, it may represent MCG, and if indicated by another value, it may represent SCGs.

[0279] * List of RLC bearer configuration information to be added or modified (rlc-BearerToAddModList): rlc-BearerToAddModList may contain one or more RLC bearer configuration information (RLC-BearerConfig), and each RLC-BearerConfig may contain a logical channel identifier (logicalChannelIdentity), an SRB identifier (srb-Idendity) or DRB identifier (drb-Identity) associated with the RLC bearer, an indicator indicating whether the RLC should be reestablished (reestablishRLC), RLC configuration information (rlc-Config), or a MAC-logical channel configuration information (mac-LogicalChannelConfig) containing logical channel information.

[0280] * List of RLC bearer configuration information to be released (rlcBearerToReleaseList): May include one or more logicalChannelIdentities associated with the RLC bearer to be released.

[0281] MAC Cell Group Configuration Information (mac-CellGroupConfig)

[0282] * PHYSICAL cell group configuration information (physical-CellGroupConfig)

[0283] * Configuration information for SpCell (spCellConfig): spCellConfig may include an index (servCellIndex) that can identify the SpCell (meaning Primary Cell (PCell) of MCG or Primary SCG Cell (PSCell) of SCG), parameters for synchronous reconfiguration in the target SpCell (reconfigurationWithSync), information on whether to set or disable parameters containing timer values ​​and constant values ​​for detecting and triggering cell-level wireless link failure (rlf-TimerAndConstants), rlmInSyncOutOfSyncThreshold, or spCellConfigDedicated.

[0284] List of SCell setting information to add or modify (sCellToAddModList)

[0285] * List of SCell settings to be released (sCellToReleaseList)

[0286] * Measurement configuration information (measConfig)

[0287] * Master Key configuration information to update (masterKeyUpdate): masterKeyUpdate may include keySetChangeIndicator, nextHopChainingCount, or nas Container. masterKeyUpdate must always be included when an RRC connection reconfiguration procedure is performed due to a handover that requires changing the security algorithm, and may be optionally included if ReconfigurationWithSync is included in other cases.

[0288] The above message may additionally include dedicatedNAS-MessageList, dedicatedSIB1-Delivery, dedicatedSystemInformationDelivery, or otherConfig. A terminal that receives an RRC connection reconfiguration message may apply the above information and then send an RRC connection reconfiguration complete message (RRCReconfigurationComplete message) to the base station (3e-60).

[0289] FIG. 3f is a diagram illustrating, according to one embodiment of the present disclosure, a procedure in which a terminal performs an RRC connection establishment procedure with a base station to switch from an RRC idle mode to an RRC connected mode, and a procedure in which a base station and a terminal perform an RRC reconfiguration procedure.

[0290] Referring to FIG. 3f, a terminal (3f-01) may be in an RRC connected mode (RRC_CONNECTED) by establishing an RRC connection with a base station (3f-02) (3f-05). If the terminal transmitting and receiving data in the RRC connected mode does not transmit or receive data for a certain reason or for a certain period of time, the base station may transmit an RRC disconnection message (RRCRelease message) including suspend configuration information (suspendConfig) to cause the terminal to switch to an RRC disabled mode (RRC_IDLE) (3f-10). In the RRC disabled mode, the terminal finds a suitable cell through a cell selection procedure and / or a cell re-selection procedure, camps on to the cell, and provides system information

[0291] It can be received (3f-15).

[0292] The terminal (3f-01) may perform a random access procedure to resume an RRC connection with the base station (3f-02). When random access is triggered (3f-16), the terminal may select a PRACH occasion and transmit a random access preamble to the base station (3f-20). Upon receiving the random access preamble, the base station may transmit a random access response (RAR) message to the terminal (3f-25). The terminal (3f-01), which is in an RRC disabled mode, may establish a reverse transmission synchronization with the base station (3f-02) through steps 3f-20 and 3f-25.

[0293] A terminal (3f-01) in an RRC disabled mode that has established reverse transmission synchronization can perform an RRC connection resume procedure with a base station (3f-02). First, the terminal can transmit an RRC connection resume request message or an RRC connection resume request 1 message to the base station (3f-30). The RRC connection resume request message or the RRC connection resume request 1 message may include the terminal's identifier (resumeIdentity) for reclaiming the terminal context from the base station, resume encryption information (resumeMAC-I), and the reason for resuming the RRC connection (resumeCause). Upon receiving the RRC connection resume request message or the RRC connection resume request 1 message, the base station can transmit an RRC connection resume message (RRCResume message) to the terminal (3f-35). The message may include radio bearer configuration information (radioBearerConfig), master cell group configuration information (masterCellGroup), measurement configuration information (measConfig), etc. Specifically, the radio bearer configuration information and master cell group configuration information may include configuration information for one or more signaling radio bearers (SRBs) to be resumed, configuration information for one or more data radio bearers (DRBs), RLC bearer configuration information, MAC cell group configuration information (mac-CellGroupConfig), physical cell group configuration information (physicalCellGroupConfig), etc. When an RRC connection resumption message is received, the terminal may apply the above information and switch to RRC connection mode (2f-36).A terminal that has switched to RRC connection mode can send an RRC connection resumption completion message (RRCResumeComplete message) to the base station via SRB1 (2f-40).

[0294] If the RRC connection resumption procedure is successfully performed, the base station (3f-02) may send a security mode command message to the terminal (3f-01) in RRC connection mode to activate AS Security (3f-45). Upon receiving the security mode command message, the terminal may send a security mode complete message to the base station (3f-50).

[0295] The base station (3f-02) may perform an RRC reconfiguration procedure with the terminal (3f-01) when transmitting a security mode command message, after transmitting the security mode command message, or after receiving the security mode completion message. First, the base station may transmit an RRC reconfiguration message to the terminal (3f-55). The message may include some or all of the following information.

[0296] - Directive (fullConfig) indicating whether to apply full configuration information

[0297] - Radio Bearer Configuration Information (radioBearerConfig): radioBearerConfig may include at least one of the following information.

[0298] * SRB list to be added or modified (srb-ToAddModList): srb-ToAddModList may include one or more SRB configuration information (SRB-ToAddMod), and each SRB-ToAddMod may include an SRB identifier (srb-Identity), an indicator (reestablishmentPDCP) indicating whether to re-establish PDCP, an indicator indicating whether to discard Service Data Units (SDU) and Protocol Data Units (PDU) stored in the terminal, or PDCP configuration information (pdcp-Config).

[0299] * Indicator for whether to release SRB3 (srb3-ToRelease): SRB3 can be released only through SRB1, and SRB3 can be released only when releasing a Secondary Cell Group (hereinafter SCG) configured for the terminal and / or by reconfiguration withsync.

[0300] * List of DRBs to be added or modified (drb-ToAddModList): drb-ToAddModList may contain one or more DRB configuration information (DRB-ToAddMod), and each DRB-ToAddMod may contain a DRB identifier (drb-Identity), an indicator indicating whether to re-establish PDCP (reestablishmentPDCP), an indicator indicating whether PDCP will perform a recovery procedure (recoverPDCP), PDCP configuration information (pdcp-Config), or information indicating whether the bearer is associated with eps-bearerIdentity or SDAP configuration information (sdapConfig) (cnAssociation). cnAssociation may include eps-BearerIdentity if connected to EPC and sdap-Config if connected to 5GC.

[0301] * List of DRBs to be released (drb-ToReleaseList): drbToReleaseList contains one or more DRB identifiers (DRB) to be released

[0302] Identity) may be included.

[0303] * Security configuration information (securityConfig): securityConfig may include information indicating whether to use a master key (key for Master Cell Group (hereinafter MCG)) or a secondary key (key for SCG) to derive a key for security algorithm configuration information (SecurityAlgorithmConfig) or for ciphering and / or integrity protection.

[0304] - Master Cell Group Configuration Information (masterCellGroup): masterCellGroupConfig may include at least one of the following information.

[0305] * Information that identifies a cell group (cellGroupId): CellGroupId can be indicated by a single value. For example, if indicated by 0, it may represent MCG, and if indicated by another value, it may represent SCGs.

[0306] * List of RLC bearer configuration information to be added or modified (rlc-BearerToAddModList): rlc-BearerToAddModList may contain one or more RLC bearer configuration information (RLC-BearerConfig), and each RLC-BearerConfig may contain a logical channel identifier (logicalChannelIdentity), an SRB identifier (srb-Idendity) or DRB identifier (drb-Identity) associated with the RLC bearer, an indicator indicating whether the RLC should be reestablished (reestablishRLC), RLC configuration information (rlc-Config), or MAC-LogicalChannelConfig containing logical channel information.

[0307] * List of RLC bearer configuration information to be released (rlcBearerToReleaseList): May include one or more logicalChannelIdentities associated with the RLC bearer to be released.

[0308] MAC Cell Group Configuration Information (mac-CellGroupConfig)

[0309] * PHYSICAL cell group configuration information (physical-CellGroupConfig)

[0310] * Configuration information for SpCell (spCellConfig): spCellConfig may include an index (servCellIndex) that can identify the SpCell (meaning Primary Cell (PCell) of MCG or Primary SCG Cell (PSCell) of SCG), parameters for synchronous reconfiguration in the target SpCell (reconfigurationWithSync), information on whether to set or disable parameters containing timer values ​​and constant values ​​for detecting and triggering cell-level wireless link failure (rlf-TimerAndConstants), rlmInSyncOutOfSyncThreshold, or spCellConfigDedicated.

[0311] List of SCell setting information to add or modify (sCellToAddModList)

[0312] * List of SCell settings to be released (sCellToReleaseList)

[0313] * Measurement configuration information (measConfig)

[0314] * Master Key configuration information to update (masterKeyUpdate): masterKeyUpdate may include keySetChangeIndicator, nextHopChainingCount, or nas Container. masterKeyUpdate must always be included when an RRC connection reconfiguration procedure is performed due to a handover that requires changing the security algorithm, and may be optionally included if ReconfigurationWithSync is included in other cases.

[0315] The above message may additionally include dedicatedNAS-MessageList, dedicatedSIB1-Delivery, dedicatedSystemInformationDelivery, or otherConfig. A terminal that receives an RRC connection reconfiguration message may apply the above information and then send an RRC connection reconfiguration completion message (RRCReconfigurationComplete message) to the base station (3f-60).

[0316] FIG. 3g is a flowchart of a terminal operation according to a condition in which a wireless bearer setting is instructed when a terminal in RRC connection mode (RRC_CONNECTED) receives an RRCReconfiguration message from a base station in accordance with one embodiment of the present disclosure.

[0317] In step 3g-05, a terminal in RRC idle mode (RRC_IDLE) or RRC disabled mode (RRC_INACTIVE) can receive an RRCSetup message from the base station.

[0318] In the 3g-10 stage, the terminal can set up SRB1 by applying the received RRCSetup message. Then, the terminal can transition to an RRC connection mode. In one embodiment, when SRB2 is not set and only SRB1 is set, the base station and the terminal can transmit and receive NAS messages by including them in the RRC message through SRB1. In another embodiment, when SRB2 is not set and only SRB1 is set, the terminal transmits MDT-related information to the base station through SRB1.

[0319] A terminal that has transitioned to RRC connection mode in the 3g-15 stage can receive an RRCReconfiguration message from the base station.

[0320] In the 3g-20 stage, the terminal can determine whether one of the a, b, or c events described below has occurred based on the received RRCReconfiguration message.

[0321] - Event a: When SRB2 and DRB settings are instructed

[0322] - Event b: When only DRB is set

[0323] - My c event: When only SRB2 is set

[0324] When the base station instructs the above SRB2, the terminal sets up SRB2, and up to one can be set. When the base station instructs the above DRB, the terminal sets up DRB, and up to n can be set.

[0325] If it is determined that event c has occurred in step 3g-20, the terminal may initiate an operation to transition to an RRC idle mode state in step 3g-25. When initiating the operation to transition to an RRC idle mode state, if security is not enabled, the terminal may set the release cause to 'other' and not perform the NAS Recovery procedure. When initiating the operation to transition to an RRC idle mode state, if AS security is enabled, the terminal may set the release cause to 'RRC connection failure' and perform the NAS Recovery procedure.

[0326] If it is determined that the a or b event has occurred in step 3g-20, in step 3g-30, the terminal can determine whether one of the first event, the second event, the third event, or the fourth event described below has occurred.

[0327] - Event 1: If the received RRCReconfiguration includes reconfigurationWithSync and security is enabled

[0328] - Event 2: If the received RRCReconfiguration includes reconfigurationWithSync and security is not enabled

[0329] - 3rd Event: If some or all settings instructed in the received RRCReconfiguration message cannot be performed and security is enabled

[0330] - Event 4: If some or all settings instructed in the received RRCReconfiguration message cannot be performed and security is not enabled

[0331] If the terminal cannot perform some or all settings as instructed in the RRCReconfiguration message received (3rd event, 4th event), it may be considered a Reconfiguration failure. If the terminal cannot perform some or all settings as instructed in the RRCReconfiguration message received, the terminal may continue to use the configuration information it was using before receiving the RRCReconfiguration message.

[0332] If it is determined that the first event has occurred in step 3g-30, the terminal may perform an RRCReconfiguration operation in step 3g-35. For example, the terminal may transmit an RRCReconfigurationComplete message to the base station. In one embodiment, when an RRCReconfiguration message containing content corresponding to the b-th event is received, the terminal checks whether reconfigurationWithSync is included in the received RRCReconfiguration message and checks whether security is enabled. If reconfigurationWithSync is included in the received RRCReconfiguration message and security is enabled, the terminal may perform an RRCReconfiguration operation and transmit an RRCReconfigurationComplete message to the base station.

[0333] If it is determined that a second event has occurred in step 3g-30, the terminal may initiate an operation to transition to an RRC idle mode state in step 3g-40. When initiating the operation to transition to an RRC idle mode state, the release cause for releasing the RRC connection may be set to 'other' and the NAS Recovery procedure may not be performed.

[0334] In one embodiment, when a terminal receives an RRCReconfiguration message containing content corresponding to event b, the terminal checks whether reconfigurationWithSync is included in the received RRCReconfiguration message and checks whether security is enabled. If reconfigurationWithSync is included in the received RRCReconfiguration message and security is not enabled, the terminal can perform a transition operation to the RRC IDLE state.

[0335] If it is determined that a third event has occurred in step 3g-30, the terminal may initiate an RRC connection re-establishment procedure to the base station in step 3g-45. In one embodiment, if an RRCReconfiguration message containing content corresponding to event b is received, the terminal checks whether it is possible to perform some or all of the specified settings among the settings included in the received RRCReconfiguration message. If it is determined that at least some of the settings included in the received RRCReconfiguration message cannot be set and security is enabled, the terminal may perform an RRCReconfiguration operation and initiate an RRC connection re-establishment procedure by sending an RRCReconfigurationComplete message to the base station.

[0336] If it is determined that the fourth event has occurred in step 3g-30, the terminal may initiate an operation to transition to an RRC idle mode state in step 3g-50. When initiating the operation to transition to an RRC idle mode state, the release cause for releasing the RRC connection may be set to 'other', and the NAS Recovery procedure may not be performed. In one embodiment, if an RRCReconfiguration message containing content corresponding to the b-th event is received, the terminal checks whether it can perform some or all of the specified settings among the settings included in the received RRCReconfiguration message. If it is determined that at least some of the settings included in the received RRCReconfiguration message cannot be set and security is not enabled, the terminal may perform an operation to transition to an RRC IDLE state.

[0337] FIG. 3h is a flowchart of the operation of a terminal according to a pre-configured wireless bearer setting when a terminal in RRC connection mode (RRC_CONNECTED) receives an RRCRelease message containing suspend configuration information (suspendConfig) from a base station according to one embodiment of the present disclosure.

[0338] In step 3h-05, a terminal in RRC idle mode (RRC_IDLE) or RRC disabled mode (RRC_INACTIVE) can receive an RRCSetup message from the base station.

[0339] In step 3h-10, the terminal can configure SRB1 by applying the received RRCSetup message. The terminal can then transition to an RRC connection mode. In one embodiment, when SRB2 is not configured and only SRB1 is configured, the base station and the terminal can transmit and receive NAS messages by including them in an RRC message through SRB1. In another embodiment, when SRB2 is not configured and only SRB1 is configured, the terminal transmits MDT-related information to the base station through SRB1.

[0340] After performing steps 3h-10, the terminal that transitioned to RRC connection mode may receive an RRCRelease message from the base station that does not include suspendConfig in steps 3h-15.

[0341] In step 3h-20, the terminal may initiate an operation to transition to an RRC idle mode. When initiating the operation to transition to an RRC idle mode, if security is not enabled, the terminal may set the release cause to 'other' and not perform the NAS Recovery procedure. When initiating the operation to transition to an RRC idle mode, if AS security is enabled, the terminal may set the release cause to 'RRC connection failure' and perform the NAS Recovery procedure.

[0342] Alternatively, the terminal that transitioned to RRC connection mode after performing step 3h-10 may receive an RRCReconfiguration message from the base station in step 3h-25.

[0343] In step 3h-30, the terminal can determine whether one of the a, b, or c events described below has occurred based on the received RRCReconfiguration message.

[0344] - Event a: When SRB2 and DRB settings are instructed

[0345] - Event b: When only DRB is set

[0346] - My c event: When only SRB2 is set

[0347] When the base station instructs the above SRB2, the terminal sets up SRB2, and up to one can be set. When the base station instructs the above DRB, the terminal sets up DRB, and up to n can be set.

[0348] If it is determined that event c has occurred in step 3h-30, the terminal may initiate an operation to transition to an RRC idle mode state in step 3h-35. When initiating the operation to transition to an RRC idle mode state, if security is not enabled, the terminal may set the release cause to 'other' and not perform the NAS Recovery procedure. When initiating the operation to transition to an RRC idle mode state, if AS security is enabled, the terminal may set the release cause to 'RRC connection failure' and perform the NAS Recovery procedure.

[0349] If it is determined that event a or event b has occurred in step 3h-30, in step 3h-40, the terminal may receive an RRCRelease message containing suspendConfig from the base station.

[0350] In step 3h-45, if the terminal receives an RRCRelease message containing suspendConfig while it is determined that event a or event b has occurred, the terminal may transition to the RRC_INACTIVE state. In one embodiment, after receiving an RRCReconfiguration message containing content corresponding to event b and setting the DRB accordingly, the terminal checks whether suspendConfig is included in the message when it receives an RRCRelease message. If, upon receiving the RRCRelease message, suspendConfig is included in the message, the terminal may perform a transition operation to the RRC INACTIVE state.

[0351] In step 3h-50, the terminal may initiate an RRC connection resume procedure if it receives a message from the base station regarding instructions to perform an RRC connection resume, or if the terminal determines that an RRC connection resume process is necessary.

[0352] FIG. 3i is a flowchart of the operation of a terminal according to a set radio bearer when a terminal in RRC connection mode (RRC_CONNECTED) detects a radio link failure (hereinafter RLF) according to one embodiment of the present disclosure.

[0353] In step 3i-05, a terminal in RRC idle mode (RRC_IDLE) or RRC disabled mode (RRC_INACTIVE) can receive an RRCSetup message from the base station.

[0354] In step 3i-10, the terminal can configure SRB1 by applying the received RRCSetup message. The terminal can then transition to an RRC connection mode. In one embodiment, when SRB2 is not configured and only SRB1 is configured, the base station and the terminal can transmit and receive NAS messages by including them in an RRC message through SRB1. In another embodiment, when SRB2 is not configured and only SRB1 is configured, the terminal transmits MDT-related information to the base station through SRB1.

[0355] After performing step 3i-10, if the terminal that has transitioned to RRC connection mode detects RLF, the terminal may initiate an operation to transition to an RRC idle mode state in step 3i-15. When initiating the operation to transition to an RRC idle mode state, if security is not enabled, the terminal may set the release cause to 'other' and not perform the NAS Recovery procedure.

[0356] When initiating an operation to transition to the RRC idle mode state, if AS security is enabled, the terminal may set the reason for disconnecting the RRC connection as 'RRC connection failure' and perform the NAS Recovery procedure.

[0357] Alternatively, the terminal that transitioned to RRC connection mode after performing step 3i-10 may receive an RRCReconfiguration message from the base station in step 3i-20.

[0358] In step 3i-25, the terminal can determine whether one of the a, b, or c events described below has occurred based on the received RRCReconfiguration message.

[0359] - Event a: When SRB2 and DRB settings are instructed

[0360] - Event b: When only DRB is set

[0361] - My c event: When only SRB2 is set

[0362] When the base station instructs the above SRB2, the terminal sets up SRB2, and up to one can be set. When the base station instructs the above DRB, the terminal sets up DRB, and up to n can be set.

[0363] If it is determined that the c event has occurred in step 3i-25, the terminal may initiate an operation to transition to an RRC idle mode state in step 3i-30. When initiating the operation to transition to an RRC idle mode state, if security is not enabled, the terminal may set the release cause to 'other' and not perform the NAS Recovery procedure. When initiating the operation to transition to an RRC idle mode state, if AS security is enabled, the terminal may set the release cause to 'RRC connection failure' and perform the NAS Recovery procedure.

[0364] If RLF is detected in step 3i-25 and it is determined that the a-th event or the b-th event has occurred, in step 3i-35 the terminal can determine whether the first event or the second event described below has occurred.

[0365] - Event 1: If security is not enabled

[0366] - Event 2: When security is enabled

[0367] If RLF is detected in step 3i-35 and it is determined that the first event has occurred, in step 3i-40, the terminal may initiate an RRC connection reestablishment procedure to the base station.

[0368] If an RLF is detected in step 3i-35, or if it is determined that a second event has occurred, the terminal may initiate an operation to transition to an RRC idle mode state in step 3i-45. When initiating the operation to transition to an RRC idle mode state, the release cause for releasing the RRC connection may be set to 'other', and the NAS Recovery procedure may not be performed.

[0369] FIG. 3j illustrates the structure of a terminal according to one embodiment of the present disclosure.

[0370] According to one embodiment of the present disclosure, the terminal may include an RF (Radio Frequency) processing unit (3j-10), a baseband processing unit (3j-20), a storage unit (3j-30), and a control unit (3j-40).

[0371] According to one embodiment of the present disclosure, the RF processing unit (3j-10) can perform functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification.

[0372] That is, the RF processing unit (3j-10) can up-convert a baseband signal provided by the baseband processing unit (3j-20) into an RF band signal and transmit it through an antenna, and down-convert an RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (3j-10) includes a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC (digital to analog converter), an ADC (analog to digital converter), etc.

[0373] You can do it.

[0374] In the drawing, only one antenna is shown, but the terminal may be equipped with multiple antennas.

[0375] Additionally, the RF processing unit (3j-10) may include multiple RF chains. Furthermore, the RF processing unit (3j-10) may perform beamforming. For beamforming, the RF processing unit (3j-10) may adjust the phase and magnitude of each of the signals transmitted and received through multiple antennas or antenna elements. Additionally, the RF processing unit may perform MIMO and may receive multiple layers when performing MIMO operation. The RF processing unit (3j-10) may perform receiving beam sweeping by appropriately setting multiple antennas or antenna elements according to the control of the control unit, or adjust the direction and beam width of the receiving beam so that the receiving beam is coordinated with the transmitting beam.

[0376] The baseband processing unit (3j-20) can perform conversion functions between baseband signals and bit sequences according to the physical layer specifications of the system. For example, when transmitting data, the baseband processing unit (3j-20) can generate complex symbols by encoding and modulating the transmitted bit sequence. Additionally, when receiving data, the baseband processing unit (3j-20) can restore the received bit sequence by demodulating and decoding the baseband signal provided by the RF processing unit (3j-10). For example, in the case of following the orthogonal frequency division multiplexing (OFDM) method, when transmitting data, the baseband processing unit (3j-20) can generate complex symbols by encoding and modulating the transmitted bit sequence, map the complex symbols to subcarriers, and then construct OFDM symbols through inverse fast Fourier transform (IFFT) operations and cyclic prefix (CP) insertion. Additionally, when receiving data, the baseband processing unit (3j-20)

[0377] The baseband signal provided from the RF processing unit (3j-10) is divided into OFDM symbol units, and after restoring the signals mapped to subcarriers through a fast Fourier transform (FFT) operation, the received bit sequence can be restored through demodulation and decoding.

[0378] The baseband processing unit (3j-20) and the RF processing unit (3j-10) can transmit and receive signals as described above. Accordingly, the baseband processing unit (3j-20) and the RF processing unit (3j-10) may be referred to as a transmitting unit, a receiving unit, a transmitting and receiving unit, or a communication unit. Furthermore, at least one of the baseband processing unit (3j-20) and the RF processing unit (3j-10) may include a plurality of communication modules to support a plurality of different wireless access technologies. Additionally, at least one of the baseband processing unit (3j-20) and the RF processing unit (3j-10) may include different communication modules to process signals of different frequency bands. For example, different wireless access technologies may include LTE networks, NR networks, etc. In addition, different frequency bands may include super high frequency (SHF) bands (e.g., 2.2 GHz, 2 GHz) and millimeter wave (e.g., 60 GHz) bands.

[0379] The storage unit (3j-30) can store data such as basic programs, application programs, and setting information for the operation of the terminal. The storage unit (3j-30) can provide the stored data upon request from the control unit (3j-40).

[0380] The control unit (3j-40) can control the overall operations of the terminal. For example, the control unit (3j-40) can transmit and receive signals through the baseband processing unit (3j-20) and the RF processing unit (3j-10). Additionally, the control unit (3j-40) writes and reads data to and from the storage unit (3j-40). To this end, the control unit (3j-40) may include at least one processor. For example, the control unit (3j-40) may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as applications.

[0381] FIG. 3n is a block diagram (3n00) of an electronic device (3n001) for supporting legacy network communication and 5G network communication according to various embodiments. Referring to FIG. 3n, the electronic device (3n001) comprises a first communication processor (3n12), a second communication processor (3n14), a first radio frequency integrated circuit (RFIC) (3n22), a second RFIC (3n24), a third RFIC (3n26), a fourth RFIC (3n28), and a first radio frequency front

[0382] It may include an end (RFFE) (3n32), a second RFFE (3n34), a first antenna module (3n42), a second antenna module (3n44), and an antenna (3n48). The electronic device (3n001) may further include a processor (3n020) and a memory (3n030). The network (3n099) may include a first network (3n92) and a second network (3n94). According to another embodiment, the electronic device (3n001) may further include at least one of the components described in FIG. 3n0, and the network (3n099) may further include at least one other network. According to one embodiment,

[0383] The first communication processor (3n12), the second communication processor (3n14), the first RFIC (3n22), the second RFIC (3n24), the fourth RFIC (3n28), the first RFFE (3n32), and the second RFFE (3n34) may form at least a part of the wireless communication module (3n092). According to another embodiment, the fourth RFIC (3n28) may be omitted or included as part of the third RFIC (3n26).

[0384] The first communication processor (3n12) can establish a communication channel in a band to be used for wireless communication with the first network (3n92), and support legacy network communication through the established communication channel. According to various embodiments, the first network may be a legacy network including a second-generation (2G), 3G, 4G, or long-term evolution (LTE) network. The second communication processor (3n14) can establish a communication channel corresponding to a designated band (e.g., about 6 GHz to about 60 GHz) among the bands to be used for wireless communication with the second network (3n94), and support 5G network communication through the established communication channel. According to various embodiments, the second network (3n94) may be a 5G network as defined by 3GPP. Additionally, according to one embodiment, the first communication processor (3n12) or the second communication processor (3n14) may support the establishment of a communication channel corresponding to another designated band (e.g., about 6 GHz or less) among the bands to be used for wireless communication with the second network (3n94), and 5G network communication through the established communication channel. According to one embodiment, the first communication processor (3n12) and the second communication processor (3n14) may be implemented within a single chip or a single package. According to various embodiments, the first communication processor (3n12) or the second communication processor (3n14) may be formed within a single chip or a single package with the processor (3n020), the auxiliary processor (3n023), or the communication module (3n090).

[0385] The first RFIC (3n22) can convert a baseband signal generated by the first communication processor (3n12) during transmission into a radio frequency (RF) signal of about 700 MHz to about 3 GHz used in the first network (3n92) (e.g., legacy network). During reception, the RF signal is acquired from the first network (3n92) (e.g., legacy network) through an antenna (e.g., first antenna module (3n42)) and can be preprocessed through an RFFE (e.g., first RFFE (3n32)). The first RFIC (3n22) can convert the preprocessed RF signal into a baseband signal so that it can be processed by the first communication processor (3n12).

[0386] The second RFIC (3n24) can convert a baseband signal generated by the first communication processor (3n12) or the second communication processor (3n14) into an RF signal of the Sub6 band (e.g., about 6 GHz or less) used in the second network (3n94) (e.g., 5G network) (hereinafter, 5G Sub6 RF signal). When receiving, the 5G Sub6 RF signal is acquired from the second network (3n94) (e.g., 5G network) through an antenna (e.g., the second antenna module (3n44)) and can be preprocessed through an RFFE (e.g., the second RFFE (3n34)). The second RFIC (3n24) can convert the preprocessed 5G Sub6 RF signal into a baseband signal so that it can be processed by the corresponding communication processor among the first communication processor (3n12) or the second communication processor (3n14).

[0387] The third RFIC (3n26) can convert a baseband signal generated by the second communication processor (3n14) into an RF signal of the 5G Above6 band (e.g., approximately 6 GHz to approximately 60 GHz) (hereinafter, 5G Above6 RF signal) to be used in the second network (3n94) (e.g., 5G network). Upon reception, the 5G Above6 RF signal is acquired from the second network (3n94) (e.g., 5G network) through an antenna (e.g., antenna (3n48)) and can be preprocessed through the third RFFE (3n36). The third RFIC (3n26) can convert the preprocessed 5G Above6 RF signal into a baseband signal so that it can be processed by the second communication processor (3n14). According to one embodiment, the third RFFE (3n36) may be formed as part of the third RFIC (3n26).

[0388] According to one embodiment, the electronic device (3n001) may include a fourth RFIC (3n28) separately from or at least as part of the third RFIC (3n26). In this case, the fourth RFIC (3n28) may convert a baseband signal generated by the second communication processor (3n14) into an RF signal (hereinafter referred to as an IF signal) in an intermediate frequency band (e.g., about 9 GHz to about 13 GHz), and then transmit the IF signal to the third RFIC (3n26). The third RFIC (3n26) may convert the IF signal into a 5G Above6 RF signal. Upon reception, the 5G Above6 RF signal may be received from the second network (3n94) (e.g., a 5G network) through an antenna (e.g., antenna (3n48)) and converted into an IF signal by the third RFIC (3n26). The fourth RFIC (3n28) can convert the IF signal into a baseband signal so that the second communication processor (3n14) can process it.

[0389] According to one embodiment, the first RFIC (3n22) and the second RFIC (3n24) may be implemented as at least part of a single chip or a single package. According to one embodiment, the first RFFE (3n32) and the second RFFE (3n34) may be implemented as at least part of a single chip or a single package. According to one embodiment, at least one of the first antenna module (3n42) or the second antenna module (3n44) may be omitted or combined with another antenna module to process RF signals of a plurality of corresponding bands.

[0390] According to one embodiment, the third RFIC (3n26) and the antenna (3n48) may be placed on the same substrate to form a third antenna module (3n46). For example, a wireless communication module (3n092) or a processor (3n020) may be placed on the first substrate (e.g., main PCB). In this case, the third RFIC (3n26) may be placed on a portion of a second substrate (e.g., sub PCB) separate from the first substrate (e.g., bottom surface), and the antenna (3n48) may be placed on another portion of a second substrate (e.g., sub PCB) to form the third antenna module (3n46). According to one embodiment, the antenna (3n48) may include an antenna array that can be used for beamforming, for example. By placing the third RFIC (3n26) and the antenna (3n48) on the same substrate, it is possible to reduce the length of the transmission line between them. This can reduce the loss (e.g., attenuation) of signals in the high-frequency band (e.g., about 6 GHz to about 60 GHz) used for 5G network communication by the transmission line. As a result, the electronic device (3n001) can improve the quality or speed of communication with the second network (3n94) (e.g., 5G network).

[0391] It can cause injury.

[0392] The second network (3n94) (e.g., 5G network) may be operated independently of the first network (3n92) (e.g., legacy network) (e.g., Stand-Alone (SA)) or connected to it (e.g., Non-Stand Alone (NSA)). For example, the 5G network may only have an access network (e.g., 5G radio access network (RAN) or next generation RAN (NG RAN)) and no core network (e.g., next generation core (NGC)). In this case, the electronic device (3n001) can access the access network of the 5G network and then access an external network (e.g., the Internet) under the control of the core network of the legacy network (e.g., evolved packed core (EPC)). Protocol information for communication with a legacy network (e.g., LTE protocol information) or protocol information for communication with a 5G network (e.g., NR protocol information) is stored in memory (3n30) and can be accessed by other parts (e.g., processor (3n020), first communication processor (3n12), or second communication processor (3n14)).

[0393] FIG. 3k illustrates the structure of a base station according to one embodiment of the present disclosure. A base station according to one embodiment of the present disclosure may include one or more transmission reception points (TRPs).

[0394] A base station according to one embodiment of the present disclosure may be configured to include an RF processing unit (3k-10), a baseband processing unit (3k-20), a backhaul communication unit (3k-30), a storage unit (3k-40), and a control unit (3k-50).

[0395] The RF processing unit (3k-10) can perform functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (3k-10) can up-convert a baseband signal provided by the baseband processing unit (3k-20) into an RF band signal and transmit it through an antenna, and down-convert an RF band signal received through an antenna into a baseband signal. For example, the RF processing unit (3k-10) may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. Although only one antenna is shown in the drawing, the first connection node may be equipped with multiple antennas. Additionally, the RF processing unit (3k-10) may include multiple RF chains. Furthermore, the RF processing unit (3k-10) can perform beamforming. For beamforming, the RF processing unit (3k-10) can adjust the phase and magnitude of each of the signals transmitted and received through multiple antennas or antenna elements. The RF processing unit can perform down-to-down MIMO operation by transmitting one or more layers.

[0396] The baseband processing unit (3k-20) can perform a conversion function between a baseband signal and a bit sequence according to the physical layer specifications of the first wireless access technology. For example, when transmitting data, the baseband processing unit (3k-20) can generate complex symbols by encoding and modulating the transmitted bit sequence. Additionally, when receiving data, the baseband processing unit (3k-20) can restore the received bit sequence by demodulating and decoding the baseband signal provided by the RF processing unit (3k-10). For example, in the case of following the OFDM method, when transmitting data, the baseband processing unit (3k-20) can generate complex symbols by encoding and modulating the transmitted bit sequence, map the complex symbols to subcarriers, and then construct OFDM symbols through IFFT operation and CP insertion. Additionally, upon receiving data, the baseband processing unit (3k-20) can divide the baseband signal provided by the RF processing unit (3k-10) into OFDM symbol units, restore the signals mapped to subcarriers through FFT operations, and then restore the received bit sequence through demodulation and decoding. The baseband processing unit (3k-20) and the RF processing unit (3k-10) can transmit and receive signals as described above. Accordingly, the baseband processing unit (3k-20) and the RF processing unit (3k-10) may be referred to as a transmitting unit, a receiving unit, a transmitting and receiving unit, a communication unit, or a wireless communication unit.

[0397] The communication unit (3k-30) can provide an interface for communicating with other nodes in the network.

[0398] The storage unit (3k-40) can store data such as basic programs, application programs, and configuration information for the operation of the main station. In particular, the storage unit (3k-40) can store information regarding bearers assigned to connected terminals, measurement results reported from connected terminals, etc. Additionally, the storage unit (3k-40) can store information that serves as a criterion for determining whether to provide or disconnect multiple connections to the terminals. Furthermore, the storage unit (3k-40) can provide the stored data upon a request from the control unit (3k-50).

[0399] The control unit (3k-50) can control the overall operations of the main station. For example, the control unit (3k-50) can transmit and receive signals through the baseband processing unit (3k-20) and the RF processing unit (3k-10) or through the backhaul communication unit (3k-30). Additionally, the control unit (3k-50) writes and reads data to and from the storage unit (3k-40). To this end, the control unit (3k-50) may include at least one processor. The storage unit (3k-20) and the RF processing unit (3k-10) may be referred to as a transmitter, receiver, transceiver, communication unit, or wireless communication unit.

[0400] The communication unit (3k-30) can provide an interface for communicating with other nodes in the network.

[0401] The storage unit (3k-40) can store data such as basic programs, application programs, and configuration information for the operation of the main station. In particular, the storage unit (3k-40) can store information regarding bearers assigned to connected terminals, measurement results reported from connected terminals, etc. Additionally, the storage unit (3k-40) can store information that serves as a criterion for determining whether to provide or disconnect multiple connections to the terminals. Furthermore, the storage unit (3k-40) is a control unit

[0402] Stored data can be provided upon request from (3k-50).

[0403] The control unit (3k-50) can control the overall operations of the main station. For example, the control unit (3k-50) can transmit and receive signals through the baseband processing unit (3k-20) and the RF processing unit (3k-10) or through the backhaul communication unit (3k-30). Additionally, the control unit (3k-50) writes and reads data to and from the storage unit (3k-40). To this end, the control unit (3k-50) may include at least one processor.

[0404] Methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0405] When implemented in software, a computer-readable storage medium may be provided for storing one or more programs (software modules). One or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. One or more programs include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of this disclosure.

[0406] Such programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, ROM (Read Only Memory), Electrically Erasable Programmable Read Only Memory (EEPROM), magnetic disc storage devices, Compact Disc-ROM (CD-ROM), Digital Versatile Discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in memory composed of some or all of these. Additionally, each constituent memory may include multiple units.

[0407] Additionally, the above program may be stored on an attachable storage device that can be accessed via a communication network such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), or Storage Area Network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure through an external port. Additionally, a separate storage device on a communication network may be connected to a device performing an embodiment of the present disclosure.

[0408] In the specific embodiments of the present disclosure described above, the components included in the invention are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed of a singular form, or even if a component is expressed in the singular form, it may be composed of a plural form.

[0409] Meanwhile, although specific embodiments have been described in the detailed description of the present disclosure, it is understood that various modifications are possible within the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims set forth below as well as equivalents thereof.

Claims

Claim 1 A method for a terminal to perform communication in a wireless communication system, comprising: receiving danger area information including SSB (synchronization signal block) identification information corresponding to a danger area from a base station; performing an SSB measurement for at least one SSB received from the base station; identifying an SSB among the at least one SSB based on the SSB measurement; acquiring P2V (pedestrian to vehicle) data based on the SSB identification information corresponding to the identified SSB when the terminal is located in the danger area; and transmitting the P2V data to another terminal through a resource allocated to the terminal from the base station. Claim 2 delete Claim 3 A method according to claim 1, further comprising the step of identifying whether the terminal is located in the dangerous area by comparing the location information of the dangerous area with the location information of the terminal when the dangerous area information includes location information of the dangerous area. Claim 4 In claim 1, the step of identifying the SSB among the at least one SSB is a method of identifying the SSB in which the RSRP (reference signal received power) exceeds a threshold value based on the SSB measurement. Claim 5 In claim 1, the step of receiving the risk area information is a method of receiving the risk area information through at least one of system information, a paging signal, or a short message. Claim 6 A method according to claim 5, wherein the step of receiving the risk area information comprises: obtaining SSB identification information corresponding to the risk area from the system information or the paging signal; and receiving a short message indicating that the terminal is located in the risk area within the area covered by the SSB corresponding to the risk area. Claim 7 A method for a base station to perform communication in a wireless communication system, comprising: transmitting danger area information including SSB (synchronization signal block) identification information corresponding to a danger area; transmitting at least one SSB; receiving a P2V (pedestrian to vehicle) transmission resource allocation request from a terminal based on the at least one SSB and the SSB identification information corresponding to the danger area when a terminal is located in the danger area; and allocating a P2V transmission resource to the terminal based on the P2V transmission resource allocation request. Claim 8 In claim 7, the step of transmitting the risk area information is a method of transmitting the risk area information through either a paging signal or a short message to the cover area of ​​an SSB corresponding to the risk area. Claim 9 A terminal performing communication in a wireless communication system, comprising: a transceiver; and a processor connected to the transceiver, wherein the processor receives danger area information including SSB (synchronization signal block) identification information corresponding to a danger area from a base station, performs an SSB measurement for at least one SSB received from the base station, identifies an SSB among the at least one SSB based on the SSB measurement, and when the terminal is located in the danger area, acquires P2V (pedestrian to vehicle) data based on the SSB identification information corresponding to the identified SSB, and transmits the P2V data to another terminal through a resource allocated to the terminal from the base station. Claim 10 delete Claim 11 In claim 9, the processor identifies whether the terminal is located in the dangerous area by comparing the location information of the dangerous area with the location information of the terminal when the dangerous area information includes the location information of the dangerous area. Claim 12 In claim 9, the processor identifies the SSB in which the RSRP (reference signal received power) exceeds a threshold value based on the SSB measurement, a terminal. Claim 13 In claim 9, the processor is a terminal that receives the danger area information through at least one of system information, a paging signal, or a short message. Claim 14 In claim 13, the processor obtains SSB identification information corresponding to the danger area from the system information or the paging signal, and receives a short message indicating that the terminal is located in the danger area within the area covered by the SSB corresponding to the danger area. Claim 15 A base station performing communication in a wireless communication system, comprising: a transceiver; and a processor connected to the transceiver, wherein the processor transmits danger area information including SSB (synchronization signal block) identification information corresponding to a danger area and transmits at least one SSB, and when a terminal is located in the danger area, receives a P2V (pedestrian to vehicle) transmission resource allocation request from the terminal based on the at least one SSB and the SSB identification information corresponding to the danger area, and allocates a P2V transmission resource to the terminal based on the P2V transmission resource allocation request.

Images