TW201935981A - Sidelink resource pool activation - Google Patents

Abstract

Processing for activating and deactivating sidelink resource pools is described. A WTRU may be configured with a plurality of sidelink resource pools and may activate one or more resource pools for use in communicate with other WTRUs. The WTRU may autonomously and dynamically determine which resource pools to activate and deactivate. For example, the WTRU may determine, based upon the characteristics of the data that it will be sending and/or receiving, to activate a resource pool suitable for transmitting and receiving the data. The WTRU may determine, based upon indications that it receives from another WTRU, to activate a resource pool compatible with that being used by the other WTRU. The WTRU may determine, based upon instructions and/or communications that it receives from a radio access network to activate a particular resource pool.

Description

Start of sidechain resource field

Cross-reference to related applications

This application claims the benefit of US Provisional Application No. 62 / 629,977 entitled "Dynamic Resource Allocation in NR EV2X" filed on February 13, 2018, and asserted in 2018 Interest of U.S. Provisional Application No. 62 / 652,016 entitled "Dynamic Resource Allocation in NR EV2X" filed on April 3, and claiming the question filed on September 24, 2018 This is the benefit of US Provisional Application No. 62 / 735,237 for "Dynamic Resource Allocation in NR eV2X", the entire contents of which are incorporated herein by reference.

Wireless communication devices can establish communication with each other via one or more networks. For example, a first wireless communication device may form a wireless connection with a radio access network (RAN) device such as eNodeB, and eNodeB may forward data to a second wireless communication device via a wired network, and may have formed with it. Wireless connection to another eNodeB. Data passed between wireless devices traverses radio access networks and intervening wired networks on paths between the devices.

In some cases, wireless communication devices can establish direct communication with each other. Data can be transferred directly between wireless devices without having to traverse a radio access network and / or related communication network. Such device-to-device communication may be referred to as side-link communication. Side-link communication can use a resource pool, which defines the physical resources in time and frequency that can be used to carry control and traffic data between wireless devices. The side-link resource pool can specify resource blocks and corresponding sub-frames that can be used to directly transfer data between wireless devices.

Systems and methods for side-link resource pool activation for device-to-device communication are disclosed here. A mobile device, which may be, for example, a wireless transmit and receive unit (WTRU), may be configured with multiple side-link resource pools. The WTRU may utilize the activated first side link resource pool for side link communication with the second WTRU. The WTRU uses the resource blocks and sub-frames indicated by the first side link resource pool to communicate directly with the second WTRU.

The WTRU may determine to start a second side link resource pool from multiple resource pools configured for the WTRU. This determination may be made autonomously by the WTRU based on one or more factors. For example, the WTRU may determine that the activated first side link resource pool is not suitable for transmission and / or reception of the side link packet based on the priority associated with the side link packet, and may also determine the second side chain The channel resource pool is suitable for transmitting and / or receiving the side link packets. In another example, the WTRU may determine that the activated first side link resource pool does not support the transmission latency associated with the side link packet, and may determine that the second side link pool supports the transmission latency. In another example, when it is determined that the energy on the activated first side link resource pool meets a critical value, the WTRU may determine to activate the second side link resource pool. When it is determined that the measurement channel busy ratio (CBR) on the activated first-side link resource pool meets a critical value, the WTRU may also determine to start the second resource pool.

The WTRU may start the second-side link resource pool. Initiating the second side link resource pool may include the WTRU identifying that the resources specified by the second side link resource pool are available for the side link communication of the WTRU. The WTRU may use the resource blocks and sub-frames specified by the side-link resource pool to transfer data.

The WTRU may transmit an indication to other devices that the mobile device has activated the second-side link resource pool. This indication may be communicated explicitly or implicitly. For example, an indication in a side link control information (SCI) message, an indication in a separate physical channel, and / or an indication in an active resource pool may be used to explicitly convey an indication that the side link resource pool has been activated.

A WTRU may be configured to determine an initiating-side link resource pool based on communication from another WTRU. The first WTRU may receive an instruction to start the first side link resource pool from the second WTRU. The first side link resource pool is one of a plurality of side link resource pools configured for the first WTRU. For example, the WTRU may receive a side link control information (SCI) message from another WTRU indicating that the first side link resource pool is activated. The message may include a resource pool indicator (RPI) identifying the specific resource pool to be started. The message may indicate that a resource pool associated with a particular priority or latent classification is initiated. Upon receiving and processing the indication from another mobile device, the WTRU may initiate the identified resource pool.

The WTRU may be configured to determine the initiating-side link resource pool based on communication from the network. The WTRU may be configured to receive explicit instructions from a network (eg, a RAN network (eg, gNB, eNB, etc.)) to activate and / or deactivate a side link resource pool. For example, the WTRU may monitor the downlink control information (DCI) for an indication for starting the side link resource pool. The WTRU may be configured to monitor implicit indications from the network to activate and / or deactivate the side link resource pool. For example, the WTRU may be configured to monitor changes in operating parameters (eg, dynamic beam configuration and / or dynamic bandwidth configuration), and the WTRU may be configured to interpret it as a request to activate and / or deactivate the side link resource pool.

This summary is provided to introduce a selection of concepts in a simplified form that are further described in the embodiments herein. This summary is not intended to limit the scope of the claimed subject matter. This article describes other features.

The WTRU may be configured to perform processing for initiating and deactivating a side link resource pool for direct communication with one or more other WTRUs. A WTRU may be configured with one or more sets of receive / transmit resource pools, which define resources that can be used for side-link communication with other WTRUs. For example, side-link communication can be used for applications such as vehicle-to-everything (V2X) communication. The examples described herein can be applied to the WTRU enabling and / or deactivating various transmission / reception resource pools, and the transmission / reception resources can be used to support various communication types and / or applications.

The side-link resource pool that can be started in side-link communication and used can be changed. The WTRU may dynamically and autonomously determine to activate and / or deactivate the side link resource pool. For example, the WTRU may determine to initiate a pool of resources suitable for transmitting and / or receiving data based on the characteristics of the data it will send and / or receive. The WTRU may also determine to activate and / or deactivate the side link resources in response to the received indication, which may be a resource pool indication (RPI). This RPI may be received from the network and / or from another WTRU. It may be explicitly signaled that the RPI and / or the WTRU may implicitly determine the RPI based on one or more criteria. For example, the RPI may be clearly indicated in the downlink control information (DCI), and the WTRU may monitor the downlink control information on one or more downlink channels (for example, the downlink control channel). The RPI may be implicitly indicated based on one or more of the following: a group public entity carrying a time slot format indicator (SFI), a downlink control channel (PDCCH), a dynamic change in beam configuration, and / or a dynamic Bandwidth is enabled / disabled.

FIG. 1A is a diagram illustrating an exemplary communication system 100 that can implement the disclosed embodiments. The communication system 100 may be a multiple access system that provides multiple wireless users with content such as voice, data, video, messaging, and broadcasting. The communication system 100 can enable multiple wireless users to access such content by sharing system resources including wireless bandwidth. For example, the communication system 100 may use one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA) ), Single carrier FDMA (SC-FDMA), zero tail unique word DFT extended OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtering OFDM, and filter bank multi-carrier (FBMC), etc. Wait.

As shown in FIG. 1A, the communication system 100 may include a wireless transmission / reception unit (WTRU) 102a, 102b, 102c, 102d, RAN 104/113, CN 106/115, a public switched telephone network (PSTN) 108, the Internet Circuit 110 and other networks 112, however it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each WTRU 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. For example, WTRUs 102a, 102b, 102c, 102d (each of which may be referred to as a "station" and / or "STA") may be configured to transmit and / or receive wireless signals and may include user equipment (UE), mobile station, fixed or mobile subscriber unit, subscription-based unit, pager, mobile phone, personal digital assistant (PDA), smart phone, laptop, small laptop, personal computer, wireless Monitors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMD), vehicles, drones, medical devices and applications (such as remote surgery), industrial equipment, and Applications (such as robots and / or other wireless devices operating in an industrial and / or automated processing chain environment), consumer electronics devices, and devices operating on commercial and / or industrial wireless networks. Any of the WTRUs 102a, 102b, 102c, 102d may be interchangeably referred to as a UE.

The communication system 100 may further include a base station 114a and / or a base station 114b. Each base station 114a, 114b may be configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate its access to one or more communication networks (e.g., CN 106/115, Internet) 110, and / or other networks 112). For example, the base stations 114a, 114b may be base transceiver stations (BTS), node B, e-node B, local node B, local e-node B, gNB, NR node B, site controller, access point (AP ), And wireless routers. Although each base station 114a, 114b is described as a single element, it should be understood. The base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

The base station 114a may be part of the RAN 104/113, and the RAN 104/113 may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller ( RNC), relay nodes, and so on. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies called cell (not shown). These frequencies can be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. Cells can provide wireless service coverage for specific geographic areas that are relatively fixed or are likely to change over time. Cells can be further divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Therefore, in one embodiment, the base station 114a may include three transceivers, that is, one transceiver for each sector of a cell. In an embodiment, the base station 114a may use multiple-input multiple-output (MIMO) technology and may use multiple transceivers for each sector of a cell. For example, beamforming may be used to transmit and / or receive signals in a desired spatial direction.

The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d via an air interface 116, where the air interface may be any suitable wireless communication link such as radio frequency (RF), Microwave, centimeter wave, micro wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

More specifically, as described herein, the communication system 100 may be a multiple access system and may use one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, base stations 114a and WTRUs 102a, 102b, 102c in RAN 104/113 may implement radio technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) ) To build the air interface 115/116/117. WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA +). HSPA may include high-speed downlink (DL) packet access (HSDPA) and / or high-speed UL packet access (HSUPA).

In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as evolved UMTS terrestrial radio access (E-UTRA), where the technology may use long-term evolution (LTE) and / or advanced LTE (LTE-A) and / or Advanced LTA Pro (LTE-A Pro) to establish the air interface 116.

In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR radio access, where the radio technology may use a new radio (NR) to establish the air interface 116.

In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, base station 114a and WTRUs 102a, 102b, 102c may implement LTE radio access as well as NR radio access (eg, using the dual connectivity (DC) principle). Therefore, the air interface used by WTRUs 102a, 102b, and 102c can be characterized by multiple types of radio access technologies and / or transmissions to / from multiple types of base stations (such as eNBs and gNBs).

In other embodiments, the base station 114a and the WTRUs 102a, 102b, and 102c may implement, for example, IEEE 802.11 (ie, wireless high-fidelity (WiFi)), IEEE 802.16 (Global Interoperable Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rate for GSM Evolution (EDGE) And GSM EDGE (GERAN) and other radio technologies.

The base station 114b in FIG. 1A may be a wireless router, a local Node B, a local eNode B, or an access point, and may use any suitable RAT to facilitate, for example, a business place, a residence, a vehicle, a campus, an industrial facility, an air corridor (Such as for drones) and wireless connections in local areas such as roads. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may use a cellular-based RAT (such as WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a picocell or Femtocell. As shown in FIG. 1A, the base station 114 b may have a direct connection to the Internet 110. Therefore, the base station 114b does not need to access the Internet 110 via the CN 106/115.

RAN 104/113 may communicate with CN 106/115, where the CN may be configured to provide voice, data, applications, and / or Internet Protocol Voice (VoIP) to one or more WTRUs 102a, 102b, 102c, 102d ) Serving any type of network. The data can have different quality of service (QoS) requirements, such as different liquidity requirements, latency requirements, fault tolerance requirements, reliability requirements, data circulation requirements, and mobility requirements. CN 106/115 can provide call control, billing services, mobile location-based services, pre-paid calling, internet connection, video distribution, etc., and / or can perform high-level security functions such as user authentication. Although not shown in Figure 1A, it should be understood that RAN 104/113 and / or CN 106/115 can communicate directly or indirectly with other RANs that use the same RAT as RAN 104/113, or Different RATs are used. For example, in addition to connecting to RAN 104/113 using NR radio technology, CN 106/115 can also communicate with another RAN (not shown) using GSM, UMTS, CDMA 2000, WiMAX, E-UTRA or WiFi radio technology .

CN 106/115 may also act as a gateway for WTRUs 102a, 102b, 102c, 102d to access PSTN 108, Internet 110, and / or other networks 112. PSTN 108 may include a circuit-switched telephone network that provides simple legacy telephone service (POTS). The Internet 110 may include a public communication protocol such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and / or Internet Protocol (IP) in the TCP / IP Internet Protocol family. Globally interconnected computer network device system. The other networks 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, the other network 112 may include another CN connected to one or more RANs, where the one or more RANs may use the same RAT or different RATs as the RAN 104/113.

Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities (eg, WTRUs 102a, 102b, 102c, 102d may include multiple transceivers communicating with different wireless networks on different wireless links) . For example, the WTRU 102c shown in FIG. 1A may be configured to communicate with a base station 114a that may use cellular-based radio technology, and with a base station 114b that may use IEEE 802 radio technology.

FIG. 1B is a system diagram illustrating an exemplary WTRU 102. FIG. As shown in FIG. 1B, the WTRU 102 may include a processor 118, a transceiver 120, a transmitting / receiving element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, a non-removable memory 130, and a removable Memory 132, power supply 134, global positioning system (GPS) chipset 136, and other peripheral devices 138. It should be understood that, while remaining consistent with embodiments, the WTRU 102 may also include any sub-combination of the aforementioned elements.

The processor 118 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, and a microcontroller , Special integrated circuit (ASIC), field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), state machine, etc. The processor 118 may perform signal encoding, data processing, power control, input / output processing, and / or any other function that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, and the transceiver 120 may be coupled to the transmitting / receiving element 122. Although FIG. 1B depicts the processor 118 and the transceiver 120 as separate components, it should be understood that the processor 118 and the transceiver 120 may also be integrated into one electronic component or chip.

The transmitting / receiving element 122 may be configured to transmit signals to or receive signals from a base station (eg, base station 114a) via the air interface 116. For example, in one embodiment, the transmitting / receiving element 122 may be an antenna configured to transmit and / or receive RF signals. For example, in an embodiment, the transmitting / receiving element 122 may be a radiator / detector configured to transmit and / or receive IR, UV, or visible light signals. In an embodiment, the transmission / reception element 122 may be configured to transmit and / or receive RF and optical signals. It should be understood that the transmission / reception element 122 may be configured to transmit and / or receive any combination of wireless signals.

Although the transmitting / receiving element 122 is described as a single element in FIG. 1B, the WTRU 102 may include any number of transmitting / receiving elements 122. More specifically, the WTRU 102 may use MIMO technology. Accordingly, in an embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (eg, multiple antennas) via the air interface 116 to transmit and receive radio signals.

The transceiver 120 may be configured to modulate a signal to be transmitted by the transmission / reception element 122 and to demodulate a signal received by the transmission / reception element 122. As described herein, the WTRU 102 may have multi-mode capabilities. Accordingly, the transceiver 120 may include multiple transceivers that enable the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

The processor 118 of the WTRU 102 may be coupled to a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (such as a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit), and may Receive user input from these components. The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from and store data in any suitable memory, such as non-removable memory 130 and / or removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access and store information from memory that is not physically located on the WTRU 102. For example, such memory may be located on a server or a home computer (not shown) .

The processor 118 may receive power from the power source 134 and may be configured to distribute and / or control power for other elements in the WTRU 102. The power source 134 may be any suitable device that powers the WTRU 102. For example, the power source 134 may include one or more dry battery packs (such as nickel-cadmium (Ni-Cd), nickel-zinc (Ni-Zn), nickel-hydrogen (NiMH), lithium-ion (Li-ion), etc.), solar cells, and Fuel cells and more.

The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (eg, longitude and latitude) related to the current location of the WTRU 102. In addition to or instead of the information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) via the air interface 116, and / or based on information from two or more nearby base stations Received signal timing to determine its location. It should be understood that while maintaining compliance with the embodiments, the WTRU 102 may use any suitable positioning method to obtain location information.

The processor 118 may also be coupled to other peripheral devices 138, where the peripheral devices may include one or more software and / or hardware modules that provide additional features, functions, and / or wired or wireless connections. For example, peripheral devices 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or video), a universal serial bus (USB) port, a vibration device, a TV transceiver, a hands-free headset, Bluetooth ® modules, FM radio units, digital music players, media players, video game console modules, Internet browsers, virtual reality and / or augmented reality (VR / AR) devices, and event tracking And so on. The peripheral device 138 may include one or more sensors, and the sensors may be one or more of the following: a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor Sensor, temperature sensor, time sensor, geographic location sensor, altimeter, light sensor, touch sensor, magnetometer, barometer, gesture sensor, biometric sensor, and / or humidity Sensor.

WTRU 102 may include a full-duplex radio device for which some or all signals are received or transmitted (eg, associated with specific sub-frames for UL (eg, for transmission) and downlink (eg, for reception)) It can be parallel and / or simultaneous. A full-duplex radio may include signal processing via hardware (such as a choke) or via a processor (such as a separate processor (not shown) or via processor 118) to reduce and / or substantially eliminate Interference Interference Management Unit. In an embodiment, the WTRU 102 may include a half-duplex radio that transmits and receives some or all signals (eg, associated with specific sub-frames for UL (eg, for transmission) or downlink (eg, for reception).

FIG. 1C is a system diagram showing the RAN 104 and the CN 106 according to the embodiment. As described herein, the RAN 104 may use E-UTRA radio technology on the air interface 116 to communicate with the WTRUs 102a, 102b, 102c. The RAN 104 can also communicate with the CN 106.

The RAN 104 may include eNodeBs 160a, 160b, 160c, however it should be understood that while maintaining compliance with embodiments, the RAN 104 may include any number of eNodeBs. Each eNodeB 160a, 160b, 160c may include one or more transceivers on the air interface 116 to communicate with the WTRUs 102a, 102b, 102c. In one embodiment, eNodeB 160a, 160b, 160c may implement MIMO technology. Thus, for example, eNodeB 160a may use multiple antennas to transmit and / or receive wireless signals to and from WTRU 102a.

Each eNodeB 160a, 160b, 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, etc. . As shown in FIG. 1C, the eNodeBs 160a, 160b, and 160c can communicate with each other through an X2 interface.

The CN 106 shown in FIG. 1C may include a mobility management entity (MME) 162, a service gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. Although each of the aforementioned elements is described as being part of the CN 106, it should be understood that any of these elements may be owned and / or operated by entities other than the CN operator.

The MME 162 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the S1 interface, and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, performing bearer activation / deactivation, and selecting specific service gateways during the initial connection of the WTRUs 102a, 102b, 102c, and so on. The MME 162 may also provide a control plane function for switching between the RAN 104 and other RANs (not shown) using other radio technologies such as GSM and / or WCDMA.

The SGW 164 may be connected to each eNodeB 160a, 160b, 160c in the RAN 104 via the S1 interface. SGW 164 can generally route and forward user data packets to / from WTRU 102a, 102b, 102c / user data packets from WTRU 102a, 102b, 102c. SGW 164 can perform other functions, such as anchoring the user plane during handover between eNBs, triggering paging when DL data is available to WTRU 102a, 102b, 102c, and managing and storing the context of WTRU 102a, 102b, 102c, etc. .

SGW 164 can be connected to PGW 166, which can provide WTRU 102a, 102b, 102c access to a packet-switched network (such as Internet 110) to facilitate WTRU 102a, 102b, 102c and IP-enabled devices Communication.

CN 106 can facilitate communication with other networks. For example, the CN 106 may provide circuit-switched network (such as PSTN 108) access to the WTRUs 102a, 102b, and 102c to facilitate communication between the WTRUs 102a, 102b, and 102c and traditional landline communications devices. For example, the CN 106 may include or communicate with an IP gateway, such as an IP Multimedia Subsystem (IMS) server, and the IP gateway may serve as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, where the network 112 may include other wired and / or wireless networks owned and / or operated by other service providers.

Although the WTRU is described as a wireless terminal in Figures 1A to 1D, it should be thought that in some typical embodiments, such terminals can use (eg, temporarily or permanently) wired communication with a communication network interface.

In a typical embodiment, the other network 112 may be a WLAN.

A WLAN adopting the infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STA) associated with the AP. The AP can access or interface to a decentralized system (DS) or another type of wired / wireless network that carries traffic in and / or out of the BSS. Traffic originating outside the BSS and to the STA can arrive via the AP and be delivered to the STA. Traffic originating from STAs and to destinations outside the BSS can be sent to APs for delivery to their respective destinations. The traffic between STAs within the BSS can be sent via the AP, for example where the source STA can send traffic to the AP and the AP can deliver the traffic to the destination STA. Traffic between STAs within a BSS may be considered and / or referred to as point-to-point traffic. The point-to-point traffic can be sent between the source and destination STAs (eg, directly between them) using direct link setup (DLS). In some typical embodiments, the DLS may use 802.11e DLS or 802.11z Tunneled DLS (TDLS). The WLAN using the independent BSS (IBSS) mode may not have an AP, and STAs (for example, all STAs) within the IBSS or using the IBSS can directly communicate with each other. Here, the IBSS communication mode may sometimes be referred to as an "ad-hoc" communication mode.

When using the 802.11ac infrastructure operating mode or a similar operating mode, the AP can transmit beacons on a fixed channel, such as the main channel. The main channel can have a fixed width (for example, a bandwidth of 20 MHz) or a width that can be dynamically set through signaling. The main channel can be the operating channel of the BSS and can be used by the STA to establish a connection with the AP. In some typical embodiments (eg, in an 802.11 system) carrier sense multiple access (CSMA / CA) with collision avoidance may be implemented. For CSMA / CA, STAs that include APs (such as each STA) can sense the main channel. If a specific STA senses / detects and / or determines that the main channel is busy, then the specific STA may fall back. In a given BSS, a STA (for example, only one station) can transmit at any given time.

High Throughput (HT) STAs can use 40 MHz wide channels for communication (eg, by combining a 20 MHz wide main channel with 20 MHz wide adjacent or non-adjacent channels to form a 40 MHz wide channel).

Very High Throughput (VHT) STAs can support 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. The 40 MHz and / or 80 MHz channels can be formed by combining consecutive 20 MHz channels. A 160 MHz channel can be formed by combining eight consecutive 20 MHz channels or by combining two discrete 80 MHz channels (this combination can be referred to as an 80 + 80 configuration). For the 80 + 80 configuration, after channel encoding, the data can be passed and passed through a segmented parser, which can split the data into two streams. Inverse fast Fourier transform (IFFT) processing and time domain processing can be performed separately on each stream. The stream can be mapped on two 80 MHz channels and the data can be transmitted by a transmitting STA. On a receiver of a receiving STA, the operations described herein for 80 + 80 configuration may be reversed, and the combined data may be sent to a media access control (MAC).

802.11af and 802.11ah support sub-1 GHz operation modes. Compared with the channel operating bandwidth and carrier in 802.11n and 802.11ac, the channel operating bandwidth and carrier used in 802.11af and 802.11ah are reduced. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to typical embodiments, 802.11ah may support meter type control / machine type communication, such as MTC devices in a macro coverage area. MTC may have certain capabilities, such as limited capabilities that include support (eg, support only) certain and / or limited bandwidth. The MTC device may include a battery, and the battery life of the battery is above a critical value (for example, to maintain a long battery life).

WLAN systems that can support multiple channels and channel bandwidth (for example, 802.11n, 802.11ac, 802.11af, and 802.11ah) include channels that can be designated as the primary channel. The main channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the main channel may be set and / or limited by STAs among all STAs operating in a BSS that supports the minimum bandwidth operation mode. In the 802.11ah example, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operation modes, but for STAs that support (for example, only support 1 MHz mode) (Eg MTC type devices), the main channel can be 1 MHz wide. Carrier sensing and / or network allocation vector (NAV) settings can depend on the status of the primary channel. If the main channel is busy (for example, because STAs (eg, STAs in 1 MHz operation mode) transmit APs), then even if most of the frequency bands remain space and available, the entire available frequency band can be considered busy.

In the United States, the available frequency bands available for 802.11ah are from 902 MHz to 928 MHz. In South Korea, the available frequency band is from 917.5 MHz to 923.5 MHz. In Japan, the available frequency band is from 916.5 MHz to 927.5 MHz. According to the country code, the total bandwidth available for 802.11ah is from 6 MHz to 26 MHz.

FIG. 1D is a system diagram showing the RAN 113 and the CN 115 according to the embodiment. As described herein, the RAN 113 may use NR radio technology on the air interface 116 to communicate with the WTRUs 102a, 102b, 102c. The RAN 113 can also communicate with the CN 115.

RAN 113 may include gNBs 180a, 180b, 180c, but it should be understood that while maintaining compliance with embodiments, RAN 113 may include any number of gNBs. Each gNB 180a, 180b, 180c may include one or more transceivers to communicate with the WTRU 102a, 102b, 102c via the intermediary 116. In one embodiment, gNB 180a, 180b, 180c may implement MIMO technology. For example, gNB 180a, 180b may use a beamforming process to transmit and / or receive signals to and / or from gNB 180a, 180b, 180c. Thus, for example, gNB 180a may use multiple antennas to transmit and / or receive wireless signals to and from WTRU 102a. In an embodiment, the gNB 180a, 180b, 180c may implement a carrier aggregation technology. For example, gNB 180a may transmit multiple component carriers (not shown) to WTRU 102a. A subset of these component carriers may be on the unlicensed spectrum, while the remaining component carriers may be on the licensed spectrum. In an embodiment, gNB 180a, 180b, 180c may implement a Coordinated Multipoint (CoMP) technology. For example, WTRU 102a may receive cooperative transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

WTRUs 102a, 102b, 102c may use transmissions associated with scalable parameter configuration to communicate with gNB 180a, 180b, 180c. For example, for different transmissions, different cells, and / or different portions of the wireless transmission spectrum, the OFDM symbol spacing and / or OFDM subcarrier spacing may be different. WTRUs 102a, 102b, and 102c may use sub-frames or transmission time intervals (TTIs) with different or scalable lengths (for example, containing different numbers of OFDM symbols and / or continuously changing absolute time lengths) to communicate with gNB 180a, 180b , 180c for communication.

The gNBs 180a, 180b, 180c may be configured to communicate with WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a stand-alone configuration, WTRUs 102a, 102b, and 102c can communicate with gNB 180a, 180b, and 180c without access to other RANs (eg, eNodeB 160a, 160b, 160c). In a standalone configuration, WTRUs 102a, 102b, 102c may use one or more of gNB 180a, 180b, 180c as an action anchor. In a standalone configuration, WTRUs 102a, 102b, 102c may use signals in the unlicensed frequency band to communicate with gNB 180a, 180b, 180c. In a non-independent configuration, the WTRUs 102a, 102b, 102c may communicate / connect with the gNB 180a, 180b, 180c while communicating / connecting with another RAN (e.g., eNodeB 160a, 160b, 160c). For example, WTRUs 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more eNodeBs 160a, 160b, 160c substantially simultaneously. In a non-independent configuration, eNodeB 160a, 160b, 160c can act as an anchor for WTRU 102a, 102b, 102c, and gNB 180a, 180b, 180c can provide additional coverage and / or traffic to serve WTRU 102a, 102b, 102c.

Each gNB 180a, 180b, 180c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, support network interception Cut, implement dual connectivity, implement interworking between NR and E-UTRA, route user plane data to user plane functions (UPF) 184a, 184b, and route control plane information to access and mobility management functions (AMF ) 182a, 182b, etc. As shown in FIG. 1D, the gNBs 180a, 180b, and 180c can communicate with each other via an Xn interface.

The CN 115 shown in FIG. 1D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and may include a data network (DN) 185a, 185b. Although each of the aforementioned elements is described as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by entities other than the CN operator.

The AMF 182a, 182b may be connected to one or more of the RAN 113 gNB 180a, 180b, 180c via the N2 interface, and may serve as a control node. For example, AMF 182a, 182b can be responsible for verifying the users of WTRU 102a, 102b, 102c, supporting network truncation (such as processing different PDU conversations with different requirements), selecting specific SMF 183a, 183b, managing registration areas, terminating NAS Messaging and mobile management. AMF 182a, 1823b can use network truncation to customize the CN support provided to WTRU 102a, 102b, 102c based on the type of service used by WTRU 102a, 102b, 102c. For example, different network slices can be established for different use cases, such as services that rely on ultra-reliable low-latency (URLLC) access, rely on enhanced large-scale mobile broadband (eMBB) storage Access to services, and / or services for machine type communication (MTC) access, etc. AMF 162 may provide for switching between RAN 113 and other RANs (not shown) using other radio technologies (such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi) Control plane function.

The SMF 183a, 183b can be connected to the AMF 182a, 182b in the CN 115 via the N11 interface. SMF 183a, 183b can also be connected to UPF 184a, 184b in CN 115 via N4 interface. SMF 183a, 183b can select and control UPF 184a, 184b, and can configure traffic routing via UPF 184a, 184b. SMF 183a, 183b can perform other functions, such as managing and allocating UE IP addresses, managing PDU conversations, controlling policy implementation and QoS, and providing notification of downlink information, etc. PDU conversation types can be IP-based, non-IP-based, Ethernet-based, and so on.

UPF 184a, 184b can be connected to one or more of RAN 113 gNB 180a, 180b, 180c via the N3 interface, which can provide a packet switching network for WTRU 102a, 102b, 102c (such as Internet 110) Access to facilitate communication between WTRUs 102a, 102b, 102c and IP-enabled devices, UPF 184, 184b can perform other functions, such as routing and forwarding packets, implementing user plane policies, supporting multi-homed PDU conversations, Handle user plane QoS, buffer downlink packets, and provide mobile anchoring.

CN 115 can facilitate communication with other networks. For example, CN 115 may include or may communicate with an IP gateway (such as an IP Multimedia Subsystem (IMS) server) that acts as an interface between CN 115 and PSTN 108. In addition, CN 115 may provide WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, and 102c may be connected to the UPF 184a, 184b through the N3 interface and the N6 interface between the UPF 184a, 184b and the DN 185a, 185b, and connected to the UPF 184a, 184b. Local Data Network (DN) 185a, 185b.

In view of Figures 1A to 1D and the corresponding descriptions of Figures 1A to 1D, one or more or all functions described here with reference to one or more of the following may be performed by one or more simulation devices (not shown) ) To perform: WTRU 102a-d, base stations 114a-b, eNodeB 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b , DN 185 ab, and / or any other device (s) described herein. These simulation devices may be one or more devices configured to simulate one or more or all of the functions herein. For example, these simulated devices can be used to test other devices and / or simulate network and / or WTRU functions.

The simulation device may be designed to perform one or more tests on other devices in a laboratory environment and / or an operator network environment. For example, the one or more emulated devices may perform one or more or all functions while being implemented and / or deployed wholly or partially as part of a wired and / or wireless communication network to test other devices within the communication network. The one or more emulation devices may perform one or more or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The emulation device may be directly coupled to another device to perform the test, and / or may use air wireless communication to perform the test.

The one or more emulation devices may perform one or more functions including all functions while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device may be used in a test laboratory and / or a test scenario of a wired and / or wireless communication network that is not deployed (eg, tested) to perform testing of one or more components. The one or more simulation devices may be a test device. The simulation device may use direct RF coupling and / or wireless communication via an RF circuit (eg, the circuit may include one or more antennas) to transmit and / or receive data.

Processes for starting and deactivating side-link resource pools for communication between WTRUs, such as those described in connection with FIG. 1, are described herein. A WTRU may be configured with multiple side-link resource pools and may initiate one or more resource pools to communicate with other WTRUs. A resource pool can be defined in terms of one or more of: frequency (for example, one or more of a subcarrier, resource block, bandwidth portion, transmission band, etc.), time (for example, symbol, time slot, sub One or more of frame, periodicity, offset, etc.), code (for example, one or more of cyclic shift, orthogonal code, etc.), space (for example, beam, one or more preambles, etc.) Encoder, etc.), and / or any combination of time / frequency / code / spatial resources. The WTRU may use the resources indicated by the activated side-link resource pool (eg, resource blocks and time slots / subframes) to communicate directly with other WTRUs. The WTRU can autonomously and dynamically determine the activation and deactivation of the resource pool. For example, the WTRU may determine to initiate a resource pool suitable for transmitting and receiving the data based on the characteristics of the data it will send and / or receive. The WTRU may also determine to initiate a resource pool that is compatible with the resource pool being used by another WTRU based on the indication it received from the other WTRU. The WTRU may determine to start a particular resource pool based on the instructions, instructions, and / or communications it receives from the radio access network.

Direct device-to-device, or WTRU-to-WTRU communication can occur in the environment in which the vehicle operates. Vehicle-to-vehicle (V2V) and vehicle-to-everything (V2X) scenarios are envisaged in which a WTRU that can be associated with a vehicle can directly interact with other vehicles, infrastructure, people, and / or any other applicable items Associated other WTRU communications. V2X operation may occur during a coverage scenario (where the WTRU is within the coverage of the radio access network) and / or during an out-of-coverage scenario (where the WTRU is outside the coverage of the radio access network) occur. For example, in this coverage scenario, the WTRU may receive instructions from the network when transmitting and / or receiving V2X messages. In out-of-coverage scenarios, WTRUs outside the coverage of the radio access network can use pre-configured parameters when transmitting and receiving V2X messages.

V2X communication may involve many different communication pairs. V2X communication services may include, for example, one or more of the following: vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-network (V2N) communication, and vehicle-to-pedestrian (V2P) communication. Regarding V2V communication, vehicle WTRUs can communicate directly with each other. In V2I communication, a vehicle WTRU may communicate with a roadside unit (RSU) and / or a network eNB. In V2N communication, a vehicle WTRU may communicate with a network, which may be, for example, an LTE evolved packet core network. In V2P communication, a vehicle WTRU may communicate with one or more WTRUs that may have special conditions (eg, low battery capacity).

In LTE and / or NR processing, there may be two or more operation modes, and the WTRU may use these two or more operation modes to support V2X communication. For example, in the first mode, the network may provide the WTRU with a scheduling assignment for V2X side link transmission (for example, it may be referred to as mode 3 V2X communication). In the second mode, the WTRU may select (for example, may autonomously select) resources for side-link transmission from the configured / pre-configured resource pool (for example, may be referred to as mode 4 V2X communication).

LTE V2X processing can define one or more categories of resource pools (eg, two categories of resource pools). The resource pool category may include, for example, a V2X receiving pool and / or a V2X transmission pool. For example, a V2X receive pool can be used in monitoring receive V2X transmissions. The WTRU may use a V2X transmission pool to, for example, select transmission resources (eg, in mode 4). In an example, a WTRU configured in a network-scheduled D2D mode (eg, mode 3) may not use a transmission pool.

The resource pool used by the WTRU may be configured via messaging. Messaging can be performed semi-statically via Radio Resource Control (RRC) messaging. In mode 4, the WTRU may use sensing (eg, signal measurements such as RSRP measurements) before selecting resources from the RRC-configured transmission pool. In an example, the V2X resource pool configuration may be implemented via system information block (SIB) and / or dedicated RRC signaling, and / or the WTRU may be configured (eg, pre-configured) with a pool configuration.

V2X processing may be performed using a new radio (NR) communication system (for example, a 5G communication system). NR systems can support many use cases, such as enhanced mobile broadband (eMBB) and ultra-reliable low-latency communication (URLLC).

For scenarios such as sensor information sharing between V2X WTRUs and / or emergency trajectory alignment between V2X WTRUs, V2X performance goals may include a maximum end-to-end latency of 3 milliseconds (ms). End-to-end latency can be defined as the time it takes to transmit a given piece of information from the source to the destination. End-to-end latency can be measured at the application level (for example, from the moment the source application transmits information to the moment the destination application receives the information). In the physical layer, retransmission of transmission blocks (for example, the same transmission block) can be used to increase the reliability and / or coverage of V2X transmission. When performing retransmissions, more time resource opportunities within the 3ms window can be used. V2X LTE may not support ultra-low latency requirements.

Can support V2X communication in various scenarios. For example, V2X can be used for coverage scenarios (for example, in the eNB / gNB coverage that supports DL and UL transmissions). Supports V2X on frequency bands shared with non-V2X traffic. If V2X is supported on a frequency band shared with non-V2X traffic, allocating V2X resources (eg, to meet latency requirements) may become challenging and / or inefficient.

Frequency division multiplexing (FDM) can be used to support V2X communications. For example, the network may reserve frequency resource blocks for V2X transmissions, while other frequency blocks are reserved for other transmissions. Figure 2 shows a diagram of an exemplary frequency division multiplexing technique. The frequency resources may correspond to, for example, different physical resource blocks (PRB), different bandwidth portions (BWP), different carriers, and the like.

When trying to use frequency division multiplexing to provide V2X communication, spectrum efficiency can be considered. For example, ultra-low-latency V2X communications may be transmitted in bursts (eg, emergency trajectory alignment between V2X WTRUs), and reserved resources may not be used in each transmission opportunity (eg, may be discontinuously used). The network can operate in mode 3, in which case the network can know if the uplink (UL) resource is allocated to a non-V2X WTRU. If the network is operating in mode 3, the network can manage WTRUs in mode 3 (eg, all WTRUs in mode 3). For example, during high-traffic scenarios, the management of WTRUs in Mode 3 may increase complexity as the number of devices that may occur increases, for example. This increase in complexity can be applied (for example, also) to situations outside of coverage. Techniques can be implemented to reduce the amount of low-latency dedicated resources in a pre-configured pool.

Time division duplexing (TDD) can be used to support V2X communications. In TDD, the resource pool group used for V2X communication can be restricted. For example, a set of resource pools can be limited to an uplink (UL) time slot (for example, because V2X transmissions can use uplink resources). Referring to FIG. 3, a V2X WTRU may have ultra-low latency traffic, which may be scheduled for transmission in period n (eg, subframe n). But subframe n may be dedicated to downlink (DL) transmission, and the WTRU may not be able to transmit traffic before subframe n + 4 for UL. Delays in transmitting traffic can be attributed to semi-static resource allocation and / or operating modes. Note that the time-sharing example disclosed here can be presented by way of example in terms of sub-frame allocation or pooling, but it is also expected to be divided by other types of time units (eg, symbols, time slots, transmission time intervals, etc.) Time. Therefore, the examples described herein regarding the sub-frame time interval can be equally applied to other time units such as time slots, and these examples are not meant to be limited to sub-frame based timing.

V2X communication can be supported using side-link resource pool reconfiguration including activation and / or deactivation. Resource pool reconfiguration can be performed dynamically.

The WTRU may be configured with one or more sets of side-link receive / transmit resource pools (RPs). The resource pool defines resources that can be used to receive / transmit control information and / or data on the side link channel. A set (eg, each set) of side-link receive / transmit resource pools can be associated with one or more of the following: time slot format; modes in the time domain that include time slots with the configured time slot format Slot; configuration period; component carrier (CC); bandwidth portion (BWP); path loss gNB-WTRU or RSU-WTRU; and / or beam configuration.

Regarding the slot format for the receive / transmit resource pool, the WTRU may associate a set of receive resource pools with a slot format (for example, a single slot format), or associate multiple sets of receive resource pools with a slot format (for example, , Single slot format). The side link slot format may include a symbol indicating a side link transmission or reception. The side link slot format may include one or more symbols for each slot. Indicate that the symbols used for side-link transmission or reception may be reconfigured (eg, dynamically reconfigured).

For modes in the time domain that include the time slot of the configured time slot format, the WTRU may be configured with a receive resource pool, which may include a repeating side chain for sub-frames (eg, each sub-frame) Time slot configuration. The WTRU may be configured with a receiving pool having a changed time slot configuration for sub-frames (eg, each sub-frame).

Regarding the configuration cycle associated with the resource pool, the configured time domain mode can be repeated. For example, the configured time domain can be repeated during the configuration period.

FIG. 4 shows an exemplary configuration of a side link receive / transmit resource pool in the time domain. The WTRU may be configured with one or more receiving resource pools, which may have different numbers of side-link receiving time slots. For example, the WTRU may be configured with one or more of the following: a receiving resource pool with a large allocation for a side link reception time slot; and / or a small allocation with a small allocation for a side link reception time slot Receive resource pool.

Referring to FIG. 4, an exemplary receiving resource pool having a large number of allocations for a side link receiving time slot is shown in the resource pool 1. For example, when receiving data that requires low latency and / or high throughput, the WTRU may be configured with a heavily allocated receive resource pool for side-link receive time slots.

An exemplary resource pool with relatively few allocations for time slots for side link reception is shown in resource pool 2 of FIG. 4. For example, when receiving data associated with relatively low-throughput applications and / or with more conventional data traffic, the WTRU may be configured with a receiving resource pool having a relatively small number of receiving time slots.

The WTRU may be configured with one or more receive / transmit resource pools. The resource pool may include a side link slot (s) (for example, a set of side link slots) and / or a side link symbol (s) (for example, a set of side link symbols) . The side link symbol (s) (eg, a side link symbol group) may include NR variable symbols. For example, as shown in Figure 5, a WTRU may be configured to contain N time slots for side link transmission / reception and M time slots for side link transmission / reception (which may include K _M (For example, only K _M symbols)). The slots / symbol groups within the resource pool may be continuous in time and / or distributed across different NR slots / symbols (eg, non-contiguous). An exemplary configuration may include a first bit image and a second bit image, the first bit image may indicate a set of time slots for side link transmission / reception, and the second bit image may indicate that the The side-link symbol in the time slot indicated by the bitmap.

The WTRU may determine the resource pool (s) that should be activated / deactivated for side link reception / transmission. The WTRU may make this determination in any number of ways, including, for example: autonomous processing based on the WTRU; based on explicit and / or implicit messaging from another WTRU; and / or based on explicit and / or implicit messaging from the network. The WTRU may start a side-link resource pool by identifying or considering resources specified in the resource pool by the WTRU for side-link communication in a manner specified in the resource pool.

The WTRU may be configured (eg, semi-statically configured) with a set of receive / transmit resource pools. The WTRU determines which side link resource pool should be enabled and / or disabled for the upcoming V2X or enhanced V2X (eV2X) transmission. The WTRU may autonomously determine the side-link resource pool to be activated / deactivated based on, for example, various system information and / or data requirements or characteristics. The WTRU may determine the side link resource pool to be activated / deactivated based on the received indication. For example, a resource pool indication (RPI) may be received from another WTRU or from the RAN network to provide a dynamic indication of the resource pool to be activated / deactivated. The dynamic indication may be implicit or explicit.

The WTRU may receive an indication (eg, RPI) from a network (which may be, for example, a radio access network) indicating a reconfiguration (including activation and / or deactivation) of a side-link resource pool. The indication may be explicit or implicit. For example, the WTRU may be configured to monitor NR downlink control information (DCI), which may carry a side link resource pool indicator (RPI). The WTRU may be configured (eg, pre-configured) with a monitoring period and / or a radio network temporary identifier (RNTI) for decoding DCI. The WTRU may receive (eg, may receive in broadcast system information) a set of DCI monitoring parameters. For example, the WTRU may receive the corresponding CORESET and / or search space in the remaining system information (RMSI) or other system information (OSI). For example, when an RRC connection is established, the WTRU may receive a monitoring configuration for RPI in a radio resource control (RRC) messaging.

The WTRU may receive an indication of the side-link resource pool to be used via a low-cost signal (eg, a predefined sequence such as Zadoff-Chu).

The WTRU may receive a MAC control element, which may indicate to the WTRU the initiating side link resource pool.

In an exemplary process for side link resource reconfiguration, the WTRU may receive the side link resource pool group configuration in the system broadcast information and / or RRC signaling information. The WTRU may receive a MAC CE indicating that one or more resource pools are started from the group. For example, the MAC CE may indicate that one or more resource pools from the group are preset side link resource pools.

The WTRU may monitor the RPI DCI based on the network configuration (eg, including the monitoring period). The RPI DCI may be associated with an RPI timer. The RPI timer may include a configured length (eg, the length is an integer multiple of the monitoring period). When the RPI timer runs, the WTRU may consider the pool to be active.

Depending on any suitable criteria, the WTRU may revert to a side link (eg, a preset side link) resource pool configuration. For example, the WTRU may revert to a preset side link resource pool when one or more of the following apply: the RPI timer expires; the WTRU does not detect another RPI DCI at the RPI monitoring timing; and / or the WTRU Side link messages have not been received in a dynamically started resource pool for a period of time (eg, a configured period of time).

The WTRU may reconfigure the side link resource pool based on the received side link resource pool indication, for example, starting and / or deactivating a resource pool in the set of resource pools. This reconfiguration may allow the WTRU to allocate time slots when appropriate. For example, the reconfiguration may start a side link resource pool that specifies, for example, more side link reception time slots that may be useful during side link operation of a low-latency application. This reconfiguration can change the allocation between NR downlink (DL) and uplink (UL) time slots and / or side link time slots.

The WTRU may receive a DCI, which may include an indication of changing a side link slot format of a side link resource pool, which may be, for example, an active side link resource pool. For example, as shown in Figure 4, the WTRU may reconfigure the side link transmission time slot to the same side link reception time slot as the side link reception time slot configured for the resource pool. The side-link time slot assignments can be consistent.

The resource pool indication (RPI) for side-link resource pool (RP) reconfiguration including activation / deactivation may be implicitly determined by the WTRU and / or may be implicitly indicated by the network (eg, RAN) . The WTRU may receive an indication from the network, which may be interpreted by the WTRU as an implicit indication of a resource pool indication. For example, the WTRU may determine an applicable resource pool based on one or more of the following configuration parameters: a PDCCH (eg, a group common PDCCH carrying a slot format indicator (SFI)); a change in beam configuration (eg, Dynamic beam configuration); bandwidth portion enable / disable (e.g., dynamic bandwidth portion enable / disable), etc. Regarding the implicit indication based on the PDCCH signal, for example, the WTRU may be configured to map the SFI index to a resource pool configuration. The WTRU may monitor the SFI to determine DL symbols, variable symbols, and / or UL symbols. The WTRU may then determine to use a set of UL symbols for side-link transmissions, which may be based on the resource pool to SFI mapping.

The WTRU may determine the side link resource pool based on the association between one or more of the above configuration parameters and the configured side link resource pool. For example, different resource pools may be configured / associated with different bandwidth portions, and a change in the bandwidth portion may be an implicit indication that the resource pool is also changed. In an example, different resource pools may be configured / associated with different beam configurations, and a change in beam configuration may be an implicit indication that the resource pool is also changed.

A WTRU may communicate via a side link to receive an explicit resource pool indication from another WTRU. The resource pool indicator for the activation / deactivation of the side link resource pool can be explicitly signaled via the side link data and / or the control channel. For example, explicit resource pool indications may be carried in a side link control information (SCI) format (eg, a special SCI format) and / or broadcast (eg, via side link system information and / or via a separate physical channel) Being broadcast). This RPI may be transmitted via a resource pool (eg, via one active resource pool in a group of active resource pools). For example, the WTRU may be configured to monitor a resource pool for the RPI. The RPI may be transmitted on a resource, which may be, for example, a fixed time / frequency resource.

The WTRU may determine that an implicit resource pool indication has been received from another WTRU via a side link communication. A resource pool indicator for side link resource pool activation / deactivation (eg, reconfiguration) may be implicitly indicated based on one or more side link communications. The WTRU may change its active resource pool based on the reception of the side link data, which is determined to be an implicit indication of the side link pool being reconfigured to start and deactivate. For example, the side link information may be received from another WTRU. Changes to the active resource pool and the disabled resource pool can be triggered by receiving control messages and / or data messages. The control message and / or data message may be sent by the WTRU to another WTRU via a side link. A change in a resource pool may be triggered by receiving a transmission on a specific resource (eg, time and / or frequency) in a resource pool (eg, a resource pool dedicated to such an active pool change). A change in the resource pool may be triggered by receiving a control message indicating a side-link data channel for transmission (eg, transmission via a pre-configured RP, which may not be active). Upon receiving the side link data, the WTRU may determine that the data implicitly indicates that one or more resource pools are activated and / or another one or more resource pools are deactivated.

The WTRU may autonomously determine to reconfigure (eg, activate and / or deactivate) the side link resource pool. In an exemplary process for autonomous resource pool determination, the WTRU may be configured with side-link resource pool resources that may be associated with a set of packet priorities. The association may be based on, for example, one or more of a side-link transmission service type, reliability, latency requirements, and the like. The WTRU may be configured to autonomously select and activate and / or deactivate side-link resource pool resources for side-link transmission / or reception. The selection and activation / deactivation and / or reconfiguration may be based on, for example, one or more of the following: a higher layer (e.g., communication layer) of the WTRU may have side-link packets for transmission and / or reception, with The associated priority order is higher than the priority order associated with the currently applied side-link resource pool configuration (including the currently activated resource pool); the higher layers (for example, the communication layer) of the WTRU may have SL packets. The link resource pool configuration (including the currently started resource pool) may not support, for example, the transmission latency required for this SL packet; the WTRU may receive from another WTRU a side link resource pool configuration (including the currently started Resource pool) associated high-priority packets; measurement results (eg, determined by the WTRU); sensing results (eg, determined by the WTRU); and / or, the currently started resource pool does not support the intended use Quality of service characteristics of side-link communication. The WTRU may be configured to determine that the initiated side link pool is not suitable for a particular profile and / or the requirements associated with that profile, and may identify one or more other side link resource pools that are suitable. The WTRU initiates the appropriate side link pool (s) and may transmit activation instructions regarding the side link pool to other WTRUs and / or radio access networks.

Regarding the determination of autonomous resource pools based on data packet characteristics or requirements (for example, higher priority or lower latency), the currently activated resource pool may not support data characteristics or requirements. Regarding the data packet priority example, higher priority packets can be received in any number of cases. For example, the WTRU may receive side-link messages with enhanced priority, such as side-link emergency messages, which may need to be relayed to other WTRUs. In an example, the WTRU may receive an SCI message, which may indicate a relatively high priority, for example, a priority associated with a low-latency packet transmission. Based on the priority of the data that needs to be transmitted (which can be identified by the required latency), the WTRU can determine that the resource pool started is not suitable for the data, and can choose to start a suitable side-link resource pool and which one can have more Many side-link resources, for example, have more UL symbols and / or more flexible symbols in the time domain than currently activated resource pools. The WTRU may start the selected resource pool (s) and use the started resource pool (s) to transfer data. As described herein, the WTRU may pass the initiation of the side-link resource pool to other WTRUs and / or RANs.

Regarding the autonomous resource pool determination based on the measurement results, the WTRU may be configured to perform a measurement, and depending on the measurement, may autonomously determine a resource pool for reconfiguration activation / deactivation. For example, the WTRU may be configured to sense or measure energy on a set of resource pools (eg, for a pre-configured duration). If the measured energy is above a critical value, the WTRU may start one or more resource pools (eg, one or more additional resource pools). As another example, a WTRU may be configured to measure a channel busy ratio (CBR) on one or more resource pools (eg, a set of resource pools). The WTRU can compare this CBR with a threshold. For example, the WTRU may determine whether the CBR is above or below a critical value. If the WTRU determines that the CBR is above a critical value, the WTRU may start the selected resource pool (s) and use the started resource pool (s) to transfer data.

When the WTRU is configured to select (for example, autonomously reselect) based on the sensing results to enable / disable and / or reconfigure the side link resource pool resources for side link transmission and / or reception, the following can be applied: One or more of them. The WTRU may be configured to start one or more resource pools (eg, one or more additional resource pools). The WTRU may determine the number of WTRUs that use a set of resource pool (s) (eg, within the range of Side-Link Reference Signal Received Power (S-RSRP)). The WTRU may compare the number of WTRUs using a set of resource pools with a critical value. If the number of WTRUs using a set of resource pools within the configured S-RSPR range is above a critical value, the WTRU may start a suitable set of resource pools, which may be an additional set of resource pools. The WTRU may use the activated side link pool (s) to transmit side link packets.

When the WTRU is configured to select (eg, autonomously select or reselect) based on the QoS characteristic (s) for activation / deactivation and / or reconfiguration of the side chain for side link transmission and / or reception You can apply one or more of the following resource pool resources. For example, the higher layers of the WTRU may initiate the transmission of side-link packets with QoS characteristics (eg, V2X QoS Index (VQI) parameters). The currently activated resource pool (s) may or may not support this QoS feature. The WTRU may be configured with VQI parameters and mapping rules between resource pools. The WTRU may use the mapping rule to determine whether the currently activated resource pool (s) support the QoS feature. The WTRU may use this mapping rule to select a resource pool that can support the QoS characteristics for the transmission side link packet. The WTRU may start the selected resource pool and use it to transmit side link packets. The WTRU may also send an indication to one or more other WTRUs that it has activated a particular side link resource pool.

The WTRU may use the active side link resource pool to send a resource pool indication (RPI) on the side link channel. For example, after autonomously starting a resource pool, the WTRU may send the RPI of the started resource pool to other WTRUs. While sending the RPI indicating the start of the new resource pool, the WTRU may transmit side-link packets on a set of started resource pool (s). The WTRU may be configured with a resource pool to send the RPI to other WTRUs. The WTRU may send the RPI and then switch to the initiated resource pool. The WTRU can transmit data on the activated resource pool and transmit the RPI at the same time.

The WTRU may be configured to indicate to the network and / or other WTRUs the resource pool group that was started. For example, after autonomously starting one or more side-link resource pools, the WTRU may indicate the group of active resource pools after autonomously starting and / or deactivating the resource pools. The indication may be transmitted using a side link control information (SCI) message, which may include, for example, one or more RPIs.

The WTRU may be configured (eg, may be configured by the NW) to enable and / or disable autonomous side link resource pool reconfiguration. The WTRU may be configured (eg, by the NW) with a subset of allowable pool configurations that the WTRU may use for autonomous reconfiguration.

The WTRU may perform processing after receiving the RPI. For example, upon receiving an RPI from, for example, another WTRU or from the network, the WTRU may initiate a pre-configured pool indicated in the RPI. The process of starting a side link resource pool may include the WTRU identifying or considering that resources specified in the resource pool are available for performing side link communication. Deactivating a side link resource may involve the WTRU identifying or considering that resources specified in a particular resource pool are not available for communication.

The RPI may be received in any suitable manner, such as a broadcast control message. The WTRU may be configured to perform processing for activating / deactivating resources and / or resource pools based on receipt of RPI via, for example, broadcast control messages. For example, when the WTRU receives a start command for a pool with a specific class or classification (for example, a type of resource pool that can be associated with certain delay characteristics)-it can be designated as a class A for explanation purposes-the WTRU can be Configure to deactivate one or more active pools (for example, all active pools) with lower classes (for example, B, C, etc.). The WTRU may be configured to restart a previously active resource pool (eg, class B, class C, etc.) based on the resource pool (s) started for class A becoming deactivated. In an example, the WTRU may be configured to avoid starting a resource pool of a lower class unless and / or until a resource pool of a higher class has been deactivated. The activation and deactivation of the side link resource pool may be performed in response to receiving an RPI from another WTRU and / or from a network device.

The WTRU may be configured with one or more dedicated resources in a side-link resource pool. This dedicated resource can be used for implicit activation / deactivation of other resource pools. For example, when a WTRU detects a side-link transmission on a dedicated resource, the WTRU may use the processing techniques described herein to perform activation / deactivation of other resource pools.

The WTRU may transmit the RPI to other WTRUs (eg, via a side link). The WTRU may be configured to broadcast control messages via a side link to perform resource pool selection, or otherwise indicate RPI. For example, a WTRU may broadcast a control message / RPI when one or more of the following occurs: a low-latency service is started; an instruction is received from an upper layer to perform such a control message transmission; a side link bearer (for example, Some low-latency characteristics) are established; and / or receive data from the network and / or from another WTRU (eg, in the case of a relay) (eg, have certain low-latency characteristics). The broadcast control message may include one or more of the following information: an indication (for example, in the form of an index) of a resource pool configuration (for example, a specific pool configuration) for activation / deactivation; and / or for activation Indication of a type of resource pool configuration for deactivation / deactivation. The WTRU may already be configured (for example, by RRC messages) to have a set of pools, and the pool (for example, each pool) may be associated with one or more categories. A message (eg, a broadcast control message) received by the WTRU may indicate the activation and / or deactivation of a pool associated with a particular category.

The WTRU may use a resource pool (eg, a common resource pool) to transmit RPI. This resource pool (eg, a common resource pool) may or may not be subject to dynamic reconfiguration.

The WTRU may be configured with side-link semi-persistent scheduling (SPS) resources, which may be used for side-link transmissions. The SPS resource may correspond to a group of one or more transmission resources that are periodically reserved or dedicated to a particular WTRU. For example, SPS allocation may be related to period, sub-frame offset, symbol offset, resource block (or sub-resource block) assignment, and / or other settings that allow the WTRU to transmit and / or receive in the resource pool in a periodic manner. Associated. The WTRU may be configured to monitor resource reconfiguration (eg, dynamic resource reconfiguration). For example, when receiving the dynamic resource reconfiguration, the WTRU may stop transmitting on a semi-persistently configured grant. The WTRU may be configured with a set of authorizations, which may be applied in different resource pools depending on dynamic resource reconfiguration. For example, the WTRU may be pre-configured with N resource pools (one or more). Individual SPS authorizations can be associated with each pre-configured resource pool. If the network dynamically changes the resource pool, the WTRU may implicitly determine the SPS authorization to apply.

The WTRU may request a resource pool reconfiguration (for example, request the network to perform a resource pool reconfiguration). This request can be used for side-link resource pool reconfiguration. The WTRU may be configured with an on-chain resource, which may be used to request a resource pool reconfiguration. For example, the WTRU may be configured with a PUCCH resource, which may carry uplink control information (UCI). The UCI may request reconfiguration of the side link resource pool. The WTRU may indicate (eg, indicated in UCI) a side link resource pool (eg, a better side link resource pool). The WTRU may be configured with a scheduling request (SR) resource, which may be used to request (eg, implicitly request) a side link resource pool reconfiguration. A WTRU may be configured with one or more SR resources, which may be associated with one or more side-link resource pool configurations (eg, each SR resource may be associated with it). For example, a WTRU may be configured with one or more (eg, two) different SR resources. The SR resources (for example, each of the SR resources) may correspond to different side link resource pool configurations (for example, two different RP configurations). The WTRU may be configured to request side-link resource pool reconfiguration based on one or more of the following: side-link measurement, sensing, geographic location, side-link packet service type, side-link packet priority, and so on.

Side link channel processing can be used to support a variety of services, including, for example, ultra-reliable low latency communication (URLLC) services. For example, one or more side link channel structures may be provided for the URLLC service. The WTRU may be configured with one or more physical side link control channel (PSCCH) and / or physical side link shared channel (PSSCH) structures. The PSCCH and / or PSSCH structure can carry different types of side link control information / side link data. For example, the first PSCCH structure may schedule ultra-reliable low-latency (URLLC) traffic, and / or the second PSCCH structure may schedule other traffic (eg, non-URLLC traffic). The PSCCH structure for URLLC may have a small relative duration (eg, one symbol duration) and / or a large frequency domain allocation. For example, PSCCH (eg, non-URLLC traffic) for other traffic may be allocated across time slots (eg, the entire time slot) and / or smaller frequency domains.

The URLLC PSCCH and PSSCH may be multiplexed in the frequency domain and may, for example, be at the same symbol position. The WTRU may decode PSCCH and / or PSSCH that are very close to each other (eg, at the same symbol). The WTRU may receive a PSSCH timing indication via, for example, a PSCCH transmission, and the timing indication may depend on one or more side link transmission parameters, such as parameter configuration BWP and / or WTRU capabilities.

The WTRU may receive a resource pool indication (RPI) to reconfigure one or more variable symbols, which may be, for example, variable symbols used for side-link URLLC transmissions. This reconfiguration may trigger the WTRU to monitor one or more SCIs (eg, a set of SCIs). The SCI may be specific to URLLC transmissions on reconfigured symbols, and / or may have a shorter monitoring period. For example, the WTRU may monitor the SCI of URLLC traffic at every symbol and / or every two symbols, while for non-URLLC transmissions, this monitoring may be less frequent.

The resource pool configuration received from the network may include an indication in the SCI format and / or an indication in the PSSCH format, which may be used for transmission / reception using the resource pool. The WTRU may monitor the SCI and / or decode the PSSCH based on a format that may be associated with a resource pool (eg, different SCI formats may be expected to be used for different resource pools). The WTRU may be configured (eg, may also be configured) with one or more SCIs and / or one or more PSSCH formats for the pool. The WTRU may monitor the receiving pool (RX pool) and / or transmission pool (TX) based on one or more of the SCI / PSSCH configurations that may be associated with the receiving pool (RX pool) and / or transmission pool (TX pool). Pool).

A WTRU operating on the URLLC service may first occupy the side link SPS transmission. A WTRU may be configured to preempt a side-link SPS grant from another WTRU. For example, the WTRU may be configured to determine SPS authorizations used by other WTRUs. For example, a WTRU may be configured to determine the SPS authorization used by other WTRUs by decoding the SCIs of other WTRUs. The WTRU may determine (eg, then may determine) SPS resources (eg, target SPS resources) based on one or more of the following: the priority indicated in the SCI of the SPS authorization of the target WTRU; the SPS of the target WTRU authorized Transmission opportunities (eg, delay requirements relative to the data to be transmitted); measured reference signal received power (RSRP) of the PSCCH carrying the SCI of the target WTRU; and / or WTRU's packet priority.

The WTRU may be configured with a side link SPS, which may support URLLC service preemption. A WTRU configured with SL SPS resources may be configured to monitor the SCI of the URLLC WTRU, which may be used to determine whether a preemption of SPS resources for the WTRU has occurred. This monitoring can be applied to certain WTRUs and / or certain transmissions. For example, the WTRU may be configured to monitor side-link SPS resources used for data transmission with a priority order below a certain threshold. The monitoring of the URLLC WTRU's SCI can be applied to a subset of resources in the resource pool (eg, the WTRU can monitor the SCI to preempt the SCI corresponding to the subset of resources in the RP). WTRUs configured with side-link SPS resources can monitor special or specific SCIs. The special or specific SCI may include a preemptive indication. For example, a WTRU configured with side-link SPS resources may not monitor side-link grants, but may monitor SCIs with preemptive indications. The resource allocation of the PSCCH carrying the special SCI can be determined based on the RP (re) configuration.

The WTRU may perform resource reselection. For example, a WTRU that uses mode 4 forward booking to perform transmission may perform resource reselection. For example, the WTRU may perform resource reselection when a preemption indication is detected by another WTRU. The WTRU may continue to use reselection resources and / or may perform blanking of symbols associated with the preemption transmission (eg, assuming that the preemption transmission uses the URLLC format SCI and PSSCH). The WTRU may be configured with a SCI transmission format and / or a PSSCH format. The SCI transmission format as well as the PSSCH format can be used for transmission (for example, in a resource preempted by URLLC transmission). For example, when pre-emption by URLLC has occurred, the WTRU may utilize the SCI transmission format and the PSSCH format on its pre-reserved resources.

WTRUs operating URLLC services may use UL resources of other WTRUs for transmission. The WTRU may be configured to preempt UL transmissions of other WTRUs, which may allow the WTRU to transmit side link packets. For example, the WTRU may be configured with an uplink resource that can be used for preemption. The WTRU may be configured with one or more resources, which may be used to transmit a preemption indication (eg, to the network). This preemption indication may be transmitted before the UL transmission of another WTRU is preempted. In this case, the network may send a message / signal (eg, "off" or "stop transmission" message / signal) to the preempted WTRU (eg, if the WTRU is authorized for those resources). The WTRU may send a preemption indication after preempting the UL resources (eg, so that the network can perform rate matching around those UL resources).

The WTRU operating the URLLC service can use its configuration / scheduled uplink authorization for side-link transmission. The WTRU may be configured to use its configured / scheduled uplink authorization for side-link transmissions, for example to reduce latency, which may be, for example, by requesting a buffer status report (BSR) of the side link resources Caused. For example, a WTRU may be configured / scheduled to have an uplink grant that may span one or more OFDM symbols (eg, x OFDM symbols as shown in Figure 6). As shown in Figure 6, the WTRU may be configured to use the first y symbols to send a preemption indication to the gNB and use the remaining (x-y) symbols for side-link transmission. For example, if the WTRU uses the authorization to multiplex the side link transmission and the uplink transmission, as shown in Figure 7, the preemption indication may carry rate matching information (for example, the Symbols and / or the number / location of RBs), this may allow the network to decode the multiplexed uplink transmission.

The priorities can be updated dynamically. For example, the priority of the active pool can be updated dynamically. The ProSe Priority (PPPP) per packet associated with the pool can be updated.

Therefore, this article describes the process for reconfiguring (including enabling and disabling) the side link resource pool. The WTRU may dynamically and autonomously determine to activate and / or deactivate the side link resource pool. For example, the WTRU may determine to initiate a resource pool suitable for transmitting and receiving the data based on the characteristics of the data it will send and / or receive. The WTRU may also determine to activate and / or deactivate the side link resources in response to the received indication, which may be a resource pool indication (RPI). This RPI may be received from the network (which may be a RAN) and / or from another WTRU. The RPI may be explicitly signaled and / or the WTRU may implicitly determine the indication based on one or more criteria. For example, the RPI may be clearly indicated in the downlink control information (DCI), and the WTRU may monitor the downlink control information on one or more downlink channels (for example, the downlink control channel). The indication may be implicitly indicated based on one or more of the following: a group public entity downlink control channel (PDCCH) carrying a time slot format indicator (SFI), dynamic changes in beam configuration, and / or dynamics Bandwidth is enabled / disabled.

It should be understood that although illustrative embodiments have been disclosed, the scope of potential embodiments is not limited to those explicitly set forth. For example, although the system has been described with reference to 3GPP and / or NR network layers, the contemplated embodiments are extended beyond implementations using specific network layer technologies. Similarly, potential implementations can be extended to all types of service layer architectures, systems, and embodiments. Although the illustrative embodiments relate to specific types of communication between specific types of devices, processing may be performed by and between any suitable devices. Although the examples described herein can be described with respect to V2X / eV2X communication, the techniques described herein can be equally applied to other types of communication. Although the transmission / reception of V2X messages is used as an example, the communication technology described here can be used to transmit / receive other types of data (the data is not a V2X message, or the data is other than V2X messages). The techniques described herein can be applied independently and / or used in combination with other resource allocation techniques.

It should be understood that the entity that performs the processes described herein may be a logical entity that may be used in the memory of a mobile device, network node, or computer system and processed in the mobile device, network node, or computer system Is implemented in the form of software (ie, computer executable instructions) running on a computer. That is, the method (s) may be in the form of software (ie, computer executable instructions) stored in the memory of a mobile device and / or network node (eg, a node or computer system) When implemented, the computer-executable instructions, when executed by a node's processor, perform the process in question. It should also be understood that any transmission and reception process shown in the figure may be performed by the node's communication circuit under the control of the node's processor and computer-executable instructions (eg, software) executed by the node.

The various techniques described herein may be implemented in conjunction with hardware or software, or where appropriate, a combination of the two. As such, the methods and devices of the subject matter described herein, or some aspects or portions thereof, may employ program code (i.e., floppy disks, CD-ROMs, hard drives, or any other machine-readable storage medium) , Instruction) in which the code becomes a device for practicing the subject matter of this document when the code is loaded into and executed by a machine such as a computer. Where the code is stored on a medium, it is possible that the code in question is stored on one or more media that collectively perform the action in question, that is, one or more media together contains A code to perform an action, but in the presence of multiple single media, it is not required to store any particular part of the code on any particular media. Where the program code is executed on a programmable device, the computing device typically includes a processor, a storage medium readable by the processor (including volatile and non-volatile memory and / or memory elements), at least one input device, And at least one output device. One or more programs may implement or utilize processes described in conjunction with the subject matter described herein, for example, through the use of APIs or reusable controls. These programs are preferably implemented in high-level procedures or object-oriented programming languages to communicate with computer systems. However, if desired, these programs (s) can be implemented in combinatorial or machine language. In any case, the language can be a compiled or interpreted language combined with a hardware implementation.

Although exemplary embodiments may mention utilizing aspects of the subject matter described herein in the context of one or more independent computing systems, the subject matter described herein is not limited thereto, but may be incorporated in any computing environment such as a network or Decentralized computing environment). Still further, aspects of the subject matter described herein may be implemented in or across multiple processing wafers or devices, and the storage may similarly be affected on multiple devices. These devices may include personal computers, web servers, handheld devices, supercomputers, or computers integrated into other systems such as cars and airplanes.

In describing preferred embodiments of the subject matter of the present disclosure, as shown in the figures, certain terminology is used for the sake of clarity. However, the claimed subject matter is not intended to be limited to the specific terminology so selected, and it is to be understood that each specific element includes all technical equivalents that operate in a similar manner to achieve a similar purpose.

Table 1 below provides a list of acronyms that may appear in this article.
Table 1

Although features and elements using specific combinations are described herein, those of ordinary skill in the art will recognize that each feature or element may be used alone or in any combination with other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), scratchpads, cache memory, semiconductor memory devices, magnetic media (for example, internal hard drives And removable magnetic disks), magneto-optical media, and optical media (such as CD-ROM discs and digital versatile discs (DVDs)). The processor associated with the software can be used to implement a radio frequency transceiver for a WTRU, UE, terminal, base station, RNC, or any host computer.

DL‧‧‧Unchain

OFDM‧‧‧ Orthogonal Frequency Division Multiplexing

N2, N3, N4, N6, N11, S1, X2, Xn‧‧‧ interfaces

NR‧‧‧New Radio

SL‧‧‧Side Link

TDD‧‧‧time division duplex

UL‧‧‧winding

V2X‧‧‧Vehicle communication

WTRU, 102, 102a, 102b, 102c, 102d ‧‧‧ wireless transmission / reception unit

100‧‧‧communication system

104, 113‧‧‧ Radio Access Network (RAN)

106 / 115‧‧‧ Core Network (CN)

108‧‧‧ Public Switched Telephone Network (PSTN)

110‧‧‧Internet

112‧‧‧Other networks

114a, 114b‧‧‧ base station

116‧‧‧ air interface

118‧‧‧Processor

120‧‧‧ Transceiver

122‧‧‧Transmit / Receive Element

124‧‧‧Speaker / Microphone

126‧‧‧Keyboard

128‧‧‧Display / Touchpad

130‧‧‧non-removable memory

132‧‧‧ Removable memory

134‧‧‧Power

136‧‧‧Global Positioning System (GPS) Chipset

138‧‧‧Peripheral equipment

160a, 160b, 160c‧‧‧e Node B

162‧‧‧Mobile Management Entity (MME)

164‧‧‧Service Gateway (SGW)

166‧‧‧ Packet Data Network (PDN) Gateway (or PGW)

180a, 180b, 180c‧‧‧gNB

182a, 182b‧‧‧ access and mobile management functions (AMF)

183a, 183b‧‧‧ Dialogue Management Function (SMF)

184a, 184b ‧‧‧ User Plane Function (UPF)

185a, 185b‧‧‧ Data Network (DN)

The foregoing summary of the invention and the following additional descriptions of illustrative embodiments may be better understood when read in conjunction with the accompanying exemplary drawings. It should be understood that the potential embodiments of the disclosed systems and methods are not limited to those depicted. The same element symbols in the drawings represent the same elements.

FIG. 1A is a system diagram illustrating an exemplary communication system in which one or more disclosed embodiments may be implemented.

FIG. 1B is a system diagram illustrating an exemplary wireless transmission / reception unit (WTRU) that can be used within the communication system shown in FIG. 1A according to an embodiment.

FIG. 1C is a system diagram showing an exemplary radio access network (RAN) and an exemplary core network (CN) that can be used in the communication system shown in FIG. 1A according to an embodiment.

FIG. 1D is a system diagram illustrating another exemplary RAN and another exemplary CN that can be used in the communication system illustrated in FIG. 1A according to an embodiment.

FIG. 2 is a diagram showing an exemplary frequency multiplexing in a time domain duplex (TDD) mode.

FIG. 3 is a diagram showing an exemplary delay added by an exemplary TDD configuration.

FIG. 4 is a diagram showing an exemplary side link time domain resource pool configuration.

FIG. 5 is a diagram showing an exemplary time slot and symbol resource pool configuration for a side link.

Fig. 6 is a diagram showing an exemplary use of uplink authorization in side-link transmission.

FIG. 7 is a diagram illustrating an exemplary use of uplink authorization for multiplex side links and uplink transmission.

Claims (20)

A method for starting a side-link resource pool implemented by a wireless transmission and reception unit (WTRU), the method includes: A WTRU uses a started first side link resource pool for side link communication. The first side link resource pool is one of a plurality of side link resource pools configured for the WTRU. The WTRU determines to start a second side link resource pool, and the second side link resource pool is one of the multiple side link resource pools configured for the WTRU; The WTRU initiates the second-side link resource pool; and The WTRU passes an indication to the second WTRU that the WTRU has started the second-side link resource pool. The method according to item 1 of the scope of patent application, wherein the WTRU starting the second side link resource pool includes that the WTRU identifies resources of the second side link resource pool that can be used for side link communication of the WTRU. The method of claim 1, wherein transmitting an indication that the WTRU has activated the second-side link resource pool includes transmitting a resource pool indicator (RPI). The method of claim 1, wherein transmitting an indication that the WTRU has started the second-side link resource pool includes passing an indication on an active resource pool. The method of claim 1, wherein transmitting an indication that the WTRU has activated the second-side link resource pool includes transmitting an indication on a separate physical channel. The method according to item 1 of the scope of patent application, wherein determining to start the second-side link resource pool includes: Determining that the activated first side link resource pool is not suitable for transmission of the side link packet based on a priority order associated with the side link packet to be transmitted by the WTRU; and Based on the priority order associated with the side link packet, it is determined that the second side link resource pool is suitable for the side link packet. The method according to item 1 of the scope of patent application, wherein determining to start the second-side link resource pool includes: Determining that the activated first side link resource pool is not suitable for receiving the side link packet based on a priority associated with a received side link packet; and Based on the priority associated with the side link packet, it is determined that the second side link resource pool is suitable for the side link packet. The method according to item 1 of the scope of patent application, wherein determining to start the second-side link resource pool includes: Determining that a transmission latency associated with a side link packet to be transmitted by the WTRU is not supported by the activated first side link resource pool; and It is determined that the second side link resource pool supports a transmission latency associated with the side link packet to be transmitted. The method according to item 8 of the scope of patent application, wherein the second-side link resource pool makes resources more frequently available in the time domain than the first-side link resource pool. The method described in item 8 of the patent application scope further includes: A side link control information (SCI) message indicating the transmission latency associated with the side link packet is received. The method described in item 1 of the patent application scope further includes: The WTRU measures an energy on the activated first side link resource pool, Wherein it is determined to start the second-side link resource pool including: Determining that the measured energy meets a critical value; and When it is determined that the measured energy meets a critical value, it is determined to start the second-side link resource pool. The method described in item 1 of the patent application scope further includes: The WTRU measures a channel busy ratio (CBR) on the activated first side link resource pool, Wherein it is determined to start the second-side link resource pool including: Determining that the measured CBR satisfies a critical value; and When it is determined that the measured CBR meets a critical value, it is determined to start the second-side link resource pool. The method described in item 1 of the patent application scope further includes: The number of a WTRU using a group of resource pools within a reference signal received power (RSRP) is sensed by the WTRU, Wherein it is determined to start the second-side link resource pool including: Determining that the number of WTRUs using the set of resource pools in the RSRP meets a critical value; and When it is determined that the number of the WTRUs using the group of resource pools in the RSRP meets a critical value, the starting side link resource pool is determined. The method according to item 1 of the scope of patent application, wherein determining to start the second-side link resource pool includes: Determining that the activated first-side link resource pool does not support a voice quality index (VQI) value; and It is determined that the second side link resource pool supports the VQI value. A method for starting a side-link resource pool implemented by a wireless transmission and reception unit (WTRU), the method includes: A first WTRU receives an instruction to start a first side link resource pool from a second WTRU, the first side link resource pool being one of a plurality of side link resource pools configured for the first WTRU; The first WTRU determines to start the first-side link resource pool based on the received instruction to start a first-side link resource pool; and The first WTRU starts the first side link resource pool. The method of claim 15, wherein receiving an instruction to start a first-side link resource pool includes receiving one-side link control information (SCI). The method of claim 15, wherein receiving an instruction to start a first side link resource pool includes detecting a plurality of side link transmissions using the first side link resource pool. The method according to item 15 of the scope of patent application, wherein receiving an instruction to start a first-side link resource pool comprises: receiving a resource pool indicator (RPI). The method of claim 15, wherein receiving an instruction to start a first-side link resource pool includes receiving an instruction to start a plurality of side-link resource pools associated with an identified classification. The method described in item 19 of the patent application scope further includes: Deactivate multiple active-side link resource pools with a classification smaller than the identified classification.