Apparatus, system, method, and computer-readable medium for connection-oriented vehicle-to-all (VTX) communication 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 of related applications) This application is a continuation of U.S. Provisional Application No. 62 / 805,121, filed February 13, 2019. and the benefit of U.S. Provisional Application No. 62 / 841,579, filed May 1, 2019. No. 6,239,999, the entire contents of which are incorporated herein by reference.

[0002] FIELD OF THE DISCLOSURE The present disclosure relates generally to wireless communications, and more particularly to a method for performing vehicle-to-all communications. The present invention relates to a wireless communication system, device, method, and computer-readable medium. [Background technology]

[0003] The "Background" section provided herein is provided to generally present the context of the present disclosure. The presently named inventions to the extent described in this Background section The work of the inventors and aspects of the disclosure that may not be admitted as prior art at the time of filing are No admission is expressly or impliedly made as prior art to the present application.

[0004] Existing vehicle-to-X systems and methods are connectionless, which is necessary for 5G systems. It does not support the requirements of high data rates, high reliability, and low latency. Furthermore, in existing systems, connectionless transmission results in high protocol overhead. It brings several drawbacks such as high processing overhead and physical layer feedback. It is difficult to make this possible. Summary of the Invention

[0005] An exemplary embodiment of the present disclosure includes a first device including a processor, a memory, and a communication circuit. The first device is connected to a communication network via a communication circuit. The apparatus of claim 1 further includes computer-executable instructions stored in the memory, and the computer The executable instructions, when executed by the processor, cause the first device to and discovering a second device capable of performing the authentication and authentication of the second device, obtaining device information related to the second device, and The wireless protocol of the first device is configured for direct sidelink communication with the first device.

[0006] An exemplary embodiment of the present disclosure includes a first device including a processor, a memory, and a communication circuit. a first device communicating with a second device via a communication circuit; The method includes: a first device identifying a second device with which it can communicate; Discovering and obtaining device information associated with the second device; and communicating with the second device. and configuring a radio protocol of the first device for direct sidelink communication.

[0007] An exemplary embodiment of the present disclosure is a non-transitory computer-readable storage medium having computer-readable instructions tangibly recorded thereon. a computer-readable storage medium, the computer-readable instructions being executable by a processing circuit; and causing the processing circuit to perform a method for direct sidelink communication using the first device. The method includes a first device discovering a second device with which it can communicate and a second device associated with the second device. and obtaining device information for direct sidelink communication with the second device. and configuring the wireless protocol of the device.

[0008] This Summary of the Invention is presented in a simplified form that is further described in the Detailed Description below. This Summary is provided to introduce a selection of concepts in a format that is consistent with the claimed subject matter. It is not intended to identify key or essential features of the subject matter, and Nor is it intended to be used to limit the scope of the claimed subject matter. Furthermore, claimed subject matter may be derived from any or all of the methods described anywhere in this disclosure. Not bound by restrictions that solve all disadvantages. [Brief explanation of the drawings]

[0009] The scope of the present disclosure is best understood from the following detailed description of exemplary embodiments when read in conjunction with the accompanying drawings. It is best understood from the perspective of [Figure 1A] FIG. 1A is a system diagram illustrating an example 3GPP architecture. [Figure 1B] FIG. 1B is a system diagram of an exemplary apparatus or device configured for wireless communication. [Figure 1C] FIG. 1C is a system diagram illustrating an example of a Radio Access Network (RAN) architecture and a core network architecture. [Figure 1D] FIG. 1D is a system diagram illustrating an example of a radio access network (RAN) architecture and a core network architecture. [Figure 1E] FIG. 1E is a system diagram illustrating an example of a radio access network (RAN) architecture and a core network architecture. [Figure 1F] FIG. 1F is a system diagram illustrating an example of a computing system for use in a communications network. [Figure 1G] FIG. 1G is a system diagram illustrating an example 3GPP architecture. [Figure 2] FIG. 2 illustrates a control plane protocol stack for point-to-point sidelink communication according to an example embodiment. [Figure 3]FIG. 3 illustrates the establishment of a secure Layer 2 link via PC5 according to an example embodiment. [Figure 4] FIG. 4 illustrates a user plane protocol stack for sidelink communications according to an example embodiment. [Figure 5] FIG. 5 illustrates an overview of 5G V2X requirements versus LTE V2V R14 requirements, according to an example embodiment. [Figure 6] FIG. 6 illustrates an SDAP sublayer structure for V2X sidelink communications, according to an example embodiment. [Figure 7] FIG. 7 illustrates an L2 architecture for V2X sidelink communication, according to an example embodiment. [Figure 8] FIG. 8 illustrates an L2 architecture for V2X sidelink communication, according to an exemplary embodiment. [Figure 9] FIG. 9 illustrates an L2 architecture for V2X sidelink communication, according to an example embodiment. [Figure 10] FIG. 10 illustrates an SDAP layer functional diagram for V2X sidelink communications, according to an example embodiment. [Figure 11] FIG. 11 illustrates a UL or DL ​​sidelink SDAP data PDU format with an SDAP header according to an example embodiment. [Figure 12] FIG. 12 illustrates a method for transmitting V2X communications, according to an example embodiment. [Figure 13] FIG. 13 illustrates a method for receiving V2X communications, according to an example embodiment. [Figure 14] FIG. 14 illustrates a sender-side unicast method for Layer 2 link management, according to an example embodiment. [Figure 15] FIG. 15 illustrates a receiver-side unicast method for Layer 2 link management, according to an example embodiment. [Figure 16A] FIG. 16A illustrates a unicast connection establishment method in which an initiating UE RRC configures or assists in configuring a target UE, according to an example embodiment. [Figure 16B] FIG. 16B illustrates a unicast connection establishment method in which an initiating UE RRC configures or assists in configuring a target UE, according to an example embodiment. [Figure 16C] FIG. 16C illustrates a unicast connection establishment method in which an initiating UE RRC configures or assists in configuring a target UE, according to an example embodiment. [Figure 17A] FIG. 17A illustrates a unicast connection establishment method in which an initiating UE PC5 configures or assists in configuring a target UE, according to an example embodiment. [Figure 17B] FIG. 17B illustrates a unicast connection establishment method in which an initiating UE PC5 configures or assists in configuring a target UE, according to an example embodiment. [Figure 17C] FIG. 17C illustrates a unicast connection establishment method in which an initiating UE PC5 configures or assists in configuring a target UE, according to an example embodiment. [Figure 18A] FIG. 18A illustrates a unicast connection establishment method in which an initiating UE RRC configures or assists in configuring a target UE, according to an example embodiment. [Figure 18B] FIG. 18B illustrates a unicast connection establishment method in which an initiating UE RRC configures or assists in configuring a target UE, according to an example embodiment. [Figure 18C] FIG. 18C illustrates a unicast connection establishment method in which an initiating UE RRC configures or assists in configuring a target UE, according to an example embodiment. [Figure 19A] FIG. 19A illustrates a unicast connection establishment method in which a target UE PC5 configures or assists in configuring a target UE, according to an example embodiment. [Figure 19B] FIG. 19B illustrates a unicast connection establishment method in which a target UE PC5 configures or assists in configuring a target UE, according to an example embodiment. [Figure 19C] FIG. 19C illustrates a unicast connection establishment method in which a target UE PC5 configures or assists in configuring a target UE, according to an example embodiment. [Figure 20A] FIG. 20A illustrates a unicast connection establishment method in which a target UE PC5 configures or assists in configuring a target UE, according to an example embodiment. [Figure 20B] FIG. 20B illustrates a unicast connection establishment method in which a target UE PC5 configures or assists in configuring a target UE, according to an example embodiment. [Figure 20C] FIG. 20C illustrates a unicast connection establishment method in which a target UE PC5 configures or assists in configuring a target UE, according to an example embodiment. [Figure 21A] FIG. 21A illustrates a unicast connection establishment method in which a target UE RRC configures an initiating UE, according to an example embodiment. [Figure 21B] FIG. 21B illustrates a unicast connection establishment method in which a target UE RRC configures an initiating UE, according to an example embodiment. [Figure 21C] FIG. 21C illustrates a unicast connection establishment method in which a target UE RRC configures an initiating UE, according to an example embodiment. [Figure 22] FIG. 22 illustrates a sender groupcast method for Layer 2 link management, according to an example embodiment. [Figure 23] FIG. 23 illustrates a receiver groupcast method for Layer 2 link management, according to an example embodiment. [Figure 24] FIG. 24 illustrates sender broadcast transmission settings according to an example embodiment. [Figure 25] FIG. 25 illustrates receiver broadcast transmission settings according to an example embodiment. [Figure 26] FIG. 26 shows the PC5 RRC connection state between two UEs. [Figure 27]Figure 27 shows a UE having multiple RRC connections with a gNB and multiple UEs. [Figure 28] FIG. 28 illustrates a first exemplary PC5 unicast link model. [Figure 29] FIG. 29 illustrates a second exemplary PC5 unicast link model. [Figure 30] 30 illustrates a third exemplary PC5 unicast link model. Further areas of applicability of the present 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 intended to necessarily limit the scope of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0010] 3rd Generation Partnership Project: 3GPP) is a group of companies that develops radio access, core transport networks, and codecs. ,security, and service capabilities, including work on quality of service, cellular Developing technical standards for communication network technology. :RAT) standards include WCDMA (commonly known as 3G), LTE (commonly known as LTE-Advanced standards, and the new LTE standard also known as "5G." There is a new radio technology (New Radio: NR). Development of the 3GPP NR standard will continue. This is expected to include the definition of next generation radio access technologies (new RATs). New flexible wireless access offerings below 7 GHz and new ones above 7 GHz This is expected to include the provision of ultra-mobile broadband wireless access. Flexible wireless access is a new, non-backward compatible wireless technology in new frequency bands below 7 GHz. 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 different requirements. Ultra-mobile broadband includes, for example, indoor applications and hotspots. Centimeter and millimeter wave frequencies provide ultra-mobile broadband access opportunities It is expected that frequency bands will be included. Flexible wireless access below 7 GHz with dedicated design optimization for inch and mmWave It is expected that they will share a common design framework.

[0011] 3GPP has identified a variety of use cases that NR is expected to support. This results in a wide variety of user preferences regarding data rates, latency, and mobility. The use cases fall into the following general categories: Enhanced Mobile Broadband (eMBB) ultra-reliable, low-latency communications Ultra-Reliable Low-Latency Communication (URLLC), large-scale machine types Massive Machine Type Communications (mMTC), network operations (e.g. For example, network slicing, routing, migration and interworking and Enhanced Vehicle-To-Everything : eV2X) communication, Vehicle-To-Vehicle Communication (V 2V), Vehicle-To-Infrastructure Communication :V2I), Vehicle-To-Network Communication (V2N) , Vehicle-To-Pedestrian Communication (V2P), and other These categories include those that can include vehicle communications with the public or private entities. Specific services and applications in the network include, for example, monitoring and sensor networks. Work, remote device control, two-way remote control, personal cloud computing , video streaming, wireless cloud-based office, first responders connectivity, car emergency call systems, disaster warnings, real-time gaming, multi-person video games Video calling, autonomous driving, augmented reality, touch internet, virtual reality, home automation Applications, robots, and aerial drones are just a few examples. All of the above and other use cases are contemplated herein.

[0012] Next, we will introduce some abbreviations related to service levels and core network technologies that may appear in the following description. Unless otherwise specified, the abbreviations used herein are as follows: means the corresponding term shown.

[0013] Abbreviation 3GPP:3 rd Generation Partnership Project to) 5G: 5th Generation 5QI:5G QoS identifier ACK: ACKnowledgement AM: Acknowledged Mode AMF: Access and Mobility Function APP: APPlication AS: Access Stratum BWP: Bandwidth Part BSD:Bucket Size Duration BSR: Buffer Status Report CBR: Channel Busy Ratio Config:Configuration 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 Radio Access Network) eNB: evolved NodeB 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 Info:Information IP: Internet Protocol ITS: Intelligent Transport System ITS-AID: ITS Application Identifier I-UE: Initiating 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: Node B NR: New Radio (New Radio Technology) PBR: Prioritized Bit 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 ProSe control plane and user plane for UE-to-network relay (reference point between ProSe-enabled UEs used for the 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 Channel) SCCH: Sidelink Control Channel SL-SCH: Sidelink Shared Channel TM: Transparent Mode T-UE: Target UE TX: Transmitter or Transmitting UDC: Header Data Compression UE: User Equipment UL: Uplink UM: Unacknowledged Mode UMTS: Universal Mobile Telecommunications System System) UpL: Upper Layer USIM: Universal Subscriber Identify Module ) Uu: Uu Interface connecting UE to RAN (Source) V2V: Vehicle-to-Vehicle Communication V2X: Vehicle-to-X Communication VQI:V2X QoS Identifier WG2: Working Group 2 WiFi:WLAN radio wireless technology, used interchangeably with WLAN in This document (WLAN wireless technology, which is used interchangeably with WLAN in this document) (used) WLAN: Wireless Local Area Network

[0014] In this disclosure, the following features / procedures / functions are described: NR V2X side link L2 structure. Covering unicast, groupcast and broadcast transmission modes, Connection V2X upper layer connection setting, V2X AS connection setting, V2X for V2X upper layer connection V2 connection setup procedure, including AS support. Provision for V2X transmitter and receiver. V2X RAT and interface selection. -V2X communication mode selection. Specifically, the following concepts and topics will be covered: 1. Layer 2 protocol structure, 2. V2X sender and receiver provisioning, 3. V2X transmission or V2X reception trigger, 4. Who selects and based on which criteria, the sending and receiving RATs and interfaces Interface selection, 5. Transmitter and receiver transmission mode selection and selection criteria; 6. Unicast connection, including a description of the support parameters from the UE (e.g., receiver capabilities) Detailed procedures for management and scheduling entities or unicast configuration parameters configured in the UE by a supporting UE in cooperation with the 7. Different Alternatives for Connection Management 8. Group connection configuration and V2X upper layer group mapping to AS layer subgroups The idea of ​​ping, the maintenance of a mapping table in the AS, and the AS to PHY Broadcast configuration and various options for broadcast configuration signaling tion. 9. Method for UE handling of multiple simultaneous sidelink RRC connections. 10. PC5 Unicast Link Granularity Modeling, Unicast Link Updates, and Unicast Links How to add a unicast link.

[0015] Exemplary Communication Systems and Networks FIG. 1A illustrates a system in which the methods and apparatus described and claimed herein may be incorporated. 1 illustrates an embodiment of an exemplary communication system 100. As shown, The communication system 100 includes a wireless transmit / receive unit (WT RU) 102a, 102b, 102c, 102d, 102e, 102f, and / or 102g (which may be referred to generally or collectively 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 Server) 113, although the disclosed embodiments may include any number of WTRUs, It is understood that base stations, networks, and / or network elements are intended. WTRU 102a, 102b, 102c, 102d, 102e, 102f, 1 Each of the 02g includes any device configured to operate and / or communicate in a wireless environment. Each WTRU 102a, 102b, 102b may be any type of apparatus or device. 1A to 1E, 102c, 102d, 102e, 102f, and 102g are handheld wireless devices. Although illustrated as a wired communication device, a wide variety of use cases are intended for wireless communication. In the example, each WTRU may be any WTRU configured to transmit and / or receive wireless signals. It may include or embody any type of apparatus or device. It will be understood that, by way of example only, a user equipment (UE), a mobile station, a fixed or mobile subscriber Units, pagers, cellular phones, personal digital assistants Digital Assistant (PDAs), smartphones, laptops, tablets, internet browsers computers, notebook computers, personal computers, wireless sensors, home appliances, Wearable devices such as smart watches or smart clothing, medical or electronic health devices devices, robots, industrial equipment, drones, cars, buses or trucks, trains, or This includes vehicles such as airplanes.

[0016] The communication system 100 may also include a base station 114a and a base station 114b. The base station 114a is connected to the core network 106 / 107 / 109 and the Internet 110. , network services 113, and / or other networks 112, etc. To facilitate access to the communication network, the WTRUs 102a, 102b, Any type configured to wirelessly interface with at least one of the 02c Examples of network services include V2X services. , ProSe services, IoT services, video streaming, edge computing The base station 114b may be connected to the core network 106 / 107 / 109. , the Internet 110, other networks 112, and / or network services To facilitate access to one or more communication networks, such as Remote radio heads) 118a, 118b, TRPs (transmitting / receiving points) 119a, 119b, and / or RSU (Road Side Unit) 120a and / or RSU (Road Side Unit) 120b ... Any type of device configured to interface wired and / or wirelessly The RRHs 118a and 118b can be connected to the core network 106 / 107 / 1 09, Internet 110, network services 113, and / or other networks WT to facilitate access to one or more communication networks, such as network 112. Any type configured to interface wirelessly with at least one RU102c The TRPs 119a and 119b can be devices of the core network 10. 6 / 107 / 109, Internet 110, Network Services 113, and / or or other networks 112. configured to wirelessly interface with at least one of the WTRUs 102d to The RSUs 120a and 120b can be any type of device. Network 106 / 107 / 109, Internet 110, Other Networks 11 2, and / or to one or more communication networks such as network services 113. For ease of access, at least one WTRU 102e or 102f and a wireless The device can be any type of device configured to interface with. The base stations 114a and 114b are wireless base station devices (Base Transceiver Stations: 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 The base station 114 may be an access point (AP), a wireless router, etc. Although each is illustrated as a single element, base stations 114a, 114b b may include any number of interconnected base stations and / or network elements. It will be understood that

[0017] The base station 114a may be part of the RAN 103 / 104 / 105, which may also In addition, the Base Station Controller (BSC), the wireless network controller, other base stations and relay nodes such as Radio Network Controller (RNC), The base station 114b may also include RA and / or other network elements (not shown). N103b / 104b / 105b, which can also be part of the base station controller other base stations, such as base station controllers (BSCs), radio network controllers (RNCs), and relay nodes. Base stations and / or network elements (not shown) may also be included. transmits and receives radio signals within a particular geographic area, which can be called a cell (not shown). The base station 114b may be configured to receive and / or transmit signals from a cell (not shown). Transmitting and receiving wired and / or wireless signals within a specific geographic area that can be called The cell may be further divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may, for example, In one embodiment, the base station 11 may include three transceivers, one for each sub-sub-sub-channel. 4a uses Multiple-Input Multiple Output (MIMO) technology Therefore, multiple transceivers can be used for each sector of a cell. Cut.

[0018] The base station 114a communicates with the WTRU 1 via the air interface 115 / 116 / 117. 102a, 102b, 102c, and may be connected to any suitable wireless communication link. (e.g., Radio Frequency (RF), Microwave, Infrared IR, ultraviolet (UV), visible light, centimeter waves, millimeter waves, etc.) The air interface 115 / 116 / 117 may be implemented using any suitable radio access technology. This can be established using the RAT technique.

[0019] The base station 114b receives signals via wired or air interfaces 115b / 116b / 117b. and RRH118a, 118b, TRP119a, 119b, and / or RSU1 20a, 120b, which may be communicated with one or more of the cable, optical fiber, etc.) or wireless communication links (e.g., radio frequency (RF) ), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter waves, millimeter waves, etc. The air interfaces 115b / 116b / 117b can be any suitable It can be established using a radio access technology (RAT).

[0020] RRH118a, 118b, TRP119a, 119b, and / or RSU120 a, 120b communicate with the WTRU via the air interface 115c / 116c / 117c. 102c, 102d, 102e, and 102f, which may be Any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR) , ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc. The interfaces 115c / 116c / 117c may use any suitable radio access technology (RAT). can be established using

[0021] WTRUs 102a, 102b, 102c, 102d, 102e, 102f, and / or or 102g for direct communication such as vehicle-to-vehicle (V2V) sidelink communication. can communicate with each other via a direct air interface 115d / 116d / 117d. WTRUs 102a, 102b, 102c, 102d, 102e, 102f, and and / or 102g may be used for direct communication, such as vehicle-to-infrastructure (V2I) sidelink communications. Network services via direct air interface 115e / 116e / 117e 113 (not shown), which may be communicated via any suitable wireless communication The link can be (e.g., radio frequency (RF), microwave, infrared (IR) , ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.) Air Interface 115d / 1 16d / 117d may be established using any suitable radio access technology (RAT). can be done.

[0022] More specifically, as noted above, communication system 100 is a multiple access system. It can be one or more of CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. The above channel access method can be adopted. For example, RAN103 / 104 / 1 05 and the base station 114a and the WTRU 102a, 102b, 102c, or the RA RRH118a, 118b, and TRP119a in N103b / 104b / 105b; 119b, and / or RSUs 120a, 120b and WTRUs 102c, 102 d, 102e, and 102f are Universal Mobile Telecommunications Systems (UMTSs). UMTS Terrestrial Radio Access It can implement wireless technologies such as Wideband CDMA (Wideband CDMA), DMA:WCDMA) using 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 Evolved High-Speed ​​Packet It can include communication protocols such as HSPA (Evolved HSPA: HSPA+). SPA stands for High-Speed ​​Downlink Packet Access HSDPA and / or High-Speed ​​Uplink Packet Access Packet Access (HSUPA).

[0023] In one embodiment, the base station 114a and the WTR in the RAN 103 / 104 / 105 In U102a, 102b, 102c or RAN103b / 104b / 105b RRH118a, 118b, TRP119a, 119b, and / or RSU120 a, 120b and WTRUs 102c, 102d are Evolved UMTS Terrestrial Radio Access ( Evolved UMTS Terrestrial Radio Access (E-UTRA) and other wireless technologies are implemented. Long Term Evolution (LTE) and and / or LTE-Advanced (LTE-A) over the air interface. Establishing the base stations 115 / 116 / 117 or 115c / 116c / 117c respectively Air interface 115 / 116 / 117 or 115c / 116c / 1 17c can implement 3GPP NR technology. LTE and LTE-A technologies LTE D2D and V2X technologies and interfaces (e.g., sidelink communication) 3GPP NR technology includes NR V2X technology and interfaces (sidelink communication). This includes information such as trust.

[0024] In one embodiment, the base station 114a in the RAN 103 / 104 / 105 and the WT In RU102a, 102b, 102c or RAN103b / 104b / 105b RRH118a, 118b, TRP119a, 119b, and / or RSU120 a, 120b and WTRUs 102c, 102d, 102e, and 102f are IEEE80 2.16 (e.g., 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 may be implemented.

[0025] The base station 114c in FIG. 1A may be, for example, a wireless router, a Home NodeB, or a Home eNodeB. or access point, can be a business, home, vehicle, train, air, satellite, Any suitable RAID controller to facilitate wireless connectivity in a localized area such as a factory, campus, etc. In one embodiment, the base station 114c and the WTRU 102e Wireless Local Area Network (WLAN) To establish this, wireless technology such as IEEE 802.11 can be implemented. In this embodiment, the base station 114c and the WTRU 102d form a wireless personal area network. In order to establish a Wireless Personal Area Network (WPAN), In yet another embodiment, the base station 11 may implement a wireless technology such as IEEE 802.15. 4c and the WTRU 102e can be used with cellular -based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE- As shown in FIG. 1A, the base station 114c can utilize the Internet. The base station 114c may have a direct connection to the internet 110. Access to the Internet 110 via the core network 106 / 107 / 109 It may not be necessary.

[0026] RAN103 / 104 / 105 and / or RAN103b / 104b / 105b , can communicate with the core network 106 / 107 / 109, and this network , voice, data, messaging, authorization and authentication, applications, and / or Voice Over Internet Protocol (VoI) P) service to one of the WTRUs 102a, 102b, 102c, 102d, and 102f. The network can be any type of network configured to provide one or more For example, the core network 106 / 107 / 109 provides call control, billing services, mobile location services, and Prepaid calling, Internet connectivity, packet data network It can provide network connectivity, Ethernet connectivity, video distribution, etc. It can be used to 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 and Communicate directly or indirectly with other RANs employing the same or different RATs. It will be understood that this may be achieved by utilizing, for example, E-UTRA radio technology. RAN103 / 104 / 105 and / or RAN103b / 104b / 1 In addition to being connected to 05b, the core network 106 / 107 / 109 also , capable of communicating with another RAN (not shown) employing GSM or NR radio technology. Cut.

[0028] The core network 106 / 107 / 109 also includes the WTRUs 102a, 102b, 10 2c, 102d, 102e, and 102f are connected to the PSTN 108, the Internet 110, and / or act as a gateway to access other networks 112. PSTN108 stands for Plain Old Telephone Service. The Internet 110 may include a circuit-switched telephone network providing a Power On / Off Service (POTS). , Transmission Control Protocol in the TCP / IP Internet Protocol Suite Transmission Control Protocol (TCP), User Datagram Protocol (UDP) UDP (Internet Protocol), IP (Internet Protocol), etc. Interconnected computer networks and devices that use a common communication protocol Other networks 112 may include a global system of other services. Wired or wireless communications networks owned and / or operated by a service provider For example, the network 112 may include any type of packet data. A network (e.g., an IEEE 802.3 Ethernet network) or more than one RAN103 / Same RAT as 104 / 105 and / or RAN103b / 104b / 105b or Different RATs can be employed.

[0029] WTRUs 102a, 102b, 102c, 102d, 10 2e, and some or all of 102f may include multimode capabilities, e.g. , WTRUs 102a, 102b, 102c, 102d, 102e, and 102f are different a plurality of transceivers for communicating with different wireless networks via different wireless links; For example, the WTRU 102g shown in FIG. 1A may include a cellular-based wireless technology and a base station 114a that can employ IEEE802 wireless technology. The base station 114c may be configured to communicate with the base station 114a.

[0030] Although not shown in FIG. 1A, the user equipment may have a wired connection to the gateway. It will be understood that the gateway may be a residential gateway. The RG can be a Relay Gateway (RG). Many of the ideas contained herein can be applied to W Applies equally to UEs that are TRUs and UEs that connect to the network using a wired connection It will be appreciated that the wireless interface 115, 1 The idea applies to 16, 117 and 115c / 116c / 117c, but for wired connections can be applied in the same way.

[0031] FIG. 1B illustrates a wireless WTRU 102 according to an embodiment illustrated herein. FIG. 1B is a block diagram of an exemplary apparatus or device configured for communication. Thus, the exemplary WTRU 102 includes a processor 118, a transceiver 120, and transmit and receive elements. 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) chip set The WTRU 102 may include a wireless LAN controller 136, a wireless LAN controller 138, and other peripherals 138. In one embodiment, the WTRU 102 Consistent with the form, it may include any subcombination of the aforementioned elements. It will be appreciated that the embodiment may also include base stations 114a and 114b, etc. and / or the nodes that base stations 114a and 114b may represent, e.g. Including but not limited to Base Station Equipment (BTS), Node B, Site Controller, Access Access Point (AP), Home Node B, Evolved Node B (eNodeB), Home Evolved Node B (HeNB), Home evolved Node B Gateway, Next Generation Node B (gNod eB) and proxy nodes, etc., are particularly shown in FIG. 1B and described herein. It is intended that some or all of the elements may be included.

[0032] The processor 118 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital Digital Signal Processor (DSP), multiple microprocessors, One or more microprocessors, controllers, or microcontrollers associated with a DSP core controller, Application Specific Integrated Circuit (ASIC) ), Field Programmable Gate Array (FP GA circuits, other types of integrated circuits (ICs), state machines The processor 118 may be a processor for signal coding, data processing, power control, Input / output processing and / or any other function that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to a transceiver 120. The transceiver may be coupled to the transmit / receive element 122. does not illustrate the processor 118 and the transceiver 120 as separate components. However, the processor 118 and transceiver 120 may be integrated into an electronic package or chip. It will be appreciated that the above-mentioned methods can be integrated together.

[0033] The transmit / receive element 122 of the UE communicates with the base station via the air interface 115 / 116 / 117. between stations (e.g., base station 114a) or over air interface 115d / 116d / 117d to transmit or receive signals to or from another UE For example, in one embodiment, the transmit / receive element 122 can transmit and / or receive RF signals. can be an antenna configured to receive. 122 may be configured to transmit and / or receive, for example, IR, UV, or visible light signals. Furthermore, in one embodiment, the transmitting and receiving elements may be configured as emitters / detectors. The transmitter 122 can be configured to transmit and receive both RF and optical signals. The receiving element 122 may transmit and / or receive any combination of wireless or wired signals. It will be appreciated that the present invention may be configured to

[0034] Furthermore, although the transmit / receive element 122 is illustrated as a single element in FIG. 1B, the WTRU 1 WTRU1 may include any number of transmit / receive elements 122. More specifically, WTRU1 02 may employ MIMO technology. 102 transmits and receives wireless signals via the air interface 115 / 116 / 117. The transmitter / receiver may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving signals.

[0035] The transceiver 120 modulates and transmits / receives signals to be transmitted by the transmit / receive element 122. The receiver element 122 may be configured to demodulate the signal received by the receiver element 122. The WTRU 102 may have multi-mode capabilities. The receiver 120 may be configured to allow the WTRU 102 to communicate with multiple RATs, e.g., NR and IEEE 802.11. or communicating with NR via E-UTRA, or different RRHs, TRPs, and RSUs or to allow nodes to communicate over the same RAT via multiple beams. , may include multiple transceivers.

[0036] The processor 118 of the WTRU 102 controls the speaker / microphone 124, the keypad 126, and / or a display / touchpad / indicator 128 (e.g., liquid crystal display). Liquid Crystal Display (LCD) display unit or Organic Light-Emitting Diode (OLED) display unit and can receive user input data from them. The sensor 118 also includes a speaker / microphone 124, a keypad 126, and / or , and can output user data to the display / touchpad / indicator 128. Additionally, the processor 118 may include non-removable memory 130 and / or removable memory. Access information from any type of suitable memory, such as bubble memory 132, and store it in memory. The non-removable memory 130 can store data. Random-Access Memory (RAM), Read-Only Memory (R OM), hard disk, or any other type of memory storage device. The removable memory 132 can store a subscriber identity module (SIM). SIM (Smart Card Module) cards, memory sticks, Secure Digital (Secure Digital In one embodiment, the processor 118 may include a cloud storage device (e.g., a storage device such as a cloud storage device ... Servers hosted on cloud or edge computing platforms or on a home computer (not shown) that is physically located on the WTRU 102. It can access information from and store data in memory that is not available.

[0037] The processor 118 receives power from a power supply 134 and operates in conjunction with the other components within the WTRU 102. The power supply 134 may be configured to distribute and / or control power to the power supply components. may be any suitable device for providing power to the WTRU 102. For example, the power source 134 may include one or more dry batteries, solar cells, fuel cells, etc. .

[0038] The processor 118 may also be coupled to a GPS chipset 136. The chipset 136 stores location information (e.g., longitude and The GPS chipset 136 can be configured to provide information on the location of the satellite (e.g., latitude). Additionally or alternatively, the WTRU 102 may communicate with a base station (e.g., base station 114a, 114b) via the air interface 115 / 116 / 117 and / or timing of signals being received from two or more nearby base stations. The WTRU 102 can determine its location based on the Location information can be obtained by any suitable location determination method while maintaining consistency. It will be understood that

[0039] The processor 118 may further be coupled to other peripherals 138, Peripheral devices 138 may provide additional features, functionality, or wired and / or wireless connectivity. The system may include one or more software and / or hardware modules. For example, the peripherals 138 may include various sensors such as accelerometers, biometrics (e.g., Fingerprint) sensors, electronic compasses, satellite transceivers, digital cameras (for photos or videos) ), Universal Serial Bus (USB) port or other compatible Interconnection interface, vibration device, television transceiver, hands-free headset , Bluetooth (registered trademark) module, Frequency Modulated (F M) Wireless units, digital music players, media players, video game players This may include a module, an internet browser, etc.

[0040] The WTRU102 is ideal for sensors, home appliances, smart watches, smart wear, and other applications. Wearable devices, medical or electronic health devices, robots, industrial equipment, drones , within other apparatus or devices, such as vehicles, such as automobiles, trucks, trains, or airplanes The WTRU 102 may comprise one of the peripheral devices 138. such interconnection interfaces through one or more interconnection interfaces, Connect to other components, modules, or systems of such equipment or devices. It is possible.

[0041] FIG. 1C is a system diagram of the RAN 103 and core network 106 according to an embodiment. As described above, the RAN 103 communicates with the WTRU 10 via the air interface 115. 2a, 102b, and 102c. The RAN 103 can also communicate with the core network 106. As shown, the RAN 103 may include Node Bs 140a, 140b, and 140c. These communicate with the WTRUs 102a, 102b via the air interface 115, respectively. , 102c. Each of 140a, 140b, and 140c is associated with a particular cell (not shown) within the RAN 103. The RAN 103 may also include RNCs 142a and 142b. Consistent with an embodiment, the RAN 103 may include any number of Node Bs and RANs. It will be understood that NC may be included.

[0042] As shown in FIG. 1C, Node Bs 140a, 140b communicate with an RNC 142a. Additionally, Node B 140c can communicate with RNC 142b. The RNs 140a, 140b, and 140c communicate with each other via the Iub interface. RNCs 142a and 142b can communicate with Iur Internet. The RNCs 142a and 142b can communicate with each other via the RNC interface. It controls each Node B 140a, 140b, 140c to which it is connected. Furthermore, each of the RNCs 142a and 142b can be configured to Loop power control, load control, admission control, packet scheduling, handover Performs other functionality such as control, macro diversity, security functions, data encryption, etc. or can be configured to support it.

[0043] The core network 106 shown in FIG. 1C includes 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 Suppo Each of the above elements may include a core network 1 Although illustrated as part of 06, any one of these elements may be part of the core network. You understand that the Service may be owned and / or operated by an entity other than the Company. It will be done.

[0044] RNC 142a in RAN 103 communicates with the core network via the IuCS interface. The MSC 146 can be connected to the MGW 144. The MSC 146 and the MGW 144 can be connected to the WTRUs 102a, 102b, and 102c. b, 102c, providing access to a circuit-switched network such as the PSTN 108; Facilitates communication between the WTRUs 102a, 102b, 102c and traditional landline communication devices It can be made into.

[0045] RNC 142a in RAN 103 also communicates with the core network via the IuPS interface. The SGSN 148 can be connected to the GGS 148 in the network 106. The SGSN 148 and the GGSN 150 can be connected to the WTRU 1 102a, 102b, and 102c, a packet-switched network such as the Internet 110; provides access to the WTRUs 102a, 102b, and 102c and IP-enabled devices. This can facilitate communication between

[0046] As noted above, the core network 106 may also be owned by other service providers. and / or other wired or wireless networks operated by It can be connected to a network 112 .

[0047] FIG. 1D is a system diagram of the RAN 104 and core network 107 according to an embodiment. As described above, the RAN 104 communicates with the WTRU 10 via the air interface 116. 2a, 102b, and 102c. The RAN 104 may also be in communication with a core network 107.

[0048] The RAN 104 may include eNodeBs 160a, 160b, and 160c, but may also include R The AN 104 may include any number of eNodeBs while remaining consistent with an embodiment. It will be understood that the eNodeBs 160a, 160b, and 160c can each , and communicates with the WTRUs 102a, 102b, and 102c via the air interface 116. In one embodiment, the eNodeB 16 may include one or more transceivers for transmitting the 0a, 160b, and 160c can implement MIMO technology. The WTRU 102a may transmit wireless signals to the WTRU 102a using, for example, multiple antennas. It is capable of transmitting and receiving wireless signals from the WTRU 102a.

[0049] Each of the eNodeBs 160a, 160b, and 160c serves a particular cell (not shown). ) and can be associated with radio resource management decisions, handover decisions, uplink and / or configured to handle scheduling of users in the downlink, etc. As shown in FIG. 1D, the eNodeBs 160a, 160b, and 160c , can communicate with each other via the X2 interface.

[0050] The core network 107 shown in FIG. 1D includes a mobility management gateway (Mobility Management Gateway). Management Gateway (MME) 162, Serving Gateway 164, and Packet Including a Packet Data Network (PDN) Gateway 166 Although each of the aforementioned elements is illustrated as part of the core network 107, Any one of these elements may be owned by an entity other than the core network operator. and / or operated by the company.

[0051] The MME 162 communicates with the eNodeB 160a in the RAN 104 via the S1 interface. , 160b, and 160c, which can be connected to each of the For example, the MME 162 may Authentication of users, activation / deactivation of bearers, WTRUs 102a, 102b, 1 It can be responsible for selecting a specific serving gateway during the initial connection of 02c. The MME 162 also communicates with the RAN 104 and other wireless technologies such as GSM or WCDMA. Provides control plane functionality for switching between other RANs (not shown) that are employed. This can be done.

[0052] The serving gateway 164 communicates with the e within the RAN 104 via the S1 interface. Each of the nodes B 160a, 160b, and 160c can be connected to the server. The Bing gateway 164 generally communicates between the WTRUs 102a, 102b, and 102c. It is capable of routing and forwarding user data packets. The gateway 164 also anchors the user plane during eNodeB handover. and when downlink data is available at the WTRUs 102a, 102b, and 102c, triggering alerts, managing the context of the WTRUs 102a, 102b, and 102c. It may perform other functions such as managing and storing the data.

[0053] The serving gateway 164 can also connect to a PDN gateway 166. This allows the WTRUs 102a, 102b, 102c to access the Internet 110 or other providing access to a packet-switched network to allow the WTRUs 102a, 102b, 102c c and IP-enabled devices.

[0054] The core network 107 may facilitate communication with other networks. For example, the core network 107 may provide the WTRUs 102a, 102b, and 102c with a PSTN 108 to provide access to a circuit-switched network, such as the WTRUs 102a, 102 b, 102c, and conventional landline communication devices. For example, the core network 107 may be configured to provide a IP gateways (e.g., IP multimedia subsystems) that act as interfaces to It may include or contain an IP Multimedia Subsystem (IMS) server. Furthermore, the core network 107 can communicate with the WTRUs 102a, 102b, and 2b, 102c, and other services owned and / or operated by other service providers. providing access to a network 112, which may be a wired or wireless network; It can be provided.

[0055] FIG. 1E is a system diagram of the RAN 105 and core network 109 according to an embodiment. The RAN 105 communicates with the WTRUs 102a and 102b via an air interface 117. 2b. The RAN 105 may also employ NR radio technology. The N3IWF 199 can communicate with the air interface network 109. Employing non-3GPP radio technology to communicate with the WTRU 102c via the wireless LAN 198 The N3IWF 199 can also communicate with the core network 109. .

[0056] The RAN 105 may include eNodeBs 180a and 180b. 05 may include any number of gNodeBs while remaining consistent with an embodiment. It will be understood that the g Node Bs 180a and 180b each have an air interface. one or more WTRUs 102a and 102b for communicating with the WTRUs 102a and 102b via the interface 117. A combined access and backhaul connection may be used. In one embodiment, the same air interface is used between the WTRU and the gNode B. This can be a core network 109 via one or more gNBs. In one embodiment, the g Node Bs 180a and 180b can support MIMO, MU -MIMO and / or digital beamforming technology may be implemented. Thus, the g Node B 180a may, for example, use multiple antennas to The WTRU 102a may transmit wireless signals to and receive wireless signals from the WTRU 102a. It is understood that the RAN 105 may employ other types of base stations, such as eNodeB. It should also be understood that the RAN 105 may employ more than one type of base station. For example, the RAN may have eNodeB and gNodeB can be adopted.

[0057] The N3IWF 199 may include non-3GPP access points 180c, but may not include N The 3IWF 199 may be configured to handle any number of non-3GPP access points while remaining consistent with one embodiment. It will be understood that the non-3GPP access point 1 may include a non-3GPP access point. 80c includes one or more WTRUs for communicating with the WTRU 102c over the air interface 198. In one embodiment, the non-3GPP access point 1 80c communicates with the WT over the air interface 198 using the 802.11 protocol. It is possible to communicate with RU102c.

[0058] Each of the gNodeBs 180a and 180b is associated with a particular cell (not shown). radio resource management decisions, handover decisions, uplink and / or can be configured to handle user scheduling in the downlink, etc. As shown in FIG. 1E, g-node Bs 180a and 180b can be connected to the Xn interface. They can communicate with each other via the

[0059] The core network 109 shown in FIG. 1E is a 5G Core Network 5GC is a system that connects networks to each other via a radio access network. It will be possible to provide a wide range of communication services to connected customers. The network 109 consists of a number of entities that perform the functionality of the core network. When used in the specification, "core network entity" or "network function" The term refers to any entity that performs one or more functions of the core network. Such core network entities may include: A device or computer system configured for wireless and / or network communications The software stored in the system's memory and running on the processor (i.e., It is understood that the program may be a logical entity implemented in the form of executable instructions. can be.

[0060] As shown in FIG. 1E, the 5G core network 109 provides access and mobility management Function (Access and Mobility Management Function: AMF) 172, Session Management Session Management Function (SMF) 174, User Plane Function (User Plane Function (UPF) 176a and 176b, User Data Management Function (User D Data Management Function (UDM) 197, Authentication Server Function (Authentication Server r Function:AUSF)190, Network Exposure Function NEF (196), Policy Control Function (PCF) (184) , Non-3GPP Interworking Function (N3IWF) ) 199, Application Function (AF) 188, User Data Each of the aforementioned may include a User Data Repository (UDR) 178. Although the elements are illustrated as part of the 5G Core Network 109, any of these elements may one of which is owned and / or operated by an entity other than the core network operator It will be understood that the 5G core network will be able to operate It does not have to be made up of all of these elements, but can be made up of additional elements, It should also be understood that the diagram may be comprised of multiple instances of each element. 1E shows that network functions are directly connected to each other, but the diameter routing communicate through a routing agent such as a messaging agent or message bus. It should be understood that the connections between network functions may be the same. It indicates that the network is achieved through a set of related interfaces or reference points. Network functions may be invoked or may be modeled, described, or implemented as a set of services that are called It should be understood that calls to network function services are via direct connection, message exchange on a message bus, or software function calls. This can be achieved by:

[0061] The AMF172 can be connected to the RAN105 via the N2 interface and For example, the AMF 172 can perform registration management, connection management, It can be responsible for reachability management, access authentication, and access authorization. Transfers the tunnel configuration information of the plane to the RAN 105 via the N2 interface. The AMF172 can be used to transmit SMF signals via the N11 interface. AMF 172 can receive user plane tunnel configuration information from Specifically, the NA is transmitted between the WTRUs 102a, 102b, and 102c via the N1 interface. The N1 interface can route and forward packets. is not shown.

[0062] The SMF174 can be connected to the AMF172 via the N11 interface, It can be connected to the PCF184 through the N7 interface, and the N4 interface The SMF 174 can be connected to the UPF 176 via the SMF 174. The SMF 174 functions as a control node. For example, the SMF 174 can manage session management, WTRUs 102a and 102b, and b, IP address allocation for 102c, UPF176a and UPF176b Manage and configure traffic steering rules in AMF172 The UE may be responsible for generating downlink data notifications.

[0063] UPF176a and UPF176b are used for WTRU102a, 102b, and 102c. to a packet data network (DN) such as the Internet 110 provides access to communicate between the WTRUs 102a, 102b, 102c and other devices UPF176a and UPF176b can also facilitate WTRU1 02a, 102b, 102c, access to other types of packet data networks For example, the other network 112 may be an Ethernet network. It can be any type of network that exchanges data or packets of data. The UPF176a and UPF176b are connected to the SMF174 via the N4 interface. Traffic steering rules can be received. UPF176a and UPF 176b by connecting the packet data network at the N6 interface. or by connecting with other UPFs at the N9 interface, can provide access to packet data networks. In addition to providing the necessary security, the UPF176 also provides packet routing and forwarding, policing, and Enforcement of sea rules, handling quality of service for user plane traffic, downtime It can handle the buffering of link packets.

[0064] The AMF172 can also be connected to the N3IWF199 via the N2 interface. N3IWF can communicate over air interface technologies not defined by 3GPP. The AMF facilitates connectivity between the WTRU 102c and the 5G core network 170. It interacts with N3IWF199 in the same or similar way as it interacts with RAN105. It can work.

[0065] The PCF184 is connected to the SMF174 via the N7 interface and the N15 interface. It is connected to the AMF172 via the N5 interface and to the application The N15 and N5 interfaces can be connected to the Autonomous Function (AF) 188. PCF184 is not shown in Figure 1E. It provides policy rules to the control plane nodes and the control plane nodes enforce these rules. The PCF184 allows the AMF to communicate over the N1 interface. to distribute policies to the WTRUs 102a, 102b, and 102c. 2a, 102b, and 102c to the AMF 172. The policy is then enforced or applied at the WTRUs 102a, 102b, and 102c. It is possible.

[0066] The UDR 178 serves as a repository of authentication credentials and subscription information. UDRs allow network functions to add to, read from, and modify data in the repository. It can be connected to a network function so that it can be used. For example, UDR1 78 can be connected to PCF184 via N36 interface, UDR17 8 can be connected to the NEF196 through the N37 interface, UDR178 can be connected to the UDM197 via the N35 interface.

[0067] The UDM197 acts as an interface between the UDR178 and other network functions. The UDM 197 can authorize the UDR 178 to access the network functions. For example, the UDM197 can be connected to the AMF17 via the N8 interface. 2, UDM197 can be connected to SMF174 through N10 interface The UDM197 can be connected to the AUSF190 via the N13 interface. The UDR178 and UDM197 can be tightly integrated. .

[0068] The AUSF190 performs authentication-related operations and communicates with the UDM1 through the N13 interface. 78 and connects to AMF172 via the N12 interface.

[0069] The NEF196 will identify capabilities and services within the 5G Core Network109 as The information is published to the application function 188. The publication is done on the N33 API interface. NEF can connect to AF188 via N33 interface, to other network functions to expose the capabilities and services of the network. can be connected.

[0070] The application functions 188 correspond to the network functions of the 5G core network 109. Interaction between application functions 188 and network functions. Actions can occur through a direct interface or through the NEF196. The application function 188 can be part of the 5G core network 109. or outside the 5G core network 109 and can be considered as a mobile network It can be deployed by companies that have business relationships with work operators.

[0071] Network slicing is a technology that allows mobile network operators to It can be used to support one or more "virtual" core networks behind an interface. This is a mechanism for "sliding" a core network into one or more virtual networks. "issuing" different services running across different RANs or a single RAN Network slicing allows operators to: Various market scenarios with diverse requirements for functionality, performance, and isolation Creating a customized network to provide the best solution for Rio can.

[0072] 3GPP is developing the 5G core network based on the concept of network slicing. Network slicing is designed to allow network operators to manage highly diverse and time-varying networks. A diverse set of 5G use cases (e.g., Massive IoT) will place extreme demands on , Critical Communications, V2X, and Enhanced Mobile Broadband) Network Slicing is a great tool that can be used to support Without technology, each use case cannot meet a specific set of performance, scalability, and availability requirements. If there are usability requirements, the network architecture should be able to accommodate a wider range of use cases. may not be flexible and scalable enough to be efficiently supported. The introduction of new network services should be done more efficiently.

[0073] In a network slicing scenario, the WTRUs 102a, 102b, and 102c It can be connected to the AMF 172 via the N1 interface. The AMF is a logical An AMF can be part of one or more slices. An AMF can be part of one or more UPFs (single or multiple). (Single or Multiple) 176, SMF(s) 174, and other network functions, UPF(s) 176, which may coordinate connections or communications with WTRUs; Each of the SMF(s) 174, and other network functions, They can be different slices or parts of the same slice. When they are part of a network, they share different computing resources, security credentials, and They can be separated from each other in the sense that they can use other services such as virtual currency.

[0074] The 5G core network 109 can facilitate communication with other networks For example, the 5G core network 109 is a network that connects the 5G core network 109 and the PSTN 10 IP gateways (e.g., IP multimedia gateways) that act as interfaces between the It may contain or communicate with an Internet Management System (IMS) server. For example, the core network 109 may facilitate communication via short message service. Short Message Service (SMS) service center that For example, the 5G Core Network may include or be in communication with a The network 109 includes the WTRUs 102a, 102b, and 102c and the server or application It can facilitate the exchange of non-IP data packets between the application function 188 and the , the core network 170 may provide other services to the WTRUs 102a, 102b, and 102c. other wired or wireless networks owned and / or operated by the provider. 112, which may include:

[0075] The core network described herein and shown in Figures 1A, 1C, 1D, and 1E Network entities are required to comply with the requirements of the specific existing 3GPP specifications for those entities. Although these entities and functionality are identified by their respective names, in the future, these entities and functionality may be identified by other names. and specific entities or functions may be identified in future 3GPP NR specifications. It is understood that this specification can be combined with future specifications published by 3GPP, including Therefore, the structures described and shown in Figures 1A, 1B, 1C, 1D, and 1E are The specific network entities and functionality are provided as examples only and may not be used in conjunction with this The subject matter disclosed and claimed in the specification is either currently defined or will be defined in the future. It is understood that the present invention may be embodied or implemented in any similar communication system, regardless of whether it is a It is understood.

[0076] FIG. 1F is a block diagram of an exemplary computing system 90. One or more devices of the communication network shown in FIGS. 1A, 1C, 1D, and 1E RAN103 / 104 / 105, Core Network 106 / 107 / 109, PSTN1 08, Internet 110, other networks 112, or network services The present invention may be embodied as a specific node or functional entity in the service 113. The computing system 90 is composed of a computer or server, and is primarily The computer-readable instructions may be software. or wherever such software is stored. Such computer readable instructions may be accessed by any means. , which execute within the processor 91 to cause the computing system 90 to perform operations. The processor 91 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital processor, or a Digital Signal Processors (DSPs), multiple microprocessors, and one associated DSP core More than one microprocessor, controller, microcontroller, application specific integrated circuit circuits (ASIC), field programmable gate array (FPGA) circuits, and other The processor 91 can be any type of integrated circuit (IC), state machine, etc. , signal coding, data processing, power control, input / output processing, and / or computing Any other functionality that enables the operating system 90 to operate in a telecommunications network. The coprocessor 81 can execute different options from the main processor 91. processor and may perform additional functions or assist processor 91. The processor 91 and / or co-processor 81 may implement the methods and The device may receive, generate, and process data related to the device.

[0077] In operation, processor 91 fetches, decodes, and executes instructions to perform computing tasks. with other resources via the system bus 80, which is the main data transfer path for the operating system. Such a system bus transfers information between the computers in the computing system 90. The system bus 80 connects the components and defines the medium for data exchange. In other words, there is a data line for sending data and an address line for sending addresses. It also includes control lines for sending interrupts and for operating the system bus. An example of such a system bus 80 is a Peripheral Component Interconnect (Pe PCI bus.

[0078] The memory coupled to the system bus 80 is a random access memory (RAM). RAM 82 and ROM 93 Such memories include circuits that can store and retrieve information. RAM 82 generally contains stored data that cannot be easily altered. , which may be read by the processor 91 or other hardware device, or Access to RAM 82 and / or ROM 93 can be changed by the memory controller. The memory controller 92 controls the execution of the instructions. It is possible to provide an address translation function that converts virtual addresses into physical addresses when The memory controller 92 also separates processes within the system, allowing user processes It can provide memory protection that isolates system processes from other processes. A program running in the first mode is mapped by the virtual address space of the process. Only mapped memory can be accessed, and memory sharing between processes is configured. Unless a process is configured to access memory in the virtual address space of another process, it cannot do not have.

[0079] Additionally, the computing system 90 may transmit instructions from the processor 91 to the printer 9 4, to communicate with peripherals such as keyboard 84, mouse 95, and disk drive 85. The device may include a peripheral controller 83 responsible for:

[0080] The display 86 controlled by the display controller 96 is It is used to display the visual output generated by the operating system 90. Such visual output includes text, graphics, animated graphics, and The visual output may include a graphical user interface (Graphi The display 86 may be provided in the form of a graphical user interface (GUI). CRT-based video displays, LCD-based flat panel displays, gas It can be implemented in plasma-based flat panel displays or touch panels. The display controller 96 generates the video signal that is sent to the display 86. Contains the electronic components necessary to complete the

[0081] Furthermore, the computing system 90 may be configured as shown in FIGS. 1A, 1B, 1C, 1D, RAN 103 / 104 / 105, Core Network 106 / 107 / 10 9, PSTN 108, Internet 110, WTRU 102, or other network The computing system may be connected to an external communication network or device, such as a 90, and the computing system 90 is used to connect those networks. This may enable communication with other nodes or functional entities in the network, e.g. It may include communications circuitry such as a wireless or wired network adapter 97. may be used alone or in combination with processor 91 to implement the specific devices described herein. may be used to perform transmitting and receiving steps of a device, node, or functional entity. can.

[0082] FIG. 1G illustrates a system in which the methods and apparatus described and claimed herein may be incorporated. 1 illustrates an embodiment of an exemplary communication system 111. As shown, the exemplary communication The system 111 includes wireless transmit / receive units (WTRUs) A, B, C, D, E, and F, a base station g The V2X server 124 includes the NB 121, the V2X server 124, and the RSUs 123a and 123b. However, the disclosed embodiments may be implemented with any number of WTRUs, base stations gNBs, and V2X networks. It will be understood that the term "network" contemplates a network and / or network element. One or some or all of WTRUs A, B, C, D, E may be part of the access network. WTRUs A, B, and C can be outside the V2X group coverage 122. They form a group, with WTRU A as the group lead, WTRU B and WTRUs A, B, C, D, E, and F are group members. via Uu interface 129a / 129b when under network coverage. under or outside the access network coverage In this case, the sidelink (PC5 or NR PC5) interface 125a is used. WTRUs A, B, C, D, E, and F can communicate between the vehicle and the network. Network communication (V2N) interface 126 or side link interface 125 b. WTRUs A, B, C, D, E, and F can communicate with the RSU via via a V2I interface 127, a V2X server 124. WTRUs A, B, C, D, E, and F can communicate with vehicle-to-person communications ( communicating with another UE via a Vehicle-to-Person (V2P) interface 128; can be done.

[0083] Any or all of the devices, systems, methods, and processes described herein The computer-executable instructions (e.g., programs) stored on a computer-readable storage medium The instructions may be embodied in the form of program code, which may be transmitted to the processor 118 or 9. When executed by a processor, such as a processor 1, the processor is configured to implement the system described herein. It is understood that the systems, methods, and processes are performed and / or caused to be performed. Any of the steps, operations, or functions described herein may be implemented using wireless and / or or a device or computing system configured for wired network communication. Implemented in the form of such computer-executable instructions executed on a processor of the system. A computer-readable storage medium may be any non-transitory (e.g., Volatile and non-volatile, implemented in any tangible or physical (e.g., tangible or physical) method or technology, Such computer-readable storage media includes removable and non-removable media. The computer-readable storage medium does not include a RAM, a ROM, an EEPROM, Flash memory or other memory technologies, CD-ROM, Digital Versatile Disk (DV) Digital Versatile Disk (DVD) or other optical disk storage, magnetic cassette, Magnetic tape, magnetic disk storage or other magnetic storage device, or It is used to store desired information and to access it by a computing system. This includes, but is not limited to, any other tangible or physical medium capable of transmitting the information.

[0084] (Connection Management in LTE D2D Sidelink) (One-to-many ProSe direct communication) ProSe, especially in LTE D2D sidelink communication, is a one-to-many ProSe direct communication. Faith has the following characteristics: One-to-many ProSe direct communication is connectionless. Therefore, PC5 control player There is no signaling through the network. The radio layer is a user layer for transmitting IP packets between UEs that are directly involved in the communication. Provides plain communication services. Group members share a secret from which they derive a group security key, All user data for that group can be encrypted. One-to-many ProSe direct communication is authorized by the ProSe function using the PC3 reference point. It is configured in the UE. ProSe UE configuration parameters (e.g., ProSe group IP multicast address) Address, ProSe group ID, group security material, transmitting and receiving radio related parameters) are configured in the UE.

[0085] (One-to-one ProSe direct communication) One-to-one ProSe direct communication is connection-oriented and secure over PC5 between two UEs. This is achieved by establishing a Layer 2 link. The control plane for establishing, maintaining, and releasing physical connections is shown in Figure 2. Please note that the PC5 and Sidelink interfaces are used interchangeably. I want to be done that.

[0086] Each UE (e.g., UE A and UE B in Figure 2) has a layer for unicast communication. It has a Layer 2 ID, which identifies all the packets it sends on the Layer 2 link. The Source Layer 2 ID field of all frames and Included in the destination Layer 2 ID of all frames received on the Conflicts between destination Layer 2 IDs for point-to-multipoint communications are resolved by RAN WG2. ensure that Layer 2 IDs for unicast communication are at least locally unique We need to be sure.

[0087] The Layer 2 link for one-to-one ProSe direct communication is based on the Layer 2 IDs of the two UEs. This means that UEs can identify each other using the same Layer 2 ID. ProSe means that multiple Layer 2 links can be involved for direct communication. do.

[0088] In ProSe, as shown in Figure 3, PC5-S signaling is used for connection management and It is designed for security management. In FIG. 3, in step S302, the UE 1 sends a direct communication request to UE2. In step S304, authentication and security Establish a tier association.

[0089] Connection management procedures include PC5 link setup, link maintenance using keep-alive functions, Security management includes PC5 security mode control. Includes procedures and (re)keying procedures.

[0090] PC5-S does not allow setting of AS layer parameters except for security parameters. RRC currently requires PC5 AS configuration to support sidelink communication. It should be noted that RRC is not used for sidelink broadcasts. Sidelink Broadcast Control Channel (SBCCH) via the control channel It is used only to broadcast link-generic configuration parameters.

[0091] (QoS support in ProSe) QoS control is packet-based QoS. When the PC5 access layer (above) passes a protocol data unit to the PC5 access layer, the Pro The Se upper layer assigns a per-Prose packet priority (ProSe) from a range of eight possible values. Per-Packet Priority (PPPP), and Prose packet priority from a range of eight possible values. Providing per-packet reliability (PPPR). and PPPR are independent of the destination Layer 2 ID and are compatible with one-to-one and one-to-many ProS PPPP and PPPR are both applied to the application layer. The priority value for each Prose packet is assigned to the PC5-S message. The UE has one PC5-S message that can be used to send any of the messages. A priority value is set for each Prose packet. PPPP and PPPR are the modes in which UEs access the medium, i.e., schedules. The IEEE 802.11b standard is neutral to whether the IEEE 802.11b standard uses loop or autonomous transmission modes.

[0092] The ProSe access layer associates protocol data units received from higher layers with The priority of each Prose packet received is used to differentiate between other intra-UE transmissions (i.e., Protocol data units associated with different priorities waiting for transmission in the UE) and and UE-to-UE transmissions (i.e., transmissions associated with different priorities waiting for transmission in different UEs). Prioritizes transmission of the received protocol data units (protocol data units). The ProSe access layer associates protocol data units received from higher layers with Use the provided PPPR to determine and adjust transmission behavior, or for example packet duplication. .

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

[0094] As mentioned above, one-to-many ProSe communication over the PC5 interface is connectionless. It is a service that does not have a specific intended receiver. Therefore, it is not possible to control the receiver or wirelessly No configuration is required depending on the protocol stack or wireless resource capabilities. One-to-one ProSe communication over an interface is connection-oriented, but as mentioned above, the protocol used to establish the connection is The PC5-S signaling protocol used is not designed to handle AS layer parameters. As a result, both one-to-many ProSe communication and one-to-one ProSe communication are Regarding the RX UE protocol stack configuration, all the functions required for the RX UE are For example, HARQ feedback is required for sidelink communication. No wireless backbone is used, RLC UM is used for sidelink communication, For sidelink communication, ROHC unidirectional mode is used for PDCP header compression. Not using Uplink Data Compression (UDC) A receiving UE must have at least one RLC UM entity for each transmitting peer UE. The receiving RLC UM entity used for sidelink communication must maintain It does not need to be configured before receiving the first RLC UMD PDU. For TX UEs, the AS Parameters are set or derived from QoS input provided by higher layers For example, a UE may choose to allocate multiple logical channels based on QoS input from higher layers. The LCID contained in the MAC subheader is used to establish a single source layer. Uniquely identifies a logical channel within the combination of Layer 2 ID and destination Layer 2 ID. As mentioned above, no parameters are set for logical channel prioritization. The Access Stratum (AS) is connected to the upper layer via the PC5 interface. Each logical channel provides a PPPP protocol data unit. PPP is associated with the AS. Similarly, PPPR is not configured. PPP Protocol Data Units sent by the R is provided. The radio resources used for ProSe direct communication are determined by higher layers. Based on the provided QoS input and radio resource configuration information, U It can be selected autonomously by the EAS or reported to the eNB by the UE. Considering the QoS inputs and higher layer resource configurations, e.g. can be scheduled by the eNB when in coverage or out of coverage. do.

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

[0096] (One-to-one V2X communication) LTE does not support connection-oriented and point-to-point V2X communication. stomach.

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

[0098] (PC5 Access Layer (Radio) Configuration for V2X) The PC5 access layer settings are the same as those for ProSe direct communication. do.

[0099] Point-to-multipoint V2X communication over the PC5 interface is connectionless and is intended Therefore, there is no need to control the receiver or the wireless protocol stack. Or there is no need to configure the radio resource according to its capabilities. As a result, the RX UE protocol The stack configuration is predefined in the specification with all the required features for the 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 sidelink communication. ROHC unidirectional mode is used for sidelink communication, and uplink data compression (UDC) is used for sidelink communication. C) is not used. The receiving UE must have at least one R The LC UM entity must 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. For the TX UE, the AS parameters are provided by the QoS input and higher layers. It is set or derived from other configuration parameters such as the TX profile. For example, the UE may establish multiple logical channels based on QoS input from higher layers. The LCID contained in the MAC subheader is a source Layer 2 ID. Uniquely identifies a logical channel within a range of destination Layer 2 ID combinations. In the access stratum, no parameters for logical channel prioritization are configured. S) is the protocol data sent by the upper layer over the PC5 interface. A PPPP of units is provided. Each logical channel has an associated PPPP. Similarly, PPPR is not configured. The AS is configured by the upper layer to PPPR of protocol data units transmitted over the ProSe is provided. The radio resources used for wireless communication depend on the QoS input and wireless Autonomously selected by UE AS when out of coverage based on wire resource configuration information or the QoS input and higher level reported by the UE to the eNB. Considering the resource configuration of the ear, e.g., when in coverage or out of coverage Sometimes it can be scheduled by the eNB. The TX profile is V2 X sidelink transmissions using either Release 14 PHY format or Release 15 PHY format Used to determine which Y format (e.g., 64QAM) to use. do.

[0100] (NR V2X use case) SA1 supports vehicle platooning, extended sensors, advanced driving, and remote, four-way communication. have identified three main groups of advanced V2X use cases [1][2]: Vehicle platooning allows vehicles to dynamically form groups that travel together All vehicles in the platoon receive data periodically from the lead vehicle to perform platooning operations. With this information, the distance between vehicles can be made very small, i.e., in a timely manner. The gap distance can be converted to very small values ​​(sub-seconds). This allows the following vehicle to drive autonomously. Extended sensors include vehicles, RSUs, pedestrian devices, and V2X application servers. between servers, raw data collected via local sensors or live video data, or It allows the exchange of processed data. Vehicles can see beyond the range of their own sensors. It will increase awareness of the environment and provide a more holistic view of the local situation. A high data rate is one of the key characteristics. Advanced driving allows semi-automated or fully automated driving. Larger following distances are expected. Each vehicle and / or RSU distributes the data obtained from its local sensors to the neighboring This information can be shared with other vehicles, allowing them to adjust their trajectory or maneuver. Each vehicle shares its driving intentions with nearby vehicles. The benefits are safer driving, collision avoidance and increased traffic efficiency. Remote driving is used to provide passengers who are unable to drive themselves or to provide remote vehicles in dangerous environments. , allowing remote drivers or V2X applications to operate. Public transport In cases where changes are limited and paths are predictable, cloud computing-based operations are High reliability and low latency are the main requirements. The requirements for NR V2X are much more diverse than those for LTE V2X, as shown in Figure 5. strict.

[0101] As mentioned earlier, from the AS perspective, ProSe sidelink unicast and group Furthermore, LTE V2X does not support group casting. NR V2X only supports stream transmission, which is also connectionless. Considering that the requirements are much more diverse and stringent than those of LTE V2X, Connectionless transmission presents many challenges, especially in the context of the diverse and demanding requirements of NR V2X. For example, requirements for higher data rates, higher reliability, and lower latency From the viewpoint of supporting unicast, it may not be appropriate. and groupcast AS connectionless transmission to meet NR V2X requirements. Some examples of challenges to be met are given below. Note that the terms ipv4 and multicast are used interchangeably. 1. Higher protocol overhead. AS connectionless transmission requires more overhead than 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 the SAP (SESS Point), but also the SL RX UE is different To be able to distinguish between SL TX UEs, each V2X packet contains a destination ID and a source ID. Furthermore, the AS connector multiplexes traffic at the MAC layer. Connectionless transmission uniquely identifies a logical channel within the context of a destination-source pair. Each MAC PDU sent includes an L2 destination ID and a source L2 ID to identify the For ProSe sidelink and V2X sidelink, To limit overhead, each MAC PDU contains a source ID and a destination ID for the higher layer. D, which carries the L2 source ID and L2 destination ID mapped to Despite the mapping, each V2X packet transmission still includes the L2 source ID and This protocol overhead incurs the overhead of the L2 destination ID. Acceptable in the context of LTE V2X transmissions, which use relatively low data rate transmissions Although it was possible, in the context of NR V2X, such overhead is There is a risk of it becoming excessive. 2. Higher processing overhead. Each sidelink packet requires L2 source ID and L2 The fact that it preserves the destination ID also allows for more packet filtering at L2. It also means processing overhead. For example, in LTE V2X, the RX PHY layer The receiver receives all successfully decoded V2X packets on the configured RX resource pool. The V2X packet is then passed to the RX L2 with a 24-bit L2 destination ID and This RX U is filtered at L2 using a 4-bit L2 source ID. Only V2X packets from E are passed to the V2X upper layer. In this case, the PHY layer decodes all packets received on the configured RX resources. and partial filtering based on the 8 LSB bits of the SCI's L2 destination ID. filtering, then passes the partially filtered packet to L2, Filtering is based on the 16 MSB bits of the L2 destination ID and the 24-bit long source L2 ID. Such processing overhead is not possible with relatively low data rate transmission. While this was acceptable in the context of LTE V2X transmissions, it is not In this context, such processing overhead may be excessive. 3. Difficulty in enabling physical layer feedback. Connectionless transmission of AS L2 feedback is not supported in the conventional LTE ProSe Or in traditional V2X sidelink communication, there is no support for RLC feedback. No support for HARQ feedback. Separate feedback from RX UE to TX UE. C-RNTI or communication context dedicated to a specific UE to support the transmission of There is no UE specific identity (source or destination) at the PHY layer, such as the It would be very complicated to implement without continuation-oriented transmission. 4. It is difficult to enable link management to meet QoS requirements. Wireless transmission includes radio link monitoring and recovery, beam management, and link adapter Adaptation (power control and rate control), and channel dependent speed It is not practical to enable UE specific radio link management functions such as scheduling In the case of ProSe sidelink or V2X sidelink, The lack of these features was tolerated, but was accompanied by higher reliability and lower latency. The diverse and demanding requirements of NR V2X, such as higher data rates, require more efficient wireless routing. Furthermore, connection-based SL allows for per-QoS flow-based SL QoS control becomes easy, and the foundation for integrated QoS processing in SL and Uu is established. Provided. 5. RX UE differentiated configuration cannot be supported. For AS connectionless transmission, e.g. Configuring the RX UE with a specific AS setting for the RX UE based on the capabilities of the RX UE Therefore, it is not possible to specify all ProSe sidelink features or or LTE V2X sidelink capability is mandatory for all RX UE for that release NR V2X requirements are diverse and may not be compatible with all NR V2 devices of any given release. It is not practical to make this functionality mandatory for all NR V2X UEs in that release. Connection-based SL transmission in the AS layer allows for more flexible configuration of the SL radio protocol. It is possible.

[0102] Considering the above drawbacks of AS connectionless transmission in the context of NR V2X communications, Considering this, NR V2X unicast and NR V2X groupcast are also supported by 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 unicast connection establishment, connection modification / reconfiguration, and disconnection 2. Authorizing and Provisioning the UE to Support Connection-Oriented Unicast Transmission (In and out of coverage) 3. Shared by the UE with the gNB to support unicast connection establishment, modification, or teardown V2X provisioning information (UE assistance information). 4. Triggers for unicast connection reconfiguration, disconnection, and connection relocation 5.SLAS protocol settings, including: a. Flow-based QoS vs. packet-based QoS, Mode 1 vs. Mode 2 resource MAC, RLC (e.g., UM vs. AM decision) settings), PDCP, SDAP, radio resources / radio bearers, PHY settings (e.g., feed HARQ TX with feedback vs. HARQ Tx without feedback HARQ with CSI etc.) settings b.SL unicast required for exchange between UEs via sidelink, e.g. , UE ID, UE capabilities, radio / bearer configuration, PHY information / configuration (e.g., HARQ, C AS-level information, such as SI), resource information / configuration, and QoS information c. Extension of Uu to support SL connection management and QoS, and SL Uniq AS level information required to be exchanged between UE and gNB for live communication d. How to support unicast between UEs via sidelink Specify whether S-level information is exchanged and the details of RRC and PC5 signaling. 6. Admission control, how this is done and which entity performs admission control mosquito 7. Configuring UE identification between TX UE and RX UE to support unicast transmission For example, in the LTE ProSe sidelink unicast design, the UE ensure that Layer 2 IDs for unicast communication are at least locally unique Therefore, the UE must use an unspecified mechanism to The UE should be prepared to handle Layer 2 ID conflicts with other UEs (e.g., if a 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 discussed below. It is an issue that needs to be addressed. 8. A discovery procedure is used to identify a specific UE to initiate point-to-point communication. The upper layer above the access layer is expected to share QoS related information and Whether it should be unicast, groupcast, or broadcast, the access layer Although unicast communication can be performed in a connectionless or connection-oriented manner, Access layer specific rules and criteria need to be designed when determining what should be Furthermore, the interaction between discovery and unicast connection management, etc. and to support unicast connection establishment, disconnection, or connection relocation decisions. The question of how to use the output of discovery needs to be addressed.

[0104] (Issues related to connection-oriented groupcast transmission) Similarly, as discussed in the section above entitled "Issues Related to Connection-Oriented Unicast Transmission," The problems identified need to be addressed in the context of connection-oriented groupcast transmission. Specifically, to support connection-oriented groupcast transmission in AS, the following issues must be addressed: The issue needs to be addressed. 1. Overall procedure for establishing a Groupcast connection, changing / resetting the connection, and disconnecting 2. Authorizing and provisioning the UE to support connection-oriented groupcast transmissions (in and out of coverage) 3. Shared by the UE with the gNB to support unicast connection establishment, modification, or teardown V2X provisioning information (UE assistance information). 4. For example, to establish a groupcast connection between a group member and a group lead. Triggering a groupcast connection reconfiguration, disconnecting, and connecting to another group Connection relocation by group members to 5.SLAS protocol settings, including: a. Flow-based QoS vs. packet-based QoS, Mode 1 vs. Mode 2 resource MAC, RLC (e.g., UM vs. AM decision) settings), PDCP, SDAP, radio resources / radio bearers, PHY settings (e.g., feed HARQ TX with feedback vs. HARQ Tx without feedback HARQ with CSI Settings such as: b. Required for exchange between UEs via the SL Groupcast sidelink, e.g. For example, UE ID, UE capabilities, radio / bearer configuration, PHY information / configuration (e.g., HARQ AS-level information, such as,CSI, resource information / configuration, 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 broadcast communication d. How to support unicast between UEs via sidelink Specify whether S-level information is exchanged and the details of RRC and PC5 signaling. 6. Admission control, how this is done and which entity performs admission control mosquito. 7. UE identification between TX UE and RX UE to support groupcast transmission Configuration and Association. The RX UE must participate in receiving two or more groupcast communications. Similarly, a TX UE may be involved in transmitting more than one groupcast communication. Layer 2 IDs for groupcast communication must be at least locally unique. It is necessary to ensure that the L2 ID for connection-oriented groupcast communication is How to ensure the uniqueness of is a problem that needs to be addressed. 8. The discovery procedure is used to discover a specific UE or a group of UEs in order to initiate one-to-many communication. It is expected that the upper layer above the access layer will QoS related information and whether the communication is unicast, groupcast, or broadcast The access layer can indicate to the access layer whether groupcast communication should be performed. In determining whether the access control should be performed in a connectionless or connection-oriented manner, Layer-specific rules and criteria may need to be designed. Interaction between the network and groupcast connection management, and groupcast connection establishment How to use the discovery output to support connection, disconnection, or connection relocation decisions One related question is how to use V2 X group management can be performed only at the V2X upper layer, only at the AS layer, or at both layers. If so, what is the relationship between AS groups and V2X upper layer groups? For example, if the UE members of an upper layer group are spread over a wide area, In this case, perhaps one single AS layer group cannot cover all UE members. First, to enable normal communication between all UEs in the upper layer UE group, multiple A For each AS group, a member UE (one or more) ) is responsible for establishing and maintaining connectivity between the AS group leader and the AS layer group. When a member UE (or UEs) moves, it can leave the original AS layer group. The AS group cast connection is established and reconnected to another AS group. for establishment and maintenance, and mapping to higher layer sessions / connections. The procedures, configurations and interactions between the router and the AS layer need to be designed and specified.

[0105] (Summary of proposed solution) In this disclosure, we propose the following solution to support unicast connection management: . 1. Layer 2 protocol structure, including: One SDAP entity per V2X destination, providing reflective Qo Since support for the S feature is not required, only the QOS flow ID in the SDAP protocol header is used. A new proposal to have MAC SDUs are subject to connection-oriented transmission, whereas M SDUs are subject to connectionless transmission. It is multiplexed separately from the AC SDU. · MAC PDUs subject to connection-oriented transmission do not carry source ID and destination ID. Sidelink multicast control channel and sidelink multicast transformer Port channel support. 2. V2X Sender and Receiver Provisioning 3. V2X transmission or V2X reception trigger 4. The sender and receiver of which entities perform the selection and on what criteria. Selection of the side RAT and interface, 5. Selection of transmission mode by transmitter and receiver and criteria for selection 6. Unicast connection, including a description of the support parameters from the UE (e.g., receiver capabilities) Detailed procedures for management and scheduling entities or Unicast configuration parameters configured in the UE by a supporting UE in cooperation with the UE. 7. Describe alternatives for connection management procedures, including the following options: Uses PC5 RRC signaling to establish V2X upper layer connections and AS layer The T-UE simultaneously carries the UE connection setup. It is set by the I-UE in cooperation with E. See Figure 16. PC5-S signaling is used to establish V2X upper layer connections and AS layer connections. The T-UE communicates with the scheduling entity or the I-UE. Set by the associated I-UE, see Figure 17. V2 to support AS layer connectivity using PC5 RRC signaling X upper layer configuration information and AS layer connection configuration are carried simultaneously. It is set by the I-UE in cooperation with the Journing Entity or the I-UE. In addition, V2X upper layer connectivity setup is independent of AS connectivity setup using PC5-S signaling. See Figure 18. V2X over LAN to support AS layer connectivity using PC5-S signaling The I-UE simultaneously carries the AS layer configuration information and the AS layer connection configuration. It is set by the T-UE in association with the ring entity or I-UE, and V2X upper layer connectivity setup is performed independently of AS connectivity setup using PC5-S signaling. See Figure 19. PC5-S signaling is used to establish V2X upper layer connections and AS layer connections. The I-UE carries the connection configuration at the same time. It is configured by the T-UE in cooperation with the serving entity, see Figure 20. Uses PC5 RRC signaling to establish V2X upper layer connections and AS layer The I-UE also carries the UE connection setup. It is configured by the T-UE in cooperation with the scheduling entity, see Figure 21. 8. Group connection configuration and V2X upper layer group mapping to AS layer subgroups The idea of ​​ping, the maintenance of a mapping table in the AS, and the AS to PHY One or more of the following instructions: Group Layer 2 Destination ID. V2X UE ID of group members (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 ID, or other that can be used by the UE as the source ID of a member UE A list of identifiers for For each subgroup, whether to relay data received for that subgroup , or an instruction requesting not to relay. 9. Various options for broadcast settings and broadcast setting signaling . 10. Method for UE handling of multiple simultaneous sidelink RRC connections. 11. PC5 Unicast Link Granularity Modeling, Unicast Link Updates, and Unicast Links How to add a unicast link

[0106] (UE behavior before V2X communication) (Layer 2 protocol structure) The Layer 2 sidelink structure for NR V2X is shown in Figures 6, 7, 8, and 9.

[0107] Figure 6 shows the Service Data Adaptation Protocol (SDA). Provides a description of the SDAP (V2X Destination) sublayer. One SDAP entity per V2X destination. In one embodiment, the V2X destination is a peer V2X UE destination. In such an embodiment, the UE may simultaneously communicate with n peer V2X UEs. If having V2X communication, the UE then establishes n SDAPs, one for each peer V2X destination UE. Each SDAP entity maintains a specific bearer for the peer V2X destination UE. maintain a set of multiple V2X destination UEs between the UE (in this case, the source UE) and the peer V2X destination UE. There may be several simultaneous V2X services, so the services are mapped The L2 destination IDs assigned to these services and the radio bearers associated with them are stored in this particular The V2X UE is mapped to the same SDAP entity associated with the peer V2X destination UE. V2X packets associated with a given peer V2X destination UE are of the transmission cast type (all whether it is unicast, groupcast, or broadcast The bearer or destination Layer 2 ID to be mapped to the mapped SDAP entity In the case of broadcast or groupcast, the peer V2X destination UE is The corresponding bearer and associated Layer 2 destination identity, even if not explicitly known to S, It can be mapped to any SDAP entity, or alternatively, one or more SDAP entities dedicated to supporting broadcast communications, or one or more SDAP entities to support groupcast communications, or One or more S to support both groupcast and broadcast communications There can be a DAP entity.

[0108] In another embodiment, the UE may be subsumed into a group that is (pre)configured or provisioned. In this embodiment, the V2X destination in FIG. It refers to a group of bis.

[0109] In an alternative embodiment, one SDAP per UE for V2X sidelink communication. In such a case, the identity of the V2X communication bearer is , which may need to be unique within the UE.

[0110] Figure 7 shows the Layer 2 network configuration to support V2X communication in an AS broadcasting configuration. Structure and Transport Sidelink Broadcast Channel Sidelink Broadcast Control Channel (SB-BCH) The mapping of the transport sidelink shared channel (SCH) is shown. Sidelink traffic logical channel (SL-SCH) on the Sidelink Traffic Logical Channel (STCH) multiplexing is performed by assigning each MAC PDU a source ID. and destination ID for which logical channels to support MAC multiplexing are It is assumed that the identification is unique. Multiplexing with logical STCH on SL-SCH The Sidelink Control Channel (SCCH) is introduced to It is also proposed that logical channels such as SCCH can be mapped to the Sidelink Signaling Radio Bearer (SL- It is also proposed to introduce a SL-SRB. The SL-SRB is responsible for connection management (e.g. signaling (connection establishment, connection reconfiguration, or disconnection) or sidelink measurements Can be used for configuration and reporting.

[0111] Figure 8 shows the Layer 2 configuration to support V2X communication in an AS unicast connection oriented configuration. The peer V2X receiver can, for example, implement a dedicated unicast receiver that takes into account the capabilities of the peer V2X UE. In this case, the sidelink traffic logical channel Multiplexing of the Transport Sidelink Shared Channel (SL-SCH) on the STCH is Each MAC PDU contains a source ID and a destination ID, for which MAC multiplexing is supported. It does not assume that the identification of the logical channel to which it is ported is unique. ,Multiplexing on STCH is performed by setting up a separate instance of SL-SCH at connection establishment, V HARQ element dedicated to transmitting 2X unicast traffic or SL-RRC signaling It is assumed that the AS is connected to the entity in an AS connection oriented manner. A MAC Service Access Point (SAP) is created for each instance of the SL-SCH. , communicated to the PHY, where the PHY receives the SL-SCH instance indicated by the MAC. PHY channel associated with the service (e.g., physical sidelink shared channel (Phys Create a corresponding instance of the ical Sidelink Shared Channel (PSSCH), As part of the connection context, each V2X server included in the connection context For service or data radio bearers, Layer 2 destinations mapped to V2X services A destination ID is maintained in association with the logical channel and the corresponding radio bearer. In this manner, the connection is For each of the two V2X UEs involved in the connection, the physical layer (Physical Layer: PHY) unique identifier, e.g., to identify both V2X UEs for connection-oriented reception purposes The PC5 sidelink RNTIs are assigned to each of the peer UEs, and both peer UEs Alternatively, each of the peer UEs may autonomously set its own PHY identification The TX UE can derive the child and exchange it with the peer R X Use the V2X UE's PHY identifier to identify the peer V2X UE to which the data is destined For example, a TX UE may map its transmitted data to the PHY identification of its peer RX V2X UE. The RX UE uses the The PHY identifier used is used to identify the RX UE of the data. Once decoded, The RX UE uses the association created during connection establishment between the PHY and MAC SAP. Therefore, the PHY is in a position to correctly route the received data to the correct MAC SAP. No layer multiplexing, e.g. traffic from peer V2X UE to UE (previously ) Alternative options carried over configured or provisioned dedicated PHY resources In this case, a PHY identifier that uniquely identifies the peer UE involved in the connection may not be required. In this case, the RX UE will select the peer V2X UE based on the PHY resource on which it received the V2X packet. X identifies the correct routing SAP in the transmitting UE and MAC. AS identifies the peer V2X The UE source ID (e.g., in the case of unicast) or groupcast is the destination Layer 2 ID of the peer V2X UE (e.g., ProSe Layer 2 group ID or ProSe Application Layer Group ID) to the PHY. The PHY can use such ID to identify the peer V2X to which it is sending. It is possible to derive an RNTI used to identify the UE. As part of the Sidelink Signaling Radio Bearer (SL-SRB) The logical channel carrying the control information (e.g., SCCH) is the sidelink data radio bearer. Sidelink Data Radio Bearer (SL-DRB) The logical channel (STCH) that carries the traffic and is configured for connection-oriented reception. It can be multiplexed on the SL-SCH transport channel. In this case, a sidelink control channel is used to configure and control unicast traffic. It is proposed to introduce a logical SL control channel, denoted SCCH. The SCCH can be associated with the SL-SRB. The L-SRB can be expressed as SL-SRB0. SL-SRB sent in the broadcast manner (AS connectionless) is 1. The SL- SRB can be expressed as SL-SRB2.

[0112] Figure 9 shows the layers to support V2X communication in an AS groupcast connection-oriented configuration. The V2X peer receivers are configured with dedicated groups that take into account the capabilities of the peer V2X UEs. Configured in Loopcast V2X configuration. In this case, the sidelink traffic logic Transport Sidelink Shared Channel (S) on a channel (e.g., SL-MTCH) Each MAC PDU contains a source ID and a destination ID, It is assumed that the logical channel identification is unique to support MAC multiplexing. Instead, the multiplexing on the SL-MCH is performed by a separate instance of the SL-MCH. is set at connection establishment and is used for V2X groupcast traffic or SL-RRC signaling. It is assumed that the HARQ entity is AS-connection oriented and is dedicated to the transmission of the nulling. When a connection is established, the MAC service access point of each instance of the SL-MCH is A request (SAP) is created and communicated to the PHY, which then The PHY channel (e.g., physical side) associated with the SL-MCH instance Physical Sidelink Shared Channel (PSMCH) As part of the connection context, the application creates and maintains an instance of the For each V2X service or data radio bearer included in the text, The mapped Layer 2 destination ID is associated with a logical channel and the corresponding radio bearer. In this way, the PHY level of traffic to the multicast channel is To support multiplexing of the TX V2X UE and RX group involved in the connection, For each group member UE, a physical layer (PHY) unique identifier, e.g., TX PC5 sidelink RNTI to identify the V2X UE and for connection-oriented reception purposes A physical layer unique identifier that identifies the RX group member UEs for Alternatively, the UE may be assigned a QoS policy and configured in the UE. Each autonomously derives its own unique PHY identifier and exchanges it with the other as part of the connection setup. The TX UE can use the PHY group identifier of the peer RX V2X UE to to identify the peer V2X group member UE to which the data is destined. For example, the TX UE is the PHY identifier of the peer RX V2X group member UE and scrambles the transmitted data. The RX UE can select the PHY group used by the transmitter. The loop identifier is used to identify the RX UE of the data. Once decoded, the RX UE , based on the association created during connection establishment between the PHY and MAC SAP. are in a position to correctly route the data to the correct MAC SAP. There is no PHY layer multiplexing of traffic, e.g., groupcast traffic is E is transmitted over dedicated PHY resources configured or provisioned (pre-) The exchange option does not require a PHY group identifier to uniquely identify the peer UEs involved in the connection. In this case, the RX member UE receives the groupcast traffic. Based on the PHY resources allocated, the correct routing of groupcast traffic and MAC The AS identifies the routing SAP of the UE, not only its own source ID but also the peer V2X The source ID of the UE (e.g. to support unicast) or the In case of peer V2X UE peer-to-peer communication, the destination Layer 2 ID (e.g., Pro Like Se Layer 2 Group ID, or ProSe Application Layer Group A PHY can provide a unique ID (or a unique identifier) ​​to the PHY. The PHY can then use such ID to It is possible to derive an RNTI that is used to identify the peer V2X UE to which the Additionally, as part of the connection setup, a Sidelink Signalling Radio Bearer (SL-S Logical channels carrying sidelink multicast control information mapped to RBs (e.g., SL-MCCH) is mapped to a Sidelink Data Radio Bearer (SL-DRB). Logical Channels (SL- MTCH) and the SL-MCH transport channel configured for connection-oriented reception For groupcast, groupcast traffic can be multiplexed on A Sidelink Multicast Control Channel (SMC) is used to configure and control the sidelink. Logical sidelink control, denoted as SL-MCCH (Multicast Control Channel) A channel can be introduced. MCCH can be associated with SL-SRB. The SL-SRB to which the SBCCH is mapped can be represented as SL-SRB0. MCCH is mapped and transmitted in a broadcast manner (AS connectionless). The SL-SRB to be used can be represented as SL-SRB1. The SL-SRB transmitted in a connection-oriented manner can be denoted as SL-SRB2.

[0113] Figure 10 provides a functional diagram of the SDAP sublayer. Reflective QoS is a V2X side link. It is proposed that this will not be supported in the SD It is proposed to simplify the AP header and make the header the same between downlink and uplink. The QoS Flow Identifier (QFI) is 6 bits or less. while the remaining bits of the header can be reserved bits or can store data It can be used to carry QoS flow over V2X sidelink. This minimizes the support overhead for

[0114] (Sender operation) Either AS broadcast, AS unicast, or AS groupcast 1 illustrates an exemplary transmit-side high-level view of UE operation, including intermediate steps within the UE leading to a decision to engage in V2X communication via A detailed description is provided in FIG. In step S1200, the UE performs V2X operation, i.e., the UE performs V2X communication. The discovery procedure that the UE performs on the V2X device to discover other devices. V2X by communicating with other V2X devices as required by the V2X application Pre-configured (in the SIM or ME) to support X communication, or Provisioning is performed by the V2X control function located in the core network that has the information. The UE and V2X communication for provisioning of V2X operational parameters is either Communication between the 2X control functions can be via the user plane or via the control plane NR V2X operation, and in particular unicast or groupcast communication For provisioning parameters to support V2X communication, see "Transmitter V2X Communication" below. This is described in the section entitled "Provisioning of Communications." When 2X communication is triggered, the UE will synchronize if it is not already synchronized in step S1204. The UE may also perform synchronization as dictated by the trigger conditions of the communication. and performing discovery to identify peer UEs or groups of UEs with which it can communicate. For example, an application in the application layer can to discover a peer UE or group of UEs if they have not already been discovered, and V2X communication can be initiated for a UE or group of UEs such as Output from the recovery procedure, e.g., Layer 2 link of a discovered UE or group of UEs The ID(s) are used to establish a connection or subsequent steps in V2X operation, such as configuring broadcast resources for V2X transmissions, The steps S1206 and S1207 can be used by the UE in one or more steps. At 208, the UE determines the RAT selection and interface (e.g., sidelink vs. U-band). u interface) selection is performed. Steps S1206 and S1208 are separate. Although it is described as a separate step, "sender RAT selection and interface selection" The two steps are performed simultaneously, as explained below in the section entitled In step S1210, it is determined whether the SL interface is selected. If yes, it is determined what the SL transmission mode is (step S If the SL transmission mode is the broadcast mode, the broadcast is AS setting for broadcast transmission is performed. SL transmission mode is set to unicast mode. In this case, the layer 2 link setup for unicast transmission is performed in step S1214. If the SL transmission mode is the multicast mode, the multicast is In step S1210, a layer 2 link is set up for receiving the message. If no interface is selected, start transmitting over the Uu interface ( Step S1220).

[0115] (Provisioning of V2X communication on the transmitting side) Unicast transmission, groupcast transmission, broadcast transmission, or flow-based To support QoS in the NR V2X environment, the NR V2X UE must be configured with the following system parameters: It can be pre-configured or pre-provisioned. The configuration can be, for example, NR Uu interface, LTE sidelink interface, L From the TE Uu interface, WLAN sidelink interface, or WLAN This can be on a per interface basis, such as an interface to a network. A list of authorized V2X services and, for each service, the transmission mode (transmission key type), i.e. whether the service is a broadcast-based transmission or a group Whether it is a broadcast-based transmission or a unicast-based transmission, The service transmission mode can be on a PLMN or group of PLMNs basis, or on a cell or on a group of cells basis, or on a geographic area or group of geographic areas basis It can be defined as: A list of authorized V2X services and, for each service, whether transmission is permitted at the V2X upper level Whether it is ear connectionless or V2X upper layer connection oriented. For example, While a unicast transmission can be a connectionless transmission, It can be a connection-oriented transmission or a groupcast transmission, or it can be a V2X upper layer It can be a connectionless transmission. A list of authorized V2X services and, for each service, the AS layer controller that transmits the Whether it is connectionless or V2X AS layer connection oriented. For example, broadcast A unicast or Groupcast transmissions can be connection-oriented or can be routed to the AS layer. It can be transmitted without any response. the scheduler or scheduling entity of another UE or the local computer Authorization to act as a controller or scheduler node. Such authorization is LMN-based or PLMN group-based, cell-based, cell group-based Define it on a geographical area basis or on a group of geographical areas basis. In the present disclosure, a local controller, a scheduling entity, or The terms scheduler entity are used interchangeably. For example, a platoon lead may: It can be provisioned with authorization to act as a scheduling entity. Such authorization can also be defined on a per service or per group of services basis. can. Authorization to the scheduling entity to act as a supporting UE. Such authorization may be On a PLMN or group of PLMN basis, on a cell or group of cells basis Defined on a group basis or on a geographic area or group of geographic areas It is possible. Overlapping authorizations across radio interfaces, i.e., authorizations for two or more radio interfaces For example, transmission of the same data over two or more of the following radio interfaces: N NR sidelink interface, NR Uu interface, LTE sidelink interface interface, LTE Uu interface, WLAN sidelink interface, or WLAN to network interface. Such duplication is necessary to meet reliability requirements, e.g. In the case of a packet-based QoS model, the reliability value of each ProSe packet is Or, in the case of QoS flow or bearer-based QoS models, packet error rate. Such authorization can be defined based on service-based or QoS identifier values. Furthermore, such authorization can be defined per cell or group of cells. Group or by geographic area or group of geographic areas or PL It can be defined per MN or PLMN group basis. In this test, the QoS identifier is called the V2X QoS Identifier (VQI). It is expressed as: A list of V2X QoS identifiers. For each VQI, the corresponding QoS profile The QoS profile defines the priority level (i.e., scheduling priority level), payload, sending rate, maximum end-to-end delay, signal reliability, data rate, minimum required range, preemption priority level (i.e., The priority level may include one or more of the following: The QoS profile defines the priority level (i.e., the scheduling priority level) , resource type (e.g., GBR, delay-critical GBR or non-GBR), packet delay budget, packet error rate, averaging window, and maximum data burst size. This configuration can be PLMN-based or PLMN group-based. per site, cell or group of cells, geographic area or It can be defined on a group basis. 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 On a cell or group of cells basis, per MN or group of PLMN basis , which can be defined per geographic area or group of geographic areas . Connection-oriented transmission and the resources 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 a resource pool is It can be a shared resource pool that is also used for connectionless PC5 data transmission. .

[0116] Each of the provisioning parameters defined above is used when the UE is connected to the radio access network. provided by the network or provided by the radio access network Furthermore, the radio access network If not provided, is the carrier frequency for V2X communication operator-managed? Set provisioning parameters based on whether the device is operator-managed or non-operator-managed It is possible.

[0117] The UE may also pre-configure the following capability parameters (e.g., SIM or is a Mobile Equipment (ME). Support for AS-based unicast transmission - Support for AS-based groupcast transmission Support for V2X UpL-based unicast transmission Supports V2X UpL-based groupcast transmission Supports AS connectionless transmission Support for AS connection-oriented transmission Supports packet duplication across wireless interfaces Support for the ability to act as a scheduling entity. Support for the ability to act as a supporting UE to the scheduling entity Support for flow-based QoS model, e.g., V2X upper layer to V2X QoS model, where the QoS requirements of packets forwarded to an AS are indicated using QoS flows. Features that support Dell. Support for per-packet QoS mode, e.g., V2X upper layer to V2X AS Each packet forwarded to carries its QoS requirement, e.g., PPPP or PPPR. Ability to support QoS models.

[0118] (Transmitter trigger for V2X communication) In the context of the high-level description of V2X operation given in Figure 12, the following events One or more of the V2X communication devices may trigger the V2X communication procedure, including the connection establishment procedure in the UE. can. Sending V2X packets for transmission by the V2X application. In this case, the procedure is , which are triggered as a result of events originating from the application layer. · Discovery triggered by the application layer. The communication quality of the current / existing V2X communication no longer meets the quality threshold. ,one or more QoS profile metrics (e.g., packet error rate, delay, reliability, In this case, the V2X upper layer of the V2X UE , another UE or A mobile station can initiate communication to a single UE or a group of UEs. Radio link failure, beam failure, or beam failure recovery failure. In this case, V2X The V2X upper layer of the AS manages V2X communication initiated by the application layer. To continue, communication can be initiated to another UE or group of UEs. The wireless link quality no longer meets the quality threshold. Congestion exceeds 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 the V2X AS, To continue V2X communication initiated by the application layer, another UE or group of UEs The mobility event is the UE's own mobility event. or may be related to the mobility of the peer UE. Scheduling, e.g., controlling resource allocation from or to peer UEs Receipt of a disconnect from the destination entity. Scheduling entity that controls resource allocation from / to peer UEs Receiving a connection establishment request from an entity. Scheduling entity that controls resource allocation from / to peer UEs Receiving a handover request from the entity. -Connection re-establishment failure.

[0119] The V2X upper layer can trigger the V2X communication operations described in Figure 12. Similarly, the V2X AS layer can trigger the V2X communication operations described in Figure 12. do.

[0120] (Sender RAT selection and interface selection) The V2X upper layer can perform RAT selection or interface selection. V2X upper layers perform RAT selection and interface selection sequentially or simultaneously. V2X AS can be used for RAT or interface selection. Support information such as functionality information can be provided to the V2X upper layer. For example, S can determine the availability of its RAT. Furthermore, the AS can determine the availability of a particular RAT. In an exemplary embodiment, the RAT is one of the following RATs: NR RAT, LTE RAT, Wi-Fi, or WLAN RAT Similarly, the interface can be a sidelink NR RAT, a Uu RAT, Sidelink LTE RAT, Uu LTE RAT, Sidelink Wi-F i, or WLAN RAT, and the wireless interface between the WLAN and the network An AS may be one or more of the RATs or specific The availability of an interface associated with a particular RAT can be determined. Communication Quality Threshold. The quality threshold is determined by one or more QoS profile metrics (e.g., packet The communication speed can be related to the bit error rate, delay, reliability, range, etc. ·Radio link quality threshold. Congestion threshold. The congestion threshold is, for example, the Channel Busy Ratio (CBR) and and / or Channel Occupancy Ratio (CR). Cut. Radio link failure, or beam failure, or beam failure recovery failure. Out-of-coverage or partial out-of-coverage detection. · Predicted transmit power threshold or path loss threshold. ·UE ability. The availability information may include one or more of the following information: ·Available or unavailable. Communication quality threshold Wireless link quality threshold Congestion Threshold Out-of-coverage or partial out-of-coverage detection ·UE ability

[0121] (Select the sender's communication mode) V2X upper layer selects the transmission type, i.e., broadcast vs. group. It performs loopcast vs. unicast and compares the selected transmission type with the V2X AS relay. The V2X upper layer can show the AS layer to the V2X AS layer. Such an approach allows a user to indicate the transmission cast type of each packet sent to the user. The V2X upper layer sends a packet-by-packet transmission cast to the V2X AS layer. The V2X upper layer can, for example, provide per-packet QoS In conjunction with the specification, a per-packet indication of transmission cast type may be used. In an alternative embodiment, the V2X upper layer and AS layer are configured to support each transmission type. For each embodiment, a service access point (SAP) can be specified. Each transmission type (i.e., unicast, groupcast, or broadcast) For each transmission type, the AS layer provides one or more transmission type features to the V2X upper layer. The V2X upper layer publishes the specified SAP according to the transmission cast type. The AS receives the packet from the SAP where the packet is sent to the AS. The V2X AS layer derives the transmission cast type of the packet. A particular V2X upper layer is selected according to the transmission cast type associated with that SAP received. Send packets received via layer SAP.

[0122] The V2X upper layers establish and transmit connections to support secure Layer 2 links. The association (including security association) between a source and destination identity. It is possible to create a V2X upper layer context for such a connection. From the perspective of the layer, the transmission can therefore be connection-oriented, in which case the layer The V2X link connection context is maintained by the V2X upper layer or the transmission is A connection that is created between a source and destination before communication begins and has no associated context. V2X upper layers can be connectionless. If so, it can be indicated to the V2X AS. The AS layer can create AS-level connections. and transfers the context of such a connection to the connection context of the higher layer in the UE. The AS context of an AS connection can be associated with a connection-oriented AS protocol. It may contain stack configuration and security associations between source and destination. Alternatively, an AS can create an AS-level connection for a specific V2X upper layer connection. In such cases, the higher layer connection-oriented SAP may not The transmitted upper layer packets are, for example, broadcast packets at the AS layer level. It can be transmitted in a connectionless manner at the AS level via

[0123] (V2X upper layers use unicast vs. groupcast vs. broadcast transmission) mechanism for determining the use The V2X upper layer decides to use a transmission 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 determined by one or more QoS profile metrics (e.g., packet Bit error rate, delay, reliability, communication range, scheduling priority, preemption priority can be related to the degree of Service type or traffic type, e.g., signaling vs. application data. Service authorization settings. ·ability. Destination ID or number of destination UEs. Pre-configuration (e.g., ME, SIM) and provisioning to the UE by the network; For example, V2X control functions or scheduling entities may configure the UE. Configuration to the UE, including the mapping of services to transmission cast types. This can be done. Link Quality

[0124] (Using unicast vs. groupcast vs. broadcast transmission in the AS upper layer) mechanism that determines The V2X AS layer decides to use a transmission cast type based on one or more of the following: It is possible. - Instructions from V2X upper layer. Communication Quality Threshold. The quality threshold is determined by one or more QoS profile metrics (e.g., packet The communication speed can be related to the bit error rate, delay, reliability, range, etc. 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, capabilities, gNB or network capabilities, etc. Destination ID or number of destination UEs. Pre-configuration (e.g., ME, SIM) and provisioning to the UE by the network; For example, V2X control functions or scheduling entities may configure the UE. Configuration to the UE, including the mapping of services to transmission cast types. This can be done. Wireless link quality.

[0125] (Mechanism by which V2X upper layers decide to use connection-oriented vs. connectionless) The V2X upper layers implement connection-oriented transmission, or connection-based transmission, based on one or more of the following: You can decide to use a non-transmitting address. -Instructions from the application layer. Communication Quality Threshold. The quality threshold is determined by one or more QoS profile metrics (e.g., packet The communication speed can be related to the bit error rate, delay, reliability, range, etc. 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, gNB or network capabilities. Destination ID or number of destination UEs. Pre-configuration (e.g. ME, SIM, etc.), provisioning to UE by network configuration to the UE by the V2X control function or scheduling entity. Configuration to the UE, including the mapping of services to transmission cast types. It can be done. Link Quality Security requirements (e.g., security thresholds). Security requirements include authentication, integrity, , or encryption-related requirements.

[0126] Next, we will discuss how the AS layer decides to use connection-oriented versus connectionless. The V2X AS upper layer determines the transmission cast time based on one or more of the following: You can decide to use the group. - Instructions from V2X upper layer. Communication Quality Threshold. The quality threshold is determined by one or more QoS profile metrics (e.g., packet The communication speed can be related to the bit error rate, delay, reliability, range, etc. 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, gNB or network capabilities, etc.). Destination ID or number of destination UEs. Pre-configuration (e.g. ME, SIM, etc.), provisioning to UE by network (e.g., V2X control function or scheduling entity) ) to the UE. The configuration specifies the mapping of services to transmission cast types. It can include. Wireless link quality. Security requirements (e.g., security thresholds). Security requirements can be integrity or can be a requirement related to encryption.

[0127] (Receiver operation) Either AS broadcast, AS unicast, or AS groupcast 1. An exemplary receiver-side high-level view of UE operation, including intermediate steps within the UE leading to a decision to engage in V2X communication via A detailed description is provided in FIG.

[0128] In step S1300, the UE performs V2X operation, i.e., the UE performs V2X communication. discovery procedure to discover other devices for V2X communication, and To support V2X communication by or by a V2X control function located in the core network that has the information. Provisioning of V2X operating parameters The communication between the UE and the V2X control function for V2X control is via the user plane or via the control plane. NR V2X operation and especially unicast communication or Provisioning parameters for supporting receiving groupcast communications is described below in the section entitled "Provisioning Receiver V2X Communications." When V2X communication is triggered in step S1302, the UE If not already synchronized, it can perform synchronization. The UE also Discovery is performed to identify peer UEs or groups of UEs that can receive The output from the discovery procedure, e.g., the discovered UE or UEs The Layer 2 link ID(s) of the group E shall be used to identify the model for receiving V2X communications. Monitoring, establishing a connection to a specific UE or group of UEs, or V2X communication Subsequent steps in V2X operation (single or multiple) such as setting up broadcast resources for reception of can be used by the UE in steps S1306 and S1308. In this case, the UE must decide the RAT selection and interface (e.g., sidelink vs. Uu interface). Steps S1306 and S1308 are separate steps. Although it is described as a step, it is titled "Receiver RAT Selection and Interface Selection" The two steps can be performed simultaneously, as described in the following sections. In step S1310, it is determined whether the SL interface is selected. If yes, it is determined what the SL reception mode is (step S1312 If the SL reception mode is the broadcast mode, the broadcast is When the SL reception mode is unicast, AS setting for unicast reception is performed. In step S1314, a layer 2 link is set up for unicast reception. If the reception mode is multicast mode, the groupcast reception is started in step S1316. In step S1310, the SL interface is set up. If no interface is selected, start configuration for receiving via the Uu interface (step S1320).

[0129] (Provisioning of V2X communication on the receiving side) Unicast reception, groupcast reception, broadcast reception, connection-oriented reception, or To support flow-based QoS, NR V2X UEs must be able to: The configuration can be pre-configured or provisioned with system parameters. NR sidelink interface, NR Uu interface, LTE sidelink interface interface, LTE Uu interface, WLAN sidelink interface, and on a per interface basis, such as the interface from a WLAN to a network It is possible. A list of authorized V2X services and, for each service, the reception mode (reception key) type), i.e. whether the service is broadcast-based reception or group Whether it is a broadcast-based or unicast-based reception, the server The service reception mode can be on a PLMN or group of PLMN basis, or on a cell or on a group of cells basis, or on a geographic area or group of geographic areas basis It can be defined as: A list of authorized V2X services and, for each service, the V2X upper level Whether it is ear connectionless or V2X upper layer connection oriented. For example, While a unicast receive can be a connectionless receive, For example, groupcast reception can be performed using connection-oriented reception, or V2X upper layers can be used. Connectionless reception can be achieved with A list of authorized V2X services and, for each service, the AS layer controller Whether it is connectionless or V2X AS layer connection oriented. For example, broadcast While a stream reception can be a connectionless reception, a unicast reception or Groupcast reception can be performed as connection-oriented reception or at the V2X AS layer. Connectionless transmission and reception can be performed. the scheduler or scheduling entity of another UE or the local computer Authorization to act as a controller or scheduler node. Such authorization is LMN-based or PLMN group-based, cell-based, cell group-based Define it on a geographical area basis or on a group of geographical areas basis. In the present disclosure, a local controller, a scheduling entity, or The terms scheduler entity are used interchangeably. For example, a platoon lead may: It can be provisioned with authorization to act as a scheduling entity. Such authorization can also be defined on a per service or per group of services basis. can. Authorization to the scheduling entity to act as a supporting UE. Such authorization may be PLMN-based or group of PLMN-based, cell-based or group of cells-based Defined on a geographical area basis or on a geographical area group basis. It is possible. Allowing overlapping reception across radio interfaces, i.e., two or more radio interfaces Reception of the same data across multiple wireless interfaces, for example, on 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 or WLAN to network interface. Such overlapping may be due to reliability requirements, e.g. For example, in the case of a packet-based QoS model, the reliability value for each ProSe packet is , or the packet error rate in the case of QoS flow or bearer-based QoS models. or based on QoS identifier values. Furthermore, such authorization can be defined per cell or cell area. In groups or by geographic area or group of geographic areas basis; It can be defined per PLMN or group of PLMNs. In the text, the QoS identifier is referred to as the V2X QoS identifier (VQI). A list of V2X QoS identifiers. For each VQI, the corresponding QoS profile The QoS profile defines the priority level, i.e., Scheduling priority level, payload, sending rate, maximum end-to-end delay, reliability performance, data rate, minimum required range, preemption priority level (i.e., preemption priority levels). ,The QoS profile is a priority level (i.e., scheduling priority level), Resource type (e.g., GBR, delay-critical GBR or non-GBR), packet packet delay budget, packet error rate, averaging window, and maximum data burst size. This configuration can be on a PLMN basis or on a group of PLMNs. By base, cell or group of cells basis, geographic area basis or geographic area basis It can be defined on a per rear group basis. A list of QoS flow identifiers (QFIs). For each QFI, a mapping between the QFI and the VQI is performed. QoS flow is the finest granularity of QoS differentiation. is a cell or group of cells on a per PLMN or per group of PLMN basis. Defined on a geographic area basis or group of geographic areas basis can be done. For signaling to support connection-oriented receiving and the maintenance of these connections Resource pool settings. A PC to support signaling reception for connection establishment and maintenance of that connection. Resource pool configuration for 5 signaling or SL RRC signaling. The resource pool is a shared resource pool that is also used for connectionless PC5 data transmission. It can be a pool.

[0130] Each of the provisioning parameters defined above is used when the UE is connected to the radio access network. provided by the network or provided by the radio access network Furthermore, the radio access network If not provided, is the carrier frequency for V2X communication operator-managed? You can set provisioning parameters based on whether the device is operator-managed or not. can.

[0131] The UE may also pre-configure the following capability parameters (e.g., SIM or on a Mobile Device (ME). - Support for AS-based unicast reception. - Support for AS-based groupcast reception. Support for V2X UpL-based unicast reception. Supports V2X UpL-based groupcast reception. Support for AS connectionless reception. Support for AS connection-oriented receiving. Supports packet duplication reception across wireless interfaces Support for the ability to act as a scheduling entity. Support for the ability to act as a supporting UE to the scheduling entity QoS Support for flow-based QoS specifications, e.g., V2X AS layer receives When delivering the received packets to the V2X upper layer, the radio bearer is Ability to support packet mapping and QoS models. Support for per-packet QoS mode, e.g., from V2X AS to V2X upper layer Each packet delivered to the The ability to support different QoS models.

[0132] (Receiver trigger for V2X reception) In the context of the high-level description of V2X receive operation described in Figure 13, One or more of the events may be connection management related messages, including, for example, the receipt of a connection establishment message. It can trigger V2X reception procedures, including monitoring of V2X messages. Trigger from the V2X application for transmission. In this case, the procedure is It is triggered as a result of an event originating from the application layer. · Discovery triggered by the application layer. Periodic monitoring of reception in the V2X reception resource pool The communication quality of the current / existing V2X communication no longer meets the quality threshold. ,one or more QoS profile metrics (e.g., packet error rate, delay, reliability, In this case, the V2X upper layer of the V2X AS ,to continue receiving V2X communications initiated by the application layer, another It can initiate communication to a UE or a group of UEs. For example, if a UE is in a formation If it detects that the V2X reception quality no longer meets the quality threshold, E can initiate communication towards other platoon lead UEs. Radio link failure, beam failure, or beam failure recovery failure. In this case, V2X The V2X upper layer of the AS manages V2X communication initiated by the application layer. To continue, it can start receiving communications for another UE or group of UEs. Cut. The radio link quality of the current / existing V2X communication no longer meets the quality threshold. -Current / existing V2X communication congestion exceeds the threshold. The transmission power of the current / existing V2X communication exceeds the threshold, or the path loss exceeds the threshold. are. Mobility events, in this case the V2X upper layer of the V2X AS, To continue V2X communication initiated by the application layer, another UE or group of UEs The UE can then start receiving V2X communications towards the target. It can be related to the mobility of the UE itself or related to the mobility of a peer UE. can. Scheduling, e.g., controlling resource allocation from or to peer UEs Receipt of a disconnect from the destination entity. Scheduling entity that controls resource allocation from / to peer UEs Receiving a connection establishment request from an entity. Scheduling entity that controls resource allocation from / to peer UEs Receiving a handover request from the entity. -Failure to re-establish current / existing V2X communications connections.

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

[0134] (Receiver RAT selection and interface selection) Similar to the transmitter operation described above, the V2X upper layer performs RAT selection or interface selection. In one embodiment, the receiving RAT of a given UE can select the transmitting RAT. T, i.e., set to be the same as the sending RAT. Similarly, the receiving interface can be the same as the sending interface, i.e. In another embodiment, the receiving R The AT can be different from the sending RAT. Similarly, the receiving interface can be different from the sending RAT. The V2X upper layer decides the RAT selection and interface. The RAT selection can be performed sequentially or simultaneously. The V2X AS For the selection of the V2X network or interface, support information such as availability information is sent to the V2X upper layer. For example, the AS of a RAT can determine the availability of that RAT. Additionally, the AS determines the availability of interfaces in relation to a particular RAT. In an exemplary embodiment, the RATs include an NR RAT, an LTE RAT, and a Wi-Fi RAT. -Fi RAT, etc. Similarly, the interface can be one or more of: Sidelink NR RAT, Uu RAT, Sidelink LTE RAT, Uu LTE RAT, sidelink Wi-Fi RAT, and between Wi-Fi and the network An AS can be one or more of the following: , the availability of an interface associated with a particular RAT for RAT or V2X reception Gender can be determined. Communication Quality Threshold. The quality threshold is determined by one or more QoS profile metrics (e.g., packet The communication speed can be related to the bit error rate, delay, reliability, range, etc. ·Radio link quality threshold. Congestion threshold. The congestion threshold is, for example, the channel congestion rate (CBR) or the channel occupancy rate (CR). It can be related to etc. Radio link failure, or beam failure, or beam failure recovery failure. Out-of-coverage or partial out-of-coverage detection. · Expected received power threshold or path loss threshold. Capabilities (e.g., UE capabilities, peer V2X UE capabilities, scheduling entity capabilities, gNB or network capabilities, etc.). The availability information may include one or more of the following information: ·Available or unavailable. Communication quality threshold Wireless link quality threshold Congestion Threshold Out-of-coverage or partial out-of-coverage detection Capabilities (e.g., UE capabilities, peer V2X UE capabilities, scheduling entity capacity, gNB or network capacity, etc.)

[0135] (Receiver sidelink communication mode selection) In this section, we explain how V2X upper layers can differentiate between unicast and group for V2X reception. Explain how to decide on the use of broadcast vs. The receiver may decide to use a receiver cast type based on one or more of the following: . -Instructions from the application layer. For example, as part of a connection establishment procedure or other connection management procedure, such as a connection reconfiguration procedure. ,Instruction from peer V2X UE sender. Communication Quality Threshold. The quality threshold is determined by one or more QoS profile metrics (e.g., packet The following can be related to the following: bit error rate, delay, reliability, communication range, etc. The member UEs of the group may decide to opt out of groupcast communication based on, for example, a threshold for communication reception quality. It may decide to request a switch from unicast to unicast communication, or On a broadcast basis, it switches to receiving communications from other member UEs acting as relay UEs. It may be decided to 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, gNB or network capabilities, etc. Pre-configuration (e.g. ME, SIM, etc.), provisioning to UE by network configuration to the UE by the V2X control function or scheduling entity. Configuration to the UE, including the mapping of services to transmission cast types. It can be done. Link Quality

[0136] (Using unicast vs. groupcast vs. broadcast transmission in the AS upper layer) mechanism that determines The V2X AS layer decides to use the receive cast type based on one or more of the following: It is possible. - Instructions from V2X upper layer. For example, as part of a connection establishment procedure or other connection management procedure, such as a connection reconfiguration procedure. ,Instruction from peer V2X UE sender. Communication Quality Threshold. The quality threshold is determined by one or more QoS profile metrics (e.g., packet The following can be related to the following: bit error rate, delay, reliability, communication range, etc. The member UEs of the group may decide to opt out of groupcast communication based on, for example, a threshold for communication reception quality. It may decide to request a switch from unicast to unicast communication, or On a broadcast basis, it switches to receiving communications from other member UEs acting as relay UEs. It may be decided to 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, gNB or network capabilities, etc.). Pre-configuration (e.g. ME, SIM, etc.), provisioning to UE by network , e.g., by the V2X control function or the scheduling entity to configure the UE. Configuration to the UE, including mapping of services to transmission cast types It is possible. Wireless link quality.

[0137] (Mechanism for determining whether V2X upper layers should use connection-oriented vs. connectionless reception) ) The V2X upper layers implement connection-oriented reception, or connection-based reception, based on one or more of the following: You can decide to use response reception. -Instructions from the application layer. For example, as part of a connection establishment procedure or other connection management procedure, such as a connection reconfiguration procedure. ,Instruction from peer V2X UE sender. Communication Quality Threshold. The quality threshold is determined by one or more QoS profile metrics (e.g., packet The following can be related to the following: bit error rate, delay, reliability, communication range, etc. Member UEs of the group are required to switch from connectionless reception to connection-oriented reception quality thresholds. It can decide to request a connection or act as a relay UE on a connection-oriented basis. The UE may 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, gNB or network capabilities, etc.). Pre-configuration (e.g. ME, SIM, etc.), provisioning to UE by network , e.g., by the V2X control function or the scheduling entity to configure the UE. Configuration to the UE, including mapping of services to transmission cast types It is possible. Link Quality Security requirements, e.g., security thresholds. Security requirements include authentication, integrity, Or it could be a requirement related to encryption.

[0138] (Mechanism by which the AS layer decides whether to use connection-oriented or connectionless) The V2X AS layer decides to use a transmission cast type based on one or more of the following: It is possible. - Instructions from V2X upper layer. For example, as part of a connection establishment procedure or other connection management procedure, such as a connection reconfiguration procedure. ,Instruction from peer V2X UE sender. Communication Quality Threshold. The quality threshold is determined by one or more QoS profile metrics (e.g., packet The following can be related to the following: bit error rate, delay, reliability, communication range, etc. Member UEs of the group are required to switch from connectionless reception to connection-oriented reception quality thresholds. It can decide to request a connection or act as a relay UE on a connection-oriented basis. The UE may 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, capabilities, gNB or network capabilities, etc. Pre-configuration (e.g. ME, SIM, etc.), provisioning to UE by network configuration to the UE by the V2X control function or scheduling entity. Configuration to the UE, including the mapping of services to transmission cast types. It can be done. Wireless link quality. Security requirements, e.g., security thresholds. Security requirements can be integrity or It can be a requirement related to encryption.

[0139] (Unicast Connection Management) (High-Level Unicast Connection Management Procedures) Figure 14 shows a high level view of sender operations for unicast Layer 2 link management, including connection establishment. In step S1400, it is determined whether the AS is connection-oriented. Step S1402 and step S1410 are steps for V2X communication between peer V2X UEs. Unicast connection establishment and connection context in the upper layer (V2X UpL) The unicast connection also means association as shown in step S1404. As shown in Figure 1, before forwarding unicast packets, the AS context between peer V2X UEs is configured. For the purpose of association and connection establishment signaling between peer V2X UEs is used to establish AS relationships. In this case, the peer V2X UE receiver can establish a UE Considering capabilities, dedicated radio resources may be included for unicast reception. As part of the unicast connection establishment procedure, the UE Associating the S-context with the corresponding V2X upper layer unicast context In an alternative embodiment shown in step S1410, the AS can In this case, V2X upper layer unicast connection can be supported in a wireless configuration. ,The AS may take into account, for example, the UE capabilities of the receiving UE,for the receiving UE AS configuration. AS connectionless approach, where AS resources are configured in a connectionless manner without In this case, the system for setting up the receiving UE, which is required before receiving the V2X packet, is There is no signaling. The receiving AS uses common default parameters for V2X packet reception. The sender sends the packet in a broadcast manner from the perspective of the AS MAC. where the encapsulated source ID and the sender ID in the received MAC PDU are The received packets are filtered based on the destination ID. In the case of the connection-oriented AS resource configuration shown, before forwarding of data packets occurs, PHY, MAC, RLC, PDCP, and SDAP in the receiving UE and transmitting UE (if applicable) is set for this particular connection. Both the transmitting and receiving UEs have PHY channel configurations that may include radio resource configurations. configuration, transport channel configuration, HARQ entity configuration, logical channel configuration, Bearer configuration, which may include security configuration, QoS flow configuration, and AS protocol AS contexts that consist of configurations, including the association of these configurations across sublayers Steps S1402 and S1404, or step S1406, are performed. Upon completion of steps S1410 and S1412, the transmitting UE and the receiving UE It is possible to exchange packets (data or signaling) in a two-way communication manner.

[0140] Step S1406 refers to link monitoring in the AS connection oriented case. Monitoring is based, for example, on radio link monitoring and beam management procedures. Link monitoring can be implemented in S. This can trigger the execution of connection maintenance procedures such as connection relocation, or disconnection. The maintenance procedure may involve the transmitting UE, the receiving UE, or a third party such as a scheduling entity. In the case of AS connectionless communication, The link monitoring mentioned in step S1414 is, for example, performed by the V2X upper layer. This is realized in the V2X upper layer based on the link keep-alive procedure executed by the In this case, link monitoring can be used to reconfigure the sender, rearrange the connection, or In this case, the link maintenance procedure can trigger the execution of the disconnection of the sending U. E, the receiving UE, or a third entity such as a scheduling entity. In step S1408, the link is released. In step S1416, the link is released.

[0141] Figure 15 shows a high-level diagram of receiver operation for Layer 2 link management, including connection establishment. In step S1500, it is determined whether an AS connection is directed. If yes, in step S1502, the Layer 2 unicast link connection establishment If no, then in step S1510, the V2X upper layer configuration is performed. Then, V2X upper layer configuration for Layer 2 unicast link connection establishment is performed. In step S1512, the V2X SL RX AS configuration, i.e., Layer 2 unicast Common signaling pre-configuration or signaling-less basis for stream connection establishment In step S1514, the V2X upper layer SL RX AS setting is performed. Link monitoring and maintenance in the ya is performed. In step S1504, the V2X SL RX AS setting is performed. , i.e., a dedicated signaling base for Layer 2 for unicast link connection establishment. In step S1506, the SL RX AS setting of the AS is performed. In step S1508, link monitoring and maintenance is performed. The release is executed.

[0142] (Detailed steps for establishing a unicast connection) Figures 16, 17, 18, 19, 20, and 21 show the unicast connection establishment and and different alternative embodiments of detailed procedures for supporting follow-up data transfer. They provide further detailed embodiments of the high level procedures shown in Figures 14 and 15. Its procedure is structured around three entities: connection establishment procedure An initiating UE (I-UE) is the UE that initiates the connection establishment request. A target UE (T-UE) and a resource configuration or resource scheduling mechanism The scheduling entity is an entity that provides the scheduling function. The gNB controls the resource configuration of other UEs or The UE that supports resource configuration, RSU-UE (i.e., Roadside Unit (RoSU) that functions as a UE) Ad Side Unit (RSU), RSU-gNB (i.e., RSU acting as a gNB) UE-to-network relay (i.e., an UE acting as a relay node towards other UEs) entity (e.g., IAB node)) or the UE under its control. In the remainder of this disclosure, the following will be used: The definition of I-UE and T-UE is further extended as follows: The T-UE for the setup procedure via the C5 interface or Uu interface E, which is the receiving UE of the setup request. The I-UE for the configuration procedure over the I-UE or Uu interface sends a configuration request. The configuration request may be a connection establishment request, a connection reconfiguration or change, a connection relocation, or There can be one or more of the disconnections.

[0143] These figures also show that one or more of the steps described in Figures 12 and 13 have already been performed. With respect to resource allocation, each of the figures also assumes that Both T-UE and I-UE communicate via RRC signaling or PC5-S signaling. After being configured in the radio resource configuration, the T-UE uses autonomous resource selection for transmission. can be used or by the scheduling entity or the I-UE It has also been proposed that I-UEs can be dynamically scheduled. Autonomous resource selection can be used for transmission or the scheduling entity can select the resource. It can be dynamically scheduled by the entity or T-UE.

[0144] 16A to 16C show the timing chart of the T-UE by the I-UE or the scheduling entity. The steps of connection establishment are shown when the connection is established by an I-UE in association with a In this embodiment of the connection establishment procedure, the V2X upper layer configuration of the T-UE is SL RRC signalling from the T-UE to the T-UE is used to synchronize the AS layer configuration of the T-UE. It is transported at times.

[0145] 16A to 16C show a target UE / RSU UP stack 1602, a target UE / RSU RRC1604, Target UE / RSU-V2X Upper Layer Functions160 6, Initiate UE / RSU RRC 1608, initiate UE / RSU UP stack 1610, The UE / RSU-V2X upper layer function 1612 and the gNB / RSU / scheduling In step S1600, the UE / RSU-V2X The communication is sent directly from the upper layer function 1612. In step S1602, UE / RSU RRC1608 sends SL RRC signaling - target device information In step S1604, the target UE / RSU RRC1 In step S1606, the target A response to the upper layer information is sent from the UE / RSU-V2X upper layer function 1606. In step S1608, the target UE / RSU RRC 1604 sends the SL An RRC signaling-target device information response is sent. In this case, from the initiating UE / RSU RRC 1608, RRC signaling - direct security In step S1612, a resource allocation command is sent. In optional step S1614, the criteria for establishing a connection can be set as It can be verified and, if necessary, establish a connection, but otherwise In step S1610a, security procedures are performed. .

[0146] In step S1616, the initiating UE / RSU RRC 1608 sends an RRC signal to the In step S1618, the SL transmission setting information request is transmitted. In step S1620, the gNB performs admission control and determination of the constant parameters. / RSU / Scheduling entity 1614 sends RRC signaling V2X signaling In step S1622, the target UE / RSU RRC1604 sends RRC signaling - Direct Security Mode Complete message In step S1624, the initiating UE / RSU RRC 1608 sends L RRC signaling - a direct communication request is sent.

[0147] In step S1628, the upper layer configuration information is transmitted. In step S1632, the T-UE protocol stack is configured. An RRC signaling-direct communication accept message is sent. In step S1636, the gNB / SL resource grant DCI information from the RSU / scheduling entity 1614 In optional step S1638, the initiating UE / RSU UP start The block 1610 transmits the SL resource grant DCI information to the target UE / RSU UP switch. In an alternative embodiment, steps S1640 and S1642 may be transmitted to the In step S1640, the target UE / RSU UP stack 1602 starts UE / RSU UP stack 1610, SR / BSR In step S1642, the initiating UE / RSU UP stack 1610 SL resource grant DCI information to the target UE / RSU UP stack 1602 In another alternative embodiment, steps S1644 and S1646 are performed. In step S1644, the target UE / RSU UP stack 1602 SR / BSR is sent to the gNB / RSU scheduling entity 1614, and In step S1646, the gNB / RSU / entity 1614 The target UE / RSU UP stack 1602 sends the runt DCI information to the target UE / RSU UP stack 1602. In step S1684, the SL data can be received or transmitted. In step S1650, reception or transmission can be performed. In step S1654, wireless link monitoring can be performed. , the release of the radio link can be performed.

[0148] 17A to 17C show the timing charts for the T-UE by the I-UE or by the scheduling entity. The steps of connection establishment are set up by the I-UE in cooperation with the 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- It is carried together with the AS layer configuration of the T-UE using PC5-signaling to the UE. In FIG. 17A to FIG. 17C, steps S1600, S1602, S1604, S1606, S1608, S1609, S1610, S1611, S1612, S1613, S1614, S1615, S1616, S1617, S1618, S1619, S1620, S1621, S16 606, S1608, S1610, S1610a, S1612, S1614, S1616 , S1618, S1620, and S1622 are the same as those in FIGS. 16A to 16C. In step S1656, the AS SL setting information is transferred. In step S1660, PC5 signaling—direct communication request is executed. In step S1662, the I-UE processor transfers the AS SL setting information. In step S1664, the T-UE protocol stack is set. In step S1666, PC5 signaling-direct communication acceptance is set. In step S1668, which may be optional, for example, SR / BSR to support Mode 2-d or Mode 2-b resource allocation may be transmitted to the gNB / RSU / scheduling entity 1614. In step S1670, which may be optional, the gNB / RSU / schedule The SL resource grant DCI is sent from the ring entity 1614. In step S1672, which may be an option, the initiating UE / RSU UP stack From step S1610, the SL resource grant DCI is transmitted. Steps S1676 is Alternative 1, and steps S1678 and S1680 are Alternative 2. In step S1674, the target UE / RSU UP stack 1602 sends the SR In step S1676, the initiating UE / RSU UP stack From step S1610, an SL resource grant SCI is transmitted. , target UE / RSU UP stack 1602 to gNB / RSU / scheduling In step S1680, the SR / BSR is transmitted to the facilitating entity 1614. gNB / RSU / scheduling entity 1614 to target UE / RSU The SL resource grant SCI is sent to the UP stack 1602. Step S168 In step S1648, the SL data is received or transmitted. In step S1686, the wireless link monitor 1686 receives or transmits the SL data. In step S1688, wireless link release is performed.

[0149] 18A to 18C show the timing charts for the T-UE by the I-UE or the scheduling entity. The steps of connection establishment are shown when the connection is established by an I-UE in association with a In this embodiment of the connection establishment procedure, the V2X upper layer configuration of the T-UE is RRC signaling from the T-UE to the T-UE is used to carry the AS layer configuration of the T-UE. Furthermore, the V2X upper layer connection establishment procedure is transmitted in accordance with the V2X AS layer connection establishment procedure. In step S1800, the initiating UE / RSU-V2X A PC5 signaling-direct communication request is sent from the upper layer function 1612. In step S1802, the target UE / RSU-V2X upper layer function 1606 PC5 signaling - direct security mode command is sent. Step S180 6, the target UE / RSU-V2X upper layer function 1606 sends a PC5 signal Nulling-direct communication acceptance information is transmitted. In step S1808, direct communication Steps S1810, S1812, S1814, and S1816 are This can be an optional step. In step S1810, the initiating UE / RS U RRC 1608 sends SL RRC signaling - target device information request. In step S1812, the target UE / RSU RRC 1604 In step S1814, the target UE / R sends a higher layer information request. A higher layer information response is sent from the SU-V2X higher layer function 1606. In S1816, the target UE / RSU RRC1604 sends the SL RRC signal In step S1818, the target device information response is sent. Source allocation can be performed (Alternative 1). Steps S1820, S1822 , S1824, and S1826 are alternative 2. In step S1820, the criteria for establishing a connection are verified and, if necessary, the connection is established. If not, perform resource allocation. In step S1822, the initiating UE / RSU RRC1608 sends RRC signaling V2X connection setup information request In step S1824, the acceptance control and determination of 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, the initiating UE / RSU RRC 1608 sends the SL RRC Signaling—A direct AS connection request is sent. In step S1830, the I-UE The protocol stack is configured. In step S1832, upper layer configuration is performed. In step S1834, the T-UE protocol stack is configured. In step S1836, SL RRC signaling - direct AS connection acceptance signal is sent Steps S1838 and S1840 are optional. Step S1838 At , an SR / BSR is sent from the initiating UE / RSU UP stack 1610. In step S1840, the initiating UE / RSU UP stack 1610 receives the SL resource Alternative 1 includes optional steps S1842 and S1844 4, and S1846. In step S1842, the target UE / RSU The UP stack 1602 receives the SL resource grant DCI. In the example, the target UE / RSU UP stack 1602 sends an SR / BSR. In step S1846, the target UE / RSU UP stack 1602 Alternative 2 includes optional steps S1848 and S1849. In step S1848, the target UE / RSU UP switch Tack 1602 sends SR / BSR to gNB / RSU / scheduling entity 16 14. In step S1850, the target UE / RSU UP stack In step S1852, the terminal 1602 receives the SL resource grant DCI. The target UE / RSU UP stack 1602 receives or transmits SL data. In step S1854, the initiating UE / RSU UP stack 1610 Therefore, the SL data is received or transmitted. Link monitoring is performed. In step S1858, wireless link release is performed. will be done.

[0151] 19A to 19C show the I-UE and the T-UE, respectively. The figure shows the steps of connection establishment when set up by a T-UE in association with a In this embodiment of the connection establishment procedure, the V2X upper layer configuration of the I-UE is PC5-S signaling from the I-UE to the I-UE is used to simultaneously configure the AS layer of the I-UE. Furthermore, the V2X upper layer connection establishment procedure is carried to the V2X AS layer connection. It is performed independently of the establishment procedure.

[0152] 19A to 19C show an initiating UE / RSU UP stack 1902, an initiating UE / RSU RRC 1904, Initiating UE / RSU-V2X Upper Layer Function 1906, Target UE / RSU RRC 1908, target UE / RSU UP stack 1910, target UE / RSU-V2X upper layer functions 1912 and gNB / RSU / scheduling In step S1900, the PC5 signaling entity 1614 is A direct communication request is sent. In step S1902, PC5 signaling-direct communication In step S1904, the PC5 signaling 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 initiating UE / RSU-V2X upper layer function 1906 Target UE / RSU-V2X upper layer function 1912, PC5 signaling - Direct A In step S1914, a direct AS connection resource request is sent. In step S1916 (alternative 1), resource allocation is performed. Alternative 2 includes steps S1918, S1920, S1922, and S1924. In step S1918 (optional), the criteria for establishing a connection are verified. If necessary, a connection is established; otherwise, resource allocation is performed. In step S1920, an RRC signaling V2X connection setup information request is sent. In step S1922, the acceptance control and determination of SL transmission setting parameters are performed. In step S1924, the RRC signaling V2X signaling configuration information response In step S1926, a direct AS connection resource response is sent. .

[0153] In step S1928, a PC5 signaling-direct AS connection acceptance message is sent. In step S1930, a direct AS connection acceptance message is sent. In step S1932, the T-UE protocol stack is configured. In step S1934, the I-UE protocol stack is configured. 1938 is optional. In step S1936, the target UE / RSU The RRC 1908 sends the SR / In step S1938, the gNB / RSU / scheduling The entity 1614 sends the SL resource to the target UE / RSU UP stack 1910. A source grant DCI is transmitted. Steps S1940, S1942, and S1944 is also an optional step as Alternative 1, steps S1946, and S Step S1948 is an optional step for Alternative 2. In step S1942, the SL resource grant DCI message is transmitted. In step S1944, the SL resource grant SC In alternative 2, in step S1946, the initiating UE / R SU UP stack 1902 to gNB / RSU / scheduling entity 161 In step S1948, the gNB / RSU / schedule Starting from the scheduling entity 1614, the RSU UP stack 1902 is In step S1950, the source grant DCI is transmitted. The stack 1902 receives or transmits the SL data. Step S19 At 52, the target UE / RSU UP stack 1910 In step S1954, radio link monitoring is performed. In step S1956, the radio link is released.

[0154] 20A to 20C show the I-UE and the T-UE, respectively. The figure shows the steps of connection establishment when set up by a T-UE in association with a In this embodiment of the connection establishment procedure, the V2X upper layer configuration of the I-UE is PC5-S signaling from the I-UE to the I-UE is used to simultaneously configure the AS layer of the I-UE. will be transported to.

[0155] 20A to 20C show an initiating UE / RSU UP stack 2002, an initiating UE / RSU RRC 1904, Initiating UE / RSU-V2X Upper Layer Function 1906, Target UE / RSU RRC 1908, target UE / RSU UP stack 1910, target UE / RSU-V2X upper layer functions 1912 and gNB / RSU / scheduling In step S2000, the initiating UE / RSU-V 2X upper layer function 1906 starts to transmit direct communication AS information to UE / RSU RRC 1904. In step S2002, the initiating UE / RSU RRC 1904 A direct communication AS information response is sent to the UE / RSU-V2X upper layer function 1906 from In step S2004, the initiating UE / RSU-V2X upper layer function 190 6 to target UE / RSU-V2X upper layer function 1912, SL PC5 signaling In step S2006, the target UE / R sends a ring-direct communication request. From the SU-V2X upper layer function 1912 to the target UE / RSU RRC 1908, A direct communication AS information request is sent.

[0156] Steps S2008, S2010, S2012, S2014, and S2016 are In step S2008 (alternative 1), Alternative 2 can perform source allocation in steps S2010 and S2012. , S2014, and S2016. In step S2010, The criteria are verified and if necessary, a connection is established, otherwise the resource allocation is In step S2012, the target UE / RSU RRC 1908 Then, an RRC signaling V2X connection setup information request is transmitted. In step S2016, the acceptance control and determination of SL transmission setting parameters are performed. In the above, the gNB / RSU / scheduling entity 1614 sends a / RSU RRC1908 receives RRC signaling V2X signaling configuration information response In step S2018, the target UE / RSU RRC 1908 Initiating UE / RSU RRC1904, RRC signaling - direct security mode control In step S2018a, a security procedure is performed. In step S2020, the initiating UE / RSU RRC 1904 sends the RRC signaling - Direct security mode complete for UE / RSU RRC1908 In step S2022, the 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, target UE / RSU-V2X upper layer functions 1912 to Initiate UE / RSU-V2X upper layer function 1906, SL PC5 signaling - direct In step S2028, the initiating UE / RSU-V 2X upper layer function 1906 starts from UE / RSU RRC 1904, AS layer configuration An information transfer message is sent. In step S2030, the I-UE protocol Steps S2032 and S2034 are optional. In step S2032, the target UE / RSU UP stack 1910 receives the gN The SR / BSR is sent to the B / RSU / scheduling entity 1614. In step S2034, the gNB / RSU / scheduling entity 1614 The SL resource grant DCI is sent from the UP stack 1910 to the target UE / RSU. It is believed.

[0158] In step S2036 (optional step), the target UE / RSU U Starting from P stack 1910, UE / RSU UP stack 2002 receives SL resource graphs. Steps S2038 and S2040 are optional. Step S2038 is the step of Alternative 1. In step S2038, the initiating UE / RSU From the UP stack 2002 to the target UE / RSU UP stack 1910, In step S2040, the target UE / RSU UP stack Starting from Q1910, UE / RSU UP stack 2002, SL resource grant SC In alternative 2, in step S2042, the initiating UE / RSU UP From the stack 2002 to the gNB / RSU / scheduling entity 1614, the SR In step S2044, the gNB / RSU / scheduling The UE / RSU UP start entity 1614 initiates the SL resource grant DCI. In step S2046, the sidelink data is transmitted to the block 2002. In step S2048, the sidelink data is transmitted or received. In step S2050, radio link monitoring is performed. In step S2052, radio link release is performed.

[0159] 21A to 21C show the I-UE and the T-UE, respectively. The figure shows the steps of connection establishment when set up by a T-UE in association with a In this embodiment of the connection establishment procedure, the V2X upper layer configuration of the I-UE is It is carried simultaneously with the AS layer configuration of the I-UE using RRC signaling from the I-UE to the I-UE. will be sent.

[0160] In step S2100, from the initiating UE / RSU-V2X upper layer function 1906 Step S2102: A direct communication request is sent to the initiating UE / RSU RRC 1904. In the example, the initiating UE / RSU RRC 1904 sends the At step S2104, a SL RRC signaling-direct communication request is sent. In this case, the target UE / RSU RRC1908 sends the 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 RRC 1908. In step S2108 (alternative 1), resource allocation is performed. , including steps S2110, S2112, S2114, and S2116. 2110, in an optional step, criteria are verified for connection establishment and, if necessary, If so, a connection is established, otherwise resource allocation is performed. 12, the target UE / RSU RRC1908 sends the An RRC signaling V2X connection setup information request is sent to the RRC signaling entity 1614. In step S2114, the acceptance control and determination of the SL transmission setting parameters are performed. In step S2116, the gNB / RSU / scheduling The entity 1614 sends the RRC signaling V2X signaling configuration information response to the target. In step S2118, the target UE / RSU RRC 1908 receives the UE / RSU RRC 1908 starts UE / RSU UP stack 2002, RR C signaling-direct security mode command is sent. Step S2118a In step S2120, the initiating UE / R performs a security procedure. RRC signaling is sent from the SU RRC 1904 to the target UE / RSU RRC 1908. ing-direct security mode complete message is sent.

[0161] In step S2122, the T-UE protocol stack is configured. At 2124, the target UE / RSU RRC 1908 An SL RRC signaling-direct communication accept message is sent to the RC 1904. In step S2126, the I-UE protocol stack is configured. 28. In an optional step, the target UE / RSU UP stack 1910 SR / BSR is sent from the gNB / RSU / scheduling entity 1614 In step S2130, the gNB / RSU / scheduling entity 1 614 sends the SL resource grant DCI message to the target UE / RSU UP start In step S2132, an optional step, the target The UE / RSU UP stack 1910 sends the SL resource grant DCI message. Steps S2134 and S2135 are sent to the initiating UE / RSU UP stack 2002. Steps S2138 and S2140 are alternative 2. In step S2134, the initiating UE / RSU UP stack 2002 sends the target UE / RSU UP An SR / BSR message is sent to the E / RSU UP stack 1910. In S2136, the target UE / RSU UP stack 1910 An SL resource grant SCI message is sent to the SU UP stack 2002 . In step S2138, the initiating UE / RSU UP stack 2002 to the gNB / R An SR / BSR message is sent to the SU / scheduling entity 1614. In step S2142, the initiating UE / RSU UP stack 2002 In step S2144, the target The UE / RSU UP stack 1910 controls the transmission or reception of sidelink data. In step S2146, radio link monitoring is performed. In step S2148, radio link release is performed.

[0162] (Unicast connection setting parameters) (UE support information) Unicast connection settings, groupcast connection settings, or broadcast connection settings To support this configuration, the T-UE may pass one or more of the following configuration parameters to the I-UE: or a scheduling entity. Such information may be provided to the PC T-UE acting as a receiving UE with protocol stack configuration across five interfaces Therefore, the scheduling entity, or I-UE, can also or can be set by the I-UE in cooperation with a scheduling entity Examples of related use cases are shown in Figures 16, 17 or 18. Alternative Embodiments In this case, the I-UE may specify one or more of the following configuration parameters to the T-UE or the scheduler: Such information can be provided to the PC5 interface. This is provided by the I-UE, which acts as the receiving UE for protocol stack configuration throughout the Therefore, the scheduling entity, or the T-UE or the scheduler This can be configured by the T-UE in conjunction with the relevant operating entity. Examples of such a source are shown in Figure 18, Figure 20 or Figure 21. One or more of the following information may be included in the IU: It is provided to both the E- and T-UE scheduling entities and is not used by the I-UE or T-UE. -Can support scheduling entities for UE configuration.

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

[0164] (T-UE or I-UE setting parameters) A scheduling entity, or an I- in conjunction with a scheduling entity To support connection setup by the UE, one or more of the following parameters may be configured in the T-UE: Examples of such connection settings are shown in Figs. 16, 17, and 18. 18. Similarly, the scheduling entity Supports connection setup by the T-UE in cooperation with the QoS entity or scheduling entity To achieve this, one or more of the following parameters can be set in the I-UE: Examples of suitable connection setup procedures include the connection establishment procedures shown in Figures 19, 20, and 21. It can be done.

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

[0166] (Groupcast connection management) (High-level Groupcast connection management procedures) Figure 22 shows the sender operation for groupcast Layer 2 link management, including connection establishment. In step S2200, it is determined whether the AS is connection-oriented. Step S2202 and step S2210 are performed to determine whether V2X communication is performed between peer V2X UEs. Groupcast connection establishment and connection contention in V2X upper layer (V2X UpL) The groupcast connection also refers to the association of a message. As described above, before forwarding a groupcast packet, the group UEs and group members Group Lead U for AS context configuration and association between V2X UEs The connection establishment signaling between the V2X UE and the group member V2X UE is used to establish the connection at the AS layer. In this case, the group member V2X UE receiver can Considering UE capabilities, this may include dedicated radio resource configuration for unicast reception. As part of the groupcast connection establishment procedure, UEs involved in groupcast communication will transfer the groupcast AS context to the corresponding V2X upper layer The earphone groupcast context can be associated with the earphone groupcast context. In an alternative embodiment, the AS may communicate with the V2X upper layer group in an AS connectionless configuration. Broadcast connections can be supported.

[0167] In this case, the AS may allocate AS resources without considering, for example, the group member UE capabilities. The AS is configured in a connectionless manner. In this case, Signaling for configuration of receiving group member UEs required before receiving V2X packets The receiving group member AS has a common node for receiving V2X groupcast packets. The sender is configured with the default parameters for broadcasting from the perspective of the AS MAC. The packet is sent in a standard manner, where the encapsulated Filtering of incoming packets is performed based on source and destination IDs. In the continuity-oriented AS resource configuration illustrated in step S2204, data packets are forwarded. Before transmission, the receiving UE and the transmitting UE must have PHY, MAC, RLC, and PDCP , and SDAP (if applicable) configured for this particular groupcast connection. Before forwarding a groupcast data packet, both the sending and receiving UEs , PHY channel configuration, which may include physical layer multicast radio resource configuration; Transport channel configuration, HARQ entity configuration, logical channel configuration, security Bearer configuration, which may include service configuration, QoS flow configuration, and AS protocol subroutines Groupcast AS consists of settings, such as the association of these settings across layers A context is created. When step S2210 and step S2212 are completed, the transmitting UE and the receiving UE , exchange packets (data or signaling) in a groupcast connection-oriented communication method It is possible.

[0168] Step S2206 is a link monitoring step in the case of AS groupcast connection-oriented communication. Link monitoring refers to, for example, radio link monitoring and beamforming. This can be realized in the AS based on the control procedure. It can trigger the execution of connection maintenance procedures such as relocation or disconnection. The protection procedure may be performed by the transmitting UE, the receiving UE, or a third party such as a scheduling entity. It can be triggered by the AS groupcast connectionless entity. In the case of communication, the link monitoring mentioned in step S2214 is performed, for example, on V2X. Based on the link keep-alive procedure performed by the V2X upper layer, In this case, link monitoring is implemented by reconfiguring the sender, reconnecting, etc. Groups, including placing, disconnecting, or leaving a group and joining a new group In this case, the link maintenance procedure can trigger the sending side to perform a link reconfiguration. by the UE, the receiving UE, or a third entity such as a scheduling entity. In step S2208, the unlinking is performed. Also, in step S2216, the link is removed.

[0169] Figure 23 shows the receiver operation for groupcast Layer 2 link management, including connection establishment. A high level illustration is provided. In step S2300, whether the AS is connection-oriented is determined. If yes, in step S2302, the V2X upper layer configuration is If no, step S2 is performed to establish a Layer 2 unicast link connection. In 310, the V2X upper layer configuration is In step S2304, V2X SL RX AS setting, that is, Dedicated Signaling-Based Scheme for Layer 2 Groupcast Link Connection Establishment L RX AS setting is performed. In step S2306, the link monitor in the AS Monitoring and maintenance is performed. In step S2308, unlinking is performed. In step S2312, the V2X SL RX AS is configured, that is, the Layer 2 Pre-configuration or signaling of common signaling for establishing groupcast link connections In step S2314, the SL RX AS setting without any routing is performed. Step S231: Link monitoring and maintenance at the 2X upper layer is performed. At 6, the unlinking is performed.

[0170] The details of the groupcast connection establishment procedure are the same as the unicast procedure. The parameters are the same as those in the "T-UE or I-EU configuration parameters" and "UE assistance information" mentioned above. ", similar to that described above.

[0171] In one embodiment, groupcast communication is performed using the method described in the section entitled "Unicast Connection Management." Group member UEs are individually configured using the unicast configuration procedure described in section Similarly, connections for new group members can be set up by It can be added using the unicast connection setup procedure.

[0172] In an alternative embodiment, the groupcast connection is established in a group manner. For a given group, the specific UE capabilities to support connection-oriented communication for that group are Such capability can be requested from group member UEs. , SIM or ME) or by a scheduling entity, e.g. For example, by a UE acting as a scheduling entity or a group lead. Broadcast signaling or scheduling entities for resource configuration The V2X control function is configured in the UE via the V2X support function. For example, to request connection setup or Support information including scheduling configuration of group members to discover follow-up configuration information; Such information can be sent via dedicated signaling to group member UEs. It can be provided by SL-MCCH (SL multicast) or, for example, control channel) in a groupcast manner, or Using SCCH (Sidelink Control Channel) via SL-SCH (SL Shared Channel) or STCH (Side Link Channel) via SL-SCH (SL Shared Channel) Use the SBCCH (Sidelink Broadcast Channel) or This can be provided in a broadcast manner using a group control channel. The broadcast connection setup information is signaled on the SL-MCCH or on the SL-SCH (S Use SCCH (Sidelink Control Channel) over L shared channel or if Or STCH (Sidelink Traffic Channel) via SL-SCH (SL Shared Channel). Channel) or SBCCH (Sidelink Broadcast Control Channel) The configuration information can be provided by broadcasting it periodically. can be signaled to

[0173] The configuration parameters described in the section entitled "Configuration Parameters for T-UE or I-UE" In the meter, the destination ID in the bearer setup is the groupcast group identifier.

[0174] The group management function is performed by the V2X upper layer or application layer. When this is the case, for effective and efficient groupcast connection management from the viewpoint of radio resource management, For this reason, the group provided to the AS by the V2X upper layer may be too large. The AS assigns the upper layer V2X group to the PH to support groupcast communication. The AS can be subdivided into subgroups that are communicated to the Y layer. with a mapping between the group ID and the corresponding larger group Layer 2 destination ID. , each subgroup can be assigned a Layer 2 destination ID. A table of mappings between Layer 2 destination IDs of the corresponding larger groups and their corresponding IDs. The groupcast connection setup in the UE is directed to the subgroup Layer 2. A table of mappings between destination IDs and corresponding larger group Layer 2 destination IDs In one embodiment, the subgroup destination ID and the group destination ID may include In addition to the table of associations, the groupcast connection configuration configured in the UE is Indication of whether V2X data of the loop destination ID should be relayed and the data received by the UE The data may include an indication of whether the data is requested to be relayed. For cast, the AS can configure the PHY with one or more of the following information: Group Layer 2 Destination ID. V2X UE ID of group members (e.g., ProSe UE ID, UE ID) or any other identifier that can be used by the UE as the source ID of a member UE. 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 Or instructions requesting not to relay.

[0175] (Settings for V2X broadcast communication) A high-level illustration of AS configuration for broadcast V2X communication is shown in Figure 1 for the sender side. The receiver side is shown in Figure 24 and the receiver side is shown in Figure 25. In Rio, the T-UE, i.e., the UE receiving the configuration request, is assigned a UE status based on, for example, the UE capabilities. Instead, the AS protocol stack uses the Based on the settings specified in the default parameters or in the UE (SIM or ME) based on pre-configured settings in the UE or provisioned to the UE by, for example, the V2X control function. The AS is configured based on the configured settings. configured with a broadcast resource that carries the source ID and the Layer 2 destination ID. Therefore, from the perspective of the AS protocol stack configuration, it is a transmission connectionless, but The layer is a unicast layer in the V2X upper layer where the Layer 2 context is configured. V2X over peer connections or groupcast connections maintained by the V2X upper layer It is noted that the association between the upper layer contexts can still be maintained. In step S2400 of FIG. 24, V2X SL TX AS setting, that is, Pre-configuration of common signaling for SL TX AS settings for broadcast-based transmission Alternatively, the use of dedicated signaling-based configuration is performed. The signaling for context setup including association between V2X UE and peer V2X UE is For example, one or more of the following may be used to support a secure data link: . - Connectionless transmission of user data in a connectionless manner where each MAC PDU carries a source and destination ID. PC5-S signaling via the cytoplasmic plane. PC5-S signaling over the user plane in an AS connection oriented manner. There is already an AS connection (e.g., unicast) between the two V2X UEs involved in V2X communication. This can happen if there is a ·PC5-S messages embedded in RRC signaling messages.

[0176] In step S2500 of FIG. 25, V2X SL RX AS setting, that is, Pre-configuration of common signaling for SL RX AS configuration for broadcast-based reception Alternatively, the use of a signaling-free base configuration is performed.

[0177] In the next section, a method for UE handling of multiple simultaneous sidelink RRC connections is described. This article explains:

[0178] (PC5 RRC connection status) Based on the discussion in the previous sections, two peer UEs communicate via a V2X communication link. Before communicating via the PC5 RRC connection, it may be necessary to initiate a PC5 RRC connection. The steps for establishing a connection are described below and illustrated in FIG. Step S2600. A peer wants to communicate over the PC5 interface. PC5-S signaling (DIRECT_COMMUNICA TION_REQUEST). Step S2602. UE capability exchange between two peer UEs Step S2604: Configure the access stratum (AS) of the peer UE to enable V2X communication. fixed Step S2606. UE-to-UE communication via PC5

[0179] During steps S2600 to S1604, the UE In this state, the UE receives a (pre-)configured communication profile. monitors the peer UE for any possible PC5-S signaling messages from the peer UE In this state, all communications with the UE are performed via the sidelink common control channel. This can be thought of as being done over the SL_CCCH channel. Upon receiving a COMMUNICATION REQUEST, the UE sends PC5 signaling The layer determines whether a direct link is allowed and responds to the peer UE. If allowed, the UE sends DIRECT_COMMUNICATON_ACCEPT. Subsequently, the RRC layer exchanges UE capabilities and access stratum configuration with the peer UE. These exchanges can also be made via SL_CCCH. After successful completion, the UE can be considered to have established a PC5 RRC connection, and In this state, the UE can transition to the RRC_CONNECTED state. , Control information is sent via the sidelink dedicated control channel (S_DCCH). User data can be transmitted via the SL_DTCH. , Can have sidelink radio bearer setup for communication with peer UEs , A reference signal is required to be transmitted to assist peer UEs in measuring channel quality. There is a possibility, May be required to act as a synchronization reference source and transmit system information signals can be, Monitors side link status to assess link quality, declares link failure, and You can take action accordingly.

[0180] In the above, it is assumed that the PC5 RRC connection is established immediately after the AS configuration exchange. Alternatively, the PC5 RRC connection is set to PC5RRCConnectionSet The confirmation is made after a subsequent signaling exchange between UE1 and UE2 using the form of an up message. It can stand.

[0181] A PC5 RRC connection between two peer UEs is established with one UE acting as the master of the connection. In this case, one UE acts as the slave of the connection. Only the master of the connection can manage the PC5 RRC connection. For example, if UE1 has a PC5 RRC connection with UE2, If initiated, UE1 can become the master of the PC5 RRC connection and UE2 can become the slave. Alternatively, after the capability exchange shown in step S2602, UE1 can It can be determined that UE2 should be the master of the PC5 RRC connection, and UE1 can request that UE2 act as master (e.g., AS configuration state) or optionally in a dedicated PC5RRCConnectionSetup step UE1 may make a decision based on many factors, including one or more of the following: do. Current load, e.g. if there are many active RRC connections, UE2 will be the master. You can ask it to work. Connectivity to the cellular network / quality of the Uu link. If UE1 is out of coverage In this case, UE2 can be asked to act as the master. Power status. If the UE2 has more power or is powered down from the mains (e.g. When powered by a power supply (connected to the port), UE1 will ask UE2 to act as the master. It can be expected that the function of Ability. UE1 does not have the ability to function as a master, so it assigns the master to UE2. It can be asked to function as

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

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

[0184] (Keep UE1 in connected mode) This process can monitor the number of simultaneous PC5 RRC connections, and this number is configurable. If the threshold (K) is greater than the threshold (K) that can be used, UE1 will terminate the RRC connection to the gNB as RRC_CONN ECTED mode, so that UE1 can be scheduled first. Buffer Status Request to the gNB without the need to send a buffer status request. t:BSR) report, which allows the sidelink transmission on PC5 to be This can speed up resource allocation for UE1 (to gNB) If the UE is in IDLE mode and the number of PC5 RRC connections exceeds this threshold, the UE E1 is requesting a connection so that it can send a BSR for sidelink transmission. Initiate an RRC connection with the gNB using an establishment cause configured to indicate to the gNB that For example, the establishment cause can be "sidelinkResourceAllo cation".

[0185] (Disconnect all RRC connections) This process involves receiving a request from the gNB to stop all sidelink communications. A UE in RRC_IDLE mode (with respect to a gNB) can perform autonomous resource selection. In some cases, the gNB may use To limit interference to neighboring cells and / or reduce cell load, all It may be necessary to stop sidelink transmissions. In such cases, RRC_IDL gNB provides a mechanism to inform the UE to transition to E and stop all sidelink transmissions. For example, the gNB may need to provide a This message moves UE1 to RRC_IDLE. It may also include an instruction to release one or more or all PC5 RRC connections. Upon receiving the message from the NB, UE1 sends a Based on Figure 27, this means that PC5 RRC connection 2 and PC5 is for RRC connection 3. At the same time, UE1 sends PC 5. Send an RRCConnectionReleaseIndication message. This allows these UEs to release the PC5 RRC connection to UE1. The RCConnectionReleaseIndication includes the reason for the release. (e.g., "gNB unlock").

[0186] (PC5 RRC connection priority management) Each PC5 RRC connection can be assigned a priority at setup time. One process can monitor the priority of all PC5 RRC connections and These PC5 Rs are based on many factors such as available power, load, and proximity to peer UEs. It may be decided to pause or release one or more of the RC connections. When used together, PC5 RRC connection 3 can be the highest priority. The UE can suspend or release PC5 RRC connections 1, 2, and 4 accordingly. UE1 releases all PC5 RRC connections for which it is the master. Based on Figure 27 For example, this is for PC5 RRC connection 2. At the same time, UE1 is connected to UE2 and and UEk sends PC5RRCConnectionReleaseIndication message message to cause these UEs to release the PC5 RRC connection to UE1. PC5RRCConnectionReleaseIndication indicates A reason for removal may be included (e.g., "Deprioritized").

[0187] (PC5 unicast link granularity, unicast link updates, and unicast link (Additional hand) In LTE D2D, the direct link setup procedure is used to establish a link between two ProSs. Establish a secure direct link between e-enabled UEs. AS configuration is performed between the initiating UE and the target UE. As described herein, in NR V2X, unicast Establishing a stream link involves an AS (Access Stratum) configuration exchange between the initiating UE and the target UE. An example of such a configuration is the configuration for the bearer. Such bearer configuration is associated with V2X services supported on unicast links. The corresponding QoS flow needs to be configured in the V2X layer. QoS Flow Identifier (QFI), i.e., the finest granularity available. The OS level relates to V2X services supported over PC5 unicast links. PQI and packet filter set that are mapped to the AS bearer configuration The V2X application running on the UE includes QoS characteristics identified in the QoS rule having the following characteristics: The application routes the data traffic associated with each service into 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 the UE, and each application can: It can generate data to support different services, and the data from each service can be The data can be mapped to one or more QoS flows.

[0188] Based on the above, a direct PC5-S link setup procedure for NR V2X is The order is to use V2X Raytheon to support service data carried over the PC5 link. In addition to setting up QoS flows between the peers, it also sets up a secure link between two V2X peer UEs. Therefore, PC5 direct unicast link setup The procedure is described as establishing a security context for a secure link between peer V2X UEs, and Supports service(s) data carried over unicast links It is proposed to be used for both QoS flow configuration and for

[0189] (Unicast link modeling) Model 1

[0190] As shown in Figure 28, there is only one unicast link between two peer V2X UEs. No. The PC5 unicast link establishment procedure establishes a secure link between two peer V2X UEs. and configure QoS flows for one or more services, where the services are , which are mapped to one or more applications. In this model, the establishment of a security context is essential for subsequent QoS flows. The addition of is proposed to be achieved by the PC5 unicast link update procedure. This procedure essentially involves setting up additional QoS flows after the unicast link is established, A QoS flow consists of one or more subroutines transported over a PC5 unicast link. The security context is mapped to the data of the unicast may not be updated as part of the link update procedure and therefore may not be updated in a unicast link update. There may be cases where security parameters are not 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 two peer UEs. As shown in Figure 29, there are two peer applications for each pair of two peer UEs. There is one unicast link between the applications.

[0193] In this embodiment, the PC5 unicast link establishment procedure is performed between two peer V2X UEs. Create secure links between them and configure QoS flows for one or more services. Here, a service is mapped to one application. , creating two or more unicast links simultaneously during the same unicast link establishment procedure. The PC5 unicast link establishment procedure provides a secure link between two peer V2X UEs. Create a link and configure QoS flows for one or more services, where the services In this model, a service is mapped to two or more applications. It is proposed that the addition of QoS flows is achieved by the PC5 unicast link update procedure. This procedure is essentially a way to add additional QoS flows after the unicast link is established. The QoS flow is transported over the PC5 unicast link. It is mapped to the data of one or more services. It is added via a PC5 unicast link. One or more services to be added may be added to the unicast link established during the unicast link establishment procedure. It can belong to an existing application that has a link or links. In this model, a new unicast link management procedure, i.e., PC5 unicast It is also proposed to introduce a link addition procedure, which is a procedure for two peer V2X applications. V2 adds additional links between applications and adds new unicast links One or more QoS flows to support one or more services of the X application. This procedure can be used 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. Therefore, there may be cases where security is required between V2X peer UEs during the unicast link update procedure. In some cases, the parameters may not be exchanged.

[0194] Model 3

[0195] In this model, there are two or more PC5 unicast links between two peer UEs. There may be two peer UEs, one for each service, as shown in Figure 30. There are unicast links.

[0196] In this embodiment, the PC5 unicast link establishment procedure is performed between two peer V2X UEs. It creates a secure link between them and also sets up QoS flows for one service. In an alternative embodiment, two or more unicast links may be established during the same unicast link establishment procedure. The PC5 unicast link establishment procedure is the same as that of the two peer V2 It creates a secure link between V2X UEs and also provides QoS functions for one or more V2X services. A row is configured where a 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. This procedure is basically the same as that of a unicast link. After the establishment, additional QoS flows are configured and the QoS flows are routed via the PC5 unicast link. It maps to the data of one or more existing services that are transported via P One or more services added over the C5 unicast link must be Existing applications that have unicast link(s) established during the setup procedure In this model, a new unicast link management method is It is also proposed to introduce a PC5 unicast link addition procedure. This procedure adds an additional link between two peer UEs for a new service and establishes a new uniform One or more Qo to support V2X services with additional cast links This procedure allows you to add two or more unicast links at the same time. The security context is updated as part of the unicast link update procedure. Therefore, security may not be possible between V2X peer UEs during the unicast link update procedure. Security parameters may not be exchanged.

[0197] An exemplary embodiment of the present disclosure includes a processor (e.g., processor 118), a memory (e.g., For example, non-removable memory 130, removable memory 132, etc.), and communication circuitry. a first device (UE, e.g., a mobile device) including a first device (UE, e.g., a mobile device) devices 102a, computers, vehicles (e.g., automobiles 102b, motorcycles, boats, etc.) The first device provides a communication network (e.g., RAN103 / 104 / 105 / 103b / 104b / 105b). The apparatus of claim 1 further includes computer-executable instructions stored in the memory, and the computer The executable instructions, when executed by the processor, cause the first device to a second device (second UE, e.g., a mobile device 102a, a computer, a vehicle, (e.g., a car 102b, a motorcycle, a boat, etc.)) and and causing associated device information to be obtained and a first device to communicate with the second device directly via sidelink. Configure the device's wireless protocol (e.g., PC5 signaling protocol).

[0198] In an exemplary embodiment, a first device may transmit to a second device a device associated with the second device. The second device initiates retrieval of device information associated with the second device by sending a request for device information. (e.g., FIG. 16A, SL RRC signaling - target device (See Service Information Request).

[0199] In an exemplary embodiment, a first device may request device information associated with a second device. Responses (e.g., FIG. 16A, SL RRC signaling) can be received. The Response (see Response - Target Device Information Response) contains device information related to the second device. nothing.

[0200] In an exemplary embodiment, the device information associated with the second device includes device capabilities, V2X This includes one or more of the QoS configuration parameters for the communication and sidelink measurements. 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 bands and sub-bands The sidelink measurements can relate to one or more of the following: RF, including capabilities, etc. For example, it can be RSRP, RSRQ, RSSI, CBR, CR, etc.

[0201] In an exemplary embodiment, the first device may The wireless protocol configuration parameters of the second device can be determined. Alternatively, the first device may receive from a third device (e.g., a scheduling entity): Wireless protocol setting parameters of the first device and wireless protocol setting parameters of the second device and requesting a meter to obtain wireless protocol configuration parameters of the first device and the wireless protocol of the second device. Protocol configuration parameters can be received.

[0202] In an exemplary embodiment, determining the wireless protocol configuration parameters of the second device includes: Consider the device information associated with the second device. In an exemplary embodiment, The determination of the wireless protocol configuration parameters is based on device information associated with the second device and the first Consider device information related to the device.

[0203] In an exemplary embodiment, the first device receives wireless protocol configuration parameters of the second device. The data can be transmitted to the second device, or the second device can receive the data from the second device's wireless protocol. Protocol configuration parameters may be received from a third device. The wireless setting parameters of the second device sent to the second device are stored in the wireless profile of the second device. Used by the second device to set the protocol.

[0204] In an exemplary embodiment, a first device may transmit to a second device a device associated with the first device. In an exemplary embodiment, the first device may transmit device information associated with the first device. The location information includes device capabilities, QoS configuration parameters for V2X communication, and sidelink measurements. Contains one or more of the values.

[0205] In an exemplary embodiment, a PC5 interface (see, e.g., FIG. 10) is a first PC5 RR allows communication between the device and a second device via the PC5 interface In an exemplary embodiment, PC5-C signaling or PC5-S signaling is used. , the PC5 interface allows communication between a first device and a third device, or The PC5 interface allows communication between a second device and a third device. In one embodiment, PC5 RRC signaling or PC5-S signaling is It can be used via PC5 interface.

[0206] In an exemplary embodiment, the wireless protocol includes, for example, an SDAP layer, a PDCP layer, and The layer includes an RLC layer, a MAC layer, and a PHY layer. For example, FIG. 2 and FIG. Please refer to 6.

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

[0208] In an exemplary embodiment, the first device is a transceiver (e.g., transceiver 12 0) allows data to be sent from a first device to a second device.

[0209] In an exemplary embodiment, the third device is a roadside unit (e.g., RSU 120b), a base station, or the like. 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 includes a processor (e.g., processor 118) , memory (e.g., non-removable memory 130, removable memory 132), and The second device includes a communication circuit (e.g., including a transceiver 120). The second device is connected to a communication network via a computer stored in a memory. The computer-executable instructions include executable instructions that, when executed by a processor, and causing the second device to: 1) determine wireless protocol configuration parameters of the first device; or 2) determining wireless protocol configuration parameters of the first device from a third device. wireless protocol setting parameters of the first device and wireless protocol setting parameters of the second device and requesting the wireless protocol setting parameters of the first device and the wireless protocol setting parameters of the second device. In an exemplary embodiment, the first device receives a wireless protocol configuration parameter. The determination of the protocol configuration parameters takes into account device information associated with the first device, or The determination of the wireless protocol configuration parameters of the first device may be performed by a device associated with the second device. In an exemplary embodiment, the first device is configured to receive the first request and the second request. The second device transmits wireless protocol configuration parameters of the first device to the first device. or the first device may update wireless protocol configuration parameters of the first device to the third device. In an exemplary embodiment, the first device may receive the The wireless configuration parameters of the first device are sent to the first device to configure the wireless protocol of the first device. Used by the device.

[0211] In an exemplary embodiment, a first device may transmit to a second device a device associated with the first device. The device information associated with the first device may include device capabilities, V QoS configuration parameters for the 2X communication, and one or more of sidelink measurements. The device includes a processor, a memory, and a communication circuit. The second device communicates with the processor via the communication circuit. The second device is connected to a communications network. The computer-executable instructions include computer-executable instructions that, when executed by a processor, The second device determines wireless protocol configuration parameters of the first device and wirelessly transmits the second device's wireless protocol configuration parameters. Alternatively, the second device may receive from the third device: Wireless protocol setting parameters of the first device and wireless protocol setting parameters of the second device and requesting a meter to obtain wireless protocol configuration parameters of the first device and the wireless protocol of the second device. Protocol configuration parameters can be received.

[0212] An exemplary embodiment of the present disclosure includes a first device including a processor, a memory, and a communication circuit. a first device communicating with a second device via a communication circuit; The method includes: a first device identifying a second device with which it can communicate; Discovering and obtaining device information associated with the second device; and communicating with the second device. and configuring a radio protocol of the first device for direct sidelink communication.

[0213] An exemplary embodiment of the present disclosure is a non-transitory computer-readable storage medium having computer-readable instructions tangibly recorded thereon. a computer-readable storage medium, the computer-readable instructions being executable by a processing circuit; and causing the processing circuit to perform a method for direct sidelink communication using the first device. The method includes a first device discovering a second device with which it can communicate and a second device associated with the second device. and obtaining device information for direct sidelink communication with the second device. and configuring the wireless protocol of the device.

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

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

[0216] In an exemplary embodiment, one PC5 unicast link may carry one or more services. Type is at least one of the peer applications for this pair of PC5 unicast links. If also associated with it, it supports one or more service types.

[0217]

[0218] Any of the methods and processes described herein may be stored on a computer-readable storage medium. embodied in the form of stored computer-executable instructions (i.e., program code) The instructions can be transmitted to a computer, a server, an M2M terminal device, an M2M gate, When executed by a machine, such as a data entry device, the systems, methods, and It will be understood that the methods and processes used in the present invention may include: , any of the steps, acts, or functions described above may be implemented by such computer-executable instructions. The computer-readable storage medium may be implemented in the form of a computer program. Volatile and non-volatile, removable and detachable, implemented in any manner or technology Such computer-readable storage media include non-transitory media, but do not include signals. The computer readable storage medium may include RAM, ROM, EEPROM, flash memory or does not include other memory technologies, CD-ROM, Digital Versatile Disc (DVD) or other optical discs Disk storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic Any storage device or computer that can be used to store desired information. This includes, but is not limited to, other physical media that can be accessed by a computer. It will not be done.

[0219] In describing preferred embodiments of the subject matter of the present disclosure as illustrated in the figures, particular reference will be made to the drawings for clarity. Certain terms are employed. However, claimed subject matter is not limited to those so selected. It is not intended to be limited to a specific term, and each specific element may accomplish a similar purpose. It should be understood that the present invention includes all technical equivalents which operate in a similar manner for the purposes of the present invention.

[0220] Therefore, the disclosed system and method may not deviate from its spirit or essential characteristics. Those skilled in the art will appreciate that the present invention may be embodied in other specific forms without departing from the spirit and scope of the present invention. The presently disclosed embodiments are therefore considered in all respects to be illustrative. It is not intended to be exhaustive or to be limiting as disclosed. Nor is it intended to limit the disclosure to the precise form, and modifications and variations are possible in light of the above teachings. or that may be acquired from practice of the present disclosure without departing from the breadth or scope thereof. Therefore, although a particular configuration has been described herein, other configurations may also be used. Numerous modifications and other embodiments (e.g., combinations, rearrangements, etc.) are possible. ) are possible due to the present disclosure and are within the skill of the art, and are within the scope of the disclosed subject matter and The present invention is intended to fall within the scope of any equivalents thereof. may be combined, rearranged, and simplified within the scope of the present invention to produce additional embodiments. Furthermore, certain features may sometimes be used in conjunction with other features. Therefore, the applicant(s) may use the invention to their advantage without All such alternatives, modifications, equivalents, and equivalents falling within the spirit and scope of the subject matter indicated are hereby expressly excluded. It is intended to encompass all such modifications and variations.

[0221] References to singular elements are to "one and only one" unless expressly stated as such. "A, B, or When a phrase similar to "at least one of" is used in a claim, that phrase The phrase "A" can only be present in the embodiment, and "B" can only be present in the embodiment. that only C can be present in an embodiment, or that A, B and C It is understood that any combination of elements may be present in a single embodiment, for example, A and and B, A and C, B and C, or A, B and C. This is the intention.

[0222] Unless an element is expressly recited herein using the phrase "means for," Unless otherwise specified, no claim element shall be construed under the provisions of 35 U.S.C. § 112(f). As used herein, the terms "comprise," "include," or other similar terms are not intended to be limiting. The term "variant" is intended to cover a non-exclusive inclusion and does not include any element consisting of a list of elements. A process, method, article, or apparatus includes, but is not limited to, those elements. Any process, method, article, or apparatus not expressly listed or inherent in such The scope of the invention is defined by the appended claims, rather than the foregoing description. All claims and all claims within the meaning, scope and equivalence of the claims. are intended to be encompassed therein.

Claims

1. a processor; Memory and a communication circuit, wherein the first device communicates via the communication circuit. the first device is connected to a communication network, and the first device is connected to a computer implementation stored in the memory. and further comprising computer-executable instructions, the computer-executable instructions being executed by the processor. When executed, the first device causing the first device to discover a second device with which it can communicate; obtaining device information associated with the second device; a radio protocol of the first device for direct sidelink communication with the second device; Let it be set, First device.

2. The computer-executable instructions further cause the first device to: by sending a request to the second device for the device information associated with the second device; Therefore, the acquisition is started. The first device of claim 1 .

3. The computer-executable instructions further cause the first device to: receiving a response to the request for the device information associated with the second device; the response includes the device information associated with the second device. The first device of claim 2 .

4. The device information related to the second device may include device capabilities, QoS settings for V2X communication, 4. The first method of claim 3, wherein the first parameter comprises one or more of: a constant parameter; and a sidelink measurement. Equipment.

5. The computer-executable instructions further cause the first device to: determining wireless protocol configuration parameters of the first device and Determine protocol configuration parameters, or from a third device, the wireless protocol setting parameters of the first device and the second device; and causing the wireless protocol setting parameters of the first device to be requested, and and receiving the wireless protocol configuration parameters of the second device. to make, The first device of claim 1 .

6. The determining of the wireless protocol configuration parameters of the second device includes: taking into account the relevant device information or the wireless protocol of the second device The determination of the configuration parameters is based on the device information associated with the second device and the first device. The first device of claim 5 , taking into account device information associated with the device.

7. The computer-executable instructions further cause the first device to: causing wireless protocol configuration parameters of the second device to be transmitted to the second device; Alternatively, the second device may transmit the wireless protocol setting parameters of the second device to the Receive from device 3, 6. The first device according to claim 5.

8. The wireless setting parameters of the second device transmitted to the second device are 8. The method of claim 7, wherein the second device is used to configure the wireless protocol of the device. The first device described above.

9. The computer-executable instructions further cause the first device to: causing device information associated with the first device to be transmitted to the second device; The first device of claim 1 .

10. The device information related to the first device may include device capabilities, QoS settings for V2X communication, 10. The first method of claim 9, wherein the first parameter comprises one or more of: a constant parameter; and a sidelink measurement. Equipment.

11. a PC5 interface enabling communication between the first device and the second device; PC5 RRC signaling or PC5-S signaling via the PC5 interface The first device according to claim 1 , wherein a ring is used.

12. A PC5 interface allows communication between the first device and the third device. or the PC5 interface is adapted to facilitate communication between the second device and the third device. Enable PC5 RRC signaling or PC5-S signaling via the PC5 interface Nulling is used, The first device of claim 5 .

13. The radio protocol includes an SDAP layer, a PDCP layer, an RLC layer, a MAC layer, The first device of claim 1 , comprising a PHY layer.

14. The first device of claim 1 , wherein the first device or the second device is a vehicle.

15. The computer-executable instructions further cause the first device to: causing a transceiver to transmit data from the first device to a second device; The first device of claim 1 .

16. The third device may be a roadside unit, a base station, a relay node, a vehicle, or an integrated access and and a backhaul unit.

17. the first device; and a processor; Memory and and a communication circuit, wherein the second device communicates with the the second device is connected to the communication network via a computer stored in the memory; and further comprising computer-executable instructions for causing the processor to: When executed by the determining wireless protocol configuration parameters of the first device and Determine protocol configuration parameters, or from a third device, the wireless protocol setting parameters of the first device and the second device; and causing the wireless protocol setting parameters of the first device to be requested, and and receiving the wireless protocol configuration parameters of the second device. to make, The first device of claim 1 .

18. The determining of the wireless protocol configuration parameters of the first device includes: taking into account the relevant device information or the wireless protocol of the first device The determination of the configuration parameters includes determining the device information associated with the second device and the The first device of claim 17 , taking into account device information associated with the first device.

19. The computer-executable instructions further cause the second device to: causing wireless protocol configuration parameters of the first device to be transmitted to the first device; Alternatively, the first device may transmit the wireless protocol setting parameters of the first device to the Receive from device 3, 18. The first device according to claim 17.

20. The wireless setting parameters of the first device transmitted to the first device are 20. The method of claim 19, wherein the first device is used to configure the wireless protocol of the device.

10. The first device according to claim 9.

21. The computer-executable instructions further include instructions for transmitting to the first device a transmitting device information to the second device; The device information related to the first device may include device capabilities, QoS settings for V2X communication, and one or more of: a constant parameter; and a sidelink measurement; The second device is a processor; Memory and a communication circuit, wherein the second device is connected to the communication network via the communication circuit. and the second device is further connected to the computer-executable instructions stored in the memory. the computer-executable instructions, when executed by the processor, The second device comprises: determining wireless protocol configuration parameters of the first device and Determine protocol configuration parameters, or from a third device, the wireless protocol setting parameters of the first device and the second device; and causing the wireless protocol setting parameters of the first device to be requested, and and receiving the wireless protocol configuration parameters of the second device. to make, The first device of claim 1 .

22. Direct sidelink using a first device including a processor, a memory, and a communication circuit A method of communication, wherein the first device is connected to a communication network via the communication circuit. The method comprises: discovering a second device with which the first device can communicate; obtaining device information associated with the second device; a radio protocol of the first device for direct sidelink communication with the second device; To set up and A method comprising:

23. A non-transitory computer-readable storage medium having computer-readable instructions tangibly recorded thereon. wherein the computer-readable instructions, when executed by a processing circuit, cause the processing circuit to , causing a first device to perform a method for direct sidering communication, said method comprising: discovering a second device with which the first device can communicate; obtaining device information associated with the second device; a radio protocol of the first device for direct sidelink communication with the second device; To set up and 1. A non-transitory computer-readable storage medium having computer-readable instructions, comprising:

24. The PC5 interface is a unicast interface between the first device and the second device. a link, and one or more pairs of peer services at the first device and the second device; The first device of claim 11 , wherein the first device enables communication between the first device and the second device.

25. All services using the same PC5 unicast link run the same application.

25. The first device according to claim 24, for use.

26. A PC5 unicast link can have more than one service type. If the unicast link is associated with at least one peer application, 25. The first device of claim 24, wherein the first device supports the one or more service types.

Images