Apparatus, systems, methods, and computer-readable media for connectivity-oriented vehicle-to-all (VTX) communications in 5G

Abstract

To provide a device and a method for performing vehicle-to-all communication.SOLUTION: A first wireless transmit / receive unit (WTRU) transmits a first SL radio resource control (RRC) message requesting sidelink (SL) information of a second WTRU to the second WTRU, and receives from the second WTRU a second SL RRC message including capability information associated with the second WTRU. The capability information includes access stratum (AS) layer parameters for sidelink communication. The first WTRU also transmits to a network node a first RRC message requesting SL transmission resources, based on receiving the second SL RRC message from the second WTRU. The first RRC message includes an indication of the capability information in the second SL RRC message received from the second WTRU. The first WTRU further receives from the network node a second RRC message including SL resource allocation information.SELECTED DRAWING: Figure 27

Description

Technical Field

[0001] (Cross - reference to related applications) This application claims the benefit of U.S. Provisional Application No. 62 / 805,121, filed on February 13, 2019, and U.S. Provisional Application No. 62 / 841,579, filed on May 1, 2019, and the entire contents thereof are hereby incorporated by reference into this specification.

[0002] The present disclosure generally relates to wireless communication, and more particularly, to wireless communication systems, devices, methods, and computer - readable media for performing vehicle - to - everything communication.

Background Art

[0003] The description of "Background Art" provided herein is for the purpose of generally presenting the context of the present disclosure. The current inventors' research within the scope described in this Background Art section, as well as aspects of the description that may not be recognized as prior art at the time of filing, are not expressly or implicitly recognized as prior art to the present invention.

[0004] Existing vehicle - to - X systems and methods are connectionless and do not support the high data rate, high reliability, and low latency requirements that are required in 5G systems. Furthermore, in existing systems, connectionless transmission results in several drawbacks such as high protocol overhead, high processing overhead, etc., and it is difficult to enable physical layer feedback. ? ?

Summary of the Invention

[0005] Exemplary embodiments of the present disclosure include a first device including a processor, a memory, and a communication circuit. The device provides a location. The first device is connected to a communication network via a communication circuit. Device 1 further includes computer executable instructions stored in memory, and the computer When an executable instruction is executed by the processor, it communicates to the first device, enabling the first device to communicate. To discover a capable second device, to obtain information about devices related to the second device, and the second device The wireless protocol of the first device is configured for direct sidelink communication with the other device.

[0006] Exemplary embodiments of this disclosure include a first device comprising a processor, memory, and communication circuitry. The device provides a method for direct sidelink communication using a device, the first device communicating via a communication circuit It is connected to a communication network. This method involves the first device communicating with a second device that can communicate with it. To discover, to obtain information about devices related to the second device, and with the second device This includes configuring the radio protocol of the first device for direct sidelink communication.

[0007] Exemplary embodiments of the present disclosure are non-temporary having tangibly recorded computer-readable instructions. It provides a computer-readable storage medium, and computer-readable instructions are executed by processing circuits. Then, the processing circuit is instructed to use the first device to directly perform the sidering communication method. This method involves the first device discovering a second device with which it can communicate, and the second device being related to To obtain device information and to enable direct sidelink communication with the second device, the first This includes configuring the wireless protocol of the device.

[0008] The outline of this invention is further described in the following simplified forms for carrying out the invention. The format is provided to introduce the selection of concepts. The outline of this invention is described in the claims. This is not intended to identify the main or essential features of the subject, and please It is not intended to be used to limit the scope of the subject matter stated in the request. Furthermore, the subject matter described in the claims is any or It is not restricted by limitations that resolve all disadvantages. [Brief explanation of the drawing]

[0009] The scope of this disclosure is to be read in conjunction with the accompanying drawings for the following detailed description of exemplary embodiments. It is best understood from the perspective of the Ming Dynasty. [Figure 1A] Figure 1A is a system diagram showing an exemplary 3GPP architecture. [Figure 1B] Figure 1B is a system diagram of an exemplary device or apparatus configured for wireless communication. [Figure 1C] Figure 1C is a system diagram showing an example of a Radio Access Network (RAN) architecture and a core network architecture. [Figure 1D] Figure 1D is a system diagram showing an example of a wireless access network (RAN) architecture and a core network architecture. [Figure 1E] Figure 1E is a system diagram showing an example of a wireless access network (RAN) architecture and a core network architecture. [Figure 1F] Figure 1F is a system diagram showing an example of a computing system used in a communication network. [Figure 1G] Figure 1G is a system diagram showing an exemplary 3GPP architecture. [Figure 2] Figure 2 shows a protocol stack of the control plane for one-to-one sidelink communication according to an exemplary embodiment. [Figure 3]Figure 3 shows the establishment of a secure Layer 2 link via the PC5 according to an exemplary embodiment. [Figure 4] Figure 4 shows a user plane protocol stack for sidelink communication according to an exemplary embodiment. [Figure 5] Figure 5 shows an overview of 5G V2X requirements versus LTE V2V R14 requirements according to an exemplary embodiment. [Figure 6] Figure 6 shows an SDAP sublayer structure for V2X sidelink communication according to an exemplary embodiment. [Figure 7] Figure 7 shows an L2 structure for V2X sidelink communication according to an exemplary embodiment. [Figure 8] Figure 8 is a diagram showing an L2 structure for V2X sidelink communication according to an exemplary embodiment. [Figure 9] Figure 9 shows an L2 structure for V2X sidelink communication according to an exemplary embodiment. [Figure 10] Figure 10 shows an SDAP layer functional diagram for V2X sidelink communication according to an exemplary embodiment. [Figure 11] Figure 11 shows a UL or DL sidelink SDAP data PDU format with an SDAP header according to an exemplary embodiment. [Figure 12] Figure 12 shows a method for transmitting side V2X communication according to an exemplary embodiment. [Figure 13] Figure 13 shows a method for receiving side V2X communication according to an exemplary embodiment. [Figure 14] Figure 14 shows a transmission side unicast method for layer 2 link management according to an exemplary embodiment. [Figure 15] Figure 15 shows a reception side unicast method for layer 2 link management according to an exemplary embodiment. [Figure 16A] Figure 16A shows a unicast connection establishment method in which the initiating UE RRC sets or assists in setting the target UE according to an exemplary embodiment. [Figure 16B] Figure 16B illustrates a method for establishing a unicast connection in which the initiating UE RRC configures or assists in configuring the target UE, according to an exemplary embodiment. [Figure 16C] Figure 16C illustrates a method for establishing a unicast connection in which the initiating UE RRC configures or assists in configuring the target UE, according to an exemplary embodiment. [Figure 17A] Figure 17A illustrates a method for establishing a unicast connection in which the initiating UE PC5 configures or assists in configuring the target UE, according to an exemplary embodiment. [Figure 17B] Figure 17B illustrates a method for establishing a unicast connection in which the initiating UE PC5 configures or assists in configuring the target UE, according to an exemplary embodiment. [Figure 17C] Figure 17C illustrates a method for establishing a unicast connection in which the initiating UE PC5 configures or assists in configuring the target UE, according to an exemplary embodiment. [Figure 18A] Figure 18A illustrates a method for establishing a unicast connection in which the initiating UE RRC configures or assists in configuring the target UE, according to an exemplary embodiment. [Figure 18B] Figure 18B illustrates a method for establishing a unicast connection in which the initiating UE RRC configures or assists in configuring the target UE, according to an exemplary embodiment. [Figure 18C] Figure 18C illustrates a method for establishing a unicast connection in which the initiating UE RRC configures or assists in configuring the target UE, according to an exemplary embodiment. [Figure 19A] Figure 19A illustrates a method for establishing a unicast connection in which the target UE PC5 configures the initiating UE or assists in configuring the target UE, according to an exemplary embodiment. [Figure 19B] Figure 19B illustrates a method for establishing a unicast connection in which the target UE PC5 configures the initiating UE or assists in configuring the target UE, according to an exemplary embodiment. [Figure 19C] Figure 19C illustrates a method for establishing a unicast connection in which the target UE PC5 configures the initiating UE or assists in configuring the target UE, according to an exemplary embodiment. [Figure 20A] Figure 20A illustrates a method for establishing a unicast connection in which the target UE PC5 configures the initiating UE or assists in configuring the target UE, according to an exemplary embodiment. [Figure 20B] Figure 20B illustrates a method for establishing a unicast connection in an exemplary embodiment, in which the target UE PC5 configures the initiating UE or assists in configuring the target UE. [Figure 20C] Figure 20C illustrates a method for establishing a unicast connection in which the target UE PC5 configures the initiating UE or assists in configuring the target UE, according to an exemplary embodiment. [Figure 21A] Figure 21A illustrates a method for establishing a unicast connection in an exemplary embodiment, where the target UE RRC sets up the initiating UE. [Figure 21B] Figure 21B illustrates a method for establishing a unicast connection in an exemplary embodiment, where the target UE RRC sets up the initiating UE. [Figure 21C] Figure 21C illustrates a method for establishing a unicast connection in an exemplary embodiment, where the target UE RRC sets up the initiating UE. [Figure 22] Figure 22 shows a transmitter-side group cast method for Layer 2 link management according to an exemplary embodiment. [Figure 23] Figure 23 shows a receiver-side group cast method for Layer 2 link management according to an exemplary embodiment. [Figure 24] Figure 24 shows the broadcast transmission settings on the transmitting side according to an exemplary embodiment. [Figure 25] Figure 25 shows the receiving-side broadcast transmission settings according to an exemplary embodiment. [Figure 26] Figure 26 shows the PC5 RRC connection status between the two UEs. [Figure 27]Figure 27 shows a UE with multiple RRC connections to a gNB and multiple UEs. [Figure 28] Figure 28 shows the first exemplary PC5 unicast link model. [Figure 29] Figure 29 shows a second exemplary PC5 unicast link model. [Figure 30] Figure 30 shows a third exemplary PC5 unicast link model. Further application areas of this disclosure will become apparent from the detailed description provided below. It should be understood that the detailed description of exemplary embodiments is for illustrative purposes only and is therefore not necessarily intended to limit the scope of this disclosure. [Modes for carrying out the invention]

[0010] 3rd Generation Partnership Project: 3GPP) is a framework for wireless access, core transport networks, and codecs. Cellular We develop technical standards for communication network technologies. (Recent Radio Access Technology) :RAT) standards include WCDMA (registered trademark) (commonly called 3G), LTE (commonly (These are referred to as 4G), the LTE-Advanced standard, and the newer "5G" There is a new wireless technology (New Radio: NR). Development of 3GPP NR standards will continue. This is expected to include a definition of next-generation wireless access technology (new RAT). Providing new flexible wireless access below 7GHz, and new above 7GHz It is expected that this will include the provision of ultra-mobile broadband wireless access. Flexible wireless access is a new, backward-incompatible wireless in the new frequency band below 7GHz. It consists of line access and includes different operating modes that can be multiplexed in the same frequency band. This is expected to address a wide range of 3GPP NR use cases with varying requirements. Ultra-mobile broadband is used for indoor applications and hotspots, for example. Centimeter and millimeter wave frequencies provide opportunities for ultra-mobile broadband access. It is expected that frequency bands will be included. Especially in ultra-mobile broadband, Design optimization specifically for millimeter and millimeter waves enables flexible wireless access below 7GHz. It is expected that they will share a common design framework.

[0011] 3GPP has identified various use cases that NR is expected to support. As a result, a wide variety of users regarding data rate, latency, and mobility have emerged. The requirements for the experience have arisen. Use cases include the following common categories, and extended models. Enhanced Mobile Broadband (eMBB) ultra-high reliability low latency communication Ultra-Reliable Low-Latency Communication (URLLC), large-scale machine type Communications (Massive Machine Type Communications: mMTC), network operation (for example) Network slicing, routing, migration and interwork Enhanced Vehicle-To-Everything (enhanced vehicle-to-everything), as well as energy efficiency. Vehicle-to-Vehicle Communication (V2X) is a type of communication between vehicles. 2V), Vehicle-to-Infrastructure Communication Vehicle-to-Network Communication (V2N) , Vehicle-to-Pedestrian Communication (V2P), and other This includes those that can include any vehicle communication with the NTIT. Specific services and applications in this area include, for example, monitoring and sensor networks. Remote control of devices, two-way remote control, personal cloud computing Video streaming, wireless cloud-based office, first responder Connectivity, car emergency call system, disaster alert, real-time gaming, multiplayer Audio calling, autonomous driving, augmented reality, touch internet, virtual reality, home automation Engines, robots, and aerial drones are just a few examples. All of the use cases and other use cases described herein are intended to be used in this specification.

[0012] Next, the following abbreviations related to service levels and core network technologies may appear in the description below. A list of terms is provided below. Unless otherwise specified, abbreviations used in this specification are listed below. It means the corresponding term.

[0013] Abbreviation 3GPP:3 rd Generation Partnership Project (3rd Generation Partnership Project) to) 5G: 5th Generation 5QI:5G QoS identifier ACK: ACKnowledgement (affirmative response) AM: Acknowledged Mode AMF: Access and Mobility Function APP: Application AS: Access Layer BWP: Bandwidth Part BSD: Bucket Size Duration BSR: Buffer Status Report CBR: Channel Busy Ratio Config:Configuration (Settings) CSR: Channel State Report CR: Channel occupancy ratio D2D: Device to Device Communication DCI: Downlink Control Information eNB: Evolved Node B eV2X: Enhanced Vehicle-to-X Communication E-UTRA: Evolved UMTS Terrestrial Radio Access vinegar) E-UTRAN: Evolved UMTS Terrestrial Radio Access Network Wireless access network) eNB:evolved NodeB (Advanced Node B) gNB:NR NodeB (NR Node B) GBR: Guarantee Bit Rate GSM: Global System for Mobile Communication HARQ:Hybrid Automatic Repeat Request IAB: Integrated Access Backhaul ID: Identity or Identifier (identification information or identifier) Info: Information IP: Internet Protocol ITS: Intelligent Transport System ITS-AID: ITS Application Identifier I-UE: Initiating UE (Starting UE) L2: Layer-2 LBT: Listen Before Talk LCH: Logical Channel LCID: Logical Channel Identity LCG: Logical Channel Group LTE: Long Term Evolution MAC: Medium Access Control MCH: Multicast Transport Channel ME: Mobile Equipment MTCH: Multicast Traffic Channel MSB: Most Significant Bit NAS: Non-AS NB: NodeB (Node B) NR: New Radio (New Wireless Technology) PBR: Prioritized Bite Rate PC3:The reference point between the UE and the ProSe Function (Reference point between ProSe functions) PC5:The reference point between ProSe-enabled UEs used for control and user plane for ProSe Direct Discovery, ProSe Direct Communication and ProSe UE-to-Network Relay (ProSe Direct Discovery, ProSe Direct Communication) and control plane and user player for ProSe UE to network relay. (Reference point between ProSe-compatible UEs used in the application) PDCP: Packet Data Convergence Protocol PDU: Protocol Data Unit PHY: Physical layer PLMN: Public Land Mobile Network PPPP: ProSe Per Packet Priority PPPR: ProSe Per Packet Reliability ProSe: Proximity-Based Services PSDCH: Physical Sidelink Discovery Channel Nell) PSSCH: Physical Sidelink Shared Channel PSID: Provider Service Identifier QAM: Quadrature Amplitude Modulation QFI: QoS Flow Identifier QoS: Quality of Service SA1: System Architecture Working Group 1 Loop 1) SAP: Service Access Point SBCCH: Sidelink Broadcast Channel SCI: Sidelink Control Information SCS: Subcarrier Spacing SDAP: Service Data Adaptation Protocol SDU: Service Data Unit SIM: Subscriber Identity Module SL: Sidelink SL-BCH: SL Broadcast Channel SL-DCH: SL Discovery Channel SL-MCH: SL MCH (SL MCH) SL-MTCH: SL MTCH (SL MTCH) SR: Scheduling Request SRB: Signaling Radio Bearer RAN: Radio Access Network RAT: Radio Access Technology RLC: Radio Link Control RNTI: Radio Network Temporary Identifier ROHC: Robust Header Compression RRC: Radio Resource Control RSRP: Reference Signal Received Power RSRQ: Reference Signal Received Quality RSSI: Received Signal Strength Indicator RSU:Road Side Unit RX: Receiver or Receiving SAP: Service Access Point SBCCH: Sidelink Broadcast Control Channel Chanel) SCCH: Sidelink Control Channel SL-SCH: Sidelink Shared Channel TM: Transparent Mode T-UE: Target UE TX: Transmitter or Transmitting (sender or sender) UDC: Header Data Compression UE: User Equipment UL: Uplink UM: Unacknowledged Mode UMTS: Universal Mobile Telecommunications System Tem) UpL: Upper Layer USIM: Universal Subscriber Identify Module ) Uu:Uu Interface connecting UE to RAN -) V2V: Vehicle-to-Vehicle Communication V2X: Vehicle-to-X Communication (Vehicle-to-all communication) VQI:V2X QoS Identifier WG2: Working Group 2 WiFi:WLAN radio wireless technology, used interchangeably with WLAN in This document (WLAN wireless technology; in this specification, it is used interchangeably with WLAN) (It is being used) WLAN: Wireless Local Area Network

[0014] The following features / procedures / functions in this disclosure are described below. • NR V2X side link L2 structure. Covers unicast, groupcast, and broadcast transmission modes. V2X upper layer connection settings, V2X AS connection settings, V2X for V2X upper layer connection V2 connection setup procedure, including AS support. • Provides both the transmitter and receiver for V2X. • V2X RAT and interface selection. • Select V2X communication mode. Specifically, the following concepts and topics will be explained. 1. Layer 2 protocol structure, 2. Provisioning of the V2X transmitter and receiver. 3. Trigger for V2X transmission or V2X reception, 4. Who makes the selection and on what criteria, and the sender and receiver RATs and interfaces. Face selection, 5. Selection of transmission mode and selection criteria for the transmitter and receiver. 6. Unicast connection including a description of support parameters from the UE (e.g., the capabilities of the receiving end). Detailed management procedures, and scheduling entities or scheduling entities Unicast setting parameters set in the UE by the support UE in conjunction with T, 7. Different alternatives for connection management 8. Group connection settings and V2X upper layer group mapping to AS layer subgroups PING ideas, maintenance of mapping tables in AS, and AS to PHY Instructions. Various options for broadcast configuration and broadcast signaling configuration. Yon. 9. Method for UE processing of multiple simultaneous sidelink RRC connections. 10. PC5 Unicast Link granularity modeling, Unicast Link update, and Instructions for adding a nicast link.

[0015] (Exemplary communication systems and networks) Figure 1A shows the methods and apparatus described and claimed herein that can be incorporated. An exemplary embodiment of the communication system 100 is shown. As illustrated, The communication system 100 includes a Wireless Transmit / Receive Unit (WT). RU) 102a, 102b, 102c, 102d, 102e, 102f, and / or 102g (These are sometimes commonly or collectively referred to as WTRU102), Radio Access Network (RAN) 103 / 104 / 105 / 103b / 104b / 105b, core network 106 / 107 / 109, public exchange Public Switched Telephone Network (PSTN) 108, Internet 1 10, other networks 112, and V2X servers (or ProSe functions and The disclosed embodiments may include a server 113, but any number of WTRUs, It is understood that this refers to local stations, networks, and / or network elements. It is likely. WTRU102a, 102b, 102c, 102d, 102e, 102f, 1 Each of the 02g is configured to operate and / or communicate in a wireless environment. It can be a type of device or apparatus. Each WTRU102a, 102b, 102 c, 102d, 102e, 102f, 102g are shown in Figures 1A to 1E without a handheld. Although illustrated as a linear communication device, it is intended for a wide variety of use cases in wireless communication. Each WTRU is configured to transmit and / or receive wireless signals. It may include or embody any type of apparatus or device. This is understood to mean, as just one example, user equipment (UE), mobile station, fixed or mobile subscriber. Units, pagers, cellular phones, personal digital assistants Digital Assistant (PDA), smartphone, laptop, tablet, internet browser Notebooks, personal computers, wireless sensors, home appliances, Wearable devices such as smartwatches or smartwear, medical or electronic health Devices, robots, industrial equipment, drones, automobiles, buses or trucks, trains, This includes vehicles such as airplanes.

[0016] The communication system 100 may also include base stations 114a and 114b. Base station 114a connects to the core network 106 / 107 / 109 and the internet 110 , network service 113, and / or one or more other networks 112 To facilitate access to the communication network, WTRU102a, 102b, 1 Any ty configured to wirelessly interface with at least one of the 02c It can be a device. An example of a network service is a V2X service. ProSe services, IoT services, video streaming, edge computing You could also mention things like ng. Base station 114b is part of the core network 106 / 107 / 109 , Internet 110, other networks 112, and / or network services To facilitate access to one or more communication networks such as S113, RRH( Remote wireless heads) 118a, 118b, TRP (transmit / receive point) 119a, 119b, and / or at least one of RSU (Roadside Unit) 120a and 120b Any type of device configured to interface by wire and / or wireless It is possible. RRH118a, 118b are on the core network 106 / 107 / 1 09, Internet 110, Network Services 113, and / or other networks To facilitate access to one or more communication networks such as Work 112, WT Any tether configured to wirelessly interface with at least one RU102c It can be a device. TRP119a, 119b are core network 10 6 / 107 / 109, Internet 110, Network Services 113, and / or or to facilitate access to one or more communication networks such as other networks 112 To do this, it is configured to wirelessly interface with at least one WTRU102d. It can be any type of device. RSU120a and 120b are Network 106 / 107 / 109, Internet 110, Other Networks 11 2, and / or to one or more communication networks such as network service 113 To facilitate access, at least one of WTRU102e or 102f and wireless It can be any type of device configured to interface with it. Example Base stations 114a and 114b are wireless base station equipment (Base Transceiver Station: BTS), Node B, eNode B, Home Node B, Home eNode B, Next Generation Node B (Next Generation Node-B: gNode B), satellite, site controller, access This can be an access point (AP), a wireless router, etc. Base station 114 Although a and 114b are shown as single elements, base stations 114a and 114 b may include any number of interconnected base stations and / or network elements. It will be understood that this is possible.

[0017] Base station 114a can be part of RAN103 / 104 / 105, and this is Also, Base Station Controller (BSC), Wireless Network Controller Radio Network Controller (RNC), relay nodes and other base stations and It may also include and / or network elements (not shown). Base station 114b is RA It can be part of N103b / 104b / 105b, which is also base station control Other bases such as the BSC (Broadcasting System Controller), Wireless Network Controller (RNC), and relay nodes. It may also include local stations and / or network elements (not shown). Base station 114a This involves transmitting radio signals within a specific geographical area that can be called a cell (not shown) and / or it can be configured to receive. Base station 114b has a cell (not shown) and Within a specific geographical area where it can be called, wired and / or wireless signals are transmitted and / or it can be configured to receive. The cell is further divided into cell sectors. For example, a cell associated with base station 114a can be divided into three sectors. Therefore, in one embodiment, the base station 114a can, for example, control each cell. Each kuta can contain three transceivers, one each. In one embodiment, base station 11 4a employs Multiple-Input Multiple Output (MIMO) technology. This allows for the use of multiple transceivers for each sector of a cell. Cut.

[0018] Base station 114a connects to WTRU1 via air interfaces 115 / 116 / 117. It can communicate with one or more 02a, 102b, and 102c, and any suitable wireless communication Infrared (for example, radio frequency (RF), microwave, infrared) (IR), ultraviolet (UV), visible light, centimeter waves, millimeter waves, etc.) This is possible. Air Interface 115 / 116 / 117 can be used with any suitable wireless access technology. It can be established using the RAT (Regenerative Action Technique).

[0019] Base station 114b connects via wired or air interface 115b / 116b / 117b RRH118a, 118b, TRP119a, 119b, and / or RSU1 It can communicate with one or more of 20a and 120b, and this is possible with any suitable wired connection. For example, cables, optical fibers, etc.) or wireless communication links (for example, radio frequency (RF) ), microwaves, infrared (IR), ultraviolet (UV), visible light, centimeter waves, millimeter waves, etc. It is possible. Air interface 115b / 116b / 117b can be any suitable It can be established using wireless access technology (RAT).

[0020] RRH118a, 118b, TRP119a, 119b, and / or RSU120 a, 120b are connected via air interfaces 115c / 116c / 117c to the WTRU It can communicate with one or more 102c, 102d, 102e, and 102f, and this is possible. The appropriate wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR)) This can include ultraviolet (UV), visible light, centimeter waves, millimeter waves, etc. Air Interface Face 115c / 116c / 117c can use any appropriate radio access technology (RAT). It can be established using this method.

[0021] WTRU102a, 102b, 102c, 102d, 102e, 102f, and / or The 102g is a direct link for vehicle-to-vehicle (V2V) sidelink communication, etc. They can communicate with each other via the direct air interface 115d / 116d / 117d. This is possible with WTRU102a, 102b, 102c, 102d, 102e, 102f, and / or 102g is a direct connection for vehicle-to-infrastructure (V2I) sidelink communication, etc. Network services via the 115e / 116e / 117e air interface It can communicate with 113 (not shown in the diagram), which is any suitable wireless communication. It can be a link (for example, radio frequency (RF), microwave, infrared (IR)). (Ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). Air interface 115d / 1 16d / 117d is established using any appropriate radio access technology (RAT). It is possible.

[0022] More specifically, as described above, the communication system 100 is a multiple access system. It is possible to use one or more of the following: CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. The above channel access method can be adopted. For example, RAN103 / 104 / 1 Base stations 114a and WTRU 102a, 102b, 102c, or RA in 05 RRH118a, 118b, TRP119a in N103b / 104b / 105b, 119b, and / or RSU120a, 120b and WTRU102c, 102 d, 102e, and 102f are Universal Mobile Telecommunications Systems (Tel). Ecomunications System (UMTS) Terrestrial Radio Access (UMTS Terrestrial Radio Access) It can implement wireless technologies such as UTRA, and wideband CDMA (Cryptography) Using DMA (WCDMA) air interface 115 / 116 / 117 or 115 c / 116c / 117c can be established respectively. WCDMA is a high-speed packet High-Speed ​​Packet Access (HSPA) and / or Advanced High-Speed ​​Packet Access It can include communication protocols such as Access (Evolved HSPA: HSPA+). SPA stands for High-Speed ​​Downlink Packet Access (HSDPA) and / or High-Speed ​​Uplink Packet Access Packet Access (HSUPA) may be included.

[0023] In one embodiment, base stations 114a and WTR in RAN103 / 104 / 105 In U102a, 102b, 102c, or RAN103b / 104b / 105b RRH118a, 118b, TRP119a, 119b, and / or RSU120 a, 120b and WTRU102c, 102d are advanced UMTS terrestrial radio access devices. Evolved UMTS (Terrestrial Radio Access: E-UTRA) implements wireless technologies. Even if it's not, Long Term Evolution (LTE) is also fine. and / or use LTE-Advanced (LTE-A) for air interface - Establish 115 / 116 / 117 or 115c / 116c / 117c respectively. It can do this. Air interface 115 / 116 / 117 or 115c / 116c / 1 17c can implement 3GPP NR technology. LTE and LTE-A technologies are LTE D2D and V2X technologies and interfaces (such as sidelink communication) Includes. 3GPP NR technology, NR V2X technology and interface (sidelink). Includes (such as "trust").

[0024] In one embodiment, base stations 114a and WT in RAN103 / 104 / 105 In RU102a, 102b, 102c, or RAN103b / 104b / 105b RRH118a, 118b, TRP119a, 119b, and / or RSU120 a, 120b and WTRU102c, 102d, 102e, 102f are IEEE80 2.16 (For example, WiMAX (Worldwide Interoperability for Microwave Access) s)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (Interim Standard 2000:IS-2000) im Standard 95:IS-95), Interim Standard 856:IS-8 56) GSM (Global System for Mobile Communication) (registered trademark), EDG E (Enhanced Data rates for GSM Evolution), GERAN (GSM EDGE), etc. Wireless technology can be implemented.

[0025] The base station 114c in Figure 1A is, for example, a wireless router, home node B, and home e-node B. , or can be an access point, such as a business premises, house, vehicle, train, airborne, satellite, or manufacturing Any appropriate R to facilitate wireless connectivity in localized areas such as factories and campuses. AT can be used. In one embodiment, base station 114c and WTRU102e This refers to a Wireless Local Area Network (WLAN). To establish this, wireless technologies such as IEEE 802.11 can be implemented. In terms of configuration, base stations 114c and WTRU102d are wireless personal area network To establish a Wireless Personal Area Network (WPAN), IEEE 80 Wireless technologies such as 2.15 can be implemented. In yet another embodiment, base station 11 4c and WTRU102e are used to establish picocells or femtocells, cellular -Base RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE- A, NR, etc. can be used. It can have a direct connection to the network 110. Therefore, base station 114c, Access to the Internet 110 via core networks 106 / 107 / 109 It may not be necessary.

[0026] RAN103 / 104 / 105 and / or RAN103b / 104b / 105b are It can communicate with core networks 106 / 107 / 109, and this network is , voice, data, messaging, authorization and authentication, applications, and / or Voice Over Internet Protocol (VoI) P) Service WTRU102a, 102b, 102c, 102d, and 102f It can be any type of network configured to provide more than one. For example, core networks 106 / 107 / 109 handle call control, billing services, and mobile positioning. Baseline services, prepaid calling, internet connectivity, packet data network It can provide network connectivity, Ethernet® connectivity, video distribution, etc. It can perform high-level security functions such as user authentication.

[0027] Although not shown in Figure 1A, RAN103 / 104 / 105 and / or RAN1 03b / 104b / 105b and / or core network 106 / 107 / 109 , RAN103 / 104 / 105 and / or RAN103b / 104b / 105b Communicating directly or indirectly with other RANs employing the same or different RATs. It will be understood that this is possible. For example, by using E-UTRA wireless technology RAN103 / 104 / 105 and / or RAN103b / 104b / 1 In addition to being connected to 05b, core networks 106 / 107 / 109 also It can communicate with another RAN (not shown) that employs GSM or NR radio technology. Cut.

[0028] Core networks 106 / 107 / 109 also include WTRU102a, 102b, and 10 2c, 102d, 102e, and 102f are PSTN 108, Internet 110, It also functions as a gateway to access other networks 112. It is possible. PSTN108 is a plain old telephone service. It may include circuit-switched telephone networks that provide ce:POTS. Internet 110 is , the Transmission Control Protocol (Transm) in the TCP / IP Internet Protocol Suite User Datagram Protocol (TCP), User Datagram Protocol (e.g., m Protocol: UDP), Internet Protocol (IP), etc.) Interconnected computer networks and data that use a common communication protocol. It can include Vice's global system. Other networks 112 are other servers Wired or wireless communications networks owned and / or operated by service providers It can include any type of packet data. For example, network 112 can include any type of packet data. A network (e.g., an IEEE 802.3 Ethernet network) or one or more It can include another core network connected to the RAN, which is RAN103 / Same RAT as 104 / 105 and / or RAN103b / 104b / 105b Different RATs can be used.

[0029] WTRU102a, 102b, 102c, 102d, 10 in communication system 100 Some or all of the 2e and 102f may include multimode capability, for example. WTRU102a, 102b, 102c, 102d, 102e, and 102f are different. Multiple transceivers for communicating with different wireless networks via a wireless link It can include. For example, the WTRU102g shown in Figure 1A is a cellular-based radio technology. Base station 114a that can employ the technology, and IEEE802 wireless technology It can be configured to communicate with base station 114c.

[0030] Although not shown in Figure 1A, user devices can connect to the gateway via a wired connection. It will be understood that this is possible. The gateway is a residential gateway (Reside The RG can be the Core Gateway (RG). The RG is the core network 106 / 107 It can provide connectivity to / 109. Many of the ideas included herein are W This also applies to UEs that are TRUs, and UEs that connect to the network using wired connections. It will be understood that it can be used. For example, wireless interface 115, 1 The idea that applies to 16, 117 and 115c / 116c / 117c is for wired connections. The same can be applied.

[0031] Figure 1B shows a wireless device according to an embodiment illustrated herein, such as WTRU102. This is a block diagram of an exemplary device or apparatus configured for communication, as shown in Figure 1B. As an example, the WTRU102 includes a processor 118, a transceiver 120, and a transmit / receive element. Child 122, Speaker / Microphone 124, Keypad 126, Display / Touch Pad / indicator 128, non-removable memory 130, removable memory 132 Power supply 134, Global Positioning System (GPS) chipset It may include a 136 and other peripherals 138. WTRU102 is a single implementation. It is possible to include any subcombination of the aforementioned elements while maintaining consistency with the form. It will be understood that this is possible. Furthermore, the embodiment includes base stations 114a and 114b, A node that base stations 114a and 114b can represent, for example, and not limited to these, base station equipment (BTS), node B, site controller, and Node Point (AP), Home Node B, Advanced Node B (eNode B), Home Advanced Node B (HeNB), Home-Advanced Node B Gateway, Next-Generation Node B (gNod eB) and proxy nodes, etc., are particularly illustrated in Figure 1B and described herein. It is intended to include some or all of the elements.

[0032] Processor 118 includes general-purpose processors, dedicated processors, conventional processors, and digital processors. Digital Signal Processor (DSP), multiple microprocessors, One or more microprocessors, controllers, or microcontrollers associated with the DSP core. - Application Specific Integrated Circuit (ASIC) ), Field Programmable Gate Array (FP) GA) circuits, other types of integrated circuits (ICs), state machines It can be, for example. Processor 118 is responsible for signal coding, data processing, power control, Input / output processing, and / or the ability to enable WTRU102 to operate in a wireless environment. It can perform other functions of its own choosing. The processor 118 is connected to the transceiver 120. The transceiver can be coupled to the transmitting / receiving element 122. Figure 1B The processor 118 and transceiver 120 are shown as separate components. However, the processor 118 and transceiver 120 are located within an electronic package or chip. It will be understood that they can be integrated together.

[0033] The UE's transceiver element 122 connects to the base station via air interfaces 115 / 116 / 117. Between the station (e.g., base station 114a) or via air interface 115d / 116d To configure to transmit or receive signals to or from another UE via / 117d This is possible. For example, in one embodiment, the transmitting and receiving element 122 transmits and / or transmits an RF signal. This can be an antenna configured to receive. In one embodiment, a transmitting and receiving element 122, for example, to transmit and / or receive IR, UV, or visible light signals. It can be an emitter / detector configured as follows. Furthermore, in one embodiment, the transmit / receive element Sub-unit 122 can be configured to transmit and receive both RF signals and optical signals. The receiving element 122 transmits and / or receives any combination of wireless or wired signals. It will be understood that it can be configured in this way.

[0034] Furthermore, although the transmitting / receiving element 122 is shown as a single element in Figure 1B, WTRU1 02 can include any number of transmit / receive elements 122. More specifically, WTRU1 02 can employ MIMO technology. Therefore, in one embodiment, WTRU 102 transmits and receives radio signals via air interfaces 115 / 116 / 117. It may include two or more transmitting and receiving elements 122 (for example, multiple antennas).

[0035] The transceiver 120 modulates the signal to be transmitted by the transmitting and receiving element 122, and transmits and receives The signal received by the signal element 122 can be configured to demodulate the signal. Therefore, the WTRU102 can have multimode capability. The Seeba 120 WTRU102 supports multiple RATs, such as NR and IEEE 802.11. Alternatively, they can communicate via NR and E-UTRA, or use different RRH, TRP, and RSU. or to enable communication between nodes via multiple beams using the same RAT. It can include multiple transceivers.

[0036] The WTRU102 has a processor (118), a speaker / microphone (124), and a keypad. 126, and / or display / touchpad / indicator 128 (e.g., liquid Liquid Crystal Display (LCD) display unit, or with Organic Light-Emitting Diode (OLED) Display Unit It can be connected to these and receive user input data from them. SA118 also includes speaker / microphone 124, keypad 126, and / or It is possible to output user data to the display / touchpad / indicator 128. It can. Furthermore, the processor 118 controls the non-removable memory 130 and / or removable Access information from any type of suitable memory, such as bubble memory 132, and put it into memory. Data can be stored. Non-removable memory 130 is random access memory. Random-Access Memory (RAM), Read-Only Memory (R This includes OM, hard disks, or any other type of memory storage device. This is possible. Removable memory 132 is a subscriber identification module. ty Module: SIM card, memory stick, Secure Digital: It may include an SD memory card, etc. In one embodiment, the processor 118 is Servers hosted on a loud or edge computing platform Alternatively, on a home computer (not shown), etc., the WTRU102 is physically located It is possible to access information from non-existent memory and save data.

[0037] The processor 118 receives power from the power supply 134 and powers the other components in the WTRU 102. It can be configured to distribute and / or control power to the network. Power supply 134 This can be any suitable device for supplying power to the WTRU102. For example, power source 134 may include one or more dry cell batteries, solar cells, fuel cells, etc. .

[0038] The processor 118 can also be coupled to the GPS chipset 136, and the GPS chip The topset 136 contains location information (e.g., longitude and) about the current location of WTRU102. It can be configured to provide latitude. In addition, or instead, WTRU102 is a base station (e.g., base station 114a, Receive location information via air interfaces 115 / 116 / 117 from 114b). It is possible, as well as the timing of signals received from two or more nearby base stations The position can be determined based on the .WTRU102 is an arrangement with one embodiment. While maintaining compatibility, location information can be acquired using any appropriate location determination method. It will be understood that...

[0039] The processor 118 can also be coupled to other peripherals 138, and these peripherals The peripheral device 138 provides additional features, functionality, or wired and / or wireless connectivity. It may include one or more software and / or hardware modules. For example, peripheral device 138 includes various sensors such as accelerometers, biometrics (for example, Fingerprint sensor, electronic compass, satellite transceiver, digital camera (for photos or videos) ), Universal Serial Bus (USB) port or other phase Interconnection interfaces, vibration devices, TV transceivers, hands-free headsets Bluetooth (registered trademark) module, Frequency Modulation (F) M) Wireless unit, digital music player, media player, video game player This may include things like a web browser.

[0040] WTRU102 is used in sensors, home appliances, smartwatches, or smart wear. Wearable devices, medical or electronic health devices, robots, industrial equipment, drones , within other devices or equipment such as automobiles, trucks, trains, or airplanes It can be materialized. WTRU102 can constitute one of the peripheral devices 138. Through one or more interconnect interfaces, such as an interconnect interface, Connects to other components, modules, or systems of the device or equipment. It is possible.

[0041] Figure 1C is a system diagram of RAN103 and core network 106 according to an embodiment. Yes. As mentioned above, RAN103 connects to WTRU10 via air interface 115. To communicate with 2a, 102b, and 102c, UTRA wireless technology is adopted. Yes, it is possible. RAN103 can also communicate with the core network 106. Figure 1C As shown, RAN103 may include nodes B140a, 140b, and 140c. These are respectively connected via the air interface 115 to WTRU102a and 102b It can include one or more transceivers for communicating with 102c. Node B14 0a, 140b, and 140c are each associated with a specific cell (not shown) within RAN103. It can be attached. RAN103 can also include RNC142a and 142b. RAN103, while maintaining consistency with one embodiment, allows any number of nodes B and R It will be understood that NC can be included.

[0042] As shown in Figure 1C, nodes B140a and B140b communicate with RNC142a. This is possible. Furthermore, node B140c can communicate with RNC142b. The B140a, 140b, and 140c are connected via the Iub interface to their respective RNs. It can communicate with C142a and 142b. RNC142a and 142b are Iur They can communicate with each other via an interface. RNC142a and 142b This controls each of the nodes B140a, 140b, and 140c to which it is connected. It can be configured in such a way. Furthermore, each of RNC142a and 142b is an out Tarloop power control, load control, reception control, packet scheduling, handover It also performs other functionalities such as control, macrodiversity, security features, and data encryption. Alternatively, it can be configured to support it.

[0043] The core network 106 shown in Figure 1C is a Media Gateway (M GW)144, Mobile Switching Center (MSC) 146. Serving GPRS Support Node (SGSN) )148, and / or Gateway GPRS Support Node (Gateway GPRS Support Node) rt Node:GGSN)150 can be included. Each of the aforementioned elements is part of the core network 1 Although illustrated as part of 06, any one of these elements is the core network It is understood that it may be owned and / or operated by an entity other than a business operator. It will likely happen.

[0044] RNC142a within RAN103 communicates with the core network via the IuCS interface. It can be connected to MSC146 in 106. MSC146 is connected to MGW144. It can be connected. MSC146 and MGW144 are WTRU102a, 102 b, 102c provides access to circuit-switched networks such as PSTN108, Facilitates communication between WTRU102a, 102b, and 102c and conventional landline communication devices. It can be done.

[0045] RNC142a within RAN103 also communicates via the IuPS interface to the core network. It can connect to SGSN148 within network 106. SGSN148 is GGS It can be connected to N150. SGSN148 and GGSN150 are WTRU1 02a, 102b, 102c, and packet-switched networks such as Internet 110. Provides access to WTRU102a, 102b, 102c, and IP-enabled devices. This can facilitate communication between them.

[0046] As mentioned above, core network 106 is also owned by other service providers. and / or other wired or wireless networks that operate, including other It can connect to network 112.

[0047] Figure 1D is a system diagram of RAN104 and core network 107 according to an embodiment. Yes. As stated above, RAN104 connects to WTRU10 via air interface 116. To communicate with 2a, 102b, and 102c, E-UTRA wireless technology is employed. RAN104 can also communicate with the core network 107.

[0048] RAN104 can include e-nodes B160a, 160b, and 160c, but R AN104 may include any number of enodes B while maintaining consistency with one embodiment. It will be understood what is possible. eNodes B160a, 160b, and 160c are respectively It communicates with WTRU102a, 102b, and 102c via the air interface 116. It may include one or more transceivers for this purpose. In one embodiment, e-node B16 0a, 160b, and 160c can implement MIMO technology. Therefore, e The B160a, for example, uses multiple antennas to send wireless signals to the WTRU102a. It can transmit and receive wireless signals from WTRU102a.

[0049] Each of the e-nodes B160a, 160b, and 160c is a specific cell (not shown). ) can be associated with wireless resource management decisions, handover decisions, and uplinks. and / or configured to handle user scheduling in the downlink. This can be achieved. As shown in Figure 1D, e-nodes B160a, 160b, and 160c are They can communicate with each other via the X2 interface.

[0050] The core network 107 shown in Figure 1D is a mobility management gateway (Mobility Management Gateway). Management Gateway (MME) 162, Serving Gateway 164, and Packet Includes data network (Packet Data Network: PDN) gateway 166. This is possible. Although each of the aforementioned elements is illustrated as part of the core network 107, Any one of these elements is owned by an entity other than the core network operator. It will be understood that they may and / or operate.

[0051] MME162 connects to e-node B160a in RAN104 via the S1 interface. It can be connected to 160b and 160c respectively and functions as a control node. It is possible. For example, MME162 is a user of WTRU102a, 102b, and 102c. -ser authentication, bearer activation / deactivation, WTRU102a, 102b, 1 It can be responsible for selecting a specific serving gateway during the initial connection of 02c. The MME162 also supports RAN104 and other wireless technologies such as GSM or WCDMA. This provides a control plane function for switching between other RANs (not shown) that have been adopted. It is possible.

[0052] The serving gateway 164, via the S1 interface, accesses the RAN104. It can be connected to nodes B160a, 160b, and 160c, respectively. The Bing Gateway 164 is generally used between WTRU102a, 102b, and 102c. User data packets can be routed and forwarded. Serving gateway Way 164 also anchors the user plane during eNode B handover. And, when downlink data is available on WTRU102a, 102b, and 102c, Triggering aging, managing the context of WTRU102a, 102b, and 102c It can perform other functions, such as processing and saving data.

[0053] Serving gateway 164 can also connect to PDN gateway 166. This applies to WTRU102a, 102b, and 102c, as well as to Internet 110 and other networks. Provides access to the ket-switched network, WTRU102a, 102b, 102 This facilitates communication between device c and IP-enabled devices.

[0054] The core network 107 can facilitate communication with other networks. For example, core network 107 connects to WTRU102a, 102b, and 102c, and to the PSTN. Provides access to circuit-switched networks such as WTRU102a, WTRU102 b, 102c, and communication between conventional landline communication devices can be facilitated. For example, the core network 107 is connected to the PSTN 108. An IP gateway that functions as an interface (for example, an IP multimedia subnet) It may include a system (IP Multimedia Subsystem: IMS) server, or it It can communicate with WTRU102a, 10 2b, 102c, other services owned and / or operated by other service providers Provides access to network 112, which can include wired or wireless networks. It can be provided.

[0055] Figure 1E is a system diagram of RAN105 and core network 109 according to an embodiment. Yes. RAN105 connects to WTRU102a and 10 via air interface 117. To communicate with 2b, NR radio technology can be employed. RAN105 also uses It can communicate with the A-Network 109. N3IWF199 is an air interface To communicate with WTRU102c via S198, non-3GPP wireless technology is employed. It can do that. N3IWF199 can also communicate with core network 109. .

[0056] RAN105 can include enodes B180a and 180b, but RAN1 05 can include any number of gnodes B while maintaining consistency with one embodiment. It will be understood that g-nodes B180a and 180b are air interfaces, respectively. One or more to communicate with WTRU102a and 102b via face 117 It may include transceivers. Integrated access and backhaul connectivity is used. In one embodiment, the same air interface is used between the WTRU and the g node B. This is possible, and this is the core network 109 via one or more gNBs. This is possible. In one embodiment, g nodes B180a and 180b are MIMO, MU - MIMO and / or digital beamforming technologies can be implemented. Therefore, the g node B180a can, for example, use multiple antennas to connect to WTRU10 It can transmit a wireless signal to 2a and receive a wireless signal from WTRU102a. The RAN105 can employ other types of base stations such as eNode B. should be solved. Also, RAN105 can adopt one or more types of base stations which should be understood. For example, RAN can adopt eNodeB and gNodeB .

[0057] N3IWF199 can include non-3GPP access point 180c, but N 3IWF199 can include any number of non-3GPP access points while maintaining consistency with one embodiment which will be understood. Non-3GPP access point 1 80c can include one or more transceivers for communicating with WTRU102c via air interface 198 . In one embodiment, non-3GPP access point 1 80c can communicate with WTRU102c via air interface 198 using the 802.11 protocol .

[0058] Each of gNodeBs 180a and 180b can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in the uplink and / or downlink, etc. As shown in Figure 1E, gNodeBs 180a and 180b can communicate with each other via the Xn interface . As shown in Figure 1E, the core network 109 can be a 5G core network (5G Core Network : 5GC). 5GC can provide a number of communication services to customers interconnected by a radio access network

[0059] <##00##903> . 5GC can provide a number of communication services to customers interconnected by a radio access network . 5GC can provide a number of communication services to customers interconnected by a radio access network Cluster 109 is composed of a number of entities that execute the functionality of the core network. This When used in this specification, the term "core network entity" or "network function" refers to any entity that executes one or more functionalities of the core network. Such core network entities can be logical entities implemented in the form of software (i.e., computer executable instructions) stored in the memory of a device or computer system configured for wireless and / or network communication and executed on a processor, such as those illustrated in FIG. 1F. It should be understood that it can be.

[0060] As shown in FIG. 1E, the 5G core network 109 includes an Access and Mobility Management Function (AMF) 172, a Session Management Function (SMF) 174, User Plane Functions (UPF) 176a and 176b, a User Data Management Function (UDM) 197, an Authentication Server Function (AUSF) 190, a Network Exposure Function (NEF) 196, a Policy Control Function (PCF) 184, a Non-3GPP Interworking Function (N3IWF) 199, an Application Function (AF) 188, a User Data As shown in FIG. 1E, the 5G core network 109 includes an Access and Mobility Management Function (AMF) 172, a Session Management Function (SMF) 174, User Plane Functions (UPF) ​It can include User Data Repository (UDR) 178. The elements are illustrated as part of the 5G core network 109, but these elements Either one is owned and / or is owned by an entity other than the core network operator. It will be understood that it can be operated. Also, the 5G core network is It does not have to consist of all of these elements, and can be composed of additional elements, these It should also be understood that each element can be composed of multiple instances. 1E indicates that network functions are directly connected to each other, but the diameter route Communication is conducted via routing agents such as message buses or other routing agents. It should be understood that this is possible. Figure 1E shows the connections between network functions. It is shown that this is achieved through a set of interfaces or reference points, but Network functionality is invoked by other network functions or services. This can be modeled, described, or implemented as a set of services that are called. It should be understood that calls to network function services are made between network functions. Direct connection, message exchange via message bus, calling software functions, etc. This can be achieved.

[0061] The AMF172 can be connected to the RAN105 via the N2 interface, and control It can function as a node. For example, AMF172 can handle registration management, connection management, AMF can handle reachability management, access authentication, and access authorization. The tunnel configuration information of the plane is transferred to RAN105 via the N2 interface. It can handle this. The AMF172 can handle SMF via the N11 interface. It can receive user plane tunnel configuration information from the AMF172. Specifically, NA is connected between WTRU102a, 102b, and 102c via the N1 interface. S packets can be routed and forwarded. The N1 interface is shown in Figure 1E. It is not shown.

[0062] The SMF174 can be connected to the AMF172 via the N11 interface. It can connect to the PCF184 via the N7 interface, and the N4 interface It can be connected to UPF176 via this. SMF174 functions as a control node. It is possible. For example, SMF174 is a session management, WTRU102a, 102 b. IP address allocation for 102c, UPF176a and UPF176b Managing and configuring traffic steering rules in AMF172, as well as for AMF172. It can be responsible for generating downlink data notifications.

[0063] UPF176a and UPF176b correspond to WTRU102a, 102b, and 102c. To packet data networks (DNs) such as Internet 110 It provides access and communication between WTRU102a, 102b, 102c and other devices. This can make it easier to communicate. UPF176a and UPF176b are also WTRU1 Access to other types of packet data networks for 02a, 102b, and 102c. It can provide. For example, other network 112 is an Ethernet network It can be any type of network that exchanges packets of data or information. UPF176a and UPF176b can receive traffic steering rules from SMF174 via the N4 interface. UPF176a and UPF176b can provide access to the packet data network by connecting to the packet data network at the N6 interface or by connecting to other UPFs at the N9 interface. In addition to providing access to the packet data network, UPF176 can be responsible for packet routing and forwarding, enforcement of policy rules, handling of quality of service for user plane traffic, and buffering of downlink packets.

[0064] AMF172 can also be connected to N3IWF199 via the N2 interface. N3IWF facilitates the connection between WTRU102c and the 5G core network 170 via a radio interface technology not defined by 3GPP. AMF can interact with N3IWF199 in the same or a similar way as it interacts with RAN105.

[0065] PCF184 is connected to SMF174 via the N7 interface, connected to AMF172 via the N15 interface, and can be connected to the application function (AF) 188 via the N5 interface. The N15 and N5 interfaces are not shown in Figure 1E. PCF184 can interact with control functions such as AMF172 and SMF174. ​​​​​​​​​​​​​Policy rules are provided to the plane nodes, and the control plane nodes enforce these rules. It can be made possible. The PCF184 allows AMF to use the N1 interface. To enable policy delivery to WTRU102a, 102b, and 102c, WTRU10 Policies can be sent to AMF172 for 2a, 102b, and 102c. Subsequently, the policy will be enforced or applied under WTRU 102a, 102b, and 102c. It is possible.

[0066] UDR178 functions as a repository for authentication credentials and enrollment information. UDR allows network functionality to add to, read from, and modify data within the repository. It can connect to network functions so that it can do so. For example, UDR1 78 can connect to PCF184 via the N36 interface, and UDR17 8 can connect to NEF196 via the N37 interface, and UDR178 It can connect to the UDM197 via the N35 interface.

[0067] The UDM197 serves as an interface between the UDR178 and other network functions. It can function. UDM197 recognizes network function access of UDR178. This is possible. For example, UDM197 can connect to AMF17 via the N8 interface. It can connect to 2, and UDM197 can connect to SMF174 via the N10 interface. It can connect to the AUSF190 via the N13 interface, and the UDM197 can connect to the AUSF190 It can be connected to. UDR178 and UDM197 can be tightly integrated. .

[0068] The AUSF190 performs authentication-related operations and communicates via the N13 interface to the UDM1 Connect to 78, and then connect to AMF172 via the N12 interface.

[0069] NEF196 provides capabilities and services within the 5G core network 109. It will be exposed to Relation function 188. The exposure will be performed via the N33 API interface. The NEF can connect to the AF188 via the N33 interface, and 5G To expose the capabilities and services of A-Network 109, other network functions It can be connected.

[0070] Application function 188 is compatible with the network function of the 5G core network 109. They can interact. Interaction between application function 188 and network function The action can occur via a direct interface or via NEF196. It is possible. Application function 188 is part of the 5G core network 109 and It can be considered, or outside the 5G core network 109, mobile network This can be implemented by companies that have business relationships with work providers.

[0071] Network slicing is a method used by mobile network operators to control the network infrastructure of their network infrastructure. It can be used to support one or more "virtual" core networks behind the face. This is a mechanism that "slashes" the core network into one or more virtual networks. "Issing" means different services running across different RANs or a single RAN. This relates to supporting the type. Network slicing allows operators to Sina in various markets where diverse requirements such as functionality, performance, and isolation are demanded. Creating a customized network to provide the best solution for Rio can.

[0072] 3GPP is based on the concept of network slicing for 5G core networks. It is being designed. Network slicing is a very diverse and timely design for network operators. This presents a diverse range of 5G use cases that demand extreme requirements (e.g., massive IoT). (critical communications, V2X, and enhanced mobile broadband) It is an excellent tool that can be used to port. Network slicing Without using this technology, each use case would lack a specific set of performance, scalability, and capabilities. When usability requirements exist, the network architecture can accommodate a wider range of use cases. It may not be flexible and scalable enough to provide efficient support. Furthermore, The introduction of new network services should be carried out more efficiently.

[0073] In network slicing scenarios, WTRU102a, 102b, and 102c are used. It can be connected to the AMF172 via the N1 interface. The AMF is logical It can be part of one or more slices. AMF can be one or more UPF (singular) (or multiple) 176, SMF (singular or plural) 174, and other network functions, It can coordinate the connection or communication of WTRUs. UPF(singular or plural) 176, Each of the SMF(singular or plural)174 and other network functions is different. They can be different slices or parts of the same slice. When they are part of a system, they have different computing resources and security credentials. They can be separated from each other in the sense that they can utilize things like `initials`.

[0074] The 5G core network 109 can facilitate communication with other networks. For example, 5G core network 109 is connected to PSTN10 An IP gateway that acts as an interface between 8 (e.g., IP Multimedia) It may include an Assubsystem (IMS) server, or be able to communicate with it. For example, the core network 109 communicates via the Short Message Service. Short Message Service (SMS) service It can include or communicate with a center. For example, a 5G core network. Workpiece 109 is WTRU102a, 102b, 102c and server or application This facilitates the exchange of non-IP data packets between the 188 function and the other function. Core network 170 connects to WTRU102a, 102b, and 102c, and other services. Other wired or wireless networks owned and / or operated by the provider It can provide access to network 112, which may include it.

[0075] The core net described herein and shown in Figures 1A, 1C, 1D, and 1E Twerk entities are given to those entities in certain existing 3GPP specifications. They are identified by their current names, but in the future, those entities and functionalities may be renamed. It may be identified as a specific entity or function, and may be subject to future 3GPP NR specifications. It is understood that this can be combined with future specifications issued by 3GPP, including the "[Name]" designation. Therefore, as explained and shown in Figures 1A, 1B, 1C, 1D, and 1E. Specific network entities and functionalities are provided for illustrative purposes only. The subject matter disclosed and claimed in the specification is defined now or will be defined in the future. Regardless, it is reasonable to assume that it can be materialized or implemented in any similar communication system. It is understood.

[0076] Figure 1F is a block diagram of an exemplary computing system 90, which is a diagram of the system. One or more devices of the communication network shown in Figures 1A, 1C, 1D, and 1E, RAN103 / 104 / 105, Core Network 106 / 107 / 109, PSTN1 08, Internet 110, Other Networks 112, or Network Server This can be embodied in specific nodes or functional entities in bis113. The computing system 90 consists of computers or servers, and is primarily composed of It can be controlled by computer-readable instructions, and computer-readable instructions are software It can be in that form, or wherever such software is stored, Or by what means can it be accessed? Such computer-readable instructions ...to be executed within the processor 91 and to cause the computing system 90 to operate. This is possible. Processor 91 is a general-purpose processor, dedicated processor, conventional processor, and Digital signal processor (DSP), multiple microprocessors, and a DSP core related to 1 Multiple microprocessors, controllers, microcontrollers, application-specific integrated circuits Circuits (ASICs), field-programmable gate array (FPGA) circuits, and others It can be an integrated circuit (IC), a state machine, etc. Processor 91 is , signal coding, data processing, power control, input / output processing, and / or computing Any other functionality that enables the 90 system to operate on a telecommunications network It can be executed. The coprocessor 81 has different options than the main processor 91. It is a processor that can perform additional functions or support processor 91. Processor 91 and / or coprocessor 81 are operated by the methods disclosed herein. It can receive, generate, and process data related to the device.

[0077] During operation, processor 91 fetches, decodes, and executes instructions, and computes The system's main data transfer path is the system bus 80, which connects to other resources. Information is transferred via this system bus. Such a system bus is used within the computing system 90. It connects components and defines the medium for data exchange. System bus 80 is typical. In terms of data lines, there are data lines for sending data and address lines for sending addresses. This also includes control lines for sending interrupts and operating the system bus. An example of a system bus 80 like this is the Peripheral Component Interconnect (Pe It is a ripheral component interconnect (PCI) bus.

[0078] The memory connected to the system bus 80 is random access memory. Memory (RAM) 82 and Read Only Memory (ROM) 93 Includes. Such memory includes circuits that can store and retrieve information. ROM9 3 generally includes saved data that cannot be easily modified. The data stored in RAM82 , which can be read by processor 91 or other hardware devices, or It can be changed. Access to RAM82 and / or ROM93 is via memory code It can be controlled by the controller 92. The memory controller 92 controls the execution of instructions. When this happens, an address translation function is provided to convert virtual addresses to physical addresses. Yes, it is possible. The memory controller 92 also isolates processes within the system and user processes. It can provide a memory protection function that isolates system processes from the system. A program running in the first mode is defined by the virtual address space of its process. Only the memory that has been uploaded can be accessed, and memory sharing between processes is configured. Unless otherwise specified, it is not possible to access memory within the virtual address space of another process. do not have.

[0079] Furthermore, the computing system 90 receives instructions from the processor 91 to the printer 9 4. Communicate with peripherals such as keyboard 84, mouse 95, and disk drive 85. It may include a peripheral device controller 83 that plays a role in this.

[0080] The display 86, controlled by the display controller 96, is a computer This is used to display the visual output generated by the 90-inch display system. The visual output includes text, graphics, animated graphics, and It can include video. Visual output is a graphical user interface (Graphi It can be provided in the form of a User Interface (GUI). Display 86 is CRT-based video displays, LCD-based flat panel displays, gas It can be implemented as a plasma-based flat panel display or a touch panel. The display controller 96 generates the video signal that is sent to the display 86. Includes the necessary electronic components to achieve this.

[0081] Furthermore, the computing system 90 is shown in Figures 1A, 1B, 1C, and 1D, if The following are shown in Figure 1E: RAN103 / 104 / 105, Core Network 106 / 107 / 10 9. PSTN108, Internet 110, WTRU102, or other network Computing systems to external communication networks or devices such as 112 Used to connect the M90, the computing system 90 uses those networks It can be made possible to communicate with other nodes or functional entities in the project, for example. It may include communication circuits such as a wireless or wired network adapter 97. This can be used alone or in combination with the processor 91, in the specific configurations described herein. It can be used to perform the sending and receiving steps for a location, node, or functional entity. can.

[0082] Figure 1G shows the methods and apparatus described and claimed herein that can be incorporated. An exemplary communication system 111 is shown. As illustrated, the exemplary communication System 111 includes wireless transceiver units (WTRUs) A, B, C, D, E, F, and base station g This includes NB121, V2X server 124, and RSU123a and RSU123b. However, the disclosed embodiments can be any number of WTRUs, base stations, gNBs, V2X networks. It will be understood that this is intended to be a twerk and / or network element. One, some, or all WTRUs A, B, C, D, E are access networks. It may be outside the scope of coverage 122. WTRU A, B, and C are V2X group They form a group, with WTRU A being the group lead and WTRU B being the group lead. WTRU C is a group member. WTRU A, B, C, D, E, F are accessors. If under network coverage, via Uu interface 129a / 129b and are under or outside access network coverage In that case, via the sidelink (PC5 or NR PC5) interface 125a, They can communicate with each other. WTRU A, B, C, D, E, F are vehicle-to-network. Work communication (V2N) interface 126 or side link interface 125 Communication with the RSU is possible via b. WTRU A, B, C, D, E, F are vehicles. V2X server via V2I interface 127 It can communicate with 124. WTRU A, B, C, D, E, F are vehicle-to-person communication ( Vehicle-to-Person (V2P) interface 128 to communicate with another UE. It is possible.

[0083] Any or all of the apparatus, systems, methods, and processes described herein However, computer executable instructions stored on a computer-readable storage medium (for example, programme It can be embodied in the form of Gram code, and this instruction is on processor 118 or 9 When executed by a processor such as 1, the processor provides the system described herein. It is understood that the method, method, and process must be executed and / or implemented. Specifically Any of the steps, operations, or functions described herein are wireless and / or devices or computing systems configured for wired network communication Implemented in the form of such computer executable instructions that run on the processor. It is possible. Computer-readable storage media can store information in any non-temporary manner (e.g., For example, volatile and non-volatile substances implemented by tangible or physical methods or technologies. This includes removable and non-removable media, but such computer-readable storage media This does not include signals. Computer-readable storage media include RAM, ROM, EEPROM, Flash memory or other memory technologies, CD-ROM, Digital Multipurpose Disk (Di Digital Versatile Disk (DVD) or other optical disc storage, magnetic cassette, Magnetic tape, magnetic disk storage or other magnetic storage devices, or Used to store desired information and accessed by computing systems. This includes, but is not limited to, other tangible or physical media that can be used.

[0084] (Connection management in LTE D2D sidelink) (One-to-many ProSe direct communication) ProSe, especially in LTE D2D sidelink communication, one-to-many ProSe direct communication Trust has the following characteristics: • One-to-many ProSe direct communication is connectionless. Therefore, PC5 control player There is no signaling via [the network / platform]. The wireless layer is for users to send IP packets between UEs directly involved in communication. We provide plaincast communication services. The group members share a secret, from which they derive the group security key. All user data for that group can be encrypted. • Authorization for one-to-many ProSe direct communication is granted by the ProSe function using the PC3 reference point. This is configured within UE. • ProSe UE configuration parameters (for example, ProSe group IP multicast parameters) Dress, ProSe group ID, group security materials, wireless-related for sending and receiving. The parameters are set within the UE.

[0085] (1-to-1 ProSe direct communication) 1-to-1 ProSe direct communication is connection-oriented and secure between two UEs via PC5. This is achieved by establishing a Layer 2 link. (The theory of one-to-one sidelink communication) Figure 2 shows the control plane for establishing, maintaining, and disconnecting the connection. However, it should be noted that the PC5 and SideLink interfaces are used interchangeably. I want to be treated that way.

[0086] Each UE (for example, UE A and UE B in Figure 2) is a ray for unicast communication. It has a Layer 2 ID, and this Layer 2 ID is used to determine all that it transmits over a Layer 2 link. The source Layer 2 ID field of each frame is included, and it is a Layer 2 link It is included in the destination Layer 2 ID of all frames received above. Unicast communications and Conflicts between destination Layer 2 IDs in one-to-many communication are resolved by RAN WG2. UE This means that the Layer 2 ID for unicast communication is at least locally unique. It needs to be made sure.

[0087] A Layer 2 link for one-to-one ProSe direct communication is provided by the Layer 2 IDs of the two UEs. Identified by combination. This means that the UE uses the same Layer 2 ID for a one-to-one correspondence. This means that multiple Layer 2 links can be involved for ProSe direct communication. ru.

[0088] In ProSe, as shown in Figure 3, PC5-S signaling handles connection management and Designed for security management. In Figure 3, in step S302, UE 1 sends a communication request directly to UE2. In step S304, authentication and security Implement the establishment of a tier association.

[0089] The connection management procedure includes PC5 link setup, link maintenance using the keep-alive function, This includes the procedure for unlinking. Security management is PC5 security mode control. Includes procedures and (re)keying procedures.

[0090] PC5-S does not allow parameter settings for the AS layer, except for security parameters. RRC currently requires PC5 AS configuration to support sidelink communication. It should be noted that it is not used. RRC is sidelink broadcasting. Sidelink Broadcast Control Channel (SBCCH) Used solely for broadcasting generic link configuration parameters.

[0091] (QoS support in ProSe) QoS control is packet-based QoS. ProSe upper layer (i.e., PC When a layer above the PC5 access layer passes a protocol data unit to the PC5 access layer, The upper layer of the SE determines the priority of each Prose packet from a range of eight possible values ​​(ProSe Per-Packet Priority (PPPP), and Prose Packet Priority from a range of 8 possible values. Provides per-packet reliability (ProSe Per-Packet Reliability: PPPR). PPPR is independent of the destination Layer 2 ID and is one-to-one and one-to-many ProS This applies to both direct and direct communications. PPPP and PPPR are applied at the application layer. Therefore, it is selected. The priority value for each Prose packet is assigned to the PC5-S message. It will be targeted. The UE will be used to send one of the PC5-S messages. A priority value is set for each Prose packet. PPPP and PPPR refer to the modes, or schedules, by which the UE accesses the media. It is neutral regarding whether to use manual transmission mode or autonomous transmission mode.

[0092] The ProSe access layer associates protocol data units received from higher layers. The priority of each Prose packet is used for other UE transmissions (i.e., the same (Protocol data units associated with different priorities waiting to be sent within the UE) and inter-UE transmission (i.e., transmissions waiting within different UEs, associated with different priorities) Prioritize the transmission of the specified protocol data units. The ProSe access layer associates protocol data units received from higher layers. Using the provided PPPR, the transmission behavior, or for example, packet duplication, is determined and coordinated. .

[0093] (PC5 Access Layer (Wireless) Settings for ProSe) The user plane access protocol stack (AS) for the PC5 interface is shown in Figure 4. As shown, it consists of PDCP, RLC, MAC, and PHY.

[0094] As mentioned above, one-to-many ProSe communication via the PC5 interface is connectionless. It is a wireless device and does not have a specific intended receiver. Therefore, it does not have control over the receiver, or wireless No configuration is required depending on the protocol stack or the capabilities of the wireless resources. PC5 interface One-to-one ProSe communication via a face is connection-oriented, but as mentioned above, it is used to establish a connection. The PC5-S signaling protocol used is not designed, and the AS layer parameters It is not possible to configure this. As a result, both one-to-many ProSe communication and one-to-one ProSe communication are not possible. Regarding this, the RX UE protocol stack configuration provides all the necessary functions for RX UE. It is predefined in the specifications provided. For example, sidelink communication has HARQ Fee Do not use DOBAC, use RLC UM for sidelink communication, sidelink communication For communication, ROHC unidirectional mode is used for PDCP header compression, and for sidelink communication... One example is not using Uplink Data Compression (UDC). The receiving UE has at least one RLC UM entity for each transmitting peer UE. Maintenance is required. The receiving RLC UM entity used for sidelink communication is No configuration is required before receiving the first RLC UMD PDU. For TX UE, AS The parameters are set from or derived from QoS inputs provided by the upper layer. For example, the UE uses multiple logical channels based on QoS input from the upper layer. It is possible to establish a MAC subheader containing the LCID, which is one source ray. The logical channel is uniquely identified within the range of combinations of the Ya2ID and the destination Layer 2ID. As mentioned above, no parameters for logical channel prioritization are set. The Access Stratum (AS) is accessed by the upper layers via the PC5 interface. The PPPP protocol data unit is provided for transmission. Each logical channel has P PPP is associated. Similarly, PPPR is not set. AS is upper ray PPP protocol data unit transmitted via PC5 interface by Ya R is provided. The radio resources used for ProSe direct communication are provided by the upper layer. Based on the provided QoS input and wireless resource configuration information, when outside of coverage, U Can it be autonomously selected by the E AS, or reported to the eNB by the UE? Considering the QoS inputs and resource settings of higher layers, for example, within coverage When it is outside of coverage, it can be scheduled by eNB. ru.

[0095] (Connection management in LTE V2X sidelink) (One-to-many V2X communication) V2X communication on the PC5 reference point is a type of ProSe direct communication, where the PC5 base V2X communication on the quasi-point is connectionless and requires a PC5 control plane for connection establishment. There is no signaling via this. V2X messages are transmitted via the PC5 user plane to the UE. They are exchanged in between.

[0096] (1-to-1 V2X communication) LTE does not support connection orientation and does not support one-to-one V2X communication. stomach.

[0097] (QoS support in V2X) QoS control for V2X sidelink communication is packet-based QoS, and sector It follows the same principle as the ProSe sidelink communication described in section 2.2.3.

[0098] (PC5 Access Layer (Wireless) Settings for V2X) The PC5 access layer settings are the same as those for ProSe direct communication. ru.

[0099] One-to-many V2X communication via the PC5 interface is connectionless and is intended to be It does not have a specific receiver. Therefore, it does not have receiver control or wireless protocol stack. Alternatively, no configuration is required depending on the capabilities of the wireless resources. As a result, the RX UE protocol The stack configuration is a predefined specification that includes all the necessary features for RX UE. For example, HARQ feedback is not used for sidelink communication. RLC UM is used for link communication, and PDCP header compression is used for side-link communication. ROHC unidirectional mode is used, and uplink data compression (UD) is used for sidelink communication. One example is not using C). The receiving UE must have at least one R for each transmitting peer UE. The LC UM entity needs to be maintained. The receiving RL used for sidelink communication. The C UM entity does not need to be configured before receiving the first RLC UMD PDU. In the case of TX UE, AS parameters are provided by the QoS input and the higher layer. It is set or derived from other configuration parameters such as the TX profile. For example, the UE establishes multiple logical channels based on QoS input from the upper layer. It is possible. The LCID included in the MAC subheader is one source Layer 2 ID and The logical channel is uniquely identified within a range of destination Layer 2 ID combinations. No parameters for logical channel prioritization are set. Access tier (A S) is protocol data transmitted by the upper layer via the PC5 interface. The unit's PPPP is provided. Each logical channel is associated with PPPP. Similarly, PPPR is not configured. AS is connected to the PC5 interface by the upper layer. ProSe Direct The wireless resources used for communication are QoS inputs and wireless resources provided by the higher layer. Based on line resource configuration information, the UE AS autonomously selects when outside of coverage. It is possible to report QoS inputs and higher-level QoS inputs and higher-level QoS inputs to the eNB by the UE. Considering the resource settings of the ear, for example, when it is within coverage or outside of coverage Sometimes, scheduling can be done by eNB. The TX profile is V2 X sidelink transmission, Release 14 PHY format or Release 15 PH Used to determine which Y format (e.g., 64QAM) to use. ru.

[0100] (NR V2X Use Case) SA1 enables vehicle platooning, extended sensors, advanced driving, and remote operation, as follows: We have identified two main advanced V2X use case groups[1][2]. • Vehicle platooning allows vehicles to form groups that travel together dynamically. All vehicles in the convoy receive data periodically from the lead vehicle in order to perform convoy maneuvers. This information allows the distance between vehicles to be made very small, that is, in time. The gap distance to be converted can be made very small (sub-seconds). Platooning application This allows following vehicles to operate autonomously. • The expanded sensors are for vehicles, RSUs, pedestrian devices, and V2X application services. Between local sensors or live video data, raw data or It enables the exchange of processed data. Vehicles can move beyond the range that their sensors can detect. This will increase awareness of those environments and allow for a more holistic understanding of the local situation. High data rate is one of the important characteristics. • Advanced driving enables semi-automated or fully automated driving. Larger following distances are anticipated. Each vehicle and / or RSU will use data acquired from its local sensors in proximity to By sharing with other vehicles, it allows the vehicles to adjust their trajectory or operation. Each vehicle then shares its driving intentions with nearby vehicles. The advantages include safer driving, collision avoidance, and improved traffic efficiency. • Remote driving allows passengers who are unable to drive themselves, or remote vehicles in dangerous environments. This allows remote drivers or V2X applications to operate public transportation. In cases where changes are limited and paths are predictable, cloud computing-based operations A rotary method can be used. High reliability and low latency are the main requirements. As shown in Figure 5, the requirements for NR V2X are far more diverse than those for LTE V2X. strict.

[0101] As mentioned earlier, from the perspective of AS, ProSe sidelink unicast and group Broadcast transmission is connectionless. Furthermore, LTE V2X is groupcast. It only supports stream transmission, and this is also connectionless. NR V2X requirements Considering that the requirements for LTE V2X are far more diverse and stringent, AS connectivity Contourless transmission presents many challenges, given the diverse and stringent requirements of NR V2X. For example, requirements for higher data rates, higher reliability, and lower latency. From the perspective of supporting unicast, it may not be appropriate. Below, unicast And using AS connectionless transmission for groupcasts to meet NR V2X requirements Several examples of the challenges to be addressed are shown. Throughout this disclosure, group cast Note that multicast is used interchangeably. 1. Higher protocol overhead. In AS connectionless transmission, the received V2 X packets to the correct upper-layer service access point (Service Access Point) of the RX UE. Not only can it be delivered to ess Point (SAP), but the SL RX UE is different To distinguish between SL, TX, and UE, each V2X packet includes a destination ID and a source ID. It must be transported. Furthermore, AS connections that multiplex traffic at the MAC layer In actionless transmission, the logical channel is unique within the context of the destination and source pair. To identify each MAC PDU being sent, each MAC PDU must have an L2 destination ID and a source L2 ID. It needs to be transported. For ProSe side links and V2X side links, over - To limit the number of heads, each MAC PDU has a source ID and destination ID at the upper layer. D carries the L2 source ID and L2 destination ID mapped to each other, but this Despite the rapping, each V2X packet transmission still requires an L2 source ID and This causes overhead in the L2 destination ID. Such protocol overhead Acceptable in the context of LTE V2X transmission using relatively low data rate transmissions. It was possible, but in the context of NR V2X, such overhead was There is a risk of it becoming excessive. 2. Higher processing overhead. Each sidelink packet has an L2 source ID and L2 The fact that it retains the destination ID also means more packet filtering at L2. This also implies processing overhead. For example, in LTE V2X, RX PHY ray Ya is all successfully decoded V2X packets received on the configured RX resource pool. The RX L2 then receives the V2X packet, which contains a 24-bit L2 destination ID and 2 Because it is filtered at L2 using a 4-bit L2 source ID, this RX U Only V2X packets of type E are passed to the V2X upper layer. Similarly, ProSe sidelining In this case, the PHY layer decodes all packets received by the configured RX resource. It must be partially filtered based on the 8 LSB bits of the SCI's L2 destination ID. It performs filtering, then passes the partially filtered packets to L2, and then at L2... Based on the 16MSB bits of the L2 destination ID and the 24-bit length of the source L2 ID, the file This process involves retarding. This type of processing overhead is avoided when using relatively low data rate transmissions. While acceptable in the context of LTE V2X transmission, NR V2X In this context, such processing overhead may be excessive. 3. Enabling physical layer feedback is difficult. With AS connectionless transmission. L2 feedback is not supported. In other words, conventional LTE ProSe Alternatively, in conventional V2X sidelink communication, there is no support for RLC feedback. There is no support for HARQ feedback. Individual fees from RX UE to TX UE. C-RNTI or a communication context specific to a particular UE to support the transmission of backs There is no UE-specific identification information (source or destination) in the PHY layer, such as in the case of a strike, and this is because the connection Implementing this without sequential directional transmission is extremely complex. 4. It is difficult to enable link management to meet QoS requirements. AS connections Response transmission includes wireless link monitoring and wireless link recovery, beam management, and link adapter. Power control and rate control, as well as channel-dependent settings Enabling UE-specific wireless link management features, such as scheduling, is not practical. Or, it is impossible. In the case of ProSe sidelink or V2X sidelink, The lack of these features was acceptable, but it came with higher reliability and lower latency. The diverse and demanding requirements of NR V2X, such as higher data rates, necessitate more efficient wireless communication. Source control is required. Furthermore, connection-based SLs provide QoS flow-based per SL QoS control becomes easily achievable, thus providing a foundation for integrated QoS processing in SL and Uu. It will be provided. 5. Differentiated configurations of RX UE are not supported. For example, in AS connectionless transmission, Based on the capabilities of the RX UE, configure the RX UE with a specific AS configuration. This is not possible. Therefore, all ProSe sidelink functionality for a given release is not available. Alternatively, the LTE V2X sidelink functionality is required for all RX UE releases. The requirements for NR V2X are diverse, and all NR V2 aircraft of any given release Making this capability a requirement for all NR V2X UEs in that release is not practical. AS layer connectivity-based SL transmission allows for more flexible SL radio protocol configuration. It is possible.

[0102] Considering the above drawbacks of AS connectionless transmission in the context of NR V2X communication With consideration, NR V2X unicast and NR V2X groupcast are also handled similarly, AS Support for connection-oriented transmission is desired.

[0103] (Issues related to connection-oriented unicast transmission) To support AS connection-oriented unicast transmission, the following issues must be addressed. There is a need. 1. Overall procedure for establishing, changing / reconfiguring, and disconnecting unicast connections. 2. Authorization and provisioning of UEs to support connectivity-oriented unicast transmissions. (In-coverage and out-of-coverage) 3. The UE shares with the gNB to support the establishment, modification, or termination of unicast connections. V2X provisioning information (UE support information). 4. Triggers for unicast connection reconfiguration, disconnection, and relocation. 5. SL AS protocol configuration including the following a. Flow-based QoS vs. packet-based QoS, Mode 1 vs. Mode 2 One or more of the following assignments are expected: MAC, RLC (for example, UM vs. AM) (Settings), PDCP, SDAP, Wireless Resource / Wireless Bearer, PHY Settings (e.g., Feed) HARQ, CSI including HARQ TX with feedback vs. HARQ TX without feedback Settings (etc.) b. For example, what is necessary to exchange between UEs via SL unicast sidelinks UE ID, UE capability, wireless / bearer settings, PHY information / settings (e.g., HARQ, C AS-level information such as SI, resource information / configurations, and QoS information. c. Extension of Uu to support SL connection management and QoS, and SL Uniqlo AS level information required to be exchanged between UE and gNB for AS communication. d. How to support unicast between UEs via sidelinks Specify whether to exchange S-level information, or to specify the details of the signaling between RRC and PC5. 6. Reception control, how this is done, and which entity performs reception control. mosquito 7. Configuring UE identification between TX UE and RX UE to support unicast transmission. and collaboration. For example, in an LTE ProSe sidelink unicast design, UE This means that the Layer 2 ID for unicast communication is at least locally unique. This needs to be ensured. Therefore, the UE uses an unspecified mechanism to ensure proximity You should be prepared to handle Layer 2 ID conflicts with the UE (for example, if the conflict is detected (When issued, it self-assigns a new Layer 2 ID for unicast communication.) How to ensure the uniqueness of L2 IDs for unicast connection-oriented communication is This is a problem that needs to be addressed. 8.1 A discovery procedure is used to identify a specific UE in order to initiate one-to-one communication. It is expected that the upper layers above the access layer will handle QoS-related information and communications. Whether it should be unicast, groupcast, or broadcast depends on the access layer. This can be shown, but unicast communication can be performed without a connection or in a connection-oriented manner. When deciding whether or not this should be done, access layer-specific rules and criteria need to be designed. There is a possibility that... To support the decision to establish, disconnect, or relocate unicast connections in Rabin We need to address the issue of how to use the discovery output.

[0104] (Issues related to connection-oriented groupcast transmissions) Similarly, as explained in the section titled "Issues related to connection-oriented unicast transmission" above. The identified issues need to be addressed in relation to connection-oriented groupcast transmissions. In terms of practical application, to support AS connection-oriented group cast transmission, the following questions arise: We need to address the issue. 1. Overall procedure for establishing, changing / reconfiguring, and disconnecting groupcast connections. 2. UE authorization and provisioning to support connection-oriented groupcast transmission (In-coverage and out-of-coverage) 3. The UE shares with the gNB to support the establishment, modification, or termination of unicast connections. V2X provisioning information (UE support information). 4. For example, to establish a groupcast connection between a group member and a group lead. Triggers include groupcast connection reset, disconnection, and another group lead. Reconfiguration of connections by group members. 5. SL AS protocol configuration including the following a. Flow-based QoS vs. packet-based QoS, Mode 1 vs. Mode 2 One or more of the following assignments are expected: MAC, RLC (for example, UM vs. AM) (Settings), PDCP, SDAP, Wireless Resource / Wireless Bearer, PHY Settings (e.g., Feed) HARQ, CSI including HARQ TX with feedback vs. HARQ TX without feedback Settings such as (etc.). b. Examples of what is needed to exchange between UEs via SL groupcast sidelinks. For example, UE ID, UE capabilities, wireless / bearer settings, PHY information / settings (e.g., HARQ AS-level information such as CSI, resource information / configurations, and QoS information. c. Extension of Uu to support SL connection management and QoS, and SL group AS level information required to be exchanged between UE and gNB for precast communication d. How to support unicast between UEs via sidelinks Specify whether to exchange S-level information, or to specify the details of the signaling between RRC and PC5. 6. Reception control, how this is done, and which entity performs reception control. mosquito. 7. UE identification between TX UE and RX UE to support groupcast transmission. Configuration and integration. RX UE is involved in receiving two or more groupcast communications. This is possible. Similarly, a TX UE can be involved in sending two or more groupcast communications. This is possible. The Layer 2 ID for groupcast communication is at least locally unique. It is necessary to ensure that this is the case. L2 ID for connection-oriented groupcast communication Ensuring the uniqueness of the data is a problem that needs to be addressed. 8. The discovery procedure initiates one-to-many communication between a specific UE or a group of UEs. It is expected to be used to identify the access layer. The upper layer above the access layer is QoS-related information, and whether communications are unicast, groupcast, or broadcast. It is possible to indicate to the access layer whether it should be connected, but groupcast communication connects When deciding whether to implement it in a connectionless or connection-oriented way, access It may be necessary to design specific rules and criteria for each layer. Furthermore, discovery Interaction between groupcast connection management and groupcast connection establishment. How to use the discovery output to support the decision to disconnect or reconnect The question of how to use it needs to be addressed. One related question is, V2 X group management can be done at the V2X upper layer only, or the AS layer only, or both layers. How is it executed, and if so, what is the relationship between the AS group and the V2X upper layer group? What is it? For example, in a situation where the UE members of a higher layer group are spread across a wide area. In total, it is probably possible to cover all UE members with a single AS layer group. In addition, in order to enable normal communication between all UEs in the upper layer UE group, multiple A An S-layer group is required. For each AS group, one or more member UEs are needed. ) is responsible for establishing and maintaining connections between AS group leaders and AS layer groups. This is possible. If a member UE(s) moves, the original AS layer group or The connection is terminated and reconnected to another AS group. AS group cast connection confirmed. For setup and maintenance, as well as mapping to sessions / connections in higher layers, The procedures, configurations, and interactions between the earpiece and the AS layer need to be designed and specified.

[0105] (Summary of proposed solutions) In this disclosure, we propose the following solutions to support unicast connection management. . 1. A Layer 2 protocol structure including the following: • Have one SDAP entity per V2X destination, and reflective Qo on sidelinks Since support for S features is not required, only the QoS flow ID in the SDAP protocol header is used. A new proposal: to possess. • MAC SDUs that are subject to connection-oriented transmission are M It is multiplexed separately from AC SDU. MAC PDUs targeted for connection-oriented transmission do not carry source ID or destination ID. • Sidelink multicast control channel and sidelink multicast transformer Port channel support. 2. Provisioning of V2X transmitter and receiver 3. Triggering V2X transmission or V2X reception 4. The sender and receiver must identify which entities perform the selection and on what criteria. Selection of side RAT and interface, 5. Selection of transmission mode for the transmitter and receiver, and the criteria for selection. 6. Unicast connection including a description of support parameters from the UE (e.g., the capabilities of the receiving end). Detailed management procedures, and scheduling entities or scheduling entities Unicast setting parameters set in the UE by a support UE working in conjunction with T. 7. Describe alternative connection management procedures, including the following options: • Using PC5 RRC signaling, V2X upper layer connection settings and AS ray It simultaneously carries connection settings. T-UE is a scheduling entity or IU This is configured by I-UE in conjunction with E. See Figure 16. • Using PC5-S signaling, configure V2X upper layer connections and AS layer connections. The T-UE simultaneously transports the subsequent settings. The T-UE is a scheduling entity or I-UE. This is configured by the integrated I-UE. See Figure 17. • V2 to support AS layer connectivity using PC5 RRC signaling It simultaneously transmits X upper layer configuration information and AS layer connection settings. T-UE is a schedule It is configured by a Jurling entity or an I-UE in conjunction with another I-UE. Furthermore, the V2X upper-layer connection settings use PC5-S signaling independently of the AS connection settings. It is then executed. See Figure 18. • V2X to support AS layer connectivity using PC5-S signaling It simultaneously transmits position layer configuration information and AS layer connection settings. I-UE is scheduled It is configured by a TUE in conjunction with a ring entity or IUE. Furthermore, V2X upper-layer connection settings are configured independently of AS connection settings using PC5-S signaling. It will be executed. See Figure 19. • Using PC5-S signaling, configure V2X upper layer connections and AS layer connections. It transports the subsequent settings simultaneously. I-UE is a scheduling entity, or schedule This is configured by a T-UE in conjunction with a ring entity. See Figure 20. • Using PC5 RRC signaling, V2X upper layer connection settings and AS ray It simultaneously carries connection settings. I-UE is a scheduling entity, or schedule This is configured by a T-UE in conjunction with a juring entity. See Figure 21. 8. Group connection settings and V2X upper layer group mapping to AS layer subgroups PING ideas, maintenance of mapping tables in AS, and AS to PHY One or more of the following instructions: • Group Layer 2 Destination ID. • Group member's V2X UE ID (e.g., ProSe UE ID, UE ID) D, or any other ID that can be used by the UE as the source ID of a member UE. A list of identifiers. • Subgroup Layer 2 destination ID. • V2X UE ID of subgroup members (e.g., ProSe UE ID, U Other IDs, or other IDs that can be used by a UE as the source ID of a member UE. A list of identifiers. • For each subgroup, relay the data received for that subgroup. An instruction to request that the relay not be relayed. 9. Broadcast Configuration and Various Broadcast Signaling Options . 10. Method for UE processing of multiple simultaneous sidelink RRC connections. 11. PC5 Unicast Link Granularity Modeling, Unicast Link Update, and Instructions for adding a Nicast link

[0106] (UE operation before V2X communication) (Layer 2 protocol structure) The Layer 2 side link structure of the NR V2X is shown in Figures 6, 7, 8, and 9.

[0107] Figure 6 shows the Service Data Adaptation Protocol (S Provides a description of the DAP sublayer. One SDAP entity per V2X destination. It has been proposed that it exist. In one embodiment, the V2X destination is the peer V2X UE destination. This can be done. In such an embodiment, the UE can simultaneously interact with n peer V2X UEs. If V2X communication is available, the UE then has n SDAPs, one for each peer V2X destination UE. Maintain entities. Each SDAP entity has a specific bare Maintain the set of UEs. Multiple connections between the UE (in this case, the source UE) and the peer V2X destination UE. Because there may be a number of simultaneous V2X services, those services are mapped The L2 destination IDs and the wireless bearers associated with those services are identified. It is mapped to the same SDAP entity associated with the peer V2X destination UE. A V2X packet associated with a given peer V2X destination UE is of the transmit cast type ( Regardless of whether it is a unicast, groupcast, or broadcast, support is available. The bearer or destination Layer 2 ID is mapped to the SDAP entity. It will be broadcast or groupcast, if the peer V2X destination UE is A Even if not explicitly known to S, the corresponding bearer and associated Layer 2 destination ID are, It can be mapped to any SDAP entity, or, instead, blow One or more SDAP entities dedicated to supporting doccast communication, or One or more SDAP entities to support groupcast communication, or One or more S to support both groupcast and broadcast communication DAP entities can exist.

[0108] In another embodiment, the UE has a group that is (pre-configured) or provisioned. A service can be placed. In this embodiment, the V2X destination in Figure 6 is a V2X service. It means one group of screws.

[0109] In an alternative embodiment, one SDAP per UE for V2X sidelink communication An entity may exist. In such cases, the identification information of the V2X communication bearer is It may need to be unique within the UE.

[0110] Figure 7 shows Layer 2 for supporting V2X communication in AS broadcasting configuration. Structure, and transport sidelink broadcast channel (Sidelink Broa Sidelink broadcast control channel (SB) to dcast Channel:SL-BCH This shows the mapping of the transport sidelink shared channel (CCH). Sidelink traffic logical channel on ared Channel (SL-SCH) Traffic Logical Channel (STCH) multiplexing is performed with each MAC PDU being the source ID. and the destination ID, and the logical channel to support MAC multiplexing for this It is assumed that identification is unique. Multiplexing with logical STCH on SL-SCH. Introducing a Sidelink Control Channel (SCCH) that enables this. It has also been proposed that logical channels such as SCCH can be mapped. Sidelink Signaling Radio Bearer (SL- It has also been proposed to introduce SL-SRB. SL-SRB is used for connection management (for example, connection management). Signaling of re-establishment, reconnection, or disconnection, or sidelink measurement values It can be used for configuration and reporting.

[0111] Figure 8 shows a Layer 2 configuration for supporting V2X communication with an AS unicast connection orientation. The structure indicates that the peer V2X receiver side, for example, has a dedicated unit that takes into account the capabilities of the peer V2X UE. This is configured in the Cast V2X settings. In this case, the sidelink traffic logical channel Multiplexing of the transport sidelink shared channel (SL-SCH) on (STCH) is Each MAC PDU includes a source ID and a destination ID, and MAC multiplexing is performed on these. It is not assumed that the identification of the logical channel for porting is unique. Multiplexing in STCH is configured when another instance of SL-SCH is established, V HARQ dedicated to transmitting 2X unicast traffic or SL-RRC signaling. It is assumed that the entity is connected in an AS connection-oriented manner. When the connection is established, A MAC Service Access Point (SAP) is created for each instance of SL-SCH. The PHY is then communicated to, where the PHY is the Instagram of the SL-SCH indicated by the MAC. PHY channels associated with a link (e.g., physical sidelink shared channels (Phys Create the corresponding instance of ical Sidelink Shared Channel (PSSCH), And maintain. As part of the connection context, each V2X service included in the connection context For service or data radio bearers, to Layer 2 mapped to V2X services. The previous ID is associated with and maintained for the logical channel and the corresponding wireless bearer. In the formula, to support the multiplexing of the PHY layer for traffic to the shared channel, For each of the two V2X UEs involved, the Physical Layer: PHY) Unique identifier, for example, to identify both V2X UEs for connection-oriented receiving purposes. Assign the PC5 sidelink RNTI to each of the peer UEs, and both peer UEs It can be set to this. Alternatively, each peer UE can autonomously identify its own PHY. Children can be derived and exchanged with each other as part of the connection configuration. TX UE is peer R The PHY identifier of the X V2X UE is used to identify the peer V2X UE to which the data is destined. To separate. For example, the TX UE identifies the transmitted data as PHY-identified by the peer RX V2X UE. Separately, it can be scrambled or masked. RX UE is used by the transmitter. The PHY identifier used is then used to identify the RX UE of the data. Once decrypted, RX UE is based on the association created when the connection between PHY and MAC SAP is established. Therefore, it is in a position to correctly route incoming data to the correct MAC SAP. There is no layer multiplexing; for example, traffic from a peer V2X UE to the UE (in advance) ) Alternative options carried by dedicated PHY resources that are configured or provisioned. Therefore, a PHY identifier that uniquely identifies the peer UE involved in the connection may not be necessary. In this case, the RX UE, based on the PHY resource that received the V2X packet, determines the peer V2 Identify the correct routing SAP within the X-transmitting UE and MAC. AS uses peer V2X. The UE source ID (for example, in the case of a unicast), or in the case of a groupcast. This is the destination Layer 2 ID of the peer V2X UE (for example, the ProSe Layer 2 group ID). Provide the PHY with something like this (or a ProSe application layer group ID). It is possible. The PHY uses such an ID to send to the peer V2X which is the destination of the transmission. The RNTI used to identify the UE can be derived. Furthermore, the connection settings As part of this, it is mapped to a side-link signaling radio bearer (SL-SRB). The logic channel that carries control information (e.g., SCCH) is a sidelink data wireless carrier. Sidelink mapped to Sidelink Data Radio Bearer (SL-DRB) Logical channels (STCHs) that carry traffic, and configured for connection-oriented reception. It can be multiplexed on the SL-SCH transport channel. Therefore, for setting and controlling unicast traffic, the side link control channel It has been proposed to introduce a logical SL control channel represented as (SCCH). SCCH can be associated with SL-SRB. SBCCH is mapped to S L-SRB can be represented as SL-SRB0. SCCH is mapped, blow SL-SRB transmitted using the docast method (AS connectionless) is SL-SRB It can be represented as 1. SCCH is mapped and SL- is sent in a connection-oriented manner. SRB can be represented as SL-SRB2.

[0112] Figure 9 shows the layer for supporting V2X communication in AS groupcast connection-oriented configuration. The two structures are shown, and the peer V2X receiver side has a dedicated g, for example, that takes into account the capabilities of the peer V2X UE. This is configured in the Loopcast V2X settings. In this case, the sidelink traffic logic Transport sidelink shared channel (S) on channel (e.g., SL-MTCH) L-MCH) multiplexing means that each MAC PDU contains a source ID and a destination ID, and In contrast, assuming that the identification of logical channels to support MAC multiplexing is unique No. Instead, multiplexing in SL-MCH is another instance of SL-MCH. This is set when the connection is established, and V2X groupcast traffic or SL-RRC signature It is assumed that the HARQ entity is connected in an AS connectivity-oriented manner to a dedicated HARQ entity for transmitting naring. It does so. When the connection is established, the MAC service access point of each instance of SL-MCH A statement (SAP) is created and communicated to the PHY, where the PHY is indicated by the MAC. The PHY channel associated with the SL-MCH instance (for example, the physical side Support for Link Sharing Channels (Physical Sidelink Shared Channel: PSMCH) Create and maintain an instance of the connection as part of the connection context. For each V2X service or data radio bearer included in the KIST, the V2X service The mapped Layer 2 destination ID is associated with the logical channel and the corresponding radio bearer. It is maintained by being blocked. In this method, the PHY of traffic to multicast channels To support ear multiplexing, the TX V2X UE and RX group involved in the connection For each member UE, a unique physical layer (PHY) identifier, e.g., TX PC5 sidelink RNTI for identifying V2X UE, and for connection-oriented receiving purposes A physical layer unique identifier is used to identify RX group member UEs, which are part of the group. It can be assigned to each of the UEs and set as a UE. Alternatively, the peer UEs Each device autonomously derives its own PHY identifier and exchanges it with the others as part of the connection configuration. This is possible. The TX UE uses the PHY group identifier of the peer RX V2X UE. Then, identify the peer V2X group member UE that will be the destination of the data. For example, TX UE This is the PHY identifier of the peer RX V2X group member UE, which scrambles the transmitted data. Alternatively, it can be masked. RX UE is the PHY used by the sender. The loop identifier is used to identify the RX UE of the data. Once decrypted, the RX UE is Based on the association created when the connection between PHY and MAC SAP was established, the received data We are in a position to correctly route the data to the correct MAC SAP. There is no multiplexing of the PHY layer in Raffic, for example, groupcast traffic U The signal sent to E is sent using a dedicated PHY resource that has been (pre-configured or provisioned) In the alternative option, a PHY group identifier that uniquely identifies the peer UE involved in the connection is required. It may not be necessary. In this case, the RX member UE receives the groupcast traffic. Based on the PHY resources, the correct groupcast traffic and MAC address are determined. Identify the sending SAP. The AS is not only the UE's own source ID, but also the peer V2X UE source ID (for example, to support unicast), or for example, group In the case of broadcast communication, the destination Layer 2 ID of the peer V2X UE (for example, Pro Se Layer 2 Group ID, or ProSe Application Layer Group The ID can be provided to the PHY. The PHY uses such an ID to send It is possible to derive the RNTI used to identify the peer V2X UE that will be the destination. It can be done. Furthermore, as part of the connection settings, a sidelink signaling wireless bearer (SL-S Logical channel that carries sidelink multicast control information mapped to RB) (For example, SL-MCCH) matches the sidelink data radio bearer (SL-DRB). Logical channel (SL-) that carries pinged sidelink multicast traffic. MTCH) and SL-MCH transport channels configured for connection-oriented reception. Multiplexing is possible above. For group casts, group cast traffic For setting up and controlling the Sidelink multicast control channel, Logical side link control, represented as Multicast Control Channel (SL-MCCH). A channel can be introduced. MCCH can be associated with SL-SRB. The SL-SRB to which SBCCH is mapped can be represented as SL-SRB0. The MCCH is mapped and transmitted using the broadcast method (AS connectionless). The SL-SRB can be represented as SL-SRB1. MCCH is mapped, SL-SRB transmitted in a connection-oriented manner can be represented as SL-SRB2.

[0113] Figure 10 provides a functional diagram of the SDAP sublayer. Reflective QoS is V2X sidelink. It has been suggested that it will not be supported in the link. Therefore, as shown in Figure 11, SD It is proposed to simplify the AP header and make the header the same for both downlink and uplink. The QoS Flow Identifier (QFI) is 6 bits or less. On the other hand, the remaining bits of the header can be reserved bits, or the data It can be used for transport, thereby enabling QoS flow via V2X sidelink. This minimizes the overhead of support required for this purpose.

[0114] (Transmitter's operation) AS broadcast, AS unicast, or AS groupcast An example of UE operation, including intermediate procedures within the UE leading to the decision on V2X communication, and high-level transmission on the transmitting side. A description of the bell is provided in Figure 12. In step S1200, the UE performs V2X operation, that is, the UE performs V2X communication A discovery procedure to discover other devices, and the UE performing on the V2X device. V2X communication with other V2X devices in response to requests from V2X applications. To support X communication, it must be pre-configured (on the SIM or ME), or Provisioning is performed by V2X control functions located in the core network that possesses information. It is either done or done. UE and V for provisioning V2X operating parameters Communication between 2X control functions is possible via the user plane or via the control plane. This applies to NR V2X operation, and especially unicast or groupcast communication. For provisioning parameters to support this, see "Sender V2X Pass" below. This is explained in the section titled "Provisioning Trust". Step S1202 V When 2X communication is triggered, the UE, if not yet synchronized in step S1204, Synchronization can be performed. The UE can also be instructed by the communication trigger conditions. Next, perform discovery to identify a group of peer UEs or UEs that can communicate. For example, an application at the application layer can be used with V2X upper layers. This triggers the discovery of a peer UE or group of UEs if they have not yet been found, and V2X communication can be initiated towards a UE or group of UEs such as this. Output from the coverage procedure, e.g., Layer 2 links to the discovered UE or group of UEs. The ID (singular or plural) is used to establish a connection to a specific UE or group of UEs, or subsequent steps in V2X operation, such as setting up broadcast resources for V2X transmission ( It can be used by UE (singular or plural). Steps S1206 and S1 In 208, the UE selects the RAT and interface (e.g., sidelink vs U). The u interface) selection is performed. Steps S1206 and S1208 are separate. Although described as a separate step, "Sender RAT selection and interface selection" As explained below in the section titled, the two steps are performed simultaneously. This is possible. In step S1210, whether the SL interface is selected or not. The question is answered. If yes, the SL transmission mode is determined (step S). 1212). If the SL transmission mode is broadcast mode, in step S1218, AS settings for loadcast transmission are performed. SL transmission mode is set to unicast mode. In this case, step S1214 performs Layer 2 link configuration for unicast transmission. If the SL transmission mode is multicast mode, in step S1216, the multicast Layer 2 link configuration for receiving signals is performed. In step S1210, SL If no interface is selected, transmission will begin via the Uu interface. Step S1220).

[0115] (Provisioning of V2X communication on the transmitting side) Unicast transmission, groupcast transmission, broadcast transmission, or flow To support QoS, NR V2X UE uses the following system parameters: It can be pre-configured or provisioned. Configuration can be, for example, NR sidelining. QR interface, NR UU interface, LTE side link interface, L TE Uu interface, WLAN sidelink interface, or from WLAN This is possible on an interface-by-interface basis, such as the interface to the network. • A list of authorized V2X services, and for each service, the transmission mode (transmission key). Cast type), i.e., whether the service is broadcast-based transmission or group Whether it is a cast-based transmission or a unicast-based transmission, The transmission mode of the BIS is PLMN or PLMN group-based, or cell-based. This is based on cell groups, or geographical areas or geographical area groups. It can be defined as follows. • A list of authorized V2X services, and for each service, the transmission of V2X services. Is it ear connection-less, or is it V2X upper layer connection oriented? For example, broad While cast transmissions can be made connectionless, unicast transmissions can also be made connectionless. Can groupcast transmissions be connected-oriented transmissions, or are they V2X upper layers? Connectionless transmission is possible. • A list of authorized V2X services, and for each service, the transmission of AS Layer Code Is it connectionless, or is it V2X AS layer-oriented? For example, broadcast While stream transmission can be made connectionless transmission, unicast transmission or Can groupcast transmissions be made connection-oriented transmissions, or can connections at the AS layer It can be transmitted without a compression. • Other UE schedulers or scheduling entities, or local controllers Authorization to function as a troller or scheduler node. Such authorization is P LMN-based or PLMN group-based, cell-based, cell group-based Defined by a specific area, or on a geographical area basis or a geographical area group basis. This disclosure allows for the use of a local controller, scheduling entity, or The term "scheduler entity" is used interchangeably. For example, a column lead is It can be provisioned using authorization, which functions as a scheduling entity. Authorizations like these can also be defined on a service-based or service-group-based basis. can. • Authorization that acts as a support UE for scheduling entities. Such authorizations are, PLMN-based or PLMN group-based, cell-based or cell group Defined on a map basis, or on a geographical area basis or on a geographical area group basis. It is possible. • Duplicate authorization across wireless interfaces, i.e., authorization for two or more wireless interfaces Transmitting the same data across, for example, two or more of the following wireless interfaces: N R side link interface, NR Uu interface, LTE side link interface Face, LTE Uu interface, WLAN sidelink interface, or WLAN to network interface. Such duplication is a reliability requirement, for example. In the case of a packet-based QoS model, the reliability value for each ProSe packet, Alternatively, in the case of QoS flow or bearer-based QoS models, the packet error rate is also... This can be defined based on the QoS identifier value. Such authorization is service-based. This can be defined for each cell. Furthermore, such authorization can be defined for each cell or group of cells. By group, or by geographical area or group of geographical areas, or PL It can be defined for each MN or PLMN group base. V2X context In the context of the system, the QoS identifier is a V2X QoS Identifier (VQI). This is how it is expressed. • A list of V2X QoS identifiers. For each VQI, the corresponding QoS profile The parameters can be set. QoS profiles are priority levels (i.e., S Scheduling priority level, payload, transmit speed, maximum end-to-end delay, signal Reliability, data rate, minimum required communication range, preemption priority level (i.e., It may include one or more of the following (with preemption priority levels). The QoS profile is a priority level (i.e., scheduling priority level). Resource type (e.g., GBR, delayed critical GBR, or non-GBR), packet Of the following: delay budget, packet error rate, averaging window, and maximum data burst amount It can contain one or more. This setting is PLMN-based or PLMN group-based. For each cell or group of cells, based on geographical area or geographical region. This can be defined for each group base of A. • A list of QoS flow identifiers (QFIs). For each QFI, the relationship between the QFI and the VQI. Mapping. QoS flow is the finest granularity of QoS differentiation. This setting is PL For each MN-based or PLMN group-based, by cell or group-based of cells This can be defined on a geographical area basis or on a geographical area group basis. . • Connection-oriented transmission, and lithography for signaling to support these connections. -Spool settings. • PC5 signaling or SL to support connection establishment and maintenance of that connection. Resource pool configuration for RRC signaling. Such resource pools are connected It can also be used as a shared resource pool for actionless PC5 data transmission. .

[0116] Each of the provisioning parameters defined above is used by the UE to determine the wireless access network. Supplied by twerks or by wireless access networks It can be defined based on whether or not it is present. Furthermore, wireless access network If not provided, is the carrier frequency for V2X communication operator-controlled? Set provisioning parameters based on whether it is operator-managed or not. It is possible.

[0117] UE can also pre-set the following capability parameters (for example, SIM or (This refers to mobile devices (ME)). • Support for AS-based unicast transmissions • Support for AS-based groupcast transmissions • Support for V2X UpL-based unicast transmissions • Support for V2X UpL-based groupcast transmissions • Support for AS connectionless transmission • Support for AS connection-oriented transmission • Support for packet duplication across wireless interfaces • Support for the ability to function as a scheduling entity. • Support for the ability to function as a support UE for scheduling entities. • Support for QoS flow-based QoS models, e.g., V2X upper layer to V2X QoS requests for packets forwarded to the AS are indicated using QoS flows. Features that support Dell. • Support for per-packet QoS modes, e.g., V2X upper layer to V2X AS Each packet forwarded carries its QoS request, such as PPPP or PPPR. A feature that supports QoS models.

[0118] (Transmitter trigger for V2X communication) In the context of the high-level explanation of V2X operation described in Figure 12, the following events One or more of the signals can trigger a V2X communication procedure, including the connection establishment procedure in the UE. can. • Sending V2X packets for transmission by a V2X application. In this case, the procedure is It is triggered as a result of an event originating from the application layer. • Discovery is triggered by the application layer. • The communication quality of current / existing V2X communications no longer meets the quality threshold. , one or more QoS profile metrics (e.g., packet error rate, latency, reliability, This can relate to things like communication range. In this case, the V2X upper layer of the V2X UE is To continue the V2X communication initiated by the application layer, another UE is needed. Alternatively, you can initiate communication with the UE group. • Wireless link failure, or beam failure, or failure to recover from beam failure. In this case, V2X The AS's V2X upper layer handles V2X communication initiated by the application layer. To continue, you can initiate communication with another UE or group of UEs. • Wireless link quality no longer meets the quality threshold. • Congestion has exceeded the threshold. • The transmit power exceeds the threshold, or the path loss exceeds the threshold. • Mobility events, in this case, the V2X upper layer of V2X AS, application To continue the V2X communication initiated by the layer, another UE or UE group Communication can be initiated toward the target. Mobility events are UE's own mobility It can be related to, or it can be related to peer UE mobility. • For example, a scheduler that controls resource allocation from or to peer UEs. Received a disconnection notification from the entity. • Scheduling enterprise controls resource allocation from or to peer UEs. Received connection establishment request from the company. • Scheduling enterprise controls resource allocation from or to peer UEs. Received a handover request from the company. • Connection reset failure.

[0119] The V2X upper layer can trigger the V2X communication operation described in Figure 12. As shown, the V2X AS layer can trigger the V2X communication operation described in Figure 12. ru.

[0120] (Selection of transmitting RAT and interface) The V2X upper layer can perform RAT selection or interface selection. The V2X upper layer performs RAT selection and interface selection sequentially or simultaneously. It is possible. V2X AS is available for RAT or interface selection. Support information such as sexual information can be provided to the V2X upper layer. For example, RAT's A S can determine the availability of that RAT. Furthermore, AS can determine the availability of a particular RAT. The availability of the interface can be determined in conjunction with this. In an exemplary embodiment, RAT This is one of the following: NR RAT, LTE RAT, Wi-Fi, or WLAN RAT. The above is possible. Similarly, the interface is Sidelink NR RAT, Uu RAT, Sidelink LTE RAT, Uu LTE RAT, Sidelink Wi-Fi i, or WLAN RAT, and the wireless interface between the WLAN and the network It can be one or more of the following. AS is RAT or special based on one or more of the following. The availability of the interface associated with a specific RAT can be determined. • Communication quality threshold. The quality threshold is one or more QoS profile metrics (e.g., packet This can relate to factors such as error rate, latency, reliability, and communication range. • Wireless link quality threshold. • Congestion threshold. The congestion threshold is, for example, the Channel Busy Ratio (CBR). This can be related to and / or the Channel Occupancy Ratio (CR). Cut. • Wireless link failure, or beam failure, or failure to recover from beam failure. • Detection of areas outside of coverage or partial coverage. • Predicted transmit power threshold or path loss threshold. ·UE ability. Availability information may include one or more of the following: Available or unavailable. • Communication quality threshold • Wireless link quality threshold • Congestion threshold • Detection of out-of-coverage or partially out-of-coverage areas ·UE ability

[0121] (Selecting the transmitting communication mode) The V2X upper layer selects the transmission cast type, i.e., broadcast versus group Perform a transcast versus unicast and select the transcast type as V2X AS. It can be shown to the V2X upper layer, to the V2X AS layer, AS Ray It is possible to indicate the transmission cast type of each packet sent to Ya. The process involves the transmission of each packet to the V2X AS layer by the V2X upper layer. This can be considered an instruction for the IP. The V2X upper layer, for example, provides QoS per packet. In relation to the specifications, instructions for the send cast type per packet can be used. In the alternative embodiment, the V2X upper layer and AS layer are configured for each transmission cast type. You can specify the Service Access Point (SAP). For each example, Each sending cast type (i.e., unicast, groupcast or broadcast) Regarding the transmission, the AS layer has one or more transmission cast type features in the V2X upper layer. The standard SAP will be released. The V2X upper layer will send cast type according to the AS layer. Send a packet to SAP. AS receives the packet from SAP, which is sending the packet to AS. Derive the transmission cast type of the packet. The V2X AS layer determines the packet's transmission type from the upper layer. According to the send cast type associated with the SAP that is received, a specific V2X upper Sends packets received via Layer SAP.

[0122] The V2X upper layer establishes a connection to support a secure Layer 2 link and transmits The association between the source ID and the destination ID (including security associations) It is possible to create a context for the V2X upper layer for the connection. From a layer perspective, transmission can therefore be connection-oriented, in which case, The 2-link connection context is maintained by the V2X upper layer, or transmission is sent A connection that was created between the sender and recipient before the start of the transmission and does not have an associated context. It can be actionless. The V2X upper layer has a Layer 2 link connection. In this case, it can be shown as V2X AS. The AS layer creates an AS-level connection. Determine and transfer the context of such a connection to the connection context of the higher layer within the UE. They can be associated. The AS context of an AS connection includes connection-oriented AS protocols. This includes stack configuration and security associations between the source and destination. Yes, it's possible. Alternatively, the AS can create an AS-level connection for a specific V2X upper-layer connection. In some cases, this does not happen. In such cases, the transmission is from the upper-layer connectivity-oriented SAP to the AS. The transmitted upper-layer packets are, for example, broadcast transmissions at the AS layer level. It can be transmitted at the AS level in a connectionless manner via this method.

[0123] (V2X upper layer uses unicast vs groupcast vs broadcast transmission) (Mechanism for determining usage) The V2X upper layer determines the use of the transmit cast type based on one or more of the following: It is possible. Instructions from the application layer. • Communication quality threshold. The quality threshold is one or more QoS profile metrics (e.g., packet Error rate, latency, reliability, communication range, scheduling priority, preemption priority It can be related to degrees, etc. • Service type or traffic type, e.g., signaling vs. application data. • Service authorization settings. ·ability. • Destination ID, or the number of destination UEs. • Pre-configuration (e.g., ME, SIM), provisioning to UE via network, For example, this includes V2X control functions or configuration of UEs by scheduling entities. Hmm, configuration for the UE. The configuration includes mapping the service to the outcast type. It is possible. • Link quality

[0124] (AS upper layer uses unicast vs groupcast vs broadcast transmission) (Mechanisms that determine this) The V2X AS layer determines the use of the transmit cast type based on one or more of the following: It is possible. • Instructions from the V2X upper layer. • Communication quality threshold. The quality threshold is one or more QoS profile metrics (e.g., packet This can relate to factors such as error rate, latency, reliability, and communication range. • Service type or traffic type (e.g., signaling vs. application) data). • Service authorization settings. • Capabilities (e.g., UE capabilities, peer V2X UE capabilities, scheduling entity capabilities) (e.g., capabilities of the system, gNB, or network). • Destination ID, or the number of destination UEs. • Pre-configuration (e.g., ME, SIM), provisioning to UE via network, For example, this includes V2X control functions or configuration of UEs by scheduling entities. Hmm, configuration for the UE. The configuration includes mapping the service to the outcast type. It is possible. • Wireless link quality.

[0125] (The mechanism by which the V2X upper layer decides whether to use connection-oriented or connectionless The V2X upper layer performs connection-oriented transmission or connection based on one or more of the following: You can decide whether to use the reply sending function. Instructions from the application layer. • Communication quality threshold. The quality threshold is one or more QoS profile metrics (e.g., packet This can relate to factors such as error rate, latency, reliability, and communication range. • Service type or traffic type (e.g., signaling vs. application) data). • Service authorization settings. • Capabilities, e.g., UE capabilities, peer V2X UE capabilities, scheduling entities The capability of gNB or network. • Destination ID, or the number of destination UEs. • Pre-configuration (e.g., ME, SIM, etc.), provisioning to UE via the network For example, V2X control functions, or scheduling entities can be used to configure UEs. Configuration to the UE, including the mapping of services to the outcast type. It is possible. • Link quality • Security requirements (e.g., security thresholds). Security requirements include authentication, integrity, etc. , or it could be a requirement related to encryption.

[0126] Next, regarding how the AS layer decides whether to use connection-oriented versus connectionless... Let me explain. The V2X AS upper layer transmits cast based on one or more of the following: You can decide whether to use the program. • Instructions from the V2X upper layer. • Communication quality threshold. The quality threshold is one or more QoS profile metrics (e.g., packet This can relate to factors such as error rate, latency, reliability, and communication range. • Service type or traffic type (e.g., signaling vs. application) data). • Service authorization settings. • Capabilities (e.g., UE capabilities, peer V2X UE capabilities, scheduling entities) (e.g., capabilities of gNB or network). • Destination ID, or the number of destination UEs. • Pre-configuration (e.g., ME, SIM, etc.), provisioning to UE via the network (For example, V2X control function, or setting to UE by scheduling entity) ) configuration to UE. The configuration maps the service to the outcast type. It can include. • Wireless link quality. • Security requirements (e.g., security thresholds). Security requirements include integrity, and This can be a requirement related to encryption.

[0127] (Receiver operation) AS broadcast, AS unicast, or AS groupcast An example of UE operation, including intermediate procedures within the UE leading to the decision on V2X communication, and high-level receiver behavior. A description of the bell is provided in Figure 13.

[0128] In step S1300, the UE performs V2X operation, that is, the UE performs V2X communication Discovery procedures to discover other devices, and the UE communicating with other V2X devices. To support V2X communication by performing the following, (SIM or ME) It is determined by or by a V2X control function located in the core network that has the information. It is either provisioned or provisioned. Provisioning of V2X operating parameters Communication between the UE and the V2X control function for the control is via the user plane, or This is possible via the plane. NR V2X operation, and especially unicast communication or Provisioning parameters to support receiving groupcast communications This is explained below in the section titled "Provisioning Receiver V2X Communication" When V2X communication is triggered in step S1302, the UE in step S1304 If synchronization has not yet been performed, synchronization can be initiated. UE further enables V2X communication. To identify a group of peer UEs or UEs that can receive, use discovery. It can be executed. Output from the discovery procedure, e.g., discovered UE or U The Layer 2 link ID (singular or plural) of group E is used for receiving V2X communication. Monitoring, establishing connections to a specific UE or group of UEs, or V2X communication. Subsequent steps in V2X operation, such as setting up broadcast resources for receiving (single or (Multiple) can be used by UE. Steps S1306 and S1308 In this context, the UE selects the RAT and interface (e.g., sidelink vs. Uu interface) Perform face selection. Steps S1306 and S1308 are separate steps. It is listed as a top, but is titled "Receiver RAT Selection and Interface Selection" As explained in the following section, the two steps can be performed simultaneously. It is possible. In step S1310, it is determined whether the SL interface is selected. Determined. If yes, the SL receiving mode is determined (step S1312). ). If the SL receiving mode is broadcast mode, in step S1318, broadcast AS settings for cast reception are executed. (If SL reception mode is unicast mode) In step S1314, a Layer 2 link configuration for unicast reception is performed. If the receiving mode is multicast mode, in step S1316, groupcast receiving Layer 2 link configuration for communication is performed. In step S1310, SL interface If no face is selected, start the setup for receiving via the Uu interface. Do (step S1320).

[0129] (Provisioning of V2X communication on the receiving end) Unicast reception, groupcast reception, broadcast reception, connection-oriented reception, To support flow-based QoS, NR V2X UE uses the following system These can be pre-configured or provisioned using parameters. For example, the settings can be: NR sidelink interface, NR Uu interface, LTE sidelink interface Toughface, LTE Uu interface, WLAN sidelink interface, also This is based on the interface, such as the interface from the WLAN to the network. It is possible. • A list of authorized V2X services, and for each service, the receiving mode (receiving key). Cast type), i.e., whether the service is broadcast-based reception or group Whether it is cast-based reception or unicast-based reception, The receiving mode of the BIS is PLMN or PLMN group-based, or cell-based. This is based on cell groups, or geographical areas or geographical area groups. It can be defined as follows. • A list of authorized V2X services, and for each service, the V2X higher level of reception. Is it ear connection-less, or is it V2X upper layer connection oriented? For example, broad While it is possible to make cast reception connectionless, unicast reception also Can groupcast reception be connected-oriented reception, or is it a V2X upper layer? Connectionless reception is possible. • A list of authorized V2X services, and for each service, the receiving AS layer code. Is it connectionless, or is it V2X AS layer-oriented? For example, broadcast While stream reception can be made connectionless, unicast reception or Can groupcast reception be connected-oriented reception, or at the V2X AS layer? Connectionless transmission and reception can be enabled. • Other UE schedulers or scheduling entities, or local controllers Authorization to function as a troller or scheduler node. Such authorization is P LMN-based or PLMN group-based, cell-based, cell group-based Defined by a specific area, or on a geographical area basis or a geographical area group basis. This disclosure allows for the use of a local controller, scheduling entity, or The term "scheduler entity" is used interchangeably. For example, a column lead is It can be provisioned using authorization, which functions as a scheduling entity. Authorizations like these can also be defined on a service-based or service-group-based basis. can. • Authorization that acts as a support UE for scheduling entities. Such authorizations are, PLMN-based or PLMN group-based, cell-based or cell-glue Defined on a platform basis, or on a geographical area basis or on a geographical area group basis. It is possible. • Authorization of duplicate reception across wireless interfaces, i.e., two or more wireless interfaces Receiving the same data across multiple wireless interfaces, for example, two or more of the following wireless interfaces. NR sidelink interface, NR Uu interface, LTE sidelink interface Interface, LTE UU interface, WLAN sidelink interface, Or the interface from the WLAN to the network. Such duplication is a reliability requirement, for example. For example, in the case of a packet-based QoS model, the reliability value per ProSe packet. Or, in the case of a QoS flow or bearer-based QoS model, the packet error rate. Alternatively, it can be defined based on the QoS identifier value. Such authorization is a service Such authorizations can be defined for each space. Furthermore, such authorizations can be defined for each cell or for each cell. By group, or by geographical area or by group base of geographical areas, It can be defined for each PLMN or PLMN group base. In text, QoS identifiers are represented as V2X QoS identifiers (VQIs). • A list of V2X QoS identifiers. For each VQI, the corresponding QoS profile The parameters can be set. The QoS profile is a priority level, i.e., Scheduling priority level, payload, transmit speed, maximum end-to-end delay, reliability Sex, data rate, minimum required communication range, preemption priority level (i.e., acceptance) It can include one or more of the preemption priority levels. Another alternative is QoS profiles are priority levels (i.e., scheduling priority levels), Resource type (e.g., GBR, delayed critical GBR, or non-GBR), packet Among the packet delay budget, packet error rate, averaging window, and maximum data burst amount, This can include one or more of the following: This setting is PLMN-based or PLMN group For each base, on a cell or group of cell basis, on a geographical area basis or geographical area This can be defined for each rear group base. • A list of QoS flow identifiers (QFIs). For each QFI, the time between the QFI and the VQI. A setting exists. QoS flow is the finest granularity of QoS differentiation. This setting This is for each PLMN base or PLMN group base, for cells or groups of cells. Defined on a geographical area basis or on a geographical area group basis. It is possible. • For signaling to support connection-oriented reception and maintenance of these connections. Resource pool settings. • To support signaling reception for establishing and maintaining connections, PC Resource pool configuration for 5-signaling or SL RRC signaling. The resource pool is a shared resource also used for connectionless PC5 data transmission. It can be used as a swimming pool.

[0130] Each of the provisioning parameters defined above is used by the UE to determine the wireless access network. Supplied by twerks or by wireless access networks It can be defined based on whether or not it is present. Furthermore, wireless access network If not provided, is the carrier frequency for V2X communication operator-controlled? Based on whether it is operator-managed or not, provisioning parameters can be set. can.

[0131] UE can also pre-set the following capability parameters (for example, SIM or (This is on mobile devices (ME)). • Support for AS-based unicast reception. • Support for receiving AS-based groupcasts. • Support for V2X UpL-based unicast reception. • Support for receiving groupcasts based on V2X UpL. • Support for AS connectionless reception. • Support for AS connection-oriented reception. • Support for packet duplication reception across cross-wireless interfaces • Support for the ability to function as a scheduling entity. • Support for the ability to function as a support UE for scheduling entities. • Support for QoS flow-based QoS specifications, for example, the V2X AS layer receiving When delivering packets to the V2X upper layer, the QoS flow SAP from the wireless bearer The ability to support packet mapping and QoS models. • Support for per-packet QoS modes, e.g., from V2X AS to V2X upper layer. Each packet delivered carries its QoS request (e.g., PPPP or PPPR). The ability to support various QoS models.

[0132] (Receiver trigger for V2X reception) In the context of the high-level explanation of the V2X receiving operation described in Figure 13, the following One or more events include connection management-related messages, such as receiving a connection establishment message. This can trigger a V2X reception procedure, including monitoring of the device. • Triggered by a V2X application for transmission. In this case, the procedure is: application It is triggered as a result of an event originating from the layer. • Discovery is triggered by the application layer. • Periodic monitoring of reception in the V2X receive resource pool • The communication quality of current / existing V2X communications no longer meets the quality threshold. , one or more QoS profile metrics (e.g., packet error rate, latency, reliability, This can relate to things like communication range. In this case, the V2X upper layer of the V2X AS is To continue receiving V2X communication initiated by the application layer, another You can initiate communication with a UE or a group of UEs. For example, a UE can initiate communication with a formation group If it is a loop, when it detects that the V2X receive quality no longer meets the quality threshold, U E can initiate communication with other convoy lead UEs. • Wireless link failure, or beam failure, or failure to recover from beam failure. In this case, V2X The AS's V2X upper layer handles V2X communication initiated by the application layer. To continue, you can initiate receiving communications to another UE or group of UEs. Cut. • The current / existing V2X wireless link quality no longer meets the quality threshold. • Current / existing V2X communication congestion has exceeded the threshold. • The current / existing V2X communication transmit power exceeds the threshold, or the path loss exceeds the threshold. It is. • Mobility events, in this case, the V2X upper layer of V2X AS, application To continue the V2X communication initiated by the layer, another UE or UE group It can begin receiving V2X communications toward the target. Mobility events are transmitted to the UE itself. It can be related to the mobility of or related to the mobility of peer UE can. • For example, a scheduler that controls resource allocation from or to peer UEs. Received a disconnection notification from the entity. • Scheduling enterprise controls resource allocation from or to peer UEs. Received connection establishment request from the company. • Scheduling enterprise controls resource allocation from or to peer UEs. Received a handover request from the company. • Failure to reconfigure current / existing V2X communication connections.

[0133] The V2X upper layer can trigger the reception of the V2X communication operation as described in Figure 13. Similarly, the V2X AS layer triggers the reception of the V2X communication operation shown in Figure 13. It is possible.

[0134] (Receiver RAT selection and interface selection) Similar to the transmitting side operation described above, the V2X upper layer performs RAT selection or interface selection. A selection can be performed. In one embodiment, the receiving RAT of a given UE is the transmitting RA It can be set to be the same as T, that is, to be the same as the transmitting RAT. Similarly, the receiving interface can be the same as the transmitting interface, that is, The receiving side R is configured to be the same as the transmitting side interface. In another embodiment, the receiving side R The AT can be different from the transmitting RAT. Similarly, the receiving interface can be different from the transmitting interface. The interface can be different. The V2X upper layer is RAT selection and interface Face selection can be performed sequentially or simultaneously. V2X AS selects RAT For selection of an interface or configuration, support information such as availability information is provided at the V2X upper layer. It can be provided to. For example, the AS of a RAT can determine the availability of that RAT. This is possible. Furthermore, the AS determines the availability of an interface in relation to a specific RAT. This is possible. In an exemplary embodiment, the RAT is an NR RAT, an LTE RAT, and a Wi -It can be one or more of the following, such as Fi RAT. Similarly, the interface is Sidelink NR RAT, Uu RAT, Sidelink LTE RAT, Uu LTE RAT, sidelink Wi-Fi RAT, and between Wi-Fi and network It can be one or more wireless interfaces. The AS is based on one or more of the following , availability of interfaces associated with a specific RAT for RAT or V2X reception It can determine sex. • Communication quality threshold. The quality threshold is one or more QoS profile metrics (e.g., packet This can relate to factors such as error rate, latency, reliability, and communication range. • Wireless link quality threshold. • Congestion threshold. Congestion thresholds are used, for example, for channel congestion rate (CBR) and channel occupancy rate (CR). It can be related to things like that. • Wireless link failure, or beam failure, or failure to recover from beam failure. • Detection of areas outside of coverage or partial coverage. • Predicted received power threshold or path loss threshold. • Capabilities (e.g., UE capabilities, peer V2X UE capabilities, scheduling entities) (e.g., capabilities of gNB or network). Availability information may include one or more of the following: Available or unavailable. • Communication quality threshold • Wireless link quality threshold • Congestion threshold • Detection of out-of-coverage or partially out-of-coverage areas • Capabilities (e.g., UE capabilities, peer V2X UE capabilities, scheduling entities) (e.g., capabilities of gNB or network)

[0135] (Receiver sidelink communication mode selection) This section explains how the V2X upper layer performs unicast versus glue for V2X reception. This explains how to decide whether to use broadcast versus cast. (V2X upper level) The ear can decide which incoming cast type to use based on one or more of the following: . Instructions from the application layer. For example, as part of other connection management procedures such as connection establishment procedures or connection reconfiguration procedures. Instructions from the peer V2X UE sender. • Communication quality threshold. The quality threshold is one or more QoS profile metrics (e.g., packet This can relate to factors such as error rate, latency, reliability, and communication range. For example, a convoy group The group's member UE can, for example, determine whether groupcast communication is possible based on a threshold for communication reception quality. It can decide to request a switch to unicast communication, or uni Switch to receiving communications from other member UEs acting as relay UEs, based on cast. It is possible to decide to do so. • Service type or traffic type, e.g., signaling vs. application data. • Service authorization settings. • Capabilities, e.g., UE capabilities, peer V2X UE capabilities, scheduling entities Capabilities such as gNB or network capabilities. • Pre-configuration (e.g., ME, SIM, etc.), provisioning to UE via the network For example, V2X control functions, or scheduling entities can be used to configure UEs. Configuration to the UE, including the mapping of services to the outcast type. It is possible. • Link quality

[0136] (AS upper layer uses unicast vs groupcast vs broadcast transmission) (Mechanisms that determine this) The V2X AS layer determines the use of the incoming cast type based on one or more of the following: It is possible. • Instructions from the V2X upper layer. For example, as part of other connection management procedures such as connection establishment procedures or connection reconfiguration procedures. Instructions from the peer V2X UE sender. • Communication quality threshold. The quality threshold is one or more QoS profile metrics (e.g., packet This can relate to factors such as error rate, latency, reliability, and communication range. For example, a convoy group The group's member UE can, for example, determine whether groupcast communication is possible based on a threshold for communication reception quality. It can decide to request a switch to unicast communication, or uni Switch to receiving communications from other member UEs acting as relay UEs, based on cast. It is possible to decide to do so. • Service type or traffic type, e.g., signaling vs. application data. • Service authorization settings. • Capabilities (e.g., UE capabilities, peer V2X UE capabilities, scheduling entities) (e.g., capabilities of gNB or network). • Pre-configuration (e.g., ME, SIM, etc.), provisioning to the UE via the network. For example, V2X control function, or setting to UE by scheduling entity Includes configuration to the UE. The configuration includes mapping the service to the outcast type. It is possible. • Wireless link quality.

[0137] (Mechanism by which the V2X upper layer decides to use connection-oriented versus connectionless reception) ) The V2X upper layer performs connection-oriented reception or connection based on one or more of the following: You can decide whether to use the response reception feature. Instructions from the application layer. For example, as part of other connection management procedures such as connection establishment procedures or connection reconfiguration procedures. Instructions from the peer V2X UE sender. • Communication quality threshold. The quality threshold is one or more QoS profile metrics (e.g., packet This can relate to factors such as error rate, latency, reliability, and communication range. For example, a convoy group The member UE of the loop requires switching from connectionless reception to connection-oriented reception quality threshold. It can decide to request, or, on a connection-oriented basis, function as a relay UE. It can decide to switch to receiving communications from other member UEs. • Service type or traffic type, e.g., signaling vs. application data. • Service authorization settings. • Capabilities (e.g., UE capabilities, peer V2X UE capabilities, scheduling entities) (e.g., capabilities of gNB or network). • Pre-configuration (e.g., ME, SIM, etc.), provisioning to the UE via the network. For example, V2X control function, or setting to UE by scheduling entity Includes configuration to the UE. The configuration includes mapping the service to the outcast type. It is possible. • Link quality • Security requirements, e.g., security thresholds. Security requirements include authentication, integrity, Alternatively, it could be a requirement related to encryption.

[0138] (The mechanism by which the AS layer decides whether to use connection-oriented or connectionless) The V2X AS layer determines the use of the transmit cast type based on one or more of the following: It is possible. • Instructions from the V2X upper layer. For example, as part of other connection management procedures such as connection establishment procedures or connection reconfiguration procedures. Instructions from the peer V2X UE sender. • Communication quality threshold. The quality threshold is one or more QoS profile metrics (e.g., packet This can relate to factors such as error rate, latency, reliability, and communication range. For example, a convoy group The member UE of the loop requires switching from connectionless reception to connection-oriented reception quality threshold. It can decide to request, or, on a connection-oriented basis, function as a relay UE. It can decide to switch to receiving communications from other member UEs. • Service type or traffic type, e.g., signaling vs. application data. • Service authorization settings. • Capabilities (e.g., UE capabilities, peer V2X UE capabilities, scheduling entity capabilities) (e.g., capabilities of the system, gNB, or network). • Pre-configuration (e.g., ME, SIM, etc.), provisioning to UE via the network For example, V2X control functions, or scheduling entities can be used to configure UEs. Configuration to the UE, including the mapping of services to the outcast type. It is possible. • Wireless link quality. • Security requirements, e.g., security thresholds. Security requirements include integrity, or These can be requirements related to encryption.

[0139] (Unicast connection management) (High-level unicast connection management procedure) Figure 14 shows the high-level transmitting operation for unicast Layer 2 link management, including connection establishment. This is a diagram illustrating the bell. In step S1400, it is determined whether AS is connection-oriented. Steps S1402 and S1410 are performed. V2X between peer V2X UEs. Unicast connection establishment and connection context in the upper layer (V2X UpL) It means association. A unicast connection is also illustrated in step S1404. First, before forwarding unicast packets, configure the AS context between peer V2X UEs. And for association purposes, connection establishment signaling between peer V2X UEs is used, AS It can also be established without a connection. In this case, the peer V2X UE receiving side is connected to the receiving UE's UE. Considering the capabilities, this may include a dedicated radio resource configuration for unicast reception. This is configured in the settings. As part of the unicast connection establishment procedure, the UE uses unicast A This associates the S context with the corresponding V2X upper layer unicast context. This is possible. In the alternative embodiment shown in step S1410, AS is AS Connection In wireless settings, V2X upper layer unicast connections can be supported. The AS considers, for example, the UE capabilities of the receiving UE when configuring the receiving UE AS. Instead, AS resources are configured in a connectionless manner. This is configured. In this case, the necessary settings for the receiving UE are required before receiving the V2X packet. There is no Gunnaring. The receiving AS uses common default parameters for receiving V2X packets. The sender is configured to broadcast packets from an AS MAC perspective. It sends the encapsulated source ID and transmission within the received MAC PDU. Filtering of received packets is performed based on the destination ID. Step S1404 is shown in Figure In the case of the connection-oriented AS resource configuration shown, before the data packet is forwarded, the receiving On the side UE and the transmitting side UE, PHY, MAC, RLC, PDCP, and SDAP (If applicable) is set for this particular connection. Send before forwarding data packets. PHY channels that may include radio resource settings on both the sending and receiving UEs Logical settings, transport channel settings, HARQ entity settings, logical channel settings, Bearer configurations that may include security settings, QoS flow settings, and AS protocols AS context consisting of settings such as the association of these settings across the Corsa layer A st is created. Steps S1402 and S1404, or step S1 Once steps 410 and S1412 are completed, the transmitting UE and the receiving UE will connect the Packets (data or signaling) can be exchanged using the same communication method.

[0140] Step S1406 refers to link monitoring in the case of AS connectivity orientation. Monitoring is performed, for example, based on wireless link monitoring and beam management procedures, A This can be achieved in S. Link monitoring includes connection reset, beam recovery, and connection This can trigger the execution of connection maintenance procedures such as subsequent relocation or disconnection. Maintenance procedures involve the transmitting UE, receiving UE, or third party such as the scheduling entity. It can be triggered by the entity. In the case of AS connectionless communication, Link monitoring mentioned in step S1414 is, for example, performed by the V2X upper layer. Based on the link keep-alive procedure that is executed, it is implemented in the V2X upper layer. This is possible. In this case, link monitoring can detect sender reconfiguration, connection relocation, or connection This can trigger the execution of the deactivation. Also, in this case, the link maintenance procedure is performed on the transmitting side U By a third entity such as E, the receiving UE, or the scheduling entity This can be triggered. In step S1408, the link is released. Also, In step S1416, the link is released.

[0141] Figure 15 is a high-level explanatory diagram of the receiver operation for Layer 2 link management, including connection establishment. Provided. In step S1500, it is determined whether an AS connection is intended. Yes. If yes, in step S1502, establish a Layer 2 unicast link connection. The V2X upper layer configuration is performed. If not, in step S1510 Then, V2X upper layer configuration is performed to establish a Layer 2 unicast link connection. In Step S1512, the V2X SL RX AS setting, that is, Layer 2 unified Pre-configuration of common signaling or no signaling required for establishing a string connection. The SL RX AS configuration is executed. In step S1514, the V2X upper ray Link monitoring and maintenance are performed in Ya. In step S1516, The link will be unlinked. In step S1504, V2X SL RX AS settings In other words, a dedicated signaling base for Layer 2 for establishing a unicast link connection. The SL RX AS configuration is executed. In step S1506, the AS layer is configured. Link monitoring and maintenance are performed. In step S1508, link The cancellation process is executed.

[0142] (Detailed procedure for establishing a unicast connection) Figures 16, 17, 18, 19, 20, and 21 show the establishment of a unicast connection. Different alternative embodiments of detailed procedures to support follow-up data transfer They provide further detailed embodiments of the high-level procedures shown in Figures 14 and 15. It provides the following procedure, which is structured around three entities: Connection establishment procedure. The initiating UE (I-UE) is the UE that initiates the sequence, and the end receiving UE is the UE that initiates the connection establishment request. Target UE (T-UE), and resource configuration or resource scheduling machine A scheduling entity is an entity that provides functionality. The gentity controls the resource settings of gNB and other UEs, or other UEs A UE that assists in resource configuration, RSU-UE (i.e., a roadside unit that functions as a UE (Ro Ad Side Unit (RSU), RSU-gNB (i.e., RSU functioning as a gNB) UE to network relay (i.e., UEs that act as relay nodes to other UEs) Resource settings for an entity (e.g., an IAB node) or a UE under its control. This could be another local controller that provides the following. The remainder of this disclosure will be discussed below. Further extend the definitions of I-UE and T-UE as follows: Interface (e.g., P T-UE for configuration procedures via C5 interface or Uu interface is U It is E, the receiving UE of the configuration request. Interface (e.g., PC5 interface). The I-UE, regarding configuration procedures via the Uu interface, sends a configuration request. It is a UE. Configuration requests include connection establishment requests, connection reconfiguration or modification, connection relocation, or It can be one or more of the following: disconnection.

[0143] These figures also show that one or more of the steps described in Figures 12 and 13 have already been implemented. It is assumed that this has been done. Regarding resource allocation, each of the figures in the diagram also, Both T-UE and I-UE use RRC signaling or PC5-S signaling. After the wireless resource settings are configured, the T-UE uses autonomous resource selection for transmission. It can be used, or by the scheduling entity or I-UE It has also been proposed that it be possible to schedule dynamically. Similarly, I-UE, Can autonomous resource selection be used for transmission, or scheduling entry? It can be dynamically scheduled using either IT or T-UE.

[0144] Figures 16A to 16C show that the T-UE is controlled by the I-UE, or the scheduling enterprise This shows the steps for establishing a connection when configured by an I-UE in conjunction with the IT. In this embodiment of the connection establishment procedure, the V2X upper layer settings of the T-UE are configured in the I-UE Using SL RRC signaling from to T-UE, the AS layer settings of the T-UE are the same. They are sometimes transported.

[0145] Figures 16A to 16C show the target UE / RSU UP stack 1602, target UE / RSU RRC1604, Target UE / RSU-V2X Upper Layer Function 160 6. Start UE / RSU RRC1608, Start UE / RSU UP stack 1610, Open Initial UE / RSU-V2X upper layer function 1612, and gNB / RSU / scheduler Includes entity 1614. In step S1600, UE / RSU-V2X Communication is transmitted directly from the upper layer function 1612. In step S1602, start From UE / RSU RRC1608, SL RRC signaling - target device information A report request is sent. In step S1604, target UE / RSU RRC1 A request for upper layer information is sent from 604. In step S1606, the target A higher layer information response is sent from the UE / RSU-V2X higher layer function 1606. In step S1608, from target UE / RSU RRC1604, SL RRC signaling - Target device information response is sent. Step S1610 In addition, starting with UE / RSU RRC1608, RRC signaling - direct security A command is sent. In step S1612, resource allocation is performed. It is possible. In the optional step S1614, the criteria for establishing the connection are It can be verified and a connection can be established if necessary, but otherwise the resource - The allocation is performed. In step S1610a, the security procedure is performed. .

[0146] In step S1616, from the start UE / RSU RRC1608, RRC signal A request for ring V2X connection setting information is sent. In step S1618, the SL transmission setting The reception control and determination of fixed parameters are performed. In step S1620, gNB From / RSU / scheduling entity 1614, RRC signaling V2X sig Narrating information response is sent. In step S1622, target UE / RSU From RRC1604, the RRC Signaling - Direct Security Mode Complete message is displayed. It is sent. In step S1624, from start UE / RSU RRC1608, S L RRC signaling - Direct communication request is sent.

[0147] In step S1628, upper layer configuration information is transmitted. Step S1630 In step S1632, the T-UE protocol stack is configured. L RRC signaling - Direct communication acceptance message is sent. Step S1634 Then, an SR / BSR message is sent. In step S1636, gNB / From RSU / scheduling entity 1614, SL resource grant DCI information. The following is sent. In the optional step S1638, start UE / RSU UP start The 1610 uses SL resource grant DCI information to target UE / RSU UPs. It can be sent to tack 1602. In an alternative embodiment, step S1640 Step S1642 is executed. In step S1640, the target UE / RSU UP stack 1602 starts UE / RSU, UP stack 1610, SR / BSR The transmission is made, and in step S1642, the start UE / RSU UP stack 1610 is initiated. SL Resource Grant DCI information to target UE / RSU UP stack 1602 Send. In another alternative embodiment, steps S1644 and S1646 are performed. In step S1644, from target UE / RSU UP stack 1602 An SR / BSR was sent to the gNB / RSU scheduling entity 1614, and In pp S1646, gNB / RSU / entity1614 is SL resource group Send the Rant DCI information to the target UE / RSU UP stack 1602. Step S1684 can receive or transmit SL data. In step S1650, reception or transmission can be performed. In step S1652 In step S1654, wireless link monitoring can be performed. It can then perform the wireless link disconnection.

[0148] Figures 17A to 17C show that the T-UE is controlled by the I-UE, or the scheduling enterprise This shows the steps for establishing a connection, which is set up by I-UE in conjunction with the IT. In this embodiment of the establishment procedure, the V2X upper layer configuration of the T-UE is performed from the I-UE to the T- PC5 signaling to the UE is used to transport the AS layer configuration of the T-UE simultaneously. In Figures 17A to 17C, steps S1600, S1602, S1604, S1 606, S1608, S1610, S1610a, S1612, S1614, S1616 S1618, S1620, and S1622 are the same as in Figures 16A to 16C. In step S1656, the AS SL configuration information is transferred. In step S1658... In step S1660, a PC5 signaling-direct communication request is executed. Then, the transfer of AS SL configuration information is performed. In step S1662, I-UE P The protocol stack is set up. In step S1664, the T-UE protocol stack is set up. The block is set. In step S1666, PC5 signaling - direct communication acceptance This is executed. In step S1668, which can be optional, for example, To support mode 2-d or mode 2-b resource allocation, SR / BSR This can be sent to the gNB / RSU / scheduling entity 1614. In step S1670, which can be optional, gNB / RSU / schedule A Linking Entity 1614 sends an SL Resource Grant DCI. In step S1672, which can be performed, the start UE / RSU UP stack From step 1610, the SL resource grant DCI is sent. Steps S1674 and S Step 1676 is Alternative 1, and steps S1678 and S1680 are Alternative 2. In step S1674, from target UE / RSU UP stack 1602, SR / BSR is sent. In step S1676, start UE / RSU UP stack From step 1610, an SL resource grant SCI is sent. In step S1678 Target UE / RSU UP stack 1602 to gNB / RSU / scheduling An SR / BSR is sent to entity 1614. In step S1680, From gNB / RSU / scheduling entity 1614 to target UE / RSU An SL resource grant SCI is sent to UP stack 1602. Step S168 In step 2, the reception or transmission of SL data is performed. In step S1648, Reception or transmission of SL data is performed. In step S1686, the wireless link motor Monitoring is performed. In step S1688, wireless link disconnection is performed.

[0149] Figures 18A to 18C show that the T-UE is controlled by the I-UE, or the scheduling enterprise This shows the steps for establishing a connection when configured by an I-UE in conjunction with the IT. In this embodiment of the connection establishment procedure, the V2X upper layer settings of the T-UE are configured in the I-UE Using RRC signaling from to T-UE, the AS layer configuration of the T-UE is carried out simultaneously. It is sent. Furthermore, the V2X upper layer connection establishment procedure is the V2X AS layer connection establishment. It is executed independently of the procedure. In step S1800, start UE / RSU-V2X A PC5 signaling-direct communication request is sent from the upper layer function 1612. In the S1802, from the target UE / RSU-V2X upper layer function 1606, PC5 signaling - Direct security mode command is sent. Step S180 In step 6, from the target UE / RSU-V2X upper layer function 1606, PC5 signature Naring - Direct communication acceptance information is transmitted. In step S1808, direct communication Steps S1810, S1812, S1814, and S1816 are established. This can be an optional step. In step S1810, start UE / RS U RRC1608 sends SL RRC signaling - target device information request It is believed. In step S1812, from target UE / RSU RRC1604 Then, a request for upper layer information is sent. In step S1814, the target UE / R A higher layer information response is sent from the SU-V2X higher layer function 1606. In S1816, from target UE / RSU RRC1604, SL RRC signature A ringing-target device information response is sent. In step S1818, Source assignment can be performed (Alternative 1). Steps S1820, S1822 S1824 and S1826 are alternative 2. Options may be available. In step S1820, the criteria for establishing a connection are verified, and the connection is established as necessary. Otherwise, resource allocation is performed. In step S1822, start UE / RSU RRC1608 sends RRC signaling V2X connection configuration information request. In step S1824, the reception control and determination of the SL transmission setting parameters are performed. In step S1826, the gNB / RSU / scheduling entity From 1614, an RRC signaling V2X signaling configuration information response is sent.

[0150] In step S1828, starting from UE / RSU RRC1608, SL RRC Signaling - A direct AS connection request is sent. In step S1830, I-UE The protocol stack is configured. In step S1832, the upper layer configuration is performed. In step S1834, the T-UE protocol stack is configured. In step S1836, the SL RRC signaling - Direct AS connection acceptance signal is transmitted. Steps S1838 and S1840 are optional. Step S1838 In this process, an SR / BSR is sent from the starting UE / RSU UP stack 1610. In step S1840, the start UE / RSU UP stack 1610 is SL RISO Receive grant DCI. Alternative 1 is optional steps S1842, S184 4, and including S1846. In step S1842, target UE / RSU UP stack 1602 receives SL resource grant DCI. Step S1844 In this case, target UE / RSU UP stack 1602 transmits SR / BSR. In step S1846, the target UE / RSU UP stack 1602 is S L Resource Grant SCI is received. Alternative 2 is optional step S1848 This includes S1850. In step S1848, target UE / RSU UP Tack 1602 is SR / BSR to gNB / RSU / scheduling entity 16 Send to step 14. In step S1850, target UE / RSU UP stack 1602 receives SL resource grant DCI. In step S1852, - The GET UE / RSU UP stack 1602 receives or transmits SL data. Executed. In step S1854, start UE / RSU UP stack 1610 Therefore, the reception or transmission of SL data is performed. In step S1856, wireless Link monitoring is performed. In step S1858, wireless link disconnection is performed. It will be done.

[0151] Figures 19A to 19C show that the I-UE is controlled by the T-UE, or the scheduling enterprise This shows the steps for establishing a connection when configured by a T-UE in conjunction with the IT. In this embodiment of the connection establishment procedure, the V2X upper layer settings of the I-UE are configured in the T-UE Using PC5-S signaling from to I-UE, simultaneously with the AS layer configuration of the I-UE It is transported to. Furthermore, the connection establishment procedure for the upper layer of V2X is the connection of the V2X AS layer. This is performed independently of the establishment procedure.

[0152] Figures 19A to 19C show the start UE / RSU UP stack 1902, start UE / RSU RRC1904, Start UE / RSU-V2X Upper Layer Function 1906, Target UE / RSU RRC1908, target UE / RSU UP stack 1910, target UE / RSU-V2X upper layer function 1912, and gNB / RSU / scheduler The signaling entity 1614 is shown. In step S1900, PC5 signaling - A direct communication request is sent. In step S1902, PC5 signaling - direct A security mode command is sent. In step S1904, the PC5 signal A direct mode response completion message is sent. In step S1906, the PC 5. Signaling - A direct communication acceptance message is sent. In step S1908, Direct communication is established. In step S1910, a direct AS connection request is sent. In step S1912, the start UE / RSU-V2X upper layer function 1906 is performed. Get UE / RSU-V2X upper layer function 1912, PC5 signaling - direct A An S connection request is sent. In step S1914, a direct AS connection resource request is sent. It is trusted. In step S1916 (alternative 1), resource allocation is performed. Alternative 2 includes steps S1918, S1920, S1922, and S1924. This can be done. In step S1918 (optional), the criteria for establishing the connection are verified. A connection is established as needed; otherwise, resource allocation is performed. In step S1920, an RRC signaling V2X connection configuration information request is sent. In step S1922, the reception control and determination of the SL transmission setting parameters are performed. In step S1924, RRC signaling V2X signaling setting information is provided. The response is sent. In step S1926, a direct AS connection resource response is sent. .

[0153] In step S1928, the PC5 signaling-direct AS connection acceptance message is sent. It is trusted. In step S1930, the AS connection acceptance message is sent directly. In step S1932, the T-UE protocol stack is configured. Step S19 In step 34, the I-UE protocol stack is configured. Steps S1936 and S Step S1938 is optional. In step S1936, target UE / RSU From RRC1908 to gNB / RSU / scheduling entity 1614, SR / BSR is sent. In step S1938, gNB / RSU / scheduling From entity 1614 to target UE / RSU UP stack 1910, SL resource - Grant DCI is sent. Steps S1940, S1942, and S1944 This is also an optional step as alternative 1, step S1946, and S Step S1948 is an optional step as alternative 2. Then, the SL resource grant DCI message is sent. In step S1942 , SR / BSR is sent. In step S1944, SL resource grant SC The I message is sent. In alternative 2, in step S1946, the start UE / R SU UP stack 1902 to gNB / RSU / scheduling entity 161 In step 4, SR / BSR is transmitted. In step S1948, gNB / RSU / Ske Starting from Juring entity 1614 / RSU UP stack 1902, SL Source grant DCI is sent. In step S1950, start / RSU UP Stack 1902 performs the reception or transmission of SL data. Step S19 In step 52, the target UE / RSU UP stack 1910 processes the SL data. Reception or transmission is performed. In step S1954, wireless link monitoring is performed. The process is executed. In step S1956, the wireless link is disconnected.

[0154] Figures 20A to 20C show that the I-UE is controlled by the T-UE, or the scheduling enterprise This shows the steps for establishing a connection when configured by a T-UE in conjunction with the IT. In this embodiment of the connection establishment procedure, the V2X upper layer settings of the I-UE are configured in the T-UE Using PC5-S signaling from to I-UE, simultaneously with the AS layer configuration of the I-UE They will be transported to [location].

[0155] Figures 20A to 20C show the start UE / RSU UP stack 2002, start UE / RSU RRC1904, Start UE / RSU-V2X Upper Layer Function 1906, Target UE / RSU RRC1908, target UE / RSU UP stack 1910, target UE / RSU-V2X upper layer function 1912, and gNB / RSU / scheduler This shows entity 1614. In step S2000, start UE / RSU-V Starting with the 2X upper layer function 1906, UE / RSU RRC1904 directly communicates AS information. A report request is sent. In step S2002, the start UE / RSU RRC1904 Starting from UE / RSU-V2X upper layer function 1906, a direct communication AS information response is sent. In step S2004, the UE / RSU-V2X upper layer function 190 is initiated. From 6 to Target UE / RSU-V2X upper layer function 1912, SL PC5 signal A ring-direct communication request is sent. In step S2006, the target UE / R From SU-V2X upper layer function 1912 to target UE / RSU RRC1908, A direct communication AS information request is sent.

[0156] Steps S2008, S2010, S2012, S2014, and S2016 are O This can be an option step. In step S2008 (alternative 1), Source assignment can be performed. Alternative 2 is steps S2010, S2012 These are S2014 and S2016. In step S2010, for establishing a connection The criteria are verified, a connection is established if necessary, and if not, resource allocation is... Executed. In step S2012, target UE / RSU RRC1908 or Then, an RRC signaling V2X connection configuration information request is sent. In step S2014... Then, the reception control and determination of the SL transmission setting parameters are performed. Step S2016 In this case, from gNB / RSU / scheduling entity 1614 to target UE RRC Signaling V2X Signaling Configuration Information Response sent to / RSU RRC1908 It is believed. In step S2018, from target UE / RSU RRC1908 Initiating UE / RSU RRC1904, RRC signaling - direct security mode A command is sent. In step S2018a, perform the security procedure. This is possible. In step S2020, target from start UE / RSU RRC1904 UE / RSU RRC1908, RRC signaling - direct security mode complete A completion message is sent. In step S2022, target UE / RSU R Direct communication from RC1908 to target UE / RSU-V2X upper layer function 1912. An AS information response is sent.

[0157] In step S2024, the T-UE protocol stack is configured. In S2026, from target UE / RSU-V2X upper layer function 1912 Initiating UE / RSU-V2X upper layer functionality 1906, SL PC5 signaling - direct A communication acceptance message is sent. In step S2028, the start UE / RSU-V Starting with the 2X upper layer function in version 1906, AS layer settings will be applied to UE / RSU RRC1904. Information transfer message is sent. In step S2030, I-UE protocols The tack configuration is performed. Steps S2032 and S2034 are optional. In step S2032, the target UE / RSU UP stack 1910 is converted to gN An SR / BSR is sent to B / RSU / scheduling entity 1614. In step S2034, gNB / RSU / scheduling entity 1614 or The SL resource grant DCI sends to target UE / RSU UP stack 1910. It is believed.

[0158] In step S2036 (optional step), target UE / RSU U Starting from P stack 1910, UE / RSU UP stack 2002, SL resource graphics You can send a DCI signal. Steps S2038 and S2040 are optional. This is step S2038, and is alternative 1. In step S2038, start UE / RSU From UP stack 2002 to target UE / RSU UP stack 1910, SR / B SR is sent. In step S2040, target UE / RSU UP staff Starting from 1910, UE / RSU UP stack 2002, SL resource grant SC I is sent. In alternative 2, in step S2042, start UE / RSU UP From stack 2002 to gNB / RSU / scheduling entity 1614, SR / BSR is sent. In step S2044, gNB / RSU / scheduling Entity 1614 initiated SL resource grant DCI UE / RSU UPst Send to 2002. In step S2046, transmit sidelink data and Reception occurs. In step S2048, sidelink data is transmitted or received. This is performed. In step S2050, wireless link monitoring is performed. In step S2052, the wireless link is disconnected.

[0159] Figures 21A to 21C show that the I-UE is controlled by the T-UE, or the scheduling enterprise This shows the steps for establishing a connection when configured by a T-UE in conjunction with the IT. In this embodiment of the connection establishment procedure, the V2X upper layer settings of the I-UE are configured in the T-UE Using RRC signaling from the I-UE, the AS layer configuration of the I-UE is carried out simultaneously. It will be sent.

[0160] In step S2100, the start UE / RSU-V2X upper layer function 1906 A direct communication request is sent to the initiating UE / RSU RRC1904. Step S2102 In this case, from the starting UE / RSU RRC1904 to the target UE / RSU RRC19 In step 08, an SL RRC signaling-direct communication request is sent. In step S2104 Next, from target UE / RSU RRC1908 to target UE / RSU-V2X A direct communication V2X UPL information request is sent to the upper layer function 1912. Step S In 2106, the target UE / RSU-V2X upper layer function 1912 A direct communication V2X UPL information response is sent to the UE / RSU RRC1908. In step S2108 (Alternative 1), resource allocation is performed. Alternative 2 is , including steps S2110, S2112, S2114, and S2116. Step S 2110. In the optional step, the criteria are verified for connection establishment and, if necessary, The connection is established, otherwise resource allocation is performed. Step S21 In step 12, from target UE / RSU RRC1908 to gNB / RSU / schedule A request for RRC signaling V2X connection configuration information was sent to the ringing entity 1614. In step S2114, the reception control and determination of the SL transmission setting parameters are implemented. This can be done. In step S2116, gNB / RSU / scheduling Entity 1614 targets the RRC signaling V2X signaling configuration information response. Send to UE / RSU RRC1908. In step S2118, the target Starting from UE / RSU RRC1908, to UE / RSU UP stack 2002, RR C signaling - Direct security mode command is sent. Step S2118a In this step, security procedures are performed. In step S2120, the start UE / R From SU RRC1904 to target UE / RSU RRC1908, RRC signal A message indicating that security mode is complete is sent.

[0161] In step S2122, the T-UE protocol stack is configured. In 2124, starting from target UE / RSU RRC1908, UE / RSU R A message accepting direct communication via SL RRC signaling is sent to RC1904. In step S2126, the I-UE protocol stack is configured. Step S21 28. In the optional step, target UE / RSU UP stack 1910 An SR / BSR was sent from gNB / RSU / scheduling entity 1614. In step S2130, gNB / RSU / scheduling entity 1 614 is an SL resource grant DCI message targeting UE / RSU UPst Send to 1910. In step S2132, an optional step, target The UE / RSU UP stack 1910 is an SL resource grant DCI Message Send Start UE / RSU UP to stack 2002. Steps S2134 and S21 Step 36 is Alternative 1. Steps S2138 and S2140 are Alternative 2. In step S2134, the starting UE / RSU UP stack 2002 is used to target U An SR / BSR message is sent to the E / RSU UP stack 1910. In S2136, the target UE / RSU UP stack 1910 started the UE / R An SL resource grant SCI message is sent to SU UP stack 2002. In step S2138, the start UE / RSU UP stack 2002 is used to start gNB / R An SR / BSR message is sent to SU / scheduling entity 1614. In step S2142, the start UE / RSU UP stack 2002 is activated. The transmission or reception of iDLINK data is performed. In step S2144, the target The UE / RSU UP stack 1910 transmits or receives sidelink data. The signal is executed. In step S2146, wireless link monitoring is performed. In step S2148, the wireless link is disconnected.

[0162] (Unicast connection configuration parameters) (UE support information) Unicast connection settings or groupcast connection settings or broadcast connection settings To support this, T-UE requires one or more of the following setting parameters to be set in I-UE Alternatively, this information can be provided to the scheduling entity. T-UE acts as the receiving UE for protocol stack configuration across 5 interfaces. Because it can be provided by, the scheduling entity, or I-UE, Alternatively, it can be configured by an I-UE linked to a scheduling entity. Examples of relevant use cases are shown in Figures 16, 17, or 18. Alternative Embodiments In this configuration, the I-UE sets one or more of the following configuration parameters to the T-UE or scheduler. This information can be provided to the ing entity. Such information is available on the PC5 interface. This is provided by the I-UE, which acts as the receiving UE for protocol stack configuration across the board. Therefore, scheduling entities, or T-UEs or schedulers It can be configured by T-UE in conjunction with the ing entity. Related Yusuke Examples of the - are shown in Figure 18, Figure 20, or Figure 21. One or more of the following pieces of information are IU Provided to both E and T-UE scheduling entities, and I-UE or T - Can assist scheduling entities for UE configuration.

[0163] [Table 1-1] [Table 1-2]

[0164] (T-UE or I-UE configuration parameters) Scheduling entities, or I- To support connection settings by the UE, set one or more of the following parameters in the T-UE. This can be determined. Examples of such connection settings are shown in Figures 16, 17, and 17. The connection establishment procedure shown in 18 can be cited. Similarly, the scheduling entity or supports connection settings via T-UE in conjunction with scheduling entities. To achieve this, you can set one or more of the following parameters in the I-UE. Examples of connection configurations include the connection establishment procedures shown in Figures 19, 20, and 21. It is possible to do so.

[0165] [Table 2-1] [Table 2-2] [Table 2-3]

[0166] (Groupcast connection management) (High-level groupcast connection management procedure) Figure 22 shows the sender operation for groupcast Layer 2 link management, including connection establishment. This is a high-level explanatory diagram. In step S2200, whether AS is connection-oriented or not The determination is made. Steps S2202 and S2210 determine the V between peer V2X UE. Group cast connection establishment and connection container in 2X upper layer (V2X UpL) This signifies a quist association. The groupcast connection is also illustrated in step S2204. As described above, before forwarding the groupcast packet, the group UE and group members Group Lead U for setting and associating AS contexts between V2X UE Connection establishment signaling between E and group member V2X UE is used at the AS layer. It is also possible to stand. In this case, the group member V2X UE receiver is the group member Considering UE capabilities, this may include setting up a dedicated wireless resource for unicast reception. It is configured with a dedicated setting. As part of the groupcast connection establishment procedure, groupcast UEs involved in the communication use the groupcast AS context to connect to the corresponding V2X upper layer. It can be associated with the ear group cast context. As shown in step S2210. In an alternative embodiment, the AS uses an AS connectionless configuration with a V2X upper layer group. It can support precast connections.

[0167] In this case, AS does not consider, for example, the group member UE capabilities, AS resources This is configured using the AS connectionless method, which is configured in a connectionless manner. Signaling for setting up the receiving group member UE required before receiving V2X packets. There is no such thing. The receiving group member AS is a shared group member for receiving V2X groupcast packets. Set to the default parameters, the sender broadcasts from an AS MAC perspective. The packet is sent using the ST method, and here, the encapsulated MAC PDU received is... Receiving packets are filtered based on the source ID and destination ID. In the sequential AS resource configuration illustrated in step S2204, data packet forwarding is performed. Before this happens, the receiving UE and transmitting UE should configure the PHY, MAC, RLC, and PDCP. , and SDAP (if applicable) is configured for this particular groupcast connection This is done on both the sending and receiving UEs before the groupcast data packet is forwarded. PHY channel configuration, which may include physical layer multicast radio resource configuration. Transport channel configuration, HARQ entity configuration, logical channel configuration, security Bearer settings, QoS flow settings, and AS protocol sub-settings, which may include ti settings. Group cast AS consisting of settings such as the association of these settings across layers. A context is created. Steps S2202 and S2204, or steps Once steps S2210 and S2212 are completed, the transmitting UE and the receiving UE , exchanging packets (data or signaling) using a groupcast connection-oriented communication method It is possible.

[0168] Step S2206 is link monitoring in the case of AS groupcast connection-oriented communication. Link monitoring refers to, for example, wireless link monitoring and beam tube monitoring. Based on the established procedures, this can be achieved in AS. Connection reset, beam recovery, connection This can trigger the execution of connection maintenance procedures such as relocation or disconnection. The procedure is followed by the sending UE, receiving UE, or a third party such as the scheduling entity. It can be triggered by an entity. AS groupcast connectionless In the case of communications, the link monitoring mentioned in step S2214 is, for example, on V2X. Based on the link keep-alive procedure performed by the upper layer, the V2X upper layer This can be achieved in this case. In this case, link monitoring will be performed by resetting the sender and reconnecting. Groups including placement, disconnection, or leaving a group and joining a new group. This can trigger the execution of a reset. Also, in this case, the link maintenance procedure is performed on the transmitting side. By a UE, a receiving UE, or a third entity such as a scheduling entity This can be triggered. In step S2208, the link is unlinked. Furthermore, in step S2216, the link is unlinked.

[0169] Figure 23 shows the receiving side operation for groupcast Layer 2 link management, including connection establishment. Provide a high-level explanatory diagram. In step S2300, whether AS is connection-oriented or not. The determination is made. If yes, in step S2302, the V2X upper layer setting is This is performed to establish a Layer 2 unicast link connection. If no, step S2 In 310, the V2X upper layer setting is for establishing a Layer 2 unicast link connection. This is executed. In step S2304, the V2X SL RX AS configuration, i.e., Dedicated signaling-based S for Layer 2 for establishing Groupcast link connections L RX AS setting is performed. In step S2306, the link mode in AS is executed. Monitoring and maintenance are performed. In step S2308, link removal is performed. In step S2312, the V2X SL RX AS setting, i.e., Layer 2 Pre-configuration of common signaling or signaling for establishing a group cast link connection A no-setting-based SL RX AS configuration is performed. In step S2314, V Link monitoring and maintenance are performed at the 2X upper layer. Step S231 In step 6, the link is removed.

[0170] The detailed procedure for establishing a groupcast connection is the same as the procedure for unicast. Lameter refers to the "T-UE or I-EU configuration parameters" and "UE support information" mentioned above. The section titled "[...]" is the same as described above.

[0171] In one embodiment, groupcast communication is handled by a sector titled "Unicast Connection Management" Use the unicast configuration procedure described in the instructions to configure group member UEs individually. This can be configured by doing so. Similarly, connections for new group members can be configured by doing so. It can be added using the unicast connection setup procedure.

[0172] In an alternative embodiment, the groupcast connection is configured in a group manner. Given For a given group, specific UE capabilities to support connection-oriented communication for that group. Force can be requested from group member UEs. Such capabilities are available to UEs (e.g., Pre-configured in SIM or ME, for example, scheduling entities, for example For example, by a UE or group lead that functions as a scheduling entity. Broadcast signaling, or scheduling entity for resource configuration Through supporting the UE, it is set to the UE or by the V2X control function It can be provisioned for, for example, to request connection settings, or for connection Support information, including scheduling for group members to discover further configuration information, This information can be set in the UE. This information is a dedicated signal to the group member UE. Can it be provided via a multi-channel, or for example, SL-MCCH (SL multicast)? Can this be provided using a control channel in the manner of group casting, or SCCH (Sidelink Control Channel) is used via SL-SCH (SL Shared Channel). Either use SL-SCH (SL shared channel) or STCH (sidelinked Use a Rough Channel or SBCCH (Sidelink Broadcasting) It can be provided via broadcast using a control channel. The precast connection setting information is sent via SL-MCCH or SL-SCH(S Use SCCH (Side Link Control Channel I) via L Shared Channel, or if or via SL-SCH (SL Shared Channel) to STCH (Side Link Traffic Channel) Use the channel, or use SBCCH (Sidelink Broadcast Control Channel) It can be provided via broadcast using (L). Configuration information is periodically It can be sent as a signal.

[0173] The setting parameters described in the section titled "T-UE or I-UE setting parameters" In the meter, the destination ID in the bearer configuration becomes the group cast group identifier.

[0174] Group management functionality is performed by the V2X upper layer or application layer. When doing so, effective and efficient groupcast connection management from the perspective of wireless resource management. In some cases, the groups provided to the AS by the V2X upper layer may be too large. AS supports groupcast communication by using higher layer V2X groups in PH It can be subdivided into subgroups that communicate at the Y layer. AS is an AS subgroup. Using a mapping between the P ID and the corresponding Layer 2 destination ID of a larger group Each subgroup can be assigned a Layer 2 destination ID. AS is a subgroup A mapping table between the Layer 2 destination ID and the corresponding larger group ID. Maintain the settings. The group cast connection settings configured in the UE are directed to subgroup layer 2. Table of mappings between destination IDs and corresponding larger group Layer 2 destination IDs It may include the relationship between the subgroup destination ID and the group destination ID. In addition to the association table, the groupcast connection settings configured in UE are subgroup Instructions on whether to relay V2X data for the loop destination ID, and the data received by the UE. It may include instructions on whether or not it is requested to relay the data. Given group For a cast, the AS can configure the PHY with one or more of the following pieces of information: • Group Layer 2 Destination ID. • Group member's V2X UE ID (e.g., ProSe UE ID, UE ID) , or other identifiers that can be used by the UE as the source ID of a member UE. A list of Besshi. • Subgroup Layer 2 destination ID. • V2X UE ID of subgroup members (e.g., ProSe UE ID, UI D, or any other ID that can be used by the UE as the source ID of a member UE. A list of identifiers. For each subgroup, relay the data received for that subgroup, Or an instruction to not relay the message.

[0175] (Settings for V2X broadcast communication) A high-level diagram illustrating the AS configuration for broadcast V2X communication is provided for the transmitting side. Figure 24 shows the receiving side, and Figure 25 shows the AS broadcast V2X communication scenario. In Rio, T-UEs, i.e., UEs that receive configuration requests, are based on, for example, UE capabilities. No dedicated configuration is provided. Instead, the AS protocol stack uses, for example, the specifications. Based on the settings specified in the default parameters, or UE (SIM or ME) Based on the pre-configured settings, or provided to the UE by, for example, the V2X control function Based on the configured settings, the AS will be configured so that each MAC PDU is a Layer 2 sender. The broadcast resource that carries the source ID and Layer 2 destination ID is configured and Therefore, from the perspective of AS protocol stack configuration, it becomes a transmit connectionless system, but The layer is unicast in the V2X upper layer where the Layer 2 context is set. Connections or groupcast connections, and peer V2X maintained at the V2X upper layer. It was noted that the associations between layer contexts can still be maintained. In step S2400 of Figure 24, the V2X SL TX AS setting, that is, Pre-configuration of common signaling for SL TX AS settings for loadcast-based transmission Alternatively, the use of a dedicated signaling-based configuration is performed. Upper layer V2X connection configuration and Signaling for context setting, including associations between peer V2X UEs, for example In order to support a secure data link, one or more of the following may be used: . • In a connectionless manner, each MAC PDU carries the source and destination IDs. - PC5-S signaling via the plane. • PC5-S signaling via the user plane in an AS connection-oriented manner. If two V2X UEs involved in drink communication already have an AS connection (e.g., Unicast), This is possible if (T) is present. • PC5-S message embedded in RRC signaling message.

[0176] In step S2500 of Figure 25, the V2X SL RX AS setting, that is, Pre-configuration of common signaling for SL RX AS settings for broadcast-based reception Alternatively, the use of a base setting without signaling will be implemented.

[0177] The following section describes a method for UE processing of multiple simultaneous sidelink RRC connections. I will explain this.

[0178] (PC5 RRC connection status) Based on the explanations in the previous sections, the two peer UEs communicate via a V2X communication link. Before communication can begin, it may be necessary to initiate a PC5 RRC connection. The steps to establish the connection are described below and shown in Figure 26. Step S2600. The peer wants to communicate via the PC5 interface. PC5-S signaling to determine whether or not (DIRECT_COMMUNICA TION_REQUEST). Step S2602. UE capability exchange between two peer UEs. Step S2604. Access Layer (AS) configuration of the peer UE to enable V2X communication. fixed Step S2606. Inter-UE communication via PC5

[0179] Between steps S2600 and S1604, the UE is PC5_RRC_IDLE It can enter this state. In this state, the UE can receive communications as set (in advance). Monitor the signal and receive any possible PC5-S signaling messages from peer UE. Determine the status. In this state, all communication with the UE is controlled by the sidelink common control channel. It can be thought that this is done via the channel (SL_CCCH). Valid DIRECT When a _COMMUNICATION_REQUEST is received, the UE's PC5 signaling Graya determines whether direct linking is permitted and responds to the peer UE. If permitted, the UE will accept DIRECT_COMMUNICATON_ACCEPT. Send. Subsequently, the RRC layer exchanges UE capabilities with the peer UE and access layer configuration. The exchange will begin. These exchanges can also be done via SL_CCCH. These exchanges After successful completion, the UE can consider that a PC5 RRC connection has been established, and PC5 It can transition to the _RRC_CONNECTED state. In this state, the UE , • Control information is transmitted via a dedicated control channel (S_DCCH) for side links. User data can be sent via the traffic channel (SL_DTCH). , • Can have a sidelink wireless bearer setup for communication with peer UE. , • It is required to transmit a reference signal to assist in measuring the channel quality of the peer UE. There is a possibility, • It may be required to function as a synchronization reference source and transmit system information signals. can be, • Monitor the condition of the side links to evaluate link quality, declare a link failure, and report a link failure. They can take appropriate action.

[0180] In the above, it is assumed that the PC5 RRC connection will be established immediately after the AS configuration is changed. It is. Alternatively, the PC5 RRC connection is PC5RRCConnectionSet The `up` message format is used to confirm after subsequent signaling exchanges between UE1 and UE2. It can stand.

[0181] A PC5 RRC connection between two peer UEs involves one UE acting as the master of the connection. One UE acts as the slave of the connection. Only the master of the connection can access the PC5 RRC connection. You can change or delete connections. For example, UE1 can change the PC5 RRC connection between UE2 and UE2. If initiated, UE can become the master of the PC5 RRC connection, and UE2 will be the slayer. It can become a b. Alternatively, after the capability exchange shown in step S2602, UE1 is UE2 can be determined to be the master of the PC5 RRC connection, and UE1 This allows you to request that UE2 act as the master (for example, AS settings state The dedicated PC5RRCConnectionSetup station is available as an option. (At the top). UE1 can be determined based on many factors, including one or more of the following: ru. • Current load. For example, if there are many active RRC connections, UE2 will be set as the master. It can be expected to function. • Connectivity to the cellular network / Uu link quality. Where UE1 is outside the coverage area. In addition, you can request UE2 to function as a master. • Power status. If the UE2 has more power, or if the mains power supply (e.g., outlet) If powered from (connected to), UE1 acts as the master to UE2. It can be expected to function as intended. • Ability. UE1 does not possess the ability to function as a master, therefore UE2 must be the master. It can be requested to function in that way.

[0182] (Multiple PC5 RRC connections in UE) A typical UE has one or more RRC connections (see Figure 27). Of these connections One of these connections can be a connection to a gNB, and one or more of these connections can be a peer UE. This can be a connection to a PC. These latter connections are PC5 RRC connections. For each of the 5 RRC connections, the UE can be the master of the connection, or a thread. It can also be a link. For example, Figure 27 shows four PC5 RRC connections. 1. PC5 RRC connection 1, UE1 ←→ UE2 a. UE2 is the master, UE1 is the connected slave. 2. PC5 RRC connection 2, UE1 ←→ UE3 a. UE1 is the master, and UE3 is the connected slave. 3. PC5 RRC connection 3, UE1 ←→ UE4 a. UE1 is the master, and UE4 is the connected slave. 4. PC5 RRC connection 4, UE1 ←→ UEk a.UEk is the master, UE1 is the connected slave.

[0183] If the UE has multiple simultaneous RRC connections (as in UE1 in Figure 27), the UE will handle these It may be necessary to have a process for managing the links / relationships between connections.

[0184] (Keep UE1 in connected mode) This process can monitor the number of simultaneous PC5 RRC connections, and this number is configurable. If it is greater than the valid threshold (K), UE1 will block the RRC connection to the gNB as RRC_CONN It should be kept in ECTED mode. This will cause UE1 to schedule first. Without needing to send a request, you can send a Buffer Status Request to gNB. t:BSR) Reports can be sent. This allows sidelink transmission on PC5 This allows for faster resource allocation. UE1 can use RRC (for gNB). In IDLE mode, if the number of PC5 RRC connections exceeds this threshold, the UE will... E1 is requesting a connection so that it can send a BSR for sidelink transmission. To initiate an RRC connection with gNB, use the established cause set as shown in gNB. It is possible. For example, the establishment cause is "sidelinkResourceAllo It can be written as "cation".

[0185] (Disconnect all RRC connections) This process involves receiving a request from the gNB to stop all sidelink communications. Yes, it is possible. In RRC_IDLE mode (for gNB), the UE performs autonomous resource selection. It can be used to continue sending via sidelink. In some cases, gNB, To limit interference to neighboring cells and / or to reduce the load on cells, all It may be necessary to stop sending sidelinks. In such cases, RRC_IDL gNB is a mechanism to tell the UE to switch to E and stop all sidelink transmissions. Providing this could be useful. For example, gNB disconnects the RRC connection. This allows UE1 to be moved to RRC_IDLE. This message is It may also include instructions to disconnect one or more or all PC5 RRC connections. Upon receiving a message from NB, UE1 will send a message to all PC5 R, for which UE1 is the master. Disconnect the RC connection. Based on Figure 27, this is PC5 RRC connection 2 and This is for PC5 RRC connection 3. At the same time, UE1 connects to UE2 and UEk via PC Send the 5RRCConnectionReleaseIndication message. This allows these UEs to disconnect the PC5 RRC connection to UE1. The RCConnectionReleaseIndication should include the reason for the release. It is possible to do this (for example, "deactivate gNB").

[0186] (PC5 RRC connection priority management) Each PC5 RRC connection can be assigned a priority during setup. Process 1 can monitor the priority of all PC5 RRC connections and is available. Based on many factors such as available power, load, and proximity to peer UE, these PC5 R You can decide to pause or disconnect one or more RC connections. See Figure 27 as an example. When used in this way, PC5 RRC connection 3 can have the highest priority. Then, the UE can pause or disconnect PC5 RRC connections 1, 2, and 4. UE1 disconnects all PC5 RRC connections where it is the master. Based on Figure 27. This is for PC5 RRC connection 2. At the same time, UE1 is connected to UE2 and UEk to PC5RRCConnectionReleaseIndication message By sending a message, these UEs can be made to disconnect the PC5 RRC connection to UE1. It is possible. PC5RRCConnectionReleaseIndication is a solution. The reason for removal can be included (for example, "removed priority").

[0187] (PC5 unicast link granularity, unicast link update, and unicast link (Additional move) With LTE D2D, use the direct link setup procedure to set up two ProS Establish a secure direct link between e-compatible UEs. AS configuration is set to start UE and target UE. Not exchanged between UEs. As described herein, NR V2X is unified. Establishing a link requires the exchange of Access Layer (AS) settings between the starting UE and the target UE. It is necessary. An example of such a setting is the setting for bearers. This at the AS level Such bearer configurations are associated with V2X services supported over unicast links. This requires configuration of the corresponding QoS flow at the V2X layer. QoS flow ( Identified by a QoS flow identifier (QFI), i.e., the finest granularity of Q available. The OS level is related to V2X services supported via PC5 unicast links. PQI and packet filter sets that are attached and mapped to the AS bearer configuration. Includes QoS characteristics identified by QoS rules. V2X app running on UE The application manages the data traffic associated with each service using one or more QoS flows. It can support one or more services that can be mapped to several V 2X applications can run simultaneously on UE, and each application can run: It can generate data to support different services, and data from each service A data set can be mapped to one or more QoS flows.

[0188] Based on the above, the direct PC5-S link setup procedure for NR V2X The sequence is to support service data being transported via PC5 link using V2X Ray. In addition to configuring the QoS flow, a secure link is also established between the two V2X peer UEs. It has been proposed to define the following: Therefore, PC5 direct unicast link setup The procedure involves establishing a security context for a secure link between peer V2X UEs, and Supports service(s) data (one or more) delivered via unicast links. It has been proposed to use this for both configuring QoS flows and for other purposes.

[0189] (Unicast Link Modeling) Model 1

[0190] As shown in Figure 28, there is only one unicast link between the two peer V2X UEs. No. The PC5 unicast link establishment procedure establishes a secure link between two peer V2X UEs. Create a QoS flow for one or more services, where the service is , mapped to one or more applications. Establishing a security context is essential. In this model, the subsequent QoS flow The addition of this feature is proposed to be achieved through the PC5 unicast link update procedure. This procedure essentially involves setting up additional QoS flows after the unicast link has been established. The QoS flow is one or more services transported via a PC5 unicast link. It is mapped to the service data. The security context is unicast. The unicast link update procedure may not be performed as part of the update process, and therefore, the unicast link update may not be performed. In some cases, security parameters may not be exchanged between V2X peer UEs during the new procedure.

[0191] Model 2

[0192] In this model, there are two or more PC5 unicast links between the two peer UEs. It is possible that, as shown in Figure 29, there are two peer apps for each pair of two peer UEs. There is one unicast link between the communications.

[0193] In this embodiment, the PC5 unicast link establishment procedure involves two peer V2X UEs Create a secure link in between, and configure QoS flows for one or more services. Here, the service is mapped to a single application. In an alternative embodiment... , creating two or more unicast links simultaneously during the same unicast link establishment procedure The PC5 unicast link establishment procedure can securely establish a connection between two peer V2X UEs. Create a link and configure QoS flows for one or more services here The bis is mapped to two or more applications. In this model, the subsequent The addition of QoS flows is proposed to be achieved through the PC5 unicast link update procedure. This procedure is proposed. This procedure basically involves an additional QoS flow after the unicast link has been established. The QoS flow is configured and transported via the PC5 unicast link. It is mapped to data from one or more services. Followed via PC5 unicast link. One or more services to be added are unicasts established during the unicast link establishment procedure. It can belong to an existing application that has a Tlink (singular or plural). In this model, the new unicast link management procedure, namely PC5 unicast It has also been suggested to introduce a procedure for adding links. This procedure involves two peer V2X applications V2 adds additional links between applications and includes a new unicast link. One or more QoS flows to support one or more services of the X application Set this up. This procedure allows you to add two or more unicast links at the same time. The security context is not updated as part of the unicast link update procedure. In some cases, security may be required between V2X peer UEs during the unicast link update procedure. In some cases, the ty parameters may not be exchanged.

[0194] Model 3

[0195] In this model, there are two or more PC5 unicast links between the two peer UEs. It is possible that, as shown in Figure 30, one service for each of the two peer UEs A unicast cast link exists.

[0196] In this embodiment, the PC5 unicast link establishment procedure involves two peer V2X UEs Create a secure link between them and configure a QoS flow for a single service. In an alternative embodiment, two or more unicast links are established during the same unicast link establishment procedure. It is possible to create a link simultaneously, and the PC5 unicast link establishment procedure involves two peers V2 Creates a secure link between XUEs and also provides QoS for one or more V2X services. The row is set, and here the service is mapped to one or more applications. In this model, the addition of subsequent QoS flows is handled by the PC5 unicast link update procedure. Therefore, it has been proposed that this be achieved. This procedure basically involves a unicast link After establishment, additional QoS flows can be configured, and these QoS flows will be routed through the PC5 unicast link. It is then mapped to data from one or more existing services that are being transported. One or more services added via C5 Unicast Link are Unicast Link Existing applications with unicast links (one or more) established during the establishment procedure It can belong to the category. In this model, a new unicast link management tool It has also been proposed to introduce the procedure for adding a PC5 unicast link in that order. The procedure involves adding an additional link between the two peer UEs for the new service, and the new unit One or more Qo to support V2X services with added cast links. Configure S-flow. This procedure allows you to add two or more unicast links simultaneously. Yes, it is possible. The security context is updated as part of the unicast link update procedure. This may not always be possible, and therefore, during the unicast link update procedure, the V2X peer UEs may not be able to connect. Security parameters may not be exchanged.

[0197] Exemplary embodiments of this disclosure include a processor (e.g., processor 118), memory (e.g., For example, non-removable memory 130, removable memory 132, etc., and communication circuits A first device (UE, e.g., mobile device) including (for example, transceiver 120). Vice 102a, computer, vehicle (e.g., automobile 102b, motorcycle, boat) The first device provides (etc.) a communication network (for example, It is connected to RAN103 / 104 / 105 / 103b / 104b / 105b). Device 1 further includes computer executable instructions stored in memory, and the computer When an executable instruction is executed by the processor, it communicates to the first device, enabling the first device to communicate. A capable second device (second UE, e.g., mobile device 102a, computer, vehicle) (For example, cars 102b, motorcycles, boats, etc.) are detected and the second device is used to detect them. To obtain related device information, the first device establishes direct sidelink communication with the second device. Configure the device's wireless protocol (e.g., PC5 signaling protocol).

[0198] In an exemplary embodiment, the first device provides the second device with a device related to the second device. By sending a request for device information, the acquisition of device information related to the second device is opened. It can be started (for example, Figure 16A, SL RRC signaling-target device (See the information request.)

[0199] In an exemplary embodiment, the first device requests device information related to the second device. A response can be received to the response (for example, Figure 16A, SL RRC signaling The (see Target Device Information Response) includes device information related to the second device. nothing.

[0200] In an exemplary embodiment, the device information related to the second device is the device capability, V2X Includes one or more communication QoS setting parameters and sidelink measurements. Device capabilities The capabilities include, for example, V2X upper layer capabilities (e.g., security capabilities), SDAP capabilities, P DCP capability, RLC capability, MAC capability, baseband capability, RF band and subband It can be related to one or more factors, such as RF, including capability. Sidelink measurements are, for example, For example, these could be RSRP, RSRQ, RSSI, CBR, CR, etc.

[0201] In an exemplary embodiment, the first device sets the wireless protocol setting parameters of the first device. It is possible to determine the value of the device and also determine the wireless protocol setting parameters of the second device. Alternatively, the first device may receive information from the third device (e.g., a scheduling entity). Wireless protocol setting parameters of the first device and wireless protocol setting parameters of the second device Request the meter and the wireless protocol setting parameters of the first device and the wireless protocol of the second device. It can receive rotocol setting parameters.

[0202] In an exemplary embodiment, the determination of the wireless protocol setting parameters of the second device is performed by the second Consider the device information related to the second device. In an exemplary embodiment, the second device The determination of wireless protocol setting parameters is based on device information related to the second device and the first Consider the device information related to the device.

[0203] In an exemplary embodiment, the first device sets the wireless protocol setting parameters of the second device. The signal can be transmitted to the second device, or the second device can transmit the wireless program of the second device. The Tocol setting parameters can be received from the third device. In an exemplary embodiment, The wireless configuration parameters of the second device, transmitted to the second device, are then transmitted to the second device's wireless programme It is used by a second device to set the Tokol.

[0204] In an exemplary embodiment, the first device provides the second device with a device related to the first device. Chair information can be transmitted. In an exemplary embodiment, the equipment related to the first device The location information includes device capabilities, V2X communication QoS setting parameters, and sidelink measurements. Contains one or more values.

[0205] In an exemplary embodiment, the PC5 interface (see, for example, Figure 10) is the first Enables communication between the device and the second device via the PC5 interface and PC5 RR C signaling or PC5-S signaling is used. In exemplary embodiments, The PC5 interface enables communication between the first device and the third device, and The PC5 interface enables communication between the second and third devices. In a typical embodiment, PC5 RRC signaling or PC5-S signaling is used. It can be used via the PC5 interface.

[0206] In an exemplary embodiment, the wireless protocol includes, for example, an SDAP layer, a PDCP layer. This includes the ear, RLC layer, MAC layer, and PHY layer. For example, Figure 2 and Figure See section 6.

[0207] In exemplary embodiments, the first device or the second device is a vehicle. Both the first and second devices can be vehicles. One can be a mobile device, and the other can be a vehicle.

[0208] In an exemplary embodiment, the first device includes a transceiver (for example, transceiver 12 By (0), data can be transmitted from the first device to the second device.

[0209] In an exemplary embodiment, the third device is a roadside unit (e.g., RSU120b), a base station Stations (e.g., base stations 114a, 114b), relay nodes, vehicles (e.g., vehicle 102b) , or an integrated access and backhaul unit.

[0210] In an exemplary embodiment, the second device is a processor (e.g., processor 118) , memory (e.g., non-removable memory 130, removable memory 132), and The second device includes a communication circuit (for example, a transceiver 120). It is connected to a communication network. The second device is a computer stored in memory. Computer-executable instructions, including executable instructions, are executed by the processor. The second device is instructed to 1) determine the wireless protocol setting parameters of the first device, and the second device Either determine the wireless protocol setting parameters of the device, or 2) from the third device, the first The wireless protocol setting parameters of the first device and the wireless protocol setting parameters of the second device The system requests the wireless protocol setting parameters of the first device and the wireless protocol of the second device. The Tocol setting parameters are received. In an exemplary embodiment, the wireless programmer of the first device The determination of the Tokol setting parameters takes into account device information related to the first device, or The determination of the wireless protocol setting parameters of the first device is related to the second device. Consideration of S information and device information related to the first apparatus. In an exemplary embodiment, The second device transmits the wireless protocol configuration parameters of the first device to the first device. Whether or not the first device can set the wireless protocol setting parameters of the first device to the third It can be received from the device. In an exemplary embodiment, transmitted to the first device The wireless configuration parameters of the first device are used to configure the wireless protocol of the first device. It is used by the device.

[0211] In an exemplary embodiment, the first device provides the second device with a device related to the first device. It can transmit device information. Device information related to the first device includes device capability, V Includes one or more QoS setting parameters and sidelink measurements for 2X communication. The device includes a processor, memory, and communication circuitry. The second device communicates via the communication circuitry. It is connected to a communication network. The second device is a computer that stores data in memory. Computer-executable instructions, including executable instructions, are executed by the processor. The second device is instructed to determine the wireless protocol setting parameters of the first device, and the second device's wireless Determine the line protocol setting parameters. Alternatively, the second device receives from the third device, Wireless protocol setting parameters of the first device and wireless protocol setting parameters of the second device Request the meter and the wireless protocol setting parameters of the first device and the wireless protocol of the second device. It can receive rotocol setting parameters.

[0212] Exemplary embodiments of this disclosure include a first device comprising a processor, memory, and communication circuitry. The device provides a method for direct sidelink communication using a device, the first device communicating via a communication circuit It is connected to a communication network. This method involves the first device communicating with a second device that can communicate with it. To discover, to obtain information about devices related to the second device, and with the second device This includes configuring the radio protocol of the first device for direct sidelink communication.

[0213] Exemplary embodiments of the present disclosure are non-temporary having tangibly recorded computer-readable instructions. It provides a computer-readable storage medium, and computer-readable instructions are executed by processing circuits. Then, the processing circuit is instructed to use the first device to directly perform the sidering communication method. This method involves the first device discovering a second device with which it can communicate, and the second device being related to To obtain device information and to enable direct sidelink communication with the second device, the first This includes configuring the wireless protocol of the device.

[0214] In an exemplary embodiment, the PC5 interface is between the first device and the second device. It is a unicast link, and one or more pairs of peers in the first device and the second device. This enables communication between services.

[0215] In an exemplary embodiment, all services using the same PC5 unicast link They use the same application.

[0216] In an exemplary embodiment, one PC5 unicast link provides one or more services This type is less likely to be used for peer applications of this one PC5 unicast link pair. If associated, it supports one or more service types.

[0217]

[0218] Perform any of the methods and processes described herein on a computer-readable storage medium. It is embodied in the form of stored computer executable instructions (i.e., program code). This allows the commands to be sent to computers, servers, M2M terminal devices, and M2M gates. When executed by a machine such as a way device, the system described herein, It will be understood that laws and processes are to be executed and / or implemented. Specifically , any of the above steps, operations, or functions, such computer executable life It can be implemented in the form of a decree. Computer-readable storage media are for storing information. Volatile and non-volatile, removable and removable, implemented by any method or technique. This includes media that are impossible to store, but such computer-readable storage media do not contain signals. Computer-readable storage media include RAM, ROM, EEPROM, flash memory, and This is not a memory technology, CD-ROM, Digital Multipurpose Disc (DVD), or other optical data Disc storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic It can be used as a storage device or to store desired information. This includes, but is not limited to, other physical media that can be accessed by the computer. It will not be done.

[0219] When describing preferred embodiments of the subject matter of this disclosure as shown in the figures, in order to clarify, Fixed terminology is used. However, the subject matter described in the claims is selected in this way. It is not intended to be limited to specific terms, and each specific element serves a similar purpose. Therefore, it should be understood that this includes all technical equivalents that operate in a similar manner.

[0220] Therefore, the disclosed systems and methods deviate from their spirit or essential characteristics. Those skilled in the art will understand that it can be realized in other concrete forms without having to do so. Therefore, the embodiments disclosed herein are exemplary in all respects. Therefore, it is not considered to be limited. It is not exhaustive, and is as disclosed. This disclosure is not limited to any form. Modifications and variations are possible in consideration of the above teachings. And, without deviating from the breadth or scope, the results obtained from the practice of this disclosure This is possible. Therefore, although this specification has described specific settings, other settings are also possible. It is also possible to adopt numerous modifications and other embodiments (e.g., combinations, rearrangements, etc.). ) is made possible by this disclosure, is within the scope of the art, and applies to the disclosed subject matter and its It is intended to fall within the range of any equivalent. Features of the disclosed embodiments These are combined, rearranged, and simplified within the scope of the invention to produce additional embodiments. It can be abbreviated, etc. Furthermore, certain features can sometimes be used in conjunction with other features. It can be used advantageously without having to do so. Therefore, the applicant(s) can open All such substitutes, modifications, equivalents, and It is intended to include deformed objects.

[0221] A reference to a singular element means "only one" unless explicitly stated otherwise. It does not mean "one or more," but rather is intended to mean "one or more." Furthermore, "A, B, or If a phrase similar to "at least one of C" is used in the claims, that word The phrase states that only A can exist in the embodiment, and only B can exist in the embodiment. It is possible that C may be present in the embodiment, or that A, B and C Any combination of elements can exist in a single embodiment, for example, A and It is interpreted to mean B, A and C, B and C, or A, B and C. That is the intention.

[0222] In this specification, elements are not explicitly enumerated using the phrase “means for” To the extent that otherwise, any claim element shall be interpreted in accordance with Section 112(f) of the United States Patent Act. It does not mean that. The terms "constitute," "include," or other similar terms used herein are not applicable. The variant term is intended to cover non-exclusive inclusion, from a list of elements. The process, method, article, or apparatus includes not only those elements but also the following: Any process, method, article, or apparatus not explicitly listed or unique to it It may include other elements that are not present in the above description. The scope of the present invention is not as described above but as per the attached patent application. The scope of the request is indicated, and all that fall within its meaning, scope, and equivalence. The changes are intended to be included there.

Claims

1. A first Wireless Transmit / Receive Unit (WTRU), A first sidelink radio resource control (RRC) message requesting sidelink information from the second WTRU is transmitted to the second WTRU, Receiving a second sidelink RRC message from the second WTRU, which includes capability information associated with the second WTRU, wherein the capability information includes one or more access layer (AS) layer parameters for sidelink communication. Based on the receipt of the second sidelink RRC message from the second WTRU, a first RRC message requesting sidelink transmission resources is sent to the network node, wherein the first RRC message includes the capability information instruction in the second sidelink RRC message received from the second WTRU. Receiving a second RRC message containing sidelink resource allocation information from the network node A first WTRU comprising a processor configured to perform the following.

2. The first WTRU according to claim 1, wherein the second RRC message includes AS configuration information for sidelink communication between the first WTRU and the second WTRU.

3. The first WTRU according to claim 2, wherein the processor is configured to transmit a third sidelink RRC message to the second WTRU, the third sidelink RRC message including the AS configuration information in the second RRC message received from the network node.

4. The first WTRU according to claim 3, wherein the processor is configured to receive a fourth sidelink RRC message from the second WTRU, the fourth sidelink RRC message indicating that the second WTRU has received the AS configuration information for communication with the first WTRU.

5. The first WTRU according to claim 3, wherein the third sidelink RRC message includes sidelink link wireless bearer configuration information.

6. The first WTRU according to claim 3, wherein the third sidelink RRC message includes sidelink link logic channel setting information.

7. The first WTRU according to claim 3, wherein the third side link RRC message includes side link measurement value setting information.

8. The first WTRU according to claim 1, wherein the first and second sidelink RRC messages are PC5-RRC messages.

9. The first WTRU according to claim 1, wherein the second sidelink RRC message includes frequency information that the second WTRU is interested in using for sidelink communication.

10. The first WTRU according to claim 2, wherein the AS layer parameters included in the capability information of the second sidelink RRC message include one or more radio link control (RLC) parameters.

11. A method performed by a first Wireless Transmit / Receive Unit (WTRU), A first sidelink radio resource control (RRC) message requesting sidelink information from the second WTRU is transmitted to the second WTRU, Receiving a second sidelink RRC message from the second WTRU, which includes capability information associated with the second WTRU, wherein the capability information includes one or more access layer (AS) layer parameters for sidelink communication. Based on the receipt of the second sidelink RRC message from the second WTRU, a first RRC message requesting sidelink transmission resources is sent to the network node, wherein the first RRC message includes the capability information instruction in the second sidelink RRC message received from the second WTRU. Receiving a second RRC message containing sidelink resource allocation information from the network node Methods that include...

12. The method according to claim 11, wherein the second RRC message includes AS configuration information for sidelink communication between the first WTRU and the second WTRU.

13. The method according to claim 12, further comprising sending a third sidelink RRC message to the second WTRU, wherein the third sidelink RRC message includes the AS configuration information in the second RRC message received from the network node.

14. The method of claim 13, further comprising receiving a fourth sidelink RRC message from the second WTRU, the fourth sidelink RRC message indicating that the second WTRU has received the AS configuration information for communication with the first WTRU.

15. The method according to claim 13, wherein the third sidelink RRC message includes sidelink link wireless bearer configuration information.

16. The method according to claim 13, wherein the third sidelink RRC message includes sidelink link logical channel setting information.

17. The method according to claim 13, wherein the third side link RRC message includes side link measurement value setting information.

18. The method according to claim 13, wherein the first and second sidelink RRC messages are PC5-RRC messages.

19. The method according to claim 13, wherein the second sidelink RRC message includes frequency information that the second WTRU is interested in using for sidelink communication.

20. The method according to claim 13, wherein the AS layer parameters included in the capability information of the second sidelink RRC message include one or more radio link control (RLC) parameters.

Images