Resource management for 5g-ev2x

JP2025029183A5Pending Publication Date: 2025-10-10INTERDIGITAL PATENT HOLDINGS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2024213856
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2019-01-10
Filing Date
2024-12-06
Publication Date
2025-10-10

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

To provide a method and system for resource management on Sidelink (SL) for vehicle to everything (V2X) scenarios.SOLUTION: A method includes: receiving a configuration associated with a resource pool located in a SL bandwidth part; and determining resources available in the resource pool, including setting a time interval for a sensing window, The time interval for the sensing window is based on whether transmission of a SL shared channel is a periodic transmission or an aperiodic transmission, The method also includes: selecting resources from the available resources in the resource pool relative to transmission of the SL shared channel; and transmitting the transmission of the SL shared channel using the selected resources and transmitting transmission of a sidelink control channel, The SL shared channel and a SL control channel overlap in time without overlapping in a frequency each other.SELECTED DRAWING: Figure 6A
Need to check novelty before this filing date? Find Prior Art

Description

[Background technology]

[0001] Vehicle-To-Everything (V2X) applications are gaining popularity As the technology advances, it will provide short messages about the vehicle's own status data for basic safety. The message transmission includes raw sensor data, vehicle intent data, collaboration, and confirmation of upcoming operations. These advanced applications may need to be expanded with the transmission of larger messages, including For each application, the required data rate, latency, reliability, range, and The anticipated requirements for meeting speeds become more stringent.

[0002] 3rd generation partnership for enhanced V2X (eV2X) services The 3rd Generation Partnership Project (3GPP) is a project that has 25 Identifies illustrative use cases and related requirements (3GPP TR 22.886 Study on enhancements Refer to the Announcement of 3GPP Support for 5G V2X Services, Release 15, V15.2.0. The set of normative requirements is also categorized into four use case groups: It is defined by use cases. Vehicle platooning, extended sensors, advanced driving, and remote driving ( 3GPP TS 22.186 Enhancement of 3GPP support for V2X scenarios (Stage 1 ), Release 15, V15.3.0). Detailed performance requirements for each use case group A detailed description is given in TS 22.186. Summary of the Invention

[0003] Resources in Sidelink for Vehicle-to-Everything (V2X) Scenarios A method and system for managing resource structures in a sidelink is disclosed. An exemplary method and system for providing control and data channels is disclosed. Frequency division multiplexing (OFDM) waveform It can be frequency division multiplexed (Famed) or time division multiplexed (Timed). SUMMARY OF THE DISCLOSURE An exemplary method and system for resource configuration in a multi-threaded datacenter is disclosed. may be statically configured, locally semi-persistent, or dynamically configured. Exemplary methods and systems for supplemental resource allocation are disclosed. The sensing is done by a special device or by a group lead or roadside unit (Roadside User Equipment (UE) or Scheduling User Unit (RSU) Local scheduling may be performed by any user equipment (UE) and may be implemented by a specific device, or group lead or RSU or scheduling UE, etc. It may be implemented by a user equipment (UE). Exemplary methods and systems for scheduler allocation schemes for both with and without network control A system for both network controlled and non-network controlled applications is disclosed. An exemplary method and system for a resource allocation mode switching scheme is disclosed. Slots with resource allocation of control and data channels for different communications Exemplary methods and systems for subframe structure are disclosed. Exemplary methods and sensing schemes for both periodic and aperiodic data transmissions A sensing based resource selection and congestion control transmission scheme and system are disclosed. Exemplary methods and systems for are disclosed.

[0004] This Summary is an introduction to a simplified form of concepts that are further described below in the Detailed Description. This Summary is provided to introduce a selection of key features or essential aspects of the claimed subject matter. It is not intended to specify any mechanism, nor is it intended to be used to limit the scope of the claimed subject matter. Moreover, claimed subject matter is not intended to be used in any manner whatsoever in any part of this disclosure. It is not intended to be limited to a limitation that addresses any or all of the shortcomings noted.

[0005] BRIEF DESCRIPTION OF THE DRAWINGS The following detailed description will be better understood when read in conjunction with the accompanying drawings, in which: Although examples are presented in the drawings, the subject matter is not limited to the specific elements and instrumentalities disclosed. [Brief description of the drawings]

[0006] [Figure 1A] FIG. 1A illustrates an exemplary communication system. [Figure 1B] FIG. 1B is a system diagram of an example Radio Access Network (RAN) and core network. [Figure 1C] FIG. 1C is a system diagram of an example RAN and core network. [Figure 1D] FIG. 1D is a system diagram of an example RAN and core network. [Figure 1E] FIG. 1E illustrates another exemplary communication system. [Figure 1F]FIG. 1F is a block diagram of an example apparatus or device, such as a Wireless Transmit / Receive Unit (WTRU). [Figure 1G] FIG. 1G is a block diagram of an exemplary computing system. [Diagram 2] FIG. 2 shows an example block diagram of advanced V2X services. [Diagram 3] FIG. 3 shows an example one-symbol resource structure in the sidelink. [Figure 4] FIG. 4 shows example 2-symbol and 4-symbol resource structures in the sidelink. [Diagram 5] FIG. 5 shows an example 2-symbol minislot resource structure in the sidelink. [Figure 6A] FIG. 6A illustrates an example call flow for resource reconfiguration when joining a platoon. [Figure 6B] FIG. 6B illustrates an example call flow for resource reconfiguration when joining a platoon. [Figure 7A] FIG. 7A illustrates an example call flow for resource reconfiguration when exiting the formation. [Figure 7B] FIG. 7B illustrates an example call flow for resource reconfiguration when exiting the formation. [Figure 8A] FIG. 8A illustrates an example call flow of resource reconfiguration when switching RSUs. [Figure 8B] FIG. 8B illustrates an example call flow of resource reconfiguration when switching RSUs. [Figure 9A] FIG. 9A illustrates an example call flow for supplemental resource sensing. [Figure 9B] FIG. 9B illustrates an example call flow for supplemental resource sensing. [Figure 10A] FIG. 10A illustrates an example call flow for scheduling locally by lead. [Figure 10B]FIG. 10B illustrates an example call flow for scheduling locally by a lead. [Figure 11] FIG. 11 illustrates the allocated or scheduled broadcast, multicast, and unicast resources in the sidelink operating band or in the sidelink resource pool. [Figure 12] FIG. 12 shows an example of aggregated slot scheduling in the sidelink, where a broadcast transmission in the Physical Sidelink Shared Channel (PSSCH) spans the slot boundary between slots SL1 and SL2. [Figure 13] FIG. 13 shows an example of Sidelink Channel State Information (SL-CSI) acquisition. [Figure 14] FIG. 14 illustrates minislot-based scheduling. [Figure 15A] FIG. 15A illustrates a receiving UE initiated unicast. [Figure 15B] FIG. 15B shows a transmitting UE initiated unicast. [Figure 16] FIG. 16 illustrates an example method of sensing for periodic and aperiodic data transmissions over a shared resource pool. [Figure 17] FIG. 17 shows an example of UE-initiated scheduler selection with network control. [Figure 18] FIG. 18 shows an example of network-initiated scheduler selection with network control. [Figure 19A] FIG. 19A shows an example of scheduler selection without network control. [Figure 19B] FIG. 19B shows an example of scheduler selection without network control. [Figure 20A] FIG. 20A shows an example call flow for scheduler selection without network control. [Figure 20B]FIG. 20B illustrates an example call flow for scheduler selection without network control. [Figure 21] FIG. 21 illustrates an example call flow for scheduler modification with network control. [Figure 22] FIG. 22 shows an example of scheduler modification without network control. [Diagram 23] FIG. 23 shows an example call flow for scheduler modification without network control. [Figure 24A] FIG. 24A illustrates an example call flow for resource allocation mode switching with network control. [Figure 24B] FIG. 24B illustrates an example call flow for resource allocation mode switching with network control. [Figure 25A] FIG. 25A illustrates an example call flow for resource allocation mode switching without network control. [Figure 25B] FIG. 25B illustrates an example call flow for resource allocation mode switching without network control. [Figure 26A] FIG. 26A illustrates an example of sensing-based resource selection. [Figure 26B] FIG. 26B illustrates an example of sensing-based resource selection. [Figure 26C] FIG. 26C illustrates an example of sensing-based resource selection. [Figure 27] FIG. 27 illustrates an example of a call flow for sensing-based resource selection. [Figure 28] FIG. 28 shows an example of congestion measurement. [Figure 29] FIG. 29 shows an example of a call flow for congestion control based transmission. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0007] Exemplary Communication Systems and Networks The 3rd Generation Partnership Project (3GPP) is a global initiative to develop and deploy wireless access, core transformers, and other Port network and service capabilities (codec, security, and service technologies for cellular telecommunications network technologies, including those affecting the quality of The latest Radio Access Technology (RAT) The WCDMA (registered trademark) standard is based on Wideband CDMA (commonly known as 3G). and Long Term Evolution (commonly referred to as 4G). The new standard is called LTE (LTE Evolution), the LTE Advanced standard, and 5G (New Wireless 3GPP NR standard development is the next generation radio access technology (NEW It is expected that the definition of the new RAT (New Radio Access Technology) will continue to include new sub-7 GHz bands. Providing flexible wireless access and new ultra-mobile broadcasting above 7GHz and providing broadband wireless access. The access is a new non-backwards compatible wireless access in new spectrum below 7GHz. It is expected to consist of multiplexed together in the same spectrum to meet diverse requirements. Different operating modes that may address a broad set of 3GPP NR use cases involving Ultra-mobile broadband is expected to include Providing opportunities for broadband access, e.g., indoor applications and hotspots It is expected that the range of applications will include the ultramobile, centimeter-wave and millimeter-wave spectrum. Broadband will develop a common design framework with cmWave and mmWave specific design optimizations. It is expected that the network will share the same bandwidth as flexible wireless access below 7 GHz. .

[0008] 3GPP is working on a range of user experiences for data rate, latency, and mobility. It identifies the various use cases that NR is expected to support, which drive the requirements. The use cases fall into the following general categories: Enhanced Mobile Broadband (enhanced Mobile Broadband:eMBB), Ultra-Reliable Low Latency Communications (Ultra-Reliable L Low-Latency Communication (URLLC), Massive Machine Type Communication (MAC) e Type Communication (mMTC), network operation (e.g., network slice routing, migration and interworking, energy conservation), and enhancements This includes vehicle-to-everything (eV2X) communication, which is a type of communication that Vehicle-To-Vehicle (V2V) communication, Vehicle-to-infrastructure (V2V) e-To-Infrastructure (V2I) communication, Vehicle-To-Network :V2N) communication, Vehicle-To-Pedestrian (V2P) communication, and These categories may include any of the following: vehicle communications with other entities. Specific services and applications that will be used include, for example, monitoring and and sensor networks, device remote control, two-way remote control, personal cloud computing Computing, Video Streaming, Wireless Cloud-Based Office, First Responder Co Connectivity, car e-calls, disaster warnings, real-time gaming, multi-party video calls , autonomous driving, augmented reality, tactile internet, virtual reality, home automation, robotics tics, and aerial drones. All of these use cases and more , discussed herein.

[0009] FIG. 1A illustrates a system, method, and apparatus according to the present invention, in which the systems, methods, and apparatus described and claimed herein may be used. 1 illustrates an exemplary communication system 100. The communication system 100 may generally or collectively In addition, wireless transmit / receive units (WTRUs) 102a, 102b, which may be referred to as WTRUs 102, b, 102c, 102d, 102e, 102f, and / or 102g. The communication system 100 includes a radio access network (RAN) 103 / 104 / 105 / 1 03b / 104b / 105b, Core Network 106 / 107 / 109, Public Exchange Public Switched Telephone Network (PSTN) 108 and Internet The network includes a network 110, other networks 112, and network services 113. The network service 113 may include, for example, a V2X server, a V2X function, a ProS, eServer, ProSe functionality, IoT services, video streaming, and / or These may include edge computing, etc.

[0010] The concepts disclosed herein may be implemented in any number of WTRUs, base stations, networks, and It will be appreciated that the WTRU 102 may be used in a network element and / or a wireless network. The present invention relates to any type of device or equipment configured to operate and / or communicate in a wireless environment. In the example of FIG. 1A, each of the WTRUs 102 may be a handheld wireless communication device. 1A to 1E are diagrams showing various use scenarios considered for wireless communication. Along with the base station, each WTRU may be referred to as, by way of example only, a user equipment (UE), a mobile station, a fixed or mobile subscriber units, pagers, cellular telephones, personal digital assistants (Pe Real-time Digital Assistant (PDA), smartphones, laptops, tablets, Netbooks, Notebook Computers, Personal Computers, Wireless Sensors, Massive Consumer electronics, wearable devices such as smart watches or smart clothing, medical or e-health devices, robots, industrial equipment, drones, e.g. cars, buses or trucks Any equipment that transmits and / or receives radio signals, including vehicles such as cars, trains, or airplanes. The present invention may comprise or be included in any type of apparatus or device configured to Please understand that this is also a good idea.

[0011] The communications system 100 may also include a base station 114a and a base station 114b. In the example of A, each base station 114a and 114b is shown as a single element. , base stations 114a and 114b may be connected to any number of interconnected base stations and / or networks. The base station 114a may include a WTRU 102a, 102b, and 02c and wirelessly interfaces with at least one of the core networks 10 6 / 107 / 109, Internet 110, Network Services 113, and / or or other networks 112. The base station 114b may be any type of device configured to transmit and receive data. , Remote Radio Heads (RRH) 118a, 118b, transmitting and receiving points Transmission and Reception Point (TRP) 119a, 119b, and / or at least one of the roadside units (RSUs) 120a and 120b. and a core network 106 / 107 that interfaces with the / 109, the Internet 110, other networks 112, and / or networks facilitating access to one or more communications networks, such as the The RRHs 118a and 118b may be any type of device configured to WTRU 102c. Take the core network 106 / 107 / 109, the Internet 110, and the network One or more communication networks, such as the service 113 and / or other networks 112 The device may be any type of device configured to facilitate access to a network. .

[0012] The TRPs 119a and 119b communicate wirelessly with at least one of the WTRUs 102d. The interfaces are Core Network 106 / 107 / 109 and Internet 110 , network services 113, and / or other networks 112. Any type of device configured to facilitate access to multiple communication networks. The RSUs 120a and 120b may be the WTRUs 102e or 102f. It wirelessly interfaces with at least one of these networks and is part of the core network 106 / 10 7 / 109, the Internet 110, other networks 112, and / or networks facilitating access to one or more communications networks, such as the The base station 114a, 114b, 114c, 114d, 114e, 114f, 114g, 114h, 114h, 114h, 114h, 114i, 114j, 114h ... 4b is a base transceiver station (BTS), node B, e-node B, Home Node B, Home eNode B, Next Generation Node B (gNode B), Satellite, Site It can be a controller, an access point (AP), a wireless router, etc. .

[0013] The base station 114a may be part of the RAN 103 / 104 / 105. N also includes the Base Station Controller (BSC), the wireless network controller, Radio Network Controller (RNC), relay nodes, and other base stations The base station 114b may also include other stations and / or network elements (not shown). , RAN 103b / 104b / 105b, which may also be part of B Other base stations and / or network elements such as SCs, RNCs, relay nodes, etc. (not shown) ) may also include a base station 114a that transmits and / or receives wireless signals within a particular geographic area. A mobile station may be configured to receive a signal from a geographic area, which may be referred to as a cell (not shown). Similarly, base station 114b transmits and receives wired and / or wireless signals within a particular geographic region. Each station may be configured to transmit and / or receive signals from a geographic area referred to as a cell (not shown). The cell may be further divided into cell sectors. The cell served by the base station 114a may be divided into three sectors. , for example, may include three transceivers, one for each sector of the cell. Multiple-Input Multiple Output (MIMO) technology may be adopted; Thus, for example, multiple transceivers may be utilized per sector of a cell.

[0014] The base station 114a may communicate with the network via any suitable wireless communication link (e.g., radio frequency (RF)). RF, microwave, infrared (IR), ultraviolet (UV) , visible light, centimeter wave, millimeter wave, etc.) 17 to one or more of WTRUs 102a, 102b, 102c, and 102g. The air interface 115 / 116 / 117 may communicate with any suitable wireless It may be established using a Line Access Technology (RAT).

[0015] The base station 114b may be implemented using any suitable wired (e.g., cable, fiber optic, etc.) or Wireless communication links (e.g. RF, microwave, IR, UV, visible light, centimeter wave, millimeter wave, etc.) via wired or air interface 115b / 116b / 117b, which may be RRH118a and 118b, TRP119a and 119b, and / or RS The air interface may communicate with one or more of U 120a and 120b. 115b / 116b / 117b may be established using any suitable RAT.

[0016] RRH118a, 118b, TRP119a, 119b, and / or RSU120 a, 120b may be any suitable wireless communication link (e.g., RF, microwave, IR, ultraviolet Air interface 115c / 1, which can be 1000 Hz, UV, visible light, centimeter wave, millimeter wave, etc. One of WTRU102c, 102d, 102e, 102f via 16c / 117c The air interface 115c / 116c / 117c may communicate with any one of The RAT may be established using any suitable RAT.

[0017] The WTRU 102 may communicate with any suitable wireless communication link (e.g., RF, microwave, IR, Direct communication such as sidelink communication, which can be ultraviolet UV, visible light, centimeter wave, millimeter wave, etc. The devices may communicate with each other via the air interfaces 115d / 116d / 117d. The interfaces 115d / 116d / 117d may be established using any suitable RAT. It can be done.

[0018] The communication system 100 may be a multiple access system and may include CDMA, TD One or multiple channel accesses such as MA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a and and the WTRU 102a, 102b, 102c, or the RAN 103b / 104b / 105b RRH118a, 118b, TRP119a, 119b, and / or RSU1 in 20a and 120b, and WTRUs 102c, 102d, 102e, and 102 f stands for Universal Mobile Telecommunications System UMTS System, Universal Terrestrial Radio Access :UTRA), thereby implementing radio technologies such as Wideband Code Division Multiple Access (WCDM) A) using air interfaces 115 / 116 / 117 and / or 115c WCDMA is a high speed packet access (Hi gh-Speed ​​Packet Access (HSPA) and / or Evolved HSPA HSPA can include communication protocols such as HSPA+. HSPA is a high-speed downlink packet High-Speed ​​Downlink Packet Access (HSDPA) and / or High Speed High-Speed ​​Uplink Packet Access (HSUPA) It may include.

[0019] The base station 114a and the WTRUs 102a, 102b in the RAN 103 / 104 / 105 b, 102c, and 102g, or RRH in RAN 103b / 104b / 105b 118a and 118b, TRP119a and 119b, and / or RSU12 0a and 120b, and WTRUs 102c and 102d are Evolved UMTS terrestrial radio Wireless access such as Evolved UMTS Terrestrial Radio Access (E-UTRA) The technology may be implemented, for example, in accordance with Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) for air Interface 115 / 116 / 117 or 115c / 116c / 117c respectively The air interface 115 / 116 / 117 or 115c / 116c / 117c may implement 3GPP NR technology. LTE and LTE-A technologies are ( LTE D2D and / or V2X technologies and interfaces Similarly, 3GPP NR technology may include NR V2 (e.g., sidelink communications) X technologies and interfaces.

[0020] The base station 114a and the WTRUs 102a, 102b in the RAN 103 / 104 / 105 b, 102c, and 102g, or RRH in RAN 103b / 104b / 105b 118a and 118b, TRP119a and 119b, and / or RSU12 0a and 120b, and WTRUs 102c, 102d, 102e, and 102f. IEEE802.16 (e.g. Worldwide Interoperability Forum) Worldwide Interoperability For Microwave Access s:WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 2000 (IS-2000), IS-95, Interim Standard 856 (IS-856), Global System for Mobile Communications Global System for Mobile communications (GSM (registered trademark)), GS Enhanced Data Rates For GSM Evolution (EDGE) , GSM EDGE (GERAN), and other wireless technologies may be implemented.

[0021] The base station 114c in FIG. 1A may be a wireless router, a home NodeB, a home eNodeB, Or it may be an access point, for example, in a company, a home, a vehicle, a train, an airplane, a satellite, Facilitate wireless connectivity within localized areas such as satellites, factories, campuses, and other locations The base station 114c and the WTRU 102, e.g., The WTRU102e implements wireless technologies such as IEEE802.11 to provide wireless local area network (WLAN). A wireless local area network (WLAN) can be established. The base station 114c and the WTRUs 102 and 102d are IEEE 802.15 and the like. Which wireless technology is implemented to create a wireless personal area network (WPA)? The base station 114c and the WTRU 102 may establish a wireless personal area network (WPAN). The WRTU102e supports cellular-based RATs (e.g. WCDMA, CDMA2000 , GSM, LTE, LTE-A, NR, etc.) to provide picocells or femtocells As shown in FIG. 1A, the base station 114c may establish a direct connection to the Internet 110. Thus, the base station 114c may have a connection to the core network 106 / 107 / 10 9 may not require access to the Internet 110.

[0022] RAN103 / 104 / 105 and / or RAN103b / 104b / 105b , may communicate with a core network 106 / 107 / 109, which may , voice, data, messaging, authorization and authentication, applications, and / or Voice Over Internet Protocol (Vo any one of the WTRUs 102 configured to provide IP (Internet Protocol) services to one or more of the WTRUs 102. The network may be of any type. For example, the core network 106 / 107 / 10 9. Call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, packet data network connectivity, provides Ethernet connectivity, video distribution, etc., and / or It may implement high-level security features such as user authentication.

[0023] Although not shown in FIG. 1A, RAN103 / 104 / 105 and / or RAN 103b / 104b / 105b and / or Core Network 106 / 107 / 10 9 is RAN103 / 104 / 105 and / or RAN103b / 104b / 10 5b may communicate directly or indirectly with other RANs employing the same or different RATs. For example, it will be appreciated that the RAN 103 / 104 may utilize E-UTRA radio technology. RAN 103b / 104b / 105b and / or RAN 103b / 104b / 105b. The core network 106 / 107 / 109 may also employ GSM or NR radio technology. It may communicate with another RAN (not shown).

[0024] The core network 106 / 107 / 109 also includes a WTRU 102 that is connected to the PSTN 108, A gateway for accessing the Internet 110 and / or other networks 112 The PSTN 108 is the Plain Old Telephone Service. This may include a circuit-switched telephone network providing Internet Telephone Service (POTS). The network 110 uses the Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and TCP / Internet Protocol (IP) Internet Protocol switch Use common communication protocols such as the Internet Protocol (IP) on the Internet. It may include a global system of interconnected computer networks and devices. Other networks 112 may be owned and / or operated by other service providers. For example, network 112 may include a wired or wireless communication network operated by a , any type of packet data network (e.g., IEEE 802.3 Ethernet network), or RAN103 / 104 / 105 and / or RAN103 b / 104b / 105b, or one or more that may employ the same RAT or a different RAT. The core network may include another core network connected to multiple RANs.

[0025] WTRUs 102a, 102b, 102c, 102d, and 102e in the communication system 100 , and some or all of 102f may include multi-mode capabilities, e.g., WT RUs 102a, 102b, 102c, 102d, 102e, and 102f are different It may include multiple transceivers for communicating with different wireless networks over wire links. For example, the WTRU 102g shown in FIG. 1A may employ a cellular-based wireless technology. The base station 114a communicates with the base station 114c, which may employ IEEE 802 wireless technology. The present invention may be configured to:

[0026] Although not shown in FIG. 1A, the user terminal may have a wired connection to the gateway. It will be understood that the gateway is a residential gateway. RG can be a 10Gb / s 10Gb / s 10H ... Many of the ideas contained herein may be applied to a UE, which is a WTRU, and a network. It will be appreciated that the present invention may be equally applicable to UEs that use a wired connection to connect to the network. For example, the wireless interfaces 115, 116, 117, and 115c / 11 The ideas that apply to 6c / 117c can be equally applied to wired connections.

[0027] FIG. 1B is a system diagram of an example RAN 103 and core network 106. As mentioned above, the RAN 103 adopts UTRA radio technology to provide air interface 1 15 with the WTRUs 102a, 102b, and 102c. RAN 103 may also be in communication with a core network 106. As shown in FIG. 1B, RAN 103 may include: The WTRUs 102a, 102b, and 102c communicate with each other via an air interface 115. Node Bs 140a, 140b, and 140c, each of which may include one or more transceivers for receiving Node Bs 140a, 140b, and 140c may each include a RAN The RAN 103 may also correspond to a particular cell (not shown) within the RNC 1. The RAN 103 may include any number of Node Bs and wireless networks. It will be appreciated that the RNC may include a network controller (NNC).

[0028] As shown in FIG. 1B, Node Bs 140a, 140b may be in communication with an RNC 142a. In addition, Node B 140c may communicate with RNC 142b. b, and 140c communicate with their respective RNCs 142a and 142b via an Iub interface. The RNCs 142a and 142b communicate with each other via an Iur interface. Each of the RNCs 142a and 142b may communicate with each other via Each of the Node Bs 140a, 140b, and 140c may be configured to control the respective Node Bs 140a, 140b, and 140c. In addition, each of the RNCs 142a and 142b performs outer loop power control, load control, reception Attachment control, packet scheduling, handover control, macro diversity, security may be configured to perform or support other functionality, such as security functions, data encryption, etc. It is possible.

[0029] The core network 106 shown in FIG. 1B includes a media gateway :MGW) 144, Mobile Switching Center (MSC) 146, Serving GPRS Support Node (SGSN) 148 , and / or Gateway GPRS Support Node Each of the above elements may be part of the core network 106. Although shown as a set of elements, any one of these elements may be It will be understood that the electronic documentation may be owned and / or operated by entities other than .

[0030] RNC 142a in RAN 103 communicates with the core network via the IuCS interface. The MSC 146 may be connected to the MGW 144. The MSC 146 and the MGW 144 may 2c to access a circuit-switched network such as the PSTN 108, and WTRU 1 02a, 102b, and 102c and conventional terrestrial communication devices. .

[0031] RNC 142a in RAN 103 also communicates with the core network via the IuPS interface. The SGSN 148 may be connected to the GGSN 15 in the network 106. 0. The SGSN 148 and the GGSN 150 may be connected to the WTRUs 102a, 102b, b, and 102c provide access to packet-switched networks such as the Internet 110. provides access between the WTRUs 102a, 102b, and 102c and IP-enabled devices. This may facilitate communication between the parties.

[0032] The core network 106 may also be owned and / or operated by other service providers. 112, which may include other wired or wireless networks operated by It is possible.

[0033] FIG. 1C is a system diagram of an example RAN 104 and core network 107. As mentioned above, the RAN 104 employs E-UTRA radio technology and provides an air interface 116 with the WTRUs 102a, 102b, and 102c. 4 may also be in communication with the core network 107.

[0034] The RAN 104 may include eNodeBs 160a, 160b, and 160c, while the RA It will be appreciated that the N104 may include any number of eNodeBs. , 160b, and 160c each communicate with the WTRU 10 via the air interface 116. 2a, 102b, and 102c. For example, eNodeBs 160a, 160b, and 160c may implement MIMO technology. Thus, the eNodeB 160a may, for example, use multiple antennas to The WTRU 102a may transmit wireless signals to and receive wireless signals from the WTRU 102a.

[0035] Each of the eNodeBs 160a, 160b, and 160c is associated with a particular cell (not shown). It may be associated with radio resource management decisions, handover decisions, uplink and and / or handling user scheduling in the downlink. As shown in FIG. 1C, eNodeBs 160a, 160b, and 160c may be configured as may communicate with each other via the X2 interface.

[0036] The core network 107 shown in FIG. 1C includes a mobility management gateway (MMG). Management Gateway (MME) 162, a serving gateway 164, and a packet A packet data network (PDN) gateway 166, Each of the above elements is shown as part of the core network 107. Any one of these elements may be provided by an entity other than the core network operator. It will be understood that the Company may be owned and / or operated by its affiliates.

[0037] The MME 162 communicates with the eNodeB 160 in the RAN 104 via the S1 interface. a, 160b, and 160c, which may function as control nodes. For example, the MME 162 may recognize users of the WTRUs 102a, 102b, and 102c. bearer activation / deactivation, WTRUs 102a, 102b, and and selection of a particular serving gateway during the initial attachment of 102c. The MME 162 may also communicate 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 employ the same technology. possible.

[0038] The serving gateway 164 communicates with the RAN 104 via the S1 interface. A serving gateway may be connected to each of the eNodeBs 160a, 160b, and 160c. The gateway 164 generally transmits user data packets to the WTRUs 102a, 102b, and Routing and forwarding to / from WTRUs 102a, 102b, and 102c The serving gateway 164 may also transmit user The downlink data is sent to the WTRUs 102a, 102b, and 10 Triggering paging when available for WTRU 102a, 102b, and 102c may perform other functions such as managing and storing the context.

[0039] The serving gateway 164 also serves the WTRUs 102a, 102b, and 102c. 110, providing WT A PDN that may facilitate communication between the RUs 102a, 102b, 102c and IP-enabled devices. 166.

[0040] The core network 107 may facilitate communication with other networks. The network 107 provides connections to the WTRUs 102a, 102b, and 102c, and the PSTN 108. WTRUs 102a, 102b, and 102c and traditional terrestrial communication devices. The network 107 serves as an interface between the core network 107 and the PSTN 108. IP gateways (e.g. IP Multimedia Subsystems) that function as In addition, the core may include an IMS (Intermediate Media Subsystem) server. The network 107 provides other services to the WTRUs 102a, 102b, and 102c. including other wired or wireless networks owned and / or operated by the provider. The network 112 may provide access to a network that may be accessed by the user.

[0041] FIG. 1D is a system diagram of an example RAN 105 and core network 109. The RAN 105 employs NR radio technology and communicates with the WTRU over the air interface 117. RAN 105 may also communicate with core network 109. Non-3GPP Interworking Function: N3IWF) 199 employs non-3GPP wireless technologies and transmits data over the air interface 198 The N3IWF 199 may also communicate with the core network 109 and

[0042] The RAN 105 may include g Node Bs 180a and 180b. It will be appreciated that any number of g Node Bs may be included. Each of the WTRUs 102a and 102b communicates with the WTRUs 102a and 102b over an air interface 117. The integrated access and backhaul connection may include one or more transceivers for When used, the same air interface is used between the WTRU and the gNode B. This may be a core network 109 via one or more gNBs Node Bs 180a and 180b may support MIMO, MU-MIMO, and / or digital Therefore, the g Node B 180a may implement digital beamforming techniques, e.g. For example, multiple antennas may be used to transmit wireless signals to WTRU 102a and WTRU 102b. RAN 105 may receive radio signals from other types of base stations, such as eNodeB. It should be understood that the RAN 105 may employ multiple types of base stations. It will also be appreciated that, for example, the RAN may employ eNodeBs and gNodeBs.

[0043] The N3IWF 199 may include a non-3GPP access point 180c. It will be appreciated that 99 may include any number of non-3GPP access points. The PP access point 180c communicates with the WTRU 102 via the air interface 198. c. The non-3GPP access point may include one or more transceivers for communicating with the non-3GPP access point. 180c uses the 802.11 protocol and transmits wireless signals over the air interface 198. It may communicate with TRU 102c.

[0044] Each of the g NodeBs 180a and 180b is associated with a particular cell (not shown). Radio resource management decisions, handover decisions, uplink and / or downlink The system may be configured to handle user scheduling, etc. As shown in FIG. 1D, the g-nodes B 180a and 180b are connected to the Xn The devices can communicate with each other via the interface.

[0045] The core network 109 shown in FIG. 1D is a 5G Core (5GC) network. The core network 109 provides many communication services through the wireless access network. The core network 109 may provide services to customers interconnected by a core network. As used herein, the term "network" refers to a set of entities that implement the functionality of the network. When referring to a network function, the term "core network entity" or "network function" refers to Refers to any entity that implements one or more functionality of the core network. Such core network entities may include wireless and and / or network communication or computer system The computer-executable instructions (software) stored in memory and executed on the processor of the device. It should be understood that the control unit 100 may be a logical entity implemented in the form of software.

[0046] In the example of FIG. 1D, the 5G core network 109 includes an access mobility management function (ACC ss and Mobility Management Function (AMF) 172 and Session Management Function (S ESSENCE MANAGEMENT FUNCTION (SMF) 174 and USER PLANE FUNCTION (USER PLANE User Data Management Function (UPF) 176a and 176b Management Function (UDM) 197 and Authentication Server Function (Authentication Server Function:AUSF)190 and Network Exposure Function NEF (Non-Opportunistic Function) 196 and PCF (Policy Control Function) ) 184, a non-3GPP interworking function (N3IWF) 199, and user data and a User Data Repository (UDR) 178. Although these are shown as part of the 5G Core Network109, One of them is owned and / or operated by an entity other than the core network operator. It will be understood that the 5G core network may be operated in any manner. It may not be composed of all of these elements, but may be composed of additional elements, and multiples of each of these elements may be used. It will also be appreciated that the network function may be configured with an instance of It indicates that the Diameter routing agents are directly connected to each other. It is understood that the communication may be via a routing agent or message bus, such as I want to.

[0047] In the example of Figure 1D, connectivity between network functions is determined by a set of interfaces. A network function is realized through other network functions or reference points. Modeled as a set of services that are invoked or called by a service It will be understood that the initiation of a network function service may be described or implemented as follows: Direct connections between network functions, messaging exchanges over a message bus, and software This can be achieved through a function call.

[0048] The AMF 172 may be connected to the RAN 105 via an N2 interface. For example, the AMF 172 may perform registration management, connection management, reachability management, and other functions. AMF can play a role in managing, authenticating, and authorizing access to the N2 interface. The RAN 105 may be responsible for forwarding user plane tunnel configuration information to the RAN 105 via the The AMF172 receives the user plane tunnel from the SMF via the N11 interface. AMF 172 may receive configuration information from non-AMFs generally via the N1 interface. Non-Access-Stratum (NAS) packets are sent to the WTRUs 102a, 102b, and Routing and forwarding to / from WTRUs 102a, 102b, and 102c The N1 interface is not shown in FIG.

[0049] The SMF 174 can be connected to the AMF 172 via an N11 interface. Additionally, the SMF may be connected to the PCF 184 via an N7 interface, and the SMF may be connected to the PCF 184 via an N4 interface. The SMF 174 can be connected to the UPFs 176a and 176b via the SMF 174 interface. For example, the SMF 174 may function as a session management node, a WTRU 1 IP address assignment for 02a, 102b, and 102c, UPF176a and and management and configuration of traffic steering rules in UPF176b and AMF 172.

[0050] UPF176a and UPF176b are WTRU102a, 102b, and 102 c, access to a packet data network (PDN) such as the Internet 110; and facilitates communication between the WTRUs 102a, 102b, and 102c and other devices. UPF176a and UPF176b can also promote WTRU102a, 102b 102c may provide access to other types of packet data networks. For example, the other network 112 may be an Ethernet network or a packet The UPF176a and UPF176 can be any type of network that exchanges b receives the traffic steering rules from the SMF174 via the N4 interface. The UPF 176a and the UPF 176b may receive the packet data network. 6 interface or via the N9 interface. By connecting to other UPFs, it provides access to packet data networks. In addition to providing access to packet data networks, UP The F176 is responsible for packet routing and forwarding, policy rule enforcement, and user plane traffic. Quality of service handling for traffic, role of downlink packet buffering It can fulfill its role.

[0051] The AMF172 also connects to the N3IWF199 via the N2 interface, for example. The N3IWF may be, for example, a wireless interface that is not defined by 3GPP. Facilitating connectivity between the WTRU 102c and the 5G core network 170 via technology AMF interacts with N3IWF19 in the same or similar manner as it interacts with RAN105. 9.

[0052] The PCF 184 may be connected to the SMF 174 via an N7 interface, 15 interface, and may be connected to the AMF 172 via the N5 interface 188 via the Application Function (AF) 188. The N15 and N5 interfaces are not shown in FIG. 1D. The policy rules may be provided to control plane nodes such as the AMF 172 and the SMF 174. , allowing control plane nodes to enforce these rules. The MF transmits the policy to the WTRUs 102a, 102b, and 102c via the N1 interface. 2c. , to the AMF 172. The policy may then be transmitted to the WTRUs 102a, 102b, and 102c may be imposed or applied.

[0053] The UDR 178 may act as a repository for authentication credentials and contract information. The DR may be connected to a network function so that the network function can The data may be added to, read from, or modified by the data in the library. For example, the UDR 178 may connect to the PCF 184 via an N36 interface. Similarly, the UDR178 may be connected to the NEF196 via the N37 interface. In addition, the UDR 178 may connect to the UDM 197 via an N35 interface.

[0054] The UDM197 acts as an interface between the UDR178 and other network functions. The UDM 197 may authorize the UDR 178 to access network functions. For example, the UDM197 can be connected to the AMF172 via the N8 interface. Preferably, the UDM 197 can be connected to the SMF 174 via an N10 interface. Similarly, the UDM 197 may connect to the AUSF 190 via an N13 interface. UDR178 and UDM197 may be tightly integrated.

[0055] The AUSF190 performs authentication related operations and transmits the UDM1 through the N13 interface. 78 and then connects to the AMF172 via the N12 interface.

[0056] NEF196 is a 5G Core Network109 application and service The exposure is via the Application Function (AF) 188. The NEF may be connected to the AF188 via the N33 interface. Rather, it is a network that allows other networks to be exposed to the capabilities and services of the 5G core network. It can be connected to the network function.

[0057] Application function 188 is the network function in the 5G core network 109. The interaction between the application function 188 and the network function may be This may be through a direct interface or occur via the NEF196 The application function 188 may be considered as part of the 5G core network 109. It may be outside the 5G core network 109 and may be part of the mobile network. It may be deployed by companies that have a business relationship with the network operator.

[0058] Network slicing is the integration of one or more To support multiple "virtual" core networks, mobile network operators This is a mechanism that can be used by different RANs or by The core network can be expanded to support different service types launched between Network slicing involves "slicing" a network into multiple virtual networks. The program allows operators to set different requirements, for example in the areas of functionality, performance and isolation. We will tailor our solutions to meet the needs of different market scenarios. This allows the generation of networks that are optimized.

[0059] 3GPP is upgrading the 5G core network to support network slicing Network slicing is designed to allow network operators to ,Sometimes, 5G use cases (e.g., large-scale IoT, critical communications,,V Used to support a diverse set of mobile broadband (2X, LTE, and enhanced mobile broadband) Without the use of network slicing technology, The network architecture allows each use case to adapt to its own set of performance, scalability, and availability requirements. Efficiently support a wider range of use cases when you have a specific set of bodies In addition, the new network may not be flexible and scalable enough to support The introduction of work services should be made more efficient.

[0060] Referring again to FIG. 1D, in a network slicing scenario, the WTRU 102a, 102b or 102c may connect to the AMF 172 via the N1 interface. An AMF can logically be part of one or more slices. An AMF is a part of the WTR. U102a, 102b, or 102c connection or communication with one or more UPF17 6a and 176b, and may be coordinated with SMF 174 and other network functions. Each of F176a and 176b, SMF174, and other network functions are They may be part of the same slice or different slices. At some point, different computing resources, security credentials, etc. may be available. They can be separated from each other in this sense.

[0061] The core network 109 may facilitate communication with other networks. The network 109 is an interface between the 5G core network 109 and the PSTN 108. IP gateways such as IP Multimedia Subsystem (IMS) servers that act as For example, the core network 109 may include or communicate with a system Short Message Service (SMS) is a service that facilitates communication via short message service. It may include or communicate with an SMS (SMS) service center. For example, the 5G core network 109 includes WTRUs 102a, 102b, and 102c. , facilitating the exchange of non-IP data packets between the server or application function 188 In addition, the core network 170 may 2c, other wired or It may provide access to a network 112, which may include a wireless network.

[0062] The core network described herein and shown in Figures 1A, 1C, 1D, and 1E The working entities are given the terms and conditions for those entities in certain existing 3GPP specifications. Although these entities and functionality will be identified by names used in the future, Other names may be used to identify specific entities or functions, and future 3GPP These specifications may be combined in future specifications published by 3GPP, including the NR specifications. It should be understood that, therefore, in Figs. 1A, 1B, 1C, 1D, and 1E The specific network entities and functionality described and illustrated are provided as examples only. The subject matter disclosed and claimed herein is provided solely for illustrative purposes and is not intended to be limiting or to be limiting, either currently or in the future. embodied or implemented in any similar communication system, whether or not traditionally defined. It should be understood that the present invention may be embodied in various ways.

[0063] FIG. 1E illustrates an example communication system in which the systems, methods, and devices described herein may be used. The communication system 111 includes a wireless transmit / receive unit (WTRU) A, B, C, D, E, F, a base station gNB 121, a V2X server 124, and a roadside user In practice, the present invention may include a plurality of RSUs 123a and 123b. The concept is to integrate any number of WTRUs, base stations gNBs, V2X networks, and / or or other network elements. WTRUs A, B, C, D, E, and F are in the access network coverage 131 WTRUs A, B, and C may be out of range, with WTRU A being the group lead. and forms a V2X group with WTRUs B and C as group members.

[0064] WTRUs A, B, C, D, E, and F are in the access network coverage 131 If they are within the same region, they communicate with each other via the Uu interface 129 via the gNB 121. In the example of FIG. 1E, WTRUs B and F are in access network coverage 13. WTRUs A, B, C, D, E, and F are access network 131 under access network coverage or outside access network coverage Whether or not the sidelink interface, such as interface 125a, 125b, or 128, is They may communicate directly with each other via a PC5 or NR PC5 interface. For example, in the example of FIG. 1E, WRTU D, which is outside the access network coverage 131, communicates with WTRU F that is inside the coverage 131 .

[0065] WTRUs A, B, C, D, E, and F are Vehicle-to-Network (V2N)1 33 or via the sidelink interface 125b, RSU 123a or 123 b. WTRUs A, B, C, D, E, and F may communicate with vehicle-to-infrastructure The V2X server 124 may communicate with the V2X infrastructure (V2I) interface 127. WTRUs A, B, C, D, E, and F are used for Vehicle-to-Person (V2P) interoperability. The UE may communicate with another UE via interface 128.

[0066] FIG. 1F illustrates a WTRU 102, such as the WTRU 102 of FIG. 1A, FIG. 1B, FIG. 1C, FIG. 1D, or FIG. 1E. For wireless communication and operation in accordance with the systems, methods, and apparatus described herein. FIG. 1F is a block diagram of an example apparatus or device WTRU 102 that may be configured in accordance with the present invention. As shown, the example WTRU 102 includes a processor 118, a transceiver 120, and a transmission / receiving element 122, speaker / microphone 124, keypad 126, display 128, non-removable memory 130, and removable A storage memory 132, a power source 134, and a Global Positioning System (GPS) The WTRU 10 may include a GPS (Global Positioning System) chipset 136 and other peripherals 138. It will be understood that 2 may include any subcombination of the elements described above. Among others, but not limited to, Base Transceiver Stations (BTS), Node B, Site Controllers, Access Point (AP), Home Node B, Evolved Home Node B (eNodeB), Home Home Evolved Node-B (HeNB), Home Evolved Node-B gate base stations 114a and 114b, such as a 1G-way, a next-generation Node B (gNode B), and a proxy node; and 114b, and / or base stations 114a and 114b may represent nodes as shown in FIG. 1F and described herein.

[0067] 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 associated with the DSP cores; a controller; Microcontrollers, Application Specific Integrated Circuits ircuit:ASIC, Field Programmable Gate Array FPGA (Field Programmable Gauge) circuits, any other type of Integrated Circuit (Integrated Circuit C), a state machine, etc. The processor 118 may be used for signal coding, data processing, etc. , power control, input / output processing, and / or operation of the WTRU 102 within a wireless environment. The processor 118 may perform any other functionality that enables the transmit / receive element 1 1F shows the individual components. Although the processor 118 and the transceiver 120 are shown as a single unit, It will be appreciated that the receiver 120 may be integrated together in an electronic package or chip. cormorant.

[0068] The UE's transmit / receive element 122 communicates with the UE via the air interface 115 / 116 / 117. 1A), or air interface 115d / 116d / 117d to transmit signals to or receive signals from other UEs. For example, the transmit / receive element 122 may be configured to transmit and / or receive RF signals. The transmit / receive element 122 may be, for example, an antenna configured to receive the An emitter / configured to transmit and / or receive R, UV, or visible light signals The transmit / receive element 122 can transmit and receive both RF and optical signals. The transmit / receive element 122 may be configured to transmit any combination of wireless or wired signals. It will be appreciated that the device may be configured to transmit and / or receive matching information.

[0069] In addition, the transmit / receive element 122, although shown in FIG. 1F as a single element, may be a WTR The WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 1 The WTRU 102 may employ MIMO technology. Thus, the WTRU 102 may Two or more transmitters for transmitting and receiving radio signals via the 115 / 116 / 117 It may include a transmit / receive element 122 (eg, multiple antennas).

[0070] The transceiver 120 modulates the signal to be transmitted by the transmit / receive element 122. , may be configured to demodulate the signal received by the transmit / receive element 122. Thus, the WTRU 102 may have multi-mode capabilities. In one embodiment, the WTRU 102 supports multiple RATs, such as NR and IEEE 802.11 or communicate via NR and E-UTRA or communicate with different RRHs, TRPs, RSUs, Or multiple beams to allow a node to communicate with the same RAT via multiple beams. The wireless communication system may include a number of transceivers.

[0071] The processor 118 of the WTRU 102 controls the speaker / microphone 124, the keypad 1 26, and / or a display / touchpad / indicator 128 (e.g., LCD Display (Liquid Crystal Display: LCD) display unit or organic Organic Light-Emitting Diode (OLED) display unit The processor 118 may also be connected to and receive user input data from the The data is transmitted to a speaker / microphone 124, a keypad 126, and / or a display. In addition, the processor 118 may output a non- Any type of removable memory 130 and / or removable memory 132 The information may be accessed from and data may be stored in suitable memory. The memory 130 is a random access memory (RAM), a read-only memory (RW), Read-Only Memory (ROM), hard disk, or any other type The removable memory 132 may include a memory storage device such as a subscriber identity module (SIM), (Subscriber Identity Module: SIM) cards, memory sticks, secure digital The processor 118 may include a Secure Digital (SD) memory card, etc. on servers hosted on cloud or edge computing platforms, and is a memory that is not physically located on the WTRU 102, such as in a home computer (not shown). The information may be accessed from and data may be stored in the library.

[0072] The processor 118 may receive power from the power source 134 and may also receive power from other The power supply 134 may be configured to distribute and / or control power to the components. Power supply 1 may be any suitable device for powering the WTRU 102. 34 may include one or more dry batteries, solar cells, fuel cells, or the like.

[0073] The processor 118 also generates location information (e.g., longitude, latitude, and latitude). In addition to, or instead of, information from the GPS chipset 136, the WTRU 102 may: A base station (e.g., base station 114a) , 114b) and / or from two or more nearby base stations. The WTRU 102 may determine its location based on the timing of the signal being received. It will be appreciated that the location information may be obtained by any suitable location determination method.

[0074] The processor 118 may further include additional features, functionality, and / or wired or wireless components. One or more pieces of software and / or hardware that provide connectivity The peripherals 138 may be connected to other peripherals 138, which may include a cellular module. For example, the peripherals 138 may be , various sensors such as accelerometers, biometric (e.g., fingerprint) sensors, e-compasses , satellite transceivers, digital cameras (for photos or videos), Universal Serial Bus ( Universal Serial Bus (USB) port or other interconnection interface, vibration device devices, TV receivers, hands-free headsets, Bluetooth (registered trademark) Modules, Frequency Modulated (FM) radio units, digital music players Layer, Media Player, Video Game Player Module, Internet Browser etc.

[0075] The WTRU102 can be used in sensors, consumer electronics products, smart watches or smart clothing. Wearable devices, medical or e-health devices, robots, industrial equipment, to other equipment or devices, such as a car, truck, train, or airplane vehicle. The WTRU 102 may include an interconnection interface that may comprise one of the peripherals 138. Such devices may communicate with one or more interconnection interfaces, such as a or may be connected to other components, modules, or systems of the device.

[0076] FIG. 1G is a block diagram of an exemplary computing system 90, in which R AN103 / 104 / 105, Core Network 106 / 107 / 109, PSTN108, on the Internet 110, other networks 112, or network services 113 1A, 1C, 1D, and 1E, such as specific nodes or functional entities of One or more devices of the communication network shown in FIG. E may be embodied. The operating system 90 may comprise a computer or server and may be in the form of software. the state (where or how such software is stored or accessed); The present invention may be primarily controlled by computer readable instructions, which may be any suitable programmable logic device, including a computer readable memory. Such computer readable instructions may be used to operate the computing system 90 in the following manner: The program may be executed within a processor 91. The processor 91 may be a general-purpose processor, a special-purpose processor, or the like. processors, conventional processors, digital signal processors (DSPs), multiple microprocessors one or more microprocessors associated with the DSP cores; a controller; Microcontrollers, Application Specific Integrated Circuits (ASICs), Field Programmable Gate array (FPGA) circuits, any other type of integrated circuit (IC), state machines, etc. The processor 91 may be responsible for signal coding, data processing, power control, input / output A processing and / or computing system 90 operates within a communications network. The coprocessor 81 may perform any other functionality that enables the main processor to An optional processor distinct from the 91 that performs additional functions or The processor 91 and / or the co-processor 81 may be It may receive, generate, and process data relating to the methods and apparatus disclosed herein.

[0077] In operation, the processor 91 fetches, decodes, and executes instructions to perform computing The information is transmitted to other resources via the system bus 80, which is the main data transfer path of the operating system. Such a system bus transfers data to and from the computer's resources. It connects the components in the data exchange system 90 and defines the medium for data exchange. The system bus 80 typically includes a data line for transmitting data and an address line for address lines for sending data, and for sending interrupts and for the system bus. and control lines for operating the system. Peripheral Component Interconnect (PCI) bus .

[0078] The memories connected to the system bus 80 include a random access memory (RAM) 82 and and a read only memory (ROM) 93. Such memory is a memory in which information is stored, ROM 93 generally includes circuitry that allows the ROM to be written and read. The data stored in RAM 82 includes data stored in the RAM that cannot be read by the processor. The IP address can be read or changed by the IP address 91 or other hardware devices. Access to the RAM 82 and / or ROM 93 is controlled by a memory controller 92. The memory controller 92 converts virtual addresses into physical addresses when instructions are executed. The memory controller 92 may also provide an address translation function that translates the Isolate processes in the system and use memory reserves to isolate system processes from user processes. Thus, a program running in the first mode can protect itself against may only access memory that is mapped by the process virtual address space. , within the virtual address space of another process, unless inter-process memory sharing is configured The memory cannot be accessed.

[0079] In addition, the computing system 90 includes a processor 91, a printer 94, a keyboard 95, and a communicates commands to peripherals such as the board 84, mouse 95, and disk drive 85 The peripheral controller 83 may be responsible for:

[0080] The display 86 controlled by the display controller 96 is 90. The visual output may include text, graphics, animated graphics, and video. The visual output is called a Graphical User Interface (GUI). The display 86 may be provided in the form of a CRT-based video display. B. LCD-based flat panel displays, gas plasma-based flat panels The display controller 9 may be implemented using a display or a touch panel. 6 is the electronic components required to generate a video signal that is sent to a display 86. Includes components.

[0081] Further, the computing system 90 may be N103 / 104 / 105, Core Network 106 / 107 / 109, PSTN108 , the Internet 110, the WTRU 102, or the like shown in FIG. 1A, FIG. 1B, FIG. 1C, FIG. 1D, and and to external communication networks or devices, such as other networks 112 of FIG. 1E. A communication adapter, such as a wireless or wired network adapter 97, may be used to The computing system 90 includes a network of other nodes or The communication circuitry may be capable of communicating with the functional entities. In combination with the sensor 91, a particular device, node, or functional entity as described herein may be The above-mentioned method may be used to perform the steps of transmitting and receiving the entity.

[0082] Any of the devices, systems, methods, and processes described herein or All are implemented by computer executable instructions (e.g., The instructions may be embodied in the form of a program code (program code), which may be executed by the processor 118 or When executed by a processor, such as 91, the processor performs the system described herein. It is understood that the systems, methods, and processes may be implemented and / or performed by the present invention. Specifically, any of the steps, operations, or functions described herein may be implemented in any manner that is suitable for use in a particular application. Implemented in the form of such computer-executable instructions, Executed on a processor of a device or computing system configured for communications The computer-readable storage medium may be any non-transitory (e.g., volatile) medium for storing information. Volatile and non-volatile media implemented in any form or physical method or technology, removable and non-removable media, such computer-readable storage media including signals. The computer readable storage medium may include RAM, ROM, EEPROM, flash memory, or other memory technologies, CD-ROMs, Digital Versatile Disks DVD) or other optical disk storage devices, magnetic cassettes, magnetic tapes, A magnetic disk storage device or other magnetic storage device or a storage medium for storing the desired information. Any information that may be used for any purpose and that can be accessed by a computing system. This includes, but is not limited to, any other tangible or physical medium.

[0083] (Brief introduction) In Release 14 of LTE V2X, the basic requirement for V2X services is road safety. Supported for safety services (e.g. vehicle and infrastructure Supports low latency and reliable message exchange between Improved network performance to meet vehicle-to-vehicle (V2V) latency requirements while providing high-density The two configurations of resource pools are Schedule in the Physical Sidelink Control Channel (PSCCH) allocation and the physical sidelink shared channel (PSSCH) For associated data transmission (3GPP TS 36.213 Physical layer protocol cedures, Release 15, V15.2.0).

[0084] Meets latency requirements and meets high Doppler spread and high density requirements for V2X communications To accommodate vehicles, sidelink transmission modes 3 and 4 are specified in TS36.213. It has been done.

[0085] Mode 4 uses direct LTE sidelink (SL) between two vehicular UEs. Mode 4 uses the new PC5 interface, which provides a semi-persistent transmission. Distributed UE scheduling based on sensing is adopted. V2V traffic from the device is Traffic is mostly periodic and small in nature, which is a major constraint on resources. The estimation is used to sense congestion in a resource and estimate future congestion on that resource. Based on this, resources are reserved.

[0086] On the other hand, mode 3 uses a centralized eNB scheduler. B uses the Uu interface to communicate with the sidelink, e.g., the PC5 interface. Schedule communications in the network.

[0087] As shown in Figure 2, advanced V2X applications will be more proactive and sophisticated in transportation. The expected requirements are creating a shift to infrastructure that requires To meet the requirements of rate, latency, reliability, system capacity, service coverage, etc. Current LTE V2X solutions are limited in terms of the required latency and cannot deliver the required data rates, reliability, and How to optimize the source structure and resource allocation to support advanced V2X services How to allocate resources is a necessary problem that must be addressed and solved.

[0088] Resources in Sidelink for Vehicle-to-Everything (V2X) Scenarios A method and system for management is disclosed.

[0089] A method and system for resource structure in sidelink is disclosed. The data channel is frequency division multiplexed (Freq) with an orthogonal frequency division multiplexing (OFDM) waveform. uency division multiplexed (FDMed) or time division multiplexed (Time Division Multiplexed The resources are multiplexed (TDMed) based on symbols or minislots over time. A spool is also disclosed.

[0090] A method and system for resource configuration in sidelink is disclosed. The system configuration is transmitted via the Uu interface via System Information (SI). or via Radio Resource Control (RRC) messages, or Sidelink SI (SL-SI) via PC5 interface Or via Sidelink RRC (SL-RRC), the V2X system It can be statically configured in the system. For example, the configuration of the automation of the vehicle UE by level, Configuration for each vehicle UE role, service or application and associated priorities The resource configuration is based on the number of times the resource is allocated, and on the data traffic characteristics. Locally via SL-SI or SL-RRC messages over the C5 interface For example, it can be configured as a group lead, a roadside unit (RSU), or a switch. This is a configuration of special UEs such as scheduling UEs.

[0091] A method and system for supplemental resource allocation is disclosed. Localized scheduling can be performed by the predecessor, the RSU, or the UE. , can be performed by the group lead or the RSU or the UE.

[0092] Scheduler selection for both network controlled and non-network controlled or A method and system for selection and modification is disclosed.

[0093] Resource allocation modes for both network controlled and non-network controlled A method and system for a switching scheme is disclosed.

[0094] Slots with control and data channel resource allocation for different communications A method and system for subframe structure is disclosed. Both slot-based and metric-based methods are proposed.

[0095] Method for sensing schemes for both periodic and aperiodic data transmissions - Patents.com The sensing is performed in an adjustable sensing window, and the candidate litho The source is selected based on the sensing result. Listen-Before-Talk Channel sensing, such as LBT, is used to determine the selected resource to avoid possible collisions. Preemption is performed before transmission on the bus for high priority, short latency data transmissions. Options are proposed to prioritize reserved resources.

[0096] A method and system for a sensing-based resource selection scheme is disclosed. The selection is based on priority, latency, range, and / or congestion.

[0097] A method and system for a congestion control based transmission scheme is disclosed. Pings may be based on priority, latency, range, and / or congestion.

[0098] It is noted that the terms "UE" and "vehicle UE" are interchangeable in this disclosure. stomach.

[0099] The exemplary method includes: receiving a congestion report from the sidelink band; The fact that it is located in the width part and the resource usage and one determining the available resource or resources and determining when a data packet is ready for transmission; receiving an indication from a higher layer that a transmission has been initiated; and Select and reserve one or more resources in the resource pool and Transmitting one or more transmissions of data packets based on one or more resources and

[0100] Determines the resource usage in a resource pool and one or more available resources. The step of detecting the presence of the detection signal may include setting a time interval for a sensing window, The time interval for the data packet depends on the periodic or aperiodic transmission, the lay latency requirements, repetition for transmission of data packets, and hybrid automatic repeat requests Data per EST (Hybrid Automatic Repeat Request: HARQ) feedback The packet retransmission count is set based on at least one of the following:

[0101] Determines the resource usage in a resource pool and one or more available resources. This is a matter of scheduling or reserving or preempting resources. By decoding the Sidelink Control Information (SCI) By detecting resource usage, the sidelink reference signal received power (SRS R Sidelink Received Signal Strength Inference (SL-RSRP) Sidelink Received Signal Strength Indicator (SL-RSSI), measuring at least one of a channel busy rate, a channel occupancy rate, and Resources that have not been scheduled, reserved or preempted, communication range A resource that is within a surrounding zone, or a SL-RSRP measurement of a resource or an S Based on a determination that at least one of the L-RSSI measurements is below a threshold, The method may include at least one of determining available resources.

[0102] Selecting and reserving one or more resources in a resource pool is called resource selection. determining a time interval for resource selection, the time interval for resource selection comprising: One or more of the priority, latency, or reliability of the data packets being transmitted , and one or more of repetitions or retransmissions per HARQ feedback. The decision will be based on at least one of them.

[0103] Selecting and reserving one or more resources in a resource pool is a measured By comparing the SL-RSRP or RS-RSSI to a threshold, one or more The method may further include selecting a candidate resource, the threshold being a function of a priority of the data packet to be transmitted. interference measurements or based on at least one of the congestion measures.

[0104] Selecting and reserving one or more resources in a resource pool is transmitted Priority of data packets, latency, reliability, or range, or interference or selecting one or more resources based on at least one of the congestion measures; and scheduling or reservation SCI, initial transmission, repetition, HARQ fee retransmission per HARQ feedback, or next data for periodic traffic selecting one or more resources for at least one of the data packets; It may include at least one of them.

[0105] The sending of one or more transmissions of data packets is determined based on the congestion level or At least one of the following: priority, latency, reliability, or range of data packets and determining whether or not the congestion threshold is exceeded based on the result. transmitting one or more transmissions of the data packet based on the determination that the congestion threshold is reached; The congestion level or the number of data packets being transmitted is determined to be exceeded. Based on at least one of the following: priority, latency, reliability, or range It may drop a transmission or determine the congestion level or the priority of the data packets being transmitted. Based on at least one of the following: frequency, latency, reliability, or range, modulation and and adjusting the coding scheme or transmission power level, as well as the data packet of transmitting at least one of an initial transmission, a repeat, or a retransmission of the and performing at least one of the following:

[0106] (Resource Structure) To support advanced V2X services and use cases, Data communication over a network is no longer limited to small periodic transmissions. It is much more scalable and flexible. The extensible resource structure may be periodic or aperiodic (e.g., event-triggered). 5G may be required to support both small and large data. The adoption of multi-carrier OFDM waveforms for uplink transmissions is a key step forward in the adoption of OFDM in the sidelink. Allows for more flexible resource structures with FDM-based multiplexing, e.g. New Radio Physical Sidelink Control Channel for Scheduling Allocation The Physical Sidelink Control Channel (NR-PSCCH) is a new The radio physical sidelink control channel (NR-PSSCH) is time division multiplexed (TDMed ) or frequency division multiplexed (FDMed).

[0107] Much higher reliability, lower latency, and higher vehicle density for highly autonomous vehicles It is very important to support this. This is due to the optimized resource structure. High-frequency spectrum requires reduced bandwidth, improved reliability, and minimal congestion. With increasing operating bandwidth, time resources are limited by different numerologies (e.g., 15K Hz, 30KHz, 60KHz, 120KHz, and 240KHz subcarrier spacing) can be allocated at a finer granularity (e.g., symbols or minislots) in Latency and congestion, as well as reliability (e.g., available time resources for repetitions). This could help improve the quality of service.

[0108] In multi-carrier OFDM, sidelink resources are used to improve latency, reliability, and data rate. Each can be structured differently to meet requirements for speed, coverage, etc.

[0109] As shown in FIG. 3, the resources in the sidelink are divided into two parts: time domain (e.g., symbol phase domain) and One symbol in a resource block, and one frequency (e.g., a Resource Block) k:RB pool or Resource Block Group (RBG) If there are many resource blocks (RBs) available in the Or resource block group (RBG) (e.g., a group of adjacent RBs) or sub- structured as short as a subchannel (e.g., a group of adjacent RBs or RBGs) This can be achieved by using messages with short control signaling in the NR-PSCCH, For example, the Sidelink Control Information (SCI) shown in the figure, and periodic or aperiodic (e.g. For example, event-triggered transmissions) via the same symbol in a new radio Very low data latency on the Physical Sidelink Shared Channel (NR-PSSCH) This enables transmission of

[0110] Each vehicle UE may have a very short time to transmit and therefore has more time resources. The system provides coverage in high density areas such as road intersections, multi-lane highways, or multi-level bridges. UEs in each slot, subframe, or frame to improve the Available.

[0111] Each vehicle UE may have a very short time to transmit and therefore has more time resources. The service performs frame-by-frame, frame-by-frame, or frame-by-frame synchronization for improved reliability with very low latency. Repetitions in a frame are available for transmission to the receiver.

[0112] Each vehicle UE may have a very short time to transmit and therefore has more time resources. The system enables beam-based operation in the very high frequency spectrum up to 52.6 GHz. In each slot, subframe, or frame, the vehicle U is used for area coverage. E can be used to sweep the beam to different receivers.

[0113] For example, UE-v1 has more RBs in its bandwidth part (BWP) “BWP-v1 When used in ", RB k1 to RB k2 or RBG k1 to RBG k2, or from subchannel k1 to subchannel k2, for the period "Period-v 1” and “Sym1” of subframes “SF 0” and “SF l1”, respectively. " transmit short control signaling, e.g., SCI, on the NR-PSCCH.

[0114] In another example, UE-v2 may transmit short messages with control in NR-PSCCH, e.g. For example, SCI, and FDMe in the same symbol, e.g., symbol 4 "Sym4" The NR-PSSCH data to be transmitted is sent in the period "Period-v2". The same transmission occurs in symbols 5 and 6 of subframes "SF 0" and "SF 12", respectively. Repeated transmissions can be sent to the same receiver (e.g., repeated for reliability) or or each time it can be transmitted to a different receiver (e.g., a beam for area coverage). As shown in Figure 3, UE-v2 uses FDMe in NR-PSCCH. NR-PSSCH via one symbol, and transmits the NR-PSSCH data via one symbol. Therefore, the BWP "BWP-v2" has more RBs than the BWP as shown in Figure 3. When used in "BWP-v2", for example, BR 0~RB N or RBG 0~ In the range of RBG N or subchannel 0 to N, the BWP is much larger than that of UE-v1. stomach.

[0115] NR-PSCCH and NR-PSSCH are FDMed over the same symbol When the PSCCH carrying the SCI is assigned to a different location in frequency, e.g. For example, the lowest index of an RB, RBG, or subchannel, as shown in Figure 3. or the highest index, or frequency band, e.g., Bandwidth Part (BWP) It can be located in the middle.

[0116] As further shown in FIG. 3, the NR-PSCCH carrying the SCI is distributed over adjacent RBs, G, or subchannels. However, the NR-PSCCH is also assigned to the vehicle UE. The sidelink BWP may be distributed over the entire sidelink BWP, for example, in a frequency diversity gain. For each subchannel, non-adjacent RBs, RBGs, or subchannels may be allocated.

[0117] As shown in FIG. 4, the resources in the sidelink are time (e.g., symbol pool). ) and frequency (e.g., RB pool, RBG pool, or sub It can be structured by the number of RBs, RBGs, or subchannels available in a channel pool. This can be either periodic or aperiodic, and can be for medium or large size messages. This allows for very low latency transmission to

[0118] In one example, UE-v1 is configured to use more RBs in its BWP “BWP-v1”. In this case, from RB k1 to RB k2 or from RBG k1 to RBG k2, or are from subchannel k1 to subchannel k2, during the period "Period-v1", respectively. NR- at symbol 1 "Sym1" in subframes "SF 0" and "SF l1" A short message with control on the PSCCH, e.g., SCI, and symbol 2 "S In this case, the NR-PSSCH transmits data in the NR-PSSCH. The control on the CCH and the data on the NR-PSSCH must be in the same RB or RBG. or TDMed via subchannels.

[0119] In another example, UE-v2 transmits subframes “S Large messages with control on NR-PSCCH for "SF 0" and "SF 12" For example, SCI and NR-P FDMed in symbol 5 “Sym5” Data on SSCH and residual on NR-PSSCH at symbols 6 and 7 UE-v2 transmits large messages over only four symbols. In order to transmit, the BWP "BWP-v2" has more RBs as shown in the figure. When used with WP "BWP-v2", BR 0~RB N or RBG 0~RB In the range of GN or subchannel 0 to subchannel N, the BWP is longer than that of UE-v1. It's huge.

[0120] When NR-PSCCH and NR-PSSCH are TDMed as shown in Figure 4, The PSCCH carrying the SCI may be allocated over the same or different frequency locations. For example, as shown in FIG. 3, two 1000-MHz ... or may be located in a different frequency range, e.g., BWP-v2, or They may be located across different frequency locations without any overlap (not shown in FIG. 4).

[0121] As further shown in FIG. 4, the NR-PSCCH can be transmitted over adjacent RBs, RBGs, or subchannels. However, NR-PSCCH is also allocated first using frequencies (e.g. For example, first fill in the frequency resources in the first symbol, then in the second symbol. ) or first using time mapping (e.g., first the first RB, RBG, if first subchannel, then the second RB, RBG, or time resource in the subchannel The BWP of the vehicular UE can be filled with the BER (filled with the BER) and distributed within the entire BWP of the vehicular UE in the first symbol (filled with the BER). For example, they may be allocated in non-adjacent RBs, RBGs, or subchannels, or may be distributed within the BWP of the vehicle UE over the first two symbols as an example.

[0122] The resources in the sidelink may also or alternatively be determined by the time in minislots (e.g. For example, the time length in adjacent symbols can be structured as a 14-symbol slot or sub-slot. Each subframe (e.g., each subframe contains one slot, so slots and and subframe are interchangeable in the example, 15KHz subcarrier numerology) For example, a minislot may consist of 1, 2, 4, or 7 adjacent symbols. As shown in FIG. 5, a two-symbol minislot may include pool) and the number of available RBs in the frequency band. or RBG or subchannel (e.g., RB pool or RBG pool or subchannel) This is used for allocation of memory channels (channel pools) with a larger granularity than symbol-based allocation. but allows finer granularity in time than subframe-based allocation. This can save signaling bits for large data transmissions in a short time. Slot-based time allocation supports both periodic transmissions and non-periodic (e.g., event triggered) This can be applied to both (i.e., transmission of

[0123] In one example, UE-v1 is configured to use more RBs in its BWP “BWP-v1”. In this case, from RB k1 to RB k2 or from RBG k1 to RBG k2, or The subchannels k1 to k2 are displayed in the BWP "BWP-v1". In minislot 1 of frames "SF 0" and "SF l1", Short messages with control, e.g., SCI, and data in NR-PSSCH In this case, control on NR-PSCCH and The data in the same RB or RBG or subchannel within a two-symbol minislot The signal is TDMed via

[0124] In another example, UE-v2 transmits subframes “S In minislots 3 and 4 of "SF 0" and "SF 12", Large messages with control, e.g., SCI, and TDMed NR-PSS Transmit data on CH.

[0125] In another example, UE-v3 transmits in minislot 0 with control on NR-PSCCH. Transmits intermediate messages and data in the NR-PSSCH that are TDMed. Then, the same transmission is repeated in minislot 1 of subframe "SF 11". The received signal may be sent to a different receiver each time (e.g., repeatedly in minislots). The received signal may be transmitted to the receiver (e.g., beam sweeping in minislots).

[0126] As further shown in FIG. 5, the NR-PSCCH carrying the SCI is distributed over adjacent RBs, G, or subchannels. However, NR-PSCCH also first Using a frequency band (e.g., first the frequency band in the first symbol, then the frequency band in the second symbol) source), or first using time mapping (e.g., first R B, RBG, or subchannel, then a second RB, RBG, or subchannel (filled with time resources in and distributed within the entire sidelink BWP of the vehicular UE (e.g., non-adjacent RBs, R BG, or subchannel) or the first of the first minislot The sidelink BWP of the vehicular UE may be distributed over two symbols:

[0127] For frequency resources (RB or RBG pool or subchannel pool) ,The vehicular UE may use adjacent RBs, RBGs, or subchannels, or non-adjacent RBs, RBG, or subchannel. For a channel, a resource is a starting point in units of RB, RBG, or subchannel. and length from the start point, e.g., {RB start ,RB length}if RBG start ,RBG length} or {Subchannel sta rt ,Subchannel length} or RB, RBG and subchannel For non-adjacent RBs, RBGs, or subchannels, The source is {RB start1 R.B. length1 ,RB start2 R.B. lengt h2 ,...,RB startN R.B. lengthN}, {RBG start1 R.B. G length1 ,RBGstart2 RBG length2 ,...,RBG sta rtN RBG lengthN} or {Subchannel start1 Su bchannel length1 ,Subchannel start2 Subchan nel length2 ,...,Subchannel startN ,Subchannel el lengthN} (each N>1), or RB, RBG, and subchannel A combination of uniformly distributed non-adjacent RBs or RBGs or sub-RBs may be used. For each channel, the resources are start R.B. length ,RB g ap} or {RBG start RBG length ,RBG gap} or {S ubchannel start Subchannel length ,Subchannel el gap}, or a combination of RB, RBG, and subchannel.

[0128] The bitmap is used for the RB or RBG pool or the subchannel pool. If so, the bit string must operate for the sidelink, e.g. the sidelink BWP. It can be mapped to RB, RBG, or subchannels within the band. For example, RB , b RB-1 ,...,b1,b0} is the number of bits for the first RB (e.g., RB0). RB in Then, for the last RB (e.g., RB N), it is mapped with b0. In the example, {b RBG ,b RBG-1 ,...,b1,b0} is the first RBG (e.g. , RBG 0) for b RBG and the last RBG (e.g., RBG N ) with b0 or {b Subch ,b Subch-1 ,.. .,b1,b0} is the b for the first subchannel (e.g., subchannel 0). Sub ch and for the last subchannel (e.g., subchannel N) To be mapped.

[0129] For a resource (e.g., symbol or minislot pool) in time, the starting synchronisation The starting minislot or starting frame number is the System Frame Number (SF N) or Direct Frame Number (DFN) A symbol or minislot may be referenced from a time reference point. For example, a symbol or minislot may be referenced from a time reference point. or DFN number + symbol number in frame" or "SFN or DFN number + The time length or duration may be indexed as "minislot number within a frame." It can be within a symbol, a minislot or slot, or a subframe. For a new time allocation, the resource start1 Symbol le ngth1 Symbol start2 Symbol length2 ,...,Sym bol startN Symbol lengthN}, {mini-slot start 1 mini-slot length1,mini-slot start2 mini- slot length2 ,...,mini-slot startN mini-slo t lengthN}, {slot start1 ,slot length1 ,slot st art2 slot length2 ,...,slot startN slot leng thN} or {Subframe start1 Subframe length1 ,Subframe start2 Subframe length2 ,...,Subf rame startN ,Subframe lengthN} (each with N>1), and is represented as a combination of symbols, minislots and slots, or subframes. Uniformly distributed non-adjacent symbols or minislots or slots or for the subframes, and the resources are {Symbol start .Symbo l length Symbol gap} or {mini-slot start ,m ini-slot length ,mini-slot gap} or {slot st art ,slot length ,slot gap} or {subframe sta rt ,subframe length ,Subframe gap} or the symbol, It may be indicated in terms of two slots and combinations of slots and subframes.

[0130] When bitmaps are used to represent resources with symbols, the symbol For example, {b s ,b s-1 ,...,b1,b0} is the first b for symbol s and for the last symbol it is mapped to b0. A value of "1" indicates an assignment at this symbol.

[0131] When a bitmap is used to indicate resources in minislots, the number of minislots in a time interval is For example, {b m ,b m-1 ,...,b1,b0} is , b for the first minislot m and b0 for the last minislot. A value of "1" indicates an allocation in this minislot.

[0132] To save mapping bits, a two-level mapping can be used. For example, a f ,a f-1 ,...,a1,a0} is mapped to an SFN or DFN (e.g. For example, for the first SFN or DFN, f , the last SFN in the time interval or D a0) for FN, {c s ,c s-1 ,...,c1,c0} are symbols in the frame. or {c m ,c m-1 ,...,c1,c0} are frames The RBTC is mapped to a minislot or slot within the

[0133] Sidelink resource or resource pool configuration or allocation in frequency and time In this case, the cell is transferred via Uu under network control (e.g., gNB or eNB management). per carrier or cell per BWP in a Radio Resource Control (RRC) message, or without network control (e.g. UE management) The sidelink RRC (SL-RRC) may be configured via the

[0134] Sidelink resource or resource pool configuration or allocation is not required for the Uu interface. using SI or shared or common RRC over the interface, or sidelink (PC5) SL-SI or shared or common SL-RR via interface The sidelink resources can be periodically broadcast using the C message. Resource pool configuration or allocation can also be configured via the Uu interface to allow dedicated R using RC messages or via the Sidelink (PC5) interface In particular, the SL-RRC message for the This may be per UE request.

[0135] For RRC over the Uu interface, the physical downlink control channel (Phys The control resource set (CoR) carried by the Physical Downlink Control Channel (PDCCH) The Control Resource Set (CORESET) is used in common or UE-specific RRC messages. RRC assigns a common search space (CSS) or Each is composed of UE Search Space (USS). CSS Or DCI in CORESET in USS is physical downlink shared channel (Ph A common broadcast channel carried on the Physical Downlink Shared Channel (PDSCH) is Addresses the location of the stored RRC or UE-specific RRC message, respectively .

[0136] New radio physical support for SL-RRC via sidelink (PC5) interface Sidelink control resource settings carried on the sidelink control channel (NR-PSCCH) The Sidelink-Control Resource Set (SL-CORESET) is a common or UE Sidelink by RRC or SL-RRC for specific SL-RRC messages Common Search Space (Sidelink-Common Search Space: SL-CSS) or Sidelink Sidelink-UE Search Space (SL-USS) The size of the SL-CORESET in the SL-CSS or SL-USS is Sidelink Control Information (SCI) is transmitted over the New Radio Physical Sidelink Shared Channel (NR-PSSC H) carried by a common broadcasted SL-RRC or a UE-specific SL- Address the location of the RRC message respectively.

[0137] Sidelink resource pool allocation or configuration in frequency and time is also With network control (e.g., gNB or eNB managed resource allocation) A Medium Access Control (MAC) control element (Con control element (CE) or without network control (e.g. UE managed resource allocation) Sidelink medium access via sidelink (PC5) interface with Control (Sidelink-Medium Access Control: SL-MAC). RRC or The set or subset of resources or resource pools configured in SL-RRC is By the MAC CE or SL-MAC CE, e.g., using the configuration index In addition, the resource or resource pool configuration may be MA for semi-static allocation. It can be enabled or disabled by the C CE or the SL-MAC CE.

[0138] Sidelink resource pool allocation or configuration in frequency and time is also With network control (e.g., gNB or eNB managed resource allocation) via Uu It may be dynamically indicated in the Downlink Control Information (DCI) or without network control (e.g. For example, UE managed resource allocation) over the sidelink (PC5) interface It may also be dynamically indicated in the sidelink control information (SCI).

[0139] Sidelink resources or resource pools configured in RRC or SL-RRC The set or subset may be communicated by DCI over the Uu interface or by a sub By SCI via the IdLink (PC5) interface, e.g., configuration index The resource allocation in time and frequency may be indicated using the Different description methods (e.g. bitmaps) are used to determine time allocation and frequency in the allocation field, respectively, in the DCI via the Uu interface, or on the side It can be directly presented to the SCI via the Link (PC5) interface.

[0140] Additionally, sidelink resource or resource pool configuration or allocation is semi-persistent. For any allocation or scheduling, the DCI is or by the SCI via the Sidelink (PC5) interface. may be disabled, which is the same as a DCI or SCI (e.g., a scheduling assignment The resource configuration carried on the Scheduling Assignments SCI (SA SCI) and in sidelink resource allocation mode, e.g. Related sidelink resource or resource pool configuration or assignment Enable source allocation mode to allow for DCI over the Uu interface or It can be enabled or disabled by the SCI via the Sidelink interface.

[0141] (Resource configuration) A method and system for resource configuration in sidelink is disclosed.

[0142] In the first example, the sidelink resources are allocated to common or dedicated RRC or SL-RRC. The resource pool may be statically configured by a message, for example, the resource pool may be configured by a vehicle UE by As an example, the access network is When the UE is connected to a network (e.g., a gNB or a gNB-like RSU), or For example, the vehicle UE may be a non-access stratum (NAS) or an access stratum (Access-Strat V2X applications can be deployed in the cloud or infrastructure via um:AS) messages. The resource pool configuration may be configured when the vehicular UE registers with the application server. When connected to an access network or a V2X service server, RRC or S L-RRC message or Medium Access Control (MAC) Control Element (CE) or S L-MAC is performed semi-statically by the CE or by the gNB or RSU such as a gNB. It can be dynamically updated by downlink control information (DCI). The sidelink resources are allocated to the selected New Radio Sidelink Primary Synchronization Signal (New Rad io-Sidelink Primary Synchronization Signal (NR-SPSS) / New Wireless Sidelink New Radio-Sidelink Secondary Synchronization Signal :NR-SSSS) / New Radio Physical Sidelink Broadcast Channel (New Radio-P Master SL of the Basic Sidelink Broadcast Channel (NR-PSBCH) block -New radio physical sidelink broadcast channel carrying SL-SI or main SL-SI channel (NR-PSBCH) or selected NR-SPSS / NR-SSSS / NR - remaining or other SL-SI or SL-R associated with the PSBCH block New Radio Physical Sidelink Shared Channel (NR-PSSCH) to carry RC messages Statically configured by the SL-SI conveyed by or indicated by the and / or RSUs as proximate coordinators, proximate leads, groups Loop lead or synchronization source UE to New Radio Physical Sidelink Control Channel (NR -Scheduling assignment sidelink control information (SCI) carried on the PSCCH The display may be semi-persistent or dynamic.

[0143] For sidelink resources, different vehicle UEs may use different capabilities or characteristics (operational The system can be configured differently according to the vehicle's driving automation level and V2X application. For example, the resource pool for highly autonomous vehicle UEs is designed to provide very low latency, as previously mentioned. Therefore, the automation level of the vehicle UE can be increased by 100%. The role of the human operator or automated system is primarily to monitor the operating environment. Based on whether the vehicle satisfies the requirements, the level of automation for driver control is determined. n:LoA) SAE0-2 and SAE3-5 for vehicle control and other configurations can be used. The automation level of the vehicular UE is determined by the vehicular UE during the sidelink resource configuration procedure. This may be indicated by a higher layer parameter, for example auto_level, which may be indicated from the

[0144] For side link resources, the resource pool is used to manage ambulance traffic for medical emergency mode. Different operating modes, e.g. priority levels, for different types of vehicle UEs, e.g. The operating modes, e.g., high_priority_mode, , may be indicated from a higher layer or from the application layer.

[0145] For sidelink resources, the resource pool is allocated to different vehicle UEs with different speeds. may be configured separately for low latency UEs at high speeds, so that vehicular UEs at high speeds may use low latency resources. The speed parameter may be configured in the pool at the upper layer or application layer. It can be shown from

[0146] For sidelink resources, the resource pool is allocated according to the location or range of the vehicular UE. may be configured such that vehicular UEs at different locations may share shared resources, e.g. It may consist of resources that are reused per location or nearby, and the parameter loca The tion_zone can be indicated from an upper layer or from the application layer.

[0147] For sidelink resources, the vehicular UE may may be configured separately based on the role of the leader or member of the formation, for example. The UE role, e.g., ue_role, can be configured separately by higher layers or applications. The application layer may represent the

[0148] For sidelink resources, different V2X applications can be configured separately. For example, the resource pool for the lead vehicle UE is the same as that for the platooning application. The vehicle UE may be configured separately from the member vehicle UE, but may be used with the vehicle UE for extended sensor applications. The resource pools between E can be configured the same. In addition, different applications or Services may have different performance requirements and resources may be configured with different priority levels. Thus, a vehicle UE may be configured to handle different applications, each of which may have different priority levels. The priority level may be configured in different configurations associated with application IDs or service IDs. The application or service ID to server mapping is determined by the upper layer or application The vehicle UE may be handled by the application, and the vehicle UE may be pp_id or app_index or service_id for the service Select resource configuration according to higher-level parameters such as service_index possible.

[0149] For sidelink resources, different data communications may be configured differently. For example, For areas with low traffic volume, the resource pool is the upper layer or application layer. , for example, a parameter p having a value "1" for periodic and "0" for aperiodic. Periodic transmission (e.g., semi-persistent resource) as indicated by periodic_flag. subscription-based sensing) and aperiodic or event-triggered transmissions (e.g., (using rapid channel sensing for access to resources) or The spool can be managed by the upper layer or application layer, for example by the parameter Broadcast, multicast, and user as indicated by ation_type. However, for high traffic areas, semi-persistent The probability of collisions between the large periodic transmissions and the event-triggered large data transmissions is very high. To reduce collisions, the vehicular UEs may allocate different resources for different data traffic. Pooling (e.g., periodic small data transmissions using sense-based semi-persistent reservations) or intermediate data transmission), as well as priority-based channel sensing Very low latency and high reliability events using the access scheme The trigger may be configured as a resource pool for large data transmissions, and the parameter pr The identity is indicated by the upper layer or the application layer (e.g., first the channel and detects the vehicular UE's priority with or without backoff. and waiting for a time interval that may be associated with the priority of the vehicle UE, (If the channel is occupied, it will sense the channel again). To reduce collisions, e.g. In half-duplex communication, the UE cannot receive and transmit at the same time, and broadcast, Multicast and unicast may also be used to, for example, handle different packets that are allocated at different times. It may consist of a resource pool that

[0150] All parameters exemplified for resource or resource pool configuration or allocation The meter is configured by the RRC or SL-RRC and the MAC CE or SL MA C CE indicates that the data is to be transmitted by DCI or SCI. The request can be signaled automatically.

[0151] In the second example, we use very low latency to more efficiently utilize the resource pool. and to meet the more stringent resource requirements for high reliability vehicular UEs, The pool is connected to the SL- Using RRC messages, SL-MAC-CE, or SA SCI (e.g., (at busy intersections) by the RSU acting as a nearby coordinator to coordinate the platoon It may be configured locally by column leads or by adjacent group leads.

[0152] An example of resource pool configuration and reconfiguration for entering a platoon can be seen in the following steps: 6A and 6B, which may include In step 0, the vehicular UE is under network control over the Uu interface. In this case, the gNB or V2X cloud server or RSU such as a gNB, or RSU as a nearby coordinator via the Drink (PC5) interface ,The resource pool configuration is performed by the adjacent lead, group lead, or synchronization source UE. It may be constructed first and then updated.

[0153] In step 1A, the formation lead transmits the new radio primary sidelink synchronization signal for synchronization. (New Radio Primary Sidelink Synchronization Signal: NR-PSSS) and New Radio Secondary Sidelink Synchronization Signal (NR-SSSS) and Master or Primary Synchronization Signal Stem information and / or master or core group information, and for group discovery New Radio Physical Sidelink Discovery Channel channel: NR-PSDCH) or New Radio Physical Sidelink Shared Channel (NR-PS SCH) or remaining or other SL-SI or SL-RRC messages NR-PSSCH, and synchronization and transmission signals over the sidelink interface, including The information may be broadcast or beam swept periodically.

[0154] In step 1B, the vehicle UE may discover the platoon lead. One or more of the following: That is, the vehicle UE selects the best NR- The vehicle UE may select a PSSS / NR-SSSS / NP-PSBCH block, and the vehicle UE may NR-PSBCH (e.g., SL-CORESET allocation for NR-PSSCH) The NR-PSSS / NR-SSSS / NR-PS BCH blocks are mapped or quasi-colocated (QCLed) to BCH blocks. A selected system having discovery information about QCL type D for example spatial QCL relationship N Detects and decodes the R-PSDCH or NR-PSSCH and transmits it to higher layers or may be passed to the application and / or to a higher layer or application decides to join the ranks.

[0155] In the first option, the reconfiguration is performed using a broadcast link as illustrated in FIG. 6A. It may be based on a source pool (eg, broadcast-based). In step 2A, the platoon lead periodically broadcasts or This can be done, for example, by using the Sidelink Master Information Block (SMIB). The NR-PSBCH carrying the NR-SMS Master Information Block (SL-MIB), or NR-PSBCH, or each NR-PSSS / NR-SSS S / NR-PSBCH block or QCLed (e.g. , carrying the remaining or other SL-SI or SL-RRC messages) NR-P Assigned to a formation in the SSCH (e.g., secured and / or unsecured) resources (not included) or each NR-PSSS / NR-SSSS / NR-PSBCH block QCLed (e.g., SL-SI or SL- The total constellation resources (e.g., used) in that NR-PSSCH (carrying RRC) The resource may be an available resource (not yet available or reserved).

[0156] In step 2B, the vehicular UE may reconfigure the resource pool to one of the following: There may be multiple occurrences of NR-PSSS / NR-SSS. S / NR-PSBCH blocks or QCLed beams Sense available resources of the total platoon resources broadcast by the platoon lead (Note that an example of sensing is shown later in FIG. 16) whether the NR-PSSS / NR-SSSS / NR-PSBCH block corresponds to the or available broadcast by the formation lead in a QCLed beam. Based on available resources and / or sidelink channel occupancy, sidelink free Line quality or interference, e.g. Reference Signal Received Power :RSRP), Reference Signal Received Quality (RSRQ) , or DMRS for NR-PSSS / NR-SSSS or NR-PSBCH, or Periodic New Radio Sidelink Channel State Information Reference Signal Signal Interference in the CSI-RS (CSI-RS State Information Reference Signal (NR-SL)) For measuring Signal to Noise and Interference Ratio (SINR) etc. Based on the resource pool candidate, the vehicular UE may select a resource pool candidate if available. Spool or resource candidates and associated measurements, if available, are passed to higher tiers or and / or a higher layer or application may A resource pool or resource configuration to use may be determined.

[0157] In step 3, the vehicle UE may request to join the platoon. The request may be sent to the platoon by the synchronous NR-PSBCH of the lead in the current study (e.g., SL-MIB) or NR-PS DCH or NR-PSSCH, or NR-P on Sl-CSS or SL-USS Either indicated by SBCH or indicated by SL-CORESET, if or selected NR-PSSS / NR-SSSS / NR-PSBCH block, or The selected NR-PSSS / NR-SSSS / NR-PSBCH block is 2B in the selected beam, or or QCLed (e.g., carrying SL-SI or SL-RRC) NR- It may be transmitted on the default or common sidelink resources indicated by the PSSCH. The request is sent via the new format New Radio Physical Sidelink Control Channel (NR-P SCCH or New Radio Physical Sidelink Feedback Control Channel (New Radio Physical Sidelink Feedback Control Channel (NR-PSFCCH), or NR - It can be carried on PSSCH.

[0158] In step 4, the platoon lead receives the vehicle UE associated with the request to join the platoon. The response may be transmitted to the NR-PSBCH (e.g., SI-MI) of the lead in synchronization. B) or NR-PSDCH or NR-PSSCH or NR-P N, as indicated or selected by SBCH (e.g., SL-CORESET) Mapped to R-PSSS / NR-SSSS / NR-PSBCH blocks or is transmitted by QCLed NR-PSSCH (e.g., SL-SI or SL-RRC). The default sidelink resources indicated by - Mapped to SSSS / NR-PSBCH blocks or QCLed In step 3, the vehicular UE requests the beam or transmits the transmission configuration indicator. Transmission Configuration Indicator (TCI) status or associated Selection indicated by the vehicle UE with a Reference Signal (RS) index The response may be sent in the resource pool within the sidelink group ID. SL-G-RNTI and Group Member ID SL-G-CRNTI, and For different communication types such as broadcast, multicast, and unicast Sharing between platoon members for shared or dedicated resources and for each communication type The response may include the associated resource pool configuration for the new file or for the dedicated resources. Format: NR-PSCCH, NR-PSFCCH, or NR-PSSCH can be sent.

[0159] In the second option, the reconfiguration is based on multicast as illustrated in FIG. 6B. can be based on a set of criteria (e.g., group-based). In step 2, a vehicle UE may request to join the platoon. the broadcast NR-PSBCH of the Or for selected NR-PSSS / NR-SSSS / NR-PSBCH blocks Selected NR-PSSS / NR-PSSS in the attached or QCLed beam N that is mapped to an SSSS / NR-PSBCH block or QCLed The default or selected cycle indicated on the R-PSDCH or NR-PSSCH. It may be transmitted in the drink resource.

[0160] In step 3, the platoon lead receives the vehicle UE associated with the request to join the platoon. The response may be sent via the lead broadcast NR-PSBCH or NR - the default resource pool indicated by the PSDCH or NR-PSSCH, or a selected The selected NR-PSSS / NR-SSSS / NR-PSBCH block is assigned to the or indicated by UE request in QCLed beam or TCI The selected RS is indicated by the vehicle UE in terms of its status or associated RS index. The response may be sent with the sidelink group ID SL-G-RNT I and group member ID SL-G-CRNTI, as well as broadcast, Shared or dedicated resources for different communication types, such as multicast and unicast Shared or dedicated resources among platoon members for each source and for each communication type The resource pool configuration for the resource pool may include associated resource pool configuration for the resource pool.

[0161] In step 4A, the platoon lead is indicated by the Scheduling Assignment (SA) SCI. The resource pool is periodically multicast or beamed on the NR-PSSCH. This can be assigned to a formation (e.g. reserved and unreserved). Total resources (i.e. not yet reserved) or total platoon resources available (i.e. not yet reserved) It can be a valuable resource.

[0162] In step 4B, the vehicular UE may reconfigure the resource pool to one of the following: There may be multiple occurrences of NR-PSSS / NR-SSS. S / NR-PSBCH blocks or QCLed beams Use the Sidelink Group ID SL-G-RNTI for multicast messages. Decode the SA SCI using the by the SA SCI field for the group ID, source ID, or group ID. The total number of platoon resources is multi-cast by the platoon lead. Multicast based on sensing available resources of the source or by platoon lead. Based on available resources as provided and / or when available, sidelining channel occupancy, sidelink radio quality and interference (e.g. measured on the sidelink) Based on measurements such as RSRP, RSRQ, or SINR (based on the For dedicated resources that are assigned to group members according to the or the SA SCI field for the group member ID. You may select resource pool candidates based on the pool member ID SL-G-CRNTI. In addition, the vehicular UE may use the candidate resource pool and, if available, sidelink measurements to It may be passed to a higher layer or application and / or The application can determine the resource pool configuration to use.

[0163] In the third option, the reconfiguration is based on unicast as illustrated in FIG. 6B. It is possible to make a transaction (e.g., ask / response). In step 2, the vehicle UE may transmit a request to join the platoon. The request is ,As ,described ,beam-based ,broadcast ,NR-PSBCH ,(e.g. , SL-MIB) or NR-PSDCH or PSSCH (e.g., SL-SI or The sidelink resource allocation is performed using the default or selected sidelink resources indicated in the sidelink resource allocation (SL-RRC). It can be believed.

[0164] In step 3, the platoon lead receives the vehicle UE associated with the request to join the platoon. The response may be sent via the lead broadcast NR-PSBCH or NR - May be transmitted in a resource pool in PSDCH or NR-PSSCH, or The group RNTI and the link RNTI may be indicated at the UE request in the beam as described. The response includes the Sidelink Group ID SL-G-RNTI and the Group Loop member ID SL-G-CRNTI, as well as broadcast and multicast For shared or dedicated resources for different communication types, such as multicast, direct, and unicast and for shared or dedicated resources among formation members for each type of communication. , and the associated resource pool configuration. The resource pool configuration may also include individual Another unicast message, e.g. (using the UE's group member ID) The SA-SCI may be transmitted on the PSSCH that is specifically indicated to the UE by the SA-SCI.

[0165] In step 4, the vehicular UE may reconfigure the resource pool. Multiple occurrences may occur, i.e., the vehicle UE may have different available resources for the shared resource. Based on the perception of the group, or the dedicated resources presented to group members, and Sidelink measurements such as link channel occupancy, sidelink radio quality or interference Based on the value, the response may select a resource pool candidate, as described above. When possible, the vehicular UE will communicate the resource pool candidates and, if available, the measurements to higher layers. or application, and / or may be passed to a higher layer or application. The application determines the resource pool configuration to use.

[0166] An example of resource pool configuration and reconfiguration for exiting the platoon can be seen in the following steps: 7A and 7B, which may include At step 0, the vehicle UE may be associated with the platoon lead and other numbers within the group.

[0167] In the first option as illustrated in FIG. 7A, for example, an RSU or another Discover the UE. In step 1A, an RSU or another UE receives a synchronization signal and discovery information, e.g., NR-PSSS / NR-SSSS / NR-PSBCH, NR-P Each NR-P is either indicated by the SBCH (e.g., SL-MIB) or for discovery. Mapped to SSS / NR-SSSS / NR-PSBCH block or QC Periodically broadcasts or transmits the LED-illuminated NR-PSDCH or NR-PSSCH. The beam sweep is performed for each NR-PSSS / NR-SSSS / NR-PSBCH block. NR-PSCCH and The NR-PSSCH and / or NR-PSSCH may be broadcast or beamswept.

[0168] In step 1B, the vehicular UE may discover an RSU or another UE. One of the following: Or multiple occurrences may occur. That is, the vehicle UE may receive the RSRP, RSR, The best NR-PS found based on sidelink measurements such as Q or SINC SS / NR-SSSS / NR-PSBCH, and the vehicular UE may select the selected N Mapped to R-PSSS / NR-SSSS / NR-PSBCH or QCL Detect and receive NR-PSDCH or NR-PSSCH for discovery in the ed beam Receive and decode sidelink measurements, and, if available, transmit them to higher layers or applications. and / or a higher layer or application may For use after it leaves or is broadcast by an RSU or other UE The resource pool configuration may be determined to use the resource pool configuration that is being used.

[0169] In step 2, the vehicle UE may request to exit the platoon. The request is made as shown in FIG. Broadcast, multicast, or unicast as described in Figure 6A and Figure 6B. The sidelink resource may be selected from the resources provided by the mobile station.

[0170] In step 3A, the platoon lead identifies the vehicle U associated with the request to exit the platoon. The response may be sent to resource E as described with respect to Figures 6A and 6B. In the pool configuration, it may be transmitted on sidelink resources or indicated in the UE request. This is also fine.

[0171] In step 3B, the vehicle UE is configured or or other member UEs in the resource pool indicated in the UE request (e.g. Receive responses from both UEs (and relay member UEs from this vehicle UE) to leave the platoon possible.

[0172] The second option, as illustrated in FIG. 7B, for example, is to exit the formation first. In step 1, a vehicle UE may request to exit the platoon. The request is made as shown in FIG. 6A and 6B, the broadcast, multicast, or unicast The sidelink resource may be selected and transmitted over the selected sidelink resource.

[0173] In step 2A, the formation lead determines whether or not the formation is in a configuration as described with respect to FIG. 6A and FIG. 6B. Or respond to requests to leave the formation with a resource pool indicated by the UE request The UE may then transmit a response to the associated vehicle UE.

[0174] In step 2B, the vehicle UE is configured or or other member UEs in the resource pool indicated in the UE request (e.g. Receive responses from both UEs (and relay member UEs from this vehicle UE) to leave the platoon possible.

[0175] In step 3A, the RSU / other UE receives synchronization signals and discovery information, i.e., synchronization and NR-PSSS / NR-SSSS / NR-PSBCH for signal processing and beamforming, Each NR-PSSS / NR-SS indicated by the R-PSBCH or for discovery SS / NR-PSBCH block or QCLed NR- PSDCH or NR-PSSCH, and each NR-PSSS / NR-SSSS / NR- The resource pool configuration that is mapped to the PSBCH block or QCLed Periodically broadcast the NR-PSCCH and / or NR-PSSCH It may be broadcast or beam swept.

[0176] In step 3B, the vehicle UE may discover the RSU or other UEs. That is, the vehicle UE may implement one or more of the RSRP as described above. , RSRQ, or SINC. The vehicle UE may select R-PSSS / NR-SSSS / NR-PSBCH, and the vehicle UE may select NR-PSSS / NR-SSSS / NR-PSBCH or detects and decodes NR-PSDCH in the QCLed beam and makes it available If appropriate, sidelink measurements may be passed to higher layers or applications, and and / or higher layers or applications may provide or uses the resource pool configuration broadcast by the RSU or other UEs. The resource pool configuration for the QoS management may be determined.

[0177] For both the first option and the second option as shown in FIG. In step 4, the vehicular UE receives the resource selected by the higher layer or the application. The spool may be reconfigured.

[0178] In step 5, the vehicular UE transmits in the sidelink resource pool that is selected after the reconfiguration. Basic Safety Message (BSM) or consensus message transmitted A Common Awareness Message (CAM) may be broadcast.

[0179] Switching between RSUs of different Public Land Mobile Networks (PLMNs) An example of a resource pool configuration and reconfiguration to change the resource pool includes, for example, the following steps: The resulting structure is shown in FIG. 8A and FIG. 8B. In step 0, the vehicular UE configures and updates the resource pool configuration in the RSU of PLMN1. New.

[0180] In step 1A, the RSU2 of the PLMN2 receives the synchronization signal and discovery information, i.e., and NR-PSSS / NR-SSSS / NR-PSBCH for beam selection, NR- Each NR-PSSS / NR-SSSS indicated by the PSBCH or for discovery / NR-PSBCH block is mapped to or QCLed NR-PS DCH or NR-PSSCH, and each NR-PSSS / NR-SSSS / NR-P Enables resource pool configuration that is mapped to SBCH blocks or QCLed. Periodically broadcasts the NR-PSCCH and / or NR-PSSCH to The beam may be broadcast or beam swept.

[0181] In step 1B, the vehicular UE may discover RSUs of other PLMNs. One of the following: Or multiple occurrences may occur. That is, the vehicle UE may Detection based on sidelink measurements such as RSRP, RSRQ, or SINR The vehicle may select the best NR-PSSS / NR-SSSS / NR-PSBCH for which Both UEs shall use the NR-PSSS / Mapped to NR-SSSS / NR-PSBCH blocks or QCLed Detect and decode the received NR-PSDCH or NR-PSSCH, and receive discovery information and and, if available, pass sidelink measurements to higher layers or applications. and / or the upper layer or application may enter the selected RSU. The resource pool configuration for the selected NR-PSSS / NR-SS Resources that are mapped to or QCLed into SS / NR-PSBCH blocks NR-PSBCH or NR-PSCCH and / or NR-PSBCH with spool configuration - Using the resource pool configuration broadcast by the RSU in the PSSCH It may be determined that:

[0182] In the first option (broadcast, discovery-based) as shown in Figure 8A, In step 2, the vehicular UE sends a request to disassociate from the RSU1. The request may be sent to the configuration of RSU1 in a manner similar to that described in FIG. 7A and FIG. 7B. The sidelink resource pool may be used to transmit the sidelink packets.

[0183] In step 3, RSU1 of PLMN1 performs a similar process as described in FIG. 7A and FIG. 7B. In the method, the RSU1 is configured to receive a resource pool indicated in the configuration of the RSU1 or at the request of the UE. may send a response to the associated vehicle UE to the request to disassociate from the associated vehicle UE. .

[0184] In step 4, the vehicular UE may request to associate with the RSU2. The NR-PSBCH or Default or NR-PSDCH or NR-PSSCH indicated by RSU2 may be transmitted on the selected sidelink resource pool. May include UE assistance information such as priority, latency, reliability, speed, location, etc.

[0185] In step 5, RSU2 of PLMN2 performs a similar process as described in FIG. 6A and FIG. 6B. In the method, the RSU2 is configured to receive the resource from a resource pool indicated in the configuration of the RSU2 or at the request of the UE. The vehicle UE may transmit a response to the request to associate with the vehicle UE.

[0186] In the first option, steps 2 to 5 may be optional, and Note that steps 2 and 3 may be reordered with steps 4 and 5. .

[0187] In the second option (unicast-based, response-based) as shown in Figure 8B, In step 2, the vehicular UE may request to associate with the RSU2. The target is determined by its NR-PSBCH or NR-PSDCH or NR-PSSCH. The sidelink resource pool is the default or selected sidelink resource pool of the RSU2 indicated. Vehicle UEs can provide a set of criteria for priority, latency, and reliability in their requests for resource allocation. The UE assistance information may include UE capability, speed, location, traffic type, etc.

[0188] In step 3, RSU2 in PLMN2 sends, as an example, A resource pool configuration for the vehicular UE based on the UE assistant information provided in the configuration. Or a request to map the RSU2 to the resource pool indicated in the UE request. The vehicular UE may transmit a response to the resource pool configuration associated with the host. A request for reconfiguration or a request for a later reconfiguration may also be sent, which may include: New or updated UE assistant information for the resource pool (e.g. location change) The parameters may include changes in speed, etc.

[0189] In step 4, the vehicular UE may request to disassociate from the RSU1. The request may be transmitted on the configured sidelink resources of RSU1.

[0190] In step 5, RSU1 in PLMN1 selects the UE 1 in its configuration or at the UE request. Maps a request to unmap RSU1 from the indicated resource pool. The vehicle UE may then transmit a response to the received vehicle UE.

[0191] In the second option, steps 4 and 5 may be optional. I want to be loved.

[0192] For both the first option and the second option as shown in FIG. In step 6, the vehicular UE receives an RSU selected by a higher layer or an application. 2. The resource pool can be reconfigured.

[0193] In step 7, the vehicular UE determines the sidelink resource pool selected for RSU2. The BSM or CAM may be broadcast.

[0194] Messages for matching or unmatching requests or responses are sent in new fields. Format PSCCH or New Radio Physical Sidelink Feedback Channel (New R Radio Physical Sidelink Feedback Channel (NR-PSFCH), or sidelink It can be carried on the NR-PSSCH over the PC5 interface.

[0195] (Auxiliary Resource Allocation Sensing Assistant) For highly autonomous vehicles in advanced driving scenarios, low latency and high reliability are essential. For example, an autonomous vehicle UE detects a fallen object on the road and byte payload, 30 Megabits per second (Mbps) data rate features like strict QoS, 3ms maximum end-to-end latency, and 99.999% reliability Performance requirements require emergency orbits and cooperative operations to be transmitted to nearby RSUs and other UEs .

[0196] However, the sensing-based semi-persistent resource reservation scheme as specified for LTE The system takes a very long time to sense available resource pool candidates. The candidate resource pools are not completely collision-free, which may degrade reliability performance. do.

[0197] To reduce sensing time and potential collisions, the auxiliary sensing is performed by the adjacent coordinated Sensing RSUs, platoon leads, or nearby leads, or vehicle UEs as data This can be provided locally by a Sensing Assistant (SA). The agent monitors the usage and reservation status of local resource pools, as well as interference, congestion, location, Alternatively, the location zone, communication range, etc. may be periodically broadcast, and the sensing assistant The server also provides the usage and reservation status of the local resource pool upon request of the vehicular UE. It can be provided.

[0198] The sensing assistant may be pre-configured by the manufacturer or service provider. , may be configured by a gNB / eNB or a V2X server, and optionally, It is enabled and disabled by the gNB / eNB via the DCI over the interface. Alternatively, the RSU may be connected to the SCI via a sidelink (PC5) interface. Activated and deactivated by the group lead or proximity coordinator or lead. may be made effective.

[0199] An example of auxiliary resource sensing is shown in FIG. 9A and FIG. 9B, which may include the following steps. The sensing assistant can detect the following: traffic patterns (e.g., scheduling resource), information on the period, time offset, message size , QoS information, and a source or destination identifier. The sensing assistant may sense and / or collect any type of information. It should be understood that the present invention is not limited to the above examples.

[0200] In step 0, the sensing assistant collects and broadcasts the resource pool state. The sensing assistant can transmit NR-PSC locally transmitted from all vehicular UEs. Decoding of SA SCI carried on the CH and / or sidelink radio relay Resource management via measurements of link quality and interference (e.g. RSRP, RSRQ, SINC, etc.) Always collects resource pool or resource status and and may periodically broadcast interference, congestion, location or location zone, communication range, etc. .

[0201] In step 1, the vehicle UE may have a large data size to transmit. The application indicates emergency trajectory and cooperative maneuver data to be transmitted.

[0202] In the first option (resource state based on broadcast) as shown in Figure 9A, : In step 2A, the sensing assistant selects the time resource pool and the frequency resource pool. The Routing Engine may periodically broadcast or beam sweep the resource pool state, such as a pool of resources. For example, the bitmaps for the symbol pool or mini slot pool, and the RB pool or A bitmap for the RBG pool or RBG pool can be broadcast. Resource pool or resource status with other information such as location or location zone, communication range, etc. The state is indicated by the NR-PSBCH (e.g., SL-CORESET) or corresponds to each NR-PSSS / NR-SSSS / NR-PSBCH block, Or QCLed NR-PSCCH or NR-PSSCH, or NR-P SA SCI carried on SCCH or NR-PSCCH (e.g., SL-CSS Broadcast indicated by SA SCI carried in SL-CORESET A periodicity configuration may be defined and a specific broadcast The period configuration index is used to select the NR-PSBCH, e.g., four possible period values. This can be indicated by a 2-bit value indicating:

[0203] In step 2B, the vehicle UE may select a resource pool by performing the following steps: One or more of the following may occur: the vehicle UE may use the broadcast resource pool Or, based on the resource status, select a resource pool or resource candidates and Optionally, it may further provide rapid sensing of available resources, e.g., the data ( For example, one or more transport blocks) to determine timelines and latency requirements. The vehicle UE may collect resource reservations within a sensing window defined by the resource reservation. Spool or resource candidates, and sidelink channel conditions, if available ( For example, congestion, radio quality, and interference measurements can be passed to higher layers or applications. and / or a higher layer or application may provide resources for use. Determine the spool.

[0204] The second option (resource state based on request) as shown in Figure 9B: In step 2A, the vehicular UE receives a request for a resource pool or a resource state. The request may be sent over the NR-PSBCH of the sensing assistant or over the selected If it corresponds to an NR-PSSS / NR-SSSS / NR-PSBCH block, Usually, it is indicated by QCLed NR-PSDCH or broadcast NR-PSSCH. Send with default or reserved sidelink resources for urgent requests A request may be made for group-based sensing assistance, if needed. Sidelink Group ID SL-G-RNTI, Sidelink Group Member ID SL-G-CRNTI, or proximity or range-based sensing assistance, if required. Sidelink ID SL-CRNTI or position zone of the vehicle UE relative to the stance The request may include a new format SCI on the PSCCH, or a new Radio Physical Sidelink Feedback Control Channel (NR-PSFCCH) or selected The selected NR-PSSS / NR-SSSS / NR-PSBCH block is assigned to the or QCLed, or the TCI status or RS indicated to the vehicle UE New format size for NR-PSSCH with index-mapped beams Sidelink Feedback Control Information (SFC I).

[0205] In step 2B, the sensing assistant receives the NR-PSBCH of the sensing assistant, or The selected NR-PSSS / NR-SSSS / NR-PSBCH block is or QCLed or Sensing Assistant Sidelink Group NR-PSDC indicated in the vehicle UE request which may include ID or location zone ID H or the resource pool or resource pool indicated by the broadcast NR-PSSCH The response may be sent based on the resource pool or resource status at the source. If it corresponds to an NR-PSSS / NR-SSSS / NR-PSBCH block, or QCLed, or the TCI status or is indicated by the PSCCH in the beam indicated by the RS index, or Broadcast, multicast, or unicast on the associated NR-PSSCH. It can be struck.

[0206] In step 2C, the vehicular UE may select a resource pool or a resource. That is, the vehicular UE may select a resource pool or or resource pools or resource candidates that use resource states, and group base Select Group ID if location based or Location Zone ID if proximity or range based. and optionally further performing rapid sensing of available resources, e.g. The time line and latency for the data (e.g., one or more transport blocks) The resource reservation statistics may be collected within a sensing window defined by the vehicle requirements. Both UEs use the resource pool or resource candidates and, if available, the sidelink Channel conditions, radio quality, and interference measurements passed to higher layers or applications and / or a higher layer or application may provide resources for use. A pool or resource configuration may be determined.

[0207] For both the first and second option: In step 3, the vehicle UE performs energy detection or reception, if required, for example. Received Signal Strength Indication (RSSI) measurement Check the selected site to see if it is still available by using the The drink resource may further sense the channel, for example sensing channel occupancy.

[0208] In step 4, the vehicle UE transmits the urgent data using repetition or beam sweeping. The vehicle UE may broadcast the selected resource locally to all UEs. , emergency trajectories and cooperative operations. The same or different resources may be Repeated or different receptions to the same receiver, as exemplified in steps 4B and 4C, may be used. The data can be used for beam sweeping for the receiver. The SA SCI carried on the broadcast NR-PSSCH indicates obtain.

[0209] Note that step 3 may be optional.

[0210] (Auxiliary Resource Allocation Scheduler) Sensing-based resource allocation is particularly useful at traffic accident locations, busy intersections, or Many periodic event-triggered data sets with tightly spaced car platoons are not collision-free. To reduce sensing overhead and avoid possible collisions, a resource pool or The resource can be an RSU as a nearby coordinator, a platoon lead, or a nearby This may be reserved by a local scheduler, such as a lead or scheduling UE. The scheduler periodically broadcasts the resource allocation for each vehicular UE. The vehicular UE may obtain or provide resource allocation at the request of the vehicular UE.

[0211] The scheduler may be pre-configured by the manufacturer or service provider, The scheduler may be configured by the gNB / eNB or the V2X server. Optionally, enabled by the gNB / eNB via DCI over the Uu interface and may be disabled or via the Sidelink (PC5) interface Through the SCI, the RSU, group lead, or neighboring coordinator or leader It may be enabled and disabled by commands.

[0212] The scheduler may, for example, send a SL-RRC message on the PSSCH. A resource or resource pool for the UE to select may be statically configured. The user equipment may, for example, provide resources or resources to the UE via the SL-MAC CE. The pool may be semi-statically designated. The scheduler may, for example, deselect SCI enabled or disabled. Through activation, a resource or resource pool for a UE may be semi-persistently assigned. The scheduler may, for example, provide resources or may dynamically allocate the resource pool.

[0213] Lead as scheduler (e.g. RSU as coordinator or neighboring group Examples of local scheduling (e.g. lead in loop, lead in platoon, etc.) are shown below. The steps shown in FIG. 10A and FIG. 10B may include: In step 0, a vehicle UE is assigned to a group (e.g., a platoon led by a platoon leader, a nearby Group discovery and group A connection to the lead and other UEs in the group may be established via a group joining procedure. The vehicle UE also uses SL-G- as a group member ID or label within the group. A CRNTI or a location zone ID for proximity or range may be received.

[0214] In step 1, the lead is organized into a shared or dedicated resource pool or resources. The resource pool is allocated locally from all UEs and RSUs. If you want to collect resource or resource status constantly or frequently and use a shared resource pool, In this case, a resource pool or resources for the group may be reserved.

[0215] In step 2, the higher layer or application layer of the vehicular UE determines whether data is available for transmission. This can be achieved by using periodic or aperiodic, hybrid automatic repeat request (HARQ) frames. The request may indicate that the request may be repeated or retransmitted in the feedback, etc.

[0216] The first option (multicast group-based resource allocation) as shown in Figure 10A In the standby state: In step 3A, the lead determines the time resource pool and the period for each UE in the group. Periodically broadcasts resource allocations to group members, such as a frequency resource pool. The resource allocation is carried on the NR-PSCCH. The new format SA SCI or its NR-PSBCH is indicated or each NR-PSSS / NR-SSSS / NR-PSBCH block Multicast NR-PSSCH or NR-P In the multicast NR-PSSCH indicated by the SA SCI carried in the SCCH Resource allocation can be carried for broadcast, multicast, and unicast. It may be shared or dedicated for different communication types, such as broadcast, and each communication type may have its own Resource allocation may be shared or dedicated among group members for the SC It may be semi-statically enabled and disabled by the I and new format SA SCI The number of occurrences may be dynamically indicated by:

[0217] In step 3B, the vehicular UE may select a resource pool or a resource. That is, the vehicle UE may receive the (For example, the group member ID SL-G-CRNTI for a dedicated resource. or corresponds to a location zone ID for proximity or range-based resources Based on the resource pool or resource that is assigned to the and accordingly, transmits the NR-P The vehicular UE may transmit data carried on the SSCH. For shared resources, the vehicular UE may It performs intelligent sensing and sidelink measurements and communicates selected resources and measurements to higher layers or through the application and / or by a higher layer or application In another example for shared resources, the vehicle UE may load data accordingly. The channel or resources are available to transmit data. Channel occupancy sensing, for example, energy detection or RSSI based, may be performed.

[0218] In the second option (resource state based on request) as shown in Figure 10B, In step 3A, a vehicular UE, e.g., a transmitting or receiving UE, makes a request for resources. A request for a schedule or scheduling may be sent. For emergency or scheduling requests assigned by the Lead as the The request may be sent on default or reserved sidelink resources. New format SCI on NR-PSCCH, or NR-PSFCCH, or The selected NR-PSSS / NR-SSSS / NR-PSBCH block is or QCLed, or the TCI status or R New format S for NR-PSSCH in beams associated with S index May be transported by FCI.

[0219] In step 3B, the lead is assigned by the lead or at the request of the UE. Resource allocation or scheduling on the resource pool or resources shown in the The response may include transmitting a response to the group-based resource allocation for the vehicular UE. A group member ID assigned to this vehicle UE, e.g., SL-G-CRNTI , or a location zone ID for proximity or range based resource allocation. Resource allocation is based on the group member ID or the UE's sidelink ID, e.g. , SL-CRNTI, or location zone-ID, if or by the SA SCI carried on the NR-PSCCH carried on it, or by the NR - Multicast or unicast as indicated by the SA SCI carried on the PSCCH The PSSCH may be indicated by the NR-PSSCH.

[0220] In step 3C, the vehicular UE may select a resource pool or a resource. One or more of these may occur. That is, the vehicle UE may not know whether the resource is a dedicated resource. If so, the assigned or assigned SL-G-CRNTI The vehicular UE may transmit data on the scheduled resources. If so, the resource assigned to it (e.g., associated with SL-G-CRNTI) The UE may select resources based on a pool or resources, and the selected and may pass resource and sidelink measurements to higher layers or applications. and / or the upper layer or application loads the data accordingly Good too.

[0221] For both the first and second option: In step 4A, the vehicular UE may broadcast emergency data. Broadcast emergency trajectories and cooperative operations to all UEs locally on selected resources. All nearby UEs may respond accordingly by sending the The allocated resources, e.g., the broadcast response or the configured In the case of broadcast monitoring, the broadcast message can be received. Different resource allocations may be used for the same receiver, as illustrated in steps 4B and 4C. or for beam sweeping to different receivers. The data is transmitted via the broadcast channel indicated by the SA SCI carried on the NR-PSCCH. The received signal may be carried on the NR-PSSCH.

[0222] For multicast, the UEs in the multicast group perform the steps The allocated resources, which may be indicated by the lead in 3B, e.g., broadcast or multicast responses, or in the case of configured multicast monitoring, The cellular telephone may receive multicast messages.

[0223] For unicast, the request is sent in step 3A as illustrated in FIG. 10B. When sent from the transmitting UE, the receiving UE of the unicast pair performs step The allocated resources, e.g., unicast pairs, may be indicated by leads in 3B. A broadcast, multicast, or unicast response to, or configuration In the case of a unicast monitor, unicast messages may be received, and requests If is sent from the receiving UE in step 3A, the transmitting UE of the unicast pair The allocated resources as shown by the lead in step 3B, e.g., unicast Unicast in response to a broadcast, multicast, or unicast to a pair. The paired receiving UE may transmit a read message to the UE in step 3B. The unicast message may be received on the resource provided.

[0224] (Auxiliary resource allocation Scheduler allocation) The scheduler selects the RSU as the coordinator of the neighborhood, the platoon lead, or the neighborhood or, for example, outside the coverage of the serving node or Manufacturers or service providers (including service providers) may request the use of the equipment when the equipment is covered by the applicable pre-configured by a V2X service provider or network operator) Alternatively, for example, under network coverage, the scheduler allocation may be When under network control, the serving or scheduler-controlled network entity A scheduling UE that can be selected or enabled and disabled by the In this specification, a serving node or a scheduler control entity may, for example, Serving gNB or V2X server (e.g., V2X control server in the core network) or a V2X application server in a V2X service provider network) In addition, the scheduler also checks the neighboring candidate sequences of the scheduled UE. The scheduler may be selected from a group of schedulable entities.

[0225] The scheduler communicates with the RRC, MAC CE, and physical channel through the Uu interface. PDCCH, PDSCH, PUCCH, PUSCH or a new physical channel by gNBs via broadcast channels, or a combination thereof, The SL-RRC and SL-MAC C are connected via the sidelink (PC5) interface. E, Sidelink physical channels (e.g., NR-PSCCH, NR-PSFCH, NR- PSSCH, etc.), or a combination of them, by the RSU or UE. The scheduler can also receive or modify the R By the gNB via RC, MAC CE, or DCI, or by the sidelink (P C5) via the interface, SL-RRC, SL-MAC CE, or SCI Servings can be enabled and disabled or modified by the RSU or UE via Communication between the scheduler and candidate schedulers, or between the scheduler and other UEs The communication is performed via the sidelink (PC5) interface, and is CE, sidelink physical channel (e.g., NR-PSCCH, NR-PSFCH, N R-PSSCH, etc.), or a combination thereof.

[0226] FIG. 17 illustrates a UE initiated network control scheme, which is illustrated in the following steps: An example of scheduler selection is shown below.

[0227] In step 1, you request to become a scheduler, i.e. Determines the UE's context and capabilities, location or location zone, resource plan, service and QoS requirements, as well as sidelink measurements such as interference, congestion, and link quality Send a request to become a scheduler to a gNB or V2X server, including Wait for the answer.

[0228] In step 2, check the response. If no, go to step 5, if not, Continue to step 3.

[0229] Step 3 checks whether it is a rejection in response. If not, step If yes, go to step 6, if not, go to step 4.

[0230] In step 4, adjust the capabilities, resource pool requirements, etc. for each rejection reason.

[0231] In step 5, a timeout t OutSchReq Yes or no If no, go to step 1, if yes, go to step 7 to finish Do the following.

[0232] In step 6, if it is a synchronization source UE, it transmits its NR-PSBCH and its NR-P Schedule carried periodically on the SDCH or on its broadcast NR-PSSCH Start broadcasting your messaging.

[0233] In step 7, the scheduler selection is completed.

[0234] In an alternative example, the network (e.g., a gNB, a V2X server, or a scheduler) Selection Controller) Initiate scheduler selection is illustrated in Figure 18, which is shown in the following steps: As shown.

[0235] In step 1, scheduler candidates are collected, i.e., procedures such as registration, attachment, etc. update a scheduler candidate list having UEs that want to be schedulers during the period, and Based on the capability indication, update the capability list of the scheduler candidates and Update the candidate's location or location zone, as measured and reported by the scheduler candidate , sidelink channel occupancy, radio link quality, interference, etc. are collected.

[0236] Step 2 checks if a scheduler is needed. If not, step If yes, go to step 1, if not, go to step 3.

[0237] In step 3, a scheduler is selected, i.e., the UE capabilities, location, and resource pool are considered. Select a scheduler from the candidate list based on the traffic requirements, QoS requirements, sidelink measurements, etc. A scheduler is selected, a request is sent to the selected scheduler, and a response is awaited.

[0238] Step 4 checks if any response is received. If no, go to step 7. If not, go to step 5.

[0239] In step 5, check if there is a rejection in the response. If yes, go to step 3. Go ahead and select another scheduler, otherwise go to step 6.

[0240] In step 6, the RRC or MAC CE, or or enable the scheduler indicated in the Downlink Control Information (DCI).

[0241] In step 7, the timeout t OutSchReq Yes or no If yes, go to step 3 to select another scheduler, if no, If so, go to step 4 for response.

[0242] An alternative example to network-controlled scheduler selection is An example of scheduler selection is shown in Figures 19A and 19B, which illustrates the following steps: will be done.

[0243] In step 1, the scheduler selects NR-PSBCH, NR-PSDCH, or broadband For scheduling indications that may be indicated by the cast NR-PSSCH, Cancel.

[0244] Step 2 checks whether any scheduler is detected. If not, Go to step 4, if not, go to step 3.

[0245] In step 3, if a scheduler is found, its ID, resource pool, location or Extracts scheduler information such as placement zones and QoS requirements, and updates the scheduler list. do.

[0246] In step 4, a timeout t OutScanSch mosquito If yes, go to step 5; if no, go to step 1. Continue scanning for schedulers.

[0247] Step 5 checks if the scheduler list is empty. If yes, check the nearby schedules. If there is no scheduler, the process proceeds to step 6B and sends a request to the first nearby scheduler. If no, go to step 6A and send the request to another nearby scheduler. To strike.

[0248] In step 6A / 6B, the higher layer requests to become the scheduler, i.e. Or it decides to become the scheduler as indicated by the application layer and It can be used with common or default resources or resources for broadcasting in close proximity. Create a new schedule with power, resource pool configuration, QoS requirements, and location or location zones. The request is broadcast as a scheduler on the NR-PSCCH. The special format SCI to be carried, or NR-PSFCCH or broadcast It can be a special format SFCI carried on the NR-PSSCH. The default or broadcast resource, or the resource indicated in the request The device waits for a response.

[0249] In step 7A / 7B, check if there is any response. If yes, confirm rejection. If no, go to step 9A / 9B to check for timeout. Proceed to step 8A / 8B.

[0250] In step 8A / 8B, based on the upper layer parameters, a timeout t OutSchR eq If no, go to step 6A / 6B to check whether the scheduler If 8A is yes, go to step 15A and exit, and if 8B is If yes, proceed to 13B to check the UE list.

[0251] In step 9A / 9B, it is checked whether there is a rejection in the response. If yes, the UE Go to step 12A / 12B to update the context of Continue to step 10A / 10B.

[0252] In step 10A / 10B, one or more schedules in the scheduler / UE list are A scheduler / UE, e.g., a scheduler or UE that is in close proximity or within communication range is Check if the call was answered. If yes, proceed to step 14.

[0253] In step 11A / 11B, update the UE list and schedule for step 11A. Based on the response, update the UE list, e.g., the neighbor list, to step 11B. or update the scheduler or UEs in range. Then, timeout Proceed to step 8A / 8B to confirm.

[0254] In step 12A / 12B, based on the response, the UE list and schedule are generated for 12A. update the UE list for step 12B, update the UE list for step 12C, and Adjust the capacity of the network, resource pool configuration requirements, QoS requirements, etc. Then, adjust the timeout Go to step 8A / 8B to confirm.

[0255] Step 13B checks whether the UE list is empty. If yes, and there is no other UE, Go to step 14 and become the first UE there as scheduler; if no, Proceed to step 15B to finish.

[0256] In step 14, the scheduler determines the NR-PSBCH, NR-PSDCH, or or broadcast NR-PSSCH periodically broadcasts the scheduling alignment. Start broadcasting.

[0257] The call flow for scheduler selection without network control may include the following steps: This is illustrated in Figures 20A and 20B.

[0258] In step 0, configuration, i.e., scheduler UE, other UEs, and other schedulers, The controller can use the common resource pool, the default resource pool, and the broadcast resource pool. Configuration may be performed by the manufacturer or a service provider. The configuration also includes gNB and LTE networks under network coverage and network management. or by a V2X server.

[0259] In step 1, a candidate UE decides to become a scheduler, i.e., The upper layer or application layer of the possible.

[0260] In step 2, all That is, the candidate scheduler UEs can be sidelink common, default, or broadcast. The request is sent on the resources of the UE. The request is based on the UE's capabilities, location or location zone. network, resource pool requirements, and QoS requirements, as well as interference, congestion, link quality, etc. The request may include sidelink measurements. Format SCI, or NR-PSFCCH or broadcast NR-PSSC H.

[0261] In step 3, it responds to the request to become a scheduler, i.e., Other schedulers and / or other UEs may use the sidelink common, default, or Sends a response on the resource indicated in the request or on the resource of the broadcast. The response is sent in the new format SCI carried on the NR-PSCCH or in the NR- New formats carried on PSFCCH or broadcast NR-PSSCH The candidate scheduler UE decodes the responses and forwards them to its higher The layer may be passed through.

[0262] In step 4, any rejection is confirmed, i.e., the upper layer of the candidate scheduler UE: Any rejections conveyed in responses from other schedulers or UEs, and if available , the reason for the rejection may be checked, and then the scheduler UE's capabilities and context Adjust the requirements for resource pool allocation, adjust the QoS requirements, etc.

[0263] In step 5, all That is, the candidate scheduler UEs can be sidelink common, default, or broadcast. The request is sent again with the updated UE context and other information for the resource in the host. The request may include the adjusted parameters from step 4.

[0264] In step 6, it responds to the request to become a scheduler, i.e., Other schedulers and / or other UEs may use the sidelink common, default, or Sends a response on the resource indicated in the request or on the resource of the broadcast. The candidate scheduler UE may decode the responses and pass them on to its higher layers.

[0265] Step 7 becomes the scheduler, i.e., checks that there is no rejection in the response. Then it becomes the scheduler.

[0266] In step 8, we broadcast the "scheduling indication", i.e. The new scheduler UE receives its NR-PSBCH, NR-PSDCH, or broadcast Broadcast the schedule information periodically on the PSSCH. The scheduling indices in NR-PSBCH determine whether the UE is the scheduler or not. It can be a 1-bit indication to flag the NR-PSDCH or The scheduling alignment in NR-PSSCH is a discovery or association process. The scheduler in the NR-PSCCH or NR-PSSCH may be used during Notification is used by UEs that have already established a relationship with the scheduler UE to The scheduler UE's context (e.g., it is a new scheduler), and Other information, such as the resource pool configuration managed by the new scheduler, may be updated. .

[0267] In step 9, the new scheduler is associated, i.e., with other UEs and / or The scheduler is responsible for determining whether a relationship has already been established via message exchange carried on the NR-PSSCH. If so, update the new scheduler UE context or For the association process, the NR-PSDCH or NR-PSSCH is used. If a relationship has not yet been established through message exchange, the new scheduler group The scheduler is then placed into a group or pair, or associated with a new scheduler.

[0268] An example of scheduler modification with network control is shown in FIG. 21, which may include the following steps: This is illustrated in the call flow shown.

[0269] In step 0, the network is connected, i.e., scheduler 1 and scheduler The second scheduler is registered as a scheduler candidate and is given shared or dedicated resources to the scheduler. Scheduler 1 is the serving scheduler and is responsible for scheduling. Scheduler 2 is a candidate scheduler.

[0270] In step 1, the decision is made to relinquish the scheduler role, i.e., Scheduler 1 The upper layer or application layer indicates that it wishes to relinquish the scheduler role.

[0271] In step 2, a request to quit is made, i.e., scheduler 1 quits the schedule. Send a request to the gNB or V2X server to cease being a controller. Request When transmitted to the gNB on the NR Uu interface, the new format physical address Physical Uplink Control Channel (PUCCH) or Physical Uplink Shared Channel (PUSC H).

[0272] In step 3, the next scheduler is found, i.e., the gNB or V2X server. UE capabilities and status, such as location or location zone, and the candidate scheduler The sidelink measurements reported by the scheduler determine the scheduler candidate list and which candidate is the next scheduler. Determines whether a scheduler is requested.

[0273] In step 4, it requests the next scheduler, i.e., gNB or V2X support. The server will use the new format when transmitted from the gNB on the NR Uu interface. Physical Downlink Control Channel (PDCCH) or Physical Downlink Shared Channel (P The request is sent to a candidate scheduler that can be carried on the DSCH, e.g., scheduler 2. Believe.

[0274] In step 5, the request to the next scheduler is responded to, i.e., the candidate scheduler is A scheduler, e.g. scheduler 2, can send a new format PUCCH or PUSCH In case of refusal, the gNB may respond to the request with acceptance or rejection information that may be carried in the Or the V2X server reselects the candidate scheduler and selects the newly selected candidate scheduler. The request may be sent to the

[0275] In step 6, the scheduler modification is notified, i.e., the gNB notifies the RRC, M Sends an AC CE or DCI to the new scheduler (e.g., scheduler 2), Disable RRC, MAC CE, or DCI from the old scheduler (e.g., scheduler 1) and transmits the PDCCH, PDSCH, a new physical broadcast channel, or Broadcast scheduler modifications to all UEs via these combinations The V2X server sends a confirmation message to scheduler 1 and scheduler 2. Each UE may then transmit a corresponding UE notification to notify all UEs of the scheduler modification.

[0276] In step 7, the old scheduler is disassociated, i.e. the UE is deassociated with the side You can disable the old scheduler by sending notifications to it with a link, e.g. 1 and then reassociates it with the old scheduler after an acknowledgement is received from the old scheduler. The context of the object may be removed.

[0277] In step 8, the UE is associated with the new scheduler, i.e., the UE is paired with or by sending an association request to the new UE, For example, associate with scheduler 2, then receive from the new scheduler's response The new scheduler context may be saved.

[0278] Mapping and unmapping requests and notifications via the Sidelink interface The response message has a new format NR-PSCCH with SCI, SFCI or an NR-PSFCH with multiplexed SCI or SFCI. It may be carried on the PSSCH or a special mapped NR-PSSCH at higher layers. do.

[0279] An example of a scheduler replacement without network control is shown in FIG. Illustrated.

[0280] In step 1, the decision to quit is made, i.e., the upper layer or application layer , indicates that the scheduler role is to be relinquished. The request is broadcast on the NR-PSCCH. New format SCI, or NR-PSFCCH or broadcast NR -Can be carried in a new format SFCI on PSSCH. Common or default Wait for a response on the resource or indicated in the request.

[0281] Step 2 checks if there is any response. If yes, If yes, go to step 4, if no, go to step 3 to check for timeout .

[0282] In step 3, a timeout t OutQtReq or not If yes, go to step 5 and finish, if no, go to step 1 Resend the request with

[0283] In step 4, the current scheduler is handed over to the new scheduler. The controller manages the scheduler context, other associated UE contexts, and resources. The spool configuration may be passed to the new scheduler.

[0284] Step 5 ends, i.e., if no candidate scheduler responds, no Hard stop with no text exchange.

[0285] The call flow for scheduler replacement without network control may include the following steps: This is illustrated in FIG.

[0286] In step 0, the preconditions, i.e., scheduler 1 and scheduler 2, are shared or Scheduler 1 is configured as a scheduler candidate in a dedicated resource pool. Scheduler 1 is the serving scheduler and Scheduler 2 is the candidate scheduler.

[0287] In step 1, the decision is made to relinquish the scheduler role, i.e., to terminate the current scheduler. The upper layer of a scheduler, for example scheduler 1, indicates that it is relinquishing its scheduler role.

[0288] In step 2, a request is broadcast to candidate schedulers, i.e. The current scheduler, for example scheduler 1, uses the common or default resources. A request may be broadcast to candidate schedulers at NR -New format SCI on PSCCH or new frame on NR-PSFCCH Format SFCI, or PSSCH or broadcast NR-PSSCH May be transported in aggravated SCI or SFCI.

[0289] In step 3, the candidate scheduler is selected. For example, scheduler 2 may decode the request and pass it on to the upper layers. A tier may decide to become the next scheduler.

[0290] In step 4, the response to the request is broadcast, i.e., the schedule is A candidate scheduler, for example, scheduler 2, serves requests on common or default resources. The response is broadcast in a new format on the NR-PSCCH. SCI, or a new It may be carried in the same format as the SFCI.

[0291] In step 5, the response is checked, i.e., the candidate scheduler, e.g., scheduler 2 is determined from the current scheduler, from other UEs, and / or from other schedulers. The confirmation can be received in the new format SCI on the NR-PSCCH or in the NR - It can be carried in the new format SFCI on PSFCCH or NR-PSSCH. do.

[0292] In step 6, the context is passed, i.e., the current scheduler, e.g. Controller 1 provides the context, resource pool configuration, etc. to the candidate scheduler via the side link. The NR-PSSCH is then passed through a BER channel, which may be carried on the NR-PSSCH.

[0293] In step 7, the old scheduler is disassociated, i.e. the UE is deassociated with the side You can disable the old scheduler by sending notifications to it with a link, e.g. 1 and then reassociates it with the old scheduler after an acknowledgement is received from the old scheduler. The context of the object may be removed.

[0294] In step 8, the UE is associated with the new scheduler, i.e., the UE is paired with By sending a request to the new UE, a new scheduler, e.g. Then, the new scheduler is assigned to the new scheduler 2, and the new scheduler is assigned to the new scheduler 3. This can save context for the user.

[0295] (Resource allocation mode switching) Resource allocation can be fully managed by different operating modes, e.g. gNB or eNB. Controlled sidelink resource allocation (e.g., Mode 1), sidelink sensing and Sidelink resource allocation based on the BER and resource selection (e.g., Mode 2(a)), Sidelink resource allocation based on pre-configuration or configuration from the NB or eNB (e.g. For example, in mode 2(c), the scheduler, e.g., the scheduling UE, manages the Sidelink resource allocation (e.g., in Mode 2(d)) can be performed in combination with The mode or modes are configured and enabled for a vehicular UE to communicate on the sidelink. The UE may also choose to switch from one mode to another or or may be ordered to do so.

[0296] The resource allocation mode is via the Uu interface, RRC, MAC CE, Physical channel (e.g. PDCCH, PDSCH, PUCCH, PUSCH, etc.), if by gNB or via a combination of them, or via sidelink (PC5) inter- Through the interface, SL-RRC, SL-MAC CE, sidelink physical channel ( For example, NR-PSCCH, NR-PSFCH, NR-PSSCH, etc.), or configured or indicated by the RSU or UE via a combination of The resource allocation mode can also be modified by the RRC over the Uu interface. , by the gNB via MAC CE or DCI, or by the sidelink (PC5 ) interface via SL-RRC, SL-MAC CE, or SCI It can be enabled and disabled by the RSU or the UE.

[0297] The resource allocation mode is also NR-PSBCH, NR-PSDCH, NR-PSC At the physical layer, such as NR-PSFCH, NR-PSSCH, or a combination of these may be indicated by other signals or channels.

[0298] With network control, e.g., sensing-based (e.g., mode 2(a)) and scheduled Switching between resource allocation modes (e.g., mode 2(d)) and ring-based An example is illustrated in FIG. 24A and FIG. 24B, which may include the following steps.

[0299] In step 0, the UE connects to the network, i.e., the UE and the scheduler connect to the network. The scheduler is connected to a network and consists of a shared or dedicated resource pool. It is a candidate scheduler.

[0300] In step 1, V2X communication in sidelink is performed, i.e., the UE transmits the configured shared or The UE communicates with other UEs on the sidelink using a dedicated sidelink resource pool. For a given resource pool, the UE must sense and determine the resource allocation. or the UE may need to use more available resources for more dynamic resource allocation. It may be necessary to sense the channel via a resource that is available.

[0301] In step 2, the scheduler is Or it can be enabled by the gNB as a new scheduler with a dedicated resource pool.

[0302] UE initiated scheduler discovery for option 1: In step 3A, a "schedule indication" is broadcast, i.e. The scheduler then uses the NR-PSBCH / NR-PSDCH / NR-PSSCH to The scheduling information may be broadcast periodically.

[0303] In step 4A, the vehicle UE discovers a scheduler, i.e., the vehicle UE discovers a scheduler. The higher layer can then decode the signal and pass it to the higher layer. Decides to do so.

[0304] gNB initiated discovery for option 2: In step 3B, the scheduler is indicated, i.e., the gNB (e.g., the PDSCH is also or new broadcast channels), or new groupcast channels), or (e.g., P Scheduler indication to the UE via unicast message (on DSCH) The scheduler sends the request to the Scheduler, and the resource allocation mode is managed by the scheduler. The gNB may instruct the UE to switch to the RRC, MAC CE, or DC An indication may be sent by I-enable to enable the scheduler to the UE. or enable a new resource allocation mode for the UE, and Enable the source pool.

[0305] For both Option 1 and Option 2: In step 5, the vehicle UE requests the scheduler to associate with the is requested on NR-PSCCH, or NR-PSFCH or NR-PSSCH to the scheduler to join the scheduler's group or to pair with the scheduler. It can be a.

[0306] In step 6, the scheduler responds to the association request, i.e., the scheduler The correspondence may be carried on the SCCH, NR-PSFCH, or NR-PSSCH. The UE may respond to a request for establishment.

[0307] For option 1, the UE is configured or semi-persistently scheduled by the scheduler. Select the pooled resource.

[0308] In step 7A, V2X communication in the sidelink, i.e., the UE is scheduled by the scheduler. configured or semi-statically assigned (e.g., enabled SL-RRC, SL-MAC A shared or dedicated sidelink resource pool (indicated by CE, or SCI) A UE may communicate with other UEs on the sidelink by selecting resources.

[0309] For option 2, the scheduler dynamically allocates resources (e.g., dynamically scheduling).

[0310] In step 7B, a request for resource allocation or scheduling, i.e. The UE sends a request to the scheduler for resources to allow other It may transmit to the UE or receive from other UEs.

[0311] In step 8B, resources are granted or scheduled, i.e., The UE is the transmitting UE or the transmitting UE is the receiving UE, as indicated by the SA SCI carried on the NR-PSCCH. Resources may be granted or scheduled to both the transmitting and receiving UEs.

[0312] In step 9B, V2X communication in sidelink, i.e., the UE transmits the V2X signal via the SA SCI. and use sidelink resources dynamically allocated by the scheduler to Communicate with E.

[0313] An example of a resource management mode switch without network control may include the following steps: This is illustrated in Figures 25A and 25B.

[0314] In step 0, pre-configuration or configuration, i.e., UE and scheduler or scheduler Scheduler candidates consist of shared or dedicated resource pools. Scheduler 1 is a Bing scheduler, and scheduler 2 is a candidate scheduler.

[0315] In step 1, V2X communication in the sidelink, i.e., the vehicle UE, The sidelink is used to communicate with other users using resources allocated semi-statically or dynamically by the Communicate with E.

[0316] In step 2, the UE disassociates with the scheduler, i.e., the UE 1, which indicates that the higher layer (e.g., leaving the vicinity of scheduler 1) or can be triggered by a timer (e.g., beam failure timer or out of sync timer) The UE can then: The system may then switch to a non-scheduler managed resource allocation mode.

[0317] For option 1, choose resources based on perception: In step 3A, the UE senses the reserved or used resources. (For example, the S transmitted from other UEs in the vicinity of the reserved or used resource. A SCI), and / or measuring sidelink channel occupancy and quality The resource may be selected based on a configuration, etc.

[0318] In step 4A, V2X communication in sidelink, i.e., the vehicle UE communicates with itself The UE communicates with other UEs on the sidelink using resources selected by the UE.

[0319] For option 2, select the resources based on your configuration: In step 3B (optional), collision avoidance channel sensing, i.e., optionally Then, for the configured shared resources, the UE may, for example, listen on the configured resources. Channel sensing such as talk-before-talk may be used to perform channel sensing.

[0320] In step 4B, V2X communication in sidelink, i.e., the UE detects that channel sensing is stable. If used in step 3B, the configured resources are not occupied. Communicate with other UEs using drinks.

[0321] For both options: In step 5, the scheduler, i.e., scheduler 2, detects new It becomes a faster scheduler.

[0322] In step 6, we broadcast the "scheduling indication", i.e. Scheduler 2 then circulates the NR-PSBCH / NR-PSDCH / NR-PSSCH. The scheduling information may be broadcast periodically.

[0323] In step 7, the UE associates with the discovered scheduler, i.e., Scheduler 2 and maps it accordingly.

[0324] In step 8, the V2X communication in the sidelink, i.e., the vehicle UE, The scheduler switches between modes, and uses resources allocated semi-statically or dynamically by scheduler 2. The UE communicates with other UEs on the sidelink by using the same base station.

[0325] Request and response messages for different purposes as described herein are New format PSCCH with SCI, NR-PSFCH with SFCI, NR-PSSCH with multiplexed SCI or SFCI, or spatial The PSSCH may be carried on the NR-PSSCH mapped to the PSSCH.

[0326] (Example of resource allocation) NR supports different numbers of slots within a subframe, e.g., 15KHz subcarrier spacing. One slot per subframe for each channel, and 30KHz subcarrier spacing Many different numerologies that can contain two slots per subframe for To simplify the illustration, slots are used in the examples. The slot structure shown may also be applicable to a subframe.

[0327] Resource allocation or allocation in sidelink with different slot and minislot structures For scheduling, some examples are shown in Figs. 11, 12, 13, and 14. Examples of slot-based resource allocation or scheduling are shown in Figs. 11 and 12. , and shown in FIG. 13. Here, the scheduling assignment in NR-PSCCH ( The SA)SCI does not necessarily correspond to the associated NR-PSSCH that carries data in time. The NR-PSCCH and NR-PSSCH are not adjacent and are fully are the same or different depending on whether they are partially quasi-collocated (QCLed) or not. can be on different beams. Minislot-based resource allocation or scheduling An example of a ring is shown in Figure 14, where the scheduling assignment in NR-PSCCH is The SA SCI is adjacent to the associated NR-PSSCH that carries data at time. However, it may be more efficient if the sidelink is carried in the same beam.

[0328] FIG. 11 shows different BWPs of sidelink operating bands using different numerologies. For example, the allocated or scheduled in BWP1 and BWP2 Illustrates broadcast, multicast, and unicast resources. For example: With bandwidth from RB / RBG / subchannel k2 to RB / RBG / subchannel N The BWP1 has a sub-carrier space (SCS) of 15KHz. Then, the bandwidth from RB / RBG / subchannel 0 to RB / RBG / subchannel k1 is The BWP2 has a 30KHz SCS.

[0329] As shown in FIG. 11, different slot structures are used depending on the data transmitted, the time line, and It may be formed based on feedback from the receiving vehicle UE.

[0330] For example, slot "SL1_1" of BWP1 is optionally configured to control the automatic gain of the receiver. Automatic Gain Control (AGC) settings (e.g., dummy data Sequence base (using randomly generated or user-generated data) For the receiver automatic gain control (AGC), which can be a base or modulation database design. The first step (depending on numerology, e.g., symbol length, and AGC decision time requirements) and an associated NR-PSSCH (e.g., NR-P NR-PS SSCH1 and NR-PSSCH2) to indicate the resource location CCH and its SideLink Demodulation Reference Signal nal:SL-DMRS) SA SCI (e.g., short Broadcast over SCI1 and NR-PSSCH2 for low latency unicast Two synthases, as examples herein, are used as control regions for SCI2 (for the strike). The sidelink demodulation reference signal (SL-DMRS) for NR-PSSCH, Sidelink Channel State Information for Drink Channel State Information (SL-CSI) Reporting Side link for tracking reference signals (SL-CSI-RS), frequency and / or phase SideLink Phase-tracking Reference Signal (SL-PTR S), SideLink Positioning Reference Signal for Positioning Measurement For data and / or reference signal (RS) transmission such as SL-PRS Some symbols and, for example, a vehicle UE switching from receiving to transmitting or vice versa. The gap in this specification (numerology, e.g., symbol length, and Depending on the switching time of both UEs) and optionally feedback is received. Some symbols at the end if needed for the sidelink from the vehicular UE, e.g. , for short latency unicast carried on NR-PSSCH1 (to simplify the example) In order to achieve this, the AGC signal is fed to the feedback SCI "SCI_FB1" (not shown). and one symbol for HARQ ACK / NACK feedback. This slot structure as a vertical type can be used, for example, for one transmitting vehicle UE and one or several receiving The SA SCI and the data N have data or signal exchange in both directions between the vehicle UE and the For R-PSSCH, the resource mapping is done by first mapping the frequency, e.g., Then, the frequency dimension of the first channel is filled with resource elements (REs), and the second channel is filled with resource elements (REs). 2 symbols along the frequency dimension with RE. For example, CI1 is filled with the first symbol of the control area, and SA SCI2 is filled with the second symbol of the control area. Similarly, NR-PSSCH1 and NR-PSSCH2 are first filled with Mapped in frequency. 1-bit HARQ ACK / N carried on SCI_FB1 The ACK may be of a sequence-based design.

[0331] For example, slot "SL2_1" of BWP2 is the (e.g., larger) SCS or narrower symbols, having two symbols as an example in this specification) 1 and the SA carried on the NR-PSCCH and its SL-DMRS. SCI (e.g., SCI3 for multicast on NR-PSSCH3, and the next SCI4 for broadcast on NR-PSSCH4 in slot "SL2_2" ) as an example of a control region, and SL-DMRS, SL-C Data and / or reference signals (RSs) such as SI-RS, SL-PTRS, and SL-PRS ) transmission, for example, a data transmission area. CI4 indicates inter-slot resource allocation or scheduling, so there is no gap and feedback symbols may not be required here. Reciprocal slot allocation or scheduled block on NR-PSSCH4 from UE The slot "SL2_2" carrying broadcast transmission is NR-PSSCH4. It may start with some symbols, then the symbols for the gap and the previous Vehicle UE receiving multicast message on PSSCH3 in slot "SL2_1" Three exemplary methods are described herein for HARQ feedback from all or some It may start with the symbol

[0332] Multiple bits of HARQ ACK / NACK from all or some of the receiving vehicular UEs UE-specific sequence-based, which may be multiplexed over the same or different symbols The design may be a time-first mapping or a modulation symbol based design, respectively. Depending on the frequency-first mapping, the RBs are divided into groups of different symbols in time or in frequency. For example, multiple HAs from a receiving UE are mapped to a group of RBs via a loop. The RQ feedback may first be mapped in frequency, e.g., UE1 and UE2 feedback in the first symbol to UE3 and UE4 feedback at the second symbol for the time The first mapping may be, for example, a first symbol in time in a first RBG or a first RB. and then filled with the second symbol at time in the second RBG or second RB. The time first mapping is SA SCI3 and SCI4, and Illustrated herein for PSSCH3 and PSSCH4.

[0333] To maintain orthogonality, all HARQ ACK / NACKs sent to the transmitting UE are The UE needs to be synchronized with the receiver of the transmitting UE, e.g., to account for the propagation delay of the signal over the air. Properly adjust the resulting Timing Advance (TA) This is a typical case for the many-to-one feedback design of multicast. Multicast is a receiver-aware communication, so for example, the communication Group membership is performed within a group, and UEs use the group to discover nearby groups and become members of those groups. A procedure must be performed to enter the loop. The timing advance information is stored in the loop. For proximity group-based multicasting, Therefore, the signal propagation delay does not vary significantly between group members within a very small area. All group members may be largely synchronized with a common synchronization source, Therefore, TA can be adequately handled within small groups.

[0334] As shown in Figure 11, there are unicast, multicast, and broadcast The different communications are assigned or scheduled in the corresponding SA SCI in the control region. can be.

[0335] The SA SCI is the source ID for the broadcast, e.g. The SA may carry an SL-BA-RNTI for the UE and an SL-BT-RNTI for the transmitter. SCI is the group ID for multicast, e.g. Carries the LM-RNTI, SL-G-RNTI for the group or group lead. The SA SCI is the UE Sidelink ID or Pair ID for unicast, e.g. For example, SL-C-RNTI-1 for the first UE, SL-C-RNTI-2 for the second UE, The SL-C-RNTI-p for the pair may be carried by the SL-C-RNTI-2. E can detect and decode the desired SA SCI for the transmitted data.

[0336] As an example, a 2-bit communication type indication, e.g., com_type, is For example, "00" for broadcast, "00" for multicast, For example, the 1-bit The bit flag, e.g., periodicity, is used to indicate whether the SA SCI (e.g., aperiodic or event-triggered) "0" for continuous and "1" for periodic), and optionally, " A field for the period that indicates the duration of the data traffic, e.g. may be included in

[0337] SL-DMRS of NR-PSCCH carrying SA SCI or NR-PSCCH carrying data The SL-DMRS in the R-PSSCH also supports source ID for broadcast, multi- The source ID or group ID for cast and the UE's subgroup ID for unicast The sidelink ID or paired sidelink ID may be included in the UE's desired N The UE may use the R-PSCCH or the desired NR-PSSCH to identify the R-PSCCH or the desired NR-PSSCH. SL-DMRS on NR-PSCCH for synchronization and / or group or peer discovery The selected NR-PSSS / NR-SSSS / NR-PSBCH during the procedure, and is pseudo-collocation ( It may be assumed that the QCL or transmission configuration indicator for NR-PSSCH is A TCI may be indicated by its associated NR-PSCCH.

[0338] For example, the SL-DMRS for NR PSCCH or NR-PSSCH has an ID of It can be constructed by Gold sequences as follows:

[0339]

number

[0340]

number

[0341]

number

[0342]

number

[0343]

number

[0344]

number

[0345] The SL-DMRS port of the NR-PSCCH is controlled by the network. The network control may be configured by the gNB or the RSU such as a gNB via the If not, group discovery and group joining or peer discovery will be performed via SL-RRC. and during the pairing or association or connection procedure, RSU as a coordinator, neighboring lead, group lead, synchronization source UE , or may be configured by the scheduling UE.

[0346] The SL-DMRS port of the NR-PSSCH can be connected to the gNB when network controlled. or gNB, and may be signaled in the DCI by the RSU. If you do not specify this, the group discovery and group joining or peer discovery and pairing procedures will During the migration, the RSU as the proximate coordinator, the proximate lead, the group leader may be configured or signalled by the SCI by the UE or by the synchronization source UE. .

[0347] As an example shown in Figure 11, the control field and data field for SA SCI in PDSCH are and / or data transmission domain for RS. Different resource pools are and data transmission areas (e.g., one for control or multiple resource pools, and one or more resource pools for data).

[0348] FIG. 12 shows the aggregated slot scheduling in the sidelink. As an example, broadcast transmission in PSSCH is performed in slots SL1 and SL 2, e.g., the data transmission region spans the slot boundary.

[0349] Figure 13 shows an example of SL-CSI-RS acquisition, which is performed by the gNB via RRC. The RSU may be configured as a lead or a scheduler via SL-RRC. It may be configured by the UE and may also be indicated by the SA SCI in slot SL1. The SA SC in slot SL1 is swept by multi-beam (spatial multiplexing)-based sweeping. I, e.g., an SL-CSI-RS request indication in the SA SCI, and SL-CSI feedback (e.g., sidelink CSI report) in slot SL2 The SL-CSI-RS may be dynamically indicated by the transmitting UE via The multicast transmission is performed in the control area of ​​slot SL1 as an example for the multicast area coverage. However, narrow multi-beam sweeping can also be demonstrated by the SA SCI in the region. , can be applied to the SL-CSI-RS in the data domain shown in FIG. 13.

[0350] One-to-many SL-CSI-RS (similar to multicast data in NR-PSSCH) Narrow multiple beam sweeping for transmission is one example for multicast coverage. In addition, all U The CSI feedback in slot SL2 from E or some UEs is different in time. Multiplexing in symbols (e.g., TDMed), different RBs / RBGs / subchannels in frequency Multiplexing in the channel (e.g., FDMed) and / or multiplexing in different beams in space For example, at feedback position CSIFB1, beam A as shown in FIG. Space multiplexing or space division multiplexing (SDM) in beams B and C The example shown in FIG. 13 is a modulation-based feedback loop. For the SL-CSI report carried on the back channel, there are 4 × 2 × 3 = 24 SL-CSI frames. For example, the feedback SCI has a new physical side link. Either the NR-PSSCH is carried on the feedback channel or multiplexed on the NR-PSSCH, Alternatively, it is carried on NR-PSSCH specially mapped by higher layers.

[0351] UE-specific sequence-based spreading (either in the time domain, frequency domain, or When applied to the CSI feedback resource (either on the The signals may be multiplexed over different codes, e.g., in time or frequency. Code Division Multiplexed (CD) at the cost of more resources Med) may be used.

[0352] SL-CSI feedback is used to report sidelink radio channel conditions Therefore, the quasi-collocation (QCLed) type A relationship, e.g., Doppler shift The delay spread, Doppler spread, average delay, and delay spread are measured by beam pair. Reporting the channel conditions that are shared among groups in a small area can be redundant. UEs in the group may have a QCL type-A relationship with a QCL type-A beam. In this case, only one UE in the QCL type-A UE subgroup can report SL-CSI. and further reduce the overhead of many-to-one CSI feedback. It is necessary.

[0353] The proposed mechanism for multicast CSI feedback also Multicast HARQ ACK / NACK implementation, either space-based or modulation-based is applicable to.

[0354] Figure 14 shows minislot-based scheduling. Here, the SA carries the SCI. The NR-PSCCH that transmits the NR-PSSCH is adjacent to the NR-PSSCH that carries the data in time. Therefore, NR-PSCCH and NR-PSSCH are SL-DMRS, SL-C Used for data and / or RS such as SI-RS, SL-TPRS, SL-PRS In addition, it shares the same resource pool used for narrow beam-based sweeping. Thus, the PSCCH and the PSSCH may be carried on the same beam.

[0355] As shown in Figure 14, SA SCI1 is a 2-symbol minislot repeated once and The low latency and high latency signals carried on the NR-PSSCH1 over a period of one slot Demonstrating reliable periodic data transmission, SA SCI2 transmits 6 symbols per slot. Medium size low latency periodic data carried on NR-PSSCH2 via slots and SA SCI3 is carried on NR-PSSCH3 via a 6-symbol minislot. Indicates medium size low latency event trigger data to be sent, and SCI4 is an i-throttle NR-PSSCH4 is transmitted via a 2-symbol minislot for a period of i>1. 3 illustrates the very small periodic data transmissions that are carried.

[0356] For periodic transmissions, especially for frequent periodic transmissions, the receiver must properly set the AGC settings. and does not require an AGC signal for the preconditions of the receiver AGC circuit setting. This is also fine.

[0357] For event trigger transmission, the AGC signal is a prerequisite for the receiver AGC circuit settings. may be required.

[0358] An example of resource allocation or scheduling for unicast is shown in FIG. Unicast is performed by the receiving UE using the SASCI as shown in Figure 15A. The UE may initiate the packet transfer by itself or by the transmitting UE as shown in FIG. 15B.

[0359] As shown in FIG. 15A, the receiving UE requests or reserves data transmission, or The unicast may be initiated by sending an SA SCI to elicit the data.

[0360] BWP1 optionally includes an AGC signal (e.g., AGC r) from the receiving UE A data request or reserved SA SCI (e.g., SCI1 r) is the first slot (e.g., SL1) in the control area, and then the data is sent to the second slot (e.g., For example, in SL2), optional parameters associated with the data for decoding are AGC signal (e.g., AGC t) and an optional SCI (e.g., SCI1 t The UE transmits the HARQ ACK feedback. The block is at the end of slot SL2 or at the first SA SCI (e.g., SCI1 r). It may be in slot 3 which may be shown.

[0361] At BWP2, optionally with an AGC signal (e.g., AGC r) from the receiving UE A data request or reserved SA SCI (e.g., SCI2 r) is the first slot. (e.g., SL1) and data is assigned in the same slot, e.g., An optional AGC signal associated with the data for coding (e.g., AGC t) and NR-PSSCH2 with optional SCI (e.g., SCI2 t) The receiving UE's HARQ NACK feedback is sent in the second slot (e.g. For example, the retransmission may be at the beginning of the SASCI (SL2) and the retransmission on NR-PSSCH2 may be at the beginning of the SASCI ( For example, in the same slot (e.g., SL2) that can also be indicated by SCI2 r. is a resource allocation or scheduling technique for low latency data transmission. Here is an example.

[0362] As shown in FIG. 15B, the transmitting UE may allocate or schedule resources for data transmission. A unicast may be initiated by sending a request SCI to the ring.

[0363] In BWP1, a resource allocation or scheduling request SC from a transmitting UE I (e.g., SC1 t) is the feedback region of the first slot (e.g., SL1). The SA SCI (e.g., SCI1 r) is assigned in the second slot (e.g., , SL2), and then the data is transmitted in the same slot, e.g. Optionally, an SA SCI (e.g., SCI2) is used to decode the appended data. t) is transmitted on NR-PSSCH1. The receiving UE’s HARQ ACK feedback The block is allocated in slot 3.

[0364] In BWP2, optionally including an AGC signal (e.g., AGC t) from the transmitting UE A data request SCI (e.g., SCI2t) is sent to the first slot (e.g., SL1) The SA SCI (e.g., SCI2r) is assigned in the first minislot of the The data is then transmitted in the fourth minislot of the first slot (e.g., SL1), and then the data is In the first minislot of a slot (e.g., SL2), for example, data is decoded. Optionally, transmit on NR-PSSCH2 with SCI (e.g., SCI3t) to The receiving UE's HARQ ACK feedback is sent in the fourth mini-slot of the second slot. This is for low latency, short data transmission in minislots. 1 is an example of resource allocation or scheduling.

[0365] (Sensing for periodic and aperiodic transmissions) Sensitivity to periodic and aperiodic data transmissions via a shared resource pool An exemplary scheme of knowledge is shown in FIG. 16, which may have the following steps.

[0366] In step 1, the UE determines whether the planned data transmission is periodic or aperiodic, e.g. The layer parameter periodic is set to "1" for periodic and "0" for aperiodic. or the higher layer parameter period for the periodicity time interval is "1" If it is aperiodic, go to step 2A, if not, check for cyclic data transmission. Continue with Step 2B.

[0367] In step 2A, the UE determines a typical or maximum transport bandwidth for the V2X application. Maximum time resource (e.g. max- transmission-time), if it is enabled (e.g., repet ition_enable is "1", otherwise "0") iteration count (e.g., repetition-number), possible retransmission time lines (e.g., de Based on the lay-retransmission, etc., the sensing window size, e.g. For example, the window size is set as follows: can be estimated as window-size=max-transmission-time+(repet ition-number×max-transmission-time)×repe tition_enable+(delay-retransmission+max. transmission-time)+window-adjustment Here, the window adjustment is the adjustment for different nearby V2X services. The proposed method is to set the sensing window based on different QoS requirements such as latency, priority, and reliability. This is an additional time adjustment.

[0368] In step 2B, the UE determines a typical or maximum transport bandwidth for the V2X application. Maximum time resource for lock (TB) size, number of iterations if it is enabled , a possible retransmission time line, a period (e.g., period) for periodic transmissions, Based on periodic transmissions (e.g., trans-count) to ensure Sets the window size, e.g., window-size. The size can be estimated as follows: window-size=max.transmission-time+repeti tion-number × max.transmission-time (enabled (in this case)+delay-for-retransmission+max.transmi ssion-time+period×trans-count+window-adj ustment Here, the window adjustment is the adjustment for different nearby V2X services. The proposed method is to set the sensing window based on different QoS requirements such as latency, priority, and reliability. This is an additional time adjustment.

[0369] Compared with the aperiodic window size, the periodic sensing window size allows the UE to Resources for the next few transmissions of a message, e.g., trans-count If you need to store it, it is much larger. The longer the period, the larger the window size. It becomes louder.

[0370] In step 3 for resource sensing, the UE determines the resources to be used and / or the sensing Sense the resources reserved by a window. There are several mechanisms for implementing the sensing mechanism. There is a way.

[0371] If all SA SCIs within the sensing window can be decoded by the UE, the UE extracts the exact resources used and the resources reserved during the sensing window. Thus, the UE may issue periodic or aperiodic (e.g., event-triggered) The data transmission may then select a set of available resources required by the possible data transmission.

[0372] If not all SA SCIs are decodable to the UE, e.g. ,SCI is the ID, e.g., broadcast source I for V2X applications. D as source ID for the broadcast transmitter, SL-BT-RNTI, SL-M-RNTI as multicast ID, if group SL-G-RNTI as the sidelink ID of the group lead, The resource ID can be scrambled using the SL-C-RNTI or has already been scheduled or reserved by another UE via the SA SCI. In this case, the UE may detect resource usage by measurements, e.g., sidelink reference Signal Received Power (SL-RSRP) or Sidelink Reference Signal Received Quality (Sidelink Refe Receive Signal Received Quality (SL-RSRQ) is used for NR-PSCCH or NR - Measured from SL-DMRS of PSSCH. The measurement result is configured by higher layers. The threshold value, e.g., Sense_Th SL-RSRP or Sense_Th SL-R SRQ If the value is greater than 0, the measured SL-RSRP or SL-RSRQ is The associated resource is the resource to be used, e.g., as a resource that is not available. If the resources used indicate a repetitive pattern, the UE shall A turn may be expected to continue periodic transmissions for a particular length of time in the near future, e.g. For example, patterned resources are reserved for periodic transmissions. The method includes: energy-based measurements on NR-PSCCH and / or NR-PSSCH A value, for example, a Sidelink Received Signal Strength Indicator (SL-RSSI). SL-RSRP, SL-RSRQ, or SL-R Measurements on SSI can be configured via RRC or Sl-RRC. It may be based on a particular frequency unit, such as per BG or per subchannel. For more accurate use with time, use SL-RSRP, SL-RSRQ, or SL-RS Measurements on SI can also be configured via RRC or Sl-RRC, symbol by symbol NR may be based on a particular unit of time, such as per minislot, or per slot. - Energy-based measurements of PSCCH or NR-PSCH improve measured accuracy In order to achieve this, the SL-RSRP or SL-RSRQ of the NR-PSCCH, or the NR - It may be combined with SL-DMRS of PSSCH.

[0373] Another method is to use the results from the decoded SA-SCI, the NR-PSCCH and / or or SL-RSRP or SL-RSRQ measurements of NR-PSSCH, and / or or NR-PSCCH and / or NR-PSSCH energy measurement SL-RS SI, or a combination of them.

[0374] The UE shall maintain sense of the resources used and / or reserved in its sensing window. , its near future aperiodic or periodic transmissions in a time-sliding sensing window. An update may be maintained on the set of available resources for transmission.

[0375] In step 4, new data is ready for transmission, e.g. If higher layers indicate a trigger to transmit, proceed to step 5; otherwise, Continue with step 3 to sense available resources.

[0376] In step 5 for resource selection, the UE selects the TB Size, latency requirements, priority level, periodic or aperiodic (e.g. event triggers) Based on channel congestion, etc., a set of available resources is selected as candidate resources. The upper layer selects the resources to be used from the candidate resources. The UE may reserve the selected resources for the transmission or may decline to reserve. Use the selected resource for at least the initial transmission without any reservation to avoid delays For a shared resource pool or resource, the UE may use the same selected resource pool or resource. The UE transmits its data on selected resources to avoid possible collisions with other UE transmissions. Before transmitting data, resource-aware access is performed, e.g., energy-based SL-R Using Listen-Before-Talk (LBT), which is based on a very short measurement window for SSI measurement. If the measurement value exceeds a threshold, e.g., Measure_TH LBT If it is above U E may assume that the resource is being used by another UE, and then the UE is the time, e.g., T LBT_off backs off at 0 and reserves access resources for that transmission. Whether access resource sensing is valid for the data being transmitted or not For example, whether Acc_Reseource_En is 1 or 0 is indicated to the UE by higher layers. For example, for very low latency transmissions or very high priority transmissions, Access resource sensing may be disabled to save time, latency tolerant or For low priority transmissions, access resource sensing is performed to minimize latency or reduce priority. may be enabled to avoid collisions with transmissions of , Acc_Resource_En) for determining whether to sense access resources without Another way is to consider the latency budget (e.g., the time to transmit data). The latency requirement is too close to the threshold to detect the based on priority level (e.g., priority is based on the priority of the detection) or on priority level (e.g., priority is based on the priority of the detection). The priority threshold is based on whether the

[0377] In step 6, the UE determines the maximum number of LBT-based access resource sensing (e.g., x-LBT) has been reached or LBT-based access resource detection timed out by the maximum LBT timer (e.g., time-LBT) for If the UE reaches the maximum number of LBT-based access resource sensing, or if the UE is timed out for LBT-based access resource sensing; Go to step 7 for preemption decision, if not, go to step 8 , and performs LBT-based access resource sensing via the selected resource for its transmission. If max-LBT=0 or time-LBT=0, the UE There is no need to perform source sensing (e.g., there is another method to disable access resource sensing). law).

[0378] In step 7, the UE receives preemption from higher layers for a higher priority transmission. Determine whether pre-emption is enabled (for example, the parameter pre-emption is "1") or to preempt other lower priority data traffic. Allows checking the priority level (e.g., parameter priority) from higher layers or there is a latency requirement from a higher layer that allows preemption to avoid delays. (for example, the parameters latency_allowed or latency_ma x). The UE then decides to use the higher priority or lower latency transmission. It may be scheduled by other UEs with higher latency, lower priority, or less reliability. The UE may determine whether it can preempt reserved or reserved resources. It also checks the SL-RSRP, SL-RSRQ, or SL-RSSI to determine whether other UEs are receiving the The resources scheduled or reserved by the The UE may, as an example, determine whether it can receive emergency data from other UEs for its urgent data transmission. If E's scheduling or reserved resources can be preempted, If so, proceed to step 13 for preemption transmission, otherwise, Continue with step 17 to drop the transmission with an error report if out of jet, or proceeds to step 5 (not shown) to reselect candidate resources from the available resource set. The UE selects the SA SC that the selected resource is associated with for the data transmission. Preemption from other UE resources in I or SCI, e.g. emptied=1 or the 3-bit priority field in the SCI A reserved priority value for the field, e.g., priority="111" or " The SA SCI or SCI associated with the data transmission uses "000" Preemption may be implied.

[0379] In step 8, the UE, via the selected resource for accessing the resource, Perform access resource sensing, e.g., LBT-based sensing.

[0380] LBT-based access resources are allocated for different V2X services with different QoS requirements. The sensing can be implemented in several ways. For example, it can be priority based (e.g., higher priority , lower backoff, or no backoff time), adaptive based (e.g., LBT failure) Decreasing the backoff time each time), randomly based (e.g., within a backoff range) by randomly selecting values), transmitter / receiver handshaking based (e.g. For example, to avoid hidden nodes).

[0381] In step 9, resources are sensed as available via the selected resource. If so, proceed to step 12 to transmit data, otherwise, return to step 13 to back off. Continue to Step 10.

[0382] In step 10, the UE may wait a backoff time, which may be a randomly generated or priority-based, or the UE fails LBT-based resource sensing. The backoff parameters of the different backoff schemes may be decreased each time. The data may be configured and indicated by higher layers.

[0383] In step 11, the UE checks whether the backoff time expires. If so, , proceed to step 6 to check if it is a timeout, then if it is not a timeout In step 8, perform LBT-based resource sensing again; otherwise, perform step 1. Continue waiting at 0.

[0384] In step 12, the UE reserves the selected resources for the transmission, or Access selected resources for the transmission of data, as well as aperiodic V2X messages. For messages (e.g. event-triggered messages), repeat if enabled. and reserve resources for retransmissions if enabled, or periodic V2X For messages, repeat, if enabled, retransmit, if enabled, and and for some new transmissions (defined, for example, by trans-count) This will allow the company to secure the resources to do so.

[0385] If the data transmission is periodic, the periodic transmission counter is decremented by one after each successful transmission. (For example, trans-count=trans-count-1).

[0386] In step 13 for preemption transmission, the UE determines the TB size, latency requirement, , priority level, periodic or event triggered, impact on preempted UEs Select reserved resources that are preempted based on noise, interference, congestion, etc. The UE may transmit data over the preempted resources. The reserved resources of other UEs that have been registered (e.g. new response to preemption notification) New format SCI or SA SCI with preemption flag set to "1" or the priority value stored in the SA SCI ("111" or "000") Broadcasting an emptiness indication or transmitting data to a receiver The preemption in the SCI transmitted with the Data transmission through the allocated resources will be based on the urgency and priority of the data being transmitted. It can be LBT sensing based.

[0387] In step 14, the UE determines whether any reserved transmissions, e.g., repetitions for periodic data, are enabled. If not, go to step 18. Either stop sensing by pressing the If so, restart sensing (not shown), otherwise proceed to step 15 to confirm. Check whether the reserved resource is preempted.

[0388] In step 15, the UE receives the pre-transmission request as configured via RRC or Slk-RRC. In the case of preemption monitoring (e.g., a UE that preempted reserved resources) Whether there are any preemption indications broadcast by In the case of preemption monitoring or scheduling monitoring, for example, If there is no preemption indication indicated by the SCI, the UE shall Proceed to step 16 to determine whether any reservation was made and, if not, to preempt the With the reserved resources allocated, the UE proceeds to step 3 and updates its sensing window The UE re-senses available resources at the preemption time for high priority data. If enabled in this option, the UE shall perform preemption as described for step 7. Alternatively, the user may use the START_TRANSMISSION_TIME option to jump to step 7 for a new transmission (not shown in FIG. 16).

[0389] In step 16, the UE determines whether the trans-count is a periodic count on the reserved resources. Whether the data transmission is above a threshold specified by higher layers Check whether the new If there are no periodic transmissions or resources reserved for repeat or retransmission, and proceed to step 3 for window-based sensing to find candidate resources. Otherwise, repeat, retransmission, or other methods may be used for periodic data transmission on the reserved resources. Or proceed to step 4 for new data.

[0390] In step 17, the UE drops the transmission and reports a resource access error to higher layers. Then proceed to step 18 or go to step 5 to reselect candidate resources. (not shown) or go back to step 3 to sense again (not shown).

[0391] At step 18, the sensing procedure may be terminated.

[0392] (resource selection and reselection) As shown in FIG. 26A, FIG. 26B, and FIG. 26C, the UE may or X1 milliseconds) and a long time interval "sensing window 1" (e.g. For example, a short period of time (having a length of X2 slots or X2 symbols, or X2 milliseconds) The UE may perform channel sensing in “sensing window 2” every Y slot. The resource for data transmission is a "selection window" of time interval (having a length, or Y milliseconds). The source may be selected.

[0393] Initial transmission (e.g., TB1 in slot i+1), blind retransmission (e.g., for TB1 at i+2), and for periodic traffic (e.g., SA SCI (e.g., SCI for TB2) indicating resource reservation for a new transmission SCI1) in lot i is shown in Figure 26A.

[0394] Initial transmission (e.g., for TB1), HARQ retransmission (e.g., in slot i+2) retransmissions for TB1), and for periodic traffic (e.g., retransmissions for TB2 ) HARQ feedback for a new transmission (e.g., SFCI1 in slot i+1) ) indicates resource reservation for an SCI (e.g., SCI for initial transmission in slot i) 1) is shown in Figure 26B.

[0395] Retry for blind retransmission (e.g., repetition for TB1 in slot i+1) The SCI that indicates source reservation (e.g., SCI1 in the initial transmission in slot i) is For non-periodic traffic, e.g., event-triggered transmission, see FIG. 26C. can be.

[0396] As shown in FIG. 27, the UE transmits data, e.g., a transport block (TB), The following steps may be performed to select the resource:

[0397] In step 1 (long sensing for available resources), the UE transmits the NR-PSCCH Decode the scheduling or resource reservation SCI to be carried and schedule or via reserved resources, SL-RSRP and / or Sidelink reference signal received power (SL-RSRP) ), one can sense the available resources within a long sensing window. Resources may be excluded if they meet the following criteria: Resources indicated by another UE in a Scheduling SCI or a Reserved SCI. These resources are required if the UE needs them to transmit any of its next data TBs. are assigned at the same time. The resource may be preempted by another UE with preemption indicated by the SCI. will be done. The UE shall notify the scheduling SCI, reservation SCI or preemption SCI. The subchannel or RB or physical link used to transmit the associated TB. NR-PSCCH and and / or measure the average SL-RSRP of the DMRS of the NR-PSSCH, the measurement being Given threshold M th (e.g., they cannot share the same resources, collisions are low) decrease).

[0398] In step 2 (Data Available), a new data TB is timely made available for transmission from higher layers. At time T0, it is determined whether the device is ready. If so, it is used to set the selection window. If so, go to step 3, if not, go to step 1 and continue long sensing.

[0399] In step 3 (selection window), select Latency, Priority, Reliability, and Periodic Trough Set the selection window based on QoS requirements such as duration for traffic. The end of the window may be defined by a maximum latency requirement for a data TB transmission.

[0400] In step 4 (short sensing for candidate resources), we consider short sensing wins at a finer granularity. In particular, we identify available candidate resources for low latency data traffic within the The measurement is based on the NR-PSCCH DMRS and / or SL-RSRP of NR-PSSCH DMRS, or sidelink reception The signal strength indicator (SL-RSSI) can be a very low latency resource. For selection, this short sensing may be used for access resource sensing, e.g., listen-before-talk. The candidate resources can be similar to the candidate single-slot resources (Ca A single-slot resource such as a CSSR (Initialize Single-Slot Resource), or Candidate Multi-Symbol Resource (CMSR) and other There may be multiple symbols (e.g., one or more) resources. A resource is a message. Depending on the page size, a slot can have 1 to S adjacent subchannels or RBs. The UE may be configured with multiple slots or symbols, e.g., X2 slots. Select a set of CSSR or CMSR in the selection window that spans a set of bits or symbols possible.

[0401] In step 5 (threshold measurement), an initial threshold M Th Set the M Th Value of The features include priority, latency, reliability, communication range or zone, interference measurement, e.g., side link Based on QoS requirements such as SL-SINR and congestion measurements, It can be configured by higher layers.

[0402] In step 6 (initial candidate resource list), all available CSSRs from the sense Or, set the initial available candidate resource list R in the CMSR. Resources that are not monitored by the UE are not included in list R.

[0403] In step 7 (measurement), via the CSSR or CMSR of a candidate resource, e.g., R Measurements are performed on the NR-PSCCH and / or NR-P It may be SL-RSSI or SL-RSRP or SL-SINR of SSCH.

[0404] In step 8 (update candidate resource list), the threshold M Th Exceeds the measured SL-R Eliminate CSSR or CMSR with SSI or SL-RSRP or SL-SINR values By doing so, the candidate resource list R is updated.

[0405] In step 9 (Are there enough left in R?), the candidate resources left in list R are: Check if the resource is greater than p% of the total resources, where p is the priority, latency, QoS requirements such as reliability, communication range or zone, as well as interference and congestion levels If yes, proceed to step 12 for reporting. If not, proceed to step 10 and adjust the measurement threshold.

[0406] In step 10 (increasing the threshold), Th Inc dB (e.g., M Th =M Th +T h Inc ) to increase the threshold. Here, Th Inc The priority, latency, and signal Based on QoS requirements such as reliability, communication range or zone, and interference and congestion levels. Returning to step 11, the CSS collected from the sensing Check whether the candidate resource list R needs to be reconfigured in R or the CMSR.

[0407] In step 11 (Reconfigure R?), it is checked whether to reconfigure the candidate resource set R. If yes, proceed to step 6 to check the candidate in the CSSR or CMSR collected from sensing. Reconfigure the complementary resource list, otherwise proceed to step 8 and use the adjusted threshold. Update the candidate resource list.

[0408] In step 12 (measurement), measurements are made over the updated candidate resources of R, and the upper layer is notified. The measurements are based on NR-PSCCH and / or CMSR via CSSR or CMSR of R. is the line of SL-RSSI, SL-RSRP, or SL-SINR of NR-PSSCH The minimum average of S-RSSI or SL-RSRP or SL-SINR The CSSR or CMSR is selected by the UE and reported to the higher layer.

[0409] In step 14 (selection), the upper layer selects the TB size, priority, latency, reliability, and communication Based on the range or zone, and QoS requirements such as interference and congestion measurements, Select a resource from the candidate resources CSSR or CMSR or Randomly select candidate resources for transmission. Blind retransmission (e.g., repetition) is enabled. If the blind retransmission instance is selected, the candidate resource (e.g., the starting sequence If HARQ feedback is enabled, the HARQ feedback symbol can also be selected. Candidate resources corresponding to the back-end instances, e.g., based on the HARQ processing time line The starting symbol for the sidelink feedback control information (SFCI) may also be selected. For the number of HARQ processes, h, the candidate resources for HARQ retransmissions are also For example, the set of selected initial transmission opportunities is T0+T k (k=0,1,..,K is the number of TBs. , and another set of HARQ retransmission opportunities T0+T k +T h Selected against where T h ≠0, and T h ≦x, where x is the HARQ processing time of the UE Budget-based. Semi-Persistent Scheduling (SP S), e.g., for periodic transmission, the candidate resource corresponding to the next packet transmission is defined by, for example, a resource counter (RC). ,RCs can be selected randomly within a range configured by the upper layer, or,selected according to priority. , Duration, Latency, Communication Range or Zone, Packet Size, Blind Retransmission, H The selection may be based on ARQ retransmissions, interference, congestion levels, etc.

[0410] (Congestion Control) For sidelink congestion control, the UE reserves resources or transmits packets. Before transmitting or retransmitting, the new radio channel busy rate is io:NR-CBR) and New Radio Channel occupancy Ra NR-CBR is an indication of the channel congestion level. The CBR threshold M CBR Higher average SL-RSRP or SL - Previous S with SINR or SL-RSSI CBR Subchannels in a slot or NR-CR may be calculated as the amount of PRBs. It indicates that the transmitting UE is CB The subchannel or This time interval can be calculated as the amount of PRBs that resources are reserved by the transmitting UE. If so, past and future S x The NR-CBR interval and the NR The NR-CB interval is illustrated in FIG. 28. The NR-CBR interval and the NR-CB interval are different. QoS requirements, e.g., latency, priority, reliability, range or zone, and It is configured separately by higher layers according to the traffic characteristics and congestion level in the system. It can be done.

[0411] For congestion control, the channel occupancy threshold CR th The UE allocates resources and transmits For different QoS requirements, different CRs can be defined to manage th The threshold is These can be configured or signaled by the layer. For example, priority, latency, reliability, The communication range or zone is the CR for the data packet. th Used to specify the value of The transmitting UE may use Inter CBR Configured or signaled by higher layers at CBR intervals For each CBR interval, the transmitting UE may transmit at a particular CBR level. Max CR th The CR for each CBR interval cannot exceed th The value of is the packet QoS requirements, e.g. priority, latency, reliability, range or zone, etc. It may be variable.

[0412] When the transmitting UE reserves resources for blind retransmission or HARQ retransmission. ,It measures NR-CBR, and its NR-CR is its CR th Whether or not the requirements are met As a result, the UEth The retransmission resource is appropriately allocated without exceeding can be secured.

[0413] When the UE transmits or retransmits a packet, it measures the NR-CBR and NR-CR is the CR th Check whether the requirements are met. th If the value is higher than , it is due to the UE's capabilities, data packet size, and reliability, Based on data packet QoS requirements such as bandwidth, priority, range or zone, In the example below, CR th Can be reduced to less than: Dropping a transmission, i.e. the UE may decide not to can drop certain data packet transmissions based on their QoS requirements, such as zones. For example, lower priority or longer latency may reduce the NR-CR. or poor reliability, or data packet transmission outside the required communication range or zone. Drop the transmission. Reduce the number of retransmissions. UEs may experience slower transmissions due to lower priority or lower reliability or longer latency. By reducing blind retransmission or HARQ retransmission of packets in the This may reduce the CR. Modulation and Coding Scheme (MCS) That is, the UE may reduce the CR by adjusting the MCS. , the UE increases the MCS of the data packet to determine the subchannel used for transmission. or may save PRBs and / or symbols; and / or Reduce the Transmit Power (TP), i.e. the UE will not exceed the minimum range requirement. By reducing its transmission power for each case, the measurements via all NR-CBR are lowered, and Therefore, the CR th The requirements can be met.

[0414] Similarly, the receiving UE may receive NR-CBR and / or CR th Based on requirements, HARQ It may decide to drop the feedback or CSI report. The UE returns NACK feedback in response to HARQ ACK / NACK feedback. The receiver UE may drop the CSI report when the channel variation is low. This is also fine.

[0415] An example of congestion control is shown in FIG. 29, which includes the following steps.

[0416] In step 1 (measurement of NR-CBR / NR-CR), resource sensing and / or selection During the transmission, the SL-RS of the NR-PSCCH and / or the NR-PSSCH is Measure RP or SL-RSSI.

[0417] In step 2 (Data Available?), if a new data packet is available, Go to step 3 to check its CRth requirement, if not, NR-CBR / NR-CR Go to step 1 to continue the measurement.

[0418] Step 3 (CR th ?) and the measured CR is the maximum CR th If it exceeds If so, proceed to step 4A for reduced resource allocation, otherwise proceed to normal resource allocation. Continue with step 4B to ensure

[0419] In step 4A (reduced resource reservation), the resource reservation for transmission and / or retransmission is performed. For example, by increasing the MCS, the resource is reduced, and the priority, latency, reliability, communication range or zone, as well as data packet size and current Based on QoS requirements such as congestion level, blind retransmission and / or HARQ retransmission can be performed. Reduce the number of transfers.

[0420] In step 4B (regular resource allocation), priority, latency, reliability, range or reserves resources based on zones and QoS requirements such as data packet size. do.

[0421] Step 5 (CR th (exceeds CRth?) before transmission or retransmission. If yes, go to step 6 to drop the transmission, if not, If so, go to step 8 for transmission or retransmission.

[0422] Step 6 (Drop Transmission?) determines whether dropping the transmission or retransmission is permitted. If yes, go to step 7A for congestion control with dropping, otherwise If not, proceed to step 7B for no-drop congestion control.

[0423] In step 7A (congestion control with dropping), it is decided to drop the transmission. Proceed to step 9.

[0424] In step 7B (congestion controlled transmission without drops), adjustments such as increasing MCS and decreasing TP are made. Make adjustments.

[0425] In step 8 (transmission), the data packet is transmitted with the adjusted MCS and / or TP. Or retransmit.

[0426] In step 9 (Reselect resource?), the previously established Check whether the reserved resource needs to be cancelled and reselected. If yes, If so, reset the reselection counter CR and go to step 1.

[0427] For Mode 1, the gNB periodically requests each UE (e.g., the gNB period) or upon request, the measured The CBR can be reported.

[0428] Any of the devices, systems, methods, and processes described herein or All are implemented by computer executable instructions (e.g., The instructions may be embodied in the form of a program code (program code), which may be executed by the processor 118 or When executed by a processor, such as 91, the processor performs the system described herein. It is understood that the systems, methods, and processes may be implemented and / or performed by the present invention. Specifically, any of the steps, operations, or functions described herein may be implemented in any manner that is suitable for use in a particular application. Implemented in the form of such computer-executable instructions, Executed on a processor of a device or computing system configured for communications The computer-readable storage medium may be any non-transitory (e.g., volatile) medium for storing information. Volatile and non-volatile media implemented in any form or physical method or technology, removable and non-removable media, such computer-readable storage media including signals. The computer readable storage medium may include RAM, ROM, EEPROM, flash memory, or other memory technology, CD-ROM, Digital Versatile Disk (DVD) or Other optical disk storage devices, magnetic cassettes, magnetic tapes, magnetic disk storage devices or or other magnetic storage device, or may be used to store desired information, and Any other tangible or physical medium that can be accessed by a computing system Including, but not limited to:

[0429] Below is a list of acronyms related to service layer technologies that may appear in the above description. In particular: Unless specified, the acronyms used herein stand for the corresponding terms listed below. Point. ACK:ACKnowledgement BSM: Basic Safety Message CAM: Common Awareness Messages CE: Control Element DFN: Direct Frame Number EtrA: Emergency Trajectory Alignment HARQ: Hybrid Automatic Repeat Request LoA: Level of Automation LTE: Long Term Evolution MAC: Medium Access Control MIB: Master Information Block NACK: Negative ACKnowledgement NR:New Radio PLMN: Public Land Mobile Network NR-PSCCH: NR Physical Sidelink Control Channel Nell) NR-PSDCH: NR Physical Sidelink Discovery Channel Channel) NR-PSSCH: NR Physical Sidelink Shared Channel Nell) NR-PSSS: NR Primary Sidelink Synchronization Signal Link sync signal) RAN: Radio Access Network RNTI: Radio Network Temporary Identifier RRC: Radio Resource Control SA:Sensing Assistant SCI: Sidelink Control Information SI: System Information NR-SSSS: Secondary Sidelink Synchronization Signal Initial signal) UE: User Equipment V2V: Vehicle-to-Vehicle V2X: Vehicle-to-everything

Claims

1. 1. A wireless transmit / receive unit (WTRU) comprising a processor, the processor comprising: receiving a Radio Resource Control (RRC) message including a configuration associated with a resource pool located in the sidelink bandwidth part; determining a sensing window for selecting resources for sidelink transmission; performing a sidelink reference signal received power (SL-RSRP) measurement for one or more resources of the resource pool within the sensing window; determining a set of available resources in the resource pool based on the SL-RSRP measurements and priorities associated with the sidelink transmissions; selecting one or more resources from a set of available resources in the resource pool for the sidelink transmission. The WTRU is configured to:

2. The WTRU of claim 1 , wherein the processor is configured to determine the sensing window based on a time indicated in the configuration.

3. The WTRU of claim 1 , wherein the processor is further configured to transmit an indication of the selected one or more resources.

4. 4. The WTRU of claim 3, wherein the indication of the selected resource or resources is included in a scheduling assignment (SA) sidelink control information (SCI).

5. The WTRU of claim 4 , wherein the SA SCI includes an indication of resources for one or more Hybrid Automatic Repeat Request (HARQ) retransmissions associated with the sidelink transmission.

6. The WTRU of claim 1 , wherein the processor is configured to transmit the sidelink transmission using the selected one or more resources.

7. The WTRU of claim 1 , wherein the processor is configured to determine resource usage associated with the resource pool.

8. The WTRU of claim 1 , wherein the processor is configured to randomly select the one or more resources from a set of available resources in a resource pool for the sidelink transmission.

9. The WTRU of claim 1 , wherein the sidelink transmission is a periodic transmission.

10. The WTRU of claim 1 , wherein the sidelink transmission is aperiodic transmission.

11. receiving a Radio Resource Control (RRC) message including a configuration associated with a resource pool located in the sidelink bandwidth part; determining a sensing window for selecting resources for sidelink transmission; performing a sidelink reference signal received power (SL-RSRP) measurement for one or more resources of the resource pool within the sensing window; determining a set of available resources in the resource pool based on the SL-RSRP measurements and priorities associated with the sidelink transmissions; selecting one or more resources from a set of available resources in the resource pool for the sidelink transmission. A method comprising:

12. The method of claim 11 , further comprising determining the sensing window based on a time indicated in the configuration.

13. The method of claim 11 , further comprising transmitting an indication of the selected one or more resources.

14. 14. The method of claim 13, wherein the indication of the selected resource or resources is included in a Scheduling Assignment (SA) Sidelink Control Information (SCI).

15. 15. The method of claim 14, wherein the SA SCI comprises an indication of resources for one or more Hybrid Automatic Repeat Request (HARQ) retransmissions associated with the sidelink transmission.

16. 12. The method of claim 11, further comprising transmitting the sidelink transmission using the selected one or more resources.

17. The method of claim 11 , further comprising determining resource usage associated with the resource pool.

18. 12. The method of claim 11, further comprising randomly selecting the one or more resources from a set of available resources in a resource pool for the sidelink transmission.

19. 12. The method of claim 11, wherein the sidelink transmission is a periodic transmission.

20. 12. The method of claim 11, wherein the sidelink transmission is an aperiodic transmission.