WO2021172603A1 - Method for protecting v2x communication using server in wireless communication system - Google Patents

Abstract

The present specification relates to a method for a User Equipment (UE) to protect Vehicle-to-Everything (V2X) communication by using a server in a wireless communication system. The method may comprise the steps of: displaying a notification message by means of a display unit, the notification message including an input button for requesting that the server generate a security key for protecting the V2X communication; transmitting, to the server, a key request message for requesting generation of the security key, when the generation of the security key is requested through the input button; receiving an identifier for certifying the UE from the server, said identifier being generated in a core network; transmitting a certificate request message including the identifier to the core network in order to request a certificate for the V2X communication, said certificate being associated with the identifier; and receiving the certificate and a private key from the core network as a response to the certificate request message on the basis of verifying the identifier through the core network, and displaying, by means of the display unit, a notification message indicating that the certificate has been issued.

Description

A method for protecting V2X communication using a server in a wireless communication system

This specification is a method for protecting V2X communication using a server in a wireless communication system.

Wireless communication systems are being widely deployed to provide various types of communication services such as voice and data. In general, a wireless communication system is a multiple access system that can support communication with multiple users by sharing available system resources (bandwidth, transmission power, etc.). Examples of the multiple access system include a code division multiple access (CDMA) system, a frequency division multiple access (FDMA) system, a time division multiple access (TDMA) system, an orthogonal frequency division multiple access (OFDMA) system, and a single carrier frequency (SC-FDMA) system. There is a division multiple access) system, a multi carrier frequency division multiple access (MC-FDMA) system, and the like.

Various devices and technologies, such as smartphones and tablet PCs, which require machine-to-machine (M2M) communication and high data transfer rates, are emerging and disseminated. Accordingly, the amount of data required to be processed in a cellular network is increasing very rapidly. In order to satisfy such rapidly increasing data processing requirements, carrier aggregation technology, cognitive radio technology, etc., to efficiently use more frequency bands, increase the data capacity transmitted within a limited frequency. For multi-antenna technology, multi-base station cooperation technology, etc. are developing.

Meanwhile, an automobile may be classified into an internal combustion engine automobile, an external combustion engine automobile, a gas turbine automobile, an electric vehicle, or the like, depending on the type of the prime mover used. .

Autonomous vehicle refers to a vehicle that can operate on its own without driver or passenger manipulation. say

An object of the present specification is to propose a protection method for the signaling procedure of the 3GPP Layer in direct communication through PC5 between terminals.

The technical problems to be achieved by the present specification propose a method of using an application server to protect the signaling procedure of the 3GPP Layer in direct communication through PC5 between terminals.

The technical problems to be achieved by this specification are not limited to the technical problems mentioned above, and other technical problems not mentioned are clear to those of ordinary skill in the art to which this specification belongs from the detailed description of the invention below. will be able to be understood

An aspect of the present specification is a method for a terminal (UE: User Equipment) in a wireless communication system to protect V2X (Vehicle-to-Everything) communication using a server, through a display unit, the V2X communication to the server Displaying a guide message including an input button for requesting the generation of a security key (Security key) to protect the; transmitting a key request message for requesting generation of the security key to the server when the generation of the security key is requested through the input button; receiving an identifier generated in a core network for authenticating the terminal from the server; transmitting a certificate request message including the identifier to request a certificate (certificate) associated with the identifier for the V2X communication to the core network; and receiving the certificate and a private key as a response to the certificate request message from the core network based on the verification of the identifier through the core network, and indicating that the issuance of the certificate is completed through the display unit Displaying a guide message indicating; may include.

In addition, the certificate may be for determining whether the terminal is allowed in relation to the V2X communication through mutual authentication with another terminal.

In addition, the key request message may include subscriber information related to the user of the terminal available in the core network and the server.

In addition, the certificate may include information on a period during which the certificate is valid, set by a service provider related to the server.

In addition, displaying, through the display unit, a notification message including information of a provider of the service related to the server, information of a service that the provider of a service related to the server can provide, and information about a period during which the certificate is valid; may further include.

In addition, the notification message may further include information on a period during which the certificate set for each of the plurality of services is valid based on a plurality of services that the service provider related to the server may provide.

In addition, transmitting the certificate to another terminal; receiving, from the other terminal, a certificate of the other terminal; and transmitting, to the other terminal, a security key for direct communication with the other terminal based on the verification of the certificate of the other terminal. may further include.

In addition, the terminal may establish a unicast link with the other terminal through a security key for direct communication with the other terminal.

In addition, the unicast link may be based on configuration information preset in the terminal.

In addition, displaying a setting screen including the setting information; It further includes, wherein the setting screen includes an input field for receiving a setting value from the user, and the input field may have an underlined text form.

Another aspect of the present specification is a terminal (UE: User Equipment) for protecting V2X (Vehicle-to-Everything) communication using a server in a wireless communication system, comprising: a transceiver; display unit; Memory; and a processor for controlling the transceiver, the display unit, and the memory, wherein the processor is an input button for requesting generation of a security key for protecting the V2X communication to the server through the display unit displays the included guide message, and when the generation of the security key is requested through the input button, transmits a key request message for requesting generation of the security key to the server through the transceiver, and Receives an identifier generated in the core network for authenticating the terminal from the server, and a certificate request message including the identifier to request a certificate associated with the identifier for the V2X communication to the core network transmit, receive the certificate and a private key as a response to the certificate request message from the core network based on verification of the identifier through the core network, and issue the certificate through the display unit A guide message indicating that this has been completed may be displayed.

According to the embodiment of the present specification, in direct communication through PC5 between terminals, it is possible to perform a protection procedure regarding the signaling procedure of the 3GPP layer.

According to another embodiment of the present specification, an application server may be used for protection regarding the signaling procedure of the 3GPP Layer in direct communication through PC5 between terminals.

The effects obtainable in the present specification are not limited to the above-mentioned effects, and other effects not mentioned will be clearly understood by those of ordinary skill in the art to which this specification belongs from the description below. .

1 shows an AI device according to an embodiment of the present specification.

2 shows an AI server according to an embodiment of the present specification.

3 shows an AI system according to an embodiment of the present specification.

4 is a diagram illustrating a schematic structure of an Evolved Packet System (EPS) including an Evolved Packet Core (EPC).

5 is an exemplary diagram of a network structure of an evolved universal terrestrial radio access network (E-UTRAN) to which this specification can be applied.

6 is a diagram illustrating an architecture of a general NR-RAN.

7 shows an example of a general architecture of 5G.

8 illustrates a non-roaming 5G system architecture to which this specification can be applied.

9 and 10 illustrate a Roaming 5G system architecture to which this specification can be applied.

11 is an example of a provisioned AF-based service parameter to which this specification is applied.

12 illustrates an architectural reference model to which this specification can be applied.

13 is an example of a PC5 unicast link to which this specification can be applied.

14 is a diagram illustrating a procedure for a broadcast mode of V2X communication using PC5.

15 is a diagram illustrating a procedure for a groupcast mode of V2X communication using PC5.

16 is a diagram illustrating a procedure for a unicast mode of V2X communication using PC5.

17 illustrates a link identifier update procedure for a unicast link to which this specification can be applied.

18 illustrates a layer 2 link release procedure through a PC5 reference point to which this specification can be applied.

19 illustrates a layer 2 link modification procedure for a unicast link to which this specification can be applied.

20 is an exemplary diagram showing the structure of a radio interface protocol (Radio Interface Protocol) in the control plane between the UE and the eNodeB.

21 is an example of the configuration of the 3GPP V2X Layer and Application Layer (or ITS Layer) to which this specification can be applied.

22 is an example of a certificate and security key issuance procedure for unicast mode communication to which this specification can be applied.

23 is an example of an approval procedure to which this specification can be applied.

24 is an embodiment of a display to which this specification can be applied.

25 is an example of a mutual authentication procedure to which this specification can be applied.

26 is an embodiment of a display to which this specification can be applied.

27 is an embodiment of a terminal to which this specification can be applied.

28 is an embodiment of a core network to which this specification can be applied.

29 shows a wireless communication device according to an embodiment of the present specification.

30 illustrates a block diagram of a network node according to an embodiment of the present specification.

31 illustrates a block diagram of a communication device according to an embodiment of the present specification.

BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are included as a part of the detailed description to help the understanding of the present specification, provide embodiments of the present specification, and together with the detailed description, explain the technical features of the present specification.

The terms used in the present specification have been selected while considering the functions in the present specification and are currently widely used general terms, which may vary depending on the intention or precedent of a person skilled in the art, the emergence of new technology, and the like. In addition, in a specific case, there is a term arbitrarily selected by the applicant, and in this case, the meaning will be described in detail in the description of the corresponding invention. Therefore, the terms used in this specification should be defined based on the meaning of the term and the content throughout the present specification, rather than the simple name of the term.

The following embodiments combine the elements and features of the present specification in a predetermined form. Each component or feature may be considered optional unless explicitly stated otherwise. Each component or feature may be implemented in a form that is not combined with other components or features. In addition, some components and/or features may be combined to constitute an embodiment of the present specification. The order of operations described in the embodiments of the present specification may be changed. Some configurations or features of one embodiment may be included in other embodiments, or may be replaced with corresponding configurations or features of other embodiments.

In the description of the drawings, procedures or steps that may obscure the gist of the present specification are not described, and procedures or steps that can be understood at the level of those skilled in the art are also not described.

Throughout the specification, when a part is said to "comprising or including" a certain element, it means that other elements may be further included, rather than excluding other elements, unless otherwise stated. do. In addition, terms such as "... unit", "... group", and "module" described in the specification mean a unit that processes at least one function or operation, which is hardware or software or a combination of hardware and software. can be implemented as Also, "a or an", "one", "the" and like related terms are used differently herein in the context of describing this specification (especially in the context of the following claims). Unless indicated or clearly contradicted by context, it may be used in a sense including both the singular and the plural.

Embodiments of the present specification may be supported by standard documents disclosed in at least one of the wireless access systems IEEE 802.xx system, 3GPP system, 3GPP LTE system, and 3GPP2 system. That is, obvious steps or parts not described in the embodiments of the present specification may be described with reference to the above documents.

In addition, all terms disclosed in this document may be explained by the standard document. For example, this specification describes 3GPP TS 36.211, 3GPP TS 36.213, 3GPP TS 36.321, 3GPP TS 36.322, 3GPP TS 36.323, 3GPP TS 36.331, 3GPP TS 23.203, 3GPP TS 23.401, 3GPP TS 24.228, 3GPP TS 23.228, 3GPP TS 23.228 , 3GPP TS 23.218, 3GPP TS 22.011, 3GPP TS 36.413 may be incorporated by one or more of the standard documents.

Hereinafter, preferred embodiments according to the present specification will be described in detail with reference to the accompanying drawings. DETAILED DESCRIPTION The detailed description set forth below in conjunction with the appended drawings is intended to describe exemplary embodiments of the present specification and is not intended to represent the only embodiments in which the present specification may be practiced.

In addition, specific terms used in the embodiments of the present specification are provided to help the understanding of the present specification, and the use of these specific terms may be changed to other forms without departing from the technical spirit of the present specification.

In this specification, the base station has a meaning as a terminal node of a network that directly communicates with the terminal. A specific operation described as being performed by the base station in this document may be performed by an upper node of the base station in some cases. That is, it is obvious that various operations performed for communication with the terminal in a network including a plurality of network nodes including the base station may be performed by the base station or other network nodes other than the base station. 'Base station (BS: Base Station)' is a term such as a fixed station (fixed station), Node B, eNB (evolved-NodeB), BTS (base transceiver system), access point (AP: Access Point), gNB (general NB), etc. can be replaced by In addition, 'terminal' may be fixed or have mobility, UE (User Equipment), MS (Mobile Station), UT (user terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS ( Advanced Mobile Station), a wireless terminal (WT), a machine-type communication (MTC) device, a machine-to-machine (M2M) device, a device-to-device (D2D) device, and the like.

Hereinafter, downlink (DL: downlink) means communication from a base station to a terminal, and uplink (UL: uplink) means communication from a terminal to a base station. In the downlink, the transmitter may be a part of the base station, and the receiver may be a part of the terminal. In the uplink, the transmitter may be a part of the terminal, and the receiver may be a part of the base station.

For clarity of explanation, 3GPP LTE/LTE-A/NR (New Radio) is mainly described, but the technical features of the present specification are not limited thereto.

The three main requirements areas for 5G are (1) Enhanced Mobile Broadband (eMBB) area, (2) Massive Machine Type Communication (mMTC) area and (3) Ultra-reliable and It includes an Ultra-reliable and Low Latency Communications (URLLC) area.

Some use cases may require multiple areas for optimization, while other use cases may focus on only one key performance indicator (KPI). 5G is to support these various use cases in a flexible and reliable way.

eMBB goes far beyond basic mobile internet access, covering rich interactive work, media and entertainment applications in the cloud or augmented reality. Data is one of the key drivers of 5G, and for the first time in the 5G era, we may not see dedicated voice services. In 5G, voice is simply expected to be processed as an application using the data connection provided by the communication system. The main causes for increased traffic volume are an increase in content size and an increase in the number of applications requiring high data rates. Streaming services (audio and video), interactive video and mobile Internet connections will become more widely used as more devices are connected to the Internet. Many of these applications require always-on connectivity to push real-time information and notifications to users. Cloud storage and applications are rapidly increasing in mobile communication platforms, which can be applied to both work and entertainment. And, cloud storage is a special use case that drives the growth of uplink data rates. 5G is also used for remote work in the cloud, requiring much lower end-to-end latency to maintain a good user experience when tactile interfaces are used. Entertainment For example, cloud gaming and video streaming are other key factors that increase the demand for mobile broadband capabilities. Entertainment is essential on smartphones and tablets anywhere, including in high-mobility environments such as trains, cars and airplanes. Another use example is augmented reality for entertainment and information retrieval. Here, augmented reality requires very low latency and instantaneous amount of data.

Also, one of the most anticipated 5G use cases relates to the ability to seamlessly connect embedded sensors in all fields, namely mMTC. By 2020, the number of potential IoT devices is projected to reach 20.4 billion. Industrial IoT is one of the areas where 5G will play a major role in enabling smart cities, asset tracking, smart utilities, agriculture and security infrastructure.

URLLC includes new services that will transform the industry through ultra-reliable/low-latency links that allow for remote control of critical infrastructure and self-driving vehicles, such as self-driving vehicles. This level of reliability and latency is essential for smart grid control, industrial automation, robotics, and drone control and coordination.

Next, a number of usage examples will be described in more detail.

5G could complement fiber-to-the-home (FTTH) and cable-based broadband (or DOCSIS) as a means of delivering streams rated at hundreds of megabits per second to gigabits per second. This high speed is required to deliver TVs in resolutions of 4K and higher (6K, 8K and higher), as well as virtual and augmented reality. Virtual Reality (VR) and Augmented Reality (AR) applications almost include immersive sporting events. Certain applications may require special network settings. For VR games, for example, game companies may need to integrate core servers with network operators' edge network servers to minimize latency.

Automotive is expected to be an important new driving force for 5G, with many use cases for mobile communication to vehicles. For example, entertainment for passengers requires simultaneous high capacity and high mobility mobile broadband. The reason is that future users will continue to expect high-quality connections regardless of their location and speed. Another use case in the automotive sector is augmented reality dashboards. It identifies objects in the dark and overlays information that tells the driver about the distance and movement of the object over what the driver is seeing through the front window. In the future, wireless modules will allow for communication between vehicles, the exchange of information between the vehicle and the supporting infrastructure, and the exchange of information between the automobile and other connected devices (eg, devices carried by pedestrians). Safety systems can help drivers reduce the risk of accidents by guiding alternative courses of action to help them drive safer. The next step will be remote-controlled or self-driven vehicles. This requires very reliable and very fast communication between different self-driving vehicles and between vehicles and infrastructure. In the future, self-driving vehicles will perform all driving activities, allowing drivers to focus only on traffic anomalies that the vehicle itself cannot discern. The technical requirements of self-driving vehicles demand ultra-low latency and ultra-fast reliability to increase traffic safety to levels that are unattainable by humans.

Smart cities and smart homes, referred to as smart societies, will be embedded with high-density wireless sensor networks. A distributed network of intelligent sensors will identify conditions for cost and energy-efficient maintenance of a city or house. A similar setup can be performed for each household. Temperature sensors, window and heating controllers, burglar alarms and appliances are all connected wirelessly. Many of these sensors are typically low data rates, low power and low cost. However, for example, real-time HD video may be required in certain types of devices for surveillance.

The consumption and distribution of energy, including heat or gas, is highly decentralized, requiring automated control of distributed sensor networks. Smart grids use digital information and communication technologies to interconnect these sensors to collect information and act on it. This information can include supplier and consumer behavior, enabling smart grids to improve efficiency, reliability, economics, sustainability of production and distribution of fuels such as electricity in an automated manner. The smart grid can also be viewed as another low-latency sensor network.

The health sector has many applications that can benefit from mobile communications. The communication system may support telemedicine providing clinical care from a remote location. This can help reduce barriers to distance and improve access to consistently unavailable health care services in remote rural areas. It is also used to save lives in critical care and emergency situations. A wireless sensor network based on mobile communication may provide remote monitoring and sensors for parameters such as heart rate and blood pressure.

Wireless and mobile communications are becoming increasingly important in industrial applications. Wiring is expensive to install and maintain. Thus, the tolerance for replacement of cables with reconfigurable wireless links is an attractive opportunity for many industries. However, achieving this requires that the wireless connection operate with cable-like delay, reliability and capacity, and that its management be simplified. Low latency and very low error probability are new requirements that need to be connected with 5G.

Logistics and freight tracking are important use cases for mobile communications that use location-based information systems to allow tracking of inventory and packages from anywhere. Logistics and freight tracking use cases typically require low data rates but require wide range and reliable location information.

The present specification, which will be described later in this specification, may be implemented by combining or changing each embodiment to satisfy the above-mentioned requirements of 5G.

Hereinafter, it will be described in detail in relation to a technical field to which the present specification, which will be described later, can be applied.

Artificial Intelligence (AI)

Artificial intelligence refers to a field that studies artificial intelligence or methodologies that can make it, and machine learning refers to a field that defines various problems dealt with in the field of artificial intelligence and studies methodologies to solve them. do. Machine learning is also defined as an algorithm that improves the performance of a certain task through constant experience.

An artificial neural network (ANN) is a model used in machine learning, and may refer to an overall model having problem-solving ability, which is composed of artificial neurons (nodes) that form a network by combining synapses. An artificial neural network may be defined by a connection pattern between neurons of different layers, a learning process that updates model parameters, and an activation function that generates an output value.

The artificial neural network may include an input layer, an output layer, and optionally one or more hidden layers. Each layer includes one or more neurons, and the artificial neural network may include neurons and synapses connecting neurons. In the artificial neural network, each neuron may output a function value of an activation function for input signals, weights, and biases input through synapses.

Model parameters refer to parameters determined through learning, and include the weight of synaptic connections and the bias of neurons. In addition, the hyperparameter refers to a parameter to be set before learning in a machine learning algorithm, and includes a learning rate, the number of iterations, a mini-batch size, an initialization function, and the like.

The purpose of learning the artificial neural network can be seen as determining the model parameters that minimize the loss function. The loss function may be used as an index for determining optimal model parameters in the learning process of the artificial neural network.

Machine learning can be classified into supervised learning, unsupervised learning, and reinforcement learning according to a learning method.

Supervised learning refers to a method of training an artificial neural network in a state where a label for training data is given. can mean Unsupervised learning may refer to a method of training an artificial neural network in a state where no labels are given for training data. Reinforcement learning can refer to a learning method in which an agent defined in an environment learns to select an action or sequence of actions that maximizes the cumulative reward in each state.

Among artificial neural networks, machine learning implemented as a deep neural network (DNN) including a plurality of hidden layers is also called deep learning (deep learning), and deep learning is a part of machine learning. Hereinafter, machine learning is used in a sense including deep learning.

Robot

A robot can mean a machine that automatically handles or operates a task given by its own capabilities. In particular, a robot having a function of recognizing an environment and performing an operation by self-judgment may be referred to as an intelligent robot.

Robots can be classified into industrial, medical, home, military, etc. depending on the purpose or field of use.

The robot may be provided with a driving unit including an actuator or a motor to perform various physical operations such as moving the robot joints. In addition, the moving robot includes a wheel, a brake, a propeller, etc. in the driving unit, and can travel on the ground or fly in the air through the driving unit.

Self-Driving, Autonomous-Driving

Autonomous driving refers to a technology that drives by itself, and an autonomous driving vehicle refers to a vehicle that runs without a user's manipulation or with a minimal user's manipulation.

For example, autonomous driving includes technology for maintaining a driving lane, technology for automatically adjusting speed such as adaptive cruise control, technology for automatically driving along a predetermined route, technology for automatically setting a route when a destination is set, etc. All of these can be included.

The vehicle includes a vehicle having only an internal combustion engine, a hybrid vehicle having both an internal combustion engine and an electric motor, and an electric vehicle having only an electric motor, and may include not only automobiles, but also trains, motorcycles, and the like.

In this case, the autonomous vehicle may be viewed as a robot having an autonomous driving function.

Extended Reality (XR)

The extended reality is a generic term for virtual reality (VR), augmented reality (AR), and mixed reality (MR). VR technology provides only CG images of objects or backgrounds in the real world, AR technology provides virtual CG images on top of images of real objects, and MR technology is a computer that mixes and combines virtual objects in the real world. graphic technology.

MR technology is similar to AR technology in that it shows both real and virtual objects. However, there is a difference in that in AR technology, a virtual object is used in a form that complements a real object, whereas in MR technology, a virtual object and a real object are used with equal characteristics.

XR technology can be applied to HMD (Head-Mount Display), HUD (Head-Up Display), mobile phone, tablet PC, laptop, desktop, TV, digital signage, etc. can be called

1 shows an AI device 100 according to an embodiment of the present specification.

The AI device 100 is a TV, a projector, a mobile phone, a smart phone, a desktop computer, a notebook computer, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a tablet PC, a wearable device, a set-top box (STB) ), a DMB receiver, a radio, a washing machine, a refrigerator, a desktop computer, a digital signage, a robot, a vehicle, etc., may be implemented as a fixed device or a device allowing movement.

Referring to FIG. 1 , the terminal 100 includes a communication unit 110 , an input unit 120 , a learning processor 130 , a sensing unit 140 , an output unit 150 , a memory 170 and a processor 180 , and the like. may include

The communication unit 110 may transmit/receive data to and from external devices such as other AI devices 100a to 100e or the AI server 200 using wired/wireless communication technology. For example, the communication unit 110 may transmit/receive sensor information, a user input, a learning model, a control signal, and the like with external devices.

At this time, the communication technology used by the communication unit 110 includes GSM (Global System for Mobile communication), CDMA (Code Division Multi Access), LTE (Long Term Evolution), 5G, WLAN (Wireless LAN), Wi-Fi (Wireless-Fidelity) ), Bluetooth, RFID (Radio Frequency Identification), Infrared Data Association (IrDA), ZigBee, NFC (Near Field Communication), and the like.

The input unit 120 may acquire various types of data.

In this case, the input unit 120 may include a camera for inputting an image signal, a microphone for receiving an audio signal, a user input unit for receiving information from a user, and the like. Here, the camera or microphone may be treated as a sensor, and a signal obtained from the camera or microphone may be referred to as sensing data or sensor information.

The input unit 120 may acquire training data for model training and input data to be used when acquiring an output using the training model. The input unit 120 may acquire raw input data, and in this case, the processor 180 or the learning processor 130 may extract an input feature as a preprocessing for the input data.

The learning processor 130 may train a model composed of an artificial neural network by using the training data. Here, the learned artificial neural network may be referred to as a learning model. The learning model may be used to infer a result value with respect to new input data other than the training data, and the inferred value may be used as a basis for a decision to perform a certain operation.

In this case, the learning processor 130 may perform AI processing together with the learning processor 240 of the AI server 200 .

In this case, the learning processor 130 may include a memory integrated or implemented in the AI device 100 . Alternatively, the learning processor 130 may be implemented using the memory 170 , an external memory directly coupled to the AI device 100 , or a memory maintained in an external device.

The sensing unit 140 may acquire at least one of internal information of the AI device 100 , information on the surrounding environment of the AI device 100 , and user information by using various sensors.

At this time, sensors included in the sensing unit 140 include a proximity sensor, an illuminance sensor, an acceleration sensor, a magnetic sensor, a gyro sensor, an inertial sensor, an RGB sensor, an IR sensor, a fingerprint recognition sensor, an ultrasonic sensor, an optical sensor, a microphone, and a lidar. , radar, etc.

The output unit 150 may generate an output related to visual, auditory or tactile sense.

In this case, the output unit 150 may include a display unit that outputs visual information, a speaker that outputs auditory information, and a haptic module that outputs tactile information.

The memory 170 may store data supporting various functions of the AI device 100 . For example, the memory 170 may store input data obtained from the input unit 120 , learning data, a learning model, a learning history, and the like.

The processor 180 may determine at least one execution permitted operation of the AI device 100 based on information determined or generated using a data analysis algorithm or a machine learning algorithm. In addition, the processor 180 may control the components of the AI device 100 to perform the determined operation.

To this end, the processor 180 may request, search, receive, or utilize the data of the learning processor 130 or the memory 170 , and an operation that is predicted or desirable among the at least one execution permitted operation. It is possible to control the components of the AI device 100 to execute.

In this case, when the connection of the external device is required to perform the determined operation, the processor 180 may generate a control signal for controlling the corresponding external device and transmit the generated control signal to the corresponding external device.

The processor 180 may obtain intention information with respect to a user input and determine a user's requirement based on the obtained intention information.

In this case, the processor 180 uses at least one of a speech to text (STT) engine for converting a voice input into a character string or a natural language processing (NLP) engine for obtaining intention information of a natural language. Intention information corresponding to the input may be obtained.

In this case, at least one of the STT engine and the NLP engine may be configured as an artificial neural network, at least a part of which is learned according to a machine learning algorithm. And, at least one of the STT engine or the NLP engine is learned by the learning processor 130 , or learned by the learning processor 240 of the AI server 200 , or learned by distributed processing thereof. it could be

The processor 180 collects history information including the user's feedback on the operation contents or operation of the AI device 100 and stores it in the memory 170 or the learning processor 130, or the AI server 200 It can be transmitted to an external device. The collected historical information may be used to update the learning model.

The processor 180 may control at least some of the components of the AI device 100 in order to drive an application program stored in the memory 170 . Furthermore, in order to drive the application program, the processor 180 may operate two or more of the components included in the AI device 100 in combination with each other.

2 shows an AI server 200 according to an embodiment of the present specification.

Referring to FIG. 2 , the AI server 200 may refer to a device that trains an artificial neural network using a machine learning algorithm or uses a learned artificial neural network. Here, the AI server 200 may be configured with a plurality of servers to perform distributed processing, and may be defined as a 5G network. In this case, the AI server 200 may be included as a part of the AI device 100 to perform at least a part of AI processing together.

The AI server 200 may include a communication unit 210 , a memory 230 , a learning processor 240 , and a processor 260 .

The communication unit 210 may transmit/receive data to and from an external device such as the AI device 100 .

The memory 230 may include a model storage unit 231 . The model storage unit 231 may store a model (or artificial neural network, 231a) being trained or learned through the learning processor 240 .

The learning processor 240 may train the artificial neural network 231a using the training data. The learning model may be used while being mounted on the AI server 200 of the artificial neural network, or may be used while being mounted on an external device such as the AI device 100 .

The learning model may be implemented in hardware, software, or a combination of hardware and software. When a part or all of the learning model is implemented in software, one or more instructions constituting the learning model may be stored in the memory 230 .

The processor 260 may infer a result value with respect to new input data using the learning model, and may generate a response or a control command based on the inferred result value.

3 shows an AI system 1 according to an embodiment of the present specification.

Referring to FIG. 3 , the AI system 1 includes at least one of an AI server 200 , a robot 100a , an autonomous vehicle 100b , an XR device 100c , a smart phone 100d , or a home appliance 100e . It is connected to the cloud network 10 . Here, the robot 100a to which the AI technology is applied, the autonomous driving vehicle 100b, the XR device 100c, the smart phone 100d, or the home appliance 100e may be referred to as AI devices 100a to 100e.

The cloud network 10 may constitute a part of the cloud computing infrastructure or may refer to a network existing in the cloud computing infrastructure. Here, the cloud network 10 may be configured using a 3G network, a 4G or Long Term Evolution (LTE) network, or a 5G network.

That is, each of the devices 100a to 100e and 200 constituting the AI system 1 may be connected to each other through the cloud network 10 . In particular, each of the devices 100a to 100e and 200 may communicate with each other through the base station, but may also directly communicate with each other without passing through the base station.

The AI server 200 may include a server performing AI processing and a server performing an operation on big data.

The AI server 200 includes at least one or more of the AI devices constituting the AI system 1, such as a robot 100a, an autonomous vehicle 100b, an XR device 100c, a smartphone 100d, or a home appliance 100e. It is connected through the cloud network 10 and may help at least a part of AI processing of the connected AI devices 100a to 100e.

In this case, the AI server 200 may train the artificial neural network according to a machine learning algorithm on behalf of the AI devices 100a to 100e, and directly store the learning model or transmit it to the AI devices 100a to 100e.

At this time, the AI server 200 receives input data from the AI devices 100a to 100e, infers a result value with respect to the input data received using the learning model, and provides a response or control command based on the inferred result value. It can be generated and transmitted to the AI devices 100a to 100e.

Alternatively, the AI devices 100a to 100e may infer a result value with respect to input data using a direct learning model, and generate a response or a control command based on the inferred result value.

Hereinafter, various embodiments of the AI devices 100a to 100e to which the above-described technology is applied will be described. Here, the AI devices 100a to 100e shown in FIG. 3 can be viewed as specific examples of the AI device 100 shown in FIG. 1 .

AI and robots to which this specification can be applied

The robot 100a may be implemented as a guide robot, a transport robot, a cleaning robot, a wearable robot, an entertainment robot, a pet robot, an unmanned flying robot, etc. to which AI technology is applied.

The robot 100a may include a robot control module for controlling an operation, and the robot control module may mean a software module or a chip implemented as hardware.

The robot 100a obtains state information of the robot 100a by using sensor information obtained from various types of sensors, detects (recognizes) the surrounding environment and objects, generates map data, moves path and travels A plan may be determined, a response to a user interaction may be determined, or an action may be determined.

Here, the robot 100a may use sensor information obtained from at least one sensor among LiDAR, radar, and camera to determine a movement path and a travel plan.

The robot 100a may perform the above-described operations using a learning model composed of at least one artificial neural network. For example, the robot 100a may recognize a surrounding environment and an object using a learning model, and may determine an operation using the recognized surrounding environment information or object information. Here, the learning model may be directly learned from the robot 100a or learned from an external device such as the AI server 200 .

At this time, the robot 100a may perform an operation by generating a result by using the direct learning model, but transmits sensor information to an external device such as the AI server 200 and receives the result generated accordingly to perform the operation You may.

The robot 100a determines a movement path and travel plan using at least one of map data, object information detected from sensor information, or object information obtained from an external device, and controls the driving unit to apply the determined movement path and travel plan. Accordingly, the robot 100a may be driven.

The map data may include object identification information for various objects disposed in a space in which the robot 100a moves. For example, the map data may include object identification information for fixed objects such as walls and doors, and objects that are allowed to move, such as flowerpots and desks. In addition, the object identification information may include a name, a type, a distance, a location, and the like.

In addition, the robot 100a may perform an operation or drive by controlling the driving unit based on the user's control/interaction. In this case, the robot 100a may acquire intention information of an interaction according to a user's motion or voice utterance, determine a response based on the acquired intention information, and perform the operation.

AI and autonomous driving to which this specification can be applied

The autonomous driving vehicle 100b may be implemented as a mobile robot, a vehicle, an unmanned aerial vehicle, etc. by applying AI technology.

The autonomous driving vehicle 100b may include an autonomous driving control module for controlling an autonomous driving function, and the autonomous driving control module may mean a software module or a chip implemented as hardware. The autonomous driving control module may be included as a component of the autonomous driving vehicle 100b, or may be configured and connected to the outside of the autonomous driving vehicle 100b as separate hardware.

The autonomous driving vehicle 100b acquires state information of the autonomous driving vehicle 100b using sensor information obtained from various types of sensors, detects (recognizes) surrounding environments and objects, generates map data, A moving route and a driving plan may be determined, or an operation may be determined.

Here, the autonomous vehicle 100b may use sensor information obtained from at least one sensor among LiDAR, radar, and camera, similarly to the robot 100a, in order to determine a moving route and a driving plan.

In particular, the autonomous vehicle 100b may receive sensor information from external devices to recognize an environment or object for an area where the field of view is blocked or an area over a certain distance, or receive information recognized directly from external devices. .

The autonomous vehicle 100b may perform the above-described operations using a learning model composed of at least one artificial neural network. For example, the autonomous driving vehicle 100b may recognize a surrounding environment and an object using a learning model, and may determine a driving route using the recognized surrounding environment information or object information. Here, the learning model may be directly learned from the autonomous vehicle 100b or learned from an external device such as the AI server 200 .

In this case, the autonomous vehicle 100b may generate a result by using a direct learning model and perform an operation, but operates by transmitting sensor information to an external device such as the AI server 200 and receiving the result generated accordingly. can also be performed.

The autonomous driving vehicle 100b determines a moving route and a driving plan by using at least one of map data, object information detected from sensor information, or object information acquired from an external device, and controls the driving unit to determine the moving path and driving. The autonomous vehicle 100b may be driven according to a plan.

The map data may include object identification information for various objects disposed in a space (eg, a road) in which the autonomous vehicle 100b travels. For example, the map data may include object identification information for fixed objects such as street lights, rocks, and buildings, and objects that are allowed to move, such as vehicles and pedestrians. In addition, the object identification information may include a name, a type, a distance, a location, and the like.

In addition, the autonomous vehicle 100b may perform an operation or drive by controlling the driving unit based on the user's control/interaction. In this case, the autonomous vehicle 100b may acquire intention information of an interaction according to a user's motion or voice utterance, determine a response based on the obtained intention information, and perform the operation.

AI and XR to which this specification may be applied

The XR apparatus 100c is AI technology applied, so a head-mount display (HMD), a head-up display (HUD) provided in a vehicle, a television, a mobile phone, a smart phone, a computer, a wearable device, a home appliance, and a digital signage , a vehicle, a stationary robot, or a mobile robot.

The XR device 100c analyzes three-dimensional point cloud data or image data obtained through various sensors or from an external device to generate position data and attribute data for three-dimensional points, thereby providing information on surrounding space or real objects. It can be obtained and output by rendering the XR object to be output. For example, the XR apparatus 100c may output an XR object including additional information on the recognized object to correspond to the recognized object.

The XR apparatus 100c may perform the above operations by using a learning model composed of at least one artificial neural network. For example, the XR apparatus 100c may recognize a real object from 3D point cloud data or image data using a learning model, and may provide information corresponding to the recognized real object. Here, the learning model may be directly learned from the XR device 100c or learned from an external device such as the AI server 200 .

In this case, the XR device 100c may perform an operation by generating a result using the direct learning model, but transmits sensor information to an external device such as the AI server 200 and receives the result generated accordingly to perform the operation. can also be done

AI, robot and autonomous driving to which this specification can be applied

The robot 100a may be implemented as a guide robot, a transport robot, a cleaning robot, a wearable robot, an entertainment robot, a pet robot, an unmanned flying robot, etc. to which AI technology and autonomous driving technology are applied.

The robot 100a to which AI technology and autonomous driving technology are applied may mean a robot having an autonomous driving function or a robot 100a that interacts with the autonomous driving vehicle 100b.

The robot 100a having an autonomous driving function may collectively refer to devices that move by themselves according to a given movement line without user's control, or move by determining a movement line by themselves.

The robot 100a with the autonomous driving function and the autonomous driving vehicle 100b may use a common sensing method to determine one or more of a moving route or a driving plan. For example, the robot 100a having an autonomous driving function and the autonomous driving vehicle 100b may determine one or more of a moving route or a driving plan by using information sensed through lidar, radar, and camera.

The robot 100a interacting with the autonomous driving vehicle 100b exists separately from the autonomous driving vehicle 100b and is linked to an autonomous driving function inside or outside the autonomous driving vehicle 100b, or the autonomous driving vehicle 100b ) can perform an operation associated with the user on board.

At this time, the robot 100a interacting with the autonomous driving vehicle 100b acquires sensor information on behalf of the autonomous driving vehicle 100b and provides it to the autonomous driving vehicle 100b, or obtains sensor information and obtains information about the surrounding environment or By generating object information and providing it to the autonomous driving vehicle 100b, the autonomous driving function of the autonomous driving vehicle 100b may be controlled or supported.

Alternatively, the robot 100a interacting with the autonomous driving vehicle 100b may monitor a user riding in the autonomous driving vehicle 100b or control a function of the autonomous driving vehicle 100b through interaction with the user. . For example, when it is determined that the driver is in a drowsy state, the robot 100a may activate the autonomous driving function of the autonomous driving vehicle 100b or assist the control of the driving unit of the autonomous driving vehicle 100b. Here, the function of the autonomous driving vehicle 100b controlled by the robot 100a may include not only an autonomous driving function, but also a function provided by a navigation system or an audio system provided in the autonomous driving vehicle 100b.

Alternatively, the robot 100a interacting with the autonomous driving vehicle 100b may provide information or assist a function to the autonomous driving vehicle 100b from the outside of the autonomous driving vehicle 100b. For example, the robot 100a may provide traffic information including signal information to the autonomous vehicle 100b, such as a smart traffic light, or interact with the autonomous vehicle 100b, such as an automatic electric charger for an electric vehicle. You can also automatically connect an electric charger to the charging port.

AI, Robot and XR to which this specification can be applied

The robot 100a may be implemented as a guide robot, a transport robot, a cleaning robot, a wearable robot, an entertainment robot, a pet robot, an unmanned flying robot, a drone, etc. to which AI technology and XR technology are applied.

The robot 100a to which the XR technology is applied may mean a robot that is a target of control/interaction within an XR image. In this case, the robot 100a is distinguished from the XR device 100c and may be interlocked with each other.

When the robot 100a, which is the target of control/interaction in the XR image, obtains sensor information from sensors including a camera, the robot 100a or the XR device 100c generates an XR image based on the sensor information. and the XR apparatus 100c may output the generated XR image. In addition, the robot 100a may operate based on a control signal input through the XR device 100c or a user's interaction.

For example, the user can check the XR image corresponding to the viewpoint of the remotely linked robot 100a through an external device such as the XR device 100c, and adjust the autonomous driving path of the robot 100a through interaction or , control motion or driving, or check information of surrounding objects.

AI, autonomous driving and XR to which this specification may be applied

The autonomous vehicle 100b may be implemented as a mobile robot, a vehicle, an unmanned aerial vehicle, etc. by applying AI technology and XR technology.

The autonomous driving vehicle 100b to which the XR technology is applied may mean an autonomous driving vehicle equipped with a means for providing an XR image or an autonomous driving vehicle subject to control/interaction within the XR image. In particular, the autonomous driving vehicle 100b, which is the target of control/interaction in the XR image, is distinguished from the XR device 100c and may be interlocked with each other.

The autonomous driving vehicle 100b having means for providing an XR image may obtain sensor information from sensors including a camera, and output an XR image generated based on the acquired sensor information. For example, the autonomous vehicle 100b may provide an XR object corresponding to a real object or an object in the screen to the occupant by outputting an XR image with a HUD.

In this case, when the XR object is output to the HUD, at least a portion of the XR object may be output to overlap the actual object to which the passenger's gaze is directed. On the other hand, when the XR object is output to a display provided inside the autonomous driving vehicle 100b, at least a portion of the XR object may be output to overlap the object in the screen. For example, the autonomous vehicle 100b may output XR objects corresponding to objects such as a lane, other vehicles, traffic lights, traffic signs, two-wheeled vehicles, pedestrians, and buildings.

When the autonomous driving vehicle 100b, which is the subject of control/interaction in the XR image, acquires sensor information from sensors including a camera, the autonomous driving vehicle 100b or the XR device 100c performs An XR image is generated, and the XR apparatus 100c may output the generated XR image. In addition, the autonomous vehicle 100b may operate based on a control signal input through an external device such as the XR device 100c or a user's interaction.

First, terms used herein are defined as follows.

- IMS (IP Multimedia Subsystem or IP Multimedia Core Network Subsystem): an architectural framework for providing standardization for delivering voice or other multimedia services over IP.

- UMTS (Universal Mobile Telecommunications System): 3G (Generation) mobile communication technology based on GSM (Global System for Mobile Communication), developed by 3GPP.

- EPS (Evolved Packet System): A network system composed of an Internet Protocol (IP)-based PS (packet switched) core network, an Evolved Packet Core (EPC), and an access network such as LTE/UTRAN. UMTS is an evolved network.

- NodeB: base station of GERAN/UTRAN. It is installed outdoors and the coverage is macro cell scale.

- eNodeB/eNB: base station of E-UTRAN. It is installed outdoors and the coverage is macro cell scale.

- UE (User Equipment): User equipment. The UE may be referred to in terms of a terminal (UE), a mobile equipment (ME), a mobile station (MS), and the like. In addition, the UE may be a portable device such as a laptop computer, a mobile phone, a personal digital assistant (PDA), a smart phone, a multimedia device, or the like, or a non-portable device such as a personal computer (PC) or in-vehicle device. In the context of MTC, the term UE or terminal may refer to an MTC device.

- HNB (Home NodeB): As a base station of the UMTS network, it is installed indoors and the coverage is micro cell scale.

- HeNB (Home eNodeB): As a base station of the EPS network, it is installed indoors and the coverage is micro-cell scale.

- MME (Mobility Management Entity): a network node of the EPS network that performs mobility management (MM), session management (SM) functions.

- PDN-GW (Packet Data Network-Gateway)/PGW/P-GW: A network node of an EPS network that performs UE IP address allocation, packet screening and filtering, charging data collection functions, and the like.

- Serving Gateway (SGW) / S-GW: mobility anchor (mobility anchor), packet routing (routing), idle mode packet buffering, a function of triggering the MME to paging the UE, etc. Network node of the EPS network .

- PCRF (Policy and Charging Rule Function): A network node of the EPS network that performs policy decision to dynamically apply QoS and charging policies differentiated for each service flow.

- OMA DM (Open Mobile Alliance Device Management): A protocol designed to manage mobile devices such as cell phones, PDAs, and portable computers. Device configuration, firmware upgrade, error report, etc. perform the function of

- OAM (Operation Administration and Maintenance): A set of network management functions that provide network fault indication, performance information, and data and diagnostic functions.

- NAS (Non-Access Stratum): the upper end of the control plane (control plane) between the UE and the MME (stratum). As a functional layer for exchanging signaling and traffic messages between the UE and the core network in the LTE / UMTS protocol stack, the session supports mobility of the UE and establishes and maintains an IP connection between the UE and the PDN GW It supports management procedures and IP address management.

- EMM (EPS Mobility Management): As a sub-layer of the NAS layer, the EMM is in the "EMM-Registered" or "EMM-Deregistered" state depending on whether the UE is network attached or detached. there may be

- ECM (EMM Connection Management) connection (connection): a signaling connection (connection) for the exchange (exchange) of the NAS message established (established) between the UE and the MME. The ECM connection is a logical connection consisting of an RRC connection between the UE and the eNB and an S1 signaling connection between the eNB and the MME. When the ECM connection is established/terminated, the RRC and S1 signaling connections are also established/terminated. The established ECM connection means having an RRC connection established with the eNB to the UE, and means having an S1 signaling connection established with the eNB to the MME. Depending on whether a NAS signaling connection, that is, an ECM connection is established, the ECM may have a status of "ECM-Connected" or "ECM-Idle".

- AS (Access-Stratum): Includes the protocol stack between the UE and the wireless (or access) network, and is responsible for data and network control signal transmission.

- NAS configuration (configuration) MO (Management Object): MO (Management object) used in the process of setting parameters (parameters) related to NAS function (Functionality) to the UE.

- PDN (Packet Data Network): A network in which a server supporting a specific service (eg, Multimedia Messaging Service (MMS) server, Wireless Application Protocol (WAP) server, etc.) is located.

- PDN Connection: A logical connection between the UE and the PDN, expressed by one IP address (one IPv4 address and/or one IPv6 prefix).

- APN (Access Point Name): A string that refers to or distinguishes a PDN. In order to access a requested service or network, it goes through a specific P-GW, which means a name (string) predefined in the network to find this P-GW. (e.g. internet.mnc012.mcc345.gprs)

- RAN (Radio Access Network): A unit including a NodeB, an eNodeB, and a Radio Network Controller (RNC) for controlling them in a 3GPP network. It exists between UEs and provides connectivity to the core network.

- HLR (Home Location Register)/HSS (Home Subscriber Server): A database having subscriber information in the 3GPP network. The HSS may perform functions such as configuration storage, identity management, and user state storage.

- PLMN (Public Land Mobile Network): A network configured for the purpose of providing mobile communication services to individuals. It may be configured to be divided for each operator.

-ANDSF (Access Network Discovery and Selection Function): Provides a policy to discover and select the access allowed by the UE in the operator unit as one network entity.

- EPC path (or infrastructure data path): User plane communication path through EPC

- E-RAB (E-UTRAN Radio Access Bearer): refers to the concatenation of the S1 bearer and the corresponding data radio bearer. If the E-RAB exists, there is a one-to-one mapping between the E-RAB and the EPS bearer of the NAS.

- GPRS Tunneling Protocol (GTP): A group of IP-based communications protocols used to carry general packet radio service (GPRS) within GSM, UMTS and LTE networks. Within the 3GPP architecture, GTP and Proxy Mobile IPv6-based interfaces are specified on various interface points. GTP can be decomposed into several protocols (eg GTP-C, GTP-U and GTP'). GTP-C is used within the GPRS core network for signaling between Gateway GPRS Support Nodes (GGSN) and Serving GPRS Support Nodes (SGSN). In the GTP-C, the SGSN activates a session for the user (eg, activates a PDN context), deactivates the same session, and adjusts the quality of service parameters. ), or update a session for a subscriber who has just operated from another SGSN. GTP-U is used to carry user data within the GPRS core network and between the radio access network and the core network. 1 is a diagram illustrating a schematic structure of an Evolved Packet System (EPS) including an Evolved Packet Core (EPC).

- Cell as a radio resource: The 3GPP LTE / LTE-A system uses the concept of a cell to manage radio resources, and a cell associated with a radio resource is a cell of a geographic area. is separated from A "cell" associated with a radio resource is defined as a combination of downlink resources (DL resources) and uplink resources (UL resources), that is, a combination of a DL carrier and a UL carrier. A cell may be configured with a DL resource alone or a combination of a DL resource and a UL resource. When carrier aggregation is supported, linkage between a carrier frequency of a DL resource and a carrier frequency of a UL resource may be indicated by system information. Here, the carrier frequency means a center frequency of each cell or carrier. In particular, a cell operating on a primary frequency is referred to as a primary cell (Pcell), and a cell operating on a secondary frequency is referred to as a secondary cell (Scell). . The Scell refers to a cell that can be used to allow setup after RRC (Radio Resource Control) connection establishment is performed and to provide additional radio resources. According to the capabilities of the UE, the Scell may form a set of serving cells for the UE together with the Pcell. In the case of a UE in the RRC_CONNECTED state but carrier aggregation is not configured or does not support carrier aggregation, there is only one serving cell configured only as a PCell. On the other hand, a "cell" of a geographic area can be understood as coverage in which a node can provide a service using a carrier, and a "cell" of a radio resource is a frequency range configured by the carrier. It is related to bandwidth (BW). The downlink coverage, which is a range in which a node can transmit a valid signal, and the uplink coverage, which is a range in which a valid signal can be received from the UE, depend on the carrier carrying the corresponding signal. It is also associated with the coverage of a "cell". Therefore, the term "cell" may be used to mean sometimes coverage of a service by a node, sometimes a radio resource, and sometimes a range that a signal using the radio resource can reach with an effective strength.

EPC is a key element of System Architecture Evolution (SAE) to improve the performance of 3GPP technologies. SAE corresponds to a research task to determine a network structure that supports mobility between various types of networks. SAE aims to provide an optimized packet-based system, for example, supporting various radio access technologies based on IP and providing improved data transmission capability.

Specifically, the EPC is a core network of an IP mobile communication system for a 3GPP LTE system, and can support packet-based real-time and non-real-time services. In the existing mobile communication system (ie, 2nd or 3rd generation mobile communication system), the core network through two distinct sub-domains of CS (Circuit-Switched) for voice and PS (Packet-Switched) for data. The function has been implemented. However, in the 3GPP LTE system, which is an evolution of the 3G mobile communication system, sub-domains of CS and PS are unified into one IP domain. That is, in the 3GPP LTE system, the connection between the UE and the UE having IP capability is an IP-based base station (eg, eNodeB (evolved Node B)), EPC, application domain (eg, IMS ( IP Multimedia Subsystem)). That is, the EPC is an essential structure for implementing an end-to-end IP service.

The EPC may include various components, and in FIG. 1 , some of them are a Serving Gateway (SGW), a Packet Data Network Gateway (PDN GW), a Mobility Management Entity (MME), and a Serving General Packet (GPRS) (SGSN). Radio Service) Supporting Node) and ePDG (enhanced Packet Data Gateway) are shown.

The SGW (or S-GW) is an element that functions as a boundary point between the radio access network (RAN) and the core network and maintains a data path between the eNB and the PDN GW. In addition, when the UE moves over an area served by the eNB, the SGW serves as a local mobility anchor point. That is, packets may be routed through the SGW for mobility within the E-UTRAN (Evolved-Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network defined after 3GPP Release-8). In addition, the SGW provides mobility with other 3GPP networks (RANs defined before 3GPP Release-8, for example, UTRAN or GERAN (Global System for Mobile Communication (GSM)/Enhanced Data rates for Global Evolution (EDGE) Radio Access Network)). It may serve as an anchor point for

The PDN GW (or P-GW) corresponds to the termination point of the data interface towards the packet data network. The PDN GW may support policy enforcement features, packet filtering, charging support, and the like. In addition, mobility management between 3GPP networks and non-3GPP networks (eg, untrusted networks such as Interworking Wireless Local Area Network (I-WLAN), Code Division Multiple Access (CDMA) networks or trusted networks such as WiMax). It can serve as an anchor point for

Although the example of the network structure of FIG. 4 shows that the SGW and the PDN GW are configured as separate gateways, the two gateways may be implemented according to a single gateway configuration option.

The MME is an element that performs signaling and control functions to support access to a network connection of the UE, allocation of network resources, tracking, paging, roaming, and handover. The MME controls control plane functions related to subscriber and session management. The MME manages numerous eNBs and performs signaling for selection of a conventional gateway for handover to other 2G/3G networks. In addition, the MME performs functions such as security procedures, terminal-to-network session handling, and idle terminal location management.

The SGSN handles all packet data such as user's mobility management and authentication to other 3GPP networks (eg, GPRS networks).

The ePDG acts as a security node for untrusted non-3GPP networks (eg, I-WLAN, WiFi hotspots, etc.).

As described with reference to FIG. 4 , the UE having IP capability provides IP provided by the operator (ie, operator) via various elements in the EPC on the basis of 3GPP access as well as non-3GPP access. A service network (eg, IMS) may be accessed.

4 also shows various reference points (eg, S1-U, S1-MME, etc.). In the 3GPP system, a conceptual link connecting two functions existing in different functional entities of E-UTRAN and EPC is defined as a reference point. Table 1 below summarizes the reference points shown in FIG. 4 . In addition to the examples in Table 1, various reference points may exist according to the network structure.

reference point	description
S1-MME	Reference point for the control plane protocol between E-UTRAN and MME
S1-U	Reference point between E-UTRAN and Serving GW for the per bearer user plane tunneling and inter eNodeB path switching during handover
S3	Reference point between MME and SGSN providing user and bearer information exchange for mobility between 3GPP access networks in idle and/or active state. This reference point may be used for intra-PLMN or inter-PLMN (eg, in case of inter-PLMN handover)) (It enables user and bearer information exchange for inter 3GPP access network mobility in idle and/or active state This reference point can be used intra-PLMN or inter-PLMN (eg in the case of Inter-PLMN HO).)
S4	A reference point between the SGW and SGSN that provides related control and mobility support between the GPRS core and the 3GPP anchor function of the SGW. In addition, if Direct Tunnel is not established, it provides the user plane tunneling .)
S5	Reference point providing user plane tunneling and tunnel management between SGW and PDN GW. Used for SGW relocation due to terminal mobility and when a connection to a PDN GW where the SGW is not co-located is required for required PDN connectivity (It provides user plane tunneling and tunnel management between Serving GW and PDN GW. It is used for Serving GW relocation due to UE mobility and if the Serving GW needs to connect to a non-collocated PDN GW for the required PDN connectivity.)
S11	Reference point for control plane protocol between MME and SGW
SGi	Reference point between PDN GW and PDN. Here, the PDN may be an operator external public or private PDN, or an operator-internal PDN (eg, IMS service). This reference point corresponds to Gi of 3GPP access (It is the reference point between the PDN GW and the packet data network. Packet data network may be an operator external public or private packet data network or an intra operator packet data network, eg for This reference point corresponds to Gi for 3GPP accesses.)

Among the reference points shown in FIG. 4 , S2a and S2b correspond to non-3GPP interfaces. S2a is a reference point that provides the user plane with trusted non-3GPP access and related control and mobility support between PDN GWs. S2b is a reference point that provides related control and mobility support between the ePDG and PDN GW to the user plane.

5 shows an example of a network structure of an evolved universal terrestrial radio access network (E-UTRAN) to which this specification can be applied.

The E-UTRAN system is a system evolved from the existing UTRAN system, and may be, for example, a 3GPP LTE/LTE-A system. Communication networks are widely deployed to provide various communication services such as voice (eg, Voice over Internet Protocol (VoIP)) via IMS and packet data.

Referring to FIG. 4 , the E-UMTS network includes an E-UTRAN, an EPC, and one or more UEs. The E-UTRAN consists of eNBs that provide a control plane and a user plane protocol to the UE, and the eNBs are connected through an X2 interface.

An X2 user plane interface (X2-U) is defined between the eNBs. The X2-U interface provides non-guaranteed delivery of a user plane packet data unit (PDU). An X2 control plane interface (X2-CP) is defined between two neighboring eNBs. X2-CP performs functions such as context transfer between eNBs, control of a user plane tunnel between a source eNB and a target eNB, transfer of a handover related message, and uplink load management.

The eNB is connected to the terminal through the wireless interface and is connected to the evolved packet core (EPC) through the S1 interface.

The S1 user plane interface (S1-U) is defined between the eNB and a serving gateway (S-GW). The S1 control plane interface (S1-MME) is defined between the eNB and a mobility management entity (MME). The S1 interface performs an evolved packet system (EPS) bearer service management function, a non-access stratum (NAS) signaling transport function, network sharing, an MME load balancing function, and the like. The S1 interface supports many-to-many-relation between the eNB and the MME/S-GW.

MME is NAS signaling security (security), AS (Access Stratum) security (security) control, CN (Core Network) inter-node (Inter-CN) signaling to support mobility between 3GPP access networks, (perform and control paging retransmission) Including) idle (IDLE) mode UE accessibility (reachability), (for idle and active mode terminals) tracking area identifier (TAI: Tracking Area Identity) management, PDN GW and SGW selection, MME for handover in which the MME is changed Bearer management functions including selection, SGSN selection for handover to 2G or 3G 3GPP access network, roaming, authentication, dedicated bearer establishment, Public Warning System (PWS) System) (including Earthquake and Tsunami Warning System (ETWS) and Commercial Mobile Alert System (CMAS)) message transmission.

6 is a diagram illustrating an architecture of a general NR-RAN.

Referring to FIG. 6 , the NG-RAN node may be one of the following.

- gNB providing NR user plane and control plane protocols towards the UE; or

- ng-eNB providing E-UTRA user plane and control plane protocols towards the UE.

The gNB and the ng-eNB are connected to each other through the Xn interface. In addition, gNB and ng-eNB via NG interface to 5GC, more specifically via NG-C interface, Access and Mobility Management Function (AMF), user plane function via NG-U interface ( UPF: User Plane Function) (refer to 3GPP TS 23.501 [3]).

For reference, the architecture for functional separation and the F1 interface are defined in 3GPP TS 38.401 [4].

7 shows an example of a general architecture of 5G. The following is a description of each reference interface and node in FIG. 7 .

Access and Mobility Management Function (AMF: Access and Mobility Management Function) is a CN inter-node signaling for mobility between 3GPP access networks, a radio access network (RAN: Radio Access Network) CP interface (N2) termination (termination), NAS It supports functions such as the end of signaling (N1), registration management (registration area management), idle mode UE accessibility (reachability), support of network slicing, and SMF selection.

Some or all functions of AMF may be supported within a single instance of one AMF.

A data network (DN: Data network) means, for example, an operator service, Internet access, or a third party service. The DN transmits a downlink protocol data unit (PDU) to the UPF or receives a PDU transmitted from the UE from the UPF.

A policy control function (PCF) provides a function of receiving information about a packet flow from an application server and determining policies such as mobility management and session management.

A session management function (SMF) provides a session management function, and when the UE has a plurality of sessions, it may be managed by a different SMF for each session.

Some or all functions of the SMF may be supported within a single instance of one SMF.

Unified Data Management (UDM) stores user subscription data, policy data, and the like.

User plane function (UPF) delivers the downlink PDU received from the DN to the UE via (R)AN, and delivers the uplink PDU received from the UE via (R)AN to the DN. .

Application Function (AF) supports service provision (e.g., application impact on traffic routing, network capability exposure access, interaction with policy framework for policy control, etc.) to interact with the 3GPP core network.

(Radio) Access Network ((R)AN: (Radio) Access Network) is an evolved version of 4G radio access technology, evolved E-UTRA (E-UTRA) and new radio access technology (NR: New Radio) ( For example, gNB) is a generic term for a new radio access network that supports both.

gNB has functions for radio resource management (ie, Radio Bearer Control, Radio Admission Control, Connection Mobility Control), and dynamic resource allocation to the UE in uplink/downlink. It supports functions such as dynamic allocation of resources (ie, scheduling)).

User Equipment (UE) refers to user equipment.

In the 3GPP system, a conceptual link connecting NFs in the 5G system is defined as a reference point.

N1 is the reference point between the UE and AMF, N2 is the reference point between (R)AN and AMF, N3 is the reference point between (R)AN and UPF, N4 is the reference point between SMF and UPF, N6 the reference point between UPF and the data network , N9 is a reference point between the two core UPFs, N5 is a reference point between PCF and AF, N7 is a reference point between SMF and PCF, N24 is a PCF in a visited network and a PCF in a home network Reference point, N8 is a reference point between UDM and AMF, N10 is a reference point between UDM and SMF, N11 is a reference point between AMF and SMF, N12 is a reference point between AMF and Authentication Server function (AUSF: Authentication Server function), N13 is Reference point between UDM and AUSF, N14 is a reference point between two AMFs, N15 is a reference point between PCF and AMF in case of a non-roaming scenario, and a reference point between PCF and AMF in a visited network in case of a roaming scenario , N16 is the reference point between the two SMFs (in the roaming scenario, the reference point between the SMF in the visited network and the SMF between the home network), N17 is the reference point between the AMF and the 5G-EIR (Equipment Identity Register), and N18 is the AMF and the unstructured UDSF (UDSF). Data Storage Function), N22 is the reference point between AMF and Network Slice Selection Function (NSSF), N23 is the reference point between PCF and NWDAF (Network Data Analytics Function), N24 is the reference point between NSSF and NWDAF, N27 is visit Reference point between NRF (Network Repository Function) in network and NRF in home network, N31 is N in visited network Reference point between SSF and NSSF in home network, N32 is a reference point between SEPP (Security Protection Proxy) in visited network and SEPP in home network, N33 is reference point between NEF (Network Exposure Function) and AF, N40 is SMF and CHF ( A reference point between the charging function, N50 means a reference point between the AMF and the Circuit Bearer Control Function (CBCF).

Meanwhile, FIG. 7 exemplifies a reference model for a case in which the UE accesses one DN using one PDU session for convenience of description, but is not limited thereto.

In the present specification, Hybrid Automatic Repeat and reQuest (HARQ) is a kind of error control method. HARQ-ACK (HARQ acknowledgment) transmitted through downlink is used for error control on uplink data, and HARQ-ACK transmitted through uplink is used for error control on downlink data. The transmitter performing the HARQ operation waits for an acknowledgment (ACK) after transmitting data (eg, transport block, codeword). The receiving end performing the HARQ operation sends a positive acknowledgment (ACK) only when data is properly received, and sends a negative acknowledgment (negative ACK, NACK) when an error occurs in the received data. When the transmitting end receives the ACK, it can transmit (new) data, and when it receives the NACK, it can retransmit the data. After the BS transmits scheduling information and data according to the scheduling information, a time delay occurs until ACK/NACK is received from the UE and retransmission data is transmitted. Such a time delay is caused by a channel propagation delay and a time taken for data decoding/encoding. Therefore, when new data is transmitted after the current HARQ process is finished, a gap occurs in data transmission due to a time delay. Accordingly, a plurality of independent HARQ processes are used to prevent gaps in data transmission during the time delay period. For example, if there are 7 transmission opportunities between the initial transmission and the retransmission, the communication device may operate 7 independent HARQ processes to perform data transmission without a gap. Utilizing a plurality of parallel HARQ processes, UL/DL transmission may be continuously performed while waiting for HARQ feedback for a previous UL/DL transmission.

In the present specification, channel state information (CSI) refers to information capable of indicating the quality of a radio channel (or link) formed between a UE and an antenna port. CSI is a channel quality indicator (channel quality indicator, CQI), precoding matrix indicator (PMI), CSI-RS resource indicator (CSI-RS resource indicator, CRI), SSB resource indicator (SSB resource indicator, SSBRI) , may include at least one of a layer indicator (LI), a rank indicator (RI), and a reference signal received power (RSRP).

In this specification, frequency division multiplexing (FDM) may mean transmitting/receiving signals/channels/users in different frequency resources, and time division multiplexing (TDM) is It may mean transmitting/receiving signals/channels/users in different time resources.

In the present specification, frequency division duplex (FDD) refers to a communication method in which uplink communication is performed on an uplink carrier and downlink communication is performed on a downlink carrier linked to the uplink carrier, and time division Duplex (time division duplex, TDD) refers to a communication method in which uplink communication and downlink communication are performed by dividing time on the same carrier.

For background art, terms, abbreviations, etc. used in this specification, reference may be made to matters described in standard documents published before this specification. For example, you can refer to the following documents:

3GPP LTE

- 3GPP TS 36.211: Physical channels and modulation

- 3GPP TS 36.212: Multiplexing and channel coding

- 3GPP TS 36.213: Physical layer procedures

- 3GPP TS 36.214: Physical layer; Measurements

- 3GPP TS 36.300: Overall description

- 3GPP TS 36.304: User Equipment (UE) procedures in idle mode

- 3GPP TS 36.306: User Equipment (UE) radio access capabilities

- 3GPP TS 36.314: Layer 2 - Measurements

- 3GPP TS 36.321: Medium Access Control (MAC) protocol

- 3GPP TS 36.322: Radio Link Control (RLC) protocol

- 3GPP TS 36.323: Packet Data Convergence Protocol (PDCP)

- 3GPP TS 36.331: Radio Resource Control (RRC) protocol

- 3GPP TS 36.413: S1 Application Protocol (S1AP)

- 3GPP TS 36.423: X2 Application Protocol (X2AP)

- 3GPPP TS 22.125: Unmanned Aerial System support in 3GPP; Stage 1

- 3GPP TS 23.303: Proximity-based services (Prose); Stage 2

- 3GPP TS 23.401: General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio

Access Network (E-UTRAN) access

- 3GPP TS 23.402: Architecture enhancements for non-3GPP accesses

- 3GPP TS 23.286: Application layer support for V2X services; Functional architecture and information flows

- 3GPP TS 24.301: Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3

- 3GPP TS 24.302: Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3

- 3GPP TS 24.334: Proximity-services (ProSe) User Equipment (UE) to ProSe function protocol aspects; Stage 3

- 3GPP TS 24.386: User Equipment (UE) to V2X control function; protocol aspects; Stage 3

3GPP NR

- 3GPP TS 38.211: Physical channels and modulation

- 3GPP TS 38.212: Multiplexing and channel coding

- 3GPP TS 38.213: Physical layer procedures for control

- 3GPP TS 38.214: Physical layer procedures for data

- 3GPP TS 38.215: Physical layer measurements

- 3GPP TS 38.300: NR and NG-RAN Overall Description

- 3GPP TS 38.304: User Equipment (UE) procedures in idle mode and in RRC inactive state

- 3GPP TS 38.321: Medium Access Control (MAC) protocol

- 3GPP TS 38.322: Radio Link Control (RLC) protocol

- 3GPP TS 38.323: Packet Data Convergence Protocol (PDCP)

- 3GPP TS 38.331: Radio Resource Control (RRC) protocol

- 3GPP TS 37.324: Service Data Adaptation Protocol (SDAP)

- 3GPP TS 37.340: Multi-connectivity; Overall description

- 3GPP TS 23.501: System Architecture for the 5G System

- 3GPP TS 23.502: Procedures for the 5G System

- 3GPP TS 23.503: Policy and Charging Control Framework for the 5G System; Stage 2

- 3GPP TS 24.501: Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3

- 3GPP TS 24.502: Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks

- 3GPP TS 24.526: User Equipment (UE) policies for 5G System (5GS); Stage 3

(3GPP TS 23.287 v1.1.0, clause 4)

Architectural Models and Concepts

1. General

V2X communication has two operating modes: V2X communication through PC5 reference point and V2X communication through Uu reference point. These two modes of operation can be used independently by the UE for transmission and reception.

V2X communication through the PC5 reference point is supported by LTE and / or NR.

V2X communication through Uu reference point is supported by E-UTRA connected to 5GC and/or NR connected to 5GC.

2. Architectural Reference Model

1) PC5 and Uu based on V2X architecture reference model

(1) Non-roaming 5G System architecture through PC5 and Uu reference point

8 illustrates a non-roaming 5G system architecture to which this specification can be applied. Referring to FIG. 8 , a higher level of non-roaming 5G system architecture through PC5 and Uu reference points is presented.

(2) Roaming 5G System architecture for V2X communication through PC5 and Uu reference point

9 and 10 illustrate a Roaming 5G system architecture to which this specification can be applied. 9 and 10, a higher level of the Roaming 5G system architecture for V2X communication through PC5 and Uu reference point is presented. 9 and 10 , UE A uses a subscription of HPLMN.

(3) Inter-PLMN 5G System architecture for V2X communication through PC5 reference point

For communication between PLMN V2X through a PC5 reference point, PC5 parameters need to be configured in a consistent manner between UEs within a specific region. The architecture of the Inter-PLMN PC5 case is similar to the architecture defined in 2.1).(1).

2) AF-based service parameter provisioned for V2X communication

The 5G system provides the NEF service that enables communication between the PLMN and the NF of the V2X Application Server.

11 is an example of a provisioned AF-based service parameter to which this specification is applied. Referring to Figure 11, the higher level of the AF-based service parameter provisioned for V2X communication is presented. V2X Application Server can provide V2X service parameters to PLMN through NEF. NEF stores V2X service parameters in UDR.

3) Reference point

V1: Reference point of V2X application of UE and V2X Application Server. This reference point is outside the scope of this standard.

V5: Reference point between V2X applications of the UE. This reference point was not specified in this release of this specification.

PC5: A reference point between UEs, including LTE-based PC5 and/or NR-based PC5.

N1: For V2X service, in addition to related functions defined in TS 23.501 [6] for N1, for V2X service, it is also used to deliver V2X policies and parameters (including service permission) from AMF to UE.

N2: In addition to the related functions defined in TS 23.501 [6] for N2, for V2X service, it is also used to transfer V2X policies and parameters (including service permission) from AMF to NG-RAN.

Uu: the reference point between the UE and the NG-RAN.

4) Service-based interface

Nudm: In the case of Nudm, in addition to the related services defined in TS 23.501 [6], in the case of V2X services, the initial registration procedure to notify the AMF that the subscription information has changed or the UE Configuration Update (UCU) procedure to AMF related to the V2X service subscription To give information, the services provided by UDM are used.

Npcf: In the case of Npcf, in addition to the related services defined in TS 23.501 [6], in the case of V2X services, it is used to provide V2X service related parameters to the UE. This service is also used in AMF to update the UE context related to the V2X service.

Nudr: In addition to the related services defined in TS 23.501 [6] for Nudr, in the case of V2X service, the update of V2X service related information is notified to the PCF using the service provided by UDR.

Nnef: In the case of V2X service, in addition to the related services defined in TS 23.501 [6] for Nnef, V2X Application Server uses the services provided by NEF to update V2X service related information of 5GC.

3. Architectural reference model for interworking with EPS V2X

The interaction between 5GS V2X and EPS V2X does not require a new interface between the 5GS V2X architecture and the EPS V2X architecture and does not affect the existing network functional entities of EPC and 5GC.

12 illustrates an architectural reference model to which this specification can be applied.

4. Functional entities

1) UE

The UE may support the following functions in addition to the functions defined in TS 23.501 [6].

- Report V2X Capability and V2X PC5 Capability information to 5GC through N1 reference point.

- Receive V2X parameters from 5GC through N1 reference point.

- V2X communication procedure through PC5 reference point

- Configure parameters for V2X communication (e.g. target layer-2 ID, radio resource parameters, V2X Application Server address information, mapping between service types and V2X frequencies, see clause 5.1), these parameters are preset in the UE, or In this case, it can be provisioned or updated by sending a signal from the HPLMN's PCF to the N1 reference point or from the V2X Application Server to the V1 reference point or higher.

2) PCF

In addition to the functions defined in TS 23.501 [6], PCF includes the ability to provision UEs and AMFs using parameters required to use V2X communication.

- Provision of UE as authentication and policy parameters for V2X communication through PC5 reference point

- UE provisioning using policy parameters for V2X communication through Uu reference point

- Provisioning AMF with PC5 QoS parameters as defined in clause 5.4.2 used by NG-RAN

- Retrieve V2X parameters from UDR

3) V2X Application Server

V2X Application Server (V2X AS) includes AF function and can support at least the following functions.

For V2X service handling,

- Receive uplink data from UE via unicast

- Transmits downlink data to the UE through unicast.

- Request to notify NEF of possible QoS change in geographic area

For V2X service parameter provisioning

- 5GC provisioning using V2X communication parameters via PC5 and Uu reference point

- Provide UE with V2X communication parameters through PC5 reference point and/or Uu reference point

Note: V2X Application Server and V2X service parameter provisioning for V2X service processing may be the same or different.

4) AMF

AMF performs the following functions in addition to the functions defined in TS 23.501 [6].

- Obtain V2X-related subscription information from UDM and store it as part of UE context data.

- Obtain PC5 QoS information related to V2X from PCF and store it as part of UE context data.

-Provide NG-RAN through indication of UE approval status for V2X communication through PC5 reference point

- Provides NG-RAN with PC5 QoS parameters related to V2X communication

5) UDM

UDM performs the following functions in addition to the functions defined in TS 23.501 [6].

- Subscription management for V2X communication through PC5 reference point

6) UDR

UDR performs the following functions in addition to the functions defined in TS 23.501 [6].

- Save V2X service parameters

3GPP TS 23.287 v1.1.0, clause 5.2.1

V2X communication via PC5 reference point

1. General

For V2X communication, there are two types of LTE-based PC5 reference point defined in TS 23.285[8] and NR-based PC5 reference point defined in clause 4.2.3. The UE may use one or both PC5 types for V2X communication according to the services supported by the UE. V2X communication via PC5 reference point supports roaming and inter-PLMN operation. V2X communication through the PC5 reference point is supported when the UE is "serviced by NR or E-UTRA" or the UE is "not serviced by NR or E-UTRA".

The UE is authorized to send and receive V2X messages when it has valid authorization and configuration specified in 5.1.2.

The characteristics of V2X communication through PC5 reference point are as follows.

- V2X communication through LTE-based PC5 reference point is not connected, that is, broadcast mode in the access layer (AS) layer, no connection establishment signal through PC5

- V2X communication through NR-based PC5 reference point supports broadcast mode, groupcast mode, and unicast mode in the AS layer. The UE indicates the communication mode of the V2X message for the AS layer. Signaling is supported through the control plane through the PC5 reference point for unicast mode communication management.

- Supports inter-UE communication via PC5 user plane

- Exchange of V2X messages between UEs through PC5 user plane

- Both IP-based and non-IP-based V2X messages are supported via PC5 reference point

- For IP-based V2X messages, only IPv6 is used. IPv4 not supported.

The identifier used for V2X communication through the PC5 reference point is described in Section 5.6.1. The UE determines the type of PC5 reference point and Tx profile to use for the transmission of a particular packet based on the settings described in 5.1.2. When the LTE-based PC5 reference point is selected, the QoS processing procedure is defined in TS 23.285 [8]. If an NR-based PC5 reference point is selected, QoS handling and procedures are defined in clauses 5.4.1 and 6.3.

If the UE has an emergency session in progress through the IMS, the emergency session through the IMS should take precedence over V2X communication through the PC5 reference point.

NOTE: Emergency sessions via IMS setup are based on appropriate regional/national regulatory requirements and operator policies as defined in TS 23.501 [6].

2. Broadcast mode communication via PC5 reference point

Broadcast mode is supported in both LTE-based PC5 reference point and NR-based PC5 reference point. Therefore, when the broadcast mode is selected for communication through the PC5 reference point, it is necessary to perform the PC5 RAT selection based on the settings described in 5.1.2.

For the LTE-based PC5 reference point, broadcast mode is the only supported communication mode, and the operational details are defined in TS 23.285 [8].

For NR-based PC5 reference points, broadcast mode also supports enhanced QoS handling as defined in 5.4.1.

3. Groupcast mode communication via PC5 reference point

Groupcast communication mode is supported only through NR based PC5 reference point.

QoS handling for groupcast communication mode is defined in Section 5.4.1.

4. Unicast mode communication via PC5 reference point

Unicast communication mode is supported only through NR based PC5 reference point.

13 is an example of a PC5 unicast link to which this specification can be applied.

The following principles apply when V2X communication is performed over a PC5 unicast link.

- PC5 unicast link between two UEs allows V2X communication between one or more peer V2X service pairs in these UEs. All V2X services of the UE using the same PC5 unicast link use the same application layer ID.

NOTE 1: The application layer ID may change over time as described in clauses 5.6.1.1 and 6.3.3.2 for privacy reasons. This does not force the PC5 unicast link to be re-established.

- One PC5 unicast link supports one or more V2X services (eg PSID or ITS-AID). If these V2X services are associated with at least a peer application layer ID pair for this PC5 unicast link. For example, as shown in FIG. 13 , UE A and UE B have two PC5 unicast links, one between peer application layer ID 1/UE A and application layer ID 2/UE B and one It may be between peer application layer ID 3/UE A and application layer ID 4/UE B.

Remark 2: The source UE does not need to know whether different target application layer IDs for different PC5 unicast links belong to the same target UE.

- PC5 unicast link supports, for example, V2X communication using a single network layer protocol. i.e. IP or non-IP.

- The PC5 unicast link supports the per-flow QoS model specified in Section 5.4.1.

When the application layer of the UE starts data transmission for V2X service that requires unicast communication mode through PC5 reference point:

- If the peer application layer ID and the network layer protocol pair of this PC5 unicast link are the same as that required by the UE's application layer for this V2X service, the UE shall reuse the existing PC5 unicast link, as specified in clause 6.3.3.4. As such, the existing PC5 unicast link must be modified to add this V2X service.

- The UE triggers the establishment of a new PC5 unicast link as specified in clause 6.3.3.1.

After successful establishment of the PC5 unicast link, UE A and UE B use the same pair of Layer-2 IDs for subsequent PC5-S signaling message exchange and V2X service data transmission as specified in Section 5.6.1.4. The V2X layer of the transmitting UE determines whether the transmission is for a PC5-S signaling delivery message (ie, direct communication request/accept, link identifier update request/response, connection release request/response, link modification request/accept) or V2X service data. It is indicated on the AS layer whether it is for

For every PC5 unicast link, the UE self-assigns a distinct PC5 link identifier that uniquely identifies the UE's PC5 unicast link for the lifetime of the PC5 unicast link. Each PC5 unicast link is associated with a unicast link profile that includes:

- service type (eg PSID or ITS-AID), application layer ID and layer-2 ID of UE A; and

- Application Layer ID and Layer 2 ID of UE B; and

- Network layer protocol used for PC5 unicast links; and

- PC5 QoS Flow Identifier Set (PFI) for each V2X service Each PFI is associated with a QoS parameter (ie, PQI and optional range).

For privacy reasons, the application layer ID and layer 2 ID may change as described in clauses 5.6.1.1 and 6.3.3.2 over the lifetime of the PC5 unicast link, and therefore should be updated in the unicast link profile accordingly. . The UE uses the PC5 Link Identifier to indicate the PC5 unicast link to the V2X Application layer, so the V2X Application layer identifies the corresponding PC5 unicast link even if there is more than one unicast link associated with one service type (e.g.: UE establishes multiple unicast links with multiple UEs for the same service type).

The unicast link profile shall be updated accordingly after modifying the Layer 2 link for the established PC5 unicast link as specified in 6.3.3.4.

5. IP address assignment

In the case of unicast mode of V2X communication through PC5 reference point, the following mechanism for IP address/prefix assignment can be used.

a) Autoconfiguration of IPv6 stateless addresses specified in RFC 4862 [21] for IPv6 prefix assignment, one of the two UEs acting as the IPv6 default router;

NOTE: During secure layer 2 link establishment, the UE acting as the IPv6 default router is negotiated by exchanging the IP address configuration described in clause 6.3.3.1.

b) IPv6 link-local addresses as defined in RFC 4862 [21] are formed locally by the UE. IPv6 link-local addresses are exchanged during establishment of a security layer 2 link to a PC5 reference point as described in 6.3.3.1. The UE shall disable duplicate address detection after the layer 2 link is established.

3GPP TS 23.287 v1.1.0, clause 6.3

V2X communication procedure through PC5 reference point

1. Broadcast mode V2X communication through PC5 reference point

In order to perform V2X communication through the PC5 reference point in the broadcast mode operation, the UE is set with the relevant information described in 5.1.2.

14 is a diagram illustrating a procedure for a broadcast mode of V2X communication using PC5.

1) The receiving terminal determines a destination Layer-2 ID for broadcast reception. The destination Layer-2 ID is transmitted to the AS layer of the receiving terminal for reception.

2) The V2X application layer of the transmitting terminal may provide a data unit, and may provide V2X application requirements (Application Requirements).

3) The transmitting terminal determines the destination Layer-2 ID for the broadcast. The transmitting terminal itself allocates a source Layer-2 ID.

4) One broadcast message transmitted by the transmitting terminal transmits V2X service data using the source Layer-2 ID and the destination Layer-2 ID.

Note: In step 4, there is only one broadcast message transmitted from the sending terminal.

2. Groupcast mode V2X communication through PC5 reference point

In order to perform the groupcast mode of V2X communication through the PC5 reference point, the UE is set with the relevant information as described in clause 5.1.2.1.

15 is a diagram illustrating a procedure for a groupcast mode of V2X communication using PC5.

1) V2X group management is performed through the V2X application layer.

2) The V2X application layer may provide a group identifier as described in 5.6.1.3 of the 3GPP 23.287 document. In addition, the V2X application layer may provide service requirements for the communication.

3) The transmitting terminal determines the source Layer-2 ID and the destination Layer-2 ID, and the receiving terminal determines the destination Layer-2 ID. The destination Layer-2 ID is delivered to the AS Layer of the receiving terminal for group communication transmission. The transmitting terminal determines the PC5 QoS parameters for the groupcast.

4) The transmitting terminal has a V2X service related to group communication. In addition, the transmitting terminal transmits the V2X service data using the source Layer-2 ID and the destination Layer-2 ID.

Note: The transmitting terminal in step 4 has only one groupcast message.

3. Unicast mode V2X communication through PC5 reference point

1) Establishment of Layer-2 link through PC5 reference point

In order to perform the unicast mode of V2X communication through the PC5 reference point, the UE is set with related information as described in clause 5.1.2.1.

16 is a diagram illustrating a procedure for a unicast mode of V2X communication using PC5.

(1) The UE determines a destination Layer-2 ID for receiving signaling for establishing a PC5 unicast link.

(2) The V2X application layer of terminal-1 provides application information for PC5 unicast communication. The application information includes the service type (eg, PSID or ITS-AID) of the V2X application and the initiating UE's Application Layer ID. The Application Layer ID of the target terminal may be included in the application information.

The V2X application layer of UE-1 may provide service requirements for the unicast communication. Terminal-1 determines PC5 QoS parameters and PFI.

If UE-1 decides to reuse the existing PC5 unicast link, UE triggers a Layer-2 link modification procedure.

(3) Terminal-1 transmits a Direct Communication Request message to initiate a unicast layer-2 link establishment procedure. The Direct Communication Request message includes:

- Source User Info: Application Layer ID of the initiating terminal (ie, Application Layer ID of Terminal-1)

- If the V2X application layer provides the target terminal Application Layer ID of step2, it includes the following information.

Target User Info: Application Layer ID of the target terminal (ie, Application Layer ID of Terminal-2)

- V2X Service Info: Information on V2X Service requesting Layer-2 link establishment (eg PSID or ITS-AID).

- Indication of whether to use IP communication

- IP Address Configuration: IP address configuration required for this link in IP communication and indicating one of the following values

"IPv6 router" or if the initiating UE supports the IPv6 address allocation mechanism, i.e. acts as an IPv6 router

"Does not support IPv6 address allocation" if the initiating UE does not support IPv6 address allocation mechanism

- Link Local IPv6 Address: If UE-1 does not support IPv6 IP address allocation mechanism, a locally formed link-local IPv6 address according to RFC 4862 [21], i.e., "IPv6 address allocation is not supported as directed by IP Address Configuration. not".

- QoS Info: Information about PC5 QoS Flow. For each PC5 QoS Flow, the PFI and corresponding PC5 QoS parameters (i.e., other parameters conditionally such as PQI and MFBR / GFBR). (FFS whether or not QoS information exchange is required)

The source Layer-2 ID and destination Layer-2 ID used to transmit the Direct Communication Request message are determined as specified in 　5.6.1.1 and 5.6.1.4.

Terminal-1 transmits a Direct Communication Request message through PC5 broadcast using the source Layer-2 ID and the destination Layer-2 ID.

(4) Direct Communication Accept message is transmitted to terminal-1 as follows.

4a. (Establishment of a Layer-2 link directed to the terminal) If the Target User Info is included in the Direct Communication Request message, it is transmitted to the target terminal (ie, Terminal-2 responds with a Direct Communication Accept message).

4b. (Layer-2 link establishment directed to V2X service) If Target User Info is not included in the Direct Communication Request message, it is transmitted to a terminal interested in using a known V2X service. To decide to establish a Layer-2 link, it responds to terminal-1's request by sending a Direct Communication Accept message (terminal-2 and terminal-4).

The Direct Communication Accept message contains:

- Source User Info: Application Layer ID of terminal sending Direct Communication Accept message

- QoS Info: Information about PC5 QoS Flow. For each PC5 QoS Flow, PFI and corresponding PC5 QoS parameters (i.e. PQI and conditionally other parameters such as MFBR/GFBR, etc.)

- IP Address Configuration: In case of IP communication, IP Address Configuration is required for these links, and one of the following values is indicated.

"IPv6 router" or if the target UE supports IPv6 address assignment mechanism, i.e. acts as an IPv6 router

"Does not support IPv6 address allocation" if target UE does not support IPv6 address allocation mechanism

- Link Local IPv6 Address: If the target UE does not support the IPv6 IP address allocation mechanism, the locally formed Link Local IPv6 Address based on RFC 4862 [21], i.e., IP Address Configuration, says "IPv6 address allocation is not supported" ", and UE-1 includes the Link Local IPv6 Address in the Direct Communication Request message. The target UE must contain a non-conflicting Link Local IPv6 Address.

If both UEs (i.e. initiating UE and destination UE) choose to use link-local IPv6 addresses, duplicate address detection as defined in RFC 4862 [21] shall be disabled.

Note 1: If the initiating UE or the target UE indicates support of an IPv6 router, the corresponding address setting procedure is performed after establishing the layer 2 link, and the link-local IPv6 address is ignored.

The source Layer-2 ID used to transmit the Direct Communication Accept message is determined as specified in clauses 5.6.1.1 and 5.6.1.4. The destination Layer-2 ID is set as the source Layer-2 ID of the received Direct Communication Request message.

Upon receiving the Direct Communication Accept message from the peer terminal, terminal-1 acquires the Layer-2 ID of the peer terminal used for future communication for signaling and data traffic for the unicast link.

The V2X layer of the terminal that has established the PC5 unicast link delivers the PC5 Link Identifier assigned to the unicast link and information related to the PC5 unicast link to the AS layer. Information related to the PC5 unicast link includes Layer-2 ID information (ie, source Layer-2 ID and destination Layer-2 ID). This allows the AS layer to maintain a PC5 Link Identifier along with information associated with the PC5 unicast link.

(5) 2X service data is transmitted through the unicast link established as follows:

C5 Link Identifier and PFI are provided to the AS layer along with V2X service data.

Terminal-1 transmits the V2X service data using the source Layer-2 ID and the destination Layer-2 ID. (ie, the Layer-2 ID of the peer terminal for the unicast link).

Since the PC5 unicast link is bidirectional, the peer terminal of terminal-1 may transmit V2X service data to terminal-1 through the unicast link with terminal-1.

2) Update link identifier for unicast link

17 illustrates a link identifier update procedure for a unicast link to which this specification can be applied.

Referring to Figure 17, due to privacy requirements, identifiers used for unicast mode (eg, application layer ID, source layer-2 ID, and IP address/prefix) of V2X communication through PC5 reference point are 5.6.1.1 and 5.6 It should change over time as specified in .1.4. This procedure is used to update the peer UE on the unicast link of the imminent change of the identifier used for this link before the identifier is changed to avoid service interruption.

If the UE has multiple unicast links using the same application layer ID or layer 2 ID, the UE needs to perform a link identifier update procedure for each unicast link.

(0) UE-1 and UE-2 have a unicast link as described in clause 6.3.3.1.

(1) UE-1 decides to change the identifier by changing the application layer ID or expiration of a timer, and transmits a Link Identifier Update Request message to UE-2 before changing the identifier.

The link identifier update request message contains the new identifier to use (including new application layer ID, new layer-2 ID, and new IP address/prefix if IP communication is used). New identifiers should be cyphed to protect privacy.

Note: Timers run per source layer 2 ID.

(2) UE-2 responds with a Link Identifier Update Response message. Upon receiving the message, UE-1 and UE-2 start using the new identifier for data traffic. UE-1 must receive traffic with the previous Layer-2 ID until it receives the Link Identifier Update Response message from UE-2.

The V2X layer of each UE delivers the PC5 link identifier for the unicast link and the updated Layer-2 ID (the destination Layer-2 ID of UE-2) to the AS layer. This allows the AS layer to update the layer 2 ID provided for the unicast link.

3) Layer 2 link break through PC5 reference point

18 illustrates a layer 2 link release procedure through a PC5 reference point to which this specification can be applied.

(0) UE-1 and UE-2 have a unicast link as described in clause 6.3.3.1.

(1) UE-1 sends a connection release request message to UE-2 to release the layer 2 link and delete all context data related to the layer 2 link.

(2) After receiving the disconnection request message, UE-2 may respond with a disconnection response message, and may delete all context data related to the layer 2 link.

The V2X layer of each UE informs the AS layer that the unicast link is released. This allows the AS layer to delete the context associated with the published unicast link.

4) Modifying Layer 2 Links for Unicast Links

19 illustrates a layer 2 link modification procedure for a unicast link to which this specification can be applied. Referring to FIG. 19 , this procedure is as follows.

- Add new V2X service to existing PC5 unicast link

- Removed all V2X services from existing PC5 unicast links

- Fix PC5 QoS flow on existing PC5 unicast link

(0) UE-1 and UE-2 have a unicast link as described in clause 6.3.3.1.

(1) The V2X application layer of UE-1 provides application information for PC5 unicast communication. The application information includes the service type (eg, PSID or ITS-AID) of the V2X application and the application layer ID of the initiating UE. The application layer ID of the target UE may be included in the application information. If UE-1 decides to reuse the existing PC5 unicast link as specified in clause 5.2.1.4, therefore, decides to modify the unicast link established by UE-2, UE-1 requests link modification is transmitted to UE-2.

Link modification request message includes:

a) To add a new V2X service to an existing PC5 unicast link:

- V2X service information: Information about the V2X service to be added (eg PSID or ITS-AID)

- QoS Information: Information on PC5 QoS Flow of each V2X service to be added. Each PC5 QoS Flow, PFI and corresponding PC5 QoS parameters (ie PQI and other parameters such as MFBR/GFBR conditionally).

b) To remove V2X service from existing PC5 unicast link:

- V2X service information: Information about the V2X service to be removed (eg PSID or ITS-AID)

c) To modify PC5 QoS Flow on existing PC5 unicast link:

- QoS Information: Information about the PC5 QoS Flow to be modified. Each PC5 QoS Flow, PFI and corresponding PC5 QoS parameters (ie PQI and other parameters such as MFBR/GFBR conditionally).

The V2X layer of each UE provides information about unicast link modification to the AS layer. This allows the AS layer to update the context associated with the modified unicast link.

ETSI TS 102 941 v1.3.1, clause 7.2 and 7.3

Multicast SAs

Multicast applications, such as public transit information and point-of-interest notification services, require secure group communication, including message authentication, authorization, and encryption, according to the group's specific security policy.

The following standard assumes that ITS-S uses IP-based multicast communication.

ITS-S can join a multicast group using an authorization ticket (see Section 6.2.3.3) following additional registration steps).

Key management of multicast applications may be controlled by a multicast service provider or a separate security manager. Such key management may be application-specific or standard multicast key management systems such as the IETF Multicast Security (MSEC) group key management architectures [i.3], [i.8], [i.9] and [i.10]. can be used

For other use cases using non-IP-based communications, ETSI TS 103 097 [3] provides a data structure that can be used to establish an SA in a multicast group.

For key establishment, the multicast group leader generates a new symmetric key k, uses it to encrypt the first multicast message (using AES-CCM), and then encrypts k for each recipient with the corresponding recipient key. Should be.

The EtsiTs103097Data-Encrypted structure can be used to encapsulate all of this data in the following way:

The field recipients MUST contain one or more RecipientInfos for each key used to encrypt symmetric key k.

Each RecipientInfo must be of the form certRecipInfo or signedDataRecipInfo:

- certRecipInfo MUST be used when symmetric key k is encrypted with the public encryption key in the certificate.

- If the symmetric key k is encrypted with the encryption key in the previously received SignedData structure, signedDataRecipInfo must be used.

The field ciphertext MUST contain the encrypted message.

After each receiver in the multicast group receives the encrypted data structure, it must decrypt the encrypted multicast message with key k. This key can be reused to encrypt additional confidential multicast messages with the pskRecipInfo option in RecipientInfo indicating the use of a pre-shared symmetric key. However, the AES-CCM nonce must be selected randomly and must not be reused with the same key.

If the multicast group already has a pre-shared key obtained through another key establishment protocol, the group can use this key with the structure EtsiTs103097Data-Encrypted and pskRecipInfo options in RecipientInfo.

The EtsiTs103097Data-SignedAndEncrypted structure can be used when authentication is also required in the key establishment phase and/or multicast group communication.

NOTE: Detailed requirements and protocols for secure group communication, including message authentication, authorization and encryption, are later specified in ETSI TS 102 943 [9].

Unicast SAs

Unicast applications such as automatic access control, parking management and media download services require secure unicast communication, including message authentication, authorization and encryption.

The following standard assumes that ITS-S uses IP-based unicast communication.

ITS-S can subscribe to that service using an authorization ticket following additional registration protocol steps.

Unicast key management is application-specific or application-specific or IETF RFC 4301 [i.4], IETF RFC 4877 [i.12], IETF RFC 4306 [i.11], IETF RFC 4302 [i.5] and IETF RFC 4303 [ A standard key management system such as network layer security using IETF RFC 4303[i] defined by i.6] may be used. In addition, transport layer security can be provided using methods such as IETF Transport Layer Security (TLS) [i.7].

For other use cases, such as trust and privacy management services specified in this document, other unicast solutions using the ETSI ITS security standard for ITS G5 communications should be considered (ETSI TS 103 097 [3]).

In the case of a non-IP unicast SA, it is possible to proceed in the same way as a multicast SA to establish a shared key. The SA initiator must generate a new symmetric key k, use it to encrypt the first confidential message, and then use that recipient key to encrypt k for the recipient. The EtsiTs103097 data encryption structure shall be used to encapsulate all data in the following way:

- The field recipient MUST contain a RecipientInfo in the form of certRecipInfo or signedDataRecipInfo depending on the recipient key used.

- The field ciphertext shall contain the encrypted message.

After receiving the encrypted data structure, the recipient must decrypt the encrypted message with key k. This key can be reused to encrypt additional confidential messages with the pskRecipInfo option in RecipientInfo indicating the use of a pre-shared symmetric key. However, the AES-CCM nonce must be selected randomly and must not be reused with the same key.

If the device involved in unicast communication already has a pre-shared key obtained through another key establishment protocol, the device may use this key with the structures EtsiTs103097Data-Encrypted and pskRecipInfo options in RecipientInfo.

EtsiTs103097Data-SignedAnd Encrypted structure can be used when authentication is required even in the key establishment phase and/or unicast communication.

NOTE: Detailed requirements and protocols for secure unicast communication including message authentication, authorization and encryption will be specified later in ETSI TS 102 943 [9].

Control Plane Radio Interface Protocol Architecture

20 is an exemplary diagram showing the structure of a radio interface protocol (Radio Interface Protocol) in the control plane between the UE and the eNodeB.

The radio interface protocol is based on the 3GPP radio access network standard. The air interface protocol is horizontally composed of a physical layer, a data link layer, and a network layer, and vertically a user plane for data information transmission and control. It is divided into a control plane for signal transmission.

The protocol layers are L1 (first layer), L2 (second layer), and L3 (third layer) based on the lower three layers of the Open System Interconnection (OSI) reference model widely known in communication systems. ) can be distinguished.

Hereinafter, each layer of the control plane shown in FIG. 20 will be described.

The first layer, the physical layer, provides an information transfer service using a physical channel. The physical layer is connected to an upper medium access control layer through a transport channel, and data between the medium access control layer and the physical layer is transmitted through the transport channel. And, data is transferred between different physical layers, that is, between the physical layers of the transmitting side and the receiving side through a physical channel.

A physical channel is composed of several subframes on the time axis and several sub-carriers on the frequency axis. Here, one sub-frame is composed of a plurality of symbols and a plurality of sub-carriers on the time axis. One subframe is composed of a plurality of resource blocks (Resource Block), and one resource block is composed of a plurality of symbols and a plurality of subcarriers. A transmission time interval (TTI), which is a unit time for data transmission, is 1 ms corresponding to one subframe.

According to 3GPP LTE, the physical channels existing in the physical layer of the transmitting side and the receiving side are a data channel, a Physical Downlink Shared Channel (PDSCH) and a PUSCH (Physical Uplink Shared Channel), and a control channel, a Physical Downlink Control Channel (PDCCH), It can be divided into a Physical Control Format Indicator Channel (PCFICH), a Physical Hybrid-ARQ Indicator Channel (PHICH), and a Physical Uplink Control Channel (PUCCH).

The PCFICH transmitted in the first OFDM symbol of the subframe carries a control format indicator (CFI) regarding the number of OFDM symbols (ie, the size of the control region) used for transmission of control channels in the subframe. The wireless device first receives the CFI on the PCFICH and then monitors the PDCCH.

Unlike the PDCCH, the PCFICH does not use blind decoding and is transmitted through a fixed PCFICH resource of a subframe.

The PHICH carries a positive-acknowledgement (ACK)/negative-acknowledgement (NACK) signal for a UL hybrid automatic repeat request (HARQ). An ACK/NACK signal for UL (uplink) data on a PUSCH transmitted by a wireless device is transmitted on a PHICH.

A PBCH (Physical Broadcast Channel) is transmitted in the preceding four OFDM symbols of the second slot of the first subframe of the radio frame. The PBCH carries system information essential for a wireless device to communicate with a base station, and the system information transmitted through the PBCH is called a master information block (MIB). In comparison, system information transmitted on the PDSCH indicated by the PDCCH is referred to as a system information block (SIB).

PDCCH is a resource allocation and transmission format of a downlink-shared channel (DL-SCH), resource allocation information of an uplink shared channel (UL-SCH), paging information on the PCH, system information on the DL-SCH, random access transmitted on the PDSCH Resource allocation of a higher layer control message such as a response, a set of transmission power control commands for individual UEs in an arbitrary UE group, and activation of voice over internet protocol (VoIP) may be carried. A plurality of PDCCHs may be transmitted in the control region, and the UE may monitor the plurality of PDCCHs. The PDCCH is transmitted on an aggregation of one or several consecutive control channel elements (CCEs). The CCE is a logical allocation unit used to provide the PDCCH with a coding rate according to the state of a radio channel. The CCE corresponds to a plurality of resource element groups. The format of the PDCCH and the possible number of bits of the PDCCH are determined according to the correlation between the number of CCEs and the coding rates provided by the CCEs.

Control information transmitted through the PDCCH is referred to as downlink control information (DCI). DCI is a PDSCH resource allocation (this is also called a DL grant (downlink grant)), PUSCH resource allocation (this is also called a UL grant (uplink grant)), a set of transmit power control commands for individual UEs in an arbitrary UE group and/or activation of Voice over Internet Protocol (VoIP).

In the second layer, there are several layers. First, the Medium Access Control (MAC) layer serves to map various logical channels to various transport channels, and is also a logical channel multiplexing that maps multiple logical channels to one transport channel. play a role The MAC layer is connected to the RLC layer, which is an upper layer, by a logical channel, and the logical channel includes a control channel that transmits information on the control plane and It is divided into a traffic channel that transmits user plane information.

The radio link control (RLC) layer of the second layer divides and concatenates data received from the upper layer to adjust the data size so that the lower layer is suitable for data transmission in the radio section. perform the role In addition, in order to ensure the various QoS required by each radio bearer (RB), TM (Transparent mode, transparent mode), UM (Un-acknowledged mode, no response mode), and AM (Acknowledged mode, Response mode) provides three operation modes. In particular, the AM RLC performs a retransmission function through an automatic repeat and request (ARQ) function for reliable data transmission.

The packet data convergence protocol (PDCP) layer of the second layer is a relatively large IP containing unnecessary control information in order to efficiently transmit IP packets such as IPv4 or IPv6 in a wireless section with a small bandwidth. It performs a header compression function that reduces the packet header size. This serves to increase the transmission efficiency of the radio section by transmitting only necessary information in the header part of the data. In addition, in the LTE system, the PDCP layer also performs a security function, which consists of encryption (Ciphering) to prevent data interception by a third party and integrity protection (Integrity protection) to prevent data manipulation by a third party.

The Radio Resource Control (RRC) layer located at the top of the third layer is defined only in the control plane, and is configured (setup), reset (Re) of radio bearers (Radio Bearer; abbreviated as RB). -Responsible for controlling logical channels, transport channels and physical channels in relation to setting) and release. In this case, the RB means a service provided by the second layer for data transfer between the UE and the E-UTRAN.

If there is an RRC connection between the RRC of the terminal and the RRC layer of the radio network, the terminal is in the RRC connected state (Connected mode), otherwise it is in the RRC idle state (Idle mode).

Hereinafter, an RRC state of the UE and an RRC connection method will be described. The RRC state refers to whether or not the RRC of the UE is logically connected to the RRC of the E-UTRAN. If it is connected, it is called an RRC_CONNECTED state, and if it is not connected, it is called an RRC_IDLE state. Since the UE in the RRC_CONNECTED state has an RRC connection, the E-UTRAN can determine the existence of the UE on a cell-by-cell basis, and thus can effectively control the UE. On the other hand, in the UE in the RRC_IDLE state, the E-UTRAN cannot detect the UE, and the core network manages the UE in a tracking area (TA) unit that is a larger area unit than the cell. That is, in the UE in the RRC_IDLE state, only the presence of the UE is determined in a larger area unit than the cell, and in order to receive a normal mobile communication service such as voice or data, the UE must transition to the RRC_CONNECTED state. Each TA is identified through a tracking area identity (TAI). The UE may configure the TAI through a tracking area code (TAC), which is information broadcast in a cell.

When the user turns on the terminal for the first time, the terminal first searches for an appropriate cell, establishes an RRC connection in the cell, and registers the terminal information in the core network. After this, the UE stays in the RRC_IDLE state. The terminal staying in the RRC_IDLE state selects (re-)selects a cell as needed, and examines system information or paging information. This is called camping on the cell. When the UE that stayed in the RRC_IDLE state needs to establish an RRC connection, it establishes an RRC connection with the RRC of the E-UTRAN through an RRC connection procedure and transitions to the RRC_CONNECTED state. There are several cases in which the UE in the RRC_IDLE state needs to establish an RRC connection. For example, when uplink data transmission is required for reasons such as a user's call attempt, or when a paging signal is received from the E-UTRAN. and sending a response message to it.

The NAS (Non-Access Stratum) layer performs functions such as session management and mobility management.

Hereinafter, the NAS layer shown in FIG. 20 will be described in detail.

The NAS layer is divided into a NAS entity for MM (Mobility Management) and a NAS entity for SM (Session Management).

1) NAS entity for MM provides the following general functions.

NAS procedures related to AMF, including the following.

- Registration management and access management procedures. AMF supports the following functions.

- Secure NAS signal connection between UE and AMF (integrity protection, encryption)

2) The NAS entity for SM performs session management between the UE and the SMF.

The SM signaling message is processed, ie, generated and processed in the NAS-SM layer of the UE and SMF. The content of the SM signaling message is not interpreted by the AMF.

- In case of SM signaling transmission,

- The NAS entity for MM creates a NAS-MM message that derives how and where to forward the SM signaling message with a security header indicating the NAS transmission of the SM signaling, additional information about the receiving NAS-MM.

- Upon receiving the SM signaling, the NAS entity for the SM performs an integrity check of the NAS-MM message, and interprets the additional information to derive a method and a place to derive the SM signaling message.

Meanwhile, in FIG. 20 , the RRC layer, the RLC layer, the MAC layer, and the PHY layer located below the NAS layer are collectively referred to as an Access Stratum (AS).

21 is an example of the configuration of the 3GPP V2X Layer and Application Layer (or ITS Layer) to which this specification can be applied.

Referring to FIG. 21, an example of a 3GPP layer and an ITS layer is shown, where the ITS layer is a specific ITS technology or standard, as well as any application that can be used on 3GPP V2X communication that does not conform to it. XX6 and the left side indicate the Control Plane and the right side indicate the User Plane, and TCP/UDP and IP in the User Plane may or may not be included depending on the configuration.

In the above description, for convenience of explanation, the EPS system is used using the eNB, but the eNB is the gNB, the MM (mobility management) function of the MME is AMF, and the SM function of the S/P-GW is SMF, S/P- The user plane-related functions of the GW can be replaced by the 5G system using UPF, etc.

In the above, the present specification has been described with reference to EPS, but the corresponding contents may be supported through similar operations through processes/messages/information for a similar purpose in the 5G system.

<5G usage scenario>

The three main requirement areas for 5G are (1) enhanced mobile broadband (eMBB) area, (2) massive machine type communication (mMTC) area, and (3) high reliability/ultra-low latency communication (URLLC; ultra-reliable and low latency communications). Some use cases may require multiple domains for optimization, while other use cases may focus on only one key performance indicator (KPI). 5G is to support these various use cases in a flexible and reliable way.

eMBB focuses on overall improvements in data rates, latency, user density, capacity and coverage of mobile broadband connections. eMBB aims for a throughput of around 10 Gbps. eMBB goes far beyond basic mobile Internet access, covering rich interactive work, media and entertainment applications in the cloud or augmented reality. Data is one of the key drivers of 5G, and for the first time in the 5G era, we may not see dedicated voice services. In 5G, voice is simply expected to be processed as an application using the data connection provided by the communication system. The main causes of the increased traffic volume are the increase in content size and the increase in the number of applications requiring high data rates. Streaming services (audio and video), interactive video and mobile Internet connections will become more widely used as more devices are connected to the Internet. Many of these applications require always-on connectivity to push real-time information and notifications to users. Cloud storage and applications are rapidly increasing in mobile communication platforms, which can be applied to both work and entertainment. Cloud storage is a special use case that drives the growth of uplink data rates. 5G is also used for remote work on the cloud, requiring much lower end-to-end latency to maintain a good user experience when tactile interfaces are used. In entertainment, for example, cloud gaming and video streaming are another key factor demanding improvements in mobile broadband capabilities. Entertainment is essential on smartphones and tablets anywhere, including in high-mobility environments such as trains, cars and airplanes. Another use example is augmented reality for entertainment and information retrieval. Here, augmented reality requires very low latency and instantaneous amount of data.

mMTC is designed to enable communication between a large number of low-cost devices powered by batteries and is intended to support applications such as smart metering, logistics, field and body sensors. mMTC is targeting a battery life of 10 years or so and/or a million devices per square kilometer. mMTC enables the seamless connection of embedded sensors in all fields to form a sensor network, and is one of the most anticipated 5G use cases. Potentially, by 2020, there will be 20.4 billion IoT devices. Smart networks leveraging industrial IoT are one of the areas where 5G will play a major role in enabling smart cities, asset tracking, smart utilities, agriculture and security infrastructure.

URLLC enables devices and machines to communicate very reliably, with very low latency and high availability, enabling autonomous vehicle-to-vehicle communication and control, industrial control, factory automation, mission-critical applications such as telesurgery and healthcare, smart grid and public Ideal for safety applications. URLLC aims for a delay on the order of 1 ms. URLLC includes new services that will transform the industry through high-reliability/ultra-low-latency links such as remote control of critical infrastructure and autonomous vehicles. This level of reliability and latency is essential for smart grid control, industrial automation, robotics, and drone control and coordination.

More specifically, 5G could complement fiber-to-the-home (FTTH) and cable-based broadband (or DOCSIS) as a means of delivering streams rated from hundreds of megabits per second to gigabits per second. Such high speed may be required to deliver TVs with resolutions of 4K or higher (6K, 8K and higher) as well as virtual reality (VR) and augmented reality (AR). VR and AR applications almost include immersive sporting events. Certain applications may require special network settings. For VR games, for example, game companies may need to integrate core servers with network operators' edge network servers to minimize latency.

Automotive is expected to be an important new driving force for 5G, with many use cases for mobile communication to vehicles. For example, entertainment for passengers requires both high capacity and high mobile broadband. The reason is that future users will continue to expect high-quality connections regardless of their location and speed. Another example of use in the automotive sector is augmented reality dashboards. The augmented reality contrast board allows drivers to identify objects in the dark above what they are seeing through the front window. The augmented reality dashboard superimposes information to inform the driver about the distance and movement of objects. In the future, wireless modules will enable communication between vehicles, information exchange between vehicles and supporting infrastructure, and information exchange between vehicles and other connected devices (eg, devices carried by pedestrians). Safety systems can help reduce the risk of accidents by guiding drivers through alternative courses of action to help them drive safer. The next step will be remote-controlled vehicles or autonomous vehicles. This requires very reliable and very fast communication between different autonomous vehicles and/or between vehicles and infrastructure. In the future, autonomous vehicles will perform all driving activities, allowing drivers to focus only on traffic anomalies that the vehicle itself cannot discern. The technological requirements of autonomous vehicles demand ultra-low latency and ultra-fast reliability to increase traffic safety to unattainable levels for humans.

Smart cities and smart homes, referred to as smart societies, will be embedded as high-density wireless sensor networks as examples of smart networks. A distributed network of intelligent sensors will identify conditions for keeping a city or house cost- and energy-efficient. A similar setup can be performed for each household. Temperature sensors, window and heating controllers, burglar alarms and appliances are all connected wirelessly. Many of these sensors typically require low data rates, low power and low cost. However, for example, real-time HD video may be required in certain types of devices for surveillance.

The consumption and distribution of energy, including heat or gas, is highly decentralized, requiring automated control of distributed sensor networks. Smart grids use digital information and communication technologies to interconnect these sensors to collect information and act on it. This information can include supplier and consumer behavior, enabling smart grids to improve efficiency, reliability, economy, sustainability of production and distribution of fuels such as electricity in an automated manner. The smart grid can also be viewed as another low-latency sensor network.

The health sector has many applications that can benefit from mobile communications. The communication system may support telemedicine providing clinical care from a remote location. This can help reduce barriers to distance and improve access to consistently unavailable health care in remote rural areas. It is also used to save lives in critical care and emergency situations. A wireless sensor network based on mobile communication may provide remote monitoring and sensors for parameters such as heart rate and blood pressure.

Wireless and mobile communications are becoming increasingly important in industrial applications. Wiring is expensive to install and maintain. Thus, the possibility of replacing cables with reconfigurable radio links is an attractive opportunity for many industries. Achieving this, however, requires that wireless connections operate with similar latency, reliability and capacity as cables, and that their management is simplified. Low latency and very low error probability are new requirements that need to be connected with 5G.

Logistics and freight tracking are important use cases for mobile communications that use location-based information systems to enable tracking of inventory and packages from anywhere. Logistics and freight tracking use cases typically require low data rates but require wide range and reliable location information.

For protection of control signaling of direct communication between two V2X UEs, each other checks whether the other UE has received permission to use the V2X service (that is, authenticates the other UE and checks whether the UE is authorized), integrity and confidentiality It is necessary to set a security key to protect (confidentiality).

For mutual authentication and security key setting between these V2X UEs, the V2X UE provides the V2X communication in advance with a certificate of the communication service provider and the V2X service provider (eg, vehicle OEM, communication service provider, national or regional authority, etc.) Or get and store the public key. This is possible through 3GPP UE provisioning procedures such as OTA or other well-known general certificate update procedures.

Next, when there is no security key for protection of 3GPP layer communication before or when starting unicast mode direct communication between V2X UEs, the V2X UE performs the procedure for setting the security key as shown in FIG. 22 with the V2X servicer provider (or ITS service provider) application server and 3GPP service provider subscribed to.

22 is an example of a certificate and security key issuance procedure for unicast mode communication to which this specification can be applied.

A procedure in which a V2X UE (UE) is issued a certificate and a security key for protection of 3GPP layer unicast mode communication through the procedure of FIG. 22 is as follows.

1. The V2X UE may request a security key for V2X unicast mode direct communication from the Application server (V2X service provider or ITS service provider). This may include subscriber-related information that can be verified by the 3GPP service network (eg, IP multimedia private identity granted by the 3GPP carrier) and V2X service subscriber information that can be verified by the application server (ie, user ID). .

23 is an example of an approval procedure to which this specification can be applied.

Referring to FIG. 23 , the V2X UE may additionally perform an authorization procedure through the user, based on the service the user wants to use and the setting of the V2X UE.

The V2X UE may display a guide message including an input button for initiating a request for a security key for V2X unicast mode direct communication to the application server (2310). When the certificate issuance procedure to be described later is completed, the V2X UE may display a guide message indicating that the certificate issuance procedure is completed (2330).

2. The application server generates a public and private key pair for the V2X UE, and the public key can be signed with the public key of the application server.

(Optional) Since the private key is used for key exchange in direct communication between V2X UEs, if it is necessary to hide it from the 3GPP operator for privacy, the public key of the certificate issued separately by the application server to the V2X UE in advance for each V2X UE. It can be encrypted with the corresponding private key.

3. The application server includes an ID that the 3GPP network can verify (eg IMPI), a certificate containing the public key of the V2X UE, a private key (which may be encrypted as an option), and the period for which the key will be used (start, end) ) can be delivered to the 3GPP network (V2X UE's home network). An appropriate service license agreement must exist between the application service provider and the 3GPP carrier, and the communication between the two must be protected.

4. In the 3GPP network, the subscriber information is checked through the ID assigned to the subscriber, and in the case of a V2X UE capable of V2X unicast mode communication, the received certificate of the V2X UE is cross-signed with the certificate of the 3GPP operator. Alternatively, a separate certificate can be created by separately signing the public key. This certificate may include a period granted by the application service provider. For example, the application service provider may set a valid period for the certificate in the certificate. When there are a plurality of services that the application service provider can provide, the application service provider may set a different valid period for the certificate for each service.

In addition, the application service provider may randomly generate a Provision ID corresponding to this certificate. When subscriber confirmation, service permission confirmation, and certificate issuance are completed successfully, the 3GPP network may deliver the Key Provision ID to the service provider.

5. The service provider may deliver the Key Provision ID to the V2X UE.

6. V2X UE may make a certificate request with Key Provision ID and subscriber ID (eg IMPI) to the 3GPP home network. For example, the certificate request message may include the aforementioned Key Provision ID and a subscriber ID.

7. 3GPP home network sees Key Provision ID and confirms that Key Provision ID is issued to V2X V2X UE The key (which may be optionally in encrypted form in step 2) may be delivered to the V2X UE. The V2X UE can store the delivered certificate and Key.

24 is an embodiment of a display to which this specification can be applied. 24, the V2X UE may display a list of stored certificates and available services. For example, the V2X UE may display a message including the information of the application service provider, information of the service that the application service provider can provide, and/or the period during which the certificate is valid.

In addition, when the number of services that the application service provider can provide is plural, the V2X UE may display a message including information on each service and/or a period during which the certificate is valid for each service. For example, such a message may have the form of a list, and the period during which the corresponding certificate is valid for each service may be displayed.

25 is an example of a mutual authentication procedure to which this specification can be applied.

Direct communication between two V2X UEs that have been issued a certificate is possible through the procedure as shown in FIG. 25 without the help of an upper application or server. The two V2X UEs can exchange the issued certificates (steps 1 and 3) to check whether the 3GPP V2X service is a permitted V2X UE, and perform mutual authentication (steps 2, 4). According to the service policy, the V2X UE can verify the signature of the V2X service provider when mutual communication is possible only with the same V2X service provider. Alternatively, in the case of the same ITS service provider even when the 3GPP communication service provider is different, in the case of V2X UEs capable of direct communication, the V2X UE may check the signature of the ITS service provider.

26 is an embodiment of a display to which this specification can be applied. Referring to FIG. 26 , the V2X UE may display the setting information of the service policy to the user through the display unit. For example, after the V2X UE exchanges the certificate, based on the received certificate, it may display the setting information of the service policy. Through this, the user can check the setting information of the service policy related to the certificate. For example, the setting of the service policy is based on the received certificate, when the certificate is related to the same service provider, is related to the same communication operator, or the certificate can be set differently depending on the case of the unverified V2X UE.

In addition, the setting information of the service policy may be additionally set by the user. For example, the setting information of the service policy may be provided in the form of text, and among them, the text related to the setting of the service policy in which the user can change the setting may be provided in the form of underlined text. The user may change the setting of the service policy through a touch operation on the field where the underlined text is located.

After mutual authentication, security setting is completed by creating a security key to be used for communication encryption, encrypting it with the other party's public key and sending it (step 5). It is also possible to use other key exchange methods according to the service policy.

27 is an embodiment of a terminal to which this specification can be applied.

Referring to FIG. 27 , the terminal displays a guide message including an input button for requesting generation of a security key for protecting V2X communication to the server through the display unit (S2710).

When the generation of the security key is requested through the input button, the terminal transmits a key request message for requesting generation of a security key for protecting the V2X communication to the server (S2720). For example, the security key includes a public key and a private key used for V2X communication of the terminal. In addition, the key request message may include subscriber information related to the user of the terminal available in the network and the server.

The terminal receives an identifier generated in the network for authenticating the terminal from the server (S2730).

The terminal transmits a certificate request message including the identifier in order to request a certificate (certificate) associated with the identifier for the V2X communication to the network (S2740).

The terminal receives the certificate and the private key as a response to the certificate request message from the network based on the verification of the identifier through the network, and displays a guide message indicating that the issuance of the certificate is completed do (S2750). For example, the certificate may be for determining whether the terminal is allowed in relation to the V2X communication through mutual authentication with another terminal. In addition, the certificate may include information on a period during which the certificate is valid, set by a service provider related to the server.

28 is an embodiment of a core network to which this specification can be applied.

Referring to FIG. 28 , a private key generated by the server and information about the terminal are received from the server through a request from a terminal (UE) (S2810). For example, the information of the terminal may include subscriber information related to the user of the terminal, which can be used in the network and the server. In addition, the terminal information may further include the private key generated by the server in relation to the terminal. In addition, the private key may be encrypted using a private key related to the terminal's certificate preset by the server.

When the terminal is a terminal permitted in relation to the V2X communication based on the information of the terminal, a certificate for the V2X communication and an identifier related to the certificate are generated (S2820). For example, the certificate may include information on a period during which the certificate is valid, set by a service provider related to the server.

The identifier is transmitted to the server (S2830).

According to this specification, after subscriber confirmation through mutual authentication between the 3GPP network and the UE based on the 3GPP credential, the existing 3GPP Generic Bootstrapping Architecture (GBA) and Conversely, based on the V2X UE confirmation of the application server (here, the ITS server or the server of the V2X service provider), the security key to be used in the 3GPP network is transmitted through the 3GPP network. In particular, in the case of issuing a pseudonymous ITS certificate that cannot be directly linked to the V2X UE ID in accordance with local laws or for the purpose of protecting the privacy of the V2X UE through a certification authority, the 3GPP network may not directly know it, or It has the advantage of making it unknown even in the 3GPP network.

General devices to which this specification can be applied

Hereinafter, an apparatus to which the present specification can be applied will be described.

29 shows a wireless communication device according to an embodiment of the present specification.

Referring to FIG. 29 , a wireless communication system may include a first device 9010 and a second device 9020 .

The first device 9010 includes a base station, a network node, a transmitting terminal, a receiving terminal, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, a connected car, a drone (Unmanned Aerial Vehicle, UAV), Artificial Intelligence (AI) Module, Robot, AR (Augmented Reality) Device, VR (Virtual Reality) Device, MR (Mixed Reality) Device, Hologram Device, Public Safety Device, MTC Device, IoT Device, Medical Device, Pin It may be a tech device (or financial device), a security device, a climate/environment device, a device related to 5G services, or other devices related to the 4th industrial revolution field.

The second device 9020 includes a base station, a network node, a transmitting terminal, a receiving terminal, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, a connected car, a drone (Unmanned Aerial Vehicle, UAV), Artificial Intelligence (AI) Module, Robot, AR (Augmented Reality) Device, VR (Virtual Reality) Device, MR (Mixed Reality) Device, Hologram Device, Public Safety Device, MTC Device, IoT Device, Medical Device, Pin It may be a tech device (or financial device), a security device, a climate/environment device, a device related to 5G services, or other devices related to the 4th industrial revolution field.

For example, the terminal includes a mobile phone, a smart phone, a laptop computer, a digital broadcasting terminal, personal digital assistants (PDA), a portable multimedia player (PMP), a navigation system, a slate PC, and a tablet. PC (tablet PC), ultrabook (ultrabook), wearable device (wearable device, for example, a watch-type terminal (smartwatch), glass-type terminal (smart glass), HMD (head mounted display), etc. may be included. . For example, the HMD may be a display device worn on the head. For example, an HMD may be used to implement VR, AR or MR.

For example, the drone may be a flying vehicle that does not ride by a person and flies by a wireless control signal. For example, the VR device may include a device that implements an object or a background of a virtual world. For example, the AR device may include a device that implements by connecting an object or background in the virtual world to an object or background in the real world. For example, the MR device may include a device that implements a virtual world object or background by fusion with a real world object or background. For example, the hologram device may include a device for realizing a 360-degree stereoscopic image by recording and reproducing stereoscopic information by utilizing an interference phenomenon of light generated by the meeting of two laser beams called holography. For example, the public safety device may include an image relay device or an image device that can be worn on a user's body. For example, the MTC device and the IoT device may be devices that do not require direct human intervention or manipulation. For example, the MTC device and the IoT device may include a smart meter, a bending machine, a thermometer, a smart light bulb, a door lock, or various sensors. For example, a medical device may be a device used for the purpose of diagnosing, treating, alleviating, treating, or preventing a disease. For example, a medical device may be a device used for the purpose of diagnosing, treating, alleviating or correcting an injury or disorder. For example, a medical device may be a device used for the purpose of examining, replacing, or modifying structure or function. For example, the medical device may be a device used for the purpose of controlling pregnancy. For example, the medical device may include a medical device, a surgical device, an (ex vivo) diagnostic device, a hearing aid, or a device for a procedure. For example, the security device may be a device installed to prevent a risk that may occur and maintain safety. For example, the security device may be a camera, CCTV, recorder or black box. For example, the fintech device may be a device capable of providing financial services such as mobile payment. For example, the fintech device may include a payment device or a Point of Sales (POS). For example, the climate/environment device may include a device for monitoring or predicting the climate/environment.

The first device 9010 may include at least one processor such as a processor 9011 , at least one memory such as a memory 9012 , and at least one transceiver such as a transceiver 9013 . The processor 9011 may perform the functions, procedures, and/or methods described above. The processor 9011 may perform one or more protocols. For example, the processor 9011 may perform one or more layers of an air interface protocol. The memory 9012 is connected to the processor 9011 and may store various types of information and/or instructions. The transceiver 9013 may be connected to the processor 9011 and may be controlled to transmit/receive a wireless signal.

The second device 9020 may include at least one processor such as a processor 9021 , at least one memory device such as a memory 9022 , and at least one transceiver such as a transceiver 9023 . The processor 9021 may perform the functions, procedures, and/or methods described above. The processor 9021 may implement one or more protocols. For example, the processor 9021 may implement one or more layers of an air interface protocol. The memory 9022 is connected to the processor 9021 and may store various types of information and/or commands. The transceiver 9023 may be connected to the processor 9021 and may be controlled to transmit/receive a wireless signal.

The memory 9012 and/or the memory 9022 may be respectively connected inside or outside the processor 9011 and/or the processor 9021, and may be connected to another processor through various technologies such as wired or wireless connection. may be connected to

The first device 9010 and/or the second device 9020 may have one or more antennas. For example, antenna 9014 and/or antenna 9024 may be configured to transmit and receive wireless signals.

30 illustrates a block diagram of a network node according to an embodiment of the present specification.

In particular, FIG. 30 is a diagram illustrating the network node of FIG. 29 in more detail when the base station is divided into a central unit (CU) and a distributed unit (DU).

Referring to FIG. 30 , base stations W20 and W30 may be connected to the core network W10 , and the base station W30 may be connected to a neighboring base station W20 . For example, the interface between the base stations W20 and W30 and the core network W10 may be referred to as NG, and the interface between the base station W30 and the neighboring base station W20 may be referred to as Xn.

The base station W30 may be divided into CUs W32 and DUs W34 and W36. That is, the base station W30 may be hierarchically separated and operated. The CU W32 may be connected to one or more DUs W34 and W36, for example, an interface between the CU W32 and the DUs W34 and W36 may be referred to as F1. The CU (W32) may perform functions of upper layers of the base station, and the DUs (W34, W36) may perform functions of lower layers of the base station. For example, the CU W32 is a radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) layer of a base station (eg, gNB) hosting a logical node (logical node) , and the DUs W34 and W36 may be logical nodes hosting radio link control (RLC), media access control (MAC), and physical (PHY) layers of the base station. Alternatively, the CU W32 may be a logical node hosting the RRC and PDCP layers of the base station (eg, en-gNB).

The operation of the DUs W34 and W36 may be partially controlled by the CU W32. One DU (W34, W36) may support one or more cells. One cell can be supported by only one DU (W34, W36). One DU (W34, W36) may be connected to one CU (W32), and one DU (W34, W36) may be connected to a plurality of CUs by appropriate implementation.

31 illustrates a block diagram of a communication device according to an embodiment of the present specification.

In particular, FIG. 31 is a diagram illustrating the terminal of FIG. 30 in more detail above.

Referring to FIG. 31 , the terminal includes a processor (or a digital signal processor (DSP) (Y10), an RF module (or an RF unit) (Y35), and a power management module (Y05). ), antenna (Y40), battery (Y55), display (Y15), keypad (Y20), memory (Y30), SIM card (SIM (Subscriber Identification Module) ) card) (Y25) (this configuration is optional), a speaker (Y45) and a microphone (Y50) may be included. The terminal may also include a single antenna or multiple antennas. can

The processor Y10 implements the functions, processes and/or methods proposed above. The layer of the air interface protocol may be implemented by the processor Y10.

The memory Y30 is connected to the processor Y10 and stores information related to the operation of the processor Y10. The memory Y30 may be inside or outside the processor Y10, and may be connected to the processor Y10 by various well-known means.

The user inputs command information such as a phone number by, for example, pressing (or touching) a button of the keypad Y20 or by voice activation using the microphone Y50. The processor Y10 receives such command information and processes it to perform an appropriate function, such as making a call to a phone number. Operational data may be extracted from the SIM card Y25 or the memory Y30. In addition, the processor Y10 may display command information or driving information on the display Y15 for the user to recognize and for convenience.

The RF module Y35 is connected to the processor Y10 to transmit and/or receive RF signals. The processor Y10 transmits command information to the RF module Y35 to transmit, for example, a radio signal constituting voice communication data to initiate communication. The RF module Y35 includes a receiver and a transmitter to receive and transmit a radio signal. The antenna Y40 functions to transmit and receive radio signals. When receiving a wireless signal, the RF module Y35 may forward the signal and convert the signal to baseband for processing by the processor Y10. The processed signal may be converted into audible or readable information output through the speaker Y45.

The embodiments described above are those in which the elements and features of the present specification are combined in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented in a form that is not combined with other components or features. It is also possible to configure embodiments of the present specification by combining some components and/or features. The order of operations described in the embodiments of the present specification may be changed. Some features or features of one embodiment may be included in another embodiment, or may be replaced with corresponding features or features of another embodiment. It is obvious that claims that are not explicitly cited in the claims can be combined to form an embodiment or included as a new claim by amendment after filing.

Embodiments according to the present specification may be implemented by various means, for example, hardware, firmware, software, or a combination thereof. In the case of implementation by hardware, an embodiment of the present specification provides one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), FPGAs ( field programmable gate arrays), a processor, a controller, a microcontroller, a microprocessor, and the like.

In the case of implementation by firmware or software, an embodiment of the present specification may be implemented in the form of a module, procedure, function, etc. that performs the functions or operations described above. The software code may be stored in the memory and driven by the processor. The memory may be located inside or outside the processor, and may transmit/receive data to and from the processor by various known means.

The above-described specification is permitted to be implemented as computer-readable code on a medium in which a program is recorded. The computer-readable medium includes all types of recording devices in which data readable by a computer system is stored. Examples of computer-readable media include Hard Disk Drive (HDD), Solid State Disk (SSD), Silicon Disk Drive (SDD), ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage device, etc. There is also a carrier wave (eg, transmission over the Internet) that is implemented in the form of. Also, the computer may include a processor Y120 of the terminal. Accordingly, the above detailed description should not be construed as restrictive in all respects but as exemplary. The scope of this specification should be determined by a reasonable interpretation of the appended claims, and all modifications within the scope of equivalents of this specification are included in the scope of this specification.

The communication method as described above is allowed to be applied to various wireless communication systems including IEEE 802.16x and 802.11x systems in addition to the 3GPP system. Furthermore, the proposed method can be applied to a mmWave communication system using a very high frequency band.

Claims (20)

1. In a method for a UE (User Equipment) to protect V2X (Vehicle-to-Everything) communication using a server in a wireless communication system,

   Displaying a guide message including an input button for requesting generation of a security key (Security key) for protecting the V2X communication to the server through the display unit;

   transmitting a key request message for requesting generation of the security key to the server when the generation of the security key is requested through the input button;

   receiving an identifier generated in a core network for authenticating the terminal from the server;

   transmitting a certificate request message including the identifier to request a certificate (certificate) associated with the identifier for the V2X communication to the core network; and

   Based on the verification of the identifier through the core network, the certificate and the private key are received from the core network as a response to the certificate request message, and the display unit indicates that the issuance of the certificate has been completed. displaying a guide message;

   A method for protecting V2X communication, including.
2. According to claim 1,

   The certificate is

   Through mutual authentication with other terminals, a method for protecting V2X communication for determining whether the terminal is allowed in relation to the V2X communication.
3. 3. The method of claim 1 or 2,

   The key request message is

   A method for protecting V2X communication, including subscriber information related to the user of the terminal, available in the core network and the server.
4. 4. The method according to any one of claims 1 to 3,

   The certificate is

   The method for protecting V2X communication, including information on the validity period of the certificate set by the provider of the service related to the server.
5. 5. The method of claim 4,

   displaying, through the display unit, a notification message including information on a provider of a service related to the server, information on a service that the provider of a service related to the server can provide, and information on a period during which the certificate is valid;

   Further comprising, a method for protecting V2X communication.
6. 6. The method of claim 5,

   The notification message is

   Based on the plurality of services that the provider of the service related to the server can provide, the method for protecting V2X communication, further comprising information on the validity period of the certificate set for each of the plurality of services.
7. 7. The method according to any one of claims 1 to 6,

   transmitting the certificate to another terminal;

   receiving, from the other terminal, a certificate of the other terminal; and

   transmitting, to the other terminal, a security key for direct communication with the other terminal based on verification of the certificate of the other terminal;

   Further comprising, a method for protecting V2X communication.
8. 8. The method of claim 7,

   the terminal is

   A method for protecting V2X communication by establishing a unicast link with the other terminal through a security key for direct communication with the other terminal.
9. 9. The method of claim 8,

   The unicast link is

   Based on the configuration information preset in the terminal, a method for protecting the established V2X communication.
10. 10. The method of claim 9,

    displaying a setting screen including the setting information;

    further comprising,

    The setting screen includes an input field for receiving a setting value from the user, and the input field has an underlined text form, a method for protecting V2X communication.
11. In a terminal (UE: User Equipment) for protecting V2X (Vehicle-to-Everything) communication using a server in a wireless communication system,

    transceiver;

    display unit;

    Memory; and

    a processor for controlling the transceiver, the display unit, and the memory;

    the processor

    Displaying a guide message including an input button for requesting generation of a security key (Security key) for protecting the V2X communication to the server through the display unit,

    When the generation of the security key is requested through the input button, a key request message for requesting generation of the security key is transmitted to the server through the transceiver;

    Receives an identifier generated in the core network for authenticating the terminal from the server,

    Transmitting a certificate request message including the identifier to request a certificate (certificate) associated with the identifier for the V2X communication to the core network,

    Based on the verification of the identifier through the core network, the certificate and the private key are received from the core network as a response to the certificate request message, and the issuance of the certificate is completed through the display unit. A terminal that displays a guide message indicating.
12. 12. The method of claim 11,

    The certificate is

    Through mutual authentication with other terminals, the terminal is for determining whether the terminal is allowed in relation to the V2X communication.
13. 13. The method of claim 11 or 12,

    The key request message is

    A terminal comprising subscriber information related to a user of the terminal, available in the core network and the server.
14. 14. The method according to any one of claims 11 to 13,

    The certificate is

    The terminal, including information on the validity period of the certificate set by the service provider related to the server.
15. 15. The method of claim 14,

    the processor

    A terminal for displaying, through the display unit, a notification message including information on a provider of a service related to the server, information on a service that can be provided by a provider of a service related to the server, and information on a period during which the certificate is valid.
16. 16. The method of claim 15,

    The notification message is

    The terminal further includes information on a period during which the certificate set for each of the plurality of services is valid based on the plurality of services that the service provider related to the server can provide.
17. 17. The method according to any one of claims 11 to 16,

    the processor

    Transmitting the certificate to another terminal through the transceiver,

    Receive a certificate of the other terminal from the other terminal,

    A terminal for transmitting, to the other terminal, a security key for direct communication with the other terminal based on verification of the certificate of the other terminal.
18. 18. The method of claim 17,

    the terminal is

    A terminal for establishing a unicast link with the other terminal through a security key for direct communication with the other terminal.
19. 19. The method of claim 18,

    The unicast link is

    The terminal is established based on the setting information preset in the memory.
20. 20. The method of claim 19,

    the processor

    Displaying a setting screen including the setting information through the display unit,

    The setting screen includes an input field for receiving a setting value from a user, and the input field has an underlined text form, the terminal.

Images