Grant settings for side-link positioning

Abstract

Systems, methods, apparatus, and computer program products for resources managed by a scheduling entity. One method includes receiving from a resource scheduling entity at least one configuration grant for sidelink transmission between multiple user devices via upper-layer signaling, and at least one resource within the at least one configuration grant for sidelink transmission based on at least one notification by at least one other user device activating or deactivating at least one resource.

Description

Technical Field

[0001] This application claims priority to U.S. Provisional Application No. 63 / 465,862, filed May 11, 2023. The entire contents of the above application are incorporated herein by reference.

[0002] Some embodiments generally relate to mobile communication systems or wireless communication systems such as 3rd Generation Partnership Project (3GPP (registered trademark)) Long Term Evolution (LTE), 5th Generation (5G) Radio Access Technology (RAT), New Radio (NR) access technology, 6th Generation (6G), and / or other communication systems. For example, some embodiments relate to systems and / or methods for resource allocation for sidelink positioning.

Background Art

[0003] Examples of mobile or wireless communication systems include radio frequency (RF) 5G RAT, Universal Mobile Communications System (UMTS) Terrestrial Radio Access Network (UTRAN), LTE Advanced UTRAN (E-UTRAN), LTE-Advanced (LTE-A), LTE-A Pro, NR access technologies, and / or the MultiFire Alliance. 5G radio systems refer to next-generation (NG) radio systems and network architectures. While 5G systems are typically based on 5G NR, 5G (or NG) networks can also be based on E-UTRA radio. NR is expected to support service categories such as enhanced mobile broadband (eMBB), ultra-high reliability low-latency communications (URLLC), and massive machine communications (mMTC). NR is expected to provide ultra-high-speed broadband, ultra-high reliability, low-latency connectivity, and massive networking to support the Internet of Things (IoT). Next-generation radio access networks (NG-RAN) refer to radio access networks (RANs) for 5G, and can provide radio access to NR, LTE, and LTE-A. In 5G, nodes that provide radio access functionality to user devices (similar to, for example, Node B in UTRAN or the evolved Node B (eNB) in LTE) are sometimes called next-generation Node B (gNB) when built on an NR radio, and next-generation eNB (NG-eNB) when built on an E-UTRAN radio. [Overview of the project]

[0004] According to some embodiments, the method may include receiving at least one configuration grant for sidelink transmission between multiple user devices from a resource scheduling entity via upper-layer signaling. The method may further include utilizing at least one resource within at least one configuration grant for sidelink transmission based on at least one notification, by at least one other user device activating or deactivating at least one resource.

[0005] According to one embodiment, the device may include means for receiving at least one configuration grant for sidelink transmission between multiple user devices from a resource scheduling entity via upper-layer signaling. The device may further include means for utilizing at least one resource within at least one configuration grant for sidelink transmission based on at least one notification, such as at least one other user device activating or deactivating at least one resource.

[0006] According to various embodiments, a non-temporary computer-readable medium, when executed by the device, may store program instructions that cause the device to execute at least the method. The method may include receiving at least one configuration grant for sidelink transmission between multiple user devices from a resource scheduling entity via upper-layer signaling. The method may further include utilizing at least one resource within at least one configuration grant for sidelink transmission based on at least one notification, by at least one other user device activating or deactivating at least one resource.

[0007] According to several embodiments, a computer program product may perform a method. The method may include receiving at least one configuration grant for sidelink transmission between multiple user devices from a resource scheduling entity via upper-layer signaling. The method may further include utilizing at least one resource within at least one configuration grant for sidelink transmission based on at least one notification, by at least one other user device activating or deactivating at least one resource.

[0008] According to one embodiment, the device may include at least one processor and at least one memory that, when executed by at least one processor, causes the device to perform at least one configuration grant for sidelink transmission between multiple user devices via upper-layer signaling from a resource scheduling entity. The at least one memory and instructions, when executed by at least one processor, may further cause the device to utilize at least one resource in at least one configuration grant for sidelink transmission based on at least one notification, by causing at least one other user device to activate or deactivate at least one resource.

[0009] According to various embodiments, the device may include a receiving circuit configured to receive at least one configuration grant for sidelink transmission between multiple user devices from a resource scheduling entity via upper-layer signaling. The device may further include a utilization circuit configured to utilize at least one resource within at least one configuration grant for sidelink transmission based on at least one notification, such as at least one other user device activating or deactivating at least one resource.

[0010] According to some embodiments, the method may include receiving at least one configuration grant for sidelink transmission between multiple user devices from a resource scheduling entity via upper-layer signaling. The method may further include sending at least one notification to at least other user devices configured to activate or deactivate at least one resource within at least one configuration grant for sidelink transmission.

[0011] According to one embodiment, the device may include means for receiving at least one configuration grant for sidelink transmission between multiple user devices from a resource scheduling entity via upper-layer signaling. The device may further include means for sending at least one notification to at least other user devices configured to activate or deactivate at least one resource within at least one configuration grant for sidelink transmission.

[0012] According to various embodiments, a non-transient computer-readable medium, when executed by the device, may store program instructions that cause the device to perform at least the Method. The Method may include receiving at least one configuration grant for sidelink transmission between multiple user devices from a resource scheduling entity via upper-layer signaling. The Method may further include sending at least one notification to at least other user devices configured to activate or deactivate at least one resource within at least one configuration grant for sidelink transmission.

[0013] According to several embodiments, a computer program product may perform a method. The method may include receiving at least one configuration grant for sidelink transmission between multiple user devices from a resource scheduling entity via upper-layer signaling. The method may further include sending at least one notification to at least other user devices configured to activate or deactivate at least one resource within at least one configuration grant for sidelink transmission.

[0014] According to one embodiment, the device may include at least one processor and at least one memory which, when executed by at least one processor, causes the device to receive at least one configuration grant from a resource scheduling entity via upper-layer signaling for sidelink transmission between multiple user devices. The at least one memory and instructions, when executed by at least one processor, may cause the device to further send at least one notification to other user devices configured to activate or deactivate at least one resource in at least one configuration grant for sidelink transmission.

[0015] According to various embodiments, the device may include a receiving circuit configured to receive from a resource scheduling entity, via upper-layer signaling, at least one configuration grant for sidelink transmission between multiple user devices. The device may further include a transmitting circuit configured to send at least one notification to other user devices, configured to activate or deactivate at least one resource within at least one configuration grant for sidelink transmission.

[0016] According to some embodiments, the method may include determining at least one configuration grant for sidelink transmission between multiple user devices. The method may further include transmitting at least one configuration grant to at least one of the multiple user devices via upper-layer signaling.

[0017] According to one embodiment, the device may include means for determining at least one configuration grant for sidelink transmission between multiple user devices. The device may further include means for transmitting at least one configuration grant to at least one of the multiple user devices via upper-layer signaling.

[0018] According to various embodiments, a non-temporary computer-readable medium, when executed by the device, may store program instructions that cause the device to execute at least one method. The method may include determining at least one configuration grant for sidelink transmission between multiple user devices. The method may further include transmitting at least one configuration grant to at least one of the multiple user devices via upper-layer signaling.

[0019] According to several embodiments, a computer program product may perform a method. The method may include determining at least one configuration grant for sidelink transmission between multiple user devices. The method may further include transmitting at least one configuration grant to at least one of the multiple user devices via upper-layer signaling.

[0020] According to one embodiment, the device may include at least one processor and at least one memory containing instructions that, when executed by at least one processor, cause the device to determine at least one configuration grant for sidelink transmission between a plurality of user devices. The at least one memory and instructions, when executed by at least one processor, may cause the device to further transmit at least one configuration grant to at least one of the plurality of user devices via higher-layer signaling.

[0021] According to various embodiments, the device may include a decision circuit configured to determine at least one setting grant for sidelink transmission between multiple user devices. The device may further include a transmission circuit configured to transmit at least one setting grant to at least one of the multiple user devices via upper-layer signaling.

[0022] According to some embodiments, the method may include sending a list of multiple user devices suitable for a sidelink configuration grant to a scheduling entity. The method may further include sending a trigger to the scheduling entity requesting resource allocation for the multiple user devices.

[0023] According to one embodiment, the device may include means for sending a list of multiple user devices suitable for a sidelink configuration grant to a scheduling entity. The device may further include means for sending a trigger to the scheduling entity requesting resource allocation for the multiple user devices.

[0024] According to various embodiments, a non-temporary computer-readable medium, when executed by the device, may store program instructions that cause the device to execute the method. The method may include sending a list of user devices suitable for a sidelink setting grant to a scheduling entity. The method may further include sending a trigger to the scheduling entity requesting resource allocation for the user devices.

[0025] According to some embodiments, a computer program product may perform a method. This method may include sending a list of multiple user devices suitable for a sidelink setting grant to a scheduling entity. The method may further include sending a trigger to the scheduling entity requesting resource allocation for the multiple user devices.

[0026] According to one embodiment, the apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to transmit, at least to a scheduling entity, a list of a plurality of user equipments suitable for a sidelink configuration grant. When the at least one memory and the instructions are executed by the at least one processor, the apparatus may further be caused to transmit, at least to the scheduling entity, a trigger for requesting resource allocation for the plurality of user equipments.

[0027] According to various embodiments, the apparatus may include a transmission circuit configured to transmit, to a scheduling entity, a list of a plurality of user equipments suitable for a sidelink configuration grant. The apparatus may further include a transmission circuit configured to transmit, to the scheduling entity, a trigger for requesting resource allocation for the plurality of user equipments.

Brief Description of the Drawings

[0028] To understand the embodiments appropriately, please refer to the accompanying drawings. [Figure 1] FIG. 1 shows an example of a sidelink positioning scenario. [Figure 2] FIG. 2 shows an example of a signaling diagram according to some embodiments. [Figure 3] FIG. 3 shows an example of another signaling diagram according to some embodiments. [Figure 4] FIG. 4 shows an example of a flowchart of a method according to various embodiments. [Figure 5] FIG. 5 shows an example of a flowchart of another method according to some embodiments. [Figure 6] FIG. 6 shows an example of a flowchart of another method according to some embodiments. [Figure 7] FIG. 7 shows an example of a flowchart of another method according to various embodiments. [Figure 8]Figure 8 shows examples of various network devices according to several embodiments. [Figure 9] Figure 9 shows examples of 5G network and system architectures in several embodiments. [Modes for carrying out the invention]

[0029] It will be readily apparent that the components of some embodiments generally described and illustrated herein can be arranged and designed in a variety of different configurations. Therefore, the following detailed description of some embodiments of systems, methods, apparatus, and computer program products relating to resource allocation for sidelink positioning is not intended to limit the scope of some embodiments, but rather to represent selected embodiments.

[0030] Sidelink (SL) positioning is performed based on the transmission of an SL positioning reference signal (PRS) between the anchor and target UE, enabling the localization of the target UE within the strict delay and accuracy requirements of the corresponding SL positioning session. Figure 1 shows an SL positioning scenario in which the target UE is performing an SL positioning session (i.e., exchanging SL-PRS with two anchor UEs to determine its position).

[0031] Various positioning methods can be used in SL positioning. For example, the SL Time to Arrive Difference (TDOA) method and the SL (Multi) Round-Trip Time (RTT) method enable the positioning of the target UE and / or the measurement of the distance of the target UE to a reference UE (e.g., an anchor UE).

[0032] Regarding resource allocation for SL PRS transmission, two methods have been introduced, based on NR SL Mode 1 (Network Control) and NR SL Mode 2 (UE Autonomous). In Method 1, a network entity (NE) (e.g., eNB, gNB) can allocate resources for SL PRS in the form of Type 1 or Type 2 dynamic grants or configuration grants (CG), similar to conventional SL communication. In contrast, in Method 2, the UE may autonomously select resources for SL PRS based on sensing or using random resource selection.

[0033] SL PRS transmission may be performed in an SL resource pool dedicated to SL positioning (i.e., a dedicated pool), or in an SL resource pool shared with SL communication (i.e., a shared pool).

[0034] With regard to SL-PRS resource allocation under Method 1, the transmitting UE may receive SL-PRS resource allocation signaling from the network via higher layers from the Location Management Function (LMF), dynamic grants, and / or via CG Type 1 / Type 2 from the Network Entity (NE). Thus, the NE may allocate resources for SL PRS transmission in the form of dynamic grants or Type 1 or Type 2 CGs, similar to conventional SL communication. To enable reliability control, dynamic SL grant downlink control information (DCI) may provide resources for one or more transport block transmissions. These transmissions may be subject to the SL Hybrid Automatic Retransmission Request (HARQ) procedure (if the operation is activated). Once the SL CG is set, it is immediately available to the UE until released by radio resource control (RRC) signaling (i.e., Type 1). The UE is permitted to continue using this type of SL CG even if a beam fault or physical layer problem occurs in the NR Uu, until the radio link fault (RLF) detection timer expires, after which it may fall back to the exception resource pool. The other type of SL CG (Type 2) may be set up once, but cannot be used until the NE sends a DCI to the UE indicating that the SL CG has been activated, and can only be used until another DCI indicates deactivation. The resources in both types of SL CG may be a collection of periodically repeating SL resources, which may be matched by the NE to the characteristics of V2X traffic. Setting up multiple CGs can accommodate different services or traffic types.

[0035] The scheduling operation by the NE may be driven by the UE performing an SL Buffer Status Report (BSR) procedure similar to that of the Uu to report its SL traffic characteristics to the NE and / or request SL resource allocation from the NE. UE support information regarding traffic patterns may be reported to the network to provide support information for CG configuration. The report message may include periodicity, time offset, message size, QoS information, and destination. During handover, SL transmission and reception can be performed based on the configuration of an exceptional transmit resource pool or SL CG type 1 and the target cell's receive resource pool, as provided in the handover command.

[0036] In SL positioning, multiple UEs may transmit SL PRS signals to estimate the absolute position of a target UE. In some positioning schemes, different UEs may need to transmit SL PRS signals with the shortest possible transmission interval or even simultaneously. For example, in the SL RTT scheme, the target UE and anchor UEs (or multiple anchor UEs) may transmit SL PRS signals to each other, but if the transmission interval is too long, the UEs may move, or clock drift or changes in synchronization criteria / synchronization state may occur, which can affect positioning accuracy and positioning delay. Similarly, in some SL TDOA schemes, multiple anchor UEs may transmit SL PRS signals simultaneously (or as close together as possible), and the target UE may calculate its own position information by measuring the time difference between the arrival of the received signals.

[0037] Some embodiments described herein may have various advantages and / or superiorities to overcome the aforementioned drawbacks. For example, in some embodiments, it is possible to allocate SL resources to multiple UEs in a timely, reliable, and efficient manner to achieve the required QoS in SL positioning involving multiple UEs transmitting SL PRS. Therefore, some embodiments described below aim to improve computer-related technologies.

[0038] In some embodiments, a group of SL positioning UEs (e.g., all anchors belonging to the same positioning session in response to a given positioning request) is identified (e.g., via an LMF or server UE). SL PRS transmissions by the UE group may be collectively scheduled by the upper layer in a single step using CG such that all (or at least simultaneous) transmissions consist of orthogonal SL PRS sequences (e.g., by the NE via RRC in Method 1 resource allocation, or by the server user equipment, possibly via the SL Positioning Protocol (SLPP), or via an RRC / Media Access Control (MAC) control element (CE) in Method 2 resource allocation). These grants may be collectively or individually activated / deactivated by lower-layer signaling on the SL (e.g., without network involvement, using SL Control Information (SCI) (e.g., outside the service area where conventional DCI activation is not possible)). Preferably, the SCI of the target UE is used, which allows UE multiplexing within the UE group at a resource granularity down to the maximum RE level and symbol level, and further enables general transmission adaptation to changing link conditions between UEs.

[0039] Several embodiments can improve the processing of SL transmissions from multiple UEs in SL positioning. In this case, SL PRS transmissions should be as close in time as possible and can be activated / deactivated based on changes in the link state between the SL positioning anchor and target. Various embodiments are applicable to all types of SL transmissions (communication, detection, positioning, etc.) and any number of scheduled UEs (one or more).

[0040] Figure 2 shows an example signaling diagram illustrating resources managed by scheduling entities such as NEs and UEs (e.g., servers and target UEs). In some embodiments, UE210, UE220, and UE230 may be similar to UE820, and scheduling entity 240 may be similar to NE810 or UE820 as shown in Figure 8.

[0041] First, UE210, UE220, UE230, and scheduling entity 240 may initiate an SL positioning session. Scheduling entity 240 may be notified of potential UEs (e.g., UE210, UE220, and UE230) that can group SL PRS transmissions for CCG resource allocation. Such information may be provided by UEs involved in SL positioning (such as target UEs and server UEs, e.g., UE210, UE220, and UE230) or by core network entities such as LMF that manage SL positioning.

[0042] Furthermore, the scheduling entity 240 may be requested / triggered to perform resource allocation for SL PRS transmissions related to a notified group of UEs. Such signaling may indicate the required SL PRS transmission characteristics (e.g., SL PRS parameters such as bandwidth and periodicity) and / or the QoS requirements for SL positioning received from the UE or LMF (e.g., positioning accuracy and delay). Accordingly, the scheduling entity 240 may determine at least one SL set CG (CCG) for SL PRS transmissions of one or more of UE210, UE220, and UE230. At least one SL CCG may include SL resources (including multiplexing) to be allocated to the UEs, which may include specific time / frequency / code domain resources, including SL PRS sequence IDs used to generate the reference signal sequence. Time / frequency resources may have coarser granularity, such as frequency subchannels and time slots / minislots, in addition to resource element (RE) and symbol unit granularity.

[0043] In operation 201, scheduling entity 240 may transmit at least one CCG to UE210, UE220, and / or UE230 via upper-layer signaling. In some embodiments, if scheduling entity 240 is an NE, scheduling entity 240 may provide the CCG via DL broadcast / groupcast / unicast signaling (e.g., RRC(re)configuration messages). Alternatively, if scheduling entity 240 is a UE, scheduling entity 240 may provide at least one CCG via SL broadcast / groupcast / unicast signaling (e.g., SLPP messages, MAC-CE, or SL unicast via SL RRC). In some embodiments, UE210, UE220, and / or UE230 may relay at least one CCG to one or more other UEs.

[0044] In some embodiments, at least one CCG may represent at least one of the following: a method for activating / deactivating resources (e.g., a UE capable of activating / deactivating, e.g., identified by ID), thresholds or ranges related to activation / deactivation (e.g., relating to time or distance), the state of the SL channel (e.g., line of sight (LOS) / non-line of sight (NLOS), SL reference signal received power (RSRP), etc.), SL congestion (e.g., measured by SL channel busy rate (CBR) and / or channel occupancy (CR)), and coverage conditions (e.g., defined by Uu and / or SL RRC state).

[0045] In various embodiments, at least one CCG may be arbitrarily configured with certain restrictions and conditions on its use. For example, at least one CCG may be used only within the coverage of the assigning NE, or it may be used both within and outside the assigning NE's coverage. Furthermore, for a group of UEs to use at least one CCG, at least one UE (e.g., a server / target UE) may need to be within the assigning NE's coverage. Also, at least one CCG may be associated with a timer, and if a UE is not within the assigning NE's coverage within the timer period, at least one CCG may be deactivated. Furthermore, at least one CCG may be associated with a geographical area and may only be activated if a UE is within the specified area (the UE knows its approximate location and can identify the geographical area). This can be used in scenarios where the network is aware of coverage gaps, and at least one CCG may be provided for a specific area.

[0046] In operation 202, UE230 may decide to activate at least one CCG (for example, at the start of an SL positioning session).

[0047] In operation 203, UE230 may send a collective activation of at least one CCG to UE210 and / or UE220 via lower-layer signaling (e.g., using SCI).

[0048] In operation 204, UE230 may use the notified / activated resources to make orthogonal SL PRS transmissions to UE210 and / or UE220 (e.g., for multi-RTT SL positioning). In operation 205, UE220 may use the notified / activated resources (e.g., for multi-RTT SL positioning) to make orthogonal SL PRS transmissions to UE230. Similarly, in operation 206, UE210 may use the notified / activated resources (e.g., for multi-RTT SL positioning) to make orthogonal SL PRS transmissions to UE230. In some embodiments, an SL CCG-activating (configured) UE (e.g., target UE) may notify other UEs of activation using control instructions via SL (e.g., via SCI), which may involve its own SL PRS transmission or physical SL shared channel (PSSCH) transmission. In some embodiments, scheduling entity 240 may continue to use DCI to activate at least one CCG for the target UE. Subsequently, the target UE (i.e., UE230) may send an SCI configured to activate at least one CCG to any UE that falls outside the coverage of the scheduling entity 240. This allows the scheduling entity 240 to exercise additional control over the resources.

[0049] In some exemplary embodiments (for example, if configured), the UE230 can also notify the scheduling entity 240 of resource activation (for example, via UL control information to the scheduling entity 240, or implicitly via SCI to the scheduling UE).

[0050] In operation 207, UE230 may decide to deactivate the CCG (e.g., at the end of the SL positioning session or when an NLOS link with the anchor is established). In various embodiments, the configured UE (i.e., UE230) may be one of the UEs that transmit the SL PRS (e.g., the anchor UE in the SL TDOA session), and at least one CCG can be activated in one or more UEs (e.g., other anchor UEs), which can then transmit SCIs for their own SL PRS transmissions. Resource activation of the anchor UE may be performed by the scheduling entity 240 or by the anchor UE (i.e., UE230) itself.

[0051] In various embodiments, the configured UE230 (e.g., target UE or server UE) can subsequently deactivate at least one SL CCG when SL positioning is complete or when an undesirable link condition occurs between UEs (e.g., due to NLOS between the target UE and the anchor UE).

[0052] In operation 208, UE230 may send a collective deactivation to at least one CCG via lower-layer signaling (e.g., using SCI). Notification of deactivation to UE210 and UE220, as well as to the scheduling entity 240, may be made according to the same signaling as for activation.

[0053] In some embodiments, activation and / or deactivation may be performed in relation only to a subset of resources or UEs within the CG.

[0054] Figure 3 shows an example signaling diagram of resources managed by scheduling entities such as NEs or UEs (e.g., servers or target UEs), which may be similar in operation to that shown in Figure 2. In some embodiments, UE320, UE330, and UE340 may be similar to UE820 shown in Figure 8, and scheduling entities 350 and LMF360 may be similar to NE810 or UE820 shown in Figure 8.

[0055] In some embodiments of the first option 301, in operation 301a, LMF360 may send a notification to scheduling entity 350 of a group of UEs suitable for the CCG (e.g., UE320, UE330, and UE340). In operation 301b, LMF360 may send a trigger / request resource allocation for the group of UEs to scheduling entity 350.

[0056] As an example of the second option 302, in operation 302a, UE340 may send a notification to scheduling entity 350 of a group of UEs (e.g., UE320, UE330, and UE340) that may also be suitable for CCG. In operation 302b, UE340 may send a trigger / request resource allocation for the group of UEs to scheduling entity 350.

[0057] In operation 303, the scheduling entity 350 may determine at least one CCG for UE320, UE330, and / or UE340.

[0058] In operation 304, scheduling entity 350 may send CCG for SL PRS for UE320, UE330, and UE340 to UE320, UE330, and UE340 by broadcast / group / unicast via upper-layer signaling.

[0059] In operation 305, UE340 may decide to activate the CCG (for example, when necessary SL positioning measurement).

[0060] In operation 306, UE340 may send a collective activation of the CCG via lower-layer signaling (e.g., SCI) to UE320 and UE330.

[0061] In operation 307, UE340 may send a notification of the activated CCG to the scheduling entity 350.

[0062] In operation 308, UE340 may transmit an orthogonal SL PRS transmission to UE320 and / or UE330 using the notified / activated resources (for example, for multi-RTT SL positioning). In operation 309, UE330 may transmit an orthogonal SL PRS transmission to UE340 using the notified / activated resources (for example, for multi-RTT SL positioning). Similarly, in operation 310 (for example, for multi-RTT SL positioning), UE320 may transmit an orthogonal SL PRS transmission to UE340 using the notified / activated resources.

[0063] In operation 311, UE340 may decide to deactivate the CCG (for example, at the end of SL positioning or when an NLOS link is established to an anchor).

[0064] In operation 312, UE340 may send a collective deactivation of the CCG to UE320 and / or UE330 via lower-layer signaling (e.g., SCI).

[0065] In operation 313, UE340 may send a notification of the deactivated CCG to the scheduling entity 350.

[0066] In various embodiments, instead of using SL control information transmitted directly between UEs, the activation / deactivation of at least one CCG may be notified by signaling over the network (for example, the target UE first notifies the NE via UL, and then the NE forwards this notification to the other UE via DL). This behavior is desirable when it is desired to deactivate resource-intensive SL PRS transmissions when UEs cannot communicate with each other due to a broken link. Communication between the LMF and the NE may be conducted via NRPPa signaling.

[0067] Figure 4 shows an example of a flowchart of Method 400, which can be performed by a UE such as the UE820 shown in Figure 8, according to various embodiments.

[0068] In step 401, the method may include receiving at least one CG for SL transmission between multiple UEs via upper-layer signaling from a resource scheduling entity such as NE810 and / or UE820, as shown in Figure 8. This at least one CG may be set for multiple UEs in an SL positioning session. The at least one CG may include at least one resource associated with multiple orthogonal SL PRS sequences. Multiple orthogonal SL PRS sequences may be orthogonal in at least the time domain, frequency domain, or code domain.

[0069] In step 402, the method further includes at least one resource in at least one CG for SL transmission based on at least one notification, by at least one other UE activating or deactivating at least one resource. The at least one notification may notify multiple UEs in an SL positioning session of the activation and / or deactivation of at least one resource via lower-layer signaling. The lower-layer signaling may include SCI. The upper-layer signaling may include at least one of RRC signaling, MAC CE signaling, LPP signaling, or SLPP signaling.

[0070] Figure 5 shows an example of a flowchart of Method 500, which can be performed by a UE such as the UE820 shown in Figure 8, according to various embodiments.

[0071] In step 501, the method may include receiving at least one CG for SL transmission between multiple UEs from resource scheduling entities such as NE810 and / or UE820 via upper-layer signaling, as shown in Figure 8.

[0072] In step 502, the method may further include sending at least one notification to at least one other UE configured to activate or deactivate at least one resource in at least one CG.

[0073] At least one CG may be set for multiple UEs in an SL positioning session. At least one CG may include at least one resource associated with multiple orthogonal SL PRS sequences. Multiple orthogonal SL PRS sequences may be orthogonal in at least one of the time domain, frequency domain, or code domain. At least one notification may notify multiple UEs in an SL positioning session of the activation and / or deactivation of at least one resource via lower-layer signaling. Lower-layer signaling may include SCI. Upper-layer signaling may include at least one of RRC signaling, MAC CE signaling, LPP signaling, or SLPP signaling.

[0074] In step 503, the method may further include sending a first list of multiple UEs suitable for SL CG to the resource scheduling entity, and sending a first trigger to the resource scheduling entity requesting resource allocation for the multiple UEs.

[0075] In step 504, the method may further include sending at least one notification to the resource scheduling entity indicating the activation or deactivation of at least one resource within at least one CG for SL transmission.

[0076] Figure 6 shows an example of a flowchart of Method 600 that can be performed by an NE or UE, such as the NE810 and / or UE820 shown in Figure 8, according to various embodiments.

[0077] In step 601, the method may include determining at least one CG for SL transmission between multiple UEs.

[0078] In step 602, the method may further include transmitting at least one CG to at least one of a plurality of UEs via upper-layer signaling.

[0079] At least one CG may be determined for multiple UEs in an SL positioning session. At least one CG may include at least one resource associated with multiple orthogonal SL PRS sequences. Multiple orthogonal SL PRS sequences may be orthogonal in at least one of the time domain, frequency domain, or code domain.

[0080] In step 603, the method may further include receiving a first list of multiple UEs suitable for SL CG from one UE, and receiving a first trigger from one UE requesting resource allocation for multiple UEs.

[0081] In step 604, the method may further include receiving at least one notification from the UE indicating the activation or deactivation of at least one resource in at least one CG for SL transmission.

[0082] In step 605, the method further includes receiving a second list of multiple UEs suitable for SL CG from the core NE, and receiving a second trigger from the core NE requesting resource allocation for the multiple UEs.

[0083] Figure 7 shows an example flowchart of Method 700, which may be performed by an LMF such as the NE810 and / or UE820 shown in Figure 8, according to various embodiments. In step 701, the Method may include sending a list of multiple UEs suitable for the SL CG to the scheduling entity. In step 702, the Method may further include sending a trigger to the scheduling entity requesting resource allocation for the multiple UEs. The device may include an LMF.

[0084] Figure 8 shows examples of systems according to several embodiments. In one embodiment, the system may include multiple devices, such as NE810 and / or UE820.

[0085] The NE810 may be one or more of the following: a base station (e.g., a 3G UMTS NodeB, a 4G LTE Advanced NodeB, or a 5G NR Next Generation NodeB), a service gateway, a server, and / or other access nodes, or a combination thereof.

[0086] The NE810 may further include at least one gNB centralized unit (CU), which may be associated with at least one gNB distributed unit (DU). At least one gNB-CU and at least one gNB-DU are connected via a fifth-generation core (5GC) to at least one F1 interface and at least one X n - Communicable via the C interface and / or at least one NG interface.

[0087] UE820 may include one or more mobile devices such as mobile phones, smartphones, PDAs, tablets, and portable media players; navigation units such as digital cameras, pocket video cameras, video game consoles, and GPS devices; desktop or laptop computers; single-location devices such as sensors and smart meters; or a combination of these. Furthermore, NE810 and / or UE820 may be one or more Citizens Broadband Wireless Service (CBSD) devices.

[0088] NE810 and / or UE820 may include at least one processor, designated as 811 and 821, respectively. Processors 811 and 821 may be embodied by any computing or data processing device, such as a central processing unit (CPU), application-specific integrated circuit (ASIC), or equivalent device. The processors may be implemented as a single controller or as multiple controllers or processors.

[0089] As shown in 812 and 822, at least one memory may be provided in one or more devices. The memory may be fixed or removable. The memory may store computer program instructions or computer code. Memories 812 and 822 may each be independently suitable storage devices such as non-temporary computer-readable media. The term “non-temporary” as used herein refers to the limitations of the medium itself (i.e., tangible, not signaling) rather than limitations on the persistence of data storage (e.g., random access memory (RAM) vs. read-only memory (ROM)). Hard disk drives (HDDs), random access memory (RAM), flash memory, and other suitable memory may be used. The memory may be integrated on a single integrated circuit, like the processor, or it may be separate from one or more processors. Furthermore, computer program instructions that may be stored in memory and processed by the processor may be computer program code in any suitable form, such as compiled or interpreted computer programs written in any suitable programming language.

[0090] Processors 811 and 821, memories 812 and 822, and any subset thereof may be configured to provide means for corresponding to the various blocks shown in Figures 2-7. Although not shown, the device may include positioning hardware, such as GPS or microelectromechanical system (MEMS) hardware, which may be used to determine the device's position. Other sensors are also permitted and may be configured to determine position, altitude, speed, bearing, etc., such as a barometer or compass.

[0091] As shown in Figure 8, transceivers 813 and 823 may be provided, and one or more devices may each include at least one antenna (814 and 824 in the illustration). A device may have multiple antennas, such as an antenna array configured for multiple input multiple output (MIMO) communication or multiple antennas for multiple communication schemes (RAT). Other configurations of these devices may also be provided. Transceivers 813 and 823 may be units or devices that can be configured as transmitters, receivers, both transmitters and receivers, or both transmit and receive.

[0092] Memory and computer program instructions are configured in combination with a processor for a specific device, allowing a hardware device such as a UE to execute one of the processes described above (i.e., Figures 2-7). Therefore, in some embodiments, computer instructions that, when executed in hardware, would execute one of the processes described herein may be encoded on a non-temporary computer-readable medium. Alternatively, in some embodiments, the process may be executed entirely in hardware.

[0093] In some embodiments, the device may include a circuit configured to perform any of the processes or functions shown in Figures 2 to 7. In this application, the term “circuit” may mean one or more or all of the following: (a) a hardware-only circuit implementation (such as an implementation consisting only of analog and / or digital circuits); (b) a combination of hardware circuitry and software (where applicable); (i) a combination of analog and / or digital hardware circuitry and software / firmware; and (ii) a configuration in which a part of a hardware processor and software (including a digital signal processor), software, and memory work together to enable a device such as a mobile phone or server to perform various functions; and (c) a hardware circuit and / or processor (e.g., a microprocessor or part of a microprocessor) that requires software (e.g., firmware) to operate, but where software is not required for operation or where it is not present. This definition of circuit applies to all uses of this term in this application (including claims). For further examples, in this application, the term “circuit” may also include a mere hardware circuit or processor (or more processors), or a part of a hardware circuit or processor and its associated software and / or firmware implementation. The term "circuit" also includes, for example, a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device, where applicable to the elements of a particular claim.

[0094] Figure 9 shows examples of 5G network and system architectures in several embodiments. It shows multiple network functions implemented as software operating as part of a network device, as the network device itself or as dedicated hardware, or as virtual functions operating as a network device or dedicated hardware. The NE and UE shown in Figure 9 may be similar to NE810 and UE820, respectively. User plane functions (UPF) may provide services such as intra-RAT and inter-RAT movement, data packet routing and forwarding, packet inspection, user plane QoS processing, downlink packet buffering, and / or triggering downlink data notifications. Application functions (AF) primarily interface with the core network, facilitate application utilization of traffic routing, and may interact with the policy framework.

[0095] In some embodiments, processors 811 and 821, as well as memories 812 and 822, may constitute part of a processing circuit or control circuit. Furthermore, in some embodiments, transceivers 813 and 823 may constitute part of a transmitting and receiving circuit.

[0096] In some embodiments, the apparatus (e.g., NE810 and / or UE820) may include means for performing the methods, processes, or any variations thereof described herein. Examples of means include one or more processors, memory, controllers, transmitters, receivers, and / or computer program code for performing the operations.

[0097] In various embodiments, the device 820 is controlled by memory 822 and processor 821 and receives at least one configuration grant for sidelink transmission between multiple user devices from a resource scheduling entity via upper-layer signaling, and utilizes at least one resource within the at least one configuration grant for sidelink transmission based on at least one notification, by at least one other user device activating or deactivating at least one resource.

[0098] Some embodiments may be directed to an apparatus that has means for performing any of the methods described herein, for example, means for receiving from a resource scheduling entity via upper-layer signaling at least one configuration grant for sidelink transmission between a plurality of user devices, and means for utilizing at least one resource in at least one configuration grant for sidelink transmission based on at least one notification, by at least one other user device activating or deactivating at least one resource.

[0099] In various embodiments, the device 820 is controlled by memory 822 and processor 821 and may receive from a resource scheduling entity via upper-layer signaling at least one configuration grant for sidelink transmission between multiple user devices and send at least one notification to at least other user devices configured to activate or deactivate at least one resource within at least one configuration grant for sidelink transmission.

[0100] Some embodiments may be directed to an apparatus having means for performing any of the methods described herein, for example, means for receiving from a resource scheduling entity via upper-layer signaling at least one configuration grant for sidelink transmission between a plurality of user devices, and means for sending to at least one notification configured to activate or deactivate at least one resource in at least one configuration grant for sidelink transmission to at least one other user device.

[0101] In various embodiments, device 810 and / or device 820, controlled by memory 812 / 822 and processor 811 / 821, may determine at least one configuration grant for sidelink transmission between multiple user devices and transmit that at least one configuration grant to at least one of the multiple user devices via upper-layer signaling.

[0102] Some embodiments may be directed to devices having means for performing any of the methods described herein. For example, a device may include means for determining at least one configuration grant for sidelink transmission between a plurality of user devices, and means for transmitting at least one configuration grant to at least one of the plurality of user devices via upper-layer signaling.

[0103] In various embodiments, the device 820 may be controlled by memory 822 and processor 821 and configured to send a list of multiple user devices suitable for setting up a sidelink to the scheduling entity and to send triggers to the scheduling entity requesting resource allocation for the multiple user devices.

[0104] Some embodiments may be directed to an apparatus having means for performing any of the methods described herein, for example, means for sending a list of multiple user devices suitable for a sidelink setting grant to a scheduling entity, and means for sending a trigger to the scheduling entity requesting resource allocation for the multiple user devices.

[0105] The features, structures, or characteristics of the embodiments described throughout this specification may be combined in any suitable way in one or more embodiments. For example, the phrases “various embodiments,” “one embodiment,” “several embodiments,” and other similar expressions used throughout this specification may mean that the specific features, structures, or characteristics described in relation to an embodiment are included in at least one embodiment. Therefore, the appearance of phrases such as “in various embodiments,” “in one embodiment,” “several embodiments,” and other similar expressions throughout this specification does not necessarily refer to the same set of exemplary embodiments, and the described features, structures, or characteristics may be combined in any suitable way in one or more exemplary embodiments.

[0106] In this specification, when the phrases "at least one of the following: <list of two or more elements>" and "list of at least one or more elements," and similar expressions, are linked by "and" or "or," they mean at least one of any two elements, at least two or more elements, or at least all of the elements.

[0107] Furthermore, the different functions and procedures described above may be performed in different orders or in parallel with each other, as needed. Also, one or more of the functions and procedures described may be optional or combined, as needed. Therefore, the above description illustrates, and does not limit, the principles and teachings of several embodiments.

[0108] Those skilled in the art will readily understand that the exemplary embodiments described above can be implemented using different sequences of steps and / or different hardware elements than those disclosed. Therefore, while several embodiments have been described based on these exemplary embodiments, those skilled in the art will understand that certain modifications, variations, and alternative structures are apparent, while remaining within the spirit and scope of the exemplary embodiments.

[0109] Partial glossary 3GPP (Registered Trademark) Third Generation Partnership Project 5G (5th generation) 5GC (5th Generation Core) 6G (6th Generation) AF Application Function AoA Arrival Corner ASIC (Application-Specific Integrated Circuit) BSR Buffer Status Report CBR channel busy rate CBSD (Citizens' Broadband Wireless Service) Equipment CCG Group Setting Grant CE control element CG setting grant CPU (Central Processing Unit) CR channel occupancy CU (Centralized Processing Unit) DCI Downlink Control Information DL Downlink DU Distributed Unit eMBB Enhanced Mobile Broadband eNB Advanced Node B gNB Next Generation Node B GPS (Global Positioning System) HARQ Hybrid Automated Resend Request HDD (Hard Disk Drive) IoT (Internet of Things) LMF location management function LOS (Limited Sight) LPP Long-Term Evolution Positioning Protocol LTE Long-Term Evolution LTE-A Long-Term Evolution Advanced MAC Media Access Control MEMS (Micro Electromechanical Systems) MIMO multiple input multiple output mMTC Large-Scale Machine-Type Communication NE Network Entity Next generation Next generation Next-generation evolution node B Next-generation evolution node B NG-RAN Next Generation Wireless Access Network NLOS out of forecast NR new radio NRPPa (New Radio Positioning Protocol A) PDA (Personal Digital Assistant) PRS positioning reference signal PSSCH Physical Sidelink Shared Channel QoS (Quality of Service) RAM (Random Access Memory) RAN (Radio Access Network) RAT (Radio Access Technology) RE Resource Element RF radio frequency RLF Wireless Link Failure ROM (Read-only memory) RRC (Radio Resource Control) RSRP Received Signal Power Round-trip time (RTT) SCI Sidelink Control Information SINR (Signal-to-Noise Ratio) SL Sidelink SLPP Sidelink Positioning Protocol TDOA Arrival Time Difference UE User Equipment UMTS Universal Mobile Communications System UPF User Plane Functionality URLLC ultra-reliable low-latency communication UTRAN Universal Mobile Communication System Terrestrial Wireless Access Network V2X vehicle-to-vehicle communication

Claims

1. The resource scheduling entity receives at least one configuration grant for sidelink transmission between multiple user devices via upper-layer signaling, At least one resource in at least one configuration grant for sidelink transmission is utilized based on at least one notification by at least one other user device activating or deactivating at least one resource, Methods that include...

2. The method according to claim 1, wherein the at least one setting grant is set for the plurality of user devices in a sidelink positioning session.

3. The method according to claim 1 or 2, wherein the at least one setting grant includes at least one resource related to a plurality of orthogonal sidelink positioning reference signal sequences.

4. The method of claim 3, wherein the plurality of orthogonal sidelink positioning reference signal sequences are orthogonal in at least one of the time domain, frequency domain, or code domain.

5. The method according to any one of claims 1 to 4, wherein the at least one notification notifies the plurality of user devices of the activation of the at least one resource in the sidelink positioning session via lower-layer signaling.

6. The method according to any one of claims 1 to 5, wherein the at least one notification notifies the plurality of user devices of the deactivation of the at least one resource in the sidelink positioning session via lower-layer signaling.

7. The method according to claim 5 or 6, wherein the lower layer signaling includes side link control information.

8. The method according to any one of claims 1 to 7, wherein the upper layer signaling includes at least one of wireless resource control signaling, media access control element signaling, long-term evolution positioning protocol signaling, or sidelink positioning protocol signaling.

9. The resource scheduling entity receives at least one configuration grant for sidelink transmission between multiple user devices via upper-layer signaling, Sending at least one notification to at least other user devices that is configured to activate or deactivate at least one resource in at least one configuration grant for sidelink transmission, Methods that include...

10. The method of claim 9, wherein the at least one setting grant is set for the plurality of user devices in a sidelink positioning session.

11. The method according to claim 9 or 10, wherein the at least one setting grant includes at least one resource related to a plurality of orthogonal sidelink positioning reference signal sequences.

12. The method according to claim 11, wherein the plurality of orthogonal sidelink positioning reference signal sequences are orthogonal in at least one of the time domain, frequency domain, or code domain.

13. The method according to any one of claims 9 to 12, wherein the at least one notification notifies the plurality of user devices of the activation of the at least one resource in the sidelink positioning session via lower-layer signaling.

14. The method according to any one of claims 9 to 13, wherein the at least one notification notifies the plurality of user devices of the deactivation of the at least one resource in the sidelink positioning session via lower-layer signaling.

15. The method according to claim 13 or 14, wherein the lower layer signaling includes side link control information.

16. The method according to any one of claims 9 to 15, wherein the upper layer signaling includes at least one of radio resource control signaling, media access control element signaling, long-term evolution positioning protocol signaling, or sidelink positioning protocol signaling.

17. To transmit to the resource scheduling entity the first list of the multiple user devices suitable for side link setting grant, To send a first trigger to the resource scheduling entity requesting resource allocation for the plurality of user devices, The method according to any one of claims 9 to 16, further comprising:

18. The method according to any one of claims 9 to 17, further comprising sending the at least one notification to the resource scheduling entity notifying it of the activation or deactivation of the at least one resource in the at least one setting grant for sidelink transmission.

19. Determine at least one configuration grant for sidelink transmission between multiple user devices, via upper-layer signaling, transmit the at least one configuration grant to at least one of the plurality of user devices, Methods that include...

20. The method according to claim 19, wherein the at least one setting grant is determined for the plurality of user devices in a sidelink positioning session.

21. The method according to claim 19 or 20, wherein the at least one setting grant includes at least one resource related to a plurality of orthogonal sidelink positioning reference signal sequences.

22. The method according to claim 21, wherein the plurality of orthogonal sidelink positioning reference signal sequences are orthogonal in at least one of the time domain, frequency domain, or code domain.

23. Receiving a first list of the user devices suitable for granting sidelink settings from the user devices, The first trigger is received from the user device requesting resource allocation to the plurality of user devices, The method according to any one of claims 19 to 22, further comprising:

24. The method according to any one of claims 19 to 23, further comprising receiving at least one notification from the user device notifying the activation or deactivation of the at least one resource in the at least one configuration grant for sidelink transmission.

25. Receiving a second list of the multiple user devices suitable for sidelink configuration grants from the core network entity, The core network entity receives a second trigger to request resource allocation for the multiple user devices, The method according to any one of claims 19 to 24, further comprising:

26. Sending a list of the multiple user devices suitable for side link configuration grants to the scheduling entity, Sending a trigger to the scheduling entity to request resource allocation for the aforementioned multiple user devices, Methods that include...

27. The method according to claim 26, wherein the device includes a position management function.

28. It is a device, At least one processor, When executed by the at least one processor, the device has at least one memory that stores instructions causing it to perform the method according to any one of claims 1 to 27, A device equipped with the following features.

29. An apparatus comprising means for carrying out the method described in any one of claims 1 to 27.

30. A non-temporary computer-readable medium that, when executed by the device, stores program instructions causing the device to execute at least one of the methods according to claims 1 to 27.

31. An apparatus comprising a circuit configured to perform the method according to any one of claims 1 to 27.

32. A computer program that, when executed by a device, stores instructions causing the device to perform the method according to any one of claims 1 to 27.

Images